From owner-freebsd-hackers Sun Dec 12 0:22:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B337715096 for ; Sun, 12 Dec 1999 00:22:11 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.8.7/8.8.7) with ESMTP id AAA08125; Sun, 12 Dec 1999 00:23:22 -0800 Date: Sun, 12 Dec 1999 00:23:22 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Ronald F. Guilmette" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI tape minor device numbers In-Reply-To: <1032.944973464@monkeys.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 > Can anyone interpret this for me: > > HARDWARE FAILURE asc:0,4 > > What does it mean? > > It this just the numeric code for ``Buy another tape drive''? > :-) Yes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 7:41:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 4BB7414D34; Sun, 12 Dec 1999 07:41:31 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id QAA19005; Sun, 12 Dec 1999 16:38:29 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id PAA03904; Sun, 12 Dec 1999 15:59:33 +0100 (CET) From: Juergen Lock Date: Sun, 12 Dec 1999 15:59:32 +0100 To: Mike Smith Cc: zzhang@cs.binghamton.edu, freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: loader hacks (was: Re: easyboot far into disk) Message-ID: <19991212155932.A1107@saturn.kn-bremen.de> References: <19991107035454.B59629@saturn.kn-bremen.de> <199911071957.LAA13619@dingo.cdrom.com> <19991111224730.A739@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <19991111224730.A739@saturn.kn-bremen.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Cc'd to -hackers because, well, it contains hacks...) On Thu, Nov 11, 1999 at 10:47:30PM +0100, nox wrote: > On Sun, Nov 07, 1999 at 11:57:26AM -0800, Mike Smith wrote: > > > > Rootdev ought to work, actually. But if you get it wrong, the loader > > > > will fall back to using currdev. > > > > > > Hmm then thats strange. I first tried rootdev, which didn't work, and > > > then later currdev, which did work, and i believe i used the same value > > > both times! Or was rootdev fixed only recently, the boot floppies i > > > had lying around and tested this on weren't the latest... > > > > I thought rootdev was fixed a long time back. If it's not, please tell > > me and I'll fix it again. 8) > > Alright I finally got around testing this with a later kern.flp > (3.3-R actually), and it still didn't work. ... Well i played with this once more yesterday and now i know what was wrong: Unlike currdev, rootdev needs a `:' at the end... So either I'm blind or the manpage needs fixing. :) I also actually started making that FAQ entry (yeah!), and then wondered if you could also make an automagic boot floppy for a root disk that is entirely invisible to the BIOS, like when its on a BIOS-less (but otherwise supported) SCSI controller. I didn't find a way to do it with the original (-stable) loader, but when i made this patch, Index: biosdisk.c =================================================================== RCS file: /home/cvs/cvs/src/sys/boot/i386/libi386/biosdisk.c,v retrieving revision 1.20.2.7 diff -u -u -r1.20.2.7 biosdisk.c --- biosdisk.c 1999/08/29 16:20:59 1.20.2.7 +++ biosdisk.c 1999/12/12 00:14:52 @@ -785,23 +785,45 @@ int bd_getdev(struct i386_devdesc *dev) { - struct open_disk *od; + struct open_disk *od = NULL; int biosdev; int major; int rootdev; char *nip, *cp; int unitofs = 0, i, unit; + /* XXX kludge to allow the type of the root disk to be specified */ + cp = getenv("root_disk_type"); biosdev = bd_unit2bios(dev->d_kind.biosdisk.unit); DEBUG("unit %d BIOS device %d", dev->d_kind.biosdisk.unit, biosdev); - if (biosdev == -1) /* not a BIOS device */ + if (biosdev == -1) { /* not a BIOS device */ + int lastbiosdev; + /* + * BIOS doesn't know about this disk, this is not an error + * when root_disk_type is set unless the number is + * completely bogus + * (set root_disk_type=da and you may e.g. have the root + * disk hanging off a BIOS-less SCSI controller...) + */ + if (!cp || dev->d_kind.biosdisk.unit < 0 || + dev->d_kind.biosdisk.unit >= 256) + return(-1); + /* + * numbering of unknown-to-BIOS units starts with the first + * hard disk above the last one the BIOS saw, this is 0x80 + * if the BIOS only saw floppies + */ + lastbiosdev = bd_unit2bios(nbdinfo - 1); + biosdev = dev->d_kind.biosdisk.unit - nbdinfo + + (lastbiosdev < 0x80 ? 0x80 : lastbiosdev + 1); + } else if (bd_opendisk(&od, dev) != 0) /* oops, not a viable device */ return(-1); - if (bd_opendisk(&od, dev) != 0) /* oops, not a viable device */ - return(-1); - if (biosdev < 0x80) { + /* only assume floppy if root_disk_type is not set or is *fd* */ + if ((biosdev < 0x80 && !cp) || strstr(cp, "fd")) { /* floppy (or emulated floppy) or ATAPI device */ - if (bdinfo[dev->d_kind.biosdisk.unit].bd_type == DT_ATAPI) { + if ((cp && !strcmp(cp, "wfd")) || + bdinfo[dev->d_kind.biosdisk.unit].bd_type == DT_ATAPI) { /* is an ATAPI disk */ major = WFDMAJOR; } else { @@ -810,8 +832,10 @@ } } else { /* harddisk */ - if ((od->od_flags & BD_LABELOK) && (od->od_disklabel.d_type == DTYPE_SCSI)) { - /* label OK, disk labelled as SCSI */ + if ((cp && !strcmp(cp, "da")) || + (od && (od->od_flags & BD_LABELOK) && + (od->od_disklabel.d_type == DTYPE_SCSI))) { + /* label OK or root_disk_type set, disk labelled as SCSI */ major = DAMAJOR; /* check for unit number correction hint, now deprecated */ if ((nip = getenv("num_ide_disks")) != NULL) { @@ -820,23 +844,24 @@ if ((cp != nip) && (*cp == 0)) unitofs = i; } - } else if ((od->od_flags & BD_LABELOK) && - (od->od_disklabel.d_type == DTYPE_DOC2K)) { + } else if ((cp && !strcmp(cp, "fla")) || + (od && (od->od_flags & BD_LABELOK) && + (od->od_disklabel.d_type == DTYPE_DOC2K))) { major = FLAMAJOR; } else { /* assume an IDE disk */ major = WDMAJOR; } } + /* allow for #wd compenstation in da case */ + unit = (biosdev & 0x7f) - unitofs; + /* XXX a better kludge to set the root disk unit number */ if ((nip = getenv("root_disk_unit")) != NULL) { i = strtol(nip, &cp, 0); /* check for parse error */ if ((cp != nip) && (*cp == 0)) unit = i; - } else { -/* allow for #wd compenstation in da case */ - unit = (biosdev & 0x7f) - unitofs; } rootdev = MAKEBOOTDEV(major, Index: bootinfo.c =================================================================== RCS file: /home/cvs/cvs/src/sys/boot/i386/libi386/bootinfo.c,v retrieving revision 1.15.2.3 diff -u -u -r1.15.2.3 bootinfo.c --- bootinfo.c 1999/08/29 16:21:01 1.15.2.3 +++ bootinfo.c 1999/12/11 20:12:40 @@ -262,6 +262,7 @@ default: printf("aout_exec: WARNING - don't know how to boot from device type %d\n", rootdev->d_type); + return(EINVAL); } free(rootdev); *bootdevp = bootdevnr; (the last changes are actually fixes for what looked like genuine bugs, tho they don't seem to matter much.) I was then able to boot from a floppy with the SCSI BIOS turned off: set root_disk_type=da set root_disk_unit=2 set rootdev=disk0s1a: although when i tried a cold boot i got a panic because apparently the kernel didn't expect to have to `start unit' some disks and wait for them to come online. (well it did send the start unit to one, paniced, then the at the next boot started another... until when all were up, so in the end the boot `just' took longer...) Should i try to make a proper bugreport for that or is it to be expected? And note how you still have to split the actual device name up (da2s1a here) if you don't want to depend on how the BIOS numbers the disks which often differs from the kernel. (`da' goes into root_disk_type, `2' goes into root_disk_unit und the slice/partition `s1a' goes into rootdev. at least the 0 in disk0 should not matter anymore now when both of the others are set so these three lines could then also be generated by e.g. sysinstall without any additional knowledge about the BIOS.) I believe -current now also has a fix for this although i don't know if the way its been done there would still work with older kernels. With this you should be able to boot even pre-loader systems if you put the old kernel on the floppy... Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 11:31:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from onyx.extra.dp.ua (bowling.dp.ua [195.248.163.33]) by hub.freebsd.org (Postfix) with ESMTP id 46F7414CA5; Sun, 12 Dec 1999 11:31:22 -0800 (PST) (envelope-from white@onyx.extra.dp.ua) Received: (from white@localhost) by onyx.extra.dp.ua (8.9.3/8.9.3/BSD) id VAA04064; Sun, 12 Dec 1999 21:31:15 +0200 (EET) Date: Sun, 12 Dec 1999 21:31:13 +0200 From: Alexander Prohorenko To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: ATAPI tape drive (wst0) problem. Message-ID: <19991212213113.A3710@extra.dp.ua> Reply-To: white@la.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i X-Operating-System: FreeBSD 2.2.8-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've got some problem and I need your help to solve it. uname -mrs FreeBSD 3.3-STABLE i386 dmesg output: wdc1: unit 1 (atapi): , removable, accel, iordy I've added such strings to kernel configuration file: options ATAPI device wst0 Of course, I did: cd /dev ./MAKEDEV wst0 ls -al /dev/rwst0 crw-r----- 1 root operator 90, 0 Dec 12 12:05 /dev/rwst0 When I'm trying to do: mt -f /dev/rwst0 status I'm getting: mt: /dev/rwst0: Device not configured and Dec 12 12:27:20 zzz-oz /kernel: ENXIO lun=0, wstnlun=0, im=0xc01d0b34 Please, be so kind to let me know where is my mistake and what I'm doing incorrect. `man wst` didn't help, - besides, it refers to wst(1) but I was failed to find such. Thank you very much and looking forward your help. -- Alexander Prohorenko (white@la.com) ..."Death is God's way of telling you not to be such a wise guy." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 11:40:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 17EF014CB4 for ; Sun, 12 Dec 1999 11:40:16 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2650.21) id ; Sun, 12 Dec 1999 12:40:14 -0700 Message-ID: <64003B21ECCAD11185C500805F31EC0304D96BE6@houston.matchlogic.com> From: Charles Randall To: freebsd-hackers@freebsd.org Subject: timezone var vs timezone() function Date: Sun, 12 Dec 1999 12:40:06 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my FreeBSD 3.3R system, /usr/include/time.h includes a prototype for the timezone() function. The timezone(3) manual page indicates that this function is for compatibility purposes only and notes that the timezone() function first appeared in AT&T Unix V7. Version 2 of the Single Unix Specification (www.opengroup.org) states that time.h defines a global variable named timezone which indicates the difference in seconds between the local timezone and UTC. It also notes that this is, "Derived from Issue 1 of the SVID." I don't know what that means. I realize that I can work around this in an application a number of ways. For example, use FreeBSD's tm_gmtoff member of struct tm. However, is it a long-term goal for FreeBSD to conform to the Single Unix Specification? Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 11:45:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eth0-gw.poli.hu (eth0-gw.poli.hu [195.199.8.27]) by hub.freebsd.org (Postfix) with ESMTP id 49CCE14CEF for ; Sun, 12 Dec 1999 11:45:30 -0800 (PST) (envelope-from mauzi@faber.poli.hu) Received: from faber.poli.hu ([195.199.8.29]) by eth0-gw.poli.hu with esmtp (Exim 3.11 #1 (Debian)) id 11xEvy-0004ux-00 for ; Sun, 12 Dec 1999 20:45:30 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.11 #1 (Debian)) id 11xEw0-0005dC-00 for ; Sun, 12 Dec 1999 20:45:32 +0100 Date: Sun, 12 Dec 1999 20:45:32 +0100 (CET) From: Egervary Gergely To: freebsd-hackers@freebsd.org Subject: silo overflows 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 hy, i still can't get rid of silo overflows :( 3.3-STABLE, a simple pentium2 system w/ external 33.6 rockwell modem attached to sio0. i see nothing special. and the overflows just still come :( what should i check/ look after? --mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 12: 0:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7941C14D87; Sun, 12 Dec 1999 12:00:07 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA63063; Sun, 12 Dec 1999 20:59:56 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912121959.UAA63063@freebsd.dk> Subject: Re: ATAPI tape drive (wst0) problem. In-Reply-To: <19991212213113.A3710@extra.dp.ua> from Alexander Prohorenko at "Dec 12, 1999 09:31:13 pm" To: white@la.com Date: Sun, 12 Dec 1999 20:59:56 +0100 (CET) Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alexander Prohorenko wrote: > Hello, > > I've got some problem and I need your help to solve it. > > uname -mrs > FreeBSD 3.3-STABLE i386 > > dmesg output: > > wdc1: unit 1 (atapi): , removable, accel, iordy Hmm, I've gotten a failure report on one of these before, I'm afraid we dont have support for this drive, it seems as if Sony didn't follow the ATAPI spec on the model (same goes for Onstream btw). Until I get some docs out of Sony, or a drive to experiment with, there really isn't much I can do... -SЬren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 12: 5:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id C194614CCB for ; Sun, 12 Dec 1999 12:05:49 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id OAA58184 for freebsd-hackers@freebsd.org; Sun, 12 Dec 1999 14:05:42 -0600 (CST) Message-ID: <19991212140541.A57969@Denninger.Net> Date: Sun, 12 Dec 1999 14:05:41 -0600 From: Karl Denninger To: freebsd-hackers@freebsd.org Subject: ATAPI tape support - how to format? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Well, I'm in for it now ;-) I'm going to have to start supporting ATAPI tape drives on FreeBSD for some business associates - they're too cheap to go SCSI. Some of these (if not all) require formatting, right? This leads to the obvious question: How do you format a tape for these drives under FreeBSD? :-) Anything else I should know offhand other than "plug it in and use dump like everything else"? -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 12:25:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (Postfix) with ESMTP id 3C7B214D06; Sun, 12 Dec 1999 12:25:19 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.9.3/8.9.3) id PAA72119; Sun, 12 Dec 1999 15:29:32 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199912122029.PAA72119@cc942873-a.ewndsr1.nj.home.com> Subject: Re: ATAPI tape drive (wst0) problem. In-Reply-To: <19991212213113.A3710@extra.dp.ua> from Alexander Prohorenko at "Dec 12, 1999 09:31:13 pm" To: white@la.com Date: Sun, 12 Dec 1999 15:29:31 -0500 (EST) Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Reply-To: cjclark@home.com 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 Alexander Prohorenko wrote, > Hello, > > I've got some problem and I need your help to solve it. > > uname -mrs > FreeBSD 3.3-STABLE i386 > > dmesg output: > > wdc1: unit 1 (atapi): , removable, accel, iordy > > I've added such strings to kernel configuration file: > > options ATAPI > device wst0 And you did rebuild the kernel and reboot right? The dmesg output should contain references to this device, wst0, besides just the fact wcd1 found _something,_ no? -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 13: 5:47 1999 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 C292314E96 for ; Sun, 12 Dec 1999 13:05:45 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA90073; Sun, 12 Dec 1999 13:05:30 -0800 (PST) Date: Sun, 12 Dec 1999 13:05:29 -0800 (PST) From: Julian Elischer To: Egervary Gergely Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: silo overflows 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 what kind of disk to you have? and the chipset? (this may seem irrelevant but misconfigured DMA devices can block the cpu for long enough to cause this sort of thing in some cases). ALSO check systat -vmstat while this is happenning and check that you don't have a source of spurious interrupts. Julian On Sun, 12 Dec 1999, Egervary Gergely wrote: > hy, > > i still can't get rid of silo overflows :( > > 3.3-STABLE, a simple pentium2 system w/ external 33.6 rockwell modem > attached to sio0. i see nothing special. and the overflows just still come > :( > > what should i check/ look after? > > --mauzi > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 13:19:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eth0-gw.poli.hu (eth0-gw.poli.hu [195.199.8.27]) by hub.freebsd.org (Postfix) with ESMTP id 4CE6014DBE for ; Sun, 12 Dec 1999 13:19:17 -0800 (PST) (envelope-from mauzi@aquarius.poli.hu) Received: from dial-6.poli.hu ([195.199.8.22] helo=aquarius.poli.hu) by eth0-gw.poli.hu with esmtp (Exim 3.11 #1 (Debian)) id 11xGOi-0004vt-00 for ; Sun, 12 Dec 1999 22:19:16 +0100 Received: from mauzi (helo=localhost) by aquarius.poli.hu with local-esmtp (Exim 3.03 #1) id 11xGS5-0000L0-00 for freebsd-hackers@freebsd.org; Sun, 12 Dec 1999 22:22:45 +0100 Date: Sun, 12 Dec 1999 22:22:45 +0100 (CET) From: Gergely EGERVARY Reply-To: mauzi@poli.hu To: freebsd-hackers@freebsd.org Subject: Re: silo overflows 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 > what kind of disk to you have? and the chipset? (this may seem irrelevant > but misconfigured DMA devices can block the cpu for long enough to cause > this sort of thing in some cases). ALSO check systat -vmstat while this > is happenning and check that you don't have a source of spurious > interrupts. > > Julian intel 440bx chipset (abit-bh6 mainboard) quantum cx13.0a ata4 disk actually i don't see any spurious interrupts :) anyway... the raw disk read access speed (not fs!) is about 3MB/sec this disk reads more than 10MB/secs with other OS'es... any ideas? -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 13:24:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id DA60714DB8 for ; Sun, 12 Dec 1999 13:24:44 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id PAA91492 for freebsd-hackers@freebsd.org; Sun, 12 Dec 1999 15:24:43 -0600 (CST) Message-ID: <19991212152443.A80500@Denninger.Net> Date: Sun, 12 Dec 1999 15:24:43 -0600 From: Karl Denninger To: freebsd-hackers@freebsd.org Subject: Reminder - changes to sources and such Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Just something to keep in mind.... I am trying to update from a Juneish -CURRENT to a current -CURRENT. I've run into two instances (the latest being the use of "colldef" in /usr/src/share/colldef) where older binaries are INCOMPATIBLE with the newer files they are processing, AND the "make buildworld" target uses the OLD binary in an attempt to read the NEW file. This blows up, obviously. Isn't this a dependancy that should be caught? More specifically, shouldn't the "buildworld" target build /usr/src/usr.bin, bin, sbin, etc FIRST - and THEN rebuild things in share USING THE OBJECTS IT JUST BUILT? I've run into this before with the control files for make in /usr/share/mk being read for a "buildworld", and if they are far enough out of date you get screwed by them - but this is the first time I've seen it with general utilities and share directory where things have to be run through a table processor. Having been bit twice now in my most recent attempt to update by this, I thought I'd post here and see if this is expected behavior or not, and if I'm missing something in the "correct" steps to take to run a buildworld. I would *expect* that in general I should be able to rm -rf /usr/src and /usr/obj, "cvs co src" from the /usr directory, cd into there, and type "make buildworld" and have it complete with *NO* outside dependancies except what is necessary to bootstrap the compiler initially (that is, a working compiler to build the compiler with.) If I can't do this then updating a system in the general case to the current software simply isn't possible without manual intervention. Am I missing something here? -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 13:31:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 4AEFC14C22; Sun, 12 Dec 1999 13:31:20 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 94E341CA0; Mon, 13 Dec 1999 05:31:17 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Karl Denninger Cc: freebsd-hackers@freebsd.org, marcel@freebsd.org Subject: Re: Reminder - changes to sources and such In-Reply-To: Message from Karl Denninger of "Sun, 12 Dec 1999 15:24:43 CST." <19991212152443.A80500@Denninger.Net> Date: Mon, 13 Dec 1999 05:31:17 +0800 From: Peter Wemm Message-Id: <19991212213117.94E341CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Denninger wrote: > Hi folks, > > Just something to keep in mind.... > > I am trying to update from a Juneish -CURRENT to a current -CURRENT. > > I've run into two instances (the latest being the use of "colldef" in > /usr/src/share/colldef) where older binaries are INCOMPATIBLE with the newer > files they are processing, AND the "make buildworld" target uses the OLD > binary in an attempt to read the NEW file. > > This blows up, obviously. This would appear to be another thing Marcel has broken.. colldef used to have special treatment, but it no longer has. peter@overcee[5:29am]~src-124> cvs up -p -r1.89 Makefile.inc1 | grep colldef usr.bin/colldef \ peter@overcee[5:29am]~src-125> grep colldef Makefile.inc1 peter@overcee[5:29am]~src-126> Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 13:39:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id B418A152AE; Sun, 12 Dec 1999 13:39:09 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id PAA03733; Sun, 12 Dec 1999 15:38:53 -0600 (CST) Message-ID: <19991212153853.A1509@Denninger.Net> Date: Sun, 12 Dec 1999 15:38:53 -0600 From: Karl Denninger To: Peter Wemm Cc: freebsd-hackers@FreeBSD.ORG, marcel@FreeBSD.ORG Subject: Re: Reminder - changes to sources and such References: <19991212213117.94E341CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19991212213117.94E341CA0@overcee.netplex.com.au>; from Peter Wemm on Mon, Dec 13, 1999 at 05:31:17AM +0800 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 13, 1999 at 05:31:17AM +0800, Peter Wemm wrote: > Karl Denninger wrote: > > Hi folks, > > > > Just something to keep in mind.... > > > > I am trying to update from a Juneish -CURRENT to a current -CURRENT. > > > > I've run into two instances (the latest being the use of "colldef" in > > /usr/src/share/colldef) where older binaries are INCOMPATIBLE with the newer > > files they are processing, AND the "make buildworld" target uses the OLD > > binary in an attempt to read the NEW file. > > > > This blows up, obviously. > > This would appear to be another thing Marcel has broken.. > > colldef used to have special treatment, but it no longer has. > > peter@overcee[5:29am]~src-124> cvs up -p -r1.89 Makefile.inc1 | grep colldef > usr.bin/colldef \ > peter@overcee[5:29am]~src-125> grep colldef Makefile.inc1 > peter@overcee[5:29am]~src-126> > > Cheers, > -Peter Thanks Peter. This kind of thing is an issue that is very real; I've run into it before, and for a while I had trouble with this kind of thing when I was at MCS (usually the problem there was in the /usr/share/mk directory, but the same principle applies) Can I ask why the makefiles for the world don't build in this order? 1. Build the "basic" GNU kit necessary to compile things. 2. Build the LIBRARIES necessary to LINK things. 3. Rebuild the gnu kid using (2); you now have a self-consistent development system regardless of what you started with. 4. Build the world's binaries. 5. Process anything in /usr/share or other places that requires the use of those binaries, using the OBJECTS compiled in step (4). This way all you need to build the world is a compiler that kinda works. If include files have changed, or binaries that read files have changed, it doesn't matter and won't bite you. As long as you can get executable code in step (1) the build will complete AND the completed build will be up to date using the current headers and libraries. (I may be missing a step or two here but I think the question I'm asking is fairly clear) :-) Special-casing things like this looks rather evil to me; shouldn't we fix the general case instead? -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 14:12:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 5E06114D6A for ; Sun, 12 Dec 1999 14:12:11 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11xHDt-0001sl-00; Sun, 12 Dec 1999 22:12:10 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id XAA53401; Sun, 12 Dec 1999 23:12:06 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <38541DB6.17A97868@scc.nl> Date: Sun, 12 Dec 1999 23:12:06 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 To: Karl Denninger Cc: Peter Wemm , freebsd-hackers@FreeBSD.ORG Subject: Re: Reminder - changes to sources and such References: <19991212213117.94E341CA0@overcee.netplex.com.au> <19991212153853.A1509@Denninger.Net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Karl Denninger wrote: > > Can I ask why the makefiles for the world don't build in this order? > > 1. Build the "basic" GNU kit necessary to compile things. > 2. Build the LIBRARIES necessary to LINK things. > 3. Rebuild the gnu kid using (2); you now have a self-consistent > development system regardless of what you started with. This won't work in all cases, because the libraries don't always match the kernel. You need to build your tools against the includes and libraries that correspond to the machine your building on. > 4. Build the world's binaries. > 5. Process anything in /usr/share or other places that requires > the use of those binaries, using the OBJECTS compiled in step (4). This won't work if you're cross-building. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 15: 7: 2 1999 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 7398014DB2 for ; Sun, 12 Dec 1999 15:06:59 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA92085; Sun, 12 Dec 1999 15:06:56 -0800 (PST) Date: Sun, 12 Dec 1999 15:06:54 -0800 (PST) From: Julian Elischer To: mauzi@poli.hu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: silo overflows 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, 12 Dec 1999, Gergely EGERVARY wrote: > > what kind of disk to you have? and the chipset? (this may seem irrelevant > > but misconfigured DMA devices can block the cpu for long enough to cause > > this sort of thing in some cases). ALSO check systat -vmstat while this > > is happenning and check that you don't have a source of spurious > > interrupts. > > > > Julian > > intel 440bx chipset (abit-bh6 mainboard) > quantum cx13.0a ata4 disk > > actually i don't see any spurious interrupts :) (that had happenned to me) If you can get the disk working right it may even solve the silo problem. (it did for me) It turned out that the disk system was blocking the PCI bus during DMA Julian > > anyway... the raw disk read access speed (not fs!) is about 3MB/sec > this disk reads more than 10MB/secs with other OS'es... Do you have UDMA turned on? > > any ideas? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 15:20:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id C354415289 for ; Sun, 12 Dec 1999 15:20:12 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA29691; Sun, 12 Dec 1999 23:18:04 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA76937; Sun, 12 Dec 1999 23:49:39 +0100 (CET) (envelope-from wilko) Date: Sun, 12 Dec 1999 23:49:39 +0100 From: Wilko Bulte To: Charles Randall Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: timezone var vs timezone() function Message-ID: <19991212234939.C76834@yedi.iaf.nl> References: <64003B21ECCAD11185C500805F31EC0304D96BE6@houston.matchlogic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <64003B21ECCAD11185C500805F31EC0304D96BE6@houston.matchlogic.com>; from crandall@matchlogic.com on Sun, Dec 12, 1999 at 12:40:06PM -0700 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 12, 1999 at 12:40:06PM -0700, Charles Randall wrote: > On my FreeBSD 3.3R system, /usr/include/time.h includes a prototype for the > timezone() function. The timezone(3) manual page indicates that this > function is for compatibility purposes only and notes that the timezone() > function first appeared in AT&T Unix V7. > > Version 2 of the Single Unix Specification (www.opengroup.org) states that > time.h defines a global variable named timezone which indicates the > difference in seconds between the local timezone and UTC. It also notes that > this is, "Derived from Issue 1 of the SVID." I don't know what that means. SVID == System V Interface Definition. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl 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 Sun Dec 12 15:30:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id D1EA114E27 for ; Sun, 12 Dec 1999 15:30:17 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id EE2921CA0; Mon, 13 Dec 1999 07:30:13 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: mauzi@poli.hu Cc: Julian Elischer , freebsd-hackers@FreeBSD.ORG Subject: Re: silo overflows In-Reply-To: Message from Julian Elischer of "Sun, 12 Dec 1999 15:06:54 PST." Date: Mon, 13 Dec 1999 07:30:13 +0800 From: Peter Wemm Message-Id: <19991212233013.EE2921CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Julian Elischer wrote: > > > On Sun, 12 Dec 1999, Gergely EGERVARY wrote: > > > > what kind of disk to you have? and the chipset? (this may seem irrelevant > > > but misconfigured DMA devices can block the cpu for long enough to cause > > > this sort of thing in some cases). ALSO check systat -vmstat while this > > > is happenning and check that you don't have a source of spurious > > > interrupts. > > > > > > Julian > > > > intel 440bx chipset (abit-bh6 mainboard) > > quantum cx13.0a ata4 disk > > > > actually i don't see any spurious interrupts :) > > (that had happenned to me) > > If you can get the disk working right it may even solve the silo problem. > (it did for me) > It turned out that the disk system was blocking the PCI bus during DMA > > Julian For what it's worth, your problem is a wdc driver and/or a configuration problem. outback# dd if=/dev/ad0s1b of=/dev/null bs=256k count=512 512+0 records in 512+0 records out 134217728 bytes transferred in 6.868476 secs (19541122 bytes/sec) That's a 440bx and a quantum cx drive (slightly smaller, 10MB), but under -current. You have remembered to set flags 0xa0ffa0ff on the wdc controller right? Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 16:19:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles552.castles.com [208.214.165.116]) by hub.freebsd.org (Postfix) with ESMTP id 0CB1114E32; Sun, 12 Dec 1999 16:19:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA04346; Sun, 12 Dec 1999 16:21:15 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130021.QAA04346@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Juergen Lock Cc: Mike Smith , zzhang@cs.binghamton.edu, freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: loader hacks (was: Re: easyboot far into disk) In-reply-to: Your message of "Sun, 12 Dec 1999 15:59:32 +0100." <19991212155932.A1107@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Dec 1999 16:21:15 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I thought rootdev was fixed a long time back. If it's not, please tell > > > me and I'll fix it again. 8) > > > > Alright I finally got around testing this with a later kern.flp > > (3.3-R actually), and it still didn't work. ... > > Well i played with this once more yesterday and now i know what was > wrong: Unlike currdev, rootdev needs a `:' at the end... So either > I'm blind or the manpage needs fixing. :) The manpage is probably wrong. $rootdev is obsolete and will be removed for 4.x (if I remember). > I also actually started making that FAQ entry (yeah!), and then > wondered if you could also make an automagic boot floppy for a root > disk that is entirely invisible to the BIOS, like when its on a > BIOS-less (but otherwise supported) SCSI controller. I didn't find > a way to do it with the original (-stable) loader, but when i made > this patch, 4.x does this differently (better) by passing in a complete identifier. I need to update the online help and manpage for it. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 16:58:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from houston.matchlogic.com (houston.matchlogic.com [205.216.147.127]) by hub.freebsd.org (Postfix) with ESMTP id 7C4C214E36 for ; Sun, 12 Dec 1999 16:58:23 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2650.21) id ; Sun, 12 Dec 1999 17:58:11 -0700 Message-ID: <64003B21ECCAD11185C500805F31EC0304D96BE8@houston.matchlogic.com> From: Charles Randall To: freebsd-hackers@FreeBSD.ORG Subject: RE: timezone var vs timezone() function Date: Sun, 12 Dec 1999 17:58:02 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Wilko Bulte [mailto:wilko@yedi.iaf.nl] >Charles Randall wrote: >> ... It also notes that >> this is, "Derived from Issue 1 of the SVID." > >SVID == System V Interface Definition. Interesting, my Solaris 2.6 box defines timezone as the global variable (in accordance with the Single Unix Spec). See the tzset() manpage for their description. Charles To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 20:13:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tinker.exit.com (exit-gw.power.net [207.151.46.196]) by hub.freebsd.org (Postfix) with ESMTP id 7637F14DA5; Sun, 12 Dec 1999 20:13:06 -0800 (PST) (envelope-from frank@exit.com) Received: from realtime.exit.com (realtime.exit.com [206.223.0.5]) by tinker.exit.com (8.9.3/8.9.3) with ESMTP id UAA01172; Sun, 12 Dec 1999 20:13:01 -0800 (PST) (envelope-from frank@exit.com) Received: (from frank@localhost) by realtime.exit.com (8.9.3/8.9.3) id UAA06415; Sun, 12 Dec 1999 20:13:01 -0800 (PST) (envelope-from frank) Date: Sun, 12 Dec 1999 20:13:01 -0800 (PST) Message-Id: <199912130413.UAA06415@realtime.exit.com> To: FreeBSD-gnats-submit@freebsd.org Subject: vi screws up relative tag paths (with patch). From: frank@exit.com Cc: hackers@freebsd.org Reply-To: frank@exit.com X-send-pr-version: 3.2 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Submitter-Id: current-users >Originator: Frank Mayhar >Organization: Subversive Atheists -R- Us >Confidential: no >Synopsis: The name of the tagfile is left in the path. >Severity: serious >Priority: high >Category: bin >Release: FreeBSD 3.4-RC i386 >Class: sw-bug >Environment: 3.4-RC, 4.0-current, etc. >Description: The routine ctag_file(), when constructing the path to the file from a relative path in the tagfile, leaves the name of the tagfile in the path. >How-To-Repeat: Create a tagfile with relative entries, go to a different directory, and do a "vi -t ". >Fix: Index: ex_tag.c =================================================================== RCS file: /cvs/repos/src/contrib/nvi/ex/ex_tag.c,v retrieving revision 1.2 diff -c -r1.2 ex_tag.c *** ex_tag.c 1997/04/18 23:36:43 1.2 --- ex_tag.c 1999/06/25 20:59:29 *************** *** 1339,1349 **** stat(name, &sb) && (p = strrchr(tfp->name, '/')) != NULL) { *p = '\0'; len = snprintf(buf, sizeof(buf), "%s/%s", tfp->name, name); - *p = '/'; if (stat(buf, &sb) == 0) { *dirp = tfp->name; *dlenp = strlen(*dirp); } } } --- 1339,1349 ---- stat(name, &sb) && (p = strrchr(tfp->name, '/')) != NULL) { *p = '\0'; len = snprintf(buf, sizeof(buf), "%s/%s", tfp->name, name); if (stat(buf, &sb) == 0) { *dirp = tfp->name; *dlenp = strlen(*dirp); } + *p = '/'; } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 20:50:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mtiwmhc01.worldnet.att.net (mtiwmhc01.worldnet.att.net [204.127.131.36]) by hub.freebsd.org (Postfix) with ESMTP id EBDC414DB4; Sun, 12 Dec 1999 20:50:42 -0800 (PST) (envelope-from Thrumbar@Worldnet.att.net) Received: from 11.neworleans-01-02rs16rt.la.dial-access.att.net ([12.73.238.11]) by mtiwmhc01.worldnet.att.net (InterMail v03.02.07.07 118-134) with SMTP id <19991213045040.GYKN5516@11.neworleans-01-02rs16rt.la.dial-access.att.net>; Mon, 13 Dec 1999 04:50:40 +0000 From: Thrumbar Pathfinder To: freebsd-hackers@FreeBSD.ORG Cc: arch@freebsd.org Subject: Developer's Interface Guide for IA-64 Servers (DIG64) Adopter Date: Sun, 12 Dec 1999 22:47:37 -0600 Organization: OmniCorp Interstellar Message-ID: X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Attention, all FreeBSD, OpenBSD and NetBSD developers.. This is a chance we cannot ignore.. Please form up a development team with a central tram leader and get signed up for this offer. The Documentation personnel should sign up for the Contributors link to add BSD's voice in setting the guidelines for future BSD development for all three forms... Please read below.. (also, team leaders, send me a e-mail when you sign-up to keep me informed as to the process and to get an idea on how many teams there is involved) About the DIG64 Leading hardware and software vendors have formed an industry group to develop the DIG64 guidelines. These guidelines establish basic system building blocks, interfaces, and programming conventions for upcoming IA-64 based servers and their system-level software in order to define hardware and software compatibility and interoperability.=20 DIG64 is...=20 an industry-driven set of technical guidelines that define hardware, firmware and operating system's compatibility for IA-64 servers providing IT with systems built on common, stabilized interfaces that improve reliability and interoperability, lower qualification and support costs developed and backed by the key IA-64 OEMs, OSVs, and BIOS vendors who are contributing to its development and are building compliant products allowing the industry to accelerate the pace of IA-64 technology adoption=20 By defining common building blocks and interfaces and proactively addressing legacy issues, the DIG64 provides an array of benefits for both developers and IT organizations.=20 =46or developers, the DIG64: =20 Increases the efficiency of the design process, freeing developers to focus design resources of features that add unique value and differentiate their products in the marketplace. =20 Gives firmware and OS vendors a known set of interfaces to build to, enabling them to confidentially develop their products concurrently with the hardware and shrink time to markets. =20 Provides a technology migration roadmap that extends the planning horizon for developers and allows them to create designs with increased longevity.=20 =46or business users and Information Technology (IT) departments: =20 Standard interfaces and interoperable layers enhance the reliability and robustness of the resulting servers as well as lowering qualification costs. Since developers find it easier to build components that work together, customers can enjoy a greater choice of robust, innovative server solutions. Because the DIG64 addresses the migration of support-intensive, obsolete technologies to newer, more robust choices, IT departments can control or reduce the cost of server support.=20 DIG64 Defined =20 The DIG64 specification defines basic system building blocks, interfaces and programming conventions between IA-64 based servers and system-level software such as the operating system and device drivers. The specification covers:=20 Core system components such as the processor, chipset, memory, I/O bus, and server management hardware.=20 =20 Interfaces to peripheral devices for networking, communications and storage.=20 =20 Low-level firmware interfaces to the operating system for system configuration, boot and runtime services.=20 The guide does not create new standards and interfaces, but selects components and interfaces from already existing technologies. To ensure interoperability, the DIG64 also specifies implementation requirements for each specification or standard.=20 The DIG64 spells out a roadmap for eliminating obsolete technologies. Release 1.0, which is currently available , pertains to servers=20 based on the Intel=AE Itanium=99 processor. Subsequent versions will address future processors as they are developed. A three-level hierarchy of required, recommended and optional features enables vendors to choose how quickly they want to remove older technologies.=20 The DIG64 is operating-system independent, promoting cross-platform interoperability among servers running Windows 2000*, Linux and other UNIX* operating systems.=20 Join Other Industry Leaders Already Building Compatible IA-64 Server Solutions! =20 =20 There is still time to get involved by becoming a DIG64 Adopter member. To find out more about the advantages of becoming a DIG64 Adopter, take look at the DIG64 www site.... http://www.dig64.org/ To sign up as a Developer's Interface Guide for IA-64 Servers (DIG64) Adopter, complete all of the information at the link listed below and hit the submit button. You will then be able to download a "DIG64 Adopters Agreement". http://www.dig64.org/signup.htm By becoming a DIG64 Contributor, you will be able to provide technical input into the development of the DIG64 guidelines in addition to gaining access to the latest published draft. All input will be reviewed by the DIG64 Working Group for possible inclusion in the guideline. http://www.dig64.org/contributor.htm When you have formed your group please e-mail me so that I will know how many groups there are.. Please include a list of the individuals on the team and their position on said team as well as any contact information you are willing to provide... Thrumbar@Worldnet.att.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 20:53:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id DA95914D2D for ; Sun, 12 Dec 1999 20:53:52 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id FAA01395; Mon, 13 Dec 1999 05:54:05 +0100 (CET) (envelope-from assar) To: hackers@FreeBSD.ORG Subject: patches to always have getfh as syscall From: Assar Westerlund Date: 13 Dec 1999 05:54:05 +0100 Message-ID: <5l1z8r1lw2.fsf@assaris.sics.se> Lines: 5 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, in PR kern/15452 I have sent in patches to make getfh always be in the system call table. Details are also included in the PR. Any thoughts/comments/flames? /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 22: 0:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mobil.surnet.ru (mobil.surnet.ru [195.54.2.7]) by hub.freebsd.org (Postfix) with ESMTP id 261D214F06 for ; Sun, 12 Dec 1999 22:00:09 -0800 (PST) (envelope-from ilia@cgilh.chel.su) Received: (from uucgilh@localhost) by mobil.surnet.ru (8.9.1a/8.9.1) with UUCP id KAA12783 for hackers@FreeBSD.ORG; Mon, 13 Dec 1999 10:53:27 +0500 (ES) Received: (from uucp@localhost) by cgilh.chel.su (8.8.7/8.8.7) with UUCP id KAA01659 for hackers@FreeBSD.ORG; Mon, 13 Dec 1999 10:11:16 +0500 Received: from localhost (ilia@localhost) by jane.cgu.chel.su (8.9.3/8.9.2) with ESMTP id KAA00273 for ; Mon, 13 Dec 1999 10:06:22 +0500 (ES) (envelope-from ilia@cgilh.chel.su) X-Authentication-Warning: jane.cgu.chel.su: ilia owned process doing -bs Date: Mon, 13 Dec 1999 10:06:20 +0500 (ES) From: Ilia Chipitsine X-Sender: ilia@jane.cgu.chel.su To: hackers@FreeBSD.ORG Subject: technical info needed Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=koi8-r Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Dear hackers, How can I find how often is particular routine (say wdintr()) called. Is it called once an year or 500000 times a second ? Is there a way how can I determine it by myself ? Regards, (Наилучшие пожелания) Ilia Chipitsine (Илья Шипицин) -----BEGIN PGP SIGNATURE----- Version: 2.6.3ia Charset: noconv iQB1AwUBOFR+zuRxlWKN2EXhAQGiCgL/eVeEiTu9iEZPGWzIEyaucA4+PZq6anW4 g9jqKehLKG0apK613kl92uiuS5XnyddKrCoOya1blBe9ywJDR3Pl3Wrhr+fMBxUT DyQ35FPk5wIEWKbCw9vkt6NFvN36DY5t =k66v -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 22: 3:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 9D71B14E07 for ; Sun, 12 Dec 1999 22:03:25 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMO00NQ40TM36@mta4.rcsntx.swbell.net> for hackers@FreeBSD.ORG; Mon, 13 Dec 1999 00:03:23 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id AAA01305; Mon, 13 Dec 1999 00:05:57 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Mon, 13 Dec 1999 00:05:56 -0600 From: Chris Costello Subject: Re: technical info needed In-reply-to: To: Ilia Chipitsine Cc: hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991213000556.B868@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 13, 1999, Ilia Chipitsine wrote: > Is it called once an year or 500000 times a second ? > Is there a way how can I determine it by myself ? Add a statement like printf("somefunc() being called!\n"); to the top of the function you want to 'measure'. -- |Chris Costello |Nobody has ever, ever, EVER learned all of WordPerfect. `------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 22:35:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id C28CF14EE7 for ; Sun, 12 Dec 1999 22:35:15 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id WAA19989; Sun, 12 Dec 1999 22:34:44 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Sun, 12 Dec 1999 22:34:44 -0800 Date: Sun, 12 Dec 1999 22:34:44 -0800 (PST) From: Kip Macy To: Chris Costello Cc: Ilia Chipitsine , hackers@FreeBSD.ORG Subject: Re: technical info needed In-Reply-To: <19991213000556.B868@holly.calldei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: chris@calldei.com,ilia@cgilh.chel.su,hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems like using gprof would be a little bit more useful than potentially having something print to the screen 50k times. I guess printf would be fine if you only care if something is called a lot or not at all. -Kip On Mon, 13 Dec 1999, Chris Costello wrote: > On Mon, Dec 13, 1999, Ilia Chipitsine wrote: > > Is it called once an year or 500000 times a second ? > > Is there a way how can I determine it by myself ? > > Add a statement like > > printf("somefunc() being called!\n"); > > to the top of the function you want to 'measure'. > > -- > |Chris Costello > |Nobody has ever, ever, EVER learned all of WordPerfect. > `------------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 22:49:57 1999 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 D2B0114C8D for ; Sun, 12 Dec 1999 22:49:55 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id WAA99186; Sun, 12 Dec 1999 22:49:42 -0800 (PST) Date: Sun, 12 Dec 1999 22:49:41 -0800 (PST) From: Julian Elischer To: Chris Costello Cc: Ilia Chipitsine , hackers@FreeBSD.ORG Subject: Re: technical info needed In-Reply-To: <19991213000556.B868@holly.calldei.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 You can compile the kernel with -p -g and use the profiling. On Mon, 13 Dec 1999, Chris Costello wrote: > On Mon, Dec 13, 1999, Ilia Chipitsine wrote: > > Is it called once an year or 500000 times a second ? > > Is there a way how can I determine it by myself ? > > Add a statement like > > printf("somefunc() being called!\n"); > > to the top of the function you want to 'measure'. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 23:31:55 1999 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 07F8E14D07 for ; Sun, 12 Dec 1999 23:31:54 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id AAA16038; Mon, 13 Dec 1999 00:02:08 -0800 (PST) Date: Mon, 13 Dec 1999 00:02:08 -0800 (PST) From: Alfred Perlstein To: Julian Elischer Cc: Chris Costello , Ilia Chipitsine , hackers@FreeBSD.ORG Subject: Re: technical info needed 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, 12 Dec 1999, Julian Elischer wrote: > On Mon, 13 Dec 1999, Chris Costello wrote: > > > On Mon, Dec 13, 1999, Ilia Chipitsine wrote: > > > Is it called once an year or 500000 times a second ? > > > Is there a way how can I determine it by myself ? > > > > Add a statement like > > > > printf("somefunc() being called!\n"); > > > > to the top of the function you want to 'measure'. > > > > > > You can compile the kernel with -p -g and use the profiling. > Julian's way is the best however a quick 'n dirty would be just to create a sysctl node for your counter, useful if you only have a couple of things you want to track. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 23:38:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id CCE8814CB3 for ; Sun, 12 Dec 1999 23:38:53 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA28004; Mon, 13 Dec 1999 08:38:45 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912130738.IAA28004@freebsd.dk> Subject: Re: ATAPI tape support - how to format? In-Reply-To: <19991212140541.A57969@Denninger.Net> from Karl Denninger at "Dec 12, 1999 02:05:41 pm" To: karl@Denninger.Net (Karl Denninger) Date: Mon, 13 Dec 1999 08:38:44 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Karl Denninger wrote: > Hi folks, > > Well, I'm in for it now ;-) > > I'm going to have to start supporting ATAPI tape drives on FreeBSD for some > business associates - they're too cheap to go SCSI. > > Some of these (if not all) require formatting, right? This leads to the > obvious question: > > How do you format a tape for these drives under FreeBSD? :-) You dont, they "just works" out of the box. > Anything else I should know offhand other than "plug it in and use dump like > everything else"? Not really... -SЬren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 23:45:13 1999 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 4578714ED9 for ; Sun, 12 Dec 1999 23:45:08 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id XAA00188; Sun, 12 Dec 1999 23:44:58 -0800 (PST) Date: Sun, 12 Dec 1999 23:44:57 -0800 (PST) From: Julian Elischer To: Alfred Perlstein Cc: Chris Costello , Ilia Chipitsine , hackers@FreeBSD.ORG Subject: Re: technical info needed 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, 13 Dec 1999, Alfred Perlstein wrote: > > On Sun, 12 Dec 1999, Julian Elischer wrote: > > > On Mon, 13 Dec 1999, Chris Costello wrote: > > > > > On Mon, Dec 13, 1999, Ilia Chipitsine wrote: > > > > Is it called once an year or 500000 times a second ? > > > > Is there a way how can I determine it by myself ? > > > > > > Add a statement like > > > > > > printf("somefunc() being called!\n"); > > > > > > to the top of the function you want to 'measure'. > > > > > > > > > > You can compile the kernel with -p -g and use the profiling. Actually from memory you can compile just the files in question > > > > Julian's way is the best however a quick 'n dirty would be just > to create a sysctl node for your counter, useful if you only have > a couple of things you want to track. > > -Alfred > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 12 23:51:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw-out.comptel.com (mgw-out.comptel.com [195.237.145.101]) by hub.freebsd.org (Postfix) with ESMTP id 0D00A14FB5 for ; Sun, 12 Dec 1999 23:51:27 -0800 (PST) (envelope-from stefan.parvu@comptel.com) Received: from ctlfw1 ([195.237.145.97]) by mgw-out.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 13 Dec 1999 09:51:26 +0200 Received: from mgw-in.comptel.com ([192.102.20.150]) by ctlfw1.comptel.com; Mon, 13 Dec 1999 09:50:48 +0000 (EET) Received: from xf174 ([195.237.135.174]) by mgw-in.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 13 Dec 1999 09:51:24 +0200 Message-Id: <3.0.6.32.19991213094911.009290d0@miina.comptel.com> X-Sender: sparvu@miina.comptel.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 13 Dec 1999 09:49:11 -0800 To: freebsd-hackers@freebsd.org From: Stefan Parvu Subject: 2questions 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 have posted this email for question@freebsd.org but I didn't got any answer. I am running FreeBSD 3.3 Release on one laptop Toshiba and as XServer the Accelerated X 5.0.2. I am curious about one fact. Everytime when I exit from XServer I 've got: > pid 8971 (Xaccel): trap 12 with interrupts disabled What it is about ? Anyway on AccelX box it is said that FreeBSD OS is supported but only inside in box I have found that only 2.x are supported, according with members of FreeBSD project. Why ? Why not 3.x? On the other hand using FreeBSD 3.3 on another box (Compaq Desktop, AMD K6-333, 80MBRAM; 4GB, Voodoo3 PCI 2000) I ran top and the SIZE of XF86_SVGA goes to 54MB and RSIZE the same. Why ? Thanks, Stef To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 0: 2:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 7294814F3B for ; Mon, 13 Dec 1999 00:02:32 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA05895; Mon, 13 Dec 1999 00:05:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130805.AAA05895@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Stefan Parvu Cc: freebsd-hackers@freebsd.org Subject: Re: 2questions In-reply-to: Your message of "Mon, 13 Dec 1999 09:49:11 PST." <3.0.6.32.19991213094911.009290d0@miina.comptel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 00:05:04 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi all, > > I have posted this email for question@freebsd.org but I didn't got any answer. > > > I am running FreeBSD 3.3 Release on one laptop Toshiba and as XServer the > Accelerated X 5.0.2. I am curious about one fact. Everytime when I exit > from XServer I 've got: > > > pid 8971 (Xaccel): trap 12 with interrupts disabled > > What it is about ? The X server has turned off interrupts, and then generated a page fault (which may require interrupts to work before it can be completed). It indicates a programming error by the Xig folks. > Anyway on AccelX box it is said that FreeBSD OS is supported but only > inside in box I have found that only 2.x are supported, according with > members of FreeBSD project. Why ? Why not 3.x? This is a persistent misunderstanding with Xig. I haven't asked them recently what their side of the story is. As long as you have the 2.2 support libraries on your system, however, their server works fine under 2.2, 3.x and the upcoming 4.0 release. > On the other hand using FreeBSD 3.3 on another box (Compaq Desktop, AMD > K6-333, 80MBRAM; 4GB, Voodoo3 PCI 2000) I ran top and the SIZE of XF86_SVGA > goes to 54MB and RSIZE the same. Obviously, because it's using that much memory. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 0:12:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw-out.comptel.com (mgw-out.comptel.com [195.237.145.101]) by hub.freebsd.org (Postfix) with ESMTP id CAF2914D22; Mon, 13 Dec 1999 00:12:49 -0800 (PST) (envelope-from stefan.parvu@comptel.com) Received: from ctlfw1 ([195.237.145.97]) by mgw-out.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 13 Dec 1999 10:12:48 +0200 Received: from mgw-in.comptel.com ([192.102.20.150]) by ctlfw1.comptel.com; Mon, 13 Dec 1999 10:12:11 +0000 (EET) Received: from xf174 ([195.237.135.174]) by mgw-in.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Mon, 13 Dec 1999 10:12:47 +0200 Message-Id: <3.0.6.32.19991213101035.00954650@miina.comptel.com> X-Sender: sparvu@miina.comptel.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Mon, 13 Dec 1999 10:10:35 -0800 To: Mike Smith From: Stefan Parvu Subject: Re: 2questions Cc: freebsd-hackers@freebsd.org In-Reply-To: <199912130805.AAA05895@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG thanks for your answers. With some comments: 1. I've asked at XIG what it is about and they told me that this a problem of FreeBSD OS. Not about their server. Anyway I have asked also why they didn't test Accel 5.0.2 on FreeBSD 3.x ? With no success.No comments. I have also asked about 3D X server why they did not provide a version for FreeBSD and chambers@xig.com told me that there is no plan port for this yet :( 2. Well indeed, it is using that much memory but I have 80 MBRAM on my box and starting X, and a terminal (xterm) I have reported by top: Free 55M. So am I wrong with something how can a process to be in SIZE 54 and free mem to have 55M. stef At 12:05 AM 12/13/99 -0800, Mike Smith wrote: >> Hi all, >> >> I have posted this email for question@freebsd.org but I didn't got any answer. >> >> >> I am running FreeBSD 3.3 Release on one laptop Toshiba and as XServer the >> Accelerated X 5.0.2. I am curious about one fact. Everytime when I exit >> from XServer I 've got: >> >> > pid 8971 (Xaccel): trap 12 with interrupts disabled >> >> What it is about ? > >The X server has turned off interrupts, and then generated a page fault >(which may require interrupts to work before it can be completed). > >It indicates a programming error by the Xig folks. > >> Anyway on AccelX box it is said that FreeBSD OS is supported but only >> inside in box I have found that only 2.x are supported, according with >> members of FreeBSD project. Why ? Why not 3.x? > >This is a persistent misunderstanding with Xig. I haven't asked them >recently what their side of the story is. > >As long as you have the 2.2 support libraries on your system, however, >their server works fine under 2.2, 3.x and the upcoming 4.0 release. > >> On the other hand using FreeBSD 3.3 on another box (Compaq Desktop, AMD >> K6-333, 80MBRAM; 4GB, Voodoo3 PCI 2000) I ran top and the SIZE of XF86_SVGA >> goes to 54MB and RSIZE the same. > >Obviously, because it's using that much memory. > >-- >\\ Give a man a fish, and you feed him for a day. \\ Mike Smith >\\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org >\\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 0:25:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 8C56714D4B; Mon, 13 Dec 1999 00:25:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA06092; Mon, 13 Dec 1999 00:28:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130828.AAA06092@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Stefan Parvu Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: 2questions In-reply-to: Your message of "Mon, 13 Dec 1999 10:10:35 PST." <3.0.6.32.19991213101035.00954650@miina.comptel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 00:28:21 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > thanks for your answers. With some comments: > > 1. I've asked at XIG what it is about and they told me that this a problem > of FreeBSD OS. Not about their server. Xig have not been providing accurate answers to many questions asked of them about FreeBSD recently. It would appear that they have again been misleading here. Can you tell me exactly who you spoke to at Xig? The history of this issue is that back around the FreeBSD 3.0 release, it was suggested to Xig that they might want to stick with an a.out rather than ELF-format server while we and our customer base transitioned to ELF. They've stuck with the a.out format ever since, and I suspect that cognitive dissonance has set in - the person you spoke to probably has no idea why they don't test on 3.x. > Anyway I have asked also why they > didn't test Accel 5.0.2 on FreeBSD 3.x ? With no success.No comments. > I have also asked about 3D X server why they did not provide a version for > FreeBSD and chambers@xig.com told me that there is no plan port for this > yet :( There are a couple of issues with the 3D server, one of them is the lack of suitable AGP control interfaces. (This is tentatively on my todo list) > 2. Well indeed, it is using that much memory but I have 80 MBRAM on my box and > starting X, and a terminal (xterm) I have reported by top: Free 55M. So am > I wrong with something how can a process to be in SIZE 54 and free mem to > have 55M. Explaining this is probably beyond the scope of anything I can write this evening, and I suspect that the explanation wouldn't do you a lot of good. I hope you'll be satisified with two points: - the size of the X server includes the size of video RAM mapped from the card. - numbers lie. Be happy that it works. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 0:37: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id C88E414D76 for ; Mon, 13 Dec 1999 00:37:00 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA06175; Mon, 13 Dec 1999 00:39:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130839.AAA06175@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Vladimir N. Silyaev" Cc: hackers@freebsd.org Subject: Re: Multiple instances of the same character device In-reply-to: Your message of "Sat, 11 Dec 1999 17:33:37 EST." <19991211173336.A635@jupiter.delta.ny.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 00:39:42 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The question is very simple. Is it possible to open the same character > pseudo device, for example /dev/foo0, simultaneously from other programs, and > to work with this instances independently? Not in the fashion that I believe you're trying to do, no. > I'm asked as the developer of a driver with such requirements, so please > don't complain about such technique. I think I'm going to complain anyway; this is an _extremely_ lame way to do things, and it breaks many assumptions about how files are meant to work. In your case, however, you can probably steal the 'emuldata' field in the proc structure to store a pointer to your per-instance data. At some stage, the Linux emulator will want to use this as well, and it will need to provide an API for multiple emulator plugins to use. By then I hope that we'll have convinced the VMware folks to do things properly, or have our own binary version... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 1:26:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 2729E15005 for ; Mon, 13 Dec 1999 01:26:53 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=scones.sup.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 11xRkp-0000xp-00; Mon, 13 Dec 1999 09:26:51 +0000 Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by scones.sup.scc.nl (8.9.3/8.9.3) with ESMTP id KAA89775; Mon, 13 Dec 1999 10:26:51 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <3854BBDB.38571966@scc.nl> Date: Mon, 13 Dec 1999 10:26:51 +0100 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.5 i386) X-Accept-Language: en MIME-Version: 1.0 Cc: Karl Denninger , freebsd-hackers@freebsd.org Subject: Re: Reminder - changes to sources and such References: <19991212213117.94E341CA0@overcee.netplex.com.au> 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 wrote: > > Karl Denninger wrote: > > Hi folks, > > > > Just something to keep in mind.... > > > > I am trying to update from a Juneish -CURRENT to a current -CURRENT. > > > > I've run into two instances (the latest being the use of "colldef" in > > /usr/src/share/colldef) where older binaries are INCOMPATIBLE with the newer > > files they are processing, AND the "make buildworld" target uses the OLD > > binary in an attempt to read the NEW file. > > > > This blows up, obviously. > > This would appear to be another thing Marcel has broken.. > > colldef used to have special treatment, but it no longer has. Fixed thanks. I actually had it in my -stable to -current tests, but somehow got lost while committing it. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@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 Dec 13 2: 5:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 2E6D414D9A for ; Mon, 13 Dec 1999 02:05:08 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id CAA07871; Mon, 13 Dec 1999 02:04:57 -0800 (PST) To: mjacob@feral.com Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: SCSI tape minor device numbers In-reply-to: Your message of Sun, 12 Dec 1999 00:23:22 -0800. Date: Mon, 13 Dec 1999 02:04:57 -0800 Message-ID: <7869.945079497@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , you wrot e: >> Can anyone interpret this for me: >> >> HARDWARE FAILURE asc:0,4 >> >> What does it mean? >> >> It this just the numeric code for ``Buy another tape drive''? >> :-) > >Yes. Thank you. P.S. Power cycling _just_ the tape drive seems to have cured it for now. Gee! If only hardware could be as reliable as software! Oops! NEVERMIND! :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 4: 2:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bootp.sls.usu.edu (bootp.sls.usu.edu [129.123.82.251]) by hub.freebsd.org (Postfix) with ESMTP id 00ECD14A27; Mon, 13 Dec 1999 04:02:20 -0800 (PST) (envelope-from kurto@bootp.sls.usu.edu) Received: (from kurto@localhost) by bootp.sls.usu.edu (8.9.3/8.9.3) id FAA59691; Mon, 13 Dec 1999 05:02:17 -0700 (MST) (envelope-from kurto) Date: Mon, 13 Dec 1999 05:02:17 -0700 (MST) From: Kurt Olsen Message-Id: <199912131202.FAA59691@bootp.sls.usu.edu> To: msmith@FreeBSD.ORG, stefan.parvu@comptel.com Subject: Re: 2questions Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199912130828.AAA06092@mass.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > - the size of the X server includes the size of video RAM mapped from > the card. The 3dfx cards also map significantly more memory than there is RAM on the card itself. Mostly for control registers and stuff. It might be as much as 32 MB on top of the actual RAM available. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 5:30:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eth0-gw.poli.hu (eth0-gw.poli.hu [195.199.8.27]) by hub.freebsd.org (Postfix) with ESMTP id 1E58B150DA for ; Mon, 13 Dec 1999 05:30:54 -0800 (PST) (envelope-from mauzi@aquarius.poli.hu) Received: from dial-6.poli.hu ([195.199.8.22] helo=aquarius.poli.hu) by eth0-gw.poli.hu with esmtp (Exim 3.11 #1 (Debian)) id 11xVYp-0005Nu-00 for ; Mon, 13 Dec 1999 14:30:43 +0100 Received: from mauzi (helo=localhost) by aquarius.poli.hu with local-esmtp (Exim 3.03 #1) id 11xUtf-00004s-00 for freebsd-hackers@FreeBSD.ORG; Mon, 13 Dec 1999 13:48:11 +0100 Date: Mon, 13 Dec 1999 13:48:10 +0100 (CET) From: Gergely EGERVARY Reply-To: mauzi@poli.hu To: freebsd-hackers@FreeBSD.ORG Subject: Re: silo overflows 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 > Do you have UDMA turned on? is ``flags 0xa0ffa0ff'' enough or should I set something else too? -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 7:26:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eth0-gw.poli.hu (eth0-gw.poli.hu [195.199.8.27]) by hub.freebsd.org (Postfix) with ESMTP id CFD6715289 for ; Mon, 13 Dec 1999 07:26:07 -0800 (PST) (envelope-from mauzi@aquarius.poli.hu) Received: from dial-6.poli.hu ([195.199.8.22] helo=aquarius.poli.hu) by eth0-gw.poli.hu with esmtp (Exim 3.11 #1 (Debian)) id 11xXMO-0005RP-00 for ; Mon, 13 Dec 1999 16:26:00 +0100 Received: from mauzi (helo=localhost) by aquarius.poli.hu with local-esmtp (Exim 3.03 #1) id 11xXO8-00005D-00 for freebsd-hackers@freebsd.org; Mon, 13 Dec 1999 16:27:48 +0100 Date: Mon, 13 Dec 1999 16:27:48 +0100 (CET) From: Gergely EGERVARY Reply-To: mauzi@poli.hu To: freebsd-hackers@freebsd.org Subject: umount -f causes page fault in kernel? 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, mount /cdrom cd /cdrom umount -f /cdrom cd .. will cause 100% reproduceable kernel panic (page fault) I know forced umount is dangerous, but soo ... =P it's 3.3-RELEASE -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 7:56:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tetron02.tetronsoftware.com (ftp.tetronsoftware.com [208.236.46.106]) by hub.freebsd.org (Postfix) with ESMTP id C8CB914C32 for ; Mon, 13 Dec 1999 07:56:28 -0800 (PST) (envelope-from zeus@tetronsoftware.com) Received: from development (development.tetronsoftware.com [10.0.0.3]) by tetron02.tetronsoftware.com (8.9.3/8.9.3) with SMTP id JAA02283 for ; Mon, 13 Dec 1999 09:58:45 -0600 (CST) (envelope-from zeus@tetronsoftware.com) Reply-To: From: "Gene Harris" To: Subject: Xlib.h Question Date: Mon, 13 Dec 1999 09:56:12 -0600 Message-ID: <51F9B228ED26D311A17700A0C9982664010AA6@tetboss.tetronsoftware.com> X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed a problem with includes in Xlib.h on my FreeBSD 3.3-Stable box: The following includes incorrectly specify an X11 subdirectory: #include /* applications should not depend on these two headers being included! */ #include #include If I edit out the "X11/" subdir, everything compiles correctly. Is this a known bug, or have I placed Xlib.h in the wrong subdir? (It is found in /usr/X11R6/include/X11 on my machine.) Gene Harris http://www.tetronsoftware.com Home of TeamAccess http://www.teamaccess.com DOS Drools, FreeBSD Rules! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 8: 3:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id BF0D614FB8 for ; Mon, 13 Dec 1999 08:03:42 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11xXwV-0008W7-00; Mon, 13 Dec 1999 18:03:19 +0200 From: Sheldon Hearn To: zeus@tetronsoftware.com Cc: freebsd-hackers@freebsd.org Subject: Re: Xlib.h Question In-reply-to: Your message of "Mon, 13 Dec 1999 09:56:12 CST." <51F9B228ED26D311A17700A0C9982664010AA6@tetboss.tetronsoftware.com> Date: Mon, 13 Dec 1999 18:03:19 +0200 Message-ID: <32742.945100999@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Dec 1999 09:56:12 CST, "Gene Harris" wrote: > #include > #include > > If I edit out the "X11/" subdir, everything compiles correctly. Is > this a known bug, or have I placed Xlib.h in the wrong subdir? (It is > found in /usr/X11R6/include/X11 on my machine.) You're probably compiling with -I/usr/X11R6/include/X11 instead of -I/usr/X11R6/include 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 Dec 13 9:31:42 1999 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 0D24B154B0 for ; Mon, 13 Dec 1999 09:31:36 -0800 (PST) (envelope-from imp@harmony.village.org) 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 KAA68241; Mon, 13 Dec 1999 10:31:32 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA44607; Mon, 13 Dec 1999 10:31:31 -0700 (MST) Message-Id: <199912131731.KAA44607@harmony.village.org> To: Soren Schmidt Subject: Re: ATAPI tape support - how to format? Cc: karl@Denninger.Net (Karl Denninger), freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 13 Dec 1999 08:38:44 +0100." <199912130738.IAA28004@freebsd.dk> References: <199912130738.IAA28004@freebsd.dk> Date: Mon, 13 Dec 1999 10:31:31 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912130738.IAA28004@freebsd.dk> Soren Schmidt writes: : > Anything else I should know offhand other than "plug it in and use dump like : > everything else"? : : Not really... Actually yes. There is one thing you should know. The ata tape drives tend to be more flakey than their scsi brotheren. This isn't to say a specific drive won't be reliable, but in general I've found that they are fussier and require more care and feeding than my old Exebyte drives (Which should tell the old users of the 8200 and 8500 something here). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 9:37:58 1999 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 24EC614C11 for ; Mon, 13 Dec 1999 09:37:56 -0800 (PST) (envelope-from imp@harmony.village.org) 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 KAA68272; Mon, 13 Dec 1999 10:37:54 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA44681; Mon, 13 Dec 1999 10:37:54 -0700 (MST) Message-Id: <199912131737.KAA44681@harmony.village.org> To: zeus@tetronsoftware.com Subject: Re: Xlib.h Question Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 13 Dec 1999 09:56:12 CST." <51F9B228ED26D311A17700A0C9982664010AA6@tetboss.tetronsoftware.com> References: <51F9B228ED26D311A17700A0C9982664010AA6@tetboss.tetronsoftware.com> Date: Mon, 13 Dec 1999 10:37:54 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <51F9B228ED26D311A17700A0C9982664010AA6@tetboss.tetronsoftware.com> "Gene Harris" writes: : The following includes incorrectly specify an X11 subdirectory: : : #include No. You are wrong. That include is 100% correct. It is the documented way to include X.h, and has been since at least X11R2 when I started doing X programming, and likely dates back to X11R1 (but I doubt it dates to X10R4, which is the first version of X I used, but didn't program in). : If I edit out the "X11/" subdir, everything compiles correctly. Is : this a known bug, or have I placed Xlib.h in the wrong subdir? (It is : found in /usr/X11R6/include/X11 on my machine.) The bug here is that you likely did a -I/usr/X11R6/include/X11 where you should have done a -I/usr/X11R6/include. This is a bug in your code, not in the X code. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 10:50:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 5821115059 for ; Mon, 13 Dec 1999 10:50:38 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id SAA25850; Mon, 13 Dec 1999 18:43:57 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00923; Mon, 13 Dec 1999 19:25:46 +0100 (CET) (envelope-from wilko) Date: Mon, 13 Dec 1999 19:25:45 +0100 From: Wilko Bulte To: Warner Losh Cc: Soren Schmidt , Karl Denninger , freebsd-hackers@FreeBSD.ORG Subject: Re: ATAPI tape support - how to format? Message-ID: <19991213192545.D636@yedi.iaf.nl> References: <199912130738.IAA28004@freebsd.dk> <199912131731.KAA44607@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912131731.KAA44607@harmony.village.org>; from imp@village.org on Mon, Dec 13, 1999 at 10:31:31AM -0700 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 13, 1999 at 10:31:31AM -0700, Warner Losh wrote: > In message <199912130738.IAA28004@freebsd.dk> Soren Schmidt writes: > : > Anything else I should know offhand other than "plug it in and use dump like > : > everything else"? > : > : Not really... > > Actually yes. There is one thing you should know. The ata tape > drives tend to be more flakey than their scsi brotheren. This isn't > to say a specific drive won't be reliable, but in general I've found > that they are fussier and require more care and feeding than my old > Exebyte drives (Which should tell the old users of the 8200 and 8500 > something here). It does, yes. I never had any desire to go for IDE tapes but I have now filed the idea as insane ;-) -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl 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 Mon Dec 13 10:55:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 4A04314CA4 for ; Mon, 13 Dec 1999 10:55:50 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id MAA00574; Mon, 13 Dec 1999 12:55:20 -0600 (CST) Message-ID: <19991213125520.A567@Denninger.Net> Date: Mon, 13 Dec 1999 12:55:20 -0600 From: Karl Denninger To: Wilko Bulte , Warner Losh Cc: Soren Schmidt , freebsd-hackers@FreeBSD.ORG Subject: Re: ATAPI tape support - how to format? References: <199912130738.IAA28004@freebsd.dk> <199912131731.KAA44607@harmony.village.org> <19991213192545.D636@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19991213192545.D636@yedi.iaf.nl>; from Wilko Bulte on Mon, Dec 13, 1999 at 07:25:45PM +0100 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 13, 1999 at 07:25:45PM +0100, Wilko Bulte wrote: > On Mon, Dec 13, 1999 at 10:31:31AM -0700, Warner Losh wrote: > > In message <199912130738.IAA28004@freebsd.dk> Soren Schmidt writes: > > : > Anything else I should know offhand other than "plug it in and use dump like > > : > everything else"? > > : > > : Not really... > > > > Actually yes. There is one thing you should know. The ata tape > > drives tend to be more flakey than their scsi brotheren. This isn't > > to say a specific drive won't be reliable, but in general I've found > > that they are fussier and require more care and feeding than my old > > Exebyte drives (Which should tell the old users of the 8200 and 8500 > > something here). > > It does, yes. I never had any desire to go for IDE tapes but I have now > filed the idea as insane ;-) Well I never have had any desire to do so EITHER, but the problem is that one project I'm being sucked into is replacing NT-style machines with FreeBSD/Samba ones (quite a nice niche application for small offices, natch) and the problem is those folks are VERY cost-conscious. As in the $100 price difference for a DAT drive plus the extra couple hundred for the SCSI controller is too much. Yeah, I know IDE disks suck too. They don't care, and in this application the performance difference won't be noticable either. Thus, the question. BTW, I have older HP DAT drives (4 & 8gb models) that have several YEARS of active use on them, and other than using a cleaning tape when the front panel "clean me" light flashes I've NEVER had ANY problem with them. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 10:56:29 1999 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 2FAB314E97 for ; Mon, 13 Dec 1999 10:56:23 -0800 (PST) (envelope-from imp@harmony.village.org) 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 LAA68558; Mon, 13 Dec 1999 11:56:21 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA45348; Mon, 13 Dec 1999 11:56:21 -0700 (MST) Message-Id: <199912131856.LAA45348@harmony.village.org> To: Wilko Bulte Subject: Re: ATAPI tape support - how to format? Cc: Soren Schmidt , Karl Denninger , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 13 Dec 1999 19:25:45 +0100." <19991213192545.D636@yedi.iaf.nl> References: <19991213192545.D636@yedi.iaf.nl> <199912130738.IAA28004@freebsd.dk> <199912131731.KAA44607@harmony.village.org> Date: Mon, 13 Dec 1999 11:56:20 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991213192545.D636@yedi.iaf.nl> Wilko Bulte writes: : It does, yes. I never had any desire to go for IDE tapes but I have now : filed the idea as insane ;-) Well, come to think of the 8500 experiences I've had, it isn't as bad as that. The 8200 was a pain, but usable and useful. That's the level of pain the IDE tape drives I have put me through... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 13:14:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id C6996151E0; Mon, 13 Dec 1999 13:14:08 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id WAA20095; Mon, 13 Dec 1999 22:11:13 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id WAA12495; Mon, 13 Dec 1999 22:09:41 +0100 (CET) From: Juergen Lock Date: Mon, 13 Dec 1999 22:09:41 +0100 To: Mike Smith Cc: Mike Smith , zzhang@cs.binghamton.edu, freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: loader hacks (was: Re: easyboot far into disk) Message-ID: <19991213220941.C8035@saturn.kn-bremen.de> References: <19991212155932.A1107@saturn.kn-bremen.de> <199912130021.QAA04346@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <199912130021.QAA04346@mass.cdrom.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 12, 1999 at 04:21:15PM -0800, Mike Smith wrote: > > > > I thought rootdev was fixed a long time back. If it's not, please tell > > > > me and I'll fix it again. 8) > > > > > > Alright I finally got around testing this with a later kern.flp > > > (3.3-R actually), and it still didn't work. ... > > > > Well i played with this once more yesterday and now i know what was > > wrong: Unlike currdev, rootdev needs a `:' at the end... So either > > I'm blind or the manpage needs fixing. :) > > The manpage is probably wrong. $rootdev is obsolete and will be removed > for 4.x (if I remember). > > > I also actually started making that FAQ entry (yeah!), and then > > wondered if you could also make an automagic boot floppy for a root > > disk that is entirely invisible to the BIOS, like when its on a > > BIOS-less (but otherwise supported) SCSI controller. I didn't find > > a way to do it with the original (-stable) loader, but when i made > > this patch, > > 4.x does this differently (better) by passing in a complete identifier. > I need to update the online help and manpage for it. Ah, but that does need changes in the kernel right? The way i did it should even work with an old 2.x kernel, you just have to put it on the floppy... Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 14:52:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from camxch01.veritas.com (camxch01.cam.veritas.com [166.98.49.3]) by hub.freebsd.org (Postfix) with ESMTP id 9801314D27; Mon, 13 Dec 1999 14:52:07 -0800 (PST) (envelope-from quan.guo@veritas.com) Received: by CAMXCH01 with Internet Mail Service (5.5.2448.0) id ; Mon, 13 Dec 1999 17:50:56 -0500 Message-ID: From: Quan Guo To: "'freebsd-questions@FreeBSD.org'" Cc: "'freebsd-hackers@FreeBSD.org'" Subject: FW: popen in RPC svc code Date: Mon, 13 Dec 1999 17:50:56 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, > I wrote a standard popen program inside rpc svc interface code . > The fgets could not get anything it should get. > Do you know what kind of problem I am facing? > Thank very much for your time. > > -Quan > Software Engineer > Veritas Software To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 15:12:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id C99AE14C16 for ; Mon, 13 Dec 1999 15:10:39 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id SAA00352 for freebsd-hackers@freebsd.org; Mon, 13 Dec 1999 18:10:21 -0500 (EST) (envelope-from steve) Date: Mon, 13 Dec 1999 18:10:21 -0500 (EST) From: Steve Ames Message-Id: <199912132310.SAA00352@virtual-voodoo.com> To: freebsd-hackers@freebsd.org Subject: ATA w/ today's -CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hrm... no question that the ATA driver is better today, but its still not reporting DMA on my Quantum bigfoot drive (which should support DMA: http://www.quantum.com/products/archive/bigfoot_cy/bigfoot_cy_features.htm) The Maxtor is pretty old (But its been current since 3.0 :) but may still have some DMA support? (ftp://ftp.maxtor.com/pub/ide/71626ap.txt) What am I missing? Here's the bootup info: -Steve Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #1: Mon Dec 13 17:50:31 EST 1999 steve@virtual-voodoo.com:/source/src/sys/compile/VV-ATA Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 233866223 Hz CPU: AMD-K6(tm) 3D processor (233.87-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 Features=0x8001bf AMD Features=0x80000800 real memory = 134217728 (131072K bytes) avail memory = 127287296 (124304K bytes) Preloaded elf kernel "kernel" at 0xc02a1000. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 ata-pci0: irq 0 at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 vga-pci0: irq 0 at device 11.0 on pci0 ed0: irq 11 at device 15.0 on pci0 ed0: address 52:54:00:dc:08:ca, type NE2000 (16 bit) vga-pci1: irq 0 at device 20.0 on pci0 fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ed1 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 ed1: address 00:40:05:24:1e:c4, type NE2000 (16 bit) pca0 at port 0x40 on isa0 pca0: PC speaker audio driver IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, logging disabled ad0: ATA-0 disk at ata0 as master ad0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, PIO ad1: ATA-0 disk at ata0 as slave ad1: 4134MB (8467200 sectors), 8960 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, PIO acd0: CDROM drive at ata1 as master acd0: read 1033KB/s (1033KB/s), 256KB buffer, PIO acd0: supported read types: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ata_command: timeout waiting for interrupt Mounting root from ufs:/dev/ad0s1a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 15:36:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from satsuma.mail.easynet.net (satsuma.mail.easynet.net [195.40.1.44]) by hub.freebsd.org (Postfix) with ESMTP id 6FA6B15967 for ; Mon, 13 Dec 1999 15:35:56 -0800 (PST) (envelope-from andrew@dogma.freebsd-uk.eu.org) Received: from cream.org (boothman.easynet.co.uk [194.154.100.117]) by satsuma.mail.easynet.net (Postfix) with ESMTP id BF4CD7B004 for ; Mon, 13 Dec 1999 23:35:46 +0000 (GMT) Content-Length: 626 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 13 Dec 1999 23:37:23 -0000 (GMT) From: Andrew Boothman To: hackers@freebsd.org Subject: DMI Support Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! What's the current situation with DMI support on FreeBSD? A search of the mail archives reveal that we have support for finding the code in the BIOS but not a lot else. Is that still accurate? Do we have any plans to add more support? This is the kind of thing that I would LOVE to help out on myself, but my knowledge of FreeBSD isn't detailed enough, and my knowledge of OS programming is even worse! :) So while I'm still learning, is anyone else working on this? Many thanks! --- Andrew Boothman FreeBSD UK User Group http://ukug.uk.FreeBSD.org/~andrew/ http://ukug.uk.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 15:57:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sdcc10.ucsd.edu (sdcc10.ucsd.edu [132.239.50.10]) by hub.freebsd.org (Postfix) with ESMTP id 106ED14D8A for ; Mon, 13 Dec 1999 15:57:37 -0800 (PST) (envelope-from tshansen@sdcc10.ucsd.edu) Received: from localhost (tshansen@localhost) by sdcc10.ucsd.edu (8.9.3/8.9.3) with ESMTP id PAA22512; Mon, 13 Dec 1999 15:57:35 -0800 (PST) Date: Mon, 13 Dec 1999 15:57:35 -0800 (PST) From: Todd Hansen Reply-To: tshansen@ucsd.edu To: freebsd-hackers@freebsd.org Cc: bpowell@ucsd.edu Subject: an lm79 device driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Powell and I recently finished implementing a FreeBSD device driver for the lm79 system monitor by national semiconductor. We are interested in submitting it for inclusion in the FreeBSD kernel. However, we are also very interested in getting constructive feedback on our design. You can access the driver at: http://millenium.atcg.com/~taco/lm79.html. Below is a listing of features and areas we would like some ideas on in order to pursue further. BTW, if this device driver ever gets into FreeBSD we are interested in further developing it and supporting it as well. Features: 1) can read lm79 sensor values into a struct by simply opening the device file. 2) can read lm79 sensor values with ioctl call 3) can set lm79 thresholds and check them, using a simple user program (provided) you can even halt the system or log a message on violation. What we need help/leads on: 1) how to get a call back function to occur at a specific time (useful for select's 1.5 second delay as well as to periodically check thresholds on lm79 without a user program). -Todd Hansen & Brian Powell University of California, San Diego To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 17:17:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 94E38152C5; Mon, 13 Dec 1999 17:17:28 -0800 (PST) (envelope-from vsilyaev@mindspring.com) Received: from mindspring.com (user-2ivebg7.dialup.mindspring.com [165.247.46.7]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id UAA02634; Mon, 13 Dec 1999 20:17:18 -0500 (EST) Received: (from vsilyaev@localhost) by mindspring.com (8.9.3/8.9.3) id UAA00374; Mon, 13 Dec 1999 20:16:01 -0500 (EST) (envelope-from vsilyaev) Date: Mon, 13 Dec 1999 20:16:00 -0500 From: "Vladimir N. Silyaev" To: Mike Smith Cc: "Vladimir N. Silyaev" , hackers@freebsd.org Subject: Re: Multiple instances of the same character device Message-ID: <19991213201600.A253@jupiter.delta.ny.us> References: <19991211173336.A635@jupiter.delta.ny.us> <199912130839.AAA06175@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912130839.AAA06175@mass.cdrom.com>; from msmith@freebsd.org on Mon, Dec 13, 1999 at 12:39:42AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 13, 1999 at 12:39:42AM -0800, Mike Smith wrote: > > > > The question is very simple. Is it possible to open the same character > > pseudo device, for example /dev/foo0, simultaneously from other programs, and > > to work with this instances independently? > > Not in the fashion that I believe you're trying to do, no. > > > I'm asked as the developer of a driver with such requirements, so please > > don't complain about such technique. > > I think I'm going to complain anyway; this is an _extremely_ lame way to > do things, and it breaks many assumptions about how files are meant to > work. > > In your case, however, you can probably steal the 'emuldata' field in the > proc structure to store a pointer to your per-instance data. At some > stage, the Linux emulator will want to use this as well, and it will need > to provide an API for multiple emulator plugins to use. Oh no, I think it's a bad idea to store something in the proc structure, because program want two different devices with such semantics, and it some time 'forked'. And in common, it's a very dirty hack, and it's doesn't remove the 'last close' problem. Probably I'll be try to do something like 'rotated' symlink, or intercept linux open syscall and substitute devices like /dev/foo0a, /dev/foo0b, until don't open one. > > By then I hope that we'll have convinced the VMware folks to do things > properly, or have our own binary version... Ya-ya, I hope too. -- Vladimir Silyaev To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 17:37: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 4DC1B151D3 for ; Mon, 13 Dec 1999 17:37:02 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02033; Mon, 13 Dec 1999 17:38:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912140138.RAA02033@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Boothman Cc: hackers@freebsd.org Subject: Re: DMI Support In-reply-to: Your message of "Mon, 13 Dec 1999 23:37:23 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 17:38:04 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's the current situation with DMI support on FreeBSD? Basically, there is none. I spent some time looking at it, and finally concluded that there wasn't much to be gained (for me) from it, and moved on. From a functional standpoint DMI doesn't actually offer us very much; ACPI is a closer match to our needs. > Is that still accurate? Do we have any plans to add more support? There are no active plans, no. > This is the kind of thing that I would LOVE to help out on myself, but my > knowledge of FreeBSD isn't detailed enough, and my knowledge of OS programming > is even worse! :) It'd be a good project to cut your teeth on, especially integrating the DMI information into a backend suitable for use with an SNMP server. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 17:44: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fep02-svc.mail.telepac.pt (fep02-svc.mail.telepac.pt [194.65.5.201]) by hub.freebsd.org (Postfix) with ESMTP id AB035152CD for ; Mon, 13 Dec 1999 17:43:52 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: from manecao.tafkap.priv ([212.55.187.66]) by fep02-svc.mail.telepac.pt (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991214013942.UYJU10720.fep02-svc@manecao.tafkap.priv> for ; Tue, 14 Dec 1999 01:39:42 +0000 Content-Length: 767 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 14 Dec 1999 01:43:27 -0000 (GMT) From: Joao Pedras To: freebsd-hackers@freebsd.org Subject: bsd signals Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all I am new to C so I need a little help on this one. I am in need for something that calls an app and leaves it running. What is so special about this is that this app is called by php3 scripts. A very good soul handed these lines of code which work perfectly well in FreeBSD : #include #include #include int main(int argc, char *argv[]) { int pid; pid=fork(); if (pid!=0) { pid=setsid(); close(STDOUT_FILENO); close(STDIN_FILENO); close(STDERR_FILENO); execl(argv[1],argv[2],0); } return 0; } The problem is : how to make this work on linux systems ?? This works perfectly on my FreeBSD systems, but a single linux box needs this functionality. Any help would appreciated. Thanks Joao To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 19:34:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shidahara1.planet.sci.kobe-u.ac.jp (shidahara1.planet.sci.kobe-u.ac.jp [133.30.50.200]) by hub.freebsd.org (Postfix) with ESMTP id 3B01B15304 for ; Mon, 13 Dec 1999 19:34:01 -0800 (PST) (envelope-from takawata@shidahara1.planet.sci.kobe-u.ac.jp) Received: from shidahara1.planet.sci.kobe-u.ac.jp (localhost [127.0.0.1]) by shidahara1.planet.sci.kobe-u.ac.jp (8.8.8+2.7Wbeta7/8.8.8) with ESMTP id MAA02585; Tue, 14 Dec 1999 12:32:46 +0900 (JST) Message-Id: <199912140332.MAA02585@shidahara1.planet.sci.kobe-u.ac.jp> To: tshansen@ucsd.edu Cc: hackers@freebsd.org Subject: Re: an lm79 device driver In-reply-to: Your message of "Mon, 13 Dec 1999 15:57:35 PST" References: Date: Tue, 14 Dec 1999 12:32:45 +0900 From: Takanori Watanabe Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Todd Han sen wrote: >Brian Powell and I recently finished implementing a FreeBSD device driver >for the lm79 system monitor by national semiconductor. We are interested >in submitting it for inclusion in the FreeBSD kernel. However, we are also >very interested in getting constructive feedback on our design. You can >access the driver at: http://millenium.atcg.com/~taco/lm79.html. Below is >a listing of features and areas we would like some ideas on in order to >pursue further. BTW, if this device driver ever gets into FreeBSD we are >interested in further developing it and supporting it as well. I checked it.And it seems to be written in before-2.2 manner.And ISA only device. I also wrote a simple driver that supports LM78/79 ,W83781 ,AS88127F as a device of smbus.For ISA device, I wrote a device driver that pretend SMbus.I sent PR about the ISA driver part at i386/14891. Will you have a look my code at ? Takanori Watanabe. Public Key Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 22:11:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id A296214ED0 for ; Mon, 13 Dec 1999 22:11:35 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id QAA01791; Tue, 14 Dec 1999 16:41:26 +1030 (CST) (envelope-from newton) Date: Tue, 14 Dec 1999 16:41:26 +1030 From: Mark Newton To: mauzi@poli.hu Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: umount -f causes page fault in kernel? Message-ID: <19991214164126.C1587@internode.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 13, 1999 at 04:27:48PM +0100, Gergely EGERVARY wrote: [ ... ] "Doctor, it hurts when I do this:" > mount /cdrom > cd /cdrom > umount -f /cdrom > cd .. > will cause 100% reproduceable kernel panic (page fault) "So don't do that then!" > I know forced umount is dangerous, but soo ... =P It's described as "dangerous" precisely because it causes a kernel panic. Why on earth would you want/need to do that anyway? - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 13 23:36:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 29A791514B for ; Mon, 13 Dec 1999 23:36:35 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA68617; Tue, 14 Dec 1999 08:36:22 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912140736.IAA68617@freebsd.dk> Subject: Re: ATA w/ today's -CURRENT In-Reply-To: <199912132310.SAA00352@virtual-voodoo.com> from Steve Ames at "Dec 13, 1999 06:10:21 pm" To: steve@virtual-voodoo.com (Steve Ames) Date: Tue, 14 Dec 1999 08:36:21 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Steve Ames wrote: > > Hrm... no question that the ATA driver is better today, but its still > not reporting DMA on my Quantum bigfoot drive (which should support DMA: > http://www.quantum.com/products/archive/bigfoot_cy/bigfoot_cy_features.htm) > > The Maxtor is pretty old (But its been current since 3.0 :) but may > still have some DMA support? (ftp://ftp.maxtor.com/pub/ide/71626ap.txt) > > What am I missing? Drives that report their capabilities right :) > ad0: ATA-0 disk at ata0 as master > ad0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, PIO > ad1: ATA-0 disk at ata0 as slave > ad1: 4134MB (8467200 sectors), 8960 cyls, 15 heads, 63 S/T, 512 B/S > ad1: 16 secs/int, 1 depth queue, PIO Both reports "dont care" fields in the ata conformance field thereby being set as ATA-0 disks. Since I've put in test to only enable WDMA2 on at least ATA-2 disks and only enable UDMA2 on at least ATA-3 disks, well your disks are not even tried. You can change that in ata-disk.c by commenting out the test for this, they look like: "ad_version(ap->versmajor) >= 2". I've put them in recently to try to avoid runniing DMA on known problematic HW, but they will also reject some good ones regrettably... -SЬren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 14 3: 5:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penguin.wise.edt.ericsson.se (penguin-ext.wise.edt.ericsson.se [194.237.142.110]) by hub.freebsd.org (Postfix) with ESMTP id F29DD14C05 for ; Tue, 14 Dec 1999 03:05:55 -0800 (PST) (envelope-from mattias.pettersson@era.ericsson.se) Received: from era-t.ericsson.se (koff.ericsson.se [147.214.173.137]) by penguin.wise.edt.ericsson.se (8.9.3/8.9.3/WIREfire-1.5) with SMTP id MAA24582 for ; Tue, 14 Dec 1999 12:05:53 +0100 (MET) Received: from era.ericsson.se by era-t.ericsson.se (SMI-8.6/LME-DOM-2.2.5(ERA/T)) id MAA27729; Tue, 14 Dec 1999 12:05:52 +0100 Message-ID: <38562482.61968B74@era.ericsson.se> Date: Tue, 14 Dec 1999 12:05:38 +0100 From: Mattias Pettersson Organization: Ericsson Radio Systems AB X-Mailer: Mozilla 4.08 [en] (Win95; I) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Route delete Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hope for someone to point me at how to easiest do a user space "route delete -host xxxx"-similar thing in the kernel of FreeBSD3. The problem is the reference count. Only calling rtrequest(RTM_DELETE, ...) will only free the route if refcount = 0. I added a loop to call all pfctlinput()s with REDIRECT to clear all cached routes in the upper layer protocols. This works fine, it clears all tcp and udp sockets. Still though, what do I do regarding the cached routes of ICMP and the likes? This isn't taken care of by my attempts. Still, "route delete" fixes this. What functions to call? Do I need to send something over the routing socket? /Mattias Pettersson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 14 7: 9: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 64E7014A06 for ; Tue, 14 Dec 1999 07:09:00 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from daniel.sobral (root@p19-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.148]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id AAA24442 for ; Wed, 15 Dec 1999 00:08:41 +0900 (JST) Received: (from dcs@localhost) by daniel.sobral (8.9.1/8.9.3) id AAA02382 for freebsd-hackers@freebsd.org; Wed, 15 Dec 1999 00:05:54 +0900 (JST) (envelope-from dcs) From: "Daniel C. Sobral" Message-Id: <199912141505.AAA02382@daniel.sobral> Subject: rc.conf/loader.conf manipulation library To: freebsd-hackers@freebsd.org Date: Wed, 15 Dec 1999 00:05:50 +0900 (JST) Disclaimer: Klaatu Barada Nikto! 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 I have been working on a library to manipulate files in the general format of rc.conf and loader.conf. This library will see use in sysinstall, enabling it to change any variable in these files, and removing that horrible "append changes" behavior. :-) As a bonus, I plan to at a "install splash screen" option to sysinstall. This library can also be used as back-end by any other programs wishing to manipulate these files, or any other files in the same format. Anyone wishing to review it, please get it at: http://www.freebsd.org/~dcs/libconf19991215.tar.gz It has two example programs: chconf and prog. The first one is a cli to changing these files, and the second one is an example of a number of ways to iterate through the data read from these configuration files. A man page is in the works. Meanwhile, any suggestions feedback is welcome. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org If you don't have time to do it right, where are you going to find the time to do it over? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 14 7:58:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id D67DC1515A for ; Tue, 14 Dec 1999 07:58:47 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id JAA33923; Tue, 14 Dec 1999 09:58:32 -0600 (CST) (envelope-from dan) Date: Tue, 14 Dec 1999 09:58:32 -0600 From: Dan Nelson To: Mark Newton Cc: mauzi@poli.hu, freebsd-hackers@FreeBSD.ORG Subject: Re: umount -f causes page fault in kernel? Message-ID: <19991214095832.A33777@dan.emsphone.com> References: <19991214164126.C1587@internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991214164126.C1587@internode.com.au>; from "Mark Newton" on Tue Dec 14 16:41:26 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Dec 14), Mark Newton said: > On Mon, Dec 13, 1999 at 04:27:48PM +0100, Gergely EGERVARY wrote: > > mount /cdrom > > cd /cdrom > > umount -f /cdrom > > cd .. > > will cause 100% reproduceable kernel panic (page fault) > > "So don't do that then!" > > > I know forced umount is dangerous, but soo ... =P > > It's described as "dangerous" precisely because it causes a kernel > panic. Well, it actually *shouldn't* cause a kernel panic. I know I've forcibly unmounted filesystems with no problems. Gergely: could you rebuild your kernel with debugging, create a kernel crashdump, and post a stack traceback of the panic? Instructions are at http://www.freebsd.org/handbook/kerneldebug.html . -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 14 11: 1:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sdcc10.ucsd.edu (sdcc10.ucsd.edu [132.239.50.10]) by hub.freebsd.org (Postfix) with ESMTP id CB52C152B3 for ; Tue, 14 Dec 1999 11:01:23 -0800 (PST) (envelope-from tshansen@sdcc10.ucsd.edu) Received: from localhost (tshansen@localhost) by sdcc10.ucsd.edu (8.9.3/8.9.3) with ESMTP id LAA25491; Tue, 14 Dec 1999 11:01:11 -0800 (PST) Date: Tue, 14 Dec 1999 11:01:11 -0800 (PST) From: Todd Hansen Reply-To: tshansen@ucsd.edu To: Takanori Watanabe Cc: hackers@freebsd.org, bpowell@ucsd.edu Subject: Re: an lm79 device driver In-Reply-To: <199912140332.MAA02585@shidahara1.planet.sci.kobe-u.ac.jp> 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 didn't realize the architecture had changed after 2.2. We were working off of examples in the source code. Anyway, where can I find information on the new device driver archtecture? Thanks for checking it out. I will definitly check out your code after finals week. -todd On Tue, 14 Dec 1999, Takanori Watanabe wrote: > In message , Todd Han > sen wrote: > >Brian Powell and I recently finished implementing a FreeBSD device driver > >for the lm79 system monitor by national semiconductor. We are interested > >in submitting it for inclusion in the FreeBSD kernel. However, we are also > >very interested in getting constructive feedback on our design. You can > >access the driver at: http://millenium.atcg.com/~taco/lm79.html. Below is > >a listing of features and areas we would like some ideas on in order to > >pursue further. BTW, if this device driver ever gets into FreeBSD we are > >interested in further developing it and supporting it as well. > > I checked it.And it seems to be written in before-2.2 manner.And ISA only > device. > > I also wrote a simple driver that supports LM78/79 ,W83781 ,AS88127F as > a device of smbus.For ISA device, I wrote a device driver that pretend > SMbus.I sent PR about the ISA driver part at i386/14891. > > Will you have a look my code at > > ? > > Takanori Watanabe. > > Public Key > Key fingerprint = 2C 51 E2 78 2C E1 C5 2D 0F F1 20 A3 11 3A 62 2A > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 14 11:25:12 1999 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 470A8152C8 for ; Tue, 14 Dec 1999 11:25:06 -0800 (PST) (envelope-from imp@harmony.village.org) 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 MAA72930; Tue, 14 Dec 1999 12:24:59 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA54773; Tue, 14 Dec 1999 12:24:59 -0700 (MST) Message-Id: <199912141924.MAA54773@harmony.village.org> To: tshansen@ucsd.edu Subject: Re: an lm79 device driver Cc: Takanori Watanabe , hackers@FreeBSD.ORG, bpowell@ucsd.edu In-reply-to: Your message of "Tue, 14 Dec 1999 11:01:11 PST." References: Date: Tue, 14 Dec 1999 12:24:58 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Todd Hansen writes: : I didn't realize the architecture had changed after 2.2. We were working : off of examples in the source code. Anyway, where can I find information : on the new device driver archtecture? Thanks for checking it out. I will : definitly check out your code after finals week. /usr/src/sys :-) There are man pages, but none that have the whole gestalt of the new system. Work is underway to produce such a gestalt document. The ep driver (sys/dev/ep) isn't bad too look at, nor is the aha driver, but there are likely more edge cases in the latter than the former that need to be cleaned up. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 14 16:59:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 8971B1527A for ; Tue, 14 Dec 1999 16:59:52 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id TAA03712; Tue, 14 Dec 1999 19:59:59 -0500 (EST) (envelope-from steve) Date: Tue, 14 Dec 1999 19:59:59 -0500 From: Steve Ames To: Soren Schmidt Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: ATA w/ today's -CURRENT Message-ID: <19991214195959.A3700@virtual-voodoo.com> References: <199912132310.SAA00352@virtual-voodoo.com> <199912140736.IAA68617@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199912140736.IAA68617@freebsd.dk>; from Soren Schmidt on Tue, Dec 14, 1999 at 08:36:21AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What am I missing? > > Drives that report their capabilities right :) > > ad0: ATA-0 disk at ata0 as master > > ad0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 1 depth queue, PIO > > ad1: ATA-0 disk at ata0 as slave > > ad1: 4134MB (8467200 sectors), 8960 cyls, 15 heads, 63 S/T, 512 B/S > > ad1: 16 secs/int, 1 depth queue, PIO > > Both reports "dont care" fields in the ata conformance field > thereby being set as ATA-0 disks. Since I've put in test > to only enable WDMA2 on at least ATA-2 disks and only enable > UDMA2 on at least ATA-3 disks, well your disks are not even > tried. You can change that in ata-disk.c by commenting out the > test for this, they look like: "ad_version(ap->versmajor) >= 2". This makes sense. I'll try giving it a tweak. > I've put them in recently to try to avoid runniing DMA on known > problematic HW, but they will also reject some good ones > regrettably... Hrm... any chance of making that a config option? People should be allowed to hurt themselves if they want :) Or maybe in LINT point to the correct spot in the source so that people can hurt themselves from there? -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 14 17:59:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from screech.weirdnoise.com (209-128-78-198.bayarea.net [209.128.78.198]) by hub.freebsd.org (Postfix) with ESMTP id B8B6115395 for ; Tue, 14 Dec 1999 17:59:16 -0800 (PST) (envelope-from edhall@screech.weirdnoise.com) Received: from screech.weirdnoise.com (localhost [127.0.0.1]) by screech.weirdnoise.com (8.9.3/8.8.7) with ESMTP id RAA15697; Tue, 14 Dec 1999 17:59:39 -0800 Message-Id: <199912150159.RAA15697@screech.weirdnoise.com> X-Mailer: exmh version 2.0.2 To: freebsd-hackers@FreeBSD.ORG Cc: edhall@screech.weirdnoise.com Subject: VM Scan Rate: Speed Kills on 3.3 Mime-Version: 1.0 Content-Type: multipart/mixed ; boundary="==_Exmh_1410642600" Date: Tue, 14 Dec 1999 17:59:39 -0800 From: Ed Hall Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multipart MIME message. --==_Exmh_1410642600 Content-Type: text/plain; charset=us-ascii Under certain circumstances the VM scan rate can spike into the millions/sec (as reported by vmstat) followed quickly by a system lockup (an endless loop in vm_pageout()), suggesting that the page queue has been tied in a loop. This effect was observed in a program ported from Solaris that updated a large file by mmap()'ing small parts of it. Although using read()/write() eliminates the problem (and with a sizable increase in performance as well), there may be other triggers for this bug. (A side comment: although using mmap() for file updates in FreeBSD applications seems to perform quite poorly when compared to read()/write(), this is not the case on some other systems, such as Solaris. Also, there may be cases where the shared memory semantics of mmap() are important to an application such that conversion to read()/write() is not possible.) I've attached a small test program that provokes the same behavior as my (old) application did. It accepts two arguments: a file size in MB, and an update size in KB. Make the first twice the size of physical memory and the second a small multiple of the page size (see example run in second attachment). In my case there was .5GB of physical memory on an N440BX (500MHz P-III) server w/IDE disk. -Ed Hall Technical Yahoo, Yahoo! Inc. --==_Exmh_1410642600 Content-Type: text/plain ; name="vmtest1.txt"; charset=us-ascii Content-Description: vmtest1.txt Content-Disposition: attachment; filename="vmtest1.txt" A sample stack trace: siointr1(c617e000,e8e33f44,c01c1057,0,80000010) at siointr1+0xb9 siointr(0) at siointr+0x12 Xfastintr4(3425000,80000000,c0131c28,8000,c0140f94) at Xfastintr4+0x17 vm_pageout_scan(80000000,c0208404,e8e33fb0,c0131c5a,e8e2bdff) at vm_pageout_scan+0x173 vm_pageout(e8e2bdff,c01ecf38,c0208404,c0278ff4,c01c0e2a) at vm_pageout+0x226 kproc_start(c0208404) at kproc_start+0x32 fork_trampoline(0,0,c040c000,0,c040c008) at fork_trampoline+0x3a Here is the standard output leading up to the tragedy; the perfect interleave of program output with "vmstat 1" output is pure luck: % vmstat 1 & . . . % ./a.out 2048 8 00000000 1 0 0 2100992416600 17886 0 0 0 19 0 4 241 17929 30 47 47 7 00010000 1 0 0 2100992343144 19333 0 0 0 0 0 0 236 19357 24 57 43 0 00020000 1 0 0 2100992272096 19419 0 0 0 0 0 4 242 19443 25 59 41 0 00030000 1 0 0 2100992203096 19661 0 0 0 0 0 0 236 19685 23 55 45 0 00040000 1 0 0 2100992135896 19661 0 0 0 0 0 0 241 19685 25 65 35 0 00050000 1 0 0 2100992 70704 19871 0 0 0 0 0 0 237 19895 24 64 36 0 00060000 1 0 0 3840 18296 18339 0 0 0 0 121030 0 237 18364 25 52 48 0 00070000 1 2 1 2101332 1492 5963 0 3 89 36 1001341 84 341 5987 129 15 75 10 and then dialtone. --==_Exmh_1410642600 Content-Type: text/plain; name="vmtest1.c"; charset=us-ascii Content-Description: vmtest1.c Content-Disposition: attachment; filename="vmtest1.c" #include #include #include #include #include #include int main(int argc, char **argv) { off_t filesize; size_t maplen; off_t randoffset; void *maploc; void *memorybuf; int fd; int i; int r; if (argc != 3) fprintf(stderr, "usage: %s filesize-MB mapsize-KB\n", *argv), exit(1); filesize = (off_t)1048576 * (off_t)atoi(argv[1]); maplen = (size_t)1024 * (size_t)atoi(argv[2]); if ((memorybuf = calloc(maplen, 1)) == NULL) perror("calloc() failed"), exit(1); if ((fd = open("test.gomi", O_RDWR|O_CREAT, 0666)) < 0) perror("can't create/open test.gomi"), exit(1); if (ftruncate(fd, filesize) < 0) perror("ftruncate failed"), exit(1); for (i = 0;; i++) { r = random() % (int)((filesize / (off_t)maplen) - 1); randoffset = (off_t)(r * maplen); if (randoffset + maplen > filesize) continue; if ((maploc = mmap(NULL, maplen, PROT_READ|PROT_WRITE, MAP_SHARED, fd, randoffset)) == MAP_FAILED) perror("mmap failed"), exit(1); memcpy(memorybuf, maploc, maplen); ((int *)memorybuf)[0]++; memcpy(maploc, memorybuf, maplen); if (munmap(maploc, maplen) < 0) perror("munmap failed"), exit(1); if (i%10000 == 0) fprintf(stderr, "%08d\n", i); } } --==_Exmh_1410642600-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 14 18:59:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id BAF7714E9D for ; Tue, 14 Dec 1999 18:59:47 -0800 (PST) (envelope-from kris@hiwaay.net) Received: from hiwaay.net (tnt6-216-180-5-9.dialup.HiWAAY.net [216.180.5.9]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id UAA15779 for ; Tue, 14 Dec 1999 20:59:41 -0600 (CST) Message-ID: <3857041C.146D0F35@hiwaay.net> Date: Tue, 14 Dec 1999 20:59:40 -0600 From: Kris Kirby Organization: Non Illegitemus Carborundum. X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Using make to allow parallel operations? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am attempting to start a program on a impromptu cluster, one program per machine. I am using make, and seq from the cluster-it package in the ports collection. My problem is that make doesn't start the jobs parallel, it just goes from one to the other. In my project root, I have the following makefile: SUBDIR = 1 2 3 4 5 6 7 8 9 .include In my SUBDIRs, I have these makefiles: PROG = seq ls -la PAF = ${.CURDIR} all: @for prog in ${OBJ} ; do \ ${PROG} ${PAF}/$$prog ; \ done OBJ = Track01.wav \ Track02.wav I am thinking that the for loop is not the way to run things parallel, but I see no other option. This is a batch MP3 encode, not a compling run, but the concepts are similar (programs and thier arguments). I appreciate any time taken and hints offered. [Why -hackers? Well, I don't have a copy of the CVS log, so I can't go bother whoever built the makefiles in /usr/src ;-)] -- Kris Kirby, KE4AHR ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 14 20:45:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AD0271540F for ; Tue, 14 Dec 1999 20:45:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA25923; Tue, 14 Dec 1999 20:45:13 -0800 (PST) (envelope-from dillon) Date: Tue, 14 Dec 1999 20:45:13 -0800 (PST) From: Matthew Dillon Message-Id: <199912150445.UAA25923@apollo.backplane.com> To: Ed Hall Cc: freebsd-hackers@FreeBSD.ORG, edhall@screech.weirdnoise.com Subject: Re: VM Scan Rate: Speed Kills on 3.3 References: <199912150159.RAA15697@screech.weirdnoise.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Under certain circumstances the VM scan rate can spike into the millions/sec :(as reported by vmstat) followed quickly by a system lockup (an endless :loop in vm_pageout()), suggesting that the page queue has been tied in a :loop. This effect was observed in a program ported from Solaris that :updated a large file by mmap()'ing small parts of it. Although using :read()/write() eliminates the problem (and with a sizable increase in :performance as well), there may be other triggers for this bug. : :(A side comment: although using mmap() for file updates in FreeBSD :applications seems to perform quite poorly when compared to read()/write(), :this is not the case on some other systems, such as Solaris. Also, :there may be cases where the shared memory semantics of mmap() are :important to an application such that conversion to read()/write() is :not possible.) : :I've attached a small test program that provokes the same behavior as :... This is a known problem which has not been fixed in 3.x. The problem has been mostly fixed in 4.x. The problem is that in a low-memory situation the page daemon winds up being the only system process left that is capable of cleaning (flushing) dirty pages to disk. However, the page daemon cannot flush pages associated with files whos vnodes are locked. So the lockup occurs when some other process (even another system process) holds the vnode locked and the system runs out of memory. The page daemon scans through tonnes of pages but can't flush any of them due to the locked vnode. There is no simple solution for 3.x. It may be possible to place a workaround in vm_fault to block early on a low memory condition before memory becomes critical but it would be a pretty nasty hack. The below hack (for 3.x) is not something I would commit to the tree because it is too drastic, but try it and see if it solves your problem. -Matt Index: vm_fault.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_fault.c,v retrieving revision 1.93.2.4 diff -u -r1.93.2.4 vm_fault.c --- vm_fault.c 1999/08/29 16:33:30 1.93.2.4 +++ vm_fault.c 1999/12/15 04:43:57 @@ -191,6 +191,10 @@ RetryFault:; fs.map = map; + while ((fault_type & VM_PROT_WRITE) && (cnt.v_free_count + cnt.v_cache_count) < cnt.v_free_min) { + VM_WAIT; + } + /* * Find the backing store object and offset into it to begin the * search. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 14 23: 9:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C587214FF7 for ; Tue, 14 Dec 1999 23:09:50 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA08058; Wed, 15 Dec 1999 08:09:46 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912150709.IAA08058@freebsd.dk> Subject: Re: ATA w/ today's -CURRENT In-Reply-To: <19991214195959.A3700@virtual-voodoo.com> from Steve Ames at "Dec 14, 1999 07:59:59 pm" To: steve@virtual-voodoo.com (Steve Ames) Date: Wed, 15 Dec 1999 08:09:46 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Steve Ames wrote: > > > I've put them in recently to try to avoid runniing DMA on known > > problematic HW, but they will also reject some good ones > > regrettably... > > Hrm... any chance of making that a config option? People should be > allowed to hurt themselves if they want :) Or maybe in LINT point > to the correct spot in the source so that people can hurt themselves > from there? I'm working on a fix for this that can be used without recompiling... -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 Dec 15 2:23: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id BCFF3155CC for ; Wed, 15 Dec 1999 02:22:54 -0800 (PST) (envelope-from freebsd-hackers@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id LAA22518 for hackers@FreeBSD.org; Wed, 15 Dec 1999 11:06:49 +0100 (CET) (envelope-from freebsd-hackers@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for hackers@FreeBSD.org (hackers@FreeBSD.org) To: hackers@FreeBSD.org Date: Wed, 15 Dec 1999 11:06:45 +0100 From: Marcel Moolenaar Message-ID: <38576835.2BEC9E67@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: <3857041C.146D0F35@hiwaay.net> Subject: Re: Using make to allow parallel operations? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kirby wrote: > In my project root, I have the following makefile: > SUBDIR = 1 2 3 4 5 6 7 8 9 > .include Assuming you have an `encode' target that you want to run in parallel; you need something like: .for entry in ${SUBDIR} ${entry}.encode__D: .PHONY @if test -d ${.CURDIR}/${entry}.${MACHINE_ARCH}; then \ ${ECHODIR} "===> ${DIRPRFX}${entry}.${MACHINE_ARCH}"; \ edir=${entry}.${MACHINE_ARCH}; \ cd ${.CURDIR}/$${edir}; \ else \ ${ECHODIR} "===> ${DIRPRFX}${entry}"; \ edir=${entry}; \ cd ${.CURDIR}/$${edir}; \ fi; \ ${MAKE} encode DIRPRFX=${DIRPRFX}$${edir}/ .endfor par-encode: ${SUBDIR:S/$/.encode__D/} (Taken from src/Makefile.inc1) By having all the subdirs as dependencies for the par-encode target, make will start doing them in parallel. > @for prog in ${OBJ} ; do \ > ${PROG} ${PAF}/$$prog ; \ > done > > I am thinking that the for loop is not the way to run things parallel, > but I see no other option. This is a batch MP3 encode, not a compling > run, but the concepts are similar (programs and thier arguments). Correct. The for-loop is expanded before any targets are made. That's why the normal use of SUBDIR is non-parallel; it's used in a for-loop. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 3:29:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id C7B0015236 for ; Wed, 15 Dec 1999 03:29:45 -0800 (PST) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.1a/8.9.1) id TAA29972 for freebsd-hackers@freebsd.org; Wed, 15 Dec 1999 19:29:41 +0800 (WST) From: Michael Kennett Message-Id: <199912151129.TAA29972@laurasia.com.au> Subject: pccard disruptions : how did it go? To: freebsd-hackers@freebsd.org Date: Wed, 15 Dec 1999 19:29:40 +0800 (WST) X-Mailer: ELM [version 2.4ME+ PL32 (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 Hello All, I've just scoured the archives, and found a thread from late October 1999 titled: Massive pccard disruptions to continue So, have these disruptions continued? And what is the current status with pccard support in the kernel? I've noticed that a few files still contain the PCCARD_MODULE macro - in particular, the dev/pccard/if_xe.c Xircom driver. I'm interested in getting the if_xe.c driver to work under -current (12-Dec sources). I'd be interested in any ideas on how to convert the old if_xe.c driver to the 'newbus' code. (I'm not familiar with either the old PCCARD_MODULE, or the newbus code.) Regards, Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 8:55:38 1999 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 5196A15338 for ; Wed, 15 Dec 1999 08:55:35 -0800 (PST) (envelope-from imp@harmony.village.org) 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 JAA76794; Wed, 15 Dec 1999 09:55:29 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA61300; Wed, 15 Dec 1999 09:55:27 -0700 (MST) Message-Id: <199912151655.JAA61300@harmony.village.org> To: Michael Kennett Subject: Re: pccard disruptions : how did it go? Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 15 Dec 1999 19:29:40 +0800." <199912151129.TAA29972@laurasia.com.au> References: <199912151129.TAA29972@laurasia.com.au> Date: Wed, 15 Dec 1999 09:55:27 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912151129.TAA29972@laurasia.com.au> Michael Kennett writes: : I've just scoured the archives, and found a thread from late October 1999 : titled: : Massive pccard disruptions to continue : : So, have these disruptions continued? And what is the current status with : pccard support in the kernel? The new pccard code is still being worked on. However, the old pccard code mostly works again, modulo a couple of if_detach issues that I'm trying to work through. : I've noticed that a few files still contain the PCCARD_MODULE macro : - in particular, the dev/pccard/if_xe.c Xircom driver. I'm : interested in getting the if_xe.c driver to work under -current : (12-Dec sources). I'd be interested in any ideas on how to convert : the old if_xe.c driver to the 'newbus' code. (I'm not familiar with : either the old PCCARD_MODULE, or the newbus code.) The if_xe and if_fe drivers no longer work for pccard. You may wish to investigate how the ep and ed drivers were converted. There is one issue with the if_xe driver, namely it needs to access the CIS of the card to determine which kind of card it is and that will need some work in -current to get working again... I can provide support for this effort, but I'm not sure that I have time to do this effort. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 9:17:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 02B2B154CF for ; Wed, 15 Dec 1999 09:17:43 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id JAA17392; Wed, 15 Dec 1999 09:17:34 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id JAA16812; Wed, 15 Dec 1999 09:17:34 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA06645; Wed, 15 Dec 99 09:17:31 PST Message-Id: <3857CD74.5B20CCD3@softweyr.com> Date: Wed, 15 Dec 1999 10:18:44 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Kris Kirby Cc: hackers@FreeBSD.ORG Subject: Re: Using make to allow parallel operations? References: <3857041C.146D0F35@hiwaay.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kirby wrote: > > I am attempting to start a program on a impromptu cluster, one program > per machine. I am using make, and seq from the cluster-it package in the > ports collection. My problem is that make doesn't start the jobs > parallel, it just goes from one to the other. Have you explored pmake, in ports/devel? I use it at work on a large farm of Sun Ultra servers and workstations and it works quite well there. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 9:45:38 1999 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 5D5C7154F9 for ; Wed, 15 Dec 1999 09:45:27 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (ibmpc.whistle.com [207.76.205.196]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA83241; Wed, 15 Dec 1999 09:45:26 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.3/8.9.1) id JAA22374; Wed, 15 Dec 1999 09:23:49 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199912151723.JAA22374@whistle.com> Subject: Re: pccard disruptions : how did it go? In-Reply-To: <199912151655.JAA61300@harmony.village.org> from Warner Losh at "Dec 15, 1999 09:55:27 am" To: Warner Losh Date: Wed, 15 Dec 1999 09:23:49 -0800 (PST) Cc: Michael Kennett , 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 Warner Losh writes: | In message <199912151129.TAA29972@laurasia.com.au> Michael Kennett writes: | : I've just scoured the archives, and found a thread from late October 1999 | : titled: | : Massive pccard disruptions to continue | : | : So, have these disruptions continued? And what is the current status with | : pccard support in the kernel? | | The new pccard code is still being worked on. | | However, the old pccard code mostly works again, modulo a couple of | if_detach issues that I'm trying to work through. | | : I've noticed that a few files still contain the PCCARD_MODULE macro | : - in particular, the dev/pccard/if_xe.c Xircom driver. I'm | : interested in getting the if_xe.c driver to work under -current | : (12-Dec sources). I'd be interested in any ideas on how to convert | : the old if_xe.c driver to the 'newbus' code. (I'm not familiar with | : either the old PCCARD_MODULE, or the newbus code.) | | The if_xe and if_fe drivers no longer work for pccard. You may wish | to investigate how the ep and ed drivers were converted. There is one | issue with the if_xe driver, namely it needs to access the CIS of the | card to determine which kind of card it is and that will need some | work in -current to get working again... I will try to take a look at the Xircom driver and try to newbus it after I finish some work on the Arionet driver (It's annoying have to deal with non robust dongles and then I don't have to carry a modem & 2 ethernet adapters). However, Linksys has an interesting card .. unfortunately you can't stick 2 of them in at the same time. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 13:32:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from urquell.pilsnet.sunet.se (urquell.pilsnet.sunet.se [192.36.125.77]) by hub.freebsd.org (Postfix) with ESMTP id 657B114BC6 for ; Wed, 15 Dec 1999 13:32:37 -0800 (PST) (envelope-from bd@urquell.pilsnet.sunet.se) Received: (from bd@localhost) by urquell.pilsnet.sunet.se (8.9.1/8.9.1) id WAA23759; Wed, 15 Dec 1999 22:32:35 +0100 (CET) (envelope-from bd) To: freebsd-hackers@freebsd.org Subject: Re: PCI DMA lockups in 3.2 (3.3 maybe?) From: Bjorn Danielsson Date: 15 Dec 1999 22:32:35 +0100 Message-ID: Lines: 47 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 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 I have had similar problems (with 3.3-RELEASE), and yesterday I tried the ncr.c from 4.x but unfortunately it didn't help. My system crashed after 26 hours, with instruction pointer == random page fault address. The machine is a Compaq Proliant 1850R with 640M RAM and a "ThunderLAN" (tl) network interface. It's a newsfeed machine running Diablo 1.25. The load during the past 26 hours was about 12 Mbit/s in, 55 Mbit/s out constantly (on the tl0 device), and about 150 tps on each of the two disks. I have had great success running Diablo 1.14 on FreeBSD-2.2.5 on older hardware. Success, like 434 days of uninterrupted service until a power outage that occurred during a scheduled (!) test of the UPS system this summer. (Diablo actually saved our asses here back in 1997, since we had been relying on INN 1.5 until then... my kudos to Matt!) I'd very much like to repeat that success on the new machine, if possible. Matthew Dillon wrote: > > :I've confirmed that neither problem exists in 4.0. There are ample > :work-arounds, both hardware and software, including just not using 3.3. > :No fixes, though, just work-arounds... Workarounds for the NCR/FXP > :issue included: > : > :1) Using 2.2.8 (4.0 isn't a production option). > :2) Using a different NIC (a Tulip worked fine). > :3) Using a different SCSI adapter (Adaptec, as Matt suggested, works fine). > :4) Using a different SCSI driver (Peter managed to get a driver from 4.0 > : hooked up under 3.3, and it survived two days of torture that would > : have toasted things within an hour using the stock driver; you'll have > : to ask him for details). > > Ed, this is great stuff! > > Are you sure about #4? Is that the same ncr.c driver or something > else? There are only a few differences between the 3.x and 4.x > /usr/src/sys/pci/ncr.c drivers. Which Peter, Peter Wemm? > > -Matt > Matthew Dillon > -- BjЖrn Danielsson KTHNOC / Swedish University Network (mail me for my real e-mail address) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 14:26:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.49]) by hub.freebsd.org (Postfix) with ESMTP id 886E4155D8 for ; Wed, 15 Dec 1999 14:26:47 -0800 (PST) (envelope-from whs@xs4all.nl) Received: from localhost.localdomain (dc2-isdn2309.dial.xs4all.nl [194.109.157.5]) by smtp3.xs4all.nl (8.9.3/8.9.3) with SMTP id XAA00893 for ; Wed, 15 Dec 1999 23:26:41 +0100 (CET) Message-ID: <385823F9.30DA261D@xs4all.nl> Date: Wed, 15 Dec 1999 23:27:53 +0000 From: WHS Organization: robots anonymous X-Mailer: Mozilla 3.01 (X11; I; Linux 2.2.5-22 i686) MIME-Version: 1.0 To: hackers@freebsd.org Subject: ncr scsi timeout Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG L.S. The kernel hangs (rather an endless loop) with messages like: ncr0: timeout nccb=0xc0c38000 if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the ncr source it seems there's a problem with the script stuff in case of a timeout. Anyway, this doesn't happen with either the obsd or linux ncr driver (both derived from the fbsd one I believe), so that may provide some info for whoever maintains this driver. Please mail me with suggestions or pacthes to try out as I need the MO drive. Regards, Wouter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 14:31:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.geocrawler.com (sourceforge.net [209.81.8.17]) by hub.freebsd.org (Postfix) with ESMTP id 0C01714C58 for ; Wed, 15 Dec 1999 14:31:38 -0800 (PST) (envelope-from nobody@www.geocrawler.com) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id OAA23028; Wed, 15 Dec 1999 14:31:35 -0800 Date: Wed, 15 Dec 1999 14:31:35 -0800 Message-Id: <199912152231.OAA23028@www.geocrawler.com> To: freebsd-hackers@freebsd.org Subject: PCI/ISA device name From: "Alex" Reply-To: "Alex" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Alex" Be sure to reply to that address. Hello, My driver support ISA/PCI network boards. Can I use the same name for ISA and PCI devices in kernel configuration file? Like this: device wanpipe0 at isa? ... # for ISA device wanpipe0 # for PCI In files.i386 I added: i386/isa/sdladev.c optional wanpipe device-driver Or this is can be cause for some problem? Thank you Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 14:32: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.geocrawler.com (sourceforge.net [209.81.8.17]) by hub.freebsd.org (Postfix) with ESMTP id 50FCD1508F for ; Wed, 15 Dec 1999 14:31:56 -0800 (PST) (envelope-from nobody@www.geocrawler.com) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id OAA23056; Wed, 15 Dec 1999 14:31:56 -0800 Date: Wed, 15 Dec 1999 14:31:56 -0800 Message-Id: <199912152231.OAA23056@www.geocrawler.com> To: freebsd-hackers@freebsd.org Subject: Major device number From: "Alex" Reply-To: "Alex" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Alex" Be sure to reply to that address. Hello, How can I choose major device number for our network adapter driver? Thank you, Alex Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 14:34:24 1999 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 0A30C14C14 for ; Wed, 15 Dec 1999 14:34:18 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA17724; Wed, 15 Dec 1999 17:34:14 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id RAA16921; Wed, 15 Dec 1999 17:34:13 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id RAA69777; Wed, 15 Dec 1999 17:34:13 -0500 (EST) Date: Wed, 15 Dec 1999 17:34:13 -0500 (EST) From: Thomas David Rivers Message-Id: <199912152234.RAA69777@lakes.dignus.com> To: hackers@FreeBSD.ORG, whs@xs4all.nl Subject: Re: ncr scsi timeout In-Reply-To: <385823F9.30DA261D@xs4all.nl> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The kernel hangs (rather an endless loop) with messages like: > > ncr0: timeout nccb=0xc0c38000 > > if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the > ncr source it seems there's a problem with the script stuff in case of a > timeout. Anyway, this doesn't happen with either the obsd or linux ncr > driver (both derived from the fbsd one I believe), so that may provide > some info for whoever maintains this driver. > > Please mail me with suggestions or pacthes to try out as I need the MO > drive. > > Regards, > > Wouter You didn't say which version of FreeBSD you're using.... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 14:38:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id ADB1614A0E for ; Wed, 15 Dec 1999 14:38:48 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01799; Wed, 15 Dec 1999 14:41:58 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912152241.OAA01799@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Alex" Cc: freebsd-hackers@freebsd.org Subject: Re: Major device number In-reply-to: Your message of "Wed, 15 Dec 1999 14:31:56 PST." <199912152231.OAA23056@www.geocrawler.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 14:41:58 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This message was sent from Geocrawler.com by "Alex" > Be sure to reply to that address. > > Hello, > How can I choose major device number for our > network adapter driver? Network adapters don't have major/minor numbers, so you don't need to do this. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 15:48:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp7.xs4all.nl (smtp7.xs4all.nl [194.109.127.50]) by hub.freebsd.org (Postfix) with ESMTP id 63C4615617 for ; Wed, 15 Dec 1999 15:48:37 -0800 (PST) (envelope-from whs@xs4all.nl) Received: from localhost.localdomain (dc2-isdn2179.dial.xs4all.nl [194.109.156.131]) by smtp7.xs4all.nl (8.9.3/8.9.3) with SMTP id AAA20675; Thu, 16 Dec 1999 00:48:27 +0100 (CET) Message-ID: <3858372B.D5BBFAF@xs4all.nl> Date: Thu, 16 Dec 1999 00:49:47 +0000 From: WHS Organization: robots anonymous X-Mailer: Mozilla 3.01 (X11; I; Linux 2.2.5-22 i686) MIME-Version: 1.0 To: Thomas David Rivers Cc: hackers@FreeBSD.ORG Subject: Re: ncr scsi timeout References: <199912152234.RAA69777@lakes.dignus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thomas David Rivers wrote: > > > > > The kernel hangs (rather an endless loop) with messages like: > > > > ncr0: timeout nccb=0xc0c38000 > > > > if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the > > ncr source it seems there's a problem with the script stuff in case of a > > timeout. Anyway, this doesn't happen with either the obsd or linux ncr > > driver (both derived from the fbsd one I believe), so that may provide > > some info for whoever maintains this driver. > > > > Please mail me with suggestions or pacthes to try out as I need the MO > > drive. > > > > Regards, > > > > Wouter > > You didn't say which version of FreeBSD you're using.... Oops.. It's 3.3 (RELEASE I guess, the oct cdrom). Wouter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 15:53:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id 80F96155FC for ; Wed, 15 Dec 1999 15:53:13 -0800 (PST) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.1a/8.9.1) id HAA09649; Thu, 16 Dec 1999 07:52:54 +0800 (WST) From: Michael Kennett Message-Id: <199912152352.HAA09649@laurasia.com.au> Subject: Re: pccard disruptions : how did it go? In-Reply-To: <199912151655.JAA61300@harmony.village.org> from Warner Losh at "Dec 15, 99 09:55:27 am" To: imp@village.org (Warner Losh) Date: Thu, 16 Dec 1999 07:52:54 +0800 (WST) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (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 Warner wrote: > In message <199912151129.TAA29972@laurasia.com.au> Michael Kennett writes: > : I've just scoured the archives, and found a thread from late October 1999 > : titled: > : Massive pccard disruptions to continue > : > : So, have these disruptions continued? And what is the current status with > : pccard support in the kernel? > > The new pccard code is still being worked on. To confirm: The new pccard code contains the `controller pccard' config directive. - the source code is in sys/dev/pcic sys/dev/pccard The old pccard code contains the `controller card' config directive. - the source code is in sys/pccard Is this correct ? > > However, the old pccard code mostly works again, modulo a couple of > if_detach issues that I'm trying to work through. > > : I've noticed that a few files still contain the PCCARD_MODULE macro > : - in particular, the dev/pccard/if_xe.c Xircom driver. I'm > : interested in getting the if_xe.c driver to work under -current > : (12-Dec sources). I'd be interested in any ideas on how to convert > : the old if_xe.c driver to the 'newbus' code. (I'm not familiar with > : either the old PCCARD_MODULE, or the newbus code.) > > The if_xe and if_fe drivers no longer work for pccard. You may wish > to investigate how the ep and ed drivers were converted. There is one > issue with the if_xe driver, namely it needs to access the CIS of the > card to determine which kind of card it is and that will need some > work in -current to get working again... > > I can provide support for this effort, but I'm not sure that I have > time to do this effort. Thank you for your help. I'm not asking you to do it all, but instead what needs to be done, and in what direction I should be going! I think hacking the xe driver to work with the newbus kludge is less than desirable. Instead, I'd like to aim for support under the new pccard code. However, I've noticed that the file /dev/pcic/i82365_isasubr.c is missing from the Dec 12 -current sources, and compilation fails for `controller pccard'. Regards, Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 15:56:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3FFAB15625 for ; Wed, 15 Dec 1999 15:56:15 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA08720; Wed, 15 Dec 1999 16:55:51 -0700 (MST) (envelope-from ken) Date: Wed, 15 Dec 1999 16:55:51 -0700 From: "Kenneth D. Merry" To: WHS Cc: Thomas David Rivers , hackers@FreeBSD.ORG Subject: Re: ncr scsi timeout Message-ID: <19991215165550.A8672@panzer.kdm.org> References: <199912152234.RAA69777@lakes.dignus.com> <3858372B.D5BBFAF@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3858372B.D5BBFAF@xs4all.nl>; from whs@xs4all.nl on Thu, Dec 16, 1999 at 12:49:47AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 00:49:47 +0000, WHS wrote: > Thomas David Rivers wrote: > > > > > > > > The kernel hangs (rather an endless loop) with messages like: > > > > > > ncr0: timeout nccb=0xc0c38000 > > > > > > if I attach a fujitsu M2513A2 640MB MO drive. From a quick glance in the > > > ncr source it seems there's a problem with the script stuff in case of a > > > timeout. Anyway, this doesn't happen with either the obsd or linux ncr > > > driver (both derived from the fbsd one I believe), so that may provide > > > some info for whoever maintains this driver. > > > > > > Please mail me with suggestions or pacthes to try out as I need the MO > > > drive. > > > > > > Regards, > > > > > > Wouter > > > > You didn't say which version of FreeBSD you're using.... > > Oops.. It's 3.3 (RELEASE I guess, the oct cdrom). Depending on what sort of NCR board you have, I would suggest trying out the new sym driver, written by Gerard Roudier . It is located here: ftp://ftp.tux.org/tux/roudier/drivers/freebsd/experimental/ Look at the readme file in that directory to determine whether your board is supported. If you have questions, problems, etc., with the sym driver, contact Gerard. In general, the stock NCR driver isn't being actively maintained, and your problem could be the result of a bug in the driver, or some problem with your MO drive. It's hard to say for sure. Gerard's driver is actively maintained, though, so if you still have problems with his driver, it'll be easier to get the problems fixed. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 16:25:30 1999 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 5D95515632 for ; Wed, 15 Dec 1999 16:25:24 -0800 (PST) (envelope-from imp@harmony.village.org) 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 RAA79080; Wed, 15 Dec 1999 17:25:19 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA65931; Wed, 15 Dec 1999 17:25:19 -0700 (MST) Message-Id: <199912160025.RAA65931@harmony.village.org> To: Michael Kennett Subject: Re: pccard disruptions : how did it go? Cc: freebsd-hackers@freebsd.org In-reply-to: Your message of "Thu, 16 Dec 1999 07:52:54 +0800." <199912152352.HAA09649@laurasia.com.au> References: <199912152352.HAA09649@laurasia.com.au> Date: Wed, 15 Dec 1999 17:25:19 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912152352.HAA09649@laurasia.com.au> Michael Kennett writes: : To confirm: : : The new pccard code contains the `controller pccard' config directive. : - the source code is in sys/dev/pcic : sys/dev/pccard : : The old pccard code contains the `controller card' config directive. : - the source code is in sys/pccard : : Is this correct ? Yes. That's right. : Thank you for your help. I'm not asking you to do it all, but : instead what needs to be done, and in what direction I should be : going! I think hacking the xe driver to work with the newbus kludge : is less than desirable. Instead, I'd like to aim for support under : the new pccard code. It is indended attach will be the same, and that probe will nearly be the same, at least at first. The probe code for the drivers will be longer for newcard in that it will have to claim the device if the driver supports it. In the old pccard code probe is just a nice dummy which calls the usual probe routine for its side effects (the sio driver's probe routine leaves the uart in a known state, for example). I've been toying with the idea of having an identify routine which would make it possible to have the same binary for both the old driver and new, but that's not completely settled. I'm slogging through hooking up the newbus routines to the old chip tag stuff. I need to map the rid into the window that they currently return. I also need to figure out how to get the card's address (in card space) mapped with the allocation routines that we have now. Then I move into pccard and convert the chip tag calls into newbus calls. I also need to go through and make sure that the softc/ivars stuff connected and working properly. The pcic is the bridge driver. It will have n children, one per slot. Each slot will have zero or more children drivers based on the cards that are connected. It is intended that we'll support multiple functions in this way. The pccard children devices will have pcic_ivars as their ivars. The children of the pccard children will have pccard_ivars. : However, I've noticed that the file /dev/pcic/i82365_isasubr.c is missing : from the Dec 12 -current sources, and compilation fails for `controller : pccard'. Did you rerun config (or did I botch the commit and not commit conf/files wich removed it)? Oh, looks like my botch.... sorry about that... fixed. What can you do to help? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 16:31:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 92F3014D02; Wed, 15 Dec 1999 16:31:36 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA85601; Thu, 16 Dec 1999 11:01:01 +1030 (CST) Date: Thu, 16 Dec 1999 11:01:01 +1030 From: Greg Lehey To: David Bein Cc: FreeBSD Hackers Subject: Re: Solaris 2.7 ufs file systems ... Message-ID: <19991216110101.O48955@freebie.lemis.com> References: <945005691/bein@sanity.mass.pyramid.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <945005691/bein@sanity.mass.pyramid.com> 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [redirected to -hackers] On Sunday, 12 December 1999 at 8:34:51 -0500, David Bein wrote: > Hi ... > > I have a PC with triple boot partitions setup, one of > which is loaded with Solaris 2.7 (officially called version 7). > I am wondering if anyone has any experience directly mounting ufs > partitions which Solaris created. It should be pretty straight > forward to come up with a modified ufs source to read them > (much like ext2fs), but of course figuring out where Solaris > keeps the partition tables needed to get at the slices within > the partition is apparently a military secret. Can anyone > offer any advice on how to go about this? You'll probably find more interested people on -hackers, so I've redirected the message there. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 17: 2:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id 65D2115414 for ; Wed, 15 Dec 1999 17:02:14 -0800 (PST) (envelope-from whs@xs4all.nl) Received: from localhost (dc2-isdn2218.dial.xs4all.nl [194.109.156.170]) by smtp1.xs4all.nl (8.9.3/8.9.3) with SMTP id CAA21971 for ; Thu, 16 Dec 1999 02:02:11 +0100 (CET) Message-ID: <3858485E.167EB0E7@xs4all.nl> Date: Thu, 16 Dec 1999 02:03:10 +0000 From: "W.H.Scholten" Organization: Robots anonymous X-Mailer: Mozilla 3.04 (X11; I; FreeBSD 3.3-RELEASE i386) MIME-Version: 1.0 To: hackers@FreeBSD.ORG Subject: Re: ncr scsi timeout References: <199912152234.RAA69777@lakes.dignus.com> <3858372B.D5BBFAF@xs4all.nl> <19991215165550.A8672@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth D. Merry wrote: > In general, the stock NCR driver isn't being actively maintained, and your > problem could be the result of a bug in the driver, or some problem with > your MO drive. It's hard to say for sure. Gerard's driver is actively > maintained, though, so if you still have problems with his driver, it'll be > easier to get the problems fixed. I'm using a Tekram DC 390U (ncr 875 ultra, not wide) controller which the readme said was supported, so I just compiled a new kernel with the new driver and everything works hunky dory now :-) Thanks. Wouter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 17:36:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 997C414A16 for ; Wed, 15 Dec 1999 17:36:42 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA09899; Wed, 15 Dec 1999 18:36:35 -0700 (MST) (envelope-from ken) Date: Wed, 15 Dec 1999 18:36:35 -0700 From: "Kenneth D. Merry" To: "W.H.Scholten" Cc: hackers@FreeBSD.ORG Subject: Re: ncr scsi timeout Message-ID: <19991215183635.A9876@panzer.kdm.org> References: <199912152234.RAA69777@lakes.dignus.com> <3858372B.D5BBFAF@xs4all.nl> <19991215165550.A8672@panzer.kdm.org> <3858485E.167EB0E7@xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3858485E.167EB0E7@xs4all.nl>; from whs@xs4all.nl on Thu, Dec 16, 1999 at 02:03:10AM +0000 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 02:03:10 +0000, W.H.Scholten wrote: > Kenneth D. Merry wrote: > > > In general, the stock NCR driver isn't being actively maintained, and your > > problem could be the result of a bug in the driver, or some problem with > > your MO drive. It's hard to say for sure. Gerard's driver is actively > > maintained, though, so if you still have problems with his driver, it'll be > > easier to get the problems fixed. > > I'm using a Tekram DC 390U (ncr 875 ultra, not wide) controller which > the readme said was supported, so I just compiled a new kernel with the > new driver and everything works hunky dory now :-) Good, glad to hear it! Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 15 20:52:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 3738D15543 for ; Wed, 15 Dec 1999 20:52:21 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id XAA23930 for ; Wed, 15 Dec 1999 23:52:11 -0500 Date: Wed, 15 Dec 1999 23:52:11 -0500 (EST) From: Mike Nowlin To: freebsd-hackers@freebsd.org Subject: fixing a catch-22 with getty Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (this is on 3.4-RC as of Dec. 11) Here's the situation -- a lot of modems are brain-dead, and don't do a full reset when you tell them to (by a DTR drop, with (usually) AT&D3)... The DTE baud rate likes to stay where it was, instead of returning to the 115200 that (my) gettys are expecting. I was hoping to fix this by using the "ic" init-chat script ability from gettytab -- send it a 115200 "ATS0=1\r" or something, and that's where the problems started... :) Apparently, the chat scripts like to see a carrier on the line before it will write to the tty. Tried setting gettytab to impose CLOCAL on the line, no luck. Went into main.c and added the following to main(): (lines marked with "-->") --> struct termios tmpbmode; ... ... if (IC) { if (!opentty(ttyn, O_RDWR|O_NONBLOCK)) exit(1); setdefttymode(tname); --> /* create a copy to work with */ --> (void)tcgetattr(STDIN_FILENO, &tmpbmode); --> /* set CLOCAL in the working copy, and tcsetattr() it */ --> tmpbmode.c_cflag |= CLOCAL; --> (void)tcsetattr(STDIN_FILENO, TCSANOW, &tmpbmode); if (getty_chat(IC, CT, DC) > 0) { syslog(LOG_ERR, "modem init problem on %s", tty); (void)tcsetattr(STDIN_FILENO, TCSANOW, &tmode); exit(1); } --> /* restore the saved copy of the terminal attrs */ --> setdefttymode(tname); } if (AC) { ...... (yes, I know it's icky, but it's an experiment.) This did allow the chat script to work, and the modem did init correctly at the right baud rate, but now I'm running into the fact that nothing other than getty can talk to the port (UUCP, kermit, etc.), probably due to the non-blocking open... A "ps ax" shows the "TT" column with a value of "c04" with the init script, where it is normally "--" when I just use the "wait for carrier before becoming active" (blocking open) method. I DO want it to switch back to the wait-for-carrier way of life after the init script is finished.... I'm going to continue working on this until the wee hours of the morning, but maybe somebody has some ideas? thanks - mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 2: 0:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from laurasia.com.au (lauras.lnk.telstra.net [139.130.93.142]) by hub.freebsd.org (Postfix) with ESMTP id 44FBD155A1 for ; Thu, 16 Dec 1999 02:00:17 -0800 (PST) (envelope-from mike@laurasia.com.au) Received: (from mike@localhost) by laurasia.com.au (8.9.1a/8.9.1) id SAA18401; Thu, 16 Dec 1999 18:00:06 +0800 (WST) From: Michael Kennett Message-Id: <199912161000.SAA18401@laurasia.com.au> Subject: Re: pccard disruptions : how did it go? In-Reply-To: <199912160025.RAA65931@harmony.village.org> from Warner Losh at "Dec 15, 99 05:25:19 pm" To: imp@village.org (Warner Losh) Date: Thu, 16 Dec 1999 18:00:05 +0800 (WST) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (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 Hi Warner, Thanks for your detailed writeup of the direction that you want to go in. > > What can you do to help? > Well, firstly I'd like to get the xe driver under FreeBSD. But before I even get to that stage, I'll have to learn about the pccard subsystem, and more about the FreeBSD kernel internals. I've had a look at the man pages Doug Rabson wrote for the device attach code - they are very good - and thought about writing a man page for pccard (4) that would detail the ioctl's provided by the system, and other man pages that would detail the design of the pccard subsystem. I suppose the eventual goal of this work would be to have a 'howto-write-a-pccard-driver-for-freebsd' howto. In any case, before porting the xe driver I'll have to have a clue on how to do the port, so this howto should be an easy by-product. I've got -current (12th dec sources) on an IBM 365X, and I can/will use that box for testing. Unfortunately, the network connection is by floppy-net, and so I'm not too keen on reinstalling lots of software on it. But I'll try to track -current reasonably closely (fortnightly). As usual, I'm constrained on time. So I'm not going to make any commitments on getting stuff done! By the same token, I don't expect anyone else to get anything done, and I'll certainly not make demands on FreeBSD, or its developers. I doubt that I'd get the xe driver ported before 4.0 is released. What help do you require? Regards, Mike Kennett (mike@laurasia.com.au) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 2:59:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 70F8214CB8; Thu, 16 Dec 1999 02:59:15 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id KAA07017 Thu, 16 Dec 1999 10:59:13 GMT Message-ID: <3858C600.41C6@cs.strath.ac.uk> Date: Thu, 16 Dec 1999 10:59:12 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: hackers@freebsd.org, multimedia@freebsd.org Subject: Multi Head XFree86 VGA card recomendations wanted Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I need to build some new Multi-Head FreeBSD machines in my lab using XFree86 3.9.16. I want to know which VGA cards to buy for Multi-Head (dual monitor) support. Currently I have 1 multi-head FreeBSD machine using Matrox Millenium cards abd XFree86 3.9.16. It works great, but you cannot buy Millenium cards any more. Reading the XFree86 docs, it seems almost all PCI cards are supported multihead on Linux where they can issue an INT 10 call to initialise the BIOS in the secondary card. I'm not sure it we can support that in FreeBSD. Cheers Roger -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 3: 4:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eth0-gw.poli.hu (eth0-gw.poli.hu [195.199.8.27]) by hub.freebsd.org (Postfix) with ESMTP id 2157915569; Thu, 16 Dec 1999 03:04:04 -0800 (PST) (envelope-from mauzi@faber.poli.hu) Received: from faber.poli.hu ([195.199.8.29]) by eth0-gw.poli.hu with esmtp (Exim 3.11 #1 (Debian)) id 11yYgS-00071n-00; Thu, 16 Dec 1999 12:02:56 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.11 #1 (Debian)) id 11yYgR-0002bA-00; Thu, 16 Dec 1999 12:02:55 +0100 Date: Thu, 16 Dec 1999 12:02:55 +0100 (CET) From: Egervary Gergely To: Roger Hardiman Cc: hackers@freebsd.org, multimedia@freebsd.org Subject: Re: Multi Head XFree86 VGA card recomendations wanted In-Reply-To: <3858C600.41C6@cs.strath.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 > I need to build some new Multi-Head FreeBSD machines > in my lab using XFree86 3.9.16. > > I want to know which VGA cards to buy > for Multi-Head (dual monitor) support. > > Currently I have 1 multi-head FreeBSD machine using > Matrox Millenium cards abd XFree86 3.9.16. > It works great, but you cannot buy Millenium cards any more. matrox :) g200 / g400 you can buy dual-head cards, or use more than one card (pci only) -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 3:25:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 1E45A14C2F; Thu, 16 Dec 1999 03:25:31 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id LAA08522 Thu, 16 Dec 1999 11:25:27 GMT Message-ID: <3858CC26.2781@cs.strath.ac.uk> Date: Thu, 16 Dec 1999 11:25:26 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: Egervary Gergely Cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Multi Head XFree86 VGA card recomendations wanted References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I need to build some new Multi-Head FreeBSD machines > > in my lab using XFree86 3.9.16. > > > > I want to know which VGA cards to buy > > for Multi-Head (dual monitor) support. > > > matrox :) > > g200 / g400 > > you can buy dual-head cards, or use more than one card (pci only) The Dual-Head G400 (the one in a single AGP card) does not work with XFree86. XFree86 was written to support one monitor per VGA chip and cannot cope with 2 RAMDACs on one controller. Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 3:37:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eth0-gw.poli.hu (eth0-gw.poli.hu [195.199.8.27]) by hub.freebsd.org (Postfix) with ESMTP id E7B391562E; Thu, 16 Dec 1999 03:37:07 -0800 (PST) (envelope-from mauzi@faber.poli.hu) Received: from faber.poli.hu ([195.199.8.29]) by eth0-gw.poli.hu with esmtp (Exim 3.11 #1 (Debian)) id 11yZCl-00072I-00; Thu, 16 Dec 1999 12:36:19 +0100 Received: from mauzi (helo=localhost) by faber.poli.hu with local-esmtp (Exim 3.11 #1 (Debian)) id 11yZCm-0002dy-00; Thu, 16 Dec 1999 12:36:20 +0100 Date: Thu, 16 Dec 1999 12:36:20 +0100 (CET) From: Egervary Gergely To: Roger Hardiman Cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Multi Head XFree86 VGA card recomendations wanted In-Reply-To: <3858CC26.2781@cs.strath.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 > XFree86 was written to support one monitor per VGA chip > and cannot cope with 2 RAMDACs on one controller. ok then need to use pci cards. damn. -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 4:28:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.orakel.ntnu.no (apollo.orakel.ntnu.no [129.241.56.245]) by hub.freebsd.org (Postfix) with SMTP id 6C75314DFB for ; Thu, 16 Dec 1999 04:28:17 -0800 (PST) (envelope-from oyvindmo@orakel.ntnu.no) Received: (qmail 28943 invoked by uid 28778); 16 Dec 1999 12:28:15 -0000 To: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Multi Head XFree86 VGA card recomendations wanted References: From: Oyvind Moll Date: 16 Dec 1999 13:28:14 +0100 In-Reply-To: Message-ID: Lines: 15 User-Agent: Gnus/5.070097 (Pterodactyl Gnus v0.97) Emacs/20.3 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 * Egervary Gergely | | > XFree86 was written to support one monitor per VGA chip | > and cannot cope with 2 RAMDACs on one controller. | | ok then need to use pci cards. damn. Is it possible to use one AGP card and one PCI card together? (e.g. PCI Matrox Mill. I + AGP Matrox Mill. II) The release notes for XFree86 3.9.16 were a bit vague on that point. -- ьyvind MЬll oyvindmo@initio.no http://www.initio.no/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 4:58:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 909A715602; Thu, 16 Dec 1999 04:58:11 -0800 (PST) (envelope-from mestery@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 19EEF37EC; Thu, 16 Dec 1999 06:55:26 -0600 (CST) Received: from localhost (mestery@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id GAA29943; Thu, 16 Dec 1999 06:55:26 -0600 (CST) X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs Date: Thu, 16 Dec 1999 06:55:26 -0600 (CST) From: To: Roger Hardiman Cc: Egervary Gergely , hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Multi Head XFree86 VGA card recomendations wanted In-Reply-To: <3858CC26.2781@cs.strath.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 On Thu, 16 Dec 1999, Roger Hardiman wrote: > The Dual-Head G400 (the one in a single AGP card) does not > work with XFree86. > It works fine with XFree86 using only one monitor output, however. It's a very nice card, even without the dual monitor support. -- Kyle Mestery | Ancor Communications mestery@visi.com | http://www.freebsd.org/ mestery@netwinder.org | http://www.netwinder.org/ Protect your right to privacy: www.freecrypto.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 5:41:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fleming.cs.strath.ac.uk (fleming.cs.strath.ac.uk [130.159.196.126]) by hub.freebsd.org (Postfix) with ESMTP id 747F814DCC; Thu, 16 Dec 1999 05:41:30 -0800 (PST) (envelope-from roger@cs.strath.ac.uk) Received: from muir-10 (roger@muir-10.cs.strath.ac.uk [130.159.148.10]) by fleming.cs.strath.ac.uk (8.8.8/8.8.8) with SMTP id NAA14566 Thu, 16 Dec 1999 13:40:26 GMT Message-ID: <3858EBC9.41C6@cs.strath.ac.uk> Date: Thu, 16 Dec 1999 13:40:25 +0000 From: Roger Hardiman Organization: University of Strathclyde X-Mailer: Mozilla 3.04Gold (X11; I; OSF1 V4.0 alpha) MIME-Version: 1.0 To: mestery@visi.com Cc: Egervary Gergely , hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Multi Head XFree86 VGA card recomendations wanted References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > The Dual-Head G400 (the one in a single AGP card) does not > > work with XFree86. > > > It works fine with XFree86 using only one monitor output. Sorry, I was unclear with my last statement. The Dual-Head G400 is cannot be used with XFree86 as a Dual-Head card, but is great for use with a single monitor. Roger -- Roger Hardiman | Telepresence Research Group roger@cs.strath.ac.uk | DMEM, University of Strathclyde tel: 0141 548 2897 | Glasgow, Scotland, G1 1XJ, UK fax: 0141 552 0557 | http://www.telepresence.strath.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 8:51:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 83B7414DC7; Thu, 16 Dec 1999 08:51:24 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 3.03 #3) id 11ye7e-0003eI-00; Thu, 16 Dec 1999 09:51:23 -0700 Message-ID: <385918DA.8F7F84D@softweyr.com> Date: Thu, 16 Dec 1999 09:52:42 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Roger Hardiman Cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Multi Head XFree86 VGA card recomendations wanted References: <3858C600.41C6@cs.strath.ac.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roger Hardiman wrote: > > Hi, > > I need to build some new Multi-Head FreeBSD machines > in my lab using XFree86 3.9.16. > > I want to know which VGA cards to buy > for Multi-Head (dual monitor) support. > > Currently I have 1 multi-head FreeBSD machine using > Matrox Millenium cards abd XFree86 3.9.16. > It works great, but you cannot buy Millenium cards any more. > > Reading the XFree86 docs, it seems almost all PCI cards are > supported multihead on Linux where they can issue an INT 10 > call to initialise the BIOS in the secondary card. > I'm not sure it we can support that in FreeBSD. Have you considered buying Metro-X? It supports up to 4 screens on just about any combination of AGP and PCI Matrox cards. For more information, see http://www.metrolink.com/productindex.html and look for Multi-Headed Display Support. Metro-X is only $39. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 9: 0:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id 573EE15617 for ; Thu, 16 Dec 1999 09:00:16 -0800 (PST) (envelope-from cillian@psn.ie) Received: from alto.internal ([192.168.0.254]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 11ye0A-0006p5-00 for hackers@freebsd.org; Thu, 16 Dec 1999 16:43:38 +0000 Received: from cillian (helo=localhost) by alto.internal with local-esmtp (Exim 2.12 #1) id 11ye09-0005uW-00 for hackers@freebsd.org; Thu, 16 Dec 1999 16:43:38 +0000 Date: Thu, 16 Dec 1999 16:43:37 +0000 (GMT) From: Cillian Sharkey X-Sender: cillian@alto.internal To: hackers@freebsd.org Subject: Strange problem with NFS 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 folks, I've been trying to accomplish the simple task of mounting filesystems from a central server 'hostA' onto a new client 'hostB'. the new client has a basic 3.3 'bin' distrib installed on it and I am trying to mount /usr/src & /usr/obj from hostA so that I can upgrade it. the problem is that the mounts hang and never succeed. i've added hostB to hostA's /etc/exports file of course. other machines are already mounting from /usr/src etc. from hostA with no problems. i've tried a different NIC, different machine and a 3.3-STABLE kernel with no luck. tcpdump on hostA : .. 16:33:36.097396 hostB.1023 > hostA.sunrpc: udp 56 16:33:36.097986 hostA.sunrpc > hostB.1023: udp 28 16:33:36.098660 hostB.1022 > hostA.sunrpc: udp 56 16:33:36.099028 hostA.sunrpc > hostB.1022: udp 28 16:33:36.099761 hostB.827471909 > hostA.nfs: 40 null 16:33:36.099898 hostA.nfs > hostB.827471909: reply ok 24 getattr [|nfs] 16:33:36.100515 hostB.1020 > hostA.sunrpc: udp 56 16:33:36.100883 hostA.sunrpc > hostB.1020: udp 28 16:33:36.101863 hostB.1019 > hostA.1023: udp 120 16:33:36.102261 hostA.1023 > hostB.1019: udp 68 16:33:36.103849 hostB.494063090 > hostA.nfs: 120 getattr [|nfs] 16:33:36.104031 hostA.nfs > hostB.494063090: reply ok 112 read [|nfs] 16:33:36.104427 hostB > hostA: icmp: hostB udp port 1018 unreachable 16:33:37.107671 hostB.494063090 > hostA.nfs: 120 getattr [|nfs] 16:33:37.107821 hostA.nfs > hostB.494063090: reply ok 112 read [|nfs] 16:33:37.108206 hostB > hostA: icmp: hostB udp port 1018 unreachable 16:33:38.664513 hostB.1024 > hostA.domain: 50+ (44) 16:33:38.664862 hostA.domain > hostB.1024: 50* 1/1/2 (154) 16:33:39.117600 hostB.494063090 > hostA.nfs: 120 getattr [|nfs] 16:33:39.117740 hostA.nfs > hostB.494063090: reply ok 112 read [|nfs] 16:33:39.118163 hostB > hostA: icmp: hostB udp port 1018 unreachable 16:33:43.127284 hostB.494063090 > hostA.nfs: 120 getattr [|nfs] 16:33:43.127417 hostA.nfs > hostB.494063090: reply ok 112 read [|nfs] 16:33:43.127822 hostB > hostA: icmp: hostB udp port 1018 unreachable 16:33:44.918311 hostB.blackjack > hostA.domain: 58213+ (44) 16:33:44.918635 hostA.domain > hostB.blackjack: 58213* 1/1/2 (154) 16:33:47.720648 hostB.1026 > hostA.domain: 58987+ (44) 16:33:47.721044 hostA.domain > hostB.1026: 58987* 1/1/2 (154) 16:33:51.136773 hostB.494063090 > hostA.nfs: 120 getattr [|nfs] 16:33:51.136930 hostA.nfs > hostB.494063090: reply ok 112 read [|nfs] 16:33:51.137363 hostB > hostA: icmp: hostB udp port 1018 unreachable .. notice the icmp port unreachable msgs, yet on hostB: netstat -a : .. udp 0 0 hostB.1018 hostA.nfsd .. ps axlw : .. 0 254 1 0 2 0 340 200 sbwait D v0 0:00.01 nfs -o ro -o noatime -o noauto hostA /usr/src (mount_nfs) .. any ideas ? Thanks, Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 9: 7:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 141A214DDC for ; Thu, 16 Dec 1999 09:07:14 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA54566; Thu, 16 Dec 1999 09:07:09 -0800 (PST) (envelope-from dillon) Date: Thu, 16 Dec 1999 09:07:09 -0800 (PST) From: Matthew Dillon Message-Id: <199912161707.JAA54566@apollo.backplane.com> To: Cillian Sharkey Cc: hackers@FreeBSD.ORG Subject: Re: Strange problem with NFS References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi folks, : :I've been trying to accomplish the simple task of mounting filesystems :from a central server 'hostA' onto a new client 'hostB'. the new client :has a basic 3.3 'bin' distrib installed on it and I am trying to mount :/usr/src & /usr/obj from hostA so that I can upgrade it. : :the problem is that the mounts hang and never succeed. i've added hostB to :hostA's /etc/exports file of course. other machines are already mounting :from /usr/src etc. from hostA with no problems. : :i've tried a different NIC, different machine and a 3.3-STABLE kernel with :no luck. : :tcpdump on hostA : :.. :16:33:36.097396 hostB.1023 > hostA.sunrpc: udp 56 :16:33:36.097986 hostA.sunrpc > hostB.1023: udp 28 :16:33:36.098660 hostB.1022 > hostA.sunrpc: udp 56 :16:33:36.099028 hostA.sunrpc > hostB.1022: udp 28 :16:33:36.099761 hostB.827471909 > hostA.nfs: 40 null :16:33:36.099898 hostA.nfs > hostB.827471909: reply ok 24 getattr [|nfs] :16:33:36.100515 hostB.1020 > hostA.sunrpc: udp 56 :16:33:36.100883 hostA.sunrpc > hostB.1020: udp 28 :16:33:36.101863 hostB.1019 > hostA.1023: udp 120 :16:33:36.102261 hostA.1023 > hostB.1019: udp 68 :16:33:36.103849 hostB.494063090 > hostA.nfs: 120 getattr [|nfs] :16:33:36.104031 hostA.nfs > hostB.494063090: reply ok 112 read [|nfs] :16:33:36.104427 hostB > hostA: icmp: hostB udp port 1018 unreachable Looks like a firewall to me. Either a firewall in a router sitting between the hosts, or an ipfw setup sitting on one or the other host. :notice the icmp port unreachable msgs, yet on hostB: : :netstat -a : :.. :udp 0 0 hostB.1018 hostA.nfsd :... :Thanks, :Cillian This is meaningless. Since UDP is connectionless this is simply a placemark for what the machine wants to do, not for what it is able to do. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 10: 7: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dns1.sports.gov.uk (dns1.sports.gov.uk [212.125.74.131]) by hub.freebsd.org (Postfix) with ESMTP id 9ACA3151F2 for ; Thu, 16 Dec 1999 10:06:56 -0800 (PST) (envelope-from ad@dns1.sports.gov.uk) Received: from ad (helo=localhost) by dns1.sports.gov.uk with local-esmtp (Exim 3.03 #1) id 11yfDk-0005Xw-00; Thu, 16 Dec 1999 18:01:44 +0000 Date: Thu, 16 Dec 1999 18:01:44 +0000 (GMT) From: Andy Doran X-Sender: ad@dns1.sports.gov.uk To: Matthew Dillon Cc: Cillian Sharkey , hackers@FreeBSD.ORG Subject: Re: Strange problem with NFS In-Reply-To: <199912161707.JAA54566@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 16 Dec 1999, Matthew Dillon wrote: > Looks like a firewall to me. Either a firewall in a router > sitting between the hosts, or an ipfw setup sitting on one or the > other host. I set up the NFS server in question ages ago. I haven't looked at the problem, but... The server does use ipfw. The broken client is on the same subnet as the working ones and nothing in the server's ipfw ruleset refers directly to the broken client. - ad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 10: 9:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id A44F114EEB for ; Thu, 16 Dec 1999 10:09:35 -0800 (PST) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id LAA40339 for ; Thu, 16 Dec 1999 11:09:34 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id LAA68945; Thu, 16 Dec 1999 11:09:34 -0700 (MST) (envelope-from jjreynold@home.com) From: John and Jennifer Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14425.10973.878258.39420@whale.home-net> Date: Thu, 16 Dec 1999 11:09:33 -0700 (MST) To: freebsd-hackers@freebsd.org Subject: anybody using tn-gw-nav to tunnel ssh through a proxy? X-Mailer: VM 6.73 under Emacs 20.4.1 Cc: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello hackers, I have a rather bizzare problem and I'm hoping that somebody here can help me find the solution or at least other places to go look. At work, we use the tn-gw software to allow users to telnet out to hosts outside our firewall when necessary. There is some software called tn-gw-nav available at ftp://ftp.nlc.net.au/pub/unix/tn-gw-nav/index.html that claims to be able to allow a user to use ssh over the telnet gateway. A co-worker who has the exact same cable-modem setup that I have has gotten this working with his Linux box. He can ssh directly to his box from work. When I tried setting this software up on my end here, I ran into strange problems we can't duplicate with his Linux box. I modified /etc/services and /etc/inetd.conf like the above URL instructs (I'm not running TCP wrappers, yet). I can telnet to my "high" port and see that ssh is "answering" Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. SSH-1.5-OpenSSH-1.2 but upon trying to ssh from work to my box I get this error message: Local: Corrupted check bytes on input. If I run just the "ssh" port instead of openssh, I get the following in my messages file each time the connection fails: Dec 16 09:41:00 dolphin sshd[30368]: fatal: Local: Bad packet length 4267834977. Both of these error messages seem to be coming from sshd (grepping for strings in the binary). A "verbose" output from ssh trying to connect to my machine shows: hip186 [~]<471>% ssh -v dolphin SSH Version 1.2.20 [hppa1.1-hp-hpux10.20], protocol version 1.5. Standard version. Does not use RSAREF. hip186: Reading configuration data /eng/eng9/jreynold/.ssh/config hip186: Applying options for dolphin hip186: ssh_connect: getuid 25155 geteuid 25155 anon 1 hip186: Executing proxy command: exec tn-gw-nav -i -h proxy.domain.com hostname.home.com 3456 hip186: Remote protocol version 1.5, remote software version 1.2.27 hip186: Waiting for server public key. hip186: Received server public key (768 bits) and host key (1024 bits). hip186: Host 'hostname.home.com' is known and matches the host key. hip186: Initializing random; seed file /eng/eng9/jreynold/.ssh/random_seed hip186: Encryption type: idea hip186: Sent encrypted session key. Local: Corrupted check bytes on input. I have tried everything I can think of to get around this problem. I've tried: o using the OpenSSH port o using the linux binary for tn-gw-nav from my co-worker's Linux box o compiling tn-gw-nav with no optimization Nothing seems to work. Does anybody have any clues as to what *might* be going on here? The 4267834977 in the "bad packet length" seems awfully large, yes? With everything else being "identical" on my co-worker's Linux box (same port used, same version of OpenSSH and ssh1, same version of tn-gw-nav, and same version of ssh used here at work) it appears that something FreeBSD-related is causing me the grief. I am perfectly willing to debug this to the eye teeth (because I *really* want this functionality), but I need some pointers as to where to look. I will begin with the sshd source, but with any good debugging problem, I have to rule out FreeBSD's network code and possibly the "ed" driver as "suspects." I have searched the archives for these particular error messages but came up dry. Thank you for any "tips" as to where to look next. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds jjreynold@home.com FreeBSD 3.3-STABLE. FreeBSD: The Power to Serve. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 10:26:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fry.cs.purdue.edu (fry.cs.purdue.edu [128.10.2.30]) by hub.freebsd.org (Postfix) with SMTP id E43C31558E for ; Thu, 16 Dec 1999 10:26:54 -0800 (PST) (envelope-from splite@fry.cs.purdue.edu) Received: (qmail 197704 invoked by uid 118); 16 Dec 1999 18:27:03 -0000 Date: Thu, 16 Dec 1999 13:27:03 -0500 From: splite@purdue.edu To: Oyvind Moll Cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Multi Head XFree86 VGA card recomendations wanted Message-ID: <19991216132703.A198331@fry.cs.purdue.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: X-Disclaimer: Any similarity to an opinion of Purdue is purely coincidental Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 01:28:14PM +0100, Oyvind Moll wrote: > * Egervary Gergely > | > | > XFree86 was written to support one monitor per VGA chip > | > and cannot cope with 2 RAMDACs on one controller. > | > | ok then need to use pci cards. damn. > > Is it possible to use one AGP card and one PCI card together? > (e.g. PCI Matrox Mill. I + AGP Matrox Mill. II) > The release notes for XFree86 3.9.16 were a bit vague on that point. Yes, it is. I've used precisely that setup and it worked well. (Okay, this was XFree86 3.9.16 under Linux (sorry, this was at work), but I can't imagine it not working under FreeBSD as well.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 14: 2:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 39C41157FF for ; Thu, 16 Dec 1999 14:02:32 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id IAA03503; Fri, 17 Dec 1999 08:32:27 +1030 (CST) (envelope-from newton) Date: Fri, 17 Dec 1999 08:32:27 +1030 From: Mark Newton To: John and Jennifer Reynolds Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: anybody using tn-gw-nav to tunnel ssh through a proxy? Message-ID: <19991217083227.A3471@internode.com.au> References: <14425.10973.878258.39420@whale.home-net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <14425.10973.878258.39420@whale.home-net> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 11:09:33AM -0700, John and Jennifer Reynolds wrote: > but upon trying to ssh from work to my box I get this error message: > Local: Corrupted check bytes on input. tn-gw isn't 8-bit-clean; you'll need to patch it. Try something like this: it creates a new tn-gw-> prompt command called "rawopen" which gives you an 8-bit-clean link to whatever host/port you specify. ... and check with your IT security folks before running nos-tun over it, won't you? :-) - mark *** tn-gw.c.orig Fri Jul 4 10:05:22 1997 --- tn-gw.c Mon Jul 7 10:48:15 1997 *************** *** 61,66 **** --- 61,67 ---- static unsigned char prebuf[BUFSIZ]; static int prebufc; static int kludgeraw = 0; + static int gimme8bit = 0; static time_t ontime; static time_t offtime; *************** *** 78,83 **** --- 79,85 ---- static int cmd_connect(); static int cmd_passwd(); static int cmd_xforward(); + static int cmd_rawconn(); typedef struct { char *name; *************** *** 88,93 **** --- 90,96 ---- "connect", " connect hostname [serv/port]", cmd_connect, "telnet", " telnet hostname [serv/port]", cmd_connect, "open", 0, cmd_connect, + "rawopen", " rawopen hostname [serv/port]", cmd_rawconn, "x-gw", " x-gw [hostname/display]", cmd_xforward, "help", " help/?", cmd_help, "quit", " quit/exit", cmd_quit, *************** *** 316,322 **** if(!kludgeraw && FD_ISSET(0,&rdy)) { if(rfd == -1) { ! say(0,"Remote server has closed connection"); goto leave; } x = read(0,xuf,sizeof(xuf)); --- 319,325 ---- if(!kludgeraw && FD_ISSET(0,&rdy)) { if(rfd == -1) { ! if (!gimme8bit) say(0,"Remote server has closed connection"); goto leave; } x = read(0,xuf,sizeof(xuf)); *************** *** 342,348 **** } if(write(rfd,clientnull,x) != x) { ! say(0,"Remote server has closed connection"); goto leave; } outbytcnt += x; --- 345,351 ---- } if(write(rfd,clientnull,x) != x) { ! if (!gimme8bit) say(0,"Remote server has closed connection"); goto leave; } outbytcnt += x; *************** *** 356,362 **** if(rfd != -1 && FD_ISSET(rfd,&rdy)) { x = read(rfd,xuf,sizeof(xuf)); if(x <= 0) { ! say(0,"Remote server has closed connection"); goto leave; } if(write(0,xuf,x) != x) --- 359,365 ---- if(rfd != -1 && FD_ISSET(rfd,&rdy)) { x = read(rfd,xuf,sizeof(xuf)); if(x <= 0) { ! if (!gimme8bit) say(0,"Remote server has closed connection"); goto leave; } if(write(0,xuf,x) != x) *************** *** 738,744 **** } else syslog(LLEV,"permit host=%s/%s destination=%s",rladdr,riaddr,av[1]); ! if(port != TNPORT) { unsigned char xuf[9]; xuf[0] = IAC; --- 741,753 ---- } else syslog(LLEV,"permit host=%s/%s destination=%s",rladdr,riaddr,av[1]); ! /* 19970704 newton@atdot.dotat.org ! * "gimme8bit" flag used to determine whether this actually happens. ! * Normally, if the proxy isn't connecting to port 23 it will ! * intercept telnet IAC sequences, meaning that we can't get an ! * 8-bit clean connection. If gimme8bit is true, this behaviour ! * will be suppressed. */ ! if((port != TNPORT) && (!gimme8bit)) { unsigned char xuf[9]; xuf[0] = IAC; *************** *** 753,758 **** --- 762,769 ---- if(write(0,xuf,9) != 9) return(1); kludgeraw = 1; + } else if (gimme8bit) { + syslog(LLEV, "RAW connection requested"); } if((rfd = conn_server(av[1],port,0,buf)) < 0) { *************** *** 768,774 **** return(2); } ! baddest(fd,dest) int fd; --- 779,793 ---- return(2); } ! static int ! cmd_rawconn(ac, av, cbuf) ! int ac; ! char *av[]; ! char *cbuf; ! { ! gimme8bit = 1; ! return(cmd_connect(ac, av, cbuf)); ! } baddest(fd,dest) int fd; -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 15:41:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id E0ADD14F2D; Thu, 16 Dec 1999 15:40:53 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA01895; Thu, 16 Dec 1999 15:43:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912162343.PAA01895@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Roger Hardiman Cc: hackers@freebsd.org, multimedia@freebsd.org Subject: Re: Multi Head XFree86 VGA card recomendations wanted In-reply-to: Your message of "Thu, 16 Dec 1999 10:59:12 GMT." <3858C600.41C6@cs.strath.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Dec 1999 15:43:41 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Reading the XFree86 docs, it seems almost all PCI cards are > supported multihead on Linux where they can issue an INT 10 > call to initialise the BIOS in the secondary card. > I'm not sure it we can support that in FreeBSD. We can. If you want to write the XFree86 code for it for FreeBSD, please let me know. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 17:36:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from w2xo.pgh.pa.us (ipl-229-010.npt-sdsl.stargate.net [208.223.229.10]) by hub.freebsd.org (Postfix) with ESMTP id D6897155B6 for ; Thu, 16 Dec 1999 17:36:42 -0800 (PST) (envelope-from durham@w2xo.pgh.pa.us) Received: from w2xo.pgh.pa.us (shazam.internal [192.168.5.3]) by w2xo.pgh.pa.us (8.9.3/8.9.3) with ESMTP id BAA12600 for ; Fri, 17 Dec 1999 01:36:41 GMT Message-ID: <385993A9.55086450@w2xo.pgh.pa.us> Date: Thu, 16 Dec 1999 20:36:41 -0500 From: Jim Durham Organization: dis- X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd hackers Subject: Resolv.conf question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I posted this to -questions, but didn't really get any answer that seemed to fit, so I thought I would ask here. On a 3.3-RELEASE box, not realizing at first that I didn't need an entry for the local nameserver, I had it's IP in as the first line in resolv.conf, followed by two more nameservers on the next two lines. Something in the daily scripts seemed to eliminate the first line, containing the local nameserver. I say this because the file date was 1:59am, the time that periodic/daily runs. I put it back every day, and the next day, it was gone again. I hunted quite a while in the scripts, but couldn't figure out what was doing this? Just for the sake of my curiosity, what was modifiying resolv.conf? Is this a security feature? Thanks, -- Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 17:40:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 7A8FC14E0D for ; Thu, 16 Dec 1999 17:40:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA03627; Thu, 16 Dec 1999 17:43:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912170143.RAA03627@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jim Durham Cc: freebsd hackers Subject: Re: Resolv.conf question In-reply-to: Your message of "Thu, 16 Dec 1999 20:36:41 EST." <385993A9.55086450@w2xo.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Dec 1999 17:43:45 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Something in the daily scripts seemed to eliminate the > first line, containing the local nameserver. I say this > because the file date was 1:59am, the time that periodic/daily > runs. I put it back every day, and the next day, it was gone again. > > I hunted quite a while in the scripts, but couldn't > figure out what was doing this? Nothing should. > Just for the sake of my curiosity, what was modifiying > resolv.conf? Is this a security feature? No idea. Are you running DHCP there by any chance? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 17:41:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 7A22215348 for ; Thu, 16 Dec 1999 17:41:15 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id RAA17989; Thu, 16 Dec 1999 17:32:37 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id RAA00770; Thu, 16 Dec 1999 17:32:37 -0800 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA29227; Thu, 16 Dec 99 17:32:34 PST Message-Id: <38599305.EB69D41E@softweyr.com> Date: Thu, 16 Dec 1999 18:33:57 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Greg Lehey Cc: David Bein , FreeBSD Hackers Subject: Re: Solaris 2.7 ufs file systems ... References: <945005691/bein@sanity.mass.pyramid.com> <19991216110101.O48955@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > > [redirected to -hackers] > > On Sunday, 12 December 1999 at 8:34:51 -0500, David Bein wrote: > > Hi ... > > > > I have a PC with triple boot partitions setup, one of > > which is loaded with Solaris 2.7 (officially called version 7). > > I am wondering if anyone has any experience directly mounting ufs > > partitions which Solaris created. It should be pretty straight > > forward to come up with a modified ufs source to read them > > (much like ext2fs), but of course figuring out where Solaris > > keeps the partition tables needed to get at the slices within > > the partition is apparently a military secret. Can anyone > > offer any advice on how to go about this? > > You'll probably find more interested people on -hackers, so I've > redirected the message there. With NetBSD (1.3.3, 1.4, 1.4.1) and Solaris on SPARC hardware, it just works, so it must not be all that secret. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 17:56: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dns1.sports.gov.uk (dns1.sports.gov.uk [212.125.74.131]) by hub.freebsd.org (Postfix) with ESMTP id 39B7314D93 for ; Thu, 16 Dec 1999 17:56:06 -0800 (PST) (envelope-from ad@dns1.sports.gov.uk) Received: from ad (helo=localhost) by dns1.sports.gov.uk with local-esmtp (Exim 3.03 #1) id 11ymVU-0005mw-00; Fri, 17 Dec 1999 01:48:32 +0000 Date: Fri, 17 Dec 1999 01:48:32 +0000 (GMT) From: Andy Doran X-Sender: ad@dns1.sports.gov.uk To: David Bein Cc: FreeBSD Hackers Subject: Re: Solaris 2.7 ufs file systems ... In-Reply-To: <38599305.EB69D41E@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 I know little about all things Sun, but a quick grep in NetBSD-current reveals: sys/dev/sun/disklabel.h sys/arch/sparc/sparc/disksubr.c Could be what you're looking for. - ad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 20:57:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 7A06D15042 for ; Thu, 16 Dec 1999 20:57:38 -0800 (PST) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id VAA42138; Thu, 16 Dec 1999 21:57:37 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id VAA69562; Thu, 16 Dec 1999 21:57:37 -0700 (MST) (envelope-from jjreynold@home.com) From: John and Jennifer Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14425.49856.663134.482116@whale.home-net> Date: Thu, 16 Dec 1999 21:57:36 -0700 (MST) To: Mark Newton Subject: Re: anybody using tn-gw-nav to tunnel ssh through a proxy? In-Reply-To: <19991217083227.A3471@internode.com.au> References: <14425.10973.878258.39420@whale.home-net> <19991217083227.A3471@internode.com.au> X-Mailer: VM 6.73 under Emacs 20.4.1 Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Friday, December 17, Mark Newton wrote: ] > > > but upon trying to ssh from work to my box I get this error message: > > Local: Corrupted check bytes on input. > > tn-gw isn't 8-bit-clean; you'll need to patch it. Try something like > this: it creates a new tn-gw-> prompt command called "rawopen" which > gives you an 8-bit-clean link to whatever host/port you specify. When you say 8-bit-clean, what exactly does that mean? I've heard that phrase several times in the past N months, but don't honestly know what it implies. (I did a few searches in various places looking for the jargon, but came up dry) Is there anything that can be done on the FreeBSD to make this work, or anything to the tn-gw-nav program itself? I'm wondering why this whole charade works for Linux clients and others (their Makefile also suggests people have compiled it for Sun, AIX, and the bastard of them all, HP-UX) but not FreeBSD. What do we do differently? > ... and check with your IT security folks before running nos-tun > over it, won't you? :-) Of course ;-) Thank you for the reply. If I can get them to patch tn-gw, your patch will certainly help. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds jjreynold@home.com FreeBSD 3.4-RC. FreeBSD: The Power to Serve. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 21: 9:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from w2xo.pgh.pa.us (ipl-229-010.npt-sdsl.stargate.net [208.223.229.10]) by hub.freebsd.org (Postfix) with ESMTP id F326514A07; Thu, 16 Dec 1999 21:09:22 -0800 (PST) (envelope-from durham@w2xo.pgh.pa.us) Received: from w2xo.pgh.pa.us (shazam.internal [192.168.5.3]) by w2xo.pgh.pa.us (8.9.3/8.9.3) with ESMTP id FAA13327; Fri, 17 Dec 1999 05:09:21 GMT Message-ID: <3859C580.A4B9FAD8@w2xo.pgh.pa.us> Date: Fri, 17 Dec 1999 00:09:20 -0500 From: Jim Durham Organization: dis- X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: freebsd hackers Subject: Re: Resolv.conf question References: <199912170143.RAA03627@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > > Something in the daily scripts seemed to eliminate the > > first line, containing the local nameserver. I say this > > because the file date was 1:59am, the time that periodic/daily > > runs. I put it back every day, and the next day, it was gone again. > > > > I hunted quite a while in the scripts, but couldn't > > figure out what was doing this? > > Nothing should. > > > Just for the sake of my curiosity, what was modifiying > > resolv.conf? Is this a security feature? > > No idea. Are you running DHCP there by any chance? > Nope. There's an NT box on the LAN doing DHCP. The 3.3 Box is a local server on a disconnected LAN talking to a "remote" server that spools mail, which is grabbed by fetchmail. We are running PPP on-demand to the external server via a dial-up to an ISP. However, PPP only holds the line up from 8am-8pm and this is happening at 1:59am, coinciding with the "periodic daily" scripts from crontab. Seemed wierd to me.. - Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 21:28:27 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 28F9314DBC for ; Thu, 16 Dec 1999 21:28:24 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id PAA04892; Fri, 17 Dec 1999 15:58:15 +1030 (CST) (envelope-from newton) Date: Fri, 17 Dec 1999 15:58:14 +1030 From: Mark Newton To: John and Jennifer Reynolds Cc: freebsd-hackers@freebsd.org Subject: Re: anybody using tn-gw-nav to tunnel ssh through a proxy? Message-ID: <19991217155814.A448@internode.com.au> References: <14425.10973.878258.39420@whale.home-net> <19991217083227.A3471@internode.com.au> <14425.49856.663134.482116@whale.home-net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <14425.49856.663134.482116@whale.home-net> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 09:57:36PM -0700, John and Jennifer Reynolds wrote: > > tn-gw isn't 8-bit-clean; you'll need to patch it. Try something like > > this: it creates a new tn-gw-> prompt command called "rawopen" which > > gives you an 8-bit-clean link to whatever host/port you specify. > > When you say 8-bit-clean, what exactly does that mean? Generally speaking it means that certain bytes don't get passed through correctly: You don't end up with a clear 8-bit-wide datapath between point A and point B unless you use special escaping mechanisms. Example: Some systems don't pass through the most-significant- bit of any data presented to them. So if you punch character code 283 (which is binary 100011011) in you'll get character code 27 (which is binary 000011011) out. fwtk isn't quite like that, but it's similar: tn-gw tries to do options spoofing, because it thinks it understands more about things like telnet echo enabling than the server at the other end. So, if you pass character code 255 (which introduces a telnet option) into it from the server side, you get basically nothing popping out at the client side. Meanwhile, you can get telnet options arriving at the client side with no prompting from the server whatsoever if tn-gw happens to think it's a good idea. This doesn't bother telnet one iota (after all, the bogus options are intended to make telnet work better), but it knocks other application layer protocols for six. Solution: Disable the options spoofing which tn-gw tries to do, which is precisely what the patch I posted does. > I'm wondering why this whole charade > works for Linux clients and others (their Makefile also suggests people have > compiled it for Sun, AIX, and the bastard of them all, HP-UX) but not > FreeBSD. What do we do differently? Incidentally, with my patch in place a whole raft of "punch this through the firewall" possiblities arrive. I wrote a proxy which went through a send-expect sequence to "plug-through" any arbitrary TCP port when I was forced to endure a tn-gw proxy with a previous employer; I can provide it (under a BSD-style license) if anyone is interested. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 22:40:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from virtual-voodoo.com (virtual-voodoo.com [204.120.165.254]) by hub.freebsd.org (Postfix) with ESMTP id 3752F14DB9 for ; Thu, 16 Dec 1999 22:40:44 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: (from steve@localhost) by virtual-voodoo.com (8.9.3/8.9.3) id BAA00321; Fri, 17 Dec 1999 01:40:37 -0500 (EST) (envelope-from steve) Date: Fri, 17 Dec 1999 01:40:37 -0500 (EST) From: Steve Ames Message-Id: <199912170640.BAA00321@virtual-voodoo.com> To: sos@freebsd.dk, steve@virtual-voodoo.com Subject: Re: ATA w/ today's -CURRENT Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <199912140736.IAA68617@freebsd.dk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Drives that report their capabilities right :) > > ad0: ATA-0 disk at ata0 as master > > ad0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S > > ad0: 16 secs/int, 1 depth queue, PIO > > ad1: ATA-0 disk at ata0 as slave > > ad1: 4134MB (8467200 sectors), 8960 cyls, 15 heads, 63 S/T, 512 B/S > > ad1: 16 secs/int, 1 depth queue, PIO > > Both reports "dont care" fields in the ata conformance field > thereby being set as ATA-0 disks. Since I've put in test > to only enable WDMA2 on at least ATA-2 disks and only enable > UDMA2 on at least ATA-3 disks, well your disks are not even > tried. You can change that in ata-disk.c by commenting out the > test for this, they look like: "ad_version(ap->versmajor) >= 2". That certainly fixed things (-CURRENT from about 1:30AM EST 12/17 with this check removed from the udma and wdma sections in ata-disk.c): ata0: master: success setting up WDMA2 mode on SiS chip ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 ad0: ATA-0 disk at ata0 as master ad0: 1554MB (3183264 sectors), 3158 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, DMA Creating DISK ad0 Creating DISK wd0 ata0: slave: success setting up WDMA2 mode on SiS chip ad1: piomode=4 dmamode=2 udmamode=-1 cblid=0 ad1: ATA-0 disk at ata0 as slave ad1: 4134MB (8467200 sectors), 8960 cyls, 15 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, DMA Creating DISK ad1 Creating DISK wd1 ata1-master: piomode=3 dmamode=1 udmamode=-1 dmaflag=1 acd0: CDROM drive at ata1 as master acd0: read 1033KB/s (1033KB/s), 256KB buffer, PIO acd0: Reads: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ata_command: timeout waiting for interrupt ^^^^^^^^^^^ Still getting this timeout though... -Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 23:24:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 4D0B515712; Thu, 16 Dec 1999 23:24:15 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA02698; Fri, 17 Dec 1999 02:23:46 -0500 Date: Fri, 17 Dec 1999 02:23:46 -0500 (EST) From: Mike Nowlin To: Jim Durham Cc: Mike Smith , freebsd hackers Subject: Re: Resolv.conf question In-Reply-To: <3859C580.A4B9FAD8@w2xo.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 > > > Just for the sake of my curiosity, what was modifiying > > > resolv.conf? Is this a security feature? Ran into a similar "what's changing this file?" problem a while ago -- fstat(1) is your friend... #!/bin/sh while true do fstat /etc/resolv.conf >> /fstatlogfile done Throw that into your crontab to start at 1:58 AM (right before the modification takes place), and be there to kill it at 2:00 (after the modification). It's ugly, it's far from perfect, and it might not catch really fast transitions, but it's been known to work... mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 16 23:24:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3647615174 for ; Thu, 16 Dec 1999 23:24:33 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA05293; Fri, 17 Dec 1999 08:24:21 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912170724.IAA05293@freebsd.dk> Subject: Re: ATA w/ today's -CURRENT In-Reply-To: <199912170640.BAA00321@virtual-voodoo.com> from Steve Ames at "Dec 17, 1999 01:40:37 am" To: steve@virtual-voodoo.com (Steve Ames) Date: Fri, 17 Dec 1999 08:24:21 +0100 (CET) Cc: freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Steve Ames wrote: > > > > Both reports "dont care" fields in the ata conformance field > > thereby being set as ATA-0 disks. Since I've put in test > > to only enable WDMA2 on at least ATA-2 disks and only enable > > UDMA2 on at least ATA-3 disks, well your disks are not even > > tried. You can change that in ata-disk.c by commenting out the > > test for this, they look like: "ad_version(ap->versmajor) >= 2". > > That certainly fixed things (-CURRENT from about 1:30AM EST 12/17 with > this check removed from the udma and wdma sections in ata-disk.c): Hmm, I've already weakend the tests here somewhat, but I still need to catch old drives, but apparently lots of disks doesn't report thier conformance level according to spec, bummer.... > ata_command: timeout waiting for interrupt > ^^^^^^^^^^^ Thats an aritifact from the ATAPI probes, it should be of no harm... -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 Dec 16 23:43:48 1999 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 2F73014E98 for ; Thu, 16 Dec 1999 23:43:46 -0800 (PST) (envelope-from imp@harmony.village.org) 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 AAA94685; Fri, 17 Dec 1999 00:43:44 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA78455; Fri, 17 Dec 1999 00:43:43 -0700 (MST) Message-Id: <199912170743.AAA78455@harmony.village.org> To: John and Jennifer Reynolds Subject: Re: anybody using tn-gw-nav to tunnel ssh through a proxy? Cc: Mark Newton , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Thu, 16 Dec 1999 21:57:36 MST." <14425.49856.663134.482116@whale.home-net> References: <14425.49856.663134.482116@whale.home-net> <14425.10973.878258.39420@whale.home-net> <19991217083227.A3471@internode.com.au> Date: Fri, 17 Dec 1999 00:43:43 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14425.49856.663134.482116@whale.home-net> John and Jennifer Reynolds writes: : When you say 8-bit-clean, what exactly does that mean? I've heard that phrase : several times in the past N months, but don't honestly know what it implies. : (I did a few searches in various places looking for the jargon, but came up dry) 8bit clean means that it doesn't use or molest the high order bit. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 0:26:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from urquell.pilsnet.sunet.se (urquell.pilsnet.sunet.se [192.36.125.77]) by hub.freebsd.org (Postfix) with ESMTP id CA71314FD1 for ; Fri, 17 Dec 1999 00:26:11 -0800 (PST) (envelope-from bd@urquell.pilsnet.sunet.se) Received: (from bd@localhost) by urquell.pilsnet.sunet.se (8.9.1/8.9.1) id JAA28076; Fri, 17 Dec 1999 09:25:56 +0100 (CET) (envelope-from bd) To: Jim Durham Cc: freebsd hackers Subject: Re: Resolv.conf question References: <199912170143.RAA03627@mass.cdrom.com> <3859C580.A4B9FAD8@w2xo.pgh.pa.us> From: Bjorn Danielsson Date: 17 Dec 1999 09:25:56 +0100 In-Reply-To: Jim Durham's message of "Fri, 17 Dec 1999 00:09:20 -0500" Message-ID: Lines: 17 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 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 Jim Durham wrote: > The 3.3 Box is a local server on a disconnected LAN talking > to a "remote" server that spools mail, which is grabbed by > fetchmail. We are running PPP on-demand to the external > server via a dial-up to an ISP. However, PPP only holds the > line up from 8am-8pm and this is happening at 1:59am, coinciding > with the "periodic daily" scripts from crontab. Try changing "netstat -i" to "netstat -ni" in the script /etc/periodic/daily/420.status-network Maybe the reverse dns lookup done by netstat -i tries to activate ppp which then wipes /etc/resolv.conf. Just a crazy idea... -- BjЖrn Danielsson KTHNOC / Swedish University Network (mail me for my real e-mail address) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 2: 6: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 81E781510B for ; Fri, 17 Dec 1999 02:05:33 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id MAA07270; Fri, 17 Dec 1999 12:04:13 +0200 (EET) (envelope-from ru) Date: Fri, 17 Dec 1999 12:04:13 +0200 From: Ruslan Ermilov To: Jim Durham Cc: freebsd hackers Subject: Re: Resolv.conf question Message-ID: <19991217120413.D76255@relay.ucb.crimea.ua> Mail-Followup-To: Jim Durham , freebsd hackers References: <385993A9.55086450@w2xo.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <385993A9.55086450@w2xo.pgh.pa.us>; from Jim Durham on Thu, Dec 16, 1999 at 08:36:41PM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 08:36:41PM -0500, Jim Durham wrote: > I posted this to -questions, but didn't really > get any answer that seemed to fit, so I thought > I would ask here. > > On a 3.3-RELEASE box, not realizing at first that > I didn't need an entry for the local nameserver, I > had it's IP in as the first line in resolv.conf, followed > by two more nameservers on the next two lines. > > Something in the daily scripts seemed to eliminate the > first line, containing the local nameserver. I say this > because the file date was 1:59am, the time that periodic/daily > runs. I put it back every day, and the next day, it was gone again. > > I hunted quite a while in the scripts, but couldn't > figure out what was doing this? > > Just for the sake of my curiosity, what was modifiying > resolv.conf? Is this a security feature? > Could be ppp(8). -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 3: 7:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (dialfwn01.fwn.rug.nl [129.125.32.151]) by hub.freebsd.org (Postfix) with ESMTP id 730AC150B3 for ; Fri, 17 Dec 1999 03:07:23 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id MAA22616; Fri, 17 Dec 1999 12:07:26 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Fri, 17 Dec 1999 12:07:25 +0100 (CET) From: Nick Hibma Reply-To: Nick Hibma To: Soren Schmidt Cc: Steve Ames , freebsd-hackers@FreeBSD.ORG Subject: Re: ATA w/ today's -CURRENT In-Reply-To: <199912170724.IAA05293@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > ata_command: timeout waiting for interrupt > > ^^^^^^^^^^^ > > Thats an aritifact from the ATAPI probes, it should be of no harm... In that case, is there some way of getting rid of the message? Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 3:10:11 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 593C115024 for ; Fri, 17 Dec 1999 03:10:09 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id MAA58068; Fri, 17 Dec 1999 12:09:58 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <199912171109.MAA58068@freebsd.dk> Subject: Re: ATA w/ today's -CURRENT In-Reply-To: from Nick Hibma at "Dec 17, 1999 12:07:25 pm" To: n_hibma@webweaving.org (Nick Hibma) Date: Fri, 17 Dec 1999 12:09:58 +0100 (CET) Cc: steve@virtual-voodoo.com (Steve Ames), freebsd-hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Nick Hibma wrote: > > > ata_command: timeout waiting for interrupt > > > ^^^^^^^^^^^ > > > > Thats an aritifact from the ATAPI probes, it should be of no harm... > > In that case, is there some way of getting rid of the message? Erhm well, I said harmless, but it indicates there is a problem with drive compliance.... -SЬren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 4: 0:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mailhub.psn.ie (mailhub.psn.ie [194.106.150.254]) by hub.freebsd.org (Postfix) with ESMTP id D5CA71510B for ; Fri, 17 Dec 1999 04:00:45 -0800 (PST) (envelope-from cillian@psn.ie) Received: from alto.internal ([192.168.0.254]) by mailhub.psn.ie with esmtp (Exim 2.12 #3) id 11yw0f-0008SM-00; Fri, 17 Dec 1999 11:57:21 +0000 Received: from cillian (helo=localhost) by alto.internal with local-esmtp (Exim 2.12 #1) id 11yw0f-0006LE-00; Fri, 17 Dec 1999 11:57:21 +0000 Date: Fri, 17 Dec 1999 11:57:21 +0000 (GMT) From: Cillian Sharkey X-Sender: cillian@alto.internal To: Andy Doran Cc: Matthew Dillon , hackers@FreeBSD.ORG Subject: Re: Strange problem with NFS 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 > > Looks like a firewall to me. Either a firewall in a router > > sitting between the hosts, or an ipfw setup sitting on one or the > > other host. > > I set up the NFS server in question ages ago. I haven't looked at the > problem, but... The server does use ipfw. The broken client is on the same > subnet as the working ones and nothing in the server's ipfw ruleset refers > directly to the broken client. I can confirm this. The 1st 3 ipfw rules on server : 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 02000 allow ip from 192.168.0.0/24 to 192.168.0.0/24 via fxp0 (192.168.0.0/24 is subnet both client and server are on and fxp0 is internal NIC) there is no ipfw/ipfilter setup on the client, everything is open.. Cillian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 6:59:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from donhm.calcasieu.com (dread.austin.texas.net [206.127.24.91]) by hub.freebsd.org (Postfix) with ESMTP id 6983415758; Fri, 17 Dec 1999 06:59:03 -0800 (PST) (envelope-from dread@donhm.calcasieu.com) Received: (from dread@localhost) by donhm.calcasieu.com (8.9.3/8.9.3) id IAA01684; Fri, 17 Dec 1999 08:58:05 -0600 (CST) (envelope-from dread) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <3859C580.A4B9FAD8@w2xo.pgh.pa.us> Date: Fri, 17 Dec 1999 08:58:05 -0600 (CST) From: Don Read To: Jim Durham Subject: Re: Resolv.conf question Cc: freebsd hackers , Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Dec-99 Jim Durham wrote: > Mike Smith wrote: >> >> > Something in the daily scripts seemed to eliminate the >> > first line, containing the local nameserver. I say this >> > because the file date was 1:59am, the time that periodic/daily >> > runs. I put it back every day, and the next day, it was gone again. >> > >> > I hunted quite a while in the scripts, but couldn't >> > figure out what was doing this? >> >> Nothing should. >> >> > Just for the sake of my curiosity, what was modifiying >> > resolv.conf? Is this a security feature? >> >> No idea. Are you running DHCP there by any chance? >> > > Nope. There's an NT box on the LAN doing DHCP. > > The 3.3 Box is a local server on a disconnected LAN talking > to a "remote" server that spools mail, which is grabbed by > fetchmail. We are running PPP on-demand to the external > server via a dial-up to an ISP. However, PPP only holds the > line up from 8am-8pm and this is happening at 1:59am, coinciding > with the "periodic daily" scripts from crontab. > to mail the output of the periodic; sendmail is pulling up ppp > Seemed wierd to me.. me too. Regards, -- Don Read dread@calcasieu.com EDP Manager dread@texas.net Calcasieu Lumber Co. Austin TX -- No Coffee No Peace To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 7: 8:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 608) id 0F25514F01; Fri, 17 Dec 1999 07:08:44 -0800 (PST) From: "Jonathan M. Bresler" To: sos@freebsd.dk Cc: n_hibma@webweaving.org, steve@virtual-voodoo.com, freebsd-hackers@FreeBSD.ORG In-reply-to: <199912171109.MAA58068@freebsd.dk> (message from Soren Schmidt on Fri, 17 Dec 1999 12:09:58 +0100 (CET)) Subject: Re: ATA w/ today's -CURRENT Message-Id: <19991217150844.0F25514F01@hub.freebsd.org> Date: Fri, 17 Dec 1999 07:08:44 -0800 (PST) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Nick Hibma wrote: > > > > ata_command: timeout waiting for interrupt > > > > ^^^^^^^^^^^ > > > > > > Thats an aritifact from the ATAPI probes, it should be of no harm... > > > > In that case, is there some way of getting rid of the message? > > Erhm well, I said harmless, but it indicates there is a problem with > drive compliance.... perhaps change the message to indicate that the drive is non-compliant. as it appears now, it seems to say that there it a problem that may affect the user. how about: "timeout waiting for interrupt, non-compliant drive, compensating". ;) jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 8:19:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.geocrawler.com (sourceforge.net [209.81.8.17]) by hub.freebsd.org (Postfix) with ESMTP id 9431914CD4 for ; Fri, 17 Dec 1999 08:19:55 -0800 (PST) (envelope-from nobody@www.geocrawler.com) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id IAA26603; Fri, 17 Dec 1999 08:19:57 -0800 Date: Fri, 17 Dec 1999 08:19:57 -0800 Message-Id: <199912171619.IAA26603@www.geocrawler.com> To: freebsd-hackers@freebsd.org Subject: Upper <->Lower in shell script From: "Alex" Reply-To: "Alex" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Alex" Be sure to reply to that address. Hello, I need in my shell script change upper case to lower case for characters. Cureently , I call c programm from script which do it. Is anybody did this inside script? Thank you Alex Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 8:22:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 7834614DF1 for ; Fri, 17 Dec 1999 08:22:53 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id KAA44348; Fri, 17 Dec 1999 10:22:47 -0600 (CST) (envelope-from dan) Date: Fri, 17 Dec 1999 10:22:47 -0600 From: Dan Nelson To: Alex Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Upper <->Lower in shell script Message-ID: <19991217102247.A43333@dan.emsphone.com> References: <199912171619.IAA26603@www.geocrawler.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912171619.IAA26603@www.geocrawler.com>; from "Alex" on Fri Dec 17 08:19:57 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Dec 17), Alex said: > I need in my shell script change upper case to lower case for > characters. Cureently , I call c programm from script which do it. Is > anybody did this inside script? #!/bin/sh var=MixedCase lvar=`echo $var | tr A-Z a-z` echo $lvar #!/usr/local/bin/zsh var=MixedCase lvar=${var:l} echo $lvar -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 8:25: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 217ED14E9F for ; Fri, 17 Dec 1999 08:25:00 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMW00GC389JNU@mta4.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Fri, 17 Dec 1999 10:24:56 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id KAA02846; Fri, 17 Dec 1999 10:27:36 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Fri, 17 Dec 1999 10:27:35 -0600 From: Chris Costello Subject: Re: Upper <->Lower in shell script In-reply-to: <199912171619.IAA26603@www.geocrawler.com> To: Alex Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991217102735.E523@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <199912171619.IAA26603@www.geocrawler.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999, Alex wrote: > I need in my shell script change upper case to > lower case for characters. Cureently , I call c > programm from script which do it. > Is anybody did this inside script? Shells such as ksh (both PDKSH and AT&T KSH, available in ports, support this) and bash have a typeset command. To convert something to all upper-case is surprisingly easy: typeset -u variable Example: $ typeset -u f $ f=abc $ echo $f ABC -- |Chris Costello |Beware of programmers who carry screwdrivers. - Leonard Brandwein `------------------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 8:25:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 0D85615789 for ; Fri, 17 Dec 1999 08:25:40 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMW00E7O8AP49@mta1.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Fri, 17 Dec 1999 10:25:38 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id KAA02869; Fri, 17 Dec 1999 10:28:18 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Fri, 17 Dec 1999 10:28:18 -0600 From: Chris Costello Subject: Re: Upper <->Lower in shell script In-reply-to: <199912171619.IAA26603@www.geocrawler.com> To: Alex Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991217102818.F523@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <199912171619.IAA26603@www.geocrawler.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 17, 1999, Alex wrote: > I need in my shell script change upper case to > lower case for characters. Cureently , I call c > programm from script which do it. > Is anybody did this inside script? Oops. That should be typeset -l. $ typeset -l var $ var=ABC $ echo $var abc -- |Chris Costello |Random access is the optimum of the mass storages. `-------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 8:28:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from maybe.csap.af.mil (mudd.csap.af.mil [192.203.1.250]) by hub.freebsd.org (Postfix) with SMTP id 4E30C15752 for ; Fri, 17 Dec 1999 08:28:30 -0800 (PST) (envelope-from leopold@mailcenter.csap.af.mil) Received: from raider.csap.af.mil(really [192.168.70.17]) by maybe.csap.af.mil via sendmail with esmtp id for ; Fri, 17 Dec 1999 10:28:29 -0600 (CST) (Smail-3.2 1996-Jul-4 #5 built 1999-Sep-4) Content-Length: 785 X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 17 Dec 1999 10:28:00 -0600 (CST) From: Corey Leopold To: freebsd-hackers@freebsd.org Subject: IPFW Question Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hi, We have a situation where we would like to drop packets based on the IP datagram length. I was wondering if this was possible with ipfw, and if not, how hard would this functionality be to implement into it. Thanks in advance... Corey - ---------------------------------- Corey Leopold E-Mail: Corey Leopold Phone (210)-925-3459 - ---------------------------------- -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQCVAwUBOFpWgD3+cS8MmLXZAQHVPQQAqvSZkGoJSpmDPnKkxESgNNqHWbtwkIum G5Vff+7GANvoBzCjw5oD6q1+6IdSnHh5ZjssCq8z0OAyCg9nvO3KnS3dpjtfGCWC wcSjZV/gOdxXlMtF8tp5TIce1WFJADP8L4s/7qp+VuYxXfr5Msoc8qtw72grwrzG o9TwK2bE+Bk= =T410 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 8:28:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 28E961579B for ; Fri, 17 Dec 1999 08:28:39 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.092 #1) id 11z09W-000DIV-00; Fri, 17 Dec 1999 16:22:46 +0000 Date: Fri, 17 Dec 1999 16:22:46 +0000 From: Ben Smithurst To: Jim Durham Cc: freebsd hackers Subject: Re: Resolv.conf question Message-ID: <19991217162246.A3076@strontium.scientia.demon.co.uk> References: <385993A9.55086450@w2xo.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <385993A9.55086450@w2xo.pgh.pa.us> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jim Durham wrote: > Something in the daily scripts seemed to eliminate the > first line, containing the local nameserver. I say this > because the file date was 1:59am, the time that periodic/daily > runs. I put it back every day, and the next day, it was gone again. > > I hunted quite a while in the scripts, but couldn't > figure out what was doing this? Are you running ppp (user, not kernel pppd)? I think it will modify /etc/resolv.conf if you specify ``enable dns'', but I'm not too sure (check the source if you want). -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 9:38:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.nobell.com (ns.nobell.com [216.140.184.2]) by hub.freebsd.org (Postfix) with ESMTP id 3C0E415006; Fri, 17 Dec 1999 09:38:27 -0800 (PST) (envelope-from aaron@nobell.com) Received: from WIN2K1 (st84042.nobell.com [216.140.184.42]) by ns.nobell.com (8.9.3/8.9.3) with SMTP id LAA55143; Fri, 17 Dec 1999 11:38:15 -0600 (CST) (envelope-from aaron@nobell.com) From: "Aaron Sonntag" To: "Freebsd Hackers" , "Freebsd-Hardware" Subject: PRO/100+ DUAL PORT SERVER ADAPTER Date: Fri, 17 Dec 1999 11:38:57 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Importance: Normal Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anybody have positive experience with this adapter? I will be using it in a router box. PRO/100+ DUAL PORT SERVER ADAPTER Thank you, Aaron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 9:44:35 1999 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 540201571B; Fri, 17 Dec 1999 09:44:32 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 703AB1C2B; Fri, 17 Dec 1999 12:44:10 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 6CA66381B; Fri, 17 Dec 1999 12:44:10 -0500 (EST) Date: Fri, 17 Dec 1999 12:44:10 -0500 (EST) From: Bill Fumerola To: Aaron Sonntag Cc: Freebsd Hackers , Freebsd-Hardware Subject: Re: PRO/100+ DUAL PORT SERVER ADAPTER 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 Fri, 17 Dec 1999, Aaron Sonntag wrote: > Anybody have positive experience with this adapter? > I will be using it in a router box. > > PRO/100+ DUAL PORT SERVER ADAPTER pcib3: at device 10.0 on pci2 pci3: on pcib3 fxp0: irq 10 at device 4.0 on pci3 fxp0: Ethernet address 00:90:27:2a:65:3e fxp1: irq 10 at device 5.0 on pci3 fxp1: Ethernet address 00:90:27:2a:65:3f Works perfectly over here. FreeBSD hawk.internal.chc-chimes.com 4.0-CURRENT FreeBSD 4.0-CURRENT #9: Mon Dec 13 22:07:08 EST 1999 billf@hawk.internal.chc-chimes.com:/usr/src/sys/compile/LOVEMACHINE i386 -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.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 Fri Dec 17 11:41:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from c62443-a.frmt1.sfba.home.com (c62443-a.frmt1.sfba.home.com [24.0.69.165]) by hub.freebsd.org (Postfix) with ESMTP id 605E0157B9 for ; Fri, 17 Dec 1999 11:41:16 -0800 (PST) (envelope-from adsharma@c62443-a.frmt1.sfba.home.com) Received: (from adsharma@localhost) by c62443-a.frmt1.sfba.home.com (8.9.3/8.9.3) id LAA25185; Fri, 17 Dec 1999 11:41:15 -0800 Date: Fri, 17 Dec 1999 11:41:15 -0800 From: Arun Sharma Message-Id: <199912171941.LAA25185@c62443-a.frmt1.sfba.home.com> To: hackers@freebsd.org Subject: Re: Per CPU timekeeping for SMP In-Reply-To: <19991205222423.A1391@sharmas.dhs.org> References: <19991205222423.A1391@sharmas.dhs.org> Reply-To: adsharma@sharmas.dhs.org.nospam Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Arun Sharma wrote: > > > Here's a reimplementation of my earlier per cpu time keeping patch > on SMP. The attached patch is against a 11/20/99 -current that I > cvsup'ed. Did anyone get a chance to review this ? Is everyone busy or sending patches to -hackers is frowned upon ? Or is this something that people aren't so excited about ? > 4. I've gotten sysctls working for sys_time - > > $ sysctl -A | grep kern.stats > kern.stats.systime.user: 25150 > kern.stats.systime.nice: 3878 > kern.stats.systime.sys: 14071 > kern.stats.systime.intr: 7395 > kern.stats.systime.idle: 5326029 > > I'm working on generating the per cpu sysctls. I've completed this work now. Here's the output of the new sysctl on my dual cpu box: $ sysctl -A | grep kern.stats kern.stats.systime.user: 13710 kern.stats.systime.nice: 552 kern.stats.systime.sys: 4296 kern.stats.systime.intr: 2602 kern.stats.systime.idle: 1878764 kern.stats.cpu.user.0: 7082 kern.stats.cpu.user.1: 7169 kern.stats.cpu.nice.0: 9 kern.stats.cpu.nice.1: 2 kern.stats.cpu.sys.0: 2120 kern.stats.cpu.sys.1: 2177 kern.stats.cpu.intr.0: 1309 kern.stats.cpu.intr.1: 1293 kern.stats.cpu.idle.0: 939407 kern.stats.cpu.idle.1: 939358 I have also figured out how to dynamically register sysctl nodes. The trick is to basically malloc a sysctl_oid and fill in the right fields and calling sysctl_register_oid. The code is in a kernel module available from: http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz It really needs to go into the base kernel. Also, I think sysctl_register_long and its yet to be written friends (register_int) etc, need to go into kern_sysctl - so that others can reuse the code to dynamically create sysctl nodes. I really don't want to spend my time on getting xosview and ktop to use these patches until I'm convinced that this code is going into the kernel. Again, the patches may not be perfect. But if people can review it I'll fix any issues. Also, Alpha guys need to make minor changes to keep things working. -Arun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 12: 2:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 24C1E157CE for ; Fri, 17 Dec 1999 12:02:44 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00708; Fri, 17 Dec 1999 12:06:12 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912172006.MAA00708@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Alex" Cc: freebsd-hackers@freebsd.org Subject: Re: Upper <->Lower in shell script In-reply-to: Your message of "Fri, 17 Dec 1999 08:19:57 PST." <199912171619.IAA26603@www.geocrawler.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Dec 1999 12:06:12 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This message was sent from Geocrawler.com by "Alex" > Be sure to reply to that address. > > Hello, > > I need in my shell script change upper case to > lower case for characters. Cureently , I call c > programm from script which do it. > Is anybody did this inside script? tr A-Z a-z -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 13: 9:12 1999 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 CEE4E14C93 for ; Fri, 17 Dec 1999 13:09:10 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA58486 for ; Fri, 17 Dec 1999 13:09:04 -0800 (PST) Date: Fri, 17 Dec 1999 13:09:03 -0800 (PST) From: Julian Elischer To: hackers@freebsd.org Subject: aout gdb in 3.x 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 How does one compile a version of GDB that can read a.out files? I know there is a way of doing it but I have totoally failed to work out how to do so. Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 13:12: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 568DD14C93 for ; Fri, 17 Dec 1999 13:12:03 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA17308; Fri, 17 Dec 1999 16:11:51 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <199912171941.LAA25185@c62443-a.frmt1.sfba.home.com> References: <19991205222423.A1391@sharmas.dhs.org> <199912171941.LAA25185@c62443-a.frmt1.sfba.home.com> Date: Fri, 17 Dec 1999 16:17:36 -0500 To: adsharma@sharmas.dhs.org, hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: Per CPU timekeeping for SMP Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:41 AM -0800 12/17/99, Arun Sharma wrote: >Arun Sharma wrote: > > > > > > Here's a reimplementation of my earlier per cpu time keeping patch > > on SMP. The attached patch is against a 11/20/99 -current that I > > cvsup'ed. > >Did anyone get a chance to review this ? Is everyone busy or sending >patches to -hackers is frowned upon ? Or is this something that >people aren't so excited about ? Probably need to send this to -current instead of -hackers. Also, pick a subject that says something about "patches for review". Also note that people are in the middle of pushing out the 3.4-release, so they might not have time to read all of the articles in hackers right now. I'm interested in the idea of per-CPU timekeeping, but at the moment I don't have a 4.x-current system setup, so I can't try this... I know I've seen others ask for detail at the per-CPU level, although I obviously don't know if your patch does exactly what they were asking for. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 14:24: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 415D314E56; Fri, 17 Dec 1999 14:24:01 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id E641E2DC07; Fri, 17 Dec 1999 23:24:37 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 7EF1B7811; Fri, 17 Dec 1999 23:23:22 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 74EAE10E10; Fri, 17 Dec 1999 23:23:22 +0100 (CET) Date: Fri, 17 Dec 1999 23:23:22 +0100 (CET) From: Andrzej Bialecki To: adsharma@sharmas.dhs.org.nospam Cc: hackers@freebsd.org, msmith@freebsd.org Subject: Dynamic sysctls (Re: Per CPU timekeeping for SMP) In-Reply-To: <199912171941.LAA25185@c62443-a.frmt1.sfba.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 On Fri, 17 Dec 1999, Arun Sharma wrote: > I have also figured out how to dynamically register sysctl nodes. > The trick is to basically malloc a sysctl_oid and fill in the right > fields and calling sysctl_register_oid. The code is in a kernel > module available from: > > http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz > > It really needs to go into the base kernel. Also, I think > sysctl_register_long and its yet to be written friends (register_int) > etc, need to go into kern_sysctl - so that others can reuse the code > to dynamically create sysctl nodes. I was thinking exactly about the same, and I was going to implement them myself... IMO these patches should go to the tree - without them the work that Mike Smith put into sysctl infrastructure is much less useful for average Joe Kernel Hacker... Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 14:32:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id D41C11514D; Fri, 17 Dec 1999 14:32:42 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id DED231CA0; Sat, 18 Dec 1999 06:32:23 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrzej Bialecki Cc: adsharma@sharmas.dhs.org, hackers@freebsd.org, msmith@freebsd.org Subject: Re: Dynamic sysctls (Re: Per CPU timekeeping for SMP) In-Reply-To: Message from Andrzej Bialecki of "Fri, 17 Dec 1999 23:23:22 +0100." Date: Sat, 18 Dec 1999 06:32:23 +0800 From: Peter Wemm Message-Id: <19991217223223.DED231CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On Fri, 17 Dec 1999, Arun Sharma wrote: > > > I have also figured out how to dynamically register sysctl nodes. > > The trick is to basically malloc a sysctl_oid and fill in the right > > fields and calling sysctl_register_oid. The code is in a kernel > > module available from: > > > > http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz > > > > It really needs to go into the base kernel. Also, I think > > sysctl_register_long and its yet to be written friends (register_int) > > etc, need to go into kern_sysctl - so that others can reuse the code > > to dynamically create sysctl nodes. > > I was thinking exactly about the same, and I was going to implement them > myself... IMO these patches should go to the tree - without them the work > that Mike Smith put into sysctl infrastructure is much less useful for > average Joe Kernel Hacker... Err.. That was Doug Rabson (dfr) who fixed the sysctl stuff to finish making it dynamic. sysctl_register_xxx() are wrappers around sysctl_register_oid(), but I guess it's ok to make some helper functions to make the existing functionality to make it easier to use. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 14:49: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 6CADE14DEA; Fri, 17 Dec 1999 14:48:59 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 438892DC07; Fri, 17 Dec 1999 23:49:37 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id DF4B47811; Fri, 17 Dec 1999 23:49:31 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id D2B4610E10; Fri, 17 Dec 1999 23:49:31 +0100 (CET) Date: Fri, 17 Dec 1999 23:49:31 +0100 (CET) From: Andrzej Bialecki To: Peter Wemm Cc: adsharma@sharmas.dhs.org, hackers@freebsd.org, msmith@freebsd.org Subject: Re: Dynamic sysctls (Re: Per CPU timekeeping for SMP) In-Reply-To: <19991217223223.DED231CA0@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Dec 1999, Peter Wemm wrote: > Andrzej Bialecki wrote: > > On Fri, 17 Dec 1999, Arun Sharma wrote: > > > > > I have also figured out how to dynamically register sysctl nodes. > > > The trick is to basically malloc a sysctl_oid and fill in the right > > > fields and calling sysctl_register_oid. The code is in a kernel > > > module available from: > > > > > > http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz > > > > > > It really needs to go into the base kernel. Also, I think > > > sysctl_register_long and its yet to be written friends (register_int) > > > etc, need to go into kern_sysctl - so that others can reuse the code > > > to dynamically create sysctl nodes. > > > > I was thinking exactly about the same, and I was going to implement them > > myself... IMO these patches should go to the tree - without them the work > > that Mike Smith put into sysctl infrastructure is much less useful for > > average Joe Kernel Hacker... > > Err.. That was Doug Rabson (dfr) who fixed the sysctl stuff to finish > making it dynamic. sysctl_register_xxx() are wrappers around > sysctl_register_oid(), but I guess it's ok to make some helper functions to > make the existing functionality to make it easier to use. Oh... My sincere apologies then for wrong attribution. Anyway, I think this stuff (although it may seem redundant to you) is very helpful. It takes some time to figure out how to untangle the SYSCTL_*, SLIST_*, DATA_SET and linker sets (which are not really indispensable here) to really learn how the dynamic sysctls work. These functions provide useful and handy shortcuts. IMHO, of course. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 16:30:37 1999 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 8A5121514D; Fri, 17 Dec 1999 16:30:32 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id TAA15979; Fri, 17 Dec 1999 19:29:30 -0500 (EST) Date: Fri, 17 Dec 1999 18:16:11 -0500 (EST) From: Zhihui Zhang To: Andrzej Bialecki Cc: adsharma@sharmas.dhs.org.nospam, hackers@FreeBSD.ORG, msmith@FreeBSD.ORG Subject: Re: Dynamic sysctls (Re: Per CPU timekeeping for SMP) 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 Fri, 17 Dec 1999, Andrzej Bialecki wrote: > On Fri, 17 Dec 1999, Arun Sharma wrote: > > > I have also figured out how to dynamically register sysctl nodes. > > The trick is to basically malloc a sysctl_oid and fill in the right > > fields and calling sysctl_register_oid. The code is in a kernel > > module available from: > > > > http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz > > > > It really needs to go into the base kernel. Also, I think > > sysctl_register_long and its yet to be written friends (register_int) > > etc, need to go into kern_sysctl - so that others can reuse the code > > to dynamically create sysctl nodes. > Can this patch be applied to FreeBSD 3.3-Release? If so, is it difficult to do so? -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 17:39:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id BDACF14D6D for ; Fri, 17 Dec 1999 17:39:11 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA01139; Sat, 18 Dec 1999 12:08:33 +1030 (CST) Date: Sat, 18 Dec 1999 12:08:32 +1030 From: Greg Lehey To: Karl Denninger Cc: Wilko Bulte , Warner Losh , Soren Schmidt , freebsd-hackers@FreeBSD.ORG Subject: Re: ATAPI tape support - how to format? Message-ID: <19991218120832.A1108@freebie.lemis.com> References: <199912130738.IAA28004@freebsd.dk> <199912131731.KAA44607@harmony.village.org> <19991213192545.D636@yedi.iaf.nl> <19991213125520.A567@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991213125520.A567@Denninger.Net> 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 13 December 1999 at 12:55:20 -0600, Karl Denninger wrote: > > BTW, I have older HP DAT drives (4 & 8gb models) that have several YEARS > of active use on them, and other than using a cleaning tape when the front > panel "clean me" light flashes I've NEVER had ANY problem with them. This is in stark contrast with my experience. Which models? The 35480A DDS-1 drives I had had a life of about 8 months with daily backups. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 18:19:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id E58CB14E28 for ; Fri, 17 Dec 1999 18:19:47 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id UAA34473; Fri, 17 Dec 1999 20:19:10 -0600 (CST) Message-ID: <19991217201910.A34455@Denninger.Net> Date: Fri, 17 Dec 1999 20:19:10 -0600 From: Karl Denninger To: Greg Lehey Cc: Wilko Bulte , Warner Losh , Soren Schmidt , freebsd-hackers@FreeBSD.ORG Subject: Re: ATAPI tape support - how to format? References: <199912130738.IAA28004@freebsd.dk> <199912131731.KAA44607@harmony.village.org> <19991213192545.D636@yedi.iaf.nl> <19991213125520.A567@Denninger.Net> <19991218120832.A1108@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19991218120832.A1108@freebie.lemis.com>; from Greg Lehey on Sat, Dec 18, 1999 at 12:08:32PM +1030 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG C1533As, circa 1994. I have two of them and they are still working. They were in use at an *ISP* as primary backup devices for more than two years (read: had the shit beaten out of them nightly) until we outgrew them and went to Exabyte 8705s (which SUCKED reliability-wise, although they're better than the 8500s!). The final step was to go to two DLT IIIXTs (after that I have no idea; I don't run the place anymore) Their predecessors, two 35480As, were replaced ONLY for capacity reasons. As far as I know *those* are still working (I know where one of them is and its not broken) I've never had trouble with HP DAT drives. None whatsoever. -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! On Sat, Dec 18, 1999 at 12:08:32PM +1030, Greg Lehey wrote: > On Monday, 13 December 1999 at 12:55:20 -0600, Karl Denninger wrote: > > > > BTW, I have older HP DAT drives (4 & 8gb models) that have several YEARS > > of active use on them, and other than using a cleaning tape when the front > > panel "clean me" light flashes I've NEVER had ANY problem with them. > > This is in stark contrast with my experience. Which models? The > 35480A DDS-1 drives I had had a life of about 8 months with daily > backups. > > Greg > -- > Finger grog@lemis.com for PGP public key > See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 18:25:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 271DD14CCA for ; Fri, 17 Dec 1999 18:25:09 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id MAA01548; Sat, 18 Dec 1999 12:54:42 +1030 (CST) Date: Sat, 18 Dec 1999 12:54:42 +1030 From: Greg Lehey To: Karl Denninger Cc: Wilko Bulte , Warner Losh , Soren Schmidt , freebsd-hackers@FreeBSD.ORG Subject: Tape reliability (was: ATAPI tape support - how to format?) Message-ID: <19991218125441.C1108@freebie.lemis.com> References: <199912130738.IAA28004@freebsd.dk> <199912131731.KAA44607@harmony.village.org> <19991213192545.D636@yedi.iaf.nl> <19991213125520.A567@Denninger.Net> <19991218120832.A1108@freebie.lemis.com> <19991217201910.A34455@Denninger.Net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991217201910.A34455@Denninger.Net> 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Friday, 17 December 1999 at 20:19:10 -0600, Karl Denninger wrote: > On Sat, Dec 18, 1999 at 12:08:32PM +1030, Greg Lehey wrote: >> On Monday, 13 December 1999 at 12:55:20 -0600, Karl Denninger wrote: >>> >>> BTW, I have older HP DAT drives (4 & 8gb models) that have several YEARS >>> of active use on them, and other than using a cleaning tape when the front >>> panel "clean me" light flashes I've NEVER had ANY problem with them. >> >> This is in stark contrast with my experience. Which models? The >> 35480A DDS-1 drives I had had a life of about 8 months with daily >> backups. > > C1533As, circa 1994. I have two of them and they are still working. I had one of them. In fact I still do, and it didn't fail on me; it got damaged in transit instead, and I never got it repaired. > They were in use at an *ISP* as primary backup devices for more than > two years (read: had the shit beaten out of them nightly) until we > outgrew them and went to Exabyte 8705s (which SUCKED > reliability-wise, although they're better than the 8500s!). I've never used an 8700. My 8505XL still seems to be working, the 8500 before it wore out. > The final step was to go to two DLT IIIXTs (after that I have no > idea; I don't run the place anymore) I'm having trouble with a Quantum DLT4000 right now, but it looks like a compatibility problem. > Their predecessors, two 35480As, were replaced ONLY for capacity reasons. > As far as I know *those* are still working (I know where one of them is and > its not broken) > > I've never had trouble with HP DAT drives. None whatsoever. Amazing. I certainly had your share of the trouble as well. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 18:39: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from Genesis.Denninger.Net (209-176-244-82.inil.com [209.176.244.82]) by hub.freebsd.org (Postfix) with ESMTP id 8BC6514CCA for ; Fri, 17 Dec 1999 18:39:06 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id UAA34620; Fri, 17 Dec 1999 20:38:46 -0600 (CST) Message-ID: <19991217203846.A34611@Denninger.Net> Date: Fri, 17 Dec 1999 20:38:46 -0600 From: Karl Denninger To: Greg Lehey Cc: Wilko Bulte , Warner Losh , Soren Schmidt , freebsd-hackers@FreeBSD.ORG Subject: Re: Tape reliability (was: ATAPI tape support - how to format?) References: <199912130738.IAA28004@freebsd.dk> <199912131731.KAA44607@harmony.village.org> <19991213192545.D636@yedi.iaf.nl> <19991213125520.A567@Denninger.Net> <19991218120832.A1108@freebie.lemis.com> <19991217201910.A34455@Denninger.Net> <19991218125441.C1108@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19991218125441.C1108@freebie.lemis.com>; from Greg Lehey on Sat, Dec 18, 1999 at 12:54:42PM +1030 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers cheerfully broiled for supper and served with ketchup! Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999 at 12:54:42PM +1030, Greg Lehey wrote: > On Friday, 17 December 1999 at 20:19:10 -0600, Karl Denninger wrote: > > On Sat, Dec 18, 1999 at 12:08:32PM +1030, Greg Lehey wrote: > >> On Monday, 13 December 1999 at 12:55:20 -0600, Karl Denninger wrote: > >>> > >>> BTW, I have older HP DAT drives (4 & 8gb models) that have several YEARS > >>> of active use on them, and other than using a cleaning tape when the front > >>> panel "clean me" light flashes I've NEVER had ANY problem with them. > >> > >> This is in stark contrast with my experience. Which models? The > >> 35480A DDS-1 drives I had had a life of about 8 months with daily > >> backups. > > > > C1533As, circa 1994. I have two of them and they are still working. > > I had one of them. In fact I still do, and it didn't fail on me; it > got damaged in transit instead, and I never got it repaired. Ah. Well, they're good drives. I still have one in my production machine; its all original (still has a 9406 firmware stamp!) ;-) > > They were in use at an *ISP* as primary backup devices for more than > > two years (read: had the shit beaten out of them nightly) until we > > outgrew them and went to Exabyte 8705s (which SUCKED > > reliability-wise, although they're better than the 8500s!). > > I've never used an 8700. My 8505XL still seems to be working, the > 8500 before it wore out. I had 8505XLs too - they sucked badly as well. My luck with Exabytes has been somewhere between shit and worse. I could tell you horror stories from the early 90s on production machines that ate their tapes or worse, wrote tapes that couldn't be restored...... > > The final step was to go to two DLT IIIXTs (after that I have no > > idea; I don't run the place anymore) > > I'm having trouble with a Quantum DLT4000 right now, but it looks like > a compatibility problem. I still have the two IIIXTs - they're overkill for my network at the house but they work and the price was right. :-) > > Their predecessors, two 35480As, were replaced ONLY for capacity reasons. > > As far as I know *those* are still working (I know where one of them is and > > its not broken) > > > > I've never had trouble with HP DAT drives. None whatsoever. > > Amazing. I certainly had your share of the trouble as well. That's ok - I got your share of trouble with the Exabytes, so we're even ;-). -- -- Karl Denninger (karl@denninger.net) Web: http://childrens-justice.org Isn't it time we started putting KIDS first? See the above URL for a plan to do exactly that! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 20: 8:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from p.wl.vg (209-9-69-194.sdsl.cais.net [209.9.69.194]) by hub.freebsd.org (Postfix) with ESMTP id 9399515222; Fri, 17 Dec 1999 20:08:25 -0800 (PST) (envelope-from patrick@p.wl.vg) Received: (from patrick@localhost) by p.wl.vg (8.9.3/8.9.3) id XAA24609; Fri, 17 Dec 1999 23:08:00 -0500 (EST) (envelope-from patrick) Message-Id: <199912180408.XAA24609@p.wl.vg> Date: Fri, 17 Dec 1999 23:08:00 -0500 (EST) From: patrick@whetstonelogic.com Subject: Sun4c as Xterminal - Problems To: freebsd-current@freebsd.org, freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is a question that will test your memories! I'm trying to use a Sun ELC (sun4c) as an Xterminal on my FreeBSD system using Xkernel 2.0. I've used the old howto's from 1996 (Philippe Regnauld) as well as NetBSD diskless howto's to set this up. I've got it working up to a point: It finds it IP address via rarp loads the boot loader via tftp mounts it's root via nfs and boots the kernel. But then it freezes with the message: le0 at SBus slot 0 0xc00000 pri 5 bwtwo0 at SBus slot 3 0x0 pri 7 No bootparam server responding; still trying whoami: pmap_rmtcall status 0x5 Looking at a tcpdump, I see: 22:45:09.936573 sun.wl.vg.1023 > 209.9.69.0.sunrpc: udp 100 repeated frequently. From what I've seen in the mail archives, it's probably a networking issue, and several people asked about it in 1996. But I never found a solution in the archives, only questions. So, does anyone have a fix for this? Back in '96-97, Luigi Rizzo and Mike Smith (among others) seemed to be doing this, so I'm hoping someone still does. Patrick Gardella My setup: 4.0-CURRENT #2: Sun Dec 12 20:35:48 EST 1999 fxp0: flags=8943 mtu 1500 inet 209.9.69.194 netmask 0xffffffe0 broadcast 209.9.69.223 ether 00:90:27:cb:0f:32 media: autoselect (10baseT/UTP) status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 17 21: 0:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 91E2614D58; Fri, 17 Dec 1999 21:00:29 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id AAA50185; Sat, 18 Dec 1999 00:00:12 -0500 (EST) (envelope-from wollman) Date: Sat, 18 Dec 1999 00:00:12 -0500 (EST) From: Garrett Wollman Message-Id: <199912180500.AAA50185@khavrinen.lcs.mit.edu> To: Robert Watson Cc: cvs-committers@freebsd.org, hackers@freebsd.org Reply-To: wollman@lcs.mit.edu Group-Reply-To: wollman@lcs.mit.edu Subject: New victim.. er.. committer In-Reply-To: References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > although I actually live near Amherst, Massachusetts much of the > time. Anyone up for a Southern New England FreeBSD ftf gtg? I can host. If you think you might be interested, please reply privately. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 5:21:19 1999 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 9FC8A14EAC for ; Sat, 18 Dec 1999 05:21:17 -0800 (PST) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 18 Dec 1999 13:21:16 +0000 (GMT) To: patrick@whetstonelogic.com Cc: freebsd-hackers@freebsd.org, iedowse@maths.tcd.ie Subject: Re: Sun4c as Xterminal - Problems In-reply-to: Your message of "Fri, 17 Dec 1999 23:08:00 EST." <199912180408.XAA24609@p.wl.vg> Date: Sat, 18 Dec 1999 13:21:16 +0000 From: Ian Dowse Message-ID: <199912181321.aa26630@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912180408.XAA24609@p.wl.vg>, patrick@whetstonelogic.com writes: >I'm trying to use a Sun ELC (sun4c) as an Xterminal on my FreeBSD >system using Xkernel 2.0. I've used the old howto's from 1996 >(Philippe Regnauld) as well as NetBSD diskless howto's to set this up. >So, does anyone have a fix for this? Back in '96-97, Luigi Rizzo and >Mike Smith (among others) seemed to be doing this, so I'm hoping someone >still does. I think sometime around 3.0, the networking code in FreeBSD stopped responding to IP broadcasts where the 'zero' subnet broadcast address, which in your case is 209.9.69.0. We currently work around this on some 3.x machines by adding an alias address (which can be anything, even not in the same subnet) that has a broadcast address of our subnet zero address. Try something like: ifconfig fxp0 inet 10.0.0.1 netmask 0xffffffff broadcast 209.9.69.0 alias Maybe the old behaviour of responding to the subnet zero address should be available via a sysctl? Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 6:41:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 868C914EB3 for ; Sat, 18 Dec 1999 06:41:56 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id OAA84682; Sat, 18 Dec 1999 14:51:59 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 18 Dec 1999 14:51:59 +0000 (GMT) From: Doug Rabson To: Julian Elischer Cc: hackers@freebsd.org Subject: Re: aout gdb in 3.x 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 Fri, 17 Dec 1999, Julian Elischer wrote: > > How does one compile a version of GDB that can read a.out files? > I know there is a way of doing it but I have totoally failed to work > out how to do so. I think you can do this by changing src/gnu/usr.bin/binutils/gdb/Makefile. Change: CFLAGS += -DFREEBSD_ELF to set FREEBSD_AOUT instead. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 6:43:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1616114CAE; Sat, 18 Dec 1999 06:43:46 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id OAA85016; Sat, 18 Dec 1999 14:53:59 GMT (envelope-from dfr@nlsystems.com) Date: Sat, 18 Dec 1999 14:53:59 +0000 (GMT) From: Doug Rabson To: Zhihui Zhang Cc: Andrzej Bialecki , adsharma@sharmas.dhs.org.nospam.demon.co.uk, hackers@freebsd.org, msmith@freebsd.org Subject: Re: Dynamic sysctls (Re: Per CPU timekeeping for SMP) 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 Fri, 17 Dec 1999, Zhihui Zhang wrote: > > On Fri, 17 Dec 1999, Andrzej Bialecki wrote: > > > On Fri, 17 Dec 1999, Arun Sharma wrote: > > > > > I have also figured out how to dynamically register sysctl nodes. > > > The trick is to basically malloc a sysctl_oid and fill in the right > > > fields and calling sysctl_register_oid. The code is in a kernel > > > module available from: > > > > > > http://sharmas.dhs.org/~adsharma/projects/freebsd/sysctl.tar.gz > > > > > > It really needs to go into the base kernel. Also, I think > > > sysctl_register_long and its yet to be written friends (register_int) > > > etc, need to go into kern_sysctl - so that others can reuse the code > > > to dynamically create sysctl nodes. > > > > Can this patch be applied to FreeBSD 3.3-Release? If so, is it difficult > to do so? You would need to port the dynamic sysctl work first. In principle it isn't difficult but it affects quite a few files other than the core sysctl code itself. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 6:46:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from w2xo.pgh.pa.us (ipl-229-010.npt-sdsl.stargate.net [208.223.229.10]) by hub.freebsd.org (Postfix) with ESMTP id C457314DBC; Sat, 18 Dec 1999 06:46:38 -0800 (PST) (envelope-from durham@w2xo.pgh.pa.us) Received: from w2xo.pgh.pa.us (shazam.internal [192.168.5.3]) by w2xo.pgh.pa.us (8.9.3/8.9.3) with ESMTP id OAA21639; Sat, 18 Dec 1999 14:46:27 GMT Message-ID: <385B9E43.358F3DC@w2xo.pgh.pa.us> Date: Sat, 18 Dec 1999 09:46:27 -0500 From: Jim Durham Organization: dis- X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Andy Farkas , freebsd hackers , frebsd-questions@FreeBSD.ORG Subject: Re: Resolv.conf question References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andy Farkas wrote: > > On Fri, 17 Dec 1999, Jim Durham wrote: > > > The 3.3 Box is a local server on a disconnected LAN talking > > to a "remote" server that spools mail, which is grabbed by > > fetchmail. We are running PPP on-demand to the external > > server via a dial-up to an ISP. However, PPP only holds the > > line up from 8am-8pm and this is happening at 1:59am, coinciding > > with the "periodic daily" scripts from crontab. > > > > Seemed wierd to me.. > > "enable dns" in /etc/ppp/ppp.conf will cause ppp to fiddle with > resolv.conf everytime you connect (8am-8pm). Hello Andy, You were correct. One of the scripts in "periodic/daily" was tickling the tun0: interface, causing ppp to automatically connect to the ISP at 1:59am. Apparently, it was busy enough to stay up and not reconnect on the days when I checked the modification time of the /etc/resolv.conf file, so it fooled me by being 1:59m instead of 8am, when cron fires up the connection. I pulled the "enable dns" line out and all should be well now. It had me puzzled for sure. Thanks to you and all who replied. -- Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 9:15:10 1999 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 B543614CAA for ; Sat, 18 Dec 1999 09:15:08 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id MAA03024 for ; Sat, 18 Dec 1999 12:15:04 -0500 (EST) Date: Sat, 18 Dec 1999 11:01:42 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Register a KLD module 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 looked at the KLD examples and found out that they boils down to a DECLARE_MODULE() macro with the subsystem given as SI_SUB_DRIVERS. Is there any reason for using this particular SI_SUB_DRIVERS? I see another example at http://www.freebsd.org/~abial/ that uses SI_SUB_EXEC. Is this subsystem id really useful for KLDs? KLDs are loaded when we run the kldload command and the subsystem ids are sorted at boot time. Any help is appreciated. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 9:49: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id B0EA614E74 for ; Sat, 18 Dec 1999 09:48:59 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 448762DC0A; Sat, 18 Dec 1999 18:49:36 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 16AE87812; Sat, 18 Dec 1999 18:49:09 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 118B510E10; Sat, 18 Dec 1999 18:49:09 +0100 (CET) Date: Sat, 18 Dec 1999 18:49:09 +0100 (CET) From: Andrzej Bialecki To: Zhihui Zhang Cc: freebsd-hackers@freebsd.org Subject: Re: Register a KLD module 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 Sat, 18 Dec 1999, Zhihui Zhang wrote: > > I have looked at the KLD examples and found out that they boils down to a > DECLARE_MODULE() macro with the subsystem given as SI_SUB_DRIVERS. Is > there any reason for using this particular SI_SUB_DRIVERS? I see another > example at http://www.freebsd.org/~abial/ that uses SI_SUB_EXEC. > > Is this subsystem id really useful for KLDs? KLDs are loaded when we run > the kldload command and the subsystem ids are sorted at boot time. This is not quite true. The KLDs can be loaded by the bootloader. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 11: 1:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 78CF31507B for ; Sat, 18 Dec 1999 11:01:24 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 62A401CA0; Sun, 19 Dec 1999 03:01:21 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrzej Bialecki Cc: Zhihui Zhang , freebsd-hackers@freebsd.org Subject: Re: Register a KLD module In-Reply-To: Message from Andrzej Bialecki of "Sat, 18 Dec 1999 18:49:09 +0100." Date: Sun, 19 Dec 1999 03:01:21 +0800 From: Peter Wemm Message-Id: <19991218190121.62A401CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On Sat, 18 Dec 1999, Zhihui Zhang wrote: > > > > > I have looked at the KLD examples and found out that they boils down to a > > DECLARE_MODULE() macro with the subsystem given as SI_SUB_DRIVERS. Is > > there any reason for using this particular SI_SUB_DRIVERS? I see another > > example at http://www.freebsd.org/~abial/ that uses SI_SUB_EXEC. > > > > Is this subsystem id really useful for KLDs? KLDs are loaded when we run > > the kldload command and the subsystem ids are sorted at boot time. > > This is not quite true. The KLDs can be loaded by the bootloader. > > Andrzej Bialecki And DECLARE_MODULE() is a primary method of initializing things in the static kernel binaries too. For device driver modules it doesn't matter much, but should be done at the same time as the others so that a complete device driver set is available before probing begins. Drivers that are added after probing cause a reprobe to happen/ Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 11:42: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 8527714DA2 for ; Sat, 18 Dec 1999 11:41:58 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id NAA68434 for hackers@freebsd.org; Sat, 18 Dec 1999 13:44:59 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199912181944.NAA68434@celery.dragondata.com> Subject: Practical limit for number of TCP connections? To: hackers@freebsd.org Date: Sat, 18 Dec 1999 13:44:59 -0600 (CST) X-Mailer: ELM [version 2.5 PL1] 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've started a side project that I'm trying to figure out how to scale. The end result will be a test-based realtime chat (IRC, java, or otherwise) that will bring very large crowds. You wouldn't believe how many geeks will show up on IRC for a TV/Movie star.... even lessor known ones. I've found that a poorly advertised event with a not-so-famous actress can draw 3-5 thousand people, easily. If I'm able to make this grow, I'm sure that number will go much higher. What's the practical number of TCP connections per server? Is there an easy guideline for how ram the kernel will be taking per connection/route/socket/fd/etc? My next interview will be Sunday, but to a much smaller audience than normal, so I'll be able to do some experimenting. Can anyone recommend specific things to watch for, wrt limits and memory use? I'll be watching vmstat carefully, at least. Thanks, Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 12:17:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from java.dpcsys.com (java.dpcsys.com [206.16.184.7]) by hub.freebsd.org (Postfix) with ESMTP id 5C20D14C84 for ; Sat, 18 Dec 1999 12:17:35 -0800 (PST) (envelope-from dan@dpcsys.com) Received: from localhost (dan@localhost) by java.dpcsys.com (8.9.1a/8.9.1) with SMTP id MAA02373; Sat, 18 Dec 1999 12:15:29 -0800 (PST) Date: Sat, 18 Dec 1999 12:15:29 -0800 (PST) From: Dan Busarow To: Ian Dowse Cc: patrick@whetstonelogic.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Sun4c as Xterminal - Problems In-Reply-To: <199912181321.aa26630@salmon.maths.tcd.ie> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Dec 1999, Ian Dowse wrote: > In message <199912180408.XAA24609@p.wl.vg>, patrick@whetstonelogic.com writes: > >I'm trying to use a Sun ELC (sun4c) as an Xterminal on my FreeBSD > >system using Xkernel 2.0. I've used the old howto's from 1996 > >(Philippe Regnauld) as well as NetBSD diskless howto's to set this up. > > >So, does anyone have a fix for this? Back in '96-97, Luigi Rizzo and > >Mike Smith (among others) seemed to be doing this, so I'm hoping someone > >still does. > > I think sometime around 3.0, the networking code in FreeBSD stopped > responding to IP broadcasts where the 'zero' subnet broadcast address, > which in your case is 209.9.69.0. Earlier than that. 2.2.5? It prevents the machine from being used as part of a smurf amplifier. If you want to change the behaviour see icmp_bmcastecho="NO" # respond to broadcast ping packets in rc.conf If you do turn it on make sujre your firewall or router are blocking pings to your broadcast address. Dan -- Dan Busarow 949 443 4172 Dana Point Communications, Inc. dan@dpcsys.com Dana Point, California 83 09 EF 59 E0 11 89 B4 8D 09 DB FD E1 DD 0C 82 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 12:28: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 13FF914EB4 for ; Sat, 18 Dec 1999 12:27:58 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost [127.0.0.1]) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id PAA91020; Sat, 18 Dec 1999 15:26:36 -0500 (EST) (envelope-from green@FreeBSD.org) Date: Sat, 18 Dec 1999 15:26:35 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Steve Ames Cc: freebsd-hackers@FreeBSD.org Subject: Re: ATA w/ today's -CURRENT In-Reply-To: <199912132310.SAA00352@virtual-voodoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Dec 1999, Steve Ames wrote: > Hrm... no question that the ATA driver is better today, but its still > not reporting DMA on my Quantum bigfoot drive (which should support DMA: > http://www.quantum.com/products/archive/bigfoot_cy/bigfoot_cy_features.htm) > > The Maxtor is pretty old (But its been current since 3.0 :) but may > still have some DMA support? (ftp://ftp.maxtor.com/pub/ide/71626ap.txt) I have this drive lying in the general few-foot radius of my computer. It's... well, problematic, to say the least, if trying to use it as a slave on ata1 where ata-pci0 (ALi) ---- ata0 --- ad0: ATA-4 (16 s/i, 1 dq, UDMA33) \ `-- acd0: (PIO) `-- ata1 --- ad1: ATA-4 (ditto ad0) `-- ad2: ATA-0 (16, 1, PIO) I get these messages and very goofy access to ad1: Dec 15 19:08:06 green /kernel: Mounting root from ufs:/dev/ad0s1a Dec 15 19:08:06 green /kernel: ad1: ad_timeout: lost disk contact - resetting Dec 15 19:08:06 green /kernel: ata1: resetting devices .. done Dec 15 19:08:06 green /kernel: ad1: ad_timeout: lost disk contact - resetting Dec 15 19:08:06 green /kernel: ata1: resetting devices .. done Dec 15 19:08:06 green /kernel: ad1: ad_timeout: lost disk contact - resetting Dec 15 19:08:06 green /kernel: ata1: resetting devices .. done Dec 15 19:08:06 green /kernel: ad1: ad_timeout: lost disk contact - resetting Dec 15 19:08:06 green /kernel: ad1: ad_timeout: trying fallback to PIO mode Dec 15 19:08:06 green /kernel: ata1: resetting devices .. done (rc continues here) So ad1 runs in PIO, and mount may or may not have successfully gotten ad1 mount entries up. > > What am I missing? > Something possibly close to what I am :/ That 71626 seems strange. > -Steve -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 12:34: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 4D4B414EBC for ; Sat, 18 Dec 1999 12:34:00 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id HAA03687; Sun, 19 Dec 1999 07:03:54 +1030 (CST) Date: Sun, 19 Dec 1999 07:03:54 +1030 From: Greg Lehey To: Doug Rabson Cc: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: aout gdb in 3.x Message-ID: <19991219070354.H815@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: 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 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 18 December 1999 at 14:51:59 +0000, Doug Rabson wrote: > On Fri, 17 Dec 1999, Julian Elischer wrote: > >> >> How does one compile a version of GDB that can read a.out files? >> I know there is a way of doing it but I have totoally failed to work >> out how to do so. > > I think you can do this by changing src/gnu/usr.bin/binutils/gdb/Makefile. > Change: > > CFLAGS += -DFREEBSD_ELF > > to set FREEBSD_AOUT instead. I thought it used to be possible for gdb to recognize multiple formats. Is this no longer the case? 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 Dec 18 12:41:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id D27E314D1C for ; Sat, 18 Dec 1999 12:41:19 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id MAA42831; Sat, 18 Dec 1999 12:41:07 -0800 (PST) To: Kevin Day Cc: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sat, 18 Dec 1999 13:44:59 -0600. <199912181944.NAA68434@celery.dragondata.com> Date: Sat, 18 Dec 1999 12:41:07 -0800 Message-ID: <42829.945549667@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912181944.NAA68434@celery.dragondata.com>, you wrote: >What's the practical number of TCP connections per server? I've gotten over 8,000 at one time on one FreeBSD box. >Is there an easy guideline for how {much} ram the kernel will be taking per >connection/route/socket/fd/etc? Not that I am aware of. The biggest memory issue for a box that's handling a lot of TCP con- nections at a time is the socket I/O buffer sizes. Unless you take steps, programatically, to reduce these, you will get (I think) one 4KB buffer for input and another 4KB buffer for output. This is for EACH active TCP connection. This can add up to a substantial amount of memory if you have a lot of connections. The way to solve that is to include calls to setsockopt() in your server that will have the effect of reducing the per-connection I/O buffer sizes just after you accept() each new connection. Quite a lot of memory (either virtual or real) will also get sucked up *if* you have a separate and independent process handling each separate connection. A simple experiment I did awhile back indicated that on recent-vintage versions of FreeBSD, the absolute minimum per-process overhead was 12KB. That is a *minimum*, e.g. for a process that contains essentially no code and no data. But you will probably never see that in practice, which is to say your minimum per-process overhead is going to be bigger than that. If this part of the equation (i.e. per-process overhead) causes you grief (as it did in my case) then you might consider writing your server as a sort of multi-user monitor sort-of thing, i.e. a single process that will service multiple connections. (That's what I did.) There are _potentially_ a couple of ways of doing this, but at the present time, and with current FreeBSD kernels, you probably don't have a lot of choice, and I think there's only one way of doing it. The _clean_ way of doing it would be to write your multi-user server using threads, and to assign one thread to each connection. If you can do that, then the logic in the program becomes quite simple. Each thread just sits there, blocked on a call to read(), until something comes in, and then it just parses the command, does whatever it is supposed to do in response to that command, and then goes back to the read() again. But as I understand it, there is not yet sufficient threads support in the FreeBSD kernel to make this work well/properly. (I may perhaps be misinformed about that, but that's what I have been told anyway.) The other way is just have your server be a single thread/process, and to have it keep one big list of all of the connections (i.e. socket fds) that it has open at present. Then it just executes mail loop, over and over again. At the top of the main look is one big honkin' call to select() in which you find out which of your connections is ready to be read or written. Then you go off and read/write those as appropriate, and then just come back and do the big select() again. (You could do this using calls to poll() instead of calls to select(), and that might be a bit more efficient.) The only real problem with doing things this way is that you have to diddle some things to make sure the bit arrays that you pass to select() are big enough to handle the maximum number of connections you ever anticipate having to service/maintain at one time. Ideally, all you really have to do in order to get this to happen is to redefine the pre-processor symbol FD_SETSIZE to your max connections number before you include , but then your are stuck selecting some other compile-time fixed number (in place of the default 1024), and personally, I prefer to use a somewhat different approach that allows me to use a dynamic number, i.e. one I get from querying the kernel for the current hard limit on simultaneously open fds. >My next interview will be Sunday, but to a much smaller audience than >normal, so I'll be able to do some experimenting. Can anyone recommend >specific things to watch for, wrt limits and memory use? I'll be watching >vmstat carefully, at least. If you want a lot of connections, start by increasing the values of "maxusers" and NMBCLUSTERS in your kernel config file. Then build and install a new kernel. How much is enough for these parameters? Beats me. If you find that you are running out of resources, increase them some more and then try again. After installing your new kernel, you'll probably want to add commands like the following to your /etc/rc.local file: # Increase the max # of open files, systemwide /sbin/sysctl -w kern.maxfiles=16384 # Increase the max # of open sockets, systemwide (use only on older kernels) #/sbin/sysctl -w kern.somaxconn=16384 # Increase max # of open files per process /sbin/sysctl -w kern.maxfilesperproc=16384 Last but not least, make sure that whatever account your server will run under is associated with some login class (see /etc/login.conf) that has an appropriately high setting for openfiles-cur and/or openfiles-max. If you would like to see an example of a very simple multi-connection server that runs as a single process (written in C) as described above, let me know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 12:55:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 449CA14EBC for ; Sat, 18 Dec 1999 12:55:10 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id OAA42531; Sat, 18 Dec 1999 14:58:10 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199912182058.OAA42531@celery.dragondata.com> Subject: Re: Practical limit for number of TCP connections? To: rfg@monkeys.com (Ronald F. Guilmette) Date: Sat, 18 Dec 1999 14:58:09 -0600 (CST) Cc: toasty@dragondata.com (Kevin Day), hackers@FreeBSD.ORG In-Reply-To: <42829.945549667@monkeys.com> from "Ronald F. Guilmette" at Dec 18, 1999 12:41:07 PM X-Mailer: ELM [version 2.5 PL1] 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 Wow, thanks for such a detailed reply. :) > > > In message <199912181944.NAA68434@celery.dragondata.com>, you wrote: > > >What's the practical number of TCP connections per server? > > I've gotten over 8,000 at one time on one FreeBSD box. Yeah, best case, I've had several thousand myself, but not really doing anything. :) I'm going to try to come up with a test suite for this sorta thing, unless someone pipes in that it already exists. > The biggest memory issue for a box that's handling a lot of TCP con- > nections at a time is the socket I/O buffer sizes. Unless you take > steps, programatically, to reduce these, you will get (I think) one > 4KB buffer for input and another 4KB buffer for output. This is for > EACH active TCP connection. I hadn't considered this much buffering, but it makes sense. > > This can add up to a substantial amount of memory if you have a lot of > connections. > > The way to solve that is to include calls to setsockopt() in your server > that will have the effect of reducing the per-connection I/O buffer sizes > just after you accept() each new connection. Speaking of accepting... What's the upper limit on listen queues? Something around 64, correct? > > Quite a lot of memory (either virtual or real) will also get sucked up > *if* you have a separate and independent process handling each separate > connection. A simple experiment I did awhile back indicated that on > recent-vintage versions of FreeBSD, the absolute minimum per-process > overhead was 12KB. That is a *minimum*, e.g. for a process that contains > essentially no code and no data. But you will probably never see that in > practice, which is to say your minimum per-process overhead is going to > be bigger than that. Yeah, I don't plan on doing things the apache way. :) One process per client seems silly here, since nearly every client will be getting the exact same data. > The _clean_ way of doing it would be to write your multi-user server using > threads, and to assign one thread to each connection. If you can do that, > then the logic in the program becomes quite simple. Each thread just sits > there, blocked on a call to read(), until something comes in, and then it > just parses the command, does whatever it is supposed to do in response to > that command, and then goes back to the read() again. > > But as I understand it, there is not yet sufficient threads support in the > FreeBSD kernel to make this work well/properly. (I may perhaps be misinformed > about that, but that's what I have been told anyway.) I believe this is how ConferenceRoom works, so it seems ok, but I remember the comments that FreeBSD was their least preferred platform because of thread problems. > The other way is just have your server be a single thread/process, and to > have it keep one big list of all of the connections (i.e. socket fds) that > it has open at present. Then it just executes mail loop, over and over > again. At the top of the main look is one big honkin' call to select() > in which you find out which of your connections is ready to be read or > written. Then you go off and read/write those as appropriate, and then > just come back and do the big select() again. (You could do this using > calls to poll() instead of calls to select(), and that might be a bit > more efficient.) This is how traditional ircd's handle it, and how I was planning to. It seems the most efficient, especially since 99.999% of the clients will be receiving the same data, it'll make transmission pretty easy. > If you want a lot of connections, start by increasing the values of > "maxusers" and NMBCLUSTERS in your kernel config file. Then build and > install a new kernel. How much is enough for these parameters? Beats > me. If you find that you are running out of resources, increase them > some more and then try again. I really wish more of those options were dynamically tunable, instead of a magic formula that maxusers controls. :) Thanks again, Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 13:14:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 8254214E60 for ; Sat, 18 Dec 1999 13:14:34 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id NAA43035; Sat, 18 Dec 1999 13:14:25 -0800 (PST) To: Kevin Day Cc: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sat, 18 Dec 1999 14:58:09 -0600. <199912182058.OAA42531@celery.dragondata.com> Date: Sat, 18 Dec 1999 13:14:25 -0800 Message-ID: <43033.945551665@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912182058.OAA42531@celery.dragondata.com>, you wrote: >Speaking of accepting... What's the upper limit on listen queues? Something >around 64, correct? I don't know, but why do you ask? Do you have some reason to believe that the length of listen queues is going to be an issue? >> Quite a lot of memory (either virtual or real) will also get sucked up >> *if* you have a separate and independent process handling each separate >> connection. A simple experiment I did awhile back indicated that on >> recent-vintage versions of FreeBSD, the absolute minimum per-process >> overhead was 12KB. That is a *minimum*, e.g. for a process that contains >> essentially no code and no data. But you will probably never see that in >> practice, which is to say your minimum per-process overhead is going to >> be bigger than that. > >Yeah, I don't plan on doing things the apache way. :) One process per client >seems silly here, since nearly every client will be getting the exact same >data. I think that you mean that you don't plan on doing things the Sendmail way. (1/2 :-) Seriously, Sendmail forks a child for every connection... two actually, assuming that the client actually DOES SOMTHING (e.g. sending mail) and then that child/children hang around until the _client_ finishes what it is doing... which can sometimes take a long long time if the client itself is slow. But unless I'm mistaken... which I very well might be... apache just gets a request, services it, and that that it... That par- ticular instance of Apache then goes immediately back to the free servers pool. That's what I was told anyway. >> The _clean_ way of doing it would be to write your multi-user server using >> threads, and to assign one thread to each connection. If you can do that, >> then the logic in the program becomes quite simple. Each thread just sits >> there, blocked on a call to read(), until something comes in, and then it >> just parses the command, does whatever it is supposed to do in response to >> that command, and then goes back to the read() again. >> >> But as I understand it, there is not yet sufficient threads support in the >> FreeBSD kernel to make this work well/properly. (I may perhaps be misinform >ed >> about that, but that's what I have been told anyway.) > >I believe this is how ConferenceRoom works, so it seems ok, but I remember >the comments that FreeBSD was their least preferred platform because of >thread problems. Yes. As I say, my understanding is that FreeBSD still doesn't have real and/or complete thread support in the kernel. So if you have a multi-threaded application and one thread blocks (e.g. on I/O) then the whole thing is blocked. >> The other way is just have your server be a single thread/process, and to >> have it keep one big list of all of the connections (i.e. socket fds) that >> it has open at present. Then it just executes mail loop, over and over >> again. At the top of the main look is one big honkin' call to select() >> in which you find out which of your connections is ready to be read or >> written. Then you go off and read/write those as appropriate, and then >> just come back and do the big select() again. (You could do this using >> calls to poll() instead of calls to select(), and that might be a bit >> more efficient.) > >This is how traditional ircd's handle it, and how I was planning to. It >seems the most efficient, especially since 99.999% of the clients will be >receiving the same data, it'll make transmission pretty easy. Not really. To be safe, you really shouldn't just assume that you can just blast out the same output data to all of the connections at the same time. You really should check (using select() or poll()) to see which ones are actually and currently in a state where you _can_ write to them. Some may not be, in which case writing to them is a Bad Idea... either that data you write will be thrown away (if you set the socket to non-blocking mode) or else worse, your whole server will block on that one socket and the one call to write() or send(). >> If you want a lot of connections, start by increasing the values of >> "maxusers" and NMBCLUSTERS in your kernel config file. Then build and >> install a new kernel. How much is enough for these parameters? Beats >> me. If you find that you are running out of resources, increase them >> some more and then try again. > >I really wish more of those options were dynamically tunable, instead of a >magic formula that maxusers controls. :) I can only agree. The system I was running that had more than 8,000 connections open at a time in fact had only a small handful of ``users'', i.e. me and a few daemon processes, and the big server process I described. It therefore seemed kinda weird to have to set maxusers to something in excess of 200, and doing so probably caused a bunch of kernel tables to be a lot bigger than they really had to be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 14:20:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lily.ezo.net (lily.ezo.net [206.102.130.13]) by hub.freebsd.org (Postfix) with ESMTP id 1EA2914F37; Sat, 18 Dec 1999 14:20:11 -0800 (PST) (envelope-from jflowers@ezo.net) Received: from lily.ezo.net (jflowers@localhost.ezo.net [127.0.0.1]) by lily.ezo.net (8.8.7/8.8.7) with SMTP id RAA16950; Sat, 18 Dec 1999 17:19:29 -0500 (EST) Date: Sat, 18 Dec 1999 17:19:28 -0500 (EST) From: Jim Flowers To: freebsd-questions@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: Natd with Pmtu Discovery 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 Natd does not handle pmtu discovery well when the mtu for the interface it is using is changed, either manually or under program control, after natd is started. The following provides details of why, and a work-around. Problem ------- Gateway router with natd has erratic or poor TCP performance when the outbound (nat) interface is modified after startup or during startup subsequent to launcing natd from rc.network such as from scripts in /usr/local/etc/rc.d or /etc/rc.local. Analysis -------- 1. Natd learns the mtu value of its interface on startup from rc.network following ifconfig or DHCP initialization. 2. Skip startup from a startup script in /usr/local/etc/rc.d/skip.sh modifies the mtu value in the kernel interface structure. 3. On receiving a packet to transmit outbound, natd generates an icmp type 3 need-to-fragment packet back to the sending host using the value learned in paragraph 1. 4. The sending host retransmits using this size. The packet is still too large for the outbound interface to transmit. 5. If the sending host happens to be a WinNT with pmtu discovery enabled, paragraphs 3 and 4 are repeated until black hole discovery takes over, if enabled, or forever, if not enabled. The -dynamic flag does not cause natd to learn the new value when the interface mtu is modified. While this problem was discovered in gateways that use both skip and natd on the same interface, it has been confirmed that the problem exists any time the natd interface mtu is modified, either manually or during startup after the natd daemon has been started. Workaround ---------- This behavior can be avoided for the current autostart requirement by delaying the startup of natd until after the interface mtu is set by skip from skip.sh (such as placing the equivalent shell script line in /etc/rc.local). The program name, option flags and interface name will have to be given explicitly as these values from rc.conf are not available in rc.local. Correction ---------- The natd program should learn the modified value of the interface mtu before transmitting need-to-fragment messages. As this method of avoiding fragmentation is becoming more common (and is mandatory in IPV6) this would be a worthwhile modification. Wierd Note ---------- The problem does not appear to occur in 3 gateways that are bit-identical except that they are running unstripped binaries (identical, if stripped) of natd. Jim Flowers #4 ISP on C|NET, #1 in Ohio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 14:26:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 1B41F14D31 for ; Sat, 18 Dec 1999 14:26:28 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 8A7791CD0; Sun, 19 Dec 1999 06:04:24 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Kevin Day Cc: rfg@monkeys.com (Ronald F. Guilmette), hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-Reply-To: Message from Kevin Day of "Sat, 18 Dec 1999 14:58:09 CST." <199912182058.OAA42531@celery.dragondata.com> Date: Sun, 19 Dec 1999 06:04:24 +0800 From: Peter Wemm Message-Id: <19991218220424.8A7791CD0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Day wrote: > > In message <199912181944.NAA68434@celery.dragondata.com>, you wrote: > > > > >What's the practical number of TCP connections per server? > > > > I've gotten over 8,000 at one time on one FreeBSD box. I'm aware of boxes having been tested to ~100,000 connections if my memory serves correctly. I know there were problems going over 64k connections at one point due to a 16 bit reference counter in the routes. > > The way to solve that is to include calls to setsockopt() in your server > > that will have the effect of reducing the per-connection I/O buffer sizes > > just after you accept() each new connection. > > Speaking of accepting... What's the upper limit on listen queues? Something > around 64, correct? Tuneable: peter@overcee[6:00am]~src/sys/kern-244> sysctl kern.ipc.somaxconn kern.ipc.somaxconn: 128 Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 14:29:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from fremont.bolingbroke.com (adsl-216-102-90-210.dsl.snfc21.pacbell.net [216.102.90.210]) by hub.freebsd.org (Postfix) with ESMTP id F18CF14CCB for ; Sat, 18 Dec 1999 14:29:30 -0800 (PST) (envelope-from ken@bolingbroke.com) Received: from localhost (ken@localhost) by fremont.bolingbroke.com (Pro-8.9.3/Pro-8.9.3) with ESMTP id OAA02007; Sat, 18 Dec 1999 14:29:30 -0800 (PST) Date: Sat, 18 Dec 1999 14:29:30 -0800 (PST) From: Ken Bolingbroke X-Sender: ken@fremont.bolingbroke.com To: hackers@FreeBSD.ORG Cc: "Ronald F. Guilmette" Subject: Re: Practical limit for number of TCP connections? In-Reply-To: <42829.945549667@monkeys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Dec 1999, Ronald F. Guilmette wrote: > # Increase the max # of open sockets, systemwide (use only on older kernels) > #/sbin/sysctl -w kern.somaxconn=16384 Regarding the comment, "use only on older kernels", why only on older kernels? What classifies as an older kernel--pre-3.0? pre-3.3? If you don't use this on new kernels, is there an alternative or is it now dynamically allocated as I've seen rumored will happen? > If you would like to see an example of a very simple multi-connection server > that runs as a single process (written in C) as described above, let me know. I'd be very interested in seeing this, if you could post a URL perhaps? Thanks, Ken Bolingbroke hacker@bolingbroke.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 14:57:26 1999 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 5A45B14D7D for ; Sat, 18 Dec 1999 14:57:23 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id PAA12420; Sat, 18 Dec 1999 15:28:33 -0800 (PST) Date: Sat, 18 Dec 1999 15:28:33 -0800 (PST) From: Alfred Perlstein To: Kevin Day Cc: "Ronald F. Guilmette" , hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-Reply-To: <199912182058.OAA42531@celery.dragondata.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Dec 1999, Kevin Day wrote: > > The _clean_ way of doing it would be to write your multi-user server using > > threads, and to assign one thread to each connection. If you can do that, > > then the logic in the program becomes quite simple. Each thread just sits > > there, blocked on a call to read(), until something comes in, and then it > > just parses the command, does whatever it is supposed to do in response to > > that command, and then goes back to the read() again. > > > > But as I understand it, there is not yet sufficient threads support in the > > FreeBSD kernel to make this work well/properly. (I may perhaps be misinformed > > about that, but that's what I have been told anyway.) > > I believe this is how ConferenceRoom works, so it seems ok, but I remember > the comments that FreeBSD was their least preferred platform because of > thread problems. Using a thread per connection has always been a bogus way of programming, it's easy, but it doesn't work very well. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 15:31:30 1999 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 857C915028 for ; Sat, 18 Dec 1999 15:31:28 -0800 (PST) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 18 Dec 1999 23:31:27 +0000 (GMT) To: Dan Busarow Cc: patrick@whetstonelogic.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Sun4c as Xterminal - Problems In-reply-to: Your message of "Sat, 18 Dec 1999 12:15:29 PST." Date: Sat, 18 Dec 1999 23:31:27 +0000 From: Ian Dowse Message-ID: <199912182331.aa58316@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Dan Busa row writes: >Earlier than that. 2.2.5? It prevents the machine from being used >as part of a smurf amplifier. If you want to change the behaviour >see > >icmp_bmcastecho="NO" # respond to broadcast ping packets This is different; the change I was referring to stops FreeBSD from recognising old-style IP broadcasts as broadcasts. If you have a network 172.16.0.0/16, then 172.16.255.255 is accepted as a broadcast address, but 172.16.0.0 is not. Diskless Sun machines attempt to use the latter, so the broadcasts get ignored. The change is older than I thought though. The code was #ifdef'd out back in Dec 1995 in v1.33 of sys/netinet/ip_input.c, and was removed completely in v1.48 (Oct 1996). Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 15:41:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id EFCE614C9E for ; Sat, 18 Dec 1999 15:41:53 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id PAA43838; Sat, 18 Dec 1999 15:41:40 -0800 (PST) To: Ken Bolingbroke Cc: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sat, 18 Dec 1999 14:29:30 -0800. Date: Sat, 18 Dec 1999 15:41:40 -0800 Message-ID: <43836.945560500@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , you wrote: > > >On Sat, 18 Dec 1999, Ronald F. Guilmette wrote: > >> # Increase the max # of open sockets, systemwide (use only on older kernels) >> #/sbin/sysctl -w kern.somaxconn=16384 > >Regarding the comment, "use only on older kernels", why only on older >kernels? Ummm.... because newer kernels don't seem to have any such parameter. :-) >What classifies as an older kernel--pre-3.0? pre-3.3? Try executing the command: /sbin/sysctl -w kern.somaxconn=16384 as root. If it works, then you have an ``older'' kernel. If it doesn't, then you have a ``newer'' one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 15:44: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 1AFC514BE2 for ; Sat, 18 Dec 1999 15:43:59 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id PAA43947 for ; Sat, 18 Dec 1999 15:43:58 -0800 (PST) To: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sat, 18 Dec 1999 15:28:33 -0800. Date: Sat, 18 Dec 1999 15:43:58 -0800 Message-ID: <43945.945560638@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Alfred Perlstein wrote: >On Sat, 18 Dec 1999, Kevin Day wrote: > >> > The _clean_ way of doing it would be to write your multi-user server using >> > threads, and to assign one thread to each connection. If you can do that, >> > then the logic in the program becomes quite simple. Each thread just sits >> > there, blocked on a call to read(), until something comes in, and then it >> > just parses the command, does whatever it is supposed to do in response to >> > that command, and then goes back to the read() again. >> > >> > But as I understand it, there is not yet sufficient threads support in the >> > FreeBSD kernel to make this work well/properly. (I may perhaps be misinfo >rmed >> > about that, but that's what I have been told anyway.) >> >> I believe this is how ConferenceRoom works, so it seems ok, but I remember >> the comments that FreeBSD was their least preferred platform because of >> thread problems. > >Using a thread per connection has always been a bogus way of programming, >it's easy, but it doesn't work very well. OK, even if nobody else does, I'll bite. Why not? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 16:10:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles522.castles.com [208.214.165.86]) by hub.freebsd.org (Postfix) with ESMTP id B987414D31 for ; Sat, 18 Dec 1999 16:10:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA01313; Sat, 18 Dec 1999 16:13:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912190013.QAA01313@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ronald F. Guilmette" Cc: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of "Sat, 18 Dec 1999 15:43:58 PST." <43945.945560638@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Dec 1999 16:13:50 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Using a thread per connection has always been a bogus way of programming, > >it's easy, but it doesn't work very well. > > > OK, even if nobody else does, I'll bite. > > Why not? It scales poorly. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 17:21:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id F0A0A15155 for ; Sat, 18 Dec 1999 17:21:04 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id RAA44342; Sat, 18 Dec 1999 17:20:59 -0800 (PST) To: Ken Bolingbroke Cc: hackers@FreeBSD.ORG, lutz@iks-jena.de Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sat, 18 Dec 1999 14:29:30 -0800. Date: Sat, 18 Dec 1999 17:20:59 -0800 Message-ID: <44340.945566459@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Ken Bolingbroke wrote: >> If you would like to see an example of a very simple multi-connection server >> that runs as a single process (written in C) as described above, let me know >. > >I'd be very interested in seeing this, if you could post a URL perhaps? OK. Try this URL: ftp://ftp.e-scrub.com/pub/teergrube/sendmail-8.9.3-teergrube-patches.gz Fetch that file and then un-gzip it. Once you have done that, get a virgin set of Sendmail 8.9.3 sources, unpack them, cd to the root of the resulting directory, and then use un-gzipped file as a patchkit to patch the Sendmail sources. Then read the README.teergrube file which describes everything in great detail. (The part you are really looking for... the simple milti-connection daemon... is in the file tgd.c.) Basically, this patchkit adds a new (but very simple) daemon program to the Sendmail distribution. After applying the patches, and building Sendmail as you normally would, you will end up with both an executable for Sendmail and also an executable called `tgd'... the teergrubing daemon. (These will both get installed, e.g. into /usr/sbin) when/if you then install Sendmail as you normally would.) The code for the tgd daemon, in addition to being a simple demonstration of a single-process/multi-connection server daemon (as well as a nice simple demonstration of how to pass open file descriptors via UNIX domain sockets) also has a great deal of utilitarian value, especially if you happen to be one of the folks who, like myself, abhor all of the e-mail spam that seems to ceasely flow through the net's many remaining open and unsecured mail relays. Suffice it to say that if we could get a couple of hundred sites running this daemon, the current unsecured mail server hijacking problem on the net could be (and most likely would be) almost instantly reduced to per- haps 1/100th of its current size... not necessarily because all those remaining open relays would get properly closed/secured by their owners, but just because they would all suddenly become a lot less effective as spam conduits. Please see: http://www.iks-jena.de/mitarb/lutz/usenet/teergrube.en.html for a brief introduction to basic tactical teergrubing. (The tgd daemon takes this quite a bit further, into what I would call ``advanced hard-core strategic teergrubing''). In a nutshell, teergrubing is the name that has been given to a simple technique that exploits a small but significant known weakness of most SMTP client implementations. This weakness is exploited to either slow down or halt the flow of e-mail from some SMTP client to some SMTP server. Teergrubing has been employed for some time in the fight against e-mail spam on the net, but I believe that it would be fair to say that the Sendmail patchkit whose URL is given above, and the `tgd' daemon contained therein, takes the general strategy of teergrubing to a new level. Teergrubing has been approved for use throughout the Internet by the Coalition for Non-Violent Resistance (CNVR). Ideally, tgd, and the associated Sendmail patches, should be used in conjunction with some external list of the IP addresses of ``bad'' e-mail sources that are to be disiplined. In this context, ``bad'' E-mail sources are either mail servers belonging to known spammers or else unsecured open mail relays (that may be remotely hijacked by spammers) or both. Three such lists exist at the present time. They go by the names of ORBS, RSS, and MAPS RBL. (Most people have probably heard of the MAPS RBL by now.) The ORBS list is most agressive of the three. It lists essentially any and all open/unsecured mail relays that have been brought to its attention. For more info regarding the ORBS list see http://www.orbs.org/. The RSS list only lists open mail relays that have already been found and explioted by spammers to relay spam. For more information on the RSS list see http://www.orbs.org/. The MAPS RBL list primarily lists IP addresses associated with mail servers of known spammers, but also lists some open mail relays that have already been exploited. See http://www.mail-abuse.org/rbl/ for more information on the MAPS RBL. The patchkit mentioned above allows any one of these lists to be used to select which mail senders will be teergrubed. In addition, a locally- maintained list of ``bad'' e-mail sources may also be specified, in addition to one of the external lists just mentioned. One last word about the goals of teergrubing... It will in fact most likely NEVER be possible to get every last one of the morons who are still running open/unsecured mail servers to properly secure/ close those servers. Some, perhaps many, will merely upgrade to more recent version of their current mail server software... versions which include anti-teergrubing logic... and then just continue on running their servers as open/unsecured mail relays. That's OK. Those few can then be blocked individually, and eventually, there will be so few of them remaining that all the spammers will be fighting over those few remaining open servers, just like fish struck in an ever-shrinking pond as the dry season approaches. The real point, for now, is just to force everyone (or almost everyone) to upgrade to recent-vintage mail servers that at least give them the CHOICE of whether or not to fully disble relaying by outsiders. (Old mail servers don't provide such options, but almost all current releases of all popular mail servers now DO provide this as a configuration choice.) -- rfg P.P.S. Real-world experience with tgd indicates that that on the order of 1 out of every 200 mail servers which are teergrubed will result in a nasty phone call (or e-mail) from the relevant (cluless) system administrator claim- ing that YOU are spamming HIM, when in fact the exact opposite is what is actually occuring. In these cases, a calm and patient lesson, provided to the clueless sysadmin, on how to properly read and interpret the output of `netstat' almost always succeeds in converting initial hostility to expres- sions of gratitude. P.P.S. Experience also indicates that on the order of 1 out of every 1000 or so teergrubed mail servers will result in a nasty phone call (or e-mail) in which the operator of the mail server on the other end of the open connection(s) will attempt to assert that what YOU are doing (teergrubing) is, in some unspecified way, ``illegal''. In such cases, it is best not to waste time arguing this ridiculous point, but rather to simply assert that your mail server is indeed accepting mail from the other party's mail server, but that due to circumstances beyond your control, it is merely doing so extraordinarily slowly. :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 17:33:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1D14E14C1D for ; Sat, 18 Dec 1999 17:33:09 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA76536; Sat, 18 Dec 1999 17:33:08 -0800 (PST) (envelope-from dillon) Date: Sat, 18 Dec 1999 17:33:08 -0800 (PST) From: Matthew Dillon Message-Id: <199912190133.RAA76536@apollo.backplane.com> To: freebsd-hackers@freebsd.org Subject: Anybody know if there is any way to make ports use different work dir? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to get my /usr/ports over a read-only NFS mount. At the moment the only way I can compile up any given port is to mkdir work and create and mount an MFS filesystem over it. A union mount might also work but union mounts are still somewhat problematic. It would be nice if there were a way to tell the ports system to put the work directory somewhere other then where it is currently placed. For example, to put it in /usr/obj or something like that. Has anyone done this? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 17:41:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta3.rcsntx.swbell.net (mta3.rcsntx.swbell.net [151.164.30.27]) by hub.freebsd.org (Postfix) with ESMTP id 7AD1A15158 for ; Sat, 18 Dec 1999 17:41:12 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta3.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMY00GAQSOGA2@mta3.rcsntx.swbell.net> for freebsd-hackers@FreeBSD.ORG; Sat, 18 Dec 1999 19:41:04 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id TAA11225; Sat, 18 Dec 1999 19:43:38 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Sat, 18 Dec 1999 19:43:37 -0600 From: Chris Costello Subject: Re: Anybody know if there is any way to make ports use different work dir? In-reply-to: <199912190133.RAA76536@apollo.backplane.com> To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991218194337.M523@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <199912190133.RAA76536@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999, Matthew Dillon wrote: > It would be nice if there were a way to tell the ports system to put the > work directory somewhere other then where it is currently placed. For > example, to put it in /usr/obj or something like that. Has anyone done > this? The authors of bsd.port.mk have. Try this: $ cd /usr/ports/misc/rtfm $ WRKDIRPREFIX=/tmp DISTDIR=/tmp make >> rtfm-0.2.tar.gz doesn't seem to exist on this system. >> Attempting to fetch from http://www.freebsd.org/~chris/distfiles/. Receiving rtfm-0.2.tar.gz (4881 bytes): 100% 4881 bytes transferred in 0.1 seconds (48.25 Kbytes/s) ===> Extracting for rtfm-0.2 >> Checksum OK for rtfm-0.2.tar.gz. ===> Patching for rtfm-0.2 ===> Applying FreeBSD patches for rtfm-0.2 ===> Configuring for rtfm-0.2 ===> Building for rtfm-0.2 cc -o rtfm rtfm.c -O -pipe -Wall Simply set WRKDIRPREFIX and DISTDIR and nothing gets written to the ports directory. Obviously you could put this in /etc/make.conf and make it much easier on yourself. Note that you end up in this case with /tmp/usr/ports/misc/rtfm/work/rtfm-0.2/ that you get to rip out later. Additionally, a /tmp/rtfm-0.2.tar.gz is left behind. -- |Chris Costello |State-of-the-practice: What we can do with the money you have. `-------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 17:41:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id CE50114BE9 for ; Sat, 18 Dec 1999 17:41:31 -0800 (PST) (envelope-from sprice@hiwaay.net) Received: from localhost (sprice@localhost) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id TAA24880; Sat, 18 Dec 1999 19:41:23 -0600 (CST) Date: Sat, 18 Dec 1999 19:41:23 -0600 (CST) From: Steve Price To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Anybody know if there is any way to make ports use different work dir? In-Reply-To: <199912190133.RAA76536@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Dec 1999, Matthew Dillon wrote: # It would be nice if there were a way to tell the ports system to put the # work directory somewhere other then where it is currently placed. For # example, to put it in /usr/obj or something like that. Has anyone done # this? Try setting the value of WRKDIRPREFIX which is akin to MAKEOBJDIRPREFIX in bsd.obj.mk. -steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 18:23:54 1999 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 C38AF14E72 for ; Sat, 18 Dec 1999 18:23:52 -0800 (PST) (envelope-from dscheidt@enteract.com) 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 UAA11282; Sat, 18 Dec 1999 20:23:41 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Sat, 18 Dec 1999 20:23:41 -0600 (CST) From: David Scheidt To: "Ronald F. Guilmette" Cc: Ken Bolingbroke , hackers@FreeBSD.ORG, lutz@iks-jena.de Subject: Re: Practical limit for number of TCP connections? In-Reply-To: <44340.945566459@monkeys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Dec 1999, Ronald F. Guilmette wrote: > > In a nutshell, teergrubing is the name that has been given to a simple > technique that exploits a small but significant known weakness of most > SMTP client implementations. This weakness is exploited to either slow > down or halt the flow of e-mail from some SMTP client to some SMTP server. Think about it before you fire it up. You are essentially launching a DOS attack on somebody's mail server. In some jurisdictions, that's a felony. David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 18:30:12 1999 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 3282B15199 for ; Sat, 18 Dec 1999 18:30:11 -0800 (PST) (envelope-from dscheidt@enteract.com) 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 UAA11553; Sat, 18 Dec 1999 20:30:07 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Sat, 18 Dec 1999 20:30:07 -0600 (CST) From: David Scheidt To: "Ronald F. Guilmette" Cc: Ken Bolingbroke , hackers@FreeBSD.ORG, lutz@iks-jena.de Subject: Re: Practical limit for number of TCP connections? 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 Sat, 18 Dec 1999, David Scheidt wrote: > On Sat, 18 Dec 1999, Ronald F. Guilmette wrote: > > > > > In a nutshell, teergrubing is the name that has been given to a simple > > technique that exploits a small but significant known weakness of most > > SMTP client implementations. This weakness is exploited to either slow > > down or halt the flow of e-mail from some SMTP client to some SMTP server. > > Think about it before you fire it up. You are essentially launching a DOS > attack on somebody's mail server. In some jurisdictions, that's a felony. My mistake. I confused this with some of the other anti-spam measures. Being slow isn't criminal. (fortunatly for me!)_ David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 18:33:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 8C37814C08 for ; Sat, 18 Dec 1999 18:33:36 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id UAA48058; Sat, 18 Dec 1999 20:33:30 -0600 (CST) (envelope-from dan) Date: Sat, 18 Dec 1999 20:33:30 -0600 From: Dan Nelson To: Kevin Day Cc: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? Message-ID: <19991218203330.A47909@dan.emsphone.com> References: <199912181944.NAA68434@celery.dragondata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912181944.NAA68434@celery.dragondata.com>; from "Kevin Day" on Sat Dec 18 13:44:59 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Dec 18), Kevin Day said: > I've started a side project that I'm trying to figure out how to > scale. The end result will be a test-based realtime chat (IRC, java, > or otherwise) that will bring very large crowds. You wouldn't believe > how many geeks will show up on IRC for a TV/Movie star.... even > lessor known ones. > > I've found that a poorly advertised event with a not-so-famous > actress can draw 3-5 thousand people, easily. If I'm able to make > this grow, I'm sure that number will go much higher. > > What's the practical number of TCP connections per server? Is there > an easy guideline for how ram the kernel will be taking per > connection/route/socket/fd/etc? As a datapoint, the busiest IRC server in 1998 was irc.blackened.com, which peaked at around 8700 simultaneous connections (with a lot more traffic than you're likely to see). I forget whether it was running 2.2.7 or 3.0, but it was definitely FreeBSD, running a standard ircd. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 18:45:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 3D9451503C for ; Sat, 18 Dec 1999 18:45:12 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id SAA44827; Sat, 18 Dec 1999 18:45:08 -0800 (PST) To: David Scheidt Cc: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sat, 18 Dec 1999 20:23:41 -0600. Date: Sat, 18 Dec 1999 18:45:08 -0800 Message-ID: <44825.945571508@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , David Scheidt wrote: >On Sat, 18 Dec 1999, Ronald F. Guilmette wrote: > >> >> In a nutshell, teergrubing is the name that has been given to a simple >> technique that exploits a small but significant known weakness of most >> SMTP client implementations. This weakness is exploited to either slow >> down or halt the flow of e-mail from some SMTP client to some SMTP server. > >Think about it before you fire it up. You are essentially launching a DOS >attack on somebody's mail server. In some jurisdictions, that's a felony. That is just plain false. In fact it is more than false. It is silly. Why would you want to spread such a ridiculous rumor? Do you work for the DMA or something? The tgd daemon is an entirely defensive weapon... kinda like the old Regan-era Star Wars idea. It just sits there and does nothing until someone else attacks. If and when you _do_ start spamming my server, if I happen to be running the thing, all that happens is that you get stuck like a bug on flypaper. Next you'll be telling us that flypaper is against the laws that prohibit cruelty to animals. :-) Yea. Right. In which parallel Universe? P.S. What's so silly about this is that you got it entirely bass-ackwards. If *you* are sending *me* a ton of spam, it is *you* you might be prosecuted for having launced a Denial-Of-Service attack, not me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 20: 8:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id BD9C414A26 for ; Sat, 18 Dec 1999 20:08:55 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA45697; Sat, 18 Dec 1999 23:08:48 -0500 (EST) Message-Id: <199912190408.XAA45697@cs.rpi.edu> To: freebsd-hackers@freebsd.org Cc: crossd@cs.rpi.edu, perera@cs.rpi.edu Subject: NLM v4 (file locking and NFS v3) Date: Sat, 18 Dec 1999 23:08:48 -0500 From: "David E. Cross" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have come across a problem wrt to a network file lock manager. Consider the case of a lock on a local file, and a request from a remote machine to lock that same file. fcntl(fd, F_SETLK, &fl) will return immediately with EAGAIN (this is for an exclusive case, of course), F_SETLKW will block (even if O_NONBLOCK has been set, this is annoying even if documented behavior). The question then becomes how is a user process to tell when the lock has become available again? Neither select(), nor poll() seem to have the desired affect. A couple possibilities that have floated by are to have a select() with a 30 second timeout, at which point scan the entire lock pending list. Are there any other possibilities? Also, could we get the fhopen, fhstat, and fhstatfs calls MFC-ed? They appear to be straightforward calls that do not depend on any VFS changes in -CURRENT. Furthermore they are very special purpose, they only have the potential to destabilize the system (if there are any bugs in them) if a program calls them. As it stands I know of zero production programs that would call these [nonexistent] syscalls :) -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 20:10:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 05C5915186 for ; Sat, 18 Dec 1999 20:10:11 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA01049; Sat, 18 Dec 1999 20:10:10 -0800 (PST) (envelope-from dillon) Date: Sat, 18 Dec 1999 20:10:10 -0800 (PST) From: Matthew Dillon Message-Id: <199912190410.UAA01049@apollo.backplane.com> To: freebsd-hackers@FreeBSD.ORG Subject: Cool little 100BaseTX switch - they're coming down in price Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I picked up a nifty little D-Link DSS-5+ 5-port 10/100 switch today CompUSA had a 5-port network kit labeled 'DFE-910' which had the DSS-5+ and two DFE-530TX+ NIC Cards ('rl' driver), plus cables, for $130. It appears to operate quite nicely. I can run all 5 ports at 100BaseTX speeds in full-duplex mode and it seems to take whatever I throw at it, though I didn't life test it so I don't know what it can actually handle. It seems to have sufficient buffering to deal with fragmented NFS packets without losing anything so I'm happy. Prices have fallen a lot in the last year. I'm happy to be able to get rid of my HUBs, I was constantly having to deal with packet loss when running saturation tests and never able to figure out what was causing it. Note that buy.com lists a 'DFE-910' kit for around $100, but their description of it is that it contains a hub rather then a switch. I know what I got at CompUSA was a switch, not a hub, but I don't know what you'd get if you bought the DFE-910 part number from buy.com. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 20:31: 6 1999 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 67AB3151CC for ; Sat, 18 Dec 1999 20:31:04 -0800 (PST) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-117-168.bellatlantic.net [151.198.117.168]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id XAA04591; Sat, 18 Dec 1999 23:30:54 -0500 (EST) Message-ID: <385C60FC.7613CB55@bellatlantic.net> Date: Sat, 18 Dec 1999 23:37:16 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.0-980222-SNAP i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > I picked up a nifty little D-Link DSS-5+ 5-port 10/100 switch today > CompUSA had a 5-port network kit labeled 'DFE-910' which had the > DSS-5+ and two DFE-530TX+ NIC Cards ('rl' driver), plus cables, for $130. > > It appears to operate quite nicely. I can run all 5 ports at At work I've got experience with 32-port D-Link 10/100 switched hub. It works fine except that it hangs occasionally (can be reset by power-cycling). So we don't buy them any more. Also at my pre-previous employer we had small 8-port 10Mpbs hubs from D-Link and they had the same problem, so it seems to be a family problem. With about 20 hubs there was a hang approximately every other day. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 20:45: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DE56A1517A for ; Sat, 18 Dec 1999 20:45:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA01335; Sat, 18 Dec 1999 20:43:45 -0800 (PST) (envelope-from dillon) Date: Sat, 18 Dec 1999 20:43:45 -0800 (PST) From: Matthew Dillon Message-Id: <199912190443.UAA01335@apollo.backplane.com> To: Sergey Babkin Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :At work I've got experience with 32-port D-Link 10/100 switched :hub. It works fine except that it hangs occasionally (can be :reset by power-cycling). So we don't buy them any more. Also :at my pre-previous employer we had small 8-port 10Mpbs hubs from :D-Link and they had the same problem, so it seems to be a family :problem. With about 20 hubs there was a hang approximately every :other day. : :-SB Oh joy. Well, we'll see what happens with this one. I had a Sohoware superflex 10/100 hub and it hung nearly every day. I'm also testing out a linksys switch (I bought a D-Link switch and a LinkSys switch). Unfortunately the NIC cards that came with the LinkSys switch, as far as I can tell, are no longer supported in -current. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 21: 0:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 19E0114DEA for ; Sat, 18 Dec 1999 21:00:40 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id WAA23949; Sat, 18 Dec 1999 22:57:58 -0600 (CST) Date: Sat, 18 Dec 1999 22:57:58 -0600 From: Tim Tsai To: Sergey Babkin Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price Message-ID: <19991218225758.A23729@futuresouth.com> References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <385C60FC.7613CB55@bellatlantic.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hub. It works fine except that it hangs occasionally (can be > reset by power-cycling). Most of these can be attributed to the crappy wall wart they call a power supply. If it's plugged into an UPS or replace it with your own DC power supply they generally hold up a lot better. I have a Netgear FS108 at home (8 port 10/100 switch) and I've found Netgear stuff to be as cheap as I would go and still be reasonably reliable. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 21:57:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 85A2715153 for ; Sat, 18 Dec 1999 21:57:39 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id AAA08484; Sun, 19 Dec 1999 00:56:19 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199912190556.AAA08484@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tim Tsai Cc: Sergey Babkin , Matthew Dillon , freebsd-hackers@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <19991218225758.A23729@futuresouth.com> In-reply-to: Your message of "Sat, 18 Dec 1999 22:57:58 CST." <19991218225758.A23729@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Dec 1999 00:56:19 -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > hub. It works fine except that it hangs occasionally (can be > > reset by power-cycling). > > Most of these can be attributed to the crappy wall wart they call a > power supply. If it's plugged into an UPS or replace it with your own DC > power supply they generally hold up a lot better. > > I have a Netgear FS108 at home (8 port 10/100 switch) and I've found > Netgear stuff to be as cheap as I would go and still be reasonably > reliable. In the "don't do this at home" category, I have to relate a story regarding one of the Netgear FS108 switches. Recently, at my "day job" at UUNET, we moved into some new office space. I packed up all my stuff (including one of these FS108 switches) and put it all back together again in my new office space. I noticed a couple of things, first that my SGI LCD display panel wasn't working any more; I though the @$&*$ moves must have dropped it or something. The other thing was that when I powered up the FS108 ethernet swtich under my desk, that I immediately smelled that distinctive "hot electronic smell", followed by smoke (!) coming out of the FS108 box. Hmm.. So, I open up the case of the switch, and noticed that there's a *really* big chip with a *really* big heatsink attached -this is the "bridge on chip". And I noticed another, smaller IC which had a hole blown out of the epoxy case (which subsequently allowed the smoke to escape. It was than than I make the connection - Hmm.. SGI LCD monitor don't work. Ethernet switch makes smoke. Ethernet switch wants 5VDC power brick. SGI LCD monitor wants 12VDC power brick. Ooops! So, after switching power bricks, the SGI LCD monitor starts working again. It really wants 12V and not 5V. In a "what the hell" move, I powered up the ethernet Netgear Ethernet switch with it's preferred 5V power brick -- AND IT WORKS JUST FINE! Well mostly; I think the chip with the hole was involved in driving the Transmit/Collision LEDs which don't do anything anymore. But pushing packets through the box seems to work great; it's still doing the bridge thing of forwarding traffic to the right port, etc. So, please don't do this. I'm sure I'm just luckly. Hell, the thing might burst into flames one day. But I was sure impressed that I keept on working, even after the smoke got loose. Oh, and double check your power bricks before you plug them in. It would sure be nice if there were standard connections for each voltage, but that's certainly not the case.. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 18 22:17:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id A106B151EA for ; Sat, 18 Dec 1999 22:17:14 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id WAA10127; Sat, 18 Dec 1999 22:16:40 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id WAA09033; Sat, 18 Dec 1999 22:16:40 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA00198; Sat, 18 Dec 99 22:16:34 PST Message-Id: <385C789C.DD290597@softweyr.com> Date: Sat, 18 Dec 1999 23:18:04 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > I picked up a nifty little D-Link DSS-5+ 5-port 10/100 switch today > CompUSA had a 5-port network kit labeled 'DFE-910' which had the > DSS-5+ and two DFE-530TX+ NIC Cards ('rl' driver), plus cables, for $130. Warehouse.com sells the Netgear FS105 for $99.99. If you open them up, don't be surprised to see exactly the same chipset, and perhaps even the same board. You'd be astonished how many of these commodity items are OEM'd from the same vendor. I have a nice, shiny new 8-port 10/100 switch at work, with ATM-155 uplink, ATM T1/E1 Circuit emulation on the front, and AAL-1 inputs for bridging your PBX over the same DS3 or OC3 uplink circuit. It costs a bit more than $130, or at least it will when I get the IP routing software working. ;^) > It appears to operate quite nicely. I can run all 5 ports at > 100BaseTX speeds in full-duplex mode and it seems to take whatever > I throw at it, though I didn't life test it so I don't know what > it can actually handle. It seems to have sufficient buffering to > deal with fragmented NFS packets without losing anything so I'm happy. If you can spare it for a few days, I'll be glad to plug it into a SmartBits and tell you what it'll REALLY do. > Prices have fallen a lot in the last year. I'm happy to be able to > get rid of my HUBs, I was constantly having to deal with packet loss > when running saturation tests and never able to figure out what > was causing it. Switches are a better solution, no doubt about it. They are well worth the cost, even if you're just trying to pep up an old 10Base-T network. Investing in 10Base-T switches at this time is a false economy; for only a few dollars more per port you can get 10/100 switches like yours and upgrade machines to Fast Ethernet as budget allows. > Note that buy.com lists a 'DFE-910' kit for around $100, but their > description of it is that it contains a hub rather then a switch. I > know what I got at CompUSA was a switch, not a hub, but I don't know > what you'd get if you bought the DFE-910 part number from buy.com. Warehouse.com lists the D-Link DSS-5+ as a 5 port auto 10/100 desktop switch ext pwr (external power, I presume) for $109.99. I suspect that might be the same as what you got, despite the clash in product nomenclature. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 2:34:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 7AEE514D03 for ; Sun, 19 Dec 1999 02:34:15 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA78376; Sun, 19 Dec 1999 10:44:28 GMT (envelope-from dfr@nlsystems.com) Date: Sun, 19 Dec 1999 10:44:28 +0000 (GMT) From: Doug Rabson To: Greg Lehey Cc: Julian Elischer , hackers@FreeBSD.ORG Subject: Re: aout gdb in 3.x In-Reply-To: <19991219070354.H815@freebie.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 On Sun, 19 Dec 1999, Greg Lehey wrote: > On Saturday, 18 December 1999 at 14:51:59 +0000, Doug Rabson wrote: > > On Fri, 17 Dec 1999, Julian Elischer wrote: > > > >> > >> How does one compile a version of GDB that can read a.out files? > >> I know there is a way of doing it but I have totoally failed to work > >> out how to do so. > > > > I think you can do this by changing src/gnu/usr.bin/binutils/gdb/Makefile. > > Change: > > > > CFLAGS += -DFREEBSD_ELF > > > > to set FREEBSD_AOUT instead. > > I thought it used to be possible for gdb to recognize multiple > formats. Is this no longer the case? I think that most of gdb can cope with both a.out and elf. The main problem is the shared library support which has ifdefs all over it to cope with the differences between SunOS and SVR4 shared libs. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 3:56:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.pernet.net (mail.pernet.net [205.229.0.40]) by hub.freebsd.org (Postfix) with ESMTP id 8E3CE151D4 for ; Sun, 19 Dec 1999 03:56:14 -0800 (PST) (envelope-from jking@pernet.net) Received: from pernet.net (mail.pernet.net [205.229.0.40]) by mail.pernet.net (8.9.1a/8.9.1) with SMTP id FAA21939 for freebsd-hackers@freebsd.org; Sun, 19 Dec 1999 05:56:13 -0600 (CST) Date: Sun, 19 Dec 1999 05:56:13 -0600 (CST) Message-Id: <199912191156.FAA21939@mail.pernet.net> To: freebsd-hackers@freebsd.org Subject: XDM, KDM, PAM, FreeBSD, and a partridge in a pear tree... From: Rob King X-Mailer: TWIG 1.0.3 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Once again, I apologize for asking a question that is probably off-list, but... Here's the problem: I'm running a fresh install of 3.3-STABLE, and trying to get the nice graphical login, with either XDM or KDM. Unfortunantly, I get an 'incorrect password' error no matter what I type. I also get a "pam: no modules loaded for xdm service" or kdm service, depending. I have a line in my /etc/pam.conf: xdm auth required pam_unix.so try_first_pass Unfortunantly, no matter what happens, neither KDM nor XDM will recognize me. Any ideas, anyone? Thanks all, Rob -- Rob King System Administrator - PERnet Communications, Inc. jking@pernet.net - http://www.pernet.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 7:31:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id EE1C514D98 for ; Sun, 19 Dec 1999 07:31:13 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id QAA16783 for freebsd-hackers@freebsd.org; Sun, 19 Dec 1999 16:31:12 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id NAA27578 for freebsd-hackers@freebsd.org; Sun, 19 Dec 1999 13:45:38 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: Re: Cool little 100BaseTX switch - they're coming down in price Date: 19 Dec 1999 13:45:38 +0100 Message-ID: <83ik1i$qt6$1@bigeye.rhein-neckar.de> References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> Reply-To: freebsd-chat@freebsd.org To: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergey Babkin wrote: > At work I've got experience with 32-port D-Link 10/100 switched > hub. It works fine except that it hangs occasionally (can be > reset by power-cycling). So we don't buy them any more. Also > at my pre-previous employer we had small 8-port 10Mpbs hubs from > D-Link and they had the same problem, so it seems to be a family > problem. I have a D-Link DSH-5 5-port 10/100 dualspeed hub here at home, and I'm reasonably happy with it. It certainly doesn't hang. One of the machines here has trouble negotiating a working 100Mbit/s link, but that's just as likely a problem of the Linux tulip driver. After a couple of months I put a drop of oil into the bearing of the cooling fan, which strongly suggested that treatment by the noises it was making. Somebody mentioned power supplies: Since I ordered the hub from the US but live in 230V-land, I had to experiment a bit with the transformers I had lying around. Eventually I ended up feeding the hub's power supply 120V/50Hz and it's happy with that. 100V/50Hz didn't work. This should move to -chat. -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 7:40:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 56A80150F9 for ; Sun, 19 Dec 1999 07:40:36 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id BEE0E1CC6; Sun, 19 Dec 1999 23:40:30 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Tim Tsai Cc: Sergey Babkin , Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price In-Reply-To: Message from Tim Tsai of "Sat, 18 Dec 1999 22:57:58 CST." <19991218225758.A23729@futuresouth.com> Date: Sun, 19 Dec 1999 23:40:30 +0800 From: Peter Wemm Message-Id: <19991219154030.BEE0E1CC6@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tim Tsai wrote: > > hub. It works fine except that it hangs occasionally (can be > > reset by power-cycling). > > Most of these can be attributed to the crappy wall wart they call a > power supply. If it's plugged into an UPS or replace it with your own DC > power supply they generally hold up a lot better. > > I have a Netgear FS108 at home (8 port 10/100 switch) and I've found > Netgear stuff to be as cheap as I would go and still be reasonably > reliable. I grabbed a Sohoware 8 port switch (NSH800S) a few months back. It's physically bigger than the FS108 and a bit cheaper. I picked it because the RJ45's were on the back instead of the front (as the netgear has) as it was more convenient for me. It's nice and has been totally reliable, but it runs hotter than hell. It's got two monster heatsinks on the two core VLSI chips that do the switching. The 8 phy's also get damn hot too. I'm quite concerned about it and am just about to find some power inside and put some fans in. I don't know if it's worth much, but it supposedly changes between cut-through, fragment-free cut-through and store-and-forward switching modes depending on load characteristics. Anyway, it seems the sohoware web site only refers to the NSH510 and 810, so it looks like it's superceded already. Apprently the new ones do store-and-forward only as do most of the cheaper netgear models. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 7:43:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1A3EC15340 for ; Sun, 19 Dec 1999 07:43:39 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p16-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.145]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id AAA23141; Mon, 20 Dec 1999 00:43:24 +0900 (JST) Message-ID: <385CEE25.5239137E@newsguy.com> Date: Sun, 19 Dec 1999 23:39:33 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: "Ronald F. Guilmette" Cc: Kevin Day , hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? References: <43033.945551665@monkeys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Ronald F. Guilmette" wrote: > > As I say, my understanding is that FreeBSD still doesn't have real and/or > complete thread support in the kernel. So if you have a multi-threaded > application and one thread blocks (e.g. on I/O) then the whole thing is > blocked. Ouch! That's just not true. FreeBSD has userland threads. This is faster than kernel threads, but has two disadvantages. First, it doesn't make use of SMP. Second, they all compete together as a single process for CPU time. It seems some programmers prefer to use threads to increase their process' CPU time than lowering the process' priority. OTOH, all releases so far of FreeBSD *do* have incomplete thread support. Some very important functions were missing, but it seems this is (mostly?) solved. Also, the way threads dealt with signals and wakeup's resulted in heavy overhead, but this have been changing, and it's probably ok now. Not to dismiss FreeBSD's kernel problems, but that thing about blocking is absurdly untrue. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 9:22:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 72D20151CF for ; Sun, 19 Dec 1999 09:22:19 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA01832; Sun, 19 Dec 1999 09:22:18 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA28697; Sun, 19 Dec 1999 09:22:17 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 19 Dec 1999 09:22:17 -0800 (PST) Message-Id: <199912191722.JAA28697@vashon.polstra.com> To: dcs@newsguy.com Subject: Re: Practical limit for number of TCP connections? In-Reply-To: <385CEE25.5239137E@newsguy.com> References: <43033.945551665@monkeys.com> <385CEE25.5239137E@newsguy.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <385CEE25.5239137E@newsguy.com>, Daniel C. Sobral wrote: > "Ronald F. Guilmette" wrote: > > > As I say, my understanding is that FreeBSD still doesn't have real > > and/or complete thread support in the kernel. So if you have a > > multi-threaded application and one thread blocks (e.g. on I/O) > > then the whole thing is blocked. [...] > Not to dismiss FreeBSD's kernel problems, but that thing about > blocking is absurdly untrue. It is in fact partially true. If a thread blocks on disk I/O then the whole process (all threads) blocks. That can be significant for applications that are disk intensive. I believe it to be the most significant bottleneck in current versions of CVSup, for example. (CVSup doesn't use FreeBSD's threads library, but it uses Modula-3's built-in threads package which is similar in design.) Once our aio support is knocked into shape, it should be possible for userland threads packages to use that in preference to select(). Then threads could run while one or more others were blocked on disk I/O. Of course kernel thread support may improve soon enough so that this approach isn't necessary. For CVSup I plan to experiment with using a small farm of disk I/O subprocesses (processes, not threads), communicating with the master process via shared memory and/or pipes. Without trying it, I can't say for sure whether it will yield a net win or a net loss in speed. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 10: 0:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from vorbis.noc.easynet.net (vorbis.noc.easynet.net [195.40.1.254]) by hub.freebsd.org (Postfix) with SMTP id 52E0E151F3 for ; Sun, 19 Dec 1999 10:00:24 -0800 (PST) (envelope-from chrisy@vorbis.noc.easynet.net) Received: (qmail 14436 invoked by uid 1943); 19 Dec 1999 18:00:23 -0000 Message-ID: <19991219180022.A17099@flix.net> Date: Sun, 19 Dec 1999 18:00:22 +0000 From: Chrisy Luke To: Wes Peters , Roger Hardiman Cc: hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Multi Head XFree86 VGA card recomendations wanted References: <3858C600.41C6@cs.strath.ac.uk> <385918DA.8F7F84D@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <385918DA.8F7F84D@softweyr.com>; from Wes Peters on Thu, Dec 16, 1999 at 09:52:42AM -0700 Organization: The Flirble Internet Exchange X-URL: http://www.flix.net/ X-FTP: ftp://ftp.flirble.org/ Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters wrote (on Dec 16): > Have you considered buying Metro-X? It supports up to 4 screens on just > about any combination of AGP and PCI Matrox cards. For more information, > see http://www.metrolink.com/productindex.html and look for Multi-Headed > Display Support. Metro-X is only $39. Someting I'd be keen to know is the extent of support for the new G100 MMS (Quad-head). Four G100's on one card, it seems. Works well with NT (puke) - with the limitation that all the displays need to run with the same resolution (very very sucky when you have an odd combination of monitors). Chris. -- == chris@easynet.net, chrisy@flirble.org. +44 20 7900 4444 == Systems Manager for Easynet, a part of Easynet Group PLC. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 10:44:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 39B68150F9 for ; Sun, 19 Dec 1999 10:44:53 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA03221; Sun, 19 Dec 1999 13:48:57 -0500 From: Bill Paul Message-Id: <199912191848.NAA03221@skynet.ctr.columbia.edu> Subject: Re: Cool little 100BaseTX switch - they're coming down in price To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 19 Dec 1999 13:48:56 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: <199912190443.UAA01335@apollo.backplane.com> from "Matthew Dillon" at Dec 18, 99 08:43:45 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2222 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > :At work I've got experience with 32-port D-Link 10/100 switched > :hub. It works fine except that it hangs occasionally (can be > :reset by power-cycling). So we don't buy them any more. Also > :at my pre-previous employer we had small 8-port 10Mpbs hubs from > :D-Link and they had the same problem, so it seems to be a family > :problem. With about 20 hubs there was a hang approximately every > :other day. > : > :-SB > > Oh joy. Well, we'll see what happens with this one. I > had a Sohoware superflex 10/100 hub and it hung nearly > every day. I'm also testing out a linksys switch (I > bought a D-Link switch and a LinkSys switch). > Unfortunately the NIC cards that came with the LinkSys > switch, as far as I can tell, are no longer supported > in -current. Uhm uhm uhm. You do *not* want to say things like that within earshot of me. Describe the cards better. Describe how you came to the conclusion that they aren't supported. What chip is on them? If it's the LC82C115 then these are the LNE100TX Version 2.0 with Wake On LAN, and they *are* supported: you need to use the if_dc driver. It should be in the GENERIC kernel. This same driver now also supports the older LNE100TX with the 82c168/82c169 PNIC chips. In fact the dc driver now supports all of the DEC tulip workalike chipsets. (Well, except for the Winbond W89C840F, which is still supported by the wb driver.) The really really old LNE100TX cards were based on the DEC 21140, and LinkSys doesn't sell those anymore, so I doubt you have one of those. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 11:16:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 2AC9E14CDE for ; Sun, 19 Dec 1999 11:15:54 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA06486; Sun, 19 Dec 1999 11:15:46 -0800 (PST) (envelope-from dillon) Date: Sun, 19 Dec 1999 11:15:46 -0800 (PST) From: Matthew Dillon Message-Id: <199912191915.LAA06486@apollo.backplane.com> To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912191848.NAA03221@skynet.ctr.columbia.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Uhm uhm uhm. You do *not* want to say things like that within earshot :of me. Describe the cards better. Describe how you came to the :conclusion that they aren't supported. What chip is on them? If it's :the LC82C115 then these are the LNE100TX Version 2.0 with Wake On LAN, :and they *are* supported: you need to use the if_dc driver. It should :be in the GENERIC kernel. This same driver now also supports the older :LNE100TX with the 82c168/82c169 PNIC chips. In fact the dc driver now :supports all of the DEC tulip workalike chipsets. (Well, except for :the Winbond W89C840F, which is still supported by the wb driver.) The :really really old LNE100TX cards were based on the DEC 21140, and :LinkSys doesn't sell those anymore, so I doubt you have one of those. : :-Bill : :-- :============================================================================= :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Heh heh. Indeed, they are LNE100TX V2.0 cards. I'll try adding 'dc' in. If it works, can I add a comment about 'LNE100TX' cards to the comments in LINT for 'dc'? -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 11:23:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 683341509D for ; Sun, 19 Dec 1999 11:23:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA06576; Sun, 19 Dec 1999 11:23:28 -0800 (PST) (envelope-from dillon) Date: Sun, 19 Dec 1999 11:23:28 -0800 (PST) From: Matthew Dillon Message-Id: <199912191923.LAA06576@apollo.backplane.com> To: naddy@mips.rhein-neckar.de (Christian Weisgerber) Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <83ik1i$qt6$1@bigeye.rhein-neckar.de> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I have a D-Link DSH-5 5-port 10/100 dualspeed hub here at home, :and I'm reasonably happy with it. It certainly doesn't hang. One :of the machines here has trouble negotiating a working 100Mbit/s :link, but that's just as likely a problem of the Linux tulip driver. :... :Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de My one 'de' card (tulip driver) couldn't negotiate a full-duplex link but did appear to work in half-duplex. I also have to ifconfig it down and then up again in my rc.local to get it to negotiate correctly. At BEST we used tulip cards for a few months since they were one of the first 100BaseTX cards available, but had lots of compatibility problems between them and the cisco switches so we eventually replaced them. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 11:36:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 915BF151B2 for ; Sun, 19 Dec 1999 11:36:22 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id OAA03446; Sun, 19 Dec 1999 14:40:26 -0500 From: Bill Paul Message-Id: <199912191940.OAA03446@skynet.ctr.columbia.edu> Subject: Re: Cool little 100BaseTX switch - they're coming down in price To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 19 Dec 1999 14:40:24 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: <199912191915.LAA06486@apollo.backplane.com> from "Matthew Dillon" at Dec 19, 99 11:15:46 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1313 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Matthew Dillon had to walk into mine and say: > :Uhm uhm uhm. You do *not* want to say things like that within earshot > :of me. Describe the cards better. Describe how you came to the > :conclusion that they aren't supported. What chip is on them? If it's > :the LC82C115 then these are the LNE100TX Version 2.0 with Wake On LAN, > :and they *are* supported: you need to use the if_dc driver. > Heh heh. Indeed, they are LNE100TX V2.0 cards. > > I'll try adding 'dc' in. If it works, can I add a comment about > 'LNE100TX' cards to the comments in LINT for 'dc'? Sure, if you like, however note that "man 4 dc" should also yield a list of supported cards, including the LNE100TX v2.0. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 11:43:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8920A1509D for ; Sun, 19 Dec 1999 11:43:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA06826; Sun, 19 Dec 1999 11:43:14 -0800 (PST) (envelope-from dillon) Date: Sun, 19 Dec 1999 11:43:14 -0800 (PST) From: Matthew Dillon Message-Id: <199912191943.LAA06826@apollo.backplane.com> To: "Louis A. Mamakos" Cc: Tim Tsai , Sergey Babkin , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <19991218225758.A23729@futuresouth.com> <199912190556.AAA08484@whizzo.transsys.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :with a *really* big heatsink attached -this is the "bridge on chip". And :I noticed another, smaller IC which had a hole blown out of the epoxy case :(which subsequently allowed the smoke to escape. : :It was than than I make the connection - Hmm.. SGI LCD monitor don't work. :Ethernet switch makes smoke. Ethernet switch wants 5VDC power brick. :SGI LCD monitor wants 12VDC power brick. Ooops! : :So, after switching power bricks, the SGI LCD monitor starts working again. :It really wants 12V and not 5V. : :louie Ouch. That switch is using a terrible design if it blows up with too high a DC voltage input! I really hate these switching regulated DC wall plugs. They always use cheap caps in them to save money and then don't bother adding any protection to the motherboard. I prefer AC wall plugs or unregulated DC wall plugs and then a small switching regulator on the motherboard. That way you can throw anything up to 40V into it and it will still work. In BEST's early days we were using off the shelf USR sportsters for our modems. Sportsters have a heat problem mainly due to bad design, but they *did* have a switching regulator on board and after dissecting it I determined that we could simply bump up the unregulated AC going into them by a couple of volts (which reduces the current going through the switching power supply and thus reduces the heat). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 12: 2:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4AA4C151A6 for ; Sun, 19 Dec 1999 12:02:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA08083; Sun, 19 Dec 1999 12:02:22 -0800 (PST) (envelope-from dillon) Date: Sun, 19 Dec 1999 12:02:22 -0800 (PST) From: Matthew Dillon Message-Id: <199912192002.MAA08083@apollo.backplane.com> To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912191940.OAA03446@skynet.ctr.columbia.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> I'll try adding 'dc' in. If it works, can I add a comment about :> 'LNE100TX' cards to the comments in LINT for 'dc'? : :Sure, if you like, however note that "man 4 dc" should also yield a :list of supported cards, including the LNE100TX v2.0. : :-Bill Yup, but that assumes you alredy know which manual page to look at. Historically I've always looked for card brands in 'LINT' because that is historically where I've always found them to be up to date. P.S. I would like to take this opportunity to thank you for all the work you've done on various PCI ethernet cards, it's a made a big difference for me and I'm sure many people! -Matt Matthew Dillon :-- :============================================================================= :-Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 12: 3:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from maxwell.syr.edu (maxwell.syr.edu [128.230.129.5]) by hub.freebsd.org (Postfix) with ESMTP id A664B1526A for ; Sun, 19 Dec 1999 12:03:21 -0800 (PST) (envelope-from cmsedore@maxwell.syr.edu) Received: from qwerty.maxwell.syr.edu (qwerty.maxwell.syr.edu [128.230.129.248]) by maxwell.syr.edu (8.9.1a/8.9.1) with ESMTP id OAA22920; Sun, 19 Dec 1999 14:59:39 -0500 (EST) Date: Sun, 19 Dec 1999 15:01:41 -0500 (EST) From: Chris Sedore To: Alfred Perlstein Cc: Kevin Day , "Ronald F. Guilmette" , hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? 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 Sat, 18 Dec 1999, Alfred Perlstein wrote: > On Sat, 18 Dec 1999, Kevin Day wrote: > > > > The _clean_ way of doing it would be to write your multi-user server using > > > threads, and to assign one thread to each connection. If you can do that, > > > then the logic in the program becomes quite simple. Each thread just sits > > > there, blocked on a call to read(), until something comes in, and then it > > > just parses the command, does whatever it is supposed to do in response to > > > that command, and then goes back to the read() again. > > > > > > But as I understand it, there is not yet sufficient threads support in the > > > FreeBSD kernel to make this work well/properly. (I may perhaps be misinformed > > > about that, but that's what I have been told anyway.) > > > > I believe this is how ConferenceRoom works, so it seems ok, but I remember > > the comments that FreeBSD was their least preferred platform because of > > thread problems. > > Using a thread per connection has always been a bogus way of programming, > it's easy, but it doesn't work very well. Ahem. Well, that kind of depends on the threads implementation, how many connections you're talking about, and likely some other factors too. I've got an NT box that handles about 1000 concurrent connections with 1000 (plus a few) threads doing the work. Runs fine, performs very well. I wouldn't argue that it is the most scalable solution to problems, but it is easier, and scales proportionally to the quality of the threads implementation. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 12: 8: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from maild.telia.com (maild.telia.com [194.22.190.3]) by hub.freebsd.org (Postfix) with ESMTP id BC35E151CF for ; Sun, 19 Dec 1999 12:08:02 -0800 (PST) (envelope-from stefan@syprix.se) Received: from d1o49.telia.com (d1o49.telia.com [195.198.194.241]) by maild.telia.com (8.9.3/8.9.3) with ESMTP id VAA23576; Sun, 19 Dec 1999 21:07:53 +0100 (CET) Received: from syprix.se (t5o49p49.telia.com [195.198.195.49]) by d1o49.telia.com (8.8.8/8.8.8) with ESMTP id VAA18414; Sun, 19 Dec 1999 21:07:51 +0100 (CET) Message-ID: <385D401C.24FE57C6@syprix.se> Date: Sun, 19 Dec 1999 21:29:16 +0100 From: Stefan Lindgren Reply-To: stefan@syprix.se Organization: Syprix AB X-Mailer: Mozilla 4.61 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Rob King Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: XDM, KDM, PAM, FreeBSD, and a partridge in a pear tree... References: <199912191156.FAA21939@mail.pernet.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try this, cat ~/.xsession xterm -sl 1000 -sb & twm(or the famous $SOMEPATH/startkde;) Ctrl-d /stefan Rob King wrote: > > Once again, I apologize for asking a question that is probably off-list, > but... > > Here's the problem: I'm running a fresh install of 3.3-STABLE, and trying to > get the nice graphical login, with either XDM or KDM. Unfortunantly, I get an > 'incorrect password' error no matter what I type. I also get a "pam: no > modules loaded for xdm service" or kdm service, depending. I have a line in my > /etc/pam.conf: > > xdm auth required pam_unix.so try_first_pass > > Unfortunantly, no matter what happens, neither KDM nor XDM will recognize me. > Any ideas, anyone? > > Thanks all, > Rob > > -- > Rob King > System Administrator - PERnet Communications, Inc. > jking@pernet.net - http://www.pernet.net/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 12:32:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from search.sparks.net (search.sparks.net [208.5.188.60]) by hub.freebsd.org (Postfix) with ESMTP id 2F5FC14DC3 for ; Sun, 19 Dec 1999 12:32:41 -0800 (PST) (envelope-from dmiller@search.sparks.net) Received: by search.sparks.net (Postfix, from userid 100) id 095E6250; Sun, 19 Dec 1999 15:32:34 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by search.sparks.net (Postfix) with SMTP id ED588246 for ; Sun, 19 Dec 1999 15:32:34 -0500 (EST) Date: Sun, 19 Dec 1999 15:32:34 -0500 (EST) From: David Miller To: freebsd-hackers@freebsd.org Subject: Alternate ftpd? 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 all:) I'm looking for an alternate ftpd which allows me to take certain (configurable) actions based on the receipt of certain files. For exmple, I want to "process" a tar file full of jpg images upon receipt. I know there are alternatives. I can run swatch on the log file or torture syslog to piping its output into something, but I think these are all ugly kludges. I know ncftpd sort of has this option, but it does it by sending udp packets to a process which is supposed to be running and not miss the packet. I looked at the source for ftpd and got lost in the ftpcmd.y processing. Adding a simple printf statement blows the whole thing out of the water. All the ftp servers in the ports collection appear to have the same structure. troll counts on linux specific syscalls. Any simple ftpd servers out there? Any which have configurable actions to handle incoming files? Thanks, --- David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 12:40:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 8C09D14A1E for ; Sun, 19 Dec 1999 12:40:11 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id MAA47487 for ; Sun, 19 Dec 1999 12:40:10 -0800 (PST) To: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sun, 19 Dec 1999 23:39:33 +0900. <385CEE25.5239137E@newsguy.com> Date: Sun, 19 Dec 1999 12:40:09 -0800 Message-ID: <47485.945636009@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <385CEE25.5239137E@newsguy.com>, "Daniel C. Sobral" wrote: >"Ronald F. Guilmette" wrote: >> >> As I say, my understanding is that FreeBSD still doesn't have real and/or >> complete thread support in the kernel. So if you have a multi-threaded >> application and one thread blocks (e.g. on I/O) then the whole thing is >> blocked. > >Ouch! That's just not true. > >FreeBSD has userland threads. This is faster than kernel threads, but >has two disadvantages. First, it doesn't make use of SMP. Second, they >all compete together as a single process for CPU time. It seems some >programmers prefer to use threads to increase their process' CPU time >than lowering the process' priority. Well, my apologies for mis-speaking. When I say ``real/complete threads support'', I usually mean threads that: o will in fact get distributed across multiple processors in an a multiprocessor system (if the kernel support multi-processors at all that is), and threads that... o will in fact compete against all other threads/processes in the system for CPU slices, and threads that... o can block on I/O while other threads in the same process continue to be scheduled. Now you are saying that at present, the FreeBSD implementation of threads has at least the last of these three attributes. That's the first _I've_ heard of that, but it is certainly encouraging, and it may cause me to start doing some stuff with threads under FreeBSD. I would really be very grateful however if _someone_ would explain to me the actual low level-mechanics of how this works, i.e. how one thread in a ``multi-userland-thread'' process can manage to get control and/or a CPU time slice when and if a different thread within the same process gets blocked awaiting some I/O completion. For example, take the simplest possible case.... I have a process that is running two threads. One of those threads issues a call to read(2) to read characters from some interactive device... like a terminal. But no characters are yet available. So that thread blocks on the I/O request. In this simple scenario, how does the other thread (which is part of this same process) get control back? Give the other assertions that you've made about threads, i.e. that (in recent releases of FreeBSD at least) they DO NOT compete with each other and/or with other processes on a system-wide basis, I really have a little trouble understanding how the second thread in the scenario I described would manage to get control back. The kernel doesn't even know that that second thread exists as a separately schedualable entity, right? So who (or what) exactly is going to schedule it for execution when the first thread becomes blocked on I/O? >Not to dismiss FreeBSD's kernel problems, but that thing about blocking >is absurdly untrue. I'll take your word for it. I juts wish that I could understand how that could be the case. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 12:47:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 9742C14C1D for ; Sun, 19 Dec 1999 12:47:26 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id MAA47601 for ; Sun, 19 Dec 1999 12:47:25 -0800 (PST) To: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sun, 19 Dec 1999 09:22:17 -0800. <199912191722.JAA28697@vashon.polstra.com> Date: Sun, 19 Dec 1999 12:47:25 -0800 Message-ID: <47599.945636445@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912191722.JAA28697@vashon.polstra.com>, John Polstra wrote: >In article <385CEE25.5239137E@newsguy.com>, Daniel C. Sobral > wrote: > >> "Ronald F. Guilmette" wrote: >> >> > As I say, my understanding is that FreeBSD still doesn't have real >> > and/or complete thread support in the kernel. So if you have a >> > multi-threaded application and one thread blocks (e.g. on I/O) >> > then the whole thing is blocked. > >[...] > >> Not to dismiss FreeBSD's kernel problems, but that thing about >> blocking is absurdly untrue. > >It is in fact partially true. If a thread blocks on disk I/O then >the whole process (all threads) blocks... I'd like to just take a second and re-express my growing confusion on this whole topic. Why do you say that this complete-process-blocking effect only takes place in the case of disk reads?? Isn't a read a read? What difference does it make what the device type being read from is? Is there some piece of code burried somewhere in either libc or the kernel that checks each call to read(2) to find out if that is a disk drive you are reading from versus reading from a terminal or a network socket? I'm just trying to understand this stuff. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 12:58:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 5930D14DC3 for ; Sun, 19 Dec 1999 12:58:29 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id OAA06083; Sun, 19 Dec 1999 14:58:21 -0600 (CST) (envelope-from dick) Date: Sun, 19 Dec 1999 14:58:21 -0600 From: "Richard Seaman, Jr." To: "Ronald F. Guilmette" Cc: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? Message-ID: <19991219145821.D317@tar.com> References: <385CEE25.5239137E@newsguy.com> <47485.945636009@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <47485.945636009@monkeys.com>; from rfg@monkeys.com on Sun, Dec 19, 1999 at 12:40:09PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 19, 1999 at 12:40:09PM -0800, Ronald F. Guilmette wrote: > > In message <385CEE25.5239137E@newsguy.com>, > "Daniel C. Sobral" wrote: > >FreeBSD has userland threads. This is faster than kernel threads, but Actually, userland threads *should* be faster, but for lots of things, they aren't in the current implementation. There is discussion about how to improve this in the -arch mailing list. [snip] > o can block on I/O while other threads in the same process continue > to be scheduled. > > Now you are saying that at present, the FreeBSD implementation of threads > has at least the last of these three attributes. That's the first _I've_ > heard of that, but it is certainly encouraging, and it may cause me to > start doing some stuff with threads under FreeBSD. This has been true for a long very time. > I would really be very grateful however if _someone_ would explain to me > the actual low level-mechanics of how this works, i.e. how one thread in > a ``multi-userland-thread'' process can manage to get control and/or a > CPU time slice when and if a different thread within the same process > gets blocked awaiting some I/O completion. It would be easier for you to read the code (see libc_r/uthread). Its very messy. Basically, all i/o syscalls that can block are converted to non-blocking. If the syscall would block, the userland thread scheduler handles the "blocking", by scheduling another thread, and then periodically polling the i/o device to see if its ready. When it is, the original thread can be restarted. This is why the userland thread scheduler is not very swift, and why user thread context switches are a lot slower than kernel thread context switches. Also note that you can try kernel threads using ports/devel/linuxthreads. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 12:59:26 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 723A6151F6 for ; Sun, 19 Dec 1999 12:59:18 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id QAA03584 for hackers@freebsd.org; Sun, 19 Dec 1999 16:03:28 -0500 From: Bill Paul Message-Id: <199912192103.QAA03584@skynet.ctr.columbia.edu> Subject: USB ethernet hacking To: hackers@freebsd.org Date: Sun, 19 Dec 1999 16:03:26 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 5912 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those of you who don't know, I've been working on a driver for the ADMtek USB Ethernet chip (AN986 Pegasus). It kinda sorta works: aue0: ADMtek Inc. ADMtek 10/100 USB MAC, rev 1.10/1.01, addr 2 aue0: Ethernet address: 00:00:e8:00:00:a2 miibus0: on aue0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto The particular adapter I have is a combo device which supports both 10/100 ethernet and 1Mbps HomePNA (ethernet over home telephone cabling). I only have the ethernet PHY enabled for the moment since I don't have any way to test the HomePNA part, and I need to write a separate HomePNA PHY driver so that the media type is recognized correctly. (Right now, the ukphy driver thinks it's just another 10Mbps PHY, which causes the miibus layer to think the interface has two 10baseT/UTP media selections, which doesn't work.) I've gotten the thing working well enough with FreeBSD-current that I can telnet over it and type this message. However, there are some problems that I've run into which I don't know how to solve due to my inexperience with USB. First of all, there's one major problem with the USB code as it's currently implemented with regard to "synchronous" transfers. There are two basic ways to transfer data to/from a USB device: an asynchronous method, and a synchronous one. The asynchronous one works like this: - allocate a USB transfer handle - set it up with the correct parameters, including a pointer to a callback routine - call usbd_transfer() to initiate it - go off and to other stuff for a while - when the transfer is done, the USB controller's interrupt handler will call the callback routine with the transfer results. The synchronous method works like this: - allocate a USB transfer handle - set it up with the correct parameters - call usbd_sync_transfer() to initiate it - usbd_sync_transfer() blocks until the transfer is complete, and which point you can call usbd_get_xfer_status() to find the results The problem is that the synchronous method is not really synchronous: in usbdi.c:usbd_transfer(), if we are performing a sync transfer and the transfer doesn't complete right away, the code calls tsleep() in the hope that it can pause the process that initiated the transfer and wake it up later. Unfortunately, you can't call tsleep() from interrupt context, and I need to be able to do that. Why? Because reading and writing the registers on the ethernet MAC in the ADMtek device is done by performing transfers using USB endpoint 0 (the control endpoint). The miibus code needs to be able to read the PHY status once in a while, and this is done by setting up a timeout() that fires once a second to tall the aue_tick() routine, which in turn calls mii_tick() to drive the miibus code. But aue_tick() is called at interrupt context, and the kernel panicks whenever it hits that tsleep() in usbd_transfer(). I have worked around this for now by hacking usbdi.c so that it polls the controller interrupt/status register instead of tsleep()ing. I'm not sure this is the best solution, but it's the only one that seems to work. However that's not my biggest problem. My biggest problem is getting transfers over 1100 bytes or so to work reliably. My initial scheme for transmitting and receiving packets was to set up asynchronous transfers with callbacks. Packets are sent over bulk transfer endpoints (one for RX, one for TX). For TX, I would set up a transfer and initiate it, then wait until the callback is called to free the mbuf containing the packet data. This seemed to work, but only for transfers around 1000 to 1100 bytes or so. Trying to transfer packets of 1200 bytes or more always seemed to yield an "IOERROR" error. I switched the packet transmission code to use synchronous transfers (i.e. waiting for the transfer to complete before moving on) and this seemed to help: I could now get transmissions up to 1500 bytes to work without errors. However, I have the same problem now with received packets: trying to receive a frame larger than 1100 bytes also causes an IOERROR, however I can't use a synchronous transfer here since that would cause the kernel to freeze in its tracks waiting for a packet. Tracing down the error shows that the uhci driver is getting an error status of 0x500000, which is apparently the logical OR of two error bits: "babble" and "stall." I have the Intel UHCI spec document and it mentions these errors, however it doesn't seem to say what causes them, how to clear them or, more importantly, how to avoid them. If I could just figure out how to get this thing to handle these "large" transfers, I would be a happy camper. I put a copy of my current code at: http://www.freebsd.org/~wpaul/ADMtek/USB/4.0 This directory contains the source for the if_aue driver, plus a patch for usbdi.c with the changes I made to get sync transfers to work properly in interrupt context. The code is still very grotty. The datasheet for the ADMtek Pegasus chip is at http://www.admtek.com.tw. -Bill P.S.: Please don't write me asking for help getting your USB ethernet adapter work with FreeBSD. Don't ask me when/if the driver will be done. Don't ask me if your favorite adapter will be supported. Don't ask me how to make the code work with FreeBSD 3.x. -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 13: 6:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id D22A3151D7 for ; Sun, 19 Dec 1999 13:06:29 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id NAA11396; Sun, 19 Dec 1999 13:00:37 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id NAA04547; Sun, 19 Dec 1999 13:00:36 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA11364; Sun, 19 Dec 99 13:00:31 PST Message-Id: <385D47D3.FCEE9EAB@softweyr.com> Date: Sun, 19 Dec 1999 14:02:11 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: "Louis A. Mamakos" , Tim Tsai , Sergey Babkin , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <19991218225758.A23729@futuresouth.com> <199912190556.AAA08484@whizzo.transsys.com> <199912191943.LAA06826@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :with a *really* big heatsink attached -this is the "bridge on chip". And > :I noticed another, smaller IC which had a hole blown out of the epoxy case > :(which subsequently allowed the smoke to escape. > : > :It was than than I make the connection - Hmm.. SGI LCD monitor don't work. > :Ethernet switch makes smoke. Ethernet switch wants 5VDC power brick. > :SGI LCD monitor wants 12VDC power brick. Ooops! > : > :So, after switching power bricks, the SGI LCD monitor starts working again. > :It really wants 12V and not 5V. > : > :louie > > Ouch. That switch is using a terrible design if it blows up with too > high a DC voltage input! > > I really hate these switching regulated DC wall plugs. They always use > cheap caps in them to save money and then don't bother adding any > protection to the motherboard. I prefer AC wall plugs or unregulated DC > wall plugs and then a small switching regulator on the motherboard. That > way you can throw anything up to 40V into it and it will still work. And nearly double the cost of the item, and make it much more difficult (read as "expensive") to pass FCC/EC requirements. You may prefer such things, but you're not willing to pay for them. (Generic "you" meaning "everyone" here). -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 13:17:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 6E273151FB for ; Sun, 19 Dec 1999 13:17:07 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost.orthanc.ab.ca [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id dBJLH2Q37983 for ; Sun, 19 Dec 1999 14:17:03 -0700 (MST) Message-Id: <199912192117.dBJLH2Q37983@orthanc.ab.ca> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price In-reply-to: Your message of "Sat, 18 Dec 1999 20:43:45 PST." <199912190443.UAA01335@apollo.backplane.com> Date: Sun, 19 Dec 1999 14:17:01 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Matthew" == Matthew Dillon writes: Matthew> :At work I've got experience with 32-port D-Link 10/100 Matthew> switched :hub. It works fine except that it hangs Matthew> occasionally (can be :reset by power-cycling). So we Matthew> don't buy them any more. Also :at my pre-previous Matthew> employer we had small 8-port 10Mpbs hubs from :D-Link and Matthew> they had the same problem, so it seems to be a family Matthew> :problem. With about 20 hubs there was a hang Matthew> approximately every :other day. : :-SB Matthew> Oh joy. Well, we'll see what happens with this one. As a counter-point, we have five D-Link 24 port hubs with the 10/100 switch module, SNMP, and a fibre link between the two stacks. They've been running for a year (almost to the day) and we haven't ever seen one lock up. The DFE-530TX's have been giving me good throughput, although they usually fail to autosense a 10 Mb/s network correctly. And FWIW, I just picked up a D-Link DSH II eight port 10/100 hub yesterday. It has a switch between the 10/100 segments, which means I can now get my PAO-based laptop on the network at home (@10 Mb/s). It ran me CAN$249 retail at the corner computer store. (That's about USD$160.) --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 13:21:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 5269A14ED7 for ; Sun, 19 Dec 1999 13:21:16 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id NAA47933 for ; Sun, 19 Dec 1999 13:21:15 -0800 (PST) To: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sun, 19 Dec 1999 14:58:21 -0600. <19991219145821.D317@tar.com> Date: Sun, 19 Dec 1999 13:21:15 -0800 Message-ID: <47931.945638475@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991219145821.D317@tar.com>, "Richard Seaman, Jr." wrote: >> I would really be very grateful however if _someone_ would explain to me >> the actual low level-mechanics of how this works, i.e. how one thread in >> a ``multi-userland-thread'' process can manage to get control and/or a >> CPU time slice when and if a different thread within the same process >> gets blocked awaiting some I/O completion. > >It would be easier for you to read the code (see libc_r/uthread). >Its very messy. Basically, all i/o syscalls that can block are >converted to non-blocking. If the syscall would block, the userland >thread scheduler handles the "blocking", by scheduling another thread, >and then periodically polling the i/o device to see if its ready. OK. That is a clear and adequate explanation. Thank you. I'm not at all sure that I like the idea of something intercepting my syscalls and rewriting them for me, but I understand why it is being done, and (now) I understand how the current ``userland threads'' stuff works. >This is why the userland thread scheduler is not >very swift, and why user thread context switches are a lot slower >than kernel thread context switches. Yes. It sounds to me like each and every time there is a thread context switch, some code in the library may have to execute a (perhaps enormous) call to select() or else to poll(). Yes? (Please don't tell me this is all implemented with asynchronous I/O completion signals. Yecch. That would be awfully slow I think.) >Also note that you can try kernel threads using ports/devel/linuxthreads. I'm in no big hurry. I'll wait for the freebsdthreads. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 13:22:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 29B0A1523A for ; Sun, 19 Dec 1999 13:22:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA09115; Sun, 19 Dec 1999 13:22:24 -0800 (PST) (envelope-from dillon) Date: Sun, 19 Dec 1999 13:22:24 -0800 (PST) From: Matthew Dillon Message-Id: <199912192122.NAA09115@apollo.backplane.com> To: Bill Paul Cc: hackers@freebsd.org Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912191940.OAA03446@skynet.ctr.columbia.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Heh heh. Indeed, they are LNE100TX V2.0 cards. :> :> I'll try adding 'dc' in. If it works, can I add a comment about :> 'LNE100TX' cards to the comments in LINT for 'dc'? : :Sure, if you like, however note that "man 4 dc" should also yield a :list of supported cards, including the LNE100TX v2.0. : :-Bill Works like a charm! Cool stuff! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 13:27:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 5950A1509D for ; Sun, 19 Dec 1999 13:27:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA09156; Sun, 19 Dec 1999 13:27:48 -0800 (PST) (envelope-from dillon) Date: Sun, 19 Dec 1999 13:27:48 -0800 (PST) From: Matthew Dillon Message-Id: <199912192127.NAA09156@apollo.backplane.com> To: Wes Peters Cc: "Louis A. Mamakos" , Tim Tsai , Sergey Babkin , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <19991218225758.A23729@futuresouth.com> <199912190556.AAA08484@whizzo.transsys.com> <199912191943.LAA06826@apollo.backplane.com> <385D47D3.FCEE9EAB@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> I really hate these switching regulated DC wall plugs. They always use :> cheap caps in them to save money and then don't bother adding any :> protection to the motherboard. I prefer AC wall plugs or unregulated DC :> wall plugs and then a small switching regulator on the motherboard. That :> way you can throw anything up to 40V into it and it will still work. : :And nearly double the cost of the item, and make it much more difficult :(read as "expensive") to pass FCC/EC requirements. You may prefer such :things, but you're not willing to pay for them. (Generic "you" meaning :"everyone" here). : :Wes Peters Softweyr LLC This is not true at all. First, the U.L. is handled by the wall adapter. Second, getting FCC certification for a small device whos U.L. is arleady handled by a wall adapter is *trivial*. Moving the switching supply inside verses depending on a DC adapter does not make FCC cert. more difficult. There is an expense in the power supply verses the cheap crap you get in a DC regulated wall adapter - well, doh! That's why it's better! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 13:39:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 59357151A6 for ; Sun, 19 Dec 1999 13:39:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA09232; Sun, 19 Dec 1999 13:39:18 -0800 (PST) (envelope-from dillon) Date: Sun, 19 Dec 1999 13:39:18 -0800 (PST) From: Matthew Dillon Message-Id: <199912192139.NAA09232@apollo.backplane.com> To: "Ronald F. Guilmette" Cc: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? References: <47599.945636445@monkeys.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'd like to just take a second and re-express my growing confusion on :this whole topic. : :Why do you say that this complete-process-blocking effect only takes :place in the case of disk reads?? Isn't a read a read? What difference :does it make what the device type being read from is? : :Is there some piece of code burried somewhere in either libc or the :kernel that checks each call to read(2) to find out if that is a disk :drive you are reading from versus reading from a terminal or a network :socket? : :I'm just trying to understand this stuff. There are certain I/O related operations which are assumed to not block, even though the kernel *might* block on the temporarily. For example, when you open and read() from a file, you assume your read() command will return reasonably quickly - even though in actual fact the data may not be cached and the OS may have to read it from the physical disk, blocking temporarily. On the otherhand, if you are read()ing from a pipe, keyboard, or a TCP connection, you assume that the read() will block for (potentially) long periods of time. In such cases where you believe the read() or write() might block, you typically use select() and O_NONBLOCK to tell the system not to block on the I/O and to tell you when you *can* read or write to it without blocking. However, things like disk I/O are assumed to not block, even if they do for short periods of time, and select() does not work on such those descriptors. The reason this is important is the same reason why a program doing lots of heavy, parallel disk I/O might decide to fork a couple of processes - because some disk I/O operations can be handled from the cache without blocking, and others will not be, and it's impossible to know which ones will and which ones won't. So the reason you fork a couple of processes in this case is to ensure that if one blocks on a disk I/O, some of the others can still do read()'s and write()'s through the cache without waiting for the one blocked on disk I/O to complete first. If you don't do this then all of your I/O operations will be held up by the one blocking on disk I/O even if some of the others could be handled from the disk cache without blocking. - The current threads implementation has this problem because you have N threads running under a single process. If one thread blocks on a disk I/O then all the threads essentially block. The proposed new threads implementation does not have this problem. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 13:42:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [205.159.88.46]) by hub.freebsd.org (Postfix) with ESMTP id A1325151A6 for ; Sun, 19 Dec 1999 13:42:15 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id NAA01963 for ; Sun, 19 Dec 1999 13:42:50 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id NAA05615; Sun, 19 Dec 1999 13:42:31 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Sun, 19 Dec 1999 13:42:31 -0800 (PST) From: Brian Beattie To: freebsd-hackers@freebsd.org Subject: Parallel-port ethernet interfaces 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 Anybody know of any currently available, that are supported by FreeBSD? Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 13:45: 2 1999 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 10BB814CA4 for ; Sun, 19 Dec 1999 13:44:59 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA07731; Sun, 19 Dec 1999 13:44:48 -0800 (PST) Date: Sun, 19 Dec 1999 13:44:47 -0800 (PST) From: Julian Elischer To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: USB ethernet hacking In-Reply-To: <199912192103.QAA03584@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Dec 1999, Bill Paul wrote: > For those of you who don't know, I've been working on a driver for the > ADMtek USB Ethernet chip (AN986 Pegasus). It kinda sorta works: > > aue0: ADMtek Inc. ADMtek 10/100 USB MAC, rev 1.10/1.01, addr 2 > aue0: Ethernet address: 00:00:e8:00:00:a2 > miibus0: on aue0 > ukphy0: on miibus0 > ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > > The particular adapter I have is a combo device which supports both > 10/100 ethernet and 1Mbps HomePNA (ethernet over home telephone cabling). > I only have the ethernet PHY enabled for the moment since I don't > have any way to test the HomePNA part, and I need to write a separate > HomePNA PHY driver so that the media type is recognized correctly. > (Right now, the ukphy driver thinks it's just another 10Mbps PHY, > which causes the miibus layer to think the interface has two 10baseT/UTP > media selections, which doesn't work.) > > I've gotten the thing working well enough with FreeBSD-current that I > can telnet over it and type this message. However, there are some problems > that I've run into which I don't know how to solve due to my inexperience > with USB. > > First of all, there's one major problem with the USB code as it's currently > implemented with regard to "synchronous" transfers. There are two basic ways > to transfer data to/from a USB device: an asynchronous method, and a > synchronous one. The asynchronous one works like this: > > - allocate a USB transfer handle > - set it up with the correct parameters, including a pointer > to a callback routine > - call usbd_transfer() to initiate it > - go off and to other stuff for a while > - when the transfer is done, the USB controller's interrupt > handler will call the callback routine with the transfer > results. > > The synchronous method works like this: > > - allocate a USB transfer handle > - set it up with the correct parameters > - call usbd_sync_transfer() to initiate it > - usbd_sync_transfer() blocks until the transfer is complete, > and which point you can call usbd_get_xfer_status() to > find the results > > The problem is that the synchronous method is not really synchronous: > in usbdi.c:usbd_transfer(), if we are performing a sync transfer and > the transfer doesn't complete right away, the code calls tsleep() in > the hope that it can pause the process that initiated the transfer and > wake it up later. Unfortunately, you can't call tsleep() from interrupt > context, and I need to be able to do that. Why? Because reading and > writing the registers on the ethernet MAC in the ADMtek device is done > by performing transfers using USB endpoint 0 (the control endpoint). > The miibus code needs to be able to read the PHY status once in a while, > and this is done by setting up a timeout() that fires once a second to > tall the aue_tick() routine, which in turn calls mii_tick() to drive > the miibus code. But aue_tick() is called at interrupt context, and > the kernel panicks whenever it hits that tsleep() in usbd_transfer(). Doug Ambrisko and I wrote a netgraph based USB-to-USB networking device node. We used the async method and it works fine. We just added a queue and called an interrupt level 'start routine' much like any other driver. It works like a charm. I don't see why it wouldn't work for an ethenet style device.. We had to add splimp() protection in some places because splusb() is actually splbio() but it seems to work as expected. > > I have worked around this for now by hacking usbdi.c so that it polls > the controller interrupt/status register instead of tsleep()ing. I'm not > sure this is the best solution, but it's the only one that seems to work. why not use the async method? > > However that's not my biggest problem. My biggest problem is getting > transfers over 1100 bytes or so to work reliably. My initial scheme > for transmitting and receiving packets was to set up asynchronous > transfers with callbacks. That's what we did and we can send 1500 byte packets with no problems. > Packets are sent over bulk transfer endpoints > (one for RX, one for TX). For TX, I would set up a transfer and initiate > it, then wait until the callback is called to free the mbuf containing > the packet data. We just copied the data from the mbuf into a dedicated buffer and freed the mbuff immediatly. > This seemed to work, but only for transfers around > 1000 to 1100 bytes or so. Trying to transfer packets of 1200 bytes or > more always seemed to yield an "IOERROR" error. I switched the packet > transmission code to use synchronous transfers (i.e. waiting for the > transfer to complete before moving on) and this seemed to help: I could > now get transmissions up to 1500 bytes to work without errors. Once again, we used a dedicated buffer which we copied from. > > However, I have the same problem now with received packets: trying to > receive a frame larger than 1100 bytes also causes an IOERROR, however > I can't use a synchronous transfer here since that would cause the kernel > to freeze in its tracks waiting for a packet. > > Tracing down the error shows that the uhci driver is getting an error > status of 0x500000, which is apparently the logical OR of two error bits: > "babble" and "stall." I have the Intel UHCI spec document and it mentions > these errors, however it doesn't seem to say what causes them, how to > clear them or, more importantly, how to avoid them. If I could just > figure out how to get this thing to handle these "large" transfers, I > would be a happy camper. > > I put a copy of my current code at: > > http://www.freebsd.org/~wpaul/ADMtek/USB/4.0 > > This directory contains the source for the if_aue driver, plus a patch > for usbdi.c with the changes I made to get sync transfers to work properly > in interrupt context. The code is still very grotty. The datasheet for > the ADMtek Pegasus chip is at http://www.admtek.com.tw. > > -Bill > > P.S.: Please don't write me asking for help getting your USB ethernet > adapter work with FreeBSD. Don't ask me when/if the driver will > be done. Don't ask me if your favorite adapter will be supported. > Don't ask me how to make the code work with FreeBSD 3.x. > > Julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 14: 6:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id E203315105 for ; Sun, 19 Dec 1999 14:06:50 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id QAA06450; Sun, 19 Dec 1999 16:06:45 -0600 (CST) (envelope-from dick) Date: Sun, 19 Dec 1999 16:06:45 -0600 From: "Richard Seaman, Jr." To: "Ronald F. Guilmette" Cc: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? Message-ID: <19991219160645.E317@tar.com> References: <19991219145821.D317@tar.com> <47931.945638475@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <47931.945638475@monkeys.com>; from rfg@monkeys.com on Sun, Dec 19, 1999 at 01:21:15PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 19, 1999 at 01:21:15PM -0800, Ronald F. Guilmette wrote: > It sounds to me like each and every time there is a thread context switch, > some code in the library may have to execute a (perhaps enormous) call to > select() or else to poll(). Yes? poll(). It used to use select(). And, not only at each thread context switch, but each time it has to consider whether to do a switch at all (eg. at the end of a timeslice). -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 14:14:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 4189B151FB for ; Sun, 19 Dec 1999 14:14:37 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id RAA03775; Sun, 19 Dec 1999 17:18:38 -0500 From: Bill Paul Message-Id: <199912192218.RAA03775@skynet.ctr.columbia.edu> Subject: Re: USB ethernet hacking To: julian@whistle.com (Julian Elischer) Date: Sun, 19 Dec 1999 17:18:37 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: from "Julian Elischer" at Dec 19, 99 01:44:47 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3419 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Julian Elischer had to walk into mine and say: > Doug Ambrisko and I wrote a netgraph based USB-to-USB networking device > node. We used the async method and it works fine. We just added > a queue and called an interrupt level 'start routine' much like any other > driver. It works like a charm. I don't see why it wouldn't work for an > ethenet style device.. We had to add splimp() protection in some places > because splusb() is actually splbio() but it seems to work as expected. I don't know why it doesn't work either. Hence my posting here. :) > > I have worked around this for now by hacking usbdi.c so that it polls > > the controller interrupt/status register instead of tsleep()ing. I'm not > > sure this is the best solution, but it's the only one that seems to work. > > why not use the async method? Because this is not an asynchronous task that I'm trying to do here. I'm talking about reading and writing registers from the ethernet controller. If this was a PCI device, I'd be using bus_space_read_X()/bus_space_write_X() to read the registers directly. I don't want to start reading a register and then come back a while later to read the results. The code isn't meant to work like that. > > However that's not my biggest problem. My biggest problem is getting > > transfers over 1100 bytes or so to work reliably. My initial scheme > > for transmitting and receiving packets was to set up asynchronous > > transfers with callbacks. > > That's what we did and we can send 1500 byte packets with no problems. You're not allowed to say "that's what we did" without a) looking at the code that I wrote and comparing it and b) showing me your code so that I can compare it too and see where I might have gone wrong. One other interesting thing that I found is that I had to use the USBD_SHORT_XFER_OK flag in order to receive packets at all. Right now, the only way I can make it work at all is to set the interface MTU to 1000 bytes. Right now I'm just talking through a crossover cable to another machine, so I can set the MTU on both ends for experimenting, but obviously I can't keep it like that. I still would like to know what a "babble" error means in this context, and how to clear it. With ethernet, it usually means that somebody is sending way, way, *way* too much data in a single transaction, but I'm not sure how to interpret it here. > > Packets are sent over bulk transfer endpoints > > (one for RX, one for TX). For TX, I would set up a transfer and initiate > > it, then wait until the callback is called to free the mbuf containing > > the packet data. > > We just copied the data from the mbuf into a dedicated > buffer and freed the mbuff immediatly. Did you just allocate a buffer with malloc() (or contigmalloc()), or did you use usbd_alloc_buffer()? -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 14:19:30 1999 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 9DD7415233 for ; Sun, 19 Dec 1999 14:19:26 -0800 (PST) (envelope-from imp@harmony.village.org) 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 PAA08390; Sun, 19 Dec 1999 15:19:25 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA08250; Sun, 19 Dec 1999 15:19:24 -0700 (MST) Message-Id: <199912192219.PAA08250@harmony.village.org> To: Brian Beattie Subject: Re: Parallel-port ethernet interfaces Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Sun, 19 Dec 1999 13:42:31 PST." References: Date: Sun, 19 Dec 1999 15:19:24 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Brian Beattie writes: : Anybody know of any currently available, that are supported by FreeBSD? No. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 14:38:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 2FE6C14DA5 for ; Sun, 19 Dec 1999 14:38:29 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id OAA48479 for ; Sun, 19 Dec 1999 14:38:28 -0800 (PST) To: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sun, 19 Dec 1999 13:39:18 -0800. <199912192139.NAA09232@apollo.backplane.com> Date: Sun, 19 Dec 1999 14:38:28 -0800 Message-ID: <48477.945643108@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912192139.NAA09232@apollo.backplane.com>, Matthew Dillon wrote: >:I'd like to just take a second and re-express my growing confusion on >:this whole topic. >: >:Why do you say that this complete-process-blocking effect only takes >:place in the case of disk reads?? Isn't a read a read? What difference >:does it make what the device type being read from is? >: >:Is there some piece of code burried somewhere in either libc or the >:kernel that checks each call to read(2) to find out if that is a disk >:drive you are reading from versus reading from a terminal or a network >:socket? >: >:I'm just trying to understand this stuff. > > There are certain I/O related operations which are assumed to not > block, even though the kernel *might* block on the temporarily. > > For example, when you open and read() from a file, you assume your > read() command will return reasonably quickly... What do you mean by ``you'' in this context? > ... > However, things like disk I/O are assumed to not block... Assumed by what exactly? Thank you for the elaborate answer, but you didn't really address my question. Is there code somewhere, perhaps within the libc implementation of read(2) that looks to see what kind of device I am reading from, and then does two different things if the read is for a disk file versus a read for a terminal? If so, and if that code operates in userland (as opposed to being in the kernel), then to a certain extent that kinda shoots the hell out of the old UNIX transparency notion that ``a file is a file is a file''. I'm not complaining about that mind you. I'm just noting it, and the fact that (for me at least) it makes me just slightly uneasy for reasons I can't quite put into words. > The current threads implementation has this problem because you have N > threads running under a single process. If one thread blocks on a disk > I/O then all the threads essentially block. The proposed new > threads implementation does not have this problem. Good. I gather from your other comments that the new threads implementation will indeed return us to a state where ``a file is a file is a file'' and where no special handling of different _kinds_ of files takes place (or needs to take place) within, for example libc read(2). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 14:49:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 6271B1515C for ; Sun, 19 Dec 1999 14:49:26 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id OAA48574 for ; Sun, 19 Dec 1999 14:49:26 -0800 (PST) To: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-reply-to: Your message of Sun, 19 Dec 1999 16:06:45 -0600. <19991219160645.E317@tar.com> Date: Sun, 19 Dec 1999 14:49:26 -0800 Message-ID: <48572.945643766@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991219160645.E317@tar.com>, "Richard Seaman, Jr." wrote: >On Sun, Dec 19, 1999 at 01:21:15PM -0800, Ronald F. Guilmette wrote: > >> It sounds to me like each and every time there is a thread context switch, >> some code in the library may have to execute a (perhaps enormous) call to >> select() or else to poll(). Yes? > >poll(). It used to use select(). And, not only at each thread >context switch, but each time it has to consider whether to >do a switch at all (eg. at the end of a timeslice). Bummer. I dunno if it goes without saying or not, but this certainly makes the current FreeBSD threads implementation highly unpalatable, except to support ported code which has been developed elsewhere and which is already written to assume the presence/availability of thread library primitives. Certainly, if I were starting out to write a brand new new multi-threaded application program specifically for execution on FreeBSD _today_, I'd either (a) wait for the new thread implementation to be ready or else (b) not use threads at all. (Actually, I guess there is a third option, i.e. writing my code to use the existing threads API, and then just hoping that the new threads implementation shows up before I was done coding my application.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 15: 9:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 480D114A2B for ; Sun, 19 Dec 1999 15:09:46 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40341>; Mon, 20 Dec 1999 10:00:56 +1100 Content-return: prohibited Date: Mon, 20 Dec 1999 10:09:22 +1100 From: Peter Jeremy Subject: CVS Log comments for large changes To: freebsd-hackers@FreeBSD.ORG Message-Id: <99Dec20.100056est.40341@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This might not belong on -hackers, but I'm not sure where this sort of discussion _does_ belong}. Occasionally, single CVS changes affect large numbers of files. The comments associated with those commits generally fall into 3 categories: 1) Import version x.y into vendor branch z 2) [Detailed discussion of change] 3) Implement xxx as discussed on freebsd-yyy I'm not concerned about the first change. Information regarding the specifics will normally be in a CHANGELOG or similar file associated with the change. The second commit style correctly documents what has been done, but leads to repository bloat by repeating the message in multiple locations. The third commit style solves the repo-bloat problem, but loses the reasoning behind the change. (It might be in one of the mailing list archives, but locating it in future may be difficult). I'd like to suggest that where a major change (one that needs more than a line or two of explanation) affects a significant number of files, the commit be performed in two pieces: Firstly a null commit to a convenient file associated with the change (eg a README or Makefile) including the full explanation behind the proposed commit in the log message. Secondly the actual change of all files, with the log message just referencing the file/version containing the detailled log message. In this way, the reasons for the change get stored within the repository, without bloating it. I believe the 'description first, then changes' order is better than the opposite order for two reasons: 1) This allows comments to be added to files that are going to be deleted. 2) The change commit can specify the already known version of the file containing the log message. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 15:11:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id 4F37415172 for ; Sun, 19 Dec 1999 15:11:36 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id RAA00450; Sun, 19 Dec 1999 17:11:30 -0600 (CST) (envelope-from dick) Date: Sun, 19 Dec 1999 17:11:30 -0600 From: "Richard Seaman, Jr." To: "Ronald F. Guilmette" Cc: hackers@FreeBSD.ORG Subject: FreeBSD Threads (was Re: Practical limit for number of TCP connections?) Message-ID: <19991219171130.A338@tar.com> References: <19991219160645.E317@tar.com> <48572.945643766@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <48572.945643766@monkeys.com>; from rfg@monkeys.com on Sun, Dec 19, 1999 at 02:49:26PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 19, 1999 at 02:49:26PM -0800, Ronald F. Guilmette wrote: > I dunno if it goes without saying or not, but this certainly makes > the current FreeBSD threads implementation highly unpalatable, except > to support ported code which has been developed elsewhere and which > is already written to assume the presence/availability of thread > library primitives. I wouldn't go that far. The current implementation is not nearly as good as it could be, but it works nicely for some reasonable range of applications. > Certainly, if I were starting out to write a brand new new multi-threaded > application program specifically for execution on FreeBSD _today_, I'd > either (a) wait for the new thread implementation to be ready or else > (b) not use threads at all. If user threads don't work for you, then the linuxthreads port (uses kernel threads) might. Its a POSIX style pthreads implementation, so when FreeBSD does "kernel threads", or the equivalent, if should be as easy (cross your fingers) as recompiling and relinking to a different library. > (Actually, I guess there is a third option, > i.e. writing my code to use the existing threads API, and then just hoping > that the new threads implementation shows up before I was done coding my > application.) Or code your application and use either user threads or linux (kernel) threads until the new threads library is available. Unless I misunderstand, all three (user, linux, and the "new") will (do) use POSIX pthread API's. Migration shouldn't be very hard. The new version might have more functionality, so you might need to recode slightly to take advantage of the wider range of options (eg. mixing PTHREAD_SCOPE_SYSTEM threads with PTHREAD_SCOPE_PROCESS threads), but only if you need the added functionality. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 15:54:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from msk1.mail.ru (mx1.mail.ru [194.67.23.32]) by hub.freebsd.org (Postfix) with ESMTP id 5BC9014BEA for ; Sun, 19 Dec 1999 15:54:34 -0800 (PST) (envelope-from kabaev@mail.ru) Received: from h0050da20495b.ne.mediaone.net ([24.218.93.188] helo=kan.ne.mediaone.net) by msk1.mail.ru with esmtp (Exim 3.02 #115) id 11zqDN-00038r-00 for freebsd-hackers@freebsd.org; Mon, 20 Dec 1999 02:58:17 +0300 Content-Length: 453 Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 19 Dec 1999 18:54:38 -0500 (EST) From: "Alexander N. Kabaev" To: freebsd-hackers@freebsd.org Subject: Page attribute table (PAT) support? Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there plans to add support for PAT on Intel P6 and AMD Athlon processors? This feature provides more flexible interface allowing to setup various memory cache modes on a page-by-page bases. It is much easier to program than MTRRs and does not suffer from their size/alignment limitations. Provided there are patches to support PAT in kernel, how it should be exposed to the user level code? Will something like mmprotect system call suffice? -Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 16:31: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles501.castles.com [208.214.165.65]) by hub.freebsd.org (Postfix) with ESMTP id 5E40214FF9 for ; Sun, 19 Dec 1999 16:31:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03909; Sun, 19 Dec 1999 16:34:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912200034.QAA03909@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bill Paul Cc: hackers@freebsd.org Subject: Re: USB ethernet hacking In-reply-to: Your message of "Sun, 19 Dec 1999 17:18:37 EST." <199912192218.RAA03775@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Dec 1999 16:34:37 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I have worked around this for now by hacking usbdi.c so that it polls > > > the controller interrupt/status register instead of tsleep()ing. I'm not > > > sure this is the best solution, but it's the only one that seems to work. > > > > why not use the async method? > > Because this is not an asynchronous task that I'm trying to do here. > I'm talking about reading and writing registers from the ethernet > controller. If this was a PCI device, I'd be using > bus_space_read_X()/bus_space_write_X() to read the registers directly. I > don't want to start reading a register and then come back a while later > to read the results. The code isn't meant to work like that. Unfortunately, given that your 'register read request' is being queued over what is basically a packet-switched network, you're going to have to change the way the code works so that it _can_ work like that. If you don't like it now, imagine how much less you're going to like, say, I2O or SystemIO... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 17: 0: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id A48C715118; Sun, 19 Dec 1999 16:59:58 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id UAA04092; Sun, 19 Dec 1999 20:04:07 -0500 From: Bill Paul Message-Id: <199912200104.UAA04092@skynet.ctr.columbia.edu> Subject: Re: USB ethernet hacking To: msmith@freebsd.org (Mike Smith) Date: Sun, 19 Dec 1999 20:04:05 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: <199912200034.QAA03909@mass.cdrom.com> from "Mike Smith" at Dec 19, 99 04:34:37 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2036 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Mike Smith had to walk into mine and say: > > > why not use the async method? > > > > Because this is not an asynchronous task that I'm trying to do here. > > I'm talking about reading and writing registers from the ethernet > > controller. If this was a PCI device, I'd be using > > bus_space_read_X()/bus_space_write_X() to read the registers directly. I > > don't want to start reading a register and then come back a while later > > to read the results. The code isn't meant to work like that. > > Unfortunately, given that your 'register read request' is being queued > over what is basically a packet-switched network, you're going to have to > change the way the code works so that it _can_ work like that. If you > don't like it now, imagine how much less you're going to like, say, I2O > or SystemIO... I need to be able to read/write registers in the MAC at interrupt context. I'm not trying to be stubborn: there's just no other way to do the things I need to do. If I get a transmit timeout and I need to flip the 'reset MAC' bit in one of the control registers, how am I supposed to do it? When a timeout fires and I have to check the PHY's link state or read the MAC stats counter registers, how am I supposed to do it? The hack that I made to usbdi.c seems to have fixed that problem for now, however I'm still not sure why I can't seem to transfer full 1500 byte frames without getting an I/O error. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 17: 1:47 1999 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 C5000151DE for ; Sun, 19 Dec 1999 17:01:45 -0800 (PST) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (cs1-gw.cs.binghamton.edu [128.226.171.72]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with SMTP id UAA15786 for ; Sun, 19 Dec 1999 20:01:43 -0500 (EST) Date: Sun, 19 Dec 1999 18:48:22 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: user-level asynchronous I/O 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 Is there such a thing called "user-level asynchronous i/o" in FreeBSD? I assume that the aio_read(), aio_write() stuff is kernel-based asynchronous i/o. SIGIO is also a kernel stuff. Thanks for any enlightment. -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 17: 5:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles501.castles.com [208.214.165.65]) by hub.freebsd.org (Postfix) with ESMTP id 1482814C04 for ; Sun, 19 Dec 1999 17:05:33 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04120; Sun, 19 Dec 1999 17:09:05 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912200109.RAA04120@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bill Paul Cc: hackers@freebsd.org Subject: Re: USB ethernet hacking In-reply-to: Your message of "Sun, 19 Dec 1999 20:04:05 EST." <199912200104.UAA04092@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Dec 1999 17:09:05 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > bus_space_read_X()/bus_space_write_X() to read the registers directly. I > > > don't want to start reading a register and then come back a while later > > > to read the results. The code isn't meant to work like that. > > > > Unfortunately, given that your 'register read request' is being queued > > over what is basically a packet-switched network, you're going to have to > > change the way the code works so that it _can_ work like that. If you > > don't like it now, imagine how much less you're going to like, say, I2O > > or SystemIO... > > I need to be able to read/write registers in the MAC at interrupt context. > I'm not trying to be stubborn: there's just no other way to do the things > I need to do. If I get a transmit timeout and I need to flip the 'reset MAC' > bit in one of the control registers, how am I supposed to do it? When a > timeout fires and I have to check the PHY's link state or read the MAC > stats counter registers, how am I supposed to do it? Build and queue the request, and have the callback handle completion. Use a state machine, or just fragment your code along the async boundaries. > The hack that I made to usbdi.c seems to have fixed that problem for now, > however I'm still not sure why I can't seem to transfer full 1500 byte > frames without getting an I/O error. I wonder if it's a limit on the payload size in a USB frame. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 17:15:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 179E414EDB; Sun, 19 Dec 1999 17:15:41 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 52D151CCF; Mon, 20 Dec 1999 09:15:37 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Tony Finch Cc: hackers@freebsd.org, jkh@freebsd.org Subject: Re: Practical limit for number of TCP connections? In-Reply-To: Message from Tony Finch of "Sun, 19 Dec 1999 23:55:22 GMT." Date: Mon, 20 Dec 1999 09:15:37 +0800 From: Peter Wemm Message-Id: <19991220011537.52D151CCF@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Finch wrote: > Peter Wemm wrote: > > > >I'm aware of boxes having been tested to ~100,000 connections if my memory > >serves correctly. I know there were problems going over 64k connections at > >one point due to a 16 bit reference counter in the routes. > > The fix for this hasn't been MFCed yet (rev 1.30 of sys/net/route.h). > A related problem with the ifa_refcnt field has been fixed. eep.. I thought this was all done for 3.4.. ouch.. On the other hand, to run that many connections generally requires the tcp timer enhancements or it spends a lot of time doing list processing. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 17:43:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id E8A3114C1A for ; Sun, 19 Dec 1999 17:43:38 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id SAA15271; Sun, 19 Dec 1999 18:43:38 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id SAA05670; Sun, 19 Dec 1999 18:43:37 -0700 Date: Sun, 19 Dec 1999 18:43:37 -0700 Message-Id: <199912200143.SAA05670@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Ronald F. Guilmette" Cc: hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-Reply-To: <43945.945560638@monkeys.com> References: <43945.945560638@monkeys.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Using a thread per connection has always been a bogus way of programming, > >it's easy, but it doesn't work very well. > > OK, even if nobody else does, I'll bite. Even something as lightweight as a thread is still too heavy for large systems. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 19:14: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.33.127]) by hub.freebsd.org (Postfix) with ESMTP id D33F614C20 for ; Sun, 19 Dec 1999 19:14:06 -0800 (PST) (envelope-from thorpej@lestat.nas.nasa.gov) Received: from lestat (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.8.8/8.6.12) with ESMTP id TAA14692; Sun, 19 Dec 1999 19:13:37 -0800 (PST) Message-Id: <199912200313.TAA14692@lestat.nas.nasa.gov> To: Bill Paul Cc: julian@whistle.com (Julian Elischer), hackers@FreeBSD.ORG Subject: Re: USB ethernet hacking Reply-To: Jason Thorpe From: Jason Thorpe Date: Sun, 19 Dec 1999 19:13:36 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Dec 1999 17:18:37 -0500 (EST) Bill Paul wrote: > Because this is not an asynchronous task that I'm trying to do here. > I'm talking about reading and writing registers from the ethernet > controller. If this was a PCI device, I'd be using > bus_space_read_X()/bus_space_write_X() to read the registers directly. I > don't want to start reading a register and then come back a while later > to read the results. The code isn't meant to work like that. All this means is that you can't structure a USB Ethernet driver like a traditional directly-connected Ethernet driver. NetBSD supports a SCSI Ethernet adapter, and it works just fine (it's the only way for those PC532 owners to talk to Ethernet :-) -- Jason R. Thorpe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 19:15:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 0CA4915071 for ; Sun, 19 Dec 1999 19:15:08 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA03931; Sun, 19 Dec 1999 19:14:56 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA30474; Sun, 19 Dec 1999 19:14:54 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 19 Dec 1999 19:14:54 -0800 (PST) Message-Id: <199912200314.TAA30474@vashon.polstra.com> To: rfg@monkeys.com Subject: Re: Practical limit for number of TCP connections? In-Reply-To: <42829.945549667@monkeys.com> References: <42829.945549667@monkeys.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <42829.945549667@monkeys.com>, Ronald F. Guilmette wrote: > > The other way is just have your server be a single thread/process, and to > have it keep one big list of all of the connections (i.e. socket fds) that > it has open at present. Then it just executes mail loop, over and over > again. At the top of the main look is one big honkin' call to select() > in which you find out which of your connections is ready to be read or > written. Then you go off and read/write those as appropriate, and then > just come back and do the big select() again. (You could do this using > calls to poll() instead of calls to select(), and that might be a bit > more efficient.) > > The only real problem with doing things this way is that you have to diddle > some things to make sure the bit arrays that you pass to select() are big > enough to handle the maximum number of connections you ever anticipate > having to service/maintain at one time. [... etc] The "eventlib" package is pretty nice for this style of programming. It takes care of all these gory details for you. It's part of BIND (www.isc.org) and it might be distributed separately too -- I forget. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 19:25:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9155315242 for ; Sun, 19 Dec 1999 19:25:07 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA03976; Sun, 19 Dec 1999 19:25:05 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA30555; Sun, 19 Dec 1999 19:25:02 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 19 Dec 1999 19:25:02 -0800 (PST) Message-Id: <199912200325.TAA30555@vashon.polstra.com> To: rfg@monkeys.com Subject: Re: Practical limit for number of TCP connections? In-Reply-To: <48477.945643108@monkeys.com> References: <48477.945643108@monkeys.com> Organization: Polstra & Co., Seattle, WA Cc: hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <48477.945643108@monkeys.com>, Ronald F. Guilmette wrote: > > Is there code somewhere, perhaps within the libc implementation of read(2) > that looks to see what kind of device I am reading from, and then does two > different things if the read is for a disk file versus a read for a terminal? No. It's simply that the read() and write() system calls are willing to return EAGAIN or only do a portion of the requested I/O for pipes and sockets and terminals, but they are not willing to do that for disk I/O. There is a long-standing distinction in Unix between "slow" I/O devices and "fast" ones. Disks are "fast" ones, and the process always blocks until the full I/O has completed. This is not some kind of brokenness particular to FreeBSD; it's the way Unix has always behaved. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 20:49: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from guppy.pond.net (guppy.pond.net [205.240.25.2]) by hub.freebsd.org (Postfix) with ESMTP id 7814515266; Sun, 19 Dec 1999 20:49:03 -0800 (PST) (envelope-from ptacek@dashmail.net) Received: from Ptacek (rc1s7p8.dashmail.net [216.36.33.80]) by guppy.pond.net (8.9.3/8.9.3) with SMTP id UAA22312; Sun, 19 Dec 1999 20:42:25 -0800 (PST) Message-ID: <001501bf4aa5$45e29640$502124d8@Ptacek> From: "Ptacek" To: , Subject: DES routines? Date: Sun, 19 Dec 1999 20:47:07 -0800 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am looking for some routines to perform DES encryption in electronic code book mode. I have found the ecb_cyrpt function, however when I try and use it the buffer is not encrypted. Am I missing something, do these functions not work, and is there a better way of doing this? Below I have included a basic test program I am using to try and get the encryption working. Thanks for any help, - Chris ---------------------------------------------------- #include #include #include int main() { char testbuf[16] = {0x00,0x01,0x02,0x03,0x04, 0x05,0x06,0x07,0x08,0x09, 0x0a,0x0b,0x0c,0x0d,0x0e, 0x0f} ; char testkey[8] = {0x01,0x02,0x03,0x04, 0x05,0x06,0x07,0x08} ; int status ; int i ; des_setparity(testkey) ; status = ecb_crypt(testkey, testbuf, 16, DES_HW | DES_ENCRYPT) ; printf("status=%d\n", status) ; for(i=0; i<16; i++) { printf("%02x ", (unsigned char)testbuf[i]) ; } exit(0) ; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 21:27:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 03671152BA for ; Sun, 19 Dec 1999 21:26:32 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id WAA26352; Sun, 19 Dec 1999 22:26:19 -0700 (MST) Received: from ip-83-008.prc.primenet.com(207.218.83.8), claiming to be "pinyon.org" via SMTP by smtp01.primenet.com, id smtpdAAADGaaxZ; Sun Dec 19 22:26:13 1999 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id E078A78; Sun, 19 Dec 1999 22:26:08 -0700 (MST) X-Mailer: exmh version 2.1.0 09/18/1999 To: "Richard Seaman, Jr." Cc: "Ronald F. Guilmette" , hackers@FreeBSD.ORG Subject: Re: FreeBSD Threads (was Re: Practical limit for number of TCP connections?) In-Reply-To: Message from "Richard Seaman, Jr." of "Sun, 19 Dec 1999 17:11:30 CST." <19991219171130.A338@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Dec 1999 22:26:08 -0700 From: "Russell L. Carter" Message-Id: <19991220052608.E078A78@pinyon.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %On Sun, Dec 19, 1999 at 02:49:26PM -0800, Ronald F. Guilmette wrote: % %> I dunno if it goes without saying or not, but this certainly makes %> the current FreeBSD threads implementation highly unpalatable, except %> to support ported code which has been developed elsewhere and which %> is already written to assume the presence/availability of thread %> library primitives. % %I wouldn't go that far. The current implementation is not nearly %as good as it could be, but it works nicely for some reasonable %range of applications. Adding to Richard's comments: libc_r threads work damn fine for wide variety of applications. There are specific user-space issues which preclude using a lot of POSIX RT stuff, and libc_r threads naturally don't scale to multiple processors. But they're relatively lightweight :-). And I believe most of the essential interfaces are there, and not harmful if used. %> Certainly, if I were starting out to write a brand new new multi-threaded %> application program specifically for execution on FreeBSD _today_, I'd %> either (a) wait for the new thread implementation to be ready or else %> (b) not use threads at all. % %If user threads don't work for you, then the linuxthreads port %(uses kernel threads) might. Its a POSIX style pthreads implementation, %so when FreeBSD does "kernel threads", or the equivalent, if should %be as easy (cross your fingers) as recompiling and relinking %to a different library. Yep. You might try the information on www.pinyon.org/ace to see any differences in compilation requirements. %> (Actually, I guess there is a third option, %> i.e. writing my code to use the existing threads API, and then just hoping %> that the new threads implementation shows up before I was done coding my %> application.) I build against both existing interfaces, and adhere to the several POSIX specs. It seems to work fine. Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 21:38:58 1999 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 E8C3015171 for ; Sun, 19 Dec 1999 21:38:56 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id VAA14658; Sun, 19 Dec 1999 21:38:50 -0800 (PST) Date: Sun, 19 Dec 1999 21:38:49 -0800 (PST) From: Julian Elischer To: Bill Paul Cc: hackers@freebsd.org Subject: Re: USB ethernet hacking In-Reply-To: <199912192218.RAA03775@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 19 Dec 1999, Bill Paul wrote: > > > > We just copied the data from the mbuf into a dedicated > > buffer and freed the mbuff immediatly. > > Did you just allocate a buffer with malloc() (or contigmalloc()), or > did you use usbd_alloc_buffer()? ummm I don't have the driver with me here. Doug Ambrisko has is so we'll send it to you as soon as he reads this I guess. I don't think there was anything special about the memory used for a buffer. > > -Bill > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 22:45:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 78C2A14D73; Sun, 19 Dec 1999 22:45:45 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id WAA12779; Sun, 19 Dec 1999 22:23:54 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id WAA20346; Sun, 19 Dec 1999 22:23:53 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA18279; Sun, 19 Dec 99 22:23:49 PST Message-Id: <385DCBDA.5F13D43D@softweyr.com> Date: Sun, 19 Dec 1999 23:25:30 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Chrisy Luke Cc: Roger Hardiman , hackers@FreeBSD.ORG, multimedia@FreeBSD.ORG Subject: Re: Multi Head XFree86 VGA card recomendations wanted References: <3858C600.41C6@cs.strath.ac.uk> <385918DA.8F7F84D@softweyr.com> <19991219180022.A17099@flix.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chrisy Luke wrote: > > Wes Peters wrote (on Dec 16): > > Have you considered buying Metro-X? It supports up to 4 screens on just > > about any combination of AGP and PCI Matrox cards. For more information, > > see http://www.metrolink.com/productindex.html and look for Multi-Headed > > Display Support. Metro-X is only $39. > > Someting I'd be keen to know is the extent of support for the new > G100 MMS (Quad-head). Four G100's on one card, it seems. Works well > with NT (puke) - with the limitation that all the displays need to run > with the same resolution (very very sucky when you have an odd combination > of monitors). You want me to call them? Do we have any FreeBSD multimedia members physically co-located with MetroLink, so it'll be a local call? -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 22:59: 3 1999 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 2CC8114EC9 for ; Sun, 19 Dec 1999 22:59:01 -0800 (PST) (envelope-from imp@harmony.village.org) 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 XAA10049 for ; Sun, 19 Dec 1999 23:58:59 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA11677 for ; Sun, 19 Dec 1999 23:58:59 -0700 (MST) Message-Id: <199912200658.XAA11677@harmony.village.org> To: hackers@freebsd.org Subject: When can I call kthread_create? Date: Sun, 19 Dec 1999 23:58:59 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When can I call kthread_create? I tried in the driver attach, but that failed in fdcopy() calling vref with a NULL pointer. I tried calling at the end of config (in config_intrhook_establish called function), but no dice. I see that this makes its calls at SI_SUB_INT_CONFIG_HOOKS (0xa800000 in init sequence). I'd like to run it before SI_SUB_COM_ROOT_CONF, but it doesn't look like I could call it until SI_SUB_KTHREAD_INIT, which is too late to allow an insert event to happen to allow a root device to be in a pccard/cardbus (well, I could poll the device in attach routine if I'm not already doing this, so that restriction might not be a big deal). Is this analysis accurate? Do I have to wait until at least SI_SUB_KTHREAD_INIT? Or is INIT special and I'd have to wait until after all the "special" processes are created? Thanks for your help in this matter. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Dec 19 23:43:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id BD30714BCF for ; Sun, 19 Dec 1999 23:43:53 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id XAA13298; Sun, 19 Dec 1999 23:43:21 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id XAA01510; Sun, 19 Dec 1999 23:43:21 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA19510; Sun, 19 Dec 99 23:43:18 PST Message-Id: <385DDE7A.1A0ED466@softweyr.com> Date: Mon, 20 Dec 1999 00:44:58 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Matthew Dillon Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <19991218225758.A23729@futuresouth.com> <199912190556.AAA08484@whizzo.transsys.com> <199912191943.LAA06826@apollo.backplane.com> <385D47D3.FCEE9EAB@softweyr.com> <199912192127.NAA09156@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > > :> I really hate these switching regulated DC wall plugs. They always use > :> cheap caps in them to save money and then don't bother adding any > :> protection to the motherboard. I prefer AC wall plugs or unregulated DC > :> wall plugs and then a small switching regulator on the motherboard. That > :> way you can throw anything up to 40V into it and it will still work. > : > :And nearly double the cost of the item, and make it much more difficult > :(read as "expensive") to pass FCC/EC requirements. You may prefer such > :things, but you're not willing to pay for them. (Generic "you" meaning > :"everyone" here). > > This is not true at all. Oh, and how many products have you passed through FCC/EC/Japanese environmental certification? None, apparently. > First, the U.L. is handled by the wall adapter. > Second, getting FCC certification for a small device whos U.L. is > arleady handled by a wall adapter is *trivial*. Right, becasue you don't have to certify the power supply, you just buy one that's already certified. If your "unit under test" requires 12vdc input, you can provide it with any form of 12vdc power you want. At our test facility, the most common is a car battery 200 ft away. The power supplies are often the hardest part to certify, and the major reason why most networking equipment is on FCC Class B certified, rather than Class A. For those of you who are wondering why this matters, it means it is illegal for you to use the equipment IN YOUR HOME anywhere in the USA if it interferes with any radio or TV reception anywhere. > Moving the switching > supply inside verses depending on a DC adapter does not make FCC cert. > more difficult. You're wrong. It nearly always requires adding some sort of faraday cage around the power supply, and often around the entire enclosure due to the difficulty in isolating the 60 Hz harmonics within the power supply in small equipment. For a small, cheap hub or switch this just kills the bill of materials. The Intel 8-port switch was already noisy enough they had to paint the inside of the case with copper spray; an internal power supply would have killed the product entirely due to the cost of the casing material. > There is an expense in the power supply verses the cheap crap you get > in a DC regulated wall adapter - well, doh! That's why it's better! Yup, and you'd be amazed the number of people that will buy the $99 switch over the $139 (or even $109) switch, even if they don't know the difference is the wall-wart. Other factors (like brand recognition) aside, that number is vanishingly close to "all of them." -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 0:43:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from urquell.pilsnet.sunet.se (urquell.pilsnet.sunet.se [192.36.125.77]) by hub.freebsd.org (Postfix) with ESMTP id 365AD15100 for ; Mon, 20 Dec 1999 00:43:12 -0800 (PST) (envelope-from bd@urquell.pilsnet.sunet.se) Received: (from bd@localhost) by urquell.pilsnet.sunet.se (8.9.1/8.9.1) id JAA08086; Mon, 20 Dec 1999 09:43:10 +0100 (CET) (envelope-from bd) To: freebsd-hackers@freebsd.org Subject: UTC time in crontabs From: Bjorn Danielsson Date: 20 Dec 1999 09:43:10 +0100 Message-ID: Lines: 16 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 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 I have made a small patch (about 10 lines of code) to "cron" that lets people choose between localtime and gmtime for their crontab entries. The choice is made depending on the setting of an environment variable in the crontab file. The cost is a factor 2 for the tiny amount of work that cron does when it checks all the crontab entries every minute. Any interest in this? I finally got tired of having to use local daylight saving time for crontabs after seeing my nightly statistics-gathering scripts having to deal with 23 hour days, 25 hour days, some scripts running twice the same night, or not running at all, etc. -- BjЖrn Danielsson KTHNOC / Swedish University Network (mail me for my real e-mail address) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 1:31:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 1FCD514F77 for ; Mon, 20 Dec 1999 01:31:30 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id BAA13734; Mon, 20 Dec 1999 01:30:34 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id BAA03387; Mon, 20 Dec 1999 01:30:34 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA21699; Mon, 20 Dec 99 01:30:26 PST Message-Id: <385DF796.FD98D61E@softweyr.com> Date: Mon, 20 Dec 1999 02:32:06 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Warner Losh Cc: Brian Beattie , freebsd-hackers@FreeBSD.ORG Subject: Re: Parallel-port ethernet interfaces References: <199912192219.PAA08250@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message Brian Beattie writes: > : Anybody know of any currently available, that are supported by FreeBSD? > > No. Yes. Another FreeBSD machine, with an ethernet interface and a parallel port for running PLIP over. They are kind of large, though. ;^) -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 1:50:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id 610F71530F for ; Mon, 20 Dec 1999 01:50:25 -0800 (PST) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id UAA41842 for hackers@freebsd.org; Mon, 20 Dec 1999 20:03:27 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199912201003.UAA41842@mail.theinternet.com.au> Subject: Applixware To: hackers@freebsd.org Date: Mon, 20 Dec 1999 20:03:27 +1000 (EST) 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 To whom do I send Kudos for Applixware? All I need is an icon for my WindowMaker Dock, and I'll be v. happy d8) -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 2:12: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tardis.mx.com.au (tardis.mx.com.au [203.34.34.73]) by hub.freebsd.org (Postfix) with ESMTP id 7945A15163 for ; Mon, 20 Dec 1999 02:11:52 -0800 (PST) (envelope-from justin@tardis.mx.com.au) Received: from localhost (justin@localhost) by tardis.mx.com.au (8.9.3/8.9.3) with ESMTP id UAA01172 for ; Mon, 20 Dec 1999 20:41:42 +1030 (CST) (envelope-from justin@tardis.mx.com.au) Date: Mon, 20 Dec 1999 20:41:41 +1030 (CST) From: Justin Hawkins To: freebsd-hackers@freebsd.org Subject: Serial boot prompt messages and a modem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I've recently had .. ahem .. fun trying to get my headless FreeBSD box to spit messages at the console. I've got the kernel doing it right, but not the boot loaders. The boot loader will print to the serial device - but it won't load my kernel :-( I haven't exhausted all oppurtunities here yet - this isn't a cry for help on that. The reason I need to play around with the boot loaders is that I need the serial console on COM2. I have a modem on COM1. Before you ask, I can't swap them over easily, I'd need to swap the connectors internally or buy some 9-25 adaptors. But I digress. I think (I am not positive on this) that if the boot loader talks to a modem in command mode with echo on, it gets confused and won't boot any further. Is this a known problem? Is there enough room in there for some code, which checks for this? IE if the first line output to the serial device == the first input (some version string probably) then it just ignores it and does the default action? Sorry about the vagueness - I didn't have time to test this or gain any real empirical evidence - I needed to get the machine back in action ASAP. Please CC any replies - I'm not on this list. Thanks. - Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 2:51:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 03249152EF; Mon, 20 Dec 1999 02:51:20 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id LAA22236; Mon, 20 Dec 1999 11:51:10 +0100 (CET) (envelope-from asmodai) Date: Mon, 20 Dec 1999 11:51:10 +0100 From: Jeroen Ruigrok van der Werven To: Ptacek Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: DES routines? Message-ID: <19991220115109.R3961@lucifer.bart.nl> References: <001501bf4aa5$45e29640$502124d8@Ptacek> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <001501bf4aa5$45e29640$502124d8@Ptacek>; from ptacek@dashmail.net on Sun, Dec 19, 1999 at 08:47:07PM -0800 Organisation: bART Internet Services B.V. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991220 05:55], Ptacek (ptacek@dashmail.net) wrote: >I am looking for some routines to perform DES encryption in electronic code >book mode. >I have found the ecb_cyrpt function, however when I try and use it the >buffer is not encrypted. apropos des and look at the manpages it returns. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / Tel: +31 - (0) 10 - 240 39 70 VIA NET.WORKS Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 5:20:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (dialfwn05.fwn.rug.nl [129.125.32.155]) by hub.freebsd.org (Postfix) with ESMTP id 5258C152C0 for ; Mon, 20 Dec 1999 05:20:44 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id OAA00430; Mon, 20 Dec 1999 14:16:36 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Mon, 20 Dec 1999 14:16:36 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: USB ethernet hacking In-Reply-To: <199912192103.QAA03584@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have worked around this for now by hacking usbdi.c so that it polls > the controller interrupt/status register instead of tsleep()ing. I'm not > sure this is the best solution, but it's the only one that seems to work. It isn't. You don't want to be polling for 2msecs for every register transfer. The 2 msecs is due to the framing of the transfers and _nothing_ can be done about that. You'll have to live with that. > Tracing down the error shows that the uhci driver is getting an error > status of 0x500000, which is apparently the logical OR of two error bits: > "babble" and "stall." I have the Intel UHCI spec document and it mentions > these errors, however it doesn't seem to say what causes them, how to > clear them or, more importantly, how to avoid them. If I could just > figure out how to get this thing to handle these "large" transfers, I > would be a happy camper. Please compile your kernel with UHCI_DEBUG and set the uhcidebug in the header of uhci.c to 11 or greater. Then look for uhci_idone. That should show what the error exactly is. If it is babble we have a piece of broken software. If it is NAK then you should set the timeout to a larger value. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 5:21: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (dialfwn05.fwn.rug.nl [129.125.32.155]) by hub.freebsd.org (Postfix) with ESMTP id 8981B152EC; Mon, 20 Dec 1999 05:20:48 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id OAA00422; Mon, 20 Dec 1999 14:07:23 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Mon, 20 Dec 1999 14:07:23 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Mike Smith Cc: Bill Paul , hackers@FreeBSD.ORG Subject: Re: USB ethernet hacking In-Reply-To: <199912200034.QAA03909@mass.cdrom.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 Your register read will take at least 1msec. That is the time between scheduling the transfer and the interrupt being triggered for completion. But typically it will take 2msecs. Nick > > Because this is not an asynchronous task that I'm trying to do here. > > I'm talking about reading and writing registers from the ethernet > > controller. If this was a PCI device, I'd be using > > bus_space_read_X()/bus_space_write_X() to read the registers directly. I > > don't want to start reading a register and then come back a while later > > to read the results. The code isn't meant to work like that. > > Unfortunately, given that your 'register read request' is being queued > over what is basically a packet-switched network, you're going to have to > change the way the code works so that it _can_ work like that. If you > don't like it now, imagine how much less you're going to like, say, I2O > or SystemIO... > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 5:21:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (dialfwn05.fwn.rug.nl [129.125.32.155]) by hub.freebsd.org (Postfix) with ESMTP id 4161814BE4 for ; Mon, 20 Dec 1999 05:21:17 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id OAA00432; Mon, 20 Dec 1999 14:18:11 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Mon, 20 Dec 1999 14:18:11 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Julian Elischer Cc: Bill Paul , hackers@FreeBSD.ORG Subject: Re: USB ethernet hacking In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I don't think there was anything special about the memory used for > a buffer. There isn't. All i386 mem is DMA-able. I still have to make things work with bus_dma and friends. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 7:10:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from linux.ssc.nsu.ru (linux.ssc.nsu.ru [193.124.209.130]) by hub.freebsd.org (Postfix) with SMTP id 7695B14E4A for ; Mon, 20 Dec 1999 07:10:06 -0800 (PST) (envelope-from danfe@inet.ssc.nsu.ru) Received: (qmail 8142 invoked from network); 20 Dec 1999 15:09:39 -0000 Received: from inet.ssc.nsu.ru (62.76.110.12) by hub.freebsd.org with SMTP; 20 Dec 1999 15:09:39 -0000 Received: from localhost (danfe@localhost) by inet.ssc.nsu.ru (8.8.7/8.8.7) with ESMTP id VAA28378 for ; Mon, 20 Dec 1999 21:09:20 +0600 Date: Mon, 20 Dec 1999 21:09:20 +0600 (NOVT) From: "Alexey N. Dokuchaev" To: freebsd-hackers@freebsd.org Subject: Terminal colors 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! Say I want to change the man colors when I read mans at the console. More precisely, I don't like that underlined text shows up as reversed (black letter on while(grey,7) backround). How (and where) do I need to say that I want, say, yellow on black instead of reversed when displaying underlined-supposed-to-be text. Any help is greatly appreciated. ./danfe P.S. Please reply directly, since I am not the member of this list (yet ;-). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 7:12:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (dialfwn05.fwn.rug.nl [129.125.32.155]) by hub.freebsd.org (Postfix) with ESMTP id 52B3614D46 for ; Mon, 20 Dec 1999 07:12:53 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id PAA00533; Mon, 20 Dec 1999 15:09:00 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Mon, 20 Dec 1999 15:09:00 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: USB ethernet hacking In-Reply-To: <199912192103.QAA03584@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > However that's not my biggest problem. My biggest problem is getting > transfers over 1100 bytes or so to work reliably. My initial scheme > for transmitting and receiving packets was to set up asynchronous > transfers with callbacks. Packets are sent over bulk transfer endpoints > (one for RX, one for TX). For TX, I would set up a transfer and initiate > it, then wait until the callback is called to free the mbuf containing > the packet data. This seemed to work, but only for transfers around > 1000 to 1100 bytes or so. Trying to transfer packets of 1200 bytes or > more always seemed to yield an "IOERROR" error. I switched the packet > transmission code to use synchronous transfers (i.e. waiting for the > transfer to complete before moving on) and this seemed to help: I could > now get transmissions up to 1500 bytes to work without errors. This sounds to me like the device wants the xfer all in one go, occupying the best part of two USB frames. Why the switch to synchronous transfers changes things I don't know, but it might be coincidental. > However, I have the same problem now with received packets: trying to > receive a frame larger than 1100 bytes also causes an IOERROR, however > I can't use a synchronous transfer here since that would cause the kernel > to freeze in its tracks waiting for a packet. Would it be possible to limit the MTU length on the ethernet network to something less then 1000 bytes (the USB frame length)? Just to make sure you get the rest working before addressing this problem. > Tracing down the error shows that the uhci driver is getting an error > status of 0x500000, which is apparently the logical OR of two error bits: > "babble" and "stall." I have the Intel UHCI spec document and it mentions > these errors, however it doesn't seem to say what causes them, how to > clear them or, more importantly, how to avoid them. If I could just > figure out how to get this thing to handle these "large" transfers, I > would be a happy camper. BABBLE means that the device is transmitting more than it should be. It indicates a protocol or firmware error. You'll have to reset the device to bring it into a known state. At that point, the total length is not valid. > I put a copy of my current code at: > > http://www.freebsd.org/~wpaul/ADMtek/USB/4.0 line 928: USBD_SHORT_XFER_OK on outgoing transfers is useless. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 7:13: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (dialfwn05.fwn.rug.nl [129.125.32.155]) by hub.freebsd.org (Postfix) with ESMTP id 5276414EF3 for ; Mon, 20 Dec 1999 07:13:05 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id OAA00517; Mon, 20 Dec 1999 14:50:23 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Mon, 20 Dec 1999 14:50:23 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Bill Paul Cc: hackers@FreeBSD.ORG Subject: Re: USB ethernet hacking In-Reply-To: <199912192103.QAA03584@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > P.S.: Please don't write me asking for help getting your USB ethernet > adapter work with FreeBSD. Don't ask me when/if the driver will > be done. Don't ask me if your favorite adapter will be supported. > Don't ask me how to make the code work with FreeBSD 3.x. :-))) What's wrong? Delete button ain't working? The problem of usbd_abort_pipe is caused by the following code: if (status == USBD_CANCELLED) { usbd_setup_xfer(xfer, sc->aue_ep[AUE_ENDPT_RX], sc, sc->aue_rx_buf, 1536, USBD_SHORT_XFER_OK, USBD_NO_TIMEOUT, aue_rxeof); usbd_transfer(xfer); splx(s); return; } USBD_CANCELLED is the error code returned when the transfer was cancelled by abort_pipe. It might mean 'your dead, go away'. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 9: 6:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from www.geocrawler.com (sourceforge.net [209.81.8.17]) by hub.freebsd.org (Postfix) with ESMTP id 8306415330 for ; Mon, 20 Dec 1999 09:06:08 -0800 (PST) (envelope-from nobody@www.geocrawler.com) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id JAA31593; Mon, 20 Dec 1999 09:06:09 -0800 Date: Mon, 20 Dec 1999 09:06:09 -0800 Message-Id: <199912201706.JAA31593@www.geocrawler.com> To: freebsd-hackers@freebsd.org Subject: splimp for PCI From: "Alex" Reply-To: "Alex" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Alex" Be sure to reply to that address. Hello, I'm little confuse to using splimp/splx in driver that support PCI board. IRQ is shared for PCI. Is using splimp can cause for some problem? Thank a lot Alex Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 9:29:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from guppy.pond.net (guppy.pond.net [205.240.25.2]) by hub.freebsd.org (Postfix) with ESMTP id 9F49E15315; Mon, 20 Dec 1999 09:29:43 -0800 (PST) (envelope-from ptacek@dashmail.net) Received: from Ptacek (rc1s7p8.dashmail.net [216.36.33.80]) by guppy.pond.net (8.9.3/8.9.3) with SMTP id JAA14659; Mon, 20 Dec 1999 09:22:43 -0800 (PST) Message-ID: <023501bf4b0f$8332cb40$502124d8@Ptacek> From: "Ptacek" To: "Jeroen Ruigrok van der Werven" Cc: , References: <001501bf4aa5$45e29640$502124d8@Ptacek> <19991220115109.R3961@lucifer.bart.nl> Subject: Re: DES routines? Date: Mon, 20 Dec 1999 09:27:36 -0800 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well I tried that, but the only encryption I find are the encrypt and the ecb_crypt routines. The ecb_crypt is what I have been using, but I can't get it to encrypt anything. So then I tried the encrypt routine, no luck either. when I try and compile I get an error saying that encrypt is not present on the system (I did install the des stuff from /stand/ sysinstall). Thanks, Chris ----- Original Message ----- From: Jeroen Ruigrok van der Werven To: Ptacek Cc: ; Sent: Monday, December 20, 1999 2:51 AM Subject: Re: DES routines? > -On [19991220 05:55], Ptacek (ptacek@dashmail.net) wrote: > >I am looking for some routines to perform DES encryption in electronic code > >book mode. > >I have found the ecb_cyrpt function, however when I try and use it the > >buffer is not encrypted. > > apropos des and look at the manpages it returns. > > -- > Jeroen Ruigrok van der Werven Network- and systemadministrator > bART Internet Services / > Tel: +31 - (0) 10 - 240 39 70 VIA NET.WORKS Netherlands > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 9:36:35 1999 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 5275214A27 for ; Mon, 20 Dec 1999 09:36:33 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id JAA27190; Mon, 20 Dec 1999 09:36:31 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id JAA45601; Mon, 20 Dec 1999 09:35:46 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199912201735.JAA45601@whistle.com> Subject: Re: USB ethernet hacking In-Reply-To: from Julian Elischer at "Dec 19, 99 09:38:49 pm" To: julian@whistle.com (Julian Elischer) Date: Mon, 20 Dec 1999 09:35:46 -0800 (PST) Cc: wpaul@skynet.ctr.columbia.edu, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (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 Julian Elischer writes: | | | On Sun, 19 Dec 1999, Bill Paul wrote: | > > | > > We just copied the data from the mbuf into a dedicated | > > buffer and freed the mbuff immediatly. | > | > Did you just allocate a buffer with malloc() (or contigmalloc()), or | > did you use usbd_alloc_buffer()? | | ummm I don't have the driver with me here. | | Doug Ambrisko has is so we'll send it to you as soon as he reads this I | guess. Technical note, device only has an internal 15*64 (960) byte buffer. 1500 MTU's work fine and no performance hit over a 900 byte MTU. We just let the USB stack do what it has to do, we only talk to it in complete ethernet packets. http://www.ambrisko.com/doug/udbp.tgz From the README: Apply the patch relative /usr/src Add udbp to kernel or do kld thing. Once the device is up use ngctl (netgraph control) to connect it to an interface (this could be done via usbd.conf). ngctl connect udbp0: ng0: data inet || ngctl mkpeer udbp0: iface data inet ifconfig ng0 192.168.1.1 192.168.1.2 Works with Anchor EzLink and with minor change should support NetChip devices. You will have to add the device & vendor id info. Nick gave us the raw USB code, Julian supplied the netgraph code and I helped bug fix and bridge the gaps. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 11:49:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B21014A1F for ; Mon, 20 Dec 1999 11:49:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA16719; Mon, 20 Dec 1999 11:49:45 -0800 (PST) (envelope-from dillon) Date: Mon, 20 Dec 1999 11:49:45 -0800 (PST) From: Matthew Dillon Message-Id: <199912201949.LAA16719@apollo.backplane.com> To: Wes Peters Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <19991218225758.A23729@futuresouth.com> <199912190556.AAA08484@whizzo.transsys.com> <199912191943.LAA06826@apollo.backplane.com> <385D47D3.FCEE9EAB@softweyr.com> <199912192127.NAA09156@apollo.backplane.com> <385DDE7A.1A0ED466@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :"everyone" here). :> :> This is not true at all. : :Oh, and how many products have you passed through FCC/EC/Japanese environmental :certification? None, apparently. Four in the last 15 years. I've been involved with in-home electronic management systems and believe me, all that shit needs FCC and UL. :> supply inside verses depending on a DC adapter does not make FCC cert. :> more difficult. : :You're wrong. It nearly always requires adding some sort of faraday cage :around the power supply, and often around the entire enclosure due to the :difficulty in isolating the 60 Hz harmonics within the power supply in :small equipment. For a small, cheap hub or switch this just kills the : :Wes Peters Softweyr LLC :wes@softweyr.com http://softweyr.com/ This is old news - modern switching power supplies (and we are talking basically a chip, an inductor, and two big caps here) switch at 50 KHz or higher, which makes things a whole lot easier. No 60Hz humm, no vibration - hell, you can even run the frequency up past 100 MHz and not hear a peep out of it. Modern switching power supply chips also have most of the shutdown circuitry required, including temperature and current limiting, slow-start, and other features. Add in few small caps or perhaps a ferrite bead or two to filter out HF on the DC output and you are all done. Whoopie. Whoopie. The only time we've ever needed a faraday cage has been in a cable network unit for a hotel, and the video switching channels for the in-home unit - to protect sensitive RF circuitry from the rest of the world. If there is a specific reason you believe that putting a small switching supply inside the box requires extra FCC work, I'm all ears. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 12:24:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 81A9314A2B for ; Mon, 20 Dec 1999 12:24:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA17008; Mon, 20 Dec 1999 12:24:30 -0800 (PST) (envelope-from dillon) Date: Mon, 20 Dec 1999 12:24:30 -0800 (PST) From: Matthew Dillon Message-Id: <199912202024.MAA17008@apollo.backplane.com> To: Matthew Dillon Cc: Wes Peters , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <19991218225758.A23729@futuresouth.com> <199912190556.AAA08484@whizzo.transsys.com> <199912191943.LAA06826@apollo.backplane.com> <385D47D3.FCEE9EAB@softweyr.com> <199912192127.NAA09156@apollo.backplane.com> <385DDE7A.1A0ED466@softweyr.com> <199912201949.LAA16719@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : or higher, which makes things a whole lot easier. No 60Hz humm, no : vibration - hell, you can even run the frequency up past 100 MHz and ^^^^ Needless to say I meant 100 KHz here, not 100 MHz. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 12:34:58 1999 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 7E0F614CB2 for ; Mon, 20 Dec 1999 12:34:52 -0800 (PST) (envelope-from imp@harmony.village.org) 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 NAA12476; Mon, 20 Dec 1999 13:34:50 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA18342; Mon, 20 Dec 1999 13:34:50 -0700 (MST) Message-Id: <199912202034.NAA18342@harmony.village.org> To: Matthew Dillon Subject: Re: Cool little 100BaseTX switch - they're coming down in price Cc: Wes Peters , freebsd-hackers@FreeBSD.ORG In-reply-to: Your message of "Mon, 20 Dec 1999 12:24:30 PST." <199912202024.MAA17008@apollo.backplane.com> References: <199912202024.MAA17008@apollo.backplane.com> <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <19991218225758.A23729@futuresouth.com> <199912190556.AAA08484@whizzo.transsys.com> <199912191943.LAA06826@apollo.backplane.com> <385D47D3.FCEE9EAB@softweyr.com> <199912192127.NAA09156@apollo.backplane.com> <385DDE7A.1A0ED466@softweyr.com> <199912201949.LAA16719@apollo.backplane.com> Date: Mon, 20 Dec 1999 13:34:50 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912202024.MAA17008@apollo.backplane.com> Matthew Dillon writes: : : or higher, which makes things a whole lot easier. No 60Hz humm, no : : vibration - hell, you can even run the frequency up past 100 MHz and : ^^^^ : Needless to say I meant 100 KHz here, not 100 MHz. Yes. The nice thing about modern swithcing power supplies are that if you DO hear any vibration, you know you have big problems and are courting disaster. At least that's my experience in homebrewing a 12V -> 16V converter for my Sony VAIO 505TS. The original magnetics I chose easily overloaded, producing a noticable hum. I didn't think much of this at the time, but about 3 hours into my test the coil started smoking a little, and then the cascade failure from that caused an overload on the regulator ic I was using and after the pop no more hum, but no more +16V either :-( And I was only running at 20 kHz.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 12:40:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id D852215540 for ; Mon, 20 Dec 1999 12:40:46 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40329>; Tue, 21 Dec 1999 07:31:55 +1100 Content-return: prohibited Date: Tue, 21 Dec 1999 07:40:37 +1100 From: Peter Jeremy Subject: Re: Parallel-port ethernet interfaces To: hackers@FreeBSD.ORG Message-Id: <99Dec21.073155est.40329@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-20 02:32:06 -0700, Wes Peters wrote: >> In message Brian Beattie writes: >> : Anybody know of any currently available, that are supported by FreeBSD? >> >> No. > >Yes. Another FreeBSD machine, with an ethernet interface and a parallel port >for running PLIP over. They are kind of large, though. ;^) This approach is also unreliable (as in 'you will hang one of the machines when you use it'). PLIP is broken (see i386/5698 and kern/6099). The change to ppbus has (if anything) made it worse (see kern/13382). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 12:51: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E4F2915332 for ; Mon, 20 Dec 1999 12:50:58 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA17151; Mon, 20 Dec 1999 12:50:54 -0800 (PST) (envelope-from dillon) Date: Mon, 20 Dec 1999 12:50:54 -0800 (PST) From: Matthew Dillon Message-Id: <199912202050.MAA17151@apollo.backplane.com> To: Warner Losh Cc: Wes Peters , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912202024.MAA17008@apollo.backplane.com> <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <19991218225758.A23729@futuresouth.com> <199912190556.AAA08484@whizzo.transsys.com> <199912191943.LAA06826@apollo.backplane.com> <385D47D3.FCEE9EAB@softweyr.com> <199912192127.NAA09156@apollo.backplane.com> <385DDE7A.1A0ED466@softweyr.com> <199912201949.LAA16719@apollo.backplane.com> <199912202034.NAA18342@harmony.village.org> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Yes. The nice thing about modern swithcing power supplies are that if :you DO hear any vibration, you know you have big problems and are :courting disaster. At least that's my experience in homebrewing a 12V :-> 16V converter for my Sony VAIO 505TS. The original magnetics I :chose easily overloaded, producing a noticable hum. I didn't think :much of this at the time, but about 3 hours into my test the coil :started smoking a little, and then the cascade failure from that :caused an overload on the regulator ic I was using and after the pop :no more hum, but no more +16V either :-( And I was only running at :20 kHz.... : :Warner Also, step-up switching supplies are a lot more finicky then step-down supplies. We usually use a flyback configuration for step-up but the input voltage range tends to be more constrained and the efficiency is lower so I try to avoid step-up whenever possible. I used a step-up (flyback) in one of my telemetry boards - incredible sucker, it took 12V in and produced 24V at 3A. I made one mistake in the design and that was to use too low a wattage on the 0.05 ohm current limit resistors (the last thing you'd expect to overheat). My personal preference is to use an *unregulated* DC wall plug (which is essentially just an AC transformer, rectifier, and big caps) that produces somewhere on the order of 15-25V and then put a step-down switching supply on the motherboard. This way we don't really care what the DC power going into the device is, or how noisy it is, just as long as it's at least 1.5V more then our regulator output. It lets us use virtually any wall plug, or a solar panel, battery, or DC power without making a single change to the design. The standard national switching supply chips can handle DC inputs up to, what, 40V? I think they have an industrial (read: for a car) version that can handle even more. They are efficient enough that even worse case inputs have low enough heat dissipation. I usually use the 1A parts though one recent design uses their 5A part. If we needed more power we used to use TO-220 packaged PFETs for the switching circuit. Now days we use SMT duel-PFETs which are actually rated for higher current in plastic then the old PFETs were in ceramic. But for low-current (< 3A) applications the national parts can handle the switching natively, which I really really like. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 13:29:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from donhm.calcasieu.com (dread.austin.texas.net [206.127.24.91]) by hub.freebsd.org (Postfix) with ESMTP id 66E4214E59 for ; Mon, 20 Dec 1999 13:29:43 -0800 (PST) (envelope-from dread@donhm.calcasieu.com) Received: (from dread@localhost) by donhm.calcasieu.com (8.9.3/8.9.3) id PAA21724; Mon, 20 Dec 1999 15:29:20 -0600 (CST) (envelope-from dread) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 20 Dec 1999 15:29:19 -0600 (CST) From: Don Read To: David Miller Subject: RE: Alternate ftpd? Cc: freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 19-Dec-99 David Miller wrote: > Hello all:) > > I'm looking for an alternate ftpd which allows me to take certain > (configurable) actions based on the receipt of certain files. For exmple, > I want to "process" a tar file full of jpg images upon receipt. > > I know there are alternatives. I can run swatch on the log file or > torture syslog to piping its output into something, but I think these are > all ugly kludges. speaking of kludgies, I run a cron job ash.root# cat check_ftp #!/bin/sh cd /root LIST=`find /usr/ftp/incoming -newer .time.ftp -print` if [ -n "$LIST" ] then echo $LIST | mail -s "new ftp files" root fi touch .time.ftp Regards, -- Don Read dread@calcasieu.com EDP Manager dread@texas.net Calcasieu Lumber Co. Austin TX -- No Coffee No Peace To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 13:36:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasknow.com (h139-142-245-96.ss.fiberone.net [139.142.245.96]) by hub.freebsd.org (Postfix) with ESMTP id C2F661531F for ; Mon, 20 Dec 1999 13:36:15 -0800 (PST) (envelope-from freebsd@sasknow.com) Received: from localhost (freebsd@localhost) by sasknow.com (8.9.3/8.9.3) with ESMTP id PAA30408 for ; Mon, 20 Dec 1999 15:36:54 -0600 (CST) (envelope-from freebsd@sasknow.com) Date: Mon, 20 Dec 1999 15:36:54 -0600 (CST) From: Ryan Thompson To: freebsd-hackers@freebsd.org Subject: Default minfree performance restrictions? 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 all, After creating some larger slices than I'm used to, I finally felt the full force of a default 8% minfree setting. So, I went to tunefs(8) to try and put a damper on the multiple gigabytes that aren't being made available to users. However, I was a bit disappointed to note that setting minfree at or below 5% (using integer values!) would result in SPACE optimization. So, on my 3.4-STABLE system, I did some hunting around. In /usr/src/sys/ufs/ffs/fs.h, I see MINFREE defaults to 8%, and default time optimization, like tunefs says. Nothing fancy, there. In ./ffs_alloc.c, however, I found out how the SPACE/TIME optimization is determined. In particular, in ffs_realloccg(), I find (from yesterday's -STABLE), the following snippet: /* * Allocate a new disk location. */ if (bpref >= fs->fs_size) bpref = 0; switch ((int)fs->fs_optim) { case FS_OPTSPACE: /* * Allocate an exact sized fragment. Although this makes * best use of space, we will waste time relocating it if * the file continues to grow. If the fragmentation is * less than half of the minimum free reserve, we choose * to begin optimizing for time. */ request = nsize; if (fs->fs_minfree <= 5 || /* !!! */ fs->fs_cstotal.cs_nffree > fs->fs_dsize * fs->fs_minfree / (2 * 100)) break; log(LOG_NOTICE, "%s: optimization changed from SPACE to TIME\n", fs->fs_fsmnt); fs->fs_optim = FS_OPTTIME; break; Questions: - Can the line I've marked /* !!! */ have the minimum value of 5 safely reduced? Eliminated? (safely = if/when a filesystem fills up, could writes potentially corrupt the fs?) On small partitions with many inodes, perhaps 5% is appropriate, but in cases like mine, where I have filesystems in excess of 20GB with < 0.1% fragmentation, > 5% minfree is frankly too much to give away. - Would it make sense to externalize this option into a header file, kernel config option, or perhaps tunefs itself? I'm guessing the latter would require modifications to our UFS implementation to allow for the extra parameter for each filesystem... And would definitely qualify as an "invasive" change. Food for thought, though :-) Any insights? I suppose I could just go ahead and try it, but, before I end up doing a reinstall (cd /usr/src && make blowupworld), I thought it better to ask a more experienced following of users :-) -- Ryan Thompson 50% Owner, Technical and Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 16:46:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 2743C14C24 for ; Mon, 20 Dec 1999 16:46:50 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 39779 invoked by uid 1001); 21 Dec 1999 00:45:17 -0000 Date: Mon, 20 Dec 1999 16:45:17 -0800 From: Jason Evans To: Chris Sedore Cc: Alfred Perlstein , Kevin Day , "Ronald F. Guilmette" , hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? Message-ID: <19991220164517.F26743@sturm.canonware.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cmsedore@maxwell.syr.edu on Sun, Dec 19, 1999 at 03:01:41PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 19, 1999 at 03:01:41PM -0500, Chris Sedore wrote: > > > On Sat, 18 Dec 1999, Alfred Perlstein wrote: > > > On Sat, 18 Dec 1999, Kevin Day wrote: > > > > > > The _clean_ way of doing it would be to write your multi-user server using > > > > threads, and to assign one thread to each connection. If you can do that, > > > > then the logic in the program becomes quite simple. Each thread just sits > > > > there, blocked on a call to read(), until something comes in, and then it > > > > just parses the command, does whatever it is supposed to do in response to > > > > that command, and then goes back to the read() again. > > > > > > > > But as I understand it, there is not yet sufficient threads support in the > > > > FreeBSD kernel to make this work well/properly. (I may perhaps be misinformed > > > > about that, but that's what I have been told anyway.) > > > > > > I believe this is how ConferenceRoom works, so it seems ok, but I remember > > > the comments that FreeBSD was their least preferred platform because of > > > thread problems. > > > > Using a thread per connection has always been a bogus way of programming, > > it's easy, but it doesn't work very well. > > Ahem. Well, that kind of depends on the threads implementation, how many > connections you're talking about, and likely some other factors too. > I've got an NT box that handles about 1000 concurrent connections with > 1000 (plus a few) threads doing the work. Runs fine, performs very well. > > I wouldn't argue that it is the most scalable solution to problems, but it > is easier, and scales proportionally to the quality of the threads > implementation. 1000 simultaneous connections really isn't that many, but even at 1000 threads, you could likely achieve much better performance by using thread pools or a simple poll() loop rather than one thread per connection. Why? Locality, locality, locality. Consider that each thread has its own stack, which in the best of worlds would be 4K, but is more likely at least 16K. Now, start switching between threads to handle relatively small amounts of I/O for each connection, and consider what that does to the VM, not to mention the memory hierarchy of the hardware. You might as well not even have L2 cache, because the program will thrash the cache so badly. Of course, you won't see worst case performance if client activity is unevenly distributed, but you just can't get past the fact that the memory footprint of one thread per connection is larger than a bounded pool of threads. Some threads implementations are better than others at handling such abuses, but the performance of such an approach will almost always suffer in comparison to a design that takes locality into consideration. I disagree with your assessment that scalability of one thread per connection is proportional to the quality of the threads implementation. An ideal threaded program would have exactly as many threads as available processors, and the threads would always be runnable. Of course, real-world applications almost never work that way, but the goal of a programmer should be to have as few threads as possible while still achieving maximal parallelism. If connection scalability is an issue, using one thread per connection ignores a critical aspect of high performance threaded application design. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 17:26:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from maxwell.syr.edu (maxwell.syr.edu [128.230.129.5]) by hub.freebsd.org (Postfix) with ESMTP id 02A4A153E0 for ; Mon, 20 Dec 1999 17:26:08 -0800 (PST) (envelope-from cmsedore@maxwell.syr.edu) Received: from qwerty.maxwell.syr.edu (qwerty.maxwell.syr.edu [128.230.129.248]) by maxwell.syr.edu (8.9.1a/8.9.1) with ESMTP id UAA14603; Mon, 20 Dec 1999 20:22:00 -0500 (EST) Date: Mon, 20 Dec 1999 20:24:28 -0500 (EST) From: Chris Sedore To: Jason Evans Cc: Alfred Perlstein , Kevin Day , "Ronald F. Guilmette" , hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? In-Reply-To: <19991220164517.F26743@sturm.canonware.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Dec 1999, Jason Evans wrote: > On Sun, Dec 19, 1999 at 03:01:41PM -0500, Chris Sedore wrote: > > > > > > On Sat, 18 Dec 1999, Alfred Perlstein wrote: > > [...TRIM...] > > > Using a thread per connection has always been a bogus way of programming, > > > it's easy, but it doesn't work very well. > > > > Ahem. Well, that kind of depends on the threads implementation, how many > > connections you're talking about, and likely some other factors too. > > I've got an NT box that handles about 1000 concurrent connections with > > 1000 (plus a few) threads doing the work. Runs fine, performs very well. > > > > I wouldn't argue that it is the most scalable solution to problems, but it > > is easier, and scales proportionally to the quality of the threads > > implementation. > > 1000 simultaneous connections really isn't that many, but even at 1000 > threads, you could likely achieve much better performance by using thread > pools or a simple poll() loop rather than one thread per connection. Why? > Locality, locality, locality. Consider that each thread has its own stack, > which in the best of worlds would be 4K, but is more likely at least 16K. > Now, start switching between threads to handle relatively small amounts of > I/O for each connection, and consider what that does to the VM, not to > mention the memory hierarchy of the hardware. You might as well not even > have L2 cache, because the program will thrash the cache so badly. Of > course, you won't see worst case performance if client activity is unevenly > distributed, but you just can't get past the fact that the memory footprint > of one thread per connection is larger than a bounded pool of threads. In my case, load is reasonably distributed. Is poll() really that much better than select()? I thought that, excepting bit flag manipulations, it worked basically the same way on the kernel end. > Some threads implementations are better than others at handling such > abuses, but the performance of such an approach will almost always suffer > in comparison to a design that takes locality into consideration. True enough. In some cases, this may not be that much of an issue, though. Imagine a thread-per-connection that does much of its work in a limited call tree, with much of its work context within 8k (+/-) of the current stack pointer. It has to pull this into cache every time that thread is activated. In a thread pool implementation, it would likely have to move about the same 16k into the cache, only from a "context structure" which would be probably approximately as open to thrashing as the thread stack. Add to that the fact that thread-pool applications often utilize more synchronization primitives. > I disagree with your assessment that scalability of one thread per > connection is proportional to the quality of the threads implementation. > An ideal threaded program would have exactly as many threads as available > processors, and the threads would always be runnable. Of course, > real-world applications almost never work that way, but the goal of a > programmer should be to have as few threads as possible while still > achieving maximal parallelism. If connection scalability is an issue, > using one thread per connection ignores a critical aspect of high > performance threaded application design. I don't disagree with any of what you have written. I'd expect you to concede that it is true that the scalability is proportional. That is, LinuxThreads (that is, rfork()) is probably not anything like optimally scalable, but something like the last FreeBSD KSE model that I saw bouncing around on -arch would do alot better. I was really responding to the assertion that thread-per-connection is broken as a methodology. I've written programs both ways, mixed the two, etc. My point was that at least one OS has no problem coping with 1000 threads essentially blocked on sockets, so the base argument of "it doesn't scale well" is, without further elaboration, hollow. I would agree that there is a crossover point for performance, probably below 1000 threads. I was just injecting a little real-world experience with this in an application which is somewhere above "small" and somewhere below "really large". People are still doing things like this with process-per-connection, so threads sound much better as an alternative. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 17:45:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id A0986153E6 for ; Mon, 20 Dec 1999 17:45:14 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 40040 invoked by uid 1001); 21 Dec 1999 01:43:42 -0000 Date: Mon, 20 Dec 1999 17:43:41 -0800 From: Jason Evans To: Chris Sedore Cc: Jason Evans , hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? Message-ID: <19991220174341.A39990@sturm.canonware.com> References: <19991220164517.F26743@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cmsedore@maxwell.syr.edu on Mon, Dec 20, 1999 at 08:24:28PM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 08:24:28PM -0500, Chris Sedore wrote: > On Mon, 20 Dec 1999, Jason Evans wrote: > > I disagree with your assessment that scalability of one thread per > > connection is proportional to the quality of the threads implementation. > > An ideal threaded program would have exactly as many threads as available > > processors, and the threads would always be runnable. Of course, > > real-world applications almost never work that way, but the goal of a > > programmer should be to have as few threads as possible while still > > achieving maximal parallelism. If connection scalability is an issue, > > using one thread per connection ignores a critical aspect of high > > performance threaded application design. > > I don't disagree with any of what you have written. I'd expect you to > concede that it is true that the scalability is proportional. That is, > LinuxThreads (that is, rfork()) is probably not anything like optimally > scalable, but something like the last FreeBSD KSE model that I saw > bouncing around on -arch would do alot better. Yes, LinuxThreads has a number of scalability problems that make using even a relatively small number of threads perform quite poorly, especially if there are multiple multi-threaded applications running on the same machine. I have serious issues with the 1:1 approach that LinuxThreads uses, because it fails to perform reasonably for anything but a very constrained set of multi-threaded programming models. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 19:45:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 1426114F62 for ; Mon, 20 Dec 1999 19:45:05 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA242898; Mon, 20 Dec 1999 22:44:49 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <385C789C.DD290597@softweyr.com> References: <199912190410.UAA01049@apollo.backplane.com> <385C789C.DD290597@softweyr.com> Date: Mon, 20 Dec 1999 22:50:26 -0500 To: Wes Peters , Matthew Dillon From: Garance A Drosihn Subject: Re: Cool little 100BaseTX switch - they're coming down in price Cc: freebsd-hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:18 PM -0700 12/18/99, Wes Peters wrote: >Matthew Dillon wrote: > > Prices have fallen a lot in the last year. I'm happy to be able to > > get rid of my HUBs, I was constantly having to deal with packet loss > > when running saturation tests and never able to figure out what > > was causing it. > >Switches are a better solution, no doubt about it. They are well worth >the cost, even if you're just trying to pep up an old 10Base-T network. >Investing in 10Base-T switches at this time is a false economy; for only >a few dollars more per port you can get 10/100 switches like yours and >upgrade machines to Fast Ethernet as budget allows. Getting back to the topic of switches, I've recently bought three different "reasonably cheap" 10/100 switches for some testing. One thing I would have liked to have had was an option to "mirror" the traffic of one port on some other port. I've got one of those non-peppy 10base-T networks I have to connect to, and I'd like to be able to have one of "my machines" (on the 10/100 switch) be able to see all traffic on that 10base-T network. All three of the switches I bought do not have configuration options to do something like this (which is fine...), but I was wondering how much one has to fork out before you get extra options like a port-mirroring capability... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 20:23:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monk.via.net (monk.via.net [209.81.2.10]) by hub.freebsd.org (Postfix) with ESMTP id A65FA15237 for ; Mon, 20 Dec 1999 20:23:08 -0800 (PST) (envelope-from joe@via.net) Received: (from joe@localhost) by monk.via.net (8.9.3/8.9.3) id UAA76829 for hackers@freebsd.org; Mon, 20 Dec 1999 20:23:11 -0800 (PST) (envelope-from joe) From: Joe McGuckin Message-Id: <199912210423.UAA76829@monk.via.net> Date: Mon, 20 Dec 1999 20:23:11 -0800 (PST) To: hackers@freebsd.org Subject: motherboard serial port dropping chars ? X-Mailer: Ishmail 1.3.1-970608-bsdi MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an application where I need to receive data constantly on a serial port at 38,400. When we write the data to a database, we constantly see dropped chars on the incoming serial port. Is the stock PC serial hardware capable of sustained thruput at 38.4K? Is there an ioctl option or something to improve the buffering on the serial ports ? Any suggestions? Thanks, Joe -- Joe McGuckin ViaNet Communications 994 San Antonio Road Palo Alto, CA 94303 Phone: 650-969-2203 Cell: 650-207-0372 Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 20:47:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 0984F14C49 for ; Mon, 20 Dec 1999 20:47:54 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id WAA21247; Mon, 20 Dec 1999 22:46:38 -0600 (CST) Date: Mon, 20 Dec 1999 22:46:37 -0600 From: Tim Tsai To: Garance A Drosihn Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price Message-ID: <19991220224637.A20946@futuresouth.com> References: <199912190410.UAA01049@apollo.backplane.com> <385C789C.DD290597@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > something like this (which is fine...), but I was wondering how > much one has to fork out before you get extra options like a > port-mirroring capability... You usually find this capability on managed switches (fairly obvious, since you need a management interface to configure port mirroring). This usually means SNMP capable too. So do your regular search on a managed switch or SNMP capable switch and chances are it will do what you want. Allied Telesyn probably has the lowest price managed switch I've seen but I think Netgear has one too. I am too lazy to dig up information at the moment - let me know if you have trouble finding them. Best bang for the buck category: HP ProCurve 4000M. 40 switched 10/100 ports (that's with the chassis half filled). $1499 (with a $400 HP rebate) from www.warehouse.com. Try not to buy up all the inventory because we're going to need one or two soon. :-) Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 21:20:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from w2xo.pgh.pa.us (ipl-229-010.npt-sdsl.stargate.net [208.223.229.10]) by hub.freebsd.org (Postfix) with ESMTP id DC9F415393 for ; Mon, 20 Dec 1999 21:20:27 -0800 (PST) (envelope-from durham@w2xo.pgh.pa.us) Received: from w2xo.pgh.pa.us (shazam.internal [192.168.5.3]) by w2xo.pgh.pa.us (8.9.3/8.9.3) with ESMTP id FAA33285; Tue, 21 Dec 1999 05:18:21 GMT Message-ID: <385F0D9C.A1337448@w2xo.pgh.pa.us> Date: Tue, 21 Dec 1999 00:18:20 -0500 From: Jim Durham Organization: dis- X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Bjorn Danielsson , Ben Smithurst , der , Don Read , Mike Nowlin , Ruslan Ermilov Cc: freebsd hackers Subject: Re: Resolv.conf question References: <199912170143.RAA03627@mass.cdrom.com> <3859C580.A4B9FAD8@w2xo.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bjorn Danielsson wrote: > > Jim Durham wrote: > > The 3.3 Box is a local server on a disconnected LAN talking > > to a "remote" server that spools mail, which is grabbed by > > fetchmail. We are running PPP on-demand to the external > > server via a dial-up to an ISP. However, PPP only holds the > > line up from 8am-8pm and this is happening at 1:59am, coinciding > > with the "periodic daily" scripts from crontab. > > Try changing "netstat -i" to "netstat -ni" in the script > /etc/periodic/daily/420.status-network > > Maybe the reverse dns lookup done by netstat -i tries to activate > ppp which then wipes /etc/resolv.conf. Just a crazy idea... > > -- You are so correct. I actually found it by executing all the scripts in /etc/periodic/daily "by hand" until it changed the file. It was the network status script, as you surmised. Alex Derevyanko , also came to the same conclusion, so you two have to share the prize. Here's Alex's info: > I have the same problem few weeks ago - it's 'netstat -r' problem - it tryes to > resolve hostnames. Sometimes the cache on my caching nameserver was up-to-date, > and ppp doesn't ring, sometimes no. Change it to 'netstat -rn' > Thanks to all who replied. -- Jim Durham To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 21:41:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 9F3E714BD0 for ; Mon, 20 Dec 1999 21:41:50 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id AAA06112; Tue, 21 Dec 1999 00:41:49 -0500 (EST) Date: Tue, 21 Dec 1999 00:41:49 -0500 (EST) From: Bosko Milekic To: Alex Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: splimp for PCI In-Reply-To: <199912201706.JAA31593@www.geocrawler.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Dec 1999, Alex wrote: !>This message was sent from Geocrawler.com by "Alex" !>Be sure to reply to that address. !> !>Hello, !>I'm little confuse to using splimp/splx in driver !>that support PCI board. IRQ is shared for PCI. !>Is using splimp can cause for some problem? !>Thank a lot !>Alex !> !>Geocrawler.com - The Knowledge Archive Here's my `first glance' shot at an answer: [ ;-) ] Nope, using splimp() will not cause problems in terms of shared IRQs. However, it may cause problems if you're blocking interrupt handlers of priorities that you don't want to. Shared IRQs are dealt with thanks to a linked list of handlers for each shared IRQ, which all end up being called as a result of at least one of the devices "registered" for that IRQ asserts an int request. Each device, however, is "registered" with its own 'mask,' and this mask should correspond to one of several given values, where _handlers_ executing at that priority level will be blocked as per the present priority level. If you haven't done so already, my suggestion is to take a look at spl(9) [e.g. `man 9 spl'], and, if still interested, taking a look at *some* of i386/isa/intr_machdep.c as well as most of sys/i386/i386/nexus.c -- which brings up the question: Is anybody _currently_ working on cleaning this stuff up, and completely getting rid of the remains of the "old" interface? Bosko. ...... . . . . . . . . . . . . . Bosko Milekic -- bmilekic@dsuper.net . . . . . . . . . . . ...... . . WWW: http://pages.infinit.net/bmilekic/ . ................................................ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Dec 20 23:18: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 0621B14BE3 for ; Mon, 20 Dec 1999 23:18:00 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id IAA18328 for freebsd-hackers@FreeBSD.ORG; Tue, 21 Dec 1999 08:17:58 +0100 (CET) (envelope-from olli) Date: Tue, 21 Dec 1999 08:17:58 +0100 (CET) From: Oliver Fromme Message-Id: <199912210717.IAA18328@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price Organization: Administration TU Clausthal Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On the topic of switches... Does anyone have experience (good or bad) with the CNet CNSH-1601 or CNSH-2401? Those are unmanaged 19" switches (10/100) with 16 and 24 ports, respectively, and a 100BaseFX (fibre) uplink port. And they're suspiciously cheap over here [1]. We might get one of those to upgrade part of our students dorm network from 10 to 100 Mbit/s. A 100BaseFX port is required for our uplink. The price is very tempting, but if the beast hangs every other day, this is no good, obviously... Regards Oliver [1] About 500 and 900 $US, respectively. -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem StЭck Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 0:19:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id 1410D14D9D for ; Tue, 21 Dec 1999 00:19:49 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id AAA00834; Tue, 21 Dec 1999 00:18:36 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id AAA00719; Tue, 21 Dec 1999 00:18:35 -0800 Received: from softweyr.com ([204.68.178.39]) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA17989; Mon, 20 Dec 99 23:43:15 PST Message-Id: <385F2FFD.CA594829@softweyr.com> Date: Tue, 21 Dec 1999 00:45:01 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: Garance A Drosihn Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C789C.DD290597@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 Garance A Drosihn wrote: > > At 11:18 PM -0700 12/18/99, Wes Peters wrote: > >Matthew Dillon wrote: > > > Prices have fallen a lot in the last year. I'm happy to be able to > > > get rid of my HUBs, I was constantly having to deal with packet loss > > > when running saturation tests and never able to figure out what > > > was causing it. > > > >Switches are a better solution, no doubt about it. They are well worth > >the cost, even if you're just trying to pep up an old 10Base-T network. > >Investing in 10Base-T switches at this time is a false economy; for only > >a few dollars more per port you can get 10/100 switches like yours and > >upgrade machines to Fast Ethernet as budget allows. > > Getting back to the topic of switches, I've recently bought three > different "reasonably cheap" 10/100 switches for some testing. > One thing I would have liked to have had was an option to "mirror" > the traffic of one port on some other port. > [...] but I was wondering how > much one has to fork out before you get extra options like a > port-mirroring capability... Lots more, in terms of dollars. For this, you need at least a managed switch, and probably a smart switch. I know for a fact this one, a 24-port 10Base-T switch with 2 10/100 uplink ports, supports port mirroring and hundreds of other features -- about $1100: http://shopper.cnet.com/shopping/resellers/1,10231,0-11726-311-1459828-3,00.html?tag=st.sh.11726-311-1459828.sort.price For 24 100Base-TX ports, you step up to about $2100: http://shopper.cnet.com/shopping/resellers/1,10231,0-11726-311-794908-3,00.html?tag=st.sh.11726-311-794908.sort.price For more info about both, see: http://www.ind.alcatel.com/enterprise/products/omnistack/ost04.html Note that these are "Layer 3" switches with VLAN support, IP and IPX routing, etc. The per-port prices aren't that different than the simpler managed switches, but the port count tends to be high. Caveat: I work on these things daily. Consider whatever I say about them to be evangelism. Also note that turning on software-dependent features like port mirroring can do terrible things to your throughput if not used judiciously. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 1:25:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 1DBF314EF4 for ; Tue, 21 Dec 1999 01:25:29 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA84886; Tue, 21 Dec 1999 09:34:44 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 21 Dec 1999 09:34:44 +0000 (GMT) From: Doug Rabson To: Tim Tsai Cc: Sergey Babkin , Matthew Dillon , freebsd-hackers@freebsd.org Subject: Re: Cool little 100BaseTX switch - they're coming down in price In-Reply-To: <19991218225758.A23729@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Dec 1999, Tim Tsai wrote: > > hub. It works fine except that it hangs occasionally (can be > > reset by power-cycling). > > Most of these can be attributed to the crappy wall wart they call a > power supply. If it's plugged into an UPS or replace it with your own DC > power supply they generally hold up a lot better. > > I have a Netgear FS108 at home (8 port 10/100 switch) and I've found > Netgear stuff to be as cheap as I would go and still be reasonably > reliable. That rings a bell. I had a D-Link 4 port hub and I went through about 4 power supplies before I gave up, binned it and bought a Netgear. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 3:58:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from maxwell.syr.edu (maxwell.syr.edu [128.230.129.5]) by hub.freebsd.org (Postfix) with ESMTP id 53FD014DD5 for ; Tue, 21 Dec 1999 03:58:15 -0800 (PST) (envelope-from cmsedore@maxwell.syr.edu) Received: from qwerty.maxwell.syr.edu (qwerty.maxwell.syr.edu [128.230.129.248]) by maxwell.syr.edu (8.9.1a/8.9.1) with ESMTP id GAA19050; Tue, 21 Dec 1999 06:55:37 -0500 (EST) Date: Tue, 21 Dec 1999 06:58:08 -0500 (EST) From: Chris Sedore To: Wes Peters Cc: Garance A Drosihn , Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price In-Reply-To: <385F2FFD.CA594829@softweyr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Dec 1999, Wes Peters wrote: > Garance A Drosihn wrote: > > > > At 11:18 PM -0700 12/18/99, Wes Peters wrote: > > >Matthew Dillon wrote: > > > > Prices have fallen a lot in the last year. I'm happy to be able to > > > > get rid of my HUBs, I was constantly having to deal with packet loss > > > > when running saturation tests and never able to figure out what > > > > was causing it. > > > > > >Switches are a better solution, no doubt about it. They are well worth > > >the cost, even if you're just trying to pep up an old 10Base-T network. > > >Investing in 10Base-T switches at this time is a false economy; for only > > >a few dollars more per port you can get 10/100 switches like yours and > > >upgrade machines to Fast Ethernet as budget allows. > > > > Getting back to the topic of switches, I've recently bought three > > different "reasonably cheap" 10/100 switches for some testing. > > One thing I would have liked to have had was an option to "mirror" > > the traffic of one port on some other port. > > [...] but I was wondering how > > much one has to fork out before you get extra options like a > > port-mirroring capability... > > Lots more, in terms of dollars. For this, you need at least a managed > switch, and probably a smart switch. I know for a fact this one, a > 24-port 10Base-T switch with 2 10/100 uplink ports, supports port mirroring > and hundreds of other features -- about $1100: > > http://shopper.cnet.com/shopping/resellers/1,10231,0-11726-311-1459828-3,00.html?tag=st.sh.11726-311-1459828.sort.price > You can get more from the HP Procurve 4000s for a little more money. You can buy them for $1500 (after a $400 rebate). 40 100BaseTX ports, with 5 open slots for more 8 port carts (we have some with 80 ports) or for gigabit cards (have two like this). We've got about 18 of these installed--they work great, and we haven't had autosense problems like we have with some other switches. Does port mirroring, trunking, IP multicast, VLANs, etc. http://www.cdw.com/shop/products/default.asp?EDC=126119 No connection with HP, except for being happy with this switch. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 6:18:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.clara.net (oracle.clara.net [195.8.69.94]) by hub.freebsd.org (Postfix) with ESMTP id 1B565154AD for ; Tue, 21 Dec 1999 06:18:06 -0800 (PST) (envelope-from ngould@zoo.co.uk) Received: from [195.8.67.157] (helo=zoo.co.uk ident=ngould) by oracle.clara.net with esmtp (Exim 2.12 #2) id 120Q71-000HGx-00 for freebsd-hackers@FreeBSD.org; Tue, 21 Dec 1999 14:18:04 +0000 Message-ID: <385F8AE3.A1E9EC88@zoo.co.uk> Date: Tue, 21 Dec 1999 14:12:51 +0000 From: Nathan Gould X-Mailer: Mozilla 4.61 [en] (X11; U; OpenBSD 2.6 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: I'd like to help! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'd like to contribute, if I may. Is there anything that high on the wishlist that I may help with? A bit of background: I've been with FreeBSD since 2.1. previously NeXTSTEP, SCO (don't laugh), HP-UX and SUNOS/Solaris. One thing I though about is the lack of an LVM equivalent - most commerical system offer this- any thoughts? Regards, Nathan Gould ngould@zoo.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 7:22:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 3D7CB14F8E for ; Tue, 21 Dec 1999 07:22:08 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id JAA22484; Tue, 21 Dec 1999 09:22:06 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id JAA28477; Tue, 21 Dec 1999 09:22:05 -0600 (CST) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id JAA04702; Tue, 21 Dec 1999 09:22:04 -0600 (CST) Date: Tue, 21 Dec 1999 09:22:04 -0600 (CST) From: Jonathan Lemon Message-Id: <199912211522.JAA04702@free.pcs> To: cmsedore@maxwell.syr.edu, hackers@freebsd.org Subject: Re: Practical limit for number of TCP connections? X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >In my case, load is reasonably distributed. Is poll() really that much >better than select()? I thought that, excepting bit flag manipulations, >it worked basically the same way on the kernel end. Yes, it is better. Select uses the same backend as poll(), but those "bit flag manipulations" that you are talking about consume a measurable amount of CPU time when you start throwing thousands of descriptors at it. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 7:29:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from manor.msen.com (manor.msen.com [148.59.4.13]) by hub.freebsd.org (Postfix) with ESMTP id 504DE14F23 for ; Tue, 21 Dec 1999 07:29:13 -0800 (PST) (envelope-from wayne@staff.msen.com) Received: (from wayne@localhost) by manor.msen.com (8.8.8/8.8.8) id KAA26966 for freebsd-hackers@FreeBSD.ORG; Tue, 21 Dec 1999 10:29:11 -0500 (EST) (envelope-from wayne) Message-ID: <19991221102911.A26853@staff.msen.com> Date: Tue, 21 Dec 1999 10:29:11 -0500 From: "Michael R. Wayne" To: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C789C.DD290597@softweyr.com> <19991220224637.A20946@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <19991220224637.A20946@futuresouth.com>; from Tim Tsai on Mon, Dec 20, 1999 at 10:46:37PM -0600 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 10:46:37PM -0600, Tim Tsai wrote: > > Best bang for the buck category: HP ProCurve 4000M. 40 switched 10/100 > ports (that's with the chassis half filled). Note that HP's pricing on additional cards is silly. It's cheaper to buy 2 4000Ms and throw the second chassis away than to buy 5 more cards. Other than that, great product. 2424M (not 2424) has simialr feature set in a 24 port version. /\/\ \/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 8:17:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id AA43A14FBE for ; Tue, 21 Dec 1999 08:13:18 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id QAA97697 for hackers@freebsd.org; Tue, 21 Dec 1999 16:11:32 GMT (envelope-from nik) Date: Tue, 21 Dec 1999 16:11:31 +0000 From: Nik Clayton To: hackers@freebsd.org Subject: wchar support? Message-ID: <19991221161131.A72885@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I'm trying to compile OpenJade 1.3, a C++ application, for the Doc. Proj. The build fails with LangObj.cxx:15: wchar.h: No such file or directory LangObj.cxx:16: wctype.h: No such file or directory gmake[2]: *** [LangObj.lo] Error 1 which is obvious enough. A hunt through /usr/include, /usr/local/include, and /usr/X11R6/include doesn't turn up anything approximating these headers as far as I can tell (this is on a -stable system, but I've got a -current source tree extracted as well, and I can't find it in there either). A hunt through the mailing list archives turned up various messages about wchar support, in particular a thread last year, pointing at the xview3.2 libraries. I've just extracted the x11-toolkit/xview port (which unextracts to xview3.2p1-X11R6, so I assume I've got the right one), but the only mention of wchar.h in there is a comment in clients/olwm/charset.h /* Following macros are defined in via in ALE so I figure the information in that thread was either wrong, or is now out of date. Any suggestions appreciated, thanks. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 8:18:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 0033A151FC for ; Tue, 21 Dec 1999 08:18:42 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 3.03 #3) id 120Rzl-0000o9-00; Tue, 21 Dec 1999 09:18:42 -0700 Message-ID: <385FA8CD.4676A83E@softweyr.com> Date: Tue, 21 Dec 1999 09:20:29 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Nathan Gould Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: I'd like to help! References: <385F8AE3.A1E9EC88@zoo.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nathan Gould wrote: > > Hi, > > I'd like to contribute, if I may. Is there anything that high on the > wishlist that I may help with? > > A bit of background: I've been with FreeBSD since 2.1. previously > NeXTSTEP, SCO (don't laugh), HP-UX and SUNOS/Solaris. > > One thing I though about is the lack of an LVM equivalent - most > commerical system offer this- any thoughts? man vinum(4). If you want to contribute in some way, contact grog@lemis.com for guidance. A filesystem expander would be nice, for adding space to an existing filesystem. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 8:29:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id ED85C1544F for ; Tue, 21 Dec 1999 08:29:32 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id IAA21355; Tue, 21 Dec 1999 08:29:31 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Dec 1999 08:29:30 -0800 (PST) From: Doug White To: "Michael R. Wayne" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price In-Reply-To: <19991221102911.A26853@staff.msen.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Dec 1999, Michael R. Wayne wrote: > On Mon, Dec 20, 1999 at 10:46:37PM -0600, Tim Tsai wrote: > > > > Best bang for the buck category: HP ProCurve 4000M. 40 switched 10/100 > > ports (that's with the chassis half filled). > > Note that HP's pricing on additional cards is silly. It's cheaper > to buy 2 4000Ms and throw the second chassis away than to buy 5 > more cards. Ever noticed it's this way with *anything* that has add-in blades? :) If you buy two chassis, you can take the parts and make one fully populated one -- with both power supplies even. And $3000 for 80 100mbit ports is pretty good port density if you ask me. And they take Gig Ethernet cards so you can set up a neat switching fabric for cheap. The 2GB backplane speed is the only limiting factor. Forestall the Cisco invasion a little longer. :) I remember TotalControl modem racks are sold the same way, generally. > Other than that, great product. 2424M (not 2424) has simialr > feature set in a 24 port version. The 8000M is a waste of money, btw. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 11:11:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 722F2151F2 for ; Tue, 21 Dec 1999 11:11:27 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA17006; Tue, 21 Dec 1999 11:13:21 -0800 Date: Tue, 21 Dec 1999 11:13:20 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-hackers@FreeBSD.ORG Subject: Preliminary Intel PRO/1000 Gigabit driver for FreeBSD-current In-Reply-To: <14351.18373.418811.886740@hip186.ch.intel.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've copied a first cut of an Intel Pro/1000 Gigabit driver for freebsd to: http://www.freebsd.org/~mjacob/FreeBSD_Intel_Gige.patch.gz This is a patch against -current's /usr/src/sys as of today. I have run it on a 2xPPro Intel 440FX and a Alpha PC164 (432Mhz). This is a very first cut, but seems fairly clean to me. It lacks many many things, but certainly is functional. I'd like to get some feedback about this soon before I drop it into the tree. Known Problems: Link management is 'primitive'. I don't have a switch, so I've only tested full duplex point2point. Right now, up'ing the interface will fail if link isn't seen. Known MetaProblems: Performance is abysmal (~130Mbit). That's next to figure out what's up and what I've done stupidly. Feel free to comment.. Some (most) of the stuff is based upon the released Linux driver because this driver was done w/o recourse to officially released Intel chip specs. In particular, accomodating early revision boards (the only two I have) is based on information out of the Linux driver which has no explicable collateral (so should be looked at more carefully). Also there appears to be some issue with some PCI chipsets that means that using the feature of reporting a packet sent when it gets into the chip's xmit fifo can't be used (have to wait for it to get onto the wire). Futures: Support for JumboGrams (requires thwacking the driver to handle more than one receive descriptor per packet). Statistics gathering. Vlan tagging (if I can get good documentation on this) Better multicast support (I'm only using the extra 15 addresses in the address match array before going to Multicast Promiscuous, and not using the MTA hash array). All feedback gratefully solicited- I'm not, primarily, a NetWork driver writer, so any pointers/comments would be appreciated. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 11:30:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 8172B14DA7; Tue, 21 Dec 1999 11:30:38 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.194]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA5F30; Tue, 21 Dec 1999 20:30:31 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id UAA51520; Tue, 21 Dec 1999 20:30:22 +0100 (CET) (envelope-from asmodai) Date: Tue, 21 Dec 1999 20:30:21 +0100 From: Jeroen Ruigrok/Asmodai To: Nik Clayton Cc: hackers@freebsd.org Subject: Re: wchar support? Message-ID: <19991221203021.D50448@daemon.ninth-circle.org> References: <19991221161131.A72885@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991221161131.A72885@catkin.nothing-going-on.org>; from nik@freebsd.org on Tue, Dec 21, 1999 at 04:11:31PM +0000 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991221 18:25], Nik Clayton (nik@freebsd.org) wrote: >I'm trying to compile OpenJade 1.3, a C++ application, for the Doc. Proj. >The build fails with Bah, you beat me to it ;) >LangObj.cxx:15: wchar.h: No such file or directory >LangObj.cxx:16: wctype.h: No such file or directory >gmake[2]: *** [LangObj.lo] Error 1 On CURRENT I have the above, but prefixed with a c, so: cwchar.h and cwctype.h under /usr/include/g++/ I do see wchar and wctype.h as part of SUSv2 though. I also see them as part of Linux libc. But that's all I can tell about it. HTH a bit Nik, -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project A rose is a rose is a rose is a rose... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 11:36:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 8CF6D1514C; Tue, 21 Dec 1999 11:36:20 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id LAA23523; Tue, 21 Dec 1999 11:36:05 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Tue, 21 Dec 1999 11:36:05 -0800 Date: Tue, 21 Dec 1999 11:36:05 -0800 (PST) From: Kip Macy To: Jeroen Ruigrok/Asmodai Cc: Nik Clayton , hackers@freebsd.org Subject: Re: wchar support? In-Reply-To: <19991221203021.D50448@daemon.ninth-circle.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: asmodai@wxs.nl,nik@freebsd.org,hackers@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Dec 1999, Jeroen Ruigrok/Asmodai wrote: > -On [19991221 18:25], Nik Clayton (nik@freebsd.org) wrote: > >I'm trying to compile OpenJade 1.3, a C++ application, for the Doc. Proj. > >The build fails with > > Bah, you beat me to it ;) > > >LangObj.cxx:15: wchar.h: No such file or directory > >LangObj.cxx:16: wctype.h: No such file or directory > >gmake[2]: *** [LangObj.lo] Error 1 > > On CURRENT I have the above, but prefixed with a c, so: > > cwchar.h and cwctype.h under /usr/include/g++/ > > I do see wchar and wctype.h as part of SUSv2 though. > > I also see them as part of Linux libc. > > But that's all I can tell about it. > > HTH a bit Nik, I am afraid it is not that simple. io [lyris/cb/source|11:34|111|]locate wchar.h /usr/include/g++/std/cwchar.h /usr/src/contrib/libg++/libstdc++/std/cwchar.h io [lyris/cb/source|11:35|112|]more /usr/include/g++/std/cwchar.h // The -*- C++ -*- wide character header. // This file is part of the GNU ANSI C++ Library. #ifndef __CWCHAR__ #define __CWCHAR__ #include #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 11:39:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 5072314E34 for ; Tue, 21 Dec 1999 11:39:26 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id NAA24015; Tue, 21 Dec 1999 13:39:23 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id NAA04296; Tue, 21 Dec 1999 13:39:21 -0600 (CST) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id NAA04949; Tue, 21 Dec 1999 13:39:21 -0600 (CST) Date: Tue, 21 Dec 1999 13:39:21 -0600 (CST) From: Jonathan Lemon Message-Id: <199912211939.NAA04949@free.pcs> To: mjacob@feral.com, hackers@freebsd.org Subject: Re: Preliminary Intel PRO/1000 Gigabit driver for FreeBSD-current X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: > >I've copied a first cut of an Intel Pro/1000 Gigabit driver for freebsd to: > >http://www.freebsd.org/~mjacob/FreeBSD_Intel_Gige.patch.gz Um, no offense, but why didn't you coordinate with me earlier about this? I did tell you that I was working on the Intel GigE driver, and that I _DO_ have the documentation, but never heard back from you. I currently get roughly 300Mb/sec with my driver, and that's with the untuned version. I'm still waiting on Intel to get back to me about releasing the driver, but I don't really anticipate any problems, since the version that they have released is also under the BSD license. Note that the chip I'm working with is the next revision of this card, so it's entirely probable that your driver will not work with the newer Intel cards. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 11:48:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D705714E1F for ; Tue, 21 Dec 1999 11:48:25 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA17198; Tue, 21 Dec 1999 11:50:20 -0800 Date: Tue, 21 Dec 1999 11:50:20 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Jonathan Lemon Cc: hackers@FreeBSD.ORG Subject: Re: Preliminary Intel PRO/1000 Gigabit driver for FreeBSD-current In-Reply-To: <199912211939.NAA04949@free.pcs> 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 did coordinate with you- you didn't offer to share any technical information with me and seemed to indicate that the driver would have trouble being released with source. You also said "I haven't written a NetWork driver either". See correspondence below. Hey- if your driver is cleaner and better and the way to go, maybe it should go in. I was paid by a company (that's why the copyright is Traakan, not me) to do an Intel GigE driver for their proprietary OS, and I said a FreeBSD/NetBSD version would be part of the deal. I've had some fun doing this and some grief, and I happen to like the spareness of what I've done, but I'm not *totally* wedded to it. It is in fact *because* I remember you mentioning that you were doing a driver that I didn't just check this into CVS (about 50%- the other 50% would be to get some review). -matt Date: Mon, 22 Nov 1999 09:03:08 -0600 From: Jonathan Lemon To: mjacob@feral.com Subject: Re: Intel PRO/1000 Gigabit driver Hello - If possible, please send me what you have. I just received the manuals and a sample card for the next generation silicon of this chip, but probably won't be able to start work on it until later this week. -- Jonathan Date: Mon, 22 Nov 1999 07:10:05 -0800 (PST) From: Matthew Jacob To: Jonathan Lemon Subject: Re: Intel PRO/1000 Gigabit driver How did you manage to get manuals? I had to reverse engineer the linux driver? And after having been up for about 72 hours to try and finish this for a customer, you can imagine I'm a bit dismayed by your mail. Like, who the heck are you? :-) On Mon, 22 Nov 1999, Jonathan Lemon wrote: > Hello - > > If possible, please send me what you have. I just received the > manuals and a sample card for the next generation silicon of this > chip, but probably won't be able to start work on it until later this > week. > -- > Jonathan > On Mon, Nov 22, 1999 at 07:10:05AM -0800, Matthew Jacob wrote: > How did you manage to get manuals? I had to reverse engineer the linux > driver? And after having been up for about 72 hours to try and finish this > for a customer, you can imagine I'm a bit dismayed by your mail. > > Like, who the heck are you? :-) Well, the startup that I was working for got gobbled by cisco, so I guess I'm now working for cisco. These chips were actually (as was explained to me) a cisco design, and are produced by intel. So I asked someone at cisco to obtain documentation on the card for me, and a package arrived on my desk last friday. Now, every page has an "Intel Restricted Secret" stamped on it, and I haven't signed an NDA, but this is probably covered by the employment agreement I signed last week. However, my understanding is that both cisco and intel would like to open-source any driver written for the card. Meaning, I'll write a driver, which should cover both the existing card and the next-generation card which is due to be released. As far as FreeBSD is concerned, I know I can release a binary driver immediatly, while I figure out what cisco's procdedure is for releasing sources as well. Intel's version is under a BSD license, so I don't anticipate this being a problem. Who do you work for, anyway? -- Jonathan Date: Mon, 22 Nov 1999 09:47:56 -0600 From: Jonathan Lemon To: Matthew Jacob Subject: Re: Intel PRO/1000 Gigabit driver On Mon, Nov 22, 1999 at 07:37:04AM -0800, Matthew Jacob wrote: > It's my understanding that the next rev chip is Intel only- not cisco. Perhaps it is, maybe they took the orignal silicon and redid it. But I'm pretty sure that cisco will be using the next rev in their products. > Myself. Let me ponder whether to show you my pathetic attempts at a > network driver. Well, be forewarned that I haven't written a network driver either; the only driver I've written is the compaq ida driver, and that was reverse-engineered from the Linux one. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 12: 7:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 7377F14E7B for ; Tue, 21 Dec 1999 12:07:40 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id OAA24155; Tue, 21 Dec 1999 14:07:39 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.8.5/8.6.4) id OAA14532; Tue, 21 Dec 1999 14:07:35 -0600 (CST) Message-ID: <19991221140733.10659@right.PCS> Date: Tue, 21 Dec 1999 14:07:33 -0600 From: Jonathan Lemon To: mjacob@feral.com Cc: hackers@FreeBSD.ORG Subject: Re: Preliminary Intel PRO/1000 Gigabit driver for FreeBSD-current References: <199912211939.NAA04949@free.pcs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: ; from Matthew Jacob on Dec 12, 1999 at 11:50:20AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 12, 1999 at 11:50:20AM -0800, Matthew Jacob wrote: > I did coordinate with you- you didn't offer to share any technical > information with me and seemed to indicate that the driver would have > trouble being released with source. You also said "I haven't written a > NetWork driver either". See correspondence below. Well, I congratulate you for posting private mail to a public list. Now, if you go back and look at it, I quite clearly said that the docs are covered under NDA, so of course I can't share any details with you, unless you're willing to sign an NDA as well. That's the way they work, after all. I also said that I did not anticipate any problems releasing the driver source, _BUT_ that I did have to get permission first. I'm currently waiting on that from Intel. Given that their own driver is under a BSD license, I don't think that they will have any objections. And no, I haven't written a network driver before, but what's your point? All I meant was that I can't produce results inside of one week, like Bill "maniac network driver writer" Paul; not that my code would be horrible. Not that I'm implying yours is, either! > It is in fact *because* I remember you mentioning that you were doing a > driver that I didn't just check this into CVS (about 50%- the other 50% > would be to get some review). So, how do you want to proceed? At this point, you have a driver that you can release, and I don't. We can either just check yours into CVS, and then replace it with mine later, or just completely forget about the one that I have. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 12:14:12 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from merc92.us.sas.com (merc92.us.sas.com [192.58.184.17]) by hub.freebsd.org (Postfix) with ESMTP id A2C0715502 for ; Tue, 21 Dec 1999 12:14:10 -0800 (PST) (envelope-from David.Quattlebaum@sas.com) Received: by merc92.us.sas.com with Internet Mail Service (5.5.2650.21) id ; Tue, 21 Dec 1999 15:14:07 -0500 Message-ID: <5FA575D78630D3118B2E0090276DC89F01B59270@merc08.us.sas.com> From: David Quattlebaum To: 'FreeBSD Hackers' Subject: modifying an object file Date: Tue, 21 Dec 1999 15:14:00 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone, I have an object file: foo.o In foo.o I have a call to bar(). Now, I want foo.o to actually call yo() instead of bar() and say I don't have the source for foo.c (so recompiling is out of the question). I want to change the object file foo.o to call yo() instead of bar(). Has anyone accomplished this without having to dissect the ELF object, change it and reconstruct the pieces? Thanks. -- David Quattlebaum, (david.quattlebaum@sas.com ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 12:17: 0 1999 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 8747F1501A for ; Tue, 21 Dec 1999 12:16:57 -0800 (PST) (envelope-from imp@harmony.village.org) 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 NAA17049; Tue, 21 Dec 1999 13:16:55 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA27010; Tue, 21 Dec 1999 13:16:54 -0700 (MST) Message-Id: <199912212016.NAA27010@harmony.village.org> To: David Quattlebaum Subject: Re: modifying an object file Cc: "'FreeBSD Hackers'" In-reply-to: Your message of "Tue, 21 Dec 1999 15:14:00 EST." <5FA575D78630D3118B2E0090276DC89F01B59270@merc08.us.sas.com> References: <5FA575D78630D3118B2E0090276DC89F01B59270@merc08.us.sas.com> Date: Tue, 21 Dec 1999 13:16:54 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <5FA575D78630D3118B2E0090276DC89F01B59270@merc08.us.sas.com> David Quattlebaum writes: : Has anyone accomplished this without having to dissect the ELF object, change it : and reconstruct the pieces? Change the string table. This is the time honored way of kludging binaries to do things that the original .o's were never intended to do. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 12:26: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from server.baldwin.cx (ric-54.freedomnet.com [198.240.105.54]) by hub.freebsd.org (Postfix) with ESMTP id 081CC154CE for ; Tue, 21 Dec 1999 12:25:56 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id PAA58860; Tue, 21 Dec 1999 15:26:06 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <199912212026.PAA58860@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <5FA575D78630D3118B2E0090276DC89F01B59270@merc08.us.sas.com> Date: Tue, 21 Dec 1999 15:26:04 -0500 (EST) From: John Baldwin To: David Quattlebaum Subject: RE: modifying an object file Cc: FreeBSD Hackers Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Dec-99 David Quattlebaum wrote: > Anyone, > > I have an object file: foo.o > > In foo.o I have a call to bar(). > > Now, I want foo.o to actually call yo() instead of bar() and say I don't have > the source > for foo.c (so recompiling is out of the question). I want to change the > object file > foo.o to call yo() instead of bar(). > > Has anyone accomplished this without having to dissect the ELF object, change > it > and reconstruct the pieces? void bar(void) { yo(); } perhaps? > Thanks. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 12:41:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from merc92.us.sas.com (merc92.us.sas.com [192.58.184.17]) by hub.freebsd.org (Postfix) with ESMTP id 0996F1500B; Tue, 21 Dec 1999 12:41:50 -0800 (PST) (envelope-from David.Quattlebaum@sas.com) Received: by merc92.us.sas.com with Internet Mail Service (5.5.2650.21) id ; Tue, 21 Dec 1999 15:41:48 -0500 Message-ID: <5FA575D78630D3118B2E0090276DC89F01B59271@merc08.us.sas.com> From: David Quattlebaum To: 'John Baldwin' Cc: 'FreeBSD Hackers' Subject: RE: modifying an object file Date: Tue, 21 Dec 1999 15:41:44 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: John Baldwin [mailto:jhb@FreeBSD.org] > Sent: Tuesday, December 21, 1999 3:26 PM > To: David Quattlebaum > Cc: FreeBSD Hackers > Subject: RE: modifying an object file > > > > On 21-Dec-99 David Quattlebaum wrote: > > Anyone, > > > > I have an object file: foo.o > > > > In foo.o I have a call to bar(). > > > > Now, I want foo.o to actually call yo() instead of bar() > and say I don't have > > the source > > for foo.c (so recompiling is out of the question). I want > to change the > > object file > > foo.o to call yo() instead of bar(). > > > > Has anyone accomplished this without having to dissect the > ELF object, change > > it > > and reconstruct the pieces? > > void bar(void) { > yo(); > } > > perhaps? No, not wanting to re-compile anything. > > > Thanks. > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 13:16: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 7C72D15140 for ; Tue, 21 Dec 1999 13:15:57 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40323>; Wed, 22 Dec 1999 08:07:02 +1100 Content-return: prohibited Date: Wed, 22 Dec 1999 08:15:48 +1100 From: Peter Jeremy Subject: Re: Practical limit for number of TCP connections? To: hackers@FreeBSD.ORG Message-Id: <99Dec22.080702est.40323@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Dec 1999 09:22:04 -0600 (CST), Jonathan Lemon wrote: >In article you write: >>In my case, load is reasonably distributed. Is poll() really that much >>better than select()? I thought that, excepting bit flag manipulations, >>it worked basically the same way on the kernel end. > >Yes, it is better. Select uses the same backend as poll(), but those >"bit flag manipulations" that you are talking about consume a measurable >amount of CPU time when you start throwing thousands of descriptors at it. I'm not as sure that it's that clear cut. poll(2) requires far more copyin/copyout than select(2) (8 bytes per fd instead of 1-3 bits/fd). And if it's the bit twiddling that you're worried about, the kernel has to check 10 bits in each pollfd entry, rather than the 1-3 bits for select(2). If you have a very sparse set of FD's to select on, then poll(2) should be better. I suspect the normal server case is closer to selecting on fds [3 .. nfds-1] - so select(2) is probably faster. poll(2) does have advantages over select(2): - Separate input-only and output-only fields mean you may not need to separately keep (or re-generate) the list of events of interest. - A wider range of states/events can be requested/reported. Has anyone done any timing comparisons between poll(2) and select(2)? Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 13:16:18 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id BBF0C15547 for ; Tue, 21 Dec 1999 13:16:13 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id QAA39067; Tue, 21 Dec 1999 16:25:04 -0500 (EST) Date: Tue, 21 Dec 1999 16:25:04 -0500 (EST) From: Ben Rosengart To: Chris Costello Cc: Matthew Dillon , freebsd-hackers@FreeBSD.ORG Subject: Re: Anybody know if there is any way to make ports use different work dir? In-Reply-To: <19991218194337.M523@holly.calldei.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 18 Dec 1999, Chris Costello wrote: > The authors of bsd.port.mk have. Try this: Oh, that's great! I've wanted for a long time to have a way of building ports without being root. Thank you. -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 14: 4:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from prism.flugsvamp.com (prism.flugsvamp.com [208.139.222.230]) by hub.freebsd.org (Postfix) with ESMTP id CC85E15544 for ; Tue, 21 Dec 1999 14:04:55 -0800 (PST) (envelope-from jlemon@prism.flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id QAA10190; Tue, 21 Dec 1999 16:05:54 -0600 (CST) (envelope-from jlemon) Date: Tue, 21 Dec 1999 16:05:54 -0600 From: Jonathan Lemon To: Matthew Dillon , hackers@freebsd.org Subject: Re: Odd TCP glitches in new currents Message-ID: <19991221160554.A10150@prism.flugsvamp.com> References: <199912212146.PAA05052@free.pcs> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912212146.PAA05052@free.pcs> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Dec 1999 12:50:50 -0800 (PST), Matthew Dillon wrote: > What happens when you specify a 1-tick timeout and the tick interrupt > occurs a microsecond later? For that matter what happens when you want > 1.5 ticks worth of timeout? Do you get only 1? What happens is that > the TCP stack thinks it timed out when it only just sent the packet a > few microseconds ago. This should be taken care of by the TCP_REXMTVAL macro, it adds in one additional tick, plus .5 ticks for rounding. It's possible that I've defined the TCPTV_MIN value to be wrong, you could try bumping this up while I go back and review my notes. -- Jonaghan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 14: 6:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1699C14F20 for ; Tue, 21 Dec 1999 14:06:45 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA17687 for ; Tue, 21 Dec 1999 14:08:41 -0800 Date: Tue, 21 Dec 1999 14:08:41 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-hackers@FreeBSD.ORG Subject: Re: Preliminary Intel PRO/1000 Gigabit driver for FreeBSD-current 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 > Performance is abysmal (~130Mbit). That's next to figure out > what's up and what I've done stupidly. Feel free to comment.. I should note, btw, that this is, in fact, better than I could get the Linux released Intel driver to do, so far all I know it's just the cards I have. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 14:19:11 1999 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 9632814F80; Tue, 21 Dec 1999 14:19:04 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id RAA22030; Tue, 21 Dec 1999 17:19:00 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id RAA30671; Tue, 21 Dec 1999 17:18:59 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id RAA04673; Tue, 21 Dec 1999 17:18:58 -0500 (EST) Date: Tue, 21 Dec 1999 17:18:58 -0500 (EST) From: Thomas David Rivers Message-Id: <199912212218.RAA04673@lakes.dignus.com> To: David.Quattlebaum@sas.com, jhb@FreeBSD.ORG Subject: RE: modifying an object file Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: <5FA575D78630D3118B2E0090276DC89F01B59271@merc08.us.sas.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David - The man page for the ELF linker says: ld accepts Linker Command Language files to provide ex- plicit and total control over the linking process. This man page does not describe the command language; see the `ld' entry in `info', or the manual ld: the GNU linker , for full details on the command language and on other as- pects of the GNU linker. I'd bet there's something there that will let you rename your reference. On a 3.3 box, you can find the texi files in /usr/src/contrib/binutils/ld Just a possible place to look... - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 14:36:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7352B15570 for ; Tue, 21 Dec 1999 14:36:36 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p02-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.131]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id HAA13974; Wed, 22 Dec 1999 07:36:24 +0900 (JST) Message-ID: <3860003A.548F8343@newsguy.com> Date: Wed, 22 Dec 1999 07:33:30 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Justin Hawkins Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Justin Hawkins wrote: > > I think (I am not positive on this) that if the boot loader talks to a > modem in command mode with echo on, it gets confused and won't boot any > further. Is this a known problem? I'd say this is an expected result, not a known problem. It is doing exactly what it is being told to (gibberish). Junk in, junk out. :-) > Is there enough room in there for some code, which checks for this? IE if > the first line output to the serial device == the first input (some > version string probably) then it just ignores it and does the default > action? Just configure it correctly. Don't tell it to talk to a serial device that will be sending it gibberish. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 14:58:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tardis.mx.com.au (tardis.mx.com.au [203.34.34.73]) by hub.freebsd.org (Postfix) with ESMTP id 4EA5814DFD for ; Tue, 21 Dec 1999 14:58:50 -0800 (PST) (envelope-from justin@tardis.mx.com.au) Received: from localhost (justin@localhost) by tardis.mx.com.au (8.9.3/8.9.3) with ESMTP id JAA00567; Wed, 22 Dec 1999 09:28:05 +1030 (CST) (envelope-from justin@tardis.mx.com.au) Date: Wed, 22 Dec 1999 09:28:04 +1030 (CST) From: Justin Hawkins To: "Daniel C. Sobral" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem In-Reply-To: <3860003A.548F8343@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Dec 1999, Daniel C. Sobral wrote: > I'd say this is an expected result, not a known problem. It is doing > exactly what it is being told to (gibberish). Junk in, junk out. :-) Sure. > > Is there enough room in there for some code, which checks for this? IE if > > the first line output to the serial device == the first input (some > > version string probably) then it just ignores it and does the default > > action? > > Just configure it correctly. Don't tell it to talk to a serial device > that will be sending it gibberish. Well that was what I was trying to do. Given the relatice complexity of setting up for a serial console on the second serial port (kernel recompile, boot loader(s) recompile, boot block install etc). There is a better than even chance it's going to take someone like me a couple of reboots to get it all working. When the (previously working) boot process inexplicably stops for no apparent reason (the reason being the boot loader has been confused by the modem) it's a little disconcerting. I understand it's not really a bug and perhaps is not worth the code effort. A note in the handbook might not go astray - I am sure a lot of people who need a COM2 console will have modem on COM1. Thanks for your time. - Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 15: 8:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 70B9E15577 for ; Tue, 21 Dec 1999 15:08:31 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id RAA25184; Tue, 21 Dec 1999 17:08:26 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.8.5/8.6.4) id RAA17496; Tue, 21 Dec 1999 17:08:24 -0600 (CST) Message-ID: <19991221170823.39068@right.PCS> Date: Tue, 21 Dec 1999 17:08:23 -0600 From: Jonathan Lemon To: Jason Nordwick Cc: cmsedore@maxwell.syr.edu, hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? References: <199912211522.JAA04702@free.pcs> <199912212355.PAA25570@erdos.hq.askjeeves.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199912212355.PAA25570@erdos.hq.askjeeves.com>; from Jason Nordwick on Dec 12, 1999 at 03:55:18PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 12, 1999 at 03:55:18PM -0800, Jason Nordwick wrote: > > >In article you write: > >>In my case, load is reasonably distributed. Is poll() really that much > >>better than select()? I thought that, excepting bit flag manipulations, > >>it worked basically the same way on the kernel end. > > > >Yes, it is better. Select uses the same backend as poll(), but those > >"bit flag manipulations" that you are talking about consume a measurable > >amount of CPU time when you start throwing thousands of descriptors at it. > >-- > >Jonathan > > > > I cannot believe that this is true. It would seem, to me, that it is highly > dependant on the density of the interest bit vector of select(). If it is > very dense, then select is more appropriate. Obviously, if you are only > interested in fd# 5 and fd# 1000, then, yes, there is unecessary scanning. > However is you are interested in 90% of the descriptors from 5 to 1000, then > all the scanning is necessary. (you can also, obviously, look through 32 > descriptors at a time). > > Also, doesn't the kernel need to copy the argument arrays into kernel space. > A struct pollfd is 8 bytes per interested descriptor, whereas, select() only > needs 1 bit per interested descriptor. If I am interested in 1000 descriptors > (assuming in a row), that is 8000 bytes to copyin, versus 125 bytes. > > Can somebody who knows better explain, please? I'd suggest doing your own measurements. :-) Possibly it's application dependent. For my application, the overhead of copying more bytes is outweighed by the CPU time spent bit twiddling. I'll also note that you can set up the poll array for 100% density, so you don't have to copyin/out descriptors you aren't interested in. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 15:17:15 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 69F1015577 for ; Tue, 21 Dec 1999 15:17:09 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p14-dn01kiryunisiki.gunma.ocn.ne.jp [210.132.6.143]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id IAA19403; Wed, 22 Dec 1999 08:16:37 +0900 (JST) Message-ID: <38600996.EFC47AFE@newsguy.com> Date: Wed, 22 Dec 1999 08:13:26 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Justin Hawkins Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Justin Hawkins wrote: > > I understand it's not really a bug and perhaps is not worth the code > effort. A note in the handbook might not go astray - I am sure a lot of > people who need a COM2 console will have modem on COM1. A note on the handbook and/or man pages can certainly be done. I'd be happy to apply any such changes you volunteer. You might add that before trying this, replacing loader.rc with one with the single line "boot" will garantee that loader will not stop. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 15:50: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tardis.mx.com.au (tardis.mx.com.au [203.34.34.73]) by hub.freebsd.org (Postfix) with ESMTP id BD8BC14D56 for ; Tue, 21 Dec 1999 15:49:56 -0800 (PST) (envelope-from justin@tardis.mx.com.au) Received: from localhost (justin@localhost) by tardis.mx.com.au (8.9.3/8.9.3) with ESMTP id KAA00947; Wed, 22 Dec 1999 10:19:11 +1030 (CST) (envelope-from justin@tardis.mx.com.au) Date: Wed, 22 Dec 1999 10:19:10 +1030 (CST) From: Justin Hawkins To: "Daniel C. Sobral" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem In-Reply-To: <38600996.EFC47AFE@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Dec 1999, Daniel C. Sobral wrote: > Justin Hawkins wrote: > > > > I understand it's not really a bug and perhaps is not worth the code > > effort. A note in the handbook might not go astray - I am sure a lot of > > people who need a COM2 console will have modem on COM1. > > A note on the handbook and/or man pages can certainly be done. I'd be > happy to apply any such changes you volunteer. You might add that before > trying this, replacing loader.rc with one with the single line "boot" > will garantee that loader will not stop. Where is the 'boot' option documented - I couldn't find it in loader.conf(5). What does it do - does it disable all input, or does it create a failsafe where is does something sensible in case garbage is received over the serial line/keyboard. Regarding the documentation change, something like: -- Note that if you cannot use sio0 because a modem lives on that port, be sure to have it switched off while you are making the changes below. If you reboot while the changes are not complete, and the boot loader is still looking at sio0, the modem will echo the boot loaders banner back at the boot loader, most likely causing the boot process to stop. Once you are sure that the boot loader is looking at sio1 (or whichever port you have changed it to) the modem can be safely left on during bootup. -- This probably fits under the paragraph: Using a port other than sio0 as the console requires some recompiling. If you want to use another serial port for whatever reasons, recompile the boot blocks, the boot loader and the kernel as follows. in 14.5.4.2. I think I need to have a look at how to submit documtation changes properly :-) While I think of it, it might be worth a bit more explanation in step 7: 7. Write the boot blocks to the boot disk with disklabel(8) and boot from the new kernel. Maybe something like: 7. Write the boot blocks to the boot disk with disklabel(8) with the -B option. For instance, if your boot disk is wd0, use 'disklabel -B wd0' 8. Boot from the new kernel. (Well I hope that's the right way to use disklabel, worked for me :-) - Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 16:24: 8 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id D7D8815022; Tue, 21 Dec 1999 16:24:02 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id TAA07925; Tue, 21 Dec 1999 19:28:11 -0500 From: Bill Paul Message-Id: <199912220028.TAA07925@skynet.ctr.columbia.edu> Subject: Possible solution for USB Ethernet problem To: hackers@freebsd.org Date: Tue, 21 Dec 1999 19:28:09 -0500 (EST) Cc: n_hibma@freebsd.org X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2876 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Previously I mentioned that I was having trouble sending full sized ethernet frames (1500 bytes) over USB using my ADMtek AN986 Pegasus eval board. The problem turned out to be in the uhci driver, however I'm not certain exactly how to incorporate my fix. The problem I was seeing was that large frames would trigger babble errors, which would cause an endpoint halt and wedge the RX or TX pipe. Julian brought up another driver written by Doug Ambrisko which appeared to be able to transfer 1500-byte frames without any trouble. However, neither he nor Doug bothered to mention if their test machines had UHCI or OHCI hubs. Given what I've learned, I suspect they were OHCI. I downloaded a copy of the Intel UHCI spec document from ftp://download.intel.com/design/usb/UHCI11D.PDF and scrutinized it for a while. On page 17, it describes the MAXP bit in the command register. The description reads: Max Packet (MAXP). 1=64 bytes, 0=32 bytes. This bit selects the maximum packet size that can be used for full speed bandwitdh reclamation at the end of a frame. This value is used by the Host Controller to determine whether it should initiate another transaction based on the time remaining in the SOF counter. Use of reclamation packets larger than the programmed size will cause a Babble error if executed during the critical window at frame end. The Babble error results in the offending endpoint being stalled. Software is responsible for ensuring that any packet which could be executed under bandwidth reclamation be within this size limit. The ADMtek part is documented to use 64-byte USB packets for frame transfers. However, /sys/dev/usb/uhci.c:uhci_run() never sets the MAXP bit in the command register when it starts the controller running. I modified uhci_run() to include the UHCI_CMD_MAXP bit and now the ADMtek ethernet controller sends and receives 1500-byte frames with no problems. The question is, how should this be handled? Should the UHCI_CMD_MAXP bit be set all the time, or just when high speed devices are attached to the bus? The Intel manual seems to imply that it's safe to leave this bit enabled all the time, however I can't test this since I only have the one USB device. Also, should something similar be done with OHCI controllers, or do they handle this sort of thing correctly? -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 16:35:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 46E2E14EF2 for ; Tue, 21 Dec 1999 16:35:32 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id TAA193614; Tue, 21 Dec 1999 19:35:23 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <385F2FFD.CA594829@softweyr.com> References: <199912190410.UAA01049@apollo.backplane.com> <385C789C.DD290597@softweyr.com> <385F2FFD.CA594829@softweyr.com> Date: Tue, 21 Dec 1999 19:40:59 -0500 To: Wes Peters From: Garance A Drosihn Subject: Re: Cool little 100BaseTX switch - they're coming down in price Cc: freebsd-hackers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:45 AM -0700 12/21/99, Wes Peters wrote: >Garance A Drosihn wrote: > > [...] but I was wondering how much one has to fork out before you > > get extra options like a port-mirroring capability... > >Lots more, in terms of dollars. For this, you need at least a managed >switch, and probably a smart switch. I know for a fact this one, [...] >For more info about both, see: > >http://www.ind.alcatel.com/enterprise/products/omnistack/ost04.html > >Note that these are "Layer 3" switches with VLAN support, IP and IPX routing, >etc. The per-port prices aren't that different than the simpler managed >switches, but the port count tends to be high. Thanks for all the replies. I should have mentioned that I'm thinking of this as an "office switch". I have a 10baseT connection coming into my office (you might ask "why?"-- I know I do!), but several machines in here which can do 100baseT. I figured that with a switch I can at least get faster connections between my own machines, and keep all my intra-office traffic off the 10baseT leg at the same time. The upshot of this is that the 80-port options that some people have mentioned are probably a bit overkill for my office... :-) >Caveat: I work on these things daily. Consider whatever I say about them >to be evangelism. Also note that turning on software-dependent features >like port mirroring can do terrible things to your throughput if not used >judiciously. My idea was to take the 10baseT connection coming into my office (the other end of which is on a hub, not a switch...), and mirror it to a port on a machine which isn't used for much. That way I could use that machine to do tcpdump's of the traffic on the 10baseT subnet, even though all the traffic between office machines will be on the switch. Sounds like I'd be better off financially to have a simple 10baseT hub, and plug both an unmanaged switch and my spare machine into that hub. But if I were to go with a managed switch, what is it that you're warning me about? If I mirror all the 10baseT traffic on the port for my spare machine, will that effect the throughput to just my spare machine (which is fine by me), or will it also slow down throughput between machines on other ports of the switch? Pardon the tangents, but I'm just curious... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 16:59:27 1999 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 D44F314D08; Tue, 21 Dec 1999 16:59:25 -0800 (PST) (envelope-from ambrisko@whistle.com) Received: from whistle.com (crab.whistle.com [207.76.205.112]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id QAA84456; Tue, 21 Dec 1999 16:59:20 -0800 (PST) Received: (from ambrisko@localhost) by whistle.com (8.9.1/8.9.1) id QAA02378; Tue, 21 Dec 1999 16:59:01 -0800 (PST) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <199912220059.QAA02378@whistle.com> Subject: Re: Possible solution for USB Ethernet problem In-Reply-To: <199912220028.TAA07925@skynet.ctr.columbia.edu> from Bill Paul at "Dec 21, 99 07:28:09 pm" To: wpaul@skynet.ctr.columbia.edu (Bill Paul) Date: Tue, 21 Dec 1999 16:59:01 -0800 (PST) Cc: hackers@FreeBSD.ORG, n_hibma@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL29 (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 Bill Paul writes: | Previously I mentioned that I was having trouble sending full sized | ethernet frames (1500 bytes) over USB using my ADMtek AN986 Pegasus | eval board. The problem turned out to be in the uhci driver, however | I'm not certain exactly how to incorporate my fix. | | The problem I was seeing was that large frames would trigger babble | errors, which would cause an endpoint halt and wedge the RX or TX pipe. | Julian brought up another driver written by Doug Ambrisko which appeared | to be able to transfer 1500-byte frames without any trouble. However, | neither he nor Doug bothered to mention if their test machines had UHCI | or OHCI hubs. Given what I've learned, I suspect they were OHCI. We used both OHCI to itself for initial debugging then an OHCI machine to UHCI and a UHCI to UHCI. So it didn't seem that saying what stack we used was important since they both worked for us. This was -current as of a week or so ago. We did run into an issue with OHCI, in that if we plugged in any USB device after the machine was booted we would get the td_??? panic. So we had to have the device plugged in when we booted the machine. After the machine was up we could unplug it and plug it back in. For testing we did ping's and ftp's of /kernel and it worked okay. I also ran netperf and got 3.4Mbits/sec with MTU's of 900 & 1500. So we are not saying the USB stack is perfect, but it worked for us. Doug A. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 17: 9:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 7067E14BF3 for ; Tue, 21 Dec 1999 17:09:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04353; Tue, 21 Dec 1999 17:13:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912220113.RAA04353@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Justin Hawkins Cc: freebsd-hackers@freebsd.org Subject: Re: Serial boot prompt messages and a modem In-reply-to: Your message of "Mon, 20 Dec 1999 20:41:41 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Dec 1999 17:13:07 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've recently had .. ahem .. fun trying to get my headless FreeBSD box to > spit messages at the console. I've got the kernel doing it right, but not > the boot loaders. The boot loader will print to the serial device - but it > won't load my kernel :-( I haven't exhausted all oppurtunities here yet - > this isn't a cry for help on that. > > The reason I need to play around with the boot loaders is that I need the > serial console on COM2. I have a modem on COM1. Before you ask, I can't > swap them over easily, I'd need to swap the connectors internally or buy > some 9-25 adaptors. But I digress. "Swapping them internally" would probably involve about 30 seconds of work. It's not hard, really. 8) > I think (I am not positive on this) that if the boot loader talks to a > modem in command mode with echo on, it gets confused and won't boot any > further. Is this a known problem? Yes. The solution is "do not connect a modem with echo enabled to the console". The loader will spend endless hours talking to the modem (and if _it_ didn't, getty would a few seconds later). > Is there enough room in there for some code, which checks for this? IE if > the first line output to the serial device == the first input (some > version string probably) then it just ignores it and does the default > action? No. Wrong solution. Connect your console to the console port and your modem to the modem port. > Sorry about the vagueness - I didn't have time to test this or gain any > real empirical evidence - I needed to get the machine back in action ASAP. Sorry about the fascist attitude, but you really do just need to Do The Right Thing here. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 17:26: 5 1999 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 E3E3D14DBD; Tue, 21 Dec 1999 17:26:01 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA85168; Tue, 21 Dec 1999 17:25:52 -0800 (PST) Date: Tue, 21 Dec 1999 17:25:50 -0800 (PST) From: Julian Elischer To: Bill Paul Cc: hackers@FreeBSD.ORG, n_hibma@FreeBSD.ORG Subject: Re: Possible solution for USB Ethernet problem In-Reply-To: <199912220028.TAA07925@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG we were usug both IHCI and UHCI which is why we didn't mention it. we DID have a problem one one of them (which seemed unrelated) but I can't remember which. It was reported by other people around the same time so we didn't connect it with our driver. On Tue, 21 Dec 1999, Bill Paul wrote: > Previously I mentioned that I was having trouble sending full sized > ethernet frames (1500 bytes) over USB using my ADMtek AN986 Pegasus > eval board. The problem turned out to be in the uhci driver, however > I'm not certain exactly how to incorporate my fix. > > The problem I was seeing was that large frames would trigger babble > errors, which would cause an endpoint halt and wedge the RX or TX pipe. > Julian brought up another driver written by Doug Ambrisko which appeared > to be able to transfer 1500-byte frames without any trouble. However, > neither he nor Doug bothered to mention if their test machines had UHCI > or OHCI hubs. Given what I've learned, I suspect they were OHCI. > I downloaded a copy of the Intel UHCI spec document from > ftp://download.intel.com/design/usb/UHCI11D.PDF and scrutinized it > for a while. On page 17, it describes the MAXP bit in the command > register. The description reads: > > Max Packet (MAXP). 1=64 bytes, 0=32 bytes. This bit selects the > maximum packet size that can be used for full speed bandwitdh > reclamation at the end of a frame. This value is used by the > Host Controller to determine whether it should initiate another > transaction based on the time remaining in the SOF counter. Use > of reclamation packets larger than the programmed size will > cause a Babble error if executed during the critical window at > frame end. The Babble error results in the offending endpoint > being stalled. Software is responsible for ensuring that any > packet which could be executed under bandwidth reclamation be > within this size limit. > > The ADMtek part is documented to use 64-byte USB packets for frame > transfers. However, /sys/dev/usb/uhci.c:uhci_run() never sets the > MAXP bit in the command register when it starts the controller running. > I modified uhci_run() to include the UHCI_CMD_MAXP bit and now the > ADMtek ethernet controller sends and receives 1500-byte frames with > no problems. > > The question is, how should this be handled? Should the UHCI_CMD_MAXP > bit be set all the time, or just when high speed devices are attached > to the bus? The Intel manual seems to imply that it's safe to leave this > bit enabled all the time, however I can't test this since I only have > the one USB device. Also, should something similar be done with OHCI > controllers, or do they handle this sort of thing correctly? > > -Bill > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 17:27:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tardis.mx.com.au (tardis.mx.com.au [203.34.34.73]) by hub.freebsd.org (Postfix) with ESMTP id 7A7F914EA1; Tue, 21 Dec 1999 17:27:03 -0800 (PST) (envelope-from justin@tardis.mx.com.au) Received: from localhost (justin@localhost) by tardis.mx.com.au (8.9.3/8.9.3) with ESMTP id LAA01480; Wed, 22 Dec 1999 11:56:47 +1030 (CST) (envelope-from justin@tardis.mx.com.au) Date: Wed, 22 Dec 1999 11:56:45 +1030 (CST) From: Justin Hawkins To: Mike Smith Cc: freebsd-hackers@freebsd.org Subject: Re: Serial boot prompt messages and a modem In-Reply-To: <199912220113.RAA04353@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 21 Dec 1999, Mike Smith wrote: > "Swapping them internally" would probably involve about 30 seconds of > work. It's not hard, really. 8) Yes I know I could have done that. Then reconfigured my getty's, my minicom etc. It's the principle of the thing - I prefer to bend the software to my will rather than have to open the case. > Yes. The solution is "do not connect a modem with echo enabled to the > console". The loader will spend endless hours talking to the modem (and > if _it_ didn't, getty would a few seconds later). The getty is not a problem - it's configured correctly for my modem on com1. > No. Wrong solution. Connect your console to the console port and your > modem to the modem port. Hmm, last time I checked, they were just 'serial ports'. > Sorry about the fascist attitude, but you really do just need to Do The > Right Thing here. :-) I think the Right Thing is either way. Otherwise there wouldn't be documentation on how to change it to some other com port would there? A hardware swap would hardly by The Right Thing if the box was a few thousand kilometres away would it? I would expect a Microsoft product to force me to change my hardware to fit what the software wants - not FreeBSD. At any rate, the point is moot, it now works. I never had any real issue with the "problem" - I knew I would be able to resolve it in some way. I merely wanted to know if it was feasible to change the software to cope with this situation, and if not then a little note (which I have supplied) to add to the documentation for those less cluefull than me (Dog knows there must be one or two out there) is a nice touch, and equally useful. FreeBSD documentation is already very impressive, if I can help one other person avoid the (admittedly minor) problem I had, I'm happy. - Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 17:35:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id CE97214A2B; Tue, 21 Dec 1999 17:35:11 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04766; Tue, 21 Dec 1999 17:38:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912220138.RAA04766@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Justin Hawkins Cc: Mike Smith , freebsd-hackers@freebsd.org Subject: Re: Serial boot prompt messages and a modem In-reply-to: Your message of "Wed, 22 Dec 1999 11:56:45 +1030." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Dec 1999 17:38:35 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > "Swapping them internally" would probably involve about 30 seconds of > > work. It's not hard, really. 8) > > Yes I know I could have done that. Then reconfigured my getty's, my > minicom etc. It's the principle of the thing - I prefer to bend the > software to my will rather than have to open the case. I prefer to tell people to Do It Right the first time. Less work for me. 8) > > No. Wrong solution. Connect your console to the console port and your > > modem to the modem port. > > Hmm, last time I checked, they were just 'serial ports'. Nope. The significance is determined by the software, and you're stuck with the fact that the first serial port is the console port. End of story. (Note: if we don't make some assumption about which port will be the console, how do you expect the software to work out which one it "should" use?) > > Sorry about the fascist attitude, but you really do just need to Do The > > Right Thing here. > > :-) > > I think the Right Thing is either way. Otherwise there wouldn't be > documentation on how to change it to some other com port would there? Not a good assumption. The documentation is on how to assign the console to a different 'sio' device, not to a different physical port. > A hardware swap would hardly by The Right Thing if the box was a few > thousand kilometres away would it? I would expect a Microsoft product to > force me to change my hardware to fit what the software wants - not > FreeBSD. You wouldn't have (correctly) assembled the system with things the wrong way around before shipping it, so I don't consider this a problem. > At any rate, the point is moot, it now works. I never had any real issue > with the "problem" - I knew I would be able to resolve it in some way. I > merely wanted to know if it was feasible to change the software to cope > with this situation, and if not then a little note (which I have supplied) > to add to the documentation for those less cluefull than me (Dog knows > there must be one or two out there) is a nice touch, and equally > useful. The update is appreciated. There's no clean or even functional way to tweak the software, so we have to stick with what we've got. 8( -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 18:41:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from slug.rigelfore.com (adsl-63-198-180-111.dsl.snfc21.pacbell.net [63.198.180.111]) by hub.freebsd.org (Postfix) with SMTP id 2C66814DCE for ; Tue, 21 Dec 1999 18:41:29 -0800 (PST) (envelope-from m_thrope@rigelfore.com) Received: (qmail 142 invoked from network); 22 Dec 1999 02:39:21 -0000 Received: from unknown (HELO rigelfore.com) (192.168.42.2) by 192.168.42.1 with SMTP; 22 Dec 1999 02:39:20 -0000 Message-ID: <38603A40.D5FE1ADC@rigelfore.com> Date: Tue, 21 Dec 1999 18:41:04 -0800 From: Eric Melville X-Mailer: Mozilla 4.5 [en] (Win95; U) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: firewall help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i was told by a freebsd friend to ask you this question: can *bsd do kernel-space ip port forwarding? thanks. -E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 19: 0:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 8831B14D77; Tue, 21 Dec 1999 19:00:21 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id NAA13615; Wed, 22 Dec 1999 13:30:15 +1030 (CST) (envelope-from newton) Date: Wed, 22 Dec 1999 13:30:15 +1030 From: Mark Newton To: Mike Smith Cc: Justin Hawkins , freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem Message-ID: <19991222133015.B13504@internode.com.au> References: <199912220138.RAA04766@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912220138.RAA04766@mass.cdrom.com> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 21, 1999 at 05:38:35PM -0800, Mike Smith wrote: > > Hmm, last time I checked, they were just 'serial ports'. > > Nope. The significance is determined by the software, and you're stuck > with the fact that the first serial port is the console port. End of > story. (Note: if we don't make some assumption about which port will be > the console, how do you expect the software to work out which one it > "should" use?) Insist that consoles be cabled-in with "real" cables, and use the first port we find with DCD asserted as the console, falling back to COM1 if we can't find any ports with DCD (indicating that someone has failed to follow our cabling insistence) - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 22:17:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from srv4-bsb.bsb.nutecnet.com.br (argonio.bsb.nutecnet.com.br [200.252.253.4]) by hub.freebsd.org (Postfix) with ESMTP id 11F6715049; Tue, 21 Dec 1999 22:17:51 -0800 (PST) (envelope-from visi0n@aux-tech.org) Received: from ebola.chinatown.org ([200.252.15.93]) by srv4-bsb.bsb.nutecnet.com.br (8.8.5/SCA-6.6) with ESMTP id FAA26035; Wed, 22 Dec 1999 05:23:55 -0200 (BRV) Date: Wed, 22 Dec 1999 04:16:10 -0200 (EDT) From: visi0n X-Sender: visi0n@ebola.chinatown.org To: freebsd-hackers@FreeBSD.ORG Cc: freebsd-net@freebsd.org Subject: sk_buff vs mbuf 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 Is there someone closer to a linux box, tell me if sk_buff is more fast than mbuf. I was reading these codes but I can't figure out the final result. =============================================================================== visi0n AUX Technologies [www.aux-tech.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Dec 21 22:33:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.xmission.com (mail.xmission.com [198.60.22.22]) by hub.freebsd.org (Postfix) with ESMTP id 98EF6152EB for ; Tue, 21 Dec 1999 22:33:21 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com) by mail.xmission.com with esmtp (Exim 3.03 #3) id 120fKm-0005k9-00; Tue, 21 Dec 1999 23:33:17 -0700 Message-ID: <3860711B.A9098FE3@softweyr.com> Date: Tue, 21 Dec 1999 23:35:07 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Garance A Drosihn Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <199912190410.UAA01049@apollo.backplane.com> <385C789C.DD290597@softweyr.com> <385F2FFD.CA594829@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 Garance A Drosihn wrote: > > At 12:45 AM -0700 12/21/99, Wes Peters wrote: > >Garance A Drosihn wrote: > > > [...] but I was wondering how much one has to fork out before you > > > get extra options like a port-mirroring capability... > > > >Lots more, in terms of dollars. For this, you need at least a managed > >switch, and probably a smart switch. I know for a fact this one, [...] > > >For more info about both, see: > > > >http://www.ind.alcatel.com/enterprise/products/omnistack/ost04.html > > > >Note that these are "Layer 3" switches with VLAN support, IP and IPX routing, > >etc. The per-port prices aren't that different than the simpler managed > >switches, but the port count tends to be high. > > Thanks for all the replies. I should have mentioned that I'm thinking of > this as an "office switch". I have a 10baseT connection coming into my > office (you might ask "why?"-- I know I do!), but several machines in > here which can do 100baseT. I figured that with a switch I can at least > get faster connections between my own machines, and keep all my intra-office > traffic off the 10baseT leg at the same time. > > The upshot of this is that the 80-port options that some people have > mentioned are probably a bit overkill for my office... :-) Yeah. You should see some of the monsters we have in the test lab. 256 ports of switched 10/100 in one chassis. You should see the price tag, too. ;^) > >Caveat: I work on these things daily. Consider whatever I say about them > >to be evangelism. Also note that turning on software-dependent features > >like port mirroring can do terrible things to your throughput if not used > >judiciously. > > My idea was to take the 10baseT connection coming into my office (the > other end of which is on a hub, not a switch...), and mirror it to a > port on a machine which isn't used for much. That way I could use > that machine to do tcpdump's of the traffic on the 10baseT subnet, > even though all the traffic between office machines will be on the > switch. Sounds like I'd be better off financially to have a simple > 10baseT hub, and plug both an unmanaged switch and my spare machine > into that hub. > > But if I were to go with a managed switch, what is it that you're > warning me about? If I mirror all the 10baseT traffic on the port > for my spare machine, will that effect the throughput to just my > spare machine (which is fine by me), or will it also slow down > throughput between machines on other ports of the switch? In the Xylan architecture -- I assume others are similar -- all of the traffic on the mirrored port has to be handled in software instead of the switching hardware. This is handled by the processors in the network interface, or "blade." Trying to mirror too many ports will overwhelm the interface processor and slow down the mirrored ports. Ports that are still being switched by the hardware will be unaffected. Getting a small 8-port switch and a cheap hub would be a LOT less expensive. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 1:22:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from onion.ish.org (onion.ish.org [210.145.219.202]) by hub.freebsd.org (Postfix) with ESMTP id C1101150FF for ; Wed, 22 Dec 1999 01:22:47 -0800 (PST) (envelope-from ishizuka@ish.org) Received: from localhost (ishizuka@localhost [127.0.0.1]) by onion.ish.org (8.9.3/3.7Wpl1-08/27/98) with ESMTP id SAA67394 for ; Wed, 22 Dec 1999 18:22:45 +0900 (JST) To: freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD 3.4-RELEASE is now available In-Reply-To: <199912201845.KAA01421@zippy.cdrom.com> References: <199912201845.KAA01421@zippy.cdrom.com> X-Mailer: Mew version 1.94 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint20: 276D 697A C2CB 1580 C683 8F18 DA98 1A4A 50D2 C4CB X-PGP-Fingerprint16: C6 DE 46 24 D7 9F 22 EB 79 E2 90 AB 1B 9A 35 2E X-PGP-Public-Key: http://www.ish.org/pgp-public-key.txt X-URL: http://www.ish.org/ Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991222182245F.ishizuka@onion.ish.org> Date: Wed, 22 Dec 1999 18:22:45 +0900 From: Masachika ISHIZUKA X-Dispatcher: imput version 990905(IM130) Lines: 13 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. This is ishizuka@ish.org I got 3.4-RELEASE from ftp://ftp.freebsd.org/pub/FreeBSD/releases/i386/3.4-RELEASE. But, XF86335/Xlk*.tgz are not match XF86335/SUMS.MD5. I want to know were there forged or not. | % md5 Xlk* | MD5 (Xlk98.tgz) = 79232ed51169d9e242a63d5f13b7f174 | MD5 (Xlkit.tgz) = d076fac0ab1435478da9702787f208e8 Thanks for your advice. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 3:48:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (dialfwn11.fwn.rug.nl [129.125.32.161]) by hub.freebsd.org (Postfix) with ESMTP id 3330414EFF for ; Wed, 22 Dec 1999 03:48:52 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id LAA00689; Wed, 22 Dec 1999 11:43:54 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Wed, 22 Dec 1999 11:43:54 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Bill Paul Cc: hackers@freebsd.org Subject: Re: Possible solution for USB Ethernet problem In-Reply-To: <199912220028.TAA07925@skynet.ctr.columbia.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nice catch (of yet another stupidity in the UHCI controllers). In 1.3.1 they say that 'the preSOF point also prevents a packet that may not fit in the remaining frame period from being initiated.' So the UHCI controller should not start a 64 byte transfer if the MAXP is not set. What happens probably is that the controller does start it and ends up overruning its SOF. The reason for not setting it is that using a MAXP of 32 is more efficient. However, up to now I;ve not seen a device with a packet size of 32 (only 64, 16 and smaller). So switching it on should be no problem. You have a 'Intel 82371SB (PIIX3) USB controller' ? If so, we might be looking at a problem with the 1.0 specification. (please post 'dmesg|grep USB'). I have never had a BABBLE error here, which indicates to me that there was a problem with the 82371SB, which has been solved in the AB/EB. Hm, I'll have to find someone with an 82371SB board and borrow that for a while to get a trace and see what is happening on the wire. This problem should show up with any bulk-64b device if you are right. Cheers, Nick > I downloaded a copy of the Intel UHCI spec document from > ftp://download.intel.com/design/usb/UHCI11D.PDF and scrutinized it > for a while. On page 17, it describes the MAXP bit in the command > register. The description reads: > > Max Packet (MAXP). 1=64 bytes, 0=32 bytes. This bit selects the > maximum packet size that can be used for full speed bandwitdh > reclamation at the end of a frame. This value is used by the > Host Controller to determine whether it should initiate another > transaction based on the time remaining in the SOF counter. Use > of reclamation packets larger than the programmed size will > cause a Babble error if executed during the critical window at > frame end. The Babble error results in the offending endpoint > being stalled. Software is responsible for ensuring that any > packet which could be executed under bandwidth reclamation be > within this size limit. > > The ADMtek part is documented to use 64-byte USB packets for frame > transfers. However, /sys/dev/usb/uhci.c:uhci_run() never sets the > MAXP bit in the command register when it starts the controller running. > I modified uhci_run() to include the UHCI_CMD_MAXP bit and now the > ADMtek ethernet controller sends and receives 1500-byte frames with > no problems. > > The question is, how should this be handled? Should the UHCI_CMD_MAXP > bit be set all the time, or just when high speed devices are attached > to the bus? The Intel manual seems to imply that it's safe to leave this > bit enabled all the time, however I can't test this since I only have > the one USB device. Also, should something similar be done with OHCI > controllers, or do they handle this sort of thing correctly? > > -Bill > > -- > ============================================================================= > -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu > Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research > Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City > ============================================================================= > "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" > ============================================================================= > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 3:58:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ravi.lums.edu.pk (ravi.lums.edu.pk [203.128.0.4]) by hub.freebsd.org (Postfix) with ESMTP id D77261508A for ; Wed, 22 Dec 1999 03:58:13 -0800 (PST) (envelope-from 01020042@ravi.lums.edu.pk) Received: from ravi.lums.edu.pk (ravi.lums.edu.pk [203.128.0.4]) by ravi.lums.edu.pk (8.8.8/8.8.5) with SMTP id QAA27385 for ; Wed, 22 Dec 1999 16:58:06 +0500 (PKT) Date: Wed, 22 Dec 1999 16:58:06 +0500 (PKT) From: Tiger <01020042@ravi.lums.edu.pk> To: hackers@freebsd.org Subject: Code 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 like to know where can I get explanation and documentation of freebsd source and if process migration has been implemented in Freebsd. I plan to work in freebsd environment but first I would have to understand the code. I would like to know who can help me in my objective. Are there any mailing list where one can get help in understanding code. How elaborate is the documentation of Freebsd. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 6:11:41 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (Postfix) with SMTP id 2093B14D28 for ; Wed, 22 Dec 1999 06:11:37 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 15107 invoked from network); 22 Dec 1999 14:11:35 -0000 Received: from citadel.in.taronga.com (10.0.0.43) by mushi.in.taronga.com with SMTP; 22 Dec 1999 14:11:35 -0000 Received: by citadel.in.taronga.com (Postfix, from userid 100) id 57142322FC; Wed, 22 Dec 1999 08:10:45 -0600 (CST) To: hackers@freebsd.org Subject: Re: Cool little 100BaseTX switch - they're coming down in price X-Newsgroups: taronga.freebsd.hackers In-Reply-To: <199912190556.AAA08484@whizzo.transsys.com> References: <199912190410.UAA01049@apollo.backplane.com> <385C60FC.7613CB55@bellatlantic.net> <19991218225758.A23729@futuresouth.com>,<19991218225758.A23729@futuresouth.com> Organization: Cc: Message-Id: <19991222141045.57142322FC@citadel.in.taronga.com> Date: Wed, 22 Dec 1999 08:10:45 -0600 (CST) From: peter@taronga.com (Peter da Silva) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199912190556.AAA08484@whizzo.transsys.com>, Louis A. Mamakos wrote: >I noticed another, smaller IC which had a hole blown out of the epoxy case >(which subsequently allowed the smoke to escape. [...] >In a "what the hell" move, I powered up the ethernet Netgear Ethernet switch >with it's preferred 5V power brick -- AND IT WORKS JUST FINE! Well mostly; >I think the chip with the hole was involved in driving the Transmit/Collision >LEDs which don't do anything anymore. But pushing packets through the box >seems to work great; it's still doing the bridge thing of forwarding traffic >to the right port, etc. I've run into really horribly mutilated ICs that kept working. When I was at Berkeley they had a display with a little 555-based oscillator driving an LED in Cory Hall (engineering). The 555 had a pit blown in the epoxy and you could see the silicon at the bottom of the pit. Looked just like a car window that had been plinked by a rock. Still worked just fine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 6:32:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from acl.lanl.gov (acl.lanl.gov [128.165.147.1]) by hub.freebsd.org (Postfix) with ESMTP id D925C14BEC for ; Wed, 22 Dec 1999 06:32:23 -0800 (PST) (envelope-from rminnich@lanl.gov) Received: from localhost (rminnich@localhost) by acl.lanl.gov (8.8.8/8.8.5) with ESMTP id HAA276462; Wed, 22 Dec 1999 07:32:21 -0700 (MST) X-Authentication-Warning: acl.lanl.gov: rminnich owned process doing -bs Date: Wed, 22 Dec 1999 07:32:21 -0700 From: "Ronald G. Minnich" To: David Quattlebaum Cc: "'FreeBSD Hackers'" Subject: Re: modifying an object file In-Reply-To: <5FA575D78630D3118B2E0090276DC89F01B59270@merc08.us.sas.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 you can do this kind of thing with the bfd tools ... ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 6:47:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from locsg.garant.ru (locsg.garant.ru [195.209.33.196]) by hub.freebsd.org (Postfix) with ESMTP id 5F80114D70; Wed, 22 Dec 1999 06:47:40 -0800 (PST) (envelope-from taurus@cave.garant.ru) Received: from cave.garant.ru (cave.garant.ru [10.14.3.31]) by locsg.garant.ru (8.9.3/8.9.3) with ESMTP id RAA19376; Wed, 22 Dec 1999 17:46:44 +0300 (MSK) Received: from localhost (taurus@localhost) by cave.garant.ru (8.9.3/8.9.3) with ESMTP id RAA12213; Wed, 22 Dec 1999 17:47:25 +0300 (MSK) Date: Wed, 22 Dec 1999 17:47:23 +0300 (MSK) From: "Andrew A. Bely" To: freebsd-stable@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: ATAPI problems in 3.2-RELEASE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi There is a problem with an ATAPI devices - CD-ROM, TAPE All of it successfully detects but when i try to get access to them the term with current process hanging up... and neither Ctrl-C nor 'kill -9 xxx' can't ends it ( only reboot helps ). Devices are not accessable. Can anybody advise something? Thanks. Here is dmesg output: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-RELEASE #7: Mon Oct 11 19:59:34 GMT 1999 andrew@home:/usr/src/sys/compile/VAULT Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (350.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff> real memory = 134217728 (131072K bytes) avail memory = 127741952 (124748K bytes) Preloaded elf kernel "kernel" at 0xc02b4000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 chip3: rev 0x02 on pci0.7.3 wb0: rev 0x00 int a irq 5 on pci0.14.0 wb0: Ethernet address: 00:80:48:db:55:70 wb0: autoneg complete, link status good (half-duplex, 100Mbps) ncr0: rev 0x01 int a irq 10 on pci0.19.0 Probing for devices on PCI bus 1: vga0: rev 0x5c on pci1.0.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 on isa wdc0: unit 0 (atapi): , removable, intr, dma, iordis acd0: drive speed 6875KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wdc1 at 0x170-0x177 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wst0: Drive empty, readonly, reverse, qfa, ecc, 512b wst0: Max speed=600Kb/s, Transfer limit=52 blocks, Buffer size=728 blocks ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers Waiting 15 seconds for SCSI devices to settle changing root device to da0s1a da1 at ncr0 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da0 at ncr0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Andrew A. Bely Software developer in Garant-Service, Moscow, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 7:30:32 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from locsg.garant.ru (locsg.garant.ru [195.209.33.196]) by hub.freebsd.org (Postfix) with ESMTP id 3668614F78; Wed, 22 Dec 1999 07:30:27 -0800 (PST) (envelope-from taurus@cave.garant.ru) Received: from cave.garant.ru (cave.garant.ru [10.14.3.31]) by locsg.garant.ru (8.9.3/8.9.3) with ESMTP id SAA21514; Wed, 22 Dec 1999 18:29:31 +0300 (MSK) Received: from localhost (taurus@localhost) by cave.garant.ru (8.9.3/8.9.3) with ESMTP id SAA12403; Wed, 22 Dec 1999 18:30:11 +0300 (MSK) Date: Wed, 22 Dec 1999 18:30:10 +0300 (MSK) From: "Andrew A. Bely" To: Chris.Smith@raytheon.co.uk Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ATAPI problems in 3.2-RELEASE In-Reply-To: <0025684F.005226F1.00@rslhub.raytheon.co.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 On Wed, 22 Dec 1999 Chris.Smith@raytheon.co.uk wrote: > 1. Does your CD spin up and down for no reason and then the process > accessing it crash? No, it does not. > 2. Is the board a genuine intel one? No again. Maybe it made by MicroStar, but I'm not sure. Andrew A. Bely Software developer in Garant-Service, Moscow, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 8: 7:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 11C54154E9 for ; Wed, 22 Dec 1999 08:07:15 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id LAA09261; Wed, 22 Dec 1999 11:11:17 -0500 From: Bill Paul Message-Id: <199912221611.LAA09261@skynet.ctr.columbia.edu> Subject: Re: Possible solution for USB Ethernet problem To: n_hibma@webweaving.org Date: Wed, 22 Dec 1999 11:11:15 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: from "Nick Hibma" at Dec 22, 99 11:43:54 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 2624 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Nick Hibma had to walk into mine and say: > > Nice catch (of yet another stupidity in the UHCI controllers). > > In 1.3.1 they say that 'the preSOF point also prevents a packet that may > not fit in the remaining frame period from being initiated.' So the UHCI > controller should not start a 64 byte transfer if the MAXP is not set. > > What happens probably is that the controller does start it and ends up > overruning its SOF. > > The reason for not setting it is that using a MAXP of 32 is more > efficient. However, up to now I;ve not seen a device with a packet size > of 32 (only 64, 16 and smaller). So switching it on should be no > problem. It better not be, since this is the only way this device will work. Leave it to me to get all the oddball hardware. > You have a 'Intel 82371SB (PIIX3) USB controller' ? If so, we might be > looking at a problem with the 1.0 specification. (please post > 'dmesg|grep USB'). I have never had a BABBLE error here, which indicates > to me that there was a problem with the 82371SB, which has been solved > in the AB/EB. isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 uhci0: irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered So this is an AB/EB hub. The machine is a Dell Latitude CPi R400GT laptop, running FreeBSD 4.0-19991221-CURRENT. Note that there appears to be abother unrelated problem, which is that kldloading the usb KLD module into a kernel without USB support compiled in doesn't work: the machine panics immediately after printing the "uhci0: " line above. I bet a quarter it's trying to do yet another tsleep() when it's not really able to. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 9:19:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id 80DC414F97 for ; Wed, 22 Dec 1999 09:19:44 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 97D7C1BA; Wed, 22 Dec 1999 18:19:42 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 8EE7C18F for ; Wed, 22 Dec 1999 18:19:42 +0100 (CET) Date: Wed, 22 Dec 1999 18:19:42 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: freebsd-hackers@freebsd.org Subject: Question about GLIDE... 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 am in the process of porting the GLIDE library to FreeBSD/i386 which is making good progress so far. My worst enemy has been the build system itself and the huge amount if `#ifdef __linux__' in the code. I am doing this in the light of the Quake source code release, which I'd like to play natively with 3dFX hardware... :) (for the interested: I have already gotten the server and X11 client to build, but I haven't tested them yet.) My question is about this particular piece of code in swlibs/fxpci/pcilib/fxlinux.c, around line 70: if (iopl(3)<0) { pciErrorCode = PCI_ERR_NO_IO_PERM; return FXFALSE; } Does anyone know what 'iopl(3)' is supposed to do, and what it's equivalent on FreeBSD is (if at all available)? The code this is in is about opening the /dev/3dfx device (which is not available for FreeBSD so it'll fail anyway), so I _could_ just remove it, but I'm not so certain... Also, IANAL, so could anyone tell me if the 3DFX license permits me to publish my patches under a BSD-style license? Theo van Klaveren http://phoenix.student.utwente.nl / ICQ #1353681 - Why, oh why didn't I take the _blue_ pill? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 9:42:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from knight.cons.org (knight.cons.org [194.233.237.195]) by hub.freebsd.org (Postfix) with ESMTP id 338FD15065 for ; Wed, 22 Dec 1999 09:42:17 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id SAA04505; Wed, 22 Dec 1999 18:42:06 +0100 (CET) Date: Wed, 22 Dec 1999 18:42:06 +0100 From: Martin Cracauer To: Theo van Klaveren Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... Message-ID: <19991222184206.A4478@cons.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Theo van Klaveren on Wed, Dec 22, 1999 at 06:19:42PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Theo van Klaveren wrote: > My question is about this particular piece of code in > swlibs/fxpci/pcilib/fxlinux.c, around line 70: > > if (iopl(3)<0) { > pciErrorCode = PCI_ERR_NO_IO_PERM; > return FXFALSE; > } > > Does anyone know what 'iopl(3)' is supposed to do, int iopl(int level); iopl changes the I/O privilege level of the current pro cess, as specified in level. This call is necessary to allow 8514-compatible X servers to run under Linux. Since these X servers require access to all 65536 I/O ports, the ioperm call is not sufficient. In addition to granting unrestricted I/O port access, run ning at a higher I/O privilege level also allows the pro cess to disable interrupts. This will probably crash the system, and is not recommended. > and what it's equivalent on FreeBSD is (if at > all available)? See /usr/src/sys/i386/linux how it emulates the call. > The code this is in is about opening the /dev/3dfx device > (which is not available for FreeBSD so it'll fail anyway), > so I _could_ just remove it, but I'm not so certain... /dev/3dfx is a special device to allow non-root binaries to access the 3dfx card. Not needed if things run as root. > Also, IANAL, so could anyone tell me if the 3DFX license > permits me to publish my patches under a BSD-style license? Didn't read the license. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 10:17:46 1999 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 8E0D414EC2 for ; Wed, 22 Dec 1999 10:17:44 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id KAA06953; Wed, 22 Dec 1999 10:15:46 -0800 (PST) Date: Wed, 22 Dec 1999 10:15:44 -0800 (PST) From: Julian Elischer To: Tiger <01020042@ravi.lums.edu.pk> Cc: hackers@FreeBSD.ORG Subject: Re: Code 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 BSD source in general is explained in the "RED" daemon book. I believe that it's ISBN number is given in a reference part of the freebsd website. This is getting out of date, but a new one is being planned (probably still a year or two off). Actually the old one is still relevant in most places. as for process migration.. ooooooh the source of many battle in comp.unix in the '80s. SOme people have done a littel work on it but I don't know of any successful work. (particularly migrating open files) On Wed, 22 Dec 1999, Tiger wrote: > I would like to know where can I get explanation and documentation of > freebsd source and if process migration has been implemented in Freebsd. I > plan to work in freebsd environment but first I would have to understand > the code. I would like to know who can help me in my objective. Are there > any mailing list where one can get help in understanding code. How > elaborate is the documentation of Freebsd. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 11: 1:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 9BD8714F84; Wed, 22 Dec 1999 11:01:35 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA143664; Wed, 22 Dec 1999 14:01:33 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <19991221161131.A72885@catkin.nothing-going-on.org> References: <19991221161131.A72885@catkin.nothing-going-on.org> Date: Wed, 22 Dec 1999 14:07:10 -0500 To: Nik Clayton , hackers@FreeBSD.ORG From: Garance A Drosihn Subject: Re: wchar support? Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:11 PM +0000 12/21/99, Nik Clayton wrote: >A hunt through the mailing list archives turned up various messages about >wchar support, in particular a thread last year, pointing at the xview3.2 >libraries. I've just extracted the x11-toolkit/xview port (which unextracts >to xview3.2p1-X11R6, so I assume I've got the right one), but the only >mention of wchar.h in there is a comment in clients/olwm/charset.h > > /* Following macros are defined in via in ALE > >so I figure the information in that thread was either wrong, or is now >out of date. > >Any suggestions appreciated, thanks. My understanding is that the most recent public beta of the wchar support is available at: http://www.cs.rpi.edu/~crossd/FreeBSD I don't know if there are parts of it missing, or if it's just waiting for more people to test it before making it more official. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 15:49:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scam.xcf.berkeley.edu (scam.XCF.Berkeley.EDU [128.32.43.201]) by hub.freebsd.org (Postfix) with SMTP id CBC3214E42 for ; Wed, 22 Dec 1999 15:49:18 -0800 (PST) (envelope-from nordwick@scam.xcf.berkeley.edu) Received: (qmail 5771 invoked by uid 27268); 22 Dec 1999 23:48:53 -0000 Message-ID: <19991222234853.5770.qmail@scam.xcf.berkeley.edu> Date: Tue, 21 Dec 1999 15:55:18 PST To: Jonathan Lemon Cc: cmsedore@maxwell.syr.edu, hackers@FreeBSD.ORG From: Jason Nordwick Subject: Re: Practical limit for number of TCP connections? MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <5769.945906533.1@scam.XCF.Berkeley.EDU> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Return-Path: In-Reply-To: Your message of "Tue, 21 Dec 1999 09:22:04 CST." <199912211522.JAA04702@free.pcs> ---- >>In my case, load is reasonably distributed. Is poll() really that much >>better than select()? I thought that, excepting bit flag manipulations, >>it worked basically the same way on the kernel end. > >Yes, it is better. Select uses the same backend as poll(), but those >"bit flag manipulations" that you are talking about consume a measurable >amount of CPU time when you start throwing thousands of descriptors at it. >-- >Jonathan > I cannot believe that this is true. It would seem, to me, that it is highly dependant on the density of the interest bit vector of select(). If it is very dense, then select is more appropriate. Obviously, if you are only interested in fd# 5 and fd# 1000, then, yes, there is unecessary scanning. However is you are interested in 90% of the descriptors from 5 to 1000, then all the scanning is necessary. (you can also, obviously, look through 32 descriptors at a time). Also, doesn't the kernel need to copy the argument arrays into kernel space. A struct pollfd is 8 bytes per interested descriptor, whereas, select() only needs 1 bit per interested descriptor. If I am interested in 1000 descriptors (assuming in a row), that is 8000 bytes to copyin, versus 125 bytes. Can somebody who knows better explain, please? -jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 16:10: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id DDE9314DB8 for ; Wed, 22 Dec 1999 16:09:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA11643; Wed, 22 Dec 1999 16:09:55 -0800 (PST) (envelope-from dillon) Date: Wed, 22 Dec 1999 16:09:55 -0800 (PST) From: Matthew Dillon Message-Id: <199912230009.QAA11643@apollo.backplane.com> To: Jason Nordwick Cc: Jonathan Lemon , cmsedore@maxwell.syr.edu, hackers@FreeBSD.ORG Subject: Re: Practical limit for number of TCP connections? References: <19991222234853.5770.qmail@scam.xcf.berkeley.edu> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>>it worked basically the same way on the kernel end. :> :>Yes, it is better. Select uses the same backend as poll(), but those :>"bit flag manipulations" that you are talking about consume a measurable :>amount of CPU time when you start throwing thousands of descriptors at it. :>-- :>Jonathan :> : :I cannot believe that this is true. It would seem, to me, that it is highly :dependant on the density of the interest bit vector of select(). If it is :very dense, then select is more appropriate. Obviously, if you are only :interested in fd# 5 and fd# 1000, then, yes, there is unecessary scanning. :However is you are interested in 90% of the descriptors from 5 to 1000, then :all the scanning is necessary. (you can also, obviously, look through 32 :descriptors at a time). : :Also, doesn't the kernel need to copy the argument arrays into kernel space. :A struct pollfd is 8 bytes per interested descriptor, whereas, select() only :needs 1 bit per interested descriptor. If I am interested in 1000 descriptors :(assuming in a row), that is 8000 bytes to copyin, versus 125 bytes. : :Can somebody who knows better explain, please? : :-jason It's a real problem, actually. I'll give you an example: Generally speaking every time you do a select() call with a thousand descriptors, the kernel must test and setup its wait on a thousand descriptors even if only one (or none) has pending data. The moment any single descriptor has data the entire select returns, you wind up processing the one descriptor, then reentering the select. The problem is that, typically, only one descriptor will have new data at a time (since, typically, the data coming in via your network is serialized because you only have one network interface), which means that for light to medium loads you end up with O(N^2) of overhead (scanning 1000 descriptors each time one of them gets a hit). Even though select() is fast and efficient by itself, the N-squaredness of the actual select activity results in significant (noticeable) overhead. Fortunately the problem is much reduced in heavy-load situations, since more descriptors are likely to have data ready on them by the time your program gets around to calling select() again after processing the previous bunch. Even so, select() is not ideal because it tends to plateu the cpu useage beyond a certain point - an ill-use of your available cpu. The typical solution to this problem is to design your program to be multi-fork/select - that is, you take the 1000 descriptors and you dole them out to, say, 30 processes. Each process select()s on only 33 descriptors, greatly reducing the order overhead of the algorithm. There is a second problem that programmers must be sure to avoid, and that is having multiple processes select()ing on the *same* descriptor (for example, a listen socket for accept). Most select() implementations wind up waking up all the processes for every new connection (and, in fact, it could be argued that this is correct since you do not know what any given process will do with the results from the select()). One has the same problem when using multiple processes to select() on a single UDP socket for data. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 17: 8:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.zhongxing.com (szptt103-147.szptt.net.cn [202.103.147.133]) by hub.freebsd.org (Postfix) with SMTP id DB4E5155F9 for ; Wed, 22 Dec 1999 17:08:38 -0800 (PST) (envelope-from miaobo@mail.zhongxing.com) Received: by mail.zhongxing.com(Lotus SMTP MTA v1.2 (600.1 3-26-1998)) id 48256850.0005169B ; Thu, 23 Dec 1999 08:55:34 +0800 X-Lotus-FromDomain: ZTE_LTD From: miaobo@mail.zhongxing.com To: Julian Elischer Cc: hackers@freebsd.org Message-ID: <48256850.0004D3F2.00@mail.zhongxing.com> Date: Thu, 23 Dec 1999 08:53:36 +0800 Subject: Re:Re: Code Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you tell me what does "process migration" mean? Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 17:22: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id DA84D14DB8 for ; Wed, 22 Dec 1999 17:21:59 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p14-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.143]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id KAA17048; Thu, 23 Dec 1999 10:21:42 +0900 (JST) Message-ID: <3861787A.E61A6FAF@newsguy.com> Date: Thu, 23 Dec 1999 10:18:50 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Justin Hawkins Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Justin Hawkins wrote: > > Where is the 'boot' option documented - I couldn't find it in > loader.conf(5). What does it do - does it disable all input, or does it > create a failsafe where is does something sensible in case garbage is > received over the serial line/keyboard. loader(8). Also, autoboot_delay="0" should prevent it from stopping during boot too. Both alternatives simply prevent loader from entering interactive mode. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 17:25: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasknow.com (h139-142-245-96.ss.fiberone.net [139.142.245.96]) by hub.freebsd.org (Postfix) with ESMTP id DCEE6156D0 for ; Wed, 22 Dec 1999 17:24:59 -0800 (PST) (envelope-from freebsd@sasknow.com) Received: from localhost (freebsd@localhost) by sasknow.com (8.9.3/8.9.3) with ESMTP id TAA49693 for ; Wed, 22 Dec 1999 19:25:39 -0600 (CST) (envelope-from freebsd@sasknow.com) Date: Wed, 22 Dec 1999 19:25:39 -0600 (CST) From: Ryan Thompson To: freebsd-hackers@freebsd.org Subject: Re: Default minfree performance restrictions? 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 Hmm... Since I didn't get a single reply to this one, am I to assume that you all think I'm nuts, and should be publicly flogged with a copy of Greg's book for even thinking such foolish thoughts? :-) Or... Maybe most of the more knowledgeable individuals who follow this list are just gone for the holidays. Seriously, though, folks, does my idea make any sense at all? Thanks, - Ryan On Mon, 20 Dec 1999, Ryan Thompson wrote: > Hello all, > > After creating some larger slices than I'm used to, I finally felt the > full force of a default 8% minfree setting. So, I went to tunefs(8) to > try and put a damper on the multiple gigabytes that aren't being made > available to users. However, I was a bit disappointed to note that > setting minfree at or below 5% (using integer values!) would result in > SPACE optimization. > > So, on my 3.4-STABLE system, I did some hunting around. > > In /usr/src/sys/ufs/ffs/fs.h, I see MINFREE defaults to 8%, and default > time optimization, like tunefs says. Nothing fancy, there. > > In ./ffs_alloc.c, however, I found out how the SPACE/TIME optimization is > determined. In particular, in ffs_realloccg(), I find (from yesterday's > -STABLE), the following snippet: > > /* > * Allocate a new disk location. > */ > if (bpref >= fs->fs_size) > bpref = 0; > switch ((int)fs->fs_optim) { > case FS_OPTSPACE: > /* > * Allocate an exact sized fragment. Although this makes > * best use of space, we will waste time relocating it if > * the file continues to grow. If the fragmentation is > * less than half of the minimum free reserve, we choose > * to begin optimizing for time. > */ > request = nsize; > if (fs->fs_minfree <= 5 || /* !!! */ > fs->fs_cstotal.cs_nffree > > fs->fs_dsize * fs->fs_minfree / (2 * 100)) > break; > log(LOG_NOTICE, "%s: optimization changed from SPACE to TIME\n", > fs->fs_fsmnt); > fs->fs_optim = FS_OPTTIME; > break; > > Questions: > > - Can the line I've marked /* !!! */ have the minimum value of 5 safely > reduced? Eliminated? (safely = if/when a filesystem fills up, could writes > potentially corrupt the fs?) On small partitions with many inodes, perhaps > 5% is appropriate, but in cases like mine, where I have filesystems in > excess of 20GB with < 0.1% fragmentation, > 5% minfree is frankly too much > to give away. > > - Would it make sense to externalize this option into a header file, > kernel config option, or perhaps tunefs itself? I'm guessing the latter > would require modifications to our UFS implementation to allow for the > extra parameter for each filesystem... And would definitely qualify as an > "invasive" change. Food for thought, though :-) > > Any insights? > > I suppose I could just go ahead and try it, but, before I end up doing a > reinstall (cd /usr/src && make blowupworld), I thought it better to ask a > more experienced following of users :-) > > -- > Ryan Thompson > 50% Owner, Technical and Accounts > Phone: +1 (306) 664-1161 > > SaskNow Technologies http://www.sasknow.com > #106-380 3120 8th St E Saskatoon, SK S7H 0W2 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 17:25: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from tdnet.com.br (guepardo.tdnet.com.br [200.236.148.6]) by hub.freebsd.org (Postfix) with ESMTP id F37AB156F0 for ; Wed, 22 Dec 1999 17:25:01 -0800 (PST) (envelope-from grios@ddsecurity.com.br) Received: from ddsecurity.com.br [200.236.148.143] by tdnet.com.br with ESMTP (SMTPD32-5.05) id ABF0960230; Wed, 22 Dec 1999 22:33:36 -0300 Message-ID: <38618700.7FD02524@ddsecurity.com.br> Date: Thu, 23 Dec 1999 00:20:48 -0200 From: Gustavo V G C Rios X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: where you..... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to know, where does the freebsd wizards get information about this nice OS? I have been looking for documentation on such topics without success. so that's the question: Where do you get THE documentation about FreeBSD internals, userlevel, etc.... Thanks in advance. -- The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 17:26: 9 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 37DD8156F2 for ; Wed, 22 Dec 1999 17:26:02 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id RAA17427; Wed, 22 Dec 1999 17:14:20 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 22 Dec 1999 17:14:20 -0800 Date: Wed, 22 Dec 1999 17:14:20 -0800 (PST) From: Kip Macy To: miaobo@mail.zhongxing.com Cc: hackers@freebsd.org Subject: Re:Re: Code In-Reply-To: <48256850.0004D3F2.00@mail.zhongxing.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: miaobo@mail.zhongxing.com,hackers@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Typically it refers to moving a process and all its associated attributes from one machine to another. There are a lot of problems with it, to the best of my knowledge the only OS that ever managed to get it right was Berkeley's Elf which was designed with it in mind from the beginning. Osterhout, the professor heading the group, said afterwords that the costs exceeded the gains. -Kip On Thu, 23 Dec 1999 miaobo@mail.zhongxing.com wrote: > > > > Can you tell me what does "process migration" mean? > > Thanks! > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 17:28:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id 96C4B156F5 for ; Wed, 22 Dec 1999 17:28:57 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org ([216.62.157.60]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FN600LBV6S571@mta4.rcsntx.swbell.net> for hackers@FreeBSD.ORG; Wed, 22 Dec 1999 19:28:54 -0600 (CST) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id TAA68081; Wed, 22 Dec 1999 19:31:25 -0600 (CST envelope-from chris) X-URL: http://www.FreeBSD.org/~chris/ Date: Wed, 22 Dec 1999 19:31:25 -0600 From: Chris Costello Subject: Re: where you..... In-reply-to: <38618700.7FD02524@ddsecurity.com.br> To: Gustavo V G C Rios Cc: hackers@FreeBSD.ORG Reply-To: chris@calldei.com Message-id: <19991222193124.I19766@holly.calldei.com> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i X-Operating-System: FreeBSD 4.0-CURRENT (i386) References: <38618700.7FD02524@ddsecurity.com.br> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 23, 1999, Gustavo V G C Rios wrote: > I have been looking for documentation on such topics without success. > so that's the question: Where do you get THE documentation about FreeBSD > internals, userlevel, etc.... The wizards you speak of are likely kernel programmers, and thus they know already all about the internals. There's a book that's going to be written at some point about FreeBSD internals, I've heard. But that will probably be a long time from now. -- |Chris Costello |Where the system is concerned, you are not allowed to ask "Why?". `----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 17:31:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 0241D15716 for ; Wed, 22 Dec 1999 17:31:27 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id RAA17567; Wed, 22 Dec 1999 17:30:54 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Wed, 22 Dec 1999 17:30:54 -0800 Date: Wed, 22 Dec 1999 17:30:54 -0800 (PST) From: Kip Macy To: miaobo@mail.zhongxing.com Cc: hackers@freebsd.org Subject: Re:Re:Re: Code In-Reply-To: <48256850.00073A82.00@mail.zhongxing.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: miaobo@mail.zhongxing.com,hackers@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Thanks for your immediate response. From your description the concept seems > like distributed-computing related issue, is that true? I am wondering what > is it's exact uses? The main thing that I can think of off hand is load balancing - but there are probably others. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 17:34:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.zhongxing.com (szptt103-147.szptt.net.cn [202.103.147.133]) by hub.freebsd.org (Postfix) with SMTP id 7435A1575B for ; Wed, 22 Dec 1999 17:34:38 -0800 (PST) (envelope-from miaobo@mail.zhongxing.com) Received: by mail.zhongxing.com(Lotus SMTP MTA v1.2 (600.1 3-26-1998)) id 48256850.0007B1B8 ; Thu, 23 Dec 1999 09:24:02 +0800 X-Lotus-FromDomain: ZTE_LTD From: miaobo@mail.zhongxing.com To: Kip Macy Cc: hackers@freebsd.org Message-ID: <48256850.00073A82.00@mail.zhongxing.com> Date: Thu, 23 Dec 1999 09:22:03 +0800 Subject: Re:Re:Re: Code Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your immediate response. From your description the concept seems like distributed-computing related issue, is that true? I am wondering what is it's exact uses? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 17:36:19 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id 334DB15702 for ; Wed, 22 Dec 1999 17:36:17 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id RAA02010; Wed, 22 Dec 1999 17:32:09 -0800 (PST) Message-Id: <199912230132.RAA02010@implode.root.com> To: chris@calldei.com Cc: Gustavo V G C Rios , hackers@FreeBSD.ORG Subject: Re: where you..... In-reply-to: Your message of "Wed, 22 Dec 1999 19:31:25 CST." <19991222193124.I19766@holly.calldei.com> From: David Greenman Reply-To: dg@root.com Date: Wed, 22 Dec 1999 17:32:09 -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Thu, Dec 23, 1999, Gustavo V G C Rios wrote: >> I have been looking for documentation on such topics without success. >> so that's the question: Where do you get THE documentation about FreeBSD >> internals, userlevel, etc.... > > The wizards you speak of are likely kernel programmers, and >thus they know already all about the internals. There's a book >that's going to be written at some point about FreeBSD internals, >I've heard. But that will probably be a long time from now. Kirk McKusick, Sam Lefler, and I are writing a "Design and Implementation" book for FreeBSD, due out in Q1 2001. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 17:38:24 1999 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 EF90714DB8 for ; Wed, 22 Dec 1999 17:38:22 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id RAA21596; Wed, 22 Dec 1999 17:37:47 -0800 (PST) Date: Wed, 22 Dec 1999 17:37:46 -0800 (PST) From: Julian Elischer To: miaobo@mail.zhongxing.com Cc: hackers@freebsd.org Subject: Re:Re: Code In-Reply-To: <48256850.0004D3F2.00@mail.zhongxing.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG to freeze a process in mid-action, and move hte stored process state and memory image to a different machine and restart it exactly where it was frozen. The program should not be able to tell the difference. On Thu, 23 Dec 1999 miaobo@mail.zhongxing.com wrote: > > > > Can you tell me what does "process migration" mean? > > Thanks! > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 18: 9:21 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B080114E97 for ; Wed, 22 Dec 1999 18:09:05 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p14-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.143]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id LAA23407; Thu, 23 Dec 1999 11:08:53 +0900 (JST) Message-ID: <38618388.69D2E5F5@newsguy.com> Date: Thu, 23 Dec 1999 11:06:00 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Gustavo V G C Rios Cc: hackers@FreeBSD.ORG Subject: Re: where you..... References: <38618700.7FD02524@ddsecurity.com.br> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gustavo V G C Rios wrote: > > I would like to know, where does the freebsd wizards get information > about this nice OS? > > I have been looking for documentation on such topics without success. > so that's the question: Where do you get THE documentation about FreeBSD > internals, userlevel, etc.... /usr/src -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 18:21:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.zhongxing.com (szptt103-147.szptt.net.cn [202.103.147.133]) by hub.freebsd.org (Postfix) with SMTP id 5785E1559A for ; Wed, 22 Dec 1999 18:21:01 -0800 (PST) (envelope-from miaobo@mail.zhongxing.com) Received: by mail.zhongxing.com(Lotus SMTP MTA v1.2 (600.1 3-26-1998)) id 48256850.000D00BC ; Thu, 23 Dec 1999 10:22:01 +0800 X-Lotus-FromDomain: ZTE_LTD From: miaobo@mail.zhongxing.com To: hackers@freebsd.org Message-ID: <48256850.000933F2.00@mail.zhongxing.com> Date: Thu, 23 Dec 1999 10:20:04 +0800 Subject: ASYCH/message-based programming style Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi gurus: I am sorry this may be off-topic: I think, compared to the application programming style of Win32, which is asychronize and event/message based, application developing under UNIX is so different. Here under UNIX, I guess the programmers need to take care of all sychronization IPC topics in the code, that is, if a process has 2 TCP socket connection, one pipe, and one SYSV msg id to listen on, the control of program instruction flow will be hard if we don't want access to busy-wait situation, Although we can use select() to solve part of the problem, I think it's not yet enough. And handling asychronize events under UNIX, such as signal delievery and trapping is hard, the logic of the code will be unclear, and we only have one asych timer to use(alarm()/setitimer() share the same timer) and under MT programming we even need to consider sychronization primitives' ASYN signal or cancellation safety. So I wonder if there can be any ASYN mechanism in UNIX application programming in which All incoming I/O and IPC data are represented by events that contains the "pointer" to data itself, which is Win32 style like. This maybe hard that it needs modification on kernel, such as implementation by Solaris2 of POSIX4 aio_read()/aio_write(). Or, just for historical reasons that UNIX just don't have this kind of mechanism? As I think, message-based programs is easier to write and the logic will be clearer. Someone told me that message-based procedures are slower than SYCH ones just like unix does, I don't why they say so if it is true, do you have any comment about this? That is, can anyone introduce the procedures that, from NIC receives a packet to applcation's unix blocked read() returns/win32's application is informed by an event to me? Thanks in Advance! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 18:46:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id 615F315654 for ; Wed, 22 Dec 1999 18:46:12 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id NAA17353; Thu, 23 Dec 1999 13:15:31 +1030 (CST) (envelope-from newton) Date: Thu, 23 Dec 1999 13:15:31 +1030 From: Mark Newton To: Ryan Thompson Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Default minfree performance restrictions? Message-ID: <19991223131531.C17257@internode.com.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 22, 1999 at 07:25:39PM -0600, Ryan Thompson wrote: > Hmm... Since I didn't get a single reply to this one, am I to assume that > you all think I'm nuts, and should be publicly flogged with a copy of > Greg's book for even thinking such foolish thoughts? :-) The idea has merit, but you might need to increase the size of your cylinder groups to compensate if you lower the MINFREE threshhold which invokes space optimization. If UFS cylinder groups are too full the filesystem starts to find it difficult to find free blocks which are "geographically" close to the region of the disk inhabited by a file you're appending to, which reduces perforance. As such, you should build a filesystem with, perhaps, newfs -c32 (or whatever) before lowering the threshhold. > Or... Maybe most of the more knowledgeable individuals who follow this > list are just gone for the holidays. > Seriously, though, folks, does my idea make any sense at all? I'm sure if you send-pr a patch which turns the threshhold into a sysctl variable which defaults to 5 you might end up with some careful consideration being given to the idea... - mark > On Mon, 20 Dec 1999, Ryan Thompson wrote: > > > After creating some larger slices than I'm used to, I finally felt the > > full force of a default 8% minfree setting. So, I went to tunefs(8) to > > try and put a damper on the multiple gigabytes that aren't being made > > available to users. However, I was a bit disappointed to note that > > setting minfree at or below 5% (using integer values!) would result in > > SPACE optimization. > > > > So, on my 3.4-STABLE system, I did some hunting around. > > > > In /usr/src/sys/ufs/ffs/fs.h, I see MINFREE defaults to 8%, and default > > time optimization, like tunefs says. Nothing fancy, there. > > > > In ./ffs_alloc.c, however, I found out how the SPACE/TIME optimization is > > determined. In particular, in ffs_realloccg(), I find (from yesterday's > > -STABLE), the following snippet: > > > > /* > > * Allocate a new disk location. > > */ > > if (bpref >= fs->fs_size) > > bpref = 0; > > switch ((int)fs->fs_optim) { > > case FS_OPTSPACE: > > /* > > * Allocate an exact sized fragment. Although this makes > > * best use of space, we will waste time relocating it if > > * the file continues to grow. If the fragmentation is > > * less than half of the minimum free reserve, we choose > > * to begin optimizing for time. > > */ > > request = nsize; > > if (fs->fs_minfree <= 5 || /* !!! */ > > fs->fs_cstotal.cs_nffree > > > fs->fs_dsize * fs->fs_minfree / (2 * 100)) > > break; > > log(LOG_NOTICE, "%s: optimization changed from SPACE to TIME\n", > > fs->fs_fsmnt); > > fs->fs_optim = FS_OPTTIME; > > break; > > > > Questions: > > > > - Can the line I've marked /* !!! */ have the minimum value of 5 safely > > reduced? Eliminated? (safely = if/when a filesystem fills up, could writes > > potentially corrupt the fs?) On small partitions with many inodes, perhaps > > 5% is appropriate, but in cases like mine, where I have filesystems in > > excess of 20GB with < 0.1% fragmentation, > 5% minfree is frankly too much > > to give away. > > > > - Would it make sense to externalize this option into a header file, > > kernel config option, or perhaps tunefs itself? I'm guessing the latter > > would require modifications to our UFS implementation to allow for the > > extra parameter for each filesystem... And would definitely qualify as an > > "invasive" change. Food for thought, though :-) > > > > Any insights? > > > > I suppose I could just go ahead and try it, but, before I end up doing a > > reinstall (cd /usr/src && make blowupworld), I thought it better to ask a > > more experienced following of users :-) > > > > -- > > Ryan Thompson > > 50% Owner, Technical and Accounts > > Phone: +1 (306) 664-1161 > > > > SaskNow Technologies http://www.sasknow.com > > #106-380 3120 8th St E Saskatoon, SK S7H 0W2 > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 18:48:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 632C4156CD for ; Wed, 22 Dec 1999 18:48:46 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id VAA05414 for ; Wed, 22 Dec 1999 21:48:45 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA02829; Wed, 22 Dec 1999 21:48:15 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id VAA28883 for freebsd-hackers@freebsd.org; Wed, 22 Dec 1999 21:48:14 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199912230248.VAA28883@bb01f39.unx.sas.com> Subject: PCMCIA-ATA/USB support for SanDisk/Digital Cameras To: freebsd-hackers@freebsd.org Date: Wed, 22 Dec 1999 21:48:14 -0500 (EST) 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 Hi, I'm thinking about buying a digital camera, but of course it has to be usable from my FreeBSD box (-current). In looking at the Kodak series, they seem to support the PCMCIA-ATA standard. So, instead of communicating directly with the camera, I was thinking about purchasing a reader from SanDisk: http://www.sandisk.com/cons/imagemate-USB.htm referenced from: http://www.kodak.com/US/en/digital/accessories/memory/usbReader.shtml Basically, it appears to be a combination of PCMCIA-ATA support melded together with USB. Does anyone have any experience with this unit? Am I correct that with USB support coming onboard in -current that it would be feasible to get a driver working? Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 18:57:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.zhongxing.com (szptt103-147.szptt.net.cn [202.103.147.133]) by hub.freebsd.org (Postfix) with SMTP id 83F8A15615 for ; Wed, 22 Dec 1999 18:56:26 -0800 (PST) (envelope-from miaobo@mail.zhongxing.com) Received: by mail.zhongxing.com(Lotus SMTP MTA v1.2 (600.1 3-26-1998)) id 48256850.00102D9D ; Thu, 23 Dec 1999 10:56:42 +0800 X-Lotus-FromDomain: ZTE_LTD From: miaobo@mail.zhongxing.com To: Jack Rusher Cc: hackers@freebsd.org Message-ID: <48256850.000F1B98.00@mail.zhongxing.com> Date: Thu, 23 Dec 1999 10:54:42 +0800 Subject: Re: ASYCH/message-based programming style Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for your immediate response: It enlights me of some principles to access event driven programming library. But I can't imagine what the primitives you mentioned would like, can you give a breif list of them? Or, can you indicate what part of X window code that I can learn of how to build up my own event-driven library under UNIX? I wish it would not be too complicated since that Xlib and Xt stuffs are nightmares to me. @_@ Or, as I mentioned, I think knowing the procedure of: from NIC receives a network packet to application's blocked read() returns, will be helpful to me. Can you give a basic introduction on this or just refer what parts of kernel code that I should look at? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 19:32:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.zhongxing.com (szptt103-147.szptt.net.cn [202.103.147.133]) by hub.freebsd.org (Postfix) with SMTP id CB6FE15784 for ; Wed, 22 Dec 1999 19:31:43 -0800 (PST) (envelope-from miaobo@mail.zhongxing.com) Received: by mail.zhongxing.com(Lotus SMTP MTA v1.2 (600.1 3-26-1998)) id 48256850.001374A5 ; Thu, 23 Dec 1999 11:32:30 +0800 X-Lotus-FromDomain: ZTE_LTD From: miaobo@mail.zhongxing.com To: Mark Newton Cc: hackers@freebsd.org Message-ID: <48256850.00113AC7.00@mail.zhongxing.com> Date: Thu, 23 Dec 1999 11:30:29 +0800 Subject: ╢П╦╢:Re: ASYCH/message-based programming style Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hehe, I forgot this is BSD list that all IPC topics can be done with the control of various file descriptors that can be manipulated by select(). No need of SYSV ipc method maybe. :-) But for signal handling, it's somehow different, e.g. I have 10 processes that need 10 indidual ASYCH timers, can I set 10 different signal handler using signal() and call alarm(), then be correct each time when a timer expires, a SIGALRM will be delieved to the correct process that further traped it? Or, how can I deal with this kind of thing? OTOH, signal may interrupts the sleep of syscalls in kernel and jump to signal handler, we must check this situation with EINTR in our program, or sometimes use sigsetjmp()/siglongjmp(), this makes the program's logic unclear, I think. I am sorry I don't care the graphic or I/O, I just want to know if I want to implement event based programming on UNIX, what should I do? So comes my question about the procedures from NIC receive a data packet to app's blocked read() returns.I guess knowing may be helpful. Can you refer the possible useful resources to me? Thanks. regards! On Thu, Dec 23, 1999 at 10:20:04AM +0800, miaobo@mail.zhongxing.com wrote: > I think, compared to the application programming style of Win32, which is > asychronize and event/message based, application developing under UNIX is > so different. Yup, that's why we like it :-) > Here under UNIX, I guess the programmers need to take care of > all sychronization IPC topics in the code, that is, if a process has 2 TCP > socket connection, one pipe, and one SYSV msg id to listen on, the control > of program instruction flow will be hard if we don't want access to > busy-wait situation, Although we can use select() to solve part of the > problem, Sorry? select() solves *all* of the problem: Notification of asynchronous data delivery, timeouts, multiplexed IO; What problem can't you solve easily and cleanly with a select()-driven state machine? (bearing in mind that Win32 programs are essentially event-driven state machines). > I think it's not yet enough. And handling asychronize events under > UNIX, such as signal delievery and trapping is hard, What's hard about signal(2)? > the logic of the code > will be unclear, and we only have one asych timer to > use(alarm()/setitimer() share the same timer) and under MT programming we > even need to consider sychronization primitives' ASYN signal or > cancellation safety. So I wonder if there can be any ASYN mechanism in UNIX > application programming in which All incoming I/O and IPC data are > represented by events that contains the "pointer" to data itself, which is > Win32 style like. This maybe hard that it needs modification on kernel, > such as implementation by Solaris2 of POSIX4 aio_read()/aio_write(). FWIW, FreeBSD implements aio_read() and aio_write() too, as does Linux, IRIX and essentially every other UNIX variant. That does what you appear to want, so I'm still wondering what you find deficient about the UNIX approach. > Or, just for historical reasons that UNIX just don't have this kind of > mechanism? It does, and has had for some time. Scatter-gather I/O via readv() and writev(), and asynchronous I/O via aio_read() and aio_write() have been with us for a very long time now. > As I think, message-based programs is easier to write and the > logic will be clearer. Win32 forces you to think about messages, which are abstractions invented by the API. UNIX programs tend to be data-driven, which forces you to think about the actual data you're trying to manipulate, instead of some artificial construct designed by the writers of the OS. I leave it to you to work out which approach makes more sense. > Someone told me that message-based procedures are slower than SYCH ones > just like unix does, I don't why they say so if it is true, do you have any > comment about this? That is, can anyone introduce the procedures that, from > NIC receives a packet to applcation's unix blocked read() returns/win32's > application is informed by an event to me? You're trying to shoe-horn events into an OS which doesn't follow an event-driven paradigm; no wonder you're having trouble. Events are bogus; The computer doesn't think in terms of events, so why should the OS pretend it does? Think about your data, the operations you want to perform on it, and the order in which you want to perform them; I/O driven state machines are a good fit. - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 20: 8:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 702AE14DB4 for ; Wed, 22 Dec 1999 20:08:48 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA10640; Wed, 22 Dec 1999 20:08:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kip Macy Cc: miaobo@mail.zhongxing.com, hackers@FreeBSD.ORG Subject: Re: Code In-reply-to: Your message of "Wed, 22 Dec 1999 17:14:20 PST." Date: Wed, 22 Dec 1999 20:08:26 -0800 Message-ID: <10636.945922106@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Typically it refers to moving a process and all its associated attributes > from one machine to another. There are a lot of problems with it, to > the best of my knowledge the only OS that ever managed to get it right was > Berkeley's Elf which was designed with it in mind from the beginning. > Osterhout, the professor heading the group, said afterwords that the costs > exceeded the gains. True enough, but that said, I also think that a lot has been lost in Unix by not having implemented processes as proper "first class objects". Instead, we have the pretense of centralized process information in the proc structure and the reality of lots and lots of process-specific information (outstanding resource requests, timers, etc) scattered all over the place. That means that to get your hands on all the truly useful information about a process and the resources it's using, you have to invent the often evil /proc abstraction or live with grubbing in /dev/kmem. Taking a more direct implementation approach in our process model is, I feel, what also led to the current model of the open file descriptor table, a primitive mechanism which isn't even close to being abstract enough to allow one to do the really neat stuff, like break or insert things into existing pipe streams, redirect the source or sink in a stream after it's been established, etc. Such abilities would seem to be an only natural extention to Unix's traditional "give an engineer a flexible set of tools" philosophy, and maybe if people had thought a bit more about process migration back when BSD was getting its start, we'd at least have some of the nifty abstractions and mechanisms which lead up to the ability to migrate processes if not the actual ability. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 20:44:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from srv4-bsb.bsb.nutecnet.com.br (argonio.bsb.nutecnet.com.br [200.252.253.4]) by hub.freebsd.org (Postfix) with ESMTP id 5C14315633; Wed, 22 Dec 1999 20:44:11 -0800 (PST) (envelope-from visi0n@aux-tech.org) Received: from ebola.chinatown.org (dl7089-bsb.bsb.nutecnet.com.br [200.252.208.89]) by srv4-bsb.bsb.nutecnet.com.br (8.8.5/SCA-6.6) with ESMTP id DAA24073; Thu, 23 Dec 1999 03:50:04 -0200 (BRV) Date: Thu, 23 Dec 1999 02:41:56 -0200 (EDT) From: visi0n X-Sender: visi0n@ebola.chinatown.org To: "Ronald F. Guilmette" Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: sk_buff vs mbuf In-Reply-To: <62986.945886346@monkeys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Dec 1999, Ronald F. Guilmette wrote: > > In message , you wr > ote: > > > > > Is there someone closer to a linux box, tell me if sk_buff is more > >fast than mbuf. I was reading these codes but I can't figure out the final > >result. > > I have a Linux system here, but I don't understand you question. > The question is what is more fast the sk_buff method or mbuf method ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 21:28:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oberon.dnai.com (oberon.dnai.com [207.181.194.97]) by hub.freebsd.org (Postfix) with ESMTP id E0FC314CEE for ; Wed, 22 Dec 1999 21:28:56 -0800 (PST) (envelope-from kudzu@dnai.com) Received: from dnai.com (dnai-216-15-121-72.cust.dnai.com [216.15.121.72]) by oberon.dnai.com (8.9.3/8.9.3) with ESMTP id VAA09213; Wed, 22 Dec 1999 21:28:56 -0800 (PST) Message-ID: <3861B2D9.B70BA17C@dnai.com> Date: Wed, 22 Dec 1999 21:27:53 -0800 From: Michael Sierchio X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org Subject: mlockall() not implemented? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I notice that there are oblique refs to this in , but the man page on mlock() is conspicuously missing a reference to mlockall(), and attempting to compile yields an undefined symbol. Is this not implemented? I thought FBSD was closer to POSIX compliance than Linux... ;-) Thanks in advance, Michael -- QUI ME AMET, CANEM MEUM ETIAM AMET To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 21:53: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sasknow.com (h139-142-245-96.ss.fiberone.net [139.142.245.96]) by hub.freebsd.org (Postfix) with ESMTP id 42E1B14EE3 for ; Wed, 22 Dec 1999 21:52:59 -0800 (PST) (envelope-from freebsd@sasknow.com) Received: from localhost (freebsd@localhost) by sasknow.com (8.9.3/8.9.3) with ESMTP id XAA51138; Wed, 22 Dec 1999 23:53:23 -0600 (CST) (envelope-from freebsd@sasknow.com) Date: Wed, 22 Dec 1999 23:53:23 -0600 (CST) From: Ryan Thompson To: Mark Newton Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Default minfree performance restrictions? In-Reply-To: <19991223131531.C17257@internode.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Mark, Thanks for the reply. On Thu, 23 Dec 1999, Mark Newton wrote: > On Wed, Dec 22, 1999 at 07:25:39PM -0600, Ryan Thompson wrote: > > The idea has merit, but you might need to increase the size of your > cylinder groups to compensate if you lower the MINFREE threshhold which > invokes space optimization. If UFS cylinder groups are too full the > filesystem starts to find it difficult to find free blocks which are > "geographically" close to the region of the disk inhabited by a file > you're appending to, which reduces perforance. As such, you should > build a filesystem with, perhaps, newfs -c32 (or whatever) before > lowering the threshhold. Yup yup... I just tried -c 48 (see below). I took the plunge. Having to do a newfs ANYWAY, as I allocated a 13GB slice solely to my purpose, here, I set it up with 16K blocks, 48 c/g and 2048K frags. (The latter was required to go with 16K blocks). On a sidenote, I tried to specify a minfree of 6% in newfs (before turning the minimum down in the kernel source): Warning: changing optimization to space because minfree is less than 8% Nice, but somewhat annoying :-) I just gave it 8% at that point and used tunefs to set it down to 3% after newfs completed. Before mounting my 13GB guinea-pig, I reduced the minimum threshold from 5% to 1% in ffs_alloc.c (so, lowest minfree setting is 2%, without opt being changed to space..).. Funny, though, as I took more time to read over the code, it looks like that value is actually only enforced if the optimization is ALREADY set to space, presumably because the fragmentation is too high, or as a result of having newfs set it to space FOR you, then not bother to change it to time. Anyways, I rebuilt my kernel with the changed values and rebooted/mounted new partition. I'm in the process of running some tests (for starters: just copying/moving/deleting (in parallel :-) a few gigs' worth of small files at a time... I think I'll try symlinking /usr/src and /usr/obj to the new partition and try a buildworld while this is going on) All the while, keeping an eye on my frag level, and the odd dumpfs...) So far everything appears to be working quickly and efficiently. Despite what I've thrown at it so far, the frag level continues to be very low (0.1% at 25% capacity. All of this is FAR more punishment than most of my filesystems normally take. I know... This is all pretty subjective right now. Once this new fs gets past the preliminary stages, though, I'll try for some more quantitative results :-) As was expected, I DID recover nearly a gig of space :-) > > Or... Maybe most of the more knowledgeable individuals who follow this > > list are just gone for the holidays. > > Seriously, though, folks, does my idea make any sense at all? > > I'm sure if you send-pr a patch which turns the threshhold into a > sysctl variable which defaults to 5 you might end up with some careful > consideration being given to the idea... Hmmm... I might just do that once I get some more quantitative results on at least one system. Once I'm sold on the idea, it'll be easier to get motivated enough to do the patch. I'd hate to do it, submit it, then realize what a waste of time it was :-) -- Ryan Thompson 50% Owner, Technical and Accounts Phone: +1 (306) 664-1161 SaskNow Technologies http://www.sasknow.com #106-380 3120 8th St E Saskatoon, SK S7H 0W2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Dec 22 22:20:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id E6E7D1513F for ; Wed, 22 Dec 1999 22:20:41 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id AAA01893; Thu, 23 Dec 1999 00:20:39 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id AAA25509; Thu, 23 Dec 1999 00:20:38 -0600 (CST) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id AAA06610; Thu, 23 Dec 1999 00:20:37 -0600 (CST) Date: Thu, 23 Dec 1999 00:20:37 -0600 (CST) From: Jonathan Lemon Message-Id: <199912230620.AAA06610@free.pcs> To: visi0n@aux-tech.org, hackers@freebsd.org Subject: Re: sk_buff vs mbuf X-Newsgroups: local.mail.freebsd-hackers In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: > > >On Wed, 22 Dec 1999, Ronald F. Guilmette wrote: > >> >> In message >, you wr >> ote: >> >> > >> > Is there someone closer to a linux box, tell me if sk_buff is more >> >fast than mbuf. I was reading these codes but I can't figure out the final >> >result. >> >> I have a Linux system here, but I don't understand you question. >> > The question is what is more fast the sk_buff method or mbuf >method ? Fast. Flexible. Efficient. Memory-conserving. What metric do you want? Your question doesn't make sense; what do you mean by "more fast"? Under which conditions? Under what kind of load? Linux' sk_buff implementation requires that the entire packet fit within a single buffer. As such, they don't have to deal with m_pullup or mbuf clusters, since there is only _one_ buffer, and no such thing as buffer chains. This also means that buffers either must be maximally sized in all cases, or the entire buffer contents copied upon buffer overflow. They place incoming buffers directly on the receive queue, with no coalescing being done. (no equivalent to sbappend). On one hand, this is quick. On the other hand, it makes for very messy code, and wastes a lot of space for small packets. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 2: 3:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id E823114BEE; Thu, 23 Dec 1999 02:03:33 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id BAA44797; Thu, 23 Dec 1999 01:43:01 GMT (envelope-from nik) Date: Thu, 23 Dec 1999 01:43:01 +0000 From: Nik Clayton To: Jeroen Ruigrok/Asmodai Cc: Nik Clayton , hackers@freebsd.org Subject: Re: wchar support? Message-ID: <19991223014301.A44609@catkin.nothing-going-on.org> References: <19991221161131.A72885@catkin.nothing-going-on.org> <19991221203021.D50448@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991221203021.D50448@daemon.ninth-circle.org>; from Jeroen Ruigrok/Asmodai on Tue, Dec 21, 1999 at 08:30:21PM +0100 Organization: FreeBSD Project Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 21, 1999 at 08:30:21PM +0100, Jeroen Ruigrok/Asmodai wrote: > -On [19991221 18:25], Nik Clayton (nik@freebsd.org) wrote: > >I'm trying to compile OpenJade 1.3, a C++ application, for the Doc. Proj. > >The build fails with > > Bah, you beat me to it ;) If this is going to be a 'fixed in -current' problem, please take the lead. I've only got the resources to run a -stable machine at the moment. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 2:41:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from midget.dons.net.au (daniel.lnk.telstra.net [139.130.137.70]) by hub.freebsd.org (Postfix) with ESMTP id D99EC14DAF for ; Thu, 23 Dec 1999 02:41:40 -0800 (PST) (envelope-from darius@dons.net.au) Received: from guppy.dons.net.au (guppy.dons.net.au [203.31.81.9]) by midget.dons.net.au (8.9.3/8.9.1) with ESMTP id VAA43577; Thu, 23 Dec 1999 21:11:34 +1030 (CST) (envelope-from darius@dons.net.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912230248.VAA28883@bb01f39.unx.sas.com> Date: Thu, 23 Dec 1999 21:11:33 +1030 (CST) From: "Daniel J. O'Connor" To: "John W. DeBoskey" Subject: RE: PCMCIA-ATA/USB support for SanDisk/Digital Cameras Cc: freebsd-hackers@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Dec-99 John W. DeBoskey wrote: > Basically, it appears to be a combination of PCMCIA-ATA > support melded together with USB. I have a Kodak DC-240.. There is a program floating around called ophoto which talks to it over USB, and there is another (more featured) which talks to it via serial called gphoto.. You can get an adapter (infact I have one :) which turns a compact flash card into a PCMCIA card.. It appears as an ATA HD. I *think* its possible for FreeBSD to talk to it, but I haven't tried. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 3: 0:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id EDBAB15732 for ; Thu, 23 Dec 1999 03:00:27 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA87753; Thu, 23 Dec 1999 11:11:51 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 23 Dec 1999 11:11:51 +0000 (GMT) From: Doug Rabson To: Theo van Klaveren Cc: freebsd-hackers@freebsd.org Subject: Re: Question about GLIDE... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Dec 1999, Theo van Klaveren wrote: > Hello, > > I am in the process of porting the GLIDE library to FreeBSD/i386 > which is making good progress so far. My worst enemy has been the > build system itself and the huge amount if `#ifdef __linux__' in > the code. > > I am doing this in the light of the Quake source code > release, which I'd like to play natively with 3dFX hardware... :) > (for the interested: I have already gotten the server and X11 > client to build, but I haven't tested them yet.) > > My question is about this particular piece of code in > swlibs/fxpci/pcilib/fxlinux.c, around line 70: > > if (iopl(3)<0) { > pciErrorCode = PCI_ERR_NO_IO_PERM; > return FXFALSE; > } > > Does anyone know what 'iopl(3)' is supposed to do, > and what it's equivalent on FreeBSD is (if at > all available)? > > The code this is in is about opening the /dev/3dfx device > (which is not available for FreeBSD so it'll fail anyway), > so I _could_ just remove it, but I'm not so certain... > > Also, IANAL, so could anyone tell me if the 3DFX license > permits me to publish my patches under a BSD-style license? I already ported the voodoo2 sources for Glide 2.x and Glide 3.x. You can find patches at: http://www.freebsd.org/~dfr/Glide-V2-2.53.diff http://www.freebsd.org/~dfr/Glide-V2-3.01.diff -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 3:15:57 1999 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 2392F155D5 for ; Thu, 23 Dec 1999 03:15:54 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id DAA32293; Thu, 23 Dec 1999 03:15:44 -0800 (PST) Date: Thu, 23 Dec 1999 03:15:42 -0800 (PST) From: Julian Elischer To: Doug Rabson Cc: Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... 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 Theo, Though doug didn't say so, I think the equivalent code in freeBSD is if ((fd = open("/dev/io",O_RDWR,0)) == -1) { ERROR... } you are asking for permission to do direct IO to IO ports from userland. man 4 io julian On Thu, 23 Dec 1999, Doug Rabson wrote: > On Wed, 22 Dec 1999, Theo van Klaveren wrote: > > > Hello, > > > > I am in the process of porting the GLIDE library to FreeBSD/i386 > > which is making good progress so far. My worst enemy has been the > > build system itself and the huge amount if `#ifdef __linux__' in > > the code. > > > > I am doing this in the light of the Quake source code > > release, which I'd like to play natively with 3dFX hardware... :) > > (for the interested: I have already gotten the server and X11 > > client to build, but I haven't tested them yet.) > > > > My question is about this particular piece of code in > > swlibs/fxpci/pcilib/fxlinux.c, around line 70: > > > > if (iopl(3)<0) { > > pciErrorCode = PCI_ERR_NO_IO_PERM; > > return FXFALSE; > > } > > > > Does anyone know what 'iopl(3)' is supposed to do, > > and what it's equivalent on FreeBSD is (if at > > all available)? > > > > The code this is in is about opening the /dev/3dfx device > > (which is not available for FreeBSD so it'll fail anyway), > > so I _could_ just remove it, but I'm not so certain... > > > > Also, IANAL, so could anyone tell me if the 3DFX license > > permits me to publish my patches under a BSD-style license? > > I already ported the voodoo2 sources for Glide 2.x and Glide 3.x. You can > find patches at: > > http://www.freebsd.org/~dfr/Glide-V2-2.53.diff > http://www.freebsd.org/~dfr/Glide-V2-3.01.diff > > -- > Doug Rabson Mail: dfr@nlsystems.com > Nonlinear Systems Ltd. Phone: +44 181 442 9037 > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 3:23: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id CB7DA155D5 for ; Thu, 23 Dec 1999 03:22:59 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id LAA87985; Thu, 23 Dec 1999 11:34:20 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 23 Dec 1999 11:34:20 +0000 (GMT) From: Doug Rabson To: Julian Elischer Cc: Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Julian Elischer wrote: > Theo, > > Though doug didn't say so, I think the equivalent code in freeBSD is > > if ((fd = open("/dev/io",O_RDWR,0)) == -1) { > ERROR... > } > > you are asking for permission to do direct IO to IO ports from userland. > > man 4 io Thats right. Another gotcha with the Glide code is that it uses the Linux convention for outx(), i.e. outb(val, port) where we use outb(port, val). That had me going for an hour or two.. Seriously, look at my diffs. I ran all the tests and they produced the same results as for Linux. I was planning to work with the folks at glide.sourceforge.net next year to get the FreeBSD bits integrated with their source base. In the mean time, I'm looking for someone to generate a port or two for glide.. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 4: 7:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id 56D8415640 for ; Thu, 23 Dec 1999 04:07:24 -0800 (PST) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id WAA10096 for freebsd-hackers@freebsd.org; Thu, 23 Dec 1999 22:06:43 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199912231206.WAA10096@mail.theinternet.com.au> Subject: Re: Question about GLIDE...u In-Reply-To: from Doug Rabson at "Dec 23, 1999 11:11:51 am" To: freebsd-hackers@freebsd.org Date: Thu, 23 Dec 1999 22:06:43 +1000 (EST) 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 +----[ Doug Rabson ]--------------------------------------------- | On Wed, 22 Dec 1999, Theo van Klaveren wrote: | | I already ported the voodoo2 sources for Glide 2.x and Glide 3.x. You can | find patches at: | | http://www.freebsd.org/~dfr/Glide-V2-2.53.diff | http://www.freebsd.org/~dfr/Glide-V2-3.01.diff I have an old Voodo Graphics card, I've seen people talking about V2 and V3, is that because the Voodoo 1 is not going to work, or because noone else has crappy hardware like me? d8) If it's not going to work, I guess I can bite the bullet and get a V3. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 4:26:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id 50BA2155DE for ; Thu, 23 Dec 1999 04:26:16 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id D52681BB; Thu, 23 Dec 1999 13:26:17 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id CC21D1BA; Thu, 23 Dec 1999 13:26:17 +0100 (CET) Date: Thu, 23 Dec 1999 13:26:17 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: Doug Rabson Cc: Theo van Klaveren , freebsd-hackers@freebsd.org Subject: Re: Question about GLIDE... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Doug Rabson wrote: > I already ported the voodoo2 sources for Glide 2.x and Glide 3.x. You can > find patches at: > > http://www.freebsd.org/~dfr/Glide-V2-2.53.diff > http://www.freebsd.org/~dfr/Glide-V2-3.01.diff > Actually, I was talking about the Voodoo Graphics sources. Sorry for not mentioning that. Theo van Klaveren http://phoenix.student.utwente.nl / ICQ #1353681 - Why, oh why didn't I take the _blue_ pill? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 4:27: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id 2B48F155F2 for ; Thu, 23 Dec 1999 04:27:00 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 1DBBA1BE; Thu, 23 Dec 1999 13:27:02 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 1A09F1BB; Thu, 23 Dec 1999 13:27:02 +0100 (CET) Date: Thu, 23 Dec 1999 13:27:02 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: Julian Elischer Cc: Doug Rabson , Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Julian Elischer wrote: > Theo, > > Though doug didn't say so, I think the equivalent code in freeBSD is > Theo, > > if ((fd = open("/dev/io",O_RDWR,0)) == -1) { > ERROR... > } > > you are asking for permission to do direct IO to IO ports from userland. > Right, thanks! I'll try immiately. Theo van Klaveren http://phoenix.student.utwente.nl / ICQ #1353681 - Why, oh why didn't I take the _blue_ pill? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 4:32:20 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id 33C3B1555C for ; Thu, 23 Dec 1999 04:32:18 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 2B9BF1B0; Thu, 23 Dec 1999 13:32:20 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 22D7C18F; Thu, 23 Dec 1999 13:32:20 +0100 (CET) Date: Thu, 23 Dec 1999 13:32:20 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: Doug Rabson Cc: Julian Elischer , Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Doug Rabson wrote: > On Thu, 23 Dec 1999, Julian Elischer wrote: > > Thats right. Another gotcha with the Glide code is that it uses the Linux > convention for outx(), i.e. outb(val, port) where we use outb(port, val). > That had me going for an hour or two.. Ah-ha, thanks for mentioning that! What had me going for an hour or so was not noticing that they didn't supply the '-c' to install, which caused the header files to be moved OUT of the source tree on the first build pass :) > > Seriously, look at my diffs. I ran all the tests and they produced the > same results as for Linux. I was planning to work with the folks at > glide.sourceforge.net next year to get the FreeBSD bits integrated with > their source base. That'd be a Good Thing. Seriously though, the patchwork I'm creating here is NOT meant to be integrated in the source tree (it's _UGLY_)... I'd be glad to help in any such porting work though. B.t.w. I noticed the assembly files are preprocessed with gasp piped through to as, which generates an empty object file because gasp isn't on my system. It also isn't in the ports. Anyone know where to get it? Theo van Klaveren http://phoenix.student.utwente.nl / ICQ #1353681 - Why, oh why didn't I take the _blue_ pill? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 4:58: 1 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mgw-out.comptel.com (mgw-out.comptel.com [195.237.145.101]) by hub.freebsd.org (Postfix) with ESMTP id 91C6315532 for ; Thu, 23 Dec 1999 04:57:55 -0800 (PST) (envelope-from stefan.parvu@comptel.com) Received: from ctlfw1 ([195.237.145.97]) by mgw-out.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 23 Dec 1999 14:57:54 +0200 Received: from mgw-in.comptel.com ([192.102.20.150]) by ctlfw1.comptel.com; Thu, 23 Dec 1999 14:57:13 +0000 (EET) Received: from xf174 ([195.237.135.174]) by mgw-in.comptel.com with Microsoft SMTPSVC(5.5.1877.197.19); Thu, 23 Dec 1999 14:57:52 +0200 Message-Id: <3.0.6.32.19991223145522.00948b70@miina.comptel.com> X-Sender: sparvu@miina.comptel.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 23 Dec 1999 14:55:22 -0800 To: freebsd-hackers@freebsd.org From: Stefan Parvu Subject: Shrinking the BSD kernel 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 was working a couple of days to have a small as possible kernel in FreeBSD 3.3 Release. Well coud somebody point me to some docs about this subject ? Does anybody know real procedures, steps whatever to keep a small an efficient kernel ? thanks, Stef To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 5:42: 4 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 0D7E414E0C for ; Thu, 23 Dec 1999 05:42:00 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 1218Wn-000Dgq-00 for hackers@FreeBSD.org; Thu, 23 Dec 1999 15:43:37 +0200 From: Sheldon Hearn To: hackers@FreeBSD.org Subject: SIGFPE on arithmetic overflow Date: Thu, 23 Dec 1999 15:43:37 +0200 Message-ID: <52627.945956617@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I'm looking for an explanation of a difference I've found between NetBSD and FreeBSD in the handling of arithmetic overflow in typecasting. The following code, compiled on a stock FreeBSD 4.0-CURRENT machine cores on SIGFPE. On a NetBSD 1.4.1 machine (gcc-2.91.60), the program prints the value of INT_MAX. int main(void) { double x; int i; x = 1e19; i = (int)x; printf("%d\n", i); return 0; } So can anyone explain the cause of this difference to me? :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 6:32:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id B3F0E14F92 for ; Thu, 23 Dec 1999 06:32:47 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id OAA88547; Thu, 23 Dec 1999 14:44:09 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 23 Dec 1999 14:44:09 +0000 (GMT) From: Doug Rabson To: Theo van Klaveren Cc: Julian Elischer , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Theo van Klaveren wrote: > On Thu, 23 Dec 1999, Doug Rabson wrote: > > > On Thu, 23 Dec 1999, Julian Elischer wrote: > > > > Thats right. Another gotcha with the Glide code is that it uses the Linux > > convention for outx(), i.e. outb(val, port) where we use outb(port, val). > > That had me going for an hour or two.. > > Ah-ha, thanks for mentioning that! What had me going for an hour or so > was not noticing that they didn't supply the '-c' to install, which caused > the header files to be moved OUT of the source tree on the first build > pass :) Hehe. I had that too :-) > > > > > Seriously, look at my diffs. I ran all the tests and they produced the > > same results as for Linux. I was planning to work with the folks at > > glide.sourceforge.net next year to get the FreeBSD bits integrated with > > their source base. > > That'd be a Good Thing. Seriously though, the patchwork I'm creating here > is NOT meant to be integrated in the source tree (it's _UGLY_)... I'd be > glad to help in any such porting work though. > > B.t.w. I noticed the assembly files are preprocessed with gasp piped > through to as, which generates an empty object file because gasp isn't > on my system. It also isn't in the ports. Anyone know where to get it? I added it to the -current build a couple of weeks ago when I was working on Glide. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 6:58:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id D8A1314A19 for ; Thu, 23 Dec 1999 06:58:32 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id PAA01338 for freebsd-hackers@FreeBSD.ORG; Thu, 23 Dec 1999 15:58:31 +0100 (CET) (envelope-from olli) Date: Thu, 23 Dec 1999 15:58:31 +0100 (CET) From: Oliver Fromme Message-Id: <199912231458.PAA01338@dorifer.heim3.tu-clausthal.de> To: freebsd-hackers@FreeBSD.ORG Subject: Re: PCMCIA-ATA/USB support for SanDisk/Digital Cameras Organization: Administration TU Clausthal Reply-To: freebsd-hackers@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Daniel J. O'Connor wrote in list.freebsd-hackers: > On 23-Dec-99 John W. DeBoskey wrote: > > Basically, it appears to be a combination of PCMCIA-ATA > > support melded together with USB. > > I have a Kodak DC-240.. > > There is a program floating around called ophoto which talks to it over USB, http://www.fromme.com/ophoto/ (Supports the Kodak DC-240 and DC-280.) > and there is another (more featured) which talks to it via serial called > gphoto.. Yep, but it's terribly slow... Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem StЭck Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 7: 6:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 4C43314C8D for ; Thu, 23 Dec 1999 07:06:45 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id PAA88663; Thu, 23 Dec 1999 15:17:44 GMT (envelope-from dfr@nlsystems.com) Date: Thu, 23 Dec 1999 15:17:43 +0000 (GMT) From: Doug Rabson To: Andrew Kenneth Milton Cc: freebsd-hackers@freebsd.org Subject: Re: Question about GLIDE...u In-Reply-To: <199912231206.WAA10096@mail.theinternet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Andrew Kenneth Milton wrote: > +----[ Doug Rabson ]--------------------------------------------- > | On Wed, 22 Dec 1999, Theo van Klaveren wrote: > | > | I already ported the voodoo2 sources for Glide 2.x and Glide 3.x. You can > | find patches at: > | > | http://www.freebsd.org/~dfr/Glide-V2-2.53.diff > | http://www.freebsd.org/~dfr/Glide-V2-3.01.diff > > I have an old Voodo Graphics card, I've seen people talking about > V2 and V3, is that because the Voodoo 1 is not going to work, or > because noone else has crappy hardware like me? d8) > > If it's not going to work, I guess I can bite the bullet and get a V3. I don't have a v1. I'm sure it would work pretty easily though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 7:32:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id EA67E1564E; Thu, 23 Dec 1999 07:32:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id D8BBD1CD81D; Thu, 23 Dec 1999 07:32:47 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 23 Dec 1999 07:32:47 -0800 (PST) From: Kris Kennaway To: Stefan Parvu Cc: freebsd-hackers@freebsd.org Subject: Re: Shrinking the BSD kernel In-Reply-To: <3.0.6.32.19991223145522.00948b70@miina.comptel.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Stefan Parvu wrote: > Does anybody know real procedures, steps whatever to keep a small an > efficient kernel ? Don't include the stuff you don't need. This belongs on questions-, not hackers- Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 7:36:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id EF35314D7F for ; Thu, 23 Dec 1999 07:36:28 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 344AA18F; Thu, 23 Dec 1999 16:36:28 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 301BB11C; Thu, 23 Dec 1999 16:36:28 +0100 (CET) Date: Thu, 23 Dec 1999 16:36:28 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: Doug Rabson Cc: Andrew Kenneth Milton , freebsd-hackers@freebsd.org Subject: Re: Question about GLIDE...u In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Doug Rabson wrote: > On Thu, 23 Dec 1999, Andrew Kenneth Milton wrote: > > > +----[ Doug Rabson ]--------------------------------------------- > > | On Wed, 22 Dec 1999, Theo van Klaveren wrote: > > | > > | I already ported the voodoo2 sources for Glide 2.x and Glide 3.x. You can > > | find patches at: > > | > > | http://www.freebsd.org/~dfr/Glide-V2-2.53.diff > > | http://www.freebsd.org/~dfr/Glide-V2-3.01.diff > > > > I have an old Voodo Graphics card, I've seen people talking about > > V2 and V3, is that because the Voodoo 1 is not going to work, or > > because noone else has crappy hardware like me? d8) > > > > If it's not going to work, I guess I can bite the bullet and get a V3. > > I don't have a v1. I'm sure it would work pretty easily though. > I have a Voodoo 1 (and a very limited budget, too :), and the I'm porting the source you're talking about. I'll clean it up and release it as a patch as soon as I'm finished. Won't be working on it during the holidays, though. Theo van Klaveren http://phoenix.student.utwente.nl / ICQ #1353681 - Why, oh why didn't I take the _blue_ pill? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 7:39:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id AA24814D7F for ; Thu, 23 Dec 1999 07:39:38 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id B970D11C; Thu, 23 Dec 1999 16:39:40 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id B5089AC; Thu, 23 Dec 1999 16:39:40 +0100 (CET) Date: Thu, 23 Dec 1999 16:39:40 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: Doug Rabson Cc: Theo van Klaveren , Julian Elischer , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Doug Rabson wrote: > I added it to the -current build a couple of weeks ago when I was working > on Glide. > Hadn't seen it :) Thanks! Theo van Klaveren http://phoenix.student.utwente.nl / ICQ #1353681 - Why, oh why didn't I take the _blue_ pill? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 8: 0:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 4849D14BFA; Thu, 23 Dec 1999 08:00:38 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0746E1CD81E; Thu, 23 Dec 1999 08:00:37 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 23 Dec 1999 08:00:37 -0800 (PST) From: Kris Kennaway To: Ptacek Cc: freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: DES routines? In-Reply-To: <001501bf4aa5$45e29640$502124d8@Ptacek> 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, 19 Dec 1999, Ptacek wrote: > I am looking for some routines to perform DES encryption in electronic code > book mode. I assume you have some reason for wanting ECB, and not the usual (more secure) CBC mode.. > I have found the ecb_cyrpt function, however when I try and use it the > buffer is not encrypted. > Am I missing something, do these functions not work, and is there a better > way of doing this? Hmm..I can't find any documentation (manpages) on ecb_crypt, which suggests it's a deprecated interface. You should use the des_ecb_encrypt function and related calls as described in that manpage, as these are the "standard FreeBSD API". Note the different calling syntax. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 8:45:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 1904914E11 for ; Thu, 23 Dec 1999 08:45:20 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id IAA22949; Thu, 23 Dec 1999 08:44:34 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Thu, 23 Dec 1999 08:44:33 -0800 Date: Thu, 23 Dec 1999 08:44:33 -0800 (PST) From: Kip Macy To: "Jordan K. Hubbard" Cc: miaobo@mail.zhongxing.com, hackers@FreeBSD.ORG Subject: Re: Code In-Reply-To: <10636.945922106@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: jkh@zippy.cdrom.com,miaobo@mail.zhongxing.com,hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Taking a more direct implementation approach in our process model is, > I feel, what also led to the current model of the open file descriptor > table, a primitive mechanism which isn't even close to being abstract > enough to allow one to do the really neat stuff, like break or insert > things into existing pipe streams, redirect the source or sink in a > stream after it's been established, etc. Such abilities would seem to > be an only natural extention to Unix's traditional "give an engineer a > flexible set of tools" philosophy, and maybe if people had thought a > bit more about process migration back when BSD was getting its start, > we'd at least have some of the nifty abstractions and mechanisms which > lead up to the ability to migrate processes if not the actual > ability. :-) > > - Jordan Interesting. I had just become so accustomed to thinking that the ad hoc nature of processes as being the only way for things to be. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 9: 5: 3 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from devserv.devel.redhat.com (devserv.devel.redhat.com [207.175.42.156]) by hub.freebsd.org (Postfix) with ESMTP id CF6D01572C for ; Thu, 23 Dec 1999 09:04:56 -0800 (PST) (envelope-from zab@zabbo.net) Received: from localhost (zab@localhost) by devserv.devel.redhat.com (8.8.7/8.8.7) with SMTP id MAA15039; Thu, 23 Dec 1999 12:04:40 -0500 X-Authentication-Warning: devserv.devel.redhat.com: zab owned process doing -bs Date: Thu, 23 Dec 1999 12:04:40 -0500 (EST) From: Zach Brown X-Sender: zab@devserv.devel.redhat.com To: Matthew Jacob Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Preliminary Intel PRO/1000 Gigabit driver for FreeBSD-current 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, 21 Dec 1999, Matthew Jacob wrote: > > Performance is abysmal (~130Mbit). That's next to figure out > > what's up and what I've done stupidly. Feel free to comment.. > > I should note, btw, that this is, in fact, better than I could get the > Linux released Intel driver to do, so far all I know it's just the cards I > have. fwiw, the intel donated linux driver is of dubious quaility. The curious can compare its architecture to the acenic driver that gets wire speed. -- zach - - - - - - 007 373 5963 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 9:15: 9 1999 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 25BFA15410 for ; Thu, 23 Dec 1999 09:15:07 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 23 Dec 1999 17:14:58 +0000 (GMT) Date: Thu, 23 Dec 1999 17:14:55 +0000 From: David Malone To: Sheldon Hearn Cc: hackers@FreeBSD.org Subject: Re: SIGFPE on arithmetic overflow Message-ID: <19991223171455.A27721@gosset.maths.tcd.ie> References: <52627.945956617@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <52627.945956617@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 23, 1999 at 03:43:37PM +0200, Sheldon Hearn wrote: > The following code, compiled on a stock FreeBSD 4.0-CURRENT machine > cores on SIGFPE. On a NetBSD 1.4.1 machine (gcc-2.91.60), the program > prints the value of INT_MAX. Try adding a fpsetmask(fpgetmask()&(~FP_X_OFL)); before the calculation and see what happens. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 9:41:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from guppy.pond.net (guppy.pond.net [205.240.25.2]) by hub.freebsd.org (Postfix) with ESMTP id 6E35214F4E; Thu, 23 Dec 1999 09:41:34 -0800 (PST) (envelope-from ptacek@dashmail.net) Received: from Ptacek (rc1s7p8.dashmail.net [216.36.33.80]) by guppy.pond.net (8.9.3/8.9.3) with SMTP id JAA13600; Thu, 23 Dec 1999 09:33:58 -0800 (PST) Message-ID: <037901bf4d6c$b5db0620$502124d8@Ptacek> From: "Ptacek" To: "Kris Kennaway" Cc: , References: Subject: Re: DES routines? Date: Thu, 23 Dec 1999 09:39:48 -0800 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes. I have to interface to an existing system that is encrypting its data using the ECB format. Thanks for the info, by the way I found the ecb_crypt by doing a man des_crypt. Thanks, Chris ----- Original Message ----- From: Kris Kennaway To: Ptacek Cc: ; Sent: Thursday, December 23, 1999 8:00 AM Subject: Re: DES routines? > On Sun, 19 Dec 1999, Ptacek wrote: > > > I am looking for some routines to perform DES encryption in electronic code > > book mode. > > I assume you have some reason for wanting ECB, and not the usual (more > secure) CBC mode.. > > > I have found the ecb_cyrpt function, however when I try and use it the > > buffer is not encrypted. > > Am I missing something, do these functions not work, and is there a better > > way of doing this? > > Hmm..I can't find any documentation (manpages) on ecb_crypt, which > suggests it's a deprecated interface. You should use the des_ecb_encrypt > function and related calls as described in that manpage, as these are the > "standard FreeBSD API". Note the different calling syntax. > > Kris > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 10: 0:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B6F3515693 for ; Thu, 23 Dec 1999 10:00:27 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA24307; Thu, 23 Dec 1999 10:02:27 -0800 Date: Thu, 23 Dec 1999 10:02:27 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Zach Brown Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Preliminary Intel PRO/1000 Gigabit driver for FreeBSD-current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > I should note, btw, that this is, in fact, better than I could get the > > Linux released Intel driver to do, so far all I know it's just the cards I > > have. > > fwiw, the intel donated linux driver is of dubious quaility. The curious > can compare its architecture to the acenic driver that gets wire speed. The linux driver is clearly a reduced feature port of an NT driver. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 10:22:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 48C0515674 for ; Thu, 23 Dec 1999 10:22:43 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 56118137FC5 for ; Thu, 23 Dec 1999 13:22:42 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id NAA95406; Thu, 23 Dec 1999 13:22:42 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14434.26737.725275.154689@trooper.velocet.net> Date: Thu, 23 Dec 1999 13:22:41 -0500 (EST) To: freebsd-hackers@freebsd.org Subject: deX OErrs on crossed link. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been trying a number of different ethernet configurations out... and at first I was willing to accept that the cable may have been at fault. However, Now that I have had the chance for further experimentation, it appears that it may not. I am using the 4-port DLink adapter (uses tulip chips) on the server and currently intel fxp0 chips on the clients. With this setup, I get a huge number of OErrs on the deX interface (nothing shows on the fxp0 on the other end). If I use an fxp in the server, no errors... and I have tried a variety of handmade and professionally-made cables to join them. I have even tried shutting down full-duplex... doesn't help. Any ideas? Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 10:33:40 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id DB1CD14D6A for ; Thu, 23 Dec 1999 10:33:37 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id NAA03865; Thu, 23 Dec 1999 13:33:32 -0500 (EST) Date: Thu, 23 Dec 1999 13:33:32 -0500 (EST) From: Daniel Eischen Message-Id: <199912231833.NAA03865@pcnet1.pcnet.com> To: dgilbert@velocet.ca, freebsd-hackers@FreeBSD.ORG Subject: Re: deX OErrs on crossed link. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Gilbert wrote: > I've been trying a number of different ethernet configurations > out... and at first I was willing to accept that the cable may have > been at fault. However, Now that I have had the chance for further > experimentation, it appears that it may not. > > I am using the 4-port DLink adapter (uses tulip chips) on the server > and currently intel fxp0 chips on the clients. With this setup, I get > a huge number of OErrs on the deX interface (nothing shows on the fxp0 > on the other end). If I use an fxp in the server, no errors... and I > have tried a variety of handmade and professionally-made cables to > join them. > > I have even tried shutting down full-duplex... doesn't help. Someone else, just yesterday, posted the a similar problem on the -stable list. He was using a 4-port ZNYX card (de driver also). With the de driver in -stable, he got a huge number of output errors, but no errors on input. Using the ZNYX supplied driver for FreeBSD instead of de, the problem didn't exist. FWIW, I'm using a 4-port ZNYX card with the stock de driver on 3.3-stable without any problems - 10BaseT and 100BaseT, both at half-duplex. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 10:34:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id D782D15736 for ; Thu, 23 Dec 1999 10:34:06 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.28]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id NAA04279; Thu, 23 Dec 1999 13:34:04 -0500 (EST) Received: from freebsd.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA15878; Thu, 23 Dec 1999 13:33:34 -0500 Received: (from jwd@localhost) by FreeBSD.unx.sas.com (8.9.3/8.9.2) id NAA01666; Thu, 23 Dec 1999 13:41:05 -0500 (EST) (envelope-from jwd) From: "John W. De Boskey" Message-Id: <199912231841.NAA01666@FreeBSD.unx.sas.com> Subject: Re: PCMCIA-ATA/USB support for SanDisk/Digital Cameras In-Reply-To: <199912231458.PAA01338@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Dec 23, 1999 03:58:31 pm" To: freebsd-hackers@FreeBSD.ORG Date: Thu, 23 Dec 1999 13:41:05 -0500 (EST) Cc: olli@dorifer.heim3.tu-clausthal.de 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 Hi, Many thanks for the pointer! I'm going to give this a try. It looks like it will be a great solution... For those interested, I borrowed a friends SanDisk unit and plugged it into a FreeBSD-current box with usb enabled (along with all the debug features). The following is the appropriate dmesg output: uhci0: irq 11 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ugen0: SanDisk USB CFII, rev 1.00/0.05, addr 2 ugen_set_config: ugen0 to configno 1, sc=0xc0d82000 ugen_set_config: ifaceno 0 ugen_set_config: endptno 0, endpt=0x01(1,1), sce=0xc0d820cc ugen_set_config: endptno 1, endpt=0x02(2,1), sce=0xc0d82144 ugen_set_config: endptno 2, endpt=0x03(3,0), sce=0xc0d82180 Other than the above output, I don't seem to be able to talk to the device. /usr/sbin/usbdevs reports: # usbdevs -v usbdevs: no USB controllers found Happy Holidays! John > Daniel J. O'Connor wrote in list.freebsd-hackers: > > On 23-Dec-99 John W. DeBoskey wrote: > > > Basically, it appears to be a combination of PCMCIA-ATA > > > support melded together with USB. > > > > I have a Kodak DC-240.. > > > > There is a program floating around called ophoto which talks to it over USB, > > http://www.fromme.com/ophoto/ > (Supports the Kodak DC-240 and DC-280.) > > > and there is another (more featured) which talks to it via serial called > > gphoto.. > > Yep, but it's terribly slow... > > Regards > Oliver > > -- > Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany > (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) > > "In jedem St_ck Kohle wartet ein Diamant auf seine Geburt" > (Terry Pratchett) > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 10:34:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id 0C88315780; Thu, 23 Dec 1999 10:34:28 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.56]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA5EA3; Thu, 23 Dec 1999 19:34:26 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id TAA65451; Thu, 23 Dec 1999 19:30:59 +0100 (CET) (envelope-from asmodai) Date: Thu, 23 Dec 1999 19:30:59 +0100 From: Jeroen Ruigrok/Asmodai To: Nik Clayton Cc: hackers@freebsd.org Subject: Re: wchar support? Message-ID: <19991223193059.A65444@daemon.ninth-circle.org> References: <19991221161131.A72885@catkin.nothing-going-on.org> <19991221203021.D50448@daemon.ninth-circle.org> <19991223014301.A44609@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991223014301.A44609@catkin.nothing-going-on.org>; from nik@freebsd.org on Thu, Dec 23, 1999 at 01:43:01AM +0000 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [19991223 12:00], Nik Clayton (nik@freebsd.org) wrote: >On Tue, Dec 21, 1999 at 08:30:21PM +0100, Jeroen Ruigrok/Asmodai wrote: >> -On [19991221 18:25], Nik Clayton (nik@freebsd.org) wrote: >> >I'm trying to compile OpenJade 1.3, a C++ application, for the Doc. Proj. >> >The build fails with >> >> Bah, you beat me to it ;) > >If this is going to be a 'fixed in -current' problem, please take the >lead. I've only got the resources to run a -stable machine at the moment. Nah, we need to do this both on CURRENT and STABLE, but you can count on me to test the things on CURRENT. I was merely commenting on the idea that I think you are somehow psychic to know my to-do list. ;) OTOH, David O`Brien was kind enough to let me know that there was a wchar project this year and advised to browse the list archives. -- Jeroen Ruigrok van der Werven/Asmodai asmodai@[wxs.nl|bart.nl] Documentation nutter. *BSD: Technical excellence at its best... The BSD Programmer's Documentation Project So take a look at me now, well there's just an empty space... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 10:50:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id B845915672 for ; Thu, 23 Dec 1999 10:50:01 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id BEB49137FC5; Thu, 23 Dec 1999 13:49:59 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id NAA96099; Thu, 23 Dec 1999 13:49:59 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14434.28375.113250.387137@trooper.velocet.net> Date: Thu, 23 Dec 1999 13:49:59 -0500 (EST) To: Daniel Eischen Cc: dgilbert@velocet.ca, freebsd-hackers@FreeBSD.ORG Subject: Re: deX OErrs on crossed link. In-Reply-To: <199912231833.NAA03865@pcnet1.pcnet.com> References: <199912231833.NAA03865@pcnet1.pcnet.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Daniel" == Daniel Eischen writes: Daniel> Someone else, just yesterday, posted the a similar problem on Daniel> the -stable list. He was using a 4-port ZNYX card (de driver Daniel> also). With the de driver in -stable, he got a huge number of Daniel> output errors, but no errors on input. Using the ZNYX Daniel> supplied driver for FreeBSD instead of de, the problem didn't Daniel> exist. Daniel> FWIW, I'm using a 4-port ZNYX card with the stock de driver on Daniel> 3.3-stable without any problems - 10BaseT and 100BaseT, both Daniel> at half-duplex. Is it possible to try a copy of znyx driver? What changes might they have made. I'm running -current on this particular machine, but I don't think that matters. Another (identical) 4-port card is running fine, but it's half-duplex and talking to hubs in all cases. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 11:10:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 5695D156AE for ; Thu, 23 Dec 1999 11:10:52 -0800 (PST) (envelope-from nick@rapidnet.com) Received: from localhost (nick@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id MAA01827; Thu, 23 Dec 1999 12:10:15 -0700 (MST) Date: Thu, 23 Dec 1999 12:10:15 -0700 (MST) From: Nick Rogness To: David Gilbert Cc: freebsd-hackers@freebsd.org Subject: Re: deX OErrs on crossed link. In-Reply-To: <14434.26737.725275.154689@trooper.velocet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, David Gilbert wrote: > I am using the 4-port DLink adapter (uses tulip chips) on the server > and currently intel fxp0 chips on the clients. With this setup, I get > a huge number of OErrs on the deX interface (nothing shows on the fxp0 > on the other end). If I use an fxp in the server, no errors... and I > have tried a variety of handmade and professionally-made cables to > join them. > > I have even tried shutting down full-duplex... doesn't help. Ah ha! I thought I was the only one having problems with the de driver. Performance just went right down the tubes running 100BaseT at Full-Duplex. However, after days of troubleshooting why I was getting 6Kb a second across a X-over cable between two machines, I ran it down to the Full-duplex operation. Apparently, When half-duplex was enabled, performance was great...at full-duplex...6kb a sec (even ftp stalls). FreeBSD 3.3-RELEASE and 3.3-STABLE...same results on both. Anyone else? ******************************************************** Nick Rogness Speak softly and carry Systems Administrator a Gigabit switch. RapidNet, Inc., USA ******************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 11:26: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 6350A158A1 for ; Thu, 23 Dec 1999 11:25:58 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id OAA11202; Thu, 23 Dec 1999 14:25:50 -0500 (EST) Date: Thu, 23 Dec 1999 14:25:50 -0500 (EST) From: Daniel Eischen To: David Gilbert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: deX OErrs on crossed link. In-Reply-To: <14434.28375.113250.387137@trooper.velocet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, David Gilbert wrote: > >>>>> "Daniel" == Daniel Eischen writes: > > Daniel> Someone else, just yesterday, posted the a similar problem on > Daniel> the -stable list. He was using a 4-port ZNYX card (de driver > Daniel> also). With the de driver in -stable, he got a huge number of > Daniel> output errors, but no errors on input. Using the ZNYX > Daniel> supplied driver for FreeBSD instead of de, the problem didn't > Daniel> exist. > > Daniel> FWIW, I'm using a 4-port ZNYX card with the stock de driver on > Daniel> 3.3-stable without any problems - 10BaseT and 100BaseT, both > Daniel> at half-duplex. > > Is it possible to try a copy of znyx driver? What changes might they > have made. I'm running -current on this particular machine, but I > don't think that matters. Another (identical) 4-port card is running > fine, but it's half-duplex and talking to hubs in all cases. You don't get the source, only the object file. See www.znyx.com for details. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 11:40:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 08FCC15713; Thu, 23 Dec 1999 11:40:27 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA06278; Thu, 23 Dec 1999 19:45:07 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00993; Thu, 23 Dec 1999 19:59:46 +0100 (CET) (envelope-from wilko) Date: Thu, 23 Dec 1999 19:59:46 +0100 From: Wilko Bulte To: Kris Kennaway Cc: Stefan Parvu , freebsd-hackers@FreeBSD.ORG Subject: Re: Shrinking the BSD kernel Message-ID: <19991223195946.B759@yedi.iaf.nl> References: <3.0.6.32.19991223145522.00948b70@miina.comptel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Thu, Dec 23, 1999 at 07:32:47AM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 23, 1999 at 07:32:47AM -0800, Kris Kennaway wrote: > On Thu, 23 Dec 1999, Stefan Parvu wrote: > > > Does anybody know real procedures, steps whatever to keep a small an > > efficient kernel ? > > Don't include the stuff you don't need. This belongs on questions-, not > hackers- Hm. I suggest to search the mailing list archives for picoBSD. This is probably interesting reading in this context. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 12: 3:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id E90AC14D69 for ; Thu, 23 Dec 1999 12:03:38 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 121EU7-000FS8-00; Thu, 23 Dec 1999 22:05:15 +0200 From: Sheldon Hearn To: David Malone Cc: hackers@FreeBSD.org Subject: Re: SIGFPE on arithmetic overflow In-reply-to: Your message of "Thu, 23 Dec 1999 17:14:55 GMT." <19991223171455.A27721@gosset.maths.tcd.ie> Date: Thu, 23 Dec 1999 22:05:15 +0200 Message-ID: <59403.945979515@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999 17:14:55 GMT, David Malone wrote: > Try adding a fpsetmask(fpgetmask()&(~FP_X_OFL)); before the calculation > and see what happens. It still bombs, although fpsetmask(0) does the trick. I'm really interested in hearing what causes the difference in behaviour. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 12: 7:38 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 31E80156DF for ; Thu, 23 Dec 1999 12:07:35 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 121EXz-000FTF-00; Thu, 23 Dec 1999 22:09:15 +0200 From: Sheldon Hearn To: David Malone Cc: hackers@FreeBSD.org Subject: Re: SIGFPE on arithmetic overflow In-reply-to: Your message of "Thu, 23 Dec 1999 22:05:15 +0200." <59403.945979515@axl.noc.iafrica.com> Date: Thu, 23 Dec 1999 22:09:14 +0200 Message-ID: <59472.945979754@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999 22:05:15 +0200, Sheldon Hearn wrote: > It still bombs, although fpsetmask(0) does the trick. I'm really > interested in hearing what causes the difference in behaviour. It seems that the exception is happening on FP_X_INV, which is odd for what seems to be an under/overflow. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 13:46:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from irbs.irbs.com (irbs.irbs.com [209.36.62.129]) by hub.freebsd.org (Postfix) with ESMTP id 8DFA21564B for ; Thu, 23 Dec 1999 13:46:14 -0800 (PST) (envelope-from jc@irbs.com) Received: (from jc@localhost) by irbs.irbs.com (8.8.5/8.8.5) id QAA17889; Thu, 23 Dec 1999 16:45:55 -0500 (EST) Message-ID: <19991223164554.46592@irbs.com> Date: Thu, 23 Dec 1999 16:45:54 -0500 From: John Capo To: Nick Rogness , David Gilbert Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: deX OErrs on crossed link. References: <14434.26737.725275.154689@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: ; from Nick Rogness on Thu, Dec 23, 1999 at 12:10:15PM -0700 X-Organization: IRBS Engineering, (954) 463-3771 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The de driver for stable will not select full-duplex on some (all?) cards with MII transceivers. I posted a patch for the DLINK 570TX quad port card that may work with other 21143/MII cards. I don't have the patch handy at the moment, check the list archives if anyone is interested. John Capo Quoting Nick Rogness (nick@rapidnet.com): > > Ah ha! I thought I was the only one having problems with the de > driver. Performance just went right down the tubes running > 100BaseT at Full-Duplex. However, after days of troubleshooting > why I was getting 6Kb a second across a X-over cable between two > machines, I ran it down to the Full-duplex operation. Apparently, > When half-duplex was enabled, performance was great...at > full-duplex...6kb a sec (even ftp stalls). FreeBSD 3.3-RELEASE > and 3.3-STABLE...same results on both. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 14: 9: 2 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 615A214CFD for ; Thu, 23 Dec 1999 14:08:56 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id RAA04748; Thu, 23 Dec 1999 17:08:45 -0500 (EST) Date: Thu, 23 Dec 1999 17:08:45 -0500 (EST) From: Bosko Milekic To: Sheldon Hearn Cc: hackers@FreeBSD.ORG Subject: Re: SIGFPE on arithmetic overflow In-Reply-To: <59472.945979754@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Sheldon Hearn wrote: !> !> !>On Thu, 23 Dec 1999 22:05:15 +0200, Sheldon Hearn wrote: !> !>> It still bombs, although fpsetmask(0) does the trick. I'm really !>> interested in hearing what causes the difference in behaviour. !> !>It seems that the exception is happening on FP_X_INV, which is odd for !>what seems to be an under/overflow. !> !>Ciao, !>Sheldon. !> Here's a shot in the dark, although somebody else could probably offer a somewhat better explanation. From npx.c: * The 6 maskable bits in order of their preference, as stated in the * above referenced Intel manual: * 1 Invalid operation (FP_X_INV) * 1a Stack underflow * 1b Stack overflow * 1c Operand of unsupported format * 1d SNaN operand. * 2 QNaN operand (not an exception, irrelavant here) * 3 Any other invalid-operation not mentioned above or zero divide * (FP_X_INV, FP_X_DZ) * 4 Denormal operand (FP_X_DNML) * 5 Numeric over/underflow (FP_X_OFL, FP_X_UFL) * 6 Inexact result (FP_X_IMP) My guess would be that what is actually caught here is a stack over/underflow and because FP_X_INV (which covers this possibility) is not unmasked; the trap occurs and the signal is posted. Could somebody try this piece of code on a -STABLE machine, just out of curiosity...? Bosko. ...... . . . . . . . . . . . . . Bosko Milekic -- bmilekic@dsuper.net . . . . . . . . . . . ...... . . WWW: http://pages.infinit.net/bmilekic/ . ................................................ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 14:41:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id CC50614A00 for ; Thu, 23 Dec 1999 14:41:07 -0800 (PST) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id IAA16937; Fri, 24 Dec 1999 08:37:36 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199912232237.IAA16937@mail.theinternet.com.au> Subject: Re: Question about GLIDE...u In-Reply-To: from Theo van Klaveren at "Dec 23, 1999 4:36:28 pm" To: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren) Date: Fri, 24 Dec 1999 08:37:36 +1000 (EST) Cc: dfr@nlsystems.com, akm@mail.theinternet.com.au, freebsd-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 +----[ Theo van Klaveren ]--------------------------------------------- | | I have a Voodoo 1 (and a very limited budget, too :), and the I'm porting | the source you're talking about. I'll clean it up and release it as a | patch as soon as I'm finished. Won't be working on it during the holidays, | though. I'm involved with a project I can test it with. CrystalSpace is a (very) cross-platform 3d engine, so I'll get too see how much improvement it makes with 3d hardware on board.. http://www.sourceforge.net/project/?form_grp=649 or http://crystal.linuxgames.com/ For those of you interested. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 14:46:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monkeys.com (i180.value.net [206.14.136.180]) by hub.freebsd.org (Postfix) with ESMTP id 3BE1A14C28 for ; Thu, 23 Dec 1999 14:46:56 -0800 (PST) (envelope-from rfg@monkeys.com) Received: from monkeys.com (localhost [127.0.0.1]) by monkeys.com (8.9.3/8.9.3) with ESMTP id OAA03248; Thu, 23 Dec 1999 14:46:27 -0800 (PST) To: Sheldon Hearn Cc: David Malone , hackers@FreeBSD.ORG Subject: Re: SIGFPE on arithmetic overflow In-reply-to: Your message of Thu, 23 Dec 1999 22:05:15 +0200. <59403.945979515@axl.noc.iafrica.com> Date: Thu, 23 Dec 1999 14:46:27 -0800 Message-ID: <3246.945989187@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <59403.945979515@axl.noc.iafrica.com>, you wrote: > > >On Thu, 23 Dec 1999 17:14:55 GMT, David Malone wrote: > >> Try adding a fpsetmask(fpgetmask()&(~FP_X_OFL)); before the calculation >> and see what happens. > >It still bombs, although fpsetmask(0) does the trick. I'm really >interested in hearing what causes the difference in behaviour. Sorry, I breezed past the first part of this thread too quickly, so I forgot which OS is doing what. However let me say that I do still have a copy of the IEEE floating point standard around here, and if anybody needs me to, I'll be happy to look stuff up in it, and/or to cite chapter and verse. The bottom line, I think, is that the IEEE FP standard talks about two things of interest here... exceptions and traps. An exception is just some condition that probably only arises infrequently (e.g. overflow, divide by zero, and other such stuff). An exception may or may not cause a trap. A trap is one possible response to an exception, and can be thought of as being essentially the same sort of thing as a (non-blocked) UNIX signal. Anyway, to bring this back to the topic at hand, the relevant quote from IEEE Std 754-1985 (Section 7, paragraph 1) is: ``The default response to an exception shall be to proceed without a trap.'' In other words, for a conforming implementation of IEEE 754, unless you explicitly override the default behavior (e.g. with a call to fpsetmask) exceptions (including FP overflow) SHOULD NOT cause a trap. I should say however that back when I was doing compiler testing for a living... a few eons ago... this was something that a lot of implementa- tions did seem to screw up.... Many compiler/library/OS combinations would invoke main() with one or more of the IEEE FP exceptions set to cause a trap/signal (in violation of IEEE 754). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 15:20:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id 99F8C14FEC for ; Thu, 23 Dec 1999 15:20:32 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 311721BC; Fri, 24 Dec 1999 00:20:31 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 289191B2 for ; Fri, 24 Dec 1999 00:20:31 +0100 (CET) Date: Fri, 24 Dec 1999 00:20:31 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: freebsd-hackers@freebsd.org Subject: GLIDE for FreeBSD 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 Whew. After two late nights of furious hacking, you can now download the modified source for Glide 2.46 (the Voodoo Graphics version) at ftp://phoenix.student.utwente.nl/pub/glide Note: I have completely hacked the source to bits to achieve this. The source has been autoconf'ed (scary, but at least it works, which cannot be said of the build system 3DFX provided). All source files needed for FreeBSD compilation have been included, but Windows-compilation etc. have been dropped. I'd be more than happy to accept patches which'll make it compile on other platforms again, but chances are you'll have to get the neccesary files from the original source file. Also, binaries of GLIDE and Mesa+glide are available for FreeBSD-CURRENT. The GLIDE library has one bug, though: When quitting an application, it won't restore the normal display. If anyone can help me with this, that'd be GREAT! One last question: What are the chances of incorporating the sources for Voodoo2/3 into one source tree? They all have the swlibs/ directory (almost unchanged)... Theo van Klaveren http://phoenix.student.utwente.nl / ICQ #1353681 - Why, oh why didn't I take the _blue_ pill? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 15:46:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from monk.via.net (monk.via.net [209.81.2.10]) by hub.freebsd.org (Postfix) with ESMTP id D9D7714E47 for ; Thu, 23 Dec 1999 15:46:35 -0800 (PST) (envelope-from joe@via.net) Received: (from joe@localhost) by monk.via.net (8.9.3/8.9.3) id PAA41473; Thu, 23 Dec 1999 15:46:41 -0800 (PST) (envelope-from joe) From: Joe McGuckin Message-Id: <199912232346.PAA41473@monk.via.net> Date: Thu, 23 Dec 1999 15:46:41 -0800 (PST) To: freebsd-hackers@FreeBSD.ORG Cc: havoc@Cal30B054.student.utwente.nl Subject: What's the best accellerated graphics card for XF86? X-Mailer: Ishmail 1.3.1-970608-bsdi MIME-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now tha GLIDE for FreeBSD is available, what's the best video card for playing quake, etc? Thanks, Joe -- Joe McGuckin ViaNet Communications 994 San Antonio Road Palo Alto, CA 94303 Phone: 650-969-2203 Cell: 650-207-0372 Fax: 650-969-2124 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 15:53:57 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from p.wl.vg (209-9-69-194.sdsl.cais.net [209.9.69.194]) by hub.freebsd.org (Postfix) with ESMTP id BF7431580A for ; Thu, 23 Dec 1999 15:53:45 -0800 (PST) (envelope-from patrick@p.wl.vg) Received: (from patrick@localhost) by p.wl.vg (8.9.3/8.9.3) id SAA69429; Thu, 23 Dec 1999 18:53:18 -0500 (EST) (envelope-from patrick) Message-Id: <199912232353.SAA69429@p.wl.vg> Date: Thu, 23 Dec 1999 18:53:17 -0500 (EST) From: patrick@whetstonelogic.com Subject: Re: What's the best accellerated graphics card for XF86? To: joe@via.net Cc: freebsd-hackers@FreeBSD.ORG, havoc@Cal30B054.student.utwente.nl In-Reply-To: <199912232346.PAA41473@monk.via.net> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23 Dec, Joe McGuckin wrote: > > Now tha GLIDE for FreeBSD is available, what's the best video card > for playing quake, etc? > > Thanks, > > Joe And, who is going to build us a FreeBSD Quake 1, now that the source is out! Patrick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 15:55:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from bomber.avantgo.com (ws1.avantgo.com [207.214.200.194]) by hub.freebsd.org (Postfix) with ESMTP id 89A311564B for ; Thu, 23 Dec 1999 15:55:50 -0800 (PST) (envelope-from scott@avantgo.com) Received: from river ([10.0.128.30]) by bomber.avantgo.com (Netscape Messaging Server 3.5) with SMTP id 339 for ; Thu, 23 Dec 1999 15:51:25 -0800 Message-ID: <0e7b01bf4da1$1d84d060$1e80000a@avantgo.com> From: "Scott Hess" To: Subject: Status of kernel threads. Date: Thu, 23 Dec 1999 15:54:56 -0800 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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been looking at hardware upgrades for a production MYSQL server. While banging on a hardware RAID solution, I found that the performance improvement for test harnesses hitting MYSQL sucked badly compared to other tests. My hunch is that the blocking nature of disk I/O is interacting with FreeBSD's userland pthreads to effectively serialize disk requests (since disk I/O always blocks, there will never be multiple reads from disk in progress at a time, so no elevator sorting). To verify the hunch, I ran multiple MYSQL daemons against the same database (using filesystem locking to synchronize), and hit each of them with 1/N of the load from the earlier test. Indeed, the N-daemon version ran much faster overall, and showed much greater iostat numbers. Does my evaluation of the problem make sense? [For reference, in the 2-mysqld case, I ran 2 mysqld processes against a single set of tables on different ports, and hit each port with 2 100-unit client loads apiece, and 1-unit loads finished about 25% faster, while iostat tps numbers were about 40% higher. With 4 mysqld processes and 1 100-unit client load apiece, units finished an additional 10% faster and iostat tps went up another 30%. All against a 32M cache SCSI-SCSI RAID5 controller with 6 10krpm drives.] I periodically hear reference to kernel threads - but from what I can tell from following these lists for a couple months, and also searching the archives, kernel threads aren't quite "there" yet ("there"=="can use -kthread instead of -pthread and away we go"). Am I just missing the right search phrases? Assuming the "kernel threads" still means "LinuxThreads" and not something new that I haven't found, does anyone have any positive or negative comments on how reasonable LinuxThreads on FreeBSD is for production use? Is it stable, or still in development? Thanks, scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 15:58:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id 8D41E14E47 for ; Thu, 23 Dec 1999 15:58:35 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 6014512C; Fri, 24 Dec 1999 00:58:34 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 5B5B0AC; Fri, 24 Dec 1999 00:58:34 +0100 (CET) Date: Fri, 24 Dec 1999 00:58:34 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: patrick@whetstonelogic.com Cc: joe@via.net, freebsd-hackers@FreeBSD.ORG, havoc@Cal30B054.student.utwente.nl Subject: Re: What's the best accellerated graphics card for XF86? In-Reply-To: <199912232353.SAA69429@p.wl.vg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999 patrick@whetstonelogic.com wrote: > On 23 Dec, Joe McGuckin wrote: > > > > Now tha GLIDE for FreeBSD is available, what's the best video card > > for playing quake, etc? > > Well, since GLIDE only support 3DFX cards, I'd say your choice is pretty limited :) Besides that, the port I've done only supports the (now ancient) Voodoo Graphics based cards. For Voodoo2/3, look at Doug Rabson's patches to the original source code. > > And, who is going to build us a FreeBSD Quake 1, now that the source is > out! Sorry, I only got as far as the server so far :-) The X11 client built, but there is a bug in Quake's assembly code (methinks) that produces a SIGBUS in memset() ... haven't investigated thourougly(sp?) yet. I'll try and build the GL client, but I haven't got high hopes... If anyone is intersted, I can give you my patches to the QuakeWorld code (it fixes the Linux CDROM code and some other Linux specific thingies). Theo van Klaveren http://phoenix.student.utwente.nl / ICQ #1353681 - Why, oh why didn't I take the _blue_ pill? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 16: 7:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from chronis.pobox.com (chronis.pobox.com [208.210.124.49]) by hub.freebsd.org (Postfix) with ESMTP id 0E84314A04 for ; Thu, 23 Dec 1999 16:07:53 -0800 (PST) (envelope-from scott@chronis.pobox.com) Received: by chronis.pobox.com (Postfix, from userid 1001) id C03F69B1B; Thu, 23 Dec 1999 19:07:51 -0500 (EST) Date: Thu, 23 Dec 1999 19:07:51 -0500 From: scott To: Scott Hess Cc: freebsd-hackers@freebsd.org Subject: Re: Status of kernel threads. Message-ID: <19991223190751.A26191@chronis.pobox.com> References: <0e7b01bf4da1$1d84d060$1e80000a@avantgo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <0e7b01bf4da1$1d84d060$1e80000a@avantgo.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've found http://www.cornfed.com/pk looks weird, but says it will do kernel threads for FreeBSD. It replaces the kernel, though, so I don't know how it works with FreeBSD hardware drivers. I was bit by soddy mysql performance when the number of concurrent clients and queries was high under FreeBSD, and have been looking into solutions myself. scott On Thu, Dec 23, 1999 at 03:54:56PM -0800, Scott Hess wrote: > I've been looking at hardware upgrades for a production MYSQL server. > While banging on a hardware RAID solution, I found that the performance > improvement for test harnesses hitting MYSQL sucked badly compared to other > tests. My hunch is that the blocking nature of disk I/O is interacting > with FreeBSD's userland pthreads to effectively serialize disk requests > (since disk I/O always blocks, there will never be multiple reads from disk > in progress at a time, so no elevator sorting). To verify the hunch, I ran > multiple MYSQL daemons against the same database (using filesystem locking > to synchronize), and hit each of them with 1/N of the load from the earlier > test. Indeed, the N-daemon version ran much faster overall, and showed > much greater iostat numbers. > > Does my evaluation of the problem make sense? [For reference, in the > 2-mysqld case, I ran 2 mysqld processes against a single set of tables on > different ports, and hit each port with 2 100-unit client loads apiece, and > 1-unit loads finished about 25% faster, while iostat tps numbers were about > 40% higher. With 4 mysqld processes and 1 100-unit client load apiece, > units finished an additional 10% faster and iostat tps went up another 30%. > All against a 32M cache SCSI-SCSI RAID5 controller with 6 10krpm drives.] > > I periodically hear reference to kernel threads - but from what I can tell > from following these lists for a couple months, and also searching the > archives, kernel threads aren't quite "there" yet ("there"=="can > use -kthread instead of -pthread and away we go"). Am I just missing the > right search phrases? > > Assuming the "kernel threads" still means "LinuxThreads" and not something > new that I haven't found, does anyone have any positive or negative > comments on how reasonable LinuxThreads on FreeBSD is for production use? > Is it stable, or still in development? > > Thanks, > scott > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 17:54:59 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 9A1F914E70 for ; Thu, 23 Dec 1999 17:54:56 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id UAA91331; Thu, 23 Dec 1999 20:54:43 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Thu, 23 Dec 1999 20:54:42 -0500 (EST) From: Chuck Robey To: scott Cc: Scott Hess , freebsd-hackers@FreeBSD.ORG Subject: Re: Status of kernel threads. In-Reply-To: <19991223190751.A26191@chronis.pobox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, scott wrote: > I've found > > http://www.cornfed.com/pk > > looks weird, but says it will do kernel threads for FreeBSD. I looked to see this, but didn't. It does say it has a "BSD" license, and it says it *cross*builds* under FreeBSD (and, for that matter, Linux also), but I see nowhere that it makes a FreeBSD kernel. It doesn't even say if it supports a filesystem. I'm downloading the code, but it sure doesn't say more on the website. ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 18: 4:57 1999 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 F1F4A156B2 for ; Thu, 23 Dec 1999 18:04:54 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id SAA55330; Thu, 23 Dec 1999 18:04:48 -0800 (PST) Date: Thu, 23 Dec 1999 18:04:47 -0800 (PST) From: Julian Elischer To: Chuck Robey Cc: scott , Scott Hess , freebsd-hackers@FreeBSD.ORG Subject: Re: Status of kernel threads. 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 this is the small realtime kernel mentionned at usenix. It is not a replacement for Unix/BSD. On Thu, 23 Dec 1999, Chuck Robey wrote: > On Thu, 23 Dec 1999, scott wrote: > > > I've found > > > > http://www.cornfed.com/pk > > > > looks weird, but says it will do kernel threads for FreeBSD. > > I looked to see this, but didn't. It does say it has a "BSD" license, and > it says it *cross*builds* under FreeBSD (and, for that matter, Linux > also), but I see nowhere that it makes a FreeBSD kernel. > > It doesn't even say if it supports a filesystem. I'm downloading the > code, but it sure doesn't say more on the website. > > ---------------------------------------------------------------------------- > Chuck Robey | Interests include C programming, Electronics, > 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. > Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and > (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) > ---------------------------------------------------------------------------- > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 19:23: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id EEC8F14EA9 for ; Thu, 23 Dec 1999 19:23:03 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id TAA12576; Thu, 23 Dec 1999 19:21:27 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id TAA00998; Thu, 23 Dec 1999 19:21:27 -0800 Received: from softweyr.com (dyn0.utah.xylan.com) by omni.xylan.com (4.1/SMI-4.1 (xylan engr [SPOOL])) id AA09364; Thu, 23 Dec 99 19:21:23 PST Message-Id: <3862E729.6CE2F0E0@softweyr.com> Date: Thu, 23 Dec 1999 20:23:21 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en Mime-Version: 1.0 To: miaobo@mail.zhongxing.com Cc: Jack Rusher , hackers@FreeBSD.ORG Subject: Re: ASYCH/message-based programming style References: <48256850.000F1B98.00@mail.zhongxing.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG miaobo@mail.zhongxing.com wrote: > > Thanks for your immediate response: > > It enlights me of some principles to access event driven programming > library. But I can't imagine what the primitives you mentioned would like, > can you give a breif list of them? Or, can you indicate what part of X > window code that I can learn of how to build up my own event-driven library > under UNIX? I wish it would not be too complicated since that Xlib and Xt > stuffs are nightmares to me. @_@ > > Or, as I mentioned, I think knowing the procedure of: from NIC receives a > network packet to application's blocked read() returns, will be helpful to > me. Can you give a basic introduction on this or just refer what parts of > kernel code that I should look at? None. A read through "Advanced Programming in the UNIX Environment", by W. Richard Stevens, is what you really need. "UNIX Network Programming" by the same author might also be helpful. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 19:38:17 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 5470214A00 for ; Thu, 23 Dec 1999 19:38:16 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 77C56137FC3; Thu, 23 Dec 1999 22:38:14 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id WAA06855; Thu, 23 Dec 1999 22:38:13 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14434.60068.862958.87344@trooper.velocet.net> Date: Thu, 23 Dec 1999 22:38:12 -0500 (EST) To: John Capo Cc: Nick Rogness , David Gilbert , freebsd-hackers@FreeBSD.ORG Subject: Re: deX OErrs on crossed link. In-Reply-To: <19991223164554.46592@irbs.com> References: <14434.26737.725275.154689@trooper.velocet.net> <19991223164554.46592@irbs.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "John" == John Capo writes: John> The de driver for stable will not select full-duplex on some John> (all?) cards with MII transceivers. I posted a patch for the John> DLINK 570TX quad port card that may work with other 21143/MII John> cards. I don't have the patch handy at the moment, check the John> list archives if anyone is interested. I totally wan't aware of the existence of the if_dc driver in -current (which is what I found when I searched the mailing lists for 21143). Since I'm running -current in this case, this seems to be the fix. I may have a -STABLE machine on which to test this out if I had the patch handy, but the outcome is not as critical tome. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 19:57:43 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 0379315112 for ; Thu, 23 Dec 1999 19:57:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA89205; Thu, 23 Dec 1999 19:57:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Julian Elischer Cc: Doug Rabson , Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... In-reply-to: Your message of "Thu, 23 Dec 1999 03:15:42 PST." Date: Thu, 23 Dec 1999 19:57:25 -0800 Message-ID: <89201.946007845@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Though doug didn't say so, I think the equivalent code in freeBSD is > > if ((fd = open("/dev/io",O_RDWR,0)) == -1) { > ERROR... > } Correct, and I find it a little embarassing. I mean god, what a hack! :-) There has just *got* to be a better way of granting (and checking for) this privilege. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 21: 7:39 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 4326614E50 for ; Thu, 23 Dec 1999 21:07:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA00684; Thu, 23 Dec 1999 21:11:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912240511.VAA00684@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jordan K. Hubbard" Cc: Julian Elischer , Doug Rabson , Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... In-reply-to: Your message of "Thu, 23 Dec 1999 19:57:25 PST." <89201.946007845@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Dec 1999 21:11:50 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Though doug didn't say so, I think the equivalent code in freeBSD is > > > > if ((fd = open("/dev/io",O_RDWR,0)) == -1) { > > ERROR... > > } > > Correct, and I find it a little embarassing. I mean god, what a hack! :-) > There has just *got* to be a better way of granting (and checking for) > this privilege. It's called i386_set_ioperm(), and it has a manpage too. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 21:22:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BEE4215773; Thu, 23 Dec 1999 21:22:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA89679; Thu, 23 Dec 1999 21:22:13 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Mike Smith Cc: Julian Elischer , Doug Rabson , Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... In-reply-to: Your message of "Thu, 23 Dec 1999 21:11:50 PST." <199912240511.VAA00684@mass.cdrom.com> Date: Thu, 23 Dec 1999 21:22:13 -0800 Message-ID: <89675.946012933@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Though doug didn't say so, I think the equivalent code in freeBSD is > > > > > > if ((fd = open("/dev/io",O_RDWR,0)) == -1) { > > > ERROR... > > > } > > > > Correct, and I find it a little embarassing. I mean god, what a hack! :-) > > There has just *got* to be a better way of granting (and checking for) > > this privilege. > > It's called i386_set_ioperm(), and it has a manpage too. Tada! Give that man a chocolate chip cookie! :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 21:31:59 1999 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 C18A515792; Thu, 23 Dec 1999 21:31:54 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id VAA59351; Thu, 23 Dec 1999 21:31:54 -0800 (PST) Date: Thu, 23 Dec 1999 21:31:52 -0800 (PST) From: Julian Elischer To: Mike Smith Cc: "Jordan K. Hubbard" , Doug Rabson , Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... In-Reply-To: <199912240511.VAA00684@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG well this one was obviously announced with a lot of fanfare! I'm glad to see it however! On Thu, 23 Dec 1999, Mike Smith wrote: > > > Though doug didn't say so, I think the equivalent code in freeBSD is > > > > > > if ((fd = open("/dev/io",O_RDWR,0)) == -1) { > > > ERROR... > > > } > > > > Correct, and I find it a little embarassing. I mean god, what a hack! :-) > > There has just *got* to be a better way of granting (and checking for) > > this privilege. > > It's called i386_set_ioperm(), and it has a manpage too. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 22:42:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 8C3E814D5D; Thu, 23 Dec 1999 22:42:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA01745; Thu, 23 Dec 1999 22:47:01 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912240647.WAA01745@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Julian Elischer Cc: Mike Smith , "Jordan K. Hubbard" , Doug Rabson , Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: Question about GLIDE... In-reply-to: Your message of "Thu, 23 Dec 1999 21:31:52 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Dec 1999 22:47:01 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > well this one was obviously announced with a lot of fanfare! > I'm glad to see it however! It was announced, and has been referenced many times subsequently. It's only been in the tree since mid-1998, and I suspect that the usual blindness to improvement that greets so many of these little upgrades has erased it from most peoples' memories. (I can even recall bde complaining that the interface wasn't so great (which is true)). > On Thu, 23 Dec 1999, Mike Smith wrote: > > > > > Though doug didn't say so, I think the equivalent code in freeBSD is > > > > > > > > if ((fd = open("/dev/io",O_RDWR,0)) == -1) { > > > > ERROR... > > > > } > > > > > > Correct, and I find it a little embarassing. I mean god, what a hack! :-) > > > There has just *got* to be a better way of granting (and checking for) > > > this privilege. > > > > It's called i386_set_ioperm(), and it has a manpage too. > > > > > > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Dec 23 23:21:31 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles558.castles.com [208.214.165.122]) by hub.freebsd.org (Postfix) with ESMTP id 381371514F for ; Thu, 23 Dec 1999 23:21:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA02292; Thu, 23 Dec 1999 23:25:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912240725.XAA02292@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Joe McGuckin Cc: hackers@freebsd.org Subject: Re: motherboard serial port dropping chars ? In-reply-to: Your message of "Mon, 20 Dec 1999 20:23:11 PST." <199912210423.UAA76829@monk.via.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 23 Dec 1999 23:25:50 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I have an application where I need to receive data constantly on > a serial port at 38,400. When we write the data to a database, > we constantly see dropped chars on the incoming serial port. > > Is the stock PC serial hardware capable of sustained thruput at > 38.4K? Easily, modulo other peripherals which can interfere with this. > Is there an ioctl option or something to improve the buffering > on the serial ports ? No. You probably have a PCI peripheral that's hogging the bus for sufficiently long to cause the FIFO in your serial device to overflow. IDE disks doing DMA are prime culprits for this, and X servers have been known to cause it as well (by disabling interrupts entirely). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 0:17:24 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 3B28115098 for ; Fri, 24 Dec 1999 00:17:16 -0800 (PST) (envelope-from kozowski@svjava.com) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id AAA11581 for hackers@FreeBSD.ORG; Fri, 24 Dec 1999 00:17:14 -0800 (PST) Date: Fri, 24 Dec 1999 00:17:14 -0800 From: Eric Kozowski To: hackers@FreeBSD.ORG Subject: samba problem Message-ID: <19991224001713.A11540@schooner.svjava.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm not really sure if freebsd-hackers is the right place to ask this, so please feel free to redirect me to the correct place. situation: samba 2.0.6 (installed via /stand/sysinstall) on 3.4-stable smbd and nmbd start fine. testparm doesn't report and error w/ smb.conf. when _any_ kind of access attempt is made against the server, i get the following error in log.smb: [1999/12/24 00:05:44, 0] smbd/oplock.c:open_oplock_ipc(93) open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Can't assign requested address an smbclient -L SERVERNAME (per the samba troubleshooting docs) results in the following: added interface ip=XXX.XXX.XXX.16 bcast=XXX.XXX.XXX.63 nmask=255.255.255.192 session request to SERVERNAME failed (code 0) session request to *SMBSERVER failed (code 0) i tried removing then reinstalling samba, to no avail. i've searched the samba.org docs and mail archives and didn't find any relevant info. anyone have any suggestions? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 0:41:35 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id 9408714FAC for ; Fri, 24 Dec 1999 00:41:31 -0800 (PST) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id SAA25014; Fri, 24 Dec 1999 18:40:48 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199912240840.SAA25014@mail.theinternet.com.au> Subject: Re: GLIDE for FreeBSD In-Reply-To: from Theo van Klaveren at "Dec 24, 1999 0:20:31 am" To: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren) Date: Fri, 24 Dec 1999 18:40:48 +1000 (EST) Cc: freebsd-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 +----[ Theo van Klaveren ]--------------------------------------------- | | Whew. After two late nights of furious hacking, you | can now download the modified source for Glide 2.46 | (the Voodoo Graphics version) at | | ftp://phoenix.student.utwente.nl/pub/glide Ummm.... gcc -DPACKAGE=\"glide\" -DVERSION=\"2.46\" -DSTDC_HEADERS=1 -I. -I. -Wall -O6 -fomit-frame-pointer -funroll-loops -fexpensive-optimizations -ffast-math -DPORTIO_DIRECT -DMAPPL_LINUX -I../../lib/fxmisc -g -O2 -c fxlinux.c -o fxlinux.o >/dev/null 2>&1 mv -f .libs/fxlinux.lo fxlinux.lo gmake[2]: *** No rule to make target `../../lib/fxmisc/fxdll.h', needed by `fxpci.lo'. Stop. gmake[2]: Leaving directory `/home/users/akm/glide/glide-2.46/lib/fxpci' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/home/users/akm/glide/glide-2.46/lib' gmake: *** [all-recursive] Error 1 I'm lookin' now... -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 0:45:46 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id EF39914CBE for ; Fri, 24 Dec 1999 00:45:43 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 942EFAB; Fri, 24 Dec 1999 09:45:42 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 8FE39A9; Fri, 24 Dec 1999 09:45:42 +0100 (CET) Date: Fri, 24 Dec 1999 09:45:42 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: Andrew Kenneth Milton Cc: Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: GLIDE for FreeBSD In-Reply-To: <199912240840.SAA25014@mail.theinternet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Dec 1999, Andrew Kenneth Milton wrote: > +----[ Theo van Klaveren ]--------------------------------------------- > | > | Whew. After two late nights of furious hacking, you > | can now download the modified source for Glide 2.46 > | (the Voodoo Graphics version) at > | > | ftp://phoenix.student.utwente.nl/pub/glide > > Ummm.... > > gcc -DPACKAGE=\"glide\" -DVERSION=\"2.46\" -DSTDC_HEADERS=1 -I. -I. -Wall -O6 -fomit-frame-pointer -funroll-loops -fexpensive-optimizations -ffast-math -DPORTIO_DIRECT -DMAPPL_LINUX -I../../lib/fxmisc -g -O2 -c fxlinux.c -o fxlinux.o >/dev/null 2>&1 > mv -f .libs/fxlinux.lo fxlinux.lo > gmake[2]: *** No rule to make target `../../lib/fxmisc/fxdll.h', needed by `fxpci.lo'. Stop. > gmake[2]: Leaving directory `/home/users/akm/glide/glide-2.46/lib/fxpci' > gmake[1]: *** [all-recursive] Error 1 > gmake[1]: Leaving directory `/home/users/akm/glide/glide-2.46/lib' > gmake: *** [all-recursive] Error 1 > Oops... forgot to add that header to the sources, so it didn't get packages up with 'gmake dist'... To fix: Grab the new tarball or copy fxdll.h from the original glide sources to lib/fxmisc. Theo van Klaveren http://phoenix.student.utwente.nl / ICQ #1353681 - Why, oh why didn't I take the _blue_ pill? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 0:47:51 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id E206414D47 for ; Fri, 24 Dec 1999 00:47:45 -0800 (PST) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id SAA25092; Fri, 24 Dec 1999 18:46:58 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199912240846.SAA25092@mail.theinternet.com.au> Subject: Re: GLIDE for FreeBSD In-Reply-To: from Theo van Klaveren at "Dec 24, 1999 9:45:42 am" To: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren) Date: Fri, 24 Dec 1999 18:46:58 +1000 (EST) Cc: akm@mail.theinternet.com.au, havoc@Cal30B054.student.utwente.nl, freebsd-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 +----[ Theo van Klaveren ]--------------------------------------------- | On Fri, 24 Dec 1999, Andrew Kenneth Milton wrote: | | > +----[ Theo van Klaveren ]--------------------------------------------- | > | | > | Whew. After two late nights of furious hacking, you | > | can now download the modified source for Glide 2.46 | > | (the Voodoo Graphics version) at | > | | > | ftp://phoenix.student.utwente.nl/pub/glide | > | > Ummm.... | | Oops... forgot to add that header to the sources, so it didn't get | packages up with 'gmake dist'... | | To fix: Grab the new tarball or copy fxdll.h from the original glide | sources to lib/fxmisc. Will grab new tarball shortly... (at least you know someone's testing it). -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 0:54:28 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.student.utwente.nl (cal30b054.student.utwente.nl [130.89.229.25]) by hub.freebsd.org (Postfix) with ESMTP id AC06614DE3 for ; Fri, 24 Dec 1999 00:54:26 -0800 (PST) (envelope-from havoc@Cal30B054.student.utwente.nl) Received: by phoenix.student.utwente.nl (Postfix, from userid 1000) id 5CBACAB; Fri, 24 Dec 1999 09:54:26 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by phoenix.student.utwente.nl (Postfix) with ESMTP id 5406CA9; Fri, 24 Dec 1999 09:54:26 +0100 (CET) Date: Fri, 24 Dec 1999 09:54:26 +0100 (CET) From: Theo van Klaveren X-Sender: havoc@Cal30B054.student.utwente.nl To: Andrew Kenneth Milton Cc: Theo van Klaveren , freebsd-hackers@FreeBSD.ORG Subject: Re: GLIDE for FreeBSD In-Reply-To: <199912240846.SAA25092@mail.theinternet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Dec 1999, Andrew Kenneth Milton wrote: > Will grab new tarball shortly... (at least you know someone's testing it). He he... To me, that's worth a hundred bug reports :) Theo van Klaveren http://phoenix.student.utwente.nl / ICQ #1353681 - Why, oh why didn't I take the _blue_ pill? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 1: 7:50 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id A0A2914F78 for ; Fri, 24 Dec 1999 01:07:46 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id KAA34097; Fri, 24 Dec 1999 10:07:04 +0100 (CET) (envelope-from leifn@neland.dk) Date: Fri, 24 Dec 1999 10:07:04 +0100 (CET) From: Leif Neland To: "Daniel C. Sobral" Cc: Justin Hawkins , freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem In-Reply-To: <3860003A.548F8343@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Dec 1999, Daniel C. Sobral wrote: > Justin Hawkins wrote: > > > > I think (I am not positive on this) that if the boot loader talks to a > > modem in command mode with echo on, it gets confused and won't boot any > > further. Is this a known problem? > > I'd say this is an expected result, not a known problem. It is doing > exactly what it is being told to (gibberish). Junk in, junk out. :-) > You'll just turn off echo in the modem. ATZ ATE0 AT&W > > Is there enough room in there for some code, which checks for this? IE if > > the first line output to the serial device == the first input (some > > version string probably) then it just ignores it and does the default > > action? > > Just configure it correctly. Don't tell it to talk to a serial device > that will be sending it gibberish. > A hack would be to have the loader emit ATE0 to protect itself from echoing modems. Another, but perhaps annoying would be flushing the input buffer before each read. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 1: 8:56 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from rapidnet.com (rapidnet.com [205.164.216.1]) by hub.freebsd.org (Postfix) with ESMTP id 1C15B14CD4 for ; Fri, 24 Dec 1999 01:08:54 -0800 (PST) (envelope-from jseidel@rapidnet.com) Received: from localhost (jseidel@localhost) by rapidnet.com (8.9.3/8.9.3) with ESMTP id CAA58061; Fri, 24 Dec 1999 02:08:39 -0700 (MST) Date: Fri, 24 Dec 1999 02:08:37 -0700 (MST) From: Jason Seidel To: Eric Kozowski Cc: hackers@FreeBSD.ORG Subject: Re: samba problem In-Reply-To: <19991224001713.A11540@schooner.svjava.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 What does your smb.conf file look like? > > i'm not really sure if freebsd-hackers is the right place to ask this, so > please feel free to redirect me to the correct place. > > situation: samba 2.0.6 (installed via /stand/sysinstall) on 3.4-stable > > smbd and nmbd start fine. testparm doesn't report and error w/ smb.conf. > > when _any_ kind of access attempt is made against the server, i get the > following error in log.smb: > > [1999/12/24 00:05:44, 0] smbd/oplock.c:open_oplock_ipc(93) > open_oplock_ipc: Failed to get local UDP socket for address 100007f. Error was Can't assign requested address > > > an smbclient -L SERVERNAME (per the samba troubleshooting docs) > results in the following: > > added interface ip=XXX.XXX.XXX.16 bcast=XXX.XXX.XXX.63 nmask=255.255.255.192 > session request to SERVERNAME failed (code 0) > session request to *SMBSERVER failed (code 0) > > > i tried removing then reinstalling samba, to no avail. > > i've searched the samba.org docs and mail archives and didn't find any > relevant info. anyone have any suggestions? > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 1:28:10 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from schooner.svjava.com (schooner.svjava.com [204.75.228.3]) by hub.freebsd.org (Postfix) with ESMTP id 444ED157BE for ; Fri, 24 Dec 1999 01:28:07 -0800 (PST) (envelope-from kozowski@svjava.com) Received: (from kozowski@localhost) by schooner.svjava.com (8.9.1a/svjava.com) id BAA11916; Fri, 24 Dec 1999 01:27:59 -0800 (PST) Date: Fri, 24 Dec 1999 01:27:59 -0800 From: Eric Kozowski To: Jason Seidel Cc: hackers@FreeBSD.ORG Subject: Re: samba problem Message-ID: <19991224012759.A11896@schooner.svjava.com> References: <19991224001713.A11540@schooner.svjava.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 24, 1999 at 02:08:37AM -0700, Jason Seidel wrote: > > What does your smb.conf file look like? [global] workgroup = SVJAVA server string = CLIPPER log file = /var/log/log.%m max log size = 50 security = user encrypt passwords = yes socket options = TCP_NODELAY dns proxy = no [homes] comment = Home Directories browseable = no writeable = yes To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 2:27:16 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id 2543C1514D for ; Fri, 24 Dec 1999 02:27:13 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA41126; Fri, 24 Dec 1999 10:38:00 GMT (envelope-from dfr@nlsystems.com) Date: Fri, 24 Dec 1999 10:38:00 +0000 (GMT) From: Doug Rabson To: Theo van Klaveren Cc: freebsd-hackers@freebsd.org Subject: Re: GLIDE for FreeBSD 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 Fri, 24 Dec 1999, Theo van Klaveren wrote: > > Whew. After two late nights of furious hacking, you > can now download the modified source for Glide 2.46 > (the Voodoo Graphics version) at > > ftp://phoenix.student.utwente.nl/pub/glide > > Note: I have completely hacked the source to bits > to achieve this. The source has been autoconf'ed > (scary, but at least it works, which cannot be said > of the build system 3DFX provided). All source files > needed for FreeBSD compilation have been included, > but Windows-compilation etc. have been dropped. > > I'd be more than happy to accept patches which'll > make it compile on other platforms again, but chances > are you'll have to get the neccesary files from the > original source file. > > Also, binaries of GLIDE and Mesa+glide > are available for FreeBSD-CURRENT. > > The GLIDE library has one bug, though: When quitting > an application, it won't restore the normal display. > If anyone can help me with this, that'd be GREAT! > > One last question: What are the chances of incorporating > the sources for Voodoo2/3 into one source tree? They > all have the swlibs/ directory (almost unchanged)... The cvs repository at sourceforge already has both the V2 and V3 sources in it. That is just the Glide 3 sources though. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 2:44:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 2E61314D3B for ; Fri, 24 Dec 1999 02:44:43 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.092 #1) id 121S6J-0005T4-00; Fri, 24 Dec 1999 10:37:35 +0000 Date: Fri, 24 Dec 1999 10:37:35 +0000 From: Ben Smithurst To: Bosko Milekic Cc: Sheldon Hearn , hackers@FreeBSD.ORG Subject: Re: SIGFPE on arithmetic overflow Message-ID: <19991224103735.A649@strontium.scientia.demon.co.uk> References: <59472.945979754@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bosko Milekic wrote: > Could somebody try this piece of code on a -STABLE machine, just out of > curiosity...? I did, it gets SIGFPE too. (3.4-RC machine actually, but near enough :-) -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 2:49:30 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (dialfwn02.fwn.rug.nl [129.125.32.152]) by hub.freebsd.org (Postfix) with ESMTP id 77E0814BEB for ; Fri, 24 Dec 1999 02:49:21 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id LAA00644; Fri, 24 Dec 1999 11:03:19 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Fri, 24 Dec 1999 11:03:19 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "John W. DeBoskey" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: PCMCIA-ATA/USB support for SanDisk/Digital Cameras In-Reply-To: <199912230248.VAA28883@bb01f39.unx.sas.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 > Basically, it appears to be a combination of PCMCIA-ATA > support melded together with USB. Hm, with a bit of luck it is a mass storage compliant device. (But I don't think so). Please, send me the output of usb_dump -D -f /dev/ugen0 available from http://www.etla.net/~n_hibma/usb/usb_dump.c That should give us some idea of what the device looks like. Cheers, Nick \ > > Does anyone have any experience with this unit? Am I correct > that with USB support coming onboard in -current that it would > be feasible to get a driver working? > > Thanks! > John > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 2:49:48 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 8725D14CFA for ; Fri, 24 Dec 1999 02:49:41 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 121SJf-000Jsr-00; Fri, 24 Dec 1999 12:51:23 +0200 From: Sheldon Hearn To: Ben Smithurst Cc: Bosko Milekic , hackers@FreeBSD.ORG Subject: Re: SIGFPE on arithmetic overflow In-reply-to: Your message of "Fri, 24 Dec 1999 10:37:35 GMT." <19991224103735.A649@strontium.scientia.demon.co.uk> Date: Fri, 24 Dec 1999 12:51:23 +0200 Message-ID: <76436.946032683@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Dec 1999 10:37:35 GMT, Ben Smithurst wrote: > > Could somebody try this piece of code on a -STABLE machine, just out of > > curiosity...? > > I did, it gets SIGFPE too. I think this boils down to my lack of understanding of IEEE floating point arithmetic standards. The following code behaves the same on every box I can find to test it on. Although I'm surprised that the exception is INV instead of OFL, it seems to be standard behaviour. Ciao, Sheldon. #include #include void do_weird(void) { double x; int i; printf("double x = 1e19; int i = (int)x\n"); x = 1e19; i = (int)x; printf("%d\n", i); } int main(void) { printf("clearing fp exception mask\n"); (void)fpsetmask(0); do_weird(); printf("setting fp exception mask to FP_X_OFL\n"); (void)fpsetmask(FP_X_OFL); do_weird(); printf("setting fp exception mask to FP_X_INV\n"); (void)fpsetmask(FP_X_INV); do_weird(); return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 2:50:22 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (dialfwn02.fwn.rug.nl [129.125.32.152]) by hub.freebsd.org (Postfix) with ESMTP id 90A9814CEB for ; Fri, 24 Dec 1999 02:50:06 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id LAA00660; Fri, 24 Dec 1999 11:07:33 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Fri, 24 Dec 1999 11:07:32 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "John W. De Boskey" Cc: freebsd-hackers@FreeBSD.ORG, olli@dorifer.heim3.tu-clausthal.de Subject: Re: PCMCIA-ATA/USB support for SanDisk/Digital Cameras In-Reply-To: <199912231841.NAA01666@FreeBSD.unx.sas.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 > uhub0: 2 ports with 2 removable, self powered > ugen0: SanDisk USB CFII, rev 1.00/0.05, addr 2 > ugen_set_config: ugen0 to configno 1, sc=0xc0d82000 > ugen_set_config: ifaceno 0 > ugen_set_config: endptno 0, endpt=0x01(1,1), sce=0xc0d820cc > ugen_set_config: endptno 1, endpt=0x02(2,1), sce=0xc0d82144 > ugen_set_config: endptno 2, endpt=0x03(3,0), sce=0xc0d82180 > > Other than the above output, I don't seem to be able to talk > to the device. /usr/sbin/usbdevs reports: > > # usbdevs -v > usbdevs: no USB controllers found Hm, you should do a make world. Or a cd /usr/src/*/usbdevs make make install cd /dev/ sh MAKEDEV ugen0 usb0 usb usbdevs -v Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 3:52:54 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.194]) by hub.freebsd.org (Postfix) with ESMTP id E4D3D151B7 for ; Fri, 24 Dec 1999 03:52:42 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.9.3/8.7.3) id MAA88528; Fri, 24 Dec 1999 12:49:41 +0100 (MET) Date: Fri, 24 Dec 1999 12:49:41 +0100 From: Martin Cracauer To: Sheldon Hearn Cc: Ben Smithurst , Bosko Milekic , hackers@FreeBSD.ORG Subject: Re: SIGFPE on arithmetic overflow Message-ID: <19991224124941.A88203@cons.org> References: <19991224103735.A649@strontium.scientia.demon.co.uk> <76436.946032683@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <76436.946032683@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Dec 24, 1999 at 12:51:23PM +0200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <76436.946032683@axl.noc.iafrica.com>, Sheldon Hearn wrote: > > > On Fri, 24 Dec 1999 10:37:35 GMT, Ben Smithurst wrote: > > > > Could somebody try this piece of code on a -STABLE machine, just out of > > > curiosity...? > > > > I did, it gets SIGFPE too. > > I think this boils down to my lack of understanding of IEEE floating > point arithmetic standards. > > The following code behaves the same on every box I can find to test it > on. Although I'm surprised that the exception is INV instead of OFL, it > seems to be standard behaviour. The cast gets compiled into a fistpl instruction (surrounded by control word manipulation), which is documented to set "invalid operation", not "overflow". Not knowing Intels reason (they may be more twisted), I think this makes sense: - The "overflow" execption is thrown for real floaing point overflow, which - if it was not masked - had a meaningful result - the FPU infinity value. - The "invalid" execption is thrown in this case of "too big for target integer type" because the result is undefined and in fact not usable in any way. If the FPU would ensure that the result would be the integer that approaches the former floating point value best (INT_MAX), it could make sense to thow it into the same basket as the floating operation (although not really, since that would require an integer infinity value). Since it doesn't even attempt to, but sets the result to complete nonsense, it choses to signal a different kind of error. This also shows why running such code with execptions enabled is usually good, not bad. Turn off exceptions only when the code is know to be aware of the effects. If you port and fix such a packet, insett a test for > INT_MAX before the cast, don't kill the exceptions. That latter would make it impossible to find the next occurance of this coding error. More info on digging follows, partly repeating what you found out already: #include #include volatile sig_atomic_t code; void handler_siginfo(int sig, siginfo_t *info, void *nix) { code = info->si_code; } int main(void) { double x; int i; struct sigaction act; act.sa_sigaction = handler_siginfo; act.sa_flags |= SA_SIGINFO; sigemptyset(&act.sa_mask); sigaction(SIGFPE, &act, NULL); code = -1; x = 1e19; i = (int)x; printf("%d\n", i); if (code != -1) fprintf(stderr, "Code: %d\n", code); return 0; } Code 7 = "Subscript out of bounds". While this is not the direct error value from the CPU (but the portable summary), you can tell that it's not an overflow. If you run th code with exceptions disabled, you can get the statusword afterward the cast, you will find that bit one "Invalid operation" has been set by the FPU. (You can't get the real status word in a signal handler because you can't access the normal program flow's state from inside the signal handler for now). If you look at the code for the cast, it looks like this: fldl -8(%ebp) fnstcw -38(%ebp) movw -38(%ebp),%ax orw $3072,%ax movw %ax,-40(%ebp) fldcw -40(%ebp) fistpl -12(%ebp) ; causes the exception fldcw -38(%ebp) ; thowns the delayed exception Intel documentation implies that fistpl throws "invalid operation", although the manuals are not clear enough and omit this kind of error from some tables of exceptions that looked complete. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 5: 6: 7 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (Postfix) with ESMTP id 0A2EE14DF6 for ; Fri, 24 Dec 1999 05:06:03 -0800 (PST) (envelope-from akm@mail.theinternet.com.au) Received: (from akm@localhost) by mail.theinternet.com.au (8.9.3/8.9.3) id XAA27959; Fri, 24 Dec 1999 23:05:20 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199912241305.XAA27959@mail.theinternet.com.au> Subject: Re: GLIDE for FreeBSD In-Reply-To: from Theo van Klaveren at "Dec 24, 1999 0:20:31 am" To: havoc@Cal30B054.student.utwente.nl (Theo van Klaveren) Date: Fri, 24 Dec 1999 23:05:20 +1000 (EST) Cc: freebsd-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 +----[ Theo van Klaveren ]--------------------------------------------- | | Whew. After two late nights of furious hacking, you | can now download the modified source for Glide 2.46 | (the Voodoo Graphics version) at Well it's working for me now, good work d8) -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew Milton The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | ACN: 082 081 472 | M:+61 416 022 411 | Carpe Daemon PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 6:52:42 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from kleopatra.acc.umu.se (kleopatra.acc.umu.se [130.239.18.150]) by hub.freebsd.org (Postfix) with ESMTP id 457A814F8A for ; Fri, 24 Dec 1999 06:52:36 -0800 (PST) (envelope-from saska@acc.umu.se) Received: from shaka.acc.umu.se (saska@shaka-fddi.acc.umu.se [192.168.18.148]) by kleopatra.acc.umu.se (8.9.3/8.9.3) with ESMTP id PAA10776; Fri, 24 Dec 1999 15:52:29 +0100 Received: (from saska@localhost) by shaka.acc.umu.se (8.9.3/8.9.3) id PAA15019; Fri, 24 Dec 1999 15:52:28 +0100 (MET) Date: Fri, 24 Dec 1999 15:52:28 +0100 From: Markus Holmberg To: "Ronald F. Guilmette" Cc: Sheldon Hearn , David Malone , hackers@FreeBSD.ORG Subject: Re: SIGFPE on arithmetic overflow Message-ID: <19991224155228.A15007@shaka.acc.umu.se> References: <59403.945979515@axl.noc.iafrica.com> <3246.945989187@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3246.945989187@monkeys.com>; from rfg@monkeys.com on Thu, Dec 23, 1999 at 02:46:27PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a small addition to this thread: There seems to be a withstanding bug in Mozilla unique for the FreeBSD port, that seems to be quite related to this thread. It's about casting and SIGFPE's. Here's the link: http://bugzilla.mozilla.org/show_bug.cgi?id=9967 I don't know enough about these matters to be able to draw any conclusions, but anyone is of course welcome to take a look at the Mozilla bug, because it needs someone who knows this stuff. Markus On Thu, Dec 23, 1999 at 02:46:27PM -0800, Ronald F. Guilmette wrote: > > In message <59403.945979515@axl.noc.iafrica.com>, you wrote: > > > > > > >On Thu, 23 Dec 1999 17:14:55 GMT, David Malone wrote: > > > >> Try adding a fpsetmask(fpgetmask()&(~FP_X_OFL)); before the calculation > >> and see what happens. > > > >It still bombs, although fpsetmask(0) does the trick. I'm really > >interested in hearing what causes the difference in behaviour. > > Sorry, I breezed past the first part of this thread too quickly, so > I forgot which OS is doing what. > > However let me say that I do still have a copy of the IEEE floating > point standard around here, and if anybody needs me to, I'll be happy > to look stuff up in it, and/or to cite chapter and verse. > > The bottom line, I think, is that the IEEE FP standard talks about two > things of interest here... exceptions and traps. An exception is just > some condition that probably only arises infrequently (e.g. overflow, > divide by zero, and other such stuff). An exception may or may not > cause a trap. A trap is one possible response to an exception, and > can be thought of as being essentially the same sort of thing as a > (non-blocked) UNIX signal. > > Anyway, to bring this back to the topic at hand, the relevant quote from > IEEE Std 754-1985 (Section 7, paragraph 1) is: > > ``The default response to an exception shall be to proceed > without a trap.'' > > In other words, for a conforming implementation of IEEE 754, unless > you explicitly override the default behavior (e.g. with a call to > fpsetmask) exceptions (including FP overflow) SHOULD NOT cause a > trap. > > I should say however that back when I was doing compiler testing for a > living... a few eons ago... this was something that a lot of implementa- > tions did seem to screw up.... Many compiler/library/OS combinations > would invoke main() with one or more of the IEEE FP exceptions set to > cause a trap/signal (in violation of IEEE 754). > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message -- Markus Holmberg | Give me UNIX or give me a typewriter. saska@acc.umu.se | http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 8:28:34 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from dragon.ham.muohio.edu (dragon.ham.muohio.edu [134.53.141.33]) by hub.freebsd.org (Postfix) with ESMTP id 128D914CF2 for ; Fri, 24 Dec 1999 08:28:32 -0800 (PST) (envelope-from howardjp@wam.umd.edu) Received: from localhost (howardjp@localhost) by dragon.ham.muohio.edu (8.9.3/8.9.3) with ESMTP id LAA04661; Fri, 24 Dec 1999 11:43:29 -0500 X-Authentication-Warning: dragon.ham.muohio.edu: howardjp owned process doing -bs Date: Fri, 24 Dec 1999 11:43:28 -0500 (EST) From: Jamie Howard X-Sender: howardjp@dragon.ham.muohio.edu To: Kip Macy Cc: miaobo@mail.zhongxing.com, hackers@FreeBSD.ORG Subject: Re:Re: Code In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Dec 1999, Kip Macy wrote: > Typically it refers to moving a process and all its associated attributes > from one machine to another. There are a lot of problems with it, to > the best of my knowledge the only OS that ever managed to get it right was > Berkeley's Elf which was designed with it in mind from the beginning. > Osterhout, the professor heading the group, said afterwords that the costs > exceeded the gains. Was Elf related to Sprite? Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 19:27:23 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 6C88F150F8 for ; Fri, 24 Dec 1999 19:27:11 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id TAA03627; Fri, 24 Dec 1999 19:26:32 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Fri, 24 Dec 1999 19:26:32 -0800 Date: Fri, 24 Dec 1999 19:26:32 -0800 (PST) From: Kip Macy To: Jamie Howard Cc: miaobo@mail.zhongxing.com, hackers@FreeBSD.ORG Subject: Re:Re: Code In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: howardjp@wam.umd.edu,miaobo@mail.zhongxing.com,hackers@FreeBSD.ORG X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Was Elf related to Sprite? > > Jamie Doh. That is probably what I meant to refer to. It has been a long time since I read about it. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Dec 24 21:18:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hurricane.columbus.rr.com (m4.columbus.rr.com [204.210.252.19]) by hub.freebsd.org (Postfix) with ESMTP id 3FA1814CA8 for ; Fri, 24 Dec 1999 21:18:23 -0800 (PST) (envelope-from caa@columbus.rr.com) Received: from columbus.rr.com ([24.95.60.151]) by hurricane.columbus.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-53939U80000L80000S0V35) with ESMTP id com; Sat, 25 Dec 1999 00:18:05 -0500 Received: (from caa@localhost) by columbus.rr.com (8.9.3/8.9.3) id AAA97125; Sat, 25 Dec 1999 00:18:16 -0500 (EST) (envelope-from caa) Date: Sat, 25 Dec 1999 00:18:14 -0500 From: "Charles Anderson" To: Theo van Klaveren Cc: patrick@whetstonelogic.com, joe@via.net, freebsd-hackers@FreeBSD.ORG Subject: Re: What's the best accellerated graphics card for XF86? Message-ID: <19991225001814.A97034@midgard.dhs.org> References: <199912232353.SAA69429@p.wl.vg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from havoc@Cal30B054.student.utwente.nl on Fri, Dec 24, 1999 at 12:58:34AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 24, 1999 at 12:58:34AM +0100, Theo van Klaveren wrote: > On Thu, 23 Dec 1999 patrick@whetstonelogic.com wrote: > > > On 23 Dec, Joe McGuckin wrote: > > > > > > Now tha GLIDE for FreeBSD is available, what's the best video card > > > for playing quake, etc? > > > > > Well, since GLIDE only support 3DFX cards, I'd say your choice is > pretty limited :) > > Besides that, the port I've done only supports the (now ancient) > Voodoo Graphics based cards. For Voodoo2/3, look at Doug Rabson's > patches to the original source code. > GLX works pretty good with my g400 max, It get 37.4 fps at 640x480 Normal settings with quake3. > > > > And, who is going to build us a FreeBSD Quake 1, now that the source is > > out! > > Sorry, I only got as far as the server so far :-) I've built glquake but I still has some bugs to work out. > > The X11 client built, but there is a bug in Quake's assembly code > (methinks) that produces a SIGBUS in memset() ... haven't investigated > thourougly(sp?) yet. > > I'll try and build the GL client, but I haven't got high hopes... > If anyone is intersted, I can give you my patches to the QuakeWorld > code (it fixes the Linux CDROM code and some other Linux specific > thingies). See above, the gl code was actually pretty easy on a first pass sort of thing. (Notice I'm not saying it's usable yet.) > > Theo van Klaveren > http://phoenix.student.utwente.nl / ICQ #1353681 > > - Why, oh why didn't I take the _blue_ pill? > -Charlie -- Charles Anderson caa@columbus.rr.com No quote, no nothin' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 1:10:53 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 012BC151F9; Sat, 25 Dec 1999 01:10:51 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id DAA15774; Sat, 25 Dec 1999 03:09:10 -0600 (CST) Date: Sat, 25 Dec 1999 03:09:10 -0600 From: Tim Tsai To: freebsd-hackers@freebsd.org Cc: sos@freebsd.org Subject: using vgl Message-ID: <19991225030910.A15516@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to do some work based on vgl but it appears that it is tied to syscons and any vgl programs must be started off a console. Is there any way I can start a vgl program from a remote terminal (but have the output be displayed on the local VGA screen) without writing a proxy of some kind? I peeked at the source and there are various syscons related ioctl() calls. Any reason that /dev/io and /dev/mem wasn't used instead? Thanks! Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 2:40:29 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from hotmail.com (f130.law3.hotmail.com [209.185.241.130]) by hub.freebsd.org (Postfix) with SMTP id F152514FFB for ; Sat, 25 Dec 1999 02:40:26 -0800 (PST) (envelope-from xoneill@hotmail.com) Received: (qmail 46234 invoked by uid 0); 25 Dec 1999 10:40:26 -0000 Message-ID: <19991225104026.46233.qmail@hotmail.com> Received: from 216.63.49.44 by www.hotmail.com with HTTP; Sat, 25 Dec 1999 02:40:25 PST X-Originating-IP: [216.63.49.44] From: "Xavier O'Neill" To: freebsd-hackers@freebsd.org Subject: Signal 11 during setup Date: Sat, 25 Dec 1999 02:40:25 PST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I presently have FreeBSD 2.2.8 on my system. I downloaded FreeBSD 3.4 Release and made two floppy images on newly formated floppies (did it twice). During setup on the mfsroot.flp I get a signal 11 error (Signal 11 error, I am saving what I can. ). From there the computer restarts. I did all kinds of trouble shooting and diagnostics as described by the sig11 FAQ link i seen on the FreeBSD site. I went to a holographic terminal to see the debugging, this error always happens as the /etc/fstab is being written. I never had a problem with this computer. It is fairly new. A p2 300 mhz, with 128 MB ram Someone told me on the FreeBSD channel (effnet) that someone on the design team broke it, don't know if he is a reliable source but he claimed to be a part of the freebsd developer team. Thank you very much :) warm reguard -xavier ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 6:42:49 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 0DED914E9D for ; Sat, 25 Dec 1999 06:42:46 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id XAA80176; Sat, 25 Dec 1999 23:42:44 +0900 (JST) To: FreeBSD-hackers@FreeBSD.org Cc: kato@ganko.eps.nagoya-u.ac.jp Subject: device name of floppy disk From: KATO Takenori X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991225234213C.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sat, 25 Dec 1999 23:42:13 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 25 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The MAKEDEV has such lines as: # ln -f ${name}${unit}.1200 ${name}${unit}96 # ln -f r${name}${unit}.1200 r${name}${unit}96 # ln -f ${name}${unit}.1200 ${name}${unit}96ds15 # ln -f r${name}${unit}.1200 r${name}${unit}96ds15 # ln -f ${name}${unit}.1200 ${name}${unit}135ds15 # ln -f r${name}${unit}.1200 r${name}${unit}135ds15 for floppy disk device. I have questions about these lines. 1. What is meanings of the name? I cannot understand meanings of `96', `96ds15' and `135ds15'. 2. Why they are commented out? 3. Are these entries mandatory for all floppy disk devices? (Should I make such lines when I add new mode for floppy disk?) Thanks. -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 10: 7:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from 1Cust106.tnt2.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 6A4A514EDB; Sat, 25 Dec 1999 10:07:52 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Sat, 25 Dec 1999 13:07:50 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Tim Tsai Cc: freebsd-hackers@freebsd.org, sos@freebsd.org Subject: Re: using vgl In-Reply-To: <19991225030910.A15516@futuresouth.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Dec 1999, Tim Tsai wrote: > I'm trying to do some work based on vgl but it appears that it is tied to > syscons and any vgl programs must be started off a console. Is there any > way I can start a vgl program from a remote terminal (but have the output > be displayed on the local VGA screen) without writing a proxy of some > kind? Err... why do you want to do that? Even if it's a big program, it should be properly written so that the frontend and backend can be separate and network-transparent, if that's to be its purpose. So the big question is, why aren't you using X11? > > I peeked at the source and there are various syscons related ioctl() calls. > Any reason that /dev/io and /dev/mem wasn't used instead? That's simple. We're not trying to move to making things MORE platform- specific. > > Thanks! > > Tim -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 10:12:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from 1Cust106.tnt2.washington.dc.da.uu.net (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 0C3ED151CD; Sat, 25 Dec 1999 10:12:41 -0800 (PST) (envelope-from green@FreeBSD.org) Date: Sat, 25 Dec 1999 13:12:35 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: KATO Takenori Cc: FreeBSD-hackers@FreeBSD.org Subject: Re: device name of floppy disk In-Reply-To: <19991225234213C.kato@gneiss.eps.nagoya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 25 Dec 1999, KATO Takenori wrote: > The MAKEDEV has such lines as: > > # ln -f ${name}${unit}.1200 ${name}${unit}96 > # ln -f r${name}${unit}.1200 r${name}${unit}96 > # ln -f ${name}${unit}.1200 ${name}${unit}96ds15 > # ln -f r${name}${unit}.1200 r${name}${unit}96ds15 > # ln -f ${name}${unit}.1200 ${name}${unit}135ds15 > # ln -f r${name}${unit}.1200 r${name}${unit}135ds15 > > for floppy disk device. I have questions about these lines. > > 1. What is meanings of the name? I cannot understand meanings of > `96', `96ds15' and `135ds15'. They're all synonymous, so I'd say that they're different names for a double-sided, high density 5.25" floppy. The difference between 135 and 96 is probably sector sizes. In any case, I wouldn't worry over them at all. > 2. Why they are commented out? Obsolescence, I'd think. > 3. Are these entries mandatory for all floppy disk devices? (Should I > make such lines when I add new mode for floppy disk?) When's the last time you saw new modes for 5.25" floppies? I'm not being sarcastic; I'm just pointing out that they're all obsolete. > > Thanks. > > -----------------------------------------------+--------------------------+ > KATO Takenori | FreeBSD | > Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | > Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | > |http://www.jp.FreeBSD.org/| > ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 10:33:45 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 49FAA14DEA; Sat, 25 Dec 1999 10:33:43 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id MAA06877; Sat, 25 Dec 1999 12:32:01 -0600 (CST) Date: Sat, 25 Dec 1999 12:32:01 -0600 From: Tim Tsai To: Brian Fundakowski Feldman Cc: freebsd-hackers@FreeBSD.org, sos@FreeBSD.org Subject: Re: using vgl Message-ID: <19991225123201.A6180@futuresouth.com> References: <19991225030910.A15516@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 25, 1999 at 01:07:50PM -0500, Brian Fundakowski Feldman wrote: > On Sat, 25 Dec 1999, Tim Tsai wrote: > > > I'm trying to do some work based on vgl but it appears that it is tied to > > syscons and any vgl programs must be started off a console. Is there any > > way I can start a vgl program from a remote terminal (but have the output > > be displayed on the local VGA screen) without writing a proxy of some > > kind? > > Err... why do you want to do that? Even if it's a big program, it should > be properly written so that the frontend and backend can be separate > and network-transparent, if that's to be its purpose. So the big question > is, why aren't you using X11? Because I want to? :-) Okay, this particular FreeBSD box is connected to a scan converter and the output is displayed on my TV. Sitting in front of the console is not real practical literally as the computer is nicely tucked away. It just seems weird to have vgl so tied to syscons when one of the big advantages of Unix has always been remote accessibility. We run more than a dozen FreeBSD machines at work and I've never sit in front a console other than for emergency maintenance. Think about a possible embedded systems project where you might use VGL to display some banners - it would make sense to be able start/stop a vgl program without being in front of the console. X11 is way too big for what I need. I just need some simple VGA graphics on my TV. I suppose I'll end up writing a small console program that can start up my program if no better solution exists. When I said "proxy" I don't mean client/server by any means. I just mean a way to start a console program without being on the console. Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 14:36:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id ABA6914C2D for ; Sat, 25 Dec 1999 14:36:26 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.9.3/8.9.3) with UUCP id AAA03129; Sun, 26 Dec 1999 00:38:28 +0300 (MSK) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id AAA16577; Sun, 26 Dec 1999 00:12:27 +0300 (MSK) Date: Sun, 26 Dec 1999 00:12:27 +0300 (MSK) From: Alexey Zelkin Message-Id: <199912252112.AAA16577@scorpion.crimea.ua> To: danfe@inet.ssc.nsu.ru (Alexey N. Dokuchaev) Cc: hackers@FreeBSD.org Subject: Re: Terminal colors X-Newsgroups: cris.gate.freebsd.hackers In-Reply-To: User-Agent: tin/pre-1.4-980618 (UNIX) (FreeBSD/2.2.7-RELEASE (i386)) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, AND> Say I want to change the man colors when I read mans at the console. More AND> precisely, I don't like that underlined text shows up as reversed (black AND> letter on while(grey,7) backround). How (and where) do I need to say that AND> I want, say, yellow on black instead of reversed when displaying AND> underlined-supposed-to-be text. Any help is greatly appreciated. For supported escape sequences (sequences used to change colors) you can read screen(4) manpage. Then read termcap(5) manpage. It will describe you termcap file structure. Pay espessial attention for `md' (bold mode on) and `so' (standout mode on) directives. Contact me directly if you need more comments. -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@FreeBSD.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 16: 2:25 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 81C9614CDE for ; Sat, 25 Dec 1999 16:02:23 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p20-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.117]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id JAA11004; Sun, 26 Dec 1999 09:02:05 +0900 (JST) Message-ID: <38655A47.42E616B3@newsguy.com> Date: Sun, 26 Dec 1999 08:59:03 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Leif Neland Cc: Justin Hawkins , freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Leif Neland wrote: > > > Just configure it correctly. Don't tell it to talk to a serial device > > that will be sending it gibberish. > > A hack would be to have the loader emit ATE0 to protect itself from > echoing modems. AFAIK, it would not protect against all modems. I think Winmodems, for instance, won't recognize that command. > Another, but perhaps annoying would be flushing the input buffer before > each read. It's not enough. At the baud rates a modem work at, even when echoing, the flush is likely to happen before the modem finishes echoing everything. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Nice try, Lao Che." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 16: 5:55 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id 74CD615192 for ; Sat, 25 Dec 1999 16:05:53 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id SAA07730; Sat, 25 Dec 1999 18:05:31 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <199912260005.SAA07730@celery.dragondata.com> Subject: Re: Serial boot prompt messages and a modem To: dcs@newsguy.com (Daniel C. Sobral) Date: Sat, 25 Dec 1999 18:05:31 -0600 (CST) Cc: leifn@neland.dk (Leif Neland), justin@tardis.mx.com.au (Justin Hawkins), freebsd-hackers@FreeBSD.ORG In-Reply-To: <38655A47.42E616B3@newsguy.com> from "Daniel C. Sobral" at Dec 26, 1999 08:59:03 AM X-Mailer: ELM [version 2.5 PL1] 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 > > Leif Neland wrote: > > > > > Just configure it correctly. Don't tell it to talk to a serial device > > > that will be sending it gibberish. > > > > A hack would be to have the loader emit ATE0 to protect itself from > > echoing modems. > > AFAIK, it would not protect against all modems. I think Winmodems, for > instance, won't recognize that command. True, but until you've downloaded boot code to the modem, most winmodems won't respond at all... (Also, most winmodems that I've seen don't emulate a UART, so they won't even cause a problem) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 16:15:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id DEB0514C16 for ; Sat, 25 Dec 1999 16:15:07 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id BAA61606; Sun, 26 Dec 1999 01:14:43 +0100 (CET) (envelope-from leifn@neland.dk) Date: Sun, 26 Dec 1999 01:14:42 +0100 (CET) From: Leif Neland To: "Daniel C. Sobral" Cc: Justin Hawkins , freebsd-hackers@FreeBSD.ORG Subject: Re: Serial boot prompt messages and a modem In-Reply-To: <38655A47.42E616B3@newsguy.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, 26 Dec 1999, Daniel C. Sobral wrote: > Leif Neland wrote: > > > > > Just configure it correctly. Don't tell it to talk to a serial device > > > that will be sending it gibberish. > > > > A hack would be to have the loader emit ATE0 to protect itself from > > echoing modems. > > AFAIK, it would not protect against all modems. I think Winmodems, for > instance, won't recognize that command. > A: AFAIK, winmodems are not connected to a serial port, they are internal boards. B: Real men don't use anything marked win* for Real Computing. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 19:23:33 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 859F91512F; Sat, 25 Dec 1999 19:23:28 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id MAA01466; Sun, 26 Dec 1999 12:23:27 +0900 (JST) To: green@FreeBSD.org Cc: kato@ganko.eps.nagoya-u.ac.jp, FreeBSD-hackers@FreeBSD.org Subject: Re: device name of floppy disk From: KATO Takenori In-Reply-To: Your message of "Sat, 25 Dec 1999 13:12:35 -0500 (EST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991226122257Z.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sun, 26 Dec 1999 12:22:57 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 33 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Fundakowski Feldman wrote: > They're all synonymous, so I'd say that they're different names for a > double-sided, high density 5.25" floppy. The difference between 135 > and 96 is probably sector sizes. In any case, I wouldn't worry over > them at all. Thank you! Track densities of 5" and 3.5" disks are 96 and 135 tpi, respectively. > When's the last time you saw new modes for 5.25" floppies? I'm not > being sarcastic; I'm just pointing out that they're all obsolete. I know following disks: 1 8"/5" HD double side 1024 bytes/sector 8 sectors/track, 77 cylinders 2 5" DD double side 512 bytes/sector 8 sectors/track, 80 cylinders 3 5" DD double side 512 bytes/sector 8 sectors/track, 80 cylinders 4 3.5" DD double side 512 bytes/sector 8 sectors/track, 80 cylinders 5 8"/5" HD double side 256 bytes/sector 26 sectors/track, 77 cylinders 6 3.5" HD double side 256 bytes/sector 26 sectors/track, 77 cylinders 7 5" DD double side 256 bytes/sector 16 sectors/track, 77 cylinders and so on (including DEC PDP-11 :-)). I'm trying to add 1, 2, 3 and 4. -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 20: 5: 6 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id C467F14C16 for ; Sat, 25 Dec 1999 20:05:01 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id XAA97635; Sat, 25 Dec 1999 23:02:43 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sat, 25 Dec 1999 23:02:43 -0500 (EST) From: Chuck Robey To: Alexey Zelkin Cc: "Alexey N. Dokuchaev" , hackers@FreeBSD.ORG Subject: Re: Terminal colors In-Reply-To: <199912252112.AAA16577@scorpion.crimea.ua> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 26 Dec 1999, Alexey Zelkin wrote: > hi, > > AND> Say I want to change the man colors when I read mans at the console. More > AND> precisely, I don't like that underlined text shows up as reversed (black > AND> letter on while(grey,7) backround). How (and where) do I need to say that > AND> I want, say, yellow on black instead of reversed when displaying > AND> underlined-supposed-to-be text. Any help is greatly appreciated. > > For supported escape sequences (sequences used to change colors) you can > read screen(4) manpage. > > Then read termcap(5) manpage. It will describe you termcap file structure. > Pay espessial attention for `md' (bold mode on) and `so' (standout mode on) > directives. > > Contact me directly if you need more comments. And don't forget all the many different flags to xterm, you can control a *lot* that way, if you're in X. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C programming, Electronics, 213 Lakeside Dr. Apt. T-1 | communications, and signal processing. Greenbelt, MD 20770 | I run picnic.mat.net: FreeBSD-current(i386) and (301) 220-2114 | jaunt.mat.net : FreeBSD-current(Alpha) ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Dec 25 21:42:47 1999 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 2CE2914D8A; Sat, 25 Dec 1999 21:42:46 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 1D61D1CD81A; Sat, 25 Dec 1999 21:42:46 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 25 Dec 1999 21:42:46 -0800 (PST) From: Kris Kennaway To: Ptacek Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: DES routines? In-Reply-To: <037901bf4d6c$b5db0620$502124d8@Ptacek> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999, Ptacek wrote: > Thanks for the info, by the way I found the ecb_crypt by doing a man > des_crypt. Are you sure this was on a FreeBSD box? I can't see ecb_crypt listed in our des_crypt(3) manpage, though it is on e.g. Solaris. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message