From owner-freebsd-hackers Sun Dec 29 00:12:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA18969 for hackers-outgoing; Sun, 29 Dec 1996 00:12:02 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA18948 for ; Sun, 29 Dec 1996 00:11:58 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id AAA28701 for ; Sun, 29 Dec 1996 00:12:31 -0800 (PST) Received: (qmail 1916 invoked by uid 110); 29 Dec 1996 08:11:20 -0000 Message-ID: <19961229081120.1915.qmail@suburbia.net> Subject: Re: vi edit mode unstable -termcap ? In-Reply-To: from David Nugent at "Dec 29, 96 06:37:55 pm" To: davidn@sdev.usn.blaze.net.au (David Nugent) Date: Sun, 29 Dec 1996 19:11:20 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > For example if I hit the down-arrow key a few times, after about > > 3 or 4 arrow-down, it will begin to put 'B' into the editor. > > > Yes, this is really VERY annoying. I have the same problem with > any network connections, even across 10mb ethernet, which is just > plain crazy. The workaround (and it IS only a workaround!) is to > put set escapetime=10 into ~/.exrc. > > Regards, > > David Nugent - Unique Computing Pty Ltd - Melbourne, Australia > Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet > davidn@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/ > The real solution is learn to be a better nethack player; to love and cherish the escapless hijk. -Julian Assange (proff@suburbia.net) From owner-freebsd-hackers Sun Dec 29 00:13:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA19067 for hackers-outgoing; Sun, 29 Dec 1996 00:13:26 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA19058 for ; Sun, 29 Dec 1996 00:13:23 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id AAA28721 for ; Sun, 29 Dec 1996 00:13:56 -0800 (PST) Received: (qmail 1940 invoked by uid 110); 29 Dec 1996 08:12:43 -0000 Message-ID: <19961229081242.1939.qmail@suburbia.net> Subject: Re: vi edit mode unstable -termcap ? In-Reply-To: from David Nugent at "Dec 29, 96 06:37:55 pm" To: davidn@sdev.usn.blaze.net.au (David Nugent) Date: Sun, 29 Dec 1996 19:12:42 +1100 (EST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Could the maintainer of nvi PLEASE use a more reasonable default > value for escapetime? This is problematic even editing in an xterm > locally on a system running under a reasonable load. Speaking of things vi. vim 4.5 is in ports, and blows nvi away. From owner-freebsd-hackers Sun Dec 29 00:29:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA19610 for hackers-outgoing; Sun, 29 Dec 1996 00:29:55 -0800 (PST) Received: from cheops.anu.edu.au (avalon@cheops.anu.edu.au [150.203.76.24]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA19601 for ; Sun, 29 Dec 1996 00:29:46 -0800 (PST) Message-Id: <199612290829.AAA19601@freefall.freebsd.org> Received: by cheops.anu.edu.au (1.37.109.16/16.2) id AA296598003; Sun, 29 Dec 1996 19:26:43 +1100 From: Darren Reed Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters To: terry@lambert.org (Terry Lambert) Date: Sun, 29 Dec 1996 19:26:43 +1100 (EDT) Cc: julian@whistle.com, luigi@labinfo.iet.unipi.it, proff@iq.org, danny@panda.hilink.com.au, hackers@freebsd.org In-Reply-To: <199612272306.QAA25429@phaeton.artisoft.com> from "Terry Lambert" at Dec 27, 96 04:06:08 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In some mail from Terry Lambert, sie said: [...] > This is what I've been calling "layering problems". It is definitely > a goal of mine to allow a module to be debugged in user space with a > source level debugger. Making code that compiles in the kernel also compile for user programs is tricky if you only want _one_ routine for both. I try to reuse as much code as possible for IP Filter when compiling the test program using .c's that also go in to the kernel-mode stuff. Darren From owner-freebsd-hackers Sun Dec 29 00:53:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA20179 for hackers-outgoing; Sun, 29 Dec 1996 00:53:02 -0800 (PST) Received: from news1.gtn.com (news1.gtn.com [192.109.159.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA20174; Sun, 29 Dec 1996 00:52:56 -0800 (PST) Received: (from uucp@localhost) by news1.gtn.com (8.7.2/8.7.2) with UUCP id JAA07845; Sun, 29 Dec 1996 09:46:47 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.8.4/8.8.2) id JAA01930; Sun, 29 Dec 1996 09:34:52 +0100 (MET) Message-ID: Date: Sun, 29 Dec 1996 09:34:52 +0100 From: andreas@klemm.gtn.com (Andreas Klemm) To: se@FreeBSD.org (Stefan Esser) Cc: hackers@FreeBSD.org Subject: Re: option FAILSAFE in GENERIC and LINT a bit misleading ? References: X-Mailer: Mutt 0.54-PL15 Mime-Version: 1.0 In-Reply-To: ; from "Stefan Esser" on Dec 29, 1996 00:11:18 +0100 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Stefan Esser writes: > On Dec 28, andreas@klemm.gtn.com (Andreas Klemm) wrote: > > I'd suggest renaming the option to NCR_FAILSAFE and to really > > document in the kernel profile, what it does within the NCR > > driver. > > Well, and I'd suggest to NOT rename it, and to hope > it will find further use in other parts of the kernel. Ok, I hope, this option will be heavily used in the furure ;-) -- andreas@klemm.gtn.com /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ Support Unix -- andreas.klemm@wup.de pgp p-key http://www-swiss.ai.mit.edu/~bal/pks-toplev.html >>> powered by <<< ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz >>> FreeBSD <<< From owner-freebsd-hackers Sun Dec 29 04:54:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA29288 for hackers-outgoing; Sun, 29 Dec 1996 04:54:19 -0800 (PST) Received: from bunyip.cc.uq.oz.au (daemon@bunyip.cc.uq.oz.au [130.102.2.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id EAA29283 for ; Sun, 29 Dec 1996 04:54:17 -0800 (PST) Received: (from daemon@localhost) by bunyip.cc.uq.oz.au (8.8.4/8.8.3) id WAA18697 for freebsd-hackers@freebsd.org; Sun, 29 Dec 1996 22:54:14 +1000 Received: by ogre.devetir.qld.gov.au (8.7.5/DEVETIR-E0.3a) id VAA20669; Sun, 29 Dec 1996 21:08:54 +1000 (EST) Date: Sun, 29 Dec 1996 21:08:54 +1000 (EST) From: Stephen McKay Message-Id: <199612291108.VAA20669@ogre.devetir.qld.gov.au> To: freebsd-hackers@freebsd.org cc: syssgm@devetir.qld.gov.au Subject: Re: vi edit mode unstable -termcap ? X-Newsreader: NN version 6.5.0 #1 (NOV) Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk davidn@sdev.usn.blaze.net.au (David Nugent) wrote: >Kim Culhan writes: >> For example if I hit the down-arrow key a few times, after about >> 3 or 4 arrow-down, it will begin to put 'B' into the editor. > >Yes, this is really VERY annoying. I have the same problem with >any network connections, even across 10mb ethernet, which is just >plain crazy. The workaround (and it IS only a workaround!) is to >put set escapetime=10 into ~/.exrc. > >Could the maintainer of nvi PLEASE use a more reasonable default >value for escapetime? This is problematic even editing in an xterm >locally on a system running under a reasonable load. I've had no problems with escapetime=5, but I agree the default should be the good old 1 second (escapetime=10), and let optimists set escapetime=1. I've also had no problems with hjkl, but the rest of you vi die-hards would already know this. :-) >This started with the recent vendor import of the new version >of nvi. "split" disappeared too. :-( Use ":E" instead. ":split" could be made an alias of ":E" I suppose. Has anyone looked for a more recent nvi alpha to see if Keith has already done these things? Stephen. From owner-freebsd-hackers Sun Dec 29 10:58:12 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA07814 for hackers-outgoing; Sun, 29 Dec 1996 10:58:12 -0800 (PST) Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA07809 for ; Sun, 29 Dec 1996 10:58:08 -0800 (PST) Received: from sierra.zyzzyva.com (LOCALHOST [127.0.0.1]) by sierra.zyzzyva.com (8.8.4/8.8.2) with ESMTP id NAA18516 for ; Sun, 29 Dec 1996 13:00:05 -0600 (CST) Message-Id: <199612291900.NAA18516@sierra.zyzzyva.com> To: freebsd-hackers@freebsd.org Subject: DEVFS strangeness X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Dec 1996 13:00:05 -0600 From: Randy Terbush Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Been attempting to see how well the DEVFS works. Seems that sound devices are being created as follows. crw-rw---- 1 root games 30, 68 Dec 19 08:49 /dev/audio4 crw-rw---- 1 root games 30, 67 Dec 19 08:49 /dev/dsp4 crw-rw---- 1 root games 30, 69 Dec 19 08:49 /dev/dspW4 crw-rw---- 1 root games 30, 66 Dec 19 08:49 /dev/midi4 crw-rw---- 1 root games 30, 64 Dec 19 08:49 /dev/mixer4 crw-rw---- 1 root games 30, 72 Dec 19 08:49 /dev/music4 crw-rw---- 1 root games 30, 73 Dec 19 08:49 /dev/pss4 crw-rw---- 1 root games 30, 65 Dec 19 08:49 /dev/sequencer4 I have the following in my kernel config: # Sounds support controller snd0 device gus0 at isa? port 0x220 irq 12 drq 1 vector gusintr #> cat /usr/local/lib/sound/sounds/clink.au > /dev/audio4 su: /dev/audio4: Device not configured Is this a known deficiency of the DEVFS? From owner-freebsd-hackers Sun Dec 29 15:46:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA18112 for hackers-outgoing; Sun, 29 Dec 1996 15:46:42 -0800 (PST) Received: from sierra.zyzzyva.com (ppp0.zyzzyva.com [198.183.2.50]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA18094 for ; Sun, 29 Dec 1996 15:46:30 -0800 (PST) Received: from sierra.zyzzyva.com (LOCALHOST [127.0.0.1]) by sierra.zyzzyva.com (8.8.4/8.8.2) with ESMTP id RAA23734 for ; Sun, 29 Dec 1996 17:48:28 -0600 (CST) Message-Id: <199612292348.RAA23734@sierra.zyzzyva.com> To: hackers@freebsd.org Subject: LKM and MOD_DEV changes in 2.2 X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Dec 1996 17:48:27 -0600 From: Randy Terbush Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm taking a stab at porting Darren Reed's ipfilter to 2.2 and have run into a snag with some changed macros in the LKM stuff. Could someone a bit more familiar with LKM explain the differences? ------------------------------------------------------------------------ >From 2.1.6.1: /usr/include/sys/lkm.h #define MOD_DEV(name,devtype,devslot,devp) \ static struct lkm_dev _module = { \ LM_DEV, \ LKM_VERSION, \ name, \ devslot, \ devtype, \ (void *)devp \ }; ------------------------------------------------------------------------ >From 2.2: #define MOD_DEV(name,devtype,devslot,devp) \ MOD_DECL(name); \ static struct lkm_dev name ## _module = { \ LM_DEV, \ LKM_VERSION, \ #name ## "_mod", \ devslot, \ devtype, \ (void *)devp \ } #define MOD_DECL(name) \ static int name ## _load __P((struct lkm_table *lkmtp, int cmd)); \ static int name ## _unload __P((struct lkm_table *lkmtp, int cmd)); \ int name ## _mod __P((struct lkm_table *lkmtp, int cmd, int ver)) \ ------------------------------------------------------------------------ It's use in ipfilter: line 122: MOD_DEV(IPL_VERSION, LM_DT_CHAR, -1, &ipldevsw); Compiler's response: gcc -I. -I../.. -DIPFILTER_LKM -DIPFILTER_LOG -D`uname -m` -D__`uname -m`__ -DINET -DKERNEL -D_KERNEL -I/usr/include -I/sys -I/sys/sys -I/sys/arch -DIPL_NAME=\"/dev/ipl\" -c ../../mln_ipl.c -o ml_ipl.o ../../mln_ipl.c:122: parse error before string constant ../../mln_ipl.c:122: parse error before string constant ../../mln_ipl.c:125: conflicting types for `cdevsw' /usr/include/sys/conf.h:122: previous declaration of `cdevsw' ../../mln_ipl.c: In function `xxxinit': ../../mln_ipl.c:241: `_module' undeclared (first use this function) ../../mln_ipl.c:241: (Each undeclared identifier is reported only once ../../mln_ipl.c:241: for each function it appears in.) *** Error code 1 From owner-freebsd-hackers Sun Dec 29 16:05:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA19877 for hackers-outgoing; Sun, 29 Dec 1996 16:05:18 -0800 (PST) Received: from bios-nt.sunbeach.net (SUNBEACH.NET [205.214.199.134]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id QAA19866 for ; Sun, 29 Dec 1996 16:05:06 -0800 (PST) Received: from bios-nt.sunbeach.net by bios-nt.sunbeach.net (NTMail 3.02.11) with ESMTP id ca084658 for ; Sun, 29 Dec 1996 20:03:58 -0400 Date: Sun, 29 Dec 1996 20:05:35 -0400 (AST) From: "Sean Batson (Sunbeach)" X-Sender: seanb012@bsdi.net To: freebsd-hackers@freebsd.org Subject: IPCS Utility Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On executing the IPCS command the results didn't display any active semospheres. Would this be internal to the OS or the IPCS utility. What's the latest with FreeBSD equivalent of AIX's SMIT interface? Give me some specs and I think I can come up with an equivalent. (roughly 6 to 9 months). Sean Batson. From owner-freebsd-hackers Sun Dec 29 17:00:50 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA22855 for hackers-outgoing; Sun, 29 Dec 1996 17:00:50 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA22847 for ; Sun, 29 Dec 1996 17:00:46 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id RAA27883; Sun, 29 Dec 1996 17:00:21 -0800 (PST) To: "Sean Batson (Sunbeach)" cc: freebsd-hackers@freebsd.org Subject: Re: IPCS Utility In-reply-to: Your message of "Sun, 29 Dec 1996 20:05:35 -0400." Date: Sun, 29 Dec 1996 17:00:21 -0800 Message-ID: <27879.851907621@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > What's the latest with FreeBSD equivalent of AIX's SMIT interface? > Give me some specs and I think I can come up with an equivalent. > (roughly 6 to 9 months). The problem is that this is a multi-layered problem. You need to write the CLI utilities which "back" your SMIT-like tool, you need to write some GUI tools better than libdialog (which stinks) for presenting the interfaces and, finally, you need to decide which goals you're going to attack first. We've talked about doing this for 2 years now, and we always get bogged down in the process of providing the specs you request here (or we get an initial set of objectives laid down, then nobody finds the time to write anything and no progress is made). Mike, anything from that guy who was threatening to do at least the GUI components? Jordan From owner-freebsd-hackers Sun Dec 29 17:06:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA23134 for hackers-outgoing; Sun, 29 Dec 1996 17:06:57 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA23128 for ; Sun, 29 Dec 1996 17:06:51 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA04664; Mon, 30 Dec 1996 11:36:28 +1030 (CST) From: Michael Smith Message-Id: <199612300106.LAA04664@genesis.atrad.adelaide.edu.au> Subject: Re: IPCS Utility In-Reply-To: from Sean Batson at "Dec 29, 96 08:05:35 pm" To: seanb012@sunbeach.net (Sean Batson) Date: Mon, 30 Dec 1996 11:36:27 +1030 (CST) Cc: freebsd-hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sean Batson stands accused of saying: > On executing the IPCS command the results didn't display any > active semospheres. Would this be internal to the OS or the > IPCS utility. If you don't have semaphore support compiled in, there won't be any. FreeBSD doesn't use them internally; it just offers them as a service to applications. Here's a quiet system : cain:~>ipcs Message Queues: T ID KEY MODE OWNER GROUP Shared Memory: T ID KEY MODE OWNER GROUP m 458752 0 --rwarwarwa amurphy users m 196609 0 --rwarwarwa amurphy users m 262148 0 --rwarwarwa msmith users Semaphores: T ID KEY MODE OWNER GROUP > What's the latest with FreeBSD equivalent of AIX's SMIT interface? > Give me some specs and I think I can come up with an equivalent. > (roughly 6 to 9 months). Development on this is currently underway; if you're Tcl literate (or are willing to learn & want to take part regardless) then we'd love to have you aboard. I should pester our mailmaster for a list for discussions of this; it's getting difficult remembering everyone that's interested 8) > Sean Batson. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Dec 29 17:47:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA24487 for hackers-outgoing; Sun, 29 Dec 1996 17:47:06 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA24481 for ; Sun, 29 Dec 1996 17:47:03 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id MAA04910; Mon, 30 Dec 1996 12:16:29 +1030 (CST) From: Michael Smith Message-Id: <199612300146.MAA04910@genesis.atrad.adelaide.edu.au> Subject: Re: IPCS Utility In-Reply-To: <27879.851907621@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 29, 96 05:00:21 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 30 Dec 1996 12:16:28 +1030 (CST) Cc: seanb012@sunbeach.net, freebsd-hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > We've talked about doing this for 2 years now, and we always get > bogged down in the process of providing the specs you request here (or > we get an initial set of objectives laid down, then nobody finds the > time to write anything and no progress is made). > > Mike, anything from that guy who was threatening to do at least the > GUI components? Nothing after what was cc'd to you. That was Jan Knepper IIRC; I guess we should rattle his cage again 8) We need a list for this; there's a pile of people that pop up, agree to lurk and think, and then get cut out of the cycle. I can't keep track of them all 8( > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Dec 29 18:18:46 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA25486 for hackers-outgoing; Sun, 29 Dec 1996 18:18:46 -0800 (PST) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA25481 for ; Sun, 29 Dec 1996 18:18:43 -0800 (PST) Received: from mongoose.bostic.com by agora.rdrop.com with smtp (Smail3.1.29.1 #17) id m0veXI8-0008uPC; Sun, 29 Dec 96 18:17 PST Received: (from bostic@localhost) by mongoose.bostic.com (8.7.4/8.7.3) id VAA23937; Sun, 29 Dec 1996 21:15:39 -0500 (EST) Date: Sun, 29 Dec 1996 21:15:39 -0500 (EST) From: Keith Bostic Message-Id: <199612300215.VAA23937@mongoose.bostic.com> To: davidn@sdev.usn.blaze.net.au Subject: Re: David Nugent: Re: vi edit mode unstable -termcap ? Cc: hackers@freebsd.org, jkh@time.cdrom.com, kimc@w8hd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > From: davidn@sdev.usn.blaze.net.au (David Nugent) > > Kim Culhan writes: >> I have had this problem here for some time, searched for the cause today >> and cannot find it. >> >> On two -current machines here, when using an xterm and telnet to the other >> machine, when using the arrow-keys to move around the screen, vi will >> switch to the insert mode and deposit characters into the editor. >> >> For example if I hit the down-arrow key a few times, after about >> 3 or 4 arrow-down, it will begin to put 'B' into the editor. > > Yes, this is really VERY annoying. I have the same problem with > any network connections, even across 10mb ethernet, which is just > plain crazy. The workaround (and it IS only a workaround!) is to > put set escapetime=10 into ~/.exrc. Actually, it's not a workaround, that's exactly what it's intended for! ;-} > Could the maintainer of nvi PLEASE use a more reasonable default > value for escapetime? This is problematic even editing in an xterm > locally on a system running under a reasonable load. I'm happy to make the change, I do very little remote editing, so I just don't see the problem. What's a good value to use? >> On a third machine running 2.2-current from 9-15 I can telnet to it >> from either of the other machines and it will not do this. > > This started with the recent vendor import of the new version > of nvi. "split" disappeared too. :-( Actually, split was replaced. You can now capitalize most (all?) of the standard operations and they'll happen in a split screen. So, E[dit], T[ag], N[ext], P[rev] etc. all work in a split screen. (It's all documented in the reference guide, too, if you want further information.) --keith From owner-freebsd-hackers Sun Dec 29 18:45:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA26452 for hackers-outgoing; Sun, 29 Dec 1996 18:45:03 -0800 (PST) Received: from sunbeam.csusb.edu (sunbeam.csusb.edu [139.182.10.13]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA26444 for ; Sun, 29 Dec 1996 18:45:00 -0800 (PST) Received: (from rmallory@localhost) by sunbeam.csusb.edu (8.8.4/8.7.3) id SAA01714; Sun, 29 Dec 1996 18:44:56 -0800 (PST) From: Rob Mallory Message-Id: <199612300244.SAA01714@sunbeam.csusb.edu> Subject: Re: 3com 3c589b pcmcia support? To: nate@mt.sri.com (Nate Williams) Date: Sun, 29 Dec 1996 18:44:56 -0800 (PST) Cc: hackers@freebsd.org In-Reply-To: <199612222003.NAA01294@rocky.mt.sri.com> from "Nate Williams" at Dec 22, 96 01:03:50 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > >> I have a 3c589c-TP, and the default GENERIC kernel finds it, ifconfigs > > >> it up, and appears to work (I get a link light on the hub at that > > >> point). > > > > > Actually, it depends on which model and what the built-in settings are. > My two cards behave exactly opposite of one another with the link flags. > > Nate > 'Got mine working first with the zp driver, then later the PAO-ep driver. The Megahertz-xj2288 works preaty good also, but only with the PAO 961215 release merged into -current.. (well, I did not try PAO with 2.1.6 first..) works Great!! so my next question[s] are: will the PAO mods be brought into the -current branch? or will I have to keep merging the PAO releases after I sup..? Is there a nomads mailing list? -Rob From owner-freebsd-hackers Sun Dec 29 18:54:04 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA26900 for hackers-outgoing; Sun, 29 Dec 1996 18:54:04 -0800 (PST) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA26895 for ; Sun, 29 Dec 1996 18:54:01 -0800 (PST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id TAA22840; Sun, 29 Dec 1996 19:53:56 -0700 (MST) Date: Sun, 29 Dec 1996 19:53:56 -0700 (MST) Message-Id: <199612300253.TAA22840@rocky.mt.sri.com> From: Nate Williams To: Rob Mallory Cc: nate@mt.sri.com (Nate Williams), hackers@freebsd.org Subject: Re: 3com 3c589b pcmcia support? In-Reply-To: <199612300244.SAA01714@sunbeam.csusb.edu> References: <199612222003.NAA01294@rocky.mt.sri.com> <199612300244.SAA01714@sunbeam.csusb.edu> Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 'Got mine working first with the zp driver, then later the PAO-ep driver. > The Megahertz-xj2288 works preaty good also, but only with the PAO 961215 > release merged into -current.. (well, I did not try PAO with 2.1.6 first..) > works Great!! I have the Megahertz-xj288 working with -current fine. I needed to build a new entry in /etc/pccard.conf for it, but I didn't need any of the PAO mods. > so my next question[s] are: will the PAO mods be brought into > the -current branch? When I or another committer finds time. The code has bugs in it, and I'm not bringing it in lock-stock-barrel until *after* I know what exactly the code does. The problem is that there is alot of good code in it, but by the time I start separating the chaff from the wheat I start to get discouraged or run out of time. > Is there a nomads mailing list? Apperently, but it's all in Japanese. There is a 'freebsd-mobile' list, but it's pretty low key. Nate From owner-freebsd-hackers Sun Dec 29 18:54:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA26958 for hackers-outgoing; Sun, 29 Dec 1996 18:54:21 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA26945 for ; Sun, 29 Dec 1996 18:54:18 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id SAA28336; Sun, 29 Dec 1996 18:52:55 -0800 (PST) To: Michael Smith cc: seanb012@sunbeach.net, freebsd-hackers@FreeBSD.org Subject: Re: IPCS Utility In-reply-to: Your message of "Mon, 30 Dec 1996 12:16:28 +1030." <199612300146.MAA04910@genesis.atrad.adelaide.edu.au> Date: Sun, 29 Dec 1996 18:52:54 -0800 Message-ID: <28333.851914374@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > We need a list for this; there's a pile of people that pop up, agree to > lurk and think, and then get cut out of the cycle. I can't keep track of > them all 8( We used the have an alias, install-geeks@freebsd.org, which was used for this. What would you have the list called? All we need to do is agree on a name and then ask our postmaster to do the deed. :) Jordan From owner-freebsd-hackers Sun Dec 29 19:10:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA28102 for hackers-outgoing; Sun, 29 Dec 1996 19:10:13 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA28085 for ; Sun, 29 Dec 1996 19:10:06 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id NAA05238; Mon, 30 Dec 1996 13:37:53 +1030 (CST) From: Michael Smith Message-Id: <199612300307.NAA05238@genesis.atrad.adelaide.edu.au> Subject: Re: IPCS Utility In-Reply-To: <28333.851914374@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 29, 96 06:52:54 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 30 Dec 1996 13:37:52 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, seanb012@sunbeach.net, freebsd-hackers@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > We used the have an alias, install-geeks@freebsd.org, which was used > for this. What would you have the list called? All we need to do is > agree on a name and then ask our postmaster to do the deed. :) Hmm. "config-management" would probably do it. Sufficiently unambiguous that we won't get _too_ many stupid questions, and if people want to talk about Empac's product or whatever I don't think we'd be too upset. > Jordan (NB. I'm looking for a good retcon of "POG" to accompany PIB before I go loudly public with it, for all the Aardman fans out there. A bitmap for the icon would be good to, although I expect I can find one on the web somewhere...) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Sun Dec 29 19:23:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA28649 for hackers-outgoing; Sun, 29 Dec 1996 19:23:10 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA28635; Sun, 29 Dec 1996 19:22:31 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199612300322.TAA28635@freefall.freebsd.org> Subject: Re: IPCS Utility To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Sun, 29 Dec 1996 19:22:31 -0800 (PST) Cc: msmith@atrad.adelaide.edu.au, seanb012@sunbeach.net, freebsd-hackers@FreeBSD.org In-Reply-To: <28333.851914374@time.cdrom.com> from "Jordan K. Hubbard" at Dec 29, 96 06:52:54 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > > We need a list for this; there's a pile of people that pop up, agree to > > lurk and think, and then get cut out of the cycle. I can't keep track of > > them all 8( > > We used the have an alias, install-geeks@freebsd.org, which was used > for this. What would you have the list called? All we need to do is > agree on a name and then ask our postmaster to do the deed. :) > install-geeks is still there. we could call a new majordomo list ...... let me know and i will create the list within 24 hours (depends on my having secure access to freefall-- dont have that during the day, only at night) here's the list for install-geeks at this present install-geeks: install-hackers install-hackers: jkh, phk, ache, jeffh@cybernetics.net, cg@www.ar chimedia.khs-linz.ac.at, bugs@ns1.win.net, obrien@cs.ucdavis.edu, imp@village.or g, wmbfmk@urc.tue.nl jmb From owner-freebsd-hackers Sun Dec 29 19:39:14 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA29149 for hackers-outgoing; Sun, 29 Dec 1996 19:39:14 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA29144 for ; Sun, 29 Dec 1996 19:39:12 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id TAA13954; Sun, 29 Dec 1996 19:37:45 -0800 (PST) To: "Jonathan M. Bresler" cc: msmith@atrad.adelaide.edu.au, seanb012@sunbeach.net, freebsd-hackers@FreeBSD.org Subject: Re: IPCS Utility In-reply-to: Your message of "Sun, 29 Dec 1996 19:22:31 PST." <199612300322.TAA28635@freefall.freebsd.org> Date: Sun, 29 Dec 1996 19:37:44 -0800 Message-ID: <13949.851917064@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > we could call a new majordomo list ...... > let me know and i will create the list within 24 hours Please! Though can we call it config@freebsd.org because config-management, as descriptive as that is, will wear my fingers off. ;-) The "long name" would, of course, be freebsd-config. Jordan From owner-freebsd-hackers Mon Dec 30 00:32:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id AAA07407 for hackers-outgoing; Mon, 30 Dec 1996 00:32:26 -0800 (PST) Received: from turtle.ee.ncku.edu.tw (root@turtle.ee.ncku.edu.tw [140.116.72.72]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id AAA07390 for ; Mon, 30 Dec 1996 00:32:22 -0800 (PST) Received: (from antony@localhost) by turtle.ee.ncku.edu.tw (8.7.5/8.7.3) id QAA15779 for hackers@freefall.freebsd.org; Mon, 30 Dec 1996 16:47:15 +0800 (CST) Date: Mon, 30 Dec 1996 16:47:15 +0800 (CST) From: Antony Message-Id: <199612300847.QAA15779@turtle.ee.ncku.edu.tw> To: hackers@freefall.freebsd.org Subject: What is Fatal trap 12 ?? Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I enabled KTRACE, DDB, DIAGNOSTIC , and modified some source file of /sys/netinent/ip_input.c, and in some place, it shows Dec 30 16:01:34 hawk /kernel: Fatal trap 12: page fault while in kernel mode Dec 30 16:01:34 hawk /kernel: fault virtual address = 0xf0a1a004 Dec 30 16:01:34 hawk /kernel: fault code = supervisor read, page not present Dec 30 16:01:34 hawk /kernel: instruction pointer = 0x8:0xf0a106b4 Dec 30 16:01:34 hawk /kernel: code segment = base 0x0, limit 0xfff f, type 0x1b Dec 30 16:01:34 hawk /kernel: = DPL 0, pres 1, def32 1, gran Dec 30 16:01:34 hawk /kernel: processor eflags = interrupt enabled, resume, IO L = 0 Dec 30 16:01:34 hawk /kernel: current process = Idle Dec 30 16:01:34 hawk /kernel: interrupt mask = Dec 30 16:01:34 hawk /kernel: Dec 30 16:01:35 hawk /kernel: Any idea about what the hell it is ? Antony From owner-freebsd-hackers Mon Dec 30 01:03:13 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA08644 for hackers-outgoing; Mon, 30 Dec 1996 01:03:13 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA08624 for ; Mon, 30 Dec 1996 01:03:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id BAA00373; Mon, 30 Dec 1996 01:02:16 -0800 (PST) Message-Id: <199612300902.BAA00373@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: Antony cc: hackers@freefall.freebsd.org Subject: Re: What is Fatal trap 12 ?? In-reply-to: Your message of "Mon, 30 Dec 1996 16:47:15 +0800." <199612300847.QAA15779@turtle.ee.ncku.edu.tw> From: David Greenman Reply-To: dg@root.com Date: Mon, 30 Dec 1996 01:02:16 -0800 Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > I enabled KTRACE, DDB, DIAGNOSTIC , and modified some source > file of /sys/netinent/ip_input.c, and in some place, it shows > >Dec 30 16:01:34 hawk /kernel: Fatal trap 12: page fault while in kernel mode >Dec 30 16:01:34 hawk /kernel: fault virtual address = 0xf0a1a004 >Dec 30 16:01:34 hawk /kernel: fault code = supervisor read, page >not present >Dec 30 16:01:34 hawk /kernel: instruction pointer = 0x8:0xf0a106b4 >Dec 30 16:01:34 hawk /kernel: code segment = base 0x0, limit 0xfff >f, type 0x1b >Dec 30 16:01:34 hawk /kernel: = DPL 0, pres 1, def32 1, gran >Dec 30 16:01:34 hawk /kernel: processor eflags = interrupt enabled, resume, IO >L = 0 >Dec 30 16:01:34 hawk /kernel: current process = Idle >Dec 30 16:01:34 hawk /kernel: interrupt mask = >Dec 30 16:01:34 hawk /kernel: >Dec 30 16:01:35 hawk /kernel: > > Any idea about what the hell it is ? It means that you are referencing an unmapped section of memory in the kernel, causing a page fault (trap 12). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hackers Mon Dec 30 01:06:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA08956 for hackers-outgoing; Mon, 30 Dec 1996 01:06:19 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA08941 for ; Mon, 30 Dec 1996 01:06:16 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id TAA06380; Mon, 30 Dec 1996 19:35:41 +1030 (CST) From: Michael Smith Message-Id: <199612300905.TAA06380@genesis.atrad.adelaide.edu.au> Subject: Re: What is Fatal trap 12 ?? In-Reply-To: <199612300847.QAA15779@turtle.ee.ncku.edu.tw> from Antony at "Dec 30, 96 04:47:15 pm" To: antony@turtle.ee.ncku.edu.tw (Antony) Date: Mon, 30 Dec 1996 19:35:40 +1030 (CST) Cc: hackers@freefall.freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Antony stands accused of saying: > > I enabled KTRACE, DDB, DIAGNOSTIC , and modified some source > file of /sys/netinent/ip_input.c, and in some place, it shows > > Dec 30 16:01:34 hawk /kernel: Fatal trap 12: page fault while in kernel mode > Dec 30 16:01:34 hawk /kernel: fault virtual address = 0xf0a1a004 > Dec 30 16:01:34 hawk /kernel: fault code = supervisor read, page not present I strongly suggest reading the message. I can't imagine what more you could possibly want to know, except for perhaps having the kernel work out your bug and fix it itself. > Dec 30 16:01:34 hawk /kernel: instruction pointer = 0x8:0xf0a106b4 > Any idea about what the hell it is ? Yeah. You made a mistake. You could try reading the handbook section on kernel debugging. An easy start is 'nm /kernel |sort |more' and look for the symbol just before the instruction pointer, which will tell you in which function you caused the explosion. > Antony -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Dec 30 01:23:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id BAA11021 for hackers-outgoing; Mon, 30 Dec 1996 01:23:10 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA10985 for ; Mon, 30 Dec 1996 01:22:21 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id UAA18245; Mon, 30 Dec 1996 20:20:44 +1100 (EST) From: Julian Assange Message-Id: <199612300920.UAA18245@profane.iq.org> Subject: libmsun To: hackers@freebsd.org Date: Mon, 30 Dec 1996 20:20:43 +1100 (EST) Cc: rms@gnu.ai.mit.edu X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Having recently started a project that consumes libm() functions in great quantity, I thought I'd see what I could do to speed up FreeBSD's libm performance. Hope that there was room for improvement came from the posting of one researcher who had benchmarked the linux libm code (on a pentium) as twice as fast as FreeBSD's. Looking at the ieee libm (/usr/src/lib/libm/*) I discoverd that there was no FPU support, and no asm fast-pathing. Thinking, naturally enough, that this would more than easily account for all differences, I, somewhat painfully, ported the linux/glibc/dj libm to /usr/src/contrib and /usr/lib/libmdj Only then did I find out that, contrary to what one would intuit, libm is not used for /usr/lib/libm* but rather the SunPro fdlibm from /usr/src/lib/msun (perhaps it is time to nuke the old Berkeley one?). fdlibm does have i386/i387 support, though not as many functions are asm/fpu coded compared to the linux libm. If I notice a difference speed betwixt it and libmdj, then this is the obvious place for optimisation. The sun code is certainly much more pleasant to look at than the glib/linux/dj mess. Now, in terms of compile-time optimisation of fdlibm, we have: # There are two options in making libm at fdlibm compile time: # _IEEE_LIBM --- IEEE libm; smaller, and somewhat faster # _MULTI_LIBM --- Support multi-standard at runtime by # imposing wrapper functions defined in # fdlibm.h: # _IEEE_MODE -- IEEE # _XOPEN_MODE -- X/OPEN # _POSIX_MODE -- POSIX/ANSI # _SVID3_MODE -- SVID # # Here is how to set up CFLAGS to create the desired libm at # compile time: # # CFLAGS = -D_IEEE_LIBM ... IEEE libm (recommended) # CFLAGS = -D_SVID3_MODE ... Multi-standard supported # libm with SVID as the # default standard # CFLAGS = -D_XOPEN_MODE ... Multi-standard supported # libm with XOPEN as the # default standard # CFLAGS = -D_POSIX_MODE ... Multi-standard supported # libm with POSIX as the # default standard # CFLAGS = ... Multi-standard supported # libm with IEEE as the # default standard # CFLAGS+= -D_MULTI_LIBM -D_POSIX_MODE -D_IEEE_LIBM Do we really need MULTI and POSIX? The linux libm has the following specific optimisations applied: -ffast-math -mieee-fp Examining the GCC documentation, we find: `-ffast-math' This option allows GCC to violate some ANSI or IEEE rules and/or specifications in the interest of optimising code for speed. For example, it allows the compiler to assume arguments to the `sqrt' function are non-negative numbers and that no floating-point values are NaNs. This option should never be turned on by any `-O' option since it can result in incorrect output for programs which depend on an exact implementation of IEEE or ANSI rules/specifications for math functions. If the flow path in msun functions is such that NaNs/other invalid parameters are not used, then this optimisation would be a small win. However, we find that -ffast-math does more than this snippet of documentation would have us believe. `-mno-fancy-math-387' Some 387 emulators do not support the `sin', `cos' and `sqrt' instructions for the 387. Specify this option to avoid generating those instructions. This option is the default on FreeBSD. As of revision 2.6.1, these instructions are not generated unless you also use the `-ffast-math' switch. This is silly. The only way we can have gcc use its builtins for sin, cos and sqrt (possibly the three most used high-level fpu functions) is to ignore several error conditions. Clearly this isn't acceptable as a default for user code - however we can take precautions in libm for functions that use the gcc builtins and activate -mfancy-math-387 and -ffast-math for its compilation. `-mno-ieee-fp' `-mieee-fp' Control whether or not the compiler uses IEEE floating point comparisons. These handle correctly the case where the result of a comparison is unordered. ` This looks appropriate enough. I'm just trying to recall what an "unorded comparison" is. a>b : a=b? It is also possible the documentation is out of date. Someone care to check this? -Julian Assange (proff@iq.org) From owner-freebsd-hackers Mon Dec 30 03:39:10 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA21145 for hackers-outgoing; Mon, 30 Dec 1996 03:39:10 -0800 (PST) Received: (from jmb@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA21139; Mon, 30 Dec 1996 03:39:03 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199612301139.DAA21139@freefall.freebsd.org> Subject: Re: IPCS Utility To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Mon, 30 Dec 1996 03:39:03 -0800 (PST) Cc: msmith@atrad.adelaide.edu.au, seanb012@sunbeach.net, freebsd-hackers@FreeBSD.org In-Reply-To: <13949.851917064@time.cdrom.com> from "Jordan K. Hubbard" at Dec 29, 96 07:37:44 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard wrote: > > > we could call a new majordomo list ...... > > let me know and i will create the list within 24 hours > > Please! Though can we call it config@freebsd.org because > config-management, as descriptive as that is, will wear my fingers > off. ;-) The "long name" would, of course, be freebsd-config. FreeBSD-config aka config is ready saddle-up und ride. jmb From owner-freebsd-hackers Mon Dec 30 06:57:47 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id GAA29703 for hackers-outgoing; Mon, 30 Dec 1996 06:57:47 -0800 (PST) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id GAA29693 for ; Mon, 30 Dec 1996 06:57:43 -0800 (PST) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.7.5/8.7.3) with ESMTP id PAA08336 for ; Mon, 30 Dec 1996 15:57:35 +0100 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.6.12/8.6.12) with UUCP id PAA05209 for freebsd-hackers@FreeBSD.org; Mon, 30 Dec 1996 15:57:18 +0100 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.4/keltia-uucp-2.9) id NAA02382; Mon, 30 Dec 1996 13:42:19 +0100 (CET) Message-ID: Date: Mon, 30 Dec 1996 13:42:19 +0100 From: roberto@keltia.freenix.fr (Ollivier Robert) To: freebsd-hackers@FreeBSD.org Subject: Re: IPCS Utility References: <199612300106.LAA04664@genesis.atrad.adelaide.edu.au> X-Mailer: Mutt 0.55.04 Mime-Version: 1.0 X-Operating-System: FreeBSD 3.0-CURRENT ctm#2837 In-Reply-To: <199612300106.LAA04664@genesis.atrad.adelaide.edu.au>; from Michael Smith on Dec 30, 1996 11:36:27 +1030 Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk According to Michael Smith: > Development on this is currently underway; if you're Tcl literate (or are > willing to learn & want to take part regardless) then we'd love to have I hope it is not restricted to Tcl gurus... I'm afraid I don't like Tcl but can speak Perl5 easily... I know Perl5 is not in /usr/src and Tcl is but that should not be a problem :-) -- Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #33: Sat Dec 21 12:57:17 CET 1996 From owner-freebsd-hackers Mon Dec 30 11:13:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA11899 for hackers-outgoing; Mon, 30 Dec 1996 11:13:03 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA11884 for ; Mon, 30 Dec 1996 11:12:58 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id TAA04898; Mon, 30 Dec 1996 19:51:28 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA11805; Mon, 30 Dec 1996 19:51:27 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id TAA09551; Mon, 30 Dec 1996 19:40:09 +0100 (MET) From: J Wunsch Message-Id: <199612301840.TAA09551@uriah.heep.sax.de> Subject: Re: DEVFS strangeness To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Mon, 30 Dec 1996 19:40:09 +0100 (MET) Cc: randy@zyzzyva.com (Randy Terbush) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199612291900.NAA18516@sierra.zyzzyva.com> from Randy Terbush at "Dec 29, 96 01:00:05 pm" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Randy Terbush wrote: > Seems that sound devices are being created as follows. > > crw-rw---- 1 root games 30, 68 Dec 19 08:49 /dev/audio4 > # Sounds support > controller snd0 > device gus0 at isa? port 0x220 irq 12 drq 1 vector gusintr > > #> cat /usr/local/lib/sound/sounds/clink.au > /dev/audio4 > su: /dev/audio4: Device not configured > > Is this a known deficiency of the DEVFS? No, it's a known (now that you mention it :) deficiency of the sound driver. A quick glance over the source yields: static int sndattach (struct isa_device *dev) { int unit; ... unit = driver_to_voxunit(dev->id_driver); ... #ifdef DEVFS /* XXX */ /* find out where to store the tokens.. */ /* XXX */ /* should only create devices if that card has them */ #define SND_UID 0 #define SND_GID 13 snd_devfs_token[unit]= devfs_add_devswf(&snd_cdevsw, (unit << 4)+SND_DEV_CTL, DV_CHR, ^^^^ SND_UID, SND_GID, 0660, "mixer%d", unit); ^^ ^^^^ However: static int driver_to_voxunit(struct isa_driver *driver) { /* converts a sound driver pointer into the equivalent VoxWare device unit number */ if(driver == &opldriver) return(SNDCARD_ADLIB); else if(driver == &sbdriver) return(SNDCARD_SB); else if(driver == &pasdriver) return(SNDCARD_PAS); etc. pp.... So this driver seems to have to very different ideas of what a `unit' might be. If it would really use the term `unit' consistently in the above sense, it should recognize it always as being unit 4. Probably, the unit # in the DEVFS sense can only be 0 at all for this driver, however. I think this idea of a unit # is a gross abuse... If i read this correctly, it would never be possible to put two identical soundcards into the same machine (on different hardware addresses and interrupt vectors, i mean)? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Dec 30 11:28:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA12729 for hackers-outgoing; Mon, 30 Dec 1996 11:28:44 -0800 (PST) Received: from jump.net (serv1-2.jump.net [204.238.120.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA12710; Mon, 30 Dec 1996 11:28:40 -0800 (PST) Received: by jump.net (8.8.4/BERK-6.8.11) id NAA01672; Mon, 30 Dec 1996 13:28:30 -0600 (CST) Date: Mon, 30 Dec 1996 13:28:29 -0600 (CST) From: Lee Crites To: Ben Black cc: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org Subject: Re: de ethernet driver stomps SMC 10/100 In-Reply-To: <9612271830.AA25005@squid.gage.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 27 Dec 1996, Ben Black wrote: > the new chipset is the DEC 21140-A instead of the DEC 21140. though they > are in the same family, the two are not driver compatible. the SMC cards > with the 21140-A chip is generally labelled SMC EtherPower 10/100 B (the B is > the important part). i just got 5 new P6 machines with the B series and > they are useless to me. Well, I'm kind of in the same boat -- maybe. I am just no trying to bring up my first FreeBSD system. I have a recently purchased SMC9332 10/100 card. Nothing on my box or docu states it is a "B" version. I've tried just about all of the different configurations suggested in the FreeBSD DOCS cd I could find, but to no avail. I figured I was missing some important step in the process. I put the "device de0" line in the kernel (and got a clean compile and install), then did the "ifconfig de0 init ... " command (with and without the -line2). As soon as I did that, the WebRamp light for that line went out and has stayed out. What I was *going* to ask (and still am) is for someone who is using the SMC9332 to please send me the exact steps they used to get it configured and running from scratch. Most of the messages in the DOCS cd answer specific questions, but none I saw had the complete steps. *I* might be missing something. Here's what I've done so far: * configured the WebRamp hub/router (via a win95 box -- also using a SMC9332 card) so it knows all of the ip addresses in question (only three at this time) * commented out all of the ethernet related lines in the GENERIC configuration except de0 * added the above ip address info to the /etc/hosts file * compiled and installed the new kernel (with the requisite reboot to make it active) * executed the command: ifconfig de0 inet 205.182.92.2 netmask 255.255.255.0 (with and without '-link2' added at the end) It is my assumption (I know, dangerous word) that I should now be 'up.' But, as I said earlier, as soon as I started using de0, the link light on the WebRamp for this box goes out. When I was using ed0 (due to misreading one of the first messages I checked) the light stayed on. So... Am I 1) missing something, 2) doing something wrong, or 3) suffering from the same problem as above? I don't mind reading, but if your response is 'rtfm' then please include which 'fm' and which passage(s) of said 'fm.' I've been 'rt'ing' for the past week without finding the answer (or at least I didn't *think* I found it). Thanks muchly... Lee From owner-freebsd-hackers Mon Dec 30 11:30:05 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA12877 for hackers-outgoing; Mon, 30 Dec 1996 11:30:05 -0800 (PST) Received: from profane.iq.org (profane.iq.org [203.4.184.217]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA12825 for ; Mon, 30 Dec 1996 11:29:52 -0800 (PST) Received: (from proff@localhost) by profane.iq.org (8.8.4/8.8.2) id GAA29162 for hackers@freebsd.org; Tue, 31 Dec 1996 06:28:55 +1100 (EST) From: Julian Assange Message-Id: <199612301928.GAA29162@profane.iq.org> Subject: divert code not thread/smp compatible To: hackers@freebsd.org Date: Tue, 31 Dec 1996 06:28:55 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk /* * ip_input() and ip_output() set this secret value before calling us to * let us know which divert port to divert a packet to; this is done so * we can use the existing prototype for struct protosw's pr_input(). * This is stored in host order. */ u_short ip_divert_port; /* * We set this value to a non-zero port number when we want the call to * ip_fw_chk() in ip_input() or ip_output() to ignore ``divert '' * chain entries. This is stored in host order. */ u_short ip_divert_ignore; Is this an acceptable trick in the FreeBSD kernel, passing parameters with global variables? -Julian From owner-freebsd-hackers Mon Dec 30 11:50:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA14323 for hackers-outgoing; Mon, 30 Dec 1996 11:50:41 -0800 (PST) Received: from gateway.telecom.ksu.edu (smtp@gateway.telecom.ksu.edu [129.130.63.239]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA14317 for ; Mon, 30 Dec 1996 11:50:38 -0800 (PST) Received: from sioux.telecom.ksu.edu(129.130.60.32) by pawnee.telecom.ksu.edu via smap (V1.3) id sma021411; Mon Dec 30 13:50:06 1996 From: joed@telecom.ksu.edu (Joe Diehl) Message-Id: <199612301950.NAA24269@telecom.ksu.edu> Subject: 2.2-Beta install To: freebsd-hackers@freebsd.org Date: Mon, 30 Dec 1996 13:50:06 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I just upgraded from FreeBSD 2.2-ALPHA to 2.2-BETA last night, install went without problem. Couple thoughts on the upgrade process: First I noticed that after upgrading to 2.2-BETA the installer failed to install a new kernel. Essentially, the upgrade wasn't finished till I recompiled my kernel. This isn't too much of a problem for me as I was going to recompile anyways, but this could present a problem for others... I'm not sure I have a recommendation here but there was a bit of a shock booting up in my recently upgraded 2.2-BETA box, type 'uname -a' I see that I'm apparently still running 2.2-ALPHA. I probably would have paniced at this when I first started using unix. ;) The big issue is in regards of what to do with /etc. The installer overwrote several if not all of the configuration files including files that shouldn't be touched like /etc/hosts, /etc/passwd, /etc/groups, etc... What I would just assume see is that the installer not touch the /etc tree at all, but instead install a file or tree (perhaps in /root) that lists the changes made to the /etc tree over various releases. At this point I can migrate changes into my files as I see necessary. I realize that perhaps differant people would have differant preferances on this, so an option on how to deal with /etc may be in order... Just a thought if you're every bored (yeah right), I made an attempt to boot off the floppy drive by booting the hard drive the specifying to boot off fd(0,a)/kernel (I tried several varients of this line). Reason for this is because I set the system up to boot on drive C: only for security reasons. The one time the boot actually started it simply scrolled errors (can't remember what they were). It would be nice not to have to dink with the system setup to boot the floppy everytime I wanted to install a new version. Though this sort of option should be password protected. But it could be beneficial for booting off say a zip drive, or cdrom (as peecees can't seem to figure out I might want to install an o/s off something other than a floppy) to do an install. Once upon a time I just about started to push for installing FreeBSD on the machines I administrated when I worked for KSU College of Engineering. I stopped short because FreeBSD didn't, and still doesn't, support those network cards; however, I can't imagine going through 100 machines and modifing the BIOS setup everytime a new version of FreeBSD comes out. Note that the College is now looking at dual booting WinNT and Linux in those labs, so it wasn't just my dreaming of putting unix out in the lab. ...Or maybe I'm just too caught up on the proms in my Sparcs at work. Things like L1-A followed by "boot cdrom".. =) Outside of /etc the upgrades of FreeBSD seem to go very smoothly. Good job. .. I invision a time where I have installed FreeBSD on the secretaries (sorry, Administrative Assistants) desktop machine and don't have to listen to "My computer locked up again *whimper*" anymore... --- Joe Diehl KSU Dept. of Telecommunications From owner-freebsd-hackers Mon Dec 30 11:51:30 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA14440 for hackers-outgoing; Mon, 30 Dec 1996 11:51:30 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA14422 for ; Mon, 30 Dec 1996 11:51:25 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id GAA07092; Tue, 31 Dec 1996 06:47:23 +1100 Date: Tue, 31 Dec 1996 06:47:23 +1100 From: Bruce Evans Message-Id: <199612301947.GAA07092@godzilla.zeta.org.au> To: hackers@freebsd.org, proff@iq.org Subject: Re: libmsun Cc: rms@gnu.ai.mit.edu Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Only then did I find out that, contrary to what one would intuit, >libm is not used for /usr/lib/libm* but rather the SunPro fdlibm >from /usr/src/lib/msun (perhaps it is time to nuke the old >Berkeley one?). It has a few advantages, such as working on non-IEEE machines and separate implementations of gamma() and log(gamma()). >fdlibm does have i386/i387 support, though not as many functions >are asm/fpu coded compared to the linux libm. If I notice a difference >speed betwixt it and libmdj, then this is the obvious place for >optimisation. The sun code is certainly much more pleasant to look >at than the glib/linux/dj mess. fdlibm emphasizes accuracy over efficiency. The i387 support already breaks some of that. E.g., the i387 doesn't use a 396-digit approximation for pi, and exp(x) is implemented using the too-simple formula exp(x) = 2^(x * log2(e)). The accuracy of this formula depends on the multiplication being done in extended precision (which isn't the default in FreeBSD) and the result being interpreted as double precision. A full extended precision exp() would require at least as much code as fdlibm's C version. >Now, in terms of compile-time optimisation of fdlibm, we have: >Now, in terms of compile-time optimisation of fdlibm, we have: > >[lots of comments in makefile ] > >CFLAGS+= -D_MULTI_LIBM -D_POSIX_MODE -D_IEEE_LIBM > >Do we really need MULTI and POSIX? No. -D_MULTI_LIBM -D_POSIX_MODE -D_IEEE_LIBM is a bogus combination of flags. It is equivalent to IEEE_LIBM alone (fastest) Whoever imported the makefile apparently didn't read the comments. We really need only POSIX to get ANSI support. This would be even slower than now, and the ANSI support is slightly broken, so I didn't bother fixing this. >The linux libm has the following specific optimisations applied: > > -ffast-math -mieee-fp -mieee-fp is the default. -ffast-math is probably not a good idea in libmsun. It probably doesn't make much difference, and libmsun assumes full IEEE behaviour, right down to calculating expressions such as the following at run time to get their IEEE side effects: static const double huge = 1e300; ... return (huge * huge); /* return +Inf and set IEEE overflow flag */ gcc -O optimizes this to +Inf at compile time and doesn't set the overflow flag. My version of the library uses the hack `#define const volatile const' to avoid the optimization. This mainly slows things down some more :-]. >If the flow path in msun functions is such that NaNs/other invalid >parameters are not used, then this optimisation would be a small win. They are used. See e.g. e_pow.c where there are 19 special boundary cases involving NaNs or Infs. >However, we find that -ffast-math does more than this snippet of documentation >would have us believe. > >`-mno-fancy-math-387' > Some 387 emulators do not support the `sin', `cos' and `sqrt' > instructions for the 387. Specify this option to avoid generating > those instructions. This option is the default on FreeBSD. As of > revision 2.6.1, these instructions are not generated unless you > also use the `-ffast-math' switch. > >This is silly. The only way we can have gcc use its builtins for >sin, cos and sqrt (possibly the three most used high-level fpu >functions) is to ignore several error conditions. Clearly this >isn't acceptable as a default for user code - however we can take >precautions in libm for functions that use the gcc builtins and >activate -mfancy-math-387 and -ffast-math for its compilation. I believe that the change in 2.6.1 was because the 387 builtins are fast and wrong. They aren't ANSI conformant, and the trig functions don't do range reduction. >It is also possible the documentation is out of date. Someone >care to check this? The man page is a bit out of date, but gcc.info* is OK. Bruce From owner-freebsd-hackers Mon Dec 30 12:04:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA15116 for hackers-outgoing; Mon, 30 Dec 1996 12:04:26 -0800 (PST) Received: from gateway.telecom.ksu.edu (smtp@gateway.telecom.ksu.edu [129.130.63.239]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA15108 for ; Mon, 30 Dec 1996 12:04:21 -0800 (PST) Received: from sioux.telecom.ksu.edu(129.130.60.32) by pawnee.telecom.ksu.edu via smap (V1.3) id sma021450; Mon Dec 30 14:03:50 1996 From: joed@telecom.ksu.edu (Joe Diehl) Message-Id: <199612302003.OAA24881@telecom.ksu.edu> Subject: Re: IPCS Utility To: freebsd-hackers@freebsd.org Date: Mon, 30 Dec 1996 14:03:49 -0600 (CST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Ollivier Robert wrote: > > According to Michael Smith: > > Development on this is currently underway; if you're Tcl literate (or are > > willing to learn & want to take part regardless) then we'd love to have > > I hope it is not restricted to Tcl gurus... I'm afraid I don't like Tcl but > can speak Perl5 easily... I know Perl5 is not in /usr/src and Tcl is but > that should not be a problem :-) > If you need anyone else to do Perl coding let me know, I'd be happy to help. Though my perl knowledge is limited to perl4 as I havn't bought the new camel book yet... ;) --- Joe Diehl KSU Dept. of Telecommunications From owner-freebsd-hackers Mon Dec 30 12:48:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA17864 for hackers-outgoing; Mon, 30 Dec 1996 12:48:49 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA17859 for ; Mon, 30 Dec 1996 12:48:47 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id MAA24233 for ; Mon, 30 Dec 1996 12:48:41 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id MAA10143; Mon, 30 Dec 1996 12:44:49 -0800 (PST) Message-ID: <32C8297C.446B9B3D@whistle.com> Date: Mon, 30 Dec 1996 12:43:40 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Joerg Wunsch CC: FreeBSD hackers , Randy Terbush Subject: Re: DEVFS strangeness References: <199612301840.TAA09551@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Randy Terbush wrote: > > > Is this a known deficiency of the DEVFS? > > No, it's a known (now that you mention it :) deficiency of the sound > driver. A quick glance over the source yields: Randy: When I added devfs support to all teh devices, I had to add it to some devices that I didn't understand very well. the sound drivers came under this catagory. I guess I didn't understand it as well as I thought I did. you just need to fix the sections of code marked with #ifdef DEVFS there are man pages in chapter 9 for the devfs entrypoints.. if you have hte time to experiment, you migh tbe the perfect person to submit the patches. > > static int > sndattach (struct isa_device *dev) > { > int unit; > ... > > unit = driver_to_voxunit(dev->id_driver); > ... > > #ifdef DEVFS > /* XXX */ /* find out where to store the tokens.. */ > /* XXX */ /* should only create devices if that card has them */ > #define SND_UID 0 > #define SND_GID 13 > > snd_devfs_token[unit]= > devfs_add_devswf(&snd_cdevsw, (unit << 4)+SND_DEV_CTL, DV_CHR, > ^^^^ > SND_UID, SND_GID, 0660, "mixer%d", unit); > ^^ ^^^^ > > However: > > static int > driver_to_voxunit(struct isa_driver *driver) > { > /* converts a sound driver pointer into the equivalent > VoxWare device unit number */ > if(driver == &opldriver) > return(SNDCARD_ADLIB); > else if(driver == &sbdriver) > return(SNDCARD_SB); > else if(driver == &pasdriver) > return(SNDCARD_PAS); > etc. pp.... > > So this driver seems to have to very different ideas of what a `unit' > might be. If it would really use the term `unit' consistently in the > above sense, it should recognize it always as being unit 4. Probably, > the unit # in the DEVFS sense can only be 0 at all for this driver, > however. > > I think this idea of a unit # is a gross abuse... If i read this > correctly, it would never be possible to put two identical soundcards > into the same machine (on different hardware addresses and interrupt > vectors, i mean)? I think you are right.. Maybe we should take the latest drivers from amancio and the original author and import them, and FIX them :) > > -- > cheers, J"org > > joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE > Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Mon Dec 30 13:12:02 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA19903 for hackers-outgoing; Mon, 30 Dec 1996 13:12:02 -0800 (PST) Received: from calvino.alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA19879 for ; Mon, 30 Dec 1996 13:11:52 -0800 (PST) Received: from calvino.alaska.net (hmmm@calvino.alaska.net [206.149.65.3]) by calvino.alaska.net (8.8.0/8.7.3) with SMTP id MAA29326 for ; Mon, 30 Dec 1996 12:11:48 -0900 (AKST) Date: Mon, 30 Dec 1996 12:11:47 -0900 (AKST) From: hmmm To: freebsd-hackers Subject: Ints Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk this isn't particular to FreeBSD - but after searching - i don't know who else to ask! please reply via email - i am not currently a subscriber! Q: is there danger in servicing a lower priority pending interrupt while servicing the highest priority INT in the same ISR ? IE - are any interrupt functions/bits LATCHED - that may need to be cleaned up? for example - i have both COM ports tied to the same ISR - is there any danger in reading RxBuf1 (lower priority) while SERVICING an RxBuf2 INT? or - satisfying a TxBuf INT (lower priority) while taking care of RxBuf INT? OR - does eliminating any INTerrupt condition KILL all things related to that INTerrupt? thanks ahead of time ... ------------------------------------------------------------------------------ Sleep: a sign a caffeine deprivation ... http://www.alaska.net/~hmmm ------------------------------------------------------------------------------ From owner-freebsd-hackers Mon Dec 30 13:20:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA21004 for hackers-outgoing; Mon, 30 Dec 1996 13:20:49 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA20993 for ; Mon, 30 Dec 1996 13:20:42 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA29552; Mon, 30 Dec 1996 16:20:03 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 30 Dec 1996 16:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id PAA03142 for ; Mon, 30 Dec 1996 15:20:45 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id PAA29847 for freebsd-hackers@freebsd.org; Mon, 30 Dec 1996 15:24:01 -0500 (EST) Date: Mon, 30 Dec 1996 15:24:01 -0500 (EST) From: Thomas David Rivers Message-Id: <199612302024.PAA29847@lakes.water.net> To: ponds!freebsd.org!freebsd-hackers Subject: Results of 2.1.6 SL/IP test install... Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well - 2.1.6(.1) is long since frozen; but since I've been checking out all the releases thus far; I'll go ahead and let everyone know what I've found. 2.1.6(.1) was an absolute joy to install. The SL/IP support in the install has been troublesome in the past; but it worked like a champ this time! (Yeah!) Good work Jordan! I'm snarfing the 2.2 BETA floppies from Dec 25th to see how they work on this machine - but I won't be able to do a full install for some time; as I'm quite "challenged" with my network connections... It will take me quite a while to get the 2.2-BETA downloaded and put somewhere where I can try it out, and it seems to change before I can get that done :-) - Dave Rivers - From owner-freebsd-hackers Mon Dec 30 13:21:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA21036 for hackers-outgoing; Mon, 30 Dec 1996 13:21:08 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA21029 for ; Mon, 30 Dec 1996 13:21:04 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA29537; Mon, 30 Dec 1996 16:20:02 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Mon, 30 Dec 1996 16:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id PAA03070 for ; Mon, 30 Dec 1996 15:17:06 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id PAA29841 for freebsd-hackers@freebsd.org; Mon, 30 Dec 1996 15:20:20 -0500 (EST) Date: Mon, 30 Dec 1996 15:20:20 -0500 (EST) From: Thomas David Rivers Message-Id: <199612302020.PAA29841@lakes.water.net> To: ponds!freebsd.org!freebsd-hackers Subject: 2.1.6 CD shipped? Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've been waiting on my 2.1.6 CD (after snarfing and then re-snarfing 2.1.6(.1)...) I thought it was to ship well before 2.2 was ready... has it "gone out" yet? - Thanks - - Dave R. - From owner-freebsd-hackers Mon Dec 30 14:21:36 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA24824 for hackers-outgoing; Mon, 30 Dec 1996 14:21:36 -0800 (PST) Received: from ravenock.cybercity.dk (ravenock.cybercity.dk [194.16.57.32]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA24651 for ; Mon, 30 Dec 1996 14:18:56 -0800 (PST) Received: (from sos@localhost) by ravenock.cybercity.dk (8.8.4/8.7.3) id XAA00733; Mon, 30 Dec 1996 23:19:12 +0100 (MET) Message-Id: <199612302219.XAA00733@ravenock.cybercity.dk> Subject: Re: divert code not thread/smp compatible In-Reply-To: <199612301928.GAA29162@profane.iq.org> from Julian Assange at "Dec 31, 96 06:28:55 am" To: proff@iq.org (Julian Assange) Date: Mon, 30 Dec 1996 23:19:12 +0100 (MET) Cc: hackers@FreeBSD.ORG From: sos@FreeBSD.ORG Reply-to: sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In reply to Julian Assange who wrote: > > /* > * ip_input() and ip_output() set this secret value before calling us to > * let us know which divert port to divert a packet to; this is done so > * we can use the existing prototype for struct protosw's pr_input(). > * This is stored in host order. > */ > u_short ip_divert_port; > > /* > * We set this value to a non-zero port number when we want the call to > * ip_fw_chk() in ip_input() or ip_output() to ignore ``divert '' > * chain entries. This is stored in host order. > */ > u_short ip_divert_ignore; > > Is this an acceptable trick in the FreeBSD kernel, passing parameters > with global variables? No, its just bad, bad.... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@FreeBSD.org) FreeBSD Core Team Even more code to hack -- will it ever end .. From owner-freebsd-hackers Mon Dec 30 14:46:42 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA26267 for hackers-outgoing; Mon, 30 Dec 1996 14:46:42 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA26250 for ; Mon, 30 Dec 1996 14:46:32 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id JAA12084; Tue, 31 Dec 1996 09:42:55 +1100 Date: Tue, 31 Dec 1996 09:42:55 +1100 From: Bruce Evans Message-Id: <199612302242.JAA12084@godzilla.zeta.org.au> To: freebsd-hackers@freebsd.org, joed@telecom.ksu.edu Subject: Re: 2.2-Beta install Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Just a thought if you're every bored (yeah right), I made an attempt to >boot off the floppy drive by booting the hard drive the specifying to >boot off fd(0,a)/kernel (I tried several varients of this line). Reason >for this is because I set the system up to boot on drive C: only for >security reasons. The one time the boot actually started it simply scrolled >errors (can't remember what they were). The installation kernel uses a specially broken bootstrap to save space. It uses rawboot instead of biosboot. biosboot can't handle raw disks :-(. This hack shouldn't be necessary now that 1200K floppies are no longer supported. Bruce From owner-freebsd-hackers Mon Dec 30 15:15:54 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA27662 for hackers-outgoing; Mon, 30 Dec 1996 15:15:54 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA27655 for ; Mon, 30 Dec 1996 15:15:48 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id KAA13090; Tue, 31 Dec 1996 10:12:14 +1100 Date: Tue, 31 Dec 1996 10:12:14 +1100 From: Bruce Evans Message-Id: <199612302312.KAA13090@godzilla.zeta.org.au> To: hackers@freebsd.org, hmmm@alaska.net Subject: Re: Ints Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Q: is there danger in servicing a lower priority pending interrupt while >servicing the highest priority INT in the same ISR ? Only if there are bugs. >IE - are any interrupt functions/bits LATCHED - that may need to be >cleaned up? They are not latched by ISA hardware. They are latched by FreeBSD software, except for some serial interrupts. >for example - i have both COM ports tied to the same ISR - is there any >danger in reading RxBuf1 (lower priority) while SERVICING an RxBuf2 INT? There is extreme danger of this not working at all, for other reasons - ISA hardware doesn't support sharing interrupts (at the same time). >or - satisfying a TxBuf INT (lower priority) while taking care of RxBuf >INT? > >OR - does eliminating any INTerrupt condition KILL all things related to >that INTerrupt? The events that cause the interrupts can be handled in any order for xx(x)50 UARTs, except for bugs of course. 8250s have bugs involving losing modem control (?) interrupts while other interrupts are being handled. Bruce From owner-freebsd-hackers Mon Dec 30 15:15:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id PAA27676 for hackers-outgoing; Mon, 30 Dec 1996 15:15:58 -0800 (PST) Received: from irbs.irbs.com (jc@irbs.irbs.com [199.182.75.129]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id PAA27661 for ; Mon, 30 Dec 1996 15:15:53 -0800 (PST) Received: (from jc@localhost) by irbs.irbs.com (8.8.4/8.8.4) id SAA01115; Mon, 30 Dec 1996 18:15:23 -0500 (EST) Message-ID: Date: Mon, 30 Dec 1996 18:15:22 -0500 From: jc@irbs.com (John Capo) To: adonai@jump.net (Lee Crites) Cc: black@squid.gage.com (Ben Black), freebsd-hackers@freebsd.org Subject: Re: de ethernet driver stomps SMC 10/100 References: <9612271830.AA25005@squid.gage.com> X-Mailer: Mutt 0.55 Mime-Version: 1.0 X-Organization: IRBS Engineering, (954) 792-9551 In-Reply-To: ; from Lee Crites on Dec 30, 1996 13:28:29 -0600 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Quoting Lee Crites (adonai@jump.net): > On Fri, 27 Dec 1996, Ben Black wrote: > > > the new chipset is the DEC 21140-A instead of the DEC 21140. though they > > are in the same family, the two are not driver compatible. the SMC cards > > with the 21140-A chip is generally labelled SMC EtherPower 10/100 B (the B is > > the important part). i just got 5 new P6 machines with the B series and > > they are useless to me. > > Well, I'm kind of in the same boat -- maybe. I am just no trying to bring > up my first FreeBSD system. I have a recently purchased SMC9332 10/100 > card. Nothing on my box or docu states it is a "B" version. I've tried Just last night I got a SMC9332BDT working with -stable. Basically I detected that the chip was a 21140A and pointed it at a new boardsw structure. I haven't tested it a 100Mbs. Works fine at 10Mps. These diff fragments are from a 11/11/96 version of if_de.c. John Capo if_de.c: TULIP_DC21140_DEC_DE500, /* Digital DE500-?? 10/100 */ TULIP_DC21140_SMC_9332, /* SMC 9332 */ + TULIP_DC21140A_SMC_9332BDT, /* SMC 9332BDT with 21140A */ TULIP_DC21140_COGENT_EM100, /* Cogent EM100 100 only */ TULIP_DC21140_ZNYX_ZX34X, /* ZNYX ZX342 10/100 */ + static const tulip_boardsw_t tulip_dc21140A_smc9332bdt_boardsw = { + TULIP_DC21140A_SMC_9332BDT, + "SMC 9332BDT ", + tulip_dc21140_smc9332_media_probe, + tulip_dc21140_mii_media_preset, + tulip_dc21140_mii_probe, + }; sc->tulip_boardsw = &tulip_dc21140_smc9332_boardsw; return; } + if (sc->tulip_chipid == TULIP_DC21140A) { + sc->tulip_boardsw = &tulip_dc21140A_smc9332bdt_boardsw; + return; + } id1 = sc->tulip_rombuf[0x60] | (sc->tulip_rombuf[0x61] << 8); id2 = sc->tulip_rombuf[0x62] | (sc->tulip_rombuf[0x63] << 8); From owner-freebsd-hackers Mon Dec 30 16:12:16 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA00812 for hackers-outgoing; Mon, 30 Dec 1996 16:12:16 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA00798 for ; Mon, 30 Dec 1996 16:12:09 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id QAA14044; Mon, 30 Dec 1996 16:07:22 -0800 (PST) Message-ID: <32C858F6.41C67EA6@whistle.com> Date: Mon, 30 Dec 1996 16:06:14 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Julian Assange CC: hackers@freebsd.org, archie@alpo.whistle.com Subject: Re: divert code not thread/smp compatible References: <199612301928.GAA29162@profane.iq.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Julian Assange wrote: I agree.. this should be changed.. I'll point it out to archie.. he shouldbe back tomorrow. thanks. julian (E) > > /* > * ip_input() and ip_output() set this secret value before calling us to > * let us know which divert port to divert a packet to; this is done so > * we can use the existing prototype for struct protosw's pr_input(). > * This is stored in host order. > */ > u_short ip_divert_port; > > /* > * We set this value to a non-zero port number when we want the call to > * ip_fw_chk() in ip_input() or ip_output() to ignore ``divert '' > * chain entries. This is stored in host order. > */ > u_short ip_divert_ignore; > > Is this an acceptable trick in the FreeBSD kernel, passing parameters > with global variables? > > -Julian From owner-freebsd-hackers Mon Dec 30 16:32:51 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA02541 for hackers-outgoing; Mon, 30 Dec 1996 16:32:51 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA02524; Mon, 30 Dec 1996 16:32:45 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id LAA08271; Tue, 31 Dec 1996 11:02:27 +1030 (CST) From: Michael Smith Message-Id: <199612310032.LAA08271@genesis.atrad.adelaide.edu.au> Subject: Re: IPCS Utility In-Reply-To: from Ollivier Robert at "Dec 30, 96 01:42:19 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Tue, 31 Dec 1996 11:02:26 +1030 (CST) Cc: freebsd-hackers@freebsd.org, config@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Ollivier Robert stands accused of saying: > According to Michael Smith: > > Development on this is currently underway; if you're Tcl literate (or are > > willing to learn & want to take part regardless) then we'd love to have > > I hope it is not restricted to Tcl gurus... I'm afraid I don't like Tcl but > can speak Perl5 easily... I know Perl5 is not in /usr/src and Tcl is but > that should not be a problem :-) I should have been more careful with that issue : - We will be using Tcl for parts of the FCF (FreeBSD Config Facility), not least because I expect to be writing slabs of the core. - Understanding Tcl (even in a read-only capacity) will help lots, especially in the early stages of development. - I am not interested in language wars. If you want to write a module, you should be able to do it however you like, as long as you can meet the module interface rules. The planned modular design of the FCF specifically avoids stipulating any given language for modules; if you feel the need to write your module in Forth, as long as you can manage character I/O you can play. If your interpreter comes in a shared library, we'll just load you and run you in a seperate namespace. If you're run by a seperate program, we'll fork you off and talk to you on a pipe. I can see no reason for bigotry. > Ollivier ROBERT -=- The daemon is FREE! -=- roberto@keltia.freenix.fr -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Dec 30 16:40:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA03058 for hackers-outgoing; Mon, 30 Dec 1996 16:40:49 -0800 (PST) Received: from aries.bb.cc.wa.us (root@[208.8.136.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA03053 for ; Mon, 30 Dec 1996 16:40:47 -0800 (PST) Received: from localhost (chris@localhost) by aries.bb.cc.wa.us (8.7.5/8.6.9) with SMTP id QAA01996 for ; Mon, 30 Dec 1996 16:34:59 -0800 (PST) Date: Mon, 30 Dec 1996 16:34:59 -0800 (PST) From: Chris Coleman To: freebsd-hackers@freebsd.org Subject: 2.2-Beta install In-Reply-To: <199612302242.JAA12084@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just tried to install the 2.2-Beta I went through the config, and everything looked normal. then as it was detecting devices. Suddenly the screen turned blue and was flashing little characters. I had to press the reset button. I have a pentium 100 triton chipset aha-2940 W pci controller. 2 scsi II fast and Wide Barracuda Drives pci Diamond Speedstar 2MEG Svga Monitor a few isa cards. NE2000 NEt Card BOCA 16 PORT CARD ISA floppie/io card What is wrong. I think it is a conflict with the video card. I have gotten Xwindows to work. But its been a while since we have used them. Chris Coleman (chris@aries.bb.cc.wa.us) Computer Support Technician I (509)-766-8873 Big Bend Community College Internet Instructor Death is life's way of telling you you're fired. From owner-freebsd-hackers Mon Dec 30 16:41:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id QAA03114 for hackers-outgoing; Mon, 30 Dec 1996 16:41:53 -0800 (PST) Received: from pdx1.world.net (pdx1.world.net [192.243.32.18]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id QAA03109 for ; Mon, 30 Dec 1996 16:41:49 -0800 (PST) From: proff@suburbia.net Received: from suburbia.net (suburbia.net [203.4.184.1]) by pdx1.world.net (8.7.5/8.7.3) with SMTP id QAA02327 for ; Mon, 30 Dec 1996 16:42:19 -0800 (PST) Received: (qmail 17974 invoked by uid 110); 31 Dec 1996 00:41:09 -0000 Message-ID: <19961231004109.17972.qmail@suburbia.net> Subject: PCI cyclades problems solved To: hackers@freebsd.org Date: Tue, 31 Dec 1996 11:41:09 +1100 (EST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce et al, Moving the shared memory from <1M reduced silo overflows around 2-4x. Probably a good idea to put this in the handbook. What eliminated overvlows entirely however, was replacing the system's wd* card with an ne2000. It seems that the wd* was not generating ints after writes, causing non-interruptable timeouts. Cheers, Julian. From owner-freebsd-hackers Mon Dec 30 18:39:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA07712 for hackers-outgoing; Mon, 30 Dec 1996 18:39:08 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA07704 for ; Mon, 30 Dec 1996 18:39:07 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by who.cdrom.com (8.7.5/8.6.11) with SMTP id SAA25009 for ; Mon, 30 Dec 1996 18:39:05 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA01319; Mon, 30 Dec 1996 19:28:48 -0700 From: Terry Lambert Message-Id: <199612310228.TAA01319@phaeton.artisoft.com> Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters To: toor@dyson.iquest.net (John S. Dyson) Date: Mon, 30 Dec 1996 19:28:47 -0700 (MST) Cc: terry@lambert.org, julian@whistle.com, luigi@labinfo.iet.unipi.it, proff@iq.org, danny@panda.hilink.com.au, hackers@freebsd.org In-Reply-To: <199612280319.WAA07203@dyson.iquest.net> from "John S. Dyson" at Dec 27, 96 10:19:01 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > For instance, for FS's, the VFS is well defined, but the VM interface > > for doing actual disk I/O is not well abstracted at all. > > The VM code uses direct disk input when the filesystem allows it. Otherwise, > the filesystems can do VOP_READ operations as in normal UFS read write > operations. The vnode pageout uses VOP_WRITE operations. Refer to > vnode_pager (where the VM input output operations happen.) I don't think > that there are layering problems anymore (there were initially though.) No, this particular issue isn't layering -- my favorite harp to play -- it's basically definition information that would be in a "file system writer's guide"... if there were one. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Dec 30 18:51:33 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA08613 for hackers-outgoing; Mon, 30 Dec 1996 18:51:33 -0800 (PST) Received: from bios-nt.sunbeach.net (SUNBEACH.NET [205.214.199.134]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA08601 for ; Mon, 30 Dec 1996 18:51:27 -0800 (PST) Received: from bios-nt.sunbeach.net by bios-nt.sunbeach.net (NTMail 3.02.11) with ESMTP id ca085490 for ; Mon, 30 Dec 1996 22:50:04 -0400 Message-ID: <32C87FC1.41C67EA6@sunbeach.net> Date: Mon, 30 Dec 1996 22:51:45 -0400 From: Sean Batson X-Mailer: Mozilla 3.0 (X11; I; BSDI BSD/OS 2.1.5-RELEASE i386) MIME-Version: 1.0 To: hackers@freebsd.org Subject: Shutdown tip Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The next time you guys are about to shutdown try this: shutdown -h now;exit the above command should be done once all of the users are logged off. The end results would always be this: syncing ...disk press anykey to reboot. no buffers to rewrite to the filesystem. Just do an ordernary shutdown -h now, you'll get the usual syncing ..3 4 disk ,... How if someone where modify the code for the shutdown command to do a root user logout then fork or spawn the rest of the code for the shutdown thus avoiding the site of the buffer related numbers each time on a shutdown. Sean Batson. From owner-freebsd-hackers Mon Dec 30 18:53:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA08818 for hackers-outgoing; Mon, 30 Dec 1996 18:53:52 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA08807 for ; Mon, 30 Dec 1996 18:53:49 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id TAA01346; Mon, 30 Dec 1996 19:44:14 -0700 From: Terry Lambert Message-Id: <199612310244.TAA01346@phaeton.artisoft.com> Subject: Re: ipretard.c selective tcp/ip queues and throughput limiters To: avalon@coombs.anu.edu.au (Darren Reed) Date: Mon, 30 Dec 1996 19:44:14 -0700 (MST) Cc: terry@lambert.org, julian@whistle.com, luigi@labinfo.iet.unipi.it, proff@iq.org, danny@panda.hilink.com.au, hackers@freebsd.org In-Reply-To: <199612290827.BAA00338@coyote.Artisoft.COM> from "Darren Reed" at Dec 29, 96 07:26:43 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > This is what I've been calling "layering problems". It is definitely > > a goal of mine to allow a module to be debugged in user space with a > > source level debugger. > > Making code that compiles in the kernel also compile for user programs > is tricky if you only want _one_ routine for both. I beg to disagree... PIC objects don't care whose address space they are loaded or copied into... code is relatively addressed and doesn't really care post-relocation if the relocation was by way of ld -A or by way of dlopen. Anyway... Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-hackers Mon Dec 30 19:28:48 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA11355 for hackers-outgoing; Mon, 30 Dec 1996 19:28:48 -0800 (PST) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id TAA11348 for ; Mon, 30 Dec 1996 19:28:45 -0800 (PST) Received: from misery.sdf.com [204.244.213.33] by misery.sdf.com with smtp (Exim 1.59 #1) id 0veusW-0007kO-00; Mon, 30 Dec 1996 19:28:37 -0800 Date: Mon, 30 Dec 1996 19:28:36 -0800 (PST) From: Tom Samplonius To: Sean Batson cc: hackers@freebsd.org Subject: Re: Shutdown tip In-Reply-To: <32C87FC1.41C67EA6@sunbeach.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 30 Dec 1996, Sean Batson wrote: > The next time you guys are about to shutdown try this: > > shutdown -h now;exit > > the above command should be done once all of the users > are logged off. The end results would always be this: > > syncing ...disk > press anykey to reboot. > no buffers to rewrite to the filesystem. > > Just do an ordernary shutdown -h now, you'll get the > usual syncing ..3 4 disk ,... > > How if someone where modify the code for the shutdown > command to do a root user logout then fork or spawn > the rest of the code for the shutdown thus avoiding > the site of the buffer related numbers each time on > a shutdown. > > > Sean Batson. What difference does it make? You will see buffers written to disk if some other process was active also. Tom From owner-freebsd-hackers Mon Dec 30 20:24:20 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA13905 for hackers-outgoing; Mon, 30 Dec 1996 20:24:20 -0800 (PST) Received: from calvino.alaska.net (root@calvino.alaska.net [206.149.65.3]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA13900 for ; Mon, 30 Dec 1996 20:24:15 -0800 (PST) Received: from calvino.alaska.net (hmmm@calvino.alaska.net [206.149.65.3]) by calvino.alaska.net (8.8.0/8.7.3) with SMTP id TAA14530; Mon, 30 Dec 1996 19:06:54 -0900 (AKST) Date: Mon, 30 Dec 1996 19:06:52 -0900 (AKST) From: hmmm To: Bruce Evans cc: hackers@freebsd.org Subject: Re: Ints In-Reply-To: <199612302312.KAA13090@godzilla.zeta.org.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 31 Dec 1996, Bruce Evans wrote: > >IE - are any interrupt functions/bits LATCHED - that may need to be > They are not latched by ISA hardware. They are latched by FreeBSD > software, except for some serial interrupts. ok - but since ---I--- am the ISR - i would know about any interrupt conditions before FreeBSD ... right? anyway - i have this on my own OS that doesn't care ... > >for example - i have both COM ports tied to the same ISR - is there any > >danger in reading RxBuf1 (lower priority) while SERVICING an RxBuf2 INT? > There is extreme danger of this not working at all, for other reasons - > ISA hardware doesn't support sharing interrupts (at the same time). this i have heard - but cannot comprehend! the UART will activate its IRQ - negotiate with the PIC - and when the PIC acks everything it INTerrupts the CPU to picks up a vector in RAM to jump to ... who cares if the address is the same ISR or not ??? i don't understand! :) From owner-freebsd-hackers Mon Dec 30 20:29:35 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA14061 for hackers-outgoing; Mon, 30 Dec 1996 20:29:35 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA14042; Mon, 30 Dec 1996 20:29:31 -0800 (PST) Received: from time.cdrom.com (localhost [127.0.0.1]) by time.cdrom.com (8.8.4/8.6.9) with ESMTP id UAA13397; Mon, 30 Dec 1996 20:29:08 -0800 (PST) To: Michael Smith cc: roberto@keltia.freenix.fr (Ollivier Robert), freebsd-hackers@FreeBSD.ORG, config@FreeBSD.ORG Subject: Re: IPCS Utility In-reply-to: Your message of "Tue, 31 Dec 1996 11:02:26 +1030." <199612310032.LAA08271@genesis.atrad.adelaide.edu.au> Date: Mon, 30 Dec 1996 20:29:08 -0800 Message-ID: <13393.852006548@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > - We will be using Tcl for parts of the FCF (FreeBSD Config Facility), not > least because I expect to be writing slabs of the core. > ... > The planned modular design of the FCF specifically avoids stipulating > any given language for modules; if you feel the need to write your > module in Forth, as long as you can manage character I/O you can play. Do we have an actual design for the FCF which goes so far as to define such a level of interface spec? It sounds like you've got something hammered out, but I'm not sure if I've seen it yet. :-) Jordan From owner-freebsd-hackers Mon Dec 30 20:36:15 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA14276 for hackers-outgoing; Mon, 30 Dec 1996 20:36:15 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA14267 for ; Mon, 30 Dec 1996 20:36:02 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id PAA22028; Tue, 31 Dec 1996 15:31:59 +1100 Date: Tue, 31 Dec 1996 15:31:59 +1100 From: Bruce Evans Message-Id: <199612310431.PAA22028@godzilla.zeta.org.au> To: bde@zeta.org.au, hmmm@alaska.net Subject: Re: Ints Cc: hackers@freebsd.org Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> >for example - i have both COM ports tied to the same ISR - is there any >> >danger in reading RxBuf1 (lower priority) while SERVICING an RxBuf2 INT? > >> There is extreme danger of this not working at all, for other reasons - >> ISA hardware doesn't support sharing interrupts (at the same time). > >this i have heard - but cannot comprehend! the UART will activate its IRQ >- negotiate with the PIC - and when the PIC acks everything it >INTerrupts the CPU to picks up a vector in RAM to jump to ... >who cares if the address is the same ISR or not ??? >i don't understand! :) The hardware doesn't work like that. The UARTs fight for the IRQ. When one attempts to drive it high, the other is usually attempting to drive it low. The other usually wins. Bruce From owner-freebsd-hackers Mon Dec 30 20:40:45 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA14454 for hackers-outgoing; Mon, 30 Dec 1996 20:40:45 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA14437; Mon, 30 Dec 1996 20:40:39 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id PAA09696; Tue, 31 Dec 1996 15:10:18 +1030 (CST) From: Michael Smith Message-Id: <199612310440.PAA09696@genesis.atrad.adelaide.edu.au> Subject: Re: IPCS Utility In-Reply-To: <13393.852006548@time.cdrom.com> from "Jordan K. Hubbard" at "Dec 30, 96 08:29:08 pm" To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Tue, 31 Dec 1996 15:10:17 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, roberto@keltia.freenix.fr, freebsd-hackers@FreeBSD.ORG, config@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jordan K. Hubbard stands accused of saying: > > - We will be using Tcl for parts of the FCF (FreeBSD Config Facility), not > > least because I expect to be writing slabs of the core. > > ... > > The planned modular design of the FCF specifically avoids stipulating > > any given language for modules; if you feel the need to write your > > module in Forth, as long as you can manage character I/O you can play. > > Do we have an actual design for the FCF which goes so far as to define > such a level of interface spec? It sounds like you've got something > hammered out, but I'm not sure if I've seen it yet. :-) Er, not in so many words, no. We have months of off-and-on discussions on the topic, and I have this large hazy model in my head which I hope to crystallise in the "config manifesto" I've been talking about. Note the cunning term "planned modular design"; ie. I plan to make the design modular. 8) > Jordan -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Dec 30 21:05:55 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA15134 for hackers-outgoing; Mon, 30 Dec 1996 21:05:55 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA15128 for ; Mon, 30 Dec 1996 21:05:51 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id PAA09948; Tue, 31 Dec 1996 15:34:45 +1030 (CST) From: Michael Smith Message-Id: <199612310504.PAA09948@genesis.atrad.adelaide.edu.au> Subject: Re: Ints In-Reply-To: from hmmm at "Dec 30, 96 07:06:52 pm" To: hmmm@alaska.net (hmmm) Date: Tue, 31 Dec 1996 15:34:44 +1030 (CST) Cc: bde@zeta.org.au, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk hmmm stands accused of saying: > > >for example - i have both COM ports tied to the same ISR - is there any > > >danger in reading RxBuf1 (lower priority) while SERVICING an RxBuf2 INT? I think there is confusion here between ISR and IRQ. You may have one ISR handling both ports, but you must have two IRQs. > > There is extreme danger of this not working at all, for other reasons - > > ISA hardware doesn't support sharing interrupts (at the same time). > > this i have heard - but cannot comprehend! the UART will activate its IRQ > - negotiate with the PIC - and when the PIC acks everything it > INTerrupts the CPU to picks up a vector in RAM to jump to ... > who cares if the address is the same ISR or not ??? > i don't understand! :) The inputs to the PIC are edge-triggered. If one interrupt occurs while another is still asserted, the second is lost, and will prevent any other interrupts from being detected. Most ISA devices also drive their interrupt outputs inactive as well as active, so two devices in different states will fight each other, and apart from the possibility of damage to one or the other, the resultant IRQ signal isn't terribly wonderful from an electrical point of view. You can, to a degree, work around this, but every time you move your feet with the PIC and ISA hardware you open more obscure race conditions. The safest and most reliable base to work from is "never share interrupts". -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Mon Dec 30 21:06:21 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id VAA15162 for hackers-outgoing; Mon, 30 Dec 1996 21:06:21 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id VAA15156 for ; Mon, 30 Dec 1996 21:06:18 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.2/8.7.3) id PAA09961; Tue, 31 Dec 1996 15:36:03 +1030 (CST) From: Michael Smith Message-Id: <199612310506.PAA09961@genesis.atrad.adelaide.edu.au> Subject: Re: Ints In-Reply-To: <199612310431.PAA22028@godzilla.zeta.org.au> from Bruce Evans at "Dec 31, 96 03:31:59 pm" To: bde@zeta.org.au (Bruce Evans) Date: Tue, 31 Dec 1996 15:36:02 +1030 (CST) Cc: hmmm@alaska.net, hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Bruce Evans stands accused of saying: > > The hardware doesn't work like that. The UARTs fight for the IRQ. When > one attempts to drive it high, the other is usually attempting to drive it > low. The other usually wins. You mean "the wrong one ususally wins" 8) > Bruce -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hackers Tue Dec 31 02:35:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id CAA23633 for hackers-outgoing; Tue, 31 Dec 1996 02:35:52 -0800 (PST) Received: from gw.pinewood.nl (gw.pinewood.nl [194.171.50.9]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id CAA23627 for ; Tue, 31 Dec 1996 02:35:49 -0800 (PST) Received: (from smap@localhost) by gw.pinewood.nl (8.6.12/8.6.12) id LAA26774 for ; Tue, 31 Dec 1996 11:35:47 +0100 Received: from pwood1.pinewood.nl(192.168.1.10) by gw.pinewood.nl via smap (V1.3) id sma026772; Tue Dec 31 11:35:31 1996 Received: (from franky@localhost) by pwood1.pinewood.nl (8.7.3/8.6.12) id LAA08553 for freebsd-hackers@freebsd.org; Tue, 31 Dec 1996 11:35:30 +0100 (MET) From: "Frank ten Wolde" Message-Id: <9612311135.ZM8551@pwood1.pinewood.nl> Date: Tue, 31 Dec 1996 11:35:28 +0100 X-Face: 'BsFf8'k.q?J#?|$D*,)/?sRB{woUK&9\5K{ERmT;VTSyNLBb?muLf>b:Pt&VTDw8YCaC]6 C!MRSMr5UNjZLa]fi? X-Return-Receipt-To: franky@pinewood.nl X-Mailer: Z-Mail (3.2.1 10oct95) To: freebsd-hackers@freebsd.org Subject: 2.2-BETA: timezone change for Amsterdam: MET --> CET? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I wondered why the timezone for Europe/Amsterdam (and maybe some others as well) changed from 'MET' to 'CET'. The Netherlands (Amsterdam) has always been in 'MET' and 'MET DST'. -Frank -- ---------------------------------------------------------------------- F.W. ten Wolde (PA3FMT) Pinewood Automation B.V. E-mail: franky@pinewood.nl Kluyverweg 2a Phone: +31-15 2682543 2629 HT Delft From owner-freebsd-hackers Tue Dec 31 03:51:58 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id DAA25262 for hackers-outgoing; Tue, 31 Dec 1996 03:51:58 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id DAA25257 for ; Tue, 31 Dec 1996 03:51:54 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id MAA17460; Tue, 31 Dec 1996 12:51:47 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id MAA29148; Tue, 31 Dec 1996 12:51:47 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id LAA24459; Tue, 31 Dec 1996 11:53:46 +0100 (MET) From: J Wunsch Message-Id: <199612311053.LAA24459@uriah.heep.sax.de> Subject: Re: 2.2-BETA: timezone change for Amsterdam: MET --> CET? To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 31 Dec 1996 11:53:46 +0100 (MET) Cc: franky@pinewood.nl (Frank ten Wolde) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9612311135.ZM8551@pwood1.pinewood.nl> from Frank ten Wolde at "Dec 31, 96 11:35:28 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Frank ten Wolde wrote: > I wondered why the timezone for Europe/Amsterdam (and maybe some others > as well) changed from 'MET' to 'CET'. > The Netherlands (Amsterdam) has always been in 'MET' and 'MET DST'. Complain at tz@elsie.nci.nih.gov about this. I did, but they still believe that it's a Good Thing to change a timezone name after about 10 years of actual use. They tell that CET were the correct English, but i simply don't debate about this. I only debate about it being foolish to try changing it now. If MET is inappropriate, they should have changed it at least some five years ago, now it's IMHO too late. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Dec 31 04:46:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id EAA27105 for hackers-outgoing; Tue, 31 Dec 1996 04:46:24 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id EAA27098 for ; Tue, 31 Dec 1996 04:46:21 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id NAA21328 for ; Tue, 31 Dec 1996 13:46:19 +0100 Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id NAA29771 for freebsd-hackers@freebsd.org; Tue, 31 Dec 1996 13:46:18 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.4/8.6.9) id NAA24824 for freebsd-hackers@freebsd.org; Tue, 31 Dec 1996 13:39:24 +0100 (MET) From: J Wunsch Message-Id: <199612311239.NAA24824@uriah.heep.sax.de> Subject: Re: cvs commit: src/usr.bin/vi Makefile To: freebsd-hackers@freebsd.org (FreeBSD hackers) Date: Tue, 31 Dec 1996 13:39:24 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <9987.852019784@critter.dk.tfs.com> from Poul-Henning Kamp at "Dec 31, 96 09:09:44 am" X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E X-Mailer: ELM [version 2.4ME+ PL17 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (Moved to -hackers) As Poul-Henning Kamp wrote: > ("text-processing" is another that springs to mind if catman works now.) catman works, but of course, in order to _run_ catman, you need Perl. :) But then, you also need the `text-processing' subset for it as well. The catman distribution is just there for those people who will never upgrade their manpage sources, so they never need to reformat them. While the transparent update was good for fast machines, it can take a tremendous amount of time for a slower one. Well, OTOH, we also need to install X11 and ports/packages catpages then. Otherwise, troff won't be optional still... :-( I think, most people will end up with the full set of binaries anyway. Only people with 100 MB or smaller disks will think about the bloat. At a time where you can't even buy a disk smaller than 1 GB, we should probably not waste too much energy in too much splitting. > How about adding a src/perl directory tree along the lines of src/gnu ? src/tcl, too. :-) But hey!, then you have to provide four different binaries for `vi', did you realize this? One vi without anything, one with Tcl, one with Perl, one with both. Do you see where the problems arise, and why i said we should probably not waste too much time? > And just make absolutely damn sure it truly is optional, ie: no perl > in /etc/rc and so on. And no Tcl in sysinstall? And no compiler at all? => We start thinking about .o/.a file only kernel dists? And how do we handle kernel options then? There's already one system doing it this way, since they didn't want to hand out the sources... They ended up with a fairly bloated and often slow kernel in SysV. ISTR that people suspected they've also built a kitchensink in... Get me right: i don't have any argument about splitting, or keeping the required minimum low. However, developer's time is the scarcest resource in our project, and we should not waste it too much. If Tcl or Perl save us 50 % development time for some particular purpose, then by all means, use that. The diskspace is much cheaper than that wasted time! Well, it's already afternoon here in Europe, i'll be off for the Silvester party now... Happy New Year everybody! -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-hackers Tue Dec 31 09:20:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA08003 for hackers-outgoing; Tue, 31 Dec 1996 09:20:41 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id JAA07988 for ; Tue, 31 Dec 1996 09:20:39 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA22951; Tue, 31 Dec 1996 12:20:07 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 31 Dec 1996 12:20 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id JAA01940 for ; Tue, 31 Dec 1996 09:46:00 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id JAA02530 for freebsd-hackers@freefall.cdrom.com; Tue, 31 Dec 1996 09:49:18 -0500 (EST) Date: Tue, 31 Dec 1996 09:49:18 -0500 (EST) From: Thomas David Rivers Message-Id: <199612311449.JAA02530@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers Subject: CHECKSUM.MD5 values for 2.2-BETA (they seem to have gone missing.) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I'm in the process of piece-meal downloading 2.2-BETA. Every now-and-then, I like to make sure I'm getting the right bits, and need something to check against. I was wondering if we should provide the MD5 checksums in each of the sub-directories; or a single file somewhere to validate downloads. The CHECKSUM.MD5 files were present in 2.1.6(.1) - but they don't seem to be there in 2.2-BETA (in either the 'bin' or 'src' subdirectories.) Is there now a new/improved mechanism for addressing this problem? Problems I typically encounter are not related to bad bits as much as missing files... so, a file list, if nothing else; would be appreciated. Now - you should ask "why don't you just get 2.2-BETA.tar; you'd know then that you had everything." Well - I usually try that, but it seems ftp.freebsd.org isn't "connected" long enough to get it moved down (about 6 hours, I'd guess) - after a large chunk is transferred, I inevitably get a message from ftp saying the remote service is no longer available. So, then, I extract the large chunk and try to make up the difference, which is why some files have the potential to go missing. I did stumble into the "*.inf" files - have these replaced the CHECKSUM.MD5? They seem to use the older (non MD5) checksum... not that it would really matter... Also, the "*.inf" files don't describe every file in the directory; only the files that are part of the distribution (i.e. "install.sh" wouldn't be listed in "bin.inf"). So, it still doesn't tell me if I've left something behind. - Thanks - - Dave Rivers - From owner-freebsd-hackers Tue Dec 31 09:46:07 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id JAA09450 for hackers-outgoing; Tue, 31 Dec 1996 09:46:07 -0800 (PST) Received: from news.toplink.net (news.toplink.net [194.163.120.7]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id JAA09441 for ; Tue, 31 Dec 1996 09:46:04 -0800 (PST) Received: (from daemon@localhost) by news.toplink.net (8.7.5/8.7.3) id SAA19587; Tue, 31 Dec 1996 18:46:48 +0100 (MET) To: freebsd-hackers@freebsd.org Path: mail2news From: ponds!rivers@dg-rtp.dg.com (Thomas David Rivers) Newsgroups: list.freebsd.hackers Subject: CHECKSUM.MD5 values for 2.2-BETA (they seem to have gone missing.) Date: 31 Dec 1996 18:46:46 +0100 Organization: TopLink mail2news gateway Lines: 35 Message-ID: <199612311449.JAA02530@lakes.water.net> Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm in the process of piece-meal downloading 2.2-BETA. Every now-and-then, I like to make sure I'm getting the right bits, and need something to check against. I was wondering if we should provide the MD5 checksums in each of the sub-directories; or a single file somewhere to validate downloads. The CHECKSUM.MD5 files were present in 2.1.6(.1) - but they don't seem to be there in 2.2-BETA (in either the 'bin' or 'src' subdirectories.) Is there now a new/improved mechanism for addressing this problem? Problems I typically encounter are not related to bad bits as much as missing files... so, a file list, if nothing else; would be appreciated. Now - you should ask "why don't you just get 2.2-BETA.tar; you'd know then that you had everything." Well - I usually try that, but it seems ftp.freebsd.org isn't "connected" long enough to get it moved down (about 6 hours, I'd guess) - after a large chunk is transferred, I inevitably get a message from ftp saying the remote service is no longer available. So, then, I extract the large chunk and try to make up the difference, which is why some files have the potential to go missing. I did stumble into the "*.inf" files - have these replaced the CHECKSUM.MD5? They seem to use the older (non MD5) checksum... not that it would really matter... Also, the "*.inf" files don't describe every file in the directory; only the files that are part of the distribution (i.e. "install.sh" wouldn't be listed in "bin.inf"). So, it still doesn't tell me if I've left something behind. - Thanks - - Dave Rivers - From owner-freebsd-hackers Tue Dec 31 10:12:24 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA11009 for hackers-outgoing; Tue, 31 Dec 1996 10:12:24 -0800 (PST) Received: from news.toplink.net (news.toplink.net [194.163.120.7]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA11001 for ; Tue, 31 Dec 1996 10:12:18 -0800 (PST) Received: (from daemon@localhost) by news.toplink.net (8.7.5/8.7.3) id TAA20106; Tue, 31 Dec 1996 19:13:03 +0100 (MET) To: freebsd-hackers@freebsd.org Path: mail2news From: ponds!rivers@dg-rtp.dg.com (Thomas David Rivers) Newsgroups: list.freebsd.hackers Subject: CHECKSUM.MD5 values for 2.2-BETA (they seem to have gone missing.) Date: 31 Dec 1996 19:13:02 +0100 Organization: TopLink mail2news gateway Lines: 35 Message-ID: <199612311449.JAA02530@lakes.water.net> Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm in the process of piece-meal downloading 2.2-BETA. Every now-and-then, I like to make sure I'm getting the right bits, and need something to check against. I was wondering if we should provide the MD5 checksums in each of the sub-directories; or a single file somewhere to validate downloads. The CHECKSUM.MD5 files were present in 2.1.6(.1) - but they don't seem to be there in 2.2-BETA (in either the 'bin' or 'src' subdirectories.) Is there now a new/improved mechanism for addressing this problem? Problems I typically encounter are not related to bad bits as much as missing files... so, a file list, if nothing else; would be appreciated. Now - you should ask "why don't you just get 2.2-BETA.tar; you'd know then that you had everything." Well - I usually try that, but it seems ftp.freebsd.org isn't "connected" long enough to get it moved down (about 6 hours, I'd guess) - after a large chunk is transferred, I inevitably get a message from ftp saying the remote service is no longer available. So, then, I extract the large chunk and try to make up the difference, which is why some files have the potential to go missing. I did stumble into the "*.inf" files - have these replaced the CHECKSUM.MD5? They seem to use the older (non MD5) checksum... not that it would really matter... Also, the "*.inf" files don't describe every file in the directory; only the files that are part of the distribution (i.e. "install.sh" wouldn't be listed in "bin.inf"). So, it still doesn't tell me if I've left something behind. - Thanks - - Dave Rivers - From owner-freebsd-hackers Tue Dec 31 10:27:03 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA11807 for hackers-outgoing; Tue, 31 Dec 1996 10:27:03 -0800 (PST) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA11802 for ; Tue, 31 Dec 1996 10:27:00 -0800 (PST) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.8.2/8.8.2) with SMTP id KAA24256; Tue, 31 Dec 1996 10:23:44 -0800 (PST) Message-ID: <32C959EA.41C67EA6@whistle.com> Date: Tue, 31 Dec 1996 10:22:34 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Joerg Wunsch CC: hackers@freebsd.org Subject: Re: Iomega SCSI Zip Drive References: <199612310942.KAA23729@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Joao Carlos Mendes Luis wrote: > > > // I'll append you the patch to teach FreeBSD 2.1.5/2.1.6 (i hope it > > // works for both) about the ``SCSI type override'' code. This is an > > > > IT WORKS !!! > > > > Now I can use my ZIP drive without any warning about disk change, > > disk slices, etc. It's boringly silent. :) > > > > Probably should this be default in 2.2. It would help a lot those > > who don't know how to or can't compile a kernel. > > Well, what do other people think about such a change? > > I'll Cc freebsd-core on this, since i won't decide this myself. > Background for `core': my suggested patch would move the Iomega Zip > drives to the `od' driver since this one is better targeted towards > removable media devices. > what is unfixable in the sd drive? it SHOULD be able to handle these.. From owner-freebsd-hackers Tue Dec 31 10:32:52 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA12287 for hackers-outgoing; Tue, 31 Dec 1996 10:32:52 -0800 (PST) Received: from news.toplink.net (news.toplink.net [194.163.120.7]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA12261 for ; Tue, 31 Dec 1996 10:32:34 -0800 (PST) Received: (from daemon@localhost) by news.toplink.net (8.7.5/8.7.3) id TAA20462; Tue, 31 Dec 1996 19:33:18 +0100 (MET) To: freebsd-hackers@freebsd.org Path: mail2news From: ponds!rivers@dg-rtp.dg.com (Thomas David Rivers) Newsgroups: list.freebsd.hackers Subject: CHECKSUM.MD5 values for 2.2-BETA (they seem to have gone missing.) Date: 31 Dec 1996 19:33:18 +0100 Organization: TopLink mail2news gateway Lines: 35 Message-ID: <199612311449.JAA02530@lakes.water.net> Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm in the process of piece-meal downloading 2.2-BETA. Every now-and-then, I like to make sure I'm getting the right bits, and need something to check against. I was wondering if we should provide the MD5 checksums in each of the sub-directories; or a single file somewhere to validate downloads. The CHECKSUM.MD5 files were present in 2.1.6(.1) - but they don't seem to be there in 2.2-BETA (in either the 'bin' or 'src' subdirectories.) Is there now a new/improved mechanism for addressing this problem? Problems I typically encounter are not related to bad bits as much as missing files... so, a file list, if nothing else; would be appreciated. Now - you should ask "why don't you just get 2.2-BETA.tar; you'd know then that you had everything." Well - I usually try that, but it seems ftp.freebsd.org isn't "connected" long enough to get it moved down (about 6 hours, I'd guess) - after a large chunk is transferred, I inevitably get a message from ftp saying the remote service is no longer available. So, then, I extract the large chunk and try to make up the difference, which is why some files have the potential to go missing. I did stumble into the "*.inf" files - have these replaced the CHECKSUM.MD5? They seem to use the older (non MD5) checksum... not that it would really matter... Also, the "*.inf" files don't describe every file in the directory; only the files that are part of the distribution (i.e. "install.sh" wouldn't be listed in "bin.inf"). So, it still doesn't tell me if I've left something behind. - Thanks - - Dave Rivers - From owner-freebsd-hackers Tue Dec 31 10:47:57 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA13237 for hackers-outgoing; Tue, 31 Dec 1996 10:47:57 -0800 (PST) Received: from news.toplink.net (news.toplink.net [194.163.120.7]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA13226 for ; Tue, 31 Dec 1996 10:47:48 -0800 (PST) Received: (from daemon@localhost) by news.toplink.net (8.7.5/8.7.3) id TAA20776; Tue, 31 Dec 1996 19:48:20 +0100 (MET) To: freebsd-hackers@freebsd.org Path: mail2news From: julian@whistle.com (Julian Elischer) Newsgroups: list.freebsd.hackers Subject: Re: Iomega SCSI Zip Drive Date: 31 Dec 1996 19:48:18 +0100 Organization: Whistle Communications Lines: 24 Message-ID: <32C959EA.41C67EA6@whistle.com> References: <199612310942.KAA23729@uriah.heep.sax.de> MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > > As Joao Carlos Mendes Luis wrote: > > > // I'll append you the patch to teach FreeBSD 2.1.5/2.1.6 (i hope it > > // works for both) about the ``SCSI type override'' code. This is an > > > > IT WORKS !!! > > > > Now I can use my ZIP drive without any warning about disk change, > > disk slices, etc. It's boringly silent. :) > > > > Probably should this be default in 2.2. It would help a lot those > > who don't know how to or can't compile a kernel. > > Well, what do other people think about such a change? > > I'll Cc freebsd-core on this, since i won't decide this myself. > Background for `core': my suggested patch would move the Iomega Zip > drives to the `od' driver since this one is better targeted towards > removable media devices. > what is unfixable in the sd drive? it SHOULD be able to handle these.. From owner-freebsd-hackers Tue Dec 31 10:56:41 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id KAA13880 for hackers-outgoing; Tue, 31 Dec 1996 10:56:41 -0800 (PST) Received: from news.toplink.net (news.toplink.net [194.163.120.7]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id KAA13872 for ; Tue, 31 Dec 1996 10:56:36 -0800 (PST) Received: (from daemon@localhost) by news.toplink.net (8.7.5/8.7.3) id TAA20985; Tue, 31 Dec 1996 19:57:14 +0100 (MET) To: freebsd-hackers@freebsd.org Path: mail2news From: ponds!rivers@dg-rtp.dg.com (Thomas David Rivers) Newsgroups: list.freebsd.hackers Subject: CHECKSUM.MD5 values for 2.2-BETA (they seem to have gone missing.) Date: 31 Dec 1996 19:57:12 +0100 Organization: TopLink mail2news gateway Lines: 35 Message-ID: <199612311449.JAA02530@lakes.water.net> Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm in the process of piece-meal downloading 2.2-BETA. Every now-and-then, I like to make sure I'm getting the right bits, and need something to check against. I was wondering if we should provide the MD5 checksums in each of the sub-directories; or a single file somewhere to validate downloads. The CHECKSUM.MD5 files were present in 2.1.6(.1) - but they don't seem to be there in 2.2-BETA (in either the 'bin' or 'src' subdirectories.) Is there now a new/improved mechanism for addressing this problem? Problems I typically encounter are not related to bad bits as much as missing files... so, a file list, if nothing else; would be appreciated. Now - you should ask "why don't you just get 2.2-BETA.tar; you'd know then that you had everything." Well - I usually try that, but it seems ftp.freebsd.org isn't "connected" long enough to get it moved down (about 6 hours, I'd guess) - after a large chunk is transferred, I inevitably get a message from ftp saying the remote service is no longer available. So, then, I extract the large chunk and try to make up the difference, which is why some files have the potential to go missing. I did stumble into the "*.inf" files - have these replaced the CHECKSUM.MD5? They seem to use the older (non MD5) checksum... not that it would really matter... Also, the "*.inf" files don't describe every file in the directory; only the files that are part of the distribution (i.e. "install.sh" wouldn't be listed in "bin.inf"). So, it still doesn't tell me if I've left something behind. - Thanks - - Dave Rivers - From owner-freebsd-hackers Tue Dec 31 11:02:39 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA14270 for hackers-outgoing; Tue, 31 Dec 1996 11:02:39 -0800 (PST) Received: from fallout.campusview.indiana.edu (fallout.campusview.indiana.edu [149.159.1.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA14265 for ; Tue, 31 Dec 1996 11:02:37 -0800 (PST) Received: from localhost (jfieber@localhost) by fallout.campusview.indiana.edu (8.8.4/8.8.4) with SMTP id OAA00364 for ; Tue, 31 Dec 1996 14:02:35 -0500 (EST) Date: Tue, 31 Dec 1996 14:02:35 -0500 (EST) From: John Fieber To: hackers@freebsd.org Subject: New motherboard breaks tape drive Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have an Archive Viper 150 tape drive that has served me well for many years. I have never had difficulty getting the maximum performance of about 100K/second writing speed from it... ...until upgrade my old 486DX33 motherboard to a Pentium 100 (ASUS). Now the tape drive will no longer stream and typical writing speed has dropped to about 50K/second. My first thought was something with the new SCSI controller (ASUS SC200) was the problem so I put my old Adaptec 1542C in, but the result was the same (I even tried putting the drive alone on the bus). I tried team, but it didn't help. I'm fishing for where to look next. Ideas? -john From owner-freebsd-hackers Tue Dec 31 11:17:18 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA15154 for hackers-outgoing; Tue, 31 Dec 1996 11:17:18 -0800 (PST) Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA15149 for ; Tue, 31 Dec 1996 11:17:13 -0800 (PST) Received: from gateway.cybernet.com (gateway.cybernet.com [192.245.33.1]) by gateway.cybernet.com (8.7.6/8.7.3) with SMTP id OAA14039; Tue, 31 Dec 1996 14:26:01 -0500 (EST) Date: Tue, 31 Dec 1996 14:25:54 -0500 (EST) From: "Mark J. Taylor" To: Thomas David Rivers cc: hackers@freebsd.org Subject: Re: CHECKSUM.MD5 values for 2.2-BETA (they seem to have gone missing.) In-Reply-To: <199612311449.JAA02530@lakes.water.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I remember several years back that people were complaining about how long it takes to do a checksum during the installation, so putting it back in would probably be a bad idea. However, putting the MD5 checksums in and optionally NOT using them during installation sounds like a good idea (it would be a nice little security feture, put into sysinstall's "options" screen). On Tue, 31 Dec 1996, Thomas David Rivers wrote: > > I'm in the process of piece-meal downloading 2.2-BETA. Every now-and-then, > I like to make sure I'm getting the right bits, and need something to > check against. > > I was wondering if we should provide the MD5 checksums in each of the > sub-directories; or a single file somewhere to validate downloads. > > The CHECKSUM.MD5 files were present in 2.1.6(.1) - but they don't > seem to be there in 2.2-BETA (in either the 'bin' or 'src' subdirectories.) > > Is there now a new/improved mechanism for addressing this problem? > > Problems I typically encounter are not related to bad bits as much > as missing files... so, a file list, if nothing else; would be appreciated. > > Now - you should ask "why don't you just get 2.2-BETA.tar; you'd know > then that you had everything." Well - I usually try that, but it seems > ftp.freebsd.org isn't "connected" long enough to get it moved down > (about 6 hours, I'd guess) - after a large chunk is transferred, I > inevitably get a message from ftp saying the remote service is no > longer available. So, then, I extract the large chunk and try to > make up the difference, which is why some files have the potential to > go missing. > > I did stumble into the "*.inf" files - have these replaced the CHECKSUM.MD5? > They seem to use the older (non MD5) checksum... not that it would really > matter... Also, the "*.inf" files don't describe every file in the > directory; only the files that are part of the distribution (i.e. "install.sh" > wouldn't be listed in "bin.inf"). So, it still doesn't tell me if > I've left something behind. > > - Thanks - > - Dave Rivers - > > From owner-freebsd-hackers Tue Dec 31 11:41:49 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA16348 for hackers-outgoing; Tue, 31 Dec 1996 11:41:49 -0800 (PST) Received: from mail.blake.net (mail.blake.net [156.46.84.75]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id LAA16342 for ; Tue, 31 Dec 1996 11:41:45 -0800 (PST) Received: from Wizard.featherlitemfg.com (156.46.103.26) by mail.blake.net with SMTP (Apple Internet Mail Server 1.0); Tue, 31 Dec 1996 13:42:32 -0500 Message-ID: <32C96C9A.332A@blake.net> Date: Tue, 31 Dec 1996 13:42:18 -0600 From: Carl Blake Reply-To: Carl@blake.net X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: freebsd-hackers@freefall.FreeBSD.org Subject: Quick Question Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, Can you recall the name of a formatter that I can use to format my disk or FreeBSD and leave windows on it. I think there was one out there that allowed me to format the disk as long as it was one big parition. But I cannot remember the name of it. Thanks Carl From owner-freebsd-hackers Tue Dec 31 11:55:08 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id LAA18024 for hackers-outgoing; Tue, 31 Dec 1996 11:55:08 -0800 (PST) Received: from toplink1.toplink.net (toplink1.toplink.net [194.163.120.1]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id LAA17979; Tue, 31 Dec 1996 11:54:57 -0800 (PST) Received: (from ck@localhost) by toplink1.toplink.net (8.6.12/8.6.12) id UAA25226; Tue, 31 Dec 1996 20:52:52 +0100 From: Christian Kratzer Message-Id: <199612311952.UAA25226@toplink1.toplink.net> Subject: dupes in the list To: freebsd-hackers@freebsd.org, freebsd-isp@freebsd.org, freebsd-questions@freebsd.org Date: Tue, 31 Dec 1996 20:52:52 +0100 (MET) X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, sorry for the duplicates that just appeared in the lists. I screwed up our mail2news gateway. I'm tailing the news server maillog and will stop the thing if it sends out any further dupes ;( Sorry ;( Christian -- TopLink GbR, Internet Services info@toplink.net Christian Kratzer http://www.toplink.net/ Phone: +49 7452 885-0 Fax: +49 7452 885-199 FreeBSD spoken here! From owner-freebsd-hackers Tue Dec 31 12:54:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id MAA20796 for hackers-outgoing; Tue, 31 Dec 1996 12:54:06 -0800 (PST) Received: from itchy.atlas.com ([206.29.170.230]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id MAA20790 for ; Tue, 31 Dec 1996 12:54:02 -0800 (PST) Received: (from brantk@localhost) by itchy.atlas.com (8.8.0/8.8.0) id MAA03529; Tue, 31 Dec 1996 12:56:48 -0800 (PST) Message-Id: <199612312056.MAA03529@itchy.atlas.com> Subject: Re: New motherboard breaks tape drive To: jfieber@indiana.edu (John Fieber) Date: Tue, 31 Dec 1996 12:56:47 -0800 (PST) Cc: hackers@freebsd.org Reply-To: bmk@pobox.com In-Reply-To: from John Fieber at "Dec 31, 96 02:02:35 pm" From: "Brant Katkansky" Reply-To: bmk@pobox.com X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I have an Archive Viper 150 tape drive that has served me well > for many years. I have never had difficulty getting the maximum > performance of about 100K/second writing speed from it... > > ...until upgrade my old 486DX33 motherboard to a Pentium 100 > (ASUS). Now the tape drive will no longer stream and typical > writing speed has dropped to about 50K/second. > > My first thought was something with the new SCSI controller (ASUS > SC200) was the problem so I put my old Adaptec 1542C in, but the > result was the same (I even tried putting the drive alone on the > bus). I tried team, but it didn't help. > > I'm fishing for where to look next. Ideas? No ideas, but I'd like to know as well. I have the same exact problem - I'd just forgotten about it since I only do backups about every six months or so. :) -- Brant Katkansky (bmk@pobox.com, brantk@atlas.com) Software Engineer, ADC From owner-freebsd-hackers Tue Dec 31 13:37:53 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id NAA23158 for hackers-outgoing; Tue, 31 Dec 1996 13:37:53 -0800 (PST) Received: from mail.crl.com (mail.crl.com [165.113.1.22]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id NAA23153 for ; Tue, 31 Dec 1996 13:37:46 -0800 (PST) Received: from calvino.alaska.net by mail.crl.com with SMTP id AA04695 (5.65c/IDA-1.5 for ); Tue, 31 Dec 1996 13:37:50 -0800 Received: from calvino.alaska.net (hmmm@calvino.alaska.net [206.149.65.3]) by calvino.alaska.net (8.8.0/8.7.3) with SMTP id MAA13739 for ; Tue, 31 Dec 1996 12:30:42 -0900 (AKST) Date: Tue, 31 Dec 1996 12:30:41 -0900 (AKST) From: hmmm To: freebsd-hackers Subject: Re: Ints (fwd) Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk ------------------------------------------------------------------------------ Sleep: a sign a caffeine deprivation ... http://www.alaska.net/~hmmm ------------------------------------------------------------------------------ ---------- Forwarded message ---------- Received: from CHARLESB (aac-proxy2.mpb.jccbi.gov [162.58.29.160]) by calvino.alaska.net (8.8.0/8.7.3) with SMTP id IAA14915; Tue, 31 Dec 1996 08:48:36 -0900 (AKST) Message-ID: <32C94455.5ACB@admin.tc.faa.gov> Date: Tue, 31 Dec 1996 08:50:29 -0800 From: Charles Bader Organization: Federal Aviation Administration X-Mailer: Mozilla 2.0 (Win16; U) MIME-Version: 1.0 To: hmmm , davidn@sdev.usn.blaze.net.au, trolso_n@motsat.sat.mot.com, tpv@Alaska.NET Subject: Re: Ints References: Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii Content-Length: 2640 hmmm wrote: > > On Tue, 31 Dec 1996, David Nugent wrote: > > > The problem is that the ISA bus is only a binary (two-state) > > bus. Each IRQ has its own physical "line" which is either high > > or low. If two devices drive the IRQ in opposite directions at > > the same time, there's every chance that the PIC won't see it. > > Interrupts are simply lost, so the cpu never sees it to call > > the associated ISR. > > OK - so it comes down to this - Multiple devices CAN share the same IRQ as > long as one device isn't "activating" an IRQ that another is > "de-activating" at the same time - right? > > and the reason a COM1 RxINT & TxINT is different from a COM1 RxINT & COM2 > RxINT is because the COM1 device in the first instance will generate pull > on the same IRQ line in SEQUENCE - ie - not simultaneously as in the > second case ... - right? :) Wait a second guys.... The interrupt lines on the ISA bus are open-collector, which means that it is possible to OR-TIE them together- remember Digital Electronics Fundamentals? Open-collector is very similar to tri-state, and is used when there is only 1 active state. If an application should require multiple devices to share a bus, and 2 active states are required, then tri-state drivers are required on all outputs. The only state which we are concerned with is ACTIVE (low). The processor doesn't care if an interrupt isn't happening, only when one IS. So a peripheral device does not DRIVE the interrupt line "the other way", it simply de-activates it's open-collector output. If another peripheral device happens to have interrupt asserted, the state of the IRQ line will not change. A problem occurs at the tail end of an ISR, when the IF flag is cleared during the IRET instruction. If another interrupt happens to occur since the time you last checked the peripheral's flag register and prior to issuing an IRET, then the PIC will indeed lose the interrupt. The PIC will clear the first interrupt, and in so doing, will also clear the second, since they share the same line. The best solution is to never use the same interrupt line which will be used by any two devices which will be used at the same time. Barring this, it is important to check the status registers of the 2 peripherals prior to exiting the ISR as well as entering it. Problems of this sort involving communications are very difficult to track down, since the triggering event revolves around 2 separate, unsynchronized events. The probability of the second interrupt occurring during this short time frame is very small, but nevertheless will happen sooner or later. From owner-freebsd-hackers Tue Dec 31 14:41:06 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA26450 for hackers-outgoing; Tue, 31 Dec 1996 14:41:06 -0800 (PST) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA26441 for ; Tue, 31 Dec 1996 14:41:01 -0800 (PST) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id JAA15437; Wed, 1 Jan 1997 09:39:44 +1100 Date: Wed, 1 Jan 1997 09:39:44 +1100 From: Bruce Evans Message-Id: <199612312239.JAA15437@godzilla.zeta.org.au> To: hackers@FreeBSD.org, hmmm@alaska.net Subject: Re: Ints (fwd) Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Wait a second guys.... The interrupt lines on the ISA bus are open-collector, which means >that it is possible to OR-TIE them together- remember Digital Electronics Fundamentals? They aren't open-collector. Bruce From owner-freebsd-hackers Tue Dec 31 14:56:29 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id OAA28647 for hackers-outgoing; Tue, 31 Dec 1996 14:56:29 -0800 (PST) Received: from penn.com (root@penn.com [205.146.6.6]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id OAA28633; Tue, 31 Dec 1996 14:56:20 -0800 (PST) Received: from none.Compuserve.com (oport22.penn.com [208.0.122.161]) by penn.com (8.7.3/8.6.12) with SMTP id RAA00661; Tue, 31 Dec 1996 17:55:45 -0500 (EST) Date: Tue, 31 Dec 1996 17:55:45 -0500 (EST) Message-Id: <199612312255.RAA00661@penn.com> X-Sender: jnuytten@pop.penn.com X-Mailer: Windows Eudora Light Version 1.5.2 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: freebsd-questions@freebsd.org, freebsd-hackers@freebsd.org, freebsd-hardware@@freebsd.org From: Jean-Paul Nuytten Subject: Installation Problems Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just acquired FreeBSD from Walnut Creek CDROM along with the book "The Complete FreeBSD" by Greg Lehley. I have 2 EIDE hard drives; 1.2 GB (C:) which contains Windows 95 and 2.6 GB (FreeBSD partition, D:, E:). The FreeBSD partition is within the first 1024 cylinders, D: is a primary DOS partition which starts after the FreeBSD partition and E: is an extented DOS partition. To make matters worse, I have a Promise 2300 EIDE controller. I am trying to install using a DOS partition and have a directory on D: called FREEBSD with the distribution directories under it. After making a FreeBSD bootable diskette and booting the FreeBSD installation procedure (using the Novice installation option) I am have problems loading the distribution. I seem to be reading the distribution from the DOS partition OK, but I am getting write errors "Write failure transferring dists". Secondly, I have an IDE 8X CDROM (it came with the Creative Labs Sound Blaster 32PNP). The book says that I should make a boot floppy using the atapi.flp loader but I can't find that file on my distribution CDROM. Where can I get this file so that I can install from CDROM directly. Thanks in advance for your prompt attention to my questions. Regards, J-P Jean-Paul Nuytten Email: jnuytten@penn.com RD #3, Box 359A Tel: 814-641-0198 Huntingdon, PA USA 16652 FAX: 814-641-0199 From owner-freebsd-hackers Tue Dec 31 17:59:44 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id RAA07278 for hackers-outgoing; Tue, 31 Dec 1996 17:59:44 -0800 (PST) Received: from hemi.com (hemi.com [204.132.158.10]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id RAA07273 for ; Tue, 31 Dec 1996 17:59:41 -0800 (PST) Received: (from mbarkah@localhost) by hemi.com (8.8.4/8.7.3) id SAA12416 for hackers@freebsd.org; Tue, 31 Dec 1996 18:59:40 -0700 (MST) From: Ade Barkah Message-Id: <199701010159.SAA12416@hemi.com> Subject: "commerce" and 2.1.6. To: hackers@freebsd.org Date: Tue, 31 Dec 1996 18:59:40 -0700 (MST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, Has the "commerce" distribution been nuked for 2.1.6 ? I can't seem to find it on wcarchive. Thanks, -Ade ------------------------------------------------------------------- Inet: mbarkah@hemi.com - HEMISPHERE ONLINE - ------------------------------------------------------------------- From owner-freebsd-hackers Tue Dec 31 18:08:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id SAA07615 for hackers-outgoing; Tue, 31 Dec 1996 18:08:26 -0800 (PST) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.4/8.8.4) with SMTP id SAA07599 for ; Tue, 31 Dec 1996 18:08:23 -0800 (PST) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA20406; Tue, 31 Dec 1996 21:07:52 -0500 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Tue, 31 Dec 1996 21:07 EST Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.7.5/8.7.3) with ESMTP id UAA06583; Tue, 31 Dec 1996 20:37:16 -0500 (EST) Received: (from rivers@localhost) by lakes.water.net (8.7.5/8.6.9) id UAA03568; Tue, 31 Dec 1996 20:40:37 -0500 (EST) Date: Tue, 31 Dec 1996 20:40:37 -0500 (EST) From: Thomas David Rivers Message-Id: <199701010140.UAA03568@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!time.cdrom.com!jkh, ponds!lakes.water.net!rivers Subject: Re: CHECKSUM.MD5 values for 2.2-BETA (they seem to have gone missing.) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > The CHECKSUM.MD5 files were present in 2.1.6(.1) - but they don't > > seem to be there in 2.2-BETA (in either the 'bin' or 'src' subdirectories.) > > They're made by hand, so I don't always do them for the intermediate > releases. They should really be added to the installation building > process, so I'll do that soon. Sounds like a dandy idea to me - thanks for explaining that they are done by hand... I can appreciate (readily) how these last-minute hand-operations are bothersome... :-) I think adding it to the building process is an excellent idea - the fewer hand operations the better. [Hopefully, it's not a big job...] Please don't bother doing it for 2.2-BETA; it's not worth it just for me :-) [I can do a "dir" in FTP and just check myself.] > > Jordan - Dave Rivers - From owner-freebsd-hackers Tue Dec 31 19:10:26 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA09657 for hackers-outgoing; Tue, 31 Dec 1996 19:10:26 -0800 (PST) Received: from gaia.coppe.ufrj.br (root@cisigw.coppe.ufrj.br [146.164.2.31]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA09652 for ; Tue, 31 Dec 1996 19:10:22 -0800 (PST) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.3/8.7.3) id BAA12154; Wed, 1 Jan 1997 01:10:14 -0200 (EDT) From: Joao Carlos Mendes Luis Message-Id: <199701010310.BAA12154@gaia.coppe.ufrj.br> Subject: Re: DEVFS strangeness To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 1 Jan 1997 01:10:14 -0200 (EDT) Cc: freebsd-hackers@freebsd.org, randy@zyzzyva.com In-Reply-To: <199612301840.TAA09551@uriah.heep.sax.de> from J Wunsch at "Dec 30, 96 07:40:09 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk #define quoting(J Wunsch) // I think this idea of a unit # is a gross abuse... If i read this // correctly, it would never be possible to put two identical soundcards // into the same machine (on different hardware addresses and interrupt // vectors, i mean)? Humm... I did not care much about, but I could not make a GUS PnP work together with a SB16 in FreeBSD-2.1.6. At Win31 I got 2 independent wave devices working perfectly (not the same luck with midi devices, though). But my problems started at the board probes, during boot. sbxvi and opl3 devices could not be found, and the gus driver did not found a GUS Max, as it usually does. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro From owner-freebsd-hackers Tue Dec 31 20:34:19 1996 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id UAA12755 for hackers-outgoing; Tue, 31 Dec 1996 20:34:19 -0800 (PST) Received: from smtest.usit.net (smtest.usit.net [199.1.48.16]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id UAA12750 for ; Tue, 31 Dec 1996 20:34:17 -0800 (PST) Received: from abyss ([206.29.55.57]) by smtest.usit.net (8.7.5/8.6.12) with SMTP id XAA19125 for ; Tue, 31 Dec 1996 23:42:58 -0500 (EST) Message-ID: <32C9EC2F.533A@usit.net> Date: Tue, 31 Dec 1996 23:46:39 -0500 From: Troy Settle Reply-To: pitlord@usit.net X-Mailer: Mozilla 3.01 (WinNT; I) MIME-Version: 1.0 Newsgroups: comp.unix.bsd.freebsd CC: freebsd-hackers@freebsd.org Subject: booting problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hey all, I'm sick of beating myself up over this, so I'm asking for some help :) I recently installed FreeBSD on a pentium for the first time. Install went great, no problems. I rebooted, put in about 20 hours worth of configuration and package installation. Built a new kernel, and rebooted. Upon booting with the new kernel, booteasy refused to load the kernel, and just kept restarting (not rebooting, just repeatedly giving me the boot: prompt, then timing out, and attempting to load /kernel, failing, then boot: again). If I enter '/kernel' at the boot: prompt, it will load the kernel, but upon initialization, it just hangs. After about 15 minutes, I give up, and give it a 3-finger salute, and boot '/kernel.GENERIC' with no problems. I rebuilt the kernel a few times, and the problem kept repeating itself. I moved the HD off to another system, and all my kernels booted just fine. Does anyone have any suggestions at what I should look at as a possible cause? Any help would be greatly appreciated. Also, while I'm posting, does anyone know if there's a way I can use a generic NE2000 PCI card that insists on sitting at IRQ 12, 0xFF40 ? Thanks in advance, Troy