From owner-freebsd-hackers Sun Oct 7 10:49:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from orange.csi.cam.ac.uk (orange.csi.cam.ac.uk [131.111.8.77]) by hub.freebsd.org (Postfix) with ESMTP id 7683F37B407; Sun, 7 Oct 2001 10:49:15 -0700 (PDT) Received: from dr263.sel.cam.ac.uk ([131.111.129.153] helo=cam.ac.uk ident=dave) by orange.csi.cam.ac.uk with esmtp (Exim 3.22 #1) id 15qI38-0002lk-00; Sun, 07 Oct 2001 18:49:14 +0100 Message-ID: <3BC094EB.1020702@cam.ac.uk> Date: Sun, 07 Oct 2001 17:46:19 +0000 From: David Rufino User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.4) Gecko/20010916 X-Accept-Language: en-us MIME-Version: 1.0 To: freebsd-hackers@freebsd.org, freebsd-multimedia@freebsd.org Subject: atapi cd problems Content-Type: multipart/mixed; boundary="------------000704070801020104030403" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------000704070801020104030403 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Hi, I'm having trouble ripping cdda tracks, using cdda2wav under freebsd. As far as I know my IDE setup is fine, and I've successfully done it before. Attached is my dmesg output which should contain all the relevant info. Anyone know why it isn't working? Thanks, David --------------000704070801020104030403 Content-Type: text/plain; name="out" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="out" Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. Timecounter "i8254" frequency 1193182 Hz CPU: AMD Duron(tm) Processor (755.06-MHz 686-class CPU) Origin = "AuthenticAMD" Id = 0x631 Stepping = 1 Features=0x183f9ff AMD Features=0xc0440000<,AMIE,DSP,3DNow!> real memory = 201261056 (196544K bytes) avail memory = 192724992 (188208K bytes) Preloaded elf kernel "kernel" at 0xc0315000. Preloaded elf module "snd_via82c686.ko" at 0xc031509c. Preloaded elf module "snd_pcm.ko" at 0xc0315144. Pentium Pro MTRR support enabled Using $PIR table, 7 entries at 0xc00fdf00 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 10 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xd000-0xd00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd400-0xd41f irq 5 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd800-0xd81f irq 5 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered chip1: at device 7.4 on pci0 pcm0: port 0xe400-0xe403,0xe000-0xe003,0xdc00-0xdcff irq 11 at device 7.5 on pci0 vr0: port 0xe800-0xe87f mem 0xdf000000-0xdf00007f irq 11 at device 10.0 on pci0 vr0: Ethernet address: 00:80:c8:d5:6c:cf miibus0: on vr0 amphy0: on miibus0 amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto orm0:
after compiling a new kernel with only = adding=20 firewall support
my thinkpad 760xd wont reboot all the = way it just=20 syncs disks
and then hangs.
 
someone know the right flags for this? = the GENERIC=20 kernel that ships
with 4.4 and below seem to all work but = a new=20 kernel made with GENERIC dont.
 
thanks.
 
George
 
------=_NextPart_000_003D_01C150EE.4ECD7210-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 9 18:15:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 4556A37B403 for ; Tue, 9 Oct 2001 18:15:47 -0700 (PDT) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id f9A1G4i42222; Tue, 9 Oct 2001 20:16:04 -0500 (CDT) (envelope-from jlemon) Date: Tue, 9 Oct 2001 20:16:04 -0500 From: Jonathan Lemon To: "Eugene M. Kim" Cc: Jonathan Lemon , hackers@freebsd.org Subject: Re: VM question (I hate Intel 810/815 chipsets...) Message-ID: <20011009201604.D75389@prism.flugsvamp.com> References: <200110100037.f9A0bfv40852@prism.flugsvamp.com> <20011009180841.A26019@alicia.nttmcl.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20011009180841.A26019@alicia.nttmcl.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG It sounds like the right approach to me. I'm assuming that you'll be writing a kernel driver for the memory, which has a mmap entry point in the cdevsw. The driver's mmap routine would just return the address of the contigmalloc region. I believe that the bktr driver has an example of this approach. -- Jonathan On Tue, Oct 09, 2001 at 06:08:41PM -0700, Eugene M. Kim wrote: > Thank you for the reply. > > I also found contigmalloc() shortly after I posted the original question > (what an embarrassment ;-p), then met another restriction: Because these > memory regions are to be accessed by a userland process (X server), they > have to be somehow mapped into the user space. So far it seems I would > have to do something similar to vm_mmap(), but I'm not sure if this is a > right direction. Do you have any suggestions? > > Cheers, > Eugene > > On Tue, Oct 09, 2001 at 07:37:41PM -0500, Jonathan Lemon wrote: > > > > > > In article you write: > > >What would be the best way to allocate: > > > > > >1) a VM page whose physical address falls within a certain boundary, and > > >2) a VM object whose pages are contiguous in physical address space? > > > > > >Background: > > >The !@*%^*!&#^%*&!#^$!@ Intel 810/815 graphics controller requires its > > >instruction and hardware cursor buffers to reside within first 32MB and > > >512MB of *physical* memory space respectively. :( :( ;( The XFree86 > > >driver assumes the Linux memory model (virtual addr == physical addr), > > >so it runs on Linux, but not always on FreeBSD. > > > > You probably want contigmalloc(), which allocates a range of memory > > which is physically contiguous. (assuming this is a in-kernel driver) > > > > void * > > contigmalloc( > > unsigned long size, /* should be size_t here and for malloc() */ > > struct malloc_type *type, > > int flags, > > unsigned long low, > > unsigned long high, > > unsigned long alignment, > > unsigned long boundary) > > > > -- > > Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 9 18:27:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rodney.cnchost.com (rodney.concentric.net [207.155.252.4]) by hub.freebsd.org (Postfix) with ESMTP id 69D7637B406; Tue, 9 Oct 2001 18:27:39 -0700 (PDT) Received: from bitblocks.com (adsl-209-204-185-216.sonic.net [209.204.185.216]) by rodney.cnchost.com id VAA22073; Tue, 9 Oct 2001 21:27:38 -0400 (EDT) [ConcentricHost SMTP Relay 1.14] Message-ID: <200110100127.VAA22073@rodney.cnchost.com> To: Mike Barcroft Cc: freebsd-hackers@FreeBSD.org, audit@freebsd.org Subject: Re: strnstr(3) - New libc function for review In-reply-to: Your message of "Thu, 04 Oct 2001 21:57:06 EDT." <20011004215706.B34530@coffee.q9media.com> Date: Tue, 09 Oct 2001 18:27:38 -0700 From: Bakul Shah Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > I would appreciate comments/reviews of the following new addition to > libc. It is largely based off the current strstr(3) implementation. Sorry for not getting to this sooner. > /* > * Find the first occurrence of find in s, where the search is limited to the > * first slen characters of s. > */ > char * > strnstr(s, find, slen) > const char *s; > const char *find; > size_t slen; > { > char c, sc; > size_t len; > > if ((c = *find++) != '\0') { > len = strlen(find); > do { > do { > if ((sc = *s++) == '\0' || slen-- < 1) > return (NULL); > } while (sc != c); > if (len > slen) > return (NULL); > } while (strncmp(s, find, len) != 0); > s--; > } > return ((char *)s); > } Why not pass the length of the pattern as well? Regardless, why not use simpler code that is easier to prove right? char* strnstr(const char *s, size_t slen, const chat *p, size_t plen) { while (slen >= plen) { if (strncmp(s, p, plen) == 0) return (char*)s; s++, slen--; } return 0; } Another reason for passing in both string lengths is to allow switching to a more efficient algorithm. The above algorithm runs in slen*plen time. Other more efficient algorithms have a startup cost that can be hiddne for a fairly moderate value of slen*plen. So you'd insert something like if (worth_it_to_run_KMP_algo(splen, plen)) return kmp_strnstr(s, slen, p, plen); right above the while loop. This makes such functions useful for much larger strings (e.g. when you have mmapped in the whole file). -- bakul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 9 18:34:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id A6E5737B403; Tue, 9 Oct 2001 18:34:10 -0700 (PDT) Received: (from ache@localhost) by nagual.pp.ru (8.11.6/8.11.6) id f9A1Y3L86219; Wed, 10 Oct 2001 05:34:04 +0400 (MSD) (envelope-from ache) Date: Wed, 10 Oct 2001 05:34:03 +0400 From: "Andrey A. Chernov" To: Bakul Shah Cc: Mike Barcroft , freebsd-hackers@FreeBSD.ORG, audit@FreeBSD.ORG Subject: Re: strnstr(3) - New libc function for review Message-ID: <20011010053402.A86108@nagual.pp.ru> References: <20011004215706.B34530@coffee.q9media.com> <200110100127.VAA22073@rodney.cnchost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110100127.VAA22073@rodney.cnchost.com> User-Agent: Mutt/1.3.21i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 09, 2001 at 18:27:38 -0700, Bakul Shah wrote: > > Why not pass the length of the pattern as well? Regardless, > why not use simpler code that is easier to prove right? > > char* > strnstr(const char *s, size_t slen, const chat *p, size_t plen) It clearly violates API, passing two lengths. Remember that FreeBSD is not unique with strnstr(), some others have it too. -- Andrey A. Chernov http://ache.pp.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 9 18:50:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 39BE737B409 for ; Tue, 9 Oct 2001 18:50:21 -0700 (PDT) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.6/8.11.3) with ESMTP id f9A20kI06030; Tue, 9 Oct 2001 19:00:54 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200110100200.f9A20kI06030@mass.dis.org> To: "Eugene M. Kim" Cc: freebsd-hackers@freebsd.org Subject: Re: VM question (I hate Intel 810/815 chipsets...) In-Reply-To: Message from "Eugene M. Kim" of "Tue, 09 Oct 2001 16:57:35 PDT." <20011009165735.A22544@alicia.nttmcl.com> Date: Tue, 09 Oct 2001 19:00:46 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > What would be the best way to allocate: > > 1) a VM page whose physical address falls within a certain boundary, and > 2) a VM object whose pages are contiguous in physical address space? > > Background: > The !@*%^*!&#^%*&!#^$!@ Intel 810/815 graphics controller requires its > instruction and hardware cursor buffers to reside within first 32MB and > 512MB of *physical* memory space respectively. :( :( ;( The XFree86 > driver assumes the Linux memory model (virtual addr == physical addr), > so it runs on Linux, but not always on FreeBSD. You want to write a device driver to match this particular chip, which uses the bus_dmamem functions to allocate a conforming memory region, and then allow the userland process to mmap this region through your device node. It's nasty, but this sort of thing is just not normally done like this in the *nix world. Here's a sample to give you an idea of what I'm talking about wrt. allocating the memory. size_t size; /* size of region */ bus_dma_tag_t tag; /* busdma goo */ bus_dma_map_t map; void *mem; /* virtual pointer to region */ vm_offset_t physmem; /* physical pointer to region */ /* create a tag describing the memory you want */ bus_dma_tag_create( NULL, /* inherit from nobody */ 1, 0, /* alignment, boundary */ 0, /* low address */ (32 * 1024 * 1024), /* high address */ NULL, NULL, /* filter and argument */ size, /* size of region */ 1, /* maximum physical frags */ 0, /* flags */ &tag); /* allocate memory conforming to the tag */ mem = bus_dmamem_alloc(tag, &mem, BUS_DMA_NOWAIT, &map); /* map the memory into bus-visible space */ bus_dmamap_load(tag, map, mem, size, helper, (void *)&physmem, 0); ... /* unmap/free memory, free tag */ bus_dmamap_unload(tag, map); bus_dmamam_free(tag, mem, map); bus_dma_tag_destroy(tag); /* save the physical address of the region */ void helper(void *arg, bus_dma_segment_t *segs, int nseg, int error) { *(vm_offset_t *)arg = segs->ds_addr; } Note that this is the *only* correct way to do this (modulo bugs in what I've just written here). Contigmalloc() is the wrong API, and you should not use it. Regards, Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Oct 9 19:11:31 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from coffee.q9media.com (coffee.q9media.com [216.94.229.19]) by hub.freebsd.org (Postfix) with ESMTP id 020A537B406; Tue, 9 Oct 2001 19:11:21 -0700 (PDT) Received: (from mike@localhost) by coffee.q9media.com (8.11.6/8.11.6) id f9A2CLp50300; Tue, 9 Oct 2001 22:12:21 -0400 (EDT) (envelope-from mike) Date: Tue, 9 Oct 2001 22:12:20 -0400 From: Mike Barcroft To: Bakul Shah Cc: audit@FreeBSD.org Subject: Re: strnstr(3) - New libc function for review Message-ID: <20011009221220.C49828@coffee.q9media.com> References: <20011004215706.B34530@coffee.q9media.com> <200110100127.VAA22073@rodney.cnchost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110100127.VAA22073@rodney.cnchost.com>; from bakul@bitblocks.com on Tue, Oct 09, 2001 at 06:27:38PM -0700 Organization: The FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG [-hackers moved back to BCC. I had intended follow-ups to go to -audit, but there might be some interested hackers reading now. Follow-ups to this message go to -audit, thanks! :) ] Bakul Shah writes: > > I would appreciate comments/reviews of the following new addition to > > libc. It is largely based off the current strstr(3) implementation. > > Sorry for not getting to this sooner. > > > /* > > * Find the first occurrence of find in s, where the search is limited to the > > * first slen characters of s. > > */ > > char * > > strnstr(s, find, slen) > > const char *s; > > const char *find; > > size_t slen; > > { > > char c, sc; > > size_t len; > > > > if ((c = *find++) != '\0') { > > len = strlen(find); > > do { > > do { > > if ((sc = *s++) == '\0' || slen-- < 1) > > return (NULL); > > } while (sc != c); > > if (len > slen) > > return (NULL); > > } while (strncmp(s, find, len) != 0); > > s--; > > } > > return ((char *)s); > > } > > Why not pass the length of the pattern as well? Regardless, This is probably not needed for most uses for this. It would be rare to have two non-NUL terminated strings. On the other hand, this could be implemented in the future, if it's seen as useful. strnstr(3) could easily be modified to call a strnstrn() and use strlen(3) to get the missing size field. > why not use simpler code that is easier to prove right? > > char* > strnstr(const char *s, size_t slen, const chat *p, size_t plen) This prototype is inconsistent with any strn...(3) functions that I'm aware of. > { > while (slen >= plen) { > if (strncmp(s, p, plen) == 0) > return (char*)s; > s++, slen--; > } It seems to me, it would be a pessimization to call strncmp(3) when you don't even have one character that matches. > return 0; > } Do you mean: return (NULL) ? > Another reason for passing in both string lengths is to allow > switching to a more efficient algorithm. The above algorithm > runs in slen*plen time. Other more efficient algorithms have > a startup cost that can be hiddne for a fairly moderate value > of slen*plen. So you'd insert something like > > if (worth_it_to_run_KMP_algo(splen, plen)) > return kmp_strnstr(s, slen, p, plen); > > right above the while loop. This makes such functions > useful for much larger strings (e.g. when you have > mmapped in the whole file). Yes, I recall seeing these algorithms discussed recently and I believe it was concluded that making strstr(3) use one of these more advanced algorithms would be a pessimization for most cases. That said, don't let me hold you back from proposing alternative or complimentary functions to strnstr(3). Best regards, Mike Barcroft To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 0:30:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-relay1.yahoo.com (mail-relay1.yahoo.com [216.145.48.34]) by hub.freebsd.org (Postfix) with ESMTP id 4E76A37B403 for ; Wed, 10 Oct 2001 00:30:28 -0700 (PDT) Received: from yahoo-inc.com (db-cvad-2-tmp.yahoo.com [216.145.48.243]) by mail-relay1.yahoo.com (Postfix) with ESMTP id B68C58B5D4; Wed, 10 Oct 2001 00:30:27 -0700 (PDT) Message-ID: <3BC3F91A.1492C252@yahoo-inc.com> Date: Wed, 10 Oct 2001 00:30:34 -0700 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.2 i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Meyer Cc: hackers@FreeBSD.ORG Subject: Re: Debbuging hard lockups... References: <15297.57121.554185.659525@guru.mired.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Meyer wrote: > > I can generate hard lockups on my SMP box pretty easily. When locked, > it fails to respond to anything - I can't even get into the kernel > debugger to fire up. The lockups don't happen on UP machines under the > same conditions, so I can't even see if console debugging would work, > because I don't have a second SMP machine to run the kernel on. > > I'm running 4.4-stable, and I'm looking for suggestions on how to deal > with this, other than "don't do that". Debugging kernel options, maybe? How much ram do you have, and how long are you waiting? I find that it sometimes takes several minutes to dump 256M. HTH, Doug -- "We will not tire, we will not falter, and we will not fail." - George W. Bush, President of the United States September 20, 2001 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 1:18:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id E738E37B406 for ; Wed, 10 Oct 2001 01:18:06 -0700 (PDT) Received: from mindspring.com (dialup-209.247.137.241.Dial1.SanJose1.Level3.net [209.247.137.241]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA05576; Wed, 10 Oct 2001 01:18:03 -0700 (PDT) Message-ID: <3BC4046E.8C6D7189@mindspring.com> Date: Wed, 10 Oct 2001 01:18:54 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Eugene M. Kim" Cc: freebsd-hackers@freebsd.org Subject: Re: VM question (I hate Intel 810/815 chipsets...) References: <20011009165735.A22544@alicia.nttmcl.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Eugene M. Kim" wrote: > > What would be the best way to allocate: > > 1) a VM page whose physical address falls within a certain boundary, and > 2) a VM object whose pages are contiguous in physical address space? > > Background: > The !@*%^*!&#^%*&!#^$!@ Intel 810/815 graphics controller requires its > instruction and hardware cursor buffers to reside within first 32MB and > 512MB of *physical* memory space respectively. :( :( ;( The XFree86 > driver assumes the Linux memory model (virtual addr == physical addr), > so it runs on Linux, but not always on FreeBSD. How strange. There is code to allocate from the first 16M of memory, for bounce buffers and the like, for the bus code, which has to deal with ISA devices that can't address greater than 16M when doing a DMA. So if you allocated there, it would be no problem. The Linux idea seems bad to me -- but, of course, it's certainly conceptually easier, if you don't have to think about address virtualization. Normally FreeBSD's kernel lives in virtual address space in the 1G above 3G, and the user programs all think they are along in the 3G at the bottom. This makes copying data in and out much easier. For the kernel address space itself, the "physical=virtual" may be true on Linux (I doubt it is, or they could not support more than 4G on the newer Intel systems with segmentation windows to move gigs of memory around at a time for up to 16G), but on FreeBSD, you really have very little to *no* control of the memory pages you are granted. You also don't say whether the memory needs to be physically contiguous. If it does, then you will need to do contigmalloc() to get the memory; I'm pretty sure you can't do this and get bounce (low 16M) memory at the same time. So what you want to do may require you to look at the bounce buffer and contigmalloc() code. Note that FreeBSD doesn't force swappable pages out in the case you are calling contigmalloc(), so it may be that you will only be able to successfully reserve memory at boot time. If so, you would probably be much better off doing the reservation as part of machdep.c, which is memory that is contiguous off the end of the kernel BSS, and can only be allocated at boot time. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 1:21:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from albatross.prod.itd.earthlink.net (albatross.mail.pas.earthlink.net [207.217.120.120]) by hub.freebsd.org (Postfix) with ESMTP id 7053537B40A for ; Wed, 10 Oct 2001 01:21:07 -0700 (PDT) Received: from mindspring.com (dialup-209.247.137.241.Dial1.SanJose1.Level3.net [209.247.137.241]) by albatross.prod.itd.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id BAA09587; Wed, 10 Oct 2001 01:21:04 -0700 (PDT) Message-ID: <3BC40523.E7C4D13C@mindspring.com> Date: Wed, 10 Oct 2001 01:21:55 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Eugene M. Kim" Cc: Jonathan Lemon , hackers@freebsd.org Subject: Re: VM question (I hate Intel 810/815 chipsets...) References: <200110100037.f9A0bfv40852@prism.flugsvamp.com> <20011009180841.A26019@alicia.nttmcl.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG "Eugene M. Kim" wrote: > > Thank you for the reply. > > I also found contigmalloc() shortly after I posted the original question > (what an embarrassment ;-p), then met another restriction: Because these > memory regions are to be accessed by a userland process (X server), they > have to be somehow mapped into the user space. So far it seems I would > have to do something similar to vm_mmap(), but I'm not sure if this is a > right direction. Do you have any suggestions? Write a device driver, and mmap() the device after opening it. Alternately, consider doing the machdep.c trick, and setting the PG_U bit. One bad consequence of this, however, is that any runaway user process would be able to trash the memory, so a device mmap() approach is really a much better idea. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 1:54: 1 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from straylight.ringlet.net (straylight.ringlet.net [217.75.134.254]) by hub.freebsd.org (Postfix) with SMTP id E0C9D37B401 for ; Wed, 10 Oct 2001 01:53:55 -0700 (PDT) Received: (qmail 1588 invoked by uid 1000); 10 Oct 2001 08:53:49 -0000 Date: Wed, 10 Oct 2001 11:53:48 +0300 From: Peter Pentchev To: Steve Ames Cc: freebsd-hackers@freebsd.org Subject: Re: calendar nit? Message-ID: <20011010115348.C620@straylight.oblivion.bg> Mail-Followup-To: Steve Ames , freebsd-hackers@freebsd.org References: <200110092059.f99Kxmd14916@virtual-voodoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110092059.f99Kxmd14916@virtual-voodoo.com>; from steve@virtual-voodoo.com on Tue, Oct 09, 2001 at 03:59:48PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 09, 2001 at 03:59:48PM -0500, Steve Ames wrote: > > I was sending an e-mail to someone and wasn't sure what day Thanksgiving > was so I typed 'calendar -A 45' and saw the following: > > Nov 8* Thanksgiving Day (4th Thursday in November) > > Odd that... This is a little weirdness with the calendar(1) way of dealing with date specifications such as 'the Nth Wday of the month'. It calculates the date of the Wday in the week starting today, then calculates the week of the month that that date falls within. *Boggle*. There is a comparison afterwards, and if that fails, the holiday is still marked as fit to be printed, and its date is set to yesterday (around line 342 of day.c). Among other things, this is very much related to the current date, and it is of somewhat limited usability if used with the -A or -B options. Okay, it plain does not work if used with the -A or -B options. I'll try to rack my brains a bit more to see if there is a way to actually calculate the exact date that 'the Nth Wday of the month' falls upon. There seems to be a bit of a weirdness there in cases (like yours) when the current month is not the same as the month of the examined date. Hell, even the current *year* might not be the same! Okay, I'll try to think of something today, unless all of this makes my brain implode, as it is wont to do on sleepless weeks like this one.. G'luck, Peter -- Do you think anybody has ever had *precisely this thought* before? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 2: 0:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id 375A237B408 for ; Wed, 10 Oct 2001 02:00:09 -0700 (PDT) Received: from blossom.cjclark.org (dialup-209.245.138.251.Dial1.SanJose1.Level3.net [209.245.138.251]) by robin.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f9A901H18909; Wed, 10 Oct 2001 02:00:01 -0700 (PDT) Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.3) id f9A8xxD03113; Wed, 10 Oct 2001 01:59:59 -0700 (PDT) (envelope-from cjc) Date: Wed, 10 Oct 2001 01:59:58 -0700 From: "Crist J. Clark" To: Gordon Tetlow Cc: hackers@FreeBSD.ORG Subject: Re: nfsd and mountd in the wrong place Message-ID: <20011010015958.H387@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from gordont@gnf.org on Tue, Oct 09, 2001 at 05:33:18PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Oct 09, 2001 at 05:33:18PM -0700, Gordon Tetlow wrote: > I posted this to -arch and was met with (mostly) deafening silence. If > someone could please take care of this, I would be most grateful. Since it > requires a repo-copy, I guess Peter Wemm or JDP will need to be involved. Perhaps well tested patches to the rc(8) files and any source files than need to be modified would make this go more smoothly. -- Crist J. Clark cjclark@alum.mit.edu cjclark@jhu.edu cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 3:44: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-65-31-203-60.mmcable.com [65.31.203.60]) by hub.freebsd.org (Postfix) with SMTP id 4BFCF37B405 for ; Wed, 10 Oct 2001 03:43:56 -0700 (PDT) Received: (qmail 94907 invoked by uid 100); 10 Oct 2001 10:43:50 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15300.9830.589550.598186@guru.mired.org> Date: Wed, 10 Oct 2001 05:43:50 -0500 To: Doug Barton Cc: Mike Meyer , hackers@FreeBSD.ORG Subject: Re: Debbuging hard lockups... In-Reply-To: <3BC3F91A.1492C252@yahoo-inc.com> References: <15297.57121.554185.659525@guru.mired.org> <3BC3F91A.1492C252@yahoo-inc.com> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Doug Barton types: > Mike Meyer wrote: > > I can generate hard lockups on my SMP box pretty easily. When locked, > > it fails to respond to anything - I can't even get into the kernel > > debugger to fire up. The lockups don't happen on UP machines under the > > same conditions, so I can't even see if console debugging would work, > > because I don't have a second SMP machine to run the kernel on. > > > > I'm running 4.4-stable, and I'm looking for suggestions on how to deal > > with this, other than "don't do that". Debugging kernel options, maybe? > > How much ram do you have, and how long are you waiting? I find that it > sometimes takes several minutes to dump 256M. I don't think it's panicing, as I've waited 20 or more minutes at times for it, hoping it would come back. If anyone is interested in investigating this, install gkrellm along with a lot of plugins - the more, the merrier. On an SMP machine, it usually locks up pretty quickly, usually 10 to 15 minutes, though sometimes as long as an hour, though more plugins make it happen faster. But even having a single, simple plugin eventually locks things up. I've been running a couple of more complex plugins for days on a UP machine with no problems. http://www.mired.org/home/mwm/ Q: How do you make the gods laugh? A: Tell them your plans. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 4:21:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from village.telecomitalia.it (mail2.village.tin.it [195.14.96.139]) by hub.freebsd.org (Postfix) with ESMTP id 84F3D37B40A for ; Wed, 10 Oct 2001 04:21:42 -0700 (PDT) Received: from Trimarchi.SYNTHEMA ([213.82.202.73]) by village.telecomitalia.it with Microsoft SMTPSVC(5.5.1877.537.53); Wed, 10 Oct 2001 13:19:04 +0200 Message-Id: <5.0.0.25.2.20011010132443.00a3a050@pop1.village.tin.it> X-Sender: snt\sntmtrimarchi@pop1.village.tin.it X-Mailer: QUALCOMM Windows Eudora Version 5.0 Date: Wed, 10 Oct 2001 13:25:50 +0200 To: hackers@freebsd.org From: Trimarchi Michael Subject: ABI specification Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Where can i get the ABI specification and elf documentation? Best regards Michael Trimarchi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 4:29:23 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nas.dgap.mipt.ru (nas.dgap.mipt.ru [194.85.81.203]) by hub.freebsd.org (Postfix) with ESMTP id 00D1C37B409; Wed, 10 Oct 2001 04:29:12 -0700 (PDT) Received: from localhost (andrew@localhost) by nas.dgap.mipt.ru (8.11.6/8.11.6) with ESMTP id f9ABT1m50064; Wed, 10 Oct 2001 15:29:01 +0400 (MSD) (envelope-from andrew@nas.dgap.mipt.ru) Date: Wed, 10 Oct 2001 15:29:00 +0400 (MSD) From: "Andrew L. Neporada" To: Mike Barcroft Cc: audit@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: strnstr(3) - New libc function for review In-Reply-To: <20011004215706.B34530@coffee.q9media.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1603302548-1002713340=:50053" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1603302548-1002713340=:50053 Content-Type: TEXT/PLAIN; charset=US-ASCII I think you should write in ststr.3 that strnstr locates first occurrence of null-terminated string 'little' in ___null-terminated___ string 'big'. Andrew. P.S. Because str(n)str functions deal with null-terminated strings (i.e. we don't know sizes of strings), it is impossible to write algorithm, that will work faster (in average) than current implementation. P.P.S. In the case of binary strings it is possible to implement faster search -- see attachment. On Thu, 4 Oct 2001, Mike Barcroft wrote: > [BCC'd to -hackers for additional comments.] > > Hello, > I would appreciate comments/reviews of the following new addition to > libc. It is largely based off the current strstr(3) implementation. > > Patch attached and also available at: > http://people.FreeBSD.org/~mike/patches/strnstr.diff > > > Best regards, > Mike Barcroft > --0-1603302548-1002713340=:50053 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="strstr.c" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: bstrstr.c Content-Disposition: attachment; filename="strstr.c" I2luY2x1ZGUgPHN5cy90eXBlcy5oPg0KI2luY2x1ZGUgPHN5cy90aW1lLmg+ DQojaW5jbHVkZSA8bGltaXRzLmg+DQojaW5jbHVkZSA8c3RkaW8uaD4NCiNp bmNsdWRlIDxzdGRsaWIuaD4NCiNpbmNsdWRlIDxzdHJpbmcuaD4NCg0KI2Rl ZmluZQlTVFJTWgkoMTAwKjEwMjQpDQojZGVmaW5lCVBBVFNaCTUwMA0KI2Rl ZmluZQlUUllTCTEwMA0KDQp2b2lkICoNCmJzdHJzdHIocywgc2xlbiwgcCwg cGxlbikNCglyZWdpc3RlciBjb25zdCB2b2lkCSpzLCAqcDsNCglzaXplX3QJ CQlzbGVuLCBwbGVuOw0Kew0KCXJlZ2lzdGVyIGNvbnN0IHVfY2hhciAJKnN0 ciwgKnN1YnN0cjsNCglyZWdpc3RlciBzaXplX3QJCWksIG1heF9zaGlmdCwg Y3Vycl9zaGlmdDsNCg0KCXNpemVfdAkJCXNoaWZ0W1VDSEFSX01BWCArIDFd Ow0KDQoJaWYgKHMgPT0gTlVMTCB8fCBwID09IE5VTEwgfHwgcGxlbiA+IHNs ZW4gfHwgc2xlbiA9PSAwIHx8IHBsZW4gPT0gMCkNCgkJcmV0dXJuIChOVUxM KTsNCg0KCXN0ciA9IChjb25zdCB1X2NoYXIgKilzOw0KCXN1YnN0ciA9IChj b25zdCB1X2NoYXIgKilwOw0KDQoJZm9yIChpID0gMDsgaSA8PSBVQ0hBUl9N QVg7IGkrKykgc2hpZnRbaV0gPSBwbGVuICsgMTsNCglmb3IgKGkgPSAwOyBp IDwgcGxlbjsgaSsrKSBzaGlmdFtzdWJzdHJbaV1dID0gcGxlbiAtIGk7DQoN CglpID0gMDsNCgltYXhfc2hpZnQgPSBzbGVuIC0gcGxlbjsNCgl3aGlsZSAo aSA8PSBtYXhfc2hpZnQpIHsNCgkJaWYgKCpzdHIgPT0gKnN1YnN0ciAmJiAh bWVtY21wKHN0ciArIDEsIHN1YnN0ciArIDEsIHBsZW4gLTEpKQ0KCQkJcmV0 dXJuICgodm9pZCAqKXN0cik7DQoJCWN1cnJfc2hpZnQgPSBzaGlmdFtzdHJb cGxlbl1dOw0KCQlzdHIgKz0gY3Vycl9zaGlmdDsNCgkJaSArPSBjdXJyX3No aWZ0Ow0KCX0NCglyZXR1cm4gKE5VTEwpOw0KfQ0KDQppbnQNCm1haW4odm9p ZCkNCnsNCgljaGFyCQkqc3RyOw0KCXN0cnVjdCB0aW1ldmFsCWJlZm9yZSwg YWZ0ZXI7DQoJc2l6ZV90CQlpOw0KDQoNCglzcmFuZG9tZGV2KCk7DQoJc3Ry ID0gKGNoYXIgKiltYWxsb2MoU1RSU1ogKyBQQVRTWiArIDEpOw0KCWlmICgh c3RyKSB7DQoJCXByaW50Zigibm8gbWVtXG4iKTsNCgkJZXhpdCgxKTsNCgl9 DQoJZm9yIChpID0gMDsgaSA8IFNUUlNaICsgUEFUU1o7IGkrKykgew0KCQlz dHJbaV0gPSByYW5kb20oKSAmIDB4ZmY7DQoJCWlmICghc3RyW2ldKSBzdHJb aV0gPSAxOw0KCX0NCglzdHJbU1RSU1ogKyBQQVRTWl0gPSAwOw0KDQoJcHJp bnRmKCJzbGVuID0gJWQsIHBsZW4gPSAlZFxuIiwgU1RSU1ogKyBQQVRTWiwg UEFUU1opOw0KCWdldHRpbWVvZmRheSgmYmVmb3JlLCBOVUxMKTsNCglmb3Ig KGkgPSAwOyBpIDwgVFJZUzsgaSsrKQ0KCQlzdHJzdHIoc3RyLCBzdHIgKyBT VFJTWik7DQoJZ2V0dGltZW9mZGF5KCZhZnRlciwgTlVMTCk7DQoJYWZ0ZXIu dHZfc2VjIC09IGJlZm9yZS50dl9zZWM7DQoJYWZ0ZXIudHZfdXNlYyAtPSBi ZWZvcmUudHZfdXNlYzsNCglwcmludGYoIk9sZDogJWYgc2VjXG4iLCAoYWZ0 ZXIudHZfc2VjICsgYWZ0ZXIudHZfdXNlYy8xMDAwMDAwLjApL1RSWVMpOw0K DQoJZ2V0dGltZW9mZGF5KCZiZWZvcmUsIE5VTEwpOw0KCWZvciAoaSA9IDA7 IGkgPCBUUllTOyBpKyspDQoJCWJzdHJzdHIoc3RyLCBTVFJTWiArIFBBVFNa LCBzdHIgKyBTVFJTWiwgUEFUU1opOw0KCWdldHRpbWVvZmRheSgmYWZ0ZXIs IE5VTEwpOw0KCWFmdGVyLnR2X3NlYyAtPSBiZWZvcmUudHZfc2VjOw0KCWFm dGVyLnR2X3VzZWMgLT0gYmVmb3JlLnR2X3VzZWM7DQoJcHJpbnRmKCJOZXc6 ICVmIHNlY1xuIiwgKGFmdGVyLnR2X3NlYyArIGFmdGVyLnR2X3VzZWMvMTAw MDAwMC4wKS9UUllTKTsNCglmcmVlKHN0cik7DQoJcmV0dXJuICgwKTsNCn0N Cg== --0-1603302548-1002713340=:50053-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 7:15:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ranger.argus-systems.com (ranger.argus-systems.com [206.221.232.80]) by hub.freebsd.org (Postfix) with ESMTP id A332237B405 for ; Wed, 10 Oct 2001 07:15:22 -0700 (PDT) Received: from dedog.argus-systems.co.uk (host62-6-134-46.host.btclick.com [62.6.134.46]) by ranger.argus-systems.com (8.9.3/8.9.3) with ESMTP id JAA28804 for ; Wed, 10 Oct 2001 09:15:15 -0500 (CDT) Received: (from fergus@localhost) by dedog.argus-systems.co.uk (8.11.6/8.11.1) id f9AEIkN02028 for freebsd-hackers@freebsd.org; Wed, 10 Oct 2001 15:18:46 +0100 (BST) (envelope-from fergus) Date: Wed, 10 Oct 2001 15:18:46 +0100 From: Fergus Cameron To: freebsd-hackers@freebsd.org Subject: Re: reading files from win Message-ID: <20011010151846.C1834@dedog.argus-systems.co.uk> Mail-Followup-To: freebsd-hackers@freebsd.org References: <000c01c14b11$f07c74e0$1198e693@kolej.vslib.cz> <20011009085945.C27344@netapp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011009085945.C27344@netapp.com>; from boshea@netapp.com on Tue, Oct 09, 2001 at 08:59:45AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 09.10-08:59, brian o'shea wrote: > On Tue, Oct 02, 2001 at 09:14:56AM +0200, Martin Vana wrote: > > hi, > > is there any utility that can read a bsd FS from win/dos? > > thank you > > None that I have heard of. If it's really important that you access the > filesystem from Windows and you have a lot of CPU and memory to spare, > you could run VMware [1] on Windows with FreeBSD running in a virtual > machine. It's kind of a round-about way to do it, but it would probably > work. don't think so, you still won't be able to read the BSD file system as vmware does not host this in native (NTFS/FAT/FAT32 . . .) file system as far as i am aware. it uses a single large file to emulate (much like loopback image) or a disk partition (same a multi-boot). p.s. not actually run it on win so i could be wrong but that's my understanding you can, however, use ftp or other network transport between the file systems - perhaps that would be enough? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 7:38: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from straylight.ringlet.net (straylight.ringlet.net [217.75.134.254]) by hub.freebsd.org (Postfix) with SMTP id 47FA137B406 for ; Wed, 10 Oct 2001 07:37:52 -0700 (PDT) Received: (qmail 4368 invoked by uid 1000); 10 Oct 2001 14:37:32 -0000 Date: Wed, 10 Oct 2001 17:37:31 +0300 From: Peter Pentchev To: Fergus Cameron Cc: freebsd-hackers@freebsd.org Subject: Re: reading files from win Message-ID: <20011010173731.B3510@straylight.oblivion.bg> Mail-Followup-To: Fergus Cameron , freebsd-hackers@freebsd.org References: <000c01c14b11$f07c74e0$1198e693@kolej.vslib.cz> <20011009085945.C27344@netapp.com> <20011010151846.C1834@dedog.argus-systems.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011010151846.C1834@dedog.argus-systems.co.uk>; from cameron@argus-systems.com on Wed, Oct 10, 2001 at 03:18:46PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Oct 10, 2001 at 03:18:46PM +0100, Fergus Cameron wrote: > On 09.10-08:59, brian o'shea wrote: > > On Tue, Oct 02, 2001 at 09:14:56AM +0200, Martin Vana wrote: > > > hi, > > > is there any utility that can read a bsd FS from win/dos? > > > thank you > > > > None that I have heard of. If it's really important that you access the > > filesystem from Windows and you have a lot of CPU and memory to spare, > > you could run VMware [1] on Windows with FreeBSD running in a virtual > > machine. It's kind of a round-about way to do it, but it would probably > > work. > > don't think so, you still won't be able to read the BSD file system as vmware > does not host this in native (NTFS/FAT/FAT32 . . .) file system as far > as i am aware. it uses a single large file to emulate (much like loopback > image) or a disk partition (same a multi-boot). > > p.s. not actually run it on win so i could be wrong but that's my > understanding > > you can, however, use ftp or other network transport between the file > systems - perhaps that would be enough? I've done this with Samba on FreeBSD under VMware on Windows, and it... well.. it worked.. and that's about as much as I can say. You can forget about performance. I've heard that there were some non-real-time, Explorer-like programs which could read UFS/FFS and display it in an Explorer-like window to mess with. I don't remember names though. G'luck, Peter -- If this sentence were in Chinese, it would say something else. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 8:17:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from nas.dgap.mipt.ru (nas.dgap.mipt.ru [194.85.81.203]) by hub.freebsd.org (Postfix) with ESMTP id C759037B408 for ; Wed, 10 Oct 2001 08:17:08 -0700 (PDT) Received: from localhost (andrew@localhost) by nas.dgap.mipt.ru (8.11.6/8.11.6) with ESMTP id f9AFGlI51376; Wed, 10 Oct 2001 19:16:48 +0400 (MSD) (envelope-from andrew@nas.dgap.mipt.ru) Date: Wed, 10 Oct 2001 19:16:46 +0400 (MSD) From: "Andrew L. Neporada" To: Matt Dillon Cc: Maxime Henrion , Dwayne , freebsd-hackers@FreeBSD.ORG Subject: Re: Memory allocation question In-Reply-To: <200110030552.f935q5j63360@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, 2 Oct 2001, Matt Dillon wrote: > > : > :Dwayne wrote: > :> I'm creating an app where I want to use memory to store data so I > :> can get at it quickly. The problem is, I can't afford the delays that > :> would occur if the memory gets swapped out. Is there any way in FreeBSD > :> to allocate memory so that the VM system won't swap it out? > :> > :I think mlock(2) is what you want. > : > :Maxime Henrion > :-- > :Don't be fooled by cheap finnish imitations ; BSD is the One True Code > > Don't use mlock(). Could you please explain that. Thanks. > > Use SysV Shared memory segments. If you tell the kernel to use > physical ram for SysV shared memory (kern.ipc.shm_use_phys=1) > then any shm segments you allocate (see manual pages for > shmctl, shmget, and shmat) will reside in unswappable shared memory. > > -Matt > > > 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 Oct 10 8:33:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snark.rinet.ru (snark.rinet.ru [195.54.192.73]) by hub.freebsd.org (Postfix) with ESMTP id C16E637B405; Wed, 10 Oct 2001 08:33:03 -0700 (PDT) Received: (from yar@localhost) by snark.rinet.ru (8.11.6/8.11.6) id f9AFWuT64862; Wed, 10 Oct 2001 19:32:56 +0400 (MSD) (envelope-from yar) Date: Wed, 10 Oct 2001 19:32:56 +0400 From: Yar Tikhiy To: Garrett Wollman Cc: net@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Some thoughts on if_ioctl() Message-ID: <20011010193256.A64375@snark.rinet.ru> References: <20011008113214.A68390@snark.rinet.ru> <200110081853.f98IrWf39097@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200110081853.f98IrWf39097@khavrinen.lcs.mit.edu> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Oct 08, 2001 at 02:53:32PM -0400, Garrett Wollman wrote: > < said: > > > Second, let's look at the handling of SIOCADDMULTI/SIOCDELMULTI. > > There is code obviously taken from if_loop.c and used in some > > drivers, which tries to do something with the third argument "data" > > of the if_ioctl() driver method if "data" isn't NULL. > > The historic implementation passed SIOCADDMULTI directly down to the > interface to implement, which resulted in lots of duplicated code all > over the place to manage the list of multicast addresses. Several > years ago, I rewrote the multicast management code to simply indicate > to the driver when the list has changed, obviating the need for the > driver itself to manage the list. > > > If I understand the kernel code right, if_ioctl()'s third argument > > is always NULL > > Not so. Any ioctl() in class 'i' which is not handled by the generic > code will get passed down to the driver to handle; some of these > requests may require the data pointer. Sorry, I wrote an unclear phrase. I implied not all possible ioctl(2) requests, but only the SIOC{ADD|DEL}MULTI case. In that case, "data" seems to be always NULL since it's the way if_addmulti() and if_delmulti() call ifp->if_ioctl(), and there is no other way to pass SIOC{ADD|DEL}MULTI to a driver's if_ioctl(). If it's true, all the old ugly code about AF_INET and AF_INET6 multicast groups may be safely removed from the interface drivers. All the interface drivers will fall into two categories: - those which may simply do nothing on these requests (if_loop, if_sl...) - those which will rebuild some sort of a hardware multicast filter. -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 10: 0:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bubo.vslib.cz (bubo.vslib.cz [147.230.16.1]) by hub.freebsd.org (Postfix) with ESMTP id D4F2B37B40F for ; Wed, 10 Oct 2001 10:00:37 -0700 (PDT) Received: from A410A (a410a.kolej.vslib.cz [147.230.152.17]) by bubo.vslib.cz (Postfix) with SMTP id 4BBFA8370 for ; Wed, 10 Oct 2001 19:00:36 +0200 (CEST) Message-ID: <002101c151ad$664255e0$1198e693@kolej.vslib.cz> From: "Martin Vana" To: Subject: cant port Date: Wed, 10 Oct 2001 19:02:52 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG hi, when i am trying to port some program from ports directory (4.3stable) it never connects to a ftp. Problem might be a firewall, there are so few ports allowed, but 21 is. Anyone has the same experience? Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 10:27: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mx01-a.netapp.com (mx01-a.netapp.com [198.95.226.53]) by hub.freebsd.org (Postfix) with ESMTP id 88ABA37B407 for ; Wed, 10 Oct 2001 10:26:53 -0700 (PDT) Received: from frejya.corp.netapp.com (mh01 [10.10.20.91]) by mx01-a.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id f9AHQo612297; Wed, 10 Oct 2001 10:26:50 -0700 (PDT) Received: from eclipse-fe.eng.netapp.com (localhost [127.0.0.1]) by frejya.corp.netapp.com (8.11.1/8.11.1/NTAP-1.2) with ESMTP id f9AHQOx06370; Wed, 10 Oct 2001 10:26:24 -0700 (PDT) Received: (from boshea@localhost) by eclipse-fe.eng.netapp.com (8.8.8+Sun/8.8.8) id KAA29053; Wed, 10 Oct 2001 10:26:24 -0700 (PDT) Date: Wed, 10 Oct 2001 10:26:23 -0700 From: "brian o'shea" To: Fergus Cameron Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: reading files from win Message-ID: <20011010102623.D27344@netapp.com> References: <000c01c14b11$f07c74e0$1198e693@kolej.vslib.cz> <20011009085945.C27344@netapp.com> <20011010151846.C1834@dedog.argus-systems.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <20011010151846.C1834@dedog.argus-systems.co.uk>; from Fergus Cameron on Wed, Oct 10, 2001 at 03:18:46PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Oct 10, 2001 at 03:18:46PM +0100, Fergus Cameron wrote: > > > > None that I have heard of. If it's really important that you access > > the filesystem from Windows and you have a lot of CPU and memory to > > spare, you could run VMware [1] on Windows with FreeBSD running in a > > virtual machine. It's kind of a round-about way to do it, but it > > would probably work. > > don't think so, you still won't be able to read the BSD file system as > vmware does not host this in native (NTFS/FAT/FAT32 . . .) file system > as far as i am aware. it uses a single large file to emulate (much > like loopback image) or a disk partition (same a multi-boot). VMware can use a physical disk or a large file as a virtual disk. -brian -- Brian O'Shea (408) 822-3249 3.3.163(Pen) "Stare not too deeply into the Pen, lest the Pen stare back into you." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 10:35:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from revolt.poohsticks.org (revolt.poohsticks.org [63.227.60.74]) by hub.freebsd.org (Postfix) with ESMTP id DD3C537B409 for ; Wed, 10 Oct 2001 10:35:19 -0700 (PDT) Received: from revolt.poohsticks.org (localhost [127.0.0.1]) by revolt.poohsticks.org (8.11.3/8.11.3) with ESMTP id f9AHZDs31676; Wed, 10 Oct 2001 11:35:13 -0600 (MDT) (envelope-from drew@revolt.poohsticks.org) Message-Id: <200110101735.f9AHZDs31676@revolt.poohsticks.org> To: "Martin Vana" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: cant port In-reply-to: Your message of "Wed, 10 Oct 2001 19:02:52 +0200." <002101c151ad$664255e0$1198e693@kolej.vslib.cz> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <31673.1002735313.1@revolt.poohsticks.org> Date: Wed, 10 Oct 2001 11:35:13 -0600 From: Drew Eckhardt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <002101c151ad$664255e0$1198e693@kolej.vslib.cz>, martin.vana@vslib.c z writes: >hi, >when i am trying to port some program from ports directory (4.3stable) it >never connects to a ftp. Problem might be a firewall, there are so few ports >allowed, but 21 is. Anyone has the same experience? Of course, establishing an active data connection also means having the server connect to an ephemeral port on your machine which is not allowed. make FETCH_BEFORE_ARGS=-p will give you passive ftp instead. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 11: 4:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 3DFCA37B401 for ; Wed, 10 Oct 2001 11:04:08 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f9AI3w320703; Wed, 10 Oct 2001 11:03:58 -0700 (PDT) (envelope-from dillon) Date: Wed, 10 Oct 2001 11:03:58 -0700 (PDT) From: Matt Dillon Message-Id: <200110101803.f9AI3w320703@earth.backplane.com> To: "Andrew L. Neporada" Cc: Maxime Henrion , Dwayne , freebsd-hackers@FreeBSD.ORG Subject: Re: Memory allocation question References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :On Tue, 2 Oct 2001, Matt Dillon wrote: : :> :> : :> :Dwayne wrote: :> :> I'm creating an app where I want to use memory to store data so I :> :> can get at it quickly. The problem is, I can't afford the delays that :> :> would occur if the memory gets swapped out. Is there any way in FreeBSD :> :> to allocate memory so that the VM system won't swap it out? :> :> :> :I think mlock(2) is what you want. :> : :> :Maxime Henrion :> :-- :> :Don't be fooled by cheap finnish imitations ; BSD is the One True Code :> :> Don't use mlock(). : :Could you please explain that. Thanks. mlock() can only be used by root, and it isn't really all that portable an interface. It cannot guarentee that the memory will actually be locked into core. :> :> Use SysV Shared memory segments. If you tell the kernel to use :> physical ram for SysV shared memory (kern.ipc.shm_use_phys=1) :> then any shm segments you allocate (see manual pages for :> shmctl, shmget, and shmat) will reside in unswappable shared memory. :> :> -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 11: 7:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id EDE4D37B401 for ; Wed, 10 Oct 2001 11:07:13 -0700 (PDT) Received: from mindspring.com (dialup-209.244.107.249.Dial1.SanJose1.Level3.net [209.244.107.249]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id LAA06072; Wed, 10 Oct 2001 11:07:10 -0700 (PDT) Message-ID: <3BC48E80.12A6634D@mindspring.com> Date: Wed, 10 Oct 2001 11:08:00 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Fergus Cameron Cc: freebsd-hackers@freebsd.org Subject: Re: reading files from win References: <000c01c14b11$f07c74e0$1198e693@kolej.vslib.cz> <20011009085945.C27344@netapp.com> <20011010151846.C1834@dedog.argus-systems.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > > hi, > > > is there any utility that can read a bsd FS from win/dos? > > > thank you THere are two implementations of the Heidemann framework for Windows, using the IFSMgr (Installable File System Manager) interface. The first was implemented in 1996 or so by Artisoft (I was one of the engineers). When Artisoft started crashing, it was assigned as part of severance to a couple of engineers, both of whom now work at Network Appliance. I don't believe it was ever released as a product. You could not read standard FFS using the code, since we had modified the UFS and FFS implementations themselves, to crank the directory block size up to 1k, still ensure atomicity, add a Unicode namespace, an early implementation of the soft updates code, and soft read-only (which ended up changing the superblock somewhat). This was all to make it a better FS for use by Windows. Another implementation of the Heidemann framework was posted about to the FreeBSD-FS list. This implementation provided a mechanism whereby one could run the FreeBSD NFS client code under Windows, and was done earlier this year. Extending this implementation to support FFS would likely require that you do what we did back in 1996 in order to minimize the impact on the FS code itself: provide FreeBSD kernel services under the Windows kernel as a module loaded via the PELOADER mechanism, including VM services and other less obvious services: at the time, I posted to the FreeBSD lists a list of the external references by the FS modules, and the list was some 160 functions... we were able to cut this down to 134 functions. This would give you a good start on supporting any FreeBSD FS implementation under Windows. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 13: 0: 7 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from host4.rpi.wulimasters.net (host4.rpi.wulimasters.net [128.113.36.114]) by hub.freebsd.org (Postfix) with ESMTP id D176A37B406 for ; Wed, 10 Oct 2001 13:00:03 -0700 (PDT) Received: (qmail 94856 invoked by uid 89); 10 Oct 2001 20:00:07 -0000 Message-ID: <20011010200007.94855.qmail@host4.rpi.wulimasters.net> From: "Alex Newman" To: freebsd-hackers@freebsd.org Subject: NATD+SSL Date: Wed, 10 Oct 2001 20:00:07 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Ok I know this sounds wacky, but I will try justify why i think it is usefull. If someone can think of a better way to achieve goals 1-3 or if they are silly goals please tell me. How easy would it be to implement ssl in the redirection part of natd. Some reasons why this is better than sslwrap/stunnel/sslproxy: 1) say you had a packet coming in on port 443 ->application->80->thttpd thttpd would see everything coming from localhost 2) It would allow you to more efficently have ssl proxy boxes infront of an array of webservers. This is useful if you had for instance a hardware crypto card in the ssl proxy. Currently the only decent way I know to do this today is with linux+stunnel since it has transparent proxy support. 3) Since these programs always are doing a redirect anyways it seems silly not to use natd for the redirction part of the process. Alex Newman www.wulimasters.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 13:22:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.gnf.org (relay.gnf.org [208.44.31.36]) by hub.freebsd.org (Postfix) with ESMTP id 6683437B407; Wed, 10 Oct 2001 13:22:22 -0700 (PDT) Received: from mail.gnf.org (smtp.gnf.org [10.0.0.11]) by relay.gnf.org (8.11.6/8.11.6) with ESMTP id f9AKMMj16197; Wed, 10 Oct 2001 13:22:22 -0700 Received: by mail.gnf.org (Postfix, from userid 888) id 1F87D11E511; Wed, 10 Oct 2001 13:21:38 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by mail.gnf.org (Postfix) with ESMTP id 1C61011A576; Wed, 10 Oct 2001 13:21:38 -0700 (PDT) Date: Wed, 10 Oct 2001 13:21:38 -0700 (PDT) From: Gordon Tetlow To: Cc: Subject: Re: bin/30972: nfsd and mountd are in the wrong location Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here is a diff that fixes a couple of issues and will facilitate moving nfsd and mountd into /usr/sbin This also removes the bogus nfs_client_flags since it is no longer used. This needs to happen to make migrating to the rc.d system easier. -gordon diff -ur /usr/src/etc/defaults/rc.conf etc.nfsd/defaults/rc.conf --- /usr/src/etc/defaults/rc.conf Wed Oct 10 09:36:28 2001 +++ etc.nfsd/defaults/rc.conf Wed Oct 10 09:43:11 2001 @@ -159,15 +159,16 @@ amd_flags="-a /.amd_mnt -l syslog /host /etc/amd.map /net /etc/amd.map" amd_map_program="NO" # Can be set to "ypcat -k amd.master" nfs_client_enable="NO" # This host is an NFS client (or NO). -nfs_client_flags="-n 4" # Flags to nfsiod (if enabled). nfs_access_cache="2" # Client cache timeout in seconds +nfs_bufpackets="DEFAULT" # bufspace (in packets) for client (or DEFAULT) nfs_server_enable="NO" # This host is an NFS server (or NO). +nfs_server_program="/usr/sbin/nfsd" # path to nfsd nfs_server_flags="-u -t -n 4" # Flags to nfsd (if enabled). single_mountd_enable="NO" # Run mountd only (or NO). +mountd_program="/usr/sbin/mountd" # path to mountd mountd_flags="-r" # Flags to mountd (if NFS server enabled). weak_mountd_authentication="NO" # Allow non-root mount requests to be served. nfs_reserved_port_only="NO" # Provide NFS only on secure port (or NO). -nfs_bufpackets="DEFAULT" # bufspace (in packets) for client (or DEFAULT) rpc_lockd_enable="NO" # Run NFS rpc.lockd (*broken!*) if nfs_server. rpc_statd_enable="NO" # Run NFS rpc.statd if nfs_server (or NO). portmap_enable="NO" # Run the portmapper service (YES/NO). diff -ur /usr/src/etc/rc.network etc.nfsd/rc.network --- /usr/src/etc/rc.network Fri Sep 21 10:53:51 2001 +++ etc.nfsd/rc.network Wed Oct 10 10:29:47 2001 @@ -614,7 +614,7 @@ ;; esac - mountd ${mountd_flags} + ${mountd_program} ${mountd_flags} case ${nfs_reserved_port_only} in [Yy][Ee][Ss]) @@ -623,7 +623,8 @@ ;; esac - echo -n ' nfsd'; nfsd ${nfs_server_flags} + echo -n ' nfsd'; + ${nfsd_server_program} ${nfs_server_flags} case ${rpc_lockd_enable} in [Yy][Ee][Ss]) @@ -659,7 +660,6 @@ case ${nfs_client_enable} in [Yy][Ee][Ss]) - #echo -n ' nfsiod'; nfsiod ${nfs_client_flags} if [ -n "${nfs_access_cache}" ]; then echo -n " NFS access cache time=${nfs_access_cache}" sysctl -w vfs.nfs.access_cache_timeout=${nfs_access_cache} >/dev/null To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 13:48:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail6.speakeasy.net (mail6.speakeasy.net [216.254.0.206]) by hub.freebsd.org (Postfix) with ESMTP id E13C737B405 for ; Wed, 10 Oct 2001 13:48:33 -0700 (PDT) Received: (qmail 99819 invoked from network); 10 Oct 2001 20:48:33 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail6.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 10 Oct 2001 20:48:33 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 10 Oct 2001 13:47:59 -0700 (PDT) From: John Baldwin To: Gordon Tetlow Subject: Re: bin/30972: nfsd and mountd are in the wrong location Cc: hackers@FreeBSD.org, freebsd-gnats-submit@FreeBSD.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 10-Oct-01 Gordon Tetlow wrote: > Here is a diff that fixes a couple of issues and will facilitate moving > nfsd and mountd into /usr/sbin Err, you don't need this to move the binaries. They will already be in the path so it will work fine with just 'mountd' and 'nfsd' as it does now. > This also removes the bogus nfs_client_flags since it is no longer used. I've committed that part. Something else that would really help here would be to update the rc.network script to kldload the nfsclient.ko and nfsserver.ko kernel modules if needed when nfs_client_enable and/or nfs_server_enable are set to YES. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 23:23:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from pintail.mail.pas.earthlink.net (pintail.mail.pas.earthlink.net [207.217.120.122]) by hub.freebsd.org (Postfix) with ESMTP id 0E03F37B405 for ; Wed, 10 Oct 2001 23:23:16 -0700 (PDT) Received: from mindspring.com (dialup-209.247.138.177.Dial1.SanJose1.Level3.net [209.247.138.177]) by pintail.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id XAA19070; Wed, 10 Oct 2001 23:23:12 -0700 (PDT) Message-ID: <3BC53ABD.68F1EA9E@mindspring.com> Date: Wed, 10 Oct 2001 23:22:53 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alex Newman Cc: freebsd-hackers@freebsd.org Subject: Re: NATD+SSL References: <20011010200007.94855.qmail@host4.rpi.wulimasters.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Alex Newman wrote: > 2) It would allow you to more efficently have ssl proxy boxes infront of an > array of webservers. This is useful if you had for instance a hardware > crypto card in the ssl proxy. Currently the only decent way I know to do > this today is with linux+stunnel since it has transparent proxy support. ClickArray, Andes Networks, and several other vendors have boxes which can do this. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Oct 10 23:41:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from seven.Alameda.net (seven.Alameda.net [64.81.63.137]) by hub.freebsd.org (Postfix) with ESMTP id EEC4C37B401 for ; Wed, 10 Oct 2001 23:41:17 -0700 (PDT) Received: by seven.Alameda.net (Postfix, from userid 1000) id ADC4C3A239; Wed, 10 Oct 2001 23:41:17 -0700 (PDT) Date: Wed, 10 Oct 2001 23:41:17 -0700 From: Ulf Zimmermann To: Alex Newman Cc: freebsd-hackers@freebsd.org Subject: Re: NATD+SSL Message-ID: <20011010234117.J518@seven.alameda.net> Reply-To: ulf@Alameda.net References: <20011010200007.94855.qmail@host4.rpi.wulimasters.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011010200007.94855.qmail@host4.rpi.wulimasters.net>; from dolemite@wulimasters.net on Wed, Oct 10, 2001 at 08:00:07PM +0000 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 4.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Oct 10, 2001 at 08:00:07PM +0000, Alex Newman wrote: > Ok I know this sounds wacky, but I will try justify why i think it is > usefull. If someone can think of a better way to achieve goals 1-3 or if > they are silly goals please tell me. How easy would it be to implement ssl > in the redirection part of natd. Some reasons why this is better than > sslwrap/stunnel/sslproxy: > > 1) say you had a packet coming in on port 443 ->application->80->thttpd > thttpd would see everything coming from localhost > > 2) It would allow you to more efficently have ssl proxy boxes infront of an > array of webservers. This is useful if you had for instance a hardware > crypto card in the ssl proxy. Currently the only decent way I know to do > this today is with linux+stunnel since it has transparent proxy support. > > 3) Since these programs always are doing a redirect anyways it seems silly > not to use natd for the redirction part of the process. > > Alex Newman > www.wulimasters.net Alteon has a solution for this like this: Client.443 -> Loadbalancer -> SSL offloader (call iSD) -> Loadbalancer -> Real Server. the Loadbalancer has its usual config of a virtual server for that port 443 and then filters which redirect the SSL traffic to the offloader. The offloader has the SSL certificates loaded and has some SSL hardware. It then decrypts the request, sends it back to the loadbalancer on a pretermined port (81 in their examples). The continuing of the filters then forwards these port 81 packets to a real server based on persistent connections/cookies or based on its normal load balancing. The SSL offerloader has 2 modes, transparent or proxy. In proxy mode, the real server sees the request as coming from the SSL offloader and in transparant mode as coming from the real client. Now the SSL offloader is basicly a Linux box. They lately removed most of the clues to show that is is a Linux box, but I have seen them. I have been thinking trying to put something simular for FreeBSD together (with or without hardware crypto card for SSL). It would be mostly a proof of concept for me. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-865-0204 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 3:51:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rfhs8012.fh-regensburg.de (rfhs8012.fh-regensburg.de [194.95.108.29]) by hub.freebsd.org (Postfix) with ESMTP id B9D2037B407 for ; Thu, 11 Oct 2001 03:51:28 -0700 (PDT) Received: from rfhpc8320.fh-regensburg.de (wup34966@rfhpc8320.fh-regensburg.de [194.95.108.32]) by rfhs8012.fh-regensburg.de (8.11.6/8.11.6) with ESMTP id f9BApPr09703 for ; Thu, 11 Oct 2001 12:51:25 +0200 (MEST) Received: (from wup34966@localhost) by rfhpc8320.fh-regensburg.de (8.9.1/8.8.3) id MAA21558 for hackers@freebsd.org; Thu, 11 Oct 2001 12:51:26 +0200 (MET DST) Date: Thu, 11 Oct 2001 12:51:26 +0200 From: Peter Wullinger To: hackers@freebsd.org Subject: VM Documentation Message-ID: <20011011125126.A21506@rfhpc8320.fh-regensburg.de> Reply-To: RivaW@gmx.de Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-rmd160; protocol="application/pgp-signature"; boundary="/04w6evG8XlLl3ft" Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Is there any -- besides doing the obviuos thing and reading the source -- documentation on the current implementation of the current VM subsystem? I'm just interested in the odds and ends of the current implementation (and probably for some open tasks, once I've dug into into ...). Peter --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (SunOS) Comment: For info see http://www.gnupg.org iD8DBQE7xXms2o6XoYZo6n4RAsKuAJ9sGI3jr7x+5PsQ49kfE8LeLBck6QCfRXkJ bCHJNuo9eRea38XRKdJZJcs= =jRYc -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 6: 2:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snark.rinet.ru (snark.rinet.ru [195.54.192.73]) by hub.freebsd.org (Postfix) with ESMTP id 8C2E137B406; Thu, 11 Oct 2001 06:02:31 -0700 (PDT) Received: (from yar@localhost) by snark.rinet.ru (8.11.6/8.11.6) id f9BD2R203342; Thu, 11 Oct 2001 17:02:27 +0400 (MSD) (envelope-from yar) Date: Thu, 11 Oct 2001 17:02:26 +0400 From: Yar Tikhiy To: hackers@freebsd.org, doc@freebsd.org Subject: utmp(5) manpage revised Message-ID: <20011011170226.A2162@snark.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi everybody, The current utmp(5) manpage language (not markup) has a number of drawbacks and errors: o There is no information for programmers on the actual structure of the files the page describes. o The C structure members aren't described. o Despites the page language, neither utmp nor lastlog grow continually or need rotation. o It describes in a wrong way how a user's logout is recorded to wtmp. o The login(3), logout(3) and logwtmp(3) functions aren't mentioned. Here's a patch addressing all the issues. Review it please. -- Yar Index: utmp.5 =================================================================== RCS file: /home/ncvs/src/share/man/man5/utmp.5,v retrieving revision 1.16 diff -u -r1.16 utmp.5 --- utmp.5 2001/10/11 11:29:37 1.16 +++ utmp.5 2001/10/11 12:59:35 @@ -57,12 +57,6 @@ the .Nm wtmp file. -.Pp -These files can grow rapidly on busy systems, so daily or weekly rotation -is recommended. -If any one of these files does not exist, it is not created. -They must be created manually and are maintained by -.Xr newsyslog 8 . .Bd -literal -offset indent #define _PATH_UTMP "/var/run/utmp" #define _PATH_WTMP "/var/log/wtmp" @@ -73,19 +67,39 @@ #define UT_HOSTSIZE 16 struct lastlog { - time_t ll_time; - char ll_line[UT_LINESIZE]; - char ll_host[UT_HOSTSIZE]; + time_t ll_time; /* When user logged in */ + char ll_line[UT_LINESIZE]; /* Terminal line name */ + char ll_host[UT_HOSTSIZE]; /* Host user came from */ }; struct utmp { - char ut_line[UT_LINESIZE]; - char ut_name[UT_NAMESIZE]; - char ut_host[UT_HOSTSIZE]; - time_t ut_time; + char ut_line[UT_LINESIZE]; /* Terminal line name */ + char ut_name[UT_NAMESIZE]; /* User's login name */ + char ut_host[UT_HOSTSIZE]; /* Host user came from */ + time_t ut_time; /* When user logged in */ }; .Ed .Pp +The +.Nm lastlog +file is a linear array of +.Fa lastlog +structures indexed by a user's +.Tn UID . +The +.Nm utmp +file is a linear array of +.Fa utmp +structures indexed by a terminal line number +(see +.Xr ttyslot 3 ) . +The +.Nm wtmp +file consists of +.Fa utmp +structures and is a binary log file, +that is, grows linearly at its end. +.Pp Each time a user logs in, the .Xr login 1 program looks up the user's @@ -132,10 +146,19 @@ and appends the user's .Fa utmp record. -The same +The user's subsequent logout from the terminal +line is marked by a special .Fa utmp -record, with an updated time stamp is later appended -to the file when the user logs out (see +record with +.Fa ut_line +set accordingly, +.Fa ut_time +updated, but +.Fa ut_name +and +.Fa ut_host +both empty +(see .Xr init 8 ) . The .Nm wtmp @@ -184,6 +207,29 @@ .Ql \&{ indicates the new time. .El +.Sh NOTES +The +.Nm wtmp +file can grow rapidly on busy systems, so daily or weekly rotation +is recommended. +It is maintained by +.Xr newsyslog 8 . +.Pp +If any one of these files does not exist, it is not created by +.Xr login 1 . +They must be created manually. +.Pp +The supplied +.Xr login 3 , +.Xr logout 3 , +and +.Xr logwtmp 3 +utility functions should be used to perform +the standard actions on the +.Nm utmp +and +.Nm wtmp +files. .Sh FILES .Bl -tag -width /var/log/lastlog -compact .It Pa /var/run/utmp @@ -204,6 +250,10 @@ .Xr login 1 , .Xr w 1 , .Xr who 1 , +.Xr login 3 , +.Xr logout 3 , +.Xr logwtmp 3 , +.Xr ttyslot 3 , .Xr ac 8 , .Xr init 8 .Sh HISTORY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 6:55:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from obfs.sitesnow.com (ns0.sitesnow.com [63.166.182.130]) by hub.freebsd.org (Postfix) with ESMTP id 6279737B403 for ; Thu, 11 Oct 2001 06:55:51 -0700 (PDT) Received: from gskouby by obfs.sitesnow.com with local (Exim 3.22 #5) id 15rgJN-000ItU-00; Thu, 11 Oct 2001 09:55:45 -0400 Date: Thu, 11 Oct 2001 09:55:45 -0400 From: Greg Skouby To: RivaW@gmx.de Cc: hackers@freebsd.org Subject: Re: VM Documentation Message-ID: <20011011095545.A72279@sitesnow.com> References: <20011011125126.A21506@rfhpc8320.fh-regensburg.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011011125126.A21506@rfhpc8320.fh-regensburg.de>; from Peter.Wullinger@stud.fh-regensburg.de on Thu, Oct 11, 2001 at 12:51:26PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Oct 11, 2001 at 12:51:26PM +0200, Peter Wullinger wrote: > > Is there any -- besides doing the obviuos thing and reading the source -- > documentation on the current implementation of the current VM subsystem? > For an interview that Matt recently did that had a tiny bit about the VM in it check out: http://www.osnews.com/story.php?news_id=153 And then check out: http://www.daemonnews.org/200001/freebsd_vm.html for a more in-depth paper. I found the second one particularly good reading. Not that it wasn't a good interview :) I liked the interview too! Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 8: 4:11 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from host4.rpi.wulimasters.net (host4.rpi.wulimasters.net [128.113.36.114]) by hub.freebsd.org (Postfix) with ESMTP id 2A49437B405 for ; Thu, 11 Oct 2001 08:04:08 -0700 (PDT) Received: (qmail 97256 invoked by uid 89); 11 Oct 2001 15:04:14 -0000 Message-ID: <20011011150414.97255.qmail@host4.rpi.wulimasters.net> From: "Alex Newman" To: freebsd-hackers@freebsd.org Subject: NATD+SSL Date: Thu, 11 Oct 2001 15:04:14 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >tlambert2@mindspring.com wrote: >ClickArray, Andes Networks, and several other vendors have >boxes which can do this. grouped >ulf@Alameda.net wrote: >Alteon has a solution for this like this: >Client.443 -> Loadbalancer -> SSL offloader (call iSD) -> Loadbalancer-> >Real Server. This is practically useful for half of what i am talking about implementing. If you were to incorperate NATD+SSL you would ssl enable any server on the localhost without things coming from localhost. > I have been thinking trying to put something simular for FreeBSD > together (with or without hardware crypto card for SSL). It would be > mostly a proof of concept for me. That is great, I would be glad to be brought up to date on what you have done so far, and help where i can. Also a couple of friends of mine have also expressed interest in helping me and then porting this to ipnat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 9:13:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id 7368437B408 for ; Thu, 11 Oct 2001 09:13:14 -0700 (PDT) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id f9BGD8D07093; Thu, 11 Oct 2001 11:13:08 -0500 (CDT) (envelope-from tinguely) Date: Thu, 11 Oct 2001 11:13:08 -0500 (CDT) From: mark tinguely Message-Id: <200110111613.f9BGD8D07093@web.cs.ndsu.nodak.edu> To: gskouby@sitesnow.com, RivaW@gmx.de Subject: Re: VM Documentation Cc: hackers@FreeBSD.ORG Reply-To: In-Reply-To: <20011011095545.A72279@sitesnow.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG on Sun, Aug 05, 2001 at 12:20:36PM, Nik Clayton points out: > http://www.daemonnews.org/200001/freebsd_vm.html That got pulled in to the documentation project a while ago, and can be found at http://www.freebsd.org/doc/en_US.ISO8859-1/articles/vm-design/index.html This makes it pretty easy for us (you) to keep it up to date as you change FreeBSD's VM system. . . (I hope Nik does not mind me rebroadcasting his -hacker reply). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 10:10:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ra.udcast.com (ANice-101-2-1-104.abo.wanadoo.fr [193.251.10.104]) by hub.freebsd.org (Postfix) with ESMTP id 93F0737B401 for ; Thu, 11 Oct 2001 10:10:40 -0700 (PDT) Received: (from pplc@localhost) by ra.udcast.com (8.11.0/8.11.0) id f9BHAcW24404; Thu, 11 Oct 2001 19:10:38 +0200 Date: Thu, 11 Oct 2001 19:10:38 +0200 Message-Id: <200110111710.f9BHAcW24404@ra.udcast.com> From: Patrick Cipiere To: freebsd-hackers@freebsd.org Subject: contigfree, free what? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG We are currently working with FreeBSD 4.3 and we found out that kldloading/kldunloading modules working with contigmalloc()/contigfree() like if_xl.ko produces a memory leak. This is due to the contigfree() function which seems to uncompletely release the memory ressource allocated in vm_page_array. When contigmalloc() steps in vm_page_array, it does not find back the pages previously released by contigfree() The loop vm/vm_page.c is this one: for (i = start; i < cnt.v_page_count; i++) { int pqtype; phys = VM_PAGE_TO_PHYS(&pga[i]); pqtype = pga[i].queue - pga[i].pc; if (pqtype == PQ_FREE It fails on the `pqtype == PQ_FREE' test and the previously allocated (and supposedly released by contigfree) pages can't be reallocated. Anyone has a patch? Thanx, Patrick. -- UDcast: Full IP over Broadcast Media Phone: (+33) (0)4 93 00 16 99 Mobile: (+33) (0)6 14 21 55 98 Fax: (+33) (0)4 93 00 16 61 http://www.UDcast.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 10:17:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 67F5B37B407 for ; Thu, 11 Oct 2001 10:17:50 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f9BHHfP28087; Thu, 11 Oct 2001 10:17:41 -0700 (PDT) (envelope-from dillon) Date: Thu, 11 Oct 2001 10:17:41 -0700 (PDT) From: Matt Dillon Message-Id: <200110111717.f9BHHfP28087@earth.backplane.com> To: Patrick Cipiere Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: contigfree, free what? References: <200110111710.f9BHAcW24404@ra.udcast.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :We are currently working with FreeBSD 4.3 and we found out that :kldloading/kldunloading modules working with contigmalloc()/contigfree() :like if_xl.ko produces a memory leak. : :This is due to the contigfree() function which seems to uncompletely release :the memory ressource allocated in vm_page_array. : :When contigmalloc() steps in vm_page_array, it does not find back :the pages previously released by contigfree() :The loop vm/vm_page.c is this one: : : for (i = start; i < cnt.v_page_count; i++) { : int pqtype; : phys = VM_PAGE_TO_PHYS(&pga[i]); : pqtype = pga[i].queue - pga[i].pc; : if (pqtype == PQ_FREE : : :It fails on the `pqtype == PQ_FREE' test :and the previously allocated (and supposedly released by contigfree) :pages can't be reallocated. : :Anyone has a patch? : :Thanx, :Patrick. This meshes with a bug report I received a couple of weeks ago, though you provide a great deal more information. I'll take a look at it (if others have a patch and want to jump in, then by all means post away!). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 11:37:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from jim.go2net.com (jim.go2net.com [64.50.65.22]) by hub.freebsd.org (Postfix) with SMTP id EDB3237B407 for ; Thu, 11 Oct 2001 11:37:21 -0700 (PDT) Received: (qmail 20187 invoked from network); 11 Oct 2001 18:38:50 -0000 Received: from unknown (HELO ketel.go2net.com) (10.200.10.75) by jim.go2net.com with SMTP; 11 Oct 2001 18:38:49 -0000 Received: (qmail 11594 invoked from network); 11 Oct 2001 18:37:15 -0000 Received: from hunches.go2net.com (HELO infospace.com) (@[10.225.33.32]) (envelope-sender ) by ketel.go2net.com (qmail-ldap-1.03) with SMTP for ; 11 Oct 2001 18:37:15 -0000 Message-ID: <3BC5E6DB.66D93BEB@infospace.com> Date: Thu, 11 Oct 2001 11:37:15 -0700 From: Yevgeniy Aleynikov Reply-To: eugene@infospace.com X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.17 i686) X-Accept-Language: ru, en MIME-Version: 1.0 To: Matt Dillon Cc: Kirk McKusick , Ian Dowse , peter@FreeBSD.ORG, ache@FreeBSD.ORG, Ken Pizzini , hackers@FreeBSD.ORG Subject: Re: bleh. Re: ufs_rename panic References: <200110030610.f936AbR11859@beastie.mckusick.com> <3BBE3F7A.98FBC714@infospace.com> <200110052320.f95NK6685878@earth.backplane.com> Content-Type: multipart/mixed; boundary="------------D6098574028207DE244366FA" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------D6098574028207DE244366FA Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Here's another stable panic (not very often but on different boxes too). -- Yevgeniy Aleynikov Infospace, Inc. SysAdmin, USE Work: (206)357-4594 --------------D6098574028207DE244366FA Content-Type: text/plain; charset=koi8-r; name="server1.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="server1.txt" SMP 2 cpus IdlePTD 3039232 initial pcb at 2666a0 panicstr: ffs_valloc: dup alloc panic messages: --- panic: ffs_valloc: dup alloc mp_lock = 01000001; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 syncing disks... 2 #0 dumpsys () at ../../kern/kern_shutdown.c:473 473 if (dumping++) { (kgdb) bt #0 dumpsys () at ../../kern/kern_shutdown.c:473 #1 0xc015e9df in boot (howto=256) at ../../kern/kern_shutdown.c:313 #2 0xc015ede0 in poweroff_wait (junk=0xc0232e01, howto=-1071436320) at ../../kern/kern_shutdown.c:581 #3 0xc01b6600 in ffs_valloc (pvp=0xdf902600, mode=33188, cred=0xc5b83380, vpp=0xdf541c9c) at ../../ufs/ffs/ffs_alloc.c:609 #4 0xc01c32ef in ufs_makeinode (mode=33188, dvp=0xdf902600, vpp=0xdf541edc, cnp=0xdf541ef0) at ../../ufs/ufs/ufs_vnops.c:2097 #5 0xc01c0978 in ufs_create (ap=0xdf541df8) at ../../ufs/ufs/ufs_vnops.c:194 #6 0xc01c363d in ufs_vnoperate (ap=0xdf541df8) at ../../ufs/ufs/ufs_vnops.c:2382 #7 0xc0192c88 in vn_open (ndp=0xdf541ec4, fmode=1538, cmode=420) at vnode_if.h:106 #8 0xc018ee6c in open (p=0xdf4c9a00, uap=0xdf541f80) at ../../kern/vfs_syscalls.c:1077 #9 0xc0205011 in syscall2 (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 1, tf_esi = 0, tf_ebp = -1077939600, tf_isp = -548134956, tf_ebx = -1077939604, tf_edx = 1537, tf_ecx = 137102023, tf_eax = 5, tf_trapno = 7, tf_err = 2, tf_eip = 674553728, tf_cs = 31, tf_eflags = 514, tf_esp = -1077939656, tf_ss = 47}) at ../../i386/i386/trap.c:1155 #10 0xc01f291b in Xint0x80_syscall () ----------------------------------------------------------------------- fs->fs_contigdirs[cg]--; } ino = (ino_t)ffs_hashalloc(pip, cg, (long)ipref, mode, (allocfcn_t *)ffs_nodealloccg); if (ino == 0) goto noinodes; error = VFS_VGET(pvp->v_mount, ino, vpp); if (error) { UFS_VFREE(pvp, ino, mode); return (error); } ip = VTOI(*vpp); if (ip->i_mode) { printf("mode = 0%o, inum = %lu, fs = %s\n", ip->i_mode, (u_long)ip->i_number, fs->fs_fsmnt); panic("ffs_valloc: dup alloc"); } ------------------------------------------------------------------------ #3 0xc01b6600 in ffs_valloc (pvp=0xdf902600, mode=33188, cred=0xc5b83380, vpp=0xdf541c9c) at ../../ufs/ffs/ffs_alloc.c:609 (kgdb) print *pvp $6 = {v_flag = 0, v_usecount = 1, v_writecount = 0, v_holdcnt = 2, v_id = 69744400, v_mount = 0xc4174e00, v_op = 0xc4078700, v_freelist = { tqe_next = 0x0, tqe_prev = 0xe01f999c}, v_mntvnodes = { le_next = 0xdf949f00, le_prev = 0xe02ef924}, v_cleanblkhd = { tqh_first = 0xce8697ac, tqh_last = 0xce8697b4}, v_dirtyblkhd = { tqh_first = 0x0, tqh_last = 0xdf902634}, v_synclist = { le_next = 0xe034c7c0, le_prev = 0xe04904bc}, v_numoutput = 0, v_type = VDIR, v_un = {vu_mountedhere = 0x0, vu_socket = 0x0, vu_spec = { vu_specinfo = 0x0, vu_specnext = {sle_next = 0x0}}, vu_fifoinfo = 0x0}, v_lease = 0x0, v_lastw = 0, v_cstart = 0, v_lasta = 0, v_clen = 0, v_object = 0x0, v_interlock = {lock_data = 0}, v_vnlock = 0xc448d400, v_tag = VT_UFS, v_data = 0xc448d400, v_cache_src = {lh_first = 0xc5630f40}, v_cache_dst = {tqh_first = 0xc5dcfb80, tqh_last = 0xc5dcfb90}, v_dd = 0xdfac9b00, v_ddid = 69744310, v_pollinfo = {vpi_lock = { lock_data = 0}, vpi_selinfo = {si_pid = 0, si_note = {slh_first = 0x0}, si_flags = 0}, vpi_events = 0, vpi_revents = 0}, v_vxproc = 0x0} (kgdb) print **vpp $2 = {v_flag = 0, v_usecount = 1, v_writecount = 0, v_holdcnt = 0, v_id = 69818641, v_mount = 0xc4174e00, v_op = 0xc4078700, v_freelist = { tqe_next = 0xdf941dc0, tqe_prev = 0xc02670d0}, v_mntvnodes = { le_next = 0xdfd79a80, le_prev = 0xc4174e18}, v_cleanblkhd = { tqh_first = 0x0, tqh_last = 0xdfa89e2c}, v_dirtyblkhd = {tqh_first = 0x0, tqh_last = 0xdfa89e34}, v_synclist = {le_next = 0x0, le_prev = 0xc407b0cc}, v_numoutput = 0, v_type = VDIR, v_un = { vu_mountedhere = 0x0, vu_socket = 0x0, vu_spec = {vu_specinfo = 0x0, vu_specnext = {sle_next = 0x0}}, vu_fifoinfo = 0x0}, v_lease = 0x0, v_lastw = 0, v_cstart = 0, v_lasta = 0, v_clen = 0, v_object = 0x0, v_interlock = {lock_data = 0}, v_vnlock = 0xc55f1200, v_tag = VT_UFS, v_data = 0xc55f1200, v_cache_src = {lh_first = 0x0}, v_cache_dst = { tqh_first = 0x0, tqh_last = 0xdfa89e80}, v_dd = 0xdfa89e00, v_ddid = 0, v_pollinfo = {vpi_lock = {lock_data = 0}, vpi_selinfo = {si_pid = 0, si_note = {slh_first = 0x0}, si_flags = 0}, vpi_events = 0, vpi_revents = 0}, v_vxproc = 0x0} (kgdb) print mode $3 = 33188 print cred $4 = (struct ucred *) 0x0 ---------------------------------------------------------------- #4 0xc01c32ef in ufs_makeinode (mode=33188, dvp=0xdf902600, vpp=0xdf541edc, cnp=0xdf541ef0) at ../../ufs/ufs/ufs_vnops.c:2097 (kgdb) print *cnp $7 = {cn_nameiop = 1, cn_flags = 52300, cn_proc = 0xdf4c9a00, cn_cred = 0xc5b83380, cn_pnbuf = 0xdf6c9c00 "/data1/hypermart.net/mv/en/img.titles/_vti_cnf/.en_servicos.gif.tmp", cn_nameptr = 0xdf6c9c2f ".en_servicos.gif.tmp", cn_namelen = 20, cn_consume = 0} (kgdb) print *dvp $8 = {v_flag = 0, v_usecount = 1, v_writecount = 0, v_holdcnt = 2, v_id = 69744400, v_mount = 0xc4174e00, v_op = 0xc4078700, v_freelist = { tqe_next = 0x0, tqe_prev = 0xe01f999c}, v_mntvnodes = { le_next = 0xdf949f00, le_prev = 0xe02ef924}, v_cleanblkhd = { tqh_first = 0xce8697ac, tqh_last = 0xce8697b4}, v_dirtyblkhd = { tqh_first = 0x0, tqh_last = 0xdf902634}, v_synclist = { le_next = 0xe034c7c0, le_prev = 0xe04904bc}, v_numoutput = 0, v_type = VDIR, v_un = {vu_mountedhere = 0x0, vu_socket = 0x0, vu_spec = { vu_specinfo = 0x0, vu_specnext = {sle_next = 0x0}}, vu_fifoinfo = 0x0}, v_lease = 0x0, v_lastw = 0, v_cstart = 0, v_lasta = 0, v_clen = 0, v_object = 0x0, v_interlock = {lock_data = 0}, v_vnlock = 0xc448d400, v_tag = VT_UFS, v_data = 0xc448d400, v_cache_src = {lh_first = 0xc5630f40}, v_cache_dst = {tqh_first = 0xc5dcfb80, tqh_last = 0xc5dcfb90}, v_dd = 0xdfac9b00, v_ddid = 69744310, v_pollinfo = {vpi_lock = { lock_data = 0}, vpi_selinfo = {si_pid = 0, si_note = {slh_first = 0x0}, si_flags = 0}, vpi_events = 0, vpi_revents = 0}, v_vxproc = 0x0} (kgdb) print *vpp $9 = (struct vnode *) 0x0 -------------------------------------------------- #5 0xc01c0978 in ufs_create (ap=0xdf541df8) at ../../ufs/ufs/ufs_vnops.c:194 (kgdb) print *ap $11 = {a_desc = 0xc0246b40, a_dvp = 0xdf902600, a_vpp = 0xdf541edc, a_cnp = 0xdf541ef0, a_vap = 0xdf541e0c} (kgdb) print *ap->a_desc $13 = {vdesc_offset = 11, vdesc_name = 0xc0218151 "vop_create", vdesc_flags = 0, vdesc_vp_offsets = 0xc0246b24, vdesc_vpp_offset = 8, vdesc_cred_offset = -1, vdesc_proc_offset = -1, vdesc_componentname_offset = 12, vdesc_transports = 0x0} (kgdb) print *ap->a_vpp $21 = (struct vnode *) 0x0 (kgdb) print *ap->a_dvp $22 = {v_flag = 0, v_usecount = 1, v_writecount = 0, v_holdcnt = 2, v_id = 69744400, v_mount = 0xc4174e00, v_op = 0xc4078700, v_freelist = { tqe_next = 0x0, tqe_prev = 0xe01f999c}, v_mntvnodes = { le_next = 0xdf949f00, le_prev = 0xe02ef924}, v_cleanblkhd = { tqh_first = 0xce8697ac, tqh_last = 0xce8697b4}, v_dirtyblkhd = { tqh_first = 0x0, tqh_last = 0xdf902634}, v_synclist = { le_next = 0xe034c7c0, le_prev = 0xe04904bc}, v_numoutput = 0, v_type = VDIR, v_un = {vu_mountedhere = 0x0, vu_socket = 0x0, vu_spec = { vu_specinfo = 0x0, vu_specnext = {sle_next = 0x0}}, vu_fifoinfo = 0x0}, v_lease = 0x0, v_lastw = 0, v_cstart = 0, v_lasta = 0, v_clen = 0, v_object = 0x0, v_interlock = {lock_data = 0}, v_vnlock = 0xc448d400, v_tag = VT_UFS, v_data = 0xc448d400, v_cache_src = {lh_first = 0xc5630f40}, v_cache_dst = {tqh_first = 0xc5dcfb80, tqh_last = 0xc5dcfb90}, v_dd = 0xdfac9b00, v_ddid = 69744310, v_pollinfo = {vpi_lock = { lock_data = 0}, vpi_selinfo = {si_pid = 0, si_note = {slh_first = 0x0}, si_flags = 0}, vpi_events = 0, vpi_revents = 0}, v_vxproc = 0x0} ------------------------------------------------------ #6 0xc01c363d in ufs_vnoperate (ap=0xdf541df8) at ../../ufs/ufs/ufs_vnops.c:2382 (kgdb) print ap $26 = (struct vop_generic_args *) 0x0 ------------------------------------------------------ #7 0xc0192c88 in vn_open (ndp=0xdf541ec4, fmode=1538, cmode=420) at vnode_if.h:106 (kgdb) print *ndp $27 = {ni_dirp = 0x848d28ccannot read proc at 0 ------------------------------------------------------ #8 0xc018ee6c in open (p=0xdf4c9a00, uap=0xdf541f80) at ../../kern/vfs_syscalls.c:1077 (kgdb) print *p $31 = {p_procq = {tqe_next = 0x0, tqe_prev = 0xc0277b40}, p_list = { le_next = 0xdf5788a0, le_prev = 0xc0277ad8}, p_cred = 0xc43c2500, p_fd = 0xc4605400, p_stats = 0xdf540cd0, p_limit = 0xc4879a00, p_upages_obj = 0xdf5338a0, p_procsig = 0xc5447ac0, p_flag = 16389, p_stat = 2 '\002', p_pad1 = "\000\000", p_pid = 41233, p_hash = { le_next = 0x0, le_prev = 0xc405d444}, p_pglist = {le_next = 0xdf576340, le_prev = 0xe051b0bc}, p_pptr = 0xe051b080, p_sibling = {le_next = 0x0, le_prev = 0xe051b0d0}, p_children = {lh_first = 0x0}, p_ithandle = { callout = 0xce7ec0a8}, p_oppid = 0, p_dupfd = -4, p_vmspace = 0xe053d280, p_estcpu = 93, p_cpticks = 85, p_pctcpu = 45, p_wchan = 0x0, p_wmesg = 0xc0229f89 "biord", p_swtime = 1, p_slptime = 0, p_realtimer = { it_interval = {tv_sec = 0, tv_usec = 0}, it_value = {tv_sec = 1796341, tv_usec = 491839}}, p_runtime = 90127, p_uu = 0, p_su = 0, p_iu = 0, p_uticks = 9, p_sticks = 134, p_iticks = 0, p_traceflag = 0, p_tracep = 0x0, p_siglist = {__bits = {0, 0, 0, 0}}, p_textvp = 0xe0094fc0, p_lock = 0 '\000', p_oncpu = 1 '\001', p_lastcpu = 0 '\000', p_rqindex = 4 '\004', p_locks = -158, p_simple_locks = 0, p_stops = 0, p_stype = 0, p_step = 0 '\000', p_pfsflags = 0 '\000', p_pad3 = "\000", p_retval = {0, 1537}, p_sigiolst = {slh_first = 0x0}, p_sigparent = 20, p_oldsigmask = {__bits = {0, 0, 0, 0}}, p_sig = 0, p_code = 0, p_klist = { slh_first = 0x0}, p_sigmask = {__bits = {0, 0, 0, 0}}, p_sigstk = { ss_sp = 0x0, ss_size = 0, ss_flags = 4}, p_priority = 16 '\020', p_usrpri = 61 '=', p_nice = 0 '\000', p_comm = "author.exe\000\000\000\000\000\000", p_pgrp = 0xc41a3e40, p_sysent = 0xc024c3c0, p_rtprio = {type = 1, prio = 0}, p_prison = 0x0, p_args = 0xc5fff080, p_addr = 0xdf540000, p_md = {md_regs = 0xdf541fa8}, p_xstat = 0, p_acflag = 2, p_ru = 0x0, p_nthreads = 0, p_aioinfo = 0x0, p_wakeup = 0, p_peers = 0x0, p_leader = 0xdf4c9a00, p_asleep = { as_priority = 0, as_timo = 0}, p_emuldata = 0x0} (kgdb) print *uap $32 = {path = 0x848d28ccannot read proc at 0 ----------------------------------------------------------------- --------------D6098574028207DE244366FA-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 12:50: 0 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-65-31-203-60.mmcable.com [65.31.203.60]) by hub.freebsd.org (Postfix) with SMTP id 315CE37B407 for ; Thu, 11 Oct 2001 12:49:53 -0700 (PDT) Received: (qmail 78327 invoked by uid 100); 11 Oct 2001 19:49:52 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15301.63455.964624.626361@guru.mired.org> Date: Thu, 11 Oct 2001 14:49:51 -0500 To: hackers@freebsd.org Cc: chuckr@FreeBSD.org, chris@freebsd.org Subject: My contributions to the close a PR campaign X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In order to help get the # of open PR's down, I'm going to take the time to update the status of my open PR. Some should just be closed, and I hope that others get some action taken. I've tried to sort them in order of increasing work for the committer. http://www.mired.org/home/mwm/ Q: How do you make the gods laugh? A: Tell them your plans. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 14:10:10 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from holly.dyndns.org (adsl-208-191-149-224.dsl.hstntx.swbell.net [208.191.149.224]) by hub.freebsd.org (Postfix) with ESMTP id 911A237B401 for ; Thu, 11 Oct 2001 14:10:05 -0700 (PDT) Received: (from chris@localhost) by holly.dyndns.org (8.11.6/8.9.3) id f9BLAWs18747; Thu, 11 Oct 2001 16:10:32 -0500 (CDT) (envelope-from chris) Date: Thu, 11 Oct 2001 16:10:31 -0500 From: Chris Costello To: Mike Meyer Cc: hackers@FreeBSD.ORG Subject: Re: My contributions to the close a PR campaign Message-ID: <20011011161030.E696@holly.calldei.com> Reply-To: chris@FreeBSD.ORG References: <15301.63455.964624.626361@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15301.63455.964624.626361@guru.mired.org>; from mwm@mired.org on Thu, Oct 11, 2001 at 02:49:51PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thursday, October 11, 2001, Mike Meyer wrote: > kern/25266 chris fdesc file system in -STABLE locks up during nightly builds > > Fixed in -current, awaiting decision as to whether or not it should be > MFC'ed. If it's not going to be MFC'ed, it should be > closed. Hopefully, fdesc will be taken out of stable at about that > time as well. Thank you for raising this report; I've just sent an email to -arch on this subject and plan on merging the code more or less as it is in -CURRENT, lest the issue of people being astonished by the somewhat different layout be too great (which I doubt, as it seems very few people actually use it.) -- +-------------------+-------------------------+ | Chris Costello | Aibohphobia: | | chris@FreeBSD.org | The fear of palindromes | +-------------------+-------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 14:17:29 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from host4.rpi.wulimasters.net (host4.rpi.wulimasters.net [128.113.36.114]) by hub.freebsd.org (Postfix) with ESMTP id EB40137B405 for ; Thu, 11 Oct 2001 14:17:25 -0700 (PDT) Received: (qmail 99017 invoked by uid 89); 11 Oct 2001 21:17:32 -0000 Message-ID: <20011011211732.99016.qmail@host4.rpi.wulimasters.net> From: "Alex Newman" To: freebsd-hackers@freebsd.org Subject: NATD+SSL maybe should be a new subject Date: Thu, 11 Oct 2001 21:17:32 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG After discussing it more i was wondering what the plausibility of instead of implementing NATD+SSL of implementing that works like the natd does with divert. Example: 1) ipfw could send to 8669/divert which has ssld listening 2) ssld could act very much the same way natd would only all it would do is negotiate the ssl connection and then decrypt and encrypt as need be. 3) pass to natd on 8868/divert or pass back to ipfw Any ideas? Alex Newman www.wulimasters.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 14:34: 2 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail11.speakeasy.net (mail11.speakeasy.net [216.254.0.211]) by hub.freebsd.org (Postfix) with ESMTP id D073337B407 for ; Thu, 11 Oct 2001 14:33:56 -0700 (PDT) Received: (qmail 72127 invoked from network); 11 Oct 2001 21:33:56 -0000 Received: from unknown (HELO laptop.baldwin.cx) ([64.81.54.73]) (envelope-sender ) by mail11.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 11 Oct 2001 21:33:56 -0000 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <15301.63455.964624.626361@guru.mired.org> Date: Thu, 11 Oct 2001 14:33:19 -0700 (PDT) From: John Baldwin To: Mike Meyer Subject: RE: My contributions to the close a PR campaign Cc: chris@freebsd.org, chuckr@FreeBSD.org, hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On 11-Oct-01 Mike Meyer wrote: > In order to help get the # of open PR's down, I'm going to take the > time to update the status of my open PR. Some should just be closed, > and I hope that others get some action taken. I've tried to sort them > in order of increasing work for the committer. > > > > ports/23410 obrien [PATCH] FreeBSD throws away information on failed #! > execs; this > ports/19457 vanilla The gimp port has /usr/local/bin hardwired in as the > path to lib > > Both fixed, and can be closed. 23410 is already closed, I just closed 19457. > docs/27843 alex [PATCH] make.conf WITH_* variables aren't documented. > > Suspended pending further work by alex. Hmm, how is ports.conf coming again? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 15: 8:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from InterJet.elischer.org (c421509-a.pinol1.sfba.home.com [24.7.86.9]) by hub.freebsd.org (Postfix) with ESMTP id 872D037B407; Thu, 11 Oct 2001 15:08:28 -0700 (PDT) Received: from localhost (localhost.elischer.org [127.0.0.1]) by InterJet.elischer.org (8.9.1a/8.9.1) with ESMTP id QAA38144; Thu, 11 Oct 2001 16:18:43 -0700 (PDT) Date: Thu, 11 Oct 2001 16:18:41 -0700 (PDT) From: Julian Elischer To: hackers@freebsd.org Cc: developers@freebsd.org Subject: Patch to allow 4.2 driver .o to run on 4.4 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry about the crosspost but I estimate that this reaches those who need to see this.. There was a change in the 4.x kernel.h on June 15 that broke backwards compatibility for binary distributed driver files (distributed as .o files) It was an MFC of a patch by peter.. but we didn't understand the ramifications in 4.x. my fix (a reversion in part) is as follows: Index: kernel.h =================================================================== RCS file: /repos/cvs/mod/freebsd/src/sys/sys/kernel.h,v retrieving revision 1.63.2.5 diff -u -r1.63.2.5 kernel.h --- kernel.h 2001/07/26 23:27:53 1.63.2.5 +++ kernel.h 2001/10/11 21:30:03 @@ -113,13 +113,13 @@ SI_SUB_VM = 0x1000000, /* virtual memory system init*/ SI_SUB_KMEM = 0x1800000, /* kernel memory*/ SI_SUB_KVM_RSRC = 0x1A00000, /* kvm operational limits*/ - SI_SUB_CPU = 0x2000000, /* CPU resource(s)*/ - SI_SUB_KLD = 0x2100000, /* KLD and module setup */ - SI_SUB_INTRINSIC = 0x2200000, /* proc 0*/ - SI_SUB_VM_CONF = 0x2300000, /* config VM, set limits*/ - SI_SUB_RUN_QUEUE = 0x2400000, /* the run queue*/ - SI_SUB_CREATE_INIT = 0x2500000, /* create the init process */ - SI_SUB_DRIVERS = 0x3100000, /* Let Drivers initialize */ + SI_SUB_CPU = 0x1e00000, /* CPU resource(s)*/ + SI_SUB_KLD = 0x1f00000, /* KLD and module setup */ + SI_SUB_INTRINSIC = 0x2000000, /* proc 0*/ + SI_SUB_VM_CONF = 0x2100000, /* config VM, set limits*/ + SI_SUB_RUN_QUEUE = 0x2200000, /* the run queue*/ + SI_SUB_CREATE_INIT = 0x2300000, /* create the init process */ + SI_SUB_DRIVERS = 0x2400000, /* Let Drivers initialize */ SI_SUB_CONFIGURE = 0x3800000, /* Configure devices */ SI_SUB_VFS = 0x4000000, /* virtual file system*/ SI_SUB_CLOCKS = 0x4800000, /* real time and stat clocks*/ The result of this was that old .o drivers are initialise at sequence 0x2400000 but the device framework is not initialised until 0x3100000. my patch shifts all the numbers back to below that that binary ,o files would be compiled with, thus ensuring that the world is ready for them when they initialise. The hardest hit would be any drivers using the PCI compatibility shims which core-dump on a null reference because the pci compatibility shim devclass pointer is not yet initialised.. I'd like to check this in to 4.4++ as itwill allow anyone else with binary .o drivers (No idea if there are any others) to use their dirvers without having to go back to their suppliers and pay "lots-o-cash" to get them to recompile it. (If they still have the source). Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 15:45:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.noos.fr (racine.noos.net [212.198.2.71]) by hub.freebsd.org (Postfix) with ESMTP id 0927637B406 for ; Thu, 11 Oct 2001 15:45:14 -0700 (PDT) Received: (qmail 4289170 invoked by uid 0); 11 Oct 2001 22:45:12 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.231.187]) (envelope-sender ) by 212.198.2.71 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 11 Oct 2001 22:45:12 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id f9BMjAS66764; Fri, 12 Oct 2001 00:45:10 +0200 (CEST) (envelope-from root) Message-Id: <200110112245.f9BMjAS66764@gits.dyndns.org> Subject: Re: My contributions to the close a PR campaign In-Reply-To: <15301.63455.964624.626361@guru.mired.org> To: Mike Meyer Date: Fri, 12 Oct 2001 00:45:10 +0200 (CEST) Cc: hackers@freebsd.org, chuckr@freebsd.org, chris@freebsd.org Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL94c (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Meyer wrote: [snip] > conf/21722 The mixer settings are lost on system reboot. > > This should probably be closed due to the work being done on the > NetBSD rc system. The same functionality can be provided as a port, > which is probably better anyway. I'll do that if this one gets closed. much better is to keep it, at least to remember that something like that have to be done. Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 16:48:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-65-31-203-60.mmcable.com [65.31.203.60]) by hub.freebsd.org (Postfix) with SMTP id 033B037B40B for ; Thu, 11 Oct 2001 16:48:54 -0700 (PDT) Received: (qmail 83310 invoked by uid 100); 11 Oct 2001 23:48:48 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15302.12256.96805.125719@guru.mired.org> Date: Thu, 11 Oct 2001 18:48:48 -0500 To: clefevre@citeweb.net Cc: Mike Meyer , hackers@freebsd.org, chuckr@freebsd.org, chris@freebsd.org Subject: Re: My contributions to the close a PR campaign In-Reply-To: <200110112245.f9BMjAS66764@gits.dyndns.org> References: <15301.63455.964624.626361@guru.mired.org> <200110112245.f9BMjAS66764@gits.dyndns.org> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Cyrille Lefevre types: > Mike Meyer wrote: > [snip] > > conf/21722 The mixer settings are lost on system reboot. > > > > This should probably be closed due to the work being done on the > > NetBSD rc system. The same functionality can be provided as a port, > > which is probably better anyway. I'll do that if this one gets closed. > > much better is to keep it, at least to remember that something like > that have to be done. I'm not convinced it needs to be done. It's not really a critical feature, and very few people seem to miss it. It makes a lot more sense as a port that the few people who miss it can install. I've already got the script; I just want to make sure I don't do the work of turning it into a port only to have this thing committed. The script is so trivial I use it as an example of how to do rc.d scripts on -questions. /dev/null ;; stop) /usr/sbin/mixer -s > $MIXERSTATE ;; *) echo "usage: `basename $0` {start|stop}" >&2 exit 64 ;; esac -- Mike Meyer http://www.mired.org/home/mwm/ Q: How do you make the gods laugh? A: Tell them your plans. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 16:49:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wombat.bytecraft.au.com (wombat.bytecraft.au.com [203.39.118.3]) by hub.freebsd.org (Postfix) with ESMTP id 0E9BD37B401; Thu, 11 Oct 2001 16:49:28 -0700 (PDT) Received: from lt99101401.bytecraft.au.com (unknown [203.39.118.42]) by wombat.bytecraft.au.com (Postfix) with SMTP id 7E6003F0C; Fri, 12 Oct 2001 09:49:25 +1000 (EST) Message-ID: <01a201c152af$5b09ae00$2a7627cb@bytecraft.au.com> Reply-To: "MurrayTaylor" From: "MurrayTaylor" To: , Subject: Imagestream WanIC-520 interface cards Date: Fri, 12 Oct 2001 09:49:23 +1000 Organization: Bytecraft Systems MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG As the WanIC-405 is being phased out (according to my supplier down under here in OZ), has any development / testing been done on the apparent replacement, the WanIC-521 (522, 524 ... ) range I am especially interested in its compatibility with its predecessor which I am using very successfully for frame relay under Netgraph. I'm trying to get compatability info from the supplier here, but we are a long way down the food chain ;-( Tia Murray Taylor Bytecraft Systems Pty Ltd murraytaylor@bytecraftsystems.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 17:13:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web14702.mail.yahoo.com (web14702.mail.yahoo.com [216.136.224.119]) by hub.freebsd.org (Postfix) with SMTP id BF33F37B401 for ; Thu, 11 Oct 2001 17:13:47 -0700 (PDT) Message-ID: <20011012001347.70430.qmail@web14702.mail.yahoo.com> Received: from [24.43.32.161] by web14702.mail.yahoo.com via HTTP; Thu, 11 Oct 2001 17:13:47 PDT Date: Thu, 11 Oct 2001 17:13:47 -0700 (PDT) From: Ron Chen Subject: Fwd: [GE dev] Re: SGE port to Mac OS X To: Beowulf , freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG For people who want to build a cluster of BSD/MacOS X, we now have a port of Grid Engine available. It is available as opensource at: http://gridengine.sunsource.net -Ron --- Fritz Ferstl wrote: > Reply-to: dev@gridengine.sunsource.net > Date: Thu, 11 Oct 2001 14:46:33 +0200 (MEST) > From: Fritz Ferstl > To: William Van Etten > > CC: Grid Engine dev alias > , zelman@apple.com, > annc@apple.com, proclus@iname.com, > kurt@apple.com > Subject: [GE dev] Re: SGE port to Mac OS X > > Thanks Bill, > > we'll try to incorporate your changes. I hope we can > contact you in case of > questions. Would you be willing to perform a build > and run test once we > have the sources updated? > > Thanks, > > Fritz > > > On Tue, 9 Oct 2001, William Van Etten wrote: > > > I've attached a recursive diff of the Sun > gridengine distribution > > against the new and modified source. > > I've attached a tarball of the new and modified > source for patching the > > gridengine/source directory. > > Finally, I've attached a README.Darwin that > describes how to patch and > > build SGE on Mac OS X. > > > > I refer to a URL > (http://thevanettens.com/source_patch.tgz) for > > downloading the patch files, but this is an iMac > over cable modem used > > heavily by children under the age of ten. Not a > very reliable place to > > serve the patch from. Will try to find a better > place to serve it. > > > > Bill > > > > On Monday, October 1, 2001, at 04:23 AM, Fritz > Ferstl wrote: > > > > > Sending both pieces, the tar-balls and the diffs > to > > > dev@gridengine.sunsource.net will do. You can > also put the stuff on some > > > ftp-server you might have access to and send > just the URL for us to get > > > it. > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > dev-unsubscribe@gridengine.sunsource.net > For additional commands, e-mail: > dev-help@gridengine.sunsource.net > __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 17:44:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.johncharlesdesigns.com (w098.z064000241.lax-ca.dsl.cnc.net [64.0.241.98]) by hub.freebsd.org (Postfix) with ESMTP id 7BBF137B408 for ; Thu, 11 Oct 2001 17:44:24 -0700 (PDT) Received: from localhost (manele-femei-si-bautura.org [64.225.124.232]) by mail.johncharlesdesigns.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id 4VA30ZVA; Thu, 11 Oct 2001 17:39:10 -0700 To: freebsd-hackers@FreeBSD.org From: friends@openxxx.net X-Mailer: Perl+Mail::Sender 0.7.08 by Jan Krynicky Subject: Hello, your friend recommended openxxx to you Message-Id: <20011012004424.7BBF137B408@hub.freebsd.org> Date: Thu, 11 Oct 2001 17:44:24 -0700 (PDT) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG You have been invited to check out this adult site by one of your friends who visited us. click here , our URL is: http://www.openxxx.net/ enjoy, OpenXXX TEAM 2001 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 18:39:51 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by hub.freebsd.org (Postfix) with ESMTP id C741337B40A; Thu, 11 Oct 2001 18:39:44 -0700 (PDT) Received: from vicor-nb.com (dhcp122.vicor-nb.com [208.206.78.122]) by mail.vicor-nb.com (Postfix) with ESMTP id 4AE631B219; Thu, 11 Oct 2001 18:39:42 -0700 (PDT) Message-ID: <3BC649DE.36CA5121@vicor-nb.com> Date: Thu, 11 Oct 2001 18:39:42 -0700 From: Julian Elischer Organization: VICOR X-Mailer: Mozilla 4.76 [en] (X11; U; FreeBSD 4.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: cg@freebsd.org Cc: hackers@freebsd.org Subject: Sound driver non backward compatible? (voice recog) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The voice recognition software we use has suddenly stopped working when we moved from 4.1.1 to 4.4 Lookig at the ktraces (it's proprietary code so we can't look at the code) we see the following differences: in 4.1.1 we see 5015 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 5015 hapitest RET ioctl 0 5015 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 5015 hapitest RET ioctl 0 5015 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 5015 hapitest RET ioctl 0 5015 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 5015 hapitest RET ioctl 0 5015 hapitest CALL nanosleep(0xbfbff9c8,0) 5015 hapitest RET nanosleep 0 5015 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 5015 hapitest RET ioctl 0 5015 hapitest CALL read(0x5,0x84ec826,0x800) 5015 hapitest GIO fd 5 read 2048 bytes "\b\0 \0\b\0\a\0\a\0\^F\0\^F\0\b\0\a\0\a\0\b\0\^F\0\^F\0\^F\0\^E\0\^F\0\a\0\ \b\0\^F\0\^E\0\a\0\^E\0\^E\0\^F\0\a\0\^E\0\^D\0\^E\0\^E\0\^E\0\^A\0\^C\ \0\^F\0\^C\0\^E\0\^F\0\^D\0\^F\0\^D\0\^A\0\^C\0\^B\0\^A\0\^B\0\^D\0\^E\ \0\^D\0\^D\0\^E\0\^C\0\^C\0\^D\0\^C\0\^D\0\^D\0\^D\0\^C\0\^E\0\^D\0\^E\ \0\^E\0\^B\0\0\0\^C\0\^B\0\^A\0\0\0\^B\0\^C\0\^A\0\^A\0\^B\0\^B\0\^B\0\ \^C\0\^B\0\^D\0\^C\0\0\0\0\0\^A\0\^B\0\0\0\M-}\M^?\M^?\M^?\^A\0\M^?\ \M^?\0\0\^B\0\^A\0\0\0\M^?\M^?\^A\0\^A\0\^A\0\0\0\^A\0\^A\0\^A\0\0\0\ \^A\0\^C\0\0\0\M^?\M^?\^A\0\0\0\M^?\M^?\M-}\M^?\M-~\M^?\0\0\0\0\0\0\^A\ \0\0\0\M-~\M^?\M-~\M^?\M-~\M^?\M-~\M^?\M^?\M^?\M^?\M^?\M-|\M^?\M-}\M^?\ \M-~\M^?\M-~\M^?\M-~\M^?\M-}\M^?\M-~\M^?\M^?\M^?\M-}\M^?\M-}\M^?\M-~\ \M^?\M-|\M^?\M-|\M^?\M-|\M^?\M-{\M^?\M-|\M^?\M-}\M^?\M-|\M^?\M-|\M^? (and 2048 bytes of sound data read...) in 4.4 we see: 3121 hapitest RET read 226/0xe2 3121 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 3121 hapitest RET ioctl 0 3121 hapitest CALL read(0x5,0x8563dea,0x5e) 3121 hapitest GIO fd 5 read 94 bytes "\^C\0\M-}\M^?\M-}\M^?\^E\0 \0\v\0\a\0\^E\0\^B\0\M-}\M^?\0\0\^D\0\^C\0\^E\0\a\0\^E\0\^E\0\M-{\M^?\ \M-~\M^?\^F\0 \0\b\0\M^?\M^?\M-|\M^?\M-|\M^?\M-}\M^?\0\0\f\0\v\0 \0\^D\0\^B\0\ \^B\0\0\0\^E\0\^E\0\^E\0\^E\0\M^?\M^?\0\0\^F\0\^C\0\^D\0\a\0\^E\0\^E\0\ \^B\0" 3121 hapitest RET read 94/0x5e 3121 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 3121 hapitest RET ioctl 0 3121 hapitest CALL read(0x5,0x8563e48,0) 3121 hapitest GIO fd 5 read 0 bytes "" 3121 hapitest RET read 0 3121 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 3121 hapitest RET ioctl 0 3121 hapitest CALL read(0x5,0x8563e48,0x22) 3121 hapitest GIO fd 5 read 34 bytes "\M-~\M^?\^B\0\^C\0\^B\0\M-~\M^?\M-}\M^?\^E\0\^F\0\^D\0\b\0 \0\^D\ \0\M-}\M^?\M-~\M^?\^C\0\M-|\M^?\M-~\M^?" 3121 hapitest RET read 34/0x22 3121 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 3121 hapitest RET ioctl 0 3121 hapitest CALL read(0x5,0x8563e6a,0x44) 3121 hapitest GIO fd 5 read 68 bytes "\^E\0\^D\0\M-~\M^?\^B\0\^E\0\^C\0 \0\^B\0\M-z\M^?\M-z\M^?\^B\0\v\0 \0\^A\0\M^?\M^?\^A\0\^E\0\^A\0\ \0\0\^C\0\M^?\M^?\^C\0\^F\0\0\0\M-z\M^?\M-z\M^?\M-~\M^?\^E\0\M^?\M^?\ \M-~\M^?\^B\0\M-}\M^?\0\0\^C\0" 3121 hapitest RET read 68/0x44 3121 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 3121 hapitest RET ioctl 0 3121 hapitest CALL read(0x5,0x8563eae,0x88) 3121 hapitest GIO fd 5 read 136 bytes "\^D\0\M-v\M^?\M-u\M^?\M-z\M^?\M-z\M^?\^D\0\^E\0\M^?\M^?\M^?\M^?\^A\0\0\ \0\M-{\M^?\M^?\M^?\^D\0\^C\0\^F\0\v\0\a\0\M-~\M^?\M-z\M^?\M-|\M^?\0\0\ \M-}\M^?\M-y\M^?\M-x\M^?\M-z\M^?\M-}\M^?\M-~\M^?\M-z\M^?\M-x\M^?\^A\0\ \M-}\M^?\M-{\M^?\M-}\M^?\M-{\M^?\M-~\M^?\M-~\M^?\0\0\M^?\M^?\M-}\M^?\ \M-|\M^?\M^?\M^?\0\0\M-|\M^?\M-}\M^?\M-~\M^?\^C\0\a\0\^E\0\^A\0\M-~\ \M^?\^A\0\^F\0\^E\0\^B\0\M^?\M^?\M^?\M^?\M-|\M^?\M-z\M^?\M-{\M^?\M-|\ \M^?\^C\0\^E\0\0\0\M-}\M^?\M^?\M^?\M-~\M^?\M-|\M^?" 3121 hapitest RET read 136/0x88 3121 hapitest CALL ioctl(0x5,SNDCTL_DSP_GETISPACE,0x85e385c) 3121 hapitest RET ioctl 0 3121 hapitest CALL read(0x5,0x8563f36,0x110) 3121 hapitest GIO fd 5 read 272 bytes lots of little reads... now THEORETICALLY the program should read the same data either way and it should work the same, but in practice, it no-longer recognises any speech. Is there a sound guru who can give as an easy way to make it behave like before as we want to see if that is making a difference.. Kernel patches are ok, but since we can't modify the program a suggestion of "make the program do XXX" doesn't help us. The hardware is: [kxt1a] /dev <21> cat sndstat.bak0 FreeBSD Audio Driver (newpcm) Oct 11 2001 16:19:03 Installed devices: pcm0: at io 0x1440 irq 9 (1p/1r/0v channels duplex) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Oct 11 22: 7:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 6EAAC37B40A; Thu, 11 Oct 2001 22:07:51 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9C57eT03774; Thu, 11 Oct 2001 22:07:40 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "MurrayTaylor" , , Subject: RE: Imagestream WanIC-520 interface cards Date: Thu, 11 Oct 2001 22:07:40 -0700 Message-ID: <000601c152db$d12a2480$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <01a201c152af$5b09ae00$2a7627cb@bytecraft.au.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The WANic 5xx's use an incompatible chipset and the driver will not work with them. I thnk your supplier is feeding you a line of bullshit. SBS Communications has posted no plans whatsover to discontinue or change the WANic line. They are fully aware that the 405's have open source drivers and are furthermore used in embedded systems too. The WANic 5xx series of cards sell for more money and so naturally your supplier is most interested in maximizing his margin and would prefer to push you into a more expensive card. With the increase in CPU power all of the go-fast hardware on the higher-level cards is less important. Consider that the Hitachi controller chip used on the WANic 405 is the SAME chip that Cisco uses in it's 25xx series of routers, and the Cisco 2501 is the most used router in the world and has the most installed units. SBS Communications is STILL selling the RISCom series of cards which is the predecessor to the WANic, uses the same controller, these are ISA cards that have a design that's over 10 years old. You tell your supplier that since the 405 is being "phased out" that he should sell you a bunch of them at closeout prices. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com >-----Original Message----- >From: owner-freebsd-questions@FreeBSD.ORG >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of MurrayTaylor >Sent: Thursday, October 11, 2001 4:49 PM >To: freebsd-questions@FreeBSD.ORG; freebsd-hackers@FreeBSD.ORG >Subject: Imagestream WanIC-520 interface cards > > >As the WanIC-405 is being phased out (according to my supplier >down under here in OZ), has any development / testing been done on the >apparent replacement, the WanIC-521 (522, 524 ... ) range > >I am especially interested in its compatibility with its predecessor >which I am using very successfully for frame relay under Netgraph. > >I'm trying to get compatability info from the supplier here, >but we are a long way down the food chain ;-( > >Tia > >Murray Taylor >Bytecraft Systems Pty Ltd >murraytaylor@bytecraftsystems.com > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 0: 8:54 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from straylight.ringlet.net (straylight.ringlet.net [217.75.134.254]) by hub.freebsd.org (Postfix) with SMTP id 38FA737B406 for ; Fri, 12 Oct 2001 00:08:47 -0700 (PDT) Received: (qmail 96701 invoked by uid 1000); 12 Oct 2001 07:05:27 -0000 Date: Fri, 12 Oct 2001 10:05:27 +0300 From: Peter Pentchev To: Mike Meyer Cc: hackers@freebsd.org Subject: Re: My contributions to the close a PR campaign Message-ID: <20011012100527.B78786@straylight.oblivion.bg> Mail-Followup-To: Mike Meyer , hackers@freebsd.org References: <15301.63455.964624.626361@guru.mired.org> <200110112245.f9BMjAS66764@gits.dyndns.org> <15302.12256.96805.125719@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <15302.12256.96805.125719@guru.mired.org>; from mwm@mired.org on Thu, Oct 11, 2001 at 06:48:48PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Oct 11, 2001 at 06:48:48PM -0500, Mike Meyer wrote: > Cyrille Lefevre types: > > Mike Meyer wrote: > > [snip] > > > conf/21722 The mixer settings are lost on system reboot. > > > > > > This should probably be closed due to the work being done on the > > > NetBSD rc system. The same functionality can be provided as a port, > > > which is probably better anyway. I'll do that if this one gets closed. > > > > much better is to keep it, at least to remember that something like > > that have to be done. > > I'm not convinced it needs to be done. It's not really a critical > feature, and very few people seem to miss it. It makes a lot more > sense as a port that the few people who miss it can install. I've > already got the script; I just want to make sure I don't do the work > of turning it into a port only to have this thing committed. > > The script is so trivial I use it as an example of how to do rc.d > scripts on -questions. The script is indeed trivial, and I could commit it as a port, listing you as maintainer. I have just one question: would it be wise to have /var/db/mixer-state removed upon port deinstall, or should it be left behind, just in case? I think it would rather be removed to leave the system cleaner; if it is removed as part of a port update, it will be regenerated at the next shutdown anyway. G'luck, Peter -- I am jealous of the first word in this sentence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 1:35:30 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f154.law14.hotmail.com [64.4.21.154]) by hub.freebsd.org (Postfix) with ESMTP id A119237B406 for ; Fri, 12 Oct 2001 01:35:27 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 12 Oct 2001 01:35:27 -0700 Received: from 203.130.214.173 by lw14fd.law14.hotmail.msn.com with HTTP; Fri, 12 Oct 2001 08:35:27 GMT X-Originating-IP: [203.130.214.173] From: "himura kenshin" To: freebsd-hackers@FreeBSD.org Date: Fri, 12 Oct 2001 16:35:27 +0800 Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 12 Oct 2001 08:35:27.0567 (UTC) FILETIME=[D832F5F0:01C152F8] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG subscribe _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 1:39:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.noos.fr (lafontaine.noos.net [212.198.2.72]) by hub.freebsd.org (Postfix) with ESMTP id E922037B409 for ; Fri, 12 Oct 2001 01:39:22 -0700 (PDT) Received: (qmail 81032895 invoked by uid 0); 12 Oct 2001 08:39:21 -0000 Received: from unknown (HELO gits.dyndns.org) ([212.198.231.187]) (envelope-sender ) by 212.198.2.72 (qmail-ldap-1.03) with DES-CBC3-SHA encrypted SMTP for ; 12 Oct 2001 08:39:21 -0000 Received: (from root@localhost) by gits.dyndns.org (8.11.6/8.11.6) id f9C8dIr87058; Fri, 12 Oct 2001 10:39:18 +0200 (CEST) (envelope-from root) Message-Id: <200110120839.f9C8dIr87058@gits.dyndns.org> Subject: Re: My contributions to the close a PR campaign In-Reply-To: <15302.12256.96805.125719@guru.mired.org> To: Mike Meyer Date: Fri, 12 Oct 2001 10:39:17 +0200 (CEST) Cc: hackers@freebsd.org, chuckr@freebsd.org, chris@freebsd.org Reply-To: clefevre@citeweb.net From: Cyrille Lefevre Organization: ACME X-Face: X-Mailer: ELM [version 2.4ME+ PL94c (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mike Meyer wrote: > Cyrille Lefevre types: > > Mike Meyer wrote: > > [snip] > > > conf/21722 The mixer settings are lost on system reboot. > > > > > > This should probably be closed due to the work being done on the > > > NetBSD rc system. The same functionality can be provided as a port, > > > which is probably better anyway. I'll do that if this one gets closed. > > > > much better is to keep it, at least to remember that something like > > that have to be done. > > I'm not convinced it needs to be done. It's not really a critical > feature, and very few people seem to miss it. It makes a lot more a simple alternative (the one I use) is to add someting like this to /etc/defaults/rc.conf : mixer="NO" # soundcard mixer values (or NO). /etc/rc.conf : mixer="vol 100 pcm 25 speaker 50 line 0" and /etc/rc.syscons : case ${mixer} in [Nn][Oo] | '') ;; *) echo -n ' mixer'; mixer ${mixer} > /dev/null 2>&1 ;; esac Cyrille. -- Cyrille Lefevre mailto:clefevre@citeweb.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 3:52:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snark.rinet.ru (snark.rinet.ru [195.54.192.73]) by hub.freebsd.org (Postfix) with ESMTP id 33EC937B401 for ; Fri, 12 Oct 2001 03:52:31 -0700 (PDT) Received: (from yar@localhost) by snark.rinet.ru (8.11.6/8.11.6) id f9CAqS551160 for hackers@freebsd.org; Fri, 12 Oct 2001 14:52:28 +0400 (MSD) (envelope-from yar) Date: Fri, 12 Oct 2001 14:52:28 +0400 From: Yar Tikhiy To: hackers@freebsd.org Subject: Valid user name Message-ID: <20011012145227.D46577@snark.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there, Now adduser(8) and pw(8) differ in what a valid user name is. Adduser(8) enforces a user name to match the /^[a-z0-9_][a-z0-9_\-]*$/ regexp. OTOH, pw(8) uses the Good Old Wrong Way of checking validity-- it checks a user name against a list of *invalid* characters. I'm going to fix pw(8) so its view on valid user names is consistent with that of adduser(8). Is there any reason to omit the period ('.') from the list of valid characters? With the period included, the list would conform to POSIX's definition of a valid user name. -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 6:25:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-d07.mx.aol.com (imo-d07.mx.aol.com [205.188.157.39]) by hub.freebsd.org (Postfix) with ESMTP id D7AA037B409 for ; Fri, 12 Oct 2001 06:25:41 -0700 (PDT) Received: from Bsdguru@aol.com by imo-d07.mx.aol.com (mail_out_v31_r1.8.) id s.103.a728861 (25306); Fri, 12 Oct 2001 09:25:29 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <103.a728861.28f84948@aol.com> Date: Fri, 12 Oct 2001 09:25:28 EDT Subject: Re: Imagestream WanIC-520 interface cards To: tedm@toybox.placo.com Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 10/12/01 1:08:44 AM Eastern Daylight Time, tedm@toybox.placo.com writes: > Consider that the Hitachi controller chip used on the WANic 405 is the > SAME chip that Cisco uses in it's 25xx series of routers, and the Cisco > 2501 is the most used router in the world and has the most installed > units. > > SBS Communications is STILL selling the RISCom series of cards which is > the predecessor to the WANic, uses the same controller, these are ISA cards > that have a design that's over 10 years old. > > You tell your supplier that since the 405 is being "phased out" that he > should sell you a bunch of them at closeout prices. > Calm yourself Ted. Perhaps the fact that the (incredibly slow) 2501 has been phased out has caused Hitachi to "phase out" their part? You know, big chip vendors have bigger fish to fry than the WanIC series. HDLC controllers that can barely run 2 T1s are not mainstream these days, so they may just not want to make it anymore. If you think that Hitachi cares that there are "open source" drivers in use in what they would consider a handful of applications, you dont understand the chip business. When cisco goes away, they find a better use for their foundry. B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 8: 1:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id 9A8D837B405 for ; Fri, 12 Oct 2001 08:01:10 -0700 (PDT) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id f9CF17Y14052; Fri, 12 Oct 2001 10:01:07 -0500 (CDT) (envelope-from tinguely) Date: Fri, 12 Oct 2001 10:01:07 -0500 (CDT) From: mark tinguely Message-Id: <200110121501.f9CF17Y14052@web.cs.ndsu.nodak.edu> To: dillon@earth.backplane.com, Patrick.Cipiere@UDcast.com Subject: Re: contigfree, free what? Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Patrick Cipiere says: > > :We are currently working with FreeBSD 4.3 and we found out that > :kldloading/kldunloading modules working with contigmalloc()/contigfree() > :like if_xl.ko produces a memory leak. > : > :This is due to the contigfree() function which seems to uncompletely release > :the memory ressource allocated in vm_page_array. > : > :When contigmalloc() steps in vm_page_array, it does not find back > :the pages previously released by contigfree() > :The loop vm/vm_page.c is this one: In FreeBSD 4.4 (and I do not think there is any change from 4.3), I placed the contigmalloc/free using the if_xl.c structures in a new PCI probe routine so it gets called several times in a boot process. I also placed some checks on vm_map_delete to see if the range of map gets modified (and therefore some pages are not freed. Everything works correctly; the correct amount is free, and the entry that this map is found in is completely the amount of the contigmalloc. Most of the time, I get the very same range, but as I started adding drivers and reserving memory, the start of contigmalloc creaps up, as expected. I think you are hitting the problem that contigmalloc cannot be guarrenteed to work once the physical memory becomes used and there is no range large enough for your new contigmalloc. That is why large contigmallocs are done at boot time. I did not try this with a loadable module, so I can't say if there is or is not a feature of the loading/unloading of the module that allocates memory that fills part of your contiguous range. Do you wish patches to VM code to verify that the free is done completely? --mark tinguely To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 8:16:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wally.eecs.harvard.edu (wally.eecs.harvard.edu [140.247.60.30]) by hub.freebsd.org (Postfix) with ESMTP id 8320237B40A for ; Fri, 12 Oct 2001 08:16:48 -0700 (PDT) Received: (from magoutis@localhost) by wally.eecs.harvard.edu (8.10.0/8.10.0) id f9CFGlG06737; Fri, 12 Oct 2001 11:16:47 -0400 (EDT) Date: Fri, 12 Oct 2001 11:16:47 -0400 (EDT) Message-Id: <200110121516.f9CFGlG06737@wally.eecs.harvard.edu> From: Kostas Magoutis To: freebsd-hackers@FreeBSD.ORG Subject: aio question Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Looking at the aio implementation in 4.3 it seems that at least the aio_read path bypasses the buffer cache. Is this true or am I missing something? Thanks, Kostas Magoutis To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 8:31:22 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from guru.mired.org (okc-65-31-203-60.mmcable.com [65.31.203.60]) by hub.freebsd.org (Postfix) with SMTP id 92C0737B40C for ; Fri, 12 Oct 2001 08:31:17 -0700 (PDT) Received: (qmail 99698 invoked by uid 100); 12 Oct 2001 15:31:11 -0000 From: Mike Meyer MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <15303.3263.275966.640664@guru.mired.org> Date: Fri, 12 Oct 2001 10:31:11 -0500 To: Peter Pentchev Cc: hackers@freebsd.org Subject: Re: My contributions to the close a PR campaign In-Reply-To: <20011012100527.B78786@straylight.oblivion.bg> References: <15301.63455.964624.626361@guru.mired.org> <200110112245.f9BMjAS66764@gits.dyndns.org> <15302.12256.96805.125719@guru.mired.org> <20011012100527.B78786@straylight.oblivion.bg> X-Mailer: VM 6.90 under 21.1 (patch 14) "Cuyahoga Valley" XEmacs Lucid X-face: "5Mnwy%?j>IIV\)A=):rjWL~NB2aH[}Yq8Z=u~vJ`"(,&SiLvbbz2W`;h9L,Yg`+vb1>RG% *h+%X^n0EZd>TM8_IB;a8F?(Fb"lw'IgCoyM.[Lg#r\ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Peter Pentchev types: > On Thu, Oct 11, 2001 at 06:48:48PM -0500, Mike Meyer wrote: > > Cyrille Lefevre types: > > > Mike Meyer wrote: > > > [snip] > > > > conf/21722 The mixer settings are lost on system reboot. > > > > > > > > This should probably be closed due to the work being done on the > > > > NetBSD rc system. The same functionality can be provided as a port, > > > > which is probably better anyway. I'll do that if this one gets closed. > > > much better is to keep it, at least to remember that something like > > > that have to be done. > > I'm not convinced it needs to be done. It's not really a critical > > feature, and very few people seem to miss it. It makes a lot more > > sense as a port that the few people who miss it can install. I've > > already got the script; I just want to make sure I don't do the work > > of turning it into a port only to have this thing committed. > > The script is so trivial I use it as an example of how to do rc.d > > scripts on -questions. > The script is indeed trivial, and I could commit it as a port, > listing you as maintainer. I have just one question: would it be > wise to have /var/db/mixer-state removed upon port deinstall, or should > it be left behind, just in case? I think it would rather be removed > to leave the system cleaner; if it is removed as part of a port update, > it will be regenerated at the next shutdown anyway. Sure, go ahead and commit it as a port listing me as maintainer. Yes, I'd remove /var/db/mixer-state when you deinstall the port. If someone really wants to save the mixer state, they can do it by hand, or using any of a number of different tools in the ports tree. After the port is commited, you can close PR conf/21722. Thanx, http://www.mired.org/home/mwm/ Q: How do you make the gods laugh? A: Tell them your plans. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 8:52:15 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id AD69637B408; Fri, 12 Oct 2001 08:52:12 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f9CFqBu21119; Fri, 12 Oct 2001 09:52:11 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f9CFqA793345; Fri, 12 Oct 2001 09:52:11 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110121552.f9CFqA793345@harmony.village.org> To: Yar Tikhiy Subject: Re: Valid user name Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Fri, 12 Oct 2001 14:52:28 +0400." <20011012145227.D46577@snark.rinet.ru> References: <20011012145227.D46577@snark.rinet.ru> Date: Fri, 12 Oct 2001 09:52:10 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011012145227.D46577@snark.rinet.ru> Yar Tikhiy writes: : Is there any reason to omit the period ('.') from the list of valid : characters? With the period included, the list would conform to : POSIX's definition of a valid user name. Not any more. it used to be that chown user.group would be ambiguous. now it isn't, since user:group is the right syntax. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 9: 5:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ra.udcast.com (ANice-101-2-1-104.abo.wanadoo.fr [193.251.10.104]) by hub.freebsd.org (Postfix) with ESMTP id 0E40737B40F for ; Fri, 12 Oct 2001 09:05:25 -0700 (PDT) Received: (from pplc@localhost) by ra.udcast.com (8.11.0/8.11.0) id f9CG5F726010; Fri, 12 Oct 2001 18:05:15 +0200 Date: Fri, 12 Oct 2001 18:05:15 +0200 Message-Id: <200110121605.f9CG5F726010@ra.udcast.com> From: Patrick Cipiere To: tinguely@web.cs.ndsu.nodak.edu Cc: dillon@earth.backplane.com, Patrick.Cipiere@UDcast.com, freebsd-hackers@FreeBSD.ORG In-reply-to: <200110121501.f9CF17Y14052@web.cs.ndsu.nodak.edu> (message from mark tinguely on Fri, 12 Oct 2001 10:01:07 -0500 (CDT)) Subject: Re: contigfree, free what? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Mark, > I also placed some checks on vm_map_delete I did that also, and as far as I understand everything works fine. The only thing I found was the fact that when contigmalloc() grabs the contig pages it sets the value of pga[i] (for i in allocated pages) note that: vm_page_t pga = vm_page_array; Then contigfree() does a pretty good job, but does not reset the values of pga[i] to pqtype == PQ_FREE (pqtype = pga[i].queue - pga[i].pc) So the next contigmalloc() requiring the same number of pages fails on the previously released pages because they are not PQ_FREE The other thing that puzzled me is the fact that in vm_map_delete() called by contgigfree() has a variable object = entry->object.vm_object; which shows a value of 0 rather than kernel_object or kmem_object But my understanding might be wrong. Thanks, Patrick. -- UDcast: Full IP over Broadcast Media Phone: (+33) (0)4 93 00 16 99 Mobile: (+33) (0)6 14 21 55 98 Fax: (+33) (0)4 93 00 16 61 http://www.UDcast.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 9:31:56 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from straylight.ringlet.net (straylight.ringlet.net [217.75.134.254]) by hub.freebsd.org (Postfix) with SMTP id 3202637B405 for ; Fri, 12 Oct 2001 09:31:50 -0700 (PDT) Received: (qmail 74946 invoked by uid 1000); 12 Oct 2001 16:24:57 -0000 Date: Fri, 12 Oct 2001 19:24:57 +0300 From: Peter Pentchev To: Warner Losh Cc: Yar Tikhiy , hackers@FreeBSD.ORG Subject: Re: Valid user name Message-ID: <20011012192457.A74895@straylight.oblivion.bg> Mail-Followup-To: Warner Losh , Yar Tikhiy , hackers@FreeBSD.ORG References: <20011012145227.D46577@snark.rinet.ru> <200110121552.f9CFqA793345@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110121552.f9CFqA793345@harmony.village.org>; from imp@harmony.village.org on Fri, Oct 12, 2001 at 09:52:10AM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Oct 12, 2001 at 09:52:10AM -0600, Warner Losh wrote: > In message <20011012145227.D46577@snark.rinet.ru> Yar Tikhiy writes: > : Is there any reason to omit the period ('.') from the list of valid > : characters? With the period included, the list would conform to > : POSIX's definition of a valid user name. > > Not any more. it used to be that chown user.group would be > ambiguous. now it isn't, since user:group is the right syntax. This might be a problem for NIS or Kerberos domains - an older version of FreeBSD might be confuzzled by usernames which are perfectly valid for the rest of the client boxes. G'luck, Peter -- because I didn't think of a good beginning of it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 10: 7:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id DA9FF37B407 for ; Fri, 12 Oct 2001 10:07:14 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f9CH7Ax34395; Fri, 12 Oct 2001 10:07:10 -0700 (PDT) (envelope-from dillon) Date: Fri, 12 Oct 2001 10:07:10 -0700 (PDT) From: Matt Dillon Message-Id: <200110121707.f9CH7Ax34395@earth.backplane.com> To: Patrick Cipiere Cc: tinguely@web.cs.ndsu.nodak.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: contigfree, free what? References: <200110121605.f9CG5F726010@ra.udcast.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Mark, : :> I also placed some checks on vm_map_delete : :I did that also, and as far as I understand everything works fine. :The only thing I found was the fact that when contigmalloc() grabs the :contig pages it sets the value of pga[i] (for i in allocated pages) :note that: vm_page_t pga = vm_page_array; : :Then contigfree() does a pretty good job, but does not reset the values :of pga[i] to pqtype == PQ_FREE (pqtype = pga[i].queue - pga[i].pc) : :So the next contigmalloc() requiring the same number of pages fails on :the previously released pages because they are not PQ_FREE : :The other thing that puzzled me is the fact that in vm_map_delete() :called by contgigfree() has a variable :... I think what is going on is that contigmalloc() is wiring the pages but placing them in a pageable container (entry->wired_count == 0), so when contigfree() kmem_free()'s the block the system does not know that it must unwire the pages. This leaves the pages wired and prevents them from being freed. I haven't found a quick and easy solution to the problem yet. kmem_alloc() doesn't do what we want either. I tried calling vm_map_pageable() in contigmalloc1() but it crashed the machine, so there might be something else going on as well. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 10:28:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id 7303A37B405 for ; Fri, 12 Oct 2001 10:28:22 -0700 (PDT) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id f9CHSKx14929; Fri, 12 Oct 2001 12:28:20 -0500 (CDT) (envelope-from tinguely) Date: Fri, 12 Oct 2001 12:28:20 -0500 (CDT) From: mark tinguely Message-Id: <200110121728.f9CHSKx14929@web.cs.ndsu.nodak.edu> To: Patrick.Cipiere@udcast.com, tinguely@web.cs.ndsu.nodak.edu Subject: Re: contigfree, free what? Cc: dillon@earth.backplane.com, freebsd-hackers@FreeBSD.ORG In-Reply-To: <200110121605.f9CG5F726010@ra.udcast.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I can allocate the same memory block, back to back by contigmailloc and contigfree using the same if_xl structures in a PCI probe (actually I do contigmalloc/contigfree per probe call. The PCI probe gets called for each PCI device. I will print up the trace that shows the blocks are freed. I think the module load process takes a block in that contig range and the allocate can not longer be satisfied. --mark tinguely. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 11: 6:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id F3A5137B406; Fri, 12 Oct 2001 11:06:28 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f9CI5uY34981; Fri, 12 Oct 2001 11:05:56 -0700 (PDT) (envelope-from dillon) Date: Fri, 12 Oct 2001 11:05:56 -0700 (PDT) From: Matt Dillon Message-Id: <200110121805.f9CI5uY34981@earth.backplane.com> To: Julian Elischer Cc: hackers@FreeBSD.ORG, developers@FreeBSD.ORG Subject: Re: Patch to allow 4.2 driver .o to run on 4.4 References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :Sorry about the crosspost but I estimate that this reaches those who need :to see this.. : :There was a change in the 4.x kernel.h on June 15 that broke backwards :compatibility for binary distributed driver files :(distributed as .o files) It was an MFC of a patch by peter.. :but we didn't understand the ramifications in 4.x. This seems very reasonable to me... a nice quick and easy solution. -Matt :my fix (a reversion in part) is as follows: : :Index: kernel.h :=================================================================== :RCS file: /repos/cvs/mod/freebsd/src/sys/sys/kernel.h,v :retrieving revision 1.63.2.5 :diff -u -r1.63.2.5 kernel.h :--- kernel.h 2001/07/26 23:27:53 1.63.2.5 :+++ kernel.h 2001/10/11 21:30:03 :@@ -113,13 +113,13 @@ : SI_SUB_VM = 0x1000000, /* virtual memory system :init*/ : SI_SUB_KMEM = 0x1800000, /* kernel memory*/ : SI_SUB_KVM_RSRC = 0x1A00000, /* kvm operational :limits*/ :- SI_SUB_CPU = 0x2000000, /* CPU resource(s)*/ :- SI_SUB_KLD = 0x2100000, /* KLD and module setup */ :... : :The result of this was that old .o drivers are initialise at sequence :0x2400000 but the device framework is not initialised until 0x3100000. : :my patch shifts all the numbers back to below that that binary :... :Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 11:30:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from avocet.mail.pas.earthlink.net (avocet.mail.pas.earthlink.net [207.217.121.50]) by hub.freebsd.org (Postfix) with ESMTP id 6D95437B409; Fri, 12 Oct 2001 11:30:12 -0700 (PDT) Received: from dialup-209.247.139.200.dial1.sanjose1.level3.net ([209.247.139.200] helo=mindspring.com) by avocet.mail.pas.earthlink.net with esmtp (Exim 3.33 #1) id 15s74V-0002r2-00; Fri, 12 Oct 2001 11:30:11 -0700 Message-ID: <3BC736E5.2AF183F4@mindspring.com> Date: Fri, 12 Oct 2001 11:31:01 -0700 From: Terry Lambert Reply-To: tlambert2@mindspring.com X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Yar Tikhiy Cc: hackers@freebsd.org, doc@freebsd.org Subject: Re: utmp(5) manpage revised References: <20011011170226.A2162@snark.rinet.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Yar Tikhiy wrote: > > Hi everybody, > > The current utmp(5) manpage language (not markup) > has a number of drawbacks and errors: > > o There is no information for programmers on the actual structure > of the files the page describes. It is opaque. You are not supposed to access it directly, you are supposed to use library routines. You could make the same argument about "db" files... > o The C structure members aren't described. "" > o Despites the page language, neither utmp nor lastlog grow > continually or need rotation. That's a real error. Good catch. > o It describes in a wrong way how a user's logout is recorded to wtmp. I'm not sure that that's not an implementation detail that should be reomved from the man page entirely, but what you've done is equally valid. > o The login(3), logout(3) and logwtmp(3) functions aren't mentioned. This is a good correction. > Here's a patch addressing all the issues. Review it please. I'm not sure that the structure should be documented, as it will encourage people to access the data directly. The point of having them access it through library routines is that it's possible to replace the implementation by replacing the libc.so on a system, and have software continue to function. Or, it's possible to install binaries that use libc.so on a system with a different underlying implementaiton, and have them "just work" for commercial vendors. -- Terry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 11:41:38 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from web.cs.ndsu.nodak.edu (web.cs.ndsu.NoDak.edu [134.129.125.7]) by hub.freebsd.org (Postfix) with ESMTP id 1A69637B408 for ; Fri, 12 Oct 2001 11:41:36 -0700 (PDT) Received: (from tinguely@localhost) by web.cs.ndsu.nodak.edu (8.11.4/8.11.4) id f9CIfWJ15403; Fri, 12 Oct 2001 13:41:32 -0500 (CDT) (envelope-from tinguely) Date: Fri, 12 Oct 2001 13:41:32 -0500 (CDT) From: mark tinguely Message-Id: <200110121841.f9CIfWJ15403@web.cs.ndsu.nodak.edu> To: dillon@earth.backplane.com, Patrick.Cipiere@udcast.com Subject: Re: contigfree, free what? Cc: freebsd-hackers@FreeBSD.ORG, tinguely@web.cs.ndsu.nodak.edu In-Reply-To: <200110121707.f9CH7Ax34395@earth.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG apologies, as soon as I sent that mail, I realized that I was looking at the virtual address -- duh, mark. Patrick was pointed in the right direction that the entry's object is no longer the kernel_map but is NULL, changing the release path. --mark tinguely To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 11:48:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by hub.freebsd.org (Postfix) with SMTP id 60BCE37B409 for ; Fri, 12 Oct 2001 11:48:40 -0700 (PDT) Received: (qmail 28055 invoked by uid 0); 12 Oct 2001 18:47:50 -0000 Received: from pd9e16bf0.dip.t-dialin.net (HELO forge.local) (217.225.107.240) by mail.gmx.net (mp020-rz3) with SMTP; 12 Oct 2001 18:47:50 -0000 Received: from tmm by forge.local with local (Exim 3.30 #1) id 15s7LG-000BiJ-00; Fri, 12 Oct 2001 20:47:31 +0200 Date: Fri, 12 Oct 2001 20:47:30 +0200 From: Thomas Moestl To: Matt Dillon Cc: Patrick Cipiere , tinguely@web.cs.ndsu.nodak.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: contigfree, free what? Message-ID: <20011012204730.F407@crow.dom2ip.de> References: <200110121605.f9CG5F726010@ra.udcast.com> <200110121707.f9CH7Ax34395@earth.backplane.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="TakKZr9L6Hm6aLOc" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200110121707.f9CH7Ax34395@earth.backplane.com>; from dillon@earth.backplane.com on Fri, Oct 12, 2001 at 10:07:10AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --TakKZr9L6Hm6aLOc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, 2001/10/12 at 10:07:10 -0700, Matt Dillon wrote: > > :Mark, > : > :> I also placed some checks on vm_map_delete > : > :I did that also, and as far as I understand everything works fine. > :The only thing I found was the fact that when contigmalloc() grabs the > :contig pages it sets the value of pga[i] (for i in allocated pages) > :note that: vm_page_t pga = vm_page_array; > : > :Then contigfree() does a pretty good job, but does not reset the values > :of pga[i] to pqtype == PQ_FREE (pqtype = pga[i].queue - pga[i].pc) > : > :So the next contigmalloc() requiring the same number of pages fails on > :the previously released pages because they are not PQ_FREE > : > :The other thing that puzzled me is the fact that in vm_map_delete() > :called by contgigfree() has a variable > :... I have also looked into this a while ago, but got stuck at some point. I have just looked at it again, and I think I have found a solution. > I think what is going on is that contigmalloc() is wiring the pages > but placing them in a pageable container (entry->wired_count == 0), > so when contigfree() kmem_free()'s the block the system does not know > that it must unwire the pages. This leaves the pages wired and prevents > them from being freed. > > I haven't found a quick and easy solution to the problem yet. kmem_alloc() > doesn't do what we want either. I tried calling vm_map_pageable() in > contigmalloc1() but it crashed the machine, so there might be something > else going on as well. This is probably because the map entries do have a NULL object pointer. vm_map_pageable() calls vm_fault_wire(), so this will fail. I have attached a patch which works for me. It duplicates most of the logic of kmem_alloc in that it calls vm_map_findspace() first, then vm_map_insert() (which basically is what is done in kmem_alloc_pageable() too, but here, kernel_object is passed instead of a NULL pointer, so that the map entry will have a valid object pointer). Then, the pages are inserted into the object as before, and finally, the map entries are marked as wired by using vm_map_pageable(). Because this will also call vm_fault_wire(), which will among other things do a vm_page_wire(), contigmalloc does not need to wire the pages itself. The pmap_kenter() calls can also be reomved, since the pages will be mapped in any case by vm_fault(). - thomas --TakKZr9L6Hm6aLOc Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="vm_contig.diff" --- vm_contig.c.orig Fri Oct 12 20:05:09 2001 +++ vm_contig.c Fri Oct 12 20:44:03 2001 @@ -76,6 +76,8 @@ #include #include #include +#include +#include #include #include #include @@ -232,7 +234,6 @@ m->busy = 0; m->queue = PQ_NONE; m->object = NULL; - vm_page_wire(m); } /* @@ -240,24 +241,31 @@ * Allocate kernel VM, unfree and assign the physical pages to it and * return kernel VM pointer. */ - tmp_addr = addr = kmem_alloc_pageable(map, size); - if (addr == 0) { + vm_map_lock(map); + if (vm_map_findspace(map, vm_map_min(map), size, &addr) != + KERN_SUCCESS) { /* * XXX We almost never run out of kernel virtual * space, so we don't make the allocated memory * above available. */ + vm_map_unlock(map); splx(s); return (NULL); } + vm_object_reference(kernel_object); + vm_map_insert(map, kernel_object, addr - VM_MIN_KERNEL_ADDRESS, + addr, addr + size, VM_PROT_ALL, VM_PROT_ALL, 0); + vm_map_unlock(map); + tmp_addr = addr; for (i = start; i < (start + size / PAGE_SIZE); i++) { vm_page_t m = &pga[i]; vm_page_insert(m, kernel_object, OFF_TO_IDX(tmp_addr - VM_MIN_KERNEL_ADDRESS)); - pmap_kenter(tmp_addr, VM_PAGE_TO_PHYS(m)); tmp_addr += PAGE_SIZE; } + vm_map_pageable(map, addr, addr + size, FALSE); splx(s); return ((void *)addr); --TakKZr9L6Hm6aLOc-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 11:50:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 9DD6E37B405 for ; Fri, 12 Oct 2001 11:50:17 -0700 (PDT) Received: from opal (cs.binghamton.edu [128.226.123.101]) by bingnet2.cc.binghamton.edu (8.11.6/8.11.6) with ESMTP id f9CIoGG29403 for ; Fri, 12 Oct 2001 14:50:16 -0400 (EDT) Date: Fri, 12 Oct 2001 14:50:15 -0400 (EDT) From: Zhihui Zhang X-Sender: zzhang@opal To: freebsd-hackers@freebsd.org Subject: Page fault and bad memory Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am writing a program that stresses memory a lot. The program accepts a parameter to indicate how long it runs. For several big values, the program runs OK. But when I give a even bigger one, the system panics at generic_bcopy(). I am wondering whether this has something to do with bad memory chip or some other hardware problem. I do not believe that the program logic will change when given a bigger input. Although I am still studying the code, the chances of a software bug is small. How can I tell if this is due to bad memory? The system is running 4.3-Release and the program runs for about 2 hours. It is a kernel module doing a lot of I/O. Thanks for you advice. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 12:21:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 4158137B406 for ; Fri, 12 Oct 2001 12:21:30 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f9CJLR035585; Fri, 12 Oct 2001 12:21:27 -0700 (PDT) (envelope-from dillon) Date: Fri, 12 Oct 2001 12:21:27 -0700 (PDT) From: Matt Dillon Message-Id: <200110121921.f9CJLR035585@earth.backplane.com> To: Thomas Moestl Cc: Patrick Cipiere , tinguely@web.cs.ndsu.nodak.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: contigfree, free what? References: <200110121605.f9CG5F726010@ra.udcast.com> <200110121707.f9CH7Ax34395@earth.backplane.com> <20011012204730.F407@crow.dom2ip.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :I have also looked into this a while ago, but got stuck at some :point. I have just looked at it again, and I think I have found a solution. : :... : :This is probably because the map entries do have a NULL object :pointer. vm_map_pageable() calls vm_fault_wire(), so this will fail. : :I have attached a patch which works for me. It duplicates most of the :logic of kmem_alloc in that it calls vm_map_findspace() first, then :vm_map_insert() (which basically is what is done in :kmem_alloc_pageable() too, but here, kernel_object is passed instead :of a NULL pointer, so that the map entry will have a valid object :pointer). Then, the pages are inserted into the object as before, and :finally, the map entries are marked as wired by using :vm_map_pageable(). Because this will also call vm_fault_wire(), which :will among other things do a vm_page_wire(), contigmalloc does not :need to wire the pages itself. : :The pmap_kenter() calls can also be reomved, since the pages will be :mapped in any case by vm_fault(). : : - thomas Ach, of course. I see what's happening now! Thomas, your patch looks good! I'm going to patch it in and test it a bit. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 12:23:46 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from proxy.centtech.com (moat.centtech.com [206.196.95.10]) by hub.freebsd.org (Postfix) with ESMTP id EA21D37B408 for ; Fri, 12 Oct 2001 12:23:43 -0700 (PDT) Received: from sprint.centtech.com (sprint.centtech.com [10.177.173.31]) by proxy.centtech.com (8.11.6/8.11.6) with ESMTP id f9CJNh424420 for ; Fri, 12 Oct 2001 14:23:43 -0500 (CDT) Received: from centtech.com (proton [10.177.173.77]) by sprint.centtech.com (8.9.3+Sun/8.9.3) with ESMTP id OAA29848 for ; Fri, 12 Oct 2001 14:23:42 -0500 (CDT) Message-ID: <3BC742FB.B7C7D457@centtech.com> Date: Fri, 12 Oct 2001 14:22:35 -0500 From: Eric Anderson Reply-To: anderson@centtech.com Organization: Centaur Technology X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: dmesg -> $pir entries? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I saw this on my new 4.4 RELEASE box: Using $PIR table, 9 entries at 0xc00f7510 Anyone know what that means? -- ------------------------------------------------------------- Eric Anderson anderson@centtech.com Centaur Technology # rm -rf /bin/laden ------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 12:32:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from h132-197-97-45.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by hub.freebsd.org (Postfix) with ESMTP id 0ABCB37B408 for ; Fri, 12 Oct 2001 12:32:42 -0700 (PDT) Received: (from ak03@localhost) by h132-197-97-45.gte.com (8.11.6/8.11.4) id f9CJWYB58431; Fri, 12 Oct 2001 15:32:34 -0400 (EDT) (envelope-from ak03) Message-ID: X-Mailer: XFMail 1.5.1 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <3BC742FB.B7C7D457@centtech.com> Date: Fri, 12 Oct 2001 15:32:34 -0400 (EDT) Organization: Verizon Laboratories Inc. From: "Alexander N. Kabaev" To: Eric Anderson Subject: RE: dmesg -> $pir entries? Cc: hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG PCI BIOS resident table describing current pci interrupt routing, available PCI-only IRQ's, AFAIK. Message is for information only, just ignore it. On 12-Oct-2001 Eric Anderson wrote: > I saw this on my new 4.4 RELEASE box: > Using $PIR table, 9 entries at 0xc00f7510 > > Anyone know what that means? > > > -- > ------------------------------------------------------------- > Eric Anderson anderson@centtech.com Centaur Technology ># rm -rf /bin/laden > ------------------------------------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -------------------------------------------- E-Mail: Alexander N. Kabaev Date: 12-Oct-2001 Time: 15:29:34 -------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 14: 3: 3 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from robin.mail.pas.earthlink.net (robin.mail.pas.earthlink.net [207.217.120.65]) by hub.freebsd.org (Postfix) with ESMTP id 4F57837B401; Fri, 12 Oct 2001 14:03:01 -0700 (PDT) Received: from blossom.cjclark.org (dialup-209.245.143.238.Dial1.SanJose1.Level3.net [209.245.143.238]) by robin.mail.pas.earthlink.net (8.11.5/8.9.3) with ESMTP id f9CL2wT17578; Fri, 12 Oct 2001 14:02:59 -0700 (PDT) Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.3) id f9CKua705679; Fri, 12 Oct 2001 13:56:36 -0700 (PDT) (envelope-from cjc) Date: Fri, 12 Oct 2001 13:56:36 -0700 From: "Crist J. Clark" To: Yar Tikhiy Cc: hackers@FreeBSD.ORG Subject: Re: Valid user name Message-ID: <20011012135636.L293@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <20011012145227.D46577@snark.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011012145227.D46577@snark.rinet.ru>; from yar@FreeBSD.ORG on Fri, Oct 12, 2001 at 02:52:28PM +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Oct 12, 2001 at 02:52:28PM +0400, Yar Tikhiy wrote: > Hi there, > > Now adduser(8) and pw(8) differ in what a valid user name is. > Adduser(8) enforces a user name to match the /^[a-z0-9_][a-z0-9_\-]*$/ > regexp. OTOH, pw(8) uses the Good Old Wrong Way of checking validity-- > it checks a user name against a list of *invalid* characters. > > I'm going to fix pw(8) so its view on valid user names is consistent > with that of adduser(8). > > Is there any reason to omit the period ('.') from the list of valid > characters? With the period included, the list would conform to > POSIX's definition of a valid user name. The historical reason '.' is avoided is because it breaks, # chown user.group file Syntax. See the COMPATIBILITY section of chown(8). -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 14:53:57 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from navgwout.symantec.com (navgwout.symantec.com [198.6.49.12]) by hub.freebsd.org (Postfix) with ESMTP id 3C60837B408 for ; Fri, 12 Oct 2001 14:53:53 -0700 (PDT) Received: from navgwout.symantec.com (navgwout [198.6.49.12]) by navgwout.symantec.com (8.9.3+Sun/8.9.3) with SMTP id OAA13037 for ; Fri, 12 Oct 2001 14:53:49 -0700 (PDT) Received: from mailer.symantec.com ([198.6.49.176]) by navgwout.symantec.com (NAVGW 2.5.1.13) with SMTP id M2001101214534812142 for ; Fri, 12 Oct 2001 14:53:48 -0700 Received: from uscu-smtp02.symantec.com (uscu-smtp02.symantec.com [155.64.74.114]) by mailer.symantec.com (8.9.3+Sun/8.9.3) with ESMTP id OAA18687 for ; Fri, 12 Oct 2001 14:53:48 -0700 (PDT) Subject: Severe I/O Problems To: freebsd-hackers@freebsd.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Jay Rossiter" Date: Fri, 12 Oct 2001 14:51:10 -0700 X-MIMETrack: Serialize by Router on USCU-SMTP02/SYMSMTP(Release 5.0.8 |June 18, 2001) at 10/12/2001 02:46:37 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Someone on -questions recommended that I forward this over here for you guys to look at. (I'm not subbed to this list) There appear to be a lot of changes that went into the filesystem and I/O code between 4.3 and 4.4. A little over a week ago I upgraded my 4.3 box to 4.4-STABLE and immediately I started having I/O slowdown. I do development and QA on a program that is very I/O bound, but the changes between 4.3 and 4.4 aren't small enough that I can ignore them. A few statistics: BSD, P4 1.4GHz, ATA100 drives - Normal test run on 4.3 was taking ~3 hours. - Normal test run on 4.4 is taking 15-16 hours. P3-800, ATA66 drives, SuSE Linux 7.1: - Normal test run takes ~4.5 hours. UltraSparc 10, Solaris 8, ATA66 drives: - Normal test run takes ~6 hours. As you can see, this jump was just phenomenal. I can run these tests on a custom 'ramdrive' and the test run takes 1.5 hours on BSD. ~4 on Solaris, ~2.5 on Linux. Even the RS/6000 I test AIX 4.3 with doesn't take this long, though I don't have statistics for it. It appears that the app gets stuck switching between the getblk and biowr states in top and ps, and very rarely does it take more than 5% of the CPU. On all other OS's, and even on 4.3, this app was pegging the CPU while it did its work. Basically.. this all comes down to "What the hell is going on here?!" and "Are there plans to fix it and did anyone even know there was a problem?" --- Jay Rossiter 503-614-7917 QA Engineer, Test Lead Symantec Corp. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 14:57:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id A995437B430 for ; Fri, 12 Oct 2001 14:57:26 -0700 (PDT) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f9CLvHH93335; Fri, 12 Oct 2001 14:57:18 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 12 Oct 2001 14:57:17 -0700 (PDT) From: Matthew Jacob Reply-To: To: Jay Rossiter Cc: Subject: Re: Severe I/O Problems In-Reply-To: Message-ID: <20011012145533.C73308-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hmm. Interesting. What's the state of the ATA write caching bit? (sysctl hw.ata.wc)? If it is set to 1, try setting it to 0 in /boot/loader.conf (e.g., add hw.ata.wc=0 ) to /boot/loader.conf -matt On Fri, 12 Oct 2001, Jay Rossiter wrote: > > Someone on -questions recommended that I forward this over here for > you guys to look at. (I'm not subbed to this list) > > There appear to be a lot of changes that went into the filesystem and I/O > code between 4.3 and 4.4. A little over a week ago I upgraded my 4.3 box > to 4.4-STABLE and immediately I started having I/O slowdown. I do > development and QA on a program that is very I/O bound, but the changes > between 4.3 and 4.4 aren't small enough that I can ignore them. > > A few statistics: > > BSD, P4 1.4GHz, ATA100 drives > - Normal test run on 4.3 was taking ~3 hours. > - Normal test run on 4.4 is taking 15-16 hours. > > P3-800, ATA66 drives, SuSE Linux 7.1: > - Normal test run takes ~4.5 hours. > > UltraSparc 10, Solaris 8, ATA66 drives: > - Normal test run takes ~6 hours. > > As you can see, this jump was just phenomenal. > > I can run these tests on a custom 'ramdrive' and the test run takes 1.5 > hours on BSD. ~4 on Solaris, ~2.5 on Linux. > > Even the RS/6000 I test AIX 4.3 with doesn't take this long, though I don't > have statistics for it. > > It appears that the app gets stuck switching between the getblk and biowr > states in top and ps, and very rarely does it take more than 5% of the CPU. > On all other OS's, and even on 4.3, this app was pegging the CPU while it > did its work. > > Basically.. this all comes down to "What the hell is going on here?!" and > "Are there plans to fix it and did anyone even know there was a problem?" > > --- > Jay Rossiter 503-614-7917 > QA Engineer, Test Lead > Symantec Corp. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 15: 2: 7 2001 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 1832F37B405 for ; Fri, 12 Oct 2001 15:02:05 -0700 (PDT) Received: from mail.Go2France.com (ms1.meiway.com [212.73.210.73]) by mgw1.MEIway.com (Postfix Relay Hub) with ESMTP id 25AD716B13 for ; Sat, 13 Oct 2001 00:01:59 +0200 (CEST) Received: from IBM-HIRXKN66F0W.Go2France.com [66.64.14.18] by mail.Go2France.com with ESMTP (SMTPD32-6.06) id AAF2100C0286; Sat, 13 Oct 2001 00:13:06 +0200 Message-Id: <5.1.0.14.0.20011012165857.00bd8170@mail.Go2France.com> X-Sender: LConrad@Go2France.com@mail.Go2France.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 12 Oct 2001 17:01:18 -0500 To: FReebsd-hackers@freebsd.org From: Len Conrad Subject: anybody working on a driver for this multi-T1 card? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG http://www.sbei.net/hw400p.htm Len http://MenAndMice.com/DNS-training http://BIND8NT.MEIway.com : ISC BIND 8.2.4 for NT4 & W2K http://IMGate.MEIway.com : Build free, hi-perf, anti-abuse mail gateways To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 15: 3: 5 2001 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 E6A3137B405 for ; Fri, 12 Oct 2001 15:02:59 -0700 (PDT) Received: (qmail 30697 invoked by uid 1000); 12 Oct 2001 22:02:58 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 12 Oct 2001 22:02:58 -0000 Date: Fri, 12 Oct 2001 17:02:58 -0500 (CDT) From: Mike Silbersack To: Jay Rossiter Cc: Subject: Re: Severe I/O Problems In-Reply-To: Message-ID: <20011012170203.J29945-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 12 Oct 2001, Jay Rossiter wrote: > There appear to be a lot of changes that went into the filesystem and I/O > code between 4.3 and 4.4. A little over a week ago I upgraded my 4.3 box > to 4.4-STABLE and immediately I started having I/O slowdown. I do > development and QA on a program that is very I/O bound, but the changes > between 4.3 and 4.4 aren't small enough that I can ignore them. By I/O bound, do you mean that it does a lot of file creation / deletion or that it does a lot of I/O within a few large files? 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 Oct 12 15:11:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from ims1.imagestream.com (ims1.imagestream.com [205.159.243.5]) by hub.freebsd.org (Postfix) with ESMTP id 07DE937B40B; Fri, 12 Oct 2001 15:11:06 -0700 (PDT) Received: from localhost (dhass@localhost) by ims1.imagestream.com (8.9.3/8.8.7) with SMTP id RAA06641; Fri, 12 Oct 2001 17:10:57 -0500 Date: Fri, 12 Oct 2001 17:10:57 -0500 (EST) From: Doug Hass To: owner-freebsd-questions@FreeBSD.ORG, Ted Mittelstaedt , MurrayTaylor , freebsd-hackers@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Cc: Alfred Shippen Subject: Re: FYI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I'm providing this to the people whose addresses appear in the original messages. My apologies if this gets cross-posted or sent multiple times to the same place. As I mention below, the WANic 400 series cards and all of the RISCom/N2 series cards are now End Of Life, and only available in special quantity builds. If anyone reading this message needs further information, please contact me directly and I can go into further depth about the EOL cards mentioned below and their replacements in the SBS line. Regards, Doug ----- Doug Hass ImageStream Internet Solutions dhass@imagestream.com http://www.imagestream.com Office: 1-219-935-8484 Fax: 1-219-935-8488 On Fri, 12 Oct 2001, Doug Hass wrote: > The WANic 400 series is definitely EOL. The cards are available in > quantities of 100+ only by special order. The RISCom/N2 series cards are > also EOL. > > This is a recent decision--it went into effect as of September 21st. > Closeout quantities have already been sold to other companies, so the > cards are only available by special order. > > The WANic 521/522 have replaced these cards, and should be used instead. > There are no drivers for FreeBSD, however. > > Doug > > > > On Sat, 13 Oct 2001, Alfred Shippen wrote: > > > This guy is local to you and is under the misapprehension that the Risc/400 > > series is not a discontinued item. I dont know if you want to follow them up > > or not. My customer (Bytecraft) is fine by this and has passed on the > > comments to me. > > > > Cheers > > > > > > > > > > > > ----- Original Message ----- > > > From: "Ted Mittelstaedt" > > > To: "MurrayTaylor" ; > > > ; > > > Sent: Friday, October 12, 2001 3:07 PM > > > Subject: RE: Imagestream WanIC-520 interface cards > > > > > > > > > > The WANic 5xx's use an incompatible chipset and the driver will not > > > > work with them. > > > > > > > > I thnk your supplier is feeding you a line of bullshit. SBS > > > Communications > > > > has posted no plans whatsover to discontinue or change the WANic line. > > > > They are fully aware that the 405's have open source drivers and are > > > > furthermore used in embedded systems too. > > > > > > > > The WANic 5xx series of cards sell for more money and so naturally your > > > > supplier is most interested in maximizing his margin and would prefer to > > > > push you into a more expensive card. > > > > > > > > With the increase in CPU power all of the go-fast hardware on the > > > higher-level > > > > cards is less important. > > > > > > > > Consider that the Hitachi controller chip used on the WANic 405 is the > > > > SAME chip that Cisco uses in it's 25xx series of routers, and the Cisco > > > > 2501 is the most used router in the world and has the most installed > > > > units. > > > > > > > > SBS Communications is STILL selling the RISCom series of cards which is > > > > the predecessor to the WANic, uses the same controller, these are ISA > > > cards > > > > that have a design that's over 10 years old. > > > > > > > > You tell your supplier that since the 405 is being "phased out" that he > > > > should sell you a bunch of them at closeout prices. > > > > > > > > Ted Mittelstaedt > > > tedm@toybox.placo.com > > > > Author of: The FreeBSD Corporate Networker's > > > Guide > > > > Book website: > > > http://www.freebsd-corp-net-guide.com > > > > > > > > > > > > >-----Original Message----- > > > > >From: owner-freebsd-questions@FreeBSD.ORG > > > > >[mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of MurrayTaylor > > > > >Sent: Thursday, October 11, 2001 4:49 PM > > > > >To: freebsd-questions@FreeBSD.ORG; freebsd-hackers@FreeBSD.ORG > > > > >Subject: Imagestream WanIC-520 interface cards > > > > > > > > > > > > > > >As the WanIC-405 is being phased out (according to my supplier > > > > >down under here in OZ), has any development / testing been done on the > > > > >apparent replacement, the WanIC-521 (522, 524 ... ) range > > > > > > > > > >I am especially interested in its compatibility with its predecessor > > > > >which I am using very successfully for frame relay under Netgraph. > > > > > > > > > >I'm trying to get compatability info from the supplier here, > > > > >but we are a long way down the food chain ;-( > > > > > > > > > >Tia > > > > > > > > > >Murray Taylor > > > > >Bytecraft Systems Pty Ltd > > > > >murraytaylor@bytecraftsystems.com > > > > > > > > > > > > > > > > > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > >with "unsubscribe freebsd-questions" in the body of the message > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 15:22:12 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from navgwout.symantec.com (navgwout.symantec.com [198.6.49.12]) by hub.freebsd.org (Postfix) with ESMTP id 944FA37B40D for ; Fri, 12 Oct 2001 15:22:02 -0700 (PDT) Received: from navgwout.symantec.com (navgwout [198.6.49.12]) by navgwout.symantec.com (8.9.3+Sun/8.9.3) with SMTP id PAA19542 for ; Fri, 12 Oct 2001 15:22:02 -0700 (PDT) Received: from mailer.symantec.com ([198.6.49.176]) by navgwout.symantec.com (NAVGW 2.5.1.13) with SMTP id M2001101215220125236 ; Fri, 12 Oct 2001 15:22:01 -0700 Received: from uscu-smtp02.symantec.com (uscu-smtp02.symantec.com [155.64.74.114]) by mailer.symantec.com (8.9.3+Sun/8.9.3) with ESMTP id PAA29696; Fri, 12 Oct 2001 15:22:01 -0700 (PDT) Subject: Re: Severe I/O Problems To: Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Jay Rossiter" Date: Fri, 12 Oct 2001 15:19:23 -0700 X-MIMETrack: Serialize by Router on USCU-SMTP02/SYMSMTP(Release 5.0.8 |June 18, 2001) at 10/12/2001 03:14:51 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG This does seem to be doing some good. The beginning of the test run is hovering ~30% CPU. I'll have to wait until it finished before I can see if it effected the overall time, though. Something else that I forgot to mention, is that yesterday I did a profiled run, and the code-time between the two scenarios differs by less than ten minutes. (The in-memory files vs. on disk files) The disk files just take infinitely longer to do anything to. Matthew Jacob com> cc: Subject: Re: Severe I/O Problems 10/12/2001 02:57 PM Please respond to mjacob Hmm. Interesting. What's the state of the ATA write caching bit? (sysctl hw.ata.wc)? If it is set to 1, try setting it to 0 in /boot/loader.conf (e.g., add hw.ata.wc=0 ) to /boot/loader.conf -matt On Fri, 12 Oct 2001, Jay Rossiter wrote: > > Someone on -questions recommended that I forward this over here for > you guys to look at. (I'm not subbed to this list) > > There appear to be a lot of changes that went into the filesystem and I/O > code between 4.3 and 4.4. A little over a week ago I upgraded my 4.3 box > to 4.4-STABLE and immediately I started having I/O slowdown. I do > development and QA on a program that is very I/O bound, but the changes > between 4.3 and 4.4 aren't small enough that I can ignore them. > > A few statistics: > > BSD, P4 1.4GHz, ATA100 drives > - Normal test run on 4.3 was taking ~3 hours. > - Normal test run on 4.4 is taking 15-16 hours. > > P3-800, ATA66 drives, SuSE Linux 7.1: > - Normal test run takes ~4.5 hours. > > UltraSparc 10, Solaris 8, ATA66 drives: > - Normal test run takes ~6 hours. > > As you can see, this jump was just phenomenal. > > I can run these tests on a custom 'ramdrive' and the test run takes 1.5 > hours on BSD. ~4 on Solaris, ~2.5 on Linux. > > Even the RS/6000 I test AIX 4.3 with doesn't take this long, though I don't > have statistics for it. > > It appears that the app gets stuck switching between the getblk and biowr > states in top and ps, and very rarely does it take more than 5% of the CPU. > On all other OS's, and even on 4.3, this app was pegging the CPU while it > did its work. > > Basically.. this all comes down to "What the hell is going on here?!" and > "Are there plans to fix it and did anyone even know there was a problem?" > > --- > Jay Rossiter 503-614-7917 > QA Engineer, Test Lead > Symantec Corp. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 15:23:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from navgwout.symantec.com (navgwout.symantec.com [198.6.49.12]) by hub.freebsd.org (Postfix) with ESMTP id A2D1337B401 for ; Fri, 12 Oct 2001 15:23:49 -0700 (PDT) Received: from navgwout.symantec.com (navgwout [198.6.49.12]) by navgwout.symantec.com (8.9.3+Sun/8.9.3) with SMTP id PAA20252 for ; Fri, 12 Oct 2001 15:23:49 -0700 (PDT) Received: from mailer.symantec.com ([198.6.49.176]) by navgwout.symantec.com (NAVGW 2.5.1.13) with SMTP id M2001101215234809746 ; Fri, 12 Oct 2001 15:23:48 -0700 Received: from uscu-smtp02.symantec.com (uscu-smtp02.symantec.com [155.64.74.114]) by mailer.symantec.com (8.9.3+Sun/8.9.3) with ESMTP id PAA00653; Fri, 12 Oct 2001 15:23:48 -0700 (PDT) Subject: Re: Severe I/O Problems To: Mike Silbersack Cc: freebsd-hackers@freebsd.org X-Mailer: Lotus Notes Release 5.0.8 June 18, 2001 Message-ID: From: "Jay Rossiter" Date: Fri, 12 Oct 2001 15:21:10 -0700 X-MIMETrack: Serialize by Router on USCU-SMTP02/SYMSMTP(Release 5.0.8 |June 18, 2001) at 10/12/2001 03:16:37 PM MIME-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Both. It does a lot of creation and deletion, and also does quite a bit of I/O internally to files. This is a piece of code that extracts, changes, replaces, deletes, and repacks archive container files. (zip, arj, lha, mime, you name it...) Mike Silbersack To: Jay Rossiter om> Subject: Re: Severe I/O Problems 10/12/2001 03:02 PM On Fri, 12 Oct 2001, Jay Rossiter wrote: > There appear to be a lot of changes that went into the filesystem and I/O > code between 4.3 and 4.4. A little over a week ago I upgraded my 4.3 box > to 4.4-STABLE and immediately I started having I/O slowdown. I do > development and QA on a program that is very I/O bound, but the changes > between 4.3 and 4.4 aren't small enough that I can ignore them. By I/O bound, do you mean that it does a lot of file creation / deletion or that it does a lot of I/O within a few large files? 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 Oct 12 15:26:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 20F6937B401; Fri, 12 Oct 2001 15:26:11 -0700 (PDT) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f9CMQ7H93621; Fri, 12 Oct 2001 15:26:07 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 12 Oct 2001 15:26:07 -0700 (PDT) From: Matthew Jacob Reply-To: To: Jay Rossiter , , Jordan Hubbard Cc: Subject: Re: Severe I/O Problems In-Reply-To: Message-ID: <20011012152458.E73308-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Interesting. If this bears out, what this tells me is that in some cases enabling write cacheing on ATAs is good, but in other cases, bad (probably provides interference effects). Soren? Jordan? -matt On Fri, 12 Oct 2001, Jay Rossiter wrote: > > > This does seem to be doing some good. The beginning of the test run > is hovering ~30% CPU. I'll have to wait until it finished before I can > see if it effected the overall time, though. > > Something else that I forgot to mention, is that yesterday I did a > profiled run, and the code-time between the two scenarios differs by less > than ten minutes. (The in-memory files vs. on disk files) The disk files > just take infinitely longer to do anything to. > > > > > > Matthew Jacob > > com> cc: > Subject: Re: Severe I/O Problems > 10/12/2001 > 02:57 PM > Please respond > to mjacob > > > > > > > > Hmm. Interesting. What's the state of the ATA write caching bit? > (sysctl hw.ata.wc)? > > If it is set to 1, try setting it to 0 in /boot/loader.conf > (e.g., add > > hw.ata.wc=0 > > ) > > to /boot/loader.conf > > -matt > > > On Fri, 12 Oct 2001, Jay Rossiter wrote: > > > > > Someone on -questions recommended that I forward this over here for > > you guys to look at. (I'm not subbed to this list) > > > > There appear to be a lot of changes that went into the filesystem and I/O > > code between 4.3 and 4.4. A little over a week ago I upgraded my 4.3 box > > to 4.4-STABLE and immediately I started having I/O slowdown. I do > > development and QA on a program that is very I/O bound, but the changes > > between 4.3 and 4.4 aren't small enough that I can ignore them. > > > > A few statistics: > > > > BSD, P4 1.4GHz, ATA100 drives > > - Normal test run on 4.3 was taking ~3 hours. > > - Normal test run on 4.4 is taking 15-16 hours. > > > > P3-800, ATA66 drives, SuSE Linux 7.1: > > - Normal test run takes ~4.5 hours. > > > > UltraSparc 10, Solaris 8, ATA66 drives: > > - Normal test run takes ~6 hours. > > > > As you can see, this jump was just phenomenal. > > > > I can run these tests on a custom 'ramdrive' and the test run takes 1.5 > > hours on BSD. ~4 on Solaris, ~2.5 on Linux. > > > > Even the RS/6000 I test AIX 4.3 with doesn't take this long, though I > don't > > have statistics for it. > > > > It appears that the app gets stuck switching between the getblk and biowr > > states in top and ps, and very rarely does it take more than 5% of the > CPU. > > On all other OS's, and even on 4.3, this app was pegging the CPU while it > > did its work. > > > > Basically.. this all comes down to "What the hell is going on here?!" and > > "Are there plans to fix it and did anyone even know there was a problem?" > > > > --- > > Jay Rossiter 503-614-7917 > > QA Engineer, Test Lead > > Symantec Corp. > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 15:36: 2 2001 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 6CEFB37B405 for ; Fri, 12 Oct 2001 15:35:59 -0700 (PDT) Received: (qmail 30866 invoked by uid 1000); 12 Oct 2001 22:35:57 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 12 Oct 2001 22:35:57 -0000 Date: Fri, 12 Oct 2001 17:35:57 -0500 (CDT) From: Mike Silbersack To: Jay Rossiter Cc: Subject: Re: Severe I/O Problems In-Reply-To: Message-ID: <20011012173410.D29945-100000@achilles.silby.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, 12 Oct 2001, Jay Rossiter wrote: > Both. It does a lot of creation and deletion, and also does quite a > bit of I/O internally to files. > > This is a piece of code that extracts, changes, replaces, deletes, and > repacks archive container files. (zip, arj, lha, mime, you name it...) I'm wondering if you should try 4.4-release, which would be before the dirpref changes went in. I'm not sure where that is placed in relation to any ATA changes which were done, though. Are the drives now running in ATA 100 mode? Were they running in ATA 100 mode with 4.3? 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 Oct 12 15:50:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-d07.mx.aol.com (imo-d07.mx.aol.com [205.188.157.39]) by hub.freebsd.org (Postfix) with ESMTP id 4AC0137B422 for ; Fri, 12 Oct 2001 15:50:09 -0700 (PDT) Received: from Bsdguru@aol.com by imo-d07.mx.aol.com (mail_out_v31_r1.8.) id n.78.1c154275 (4412) for ; Fri, 12 Oct 2001 18:50:05 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <78.1c154275.28f8cd9d@aol.com> Date: Fri, 12 Oct 2001 18:50:05 EDT Subject: Re: 4-port T1 PCI card with integrated csu/dsu To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG n a message dated 10/12/2001 3:31:00 PM Eastern Daylight Time, LConrad@Go2France.com writes: > We need to accept handoff of 4 x T1 and want to do it with FreeBSD. > > Is there such a card with support in FreeBSD? > > If not, suggestions? > etinc supposedly has a prototype they are working on. I dont know the status however. Ever thought of using an external CSU? Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 15:53:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from winston.freebsd.org (adsl-64-173-15-98.dsl.sntc01.pacbell.net [64.173.15.98]) by hub.freebsd.org (Postfix) with ESMTP id EFB4337B407; Fri, 12 Oct 2001 15:53:15 -0700 (PDT) Received: from localhost (jkh@localhost [127.0.0.1]) by winston.freebsd.org (8.11.6/8.11.6) with ESMTP id f9CMqiH71836; Fri, 12 Oct 2001 15:52:44 -0700 (PDT) (envelope-from jkh@freebsd.org) To: mjacob@feral.com Cc: jrossiter@symantec.com, sos@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Severe I/O Problems In-Reply-To: <20011012152458.E73308-100000@wonky.feral.com> References: <20011012152458.E73308-100000@wonky.feral.com> X-Mailer: Mew version 1.94.1 on Emacs 20.7 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20011012155244Q.jkh@freebsd.org> Date: Fri, 12 Oct 2001 15:52:44 -0700 From: Jordan Hubbard X-Dispatcher: imput version 20000228(IM140) Lines: 127 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Erm, this would make this the first report of "interference effects" I've ever heard, certainly. Doesn't make it untrue, just subject to a bit more initial skepticism. Is this truly the only variable that's changing? Are we sure that the drives in question aren't simply broken in some way and manifesting this behavior as an aberration among IDE drives? Have different manufacturer's units been involved in cross-testing? Thanks. - Jordan > > Interesting. If this bears out, what this tells me is that in some cases > enabling write cacheing on ATAs is good, but in other cases, bad (probably > provides interference effects). > > Soren? Jordan? > > -matt > > > On Fri, 12 Oct 2001, Jay Rossiter wrote: > > > > > > > This does seem to be doing some good. The beginning of the test run > > is hovering ~30% CPU. I'll have to wait until it finished before I can > > see if it effected the overall time, though. > > > > Something else that I forgot to mention, is that yesterday I did a > > profiled run, and the code-time between the two scenarios differs by less > > than ten minutes. (The in-memory files vs. on disk files) The disk files > > just take infinitely longer to do anything to. > > > > > > > > > > > > Matthew Jacob > > > > com> cc: > > Subject: Re: Severe I/O Problems > > 10/12/2001 > > 02:57 PM > > Please respond > > to mjacob > > > > > > > > > > > > > > > > Hmm. Interesting. What's the state of the ATA write caching bit? > > (sysctl hw.ata.wc)? > > > > If it is set to 1, try setting it to 0 in /boot/loader.conf > > (e.g., add > > > > hw.ata.wc=0 > > > > ) > > > > to /boot/loader.conf > > > > -matt > > > > > > On Fri, 12 Oct 2001, Jay Rossiter wrote: > > > > > > > > Someone on -questions recommended that I forward this over here for > > > you guys to look at. (I'm not subbed to this list) > > > > > > There appear to be a lot of changes that went into the filesystem and I/O > > > code between 4.3 and 4.4. A little over a week ago I upgraded my 4.3 box > > > to 4.4-STABLE and immediately I started having I/O slowdown. I do > > > development and QA on a program that is very I/O bound, but the changes > > > between 4.3 and 4.4 aren't small enough that I can ignore them. > > > > > > A few statistics: > > > > > > BSD, P4 1.4GHz, ATA100 drives > > > - Normal test run on 4.3 was taking ~3 hours. > > > - Normal test run on 4.4 is taking 15-16 hours. > > > > > > P3-800, ATA66 drives, SuSE Linux 7.1: > > > - Normal test run takes ~4.5 hours. > > > > > > UltraSparc 10, Solaris 8, ATA66 drives: > > > - Normal test run takes ~6 hours. > > > > > > As you can see, this jump was just phenomenal. > > > > > > I can run these tests on a custom 'ramdrive' and the test run takes 1.5 > > > hours on BSD. ~4 on Solaris, ~2.5 on Linux. > > > > > > Even the RS/6000 I test AIX 4.3 with doesn't take this long, though I > > don't > > > have statistics for it. > > > > > > It appears that the app gets stuck switching between the getblk and biowr > > > states in top and ps, and very rarely does it take more than 5% of the > > CPU. > > > On all other OS's, and even on 4.3, this app was pegging the CPU while it > > > did its work. > > > > > > Basically.. this all comes down to "What the hell is going on here?!" and > > > "Are there plans to fix it and did anyone even know there was a problem?" > > > > > > --- > > > Jay Rossiter 503-614-7917 > > > QA Engineer, Test Lead > > > Symantec Corp. > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 15:58:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id EA9D937B401; Fri, 12 Oct 2001 15:58:09 -0700 (PDT) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f9CMw9H93801; Fri, 12 Oct 2001 15:58:09 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 12 Oct 2001 15:58:09 -0700 (PDT) From: Matthew Jacob Reply-To: To: Jordan Hubbard Cc: , , Subject: Re: Severe I/O Problems In-Reply-To: <20011012155244Q.jkh@freebsd.org> Message-ID: <20011012155746.R73308-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sure- all these are excellent questions! On Fri, 12 Oct 2001, Jordan Hubbard wrote: > Erm, this would make this the first report of "interference effects" > I've ever heard, certainly. Doesn't make it untrue, just subject to a > bit more initial skepticism. Is this truly the only variable that's > changing? Are we sure that the drives in question aren't simply > broken in some way and manifesting this behavior as an aberration > among IDE drives? Have different manufacturer's units been involved > in cross-testing? Thanks. > > - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 17:25:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from tholian.securitydynamics.com (mail.rsasecurity.com [204.167.112.129]) by hub.freebsd.org (Postfix) with SMTP id 83DC337B403 for ; Fri, 12 Oct 2001 17:25:40 -0700 (PDT) Received: from sdtihq24.securitydynamics.com by tholian.securitydynamics.com via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 13 Oct 2001 00:22:23 UT Received: from ebola.securitydynamics.com (ebola.securid.com [192.168.7.4]) by sdtihq24.securid.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id UAA16105 for ; Fri, 12 Oct 2001 20:25:35 -0400 (EDT) Received: from spirit.dynas.se (localhost [127.0.0.1]) by ebola.securitydynamics.com (8.9.3+Sun/8.9.1) with SMTP id UAA23086 for ; Fri, 12 Oct 2001 20:25:33 -0400 (EDT) Received: (qmail 25713 invoked from network); 13 Oct 2001 00:25:32 -0000 Received: from explorer.rsa.com (HELO mikko.rsa.com) (10.81.217.59) by spirit.dynas.se with SMTP; 13 Oct 2001 00:25:32 -0000 Received: (from mikko@localhost) by mikko.rsa.com (8.11.6/8.11.6) id f9D0PT562604; Fri, 12 Oct 2001 17:25:29 -0700 (PDT) (envelope-from mikko) Date: Fri, 12 Oct 2001 17:25:29 -0700 (PDT) From: Mikko Tyolajarvi Message-Id: <200110130025.f9D0PT562604@mikko.rsa.com> To: jrossiter@symantec.com Cc: hackers@freebsd.org Subject: Re: Severe I/O Problems Newsgroups: local.freebsd.hackers References: X-Newsreader: NN version 6.5.6 (NOV) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In local.freebsd.hackers you write: >There appear to be a lot of changes that went into the filesystem and I/O >code between 4.3 and 4.4. A little over a week ago I upgraded my 4.3 box >to 4.4-STABLE and immediately I started having I/O slowdown. I do >development and QA on a program that is very I/O bound, but the changes >between 4.3 and 4.4 aren't small enough that I can ignore them. >A few statistics: >BSD, P4 1.4GHz, ATA100 drives >- Normal test run on 4.3 was taking ~3 hours. >- Normal test run on 4.4 is taking 15-16 hours. >P3-800, ATA66 drives, SuSE Linux 7.1: >- Normal test run takes ~4.5 hours. >UltraSparc 10, Solaris 8, ATA66 drives: >- Normal test run takes ~6 hours. >As you can see, this jump was just phenomenal. Yup, sure looks bad. Post output from at least: % dmesg | grep ata % sysctl -a | grep ata % mount | grep ufs to give people something more to go on. $.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 Fri Oct 12 18:32:18 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m10.mx.aol.com (imo-m10.mx.aol.com [64.12.136.165]) by hub.freebsd.org (Postfix) with ESMTP id C244C37B403 for ; Fri, 12 Oct 2001 18:32:15 -0700 (PDT) Received: from Bsdguru@aol.com by imo-m10.mx.aol.com (mail_out_v31_r1.8.) id a.26.1caecb25 (4413); Fri, 12 Oct 2001 21:32:06 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <26.1caecb25.28f8f396@aol.com> Date: Fri, 12 Oct 2001 21:32:06 EDT Subject: Re: 4-port T1 PCI card with integrated csu/dsu To: LConrad@go2france.com Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 10/12/01 7:04:57 PM Eastern Daylight Time, LConrad@Go2France.com writes: > >etinc supposedly has a prototype they are working on. I dont know the status > >however. > > they already have the 4-port PCISYNC card, but it has no integrated > csu/dsu, requiring $2500 like this > http://www.kentrox.com/products/datasmart_max_t1qpad/index.asp > > sbei.com has single-port PCI cards with on-board csu/dsu. I could run 4 or > 6 of those. and they support FreeBSD. > and whats the price of that? I think etinc told me theirs will be 2495. B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 21:33:16 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id AE03637B407 for ; Fri, 12 Oct 2001 21:33:11 -0700 (PDT) Received: (qmail 2840 invoked by uid 1165); 13 Oct 2001 04:33:11 -0000 Date: 12 Oct 2001 21:33:11 -0700 Date: Fri, 12 Oct 2001 21:33:11 -0700 From: Seth Kingsley To: Peter Pentchev Cc: Mike Meyer , hackers@freebsd.org Subject: Re: My contributions to the close a PR campaign Message-ID: <20011012213311.A95968@fluff.meowfishies.com> References: <15301.63455.964624.626361@guru.mired.org> <200110112245.f9BMjAS66764@gits.dyndns.org> <15302.12256.96805.125719@guru.mired.org> <20011012100527.B78786@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="k+w/mQv8wyuph6w0" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011012100527.B78786@straylight.oblivion.bg>; from roam@ringlet.net on Fri, Oct 12, 2001 at 10:05:27AM +0300 X-Operating-System: FreeBSD 4.4-STABLE i386 X-GPG-Key-ID: 1024D/5C413B08 X-GPG-Key-Fingerprint: F772 5D24 02B4 D233 90F5 080F 0F50 3298 5C41 3B08 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --k+w/mQv8wyuph6w0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Oct 12, 2001 at 10:05:27AM +0300, Peter Pentchev wrote: > I have just one question: would it be > wise to have /var/db/mixer-state removed upon port deinstall, or should > it be left behind, just in case? Why not remove it after using it to restore the mixer state? It would only exist to survive a reboot. --=20 || Seth Kingsley || Meow Meow Fluff Fluff || sethk@meowfishies.com || --k+w/mQv8wyuph6w0 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.6 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE7x8QHD1AymFxBOwgRAhzcAJ0bKPnjMAGkEUlHElL31zhosxxePQCdGjrx KIwH7VAEK0D97MDWBDNhDHw= =OOhF -----END PGP SIGNATURE----- --k+w/mQv8wyuph6w0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 22:24: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 32E4F37B403 for ; Fri, 12 Oct 2001 22:23:59 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9D5NuT07495; Fri, 12 Oct 2001 22:23:56 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: Cc: Subject: RE: Imagestream WanIC-520 interface cards Date: Fri, 12 Oct 2001 22:23:55 -0700 Message-ID: <000401c153a7$409d9ec0$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <103.a728861.28f84948@aol.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Bsdguru@aol.com [mailto:Bsdguru@aol.com] >Sent: Friday, October 12, 2001 6:25 AM >To: tedm@toybox.placo.com >Cc: hackers@freebsd.org >Subject: Re: Imagestream WanIC-520 interface cards > > >In a message dated 10/12/01 1:08:44 AM Eastern Daylight Time, >tedm@toybox.placo.com writes: > >> Consider that the Hitachi controller chip used on the WANic 405 is the >> SAME chip that Cisco uses in it's 25xx series of routers, and the Cisco >> 2501 is the most used router in the world and has the most installed >> units. >> >> SBS Communications is STILL selling the RISCom series of cards which is >> the predecessor to the WANic, uses the same controller, these are >ISA cards >> that have a design that's over 10 years old. >> >> You tell your supplier that since the 405 is being "phased out" that he >> should sell you a bunch of them at closeout prices. >> > >Perhaps the fact that the (incredibly slow) 2501 has been >phased out has caused Hitachi to "phase out" their part? You know I really think your baiting me. You know perfectly well that Hitachi and Cisco are not the same company. Anyway, Cisco is still selling the 2501 router, (although list on it is $2600 and nobody buying it for a single connection to the Internet would buy it new) I just logged into their reseller's website and the 2501 is still readily available. And as far as speed of the router, yes the 2501 is incredibly slow. So what? This has absolutely nothing whatsover to do with the HD64570 controller chip which is rated to 7Mbts. The 2501 is slow because it has a 20Mhz Motorola 68000 series CPU, not because the serial controller chip is slow. >You know, big chip >vendors have bigger fish to fry than the WanIC series. I don't understand why your spreading FUD when a few minutes work on the Hitachi website could answer your question. Hitachi Semiconductors manufacturers thousands of semiconductors and many have much smaller markets than this. A check on their website shows this contoller still available. In fact the most recent documents are dated 1998. Trust me they still know that this chip exists. And anyway, as long as there are customers for the controller chip then someone out there will buy the design and continue to manufacture the chip. After all AMD is still selling 8088 CPU variants for the embedded market. >HDLC controllers that >can barely run 2 T1s are not mainstream these days, so they may just >not want >to make it anymore. First of all, it takes one HD64570 per port, not two. The HD64570 is not a dual ported chip. And secondly the chip is perfectly capabable of running at a T1 speed and in fact much faster. It's all a pricing issue. SBS Communications (manufacturer of the WANic) is going to manufacture these cards until they can't sell enough of them to make a profit anymore - since they haven't said they are stopping making them, that's proof they are still profitable. If they start having trouble sourcing the controller from Hitachi and there's still sufficient interest in the market then they will just approach another chip manufacturer and that one will buy the controller design from Hitachi. >If you think that Hitachi cares that there are "open >source" drivers in use in what they would consider a handful of >applications, >you dont understand the chip business. When cisco goes away, they find a >better use for their foundry. > Everything your saying seems to indicate that your the one that doesen't understand the chip business. For starters, a chip foundry that is set up for manufacture of this controller could never manufacture more modern chips without being completely razed and rebuilt. Secondly, chip foundaries don't operate like this. What happens is that Hitachi has made this chip before, so they know that their cheapest price point to make the chip is to set up a production run of, say, 15,000 devices that takes 2 weeks to run. So they simply monitor inventory and as long as the product is moving out of the warehouse, they simply wait until they are down to, say 500 devices, then at that time they schedule another run of the controller chip in the foundry. That run completes, the warehouse is replentished, and they then turn the foundry over to work on a different chip design for some other product. All Hitachi cares about is that there's customers still buying the controller, and as long as there are they will make the chip. Consider also that this is a general purpose synchronous serial controller and can be used in a lot of applications other than just T1's. What all this discussion is boiling down to IMHO is Imagestream - because they sell the WANic+driver package to ISP's that are attempting to build routers out of PC's. They have Linux drivers for the more expensive WANic cards so of course they have a vested interest in seeing the WANic 405 go away, because SBS allows any reseller to register with them to sell the WANic cards and when someone like Joe Blow Computers fills out the paperwork and start selling WANic405 cards on FreeBSD boxes as routers, Imagestream sees it cutting into their Linux/expensive WANic router business. The rumor that the WANic405 is going away is totally unsubstantiated by the facts and if it ever did then Linux would see immediate benefit because the FreeBSD OS would end up losing one more of the few cards that it has that supports a T1. So consider who it is that has a vested interest in spreading this kind of FUD. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 22:40:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id CAEFB37B403 for ; Fri, 12 Oct 2001 22:40:32 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f9D5eQW38618; Fri, 12 Oct 2001 22:40:26 -0700 (PDT) (envelope-from dillon) Date: Fri, 12 Oct 2001 22:40:26 -0700 (PDT) From: Matt Dillon Message-Id: <200110130540.f9D5eQW38618@earth.backplane.com> To: "Ted Mittelstaedt" Cc: , Subject: Re: RE: Imagestream WanIC-520 interface cards References: <000401c153a7$409d9ec0$1401a8c0@tedm.placo.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The Cisco 2600 series is great for T1's. A 2620 with a T1 card (it can take up to two) and you are done. The 2501's are ancient, don't even bother any more. You can find 2620's on EBay in the $700-$1500 range, many of which appear (in my quick look) to include a T1 card. As much as I like to support running things on BSD, I stopped trying to run T1's from general purpose unix boxes 4 years ago. When BEST Internet first started we ran the (old) Riscom cards from a BSDI box w/ an external csu/dsu, and they were great for that, but these days the overall cost of ownership is much, much lower with a used cisco and a WAN card with an integrated csu/dsu in it. It's file and forget... once you set the thing up you don't have to touch it ever again. One advantage of the dot-com crash is that EBay and other sites are saturated with high quality, barely used hardware. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Oct 12 23:51:49 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 9CF2237B403 for ; Fri, 12 Oct 2001 23:51:46 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9D6pUa23806; Sat, 13 Oct 2001 08:51:30 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bsdguru@aol.com Cc: LConrad@go2france.com, hackers@FreeBSD.ORG Subject: Re: 4-port T1 PCI card with integrated csu/dsu In-Reply-To: Your message of "Fri, 12 Oct 2001 21:32:06 EDT." <26.1caecb25.28f8f396@aol.com> Date: Sat, 13 Oct 2001 08:51:30 +0200 Message-ID: <23804.1002955890@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <26.1caecb25.28f8f396@aol.com>, Bsdguru@aol.com writes: >> sbei.com has single-port PCI cards with on-board csu/dsu. I could run 4 >or >> 6 of those. and they support FreeBSD. They also have a 4 port card which is supported by FreeBSD (but discontinued) and a new card which could trivially be modified to run under FreeBSDs driver, but so far they have not sent me a card... etinc is not recommendable. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 0:31:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id A3FBB37B407 for ; Sat, 13 Oct 2001 00:31:42 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9D7VXa24205; Sat, 13 Oct 2001 09:31:33 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Len Conrad Cc: FReebsd-hackers@FreeBSD.ORG Subject: Re: anybody working on a driver for this multi-T1 card? In-Reply-To: Your message of "Fri, 12 Oct 2001 17:01:18 CDT." <5.1.0.14.0.20011012165857.00bd8170@mail.Go2France.com> Date: Sat, 13 Oct 2001 09:31:33 +0200 Message-ID: <24203.1002958293@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <5.1.0.14.0.20011012165857.00bd8170@mail.Go2France.com>, Len Conrad writes: > >http://www.sbei.net/hw400p.htm I am pretty sure that the musycc driver in FreeBSD almost supports this card. This is the SBE card which almost matches the old LMC 1504 card. I've tried to make them send me one so I could adapt the driver but no such luck yet. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 1:52: 5 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snark.rinet.ru (snark.rinet.ru [195.54.192.73]) by hub.freebsd.org (Postfix) with ESMTP id 215C937B40B; Sat, 13 Oct 2001 01:51:57 -0700 (PDT) Received: (from yar@localhost) by snark.rinet.ru (8.11.6/8.11.6) id f9D8pp594569; Sat, 13 Oct 2001 12:51:51 +0400 (MSD) (envelope-from yar) Date: Sat, 13 Oct 2001 12:51:51 +0400 From: Yar Tikhiy To: Terry Lambert Cc: hackers@freebsd.org, doc@freebsd.org Subject: Re: utmp(5) manpage revised Message-ID: <20011013125151.A93286@snark.rinet.ru> References: <20011011170226.A2162@snark.rinet.ru> <3BC736E5.2AF183F4@mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3BC736E5.2AF183F4@mindspring.com> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Thank you Terry for your comments! On Fri, Oct 12, 2001 at 11:31:01AM -0700, Terry Lambert wrote: > Yar Tikhiy wrote: > > > > The current utmp(5) manpage language (not markup) > > has a number of drawbacks and errors: > > > > o There is no information for programmers on the actual structure > > of the files the page describes. > > It is opaque. You are not supposed to access it directly, you > are supposed to use library routines. You could make the same > argument about "db" files... There are no library functions to manage the lastlog file yet, so at least this file's structure should be documented. Why not to stay consistent and document the two other files granted that their structure can be described in a sentence or two? > > o The C structure members aren't described. > > "" The C data structures aren't opaque that much either. The lastlog file is still managed directly, and the login(3) function takes a pointer to "struct utmp". > > o It describes in a wrong way how a user's logout is recorded to wtmp. > > I'm not sure that that's not an implementation detail that > should be reomved from the man page entirely, but what you've > done is equally valid. No it shouldn't. The authors of applications similar to SSH or telnetd need to know how to record user logouts. Of course, nobody is likely to start an alternative network terminal access project within the next few years, but... :-) > > Here's a patch addressing all the issues. Review it please. > > I'm not sure that the structure should be documented, as it > will encourage people to access the data directly. The point > of having them access it through library routines is that it's > possible to replace the implementation by replacing the libc.so > on a system, and have software continue to function. Or, it's > possible to install binaries that use libc.so on a system with > a different underlying implementaiton, and have them "just work" > for commercial vendors. FreeBSD is an open system, so IMHO people would be better discouraged of accessing the files directly by a paragraph in the manpage, which reads: "Don't do it, or this or that trouble will happen because of the following reason...". -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 2: 5:35 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snark.rinet.ru (snark.rinet.ru [195.54.192.73]) by hub.freebsd.org (Postfix) with ESMTP id 82F3A37B40B for ; Sat, 13 Oct 2001 02:05:32 -0700 (PDT) Received: (from yar@localhost) by snark.rinet.ru (8.11.6/8.11.6) id f9D95AH95001; Sat, 13 Oct 2001 13:05:10 +0400 (MSD) (envelope-from yar) Date: Sat, 13 Oct 2001 13:05:10 +0400 From: Yar Tikhiy To: Peter Pentchev Cc: Warner Losh , hackers@FreeBSD.ORG Subject: Re: Valid user name Message-ID: <20011013130510.B93286@snark.rinet.ru> References: <20011012145227.D46577@snark.rinet.ru> <200110121552.f9CFqA793345@harmony.village.org> <20011012192457.A74895@straylight.oblivion.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011012192457.A74895@straylight.oblivion.bg> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Fri, Oct 12, 2001 at 07:24:57PM +0300, Peter Pentchev wrote: > On Fri, Oct 12, 2001 at 09:52:10AM -0600, Warner Losh wrote: > > In message <20011012145227.D46577@snark.rinet.ru> Yar Tikhiy writes: > > : Is there any reason to omit the period ('.') from the list of valid > > : characters? With the period included, the list would conform to > > : POSIX's definition of a valid user name. > > > > Not any more. it used to be that chown user.group would be > > ambiguous. now it isn't, since user:group is the right syntax. > > This might be a problem for NIS or Kerberos domains - an older version > of FreeBSD might be confuzzled by usernames which are perfectly valid > for the rest of the client boxes. Oh, I see. Given that the only issue about the period in user names is compatibility, should pw(8) and adduser(8) still reject it or accept it and print a warning? I think printing a warning is better since the validity check is by no means a panacea--a stupid admin can always use vipw(8) to create any kind of an invalid user name. -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 2:32:47 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from harrier.mail.pas.earthlink.net (harrier.mail.pas.earthlink.net [207.217.121.12]) by hub.freebsd.org (Postfix) with ESMTP id 2DB4E37B40B; Sat, 13 Oct 2001 02:32:45 -0700 (PDT) Received: from blossom.cjclark.org (dialup-209.245.143.238.Dial1.SanJose1.Level3.net [209.245.143.238]) by harrier.mail.pas.earthlink.net (EL-8_9_3_3/8.9.3) with ESMTP id CAA23778; Sat, 13 Oct 2001 02:32:02 -0700 (PDT) Received: (from cjc@localhost) by blossom.cjclark.org (8.11.6/8.11.3) id f9D9VHv08133; Sat, 13 Oct 2001 02:31:17 -0700 (PDT) (envelope-from cjc) Date: Sat, 13 Oct 2001 02:30:50 -0700 From: "Crist J. Clark" To: Yar Tikhiy Cc: Peter Pentchev , Warner Losh , hackers@FreeBSD.ORG Subject: Re: Valid user name Message-ID: <20011013023050.L6274@blossom.cjclark.org> Reply-To: cjclark@alum.mit.edu References: <20011012145227.D46577@snark.rinet.ru> <200110121552.f9CFqA793345@harmony.village.org> <20011012192457.A74895@straylight.oblivion.bg> <20011013130510.B93286@snark.rinet.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011013130510.B93286@snark.rinet.ru>; from yar@FreeBSD.ORG on Sat, Oct 13, 2001 at 01:05:10PM +0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Oct 13, 2001 at 01:05:10PM +0400, Yar Tikhiy wrote: > On Fri, Oct 12, 2001 at 07:24:57PM +0300, Peter Pentchev wrote: > > On Fri, Oct 12, 2001 at 09:52:10AM -0600, Warner Losh wrote: > > > In message <20011012145227.D46577@snark.rinet.ru> Yar Tikhiy writes: > > > : Is there any reason to omit the period ('.') from the list of valid > > > : characters? With the period included, the list would conform to > > > : POSIX's definition of a valid user name. > > > > > > Not any more. it used to be that chown user.group would be > > > ambiguous. now it isn't, since user:group is the right syntax. > > > > This might be a problem for NIS or Kerberos domains - an older version > > of FreeBSD might be confuzzled by usernames which are perfectly valid > > for the rest of the client boxes. > > Oh, I see. Given that the only issue about the period in user names > is compatibility, should pw(8) and adduser(8) still reject it or accept > it and print a warning? I think printing a warning is better since > the validity check is by no means a panacea--a stupid admin can always > use vipw(8) to create any kind of an invalid user name. That arguement goes both ways. They can use vipw(8) or they can edit master.passwd directly if they insist on living dangerously. They can even hack pw(8) or adduser(8) if they want. But no reason to let pw(8) or adduser(8) fsck up their systems for them. After all, tools like adduser(8) are aimed more towards the inexperienced admin. If any administrative apps are going to do hand-holding, adduser(8) is one of them. -- Crist J. Clark | cjclark@alum.mit.edu | cjclark@jhu.edu http://people.freebsd.org/~cjc/ | cjc@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 Oct 13 3:10:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from snark.rinet.ru (snark.rinet.ru [195.54.192.73]) by hub.freebsd.org (Postfix) with ESMTP id A541637B407 for ; Sat, 13 Oct 2001 03:10:30 -0700 (PDT) Received: (from yar@localhost) by snark.rinet.ru (8.11.6/8.11.6) id f9DAAKW96835; Sat, 13 Oct 2001 14:10:20 +0400 (MSD) (envelope-from yar) Date: Sat, 13 Oct 2001 14:10:20 +0400 From: Yar Tikhiy To: cjclark@alum.mit.edu Cc: Peter Pentchev , Warner Losh , hackers@FreeBSD.ORG Subject: Re: Valid user name Message-ID: <20011013141020.D93286@snark.rinet.ru> References: <20011012145227.D46577@snark.rinet.ru> <200110121552.f9CFqA793345@harmony.village.org> <20011012192457.A74895@straylight.oblivion.bg> <20011013130510.B93286@snark.rinet.ru> <20011013023050.L6274@blossom.cjclark.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011013023050.L6274@blossom.cjclark.org> User-Agent: Mutt/1.3.22.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Oct 13, 2001 at 02:30:50AM -0700, Crist J. Clark wrote: > On Sat, Oct 13, 2001 at 01:05:10PM +0400, Yar Tikhiy wrote: > > On Fri, Oct 12, 2001 at 07:24:57PM +0300, Peter Pentchev wrote: > > > On Fri, Oct 12, 2001 at 09:52:10AM -0600, Warner Losh wrote: > > > > In message <20011012145227.D46577@snark.rinet.ru> Yar Tikhiy writes: > > > > : Is there any reason to omit the period ('.') from the list of valid > > > > : characters? With the period included, the list would conform to > > > > : POSIX's definition of a valid user name. > > > > > > > > Not any more. it used to be that chown user.group would be > > > > ambiguous. now it isn't, since user:group is the right syntax. > > > > > > This might be a problem for NIS or Kerberos domains - an older version > > > of FreeBSD might be confuzzled by usernames which are perfectly valid > > > for the rest of the client boxes. > > > > Oh, I see. Given that the only issue about the period in user names > > is compatibility, should pw(8) and adduser(8) still reject it or accept > > it and print a warning? I think printing a warning is better since > > the validity check is by no means a panacea--a stupid admin can always > > use vipw(8) to create any kind of an invalid user name. > > That arguement goes both ways. They can use vipw(8) or they can edit > master.passwd directly if they insist on living dangerously. They can > even hack pw(8) or adduser(8) if they want. But no reason to let > pw(8) or adduser(8) fsck up their systems for them. After all, tools > like adduser(8) are aimed more towards the inexperienced admin. If any > administrative apps are going to do hand-holding, adduser(8) is one of > them. Good point! However, there's a certain "lobby" of people who need weird chars in user names (e.g. bin/22860 and the followup to it about I18N) and who prefer the automated tools to vipw/mkdir/cp/chown. So what about keeping the strict validity check by default and adding an option to adduser(8) and pw(8) that would turn off the check? BTW, coming to a final conclusion on this issue would help to close a number of problem reports, no matter what the conclusion will be. -- Yar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 6:26:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from segfault.kiev.ua (segfault.kiev.ua [193.193.193.4]) by hub.freebsd.org (Postfix) with ESMTP id 8CDC437B411 for ; Sat, 13 Oct 2001 06:22:43 -0700 (PDT) Received: (from uucp@localhost) by segfault.kiev.ua (8) with UUCP id QIS86992 for hackers@freebsd.org; Sat, 13 Oct 2001 16:22:39 +0300 (EEST) (envelope-from netch@iv.nn.kiev.ua) Received: (from netch@localhost) by iv.nn.kiev.ua (8.11.6/8.11.6) id f9DAwgd07449 for hackers@freebsd.org; Sat, 13 Oct 2001 13:58:42 +0300 (EEST) (envelope-from netch) Date: Sat, 13 Oct 2001 13:58:42 +0300 From: Valentin Nechayev To: hackers@freebsd.org Subject: sin_zero & bind problems Message-ID: <20011013135842.A415@iv.nn.kiev.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-42: On Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The following was initially formatted as PR, but I suppose it is reasonable to discuss first here. There were some vague mentions that sin_zero field of struct sockaddr_in may be used in future for some extensions; but this future is already expired;) without any real step. If the verdict will be to keep current behavior, it should be strictly documented to remove this permanent rake field. >Description: If bind() syscall is called for PF_INET socket with address another than INADDR_ANY, and sin_zero field in addr parameter is not filled with zero (this is common programming problem), bind() will fail. Source of failure is ifa_ifwithaddr() in src/sys/net/if.c, which compares structure contents for all their length (determined from sa_len field). ifa_ifwithaddr() is called by in_pcbbind(), which performs all work of comparing addresses and ports. The good programming style requires filling of all structures, passed to kernel or any subsystem with non-transparent behavoir, with null bytes. Stevens' examples also performs zero-filling before use. But I never saw an _explicit_ rule to perform such filling (all in /usr/share/doc/ and Stevens' books were specially searched). During last month, I saw 4 complaints to opaque and misunderstandable behavior of FreeBSD kernel in this place - 2 from Usenet and 2 from my workmates; in each case, complainer was totally confused: he fills all described fields - sin_family, sin_port and sin_addr - and what hell? ;| The needed fix is too simple, and I supposed it is better to apply it once, than continue to confuse people. That's why I also consider this as software bug, and tagged this report as sw-bug, not change-request. Another mentions found with Google: ==={{{ freebsd-current archive FROM: Mike Smith DATE: 11/25/1997 20:31:19 SUBJECT: RE: tcp/ip buglet ? ===}}} FreeBSD PR kern/9309 by ru@ NetBSD PR kern/2972 >How-To-Repeat: #define FILLER 0xDE #include #include #include #include #include #include #include int main() { int s; struct sockaddr_in sia; s = socket( PF_INET, SOCK_STREAM, 0 ); if( s == -1 ) err( 1, "socket()" ); memset( &sia, FILLER, sizeof sia ); sia.sin_family = AF_INET; sia.sin_port = htons( 4455 ); sia.sin_addr.s_addr = htonl( 0x7f000001 ); if( bind( s, ( struct sockaddr* ) &sia, sizeof sia ) < 0 ) err( 1, "bind()" ); puts( "all ok" ); return 0; } With any FILLER value other than 0, bind() will fail with EADDRNOTAVAIL. Also note than sin_len field is refilled in getsockaddr(), and garbage in it in userland copy does not matter. >Fix: --- src/sys/netinet/in_pcb.c.0 Sat Sep 22 17:41:17 2001 +++ src/sys/netinet/in_pcb.c Sat Sep 22 17:44:59 2001 @@ -198,6 +198,7 @@ sin = (struct sockaddr_in *)nam; if (nam->sa_len != sizeof (*sin)) return (EINVAL); + bzero(&sin->sin_zero, sizeof(sin->sin_zero)); #ifdef notdef /* * We should check the family, but old programs /netch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 7:51:33 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.bsdimp.com [204.144.255.66]) by hub.freebsd.org (Postfix) with ESMTP id E19F637B410; Sat, 13 Oct 2001 07:43:30 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.11.3/8.11.3) with ESMTP id f9DEhTu27815; Sat, 13 Oct 2001 08:43:29 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.11.6/8.11.6) with ESMTP id f9DEhR702842; Sat, 13 Oct 2001 08:43:27 -0600 (MDT) (envelope-from imp@harmony.village.org) Message-Id: <200110131443.f9DEhR702842@harmony.village.org> To: Yar Tikhiy Subject: Re: Valid user name Cc: Peter Pentchev , hackers@FreeBSD.ORG In-reply-to: Your message of "Sat, 13 Oct 2001 13:05:10 +0400." <20011013130510.B93286@snark.rinet.ru> References: <20011013130510.B93286@snark.rinet.ru> <20011012145227.D46577@snark.rinet.ru> <200110121552.f9CFqA793345@harmony.village.org> <20011012192457.A74895@straylight.oblivion.bg> Date: Sat, 13 Oct 2001 08:43:27 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <20011013130510.B93286@snark.rinet.ru> Yar Tikhiy writes: : Oh, I see. Given that the only issue about the period in user names : is compatibility, should pw(8) and adduser(8) still reject it or accept : it and print a warning? I think printing a warning is better since : the validity check is by no means a panacea--a stupid admin can always : use vipw(8) to create any kind of an invalid user name. acccept with warning. the compatibility issue is very very minor. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 8:47:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.huji.ac.il (cs.huji.ac.il [132.65.16.10]) by hub.freebsd.org (Postfix) with ESMTP id 6100F37B411 for ; Sat, 13 Oct 2001 08:43:41 -0700 (PDT) Received: from narn.cs.huji.ac.il ([132.65.80.43] ident=exim) by cs.huji.ac.il with esmtp (Exim 3.32 #1) id 15sQwt-00022l-00 for freebsd-hackers@freebsd.org; Sat, 13 Oct 2001 17:43:39 +0200 Received: from vadik by narn.cs.huji.ac.il with local (Exim 3.32 #1) id 15sQwt-0005XC-00 for freebsd-hackers@freebsd.org; Sat, 13 Oct 2001 17:43:39 +0200 Date: Sat, 13 Oct 2001 17:43:39 +0200 From: Vadim Vygonets To: freebsd-hackers@freebsd.org Subject: loader.conf conditional assignment Message-ID: <20011013174339.A21230@cs.huji.ac.il> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="fUYQa+Pmc3FrFX/N" Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Operating-System: BSD/OS narn.cs.huji.ac.il 4.2 i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: inline We are working on integration of network-booted FreeBSD system to our envoronment. Naturally, different machines need different kernels, so we pass the kernel paramater in DHCP response. However, it gets overwritten in /boot/defaults/loader.conf. We decided that commenting out the assignment of 'kernel' and 'kernel_options' is not what we want, because we want both to use the default value and to be able to override it via DHCP. After taking some time to learn Forth (interesting language, I must say) and a false start (involving saving environment variables (names and values) in a linked list and restoring them after the assignment), I decided to use the Makefile syntax of ?= to set an environment variable if it's not set yet, so it will be possible to say: kernel?="/kernel" In this case, if kernel is set via DHCP, the value is not changed, but if it's not, it becomes "/kernel". Attached is the patch for /boot/support.4th against the version in FreeBSD 4.4. Vadik. -- Bell Labs Unix -- Reach out and grep someone. --fUYQa+Pmc3FrFX/N Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="support.4th.diff" --- ../../4.4/boot/support.4th Thu Aug 9 08:52:20 2001 +++ support.4th Thu Oct 11 20:11:29 2001 @@ -190,6 +190,9 @@ string name_buffer string value_buffer +variable assignment_op +char = constant regular_assignment +char ? constant notdef_assignment \ File data temporary storage @@ -331,6 +334,10 @@ line_pointer c@ [char] = = ; +: question_mark? + line_pointer c@ [char] ? = +; + : comment? line_pointer c@ [char] # = ; @@ -464,8 +471,16 @@ ['] white_space_3 to parsing_function ; +: question_mark + notdef_assignment assignment_op ! + skip_character + assignment_sign? if ['] assignment_sign to parsing_function exit then + syntax_error throw +; + : white_space_2 eat_space + question_mark? if ['] question_mark to parsing_function exit then assignment_sign? if ['] assignment_sign to parsing_function exit then syntax_error throw ; @@ -554,6 +569,10 @@ module_loaderror_suffix suffix_type? ; +: notdef_assignment? + assignment_op @ notdef_assignment = +; + : set_conf_files conf_files .addr @ ?dup if free-memory @@ -717,6 +736,14 @@ then ; +: set_environment_variable_if_notdef + name_buffer .addr @ name_buffer .len @ getenv -1 = if + set_environment_variable + else + drop + then +; + : set_verbose yes_value? to verbose? ; @@ -754,6 +781,7 @@ module_beforeload? if set_module_beforeload exit then module_afterload? if set_module_afterload exit then module_loaderror? if set_module_loaderror exit then + notdef_assignment? if set_environment_variable_if_notdef exit then set_environment_variable ; @@ -775,6 +803,7 @@ 0 name_buffer .len ! 0 value_buffer .addr ! 0 value_buffer .len ! + regular_assignment assignment_op ! ; \ Higher level file processing --fUYQa+Pmc3FrFX/N-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 9:25:17 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from newsguy.com (smtp.newsguy.com [209.155.56.71]) by hub.freebsd.org (Postfix) with ESMTP id C78DE37B410 for ; Sat, 13 Oct 2001 09:21:12 -0700 (PDT) Received: from newsguy.com (ppp232-bsace7002.telebrasilia.net.br [200.181.81.232]) by newsguy.com (8.9.1a/8.9.1) with ESMTP id JAA78785; Sat, 13 Oct 2001 09:20:22 -0700 (PDT) Message-ID: <3BC86AF9.BB1CF2E8@newsguy.com> Date: Sat, 13 Oct 2001 13:25:29 -0300 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.77 [en] (Win98; U) X-Accept-Language: en,pt-BR,pt,en-GB,en-US,ja MIME-Version: 1.0 To: Vadim Vygonets Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: loader.conf conditional assignment References: <20011013174339.A21230@cs.huji.ac.il> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Vadim Vygonets wrote: > > We are working on integration of network-booted FreeBSD system to > our envoronment. Naturally, different machines need different > kernels, so we pass the kernel paramater in DHCP response. > However, it gets overwritten in /boot/defaults/loader.conf. We > decided that commenting out the assignment of 'kernel' and > 'kernel_options' is not what we want, because we want both to use > the default value and to be able to override it via DHCP. > > After taking some time to learn Forth (interesting language, I > must say) and a false start (involving saving environment > variables (names and values) in a linked list and restoring them > after the assignment), I decided to use the Makefile syntax of ?= > to set an environment variable if it's not set yet, so it will be > possible to say: > > kernel?="/kernel" > > In this case, if kernel is set via DHCP, the value is not > changed, but if it's not, it becomes "/kernel". Attached is the > patch for /boot/support.4th against the version in FreeBSD 4.4. Loader.conf's syntax was designed to be such that the files could be processed by sh(1). I rather prefer to keep faithful to that by using the shell expansions tricks sh(1) has. OTOH, that wouldn't be a trivial task to undertake, and I don't have time to do it. Add to that, being able to sh-process loader.conf files is of dubious usefulness. So I do not object to such a change, as long as more people weight in first on this matter. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org capo@the.secret.bsdconspiracy.net wow regex humor... I'm a geek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 10:23: 8 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 5655A37B417 for ; Sat, 13 Oct 2001 10:18:57 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f9DHHLR43887; Sat, 13 Oct 2001 10:17:21 -0700 (PDT) (envelope-from dillon) Date: Sat, 13 Oct 2001 10:17:21 -0700 (PDT) From: Matt Dillon Message-Id: <200110131717.f9DHHLR43887@earth.backplane.com> To: Valentin Nechayev Cc: hackers@FreeBSD.ORG Subject: Re: sin_zero & bind problems References: <20011013135842.A415@iv.nn.kiev.ua> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG : :The following was initially formatted as PR, but I suppose it is reasonable :to discuss first here. There were some vague mentions that sin_zero field :of struct sockaddr_in may be used in future for some extensions; but this :future is already expired;) without any real step. :If the verdict will be to keep current behavior, it should be strictly :documented to remove this permanent rake field. : :>Description: : :If bind() syscall is called for PF_INET socket with address another than :INADDR_ANY, and sin_zero field in addr parameter is not filled with :... Nobody in their right mind uses a struct sockaddr_in or any other struct sock* type of structure without zeroing it first. I suppose we can document that in the man pages, but we certainly should not go hacking up the kernel code to work around bad programmers. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 10:47:21 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.libero.it (smtp2.libero.it [193.70.192.52]) by hub.freebsd.org (Postfix) with ESMTP id 0811D37B40D for ; Sat, 13 Oct 2001 10:47:19 -0700 (PDT) Received: from libero.it (151.33.118.140) by smtp2.libero.it (6.0.021) id 3BC5C21D0009C376 for freebsd-hackers@FreeBSD.ORG; Sat, 13 Oct 2001 19:47:18 +0200 Received: (from flag@localhost) by libero.it (8.11.6/8.11.6) id f9DHn2W38241 for freebsd-hackers@FreeBSD.ORG; Sat, 13 Oct 2001 19:49:02 +0200 (CEST) (envelope-from flag) Date: Sat, 13 Oct 2001 19:49:02 +0200 From: Paolo Pisati To: freebsd-hackers@FreeBSD.ORG Subject: First prg with sysctl Message-ID: <20011013194902.A38183@newluxor.skynet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Useless-Header: Look ma, it's a # sign! X-Operating-System: FreeBSD newluxor.skynet.org 4.4-STABLE FreeBSD 4.4-STABLE Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Someone can tell me why this piece of code doesn't work? #include #include #include #include #include #include #include int main(void) { int mib[5], *count; mib[0]=CTL_NET; mib[1]=PF_LINK; mib[2]=NETLINK_GENERIC; mib[3]=IFMIB_SYSTEM; mib[4]=IFMIB_IFCOUNT; sysctl(mib, 5, count, sizeof(int),(void *)NULL, NULL); printf("count: %d\n",*count); } I'm searching the number of interfaces available. thanks. -- Paolo Visit the Italian FreeBSD User Group Site: www.gufi.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 10:57:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from air.linkclub.or.jp (air.linkclub.or.jp [210.250.19.40]) by hub.freebsd.org (Postfix) with ESMTP id BD92837B40C for ; Sat, 13 Oct 2001 10:57:46 -0700 (PDT) Received: from localhost.jp.FreeBSD.org (1Cust4.tnt1.hanno.jp.da.uu.net [63.12.195.4]) by air.linkclub.or.jp (8.11.4/8.11.4) with ESMTP id f9DHvXW12507 for ; Sun, 14 Oct 2001 02:57:34 +0900 (JST) (envelope-from toshi@jp.FreeBSD.org) Date: Sun, 14 Oct 2001 02:29:35 +0900 (JST) Message-Id: <200110131729.f9DHTZO15603.toshi@jp.FreeBSD.org> From: Toshihiko ARAI To: clefevre@citeweb.net Cc: freebsd-hackers@FreeBSD.org Subject: Re: [patch] extension of newsyslog In-Reply-To: <200110082136.f98LaqW83498@gits.dyndns.org> References: <200110081527.f98FR5A56224.toshi@jp.FreeBSD.org> <200110082136.f98LaqW83498@gits.dyndns.org> X-Mailer: VM 5.96 (beta) / Mule 2.3 (SUETSUMUHANA) based on 19.34.1 Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG + <200110082136.f98LaqW83498@gits.dyndns.org>, Cyrille Lefevre wrote: >> I add script call features to newsyslog. This adds a one field to >> newsyslog.conf. When newsyslog processed log file, this can execute >> arbitrary program. >> >> Situation to assume: >> * For the log file which cannot use signal. >> * Cases to do statistical application for log file. By the way, is there a user needing such a features really? It may not be general besides me. If it is features to be comparatively general, as for it, what specification method is desirable? > it would be interresting to have the possibility to pass optional > args to program. The first patch does not consider it. It specified merely pathname of program. I put a patch of a update version in the following URL. http://people.freebsd.org/~toshi/d/ > also, how about testing for the first (or the last) char to be & > to run the program asynchronously ? Command execution goes by way of /bin/sh in a new patch. Asynchronous execution of program became possible. > much better, always run the program asynchronously so that hanging > programs (who knowns?) don't block the whole process. to do this, > somewhere in main(), add something such as signal(SIGCHLD, SIG_IGN) > and delete the while statment in post_prog(). I added some debug routine, and I tested it. So far a problem does not occur. -- Toshihiko ARAI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 10:58:19 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (wall-gw.polstra.com [206.213.73.130]) by hub.freebsd.org (Postfix) with ESMTP id 044E637B40B for ; Sat, 13 Oct 2001 10:58:14 -0700 (PDT) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.11.3/8.11.3) with ESMTP id f9DHwB826092; Sat, 13 Oct 2001 10:58:12 -0700 (PDT) (envelope-from jdp@wall.polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.11.6/8.11.0) id f9DHwB009026; Sat, 13 Oct 2001 10:58:11 -0700 (PDT) (envelope-from jdp) Date: Sat, 13 Oct 2001 10:58:11 -0700 (PDT) Message-Id: <200110131758.f9DHwB009026@vashon.polstra.com> To: hackers@freebsd.org From: John Polstra Cc: dillon@earth.backplane.com Subject: Re: sin_zero & bind problems In-Reply-To: <200110131717.f9DHHLR43887@earth.backplane.com> References: <20011013135842.A415@iv.nn.kiev.ua> <200110131717.f9DHHLR43887@earth.backplane.com> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article <200110131717.f9DHHLR43887@earth.backplane.com>, Matt Dillon wrote: > Nobody in their right mind uses a struct sockaddr_in or any other > struct sock* type of structure without zeroing it first. That's definitely true in reality, but I'm not sure it's a desirable situation. It runs counter to what POSIX generally requires. For example, if you use sigaction() you only have to set the struct sigaction members that are documented in the spec, even though the structure may have additional members on some platforms. In POSIX the rule is generally that you don't have to set any extra members unless an additional non-standard flag is set (e.g., in sa_flags) indicating that the member is valid. On the other hand (now arguing against myself), I guess by setting sin_len = sizeof(struct sockaddr_in) one is saying that the entire structure is valid, including sin_zero. *Grumble* I wish they had never put the sin_zero member in there in the first place. John -- John Polstra John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 11: 6:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 88ED537B40D for ; Sat, 13 Oct 2001 11:06:32 -0700 (PDT) Received: (from dan@localhost) by dan.emsphone.com (8.11.6/8.11.6) id f9DI6Un67791; Sat, 13 Oct 2001 13:06:30 -0500 (CDT) (envelope-from dan) Date: Sat, 13 Oct 2001 13:06:29 -0500 From: Dan Nelson To: Paolo Pisati Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: First prg with sysctl Message-ID: <20011013130629.A58520@dan.emsphone.com> References: <20011013194902.A38183@newluxor.skynet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20011013194902.A38183@newluxor.skynet.org> User-Agent: Mutt/1.3.23i X-OS: FreeBSD 5.0-CURRENT X-message-flag: Outlook Error Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In the last episode (Oct 13), Paolo Pisati said: > Someone can tell me why this piece of code doesn't work? The sysctl(3) manpage says that arg 4 is a pointer to the length of the storage area pointed to by arg 3. In fact, there's an example in the manpage: mib[0] = CTL_KERN; mib[1] = KERN_MAXPROC; len = sizeof(maxproc); sysctl(mib, 2, &maxproc, &len, NULL, 0); Note: always compile your programs with -Wall. gcc would have flagged this as: test.c:18: warning: passing arg 4 of `sysctl' makes pointer from integer without a cast -- Dan Nelson dnelson@allantgroup.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 11: 9:20 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.yadt.co.uk (yadt.demon.co.uk [158.152.4.134]) by hub.freebsd.org (Postfix) with SMTP id 0A80437B401 for ; Sat, 13 Oct 2001 11:09:13 -0700 (PDT) Received: (qmail 10215 invoked from network); 13 Oct 2001 18:09:09 -0000 Received: from gattaca.local.yadt.co.uk (HELO mail.gattaca.yadt.co.uk) (qmailr@10.0.0.2) by xfiles.yadt.co.uk with SMTP; 13 Oct 2001 18:09:09 -0000 Received: (qmail 29947 invoked by uid 1000); 13 Oct 2001 18:09:09 -0000 Date: Sat, 13 Oct 2001 19:09:09 +0100 From: David Taylor To: Paolo Pisati Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: First prg with sysctl Message-ID: <20011013190909.A29541@gattaca.yadt.co.uk> Mail-Followup-To: Paolo Pisati , freebsd-hackers@FreeBSD.ORG References: <20011013194902.A38183@newluxor.skynet.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20011013194902.A38183@newluxor.skynet.org>; from flag@libero.it on Sat, Oct 13, 2001 at 19:49:02 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, 13 Oct 2001, Paolo Pisati wrote: > > Someone can tell me why this piece of code doesn't work? > > #include > #include > #include > #include > #include > #include > #include > > int main(void) { > int mib[5], *count; Here you define 'count' as an uninitialised pointer to an integer. > mib[0]=CTL_NET; > mib[1]=PF_LINK; > mib[2]=NETLINK_GENERIC; > mib[3]=IFMIB_SYSTEM; > mib[4]=IFMIB_IFCOUNT; > > sysctl(mib, 5, count, sizeof(int),(void *)NULL, NULL); Here, in arg three, you pass the value of 'count' as the address to store the count in, so you're storing it in some random address, probably resulting in -1 being returned with errno=EFAULT. In arg 4, you pass 'sizeof(int)' (probably 4) as the address of a size_t containing the length of the value, also probably resulting in EFAULT. In arg 5, casting NULL to (void *) is somewhat redundant. In arg 6, you probably want to use 0, since the arg isn't a pointer. You also don't check the return value for success/failure. > printf("count: %d\n",*count); You then dereference the random piece of memory. Consider something like: +++ sysctl.c Sat Oct 13 19:08:44 2001 @@ -1,3 +1,4 @@ +#include #include #include #include @@ -7,7 +8,9 @@ #include int main(void) { - int mib[5], *count; + int mib[5]; + int count; + int len; mib[0]=CTL_NET; mib[1]=PF_LINK; @@ -15,8 +18,12 @@ mib[3]=IFMIB_SYSTEM; mib[4]=IFMIB_IFCOUNT; - sysctl(mib, 5, count, sizeof(int),(void *)NULL, NULL); - - printf("count: %d\n",*count); + len = sizeof(int); + if (sysctl(mib, 5, &count, &len, NULL, 0) == -1) + { + perror("sysctl"); + exit(1); + } + printf("count: %d\n",count); } -- David Taylor davidt@yadt.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 11:57:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-m06.mx.aol.com (imo-m06.mx.aol.com [64.12.136.161]) by hub.freebsd.org (Postfix) with ESMTP id D130637B40A for ; Sat, 13 Oct 2001 11:57:09 -0700 (PDT) Received: from Bsdguru@aol.com by imo-m06.mx.aol.com (mail_out_v31_r1.8.) id s.165.24c83ab (4242); Sat, 13 Oct 2001 14:56:57 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <165.24c83ab.28f9e878@aol.com> Date: Sat, 13 Oct 2001 14:56:56 EDT Subject: Re: Imagestream WanIC-520 interface cards To: tedm@toybox.placo.com Cc: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 10/13/2001 1:24:14 AM Eastern Daylight Time, tedm@toybox.placo.com writes: > >> You tell your supplier that since the 405 is being "phased out" that he > >> should sell you a bunch of them at closeout prices. > >> > > > >Perhaps the fact that the (incredibly slow) 2501 has been > >phased out has caused Hitachi to "phase out" their part? > > You know I really think your baiting me. You know perfectly well that > Hitachi and Cisco are not the same company. Anyway, Cisco is still > selling the 2501 router, (although list on it is $2600 and nobody buying > it for a single connection to the Internet would buy it new) I just > logged into their reseller's website and the 2501 is still readily available. > I dont have to "bait" you..but you dont seem to "get" it. Cisco isnt manufacturing 2501s anymore, so they areent buying ICs from Hitachi anymore (I dont know where you get this "same company" stuff). Cisco may have stopped buying them years ago. Often when a chip manufacturer loses their main customer, they discontinue the part for newer parts, or often when they upgrade their foundries to new processes they can no longer make older parts, and its not cost-effective to rework them. I only suggested that a card vendor is not in control of this, so it may not be their choice that a card is being "phased out". When you buy ICs you get a notice a year in advance that the part is being phased out. You are arguing a point without any facts, and Im merely suggesting a scenario in which your "logic" doesnt work. Take if for what its worth. Im sure you dont understand the opportunity costs that Hitachi has related to their foundry capacities. B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 12: 0:48 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 72EB437B40B; Sat, 13 Oct 2001 12:00:40 -0700 (PDT) Received: from mailhost.feral.com (mjacob@mailhost.feral.com [192.67.166.1]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f9DJ0dH01847; Sat, 13 Oct 2001 12:00:39 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sat, 13 Oct 2001 12:00:39 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@beppo Reply-To: mjacob@feral.com To: Jordan Hubbard Cc: jrossiter@symantec.com, sos@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: Severe I/O Problems In-Reply-To: <20011012155746.R73308-100000@wonky.feral.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > > Erm, this would make this the first report of "interference effects" > > I've ever heard, certainly. Doesn't make it untrue, just subject to a > > bit more initial skepticism. Is this truly the only variable that's > > changing? Are we sure that the drives in question aren't simply > > broken in some way and manifesting this behavior as an aberration > > among IDE drives? Have different manufacturer's units been involved > > in cross-testing? Thanks. > > > > - Jordan Just following up myself on this... with a drive on my PC164 Alpha, the realtime difference between two different checkouts of cvs src is interesting: ------------- Script started on Sat Oct 13 10:07:07 2001 farrago.feral.com > # this is with wc off farrago.feral.com > /usr/bin/time cvs -q -d /home/ncvs co src > LOG 2478.99 real 201.48 user 1046.87 sys farrago.feral.com > exit exit Script done on Sat Oct 13 10:55:36 2001 Script started on Sat Oct 13 11:04:06 2001 farrago.feral.com > # this is with wc on farrago.feral.com > /usr/bin/time cvs -q -d /home/ncvs co src > LOG 2866.82 real 199.92 user 988.24 sys farrago.feral.com > exit exit Script done on Sat Oct 13 11:57:51 2001 ------------- All parameters were not totally lab controlled, but pretty close. I'd call it significant enough that I'll leave WC off for this machine. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 12: 8:59 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r05.mx.aol.com (imo-r05.mx.aol.com [152.163.225.101]) by hub.freebsd.org (Postfix) with ESMTP id 972EE37B409 for ; Sat, 13 Oct 2001 12:08:56 -0700 (PDT) Received: from Bsdguru@aol.com by imo-r05.mx.aol.com (mail_out_v31_r1.8.) id n.134.3014468 (4242) for ; Sat, 13 Oct 2001 15:08:51 -0400 (EDT) From: Bsdguru@aol.com Message-ID: <134.3014468.28f9eb43@aol.com> Date: Sat, 13 Oct 2001 15:08:51 EDT Subject: Re: 4-port T1 PCI card with integrated csu/dsu To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 139 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 10/13/2001 2:51:55 AM Eastern Daylight Time, phk@critter.freebsd.dk writes: > >> sbei.com has single-port PCI cards with on-board csu/dsu. I could run 4 > >or > >> 6 of those. and they support FreeBSD. > > They also have a 4 port card which is supported by FreeBSD (but discontinued) > > and a new card which could trivially be modified to run under FreeBSDs > driver, but so far they have not sent me a card... > > etinc is not recommendable. > Everyone knows that PHK has a grudge against etinc. How childish. Their stuff is so superior to what stock freebsd has. One company i worked for has 2 T3s load balanced and its doing traffic prioritization of 20K pps on average with their integrated bandwidth manager. Its been up for months. Lanmedia gear was choking on 1 T3 in the same machine. dennis can be brusk, but he knows WAN better than anyone I've ever worked with or for. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 12:15:25 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by hub.freebsd.org (Postfix) with ESMTP id 4056037B409 for ; Sat, 13 Oct 2001 12:15:22 -0700 (PDT) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.6/8.11.6) with ESMTP id f9DJFBa29723; Sat, 13 Oct 2001 21:15:11 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bsdguru@aol.com Cc: hackers@FreeBSD.ORG Subject: Re: 4-port T1 PCI card with integrated csu/dsu In-Reply-To: Your message of "Sat, 13 Oct 2001 15:08:51 EDT." <134.3014468.28f9eb43@aol.com> Date: Sat, 13 Oct 2001 21:15:11 +0200 Message-ID: <29721.1003000511@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In message <134.3014468.28f9eb43@aol.com>, Bsdguru@aol.com writes: >> etinc is not recommendable. >> > >Everyone knows that PHK has a grudge against etinc. How childish. No, I don't have a grudge against Dennis or Etinc, I merely point out that somebody who has caused so much grief in our mailing lists without ever actually submitting one single diff to us is not a (re)commendable supplier. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 12:18:27 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from milliways.chance.ru (milliways.chance.ru [195.190.107.35]) by hub.freebsd.org (Postfix) with ESMTP id F2F4337B403 for ; Sat, 13 Oct 2001 12:18:22 -0700 (PDT) Received: from do-labs.spb.ru (ppp-2.chance.ru [195.190.107.5]) by milliways.chance.ru (8.9.0/8.9.0) with SMTP id XAA04957 for ; Sat, 13 Oct 2001 23:18:20 +0400 (MSD) Received: (qmail 7288 invoked by uid 1000); 13 Oct 2001 23:19:56 -0000 Date: Sat, 13 Oct 2001 23:19:56 +0000 From: Vladimir Dozen To: hackers@FreeBSD.ORG Subject: Re: sin_zero & bind problems Message-ID: <20011013231956.A7214@eix.do-labs.spb.ru> References: <20011013135842.A415@iv.nn.kiev.ua> <200110131717.f9DHHLR43887@earth.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <200110131717.f9DHHLR43887@earth.backplane.com>; from dillon@earth.backplane.com on Sat, Oct 13, 2001 at 10:17:21AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Sat, Oct 13, 2001 at 10:17:21AM -0700, Matt Dillon wrote: > Nobody in their right mind uses a struct sockaddr_in or any other > struct sock* type of structure without zeroing it first. Nobody in their right mind requires to fill any data except these used in given call. If no one checks, reads or alters sin_zero inside libc/kernel, why should user do it? For what? Does it prevent from detecting invalid parameters? No. It just eats a few processor cycles. For me, it looks like ... like requiring setting errno to zero before any system call. If you think it still required, it must be stated explicitely in documentation; btw, Single Unix Spec has no this requirement. > I suppose > we can document that in the man pages, but we certainly should not go > hacking up the kernel code to work around bad programmers. Work around? Nope. Just removing unnecessary constraint. -- dozen @ home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 12:28:26 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from samuelstn.dhs.org (h24-64-82-66.cg.shawcable.net [24.64.82.66]) by hub.freebsd.org (Postfix) with SMTP id DEC3137B401 for ; Sat, 13 Oct 2001 12:28:19 -0700 (PDT) Received: (qmail 54902 invoked from network); 13 Oct 2001 19:28:19 -0000 Received: from celeron (192.168.1.6) by homeserver with SMTP; 13 Oct 2001 19:28:19 -0000 Message-ID: <000701c1541d$36af2fc0$0601a8c0@samuelstn.dhs.org> From: "Samuel Chow" To: Subject: booting problem on custom 4STABLE kernel Date: Sat, 13 Oct 2001 13:28:18 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hi there, I hope I am posting to the right place. I have been a user only and not a kernel developer. I built myself a custom kernel with the kernel config file attached at the end of this email. It works. However, if I remove some of the unused NICs (for example fxp, rl, sf), the kernel complains that it cannot find device ad and waiting with a 'mountroot>' prompt. I built a kernel with DDB and boot the kernel with -v. Of course, I cannot really see the messages as they scroll by rather quickly. In addition, all the messages are not on disk, as the disk is not mounting yet. How can I proceed to find out why this is happening and how to fix this problem? Thanks for your help in advance. --- Samuel Chow samuelc@samuelstn.dhs.org Segmentation Fault (core dumped) This message is displayed using recycled electrons. # # NETSERVER # # For more information on this file, please read the handbook section on # Kernel Configuration Files: # # http://www.FreeBSD.org/handbook/kernelconfig-config.html # # The handbook is also available locally in /usr/share/doc/handbook # if you've installed the doc distribution, otherwise always see the # FreeBSD World Wide Web server (http://www.FreeBSD.org/) for the # latest information. # # An exhaustive list of options and more detailed explanations of the # device lines is also present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $FreeBSD: src/sys/i386/conf/GENERIC,v 1.246.2.34 2001/08/12 13:13:46 joerg Exp $ machine i386 cpu I586_CPU ident NETSERVER maxusers 32 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options INET6 #IPv6 communications protocols options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options SOFTUPDATES #Enable FFS soft updates support options NFS #Network Filesystem options NFS_NOSERVER #Disable the NFS-server code options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extensions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies options KBD_INSTALL_CDEV # install a CDEV entry in /dev # kernel debugger options DDB # add the kernel debugger device isa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives device atapifd # ATAPI floppy drives device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 flags 0x1 device psm0 at atkbdc? irq 12 device vga0 at isa? # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? flags 0x100 # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 # PCI Ethernet NICs that use the common MII bus controller code. # NOTE: Be sure to keep the 'device miibus' line in order to use these NICs! device miibus # MII bus support device fxp # Intel EtherExpress PRO/100B (82557, 82558) device rl # RealTek 8129/8139 device sf # Adaptec AIC-6915 (``Starfire'') device sis # Silicon Integrated Systems SiS 900/SiS 7016 device ste # Sundance ST201 (D-Link DFE-550TX) device tl # Texas Instruments ThunderLAN device tx # SMC EtherPower II (83c170 ``EPIC'') device vr # VIA Rhine, Rhine II device wb # Winbond W89C840F device wx # Intel Gigabit Ethernet Card (``Wiseman'') device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') device ed # RealTek 8029 # Pseudo devices - the number indicates how many units to allocate. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device gif # IPv6 and IPv4 tunneling pseudo-device faith 1 # IPv6-to-IPv4 relaying (translation) # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 13:34:42 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 3305737B406 for ; Sat, 13 Oct 2001 13:34:37 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9DKYXT11402; Sat, 13 Oct 2001 13:34:34 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: Cc: Subject: RE: Imagestream WanIC-520 interface cards Date: Sat, 13 Oct 2001 13:34:32 -0700 Message-ID: <001e01c15426$76e20960$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <165.24c83ab.28f9e878@aol.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Bsdguru@aol.com [mailto:Bsdguru@aol.com] >Sent: Saturday, October 13, 2001 11:57 AM >To: tedm@toybox.placo.com >Cc: hackers@freebsd.org >Subject: Re: Imagestream WanIC-520 interface cards > > >> >> You know I really think your baiting me. You know perfectly well that >> Hitachi and Cisco are not the same company. Anyway, Cisco is still >> selling the 2501 router, (although list on it is $2600 and nobody buying >> it for a single connection to the Internet would buy it new) I just >> logged into their reseller's website and the 2501 is still readily >available. >> > >I dont have to "bait" you..but you dont seem to "get" it. Cisco isnt >manufacturing 2501s anymore, so they areent buying ICs from Hitachi anymore Prove this. The fact is that Cisco is still selling them. Do you work for Cisco? >(I dont know where you get this "same company" stuff). Cisco may >have stopped >buying them years ago. Often when a chip manufacturer loses their main >customer, they discontinue the part for newer parts, or often when they >upgrade their foundries to new processes they can no longer make >older parts, >and its not cost-effective to rework them. > Cisco is just one customer among many that purchases this controller chip. SBS, who makes the WANic, is another customer that purchases this chip. There are undoubtedly other manufacturers that use this controller chip. >I only suggested that a card vendor is not in control of this, so it may not >be their choice that a card is being "phased out". When you buy ICs >you get a >notice a year in advance that the part is being phased out. > Then where is the announcement on the SBS website that this card is being phased out? Where is the info from Hitachi saying this controller chip is being phased out? >You are arguing a point without any facts, wrong. Fact is that the 2500 series uses the controler chip. Fact is that Cisco is still selling 2500's. If they are selling them they must be making them. Fact is that if they are making them they must use this chip. Fact is that there's no announcement from SBS anywhere stating that the WANic400 or the RIScom (which uses this chip) is being discontinued. Fact is they are still selling them. If they are selling them they must still be making them. Fact is that if they are making them they must be purchasing this controller chip. Fact is that Hitachi does not list this part as discontinued in their catalog. and Im merely suggesting a >scenario in which your "logic" doesnt work. Take if for what its worth. Your right in saying that both you and I are suggesting a scenario. However, mine is based on observed fact. Yours is based on unfounded speculation. If you could show any notice anywhere that this card is being discontinued then I'd grant that your speculation has some validity. But, you haven't. Until you do all your doing is spreading Fear Doubt Uncertainty (FUD) >Im >sure you dont understand the opportunity costs that Hitachi has related to >their foundry capacities. > I'm sure you don't either. However, I'm sure that I do understand the opportunity costs of small chip foundaries because it so happens I used to work for a company that manufactured an electronic device that used a custom chip in it, and they regularly purchased this chip in very small lots (100 to 500) It's perfectly possible for a chip foundry to make money off small runs. If someday Hitachi cannot make money off this controller chip any more because the volumes have gone down too much then I'm sure that there will be interested companies that will purchase the design. At this point in time the WANic400 series works, is available, and the driver works. Unfounded speculation that the card may disappear in the future contributes nothing and can even be damaging in that it could cause people to stop purchasing the card and thus hasten the day that the card is obsoleted. If you have a driver to contribute for the WANic500 series to FreeBSD then I'd cut you some slack in your efforts to condem the WANic400 but until then, kindly base your opinions on some real evidence. You need to consider that there has been little change in the price matrix used by the Telco's for high-speed circuits. DSL is not and cannot replace all T1 circuits and the costs to a small company to get high speed Internet access over anything faster than a T1 are completely unreasonable and impossible. There's a large number of business out there that are not reachable with broadband circuits because they are based too far away from telephone CO's and as a result they purchase Internet access over T1's. There's also a huge number of company sites that are part of corporate WAN's that are frame-relay based. The T1 and the E1 are not going to go away any time soon, and until they do there will be plenty of demand for devices that interface to them. The T1 and the E1 aren't going to go any faster and so there's no need to change the capacity of the serial interface controllers that interface to them. In short, synchronous serial connectors of this type are in a market that is pretty static. All hardware devices eventually will stop being manufactured including every CPU that FreeBSD runs on currently. Are we to stop using FreeBSD because someday the Pentium is going to be obsolete? Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 13:51:24 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id 712FD37B401 for ; Sat, 13 Oct 2001 13:51:20 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9DKpFT11433; Sat, 13 Oct 2001 13:51:15 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Matt Dillon" Cc: , Subject: RE: RE: Imagestream WanIC-520 interface cards Date: Sat, 13 Oct 2001 13:51:14 -0700 Message-ID: <001f01c15428$cc748d60$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <200110130540.f9D5eQW38618@earth.backplane.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Matt Dillon [mailto:dillon@earth.backplane.com] >Sent: Friday, October 12, 2001 10:40 PM >To: Ted Mittelstaedt >Cc: Bsdguru@aol.com; hackers@FreeBSD.ORG >Subject: Re: RE: Imagestream WanIC-520 interface cards > > > The Cisco 2600 series is great for T1's. A 2620 with a T1 card (it > can take up to two) and you are done. The 2501's are ancient, don't > even bother any more. You can find 2620's on EBay in the $700-$1500 > range, many of which appear (in my quick look) to include a T1 card. > > As much as I like to support running things on BSD, I stopped trying to > run T1's from general purpose unix boxes 4 years ago. When BEST Internet > first started we ran the (old) Riscom cards from a BSDI box w/ >an external > csu/dsu, and they were great for that, but these days the overall > cost of ownership is much, much lower with a used cisco and a WAN > card with an integrated csu/dsu in it. It's file and forget... once > you set the thing up you don't have to touch it ever again. > > One advantage of the dot-com crash is that EBay and other sites are > saturated with high quality, barely used hardware. > This is very true for leaf-node routers as used at customer sites and I've said the same thing myself on freebsd-questions before. However, there's still a market for those "Internet access toasters" that are basically PC's plus T1 interfaces, for the "set and forget" crowd. The cost issue, however, not true for BGP routers. Despite the dot-bombs the 7204/6 and the 3640 (both minimum cost of entry for BGP4 on Cisco) are both still very expensive even on Ebay. It's still cheaper to hook a fast Celery or something like that to an ISP feed. Furthermore, I feel compelled to point out that the Internet is still getting bigger and bigger and bigger. At some point in time even with Cisco's packing algorithims, the BGP route table plus Cisco IOS will exceed 128MB of ram. (both the 7206 and 3640 are limited to this as a maximum) Long before that the CPU's used in those Cisco devices will be swamped. And, I hear your answer to that, but screw that, why should I have to settle for a half-assed BGP feed with 3/4's of the routes chopped out of it from my providers? I've run BGP4 into both 7206's with NPE200's and Pentium 500Mhz systems with WANic cards, and the PC will converge BGP views faster than the Cisco, and tolerate route flaps far better, while under routing load. Cisco has a lot of exposure here, and their answer to the need for increased routing power on the Internet has been routers costing in the $100,000 range. Now, maybe BEST Internet is now wealthy enough that you can blow that kind of money on Cisco gear without thinking about it, but a lot of smaller ISP's are not. If you look at what happened last weekend on Sunday, and the number of people that screamed about it, it's quite obvious that there are a huge number of gated and zebra boxes out there handling global routing. Take off those Cisco blinders, boy! ;-) Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 16:15:37 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from boomerang.bytehosting.com (boomerang.bytehosting.com [65.196.231.162]) by hub.freebsd.org (Postfix) with SMTP id 07D8D37B40A for ; Sat, 13 Oct 2001 16:15:33 -0700 (PDT) Received: (qmail 10583 invoked by uid 0); 13 Oct 2001 21:07:55 -0000 Received: from rob@thechain.com by boomerang.bytehosting.com with qmail-scanner-0.96 (sweep: 2.4/3.47. . Clean. Processed in 1.047959 secs); 13 Oct 2001 21:07:55 -0000 X-Qmail-Scanner-Mail-From: rob@thechain.com via boomerang.bytehosting.com X-Qmail-Scanner: 0.96 (No viruses found. Processed in 1.047959 secs) Received: from unknown (HELO winbox) (@24.2.78.52) by mail.thechain.com with SMTP; 13 Oct 2001 21:07:54 -0000 From: "Rob" To: Subject: please help my hdd Date: Sat, 13 Oct 2001 19:08:24 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I am writing this mailing list in a desperate attempt to find out how to restore my hdd with out loosing all the data on it. Recently I added two additional hard drives to my freebsd 4.2 system. Once I booted up my system and dl'ed some things with wget a bunch of errors occurred resulting in "kernel panic" and then system halt. When I rebooted I get and error and cannot boot freebsd error: Verifying DMI Pool Data ......... | int=00000000 err=00000000 efl=00010246 eip=00001b2c eax=00000002 ebx=00000002 ecx=00006564 edx=00000000 esi=00094cdc edi=000022bf ebp=00094cbc esp=00094ca4 cs=002b ds=0033 es=0033 fs=0033 gs=0033 gs=0033 ss=0033 cs:eip=f7 35 98 24 00 00 89 c7-89 f9 0f af 0d 9c 24 00 ss:esp=00 00 00 00 e0 4c 09 00-dc 4c 09 00 bf 22 00 00 BTX halted to try to fix this problem I installed a minimal install of fbsd on another hdd and ran fsck /dev/ad1a which said this: ** /dev/ad1a BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE /dev/ad1a: INCOMPLETE LABEL: type 4.2BSD fsize 0, frag 0, cpg 0, size 9809920 Although it doesn't really help I can still df -h it; df /dev/ad1a prints: Filesystem Size Used Avail Capacity Mounted on /dev/ad1a 4.5G 1.5G 2.7G 36% fdisk /dev/ad1a prints: *****Working on device /dev/ad1a ********* parameters extracted from in-core disklabel are: cylinders=621 heads=255 sectors/track=63 (16065 blks/cyl) parameters to be used for BIOS calclations are: cylinders=621 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 0, size 50000 (24 meg), flag 80 (active) beg: cyl 0/ head 0/ sector 1; end:cyl 1023/ head 255/ sector 63 Is the data on my hdd completely unrecoverable? Is there anyway I could mount the partion? mount /dev/ad1a /blah (/blah is a directory) prints this: mount: /dev/ad1a on /blah: incorrect super block To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 16:33:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from imo-r09.mx.aol.com (imo-r09.mx.aol.com [152.163.225.105]) by hub.freebsd.org (Postfix) with ESMTP id 2B03837B407 for ; Sat, 13 Oct 2001 16:33:12 -0700 (PDT) Received: from Bsdguru@aol.com by imo-r09.mx.aol.com (mail_out_v31_r1.8.) id n.d1.de52380 (4239) for ; Sat, 13 Oct 2001 19:33:09 -0400 (EDT) From: Bsdguru@aol.com Message-ID: Date: Sat, 13 Oct 2001 19:33:08 EDT Subject: Re: 4-port T1 PCI card with integrated csu/dsu To: hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: AOL 5.0 for Windows sub 138 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In a message dated 10/13/01 3:15:31 PM Eastern Daylight Time, phk@critter.freebsd.dk writes: > >> etinc is not recommendable. > >> > > > >Everyone knows that PHK has a grudge against etinc. How childish. > > No, I don't have a grudge against Dennis or Etinc, I merely point > out that somebody who has caused so much grief in our mailing lists > without ever actually submitting one single diff to us is not > a (re)commendable supplier. I dont know about you, but I base my recommendations on the ability of the product to help the person thats asking, not the number of lines of code they've contributed. I dont see how driving away commercial vendors with such a ridiculous attitude benefits the FreeBSD community. Very unprofessional. B To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 18:33:44 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id 8224D37B405 for ; Sat, 13 Oct 2001 18:33:41 -0700 (PDT) Received: (from dillon@localhost) by earth.backplane.com (8.11.6/8.11.2) id f9E1XHI45650; Sat, 13 Oct 2001 18:33:17 -0700 (PDT) (envelope-from dillon) Date: Sat, 13 Oct 2001 18:33:17 -0700 (PDT) From: Matt Dillon Message-Id: <200110140133.f9E1XHI45650@earth.backplane.com> To: "Ted Mittelstaedt" Cc: , Subject: Re: RE: RE: Imagestream WanIC-520 interface cards References: <001f01c15428$cc748d60$1401a8c0@tedm.placo.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG :on the Internet has been routers costing in the $100,000 range. Now, maybe :BEST Internet is now wealthy enough that you can blow that kind of money on :Cisco gear without thinking about it, but a lot of smaller ISP's are not. : :If you look at what happened last weekend on Sunday, and the number of people :that screamed about it, it's quite obvious that there are a huge number of :gated and zebra boxes out there handling global routing. Take off those :Cisco blinders, boy! ;-) : :Ted Mittelstaedt tedm@toybox.placo.com :Author of: The FreeBSD Corporate Networker's Guide Hmm. Well, as a person who ran gated at BEST, has hacked on gated on same, had to deal with BSDI and FreeBSD route table bugs, tracked down OSPF bugs for a friend running gated, and otherwise spent hundreds of hours (at least!) keeping boxes running gated operational... well, I'll take the Cisco any day thank you very much! If you are a small ISP and you have enough money to pay for two T1's, you have enough money to buy a used router that can do BGP for you. IMHO. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 19:50:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.twwells.com (mail.twwells.com [64.38.247.128]) by hub.freebsd.org (Postfix) with ESMTP id D92C137B409 for ; Sat, 13 Oct 2001 19:50:11 -0700 (PDT) Received: from xfermail (helo=mail.twwells.com) by mail.twwells.com with local-bsmtp (Exim 3.32 #1) id 15sbLl-000Ouj-00 for freebsd-hackers@freebsd.org; Sat, 13 Oct 2001 19:50:01 -0700 X-Filter-Status: mail.twwells.com ok 28 Received: from twwells.com ( [65.14.140.228] ) by mail.twwells.com via tcp with esmtp id 3bc8fd3d-017615; Sun, 14 Oct 2001 02:49:33 +0000 Received: from root by twwells.com with local (Exim 3.33 #1) id 15sbLH-0004Hm-00 for freebsd-hackers@freebsd.org; Sat, 13 Oct 2001 22:49:31 -0400 Subject: Re: 4-port T1 PCI card with integrated csu/dsu References: <134.3014468.28f9eb43@aol.com> To: freebsd-hackers@freebsd.org From: admin@twwells.com Message-Id: Date: Sat, 13 Oct 2001 22:49:31 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bsdguru@aol.com wrote: > dennis can be brusk, but he knows WAN better than anyone I've ever worked > with or for. > > Bryan 1) Dennis, who is etinc for all practical purposes, used to post off-topic and abusive messages on the freebsd.org mailing lists, under the address dennis@etinc.com. 2) Dennis received repeated warnings to stop and was threatened with removal if he did not stop. 3) Dennis replied that he would simply return under an alias if he was removed. 4) Dennis was removed from these lists. 5) dennis@etinc.com's last post on this list was 4/27/2001. Bsdguru@aol.com's first post was 5/23/2001. I believe the facts speak for themselves. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 21: 8:14 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.twwells.com (mail.twwells.com [64.38.247.128]) by hub.freebsd.org (Postfix) with ESMTP id 8FF3E37B40A for ; Sat, 13 Oct 2001 21:08:11 -0700 (PDT) Received: from xfermail (helo=mail.twwells.com) by mail.twwells.com with local-bsmtp (Exim 3.32 #1) id 15scZF-000PMf-00 for freebsd-hackers@freebsd.org; Sat, 13 Oct 2001 21:08:01 -0700 X-Filter-Status: mail.twwells.com ok 2 Received: from twwells.com ( [65.14.140.228] ) by mail.twwells.com via tcp with esmtp id 3bc90f9f-017cd7; Sun, 14 Oct 2001 04:07:59 +0000 Received: from root by twwells.com with local (Exim 3.33 #1) id 15scZC-0006Ky-00; Sun, 14 Oct 2001 00:07:58 -0400 From: admin@twwells.com To: freebsd-hackers@freebsd.org Subject: Re: 4-port T1 PCI card with integrated csu/dsu References: Message-Id: Date: Sun, 14 Oct 2001 00:07:58 -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Bsdguru@aol.com writes: > I dont see how driving away commercial vendors with such a ridiculous > attitude benefits the FreeBSD community. Very unprofessional. Verbal abuse, violation of AUPs, and theft of service are also unprofessional. More to the point, FreeBSD isn't driving etinc.com away, Dennis is the responsible agent. The relevant principle is: Those who do a wrong are responsible for the expectable consequences of their action. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 21:57:52 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mozone.net (mail.mozone.net [206.165.200.53]) by hub.freebsd.org (Postfix) with ESMTP id E76B037B40A for ; Sat, 13 Oct 2001 21:57:47 -0700 (PDT) Received: (from mki@localhost) by mozone.net (8.11.2/8.11.2) id f9E4vg111621 for freebsd-hackers@FreeBSD.org; Sat, 13 Oct 2001 21:57:42 -0700 Date: Sat, 13 Oct 2001 21:57:42 -0700 From: mki To: freebsd-hackers@FreeBSD.org Subject: regcomp, bounds overrun in computematchjumps Message-ID: <20011013215742.C9543@cyclonus.mozone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Here's a wierd problem i ran into with regcomp, using the attached test program linked against libefence. Am I missing something obvious, other than the fact that it is a "not-so-correct" regex? Also, the stranger part is that when the /10 is replaced with /11 (YMMV) the problem doesn't occur. #include #include #include int main(int argc, char **argv) { regex_t preg; int r; char errbuf[512]; r = regcomp(&preg, "127.0.0.1/10", REG_NOSUB|REG_EXTENDED|REG_ICASE); if ( r != 0 ) { regerror(r, &preg, errbuf, sizeof(errbuf)); printf("couldn't compile regex pattern, %s\n", errbuf); return -1; } return 0; } Program received signal SIGBUS, Bus error. 0x804c5d5 in computematchjumps (p=0xbfbff46c, g=0x28104ea0) at regcomp.c:2048 2048 ssuffix = pmatches[ssuffix]; (gdb) where #0 0x804c5d5 in computematchjumps (p=0xbfbff46c, g=0x28104ea0) at regcomp.c:2048 #1 0x8048fe8 in regcomp (preg=0xbfbff70c, pattern=0x804da20 "127.0.0.1/10", cflags=7) at regcomp.c:281 #2 0x8048d08 in main (argc=1, argv=0xbfbff770) at test.c:10 #3 0x8048c5d in _start () (gdb) frame 0 #0 0x804c5d5 in computematchjumps (p=0xbfbff46c, g=0x28104ea0) at regcomp.c:2048 2048 ssuffix = pmatches[ssuffix]; (gdb) l 2043 while (suffix <= ssuffix && suffix < g->mlen) { 2044 g->matchjump[suffix] = MIN(g->matchjump[suffix], 2045 g->mlen + ssuffix - suffix); 2046 suffix++; 2047 } 2048 ssuffix = pmatches[ssuffix]; 2049 } 2050 2051 free(pmatches); 2052 } (gdb) print ssuffix $1 = 4 (gdb) l 2000 1995 1996 /* Avoid making errors worse */ 1997 if (p->error != 0) 1998 return; 1999 2000 pmatches = (int*) malloc(g->mlen * sizeof(unsigned int)); 2001 if (pmatches == NULL) { 2002 g->matchjump = NULL; 2003 return; 2004 } (gdb) print g->mlen $2 = 4 (gdb) print pmatches[0] $3 = 3 (gdb) print pmatches[1] $4 = 3 (gdb) print pmatches[2] $5 = 3 (gdb) print pmatches[3] $6 = 4 (gdb) print pmatches[4] Error accessing memory address 0x2810d000: Bad address. (gdb) print ssuffix $7 = 4 (gdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 22: 9:58 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.freebsd-corp-net-guide.com (mail.freebsd-corp-net-guide.com [206.29.169.15]) by hub.freebsd.org (Postfix) with ESMTP id B56A437B408 for ; Sat, 13 Oct 2001 22:09:53 -0700 (PDT) Received: from tedm.placo.com (nat-rtr.freebsd-corp-net-guide.com [206.29.168.154]) by mail.freebsd-corp-net-guide.com (8.11.1/8.11.1) with SMTP id f9E59jT12280; Sat, 13 Oct 2001 22:09:46 -0700 (PDT) (envelope-from tedm@toybox.placo.com) From: "Ted Mittelstaedt" To: "Matt Dillon" Cc: , Subject: RE: RE: RE: Imagestream WanIC-520 interface cards Date: Sat, 13 Oct 2001 22:09:44 -0700 Message-ID: <002101c1546e$703d8420$1401a8c0@tedm.placo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <200110140133.f9E1XHI45650@earth.backplane.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >-----Original Message----- >From: Matt Dillon [mailto:dillon@earth.backplane.com] >Sent: Saturday, October 13, 2001 6:33 PM >To: Ted Mittelstaedt >Cc: Bsdguru@aol.com; hackers@FreeBSD.ORG >Subject: Re: RE: RE: Imagestream WanIC-520 interface cards > > >:on the Internet has been routers costing in the $100,000 range. Now, maybe >:BEST Internet is now wealthy enough that you can blow that kind of money on >:Cisco gear without thinking about it, but a lot of smaller ISP's are not. >: >:If you look at what happened last weekend on Sunday, and the number >of people >:that screamed about it, it's quite obvious that there are a huge number of >:gated and zebra boxes out there handling global routing. Take off those >:Cisco blinders, boy! ;-) >: >:Ted Mittelstaedt tedm@toybox.placo.com >:Author of: The FreeBSD Corporate Networker's Guide > > Hmm. Well, as a person who ran gated at BEST, has hacked on gated on > same, had to deal with BSDI and FreeBSD route table bugs, tracked down > OSPF bugs for a friend running gated, and otherwise spent hundreds of > hours (at least!) keeping boxes running gated operational... well, I'll > take the Cisco any day thank you very much! :-) As I've said I run both - and each has it's strengths and weaknesses. I've not had the problems you apparently did with gated. However, I'll admit that you probably ran it a lot earlier than I did, on a lot slower hardware than I, thus I'm benefiting from all the bug-squishing that you have done on gated and FreeBSD. I have found that CPU speed makes a huge difference. I have had lots of problems trying to run BGP and gated on anything slower than a 400Mhz system. > > If you are a small ISP and you have enough money to pay for two T1's, > you have enough money to buy a used router that can do BGP for you. > IMHO. > Probably for you or I because we both know Cisco and are familiar with the ins and outs of their stuff and know where to get used gear. But, if you do it the Cisco Way, where you go buy a new 7206VXR with a service contract - no way. In our market, and I swear this is true, we have CLEC's that are selling fractional T1's (split voice/data with add-drop DSU's) and they are charging less than $50 a month for 768k or greater feeds. It's competitive with DSL. The customer pays for the voice lines which are maybe $1-$5 cheaper per trunk than what the ILEC would charge, then gets in essense a free Internet feed. Now, obviously the CLEC is planning on the company growing and adding trunks onto that T1, because they are making their money off the voice circuits and the call termination payments that the RBOC's are paying them. So they give away the Internet service as an enticement. And, obviously it's crap - I've used a few of them and your lucky to get 128kbits/sec on a "768k point to point to the Internet" And these same CLECS are also still not profitable (according to the local business journal) and haven't been for years. But, the upshot is that it's tremendously depressed prices for point-to-point or Frame service in our market. It's a very hard sell to sell one of these circuits now and we usually have to walk the prospect over to another of our customers to demonstrate what a true 768Kbps is supposed to be like. Now I don't know if we are just in a over-wired market, although PDX has more Internet usage per capita than any other city in the country. But, I've heard about markets (like Phoenix) where there's only national providers and a single regional provider, all the other regional providers have gone out of business. In those markets, yes, the regional provider that has enough money to pay for 2 T1's probably can charge enough to afford a used router that will do BGP. But, in markets like ours, the margins are far, far thinner. You cut where it makes sense, and gated on FreeBSD makes sense for one of our border routers, (probably also for a second, I just haven't gotten around to replacing it) Given a choice between spending on a lot of networking hardware so we can say we are 100% Cisco, and spending the money on more bandwidth, the choice is obvious. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 22:38:53 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from db-cvad-1-tmp.yahoo.com (db-cvad-1-tmp.yahoo.com [216.145.48.242]) by hub.freebsd.org (Postfix) with ESMTP id EEF1E37B40E for ; Sat, 13 Oct 2001 22:38:49 -0700 (PDT) Received: from master.gorean.org (root@master.gorean.org [10.0.0.2]) by db-cvad-1-tmp.yahoo.com (8.11.6/8.11.6) with ESMTP id f9E5cns29517; Sat, 13 Oct 2001 22:38:49 -0700 (PDT) (envelope-from DougB@FreeBSD.org) Received: from localhost (doug@localhost) by master.gorean.org (8.11.6/8.11.6) with ESMTP id f9E5d8G42077; Sat, 13 Oct 2001 22:39:08 -0700 (PDT) (envelope-from DougB@FreeBSD.org) X-Authentication-Warning: master.gorean.org: doug owned process doing -bs Date: Sat, 13 Oct 2001 22:39:08 -0700 (PDT) From: Doug Barton X-X-Sender: doug@master.gorean.org To: Bsdguru@aol.com Cc: hackers@FreeBSD.org Subject: Re: 4-port T1 PCI card with integrated csu/dsu In-Reply-To: Message-ID: <20011013223629.O40455-100000@master.gorean.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG The virtues or foibles of individual personalities are outside the scope of this list. Anyone interested in further information is welcome to search the archives of just about any of the FreeBSD lists. Meanwhile, let's get back to our regularly scheduled bikesheds. Thanks, Doug -- "We will not tire, we will not falter, and we will not fail." - George W. Bush, President of the United States September 20, 2001 Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Oct 13 23:46:13 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from peter3.wemm.org (c1315225-a.plstn1.sfba.home.com [24.14.150.180]) by hub.freebsd.org (Postfix) with ESMTP id 547D837B408 for ; Sat, 13 Oct 2001 23:46:10 -0700 (PDT) Received: from overcee.netplex.com.au (overcee.wemm.org [10.0.0.3]) by peter3.wemm.org (8.11.0/8.11.0) with ESMTP id f9E6k9M95720 for ; Sat, 13 Oct 2001 23:46:09 -0700 (PDT) (envelope-from peter@wemm.org) Received: from wemm.org (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id DC2393811; Sat, 13 Oct 2001 23:46:09 -0700 (PDT) (envelope-from peter@wemm.org) X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: admin@twwells.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 4-port T1 PCI card with integrated csu/dsu In-Reply-To: Date: Sat, 13 Oct 2001 23:46:09 -0700 From: Peter Wemm Message-Id: <20011014064609.DC2393811@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG admin@twwells.com wrote: > Bsdguru@aol.com wrote: > > dennis can be brusk, but he knows WAN better than anyone I've ever worked > > with or for. > > > > Bryan > > 1) Dennis, who is etinc for all practical purposes, used to post > off-topic and abusive messages on the freebsd.org mailing > lists, under the address dennis@etinc.com. > > 2) Dennis received repeated warnings to stop and was threatened > with removal if he did not stop. > > 3) Dennis replied that he would simply return under an alias if > he was removed. > > 4) Dennis was removed from these lists. > > 5) dennis@etinc.com's last post on this list was 4/27/2001. > Bsdguru@aol.com's first post was 5/23/2001. Furthermore: May 22 15:53:45 {Dennis } unsubscribe freebsd-hackers dennis@etinc.com May 23 10:06:38 {Bsdguru@aol.com} subscribe freebsd-hackers Bsdguru@aol.com May 23 10:07:12 {Bsdguru@aol.com} subscribe freebsd-isp Bsdguru@aol.com May 23 13:43:09 {Dennis } unsubscribe freebsd-isp dennis@etinc.com Oh, look! over the same 24 hour period, dennis unsubscribed and "Bsdguru" [re]subscribed. And to the same mailing lists. Oh, gee! what a coincidence! > I believe the facts speak for themselves. *Hi dennis!* -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message