From owner-freebsd-hackers Sat Jan 1 3: 7:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns2.globalctg.net (ns2.globalctg.net [202.5.32.6]) by hub.freebsd.org (Postfix) with ESMTP id A573314DDC for ; Sat, 1 Jan 2000 03:07:11 -0800 (PST) (envelope-from nestar@globalctg.net) Received: from delivery.globalctg.net (ns1.aob.globalctg.net [202.5.32.5]) by ns2.globalctg.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id Z8FZ6K2J; Sat, 1 Jan 2000 17:05:28 +0600 Received: from [202.5.32.211] [202.5.32.211] by delivery.globalctg.net [202.5.32.10] with SMTP (MDaemon.v2.7.SP5.R) for ; Sat, 01 Jan 2000 17:06:13 +0600 Date: Sat, 1 Jan 2000 17:11:30 +0600 (BDT) From: "New Star Service Co." To: Freebsd-Newbie Cc: Freebsd-Hackers Subject: Install FreeBSD3.0 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-MDaemon-Deliver-To: freebsd-hackers@FreeBSD.org X-Return-Path: nestar@globalctg.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just now I subscribe in Freebsd mailing list. I use windows 98 and single user. I buy FreeBSD3.0 and 6.4GB harddisk. I want to learn freebsd installation,please help me how to i create partition for single user in my 6.4GB harddisk.I like to use complete 6.4GB for FreeBSD. Please give me details information step by step. waiting prompt reply. satyajit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 1 3:21:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-1.actllc.com (mail-1.actllc.com [209.221.160.11]) by hub.freebsd.org (Postfix) with ESMTP id 0070014D99; Sat, 1 Jan 2000 03:21:16 -0800 (PST) (envelope-from majid@ibroadcast.net) Received: from magic2 ([209.221.145.23]) by mail-1.actllc.com (8.9.3/8.9.1) with SMTP id DAA03439; Sat, 1 Jan 2000 03:25:45 -0800 Message-ID: <001d01bf544a$1dadb660$1791ddd1@balfourplace.com> From: "Majid Almassari" To: "New Star Service Co." , "Freebsd-Newbie" Cc: "Freebsd-Hackers" References: Subject: Re: Install FreeBSD3.0 Date: Sat, 1 Jan 2000 03:19:41 -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.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi and welcome a board, I strongly suggest reading the Online HandBook. It is a good coinsice reference to start with and its available at http://www.freebsd.org . It should take you through the installation step by step with no problems. It might seem intimidating at first with no prior unix knowledge but you will appreciate the superior benefits of FreeBSD, just hang in there and welcome to the new millinium with your new power to serve OS (even in a single mode). :-) Majid Almassari, MSEE, MCP. System Administrator. iBroadcast, Inc. (206) 223-5540 http://www.ibroadcast.net ----- Original Message ----- From: New Star Service Co. To: Freebsd-Newbie Cc: Freebsd-Hackers Sent: Saturday, January 01, 2000 3:11 AM Subject: Install FreeBSD3.0 > > Just now I subscribe in Freebsd mailing list. > I use windows 98 and single user. I buy FreeBSD3.0 and 6.4GB harddisk. > I want to learn freebsd installation,please help me how to i create > partition for single user in my 6.4GB harddisk.I like to use complete > 6.4GB for FreeBSD. > > Please give me details information step by step. > > waiting prompt reply. > satyajit > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 1 6:23:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id D688214F52 for ; Sat, 1 Jan 2000 06:23:39 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id PAA21152 for FreeBSD-hackers@freebsd.org; Sat, 1 Jan 2000 15:23:36 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 626718864; Sat, 1 Jan 2000 15:10:45 +0100 (CET) Date: Sat, 1 Jan 2000 15:10:45 +0100 From: Ollivier Robert To: FreeBSD hackers list Subject: Re: YES: it works.. Message-ID: <20000101151045.A18182@keltia.freenix.fr> Mail-Followup-To: FreeBSD hackers list References: <20000101002521.A51978@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: <20000101002521.A51978@yedi.iaf.nl> X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Wilko Bulte: > Happy New Millenium to all of you! Still one year to go for that Wilko :-) Nice try :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 1 11:58:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 3198815007; Sat, 1 Jan 2000 11:58:26 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 124UfH-00084E-00; Sat, 01 Jan 2000 11:58:15 -0800 Date: Sat, 1 Jan 2000 11:58:12 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Matthew Dillon Cc: Peter Wemm , freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-Reply-To: <199912311950.LAA85337@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 Fri, 31 Dec 1999, Matthew Dillon wrote: > : How many instances of postmark are you running? I used 4 separate > :instances (you must run them in separate directories). > > Well, you didn't say that! :-) I'm running one. I'll start up > another couple to match your test. Actually, I did. Postmark as a single process won't really stress your system much. Multiple instances should be similar to the load that postfix can put on a system. > : How fast are your disks? I used an external RAID-5 array that appears > :as single disk to FreeBSD. It is RAID-5, so the performance isn't that > :great for writing. I think my virtual disk is quite slow. If your system > :has fast disks, run more instances of postmark. > > Fast. Two striped 18G seacrates on each system 40 MB/sec SCSI bus on > one system, 80 MB/sec SCSI bus on the other. > > : > : Well, I lost last nights panic because of fsck complaining about several > :million unreferenced files. I'm going to log to disk next time. > : > :Tom > :Uniserve > > Ach. I think fsck verbosity is a problem. My capture file was 24 MB and growing. Almost all of it was fsck UNREF errors. Anyhow, the following is the panic. It isn't hard to see where it is going wrong. "inodedep" increases steadily. panic: kmem_malloc(4096): kmem_map too small: 213647360 total allocated mp_lock = 01000001; cpuid = 1; lapic.id = 00000000 boot() called on cpu#1 > -Matt > Matthew Dillon > > > Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 1 12: 0:49 2000 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 7725614FD3; Sat, 1 Jan 2000 12:00:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id MAA92398; Sat, 1 Jan 2000 12:00:37 -0800 (PST) (envelope-from dillon) Date: Sat, 1 Jan 2000 12:00:37 -0800 (PST) From: Matthew Dillon Message-Id: <200001012000.MAA92398@apollo.backplane.com> To: Kirk McKusick Cc: Greg Lehey , Mike Smith , Tom , freebsd-hackers@FreeBSD.ORG Subject: interesting results from softupdates/postmark test (was Re: softupdates and debug.max_softdeps) References: <199912310634.WAA00620@mass.cdrom.com> <20000101151826.L1528@freebie.lemis.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ho ho! Overnight the KVM useage in my postmark test on my FreeBSD-3.x test box jumped from 8MB to 51MB. My 4.x test box has remained stable at 18MB - no jump in KVM useage. Now I am having a hellofatime trying to stop the four postmark processes. If I stop one it prevents the others from being stopped. softupdates seems to allow processes to be stopped while holding locks! That's a bug, but not the one causing the KVM useage. st4# ps axl | fgrep post 0 684 335 0 18 0 6472 5976 softup T p1 71:26.51 postmark 0 863 335 0 -2 0 6472 6076 getblk D p1 125:05.16 postmark 0 864 335 0 -2 0 6472 6076 getblk D p1 127:46.63 postmark 0 866 335 0 18 0 6472 6076 - T p1 133:22.19 postmark 'sync' has no real effect, even after I kill the processes. iostat shows that ccd0 is completely saturated. test4# iostat ccd0 1 tty ccd0 cpu tin tout KB/t tps MB/s us ni sy in id 0 21 0.00 0 0.00 1 0 30 1 68 0 43 4.82 127 0.60 1 0 14 0 85 0 43 6.91 347 2.34 0 1 12 1 86 0 43 6.92 212 1.43 0 0 0 1 99 0 42 5.80 122 0.69 0 1 22 0 77 0 43 6.04 130 0.76 0 0 26 0 74 Here is the first vmstat -m output: NQNFS Lease 1 1K 1K 85696K 1 0 0 1K NFS hash 1 128K 128K 85696K 1 0 0 128K pagedep 64 20K 30K 85696K 150650 0 0 64,16K inodedep 95866 12112K 12468K 85696K 12084672 0 0 128,128K newblk 1 1K 1K 85696K 31740889 0 0 32,256 bmsafemap 73 3K 4K 85696K 1994953 0 0 32 allocdirect 325 21K 354K 85696K 31185275 0 0 64 indirdep 10 41K 129K 85696K 353964 0 0 32,8K allocindir 12 1K 9K 85696K 555613 0 0 64 freefrag521374 16293K 16343K 85696K 19393498 0 0 32 freeblks 72564 9071K 9147K 85696K 2318532 0 0 128 freefile 72564 2268K 2287K 85696K 2318532 0 0 32 diradd 483 16K 193K 85696K 2528350 0 0 32 mkdir 0 0K 1K 85696K 8 0 0 32 dirrem 95262 2977K 2988K 85696K 2413794 0 0 32 FFS node 25743 6436K 6436K 85696K 3221821 0 0 256 MFS node 1 1K 1K 85696K 3 0 0 64,256 UFS ihash 1 128K 128K 85696K 1 0 0 128K UFS mount 21 52K 52K 85696K 24 0 0 512,2K,4K,32K ZONE 18 3K 3K 85696K 18 0 0 128 mbuf 1 4K 4K 85696K 1 0 0 4K memdesc 1 4K 4K 85696K 1 0 0 4K Memory Totals: In Use Free Requests 51035K 2398K 156200252 Here is the second vmstat -m output, a few minutes after I've killed the four postmark processes. The softupdates dependancies are slowly draining. NQNFS Lease 1 1K 1K 85696K 1 0 0 1K NFS hash 1 128K 128K 85696K 1 0 0 128K pagedep 1 16K 30K 85696K 151028 0 0 64,16K inodedep 79358 10048K 12468K 85696K 12120648 0 0 128,128K newblk 1 1K 1K 85696K 31781645 0 0 32,256 bmsafemap 0 0K 4K 85696K 1999787 0 0 32 allocdirect 0 0K 354K 85696K 31225336 0 0 64 indirdep 0 0K 129K 85696K 354517 0 0 32,8K allocindir 0 0K 9K 85696K 556308 0 0 64 freefrag423942 13249K 16365K 85696K 19416872 0 0 32 freeblks 75076 9385K 9460K 85696K 2338023 0 0 128 freefile 75076 2347K 2365K 85696K 2338023 0 0 32 diradd 0 0K 193K 85696K 2531655 0 0 32 mkdir 0 0K 1K 85696K 8 0 0 32 dirrem 79088 2472K 2988K 85696K 2417111 0 0 32 FFS node 25743 6436K 6436K 85696K 3340478 0 0 256 MFS node 1 1K 1K 85696K 3 0 0 64,256 UFS ihash 1 128K 128K 85696K 1 0 0 128K UFS mount 21 52K 52K 85696K 24 0 0 512,2K,4K,32K ZONE 18 3K 3K 85696K 18 0 0 128 mbuf 1 4K 4K 85696K 1 0 0 4K memdesc 1 4K 4K 85696K 1 0 0 4K Memory Totals: In Use Free Requests 46714K 6718K 156702268 The drain rate: test4# while (1) while? vmstat -m | tail -2 while? sleep 10 while? end Memory Totals: In Use Free Requests (10 seconds per) 34127K 19334K 156997508 Memory Totals: In Use Free Requests 33262K 20199K 157014568 Memory Totals: In Use Free Requests 32303K 21157K 157029536 Memory Totals: In Use Free Requests 31287K 22174K 157045809 Memory Totals: In Use Free Requests 30471K 22989K 157063038 Memory Totals: In Use Free Requests 29270K 24191K 157079301 Memory Totals: In Use Free Requests 28361K 25100K 157099823 Memory Totals: In Use Free Requests 27123K 26338K 157117218 Memory Totals: In Use Free Requests 25984K 27520K 157132238 Memory Totals: In Use Free Requests 25760K 27913K 157151309 Memory Totals: In Use Free Requests 25463K 28322K 157182362 ... It's obvious to me what is going on. First we have a serious bug somewhere in the softupdates code that is allowing signal-stop to occur while softupdates is waiting for a lock. But what is really causing all hell to break loose is a combination of sotupdates building up a huge set of interrelated dependancies that eats a *lot* of disk bandwidth to unwind (due to seeking back and forth), and FreeBSD-3.x not flushing the 'right' buffers. I'm not sure what 4.x is doing that is making it less susceptible to the softupdates problem. It's quite obvious to me that 3.x is flushing its buffers non-optimally (well, we knew that already, that's one reason why getnewbuf() was rewritten and buf_daemon added!) but it's hard to say what 'optimal' should be since neither 3.x's nor 4.x's buffer cache are softupdates-aware (they can't tell whether a buffer will be redirted or not when they flush it). Kirk relies on the update daemon to flush vnodes out in the correct order but this tends to break down badly in a heavily loaded system. What we are left with is an non-optimal flush coupled with a huge set of interrelated dependancies. I also recall that the file-remove case is a complex special case with softupdates. Considering the number of 'dirrem' softupdates elements allocated I am guessing that this is the core of the problem. A vmstat -m on my 4.x test box, running the same postmark test for the same amount of time (about 24 hours) shows: inodedep 798 356K 2638K102400K 11294336 0 0 128,256K newblk 1 1K 1K102400K 10117649 0 0 32,256 bmsafemap 22 1K 12K102400K 3241677 0 0 32 allocdirect 435 28K 389K102400K 10117240 0 0 64 indirdep 0 0K 65K102400K 64 0 0 32,8K,32K allocindir 0 0K 10K102400K 408 0 0 64 freefrag 270 9K 73K102400K 2706257 0 0 32 freeblks 156 20K 1673K102400K 4255762 0 0 128 freefile 156 5K 419K102400K 4255793 0 0 32 diradd 219 7K 582K102400K 4342945 0 0 32 mkdir 0 0K 1K102400K 12 0 0 32 dirrem 96 3K 430K102400K 4255939 0 0 32 FFS node 47959 11990K 12415K102400K 4728732 0 0 256 UFS ihash 1 256K 256K102400K 1 0 0 256K UFS mount 18 49K 49K102400K 18 0 0 512,2K,4K,32K VM pgdata 1 256K 256K102400K 1 0 0 256K ZONE 18 3K 3K102400K 18 0 0 128 isadev 12 1K 1K102400K 12 0 0 64 ATA generic 3 1K 1K102400K 3 0 0 128 ATAPI generic 2 1K 1K102400K 3 0 0 32,128,256 ACD driver 3 2K 2K102400K 3 0 0 16,256,1K devbuf 749 407K 1654K102400K 22387016 0 0 16,32,64,128,256,512,1K,2K,4K,8K,16K,32K mbuf 1 4K 4K102400K 1 0 0 4K memdesc 1 4K 4K102400K 1 0 0 4K isa_devlist 19 3K 3K102400K 19 0 0 16,512,2K atkbddev 2 1K 1K102400K 2 0 0 16 Memory Totals: In Use Free Requests 18292K 7244K 97850590 The worst case KVM useage didn't blow up like it did on the 3.x box, though it is still using a considerable amount of meemory - 18+7 = 25MB at peak. But when I observe it in real time it is clear to me that although directory file removal dependancies build up, they appear to drain quickly enough to not post a problem. For example, I see 'dirrem' useage jump around between 0 and 200. I see 'diradd' useage build up to around 450 and then stabilize and finally drop down again. -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 Jan 1 13:17: 6 2000 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 519451507B; Sat, 1 Jan 2000 13:17:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA92971; Sat, 1 Jan 2000 13:17:03 -0800 (PST) (envelope-from dillon) Date: Sat, 1 Jan 2000 13:17:03 -0800 (PST) From: Matthew Dillon Message-Id: <200001012117.NAA92971@apollo.backplane.com> To: Kirk McKusick , Greg Lehey , Mike Smith , Tom , freebsd-hackers@FreeBSD.ORG Subject: Slight mistake in my DaemonNews column Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like the last set of corrections didn't get in before they published. http://www.daemonnews.org/200001/freebsd_vm.html In the section about "VM Objects" in one place I indicate that dead pages in B will not be reclaimed until B is collapsed, and near the end of this section I indicate that dead pages in B are reclaimed immediately. The first one is correct: Dead pages in B will not be reclaimed until B is collapsed. So, for example, if C1 and C2 both take a copy-on-write fault on the same page, copying that page from B, the page in B will now be inaccessible ('dead'), but the system will not be able to reclaim it until either C1 or C2 exit and the remaining Cn is collapsed into B. It can, however, swap it out, so no biggy. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 1 14:35: 4 2000 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 40AC414DCA; Sat, 1 Jan 2000 14:35:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA93859; Sat, 1 Jan 2000 14:35:02 -0800 (PST) (envelope-from dillon) Date: Sat, 1 Jan 2000 14:35:02 -0800 (PST) From: Matthew Dillon Message-Id: <200001012235.OAA93859@apollo.backplane.com> To: Kirk McKusick , Greg Lehey , Mike Smith , Tom , freebsd-hackers@FreeBSD.ORG Subject: Re: Slight mistake in my DaemonNews column Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ach, I also forgot the all-shadowed optimization, which is actually fairly important. Well, if anyone brings it up here's the problem and solution: "But doesn't the object model cause an ever deeper stack of layers as a server forks children out?". Even though we do not optimize the dead-page case we *do* optimize the all-shadowed case. Lets say that the parent, C1, touches all the pages in B causing a copy-on-write to occur to C1. C1 now entirely shadows B and therefore can BYPASS B. +----+----+ +----+ | C1 | C2 | | C2 | +----+----+ +---------+ | B | -> | C1 | B | +---------+ +---------+ | A | | A | +---------+ +---------+ Once the bypass occurs, B has only one reference and C2 and B can be collapsed together. Ok, so you might ask the question "But wait, what if B is large object (represents the entire data area of the program)? Doesn't that mean that neither C1 or C2 are likely to ever completely shadow B?". Answer: This is often true at the second level (B), but usually not true at the third level (C1 or C2). If C1 (the parent) or C2 (the child) forks again, then it is likely that something in the new layer D? will be able to completely overshadow C1 or C2 and thus D? will be able to bypass C1 or C2. The end result is that in typical useage, even with a lot of working going on, the object stack does not run more then 4 deep. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 1 15:39:24 2000 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 9DB3814C4B for ; Sat, 1 Jan 2000 15:39:20 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id RAA30322 for hackers@freebsd.org; Sat, 1 Jan 2000 17:39:07 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200001012339.RAA30322@celery.dragondata.com> Subject: No 'stupid user tricks' filenames? To: hackers@freebsd.org Date: Sat, 1 Jan 2000 17:39:07 -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 Has anyone thought about a sysctl to disallow the creation/renaming of file names to make them contain characters they probably shouldn't have? While I have no idea why, my customers seem to enjoy finding filenames that will make afio choke, or make some tool somewhere not like them. Before I go about trying to implement this, does anyone have suggestions or comments? (Yes, I realize the tools should be able to handle things like this, and that I should cluebat anyone trying this. However, it's still annoying, and should probably be not allowed under secure environments) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 1 16:23:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id C8BF314DF5 for ; Sat, 1 Jan 2000 16:23:40 -0800 (PST) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-135-42.bellatlantic.net [151.198.135.42]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id TAA15001; Sat, 1 Jan 2000 19:23:32 -0500 (EST) Message-ID: <386E9C18.A73FEAEE@bellatlantic.net> Date: Sat, 01 Jan 2000 19:30:16 -0500 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: ph0d@scr3am.com Cc: Wes Peters , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ph0d@scr3am.com wrote: > > I've got one currently and my FreeBSD box can do 3000-3300kBytes a second > without any complaints.. > > Full duplex has it's advantages, no doubt I don't think that you realy need a switch to achieve this speed on an empty network. With two machines connected to a 3Com 24-port 100Mbps hub (simplex) I had no problems achieving ~8MB/s on one FTP transfer and over 4MB/s on each of two FTP transfers running in opposite directions at the same time, when the network is otherwise idle. Cheap hubs (including that D-Link) tend to choke even at moverate load and lose packets but good hubs have no such problem. I've ran 14 FTP transmissions in parallel through 7 cards connected to this hub with quite good results, the average of total speed was over 7.8MB/s (started all transfers at once, looked at the time it took the last transfer to finish, divided the total size of all transfers by this time - so, because some of the transfers finished earlier the peak speed was higher). > On Fri, 31 Dec 1999, 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. > > > > I have a good reason to revive this thread. I thought anyone who followed > > this conversation might want to know that one of the switches we dicussed, > > the Netgear FS-105, is on a special at CompUSA right now -- THROUGH TOMORROW. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 1 20: 8:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from knecht.Sendmail.ORG (knecht.sendmail.org [209.31.233.176]) by hub.freebsd.org (Postfix) with ESMTP id 05BFF14E1F; Sat, 1 Jan 2000 20:08:19 -0800 (PST) (envelope-from mckusick@flamingo.McKusick.COM) Received: from flamingo.McKusick.COM (root@flamingo.mckusick.com [209.31.233.178]) by knecht.Sendmail.ORG (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id e0248HJ19117; Sat, 1 Jan 2000 20:08:17 -0800 (PST) Received: from flamingo.McKusick.COM (mckusick@localhost [127.0.0.1]) by flamingo.McKusick.COM (8.9.3/8.9.0) with ESMTP id TAA14605; Sat, 1 Jan 2000 19:47:31 -0800 (PST) Message-Id: <200001020347.TAA14605@flamingo.McKusick.COM> To: Matthew Dillon Subject: Re: interesting results from softupdates/postmark test (was Re: softupdates and debug.max_softdeps) Cc: Greg Lehey , Mike Smith , Tom , freebsd-hackers@freebsd.org In-reply-to: Your message of "Sat, 01 Jan 2000 12:00:37 PST." <200001012000.MAA92398@apollo.backplane.com> Date: Sat, 01 Jan 2000 19:47:31 -0800 From: Kirk McKusick Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Delta 1.40 to ffs_softdep.c (12/16/1999) fixes the `hanging while holding a lock' problem. It should be propagated to the 3.X branch. I have been working on a number of performance improvements to soft updates that will hopefully assist in the postmark benchmarks. Hopefully they will be ready to incorporate in the next week or so. I'll send them to you (Matt) when I am convinced that they are at least semantically correct to try out. Kirk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 1 21:39: 6 2000 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 6E53C14C15 for ; Sat, 1 Jan 2000 21:39:04 -0800 (PST) (envelope-from wes@softweyr.com) Received: from [204.68.178.39] (helo=softweyr.com ident=wes) by mail.xmission.com with esmtp (Exim 3.03 #3) id 124djF-0002A0-00; Sat, 01 Jan 2000 22:38:59 -0700 Message-ID: <386EE514.D30CA88D@softweyr.com> Date: Sat, 01 Jan 2000 22:41:40 -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: Sergey Babkin Cc: ph0d@scr3am.com, freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price References: <386E9C18.A73FEAEE@bellatlantic.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sergey Babkin wrote: > > I don't think that you realy need a switch to achieve > this speed on an empty network. With two machines > connected to a 3Com 24-port 100Mbps hub (simplex) > I had no problems achieving ~8MB/s on one FTP transfer > and over 4MB/s on each of two FTP transfers running > in opposite directions at the same time, when the > network is otherwise idle. Cheap hubs (including that > D-Link) tend to choke even at moverate load and lose > packets but good hubs have no such problem. > I've ran 14 FTP transmissions in parallel through 7 > cards connected to this hub with quite good results, > the average of total speed was over 7.8MB/s On a switch running full duplex on all ports, you should be able to get roughly 14 x 8MB/s with the same test. I'll let you know how it goes Monday night after I beat it up in the lab at work. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 1 22:55:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mass.cdrom.com (castles512.castles.com [208.214.165.76]) by hub.freebsd.org (Postfix) with ESMTP id AE9BC14E67; Sat, 1 Jan 2000 22:55: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 XAA09576; Sat, 1 Jan 2000 23:00:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001020700.XAA09576@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Lehey Cc: Mike Smith , Tom , freebsd-hackers@FreeBSD.ORG Subject: Re: softupdates and debug.max_softdeps In-reply-to: Your message of "Sat, 01 Jan 2000 15:18:26 +1030." <20000101151826.L1528@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 01 Jan 2000 23:00:22 -0800 From: Mike Smith Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thursday, 30 December 1999 at 22:34:04 -0800, Mike Smith wrote: > >> That is interesting. So I guess the conclusion to this is, softupdates > >> is useful for bursty IO, but not sustained because it can get far behind > >> until it eventually reaches the point where the machine reboots silently. > >> I guess the delay until reboot is dependent on the size of max_softdeps. > >> If it is big, it takes a while. > > > > I mentioned this a while back in the context of suspended I/O (in this > > case, a RAID array busy dealing with a failed disk). There wasn't much > > interest in dealing with it evinced at that point. > > On a related topic, I've taken to limiting the number of outstanding > transactions in Vinum, mainly to try to hunt down some strange > consistency problems when a very large number of transactions were > outstanding (for those of you who have been following this, this was > the "NULL b_biodone" syndrome). I still think there is a problem > hidden in the system which causes this. I've stopped seeing these in the Mylex driver after I stopped assuming that splbio() woult block re-entry into the strategy handler. In fact, if we had a lock-and-mask-interrupt primitive I wouldn't be using spl-anything, and I think that's the way we want to go. -- \\ 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 Jan 2 6:49:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from barter.dewline.com (barter.dewline.com [209.208.153.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B5A514F81; Sun, 2 Jan 2000 06:49:39 -0800 (PST) (envelope-from mackler@barter.dewline.com) Received: (from mackler@localhost) by barter.dewline.com (8.9.1/8.9.1) id JAA10783; Sun, 2 Jan 2000 09:49:38 -0500 (EST) Date: Sun, 2 Jan 2000 09:49:38 -0500 (EST) Message-Id: <200001021449.JAA10783@barter.dewline.com> To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org From: Adam Mackler Subject: creating bootable CD-ROM Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi: I have a couple questions related to booting my FreeBSD system from a CD-ROM: First, is "El Torito" the only way to boot from a CD-ROM? Is there some way to use disklabel to make the ISO9660 filesystem bootable, so that /boot and /kernel can just go in the CD-ROM filesystem, rather than being embedded in the image of a floppy disk? Second, what is the purpose of the -C boot flag? On the boot(8) man page is says "boot from CDROM," but I can boot from a CD (El Torito style) without it. Does it have any use, possibly in the context of my first question? Thanks very much in advance for any clues that anyone here has. Adam Mackler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 2 7:23:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 4068D14A14; Sun, 2 Jan 2000 07:23:24 -0800 (PST) (envelope-from jrs@enteract.com) Received: from shell-3.enteract.com (jrs@shell-3.enteract.com [207.229.143.42]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id JAA38304; Sun, 2 Jan 2000 09:23:22 -0600 (CST) (envelope-from jrs@enteract.com) Date: Sun, 2 Jan 2000 09:23:22 -0600 (CST) From: John Sconiers To: Adam Mackler Cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: creating bootable CD-ROM In-Reply-To: <200001021449.JAA10783@barter.dewline.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 Look up mkisofs. > I have a couple questions related to booting my FreeBSD > system from a CD-ROM: > First, is "El Torito" the only way to boot from a CD-ROM? > Is there some way to use disklabel to make the ISO9660 > filesystem bootable, so that /boot and /kernel can just > go in the CD-ROM filesystem, rather than being embedded in > the image of a floppy disk? > Second, what is the purpose of the -C boot flag? On the boot(8) > man page is says "boot from CDROM," but I can boot from > a CD (El Torito style) without it. Does it have any use, > possibly in the context of my first question? > Thanks very much in advance for any clues that anyone here has. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 2 8:42:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.erlangen.netsurf.de (erlangen.netsurf.de [194.163.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 838FB14E68 for ; Sun, 2 Jan 2000 08:42:18 -0800 (PST) (envelope-from d_f0rce@gmx.de) Received: from blade (user-er-u1.erlangen.netsurf.de [194.163.170.161]) by mail.erlangen.netsurf.de (8.9.3/8.9.3) with SMTP id RAA66483 for ; Sun, 2 Jan 2000 17:42:16 +0100 (CET) Message-ID: <001301bf5540$66b72610$0201a8c0@blade> From: "Steffen Merkel" To: Subject: Limited amount of variables in a multithreaded programm? Date: Sun, 2 Jan 2000 17:42:43 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I have a very strange problem here, which is that I can only define a limited amount of variables within a multithreaded program. Some days ago I described the following problem: >I want to write a programm which checks if a server is up by >pinging it. I looks like that: ###################################### main(){ for (every server){ pthread_create(....., startscan(),... ); } while(1){ sleep(1); printf("Main Awake again\n"); } } startscan(){ ping(server); printf("Going to sleep\n"); sleep(1); printf("Awake again!"); } ######################################## >I can see that the servers are getting pinged and that every >thread goes to sleep. As soon as every thread did it's job and >the first thread should awake the program get's a SIGSEGV. >I can't see the message "Awake again" from the first thread but >I saw that the first thread started to sleep and the last thread >finished too and the main thread printed "Awake again!". >Well with my little knowledge of C I would say that there is a >problem with the sleep function. But as soon as I remove the >ping() function the programm operates normally and runs forever. Meanwhile I was able to trace down the problem within the ping() function. It seems that I'm defining to many variables. ########################################### int ping(struct in_addr *ipaddress){ int s; /* socket handle for socket()*/ int ident = getpid() & 0xFFFF; /* to ident ICMP message */ int hlen; /* Header length */ struct sockaddr_in *to; /* used to prepare tohost */ struct sockaddr tohost; /* where to send ping - for sendto() */ struct sockaddr fromhost; struct ip *ip; struct icmp *icp; /* used to generate icmp message */ struct timeval *timetp; /* temporary time storage structure */ struct timeval actimetp; /* store current time */ u_char outmessage[MAXPACKET]; /* message we send */ u_char inmessage[MAXPACKET]; /* message we receive */ int i,ret; int mx_dup_ck = 1024; return(10); /* I removed the ping-routine and replaced it with * "return(10);" for testing reasons */ } ################################################ Though the program doesn't fail while it is executing ping() (as described above), I can make the program run fine, by removing the line "int mx_dup_ck = 1024;". It seems that the programm reached a kind of maximum number of variables or something like that. How can I increase this value or how can I solve my problem? Any ideas? Steffen Please reply directly to me because I'm not on the list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 2 10: 6:28 2000 Delivered-To: freebsd-hackers@freefall.freebsd.org Received: from rodia.zighelboim.com (rodia.zighelboim.com [204.27.67.11]) by hub.freebsd.org (Postfix) with ESMTP id A681014D2E for ; Sun, 2 Jan 2000 10:06:15 -0800 (PST) (envelope-from mango@rodia.zighelboim.com) Received: (from mango@localhost) by rodia.zighelboim.com (8.9.3/8.9.3) id MAA00371; Sun, 2 Jan 2000 12:06:14 -0600 (CST) (envelope-from mango) Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.4.4.FreeBSD:20000102120614:366=_" Date: Sun, 02 Jan 2000 12:06:14 -0600 (CST) Reply-To: Raul Zighelboim From: Raul Zighelboim To: freebsd-hackers@freefall.freebsd.org Subject: si0 and other kernel options... Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.4.4.FreeBSD:20000102120614:366=_ Content-Type: text/plain; charset=us-ascii Hello there; SInce I upgraded to 4.0-CURRENT from 3.0-Stable, I have not been able to get the Specializ XIO card to work; I have the card set to 0xD0000, and I reserved that address, as well as irq 11, on the bios for legaxy isa devices.... Less important, but equily frustrating, I cannot get the following devices to be recognised on a good-compiled kernel: unknown10: at port 0x200-0x207 on isa0 unknown11: at port 0x120-0x127 on isa0 unknown12: at port 0x330-0x331 on isa0 Attached is my kernel config file and the output of dmesg ... Thanks. ---------------------------------- E-Mail: Raul Zighelboim Date: 02-Jan-2000 Time: 12:00:47 ---------------------------------- --_=XFMail.1.4.4.FreeBSD:20000102120614:366=_ Content-Disposition: attachment; filename="dmesg.boot" Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii; name=dmesg.boot; SizeOnDisk=16805 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #2: Sat Jan 1 21:58:41 CST 2000 mango@rodia.zighelboim.com:/usr/src/sys/compile/RODIA Calibrating clock(s) ... TSC clock: 398278910 Hz, i8254 clock: 1193211 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II/Xeon/Celeron (398.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002fe000 - 0x040fcfff, 65007616 bytes (15871 pages) 0x04100000 - 0x07ff5fff, 66019328 bytes (16118 pages) avail memory = 126959616 (123984K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f6a90 bios32: Entry = 0xfd7b0 (c00fd7b0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x203 pnpbios: Found PnP BIOS data at 0xc00f6ae0 pnpbios: Entry = f0000:9fea Rev = 1.0 Other BIOS signatures found: ACPI: 000f6ac0 Preloaded elf kernel "kernel" at 0xc02e5000. Pentium Pro MTRR support enabled pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base f8000000, size 26 found-> vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=9 map[20]: type 1, range 32, base 00001060, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 00007000, size 4 found-> vendor=0x1013, dev=0x6001, revid=0x01 class=04-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f4302000, size 12 map[14]: type 1, range 32, base 00001000, size 5 map[18]: type 1, range 32, base f4000000, size 20 found-> vendor=0x9004, dev=0x8178, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=15 map[10]: type 1, range 32, base 00001400, size 8 map[14]: type 1, range 32, base f4301000, size 12 found-> vendor=0x8086, dev=0x1229, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base f4303000, size 12 map[14]: type 1, range 32, base 00001020, size 5 map[18]: type 1, range 32, base f4100000, size 20 found-> vendor=0x109e, dev=0x0350, revid=0x12 class=04-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 pci0: on pcib0 pcib1: at device 1.0 on pci0 found-> vendor=0x10de, dev=0x0020, revid=0x04 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f5000000, size 24 map[14]: type 1, range 32, base fc000000, size 24 pci1: on pcib1 vga-pci0: irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 pci0: Intel PIIX4 ATA controller (vendor=0x8086, dev=0x7111) at 7.1 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 9 chip1: at device 7.3 on pci0 csa0: irq 10 at device 11. 0 on pci0 device_probe_and_attach: csa0 attach returned 6 fxp0: irq 11 at device 13.0 on pci0 fxp0: Ethernet address 00:90:27:16:ac:eb bpf: fxp0 attached ahc0: irq 15 at device 14.0 on pci0 ahc0: Reading SEEPROM...done. ahc0: internal 50 cable is present, internal 68 cable is present ahc0: external cable not present ahc0: BIOS eeprom is present ahc0: High byte termination Enabled ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 411 instructions downloaded fxp1: irq 10 at device 15.0 on pci0 fxp1: Ethernet address 00:a0:c9:66:eb:72 bpf: fxp1 attached bktr0: irq 9 at device 16.0 on pci0 bktr0: could not map memory device_probe_and_attach: bktr0 attach returned 6 pnpbios: 18 devices, largest 126 bytes PNP0c02: adding memory range 0xe0000-0xe3fff, size=0x4000, align=0x4000 PNP0c02: start dependant pnpbios: handle 0 device ID PNP0c02 (020cd041) PNP0c02: adding io range 0x370-0x371, size=0x2, align=0x1 PNP0c02: adding io range 0xea-0xeb, size=0x2, align=0x1 PNP0c02: adding memory range 0xfffc0000-0xffffffff, size=0x40000 PNP0c02: start dependant pnpbios: handle 1 device ID PNP0c02 (020cd041) PNP0c01: adding memory range 0-0x9ffff, size=0xa0000 PNP0c01: adding memory range 0xe4000-0xfffff, size=0x1c000 PNP0c01: adding memory range 0x100000-0x7ffffff, size=0x7f00000 PNP0c01: adding memory range 0xfff80000-0xfffbffff, size=0x40000 PNP0c01: start dependant pnpbios: handle 2 device ID PNP0c01 (010cd041) PNP0200: adding io range 0-0xf, size=0x10, align=0x1 PNP0200: adding io range 0x81-0x8f, size=0xf, align=0x1 PNP0200: adding io range 0xc0-0xdf, size=0x20, align=0x1 PNP0200: adding dma mask 0x10 PNP0200: start dependant pnpbios: handle 3 device ID PNP0200 (0002d041) PNP0000: adding io range 0x20-0x21, size=0x2, align=0x1 PNP0000: adding io range 0xa0-0xa1, size=0x2, align=0x1 PNP0000: adding irq mask 00x4 PNP0000: start dependant pnpbios: handle 4 device ID PNP0000 (0000d041) PNP0100: adding io range 0x40-0x43, size=0x4, align=0x1 PNP0100: adding irq mask 00x1 PNP0100: start dependant pnpbios: handle 5 device ID PNP0100 (0001d041) PNP0b00: adding io range 0x70-0x71, size=0x2, align=0x1 PNP0b00: adding irq mask 0x100 PNP0b00: start dependant pnpbios: handle 6 device ID PNP0b00 (000bd041) PNP0303: adding io range 0x60-0x60, size=0x1, align=0x1 PNP0303: adding io range 0x64-0x64, size=0x1, align=0x1 PNP0303: adding irq mask 00x2 PNP0303: start dependant pnpbios: handle 7 device ID PNP0303 (0303d041) PNP0c04: adding io range 0xf0-0xff, size=0x10, align=0x1 PNP0c04: adding irq mask 0x2000 PNP0c04: start dependant pnpbios: handle 8 device ID PNP0c04 (040cd041) PNP0800: adding io range 0x61-0x61, size=0x1, align=0x1 PNP0800: start dependant pnpbios: handle 9 device ID PNP0800 (0008d041) PNP0a03: adding io range 0xcf8-0xcff, size=0x8, align=0x1 PNP0a03: start dependant pnpbios: handle 10 device ID PNP0a03 (030ad041) PNP0c02: adding io range 0x4d0-0x4d1, size=0x2, align=0x1 PNP0c02: adding io range 0x8000-0x803f, size=0x40, align=0x1 PNP0c02: adding io range 0x7000-0x700f, size=0x10, align=0x1 PNP0c02: start dependant pnpbios: handle 11 device ID PNP0c02 (020cd041) PNP0c02: adding memory range 0xcf800-0xcffff, size=0x800 PNP0c02: start dependant pnpbios: handle 12 device ID PNP0c02 (020cd041) PNP0f13: adding irq mask 0x1000 PNP0f13: start dependant pnpbios: handle 13 device ID PNP0f13 (130fd041) PNP0501: adding io range 0x3f8-0x3ff, size=0x8, align=0x8 PNP0501: adding irq mask 0x10 PNP0501: start dependant pnpbios: handle 14 device ID PNP0501 (0105d041) PNP0501: adding io range 0x2f8-0x2ff, size=0x8, align=0x8 PNP0501: adding irq mask 00x8 PNP0501: start dependant pnpbios: handle 15 device ID PNP0501 (0105d041) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x8 PNP0700: adding io range 0x3f7-0x3f7, size=0x1, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: start dependant pnpbios: handle 17 device ID PNP0700 (0007d041) PNP0400: adding io range 0x378-0x37f, size=0x8, align=0x8 PNP0400: adding irq mask 0x80 PNP0400: start dependant pnpbios: handle 19 device ID PNP0400 (0004d041) Trying Read_Port at 203 CSC0000: start dependant CSC0000: adding dma mask 0x2 CSC0000: adding dma mask 0x9 CSC0000: adding irq mask 0x20 CSC0000: adding io range 0x534-0x537, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x22f, size=0x10, align=0x20 CSC0000: start dependant CSC0000: adding dma mask 0xa CSC0000: adding dma mask 0xb CSC0000: adding irq mask 0xcb8 CSC0000: adding io range 0x534-0xfff, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x38b, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x26f, size=0x10, align=0x20 CSC0000: start dependant CSC0000: adding dma mask 0xb CSC0000: adding irq mask 0xcb8 CSC0000: adding io range 0x534-0xfff, size=0x4, align=0x4 CSC0000: adding io range 0x388-0x3cb, size=0x4, align=0x8 CSC0000: adding io range 0x220-0x30f, size=0x10, align=0x20 CSC0000: end dependant CSC0001: start dependant CSC0001: adding io range 0x200-0x207, size=0x8, align=0x8 CSC0001: start dependant CSC0001: adding io range 0x208-0x20f, size=0x8, align=0x8 CSC0001: end dependant CSC0010: adding io range 0x120-0x3af, size=0x8, align=0x8 CSC0003: start dependant CSC0003: adding irq mask 0x400 CSC0003: adding io range 0x330-0x331, size=0x2, align=0x8 CSC0003: start dependant CSC0003: adding irq mask 0xcb8 CSC0003: adding io range 0x330-0x361, size=0x2, align=0x8 CSC0003: start dependant CSC0003: adding io range 0x330-0x3e1, size=0x2, align=0x8 CSC0003: end dependant isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 26 03 c8 psm: status 26 03 c8 psm: status 26 03 c8 psm: status 10 00 64 psm: data 28 7f 81 psm: data 28 7f 81 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3-00, 3 buttons psm0: config:00000000, flags:00000000, packet size:4 psm0: syncmask:c8, syncbits:08 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 05 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0 kbd0 ppc: parallel port found at 0x378 ppc: chipset forced to generic ppc0: EPP SPP ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE/NIBBLE_ID/Extensibility Link Probing for PnP devices on ppbus0: ppbus0: PRINTER ESCPL2,BDC plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 pca0 at port 0x40 on isa0 pca0: PC speaker audio driver isa_probe_children: probing PnP devices unknown0: at iomem 0xe0000-0xe3fff on isa0 unknown1: at port 0x370-0x371,0xea-0xeb iomem 0xfffc0000-0xffffffff on isa0 unknown2: at iomem 0-0x9ffff,0xe4000-0xfffff,0x100000-0x7ffffff,0xfff8 0000-0xfffbffff on isa0 unknown3: at port 0-0xf,0x81-0x8f,0xc0-0xdf drq 4 on isa0 unknown: can't assign resources unknown4: at port 0x41-0x44 irq 0 on isa0 unknown5: at port 0x70-0x71 irq 8 on isa0 unknown: can't assign resources unknown6: at port 0xf0-0xff irq 13 on isa0 unknown: can't assign resources unknown7: at port 0xcf8-0xcff on isa0 unknown8: at port 0x4d0-0x4d1,0x8000-0x803f,0x7000-0x700f on isa0 unknown9: at iomem 0xcf800-0xcffff on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources pcm1: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 pcm: setmap c000, 2000; 0xd8307000 -> c000 pcm: setmap e000, 2000; 0xd8309000 -> e000 unknown10: at port 0x200-0x207 on isa0 unknown11: at port 0x120-0x127 on isa0 unknown12: at port 0x330-0x331 on isa0 BIOS Geometries: 0:03fe3f20 0..1022=1023 cylinders, 0..63=64 heads, 1..32=32 sectors 1:03fe3f20 0..1022=1023 cylinders, 0..63=64 heads, 1..32=32 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert enabled, rule-based forwarding disabled, unlimited logging bpf: ppp0 attached bpf: ppp1 attached bpf: ppp2 attached bpf: ppp3 attached new masks: bio 40080040, tty 400310ba, net 40071cba bpf: lo0 attached (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (probe4:ahc0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe4:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0 (probe4:ahc0:0:4:0): Invalid field in CDB ahc0: target 4 synchronous at 8.0MHz, offset = 0xf ahc0: target 1 using 16bit transfers ahc0: target 1 synchronous at 20.0MHz, offset = 0x8 ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 20.0MHz, offset = 0x8 Creating DISK da0 Creating DISK da1 Creating DISK cd0 pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number JK2240150WDXWN pass0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enable d pass1 at ahc0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number JK6238820S2XRJ pass1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enable d pass2 at ahc0 bus 0 target 4 lun 0 pass2: Removable CD-ROM SCSI-2 device pass2: 8.064MB/s transfers (8.064MHz, offset 15) Mounting root from ufs:/dev/da0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number JK6238820S2XRJ da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4340MB (8888924 512 byte sectors: 64H 32S/T 4340C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number JK2240150WDXWN da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4340MB (8888924 512 byte sectors: 64H 32S/T 4340C) da0s1: type 0xa5, start 0, end = 8888923, size 8888924 : OK start_init: trying /sbin/init da1s1: type 0xa5, start 0, end = 8888923, size 8888924 : OK da1s1: type 0xa5, start 0, end = 8888923, size 8888924 : OK --_=XFMail.1.4.4.FreeBSD:20000102120614:366=_ Content-Disposition: attachment; filename="RODIA" Content-Transfer-Encoding: 7bit Content-Description: kernel config file Content-Type: text/plain; charset=us-ascii; name=RODIA; SizeOnDisk=5092 # machine i386 cpu I586_CPU cpu I686_CPU ident ZIGHELBOIM maxusers 128 options INET #InterNETworking #options INET6 #IPv6 communications protocols #options IPSEC #IP security #options IPSEC_ESP #IP security (crypto; define w/ IPSEC) #options IPSEC_IPV6FWD #IP security tunnel for IPv6 #options IPSEC_DEBUG #debug for IP security options MROUTING # Multicast routing options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about options IPDIVERT #divert sockets #options TCP_RESTRICT_RST #restrict emission of TCP RST #options ICMP_BANDLIM options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=1500 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options INCLUDE_CONFIG_FILE # Include this file in kernel #options SOFTUPDATES options USER_LDT #allow user-level control of i386 ldt options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options MD5 controller isa0 controller pci0 # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device si0 at isa? iomem 0xD0000 irq 11 # Floppy drives controller fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # SCSI Controllers controller ahc0 # AHA2940 and onboard AIC7xxx devices options AHC_ALLOW_MEMIO # SCSI peripherals controller scbus0 at ahc0 device da0 at scbus0 target 0 device da1 at scbus0 target 1 device cd0 at scbus0 target 4 device sa0 device pass0 # atkbdc0 controls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) device apm0 at nexus? disable flags 0x20 # Advanced Power Management # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 controller ppbus0 # Parallel port bus (required) device lpt0 # Printer device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device #controller vpo0 # Requires scbus and da0 # PCI Ethernet NICs. device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) device fxp1 # Intel EtherExpress PRO/100B (82557, 82558) # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device ppp 4 # Kernel PPP pseudo-device tun 4 # Packet tunnel. pseudo-device pty # Pseudo-ttys (telnet etc) pseudo-device bpf 4 #Berkeley packet filter pseudo-device streams #pseudo-device speaker pseudo-device vn 4 pseudo-device snp 4 #options PPP_BSDCOMP #PPP BSD-compress support #options PPP_DEFLATE #PPP zlib/deflate/gzip support #options PPP_FILTER #enable bpf filtering (needs bpf) # for IPv6 #pseudo-device gif 4 #IPv6 and IPv4 tunneling #pseudo-device faith 1 #for IPv6 and IPv4 translation options AUTO_EOI_1 #options AUTO_EOI_2 options PPS_SYNC options HW_WDOG device pcm0 device csa0 device pca0 at isa? port IO_TIMER1 #device mpu0 at isa? port 0x330 irq 5 drq 0 #device joy0 at isa? port IO_GAME #device sbmidi0 at isa? port 0x330 device bktr0 controller smbus0 device smb0 at smbus? controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? #controller pcf0 at isa? port 0x320 irq 5 # USB support #controller uhci0 # UHCI PCI->USB interface #controller ohci0 # OHCI PCI->USB interface #controller usb0 # USB Bus (required) #device ugen0 # Generic #device uhid0 # "Human Interface Devices" #device ukbd0 # Keyboard #device ulpt0 # Printer #controller umass0 # Disks/Mass storage - Requires scbus and da0 #device ums0 # Mouse #device aue0 # ADMtek USB ethernet # Note that motherboard sound devices may require options PNPBIOS. options PNPBIOS options MSGBUF_SIZE=40960 --_=XFMail.1.4.4.FreeBSD:20000102120614:366=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sun Jan 2 10:34:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 05B4B14D1F for ; Sun, 2 Jan 2000 10:34:12 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p19-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.148]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA25016; Mon, 3 Jan 2000 03:33:44 +0900 (JST) Message-ID: <386F99FF.92B1B644@newsguy.com> Date: Mon, 03 Jan 2000 03:33:35 +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: Kevin Day Cc: hackers@FreeBSD.ORG Subject: Re: No 'stupid user tricks' filenames? References: <200001012339.RAA30322@celery.dragondata.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kevin Day wrote: > > Has anyone thought about a sysctl to disallow the creation/renaming of file > names to make them contain characters they probably shouldn't have? > > While I have no idea why, my customers seem to enjoy finding filenames that > will make afio choke, or make some tool somewhere not like them. > > Before I go about trying to implement this, does anyone have suggestions or > comments? > > (Yes, I realize the tools should be able to handle things like this, and > that I should cluebat anyone trying this. However, it's still annoying, and > should probably be not allowed under secure environments) Implement this as a file system layer that adds semantics to file creation and renaming. Yeah, I know that's not what you wanted to hear. :-) -- 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 Sun Jan 2 15:45:52 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id A0B2A152A4; Sun, 2 Jan 2000 15:45:43 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas1-40-78.dial.proxad.net [212.27.40.78]) by postfix2.free.fr (Postfix) with ESMTP id 4488C744D8; Mon, 3 Jan 2000 00:45:36 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id AAA13389; Mon, 3 Jan 2000 00:49:10 +0100 (CET) (envelope-from nsouch) Message-ID: <20000103004910.41467@armor.free.fr> Date: Mon, 3 Jan 2000 00:49:10 +0100 From: Nicolas Souchu To: hackers@freebsd.org Cc: current@freebsd.org, nsouch@freebsd.org Subject: HEADS-UP newppbus for beta-testing Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e X-Operating-System: FreeBSD armor 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there! FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current A major ppbus(4) release is available for beta-testing. It includes the port of the ppbus framework to the newbus system. http://www.freebsd.org/~nsouch/ppbus.html provides usefull notes about the configuration of ppbus through the MACHINE file and the newppbus developement progression (stability, caveats...) The newppbus will come in remplacement to the previous standalone ppbus architectural system. I did not read recent announces about future FreeBSD 4.x releases :( Of course, newppbus introduction would better before any -stable jump. Note that, only probe/attach and function interfaces were concerned by the port and tests are consequently only regression tests. The port was not to hard and the result should not be too bad. Moreover the current ppbus high level drivers stress the system well I think: vpo (SCSI controller), lpt (with PS data filtered by ghostscript and interrupts) Feel free to contact me for more, Nicholas. -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Jan 3 6: 3:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from vorbis.noc.easynet.net (fibalot.noc.easynet.net [195.40.1.251]) by hub.freebsd.org (Postfix) with SMTP id B829514F39 for ; Mon, 3 Jan 2000 06:03:18 -0800 (PST) (envelope-from chrisy@vorbis.noc.easynet.net) Received: (qmail 80557 invoked by uid 1943); 3 Jan 2000 14:02:45 -0000 Date: Mon, 3 Jan 2000 14:02:45 +0000 From: Chris Luke To: Steffen Merkel Cc: freebsd-hackers@freebsd.org Subject: Re: Limited amount of variables in a multithreaded programm? Message-ID: <20000103140245.A80391@easynet.net> References: <001301bf5540$66b72610$0201a8c0@blade> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <001301bf5540$66b72610$0201a8c0@blade> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steffen Merkel wrote (on Jan 02): > u_char outmessage[MAXPACKET]; /* message we send */ > u_char inmessage[MAXPACKET]; /* message we receive */ How big is MAXPACKET? This is all local scope stuff. You may not have enough stack defined. This really is C-101 type stuff. 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 Mon Jan 3 6:41:43 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web1901.mail.yahoo.com (web1901.mail.yahoo.com [128.11.23.50]) by hub.freebsd.org (Postfix) with SMTP id 27A4714E46 for ; Mon, 3 Jan 2000 06:41:40 -0800 (PST) (envelope-from manhtho@yahoo.com) Received: (qmail 6240 invoked by uid 60001); 3 Jan 2000 14:41:39 -0000 Message-ID: <20000103144139.6239.qmail@web1901.mail.yahoo.com> Received: from [202.167.121.197] by web1901.mail.yahoo.com; Mon, 03 Jan 2000 06:41:39 PST Date: Mon, 3 Jan 2000 06:41:39 -0800 (PST) From: Nguyen Manh Tho Subject: Asking about converting mailling system To: 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 Dear Sirs, Madam I am Nguyen Manh Tho, from Vietnam. I would like to know if there is any way to convert the mailling system from WinNT server using Nestcape software to Free BSD mailling system using sendmail software reserving all data and accounts ? How can I do that ? Other similar request is how to convert the mailling system from Turbo Linux system to Free BSD system reserving all data and accounts ? How can I do that ? We need to convert these mailling system to Free BSD version 2.2.7 system, and using Apache Web server, but I have no books, documents and experiences on Free BSD and Turbo Linux. I have a little experience on WinNT. I have just downloaded the Free BSD Handbook and try to read it as the only document for solving this problem I have no condition to pay and buy the book and CD set of Completed Free BSD because there is no Free BSD branch here. The Internet speed here is very terrible and not stable (about 100-150 bytes/second), very difficult to download and browse in Internet. Please answering me through both 2 address below: nmtho@dit.hcmut.edu.vn and manhtho@yahoo.com. Thank you for ahead, I am looking forward your reply, Best Regards, Nguyen Manh Tho. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 8:13:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id F26B6151A5 for ; Mon, 3 Jan 2000 08:13:18 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id LAA11371 for ; Mon, 3 Jan 2000 11:13:17 -0500 (EST) Date: Mon, 3 Jan 2000 11:13:17 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: hackers@freebsd.org Subject: microtime vs getmicrotime 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 Scanning through sys/kern_clock.c it looks like getmicrotime is preferable to microtime since only getmicrotime accounts for tco_method (set via the kern.timecounter sysctl). The same is true with getnanotime vs nanotime, etc. However, I've noticed a good bit of kernel code is still calling microtime and nanotime rather than the get- versions: $ cd /usr/src/sys; grep -Rw microtime * | wc -l 85 $ cd /usr/src/sys; grep -Rw nanotime * | wc -l 12 $ cd /usr/src/sys; grep -Rw getmicrotime * | wc -l 39 $ cd /usr/src/sys; grep -Rw getnanotime * | wc -l 23 Is there are reason for code to still use the {micro,nano}time functions as opposed to get{micro,nano}time? I should point out that I am looking at a recently-supped 3.4 source tree. Although my friend cvsweb says that -current code is still calling {micro,nano}time also. Thanks, Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 8:31: 9 2000 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 BD020151DD for ; Mon, 3 Jan 2000 08:30:56 -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 RAA61451; Mon, 3 Jan 2000 17:30:27 +0100 (MET) Date: Mon, 3 Jan 2000 17:30:27 +0100 From: Martin Cracauer To: Steffen Merkel Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Limited amount of variables in a multithreaded programm? Message-ID: <20000103173027.A61058@cons.org> References: <001301bf5540$66b72610$0201a8c0@blade> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <001301bf5540$66b72610$0201a8c0@blade>; from Steffen Merkel on Sun, Jan 02, 2000 at 05:42:43PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <001301bf5540$66b72610$0201a8c0@blade>, Steffen Merkel wrote: > int ping(struct in_addr *ipaddress){ > int s; /* socket handle for socket()*/ > int ident = getpid() & 0xFFFF; /* to ident ICMP message */ > int hlen; /* Header length */ > struct sockaddr_in *to; /* used to prepare tohost */ > struct sockaddr tohost; /* where to send ping - for sendto() */ > struct sockaddr fromhost; > struct ip *ip; > struct icmp *icp; /* used to generate icmp message */ > struct timeval *timetp; /* temporary time storage structure */ > struct timeval actimetp; /* store current time */ > u_char outmessage[MAXPACKET]; /* message we send */ > u_char inmessage[MAXPACKET]; /* message we receive */ > int i,ret; > > int mx_dup_ck = 1024; > return(10); /* I removed the ping-routine and replaced it with > * "return(10);" for testing reasons */ > } In FreeBSD, a normal process (fork/exec) has a stack that grows automatically as needed. You don't have this for threaded programs (and it is difficult to do). It's a save guess that this amount of stack allocation is more than the default stack size for a threaded program, and the stack cannot grow automatically. Did you check out the classic model before tangling with pthreads? :-) 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 Mon Jan 3 9: 0:44 2000 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 BC68C14D68 for ; Mon, 3 Jan 2000 09:00:41 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id JAA05284; Mon, 3 Jan 2000 09:00:05 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 03 Jan 2000 09:00:05 -0800 Date: Mon, 3 Jan 2000 09:00:05 -0800 (PST) From: Kip Macy To: Martin Cracauer Cc: Steffen Merkel , freebsd-hackers@FreeBSD.ORG Subject: Re: Limited amount of variables in a multithreaded programm? In-Reply-To: <20000103173027.A61058@cons.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: cracauer@cons.org,d_f0rce@gmx.de,freebsd-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 What is wrong with malloc, then free? The stack size of threads on FreeBSD is not that big, but there is no need to be declaring large auto variables. Don't get me wrong, I have blown the stack on FreeBSD, and a number of other OSs as well, but dynamic allocation has fixed it in all cases. -Kip On Mon, 3 Jan 2000, Martin Cracauer wrote: > In <001301bf5540$66b72610$0201a8c0@blade>, Steffen Merkel wrote: > > int ping(struct in_addr *ipaddress){ > > int s; /* socket handle for socket()*/ > > int ident = getpid() & 0xFFFF; /* to ident ICMP message */ > > int hlen; /* Header length */ > > struct sockaddr_in *to; /* used to prepare tohost */ > > struct sockaddr tohost; /* where to send ping - for sendto() */ > > struct sockaddr fromhost; > > struct ip *ip; > > struct icmp *icp; /* used to generate icmp message */ > > struct timeval *timetp; /* temporary time storage structure */ > > struct timeval actimetp; /* store current time */ > > u_char outmessage[MAXPACKET]; /* message we send */ > > u_char inmessage[MAXPACKET]; /* message we receive */ > > int i,ret; > > > > int mx_dup_ck = 1024; > > return(10); /* I removed the ping-routine and replaced it with > > * "return(10);" for testing reasons */ > > } > > In FreeBSD, a normal process (fork/exec) has a stack that grows > automatically as needed. You don't have this for threaded programs > (and it is difficult to do). It's a save guess that this amount of > stack allocation is more than the default stack size for a threaded > program, and the stack cannot grow automatically. > > Did you check out the classic model before tangling with pthreads? :-) > > 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 > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 9:44:13 2000 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 3C6B514CE1 for ; Mon, 3 Jan 2000 09:44:04 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id SAA17801; Mon, 3 Jan 2000 18:42:34 +0100 (CET) Date: Mon, 3 Jan 2000 18:42:33 +0100 From: Martin Cracauer To: Kip Macy Cc: Martin Cracauer , Steffen Merkel , freebsd-hackers@FreeBSD.ORG Subject: Re: Limited amount of variables in a multithreaded programm? Message-ID: <20000103184233.B17710@cons.org> References: <20000103173027.A61058@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kip@lyris.com on Mon, Jan 03, 2000 at 09:00:05AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Kip Macy wrote: > What is wrong with malloc, then free? The stack size of threads on FreeBSD > is not that big, but there is no need to be declaring large auto > variables. Don't get me wrong, I have blown the stack on FreeBSD, and a > number of other OSs as well, but dynamic allocation has fixed it in all > cases. > Not sure if this is a serious question, especially considering that the size constants aren't got from the system but from ping(8) own guessing, but anyway: 1) Stack-allocated memory gets deallocated even when you drop out the routine other than an implicit return at the end. I.e. explicit return before the end of the procudure, longjmp'ing etc. 2) Stack-allocation is faster, since malloc needs bookkeeping while the stack "allocator" just grows or shrinks with no intermedeate allocation or freeing. In other words: What gets allocated last, will be free'ed first and that guarantee makes allocation a lot faster. I see the existance of an auto-growing stack as an indication how elegant the initial UNIX concurrency/procces model really is. Some people forget this in these days of Thread-hype. Another problem with the code in question is that it calls a function (getpid()) in variable initialization. Not advertised since it hardens debugging in case of problems further down. A few "const" here and there probably won't hurt either. FreeBSD's ping(8) is not a program that should be used for teaching C coding, threaded or not :-) Happy new year! Martin > On Mon, 3 Jan 2000, Martin Cracauer wrote: > > > In <001301bf5540$66b72610$0201a8c0@blade>, Steffen Merkel wrote: > > > int ping(struct in_addr *ipaddress){ > > > int s; /* socket handle for socket()*/ > > > int ident = getpid() & 0xFFFF; /* to ident ICMP message */ > > > int hlen; /* Header length */ > > > struct sockaddr_in *to; /* used to prepare tohost */ > > > struct sockaddr tohost; /* where to send ping - for sendto() */ > > > struct sockaddr fromhost; > > > struct ip *ip; > > > struct icmp *icp; /* used to generate icmp message */ > > > struct timeval *timetp; /* temporary time storage structure */ > > > struct timeval actimetp; /* store current time */ > > > u_char outmessage[MAXPACKET]; /* message we send */ > > > u_char inmessage[MAXPACKET]; /* message we receive */ > > > int i,ret; > > > > > > int mx_dup_ck = 1024; > > > return(10); /* I removed the ping-routine and replaced it with > > > * "return(10);" for testing reasons */ > > > } > > > > In FreeBSD, a normal process (fork/exec) has a stack that grows > > automatically as needed. You don't have this for threaded programs > > (and it is difficult to do). It's a save guess that this amount of > > stack allocation is more than the default stack size for a threaded > > program, and the stack cannot grow automatically. > > > > Did you check out the classic model before tangling with pthreads? :-) > > > > 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 > > > > > -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 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 Mon Jan 3 9:56:37 2000 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 2A25D15069 for ; Mon, 3 Jan 2000 09:56:35 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id JAA05919; Mon, 3 Jan 2000 09:56:02 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 03 Jan 2000 09:56:01 -0800 Date: Mon, 3 Jan 2000 09:56:01 -0800 (PST) From: Kip Macy To: Martin Cracauer Cc: Steffen Merkel , freebsd-hackers@FreeBSD.ORG Subject: Re: Limited amount of variables in a multithreaded programm? In-Reply-To: <20000103184233.B17710@cons.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: cracauer@cons.org,d_f0rce@gmx.de,freebsd-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 > > FreeBSD's ping(8) is not a program that should be used for teaching C > coding, threaded or not :-) I am inclined to agree. Programs that could cause DOS attacks are not a good way to start one's education. My point was merely that the problem was not insurmountable without raising the threads' stack size. Unless you know a priori how many threads you are going to have, changing the threads' stack size is dangerous. And yes, threads leave a lot to be desired as a programming model. I agree with Osterhout that the event model is the best way to go for most things for which threads are used. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 10:59: 3 2000 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 AB72115214 for ; Mon, 3 Jan 2000 10:58:46 -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 247; Mon, 3 Jan 2000 10:54:27 -0800 Message-ID: <007401bf561c$6ff51930$1e80000a@avantgo.com> From: "Scott Hess" To: "Kip Macy" , "Steffen Merkel" Cc: References: Subject: Re: Kernel threads Date: Mon, 3 Jan 2000 10:57:52 -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 Kip Macy wrote: > The words "POSIX threads" only describes the API. It says nothing about > the implementation. On FreeBSD they are non-preemptive user level threads > (your main was never yielding so the thread you launched did not get any > time). On Linux they are processes sharing the same virtual memory space, > and are referred to as kernel threads. For compute bound activities you > want kernel threads to spread the computation over multiple processors. > For I/O bound activities you want user level threads so you can minimize > the context switch overhead. As currently implemented, this last is only partially true. For I/O bound activities you want user level threads for any I/O that can block - in particular, _not_ disk I/O. As I mentioned in another thread ("Status of kernel threads"), disk I/O _always_ blocks, which means that the current userland threading library effectively serializes disk access, which is a tremendous loss compared to kernel threads. The best fix I've thought of thus far (other than async I/O, which I understand isn't ready for prime time) would be to have a number of kernel threads to handle never-blocking I/O. If the file descriptor can do blocking I/O, throw it into the select() loop, but if it can't, throw the system call into a queue for a pool of seperate kernel threads to run it. This pool should definitely be bigger than the number of CPUs available, because aggregate disk I/O gets more efficient as you increase the number of outstanding requests. Later, scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 11:10:16 2000 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 22D0215426 for ; Mon, 3 Jan 2000 11:10:11 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id LAA06923; Mon, 3 Jan 2000 11:09:58 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 03 Jan 2000 11:09:57 -0800 Date: Mon, 3 Jan 2000 11:09:57 -0800 (PST) From: Kip Macy To: Scott Hess Cc: freebsd-hackers@freebsd.org Subject: AIO was Re: Kernel threads In-Reply-To: <007401bf561c$6ff51930$1e80000a@avantgo.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: scott@avantgo.com,freebsd-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 > > The best fix I've thought of thus far (other than async I/O, which I > understand isn't ready for prime time) would be to have a number of kernel Speaking of AIO, which I would really like to use if possible, how actively maintained is it? The copyright on vfs_aio.c is 1997, suggesting to me that John Dyson has moved onto other things. -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 11:18:59 2000 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 2EBC7151DB for ; Mon, 3 Jan 2000 11:18:50 -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 LAA14195; Mon, 3 Jan 2000 11:18: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 LAA26800; Mon, 3 Jan 2000 11:18:34 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id LAA08045; Mon, 3 Jan 2000 11:17:25 -0800 (PST) Message-ID: <3870F6B6.EC4EE37E@softweyr.com> Date: Mon, 03 Jan 2000 12:21:26 -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: Kip Macy Cc: Scott Hess , freebsd-hackers@freebsd.org Subject: Re: AIO was Re: Kernel threads References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kip Macy wrote: > > > > > The best fix I've thought of thus far (other than async I/O, which I > > understand isn't ready for prime time) would be to have a number of kernel > > Speaking of AIO, which I would really like to use if possible, how > actively maintained is it? The copyright on vfs_aio.c is 1997, suggesting > to me that John Dyson has moved onto other things. It's passively maintained. ;^) I've become a little familiar with the code, and BDE has graciously agreed to review whatever I do to make sure I don't hobble it. If you need help, yell. -- "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 Jan 3 11:23:55 2000 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 DA5F8151A7 for ; Mon, 3 Jan 2000 11:23:47 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id LAA07091; Mon, 3 Jan 2000 11:23:33 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Mon, 03 Jan 2000 11:23:33 -0800 Date: Mon, 3 Jan 2000 11:23:33 -0800 (PST) From: Kip Macy To: Wes Peters Cc: freebsd-hackers@freebsd.org Subject: Re: AIO was Re: Kernel threads In-Reply-To: <3870F6B6.EC4EE37E@softweyr.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: wes@softweyr.com,freebsd-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 Mon, 3 Jan 2000, Wes Peters wrote: > Kip Macy wrote: > > > > > > > > The best fix I've thought of thus far (other than async I/O, which I > > > understand isn't ready for prime time) would be to have a number of kernel > > > > Speaking of AIO, which I would really like to use if possible, how > > actively maintained is it? The copyright on vfs_aio.c is 1997, suggesting > > to me that John Dyson has moved onto other things. > > It's passively maintained. ;^) > > I've become a little familiar with the code, and BDE has graciously agreed > to review whatever I do to make sure I don't hobble it. If you need help, > yell. > I have a little, ~300LOC, program in which aio does not behave as I think it should. Would it be possible for me to send it to you and have you take a look at it? -Kip To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 12:16:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 772CE151E5; Mon, 3 Jan 2000 12:16:46 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup6-46.iptelecom.net.ua [212.9.227.110]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id WAA29137; Mon, 3 Jan 2000 22:19:16 +0200 (EET) Message-ID: <3870F784.2B1E8126@altavista.net> Date: Mon, 03 Jan 2000 21:24:52 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Nicolas Souchu Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG, nsouch@FreeBSD.ORG Subject: Re: HEADS-UP newppbus for beta-testing References: <20000103004910.41467@armor.free.fr> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Souchu wrote: > Hi there! > > FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current > > A major ppbus(4) release is available for beta-testing. Good work! Now plip, which has been broken for ages, works perfectly - no more lockups, spontaneous reboots, panics, etc! To test it I even managed to get X and NFS working over plip line, things which was impossible with oldppbus. Count on my vote to commit it before branch split because IMHO it should be considered as a bugfix rather that a new feature. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 12:18:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 3A2D5154A7 for ; Mon, 3 Jan 2000 12:18:05 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id PAA17118 for ; Mon, 3 Jan 2000 15:18:04 -0500 (EST) Date: Mon, 3 Jan 2000 15:18:04 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: hackers@FreeBSD.ORG Subject: Re: microtime vs getmicrotime 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, 3 Jan 2000, Kelly Yancey wrote: > > Scanning through sys/kern_clock.c it looks like getmicrotime is > preferable to microtime since only getmicrotime accounts for > tco_method (set via the kern.timecounter sysctl). The same is true with > getnanotime vs nanotime, etc. > However, I've noticed a good bit of kernel code is still calling > microtime and nanotime rather than the get- versions: > Replying to myself :) Once I got some food in me, I was able to think about this a little more clearly. The best I can figure is that anything which requires accurate timing calls {micro,nano}time to actually access the timecounter and get the current time. However, any interfaces which either a) don't care how accurate the timing is or b) are just passing the information on to userland call get{micro,nano}time instead to that the kern.timecounter sysctl preference is enforced. Is this correct? Thanks, Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 12:28:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news.IAEhv.nl (news.IAE.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id 7973F15130 for ; Mon, 3 Jan 2000 12:28:28 -0800 (PST) (envelope-from Arjan.deVet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id VAA21399 for hackers@freebsd.org; Mon, 3 Jan 2000 21:28:27 +0100 (MET) Received: by adv.iae.nl (Postfix, from userid 100) id 8BC2822C5; Mon, 3 Jan 2000 21:27:58 +0100 (CET) To: hackers@freebsd.org Subject: Re: AIO was Re: Kernel threads X-Newsgroups: list.freebsd.hackers In-Reply-To: References: <007401bf561c$6ff51930$1e80000a@avantgo.com> Organization: Internet Access Eindhoven, the Netherlands Cc: Message-Id: <20000103202758.8BC2822C5@adv.iae.nl> Date: Mon, 3 Jan 2000 21:27:58 +0100 (CET) From: Arjan.deVet@adv.iae.nl (Arjan de Vet) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >> The best fix I've thought of thus far (other than async I/O, which I >> understand isn't ready for prime time) would be to have a number of kernel > >Speaking of AIO, which I would really like to use if possible, how >actively maintained is it? The copyright on vfs_aio.c is 1997, suggesting >to me that John Dyson has moved onto other things. Yep, that's right. Quite recently Christopher Sedore has done some work on vfs_aio.c, to make it work better with sockets and he also added a very useful aio_waitcomplete system call which returns the first aiocb (AIO control block) from the 'completed' queue. I would be nice if these patches could be added to FreeBSD-current. About AIO not ready for prime time: I did some experiments recently by throwing up to 256 aio requests on one fd (a raw disk device) into the system and it worked without any problems. The only time I got a panic was when (I think) I had a negative aiocb->offset (I still need to reproduce this). See http://www.iae.nl/users/devet/freebsd/aio/ for my aiotest.c program. I'm thinking about using AIO for a faster Squid file system by using raw disk devices instead of UFS which has too much overhead for Squid. Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 13:29:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 5741F151C0 for ; Mon, 3 Jan 2000 13:29:11 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id 517B524D70; Mon, 3 Jan 2000 16:29:10 -0500 (EST) Received: by osaka.louisville.edu (Postfix, from userid 15) id 1223D18605; Mon, 3 Jan 2000 16:29:06 -0500 (EST) Date: Mon, 3 Jan 2000 16:29:06 -0500 From: Keith Stevenson To: freebsd-hackers@freebsd.org Cc: dillon@apollo.backplane.com Subject: Repeated softupdates panics in 3.3-STABLE Message-ID: <20000103162905.A13617@osaka.louisville.edu> 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 (Matt: I've cc'd you since you seem to have taken an interest in softupdates. If you would prefer that I not cc you directly in the future, let me know and it won't happen again.) I'm posting to -hackers, since my last post of this type to stable didn't seem to attract any attention. It looks like I may have spoken too soon when I mentioned that I had no problems with softupdates on my postfix based mail server. I have now had two panics in the last month with a panicstr of "softdep_lock: locking against myself". I thought that the first one might have been a fluke until it repeated itself today. Here's a transcript of the debugging session. I'm a novice at reading these, so expert guidance is appreciated. (I've followed the example from the handbook.) (kgdb) symbol-file kernel.debug Reading symbols from kernel.debug...done. (kgdb) exec-file kernel.1 (kgdb) core-file vmcore.1 IdlePTD 2617344 initial pcb at 219920 panicstr: softdep_lock: locking against myself panic messages: --- panic: softdep_fsync: pending ops syncing disks... panic: softdep_lock: locking against myself dumping to dev 20001, offset 4096 dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xc0145e0c in at_shutdown ( function=0xc01f87ac <__set_sysuninit_set_sym_M_DIRREM_uninit_sys_uninit+4>, arg=0xc0b18900, queue=-969667152) at ../../kern/kern_shutdown.c:446 #2 0xc019ef55 in acquire_lock (lk=0xc020ee84) at ../../ufs/ffs/ffs_softdep.c:266 #3 0xc01a2909 in softdep_update_inodeblock (ip=0xc0b18900, bp=0xc34934b0, waitfor=0) at ../../ufs/ffs/ffs_softdep.c:3447 #4 0xc019dfdc in ffs_update (vp=0xc61ff700, waitfor=0) at ../../ufs/ffs/ffs_inode.c:105 #5 0xc01a7436 in ffs_fsync (ap=0xc6340e68) at ../../ufs/ffs/ffs_vnops.c:258 #6 0xc01a580f in ffs_sync (mp=0xc0b06e00, waitfor=2, cred=0xc0752300, p=0xc022d468) at vnode_if.h:499 #7 0xc016cb8b in sync (p=0xc022d468, uap=0x0) at ../../kern/vfs_syscalls.c:549 #8 0xc01459cd in boot (howto=256) at ../../kern/kern_shutdown.c:203 #9 0xc0145e0c in at_shutdown ( function=0xc01f9522 <__set_sysctl__debug_sym_sysctl___debug_rush_requests+2882>, arg=0xc6641480, queue=0) at ../../kern/kern_shutdown.c:446 #10 0xc01a2baa in softdep_fsync (vp=0xc6641480) at ../../ufs/ffs/ffs_softdep.c:3567 #11 0xc016f462 in fsync (p=0xc62a8760, uap=0xc6340f94) at ../../kern/vfs_syscalls.c:2449 #12 0xc01d3a73 in syscall (frame={tf_es = 39, tf_ds = -1078001625, tf_edi = -1077945532, tf_esi = 0, tf_ebp = -1077945772, tf_isp = -969666588, tf_ebx = 134683656, tf_edx = 35, tf_ecx = 35, tf_eax = 95, tf_trapno = 7, tf_err = 2, tf_eip = 671813520, tf_cs = 31, tf_eflags = 582, tf_esp = -1077945788, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #13 0xc01c9fac in Xint0x80_syscall () #14 0x804e9d0 in ?? () #15 0x8049f65 in ?? () #16 0x804be69 in ?? () #17 0x804bf7a in ?? () #18 0x8052ba9 in ?? () #19 0x804c6eb in ?? () #20 0x804a276 in ?? () #21 0x8049d65 in ?? () Other system information ------------------------ # uname -a FreeBSD erouter0.it-datacntr.louisville.edu 3.3-STABLE FreeBSD 3.3-STABLE #1: Mon Sep 27 14:32:45 EDT 1999 syskts@erouter0.it-datacntr.louisville.edu:/usr/src/sys/compile/EROUTER i386 Softupdates are enabled on /var /and /var/log. (They are separate filesystems) Drives are IDE. /dev/wd2s1e 1016303 279793 655206 30% /var /dev/wd0s1f 1016303 90322 844677 10% /var/log Thanks for any guidance. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 13:47:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 03D3115148 for ; Mon, 3 Jan 2000 13:47:48 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id QAA18968 for ; Mon, 3 Jan 2000 16:47:47 -0500 (EST) Date: Mon, 3 Jan 2000 16:47:47 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: hackers@freebsd.org Subject: minor patch to fix inconsistency in getnano{up,}time declaration 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 Attached is a minor patch to sys/sys/time.h which fixes a mismatch between the declaration and definition of the getnano{up,}time routines. The mismatch definately doesn't hurt anything. I only noticed because I am trying to write man pages for this family of routines. Anyway, if a committed is feeling bored (yeah right :) ), here is a quickie patch to sync the two... Thanks, Kelly --- time.h.orig Mon Jan 3 16:40:33 2000 +++ time.h Mon Jan 3 16:40:57 2000 @@ -267,8 +267,8 @@ void getmicrouptime __P((struct timeval *tv)); void getmicrotime __P((struct timeval *tv)); -void getnanouptime __P((struct timespec *tv)); -void getnanotime __P((struct timespec *tv)); +void getnanouptime __P((struct timespec *tsp)); +void getnanotime __P((struct timespec *tsp)); void init_timecounter __P((struct timecounter *tc)); int itimerdecr __P((struct itimerval *itp, int usec)); int itimerfix __P((struct timeval *tv)); -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 14:16:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id 6F4D014DE2 for ; Mon, 3 Jan 2000 14:16:13 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 98176 invoked by uid 1010); 3 Jan 2000 22:05:55 -0000 Date: Mon, 3 Jan 2000 22:05:55 +0000 From: George Cox To: freebsd-hackers@freebsd.org Subject: Re: Repeated softupdates panics in 3.3-STABLE Message-ID: <20000103220555.C97693@extremis.demon.co.uk> References: <20000103162905.A13617@osaka.louisville.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <20000103162905.A13617@osaka.louisville.edu>; from k.stevenson@louisville.edu on Mon, Jan 03, 2000 at 04:29:06PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 03/01 16:29, Keith Stevenson wrote: > It looks like I may have spoken too soon when I mentioned that I had no > problems with softupdates on my postfix based mail server. I have now had > two panics in the last month with a panicstr of "softdep_lock: locking > against myself". I thought that the first one might have been a fluke until > it repeated itself today. I too have seen this "softdep_lock: locking against myself" panic on a Postfix server. I was able to trigger it I think maybe twice by issuing a 'postfix flush' command. :-/ This _was_ some months ago, when there was the odd commit to the softupdates code going in, which suggests it's kind of a long standing bug. :-( (yes I know this isn't particularly useful -- I'm just trying to say "ME TOO!!!" in a quasi-intelligent way. :-) ) best; gjvc -- [gjvc] \\ "...limited as I am by the sequential nature \\ of human communication." -- E. W. Dijkstra To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 14:21:23 2000 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 639E214EE5 for ; Mon, 3 Jan 2000 14:21:21 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA09560; Mon, 3 Jan 2000 14:21:18 -0800 (PST) (envelope-from dillon) Date: Mon, 3 Jan 2000 14:21:18 -0800 (PST) From: Matthew Dillon Message-Id: <200001032221.OAA09560@apollo.backplane.com> To: George Cox Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Repeated softupdates panics in 3.3-STABLE References: <20000103162905.A13617@osaka.louisville.edu> <20000103220555.C97693@extremis.demon.co.uk> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On 03/01 16:29, Keith Stevenson wrote: : :> It looks like I may have spoken too soon when I mentioned that I had no :> problems with softupdates on my postfix based mail server. I have now had :> two panics in the last month with a panicstr of "softdep_lock: locking :> against myself". I thought that the first one might have been a fluke until :> it repeated itself today. : :I too have seen this "softdep_lock: locking against myself" panic on a Postfix :server. I was able to trigger it I think maybe twice by issuing a 'postfix :flush' command. :-/ This _was_ some months ago, when there was the odd commit :to the softupdates code going in, which suggests it's kind of a long standing :bug. :-( Well, in Keith's case the locking-against-myself panic is not the cause, but the effect of the 'softdep_fsync: pending ops' panic that occured just before it. I've never seeing a pending ops panic before, this is going to be one for Kirk to track down. Be sure to keep your core dump and your debug kernel. In fact, if you could gzip them both up and make them available to me and Kirk via a hidden ftp or hidden URL I would appreciate it. NOTE! Kernel core dumps often contain sensitive information such as pieces of the password file, do not make your core available to the general lists! -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 Jan 3 14:22:11 2000 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 F2B0414D7F for ; Mon, 3 Jan 2000 14:22:09 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA09581; Mon, 3 Jan 2000 14:22:09 -0800 (PST) (envelope-from dillon) Date: Mon, 3 Jan 2000 14:22:09 -0800 (PST) From: Matthew Dillon Message-Id: <200001032222.OAA09581@apollo.backplane.com> To: Matthew Dillon Cc: George Cox , freebsd-hackers@FreeBSD.ORG Subject: Re: Repeated softupdates panics in 3.3-STABLE References: <20000103162905.A13617@osaka.louisville.edu> <20000103220555.C97693@extremis.demon.co.uk> <200001032221.OAA09560@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Well, in Keith's case the locking-against-myself panic is not the : cause, but the effect of the 'softdep_fsync: pending ops' panic : that occured just before it. : : I've never seeing a pending ops panic before, this is going to be : one for Kirk to track down. Be sure to keep your core dump and : your debug kernel. In fact, if you could gzip them both up and make Note, by 'you' I meant Keith here, not George :-) -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 Jan 3 15:25:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from staff.accessus.net (staff.accessus.net [209.145.151.3]) by hub.freebsd.org (Postfix) with ESMTP id E811A1520E for ; Mon, 3 Jan 2000 15:25:41 -0800 (PST) (envelope-from doogie@staff.accessus.net) Received: by staff.accessus.net with Internet Mail Service (5.5.2650.21) id ; Mon, 3 Jan 2000 17:25:31 -0600 Message-ID: From: Jason Young To: 'Matthew Dillon' , George Cox Cc: freebsd-hackers@FreeBSD.ORG Subject: RE: Repeated softupdates panics in 3.3-STABLE Date: Mon, 3 Jan 2000 17:25:27 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01BF5641.D387C89C" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01BF5641.D387C89C Content-Type: text/plain; charset="iso-8859-1" A "pending ops" panic can be induced in fairly short order by running the SMTP performance tests that come with Postfix. Specifically, run smtpstone/smtp-source running many parallel deliveries into a Postfix mail daemon setup running on the same machine. I had always assumed that this meant softupdates was getting too behind (the test delivers hundreds of mails per second with decent disk setups). I wasn't able to mentally parse the code well enough to confirm that. This is in all 3.x revisions that I've tested, since from back around the time of 3.0-CURRENT's great ELF transition, to 3.3-RELEASE. If somebody's interested, I can create this setup and try to duplicate the problem again. > -----Original Message----- > From: Matthew Dillon [mailto:dillon@apollo.backplane.com] > Sent: Monday, January 03, 2000 4:21 PM > To: George Cox > Cc: freebsd-hackers@FreeBSD.ORG > Subject: Re: Repeated softupdates panics in 3.3-STABLE > > > :On 03/01 16:29, Keith Stevenson wrote: > : > :> It looks like I may have spoken too soon when I mentioned > that I had no > :> problems with softupdates on my postfix based mail server. > I have now had > :> two panics in the last month with a panicstr of > "softdep_lock: locking > :> against myself". I thought that the first one might have > been a fluke until > :> it repeated itself today. > : > :I too have seen this "softdep_lock: locking against myself" > panic on a Postfix > :server. I was able to trigger it I think maybe twice by > issuing a 'postfix > :flush' command. :-/ This _was_ some months ago, when there > was the odd commit > :to the softupdates code going in, which suggests it's kind > of a long standing > :bug. :-( > > Well, in Keith's case the locking-against-myself panic is not the > cause, but the effect of the 'softdep_fsync: pending ops' panic > that occured just before it. > > I've never seeing a pending ops panic before, this is going to be > one for Kirk to track down. Be sure to keep your core dump and > your debug kernel. In fact, if you could gzip them both > up and make > them available to me and Kirk via a hidden ftp or hidden URL I > would appreciate it. NOTE! Kernel core dumps often contain > sensitive information such as pieces of the password file, do not > make your core available to the general lists! > > -Matt > Matthew Dillon > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ------_=_NextPart_001_01BF5641.D387C89C Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable RE: Repeated softupdates panics in 3.3-STABLE

A "pending ops" panic can be induced in = fairly short order by running the SMTP performance tests that come with = Postfix. Specifically, run smtpstone/smtp-source running many parallel = deliveries into a Postfix mail daemon setup running on the same = machine. I had always assumed that this meant softupdates was getting = too behind (the test delivers hundreds of mails per second with decent = disk setups). I wasn't able to mentally parse the code well enough to = confirm that.

This is in all 3.x revisions that I've tested, since = from back around the time of 3.0-CURRENT's great ELF transition, to = 3.3-RELEASE. If somebody's interested, I can create this setup and try = to duplicate the problem again.

> -----Original Message-----
> From: Matthew Dillon [mailto:dillon@apollo.backpla= ne.com]
> Sent: Monday, January 03, 2000 4:21 PM
> To: George Cox
> Cc: freebsd-hackers@FreeBSD.ORG
> Subject: Re: Repeated softupdates panics in = 3.3-STABLE
>
>
> :On 03/01 16:29, Keith Stevenson wrote:
> :
> :> It looks like I may have spoken too soon = when I mentioned
> that I had no
> :> problems with softupdates on my postfix = based mail server.
>  I have now had
> :> two panics in the last month with a = panicstr of
> "softdep_lock: locking
> :> against myself".  I thought = that the first one might have
> been a fluke until
> :> it repeated itself today.
> :
> :I too have seen this "softdep_lock: = locking against myself"
> panic on a Postfix
> :server.  I was able to trigger it I think = maybe twice by
> issuing a 'postfix
> :flush' command. :-/  This _was_ some = months ago, when there
> was the odd commit
> :to the softupdates code going in, which = suggests it's kind
> of a long standing
> :bug. :-(
>
>     Well, in Keith's case = the locking-against-myself panic is not the
>     cause, but the effect = of the 'softdep_fsync: pending ops' panic
>     that occured just = before it.
>
>     I've never seeing a = pending ops panic before, this is going to be
>     one for Kirk to track = down.  Be sure to keep your core dump and
>     your debug = kernel.  In fact, if you could gzip them both
> up and make
>     them available to me = and Kirk via a hidden ftp or hidden URL I
>     would appreciate = it.  NOTE!  Kernel core dumps often contain
>     sensitive information = such as pieces of the password file, do not
>     make your core = available to the general lists!
>
>       =         =         =         =         -Matt
>       =         =         =         =         Matthew Dillon
>       =         =         =         =         = <dillon@backplane.com>
>
>
> To Unsubscribe: send mail to = majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in = the body of the message
>

------_=_NextPart_001_01BF5641.D387C89C-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 17:34:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fysgr387.sn.umu.se (fysgr387.sn.umu.se [130.239.128.239]) by hub.freebsd.org (Postfix) with ESMTP id 845D41504F for ; Mon, 3 Jan 2000 17:34:24 -0800 (PST) (envelope-from saska@fysgr387.sn.umu.se) Received: by fysgr387.sn.umu.se (Postfix, from userid 1000) id 23836A837; Tue, 4 Jan 2000 02:36:48 +0100 (CET) Date: Tue, 4 Jan 2000 02:36:48 +0100 From: Markus Holmberg To: freebsd-hackers@freebsd.org Subject: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000104023648.A43673@fysgr387.sn.umu.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After browsing the archives of this list searching for information on SIGFPE issues in FreeBSD I believe I have learnt the following: From: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=903527+906405+/usr/local/www/db/text/1999/freebsd-hackers/19991226.freebsd-hackers IEEE Std 754-1985 (Section 7, paragraph 1) is: ``The default response to an exception shall be to proceed without a trap.'' (end quote) When checking with a simple C program and fpgetmask() I can confirm that a couple of bits are set by default, which mean they will trap some floating point operations. This is consistent with the older postings that say that default FreeBSD behaviour is *not* conforming with IEEE floating point standards. But when porting software from other platforms this becomes an issue. To my understanding, doing a fpsetmask(0) makes FreeBSD behave conforming to IEEE (i.e. not trapping the exceptions). Question 1: What is the reason for FreeBSD to differ from other platforms and not follow the IEEE standard by default? (Please forgive me if this is an ignorant question.) To avoid cluttering the code with fpsetmask(0)'s, using a compiler option to force IEEE conforming fp behaviour would be desirable. This is where the -mieee-fp parameter for gcc would be handy! Even though compiling with -mieee-fp option, fpgetmask() still returns the mask with several bits set (when I was expecting them all to be turned off). Also two binaries compiled with -mieee-fp and -mno-ieee-fp respectively turn out to be identical (i.e. the flags have no effect). Question 2: Is -mieee-fp option in gcc broken in FreeBSD? Or have I missed something.. In that case I apologize for ignorance and hope someone don't mind clarifying these matters. The direct reason for me asking about this is a FreeBSD-specific bug in Mozilla (that needs help from someone who knows this): http://bugzilla.mozilla.org/show_bug.cgi?id=9967 Feel free to check it out. /Markus -- 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 Mon Jan 3 19:48:30 2000 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 81CC615416 for ; Mon, 3 Jan 2000 19:48:25 -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 TAA61311; Mon, 3 Jan 2000 19:48:14 -0800 (PST) To: freebsd-hackers@FreeBSD.ORG Cc: Markus Holmberg , briano@netscape.com, gatgul@voicenet.com, brendan@mozilla.org, waldemar@netscape.com, daeron@Wit401305.student.utwente.nl, clayton@netscape.com, mccabe@netscape.com Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? In-reply-to: Your message of Tue, 04 Jan 2000 02:36:48 +0100. <20000104023648.A43673@fysgr387.sn.umu.se> Date: Mon, 03 Jan 2000 19:48:14 -0800 Message-ID: <61309.946957694@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000104023648.A43673@fysgr387.sn.umu.se>, Markus Holmberg wrote: >IEEE Std 754-1985 (Section 7, paragraph 1) is: > > ``The default response to an exception shall be to proceed > without a trap.'' > >(end quote) > >When checking with a simple C program and fpgetmask() I can confirm that >a couple of bits are set by default, which mean they will trap some >floating point operations. This is consistent with the older postings that >say that default FreeBSD behaviour is *not* conforming with IEEE floating >point standards. > >But when porting software from other platforms this becomes an issue. To >my understanding, doing a fpsetmask(0) makes FreeBSD behave conforming >to IEEE (i.e. not trapping the exceptions). > >Question 1: What is the reason for FreeBSD to differ from other platforms >and not follow the IEEE standard by default? >(Please forgive me if this is an ignorant question.) No, its a Good Question, and I'd like to know the answer also. >To avoid cluttering the code with fpsetmask(0)'s, using a compiler >option to force IEEE conforming fp behaviour would be desirable. This is >where the -mieee-fp parameter for gcc would be handy! No. This would be an entirely inappropriate use of that specific gcc compiler flag. And in fact, *no* special compiler flags should be necessary in order for a compiled C program to conform to the specific IEEE FP rule quoted above. Please understand that gcc compiler flags, and specifically the -mieee-fp option, are meant, in general, to control what type of code gcc emits. That is to say that the gcc compiler options (except those relating to linking, specification of the output file, etc.) For example, there are some machines (I think it is the x86 CPUs, and also the Alphas) where gcc has a choice, and can either generate code for FP operations that is fast or else code that is 100% IEEE conforming. So for those cases, gcc provides the -mieee-fp option... because gcc's default is to just generate fast code, rather than fully IEEE conformant code. But the problem you are talking about has nothing whatsoever to do what what kind of code gcc generates. It only has to do what what the ``pre- main'' code that you programs get linked with (usually called crt0.o) initialize the machine's IEEE trapping flags to. If the existing crt0.o code... which is usually considered sort-of a part of the C library... is failing to initialize all of the IEEE trapping bit to `off', then this just means that someone needs to go in and fix the crt0.o code so that it properly initializes all those bits to off... in order to fully conform to the IEEE 754 FP standard, and specifically to the rule quoted above. >The direct reason for me asking about this is a FreeBSD-specific bug in >Mozilla (that needs help from someone who knows this): > >http://bugzilla.mozilla.org/show_bug.cgi?id=9967 In that Mozilla bugreport, I see the comments: ]------- Additional Comments From brendan@netscape.com 07/15/99 21:32 ------- ]Cc'ing the real IEEE f.p. experts. I too don't want to see this change go in if ]a platform-specific compiler misfeature that results in gratuitous SIGFPEs can ]be disabled via a command line option. My opinion is that brendan is correct, and that littering the Mozilla code with a bunch of hacky kludges all over the place is *NOT* the Right Way to solve such problems. Not at all. The Right Way to solve this problem is for the Mozilla guys to just slip in the statement: fpsetmask(0); right at the very beginning of their main() function. This should be enough to disable the unrequested FP traps on any and all platforms where you/they might possibly get such traps. As I say, the *ideal* way to solve this problem is for every person who maintains a crt0.o file for any given flavor of UNIX to pay a bit more attention to IEEE 754 and for them to arrange to have all FP traps dis- abled already unpon entry into main(). However even if every maintainer of a crt0.o file in the world reads these woards and goes forth and does that TODAY, Mozilla should still be programmed so that it will avoid crashing and burning even when it is compiled on some version of some platform (e.g. FreeBSD) which is already out on the field today. In short, program defensively. You'll never be sorry. -- rfg P.S. It's been a long time now, and I don't remember for sure any more... too many brain cells cooked in my youth I guess... but I seem to recall that I was the guy who talked Stallman into adding the -mieee-fp option. I just mention it so that you will know that... once upon a time at least... I actually *did* know what I was talking about when it came to IEEE FP stuff. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 20:29: 8 2000 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 5DD2B14CF8 for ; Mon, 3 Jan 2000 20:29:05 -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 UAA61715; Mon, 3 Jan 2000 20:29:00 -0800 (PST) To: root@ihack.net (Charles M. Hannum) Cc: freebsd-hackers@FreeBSD.ORG, Markus Holmberg , briano@netscape.com, gatgul@voicenet.com, brendan@mozilla.org, waldemar@netscape.com, daeron@Wit401305.student.utwente.nl, clayton@netscape.com, mccabe@netscape.com Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? In-reply-to: Your message of 03 Jan 2000 23:19:02 -0500. Date: Mon, 03 Jan 2000 20:29:00 -0800 Message-ID: <61713.946960140@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , you wrote: > >"Ronald F. Guilmette" writes: > >> >Question 1: What is the reason for FreeBSD to differ from other platforms >> >and not follow the IEEE standard by default? >> >(Please forgive me if this is an ignorant question.) >> >> No, its a Good Question, and I'd like to know the answer also. > >That's actually a trick question. When I researched this a few years >ago, I found that *no* system other than NetBSD starts up in an >IEEE-conformant mode. To wit: > >* iBCS2/SCO, SVR4 and FreeBSD leave exceptions unmasked. > >* Linux uses the Intel default control word, which sets extended > precision mode (which is not IEEE conformant). Well, when *I* researched it a few years ago, I seem to recall that about 2/3rds of the systems I tested at that time did in fact properly disable all of the FP traps prior to entry into main(). I think that the commercial/proprietary systems were generally pretty good about doing this, e.g. Solaris, IRIX, HP/UX, DG/UX, DEC/OSF/1, etc. But I think that you are correct that SCO was one of the ones that didn't pass the test. Part of the problem is that the major commercial C/C++ compiler test suites make it a point to *only* test for ANSI/ISO conformance... IEEE 754 confor- mance is outside of their scope as far as they are concerned. The result is that a lot of people never do any serious testing of their C/C++ compilers for IEEE 754 conformance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 21:49:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ns2.globalctg.net (ns2.globalctg.net [202.5.32.6]) by hub.freebsd.org (Postfix) with ESMTP id 54BE714E02 for ; Mon, 3 Jan 2000 21:49:35 -0800 (PST) (envelope-from nestar@globalctg.net) Received: from delivery.globalctg.net (ns1.aob.globalctg.net [202.5.32.5]) by ns2.globalctg.net with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id CG6L8FD3; Tue, 4 Jan 2000 11:47:38 +0600 Received: from globalctg.net [202.5.32.222] by delivery.globalctg.net [202.5.32.10] with SMTP (MDaemon.v2.7.SP5.R) for ; Tue, 04 Jan 2000 11:47:33 +0600 Message-ID: <38718968.6BC565F2@globalctg.net> Date: Tue, 04 Jan 2000 05:47:20 +0000 From: "New Star Service Co." Organization: New Star Service Co. X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.13-7mdk i586) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Hackers Subject: installation help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-MDaemon-Deliver-To: freebsd-hackers@FreeBSD.org X-Return-Path: nestar@globalctg.net Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am complete new in FreeBSD. I collect FreeBSD3.3 two CD's from one of my friend but he not use this OS. So please help me to install FBSD3.3 . Please inform how to make partition and boot. I have 2 harddisk both 6.4 GB. One for Redhat 6.1, SuSE and another harddisk i like to use FreeBSD(FBSD). I like to install (boot)directly from CDROM. please inform how to create partition ? I want to create one partition for FreeBSD(like to complete use 6.4GB) because i'm single user. For your information , i use fdisk to create partition for linux , like this way :- n -> p -> (1-4) -> 1 -> cyl (1-784) -> 1 -> size + 2800 M n -> p -> (1-4) -> 2 -> cyl (358-784) -> 358 -> size +2800M n -> e (1-4) -> 3 -> cyl (715-784) -> 715 -> size 784 [to create extended partition] n -> l -> cyl (715-784) -> 715 -> size 750 n -> l -> cyl (751-784) -> 751 -> size 784 To create swap partition : t -> (1-6) -> 5 -> hexcode 82 To active partition : a -> 1 Please give me your expericence which you apply yourself. Please note, In linux I create two partition because I use 2 linux OS but I like to use FreeBSD complete in 6.4 Gb so please inform how can i create partition complete for FreeBSD. and also please inform how can i boot with FreeBSD boot loader instead of LILO. Please help anybody. waiting prompt reply. satyajit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Mon Jan 3 23: 0:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tomts3-srv.bellnexxia.net (tomts3.bellnexxia.net [209.226.175.141]) by hub.freebsd.org (Postfix) with ESMTP id 7D94814FC8 for ; Mon, 3 Jan 2000 23:00:53 -0800 (PST) (envelope-from hoek@FreeBSD.org) Received: from localhost.nowhere ([206.172.226.236]) by tomts3-srv.bellnexxia.net (InterMail vM.4.01.02.07 201-229-116-107) with ESMTP id <20000104070048.VLIW627.tomts3-srv.bellnexxia.net@localhost.nowhere>; Tue, 4 Jan 2000 02:00:48 -0500 Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id CAA21305; Tue, 4 Jan 2000 02:00:43 -0500 (EST) (envelope-from tim) Date: Tue, 4 Jan 2000 02:00:42 -0500 From: Tim Vanderhoek To: "Ronald F. Guilmette" Cc: "Charles M. Hannum" , freebsd-hackers@FreeBSD.ORG, Markus Holmberg , briano@netscape.com, gatgul@voicenet.com, brendan@mozilla.org, waldemar@netscape.com, daeron@Wit401305.student.utwente.nl, clayton@netscape.com, mccabe@netscape.com Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000104020041.A20965@mad> References: <61713.946960140@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <61713.946960140@monkeys.com>; from Ronald F. Guilmette on Mon, Jan 03, 2000 at 08:29:00PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 03, 2000 at 08:29:00PM -0800, Ronald F. Guilmette wrote: > > >> >Question 1: What is the reason for FreeBSD to differ from other platforms > >> >and not follow the IEEE standard by default? > >> >(Please forgive me if this is an ignorant question.) [...] > >That's actually a trick question. When I researched this a few years > >ago, I found that *no* system other than NetBSD starts up in an > >IEEE-conformant mode. To wit: > > > >* iBCS2/SCO, SVR4 and FreeBSD leave exceptions unmasked. This should be a FAQ. Over time, many people have expressed their preferrence that exceptions be masked by default in FreeBSD. They are not by conscious decision. The situation can be summed by the following quote from bde: "I don't plan to change the exception handling until the other [libm ANSI conformance bugs] are fixed." The short answer is that porting is made easiest by simply calling fpsetmask(0) on FreeBSD. I couldn't find any really good references explaining all the exact details, but... References to two message by bde that are a little more explicit: Message-ID: <199802210421.PAA18491@godzilla.zeta.org.au> Message-ID: <199802210518.QAA20463@godzilla.zeta.org.au> You can use the interface at http://www.FreeBSD.org/search to search for messages by Message-ID. Also, the following PRs are relevant: URL: http://www.FreeBSD.org/cgi/query-pr.cgi?pr=105 URL: http://www.freebsd.org/cgi/query-pr.cgi?pr=229 There are many more references in the archives for the self-motivated. -- Signature withheld by request of author. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 1:37:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.erlangen.netsurf.de (erlangen.netsurf.de [194.163.170.1]) by hub.freebsd.org (Postfix) with ESMTP id 51AED150A6 for ; Tue, 4 Jan 2000 01:37:37 -0800 (PST) (envelope-from d_f0rce@gmx.de) Received: from blade (user-er-u1.erlangen.netsurf.de [194.163.170.161]) by mail.erlangen.netsurf.de (8.9.3/8.9.3) with SMTP id KAA26389; Tue, 4 Jan 2000 10:36:03 +0100 (CET) Message-ID: <002001bf5697$31869fe0$0201a8c0@blade> From: "Steffen Merkel" To: "Martin Cracauer" , , Cc: References: <20000103173027.A61058@cons.org> <20000103184233.B17710@cons.org> Subject: Re: Limited amount of variables in a multithreaded programm? Date: Tue, 4 Jan 2000 10:36:31 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, thanks for all your help again first. As I stated in a previous question, I'v been learning C now for only some weeks. It seems that I started to work on a project that Is far far away from my knowledge :-) On the other hand I don't like learning in small steps. I always try to reach something I'm not capable of yet. I wouldn't bother you (so often) with my silly questions (as Chris Luke said: "This really is C-101 type stuff." :-) ) if you could tell me a book about programming FreeBSD. I have Stevens "Advanced programming..." and Haviland's "Unix System programming" but there is not much about threads in these books. Moreover there is nothing about variable stack sizes in threads. So how can I learn this? For you to know how little my knowledge is, I have to tell you that I've only got a vague image of what a stack is :-( I didn't find anything about stacks in my "C-Beginners Guides". So how could I know of? It would by great if there was something like a freebsd-newbie-programmers mailing list. So I don't have to bother you with my questions. Steffen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 1:48:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 0689A14A24; Tue, 4 Jan 2000 01:48:47 -0800 (PST) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cequrux.com (8.9.3/8.9.3) id LAA04659; Tue, 4 Jan 2000 11:48:23 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 4655; Tue Jan 4 11:48:15 2000 From: Graham Wheeler Reply-To: gram@cequrux.com To: Adam Mackler , freebsd-questions@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: creating bootable CD-ROM Date: Tue, 4 Jan 2000 11:44:21 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <200001021449.JAA10783@barter.dewline.com> In-Reply-To: <200001021449.JAA10783@barter.dewline.com> MIME-Version: 1.0 Message-Id: <00010411481509.10999@eureka.cequrux.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 02 Jan 2000, Adam Mackler wrote: > Hi: > > I have a couple questions related to booting my FreeBSD > system from a CD-ROM: > > First, is "El Torito" the only way to boot from a CD-ROM? It is the only way to have the BIOS boot from CD-ROM. The floppy disk image is necessary as the El Torito mechanism is a way of making the BIOS see the image as a normal boot floppy. > Is there some way to use disklabel to make the ISO9660 > filesystem bootable, so that /boot and /kernel can just > go in the CD-ROM filesystem, rather than being embedded in > the image of a floppy disk? I may be completely wrong here, but I think this is what the boot -C does. By this stage the BIOS part of the boot is passed, and there is no reason why software (like the bootstrap loader) cannot do the necessary tricks to boot from a CD-ROM as though is it a root filesystem. Unfortunately, `man boot' doesn't shed much light here, but I seem to remember booting live filesystem CDs before using boot -C. -- Dr Graham Wheeler E-mail: gram@cequrux.com CEQURUX Technologies Phone: +27(21)423-6065 Firewalls/Virtual Private Networks Fax: +27(21)424-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 3:15:21 2000 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 EFD3A15248 for ; Tue, 4 Jan 2000 03:15:05 -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 MAA09844; Tue, 4 Jan 2000 12:14:59 +0100 (MET) Date: Tue, 4 Jan 2000 12:14:59 +0100 From: Martin Cracauer To: Markus Holmberg Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000104121459.A8959@cons.org> References: <20000104023648.A43673@fysgr387.sn.umu.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000104023648.A43673@fysgr387.sn.umu.se>; from Markus Holmberg on Tue, Jan 04, 2000 at 02:36:48AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <20000104023648.A43673@fysgr387.sn.umu.se>, Markus Holmberg wrote: > The direct reason for me asking about this is a FreeBSD-specific bug in > Mozilla (that needs help from someone who knows this): > > http://bugzilla.mozilla.org/show_bug.cgi?id=9967 This specific example shows why it is sometimes good to have exceptions enabled. The problem in the Mozilla source is that a floating point number that is bigger than MAX_INT is converted to an int. Not a value that is theoretically bigger, the trap happens only when it actually is bigger, and it does in practice. This causes an FPU exception. Not an "overflow" like a normal floating point operation would, but an "invalid operation". Why's that? The normal (float -> float values) "overflow" exception signals that an overflow happened that otherwise would be handled fine by setting the result value to "infinity". If you disabled the exception, the code would be able to work, the result is a value that is correct in its semantics. because floating point numbers have special values for infinity and such. Integers don't. In the integer case (converting a float value > MAX_INT to int) the result will be undefined and in fact nonsense if you disabled the exception. Try it out: The integer result of such a conversion is not the integer value is is nearest to the float value that was converted, it is complete nonsense. Even if it was converted to INT_MAX, it would not be useful. Absulutely unusable. #include #include #include int main(void) { double bla; int foo; fpsetmask(0); bla = (double)INT_MAX + 1.0; foo = bla; printf("Result: %d\n", foo); return 0; } Result: -2147483648 There is no way that an application could to anything useful with an integer value that was converted from a float > MAX_INT, because its value is just unspecified. Hence it is good to trap this and it is a bug in Mozilla, period. The specific code in question may be built in a way that the result is not used anyway (either never or not in the overflow case). In that case (and only then), the code may work correctly. But in that case the (costly) conversion would also be useless and should not have been done in first place. If you disable exceptions in programs, you should at least leave "invalid operation" on. The "softer" traps that run into meaningful results (overflow, division by zero etc.) may be disabled with less care, but the specific case that causes the Mozilla trap should be left enabled. Similar problems exist for FPU stack errors. The i387 CPU has an unformtunate mapping of error causes to sperately maskable exceptions, in many cases it is better to leave them all unmasked so that no serious error may slip through. Search for old posting of Bruce Evans about gcc/libm bugs that may result in traps you want to catch. I think we might discuss lowing the traps so that the softer exceptions are disabled. But most cases where people cry about FreeBSD's behaviour are serious errors like the one in mozilla, so we won't gain much. If you want to change the behaviour system-wide, change __INITIAL_NPXCW__ in src/sys/i386/include/npx.h. 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 Tue Jan 4 4:55:31 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from amsterdam.xnet.is (amsterdam.xnet.is [194.144.122.7]) by hub.freebsd.org (Postfix) with ESMTP id 8E626151C2 for ; Tue, 4 Jan 2000 04:55:29 -0800 (PST) (envelope-from ) Received: by amsterdam.xnet.is with Internet Mail Service (5.5.2650.21) id ; Tue, 4 Jan 2000 12:53:22 -0000 Message-ID: <4088336A5E02D311A67A00A0C93003D150901E@amsterdam.xnet.is> From: System Administrator To: freebsd-hackers@FreeBSD.ORG Subject: Undeliverable: sdf Date: Tue, 4 Jan 2000 12:53:22 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) X-MS-Embedded-Report: Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BF56B2.AE7C5C50" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01BF56B2.AE7C5C50 Content-Type: text/plain; charset="iso-8859-1" Your message To: eoe@lame.xnet.is Subject: sdf Sent: Tue, 4 Jan 2000 12:59:34 -0000 did not reach the following recipient(s): eoe@lame.xnet.is on Tue, 4 Jan 2000 12:53:19 -0000 The recipient name is not recognized The MTS-ID of the original message is: c=IS;a= ;p=xnet.is;l=X0001041253C29YNT9F MSEXCH:IMS:xnet.is:XNET:X 0 (000C05A6) Unknown Recipient ------_=_NextPart_000_01BF56B2.AE7C5C50 Content-Type: message/rfc822 Message-ID: <3.0.6.32.20000104125934.00a26d40@mail.xnet.is> From: Einar To: eoe@lame.xnet.is Subject: sdf Date: Tue, 4 Jan 2000 12:59:34 -0000 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) X-MS-Embedded-Report: Content-Type: text/plain; charset="iso-8859-1" ------_=_NextPart_000_01BF56B2.AE7C5C50-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 6:37:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id ABD0B15265 for ; Tue, 4 Jan 2000 06:37:17 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id JAA33212; Tue, 4 Jan 2000 09:36:59 -0500 (EST) Date: Tue, 4 Jan 2000 09:36:59 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Martin Cracauer Cc: Markus Holmberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? In-Reply-To: <20000104121459.A8959@cons.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > #include > #include > #include > > int main(void) > { > double bla; > int foo; > > fpsetmask(0); > bla = (double)INT_MAX + 1.0; > foo = bla; > > printf("Result: %d\n", foo); > > return 0; > } > > Result: -2147483648 > > Actually, this the same value (INT_MIN = -2147483648) you would get if you just said foo = INT_MAX + 1 since in 2's complement notation INT_MIN = INT_MAX + 1. It definately isn't garbage. Nonetheless, your point is valid, floating point exceptions do exist for a purpose. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 6:49:29 2000 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 9E962152AA for ; Tue, 4 Jan 2000 06:49:25 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id PAA05472; Tue, 4 Jan 2000 15:49:10 +0100 (CET) Date: Tue, 4 Jan 2000 15:49:09 +0100 From: Martin Cracauer To: Kelly Yancey Cc: Martin Cracauer , Markus Holmberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000104154909.A5444@cons.org> References: <20000104121459.A8959@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kbyanc@posi.net on Tue, Jan 04, 2000 at 09:36:59AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Kelly Yancey wrote: > > > > #include > > #include > > #include > > > > int main(void) > > { > > double bla; > > int foo; > > > > fpsetmask(0); > > bla = (double)INT_MAX + 1.0; > > foo = bla; > > > > printf("Result: %d\n", foo); > > > > return 0; > > } > > > > Result: -2147483648 > > > > > > Actually, this the same value (INT_MIN = -2147483648) you would get if > you just said foo = INT_MAX + 1 since in 2's complement notation INT_MIN = > INT_MAX + 1. Try bla = (double)INT_MAX * 13.0; >It definately isn't garbage. No, you're mislead by my example that happens to choose a value combination that *looks* explainable. It in reality the results of float->int conversions without range check are neither explainable nor can you depend on them. They are just garbage when you disabled exceptions. You can draw some conclusions what happens on integer aritmetic overflows (when you know the size of the operands). That is very different from the float->int conversion results, which do not behave in the usual integer overflow manner (although my first example looked like they would). 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 Tue Jan 4 10:44:12 2000 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 F0A3415236 for ; Tue, 4 Jan 2000 10:43:22 -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 125Yuz-0001IA-00 for ; Tue, 04 Jan 2000 19:42:54 +0100 Received: from mauzi (helo=localhost) by aquarius.poli.hu with local-esmtp (Exim 3.12 #1) id 125Ykg-000AXQ-00 for hackers@freebsd.org; Tue, 04 Jan 2000 19:32:14 +0100 Date: Tue, 4 Jan 2000 19:32:13 +0100 (CET) From: Gergely EGERVARY Reply-To: mauzi@poli.hu To: hackers@freebsd.org Subject: [OFFTOPIC] alt. C compiler Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, is there any alternative (non-commercial) C compiler to use, or is gcc the best? I have just upgraded my system to -current w/egcs 2.95.2 and I have several problems with it, especially when using optimizations (-O2 and such) ok I know there's the good old gcc 2.7.2.3 but a good BSD-licensed compiler would be nice =) -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 11: 0:52 2000 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 A54EB153F4 for ; Tue, 4 Jan 2000 11:00:50 -0800 (PST) (envelope-from crandall@matchlogic.com) Received: by houston.matchlogic.com with Internet Mail Service (5.5.2650.21) id ; Tue, 4 Jan 2000 12:00:40 -0700 Message-ID: <64003B21ECCAD11185C500805F31EC0304D97089@houston.matchlogic.com> From: Charles Randall To: hackers@freebsd.org Subject: RE: [OFFTOPIC] alt. C compiler Date: Tue, 4 Jan 2000 12:00:37 -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 lcc and TenDRA are both in available as packages. Charles -----Original Message----- From: Gergely EGERVARY [mailto:mauzi@aquarius.poli.hu] Sent: Tuesday, January 04, 2000 11:32 AM To: hackers@freebsd.org Subject: [OFFTOPIC] alt. C compiler Hi, is there any alternative (non-commercial) C compiler to use, or is gcc the best? I have just upgraded my system to -current w/egcs 2.95.2 and I have several problems with it, especially when using optimizations (-O2 and such) ok I know there's the good old gcc 2.7.2.3 but a good BSD-licensed compiler would be nice =) -- 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 Tue Jan 4 11: 4: 1 2000 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 B2DE914C1C for ; Tue, 4 Jan 2000 11:03:55 -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 LAA18457; Tue, 4 Jan 2000 11:06:17 -0800 Message-Id: <200001041906.LAA18457@screech.weirdnoise.com> X-Mailer: exmh version 2.0.2 To: Gergely EGERVARY Cc: hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-Reply-To: Your message of "Tue, 04 Jan 2000 19:32:13 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jan 2000 11:06:17 -0800 From: Ed Hall Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I have just upgraded my system to -current w/egcs 2.95.2 and I have : several problems with it, especially when using optimizations (-O2 and : such) Have you reported those problems to ? Bugs aren't very likely to get fixed if no one reports them. As for free alternatives--I don't think there are any, especially if you are looking for something "better" than the current GCC. The various free C compilers I've seen over the years have been little better than toys. -Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 11:26:33 2000 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 60AC914DD4 for ; Tue, 4 Jan 2000 11:26:29 -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 OAA28162; Tue, 4 Jan 2000 14:25:51 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Tue, 4 Jan 2000 14:25:51 -0500 (EST) From: Chuck Robey To: Ed Hall Cc: Gergely EGERVARY , hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-Reply-To: <200001041906.LAA18457@screech.weirdnoise.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, 4 Jan 2000, Ed Hall wrote: > : I have just upgraded my system to -current w/egcs 2.95.2 and I have > : several problems with it, especially when using optimizations (-O2 and > : such) > > Have you reported those problems to ? Bugs aren't > very likely to get fixed if no one reports them. > > As for free alternatives--I don't think there are any, especially if > you are looking for something "better" than the current GCC. The > various free C compilers I've seen over the years have been little > better than toys. There are some, but it's very difficult to replace the system compiler. Look in ports/devel. Your given reason, tho, doesn't make too much sense ... first thing, the options have changed, and -O2 doesn't work. I know you don't mean this, but it sounds like you're complaining that you can't use -O2, not that you can't get a specified kind of optimization (which can be addressed). The gcc we have is the best choice presently, else we wouldn't be using it. I want to make it clear, so I'm going to use an extreme example of what I mean, please don't take it wrong; I could very easily give you a small shell wrapper over gcc, that would make -O2 work (it would throw the option away). You obviously don't want that, but it's the only basis of the problem you display. What specific kind of optimization are you looking for? If you ask that, probably your problem can be more directly addressed using our present compiler. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 11:28: 5 2000 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 6FBDF14D78 for ; Tue, 4 Jan 2000 11:27:57 -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 LAA18657; Tue, 4 Jan 2000 11:30:33 -0800 Message-Id: <200001041930.LAA18657@screech.weirdnoise.com> X-Mailer: exmh version 2.0.2 To: Gergely EGERVARY Cc: hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-Reply-To: Your message of "Tue, 04 Jan 2000 11:06:17 PST." <200001041906.LAA18457@screech.weirdnoise.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 04 Jan 2000 11:30:33 -0800 From: Ed Hall Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just so there is no misunderstanding. I wrote: As for free alternatives--I don't think there are any, especially if you are looking for something "better" than the current GCC. The various free C compilers I've seen over the years have been little better than toys. Obviously, compilers like LCC aren't "toys". By "free" I was following your desire for a "BSD-licensed" (or better) compiler. LCC isn't that. If it's "free enough" for you, then go for it. Whether it or some other alternative is "better" *for your application* is up to you to determine. One of the issues with an alternative compiler is that you'll likely need to keep GCC and associated tools around anyway, for ports, kernels, and updates. Probably not a problem, but occasionally multiple tool chains can be a pain. -Ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 11:36:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 4221414D66 for ; Tue, 4 Jan 2000 11:36:19 -0800 (PST) (envelope-from mreimer@vpop.net) Received: from vpop.net (bilbo.vpop.net [216.160.82.65]) by boromir.vpop.net (8.9.1/8.9.1) with ESMTP id LAA11236 for ; Tue, 4 Jan 2000 11:36:18 -0800 (PST) Message-ID: <38724BC2.767E9055@vpop.net> Date: Tue, 04 Jan 2000 11:36:34 -0800 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Porting ether-wake.c from Linux Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone have suggestions on how to port Donald Becker's ether-wake.c from Linux (ftp://cesdis.gsfc.nasa.gov/pub/linux/misc/ether-wake.c)? It's a little utility to send a Magic Packet to wake a machine (i.e., Wake on LAN). I think the trick is being able to specify the ethernet address from userland. ether-wake.c uses Linux's socket type SOCK_PACKET. What's an equivalent way to do this with FreeBSD? Matt /* Note: PF_INET, SOCK_DGRAM, IPPROTO_UDP would allow SIOCGIFHWADDR to work as non-root, but we need SOCK_PACKET to specify the Ethernet destination address. */ if ((s = socket(AF_INET, SOCK_PACKET, SOCK_PACKET)) < 0) { if (errno == EPERM) fprintf(stderr, "ether-wake must run as root\n"); else perror("ether-wake: socket"); if (! debug) return 2; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 11:41:53 2000 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 E589614D6A for ; Tue, 4 Jan 2000 11:41:43 -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 LAA87336 for ; Tue, 4 Jan 2000 11:41:38 -0800 (PST) To: hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of Tue, 04 Jan 2000 11:06:17 -0800. <200001041906.LAA18457@screech.weirdnoise.com> Date: Tue, 04 Jan 2000 11:41:38 -0800 Message-ID: <87334.947014898@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001041906.LAA18457@screech.weirdnoise.com>, Ed Hall wrote: >: I have just upgraded my system to -current w/egcs 2.95.2 and I have >: several problems with it, especially when using optimizations (-O2 and >: such) > >Have you reported those problems to ? Bugs aren't >very likely to get fixed if no one reports them. > >As for free alternatives--I don't think there are any, especially if >you are looking for something "better" than the current GCC. The >various free C compilers I've seen over the years have been little >better than toys. That is *definitely* not true in the case of lcc. lcc is a very well-thought-out compiler. The good news is that lcc is *very* ANSI/ISO conformant. The bad news is that lcc is *very* ANSI/ISO conformant. The implication of the latter statement is that lcc will probably choke on many of the gcc-specific extensions in the various FreeBSD system include files. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 11:53:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from venera.isi.edu (venera.isi.edu [128.9.176.32]) by hub.freebsd.org (Postfix) with ESMTP id 5730A14BC8 for ; Tue, 4 Jan 2000 11:53:43 -0800 (PST) (envelope-from faber@ISI.EDU) Received: from ted.isi.edu (ted.isi.edu [128.9.160.104]) by venera.isi.edu (8.8.7/8.8.6) with ESMTP id LAA01391 for ; Tue, 4 Jan 2000 11:53:37 -0800 (PST) Received: from ted.isi.edu (localhost [127.0.0.1]) by ted.isi.edu (8.9.3/8.9.3) with ESMTP id LAA11428 for ; Tue, 4 Jan 2000 11:53:41 -0800 (PST) (envelope-from faber@ted.isi.edu) Message-Id: <200001041953.LAA11428@ted.isi.edu> X-Mailer: exmh version 2.1.0 04/14/1999 To: freebsd-hackers@freebsd.org Subject: Someone should close kern/11222 X-Url: http://www.isi.edu/~faber Date: Tue, 04 Jan 2000 11:53:41 -0800 From: Ted Faber Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I noticed that the behavior that prompted me to submit kern/11222 (spurious fscks on when an mfs file system was in use at boot time) disappeared under 3.3-RELEASE, and today I finally had time to check the CVS logs to see what happened. It looks to me like Andrew Gallatin's patch to kern_shutdown.c (1.41->1.42) did the trick. I think his fix allows an mfs that is backed to a local disk file to wind up as inconsistent after a reboot, but I don't think that's a big issue. At any rate, if someone wants to clear one more bug report, as the submitter, I'd be happy to call it closed. - ---------------------------------------------------------------------- Ted Faber faber@isi.edu USC/ISI Computer Scientist http://www.isi.edu/~faber (310) 822-1511 x190 PGP Keys: http://www.isi.edu/~faber/pubkeys.asc -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use Charset: noconv iQA/AwUBOHJPxWlM93/mX/l7EQKJegCfTHHRlIC5KTYuAPxoyJT20sAhrSUAn1bB lYCKpQr5Q8Cd5MRlMjoMgtDN =YoPe -----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 Tue Jan 4 11:55:53 2000 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 B4B6014C5A for ; Tue, 4 Jan 2000 11:55:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA37840; Tue, 4 Jan 2000 11:55:50 -0800 (PST) (envelope-from dillon) Date: Tue, 4 Jan 2000 11:55:50 -0800 (PST) From: Matthew Dillon Message-Id: <200001041955.LAA37840@apollo.backplane.com> To: Ted Faber Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Someone should close kern/11222 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I noticed that the behavior that prompted me to submit kern/11222 :(spurious fscks on when an mfs file system was in use at boot time) :disappeared under 3.3-RELEASE, and today I finally had time to check :the CVS logs to see what happened. It looks to me like Andrew :Gallatin's patch to kern_shutdown.c (1.41->1.42) did the trick. I :think his fix allows an mfs that is backed to a local disk file to :wind up as inconsistent after a reboot, but I don't think that's a big :issue. : :At any rate, if someone wants to clear one more bug report, as the :submitter, I'd be happy to call it closed. Done! -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 12: 2:11 2000 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 AB46C14DED for ; Tue, 4 Jan 2000 12:02:05 -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 MAA87504 for ; Tue, 4 Jan 2000 12:02:04 -0800 (PST) To: hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of Tue, 04 Jan 2000 11:30:33 -0800. <200001041930.LAA18657@screech.weirdnoise.com> Date: Tue, 04 Jan 2000 12:02:04 -0800 Message-ID: <87502.947016124@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001041930.LAA18657@screech.weirdnoise.com>, Ed Hall wrote: >One of the issues with an alternative compiler is that you'll likely need >to keep GCC and associated tools around anyway, for ports, kernels, and >updates. Probably not a problem, but occasionally multiple tool chains >can be a pain. Make that a ``major pain''. As I mentioned, `a compiler', all by itself, is generally not what people who ask for `a compiler' want. Almost without exception, they also want a full set of _compatible_ system include files, a _compatible_ set of libraries, and usually also a _compatible_ source-level debugger. Even though I haven't done this stuff for awhile, I still get calls on occasion from people who want to contract me to do ``a GCC port'' to some new processor they are building. More than 90% of the time, they are under the impression that this is trivial 2 month job that any grad student could do... and in a way, they are correct. When they ask me for a quote, I ask them if the want a set of compatible header files, a compatible set of libraries, and a compatible debugger too. Typically, they tell me that they will have to check with someone else about these things, and then I never hear from them again. I attribute this to their realization that (a) there is a big difference between a `compiler' and a complete `compilation system' and (b) that they really want a complete compilation system and (c) they can't actually afford a complete compilation system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 12:25:19 2000 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 D4F7214F22 for ; Tue, 4 Jan 2000 12:25: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 MAA87634 for ; Tue, 4 Jan 2000 12:25:15 -0800 (PST) To: freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? In-reply-to: Your message of Tue, 04 Jan 2000 12:14:59 +0100. <20000104121459.A8959@cons.org> Date: Tue, 04 Jan 2000 12:25:15 -0800 Message-ID: <87632.947017515@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000104121459.A8959@cons.org>, Martin Cracauer wrote: >Hence it is good to trap this and it is a bug in Mozilla, period. >... >I think we might discuss lowing the traps so that the softer >exceptions are disabled. But most cases where people cry about >FreeBSD's behaviour are serious errors like the one in mozilla, so we >won't gain much. I agree that it appears that the Mozilla code had a serious bug/flaw, and that having the FP traps enabled caused that fact to become apparent. But the issue for me is still one of standards conformance. Regardless of how helpful enabled FP traps may be, on occasion, for certain programs and/or certain programmers, the IEEE 754 standard is pretty darn clear and unambiguous regarding what the default setting should be, i.e. all traps disabled. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 13: 3: 5 2000 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 144FC14CF6 for ; Tue, 4 Jan 2000 13:02:56 -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 QAA06130; Tue, 4 Jan 2000 16:06:56 -0500 From: Bill Paul Message-Id: <200001042106.QAA06130@skynet.ctr.columbia.edu> Subject: Re: Porting ether-wake.c from Linux To: mreimer@vpop.net (Matthew Reimer) Date: Tue, 4 Jan 100 16:06:54 -0500 (EST) Cc: hackers@freebsd.org In-Reply-To: <38724BC2.767E9055@vpop.net> from "Matthew Reimer" at Jan 4, 0 11:36:34 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1616 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 Reimer had to walk into mine and say: > Does anyone have suggestions on how to port Donald Becker's ether-wake.c > from Linux (ftp://cesdis.gsfc.nasa.gov/pub/linux/misc/ether-wake.c)? > It's a little utility to send a Magic Packet to wake a machine (i.e., > Wake on LAN). > > I think the trick is being able to specify the ethernet address from > userland. ether-wake.c uses Linux's socket type SOCK_PACKET. What's an > equivalent way to do this with FreeBSD? BPF. Yes, you can write to BPF descriptors too, that's how rarpd works. (No, SOCK_RAW won't work: it doesn't let you specify the ethernet frame header, only the IP/TCP/UDP headers.) Now, if you want to not only send raw ethernet frames but also send them with arbitrary origin addresses (i.e. an address other than the host's actual station address), then you need to use the magic pseudo_AF_HDRCMPLT flag. (Uhm... though I don't remember how.) It's not clear if you need this or not (I don't think you do), but if you do, now you know. -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 Jan 4 13: 3:42 2000 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 134A914D5E for ; Tue, 4 Jan 2000 13:03:37 -0800 (PST) (envelope-from kurto@bootp.sls.usu.edu) Received: (from root@localhost) by bootp.sls.usu.edu (8.9.3/8.9.3) id OAA19991; Tue, 4 Jan 2000 14:12:20 -0700 (MST) (envelope-from kurto) Date: Tue, 4 Jan 2000 14:12:20 -0700 (MST) From: Kurt Olsen Message-Id: <200001042112.OAA19991@bootp.sls.usu.edu> To: freebsd-hackers@FreeBSD.ORG, mreimer@vpop.net Subject: Re: Porting ether-wake.c from Linux In-Reply-To: <38724BC2.767E9055@vpop.net> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've not looked at ether-wake, but I use the attached program to wake up machines. It's not very fancy, but it does work for me. The limitation that an ARP entry for the destination machine is somewhat annoying, but not insurmountable. As you can see, it uses UDP packets instead of constructing raw packets to be sent. Kurt Olsen kurto@bootp.sls.usu.edu --- /* * the wakie-wakie program */ #include #include #include #include #define BUF_LEN 256 void fatal_error(char *message) { fprintf(stderr, "%s", message); exit(1); } void parse(char *addr_in, u_int32_t *addr_out) { int i,j,k; j = 0; for (i = 0; i < 50 && addr_in[i] != '\0'; i++) { if (addr_in[i] == '.') j++; } if (j != 3) fatal_error("Need four octets in ip address.\n"); *addr_out = 0; for (j = 0, i = 0; i < 4; i++) { k = atoi(&addr_in[j]); if (k < 0 || k > 255) fatal_error("Individual octets in ip address must be in the range 0-255.\n"); *addr_out = *addr_out * 256 + k; while (i < 3 && addr_in[j] != '.') j++; j++; } *addr_out = htonl(*addr_out); } int main(int argc, char **argv) { char buf[BUF_LEN]; int i,j,k,l,m; int thesock; struct sockaddr_in to; memset (buf, 0, BUF_LEN); if (argc < 3 || ((argc-1)&0x1) == 1) { fprintf(stderr, "Need ip and ethernet address pairs.\n"); fprintf(stderr, "\t%s [ ...]\n", *argv); exit(1); } for (m = 1; m < argc; m+=2, argv+=2) { thesock = socket(AF_INET, SOCK_DGRAM, 0); if (thesock < 0) fatal_error("Couldn't make a socket.\n"); if (strlen(*(argv+2)) != 12) fatal_error("Ethernet addresses require 12 digits.\n"); buf[0] = 0xff; buf[1] = 0xff; buf[2] = 0xff; buf[3] = 0xff; buf[4] = 0xff; buf[5] = 0xff; for (i = 1; i < 17; i++) { for (j = 0; j < 6; j++) { k = *(*(argv+2)+j*2); if (k >= 'a' && k <= 'f') k -= ('a'-'A'); l = *(*(argv+2)+j*2+1); if (l >= 'a' && l <= 'f') l -= ('a'-'A'); k -= '0'; if (k > 9) k -= 7; l -= '0'; if (l > 9) l -= 7; k = k * 16 + l; buf[j+i*6] = k; } } to.sin_len = sizeof(to); to.sin_family = AF_INET; to.sin_port = 5432; parse(*(argv+1), &(to.sin_addr.s_addr)); if (sendto(thesock,&buf,BUF_LEN,0,(struct sockaddr *)&to,sizeof(to)) < 0) fatal_error("Couldn't send UDP packet.\n"); close(thesock); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 13:41:17 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 4617014D60 for ; Tue, 4 Jan 2000 13:41:13 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id IAA08587; Wed, 5 Jan 2000 08:40:50 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200001042140.IAA08587@mycenae.ilion.eu.org> To: mauzi@poli.hu Cc: hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of "Tue, 04 Jan 2000 19:32:13 BST." Date: Wed, 05 Jan 2000 08:40:50 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > is there any alternative (non-commercial) C compiler to use, or is gcc the > best? > > I have just upgraded my system to -current w/egcs 2.95.2 and I have > several problems with it, especially when using optimizations (-O2 and > such) > > ok I know there's the good old gcc 2.7.2.3 but a good BSD-licensed > compiler would be nice =) Check out TenDRA in the ports tree. Unfortunately, most ppl tend to use GCC extensions a lot, so you won't be able to replace gcc, but TenDRA certainly is a solid alternative. Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 13:53:13 2000 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 4B3BF14A2C for ; Tue, 4 Jan 2000 13:53:09 -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 QAA28657; Tue, 4 Jan 2000 16:52:12 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Tue, 4 Jan 2000 16:52:12 -0500 (EST) From: Chuck Robey To: Patryk Zadarnowski Cc: mauzi@poli.hu, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-Reply-To: <200001042140.IAA08587@mycenae.ilion.eu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 5 Jan 2000, Patryk Zadarnowski wrote: > > Hi, > > > > is there any alternative (non-commercial) C compiler to use, or is gcc the > > best? > > > > I have just upgraded my system to -current w/egcs 2.95.2 and I have > > several problems with it, especially when using optimizations (-O2 and > > such) > > > > ok I know there's the good old gcc 2.7.2.3 but a good BSD-licensed > > compiler would be nice =) > > Check out TenDRA in the ports tree. Unfortunately, most ppl tend to > use GCC extensions a lot, so you won't be able to replace gcc, but > TenDRA certainly is a solid alternative. With the understanding that using Tendra just for the kernel will be painful, but (if you're determined) doable. If you want it for building world, you better make prior reservations at the local mental health clinic, because YOU WILL NEED IT before you get that done. > > Pat. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, New Year's Resolution: I | electronics, communications, and will not sphroxify gullible| signal processing. people into looking up | I run picnic.mat.net: FreeBSD-current(i386) and fictitious words in the | jaunt.mat.net : FreeBSD-current(Alpha)| dictionary. | ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 14:11:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id 22AF014D2E for ; Tue, 4 Jan 2000 14:10:48 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 97851 invoked by uid 1001); 4 Jan 2000 22:10:39 +0000 (GMT) To: Gerard Roudier , freebsd-hackers@freebsd.org Cc: anders.odberg@usit.uio.no, eivind@yes.no Subject: SYM driver saves the day (where NCR driver crashes) From: sthaug@nethelp.no X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 04 Jan 2000 23:10:39 +0100 Message-ID: <97847.947023839@verdi.nethelp.no> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We have a News server running on Compaq Proliant 3000 hardware, with NCR/Symbios 875 based SCSI controllers. This machine ran extremely stable (but using only one processor) on FreeBSD-2.2.8. Due to the News server, this machine sees reasonably heavy disk and network traffic. On FreeBSD 3.x we have been able to use both processors, but the system has never been stable. We've typically had crashes about once a week. We have suspected the problem described in the recent "PCI DMA lockups in 3.2 (3.3 maybe?)" thread, > 1) Random crashes in FXP interrupt or low-level IP code. Something is > clobbering the kernel stack--possibly the NCR driver, since using an > Adaptec made the problem stop, as did a backport of the CAM driver > Peter Wemm tried. This was on an N440BX, which is becoming quite > common in server applications. Other installations are apparantly > seeing the same problem on this hardware. but have never been able to verify this. Below are included parts of some kernel backtraces to show where it crashes. Anyway, we recently switched to the SYM driver (version 0.12.0). The machine has now been up for 16 days without a single crash, and we're very optimistic that the SYM driver has cured the problem. Kudos and thanks to Gerard Roudier! Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- crash 0,2,5: #1 0xc0144299 in panic #2 0xc015ac7e in m_copym #3 0xc019286a in tcp_output #4 0xc0194106 in tcp_usr_send #5 0xc015c4b2 in sosend #6 0xc01525dc in soo_write #7 0xc014f46a in dofilewrite #8 0xc014f373 in write #9 0xc021f39b in syscall crash 1,3,4: #1 0xc0144299 in panic #2 0xc015dfe0 in sbdrop #3 0xc015df69 in sbflush #4 0xc0194707 in tcp_disconnect #5 0xc0193ee6 in tcp_usr_disconnect #6 0xc015bf68 in sodisconnect #7 0xc015bd9e in soclose #8 0xc01527ab in soo_close #9 0xc013cf1c in closef #10 0xc013c56d in close #11 0xc021f39b in syscall crash 6 (starts with the same write/dofilewrite sequence as 0,2,5): #1 0xc0144299 in panic #2 0xc015ac7e in m_copym #3 0xc019286a in tcp_output #4 0xc0191ae8 in tcp_input #5 0xc018d07c in ip_input #6 0xc018d0db in ipintr #7 0xc020fe85 in swi_net_next () #8 0xc0226b94 in splx #9 0xc021d86f in pmap_clear_modify #10 0xc01f8775 in vm_page_set_validclean #11 0xc01642a0 in vfs_page_set_valid #12 0xc0164423 in vfs_clean_pages #13 0xc0161fbe in bdwrite #14 0xc0165ce0 in cluster_write #15 0xc01e656b in ffs_write #16 0xc016f572 in vn_write #17 0xc014f46a in dofilewrite #18 0xc014f373 in write #19 0xc021f39b in syscall crash 7 (similar to 0,2,5 followed by reboot and a new crash): #1 0xc0144299 in panic #2 0xc021f120 in trap_fatal #3 0xc021ed9b in trap_pfault #4 0xc021e9fa in trap #5 0xc01cffcc in fxp_add_rfabuf #6 0xc01cf410 in fxp_intr #7 0xc0137261 in intr_mux #8 0xc0226b94 in splx #9 0xc0163233 in getblk #10 0xc01e588e in ffs_sbupdate #11 0xc01e5494 in ffs_sync #12 0xc016b4e7 in sync #13 0xc0143e11 in boot #14 0xc0144299 in panic #15 0xc021f120 in trap_fatal #16 0xc021ed9b in trap_pfault #17 0xc021e9fa in trap #18 0xc015c362 in sosend #19 0xc01525dc in soo_write #20 0xc014f46a in dofilewrite #21 0xc014f373 in write #22 0xc021f39b in syscall crash 8 (similar to 0,2,5 followed by reboot and a new crash): #1 0xc0144299 in panic #2 0xc021f120 in trap_fatal #3 0xc021ed9b in trap_pfault #4 0xc021e9fa in trap #5 0xc01cffcc in fxp_add_rfabuf #6 0xc01cf410 in fxp_intr #7 0xc0137261 in intr_mux #8 0xc0226b94 in splx #9 0xc0163233 in getblk #10 0xc0161bad in bread #11 0xc01dd924 in ffs_update #12 0xc01e6fae in ffs_fsync #13 0xc01e5342 in ffs_sync #14 0xc016b4e7 in sync #15 0xc0143e11 in boot #16 0xc0144299 in panic #17 0xc021f120 in trap_fatal #18 0xc021ed9b in trap_pfault #19 0xc021e9fa in trap #20 0xc015c362 in sosend #21 0xc01525dc in soo_write #22 0xc014f46a in dofilewrite #23 0xc014f373 in write #24 0xc021f39b in syscall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 14:27:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id 915491509D for ; Tue, 4 Jan 2000 14:27:31 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id JAA08970; Wed, 5 Jan 2000 09:27:03 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200001042227.JAA08970@mycenae.ilion.eu.org> To: Chuck Robey Cc: mauzi@poli.hu, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of "Tue, 04 Jan 2000 16:52:12 CDT." Date: Wed, 05 Jan 2000 09:27:01 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, 5 Jan 2000, Patryk Zadarnowski wrote: > > > > Hi, > > > > > > is there any alternative (non-commercial) C compiler to use, or is gcc the > > > best? > > > > > > I have just upgraded my system to -current w/egcs 2.95.2 and I have > > > several problems with it, especially when using optimizations (-O2 and > > > such) > > > > > > ok I know there's the good old gcc 2.7.2.3 but a good BSD-licensed > > > compiler would be nice =) > > > > Check out TenDRA in the ports tree. Unfortunately, most ppl tend to > > use GCC extensions a lot, so you won't be able to replace gcc, but > > TenDRA certainly is a solid alternative. > > With the understanding that using Tendra just for the kernel will be > painful, but (if you're determined) doable. If you want it for building > world, you better make prior reservations at the local mental health > clinic, because YOU WILL NEED IT before you get that done. Certainly, although it's still probably the only trully-free C compiler around, and definitely the only more-or-less-free ISO C++ compiler. If anyone is interested, the main TenDRA web site has been down for a while, so I've set up a mirror at http://siliconbreeze.com/TenDRA/. Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 14:34: 8 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from paradox.nexuslabs.com (cc718001-a.vron1.nj.home.com [24.11.70.21]) by hub.freebsd.org (Postfix) with ESMTP id B450A14D47 for ; Tue, 4 Jan 2000 14:33:51 -0800 (PST) (envelope-from cyouse@paradox.nexuslabs.com) Received: from localhost (cyouse@localhost) by paradox.nexuslabs.com (8.9.3/8.9.3) with ESMTP id WAA89492; Tue, 4 Jan 2000 22:56:15 -0500 (EST) (envelope-from cyouse@paradox.nexuslabs.com) Date: Tue, 4 Jan 2000 22:56:15 -0500 (EST) From: Charles Youse To: mauzi@poli.hu Cc: hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler 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 While I wasn't planning to say anything for some time, I am working on a BSD-licensed aggressively optimizing C compiler. I don't expect it to be ready for another 6 months, though. Chuck On Tue, 4 Jan 2000, Gergely EGERVARY wrote: > Hi, > > is there any alternative (non-commercial) C compiler to use, or is gcc the > best? > > I have just upgraded my system to -current w/egcs 2.95.2 and I have > several problems with it, especially when using optimizations (-O2 and > such) > > ok I know there's the good old gcc 2.7.2.3 but a good BSD-licensed > compiler would be nice =) > > -- 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 Tue Jan 4 19:40:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web1901.mail.yahoo.com (web1901.mail.yahoo.com [128.11.23.50]) by hub.freebsd.org (Postfix) with SMTP id 74A5C153DE for ; Tue, 4 Jan 2000 19:40:38 -0800 (PST) (envelope-from manhtho@yahoo.com) Received: (qmail 23851 invoked by uid 60001); 5 Jan 2000 03:40:38 -0000 Message-ID: <20000105034037.23849.qmail@web1901.mail.yahoo.com> Received: from [202.167.121.197] by web1901.mail.yahoo.com; Tue, 04 Jan 2000 19:40:37 PST Date: Tue, 4 Jan 2000 19:40:37 -0800 (PST) From: Nguyen Manh Tho To: FreeBSD-Questions Cc: FreeBSD-Hackers MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear all FreeBSD experts, On Tue, 28 Dec 1999, when answering about converting mailling system from Turbo Linux to Free BSD reserving all accounts and data, Mr. Gianmarco Giovannelli wrote: >As I said these are the step necessary (as I think) to >convert a linux box >in a FreeBSD one... ----> begin <---- >The conversion from Linux to FreeBSD is quite >simple... >As I asked a few hours ago in this list you have to >import the Linux passwd file in the FreeBSD format. >Read the man on the passwd to find a script that can >make it for you (at the end of the man): man 5 passwd >Then after merging the passwd file you should make a : >vipw >to make the database happy :-) >Beware to not overlap the first accounts on the >FreeBSD side: >Everything has uin under 1000 is better to leave >unchanged... >Check /etc/group of the Linux system and apply the >users group to the FreeBSD group file. >ADD ONLY the users group(s), not the system ones. >When you have finished this step look at the >/etc/aliases in the linux system and copy the custom >ones (the one pertinents to the users only) to FreeBSD >aliases file (in /etc too), then do a: >newaliases >The last step is to copy all the old mail which is in >the Linux system (but >I don't know where it is) on the /var/mail/ in the >FreeBSD box. >I used this little perl scripts to assign the >user:group to the files. >Run it from FreeBSD /var/mail/ after you have copied >the mailbox from the >linux system. >----> cut here <--- >#!/usr/bin/perl >foreach $file (<*>) >{ >($uid)=(getpwnam($file))[2]; >($grp)=(getpwnam($file))[3]; >chown($uid,$grp,$file); >}; >---> end <---- >I read all the file passwd but I could not find the >script like this. Morever, I do not know what does the >word uin means, maybe it's is Italian. I also send >mail to Mr.Gianmarco Giovannelli but maybe he is out >of home so I have no response. If anyone know this script, please send it to me because it's very urgent.If could, please explain for me more clearly and step by step the procedure to convert mailling system from Turbo Linux to Free BSD as more detail as possible because I am not experienced both Free BSD and Turbo Linux. Thank you very much ahead for all of your help. Please answering to me through both 2 address: nmtho@dit.hcmut.edu.vn manhtho@yahoo.com I am looking forward your response. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 19:43:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from web1901.mail.yahoo.com (web1901.mail.yahoo.com [128.11.23.50]) by hub.freebsd.org (Postfix) with SMTP id 05E8D15261 for ; Tue, 4 Jan 2000 19:43:54 -0800 (PST) (envelope-from manhtho@yahoo.com) Received: (qmail 24346 invoked by uid 60001); 5 Jan 2000 03:43:53 -0000 Message-ID: <20000105034353.24345.qmail@web1901.mail.yahoo.com> Received: from [202.167.121.197] by web1901.mail.yahoo.com; Tue, 04 Jan 2000 19:43:53 PST Date: Tue, 4 Jan 2000 19:43:53 -0800 (PST) From: Nguyen Manh Tho Subject: Please explain more clearly about converting malling system To: FreeBSD-Questions Cc: FreeBSD-Hackers 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 resend message, including the subjects. Please forgive me if you receive dupplicated copy. Dear all FreeBSD experts, On Tue, 28 Dec 1999, when answering about converting mailling system from Turbo Linux to Free BSD reserving all accounts and data, Mr. Gianmarco Giovannelli wrote: >As I said these are the step necessary (as I think) to >convert a linux box >in a FreeBSD one... ----> begin <---- >The conversion from Linux to FreeBSD is quite >simple... >As I asked a few hours ago in this list you have to >import the Linux passwd file in the FreeBSD format. >Read the man on the passwd to find a script that can >make it for you (at the end of the man): man 5 passwd >Then after merging the passwd file you should make a : >vipw >to make the database happy :-) >Beware to not overlap the first accounts on the >FreeBSD side: >Everything has uin under 1000 is better to leave >unchanged... >Check /etc/group of the Linux system and apply the >users group to the FreeBSD group file. >ADD ONLY the users group(s), not the system ones. >When you have finished this step look at the >/etc/aliases in the linux system and copy the custom >ones (the one pertinents to the users only) to FreeBSD >aliases file (in /etc too), then do a: >newaliases >The last step is to copy all the old mail which is in >the Linux system (but >I don't know where it is) on the /var/mail/ in the >FreeBSD box. >I used this little perl scripts to assign the >user:group to the files. >Run it from FreeBSD /var/mail/ after you have copied >the mailbox from the >linux system. >----> cut here <--- >#!/usr/bin/perl >foreach $file (<*>) >{ >($uid)=(getpwnam($file))[2]; >($grp)=(getpwnam($file))[3]; >chown($uid,$grp,$file); >}; >---> end <---- >I read all the file passwd but I could not find the >script like this. Morever, I do not know what does the >word uin means, maybe it's is Italian. I also send >mail to Mr.Gianmarco Giovannelli but maybe he is out >of home so I have no response. If anyone know this script, please send it to me because it's very urgent.If could, please explain for me more clearly and step by step the procedure to convert mailling system from Turbo Linux to Free BSD as more detail as possible because I am not experienced both Free BSD and Turbo Linux. Thank you very much ahead for all of your help. Please answering to me through both 2 address: nmtho@dit.hcmut.edu.vn manhtho@yahoo.com I am looking forward your response. __________________________________________________ Do You Yahoo!? Talk to your friends online with Yahoo! Messenger. http://messenger.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 20:49: 3 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fysgr387.sn.umu.se (fysgr387.sn.umu.se [130.239.128.239]) by hub.freebsd.org (Postfix) with ESMTP id D8F4814E7E for ; Tue, 4 Jan 2000 20:48:58 -0800 (PST) (envelope-from saska@fysgr387.sn.umu.se) Received: by fysgr387.sn.umu.se (Postfix, from userid 1000) id 158CEA837; Wed, 5 Jan 2000 05:51:39 +0100 (CET) Date: Wed, 5 Jan 2000 05:51:38 +0100 From: Markus Holmberg To: "Ronald F. Guilmette" Cc: freebsd-hackers@freebsd.org Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000105055138.A74746@fysgr387.sn.umu.se> References: <20000104121459.A8959@cons.org> <87632.947017515@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <87632.947017515@monkeys.com>; from rfg@monkeys.com on Tue, Jan 04, 2000 at 12:25:15PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To my understanding, there isn't a flaw in the Mozilla code. What is happening is that a cast is made to test if a value inside a double actually is just an int! If it wasn't, no harm is done and the double will be continued to be treaten as a double. That's is how I've interpreted it. To see where the macro in question (that generates the SIGFPE's) is defined and used, check this link: http://lxr.mozilla.org/seamonkey/ident?i=JSDOUBLE_IS_INT Here's the definition: #define JSDOUBLE_IS_INT(d, i) (JSDOUBLE_IS_FINITE(d) && \ !JSDOUBLE_IS_NEGZERO(d) && ((d) == (i = (jsint)(d)))) (Taken from http://lxr.mozilla.org/seamonkey/source/js/src/jsnum.h#82 ) I'm not 100% sure this is the only place where this happens, but it seems to be the most frequent. If it actually is the case that the cast is made just for testing purposes, then there isn't any flaw in the code and the SIGFPE (here) just needs to be turned off? I hope someone will object if this is not the case. (Or confirm that it's ok :)) /Markus On Tue, Jan 04, 2000 at 12:25:15PM -0800, Ronald F. Guilmette wrote: > > In message <20000104121459.A8959@cons.org>, > Martin Cracauer wrote: > > >Hence it is good to trap this and it is a bug in Mozilla, period. > >... > >I think we might discuss lowing the traps so that the softer > >exceptions are disabled. But most cases where people cry about > >FreeBSD's behaviour are serious errors like the one in mozilla, so we > >won't gain much. > > I agree that it appears that the Mozilla code had a serious bug/flaw, > and that having the FP traps enabled caused that fact to become > apparent. > > But the issue for me is still one of standards conformance. Regardless of > how helpful enabled FP traps may be, on occasion, for certain programs > and/or certain programmers, the IEEE 754 standard is pretty darn clear > and unambiguous regarding what the default setting should be, i.e. all > traps disabled. > > > > 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 Tue Jan 4 22: 1: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 491EC14E6C for ; Tue, 4 Jan 2000 22:01:03 -0800 (PST) (envelope-from aron@cs.rice.edu) Received: (from aron@localhost) by cs.rice.edu (8.9.0/8.9.0) id AAA25343 for freebsd-hackers@freebsd.org; Wed, 5 Jan 2000 00:01:01 -0600 (CST) Date: Wed, 5 Jan 2000 00:01:01 -0600 (CST) From: Mohit Aron Message-Id: <200001050601.AAA25343@cs.rice.edu> To: freebsd-hackers@freebsd.org Subject: FreeBSD-4.0 on SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a 4-processor machine but I want to configure FreeBSD-4.0 to only use 1 of the processors for some tests. In addition I want the local APIC to be enabled. It seems currently that the APIC is only enabled when the kernel is compiled with the SMP option. However, when I specify NCPU to be 1, the kernel panics. So the question is - is there a way to just use one processor and still keep the APIC enabled ? - Mohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Tue Jan 4 22:37:38 2000 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 3801215247; Tue, 4 Jan 2000 22:37:22 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.91.36] ident=exim) by scientia.demon.co.uk with esmtp (Exim 3.092 #1) id 125iAd-000PSq-00; Wed, 05 Jan 2000 04:35:39 +0000 Received: (from ben) by strontium.scientia.demon.co.uk (Exim 3.092 #1) id 125iAd-0002zW-00; Wed, 05 Jan 2000 04:35:39 +0000 Date: Wed, 5 Jan 2000 04:35:39 +0000 From: Ben Smithurst To: Nguyen Manh Tho , nmtho@dit.hcmut.edu.vn Cc: FreeBSD-Questions , FreeBSD-Hackers Subject: Re: Please explain more clearly about converting malling system Message-ID: <20000105043539.A11481@strontium.scientia.demon.co.uk> References: <20000105034353.24345.qmail@web1901.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000105034353.24345.qmail@web1901.mail.yahoo.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nguyen Manh Tho wrote: >> Everything has uin under 1000 is better to leave > I read all the file passwd but I could not find the script like > this. Morever, I do not know what does the >word uin means, maybe it's > is Italian. I also send >mail to Mr.Gianmarco Giovannelli but maybe he > is out >of home so I have no response. I suspect in this case uin == uid == user id (maybe uin stands for user id number, I've seen it used before). I can't help you with the rest, since I don't know Linux. -- 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 Wed Jan 5 0:26:51 2000 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 07F9814F6D for ; Wed, 5 Jan 2000 00:26:44 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id JAA08408; Wed, 5 Jan 2000 09:23:57 +0100 (CET) Date: Wed, 5 Jan 2000 09:23:57 +0100 From: Martin Cracauer To: Markus Holmberg Cc: "Ronald F. Guilmette" , freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000105092356.A8100@cons.org> References: <20000104121459.A8959@cons.org> <87632.947017515@monkeys.com> <20000105055138.A74746@fysgr387.sn.umu.se> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="jRHKVT23PllUwdXP" X-Mailer: Mutt 1.0i In-Reply-To: <20000105055138.A74746@fysgr387.sn.umu.se>; from saska@acc.umu.se on Wed, Jan 05, 2000 at 05:51:38AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Summary of following: The mozilla construction is a speed hack and it would usually work when exceptions are disabled. However, it is slower than the real thing would be and is hence useless and dangerous. In <20000105055138.A74746@fysgr387.sn.umu.se>, Markus Holmberg wrote: > To my understanding, there isn't a flaw in the Mozilla code. What is > happening is that a cast is made to test if a value inside a double > actually is just an int! If it wasn't, no harm is done and the double > will be continued to be treaten as a double. > > That's is how I've interpreted it. To see where the macro in question > (that generates the SIGFPE's) is defined and used, check this link: > > http://lxr.mozilla.org/seamonkey/ident?i=JSDOUBLE_IS_INT > > Here's the definition: > > #define JSDOUBLE_IS_INT(d, i) (JSDOUBLE_IS_FINITE(d) && \ > !JSDOUBLE_IS_NEGZERO(d) && ((d) == (i = (jsint)(d)))) Ah, OK, this macro is a conversion where the undefined result of the (int)double_bigger_max_int is (intentionally) used as a speed hack of a range check. The only problems is that it isn't faster than correct code. It is true that in practice it this macro will work as intended when exceptions are disabled, because: While the result of (int)double_bigger_max_int is undefined, you will usually get an i that is filled with any integer value. If d was > INT_MAX, the == with return nil for any value of i. Hence the thing works if the programmer remembers only to use i if the macro return true. Beside the fact that I don't like this construction style-wise, I have two problems with it: 1) In C, when an expression is undefined, *anything* may happen. You cannot depend on the fact that the code behaves as if i was filled with an integer at all. This is not ANSI C conformant. An conformant ANSI C compiler may make assumptions about this code that break it. 2) This speed hack is already weakend: If you look into the header file in Mozilla, you will find that the IS_FINITE and IS_NEGZERO was added to make MSVC++ happy, because it will run into exceptions otherwise. The alternative to this hack is a normal range check. This will work because behaviour is defined for comparisions on infinite and other exceptional values. You would get: - ANSI C conformance. - Make VC++ happy. - Make the code ready to leave those FPU exceptions enabled that indicate real and serious problems. - On my machine, it is actually faster than the current version. Here's one version, implemented as an inline function. A complete runnable example comparing the Mozilla construction (including timekeeping) to this one is appended. On my machines, the conforming version is 2-3 times faster than the Mozilla hack (and it doesn't trigger exceptions). static inline int cra_is_int(const double d, int *const i) { if (d <= (double)INT_MAX && d >= (double)INT_MIN) { *i = (int)d; return 1; } else return 0; } I can only urge the Mozilla team to use clean constructions and leave their hands off speed hacks that trigger undefined behaviour. The project needs reliability first, and then speed. In this case, you don't even get speed. Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer/ Tel.: (private) +4940 5221829 Fax.: (private) +4940 5228536 --jRHKVT23PllUwdXP Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="cast.c" #include #include #include #include #include #if defined(SysV) || defined(__svr4__) #include #include #include #else #include #endif typedef __uint32_t uint32; typedef int jsint; /* -*- Mode: C; tab-width: 8; indent-tabs-mode: nil; c-basic-offset: 4 -*- * * The contents of this file are subject to the Netscape Public * License Version 1.1 (the "License"); you may not use this file * except in compliance with the License. You may obtain a copy of * the License at http://www.mozilla.org/NPL/ * * Software distributed under the License is distributed on an "AS * IS" basis, WITHOUT WARRANTY OF ANY KIND, either express oqr * implied. See the License for the specific language governing * rights and limitations under the License. * * The Original Code is Mozilla Communicator client code, released * March 31, 1998. * * The Initial Developer of the Original Code is Netscape * Communications Corporation. Portions created by Netscape are * Copyright (C) 1998 Netscape Communications Corporation. All * Rights Reserved. * * Contributor(s): * * Alternatively, the contents of this file may be used under the * terms of the GNU Public License (the "GPL"), in which case the * provisions of the GPL are applicable instead of those above. * If you wish to allow use of your version of this file only * under the terms of the GPL and not to allow others to use your * version of this file under the NPL, indicate your decision by * deleting the provisions above and replace them with the notice * and other provisions required by the GPL. If you do not delete * the provisions above, a recipient may use your version of this * file under either the NPL or the GPL. */ /* * JS number (IEEE double) interface. * * JS numbers are optimistically stored in the top 31 bits of 32-bit integers, * but floating point literals, results that overflow 31 bits, and division and * modulus operands and results require a 64-bit IEEE double. These are GC'ed * and pointed to by 32-bit jsvals on the stack and in object properties. * * When a JS number is treated as an object (followed by . or []), the runtime * wraps it with a JSObject whose valueOf method returns the unwrapped number. */ #define IS_LITTLE_ENDIAN #ifdef IS_LITTLE_ENDIAN #define JSDOUBLE_HI32(x) (((uint32 *)&(x))[1]) #define JSDOUBLE_LO32(x) (((uint32 *)&(x))[0]) #else #define JSDOUBLE_HI32(x) (((uint32 *)&(x))[0]) #define JSDOUBLE_LO32(x) (((uint32 *)&(x))[1]) #endif #define JSDOUBLE_HI32_SIGNBIT 0x80000000 #define JSDOUBLE_HI32_EXPMASK 0x7ff00000 #define JSDOUBLE_HI32_MANTMASK 0x000fffff #define JSDOUBLE_IS_NaN(x) \ ((JSDOUBLE_HI32(x) & JSDOUBLE_HI32_EXPMASK) == JSDOUBLE_HI32_EXPMASK && \ (JSDOUBLE_LO32(x) || (JSDOUBLE_HI32(x) & JSDOUBLE_HI32_MANTMASK))) #define JSDOUBLE_IS_INFINITE(x) \ ((JSDOUBLE_HI32(x) & ~JSDOUBLE_HI32_SIGNBIT) == JSDOUBLE_HI32_EXPMASK && \ !JSDOUBLE_LO32(x)) #define JSDOUBLE_IS_FINITE(x) \ ((JSDOUBLE_HI32(x) & JSDOUBLE_HI32_EXPMASK) != JSDOUBLE_HI32_EXPMASK) #define JSDOUBLE_IS_NEGZERO(d) (JSDOUBLE_HI32(d) == JSDOUBLE_HI32_SIGNBIT && \ JSDOUBLE_LO32(d) == 0) /* * JSDOUBLE_IS_INT first checks that d is neither NaN nor infinite, to avoid * raising SIGFPE on platforms such as Alpha Linux, then (only if the cast is * safe) leaves i as (jsint)d. This also avoid anomalous NaN floating point * comparisons under MSVC. */ #define JSDOUBLE_IS_INT(d, i) (JSDOUBLE_IS_FINITE(d) && !JSDOUBLE_IS_NEGZERO(d) \ && ((d) == (i = (jsint)(d)))) static inline int cra_is_int(const double d, int *const i) { if (d <= (double)INT_MAX && d >= (double)INT_MIN) { *i = (int)d; return 1; } else return 0; } static double cpu_so_far(void) { #if defined(SysV) || defined(__svr4__) struct tms tms; if (times(&tms) == -1) io_error("times"); return ((double) tms.tms_utime) / ((double) CLK_TCK) + ((double) tms.tms_stime) / ((double) CLK_TCK); #else struct rusage rusage; getrusage(RUSAGE_SELF, &rusage); return ((double) rusage.ru_utime.tv_sec) + (((double) rusage.ru_utime.tv_usec) / 1000000.0) + ((double) rusage.ru_stime.tv_sec) + (((double) rusage.ru_stime.tv_usec) / 1000000.0); #endif } int main(void) { double time; int count; double d; int i; int res; const int n = 5000000; fpsetmask(0); time = cpu_so_far(); d = INT_MIN + n / 2; count = 0; for (i = 0; i < n; i++) { d--; if (JSDOUBLE_IS_INT(d, res)) count++; } printf("JS : %d values were valid, time: %.2f sec\n", count, cpu_so_far() - time); time = cpu_so_far(); d = INT_MAX - n / 2; count = 0; for (i = 0; i < n; i++) { d++; if (cra_is_int(d, &res)) count++; } printf("cra: %d values were valid, time: %.2f sec\n", count, cpu_so_far() - time); return 0; } --jRHKVT23PllUwdXP-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 0:36: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id F007914BD8 for ; Wed, 5 Jan 2000 00:35:54 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id DAA26364; Wed, 5 Jan 2000 03:35:48 -0500 (EST) (envelope-from luoqi) Date: Wed, 5 Jan 2000 03:35:48 -0500 (EST) From: Luoqi Chen Message-Id: <200001050835.DAA26364@lor.watermarkgroup.com> To: aron@cs.rice.edu, freebsd-hackers@FreeBSD.ORG Subject: Re: FreeBSD-4.0 on SMP Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > I have a 4-processor machine but I want to configure FreeBSD-4.0 > to only use 1 of the processors for some tests. In addition I want the > local APIC to be enabled. It seems currently that the APIC is only enabled > when the kernel is compiled with the SMP option. However, when I specify > NCPU to be 1, the kernel panics. So the question is - is there a way to > just use one processor and still keep the APIC enabled ? > > > > - Mohit > Try again with the following patch, Index: i386/mp_machdep.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/mp_machdep.c,v retrieving revision 1.112 diff -u -r1.112 mp_machdep.c --- i386/mp_machdep.c 1999/11/27 12:32:20 1.112 +++ i386/mp_machdep.c 2000/01/05 08:28:40 @@ -1097,7 +1097,7 @@ processor_entry(proc_entry_ptr entry, int cpu) { /* check for usability */ - if ((cpu >= NCPU) || !(entry->cpu_flags & PROCENTRY_FLAG_EN)) + if (!(entry->cpu_flags & PROCENTRY_FLAG_EN)) return 0; /* check for BSP flag */ @@ -1109,11 +1109,13 @@ } /* add another AP to list, if less than max number of CPUs */ - else { + else if (cpu < NCPU) { CPU_TO_ID(cpu) = entry->apic_id; ID_TO_CPU(entry->apic_id) = cpu; return 1; } + + return 0; } Index: include/mpapic.h =================================================================== RCS file: /home/ncvs/src/sys/i386/include/mpapic.h,v retrieving revision 1.12 diff -u -r1.12 mpapic.h --- include/mpapic.h 1999/08/28 00:44:19 1.12 +++ include/mpapic.h 2000/01/05 08:24:58 @@ -98,6 +98,8 @@ static __inline int all_but_self_ipi(int vector) { + if (mp_ncpus <= 1) + return 0; return apic_ipi(APIC_DEST_ALLESELF, vector, APIC_DELMODE_FIXED); } -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 0:50:18 2000 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 639CF14FA6 for ; Wed, 5 Jan 2000 00:50:11 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id JAA08528; Wed, 5 Jan 2000 09:50:03 +0100 (CET) Date: Wed, 5 Jan 2000 09:50:02 +0100 From: Martin Cracauer To: "Ronald F. Guilmette" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000105095002.B8100@cons.org> References: <20000104121459.A8959@cons.org> <87632.947017515@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <87632.947017515@monkeys.com>; from rfg@monkeys.com on Tue, Jan 04, 2000 at 12:25:15PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <87632.947017515@monkeys.com>, Ronald F. Guilmette wrote: > > In message <20000104121459.A8959@cons.org>, > Martin Cracauer wrote: > > >Hence it is good to trap this and it is a bug in Mozilla, period. > >... > >I think we might discuss lowing the traps so that the softer > >exceptions are disabled. But most cases where people cry about > >FreeBSD's behaviour are serious errors like the one in mozilla, so we > >won't gain much. > > I agree that it appears that the Mozilla code had a serious bug/flaw, > and that having the FP traps enabled caused that fact to become > apparent. > > But the issue for me is still one of standards conformance. Regardless of > how helpful enabled FP traps may be, on occasion, for certain programs > and/or certain programmers, the IEEE 754 standard is pretty darn clear > and unambiguous regarding what the default setting should be, i.e. all > traps disabled. You mix up two things: 1) "Real" floating point arithmetic between floating types. 2) Conversion of floating point types to integer. The authority on the latter issue is ANSI C, not ieee754. ANSI C 89 states in 6.2.1.3 explicitly, that "if the value of the integral part cannot be represented by the integral type, the behaviour is undefined". ANSI C 99 (WG14/N869 Committee Draft -- January 18, 1999) has the same sentense in 6.3.1.4. Note that "undefined behaviour" in ANSI C means that anything can happen. There is no quarantee that the code in question even behaves as if variable i was filled with any integer. But the Mozilla macro relies on exactly that, hence it does not conform to the standard. It also doesn't reach its speedup goal, see my other message. Regarding the "real" (non-converting) floating point exceptions: As I stated earlier, that is a different mattter since they are covered by well-defined behaviour when they are masked. But I wonder whether turning off the harmless exceptions, but leaving on the harmfull wouldn't confuse people even further, since certain other OSes turn off everything and we would look like them on first sight and then turn up with surprises later. 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 Jan 5 1: 8: 3 2000 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 9975814C4A for ; Wed, 5 Jan 2000 01:07:59 -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 KAA68609; Wed, 5 Jan 2000 10:07:16 +0100 (MET) Date: Wed, 5 Jan 2000 10:07:16 +0100 From: Martin Cracauer To: mauzi@poli.hu Cc: hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler Message-ID: <20000105100716.A63545@cons.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Gergely EGERVARY on Tue, Jan 04, 2000 at 07:32:13PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Gergely EGERVARY wrote: > Hi, > > is there any alternative (non-commercial) C compiler to use, or is gcc the > best? > > I have just upgraded my system to -current w/egcs 2.95.2 and I have > several problems with it, especially when using optimizations (-O2 and > such) Others already said that replacing the system compiler will be difficult. However, you should be able to use any FreeBSD include file that is supposed to be used by userlevel code with any ANSI C conforming compiler. People like Bruce Evans once took great care to guarantee that. It seems this has gone under the wheel by less careful committers since around 3.0, but the goal is nontheless to keep this capability. If you have examples where it breaks, send them to me, please. You will not be able to use all features of FreeBSD, of course. Calling functions that take long long arguments doesn't work, these should be masked out when compiling struct ansi code. It may get painful quickly, as such basic things like seek() are amoung them. 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 Wed Jan 5 1: 9:49 2000 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 B5F5D14E4A for ; Wed, 5 Jan 2000 01:09:46 -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 KAA68619; Wed, 5 Jan 2000 10:09:09 +0100 (MET) Date: Wed, 5 Jan 2000 10:09:09 +0100 From: Martin Cracauer To: mauzi@poli.hu Cc: hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler Message-ID: <20000105100909.B63545@cons.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Gergely EGERVARY on Tue, Jan 04, 2000 at 07:32:13PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Gergely EGERVARY wrote: > I have just upgraded my system to -current w/egcs 2.95.2 and I have > several problems with it, especially when using optimizations (-O2 and > such) When your code breaks when using -O2 or higher, don't do that, use just -O! Almost all examples I've seen where people claimed newer gcc's broke their code are triggered by unclean C code that isn't strictly ANSI C conformant (also see the other thread about ieeefp and floating point exceptions). As far as I understand, the gcc people try to keep the -O option compatible in a way that it doesn't break code that didn't break in earlier versions of gcc. This is exactly the option you need, it's a service for you and you should use it unless you are absolutely sure your code is valid. There are examples of -O2 or higher breaking valid code, but they are much less common than implied. And such issues were in 2.7.x was well, that's the reason the base system is compiled with -O. 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 Wed Jan 5 2:10:13 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.iserlohn.netsurf.de (mail.iserlohn.netsurf.de [194.195.194.253]) by hub.freebsd.org (Postfix) with ESMTP id A692E153A0 for ; Wed, 5 Jan 2000 02:10:04 -0800 (PST) (envelope-from sascha@schumann.cx) Received: from schumann.cx (hennen32s.iserlohn.netsurf.de [194.195.194.226]) by mail.iserlohn.netsurf.de (8.9.1/8.9.1) with SMTP id LAA32305 for ; Wed, 5 Jan 2000 11:10:21 +0100 Received: (qmail 18628 invoked from network); 5 Jan 2000 10:09:58 -0000 Received: from flaubert.foo.bar (192.168.0.99) by guerilla.foo.bar with SMTP; 5 Jan 2000 10:09:58 -0000 Received: (qmail 9534 invoked by uid 500); 5 Jan 2000 10:09:58 -0000 Date: Wed, 5 Jan 2000 11:09:58 +0100 From: Sascha Schumann To: freebsd-hackers@freebsd.org Subject: undefined reference Message-ID: <20000105110958.A9444@schumann.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Notice: Copyright (c) 2000 Sascha Schumann. All rights reserved. X-Operating-System: Linux 2.2.13 #10 Mon Dec 27 20:35:15 CET 1999 alpha Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've written a new driver for ppbus (yes, I know that newppbus exists). I've added one line to conf/files, added "device pcf0" to my kernel configuration file, config'ured the kernel, and ran make depend all. The driver compiles cleanly, but then the linker complains about: isa_compat.o(.data+0xc): undefined reference to `pcfdriver' pcfdriver is declared in pcf.c: static struct ppb_driver pcfdriver = { pcfprobe, pcfattach, PCF_NAME }; DATA_SET(ppbdriver_set, pcfdriver); When I removed the static declarator test-wise, the linker complained about dupe symbols. Is it really impossible to make this work? Driver source: http://apache.org/~sascha/pcf.c I think I miss something obvious, so I'd appreciate your advice. -- Regards, Sascha Schumann Consultant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 2:15:30 2000 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 646C915374 for ; Wed, 5 Jan 2000 02:15:27 -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 555471CA0; Wed, 5 Jan 2000 18:15:25 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Sascha Schumann Cc: freebsd-hackers@freebsd.org Subject: Re: undefined reference In-Reply-To: Message from Sascha Schumann of "Wed, 05 Jan 2000 11:09:58 +0100." <20000105110958.A9444@schumann.cx> Date: Wed, 05 Jan 2000 18:15:25 +0800 From: Peter Wemm Message-Id: <20000105101525.555471CA0@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sascha Schumann wrote: > Hi, > > I've written a new driver for ppbus (yes, I know that > newppbus exists). I've added one line to conf/files, added > "device pcf0" to my kernel configuration file, config'ured > the kernel, and ran make depend all. The driver compiles > cleanly, but then the linker complains about: > > isa_compat.o(.data+0xc): undefined reference to `pcfdriver' > > pcfdriver is declared in pcf.c: > > static struct ppb_driver pcfdriver = { > pcfprobe, pcfattach, PCF_NAME > }; > DATA_SET(ppbdriver_set, pcfdriver); > > When I removed the static declarator test-wise, the linker > complained about dupe symbols. Is it really impossible to make > this work? There is another driver called 'pcf' - you'll have to use a different name. 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 Wed Jan 5 2:27:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.iserlohn.netsurf.de (mail.iserlohn.netsurf.de [194.195.194.253]) by hub.freebsd.org (Postfix) with ESMTP id 313C715374 for ; Wed, 5 Jan 2000 02:27:35 -0800 (PST) (envelope-from sascha@schumann.cx) Received: from schumann.cx (hennen32s.iserlohn.netsurf.de [194.195.194.226]) by mail.iserlohn.netsurf.de (8.9.1/8.9.1) with SMTP id LAA32373 for ; Wed, 5 Jan 2000 11:27:53 +0100 Received: (qmail 19228 invoked from network); 5 Jan 2000 10:27:26 -0000 Received: from flaubert.foo.bar (192.168.0.99) by guerilla.foo.bar with SMTP; 5 Jan 2000 10:27:26 -0000 Received: (qmail 9729 invoked by uid 500); 5 Jan 2000 10:27:26 -0000 Date: Wed, 5 Jan 2000 11:27:26 +0100 From: Sascha Schumann To: Peter Wemm Cc: freebsd-hackers@freebsd.org Subject: Re: undefined reference Message-ID: <20000105112726.A9714@schumann.cx> References: <20000105101525.555471CA0@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000105101525.555471CA0@overcee.netplex.com.au>; from peter@netplex.com.au on Wed, Jan 05, 2000 at 06:15:25PM +0800 X-Notice: Copyright (c) 2000 Sascha Schumann. All rights reserved. X-Operating-System: Linux 2.2.13 #10 Mon Dec 27 20:35:15 CET 1999 alpha Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 06:15:25PM +0800, Peter Wemm wrote: [..] > > There is another driver called 'pcf' - you'll have to use a different name. Thanks! I forgot to check i386/files/conf. Now, on to debugging. -- Regards, Sascha Schumann Consultant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 7:24:42 2000 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 5A893153CE for ; Wed, 5 Jan 2000 07:24:33 -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 MAA02133; Tue, 4 Jan 2000 12:20:15 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Tue, 4 Jan 2000 12:20:15 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Nate Williams Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: USB vs. parallel port In-Reply-To: <199912261614.JAA07297@mt.sri.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 Whether or not the system is loaded or not depends mainly on what hardware you have. OHCI tends to load the system a lot less than UHCI (Intel). But compared to serial and parallel ports, USB is a lot better. Most of the transaction is done per DMA and with large quantities it outperforms both of them in every way. 300Kb/s at less than 1% CPU should be no problem. I have no idea what the load on the PCI bus is though. That might be a problem as there are a lot of small transfers over that bus. By the way, at the moment it is better to have a UHCI controller on your motherboard. Allthough the OHCI controller is much smarter and more efficient, support for it is not as stable as the support for UHCI controllers. Nick > A co-worker is looking into buying a printer, and was wondering which > kind would be better, USB and/or parallel. (There are also some that do > both). > > Parallel printers tend to load down the system when busy, but serial > devices tend to load them down even more, although USB is a whole > different animal. > > What are the trade-offs? > > Thanks for any help you can provide! > > > Nate > > > 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 Wed Jan 5 7:32:45 2000 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 CEFFE15033 for ; Wed, 5 Jan 2000 07:32:43 -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 B0DC21CCE; Wed, 5 Jan 2000 23:32:41 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Hibma Cc: Nate Williams , freebsd-hackers@FreeBSD.ORG Subject: Re: USB vs. parallel port In-Reply-To: Message from Nick Hibma of "Tue, 04 Jan 2000 12:20:15 +0100." Date: Wed, 05 Jan 2000 23:32:41 +0800 From: Peter Wemm Message-Id: <20000105153241.B0DC21CCE@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > By the way, at the moment it is better to have a UHCI controller on > your motherboard. Allthough the OHCI controller is much smarter and more > efficient, support for it is not as stable as the support for UHCI > controllers. Sounds like UHCI => IDE, OHCI => SCSI ? (only 1/2 :-). Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 8:38:33 2000 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 0DD7C153B0 for ; Wed, 5 Jan 2000 08:38:30 -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 IAA91690; Wed, 5 Jan 2000 08:38:11 -0800 (PST) To: Martin Cracauer Cc: Markus Holmberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? In-reply-to: Your message of Wed, 05 Jan 2000 09:23:57 +0100. <20000105092356.A8100@cons.org> Date: Wed, 05 Jan 2000 08:38:11 -0800 Message-ID: <91688.947090291@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I confess that I didn't look at the original Bugzilla bugreport on this thing too closely, but... In message <20000105092356.A8100@cons.org>, Martin Cracauer wrote: >> #define JSDOUBLE_IS_INT(d, i) (JSDOUBLE_IS_FINITE(d) && \ >> !JSDOUBLE_IS_NEGZERO(d) && ((d) == (i = (jsint)(d)))) > >Ah, OK, this macro is a conversion where the undefined result of the >(int)double_bigger_max_int is (intentionally) used as a speed hack of >a range check. >... >While the result of > (int)double_bigger_max_int >is undefined, you will usually get an i that is filled with any >integer value. If d was > INT_MAX, the == with return nil for any >value of i. Hence the thing works if the programmer remembers only to >use i if the macro return true. > >Beside the fact that I don't like this construction style-wise, I have >two problems with it: > >1) In C, when an expression is undefined, *anything* may happen. You > cannot depend on the fact that the code behaves as if i was filled > with an integer at all. This is not ANSI C conformant. An > conformant ANSI C compiler may make assumptions about this code > that break it. Ah! Yea. This is a DEFINITE problem. >The alternative to this hack is a normal range check... >... >static inline int cra_is_int(const double d, int *const i) >{ > if (d <= (double)INT_MAX && d >= (double)INT_MIN) { > *i = (int)d; > return 1; > } else > return 0; >} The function shown above is indeed the correct solution/approach for what Mozilla is trying to do here, for the reasons cited above. But having said that, I also want to reiterate what I said before... Yes, the existing Mozilla code should be fixed to perform the range check in the manner that Martin Cracauer has shown above. However the can-of-worms opened up by this whole thread/discussion has revealed *two* bugs... one in the Mozilla code (which Martin Cracauer has correctly described, diagnosed, and provided a solution for) and also, there is still that annoying little deviation from the IEEE FP standard that results from FreeBSD's failure to disable all IEEE FP traps upon entry to main. _Both_ bugs should be fixed. -- rfg P.S. Actually, although Martin Cracauer's suggested replacement for the existing Mozilla code is certainly better than what Mozilla is using now, it may perhaps need to be slightly augmented with an additional check to see if the value of `d' is a NaN prior to per- forming the range check. But I'm not even sure about that. I'd have to go and dredge my copy of IEEE 754 out of my files again to find out what the results of <= and >= are in cases where one of the operands is a NaN. I think however that those operations are perhaps required to return False in that case, in which case Martin Cracauer's suggested Mozilla replacement code is just fine as it is. And in any case, that is all a moot point anyway if it is known in advance that `d' will not be a NaN. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 8:42:21 2000 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 0718E14CB7 for ; Wed, 5 Jan 2000 08:42:18 -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 IAA91756; Wed, 5 Jan 2000 08:42:06 -0800 (PST) To: Martin Cracauer Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? In-reply-to: Your message of Wed, 05 Jan 2000 09:50:02 +0100. <20000105095002.B8100@cons.org> Date: Wed, 05 Jan 2000 08:42:06 -0800 Message-ID: <91754.947090526@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000105095002.B8100@cons.org>, Martin Cracauer wrote: >In <87632.947017515@monkeys.com>, Ronald F. Guilmette wrote: >> ... >> I agree that it appears that the Mozilla code had a serious bug/flaw, >> and that having the FP traps enabled caused that fact to become >> apparent. >> >> But the issue for me is still one of standards conformance. Regardless of >> how helpful enabled FP traps may be, on occasion, for certain programs >> and/or certain programmers, the IEEE 754 standard is pretty darn clear >> and unambiguous regarding what the default setting should be, i.e. all >> traps disabled. > >You mix up two things: > >1) "Real" floating point arithmetic between floating types. > >2) Conversion of floating point types to integer. > >The authority on the latter issue is ANSI C, not ieee754. > >ANSI C 89 states in 6.2.1.3 explicitly, that "if the value of the >integral part cannot be represented by the integral type, the >behaviour is undefined". >ANSI C 99 (WG14/N869 Committee Draft -- January 18, 1999) has the same >sentense in 6.3.1.4. > >Note that "undefined behaviour" in ANSI C means that anything can >happen. I agress with your assertions regarding the C standard completely, but... I don't think that I mixed anything up. There is a bug in the Mozilla code (for the reasons you mentioned) _and_ also a bug in FreeBSD's conformance to IEEE 754 (or lack thereof). Didn't I say that? -- rfg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 8:43:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 88AFB15415 for ; Wed, 5 Jan 2000 08:43:36 -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 LAA02338; Wed, 5 Jan 2000 11:42:34 -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 LAA08454; Wed, 5 Jan 2000 11:42:34 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id LAA26756; Wed, 5 Jan 2000 11:42:33 -0500 (EST) Date: Wed, 5 Jan 2000 11:42:33 -0500 (EST) From: Thomas David Rivers Message-Id: <200001051642.LAA26756@lakes.dignus.com> To: cracauer@cons.org, rfg@monkeys.com Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Cc: freebsd-hackers@FreeBSD.ORG, saska@acc.umu.se In-Reply-To: <91688.947090291@monkeys.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > P.S. Actually, although Martin Cracauer's suggested replacement for > the existing Mozilla code is certainly better than what Mozilla is > using now, it may perhaps need to be slightly augmented with an > additional check to see if the value of `d' is a NaN prior to per- > forming the range check. But I'm not even sure about that. I'd > have to go and dredge my copy of IEEE 754 out of my files again to > find out what the results of <= and >= are in cases where one of > the operands is a NaN. I think however that those operations are > perhaps required to return False in that case, in which case Martin > Cracauer's suggested Mozilla replacement code is just fine as it is. > > And in any case, that is all a moot point anyway if it is known in > advance that `d' will not be a NaN. > I don't believe the C89 standard doesn't have a way to test for NaN - so, if we're talking portability here - you can't test for NaN. I think C99 does have some library functions to do tests for NaN and Inf. This is interesting because the 390 HFP format doesn't have NaN or Inf. Why would that matter to Mozilla - well, there's a LINUX port now for the mainframe and Mozilla might want to run there. [I don't know if that port is using the old-style HFP format or the new-style IEEE format.] - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 8:51:15 2000 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 8EA2415406 for ; Wed, 5 Jan 2000 08:51:07 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id RAA10938; Wed, 5 Jan 2000 17:50:52 +0100 (CET) Date: Wed, 5 Jan 2000 17:50:52 +0100 From: Martin Cracauer To: "Ronald F. Guilmette" Cc: Martin Cracauer , Markus Holmberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000105175051.A10840@cons.org> References: <20000105092356.A8100@cons.org> <91688.947090291@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <91688.947090291@monkeys.com>; from rfg@monkeys.com on Wed, Jan 05, 2000 at 08:38:11AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <91688.947090291@monkeys.com>, Ronald F. Guilmette wrote: > > >The alternative to this hack is a normal range check... > >... > >static inline int cra_is_int(const double d, int *const i) > >{ > > if (d <= (double)INT_MAX && d >= (double)INT_MIN) { > > *i = (int)d; > > return 1; > > } else > > return 0; > >} > > The function shown above is indeed the correct solution/approach for > what Mozilla is trying to do here, for the reasons cited above. > > But having said that, I also want to reiterate what I said before... > > Yes, the existing Mozilla code should be fixed to perform the range > check in the manner that Martin Cracauer has > shown above. However the can-of-worms opened up by this whole > thread/discussion has revealed *two* bugs... one in the Mozilla > code (which Martin Cracauer has correctly > described, diagnosed, and provided a solution for) and also, there > is still that annoying little deviation from the IEEE FP standard > that results from FreeBSD's failure to disable all IEEE FP traps > upon entry to main. > > _Both_ bugs should be fixed. As I said in the other message: This case is not covered by the IEEE exceptions that may be disabled. This case is a conversion of double -> int, it is not covered by ieee754, but by ANSI C. And the ANSI C standard has its own paragraph for exactly this case and its own sentense that if the the double is out of range the behaviour is undefined. Really, what else do you want? The issue would be different if we'd talk about float devision by zero or a pure FP overflow, but we don't. We don't talk floating point arthmetic here, we talk floating point conversion and a case that is directly covered by ANSI C. > P.S. Actually, although Martin Cracauer's suggested replacement for > the existing Mozilla code is certainly better than what Mozilla is > using now, it may perhaps need to be slightly augmented with an > additional check to see if the value of `d' is a NaN prior to per- > forming the range check. But I'm not even sure about that. I'd > have to go and dredge my copy of IEEE 754 out of my files again to > find out what the results of <= and >= are in cases where one of > the operands is a NaN. I think however that those operations are > perhaps required to return False in that case, in which case Martin > Cracauer's suggested Mozilla replacement code is just fine as it is. I test of >= and <= against NaN always returns nil. 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 Jan 5 9: 2: 8 2000 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 5405A14D37 for ; Wed, 5 Jan 2000 09:02:03 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id SAA36755; Wed, 5 Jan 2000 18:02:01 +0100 (CET) (envelope-from olli) Date: Wed, 5 Jan 2000 18:02:01 +0100 (CET) Message-Id: <200001051702.SAA36755@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler X-Newsgroups: list.freebsd-hackers In-Reply-To: <84v1pq$11kk$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) 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 Martin Cracauer wrote in list.freebsd-hackers: > You will not be able to use all features of FreeBSD, of course. > Calling functions that take long long arguments doesn't work, these > should be masked out when compiling struct ansi code. It may get > painful quickly, as such basic things like seek() are amoung them. ``long long'' is part of the C9x standard (or whatever it is called now, I'm not an expert). If TenDRA (or lcc) supports the latest C standard, then there should be no problem. 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 Wed Jan 5 9:27:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from poseidon.student.umd.edu (poseidon.student.umd.edu [129.2.220.99]) by hub.freebsd.org (Postfix) with ESMTP id 4E7811540A for ; Wed, 5 Jan 2000 09:27:23 -0800 (PST) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (localhost [127.0.0.1]) by poseidon.student.umd.edu (8.9.3/8.9.3) with ESMTP id MAA00496 for ; Wed, 5 Jan 2000 12:26:58 -0500 (EST) (envelope-from bfoz@glue.umd.edu) Message-ID: <38737EE2.D9544DBB@glue.umd.edu> Date: Wed, 05 Jan 2000 12:26:58 -0500 From: Brandon Fosdick X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: linux kld: sblive Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So I've missed the whole discussion on the sblive driver timetable and the archives didn't help much. And I just grabbed creative's source for a linux driver from opensource.creative.com. Needless to say, it needs some work before it will compile. Is anybody else working on this? I'm tired of having a soundcard that I can't use so I'm tempted to jump into this. I don't know anything about drivers, but I know that I'm tired of waiting, are there any docs that might help me along? Thanks, Brandon bfoz@glue.umd.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 10: 9:25 2000 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 0F53B153B0 for ; Wed, 5 Jan 2000 10:09:22 -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 KAA98341; Wed, 5 Jan 2000 10:08:54 -0800 (PST) To: Martin Cracauer Cc: mauzi@poli.hu, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of Wed, 05 Jan 2000 10:07:16 +0100. <20000105100716.A63545@cons.org> Date: Wed, 05 Jan 2000 10:08:54 -0800 Message-ID: <98339.947095734@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000105100716.A63545@cons.org>, Martin Cracauer wrote: >Others already said that replacing the system compiler will be >difficult. > >However, you should be able to use any FreeBSD include file that is >supposed to be used by userlevel code with any ANSI C conforming >compiler. People like Bruce Evans once took great care to guarantee >that. It seems this has gone under the wheel by less careful >committers since around 3.0, but the goal is nontheless to keep this >capability. If you have examples where it breaks, send them to me, >please. Well, if you are interested in doing some *serious* QA and ANSI/ISO conformance testing on the system include files... For hours of enjoyment, try running the following simple script: ----------------------------------------------------------------------- #!/bin/csh cd /usr/include set hfiles=(`find * -follow \( -name g++ -prune \) -o \( -type f -name \*.h -print \)`) cd /tmp foreach hfile ($hfiles) echo '------------------------------------------- Checking '$hfile echo '#include <'$hfile'>' > includer.c gcc -Wall -pedantic-errors -Wstrict-prototypes -c includer.c end ----------------------------------------------------------------------- NOTES: [1] In an Ideal Universe, the above script should run to completion while yielding ZERO errors and also ZERO warnings from the compiler. [2] We do not live in an Ideal Universe. [3] The ANSI C standard, at least, contains the requirement that each individual system include file specified by that standard should be usable all by itself, without the programmer being required to explicitly include any OTHER system include files, prior to the one he/she is actually interested in using. This is, I believe, a Good Thing. However few are the systems where this sort of elegance pervades ALL of the available system include files, which is a pity, because if this `feature' were in fact pervasive, it would make QA'ing the whole complete set of system include files much easier. [4] Even if one does not accept the advisability of having each and every system include file be ``includable'' all on its own, it should, in theory, still be possible to work out a proper partial ordering of the entire set of system include files, taking into account which ones must be included before which other ones. Using that partial order then, it should be trivially possible to construct a single .c file which just includes each and every one of the system include files in an order consistant with the partial ordering imposed by their interdependences, and THAT file should be able to be compiled (with the gcc command line shown in the script above) with zero errors and warnings. (I will volunteer to determine/document the partial ordering if anyone else is willing to then get in and fix all of the header files bugs which will be revealed by compiling the hypothesized .c file, but I won't waste my time doing this if nobody gives a damn.) [5] Taking the ordered list of #include statements generated as per [4] above, another potentially useful QA test is to attempt to compile a .c file containing that ordered set of #include's followed by another copy of that same set. This will flush out all cases of system include files that cannot be included twice in a given compilation without incuring `multiple definition' errors, e.g. . Once again, I use the ANSI/ISO C standard as my guide - It requires that each and every system include file which *it* mandates must be capable of being included twice into the same single compilation WITHOUT incuring compile-time errors. [6] For extra credit, take the script shown above and replace "gcc" with "g++' and then re-run. In this case also, neither errors nor warnings should ensue. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 10:13:42 2000 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 0973415415 for ; Wed, 5 Jan 2000 10:13:40 -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 KAA99739; Wed, 5 Jan 2000 10:13:06 -0800 (PST) To: Martin Cracauer Cc: mauzi@poli.hu, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of Wed, 05 Jan 2000 10:09:09 +0100. <20000105100909.B63545@cons.org> Date: Wed, 05 Jan 2000 10:13:06 -0800 Message-ID: <99736.947095986@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000105100909.B63545@cons.org>, Martin Cracauer wrote: >In , Gergely EGERVA >RY wrote: > >> I have just upgraded my system to -current w/egcs 2.95.2 and I have >> several problems with it, especially when using optimizations (-O2 and >> such) > >When your code breaks when using -O2 or higher, don't do that, use >just -O! Ah, excuse me, but -O is equivalent to -O2. Thus, a better statement would have been: :When your code breaks when using -O3 or higher, don't do that, use :just -O! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 10:16:59 2000 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 DA0DB1544C for ; Wed, 5 Jan 2000 10:16:54 -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 LAA24782; Wed, 5 Jan 2000 11:16:29 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA20023; Wed, 5 Jan 2000 11:16:28 -0700 Date: Wed, 5 Jan 2000 11:16:28 -0700 Message-Id: <200001051816.LAA20023@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: Martin Cracauer , mauzi@poli.hu, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-Reply-To: <98339.947095734@monkeys.com> References: <20000105100716.A63545@cons.org> <98339.947095734@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 > [3] The ANSI C standard, at least, contains the requirement that each > individual system include file specified by that standard should > be usable all by itself, without the programmer being required to > explicitly include any OTHER system include files, prior to the one > he/she is actually interested in using. Can you quote me chapter and verse for this? I don't believe this to be true, and in truth, I believe this is completely wrong. Many system include files are *NOT* for public consumption. Also, include files should never include other include files, as this messes up dependencies. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 10:37: 6 2000 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 A880915599 for ; Wed, 5 Jan 2000 10:36:46 -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 KAA00780; Wed, 5 Jan 2000 10:36:17 -0800 (PST) To: Thomas David Rivers Cc: cracauer@cons.org, freebsd-hackers@FreeBSD.ORG, saska@acc.umu.se Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? In-reply-to: Your message of Wed, 05 Jan 2000 11:42:33 -0500. <200001051642.LAA26756@lakes.dignus.com> Date: Wed, 05 Jan 2000 10:36:17 -0800 Message-ID: <778.947097377@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001051642.LAA26756@lakes.dignus.com>, you wrote: > I don't believe the C89 standard doesn't have a way to test for NaN... That is correct, but most actual C libraries DO provide some function that will check for that condition. > ... so, if we're talking portability here - you can't test for NaN. Yes, but only if you are talking about ``portability'' in its purest form. In practice, you could easily construct an `is_this_a_NaN()' function that would work on all platforms of interest. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 10:37:50 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CD9751544D for ; Wed, 5 Jan 2000 10:37:44 -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 LAA07081; Wed, 5 Jan 2000 11:37:40 -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 LAA68897; Wed, 5 Jan 2000 11:37:40 -0700 (MST) Message-Id: <200001051837.LAA68897@harmony.village.org> To: nate@mt.sri.com (Nate Williams) Subject: Re: [OFFTOPIC] alt. C compiler Cc: "Ronald F. Guilmette" , Martin Cracauer , mauzi@poli.hu, hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Jan 2000 11:16:28 MST." <200001051816.LAA20023@mt.sri.com> References: <200001051816.LAA20023@mt.sri.com> <20000105100716.A63545@cons.org> <98339.947095734@monkeys.com> Date: Wed, 05 Jan 2000 11:37:40 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001051816.LAA20023@mt.sri.com> Nate Williams writes: : > [3] The ANSI C standard, at least, contains the requirement that each : > individual system include file specified by that standard should : > be usable all by itself, without the programmer being required to : > explicitly include any OTHER system include files, prior to the one : > he/she is actually interested in using. : : Can you quote me chapter and verse for this? I don't believe this to be : true, and in truth, I believe this is completely wrong. I don't think he can. The only requirements that it has are that some header files not pull other header files in to define certain things. NULL can be defined in a number of different places, for example, but if you include stdlib.h or stddef.h for it, you don't get stdio.h. This is explained in more detail in section 7.1.1.4 of the August 3, 1998 committee draft: 7.1.1 Library 7.1.2 ... [#2] The standard headers are ... [#4] Standard headers may be included in any order; each may be included more than once in a given scope, with no effect different from being included only once, except that the effect of including depends on the definition of NDEBUG (see 7.2). [...] However, if an identifier is declared or defined in more than one header, the second and subsequent associated headers may be included after the initial reference to the identifier.[...] ... Notice that these are for the *STANDARD* header files not the *SYSTEM* header files. This is much different than having sys/mublefoo.h depending on sys/types.h being included first. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 10:45:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 658BC15486 for ; Wed, 5 Jan 2000 10:45:08 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id MAA31309; Wed, 5 Jan 2000 12:44:40 -0600 (CST) (envelope-from dan) Date: Wed, 5 Jan 2000 12:44:40 -0600 From: Dan Nelson To: "Ronald F. Guilmette" Cc: Martin Cracauer , mauzi@poli.hu, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler Message-ID: <20000105124439.A28602@dan.emsphone.com> References: <20000105100909.B63545@cons.org> <99736.947095986@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <99736.947095986@monkeys.com>; from "Ronald F. Guilmette" on Wed Jan 5 10:13:06 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 05), Ronald F. Guilmette said: > Martin Cracauer wrote: > > > >When your code breaks when using -O2 or higher, don't do that, use > >just -O! > > Ah, excuse me, but -O is equivalent to -O2. /usr/src/contrib/gcc/toplev.c:4821 if (!strcmp (argv[i], "-O")) { optimize = 1; optimize_size = 0; } So, -O is equivalent to -O1. Go down one page from there, and you'll see the individual optiomizations enabled by each level. Also note that for stock gcc, there is nothing above -O3 (If you see someone using anything higher, you can be sure they're using pgcc). The -Os flag automatically sets -O2. -- 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 Wed Jan 5 10:48: 1 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5491E1559A for ; Wed, 5 Jan 2000 10:47:55 -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 LAA07157 for ; Wed, 5 Jan 2000 11:47:52 -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 LAA69088 for ; Wed, 5 Jan 2000 11:47:52 -0700 (MST) Message-Id: <200001051847.LAA69088@harmony.village.org> Subject: Re: [OFFTOPIC] alt. C compiler To: hackers@FreeBSD.ORG In-reply-to: Your message of "Wed, 05 Jan 2000 11:37:40 MST." Date: Wed, 05 Jan 2000 11:47:52 -0700 From: Warner Losh Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -------- Warner Losh writes: : This is explained in more detail in section 7.1.1.4 of the August 3, : 1998 committee draft: Sorry to followup on my own message, but this is in section 7.1.2.4. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 10:52:16 2000 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 B424215455 for ; Wed, 5 Jan 2000 10:52:04 -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 125vWY-0001zA-00; Wed, 05 Jan 2000 19:51:10 +0100 Received: from mauzi (helo=localhost) by aquarius.poli.hu with local-esmtp (Exim 3.12 #1) id 125vVd-0000Wt-00; Wed, 05 Jan 2000 19:50:13 +0100 Date: Wed, 5 Jan 2000 19:50:13 +0100 (CET) From: Gergely EGERVARY Reply-To: mauzi@poli.hu To: Brandon Fosdick Cc: hackers@freebsd.org Subject: Re: linux kld: sblive In-Reply-To: <38737EE2.D9544DBB@glue.umd.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 > So I've missed the whole discussion on the sblive driver timetable and > the archives didn't help much. And I just grabbed creative's source for > a linux driver from opensource.creative.com. Needless to say, it needs > some work before it will compile. Is anybody else working on this? I'm > tired of having a soundcard that I can't use so I'm tempted to jump into > this. I don't know anything about drivers, but I know that I'm tired of > waiting, are there any docs that might help me along? according to www.posi.net/freebsd/drivers someone is working on it, I've mailed him, and get no response (yet?) -- mauzi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 11: 5:43 2000 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 9D7D4151C9 for ; Wed, 5 Jan 2000 11:05:39 -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 LAA00966; Wed, 5 Jan 2000 11:05:19 -0800 (PST) To: Martin Cracauer Cc: Markus Holmberg , freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? In-reply-to: Your message of Wed, 05 Jan 2000 17:50:52 +0100. <20000105175051.A10840@cons.org> Date: Wed, 05 Jan 2000 11:05:19 -0800 Message-ID: <964.947099119@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000105175051.A10840@cons.org>, Martin Cracauer wrote: >In <91688.947090291@monkeys.com>, Ronald F. Guilmette wrote: >> ... >> Yes, the existing Mozilla code should be fixed to perform the range >> check in the manner that Martin Cracauer has >> shown above. However the can-of-worms opened up by this whole >> thread/discussion has revealed *two* bugs... one in the Mozilla >> code (which Martin Cracauer has correctly >> described, diagnosed, and provided a solution for) and also, there >> is still that annoying little deviation from the IEEE FP standard >> that results from FreeBSD's failure to disable all IEEE FP traps >> upon entry to main. >> >> _Both_ bugs should be fixed. > >As I said in the other message: This case is not covered by the IEEE >exceptions that may be disabled. Are there any IEEE exceptions for which traps MAY NOT be enabled or disabled?? The first sentence of IEEE 754 section 8 would seem to suggest that the answer is `no': ``A user should be able to request a trap an any of the five exceptions...'' >This case is a conversion of double -> int, it is not covered by >ieee754, but by ANSI C. Are you sure? My reading of IEEE 754 indicates that this situation is covered by *both* the ANSI C standard and also by IEEE 754. Specifically, IEEE 754, Section 7.1, subparagraph 7, seems to cover this exact case, and seems to mandate an IEEE invalid operation exception for this exact case, i.e. conversion of an IEEE floatint-point number to an int where the int is too small to hold the actual converted value. >And the ANSI C standard has its own paragraph >for exactly this case and its own sentense that if the the double is >out of range the behaviour is undefined. Correct. And for the Mozilla programmers, the ANSI C rule is the only one of importance, because it effectively says that their code has a serious bug. But both rules (ANSI C and IEEE 754) _do_ apply. >Really, what else do you want? Its not that hard to understand really. I want: a) a world in which all Mozilla code conforms as strictly as possible to both the ANSI/ISO C standard and also as strictly as possible to the IEEE 754 standard, _and_ I want... b) a world in which FreeBSD conforms as closely as possible to (among other things) IEEE 754, e.g. with all IEEE FP traps disabled upon entry to main(). It is possible to have both without too much difficulty. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 11:11:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id 494E31541E; Wed, 5 Jan 2000 11:11:18 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas4-46-6.dial.proxad.net [212.27.46.6]) by postfix2.free.fr (Postfix) with ESMTP id 3F72A7450A; Wed, 5 Jan 2000 20:11:16 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id VAA00866; Tue, 4 Jan 2000 21:00:15 +0100 (CET) (envelope-from nsouch) Message-ID: <20000104210015.63255@breizh.free.fr> Date: Tue, 4 Jan 2000 21:00:15 +0100 From: Nicolas Souchu To: Maxim Sobolev Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP newppbus for beta-testing References: <20000103004910.41467@armor.free.fr> <3870F784.2B1E8126@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <3870F784.2B1E8126@altavista.net>; from Maxim Sobolev on Mon, Jan 03, 2000 at 09:24:52PM +0200 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 03, 2000 at 09:24:52PM +0200, Maxim Sobolev wrote: > >Nicolas Souchu wrote: > >> Hi there! >> >> FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current >> >> A major ppbus(4) release is available for beta-testing. > >Good work! Now plip, which has been broken for ages, works perfectly - no more >lockups, spontaneous reboots, panics, etc! To test it I even managed to get X >and NFS working over plip line, things which was impossible with oldppbus. Nice! But, sure the 'net' interrupt level mask (at the ppc0 declaration) in you MACHINE config file would have done the job. > >Count on my vote to commit it before branch split because IMHO it should be >considered as a bugfix rather that a new feature. > >-Maxim > Nicholas -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 11:20:58 2000 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 33298151C9 for ; Wed, 5 Jan 2000 11:20:54 -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 LAA01057; Wed, 5 Jan 2000 11:20:26 -0800 (PST) To: nate@mt.sri.com (Nate Williams) Cc: Martin Cracauer , mauzi@poli.hu, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of Wed, 05 Jan 2000 11:16:28 -0700. <200001051816.LAA20023@mt.sri.com> Date: Wed, 05 Jan 2000 11:20:26 -0800 Message-ID: <1055.947100026@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001051816.LAA20023@mt.sri.com>, you wrote: >> [3] The ANSI C standard, at least, contains the requirement that each >> individual system include file specified by that standard should >> be usable all by itself, without the programmer being required to >> explicitly include any OTHER system include files, prior to the one >> he/she is actually interested in using. > >Can you quote me chapter and verse for this? I don't believe this to be >true, and in truth, I believe this is completely wrong. ANSI 4.1.2: The header declares a set of related functions, plus any necessary types and additional macros needs to facilitate their use. (And if _that_ is not enough to convince you, then I'll just turn the question around... from _me_ having to prove a negative to _you_ having to prove a positive... and ask you to cite chapter and verse where the ANSI C standard sez that you have to include X before you include Y.) >Many system include files are *NOT* for public consumption. Note that I was _very careful_ to say only that the system include files SPECIFIED BY THE ANSI C STANDARD must be able to be included by themselves. Every system I've ever worked on provides LOTS of system include files above and beyond those required by (or mentioned in) the ANSI C standard. Should the ANSI C requirement relating to ``stand alone'' inclusion apply also to _every_ system include file, e.g. on FreeBSD. My own personal opinion is that the answer is ``yes'', if for no other reason, then just because that would make compiler-assisted routine QA of all of the system include files much easier. (It also would make life a bit simpler for programmers too, but we don't care about them, right? :-) >Also, include files should never include other include files... Really? Who said that?? >... as this messes up dependencies. Doesn't for me. Maybe you're doing something wrong. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 11:26: 9 2000 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 CE3BB151FB for ; Wed, 5 Jan 2000 11:26:06 -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 LAA01131; Wed, 5 Jan 2000 11:25:13 -0800 (PST) To: Dan Nelson Cc: Martin Cracauer , mauzi@poli.hu, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of Wed, 05 Jan 2000 12:44:40 -0600. <20000105124439.A28602@dan.emsphone.com> Date: Wed, 05 Jan 2000 11:25:13 -0800 Message-ID: <1129.947100313@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000105124439.A28602@dan.emsphone.com>, you wrote: >In the last episode (Jan 05), Ronald F. Guilmette said: >> Martin Cracauer wrote: >> > >> >When your code breaks when using -O2 or higher, don't do that, use >> >just -O! >> >> Ah, excuse me, but -O is equivalent to -O2. > >/usr/src/contrib/gcc/toplev.c:4821 > > if (!strcmp (argv[i], "-O")) > { > optimize = 1; > optimize_size = 0; > } > >So, -O is equivalent to -O1. OH MY GOD! You're right, and I stand corrected. Once upon a time, -O *was* equivalent to -O2, but it appears that this got changed somewhere along the way. (I'm glad that you pointed out my faux pas... I won't be using just -O with gcc anymore!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 11:35:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 9028315120 for ; Wed, 5 Jan 2000 11:35:56 -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 OAA17052 for ; Wed, 5 Jan 2000 14:35:51 -0500 (EST) Date: Wed, 5 Jan 2000 13:22:00 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: Post a signal within an interrupt handler 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 While reading the code vfs_aio.c, I find out some comments saying it is not safe to post a signal from the interrupt handler aio_physwakeup(). So it calls timeout(9) within that handler and let the timeout routine to post the signal. I do not understand this. Isn't the timeout mechanism also driven by an interrupt (clock)? Any enlightment 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 Wed Jan 5 11:50:40 2000 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 9ABBE15545 for ; Wed, 5 Jan 2000 11:50:28 -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 LAA01470; Wed, 5 Jan 2000 11:50:12 -0800 (PST) To: Martin Cracauer Cc: hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of Wed, 05 Jan 2000 10:07:16 +0100. <20000105100716.A63545@cons.org> Date: Wed, 05 Jan 2000 11:50:12 -0800 Message-ID: <1468.947101812@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000105100716.A63545@cons.org>, Martin Cracauer wrote: >... If you have examples where it breaks, send them to me, please. Here is a list of a few system include file problems, in no particular order. Most of these are ANSI conformance problems. /usr/include/cam/cam.h:153: comma at end of enumerator list /usr/include/cam/cam_ccb.h:478: comma at end of enumerator list /usr/include/cam/cam_ccb.h:487: comma at end of enumerator list /usr/include/cam/cam_ccb.h:494: comma at end of enumerator list /usr/include/cam/cam_ccb.h:739: comma at end of enumerator list /usr/include/cam/cam_ccb.h:92: ANSI C restricts enumerator values to range of `int' /usr/include/cam/cam_ccb.h:97: ANSI C restricts enumerator values to range of `int' /usr/include/cam/cam_ccb.h:98: comma at end of enumerator list /usr/include/cam/scsi/scsi_cd.h:132: ANSI C does not allow extra `;' outside of a function /usr/include/cam/scsi/scsi_targetio.h:48: comma at end of enumerator list /usr/include/machine/cons.h:8: i386/i386/cons.h: No such file or directory /usr/include/machine/ipl.h:42: i386/isa/icu_ipl.h: No such file or directory /usr/include/machine/mpapic.h:33: i386/isa/icu.h: No such file or directory /usr/include/machine/pcb.h:82: structure has no members /usr/include/posix4/posix4.h:36: opt_posix.h: No such file or directory /usr/include/stand.h:311: arguments given to macro `getchar' /usr/include/sys/chio.h:155: comma at end of enumerator list /usr/include/sys/namei.h:169: ANSI C forbids zero-size array `nc_name' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 11:55: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 2219C14A0D for ; Wed, 5 Jan 2000 11:55:00 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id OAA16171; Wed, 5 Jan 2000 14:54:37 -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 OAA08873; Wed, 5 Jan 2000 14:54:35 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id OAA32472; Wed, 5 Jan 2000 14:54:35 -0500 (EST) Date: Wed, 5 Jan 2000 14:54:35 -0500 (EST) From: Thomas David Rivers Message-Id: <200001051954.OAA32472@lakes.dignus.com> To: cracauer@cons.org, rfg@monkeys.com Subject: Re: [OFFTOPIC] alt. C compiler Cc: hackers@FreeBSD.ORG In-Reply-To: <1468.947101812@monkeys.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > In message <20000105100716.A63545@cons.org>, > Martin Cracauer wrote: > > >... If you have examples where it breaks, send them to me, please. > > Here is a list of a few system include file problems, in no particular > order. Most of these are ANSI conformance problems. > > > /usr/include/cam/cam.h:153: comma at end of enumerator list > /usr/include/cam/cam_ccb.h:478: comma at end of enumerator list > /usr/include/cam/cam_ccb.h:487: comma at end of enumerator list > /usr/include/cam/cam_ccb.h:494: comma at end of enumerator list > /usr/include/cam/cam_ccb.h:739: comma at end of enumerator list > /usr/include/cam/cam_ccb.h:92: ANSI C restricts enumerator values to range of `int' > /usr/include/cam/cam_ccb.h:97: ANSI C restricts enumerator values to range of `int' > /usr/include/cam/cam_ccb.h:98: comma at end of enumerator list > /usr/include/cam/scsi/scsi_cd.h:132: ANSI C does not allow extra `;' outside of a function > /usr/include/cam/scsi/scsi_targetio.h:48: comma at end of enumerator list > /usr/include/machine/cons.h:8: i386/i386/cons.h: No such file or directory > /usr/include/machine/ipl.h:42: i386/isa/icu_ipl.h: No such file or directory > /usr/include/machine/mpapic.h:33: i386/isa/icu.h: No such file or directory > /usr/include/machine/pcb.h:82: structure has no members > /usr/include/posix4/posix4.h:36: opt_posix.h: No such file or directory > /usr/include/stand.h:311: arguments given to macro `getchar' > /usr/include/sys/chio.h:155: comma at end of enumerator list > /usr/include/sys/namei.h:169: ANSI C forbids zero-size array `nc_name' This begs a question.... and to help in my understanding... Certainly, these header files aren't ANSI conforming. But - that's not to say we don't have an ANSI conforming C implementation, as these aren't ANSI header files - right? That is; isn't it true that in our "own" header files - we can do whatever we want? - 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 Jan 5 11:57:20 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fysgr387.sn.umu.se (fysgr387.sn.umu.se [130.239.128.239]) by hub.freebsd.org (Postfix) with ESMTP id 532951509F for ; Wed, 5 Jan 2000 11:57:02 -0800 (PST) (envelope-from saska@fysgr387.sn.umu.se) Received: by fysgr387.sn.umu.se (Postfix, from userid 1000) id 585BBA837; Wed, 5 Jan 2000 20:59:47 +0100 (CET) Date: Wed, 5 Jan 2000 20:59:47 +0100 From: Markus Holmberg To: Martin Cracauer Cc: freebsd-hackers@freebsd.org Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000105205947.A77037@fysgr387.sn.umu.se> References: <20000104121459.A8959@cons.org> <87632.947017515@monkeys.com> <20000105055138.A74746@fysgr387.sn.umu.se> <20000105092356.A8100@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000105092356.A8100@cons.org>; from cracauer@cons.org on Wed, Jan 05, 2000 at 09:23:57AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 05, 2000 at 09:23:57AM +0100, Martin Cracauer wrote: > > > > #define JSDOUBLE_IS_INT(d, i) (JSDOUBLE_IS_FINITE(d) && \ > > !JSDOUBLE_IS_NEGZERO(d) && ((d) == (i = (jsint)(d)))) > > Ah, OK, this macro is a conversion where the undefined result of the > (int)double_bigger_max_int is (intentionally) used as a speed hack of > a range check. Unfortunately I think it's used as more than just a range check. It also checks if the floating point part of the value is 0, as in a "true" integer, not just if the integer part is in range of the int type. > static inline int cra_is_int(const double d, int *const i) > { > if (d <= (double)INT_MAX && d >= (double)INT_MIN) { > *i = (int)d; > return 1; > } else > return 0; > } If this is used then for example the double 3.14159 would return true, when the intention was that it should return false, because the double has a floating point part, and hence cannot be stored as an integer without data loss. Martin, your solution looked great, but if my observations are correct I'm afraid we are back to square one with fpsetmask(). :( Of course, an option would be to add a check for the floating point part in Martin's suggested c function, but that would add a lot of overhead which the responsible people for this code won't accept since JSDOUBLE_IS_INT is a frequently used macro. If anyone got a suggestion for a clean way to do this check.. Speak up :). Markus -- 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 Wed Jan 5 12: 9:56 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mycenae.ilion.eu.org (mycenae.ilion.eu.org [203.35.206.129]) by hub.freebsd.org (Postfix) with ESMTP id B620515078 for ; Wed, 5 Jan 2000 12:09:48 -0800 (PST) (envelope-from patrykz@ilion.eu.org) Received: from mycenae.ilion.eu.org (localhost [127.0.0.1]) by mycenae.ilion.eu.org (8.9.3/8.9.3) with ESMTP id HAA14707; Thu, 6 Jan 2000 07:08:54 +1100 (EST) (envelope-from patrykz@mycenae.ilion.eu.org) Message-Id: <200001052008.HAA14707@mycenae.ilion.eu.org> To: Oliver Fromme Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of "Wed, 05 Jan 2000 18:02:01 BST." <200001051702.SAA36755@dorifer.heim3.tu-clausthal.de> Date: Thu, 06 Jan 2000 07:08:53 +1100 From: Patryk Zadarnowski Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Martin Cracauer wrote in list.freebsd-hackers: > > You will not be able to use all features of FreeBSD, of course. > > Calling functions that take long long arguments doesn't work, these > > should be masked out when compiling struct ansi code. It may get > > painful quickly, as such basic things like seek() are amoung them. > > ``long long'' is part of the C9x standard (or whatever it is > called now, I'm not an expert). If TenDRA (or lcc) supports > the latest C standard, then there should be no problem. TenDRA has no problem parsing any of the FreeBSD headers as far as I know (and supports long long), although, of course, nobody in their right mind supports the moving target that C9X is (it's C9X that supports GCC, not the other way around ;) Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 12:13:27 2000 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 EB4FD14D9D for ; Wed, 5 Jan 2000 12:13:22 -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 MAA01643; Wed, 5 Jan 2000 12:13:03 -0800 (PST) To: Thomas David Rivers Cc: cracauer@cons.org, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of Wed, 05 Jan 2000 14:54:35 -0500. <200001051954.OAA32472@lakes.dignus.com> Date: Wed, 05 Jan 2000 12:13:03 -0800 Message-ID: <1641.947103183@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001051954.OAA32472@lakes.dignus.com>, Thomas David Rivers wrote: rfg> Here is a list of a few system include file problems, in no particular rfg> order. Most of these are ANSI conformance problems. rfg> ... {bugz elided} ... > This begs a question.... and to help in my understanding... > > Certainly, these header files aren't ANSI conforming. That is correct. > But - that's not to say we don't have an ANSI conforming C implementation, That is also correct. > as these aren't ANSI header files - right? Right. Those are not header files that are mandated by the ANSI C standard and thus, the ANSI C standard also does not mandate that they be conformant with the standard before you can claim that you have a conforming ANSI C implementation. > That is; isn't it true that in our "own" header files - we can do whatever > we want? You're talking about the difference between the strict letter of the law, and pragmatic usefulness. Yes, according to the strict letter of the law, all of these other system include files don't even have to exist, and if they do exist, they could contain any garbage you want, including random binary bytes that drive the compiler absolutely mad. The ANSI C standard has _nothing_ to say about any system include files _except_ the very limited set that the ANSI C standard actually mandates and talks about. But pragmatically, it sure would be nice if I (or you) as a programmer developing stuff on FreeBSD could include various of the FreeBSD include files into any program that we happen to be working on, and then fire up the compiler (with our own personal favorite set of command line options) and then _not_ be plagued by a whole bunch of spurious warnings and/or errors that have noting actually to do with _our_ code. This isn't about standards conformance. It is about providing a top quality _complete_ software developement system/environment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 12:27:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id 8929014DAA for ; Wed, 5 Jan 2000 12:27:44 -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 PAA13333; Wed, 5 Jan 2000 15:27:33 -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 PAA08927; Wed, 5 Jan 2000 15:27:29 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id PAA32580; Wed, 5 Jan 2000 15:27:28 -0500 (EST) Date: Wed, 5 Jan 2000 15:27:28 -0500 (EST) From: Thomas David Rivers Message-Id: <200001052027.PAA32580@lakes.dignus.com> To: rfg@monkeys.com, rivers@dignus.com Subject: Re: [OFFTOPIC] alt. C compiler Cc: cracauer@cons.org, hackers@FreeBSD.ORG In-Reply-To: <1641.947103183@monkeys.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yes, according to the strict letter of the law, all of these other system > include files don't even have to exist, and if they do exist, they could > contain any garbage you want, including random binary bytes that drive the > compiler absolutely mad. The ANSI C standard has _nothing_ to say about > any system include files _except_ the very limited set that the ANSI C > standard actually mandates and talks about. > > But pragmatically, it sure would be nice if I (or you) as a programmer > developing stuff on FreeBSD could include various of the FreeBSD include > files into any program that we happen to be working on, and then fire up > the compiler (with our own personal favorite set of command line options) > and then _not_ be plagued by a whole bunch of spurious warnings and/or > errors that have noting actually to do with _our_ code. > > This isn't about standards conformance. It is about providing a top > quality _complete_ software developement system/environment. > Ok - i just wanted to be clear what exactly we're talking about. We're talking about making it easier to use the FreeBSD library code in other programs (i.e. `port' it somewhere) - presumably with a strict ANSI C compiler other than gcc. While that is certainly a laudable goal - I question the term "pragmatic". Just how often is this going to happen? Is it worth the effort? [These are questions that likely should be asked... - I'm just the Devil's advocate here..., personally - I agree... it would be nice to have "ANSI-clean" header files.] - 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 Jan 5 12:44:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-relay.eunet.no (mail-relay.eunet.no [193.71.71.242]) by hub.freebsd.org (Postfix) with ESMTP id DD68E154C8; Wed, 5 Jan 2000 12:44:23 -0800 (PST) (envelope-from mbendiks@eunet.no) Received: from login-1.eunet.no (mbendiks@login-1.eunet.no [193.75.110.2]) by mail-relay.eunet.no (8.9.3/8.9.3/GN) with ESMTP id VAA74242; Wed, 5 Jan 2000 21:44:21 +0100 (CET) (envelope-from mbendiks@eunet.no) Received: from localhost (mbendiks@localhost) by login-1.eunet.no (8.9.3/8.8.8) with ESMTP id VAA61703; Wed, 5 Jan 2000 21:44:21 +0100 (CET) (envelope-from mbendiks@eunet.no) X-Authentication-Warning: login-1.eunet.no: mbendiks owned process doing -bs Date: Wed, 5 Jan 2000 21:44:21 +0100 (CET) From: Marius Bendiksen To: Kenny Drobnack Cc: freebsd-hackers@FreeBSD.ORG, freebsd-fs@FreeBSD.ORG Subject: Re: CD-RW long filenames/rw filesystem. 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 > it, is grab a bunch of stuff you want to backup/record and use mkisofs and Use mkhybrid instead of mkisofs. It allows long filenames. > the CD-RW and then delete it later if you want to. Would it be possible, > or even feasible, to implement something like this in FreeBSD? Probably, but is there really much demand for this in a server OS? You can blank the CD-RW medium, with wormcontrol... - marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 12:46: 2 2000 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 5B1AC157C8 for ; Wed, 5 Jan 2000 12:45:33 -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 MAA01816; Wed, 5 Jan 2000 12:45:11 -0800 (PST) To: Thomas David Rivers Cc: cracauer@cons.org, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler In-reply-to: Your message of Wed, 05 Jan 2000 15:27:28 -0500. <200001052027.PAA32580@lakes.dignus.com> Date: Wed, 05 Jan 2000 12:45:11 -0800 Message-ID: <1814.947105111@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001052027.PAA32580@lakes.dignus.com>, Thomas David Rivers wrote: >> But pragmatically, it sure would be nice if I (or you) as a programmer >> developing stuff on FreeBSD could include various of the FreeBSD include >> files into any program that we happen to be working on, and then fire up >> the compiler (with our own personal favorite set of command line options) >> and then _not_ be plagued by a whole bunch of spurious warnings and/or >> errors that have noting actually to do with _our_ code. >> >> This isn't about standards conformance. It is about providing a top >> quality _complete_ software developement system/environment. >> > > Ok - i just wanted to be clear what exactly we're talking about. > > We're talking about making it easier to use the FreeBSD library code > in other programs (i.e. `port' it somewhere) - presumably with a > strict ANSI C compiler other than gcc. > > While that is certainly a laudable goal - I question the term "pragmatic". > Just how often is this going to happen? Is it worth the effort? > [These are questions that likely should be asked... - I'm just the > Devil's advocate here..., personally - I agree... it would be nice > to have "ANSI-clean" header files.] It would be more than `nice'. I consider it critical. And this has nothing to do with ``porting'' FreeBSD's library code... well... very little anyway. It mostly has to do with the portability of _my_ application code, and your's, and his, and everybody's. Anyone who is developing code that they *really* want to be ultra-portable and who is using gcc during the development *will* use the -pedantic-errors gcc compiler option for all of his/her compiles. I do this routinely. Often however, when doing that, I get spurious errors (relating to some system include file or another) that has nothing to do with _my_ code whatsoever. And that is most annoying when it happens. Keep in mind also that we are only talking now about ANSI conformance problems with the system include files. But as the list of system include file problems I just posted shows, some of the FreeBSD 3.3 system include files have a some even more glaring errors that go well beyond being mere ANSI conformance issues... like all those cases where header X tries to include header Y, and where the file Y doesn't even exist. Those are outright bugs in the relevant include files that will bite you no matter what compilation options you are using. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 12:46:46 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (Postfix) with ESMTP id DA18D157C8 for ; Wed, 5 Jan 2000 12:46:40 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with ESMTP id VAA17772 for ; Wed, 5 Jan 2000 21:46:50 +0100 (MET) Date: Wed, 5 Jan 2000 21:46:46 +0100 (MET) From: Marcin Cieslak To: freebsd-hackers@freebsd.org Subject: syscons: SC_MOUSE_CHAR value rationale 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 any _particular_ reason why this is #define'd to (0xd0) in /sys/dev/syscons/syscons.c? Nearly everyone who wants to set up their national locale needs to recompile the kernel, since some important characters are hidden under mouse cursor. I sure that at least these are affected: (from /usr/share/syscons/font) iso-8859-2-8x16.fnt iso02-8x8.fnt koi8-r-8x8.fnt iso02-8x14.fnt koi8-r-8x14.fnt koi8-rb-8x16.fnt iso02-8x16.fnt koi8-r-8x16.fnt koi8-rc-8x16.fnt Will changing it to 0x08 break anything? -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 12:59:33 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fysgr387.sn.umu.se (fysgr387.sn.umu.se [130.239.128.239]) by hub.freebsd.org (Postfix) with ESMTP id 2D1B115520 for ; Wed, 5 Jan 2000 12:59:28 -0800 (PST) (envelope-from saska@fysgr387.sn.umu.se) Received: by fysgr387.sn.umu.se (Postfix, from userid 1000) id B900FA837; Wed, 5 Jan 2000 22:02:18 +0100 (CET) Date: Wed, 5 Jan 2000 22:02:18 +0100 From: Markus Holmberg To: Martin Cracauer Cc: freebsd-hackers@freebsd.org Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000105220218.A77259@fysgr387.sn.umu.se> References: <20000104121459.A8959@cons.org> <87632.947017515@monkeys.com> <20000105055138.A74746@fysgr387.sn.umu.se> <20000105092356.A8100@cons.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000105092356.A8100@cons.org>; from cracauer@cons.org on Wed, Jan 05, 2000 at 09:23:57AM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, so the saga goes on. Here's a reply to Martins mail (that was posted on Bugzilla as a comment to the relevant bug). This discussion was on it's way becoming a Mozilla issue, and hence not belong on freebsd-hackers, but the comment from waldemar@netscape.com suggests that it *is* a question of standards compliance from the OS side. But I'm not sure I understand the difference between "undefined" and "unspecified"? (What a cast from double to int should return when the source doesn't fit into the destination). I'm about to give up on this.. For some (to me) unclear reason there are no intentions on making FreeBSD behave conforming to IEEE 754, and it's not clear if the Mozilla code is correct or not. Just want Mozilla work on FreeBSD too :/. (Should be in everyones interest) Put yourself on the cc: list of http://bugzilla.mozilla.org/show_bug.cgi?id=9967 to get updates and following the development if you're interested. (As I'm not sure if the discussion of the Mozilla code belongs on freebsd-hackers.. Though discussion of IEEE 754 conformance certainly does). Markus --- FORWARDED MAIL-- -------------------------------------------------------- From: bugzilla-daemon@mozilla.org To: mccabe@netscape.com, robinson@netrinsics.com, cbegle@netscape.com Cc: saska@acc.umu.se, briano@netscape.com, gatgul@voicenet.com, brendan@mozilla.org, daeron@Wit401305.student.utwente.nl, clayton@netscape.com, skumle@grin.dk Subject: [Bug 9967] Changed - JSDOUBLE_IS_INT throws SIGFPE without integer range check http://bugzilla.mozilla.org/show_bug.cgi?id=9967 *** shadow/9967 Wed Jan 5 09:50:21 2000 --- shadow/9967.tmp.4454 Wed Jan 5 12:32:59 2000 *************** *** 379,381 **** --- 379,409 ---- Martin + + ------- Additional Comments From waldemar@netscape.com 2000-01-05 12:32 ------- + It's not as simple as you state. The code you propose has three programming + bugs: + + 1. It doesn't work for NaN under MSVC due to a bug in MSVC. + 2. It doesn't work for -0.0. + 3. It doesn't work for any non-integral number (such as 1.5) between INT_MIN and + INT_MAX. + + The old C standard specified that a double-to-int conversion is undefined if the + source value can't fit in the destination value. However, the new C9X standard + differs here: if an implementation supports IEEE 754, then it should set the + invalid exception flag and return an unspecified result (paragraph F.4). + Trapping on flags is to be turned off by default. (If an implementation doesn't + support IEEE 754, then the point is moot because the ECMAScript standard requires + IEEE 754.) + + + Note: The finiteness range check is there only to work around the MSVC NaN bug + and is not needed on correctly-behaving platforms such as the Mac. On a + correctly implemented platform the following is sufficient: + + #define JSDOUBLE_IS_INT(d, i) (((d) == (i = (jsint)(d))) && + !JSDOUBLE_IS_NEGZERO(d)) + + Waldemar + -- 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 Wed Jan 5 13: 7: 2 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 43E5114C05 for ; Wed, 5 Jan 2000 13:07:00 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id QAA01362; Wed, 5 Jan 2000 16:06:57 -0500 (EST) (envelope-from luoqi) Date: Wed, 5 Jan 2000 16:06:57 -0500 (EST) From: Luoqi Chen Message-Id: <200001052106.QAA01362@lor.watermarkgroup.com> To: freebsd-hackers@FreeBSD.ORG, zzhang@cs.binghamton.edu Subject: Re: Post a signal within an interrupt handler Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While reading the code vfs_aio.c, I find out some comments saying it is > not safe to post a signal from the interrupt handler aio_physwakeup(). So > it calls timeout(9) within that handler and let the timeout routine to > post the signal. I do not understand this. Isn't the timeout mechanism > also driven by an interrupt (clock)? > > Any enlightment is appreciated. > > -Zhihui > AFAIK it is safe to post a signal in an interrupt context. Maybe it has more to do with reducing interrupt latency than safety. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 13:36:43 2000 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 C41F514E7F for ; Wed, 5 Jan 2000 13:36:40 -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 NAA02606; Wed, 5 Jan 2000 13:36:29 -0800 (PST) To: Markus Holmberg Cc: Martin Cracauer , freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? In-reply-to: Your message of Wed, 05 Jan 2000 22:02:18 +0100. <20000105220218.A77259@fysgr387.sn.umu.se> Date: Wed, 05 Jan 2000 13:36:29 -0800 Message-ID: <2604.947108189@monkeys.com> From: "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000105220218.A77259@fysgr387.sn.umu.se>, you wrote: >But I'm not sure I understand the difference between "undefined" and >"unspecified"? (What a cast from double to int should return when the source >doesn't fit into the destination). The C standard talks about "undefined behavior", and when it does, that means that *aynthing* goes. When you get into a undefined behavior situation, it's a lot like being catapulted into the 11th dimension... time may flow sideways, whales may fall from the sky, and your CPU may suddenly revert to 4004 compatibility mode. :-) We're talking about quantum level uncertainty, multiplied by a googleplex. On the other hand, the word "unspecified" is usually use in conjunction with the word "value", as in ``... and unspecified value in the range INT_MIN .. INT_MAX''. This is a far more constrained type of uncertainty. >I'm about to give up on this.. For some (to me) unclear reason there are >no intentions on making FreeBSD behave conforming to IEEE 754... I hope that isn't true. _I_ certainly haven't yet given up hope that someone will do the Right Thing and disable all IEEE traps before entry to main(). >... and it's not clear if the Mozilla code is correct or not. It isn't. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 13:48:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from po3.glue.umd.edu (po3.glue.umd.edu [128.8.10.123]) by hub.freebsd.org (Postfix) with ESMTP id 8A38015476 for ; Wed, 5 Jan 2000 13:48:12 -0800 (PST) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.220.99]) by po3.glue.umd.edu (8.9.3/8.9.3) with ESMTP id QAA25374; Wed, 5 Jan 2000 16:48:04 -0500 (EST) Message-ID: <3873BBFE.AFB2D0A4@glue.umd.edu> Date: Wed, 05 Jan 2000 16:47:42 -0500 From: Brandon Fosdick X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: mauzi@poli.hu Cc: hackers@freebsd.org Subject: Re: linux kld: sblive References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gergely EGERVARY wrote: > > > So I've missed the whole discussion on the sblive driver timetable and > > the archives didn't help much. And I just grabbed creative's source for > > a linux driver from opensource.creative.com. Needless to say, it needs > > some work before it will compile. Is anybody else working on this? I'm > > tired of having a soundcard that I can't use so I'm tempted to jump into > > this. I don't know anything about drivers, but I know that I'm tired of > > waiting, are there any docs that might help me along? > > according to www.posi.net/freebsd/drivers someone is working on it, I've > mailed him, and get no response (yet?) > > -- mauzi I saw that after I had already posted. I haven't gotten a response yet either. -Brandon -- bfoz@glue.umd.edu "Lead, follow, or get run over" "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 14:45:21 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A89F14D04; Wed, 5 Jan 2000 14:45:07 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup1-19.iptelecom.net.ua [212.9.226.19]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id AAA29920; Thu, 6 Jan 2000 00:48:16 +0200 (EET) Message-ID: <3873C990.70D294F7@altavista.net> Date: Thu, 06 Jan 2000 00:45:36 +0200 From: Maxim Sobolev Organization: Home, sweet home X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Nicolas Souchu Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP newppbus for beta-testing References: <20000103004910.41467@armor.free.fr> <3870F784.2B1E8126@altavista.net> <20000104210015.63255@breizh.free.fr> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Souchu wrote: > On Mon, Jan 03, 2000 at 09:24:52PM +0200, Maxim Sobolev wrote: > > > >Nicolas Souchu wrote: > > > >> Hi there! > >> > >> FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current > >> > >> A major ppbus(4) release is available for beta-testing. > > > >Good work! Now plip, which has been broken for ages, works perfectly - no more > >lockups, spontaneous reboots, panics, etc! To test it I even managed to get X > >and NFS working over plip line, things which was impossible with oldppbus. > > Nice! But, sure the 'net' interrupt level mask (at the ppc0 declaration) > in you MACHINE config file would have done the job. Unfortunately it is not a solution because net,tty and bio keywords went away from config(8) long time ago... I've only received `syntax error' message. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 15:19:54 2000 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 E3BCD14D9D for ; Wed, 5 Jan 2000 15:19:51 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id AAA12539; Thu, 6 Jan 2000 00:19:15 +0100 (CET) Date: Thu, 6 Jan 2000 00:19:14 +0100 From: Martin Cracauer To: "Ronald F. Guilmette" Cc: Dan Nelson , Martin Cracauer , mauzi@poli.hu, hackers@FreeBSD.ORG Subject: Re: [OFFTOPIC] alt. C compiler Message-ID: <20000106001914.A12522@cons.org> References: <20000105124439.A28602@dan.emsphone.com> <1129.947100313@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <1129.947100313@monkeys.com>; from rfg@monkeys.com on Wed, Jan 05, 2000 at 11:25:13AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <1129.947100313@monkeys.com>, Ronald F. Guilmette wrote: > >So, -O is equivalent to -O1. [...] > (I'm glad that you pointed out my faux pas... I won't be using just -O > with gcc anymore!) Is this sentense missing a smiley? I hope so, since this is the attitude that got you intro trouble in first place. 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 Jan 5 15:33:39 2000 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 E5D5A15560 for ; Wed, 5 Jan 2000 15:33:31 -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 e05NWSr84505 for ; Wed, 5 Jan 2000 16:32:29 -0700 (MST) Message-Id: <200001052332.e05NWSr84505@orthanc.ab.ca> To: freebsd-hackers@freebsd.org Subject: Reading kbd scancodes from userland Organization: The Frobozz Magic Homing Pigeon Company Date: Wed, 05 Jan 2000 16:32:28 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it possible to read the raw keyboard scancodes from a userland process? I can't find an ioctl for this. (This is 3.3-RELEASE+PAO3, atkbd and syscons.) Failing that, has anyone figured out a keyboard mapping for an Inspiron 7000 that puts the left ALT key back where it belongs? (The reason for the first request is to try to determine what effect the left ALT key actually has. On this laptop, the "windows" key does what left ALT normally does, making life miserable when running a non-win98 external keyboard.) --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 15:49:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30]) by hub.freebsd.org (Postfix) with ESMTP id 56E4B15481 for ; Wed, 5 Jan 2000 15:49:15 -0800 (PST) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id PAA26271; Wed, 5 Jan 2000 15:45:05 -0800 (PST) Date: Wed, 5 Jan 2000 15:45:05 -0800 (PST) From: Jim Shankland Message-Id: <200001052345.PAA26271@biggusdiskus.flyingfox.com> To: freebsd-hackers@FreeBSD.ORG, lyndon@orthanc.ab.ca Subject: Re: Reading kbd scancodes from userland In-Reply-To: <200001052332.e05NWSr84505@orthanc.ab.ca> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lyndon Nerenberg asks: > Is it possible to read the raw keyboard scancodes from a userland > process? I can't find an ioctl for this. (This is 3.3-RELEASE+PAO3, > atkbd and syscons.) Yup. Save the following as kbddump.c, then: cc -O kbddump.c -o kbddump ./kbddump Jim Shankland NLynx Systems, Inc. #include #include #include #include #include main(int argc, char *argv[]) { int fd; unsigned char onecode; int oldmode; int newmode = K_RAW; struct termios old_t, new_t; int rr; if (argc > 1 && strcmp(argv[1], "-k") == 0) newmode = K_CODE; if ((fd = open("/dev/ttyv0", O_RDWR)) < 0) { (void) fprintf(stderr, "/dev/kbd0: %s\n", strerror(errno)); exit(1); } if (ioctl(fd, KDGKBMODE, &oldmode) < 0) { (void) fprintf(stderr, "KDGKBMODE: %s\n", strerror(errno)); exit(1); } printf("Old mode is %d\n", oldmode); if (tcgetattr(fd, &old_t) != 0) { (void) fprintf(stderr, "tcgetattr: %s\n", strerror(errno)); exit(1); } new_t = old_t; cfmakeraw(&new_t); if (tcsetattr(fd, 0, &new_t) != 0) { (void) fprintf(stderr, "tcsetattr: %s\n", strerror(errno)); exit(1); } if (ioctl(fd, KDSKBMODE, newmode) < 0) { (void) tcsetattr(fd, 0, &old_t); (void) fprintf(stderr, "KDSKBMODE: %s\n", strerror(errno)); exit(1); } printf("Scancodes are in hexadecimal; program will terminate when the\r\n"); printf("'a' key is released (scancode 9e) ...\r\n\n"); while ((rr = read(fd, &onecode, 1)) > 0) { printf("Code: %02x\r\n", (unsigned) onecode); if (onecode == 0x9e) break; } if (rr < 0) { (void) fprintf(stderr, "keyboard read: %s\r\n", strerror(errno)); } (void) tcsetattr(fd, 0, &old_t); if (ioctl(fd, KDSKBMODE, oldmode) < 0) { (void) fprintf(stderr, "Danger, Will Robinson! Can't restore keyboard: %s\n", strerror(errno)); exit(1); } exit(0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 15:53:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 566481504C for ; Wed, 5 Jan 2000 15:53:26 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id RAA68613; Wed, 5 Jan 2000 17:52:40 -0600 (CST) (envelope-from dan) Date: Wed, 5 Jan 2000 17:52:40 -0600 From: Dan Nelson To: "Ronald F. Guilmette" Cc: Markus Holmberg , Martin Cracauer , freebsd-hackers@FreeBSD.ORG Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000105175240.A68089@dan.emsphone.com> References: <20000105220218.A77259@fysgr387.sn.umu.se> <2604.947108189@monkeys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <2604.947108189@monkeys.com>; from "Ronald F. Guilmette" on Wed Jan 5 13:36:29 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 05), Ronald F. Guilmette said: > I hope that isn't true. _I_ certainly haven't yet given up hope that > someone will do the Right Thing and disable all IEEE traps before > entry to main(). Take a look at /sys/i386/include/npx.h; I believe you can change the default FP mask there. Set __INITIAL_NPXCW__ to your favourite hex value, and rebuild the kernel. > >... and it's not clear if the Mozilla code is correct or not. > > It isn't. Aah, but we wouldn't have found the bug if FreeBSD hadn't caught it :) I prefer to trap by default. The very few programs that require IEEE conformance can call fpsetmask() themselves. -- 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 Wed Jan 5 16:25:27 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from addr2.addr.com (addr.com [209.249.147.252]) by hub.freebsd.org (Postfix) with ESMTP id 34E2515507; Wed, 5 Jan 2000 16:25:21 -0800 (PST) (envelope-from admin@addr.com) Received: from power2000 (gate.ipo.att.com [135.197.57.2]) by addr2.addr.com (8.9.3/8.9.1) with SMTP id QAA40421; Wed, 5 Jan 2000 16:23:13 -0800 (PST) (envelope-from admin@addr.com) Message-ID: <0c1901bf57dc$593db0a0$543bc587@power2000> From: "Anthony Bourov" To: "FreeBSD-Questions" Cc: "FreeBSD-Hackers" Subject: Upgrading from 3.0Release to 3.3Stable Date: Wed, 5 Jan 2000 16:24:08 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0C16_01BF5799.4A9D5160" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0C16_01BF5799.4A9D5160 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I have performed several live upgrades of FreeBSD before (3.0Stable to = 3.3Stable), and experienced no problems. However, I think there are more = differences in 3.0Release (basically, that was the first version that = supported SMP), and was hoping for some feed back. I know that the = kernel whitched from AOUT to ELF, so I need to install the new boot = loader. Will the new boot loader still be able to run the old kernel (in = case there are problems during the upgrade?). Also, currently the system compiles binaries by default into the ELF = format, and can run both AOUT and ELF. I am not sure, after the upgrade, = would the system still be able to execute AOUT binaries (or is there a = converter, just in case?). Please, if anyone is aware of any other issues, let me know (config file = differences, etc). The system is live, and I want to minimize any = downtime. Thank you very much in advance, Anthony ------=_NextPart_000_0C16_01BF5799.4A9D5160 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I have performed several live upgrades = of FreeBSD=20 before (3.0Stable to 3.3Stable), and experienced no problems. However, I = think=20 there are more differences in 3.0Release (basically, that was the first = version=20 that supported SMP), and was hoping for some feed back. I know that = the=20 kernel whitched from AOUT to ELF, so I need to install the new boot = loader. Will=20 the new boot loader still be able to run the old kernel (in case there = are=20 problems during the upgrade?).
Also, currently the system compiles = binaries by=20 default into the ELF format, and can run both AOUT and ELF. I am not = sure, after=20 the upgrade, would the system still be able to execute AOUT binaries (or = is=20 there a converter, just in case?).
Please, if anyone is aware of any other = issues, let=20 me know (config file differences, etc). The system is live, and I = want to=20 minimize any downtime.
 
Thank you very much in = advance,
Anthony
------=_NextPart_000_0C16_01BF5799.4A9D5160-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 17: 3:47 2000 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 836BF154FC for ; Wed, 5 Jan 2000 17:03:34 -0800 (PST) (envelope-from carbon-unit-1@urquell.pilsnet.sunet.se) Received: (from bd@localhost) by urquell.pilsnet.sunet.se (8.9.1/8.9.1) id CAA26873; Thu, 6 Jan 2000 02:01:52 +0100 (CET) (envelope-from carbon-unit-1@urquell.pilsnet.sunet.se) X-Authentication-Warning: urquell.pilsnet.sunet.se: bd set sender to carbon-unit-1@urquell.pilsnet.sunet.se using -f To: sthaug@nethelp.no Cc: Gerard Roudier , freebsd-hackers@FreeBSD.ORG Subject: Re: SYM driver saves the day (where NCR driver crashes) References: <97847.947023839@verdi.nethelp.no> From: Bjorn Danielsson Date: 06 Jan 2000 02:01:52 +0100 In-Reply-To: sthaug@nethelp.no's message of "Tue, 04 Jan 2000 23:10:39 +0100" Message-ID: Lines: 36 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote: > > Anyway, we recently switched to the SYM driver (version 0.12.0). The > machine has now been up for 16 days without a single crash, and we're > very optimistic that the SYM driver has cured the problem. Kudos and > thanks to Gerard Roudier! Me too. Thanks Gerard, and my personal thanks also to Ed Hall who pointed me in the right direction at the right moment. My newsfeed machine (with the sym driver) has been up for 20 days now, without a glitch except for this single log entry: (da0:sym0:0:0:0): READ(10). CDB: 28 0 0 df f7 75 0 0 80 0 (da0:sym0:0:0:0): RECOVERED ERROR info:dff7cc asc:13,0 (da0:sym0:0:0:0): Address mark not found for data field sks:80,3 (da0:sym0:0:0:0): READ(10). CDB: 28 0 0 df f7 c5 0 0 30 0 (da0:sym0:0:0:0): RECOVERED ERROR info:dff7cd asc:17,8 (da0:sym0:0:0:0): Recovered data without ECC - recommend rewrite But I couldn't see any error reports on the application level... The load is about 50 Mbit/s on the ethernet, and 3 Mbyte/s on each one of the two disks. The software is Diablo-1.25 (on FreeBSD-3.3). The machine is a Compaq Proliant 1850R (a strange Micro$oft-sucking bizarre creature, but yeah I already knew that). The main thing is, it works! Happy happy joy joy :) -- Bjorn 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 Jan 5 17: 8:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 7ADD214E55 for ; Wed, 5 Jan 2000 17:08:22 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA23895; Thu, 6 Jan 2000 11:35:36 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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 In-Reply-To: <20000105175240.A68089@dan.emsphone.com> Date: Thu, 06 Jan 2000 11:35:35 +1030 (CST) From: "Daniel O'Connor" To: Dan Nelson Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeB Cc: freebsd-hackers@FreeBSD.ORG, Martin Cracauer , Markus Holmberg , "Ronald F. Guilmette" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jan-00 Dan Nelson wrote: > Aah, but we wouldn't have found the bug if FreeBSD hadn't caught it > I prefer to trap by default. The very few programs that require > IEEE > conformance can call fpsetmask() themselves. Isn't it really a POLA issue? It affects people that port code because if the way FreeBSD works is non standard you have to patch... ie for just about any Linux app which does FPU stuff :) --- 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 Wed Jan 5 17:12:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9E4BA154E9 for ; Wed, 5 Jan 2000 17:12:33 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id LAA23906; Thu, 6 Jan 2000 11:37:39 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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 In-Reply-To: <200001052345.PAA26271@biggusdiskus.flyingfox.com> Date: Thu, 06 Jan 2000 11:37:39 +1030 (CST) From: "Daniel O'Connor" To: Jim Shankland Subject: Re: Reading kbd scancodes from userland Cc: lyndon@orthanc.ab.ca, freebsd-hackers@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Jan-00 Jim Shankland wrote: > (void) tcsetattr(fd, 0, &old_t); > if (ioctl(fd, KDSKBMODE, oldmode) < 0) { > (void) fprintf(stderr, > "Danger, Will Robinson! Can't restore keyboard: > %s\n", You know I *really* wish there was a way to make sure that when your app closed the keyboard was unborked again.. Its really annoying having to find another machine when your app coredumps so you can restore the keyboard to sanity :) --- 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 Wed Jan 5 19:58:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 3EBBB153A5 for ; Wed, 5 Jan 2000 19:58:09 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id VAA87098; Wed, 5 Jan 2000 21:57:52 -0600 (CST) (envelope-from dan) Date: Wed, 5 Jan 2000 21:57:52 -0600 From: Dan Nelson To: "Daniel O'Connor" Cc: Jim Shankland , lyndon@orthanc.ab.ca, freebsd-hackers@FreeBSD.ORG Subject: Re: Reading kbd scancodes from userland Message-ID: <20000105215752.A86025@dan.emsphone.com> References: <200001052345.PAA26271@biggusdiskus.flyingfox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from "Daniel O'Connor" on Thu Jan 6 11:37:39 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 06), Daniel O'Connor said: > > On 05-Jan-00 Jim Shankland wrote: > > (void) tcsetattr(fd, 0, &old_t); > > if (ioctl(fd, KDSKBMODE, oldmode) < 0) { > > (void) fprintf(stderr, > > "Danger, Will Robinson! Can't restore keyboard: > > %s\n", > > You know I *really* wish there was a way to make sure that when your > app closed the keyboard was unborked again.. Three ideas: 1) #! /bin/sh ./myprogram kbd_mode -a or a similar C routine that runs as the parent process, and resets the keyboard mode when the child exits 2) Is there a termios flag that could be used to indicate "raw keyboard mode"? That way you can have your shell reset the mode via tcgetattr/tcsetattr (in zsh "ttyctl -f" does this). 3) Another alternative is to write a "keyboardd" that resets the mode; your program would (say) flock /dev/console and go into raw mode. keyboardd would check every 10 seconds or so to see if the keyboard is in raw mode. If it is, it does a flock on /dev/console (whick will block until your program exits), and resets the mode back. -- 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 Wed Jan 5 21:40:27 2000 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 9573114DF8 for ; Wed, 5 Jan 2000 21:40:10 -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 AAA13431 for ; Thu, 6 Jan 2000 00:40:06 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA03637; Thu, 6 Jan 2000 00:39:36 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id AAA48104 for freebsd-hackers@freebsd.org; Thu, 6 Jan 2000 00:39:35 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <200001060539.AAA48104@bb01f39.unx.sas.com> Subject: cdrecord & Pioneer DVR-S201? To: freebsd-hackers@freebsd.org Date: Thu, 6 Jan 2000 00:39:35 -0500 (EST) 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, The subject pretty much asks the question. I'm looking for anyone who has used or tried to use the new Pioneer DVR-S201 2nd Generation 4.7GB DVD-Writer on FreeBSD/cdrecord. I've looked at the current cdrecord support page and I don't see this drive listed. I've also search deja for any references to this drive and cdrecord and could not find any. From perusing the cdrecord pages, it looks like it should be possible to simply create a very large iso9660 filesystem and then burn it... Basically, a really big cdrom. I'm currently only interested in disk-at-once writing. Thanks, John ps: Pioneers page: http://www.pioneeraus.com.au/multimedia/products/dvd-r/dvr-s201/dvr-s201_prod.htm A better site with more tech info: http://www.proh.com/DVD_recorders_Pioneer_DVR-S201_4.7GB_DVD-R-RW_drive_sales.shtml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Wed Jan 5 22: 1:41 2000 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 026B815558 for ; Wed, 5 Jan 2000 22:01:38 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA32066; Wed, 5 Jan 2000 23:01:34 -0700 (MST) (envelope-from ken) Date: Wed, 5 Jan 2000 23:01:34 -0700 From: "Kenneth D. Merry" To: "John W. DeBoskey" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: cdrecord & Pioneer DVR-S201? Message-ID: <20000105230134.A31887@panzer.kdm.org> References: <200001060539.AAA48104@bb01f39.unx.sas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001060539.AAA48104@bb01f39.unx.sas.com>; from jwd@unx.sas.com on Thu, Jan 06, 2000 at 12:39:35AM -0500 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 00:39:35 -0500, John W. DeBoskey wrote: > Hi, > > The subject pretty much asks the question. I'm looking for > anyone who has used or tried to use the new Pioneer DVR-S201 > 2nd Generation 4.7GB DVD-Writer on FreeBSD/cdrecord. > > I've looked at the current cdrecord support page and I don't > see this drive listed. I've also search deja for any references > to this drive and cdrecord and could not find any. > > From perusing the cdrecord pages, it looks like it should be > possible to simply create a very large iso9660 filesystem and then > burn it... Basically, a really big cdrom. I'm currently only > interested in disk-at-once writing. The main question is probably what interface does the drive use? Does it use the same sort of write/fixate process that CD-R's use? DVD-RAM drives use a standard read/write interface, but they're more like a standard optical drive in interface. My guess is that it acts kinda like a CD-R, but it's hard to say without specs of some sort. I'd suggest that you contact Joerg Schilling and see what he has to say about it. He may ask for at least a loner drive and specs from Pioneer in order to support it. If it does use the standard read/write interface, and not a CD-R type interface, let me know, and I can probably get you up and running. BTW, the suggested retail price is amazingly high -- $5400. I suppose it could be to discourage people from copying movies, or it could just be because it's the only DVD-R drive on the market. (is 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 Jan 5 22:13: 0 2000 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 3472614F85 for ; Wed, 5 Jan 2000 22:12:57 -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 BAA14848; Thu, 6 Jan 2000 01:12:24 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA10028; Thu, 6 Jan 2000 01:11:54 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.3/8.9.1) id BAA49055; Thu, 6 Jan 2000 01:11:53 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <200001060611.BAA49055@bb01f39.unx.sas.com> Subject: Re: AIO was Re: Kernel threads In-Reply-To: From Arjan de Vet at "Jan 3, 2000 09:27:58 pm" To: Arjan de Vet Date: Thu, 6 Jan 2000 01:11:53 -0500 (EST) Cc: freebsd-hackers@freebsd.org, David Quattlebaum 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 With respect to AIO... we run a data server which multiplexes on the select() function, and uses AIO to do all it's I/O. This has been a very stable system. system : 4.0-19990827-SNAP start time : 1999/12/24 11:14:44 up time (days hh:mm:ss) : 12 13:32:53 Current/Max/Total connections: 0 / 2 / 244 Total requests: 6228 Total aio bytes written: 573499989 (546.9M) Current/Max stat daemons: 0 / 1 Current/Max Queued for stat: 0 / 0 Current/Max cp daemons: 0 / 2 Current/Max Queued for cp: 0 / 0 Current/Max aio_write daemons: 0 / 2 Current/Max Queued for write: 0 / 0 Current/Max/ telnets: 1 / 1 The above is a sample of the stats kept by the daemon. The numbers are very low due to the holidays. Basically, this thing hands raw data to applications running on NT, where the data is kept on Network Appliance fileservers attached to FreeBSD boxes. Direct CIFS attachment to the data from the NT system does not come close to the through-put we attain using this process. I would very much like to see these patches applied also. At a minimum, it means that the following type of code loop can be removed since we would know immediately which aio operation completed. The marked loop below becomes relatively hot as the max number of outstanding aio processes is increased and the number of simultanious hits on the server grows. /*----------------------------------------------------------+ | ST_AIO | | | | A task in the ST_AIO state means that one of our | | aio_writes has finished. we will loop thru all | | outstanding aio_writes to see which one completed. | | | *----------------------------------------------------------*/ case ST_AIO: ... code deleled ... /*-----------------------------------------------------+ | we know we have a completed process. let's find out | | which one it is. | *-----------------------------------------------------*/ ---> for (j=0; j if (aio[j].task && aio_error(&aio[j].iocb) != EINPROGRESS) ---> break; } ... code deleted ... /*-----------------------------------------------------+ | Get the actual return code, check length, decrement | | active count, send message | +-----------------------------------------------------*/ t = aio[j].task; rc = aio_return(&aio[j].iocb); Since we are getting ready to bring this process forward and integrate the new signal handling code, now would be a great time for these patches to be applied and have some heavy testing done on them. Thanks! John > In article you > write: > > >> The best fix I've thought of thus far (other than async I/O, which I > >> understand isn't ready for prime time) would be to have a number of kernel > > > >Speaking of AIO, which I would really like to use if possible, how > >actively maintained is it? The copyright on vfs_aio.c is 1997, suggesting > >to me that John Dyson has moved onto other things. > > Yep, that's right. > > Quite recently Christopher Sedore has done some work on vfs_aio.c, to > make it work better with sockets and he also added a very useful > aio_waitcomplete system call which returns the first aiocb (AIO control > block) from the 'completed' queue. I would be nice if these patches > could be added to FreeBSD-current. > > About AIO not ready for prime time: I did some experiments recently by > throwing up to 256 aio requests on one fd (a raw disk device) into the > system and it worked without any problems. The only time I got a panic > was when (I think) I had a negative aiocb->offset (I still need to > reproduce this). See http://www.iae.nl/users/devet/freebsd/aio/ for my > aiotest.c program. > > I'm thinking about using AIO for a faster Squid file system by using raw > disk devices instead of UFS which has too much overhead for Squid. > > Arjan > > - -- > Arjan de Vet, Eindhoven, The Netherlands > URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl > > > > 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 Jan 5 22:26:54 2000 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 A58C8153A5 for ; Wed, 5 Jan 2000 22:26:53 -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 WAA50599; Wed, 5 Jan 2000 22:26:46 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "John W. DeBoskey" Cc: Arjan de Vet , freebsd-hackers@FreeBSD.ORG, David Quattlebaum Subject: Re: AIO was Re: Kernel threads In-reply-to: Your message of "Thu, 06 Jan 2000 01:11:53 EST." <200001060611.BAA49055@bb01f39.unx.sas.com> Date: Wed, 05 Jan 2000 22:26:46 -0800 Message-ID: <50594.947140006@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is very interesting data and I was just wondering about the actual state of functionality in our AIO code just the other day, oddly enough. Does anyone have a PR# for the mentioned patches? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 0:36:48 2000 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 8961B14C30 for ; Thu, 6 Jan 2000 00:36:44 -0800 (PST) (envelope-from cracauer@knight.cons.org) Received: (from cracauer@localhost) by knight.cons.org (8.9.3/8.9.3) id JAA14889; Thu, 6 Jan 2000 09:36:29 +0100 (CET) Date: Thu, 6 Jan 2000 09:36:29 +0100 From: Martin Cracauer To: Markus Holmberg Cc: Martin Cracauer , freebsd-hackers@freebsd.org Subject: Re: Should -mieee-fp equal fpsetmask(0) to avoid SIGFPE on FreeBSD? Message-ID: <20000106093628.A14728@cons.org> References: <20000104121459.A8959@cons.org> <87632.947017515@monkeys.com> <20000105055138.A74746@fysgr387.sn.umu.se> <20000105092356.A8100@cons.org> <20000105205947.A77037@fysgr387.sn.umu.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000105205947.A77037@fysgr387.sn.umu.se>; from saska@acc.umu.se on Wed, Jan 05, 2000 at 08:59:47PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, Folks, first of all I apologize for getting carried away and proposing replacement functions that incompletely implemented the requested behaviour. The equivalent macro with range check is 40% slower (why isn't the MS VC++ specific test case #unifdef'ed for other platforms?). Then, I am not against disabling those exceptions by default that have meaningful results when masked. That are all exceptions that would (if not trapped) result in a floating point value with meaningful semantics: overflow, underflow and divide-by zero. But I am against disabling "invalid operation" by default, because the most often cause of this exception is the case discussed here: A conversion of a too big FP value to an int where it doesn't fit. The result of this operation is at the very least (depending on the C standard in use) an unspecified integer and must not be used. Only in rare cases the programmer knew what he/she did and ignored the result of the operation just carried out. I agree that this Mozilla issue is such a case, the value is supposed to be ignored. But the macro's interface doesn't enforce it. If the macro is that often used in mozilla, I bet I can point out cases where it isn't ignored. Regarding ANSI C: - ANSI C 89 makes it clear that the behaviour is unspecified and that anything may happen and that this macro may not work. An optimizing C89 conforming compiler may chance this code in a way that breaks the macro. - Waldemar is correct that C99 changes the "undefined behaviour" to "the result is an unspecified value". In that case the Mozilla macro is quaranteed to work. However, neither gcc nor FreeBSD claim to be C99 conformant. When thinking about default FP exceptions, it all comes down to the ratio of cases where one exceptions raised a false alarm or where a serious error was caught. In the case of "invalid operation" that ratio is overwhelming in favor of "real" alarms, and in most cases of false alarm (like this Mozilla macro) it points out constructions that need to used with extreme caution. Again: Here we have a programmer that writes a really clever macro that messes with FPU conversions. He knows C89 and C99 enough to point out the relative parts. Code that is so specifically written for one FPU behaviour in mind should set the FPU exception mask. If only to document that it knows what it is doing. 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 Thu Jan 6 0:53:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news.IAEhv.nl (news.IAE.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id C6AE2155CF for ; Thu, 6 Jan 2000 00:53:08 -0800 (PST) (envelope-from Arjan.deVet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id JAA15888; Thu, 6 Jan 2000 09:53:07 +0100 (MET) Received: by adv.iae.nl (Postfix, from userid 100) id 59B8822CA; Thu, 6 Jan 2000 09:52:48 +0100 (CET) Date: Thu, 6 Jan 2000 09:52:48 +0100 To: "Jordan K. Hubbard" Cc: "John W. DeBoskey" , freebsd-hackers@FreeBSD.ORG, David Quattlebaum Subject: Re: AIO was Re: Kernel threads Message-ID: <20000106095248.A10302@adv.iae.nl> References: <200001060611.BAA49055@bb01f39.unx.sas.com> <50594.947140006@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <50594.947140006@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Wed, Jan 05, 2000 at 10:26:46PM -0800 From: Arjan.deVet@adv.iae.nl (Arjan de Vet) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan K. Hubbard wrote: >This is very interesting data and I was just wondering about the >actual state of functionality in our AIO code just the other day, >oddly enough. Does anyone have a PR# for the mentioned patches? kern/12053 A Dec 16 version of the patch can be found at: http://tfeed.maxwell.syr.edu/aio-diff They won't apply cleanly because some new syscalls have been added. Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 3: 7:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from fLuFFy.iNt.tElE.dK (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (Postfix) with ESMTP id 3317C155DA for ; Thu, 6 Jan 2000 03:07:20 -0800 (PST) (envelope-from freebeer@vsZbr.cZ) Received: from localhost (freebeer@localhost) by fLuFFy.iNt.tElE.dK (8.9.3/8.9.3) with SMTP id MAA24359 for ; Thu, 6 Jan 2000 12:07:13 +0100 (CET) (envelope-from freebeer@vsZbr.cZ) X-Authentication-Warning: fLuFFy.iNt.tElE.dK: freebeer owned process doing -bs Date: Thu, 6 Jan 2000 12:07:13 +0100 (CET) From: Kun Limfjordsporter X-Sender: freebeer@fLuFFy.iNt.tElE.dK Reply-To: crashdump@netscum.dk To: freebsd-hackers@freebsd.org Subject: newfs panics 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 Moin moin... I'm not sure where is the best list to send this, since I've seen it under both -current and -stable, so you'll have to do. Has anyone seen panics like panic: vinvalbuf: dirty bufs mp_lock = 000000000001; cpuid = 0; lapic.id = 0100000000 I get this regularly when newfs'ing a disk that I've previously newfs'ed, apparently when I've given options like -b 32768 or 65536 (which works), followed by the default value for -b. I've been trying different options to see the effect on the filesystem created. I'm also trying to get -i as large as possible since the filesystem will have no more than one file, or -i 1776something. (I get an out-of-range error but no panic if -i is too large), although my last panic was triggered by the default values for everything. I'm seeing it now with -stable cvsup'ed a few hours ago, but I saw it a few days ago with a -current from last year, so it seems to have been around for a while. If you haven't seen this and need more info, I'll be happy to pass it along. (use the reply-to header if needed since i'm not suscirbed to this list) Now I think I'll see if I can have any sort of success with the already-newfscked-up disk, and try the latest -current just for grins. thanks, barry `braneless' bouwsma, teledanmarQinterneT -- ARRGH!!@! If you are the victim of a B0RKENED MAIL SYSTEM, yo REPENT!!! PURGE THE EVIL OF REDMOND FROM YOUR HARD DRIVES!!!!1! mange tak, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 4:39:24 2000 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 05DAC14CE2 for ; Thu, 6 Jan 2000 04:39:04 -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 OAA04860; Thu, 6 Jan 2000 14:37:23 +0200 (EET) (envelope-from ru) Date: Thu, 6 Jan 2000 14:37:22 +0200 From: Ruslan Ermilov To: Jim Flowers Cc: hackers@FreeBSD.ORG Subject: Re: Natd with Pmtu Discovery Message-ID: <20000106143722.A2080@relay.ucb.crimea.ua> Mail-Followup-To: Jim Flowers , hackers@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Jim Flowers on Sat, Dec 18, 1999 at 05:19:28PM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999 at 05:19:28PM -0500, Jim Flowers wrote: > 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. > Thanks for the info, I'm working on a patch at the moment. Please track PR 15494 for this issue. http://www.freebsd.org/cgi/query-pr.cgi?15494 -- 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 Thu Jan 6 4:46:41 2000 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 C3A8315588 for ; Thu, 6 Jan 2000 04:46:39 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 18282 invoked from network); 6 Jan 2000 12:46:38 -0000 Received: from citadel.in.taronga.com (10.0.0.43) by mushi.in.taronga.com with SMTP; 6 Jan 2000 12:46:38 -0000 Received: by citadel.in.taronga.com (Postfix, from userid 100) id 4E64C32306; Thu, 6 Jan 2000 06:45:48 -0600 (CST) To: d_f0rce@gmx.de Subject: Re: Limited amount of variables in a multithreaded programm? X-Newsgroups: taronga.freebsd.hackers In-Reply-To: <002001bf5697$31869fe0$0201a8c0@blade> References: <20000103173027.A61058@cons.org> <20000103184233.B17710@cons.org> Organization: Cc: hackers@freebsd.org Message-Id: <20000106124548.4E64C32306@citadel.in.taronga.com> Date: Thu, 6 Jan 2000 06:45:48 -0600 (CST) From: peter@taronga.com (Peter da Silva) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >"This really is C-101 type stuff." :-) ) if you could tell me a book about >programming FreeBSD. I have Stevens "Advanced programming..." and >Haviland's "Unix System programming" but there is not much about threads >in these books. Moreover there is nothing about variable stack sizes in >threads. There's a good reason for this... multithreaded programming under UNIX is very complicated, and it should be avoided in most cases. You certainly shouldn't try writing a multithreaded program in *any* OS if you don't have a good, solid understanding of stacks and concurrency first. My preference at this point would be for you to read a good book on concurrent programming that digs into things at the instruction level. Douglas Comer's "Xinu" book is pretty good. Here's a page you should probably start your research with... http://www.faqs.org/faqs/os-research/part1/section-21.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 6: 2:53 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from webweaving.org (dialfwn06.fwn.rug.nl [129.125.32.156]) by hub.freebsd.org (Postfix) with ESMTP id 45F5015749 for ; Thu, 6 Jan 2000 06:02:45 -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 OAA03054; Thu, 6 Jan 2000 14:39:51 +0100 (CET) (envelope-from n_hibma@webweaving.org) Date: Thu, 6 Jan 2000 14:39:51 +0100 (CET) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Peter Wemm Cc: Nate Williams , freebsd-hackers@FreeBSD.ORG Subject: Re: USB vs. parallel port In-Reply-To: <20000105153241.B0DC21CCE@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 Except that I doubt whether UHCI will survive USB2.0. Nick On Wed, 5 Jan 2000, Peter Wemm wrote: > Nick Hibma wrote: > > > By the way, at the moment it is better to have a UHCI controller on > > your motherboard. Allthough the OHCI controller is much smarter and more > > efficient, support for it is not as stable as the support for UHCI > > controllers. > > Sounds like UHCI => IDE, OHCI => SCSI ? (only 1/2 :-). > > Cheers, > -Peter > > -- 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 Thu Jan 6 6: 6:10 2000 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 D852A15653 for ; Thu, 6 Jan 2000 06:06:06 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 21584 invoked from network); 6 Jan 2000 14:06:05 -0000 Received: from citadel.in.taronga.com (10.0.0.43) by mushi.in.taronga.com with SMTP; 6 Jan 2000 14:06:05 -0000 Received: by citadel.in.taronga.com (Postfix, from userid 100) id 190E032306; Thu, 6 Jan 2000 08:05:45 -0600 (CST) To: hackers@freebsd.org Subject: Re: alt. C compiler X-Newsgroups: taronga.freebsd.hackers In-Reply-To: <200001051816.LAA20023@mt.sri.com> References: <20000105100716.A63545@cons.org><98339.947095734@monkeys.com>,<98339.947095734@monkeys.com> Organization: Cc: Message-Id: <20000106140545.190E032306@citadel.in.taronga.com> Date: Thu, 6 Jan 2000 08:05:45 -0600 (CST) From: peter@taronga.com (Peter da Silva) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Many system include files are *NOT* for public consumption. Then it would be nice if people didn't have to grovel around system include files to find things. > Also, >include files should never include other include files, as this messes >up dependencies. That just means you need a smarter dependancy generator, one that digs into include files for more #includes. On the Amiga, all include files were supposed to include all include files they needed, *and* they were supposed to guard themselves and any include files they included (the latter being an optimization to avoid extra includes on the slow disks and processors of 1985): #ifndef GRAPHICS_RASTPORT_H #ifndef GRAPHICS_BITMAP_H #include #endif ... #endif This worked very well in practice, and I think it's a shame that UNIX systems don't do this. I'm forever patching Linux software to add extra "#include " and the like. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 6:10:35 2000 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 5EBF71569E for ; Thu, 6 Jan 2000 06:10:31 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 21886 invoked from network); 6 Jan 2000 14:10:30 -0000 Received: from citadel.in.taronga.com (10.0.0.43) by mushi.in.taronga.com with SMTP; 6 Jan 2000 14:10:30 -0000 Received: by citadel.in.taronga.com (Postfix, from userid 100) id E498932307; Thu, 6 Jan 2000 08:09:39 -0600 (CST) To: hackers@freebsd.org Subject: Re: alt. C compiler X-Newsgroups: taronga.freebsd.hackers In-Reply-To: <200001052027.PAA32580@lakes.dignus.com> References: <1641.947103183@monkeys.com> Organization: Cc: Message-Id: <20000106140939.E498932307@citadel.in.taronga.com> Date: Thu, 6 Jan 2000 08:09:39 -0600 (CST) From: peter@taronga.com (Peter da Silva) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > We're talking about making it easier to use the FreeBSD library code > in other programs (i.e. `port' it somewhere) - presumably with a > strict ANSI C compiler other than gcc. Or to use an ANSI C compiler other than GCC on a FreeBSD system. > While that is certainly a laudable goal - I question the term "pragmatic". > Just how often is this going to happen? Never, if the effort isn't made. > Is it worth the effort? I think so. GCC is a decent compiler but it would be better if we were able to reasonably easily use other tools. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 6:17:39 2000 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 D6AD015633 for ; Thu, 6 Jan 2000 06:17:36 -0800 (PST) (envelope-from peter@taronga.com) Received: (qmail 22200 invoked from network); 6 Jan 2000 14:17:35 -0000 Received: from citadel.in.taronga.com (10.0.0.43) by mushi.in.taronga.com with SMTP; 6 Jan 2000 14:17:35 -0000 Received: by citadel.in.taronga.com (Postfix, from userid 100) id 32AB432306; Thu, 6 Jan 2000 08:16:45 -0600 (CST) To: hackers@freebsd.org Subject: Re: Reading kbd scancodes from userland X-Newsgroups: taronga.freebsd.hackers In-Reply-To: References: <200001052345.PAA26271@biggusdiskus.flyingfox.com> Organization: Cc: Message-Id: <20000106141645.32AB432306@citadel.in.taronga.com> Date: Thu, 6 Jan 2000 08:16:45 -0600 (CST) From: peter@taronga.com (Peter da Silva) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Its really annoying having to find another machine when your app >coredumps so you can restore the keyboard to sanity :) If your keyboard is too borked for "^Jstty sane^J", let me know so I can avoid the app that does this. I remember running into a shell, once upon a time, that saved and restored all terminal modes before and after every program unless that program was a defined "this program changes terminal modes" utility like "tset" or "stty". (actually I think it just saved them at startup or after a utility, and restored them when you got to a prompt, but the result is the same) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 6:32:21 2000 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 AA20115648; Thu, 6 Jan 2000 06:32:16 -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 JAA00713; Thu, 6 Jan 2000 09:31:28 -0500 (EST) Date: Thu, 6 Jan 2000 09:31:27 -0500 (EST) From: Jim Flowers To: Ruslan Ermilov Cc: hackers@FreeBSD.ORG Subject: Re: Natd with Pmtu Discovery In-Reply-To: <20000106143722.A2080@relay.ucb.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 OK. I followed this a little further. The problem is that the natd read of the interface mtu precedes the skip routine that modifies it. Unfortunately, when the skip routine modifies the interface mtu it does not send a message to the socket as it does when the address is changed so the -dynamic flag doesn't help. Currently, I moved the the initiation of natd to rc.local to follow the skip change to the interface mtu but this is less than ideal. A better approach would be to notify the natd module of any interface mtu change via the socket, similar to when the address is changed with the -dynamic flag set. This would also pick of manual changes. Jim Flowers #4 ISP on C|NET, #1 in Ohio On Thu, 6 Jan 2000, Ruslan Ermilov wrote: > On Sat, Dec 18, 1999 at 05:19:28PM -0500, Jim Flowers wrote: > > 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. > > > Thanks for the info, I'm working on a patch at the moment. > Please track PR 15494 for this issue. > > http://www.freebsd.org/cgi/query-pr.cgi?15494 > > -- > 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 Thu Jan 6 7:43:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dns.sonntag.org (dns.sonntag.org [216.140.186.114]) by hub.freebsd.org (Postfix) with ESMTP id 3273514FB0 for ; Thu, 6 Jan 2000 07:43:46 -0800 (PST) (envelope-from aaron@sonntag.org) Received: from win2knoc (st84043.nobell.com [216.140.184.43]) by dns.sonntag.org (8.9.3/8.9.3) with SMTP id JAA83101 for ; Thu, 6 Jan 2000 09:44:21 -0600 (CST) (envelope-from aaron@sonntag.org) From: "Aaron Sonntag" To: Subject: VIPW user accounts Date: Thu, 6 Jan 2000 09:41:21 -0600 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I usually edit VIPW by hand. I have set up mail only accounts using /usr/bin/passwd shell. Along the same lines how do I go about setting up the following accounts: ftp only ftp and mail only Thanks Aaron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 7:45:39 2000 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 100A0155F2 for ; Thu, 6 Jan 2000 07:45:36 -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 126F6J-0001Cy-00; Thu, 06 Jan 2000 17:45:23 +0200 From: Sheldon Hearn To: "Aaron Sonntag" Cc: hackers@FreeBSD.ORG Subject: Re: VIPW user accounts In-reply-to: Your message of "Thu, 06 Jan 2000 09:41:21 CST." Date: Thu, 06 Jan 2000 17:45:23 +0200 Message-ID: <4647.947173523@axl.noc.iafrica.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 06 Jan 2000 09:41:21 CST, "Aaron Sonntag" wrote: > I usually edit VIPW by hand. I have set up mail only accounts using > /usr/bin/passwd shell. > Along the same lines how do I go about setting up the following accounts: > > ftp only > ftp and mail only I've written some fairly lengthy answers to this question before. Search the freebsd-questions mailing list archives. 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 Jan 6 8:30:34 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.iserlohn.netsurf.de (mail.iserlohn.netsurf.de [194.195.194.253]) by hub.freebsd.org (Postfix) with ESMTP id 03E50156F0 for ; Thu, 6 Jan 2000 08:30:25 -0800 (PST) (envelope-from sascha@schumann.cx) Received: from schumann.cx (hennen32s.iserlohn.netsurf.de [194.195.194.226]) by mail.iserlohn.netsurf.de (8.9.1/8.9.1) with SMTP id RAA06878 for ; Thu, 6 Jan 2000 17:30:46 +0100 Received: (qmail 520 invoked from network); 6 Jan 2000 16:23:35 -0000 Received: from flaubert.foo.bar (192.168.0.99) by guerilla.foo.bar with SMTP; 6 Jan 2000 16:23:35 -0000 Received: (qmail 31742 invoked by uid 500); 6 Jan 2000 16:23:35 -0000 Date: Thu, 6 Jan 2000 17:23:35 +0100 From: Sascha Schumann To: freebsd-hackers@freebsd.org Subject: major device number for pcfclock Message-ID: <20000106172335.A31729@schumann.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Notice: Copyright (c) 2000 Sascha Schumann. All rights reserved. X-Operating-System: Linux 2.2.13 #10 Mon Dec 27 20:35:15 CET 1999 alpha Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'd like to see the new pcfclock driver be included into FreeBSD, so I need an official major device number. Shall I simply take the highest used number (139), increase it, and send you a tarball, including the driver and the patches against conf/files, conf/majors, MAKEDEV? Current driver version: http://apache.org/~sascha/pcfclock.c -- Regards, Sascha Schumann Consultant To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 11:42:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mailer.syr.edu (mailer.syr.edu [128.230.18.29]) by hub.freebsd.org (Postfix) with ESMTP id 5800814FE1 for ; Thu, 6 Jan 2000 11:42:52 -0800 (PST) (envelope-from cmsedore@mailbox.syr.edu) Received: from rodan.syr.edu by mailer.syr.edu (LSMTP for Windows NT v1.1b) with SMTP id <0.FFF78FE7@mailer.syr.edu>; Thu, 6 Jan 2000 14:42:45 -0500 Received: from localhost (cmsedore@localhost) by rodan.syr.edu (8.8.7/8.8.7) with ESMTP id OAA21354; Thu, 6 Jan 2000 14:42:45 -0500 (EST) X-Authentication-Warning: rodan.syr.edu: cmsedore owned process doing -bs Date: Thu, 6 Jan 2000 14:42:44 -0500 (EST) From: Christopher Sedore X-Sender: cmsedore@rodan.syr.edu To: Arjan de Vet Cc: "Jordan K. Hubbard" , "John W. DeBoskey" , freebsd-hackers@FreeBSD.ORG, David Quattlebaum Subject: Re: AIO was Re: Kernel threads In-Reply-To: <20000106095248.A10302@adv.iae.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 6 Jan 2000, Arjan de Vet wrote: > Jordan K. Hubbard wrote: > > >This is very interesting data and I was just wondering about the > >actual state of functionality in our AIO code just the other day, > >oddly enough. Does anyone have a PR# for the mentioned patches? > > kern/12053 > > A Dec 16 version of the patch can be found at: > > http://tfeed.maxwell.syr.edu/aio-diff > > They won't apply cleanly because some new syscalls have been added. There may be another PR related too (although a quick search a few seconds ago didn't show it)--this patch set also fixes a problem where signals were not posted for aio completion under certain circumstances (the code just wasn't there before). Just found the PR--kern/13075 -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 12:25:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (Postfix) with ESMTP id A1AA3156D0 for ; Thu, 6 Jan 2000 12:25:24 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.3/8.9.3) with ESMTP id VAA43951; Thu, 6 Jan 2000 21:24:06 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.9.3/8.9.3) id VAA30411; Thu, 6 Jan 2000 21:24:04 +0100 (CET) Date: Thu, 6 Jan 2000 21:24:04 +0100 From: Cejka Rudolf To: hackers@FreeBSD.ORG Cc: saper@system.pl, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons: SC_MOUSE_CHAR value rationale Message-ID: <20000106212404.A30244@dcse.fee.vutbr.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from saper@system.pl on Wed, Jan 05, 2000 at 09:46:46PM +0100 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcin Cieslak wrote (2000/01/05): > Is there any _particular_ reason why this is #define'd to (0xd0) > in /sys/dev/syscons/syscons.c? From syscons.c,v - 1998/02/11 (author: yokota): - another new option: SC_MOUSE_CHAR Define the first character code of four consecutive codes to be used for the mouse cursor. Default codes are 0xd0 through 0xd3. Beware that if you decide to use any codes outside the range of 0xc0-0xdf, the mouse cursor may not look good, because of the way VGA displays characters in 9-dot-wide character cells. Requested by several people. > Nearly everyone who wants to set up their national locale > needs to recompile the kernel, since some important characters > are hidden under mouse cursor. I agree with you - it is very strange for Czech users too (and maybe for almost all ISO-8859-* users) - default mouse settings override some important characters. Maybe we should ask Kazu if it is possible: 1) Move SC_MOUSE_CHAR into sysctl tree as read-write value. 2) Make SC_ALT_MOUSE_IMAGE as default setting. But Kazu have cleared off in December and I don't know where he is... > Will changing it to 0x08 break anything? Look above. -- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Brno University of Technology, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 13:46:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id A974514E10 for ; Thu, 6 Jan 2000 13:46:04 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id QAA99094; Thu, 6 Jan 2000 16:45:50 -0500 (EST) Date: Thu, 6 Jan 2000 16:45:50 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Cejka Rudolf Cc: hackers@FreeBSD.ORG, saper@system.pl, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons: SC_MOUSE_CHAR value rationale In-Reply-To: <20000106212404.A30244@dcse.fee.vutbr.cz> 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, 6 Jan 2000, Cejka Rudolf wrote: > > Marcin Cieslak wrote (2000/01/05): > > Is there any _particular_ reason why this is #define'd to (0xd0) > > in /sys/dev/syscons/syscons.c? > > >From syscons.c,v - 1998/02/11 (author: yokota): > > - another new option: SC_MOUSE_CHAR > Define the first character code of four consecutive codes to be used for > the mouse cursor. Default codes are 0xd0 through 0xd3. Beware that > if you decide to use any codes outside the range of 0xc0-0xdf, > the mouse cursor may not look good, because of the way VGA displays > characters in 9-dot-wide character cells. > Requested by several people. > In the 90-column video modes, you can use any character you want. They work by turning off the 0th bit copy used to simulate the 9th bit position on the VGA fonts. I believe Kazu has incorporated my patches for these modes into -current (I originally wrote them for 2.2.6 syscons). So in response to the original question: sure you could move the mouse chars to 0x08 - 0x0b if you wanted, but it'll look bad unless you are running in a 90-column text mode. In any event, If we don't here from Kazu in the near future, I'll send-pr a patch to make the first character used for the mouse cursor a sysctl knob. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 14:43:58 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from funnel.cisco.com (funnel.cisco.com [161.44.131.24]) by hub.freebsd.org (Postfix) with ESMTP id 6C4F514E32 for ; Thu, 6 Jan 2000 14:43:44 -0800 (PST) (envelope-from bmcgover@bmcgover-pc.cisco.com) Received: from bmcgover-pc.cisco.com (bmcgover-pc.cisco.com [171.69.104.147]) by funnel.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id RAA06056 for ; Thu, 6 Jan 2000 17:43:37 -0500 (EST) Received: from bmcgover-pc.cisco.com (localhost.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.9.3/8.9.3) with ESMTP id RAA00334 for ; Thu, 6 Jan 2000 17:43:37 -0500 (EST) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <200001062243.RAA00334@bmcgover-pc.cisco.com> To: hackers@freebsd.org Reply-To: bmcgover@cisco.com Subject: Question on mapping PCI interrupts... (or rather, not...) Date: Thu, 06 Jan 2000 17:43:37 -0500 From: Brian McGovern Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running in to a PCI interface question. I have a board that I can select whether it will run in Interrupt or "Polled mode" (ie - no interrupt assigned). It appears that when I have it in interrupt mode, the IRQ (cfg->intline) is set to a relatively valid (0-15) setting. When it is in polled mode, it reads as 255 (I'm assuming all-bits-on). However, pci_map_int is returning the same value reguardless of whether the interrupt is valid (0-15) or not (255). In the 2.x tree, it would return an error if the register was set at 255, and I used this in the driver to determine whether to be in polled mode or interrupt driven. Given the new behavior, should I: a.) Consider this a bug, and send in a pr (after all, it didn't _really_ map a valid interrupt)... b.) Leave it as is, but check the real interrupt register value, and if its not valid (0-15), assume its in polled mode. This scares me the most, for someday there may be more (up to 255) real interrupts... c.) Be told about a better way to check for this condition... -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 15:24:16 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id BF4181589D; Thu, 6 Jan 2000 15:24:08 -0800 (PST) (envelope-from ji@research.att.com) Received: from amontillado.research.att.com (amontillado.research.att.com [135.207.24.32]) by mail-green.research.att.com (Postfix) with ESMTP id C6E301E01E; Thu, 6 Jan 2000 18:23:18 -0500 (EST) Received: from bual.research.att.com (bual.research.att.com [135.207.24.19]) by amontillado.research.att.com (8.8.7/8.8.7) with ESMTP id SAA24463; Thu, 6 Jan 2000 18:23:47 -0500 (EST) Received: (from ji@localhost) by bual.research.att.com (8.7.5/8.7) id SAA29559; Thu, 6 Jan 2000 18:23:16 -0500 (EST) Date: Thu, 6 Jan 2000 18:23:16 -0500 (EST) Message-Id: <200001062323.SAA29559@bual.research.att.com> From: John Ioannidis To: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Help, I'm stuck! Weird network/routing question. Reply-To: ji@research.att.com Organization: AT&T Labs - Research Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here is the setup: Hosts alice and bob, running 3.4-STABLE, xl interfaces. on alice: # ifconfig xl1 10.1.1.1 up netmask 255.255.255.255 # netstat -r -n ... 10.1.1.1/32 link#2 UC 0 0 xl1 ... # ping 10.1.1.1 (yes, it pings fine) # netstat -r -n ... 10.1.1.1 0:10:4b:63:80:33 UHLW 0 4 lo0 => 10.1.1.1/32 link#2 UC 0 0 xl1 ... So far, everything is fine. Do the same on bob; # ifconfig xl1 10.1.1.2 up netmask 255.255.255.255 bob can also ping himself. Now, how to ping bob from alice? The obvious thing would be to say # route add -interface 10.1.1.2 10.1.1.1 which creates the following routing entry: 10.1.1.2 10.1.1.1 UHS 0 60 xl1 which of course doesn't work. So, what's the right way to do this? (No, I can't have a shorter subnet mask and put both interfaces on the same subnet! Needless to say, what I've described is the simplified problem). There has to be a way to tell the routing code "this address may not look like it's on any of your subnets, but the way to reach it is to ARP for it through interface xl1". There was definitely a way of doing this back in the SunOS 4 (and before) days. Help? /ji -- John Ioannidis * Secure Systems Research Department * AT&T Labs - Research OUR COMMON BOND: Respect for Individuals * Dedication to Helping Customers Highest Standards of Integrity * Innovation * Teamwork To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 17:27:51 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id BD0371577F; Thu, 6 Jan 2000 17:27:48 -0800 (PST) (envelope-from ji@research.att.com) Received: from amontillado.research.att.com (amontillado.research.att.com [135.207.24.32]) by mail-green.research.att.com (Postfix) with ESMTP id 607E71E004; Thu, 6 Jan 2000 20:22:04 -0500 (EST) Received: from bual.research.att.com (bual.research.att.com [135.207.24.19]) by amontillado.research.att.com (8.8.7/8.8.7) with ESMTP id UAA28006; Thu, 6 Jan 2000 20:22:32 -0500 (EST) From: John Ioannidis Received: (from ji@localhost) by bual.research.att.com (8.7.5/8.7) id UAA06973; Thu, 6 Jan 2000 20:22:00 -0500 (EST) Date: Thu, 6 Jan 2000 20:22:00 -0500 (EST) Message-Id: <200001070122.UAA06973@bual.research.att.com> To: dylanal@earthlink.net, ji@research.att.com Subject: Re: Help, I'm stuck! Weird network/routing question. Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > John, you say that you can't have a shorter subnet mask? As it is > you've specified all of the bits to be the subnetid, thus leaving The addresses were picked as examples, of course. /ji To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 18:21:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from thehousleys.net (frenchknot.ne.mediaone.net [24.218.96.75]) by hub.freebsd.org (Postfix) with ESMTP id 395C3156AC; Thu, 6 Jan 2000 18:20:50 -0800 (PST) (envelope-from jim@thehousleys.net) Received: from thehousleys.net (localhost [127.0.0.1]) by thehousleys.net (8.9.3/8.9.3) with ESMTP id UAA40098; Thu, 6 Jan 2000 20:20:27 -0500 (EST) (envelope-from jim@thehousleys.net) Message-ID: <38753F5B.9132044F@thehousleys.net> Date: Thu, 06 Jan 2000 20:20:27 -0500 From: "James E. Housley" X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: ji@research.att.com Cc: freebsd-hackers@FreeBSD.ORG, freebsd-net@FreeBSD.ORG Subject: Re: Help, I'm stuck! Weird network/routing question. References: <200001062323.SAA29559@bual.research.att.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Ioannidis wrote: > > Here is the setup: > > Hosts alice and bob, running 3.4-STABLE, xl interfaces. > > on alice: > # ifconfig xl1 10.1.1.1 up netmask 255.255.255.255 > # netstat -r -n That is your problem, I think. try netmask of 255.255.255.0 Jim -- James E. Housley "The box said 'Requires Windows 95, NT, or better,' so I installed FreeBSD" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Thu Jan 6 18:58:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from intranova.net (blacklisted.intranova.net [209.3.31.70]) by hub.freebsd.org (Postfix) with SMTP id 8EA501568D for ; Thu, 6 Jan 2000 18:58:23 -0800 (PST) (envelope-from oogali@intranova.net) Received: (qmail 13884 invoked from network); 6 Jan 2000 21:54:45 -0000 Received: from hydrant.intranova.net (user51236@209.201.95.10) by blacklisted.intranova.net with SMTP; 6 Jan 2000 21:54:45 -0000 Date: Thu, 6 Jan 2000 21:51:04 -0500 (EST) From: Omachonu Ogali To: John Ioannidis Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: Help, I'm stuck! Weird network/routing question. In-Reply-To: <200001062323.SAA29559@bual.research.att.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 netmask is probably causing problems. Try 255.0.0.0. Omachonu Ogali Intranova Networking Group On Thu, 6 Jan 2000, John Ioannidis wrote: > Here is the setup: > > Hosts alice and bob, running 3.4-STABLE, xl interfaces. > > on alice: > # ifconfig xl1 10.1.1.1 up netmask 255.255.255.255 > # netstat -r -n > ... > 10.1.1.1/32 link#2 UC 0 0 xl1 > ... > # ping 10.1.1.1 > (yes, it pings fine) > # netstat -r -n > ... > 10.1.1.1 0:10:4b:63:80:33 UHLW 0 4 lo0 => > 10.1.1.1/32 link#2 UC 0 0 xl1 > ... > > So far, everything is fine. > > Do the same on bob; > > # ifconfig xl1 10.1.1.2 up netmask 255.255.255.255 > > bob can also ping himself. > > Now, how to ping bob from alice? > The obvious thing would be to say > > # route add -interface 10.1.1.2 10.1.1.1 > > which creates the following routing entry: > > 10.1.1.2 10.1.1.1 UHS 0 60 xl1 > > which of course doesn't work. > > So, what's the right way to do this? (No, I can't have a shorter > subnet mask and put both interfaces on the same subnet! Needless to > say, what I've described is the simplified problem). There has to be > a way to tell the routing code "this address may not look like it's on > any of your subnets, but the way to reach it is to ARP for it through > interface xl1". There was definitely a way of doing this back in the > SunOS 4 (and before) days. > > Help? > > /ji > > -- > John Ioannidis * Secure Systems Research Department * AT&T Labs - Research > OUR COMMON BOND: Respect for Individuals * Dedication to Helping Customers > Highest Standards of Integrity * Innovation * Teamwork > > > > 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 Jan 6 21:45:42 2000 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 70FB1150B0 for ; Thu, 6 Jan 2000 21:45:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA79015; Thu, 6 Jan 2000 21:42:50 -0800 (PST) (envelope-from dillon) Date: Thu, 6 Jan 2000 21:42:50 -0800 (PST) From: Matthew Dillon Message-Id: <200001070542.VAA79015@apollo.backplane.com> To: Brett Glass Cc: hackers@freebsd.org Subject: Re: Possible optimization in VM? References: <4.2.2.20000106220706.00b67650@localhost> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (repeating, Brett sent his original posting to freebsd.com instead of freebsd.org!) :As I read this, a question immediately occurred to me. I can understand why :C1 exists; when the child modifies pages, one must create COW copies for it :that are distinct from the parent's. But why create C2? Why not allow the :parent to use B, as before, and create copies in C1 if the parent modifies :pages in B? By not multiplying entities beyond necessity, one could reduce :the overhead of a fork+exec -- in which C2 goes away quickly and C1 takes :up space until the parent process dies. : :Am I missing something here, or would this be an easy optimization to make? : :--Brett Glass : :P.S. -- I don't currently subscribe to "hackers," so please copy me on any :replies. I'll join the list if the discussion gets hot and heavy. Hmm. Well, you could copy the page to C1 in order to avoid creating a C2 layer, at least as long as you do not have other entities sharing B directly (e.g. C3, C4, ...). This sort of optimization would reduce the parent object's layering complexity but at the cost of increasing the child object's layering complexity. The problem that we hit is that we really mess up the 'All Shadowed' optimization if we start throwing pages into C1 that C1 didn't touch itself. The C1 layer may wind up contaiing a significant number of *additional* dirty pages, pages the child never actually touched itself and thus pages that an additional forked child of the child probably will not ever touch. This will prevent the 'All Shadowed' optimization from occuring, resulting in a potentially deep VM Object layering on one side of the graph. The key to the 'All Shadowed' optimization is that it depends on locality of reference in nearby layers. The locality of reference is messed up if we start copying pages to layers whos governing processes didn't actually touch. Another reason why we wouldn't want to do this is that it complicates the VM Object layer accounting. It would be hard to tell whether C1 could be collapsed into B without a C2. Or, if not hard, definitely more complex then the C1,C2 -> B case where the collapsability of layers is visually obvious. -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 Fri Jan 7 0: 0:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id B7D8715655 for ; Fri, 7 Jan 2000 00:00:31 -0800 (PST) (envelope-from brett@lariat.org) Received: from workhorse (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id BAA23881; Fri, 7 Jan 2000 01:00:25 -0700 (MST) Message-Id: <4.2.2.20000107004708.01c12740@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Fri, 07 Jan 2000 01:00:26 -0700 To: Matthew Dillon From: Brett Glass Subject: Re: Possible optimization in VM? Cc: hackers@freebsd.org In-Reply-To: <200001070542.VAA79015@apollo.backplane.com> References: <4.2.2.20000106220706.00b67650@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:42 PM 1/6/2000 , Matthew Dillon wrote: > Hmm. Well, you could copy the page to C1 in order to avoid creating > a C2 layer, at least as long as you do not have other entities sharing > B directly (e.g. C3, C4, ...). Yes, if you had C3, C4, etc. (multiple children), you'd need to make sure that each of them could get at what was originally in B. This means more copying -- either to each of the C's or someplace else. The thing is, most forks are followed by execs. The most common case is that they would never look at the old contents of B. So, it pays to make the copy operation as "lazy" as possible, since the odds are that not a single child will look at B. > This sort of optimization would reduce > the parent object's layering complexity but at the cost of increasing > the child object's layering complexity. > > The problem that we hit is that we really mess up the 'All Shadowed' > optimization if we start throwing pages into C1 that C1 didn't touch > itself. The C1 layer may wind up contaiing a significant number of > *additional* dirty pages, pages the child never actually touched > itself and thus pages that an additional forked child of the child > probably will not ever touch. They'd be substitutes for pages that would have been in C2, so we'd have as many dirty pages in either case, right? > This will prevent the 'All Shadowed' > optimization from occuring, resulting in a potentially deep VM Object > layering on one side of the graph. Hmmm. It seems to me that it would cause more pages to be "shadowed," thus actually accelerating the application of the optimization. Am I off base here? > The key to the 'All Shadowed' optimization is that it depends on locality > of reference in nearby layers. The locality of reference is messed up > if we start copying pages to layers whos governing processes didn't > actually touch. > > Another reason why we wouldn't want to do this is that it complicates > the VM Object layer accounting. It would be hard to tell whether C1 could > be collapsed into B without a C2. Or, if not hard, definitely more complex > then the C1,C2 -> B case where the collapsability of layers is visually > obvious. Well, in essence, we've really collapsed C2 into B (since it's serving to hold the parent's pages). So, haven't we already "won" by going straight to the state that an optimization might have achieved? --Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 0:51:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 411B414EF0 for ; Fri, 7 Jan 2000 00:51:09 -0800 (PST) (envelope-from Etienne.DeBruin@KryptoKom.DE) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.3) id JAA07715 for ; Fri, 7 Jan 2000 09:49:59 +0100 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa07712; Fri Jan 07 09:49:55 2000 Received: from nt-notes.kryptokom.de (nt-notes.kryptokom.de [192.168.6.247]) by cirdan.kryptokom.de (8.9.3/8.9.3) with SMTP id JAA19417 for ; Fri, 7 Jan 2000 09:49:55 +0100 Received: by nt-notes.kryptokom.de(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id C125685F.0030AA89 ; Fri, 7 Jan 2000 09:51:33 +0100 X-Lotus-FromDomain: UTIMACO From: "Etienne De Bruin" To: hackers@freebsd.org Message-ID: Date: Fri, 7 Jan 2000 09:51:32 +0100 Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When compiling 3.4-RELEASE I find that whilst linking in src/bin/csh, the linker complains about not finding the following symbols: s_strlen s_strcmp vis_str short2str This all takes place during my attempt to do a make buildworld with the 3_4_0_RELEASE sources. I am currently on a 3.2-RELEASE system. Regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 0:52:11 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from Thingol.KryptoKom.DE (Thingol.KryptoKom.DE [194.245.91.1]) by hub.freebsd.org (Postfix) with ESMTP id 94F4114D35 for ; Fri, 7 Jan 2000 00:52:08 -0800 (PST) (envelope-from Etienne.DeBruin@KryptoKom.DE) Received: (from root@localhost) by Thingol.KryptoKom.DE (8.9.1/8.9.3) id JAA07726 for ; Fri, 7 Jan 2000 09:50:59 +0100 Received: from cirdan.kryptokom.de by KryptoWall via smtpp (Version 1.2.0) id kwa07722; Fri Jan 07 09:50:46 2000 Received: from nt-notes.kryptokom.de (nt-notes.kryptokom.de [192.168.6.247]) by cirdan.kryptokom.de (8.9.3/8.9.3) with SMTP id JAA19421 for ; Fri, 7 Jan 2000 09:50:46 +0100 Received: by nt-notes.kryptokom.de(Lotus SMTP MTA v4.6.3 (733.2 10-16-1998)) id C125685F.0030BE4A ; Fri, 7 Jan 2000 09:52:24 +0100 X-Lotus-FromDomain: UTIMACO From: "Etienne De Bruin" To: hackers@freebsd.org Message-ID: Date: Fri, 7 Jan 2000 09:52:19 +0100 Subject: Compiling 3.4-RELEASE problems Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When compiling 3.4-RELEASE I find that whilst linking in src/bin/csh, the linker complains about not finding the following symbols: s_strlen s_strcmp vis_str short2str This all takes place during my attempt to do a make buildworld with the 3_4_0_RELEASE sources. I am currently on a 3.2-RELEASE system. Regards To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 6:46:48 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from phoenix.aye.net (phoenix.aye.net [198.7.192.5]) by hub.freebsd.org (Postfix) with SMTP id E7D1D1576C for ; Fri, 7 Jan 2000 06:46:40 -0800 (PST) (envelope-from barrett@aye.net) Received: (qmail 3458 invoked by uid 1000); 7 Jan 2000 14:45:48 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Jan 2000 14:45:48 -0000 Date: Fri, 7 Jan 2000 09:45:48 -0500 (EST) From: Barrett Richardson To: John Ioannidis Cc: freebsd-hackers@freebsd.org, freebsd-net@freebsd.org Subject: Re: Help, I'm stuck! Weird network/routing question. In-Reply-To: <200001062323.SAA29559@bual.research.att.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, 6 Jan 2000, John Ioannidis wrote: > Here is the setup: > > Hosts alice and bob, running 3.4-STABLE, xl interfaces. > > on alice: > # ifconfig xl1 10.1.1.1 up netmask 255.255.255.255 > # ifconfig xl1 10.1.1.2 up netmask 255.255.255.255 > > > So, what's the right way to do this? (No, I can't have a shorter > subnet mask and put both interfaces on the same subnet! Needless to > say, what I've described is the simplified problem). There has to be > a way to tell the routing code "this address may not look like it's on > any of your subnets, but the way to reach it is to ARP for it through > interface xl1". There was definitely a way of doing this back in the > SunOS 4 (and before) days. > > Help? You could try publishing an arp entry for 10.1.1.2 on 10.1.1.1 (and vice versa on 10.1.1.1) using the MAC addresses physically associated with the respective IPs of course. The boxen may consider the arp entries of no consequence being that neither considers the other host to be on an attached subnet. As an alternative you could place the IPs on the loopback interfaces as aliases using the ethernet addresses as gateways to these IPs. - Barrett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 7:33:42 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 2BCF014FBC for ; Fri, 7 Jan 2000 07:33:40 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id QAA12752 for ; Fri, 7 Jan 2000 16:33:39 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id QAA19283 for ; Fri, 7 Jan 2000 16:33:45 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id QAA67958 for hackers@freebsd.org; Fri, 7 Jan 2000 16:33:39 +0100 (CET) Date: Fri, 7 Jan 2000 16:33:39 +0100 (CET) From: Christoph Kukulies Message-Id: <200001071533.QAA67958@gil.physik.rwth-aachen.de> To: hackers@freebsd.org Subject: sppp behaviour Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the 'normal' behaviour for a rlogin (ssh) or telnet session when one is logging into an ISP who assigns dynamic addresses and the connection has an idle timer (inactivity) (that is, the connection is dropped after a certain time period). I have the problem that with FreeBSDs isdn (i4b) my rlogin (ssh) sessions die (are rendered unusable - lock o' city) regularly when the idle timer drops the connection. A subsequent awaking of the connection results in a different IP address being assigned from the ISP. Strangely Netscape does not suffer from this phenomenon. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 8: 6: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id A7D9014DA3 for ; Fri, 7 Jan 2000 08:06:04 -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 CAA41219; Sat, 8 Jan 2000 02:35:28 +1030 (CST) (envelope-from newton) Date: Sat, 8 Jan 2000 02:35:28 +1030 From: Mark Newton To: Christoph Kukulies Cc: hackers@FreeBSD.ORG Subject: Re: sppp behaviour Message-ID: <20000108023528.B41147@internode.com.au> References: <200001071533.QAA67958@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200001071533.QAA67958@gil.physik.rwth-aachen.de> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 07, 2000 at 04:33:39PM +0100, Christoph Kukulies wrote: > What is the 'normal' behaviour for a rlogin (ssh) or telnet session > when one is logging into an ISP who assigns dynamic addresses and > the connection has an idle timer (inactivity) (that is, the connection is > dropped after a certain time period). Same as on any other OS: You get a new IP address when you reestablish your connection to the ISP, so the hosts at the other ends of any active network connections you happened to have open when you dropped your link will be sending their ACKs and data to someone else (who will no doubt start sending RST's, clearing the connections altogether, if anyone is responding on your old address at all). > I have the problem that with FreeBSDs isdn (i4b) my rlogin (ssh) > sessions die (are rendered unusable - lock o' city) regularly when > the idle timer drops the connection. A subsequent awaking of the connection > results in a different IP address being assigned from the ISP. This is perfectly normal, and is why "dial on demand IP with an idle timeout" sucks ass. > Strangely Netscape does not suffer from this phenomenon. That's because Netscape (and all other web browsers) create separate short-lived TCP connections for each URL they fetch, and when you leave it idle it doesn't maintain any open connections at all (usually; your Java applets will probably screw up if they expect to have persistent connections back to the host they were loaded from). - 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 Fri Jan 7 8:15:10 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cichlids.com (as3-055.rp-plus.de [149.221.238.247]) by hub.freebsd.org (Postfix) with ESMTP id F01B715786 for ; Fri, 7 Jan 2000 08:15:04 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id C27ADAB92 for ; Fri, 7 Jan 2000 17:15:05 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id RAA04227 for hackers@freebsd.org; Fri, 31 Dec 1999 17:14:23 +0100 (CET) (envelope-from alex) Date: Fri, 31 Dec 1999 17:14:23 +0100 From: Alexander Langer To: hackers@freebsd.org Subject: mktime(3) and strange struct tm entries Message-ID: <19991231171423.A4219@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Try the following: Take any year, minute, seconds, hours (etc...). set the struct tm accordingly. set the tm->tm_mon = 10 (November) set the tm->tm_mday = 31 (november has only 31 days) mktime(3) with this tm returns the date 1 Dezember. Does POSIX want this? Does anyone have the specs and could take a look? Or is this a bug? Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 8:20:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 82D99158F1 for ; Fri, 7 Jan 2000 08:20:38 -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 KAA20480; Fri, 7 Jan 2000 10:20:21 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Fri, 7 Jan 2000 10:20:21 -0600 (CST) From: David Scheidt To: Mark Newton Cc: Christoph Kukulies , hackers@FreeBSD.ORG Subject: Re: sppp behaviour In-Reply-To: <20000108023528.B41147@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 On Sat, 8 Jan 2000, Mark Newton wrote: > > I have the problem that with FreeBSDs isdn (i4b) my rlogin (ssh) > > sessions die (are rendered unusable - lock o' city) regularly when > > the idle timer drops the connection. A subsequent awaking of the connection > > results in a different IP address being assigned from the ISP. > > This is perfectly normal, and is why "dial on demand IP with an idle > timeout" sucks ass. It works if you have a static IP. ISDN helps, since connection setup time is short. It's wonderful if both sides of the link will bring it up for traffic. I have used this stuff to provide connections that appear nailed, and still get over 1 link per term server port. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 8:21:36 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cichlids.com (as3-055.rp-plus.de [149.221.238.247]) by hub.freebsd.org (Postfix) with ESMTP id C3BE515914 for ; Fri, 7 Jan 2000 08:21:34 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 33256AB92 for ; Fri, 7 Jan 2000 17:21:36 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id RAA04298 for hackers@FreeBSD.ORG; Fri, 7 Jan 2000 17:21:33 +0100 (CET) (envelope-from alex) Date: Fri, 7 Jan 2000 17:21:32 +0100 From: Alexander Langer To: hackers@FreeBSD.ORG Subject: Re: mktime(3) and strange struct tm entries Message-ID: <20000107172132.A4286@cichlids.cichlids.com> References: <19991231171423.A4219@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991231171423.A4219@cichlids.cichlids.com>; from alex@big.endian.de on Fri, Dec 31, 1999 at 05:14:23PM +0100 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Alexander Langer (alex@big.endian.de): > set the tm->tm_mday = 31 (november has only 31 days) ^^ 30, of course Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 8:23: 7 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 10A3915A2E for ; Fri, 7 Jan 2000 08:22:57 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id IAA16815; Fri, 7 Jan 2000 08:22:29 -0800 (PST) Date: Fri, 7 Jan 2000 08:22:29 -0800 (PST) From: David Wolfskill Message-Id: <200001071622.IAA16815@pau-amma.whistle.com> To: alex@big.endian.de, hackers@FreeBSD.ORG Subject: Re: mktime(3) and strange struct tm entries In-Reply-To: <19991231171423.A4219@cichlids.cichlids.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Fri, 31 Dec 1999 17:14:23 +0100 >From: Alexander Langer >Try the following: >Take any year, minute, seconds, hours (etc...). >set the struct tm accordingly. >set the tm->tm_mon = 10 (November) >set the tm->tm_mday = 31 (november has only 31 days) No. November has but 30 days. >mktime(3) with this tm returns the date 1 Dezember. This is the documented and intended behavior of mktime(). >Does POSIX want this? >Does anyone have the specs and could take a look? >Or is this a bug? It's a C library issue, rather than POSIX or -hackers. Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 8:24: 4 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id E794D157EF for ; Fri, 7 Jan 2000 08:24:00 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id RAA18372; Fri, 7 Jan 2000 17:18:46 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id RAA19756; Fri, 7 Jan 2000 17:18:53 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id RAA68221; Fri, 7 Jan 2000 17:18:51 +0100 (CET) Date: Fri, 7 Jan 2000 17:18:51 +0100 From: Christoph Kukulies To: Mark Newton Cc: Christoph Kukulies , hackers@FreeBSD.ORG Subject: Re: sppp behaviour Message-ID: <20000107171851.A68197@gil.physik.rwth-aachen.de> References: <200001071533.QAA67958@gil.physik.rwth-aachen.de> <20000108023528.B41147@internode.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000108023528.B41147@internode.com.au>; from newton@internode.com.au on Sat, Jan 08, 2000 at 02:35:28AM +1030 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 08, 2000 at 02:35:28AM +1030, Mark Newton wrote: > On Fri, Jan 07, 2000 at 04:33:39PM +0100, Christoph Kukulies wrote: > > > What is the 'normal' behaviour for a rlogin (ssh) or telnet session > > when one is logging into an ISP who assigns dynamic addresses and > > the connection has an idle timer (inactivity) (that is, the connection is > > dropped after a certain time period). > > Same as on any other OS: You get a new IP address when you reestablish > your connection to the ISP, so the hosts at the other ends of any active > network connections you happened to have open when you dropped your > link will be sending their ACKs and data to someone else (who will > no doubt start sending RST's, clearing the connections altogether, if > anyone is responding on your old address at all). > > > I have the problem that with FreeBSDs isdn (i4b) my rlogin (ssh) > > sessions die (are rendered unusable - lock o' city) regularly when > > the idle timer drops the connection. A subsequent awaking of the connection > > results in a different IP address being assigned from the ISP. > > This is perfectly normal, and is why "dial on demand IP with an idle > timeout" sucks ass. Well, 'dial on demand IP' worked perfectly a long as I had assigned a fixed IP address from my ISP (the university campus). This service has been dropped for a while (may be resurrected again). But it was very comfortable to have an editor open, a phone call comes inbetween, it takes 10 minutes. The ISDN line idle timeouts after 90 seconds and I could continue with the editor session after 10 minutes with the line going active again. (sure it's not quite like dialing, it establishing the connection at a lower level). But I'm thinking about how this sould be accomplished nonetheless technically. There are sockets open at both ends and the route gets lost inbetween. Could that be signalled to the process or could the subsequent route change be signalled to the connection to change the addresses it's bound to. What is KeepAlive for in this context? > > > Strangely Netscape does not suffer from this phenomenon. > > That's because Netscape (and all other web browsers) create separate > short-lived TCP connections for each URL they fetch, and when you leave > it idle it doesn't maintain any open connections at all (usually; your > Java applets will probably screw up if they expect to have persistent > connections back to the host they were loaded from). > > - 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 -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 8:29:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp1.vnet.net (smtp1.vnet.net [166.82.1.31]) by hub.freebsd.org (Postfix) with ESMTP id 7EC17157F2 for ; Fri, 7 Jan 2000 08:29:18 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp1.vnet.net (8.9.1a/8.9.1) with ESMTP id LAA29233; Fri, 7 Jan 2000 11:28:50 -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 LAA13350; Fri, 7 Jan 2000 11:28:48 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id LAA76267; Fri, 7 Jan 2000 11:28:48 -0500 (EST) Date: Fri, 7 Jan 2000 11:28:48 -0500 (EST) From: Thomas David Rivers Message-Id: <200001071628.LAA76267@lakes.dignus.com> To: alex@big.endian.de, hackers@FreeBSD.ORG Subject: Re: mktime(3) and strange struct tm entries In-Reply-To: <19991231171423.A4219@cichlids.cichlids.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hello! > > Try the following: > > Take any year, minute, seconds, hours (etc...). > > set the struct tm accordingly. > set the tm->tm_mon = 10 (November) > set the tm->tm_mday = 31 (november has only 31 days) > > mktime(3) with this tm returns the date 1 Dezember. > > Does POSIX want this? > Does anyone have the specs and could take a look? > Or is this a bug? I believe this is correct behaviour. - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 8:36:32 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cichlids.com (as3-055.rp-plus.de [149.221.238.247]) by hub.freebsd.org (Postfix) with ESMTP id E47461570A for ; Fri, 7 Jan 2000 08:36:24 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 3B897AB92; Fri, 7 Jan 2000 17:36:26 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id RAA04473; Fri, 7 Jan 2000 17:36:23 +0100 (CET) (envelope-from alex) Date: Fri, 7 Jan 2000 17:36:23 +0100 From: Alexander Langer To: Thomas David Rivers Cc: hackers@FreeBSD.ORG Subject: Re: mktime(3) and strange struct tm entries Message-ID: <20000107173623.B4381@cichlids.cichlids.com> References: <19991231171423.A4219@cichlids.cichlids.com> <200001071628.LAA76267@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001071628.LAA76267@lakes.dignus.com>; from rivers@dignus.com on Fri, Jan 07, 2000 at 11:28:48AM -0500 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Thomas David Rivers (rivers@dignus.com): > I believe this is correct behaviour. Ok. I got a further question: From ctime(3): til tm_mon and tm_year are determined. Mktime() returns the specified calendar time; if the calendar time cannot be represented, it returns -1; Which calendar time is meant? IMO November 31th is void and cannot be represented. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 9:44:14 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 2FE4514FE2 for ; Fri, 7 Jan 2000 09:44:12 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id LAA23363; Fri, 7 Jan 2000 11:43:37 -0600 (CST) (envelope-from dan) Date: Fri, 7 Jan 2000 11:43:37 -0600 From: Dan Nelson To: Alexander Langer Cc: Thomas David Rivers , hackers@FreeBSD.ORG Subject: Re: mktime(3) and strange struct tm entries Message-ID: <20000107114337.A17459@dan.emsphone.com> References: <19991231171423.A4219@cichlids.cichlids.com> <200001071628.LAA76267@lakes.dignus.com> <20000107173623.B4381@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000107173623.B4381@cichlids.cichlids.com>; from "Alexander Langer" on Fri Jan 7 17:36:23 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 07), Alexander Langer said: > Thus spake Thomas David Rivers (rivers@dignus.com): > > > I believe this is correct behaviour. > > Ok. I got a further question: > >From ctime(3): > til tm_mon and tm_year are determined. Mktime() returns the > specified calendar time; if the calendar time cannot be > represented, it returns -1; > > Which calendar time is meant? > IMO November 31th is void and cannot be represented. The manpage also states: The original values of the tm_wday and tm_yday components of the structure are ignored, and the original values of the other components are not restricted to their normal ranges. ... On successful completion, the values of the tm_wday and tm_yday components of the structure are set appropriately, and the other components are set to represent the specified calendar time, but with their values forced to their normal ranges. Nov 31 cannot be represented, but it gets normalized to Dec 1. The only non-representable dates are those that cannot be stored in a time_t. -- 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 Jan 7 10:21:55 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.bfm.org (mail.bfm.org [216.127.218.26]) by hub.freebsd.org (Postfix) with ESMTP id D4AB114ED6 for ; Fri, 7 Jan 2000 10:21:46 -0800 (PST) (envelope-from adam@whizkidtech.net) Received: from WhizKid (r5.bfm.org [216.127.220.101]) by mail.bfm.org (Post.Office MTA v3.5 release 215 ID# 0-52399U2500L250S0V35) with SMTP id org; Fri, 7 Jan 2000 12:21:43 -0600 Message-Id: <3.0.6.32.20000107122223.009ab930@mail85.pair.com> X-Sender: whizkid@mail85.pair.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Fri, 07 Jan 2000 12:22:23 -0600 To: Alexander Langer , hackers@FreeBSD.ORG From: "G. Adam Stanislav" Subject: Re: mktime(3) and strange struct tm entries In-Reply-To: <19991231171423.A4219@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 17:14 31-12-1999 +0100, Alexander Langer wrote: >mktime(3) with this tm returns the date 1 Dezember. > >Does POSIX want this? >Does anyone have the specs and could take a look? >Or is this a bug? Says POSIX Programmer's Guide, by Donald Lewine: "The mktime() function is not required to reject invalid dates. For example, November 55th may be equivalent to December 25th." Does that answer your questions? Cheers, Adam To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 11: 1:55 2000 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 987F714F65 for ; Fri, 7 Jan 2000 11:01:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA88409; Fri, 7 Jan 2000 11:01:42 -0800 (PST) (envelope-from dillon) Date: Fri, 7 Jan 2000 11:01:42 -0800 (PST) From: Matthew Dillon Message-Id: <200001071901.LAA88409@apollo.backplane.com> To: Brett Glass Cc: hackers@freebsd.org Subject: Re: Possible optimization in VM? References: <4.2.2.20000106220706.00b67650@localhost> <4.2.2.20000107004708.01c12740@localhost> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Yes, if you had C3, C4, etc. (multiple children), you'd need to make sure :that each of them could get at what was originally in B. This means :more copying -- either to each of the C's or someplace else. : :The thing is, most forks are followed by execs. The most common case :is that they would never look at the old contents of B. So, it pays :to make the copy operation as "lazy" as possible, since the odds are :that not a single child will look at B. The copy operation is already as lazy as it can get, with or without C2. C2 itself is just a struct vm_object -- very cheap for the kernel to create. :> optimization if we start throwing pages into C1 that C1 didn't touch :> itself. The C1 layer may wind up contaiing a significant number of :> *additional* dirty pages, pages the child never actually touched :> itself and thus pages that an additional forked child of the child :> probably will not ever touch. : :They'd be substitutes for pages that would have been in C2, so we'd :have as many dirty pages in either case, right? Yes, you would. They would all be concentrated in C1. :> This will prevent the 'All Shadowed' :> optimization from occuring, resulting in a potentially deep VM Object :> layering on one side of the graph. : :Hmmm. It seems to me that it would cause more pages to be "shadowed," thus :actually accelerating the application of the optimization. Am I off base here? No, just having 'more' doesn't help. They must be the correct pages -- the ones most likely to be touched if the sublayer forks again -- for the optimization to work. I don't think the number of pages, fewer or greater, really matters. :> then the C1,C2 -> B case where the collapsability of layers is visually :> obvious. : :Well, in essence, we've really collapsed C2 into B (since it's serving to hold :the parent's pages). So, haven't we already "won" by going straight to the state :that an optimization might have achieved? : :--Brett You haven't really collapsed C2 into B because you still can't collapse C1 and B together. All you've really done is simply avoided creating C2 and possibly helped with the dead-page case a bit, but you unbalanced the VM Layering in the process. -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 Fri Jan 7 12: 2:50 2000 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 4167614DAE for ; Fri, 7 Jan 2000 12:02:38 -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 MAA24442; Fri, 7 Jan 2000 12:02:35 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id MAA09037; Fri, 7 Jan 2000 12:02:34 -0800 Received: from softweyr.com (dyn1.utah.xylan.com [198.206.184.237]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id MAA08544; Fri, 7 Jan 2000 12:01:23 -0800 (PST) Message-ID: <3876471F.B2EDAA1E@softweyr.com> Date: Fri, 07 Jan 2000 13:05:51 -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: Pete Mckenna , 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> <386D66D4.B3DB5EB3@softweyr.com> <387501B2.C01766F@uswest.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pete Mckenna wrote: > > Wes, > Have you managed to test the switch and if so how did it do ? I have a > FS-108 on order. Yes. I bought two FS-105's, one for me and one for a co-worker. CompUSA had a $20 rebate on them from 12/26 - 1/1, making them $99. We attacked Rich's switch in the lab. We plugged ports 1-4 into 4 10/100 ports on a SmartBits 2000 test chassis and banged it with full-duplex bi- directional streams between ports 1<->2 and 3<->4. I am happy to report that it passed 100% of traffic at all packet sizes except 64 bytes, where it was still able to pass 99.415% of wire speed, or 591,716 packets per second. This is quite impressive for such an inexpensive switch, and should perform adequately for my 3-system NFS nightmare I'm building at home. ;^) -- "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 Fri Jan 7 13:29:22 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id B26B91586D for ; Fri, 7 Jan 2000 13:29:19 -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 QAA26840 for ; Fri, 7 Jan 2000 16:29:16 -0500 (EST) Date: Fri, 7 Jan 2000 15:15:22 -0500 (EST) From: Zhihui Zhang To: freebsd-hackers@freebsd.org Subject: negative value from timersub() in time.h 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 use the following statements to time the system time used by a routine: struct rusage ru_start, ru_end; struct timeval stime; getrusage(RUSAGE_SELF, &ru_start); call the routine getrusage(RUSAGE_SELF, &ru_end); timersub(&ru_end.ru_stime, &ru_start.ru_stime, &stime); Sometimes I find that the value of stime.tv_sec is negative (-1). Can anyone explain the reason for me? 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 Fri Jan 7 13:46:35 2000 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 981C214CAC for ; Fri, 7 Jan 2000 13:46:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA01836; Fri, 7 Jan 2000 13:46:28 -0800 (PST) (envelope-from dillon) Date: Fri, 7 Jan 2000 13:46:28 -0800 (PST) From: Matthew Dillon Message-Id: <200001072146.NAA01836@apollo.backplane.com> To: Wes Peters Cc: Pete Mckenna , 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> <386D66D4.B3DB5EB3@softweyr.com> <387501B2.C01766F@uswest.net> <3876471F.B2EDAA1E@softweyr.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :We attacked Rich's switch in the lab. We plugged ports 1-4 into 4 10/100 :ports on a SmartBits 2000 test chassis and banged it with full-duplex bi- :directional streams between ports 1<->2 and 3<->4. I am happy to report :that it passed 100% of traffic at all packet sizes except 64 bytes, where :it was still able to pass 99.415% of wire speed, or 591,716 packets per :second. This is quite impressive for such an inexpensive switch, and should :perform adequately for my 3-system NFS nightmare I'm building at home. ;^) : :-- : :Wes Peters Softweyr LLC :wes@softweyr.com http://softweyr.com/ That is simply amazing. You know, even just two years ago this kind of performance would have cost a considerable amount of money. I'm really happy with my apartment LAN. Both the D-Link and the LinkSys 5-port 100BaseT switches operate wonderfully for me (now that Bill Paul and I finally tracked down the D-Link ethernet card bugs!). I think the next thing I'm going to do with NFS is figure out why I can't get wire speed in both directions simultaniously over full-duplex 100BaseTX links. I mean, gee, it's *only* 20 MBytes/sec! - BTW, Kudos to the KAME folk, the ipv6 and ipsec stuff looks like it's going to turn into a winner! IPSEC is going to be one really good reason for needing ever-faster cpu's :-). -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 Fri Jan 7 13:49:58 2000 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 D1FC7154E1 for ; Fri, 7 Jan 2000 13:49:55 -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 RAA74947; Fri, 7 Jan 2000 17:01:13 -0500 (EST) Date: Fri, 7 Jan 2000 17:01:13 -0500 (EST) From: Ben Rosengart To: Matthew Dillon Cc: Wes Peters , Pete Mckenna , freebsd-hackers@FreeBSD.ORG Subject: Re: Cool little 100BaseTX switch - they're coming down in price In-Reply-To: <200001072146.NAA01836@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 Fri, 7 Jan 2000, Matthew Dillon wrote: > BTW, Kudos to the KAME folk, the ipv6 and ipsec stuff looks like it's > going to turn into a winner! IPSEC is going to be one really good reason > for needing ever-faster cpu's :-). Maybe Intel should have been approached for financial assistance with the integration ... ;-) -- 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 Fri Jan 7 16:22:37 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from cichlids.com (as1-030.rp-plus.de [149.221.236.30]) by hub.freebsd.org (Postfix) with ESMTP id 5AA1B14F3F for ; Fri, 7 Jan 2000 16:22:35 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 162FEAB92; Sat, 8 Jan 2000 01:17:08 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id BAA05560; Sat, 8 Jan 2000 01:17:05 +0100 (CET) (envelope-from alex) Date: Sat, 8 Jan 2000 01:17:05 +0100 From: Alexander Langer To: Dan Nelson Cc: Thomas David Rivers , hackers@FreeBSD.ORG Subject: Re: mktime(3) and strange struct tm entries Message-ID: <20000108011705.A4735@cichlids.cichlids.com> References: <19991231171423.A4219@cichlids.cichlids.com> <200001071628.LAA76267@lakes.dignus.com> <20000107173623.B4381@cichlids.cichlids.com> <20000107114337.A17459@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000107114337.A17459@dan.emsphone.com>; from dnelson@emsphone.com on Fri, Jan 07, 2000 at 11:43:37AM -0600 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Dan Nelson (dnelson@emsphone.com): > Nov 31 cannot be represented, but it gets normalized to Dec 1. The > only non-representable dates are those that cannot be stored in a > time_t. Ah, thank you. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 16:46:40 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 138881513F for ; Fri, 7 Jan 2000 16:46:38 -0800 (PST) (envelope-from anderson@cs.duke.edu) Received: from cold.cs.duke.edu (cold.cs.duke.edu [152.3.140.78]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id TAA07143 for ; Fri, 7 Jan 2000 19:46:31 -0500 (EST) From: Darrell Anderson Received: (anderson@localhost) by cold.cs.duke.edu (8.8.5/8.6.9) id TAA22361 for hackers@FreeBSD.ORG; Fri, 7 Jan 2000 19:46:31 -0500 (EST) Message-Id: <200001080046.TAA22361@cold.cs.duke.edu> Subject: ddb call & interrupts To: hackers@FreeBSD.ORG Date: Fri, 7 Jan 2000 19:46:31 -0500 (EST) X-Mailer: ELM [version 2.5 PL2] 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 a routine that sends an ip packet and receives an ack. The routine behaves as expected when called from an active kernel, but misbehaves when called from ddb. When called from ddb, the outgoing packet is sent, but the ack goes undetected. If I call fxp_intr() on the appropriate softc the ack is delivered and everybody is happy. This suggests interrupts aren't being delivered? A simpler test is to break to ddb, call something that takes some time, and notice ticks isn't incremented: db> e ticks ticks: 8de4bb db> call DELAY(1000000) 0xfa3 db> e ticks ticks: 8de4bb I'd like to be able to call my routine from ddb without resorting to polling. I've tried spl0(), enable_intr(), and both together with no effect. Any ideas? This is FreeBSD 4.0-CURRENT built from an up-to-date source pool. thanks, -Darrell -- Department of Computer Science, Duke University, Durham, NC 27708-0129 Darrell Anderson, anderson@cs.duke.edu, http://www.cs.duke.edu/~anderson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 18:13:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from scrabble.freeuk.net (scrabble.freeuk.net [212.126.144.6]) by hub.freebsd.org (Postfix) with ESMTP id 5DB57158AB for ; Fri, 7 Jan 2000 18:11:37 -0800 (PST) (envelope-from andrew@ukug.uk.FreeBSD.org) Received: from [212.126.147.132] (helo=cream.org) by scrabble.freeuk.net with esmtp (Exim 2.11 #1) id 126lLr-0003mS-00 for hackers@freebsd.org; Sat, 8 Jan 2000 02:11:35 +0000 Content-Length: 2108 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: Sat, 08 Jan 2000 02:11:54 -0000 (GMT) From: Andrew Boothman To: hackers@freebsd.org Subject: Automatic Documentation Index Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [This was posted to -ports, to no response] Happy New Year, everyone! With the world apparently still in one piece after the celebrations and the few Y2K incidents, I guess we're back to our regular transmissions. Since this message is going outside of -doc where it has been discussed before, I'll offer up a full explanation of what's going on. What is proposed is a system where all the documentation installed through the ports system, or locally by a sysadmin, is collected together and indexed on one HTML page; say /usr/local/share/doc/instdocs.html This page is created by a perl script, docindex, which I envisage being run either from a /etc/periodic/* or /etc/rc or both. The script gets its information from +DOCS files contained within the /var/db/pkg directory for each installed port. These files consist of three fields, colon seperated. The first field being the name of the item of documentation, the second being a filetype, and the third a full path to the file. For example, for Sharity Light : FAQ:txt:/usr/local/share/doc/Sharity-Light/FAQ README:txt:/usr/local/share/doc/Sharity-Light/README In addition the local sysadmin can add similarly formatted files into, say, /etc/docs.local/ that will also be read in and included in the index. In order to help the ports maintainers, and others, create these DOCS files that will be needed, there is a script called docsmaker. This script has a _very_ rough guess from the CONTENTS file of a port what might be documentation. But I stress that the file which it creates will still need to be checked for files that shouldn't be there, files that have been missed, and any other stupid mistakes. :-) Right, I think I'm just about finished. Apart from to say that current versions of the scripts I've been talking about and example outputs from all this are available from http://ukug.uk.freebsd.org/~andrew/docindex/ Does anyone have any thoughts or comments on how to proceed? 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 Fri Jan 7 20:10:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 021F814FE0 for ; Fri, 7 Jan 2000 20:10:52 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <20000108040840.PNMA7552.mail.rdc3.on.home.com@tristan.net>; Fri, 7 Jan 2000 20:08:40 -0800 Content-Length: 1918 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000107171851.A68197@gil.physik.rwth-aachen.de> Date: Fri, 07 Jan 2000 23:07:37 -0500 (EST) From: Colin To: Christoph Kukulies Subject: Re: sppp behaviour Cc: hackers@FreeBSD.ORG, Mark Newton Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Jan-2000 Christoph Kukulies wrote: >> >> Same as on any other OS: You get a new IP address when you reestablish >> your connection to the ISP, so the hosts at the other ends of any active >> network connections you happened to have open when you dropped your >> link will be sending their ACKs and data to someone else (who will >> no doubt start sending RST's, clearing the connections altogether, if >> anyone is responding on your old address at all). This is only true if the connection was gone long enough for your lease from the DHCP server to expire or the DHCP server is configured to not re-issue an address requested by a dynamically served host on reconnect. > But I'm thinking about how this sould be accomplished nonetheless > technically. There are sockets open at both ends and the route gets > lost inbetween. Could that be signalled to the process or could the > subsequent route change be signalled to the connection to change > the addresses it's bound to. > > What is KeepAlive for in this context? > Even though there are potentially open sockets at each end, your host has a new address. There is no reasonable way to associate the new address with the old address from the perspective of the other end. If nothing else, any checks based on reverse look-ups and such are automatically useless. The security implications of a process such as you are describing is more than a little scary ;) It would take the script-kiddies about 15 minutes to learn how to spoof such a dynamic route change. To avoid this whole situation you'll need some kind of heart-beat across the connection. Maybe a short perl script to do a reverse look-up on yourself at intervals of half the idle timeout period? ---------------------------------- E-Mail: Colin Date: 07-Jan-2000 Time: 22:52:36 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 20:24:47 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id A7DDF15237 for ; Fri, 7 Jan 2000 20:24:45 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <20000108042234.PPFS7552.mail.rdc3.on.home.com@tristan.net>; Fri, 7 Jan 2000 20:22:34 -0800 Content-Length: 703 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 07 Jan 2000 23:21:31 -0500 (EST) From: Colin To: hackers@FreeBSD.ORG Subject: Re: sppp behaviour Cc: Mark Newton , Cc: Mark Newton , Christoph Kukulies Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is only true if the connection was gone long enough for your lease > from the DHCP server to expire or the DHCP server is configured to not > re-issue > an address requested by a dynamically served host on reconnect. It occurs to me that I'm assuming a reboot/renew type request when the connection is re-established. I would think this might not be completely accurate ;) Thinking about it I would suspect a complete DHCP-discovery-request-etc would be a better choice here, but I haven't looked at the code. ---------------------------------- E-Mail: Colin Date: 07-Jan-2000 Time: 23:14:38 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 21:20:25 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id A9600150B2 for ; Fri, 7 Jan 2000 21:20:22 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:Erm65dRgv2+PrX+w1MoLbpzQEkPkvFtG@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id OAA14067; Sat, 8 Jan 2000 14:20:08 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id OAA13803; Sat, 8 Jan 2000 14:25:32 +0900 (JST) Message-Id: <200001080525.OAA13803@zodiac.mech.utsunomiya-u.ac.jp> To: Lyndon Nerenberg Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Reading kbd scancodes from userland In-reply-to: Your message of "Wed, 05 Jan 2000 16:32:28 MST." <200001052332.e05NWSr84505@orthanc.ab.ca> References: <200001052332.e05NWSr84505@orthanc.ab.ca> Date: Sat, 08 Jan 2000 14:25:31 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, >Failing that, has anyone figured out a keyboard mapping for an >Inspiron 7000 that puts the left ALT key back where it belongs? >(The reason for the first request is to try to determine what >effect the left ALT key actually has. On this laptop, the "windows" >key does what left ALT normally does, making life miserable when >running a non-win98 external keyboard.) This is pretty wiered. You mean the REAL left ALT key doesn't work on this notebook and the external keyboard? Can you veryfy that the same problem exists in other OS, such as W*ndows, environments? If so, I suspect there is a bug in the keyboard controller firmare, which traslates keyboard signal into scan codes. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Fri Jan 7 21:48:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 3365F150B2 for ; Fri, 7 Jan 2000 21:48:52 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:F3fZK5OgYwIUBH0jBpOT7ErECQ1bI8a5@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id OAA13379; Sat, 8 Jan 2000 14:48:40 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id OAA14530; Sat, 8 Jan 2000 14:53:59 +0900 (JST) Message-Id: <200001080553.OAA14530@zodiac.mech.utsunomiya-u.ac.jp> To: Cejka Rudolf Cc: hackers@freebsd.org, saper@system.pl, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: syscons: SC_MOUSE_CHAR value rationale In-reply-to: Your message of "Thu, 06 Jan 2000 21:24:04 +0100." <20000106212404.A30244@dcse.fee.vutbr.cz> References: <20000106212404.A30244@dcse.fee.vutbr.cz> Date: Sat, 08 Jan 2000 14:53:58 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Nearly everyone who wants to set up their national locale >> needs to recompile the kernel, since some important characters >> are hidden under mouse cursor. > >I agree with you - it is very strange for Czech users too (and maybe >for almost all ISO-8859-* users) - default mouse settings override some >important characters. Maybe we should ask Kazu if it is possible: > >1) Move SC_MOUSE_CHAR into sysctl tree as read-write value. Maybe we had better implement a new ioctl and use vidcontrol to set up mouse char codes. sysctl is to tweak the kernel behavior. I would rather hesitate to use it to customize device drivers, unless it has something to do with kernel state/behavior and/or security; this is not the case with SC_MOUSE_CHAR. >2) Make SC_ALT_MOUSE_IMAGE as default setting. Hmmm. I would surprise people... >But Kazu have cleared off in December and I don't know where he is... I am here :-) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 6:22:18 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from ratatosk.utfors.se (ratatosk.utfors.se [195.58.103.123]) by hub.freebsd.org (Postfix) with ESMTP id F2119152D4 for ; Sat, 8 Jan 2000 06:22:12 -0800 (PST) (envelope-from bahl@privat.utfors.se) Received: from privat.utfors.se (md4691c53.utfors.se) by ratatosk.utfors.se (Sun Internet Mail Server sims.3.5.1999.07.30.00.05.p8) with ESMTP id <0FO0003PBT8WTI@ratatosk.utfors.se> for freebsd-hackers@freebsd.org; Sat, 8 Jan 2000 15:22:10 +0100 (MET) Date: Sat, 08 Jan 2000 15:26:31 +0100 From: Bjorn Subject: i82802 Random Number Generator Patch To: freebsd-hackers@freebsd.org Message-id: <38774917.10525B2D@privat.utfors.se> MIME-version: 1.0 X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) Content-type: multipart/mixed; boundary="------------C99821942D3FF73DD20B09A4" X-Accept-Language: en Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------C99821942D3FF73DD20B09A4 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi. This is my first post to FreeBSD-Hackers. It's probably the wrong place at the wrong time and totaly inappropriate in general, so start flaming right now. Anyway, I've writting a small patch to enable the thermal noise random number generator found in the i82802 (i82810). It breaks the /dev/random semantics slightly as the bitpool never run out of fresh bits. Hopefully somebody finds it usefull :-). I do. BTW, the patch is against the REL-3.3 kernel and x86-only. /Bjorn --------------C99821942D3FF73DD20B09A4 Content-Type: text/plain; charset=us-ascii; name="rng.patch" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="rng.patch" diff -Nru sys.orig/i386/conf/files.i386 sys/i386/conf/files.i386 --- sys.orig/i386/conf/files.i386 Mon Sep 6 00:35:34 1999 +++ sys/i386/conf/files.i386 Fri Jan 7 00:21:44 2000 @@ -79,6 +79,7 @@ i386/i386/globals.s standard i386/i386/i386-gdbstub.c optional ddb i386/i386/i686_mem.c standard +i386/i386/i82802_rng.c standard i386/i386/identcpu.c standard i386/i386/in_cksum.c optional inet i386/i386/initcpu.c standard diff -Nru sys.orig/i386/i386/i82802_rng.c sys/i386/i386/i82802_rng.c --- sys.orig/i386/i386/i82802_rng.c Thu Jan 1 00:00:00 1970 +++ sys/i386/i386/i82802_rng.c Fri Jan 7 09:38:43 2000 @@ -0,0 +1,68 @@ +/* $Id$ + * + * Copyright (c) 2000 Bjorn Ahlqvist. + * All rights reserved. + * + * v1.0 - Initial version. + * + * TODO: We should make sure we're really receiving something + * that look random. The specification suggests FIPS 140-1. + * + */ + +#include +#include +#include +#include +#include +#include + +#include +#include +#include + +#include +#include + +#define I82802_RNG_NAME "i82802 thermal noise random number generator" + +#define I82802_HW_RNG_ENABLE 1 /* hw_status */ +#define I82802_HW_RNG_PRESENT 0x40 /* hw_status */ +#define I82802_RNG_DATA_PRESENT 1 /* rng_status */ +#define I82802_RNG_BASE 0xffbc0000 /* absolute address */ +#define I82802_RNG_DELAY 5 /* about 4.5 ms */ + +struct i82802_rng { + u_char fill[0x015f]; + u_char hw_status; + u_char rng_status; + u_char rng_data; +}; + + +static struct i82802_rng *rngp; +int rng_present; + +u_char rng_read(void) +{ + while(!(rngp->rng_status&I82802_RNG_DATA_PRESENT)) { /* wait.. */ + if(!curproc) DELAY(I82802_RNG_DELAY); /* ..for data */ + else tsleep(&rng_read,PRIBIO,"rngrd",1); + } + + return(rngp->rng_data); /* got some */ +} + +static void rng_probe(void *dummy) +{ + rngp=pmap_mapdev(I82802_RNG_BASE,sizeof(*rngp)); /* wire mem */ + + rng_present=rngp->hw_status&I82802_HW_RNG_PRESENT; /* present? */ + if(!rng_present) return; /* no return */ + rngp->hw_status|=I82802_HW_RNG_ENABLE; /* yes enable */ + + printf(I82802_RNG_NAME" at 0x%08x enabled.\n",I82802_RNG_BASE); +} + +SYSINIT(rng,SI_SUB_DRIVERS,SI_ORDER_ANY,rng_probe,NULL) + diff -Nru sys.orig/i386/include/random.h sys/i386/include/random.h --- sys.orig/i386/include/random.h Sun Aug 29 16:06:47 1999 +++ sys/i386/include/random.h Fri Jan 7 02:34:17 2000 @@ -66,8 +66,13 @@ int sc_intr; }; +/* Exported variables */ + +extern int rng_present; + /* Exported functions */ +u_char rng_read(void); void rand_initialize(void); void add_keyboard_randomness(u_char scancode); inthand2_t add_interrupt_randomness; diff -Nru sys.orig/i386/isa/random_machdep.c sys/i386/isa/random_machdep.c --- sys.orig/i386/isa/random_machdep.c Sun Aug 29 16:07:31 1999 +++ sys/i386/isa/random_machdep.c Fri Jan 7 09:36:37 2000 @@ -325,6 +325,13 @@ u_int read_random(void *buf, u_int nbytes) { + int i; + + if (rng_present) { /* Hardware RNG */ + for(i=0;i random_state.entropy_count) nbytes = random_state.entropy_count / 8; --------------C99821942D3FF73DD20B09A4-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 8:16:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from news.IAEhv.nl (news.IAE.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id D59E514F0D for ; Sat, 8 Jan 2000 08:16:42 -0800 (PST) (envelope-from Arjan.deVet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id RAA15265 for hackers@freebsd.org; Sat, 8 Jan 2000 17:16:41 +0100 (MET) Received: by adv.iae.nl (Postfix, from userid 100) id 5BB8622F4; Sat, 8 Jan 2000 17:16:23 +0100 (CET) Date: Sat, 8 Jan 2000 17:16:23 +0100 To: hackers@freebsd.org Subject: postfix, NO_SENDMAIL and /bin/rmail for UUCP Message-ID: <20000108171622.A3738@adv.iae.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i From: Arjan.deVet@adv.iae.nl (Arjan de Vet) Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running postfix and am using UUCP. I have NO_SENDMAIL=yes in /etc/make.conf but this has the side-effect of not installing/updating /bin/rmail which uucp needs for submitting received mail to /usr/sbin/sendmail (which is the 'fake' sendmail from postfix in this case). Should we install rmail irrespective of the NO_SENDMAIL variable? Or should it become part of the mailwrapper? Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 9:52:12 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from moffetimages.com (alar.scruz.predictive.com [207.251.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 55AAE1502F for ; Sat, 8 Jan 2000 09:52:08 -0800 (PST) (envelope-from brianm@moffetimages.com) Received: (from brianm@localhost) by moffetimages.com (8.9.3/8.9.3) id JAA06103 for freebsd-hackers@FreeBSD.ORG; Sat, 8 Jan 2000 09:52:19 -0800 (PST) (envelope-from brianm) Date: Sat, 8 Jan 2000 09:52:19 -0800 (PST) From: "Brian D. Moffet" Message-Id: <200001081752.JAA06103@moffetimages.com> To: freebsd-hackers@FreeBSD.ORG Subject: multi-nics in FreeBSD 3.3 Release In-Reply-To: <200001072146.NAA01836@apollo.backplane.com> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of course some one knows this, but does FreeBSD support 2 NICS? I have a 3com 3c905 and a 3com 3c509 in my box, but no matter how I adjust the configuration file, I cannot get the 509 to be recognized. I could put the Ne2000 clone in there instead, but the 509 is a better card. Also, does the sio driver support PCI sio boards? The 3com / US Robotics 56K faxmodem is an sio card with a modem on the other side, so that the computer should be able to talk to it as a 16550. Though the IO address may be a bit strange (in the 0x4000 or 0xa000 range). I guess this boils down to 2 questions, IO space as well as PCI interrupts. And as soon as I find out more information, I plan on modifying pciconf to be able to parse more of the PCI BIOS information instead of just the vendor and card IDs, unless someone has already done so. Where should I send the changes? Thanks Brian Moffet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 10:10:44 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id D1AC21579D for ; Sat, 8 Jan 2000 10:10:38 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id NAA42770; Sat, 8 Jan 2000 13:10:31 -0500 (EST) Date: Sat, 8 Jan 2000 13:10:31 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Kazutaka YOKOTA Cc: Cejka Rudolf , hackers@FreeBSD.ORG, saper@system.pl Subject: Re: syscons: SC_MOUSE_CHAR value rationale In-Reply-To: <200001080553.OAA14530@zodiac.mech.utsunomiya-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, 8 Jan 2000, Kazutaka YOKOTA wrote: > >I agree with you - it is very strange for Czech users too (and maybe > >for almost all ISO-8859-* users) - default mouse settings override some > >important characters. Maybe we should ask Kazu if it is possible: > > > >1) Move SC_MOUSE_CHAR into sysctl tree as read-write value. > > Maybe we had better implement a new ioctl and use vidcontrol to set up > mouse char codes. > > sysctl is to tweak the kernel behavior. I would rather hesitate to > use it to customize device drivers, unless it has something to do with > kernel state/behavior and/or security; this is not the case with > SC_MOUSE_CHAR. > > >But Kazu have cleared off in December and I don't know where he is... > > I am here :-) > Kazu, before you made yourself visible, I went ahead and patched -stable's syscons to include the hw.syscons.sc_mouse_char sysctl variable. The patch is in PR kern/15996. I could change to to use the ioctl interface if you think that is is necessary. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 10:14:24 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id B8D1E151EF for ; Sat, 8 Jan 2000 10:14:21 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id NAA00255; Sat, 8 Jan 2000 13:14:19 -0500 (EST) Date: Sat, 8 Jan 2000 13:14:19 -0500 (EST) From: "Matthew N. Dodd" To: "Brian D. Moffet" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: multi-nics in FreeBSD 3.3 Release In-Reply-To: <200001081752.JAA06103@moffetimages.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, 8 Jan 2000, Brian D. Moffet wrote: > Of course some one knows this, but does FreeBSD support 2 NICS? I have > a 3com 3c905 and a 3com 3c509 in my box, but no matter how I adjust > the configuration file, I cannot get the 509 to be recognized. I > could put the Ne2000 clone in there instead, but the 509 is a better > card. Actually it isn't. Your problem is probably due to the 509 being in PnP mode, which 3.3 doesn't cope well with. You're better off using an NE2000 IMHO. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 10:21:23 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id 4C7B81576B for ; Sat, 8 Jan 2000 10:21:15 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id TAA23903; Sat, 8 Jan 2000 19:21:09 +0100 (CET) Message-ID: <20000108192108.A23533@foobar.franken.de> Date: Sat, 8 Jan 2000 19:21:08 +0100 From: Harold Gutch To: "Brian D. Moffet" , freebsd-hackers@FreeBSD.ORG Subject: Re: multi-nics in FreeBSD 3.3 Release References: <200001072146.NAA01836@apollo.backplane.com> <200001081752.JAA06103@moffetimages.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200001081752.JAA06103@moffetimages.com>; from Brian D. Moffet on Sat, Jan 08, 2000 at 09:52:19AM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG First of all, don't reply to other mails if you're not referring to them - it messes up the threads displayed by MUAs that support them. Second, this question would have been more appropriate for -questions. On Sat, Jan 08, 2000 at 09:52:19AM -0800, Brian D. Moffet wrote: > Of course some one knows this, but does FreeBSD support 2 NICS? Yes, it does. > I have a 3com 3c905 and a 3com 3c509 in my box, but no matter how I adjust the > configuration file, I cannot get the 509 to be recognized. I could put > the Ne2000 clone in there instead, but the 509 is a better card. You didn't attach your configfile or even just quote the relevant lines from it, so it's hard to guess what you're doing wrong. Just to make sure - you do have both "xl" and "ep" in your configfile? What errormessages do you get when booting ("dmesg")? > And as soon as I find out more information, I plan on modifying pciconf > to be able to parse more of the PCI BIOS information instead of just > the vendor and card IDs, unless someone has already done so. Where should > I send the changes? File a send-pr (see "man send-pr" or check out the handbook). bye, Harold -- Someone should do a study to find out how many human life spans have been lost waiting for NT to reboot. Ken Deboy on Dec 24 1999 in comp.unix.bsd.freebsd.misc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 10:21:28 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from lafontaine.cybercable.fr (lafontaine.cybercable.fr [212.198.0.202]) by hub.freebsd.org (Postfix) with SMTP id 0678815707 for ; Sat, 8 Jan 2000 10:21:14 -0800 (PST) (envelope-from herbelot@cybercable.fr) Received: (qmail 652764 invoked from network); 8 Jan 2000 18:21:08 -0000 Received: from d016.paris-30.cybercable.fr (HELO cybercable.fr) ([212.198.30.16]) (envelope-sender ) by lafontaine.cybercable.fr (qmail-ldap-1.03) with SMTP for ; 8 Jan 2000 18:21:08 -0000 Message-ID: <38778044.E4F844EF@cybercable.fr> Date: Sat, 08 Jan 2000 19:21:56 +0100 From: Thierry Herbelot X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Brian D. Moffet" Cc: freebsd-hackers@FreeBSD.ORG Subject: Re: multi-nics in FreeBSD 3.3 Release References: <200001081752.JAA06103@moffetimages.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of course FreeBSD supports more than one NIC : gw# ifconfig -a ed0: flags=8843 mtu 1500 inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 ether 52:54:4c:1b:90:1b ed1: flags=8843 mtu 1500 inet 212.198.30.16 netmask 0xffffff00 broadcast 212.198.30.255 ether 00:40:05:61:20:3e lp0: flags=8810 mtu 1500 lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 gw# To use more than one NIC, you've two things to do : 1/ enable the NIC in your kernel, that is most likely recompiling your kernel, as it is explained on : 2/ enable both NICs in the /etc/rc.conf file where wou will write something like : network_interfaces="ed0 ed1 lo0" ifconfig_ed0="inet 192.168.1.3 netmask 255.255.255.0" ifconfig_ed1="DHCP" (my second board uses DHCP, but you may set a fixed IP address) TfH PS : you should also read "Brian D. Moffet" wrote: > > Of course some one knows this, but does FreeBSD support 2 NICS? > I have a 3com 3c905 and a 3com 3c509 in my box, but no matter how I adjust the > configuration file, I cannot get the 509 to be recognized. I could put > the Ne2000 clone in there instead, but the 509 is a better card. > > Also, does the sio driver support PCI sio boards? The 3com / US Robotics > 56K faxmodem is an sio card with a modem on the other side, so that the > computer should be able to talk to it as a 16550. Though the IO address may > be a bit strange (in the 0x4000 or 0xa000 range). I guess this boils down > to 2 questions, IO space as well as PCI interrupts. > > And as soon as I find out more information, I plan on modifying pciconf > to be able to parse more of the PCI BIOS information instead of just > the vendor and card IDs, unless someone has already done so. Where should > I send the changes? > > Thanks > Brian Moffet > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 11:10:59 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id 446D914EE0; Sat, 8 Jan 2000 11:10:55 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas3-44-149.dial.proxad.net [212.27.44.149]) by postfix2.free.fr (Postfix) with ESMTP id E811374260; Sat, 8 Jan 2000 20:10:52 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id VAA01930; Sat, 8 Jan 2000 21:18:38 +0100 (CET) (envelope-from nsouch) Message-ID: <20000108211838.12590@breizh.free.fr> Date: Sat, 8 Jan 2000 21:18:38 +0100 From: Nicolas Souchu To: Maxim Sobolev Cc: hackers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS-UP newppbus for beta-testing References: <20000103004910.41467@armor.free.fr> <3870F784.2B1E8126@altavista.net> <20000104210015.63255@breizh.free.fr> <3873C990.70D294F7@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <3873C990.70D294F7@altavista.net>; from Maxim Sobolev on Thu, Jan 06, 2000 at 12:45:36AM +0200 X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 06, 2000 at 12:45:36AM +0200, Maxim Sobolev wrote: > >Nicolas Souchu wrote: > >> On Mon, Jan 03, 2000 at 09:24:52PM +0200, Maxim Sobolev wrote: >> > >> >Nicolas Souchu wrote: >> > >> >> Hi there! >> >> >> >> FOR ANYBODY THAT USES ZIP/PRINTER/PLIP ON THE PARALLEL PORT UNDER -current >> >> >> >> A major ppbus(4) release is available for beta-testing. >> > >> >Good work! Now plip, which has been broken for ages, works perfectly - no more >> >lockups, spontaneous reboots, panics, etc! To test it I even managed to get X >> >and NFS working over plip line, things which was impossible with oldppbus. >> >> Nice! But, sure the 'net' interrupt level mask (at the ppc0 declaration) >> in you MACHINE config file would have done the job. > >Unfortunately it is not a solution because net,tty and bio keywords went away from >config(8) long time ago... I've only received `syntax error' message. Ooops! A really bad thing. I did not notice it. They did not use to manage compatibility issues like this before?! > >-Maxim > > > -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 Sat Jan 8 14:37:26 2000 Delivered-To: freebsd-hackers@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id DB35314A25; Sat, 8 Jan 2000 14:37:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C95681CD44E; Sat, 8 Jan 2000 14:37:24 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 8 Jan 2000 14:37:24 -0800 (PST) From: Kris Kennaway To: Bjorn Cc: freebsd-hackers@freebsd.org Subject: Re: i82802 Random Number Generator Patch In-Reply-To: <38774917.10525B2D@privat.utfors.se> 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, 8 Jan 2000, Bjorn wrote: > Anyway, I've writting a small patch to enable the thermal noise random > number generator found in the i82802 (i82810). > > It breaks the /dev/random semantics slightly as the bitpool never run > out of fresh bits. Not really - /dev/random is just not guaranteed to always have bits available. This looks intriguing, though I can't test it since AFAIK I don't have one of those :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 15: 7:28 2000 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 B1EF014EE1 for ; Sat, 8 Jan 2000 15:07:24 -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 SAA16318 for hackers@freebsd.org; Sat, 8 Jan 2000 18:11:00 -0500 From: Bill Paul Message-Id: <200001082311.SAA16318@skynet.ctr.columbia.edu> Subject: Looking for testers with LinkSys USB100TX To: hackers@freebsd.org Date: Sat, 8 Jan 2000 18:10:59 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 1613 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Does anyone out there have a LinkSys USB100TX USB ethernet adapter and a -current installation up to date as of last night? I've been told that it didn't work, so I made some corrections last night to the if_aue driver which should fix it, but naturally the person who told me it didn't work decided to become unavailable for a week, which is *much* longer than I care to wait to find out if my fixes work or not. Actually, any -current box from the last couple weeks or so should do, as long as you sync /sys/dev/usb with the latest stuff from the tree. You can even test it without recompiling your kernel by doing the following: # cd /sys/modules/usb # make; make load # cd /sys/modules/aue # make; make load # usbd -f /dev/usb0 If everything works, you should see aue0 and ukphy0 attached, and of course you should be able to plug the thing into a network and exchange traffic. NOTE: do _NOT_ delay. Don't tell me "Sure, I have one; I'll try it in a month and get back to you." This should only take a few minutes. -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 Sat Jan 8 15:26:54 2000 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 BD9F514D22 for ; Sat, 8 Jan 2000 15:26:48 -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 e08NQTr94269; Sat, 8 Jan 2000 16:26:30 -0700 (MST) Message-Id: <200001082326.e08NQTr94269@orthanc.ab.ca> To: Kazutaka YOKOTA Cc: freebsd-hackers@freebsd.org Subject: Re: Reading kbd scancodes from userland In-reply-to: Your message of "Sat, 08 Jan 2000 14:25:31 +0900." <200001080525.OAA13803@zodiac.mech.utsunomiya-u.ac.jp> Date: Sat, 08 Jan 2000 16:26:29 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Kazutaka" == Kazutaka YOKOTA writes: >> Failing that, has anyone figured out a keyboard mapping for an >> Inspiron 7000 that puts the left ALT key back where it belongs? >> (The reason for the first request is to try to determine what >> effect the left ALT key actually has. On this laptop, the >> "windows" key does what left ALT normally does, making life >> miserable when running a non-win98 external keyboard.) Kazutaka> This is pretty wiered. You mean the REAL left ALT key Kazutaka> doesn't work on this notebook and the external keyboard? The left ALT does *something*, I just don't know what (yet). To get the standard left ALT behaviour I have to use the "windows" key. Kazutaka> Can you veryfy that the same problem exists in other OS, Kazutaka> such as W*ndows, environments? If so, I suspect there Kazutaka> is a bug in the keyboard controller firmare, which Kazutaka> traslates keyboard signal into scan codes. Under Windows the left ALT and "windows" keys work as expected. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 17:16: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from moffetimages.com (alar.scruz.predictive.com [207.251.1.130]) by hub.freebsd.org (Postfix) with ESMTP id 61D5114E30 for ; Sat, 8 Jan 2000 17:16:03 -0800 (PST) (envelope-from brianm@moffetimages.com) Received: (from brianm@localhost) by moffetimages.com (8.9.3/8.9.3) id RAA00337; Sat, 8 Jan 2000 17:15:31 -0800 (PST) (envelope-from brianm) Date: Sat, 8 Jan 2000 17:15:31 -0800 (PST) From: "Brian D. Moffet" Message-Id: <200001090115.RAA00337@moffetimages.com> To: winter@jurai.net Subject: Re: multi-nics in FreeBSD 3.3 Release Cc: freebsd-hackers@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks for all the help, turning on en instead of di in kernel.conf solved the problem. Brian Moffet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 18:23:54 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from mail-ob.kamp.net (mail-ob.kamp.net [195.62.97.26]) by hub.freebsd.org (Postfix) with ESMTP id 80ABF14EB3 for ; Sat, 8 Jan 2000 18:23:51 -0800 (PST) (envelope-from Joachim.Jaeckel@d.kamp.net) Received: from d.kamp.net (port-10.d.kamp.de [195.62.120.202]) by mail-ob.kamp.net (8.9.3/8.9.3) with ESMTP id DAA17997 for ; Sun, 9 Jan 2000 03:23:50 +0100 Message-ID: <3877F409.49088485@d.kamp.net> Date: Sun, 09 Jan 2000 03:35:53 +0100 From: "Joachim Jäckel" X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.3-19991111-STABLE i386) MIME-Version: 1.0 To: "freebsd-hackers@freebsd.org" Subject: How to write a device-driver? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. This is the first time that I try to do a hardware related programming, (if I ever will start and finish it...) I'm currently have no knowledge of that kind of programming, but I'd like to learn! If I'd like to write a device driver for a given card, could you tell me, where I could read something about it (how to implement the interface to the kernel, where to place and name the files and so on). I read something about a device-driver tutorial under www.freebsd.org/tutorials/ddwg, but it seems, that this page isn't there anymore. And maybe you could give me a tip, whats the best point to start, a linux-device-driver, something like a specification of the different chips on the card (it seems, that there is no documentation of the card from the manufacturer), or could I listen on the data, which is posted between the system and the driver under windows? whatever... Thanks in advance for any help or answer, -- Joachim.Jaeckel@d.kamp.net -- http://home.kamp.net/home/joachim.jaeckel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message From owner-freebsd-hackers Sat Jan 8 20: 1: 5 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 592C314FEF for ; Sat, 8 Jan 2000 20:01:02 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:Ny1fb8148157vKJdZfJl6Jajztt3yncA@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id NAA17004; Sun, 9 Jan 2000 13:00:51 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id NAA07901; Sun, 9 Jan 2000 13:06:16 +0900 (JST) Message-Id: <200001090406.NAA07901@zodiac.mech.utsunomiya-u.ac.jp> To: Lyndon Nerenberg Cc: freebsd-hackers@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Reading kbd scancodes from userland In-reply-to: Your message of "Sat, 08 Jan 2000 16:26:29 MST." <200001082326.e08NQTr94269@orthanc.ab.ca> References: <200001082326.e08NQTr94269@orthanc.ab.ca> Date: Sun, 09 Jan 2000 13:06:15 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kazutaka> This is pretty wiered. You mean the REAL left ALT key > Kazutaka> doesn't work on this notebook and the external keyboard? > >The left ALT does *something*, I just don't know what (yet). To get >the standard left ALT behaviour I have to use the "windows" key. In what environment do you have the problem? If you have the problem in the X session, it must be the X server's key mapping which is somewhat wrong. The keyboard driver just passes raw scan codes to the X server and there can be little chance for the keyboard driver to screw the scan codes for the left ALT and W*ndows keys, while the X server is running. If you have the problem in the text console, tell me which keymap file in /usr/share/syscons/keymaps you are using, or dump the keymap by running: kbdcontrol -d in the text console and send it to me for diagnosis. On more thing. You mention the "standard left ALT behavior". What do you exactly mean by that? Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message