From owner-freebsd-hackers Sun Aug 27 1: 0:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns1.ovis.net (ns1.ovis.net [207.0.147.2]) by hub.freebsd.org (Postfix) with ESMTP id E416537B43C for ; Sun, 27 Aug 2000 01:00:19 -0700 (PDT) Received: from ovis.net (s30.pm5.ovis.net [207.0.147.96]) by ns1.ovis.net (8.9.3/8.9.3) with ESMTP id DAA23198; Sun, 27 Aug 2000 03:59:42 -0400 Message-ID: <39A8CB42.64AF445E@ovis.net> Date: Sun, 27 Aug 2000 04:03:14 -0400 From: Steve Kudlak Reply-To: chromexa@ovis.net X-Mailer: Mozilla 4.5 [en]C-CCK-MCD ezn/58/n (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: chris@calldei.com Cc: hspio@worldnet.att.net, hackers@FreeBSD.ORG Subject: Re: UNSUBSCRIBE REMOVE References: <39A84A4C.20198.175588@localhost> <20000826225734.P60058@holly.calldei.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Costello wrote: > On Saturday, August 26, 2000, hspio@worldnet.att.net wrote: > > [2,640 lines removed] > > ... and this was at the bottom of the message you quoted: > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hackers" in the body of the message > > At the very least, don't just mail a whole day's worth of data > back to the list with "UNSUBSCRIBE REMOVE" affixed to the subject > line. Don't you know how much bandwidth and money you're wasting > for people who have to pay for the amount of data they download? > > I'm sending this to the list because hopefully someone else > reading it and wanting to unsubscribe won't make the same > mistake. > > -- > |Chris Costello > |Justify my text? I'm sorry but it has no excuse. > `------------------------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message But it's fun!!! IT's like some magic chamy ---Have aafun Send Steve (who goes back to mainly lurking!!!:) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 9: 6:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id CF10637B42C for ; Sun, 27 Aug 2000 09:06:27 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id MAA07543 for ; Sun, 27 Aug 2000 12:50:33 -0400 (EDT) From: "Clarence Brown" To: Subject: 4.1 lockup at isa0: on reboot Date: Sun, 27 Aug 2000 12:10:46 -0400 Message-ID: <003301c01041$5c3e9da0$8c6896d1@granitepost.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 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll apologize in advance if this is the wrong list, but it seems like a question for hackers to me, and the freebsd-questions list only had one response verifying that someone else had the same problem. As an aside, I am an embedded system developer doing PCB through firmware development, so with your direction, I ought to be able to hack this myself. The problem is repeatable making it easier to find. I'll need direction configuring the development/debug tools and environment because I usually develop for the 8x52/251 microcontroller family using DOS/windows based tools. I just installed 4.1 from CD onto a machine that had been running 3.4 without problems. The machine is an old Gateway 486 DX/2 66 (Micronics Local Bus motherboard) with an upgraded processor, DVC Turbo 586 using an AMD AM5x68, and 64 Meg ram. Problem: If I do a "shutdown -h now" and then press any key to reboot, the system ALWAYS hangs after displaying the line.. isa0: on motherboard This is repeatable, Note: From a power up, or reset button the system ALWAYS starts fine. I don't know if this is related to the ISA bus problem, I also had trouble during the install with the SCSI probing, but never finishing when the scsi adaptor on the soundblaster card was enabled. SB16 SCSI w/ AIC6360 chip. This also worked fine under 3.4. Since I don't currently have any scsi devices connected I just deleted it from the list during kernel config then the install proceeded ok ... I'll tackle this later. Is 4.1 known to have hardware problems like these? I realize there is probably a shrinking base of 486 installs, which would reduce the urgency of this problem in general, this is why I'm assuming I'll probably get a quicker solution if I "volunteer" to fix it. Others also have the problem on several other 486 motherboards and the only solution they found was to abandon 4.1 and revert to 3.5, see the clipped response below which I got on the freebsd-questions list. > I had the same problem - with a few different > 486 boards. Unfortunately, my only working > solution was to revert back to 3.51 > The only way past this was to do a hard reset/cold > boot ... not a pretty option when this was a > customer's remote gateway machine. > ... Jamie Cla. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 9:12:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id CF19537B424 for ; Sun, 27 Aug 2000 09:12:55 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 580395D1B; Sun, 27 Aug 2000 18:12:54 +0200 (CEST) Date: Sun, 27 Aug 2000 18:12:54 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Clarence Brown Cc: freebsd-hackers@freebsd.org Subject: Re: 4.1 lockup at isa0: on reboot In-Reply-To: <003301c01041$5c3e9da0$8c6896d1@granitepost.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Problem: If I do a "shutdown -h now" and then press > any key to reboot, the system ALWAYS hangs after > displaying the line.. > > isa0: on motherboard I think I've seen this on a customer's 486 (used as a wireless router) and if I remember correctly it was caused by the ata driver. Unplugging the hard disk fixed it (but obviously I couldn't install FreeBSD on such a machine :), it was a Western Digital. Using the wd driver fixed it as well. Plugging in another hard disk (a newer Western Digital) fixed it as well. I chose the later route, as the old disk crashed a couple of days after using it with the wd driver. Also, I had to use userconfig to remove all drivers for hardware I didn't have. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 9:52: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id D933537B42C for ; Sun, 27 Aug 2000 09:52:05 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7RGq0Z07318; Sun, 27 Aug 2000 09:52:00 -0700 (PDT) Date: Sun, 27 Aug 2000 09:52:00 -0700 From: Alfred Perlstein To: Blaz Zupan Cc: Clarence Brown , freebsd-hackers@FreeBSD.ORG Subject: Re: 4.1 lockup at isa0: on reboot Message-ID: <20000827095200.A1209@fw.wintelcom.net> References: <003301c01041$5c3e9da0$8c6896d1@granitepost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from blaz@amis.net on Sun, Aug 27, 2000 at 06:12:54PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Blaz Zupan [000827 09:13] wrote: > > Problem: If I do a "shutdown -h now" and then press > > any key to reboot, the system ALWAYS hangs after > > displaying the line.. > > > > isa0: on motherboard > > I think I've seen this on a customer's 486 (used as a wireless router) and if > I remember correctly it was caused by the ata driver. Unplugging the hard disk > fixed it (but obviously I couldn't install FreeBSD on such a machine :), it > was a Western Digital. Using the wd driver fixed it as well. Plugging in > another hard disk (a newer Western Digital) fixed it as well. I chose the > later route, as the old disk crashed a couple of days after using it with the > wd driver. Also, I had to use userconfig to remove all drivers for hardware I > didn't have. Guys, here's what you need to do; go to: http://www.freebsd.org/handbook/kerneldebug.html Basically you need to compile a kernel with: options DDB options BREAK_TO_DEBUGGER #a BREAK on a comconsole goes to then when it hangs at boot one might be able to to hit ctrl+alt+esc to get into the kernel debugger, then hit 't' (i think, it's been a while :) ) to get a traceback. Tell us what you see. Another simpler option is interrupting the boot countdown and typing 'boot -v' to get a more verbose boot then give us more information than just "isa0: on motherboard". :) Please let us know what you find out. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 10: 1: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id D57DA37B43C for ; Sun, 27 Aug 2000 10:00:52 -0700 (PDT) Received: from sharky (adsl-151-202-97-90.bellatlantic.net [151.202.97.90]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id LAA17882 for ; Sun, 27 Aug 2000 11:02:34 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200008271702.LAA17882@mail.fpsn.net> From: "Simon" To: "freebsd-hackers@FreeBSD.ORG" Date: Sun, 27 Aug 2000 13:04:14 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Please help me identify this: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone please help me identify the following message? I get it when my freebsd panics and I have to do a cold- reboot. mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 instruction pointer = 0x8:0xc024d4e8 stack pointer = 0x10:0xdb3dcf20 frame pointer = 0x10:0xdb3dcfa0 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = inerrupt enabled, IOPL = 0 current process = 55063 (httpd) interrupt mask = none <- SMP: XXX trap number = 29 panic: unknown/reserved trap mp_lock = 01000001; cpuid = 1; lapic.id = 01000000 boot() called on cpu#1 syncing disks... 868 860 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 859 giving up on 2 buffers Uptime: 23h16m47s Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... cpu_reset called on cpu#1 cpu_reset: Stopping other CPUs cpu_reset: Restarting BSP cpu_reset_proxy: Grabbed mp lock for BSP Thank you very much in advance. -Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 10:43:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 2EFEF37B422 for ; Sun, 27 Aug 2000 10:43:06 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id 67E315D09; Sun, 27 Aug 2000 19:43:05 +0200 (CEST) Date: Sun, 27 Aug 2000 19:43:05 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Alfred Perlstein Cc: Clarence Brown , freebsd-hackers@FreeBSD.ORG Subject: Re: 4.1 lockup at isa0: on reboot In-Reply-To: <20000827095200.A1209@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Guys, here's what you need to do; go to: Ehm, I can't do anything as the machine is already back in production at the customer site (I did not have time to debug it while I had the machine, because I only had it for a day to upgrade it from 2.2.6 to 4.1). With a new disk and the ata driver. As far as I'm concerned, it was bad relation between ata driver and the old (now broken) hard disk. Clarence might be able to get a trace, of course (I hope). Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 10:59:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id E677937B422 for ; Sun, 27 Aug 2000 10:59:42 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id OAA07853; Sun, 27 Aug 2000 14:43:49 -0400 (EDT) From: "Clarence Brown" To: "'Alfred Perlstein'" , Subject: RE: 4.1 lockup at isa0: on reboot Date: Sun, 27 Aug 2000 14:03:53 -0400 Message-ID: <003601c01051$2a05ea40$8c6896d1@granitepost.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: <20000827095200.A1209@fw.wintelcom.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > Behalf Of Alfred Perlstein > * Blaz Zupan [000827 09:13] wrote: > > > Problem: If I do a "shutdown -h now" and then press > > > any key to reboot, the system ALWAYS hangs after > > > displaying the line.. > > > > > > isa0: on motherboard > > > > I think I've seen this on a customer's 486 (used > > as a wireless router) and if I remember correctly > > it was caused by the ata driver. Unplugging the > > hard disk fixed it (but obviously I couldn't > > install FreeBSD on such a machine :), it was a > > Western Digital. Using the wd driver fixed it as > > well. Plugging in another hard disk (a newer > > Western Digital) fixed it as well. I chose the > > later route, as the old disk crashed a couple of > > days after using it with the wd driver. Also, I > > had to use userconfig to remove all drivers for > > hardware I didn't have. > > Guys, here's what you need to do; go to: > > http://www.freebsd.org/handbook/kerneldebug.html > > Basically you need to compile a kernel with: > > options DDB > options BREAK_TO_DEBUGGER #a BREAK on a > comconsole goes to > > then when it hangs at boot one might be able to to > hit ctrl+alt+esc to get into the kernel debugger, > then hit 't' (i think, it's been a while :) ) to > get a traceback. Tell us what you see. > > Another simpler option is interrupting the boot > countdown and typing 'boot -v' to get a more > verbose boot then give us more information than > just "isa0: on motherboard". :) > > Please let us know what you find out. > I booted the machine with power up, logged in as root, did "shutdown -h now", hit space to reboot. During the countdown I hit "space" then at the "ok" prompt? I typed "boot -v [ENTER]" More info DID scroll by before the hang, but I didn't see any difference in the output at the point of the hang. The last 3 lines were the same as without the "boot -v": npx0: on motherboard npx0: INT16 interface isa0: on motherboard I don't think the "npx0:" lines are related to the "isa0:" line. At this point the machine appears locked up. No disk or other observable activity. If I had to guess from my HW design experience I'd say there's an obscure register somewhere that the firmware initializes properly on a hardware boot, but that is missed by the software reset. This would seem to be fixable by simply isolating the register(s) and adding their initialization to the code somewhere. Looks like I might have to figure out how to setup my system for kernel debug... Any other ideas before I start reading the kernel debug web pages ... I don't really want to have to figure out how to install and use a new (to me) compiler/debugger combo, not to mention getting all the source etc... I've got the 4 CD subscription set, is the source and all that on there somewhere? Don't tell me I also get to figure out how to use CVS at the same time . I really need to quite playing with this computer and finish putting the new floor joists where the bathroom is supposed to be... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 11: 2: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id 561DE37B423 for ; Sun, 27 Aug 2000 11:01:58 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id OAA07866; Sun, 27 Aug 2000 14:46:04 -0400 (EDT) From: "Clarence Brown" To: "'Blaz Zupan'" , Subject: RE: 4.1 lockup at isa0: on reboot Date: Sun, 27 Aug 2000 14:06:08 -0400 Message-ID: <003701c01051$7a44d2a0$8c6896d1@granitepost.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: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think I've seen this on a customer's 486 (used > as a wireless router) and if I remember correctly > it was caused by the ata driver. Unplugging the > hard disk fixed it (but obviously I couldn't install > FreeBSD on such a machine :), it > was a Western > Digital. Using the wd driver fixed it as well. > Plugging in another hard disk (a newer Western > Digital) fixed it as well. I chose the later > route, as the old disk crashed a couple of days > after using it with the wd driver. Also, I had > to use userconfig to remove all drivers for > hardware I didn't have. > This is after the install ... Don't know how I could unplug the hard disk, while it's booting from the same hard disk ... It IS a Western Digital Caviar AC22000 drive. I might be able to dig up an even older Seagate for a test install. I've never had to mess with the kernel before, generic always worked ... "userconfig"? I'll look it up. How do I make it use the WD driver? Will that affect the IDE CDROM? > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 11:36:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 01F1937B424 for ; Sun, 27 Aug 2000 11:36:15 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7RIa7V09827; Sun, 27 Aug 2000 11:36:07 -0700 (PDT) Date: Sun, 27 Aug 2000 11:36:07 -0700 From: "'Alfred Perlstein'" To: Clarence Brown Cc: freebsd-hackers@freebsd.org Subject: Re: 4.1 lockup at isa0: on reboot Message-ID: <20000827113607.B1209@fw.wintelcom.net> References: <20000827095200.A1209@fw.wintelcom.net> <003601c01051$2a05ea40$8c6896d1@granitepost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <003601c01051$2a05ea40$8c6896d1@granitepost.com>; from clabrown@granitepost.com on Sun, Aug 27, 2000 at 02:03:53PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Clarence Brown [000827 10:59] wrote: > > -----Original Message----- > > Behalf Of Alfred Perlstein > > * Blaz Zupan [000827 09:13] wrote: > > Looks like I might have to figure out how to > setup my system for kernel debug... Yes, you can choose to install the source code you can do so by running /stand/sysinstall and choosing to install the kernel sources, one doesn't need to know much to figure out how to just get a traceback. It's really just as simple as recomiling your kernel: http://www.freebsd.org/handbook/kernelconfig.html just add the options I mentioned above: > > options DDB > > options BREAK_TO_DEBUGGER and you ought to be able to get us a traceback by hitting ctrl-alt-esc, then 't' at the prompt. Btw, providing the type of disks and HD controller as well as a complete "boot -v" output would be a lot more helpful, if you can hard-reset then boot -v you should be able to find the file in /var/run/dmesg.boot. thanks, -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 11:37: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id C878737B424 for ; Sun, 27 Aug 2000 11:36:58 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13T7PP-00007C-00; Sun, 27 Aug 2000 12:43:55 -0600 Message-ID: <39A9616B.AC5BDF4D@softweyr.com> Date: Sun, 27 Aug 2000 12:43:55 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: farid.hajji@ob.kamp.net Cc: hackers@FreeBSD.org Subject: Re: Moving FreeBSD towards glibc (or: FreeBSD and Hurd/Mach) References: <39A74783.FF8CF3AF@softweyr.com> <200008261721.e7QHL8V15403@mail-ob.kamp.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Farid Hajji wrote: > > > > > are there plans to replace FreeBSD's libc with GNU glibc in the near > > > > or medium future? > Thanks for all your replies. I perfectly understand the reasons for avoiding > GNU copylefted code like glibc in FreeBSD. Using the Hurd/Mach as kernel > replacement for FreeBSD would indeed require adding the syscall emulation > feature like in Lites/RT-Mach, linking against FreeBSD's libc and adding > missing functionality as stubs. I just hoped it would be a bit easier ;-) I've never found an easy way to do hard work. I don't think anyone would fault you for trying, though. > BTW, I don't have any problems with the FreeBSD kernel itself or its libc. > They are excellent and I'm using them both at home and exclusively for > mission critical applications. Keep up the good work! Agreed. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 12:10:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id E0DD237B42C for ; Sun, 27 Aug 2000 12:10:17 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id PAA08053 for ; Sun, 27 Aug 2000 15:54:28 -0400 (EDT) From: "Clarence Brown" To: Subject: RE: 4.1 lockup at isa0: on reboot Date: Sun, 27 Aug 2000 15:14:27 -0400 Message-ID: <003901c0105b$05599840$8c6896d1@granitepost.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: <20000827113607.B1209@fw.wintelcom.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > and you ought to be able to get us a traceback by hitting > ctrl-alt-esc, then 't' at the prompt. > > Btw, providing the type of disks and HD controller as well > as a complete "boot -v" output would be a lot more helpful, > if you can hard-reset then boot -v you should be able to > find the file in /var/run/dmesg.boot. > > thanks, > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." OK ... time to go pound joists ... I'll read / try to get trace back later this evening ... Thanks very much for the help. BTW, is it still beating? Cla. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 12:14: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 39AD737B43F for ; Sun, 27 Aug 2000 12:13:59 -0700 (PDT) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 27 Aug 2000 20:13:58 +0100 (BST) Date: Sun, 27 Aug 2000 20:13:57 +0100 From: David Malone To: Simon Cc: "freebsd-hackers@FreeBSD.ORG" Subject: Re: Please help me identify this: Message-ID: <20000827201357.A1488@walton.maths.tcd.ie> References: <200008271702.LAA17882@mail.fpsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200008271702.LAA17882@mail.fpsn.net>; from simon@optinet.com on Sun, Aug 27, 2000 at 01:04:14PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 27, 2000 at 01:04:14PM -0400, Simon wrote: > Can someone please help me identify the following message? I get > it when my freebsd panics and I have to do a cold- reboot. The best thing to try is getting a trace back from the panic. Add "options DDB" to your kernel, recompile and install. Now when it dies you should find it ends up in the kernel debugger. You should be able to type "t" to get a trace of where in the kernel the problem occured. If you can post that, with the output of "dmesg" just after boot, and a copy of your kernel config file that will give people more to work on. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 13:11:32 2000 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 B11BF37B422 for ; Sun, 27 Aug 2000 13:11:24 -0700 (PDT) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id QAA11014 for ; Sun, 27 Aug 2000 16:11:24 -0400 (EDT) Date: Sun, 27 Aug 2000 16:08:06 -0400 (EDT) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Where is PType in /stand/sysinstall defined? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the FDISK-like menu of /stand/sysinstall, the PType (partition type) column is given values like 1,2,3,4,6. While the subtype field is well-defined (e.g., 0xa5 = freebsd), I can not find where the partition type is explained. I also tried PCguide in vain. Can somebody explain this to me? Is it useful or some obsolete feature? Thanks. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 13:28:39 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id CF32537B43E for ; Sun, 27 Aug 2000 13:28:23 -0700 (PDT) Received: from titanic.medinet.si (titanic.medinet.si [212.18.32.66]) by piranha.amis.net (Postfix) with ESMTP id A5C7C5D28; Sun, 27 Aug 2000 22:28:22 +0200 (CEST) Date: Sun, 27 Aug 2000 22:28:22 +0200 (CEST) From: Blaz Zupan X-Sender: blaz@titanic.medinet.si To: Clarence Brown Cc: freebsd-hackers@freebsd.org Subject: RE: 4.1 lockup at isa0: on reboot In-Reply-To: <003701c01051$7a44d2a0$8c6896d1@granitepost.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It IS a Western Digital Caviar AC22000 drive. I > might be able to dig up an even older Seagate for > a test install. Try it, it might work. > How do I make it use the WD driver? Will that > affect the IDE CDROM? Add the following lines to your kernel configuration and remove all line containing "ata". device wdc0 at isa? port IO_WD1 irq 14 device wd0 at wdc0 drive 0 device wd1 at wdc0 drive 1 device wdc1 at isa? port IO_WD2 irq 15 device wd2 at wdc1 drive 0 device wd3 at wdc1 drive 1 If it does indeed work with the wd driver and not with the ata driver, try to get together as much information as possible and send it to sos@freebsd.org. Of course it might not be the same problem I had, but it is still worth a try. Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia E-mail: blaz@amis.net, Tel: +386-2-320-6320, Fax: +386-2-320-6325 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 14:30:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 9C98737B424 for ; Sun, 27 Aug 2000 14:30:08 -0700 (PDT) Received: (qmail 29644 invoked by uid 1000); 27 Aug 2000 21:30:06 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 27 Aug 2000 21:30:06 -0000 Date: Sun, 27 Aug 2000 16:30:06 -0500 (CDT) From: Mike Silbersack To: Clarence Brown Cc: freebsd-hackers@freebsd.org Subject: Re: 4.1 lockup at isa0: on reboot In-Reply-To: <003301c01041$5c3e9da0$8c6896d1@granitepost.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Aug 2000, Clarence Brown wrote: > I just installed 4.1 from CD onto a machine that > had been running 3.4 without problems. The > machine is an old Gateway 486 DX/2 66 (Micronics > Local Bus motherboard) with an upgraded processor, > DVC Turbo 586 using an AMD AM5x68, and 64 Meg ram. > > Problem: If I do a "shutdown -h now" and then press > any key to reboot, the system ALWAYS hangs after > displaying the line.. > > isa0: on motherboard > > This is repeatable, I think it's a bug with the board. I recall working on a Gateway 486/66 a few years ago. After installing a promise BIOS extender card, the system was unable to properly warm boot anymore. (This was running windows 95.) The problem could be related somehow. You're probably best off simply replacing the board. 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 Sun Aug 27 16:33:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thelab.hub.org (nat211.169.mpoweredpc.net [142.177.211.169]) by hub.freebsd.org (Postfix) with ESMTP id 93AC937B424 for ; Sun, 27 Aug 2000 16:33:17 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id UAA05335; Sun, 27 Aug 2000 20:31:43 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Sun, 27 Aug 2000 20:31:43 -0300 (ADT) From: The Hermit Hacker To: Tom Lane Cc: freebsd-hackers@freebsd.org, pgsql-hackers@postgreSQL.org Subject: Re: Too many open files (was Re: spinlock problems reported earlier) In-Reply-To: <25215.967405372@sss.pgh.pa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Aug 2000, Tom Lane wrote: > Hmm, this is interesting: on HPUX, man sysconf(2) says that > sysconf(_SC_OPEN_MAX) returns the max number of open files per process > --- which is what fd.c assumes it means. But I see that on your FreeBSD > box, the sysconf man page defines it as > > _SC_OPEN_MAX > The maximum number of open files per user id. > > which suggests that *on that platform* we need to divide by MAXBACKENDS. > Does anyone know of a more portable way to determine the appropriate > number of open files per backend? Okay, I just checked out Solaris 8/x86, and it confirms what HP/ux thinks: _SC_OPEN_MAX OPEN_MAX Max open files per process I'm curious as to whether FreeBSD is the only one that doesn't follow this "convention"? I'm CCng in the FreeBSD Hackers mailing list to see if someone there might be able to shed some light on this ... my first thought, personally, would be to throw in some sort of: #ifdef __FreeBSD__ max_files_per_backend = sysconf(_SC_OPEN_MAX) / num_of_backends; #else max_files_per_backend = sysconf(_SC_OPEN_MAX); #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 16:33:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id 99E4F37B43C for ; Sun, 27 Aug 2000 16:33:42 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id UAA08794; Sun, 27 Aug 2000 20:17:56 -0400 (EDT) From: "Clarence Brown" To: "'Mike Silbersack'" , Subject: RE: 4.1 lockup at isa0: on reboot Date: Sun, 27 Aug 2000 19:37:35 -0400 Message-ID: <004001c0107f$c7dcc800$8c6896d1@granitepost.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: X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Silbersack Sent: Sunday, August 27, 2000 5:30 PM > > On Sun, 27 Aug 2000, Clarence Brown wrote: > > > I just installed 4.1 from CD onto a machine that > > had been running 3.4 without problems. The > > machine is an old Gateway 486 DX/2 66 (Micronics > > Local Bus motherboard) with an upgraded processor, > > DVC Turbo 586 using an AMD AM5x68, and 64 Meg ram. > > > > Problem: If I do a "shutdown -h now" and then press > > any key to reboot, the system ALWAYS hangs after > > displaying the line.. > > > > isa0: on motherboard > > > > This is repeatable, > > I think it's a bug with the board. I recall > working on a Gateway 486/66 a few years ago. > After installing a promise BIOS extender > card, the system was unable to properly warm > boot anymore. (This was running windows 95.) > > The problem could be related somehow. You're > probably best off simply replacing the board. > > Mike "Silby" Silbersack Yeah, I've had the motherboard/machine for quite a while now, and have had to work through a couple of warts to keep using it. As a matter of fact I had a reboot problem with the board which was heat related under windows9x, as well as windows 3.x when I first bought the board. When ambient temperature was above 72 deg F (old brain cells) the machine would not "reboot" soft, hard, warm, it did not matter. I traced the problem to a single custom logic chip on the mother board which I could use a can of "freeze it" on and alleviate the problem. I had them, Gateway, and later Micronics, send me a replacement motherboard, but the results were exactly the same. This is not the same problem. An obvious difference is that during the reboot process the ATI Mach32 VGA board resets and does a characteristic "blink" on the screen with Red Blue and Green color bands during reset. When the earlier heat related problem was evident the reboot froze before this point. NOW the reboot is proceeding through this, and actually starting the reboot process, including reading initial boot code from the hard drive. Another difference is that under FreeBSD 3.4 it did not have this problem. If I/We can track and solve this problem, other 486 owners, like Blaz may be helped. (BTW we've "GOT" to keep these old 486 systems running because I really LOVE it when I get to tell a colleague how well an old 486 of mine with 32 meg of RAM is performing some gritty network task that they just told me their NT based x00MHZ PIII with X-Hundred Meg of RAM can't handle. It makes for a nice comparison!!) Cla. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 17:14: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 6A6AE37B43C for ; Sun, 27 Aug 2000 17:14:00 -0700 (PDT) Received: (qmail 29990 invoked by uid 1000); 28 Aug 2000 00:13:55 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Aug 2000 00:13:55 -0000 Date: Sun, 27 Aug 2000 19:13:55 -0500 (CDT) From: Mike Silbersack To: Clarence Brown Cc: freebsd-hackers@freebsd.org Subject: RE: 4.1 lockup at isa0: on reboot In-Reply-To: <004001c0107f$c7dcc800$8c6896d1@granitepost.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Aug 2000, Clarence Brown wrote: > problem. An obvious difference is that during > the reboot process the ATI Mach32 VGA board > resets and does a characteristic "blink" on the > screen with Red Blue and Green color bands during reset. When the > earlier heat related problem was evident the reboot froze before this > point. Interesting, I didn't know there were other issues with the board. If I recall, the problem I was having on warm boot was related to the IDE drives not working right too. Perhaps the BIOS is configuring the system in a peculiar way on warm boot that the promise bios / fbsd 4 don't like. Good luck. :) 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 Sun Aug 27 18:29:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 30FFB37B43C for ; Sun, 27 Aug 2000 18:29:26 -0700 (PDT) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id UAA40185; Sun, 27 Aug 2000 20:29:18 -0500 (CDT) (envelope-from dscheidt@enteract.com) Date: Sun, 27 Aug 2000 20:29:17 -0500 (CDT) From: David Scheidt To: Mike Silbersack Cc: Clarence Brown , freebsd-hackers@freebsd.org Subject: RE: 4.1 lockup at isa0: on reboot In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Aug 2000, Mike Silbersack wrote: : :On Sun, 27 Aug 2000, Clarence Brown wrote: : :> problem. An obvious difference is that during :> the reboot process the ATI Mach32 VGA board :> resets and does a characteristic "blink" on the :> screen with Red Blue and Green color bands during reset. When the :> earlier heat related problem was evident the reboot froze before this :> point. : :Interesting, I didn't know there were other issues with the board. If I :recall, the problem I was having on warm boot was related to the IDE :drives not working right too. Perhaps the BIOS is configuring the system :in a peculiar way on warm boot that the promise bios / fbsd 4 don't like. I had a 486 that didn't reset the ISA bus on warm boot. There was a pretty good chance that the network card wouln't work until the box was power cycled. It might well be that you have something similiar going on. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 20:41:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackstar.krsu.edu.kg (blackstar.krsu.edu.kg [195.254.161.130]) by hub.freebsd.org (Postfix) with ESMTP id 2ECD337B42C; Sun, 27 Aug 2000 20:41:48 -0700 (PDT) Received: from krsu.edu.kg (krsu.edu.kg [195.254.164.3]) by blackstar (8.9.1a/8.9.1) with ESMTP id KAA20930; Tue, 1 Aug 2000 10:18:58 +0600 (KGST) Received: from localhost (slash@localhost) by krsu.edu.kg (8.9.3/8.9.3) with ESMTP id JAA98436; Fri, 18 Aug 2000 09:47:19 +0600 (KGST) (envelope-from slash@krsu.edu.kg) Date: Fri, 18 Aug 2000 09:47:19 +0600 (KGST) From: CrazZzy Slash To: securityjobs@securityfocus.com, vuln-dev@securityfocus.com, incident@securityfocus.com, bugtraq@securityfocus.com Cc: misc@openbsd.org, tech@openbsd.org, freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: help Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 20:54:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id D16E037B422; Sun, 27 Aug 2000 20:54:17 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13TG6e-0000Nv-00; Sun, 27 Aug 2000 22:01:09 -0600 Message-ID: <39A9E404.F47030C7@softweyr.com> Date: Sun, 27 Aug 2000 22:01:08 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Jim Flowers Cc: Theo PAGTZIS , Eric Kozowski , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Flowers wrote: > > Last I checked the wi driver will not do IBSS and says so in the > documentation. I also tried it and couldn't get anywhere. Would be nice. You must've last checked a long time ago: DESCRIPTION The wicontrol command controls the operation of WaveLAN/IEEE wireless networking devices via the wi(4) driver. Most of the parameters that can be changed relate to the IEEE 802.11 protocol which the WaveLAN imple- ments. This includes the station name, whether the station is operating in ad-hoc (point to point) or BSS (service set) mode, and the network name of a service set to join (IBSS) if BSS mode is enabled. The wicon- trol command can also be used to view the current settings of these pa- rameters and to dump out the values of the card's statistics counters. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Aug 27 20:56:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from homer.softweyr.com (bsdconspiracy.net [208.187.122.220]) by hub.freebsd.org (Postfix) with ESMTP id 0EA3737B43F; Sun, 27 Aug 2000 20:56:34 -0700 (PDT) Received: from localhost ([127.0.0.1] helo=softweyr.com ident=Fools trust ident!) by homer.softweyr.com with esmtp (Exim 3.16 #1) id 13TG97-0000O4-00; Sun, 27 Aug 2000 22:03:41 -0600 Message-ID: <39A9E49D.A79BF6FD@softweyr.com> Date: Sun, 27 Aug 2000 22:03:41 -0600 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.1-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Jim Flowers Cc: Theo PAGTZIS , Eric Kozowski , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Flowers wrote: > > Last I checked the wi driver will not do IBSS and says so in the > documentation. I also tried it and couldn't get anywhere. Would be nice. Uh, er, if you mean to create a service set, Lucent apparently hasn't seen fit to release that sort of information about the cards yet. I can probably get access to it, but it would be under NDA and therefore not useful. Your best bet is to bug your friendly neighborhood Lucent rep into releaseing the full documentation (and sample source code) to Bill Paul. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 0: 3:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from onoe2.sm.sony.co.jp (onoe2.sm.sony.co.jp [133.138.10.2]) by hub.freebsd.org (Postfix) with ESMTP id 3A96637B43C; Mon, 28 Aug 2000 00:03:30 -0700 (PDT) Received: from duplo.sm.sony.co.jp (onoe@localhost) by onoe2.sm.sony.co.jp (8.9.0/3.7W) with ESMTP id QAA13801; Mon, 28 Aug 2000 16:02:59 +0900 (JST) Received: (from onoe@localhost) by duplo.sm.sony.co.jp (8.11.0/8.10.2) id e7S732S01248; Mon, 28 Aug 2000 16:03:02 +0900 (JST) Date: Mon, 28 Aug 2000 16:03:02 +0900 (JST) From: Atsushi Onoe Message-Id: <200008280703.e7S732S01248@duplo.sm.sony.co.jp> To: wes@softweyr.com Cc: jflowers@peony.ezo.net, T.Pagtzis@cs.ucl.ac.uk, eric@svjava.com, freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS In-Reply-To: Your message of "Sun, 27 Aug 2000 22:03:41 -0600" <39A9E49D.A79BF6FD@softweyr.com> References: <39A9E49D.A79BF6FD@softweyr.com> X-Mailer: Cue version 0.6 (000608-1919/onoe) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Last I checked the wi driver will not do IBSS and says so in the > > documentation. I also tried it and couldn't get anywhere. Would be nice. > > Uh, er, if you mean to create a service set, Lucent apparently hasn't seen > fit to release that sort of information about the cards yet. I can probably > get access to it, but it would be under NDA and therefore not useful. Your > best bet is to bug your friendly neighborhood Lucent rep into releaseing > the full documentation (and sample source code) to Bill Paul. Lucent have shipped newer firmware this March which DOES support creating IBSS. The verision 6.04 of the firmware creates IBSS by setting wicontrol -c 1 with -p 1 (BSS mode), and joins to IBSS if no access points found. It seems that the name of created IBSS follows "network name" specified by -n option, not "SSID" by -q option. Regards, Atsushi Onoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 2:33:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nikias.cc.uoa.gr (nikias.cc.uoa.gr [195.134.68.10]) by hub.freebsd.org (Postfix) with ESMTP id DE28737B424 for ; Mon, 28 Aug 2000 02:33:07 -0700 (PDT) Received: from neutrino.particles.org (nikias.cc.uoa.gr [195.134.68.10]) by nikias.cc.uoa.gr (8.9.3/8.9.3) with ESMTP id MAA07753; Mon, 28 Aug 2000 12:32:47 +0300 (EET DST) Received: (from anteater@localhost) by neutrino.particles.org (8.9.3/8.9.3) id LAA01065; Mon, 28 Aug 2000 11:58:55 +0300 Date: Mon, 28 Aug 2000 11:58:55 +0300 From: Elias Athanasopoulos To: Clarence Brown Cc: freebsd-hackers@freebsd.org Subject: Re: 4.1 lockup at isa0: on reboot Message-ID: <20000828115855.A911@neutrino> References: <003301c01041$5c3e9da0$8c6896d1@granitepost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <003301c01041$5c3e9da0$8c6896d1@granitepost.com>; from clabrown@granitepost.com on Sun, Aug 27, 2000 at 12:10:46PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 27, 2000 at 12:10:46PM -0400, Clarence Brown wrote: > Problem: If I do a "shutdown -h now" and then press > any key to reboot, the system ALWAYS hangs after > displaying the line.. > > isa0: on motherboard I can confirm this for my 486 machine, running -CURRENT. It comes around only via a hard reset. I had the same problem with OpenBSD too, IIRC. Regards, Elias -- Elias Athanasopoulos | I bet the human brain is | H.E.P & Apps. Lab. http://www.uoa.gr/~eatha | a kludge. -Marvin Minsky | University Of Athens To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 2:52:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id 086C137B423; Mon, 28 Aug 2000 02:52:07 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Mon, 28 Aug 2000 10:50:40 +0100 Message-ID: <39AA35ED.BC9E6428@cs.ucl.ac.uk> Date: Mon, 28 Aug 2000 10:50:37 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Wes Peters Cc: Jim Flowers , Theo PAGTZIS , Eric Kozowski , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS References: <39A9E404.F47030C7@softweyr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote: > Jim Flowers wrote: > > > > Last I checked the wi driver will not do IBSS and says so in the > > documentation. I also tried it and couldn't get anywhere. Would be nice. > > You must've last checked a long time ago: > > DESCRIPTION > The wicontrol command controls the operation of WaveLAN/IEEE wireless > networking devices via the wi(4) driver. Most of the parameters that can > be changed relate to the IEEE 802.11 protocol which the WaveLAN imple- > ments. This includes the station name, whether the station is operating > in ad-hoc (point to point) or BSS (service set) mode, and the network > name of a service set to join (IBSS) if BSS mode is enabled. The wicon- > trol command can also be used to view the current settings of these pa- > rameters and to dump out the values of the card's statistics counters. > > -- > "Where am I, and what am I doing in this handbasket?" > > Wes Peters Softweyr LLC > wes@softweyr.com http://softweyr.com/ Wes, quite correct. I considered revisiting the matter non-important since anyone that would use fbsd 3.4 or later should have such features by default...(otherwise wavelan support would be pretty stranded :).. Now, I have my reservations about the card's statistics counters.....I have yet to see working statistics on the wavelan interface...That has *not* been working since 3.4 for me...anyone that can tell me I am wrong...please do as I want to use these stats pretty badly... Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 5: 6:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peony.ezo.net (peony.ezo.net [206.102.130.11]) by hub.freebsd.org (Postfix) with ESMTP id 34E1637B42C; Mon, 28 Aug 2000 05:06:37 -0700 (PDT) Received: from localhost (jflowers@localhost) by peony.ezo.net (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e7SCYsY10486; Mon, 28 Aug 2000 08:34:54 -0400 (EDT) Date: Mon, 28 Aug 2000 08:34:54 -0400 (EDT) From: Jim Flowers To: Wes Peters Cc: Theo PAGTZIS , Eric Kozowski , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS In-Reply-To: <39A9E404.F47030C7@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My point was only that the fbsd wi driver does not appear to allow the creation of a service set as the original poster wanted to do, therefore to use IBSS mode you have to have a WavePointII. From the current wicontrol man page: snip--------------------- Allow the station to create a service set (IBSS). Permitted values are 0 (don't create IBSS) and 1 (enable creation of IBSS). The default is 0. Note: this option is provided for experimental purposes only: enabling the creation of an IBSS on a host system doesn't appear to actually work. --------------- Jim Flowers #4 ranked ISP on C|NET #1 in Ohio On Sun, 27 Aug 2000, Wes Peters wrote: > Jim Flowers wrote: > > > > Last I checked the wi driver will not do IBSS and says so in the > > documentation. I also tried it and couldn't get anywhere. Would be nice. > > You must've last checked a long time ago: > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 5:24: 6 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peony.ezo.net (peony.ezo.net [206.102.130.11]) by hub.freebsd.org (Postfix) with ESMTP id 8E5B137B42C; Mon, 28 Aug 2000 05:23:57 -0700 (PDT) Received: from localhost (jflowers@localhost) by peony.ezo.net (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e7SCqFb10567; Mon, 28 Aug 2000 08:52:15 -0400 (EDT) Date: Mon, 28 Aug 2000 08:52:15 -0400 (EDT) From: Jim Flowers To: Theo PAGTZIS Cc: Wes Peters , Eric Kozowski , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS In-Reply-To: <39AA35ED.BC9E6428@cs.ucl.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seems to work ok on 4.0-RELEASE #0. Jim Flowers #4 ranked ISP on C|NET #1 in Ohio On Mon, 28 Aug 2000, Theo PAGTZIS wrote: > > Wes, > > quite correct. I considered revisiting the matter non-important since anyone > that would > use fbsd 3.4 or later should have such features by default...(otherwise wavelan > support would > be pretty stranded :).. > > Now, I have my reservations about the card's statistics counters.....I have yet to > see working statistics > on the wavelan interface...That has *not* been working since 3.4 for me...anyone > that can tell me I am > wrong...please do as I want to use these stats pretty badly... > > Theo > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 8:21: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lists01.iafrica.com (lists01.iafrica.com [196.7.0.141]) by hub.freebsd.org (Postfix) with ESMTP id 8B33937B43E for ; Mon, 28 Aug 2000 08:20:59 -0700 (PDT) Received: from nwl.fw.uunet.co.za ([196.31.2.162]) by lists01.iafrica.com with esmtp (Exim 3.12 #2) id 13TQiX-0002iR-00 for hackers@freebsd.org; Mon, 28 Aug 2000 17:20:57 +0200 Received: (from nobody@localhost) by nwl.fw.uunet.co.za (8.8.8/8.6.9) id RAA04069 for ; Mon, 28 Aug 2000 17:20:56 +0200 (SAST) Received: by nwl.fw.uunet.co.za via recvmail id 3829; Mon Aug 28 17:19:33 2000 Received: from sheldonh (helo=axl.fw.uunet.co.za) by axl.fw.uunet.co.za with local-esmtp (Exim 3.16 #1) id 13TQhB-000L6m-00 for hackers@FreeBSD.org; Mon, 28 Aug 2000 17:19:33 +0200 From: Sheldon Hearn To: hackers@freebsd.org Subject: Does le(4) have a maintainer? Date: Mon, 28 Aug 2000 17:19:33 +0200 Message-ID: <81143.967475973@axl.fw.uunet.co.za> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Does the le(4) device have a maintainer? I ask because 3 different people have reported that it's unuseable since 4.0-RELEASE (see PR misc/18641). If there's nobody to step forward and maintain the driver, we should probably add an entry about it to the release notes for 4.0-RELEASE and 4.1-RELEASE, both of which currently claim to support the le(4) hardware. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 8:25:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from biology.nmsu.edu (biology.NMSU.Edu [128.123.5.72]) by hub.freebsd.org (Postfix) with ESMTP id 90C8837B423 for ; Mon, 28 Aug 2000 08:25:23 -0700 (PDT) Received: (from brook@localhost) by biology.nmsu.edu (8.8.8/8.8.8) id JAA08118; Mon, 28 Aug 2000 09:24:00 -0600 (MDT) Date: Mon, 28 Aug 2000 09:24:00 -0600 (MDT) Message-Id: <200008281524.JAA08118@biology.nmsu.edu> X-Authentication-Warning: biology.nmsu.edu: brook set sender to brook@biology.nmsu.edu using -f From: Brook Milligan To: tgl@sss.pgh.pa.us Cc: scrappy@hub.org, freebsd-hackers@freebsd.org, pgsql-hackers@postgreSQL.org In-reply-to: <7481.967438652@sss.pgh.pa.us> (message from Tom Lane on Mon, 28 Aug 2000 00:57:32 -0400) Subject: Re: [HACKERS] Re: Too many open files (was Re: spinlock problems reported earlier) References: <7481.967438652@sss.pgh.pa.us> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker writes: > Okay, I just checked out Solaris 8/x86, and it confirms what HP/ux thinks: > _SC_OPEN_MAX OPEN_MAX Max open files per > process > I'm curious as to whether FreeBSD is the only one that doesn't follow this > "convention"? From part of the NetBSD manpage for sysconf(3): DESCRIPTION This interface is defined by IEEE Std1003.1-1988 (``POSIX''). A far more complete interface is available using sysctl(3). _SC_OPEN_MAX The maximum number of open files per user id. _SC_STREAM_MAX The minimum maximum number of streams that a process may have open at any one time. BUGS The value for _SC_STREAM_MAX is a minimum maximum, and required to be the same as ANSI C's FOPEN_MAX, so the returned value is a ridiculously small and misleading number. STANDARDS The sysconf() function conforms to IEEE Std1003.1-1990 (``POSIX''). HISTORY The sysconf function first appeared in 4.4BSD. This suggests that _SC_STREAM_MAX might be a better value to use. On one of my NetBSD boxes I have the following: _SC_OPEN_MAX: 64 _SC_STREAM_MAX: 20 In any case, if this really follows the POSIX standard, perhaps PostgreSQL code should assume these semantics and work around other cases that don't follow the standard (instead of work around the POSIX cases). Cheers, Brook To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 10:56:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id E5B7037B422 for ; Mon, 28 Aug 2000 10:56:24 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id OAA11853; Mon, 28 Aug 2000 14:40:53 -0400 (EDT) From: "Clarence Brown" To: "'Alfred Perlstein'" , Subject: RE: 4.1 lockup at isa0: on reboot Date: Mon, 28 Aug 2000 13:58:32 -0400 Message-ID: <005401c01119$95041060$8c6896d1@granitepost.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: <20000827113607.B1209@fw.wintelcom.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: 'Alfred Perlstein' > Sent: Sunday, August 27, 2000 2:36 PM > > * Clarence Brown [000827 10:59] wrote: > > > -----Original Message----- > > > Behalf Of Alfred Perlstein > > > * Blaz Zupan [000827 09:13] wrote: > > > > Looks like I might have to figure out how to > > setup my system for kernel debug... > > Yes, you can choose to install the source code you can do so by > running /stand/sysinstall and choosing to install the kernel sources, > one doesn't need to know much to figure out how to just get a > traceback. > > It's really just as simple as recomiling your kernel: > > http://www.freebsd.org/handbook/kernelconfig.html > > just add the options I mentioned above: > > > > options DDB > > > options BREAK_TO_DEBUGGER > > and you ought to be able to get us a traceback by hitting > ctrl-alt-esc, then 't' at the prompt. > > Btw, providing the type of disks and HD controller as well > as a complete "boot -v" output would be a lot more helpful, > if you can hard-reset then boot -v you should be able to > find the file in /var/run/dmesg.boot. > OK, I think I configured a debug kernel. I used the config, make depend, make, make install procedure. make depend took about 20 min, make took about 1 hr 20 min. I did a soft reboot: shutdown -h now, hit any key to reboot, hit space at count down, booted with command "boot -v". As before the system proceeded to the "isa0:" line and then locked up. At this point I tried Ctrl-Alt-Esc to enter the debugger, but nothing happened. It seems to be too locked up for the debugger. Maybe I could try hitting Ctrl-Alt-Esc before it gets to the "isa0:" line and stepping through the code up to the error? Any suggestions? Cla. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 10:57:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thelab.hub.org (nat195.206.mpoweredpc.net [142.177.195.206]) by hub.freebsd.org (Postfix) with ESMTP id 2E37C37B424 for ; Mon, 28 Aug 2000 10:57:26 -0700 (PDT) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id OAA70879; Mon, 28 Aug 2000 14:56:28 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 28 Aug 2000 14:56:28 -0300 (ADT) From: The Hermit Hacker To: Tom Lane Cc: freebsd-hackers@freebsd.org, Brook Milligan , pgsql-hackers@postgreSQL.org Subject: Re: [HACKERS] Re: Too many open files (was Re: spinlock problems reported earlier) In-Reply-To: <16545.967483978@sss.pgh.pa.us> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Aug 2000, Tom Lane wrote: > Brook Milligan writes: > > In any case, if this really follows the POSIX standard, perhaps > > PostgreSQL code should assume these semantics and work around other > > cases that don't follow the standard (instead of work around the POSIX > > cases). > > HP asserts that *they* follow the POSIX standard, and in this case > I'm more inclined to believe them than the *BSD camp. A per-process > limit on open files has existed in most Unices I've heard of; I had > never heard of a per-userid limit until yesterday. (And I'm not yet > convinced that that's actually what *BSD implements; are we sure it's > not just a typo in the man page?) > > 64 or so for _SC_OPEN_MAX is not really what I'm worried about anyway. > IIRC, we've heard reports that some platforms return values in the > thousands, ie, essentially telling each process it can have the whole > kernel FD table, and it's that behavior that I'm speculating is causing > Marc's problem. > > Marc, could you check what is returned by sysconf(_SC_OPEN_MAX) on your > box? And/or check to see how many files each backend is actually > holding open? > ./t 4136 > sysctl kern.maxfiles kern.maxfiles: 32768 > cat t.c #include #include main() { printf("%ld\n", sysconf(_SC_OPEN_MAX)); } okay, slightly difficult since they come and go, but using the database that is used for the search engine, with just a psql session: pgsql# lsof -p 85333 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME postgres 85333 pgsql cwd VDIR 13,131088 3072 7936 /pgsql/data2/udmsearch postgres 85333 pgsql rtd VDIR 13,131072 512 2 / postgres 85333 pgsql txt VREG 13,131084 4651486 103175 /pgsql/bin/postgres postgres 85333 pgsql txt VREG 13,131076 77648 212924 /usr/libexec/ld-elf.so.1 postgres 85333 pgsql txt VREG 13,131076 11860 56504 /usr/lib/libdescrypt.so.2 postgres 85333 pgsql txt VREG 13,131076 120736 56525 /usr/lib/libm.so.2 postgres 85333 pgsql txt VREG 13,131076 34336 56677 /usr/lib/libutil.so.3 postgres 85333 pgsql txt VREG 13,131076 154128 57068 /usr/lib/libreadline.so.4 postgres 85333 pgsql txt VREG 13,131076 270100 56532 /usr/lib/libncurses.so.5 postgres 85333 pgsql txt VREG 13,131076 570064 56679 /usr/lib/libc.so.4 postgres 85333 pgsql 0r VCHR 2,2 0t0 7967 /dev/null postgres 85333 pgsql 1w VREG 13,131084 995 762037 /pgsql/logs/postmaster.5432.61308 postgres 85333 pgsql 2w VREG 13,131084 316488878 762038 /pgsql/logs/5432.61308 postgres 85333 pgsql 3r VREG 13,131088 1752 8011 /pgsql/data2/udmsearch/pg_internal.init postgres 85333 pgsql 4u VREG 13,131084 22757376 15922 /pgsql/data/pg_log postgres 85333 pgsql 5u unix 0xd46a3300 0t0 ->0xd469a540 postgres 85333 pgsql 6u VREG 13,131084 8192 15874 /pgsql/data/pg_variable postgres 85333 pgsql 7u VREG 13,131088 16384 7982 /pgsql/data2/udmsearch/pg_class postgres 85333 pgsql 8u VREG 13,131088 32768 7980 /pgsql/data2/udmsearch/pg_class_relname_index postgres 85333 pgsql 9u VREG 13,131088 81920 7985 /pgsql/data2/udmsearch/pg_attribute postgres 85333 pgsql 10u VREG 13,131088 65536 7983 /pgsql/data2/udmsearch/pg_attribute_relid_attnum_index postgres 85333 pgsql 11u VREG 13,131088 8192 7945 /pgsql/data2/udmsearch/pg_trigger postgres 85333 pgsql 12u VREG 13,131088 8192 7993 /pgsql/data2/udmsearch/pg_am postgres 85333 pgsql 13u VREG 13,131088 16384 7977 /pgsql/data2/udmsearch/pg_index postgres 85333 pgsql 14u VREG 13,131088 8192 7988 /pgsql/data2/udmsearch/pg_amproc postgres 85333 pgsql 15u VREG 13,131088 16384 7991 /pgsql/data2/udmsearch/pg_amop postgres 85333 pgsql 16u VREG 13,131088 73728 7961 /pgsql/data2/udmsearch/pg_operator postgres 85333 pgsql 17u VREG 13,131088 16384 7976 /pgsql/data2/udmsearch/pg_index_indexrelid_index postgres 85333 pgsql 18u VREG 13,131088 32768 7960 /pgsql/data2/udmsearch/pg_operator_oid_index postgres 85333 pgsql 19u VREG 13,131088 16384 7976 /pgsql/data2/udmsearch/pg_index_indexrelid_index postgres 85333 pgsql 20u VREG 13,131088 16384 7942 /pgsql/data2/udmsearch/pg_trigger_tgrelid_index postgres 85333 pgsql 21u VREG 13,131084 8192 15921 /pgsql/data/pg_shadow postgres 85333 pgsql 22u VREG 13,131084 8192 15918 /pgsql/data/pg_database postgres 85333 pgsql 23u VREG 13,131088 8192 7952 /pgsql/data2/udmsearch/pg_rewrite postgres 85333 pgsql 24u VREG 13,131088 16384 7941 /pgsql/data2/udmsearch/pg_type postgres 85333 pgsql 25u VREG 13,131088 16384 7940 /pgsql/data2/udmsearch/pg_type_oid_index postgres 85333 pgsql 26u VREG 13,131088 0 7938 /pgsql/data2/udmsearch/pg_user postgres 85333 pgsql 27u VREG 13,131088 188416 7984 /pgsql/data2/udmsearch/pg_attribute_relid_attnam_index postgres 85333 pgsql 28u VREG 13,131088 65536 7959 /pgsql/data2/udmsearch/pg_operator_oprname_l_r_k_index postgres 85333 pgsql 29u VREG 13,131088 16384 7981 /pgsql/data2/udmsearch/pg_class_oid_index postgres 85333 pgsql 30u VREG 13,131088 40960 7948 /pgsql/data2/udmsearch/pg_statistic postgres 85333 pgsql 31u VREG 13,131088 32768 7947 /pgsql/data2/udmsearch/pg_statistic_relid_att_index postgres 85333 pgsql 32u VREG 13,131088 212992 7958 /pgsql/data2/udmsearch/pg_proc postgres 85333 pgsql 33u VREG 13,131088 49152 7957 /pgsql/data2/udmsearch/pg_proc_oid_index when running a vacuum on the database, the only changes appear to be adding (and removing when done) those tables that are currently being vacuumed ... so, it appears, ~48 or so files opened ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 11: 9:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 1D29737B422 for ; Mon, 28 Aug 2000 11:09:05 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7SI91x13424; Mon, 28 Aug 2000 11:09:01 -0700 (PDT) Date: Mon, 28 Aug 2000 11:09:01 -0700 From: "'Alfred Perlstein'" To: Clarence Brown Cc: freebsd-hackers@freebsd.org Subject: Re: 4.1 lockup at isa0: on reboot Message-ID: <20000828110901.Q1209@fw.wintelcom.net> References: <20000827113607.B1209@fw.wintelcom.net> <005401c01119$95041060$8c6896d1@granitepost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <005401c01119$95041060$8c6896d1@granitepost.com>; from clabrown@granitepost.com on Mon, Aug 28, 2000 at 01:58:32PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Clarence Brown [000828 10:56] wrote: > OK, I think I configured a debug kernel. I used the > config, make depend, make, make install procedure. > make depend took about 20 min, make took about 1 hr 20 min. > > I did a soft reboot: shutdown -h now, hit any key to reboot, > hit space at count down, booted with command "boot -v". It'd be more interesting to see what comes after isa0 during the initial cold boot. > As before the system proceeded to the "isa0:" line and then > locked up. At this point I tried Ctrl-Alt-Esc to enter the > debugger, but nothing happened. It seems to be too locked > up for the debugger. > > Maybe I could try hitting Ctrl-Alt-Esc before it gets to > the "isa0:" line and stepping through the code up to the > error? If you do the boot -v on the cold boot we may be able to figure out exactly which driver is causing the problem. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 12:29:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id EEC1B37B422 for ; Mon, 28 Aug 2000 12:29:29 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id QAA12230; Mon, 28 Aug 2000 16:14:01 -0400 (EDT) From: "Clarence Brown" To: "'Alfred Perlstein'" , Subject: RE: 4.1 lockup at isa0: on reboot Date: Mon, 28 Aug 2000 15:31:07 -0400 Message-ID: <005a01c01126$83e49900$8c6896d1@granitepost.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: <20000828110901.Q1209@fw.wintelcom.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: 'Alfred Perlstein' > Sent: Monday, August 28, 2000 2:09 PM > > * Clarence Brown [000828 10:56] wrote: > > OK, I think I configured a debug kernel. I used the > > config, make depend, make, make install procedure. > > make depend took about 20 min, make took about 1 hr 20 min. > > > > I did a soft reboot: shutdown -h now, hit any key to reboot, > > hit space at count down, booted with command "boot -v". > > It'd be more interesting to see what comes after isa0 during the > initial cold boot. > > > As before the system proceeded to the "isa0:" line and then > > locked up. At this point I tried Ctrl-Alt-Esc to enter the > > debugger, but nothing happened. It seems to be too locked > > up for the debugger. > > > > Maybe I could try hitting Ctrl-Alt-Esc before it gets to > > the "isa0:" line and stepping through the code up to the > > error? > > If you do the boot -v on the cold boot we may be able to > figure out exactly which driver is causing the problem. > This is a little weird, but some time ago I decided to play with splash screen option, but it didn't work. The error message was something to the effect of video mode not available. Well, before recording the dmesg.boot I decided to comment out the splash screen lines from loader.conf so the output would be a little cleaner. Now the warm boot lockup still occurs at isa0: BUT boot -v has a few more lines after isa0: which WERE NOT there when the splash screen stuff was in loader.conf. Included below is dmesg.boot from a successful cold boot. The failed warm boot -v stopped after displaying the line "Trying Read_Port at 3c3" 8 lines below the "isa0: on motherboard", just before displaying the line "isa_probe_children: disabling PnP devices". **START dmesg.boot** Copyright (c) 1992-2000 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. FreeBSD 4.1-RELEASE #0: Mon Aug 28 11:01:15 EDT 2000 root@gw01.granitepost.com:/usr/src/sys/compile/486ISADBKERNEL Calibrating clock(s) ... i8254 clock: 1193212 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CPU: AMD Am5x86 Write-Through (486-class CPU) Origin = "AuthenticAMD" Id = 0x4e4 Stepping = 4 Features=0x1 real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x00435000 - 0x03ff7fff, 62664704 bytes (15299 pages) config> di pcic0 config> di psm0 config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di cs0 config> di bt0 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 61104128 (59672K bytes) Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc041c000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc041c0a8. md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0xffffffff pci_open(2): mode 2 enable port (0x0cf8) is 0xff npx0: on motherboard npx0: INT 16 interface isa0: on motherboard Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fe0: not probed (disabled) fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x0000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at port 0x1f0-0x1f7,0x3f6 irq 14 on isa0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x0000 ata1: mask=01 status0=00 status1=ff ata1: mask=01 status0=00 status1=ff ata1: devices = 0x4 ata1 at port 0x170-0x177,0x376 irq 15 on isa0 adv0: not probed (disabled) bt0: not probed (disabled) aha0: not probed (disabled) aic0: not probed (disabled) atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0045 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0 at atkbd0 kbd0: atkbd0, AT 101/102 (2), config:0x1, flags:0x3d0000 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic0: not probed (disabled) pcic1: not probed (disabled) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16450 sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16450 sio2: not probed (disabled) sio3: not probed (disabled) ppc0: parallel port found at 0x3bc ppc0: cannot reserve I/O port range ed0 at port 0x280-0x29f iomem 0xd8000 irq 10 on isa0 bpf: ed0 attached ed0: address 00:20:18:72:e0:59, type NE2000 (16 bit) ie0: not probed (disabled) le0: not probed (disabled) lnc0: not probed (disabled) cs0: not probed (disabled) sn0: not probed (disabled) isa_probe_children: probing PnP devices BIOS Geometries: 0:03220f3f 0..802=803 cylinders, 0..15=16 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: sl0 attached bpf: ppp0 attached new masks: bio 68c040, tty 63001a, net 67041a bpf: lo0 attached bpf: gif0 attached bpf: gif1 attached bpf: gif2 attached bpf: gif3 attached bpf: faith0 attached ad0: ATA-3 disk at ata0 as master ad0: 1907MB (3907008 sectors), 3876 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, BIOSPIO ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 acd0: CDROM drive at ata1 as master acd0: read 5512KB/s (5512KB/s), 128KB buffer, BIOSPIO acd0: Reads: CD-DA stream acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked Mounting root from ufs:/dev/ad0s1a ad0s1: type 0xa5, start 63, end = 3907007, size 3906945 : OK start_init: trying /sbin/init **STOP dmesg.boot** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 12:51:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 690CF37B42C for ; Mon, 28 Aug 2000 12:50:42 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7SJocC17283; Mon, 28 Aug 2000 12:50:38 -0700 (PDT) Date: Mon, 28 Aug 2000 12:50:38 -0700 From: "'Alfred Perlstein'" To: Clarence Brown Cc: freebsd-hackers@freebsd.org Subject: Re: 4.1 lockup at isa0: on reboot Message-ID: <20000828125038.F1209@fw.wintelcom.net> References: <20000828110901.Q1209@fw.wintelcom.net> <005a01c01126$83e49900$8c6896d1@granitepost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <005a01c01126$83e49900$8c6896d1@granitepost.com>; from clabrown@granitepost.com on Mon, Aug 28, 2000 at 03:31:07PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Clarence Brown [000828 12:29] wrote: > > > Now the warm boot lockup still occurs at isa0: BUT boot -v has > a few more lines after isa0: which WERE NOT there when the splash > screen stuff was in loader.conf. Included below is dmesg.boot > from a successful cold boot. The failed warm boot -v stopped > after displaying the line "Trying Read_Port at 3c3" 8 lines below > the "isa0: on motherboard", just before displaying the > line "isa_probe_children: disabling PnP devices". > > **START dmesg.boot** > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, > 1994 [snip] > npx0: on motherboard > npx0: INT 16 interface > isa0: on motherboard > Trying Read_Port at 203 > Trying Read_Port at 243 > Trying Read_Port at 283 > Trying Read_Port at 2c3 > Trying Read_Port at 303 > Trying Read_Port at 343 > Trying Read_Port at 383 > Trying Read_Port at 3c3 > isa_probe_children: disabling PnP devices > isa_probe_children: probing non-PnP devices > fe0: not probed (disabled) > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on > isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Hmm, you used to be able to disable the pnp device (looks like where it may be hanging up). Does anyone know a safe way to disable pnp probes? can you try this patch? It's a complete blind guess but it's be interesting to see if it works, just do this: cd /usr/src/sys/isa ; patch < thisfile then recompile and see what happens Index: pnp.c =================================================================== RCS file: /home/ncvs/src/sys/isa/pnp.c,v retrieving revision 1.6 diff -u -u -r1.6 pnp.c --- pnp.c 2000/07/11 11:49:33 1.6 +++ pnp.c 2000/08/28 19:52:21 @@ -777,6 +777,7 @@ #endif /* Try various READ_DATA ports from 0x203-0x3ff */ +/* for (pnp_rd_port = 0x80; (pnp_rd_port < 0xff); pnp_rd_port += 0x10) { if (bootverbose) printf("Trying Read_Port at %x\n", (pnp_rd_port << 2) | 0x3); @@ -785,6 +786,7 @@ if (num_pnp_devs) break; } +*/ } static device_method_t pnp_methods[] = { -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 13:41:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D6FD637B423 for ; Mon, 28 Aug 2000 13:41:44 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA89634; Mon, 28 Aug 2000 14:41:43 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA04101; Mon, 28 Aug 2000 14:41:28 -0600 (MDT) Message-Id: <200008282041.OAA04101@harmony.village.org> To: Sheldon Hearn Subject: Re: Does le(4) have a maintainer? Cc: hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 28 Aug 2000 17:19:33 +0200." <81143.967475973@axl.fw.uunet.co.za> References: <81143.967475973@axl.fw.uunet.co.za> Date: Mon, 28 Aug 2000 14:41:28 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <81143.967475973@axl.fw.uunet.co.za> Sheldon Hearn writes: : Does the le(4) device have a maintainer? I ask because 3 different : people have reported that it's unuseable since 4.0-RELEASE (see PR : misc/18641). If there's nobody to step forward and maintain the driver, : we should probably add an entry about it to the release notes for : 4.0-RELEASE and 4.1-RELEASE, both of which currently claim to support : the le(4) hardware. I'm not aware of any. I do know that the fe driver, which is also broken in 4.x, does have a few patches floating around to make it work.... The FE cards were popular in Japan a while back. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 14:26:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E2E7037B43F for ; Mon, 28 Aug 2000 14:26:48 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA89858 for ; Mon, 28 Aug 2000 15:26:47 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA04541 for ; Mon, 28 Aug 2000 15:26:32 -0600 (MDT) Message-Id: <200008282126.PAA04541@harmony.village.org> To: hackers@freebsd.org Subject: PCI BIOS Date: Mon, 28 Aug 2000 15:26:32 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anybody have a good interface to pcibios for kernel devices to use? I think I have a need for it with the TI-1225 based pci cardbus bridge card that I have. I need to be able to assign interrupt numbers (or at least get them) for the slot. NetBSD has this functionality and we need it to be a true plug and play OS. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 14:32: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id 0B2F237B422 for ; Mon, 28 Aug 2000 14:31:59 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id SAA12616; Mon, 28 Aug 2000 18:16:38 -0400 (EDT) From: "Clarence Brown" To: "'Alfred Perlstein'" , Subject: RE: 4.1 lockup at isa0: on reboot Date: Mon, 28 Aug 2000 17:33:30 -0400 Message-ID: <005e01c01137$9cf2b880$8c6896d1@granitepost.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: <20000828133415.I1209@fw.wintelcom.net> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: 'Alfred Perlstein' [mailto:bright@wintelcom.net] > Sent: Monday, August 28, 2000 4:34 PM snip > > like your patch just comments out the whole for loop, right? > > Yes > I must admit that being a C coder I just couldn't resist modifying pnp.c a little differently instead of using the patch. I modified the for line to stop after 383 and before 3c3 by changing the comparison in the for statement from "< 0xff" to "< 0xf0". This did indeed do what I expected, stopping the for loop at 383 instead of 3c3, but the machine still locked up and the last line displayed was "Trying Read_Port at 383" instead of 3c3. So, what ever is going awry doesn't seem to involve the 3c3 port specifically. This make was relatively painless since the only change was to pnp.c, so I'll try commenting the whole loop out, and/or adding a printf after the for loop to see if it gets there. > > that's cool, being able to get a traceback from the hang would be > good. > I don't know how to get a trace back from the hang. When I tried what you suggested before, hitting Ctrl-Alt-Esc at the hang, there was no response. It was apparently REALLY hung... I'm used to using a symbolic debugger, where you can set breakpoints based on lines in a source file. The Debug Page seemed to say that wasn't available in DDB. What mechanism can I use in DDB to get close to the error and start single stepping, or what ever? Cla. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 15:28:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wolery.cumb.org (wolery.cumb.org [216.15.97.161]) by hub.freebsd.org (Postfix) with ESMTP id 2E2A337B422 for ; Mon, 28 Aug 2000 15:28:39 -0700 (PDT) Received: (from zack@localhost) by wolery.cumb.org (8.11.0/8.11.0) id e7SMSZh12199 for freebsd-hackers@freebsd.org; Mon, 28 Aug 2000 15:28:35 -0700 From: Zack Weinberg Date: Mon, 28 Aug 2000 15:28:35 -0700 To: freebsd-hackers@freebsd.org Subject: Portability and warnings tweaks for byacc(1)'s skeleton file Message-ID: <20000828152835.Z17776@wolery.cumb.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have noticed and corrected a number of portability problems with byacc's generated parser, also adjusted things so that it does not provoke a couple of gcc warnings that are not commonly requested but that my project uses. More specifically: - stdlib.h is not available in pre-C89 environments. I made its inclusion conditional on __STDC__ || __cplusplus, which is not perfect but will do. Otherwise, I declare malloc and realloc by hand. - 'const' is not available either in K+R C. #define it to nothing if neither __STDC__ nor __cplusplus is defined. - Change the declarations of yyname[] and yyrule[] placed in y.code.c in -r mode to match their actual definitions in y.tab.c. - gcc can be asked to issue warnings if a function definition is seen without a previous prototype - even if the definition is written in prototype form. The project I'm using byacc with has this warning turned on. I therefore added explicit prototypes for both yygrowstack and yyparse, conditioned on __STDC__ || __cplusplus. A patch is appended. Also, I don't have a patch for this, but I have to change the line in the Makefile reading MAN1=yacc.1 yyfix.1 to use MAN= instead, or yyfix.1 is not installed. This may be a problem with my copy of pmake. Please cc: me directly on any responses, I am not subscribed to this list. Thank you. zw --- byacc-1.9.1.orig/skeleton.c +++ byacc-1.9.1/skeleton.c @@ -54,11 +54,13 @@ char *banner[] = { + "#if !(defined(__cplusplus) || __STDC__)", + "#define const", + "#endif", "#ifndef lint", "static char const ", "yyrcsid[] = \"$FreeBSD: src/usr.bin/yacc/skeleton.c,v 1.28 2000/01/17 02:04:06 bde Exp $\";", "#endif", - "#include ", "#define YYBYACC 1", "#define YYMAJOR 1", "#define YYMINOR 9", @@ -84,8 +86,8 @@ "extern const short yytable[];", "extern const short yycheck[];", "#if YYDEBUG", - "extern char *yyname[];", - "extern char *yyrule[];", + "extern const char * const yyname[];", + "extern const char * const yyrule[];", "#endif", 0 }; @@ -127,6 +129,14 @@ char *body[] = { "/* allocate initial stack or double stack size, up to YYMAXDEPTH */", + "#if defined(__cplusplus) || __STDC__", + "#include ", + "static int yygrowstack(void);", + "#else", + "char *malloc();", + "char *realloc();", + "#endif", + "", "static int yygrowstack()", "{", " int newsize, i;", @@ -177,6 +187,7 @@ "#if defined(__cplusplus) || __STDC__", "#define YYPARSE_PARAM_ARG YYPARSE_PARAM_TYPE YYPARSE_PARAM", "#define YYPARSE_PARAM_DECL", + "extern int yyparse (YYPARSE_PARAM_ARG);", "#else /* ! ANSI-C/C++ */", "#define YYPARSE_PARAM_ARG YYPARSE_PARAM", "#define YYPARSE_PARAM_DECL YYPARSE_PARAM_TYPE YYPARSE_PARAM;", To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 15:32:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 50D2537B42C for ; Mon, 28 Aug 2000 15:32:50 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7SMWnx23087; Mon, 28 Aug 2000 15:32:49 -0700 (PDT) Date: Mon, 28 Aug 2000 15:32:49 -0700 From: Alfred Perlstein To: Zack Weinberg Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Portability and warnings tweaks for byacc(1)'s skeleton file Message-ID: <20000828153249.H18862@fw.wintelcom.net> References: <20000828152835.Z17776@wolery.cumb.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000828152835.Z17776@wolery.cumb.org>; from zack@wolery.cumb.org on Mon, Aug 28, 2000 at 03:28:35PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Zack Weinberg [000828 15:28] wrote: > I have noticed and corrected a number of portability problems with > byacc's generated parser, also adjusted things so that it does not > provoke a couple of gcc warnings that are not commonly requested but > that my project uses. > > More specifically: > > - stdlib.h is not available in pre-C89 environments. I made its > inclusion conditional on __STDC__ || __cplusplus, which is not > perfect but will do. Otherwise, I declare malloc and realloc by > hand. Hrm, I'm basically guessing here, but wouldn't you include in that case? Is it possible that you could file this in the PR system? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 17:25:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id 655E737B42C for ; Mon, 28 Aug 2000 17:25:48 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id VAA13128; Mon, 28 Aug 2000 21:10:31 -0400 (EDT) From: "Clarence Brown" To: "'Alfred Perlstein'" , Subject: RE: 4.1 lockup at isa0: on reboot Date: Mon, 28 Aug 2000 20:27:03 -0400 Message-ID: <006601c0114f$db1eeee0$8c6896d1@granitepost.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: <005e01c01137$9cf2b880$8c6896d1@granitepost.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I modified the for line to stop after 383 and before 3c3 by changing the comparison in the for statement from "< 0xff" to "< 0xf0". This did indeed do what I expected, stopping the for loop at 383 instead of 3c3, but the machine still locked up and the last line displayed was "Trying Read_Port at 383" instead of 3c3. So, what ever is going awry doesn't seem to involve the 3c3 port specifically. Next I added another verbose mode printf at the bottom of the loop to print "Done Read_Port at XXX" to see if it was completing that function call. It did printf the "Done" message, so it locked up after this loop. Next, just to be sure I commented out the whole for loop like your suggested patch would have done. This prevented any of the verbose mode messages about Read_Port from being displayed, but the system still locked up after the isa0: message. I tried to figure out where the pnp_identify routine was being called from using grep, but only found it in what looked like a structure definition. I don't know where it's being called from... The system seems to be locking up sometime after pnp_identify but before the line "isa_probe_children: disabling PnP devices" is printed. Any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 18: 4:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93]) by hub.freebsd.org (Postfix) with SMTP id 5B4EA37B43C for ; Mon, 28 Aug 2000 18:04:11 -0700 (PDT) Received: (qmail 49211 invoked from network); 29 Aug 2000 01:04:10 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-03-real.cdsnet.net with SMTP; 29 Aug 2000 01:04:10 -0000 Date: Mon, 28 Aug 2000 18:03:58 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: hackers@freebsd.org Subject: Anyway to ipfw filter based on MAC address? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would love to be able to filter ipfw traffic based on more than just IP. Anybody done anything like this? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 18: 7:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.fpsn.net (mail.fpsn.net [63.224.69.57]) by hub.freebsd.org (Postfix) with ESMTP id 1EA1C37B423 for ; Mon, 28 Aug 2000 18:07:10 -0700 (PDT) Received: from sharky (adsl-151-202-97-90.bellatlantic.net [151.202.97.90]) by mail.fpsn.net (8.9.3/8.9.3) with SMTP id TAA26723; Mon, 28 Aug 2000 19:08:39 -0600 (MDT) (envelope-from simon@optinet.com) Message-Id: <200008290108.TAA26723@mail.fpsn.net> From: "Simon" To: "hackers@FreeBSD.ORG" , "Jaye Mathisen" Date: Mon, 28 Aug 2000 21:10:46 -0400 Reply-To: "Simon" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 2000 (5.0.2195) In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: Anyway to ipfw filter based on MAC address? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What else do you want to filter by? did you read man ipfw? it should tell you all about it. you can filter by uid, type of packets, source, origin, etc.. -Simon On Mon, 28 Aug 2000 18:03:58 -0700 (PDT), Jaye Mathisen wrote: > > >I would love to be able to filter ipfw traffic based on more than just >IP. > >Anybody done anything like this? > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 19: 2:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93]) by hub.freebsd.org (Postfix) with SMTP id 622E137B423 for ; Mon, 28 Aug 2000 19:02:16 -0700 (PDT) Received: (qmail 81193 invoked from network); 29 Aug 2000 02:02:15 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-03-real.cdsnet.net with SMTP; 29 Aug 2000 02:02:15 -0000 Date: Mon, 28 Aug 2000 19:02:03 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Simon Cc: "hackers@FreeBSD.ORG" Subject: Re: Anyway to ipfw filter based on MAC address? In-Reply-To: <200008290108.TAA26723@mail.fpsn.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just exactly what I said in the Subject. I want to filter on the ethernet MAC address. My firewall works fine filtering on IP, now I want to make sure no new nodes come up. I guess I could play some games with arp, but just blocking MAC addresses would suffice. On Mon, 28 Aug 2000, Simon wrote: > What else do you want to filter by? did you read man ipfw? it should tell you all about it. you can filter by uid, type of > packets, source, origin, etc.. > > -Simon > > On Mon, 28 Aug 2000 18:03:58 -0700 (PDT), Jaye Mathisen wrote: > > > > > > >I would love to be able to filter ipfw traffic based on more than just > >IP. > > > >Anybody done anything like this? > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-hackers" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 19:12:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bluerose.windmoon.nu (c255152-a.plstn1.sfba.home.com [24.176.132.48]) by hub.freebsd.org (Postfix) with ESMTP id 516DA37B43C for ; Mon, 28 Aug 2000 19:12:45 -0700 (PDT) Received: from localhost (fengyue@localhost) by bluerose.windmoon.nu (8.10.2/Windmoon/8.10.2) with ESMTP id e7T2BEr15012; Mon, 28 Aug 2000 19:11:14 -0700 (PDT) Date: Mon, 28 Aug 2000 19:11:14 -0700 (PDT) From: FengYue To: Jaye Mathisen Cc: Simon , "hackers@FreeBSD.ORG" Subject: Re: Anyway to ipfw filter based on MAC address? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Also, be able to filter packets based on TTL and SYN Seq value would be useful in some cases too -- quiet a few SYN flood programs had those values hard coded and script kids don't change them. On Mon, 28 Aug 2000, Jaye Mathisen wrote: > > Just exactly what I said in the Subject. I want to filter on the ethernet > MAC address. > > My firewall works fine filtering on IP, now I want to make sure no new > nodes come up. I guess I could play some games with arp, but just > blocking MAC addresses would suffice. > > On Mon, 28 Aug 2000, Simon wrote: > > > What else do you want to filter by? did you read man ipfw? it should tell you all about it. you can filter by uid, type of > > packets, source, origin, etc.. > > > > -Simon > > > > On Mon, 28 Aug 2000 18:03:58 -0700 (PDT), Jaye Mathisen wrote: > > > > > > > > > > >I would love to be able to filter ipfw traffic based on more than just > > >IP. > > > > > >Anybody done anything like this? > > > > > > > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > > >with "unsubscribe freebsd-hackers" in the body of the message > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 19:13:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tabby.kudra.com (gw.kudra.com [199.6.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 5128737B422 for ; Mon, 28 Aug 2000 19:13:38 -0700 (PDT) Received: (from robert@localhost) by tabby.kudra.com (8.9.3/8.9.3) id WAA42391; Mon, 28 Aug 2000 22:13:12 -0400 (EDT) (envelope-from robert) Date: Mon, 28 Aug 2000 22:13:12 -0400 From: Robert Sexton To: Jaye Mathisen Cc: freebsd-hackers@freebsd.org Subject: Re: Anyway to ipfw filter based on MAC address? Message-ID: <20000828221312.A42226@tabby.kudra.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: ; from Jaye Mathisen on Mon, Aug 28, 2000 at 06:03:58PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 28, 2000 at 06:03:58PM -0700, Jaye Mathisen wrote: > > > I would love to be able to filter ipfw traffic based on more than just > IP. > > Anybody done anything like this? How about turning off arp on the network interface, (ifconfig), and using static arp? -- Robert Sexton - robert@kudra.com, Cincinnati OH, USA Put your Nose to the Grindstone! -- Amalgamated Plastic Surgeons and Toolmakers, Ltd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 19:28:33 2000 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 8DFF337B43E for ; Mon, 28 Aug 2000 19:28:30 -0700 (PDT) Received: from localhost (stein@localhost) by wally.eecs.harvard.edu (8.10.0/8.10.0) with ESMTP id e7T2STF02589 for ; Mon, 28 Aug 2000 22:28:30 -0400 (EDT) Date: Mon, 28 Aug 2000 22:28:29 -0400 (EDT) From: Christopher Stein X-Sender: stein@wally To: freebsd-hackers@freebsd.org Subject: remote gdb debugging Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have been trying to connect to a remote gdb debug session via a serial port (null modem cable) and can't seem to get the device right. I've tried the devices: /dev/ttyd* /dev/cuaa0 (as suggested by the freebsd handbook). hhmmm.. any suggestions? /dev/ttyd1 worked for a 3.3/4.0-pre install in the past, but doesn't work for this new system, which is quite similar. thanks -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 19:34:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 08EF037B43F for ; Mon, 28 Aug 2000 19:34:06 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e7T2Xq412192; Tue, 29 Aug 2000 12:03:52 +0930 (CST) (envelope-from grog) Date: Tue, 29 Aug 2000 12:03:52 +0930 From: Greg Lehey To: Christopher Stein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: remote gdb debugging Message-ID: <20000829120352.K11422@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from stein@eecs.harvard.edu on Mon, Aug 28, 2000 at 10:28:29PM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 28 August 2000 at 22:28:29 -0400, Christopher Stein wrote: > > Hello, > > I have been trying to connect to a remote gdb debug session via a serial > port (null modem cable) and can't seem to get the device right. I've tried > the devices: > > /dev/ttyd* > /dev/cuaa0 (as suggested by the freebsd handbook). > > hhmmm.. any suggestions? /dev/ttyd1 worked for a 3.3/4.0-pre install in > the past, but doesn't work for this new system, which is quite similar. Nothing has changed between 4.0 and now. I've had the devil's own job in the past, and I suspect you've hit a different problem. Do you have a breakout box on the line? If so, what's it showing? Also, you've set the sio flags correctly (0x80 or 0x90) on the debugged machine, right? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 20:31:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id D560E37B43C for ; Mon, 28 Aug 2000 20:31:06 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 61B3B1C66; Mon, 28 Aug 2000 23:31:06 -0400 (EDT) Date: Mon, 28 Aug 2000 23:31:06 -0400 From: Bill Fumerola To: Jaye Mathisen Cc: Simon , "hackers@FreeBSD.ORG" Subject: Re: Anyway to ipfw filter based on MAC address? Message-ID: <20000828233106.T33771@jade.chc-chimes.com> References: <200008290108.TAA26723@mail.fpsn.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mrcpu@internetcds.com on Mon, Aug 28, 2000 at 07:02:03PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 28, 2000 at 07:02:03PM -0700, Jaye Mathisen wrote: > > Just exactly what I said in the Subject. I want to filter on the ethernet > MAC address. I guess the "ip" in "ipfw" just wasn't obvious enough that it is an IP firewall tool. You're one layer too low. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 21: 7:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-03-real.cdsnet.net (mail-03-real.cdsnet.net [204.118.244.93]) by hub.freebsd.org (Postfix) with SMTP id F049D37B424 for ; Mon, 28 Aug 2000 21:07:47 -0700 (PDT) Received: (qmail 51754 invoked from network); 29 Aug 2000 04:07:44 -0000 Received: from schizo.cdsnet.net (204.118.244.32) by mail-03-real.cdsnet.net with SMTP; 29 Aug 2000 04:07:44 -0000 Date: Mon, 28 Aug 2000 21:07:32 -0700 (PDT) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Bill Fumerola Cc: Simon , "hackers@FreeBSD.ORG" Subject: Re: Anyway to ipfw filter based on MAC address? In-Reply-To: <20000828233106.T33771@jade.chc-chimes.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can appreciate the sarcasm... However, given today's generally IP-only connected networks, ipfw does not seem to be a necessarily bad place to do this kind of filtering... I only mention it because dummynet could be useful bandwidth limiting to MAC addresses as well. And it never hurts to ask to see if somebody else has hacked it in, even if the command name isn't exactly descriptive... On Mon, 28 Aug 2000, Bill Fumerola wrote: > On Mon, Aug 28, 2000 at 07:02:03PM -0700, Jaye Mathisen wrote: > > > > Just exactly what I said in the Subject. I want to filter on the ethernet > > MAC address. > > I guess the "ip" in "ipfw" just wasn't obvious enough that it is an IP firewall > tool. You're one layer too low. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Aug 28 21:38:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D304A37B43E for ; Mon, 28 Aug 2000 21:38:33 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id AAA92889; Tue, 29 Aug 2000 00:37:45 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 29 Aug 2000 00:37:45 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: Anyway to ipfw filter based on MAC address? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Aug 2000, Jaye Mathisen wrote: > I would love to be able to filter ipfw traffic based on more than just > IP. > > Anybody done anything like this? The OpenBSD bridge filtering code can do this, allowing you to map MAC addresses to specific interfaces, and prevent spoofing, among other things. There's been some talk of restructuring (possibly rewriting) the bridge/filtering code in FreeBSD, and Archie Cobbs has suggested that NetGraph would be a good way to do this. Arbitrary packet filtering would be fairly possible in such an environment, but we don't currently have an implementation that does that. Hopefully in a few months, we'll be able to claim otherwise. Sorry about that! Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 1:27:38 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f267.law7.hotmail.com [216.33.236.145]) by hub.freebsd.org (Postfix) with ESMTP id C9FCB37B424 for ; Tue, 29 Aug 2000 01:27:35 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 29 Aug 2000 01:27:35 -0700 Received: from 212.221.42.252 by lw7fd.law7.hotmail.msn.com with HTTP; Tue, 29 Aug 2000 08:27:35 GMT X-Originating-IP: [212.221.42.252] From: "Fabien Derudder" To: freebsd-hackers@freebsd.org Subject: two graphic boards on the same computer Date: Tue, 29 Aug 2000 08:27:35 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 29 Aug 2000 08:27:35.0687 (UTC) FILETIME=[FBFC0970:01C01192] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG DOes anyone know how to setup two graphic boards on the same computer, running different apps on the two displays ? I didn't find any relevant information in the XF86 doc, so if someone has some experience or doc concerning that kind of things... _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 1:45:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fobos.marketsite.ru (fobos.marketsite.ru [194.226.198.36]) by hub.freebsd.org (Postfix) with ESMTP id 2AE1637B422 for ; Tue, 29 Aug 2000 01:45:08 -0700 (PDT) Received: from bb.marketsite.ru ([194.226.198.1] helo=runnet-gw.marketsite.ru) by fobos.marketsite.ru with esmtp (Exim 3.14 #40) id 13Th0z-000NCH-00; Tue, 29 Aug 2000 12:45:05 +0400 Content-Length: 1089 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 29 Aug 2000 12:47:49 +0400 (MSD) Reply-To: diwil@dataart.com From: diwil@dataart.com To: Fabien Derudder Subject: RE: two graphic boards on the same computer Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Aug-00 Fabien Derudder wrote: > DOes anyone know how to setup two graphic boards on the same computer, > running different apps on the two displays ? I didn't find any relevant > information in the XF86 doc, so if someone has some experience or doc > concerning that kind of things... > do the following: shell# X :0.0 & shell# fvwm -display 0:0.0& shell# X :1.0 & shell# fvwm -display 0:1.0& refer to the X server manual to get a clue about 0:0.0 and 0:1.0. These options may vary if you do not want to share keyboard and stuff between monitors, etc... :) Have fun, Dmitry. -- ********************************************************************** ("`-''-/").___..--''"`-._ (\ Dimmy the Wild UA1ACZ `6_ 6 ) `-. ( ).`-.__.`) DataArt Enterprises, Inc. (_Y_.)' ._ ) `._ `. ``-..-' Serpukhovskaja street, 10 _..`--'_..-_/ /--'_.' ,' Saint Petersburg, Russia (il),-'' (li),' ((!.-' +7 (812) 3261780, 5552490 ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 3: 2:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tokyogw.iij.ad.jp (tokyogw.iij.ad.jp [202.232.15.22]) by hub.freebsd.org (Postfix) with ESMTP id 4695C37B446 for ; Tue, 29 Aug 2000 03:02:39 -0700 (PDT) Received: by tokyogw.iij.ad.jp; id TAA16245; Tue, 29 Aug 2000 19:02:38 +0900 (JST) Received: from mercury.iij.ad.jp(192.168.4.89) by tokyogw.iij.ad.jp via smap (V4.2) id xma016074; Tue, 29 Aug 00 19:01:42 +0900 Received: from localhost (shigeru@localhost [127.0.0.1]) by mercury.iij.ad.jp (8.9.3/8.9.3) with ESMTP id TAA03628; Tue, 29 Aug 2000 19:01:37 +0900 (JST) To: imp@village.org Cc: hackers@freebsd.org Subject: Re: PCI BIOS In-Reply-To: Your message of "Mon, 28 Aug 2000 15:26:32 -0600" <200008282126.PAA04541@harmony.village.org> References: <200008282126.PAA04541@harmony.village.org> X-Mailer: Mew version 1.93b38 on XEmacs 21.2 (Shinjuku) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000829190137J.shigeru@iij.ad.jp> Date: Tue, 29 Aug 2000 19:01:37 +0900 From: YAMAMOTO Shigeru X-Dispatcher: imput version 991025(IM133) Lines: 18 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Warner Losh Subject: PCI BIOS Date: Mon, 28 Aug 2000 15:26:32 -0600 > Anybody have a good interface to pcibios for kernel devices to use? I > think I have a need for it with the TI-1225 based pci cardbus bridge > card that I have. I need to be able to assign interrupt numbers (or > at least get them) for the slot. NetBSD has this functionality and we > need it to be a true plug and play OS. Now I'm wrinting a code to use PCI BIOS/MS$PIR. URL:http://www.bremen.or.jp/shigeru/FreeBSD/CardBus/dev.20000628.tar.gz sys/i386/pci/pci_root.c in my code is using pci interrrupt routing table in a PCI BIOS when assigning an IRQ. ------- YAMAMOTO Shigeru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 3:35:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 2622237B43F for ; Tue, 29 Aug 2000 03:35:28 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id MAA13034; Tue, 29 Aug 2000 12:35:14 +0200 (CEST) (envelope-from asmodai) Date: Tue, 29 Aug 2000 12:35:14 +0200 From: Jeroen Ruigrok van der Werven To: Clarence Brown Cc: "'Alfred Perlstein'" , freebsd-hackers@FreeBSD.ORG Subject: Re: 4.1 lockup at isa0: on reboot Message-ID: <20000829123514.G11707@lucifer.bart.nl> References: <005e01c01137$9cf2b880$8c6896d1@granitepost.com> <006601c0114f$db1eeee0$8c6896d1@granitepost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <006601c0114f$db1eeee0$8c6896d1@granitepost.com>; from clabrown@granitepost.com on Mon, Aug 28, 2000 at 08:27:03PM -0400 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000829 02:30], Clarence Brown (clabrown@granitepost.com) wrote: >I tried to figure out where the pnp_identify routine was >being called from using grep, but only found it in what >looked like a structure definition. I don't know where >it's being called from... /usr/src/sys/isa/pnp.c: DEVMETHOD(device_identify, pnp_identify), /usr/src/sys/sys/bus.h: #define DEVMETHOD KOBJMETHOD /usr/src/sys/sys/kobj.h: #define KOBJMETHOD(NAME, FUNC) { &NAME##_desc, (kobjop_t) FUNC } HTH, -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl You are more than you think, less than you could be... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 5:24:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id 9B7CB37B42C; Tue, 29 Aug 2000 05:24:38 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Tue, 29 Aug 2000 13:22:46 +0100 Message-ID: <39ABAB14.D3001EA@cs.ucl.ac.uk> Date: Tue, 29 Aug 2000 13:22:44 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Jim Flowers Cc: Theo PAGTZIS , Wes Peters , Eric Kozowski , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS and stats References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Flowers wrote: > Seems to work ok on 4.0-RELEASE #0. > > Jim Flowers > #4 ranked ISP on C|NET #1 in Ohio > > On Mon, 28 Aug 2000, Theo PAGTZIS wrote: > > > > Wes, > > > > quite correct. I considered revisiting the matter non-important since anyone > > that would > > use fbsd 3.4 or later should have such features by default...(otherwise wavelan > > support would > > be pretty stranded :).. > > > > Now, I have my reservations about the card's statistics counters.....I have yet to > > see working statistics > > on the wavelan interface...That has *not* been working since 3.4 for me...anyone > > that can tell me I am > > wrong...please do as I want to use these stats pretty badly... > > > > Theo > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message Jim, I have 7 fbsd 4.1 boxes...I do basic ping between machines and then try wicontrol -i wi0 -o all I get is Transmitted unicast frames: 0 Transmitted multicast frames: 0 Transmitted fragments: 0 Transmitted unicast octets: 0 Transmitted multicast octets: 0 Single transmit retries: 0 Multiple transmit retries: 0 Transmit retry limit exceeded: 0 Transmit discards: 0 Transmit discards due to wrong SA: 0 Received unicast frames: 0 Received multicast frames: 0 Received fragments: 0 Received unicast octets: 0 Received multicast octets: 0 Receive FCS errors: 0 Receive discards due to no buffer: 0 Can't decrypt WEP frame: 0 Received message fragments: 0 Received message bad fragments: 0 Is that what you get? Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 5:54:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from net-ninja.com (net-ninja.com [207.244.14.242]) by hub.freebsd.org (Postfix) with ESMTP id 0C99D37B423 for ; Tue, 29 Aug 2000 05:54:46 -0700 (PDT) Received: by net-ninja.com (Postfix, from userid 1000) id 796F96E8E8; Tue, 29 Aug 2000 08:54:39 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by net-ninja.com (Postfix) with ESMTP id 62C93176101; Tue, 29 Aug 2000 08:54:39 -0400 (EDT) Date: Tue, 29 Aug 2000 08:54:39 -0400 (EDT) From: Mike Wade X-Sender: mwade@net-ninja.com To: Jaye Mathisen Cc: hackers@freebsd.org Subject: Re: Anyway to ipfw filter based on MAC address? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Aug 2000, Jaye Mathisen wrote: > I would love to be able to filter ipfw traffic based on more than just > IP. > > Anybody done anything like this? You may want to check out the Ethfw (Ethernet Firewall) patches for FreeBSD at: http://spe.kakito.com/ --- Mike Wade (mwade@cdc.net) Chief Technical Officer CDC Internet, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 6:31:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id E09A537B43E; Tue, 29 Aug 2000 06:31:17 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Tue, 29 Aug 2000 14:30:17 +0100 Message-ID: <39ABBAE7.558D6011@cs.ucl.ac.uk> Date: Tue, 29 Aug 2000 14:30:15 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Bernie Doehner Cc: Jim Flowers , Wes Peters , Eric Kozowski , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS and stats References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bernie, Bernie Doehner wrote: > Quick clarrification is in order.. Are you running wi0 or wl0 driver? I am running the wi0 driver, I am only referring to wi0 driver, nothing else.. > > To the best of my knowledge wicontrol only works with the wi0 driver. > > I only have the first gen NCR full-height ISA cards at my site, so I am > using the wl0 driver, and wicontrol does not work with it. > > Bernie > > On Tue, 29 Aug 2000, Theo PAGTZIS wrote: > > > Jim Flowers wrote: > > > > > Seems to work ok on 4.0-RELEASE #0. > > > > > > Jim Flowers > > > #4 ranked ISP on C|NET #1 in Ohio > > > > > > On Mon, 28 Aug 2000, Theo PAGTZIS wrote: > > > > > > > > Wes, > > > > > > > > quite correct. I considered revisiting the matter non-important since anyone > > > > that would > > > > use fbsd 3.4 or later should have such features by default...(otherwise wavelan > > > > support would > > > > be pretty stranded :).. > > > > > > > > Now, I have my reservations about the card's statistics counters.....I have yet to > > > > see working statistics > > > > on the wavelan interface...That has *not* been working since 3.4 for me...anyone > > > > that can tell me I am > > > > wrong...please do as I want to use these stats pretty badly... > > > > > > > > Theo > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-hackers" in the body of the message > > > > Jim, > > > > I have 7 fbsd 4.1 boxes...I do basic ping between machines and then try wicontrol -i > > wi0 -o > > all I get is > > Transmitted unicast frames: 0 > > Transmitted multicast frames: 0 > > Transmitted fragments: 0 > > Transmitted unicast octets: 0 > > Transmitted multicast octets: 0 > > Single transmit retries: 0 > > Multiple transmit retries: 0 > > Transmit retry limit exceeded: 0 > > Transmit discards: 0 > > Transmit discards due to wrong SA: 0 > > Received unicast frames: 0 > > Received multicast frames: 0 > > Received fragments: 0 > > Received unicast octets: 0 > > Received multicast octets: 0 > > Receive FCS errors: 0 > > Receive discards due to no buffer: 0 > > Can't decrypt WEP frame: 0 > > Received message fragments: 0 > > Received message bad fragments: 0 > > > > Is that what you get? > > > > Theo > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-net" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 7: 4:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailbox.reptiles.org (mailbox.reptiles.org [198.96.117.155]) by hub.freebsd.org (Postfix) with ESMTP id 574F837B424 for ; Tue, 29 Aug 2000 07:04:43 -0700 (PDT) Received: from localhost (1174 bytes) by mailbox.reptiles.org via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Tue, 29 Aug 2000 10:04:42 -0400 (EDT) (Smail-3.2.0.108 1999-Sep-19 #3 built 1999-Oct-27) Date: Tue, 29 Aug 2000 10:04:42 -0400 From: Jim Mercer To: hackers@freebsd.org Subject: problem with 4.1-stable /etc/rc.network Message-ID: <20000829100441.D7777@reptiles.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i figured this would be a quick way to get this fixed: the chunk of code initializing sshd is broken: case ${sshd_enable} in [Yy][Ee][Ss]) if [ ! -f /etc/ssh/ssh_host_key ]; then echo ' creating ssh RSA host key'; /usr/bin/ssh-keygen -N "" -f /etc/ssh/ssh_host_key fi ** if [ ! -f /etc/ssh/ssh_host_dsa_key ]; then ** case ${nisdomainecho ' creating ssh DSA host key'; ** [Nn][Oo] | '') /usr/bin/ssh-keygen -d -N "" -f /etc/ssh/ssh_host_dsa_key ** fi ;; -- [ Jim Mercer jim@reptiles.org +1 416 410-5633 ] [ Reptilian Research -- Longer Life through Colder Blood ] [ Don't be fooled by cheap Finnish imitations; BSD is the One True Code. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 7:14: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fbsd01.granitepost.com (fbsd01.granitepost.com [209.150.104.131]) by hub.freebsd.org (Postfix) with ESMTP id 8B7B537B42C for ; Tue, 29 Aug 2000 07:13:59 -0700 (PDT) Received: from thunder (thunder.granitepost.com [209.150.104.140]) by fbsd01.granitepost.com (8.8.5/8.8.5) with SMTP id KAA15282 for ; Tue, 29 Aug 2000 10:59:01 -0400 (EDT) From: "Clarence Brown" To: Subject: 4.1 lockup side question ... Date: Tue, 29 Aug 2000 10:13:30 -0400 Message-ID: <007a01c011c3$4f6221a0$8c6896d1@granitepost.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 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As you may know I'm bashing about trying to find the point where my 486 based machine locks up on a warm boot. I have been programming embedded system for about 15 years using DOS and later windows based tools. I am slowly going insane trying to use ee in one window, and grep in another to find what I'm looking for in the directory tree that holds the kernel source! OK, so I'm a whimp (I used to like the command line ;) Is there any multi-file editor with an intuitive (read GUI) interface I can run under KDE that provides multi-file regular expression searching and stuff like that? I like to view 2 files at the same time to look at declaration and use at same time for instance. What do you guys use for your development environment. I don't want a religious war, just some pointers to hopefully intuitive and powerful programmer's editors. Being out of my normal editing environment where everything is now intuitive is like being pecked at by a thousand worms... Thanks, Cla. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 7:25:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id A5BAA37B43C for ; Tue, 29 Aug 2000 07:25:38 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id SAA20137; Tue, 29 Aug 2000 18:25:33 +0400 (MSD) Message-Id: <200008291425.SAA20137@aaz.links.ru> Subject: Re: 4.1 lockup side question ... In-Reply-To: <007a01c011c3$4f6221a0$8c6896d1@granitepost.com> from "Clarence Brown" at "Aug 29, 0 10:13:30 am" To: clabrown@granitepost.com (Clarence Brown) Date: Tue, 29 Aug 2000 18:25:33 +0400 (MSD) Cc: freebsd-hackers@FreeBSD.ORG From: "Aleksandr A.Babaylov" MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Clarence Brown writes: [Charset iso-8859-1 unsupported, filtering to ASCII...] > As you may know I'm bashing about trying to find > the point where my 486 based machine locks up > on a warm boot. I have been programming > embedded system for about 15 years using DOS > and later windows based tools. > > I am slowly going insane trying to use ee in one > window, and grep in another to find what I'm looking > for in the directory tree that holds the kernel source! > > OK, so I'm a whimp (I used to like the command line ;) > Is there any multi-file editor with an intuitive (read GUI) > interface I can run under KDE that provides multi-file > regular expression searching and stuff like that? I like to > view 2 files at the same time to look at declaration and > use at same time for instance. ports/editors/xcoral ? with some programming a la MultiEdit > What do you guys use for your development > environment. I don't want a religious war, just some > pointers to hopefully intuitive and powerful programmer's > editors. Being out of my normal editing environment > where everything is now intuitive is like being pecked > at by a thousand worms... -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 7:32:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 38F2937B43C for ; Tue, 29 Aug 2000 07:32:22 -0700 (PDT) Received: (qmail 7860112 invoked from network); 29 Aug 2000 14:32:20 -0000 Received: from r121m50.cybercable.tm.fr (HELO qualys.com) ([195.132.121.50]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 29 Aug 2000 14:32:20 -0000 Message-ID: <39ABCA09.7946B0CE@qualys.com> Date: Tue, 29 Aug 2000 16:34:49 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Re: 4.1 lockup side question ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I would like to suggest you to use vim. It does syntax highlighting, auto-indenting of C code (and good indenting), it supports several windows, scripting, understand regular expressions, and finally, it's lightweight. It has useful macros for C like :make and it supports ctags to browse the source code easily. It even has a little GUI but it's done primarily for console, though. Maxime Henrion Clarence Brown wrote: > As you may know I'm bashing about trying to find > the point where my 486 based machine locks up > on a warm boot. I have been programming > embedded system for about 15 years using DOS > and later windows based tools. > > I am slowly going insane trying to use ee in one > window, and grep in another to find what I'm looking > for in the directory tree that holds the kernel source! > > OK, so I'm a whimp (I used to like the command line ;) > Is there any multi-file editor with an intuitive (read GUI) > interface I can run under KDE that provides multi-file > regular expression searching and stuff like that? I like to > view 2 files at the same time to look at declaration and > use at same time for instance. > > What do you guys use for your development > environment. I don't want a religious war, just some > pointers to hopefully intuitive and powerful programmer's > editors. Being out of my normal editing environment > where everything is now intuitive is like being pecked > at by a thousand worms... > > Thanks, Cla. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 7:44: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kane.rhyason.com (kane.rhyason.com [204.209.142.193]) by hub.freebsd.org (Postfix) with SMTP id 16BF637B43E for ; Tue, 29 Aug 2000 07:43:59 -0700 (PDT) Received: (qmail 43421 invoked by uid 1000); 27 Nov 2019 16:55:16 -0000 Date: Wed, 27 Nov 2019 09:55:16 -0700 From: Jeff Rhyason To: freebsd-hackers@freebsd.org Subject: Collecting waiting statistics (simulation question) Message-ID: <20191127095516.A42415@rhyason.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anybody help me with a project I am working on? I am trying to simulate different memory allocation policies for a discrete event simulation course. Being the guy I am, I decided to collect some real statistics from a real system. The difficulty I've encountered is that I can't find how to make them accessible! Is there a way that I can log a large amount of statistics regarding kernel memory allocator activity and make that accessible to a user process? (Something like Solaris' crash(1m) and kmalog) Thanks in advance for any comments! -Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 8: 2:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7917937B43F for ; Tue, 29 Aug 2000 08:02:49 -0700 (PDT) Received: from billy-club.village.org (billy-club.village.org [10.0.0.3]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA93253; Tue, 29 Aug 2000 09:02:48 -0600 (MDT) (envelope-from imp@billy-club.village.org) Received: from billy-club.village.org (localhost [127.0.0.1]) by billy-club.village.org (8.11.0/8.8.3) with ESMTP id e7TF2kG02479; Tue, 29 Aug 2000 09:02:46 -0600 (MDT) Message-Id: <200008291502.e7TF2kG02479@billy-club.village.org> To: YAMAMOTO Shigeru Subject: Re: PCI BIOS Cc: hackers@freebsd.org In-reply-to: Your message of "Tue, 29 Aug 2000 19:01:37 +0900." <20000829190137J.shigeru@iij.ad.jp> References: <20000829190137J.shigeru@iij.ad.jp> <200008282126.PAA04541@harmony.village.org> Date: Tue, 29 Aug 2000 09:02:46 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000829190137J.shigeru@iij.ad.jp> YAMAMOTO Shigeru writes: : Now I'm wrinting a code to use PCI BIOS/MS$PIR. : URL:http://www.bremen.or.jp/shigeru/FreeBSD/CardBus/dev.20000628.tar.gz : : sys/i386/pci/pci_root.c in my code is using pci interrrupt routing : table in a PCI BIOS when assigning an IRQ. Cool. I'll have to see if that's useful for what I'm doing. I was just trying to get the TI-1225 based cardbus pci card that I have (operating in pci only mode) working with OLDCARD to solve the wi hanging problem that people are reporting. I don't know how huge an effort it is going to be, so it may have to wait for newcard, et al. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 8:47:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 180BB37B422 for ; Tue, 29 Aug 2000 08:47:23 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7TFlJj17313; Tue, 29 Aug 2000 08:47:19 -0700 (PDT) Date: Tue, 29 Aug 2000 08:47:19 -0700 From: Alfred Perlstein To: Jeff Rhyason Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Collecting waiting statistics (simulation question) Message-ID: <20000829084719.V18862@fw.wintelcom.net> References: <20191127095516.A42415@rhyason.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20191127095516.A42415@rhyason.com>; from jeff@rhyason.com on Wed, Nov 27, 2019 at 09:55:16AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jeff Rhyason [000829 07:44] wrote: > Can anybody help me with a project I am working on? I am trying > to simulate different memory allocation policies for a discrete > event simulation course. Being the guy I am, I decided to > collect some real statistics from a real system. The difficulty > I've encountered is that I can't find how to make them accessible! > > Is there a way that I can log a large amount of statistics > regarding kernel memory allocator activity and make that > accessible to a user process? (Something like Solaris' > crash(1m) and kmalog) > > Thanks in advance for any comments! Using a slew of sysctls would make it trivial, have a look at how sysctls are decared. You can then have a process that samples the sysctls from userland. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 9:11:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peony.ezo.net (peony.ezo.net [206.102.130.11]) by hub.freebsd.org (Postfix) with ESMTP id 2DCE637B423; Tue, 29 Aug 2000 09:11:11 -0700 (PDT) Received: from localhost (jflowers@localhost) by peony.ezo.net (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e7TGB2018577; Tue, 29 Aug 2000 12:11:02 -0400 (EDT) Date: Tue, 29 Aug 2000 12:11:01 -0400 (EDT) From: Jim Flowers To: Theo PAGTZIS Cc: Wes Peters , Eric Kozowski , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS and stats In-Reply-To: <39ABAB14.D3001EA@cs.ucl.ac.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nope snip ----------------------- wicontrol -i wi0 -o Transmitted unicast frames: 181061 Transmitted multicast frames: 0 Transmitted fragments: 181161 Transmitted unicast octets: 25702660 Transmitted multicast octets: 0 Single transmit retries: 13557 Multiple transmit retries: 10208 Transmit retry limit exceeded: 15151 Transmit discards: 0 Transmit discards due to wrong SA: 0 Received unicast frames: 215209 Received multicast frames: 11804 Received fragments: 5396844 Received unicast octets: 177192551 Received multicast octets: 969400 Receive FCS errors: 739429 Receive discards due to no buffer: 0 Can't decrypt WEP frame: 0 Received message fragments: 412 Received message bad fragments: 12513 ----------- Jim Flowers #4 ranked ISP on C|NET #1 in Ohio On Tue, 29 Aug 2000, Theo PAGTZIS wrote: > Jim Flowers wrote: > > > Seems to work ok on 4.0-RELEASE #0. > > > > Jim Flowers > > #4 ranked ISP on C|NET #1 in Ohio > > > > On Mon, 28 Aug 2000, Theo PAGTZIS wrote: > > Jim, > > I have 7 fbsd 4.1 boxes...I do basic ping between machines and then try wicontrol -i > wi0 -o > all I get is > Transmitted unicast frames: 0 > Transmitted multicast frames: 0 > Transmitted fragments: 0 > Transmitted unicast octets: 0 > Transmitted multicast octets: 0 > Single transmit retries: 0 > Multiple transmit retries: 0 > Transmit retry limit exceeded: 0 > Transmit discards: 0 > Transmit discards due to wrong SA: 0 > Received unicast frames: 0 > Received multicast frames: 0 > Received fragments: 0 > Received unicast octets: 0 > Received multicast octets: 0 > Receive FCS errors: 0 > Receive discards due to no buffer: 0 > Can't decrypt WEP frame: 0 > Received message fragments: 0 > Received message bad fragments: 0 > > Is that what you get? > > Theo > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 9:26:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kane.rhyason.com (kane.rhyason.com [204.209.142.193]) by hub.freebsd.org (Postfix) with SMTP id 5CBEA37B43C for ; Tue, 29 Aug 2000 09:26:41 -0700 (PDT) Received: (qmail 48110 invoked by uid 1000); 29 Aug 2000 16:26:10 -0000 Date: Tue, 29 Aug 2000 10:26:08 -0600 From: Jeff Rhyason To: freebsd-hackers@freebsd.org Subject: Re: Collecting waiting statistics (simulation question) Message-ID: <20000829102607.B47494@rhyason.com> References: <20191127095516.A42415@rhyason.com> <20000829084719.V18862@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000829084719.V18862@fw.wintelcom.net>; from bright@wintelcom.net on Tue, Aug 29, 2000 at 08:47:19AM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Omigod, Sorry to have resent this ;) I had some very strange things going on with my mail queue, and my clock was thinking it's 2019...! I did implement it with sysctl's and a circular buffer and had fantastic results. I was able to collect average service times and arrival times of memory allocation requests on a per-zone basis, though in my report I only did NAMEI which was pretty trivial since the usage corresponds directly to the files a 'find /' was opening (thus avoiding any sort of overlapping usage but weakening the usefulness of my simulation!). Thanks again to Alfred, Chuck Robey, Peter Jeremy, and Robert Watson for their help! -Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 10:38:29 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id EC07B37B43C for ; Tue, 29 Aug 2000 10:38:25 -0700 (PDT) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id NAA00167; Tue, 29 Aug 2000 13:38:23 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Tue, 29 Aug 2000 13:38:23 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Jeff Rhyason Cc: freebsd-hackers@freebsd.org Subject: Re: Collecting waiting statistics (simulation question) In-Reply-To: <20000829102607.B47494@rhyason.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Feel free to post URLs for both the implementation and resulting paper, as I think they'd be of interest to the community as a whole, allowing us to better understand the impact of real-world behavior on the implementation, as well as providing a foundation for future profiling and modifications. Sounds like cool work, I'd definitely be interested in reading about it. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services On Tue, 29 Aug 2000, Jeff Rhyason wrote: > Omigod, > > Sorry to have resent this ;) I had some very strange things going > on with my mail queue, and my clock was thinking it's 2019...! > > I did implement it with sysctl's and a circular buffer and had > fantastic results. I was able to collect average service times and > arrival times of memory allocation requests on a per-zone basis, though in > my report I only did NAMEI which was pretty trivial since the usage > corresponds directly to the files a 'find /' was opening (thus avoiding any > sort of overlapping usage but weakening the usefulness of my simulation!). > > Thanks again to Alfred, Chuck Robey, Peter Jeremy, and Robert Watson for their > help! > > -Jeff > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 11:23: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wormhole.bluestar.net (wormhole.bluestar.net [208.53.1.61]) by hub.freebsd.org (Postfix) with ESMTP id 21B3637B423 for ; Tue, 29 Aug 2000 11:22:59 -0700 (PDT) Received: from planetwe.com (admin.planetwe.com [64.182.69.146]) by wormhole.bluestar.net (8.10.1/8.10.1) with ESMTP id e7TIMrN25900 for ; Tue, 29 Aug 2000 13:22:53 -0500 (CDT) Message-ID: <39ABFF7A.78513D0@planetwe.com> Date: Tue, 29 Aug 2000 13:22:50 -0500 From: Drew Sanford X-Mailer: Mozilla 4.72 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: MIB's for FreeBSD? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm sorry if this is the wrong place for this question, but usually if you're looking for someone who knows the nitty gritty details, you look to the people that make it a point to know the details. I'm looking for a comprehensive list of snmp MIB's that can be used for monitoring FreeBSD using MRTG. If you know of a list that isn't exactly comprehensive, I'll take what I can get. I'm running FreeBSD 4.0 using ucd-snmp for snmpd. TIA. -- Drew Sanford Systems Administrator Planetwe.com Email: drew@planetwe.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 11:47:49 2000 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 CE28B37B424 for ; Tue, 29 Aug 2000 11:47:45 -0700 (PDT) Received: from localhost (stein@localhost) by wally.eecs.harvard.edu (8.10.0/8.10.0) with ESMTP id e7TIlfW00142 for ; Tue, 29 Aug 2000 14:47:42 -0400 (EDT) Date: Tue, 29 Aug 2000 14:47:41 -0400 (EDT) From: Christopher Stein X-Sender: stein@wally To: freebsd-hackers@freebsd.org Subject: freebsd port of netboot?.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG .. does anyone know if this exists? It would speed up the panic-edit-compile-boot-copy-boot kernel hacking cycle by transforming it to panic-edit-compile-netboot. thnx -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 11:50:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 0147337B422 for ; Tue, 29 Aug 2000 11:50:24 -0700 (PDT) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 8EC909B1F; Tue, 29 Aug 2000 14:50:23 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 8305CBA03; Tue, 29 Aug 2000 14:50:23 -0400 (EDT) Date: Tue, 29 Aug 2000 14:50:23 -0400 (EDT) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Christopher Stein Cc: freebsd-hackers@freebsd.org Subject: Re: freebsd port of netboot?.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Aug 2000, Christopher Stein wrote: > .. does anyone know if this exists? It would > speed up the panic-edit-compile-boot-copy-boot kernel hacking > cycle by transforming it to panic-edit-compile-netboot. > Does this help? jedgar@splat:/usr/ports$ make search key=netboot Port: etherboot-4.6.1 Path: /usr/ports/net/etherboot Info: Netboot FreeBSD a.out/ELF kernels Maint: ambrisko@whistle.com Index: net B-deps: gettext-0.10.35 gmake-3.79.1 nasm-0.98 R-deps: ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 11:56:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id DC8CC37B424 for ; Tue, 29 Aug 2000 11:56:52 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7TIuid22404; Tue, 29 Aug 2000 11:56:44 -0700 (PDT) Date: Tue, 29 Aug 2000 11:56:44 -0700 From: Alfred Perlstein To: Christopher Stein Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: freebsd port of netboot?.. Message-ID: <20000829115644.B18862@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: ; from stein@eecs.harvard.edu on Tue, Aug 29, 2000 at 02:47:41PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Christopher Stein [000829 11:49] wrote: > > .. does anyone know if this exists? It would > speed up the panic-edit-compile-boot-copy-boot kernel hacking > cycle by transforming it to panic-edit-compile-netboot. http://people.freebsd.org/~alfred/pxe/ -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 12: 2:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 4E7EB37B424 for ; Tue, 29 Aug 2000 12:02:23 -0700 (PDT) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id PAA32237; Tue, 29 Aug 2000 15:02:20 -0400 (EDT) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200008291902.PAA32237@blackhelicopters.org> Subject: Re: MIB's for FreeBSD? In-Reply-To: <39ABFF7A.78513D0@planetwe.com> from Drew Sanford at "Aug 29, 2000 1:22:50 pm" To: drew@planetwe.com (Drew Sanford) Date: Tue, 29 Aug 2000 15:02:20 -0400 (EDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just log into th machine in question and type % snmpwalk localhost private .1 This spills out pretty much everything you've got. You can add a few things as described in man snmpd.conf, such as disk capacity, but it's pretty conclusive. If you have trouble with .1, or if the ucd-snmp mibs don't show up, do # snmpwalk localhost private .1.3.6.1.4.1.2021 If you keep an eye on O'Reilly's BSD DevCenter, I have articles on MRTG and SNMP coming up in a few weeks. ==ml > I'm sorry if this is the wrong place for this question, but usually if > you're looking for someone who knows the nitty gritty details, you look > to the people that make it a point to know the details. I'm looking for > a comprehensive list of snmp MIB's that can be used for monitoring > FreeBSD using MRTG. If you know of a list that isn't exactly > comprehensive, I'll take what I can get. I'm running FreeBSD 4.0 using > ucd-snmp for snmpd. TIA. > > > -- > Drew Sanford > Systems Administrator > Planetwe.com > Email: drew@planetwe.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 13:12:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hq.ezo.net (hq.ezo.net [206.150.211.190]) by hub.freebsd.org (Postfix) with ESMTP id DBEE737B422; Tue, 29 Aug 2000 13:12:35 -0700 (PDT) Received: from zinnia (zinnia.ezo.net [206.150.211.129]) by hq.ezo.net (8.9.3/8.9.3) with SMTP id QAA03348; Tue, 29 Aug 2000 16:15:25 -0400 (EDT) (envelope-from jflowers@ezo.net) Message-ID: <003e01c011f4$31770530$81d396ce@ezo.net> From: "Jim Flowers" To: "Atsushi Onoe" , Cc: , References: <39A9E49D.A79BF6FD@softweyr.com> <200008280703.e7S732S01248@duplo.sm.sony.co.jp> Subject: Re: fbsd box acting as a wavelan BS Date: Tue, 29 Aug 2000 16:03:24 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Great. I'll try it. Bummer - it doesn't work. wicontrol dumps on next iteration after -c 1. Latest ISA board I have is Model ISAPC-00 with a barcode of 91805300 010053/C. Do you know how I can tell what version of the firmware I have? I may have to buy a new one (shudder) from Lucent. ----- Original Message ----- From: "Atsushi Onoe" To: Cc: ; ; ; ; Sent: Monday, August 28, 2000 3:03 AM Subject: Re: fbsd box acting as a wavelan BS > > > Last I checked the wi driver will not do IBSS and says so in the > > > documentation. I also tried it and couldn't get anywhere. Would be nice. > > > > Uh, er, if you mean to create a service set, Lucent apparently hasn't seen > > fit to release that sort of information about the cards yet. I can probably > > get access to it, but it would be under NDA and therefore not useful. Your > > best bet is to bug your friendly neighborhood Lucent rep into releaseing > > the full documentation (and sample source code) to Bill Paul. > > Lucent have shipped newer firmware this March which DOES support creating > IBSS. The verision 6.04 of the firmware creates IBSS by setting wicontrol > -c 1 with -p 1 (BSS mode), and joins to IBSS if no access points found. > It seems that the name of created IBSS follows "network name" specified by > -n option, not "SSID" by -q option. > > Regards, > > Atsushi Onoe > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 13:28:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id F279237B424; Tue, 29 Aug 2000 13:28:43 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Tue, 29 Aug 2000 21:28:25 +0100 Message-ID: <39AC1CE5.70C4FA9@cs.ucl.ac.uk> Date: Tue, 29 Aug 2000 21:28:21 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Jim Flowers Cc: Atsushi Onoe , wes , freebsd-hackers , freebsd-net Subject: Re: fbsd box acting as a wavelan BS References: <39A9E49D.A79BF6FD@softweyr.com> <200008280703.e7S732S01248@duplo.sm.sony.co.jp> <003e01c011f4$31770530$81d396ce@ezo.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Flowers wrote: > Great. I'll try it. Bummer - it doesn't work. wicontrol dumps on next > iteration after -c 1. > > Latest ISA board I have is Model ISAPC-00 with a barcode of 91805300 > 010053/C. Do you know how I can tell what version of the firmware I have? > I may have to buy a new one (shudder) from Lucent. > > ----- Original Message ----- > From: "Atsushi Onoe" > To: > Cc: ; ; ; > ; > Sent: Monday, August 28, 2000 3:03 AM > Subject: Re: fbsd box acting as a wavelan BS > > > > > Last I checked the wi driver will not do IBSS and says so in the > > > > documentation. I also tried it and couldn't get anywhere. Would be > nice. > > > > > > Uh, er, if you mean to create a service set, Lucent apparently hasn't > seen > > > fit to release that sort of information about the cards yet. I can > probably > > > get access to it, but it would be under NDA and therefore not useful. > Your > > > best bet is to bug your friendly neighborhood Lucent rep into releaseing > > > the full documentation (and sample source code) to Bill Paul. > > > > Lucent have shipped newer firmware this March which DOES support creating > > IBSS. The verision 6.04 of the firmware creates IBSS by setting wicontrol > > -c 1 with -p 1 (BSS mode), and joins to IBSS if no access points found. > > It seems that the name of created IBSS follows "network name" specified by > > -n option, not "SSID" by -q option. > > > > Regards, > > > > Atsushi Onoe > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message Jim, I think the firmware is not with the ISA bridge but with the wavelan card...If it is what I think then you should be able to upgrade the firmware through a windows box with the facility they provide together with the firmware upgrade.. Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 14:46:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from camus.cybercable.fr (camus.cybercable.fr [212.198.0.200]) by hub.freebsd.org (Postfix) with SMTP id 8E66E37B42C for ; Tue, 29 Aug 2000 14:46:53 -0700 (PDT) Received: (qmail 8033732 invoked from network); 29 Aug 2000 21:46:51 -0000 Received: from r121m50.cybercable.tm.fr (HELO qualys.com) ([195.132.121.50]) (envelope-sender ) by camus.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 29 Aug 2000 21:46:51 -0000 Message-ID: <39AC2FDF.D09CB511@qualys.com> Date: Tue, 29 Aug 2000 23:49:19 +0200 From: Maxime Henrion X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Modification of the default configuration of sendmail request Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, A very useful feature of sendmail is not activated by default : genericstable. It does the opposite of what virtusertable do. The following lines should be appended to the freebsd.mc file : FEATURE(genericstable, `hash -o /etc/mail/genericstable')dnl GENERICS_DOMAIN_FILE(`/etc/mail/generics-domains')dnl Perhaps it would be nice to disallow VRFY and EXPN commands by default too. This can be easily done by adding goaway to the PrivacyOptions (and so put O PrivacyOptions=authwarnings,goaway). Hoping this will help. Regards, Maxime Henrion To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 15: 7:35 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id AC38037B43C for ; Tue, 29 Aug 2000 15:07:30 -0700 (PDT) Received: from james by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13TOIx-0008vY-00 for hackers@freebsd.org; Mon, 28 Aug 2000 08:46:23 -0400 Date: Mon, 28 Aug 2000 08:46:23 -0400 From: James FitzGibbon To: hackers@freebsd.org Subject: Determining multi or single user ? Message-ID: <20000828084623.C32812@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings... Is there an standard programmatic method for determining if a FreeBSD system is running in single or multi-user ? Sysctl doesn't seem to have a specific entry, but I suspect that the value of other less-well defined sysctl values might allow me to infer what I need. Any thoughts ? -- j. James FitzGibbon james@targetnet.com Targetnet.com Inc. Voice/Fax +1 416 306-0466/0452 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 15:31:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C2AFB37B9A8 for ; Tue, 29 Aug 2000 15:31:23 -0700 (PDT) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e7TMVMN28527; Tue, 29 Aug 2000 15:31:22 -0700 (PDT) Date: Tue, 29 Aug 2000 15:31:22 -0700 From: Alfred Perlstein To: James FitzGibbon Cc: hackers@FreeBSD.ORG Subject: Re: Determining multi or single user ? Message-ID: <20000829153122.E18862@fw.wintelcom.net> References: <20000828084623.C32812@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i In-Reply-To: <20000828084623.C32812@targetnet.com>; from james@targetnet.com on Mon, Aug 28, 2000 at 08:46:23AM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * James FitzGibbon [000829 15:08] wrote: > Greetings... > > Is there an standard programmatic method for determining if a FreeBSD system > is running in single or multi-user ? Sysctl doesn't seem to have a specific > entry, but I suspect that the value of other less-well defined sysctl values > might allow me to infer what I need. > > Any thoughts ? > the kernel is not really aware of the difference between single user mode and multiuser, an interesting hack might be to make init use setproctitle() to indicate whether it's in single user mode or not. does anyone know if this could cause problems? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Aug 29 22:11:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.uni-bielefeld.de (mail2.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 2CCAC37B42C for ; Tue, 29 Aug 2000 22:11:34 -0700 (PDT) Received: from frolic.no-support.loc (ppp36-335.hrz.uni-bielefeld.de [129.70.37.79]) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.4.0.2000.05.17.04.13.p6) with ESMTP id <0G03002I0AF684@mail.uni-bielefeld.de> for freebsd-hackers@FreeBSD.ORG; Wed, 30 Aug 2000 07:11:32 +0200 (MET DST) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id FAA03945; Wed, 30 Aug 2000 05:30:00 +0200 (CEST envelope-from bjoern) Date: Wed, 30 Aug 2000 05:30:00 +0200 From: Bjoern Fischer Subject: Re: socket option IP_MULTICAST_LOOP has no effect? In-reply-to: ; from vmukkama@gmu.edu on Tue, Aug 29, 2000 at 03:56:25PM -0400 To: Vinod Mukkamala Cc: freebsd-hackers@FreeBSD.ORG Message-id: <20000830052959.C873@frolic.no-support.loc> MIME-version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-disposition: inline Content-transfer-encoding: quoted-printable User-Agent: Mutt/1.2.4i References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 29, 2000 at 03:56:25PM -0400, Vinod Mukkamala wrote: > For some reason setsockopt function takes in the a address of a char > as the 4th argument only. [code example typos corrected] >=20 > int tmp =3D 0; // to disable loop back > setsockopt(s, > IPPROTO_IP, > IP_MULTICAST_LOOP, > (char *)&tmp, > sizeof(tmp)); >=20 > and it didn't work...=20 >=20 > but=20 >=20 > char tmp =3D 0; // to disable loop back > setsockopt(s, > IPPROTO_IP, > IP_MULTICAST_LOOP, > (char *)&tmp, > sizeof(tmp)); >=20 > works perfectly fine.=20 Thank you a lot for your help, I will try this as soon as possible, but there's something weird: case IP_MULTICAST_LOOP: /* * Set the loopback flag for outgoing multicast packets. * Must be zero or one. The original multicast API required a * char argument, which is inconsistent with the rest * of the socket API. We allow either a char or an int. */ if (sopt->sopt_valsize =3D=3D 1) { u_char loop; error =3D sooptcopyin(sopt, &loop, 1, 1); if (error) break; imo->imo_multicast_loop =3D !!loop; } else { u_int loop; error =3D sooptcopyin(sopt, &loop, sizeof loop, sizeof loop); if (error) break; imo->imo_multicast_loop =3D !!loop; } break; This piece of code is out of FreeBSD 4-STABLE's kernel source. As you see it should deal with both: ints *and* chars. The code seems to be correct, so I wonder why it's not working with ints. Bj=F6rn Fischer --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 1: 6:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 2371737B424 for ; Wed, 30 Aug 2000 01:06:46 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id KAA23412 for hackers@freebsd.org; Wed, 30 Aug 2000 10:06:45 +0200 (CEST) (envelope-from asmodai) Date: Wed, 30 Aug 2000 10:06:44 +0200 From: Jeroen Ruigrok van der Werven To: hackers@freebsd.org Subject: newsyslog Message-ID: <20000830100644.C22992@lucifer.bart.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anybody confirm that the examples in newsyslog's manpage for things like: $MLD0 , $M1D0 and such actually work. No matter which I use I keep getting these mails from newsyslog: newsyslog: malformed interval/at: /var/log/news/news.notice 644 2 * $M1D0 Z AFAIK this should be a good working interval. Thanks, -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl You are more than you think, less than you could be... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 1:32: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 13FF337B43C for ; Wed, 30 Aug 2000 01:32:06 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.9.3/8.9.3) id KAA23677; Wed, 30 Aug 2000 10:32:00 +0200 (CEST) (envelope-from asmodai) Date: Wed, 30 Aug 2000 10:31:59 +0200 From: Jeroen Ruigrok van der Werven To: Clarence Brown Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: 4.1 lockup side question ... Message-ID: <20000830103159.C23417@lucifer.bart.nl> References: <007a01c011c3$4f6221a0$8c6896d1@granitepost.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <007a01c011c3$4f6221a0$8c6896d1@granitepost.com>; from clabrown@granitepost.com on Tue, Aug 29, 2000 at 10:13:30AM -0400 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000829 16:15], Clarence Brown (clabrown@granitepost.com) wrote: >I am slowly going insane trying to use ee in one >window, and grep in another to find what I'm looking >for in the directory tree that holds the kernel source! Try glimpse. /usr/local/bin/glimpseindex -o -w 1100 -B -H /home/asmodai/glimpse/FreeBSD -M 14 /usr/src alias fglimpse='glimpse -H ~/glimpse/FreeBSD/' fglimpse DEVMETHOD will then show all files which have DEVMETHOD in it. >OK, so I'm a whimp (I used to like the command line ;) >Is there any multi-file editor with an intuitive (read GUI) >interface I can run under KDE that provides multi-file >regular expression searching and stuff like that? I like to >view 2 files at the same time to look at declaration and >use at same time for instance. vim and then :window new >What do you guys use for your development >environment. I don't want a religious war, just some >pointers to hopefully intuitive and powerful programmer's >editors. Being out of my normal editing environment >where everything is now intuitive is like being pecked >at by a thousand worms... vim, glimpse, not much else. Nothing X at least. -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl You are more than you think, less than you could be... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 1:34:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.research.kpn.com (hermes.research.kpn.com [139.63.192.8]) by hub.freebsd.org (Postfix) with ESMTP id DB6B137B424 for ; Wed, 30 Aug 2000 01:34:15 -0700 (PDT) Received: from l04.research.kpn.com (l04.research.kpn.com [139.63.192.204]) by research.kpn.com (PMDF V5.2-31 #42699) with ESMTP id <01JTKTJZF4LC000ECF@research.kpn.com> for freebsd-hackers@freebsd.org; Wed, 30 Aug 2000 10:34:14 +0200 Received: by l04.research.kpn.com with Internet Mail Service (5.5.2650.21) id ; Wed, 30 Aug 2000 10:34:13 +0100 Content-return: allowed Date: Wed, 30 Aug 2000 10:34:12 +0100 From: "Koster, K.J." Subject: Microtime acting up again To: 'FreeBSD Hackers mailing list' Message-id: <59063B5B4D98D311BC0D0001FA7E4522026D77F5@l04.research.kpn.com> MIME-version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear All, Last night my machine drowned in "microtime going backwards" errors. It was there when I installed FreeBSD 4.0-release, and it went away when I cvsupped to -stable immediately after. However, it is back again. My box is an AMD Athlon on an Asus k7v motherboard. I had cvsupped to 4.1-stable this monday night. I was dialed into my ISP, when my machine became sluggish. The console was spitting "microtime going backward" messages as fast as my video board would allow. Under the flood I was able to shut down most applications and type "reboot" in a root shell I happened to have open. The machine came back up, but my mouse (logitech cordless) was crippled and spitting out psmintr out of sync errors at me. An hour of power off eventually cured the problem. Anyone on this list who can explain what this microtime problem is about? I used to be able to reproduce it by running bonnie on my disks. I might do that again this weekend, if I find the time. Kees Jan ================================================= TV is the worst of both worlds. It's not as good at words as radio is because the pictures are a distraction which demand attention, and it's not as good as cinema because the pictures are not nearly as good. [Douglas Adams] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 1:42: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6DD0B37B422 for ; Wed, 30 Aug 2000 01:42:06 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA86659; Wed, 30 Aug 2000 10:42:27 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008300842.KAA86659@freebsd.dk> Subject: Re: Microtime acting up again In-Reply-To: <59063B5B4D98D311BC0D0001FA7E4522026D77F5@l04.research.kpn.com> from "Koster, K.J." at "Aug 30, 2000 10:34:12 am" To: K.J.Koster@kpn.com (Koster, K.J.) Date: Wed, 30 Aug 2000 10:42:27 +0200 (CEST) Cc: freebsd-hackers@FreeBSD.ORG ('FreeBSD Hackers mailing list') X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Koster, K.J. wrote: You should disable APM and not have it in your kernel either, that fixed it for me on my Abit KA7... > Last night my machine drowned in "microtime going backwards" errors. It was > there when I installed FreeBSD 4.0-release, and it went away when I cvsupped > to -stable immediately after. However, it is back again. > > My box is an AMD Athlon on an Asus k7v motherboard. I had cvsupped to > 4.1-stable this monday night. I was dialed into my ISP, when my machine > became sluggish. The console was spitting "microtime going backward" > messages as fast as my video board would allow. > > Under the flood I was able to shut down most applications and type "reboot" > in a root shell I happened to have open. The machine came back up, but my > mouse (logitech cordless) was crippled and spitting out psmintr out of sync > errors at me. An hour of power off eventually cured the problem. > > Anyone on this list who can explain what this microtime problem is about? > > I used to be able to reproduce it by running bonnie on my disks. I might do > that again this weekend, if I find the time. > > Kees Jan > > ================================================= > TV is the worst of both worlds. It's not as > good at words as radio is because the pictures > are a distraction which demand attention, and > it's not as good as cinema because the pictures > are not nearly as good. [Douglas Adams] > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 11:36:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B199F37B43F for ; Wed, 30 Aug 2000 11:36:42 -0700 (PDT) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA99062; Wed, 30 Aug 2000 12:36:41 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA17828; Wed, 30 Aug 2000 12:36:19 -0600 (MDT) Message-Id: <200008301836.MAA17828@harmony.village.org> To: Christopher Stein Subject: Re: freebsd port of netboot?.. Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Tue, 29 Aug 2000 14:47:41 EDT." References: Date: Wed, 30 Aug 2000 12:36:19 -0600 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Christopher Stein writes: : .. does anyone know if this exists? It would : speed up the panic-edit-compile-boot-copy-boot kernel hacking : cycle by transforming it to panic-edit-compile-netboot. I usually mount everything readonly when I try a new module just before loading it. It saves a tone of time. All I gotta fsck on the way back up is /var since it won't mount ro after syslog starts, which makes sense if you think about it. mount -ur / mount -ur /usr moutn -ur /junk is what I have in a script. After it succeeds, I do a mount -uwa which updates all the mounts. You can also netboot via a ROM on your ethernet card or via floppy, but I've not done that. The above works well enough for me. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 14:51: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ntmail1.ener.com (ntmail1.ener.com [208.176.100.25]) by hub.freebsd.org (Postfix) with ESMTP id 97D8A37B43C for ; Wed, 30 Aug 2000 14:50:00 -0700 (PDT) Received: by ntmail1.ener.com with Internet Mail Service (5.5.2650.21) id ; Wed, 30 Aug 2000 16:49:43 -0500 Message-ID: <51F410294EBDD3118F6600805F8B207833B31A@ntmail1.ener.com> From: "Deakle, Jeff H." To: "'freebsd-hackers@freebsd.org'" Subject: Kernel ? Date: Wed, 30 Aug 2000 16:49:42 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C012CC.347FC630" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C012CC.347FC630 Content-Type: text/plain; charset="iso-8859-1" I have an odd thing happening. I have to Kernel config file that are the same except for two lines that are both remarked out. When each is compiled (without debug) one is 2.2meg and the other is over 8 meg. I have included the to files below. I assume there is a hidden character in the file some where. Could someone take a look and see if they can find the problem? The first config is the 8 meg. --------------------------------------------------------------- # # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # 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 2000/03/09 16:32:55 jlemon Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU cpu I586_CPU cpu I686_CPU ident GENERIC 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 FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required 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 extentions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): options NCPU=2 # number of CPUs options NBUS=4 # number of busses options NAPIC=1 # number of IO APICs options NINTR=24 # number of INTs device isa #device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device fd1 at fdc0 drive 1 # 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 #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device dpt # DPT Smartcache - See LINT for options! #device isp # Qlogic family #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets) #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 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? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support #device card #device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 #device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 #device sio2 at isa? disable port IO_COM3 irq 5 #device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device tx # SMC 9432TX (83c170 ``EPIC'') #device vx # 3Com 3c590, 3c595 (``Vortex'') #device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. #device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #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 vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ex #device ep # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. #device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. #device an # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device fe0 at isa? port 0x300 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 4 # 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 # USB support #device uhci # UHCI PCI->USB interface #device ohci # OHCI PCI->USB interface #device usb # USB Bus (required) #device ugen # Generic #device uhid # "Human Interface Devices" #device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da #device ums # Mouse # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet #device snd0 device pcm --------------------------------------------------------------- --------------------------------------------------------------- # Kernel from Kevin # GENERIC -- Generic kernel configuration file for FreeBSD/i386 # # 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 2000/03/09 16:32:55 jlemon Exp $ machine i386 #cpu I386_CPU #cpu I486_CPU cpu I586_CPU cpu I686_CPU ident CANCRI 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 FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, NFS required options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root, CD9660 required 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 extentions options _KPOSIX_PRIORITY_SCHEDULING options ICMP_BANDLIM #Rate limit bad replies # To make an SMP kernel, the next two are needed options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): options NCPU=2 # number of CPUs options NBUS=4 # number of busses options NAPIC=1 # number of IO APICs options NINTR=24 # number of INTs device isa #device eisa device pci # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 #device fd1 at fdc0 drive 1 # 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 #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers #device ahb # EISA AHA1742 family #device ahc # AHA2940 and onboard AIC7xxx devices #device amd # AMD 53C974 (Teckram DC-390(T)) #device dpt # DPT Smartcache - See LINT for options! #device isp # Qlogic family #device ncr # NCR/Symbios Logic device sym # NCR/Symbios Logic (newer chipsets) #device adv0 at isa? #device adw #device bt0 at isa? #device aha0 at isa? #device aic0 at isa? # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sa # Sequential Access (tape etc) device cd # CD device pass # Passthrough device (direct SCSI access) # RAID controllers #device ida # Compaq Smart RAID #device amr # AMI MegaRAID #device mlx # Mylex DAC960 family # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 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? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server on a vt console #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support #device card #device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 #device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 disable # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 #device sio2 at isa? disable port IO_COM3 irq 5 #device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? irq 7 device ppbus # Parallel port bus (required) device lpt # Printer device plip # TCP/IP over parallel device ppi # Parallel port interface device #device vpo # Requires scbus and da # PCI Ethernet NICs. #device de # DEC/Intel DC21x4x (``Tulip'') device fxp # Intel EtherExpress PRO/100B (82557, 82558) #device tx # SMC 9432TX (83c170 ``EPIC'') #device vx # 3Com 3c590, 3c595 (``Vortex'') #device wx # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. #device miibus # MII bus support #device dc # DEC/Intel 21143 and various workalikes #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 vr # VIA Rhine, Rhine II #device wb # Winbond W89C840F #device xl # 3Com 3c90x (``Boomerang'', ``Cyclone'') # ISA Ethernet NICs. #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ex #device ep # WaveLAN/IEEE 802.11 wireless NICs. Note: the WaveLAN/IEEE really # exists only as a PCMCIA device, so there is no ISA attatement needed # and resources will always be dynamically assigned by the pccard code. #device wi # Aironet 4500/4800 802.11 wireless NICs. Note: the declaration below will # work for PCMCIA and PCI cards, as well as ISA cards set to ISA PnP # mode (the factory default). If you set the switches on your ISA # card for a manually chosen I/O address and IRQ, you must specify # those paremeters here. #device an # The probe order of these is presently determined by i386/isa/isa_compat.c. #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device fe0 at isa? port 0x300 #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device cs0 at isa? port 0x300 #device sn0 at isa? port 0x300 irq 10 # requires PCCARD (PCMCIA) support to be activated #device xe0 at isa? # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device sl 1 # Kernel SLIP pseudo-device ppp 1 # Kernel PPP pseudo-device tun # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" pseudo-device gif 4 # 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 # USB support #device uhci # UHCI PCI->USB interface #device ohci # OHCI PCI->USB interface #device usb # USB Bus (required) #device ugen # Generic #device uhid # "Human Interface Devices" #device ukbd # Keyboard #device ulpt # Printer #device umass # Disks/Mass storage - Requires scbus and da #device ums # Mouse # USB Ethernet, requires mii #device aue # ADMtek USB ethernet #device cue # CATC USB ethernet #device kue # Kawasaki LSI USB ethernet #device snd0 #device pcm0 at isa? port ? tty irq 10 drq 1 flags 0x0 device pcm --------------------------------------------------------------------- Thanks for the help. Jeff Deakle Direct = (281)721-4680 Fax = (281)721-4600 ------_=_NextPart_001_01C012CC.347FC630 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Kernel ?

I have an odd thing happening.  I have to Kernel = config file that are the same except for two lines that are both = remarked out. 

When each is compiled (without debug) one is 2.2meg = and the other is over 8 meg.  I have included the to files = below.  I assume there is a hidden character in the file some = where. 

Could someone take a look and see if they can find = the problem?

The first config is the 8 meg.


---------------------------------------------------------------=
#
# GENERIC -- Generic kernel configuration file for = FreeBSD/i386
#
# For more information on this file, please read the = handbook section on
# Kernel Configuration Files:
#
#    http://www.freebsd.org/handbook/kernelconfig-config.ht= ml
#
# 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 = 2000/03/09 16:32:55 jlemon Exp $

machine         = i386
#cpu    =         I386_CPU
#cpu    =         I486_CPU
cpu     =         I586_CPU
cpu     =         I686_CPU
ident   =         GENERIC
maxusers        = 32

#makeoptions    = DEBUG=3D-g        =         #Build kernel with gdb(1) = debug symbols

options         = MATH_EMULATE    =         #Support for x87 = emulation
options         = INET            =         #InterNETworking
options         = INET6           =         #IPv6 communications = protocols
options         = FFS             =         #Berkeley Fast = Filesystem
options         = FFS_ROOT        =         #FFS usable as root device = [keep this!]
options         = MFS             =         #Memory Filesystem
options         = MD_ROOT         =         #MD is a potential root = device
options         = NFS             =         #Network Filesystem
options         = NFS_ROOT        =         #NFS usable as root device, = NFS required
options         = MSDOSFS         =         #MSDOS Filesystem
options         = CD9660          =         #ISO 9660 Filesystem
options         = CD9660_ROOT     =         #CD-ROM usable as root, = CD9660 required
options         = PROCFS          =         #Process filesystem
options         = COMPAT_43       =         #Compatible with BSD 4.3 = [KEEP THIS!]
options         = SCSI_DELAY=3D15000        #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 = extentions
options         = _KPOSIX_PRIORITY_SCHEDULING
options         = ICMP_BANDLIM           = ; #Rate limit bad replies

# To make an SMP kernel, the next two are = needed
options         = SMP             =         # Symmetric MultiProcessor = Kernel
options         = APIC_IO         =         # Symmetric (APIC) = I/O
# Optionally these may need tweaked, (defaults = shown):
options         = NCPU=3D2          =         # number of CPUs
options         = NBUS=3D4          =         # number of busses
options         = NAPIC=3D1         =         # number of IO APICs
options         = NINTR=3D24        =         # number of INTs

device  =         isa
#device         = eisa
device  =         pci

# Floppy drives
device  =         fdc0    at = isa? port IO_FD1 irq 6 drq 2
device  =         fd0     = at fdc0 drive 0
#device         = fd1     at fdc0 drive 1

# 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
#options        = ATA_ENABLE_ATAPI_DMA    #Enable DMA on ATAPI = devices

# SCSI Controllers
#device         = ahb             = # EISA AHA1742 family
#device         = ahc             = # AHA2940 and onboard AIC7xxx devices
#device         = amd             = # AMD 53C974 (Teckram DC-390(T))
#device         = dpt             = # DPT Smartcache - See LINT for options!
#device         = isp             = # Qlogic family
#device         = ncr             = # NCR/Symbios Logic
device  =         sym     =         # NCR/Symbios Logic (newer = chipsets)

#device         = adv0    at isa?
#device         = adw
#device         = bt0     at isa?
#device         = aha0    at isa?
#device         = aic0    at isa?

# SCSI peripherals
device  =         scbus   =         # SCSI bus (required)
device  =         = da      =         # Direct Access = (disks)
device  =         = sa      =         # Sequential Access (tape = etc)
device  =         = cd      =         # CD
device  =         pass    =         # Passthrough device (direct = SCSI access)

# RAID controllers
#device         = ida             = # Compaq Smart RAID
#device         = amr             = # AMI MegaRAID
#device         = mlx             = # Mylex DAC960 family

# atkbdc0 controls both the keyboard and the PS/2 = mouse
device  =         atkbdc0 at isa? port = IO_KBD
device  =         atkbd0  at atkbdc? irq = 1
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?

# Enable this and PCVT_FREEBSD for pcvt vt220 = compatible console driver
#device         = vt0     at isa?
#options        = XSERVER         =         # support for X server on a = vt console
#options        = FAT_CURSOR      =         # start with block = cursor
# If you have a ThinkPAD, uncomment this along with = the rest of the PCVT lines
#options        = PCVT_SCANSET=3D2          # IBM = keyboards are non-std

# Floating point support - do not disable.
device  =         npx0    at = nexus? port IO_NPX irq 13

# Power management support (see LINT for more = options)
#device         = apm0    at nexus? disable flags 0x20 # Advanced Power = Management

# PCCARD (PCMCIA) support
#device         = card
#device         = pcic0   at isa? irq 10 port 0x3e0 iomem 0xd0000
#device         = pcic1   at isa? irq 11 port 0x3e2 iomem 0xd4000 = disable

# Serial (COM) ports
device  =         sio0    at = isa? port IO_COM1 flags 0x10 irq 4
device  =         sio1    at = isa? port IO_COM2 irq 3
#device         = sio2    at isa? disable port IO_COM3 irq 5
#device         = sio3    at isa? disable port IO_COM4 irq 9

# Parallel port
device  =         ppc0    at = isa? irq 7
device  =         ppbus   =         # Parallel port bus = (required)
device  =         lpt     =         # Printer
device  =         plip    =         # TCP/IP over = parallel
device  =         ppi     =         # Parallel port interface = device
#device         = vpo             = # Requires scbus and da


# PCI Ethernet NICs.
#device         = de      =         # DEC/Intel DC21x4x = (``Tulip'')
device  =         fxp     =         # Intel EtherExpress = PRO/100B (82557, 82558)
#device         = tx      =         # SMC 9432TX (83c170 = ``EPIC'')
#device         = vx      =         # 3Com 3c590, 3c595 = (``Vortex'')
#device         = wx      =         # Intel Gigabit Ethernet = Card (``Wiseman'')

# PCI Ethernet NICs that use the common MII bus contro= ller code.
#device         = miibus          # MII bus = support
#device         = dc      =         # DEC/Intel 21143 and = various workalikes
#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         = vr      =         # VIA Rhine, Rhine II
#device         = wb      =         # Winbond W89C840F
#device         = xl      =         # 3Com 3c90x (``Boomerang'', = ``Cyclone'')

# ISA Ethernet NICs.
#device         = ed0     at isa? port 0x280 irq 10 iomem = 0xd8000
#device         = ex
#device         = ep
# WaveLAN/IEEE 802.11 wireless NICs. Note: the = WaveLAN/IEEE really
# exists only as a PCMCIA device, so there is no ISA = attatement needed
# and resources will always be dynamically assigned = by the pccard code.
#device         = wi
# Aironet 4500/4800 802.11 wireless NICs. Note: the = declaration below will
# work for PCMCIA and PCI cards, as well as ISA = cards set to ISA PnP
# mode (the factory default). If you set the = switches on your ISA
# card for a manually chosen I/O address and IRQ, = you must specify
# those paremeters here.
#device         = an
# The probe order of these is presently determined = by i386/isa/isa_compat.c.
#device         = ie0     at isa? port 0x300 irq 10 iomem = 0xd0000
#device         = fe0     at isa? port 0x300
#device         = le0     at isa? port 0x300 irq 5 iomem = 0xd0000
#device         = lnc0    at isa? port 0x280 irq 10 drq 0
#device         = cs0     at isa? port 0x300
#device         = sn0     at isa? port 0x300 irq 10
# requires PCCARD (PCMCIA) support to be = activated
#device         = xe0     at isa?

# Pseudo devices - the number indicates how many = units to allocated.
pseudo-device   loop    =         # Network loopback
pseudo-device   ether   =         # Ethernet support
pseudo-device   = sl      1       = # Kernel SLIP
pseudo-device   = ppp     1       # = Kernel PPP
pseudo-device   = tun             = # Packet tunnel.
pseudo-device   = pty             = # Pseudo-ttys (telnet etc)
pseudo-device   = md      =         # Memory = "disks"
pseudo-device   = gif     4       # = 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

# USB support
#device         = uhci            # = UHCI PCI->USB interface
#device         = ohci            # = OHCI PCI->USB interface
#device         = usb             = # USB Bus (required)
#device         = ugen            # = Generic
#device         = uhid            # = "Human Interface Devices"
#device         = ukbd            # = Keyboard
#device         = ulpt            # = Printer
#device         = umass           # = Disks/Mass storage - Requires scbus and da
#device         = ums             = # Mouse
# USB Ethernet, requires mii
#device         = aue             = # ADMtek USB ethernet
#device         = cue             = # CATC USB ethernet
#device         = kue             = # Kawasaki LSI USB ethernet

#device snd0
device pcm

---------------------------------------------------------------=
---------------------------------------------------------------=
# Kernel from Kevin
# GENERIC -- Generic kernel configuration file for = FreeBSD/i386
#
# For more information on this file, please read the = handbook section on
# Kernel Configuration Files:
#
#    http://www.freebsd.org/handbook/kernelconfig-config.ht= ml
#
# 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 = 2000/03/09 16:32:55 jlemon Exp $

machine         = i386
#cpu    =         I386_CPU
#cpu    =         I486_CPU
cpu     =         I586_CPU
cpu     =         I686_CPU
ident   =         CANCRI
maxusers        = 32

#makeoptions    = DEBUG=3D-g        =         #Build kernel with gdb(1) = debug symbols

options         = MATH_EMULATE    =         #Support for x87 = emulation
options         = INET            =         #InterNETworking
options         = INET6           =         #IPv6 communications = protocols
options         = FFS             =         #Berkeley Fast = Filesystem
options         = FFS_ROOT        =         #FFS usable as root device = [keep this!]
options         = MFS             =         #Memory Filesystem
options         = MD_ROOT         =         #MD is a potential root = device
options         = NFS             =         #Network Filesystem
options         = NFS_ROOT        =         #NFS usable as root device, = NFS required
options         = MSDOSFS         =         #MSDOS Filesystem
options         = CD9660          =         #ISO 9660 Filesystem
options         = CD9660_ROOT     =         #CD-ROM usable as root, = CD9660 required
options         = PROCFS          =         #Process filesystem
options         = COMPAT_43       =         #Compatible with BSD 4.3 = [KEEP THIS!]
options         = SCSI_DELAY=3D15000        #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 = extentions
options         = _KPOSIX_PRIORITY_SCHEDULING
options         = ICMP_BANDLIM    =         #Rate limit bad = replies

# To make an SMP kernel, the next two are = needed
options         = SMP             =         # Symmetric MultiProcessor = Kernel
options         = APIC_IO         =         # Symmetric (APIC) = I/O
# Optionally these may need tweaked, (defaults = shown):
options         = NCPU=3D2          =         # number of CPUs
options         = NBUS=3D4          =         # number of busses
options         = NAPIC=3D1         =         # number of IO APICs
options         = NINTR=3D24        =         # number of INTs

device  =         isa
#device         = eisa
device  =         pci

# Floppy drives
device  =         fdc0    at = isa? port IO_FD1 irq 6 drq 2
device  =         fd0     = at fdc0 drive 0
#device         = fd1     at fdc0 drive 1

# 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
#options        = ATA_ENABLE_ATAPI_DMA    #Enable DMA on ATAPI = devices

# SCSI Controllers
#device         = ahb             = # EISA AHA1742 family
#device         = ahc             = # AHA2940 and onboard AIC7xxx devices
#device         = amd             = # AMD 53C974 (Teckram DC-390(T))
#device         = dpt             = # DPT Smartcache - See LINT for options!
#device         = isp             = # Qlogic family
#device         = ncr             = # NCR/Symbios Logic
device  =         sym     =         # NCR/Symbios Logic (newer = chipsets)

#device         = adv0    at isa?
#device         = adw
#device         = bt0     at isa?
#device         = aha0    at isa?
#device         = aic0    at isa?

# SCSI peripherals
device  =         scbus   =         # SCSI bus (required)
device  =         = da      =         # Direct Access = (disks)
device  =         = sa      =         # Sequential Access (tape = etc)
device  =         = cd      =         # CD
device  =         pass    =         # Passthrough device (direct = SCSI access)

# RAID controllers
#device         = ida             = # Compaq Smart RAID
#device         = amr             = # AMI MegaRAID
#device         = mlx             = # Mylex DAC960 family

# atkbdc0 controls both the keyboard and the PS/2 = mouse
device  =         atkbdc0 at isa? port = IO_KBD
device  =         atkbd0  at atkbdc? irq = 1
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?

# Enable this and PCVT_FREEBSD for pcvt vt220 = compatible console driver
#device         = vt0     at isa?
#options        = XSERVER         =         # support for X server on a = vt console
#options        = FAT_CURSOR      =         # start with block = cursor
# If you have a ThinkPAD, uncomment this along with = the rest of the PCVT lines
#options        = PCVT_SCANSET=3D2          # IBM = keyboards are non-std

# Floating point support - do not disable.
device  =         npx0    at = nexus? port IO_NPX irq 13

# Power management support (see LINT for more = options)
#device         = apm0    at nexus? disable flags 0x20 # Advanced Power = Management

# PCCARD (PCMCIA) support
#device         = card
#device         = pcic0   at isa? irq 10 port 0x3e0 iomem 0xd0000
#device         = pcic1   at isa? irq 11 port 0x3e2 iomem 0xd4000 = disable

# Serial (COM) ports
device  =         sio0    at = isa? port IO_COM1 flags 0x10 irq 4
device  =         sio1    at = isa? port IO_COM2 irq 3
#device         = sio2    at isa? disable port IO_COM3 irq 5
#device         = sio3    at isa? disable port IO_COM4 irq 9

# Parallel port
device  =         ppc0    at = isa? irq 7
device  =         ppbus   =         # Parallel port bus = (required)
device  =         lpt     =         # Printer
device  =         plip    =         # TCP/IP over = parallel
device  =         ppi     =         # Parallel port interface = device
#device         = vpo             = # Requires scbus and da


# PCI Ethernet NICs.
#device         = de      =         # DEC/Intel DC21x4x = (``Tulip'')
device  =         fxp     =         # Intel EtherExpress = PRO/100B (82557, 82558)
#device         = tx      =         # SMC 9432TX (83c170 = ``EPIC'')
#device         = vx      =         # 3Com 3c590, 3c595 = (``Vortex'')
#device         = wx      =         # Intel Gigabit Ethernet = Card (``Wiseman'')

# PCI Ethernet NICs that use the common MII bus = controller code.
#device         = miibus          # MII bus = support
#device         = dc      =         # DEC/Intel 21143 and = various workalikes
#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         = vr      =         # VIA Rhine, Rhine II
#device         = wb      =         # Winbond W89C840F
#device         = xl      =         # 3Com 3c90x (``Boomerang'', = ``Cyclone'')

# ISA Ethernet NICs.
#device         = ed0     at isa? port 0x280 irq 10 iomem = 0xd8000
#device         = ex
#device         = ep
# WaveLAN/IEEE 802.11 wireless NICs. Note: the = WaveLAN/IEEE really
# exists only as a PCMCIA device, so there is no ISA = attatement needed
# and resources will always be dynamically assigned = by the pccard code.
#device         = wi
# Aironet 4500/4800 802.11 wireless NICs. Note: the = declaration below will
# work for PCMCIA and PCI cards, as well as ISA = cards set to ISA PnP
# mode (the factory default). If you set the = switches on your ISA
# card for a manually chosen I/O address and IRQ, = you must specify
# those paremeters here.
#device         = an
# The probe order of these is presently determined = by i386/isa/isa_compat.c.
#device         = ie0     at isa? port 0x300 irq 10 iomem = 0xd0000
#device         = fe0     at isa? port 0x300
#device         = le0     at isa? port 0x300 irq 5 iomem = 0xd0000
#device         = lnc0    at isa? port 0x280 irq 10 drq 0
#device         = cs0     at isa? port 0x300
#device         = sn0     at isa? port 0x300 irq 10
# requires PCCARD (PCMCIA) support to be = activated
#device         = xe0     at isa?

# Pseudo devices - the number indicates how many = units to allocated.
pseudo-device   loop    =         # Network loopback
pseudo-device   ether   =         # Ethernet support
pseudo-device   = sl      1       = # Kernel SLIP
pseudo-device   = ppp     1       # = Kernel PPP
pseudo-device   = tun             = # Packet tunnel.
pseudo-device   = pty             = # Pseudo-ttys (telnet etc)
pseudo-device   = md      =         # Memory = "disks"
pseudo-device   = gif     4       # = 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

# USB support
#device         = uhci            # = UHCI PCI->USB interface
#device         = ohci            # = OHCI PCI->USB interface
#device         = usb             = # USB Bus (required)
#device         = ugen            # = Generic
#device         = uhid            # = "Human Interface Devices"
#device         = ukbd            # = Keyboard
#device         = ulpt            # = Printer
#device         = umass           # = Disks/Mass storage - Requires scbus and da
#device         = ums             = # Mouse
# USB Ethernet, requires mii
#device         = aue             = # ADMtek USB ethernet
#device         = cue             = # CATC USB ethernet
#device         = kue             = # Kawasaki LSI USB ethernet

#device snd0
#device pcm0 at isa? port ? tty irq 10 drq 1 flags = 0x0
device pcm

---------------------------------------------------------------= ------



Thanks for the help.


Jeff Deakle

Direct =3D (281)721-4680
Fax =3D (281)721-4600

------_=_NextPart_001_01C012CC.347FC630-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 15: 4:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hq.ezo.net (hq.ezo.net [206.150.211.190]) by hub.freebsd.org (Postfix) with ESMTP id BE54637B43C; Wed, 30 Aug 2000 15:04:44 -0700 (PDT) Received: from zinnia (zinnia.ezo.net [206.150.211.129]) by hq.ezo.net (8.9.3/8.9.3) with SMTP id SAA05016; Wed, 30 Aug 2000 18:08:05 -0400 (EDT) (envelope-from jflowers@ezo.net) Message-ID: <002101c012cd$0b4a53b0$81d396ce@ezo.net> From: "Jim Flowers" To: "Atsushi Onoe" Cc: , References: <39A9E49D.A79BF6FD@softweyr.com> <200008280703.e7S732S01248@duplo.sm.sony.co.jp> Subject: Re: fbsd box acting as a wavelan BS (Yes it can) Date: Wed, 30 Aug 2000 17:55:42 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-Mimeole: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The 6.04 firmware does, indeed, allow establishing a network with an ISA card in a FreeBSD box, however, when doing the PCCard upgrade with a Windows machine it requires the drivers to be upgraded to 4.01 first and if you want to talk to it with the IEEE/Wave Manager Client update it, as well. Everything seems to be backward compatible (ad-hoc, Infrastructure, WaveManageer/Client, Manager. The good news is that it works farily well and will setup a network netname, with the procedure you indicated. You can also move away from the default frequency in either direction and the remote stations will follow it so the beacons must work. Works with multiple clients (simultaneously) but the cache (-C) only reports levels on a single remote. Haven't tried multiple throughput tests yet. Statistics (-o) don't show any values but these are on 4.1-STABLE #0 and maybe that is the same problem reported by Theo Pagtzis. The bad news is that the unit is not really running as an infrastructure network and is reported by the WaveManager Client as a "public ad-hoc workgroup" with the specified netname. I don't mind so much that the site monitor doesn't work (the link tests do work) but it's really a downer that, being identified as an ad-hoc network type, the max transmit rate is locked at 2 Mbps which limits TCP throughput to about 1.2 - 1.5 Mbps in both directions with turbo bronze cards. Sure would be great if someone could find a way around that but I don't hold out much hope for a simple driver modification after reading Bill Paul's driver comments. Looks like Lucent is intent on restricting the third-party functionality to avoid eating their children. Still, it can make a nice distribution point sitting out at the end of a single T-1 and we've got lots of 2 Mb cards. After looking through the Lucent driver for Linux, I see that they don't even have that much. ----- Original Message ----- From: "Atsushi Onoe" To: Cc: ; ; ; ; Sent: Monday, August 28, 2000 3:03 AM Subject: Re: fbsd box acting as a wavelan BS > > > Last I checked the wi driver will not do IBSS and says so in the > > > documentation. I also tried it and couldn't get anywhere. Would be nice. > > > > Uh, er, if you mean to create a service set, Lucent apparently hasn't seen > > fit to release that sort of information about the cards yet. I can probably > > get access to it, but it would be under NDA and therefore not useful. Your > > best bet is to bug your friendly neighborhood Lucent rep into releaseing > > the full documentation (and sample source code) to Bill Paul. > > Lucent have shipped newer firmware this March which DOES support creating > IBSS. The verision 6.04 of the firmware creates IBSS by setting wicontrol > -c 1 with -p 1 (BSS mode), and joins to IBSS if no access points found. > It seems that the name of created IBSS follows "network name" specified by > -n option, not "SSID" by -q option. > > Regards, > > Atsushi Onoe > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 15:27: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from netplex.com.au (adsl-63-207-30-186.dsl.snfc21.pacbell.net [63.207.30.186]) by hub.freebsd.org (Postfix) with ESMTP id DA29737B43F for ; Wed, 30 Aug 2000 15:27:05 -0700 (PDT) Received: from netplex.com.au (peter@localhost [127.0.0.1]) by netplex.com.au (8.11.0/8.9.3) with ESMTP id e7UMQoG95533; Wed, 30 Aug 2000 15:26:50 -0700 (PDT) (envelope-from peter@netplex.com.au) Message-Id: <200008302226.e7UMQoG95533@netplex.com.au> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: Christopher Stein , freebsd-hackers@FreeBSD.ORG Subject: Re: freebsd port of netboot?.. In-Reply-To: <200008301836.MAA17828@harmony.village.org> Date: Wed, 30 Aug 2000 15:26:50 -0700 From: Peter Wemm Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message Christopher Stein writes: > : .. does anyone know if this exists? It would > : speed up the panic-edit-compile-boot-copy-boot kernel hacking > : cycle by transforming it to panic-edit-compile-netboot. > > I usually mount everything readonly when I try a new module just > before loading it. It saves a tone of time. All I gotta fsck on the > way back up is /var since it won't mount ro after syslog starts, which > makes sense if you think about it. > > mount -ur / > mount -ur /usr > moutn -ur /junk > > is what I have in a script. After it succeeds, I do a mount -uwa > which updates all the mounts. > > You can also netboot via a ROM on your ethernet card or via floppy, > but I've not done that. The above works well enough for me. Also, if you have a PXE-aware network card or bios, netbooting with a small ramdisk is very convenient for crash-and-burn testing. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 15:33:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id AA1B337B422 for ; Wed, 30 Aug 2000 15:33:52 -0700 (PDT) Received: from mail.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.11.0.Beta3/8.11.0.Beta3) with ESMTP id e7UMXdK05523 (using TLSv1/SSLv3 with cipher EDH-RSA-DES-CBC3-SHA (168 bits) verified OK); Thu, 31 Aug 2000 00:33:41 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by mail.cicely.de (8.11.0.Beta1/8.11.0.Beta1) with ESMTP id e7UMY1q05811; Thu, 31 Aug 2000 00:34:01 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.11.0/8.9.2) id e7UMXhZ12338; Thu, 31 Aug 2000 00:33:43 +0200 (CEST) (envelope-from ticso) Date: Thu, 31 Aug 2000 00:33:42 +0200 From: Bernd Walter To: Bill Fumerola Cc: Jaye Mathisen , Simon , "hackers@FreeBSD.ORG" Subject: Re: Anyway to ipfw filter based on MAC address? Message-ID: <20000831003342.A12297@cicely8.cicely.de> References: <200008290108.TAA26723@mail.fpsn.net> <20000828233106.T33771@jade.chc-chimes.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000828233106.T33771@jade.chc-chimes.com>; from billf@chimesnet.com on Mon, Aug 28, 2000 at 11:31:06PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 28, 2000 at 11:31:06PM -0400, Bill Fumerola wrote: > On Mon, Aug 28, 2000 at 07:02:03PM -0700, Jaye Mathisen wrote: > > > > Just exactly what I said in the Subject. I want to filter on the ethernet > > MAC address. > > I guess the "ip" in "ipfw" just wasn't obvious enough that it is an IP firewall > tool. You're one layer too low. We already have filter rules to check if a packet would get bridged. And none IP protocols like IPX get bridged depending on the default rule of ipfw. I don't think that ipfw stand for ip only anymore. But I'm not shure if we still have the MAC address at this layer. Unfortunately we can't use a fwd action for bridged packets ;( Anyone with a good idea how to get missings parameters in the bridge code for calling the firewall check code. Is it OK to just get emtpy structures? If I understood it right the bridge checks only at incoming time and normaly fwd should be used for outgoing packets. Will this be any big problem? -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 16:29:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f294.law9.hotmail.com [64.4.8.169]) by hub.freebsd.org (Postfix) with ESMTP id 5E5B737B43F for ; Wed, 30 Aug 2000 16:29:17 -0700 (PDT) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Wed, 30 Aug 2000 16:29:17 -0700 Received: from 12.20.190.1 by lw9fd.law9.hotmail.msn.com with HTTP; Wed, 30 Aug 2000 23:29:17 GMT X-Originating-IP: [12.20.190.1] From: "gerald stoller" To: hackers@FreeBSD.ORG Subject: GNU's gdb Date: Wed, 30 Aug 2000 19:29:17 EDT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Message-ID: X-OriginalArrivalTime: 30 Aug 2000 23:29:17.0218 (UTC) FILETIME=[1D6C4820:01C012DA] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I used gdb several times (successfully), but each time that I try it on the Korn-shell and give the shell a pipelined command (with a few built-in commands, e.g. print 'qwertyui' | cat - ) and I place a break at c_print (even without this break, if I recall correctly), I get a core-dump from gdb and it never stops at the breakpoint. Where can I find documentation on gdb so I can check on restraints in its use? I hope the GNU people take a look at this and fix it if there is something wrong. Please respond to me directly because it's hard to go through the bulk-mail that I get from this group. _________________________________________________________________________ Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com. Share information about yourself, create your own public profile at http://profiles.msn.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 17:20: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 3399F37B422 for ; Wed, 30 Aug 2000 17:19:58 -0700 (PDT) Received: (qmail 14297 invoked from network); 31 Aug 2000 00:27:18 -0000 Received: from jhs.muc.de (HELO park.jhs.private) (193.149.49.84) by slarti.muc.de with SMTP; 31 Aug 2000 00:27:18 -0000 Received: (from jhs@localhost) by park.jhs.private (8.9.3/8.9.3) id RAA01920; Wed, 30 Aug 2000 17:11:17 GMT (envelope-from jhs) Date: Wed, 30 Aug 2000 17:11:17 GMT Message-Id: <200008301711.RAA01920@park.jhs.private> To: freebsd-hackers@freebsd.org Subject: /usr/include/openssl/rsaref.h not installed, Why ? From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 4.1 (built by `all` from 4.0, not via `world`, as that host is tooo slow!) I had to do cd /usr/src; cp crypto/openssl/rsaref/rsaref.h /usr/include/openssl/ (The rest of src/ makes OK though.) Have people been living on hand enhanced /usr/includes ? or is it just me ? Is it my mistake ? Or something to fix ? Here's my log: ---------- cd /usr/src/secure/lib/librsausa make cc -O2 -m486 -DTERMIOS -DANSI_SOURCE -DNO_IDEA -I/usr/src/secure/lib/librsausa/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/librsausa -DL_ENDIAN -DDEVRANDOM=\"/dev/urandom\" -I/usr/obj/usr/src/secure/lib/librsausa -I//usr/include -c /usr/src/secure/lib/librsausa/../../../crypto/openssl/crypto/../rsaref/rsar_err.c -o rsar_err.o /usr/src/secure/lib/librsausa/../../../crypto/openssl/crypto/../rsaref/rsar_err.c:63: openssl/rsaref.h: No such file or directory *** Error code 1 /usr/src/secure/lib/librsausa/../../../crypto/openssl/crypto/../rsaref/rsar_err .c: line 62&3 #include #include find /usr/src/secure/lib/librsausa/../../../crypto/openssl/crypto /usr/obj/usr/src/secure/lib/librsausa /usr/include -name err.h /usr/src/secure/lib/librsausa/../../../crypto/openssl/crypto/err/err.h /usr/include/openssl/err.h /usr/include/err.h cd /usr/include/openssl ; ls err.h rsaref.h err.h is there, but no rsaref.h cd /usr/src ; find . -name rsaref.h crypto/openssl/rsaref/rsaref.h cd /usr/src; cp crypto/openssl/rsaref/rsaref.h /usr/include/openssl/ make ; make install cd /usr/include find . -name rsaref.h ./openssl/rsaref.h cd /usr/include/openssl/ ls -ltr -rw-r--r-- 1 root wheel 6924 Aug 30 12:44 rsaref.h -r--r--r-- 1 root wheel 37059 Aug 30 14:21 asn1.h -r--r--r-- 1 root wheel 16166 Aug 30 14:21 bn.h .... so my rsaref.h is still old & hand installed ... ? This would seem to have nothing to do with USA/non USA as ${USA_RESIDENT} does not prepend librsausa in secure/lib/Makefile - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant Free BSD Unix, 3600 packages & source To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 17:34: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 8140637B422; Wed, 30 Aug 2000 17:33:58 -0700 (PDT) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA68029; Wed, 30 Aug 2000 17:33:58 -0700 (PDT) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Wed, 30 Aug 2000 17:33:58 -0700 (PDT) From: Kris Kennaway To: Julian Stacey Cc: freebsd-hackers@freebsd.org Subject: Re: /usr/include/openssl/rsaref.h not installed, Why ? In-Reply-To: <200008301711.RAA01920@park.jhs.private> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 30 Aug 2000, Julian Stacey wrote: > On 4.1 (built by `all` from 4.0, not via `world`, as that host is tooo slow!) > I had to do > cd /usr/src; cp crypto/openssl/rsaref/rsaref.h /usr/include/openssl/ > (The rest of src/ makes OK though.) > Have people been living on hand enhanced /usr/includes ? or is it just me ? > Is it my mistake ? Or something to fix ? Don't know..never heard this complaint before so I'm forced to conclude it's probably an artifact of the way you're building your sources. Kris -- In God we Trust -- all others must submit an X.509 certificate. -- Charles Forsythe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 18:11:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.osd.bsdi.com (mass.osd.bsdi.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 745A337B42C for ; Wed, 30 Aug 2000 18:11:38 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA06154; Wed, 30 Aug 2000 18:25:16 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008310125.SAA06154@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: YAMAMOTO Shigeru Cc: imp@village.org, hackers@freebsd.org Subject: Re: PCI BIOS In-reply-to: Your message of "Tue, 29 Aug 2000 19:01:37 +0900." <20000829190137J.shigeru@iij.ad.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Aug 2000 18:25:16 -0700 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to note that I've been looking at this code a bit, and at least the PCI bus interface/implementation is really nice. It could do with a little cleaning up, but this would give us the ability to assign PCI resources on the fly (can you say "hot-plug PCI"?). Do you plan to continue with this work? Could you write a few words describing what the goal of this particular development tree is? Thanks! > From: Warner Losh > Subject: PCI BIOS > Date: Mon, 28 Aug 2000 15:26:32 -0600 > > Anybody have a good interface to pcibios for kernel devices to use? I > > think I have a need for it with the TI-1225 based pci cardbus bridge > > card that I have. I need to be able to assign interrupt numbers (or > > at least get them) for the slot. NetBSD has this functionality and we > > need it to be a true plug and play OS. > > Now I'm wrinting a code to use PCI BIOS/MS$PIR. > URL:http://www.bremen.or.jp/shigeru/FreeBSD/CardBus/dev.20000628.tar.gz > > sys/i386/pci/pci_root.c in my code is using pci interrrupt routing > table in a PCI BIOS when assigning an IRQ. > > ------- > YAMAMOTO Shigeru > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Aug 30 22:38: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from femail3.sdc1.sfba.home.com (femail3.sdc1.sfba.home.com [24.0.95.83]) by hub.freebsd.org (Postfix) with ESMTP id 246C537B422 for ; Wed, 30 Aug 2000 22:38:06 -0700 (PDT) Received: from home.com ([24.3.185.85]) by femail3.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000831053733.YZWP25970.femail3.sdc1.sfba.home.com@home.com> for ; Wed, 30 Aug 2000 22:37:33 -0700 Message-ID: <39ADF00C.EEE4C3A@home.com> Date: Thu, 31 Aug 2000 01:41:32 -0400 From: "Gary T. Corcoran" X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Booting Linux with FreeBSD booter (hack needed) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a notebook PC with Windows, Linux, and FreeBSD on it. I installed the FreeBSD booter into the Master Boot Record (MBR). Using that, I can boot Windows or FreeBSD. But Linux doesn't show up as a boot choice, because I installed it into a "dos extended" partition (slice), to keep linux from (ridiculously) eating up half (two) of the tiny number of disk slices (it normally wants a whole partition (slice) just for swap). This way linux only takes up one of the four slices. Now since the MBR booter "knows" that you don't boot DOS/Windows from an "extended" partition (type 5), it doesn't offer it as a boot choice. Now I could probably hack the booter (boot0 ?) to accept type 5 as a valid choice. But before I risk losing my whole (work) disk by messing with the MBR :), does anyone know if I do this, and install LILO (the linux loader) into my "extended" partition, will the MBR booter find the LILO booter to really be able to boot Linux? Or will the "extended dos" partition still confuse the MBR booter - that is, not find LILO where it expects it? BTW, I tried using LILO as the MBR booter, but all it does is print "L" and "00 00 " over and over. I'm guessing because it's a large (> 8GB) disk that it's getting confused, as I've used it before (on < 8GB) to boot win/linux/freebsd... Thanks, Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 0:45:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id EBE9037B422; Thu, 31 Aug 2000 00:45:23 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 31 Aug 2000 08:45:20 +0100 Message-ID: <39AE0D0D.804963FD@cs.ucl.ac.uk> Date: Thu, 31 Aug 2000 08:45:17 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: ls -l | more inverts colour Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, for some strange reason an ls -l | more inverts the colour on an xterm. If I vi a file then colour comes back to normal (I gather vi resets xterm) Is that known? Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 0:57:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id D6A5337B423; Thu, 31 Aug 2000 00:57:02 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 31 Aug 2000 08:56:49 +0100 Message-ID: <39AE0FBE.6CD145C4@cs.ucl.ac.uk> Date: Thu, 31 Aug 2000 08:56:46 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Jim Flowers Cc: Atsushi Onoe , freebsd-hackers , freebsd-net , freebsd-mobile@FreeBSD.ORG Subject: Re: fbsd box acting as a wavelan BS (Yes it can) References: <39A9E49D.A79BF6FD@softweyr.com> <200008280703.e7S732S01248@duplo.sm.sony.co.jp> <002101c012cd$0b4a53b0$81d396ce@ezo.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim, Jim Flowers wrote: > The 6.04 firmware does, indeed, allow establishing a network with an ISA > card in a FreeBSD box, however, when doing the PCCard upgrade with a Windows > machine it requires the drivers to be upgraded to 4.01 first and if you want > to talk to it with the IEEE/Wave Manager Client update it, as well. > Everything seems to be backward compatible (ad-hoc, Infrastructure, > WaveManageer/Client, Manager. > > The good news is that it works farily well and will setup a network netname, > with the procedure you indicated. You can also move away from the default > frequency in either direction and the remote stations will follow it so the > beacons must work. Works with multiple clients (simultaneously) but the > cache (-C) only reports levels on a single remote. Haven't tried multiple > throughput tests yet. Statistics (-o) don't show any values but these are > on 4.1-STABLE #0 and maybe that is the same problem reported by Theo > Pagtzis. > thanks for checking it out. I tried to print a single statistic from the wavelan card after experiencing the 0ed wi_counters from within the kernel (device_print)... for some reason once I did that the machine...rebooted...(not beneignly :) Could someone point me on info about kernel debugging? Do I get the impression that there is something wrong with the interrupt assigned to the card. Jim mentioned that it is probably best to have the interrupt assigned to the card isolated (at least that was my impression from what Jim mentioned as grandfathering) Also in some of the new fbsd boxes (4.1 stable + KAME snap) we have here the wavelan card although detected when inserted (which is a pccardd function) it keeps giving a "no such card in database". The card is in the database of pccard.conf, I use interrupt 9 which is not in use by another device. Can anyone understand the dumpcis info from the pccardc request? I dunno if that helps in understanding the problem as I cannot understand what it means..(at least a good part of it..) Any hints? Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 1: 7: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from c3-dbn-108.dial-up.net (c3-dbn-108.dial-up.net [196.33.200.108]) by hub.freebsd.org (Postfix) with ESMTP id 2D66E37B422 for ; Thu, 31 Aug 2000 01:07:03 -0700 (PDT) Received: (from rnordier@localhost) by c3-dbn-108.dial-up.net (8.8.7/8.6.12) id KAA19347; Thu, 31 Aug 2000 10:04:59 +0200 (SAST) From: Robert Nordier Message-Id: <200008310804.KAA19347@c3-dbn-108.dial-up.net> Subject: Re: Booting Linux with FreeBSD booter (hack needed) In-Reply-To: <39ADF00C.EEE4C3A@home.com> from "Gary T. Corcoran" at "Aug 31, 2000 01:41:32 am" To: garycor@home.com (Gary T. Corcoran) Date: Thu, 31 Aug 2000 10:04:56 +0200 (SAST) Cc: freebsd-hackers@FreeBSD.ORG X-No-Archive: Yes X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gary T. Corcoran wrote: > Now since the MBR booter "knows" that you don't boot DOS/Windows > from an "extended" partition (type 5), it doesn't offer it as > a boot choice. Now I could probably hack the booter (boot0 ?) > to accept type 5 as a valid choice. But before I risk losing > my whole (work) disk by messing with the MBR :), does anyone know if > I do this, and install LILO (the linux loader) into my "extended" > partition, will the MBR booter find the LILO booter to really > be able to boot Linux? Or will the "extended dos" partition > still confuse the MBR booter - that is, not find LILO where it > expects it? Unfortunately any hack based around allowing selection of type 5 partitions won't work. There's really no simple fix to get boot0 booting stuff from within extended partitions. -- Robert Nordier rnordier@nordier.com // Le monde est plein de fous, et qui n'en veut pas voir rnordier@FreeBSD.org // Doit se tenir tout seul, et casser son miroir. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 2:46:49 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id 27CB537B424; Thu, 31 Aug 2000 02:46:45 -0700 (PDT) Received: from free.fr (paris11-nas4-47-92.dial.proxad.net [212.27.47.92]) by postfix2.free.fr (Postfix) with ESMTP id AABB7740E5; Thu, 31 Aug 2000 11:46:42 +0200 (MEST) Message-ID: <39AE45E4.E7C7B60D@free.fr> Date: Thu, 31 Aug 2000 11:47:48 +0000 From: Nicolas Souchu Organization: Home Sweet Home X-Mailer: Mozilla 4.72 [en] (X11; I; FreeBSD 4.1-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Cc: freebsd-chat@freebsd.org, BOISSEAU Jean-Philippe Subject: Mach4 BSD working group? Lites? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi hackers and others, Has anybody heard about some *BSD work on the Mach4 microkernel recently? I mean, something that would look like Hurd (from GNU) but with a complete BSD approach. How hard would it be to upgrade Lites1.1 server to support FBSD 4.0 binaries? Thanks in advance. Nicholas (I'm not subscribed to the lists) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 3:39:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0651C37B422 for ; Thu, 31 Aug 2000 03:39:09 -0700 (PDT) Received: from uucp.nl.uu.net (uucp.nl.uu.net [193.79.237.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id A86056E2920 for ; Thu, 31 Aug 2000 03:38:24 -0700 (PDT) Received: from jaknl by athos.nl.uu.net with UUCP id ; Thu, 31 Aug 2000 12:35:12 +0200 Received: from jak.nl ([192.168.0.30]) by jak.nl (8.8.8/8.8.8) with ESMTP id MAA10767 for ; Thu, 31 Aug 2000 12:31:49 +0200 (CEST) (envelope-from arjan@jak.nl) Message-ID: <39AE3203.F8599DF4@jak.nl> Date: Thu, 31 Aug 2000 12:22:59 +0200 From: Arjan Knepper Organization: JAK++ Software Development B.V. X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hackers FreeBSD Subject: Cyclades Cyclom Ze (64 serialportboard) Content-Type: multipart/mixed; boundary="------------F5CEE32457EE4508BE043BC0" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------F5CEE32457EE4508BE043BC0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, Anyone experience with this board? Any comments? Recomandations? Thanks. --------------F5CEE32457EE4508BE043BC0 Content-Type: text/x-vcard; charset=us-ascii; name="arjan.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Arjan Knepper Content-Disposition: attachment; filename="arjan.vcf" begin:vcard n:Knepper;Arjan tel;fax:+31-(0)10-243-7314 tel;work:+31-(0)10-243-7362 x-mozilla-html:FALSE url:http://www.jak.nl org:JAK++ Software Development B.V. adr:;;Stoveer 247;Rotterdam;;3032 GB;Netherlands version:2.1 email;internet:arjan@jak.nl x-mozilla-cpt:;-7904 fn:Arjan Knepper end:vcard --------------F5CEE32457EE4508BE043BC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 3:51:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tokyogw.iij.ad.jp (tokyogw.iij.ad.jp [202.232.15.22]) by hub.freebsd.org (Postfix) with ESMTP id C2A7E37B449; Thu, 31 Aug 2000 03:51:41 -0700 (PDT) Received: by tokyogw.iij.ad.jp; id TAA07769; Thu, 31 Aug 2000 19:51:40 +0900 (JST) Received: from mercury.iij.ad.jp(192.168.4.89) by tokyogw.iij.ad.jp via smap (V4.2) id xma007557; Thu, 31 Aug 00 19:51:03 +0900 Received: from localhost (shigeru@localhost [127.0.0.1]) by mercury.iij.ad.jp (8.9.3/8.9.3) with ESMTP id TAA06735; Thu, 31 Aug 2000 19:51:02 +0900 (JST) To: msmith@freebsd.org Cc: imp@village.org, hackers@freebsd.org Subject: Re: PCI BIOS In-Reply-To: Your message of "Wed, 30 Aug 2000 18:25:16 -0700" <200008310125.SAA06154@mass.osd.bsdi.com> References: <200008310125.SAA06154@mass.osd.bsdi.com> X-Mailer: Mew version 1.93b38 on XEmacs 21.2 (Shinjuku) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000831195102V.shigeru@iij.ad.jp> Date: Thu, 31 Aug 2000 19:51:02 +0900 From: YAMAMOTO Shigeru X-Dispatcher: imput version 991025(IM133) Lines: 26 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Mike Smith Subject: Re: PCI BIOS Date: Wed, 30 Aug 2000 18:25:16 -0700 > Just to note that I've been looking at this code a bit, and at least the > PCI bus interface/implementation is really nice. It could do with a > little cleaning up, but this would give us the ability to assign PCI > resources on the fly (can you say "hot-plug PCI"?). > > Do you plan to continue with this work? Could you write a few words > describing what the goal of this particular development tree is? Yes. I'm wrinting a code now. My first goal is to support dynamic assignment of PCI interrupt. It is required to support CardBus. Final goal is to support CompactPCI. A CompactPCI device is dinamically inserted/removed like a PC Card. I think we need to assign PCI resource(interrupt, bus number, etc...) on the fly to support a CompactPCI and other Hot-plug PCI devices. #Maybe, Docking Station is a Hot-plug device. ------- YAMAMOTO Shigeru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 4:19:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from genius.systems.pavilion.net (genius.systems.pavilion.net [212.74.1.100]) by hub.freebsd.org (Postfix) with ESMTP id E9ECE37B440; Thu, 31 Aug 2000 04:19:17 -0700 (PDT) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 0088A9B3F; Thu, 31 Aug 2000 12:19:16 +0100 (BST) Date: Thu, 31 Aug 2000 12:19:16 +0100 From: Josef Karthauser To: Theo PAGTZIS Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: ls -l | more inverts colour Message-ID: <20000831121916.D50038@pavilion.net> Mail-Followup-To: Josef Karthauser , Theo PAGTZIS , freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG References: <39AE0D0D.804963FD@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39AE0D0D.804963FD@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Thu, Aug 31, 2000 at 08:45:17AM +0100 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 31, 2000 at 08:45:17AM +0100, Theo PAGTZIS wrote: > Hi All, > > for some strange reason an ls -l | more inverts the colour on an > xterm. If I vi a file then colour comes back to normal (I gather vi > resets xterm) > > Is that known? What versions are you running? Please send the results of running: # uname -a # ls -l /bin/ls # env Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 4:58:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3303E37B424; Thu, 31 Aug 2000 04:58:12 -0700 (PDT) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id NAA75155; Thu, 31 Aug 2000 13:58:46 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <200008311158.NAA75155@freebsd.dk> Subject: Tagged queuing for ATA drives, patches up for testing To: current@freebsd.org, hackers@freebsd.org Date: Thu, 31 Aug 2000 13:58:46 +0200 (CEST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I've put the latest patches for tagged queueing on ATA disks up for ftp on: ftp://freebsd.dk/pub/ATA/ATA-tagged-queueing-diff-0831.gz This is a snapshot from one of my working tree's and other minor fixes are also included, but thats another story... From the README: Experimental support for tagged queing on ATA disks that supports it. (IBM drives and some WD drives that are rebadged IBM's). This code only works on drives sitting alone on an ATA channel, and should work on all controllers. Support for master/slave combinations, and ATA/ATAPI ditto is being worked on, but this requires a controller with support for the "auto nop" functionality. Which of the many different controllers supports this is unknown at this time, but HPT controllers has the needed functionality, and should be a safe bet. It seems that the DJNA series of IBM disks has some problems with tagged queueing, but at least the DPTA and DTLA series are known to work. The older DTTA series has not been tested yet. The test runs so far indicates a 3% performance gain on a make -j16 world, with a 30% reduction in system time, not too bad for a first shot. Enjoy and let me know of your findings! -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 7:42:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id C06FE37B43C for ; Thu, 31 Aug 2000 07:42:27 -0700 (PDT) Received: (qmail 20620 invoked from network); 31 Aug 2000 14:49:47 -0000 Received: from jhs.muc.de (HELO park.jhs.private) (193.149.49.84) by slarti.muc.de with SMTP; 31 Aug 2000 14:49:47 -0000 Received: from park.jhs.private (localhost [127.0.0.1]) by park.jhs.private (8.9.3/8.9.3) with ESMTP id IAA04401; Thu, 31 Aug 2000 08:52:29 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200008310852.IAA04401@park.jhs.private> To: Kris Kennaway Cc: freebsd-hackers@FreeBSD.org Subject: Re: /usr/include/openssl/rsaref.h not installed, Why ? From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Wed, 30 Aug 2000 17:33:58 PDT." Date: Thu, 31 Aug 2000 10:52:29 +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Reference: > From: Kris Kennaway > Date: Wed, 30 Aug 2000 17:33:58 -0700 (PDT) > Message-id: Hi, Kris Kennaway wrote: > On Wed, 30 Aug 2000, Julian Stacey wrote: > > > On 4.1 (built by `all` from 4.0, not via `world`, as that host is tooo slow > !) > > I had to do > > cd /usr/src; cp crypto/openssl/rsaref/rsaref.h /usr/include/openssl/ > > (The rest of src/ makes OK though.) > > Have people been living on hand enhanced /usr/includes ? or is it just me ? > > Is it my mistake ? Or something to fix ? > > Don't know..never heard this complaint before so I'm forced to conclude > it's probably an artifact of the way you're building your sources. My sources come from cvs export -r RELENG_4_1_0_RELEASE src from a cvs tree delivered by ctm_rmail. Could someone please help provide clues to locate the problem, EG part/all of: uname -r cd ~/tmp ; mkdir rm ; cd rm ; cvs export -r RELENG_4_1_0_RELEASE src find -H ~/tmp/rm /usr/include /usr/src /usr/cvs -name rsaref.h\* |xargs ls -l cd /usr/src ; make world find -H /usr/include /usr/src /usr/cvs -name rsaref.h\* | xargs ls -l uname -r Thanks. I have here for comparison: -rw-r--r-- 1 root wheel 6924 Aug 30 12:44 /usr/include/openssl/rsaref.h -rw-r--r-- 1 jhs wheel 6924 Feb 26 2000 /usr/src/crypto/openssl/rsaref/rsaref.h -rw-r--r-- 1 jhs wheel 8232 Jul 27 21:22 /usr/cvs/src/crypto/openssl/rsaref/rsaref.h,v Julian - Julian Stacey http://bim.bsn.com/~jhs/ Munich Unix Consultant. Free BSD Unix with 3600 packages & sources. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 8:36: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [216.139.128.6]) by hub.freebsd.org (Postfix) with ESMTP id 4F06237B422 for ; Thu, 31 Aug 2000 08:35:59 -0700 (PDT) Received: from bsd1.nyct.net (root@bsd1.nyct.net [216.139.128.3]) by mail.nyct.net (8.9.3/8.8.7) with ESMTP id LAA22285; Thu, 31 Aug 2000 11:35:50 -0400 (EDT) (envelope-from mbac@nyct.net) Received: from localhost (mbac@localhost) by bsd1.nyct.net (8.9.3/8.9.3) with ESMTP id LAA94861; Thu, 31 Aug 2000 11:36:00 -0400 (EDT) (envelope-from mbac@nyct.net) X-Authentication-Warning: bsd1.nyct.net: mbac owned process doing -bs Date: Thu, 31 Aug 2000 11:36:00 -0400 (EDT) From: Michael Bacarella To: "Gary T. Corcoran" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Booting Linux with FreeBSD booter (hack needed) In-Reply-To: <39ADF00C.EEE4C3A@home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have a notebook PC with Windows, Linux, and FreeBSD on it. > I installed the FreeBSD booter into the Master Boot Record (MBR). > Using that, I can boot Windows or FreeBSD. But Linux doesn't > show up as a boot choice, because I installed it into a "dos > extended" partition (slice), to keep linux from (ridiculously) > eating up half (two) of the tiny number of disk slices (it normally > wants a whole partition (slice) just for swap). This way linux > only takes up one of the four slices. Use a swap file instead, or even do without swap if you have the RAM. Also, I'm pretty sure you can enable a compile time option so that Linux can use BSD slices, which may or may not make a difference in your case (pre-boot/boot stage). -MB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 9: 3:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kane.rhyason.com (kane.rhyason.com [204.209.142.193]) by hub.freebsd.org (Postfix) with SMTP id 1811637B423 for ; Thu, 31 Aug 2000 09:03:51 -0700 (PDT) Received: (qmail 97130 invoked by uid 1000); 30 Aug 2000 15:03:40 -0000 Date: Wed, 30 Aug 2000 09:03:40 -0600 From: Jeff Rhyason To: Robert Watson Cc: freebsd-hackers@freebsd.org Subject: Re: Collecting waiting statistics (simulation question) Message-ID: <20000830090340.A96861@rhyason.com> References: <20000829102607.B47494@rhyason.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from rwatson@freebsd.org on Tue, Aug 29, 2000 at 01:38:23PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Feel free to post URLs for both the implementation and resulting paper, as > I think they'd be of interest to the community as a whole, allowing us to > better understand the impact of real-world behavior on the implementation, > as well as providing a foundation for future profiling and modifications. > Sounds like cool work, I'd definitely be interested in reading about it. OK - I'm glad there's some interest! It needs some more analysis which I would be happy to do after some comments! ;) -Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 10:56: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id 682EB37B423 for ; Thu, 31 Aug 2000 10:55:57 -0700 (PDT) Received: from ccuzner by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13UYZA-000IhO-00 for hackers@freebsd.org; Thu, 31 Aug 2000 13:55:56 -0400 Date: Thu, 31 Aug 2000 13:55:56 -0400 From: Chris Cuzner To: hackers@freebsd.org Subject: [ccuzner@targetnet.com: msgget errors] Message-ID: <20000831135556.A64919@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Forwarded message from Chris Cuzner ----- Date: Mon, 28 Aug 2000 18:18:07 -0400 From: Chris Cuzner To: netsaint-users@lists.sourceforge.net Subject: msgget errors Pardon me, i'm a little new when it comes to C, can someone please explain why/how this would be occuring after a 4.1-SNAP buildworld to 4.1-Stable (FreeBSD). [967495548] NetSaint 0.0.5 starting... (PID=78299) [967495548] Error: Could not initialize IPC message queue! I added a few lines of code to ipc.c, which gave me this output when built with --enable-DEBUG0: #ifdef DEBUG0 if( queue_id == -1 ) { printf("msgget failed, errno is %d\n", errno); } #endif init_message_queue() start msgget failed, errno is 28 init_message_queue() end Netsaint was up and functioning properlly before the buildworld was performed. Started getting the stated "Error: Could not initialize IPC message queue!" message, so i decided to rebuild netsaint. The build works fine, but for some reason i get an errno 28 when i try to run it. help ;P TIA -- Chris Cuzner ccuzner(at)targetnet(dot)com Systems Administrator 416/306.0466x916 TargetNet Inc. http://www.targetnet.com ----- End forwarded message ----- -- Chris Cuzner ccuzner(at)targetnet(dot)com Systems Administrator 416/306.0466x916 TargetNet Inc. http://www.targetnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 11:15: 9 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 769DB37B422 for ; Thu, 31 Aug 2000 11:15:06 -0700 (PDT) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id LAA34853; Thu, 31 Aug 2000 11:10:38 -0700 (PDT) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id LAA98824; Thu, 31 Aug 2000 11:09:47 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200008311809.LAA98824@whistle.com> Subject: Re: freebsd port of netboot?.. In-Reply-To: <200008302226.e7UMQoG95533@netplex.com.au> from Peter Wemm at "Aug 30, 2000 03:26:50 pm" To: Peter Wemm Date: Thu, 31 Aug 2000 11:09:47 -0700 (PDT) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Wemm writes: | Warner Losh wrote: | > In message Christopher Stein | writes: | > : .. does anyone know if this exists? It would | > : speed up the panic-edit-compile-boot-copy-boot kernel hacking | > : cycle by transforming it to panic-edit-compile-netboot. | > | > I usually mount everything readonly when I try a new module just | > before loading it. It saves a tone of time. All I gotta fsck on the | > way back up is /var since it won't mount ro after syslog starts, which | > makes sense if you think about it. | > | > mount -ur / | > mount -ur /usr | > moutn -ur /junk | > | > is what I have in a script. After it succeeds, I do a mount -uwa | > which updates all the mounts. | > | > You can also netboot via a ROM on your ethernet card or via floppy, | > but I've not done that. The above works well enough for me. | | Also, if you have a PXE-aware network card or bios, netbooting | with a small ramdisk is very convenient for crash-and-burn testing. Since vmware doesn't do PXE, etherboot works nicely with it. This way you can neboot your vmware session and with Julians psuedo serial port thing you have a nice environment. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 12:55: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from clever.visp-europe.psi.com (clever.visp-europe.psi.com [212.222.105.4]) by hub.freebsd.org (Postfix) with ESMTP id D86A337B423 for ; Thu, 31 Aug 2000 12:54:50 -0700 (PDT) Received: from ip168.berlin68.pub-ip.de.psi.net ([154.15.68.168] helo=goting.jn.berlin.snafu.de) by clever.visp-europe.psi.com with esmtp (Exim 3.14 #1) id 13UaQC-0003vb-00 for freebsd-hackers@freebsd.org; Thu, 31 Aug 2000 21:54:49 +0200 Received: by goting.jn.berlin.snafu.de (Postfix, from userid 100) id 7A8402263; Thu, 31 Aug 2000 21:54:46 +0200 (CEST) To: freebsd-hackers@freebsd.org Subject: New script to run a number of jobs (also in the background) From: Juergen Nickelsen Date: 31 Aug 2000 21:54:46 +0200 Message-ID: Lines: 202 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Canyonlands" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, a while ago I wrote yet another script to run a number of programs on a certain occasion which is similar to periodic(8). My main goal was to run jobs (fetching mail and news) in parallel when I go online with my dial-up account. These should be finished, though, before the time is set with ntpdate. (ntpdate should have a minimum round-trip time.) The script reads a directory (the only argument is the path name) of arbitrary programs and executes them in ASCII order. It executes programs with names *.bg in the background and waits for their termination either before it terminates or when it encounters a program with a name *.wait (which is then also executed). Usage: run-jobs [-v [-v]] [-p argv0] jobs-directory-path I'd like to see someone like this in the standard OS. If anyone thinks it is worth including, please do; I would then take suggestions for improvement and write a manpage. The program is deliberately not plug-compatible with periodic(8) -- I think it is more flexible to just take a pathname as an argument. The pathname may, of course, have a descriptive name like /etc/periodic/daily. Well, also if no one thinks this should be in FreeBSD, I'll gladly take suggestions, of course. I just might not feel compelled to write a manpage. :-) Greetings, Juergen. #!/usr/bin/perl -w # -*- perl -*- # # Run a number of job scripts (actually arbitrary programs) in the # specified directory. Source a file env.pl, if it exists. Run # programs with names matching *.bg in the background. On program # names matching *.wait, wait until all background processes are # finished before continuing with the *.wait program. # #- # Copyright (c) 2000 Juergen Nickelsen # All rights reserved. # # Redistribution and use in source form, with or without modification, are # permitted provided that the following conditions are met: # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the distribution. # # THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE # ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE # FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # # $Id: run-jobs.pl,v 1.3 2000/06/27 07:04:33 ni Exp $ # use strict ; my $verbose = 0 ; # verbosity flag may be 0, 1, 2, ... my $progname = "run-jobs" ; # name of program (argv[0] doesn't work) my $ls = "/bin/ls" ; # need them sorted my $envfile = "env.pl" ; # read and evaluated at startup my $verbarg = "" ; # argument for jobs if $verbose my $nprocs = 0 ; # Number of background jobs running $| = 1 ; # due to fork() my %procs = () ; # processes indexed by pid my $jobsdir ; # directory containing job scripts # return local time in iso format sub isodate { my ($sec, $min, $hour, $mday, $mon, $year, undef, undef, undef) = localtime(time); return sprintf("%04d-%02d-%02d %02d:%02d:%02d", $year + 1900, $mon + 1, $mday, $hour, $min, $sec) ; } # print something if $verbose sub vprint { print "$progname: @_\n" if $verbose ; } # print something if $verbose >= 2 sub vvprint { print "$progname: @_\n" if $verbose >= 2 ; } # run job in background sub run_bg { my ($cmd) = @_ ; my $pid = 0 ; if ($pid = fork()) { vprint "started process $pid with $cmd @ARGV" ; $procs{$pid} = $cmd ; $nprocs++ ; } else { if (!defined($pid)) { warn "fork failed ($!)" ; } else { exec "./$cmd @ARGV" ; } } } # wait for all background jobs sub wait_for_children { my $pid ; my $status ; if ($nprocs > 0) { vprint sprintf("waiting for $nprocs child process%s", $nprocs != 1 ? "es" : "") ; while (($pid = wait) != -1) { $nprocs-- ; $status = $? >> 8 ; vprint sprintf "child process $pid exits with $status" . " ($procs{$pid}), $nprocs left" ; } } } MAIN: do { # check commandline for verbose flag and program name argument FLAGS: while ($ARGV[0]) { if ($ARGV[0] =~ /^-/) { if ($ARGV[0] eq "-v") { $verbose++ ; $verbarg = "-v" ; shift ; } elsif ($ARGV[0] eq "-p") { shift ; $progname = shift ; } } else { last FLAGS ; } } $jobsdir = shift ; # directory containing job scripts if (!defined($jobsdir)) { die "usage: $progname [-v] [-p progname] directory [args...]\n" ; } # change to directory with jobs chdir $jobsdir || die "$progname: can't chdir to $jobsdir ($!)\n" ; # read file with enviroment variables etc. if present if (open (ENVF, $envfile)) { my $savenl ; my $env ; vprint "eval $envfile" ; $savenl = $/ ; $/ = undef ; # Slurp whole file $env = ; $/ = $savenl ; eval $env ; warn $@ if $@ ; } # read job file names my @jobs = `$ls` ; vprint "start jobs at " . isodate() ; # run jobs LOOP: for (@jobs) { chomp ; vvprint "check $_" ; if (-x $_ && ! -d $_) { if (/~$/) { # Skip Emacs backup files next LOOP ; } elsif (/\.bg$/) { # run *.bg in background run_bg $_ ; } else { if (/\.wait$/) { # wait for children on all *.wait` vprint "waiting on $_" ; wait_for_children() ; } vprint "run $_ @ARGV" ; system "./$_ @ARGV" ; } } } wait_for_children() ; vprint "finished at " . isodate() ; } # EOF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 12:58:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smart.visp-europe.psi.com (smart.visp-europe.psi.com [212.222.105.5]) by hub.freebsd.org (Postfix) with ESMTP id 42AAA37B423 for ; Thu, 31 Aug 2000 12:58:35 -0700 (PDT) Received: from ip86.berlin63.pub-ip.de.psi.net ([154.15.63.86] helo=goting.jn.berlin.snafu.de) by smart.visp-europe.psi.com with esmtp (Exim 3.14 #1) id 13UaTp-0002lu-00; Thu, 31 Aug 2000 21:58:33 +0200 Received: by goting.jn.berlin.snafu.de (Postfix, from userid 100) id 11C022263; Thu, 31 Aug 2000 21:58:25 +0200 (CEST) To: Juergen Nickelsen Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: New script to run a number of jobs (also in the background) References: From: Juergen Nickelsen Date: 31 Aug 2000 21:58:25 +0200 In-Reply-To: Juergen Nickelsen's message of "31 Aug 2000 21:54:46 +0200" Message-ID: Lines: 8 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Canyonlands" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just wrote: > I'd like to see someone like this in the standard OS. ^^^^^^^ "some*thing*" of course. Sorry! -- Juergen Nickelsen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 13:21:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id 9531F37B422 for ; Thu, 31 Aug 2000 13:21:39 -0700 (PDT) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 3DD019B26; Thu, 31 Aug 2000 21:21:38 +0100 (BST) Date: Thu, 31 Aug 2000 21:21:38 +0100 From: Josef Karthauser To: Theo PAGTZIS Cc: freebsd-hackers@freebsd.org Subject: Re: ls -l | more inverts colour Message-ID: <20000831212138.A16056@pavilion.net> Mail-Followup-To: Josef Karthauser , Theo PAGTZIS , freebsd-hackers@freebsd.org References: <39AE0D0D.804963FD@cs.ucl.ac.uk> <20000831121916.D50038@pavilion.net> <39AE8EF6.B295963F@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39AE8EF6.B295963F@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Thu, Aug 31, 2000 at 05:59:35PM +0100 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You're not using the flags for colourized ls are you? If you do: % ls > /tmp/ls % cat /tmp/ls | more Does it still leave the screen inverted? Joe On Thu, Aug 31, 2000 at 05:59:35PM +0100, Theo PAGTZIS wrote: > > uname ... > > FreeBSD olympos.cs.ucl.ac.uk 4.1-RELEASE FreeBSD 4.1-RELEASE #1: Thu Aug 31 > 10:44:22 BST 2000 > root@olympos.cs.ucl.ac.uk:/usr/nfs/implementation/KAME/kame/freebsd4/sys/compile/v6-MIPv6-ALTq-WvLAN-DTOP41S-000824 > i386 > > -r-xr-xr-x 1 root wheel 290056 Aug 24 11:39 /bin/ls* > > > MAIL=/var/mail/root > BLOCKSIZE=K > FTP_PASSIVE_MODE=YES > TERM=xterm > USER=root > HOME=/root > SHELL=/bin/csh > HOSTTYPE=FreeBSD > VENDOR=intel > OSTYPE=FreeBSD > MACHTYPE=i386 > SHLVL=1 > PWD=/usr/src > LOGNAME=root > GROUP=wheel > HOST=olympos.cs.ucl.ac.uk > REMOTEHOST=ginger.cs.ucl.ac.uk > OS=freebsd > CS_ARCH=i386 > CS_KARCH=unknown > CS_OS=FreeBSD > CS_OS_REL=4.1-RELEASE > CS_SHORT=olympos > CS_HOST=olympos.cs.ucl.ac.uk > CS_USER=root > CS_MAILID=TMP_MAILID > CS_HOME=/root > CS_UCLASS=staff > CS_USUBCLASS=postgrad > LD_LIBRARY_PATH=/usr/lib:/usr/local/lib > tshell=/usr/local/bin/tcsh > MUSIC_CD=/dev/wcd0c > CVSROOT=:pserver:cvsanon@eucharisto.cs.ucl.ac.uk:/cs/research/mice/starship/src/local/CVS_repository > > > > Theo > -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 13:25:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id 6457737B423 for ; Thu, 31 Aug 2000 13:25:29 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e7VKPQk93013; Thu, 31 Aug 2000 13:25:26 -0700 (PDT) Date: Thu, 31 Aug 2000 13:25:26 -0700 (PDT) From: Doug White To: Arjan Knepper Cc: hackers FreeBSD Subject: Re: Cyclades Cyclom Ze (64 serialportboard) In-Reply-To: <39AE3203.F8599DF4@jak.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Aug 2000, Arjan Knepper wrote: > Anyone experience with this board? > Any comments? Recomandations? I have a ze card that we bought for use as a cheap term server, but found that the card is particular about the motherboard chipset. We had some telenet Celeron 1Us that we wanted to use but the card wouldn't init. We put it in a standard pentium box and it worked. We still have that card with a 16 port box that I've been tempted to play with. We ended up using good ol' cisco 2511s. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 16:35:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 6004F37B423 for ; Thu, 31 Aug 2000 16:35:50 -0700 (PDT) Received: from bellatlantic.net (client-151-198-117-238.nnj.dialup.bellatlantic.net [151.198.117.238]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id TAA22366; Thu, 31 Aug 2000 19:28:49 -0400 (EDT) Message-ID: <39AEEAC6.1F832303@bellatlantic.net> Date: Thu, 31 Aug 2000 19:31:18 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Robert Nordier Cc: "Gary T. Corcoran" , freebsd-hackers@FreeBSD.ORG Subject: Re: Booting Linux with FreeBSD booter (hack needed) References: <200008310804.KAA19347@c3-dbn-108.dial-up.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier wrote: > > Gary T. Corcoran wrote: > > > Now since the MBR booter "knows" that you don't boot DOS/Windows > > from an "extended" partition (type 5), it doesn't offer it as > > a boot choice. Now I could probably hack the booter (boot0 ?) > > to accept type 5 as a valid choice. But before I risk losing > > my whole (work) disk by messing with the MBR :), does anyone know if > > I do this, and install LILO (the linux loader) into my "extended" > > partition, will the MBR booter find the LILO booter to really > > be able to boot Linux? Or will the "extended dos" partition > > still confuse the MBR booter - that is, not find LILO where it > > expects it? > > Unfortunately any hack based around allowing selection of type 5 > partitions won't work. There's really no simple fix to get boot0 > booting stuff from within extended partitions. What about installing the FreeBSD MBR into the boot sector of the extended partition and calling it recursively ? That would require some changes to the MBR: it should be able to receive somehow the knowledge that it's loaded from an extended partition and the exact geometry of that partition. No, I'm not volunteering :-) -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 16:52: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id C11AD37B42C for ; Thu, 31 Aug 2000 16:51:59 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id TAA03733 for hackers@freebsd.org; Thu, 31 Aug 2000 19:52:48 -0400 (EDT) (envelope-from dufault) From: Peter Dufault Message-Id: <200008312352.TAA03733@hda.hda.com> Subject: gdb remote debugging on slow computers To: hackers@freebsd.org Date: Thu, 31 Aug 2000 19:52:43 -0400 (EDT) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I know, this is a gdb question. Since I'm not on gdb lists I'll ask here first. I want to use my fast, well understood FreeBSD system and use gdb to attach to remote processes running on a Solaris 2.7 system. I now have a wicked slow Sun system to use to verify that my binaries run properly on Solaris 2.7. It takes longer to configure gdb on that Sun than my regular system takes to configure and build gdb. I want to do nothing other than run binaries on that Sun. I have a working cross-development system on FreeBSD that builds the Solaris executables. I want to attach a gdb running on my FreeBSD system to something running on that wicked slow Sun. I've built a gdb with a target machine of "sparc-sun-solaris2.7", I've got an executable, but I haven't found a way to run something on the Sun that I can attach to in order to debug remote processes. All I've found are ways to connect to remote serial ports. Does anyone know if I can easily do this? Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 16:57:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 8D27537B423 for ; Thu, 31 Aug 2000 16:57:27 -0700 (PDT) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 4A331A8AD; Fri, 1 Sep 2000 09:57:44 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id 46F3E54B7; Fri, 1 Sep 2000 09:57:44 +1000 (EST) Date: Fri, 1 Sep 2000 09:57:44 +1000 (EST) From: andrew@ugh.net.au To: Chris Cuzner Cc: hackers@freebsd.org Subject: Re: [ccuzner@targetnet.com: msgget errors] In-Reply-To: <20000831135556.A64919@targetnet.com> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Aug 2000, Chris Cuzner wrote: > msgget failed, errno is 28 From the man page for msgget: [ENOSPC] A new message queue could not be created because the system limit for the number of message queues has been reached. What happens when you run ipcs? If there are a lot of queues that probably aren't in use you can get rid of them with ipcrm -q . Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 17:31:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id 09A0F37B423 for ; Thu, 31 Aug 2000 17:31:56 -0700 (PDT) Received: from ccuzner by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13UekH-000LcT-00; Thu, 31 Aug 2000 20:31:49 -0400 Date: Thu, 31 Aug 2000 20:31:49 -0400 From: Chris Cuzner To: andrew@ugh.net.au Cc: hackers@freebsd.org Subject: Re: [ccuzner@targetnet.com: msgget errors] Message-ID: <20000831203149.B76472@targetnet.com> References: <20000831135556.A64919@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from andrew@ugh.net.au on Fri, Sep 01, 2000 at 09:57:44AM +1000 Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [root@as-02] [08/31/2000 20:30] -[1 ttyp0]-[ ~ # ipcs Message Queues: T ID KEY MODE OWNER GROUP Shared Memory: T ID KEY MODE OWNER GROUP Semaphores: T ID KEY MODE OWNER GROUP * andrew@ugh.net.au (andrew@ugh.net.au) [000831 19:57]: > > > On Thu, 31 Aug 2000, Chris Cuzner wrote: > > > msgget failed, errno is 28 > > >From the man page for msgget: > > [ENOSPC] A new message queue could not be created because the > system limit for the number of message queues has been > reached. > > What happens when you run ipcs? If there are a lot of queues that probably > aren't in use you can get rid of them with ipcrm -q . > > Andrew > -- Chris Cuzner ccuzner(at)targetnet(dot)com FreeBSD Systems Administrator 416/306.0466x916 TargetNet Inc. http://www.targetnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 19:33:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from starbug.ugh.net.au (starbug.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 5999A37B422 for ; Thu, 31 Aug 2000 19:33:19 -0700 (PDT) Received: by starbug.ugh.net.au (Postfix, from userid 1000) id 00C8CA8AA; Fri, 1 Sep 2000 12:33:36 +1000 (EST) Received: from localhost (localhost [127.0.0.1]) by starbug.ugh.net.au (Postfix) with ESMTP id EEDE054B5; Fri, 1 Sep 2000 12:33:36 +1000 (EST) Date: Fri, 1 Sep 2000 12:33:36 +1000 (EST) From: andrew@ugh.net.au To: Chris Cuzner Cc: hackers@freebsd.org Subject: Re: [ccuzner@targetnet.com: msgget errors] In-Reply-To: <20000831203149.B76472@targetnet.com> Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are message queues actually in your kernel? options SYSVMSG Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 20:42:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from femail4.sdc1.sfba.home.com (femail4.sdc1.sfba.home.com [24.0.95.84]) by hub.freebsd.org (Postfix) with ESMTP id 0300C37B43C for ; Thu, 31 Aug 2000 20:42:23 -0700 (PDT) Received: from home.com ([24.3.185.85]) by femail4.sdc1.sfba.home.com (InterMail vM.4.01.03.00 201-229-121) with ESMTP id <20000901034139.XDZF12879.femail4.sdc1.sfba.home.com@home.com> for ; Thu, 31 Aug 2000 20:41:39 -0700 Message-ID: <39AF266A.8391325C@home.com> Date: Thu, 31 Aug 2000 23:45:46 -0400 From: "Gary T. Corcoran" X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.ORG Subject: Re: Booting Linux with FreeBSD booter (hack needed) References: <200008310804.KAA19347@c3-dbn-108.dial-up.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ I'm sending this to the list just in case anyone searches the email archives for an answer to a similar question. ] I wrote: > > Now since the MBR booter "knows" that you don't boot DOS/Windows > > from an "extended" partition (type 5), it doesn't offer it as > > a boot choice. Now I could probably hack the booter (boot0 ?) > > to accept type 5 as a valid choice. But before I risk losing > > my whole (work) disk by messing with the MBR :), does anyone know if > > I do this, and install LILO (the linux loader) into my "extended" > > partition, will the MBR booter find the LILO booter to really > > be able to boot Linux? Or will the "extended dos" partition > > still confuse the MBR booter - that is, not find LILO where it > > expects it? Robert Nordier wrote: > Unfortunately any hack based around allowing selection of type 5 > partitions won't work. There's really no simple fix to get boot0 > booting stuff from within extended partitions. I found the latest version of the Linux loader (LILO), version 21.5.1, and installed it. Using the relatively-new "lba32" option for addressing large disks, I'm able to boot Windows/Linux/FreeBSD off my 12GB disk. Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Aug 31 20:42:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.tor3.targetnet.com (smtp.tor3.targetnet.com [207.176.132.71]) by hub.freebsd.org (Postfix) with ESMTP id 4D34A37B422 for ; Thu, 31 Aug 2000 20:42:43 -0700 (PDT) Received: from ccuzner by smtp.tor3.targetnet.com with local (Exim 3.16 #1) id 13Uhit-000MdV-00; Thu, 31 Aug 2000 23:42:35 -0400 Date: Thu, 31 Aug 2000 23:42:35 -0400 From: Chris Cuzner To: andrew@ugh.net.au Cc: hackers@freebsd.org Subject: Re: [ccuzner@targetnet.com: msgget errors] Message-ID: <20000831234235.A83127@targetnet.com> References: <20000831203149.B76472@targetnet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from andrew@ugh.net.au on Fri, Sep 01, 2000 at 12:33:36PM +1000 Organization: Targetnet.com Inc. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [root@as-02] [08/31/2000 23:41] -[6 ttyp1]-[ / # strings kernel | grep SYSVMSG ___options SYSVMSG #SYSV-style message queues * andrew@ugh.net.au (andrew@ugh.net.au) [000831 22:33]: > Are message queues actually in your kernel? > > options SYSVMSG > > Andrew > -- Chris Cuzner ccuzner(at)targetnet(dot)com FreeBSD Systems Administrator 416/306.0466x916 TargetNet Inc. http://www.targetnet.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 0: 5:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from uucp.nl.uu.net (uucp.nl.uu.net [193.79.237.146]) by hub.freebsd.org (Postfix) with ESMTP id 0912437B422 for ; Fri, 1 Sep 2000 00:05:25 -0700 (PDT) Received: from jaknl by athos.nl.uu.net with UUCP id ; Fri, 1 Sep 2000 09:05:05 +0200 Received: from jak.nl ([192.168.0.30]) by jak.nl (8.8.8/8.8.8) with ESMTP id JAA13091; Fri, 1 Sep 2000 09:00:50 +0200 (CEST) (envelope-from arjan@jak.nl) Message-ID: <39AF5212.271E5032@jak.nl> Date: Fri, 01 Sep 2000 08:52:03 +0200 From: Arjan Knepper Organization: JAK++ Software Development B.V. X-Mailer: Mozilla 4.72 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Doug White Cc: hackers FreeBSD Subject: Re: Cyclades Cyclom Ze (64 serialportboard) References: Content-Type: multipart/mixed; boundary="------------35833D0A805C1D5372E18E6F" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------35833D0A805C1D5372E18E6F Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Doug White wrote: > > On Thu, 31 Aug 2000, Arjan Knepper wrote: > > > Anyone experience with this board? > > Any comments? Recomandations? > > I have a ze card that we bought for use as a cheap term server, but found > that the card is particular about the motherboard chipset. We had some > telenet Celeron 1Us that we wanted to use but the card wouldn't init. We > put it in a standard pentium box and it worked. We still have that card > with a 16 port box that I've been tempted to play with. > > We ended up using good ol' cisco 2511s. Thanks, we had same kind of problem with an YeP card on a intel 810 chipset. Works without problems on a intel 440 chipset. I seems to me the Ze is not supported in freebsd 4.0 or 4.1 is it? Arjan --------------35833D0A805C1D5372E18E6F Content-Type: text/x-vcard; charset=us-ascii; name="arjan.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Arjan Knepper Content-Disposition: attachment; filename="arjan.vcf" begin:vcard n:Knepper;Arjan tel;fax:+31-(0)10-243-7314 tel;work:+31-(0)10-243-7362 x-mozilla-html:FALSE url:http://www.jak.nl org:JAK++ Software Development B.V. adr:;;Stoveer 247;Rotterdam;;3032 GB;Netherlands version:2.1 email;internet:arjan@jak.nl x-mozilla-cpt:;-7904 fn:Arjan Knepper end:vcard --------------35833D0A805C1D5372E18E6F-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 0:49:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id BEEFF37B440 for ; Fri, 1 Sep 2000 00:49:28 -0700 (PDT) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Fri, 1 Sep 2000 08:48:58 +0100 Message-ID: <39AF5F68.6744A863@cs.ucl.ac.uk> Date: Fri, 01 Sep 2000 08:48:56 +0100 From: Theo PAGTZIS Reply-To: t.pagtzis@cs.ucl.ac.uk Organization: UCL X-Mailer: Mozilla 4.75 [en] (X11; U; SunOS 5.8 sun4u) X-Accept-Language: el, en MIME-Version: 1.0 To: Josef Karthauser Cc: freebsd-hackers@freebsd.org Subject: Re: ls -l | more inverts colour References: <39AE0D0D.804963FD@cs.ucl.ac.uk> <20000831121916.D50038@pavilion.net> <39AE8EF6.B295963F@cs.ucl.ac.uk> <20000831212138.A16056@pavilion.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser wrote: > You're not using the flags for colourized ls are you? > > If you do: > > % ls > /tmp/ls > % cat /tmp/ls | more > > Does it still leave the screen inverted? > > Joe > Joe, As in the first place, on the first screen it does not get the screen inverted but on the second 'more' it does. By the way...I see also some weird behaviour of vi when I load a file for editing. This is on the xterm this time (not the console). The screen is left a bit garbled if I played before with the scroll bar previously. If I try a ^d or ^u so that I force a xterm refresh things are back to normal but not otherwise. Is that known? Does anyone reckon this is a flake from the upgrade 3.4 to 4.1? (The upgrade has been done by the book 101%) Theo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 1:20:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from genius.systems.pavilion.net (genesis.tao.org.uk [194.242.131.254]) by hub.freebsd.org (Postfix) with ESMTP id 2D54C37B422 for ; Fri, 1 Sep 2000 01:20:07 -0700 (PDT) Received: by genius.systems.pavilion.net (Postfix, from userid 100) id 7352D9B3F; Fri, 1 Sep 2000 09:20:08 +0100 (BST) Date: Fri, 1 Sep 2000 09:20:08 +0100 From: Josef Karthauser To: Theo PAGTZIS Cc: freebsd-hackers@freebsd.org Subject: Re: ls -l | more inverts colour Message-ID: <20000901092008.D403@pavilion.net> Mail-Followup-To: Josef Karthauser , Theo PAGTZIS , freebsd-hackers@freebsd.org References: <39AE0D0D.804963FD@cs.ucl.ac.uk> <20000831121916.D50038@pavilion.net> <39AE8EF6.B295963F@cs.ucl.ac.uk> <20000831212138.A16056@pavilion.net> <39AF5F68.6744A863@cs.ucl.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <39AF5F68.6744A863@cs.ucl.ac.uk>; from T.Pagtzis@cs.ucl.ac.uk on Fri, Sep 01, 2000 at 08:48:56AM +0100 X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 01, 2000 at 08:48:56AM +0100, Theo PAGTZIS wrote: > Josef Karthauser wrote: > > > You're not using the flags for colourized ls are you? > > > > If you do: > > > > % ls > /tmp/ls > > % cat /tmp/ls | more > > > > Does it still leave the screen inverted? > > > > Joe > > > > Joe, > > As in the first place, on the first screen it does not get the screen inverted but on the second 'more' it does. It sounds like 'more' is the culprit, not 'ls'. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 4:59:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.atrada.de (hermes.atrada.de [212.118.32.33]) by hub.freebsd.org (Postfix) with SMTP id 65ACC37B43F for ; Fri, 1 Sep 2000 04:59:12 -0700 (PDT) Received: from erlangen01.atrada.de by hermes.atrada.de via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 1 Sep 2000 11:59:12 UT Received: (private information removed) Message-ID: <58A002A02C5ED311812E0050044517F00D25DA@erlangen01.atrada.de> From: Alexander Maret To: "'freebsd-hackers@freebsd.org'" Subject: Redirect stdout/stderr to syslog [OFF-TOPIC] Date: Fri, 1 Sep 2000 13:58:56 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I wonder if it is possible to redirect stdout/stderr to syslog. Background: I'm writing a program which starts (fork=>execvp) and observes another program. I would like to redirect all output of the "execvped" program to syslog. I know this is not really FBSD related but I hope you can help me anyway. Please don't tell me that I should redirect the output to a file and not to syslog. I know how to redirect the output to a file (that's my prog doing at present state). Bye, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 5: 3:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 3B33637B424 for ; Fri, 1 Sep 2000 05:03:17 -0700 (PDT) Received: (qmail 49172 invoked by uid 1001); 1 Sep 2000 11:59:48 -0000 Date: Fri, 1 Sep 2000 14:59:48 +0300 From: Peter Pentchev To: Alexander Maret Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: Redirect stdout/stderr to syslog [OFF-TOPIC] Message-ID: <20000901145948.I46859@ringwraith.office1.bg> References: <58A002A02C5ED311812E0050044517F00D25DA@erlangen01.atrada.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <58A002A02C5ED311812E0050044517F00D25DA@erlangen01.atrada.de>; from maret@atrada.net on Fri, Sep 01, 2000 at 01:58:56PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG man 1 logger pipe your stdout/stderr to logger(1), and you're all set. You may even specify a facility/level to log with. G'luck, Peter -- What would this sentence be like if pi were 3? On Fri, Sep 01, 2000 at 01:58:56PM +0200, Alexander Maret wrote: > Hi, > > I wonder if it is possible to redirect stdout/stderr to syslog. > > Background: > I'm writing a program which starts (fork=>execvp) and observes > another program. I would like to redirect all output of the "execvped" > program to syslog. > > I know this is not really FBSD related but I hope you can help > me anyway. Please don't tell me that I should redirect the output > to a file and not to syslog. I know how to redirect the output to > a file (that's my prog doing at present state). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 5:11:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id C35F737B424 for ; Fri, 1 Sep 2000 05:11:23 -0700 (PDT) Received: (qmail 49208 invoked by uid 1001); 1 Sep 2000 12:08:02 -0000 Date: Fri, 1 Sep 2000 15:08:02 +0300 From: Peter Pentchev To: freebsd-hackers@freebsd.org Subject: lex/yacc on a string, not a file? Message-ID: <20000901150802.J46859@ringwraith.office1.bg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can lex/yacc (flex, bison, byacc, whatever) be used on an arbitrary string, not an input stream? Like lines read from a config file, or received through a network socket, or.. lots of uses; is there a way? G'luck, Peter -- If the meanings of 'true' and 'false' were switched, then this sentence wouldn't be false. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 5:13:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hermes.atrada.de (hermes.atrada.de [212.118.32.33]) by hub.freebsd.org (Postfix) with SMTP id 5E28637B422 for ; Fri, 1 Sep 2000 05:13:26 -0700 (PDT) Received: from erlangen01.atrada.de by hermes.atrada.de via smtpd (for hub.FreeBSD.org [216.136.204.18]) with SMTP; 1 Sep 2000 12:13:26 UT Received: (private information removed) Message-ID: <58A002A02C5ED311812E0050044517F00D25DB@erlangen01.atrada.de> From: Alexander Maret To: 'Peter Pentchev' Cc: "'freebsd-hackers@freebsd.org'" Subject: AW: Redirect stdout/stderr to syslog [OFF-TOPIC] Date: Fri, 1 Sep 2000 14:13:19 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Ursprungliche Nachricht----- > Von: Peter Pentchev [mailto:roam@orbitel.bg] > Gesendet: Freitag, 1. September 2000 14:00 > > man 1 logger > > pipe your stdout/stderr to logger(1), and you're all set. > You may even > specify a facility/level to log with. > Thanks for your quick answer but I would prefer to do it entirely in C without calling external progs. I could think of a solution forking another child process which does the syslog logging and redirecting stdout/stderr of the execvped program via IPC to this child. But is there any easier solution? Bye, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 5:15:41 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id A730837B42C for ; Fri, 1 Sep 2000 05:15:37 -0700 (PDT) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.10.1/8.10.1) with ESMTP id e81CFO204214; Fri, 1 Sep 2000 08:15:25 -0400 (EDT) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id IAA11771; Fri, 1 Sep 2000 08:15:23 -0400 (EDT) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id IAA99159; Fri, 1 Sep 2000 08:15:22 -0400 (EDT) Date: Fri, 1 Sep 2000 08:15:22 -0400 (EDT) From: Thomas David Rivers Message-Id: <200009011215.IAA99159@lakes.dignus.com> To: maret@atrada.net, roam@orbitel.bg Subject: Re: AW: Redirect stdout/stderr to syslog [OFF-TOPIC] Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <58A002A02C5ED311812E0050044517F00D25DB@erlangen01.atrada.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > -----Ursprungliche Nachricht----- > > Von: Peter Pentchev [mailto:roam@orbitel.bg] > > Gesendet: Freitag, 1. September 2000 14:00 > > > > man 1 logger > > > > pipe your stdout/stderr to logger(1), and you're all set. > > You may even > > specify a facility/level to log with. > > > > Thanks for your quick answer but I would prefer to > do it entirely in C without calling external progs. > I could think of a solution forking another child process > which does the syslog logging and redirecting stdout/stderr > of the execvped program via IPC to this child. > > But is there any easier solution? You can use popen() to start the external process (logger in this case) with the `IPC' already set up. Then, perhaps an freopen() stdin/stdout... to the pipes would be all you need. popen() is one-way though... - Dave R. - -- rivers@dignus.com Work: (919) 676-0847 Get your mainframe (370) `C' compiler at http://www.dignus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 5:28:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 544CF37B424 for ; Fri, 1 Sep 2000 05:28:06 -0700 (PDT) Received: (qmail 49376 invoked by uid 1001); 1 Sep 2000 12:24:43 -0000 Date: Fri, 1 Sep 2000 15:24:43 +0300 From: Peter Pentchev To: Alexander Maret Cc: "'freebsd-hackers@freebsd.org'" Subject: Re: Redirect stdout/stderr to syslog [OFF-TOPIC] Message-ID: <20000901152443.K46859@ringwraith.office1.bg> References: <58A002A02C5ED311812E0050044517F00D25DB@erlangen01.atrada.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <58A002A02C5ED311812E0050044517F00D25DB@erlangen01.atrada.de>; from maret@atrada.net on Fri, Sep 01, 2000 at 02:13:19PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 01, 2000 at 02:13:19PM +0200, Alexander Maret wrote: > > -----Ursprungliche Nachricht----- > > Von: Peter Pentchev [mailto:roam@orbitel.bg] > > Gesendet: Freitag, 1. September 2000 14:00 > > > > man 1 logger > > > > pipe your stdout/stderr to logger(1), and you're all set. > > You may even > > specify a facility/level to log with. > > > > Thanks for your quick answer but I would prefer to > do it entirely in C without calling external progs. > I could think of a solution forking another child process > which does the syslog logging and redirecting stdout/stderr > of the execvped program via IPC to this child. > > But is there any easier solution? No, I don't think you can do anything cheaper than a fork and a pipe(2). popen(), as suggested in another message, is pretty much the same. I don't think stdio has a hook to capture all the data a process is sending to a stream, and pass it to some routine - that would be perfect, but unfortunately, I am not aware of such a thing. I might be wrong though. G'luck, Peter -- This sentence contradicts itself - or rather - well, no, actually it doesn't! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 8:44:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from silby.com (cb34181-a.mdsn1.wi.home.com [24.14.173.39]) by hub.freebsd.org (Postfix) with ESMTP id 7114637B423 for ; Fri, 1 Sep 2000 08:44:30 -0700 (PDT) Received: (qmail 43018 invoked by uid 1000); 1 Sep 2000 15:44:29 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 1 Sep 2000 15:44:29 -0000 Date: Fri, 1 Sep 2000 10:44:29 -0500 (CDT) From: Mike Silbersack To: Josef Karthauser Cc: Theo PAGTZIS , freebsd-hackers@freebsd.org Subject: Re: ls -l | more inverts colour In-Reply-To: <20000901092008.D403@pavilion.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 1 Sep 2000, Josef Karthauser wrote: > It sounds like 'more' is the culprit, not 'ls'. > > Joe FWIW, I've seen the inverted color problem a few times since less replaced more, but haven't taken the effort to figure out when exactly it's happening. Ironically, it seems more likely to happen when working via console than via SecureCRT. Mike "Silby" Silbersack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 9: 8:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 07C8537B423; Fri, 1 Sep 2000 09:08:50 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e81G8mN29951; Fri, 1 Sep 2000 18:08:48 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Soren Schmidt Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Tagged queuing for ATA drives, patches up for testing In-Reply-To: Your message of "Thu, 31 Aug 2000 13:58:46 +0200." <200008311158.NAA75155@freebsd.dk> Date: Fri, 01 Sep 2000 18:08:48 +0200 Message-ID: <29949.967824528@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I've put the latest patches for tagged queueing on ATA disks up >for ftp on: > > ftp://freebsd.dk/pub/ATA/ATA-tagged-queueing-diff-0831.gz On my testmachine: atapci0: port 0xffa0-0xffaf at device 4.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... ad0: 17206MB [34960/16/63] at ata0-master UDMA66 ad1: 14664MB [29795/16/63] at ata1-master tagged UDMA66 If I enable it on ad0, without without enabling it on ad1 it chokes. ad1 seems to be stable. Is there any way to read the firmware rev on ATA disks ? -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 9:16:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id 228C937B423; Fri, 1 Sep 2000 09:16:26 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.0/8.9.3) with ESMTP id e81GGON30018; Fri, 1 Sep 2000 18:16:24 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Soren Schmidt Cc: current@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Tagged queuing for ATA drives, patches up for testing In-Reply-To: Your message of "Thu, 31 Aug 2000 13:58:46 +0200." <200008311158.NAA75155@freebsd.dk> Date: Fri, 01 Sep 2000 18:16:24 +0200 Message-ID: <30016.967824984@critter> From: Poul-Henning Kamp Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of course I should have done a "boot -v" (thanks neph!) Doesn't work with tagged queueing: ad0: ATA-4 disk at ata0-master ad0: 17206MB (35239680 sectors), 34960 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 0 depth queue, UDMA66 ad0: piomode=4 dmamode=2 udmamode=4 cblid=1 Works with tagged queueing: ad1: ATA-4 disk at ata1-master ad1: 14664MB (30033360 sectors), 29795 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 31 depth queue, tagged UDMA66 ad1: piomode=4 dmamode=2 udmamode=4 cblid=1 -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD coreteam member | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 10: 1:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sofia.csl.sri.com (sofia.csl.sri.com [130.107.19.127]) by hub.freebsd.org (Postfix) with ESMTP id 1CDA337B43C for ; Fri, 1 Sep 2000 10:01:55 -0700 (PDT) Received: (from molter@localhost) by sofia.csl.sri.com (8.9.3/8.9.3) id KAA66115 for hackers@FreeBSD.ORG; Fri, 1 Sep 2000 10:02:41 -0700 (PDT) (envelope-from molter) From: Marco Molteni Date: Fri, 1 Sep 2000 10:02:41 -0700 To: hackers@FreeBSD.ORG Subject: Re: gdb remote debugging on slow computers Message-ID: <20000901100241.B66078@sofia.csl.sri.com> References: <200008312352.TAA03733@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <200008312352.TAA03733@hda.hda.com>; from dufault@hda.com on Thu, Aug 31, 2000 at 07:52:43PM -0400 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Aug 2000, Peter Dufault wrote: [..] > I want to attach a gdb running on my FreeBSD system to something > running on that wicked slow Sun. I've built a gdb with a target > machine of "sparc-sun-solaris2.7", I've got an executable, but I > haven't found a way to run something on the Sun that I can attach > to in order to debug remote processes. All I've found are ways to > connect to remote serial ports. Does anyone know if I can easily > do this? I am not sure I understood your question. If you mean: How can I use gdb + gdbserver via a TCP connection, you do the following: hostA (gdbserver) $ gdbserver hostB:5555 prog-to-be-debugged hostB (gdb) $ gdb (gdb) target remote hostA:5555 Notes: 1. the gdb documentation, although not clearly, explains this in section 13.4.1.5 2. the gdbserver I am using DOESN'T enforce the connection to come from hostB; this means that there is a race condition that allows the first connection to hostA, port 5555 to grab the debugging section! If you are interested I have a small shared library wrapper around accept() to fix this. Marco -- Marco Molteni "rough consensus and running code" SRI International, System Design Laboratory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 10:20:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from hda.hda.com (host65.hda.com [63.104.68.65]) by hub.freebsd.org (Postfix) with ESMTP id 6ACD237B440 for ; Fri, 1 Sep 2000 10:20:17 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.9.3/8.9.3) id NAA05759; Fri, 1 Sep 2000 13:21:06 -0400 (EDT) (envelope-from dufault) From: Peter Dufault Message-Id: <200009011721.NAA05759@hda.hda.com> Subject: Re: gdb remote debugging on slow computers In-Reply-To: <20000901100241.B66078@sofia.csl.sri.com> from Marco Molteni at "Sep 1, 2000 10:02:41 am" To: Marco Molteni Date: Fri, 1 Sep 2000 13:21:05 -0400 (EDT) Cc: hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 31 Aug 2000, Peter Dufault wrote: > > [..] > > > I want to attach a gdb running on my FreeBSD system to something > > running on that wicked slow Sun. I've built a gdb with a target > > machine of "sparc-sun-solaris2.7", I've got an executable, but I > > haven't found a way to run something on the Sun that I can attach > > to in order to debug remote processes. All I've found are ways to > > connect to remote serial ports. Does anyone know if I can easily > > do this? > > I am not sure I understood your question. If you mean: How can I use > gdb + gdbserver via a TCP connection, you do the following: Yes, I've found gdbserver now, I didn't know about it. There isn't a gdbserver for sparc-sun-solaris2.7 in the distribution, after foolishly trying to quickly build one against libgdb that would support any target I've just geocrawler archive-searched and found patches specific to sparc-sun-solaris2* which I'll now try. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 10:22:33 2000 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 2FA1D37B422 for ; Fri, 1 Sep 2000 10:22:28 -0700 (PDT) Received: from localhost (stein@localhost) by wally.eecs.harvard.edu (8.10.0/8.10.0) with ESMTP id e81HM5S20183; Fri, 1 Sep 2000 13:22:05 -0400 (EDT) Date: Fri, 1 Sep 2000 13:22:05 -0400 (EDT) From: Christopher Stein X-Sender: stein@wally To: Greg Lehey Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: remote gdb debugging In-Reply-To: <20000829120352.K11422@wantadilla.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /dev/cuaa1 turned out to be the culprit. I tested this by `echo "hello" > /dev/cuaa1` on the debugger and `cat /dev/cuaa1` on the debuggee. The hello makes it across. Now I'm having some "packet error" problems with kgdb. On the debuggee I ctrl-alt-esc into ddb and do: db> gdb db> step From the debugger I do: (gdb) target remote /dev/cuaa1 Remote debugging using /dev/cuaa1 Ignoring packet error, continuing... Ignoring packet error, continuing... Ignoring packet error, continuing... Couldn't establish connection to remote target Malformed response to offset query, timeout (gdb) Anyone seen this before? What did I miss? These two systems are identical hardware-wise .. so I would expect the baud rates to match (unless gdb does some setting in the background). thanks -Chris > > > > hhmmm.. any suggestions? /dev/ttyd1 worked for a 3.3/4.0-pre install in > > the past, but doesn't work for this new system, which is quite similar. > > Nothing has changed between 4.0 and now. I've had the devil's own job > in the past, and I suspect you've hit a different problem. Do you > have a breakout box on the line? If so, what's it showing? Also, > you've set the sio flags correctly (0x80 or 0x90) on the debugged > machine, right? > > Greg > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 11:18:30 2000 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 94BC037B424 for ; Fri, 1 Sep 2000 11:18:26 -0700 (PDT) Received: from localhost (stein@localhost) by wally.eecs.harvard.edu (8.10.0/8.10.0) with ESMTP id e81IIPo16519; Fri, 1 Sep 2000 14:18:25 -0400 (EDT) Date: Fri, 1 Sep 2000 14:18:25 -0400 (EDT) From: Christopher Stein X-Sender: stein@wally To: freebsd-hackers@freebsd.org, grog@lemis.com Subject: gdb remote connection Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I discovered the source of my problem and solved it. For those interested, here is an explanation: The flags of the serial I/O device to be used for remote debugging needs to be changed in the config file. I plugged a null modem cable across the two ports labeled 1 (the other one labeled 2) on the back of the computer. I assumed that these correspond to serial port 1 as the FreeBSD kernel sees the world (wrong assumption). Therefore, I only changed the permissions of sio0 in the config file. I was able to communicate across the serial line using device /dev/cuaa1 and doing things like echo "hello" > /dev/cuaa1. GDB, however, was unable to establish a remote connection when I did "target remote /dev/cuaa1" in kgdb. I started wondering about why the device has the number "1" and not "0". So I decided to change the permissions of sio1 in addition. It works! So it turns out the FreeBSD maps the physically labelled (i.e. etched in metal) port 2 to sio0 and port 1 to sio1! Sweet. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 13:55:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from merc95.us.sas.com (merc95.us.sas.com [149.173.6.5]) by hub.freebsd.org (Postfix) with ESMTP id DA14A37B424 for ; Fri, 1 Sep 2000 13:55:26 -0700 (PDT) Received: from merc95.us.sas.com ([127.0.0.1]) by merc95.us.sas.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2651.58) id RVYT7XPJ; Fri, 1 Sep 2000 16:55:25 -0400 Received: from 10.28.149.26 by merc95.us.sas.com (InterScan E-Mail VirusWall NT); Fri, 01 Sep 2000 16:55:25 -0400 (Eastern Daylight Time) Received: from bb01f39.unx.sas.com (bb01f39.unx.sas.com [10.16.2.246]) by mozart.unx.sas.com (8.9.3 (PHNE_18979)/8.9.3) with ESMTP id QAA01622 for ; Fri, 1 Sep 2000 16:55:24 -0400 (EDT) Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id QAA38750 for freebsd-hackers@FreeBSD.org; Fri, 1 Sep 2000 16:55:24 -0400 (EDT) (envelope-from jwd) Date: Fri, 1 Sep 2000 16:55:24 -0400 From: John DeBoskey To: freebsd-hackers@FreeBSD.org Subject: SIOCSPGRP documentation? Message-ID: <20000901165524.A38704@unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Like the subject says, I'm looking for documentation on the SIOCSPGRP ioctl call: rc = ioctl(port,SIOCSPGRP,&pid); I've gone through the source tree and while I can find references where it's used, and where the functionality is defined, there appears to be no doc (or man page). Basically, I've got portable code that works sometimes and fails others. It seems to revolve around a call(or lack thereof) to set the process group leader: if (setpgid (getpid (), getpid ()) == -1) { any pointers are appreciated. Thanks! John -- FreeBSD... The choice of those who know how to choose...(anon) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 15:29:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Awfulhak.org (tun.AwfulHak.org [194.242.139.173]) by hub.freebsd.org (Postfix) with ESMTP id F35C637B424 for ; Fri, 1 Sep 2000 15:29:51 -0700 (PDT) Received: from hak.lan.Awfulhak.org (root@hak.lan.awfulhak.org [172.16.0.12]) by Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA70393; Fri, 1 Sep 2000 23:26:58 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by hak.lan.Awfulhak.org (8.11.0/8.11.0) with ESMTP id e81MQY716346; Fri, 1 Sep 2000 23:26:35 +0100 (BST) (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200009012226.e81MQY716346@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexander Maret Cc: "'freebsd-hackers@freebsd.org'" , brian@Awfulhak.org Subject: Re: Redirect stdout/stderr to syslog [OFF-TOPIC] In-Reply-To: Message from Alexander Maret of "Fri, 01 Sep 2000 13:58:56 +0200." <58A002A02C5ED311812E0050044517F00D25DA@erlangen01.atrada.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 01 Sep 2000 23:26:33 +0100 From: Brian Somers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I wonder if it is possible to redirect stdout/stderr to syslog. > > Background: > I'm writing a program which starts (fork=>execvp) and observes > another program. I would like to redirect all output of the "execvped" > program to syslog. > > I know this is not really FBSD related but I hope you can help > me anyway. Please don't tell me that I should redirect the output > to a file and not to syslog. I know how to redirect the output to > a file (that's my prog doing at present state). I guess you could do something like: int fd; fd = open(_PATH_DEVNULL, O_RDONLY); dup2(fd, STDIN_FILENO); close(STDOUT_FILENO); openlog(....); dup2(STDOUT_FILENO, STDERR_FILENO); > Bye, > Alex -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 16:10:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id E593D37B424 for ; Fri, 1 Sep 2000 16:10:55 -0700 (PDT) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id QAA07594; Fri, 1 Sep 2000 16:10:41 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id QAA01332; Fri, 1 Sep 2000 16:10:41 -0700 (PDT) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id QAA14949; Fri, 1 Sep 2000 16:10:41 -0700 (PDT) From: Don Lewis Message-Id: <200009012310.QAA14949@salsa.gv.tsc.tdk.com> Date: Fri, 1 Sep 2000 16:10:40 -0700 In-Reply-To: <20000901152443.K46859@ringwraith.office1.bg> References: <58A002A02C5ED311812E0050044517F00D25DB@erlangen01.atrada.de> <20000901152443.K46859@ringwraith.office1.bg> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: Peter Pentchev , Alexander Maret Subject: Re: Redirect stdout/stderr to syslog [OFF-TOPIC] Cc: "'freebsd-hackers@freebsd.org'" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 1, 3:24pm, Peter Pentchev wrote: } Subject: Re: Redirect stdout/stderr to syslog [OFF-TOPIC] } On Fri, Sep 01, 2000 at 02:13:19PM +0200, Alexander Maret wrote: } > > -----Ursprungliche Nachricht----- } > > Von: Peter Pentchev [mailto:roam@orbitel.bg] } > > Gesendet: Freitag, 1. September 2000 14:00 } > > pipe your stdout/stderr to logger(1), and you're all set. } > > You may even } > > specify a facility/level to log with. } > > } > } > Thanks for your quick answer but I would prefer to } > do it entirely in C without calling external progs. } > I could think of a solution forking another child process } > which does the syslog logging and redirecting stdout/stderr } > of the execvped program via IPC to this child. } > } > But is there any easier solution? } } No, I don't think you can do anything cheaper than a fork and } a pipe(2). popen(), as suggested in another message, is pretty } much the same. I don't think stdio has a hook to capture all } the data a process is sending to a stream, and pass it to some } routine - that would be perfect, but unfortunately, I am not } aware of such a thing. I might be wrong though. It's not very widely implemented, so any code using it won't be portable, but take a look at the man page for fuopen(3). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 16:16:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sentinel.office1.bg (sentinel.office1.bg [195.24.48.182]) by hub.freebsd.org (Postfix) with SMTP id 0B37337B42C for ; Fri, 1 Sep 2000 16:16:39 -0700 (PDT) Received: (qmail 53292 invoked by uid 1001); 1 Sep 2000 23:13:20 -0000 Date: Sat, 2 Sep 2000 02:13:19 +0300 From: Peter Pentchev To: Don Lewis Cc: Alexander Maret , "'freebsd-hackers@freebsd.org'" Subject: Re: Redirect stdout/stderr to syslog [OFF-TOPIC] Message-ID: <20000902021319.A52922@ringwraith.office1.bg> References: <58A002A02C5ED311812E0050044517F00D25DB@erlangen01.atrada.de> <20000901152443.K46859@ringwraith.office1.bg> <200009012310.QAA14949@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009012310.QAA14949@salsa.gv.tsc.tdk.com>; from Don.Lewis@tsc.tdk.com on Fri, Sep 01, 2000 at 04:10:40PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Sep 01, 2000 at 04:10:40PM -0700, Don Lewis wrote: > On Sep 1, 3:24pm, Peter Pentchev wrote: > } No, I don't think you can do anything cheaper than a fork and > } a pipe(2). popen(), as suggested in another message, is pretty > } much the same. I don't think stdio has a hook to capture all > } the data a process is sending to a stream, and pass it to some > } routine - that would be perfect, but unfortunately, I am not > } aware of such a thing. I might be wrong though. > > It's not very widely implemented, so any code using it won't be > portable, but take a look at the man page for fuopen(3). I presume you meant funopen() :) Hmm this one looks really nice. I guess what the original poster wanted would be a call to fwopen(), then parsing the 'output' into lines and passing those to syslog().. I'll try it later today. Thanks for the pointer! G'luck, Peter -- If I had finished 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 Sep 1 20:43: 0 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 48BA737B423; Fri, 1 Sep 2000 20:42:57 -0700 (PDT) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id UAA10976; Fri, 1 Sep 2000 20:42:56 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id UAA02513; Fri, 1 Sep 2000 20:42:55 -0700 (PDT) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id UAA15526; Fri, 1 Sep 2000 20:42:54 -0700 (PDT) From: Don Lewis Message-Id: <200009020342.UAA15526@salsa.gv.tsc.tdk.com> Date: Fri, 1 Sep 2000 20:42:54 -0700 In-Reply-To: <20000901165524.A38704@unx.sas.com> References: <20000901165524.A38704@unx.sas.com> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: John DeBoskey , freebsd-hackers@FreeBSD.ORG Subject: Re: SIOCSPGRP documentation? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sep 1, 4:55pm, John DeBoskey wrote: } Subject: SIOCSPGRP documentation? } Hi, } } Like the subject says, I'm looking for documentation } on the SIOCSPGRP ioctl call: } } rc = ioctl(port,SIOCSPGRP,&pid); } } I've gone through the source tree and while I can find } references where it's used, and where the functionality } is defined, there appears to be no doc (or man page). Take a look at man 4 tty and the controlling terminal information in man 4 termios To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Sep 1 23:59: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 1159337B43F for ; Fri, 1 Sep 2000 23:59:02 -0700 (PDT) Received: from teabag.demon.co.uk ([193.237.4.110]) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 13V7GQ-000Evb-0A for freebsd-hackers@freebsd.org; Sat, 2 Sep 2000 06:58:54 +0000 Received: from localhost (cbh@localhost) by teabag.demon.co.uk (8.11.0/8.9.3) with ESMTP id e826vkE01208 for ; Sat, 2 Sep 2000 07:57:50 +0100 (BST) (envelope-from cbh@teabag.demon.co.uk) Date: Sat, 2 Sep 2000 07:57:45 +0100 (BST) From: Chris Hedley X-Sender: cbh@teabag.cbhnet To: freebsd-hackers@freebsd.org Subject: AHC resources and SCB problems in 5.0-CURRENT Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I hope this is the right place to ask; I've searched the mailing lists and can't find any comments, so I hope it's not just me! I'm following the current development branch and all has been (generally) okay until the 29th of aug, since when I've been unable to get the kernel to boot successfully; initially the messages are strewn with "can't allocate register resources" (sorry, I don't have the exact details as they scroll off the screen before I have a chance to grab them and I can't capture dmesg since it's not booting successfully) After it starts the 2nd CPU and tries to access the Adaptec 7895 I get the following messages over and over: ahc0: ahc_intr - referenced scb not valid during SELTO (31, 255) ahc1: ahc_intr - referenced scb not valid during SELTO (31, 139) After a while the system may panic with the message: (probe0:ahc0:0:0:0): SCB 0x9 - timed out while idle, SEQADDR == 0xb panic: Waiting List inconsistency. SCB index == 255, yet numscbs == 20 The system I'm using is a dual Pentium III, Tyan Thunder DLUAN1658 BX motherboard, onboard Adaptec 7895 dual-channel UW scsi. Fairly unexciting setup overall. Anybody got any ideas? Cheers, Chris. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 2 3:12:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from happy.koganei.wide.ad.jp (koganei.wide.ad.jp [202.249.37.254]) by hub.freebsd.org (Postfix) with ESMTP id DD31137B424; Sat, 2 Sep 2000 03:12:20 -0700 (PDT) Received: from localhost (eeyore.koganei.wide.ad.jp [202.249.37.70]) by happy.koganei.wide.ad.jp (8.9.3/8.9.3) with ESMTP id TAA84169; Sat, 2 Sep 2000 19:12:24 +0900 (JST) (envelope-from ikob@koganei.wide.ad.jp) To: msmith@FreeBSD.ORG Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: IEEE1394 driver system for -current In-Reply-To: <200008250233.TAA00857@mass.osd.bsdi.com> References: <399E5A33.B552E780@koganei.wide.ad.jp> <200008250233.TAA00857@mass.osd.bsdi.com> X-Mailer: Mew version 1.95b3 on XEmacs 21.1 (Canyonlands) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000902191559C.ikob@koganei.wide.ad.jp> Date: Sat, 02 Sep 2000 19:15:59 +0900 From: ikob X-Dispatcher: imput version 20000228(IM140) Lines: 79 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Mike, and sorry for late responce, I basically understand your comment. I think the code clean-up is important befor committing. However, as you pointed out, I would like to consider structure of my code for according the treatment of device on -current on going. I basically respect current structure already implemented and USB experience could be used for IEEE1394. I have not understood NEWBUS designe architecture and I have watched the architecture in the source only. (Someonelet me know the pointer!!) After investigating the archtecture, I will decide the new structure of IEEE1394. ikob@koganei.wide.ad.jp From: Mike Smith Subject: Re: IEEE1394 driver system for -current Date: Thu, 24 Aug 2000 19:33:02 -0700 Message-ID: <200008250233.TAA00857@mass.osd.bsdi.com> msmith> msmith> There are several things that need to be fixed. I'm not going to be nice msmith> about the code, because it needs some major work before it is ready, but msmith> I do think that it is worth using your code (and your skills) in some msmith> form. msmith> msmith> 1) The code is very messy. This makes it hard to read. It needs to be msmith> reformatted before committing to reduce whitespace/style changes msmith> afterwards. msmith> msmith> 2) There are a lot of "magic numbers" (numeric values for registers and msmith> so forth) rather than defined constants. This makes it hard to work msmith> out what parts of the code are doing. msmith> msmith> 3) The code lacks structure. There are some very clear divisions that msmith> should be made between the various components in the 1394 stack, and msmith> these are not being made. Fixing this will involve moving a lot of msmith> code around, and should be done before the code is committed. msmith> msmith> 1394 can be looked at as being quite similar to USB (the predominant msmith> interface model is OHCI, also used for USB). The obvious software msmith> components are: msmith> msmith> a) Host adapter driver (eg. TI Lynx, NEC, Adaptec, etc.) msmith> b) Generic 1394 layer msmith> c) Peripheral/protocol driver layer (eg. DV, CAM shim, etc) msmith> c') Layered peripheral/protocol driver layer msmith> msmith> The interface between layers a) and b), and between layers b) and c) msmith> and between layers c) and c') should all be clearly defined. Using msmith> newbus and defining these interactions in terms of parent-child msmith> relationships and bus methods will make this very easy. msmith> msmith> Having said so many cruel things about your code, it's clear that you've msmith> spent a lot of time making your stack work, and during that time you must msmith> have accumulated a lot of experience with these peripherals. I understand msmith> that Warner has proposed you be granted CVS commit access in order to work msmith> on your code in the FreeBSD CVS repository, and I'm in favour of this. I msmith> would, however, like to see the above issues addressed before the initial msmith> import. msmith> msmith> One option that you might want to consider is working with Bill Paul on msmith> the cleanup and restructuring process. Bill has a lot of experience with msmith> network-like peripherals, and with the way in which we like things to be msmith> done. In combination with your experience with 1394 in general, I think msmith> this would result in some very good and useful code. I've already spoken msmith> to Bill about this, and he seemed interested. (Apologies if I'm dumping msmith> you in it here, pal. 8) msmith> msmith> In summary, then, I would encourage you to consider the points above, and msmith> engage in some discussion (either on the -arch list or on a new msmith> freebsd-1394 list) about how to go about reorganising and cleaning up your msmith> code ready for committing as soon as practical. msmith> msmith> Regards, msmith> msmith> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 2 14:47:15 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.122.47]) by hub.freebsd.org (Postfix) with ESMTP id CC80837B43F for ; Sat, 2 Sep 2000 14:47:07 -0700 (PDT) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.10.1/8.10.1) with ESMTP id e82Ll4C88213; Sat, 2 Sep 2000 14:47:05 -0700 (PDT) Date: Sat, 2 Sep 2000 14:47:04 -0700 (PDT) From: Doug White To: Arjan Knepper Cc: hackers FreeBSD Subject: Re: Cyclades Cyclom Ze (64 serialportboard) In-Reply-To: <39AF5212.271E5032@jak.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 1 Sep 2000, Arjan Knepper wrote: > Doug White wrote: > > > > On Thu, 31 Aug 2000, Arjan Knepper wrote: > > > > > Anyone experience with this board? > > > Any comments? Recomandations? > > > > I have a ze card that we bought for use as a cheap term server, but found > > that the card is particular about the motherboard chipset. We had some > > telenet Celeron 1Us that we wanted to use but the card wouldn't init. We > > put it in a standard pentium box and it worked. We still have that card > > with a 16 port box that I've been tempted to play with. > > > > We ended up using good ol' cisco 2511s. > > Thanks, we had same kind of problem with an YeP card on a intel > 810 chipset. Works without problems on a intel 440 chipset. > > I seems to me the Ze is not supported in freebsd 4.0 or 4.1 is > it? Considering you have to grab the cz driver from Cyclades themselves and they only have 3.X drivers, I would say so. I suppose it's time to kick them into action to get 4.X drivers out. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 2 17:36:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id F203F37B422 for ; Sat, 2 Sep 2000 17:36:37 -0700 (PDT) Received: (from grog@localhost) by wantadilla.lemis.com (8.11.0/8.9.3) id e830aQR47215; Sun, 3 Sep 2000 10:06:26 +0930 (CST) (envelope-from grog) Date: Sun, 3 Sep 2000 10:06:26 +0930 From: Greg Lehey To: Christopher Stein Cc: freebsd-hackers@freebsd.org Subject: Re: gdb remote connection Message-ID: <20000903100625.F66079@wantadilla.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from stein@eecs.harvard.edu on Fri, Sep 01, 2000 at 02:18:25PM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 1 September 2000 at 14:18:25 -0400, Christopher Stein wrote: > > Hi, I discovered the source of my problem and solved it. For those > interested, here is an explanation: > > The flags of the serial I/O device to be used for remote debugging > needs to be changed in the config file. I told you this a while ago. You can also set them with UserConfig or in the loader configuration. > I plugged a null modem cable across the two ports labeled 1 (the > other one labeled 2) on the back of the computer. I assumed that > these correspond to serial port 1 as the FreeBSD kernel sees the > world (wrong assumption). Therefore, I only changed the permissions > of sio0 in the config file. You can't change permissions in the config file. What did you really do? > I was able to communicate across the serial line using device > /dev/cuaa1 and doing things like echo "hello" > /dev/cuaa1. /dev/cuaa1 isn't sio0. It's sio1. > GDB, however, was unable to establish a remote connection when I did > "target remote /dev/cuaa1" in kgdb. I started wondering about why > the device has the number "1" and not "0". So I decided to change > the permissions of sio1 in addition. It works! Yes, that's reasonable. > So it turns out the FreeBSD maps the physically labelled > (i.e. etched in metal) port 2 to sio0 and port 1 to sio1! No, this is completely incorrect. First, what's etched in metal has nothing to do with the matter. Secondly, the first serial port is sio0. The second serial port is sio1. If this is different on your computer, then that's where the problem lies. This is all described in the man page, of course: sio(4). Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Sep 2 22:48:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id C599437B422 for ; Sat, 2 Sep 2000 22:48:47 -0700 (PDT) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA11558 for ; Sun, 3 Sep 2000 01:48:57 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Sun, 3 Sep 2000 01:48:57 -0400 (EDT) From: Adam To: freebsd-hackers@FreeBSD.ORG Subject: Re: Cheap 1000Gbyte machine Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Passing this on... :) ---------- Forwarded message ---------- Date: Tue, 22 Aug 2000 20:31:00 -0400 (EDT) From: General Lee D Mented To: bsdx@looksharp.net Subject: FWD: Re: Cheap 1000Gbyte machine (fwd) >On Fri, 18 Aug 2000, Jonathan Laventhol wrote: > >> Hello Folks -- >> >> Anybody built a file server with approx 1000 Gbyte or more? >> Or even 200 Gbyte? >> >> I'm looking for a cheap simple way of doing this. Lots of >> IDE drives? (How many can you have?) Or SCSI? (Again, >> how many can you have?). >> >> It's for lots of 1 Mbyte files: no huge files. >> >> Thanks for any tips. > >You might want to check out the Arena Industrial II Rackmount RAID system >from "www.raidweb.com". It has 8 x UDMA controllers that connect to the >host via Ultra2 SCSI (platform independant). Buy two (or more) of those >and 16 x (60/80 gb Maxtor UMDA Drives or 75 gb IBM UMDA Drives). > >2 x Arena Industrial II Rackmount RAID $3,975 >16 x Maxtor UDMA 60 gb Hard Drives $3,680 > >Total Cost $7,655 > >That comes out to about $7.98 / gb... > >--- >Mike Wade (mwade@cdc.net) There's several ways to go about this, the stupid way, the cheap way, the efficient way, and the expensive way. The stupid way is to throw 4 or more Fastrak controllers into a motherboard and hope it works. Yes, I know, 4 drives per controller, some controllers have RAID. Well the RAID is really 99.9% software anyway, (otherwise why would it be so easy to modify the non-RAID controller into one?) and because of master/slave you can't access all the drives at once, and there's no write cache, command queue, or sorting, so your write performance will suck balls. You really want high rpm drives for this because drive latency is severely going to cripple you and be the limiting factor. Cost: $20 per controller x 4 = 80 controller cost $420 per HD (IBM 75GXP 60GB) = 6720 drive cost cost per TB = $7083 The cheap way is to get 2x 3ware Escalade 6800s and start loading large IDE drives, like 60 or 75GB IBM 75GXP, or 61.4GB Maxtor 96147U8. This will cut your cpu load way down, save slots, and still be relatively cheap. 7200 vs 5400rpm is fairly moot as 16 drives in parallel need to only sustain 8.25MB/sec each to saturate PCI's theoretical limits. The latency due to lower spindle speed isn't as great an issue because of 3ware's command queue and sort (normally a scsi-only feature). Cost: $279 per controller x2 = $558 $225 per HD (Maxtor 61.4GB) x16 = $3600 cost per TB = $4232 The efficient way is to optimize the system for sustainable bandwidth. Most servers aren't too CPU intensive, rather more memory or disk intensive. Thus you can go with slightly older highend hardware but get better results than current mainstream hardware. For example, a SuperMicro P6DLH, and some AMI MegaRAID 466s. The P6DLH is an LX based motherboard with 9PCI and an I2O compliant i960 coprocessor onboard. The concept is that I2O compliant devices (like the MegaRAID and some network cards) can send and recieve data to and from each other and system ram via the i960, without bothering the host CPU. This usually results in much less overhead per memory transfer. These controllers also support large onboard caches (16MB stock, up to 128MB FPM Parity SIMMs) to greatly improve write performance. The downside is of course, the cost involved. For hard drives, the best pricepoint is currently the Quantum Atlas V 36.7GB. (Yes even better than the 47GB Elite when I checked.) Cost: $199 for the motherboard = $199 $149 x2 for controller = $149 $475 x27 for drives = $12825 cost per TB = $13294 The expensive way is to just go flat out for the highest performing hardware, which is a mistake because even our cheap solution was already saturating the PCI bus, and even if we double that performance we could build several cheap solutions for less than one expensive one. This route would be the SuperMicro S2QR6, which is a Quad Xeon Serverworks board featuring 64bit PCI, a DPT PM3755F-2F 64bit PCI controller with dual fiberchannel loops and 256MB cache onboard, and a LARGE number of fiberchannel cheetah x15s. This is far beyond overkill given how badly even 64bit PCI will cripple the system. Cost: $2555 for the motherboard = $2555 $1532 for the base DPT = $1532 $282 x 4 for 64MB cache modules = $1128 $480 x 54 for cheetah x15s = $25920 cost per TB = $31336 All this still neglects the cost of case, powersupply, cpu, etc. As we can see, 3ware is by far the cheapest. "But what about the promise with the cheap HDs?", you ask. Even with 7200rpm drives the conflicts are going to kill its performance with only a few users. I don't even want to consider it on 5400rpm drives, as it probably would spend so much time waiting for seeks and changing master/slave and syncing spindles to complete RAID stripes that it wouldn't be very useful. ______________________________________________ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup ______________________________________________ FREE Personalized Email at Mail.com Sign up at http://www.mail.com/?sr=signup To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message