From owner-freebsd-current Sun Jan 23 1: 2: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id AF21614DD0 for ; Sun, 23 Jan 2000 01:02:02 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id BAA76542; Sun, 23 Jan 2000 01:01:58 -0800 (PST) (envelope-from dillon) Date: Sun, 23 Jan 2000 01:01:58 -0800 (PST) From: Matthew Dillon Message-Id: <200001230901.BAA76542@apollo.backplane.com> To: Wilko Bulte Cc: sthaug@nethelp.no, freebsd-current@FreeBSD.ORG Subject: Re: panic (softupdates??) on yesterdays -current (alpha machine) References: <20000122113407.A54350@yedi.iaf.nl> <58638.948539231@verdi.nethelp.no> <20000122200922.F59196@yedi.iaf.nl> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> sched_sync :> fork_trampoline :> :> This is with ffs_softdep.c 1.56. Matt Dillon has already received a core :> dump, and I believe it's on its way to Kirk McKusick for analysis. : :Thanks for the info. I just got my Alpha running again, and I am now :100% sure it has ffs_softdep.c 1.56 : :Are dumps from an Alpha of any use to Kirk BTW? : :-- :Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project : WWW : http://www.tcja.nl http://www.freebsd.org I'm not sure, I don't think I can gdb an alpha dump on an i386 box. Have you determined yet if softupdates is causing the problem or not? softupdates usually panics when something goes wrong. If you are getting a lockup rather then a panic it may not be softupdates. I've been running continuous buildworlds on my test box for two days so far without any problems. That doesn't necessarily mean the problem is fixed, but it's definitely brownie points. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 1:26:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 831F814F3F for ; Sun, 23 Jan 2000 01:26:49 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id KAA81850; Sun, 23 Jan 2000 10:26:48 +0100 (CET) (envelope-from olli) Date: Sun, 23 Jan 2000 10:26:48 +0100 (CET) Message-Id: <200001230926.KAA81850@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) X-Newsgroups: list.freebsd-current In-Reply-To: <86duop$2n8d$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote in list.freebsd-current: > If I may inject some possibly-irrelevant fact into this > discussion... gzip (or rather, the ``deflate'' compression algorithm > and the libz file format) has been adopted into a number of formal > standards. It's likely that it will remain with us for a long time. > For those of us who eschew bloatware, it continues to be entirely > adequate. I don't like bzip2 for the sole fact that it takes _ages_ to compress files, compared to gzip. Saving 10% or 20% on disk space is not worth wasting >= 10 times more CPU time than gzip. Disk space is cheap nowadays, but upgrading to a CPU that is 10 times faster is not. (I once tried to compress our FreeBSD ISO images with bzip2, just to compare the space savings with gzip. I aborted the experiment after 6 hours (!). gzip took about 30 minutes. Consequently, bzip2 was considered unusable and went into the trash can.) I'd vote for keeping things as they are: bzip2 is fine as a port. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 2:16: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from ms.tokyo.jcom.ne.jp (ms.tokyo.jcom.ne.jp [210.234.123.18]) by hub.freebsd.org (Postfix) with ESMTP id 1CB2A14CA2 for ; Sun, 23 Jan 2000 02:16:01 -0800 (PST) (envelope-from musha@ms.tokyo.jcom.ne.jp) Received: from daemon.local.idaemons.org (pc062018.tokyo.jcom.ne.jp [210.155.62.18]) by ms.tokyo.jcom.ne.jp (8.9.1/3.7W 06/01/99) with ESMTP id TAA17312 for ; Sun, 23 Jan 2000 19:15:59 +0900 (JST) Received: by daemon.local.idaemons.org (8.9.3/3.7W) id TAA80898; Sun, 23 Jan 2000 19:15:27 +0900 (JST) Date: Sun, 23 Jan 2000 19:15:26 +0900 Message-ID: <86u2k5ytz5.wl@localhost.local.idaemons.org> From: Akinori MUSHA aka knu To: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-Reply-To: In your message of "Sun, 23 Jan 2000 10:26:48 +0100 (CET)" <200001230926.KAA81850@dorifer.heim3.tu-clausthal.de> References: <86duop$2n8d$1@atlantis.rz.tu-clausthal.de> <200001230926.KAA81850@dorifer.heim3.tu-clausthal.de> User-Agent: Wanderlust/2.2.15 (More Than Words) EMIKO/1.13.9 (Euglena tripteris) FLIM/1.13.2 (Kasanui) APEL/10.1 MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) Organization: A.I.D. MIME-Version: 1.0 (generated by EMIKO 1.13.9 - "Euglena tripteris") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Sun, 23 Jan 2000 10:26:48 +0100 (CET), Oliver Fromme wrote: > I don't like bzip2 for the sole fact that it takes _ages_ to > compress files, compared to gzip. Saving 10% or 20% on disk > space is not worth wasting >= 10 times more CPU time than gzip. > Disk space is cheap nowadays, but upgrading to a CPU that is > 10 times faster is not. But when one compresses a file with bzip2 and prepare a smaller distribution, hundreds of people can save their download time. That's why we compress things. I'd focus on the receivers' side. Of course a necessary manner is preparing also a gzip'ed file for those who prefer gzip's less memory usage rather than bzip2's higher compression. And still, a standard is a standard. > (I once tried to compress our FreeBSD ISO images with bzip2, > just to compare the space savings with gzip. I aborted the > experiment after 6 hours (!). gzip took about 30 minutes. > Consequently, bzip2 was considered unusable and went into the > trash can.) Not everyone wants/needs to compress such a big stuff with bzip2 to waste time. But having bzip2/bunzip2 gives us an option. > I'd vote for keeping things as they are: bzip2 is fine as > a port. Despite all of above, I have to agree that, since whether having bzip2 is already an option thanks to the port. :) -- / /__ __ / ) ) ) ) / http://www.idaemons.org/knu/ Akinori MUSHA aka / (_ / ( (__( mailto:knu@idaemons.org "We are but hungry.. Associated Ita-meshi Daemons!" http://www.idaemons.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 3:49:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 6378014FDF for ; Sun, 23 Jan 2000 03:49:11 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id LAA09965; Sun, 23 Jan 2000 11:34:21 GMT (envelope-from n_hibma@webweaving.org) Date: Sun, 23 Jan 2000 11:34:21 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Wilko Bulte Cc: Jeroen Ruigrok/Asmodai , FreeBSD CURRENT Mailing List Subject: Re: With feature freeze being in place In-Reply-To: <20000122212851.A60961@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Also, are GENERIC and LINT in sync? > > Do we want a LINT for alpha too? I guess so. I'm in favour of it. We could start of with simply copying GENERIC. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 4:44:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id E5ABF14C35 for ; Sun, 23 Jan 2000 04:44:11 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id MAA03346 for ; Sun, 23 Jan 2000 12:28:29 GMT (envelope-from n_hibma@webweaving.org) Date: Sun, 23 Jan 2000 12:28:29 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List Subject: mmap problem when resuming while mpg123 is playing Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following error shows up in my messages log when mpg123 is playing songs off a mounted CD ROM when the laptop is suspended and resumed. Jan 23 11:21:04 henny /kernel: resumed from suspended mode (slept 00:36:53) Jan 23 11:21:04 henny /kernel: ata0: resetting devices .. done Jan 23 11:21:04 henny /kernel: ata1: resetting devices .. done Jan 23 11:21:04 henny /kernel: vm_fault: pager read error, pid 9309 (mpg123) Jan 23 11:21:04 henny /kernel: pid 9309 (mpg123), uid 0: exited on signal 11 (core dumped) The contents of the cd can no longer be accessed. umount /cdrom does not work, umount -f /cdrom does, but the system later on panics in __getcwd, eventhough I had exitted all the shells (logged out) before doing the forced unmount. After mounting the CD again (before the panic happens) the CD is accessible again. Other relevant parts of the log: Jan 23 12:09:36 henny /kernel: ata-pci0: port 0xf8d0-0xf8df at device 1.1 on pci0 Jan 23 12:09:36 henny /kernel: ata-pci0: Busmastering DMA supported Jan 23 12:09:36 henny /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Jan 23 12:09:36 henny /kernel: ata1 at 0x0170 irq 15 on ata-pci0 ... Jan 23 12:09:37 henny /kernel: ad0: ATA-4 disk at ata0 as master Jan 23 12:09:37 henny /kernel: ad0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S Jan 23 12:09:37 henny /kernel: ad0: 16 secs/int, 1 depth queue, UDMA33 Jan 23 12:09:37 henny /kernel: acd0: CDROM drive at ata1 as master Jan 23 12:09:37 henny /kernel: acd0: read 2416KB/s (2416KB/s), 128KB buffer, PIO4 Jan 23 12:09:37 henny /kernel: acd0: Reads: CD-DA Jan 23 12:09:37 henny /kernel: acd0: Audio: play, 16 volume levels Jan 23 12:09:37 henny /kernel: acd0: Mechanism: ejectable tray Jan 23 12:09:38 henny /kernel: acd0: Medium: no/blank disc inside, unlocked Jan 23 12:09:38 henny /kernel: pccard: card inserted, slot 1 Jan 23 12:09:38 henny /kernel: ata_command: timeout waiting for interrupt Jan 23 12:09:38 henny /kernel: Mounting root from ufs:/dev/ad0s2a -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 5:15:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 660D91510E for ; Sun, 23 Jan 2000 05:15:24 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id OAA08361; Sun, 23 Jan 2000 14:06:04 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id NAA74825; Sun, 23 Jan 2000 13:47:55 +0100 (CET) Date: Sun, 23 Jan 2000 13:47:55 +0100 (CET) From: Juergen Lock Message-Id: <200001231247.NAA74825@saturn.kn-bremen.de> To: dgilbert@velocet.ca Subject: cross-building a kernel (was: On a lighter note... how-to upgrade) X-Newsgroups: local.list.freebsd.current In-Reply-To: <14474.15305.507542.292721@trooper.velocet.net> Organization: home Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <14474.15305.507542.292721@trooper.velocet.net> you write: >I have followed the UPDATES file... and I have source-make-world >upgraded several machines from 3.3 and 3.4 to 4.0-CURRENT recently. I >thought I'd contribute a method that is reasonably likely to work and >reasonably likely to not be going overboard. Someone should maintain >a file like this. > >(generate things needed to make kernel) >make all->install usr.sbin/config >make all->install usr.bin/genassym > >(it appears that a lot of things don't work right until the new kernel > is in place, and it can be installed first) >make 4.0 kernel >reboot with 4.0 kernel >... I recently had to build a -current kernel on -stable too, and ended up with this in the config file: makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols # kernel cross-build... makeoptions CC=gcc295 options __FreeBSD__=4 # needed? options unix options __FreeBSD_cc_version=400003 I don't know if the last two are really needed and the DEBUG of course is optional too, but without the others my kernel wouldn't even build. (I forgot what exactly failed with the old cc, but the __FreeBSD__=4 is necessary for parts that use #ifdefs to decide things like which version of a kernel interface to use, the case of this i saw was in the isdn stuff. Of course this produces redifinition warnings so probably should be done some other way but at least it works... :) Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 5:28:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-27.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.155]) by hub.freebsd.org (Postfix) with ESMTP id C05BC15099; Sun, 23 Jan 2000 05:28:39 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA36877; Sun, 23 Jan 2000 13:03:21 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA01359; Sun, 23 Jan 2000 13:03:19 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001231303.NAA01359@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Warner Losh Cc: obrien@FreeBSD.ORG, Chuck Robey , current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: Message from Warner Losh of "Fri, 21 Jan 2000 22:00:05 MST." <200001220500.WAA17674@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 23 Jan 2000 13:03:19 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <20000121180914.C44132@dragon.nuxi.com> "David O'Brien" writes: > : "load" on the mirror. Where "load" is either one of the connection > : slots, or actual kernel resource load if I have 20% packet loss and thus > : cause a lot of retransmissions to occur. > > Hmmm. A thought just occurred to me. There's no need to measure > these things. Lookup all the IP addresses. Do a non blocking > connection to each of these machines. First one to come back with the > REL16_1 response wins, and all the others get closed and you use that > one. I like this idea, except that some sort of consistency is required - ie, once I've started using cvsupX, I'd like to use it in preference to slightly better machines unless it stays bad for some configurable number of connections.... > Warner -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 6: 5:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 148E1150D7; Sun, 23 Jan 2000 06:05:48 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id OAA08367; Sun, 23 Jan 2000 14:06:04 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id OAA75362; Sun, 23 Jan 2000 14:03:44 +0100 (CET) Date: Sun, 23 Jan 2000 14:03:44 +0100 (CET) From: Juergen Lock Message-Id: <200001231303.OAA75362@saturn.kn-bremen.de> To: chuckr@picnic.mat.net Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) X-Newsgroups: local.list.freebsd.current In-Reply-To: References: <20000122123109.E59732@shadow.blackdawn.com> Organization: home Cc: Will Andrews , Shigeyuki Fukushima , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >... >A case would have to be built that bzip2 does something critical that >cannot be done without bzip2. Else, it stays as a fine port. Heck, emacs >is a fine port too, but it'll never get into the base system. Very true, but i can actually think of one thing were bzip2 would really be useful: to better compress the kernel on install floppies so you could keep more things in it. (like ptys and pass which would make fixit more useful, or pppoe which was thrown out too recently if i'm not mistaken.) Btw you could probably also kgzip the loader, that would free up some space too. Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 6:45:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 61FBE14A0D for ; Sun, 23 Jan 2000 06:45:47 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id PAA18851 for freebsd-current@FreeBSD.ORG; Sun, 23 Jan 2000 15:45:45 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 93E3D8863; Sun, 23 Jan 2000 14:14:13 +0100 (CET) Date: Sun, 23 Jan 2000 14:14:13 +0100 From: Ollivier Robert To: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Message-ID: <20000123141413.A49567@keltia.freenix.fr> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <200001230222.SAA18355@salsa.gv.tsc.tdk.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001230222.SAA18355@salsa.gv.tsc.tdk.com>; from Don.Lewis@tsc.tdk.com on Sat, Jan 22, 2000 at 06:22:47PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Don Lewis: > Doesn't bzip2 require a lot more memory for decompression? As I > recall, someone mentioned that this would cause problems for installing > releases on machines with only a small amount of RAM. Yes and is much slower than gzip. Having bzip2 as a port is enough IMO. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 6:47:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (Postfix) with ESMTP id 620A114BFF for ; Sun, 23 Jan 2000 06:47:20 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.211]) by smtp05.wxs.nl (Netscape Messaging Server 4.05) with ESMTP id FOSMEP01.90X; Sun, 23 Jan 2000 15:47:13 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id PAA23065; Sun, 23 Jan 2000 15:47:10 +0100 (CET) (envelope-from asmodai) Date: Sun, 23 Jan 2000 15:47:10 +0100 From: Jeroen Ruigrok/Asmodai To: "Matt M." Cc: current@freebsd.org Subject: Re: cvsup current - problems with -release kernel Message-ID: <20000123154710.E20851@daemon.ninth-circle.org> References: <001301bf64ef$0cb038a0$b64784d8@dns1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <001301bf64ef$0cb038a0$b64784d8@dns1>; from matt@boda.virtualave.net on Sat, Jan 22, 2000 at 07:40:37AM -0800 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000122 17:17], Matt M. (matt@boda.virtualave.net) wrote: >I cvsupd current, and did a make buildworld last night - i didn't do make >installworld - now when i boot my system (when it is initializing the >network) I get a message that is similar to "cannot allocate llinfo for >/kernel" - i tried an older kernel and i got the same message. I am using >DHCP, so I thought maybe there was a problem with that, and I ran >/stand/sysinstall to setup my system to NOT use DHCP and rebooted. Same >message. What could be the problem? make buildworld doesn't actually change >any installed files or settings does it? CURRENT introduced syscall changes, signal changes and god knows what else. Apparantly you didn't see /usr/src/UPDATING. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project Ain't gonna spend the rest of my Life, quietly fading away... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 6:58:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id B739314D18 for ; Sun, 23 Jan 2000 06:58:10 -0800 (PST) (envelope-from mzaki@e-mail.ne.jp) Received: from work.mzaki.nom (71.pool6.tokyo.att.ne.jp [165.76.23.86]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id XAA28357; Sun, 23 Jan 2000 23:58:09 +0900 (JST) Received: from work.mzaki.nom (mzaki@localhost [127.0.0.1]) by work.mzaki.nom (8.9.3/8.9.3) with ESMTP id XAA00341 for ; Sun, 23 Jan 2000 23:58:13 +0900 (JST) (envelope-from mzaki@e-mail.ne.jp) Date: Sun, 23 Jan 2000 23:58:12 +0900 Message-ID: <86d7qsomwr.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: current@FreeBSD.ORG Subject: My ATAPI CD not come ready X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I updated to today's -current from -stable. My ATAPI CD-ROM drive doesn't probed, and is seemed to be halted. (The tray is locked, won't open, and the LED keeps being on.) Mother board: ABIT BH6 CD-ROM drive: ATAPI [CDU77E-NE] on primary-master other ATAs: none It worked fine on -stable. I tried to use 'obsolete' wdc/wcd driver, it works fine. ---- : : ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0x4 : : ata0-master: drive wont come ready after identify ---- : wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (atapi): , removable, accel, dma,iordy wcd0: drive speed 689KB/sec, 128KB cache wcd0: supported read types: CD-DA wcd0: Audio: play, 256 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: CD-ROM unknown medium, unlocked -- Motomichi Matsuzaki Dept. of Biological Science, Faculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 9:30:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from sapphire.looksharp.net (mcdouga9.user.msu.edu [35.10.148.141]) by hub.freebsd.org (Postfix) with ESMTP id 935B514DD1 for ; Sun, 23 Jan 2000 09:30:12 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by sapphire.looksharp.net (8.9.3/8.9.3) with ESMTP id MAA22828; Sun, 23 Jan 2000 12:29:54 -0500 (EST) (envelope-from bsdx@looksharp.net) X-Authentication-Warning: sapphire.looksharp.net: bsdx owned process doing -bs Date: Sun, 23 Jan 2000 12:29:53 -0500 (EST) From: Adam To: "Matt M." Cc: freebsd-current@FreeBSD.ORG Subject: Re: cvsup current - problems with -release kernel In-Reply-To: <009901bf64f5$a1083ce0$b64784d8@dns1> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe that was a symptom of not listing lo0 first in the network interfaces line in rc.conf - try checking that? On Sat, 22 Jan 2000, Matt M. wrote: > I cvsupd current, and did a make buildworld last night - i didn't do make > installworld - now when i boot my system (when it is initializing the > network) I get a message that is similar to "cannot allocate llinfo for > /kernel" - i tried an older kernel and i got the same message. I am using > DHCP, so I thought maybe there was a problem with that, and I ran > /stand/sysinstall to setup my system to NOT use DHCP and rebooted. Same > message. What could be the problem? make buildworld doesn't actually change > any installed files or settings does it? > > My network doesnt work in any configuration at this point. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 9:51:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id F36B714D34 for ; Sun, 23 Jan 2000 09:51:54 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA26843; Sun, 23 Jan 2000 18:51:25 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001231751.SAA26843@freebsd.dk> Subject: Re: My ATAPI CD not come ready In-Reply-To: <86d7qsomwr.wl@tkc.att.ne.jp> from Motomichi Matsuzaki at "Jan 23, 2000 11:58:12 pm" To: mzaki@e-mail.ne.jp (Motomichi Matsuzaki) Date: Sun, 23 Jan 2000 18:51:25 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Motomichi Matsuzaki wrote: > > Hi. > > I updated to today's -current from -stable. > My ATAPI CD-ROM drive doesn't probed, > and is seemed to be halted. > (The tray is locked, won't open, and the LED keeps being on.) > > Mother board: ABIT BH6 > CD-ROM drive: ATAPI [CDU77E-NE] on primary-master > other ATAs: none > > It worked fine on -stable. > I tried to use 'obsolete' wdc/wcd driver, it works fine. This is fixed in the next update, due as soon as I get time.... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 11:13:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 0C13A14C24 for ; Sun, 23 Jan 2000 11:13:53 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 20038 invoked from network); 23 Jan 2000 19:13:51 -0000 Received: from lcm97.cvzoom.net (208.230.69.97) by ns.cvzoom.net with SMTP; 23 Jan 2000 19:13:51 -0000 Date: Sun, 23 Jan 2000 14:13:17 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: Moused hanging... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've noticed a strange problem with vidcontrol and moused recently with current. I also had the same problem about 3 weeks back, and it doesn't seem to be occurring all that regularly. Here's what I was doing: I had just exited out of X, XFree86 Version 3.9.17. I had two sessions of bladeenc going simultaneously (if that even matters). I'm guessing maybe the issue is with the PCI bus being accessed by moused and the ATA driver at the same time, since bladeenc does generate some disk activity. Anyway, I heard a `pop' through my speakers, and at the same time, moused went dead. I su'd to root, killed and restarted moused. I could not get my moused cursor back (tried vidcontrol -m off ; vidcontrol -m on a couple of times). The only way I could get moused to work again was to reboot. (???) Actually, this is a minor issue, but it is an inconvenience, since I have to reboot to get vidcontrol to work again. I'm sure some people have seen this. The last time this happened, my mouse in X stopped responding. This time, though, no X was running. As for the cause, I'm sure it is a PCI/ISA bus issue. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 11:21:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id D32A414C35 for ; Sun, 23 Jan 2000 11:21:19 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id UAA39044; Sun, 23 Jan 2000 20:21:13 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: Ollivier Robert Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) References: <200001230222.SAA18355@salsa.gv.tsc.tdk.com> <20000123141413.A49567@keltia.freenix.fr> From: Dag-Erling Smorgrav Date: 23 Jan 2000 20:21:12 +0100 In-Reply-To: Ollivier Robert's message of "Sun, 23 Jan 2000 14:14:13 +0100" Message-ID: Lines: 155 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ollivier Robert writes: > According to Don Lewis: > > Doesn't bzip2 require a lot more memory for decompression? As I > > recall, someone mentioned that this would cause problems for installing > > releases on machines with only a small amount of RAM. > Yes and is much slower than gzip. Having bzip2 as a port is enough IMO. Not only is it slower (and more memory-hungry), but it was designed and optimized for compressing text. The less text-like the input is, the worse bzip2 fares; in my tests, when compressing the output of /dev/urandom, it runs seven times slower than gzip, and produces a slightly larger output file: des@des ~/test% dd if=/dev/urandom of=random bs=1024 count=$((16*1024)) 16384+0 records in 16384+0 records out 16777216 bytes transferred in 21.406185 secs (783756 bytes/sec) des@des ~/test% time gzip -c random >random.gz gzip -c random > random.gz 12.62s user 0.63s system 88% cpu 14.997 total des@des ~/test% time bzip2 -c random >random.bz bzip2 -c random > random.bz 83.16s user 1.02s system 80% cpu 1:44.42 total des@des ~/test% ll total 49256 -rw-r--r-- 1 des des 16777216 Jan 23 18:48 random -rw-r--r-- 1 des des 16850433 Jan 23 18:54 random.bz -rw-r--r-- 1 des des 16779801 Jan 23 18:52 random.gz Of course, this is a worst-case scenario for both gzip and bzip2. Let's see how they fare with a tarball of the -CURRENT kernel tree: des@des ~/test% lcvs co sys >/dev/null 2>&1 des@des ~/test% tar cf sys.tar sys des@des ~/test% rm -rf sys des@des ~/test% time gzip -c sys.tar >sys.tar.gz gzip -c sys.tar > sys.tar.gz 37.46s user 1.04s system 89% cpu 43.062 total des@des ~/test% time bzip2 -c sys.tar >sys.tar.bz bzip2 -c sys.tar > sys.tar.bz 140.02s user 1.21s system 96% cpu 2:26.18 total des@des ~/test% ll total 59360 -rw-r--r-- 1 des des 43673600 Jan 23 19:10 sys.tar -rw-r--r-- 1 des des 7492474 Jan 23 19:22 sys.tar.bz -rw-r--r-- 1 des des 9554566 Jan 23 19:15 sys.tar.gz des@des ~/test% echo $((7492474*100/9554566)) 78 Much better! a 22% improvement over gzip - but it took nearly four times as long... How about my mail archive? des@des ~/test% tar cf mail.tar ~/Mail tar: Removing leading / from absolute path names in the archive. des@des ~/test% time gzip -c mail.tar >mail.tar.gz gzip -c mail.tar > mail.tar.gz 10.99s user 0.80s system 93% cpu 12.665 total des@des ~/test% time bzip2 -c mail.tar >mail.tar.bz bzip2 -c mail.tar > mail.tar.bz 64.16s user 0.77s system 92% cpu 1:10.40 total des@des ~/test% ll total 31048 -rw-r--r-- 1 des des 26204160 Jan 23 19:33 mail.tar -rw-r--r-- 1 des des 2329178 Jan 23 19:36 mail.tar.bz -rw-r--r-- 1 des des 3210845 Jan 23 19:34 mail.tar.gz des@des ~/test% echo $((2329178*100/3210845)) 72 Even better than source code, yet even slower. Mail is less repetitive than source code, but the repeated strings are longer - source code has much more punctuation (including operators) than text. This is the kind of data bzip2 excels at. How about a kernel? des@des ~/test% cp /kernel . des@des ~/test% time gzip -c kernel >kernel.gz gzip -c kernel > kernel.gz 2.02s user 0.02s system 98% cpu 2.068 total des@des ~/test% time bzip2 -c kernel >kernel.bz bzip2 -c kernel > kernel.bz 4.62s user 0.09s system 98% cpu 4.766 total des@des ~/test% ll total 2936 -r-xr-xr-x 1 des des 1597538 Jan 23 19:42 kernel* -rw-r--r-- 1 des des 669729 Jan 23 19:42 kernel.bz -rw-r--r-- 1 des des 696809 Jan 23 19:42 kernel.gz des@des ~/test% echo $((669729*100/1597538)) 41 des@des ~/test% echo $((696809*100/1597538)) 43 des@des ~/test% echo $((669729*100/696809)) 96 Very little improvement, and a fairly large time penalty, though the sample is too small for the comparison to make much sense (we don't know enough about overhead). Let's strip the kernel: des@des ~/test% strip kernel des@des ~/test% time gzip -c kernel >kernel.gz gzip -c kernel > kernel.gz 1.77s user 0.04s system 96% cpu 1.884 total des@des ~/test% time bzip2 -c kernel >kernel.bz bzip2 -c kernel > kernel.bz 5.80s user 0.04s system 97% cpu 5.989 total des@des ~/test% ll total 2488 -r-xr-xr-x 1 des des 1328176 Jan 23 19:44 kernel* -rw-r--r-- 1 des des 575566 Jan 23 19:45 kernel.bz -rw-r--r-- 1 des des 605411 Jan 23 19:44 kernel.gz des@des ~/test% echo $((575566*100/1328176)) 43 des@des ~/test% echo $((605411*100/1328176)) 45 des@des ~/test% echo $((575566*100/605411)) 95 Both gzip and bzip2 do worse with a stripped kernel than with an unstripped one, because what we stripped away (function and variable names) is repetitive and covers a small portion of the alphabet, and therefore compresses well. Now, here's the killer: a 2.5 MB text file which gzip compresses significantly better than bzip2: des@des ~/test% cp /usr/share/dict/web2 . des@des ~/test% time gzip -c web2 >web2.gz gzip -c web2 > web2.gz 4.25s user 0.06s system 99% cpu 4.319 total des@des ~/test% time bzip2 -c web2 >web2.bz bzip2 -c web2 > web2.bz 5.86s user 0.07s system 98% cpu 5.998 total des@des ~/test% ll total 4048 -r--r--r-- 1 des des 2493066 Jan 23 19:24 web2 -rw-r--r-- 1 des des 857838 Jan 23 19:24 web2.bz -rw-r--r-- 1 des des 754540 Jan 23 19:24 web2.gz des@des ~/test% echo $((754540*100/857838)) 87 Not much of a difference in compression time, though we still see bzip2 running slower than gzip. But gzip compressed 13% better than bzip2, because the file doesn't contain many repetitions of the kind that bzip2 exploits. bzip2 needs lots of fairly long repeated strings to work well, because it's designed to compress text, which contains lots of fairly long repeated strings. To summarize, bzip2 compresses certain types of data very well, but has more degenerate cases than gzip. Using bzip2 for source code or text (even marked-up text) is good. Using it for binaries is not-so-good. Using it for one-shot compression (e.g. compressing backup archives, or in a gather-compress-transfer-decompress-process pipeline to save bandwidth) is downright stupid unless the cost of storing or transferring the compressed data is unusually high. Note that all published benchmarks (at least, those I've seen) comparing the performance of block-sorting compression with other compression algorithms use plain text as sample input, and are therefore mostly meaningless unless all your data is plain text. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 11:23: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3AC9D14BEC for ; Sun, 23 Jan 2000 11:22:59 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA06301 for ; Sun, 23 Jan 2000 11:22:58 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA19009; Sun, 23 Jan 2000 11:22:57 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 23 Jan 2000 11:22:57 -0800 (PST) Message-Id: <200001231922.LAA19009@vashon.polstra.com> To: current@freebsd.org Subject: Re: rtld-elf, java + tya In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Max Khon wrote: > > applet_viewer bombs out with a lot of stuff in the output like this > (until killed -9): > > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 The last time this problem happened (I thought I fixed it!), it almost always appeared very soon after starting a multithreaded program. At that time I was able to reproduce it with the script below. Those of you who have seen it might be able to modify the script so it runs your failing application instead of cvsup. It might help you to get a stack trace for me (hint hint). John #! /bin/sh # # for (i = 0; i < $n; i++) { # start $prog in background # sleep($t) # kill $prog # } prog=$HOME/bin/cvsup args="/dev/null" t=0.5 n=100 if [ $# -ge 1 ]; then n=$1 fi go() { $prog $args & pid=$! sleep $t kill $pid wait %1 status=$? if [ $status -ne 143 ]; then echo "Status = $status" exit fi } i=0 while [ $i -lt $n ]; do go i=$(($i + 1)) done To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 11:27:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 46C8614E0B for ; Sun, 23 Jan 2000 11:27:29 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA06332 for ; Sun, 23 Jan 2000 11:27:28 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA19042; Sun, 23 Jan 2000 11:27:28 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 23 Jan 2000 11:27:28 -0800 (PST) Message-Id: <200001231927.LAA19042@vashon.polstra.com> To: current@freebsd.org Subject: Re: rtld-elf, java + tya In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 If any of you can reproduce this problem fairly reliably, please try the appended patch for "src/libexec/rtld-elf/lockdflt.c" and let me know if it solves the problem. Thanks, John Index: lockdflt.c =================================================================== RCS file: /home/ncvs/src/libexec/rtld-elf/lockdflt.c,v retrieving revision 1.3 diff -u -r1.3 lockdflt.c --- lockdflt.c 2000/01/09 21:13:48 1.3 +++ lockdflt.c 2000/01/23 19:03:26 @@ -28,10 +28,9 @@ /* * Default thread locking implementation for the dynamic linker. It * is used until the client registers a different implementation with - * dllockinit(). The default implementation does mutual exclusion - * by blocking the SIGVTALRM, SIGPROF, and SIGALRM signals. This is - * based on the observation that most userland thread packages use one - * of these signals to support preemption. + * dllockinit(). The default implementation does mutual exclusion by + * blocking almost all signals. This is based on the observation that + * most userland thread packages use signals to support preemption. */ #include @@ -63,10 +62,13 @@ l = NEW(LockDflt); l->depth = 0; - sigemptyset(&l->lock_mask); - sigaddset(&l->lock_mask, SIGVTALRM); - sigaddset(&l->lock_mask, SIGPROF); - sigaddset(&l->lock_mask, SIGALRM); + sigfillset(&l->lock_mask); + sigdelset(&l->lock_mask, SIGTRAP); + sigdelset(&l->lock_mask, SIGABRT); + sigdelset(&l->lock_mask, SIGBUS); + sigdelset(&l->lock_mask, SIGSEGV); + sigdelset(&l->lock_mask, SIGKILL); + sigdelset(&l->lock_mask, SIGSTOP); return l; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 11:50:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id 6ED8B150AF for ; Sun, 23 Jan 2000 11:50:09 -0800 (PST) (envelope-from dakuntz@home.com) Received: from windows ([24.2.16.41]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with SMTP id <20000123195008.LUVW9818.mail.rdc1.tn.home.com@windows> for ; Sun, 23 Jan 2000 11:50:08 -0800 Message-ID: <000901bf65da$f4945160$29100218@micronetinfo.com> From: "Douglas Kuntz" To: References: <200001231927.LAA19042@vashon.polstra.com> Subject: mcrypt Date: Sun, 23 Jan 2000 14:49:26 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While trying to compile the Apache13-php3 port, with mod_ssl, and encryption, I get the following error: -c functions/mcrypt.c -o functions/mcrypt.o functions/mcrypt.c:172: #error Please update your mcrypt library *** Error code 1 Is this a ports problem, or a current problem? Thanks in advance. Douglas Kuntz ----- Original Message ----- From: "John Polstra" To: Sent: Sunday, January 23, 2000 2:27 PM Subject: Re: rtld-elf, java + tya > > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 > > If any of you can reproduce this problem fairly reliably, please try > the appended patch for "src/libexec/rtld-elf/lockdflt.c" and let me > know if it solves the problem. > > Thanks, > John > > Index: lockdflt.c > =================================================================== > RCS file: /home/ncvs/src/libexec/rtld-elf/lockdflt.c,v > retrieving revision 1.3 > diff -u -r1.3 lockdflt.c > --- lockdflt.c 2000/01/09 21:13:48 1.3 > +++ lockdflt.c 2000/01/23 19:03:26 > @@ -28,10 +28,9 @@ > /* > * Default thread locking implementation for the dynamic linker. It > * is used until the client registers a different implementation with > - * dllockinit(). The default implementation does mutual exclusion > - * by blocking the SIGVTALRM, SIGPROF, and SIGALRM signals. This is > - * based on the observation that most userland thread packages use one > - * of these signals to support preemption. > + * dllockinit(). The default implementation does mutual exclusion by > + * blocking almost all signals. This is based on the observation that > + * most userland thread packages use signals to support preemption. > */ > > #include > @@ -63,10 +62,13 @@ > > l = NEW(LockDflt); > l->depth = 0; > - sigemptyset(&l->lock_mask); > - sigaddset(&l->lock_mask, SIGVTALRM); > - sigaddset(&l->lock_mask, SIGPROF); > - sigaddset(&l->lock_mask, SIGALRM); > + sigfillset(&l->lock_mask); > + sigdelset(&l->lock_mask, SIGTRAP); > + sigdelset(&l->lock_mask, SIGABRT); > + sigdelset(&l->lock_mask, SIGBUS); > + sigdelset(&l->lock_mask, SIGSEGV); > + sigdelset(&l->lock_mask, SIGKILL); > + sigdelset(&l->lock_mask, SIGSTOP); > return l; > } > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 11:58:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4EC2014CA4 for ; Sun, 23 Jan 2000 11:58:23 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA81502; Sun, 23 Jan 2000 11:58:11 -0800 (PST) (envelope-from dillon) Date: Sun, 23 Jan 2000 11:58:11 -0800 (PST) From: Matthew Dillon Message-Id: <200001231958.LAA81502@apollo.backplane.com> To: Nick Hibma Cc: FreeBSD CURRENT Mailing List Subject: Re: mmap problem when resuming while mpg123 is playing References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :The following error shows up in my messages log when mpg123 is playing :songs off a mounted CD ROM when the laptop is suspended and resumed. : :Jan 23 11:21:04 henny /kernel: resumed from suspended mode (slept :00:36:53) :Jan 23 11:21:04 henny /kernel: ata0: resetting devices .. done :Jan 23 11:21:04 henny /kernel: ata1: resetting devices .. done :Jan 23 11:21:04 henny /kernel: vm_fault: pager read error, pid 9309 :(mpg123) :Jan 23 11:21:04 henny /kernel: pid 9309 (mpg123), uid 0: exited on :signal 11 (core dumped) : :The contents of the cd can no longer be accessed. umount /cdrom does not :work, umount -f /cdrom does, but the system later on panics in __getcwd, :eventhough I had exitted all the shells (logged out) before doing the :forced unmount. : :After mounting the CD again (before the panic happens) the CD is :accessible again. This isn't an mmap() problem. It would appear to me that the CD's device driver gets confused and starts generating I/O errors when you resume after a suspend. I think you've found multiple bugs here. First, the fact that the CD fails on resume (which may not be easy to fix - it's a job for the device driver writers to track down), and second the __getcwd panic, which is probably fairly easy to fix if we can get a stack backtrace or kernel core dump. -Matt :... :Jan 23 12:09:37 henny /kernel: acd0: read 2416KB/s (2416KB/s), 128KB :buffer, PIO4 :Jan 23 12:09:37 henny /kernel: acd0: Reads: CD-DA :Jan 23 12:09:37 henny /kernel: acd0: Audio: play, 16 volume levels :Jan 23 12:09:37 henny /kernel: acd0: Mechanism: ejectable tray :Jan 23 12:09:38 henny /kernel: acd0: Medium: no/blank disc inside, :unlocked :Jan 23 12:09:38 henny /kernel: pccard: card inserted, slot 1 :Jan 23 12:09:38 henny /kernel: ata_command: timeout waiting for :interrupt :Jan 23 12:09:38 henny /kernel: Mounting root from ufs:/dev/ad0s2a : :-- :n_hibma@webweaving.org :n_hibma@freebsd.org USB project :http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 12:13: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 4DBB4150CD; Sun, 23 Jan 2000 12:13:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 3EA461CD437; Sun, 23 Jan 2000 12:13:01 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 23 Jan 2000 12:13:01 -0800 (PST) From: Kris Kennaway To: Douglas Kuntz Cc: current@FreeBSD.ORG Subject: Re: mcrypt In-Reply-To: <000901bf65da$f4945160$29100218@micronetinfo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jan 2000, Douglas Kuntz wrote: > -c functions/mcrypt.c -o functions/mcrypt.o > functions/mcrypt.c:172: #error Please update your mcrypt library > *** Error code 1 > > Is this a ports problem, or a current problem? Ports. Looks like it's trying to use the library from security/mcrypt. Do you have an old version of this installed which the configure script might be locating? BTW, please don't reply to an unrelated message when starting a new topic. It screws up the message threading for people who use a MUA which can do that. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 12:19:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from drama.navinet.net (drama.navinet.net [216.67.14.8]) by hub.freebsd.org (Postfix) with ESMTP id 4F99D156C0 for ; Sun, 23 Jan 2000 12:19:46 -0800 (PST) (envelope-from forrie@drama.navinet.net) Received: (from forrie@localhost) by drama.navinet.net with id e0NKJjN14831 for freebsd-current@freebsd.org; Sun, 23 Jan 2000 15:19:45 -0500 (EST) Date: Sun, 23 Jan 2000 15:19:45 -0500 From: Forrest Aldrich To: freebsd-current@freebsd.org Subject: PCCARD support Message-ID: <20000123151945.K20886@drama.navinet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Where are we with getting PCCARD support, such as the 3COM MegaHertz (3CCFEM556 B) card in the mainstream distribution? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 12:53:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 4B3DB14CA6 for ; Sun, 23 Jan 2000 12:53:38 -0800 (PST) (envelope-from trouble@netquick.net) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=netquick.net) by bekool.com with esmtp (Exim 3.03 #1) id 12CUa8-000Frx-00 for freebsd-current@freebsd.org; Sun, 23 Jan 2000 16:30:01 -0500 Message-ID: <388A1B20.20D52564@netquick.net> Date: Sat, 22 Jan 2000 16:03:28 -0500 From: TrouBle Reply-To: trouble@netquick.net X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-current@freebsd.org" Subject: Hrmm whats missing ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsuped a fresh source tree from current did a buildworld and install world, everything okay so far, but now i get funny lil errors like ftp angelsguardian.netquick.net Connected to angelsguardian.netquick.net. 220 angelsguardian.netquick.net FTP server (Version 6.00LS) ready. Name (angelsguardian.netquick.net:trouble): kerberus 331 Password required for kerberus. Password:Jan 22 16:00:14 angelsguardian ftpd[7395]: no modules loaded for `ftpd' service Jan 22 16:00:14 angelsguardian ftpd[7395]: no modules loaded for `ftpd' service Jan 22 16:00:14 angelsguardian ftpd[7395]: auth_pam: Permission denied Jan 22 16:00:14 angelsguardian ftpd[7395]: auth_pam: Permission denied whats missing, they all seem to be auth/encryption errors, did i not get like lib crypt, kerberus and the crypto sources ? if not how do i cvs them to? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 12:55:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id D1795150B6 for ; Sun, 23 Jan 2000 12:55:29 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 217CD9B39; Sun, 23 Jan 2000 15:55:28 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 17356BA0C; Sun, 23 Jan 2000 15:55:28 -0500 (EST) Date: Sun, 23 Jan 2000 15:55:28 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: TrouBle Cc: "freebsd-current@freebsd.org" Subject: Re: Hrmm whats missing ? In-Reply-To: <388A1B20.20D52564@netquick.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 22 Jan 2000, TrouBle wrote: > Jan 22 16:00:14 angelsguardian ftpd[7395]: auth_pam: Permission denied > Jan 22 16:00:14 angelsguardian ftpd[7395]: auth_pam: Permission denied > You didn't run mergemaster/update /etc; in particular, install/update pam.conf (note the auth_pam above). ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 12:55:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 5A87B14CA6; Sun, 23 Jan 2000 12:55:39 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id PAA66594; Sun, 23 Jan 2000 15:01:24 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 23 Jan 2000 15:01:23 -0500 (EST) From: Chuck Robey To: Juergen Lock Cc: Will Andrews , Shigeyuki Fukushima , current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-Reply-To: <200001231303.OAA75362@saturn.kn-bremen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jan 2000, Juergen Lock wrote: > In article you write: > >... > >A case would have to be built that bzip2 does something critical that > >cannot be done without bzip2. Else, it stays as a fine port. Heck, emacs > >is a fine port too, but it'll never get into the base system. > > Very true, but i can actually think of one thing were bzip2 would > really be useful: to better compress the kernel on install floppies > so you could keep more things in it. (like ptys and pass which > would make fixit more useful, or pppoe which was thrown out too > recently if i'm not mistaken.) > > Btw you could probably also kgzip the loader, that would free up > some space too. Juergen Lock: It's Better! Chuck: Better doesn't count, only need, functionality and compatibility. Juergen Lock: It's Better! How come I get the feeling that you didn't read the post? > > Regards, > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 13: 9:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 9ECD414D96 for ; Sun, 23 Jan 2000 13:09:15 -0800 (PST) (envelope-from trouble@netquick.net) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=netquick.net) by bekool.com with esmtp (Exim 3.03 #1) id 12CUp5-000Fwg-00; Sun, 23 Jan 2000 16:45:27 -0500 Message-ID: <388A1EBF.C1BB0ECE@netquick.net> Date: Sat, 22 Jan 2000 16:18:55 -0500 From: TrouBle Reply-To: trouble@netquick.net X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Chris D. Faulhaber" Cc: "freebsd-current@freebsd.org" Subject: Re: Hrmm whats missing ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Whooo hoooo God im dumb... thanks chris, thats fixed it all...... : )) happy cuurent system now running > You didn't run mergemaster/update /etc; in particular, install/update > pam.conf (note the auth_pam above). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 13:56:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7470A14D67 for ; Sun, 23 Jan 2000 13:56:39 -0800 (PST) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA20364 for ; Sun, 23 Jan 2000 13:56:39 -0800 Date: Sun, 23 Jan 2000 13:56:37 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: freebsd-current@freebsd.org Subject: more softdep funnies? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From a kernel built over the last day or so, alpha, ata disk: Debugger() at Debugger+0x2c panic() at panic+0x100 initiate_write_inodeblock() at initiate_write_inodeblock+0x40 softdep_disk_io_initiation() at softdep_disk_io_initiation+0xac spec_strategy() at spec_strategy+0x48 bwrite() at bwrite+0x404 vop_stdbwrite() at vop_stdbwrite+0x1c vop_defaultop() at vop_defaultop+0x2c vfs_bio_awrite() at vfs_bio_awrite+0x484 spec_fsync() at spec_fsync+0x1ec sched_sync() at sched_sync+0x1a8 exception_return() at exception_return dump not available because the ATA drive and/or driver fouled up in the middle of the dump- and the ad drive didn't show back up on reboot and the system is wedged so I'd have to go to the office to fix it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 14: 3:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 19716151EF; Sun, 23 Jan 2000 14:03:26 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id WAA19925; Sun, 23 Jan 2000 22:58:54 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id WAA89000; Sun, 23 Jan 2000 22:31:58 +0100 (CET) From: Juergen Lock Date: Sun, 23 Jan 2000 22:31:57 +0100 To: Chuck Robey Cc: Will Andrews , Shigeyuki Fukushima , current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Message-ID: <20000123223157.C81122@saturn.kn-bremen.de> References: <200001231303.OAA75362@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 23, 2000 at 03:01:23PM -0500, Chuck Robey wrote: > On Sun, 23 Jan 2000, Juergen Lock wrote: > > > In article you write: > > >... > > >A case would have to be built that bzip2 does something critical that > > >cannot be done without bzip2. Else, it stays as a fine port. Heck, emacs > > >is a fine port too, but it'll never get into the base system. > > > > Very true, but i can actually think of one thing were bzip2 would > > really be useful: to better compress the kernel on install floppies > > so you could keep more things in it. (like ptys and pass which > > would make fixit more useful, or pppoe which was thrown out too > > recently if i'm not mistaken.) > > > > Btw you could probably also kgzip the loader, that would free up > > some space too. > > Juergen Lock: It's Better! > Chuck: Better doesn't count, only need, functionality > and compatibility. > Juergen Lock: It's Better! > > How come I get the feeling that you didn't read the post? Oh, the original poster wasn't me. And how `critical' the capabilities of the kernel on the install floppy are is debatable i'd say. (Of course you probably could make a seperate one for pppoe installs by leaving out other things in that, and for fixit just make your own boot floppy... but both of these at least make things more complicated for the newbies.) Regard, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 15: 5:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from MailAndNews.com (MailAndNews.com [199.29.68.160]) by hub.freebsd.org (Postfix) with ESMTP id B6C2C1503F for ; Sun, 23 Jan 2000 15:05:49 -0800 (PST) (envelope-from mheffner@mailandnews.com) Received: from muriel.penguinpowered.com [208.138.198.103] (mheffner@mailandnews.com); Sun, 23 Jan 2000 18:05:44 -0500 X-WM-Posted-At: MailAndNews.com; Sun, 23 Jan 00 18:05:44 -0500 Content-Length: 2217 Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 23 Jan 2000 18:07:26 -0500 (EST) Reply-To: Mike Heffner From: Mike Heffner To: FreeBSD-current Subject: ATA CDR problems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Trying to write a data cd using the burndata script in /usr/share/examples/atapi, I'm getting this on the console, and I'm unable to write the cd: acd1: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=00 acd1: sequence error (no open) acd1: sequence error (no open) Here's what the script outputs: enterprise# ./burndata acd1c /usr/home/spock/disk.iso preparing disk in /dev/racd1c wormcontrol: ioctl(WORMIOCPREPDISK): Inappropriate ioctl for device setting up to transfer data track wormcontrol: ioctl(WORMIOCPREPTRACK): Inappropriate ioctl for device writing data to disk dd: /dev/racd1c: Input/output error 4+0 records in 0+0 records out 0 bytes transferred in 0.000737 secs (0 bytes/sec) fixating disk wormcontrol: ioctl(WORMIOFIXATION): Inappropriate ioctl for device done! And here's my dmesg and config lines: ata-pci0: port 0xffa0-0xffaf at device 7.1 on pc i0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ad0: ATA-4 disk at ata0 as master ad0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad1: ATA-4 disk at ata0 as slave ad1: 12416MB (25429824 sectors), 25228 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as master acd0: read 171KB/s (6187KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked acd1: CD-RW drive at ata1 as slave acd1: read 344KB/s (1034KB/s) write 344KB/s (344KB/s), 768KB buffer, PIO3 acd1: Reads: CD-R, CD-RW, CD-DA stream, packet acd1: Writes: CD-R, CD-RW, test write acd1: Audio: play, 128 volume levels acd1: Mechanism: ejectable tray acd1: Medium: no/blank disc inside, unlocked, lock protected Anyone else seeing this? Is this a crappy drive problem? --------------------------------- Mike Heffner Fredericksburg, VA ICQ# 882073 Date: 23-Jan-2000 Time: 18:00:50 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 15:15:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from MailAndNews.com (MailAndNews.com [199.29.68.160]) by hub.freebsd.org (Postfix) with ESMTP id CEF6F14C7F for ; Sun, 23 Jan 2000 15:15:27 -0800 (PST) (envelope-from mheffner@mailandnews.com) Received: from muriel.penguinpowered.com [208.138.198.103] (mheffner@mailandnews.com); Sun, 23 Jan 2000 18:15:22 -0500 X-WM-Posted-At: MailAndNews.com; Sun, 23 Jan 00 18:15:22 -0500 Content-Length: 467 Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 23 Jan 2000 18:16:34 -0500 (EST) Reply-To: Mike Heffner From: Mike Heffner To: Mike Heffner Subject: RE: ATA CDR problems Cc: FreeBSD-current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Jan-2000 Mike Heffner wrote: | And here's my dmesg and config lines: | oops, forgot the config lines. here they are: # ATAPI devices device ata0 device atadisk0 # ATAPI DISK device atapicd0 # ATAPI CDROM drives options ATA_STATIC_ID --------------------------------- Mike Heffner Fredericksburg, VA ICQ# 882073 Date: 23-Jan-2000 Time: 18:15:14 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 15:30:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 56DCA1523A for ; Sun, 23 Jan 2000 15:30:08 -0800 (PST) (envelope-from trouble@netquick.net) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=netquick.net) by bekool.com with esmtp (Exim 3.03 #1) id 12CX1V-000GUO-00 for freebsd-current@freebsd.org; Sun, 23 Jan 2000 19:06:26 -0500 Message-ID: <388A3FC7.79D6B082@netquick.net> Date: Sat, 22 Jan 2000 18:39:51 -0500 From: TrouBle Reply-To: trouble@netquick.net X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-current@freebsd.org" Subject: D?ISK I/O erros Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG this is a brand new 10gig UDMA 66 maxtor.... is this a disk problem via hardware, or is it a BSD issue with the new code ??? angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 7801951 retrying Jan 22 18:31:35 angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 7801951 retrying Jan 22 18:31:35 angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 7801951 retrying Jan 22 18:31:35 angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 7801951 retrying Jan 22 18:36:18 angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 5062847 retrying Jan 22 18:36:18 angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 5062847 retrying Jan 22 18:36:18 angelsguardian last message repeated 2 times Jan 22 18:36:18 angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 5062847WARNING: WAIT_READY active=ATA_ACTIVE_ATA Jan 22 18:36:18 angelsguardian last message repeated 2 times Jan 22 18:36:18 angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 5062847WARNING: WAIT_READY active=ATA_ACTIVE_ATA Jan 22 18:36:18 angelsguardian /kernel: falling back to PIO mode Jan 22 18:36:18 angelsguardian /kernel: falling back to PIO mode mount shows---- /dev/wd0s1a on / (ufs, local, writes: sync 713 async 2615, reads: sync 1936 async 118) dmesg output------- CPU: Pentium III/Xeon (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x387f9ff real memory = 117374976 (114624K bytes) avail memory = 110088192 (107508K bytes) --snip-- pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 --snip-- ad0: ATA-5 disk at ata0 as master ad0: 9770MB (20010816 sectors), 19852 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 15:38:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 7FF7C14A04 for ; Sun, 23 Jan 2000 15:38:07 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS3-p63.rlz.netvision.net.il [62.0.169.65]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id BAA11393; Mon, 24 Jan 2000 01:35:52 +0200 (IST) Message-ID: <388B9084.B988A990@freenet.co.uk> Date: Sun, 23 Jan 2000 23:36:36 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Heffner Cc: FreeBSD-current Subject: Re: ATA CDR problems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Heffner wrote: > > Hi, > > Trying to write a data cd using the burndata script in > /usr/share/examples/atapi, I'm getting this on the console, and I'm unable to > write the cd: > > acd1: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=00 > acd1: sequence error (no open) > acd1: sequence error (no open) If you're running -current, try the new burncd program (man burncd will tell you more). Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 16:10:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 13B5914FE1 for ; Sun, 23 Jan 2000 16:10:40 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115220>; Mon, 24 Jan 2000 11:11:12 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: With feature freeze being in place In-reply-to: <20000122210136.B18600@daemon.ninth-circle.org>; from asmodai@wxs.nl on Sun, Jan 23, 2000 at 07:03:10AM +1100 To: Nick Hibma Cc: Jeroen Ruigrok/Asmodai , FreeBSD CURRENT Mailing List Message-Id: <00Jan24.111112est.115220@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <20000122210136.B18600@daemon.ninth-circle.org> Date: Mon, 24 Jan 2000 11:11:12 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Jan-23 07:03:10 +1100, Jeroen Ruigrok/Asmodai wrote: >Also, are GENERIC and LINT in sync? Comparing LINT and GENERIC is made more difficult by the significantly different ordering. Is there some good reason for this, or would an offer of GENERIC re-written into the same order as LINT be accepted? Also, what is the best approach to submitting documentation for the `undocumented' options in LINT? send-pr for each option seems excessive (and the resultant diffs would be a pain to generate or apply except in the original order). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 16:50:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 1CB18151E5 for ; Sun, 23 Jan 2000 16:50:49 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac7.wam.umd.edu (root@rac7.wam.umd.edu [128.8.10.147]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA18224 for ; Sun, 23 Jan 2000 19:50:40 -0500 (EST) Received: from rac7.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac7.wam.umd.edu (8.9.3/8.9.3) with SMTP id TAA28743 for ; Sun, 23 Jan 2000 19:50:45 -0500 (EST) Received: from localhost (culverk@localhost) by rac7.wam.umd.edu (8.9.3/8.9.3) with ESMTP id TAA28735 for ; Sun, 23 Jan 2000 19:50:44 -0500 (EST) X-Authentication-Warning: rac7.wam.umd.edu: culverk owned process doing -bs Date: Sun, 23 Jan 2000 19:50:44 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: ATA driver and DVD's Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently downloaded and tried xmovie (there is a link to it at www.opensound.com) and when I tried to play a vob file from the DVD my xconsole filled with this error: acd0: READ_BIG - ILLEGAL REQUEST asc=6f ascq=03 error=00 Is this an ATA driver problem? ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 16:53: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 4175E14A1F for ; Sun, 23 Jan 2000 16:53:01 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id BAA42752; Mon, 24 Jan 2000 01:53:00 +0100 (CET) (envelope-from olli) Date: Mon, 24 Jan 2000 01:53:00 +0100 (CET) Message-Id: <200001240053.BAA42752@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: newpcm problem --> patch --> problem X-Newsgroups: list.freebsd-current User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I upgraded from an early December -current to a current -current (CVSupped yesterday, buildworld took 16 hours). Works fine, except that the soundcard (ISA PnP, Avance Logic ALS100+, SB16- compatible) does not work anymore. It worked fine before. (``Does not work anymore'' == it just blocks when I try to play something, and half of the mixer settings aren't recognized anymore. I can't get a single beep from the boxes. Yes, I do have ``device sbc0'' in my kernel.) Early December dmesg says: pcm0: at port 0x220-0x22f irq 5 drq 5,1 on isa0 And current dmesg says: pcm0: at port 0x220-0x22f irq 5 drq 5,1 on isa Obviously, the card is probed as something completely different, which is wrong. No wonder that it doesn't work. The following patch fixes it, and the soundcard works just like before, but... --- src/sys/dev/sound/isa/mss.c.orig Thu Jan 13 07:11:32 2000 +++ src/sys/dev/sound/isa/mss.c Mon Jan 24 00:38:08 2000 @@ -1328,7 +1328,9 @@ static struct isa_pnp_id pnpmss_ids[] = { {0x0000630e, "CS423x"}, /* CSC0000 */ {0x0001630e, "CS423x-PCI"}, /* CSC0100 */ - {0x01000000, "CMI8330"}, /* @@@0001 */ +#if 0 + {0x01000000, "CMI8330"}, /* @@@0001 */ +#endif {0x2100a865, "Yamaha OPL-SAx"}, /* YMH0021 */ {0x1110d315, "ENSONIQ SoundscapeVIVO"}, /* ENS1011 */ {0x1093143e, "OPTi931"}, /* OPT9310 */ --- src/sys/dev/sound/isa/sbc.c.orig Wed Jan 12 12:16:23 2000 +++ src/sys/dev/sound/isa/sbc.c Mon Jan 24 00:44:28 2000 @@ -202,6 +202,7 @@ {0x44008c0e, "Creative SB AWE64 Gold"}, /* CTL0044 */ {0x45008c0e, "Creative SB AWE64"}, /* CTL0045 */ + {0x01000000, "Avance Logic ALS100+"}, /* @@@0001 */ {0x01100000, "Avance Asound 110"}, /* @@@1001 */ {0x01200000, "Avance Logic ALS120"}, /* @@@2001 */ ... of course, now a real ``CMI8330'' would probably not be detected correctly anymore. I don't have such a card (and I've never heard of it before). If it really has the same device ID as the ALS100+, we're in trouble, I guess. BTW, with the above patch, my card is probed like this: sbc0: at port 0x220-0x22f irq 5 drq 5,1 on isa0 sbc0: setting card to irq 5, drq 5, 1 pcm0: on sbc0 and works happily. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 17: 5:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id F04F9150FF for ; Sun, 23 Jan 2000 17:05:09 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA07350; Sun, 23 Jan 2000 17:05:08 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA19850; Sun, 23 Jan 2000 17:05:08 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 23 Jan 2000 17:05:08 -0800 (PST) Message-Id: <200001240105.RAA19850@vashon.polstra.com> To: freebsd@gndrsh.dnsmgr.net Subject: Re: With feature freeze being in place In-Reply-To: <200001230155.RAA64409@gndrsh.dnsmgr.net> References: <200001230155.RAA64409@gndrsh.dnsmgr.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001230155.RAA64409@gndrsh.dnsmgr.net>, Rodney W. Grimes wrote: > Ohhh.. and please update your cvsup-mirror stats, the sizes of things are way > way way out of date: I think I'm just going to remove the stats and replace them with a URL for an automatically-updated list. It's practically impossible to keep them up-to-date in the port. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 17: 6:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 649C3150FF for ; Sun, 23 Jan 2000 17:06:52 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id UAA47857; Sun, 23 Jan 2000 20:06:46 -0500 (EST) Date: Sun, 23 Jan 2000 20:06:46 -0500 (EST) From: "Matthew N. Dodd" To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: PCCARD support In-Reply-To: <20000123151945.K20886@drama.navinet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jan 2000, Forrest Aldrich wrote: > Where are we with getting PCCARD support, such as the 3COM MegaHertz > (3CCFEM556 B) card in the mainstream distribution? Can you use the output of 'pccardc dumpcis' to construct an entry for /etc/pccard.conf and try the 'ep' driver to see if it will work? I suspect it will. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 17:17:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 4F7FD14A24 for ; Sun, 23 Jan 2000 17:17:46 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id RAA07396 for ; Sun, 23 Jan 2000 17:17:45 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id RAA19898; Sun, 23 Jan 2000 17:17:41 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 23 Jan 2000 17:17:41 -0800 (PST) Message-Id: <200001240117.RAA19898@vashon.polstra.com> To: current@freebsd.org Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <200001231303.NAA01359@hak.lan.Awfulhak.org> References: <200001231303.NAA01359@hak.lan.Awfulhak.org> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Before I forget: PLEASE DON'T CC ME ON YOUR REPLIES. I'LL READ THEM IN THE MAILING LIST. THANK YOU. > > Hmmm. A thought just occurred to me. There's no need to measure > > these things. Lookup all the IP addresses. Do a non blocking > > connection to each of these machines. First one to come back with the > > REL16_1 response wins, and all the others get closed and you use that > > one. > > I like this idea, except that some sort of consistency is required - > ie, once I've started using cvsupX, I'd like to use it in preference > to slightly better machines unless it stays bad for some configurable > number of connections.... Um, guys ... hello? The goal here is to spread the load more evenly. Now it's true that if every CVSup run hits every mirror site that the load will be even. But it will also be a whole helluva lot higher than it is even now. So no, I'm not going to implement any solution that involves pinging or connecting to a bunch of sites every time you start up CVSup. Please, no more pie in the sky ideas. My announcement was simply trying to address a trivial problem for today, namely that too many people are failing to use their brains when filling in that host field in their supfiles. That's all. These fancy solutions are just dandy except they don't solve the problem today and most of them are so complicated that they're extremely unlikely to get implemented (at least by me) any time soon. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 17:56:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1AFD914BEC for ; Sun, 23 Jan 2000 17:56:11 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA97878; Sun, 23 Jan 2000 18:56:07 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA47712; Sun, 23 Jan 2000 18:56:39 -0700 (MST) Message-Id: <200001240156.SAA47712@harmony.village.org> To: Brian Somers Subject: Re: Please help spread the CVSup mirror load more evenly Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 23 Jan 2000 13:03:19 GMT." <200001231303.NAA01359@hak.lan.Awfulhak.org> References: <200001231303.NAA01359@hak.lan.Awfulhak.org> Date: Sun, 23 Jan 2000 18:56:39 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001231303.NAA01359@hak.lan.Awfulhak.org> Brian Somers writes: : I like this idea, except that some sort of consistency is required - : ie, once I've started using cvsupX, I'd like to use it in preference : to slightly better machines unless it stays bad for some configurable : number of connections.... I'm hatching in my head a scheme as follows: Each host gets a value of 1 (unless you go in and tweak it). Hosts are tried in order of their values and in some unspecified order in the case of ties. Host with a value < = 0 are never tried. Floating point math is done with the results rounded up to the nearest integer. This keeps people from falling below 1. Users can disable a host by tweaking its value in the config file to be 0. Each time you successfully connect, you get a bonus of B. Each failure reduces the nubmer by x%. I'm thinking that B should be on the order of 10-20 and x should be on the order of 10-20. Try at most twice per host. If all the hosts fail, try the best host in forever mode. No updates should happen here to weightings. Not sure about this method in, say, a cron job... That way, as a host succeeds, it will be tried more often first. As a host fails, it will be tried less often. Over time if host N goes down, its weighting will decay relatively quickly and the next best one will take up the slack.... I purposely chose a linear scale up, and a non-linear scale down. Of course I don't have time to actually code this up. And it also strikes me as overkill. I'm happy with the fixed order list that I tweak as I notice things going bad... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 17:58: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 72B1E14BF2 for ; Sun, 23 Jan 2000 17:57:52 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA97883; Sun, 23 Jan 2000 18:57:40 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA47729; Sun, 23 Jan 2000 18:58:12 -0700 (MST) Message-Id: <200001240158.SAA47729@harmony.village.org> To: Forrest Aldrich Subject: Re: PCCARD support Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 23 Jan 2000 15:19:45 EST." <20000123151945.K20886@drama.navinet.net> References: <20000123151945.K20886@drama.navinet.net> Date: Sun, 23 Jan 2000 18:58:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000123151945.K20886@drama.navinet.net> Forrest Aldrich writes: : Where are we with getting PCCARD support, such as the : 3COM MegaHertz (3CCFEM556 B) card in the mainstream : distribution? Should be there already. If it isn't, then contact me and we'll talk. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 18: 1: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id AD8DF15249 for ; Sun, 23 Jan 2000 18:00:55 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id SAA97896; Sun, 23 Jan 2000 18:59:29 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id SAA47756; Sun, 23 Jan 2000 18:59:56 -0700 (MST) Message-Id: <200001240159.SAA47756@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: PCCARD support Cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 23 Jan 2000 20:06:46 EST." References: Date: Sun, 23 Jan 2000 18:59:56 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : On Sun, 23 Jan 2000, Forrest Aldrich wrote: : > Where are we with getting PCCARD support, such as the 3COM MegaHertz : > (3CCFEM556 B) card in the mainstream distribution? : : Can you use the output of 'pccardc dumpcis' to construct an entry for : /etc/pccard.conf and try the 'ep' driver to see if it will work? : : I suspect it will. I suspect it will too, unless the 'B' changed the id number, in which case if_ep_pccard.c may need to be tweaked. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 18:24:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id BD32415607; Sun, 23 Jan 2000 18:24:25 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA02060; Sun, 23 Jan 2000 21:24:19 -0500 (EST) (envelope-from wollman) Date: Sun, 23 Jan 2000 21:24:19 -0500 (EST) From: Garrett Wollman Message-Id: <200001240224.VAA02060@khavrinen.lcs.mit.edu> To: Peter Jeremy Cc: FreeBSD CURRENT Mailing List , doc@FreeBSD.ORG Group-Reply-To: doc@freebsd.org Folowup-To: doc@freebsd.org Subject: Re: With feature freeze being in place In-Reply-To: <00Jan24.111112est.115220@border.alcanet.com.au> References: <20000122210136.B18600@daemon.ninth-circle.org> <00Jan24.111112est.115220@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Comparing LINT and GENERIC is made more difficult by the significantly > different ordering. Is there some good reason for this, or would an > offer of GENERIC re-written into the same order as LINT be accepted? Speaking as the person who attempted to impart some semblance of order to LINT after it last outgrew its britches.... LINT was organized so as to group related devices together, along with their options. It is not particularly attempting to ape GENERIC (or vice versa!) but was rather organized so as to assist Jane User in locating the obscure option she needs to make the mumblefrotz driver gronkulate properly. Of course, at the same time, it's also trying to be a tool to enhance test coverage. So, generally speaking, options that users might need to set should be described near the devices or subsystems to which they pertain. Options that users don't need to set shouldn't exist at all. In general, the descriptions should be succinct and descriptive in nature; for more information, the user should be directed to a manual page. (IWBRNI the config manual were updated with information about how config works now, and descriptions of all the options and devices were added. Any troff weenies out there looking to make a heroic landing on SMM:02 atoll?) > Also, what is the best approach to submitting documentation for the > `undocumented' options in LINT? Organized them usefully, and send in one giant patch. Then nag people for a few months (updating the giant patch as required to merge changes) until it gets committed. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 19:26:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 3981F14F30 for ; Sun, 23 Jan 2000 19:26:52 -0800 (PST) (envelope-from billf@jade.chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 6A4891C41; Sun, 23 Jan 2000 22:26:51 -0500 (EST) Date: Sun, 23 Jan 2000 22:26:51 -0500 From: Bill Fumerola To: David O'Brien Cc: Will Andrews , freebsd-current@FreeBSD.ORG Subject: Re: when is FreeBSD-4.0 up for release ? Message-ID: <20000123222651.D78486@jade.chc-chimes.com> References: <200001212214.QAA17007@cs.rice.edu> <20000121173353.C541@shadow.blackdawn.com> <20000121153318.A43755@dragon.nuxi.com> <20000121190210.A7072@shadow.blackdawn.com> <20000121173420.A44094@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000121173420.A44094@dragon.nuxi.com>; from obrien@NUXI.com on Fri, Jan 21, 2000 at 05:34:20PM -0800 X-Operating-System: FreeBSD 3.2-RELEASE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 21, 2000 at 05:34:20PM -0800, David O'Brien wrote: > So every little date event needs a confirmation?? Why isn't the fact > that JKH didn't resend the event not mean that it is in effect? David, It's been previously stated that the feature freeze (is/was) planned for Jan 15 and would take effect when jkh made the announcement. If he hasn't made the announcement committers (and submitters like Will) are to assume that it hasn't taken place. This is the normal for announcements for freezes for as long as I've been a committer, or as long as I can remember, whichever is shorter. -- Bill Fumerola - Network Architect Computer Horizons Corp - CVM e-mail: billf@chc-chimes.com / billf@FreeBSD.org Office: 800-252-2421 x128 / Cell: 248-761-7272 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 19:32:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 642C414FFC for ; Sun, 23 Jan 2000 19:32:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA15731 for ; Sun, 23 Jan 2000 19:32:31 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA44733 for freebsd-current@FreeBSD.ORG; Sun, 23 Jan 2000 19:32:32 -0800 (PST) (envelope-from obrien) Date: Sun, 23 Jan 2000 19:32:32 -0800 From: "David O'Brien" To: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Message-ID: <20000123193232.A44712@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <86duop$2n8d$1@atlantis.rz.tu-clausthal.de> <200001230926.KAA81850@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001230926.KAA81850@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Sun, Jan 23, 2000 at 10:26:48AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 23, 2000 at 10:26:48AM +0100, Oliver Fromme wrote: > > Saving 10% or 20% on disk space is not worth wasting >= 10 times more > CPU time than gzip. Disk space is cheap nowadays, but upgrading to a > CPU that is 10 times faster is not. And just how do I increase the space on a CDROM??? Go look how many port distribution files on your last CDROM set were in bzip2 format -- there is a reason for that. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 19:45: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 68ACB1517F; Sun, 23 Jan 2000 19:45:03 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA29969; Sun, 23 Jan 2000 22:45:12 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 23 Jan 2000 22:45:12 -0500 (EST) From: Chuck Robey To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-Reply-To: <20000123193232.A44712@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jan 2000, David O'Brien wrote: > On Sun, Jan 23, 2000 at 10:26:48AM +0100, Oliver Fromme wrote: > > > > Saving 10% or 20% on disk space is not worth wasting >= 10 times more > > CPU time than gzip. Disk space is cheap nowadays, but upgrading to a > > CPU that is 10 times faster is not. > > And just how do I increase the space on a CDROM??? > Go look how many port distribution files on your last CDROM set were in > bzip2 format -- there is a reason for that. David, no one is arguing if bzip2 is or is not a good tool, nor are they arguing if it's good for ports. The answer to both those arguments is very obviously "yes". The argument was whether, currently, bzip2 should be placed in the source tree for the base system. We *don't* need two compressors, and (again currently) gzip is overwhelmingly more popular at ftp sites than bzip2. Furthermore bzip2 has drawbacks for running on the core system, most especially for small ones. I don't need to go over those, you already know them. Lifting those restrictions is not necessary for the base system, seeing as it would have fatal drawbacks for small systems which would see no help from bzip2 (small systems don't have ports). It is a very good thing to have bzip2 on your system, but it's *not* a requirement. Like I said before, most of the same arguments apply to, say, emacs. You'd have to be nuts (if you ran a good sized system) not to have bzip2, but it's just not a requirement. Having a compressor at all is the requirement, and gzip currently is better for that. Ask me again in 18 months, maybe bzip2 will use less memory and be faster, and it's quite likely that it will be far more popular at ftp sites. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 19:46:49 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 664) id E1F0E15242; Sun, 23 Jan 2000 19:46:47 -0800 (PST) Date: Sun, 23 Jan 2000 19:46:47 -0800 From: David O'Brien To: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Message-ID: <20000123194647.A5472@hub.freebsd.org> Reply-To: obrien@freebsd.org References: <86duop$2n8d$1@atlantis.rz.tu-clausthal.de> <200001230926.KAA81850@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <200001230926.KAA81850@dorifer.heim3.tu-clausthal.de>; from Oliver Fromme on Sun, Jan 23, 2000 at 10:26:48AM +0100 X-Operating-System: FreeBSD 3.4-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 23, 2000 at 10:26:48AM +0100, Oliver Fromme wrote: > (I once tried to compress our FreeBSD ISO images with bzip2, > just to compare the space savings with gzip. I aborted the > experiment after 6 hours (!). gzip took about 30 minutes. > Consequently, bzip2 was considered unusable and went into the > trash can.) Am I the only one that uses UNIX as a multitasking OS? nice the bzip2 process by 20 and background it. Geez. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 20:20:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from tomts2-srv.bellnexxia.net (tomts2.bellnexxia.net [209.226.175.140]) by hub.freebsd.org (Postfix) with ESMTP id 1055015110 for ; Sun, 23 Jan 2000 20:20:06 -0800 (PST) (envelope-from hoek@FreeBSD.org) Received: from localhost.nowhere ([206.172.235.114]) by tomts2-srv.bellnexxia.net (InterMail vM.4.01.02.07 201-229-116-107) with ESMTP id <20000124042003.IEAZ26813.tomts2-srv.bellnexxia.net@localhost.nowhere>; Sun, 23 Jan 2000 23:20:03 -0500 Received: (from tim@localhost) by localhost.nowhere (8.9.3/8.9.1) id XAA86497; Sun, 23 Jan 2000 23:19:24 -0500 (EST) (envelope-from tim) Date: Sun, 23 Jan 2000 23:19:24 -0500 From: Tim Vanderhoek To: Warner Losh Cc: Brian Somers , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000123231924.A81831@mad> References: <200001231303.NAA01359@hak.lan.Awfulhak.org> <200001240156.SAA47712@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <200001240156.SAA47712@harmony.village.org>; from Warner Losh on Sun, Jan 23, 2000 at 06:56:39PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 23, 2000 at 06:56:39PM -0700, Warner Losh wrote: > > Each host gets a value of 1 (unless you go in and tweak it). Hosts > are tried in order of their values and in some unspecified order in [...] > Each time you successfully connect, you get a bonus of B. I think you need to keep an element of randomness to prevent "good enough" from defeating "best". Bonus B should be weighted by wire speed. I don't know how to make cvsup spit this out when in batch mode. This isn't exactly the algorithm you described. Finding differences is left as an exercise. Acceptability of the constants chosen for the algorithm varies with expected usage pattern of script. This is the type of thing that should really be done in cvsup itself, but I don't feel like learning Modula-3... :) I disclaim responsibility for any stupid errors. All subtle errors are completely my fault. PS: I don't believe this script will work under Linux. Oops. ;-) Sample cvshosts.dat file: 50 cvsup1.freebsd.org 50 cvsup2.freebsd.org 50 cvsup3.freebsd.org 50 cvsup4.freebsd.org 50 cvsup5.freebsd.org 50 cvsup6.freebsd.org 50 cvsup7.freebsd.org 50 cvsup8.freebsd.org And the script, #! /bin/sh DATFILE=cvshosts.dat if [ -z "$1" ]; then fairings=$( (while read -t 0 host do if [ "${host%%[ ]*}" -eq 0 ] then continue fi fairings="${fairings} $((${host%% *} * $(jot -r 1 5 9) + $(jot -r 1 1 3))) ${host#*[ ]}" done; echo "${fairings}") < ${DATFILE}) hosts=`echo "$fairings" | sort -rn | awk '{print $2}'` else hosts=$1 shift fi # Potential security problem, probably trap 'rm -f /tmp/cvshosts.dat.$$' 0 cp $DATFILE /tmp/cvshosts.dat.$$ echo "Will try hosts $(echo $hosts)" for host in $hosts do echo "Using host $host" if cvsup -1 -P m -s -g ~/bin/sup/fbsd-supfile -L 2 -h $host then # 1 works fairly well as a 2, also perl -pi -e \ 's/^(\d+)[ \t]+'"$host"'[ \t]*$/int (($a=$1+1)>100?10:$a) . "'" $host"'"/e' \ $DATFILE exit; else perl -pi -e \ 's/^(\d+)[ \t]+'"$host"'[ \t]*$/int (($a=$1-$1\/6)<1?1:$a) . "'" $host"'"/e' \ $DATFILE fi done mv /tmp/cvshosts.dat.$$ $DATFILE trap 0 -- Signature withheld by request of author. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 20:21:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from drama.navinet.net (drama.navinet.net [216.67.14.8]) by hub.freebsd.org (Postfix) with ESMTP id E430214F0C for ; Sun, 23 Jan 2000 20:21:32 -0800 (PST) (envelope-from forrie@drama.navinet.net) Received: (from forrie@localhost) by drama.navinet.net with id e0O4LVI21059 for freebsd-current@freebsd.org; Sun, 23 Jan 2000 23:21:31 -0500 (EST) Date: Sun, 23 Jan 2000 23:21:31 -0500 From: Forrest Aldrich To: freebsd-current@freebsd.org Subject: SMP detection Message-ID: <20000123232131.N20886@drama.navinet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a Dell PowerEdge 1300 with dual Pentium II / 400mhz processors installed. However, upon installing today's snapshot of 4.0, the dmesg output doesn't seem to detect the second processor. I wonder if there is a problem here, or if I might have a hardware issue. Thx. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 20:35:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from MailAndNews.com (MailAndNews.com [199.29.68.160]) by hub.freebsd.org (Postfix) with ESMTP id 5A2F815195 for ; Sun, 23 Jan 2000 20:35:48 -0800 (PST) (envelope-from mheffner@mailandnews.com) Received: from muriel.penguinpowered.com [208.138.198.103] (mheffner@mailandnews.com); Sun, 23 Jan 2000 23:35:43 -0500 X-WM-Posted-At: MailAndNews.com; Sun, 23 Jan 00 23:35:43 -0500 Content-Length: 708 Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <388B9084.B988A990@freenet.co.uk> Date: Sun, 23 Jan 2000 23:37:35 -0500 (EST) Reply-To: Mike Heffner From: Mike Heffner To: Alex Subject: Re: ATA CDR problems Cc: FreeBSD-current , Cc: FreeBSD-current , Mike Heffner Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Jan-2000 Alex wrote: | | | If you're running -current, try the new burncd program (man burncd will | tell you more). | Alright, I used the burncd program, and it seems to burn the cd correctly. Unfortunately, I can't mount it in any other drive. I can mount/read it fine in the cdr drive. When burncd started I did get this error again: acd1: READ_TOC - ILLEGAL REQUEST asc=24 ascq=00 error=00 but it proceeded without any problems. When I try to mount it in any other drive I get: cd9660: Device busy Any ideas? --------------------------------- Mike Heffner Fredericksburg, VA ICQ# 882073 Date: 23-Jan-2000 Time: 23:29:34 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 20:38:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from MailAndNews.com (MailAndNews.com [199.29.68.160]) by hub.freebsd.org (Postfix) with ESMTP id 51DD114D79 for ; Sun, 23 Jan 2000 20:38:52 -0800 (PST) (envelope-from mheffner@mailandnews.com) Received: from muriel.penguinpowered.com [208.138.198.103] (mheffner@mailandnews.com); Sun, 23 Jan 2000 23:38:47 -0500 X-WM-Posted-At: MailAndNews.com; Sun, 23 Jan 00 23:38:47 -0500 Content-Length: 575 Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000123232131.N20886@drama.navinet.net> Date: Sun, 23 Jan 2000 23:40:40 -0500 (EST) Reply-To: Mike Heffner From: Mike Heffner To: Forrest Aldrich Subject: RE: SMP detection Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Jan-2000 Forrest Aldrich wrote: | I have a Dell PowerEdge 1300 with dual Pentium II / 400mhz processors | installed. However, upon installing today's snapshot of 4.0, the dmesg | output doesn't seem to detect the second processor. I wonder if there | is a problem here, or if I might have a hardware issue. | Did you config/install a custom kernel? I don't think SMP is on by default. --------------------------------- Mike Heffner Fredericksburg, VA ICQ# 882073 Date: 23-Jan-2000 Time: 23:39:58 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 20:56:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from chiba.3jane.net (chiba.3jane.net [207.170.70.27]) by hub.freebsd.org (Postfix) with ESMTP id 69FC61585F for ; Sun, 23 Jan 2000 20:56:53 -0800 (PST) (envelope-from damon@chiba.3jane.net) Received: from chiba.3jane.net (localhost [127.0.0.1]) by chiba.3jane.net (8.9.1a/8.9.1) with ESMTP id WAA25932; Sun, 23 Jan 2000 22:57:04 -0600 (CST) Message-Id: <200001240457.WAA25932@chiba.3jane.net> To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: SMP detection In-reply-to: <20000123232131.N20886@drama.navinet.net> References: <20000123232131.N20886@drama.navinet.net> Comments: In-reply-to Forrest Aldrich message dated "Sun, 23 Jan 2000 23:21:31 -0500." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <25929.948689824.1@chiba.3jane.net> Date: Sun, 23 Jan 2000 22:57:04 -0600 From: "Damon M. Conway" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Forrest Aldrich wrote: >I have a Dell PowerEdge 1300 with dual Pentium II / 400mhz processors >installed. However, upon installing today's snapshot of 4.0, the dmesg >output doesn't seem to detect the second processor. I wonder if there >is a problem here, or if I might have a hardware issue. have you recompiled the kernel to enable SMP? the GENERIC kernel does not support SMP AFAIK. damon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 20:58:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 51474158D1 for ; Sun, 23 Jan 2000 20:58:08 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:L77xthDu81M0YIj4VmdSa7MRDhYUVgw4@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id NAA18040; Mon, 24 Jan 2000 13:57:44 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id OAA20809; Mon, 24 Jan 2000 14:03:19 +0900 (JST) Message-Id: <200001240503.OAA20809@zodiac.mech.utsunomiya-u.ac.jp> To: Donn Miller Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Moused hanging... In-reply-to: Your message of "Sun, 23 Jan 2000 14:13:17 EST." References: Date: Mon, 24 Jan 2000 14:03:18 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi, I've noticed a strange problem with vidcontrol and moused recently >with current. I also had the same problem about 3 weeks back, and it >doesn't seem to be occurring all that regularly. What type of mouse is it, PS/2, serial, or USB? Is the power supply in your system big enough? Is the mouse's cable and connector look OK? >Here's what I was doing: I had just exited out of X, XFree86 Version >3.9.17. I had two sessions of bladeenc going simultaneously (if that even >matters). I'm guessing maybe the issue is with the PCI bus being accessed >by moused and the ATA driver at the same time, since bladeenc does >generate some disk activity. Anyway, I heard a `pop' through my speakers, >and at the same time, moused went dead. I cannot immediately see why only the mouse suddenly died, while the rest of the system was healthy, >I su'd to root, killed and >restarted moused. Please try `kill -HUP' to moused next time. This will make moused reopen the mouse port. >I could not get my moused cursor back (tried vidcontrol >-m off ; vidcontrol -m on a couple of times). I never heard this before. When did you make this kernel? Would you tell me the revision number of /sys/dev/syscons/syscons.c and /sys/dev/syscons/scmouse.c? >The only way I could get moused to work again was to >reboot. (???) Actually, this is a minor issue, but it is an >inconvenience, since I have to reboot to get vidcontrol to work >again. I'm sure some people have seen this. The last time this happened, >my mouse in X stopped responding. This time, though, no X was running. > >As for the cause, I'm sure it is a PCI/ISA bus issue. I am not sure. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 21:30:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0DA6315799 for ; Sun, 23 Jan 2000 21:30:23 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id VAA16202; Sun, 23 Jan 2000 21:30:22 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id VAA45470; Sun, 23 Jan 2000 21:30:23 -0800 (PST) (envelope-from obrien) Date: Sun, 23 Jan 2000 21:30:23 -0800 From: "David O'Brien" To: Dag-Erling Smorgrav Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Message-ID: <20000123213022.B44712@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001230222.SAA18355@salsa.gv.tsc.tdk.com> <20000123141413.A49567@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from des@flood.ping.uio.no on Sun, Jan 23, 2000 at 08:21:12PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 23, 2000 at 08:21:12PM +0100, Dag-Erling Smorgrav wrote: Taking my 243662 KB ~/Mail: gzip -9 every file: 80420 KB bzip2 -9 every file: 70034 KB tar ~/Mail and gzip -9: 78840 KB (4m37s) tar ~/Mail and bzip2 -9: 68960 KB (14m29s) Who cares if it took longer, I enjoy the better compression and I'm not running Winloose, so I actually *CAN* run this in the background. I certainly was not idle while Bzip2 was compressing. > Using it for one-shot compression (e.g. compressing > backup archives, or in a gather-compress-transfer-decompress-process > pipeline to save bandwidth) is downright stupid unless the cost of > storing or transferring the compressed data is unusually high. Feh. Your opinion. Why is it stupid? When is the cost of transfer not high? Most at home only have 53Kbps download speed. I can start the compression of what I want to take home before I leave the lab, by the time I'm home, it is done and I start the download. I Bzip2 *everything*. When I moved to Bzip2 a year ago, I bzip2'ed and gzip'ed every to keep the smaller of the two. Only 2% of my bzip2'ed files were larger. I don't ever bother comparing anymore. > Not only is it slower (and more memory-hungry), but it was designed and > optimized for compressing text. The less text-like the input is, the > worse bzip2 fares; Lets look at the Ports distfiles on the FreeBSD CDROM: I grabbed a few -- the kde stuff, GCC, qt, rxvt, tin, xchat: the BZIP'ed versions = 35625 Kbytes the GZIP'ed versions = 47593 Kbytes a savings of 11MB on a small sample size. The 3.1 CDROM set had 946M of packages. If these had been bzip2'ed, it would have taken 843M. [ BTW, while downloading the KDE files looks like I was saving significant download time (and this was over 10Mbit Ethernet over an OC3 pipe to the Internet)] kdeadmin-1.1.2.tar.bz2: 722195 bytes received in 26.38 seconds, 26.73 kB/s. kdeadmin-1.1.2.tar.gz: 1175621 bytes received in 44.44 seconds, 25.84 kB/s. kdebase-1.1.2.tar.bz2: 7181379 bytes received in 219.63 seconds, 31.93 kB/s. kdebase-1.1.2.tar.gz: 9178899 bytes received in 416.31 seconds, 21.53 kB/s. kdegames-1.1.2.tar.bz2: 2268814 bytes received in 82.58 seconds, 26.83 kB/s. kdegames-1.1.2.tar.gz: 2965071 bytes received in 136.58 seconds, 21.20 kB/s. kdegraphics-1.1.2.tar.bz2: 1759634 bytes received in 69.06 seconds, 24.88 kB/s. kdegraphics-1.1.2.tar.gz: 2595697 bytes received in 92.14 seconds, 27.51 kB/s. kdelibs-1.1.2.tar.bz2: 1436365 bytes received in 44.88 seconds, 31.26 kB/s. kdelibs-1.1.2.tar.gz: 2001196 bytes received in 69.84 seconds, 27.98 kB/s. kdemultimedia-1.1.2.tar.bz2: 1543683 bytes received in 46.02 seconds, 32.76 kB/ kdemultimedia-1.1.2.tar.gz: 2034164 bytes received in 61.22 seconds, 32.45 kB/s kdenetwork-1.1.2.tar.bz2: 2926118 bytes received in 95.69 seconds, 29.86 kB/s. kdenetwork-1.1.2.tar.gz: 4515573 bytes received in 154.57 seconds, 28.53 kB/s. kdesupport-1.1.2.tar.bz2: 979489 bytes received in 34.06 seconds, 28.08 kB/s. kdesupport-1.1.2.tar.gz: 1209234 bytes received in 30.06 seconds, 39.29 kB/s. kdetoys-1.1.2.tar.bz2: 318167 bytes received in 16.68 seconds, 18.63 kB/s. kdetoys-1.1.2.tar.gz: 378929 bytes received in 9.23 seconds, 40.09 kB/s. kdeutils-1.1.2.tar.bz2: 1603520 bytes received in 41.20 seconds, 38.01 kB/s. kdeutils-1.1.2.tar.gz: 2409082 bytes received in 63.95 seconds, 36.79 kB/s. korganizer-1.1.2.tar.bz2: 737251 bytes received in 27.96 seconds, 25.75 kB/s. korganizer-1.1.2.tar.gz: 922786 bytes received in 19.96 seconds, 45.14 kB/s. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 21:48:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id AFCED1580A; Sun, 23 Jan 2000 21:48:08 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id OAA69049; Mon, 24 Jan 2000 14:47:48 +0900 (JST) To: FreeBSD-current@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG Cc: FreeBSD98-hackers@jp.freebsd.org, nyan@jp.FreeBSD.ORG Subject: Re: indirection in bus space From: KATO Takenori In-Reply-To: Your message of "Fri, 21 Jan 2000 17:40:11 +0900" <20000121174011G.kato@gneiss.eps.nagoya-u.ac.jp> References: <20000121174011G.kato@gneiss.eps.nagoya-u.ac.jp> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000124144718P.kato@gneiss.eps.nagoya-u.ac.jp> Date: Mon, 24 Jan 2000 14:47:18 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 74 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do you have any comment anout the patch? If there isn't any big problem, I hope to commit it to current. Thank you. I wrote: > Do you remember this topic? I have revised the indirection support > patch. What I have changed are: > - to make diff files more readable > - introduce the bus_simple_create_bsh() that creates > a bus_space_handle_tag from a base address. > > I have made PC98 GENERIC98 kernel and i386 LINT kernel and both of > them can be compiled. > > Changed and new files are as follows: > alpha/include/bus.h > i386/include/bus.h > i386/include/bus_at386.h (new file) > i386/include/bus_pc98.h (new file) > i386/i386/nexus.c > i386/isa/isa.c > dev/advansys/adv_isa.c > dev/advansys/adv_pci.c > pci/amd.c > pci/isp_pci.c > > I put new files and diffs as follows: > http://www.FreeBSD.ORG/~kato/busspace/index.html > INDEX > > http://www.FreeBSD.ORG/~kato/busspace/alpha_bus.h.diff > diff between old bus.h and new bus.h > > http://www.FreeBSD.ORG/~kato/busspace/i386_bus.h > i386/include/bus.h > > http://www.FreeBSD.ORG/~kato/busspace/bus_at386.h > i386/include/bus_at386.h > > http://www.FreeBSD.ORG/~kato/busspace/bus_at386.h.diff > diff between old bus.h and bus_at386.h > > http://www.FreeBSD.ORG/~kato/busspace/bus_pc98.h > i386/include/bus_pc98.h > > http://www.FreeBSD.ORG/~kato/busspace/bus_pc98.h.diff > diff between old bus.h and bus_pc98.h > > http://www.FreeBSD.ORG/~kato/busspace/isa.c.diff > diff of i386/isa/isa.c > > http://www.FreeBSD.ORG/~kato/busspace/nexus.c.diff > diff of i386/i386/nexus.c > > http://www.FreeBSD.ORG/~kato/busspace/adv_isa.c.diff > diff of dev/advansys/adv_isa.c > > http://www.FreeBSD.ORG/~kato/busspace/adv_pci.c.diff > diff of dev/advansys/adv_pci.c > > http://www.FreeBSD.ORG/~kato/busspace/amd.c.diff > diff of pci/amd.c > > http://www.FreeBSD.ORG/~kato/busspace/isp_pci.c.diff > diff of pci/isp_pci.c -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 22:11: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 430AB1506F for ; Sun, 23 Jan 2000 22:10:43 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id MAA49504; Mon, 24 Jan 2000 12:10:01 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Mon, 24 Jan 2000 12:10:01 +0600 (NS) From: Max Khon To: John Polstra Cc: current@FreeBSD.org Subject: Re: rtld-elf, java + tya In-Reply-To: <200001231927.LAA19042@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! On Sun, 23 Jan 2000, John Polstra wrote: > > ld-elf.so.1: assert failed: /usr/src/libexec/rtld-elf/lockdflt.c:55 > > If any of you can reproduce this problem fairly reliably, please try > the appended patch for "src/libexec/rtld-elf/lockdflt.c" and let me > know if it solves the problem. Seems that this patch fixed the problem for me. I can not reproduce it anymore. /fjoe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 22:12:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id 21D54158E1; Sun, 23 Jan 2000 22:12:42 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.160]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOT00F4BSXPA2@mta1.snfc21.pbi.net>; Sun, 23 Jan 2000 22:06:07 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id D6664918C9; Sun, 23 Jan 2000 22:05:43 -0800 (PST) Date: Sun, 23 Jan 2000 22:05:43 -0800 (PST) From: Alex Zepeda Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-reply-to: To: Chuck Robey Cc: David O'Brien , freebsd-current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jan 2000, Chuck Robey wrote: > Ask me again in 18 months, maybe bzip2 will use less memory and be > faster, and it's quite likely that it will be far more popular at ftp > sites. Have you looked at the memory usage when you use the -s flag? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 22:19:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id E842115948; Sun, 23 Jan 2000 22:19:30 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id BAA31570; Mon, 24 Jan 2000 01:19:32 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Mon, 24 Jan 2000 01:19:32 -0500 (EST) From: Chuck Robey To: Alex Zepeda Cc: "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 23 Jan 2000, Alex Zepeda wrote: > On Sun, 23 Jan 2000, Chuck Robey wrote: > > > Ask me again in 18 months, maybe bzip2 will use less memory and be > > faster, and it's quite likely that it will be far more popular at ftp > > sites. > > Have you looked at the memory usage when you use the -s flag? No, I said ask me again in 18 months, not NOW. Even if it didn't have the memory problem, gzip has greater compatibility and does the minimum job. It's not required for the base system. It's stupid not to have it in a larger system, but *that's the reason for ports*. Ports are optional, right? > > - alex > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 22:23:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9D1F8152A0; Sun, 23 Jan 2000 22:23:35 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA23836; Mon, 24 Jan 2000 16:53:21 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000123213022.B44712@dragon.nuxi.com> Date: Mon, 24 Jan 2000 16:53:21 +1030 (CST) From: "Daniel O'Connor" To: "David O'Brien" Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi Cc: freebsd-current@FreeBSD.ORG, Dag-Erling Smorgrav Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Jan-00 David O'Brien wrote: > running Winloose, so I actually *CAN* run this in the background. I > certainly was not idle while Bzip2 was compressing. Its pretty annoying waiting for something to compress if you want to do other things that depend on it being compressed.. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 22:27:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta2.snfc21.pbi.net (mta2.snfc21.pbi.net [206.13.28.123]) by hub.freebsd.org (Postfix) with ESMTP id 9A6F2157AE; Sun, 23 Jan 2000 22:27:16 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.160]) by mta2.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOT003CJTU6AM@mta2.snfc21.pbi.net>; Sun, 23 Jan 2000 22:25:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id ABA56918C9; Sun, 23 Jan 2000 22:25:13 -0800 (PST) Date: Sun, 23 Jan 2000 22:25:13 -0800 (PST) From: Alex Zepeda Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi In-reply-to: To: Daniel O'Connor Cc: David O'Brien , freebsd-current@FreeBSD.ORG, Dag-Erling Smorgrav Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Daniel O'Connor wrote: > > On 24-Jan-00 David O'Brien wrote: > > running Winloose, so I actually *CAN* run this in the background. I > > certainly was not idle while Bzip2 was compressing. > > Its pretty annoying waiting for something to compress if you want to do > other things that depend on it being compressed.. tail -f? *vbg* - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 22:36:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 62C1B152A0 for ; Sun, 23 Jan 2000 22:36:19 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id WAA16410; Sun, 23 Jan 2000 22:36:18 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id WAA45891; Sun, 23 Jan 2000 22:36:16 -0800 (PST) (envelope-from obrien) Date: Sun, 23 Jan 2000 22:36:16 -0800 From: "David O'Brien" To: Chuck Robey Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Message-ID: <20000123223616.C44712@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from chuckr@picnic.mat.net on Mon, Jan 24, 2000 at 01:19:32AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 24, 2000 at 01:19:32AM -0500, Chuck Robey wrote: > No, I said ask me again in 18 months, not NOW. Even if it didn't have the > memory problem, gzip has greater compatibility and does the minimum > job. It's not required for the base system. BUT, if we bzip2'ed the base system distribution, we'd be able to fit more Packages on the 1st CDROM, and that is a BIG win. With it in the base system, we could also make pkg_add understand bzip2'ed packages -- again a BIG win as we could then fit more packages on the 1st CDROM. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 23:24:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 6BED61595B for ; Sun, 23 Jan 2000 23:24:15 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA18550; Mon, 24 Jan 2000 08:23:52 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001240723.IAA18550@freebsd.dk> Subject: Re: ATA driver and DVD's In-Reply-To: from Kenneth Wayne Culver at "Jan 23, 2000 07:50:44 pm" To: culverk@wam.umd.edu (Kenneth Wayne Culver) Date: Mon, 24 Jan 2000 08:23:52 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kenneth Wayne Culver wrote: > I recently downloaded and tried xmovie (there is a link to it at > www.opensound.com) and when I tried to play a vob file from the DVD my > xconsole filled with this error: > > acd0: READ_BIG - ILLEGAL REQUEST asc=6f ascq=03 error=00 > > Is this an ATA driver problem? No, that is a DVD forum/consortium problem :) The DVD drive tells you this way that it hasn't be authenticated with the right magic to allow you access to the bitstream bits. You need the css-auth program to enable you to read the data off the DVD. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 23:29:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DDA5B152AD for ; Sun, 23 Jan 2000 23:29:09 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA19777; Mon, 24 Jan 2000 08:29:03 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001240729.IAA19777@freebsd.dk> Subject: Re: D?ISK I/O erros In-Reply-To: <388A3FC7.79D6B082@netquick.net> from TrouBle at "Jan 22, 2000 06:39:51 pm" To: trouble@netquick.net Date: Mon, 24 Jan 2000 08:29:03 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems TrouBle wrote: > this is a brand new 10gig UDMA 66 maxtor.... is this a disk problem via > hardware, or is it a BSD issue with the new code ??? > angelsguardian /kernel: ad0: UDMA CRC WRITE ERROR blk# 7801951 retrying The driver is telling you that the transfers CRC check are not valid and it is retrying the transfer. This can be due to many things: Bad cableing, cable too near field generating devices in the machine, bad disk, bad controller, bad driver... Mostly though this is due to one of the two first items. > ad0: ATA-5 disk at ata0 as master > ad0: 9770MB (20010816 sectors), 19852 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, UDMA33 I need a full verbose bootlog (dmesg) before I can give you any more diagnostic on this.. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 23 23:56:45 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id EFB6F14C89; Sun, 23 Jan 2000 23:56:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E08B01CD6AE for ; Sun, 23 Jan 2000 23:56:39 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 23 Jan 2000 23:56:39 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: Missing ATAPI CD Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since the most recent round of ATA updates, my CDROM is no longer even probed at boot time. device ata0 device atadisk0 device atapicd0 options ATA_STATIC_ID Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #9: Sun Jan 23 23:20:33 PST 2000 kkenn@morden.rebel.net.au:/usr5/src2/src/sys/compile/MORDEN Calibrating clock(s) ... TSC clock: 120041864 Hz, i8254 clock: 1193600 Hz Timecounter "i8254" frequency 1193600 Hz Timecounter "TSC" frequency 120041864 Hz CPU: Pentium/P54C (120.04-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bf real memory = 50331648 (49152K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x0038b000 - 0x02feffff, 46551040 bytes (11365 pages) avail memory = 45232128 (44172K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fac90 bios32: Entry = 0xfb150 (c00fb150) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb180 pnpbios: Found PnP BIOS data at 0xc00fb9f0 pnpbios: Entry = f0000:ba18 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Intel Pentium detected, installing workaround for F00F bug VESA: information block 56 45 53 41 02 01 48 56 00 c0 00 00 00 00 8f 56 00 c0 20 00 de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de de c0 ad de VESA: 29 mode(s) found VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c568f (c000568f) VESA: Tseng Labs ET4000 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=122d8086) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 155787505 bytes/sec bzero() bandwidth = 78076202 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=122d8086) pcib0: on motherboard found-> vendor=0x8086, dev=0x122d, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x122e, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x1230, revid=0x02 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 00003000, size 4 found-> vendor=0x100c, dev=0x3206, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base f0000000, size 24 found-> vendor=0x9004, dev=0x5078, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base 00006000, size 8 map[14]: type 1, range 32, base f1000000, size 12 pci0: on pcib0 CPU Inactivity timer: clocks Peer Concurrency: enabled CPU-to-PCI Write Bursting: enabled PCI Streaming: enabled Bus Concurrency: enabled Cache: 256K pipelined-burst secondary; L1 enabled DRAM: no memory hole, 60 MHz refresh Read burst timing: x-2-2-2/x-3-3-3 Write burst timing: x-3-3-3 RAS-CAS delay: 3 clocks isab0: at device 7.0 on pci0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: enabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: disabled, B: IRQ10, C: IRQ11, D: disabled MB0: disabled, MB1: disabled isa0: on isab0 ata-pci0: port 0x3000-0x300f at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0x3000 ata0: mask=03 status0=50 status1=50 ata0: mask=03 status0=50 status1=50 ata0: devices = 0x3 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0x3008 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=50 status1=00 ata1: devices = 0x9 ata1 at 0x0170 irq 15 on ata-pci0 vga-pci0: mem 0xf0000000-0xf0ffffff irq 11 at device 18.0 on pci0 ahc0: port 0x6000-0x60ff mem 0xf1000000-0xf1000fff irq 10 at device 19.0 on pci0 ahc0: No SEEPROM available. ahc0: Using left over BIOS settings ahc0: aic7850 Single Channel A, SCSI Id=7, 3/255 SCBs ahc0: Downloading Sequencer Program... 408 instructions downloaded Trying Read_Port at 203 Trying Read_Port at 243 CTL0031: start dependant CTL0031: adding irq mask 0x20 CTL0031: adding dma mask 0x2 CTL0031: adding dma mask 0x20 CTL0031: adding io range 0x220-0x22f, size=0x10, align=0x1 CTL0031: adding io range 0x330-0x331, size=0x2, align=0x1 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding dma mask 0xe0 CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: adding io range 0x388-0x38b, size=0x4, align=0x1 CTL0031: start dependant CTL0031: adding irq mask 0x4a0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: adding io range 0x300-0x331, size=0x2, align=0x30 CTL0031: start dependant CTL0031: adding irq mask 0xca0 CTL0031: adding dma mask 0xb CTL0031: adding io range 0x220-0x28f, size=0x10, align=0x20 CTL0031: end dependant CTL2011: start dependant CTL2011: adding irq mask 0x400 CTL2011: adding io range 0x168-0x16f, size=0x8, align=0x1 CTL2011: adding io range 0x36e-0x36f, size=0x2, align=0x1 CTL2011: start dependant CTL2011: adding irq mask 0x800 CTL2011: adding io range 0x1e8-0x1ef, size=0x8, align=0x1 CTL2011: adding io range 0x3ee-0x3ef, size=0x2, align=0x1 CTL2011: start dependant CTL2011: adding irq mask 0x9c00 CTL2011: adding io range 0x100-0x1ff, size=0x8, align=0x8 CTL2011: adding io range 0x300-0x3ff, size=0x2, align=0x2 CTL2011: start dependant CTL2011: adding irq mask 0x8000 CTL2011: adding io range 0x170-0x177, size=0x8, align=0x1 CTL2011: adding io range 0x376-0x376, size=0x1, align=0x1 CTL2011: end dependant PNPffff: adding io range 0x100-0x3f8, size=0x1, align=0x8 CTL7001: adding io range 0x200-0x207, size=0x8, align=0x1 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0: irq maps: 0x61 0x71 0x61 0x61 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x61 0x69 0x61 0x61 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00ff kbdc: RESET_AUX return code:00ff kbdc: RESET_AUX return code:00ff kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <12 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) isa_probe_children: probing PnP devices sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 sbc0: setting card to irq 5, drq 1, 5 pcm0: on sbc0 pcm: setmap c000, 2000; 0xc4e5c000 -> c000 pcm: setmap e000, 2000; 0xc4e5e000 -> e000 ata2: iobase=0x01e8 altiobase=0x03ee bmaddr=0x0000 ata2: mask=00 status0=ff status1=ff unknown0: at port 0x1e8-0x1ef,0x3ee-0x3ef irq 11 on isa0 unknown1: at port 0x100 on isa0 unknown2: at port 0x200-0x207 on isa0 BIOS Geometries: 0:03113f3f 0..785=786 cylinders, 0..63=64 heads, 1..63=63 sectors 1:026a7f3f 0..618=619 cylinders, 0..127=128 heads, 1..63=63 sectors 2:030efe3f 0..782=783 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: ppp0 attached bpf: ppp1 attached new masks: bio 4008c040, tty 4003003a, net 4007003a bpf: lo0 attached Linux-ELF exec handler installed IPsec: Initialized Security Association Processing. IP Filter: initialized. Default = pass all, Logging = enabled IP Filter: v3.3.6 Waiting 2 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ata1-slave : drive wont come ready after identify ata0-master: success setting up WDMA2 mode on PIIX chip ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 ad0: ATA-0 disk at ata0 as master ad0: 1549MB (3173184 sectors), 3148 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, WDMA2 Creating DISK ad0 Creating DISK wd0 ata0-slave: success setting up WDMA2 mode on PIIX chip ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 ad1: ATA-3 disk at ata0 as slave ad1: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 1 depth queue, WDMA2 Creating DISK ad1 Creating DISK wd1 ata1-master: success setting up WDMA2 mode on PIIX chip ad2: piomode=4 dmamode=2 udmamode=2 cblid=0 ad2: ATA-4 disk at ata1 as master ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S ad2: 16 secs/int, 1 depth queue, WDMA2 Creating DISK ad2 Creating DISK wd2 Mounting root from ufs:wd0s2a wd0s1: type 0x6, start 63, end = 1745855, size 1745793 : OK wd0s2: type 0xa5, start 1745856, end = 3173183, size 1427328 : OK start_init: trying /sbin/init ad1s1: type 0x6, start 63, end = 2048255, size 2048193 : OK ad1s2: type 0x5, start 2048256, end = 3072383, size 1024128 : OK ad1s3: type 0xa5, start 3072384, end = 4999679, size 1927296 : OK ad1s5: type 0x6, start 2048319, end = 3072383, size 1024065 : OK ad2: ad_timeout: lost disk contact - resetting ata1: resetting devices .. ata1: mask=01 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip done ad2: ad_timeout: lost disk contact - resetting ata1: resetting devices .. ata1: mask=01 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip done ad2: ad_timeout: lost disk contact - resetting ata1: resetting devices .. ata1: mask=01 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip done ad2: ad_timeout: lost disk contact - resetting ata1-master: success setting up PIO4 mode on generic chip ad2: ad_timeout: trying fallback to PIO mode ata1: resetting devices .. ata1: mask=01 status0=50 status1=00 ata1-master: success setting up WDMA2 mode on PIIX chip done ad2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK ad2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK ad2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK ad2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK ad2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK ad2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK ad2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK ad2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK ad2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK ad2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK ad2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK ad2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK ad2s1: type 0xa5, start 63, end = 4193909, size 4193847 : OK ad2s2: type 0xa5, start 4193910, end = 8387819, size 4193910 : OK ad2s3: type 0xa5, start 8387820, end = 12594959, size 4207140 : OK Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 0: 2:30 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id F13B714A16; Mon, 24 Jan 2000 00:02:26 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E30401CD5FE for ; Mon, 24 Jan 2000 00:02:26 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 24 Jan 2000 00:02:26 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: ipfilter and ipfstat Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, so I finally decided to take the plunge and check out ipfilter. ipf seemed to load my ruleset with no problems, but ipfstat dies with: ioctl(SIOCGETFS): Invalid argument I have remade the 'ipl' target in MAKEDEV, and my kernel and userland are in sync. I have options IPFILTER and options IPFILTER_LOG in the kernel (because the kld wouldn't load for me). What am I doing wrong? Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 0:17:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 933BB15913; Mon, 24 Jan 2000 00:16:16 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA30866; Mon, 24 Jan 2000 09:16:14 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001240816.JAA30866@freebsd.dk> Subject: Re: Missing ATAPI CD In-Reply-To: from Kris Kennaway at "Jan 23, 2000 11:56:39 pm" To: kris@hub.freebsd.org (Kris Kennaway) Date: Mon, 24 Jan 2000 09:16:14 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kris Kennaway wrote: > Since the most recent round of ATA updates, my CDROM is no longer even > probed at boot time. > > device ata0 > device atadisk0 > device atapicd0 > options ATA_STATIC_ID > I know of this, it should be fixed in my next update, I hope to have it ready in a day or two.. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 2:24:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id D1A7F159AF for ; Mon, 24 Jan 2000 02:24:47 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id CAA03909 for ; Mon, 24 Jan 2000 02:24:45 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001241024.CAA03909@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: int10? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Jan 2000 02:24:45 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there a way to initialized a vga card after the system is booted? What I am looking for is to initialize a second vga in my system so that I can run X in a dual headed configuration with XFree86 or to be able to chose which vga card to run X with on my system. Tnks -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 3:16:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 352E014D61 for ; Mon, 24 Jan 2000 03:16:34 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id MAA41036; Mon, 24 Jan 2000 12:16:32 +0100 (CET) (envelope-from olli) Date: Mon, 24 Jan 2000 12:16:32 +0100 (CET) Message-Id: <200001241116.MAA41036@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree X-Newsgroups: list.freebsd-current In-Reply-To: <86ghar$13c3$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote in list.freebsd-current: > On Sun, Jan 23, 2000 at 10:26:48AM +0100, Oliver Fromme wrote: >> >> Saving 10% or 20% on disk space is not worth wasting >= 10 times more >> CPU time than gzip. Disk space is cheap nowadays, but upgrading to a >> CPU that is 10 times faster is not. > > And just how do I increase the space on a CDROM??? Include another CD-ROM. > Go look how many port distribution files on your last CDROM set were in > bzip2 format -- there is a reason for that. I think that's because some people -- especially Linux people, as it seems -- think that bzip is ``new and cool''. :-) >> (I once tried to compress our FreeBSD ISO images with bzip2, >> just to compare the space savings with gzip. I aborted the >> experiment after 6 hours (!). gzip took about 30 minutes. >> Consequently, bzip2 was considered unusable and went into the >> trash can.) > > Am I the only one that uses UNIX as a multitasking OS? > nice the bzip2 process by 20 and background it. Geez. Then it would have taken even longer. Sometimes you have deadlines, and waiting a few hours longer is just not an option. (In this case I finally decided to not even gzip the stuff, because it saved only a few percent of space.) But this is getting off-topic. I think everyone is entitled to his own opinion about the usefulness of bzip2. But I have yet to hear a good reason why it should replace gzip in the base system of FreeBSD. Not that my opinion matters, though. :-) Using bzip2 for the FreeBSD distribution sets would increase the minimum memory requirement by 4 Mbyte (or about 2.5 Mbyte using the -s option of bunzip2, but which doubles decompression time). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 4:39:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 201B014D52 for ; Mon, 24 Jan 2000 04:39:37 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup5-1.iptelecom.net.ua [212.9.227.1]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id OAA01992 for ; Mon, 24 Jan 2000 14:44:52 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id OAA20300 for ; Mon, 24 Jan 2000 14:38:45 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <388C47D4.50FD2100@altavista.net> Date: Mon, 24 Jan 2000 14:38:44 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: current@freebsd.org Subject: VESA modes broken in syscons driver Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It seems that recent kernels have problems initialising syscons in VESA pixel modes. Particularly "vidcontrol VESA_800x600" (actually "vidcontrol VESA_800x600 < /dev/ttyv1" to see what's going on ttyv0) command make my kernel panicing with the following output: Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xc01baee9 stack pointer = 0x10:0xc455fc78 frame pointer = 0x10:0xc455fc84 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 176 (vidcontrol) interrupt mask = tty trap number = 18 panic: integer divide fault Looking into nm /kernel output I figured that 0xc01baee9 pointer is within sc_mouse_move procedure, however I doesn't use moused. Moreover, disabling mouse support in syscons (SC_NO_SYSMOUSE) seems like a temporary workaround to this bug. -Maxim kernel config: device vga0 at isa? port ? conflicts device sc0 at isa? options VESA options SC_PIXEL_MODE options SC_TWOBUTTON_MOUSE options SC_HISTORY_SIZE=1024 dmesg: Preloaded elf kernel "kernel" at 0xc0302000. Preloaded elf module "splash_bmp.ko" at 0xc03020a8. Preloaded splash_image_data "/boot/chuck.bmp" at 0xc030214c. Intel Pentium detected, installing workaround for F00F bug VESA: information block 56 45 53 41 00 02 00 01 00 01 00 00 00 00 40 00 00 01 20 00 00 01 16 01 00 01 31 01 00 01 4a 01 00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 VESA: 20 mode(s) found VESA: v2.0, 2048k memory, flags:0x0, mode table:0xc0242f40 (1000040) VESA: CHIPS 6x554 Super VGA VESA: Chips & Technologies, Inc. 6x554 Display Controller 2 splash: image@0xc028b068, size:481078 bmp_start(): splash_mode:259 splash: image decoder found: splash_bmp vga-pci0: mem 0xfe000000-0xfeffffff at device 4.0 on pci0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x700ff fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 06 e0 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 4:45: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id BEA2E14E0E for ; Mon, 24 Jan 2000 04:45:01 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.6] (helo=mx0.01019freenet.de) by mout0.freenet.de with esmtp (Exim 3.13 #1) id 12Cirb-0006az-00 for current@freebsd.org; Mon, 24 Jan 2000 13:44:59 +0100 Received: from [213.6.51.17] (helo=Magelan.Leidinger.net) by mx0.01019freenet.de with esmtp (Exim 3.13 #1) id 12Cirb-000397-00 for current@freebsd.org; Mon, 24 Jan 2000 13:44:59 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id NAA05941 for ; Mon, 24 Jan 2000 13:43:17 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200001241243.NAA05941@Magelan.Leidinger.net> Date: Mon, 24 Jan 2000 13:43:16 +0100 (CET) From: Alexander Leidinger Subject: gimp 1.1.15 & -current To: current@freebsd.org MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've build gimp-1.1.15 (some minutes ago) on -current (cvsuped yesterday) and I'm getting sigsegv's after the parsing of the plug-in's. Anyone seeing this too? ---snip--- (150) netchild@ttyp0 > gimp gimp: fatal error: sigsegv caught gimp (pid:90581): [E]xit, [H]alt, show [S]tack trace or [P]roceed: s #0 0x28380840 in g_on_error_stack_trace () from /usr/local/lib/libglib12.so.3 #1 0x28380762 in g_on_error_query () from /usr/local/lib/libglib12.so.3 #2 0x80bd953 in gimp_fatal_error () #3 0x811be25 in main () #4 0xbfbfffac in ?? () #5 0x28296a51 in gtk_item_factory_parse_path () #6 0x28296cc7 in gtk_item_factory_create_item () #7 0x811e986 in menus_last_opened_add () #8 0x811d82f in menus_create_item_from_full_path () #9 0x81519ae in plug_in_set_menu_sensitivity () #10 0x814f12c in plug_in_init () #11 0x80712e8 in app_init () #12 0x807031b in gimp_init () #13 0x811bd5e in main () #14 0x8101826 in install_verify () #15 0x811bd27 in main () #16 0x806a2f9 in _start () ---snip--- It's build with CFLAGS= -Os -march=pentiumpro -pipe -Wall -fexpensive-optimizations \ -funroll-loops -fschedule-insns2 could this be the cause (I'm going to try it with "-O -pipe")? Bye, Alexander. P.S.: The helpbrowser gets installed and "pkg_delete gimp-1.1.15" complains about it not being in PLIST (I've removed it because of the mail from cvs-all). -- Closet extrovert. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5: 0:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 101F014F61 for ; Mon, 24 Jan 2000 05:00:02 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:qbWFrm1ndecLSjs9hlaSC4fM+qsyvoWp@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id VAA20673; Mon, 24 Jan 2000 21:58:00 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id WAA06474; Mon, 24 Jan 2000 22:03:36 +0900 (JST) Message-Id: <200001241303.WAA06474@zodiac.mech.utsunomiya-u.ac.jp> To: sobomax@altavista.net Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VESA modes broken in syscons driver In-reply-to: Your message of "Mon, 24 Jan 2000 14:38:44 +0200." <388C47D4.50FD2100@altavista.net> References: <388C47D4.50FD2100@altavista.net> Date: Mon, 24 Jan 2000 22:03:35 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It seems that recent kernels have problems initialising syscons in VESA pixel >modes. Particularly "vidcontrol VESA_800x600" (actually "vidcontrol >VESA_800x600 < /dev/ttyv1" to see what's going on ttyv0) command make my kerne >l >panicing with the following output: [...] >Looking into nm /kernel output I figured that 0xc01baee9 pointer is within >sc_mouse_move procedure, however I doesn't use moused. Moreover, disabling >mouse support in syscons (SC_NO_SYSMOUSE) seems like a temporary workaround to >this bug. Thank you for the report. Apply the following patch to /sys/dev/syscons/scmouse.c and see if it fixes the problem. Kazu Index: scmouse.c =================================================================== RCS file: /src/CVS/src/sys/dev/syscons/scmouse.c,v retrieving revision 1.10 diff -u -r1.10 scmouse.c --- scmouse.c 2000/01/20 13:21:45 1.10 +++ scmouse.c 2000/01/24 12:56:02 @@ -124,8 +124,11 @@ s = spltty(); scp->mouse_xpos = x; scp->mouse_ypos = y; - scp->mouse_pos = scp->mouse_oldpos = - (y/scp->font_size - scp->yoff)*scp->xsize + x/8 - scp->xoff; + if (ISGRAPHSC(scp)) + scp->mouse_pos = scp->mouse_oldpos = 0; + else + scp->mouse_pos = scp->mouse_oldpos = + (y/scp->font_size - scp->yoff)*scp->xsize + x/8 - scp->xoff; splx(s); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:14:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 2870F14F10; Mon, 24 Jan 2000 05:14:19 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:bNlrl7xLujx/ItJLAGZd7vwzyr6/Rqiv@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id WAA19173; Mon, 24 Jan 2000 22:14:17 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id WAA06932; Mon, 24 Jan 2000 22:19:53 +0900 (JST) Message-Id: <200001241319.WAA06932@zodiac.mech.utsunomiya-u.ac.jp> To: current@freebsd.org, hackers@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: [PATCH] Please test the PS/2 mouse driver patch Date: Mon, 24 Jan 2000 22:19:52 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote a patch for the psm driver to add support for several PS/2 mice. It is in http://www.freebsd.org/~yokota/ps2mice-24Jan2000.tar.gz. I am attaching README included in the patch. Thank you. Kazu ---------------------------------------------------------------------- PS/2 mouse driver patch for 4.0-CURRENT 24 January 2000 Kazutaka YOKOTA, yokota@FreeBSD.org This patch adds support for the following PS/2 mice to the psm driver. - Microsoft IntelliMouse Explorer: 2 buttons on top, 2 side buttons and a wheel which also acts as the middle button. - Genius NetScroll Optical: 2 buttons on top, 2 side buttons and a wheel which also acts as the middle button. - MouseSystems SmartScroll Mouse: 3 buttons on top, 1 side button and a wheel. - IBM ScrollPoint: 2 buttons on top and a stick between the buttons. (The stick can perform "horizontal scroll" in W*ndows environment. The horizontal movement of the stick is detected, but is quietly ignored by the psm driver, as we don't have framework to support it.) There are two diff files: ps2mice.diff moused.diff Apply them to 4.0-CURRENT as follows: cd /sys/isa patch < ps2mice.diff cd /usr/src/usr.sbin/moused patch < moused.diff Rebuild the kernel and moused. (Note that you need to copy /sys//include/mouse.h to /usr/include/machine/mouse.h before you rebuild moused.) The following is the list of files modified by this patch. /sys/alpha/include/mouse.h /sys/dev/kbd/atkbdcreg.h /sys/i386/include/mouse.h /sys/isa/psm.c /usr/src/usr.sbin/moused/moused.c This patch is for 4.0-CURRENT. Although I personally have not tested yet, I expect you can apply it to 3.4-STABLE without much difficulty. (FYI, /sys/isa/psm.c is for alpha only in 3.4-STABLE. psm.c for i386 is in /sys/i386/isa in 3.4-STABLE.) Kazu ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:23:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from tama.kosy.gr.jp (tama.kosy.gr.jp [210.141.104.50]) by hub.freebsd.org (Postfix) with ESMTP id BA8DA14F72 for ; Mon, 24 Jan 2000 05:23:34 -0800 (PST) (envelope-from youchan@kosy.gr.jp) Received: from KEI (d0.kosy.gr.jp [192.168.1.30]) by tama.kosy.gr.jp (8.9.3/3.7W) with ESMTP id WAA14443 for ; Mon, 24 Jan 2000 22:23:27 +0900 To: freebsd-current@freebsd.org Subject: problem of burncd From: Yosuke Koshino Message-Id: <200001242225.FIC98286.DBZPOIV@kosy.gr.jp> X-Mailer: Winbiff [Version 2.30PL4] Date: Mon, 24 Jan 2000 22:25:14 +0900 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi,there I install FreeBSD-current-20000122. I tried to write CD-R with burncd, but writing of CD-R is failed at the 'fixate' sequence. At the same time, I got the next error message. The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy". Then, I add "sleep(10);" in 'fixate' code of burncd.c. ------------------ burncd.c ----------------- if (!strcmp(argv[arg], "fixate")) { if (!quiet) fprintf(stderr, "fixating CD, please wait..\n"); > sleep(10); if (ioctl(fd, CDRIOCCLOSEDISK) < 0) err(EX_IOERR, "ioctl(CDRIOCCLOSEDISK)"); break; } ------------------ until here --------------- I have been able to write CD-R normally with burncd now. I think the cause of the failure is that My CDR drive have 4MB cache memory and the synchronize of this cache need about 7 or 8 seconds. Is there the matter of the function "acd_close_track()" of atapi-cd.c in the kernel code ? Hardware: Asustek motherboard with athlon Yamaha CRW8424E-VK atapi CD-R drive (WDMA2) IBM DPTA-372730 atapi Harddisk drive Yosuke Koshino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:32: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id DD08F14D6D for ; Mon, 24 Jan 2000 05:31:59 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id NAA28769 for ; Mon, 24 Jan 2000 13:30:56 GMT (envelope-from n_hibma@webweaving.org) Date: Mon, 24 Jan 2000 13:30:54 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List Subject: APM still ignoring DEVICE_SUSPEND errors Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-591026313-948636885=:4635" Content-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-591026313-948636885=:4635 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: The following patch fixes two things: First, DEVICE_SUSPEND errors are no longer ignored. Since we have defaults for methods we should no longer ignore these errors. Also, DEVICE_RESUME wasn't done when the apm_suspend_system event failed. Second, in the ordering of DEVICE_* and apm_hook_* is not symmetric for suspend and resume. The patch reverses the resume case as well to be apm_hook_resume(...) DEVICE_RESUME(root) Send me some feedback on this. I've mailed the people mentioned in the head of the file, but so far got no response. I would like to make sure we get this right when USB devices are used. Some of them don't suspend and the suspend should be refused in that case. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ --0-591026313-948636885=:4635 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="apm.c.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="apm.c.patch" LS0tIC91c3Ivc3JjL3N5cy9pMzg2L2FwbS9hcG0uYwlUaHUgRGVjICAyIDAz OjEzOjAwIDE5OTkNCisrKyAvaGVpZGkvdXNyL2N1cnJlbnQvc3JjL3N5cy9p Mzg2L2FwbS9hcG0uYwlTdW4gSmFuIDIzIDE0OjA3OjQ5IDIwMDANCkBAIC00 NzMsMTkgKzQ3MywxOSBAQA0KIA0KIAlpZiAoc2MtPmluaXRpYWxpemVkKSB7 DQogCQllcnJvciA9IERFVklDRV9TVVNQRU5EKHJvb3RfYnVzKTsNCi0JCS8q DQotCQkgKiBYWFggU2hvdWxkbid0IGlnbm9yZSB0aGUgZXJyb3IgbGlrZSB0 aGlzLCBidXQgc2hvdWxkDQotCQkgKiBpbnN0ZWFkIGZpeCB0aGUgbmV3YnVz IGNvZGUuICBVbnRpbCB0aGF0IGhhcHBlbnMsDQotCQkgKiBJJ20gZG9pbmcg dGhpcyB0byBnZXQgc3VzcGVuZCB3b3JraW5nIGFnYWluLg0KLQkJICovDQot CQlpZiAoZXJyb3IpDQotCQkJcHJpbnRmKCJERVZJQ0VfU1VTUEVORCBlcnJv ciAlZCwgaWdub3JlZFxuIiwgZXJyb3IpOw0KLQkJYXBtX2V4ZWN1dGVfaG9v ayhob29rW0FQTV9IT09LX1NVU1BFTkRdKTsNCi0JCWlmIChhcG1fc3VzcGVu ZF9zeXN0ZW0oUE1TVF9TVVNQRU5EKSA9PSAwKQ0KLQkJCWFwbV9wcm9jZXNz ZXZlbnQoKTsNCi0JCWVsc2UNCi0JCQkvKiBGYWlsdXJlLCAncmVzdW1lJyB0 aGUgc3lzdGVtIGFnYWluICovDQotCQkJYXBtX2V4ZWN1dGVfaG9vayhob29r W0FQTV9IT09LX1JFU1VNRV0pOw0KKwkJaWYgKGVycm9yKSB7DQorCQkJcHJp bnRmKCJTdXNwZW5kIGZhaWxlZCwgZXJyb3IgJWRcbiIsIGVycm9yKTsNCisJ CQlERVZJQ0VfUkVTVU1FKHJvb3RfYnVzKTsNCisJCX0gZWxzZSB7DQorCQkJ YXBtX2V4ZWN1dGVfaG9vayhob29rW0FQTV9IT09LX1NVU1BFTkRdKTsNCisJ CQlpZiAoYXBtX3N1c3BlbmRfc3lzdGVtKFBNU1RfU1VTUEVORCkgPT0gMCkN CisJCQkJYXBtX3Byb2Nlc3NldmVudCgpOw0KKwkJCWVsc2Ugew0KKwkJCQkv KiBGYWlsdXJlLCAncmVzdW1lJyB0aGUgc3lzdGVtIGFnYWluICovDQorCQkJ CWFwbV9leGVjdXRlX2hvb2soaG9va1tBUE1fSE9PS19SRVNVTUVdKTsNCisJ CQkJREVWSUNFX1JFU1VNRShyb290X2J1cyk7DQorCQkJfQ0KKwkJfQ0KIAl9 DQogfQ0KIA0KQEAgLTU5Myw4ICs1OTMsOCBAQA0KIAkJcmV0dXJuOw0KIA0K IAlpZiAoc2MtPmluaXRpYWxpemVkKSB7DQotCQlERVZJQ0VfUkVTVU1FKHJv b3RfYnVzKTsNCiAJCWFwbV9leGVjdXRlX2hvb2soaG9va1tBUE1fSE9PS19S RVNVTUVdKTsNCisJCURFVklDRV9SRVNVTUUocm9vdF9idXMpOw0KIAl9DQog fQ0KIA0K --0-591026313-948636885=:4635-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:33: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 0C29514A1A for ; Mon, 24 Jan 2000 05:33:01 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup7-31.iptelecom.net.ua [212.9.227.159]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id PAA23531; Mon, 24 Jan 2000 15:38:31 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id PAA20738; Mon, 24 Jan 2000 15:32:20 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <388C5463.C41DB792@altavista.net> Date: Mon, 24 Jan 2000 15:32:19 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: current@freebsd.org Subject: Re: VESA modes broken in syscons driver References: <388C47D4.50FD2100@altavista.net> <200001241303.WAA06474@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > >It seems that recent kernels have problems initialising syscons in VESA pixel > >modes. Particularly "vidcontrol VESA_800x600" (actually "vidcontrol > >VESA_800x600 < /dev/ttyv1" to see what's going on ttyv0) command make my kerne > >l > >panicing with the following output: > [...] > >Looking into nm /kernel output I figured that 0xc01baee9 pointer is within > >sc_mouse_move procedure, however I doesn't use moused. Moreover, disabling > >mouse support in syscons (SC_NO_SYSMOUSE) seems like a temporary workaround to > >this bug. > > Thank you for the report. Apply the following patch to > /sys/dev/syscons/scmouse.c and see if it fixes the problem. > > Kazu > > Index: scmouse.c > [Nice patch omitted] Yes, it solved my problem Thanks! -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:37:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id E43D414D6D for ; Mon, 24 Jan 2000 05:36:58 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA06146; Mon, 24 Jan 2000 14:36:40 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001241336.OAA06146@freebsd.dk> Subject: Re: problem of burncd In-Reply-To: <200001242225.FIC98286.DBZPOIV@kosy.gr.jp> from Yosuke Koshino at "Jan 24, 2000 10:25:14 pm" To: youchan@kosy.gr.jp (Yosuke Koshino) Date: Mon, 24 Jan 2000 14:36:39 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Yosuke Koshino wrote: > Hi,there > > I install FreeBSD-current-20000122. > I tried to write CD-R with burncd, but writing of CD-R is failed > at the 'fixate' sequence. At the same time, I got the next error > message. > The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy". > Then, I add "sleep(10);" in 'fixate' code of burncd.c. You didn't get any other error messages ?? > > I have been able to write CD-R normally with burncd now. > I think the cause of the failure is that My CDR drive have 4MB > cache memory and the synchronize of this cache need about 7 or > 8 seconds. > Is there the matter of the function "acd_close_track()" of > atapi-cd.c in the kernel code ? Hmm, acd_close_track waits uptil 5 mins for the flush to complete that should be more than enough. Maybe you drive return to ready state before it actually did write out the contents, hmmm -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:46:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 861F8158BB for ; Mon, 24 Jan 2000 05:46:42 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 10676 invoked from network); 24 Jan 2000 13:46:41 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 24 Jan 2000 13:46:41 -0000 Message-ID: <388C579F.835E05C0@cvzoom.net> Date: Mon, 24 Jan 2000 08:46:07 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: Moused hanging... References: <200001240503.OAA20809@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > What type of mouse is it, PS/2, serial, or USB? Is the power supply > in your system big enough? Is the mouse's cable and connector look > OK? Well, it's an ISA bus mouse. I bought this thing back in 1994. It's an IMSI mouse. I'll bet this stupid thing could last for 5 more years. :-) > I cannot immediately see why only the mouse suddenly died, while the > rest of the system was healthy, Yeah, I don't know. It happens extremely rarely. Maybe it's because I have an ISA bus mouse. I suppose I really should be using a PS/2 or USB mouse. (BTW, is a PS/2 mouse a type of bus mouse?) > Please try `kill -HUP' to moused next time. This will make moused > reopen the mouse port. What I did was "killall moused". Maybe this is where the problem is. > I never heard this before. When did you make this kernel? > Would you tell me the revision number of /sys/dev/syscons/syscons.c > and /sys/dev/syscons/scmouse.c? Well, I made the kernel about a couple of d/ays back. As for the rev numbers, they're: 1.334 for sys/dev/syscons/syscons.c, and 1.10 for /sys/dev/syscons/scmouse.c. I really don't think it's worth messing with too much, as it happens extremely rarely. Must be a freak occurence. I don't think it's worth pursuing any further, unless other people start complaining of similar problems. I'll try kill -HUP next time, and hopefully that will help... - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:49: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from tama.kosy.gr.jp (tama.kosy.gr.jp [210.141.104.50]) by hub.freebsd.org (Postfix) with ESMTP id F09E41528D for ; Mon, 24 Jan 2000 05:48:56 -0800 (PST) (envelope-from youchan@kosy.gr.jp) Received: from KEI (d0.kosy.gr.jp [192.168.1.30]) by tama.kosy.gr.jp (8.9.3/3.7W) with ESMTP id WAA14736; Mon, 24 Jan 2000 22:48:33 +0900 To: sos@freebsd.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: problem of burncd From: Yosuke Koshino References: <200001242225.FIC98286.DBZPOIV@kosy.gr.jp> <200001241336.OAA06146@freebsd.dk> In-Reply-To: <200001241336.OAA06146@freebsd.dk> Message-Id: <200001242250.DAC50547.DOBPZIV@kosy.gr.jp> X-Mailer: Winbiff [Version 2.30PL4] Date: Mon, 24 Jan 2000 22:50:20 +0900 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Soren Schmidt " wrote: > > The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy". > > Then, I add "sleep(10);" in 'fixate' code of burncd.c. > > You didn't get any other error messages ?? I didn't get no other error message. > Hmm, acd_close_track waits uptil 5 mins for the flush to complete > that should be more than enough. Maybe you drive return to ready > state before it actually did write out the contents, hmmm If it is true, the firmware of my drive has bug. Do you think so? Yosuke Koshino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:52:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id D2ECB14E79 for ; Mon, 24 Jan 2000 05:52:49 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id C734D12368; Mon, 24 Jan 2000 14:52:21 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: <20000121214218.A14016@skriver.dk> Date: Mon, 24 Jan 2000 13:50:24 +0100 To: Garance A Drosihn , Jesper Skriver From: Brad Knowles Subject: Re: Please help spread the CVSup mirror load more evenly Cc: John Polstra , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:43 PM -0500 2000/1/21, Garance A Drosihn wrote: >>And to my best knowledge, BIND does not support anything >>like that. > > Not directly, but I think there are ways you can have it call > some external procedure to do "load-balancing" for an IP > rotary. We talked about doing this to address a problem here > at RPI, but then we figured out an alternate solution so we > didn't really get to the point of implementing it. I don't > know if that external load-balancing procedure is given the > IP address of the host doing the lookup, for instance. There are even ways you can give the same physical IP address to multiple machines, and let routing tricks deal with figuring out the shortest possible path from the client to the server, based on where they are. Take a look at the nameservers for mci.com sometime from multiple different machines around the world. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:53: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id E332F14E91 for ; Mon, 24 Jan 2000 05:52:49 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 07B9612450; Mon, 24 Jan 2000 14:52:26 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001212207.RAA02163@whizzo.transsys.com> References: <20000121190729.C58872@florence.pavilion.net> <200001211911.LAA11701@vashon.polstra.com> <3888CFC4.E130D88D@softweyr.com> <200001212207.RAA02163@whizzo.transsys.com> Date: Mon, 24 Jan 2000 13:51:46 +0100 To: "Louis A. Mamakos" , Wes Peters From: Brad Knowles Subject: Re: Please help spread the CVSup mirror load more evenly Cc: John Polstra , joe@pavilion.net, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:07 PM -0500 2000/1/21, Louis A. Mamakos wrote: > As John mentioned earlier, what your probably most interested in is > patch quality (e.g., minimum packet loss) first and latency second as > far as network characteristics are concerned. Simply measure them if > you choose rather than trying to understand why the latency is what is. > Trying to predict path quality based on observed topology is hard to > do in an automated fashion. Sure, you can employ some simply heuristics > as a human (e.g., don't go through MAE-EAST - it sucks there) and the > occasional traceroute will reduce your candidate list of servers to a > likely set which won't suck and are in the same hemisphere. That's fine. But we can at least automate this simple 20%, can't we? -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:53:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 524CF14F15; Mon, 24 Jan 2000 05:52:56 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id A0D7F1246E; Mon, 24 Jan 2000 14:52:31 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001220123.RAA59410@gndrsh.dnsmgr.net> References: <200001220123.RAA59410@gndrsh.dnsmgr.net> Date: Mon, 24 Jan 2000 14:11:49 +0100 To: "Rodney W. Grimes" , hasty@rah.star-gate.com (Amancio Hasty) From: Brad Knowles Subject: Re: Please help spread the CVSup mirror load more evenly Cc: obrien@FreeBSD.ORG, jdp@polstra.com (John Polstra), current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:23 PM -0800 2000/1/21, Rodney W. Grimes wrote: > You don't even need to modify the protocol. Just write a small > tcp program that times the 3 way handshake on open to all the > servers, take the one with the sortest time and spit that out > for the user to stuff in his cvsupfile. Ahh, yes. But, the latency between the "master" server and the "slave" servers does not necessarily equal the latency between the cvsup client and the master or slave servers, and you want to be able to make intelligent choices based on more than *just* the network latency between the cvsup client and the servers -- if one is very close, but that one happens to be cvsup1 and is overloaded most of the time, then you want to be able to choose other servers that might not be quite so close, but which are much more lightly loaded. Small numbers of "test" data packets tell you very little about what the overall network performance is going to be like between any two sites -- you may have lots of highly bursty traffic on one route and a slightly higher latency but much more consistent level of traffic on another route. You may have small packets flying through a particular network, but when you go to actually transfer any data, you find that you get huge percentages of drops on large packets. You may have a very lightly loaded 64KB line between you and your first choice which shows up fantastically well on the "test" (both low latency and low quantity of drops), but which starts to suck huge boulders when it comes to actually transferring data. There are a lot of factors to be considered, and it seems to me that the best thing is to have some more intelligence in the client, so that it can do at least a first approximation as to network latency and available bandwidth between it and the various servers, and then this could be augmented by additional information that could be provided by cooperating servers that feed each other information about the status of the overall network from their perspective, etc.... -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:56:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 71BE414D43; Mon, 24 Jan 2000 05:56:18 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id F22BC12417; Mon, 24 Jan 2000 14:52:36 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001220500.WAA17674@harmony.village.org> References: <20000121180914.C44132@dragon.nuxi.com> <20000121173923.A44132@dragon.nuxi.com> <200001220500.WAA17674@harmony.village.org> Date: Mon, 24 Jan 2000 14:15:21 +0100 To: Warner Losh , obrien@FreeBSD.ORG From: Brad Knowles Subject: Re: Please help spread the CVSup mirror load more evenly Cc: Chuck Robey , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:00 PM -0700 2000/1/21, Warner Losh wrote: > Hmmm. A thought just occurred to me. There's no need to measure > these things. Lookup all the IP addresses. Do a non blocking > connection to each of these machines. First one to come back with the > REL16_1 response wins, and all the others get closed and you use that > one. Doesn't work. There might be a very low latency but low-bandwidth connection between you and one of the servers, when you (and everyone else) would be better off if you instead connected to a server that shows slightly higher latency but has significantly more bandwidth (or less packet loss, or a less loaded server on the other end, etc...). IMO, there are just too many factors to be considered to apply any one simplistic solution. You need more intelligence on both ends.... -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:57:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 2D52F14BEF; Mon, 24 Jan 2000 05:57:33 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 14A2E123FF; Mon, 24 Jan 2000 14:52:47 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <20000122233433.A2555@patho.gen.nz> References: <200001220021.QAA22981@rah.star-gate.com> <200001220123.RAA59410@gndrsh.dnsmgr.net> <20000122233433.A2555@patho.gen.nz> Date: Mon, 24 Jan 2000 14:17:54 +0100 To: Joe Abley , "Rodney W. Grimes" From: Brad Knowles Subject: Re: Please help spread the CVSup mirror load more evenly Cc: Amancio Hasty , obrien@FreeBSD.ORG, John Polstra , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:34 PM +1300 2000/1/22, Joe Abley wrote: > This should give you a relative performance metric between the servers > you measured, hopefully with local network performance variations > cancelled out by the fact that all tests are run around the same time. This is a really cool idea! Are you going to be writing some code to do this for us? ;-) -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 5:57:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 8654A15542 for ; Mon, 24 Jan 2000 05:57:53 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id CA3B61242C for ; Mon, 24 Jan 2000 14:52:49 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001241116.MAA41036@dorifer.heim3.tu-clausthal.de> References: <200001241116.MAA41036@dorifer.heim3.tu-clausthal.de> Date: Mon, 24 Jan 2000 14:47:52 +0100 To: freebsd-current@FreeBSD.ORG From: Brad Knowles Subject: Re: bzip2 in src tree Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:16 PM +0100 2000/1/24, Oliver Fromme wrote: > Using bzip2 for the FreeBSD distribution sets would increase > the minimum memory requirement by 4 Mbyte (or about 2.5 Mbyte > using the -s option of bunzip2, but which doubles decompression > time). I really don't see what everyone is getting all worked up about. Okay, we believe that bzip2 is probably going to be somewhat better at compressing the ports tarballs (and presumably other tarballs), but it takes longer to run (both to compress and uncompress?), and presumably requires both more memory and more CPU. But gzip is the established standard, and of all the vendors I know of, only Sun is stupid enough to ship an OS that doesn't have gzip installed on their base system. It's certainly the most backwards compatible, and likely to be the best solution for an install floppy or for running on an older machine. Can't we do both? Use gzip on the install floppy, but include bzip2 in /usr/src, and make sure that all the various programs that deal with tarballs and gzip'ed tarballs can also deal with bzip2 tarballs (including in the ports system)? I mean, if it's in /usr/src, and we have both gzip & bzip2 installed on the system, it's up to the user to choose which they prefer and use most of the time, right? And the only cost is the slight expansion of the amount of disk space required to store the source code in /usr/src and the binaries in /usr/bin, as opposed to most people having the port for it installed, with the binaries resident in /usr/local/bin? This can be a win-win situation, can't it? -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 6: 6:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from m2.cs.berkeley.edu (m2.CS.Berkeley.EDU [128.32.45.178]) by hub.freebsd.org (Postfix) with ESMTP id 0B30314E79 for ; Mon, 24 Jan 2000 06:06:33 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-14.ix.netcom.com [209.109.235.14]) by m2.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id GAA76513; Mon, 24 Jan 2000 06:05:52 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id GAA23462; Mon, 24 Jan 2000 06:04:00 -0800 (PST) To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: sigisempty? References: From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) Date: 24 Jan 2000 06:03:40 -0800 In-Reply-To: Bruce Evans's message of "Thu, 20 Jan 2000 08:27:18 +1100 (EST)" Message-ID: Lines: 28 X-Mailer: Gnus v5.7/Emacs 20.5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Bruce Evans * The correct answer seems to be "you can't do that" :-). Even checking Err. Now why am I not surprised that you said that? ;) Anyway, I have committed the following patch submitted by Alexander Langer. It has a nice feature of working for both -current and -stable without any additional #ifdef's. I hope it's ok. Satoshi ======= --- lib/libxview/notify/ntfy.h.orig Tue Jun 29 07:18:14 1993 +++ lib/libxview/notify/ntfy.h Mon Jan 10 15:50:53 2000 @@ -188,7 +197,12 @@ #define sigisempty(s) (!(((s)->__sigbits[0]) | ((s)->__sigbits[1]) \ | ((s)->__sigbits[2]) | ((s)->__sigbits[3]))) #else -#define sigisempty(s) (!(*(s))) +static int +sigisempty (sigset_t *s) { + sigset_t n; + bzero(&n, sizeof(sigset_t)); + return (! memcmp(&n, s, sizeof(sigset_t))); +} #endif /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 6:11:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id 3363E14F94 for ; Mon, 24 Jan 2000 06:11:02 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 5772 invoked by uid 1010); 24 Jan 2000 11:14:55 -0000 Date: Mon, 24 Jan 2000 11:14:55 +0000 From: George Cox To: David O'Brien Cc: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) Message-ID: <20000124111455.A5739@extremis.demon.co.uk> References: <20000123223616.C44712@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <20000123223616.C44712@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Sun, Jan 23, 2000 at 10:36:16PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23/01 22:36, David O'Brien wrote: > BUT, if we bzip2'ed the base system distribution, we'd be able to fit > more Packages on the 1st CDROM, and that is a BIG win. With it in the This would indeed be good. Let's also remember that 'tar' has built-in support for bzip2 so it's not as if it would have no other programs to work with it. :-) best; gjvc -- [gjvc] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 6:18:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 38B9014E79 for ; Mon, 24 Jan 2000 06:18:33 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id PAA15926; Mon, 24 Jan 2000 15:18:14 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001241418.PAA15926@freebsd.dk> Subject: Re: problem of burncd In-Reply-To: <200001242250.DAC50547.DOBPZIV@kosy.gr.jp> from Yosuke Koshino at "Jan 24, 2000 10:50:20 pm" To: youchan@kosy.gr.jp (Yosuke Koshino) Date: Mon, 24 Jan 2000 15:18:14 +0100 (CET) Cc: freebsd-current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Yosuke Koshino wrote: > "Soren Schmidt " wrote: > > > The message is "burncd: ioctl(CDRIOCCLOSEDISK) : Device busy". > > > Then, I add "sleep(10);" in 'fixate' code of burncd.c. > > > > You didn't get any other error messages ?? > I didn't get no other error message. OK, it could be a sideeffect of something else going wrong. > > > Hmm, acd_close_track waits uptil 5 mins for the flush to complete > > that should be more than enough. Maybe you drive return to ready > > state before it actually did write out the contents, hmmm > If it is true, the firmware of my drive has bug. Do you think so? Could be, I have a drive with 2M of buffer, and I've never seen it do this, and since the driver waits for the device to get ready before returning from the close_track function, it shouldn't happen. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 6:20:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 0D55C14F68 for ; Mon, 24 Jan 2000 06:20:18 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 12CkLh-0005I6-00; Mon, 24 Jan 2000 06:20:09 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Warner Losh Cc: FreeBSD Current Subject: Re: Please help spread the CVSup mirror load more evenly Message-Id: Date: Mon, 24 Jan 2000 06:20:09 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm hatching in my head a scheme as follows: you may want to take a look at keith moore's work on what he called sonar. there was code, but the internet draft seems to have expired. keith is usually available at Keith Moore . randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 6:20:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51]) by hub.freebsd.org (Postfix) with ESMTP id 452E015145 for ; Mon, 24 Jan 2000 06:20:31 -0800 (PST) (envelope-from sales@powerhousepress.com) Received: from win98-linux (user-38ld45b.dialup.mindspring.com [209.86.144.171]) by smtp7.atl.mindspring.net (8.9.3/8.8.5) with SMTP id JAA18424 for ; Mon, 24 Jan 2000 09:20:28 -0500 (EST) Message-Id: <200001241420.JAA18424@smtp7.atl.mindspring.net> Date: Mon, 24 Jan 2000 09:28:38 -0500 From: "Sales@powerhousepress.com" Subject: Powerhousepress.com Press Release To: "current@freebsd.org" Mime-Version: 1.0 Organization: VisionLink, Inc X-Mailer: GoldMine [4.00.9922] Content-Type: text/rtf; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG {\rtf1\ansi\deff0\deftab720{\fonttbl{\f0\fswiss MS Sans = Serif;}{\f1\froman\fcharset2 Symbol;}{\f2\fswiss\fprq2 Arial;}} {\colortbl\red0\green0\blue0;\red0\green0\blue255;} \deflang1033\pard\plain\f2\fs20 FOR IMMEDIATE RELEASE: \par=20 \par=20 \par CONTACT: \par Jeannette Guillermo \par Powerhousepress.com \par \plain\f2\fs24\cf1\ul www.powerhousepress.com\plain\f2\fs20=20 \par office: (678) 461-8855 \par fax: (404) 753-8257 \par \plain\f2\fs24\cf1\ul = jeannette.guillermo@powerhousepress.com\plain\f2\fs20=20 \par=20 \par=20 \par \plain\f2\fs26\b NEW SMALL PRESS WORKS ALL ANGLES \par \plain\f2\fs20=20 \par=20 \par \plain\f2\fs20\cf1\ul Powerhousepress.com\plain\f2\fs20 , Inc., = headquartered in Atlanta, GA, opens its virtual \par doors on January 25, 2000. A small independent press, it specializes in \par novels, children's stories, self help books, other fiction, collections of \par poetry, and video and audio tape versions of its products. Its intent is \par to produce products with universal appeal. Powerhousepress.com distributes \par through every available channel on the internet, as well as some of the \par traditional brick and mortar methods.=20 \par=20 \par The company is operated by an author/writer - Chief Executive Officer, = Toni Lee;=20 \par retail specialist -Marketing and Sales Director, Jeannette Guillermo; =20 \par computer programmer - Chief Technical Officer, Robert Ryan and \par computer specialist - Chief Information Officer, Kevin Hicks.=20 \par=20 \par In addition to producing original work, \plain\f2\fs20\cf1\ul = Powerhousepress.com\plain\f2\fs20 , Inc., will sell=20 \par e-book versions of self published authors already in print, provide video \par and audio versions of completed work, feature independent brick and mortar \par bookstores in mini-site pages, provide deaf translation versions on video \par of children's titles, and translated electronic versions of all titles in \par Spanish, French, Dutch, German and other languages. \par=20 \par The company will target book clubs, e-book reader owners, special interest \par sites and reader discussion groups. In addition to our website at \par \plain\f2\fs20\cf1\ul http://www.powerhousepress.com/\plain\f2\fs20 , = products published by Powerhousepress.com will be \par available at \plain\f2\fs20\cf1\ul Amazon.com\plain\f2\fs20 , = \plain\f2\fs20\cf1\ul Borders.com\plain\f2\fs20 , \plain\f2\fs20\cf1\ul = barnesandnoble.com\plain\f2\fs20 as well as many \par other. They will also be content providers for Nuvo-Media, and = Booklocker, \par noted e-book distributors \par=20 \par Powerhousepress.com will make its debut, featuring a novel with \par international flavor called Duplicity. After this colorful kickoff, the \par company will release an average of one electronic book every ten weeks = over \par the next eighteen months. The press operates 24 hours a day via internet, \par with phone availability - 9:00 am to 5:00 pm, five days a week, Monday \par through Friday. \par=20 \par=20 \par=20 \par This is a posting from the Powerhousepress.com marketing team. To = unsubscribe, send a blank email with the subject line of "unsubscribe" to = unsubscribe@powerhousepress.com. \par=20 \par } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 6:37: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from m2.cs.berkeley.edu (m2.CS.Berkeley.EDU [128.32.45.178]) by hub.freebsd.org (Postfix) with ESMTP id 463B414F84; Mon, 24 Jan 2000 06:37:02 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca7-14.ix.netcom.com [209.109.235.14]) by m2.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id GAA77883; Mon, 24 Jan 2000 06:36:54 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id GAA23651; Mon, 24 Jan 2000 06:36:44 -0800 (PST) Date: Mon, 24 Jan 2000 06:36:44 -0800 (PST) Message-Id: <200001241436.GAA23651@silvia.hip.berkeley.edu> X-Authentication-Warning: silvia.hip.berkeley.edu: asami set sender to asami@cs.berkeley.edu using -f To: ports@FreeBSD.org Cc: current@FreeBSD.org Reply-To: ports@FreeBSD.org Subject: 4.0-release (ports) schedule From: asami@FreeBSD.org (Satoshi - Ports Wraith - Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Since the 4.0 release is coming up soon, I'd like to remind people to check the build logs and fix what they can. The latest one is in http://bento.FreeBSD.org/errorlogs/errorlogs/e.4.20000123/ There are over 200 broken ports. In particular, there are a few dozen (78 at last count) broken by the gcc upgrade (those marked by "new compiler error"). It doesn't look good, folks. Right now we are only able to build packages for about 2,490 out of the almost 3,000 ports. Also, the freeze is tentatively scheduled for 2000/01/31, the midnight when February starts in U.S. West Coast. That will leave one week and 18 hours. Thanks for your help and happy port-fixing! -PW P.S. Please send fixes via send-pr, not a direct mail to me or the ports list. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 7:21:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 5CBC514E98; Mon, 24 Jan 2000 07:21:03 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id KAA39763; Mon, 24 Jan 2000 10:20:59 -0500 (EST) Date: Mon, 24 Jan 2000 10:20:50 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Satoshi - Ports Wraith - Asami Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: sigisempty? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24 Jan 2000, Satoshi - Ports Wraith - Asami wrote: > Anyway, I have committed the following patch submitted by Alexander > Langer. It has a nice feature of working for both -current and > -stable without any additional #ifdef's. I hope it's ok. > > Satoshi > ======= > --- lib/libxview/notify/ntfy.h.orig Tue Jun 29 07:18:14 1993 > +++ lib/libxview/notify/ntfy.h Mon Jan 10 15:50:53 2000 > @@ -188,7 +197,12 @@ > #define sigisempty(s) (!(((s)->__sigbits[0]) | ((s)->__sigbits[1]) \ > | ((s)->__sigbits[2]) | ((s)->__sigbits[3]))) > #else > -#define sigisempty(s) (!(*(s))) > +static int > +sigisempty (sigset_t *s) { > + sigset_t n; > + bzero(&n, sizeof(sigset_t)); > + return (! memcmp(&n, s, sizeof(sigset_t))); > +} > #endif > > /* > Suggestion: use sigemptyset() rather than bzero(). Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 7:21:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69]) by hub.freebsd.org (Postfix) with ESMTP id 03DFF15032; Mon, 24 Jan 2000 07:21:28 -0800 (PST) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by ckmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id KAA16579; Mon, 24 Jan 2000 10:21:25 -0500 (EST) Received: from njb140bh1.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id KAA02562; Mon, 24 Jan 2000 10:20:52 -0500 (EST) Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2448.0) id ; Mon, 24 Jan 2000 10:21:24 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'freebsd-current@freebsd.org'" Cc: "'freebsd-hackers@freebsd.org'" Subject: BPF bug or not? Date: Mon, 24 Jan 2000 10:21:16 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="koi8-r" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All, I've just found that read from /dev/bpfX never return EAGAIN/EWOULDBLOCK. It means that when you do a non blocking read and there is no data you will always get 0. Does it suppose work this way? A non blocking read from pipe return EAGAIN/EWOULDBLOCK if there is no data and pipe was opened as O_RDWR, and 0 when pipe was opened as O_RDONLY. Thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 7:24: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 2C6E914C80; Mon, 24 Jan 2000 07:24:02 -0800 (PST) (envelope-from bsd@inbox.org) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with ESMTP id KAA13885; Mon, 24 Jan 2000 10:23:10 -0500 (EST) Date: Mon, 24 Jan 2000 10:23:10 -0500 (EST) From: "Mr. K." To: Brad Knowles Cc: "Rodney W. Grimes" , Amancio Hasty , obrien@FreeBSD.ORG, John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why don't we use the download accelerator (http://www.lidan.com/) methodology and make simultaneous connections to the top 4 sites as discovered by ping? :) On Mon, 24 Jan 2000, Brad Knowles wrote: > At 5:23 PM -0800 2000/1/21, Rodney W. Grimes wrote: > > > You don't even need to modify the protocol. Just write a small > > tcp program that times the 3 way handshake on open to all the > > servers, take the one with the sortest time and spit that out > > for the user to stuff in his cvsupfile. > > Ahh, yes. But, the latency between the "master" server and the > "slave" servers does not necessarily equal the latency between the > cvsup client and the master or slave servers, and you want to be able > to make intelligent choices based on more than *just* the network > latency between the cvsup client and the servers -- if one is very > close, but that one happens to be cvsup1 and is overloaded most of > the time, then you want to be able to choose other servers that might > not be quite so close, but which are much more lightly loaded. > > > Small numbers of "test" data packets tell you very little about > what the overall network performance is going to be like between any > two sites -- you may have lots of highly bursty traffic on one route > and a slightly higher latency but much more consistent level of > traffic on another route. > > You may have small packets flying through a particular network, > but when you go to actually transfer any data, you find that you get > huge percentages of drops on large packets. > > You may have a very lightly loaded 64KB line between you and your > first choice which shows up fantastically well on the "test" (both > low latency and low quantity of drops), but which starts to suck huge > boulders when it comes to actually transferring data. > > > There are a lot of factors to be considered, and it seems to me > that the best thing is to have some more intelligence in the client, > so that it can do at least a first approximation as to network > latency and available bandwidth between it and the various servers, > and then this could be augmented by additional information that could > be provided by cooperating servers that feed each other information > about the status of the overall network from their perspective, > etc.... > > -- > These are my opinions and should not be taken as official Skynet policy > _________________________________________________________________________ > |o| Brad Knowles, Belgacom Skynet NV/SA |o| > |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| > |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| > |o| http://www.skynet.be Belgium |o| > \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ > Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. > Unix is very user-friendly. It's just picky who its friends are. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 7:27:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id A4AB41527C for ; Mon, 24 Jan 2000 07:27:05 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id HAA11748; Mon, 24 Jan 2000 07:35:24 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001241535.HAA11748@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: int10? In-reply-to: Your message of "Mon, 24 Jan 2000 02:24:45 PST." <200001241024.CAA03909@rah.star-gate.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Jan 2000 07:35:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there a way to initialized a vga card after the system is booted? > > What I am looking for is to initialize a second vga in my > system so that I can run X in a dual headed configuration > with XFree86 or to be able to chose which vga card > to run X with on my system. The Linux folks claim to be able to work out which VGA card gets initialised with an int10 call; you might want to go look how they do it - we have more or less equivalent infrastructure so once you've worked out how it's done, doing it under FreeBSD should be trivial. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 8:24: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (pC19F54BA.dip0.t-ipconnect.de [193.159.84.186]) by hub.freebsd.org (Postfix) with ESMTP id 04CE715A61; Mon, 24 Jan 2000 08:21:00 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id C9995AB94; Mon, 24 Jan 2000 17:20:49 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id RAA16682; Mon, 24 Jan 2000 17:20:23 +0100 (CET) (envelope-from alex) Date: Mon, 24 Jan 2000 17:20:23 +0100 From: Alexander Langer To: Satoshi - Ports Wraith - Asami Cc: current@FreeBSD.ORG Subject: Re: sigisempty? Message-ID: <20000124172023.B5978@cichlids.cichlids.com> Mail-Followup-To: Satoshi - Ports Wraith - Asami , current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="5vNYLRcllDrimb99" X-Mailer: Mutt 1.0i In-Reply-To: ; from asami@FreeBSD.ORG on Mon, Jan 24, 2000 at 06:03:40AM -0800 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Thus spake Satoshi - Ports Wraith - Asami (asami@FreeBSD.ORG): > Langer. It has a nice feature of working for both -current and > -stable without any additional #ifdef's. I hope it's ok. I now saw Garret Wollman's function. I like the use of the static-vars. The use of sigemptyset makes it more transparenter for later changes, that I hope won't occur, but at the moment it doesn't matter since sigemptyset is int sigemptyset(set) sigset_t *set; { int i; for (i = 0; i < _SIG_WORDS; i++) set->__bits[i] = 0; return (0); } I attached a patch against patch-lo anyways (sorry ;-) Alex -- I doubt, therefore I might be. --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="xview-patch.diff" --- /tmp/xview/patches/patch-lo Thu Jan 20 04:38:25 2000 +++ patch-lo Mon Jan 24 17:14:58 2000 @@ -20,15 +20,17 @@ union wait status; /* Return value from wait3 */ #else SVR4 int status; /* Return value from wait3 */ -@@ -188,7 +197,12 @@ +@@ -188,7 +197,14 @@ #define sigisempty(s) (!(((s)->__sigbits[0]) | ((s)->__sigbits[1]) \ | ((s)->__sigbits[2]) | ((s)->__sigbits[3]))) #else -#define sigisempty(s) (!(*(s))) +static int +sigisempty (sigset_t *s) { -+ sigset_t n; -+ bzero(&n, sizeof(sigset_t)); ++ static sigset_t n; ++ static int emptied = 0; ++ if (!emptied) ++ sigemptyset(&n), emptied++; + return (! memcmp(&n, s, sizeof(sigset_t))); +} #endif --5vNYLRcllDrimb99-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 8:36:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id AA1C715B14; Mon, 24 Jan 2000 08:36:19 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 03CA51254E; Mon, 24 Jan 2000 17:35:28 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Mon, 24 Jan 2000 17:01:55 +0100 To: "Mr. K." From: Brad Knowles Subject: Re: Please help spread the CVSup mirror load more evenly Cc: "Rodney W. Grimes" , Amancio Hasty , obrien@FreeBSD.ORG, John Polstra , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:23 AM -0500 2000/1/24, Mr. K. wrote: > Why don't we use the download accelerator > (http://www.lidan.com/) methodology and make simultaneous connections to > the top 4 sites as discovered by ping? :) As mentioned before, not all sites allow ICMP packets through their networks. In addition, ping only deals with the network latency issue, and not very well at that -- it's only an instantaneous measure. Since cvsup sessions tend to last relatively long periods of time, even if you were to look at just latency, you would want something that would look at minimum, maximum, standard deviation, and median latency over similar relatively long periods of time. Of course, there are also host loading and bandwidth issues, network congestion & drops problems, network route flapping issues, and a whole host of other things that you'd also want to look at. As I said before, I don't think any one simple solution to this problem will do the job. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 9: 3:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from chiba.3jane.net (chiba.3jane.net [207.170.70.27]) by hub.freebsd.org (Postfix) with ESMTP id 46C6314CD4 for ; Mon, 24 Jan 2000 09:03:07 -0800 (PST) (envelope-from damon@chiba.3jane.net) Received: from chiba.3jane.net (localhost [127.0.0.1]) by chiba.3jane.net (8.9.1a/8.9.1) with ESMTP id LAA29953; Mon, 24 Jan 2000 11:02:28 -0600 (CST) Message-Id: <200001241702.LAA29953@chiba.3jane.net> To: Brad Knowles Cc: Garance A Drosihn , Jesper Skriver , John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-reply-to: References: <20000121214218.A14016@skriver.dk> Comments: In-reply-to Brad Knowles message dated "Mon, 24 Jan 2000 13:50:24 +0100." MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <29950.948733347.1@chiba.3jane.net> Date: Mon, 24 Jan 2000 11:02:28 -0600 From: "Damon M. Conway" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: >At 4:43 PM -0500 2000/1/21, Garance A Drosihn wrote: > >>>And to my best knowledge, BIND does not support anything >>>like that. >> >> Not directly, but I think there are ways you can have it call >> some external procedure to do "load-balancing" for an IP >> rotary. We talked about doing this to address a problem here >> at RPI, but then we figured out an alternate solution so we >> didn't really get to the point of implementing it. I don't >> know if that external load-balancing procedure is given the >> IP address of the host doing the lookup, for instance. > > There are even ways you can give the same physical IP address to >multiple machines, and let routing tricks deal with figuring out the >shortest possible path from the client to the server, based on where >they are. Take a look at the nameservers for mci.com sometime from >multiple different machines around the world. however, that would require those ips to be all be controlled by the same network entity (AS). if the aren't, then the complexity and the adminstrative costs of such a method make it totally unworkable. damon -- Damon Conway Black Rock City Ranger...Riding the edge of chaos On the constant path of the Ranger Art To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 9: 5:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E4BD314D61 for ; Mon, 24 Jan 2000 09:05:22 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA11816; Mon, 24 Jan 2000 09:05:21 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA21098; Mon, 24 Jan 2000 09:05:15 -0800 (PST) (envelope-from jdp@polstra.com) Date: Mon, 24 Jan 2000 09:05:15 -0800 (PST) Message-Id: <200001241705.JAA21098@vashon.polstra.com> To: fjoe@iclub.nsu.ru Subject: Re: rtld-elf, java + tya In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Max Khon wrote: > > Seems that this patch fixed the problem for me. > I can not reproduce it anymore. That's good news. Thanks for testing it! I'll commit it later today. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 9:30:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from lindt.urgle.com (lindt.urgle.com [195.173.172.169]) by hub.freebsd.org (Postfix) with ESMTP id 8E28714F79 for ; Mon, 24 Jan 2000 09:30:43 -0800 (PST) (envelope-from mike@urgle.com) Received: from mike by lindt.urgle.com with local (Exim 3.03 #1) id 12CnK3-0007aI-00; Mon, 24 Jan 2000 17:30:39 +0000 Date: Mon, 24 Jan 2000 17:30:39 +0000 From: Mike Bristow To: damieon Cc: freebsd-current@freebsd.org Subject: Re: Neat little DPT utils... Message-ID: <20000124173039.A29120@lindt.urgle.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from d-man@telemere.net on Wed, Jan 19, 2000 at 09:48:33AM -0600 X-Rated: clones, Croatian Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 19, 2000 at 09:48:33AM -0600, damieon wrote: > Greetings, > > I administer several machines running freebsd. Most of > them are running FreeBSD-CURRENT, and all of them have DPT SmartRAID IV > raid controlers. I was looking though LINT and found that it made > reference to a set of tools for working with said cards and happily looked > to install it. The tools are in /usr/src/usr.sbin/dpt. To my shock and > disapointment ( ;( ) They don't compile. When I issue tha make command > this is what I get: Both the utilities and the device they need to talk to in order to get their information got stomped on in the move to CAM, I think. I'm looking at moving them forward to -current - but more so I can learn more about the kernel internals. I originaly thought that it'd be a five minute job - but I somewhat overestimated my abilities and underestimated my workload. From mails exchanged some time ago, Simon Shapiro (sp?) the original author said, IIRC, that he had fixing those utils on his to-do list - but not at the top :( -- Mike Bristow, Geek At Large ``Beware of Invisible Cows'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 9:54:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 6EA0214C4C for ; Mon, 24 Jan 2000 09:54:17 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA19177 for ; Mon, 24 Jan 2000 09:54:17 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA75201 for freebsd-current@FreeBSD.ORG; Mon, 24 Jan 2000 09:54:17 -0800 (PST) (envelope-from obrien) Date: Mon, 24 Jan 2000 09:54:17 -0800 From: "David O'Brien" To: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree Message-ID: <20000124095417.A75151@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <86ghar$13c3$1@atlantis.rz.tu-clausthal.de> <200001241116.MAA41036@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001241116.MAA41036@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Mon, Jan 24, 2000 at 12:16:32PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 24, 2000 at 12:16:32PM +0100, Oliver Fromme wrote: > > And just how do I increase the space on a CDROM??? > > Include another CD-ROM. You are missing the point. The installation CDROM only shows you the packages on that CDROM, this gives newbies the impression we don't have very many packages. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 9:55:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id 7609115264 for ; Mon, 24 Jan 2000 09:55:09 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id MAA16064; Mon, 24 Jan 2000 12:55:04 -0500 (EST) Message-ID: <20000124125504.A15109@netmonger.net> Date: Mon, 24 Jan 2000 12:55:04 -0500 From: Christopher Masto To: Donn Miller , current@FreeBSD.ORG Subject: Re: Moused hanging... References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Donn Miller on Sun, Jan 23, 2000 at 02:13:17PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 23, 2000 at 02:13:17PM -0500, Donn Miller wrote: > Hi, I've noticed a strange problem with vidcontrol and moused recently > with current. I also had the same problem about 3 weeks back, and it > doesn't seem to be occurring all that regularly. > > > Here's what I was doing: I had just exited out of X, XFree86 Version > 3.9.17. I had two sessions of bladeenc going simultaneously (if that even > matters). I'm guessing maybe the issue is with the PCI bus being accessed > by moused and the ATA driver at the same time, since bladeenc does > generate some disk activity. Anyway, I heard a `pop' through my speakers, > and at the same time, moused went dead. I su'd to root, killed and > restarted moused. I could not get my moused cursor back (tried vidcontrol > -m off ; vidcontrol -m on a couple of times). This used to happen to me a lot with my Mouse Systems PS/2 mouse. I blamed it on static. I'm not sure when or why it stopped happening. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 9:55:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 80DDF1532C; Mon, 24 Jan 2000 09:55:50 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id SAA43618; Mon, 24 Jan 2000 18:55:41 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: Alex Zepeda Cc: "Daniel O'Connor" , "David O'Brien" , freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi References: From: Dag-Erling Smorgrav Date: 24 Jan 2000 18:55:40 +0100 In-Reply-To: Alex Zepeda's message of "Sun, 23 Jan 2000 22:25:13 -0800 (PST)" Message-ID: Lines: 16 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda writes: > On Mon, 24 Jan 2000, Daniel O'Connor wrote: > > On 24-Jan-00 David O'Brien wrote: > > > running Winloose, so I actually *CAN* run this in the background. I > > > certainly was not idle while Bzip2 was compressing. > > Its pretty annoying waiting for something to compress if you want to do > > other things that depend on it being compressed.. > tail -f? *vbg* No, because bzip2 doesn't stream very well. It splits the input in blocks of several hundred kB and compresses entire blocks in memory before writing them out. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 10: 6:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from penelope.skunk.org (penelope.skunk.org [208.133.204.51]) by hub.freebsd.org (Postfix) with ESMTP id 3B25F152C0 for ; Mon, 24 Jan 2000 10:06:24 -0800 (PST) (envelope-from ben@penelope.skunk.org) Received: from localhost (ben@localhost) by penelope.skunk.org (8.9.3/8.9.3) with ESMTP id NAA15578; Mon, 24 Jan 2000 13:17:25 -0500 (EST) Date: Mon, 24 Jan 2000 13:17:24 -0500 (EST) From: Ben Rosengart To: Brad Knowles Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Brad Knowles wrote: > And the only cost is the slight expansion of the amount of disk > space required to store the source code in /usr/src and the binaries > in /usr/bin [...] And the time and disk space required to make world. No thank you. Remember that the only win here is if bzip is used in an infrastructural capacity (e.g. for packages and other install stuff), and it has been pointed out that the savings on disk space are offset by the additional memory requirements. If it won't be used for infrastructure, then why can't it stay in ports? -- Ben Rosengart UNIX Systems Engineer, Skunk Group StarMedia Network, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 10:20:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7E92C14EBE for ; Mon, 24 Jan 2000 10:20:40 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA01853; Mon, 24 Jan 2000 11:20:37 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA04735; Mon, 24 Jan 2000 11:20:24 -0700 (MST) Message-Id: <200001241820.LAA04735@harmony.village.org> To: Brad Knowles Subject: Re: Please help spread the CVSup mirror load more evenly Cc: current@FreeBSD.ORG In-reply-to: Your message of "Mon, 24 Jan 2000 14:15:21 +0100." References: <20000121180914.C44132@dragon.nuxi.com> <20000121173923.A44132@dragon.nuxi.com> <200001220500.WAA17674@harmony.village.org> Date: Mon, 24 Jan 2000 11:20:24 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Brad Knowles writes: : Doesn't work. There might be a very low latency but : low-bandwidth connection between you and one of the servers, when you : (and everyone else) would be better off if you instead connected to a : server that shows slightly higher latency but has significantly more : bandwidth (or less packet loss, or a less loaded server on the other : end, etc...). Agreed. The making lots of connections was a bad idea. However, I've rarely seen low latency and low bandwidth go together. I've also problems connecting accross high loss links more often. Sure, it is a statistical argument. I still think that the n connections wouldn't be that expensive. The cost, iirc, of a connection that drops is very low. I can certainly see enough problems with it to encourage jdp to not implement it, despite being the person that proposed it... : IMO, there are just too many factors to be considered to apply : any one simplistic solution. You need more intelligence on both : ends.... Agreed. But in the abasense of intellegence at one end is causing problems at the other end. FWIW, I've found that *MUCH* better response times since I started using cvsup{6,7,8} on a regular basis than I was getting from cvsup{1,2,3}. I'm also seeing much faster response times from 6,7,8 than cvsup-master (yes, I know I'm not supposed to use that, but there are rare times I need to snag the latest change right away...). I've not tried cvsup 4,5 in a while, but did have trouble connecting to 5 while polishing my script. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 10:24:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from tardis.patho.gen.nz (tardis.patho.gen.nz [203.97.2.226]) by hub.freebsd.org (Postfix) with ESMTP id 0C7C214DBE; Mon, 24 Jan 2000 10:24:31 -0800 (PST) (envelope-from jabley@tardis.patho.gen.nz) Received: (from jabley@localhost) by tardis.patho.gen.nz (8.9.3/8.9.3) id HAA27428; Tue, 25 Jan 2000 07:23:28 +1300 (NZDT) Date: Tue, 25 Jan 2000 07:23:28 +1300 From: Joe Abley To: Brad Knowles Cc: "Rodney W. Grimes" , Amancio Hasty , obrien@FreeBSD.ORG, John Polstra , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly Message-ID: <20000125072325.B1319@patho.gen.nz> References: <200001220021.QAA22981@rah.star-gate.com> <200001220123.RAA59410@gndrsh.dnsmgr.net> <20000122233433.A2555@patho.gen.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from blk@skynet.be on Mon, Jan 24, 2000 at 02:17:54PM +0100 X-Files: the Truth is Out There Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 24, 2000 at 02:17:54PM +0100, Brad Knowles wrote: > At 11:34 PM +1300 2000/1/22, Joe Abley wrote: > > > This should give you a relative performance metric between the servers > > you measured, hopefully with local network performance variations > > cancelled out by the fact that all tests are run around the same time. > > This is a really cool idea! Are you going to be writing some > code to do this for us? ;-) Can do if people think it is worthwhile. Could be done quite easily in a wrapper to cvsup, I would thought. It _will_ need a static test set to be installed at each of the cvsup mirrors to be useful though. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 10:36:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2B50015036 for ; Mon, 24 Jan 2000 10:36:39 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA01905; Mon, 24 Jan 2000 11:36:36 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA04877; Mon, 24 Jan 2000 11:36:22 -0700 (MST) Message-Id: <200001241836.LAA04877@harmony.village.org> To: Nick Hibma Subject: Re: APM still ignoring DEVICE_SUSPEND errors Cc: FreeBSD CURRENT Mailing List In-reply-to: Your message of "Mon, 24 Jan 2000 13:30:54 GMT." References: Date: Mon, 24 Jan 2000 11:36:22 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Nick Hibma writes: : The following patch fixes two things: First, DEVICE_SUSPEND errors are : no longer ignored. Since we have defaults for methods we should no : longer ignore these errors. Also, DEVICE_RESUME wasn't done when the : apm_suspend_system event failed. I had similar patches that workede several months ago, but they have since been lost. : Second, in the ordering of DEVICE_* and apm_hook_* is not symmetric for : suspend and resume. The patch reverses the resume case as well to be : : apm_hook_resume(...) : DEVICE_RESUME(root) : : Send me some feedback on this. I've mailed the people mentioned in the : head of the file, but so far got no response. I would like to make sure : we get this right when USB devices are used. Some of them don't suspend : and the suspend should be refused in that case. Any reason to not shoot the apm_hook_{suspend,resume} in the head and just use newbus suspend/resume everywhere? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 10:37:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8079615298; Mon, 24 Jan 2000 10:37:17 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA19341; Mon, 24 Jan 2000 10:37:10 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA75584; Mon, 24 Jan 2000 10:37:10 -0800 (PST) (envelope-from obrien) Date: Mon, 24 Jan 2000 10:37:10 -0800 From: "David O'Brien" To: ports@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: 4.0-release (ports) schedule Message-ID: <20000124103710.B75151@dragon.nuxi.com> Reply-To: obrien@FreeBSD.org References: <200001241436.GAA23651@silvia.hip.berkeley.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001241436.GAA23651@silvia.hip.berkeley.edu>; from asami@FreeBSD.org on Mon, Jan 24, 2000 at 06:36:44AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 24, 2000 at 06:36:44AM -0800, Satoshi - Ports Wraith - Asami wrote: > There are over 200 broken ports. In particular, there are a few dozen > (78 at last count) broken by the gcc upgrade (those marked by "new These are due to bogus i386 ASM: cooledit-3.11.3.log ja-kon2-14dot-0.3.log ja-kon2-16dot-0.3.log ja-wine-99.01.31.log ko-han-1.0fb.log smlnj-110.9.1.log xkoules-1.4.log zh-big5con-0.92e.log There are instructions at http://gcc.gnu.org/cgi-bin/fom.cgi?file=23 and http://gcc.gnu.org/onlinedocs/gcc_4.html#SEC94 on how to fix these. I would be happy to look review fixes or consult the maintainers. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 10:39:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 36A5014F55; Mon, 24 Jan 2000 10:38:57 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA68737; Mon, 24 Jan 2000 10:38:22 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001241838.KAA68737@gndrsh.dnsmgr.net> Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <20000125072325.B1319@patho.gen.nz> from Joe Abley at "Jan 25, 2000 07:23:28 am" To: jabley@patho.gen.nz (Joe Abley) Date: Mon, 24 Jan 2000 10:38:22 -0800 (PST) Cc: blk@skynet.be (Brad Knowles), hasty@rah.star-gate.com (Amancio Hasty), obrien@FreeBSD.ORG, jdp@polstra.com (John Polstra), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Jan 24, 2000 at 02:17:54PM +0100, Brad Knowles wrote: > > At 11:34 PM +1300 2000/1/22, Joe Abley wrote: > > > > > This should give you a relative performance metric between the servers > > > you measured, hopefully with local network performance variations > > > cancelled out by the fact that all tests are run around the same time. > > > > This is a really cool idea! Are you going to be writing some > > code to do this for us? ;-) > > Can do if people think it is worthwhile. Could be done quite easily > in a wrapper to cvsup, I would thought. It _will_ need a static > test set to be installed at each of the cvsup mirrors to be useful > though. This does not need to really be a wrapper around cvs, folks should run a tool 1 time to pick the best guess as to what server they should be using, stick that value in thier cvsup file and be done with it. If jdp calls for a ``this server is being overloaded please move'' folks should rerun the selection tool and pick new servers. This latter event happens 2 or 3 times a year, it is a waste to run this every time you start up cvsup and can cause the grief if you change cvsup servers in <1 hour due to the update policy of the mirrors. This thread should die probably die... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 10:55:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 3908F14C4C for ; Mon, 24 Jan 2000 10:55:44 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id NAA78292; Mon, 24 Jan 2000 13:55:16 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Mon, 24 Jan 2000 13:55:16 -0500 (EST) From: Chuck Robey To: Warner Losh Cc: Brad Knowles , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <200001241820.LAA04735@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Warner Losh wrote: > Agreed. The making lots of connections was a bad idea. However, I've > rarely seen low latency and low bandwidth go together. I've also > problems connecting accross high loss links more often. Sure, it is a > statistical argument. > > I still think that the n connections wouldn't be that expensive. The > cost, iirc, of a connection that drops is very low. I can certainly > see enough problems with it to encourage jdp to not implement it, > despite being the person that proposed it... That's the precise reason I suggested a system that used no probing, had feedback, and forced shared load in spite of user misconfiguration. Got shouted down. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 11: 1:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 798BE14CD2 for ; Mon, 24 Jan 2000 11:01:35 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id OAA14380; Mon, 24 Jan 2000 14:01:12 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001241901.OAA14380@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <0001222017550K.00537@rbtBSD.intranet> Date: Mon, 24 Jan 2000 14:01:11 -0500 (EST) From: John Baldwin To: Rod Taylor Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi Cc: freebsd-current@FreeBSD.org, Alex Zepeda Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 23-Jan-00 Rod Taylor wrote: > On Sat, 22 Jan 2000, you wrote: >> On Sat, 22 Jan 2000, Rod Taylor wrote: >> >> > Personally, I'd like to see less stuff in the system source for >> > smaller installs and lower compile time leaving it up to me to >> > customize the individual stuff thats installed. Unless bzip is used >> > by > 99.9% of the FreeBSD installs, I'm willing to let it >> > 'auto-install itself'. >> >> What if we began to use bzip2 instead of gzip for things like man pages, >> or releases, etc? >> >> I think gzip is somewhat like compress, in that it might never go away >> completely, but it's generally been superceded by (IMO) bzip2. > > Agreed, then it'd be useful. I also noticed a message Jordan sent through the > list oneday mentioning the possible use of Bzip2 for a new package structure. > I do believe that the system should have bzip in it, but because it's being > used by freebsd internals itself, not because a person may use it at one point. > Make gzip the port in 5.0, and bzip the root compressor... :) The new install system is probably going to use zip rather than bzip2. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 11: 3:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 68D0E15A82 for ; Mon, 24 Jan 2000 11:03:32 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA02015; Mon, 24 Jan 2000 12:03:24 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA05087; Mon, 24 Jan 2000 12:03:11 -0700 (MST) Message-Id: <200001241903.MAA05087@harmony.village.org> To: Chuck Robey Subject: Re: Please help spread the CVSup mirror load more evenly Cc: Brad Knowles , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 24 Jan 2000 13:55:16 EST." References: Date: Mon, 24 Jan 2000 12:03:11 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : That's the precise reason I suggested a system that used no probing, had : feedback, and forced shared load in spite of user misconfiguration. Got : shouted down. One reason I think that you've been shouted down (and me too, since I had similar ideas) is that people in the past have had problems with different cvsup servers being at different points in time and have been screwed to som eextent or another by this time skew. There is a large resistance to automatically switching cvsup servers. It is my perception that the cvsup servers are much better now than they were even 6 months ago (well, cvsup{1,2} do seem to be much more heavily used than 6,7,8). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 11:16:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id DCB20151E9 for ; Mon, 24 Jan 2000 11:16:38 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA02057; Mon, 24 Jan 2000 12:16:34 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA05164; Mon, 24 Jan 2000 12:16:20 -0700 (MST) Message-Id: <200001241916.MAA05164@harmony.village.org> To: Chuck Robey Subject: Re: Please help spread the CVSup mirror load more evenly Cc: Brad Knowles , current@FreeBSD.ORG In-reply-to: Your message of "Mon, 24 Jan 2000 14:06:00 EST." References: Date: Mon, 24 Jan 2000 12:16:20 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Chuck Robey writes: : Oh. If that's a problem, it would be a fatal problem (would be for me, : sometimes). It used to be a big problem. When cvsup was first getting mirrors, some seemed to update every 15 minutes, while others updated what seemed like every two days. A big part of the problem was contention at the main cvsup server. Since cvsup has gone to cvsup-master this problem has all but disappeared. The mirrors all have good connectivity and can get updates on a timely basis. In my limited testing recently, I've noticed no measurable time skew between the servers. My methodology wasn't the best in the world. It basically ran the following script a bunch of times: for i in 1 2 3 4 5 6 7 8; do cvsup -h cvsup$i.freebsd.org done and checked to see if files reverted between runs (and yes, I did have delete in the cvsup file). I the 10 or so times I ran it I got access failures for some hosts, but I never saw reversions. Another problem is that if you get partway through an update, the connetion drops and you reconnect to a different cvsup server at a different point in time. In the past reversions have happened. And fairly often when there was a big skew. People still remember that, so there is still resistance to it. Going back further to the sup days, swithcing sup servers was a huge deal. There you had all the attributes of the entire repo updated. Not fun, nor protocol friendly. For people updating 2x a day or less often, I doubt that switching between responding cvsup servers would cause great pain, or any effects at all. It is a hard problem to get right all the time.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 11:25: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id A1761157C3 for ; Mon, 24 Jan 2000 11:24:46 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id OAA90380; Mon, 24 Jan 2000 14:06:00 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Mon, 24 Jan 2000 14:06:00 -0500 (EST) From: Chuck Robey To: Warner Losh Cc: Brad Knowles , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <200001241903.MAA05087@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Warner Losh wrote: > In message Chuck Robey writes: > : That's the precise reason I suggested a system that used no probing, had > : feedback, and forced shared load in spite of user misconfiguration. Got > : shouted down. > > One reason I think that you've been shouted down (and me too, since I > had similar ideas) is that people in the past have had problems with > different cvsup servers being at different points in time and have > been screwed to som eextent or another by this time skew. Oh. If that's a problem, it would be a fatal problem (would be for me, sometimes). > > There is a large resistance to automatically switching cvsup servers. > > It is my perception that the cvsup servers are much better now than > they were even 6 months ago (well, cvsup{1,2} do seem to be much more > heavily used than 6,7,8). > > > Warner > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 11:28:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id A5373152BE for ; Mon, 24 Jan 2000 11:27:30 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id OAA90473; Mon, 24 Jan 2000 14:27:01 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Mon, 24 Jan 2000 14:27:01 -0500 (EST) From: Chuck Robey To: Warner Losh Cc: Brad Knowles , current@FreeBSD.ORG Subject: Re: Please help spread the CVSup mirror load more evenly In-Reply-To: <200001241916.MAA05164@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Warner Losh wrote: > In message Chuck Robey writes: > : Oh. If that's a problem, it would be a fatal problem (would be for me, > : sometimes). > > It used to be a big problem. When cvsup was first getting mirrors, > some seemed to update every 15 minutes, while others updated what > seemed like every two days. A big part of the problem was contention > at the main cvsup server. Since cvsup has gone to cvsup-master this > problem has all but disappeared. The mirrors all have good > connectivity and can get updates on a timely basis. [some deletions] > For people updating 2x a day or less often, I doubt that switching > between responding cvsup servers would cause great pain, or any > effects at all. > > It is a hard problem to get right all the time.... Well, I really hate the idea of lots of network pinging, both because it's not reliable for network probing, not reliable for machine load probing, and causes more congestion, so I wanted a way to force loadsharing, one that allowed some feedback so that real backups could be adjusted to. OTOH, there's no way I will try to fight folks with elephantine memories. I even began looking at Modula-3, seeing if I could offer a diff set to jdp. You know what I realized, and (for some reason) no one in my memory has ever written: modula-3, in features, looks a lot like Java. It's not a stylistic descendant of C like Java is, but featurewise, it is. > > Warner > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 11:34:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 2A61D152A5; Mon, 24 Jan 2000 11:33:05 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id OAA08860; Mon, 24 Jan 2000 14:32:50 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <20000124095417.A75151@dragon.nuxi.com> References: <86ghar$13c3$1@atlantis.rz.tu-clausthal.de> <200001241116.MAA41036@dorifer.heim3.tu-clausthal.de> <20000124095417.A75151@dragon.nuxi.com> Date: Mon, 24 Jan 2000 14:33:21 -0500 To: obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: bzip2 in src tree Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:54 AM -0800 1/24/00, David O'Brien wrote: >On Mon, Jan 24, 2000 at 12:16:32PM +0100, Oliver Fromme wrote: > > > And just how do I increase the space on a CDROM??? > > > > Include another CD-ROM. > >You are missing the point. The installation CDROM only shows >you the packages on that CDROM, this gives newbies the impression >we don't have very many packages. Then we should fix that aspect of the distribution, because no matter how good this bzip2 compression is, you're still going to have a huge number of packages which will not fit on that first CD. The space gained by using bzip2 is nearly irrelevant compared to the space needed to have a "more impressive list" of packages on that first CD-ROM. You've been arguing this for quite a while, and there has been no groundswell of support for your position. Do you think "just one more" message on this topic is going to convince anyone? Could we just table this discussion for a few months, and see what everyone thinks about it then? No one has argued to ban usage of bzip2, they're just saying it does not need to be in the base system. I can not fathom why that bugs you so much. Given some more time and maybe a few more improvements, and bzip2 may find itself popular enough to justify it being in the base system. Until then, it seems to me that it works just fine as a port. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 11:41:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 0EC311520D; Mon, 24 Jan 2000 11:41:35 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id OAA08645; Mon, 24 Jan 2000 14:16:23 -0500 (EST) (envelope-from luoqi) Date: Mon, 24 Jan 2000 14:16:23 -0500 (EST) From: Luoqi Chen Message-Id: <200001241916.OAA08645@lor.watermarkgroup.com> To: FreeBSD-current@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG, kato@ganko.eps.nagoya-u.ac.jp Subject: Re: indirection in bus space Cc: FreeBSD98-hackers@jp.freebsd.org, nyan@jp.freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Do you have any comment anout the patch? If there isn't any big > problem, I hope to commit it to current. > > Thank you. > > > I wrote: > > Do you remember this topic? I have revised the indirection support > > patch. What I have changed are: > > - to make diff files more readable > > - introduce the bus_simple_create_bsh() that creates > > a bus_space_handle_tag from a base address. > > > We shouldn't need bus_simple_create_bsh(). All drivers ought to use rman_get_bushandle()/rman_get_bustag() to retrieve the bus handle and tag, and use them in bus_space_read/write calls to perform device io. Drivers that don't do that should be fixed. Why have two files bus_at386.h and bus_pc98.h? I386_BUS_PIO_IND should be able to live with I386_BUS_PIO and I386_BUS_MEMIO happily together. -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 11:49:19 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id DB54814D8F; Mon, 24 Jan 2000 11:49:17 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C97871CD69E; Mon, 24 Jan 2000 11:49:17 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 24 Jan 2000 11:49:17 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS In-Reply-To: <61098.948740631@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Jordan K. Hubbard wrote: > On the 29th of January, I'll be freezing the -current branch (well, > OK, the trunk). That means NO commits without my review first and I Hmm. What does this mean for the ATA driver? I know Soren has some more updates in the wings, and I'm grateful for his continued work, but the truth of the matter is that it has never worked properly for my system (therefore by extension, those of a lot of other people out there who have working systems at present but who aren't using -current), and 5 days isn't likely to fix everyone's problems. I think we should consider defaulting back to the wd drivers unless soren can work miracles in the meantime, rather than risking a large subset of the user base finding 4.0 doesn't work right on their machines :-( Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 11:54:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (pC19F5474.dip0.t-ipconnect.de [193.159.84.116]) by hub.freebsd.org (Postfix) with ESMTP id BA3A414D8F; Mon, 24 Jan 2000 11:54:27 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 19818AB94; Mon, 24 Jan 2000 20:50:47 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id UAA25021; Mon, 24 Jan 2000 20:50:21 +0100 (CET) (envelope-from alex) Date: Mon, 24 Jan 2000 20:50:21 +0100 From: Alexander Langer To: "David O'Brien" Cc: ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0-release (ports) schedule Message-ID: <20000124205021.B24975@cichlids.cichlids.com> Mail-Followup-To: David O'Brien , ports@FreeBSD.ORG, current@FreeBSD.ORG References: <200001241436.GAA23651@silvia.hip.berkeley.edu> <20000124103710.B75151@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000124103710.B75151@dragon.nuxi.com>; from obrien@FreeBSD.ORG on Mon, Jan 24, 2000 at 10:37:10AM -0800 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake David O'Brien (obrien@FreeBSD.ORG): > I would be happy to look review fixes or consult the maintainers. Hello David, compiler-maintainer ;-) I noticed that many ports are broken because the compiler handles ANSI-C++ violations too strict. That means, if you do, as an example: const fubar = 10; the build _FAILS_. Other compilers implicy type "int" here, that's why many ports are broken for -current only. Just FYI, maybe you can do something against this strict handling. Or not, I don't know. Somehow, it's very good that the compiler does this... Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 12: 1:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 049CD15278; Mon, 24 Jan 2000 12:01:19 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA19742; Mon, 24 Jan 2000 12:01:18 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA75877; Mon, 24 Jan 2000 12:01:17 -0800 (PST) (envelope-from obrien) Date: Mon, 24 Jan 2000 12:01:17 -0800 From: "David O'Brien" To: ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0-release (ports) schedule Message-ID: <20000124120117.N81215@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001241436.GAA23651@silvia.hip.berkeley.edu> <20000124103710.B75151@dragon.nuxi.com> <20000124205021.B24975@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000124205021.B24975@cichlids.cichlids.com>; from alex@big.endian.de on Mon, Jan 24, 2000 at 08:50:21PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 24, 2000 at 08:50:21PM +0100, Alexander Langer wrote: > I noticed that many ports are broken because the compiler handles > ANSI-C++ violations too strict. Not too strict -- to the ratified ISO-C++ specification. > Just FYI, maybe you can do something against this strict handling. Nope. Those programs that aren't buildable aren't C++. I will not break the C++ compiler to support them. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 12:24:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 3B1761529B for ; Mon, 24 Jan 2000 12:24:54 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id VAA25318; Mon, 24 Jan 2000 21:24:43 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001241820.LAA04735@harmony.village.org> References: <20000121180914.C44132@dragon.nuxi.com> <20000121173923.A44132@dragon.nuxi.com> <200001220500.WAA17674@harmony.village.org> <200001241820.LAA04735@harmony.village.org> Date: Mon, 24 Jan 2000 19:49:50 +0100 To: Warner Losh From: Brad Knowles Subject: Re: Please help spread the CVSup mirror load more evenly Cc: current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:20 AM -0700 2000/1/24, Warner Losh wrote: > Agreed. The making lots of connections was a bad idea. However, I've > rarely seen low latency and low bandwidth go together. I have. Until recently, we had only a 512KB line between our operations facilities here in Brussels and the AMS-IX in Amsterdam. This is why our Network Manager didn't want me to add any news peerings across that link -- even just a GB/day could be a very significant load on that small of a connection. And I've seen some of our customers operating rather popular sites behind ISDN lines. If you tried a high-bandwidth cvsup on a system like that, the copper might melt! ;-) > Agreed. But in the abasense of intellegence at one end is causing > problems at the other end. Understood. That's why I suggest a more general solution needs more intelligence on both ends -- not a whole lot on the client side, just enough to have a useful dialog with a server regarding bandwidth, latency, network drops, etc... between the client and the server, the server utilization, the servers knowledge of other servers that exist and serve that information (and the latest information it might have as to their utilization), and the ability to be able to follow the references that are supplied. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 12:39:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from umd5.umd.edu (umd5.umd.edu [128.8.10.5]) by hub.freebsd.org (Postfix) with ESMTP id 3BFC9159F7 for ; Mon, 24 Jan 2000 12:38:57 -0800 (PST) (envelope-from howardjp@wam.umd.edu) Received: from morse.umd.edu (morse.umd.edu [128.8.10.185]) by umd5.umd.edu (8.9.1/8.9.1) with ESMTP id PAA18735; Mon, 24 Jan 2000 15:38:48 -0500 (EST) Received: from localhost (howardjp@localhost) by morse.umd.edu (8.9.1/8.9.1) with SMTP id PAA16040; Mon, 24 Jan 2000 15:38:48 -0500 (EST) X-Authentication-Warning: morse.umd.edu: howardjp owned process doing -bs Date: Mon, 24 Jan 2000 15:38:48 -0500 (EST) From: James Howard X-Sender: howardjp@morse.umd.edu To: Brad Knowles Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Brad Knowles wrote: > Can't we do both? Use gzip on the install floppy, but include > bzip2 in /usr/src, and make sure that all the various programs that > deal with tarballs and gzip'ed tarballs can also deal with bzip2 > tarballs (including in the ports system)? > > I mean, if it's in /usr/src, and we have both gzip & bzip2 > installed on the system, it's up to the user to choose which they > prefer and use most of the time, right? The obvious solution (and arguably, the Right Thing) is to merge the functionality into one utility. This makes everyone happy and is less painful than explicitily including both. And if one were anti-GPL, they'd start with the bzip2 sources and modify them to call zlib so that gzip can be kicked out but it's entire funcionality replaced with a more freely licensed utility. :) Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 12:54:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id ECC231599B; Mon, 24 Jan 2000 12:54:28 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id VAA07780; Mon, 24 Jan 2000 21:53:16 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001241901.OAA14380@server.baldwin.cx> References: <200001241901.OAA14380@server.baldwin.cx> Date: Mon, 24 Jan 2000 21:42:45 +0100 To: John Baldwin , Rod Taylor From: Brad Knowles Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi Cc: freebsd-current@FreeBSD.ORG, Alex Zepeda Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:01 PM -0500 2000/1/24, John Baldwin wrote: > The new install system is probably going to use zip rather than bzip2. I'm curious as to how a choice like this gets made. Could you elaborate? -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 12:54:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 4496914C22 for ; Mon, 24 Jan 2000 12:54:26 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id VAA07764; Mon, 24 Jan 2000 21:53:14 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Mon, 24 Jan 2000 21:40:48 +0100 To: Ben Rosengart From: Brad Knowles Subject: Re: bzip2 in src tree Cc: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:17 PM -0500 2000/1/24, Ben Rosengart wrote: > And the time and disk space required to make world. No thank you. What is the time & disk space requirements without bzip2? I recall multiple hours to do this, and hundreds of MB, but then maybe I'm mis-remembering things. What does bzip2 add to this mix? Doing `cd /usr/ports/archivers/bzip2; /usr/bin/time -alp make` results in the following: >> real 18.35 >> user 5.49 >> sys 8.24 Hmm. Under eighteen seconds to get the port, check the signature, untar it, apply any necessary patches, and build it. Not bad! Certainly not something I'd write home complaining about. >> 2376 maximum resident set size >> 318 average shared memory size >> 280 average unshared data size >> 130 average unshared stack size >> 73059 page reclaims >> 77 page faults >> 0 swaps >> 112 block input operations >> 200 block output operations >> 0 messages sent >> 0 messages received >> 0 signals received >> 3618 voluntary context switches >> 7822 involuntary context switches This on a rather busy Freenix Top 100 news peering server (running 3.2-RELEASE, so it's probably not as fast as it could be, especially with the VM changes in -CURRENT). Granted, it is a dual PIII@450 w/ 1MB L2 cache per processor and 1GB RAM, but that doesn't mean that this machine isn't pretty heavily loaded. What is the percentage of additional time and disk space required? I calculate that the additional disk space required is right around 2MB in /usr/ports/archivers/bzip2. This doesn't seem to be a whole lot to me. > Remember that the only win here is if bzip is used in an infrastructural > capacity (e.g. for packages and other install stuff), and it has been > pointed out that the savings on disk space are offset by the additional > memory requirements. If it won't be used for infrastructure, then why > can't it stay in ports? Actually, I think it would be useful in an infrastructural capacity. In particular, I believe that it would be worthwhile to compress the tarballs used for ports and packages with bzip2, or at least make that an option so that the CD-ROMs we produce can have more ports and packages on that first CD (which appears to be the only thing some morons look at). -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 12:56:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5208815C1E for ; Mon, 24 Jan 2000 12:56:12 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA11739 for current@freebsd.org; Mon, 24 Jan 2000 21:56:09 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001242056.VAA11739@freebsd.dk> Subject: HEADSUP!! burncd users.. To: current@freebsd.org Date: Mon, 24 Jan 2000 21:56:09 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The management of next_writeable has been move from the kernel to userspace. This means that the burncd command must be in sync with the kernel. So make world is your friend. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 12:56:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 48AC215C37 for ; Mon, 24 Jan 2000 12:56:18 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id VAA11739 for current@freebsd.org; Mon, 24 Jan 2000 21:56:09 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001242056.VAA11739@freebsd.dk> Subject: HEADSUP!! burncd users.. To: current@freebsd.org Date: Mon, 24 Jan 2000 21:56:09 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The management of next_writeable has been move from the kernel to userspace. This means that the burncd command must be in sync with the kernel. So make world is your friend. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 13: 0: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 818FF15A2C for ; Mon, 24 Jan 2000 12:59:33 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA02872; Mon, 24 Jan 2000 13:07:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001242107.NAA02872@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brad Knowles Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi In-reply-to: Your message of "Mon, 24 Jan 2000 21:42:45 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 24 Jan 2000 13:07:35 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 2:01 PM -0500 2000/1/24, John Baldwin wrote: > > > The new install system is probably going to use zip rather than bzip2. > > I'm curious as to how a choice like this gets made. Could you elaborate? Zip was selected because it's one of the few compressed bundle formats that allows for random access within the bundle. All of the stream-compressed tape archive variants require you to start at the beginning of the stream and decompress all the way up to the file you want, which is highly undesirable in several of the cases that we care about. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 13: 2:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 74FB0157B3; Mon, 24 Jan 2000 13:02:21 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA12844; Mon, 24 Jan 2000 22:00:34 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001242100.WAA12844@freebsd.dk> Subject: Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS In-Reply-To: from Kris Kennaway at "Jan 24, 2000 11:49:17 am" To: kris@hub.freebsd.org (Kris Kennaway) Date: Mon, 24 Jan 2000 22:00:34 +0100 (CET) Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), current@FreeBSD.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kris Kennaway wrote: > On Mon, 24 Jan 2000, Jordan K. Hubbard wrote: > > > On the 29th of January, I'll be freezing the -current branch (well, > > OK, the trunk). That means NO commits without my review first and I > > Hmm. What does this mean for the ATA driver? I know Soren has some more > updates in the wings, and I'm grateful for his continued work, but the > truth of the matter is that it has never worked properly for my system > (therefore by extension, those of a lot of other people out there who have > working systems at present but who aren't using -current), and 5 days > isn't likely to fix everyone's problems. Huh, you have only told me about the missing CDROM (should be fixed with the commit I just did), what else seems to be a problem ?? > I think we should consider defaulting back to the wd drivers unless soren > can work miracles in the meantime, rather than risking a large subset of > the user base finding 4.0 doesn't work right on their machines :-( I do miracles on a daily basis :), but for the pricetag on the work for FreeBSD, well, cant wonders do ?? -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 13: 7:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from ucsu.Colorado.EDU (ucsu.Colorado.EDU [128.138.129.83]) by hub.freebsd.org (Postfix) with ESMTP id 696C515272 for ; Mon, 24 Jan 2000 13:07:42 -0800 (PST) (envelope-from vinson@ucsu.Colorado.EDU) Received: from localhost (vinson@localhost) by ucsu.Colorado.EDU (8.9.3/8.9.3/ITS-5.0/standard) with SMTP id OAA06167 for ; Mon, 24 Jan 2000 14:07:32 -0700 (MST) Date: Mon, 24 Jan 2000 14:07:32 -0700 (MST) From: VINSON WAYNE HOWARD To: freebsd-current@freebsd.org Subject: 3com 574-tx PCMCIA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not to disrupt the facinating discussion about bzip2, but, 1. I've had some people tell me that support for the 3com 574-tx PCMCIA card was definitly in -current, and other people who weren't so sure. Is it, and if so, under what driver? 2. If it's included, is that driver in the GENERIC kernel? 3. Any sucess stories about using a 574 to do a ftp install? 4. If it's not included, what hardware would be recomended to get 10/100 e-net using PCMCIA under freebsd w/o PAO? With PAO? I'm just curious because this will affect my hardware purchasing, and whether or not I can adopt freebsd to replace my Linux boxes. Thanks in advance! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 13:19:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id C4E36152D5 for ; Mon, 24 Jan 2000 13:19:14 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id QAA30711; Mon, 24 Jan 2000 16:16:08 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001242116.QAA30711@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 24 Jan 2000 16:16:08 -0500 (EST) From: John Baldwin To: Brad Knowles Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi Cc: Alex Zepeda , freebsd-current@FreeBSD.org, Rod Taylor Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24-Jan-00 Brad Knowles wrote: > At 2:01 PM -0500 2000/1/24, John Baldwin wrote: > >> The new install system is probably going to use zip rather than bzip2. > > I'm curious as to how a choice like this gets made. Could you > elaborate? I did not make the choice personally, I believe that was done by Jordan. If I remember correctly, the primary reason is that an archive format that easily and efficiently allows for a subset of the files contained within to be extracted. [bg]zip'd tarballs require you to uncompress and extract the entire tarball and then throw away the data you don't use. Since zip integrates the compression and archiving in one file format, you can look in the zip header, find the file you want, and then extract and uncompress just its data. This functionality is key in the design of the new packaging system as packages will be responsible for extracting themselves in the new system. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 13:33:45 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id C70B7152BA; Mon, 24 Jan 2000 13:33:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id B81931CD417; Mon, 24 Jan 2000 13:33:43 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 24 Jan 2000 13:33:43 -0800 (PST) From: Kris Kennaway To: Soren Schmidt Cc: "Jordan K. Hubbard" , current@FreeBSD.org Subject: Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS In-Reply-To: <200001242100.WAA12844@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Soren Schmidt wrote: > Huh, you have only told me about the missing CDROM (should be fixed > with the commit I just did), what else seems to be a problem ?? My WDC drive falling back to PIO mode..see the dmesg in the previous message. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 13:41:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6FFD014F55 for ; Mon, 24 Jan 2000 13:41:48 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA02763; Mon, 24 Jan 2000 14:36:55 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA06512; Mon, 24 Jan 2000 14:36:42 -0700 (MST) Message-Id: <200001242136.OAA06512@harmony.village.org> To: VINSON WAYNE HOWARD Subject: Re: 3com 574-tx PCMCIA Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 24 Jan 2000 14:07:32 MST." References: Date: Mon, 24 Jan 2000 14:36:42 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message VINSON WAYNE HOWARD writes: : 1. I've had some people tell me that support for the 3com 574-tx PCMCIA : card was definitly in -current, and other people who weren't so sure. Is : it, and if so, under what driver? The ep driver claims to support this card. the pccard.conf.sample file also claims to support this card. Matt Dodd claims to have fixed support for this card. However, I'm currently working with someone who is having problems. : 2. If it's included, is that driver in the GENERIC kernel? yes. : 3. Any sucess stories about using a 574 to do a ftp install? No. Actually, if you are in Boulder Colorado, then I can make the extra special offer of personally helping you get this working and committing any changes needed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 14: 4:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by hub.freebsd.org (Postfix) with ESMTP id E25BC14E8C for ; Mon, 24 Jan 2000 14:04:10 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.4]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOV004U50RE6W@mta4.snfc21.pbi.net> for freebsd-current@FreeBSD.ORG; Mon, 24 Jan 2000 13:52:39 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 142FA918C9; Mon, 24 Jan 2000 13:52:26 -0800 (PST) Date: Mon, 24 Jan 2000 13:52:25 -0800 (PST) From: Alex Zepeda Subject: Re: bzip2 in src tree In-reply-to: To: Ben Rosengart Cc: Brad Knowles , freebsd-current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Ben Rosengart wrote: > And the time and disk space required to make world. No thank you. > Remember that the only win here is if bzip is used in an infrastructural > capacity (e.g. for packages and other install stuff), and it has been > pointed out that the savings on disk space are offset by the additional > memory requirements. If it won't be used for infrastructure, then why > can't it stay in ports? Again, lemmie get on my soap box, and ask have you looked at the man page, and compared the memory required when using -s to the memory required by gzip? - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 14: 8:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 13719152DD for ; Mon, 24 Jan 2000 14:08:44 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115204>; Tue, 25 Jan 2000 09:03:50 +1100 Content-return: prohibited From: Peter Jeremy Subject: Possible CTM problem To: current@FreeBSD.org Message-Id: <00Jan25.090350est.115204@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii Date: Tue, 25 Jan 2000 09:03:49 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looking at my CTM logs, I seem to be missing some pieces in the last 3 cvs-cur postings (cvs-cur 6021, 6022, 6023). I get two pieces simultaneously and then nothing until the next part. Is anyone else seeing this? Chuck isn't sure if it's anything he's done. Looking back, the `first two pieces simultaneously' seems to be the normal behaviour, but I'd expect to see the 3rd piece 30-60 minutes later, followed by successive parts every hour. The last delta with more than 3 parts was cvs-cur.5999 (arrived 18 Jan), so the problem (if there is one) has occurred since then. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 14:51:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 7648E152AD for ; Mon, 24 Jan 2000 14:51:42 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id RAA91349; Mon, 24 Jan 2000 17:47:11 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Mon, 24 Jan 2000 17:47:11 -0500 (EST) From: Chuck Robey To: Peter Jeremy Cc: current@FreeBSD.ORG Subject: Re: Possible CTM problem In-Reply-To: <00Jan25.090350est.115204@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jan 2000, Peter Jeremy wrote: > Looking at my CTM logs, I seem to be missing some pieces in the last 3 > cvs-cur postings (cvs-cur 6021, 6022, 6023). I get two pieces > simultaneously and then nothing until the next part. Is anyone else > seeing this? Chuck isn't sure if it's anything he's done. > > Looking back, the `first two pieces simultaneously' seems to be the > normal behaviour, but I'd expect to see the 3rd piece 30-60 minutes > later, followed by successive parts every hour. The last delta > with more than 3 parts was cvs-cur.5999 (arrived 18 Jan), so the > problem (if there is one) has occurred since then. If you need to, you can fetch them via ftp. Like I said, I was generating a large amount of extra (very small) deltas while I was testing the upgrade to allow PGP signing, I didn't think I'd caused any lossage, but it's *possible*. I announced on the ctm-announce list that I would be generating those extra deltas. Anyhow, all the testing is over, I'm just waiting on some admin stuff before I start sending the CTM pieces (of deltas, the pieces are the mailed version of the binary gzipped deltas) out. Probably be tomorrow or the next day. > > Peter > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 14:57: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id 97C41153FE; Mon, 24 Jan 2000 14:57:07 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 89CBB125BB; Mon, 24 Jan 2000 22:23:15 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <200001242116.QAA30711@server.baldwin.cx> References: <200001242116.QAA30711@server.baldwin.cx> Date: Mon, 24 Jan 2000 22:23:13 +0100 To: John Baldwin From: Brad Knowles Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi Cc: Alex Zepeda , freebsd-current@FreeBSD.ORG, Rod Taylor Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 4:16 PM -0500 2000/1/24, John Baldwin wrote: > Since zip integrates the > compression and archiving in one file format, you can look in the zip header, > find the file you want, and then extract and uncompress just its data. This > functionality is key in the design of the new packaging system as packages > will be responsible for extracting themselves in the new system. Hmm. Okay, that's an argument I can buy -- I may not like the resulting choice (for personal reasons, if nothing else), but I can buy the argument. Thanks! -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 15: 1:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 961D515A35; Mon, 24 Jan 2000 15:01:06 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id RAA44578; Mon, 24 Jan 2000 17:08:25 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Mon, 24 Jan 2000 17:08:56 -0500 To: "Jordan K. Hubbard" From: Garance A Drosihn Subject: Re: 4.0 CODE FREEZE vs patches to lpr/lpc Cc: current@FreeBSD.ORG, committers@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Mon, 24 Jan 2000, Jordan K. Hubbard wrote: > > > On the 29th of January, I'll be freezing the -current branch (well, > > OK, the trunk). That means NO commits without my review first ... Could someone commit the 2-line bug fix in bin/15728 before yet another system release goes out the door? Jan 7th, 1999: problem first reported in bin/9362 Sep 9th, 1999: fix first described (with patch) in bin/13549 Nov 18th, 1999: fix acknowledged by another person in bin/14975, although the update there is "backwards" (it would turn a FIXED source code to become the UNFIXED one, because it's a 'diff cmds cmds.orig'). Dec 27th, 1999: slightly prettier version of the Sept 9th patch is sent in and becomes bin/15728. There some other lpr/lpd PR's which look like they should go in, and I have more lpr/lpd patches to write up sometime, but I figure if I can't get this damn 2-line fix committed then there isn't much point pursuing any other printing improvements. It's a trivial fix to an obvious and 100% reproducible bug, and yet it just sits there. Note this is not the somewhat more controversial change (to 'lpr -r') that I was pursuing earlier this month, as it might be a bit too close to the code freeze to put that one in. Given that lpr/lpd seems to be very low priority in most committers queues, is there any way to expedite changes like these? I'm trying avoid any ranting or raving, but this has been pretty exasperating. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 15:12:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 7331714F10; Mon, 24 Jan 2000 15:12:43 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA00485; Mon, 24 Jan 2000 17:32:02 -0500 (EST) (envelope-from wollman) Date: Mon, 24 Jan 2000 17:32:02 -0500 (EST) From: Garrett Wollman Message-Id: <200001242232.RAA00485@khavrinen.lcs.mit.edu> To: obrien@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzip2 support for distribution patches) In-Reply-To: <20000123194647.A5472@hub.freebsd.org> References: <86duop$2n8d$1@atlantis.rz.tu-clausthal.de> <200001230926.KAA81850@dorifer.heim3.tu-clausthal.de> <20000123194647.A5472@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Am I the only one that uses UNIX as a multitasking OS? > nice the bzip2 process by 20 and background it. Geez. Perhaps you're the only one who compresses files just for the hell of it. Most people normally compress files to meet an immediate need, and actually care how long it takes since whatever they're doing is blocked until the compression completes. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 15:12:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id ECF81152BA for ; Mon, 24 Jan 2000 15:12:47 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id RAA00429; Mon, 24 Jan 2000 17:25:30 -0500 (EST) (envelope-from wollman) Date: Mon, 24 Jan 2000 17:25:30 -0500 (EST) From: Garrett Wollman Message-Id: <200001242225.RAA00429@khavrinen.lcs.mit.edu> To: Brad Knowles Cc: freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree (Was Re: ports/16252: bsd.port.mk: Add bzi In-Reply-To: References: <200001241901.OAA14380@server.baldwin.cx> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >I'm curious as to how a choice like this gets made. Could you elaborate? Other people have answered with the why but not the how. Choices (like this one about archive formats) get made when people sit down and actually do the work to improve FreeBSD. People with commit bits are generally (but not completely) trusted to have an understanding of software-system aesthetics and of the sorts of choices developers might reasonably make on their own. The more effort one is personally willing to put into the project, the greater latitute one has in design. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 15:37:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 532AF14E34; Mon, 24 Jan 2000 15:37:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA93308; Mon, 24 Jan 2000 15:33:06 -0800 (PST) (envelope-from dillon) Date: Mon, 24 Jan 2000 15:33:06 -0800 (PST) From: Matthew Dillon Message-Id: <200001242333.PAA93308@apollo.backplane.com> To: Garance A Drosihn Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: 4.0 CODE FREEZE vs patches to lpr/lpc References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Could someone commit the 2-line bug fix in bin/15728 before yet :another system release goes out the door? Done! :Given that lpr/lpd seems to be very low priority in most committers :queues, is there any way to expedite changes like these? I'm :trying avoid any ranting or raving, but this has been pretty :exasperating. :--- :Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu :Senior Systems Programmer or drosih@rpi.edu If it is a very simple and obvious change you can typically email one of the committers specifically and he will do it. E.G. you could just email me and I'd do it. If it's more complex then the best way to go is to get the PR assigned to a committer somehow (the 'Assigned' field). This is one of the main deficiencies of the PR system --- PR's are not automatically assigned to committers based on criterea (such as the module or subsystem). -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 15:51:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.netbenefit.co.uk (mailhost.netbenefit.co.uk [212.53.64.39]) by hub.freebsd.org (Postfix) with ESMTP id 445A914BEE for ; Mon, 24 Jan 2000 15:51:37 -0800 (PST) (envelope-from pierre.dampure@k2c.co.uk) Received: from [193.149.78.89] (helo=bladerunner.k2c.co.uk) by mailhost.netbenefit.co.uk with esmtp (NetBenefit 1.4) id 12Csmz-0007ad-00 for current@FreeBSD.ORG; Mon, 24 Jan 2000 23:20:53 +0000 Received: from k2c.co.uk (localhost [127.0.0.1]) by bladerunner.k2c.co.uk (8.9.3/8.9.3) with ESMTP id XAA05867 for ; Mon, 24 Jan 2000 23:20:58 GMT (envelope-from pierre.dampure@k2c.co.uk) Message-ID: <388CDE59.99A363DE@k2c.co.uk> Date: Mon, 24 Jan 2000 23:20:57 +0000 From: "Pierre Y. Dampure" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: VESA_800x600 mode -> kernel crash at boot time? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-RBL-Warning: See Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could someone with a recent (ie < 1 week) -CURRENT confirm whether they have problems booting their system when setting allscreens_flags to "VESA_800x600"? I have now verified the problem with two different systems -- Compaq Professional Workstation 5100 (UP, Matrox Millenium II) and Intel Providence PR440FX (SMP, Matrox G200) -- neither of which exhibited the problem previously. Cheers, -- PYD@Home To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 16: 2:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id F3A3614D62 for ; Mon, 24 Jan 2000 16:02:12 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:04S1Ku2Y2PSLRyJbh4HqPyeub59v6bvz@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id IAA20634; Tue, 25 Jan 2000 08:57:07 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA22173; Tue, 25 Jan 2000 09:02:43 +0900 (JST) Message-Id: <200001250002.JAA22173@zodiac.mech.utsunomiya-u.ac.jp> To: "Pierre Y. Dampure" Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VESA_800x600 mode -> kernel crash at boot time? In-reply-to: Your message of "Mon, 24 Jan 2000 23:20:57 GMT." <388CDE59.99A363DE@k2c.co.uk> References: <388CDE59.99A363DE@k2c.co.uk> Date: Tue, 25 Jan 2000 09:02:43 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Could someone with a recent (ie < 1 week) -CURRENT confirm whether they >have problems booting their system when setting allscreens_flags to >"VESA_800x600"? I have now verified the problem with two different >systems -- Compaq Professional Workstation 5100 (UP, Matrox Millenium >II) and Intel Providence PR440FX (SMP, Matrox G200) -- neither of which >exhibited the problem previously. This was just fixed in the following commit. Kazu ----------------------------------------------------------------- yokota 2000/01/24 05:44:39 PST Modified files: sys/dev/syscons scmouse.c Log: Fix a bug exposed by the previous commit. Do not use scp->font_size, if the screen is in a graphics mode Reported by: Maxim Sobolev Revision Changes Path 1.11 +6 -3 src/sys/dev/syscons/scmouse.c ----------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 16:18:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from tmtowtdi.perl.org (tmtowtdi.perl.org [209.85.3.25]) by hub.freebsd.org (Postfix) with SMTP id DD6AC14EBC for ; Mon, 24 Jan 2000 16:18:49 -0800 (PST) (envelope-from richard@tmtowtdi.perl.org) Received: (qmail 23328 invoked by uid 511); 25 Jan 2000 00:11:30 -0000 Subject: [ID 20000124.004] "perl in malloc(): warning: recursive call" on array write + signals To: perl5-porters@perl.org From: Lars Eggert Delivered-To: perlmail-perlbug@perl.org Cc: current@freebsd.org Date: Mon, 24 Jan 2000 16:06:09 -0800 (PST) Message-Id: <200001250006.QAA13204@sub.isi.edu> Received: (qmail 23320 invoked by uid 508); 25 Jan 2000 00:11:29 -0000 X-loop: perlbug@perl.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a bug report for perl from larse@ISI.EDU, generated with the help of perlbug 1.26 running under perl 5.00503. ----------------------------------------------------------------- [Please enter your report here] Running the following test script causes perl to crash. You may need to run the script several times before seeing the problem. (The script spawns a child process that does nothing but write to an array. The parent signals the child periodically.) #!/usr/local/bin/perl -w use strict; use constant CHUNK_SIZE => 128; use constant ARRAY_SIZE => 1_000_000; $| = 1; if(my $pid = fork) { # parent signals periodically while(1) { select undef, undef, undef, 0.1; kill(ALRM => $pid) == 1 or die "cannot signal: $!"; print "."; } } else { # is kid up? unless(defined $pid) { die "cannot fork: $!"; } # initialize array (by using last element) my @data; $data[ARRAY_SIZE] = 1; # state of the process (number of alarms received) my $state = 0; $SIG{ALRM} = sub { $state++ }; # run the test while(1) { # calculate new position for this iteration my $pos = int rand ARRAY_SIZE; # write a chunk to a random position @data[$pos..$pos+CHUNK_SIZE] = (1) x CHUNK_SIZE; } } Execution of this script results in the following output: [sub: ~/thesis/bin] short ......................perl in malloc(): warning: recursive call. Out of memory! ....perl in malloc(): warning: recursive call. Out of memory! perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl.perl in malloc(): warning: recursive call. Out of memory! perl in free(): warning: recursive call. cannot signal: No such process at short line 14. Exit 3 Please let me know if I can provide any other information to help track this bug down. [Please do not change anything below this line] ----------------------------------------------------------------- --- Site configuration information for perl 5.00503: Configured by markm at $Date: 1999/05/05 19:42:40 $. Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=freebsd, osvers=4.0-current, archname=i386-freebsd uname='freebsd freefall.freebsd.org 4.0-current freebsd 4.0-current #0: $Date: 1999/05/05 19:42:40 $' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='undef', gccversion=egcs-2.91.66 19990314 (egcs-1.1.2 release) cppflags='' ccflags ='' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags ='-Wl,-E' libpth=/usr/lib libs=-lm -lc -lcrypt libc=/usr/lib/libc.so, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-DPIC -fpic', lddlflags='-shared' Locally applied patches: --- @INC for perl 5.00503: /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . --- Environment for perl 5.00503: HOME=/nfs/ruby/larse LANG (unset) LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=.:/home/d7unsupp/FreeBSD.ELF/bin:/usr/local/v6/bin:/usr/local/v6/sbin:/usr/inet6/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/X11R6/bin:/usr/tmp/scotty/bin:/stand PERL_BADLANG (unset) SHELL=/bin/ntcsh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 16:34:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 6FE7B152BC; Mon, 24 Jan 2000 16:34:04 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id JAA72536; Tue, 25 Jan 2000 09:33:24 +0900 (JST) To: luoqi@watermarkgroup.com Cc: FreeBSD-current@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG, kato@ganko.eps.nagoya-u.ac.jp, FreeBSD98-hackers@jp.freebsd.org, nyan@jp.freebsd.org Subject: Re: indirection in bus space From: KATO Takenori In-Reply-To: Your message of "Mon, 24 Jan 2000 14:16:23 -0500 (EST)" <200001241916.OAA08645@lor.watermarkgroup.com> References: <200001241916.OAA08645@lor.watermarkgroup.com> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000125093254J.kato@gneiss.eps.nagoya-u.ac.jp> Date: Tue, 25 Jan 2000 09:32:54 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 42 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote: > We shouldn't need bus_simple_create_bsh(). All drivers ought to use > rman_get_bushandle()/rman_get_bustag() to retrieve the bus handle and tag, > and use them in bus_space_read/write calls to perform device io. Drivers > that don't do that should be fixed. Yes. I think it is correct way. It means porting isp, amd and adv drivers to newbus, but I'm not familiar with these drivers. So I added bus_simple_creat_bsh function to reduce modification. > Why have two files bus_at386.h and bus_pc98.h? I386_BUS_PIO_IND should be > able to live with I386_BUS_PIO and I386_BUS_MEMIO happily together. Because they are different in the type of bus_space_tag_t from each other. It is the u_long in PC/AT and the structure in PC-98. For example, bus_space_read_1()s of them are: PC/AT: bus_space_read_1(...) { ... return (inb(handle + offset)); ... } PC-98: bus_space_read_1(...) { ... return (inb(bsh.bsh_iat[offset])); ... } -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 16:38:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from sub.isi.edu (sub-e.isi.edu [128.9.160.215]) by hub.freebsd.org (Postfix) with ESMTP id 2D02E15274 for ; Mon, 24 Jan 2000 16:38:27 -0800 (PST) (envelope-from larse@ISI.EDU) Received: (from larse@localhost) by sub.isi.edu (8.9.3/8.8.8) id QAA13204; Mon, 24 Jan 2000 16:06:09 -0800 (PST) Date: Mon, 24 Jan 2000 16:06:09 -0800 (PST) From: Lars Eggert Message-Id: <200001250006.QAA13204@sub.isi.edu> To: perlbug@perl.com Subject: "perl in malloc(): warning: recursive call" on array write + signals Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a bug report for perl from larse@ISI.EDU, generated with the help of perlbug 1.26 running under perl 5.00503. ----------------------------------------------------------------- [Please enter your report here] Running the following test script causes perl to crash. You may need to run the script several times before seeing the problem. (The script spawns a child process that does nothing but write to an array. The parent signals the child periodically.) #!/usr/local/bin/perl -w use strict; use constant CHUNK_SIZE => 128; use constant ARRAY_SIZE => 1_000_000; $| = 1; if(my $pid = fork) { # parent signals periodically while(1) { select undef, undef, undef, 0.1; kill(ALRM => $pid) == 1 or die "cannot signal: $!"; print "."; } } else { # is kid up? unless(defined $pid) { die "cannot fork: $!"; } # initialize array (by using last element) my @data; $data[ARRAY_SIZE] = 1; # state of the process (number of alarms received) my $state = 0; $SIG{ALRM} = sub { $state++ }; # run the test while(1) { # calculate new position for this iteration my $pos = int rand ARRAY_SIZE; # write a chunk to a random position @data[$pos..$pos+CHUNK_SIZE] = (1) x CHUNK_SIZE; } } Execution of this script results in the following output: [sub: ~/thesis/bin] short ......................perl in malloc(): warning: recursive call. Out of memory! ....perl in malloc(): warning: recursive call. Out of memory! perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl in free(): warning: recursive call. perl.perl in malloc(): warning: recursive call. Out of memory! perl in free(): warning: recursive call. cannot signal: No such process at short line 14. Exit 3 Please let me know if I can provide any other information to help track this bug down. [Please do not change anything below this line] ----------------------------------------------------------------- --- Site configuration information for perl 5.00503: Configured by markm at $Date: 1999/05/05 19:42:40 $. Summary of my perl5 (5.0 patchlevel 5 subversion 3) configuration: Platform: osname=freebsd, osvers=4.0-current, archname=i386-freebsd uname='freebsd freefall.freebsd.org 4.0-current freebsd 4.0-current #0: $Date: 1999/05/05 19:42:40 $' hint=recommended, useposix=true, d_sigaction=define usethreads=undef useperlio=undef d_sfio=undef Compiler: cc='cc', optimize='undef', gccversion=egcs-2.91.66 19990314 (egcs-1.1.2 release) cppflags='' ccflags ='' stdchar='char', d_stdstdio=undef, usevfork=true intsize=4, longsize=4, ptrsize=4, doublesize=8 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 alignbytes=4, usemymalloc=n, prototype=define Linker and Libraries: ld='cc', ldflags ='-Wl,-E' libpth=/usr/lib libs=-lm -lc -lcrypt libc=/usr/lib/libc.so, so=so, useshrplib=true, libperl=libperl.so.3 Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags=' ' cccdlflags='-DPIC -fpic', lddlflags='-shared' Locally applied patches: --- @INC for perl 5.00503: /usr/libdata/perl/5.00503/mach /usr/libdata/perl/5.00503 /usr/local/lib/perl5/site_perl/5.005/i386-freebsd /usr/local/lib/perl5/site_perl/5.005 . --- Environment for perl 5.00503: HOME=/nfs/ruby/larse LANG (unset) LANGUAGE (unset) LD_LIBRARY_PATH (unset) LOGDIR (unset) PATH=.:/home/d7unsupp/FreeBSD.ELF/bin:/usr/local/v6/bin:/usr/local/v6/sbin:/usr/inet6/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/usr/X11R6/bin:/usr/tmp/scotty/bin:/stand PERL_BADLANG (unset) SHELL=/bin/ntcsh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 16:41:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from fLuFFy.iNt.tElE.dK (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (Postfix) with ESMTP id B6263152AE for ; Mon, 24 Jan 2000 16:41:47 -0800 (PST) (envelope-from kvindeservice@Fluffy.gets.an.analprobe.dk) Received: from localhost (kvindeservice@localhost) by fLuFFy.iNt.tElE.dK (8.9.3/8.9.3) with SMTP id BAA52676 for ; Tue, 25 Jan 2000 01:41:36 +0100 (CET) (envelope-from kvindeservice@Fluffy.gets.an.analprobe.dk) X-Authentication-Warning: fLuFFy.iNt.tElE.dK: kvindeservice owned process doing -bs Date: Tue, 25 Jan 2000 01:41:36 +0100 (CET) From: K0dewanker X-Sender: kvindeservice@fLuFFy.iNt.tElE.dK Reply-To: luser-boy@netscum.dk To: freebsd-current@freebsd.org Subject: big files, blocking in inode, kern.update, and so on... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, me again... I wrote to some freebsd list some months/years back asking about this, but now it's time to revisit things. We have an old t^Hrusty 2.2-RELENG box from '97 that's been running like a champ, kinda, after hacking around the problem. But it's time to retire that underpowered box that sees occasional mysterious kernel panics and move on to more reliable hardware. Our machine is running a very hacked version of INN 1.5.1 to which I've added the MD5 history routines, and remembering news articles for a full 14 days. This means that we see history file sizes on the order of -rw-rw-r-- 1 news news 1013138182 Jan 25 01:03 history -rw-rw-r-- 1 news news 120 Jan 25 01:03 history.dir -rw-rw-r-- 1 news news 167184942 Jan 25 00:32 history.hash -rw-rw-r-- 1 news news 111456628 Jan 25 00:31 history.index I've now taken this code and installed it on two machines, one a Solaris box, and the other a FreeBSD-STABLE machine from a couple weeks ago. First was the Slowaris box, it has its problems but still never becomes unresponsive for more than a second or so when giving a `ctlinnd' command. However, as I observed with -current many months ago, the FreeBSD box, every 30 seconds, will totally freeze up for the ctlinnd command for the duration of time that the history disk light is lit and innd is found in `inode' state, which can be 25 seconds, although has been only slighter better than that recently. The history text file is appended to, while the hash and index files are essentially randomly updated at a rate of 10+ articles per second, so much of the entire file needs to be updated. Our 2.2 machine hacked around this problem with the non-solution of increasing the time between `sync's to an hour, so the machine becomes unresponsive for news once an hour for a minute or so, much better than a 50% duty cycle. Now, the `kern.update' sysctl parameter is long gone, and I don't see any suitable replacement to try and tweak this, with or without softupdates. (I'm not using them yet.) But my big question is, how does Solaris do it? to be able to update these large database files without causing innd to have to pause for a significant amount of time? And... Why can't FreeBSD match the performance of Solaris here? What can I do (besides submit patches, of course)? Where did kern.update disappear and is there any chance of a replacement? I have a couple more tricks up my sleeve, but I don't think they will help as much as we need, these drives aren't what you would call slow so a faster drive won't really improve things to the point where I'd be satisfied. thanks for any responses... barry bouwsma, tele danmark internet replies should be directed to the reply-to header address To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 16:53:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 927B414F6E for ; Mon, 24 Jan 2000 16:53:32 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id TAA63817; Mon, 24 Jan 2000 19:53:27 -0500 (EST) Date: Mon, 24 Jan 2000 19:53:27 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: 3com 574-tx PCMCIA In-Reply-To: <200001242136.OAA06512@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Warner Losh wrote: > The ep driver claims to support this card. the pccard.conf.sample > file also claims to support this card. Matt Dodd claims to have fixed > support for this card. Claim nothing. It works for me and a number of other people who have tested it for me. > However, I'm currently working with someone who is having problems. I'll avoid getting Bill-like here and just ask why I haven't heard of this. > Actually, if you are in Boulder Colorado, then I can make the extra > special offer of personally helping you get this working and > committing any changes needed. I'd love it if you ran them by me first though. Thanks. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 16:55:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 1E46B1526D for ; Mon, 24 Jan 2000 16:55:29 -0800 (PST) (envelope-from kbyanc@kronos.alcnet.com) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from gateway.posi.net (alc-144.alcnet.com [63.69.28.144]) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id TAA67930 for ; Mon, 24 Jan 2000 19:55:27 -0500 (EST) Received: from localhost (kbyanc@localhost) by gateway.posi.net (8.9.3/8.9.3) with ESMTP id UAA01498 for ; Mon, 24 Jan 2000 20:04:50 -0500 (EST) (envelope-from kbyanc@gateway.posi.net) Date: Mon, 24 Jan 2000 19:30:15 -0500 (EST) From: Kelly Yancey To: freebsd-current@freebsd.org Subject: pending patch to fix lack of signed sysctl values Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since the countdown is on to a new release, I'de like to take a second and nag some committers to take a look at PR kern/15251. Greg was going to take care of it for me before he got called away on business. In any event, it would good to get into 4.0 release if for no other reason than to prevent sysctl(1) from reporting ludicrious values for some system stats on long-running systems. The patches in kern/15251 add an unsigned flag to sysctl vars and updates sysctl(1) to honor that flag. This eliminates the reporting of negative stat counts when an unsigned integer was being displayed as a signed value. In the long term, there will probably be a need to make some of these stat counts larger integers (at least on i386 where longs are 32 bits and are easily overflown on long-running systems), but for now, these patches are a step in the right direction. Thanks, Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 16:57:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 82ECB14F6E for ; Mon, 24 Jan 2000 16:57:41 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA03600; Mon, 24 Jan 2000 17:57:36 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA08486; Mon, 24 Jan 2000 17:57:26 -0700 (MST) Message-Id: <200001250057.RAA08486@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: 3com 574-tx PCMCIA Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 24 Jan 2000 19:53:27 EST." References: Date: Mon, 24 Jan 2000 17:57:26 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : On Mon, 24 Jan 2000, Warner Losh wrote: : > The ep driver claims to support this card. the pccard.conf.sample : > file also claims to support this card. Matt Dodd claims to have fixed : > support for this card. : : Claim nothing. It works for me and a number of other people who have : tested it for me. OK. : > However, I'm currently working with someone who is having problems. : : I'll avoid getting Bill-like here and just ask why I haven't heard of : this. He sent me directly? As soon as I can get information out of him and I hit a wall, I'll let you know. So far it sounds like pilot error or a new rev of the card not in pccard.conf.sample. : > Actually, if you are in Boulder Colorado, then I can make the extra : > special offer of personally helping you get this working and : > committing any changes needed. : : I'd love it if you ran them by me first though. Sure thing. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 16:59:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id 1518F14C12 for ; Mon, 24 Jan 2000 16:59:18 -0800 (PST) (envelope-from mzaki@e-mail.ne.jp) Received: from work.mzaki.nom (54.pool5.tokyo.att.ne.jp [165.76.22.69]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id HAA04287; Tue, 25 Jan 2000 07:24:51 +0900 (JST) Received: from work.mzaki.nom (mzaki@localhost [127.0.0.1]) by work.mzaki.nom (8.9.3/8.9.3) with ESMTP id HAA00323; Tue, 25 Jan 2000 07:24:48 +0900 (JST) (envelope-from mzaki@e-mail.ne.jp) Date: Tue, 25 Jan 2000 07:24:47 +0900 Message-ID: <86vh4jaz0w.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: sos@freebsd.dk Cc: current@FreeBSD.ORG Subject: Re: My ATAPI CD not come ready In-Reply-To: In your message of "Sun, 23 Jan 2000 18:51:25 +0100 (CET)" <200001231751.SAA26843@freebsd.dk> References: <86d7qsomwr.wl@tkc.att.ne.jp> <200001231751.SAA26843@freebsd.dk> X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi At Sun, 23 Jan 2000 18:51:25 +0100 (CET), Soren Schmidt wrote: > > I updated to today's -current from -stable. > > My ATAPI CD-ROM drive doesn't probed, > > and is seemed to be halted. > > (The tray is locked, won't open, and the LED keeps being on.) > > This is fixed in the next update, due as soon as I get time.... Thank you for fixing, but still not probed. What can I do for your work? ---- # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 device ata1 at isa? port IO_WD2 irq 15 device ata device atadisk # ATA disk drives device atapicd # ATAPI CDROM drives #device atapifd # ATAPI floppy drives #device atapist # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices ---- : : ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=00 status1=00 ata0: devices = 0x4 ata0 at 0x01f0 irq 14 on ata-pci0 : ata-isa0: already registered as ata0 : ata0-master: ata_command: timeout waiting for intr ata0-master: identify failed : : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 17: 0:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.qx.net (darkstar.qx.net [208.235.88.101]) by hub.freebsd.org (Postfix) with ESMTP id DFAC814A06 for ; Mon, 24 Jan 2000 17:00:43 -0800 (PST) (envelope-from gchil0@pop.uky.edu) Received: from mail.qx.net (mail.qx.net [208.235.88.10]) by darkstar.qx.net (8.8.7/8.8.7) with ESMTP id TAA06359 for ; Mon, 24 Jan 2000 19:02:21 -0500 Received: from k7 ([208.200.111.238]) by mail.qx.net (Netscape Messaging Server 3.6) with ESMTP id AAA4F92; Mon, 24 Jan 2000 19:05:12 -0500 Message-Id: <4.2.0.58.20000124185659.0095acb0@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 24 Jan 2000 19:03:43 -0500 To: Soren Schmidt From: Greg Childers Subject: Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS Cc: current@freebsd.org In-Reply-To: <4.2.0.58.20000124170340.00952cb0@pop.uky.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Huh, you have only told me about the missing CDROM (should be fixed >with the commit I just did), what else seems to be a problem ?? On some older PCI systems, including my Pentium 66, the driver still detects irq 0 for ata-pci0. Hardwiring it to irq 14 in the source as suggested= recently is the temporary fix I'm using.=20 >I do miracles on a daily basis :), but for the pricetag on the work >for FreeBSD, well, cant wonders do ?? > >-S=F8ren :) Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 17:47: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id A783A14A04 for ; Mon, 24 Jan 2000 17:47:03 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id UAA64542 for ; Mon, 24 Jan 2000 20:47:02 -0500 (EST) Date: Mon, 24 Jan 2000 20:47:02 -0500 (EST) From: "Matthew N. Dodd" To: current@freebsd.org Subject: sys/net/bridge.c IPFIREWALL & DUMMYNET? WTF? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Any reason that the IPFIREWALL and DUMMYNET code is present in sys/net/bridge.c? It appears that it makes a number of bad assumptions and in general violates the semantics of 'bridging' vs. 'routing'. Should we even encourage people to use this functionality? Do we really want bridge.c to have its own private IP stack? Should this code be diked out before 4.0 so we don't expose the masses to it? -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 18: 4:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id 3BEF11566E; Mon, 24 Jan 2000 18:04:35 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id VAA14309; Mon, 24 Jan 2000 21:04:33 -0500 (EST) (envelope-from luoqi) Date: Mon, 24 Jan 2000 21:04:33 -0500 (EST) From: Luoqi Chen Message-Id: <200001250204.VAA14309@lor.watermarkgroup.com> To: kato@ganko.eps.nagoya-u.ac.jp Subject: Re: indirection in bus space Cc: FreeBSD-current@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG, FreeBSD98-hackers@jp.freebsd.org, nyan@jp.freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Why have two files bus_at386.h and bus_pc98.h? I386_BUS_PIO_IND should be > > able to live with I386_BUS_PIO and I386_BUS_MEMIO happily together. > > Because they are different in the type of bus_space_tag_t from each > other. It is the u_long in PC/AT and the structure in PC-98. For > example, bus_space_read_1()s of them are: > > PC/AT: > bus_space_read_1(...) > { > ... > return (inb(handle + offset)); > ... > } > > PC-98: > bus_space_read_1(...) > { > ... > return (inb(bsh.bsh_iat[offset])); > ... > } > You could set the handle to point to the structure instead: bus_space_read_1(...) { if (tag == I386_BUS_PIO) { return (inb(handle + offset)); } else if (tag == I386_BUS_PIO_IND) { struct bus_space_handle_pc98 *bsh = handle; return (inb(bsh->bsh_iat[offset])); } else if (tag == I386_BUS_MEMIO) { ... } } -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 18:18:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id C26371536B for ; Mon, 24 Jan 2000 18:18:41 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA94691; Mon, 24 Jan 2000 18:17:56 -0800 (PST) (envelope-from dillon) Date: Mon, 24 Jan 2000 18:17:56 -0800 (PST) From: Matthew Dillon Message-Id: <200001250217.SAA94691@apollo.backplane.com> To: K0dewanker Cc: freebsd-current@FreeBSD.ORG Subject: Re: big files, blocking in inode, kern.update, and so on... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm. It sounds like the system is doing a huge amount of seeking to flush the dirty buffers. Your history file may be badly fragmented on the disk. The first thing I would do is take the system down and copy the history file to reorder all of its block. i.e. 'cp fubar fubar.bak' then 'mv fubar.bak fubar'. Assuming you have the space. You may be able to force the system to write more smoothly by reducing the vfs.hidirtybuffers water mark. There are other possible solutions if you can track down the piece of code causing the most trouble. I believe that newer versions of INN use shared R+W mmap()'s which can cause fragmented dirty pages. The syncer will push these pages out every 30 seconds or so. If this is what is causing the problem you can solve it under -CURRENT by adding MAP_NOSYNC to the mmap() call in question (though I don't know which one it is, I haven't used INN recently). -Matt Matthew Dillon :Howdy, me again... : :I wrote to some freebsd list some months/years back asking about :this, but now it's time to revisit things. : :We have an old t^Hrusty 2.2-RELENG box from '97 that's been running :like a champ, kinda, after hacking around the problem. But it's :time to retire that underpowered box that sees occasional mysterious :kernel panics and move on to more reliable hardware. : :Our machine is running a very hacked version of INN 1.5.1 to which I've :added the MD5 history routines, and remembering news articles for a full :14 days. This means that we see history file sizes on the order of :-rw-rw-r-- 1 news news 1013138182 Jan 25 01:03 history :-rw-rw-r-- 1 news news 120 Jan 25 01:03 history.dir :-rw-rw-r-- 1 news news 167184942 Jan 25 00:32 history.hash :-rw-rw-r-- 1 news news 111456628 Jan 25 00:31 history.index : :I've now taken this code and installed it on two machines, one a :Solaris box, and the other a FreeBSD-STABLE machine from a couple :weeks ago. : :First was the Slowaris box, it has its problems but still never :becomes unresponsive for more than a second or so when giving a :`ctlinnd' command. : :However, as I observed with -current many months ago, the FreeBSD :box, every 30 seconds, will totally freeze up for the ctlinnd :command for the duration of time that the history disk light is :lit and innd is found in `inode' state, which can be 25 seconds, :although has been only slighter better than that recently. : :The history text file is appended to, while the hash and index :files are essentially randomly updated at a rate of 10+ articles :per second, so much of the entire file needs to be updated. : :Our 2.2 machine hacked around this problem with the non-solution :of increasing the time between `sync's to an hour, so the machine :becomes unresponsive for news once an hour for a minute or so, :much better than a 50% duty cycle. : :Now, the `kern.update' sysctl parameter is long gone, and I don't :see any suitable replacement to try and tweak this, with or without :softupdates. (I'm not using them yet.) : :But my big question is, how does Solaris do it? to be able to :update these large database files without causing innd to have to :pause for a significant amount of time? And... : :Why can't FreeBSD match the performance of Solaris here? What can :I do (besides submit patches, of course)? Where did kern.update :disappear and is there any chance of a replacement? : : :I have a couple more tricks up my sleeve, but I don't think they :will help as much as we need, these drives aren't what you would :call slow so a faster drive won't really improve things to the :point where I'd be satisfied. : : :thanks for any responses... :barry bouwsma, tele danmark internet :replies should be directed to the reply-to header address To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 18:42:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 00FB114D2B for ; Mon, 24 Jan 2000 18:42:36 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id TAA16882; Mon, 24 Jan 2000 19:06:41 -0800 (PST) Date: Mon, 24 Jan 2000 19:06:41 -0800 From: Alfred Perlstein To: "Matthew N. Dodd" Cc: current@FreeBSD.ORG Subject: Re: sys/net/bridge.c IPFIREWALL & DUMMYNET? WTF? Message-ID: <20000124190641.R26520@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from winter@jurai.net on Mon, Jan 24, 2000 at 08:47:02PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew N. Dodd [000124 18:11] wrote: > Any reason that the IPFIREWALL and DUMMYNET code is present in > sys/net/bridge.c? It appears that it makes a number of bad assumptions > and in general violates the semantics of 'bridging' vs. 'routing'. > > Should we even encourage people to use this functionality? Do we really > want bridge.c to have its own private IP stack? > > Should this code be diked out before 4.0 so we don't expose the masses to > it? I'm not sure what your proposing, if it's removing BRIDGE support from the kernel, I'd have to object. BRIDGE enables me to run a transparent firewall without worrying about routing issues, just drop a machine with BRIDGE and IPFIREWALL in between two points and everything is ok. However enable a DIVERT socket, and it all goes to hell last i checked. Anyhow, can you clarify? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 19:30:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from yana.lemis.com (yana.lemis.com [192.109.197.140]) by hub.freebsd.org (Postfix) with ESMTP id AF91114CF1; Mon, 24 Jan 2000 19:29:42 -0800 (PST) (envelope-from grog@mojave.worldwide.lemis.com) Received: from mojave.worldwide.lemis.com (j13.ktb6.jaring.my [161.142.234.27]) by yana.lemis.com (8.8.8/8.8.8) with ESMTP id NAA14028; Tue, 25 Jan 2000 13:59:29 +1030 (CST) (envelope-from grog@mojave.worldwide.lemis.com) Received: (from grog@localhost) by mojave.worldwide.lemis.com (8.9.3/8.9.3) id LAA04928; Tue, 25 Jan 2000 11:19:22 +0800 (MYT) (envelope-from grog) Date: Tue, 25 Jan 2000 11:19:22 +0800 From: Greg Lehey To: Kris Kennaway Cc: Soren Schmidt , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: at driver problems (was: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS) Message-ID: <20000125111922.F4775@mojave.worldwide.lemis.com> Reply-To: Greg Lehey References: <200001242100.WAA12844@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Mon, Jan 24, 2000 at 01:33:43PM -0800 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Monday, 24 January 2000 at 13:33:43 -0800, Kris Kennaway wrote: > On Mon, 24 Jan 2000, Soren Schmidt wrote: > >> Huh, you have only told me about the missing CDROM (should be fixed >> with the commit I just did), what else seems to be a problem ?? > > My WDC drive falling back to PIO mode..see the dmesg in the previous > message. I've seen this, too. I haven't reported it because I wasn't 100% sure that the wd driver wasn't lying, and I haven't had time to check it. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 19:38:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 0982E151EC; Mon, 24 Jan 2000 19:38:25 -0800 (PST) (envelope-from trouble@netquick.net) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=netquick.net) by bekool.com with esmtp (Exim 3.03 #1) id 12CxNE-000ODH-00; Mon, 24 Jan 2000 23:14:37 -0500 Message-ID: <388D1CE1.28C90567@netquick.net> Date: Mon, 24 Jan 2000 22:47:45 -0500 From: TrouBle Reply-To: trouble@netquick.net X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lehey Cc: Kris Kennaway , Soren Schmidt , "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: at driver problems (was: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS) References: <200001242100.WAA12844@freebsd.dk> <20000125111922.F4775@mojave.worldwide.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG does it look like this ??? ad0: ATA-5 disk at ata0 as master ad0: 9770MB (20010816 sectors), 19852 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata0 as slave acd0: read 6890KB/s (6890KB/s), 256KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/wd0s1a pid 231 (E-Cpu.epplet), uid 0: exited on signal 11 (core dumped) ad0: UDMA CRC WRITE ERROR blk# 8323183 retrying ad0: UDMA CRC WRITE ERROR blk# 2192287 retrying ad0: UDMA CRC WRITE ERROR blk# 2192287 retrying ad0: UDMA CRC WRITE ERROR blk# 2192287 retrying ad0: UDMA CRC WRITE ERROR blk# 2192287WARNING: WAIT_READY active=ATA_ACTIVE_ATA falling back to PIO mode cause this is what im getting on a brand new 10 gig maxtor udma66 disk > I've seen this, too. I haven't reported it because I wasn't 100% sure > that the wd driver wasn't lying, and I haven't had time to check it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 19:41:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [24.234.53.177]) by hub.freebsd.org (Postfix) with ESMTP id 003F715429 for ; Mon, 24 Jan 2000 19:41:05 -0800 (PST) (envelope-from freebsd@mrynet.com) Received: (from freebsd@localhost) by mrynet.com (8.9.3/8.9.3) id TAA00561; Mon, 24 Jan 2000 19:41:02 -0800 (PST) (envelope-from freebsd) Posted-Date: Mon, 24 Jan 2000 19:41:02 -0800 (PST) Message-Id: <200001250341.TAA00561@mrynet.com> From: freebsd@mrynet.com (FreeBSD mailing list) Date: Mon, 24 Jan 2000 19:41:02 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: Alfred Perlstein Subject: Re: sys/net/bridge.c IPFIREWALL & DUMMYNET? WTF? Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * Matthew N. Dodd [000124 18:11] wrote: > > Any reason that the IPFIREWALL and DUMMYNET code is present in > > sys/net/bridge.c? It appears that it makes a number of bad assumptions > > and in general violates the semantics of 'bridging' vs. 'routing'. > > > > Should we even encourage people to use this functionality? Do we really > > want bridge.c to have its own private IP stack? > > > > Should this code be diked out before 4.0 so we don't expose the masses to > > it? > > I'm not sure what your proposing, if it's removing BRIDGE support from > the kernel, I'd have to object. BRIDGE enables me to run a transparent > firewall without worrying about routing issues, just drop a machine > with BRIDGE and IPFIREWALL in between two points and everything is ok. > > However enable a DIVERT socket, and it all goes to hell last i checked. > > Anyhow, can you clarify? > > -Alfred I would also object. Rather than Matthew just complaining he doesn't like the coding style or the implementation, perhaps he could suggest something constructive towards improvement or redesign rather than criticise and suggest callously pitching it. This functionality has proven instrumental and necessary for transparent and effortless combining of unlike physical topologies. It also provides the extra protective measure of being able to firewall public traffic on subnetworks connected to public-traffic providers such as cable modems. The functionality of bridging is solid. The added functionality of bridging has nothing offensive to it except perhaps offending someone's idea of sensibility in this instance. Questioning code and usefulness is one thing. Presumtive resolve with disregard is another. Regards, Scott -- Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@mrynet.lv To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 19:48:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mathserv.mps.ohio-state.edu (mathserv.mps.ohio-state.edu [128.146.111.31]) by hub.freebsd.org (Postfix) with ESMTP id 78FE514D62 for ; Mon, 24 Jan 2000 19:48:48 -0800 (PST) (envelope-from ilya@math.ohio-state.edu) Received: from monk.mps.ohio-state.edu (monk.mps.ohio-state.edu [128.146.111.52]) by mathserv.mps.ohio-state.edu (8.9.3/8.9.3) with ESMTP id WAA23739; Mon, 24 Jan 2000 22:48:47 -0500 (EST) Received: (from ilya@localhost) by monk.mps.ohio-state.edu (8.9.3/8.9.3) id WAA21600; Mon, 24 Jan 2000 22:48:46 -0500 (EST) From: Ilya Zakharevich Message-Id: <200001250348.WAA21600@monk.mps.ohio-state.edu> Subject: Re: [ID 20000124.004] "perl in malloc(): warning: recursive call" on To: larse@ISI.EDU (Lars Eggert) Date: Mon, 24 Jan 2000 22:48:46 -0500 (EST) Cc: perl5-porters@perl.org, current@freebsd.org In-Reply-To: <200001250006.QAA13204@sub.isi.edu> from "Lars Eggert" at Jan 24, 2000 04:06:09 PM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lars Eggert writes: > Running the following test script causes perl to crash. You may need > to run the script several times before seeing the problem. (The script > spawns a child process that does nothing but write to an array. The > parent signals the child periodically.) Signals and Perl do not mix. Please do not use signals if a segfault is not a desirable form of output. > $SIG{ALRM} = sub { $state++ }; One should not do anything as bad as that in a sighandler. What is the failure rate you see? You may get slightly better rate (3% in my tests) with something like $SIG{ALRM} = sub { ++$state ; return }; and preallocating $state = 0; Ilya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 19:53:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3EE5114D76 for ; Mon, 24 Jan 2000 19:53:48 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id TAA14568 for ; Mon, 24 Jan 2000 19:53:46 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id TAA23630 for current@freebsd.org; Mon, 24 Jan 2000 19:53:46 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 24 Jan 2000 19:53:45 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: Alpha world breakage in sys/modules/if_tun Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This works on the i386 but fails on the Alpha: ===> sys/modules/if_tun @ -> /c/src/sys machine -> /c/src/sys/alpha/include touch opt_devfs.h echo "#define NETATALK 1" > opt_atalk.h echo "#define ATM_CORE 1" > opt_atm.h echo "#define INET 1" > opt_inet.h echo "#define INET6 1" > opt_inet6.h echo "#define IPX 1" > opt_ipx.h echo "#define NATM 1" > opt_natm.h perl @/kern/vnode_if.pl -h @/kern/vnode_if.src rm -f .depend mkdep -f .depend -a -nostdinc -D_KERNEL -DKLD_MODULE -I- -I. -I@ -I@/../includ e -I/usr/obj/c/src/alpha/usr/include /c/src/sys/modules/if_tun/../../net/if_tun .c In file included from @/netatm/kern_include.h:105, from /c/src/sys/modules/if_tun/../../net/if_tun.c:50: @/netatm/atm_if.h:349: #error - Must define hardware-specific requirements here mkdep: compile failed *** Error code 1 John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 19:55:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from viper.columbus.rr.com (viper.columbus.rr.com [204.210.252.254]) by hub.freebsd.org (Postfix) with ESMTP id 75B6B1507D for ; Mon, 24 Jan 2000 19:55:17 -0800 (PST) (envelope-from dzerkel@columbus.rr.com) Received: from columbus.rr.com (dhcp26140113.columbus.rr.com [24.26.140.113]) by viper.columbus.rr.com (8.9.3/8.9.3) with ESMTP id WAA15677 for ; Mon, 24 Jan 2000 22:55:10 -0500 (EST) Message-ID: <388D1E86.45CFA01@columbus.rr.com> Date: Mon, 24 Jan 2000 22:54:46 -0500 From: "Danny J. Zerkel" Organization: Zerkular Software X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: Russian, ru, en MIME-Version: 1.0 To: FreeBSD Current Subject: 4.0 CODE FREEZE vs PR patches Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG While I don't have much time to hack, I have tried to spend a little time going through the open PRs. When I find something I can reproduce, I try to fix it. How can I get the patches I have submitted into 4.0? Some of the problems were not very "obvious" patches, but all of them have been very short (unsually 1 or 2 lines), so I would guess that reviewing would not be quite as easy. How can I help? Who should I bug? The PRs in question: 4420 9350 12137 12242 12806 PS- Can someone update my email address in the contributors list? phofarm.com is no more. Some day I'll get a new domain... -- Danny J. Zerkel dzerkel@columbus.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 20: 3:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id C19121535D for ; Mon, 24 Jan 2000 20:03:35 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (andyf@localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id PAA14839 for ; Tue, 25 Jan 2000 15:03:32 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Tue, 25 Jan 2000 15:03:32 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: freebsd-current@freebsd.org Subject: ascii art in hosts.allow Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What is the reason for putting a giant "Example!" in hosts.allow? I note that it was committed at 3 o'clock in the morning... was someone trying to make a point? What other files have this type of gross bit-bloat in them? Here is a patch: (please notice the spelling correction) --- hosts.allow.orig Tue Jan 25 14:53:05 2000 +++ hosts.allow Tue Jan 25 14:56:45 2000 @@ -2,20 +2,14 @@ # hosts.allow access control file for "tcp wrapped" apps. # $FreeBSD: src/etc/hosts.allow,v 1.6 1999/11/25 03:00:44 obrien Exp $ # -# NOTE: The hosts.deny file is not longer used. Instead, put both 'allow' +# NOTE: This is an example file only. You will need to modify it for your +# specific requirements. + +# NOTE: The hosts.deny file is no longer used. Instead, put both 'allow' # and 'deny' rules in the hosts.allow file. + # see hosts_options(5) for the format of this file. # hosts_access(5) no longer fully applies. - -# _____ _ _ -# | ____| __ __ __ _ _ __ ___ _ __ | | ___ | | -# | _| \ \/ / / _` | | '_ ` _ \ | '_ \ | | / _ \ | | -# | |___ > < | (_| | | | | | | | | |_) | | | | __/ |_| -# |_____| /_/\_\ \__,_| |_| |_| |_| | .__/ |_| \___| (_) -# |_| -# !!! This is an example! You will need to modify it for your specific -# !!! requirements! - # Start by allowing everything (this prevents the rest of the file # from working, so remove it when you need protection). -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 20: 4: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 92224152F0 for ; Mon, 24 Jan 2000 20:04:02 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id XAA66170; Mon, 24 Jan 2000 23:03:59 -0500 (EST) Date: Mon, 24 Jan 2000 23:03:59 -0500 (EST) From: "Matthew N. Dodd" To: Alfred Perlstein Cc: current@FreeBSD.ORG Subject: Re: sys/net/bridge.c IPFIREWALL & DUMMYNET? WTF? In-Reply-To: <20000124190641.R26520@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Alfred Perlstein wrote: > I'm not sure what your proposing, if it's removing BRIDGE support from > the kernel, I'd have to object. BRIDGE enables me to run a transparent > firewall without worrying about routing issues, just drop a machine > with BRIDGE and IPFIREWALL in between two points and everything is ok. > > However enable a DIVERT socket, and it all goes to hell last i checked. > > Anyhow, can you clarify? Take a look at the code in question. There has got to be a better solution than duplicating packet-unrolling code that makes bad assumptions about mbuf layouts. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 20:26:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 28D6F14CF4; Mon, 24 Jan 2000 20:26:04 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id NAA73085; Tue, 25 Jan 2000 13:25:08 +0900 (JST) To: luoqi@watermarkgroup.com Cc: kato@ganko.eps.nagoya-u.ac.jp, FreeBSD-current@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG, FreeBSD98-hackers@jp.freebsd.org, nyan@jp.freebsd.org Subject: Re: indirection in bus space From: KATO Takenori In-Reply-To: Your message of "Mon, 24 Jan 2000 21:04:33 -0500 (EST)" <200001250204.VAA14309@lor.watermarkgroup.com> References: <200001250204.VAA14309@lor.watermarkgroup.com> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000125132456C.kato@gneiss.eps.nagoya-u.ac.jp> Date: Tue, 25 Jan 2000 13:24:56 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Luoqi Chen wrote: > You could set the handle to point to the structure instead: I think it is difficult to implement such conversion because: - Not only bus space stuff also resource manager stuff need to perform such conversion. - The type of the bus_space_handle_t can by determined only by the bus tag. The isa_alloc_resourcev (new function) cannot modify bus tag because what it does is only to allocate resources and it cannot register the address to the bus_space_handle_pc98. But allocated resources must be stored into bus_space_handle_pc98. -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 21: 5:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 1BEC4155EC for ; Mon, 24 Jan 2000 21:04:50 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 07A2B16BE; Mon, 24 Jan 2000 21:03:27 -0800 (PST) Date: Mon, 24 Jan 2000 21:03:27 -0800 From: Chris Piazza To: Andy Farkas Cc: freebsd-current@FreeBSD.ORG Subject: Re: ascii art in hosts.allow Message-ID: <20000124210327.A591@norn.ca.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from andyf@speednet.com.au on Tue, Jan 25, 2000 at 03:03:32PM +1100 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 25, 2000 at 03:03:32PM +1100, Andy Farkas wrote: > > > What is the reason for putting a giant "Example!" in hosts.allow? > > I note that it was committed at 3 o'clock in the morning... was someone > trying to make a point? > > What other files have this type of gross bit-bloat in them? I assume it's to make sure the point does actually get across to the user, though you're right: it is overkill. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 21:33:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 557BC14CB0 for ; Mon, 24 Jan 2000 21:33:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA98864; Mon, 24 Jan 2000 21:33:20 -0800 (PST) (envelope-from dillon) Date: Mon, 24 Jan 2000 21:33:20 -0800 (PST) From: Matthew Dillon Message-Id: <200001250533.VAA98864@apollo.backplane.com> To: current@freebsd.org Subject: Swapping to NFS via diskless mount broken - patch / review Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'd like a quick review of this patch. It looks like swapdev_vnode changes broke diskless swapping too, not just swap-backed VN. I'm sure glad someone filed a PR on this (kern/16165) or we would have gone into release with this bug. Now, normally I would take this opportunity to put forth some innane comment directed towards the perpetrators, but at the moment I am simply going to leave it by expressing my profound unhappiness over the lack of testing that has gone into commits recently (last couple of months). Lets please not bof-up this release! -Matt Index: vm_swap.c =================================================================== RCS file: /home/ncvs/src/sys/vm/vm_swap.c,v retrieving revision 1.95 diff -u -r1.95 vm_swap.c --- vm_swap.c 2000/01/10 12:04:27 1.95 +++ vm_swap.c 2000/01/25 04:49:32 @@ -210,14 +210,6 @@ if (error) vrele(vp); - if (!swapdev_vp) { - error = getnewvnode(VT_NON, NULL, swapdev_vnodeop_p, - &swapdev_vp); - if (error) - panic("Cannot get vnode for swapdev"); - swapdev_vp->v_type = VNON; /* Untyped */ - } - return (error); } @@ -245,6 +237,14 @@ register long blk; swblk_t dvbase; int error; + + if (!swapdev_vp) { + error = getnewvnode(VT_NON, NULL, swapdev_vnodeop_p, + &swapdev_vp); + if (error) + panic("Cannot get vnode for swapdev"); + swapdev_vp->v_type = VNON; /* Untyped */ + } ASSERT_VOP_UNLOCKED(vp, "swaponvp"); for (sp = swdevt, index = 0 ; index < nswdev; index++, sp++) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 21:44:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from midway.uchicago.edu (midway.uchicago.edu [128.135.12.12]) by hub.freebsd.org (Postfix) with ESMTP id 225F414CB0 for ; Mon, 24 Jan 2000 21:44:42 -0800 (PST) (envelope-from charon@freethought.org) Received: from broad-208-049 (broad-208-049.rh.uchicago.edu [128.135.208.49]) by midway.uchicago.edu (8.9.3/8.9.3) with ESMTP id XAA11626 for ; Mon, 24 Jan 2000 23:44:32 -0600 (CST) From: charon@freethought.org Message-Id: <4.2.2.20000124233054.00b81e00@nsit-popmail.uchicago.edu> X-Sender: dbsypher@nsit-popmail.uchicago.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Mon, 24 Jan 2000 23:43:59 -0600 To: current@freebsd.org Subject: connectivity problems with current.freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I know this perhaps isn't the proper list, but -questions and hostmaster@freebsd.org haven't replied this post, and the -current list tends to be a bit more on the ball. Anyway, the problem is about getting a -CURRENT snapshot :) ] For the past several days (at least since 20000118), I've been trying to connect to current.freebsd.org (209.180.6.226) to download the latest -current snapshot. I'm consistently getting the transmission interrupted with the message "! Receive error: Blocking call cancelled". (I'm using WS_FTP LE 5.06 for Windows NT.) This often happens after just an "ls" on the way to the snapshots directory, but occasionally happens after 30 or so of the 240640-byte blocks have been transferred. Notably, the transmission never seems to break in the process of transferring a file, just in between files. I believe that this is a problem with the server itself, as I am able to connect consistently with no errors to other FTP servers. By chance, playing around with the fact that current.freebsd.org is an alias for usw2.freebsd.org, I found that usw3.freebsd.org (209.180.6.227) mirrors snapshots as well. Perhaps something should be added to the /snapshots readme.txt on ftp.freebsd.org about the fact that current.freebsd.org has mirrors. That said, I've gotten the same error from usw3 as from usw2. Like I said, I've been using this same program/configuration for quite a while with other FTP servers, including ftp.freebsd.org. -David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 21:53:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by hub.freebsd.org (Postfix) with ESMTP id 2F32314E9D for ; Mon, 24 Jan 2000 21:53:34 -0800 (PST) (envelope-from larse@ISI.EDU) Received: from [128.9.176.131] (ras31.isi.edu [128.9.176.131]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id VAA27171; Mon, 24 Jan 2000 21:53:26 -0800 (PST) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Mon, 24 Jan 2000 21:53:27 -0800 Subject: Re: [ID 20000124.004] "perl in malloc(): warning: recursive call" on From: Lars Eggert To: Ilya Zakharevich , Lars Eggert Cc: , Message-ID: In-Reply-To: <200001250348.WAA21600@monk.mps.ohio-state.edu> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ilya, thanks for the quick response. > Signals and Perl do not mix. Please do not use signals if a segfault > is not a desirable form of output. Never? After reading perlipc I was under the impression that using signals was okay if you keep your handlers simple. I may have to use to another form of IPC if signals cannot be made safe. Lars ____________________________________________________________________________ Lars Eggert Information Sciences Institute http://www.isi.edu/~larse/ University of Southern California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 22: 1:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id DA8091536B; Mon, 24 Jan 2000 22:01:53 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id BAA17157; Tue, 25 Jan 2000 01:01:50 -0500 (EST) (envelope-from luoqi) Date: Tue, 25 Jan 2000 01:01:50 -0500 (EST) From: Luoqi Chen Message-Id: <200001250601.BAA17157@lor.watermarkgroup.com> To: kato@ganko.eps.nagoya-u.ac.jp Subject: Re: indirection in bus space Cc: FreeBSD-current@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG, FreeBSD98-hackers@jp.freebsd.org, nyan@jp.freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I think it is difficult to implement such conversion because: > > - Not only bus space stuff also resource manager stuff need to > perform such conversion. Why? Both bus_space_handle_t and bus_space_tag_t are supposed to be opaque types. Resource manager needs not know the implementation details. > - The type of the bus_space_handle_t can by determined only by the > bus tag. The isa_alloc_resourcev (new function) cannot modify bus > tag because what it does is only to allocate resources and it > cannot register the address to the bus_space_handle_pc98. But > allocated resources must be stored into bus_space_handle_pc98. > We could create a new resource type SYS_RES_IOPORT_ARRAY, and intercept it in all isa_*_resoruce() methods. In isa_alloc_resource(), we malloc and return a fake resource record, in which we store I386_BUS_PIO_IND as bus tag and address of bus_space_handle_pc98 as bus handle. And in isa_release_resource(), we first release the underlying resources stored in the bus_space_handle_pc98 record and then free the fake resource record itself. It should be safe as long as we don't manipulate this resource by direct resource manager calls, which we shouldn't do anyway. (or we should implement it at the root bus level, if pci devices in pc98 systems also use discrete port addresses). -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 22:20:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C1D5B15112; Mon, 24 Jan 2000 22:20:23 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id HAA47372; Tue, 25 Jan 2000 07:20:10 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001250620.HAA47372@freebsd.dk> Subject: Re: at driver problems (was: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS) In-Reply-To: <388D1CE1.28C90567@netquick.net> from TrouBle at "Jan 24, 2000 10:47:45 pm" To: trouble@netquick.net Date: Tue, 25 Jan 2000 07:20:10 +0100 (CET) Cc: grog@lemis.com (Greg Lehey), kris@hub.freebsd.org (Kris Kennaway), jkh@zippy.cdrom.com (Jordan K. Hubbard), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems TrouBle wrote: > does it look like this ??? Could I have a complete dmesg, or at least all the lines that belongs to the ata driver ?? I need to know what chips etc to be able to diagnose further... > ad0: 9770MB (20010816 sectors), 19852 cyls, 16 heads, 63 S/T, 512 B/S > ad0: 16 secs/int, 1 depth queue, UDMA33 > acd0: CDROM drive at ata0 as slave > acd0: read 6890KB/s (6890KB/s), 256KB buffer, PIO4 > acd0: Reads: CD-R, CD-RW, CD-DA stream, packet > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 22:35:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9570315349 for ; Mon, 24 Jan 2000 22:35:10 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id WAA22843 for ; Mon, 24 Jan 2000 22:35:10 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id WAA83022 for current@freebsd.org; Mon, 24 Jan 2000 22:35:11 -0800 (PST) (envelope-from obrien) Date: Mon, 24 Jan 2000 22:35:11 -0800 From: "David O'Brien" To: current@freebsd.org Subject: ** HEADS UP ** Compiler / C++ library changes Message-ID: <20000124223511.A82859@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Later tonight I will make a change to our base C++ compiler that will change the way virtual tables are handled. Currently we are using THUNKS for virtual inheritance. Unfortunately there are bugs that The GCC developers thought would be fixed in GCC 2.95. However it isn't. After this change existing applications written in C++ may give errors like below when you try to run them: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "__vt_7filebuf" The only fix is to rebuild the application and any C++ libraries used. We must make this change now, or we will have to live with this bug for the life of the entire 4.x release series. If you are interested in knowing more about the issue, I have placed some applicable emails from the GCC development lists in Berkeley mailbox format at ftp://relay.nuxi.com/obrien/thunks.mbox -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 22:36: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from mathserv.mps.ohio-state.edu (mathserv.mps.ohio-state.edu [128.146.111.31]) by hub.freebsd.org (Postfix) with ESMTP id 397CB14D06 for ; Mon, 24 Jan 2000 22:36:00 -0800 (PST) (envelope-from ilya@math.ohio-state.edu) Received: from math.mps.ohio-state.edu (math.mps.ohio-state.edu [128.146.111.30]) by mathserv.mps.ohio-state.edu (8.9.3/8.9.3) with ESMTP id BAA02545; Tue, 25 Jan 2000 01:35:59 -0500 (EST) Received: (from ilya@localhost) by math.mps.ohio-state.edu (8.9.3+Sun/8.9.3) id BAA14003; Tue, 25 Jan 2000 01:35:59 -0500 (EST) Date: Tue, 25 Jan 2000 01:35:58 -0500 From: Ilya Zakharevich To: Lars Eggert Cc: perl5-porters@perl.org, current@freebsd.org Subject: Re: [ID 20000124.004] "perl in malloc(): warning: recursive call" on Message-ID: <20000125013558.B13760@math.mps.ohio-state.edu> References: <200001250348.WAA21600@monk.mps.ohio-state.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from larse@ISI.EDU on Mon, Jan 24, 2000 at 09:53:27PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 24, 2000 at 09:53:27PM -0800, Lars Eggert wrote: > > Signals and Perl do not mix. Please do not use signals if a segfault > > is not a desirable form of output. > > Never? Never. Well, I did not try XSUB signal handlers, but if it is a Perl subroutine, then the harm may be already done *before* the subroutine starts. Ilya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 22:44:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from info.iet.unipi.it (info.iet.unipi.it [131.114.9.184]) by hub.freebsd.org (Postfix) with ESMTP id 7073614D06 for ; Mon, 24 Jan 2000 22:44:22 -0800 (PST) (envelope-from luigi@info.iet.unipi.it) Received: (from luigi@localhost) by info.iet.unipi.it (8.9.3/8.9.3) id HAA06859; Tue, 25 Jan 2000 07:44:51 +0100 (CET) (envelope-from luigi) From: Luigi Rizzo Message-Id: <200001250644.HAA06859@info.iet.unipi.it> Subject: Re: sys/net/bridge.c IPFIREWALL & DUMMYNET? WTF? In-Reply-To: from "Matthew N. Dodd" at "Jan 24, 2000 08:47:02 pm" To: "Matthew N. Dodd" Date: Tue, 25 Jan 2000 07:44:51 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > Any reason that the IPFIREWALL and DUMMYNET code is present in > sys/net/bridge.c? It appears that it makes a number of bad assumptions > and in general violates the semantics of 'bridging' vs. 'routing'. the reason is that I needed that functionality, and according to my experience most people who use bridging on FreeBSD do it just because they can build a transparent firewall/traffic shaper. They tell me there are very few if any solutions like this on the market. So i don't think it is a good idea to remove this feature which is a very strong selling point. As for the quality of the code, (and i hope you refer to the version just committed to -current/-stable) i myself i am not terribly happy with it, but perhaps if you point out what are the bad assumptions i make it would help me fix the code. cheers luigi > Should we even encourage people to use this functionality? Do we really > want bridge.c to have its own private IP stack? > > Should this code be diked out before 4.0 so we don't expose the masses to > it? > > -- > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 23: 4:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 3CA84150F7 for ; Mon, 24 Jan 2000 23:04:54 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id XAA15148 for ; Mon, 24 Jan 2000 23:04:53 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id XAA23891 for current@freebsd.org; Mon, 24 Jan 2000 23:04:52 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="_=XFMail.1.3.p0.FreeBSD:000124230452:13367=_" Date: Mon, 24 Jan 2000 23:04:52 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: Need testers for libc_r patch Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format --_=XFMail.1.3.p0.FreeBSD:000124230452:13367=_ Content-Type: text/plain; charset=us-ascii The attached patch makes libc_r use the recently added hooks in the dynamic linker to provide locking so that the dynamic linker is thread-safe. I have tested it in a simple program and I believe it works OK. If any of you have a -current system with a non-trivial libc_r application, I would appreciate it if you'd give this patch a try and let me know whether you see any problems with it. You can apply the patch by getting into "src/lib/libc_r" and typing "patch -IEp < libc_r.patch" Also, if anybody can point me to programs in the ports collection that use libc_r and aren't too hard to set up and run, that would be helpful too. Thanks, John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa --_=XFMail.1.3.p0.FreeBSD:000124230452:13367=_ Content-Disposition: attachment; filename="libc_r.patch" Content-Transfer-Encoding: base64 Content-Description: libc_r.patch Content-Type: application/octet-stream; name=libc_r.patch; SizeOnDisk=4952 SW5kZXg6IHV0aHJlYWQvTWFrZWZpbGUuaW5jCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZpbGU6IC9ob21lL25j dnMvc3JjL2xpYi9saWJjX3IvdXRocmVhZC9NYWtlZmlsZS5pbmMsdgpyZXRyaWV2aW5nIHJldmlz aW9uIDEuMjIKZGlmZiAtdSAtcjEuMjIgTWFrZWZpbGUuaW5jCi0tLSB1dGhyZWFkL01ha2VmaWxl LmluYwkyMDAwLzAxLzIwIDA3OjU0OjQ4CTEuMjIKKysrIHV0aHJlYWQvTWFrZWZpbGUuaW5jCTIw MDAvMDEvMjUgMDY6NDA6MTUKQEAgLTMzLDYgKzMzLDcgQEAKIAl1dGhyZWFkX2Nvbm5lY3QuYyBc CiAJdXRocmVhZF9jcmVhdGUuYyBcCiAJdXRocmVhZF9kZXRhY2guYyBcCisJdXRocmVhZF9kbGxv Y2suYyBcCiAJdXRocmVhZF9kdXAuYyBcCiAJdXRocmVhZF9kdXAyLmMgXAogCXV0aHJlYWRfZXF1 YWwuYyBcCkluZGV4OiB1dGhyZWFkL3B0aHJlYWRfcHJpdmF0ZS5oCj09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT0KUkNTIGZp bGU6IC9ob21lL25jdnMvc3JjL2xpYi9saWJjX3IvdXRocmVhZC9wdGhyZWFkX3ByaXZhdGUuaCx2 CnJldHJpZXZpbmcgcmV2aXNpb24gMS4zNgpkaWZmIC11IC1yMS4zNiBwdGhyZWFkX3ByaXZhdGUu aAotLS0gdXRocmVhZC9wdGhyZWFkX3ByaXZhdGUuaAkyMDAwLzAxLzIwIDIxOjUzOjU4CTEuMzYK KysrIHV0aHJlYWQvcHRocmVhZF9wcml2YXRlLmgJMjAwMC8wMS8yNSAwNjo1NToyMgpAQCAtMTAz Niw2ICsxMDM2LDcgQEAKIHZvaWQgICAgX3RocmVhZF9mZF91bmxvY2tfb3duZWQocHRocmVhZF90 KTsKIHZvaWQgICAgKl90aHJlYWRfY2xlYW51cChwdGhyZWFkX3QpOwogdm9pZCAgICBfdGhyZWFk X2NsZWFudXBzcGVjaWZpYyh2b2lkKTsKK3ZvaWQgICAgX3RocmVhZF9kbGxvY2tpbml0KHZvaWQp Owogdm9pZCAgICBfdGhyZWFkX2R1bXBfaW5mbyh2b2lkKTsKIHZvaWQgICAgX3RocmVhZF9pbml0 KHZvaWQpOwogdm9pZCAgICBfdGhyZWFkX2tlcm5fc2NoZWQodWNvbnRleHRfdCAqKTsKSW5kZXg6 IHV0aHJlYWQvdXRocmVhZF9kbGxvY2suYwo9PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09ClJDUyBmaWxlOiB1dGhyZWFkX2Rs bG9jay5jCmRpZmYgLU4gdXRocmVhZF9kbGxvY2suYwotLS0gL2Rldi9udWxsCU1vbiBKYW4gMjQg MjE6NTU6NTMgMjAwMAorKysgdXRocmVhZF9kbGxvY2suYwlNb24gSmFuIDI0IDIyOjQ0OjIxIDIw MDAKQEAgLTAsMCArMSw4OCBAQAorLyoKKyAqIENvcHlyaWdodCAoYykgMjAwMCBKb2huIEQuIFBv bHN0cmEKKyAqIEFsbCByaWdodHMgcmVzZXJ2ZWQuCisgKgorICogUmVkaXN0cmlidXRpb24gYW5k IHVzZSBpbiBzb3VyY2UgYW5kIGJpbmFyeSBmb3Jtcywgd2l0aCBvciB3aXRob3V0CisgKiBtb2Rp ZmljYXRpb24sIGFyZSBwZXJtaXR0ZWQgcHJvdmlkZWQgdGhhdCB0aGUgZm9sbG93aW5nIGNvbmRp dGlvbnMKKyAqIGFyZSBtZXQ6CisgKiAxLiBSZWRpc3RyaWJ1dGlvbnMgb2Ygc291cmNlIGNvZGUg bXVzdCByZXRhaW4gdGhlIGFib3ZlIGNvcHlyaWdodAorICogICAgbm90aWNlLCB0aGlzIGxpc3Qg b2YgY29uZGl0aW9ucyBhbmQgdGhlIGZvbGxvd2luZyBkaXNjbGFpbWVyLgorICogMi4gUmVkaXN0 cmlidXRpb25zIGluIGJpbmFyeSBmb3JtIG11c3QgcmVwcm9kdWNlIHRoZSBhYm92ZSBjb3B5cmln aHQKKyAqICAgIG5vdGljZSwgdGhpcyBsaXN0IG9mIGNvbmRpdGlvbnMgYW5kIHRoZSBmb2xsb3dp bmcgZGlzY2xhaW1lciBpbiB0aGUKKyAqICAgIGRvY3VtZW50YXRpb24gYW5kL29yIG90aGVyIG1h dGVyaWFscyBwcm92aWRlZCB3aXRoIHRoZSBkaXN0cmlidXRpb24uCisgKiAzLiBBbGwgYWR2ZXJ0 aXNpbmcgbWF0ZXJpYWxzIG1lbnRpb25pbmcgZmVhdHVyZXMgb3IgdXNlIG9mIHRoaXMgc29mdHdh cmUKKyAqICAgIG11c3QgZGlzcGxheSB0aGUgZm9sbG93aW5nIGFja25vd2xlZGdlbWVudDoKKyAq CVRoaXMgcHJvZHVjdCBpbmNsdWRlcyBzb2Z0d2FyZSBkZXZlbG9wZWQgYnkgSm9obiBCaXJyZWxs LgorICogNC4gTmVpdGhlciB0aGUgbmFtZSBvZiB0aGUgYXV0aG9yIG5vciB0aGUgbmFtZXMgb2Yg YW55IGNvLWNvbnRyaWJ1dG9ycworICogICAgbWF5IGJlIHVzZWQgdG8gZW5kb3JzZSBvciBwcm9t b3RlIHByb2R1Y3RzIGRlcml2ZWQgZnJvbSB0aGlzIHNvZnR3YXJlCisgKiAgICB3aXRob3V0IHNw ZWNpZmljIHByaW9yIHdyaXR0ZW4gcGVybWlzc2lvbi4KKyAqCisgKiBUSElTIFNPRlRXQVJFIElT IFBST1ZJREVEIEJZIFRIRSBBVVRIT1IgQU5EIENPTlRSSUJVVE9SUyBgYEFTIElTJycgQU5ECisg KiBBTlkgRVhQUkVTUyBPUiBJTVBMSUVEIFdBUlJBTlRJRVMsIElOQ0xVRElORywgQlVUIE5PVCBM SU1JVEVEIFRPLCBUSEUKKyAqIElNUExJRUQgV0FSUkFOVElFUyBPRiBNRVJDSEFOVEFCSUxJVFkg QU5EIEZJVE5FU1MgRk9SIEEgUEFSVElDVUxBUiBQVVJQT1NFCisgKiBBUkUgRElTQ0xBSU1FRC4g IElOIE5PIEVWRU5UIFNIQUxMIFRIRSBBVVRIT1IgT1IgQ09OVFJJQlVUT1JTIEJFIExJQUJMRQor ICogRk9SIEFOWSBESVJFQ1QsIElORElSRUNULCBJTkNJREVOVEFMLCBTUEVDSUFMLCBFWEVNUExB UlksIE9SIENPTlNFUVVFTlRJQUwKKyAqIERBTUFHRVMgKElOQ0xVRElORywgQlVUIE5PVCBMSU1J VEVEIFRPLCBQUk9DVVJFTUVOVCBPRiBTVUJTVElUVVRFIEdPT0RTCisgKiBPUiBTRVJWSUNFUzsg TE9TUyBPRiBVU0UsIERBVEEsIE9SIFBST0ZJVFM7IE9SIEJVU0lORVNTIElOVEVSUlVQVElPTikK KyAqIEhPV0VWRVIgQ0FVU0VEIEFORCBPTiBBTlkgVEhFT1JZIE9GIExJQUJJTElUWSwgV0hFVEhF UiBJTiBDT05UUkFDVCwgU1RSSUNUCisgKiBMSUFCSUxJVFksIE9SIFRPUlQgKElOQ0xVRElORyBO RUdMSUdFTkNFIE9SIE9USEVSV0lTRSkgQVJJU0lORyBJTiBBTlkgV0FZCisgKiBPVVQgT0YgVEhF IFVTRSBPRiBUSElTIFNPRlRXQVJFLCBFVkVOIElGIEFEVklTRUQgT0YgVEhFIFBPU1NJQklMSVRZ IE9GCisgKiBTVUNIIERBTUFHRS4KKyAqCisgKiAkRnJlZUJTRCQKKyAqLworCisjaW5jbHVkZSA8 ZGxmY24uaD4KKyNpbmNsdWRlIDxzdGRsaWIuaD4KKyNpZmRlZiBfVEhSRUFEX1NBRkUKKyNpbmNs dWRlIDxwdGhyZWFkLmg+CisjaW5jbHVkZSAicHRocmVhZF9wcml2YXRlLmgiCisKK3N0YXRpYyB2 b2lkICoKK2xvY2tfY3JlYXRlKHZvaWQgKmN0eCkKK3sKKwlwdGhyZWFkX3J3bG9ja190ICpsb2Nr OworCisJaWYgKChsb2NrID0gbWFsbG9jKHNpemVvZihwdGhyZWFkX3J3bG9ja190KSkpID09IE5V TEwpCisJCVBBTklDKCJDYW5ub3QgYWxsb2NhdGUgcndsb2NrIGZvciBkeW5hbWljIGxpbmtlciIp OworCWlmIChwdGhyZWFkX3J3bG9ja19pbml0KGxvY2ssIE5VTEwpICE9IDApCisJCVBBTklDKCJD YW5ub3QgaW5pdGlhbGl6ZSByd2xvY2sgZm9yIGR5bmFtaWMgbGlua2VyIik7CisJcmV0dXJuIGxv Y2s7Cit9CisKK3N0YXRpYyB2b2lkCitybG9ja19hY3F1aXJlKHZvaWQgKmxvY2spCit7CisJaWYg KHB0aHJlYWRfcndsb2NrX3JkbG9jaygocHRocmVhZF9yd2xvY2tfdCAqKWxvY2spICE9IDApCisJ CVBBTklDKCJDYW5ub3QgbG9jayBkeW5hbWljIGxpbmtlciByd2xvY2sgZm9yIHJlYWRpbmciKTsK K30KKworc3RhdGljIHZvaWQKK3dsb2NrX2FjcXVpcmUodm9pZCAqbG9jaykKK3sKKwlpZiAocHRo cmVhZF9yd2xvY2tfd3Jsb2NrKChwdGhyZWFkX3J3bG9ja190ICopbG9jaykgIT0gMCkKKwkJUEFO SUMoIkNhbm5vdCBsb2NrIGR5bmFtaWMgbGlua2VyIHJ3bG9jayBmb3Igd3JpdGluZyIpOworfQor CitzdGF0aWMgdm9pZAorbG9ja19yZWxlYXNlKHZvaWQgKmxvY2spCit7CisJaWYgKHB0aHJlYWRf cndsb2NrX3VubG9jaygocHRocmVhZF9yd2xvY2tfdCAqKWxvY2spICE9IDApCisJCVBBTklDKCJD YW5ub3QgdW5sb2NrIGR5bmFtaWMgbGlua2VyIHJ3bG9jayIpOworfQorCitzdGF0aWMgdm9pZAor bG9ja19kZXN0cm95KHZvaWQgKmxvY2spCit7CisJaWYgKHB0aHJlYWRfcndsb2NrX2Rlc3Ryb3ko KHB0aHJlYWRfcndsb2NrX3QgKilsb2NrKSAhPSAwKQorCQlQQU5JQygiQ2Fubm90IGRlc3Ryb3kg ZHluYW1pYyBsaW5rZXIgcndsb2NrIik7CisJZnJlZShsb2NrKTsKK30KKwordm9pZAorX3RocmVh ZF9kbGxvY2tpbml0KHZvaWQpCit7CisJZGxsb2NraW5pdChOVUxMLCBsb2NrX2NyZWF0ZSwgcmxv Y2tfYWNxdWlyZSwgd2xvY2tfYWNxdWlyZSwKKwkgICAgbG9ja19yZWxlYXNlLCBsb2NrX2Rlc3Ry b3ksIE5VTEwpOworfQorI2VuZGlmCkluZGV4OiB1dGhyZWFkL3V0aHJlYWRfaW5pdC5jCj09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT0KUkNTIGZpbGU6IC9ob21lL25jdnMvc3JjL2xpYi9saWJjX3IvdXRocmVhZC91dGhyZWFk X2luaXQuYyx2CnJldHJpZXZpbmcgcmV2aXNpb24gMS4yMwpkaWZmIC11IC1yMS4yMyB1dGhyZWFk X2luaXQuYwotLS0gdXRocmVhZC91dGhyZWFkX2luaXQuYwkyMDAwLzAxLzE5IDA3OjA0OjQ3CTEu MjMKKysrIHV0aHJlYWQvdXRocmVhZF9pbml0LmMJMjAwMC8wMS8yNSAwNjozNjoyMQpAQCAtMzYw LDYgKzM2MCw5IEBACiAJICAgIHB0aHJlYWRfY29uZF9pbml0KCZfZ2NfY29uZCxOVUxMKSAhPSAw KQogCQlQQU5JQygiRmFpbGVkIHRvIGluaXRpYWxpc2UgZ2FyYmFnZSBjb2xsZWN0b3IgbXV0ZXgg b3IgY29uZHZhciIpOwogCisJLyogU2V0IHVwIHRoZSBsb2NraW5nIHRvIG1ha2UgdGhlIGR5bmFt aWMgbGlua2VyIHRocmVhZC1zYWZlLiAqLworCV90aHJlYWRfZGxsb2NraW5pdCgpOworCiAJZ2V0 dGltZW9mZGF5KCZrZXJuX2luY19wcmlvX3RpbWUsIE5VTEwpOwogCiAJcmV0dXJuOwo= --_=XFMail.1.3.p0.FreeBSD:000124230452:13367=_-- End of MIME message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 23:19:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 3013914E06 for ; Mon, 24 Jan 2000 23:19:08 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA61546; Tue, 25 Jan 2000 08:19:04 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001250719.IAA61546@freebsd.dk> Subject: Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS In-Reply-To: <4.2.0.58.20000124185659.0095acb0@pop.uky.edu> from Greg Childers at "Jan 24, 2000 07:03:43 pm" To: gchil0@pop.uky.edu (Greg Childers) Date: Tue, 25 Jan 2000 08:19:04 +0100 (CET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Greg Childers wrote: > > >Huh, you have only told me about the missing CDROM (should be fixed > >with the commit I just did), what else seems to be a problem ?? > > On some older PCI systems, including my Pentium 66, the driver still detects > irq 0 for ata-pci0. Hardwiring it to irq 14 in the source as suggested recently is the temporary fix I'm using. Could you send that patch around me please ? -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 23:25:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id D75E414A1F for ; Mon, 24 Jan 2000 23:25:52 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA99663; Mon, 24 Jan 2000 23:25:52 -0800 (PST) (envelope-from dillon) Date: Mon, 24 Jan 2000 23:25:52 -0800 (PST) From: Matthew Dillon Message-Id: <200001250725.XAA99663@apollo.backplane.com> To: current@FreeBSD.ORG Subject: nqnfs bug PR kern/15883, patch to review Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This patch is designed to fix PR kern/15883. This PR is very easy to reproduce. http://www.freebsd.org/cgi/query-pr.cgi?pr=15883 Unfortunately the patch is not entirely trivial. NQNFS has a horrendous bug in the code in question -- it's accessing a structure pointer from union elements that are not properly initialized when you use a UDP NQNFS mount. TCP NQNFS mounts are not effected. There are probably only a handful of people that understand this code well enough to review it, unfortunately. If I don't get any responses I'll get a special dispensation to commit the beast because UDP NQNFS mounts are dangerous without it (and NQNFS is considered highly experimental anyway). I've emailed the author of the PR but may not get a response quickly enough. -Matt Index: nfs_nqlease.c =================================================================== RCS file: /home/ncvs/src/sys/nfs/nfs_nqlease.c,v retrieving revision 1.48 diff -u -r1.48 nfs_nqlease.c --- nfs_nqlease.c 1999/12/19 01:55:37 1.48 +++ nfs_nqlease.c 2000/01/25 07:01:01 @@ -387,6 +387,7 @@ return; } nsso = slp->ns_so; + lph->lph_slp = slp; if (nsso && nsso->so_proto->pr_protocol == IPPROTO_UDP) { saddr = (struct sockaddr_in *)nam; lph->lph_flag |= (LC_VALID | LC_UDP); @@ -399,7 +400,6 @@ #endif } else { lph->lph_flag |= (LC_VALID | LC_SREF); - lph->lph_slp = slp; slp->ns_sref++; } } @@ -506,7 +506,6 @@ register int siz; struct nqm *lphnext = lp->lc_morehosts; struct mbuf *m, *mreq, *mb, *mb2, *mheadend; - struct socket *so; struct sockaddr *nam2; struct sockaddr_in *saddr; nfsfh_t nfh; @@ -514,12 +513,16 @@ caddr_t bpos, cp; u_int32_t xid, *tl; int len = 1, ok = 1, i = 0; - int sotype, *solockp; while (ok && (lph->lph_flag & LC_VALID)) { - if (nqsrv_cmpnam(slp, nam, lph)) + if (nqsrv_cmpnam(slp, nam, lph)) { lph->lph_flag |= LC_VACATED; - else if ((lph->lph_flag & (LC_LOCAL | LC_VACATED)) == 0) { + } else if ((lph->lph_flag & (LC_LOCAL | LC_VACATED)) == 0) { + struct socket *so; + int sotype; + int *solockp = NULL; + + so = lph->lph_slp->ns_so; if (lph->lph_flag & LC_UDP) { MALLOC(nam2, struct sockaddr *, sizeof *nam2, M_SONAME, M_WAITOK); @@ -528,20 +531,16 @@ saddr->sin_family = AF_INET; saddr->sin_addr.s_addr = lph->lph_inetaddr; saddr->sin_port = lph->lph_port; - so = lph->lph_slp->ns_so; } else if (lph->lph_flag & LC_CLTP) { nam2 = lph->lph_nam; - so = lph->lph_slp->ns_so; } else if (lph->lph_slp->ns_flag & SLP_VALID) { nam2 = (struct sockaddr *)0; - so = lph->lph_slp->ns_so; - } else + } else { goto nextone; + } sotype = so->so_type; if (so->so_proto->pr_flags & PR_CONNREQUIRED) solockp = &lph->lph_slp->ns_solock; - else - solockp = (int *)0; nfsm_reqhead((struct vnode *)0, NQNFSPROC_EVICTED, NFSX_V3FH + NFSX_UNSIGNED); fhp = &nfh.fh_generic; @@ -576,11 +575,11 @@ * nfs_sndlock if PR_CONNREQUIRED XXX */ - if (((lph->lph_flag & (LC_UDP | LC_CLTP)) == 0 && - (lph->lph_slp->ns_flag & SLP_VALID) == 0) || - (nfs_slplock(lph->lph_slp, 0) == 0)) + if ((lph->lph_flag & (LC_UDP | LC_CLTP)) == 0 && + ((lph->lph_slp->ns_flag & SLP_VALID) == 0 || + nfs_slplock(lph->lph_slp, 0) == 0)) { m_freem(m); - else { + } else { (void) nfs_send(so, nam2, m, (struct nfsreq *)0); if (solockp) Index: nqnfs.h =================================================================== RCS file: /home/ncvs/src/sys/nfs/nqnfs.h,v retrieving revision 1.20 diff -u -r1.20 nqnfs.h --- nqnfs.h 1999/12/29 04:54:55 1.20 +++ nqnfs.h 2000/01/25 07:02:20 @@ -87,31 +87,26 @@ #define LC_MOREHOSTSIZ 10 struct nqhost { + u_int16_t lph_flag; + u_int16_t lph_port; + struct nfssvc_sock *lph_slp; + union { struct { - u_int16_t udp_flag; - u_int16_t udp_port; union nethostaddr udp_haddr; } un_udp; struct { - u_int16_t connless_flag; - u_int16_t connless_spare; union nethostaddr connless_haddr; } un_connless; struct { - u_int16_t conn_flag; - u_int16_t conn_spare; - struct nfssvc_sock *conn_slp; + int dummy; } un_conn; } lph_un; }; -#define lph_flag lph_un.un_udp.udp_flag -#define lph_port lph_un.un_udp.udp_port #define lph_haddr lph_un.un_udp.udp_haddr #define lph_inetaddr lph_un.un_udp.udp_haddr.had_inetaddr #define lph_claddr lph_un.un_connless.connless_haddr #define lph_nam lph_un.un_connless.connless_haddr.had_nam -#define lph_slp lph_un.un_conn.conn_slp struct nqlease { LIST_ENTRY(nqlease) lc_hash; /* Fhandle hash list */ @@ -123,7 +118,7 @@ char lc_fiddata[MAXFIDSZ]; struct vnode *lc_vp; /* Soft reference to associated vnode */ }; -#define lc_flag lc_host.lph_un.un_udp.udp_flag +#define lc_flag lc_host.lph_flag /* lc_flag bits */ #define LC_VALID 0x0001 /* Host address valid */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 23:29:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4B6DA15234 for ; Mon, 24 Jan 2000 23:29:44 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA64029; Tue, 25 Jan 2000 08:29:32 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001250729.IAA64029@freebsd.dk> Subject: Re: My ATAPI CD not come ready In-Reply-To: <86vh4jaz0w.wl@tkc.att.ne.jp> from Motomichi Matsuzaki at "Jan 25, 2000 07:24:47 am" To: mzaki@e-mail.ne.jp (Motomichi Matsuzaki) Date: Tue, 25 Jan 2000 08:29:32 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Motomichi Matsuzaki wrote: > > Thank you for fixing, but still not probed. > What can I do for your work? > ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 > ata0: mask=03 status0=50 status1=00 > ata0: mask=03 status0=00 status1=00 > ata0: devices = 0x4 > ata0 at 0x01f0 irq 14 on ata-pci0 > : > ata-isa0: already registered as ata0 > : > ata0-master: ata_command: timeout waiting for intr That has me worried, what make/version is the drive ?? -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 23:38:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 736C31523F for ; Mon, 24 Jan 2000 23:38:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA23146; Mon, 24 Jan 2000 23:38:33 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA83484; Mon, 24 Jan 2000 23:38:34 -0800 (PST) (envelope-from obrien) Date: Mon, 24 Jan 2000 23:38:34 -0800 From: "David O'Brien" To: Andy Farkas Cc: freebsd-current@freebsd.org Subject: Re: ascii art in hosts.allow Message-ID: <20000124233834.A83466@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from andyf@speednet.com.au on Tue, Jan 25, 2000 at 03:03:32PM +1100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 25, 2000 at 03:03:32PM +1100, Andy Farkas wrote: > What is the reason for putting a giant "Example!" in hosts.allow? So you'll notice that this file is an example and *demands* your attention in configuring your system properly. > I note that it was committed at 3 o'clock in the morning... Sounds like normal hacking time to me. > was someone trying to make a point? Yes, don't shoot yourself in the foot by leaving your system wide open. > What other files have this type of gross bit-bloat in them? src/sys/ -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 23:43:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7160C150F7 for ; Mon, 24 Jan 2000 23:43:29 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id XAA23169; Mon, 24 Jan 2000 23:43:28 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id XAA83592; Mon, 24 Jan 2000 23:43:29 -0800 (PST) (envelope-from obrien) Date: Mon, 24 Jan 2000 23:43:29 -0800 From: "David O'Brien" To: Andy Farkas Cc: freebsd-current@freebsd.org Subject: Re: ascii art in hosts.allow Message-ID: <20000124234329.C83466@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from andyf@speednet.com.au on Tue, Jan 25, 2000 at 03:03:32PM +1100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 25, 2000 at 03:03:32PM +1100, Andy Farkas wrote: > Here is a patch: (please notice the spelling correction) Where? I just ran ispell on src/etc/hosts.allow and it didn't catch anything. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 23:45:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from tkc.att.ne.jp (tkc.att.ne.jp [165.76.16.7]) by hub.freebsd.org (Postfix) with ESMTP id E91B014F47 for ; Mon, 24 Jan 2000 23:45:10 -0800 (PST) (envelope-from mzaki@e-mail.ne.jp) Received: from work.mzaki.nom (36.pool5.tokyo.att.ne.jp [165.76.22.51]) by tkc.att.ne.jp (8.8.8+Spin/3.6W-CONS(10/24/99)) id QAA15470; Tue, 25 Jan 2000 16:44:55 +0900 (JST) Received: from work.mzaki.nom (mzaki@localhost [127.0.0.1]) by work.mzaki.nom (8.9.3/8.9.3) with ESMTP id QAA00922; Tue, 25 Jan 2000 16:44:41 +0900 (JST) (envelope-from mzaki@e-mail.ne.jp) Date: Tue, 25 Jan 2000 16:44:40 +0900 Message-ID: <86snzmbno7.wl@tkc.att.ne.jp> From: Motomichi Matsuzaki To: sos@freebsd.dk Cc: mzaki@e-mail.ne.jp, current@FreeBSD.ORG Subject: Re: My ATAPI CD not come ready In-Reply-To: In your message of "Tue, 25 Jan 2000 08:29:32 +0100 (CET)" <200001250729.IAA64029@freebsd.dk> References: <86vh4jaz0w.wl@tkc.att.ne.jp> <200001250729.IAA64029@freebsd.dk> X-Mailer: Wanderlust/2.2.12 (Joyride) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 (generated by WEMI 1.13.7 - "Shimada") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At Tue, 25 Jan 2000 08:29:32 +0100 (CET), Soren Schmidt wrote: > > Thank you for fixing, but still not probed. > > ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 > > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xf000 > > ata0: mask=03 status0=50 status1=00 > > ata0: mask=03 status0=00 status1=00 > > ata0: devices = 0x4 > > ata0 at 0x01f0 irq 14 on ata-pci0 > > : > > ata-isa0: already registered as ata0 > > : > > ata0-master: ata_command: timeout waiting for intr > > That has me worried, what make/version is the drive ?? > wdc says: wdc0: unit 0 (atapi): , removable, accel, dma,iordy -- Motomichi Matsuzaki Dept. of Biological Science, Faculty of Sciences, Univ. of Tokyo, Japan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 24 23:46: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from celery.dragondata.com (celery.dragondata.com [205.253.12.6]) by hub.freebsd.org (Postfix) with ESMTP id B34C6152EA; Mon, 24 Jan 2000 23:46:05 -0800 (PST) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id BAA67744; Tue, 25 Jan 2000 01:46:01 -0600 (CST) (envelope-from toasty) From: Kevin Day Message-Id: <200001250746.BAA67744@celery.dragondata.com> Subject: Re: ascii art in hosts.allow To: obrien@FreeBSD.ORG Date: Tue, 25 Jan 2000 01:46:01 -0600 (CST) Cc: andyf@speednet.com.au (Andy Farkas), freebsd-current@FreeBSD.ORG In-Reply-To: <20000124234329.C83466@dragon.nuxi.com> from "David O'Brien" at Jan 24, 2000 11:43:29 PM X-Mailer: ELM [version 2.5 PL1] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Tue, Jan 25, 2000 at 03:03:32PM +1100, Andy Farkas wrote: > > Here is a patch: (please notice the spelling correction) > > Where? I just ran ispell on src/etc/hosts.allow and it didn't catch > anything. A more direct patch would have been: -# NOTE: The hosts.deny file is not longer used. Instead, put both 'allow' +# NOTE: The hosts.deny file is no longer used. Instead, put both 'allow' :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 0: 6: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id AD4E9151F1; Tue, 25 Jan 2000 00:05:59 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12D0ye-0001wz-00; Tue, 25 Jan 2000 10:05:28 +0200 From: Sheldon Hearn To: Kevin Day Cc: obrien@FreeBSD.ORG, andyf@speednet.com.au (Andy Farkas), freebsd-current@FreeBSD.ORG Subject: Re: ascii art in hosts.allow In-reply-to: Your message of "Tue, 25 Jan 2000 01:46:01 CST." <200001250746.BAA67744@celery.dragondata.com> Date: Tue, 25 Jan 2000 10:05:28 +0200 Message-ID: <7496.948787528@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jan 2000 01:46:01 CST, Kevin Day wrote: > A more direct patch would have been: > > -# NOTE: The hosts.deny file is not longer used. Instead, put both 'allow' > +# NOTE: The hosts.deny file is no longer used. Instead, put both 'allow' I'm concerned about the authenticity of this comment. It looks to me like a comment on commonly accepted usage convention. It looks to me like hosts_access(3) still handles hosts.deny in the same way that it always has. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 0:40:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from enterprise.sanyusan.se (enterprise.sanyusan.se [212.209.55.83]) by hub.freebsd.org (Postfix) with ESMTP id BA4E914F23 for ; Tue, 25 Jan 2000 00:40:38 -0800 (PST) (envelope-from anders@enterprise.sanyusan.se) Received: (from anders@localhost) by enterprise.sanyusan.se (8.9.3/8.9.3) id JAA08620; Tue, 25 Jan 2000 09:40:11 +0100 (CET) (envelope-from anders) Date: Tue, 25 Jan 2000 09:40:11 +0100 From: Anders Andersson To: Soren Schmidt Cc: Motomichi Matsuzaki , current@FreeBSD.ORG Subject: Re: My ATAPI CD not come ready Message-ID: <20000125094011.A8591@enterprise.sanyusan.se> References: <86vh4jaz0w.wl@tkc.att.ne.jp> <200001250729.IAA64029@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200001250729.IAA64029@freebsd.dk>; from sos@freebsd.dk on Tis, Jan 25, 2000 at 08:29:32am +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have the same problem: [anders@enterprise:anders] $ dmesg | grep ata ata-pci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata-isa0: already registered as ata0 ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed -- Anders Andersson anders@sanyusan.se Sanyusan International AB http://www.sanyusan.se/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 0:48: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id EDFAF14E5A for ; Tue, 25 Jan 2000 00:48:05 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA82387; Tue, 25 Jan 2000 09:47:54 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001250847.JAA82387@freebsd.dk> Subject: Re: My ATAPI CD not come ready In-Reply-To: <20000125094011.A8591@enterprise.sanyusan.se> from Anders Andersson at "Jan 25, 2000 09:40:11 am" To: anders@sanyusan.se (Anders Andersson) Date: Tue, 25 Jan 2000 09:47:54 +0100 (CET) Cc: mzaki@e-mail.ne.jp (Motomichi Matsuzaki), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Anders Andersson wrote: > I have the same problem: > > [anders@enterprise:anders] $ dmesg | grep ata > ata-pci0: port 0xffa0-0xffaf at device 7.1 > on pci0 > ata0 at 0x01f0 irq 14 on ata-pci0 > ata-isa0: already registered as ata0 > ata0-slave: ata_command: timeout waiting for intr > ata0-slave: identify failed Could I please have a complete dmesg from that ?? -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 0:49: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 5BE0414E44; Tue, 25 Jan 2000 00:49:04 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4BE781CD5F5; Tue, 25 Jan 2000 00:49:04 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 25 Jan 2000 00:49:04 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Cc: security@freebsd.org Subject: OpenSSL docs for FAQ Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can people please review this for style and content, for inclusion in the FAQ? I'll also need someone to mark it up once it's ready since SGML is currently not among my abilities :-) Thanks, Kris ---- As of FreeBSD 4.0, the OpenSSL toolkit is a part of the base system. OpenSSL [http://www.openssl.org] provides a general-purpose cryptography library, as well as the Secure Sockets Layer v2/v3 (SSLv2/SSLv3) and Transport Layer Security v1 (TLSv1) network security protocols. However, some of the algorithms (specifically, RSA and IDEA) included in OpenSSL are protected by patents in the USA and elsewhere and are not available for unrestricted use. In addition, export of cryptographic code from the USA has (until recently) been heavily restricted. As a result, FreeBSD has available three different versions of OpenSSL depending on geographical location (US/non-US) and compliance with the RSAREF license (see below). RSA is a useful algorithm which is required for a lot of third-party software which uses OpenSSL (as well as for the SSLv2 protocol), so you should enable it if at all possible. See below for more information. SOURCE-CODE INSTALLATIONS INTERNATIONAL (NON-US) USERS: People who are located outside the USA, and who obtain their crypto sources from internat.freebsd.org (the International Crypto Repository), will build a version of OpenSSL which includes RSA, but does not include IDEA, because the latter is restricted in certain locations elsewhere in the world. In the future a more flexible identification system may allow building of IDEA in countries for which it is not restricted. US USERS: As noted above, RSA is patented in the US, with terms preventing general use without an appropriate license. Therefore the OpenSSL RSA code may not be used in the US, and has been removed from the version of OpenSSL carried on US mirror sites. The RSA patent is due to expire on September 20, 2000, at which time it is intended to add the "full" RSA code back to the US version of OpenSSL. However (and fortunately), the RSA patent holder (RSA Security, [http://www.rsasecurity.com]) has provided a "RSA reference implementation" toolkit ("RSAREF") which is available for *certain classes of use*, including "non-commercial use" (see the RSAREF license [XXX - We should put this on the website too since I can't find an external URL for it] for the definition of "non-commercial"). If you meet the conditions of the RSAREF license and wish to build your OpenSSL sources with RSAREF support, you must first install the rsaref port in /usr/ports/security/rsaref before (re)building OpenSSL (e.g. by 'make world'). Please obtain legal advice if you are unsure of your compliance with the license terms. IDEA code is also removed from the US version of OpenSSL for patent reasons. BINARY INSTALLATIONS If your FreeBSD installation was a binary installation (e.g. installed from CDROM, or from a snapshot downloaded from ftp.freebsd.org) and you selected to install the 'crypto' module, then you will have the non-RSA capable US version of the OpenSSL code (see above). If you wish to install another version (US RSAREF, or International) you will need to obtain and install one of the following packages: * OpenSSL package with RSAREF support for US users (NOTE: Be sure to read the license before installing! This is NOT licensed for general-purpose use!) ftp://ftp.freebsd.org/XXX * OpenSSL package for International (non-US) users. This is not legal for use in the US, but international users should use this one because the RSA implementation is faster and more flexible. ftp://internat.freebsd.org/XXX ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 1: 3:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id F114F14E44 for ; Tue, 25 Jan 2000 01:03:40 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 19973 invoked by uid 1001); 25 Jan 2000 09:03:40 -0000 Date: 25 Jan 2000 01:03:40 -0800 Date: Tue, 25 Jan 2000 01:03:40 -0800 From: Bill Swingle To: charon@freethought.org Cc: current@freebsd.org Subject: Re: connectivity problems with current.freebsd.org Message-ID: <20000125010340.A19603@dub.net> References: <4.2.2.20000124233054.00b81e00@nsit-popmail.uchicago.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <4.2.2.20000124233054.00b81e00@nsit-popmail.uchicago.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 24, 2000 at 11:43:59PM -0600, charon@freethought.org wrote: > By chance, playing around with the fact that current.freebsd.org is an > alias for usw2.freebsd.org, I found that usw3.freebsd.org (209.180.6.227) > mirrors snapshots as well. Perhaps something should be added to the > /snapshots readme.txt on ftp.freebsd.org about the fact that > current.freebsd.org has mirrors. That said, I've gotten the same error > from usw3 as from usw2. I can't really speak to your download problems but it should be noted that usw2 and usw3 are in the same facility at USWest, in fact they're probably in the very same rack as each other. Noting that this other 'mirror' is available would not do much good as they both sit on the exact same bandwidth. my .02. -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 1:15:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id D6B1515081 for ; Tue, 25 Jan 2000 01:15:04 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id AAA02844 for ; Tue, 25 Jan 2000 00:33:55 GMT (envelope-from n_hibma@webweaving.org) Date: Tue, 25 Jan 2000 00:33:55 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List Subject: pcm - stutters Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The output of my ESS 1869 stutters whenever there is no new data fed to it. For example pressing Ctrl-Z, or heavy disk usage (normally making mpg123 jump). The stuttering is repetition of one short fragment of about a quarter of a second, indefinitely Anything I can try with this machine current as of jan.24 02:00 GMT? Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 1:16:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 4EC9F14CFF for ; Tue, 25 Jan 2000 01:15:36 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id AAA03330; Tue, 25 Jan 2000 00:54:09 GMT (envelope-from n_hibma@webweaving.org) Date: Tue, 25 Jan 2000 00:54:09 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "Louis A. Mamakos" Cc: FreeBSD CURRENT Mailing List Subject: Re: cvs commit: src/sys/dev/usb ugen.c In-Reply-To: <200001241444.JAA81809@whizzo.transsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > One other lingering issue - I don't believe we install any of the USB > header files (in particular, /sys/dev/usb/usb.h) in /usr/include. While > I certainly have /usr/src populated on my box, we probably ought to not > require it. > > Should it be installed in /usr/include/dev/usb/*.h? Hm, you are messing with my priorities here. Well, yes, that is supposed to happen and I guess it should happen before 4.0 is released I guess. One problem is how to limit the number of header files copied there. Only usb.h, usbdi.h, usbdi_util.h and usbdevs.h should be copied there, and not the other 453 header files in src/sys/dev/usb. I presume I will have to add a special case to src/include/Makefile , right? Also, should the header files be in /usr/include/dev/usb or /usr/include/usb (requires some redesign of the Makefile in src/include) Cheers, Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 1:18:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id CA94E150C6 for ; Tue, 25 Jan 2000 01:18:14 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 12D273-000PbB-0V; Tue, 25 Jan 2000 09:18:13 +0000 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA91303; Tue, 25 Jan 2000 09:20:22 GMT (envelope-from dfr@nlsystems.com) Date: Tue, 25 Jan 2000 09:17:05 +0000 (GMT) From: Doug Rabson To: Warner Losh Cc: Nick Hibma , FreeBSD CURRENT Mailing List Subject: Re: APM still ignoring DEVICE_SUSPEND errors In-Reply-To: <200001241836.LAA04877@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Warner Losh wrote: > In message Nick Hibma writes: > : The following patch fixes two things: First, DEVICE_SUSPEND errors are > : no longer ignored. Since we have defaults for methods we should no > : longer ignore these errors. Also, DEVICE_RESUME wasn't done when the > : apm_suspend_system event failed. > > I had similar patches that workede several months ago, but they have > since been lost. > > : Second, in the ordering of DEVICE_* and apm_hook_* is not symmetric for > : suspend and resume. The patch reverses the resume case as well to be > : > : apm_hook_resume(...) > : DEVICE_RESUME(root) > : > : Send me some feedback on this. I've mailed the people mentioned in the > : head of the file, but so far got no response. I would like to make sure > : we get this right when USB devices are used. Some of them don't suspend > : and the suspend should be refused in that case. > > Any reason to not shoot the apm_hook_{suspend,resume} in the head and > just use newbus suspend/resume everywhere? Are there any non-newbus devices which need suspend/resume? I think the i386 clock uses the apm hooks but I might be misremembering. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 1:42: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from extremis.demon.co.uk (extremis.demon.co.uk [194.222.242.30]) by hub.freebsd.org (Postfix) with SMTP id 79B7914E9E for ; Tue, 25 Jan 2000 01:41:58 -0800 (PST) (envelope-from gjvc@extremis.demon.co.uk) Received: (qmail 255 invoked by uid 1010); 25 Jan 2000 00:56:44 -0000 Date: Tue, 25 Jan 2000 00:56:44 +0000 From: George Cox To: Alexander Langer Cc: David O'Brien , ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0-release (ports) schedule Message-ID: <20000125005644.A221@extremis.demon.co.uk> References: <200001241436.GAA23651@silvia.hip.berkeley.edu> <20000124103710.B75151@dragon.nuxi.com> <20000124205021.B24975@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <20000124205021.B24975@cichlids.cichlids.com>; from alex@big.endian.de on Mon, Jan 24, 2000 at 08:50:21PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT (i386) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 24/01 20:50, Alexander Langer wrote: > Just FYI, maybe you can do something against this strict handling. > Or not, I don't know. Somehow, it's very good that the compiler does > this... Ports with such sloppy code should be patched as part of the port process, or better, have the original authors ass WHUPPED and have them be taught the virtues of using the compiler flags '-Wall -Wa-few-other-things-documented-in-the-man-page' on _every_ _source_ _file_ _they_ _compile_. End rant. gjvc -- [gjvc] In god we're trussed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 1:43:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from wyvern.cc.kogakuin.ac.jp (wyvern.cc.kogakuin.ac.jp [133.80.184.10]) by hub.freebsd.org (Postfix) with ESMTP id 9EF5614EEA; Tue, 25 Jan 2000 01:43:52 -0800 (PST) (envelope-from nyan@wyvern.cc.kogakuin.ac.jp) Received: from localhost (localhost [127.0.0.1]) by wyvern.cc.kogakuin.ac.jp (8.9.3+3.2W/3.7W) with ESMTP id SAA54301; Tue, 25 Jan 2000 18:43:51 +0900 (JST) To: luoqi@watermarkgroup.com Cc: kato@ganko.eps.nagoya-u.ac.jp, FreeBSD-current@FreeBSD.ORG, FreeBSD-hackers@FreeBSD.ORG, FreeBSD98-hackers@jp.freebsd.org, nyan@jp.freebsd.org Subject: Re: indirection in bus space In-Reply-To: <200001250601.BAA17157@lor.watermarkgroup.com> References: <200001250601.BAA17157@lor.watermarkgroup.com> From: Takahashi Yoshihiro X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000125184350C.nyan@wyvern.cc.kogakuin.ac.jp> Date: Tue, 25 Jan 2000 18:43:50 +0900 (JST) X-Dispatcher: imput version 990905(IM130) Lines: 48 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001250601.BAA17157@lor.watermarkgroup.com> Luoqi Chen writes: > > I think it is difficult to implement such conversion because: > > > > - Not only bus space stuff also resource manager stuff need to > > perform such conversion. > > Why? Both bus_space_handle_t and bus_space_tag_t are supposed to be > opaque types. Resource manager needs not know the implementation details. In isa_alloc_resourcev() and isa_load_resourcev() (both new functions), it needs to store allocated resources and I/O table in bus_space_handle_pc98. > We could create a new resource type SYS_RES_IOPORT_ARRAY, and intercept > it in all isa_*_resoruce() methods. In isa_alloc_resource(), we malloc and > return a fake resource record, in which we store I386_BUS_PIO_IND as > bus tag and address of bus_space_handle_pc98 as bus handle. And in > isa_release_resource(), we first release the underlying resources stored > in the bus_space_handle_pc98 record and then free the fake resource record > itself. It should be safe as long as we don't manipulate this resource by > direct resource manager calls, which we shouldn't do anyway. > (or we should implement it at the root bus level, if pci devices in > pc98 systems also use discrete port addresses). We can't call bus_alloc_resource() directly from device drivers. Because bus_alloc_resource() is defined as the following, it can't deliver I/O table. struct resource * bus_alloc_resource(device_t dev, int type, int *rid, u_long start, u_long end, u_long count, u_int flags); If it conversion from 'bus_addr_t *' to 'u_long' and deliver to the fourth argument, we can use bus_alloc_resource(). But, it needs to perform conversions in each drivers using indirect resources. Then, only isa_alloc_resourcev() is not enough to support NS8390 based network cards and PnP devices which require to use I386_BUS_PIO_IND. So, I separate into isa_alloc_resourcev() to allocate resources and isa_load_resourcev() to store I/O table. IMHO, as IBM PC/AT and NEC PC-98 is different architecture, the bus space stuff should be implemented to different files. --- Takahashi Yoshihiro / nyan@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 1:49:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 56763150D3 for ; Tue, 25 Jan 2000 01:49:27 -0800 (PST) (envelope-from ian@niw.com.au) Received: by rose.niw.com.au (Postfix, from userid 1000) id B3D1562E59; Tue, 25 Jan 2000 20:18:37 +1030 (CST) Date: Tue, 25 Jan 2000 20:18:37 +1030 From: Ian West To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: My ATAPI CD not come ready Message-ID: <20000125201837.A534@rose.niw.com.au> References: <86vh4jaz0w.wl@tkc.att.ne.jp> <200001250729.IAA64029@freebsd.dk> <20000125094011.A8591@enterprise.sanyusan.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000125094011.A8591@enterprise.sanyusan.se>; from anders@sanyusan.se on Tue, Jan 25, 2000 at 09:40:11AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 25, 2000 at 09:40:11AM +0100, Anders Andersson wrote: > I have the same problem: > > [anders@enterprise:anders] $ dmesg | grep ata > ata-pci0: port 0xffa0-0xffaf at device 7.1 > on pci0 > ata0 at 0x01f0 irq 14 on ata-pci0 > ata-isa0: already registered as ata0 > ata0-slave: ata_command: timeout waiting for intr > ata0-slave: identify failed > > > -- > Anders Andersson anders@sanyusan.se > Sanyusan International AB http://www.sanyusan.se/ > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message With current cvsupped an hour ago, I am seeing this. With current about a month old things are perfect. (and have been for many months on ata driver) Hardware is SMP (2*PIII-450) BX chipset motherboard, second bus has IDE hard disk as primary and atapi CD as secondary.I have never prior to this seen a failure to probe. The primary drive runs fine. I get exactly the same error message on the recent kernel. Normal (correct boot messages) Jan 25 20:08:13 rose /kernel: Copyright (c) 1992-1999 The FreeBSD Project. Jan 25 20:08:13 rose /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Jan 25 20:08:13 rose /kernel: The Regents of the University of California. All rights reserved. Jan 25 20:08:13 rose /kernel: FreeBSD 4.0-CURRENT #1: Tue Dec 28 17:21:58 CST 1999 Jan 25 20:08:13 rose /kernel: ian@rose.niw.com.au:/usr/src/sys/compile/ROSE Jan 25 20:08:13 rose /kernel: Timecounter "i8254" frequency 1193182 Hz Jan 25 20:08:13 rose /kernel: CPU: Pentium III/Xeon (451.02-MHz 686-class CPU) Jan 25 20:08:13 rose /kernel: Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Jan 25 20:08:13 rose /kernel: Features=0x387fbff Jan 25 20:08:13 rose /kernel: real memory = 268423168 (262132K bytes) Jan 25 20:08:13 rose /kernel: avail memory = 256626688 (250612K bytes) Jan 25 20:08:13 rose /kernel: Programming 24 pins in IOAPIC #0 Jan 25 20:08:13 rose /kernel: FreeBSD/SMP: Multiprocessor motherboard Jan 25 20:08:13 rose /kernel: cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 Jan 25 20:08:13 rose /kernel: cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 Jan 25 20:08:13 rose /kernel: io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Jan 25 20:08:13 rose /kernel: Preloaded elf kernel "kernel" at 0xc03a0000. Jan 25 20:08:13 rose /kernel: Pentium Pro MTRR support enabled Jan 25 20:08:13 rose /kernel: md0: Malloc disk Jan 25 20:08:13 rose /kernel: npx0: on motherboard Jan 25 20:08:13 rose /kernel: npx0: INT 16 interface Jan 25 20:08:13 rose /kernel: pcib0: on motherboard Jan 25 20:08:13 rose /kernel: pci0: on pcib0 Jan 25 20:08:13 rose /kernel: pcib1: at device 1.0 on pci0 Jan 25 20:08:13 rose /kernel: pci1: on pcib1 Jan 25 20:08:13 rose /kernel: vga-pci0: irq 16 at device 0.0 on pci1 Jan 25 20:08:13 rose /kernel: isab0: at device 4.0 on pci0 Jan 25 20:08:13 rose /kernel: isa0: on isab0 Jan 25 20:08:13 rose /kernel: ata-pci0: at device 4.1 on pci0 Jan 25 20:08:13 rose /kernel: ata-pci0: Busmastering DMA supported Jan 25 20:08:13 rose /kernel: ata0 at 0x01f0 irq 14 on ata-pci0 Jan 25 20:08:13 rose /kernel: ata1 at 0x0170 irq 15 on ata-pci0 Jan 25 20:08:13 rose /kernel: pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 4.2 Jan 25 20:08:13 rose /kernel: Timecounter "PIIX" frequency 3579545 Hz Jan 25 20:08:13 rose /kernel: intpm0: at device 4.3 on pci0 Jan 25 20:08:13 rose /kernel: intpm0: I/O mapped e800 Jan 25 20:08:13 rose /kernel: intpm0: intr IRQ 9 enabled revision 0 Jan 25 20:08:13 rose /kernel: smbus0: on intsmb0 Jan 25 20:08:13 rose /kernel: smb0: on smbus0 Jan 25 20:08:13 rose /kernel: intpm0: PM I/O mapped e400 Jan 25 20:08:13 rose /kernel: bktr0: irq 19 at device 9.0 on pci0 Jan 25 20:08:13 rose /kernel: iicbb0: on bti2c0 Jan 25 20:08:13 rose /kernel: iicbus0: on iicbb0 master-only Jan 25 20:08:13 rose /kernel: smbus1: on bti2c0 Jan 25 20:08:13 rose /kernel: smb1: on smbus1 Jan 25 20:08:13 rose /kernel: bktr0: Hauppauge Model 60104 C VM Jan 25 20:08:13 rose /kernel: bktr0: Detected a MSP3400C-C6 at 0x80 Jan 25 20:08:13 rose /kernel: Hauppauge WinCast/TV, Philips PAL I tuner, msp3400c stereo. Jan 25 20:08:13 rose /kernel: fxp0: irq 16 at device 10.0 on pci0 Jan 25 20:08:13 rose /kernel: fxp0: Ethernet address 00:90:27:3c:03:4d Jan 25 20:08:13 rose /kernel: fxp0: supplying EUI64: 00:90:27:ff:fe:3c:03:4d Jan 25 20:08:13 rose /kernel: vr0: irq 17 at device 11.0 on pci0 Jan 25 20:08:13 rose /kernel: vr0: Ethernet address: 00:80:c8:4b:98:ae Jan 25 20:08:13 rose /kernel: miibus0: on vr0 Jan 25 20:08:13 rose /kernel: amphy0: on miibus0 Jan 25 20:08:13 rose /kernel: amphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto Jan 25 20:08:13 rose /kernel: ahc0: irq 16 at device 12.0 on pci0 Jan 25 20:08:13 rose /kernel: ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs Jan 25 20:08:13 rose /kernel: fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 Jan 25 20:08:13 rose /kernel: fdc0: FIFO enabled, 8 bytes threshold Jan 25 20:08:13 rose /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 Jan 25 20:08:13 rose /kernel: atkbdc0: at port 0x60-0x6f on isa0 Jan 25 20:08:13 rose /kernel: atkbd0: irq 1 on atkbdc0 Jan 25 20:08:13 rose /kernel: psm0: irq 12 on atkbdc0 Jan 25 20:08:13 rose /kernel: psm0: model Generic PS/2 mouse, device ID 0 Jan 25 20:08:13 rose /kernel: vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 Jan 25 20:08:13 rose /kernel: sc0: on isa0 Jan 25 20:08:13 rose /kernel: sc0: VGA <16 virtual consoles, flags=0x200> Jan 25 20:08:13 rose /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 Jan 25 20:08:13 rose /kernel: sio0: type 16550A Jan 25 20:08:13 rose /kernel: sio1 at port 0x2f8-0x2ff irq 3 on isa0 Jan 25 20:08:13 rose /kernel: sio1: type 16550A Jan 25 20:08:13 rose /kernel: sio2: not probed (disabled) Jan 25 20:08:13 rose /kernel: sio3: not probed (disabled) Jan 25 20:08:13 rose /kernel: ppc0 at port 0x378-0x37f irq 7 on isa0 Jan 25 20:08:13 rose /kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Jan 25 20:08:13 rose /kernel: ppb0: IEEE1284 device found /NIBBLE/ECP Jan 25 20:08:13 rose /kernel: Probing for PnP devices on ppbus0: Jan 25 20:08:13 rose /kernel: ppbus0: PRINTER PCL,MLC,PML,PJL Jan 25 20:08:13 rose /kernel: plip0: on ppbus 0 Jan 25 20:08:13 rose /kernel: lpt0: on ppbus 0 Jan 25 20:08:13 rose /kernel: lpt0: Interrupt-driven port Jan 25 20:08:13 rose /kernel: ppi0: on ppbus 0 Jan 25 20:08:13 rose /kernel: sbc0: at port 0x220-0x22f,0x330-0x331,0x388-0x38b irq 5 drq 1,5 on isa0 Jan 25 20:08:13 rose /kernel: sbc0: setting card to irq 5, drq 1, 5 Jan 25 20:08:13 rose /kernel: pcm0: on sbc0 Jan 25 20:08:13 rose /kernel: unknown0: at port 0x168-0x16f,0x36e-0x36f irq 10 on isa0 Jan 25 20:08:13 rose /kernel: unknown1: at port 0x100 on isa0 Jan 25 20:08:13 rose /kernel: unknown2: at port 0x200-0x207 on isa0 Jan 25 20:08:13 rose /kernel: APIC_IO: Testing 8254 interrupt delivery Jan 25 20:08:13 rose /kernel: APIC_IO: routing 8254 via pin 2 Jan 25 20:08:13 rose /kernel: IP packet filtering initialized, divert enabled, rule-based forwarding enabled, unlimited logging Jan 25 20:08:13 rose /kernel: SMP: AP CPU #1 Launched! Jan 25 20:08:13 rose /kernel: ad0: ATA-4 disk at ata0 as master Jan 25 20:08:13 rose /kernel: ad0: 27199MB (55704096 sectors), 55262 cyls, 16 heads, 63 S/T, 512 B/S Jan 25 20:08:13 rose /kernel: ad0: 16 secs/int, 1 depth queue, UDMA33 Jan 25 20:08:13 rose /kernel: ad2: ATA-3 disk at ata1 as master Jan 25 20:08:13 rose /kernel: ad2: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S Jan 25 20:08:13 rose /kernel: ad2: 16 secs/int, 1 depth queue, UDMA33 Jan 25 20:08:13 rose /kernel: acd0: CDROM drive at ata1 as slave Jan 25 20:08:13 rose /kernel: acd0: read 4125KB/s (4125KB/s), 128KB buffer, PIO Jan 25 20:08:13 rose /kernel: acd0: Reads: CD-R, CD-RW, CD-DA stream Jan 25 20:08:13 rose /kernel: acd0: Audio: play, 256 volume levels Jan 25 20:08:13 rose /kernel: acd0: Mechanism: ejectable tray Jan 25 20:08:13 rose /kernel: acd0: Medium: no/blank disc inside, unlocked Jan 25 20:08:13 rose /kernel: Waiting 15 seconds for SCSI devices to settle Jan 25 20:08:13 rose /kernel: Mounting root from ufs:/dev/ad0s1a Jan 25 20:08:13 rose /kernel: cd0 at ahc0 bus 0 target 2 lun 0 Jan 25 20:08:13 rose /kernel: cd0: Removable CD-ROM SCSI-2 device Jan 25 20:08:13 rose /kernel: cd0: 3.300MB/s transfers Jan 25 20:08:13 rose /kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 2:20:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 1BE671516F for ; Tue, 25 Jan 2000 02:20:27 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id MAA66774; Tue, 25 Jan 2000 12:08:05 +0200 (EET) (envelope-from ru) Date: Tue, 25 Jan 2000 12:08:05 +0200 From: Ruslan Ermilov To: "Danny J. Zerkel" Cc: FreeBSD Current Subject: Re: 4.0 CODE FREEZE vs PR patches Message-ID: <20000125120805.A65704@relay.ucb.crimea.ua> Mail-Followup-To: "Danny J. Zerkel" , FreeBSD Current References: <388D1E86.45CFA01@columbus.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <388D1E86.45CFA01@columbus.rr.com>; from Danny J. Zerkel on Mon, Jan 24, 2000 at 10:54:46PM -0500 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 24, 2000 at 10:54:46PM -0500, Danny J. Zerkel wrote: > While I don't have much time to hack, I have tried to spend a little > time > going through the open PRs. When I find something I can reproduce, > I try > to fix it. How can I get the patches I have submitted into 4.0? Some > of > the problems were not very "obvious" patches, but all of them have been > very short (unsually 1 or 2 lines), so I would guess that reviewing > would > not be quite as easy. How can I help? Who should I bug? > > The PRs in question: > 4420 > 9350 > 12137 > 12242 > 12806 > Please send your patches to committers@FreeBSD.org. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 2:44: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.ddg.com (eunuch.ddg.com [216.30.58.66]) by hub.freebsd.org (Postfix) with ESMTP id DB61214C81; Tue, 25 Jan 2000 02:44:00 -0800 (PST) (envelope-from rkw@dataplex.net) Received: from nomad (128.83.46.85) by mail.ddg.com with SMTP (Eudora Internet Mail Server 2.1); Tue, 25 Jan 2000 04:43:51 -0600 From: Richard Wackerbarth To: "Rodney W. Grimes" Subject: Re: Please help spread the CVSup mirror load more evenly Date: Tue, 25 Jan 2000 04:29:54 -0600 X-Mailer: KMail [version 1.0.28] Content-Type: Multipart/Mixed; boundary="Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD" Cc: hasty@rah.star-gate.com (Amancio Hasty), obrien@FreeBSD.ORG, jdp@polstra.com (John Polstra), current@FreeBSD.ORG References: <200001241838.KAA68737@gndrsh.dnsmgr.net> In-Reply-To: <200001241838.KAA68737@gndrsh.dnsmgr.net> MIME-Version: 1.0 Message-Id: <00012504433301.00830@nomad> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD Content-Type: text/plain Content-Transfer-Encoding: 8bit On Mon, 24 Jan 2000, Rodney W. Grimes wrote: > This does not need to really be a wrapper around cvs, folks should run > a tool 1 time to pick the best guess as to what server they should be > using, stick that value in thier cvsup file and be done with it. If > jdp calls for a ``this server is being overloaded please move'' folks > should rerun the selection tool and pick new servers. This latter > event happens 2 or 3 times a year, it is a waste to run this every time > you start up cvsup and can cause the grief if you change cvsup servers > in <1 hour due to the update policy of the mirrors. I agree that you need to do it with a "run once (in a blue moon?)" script that helps you select an appropriate host site. But for now, we can leave that to "manually select a good site" Here is a patch that I suggested to John the last time this came up. Rather than patching the supfiles, I "patch" my local `make` configuration. Just having this in the code might help steer users to a different site. If we can get most users off of "cvsup.FreeBSD.ORG", we could change that DNS CNAME to point the underutilized site of the week. --Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD Content-Type: text/plain; name="wacky.patch" Content-Transfer-Encoding: 8bit Content-Description: CVSUP Preferred Site Content-Disposition: attachment; filename="diffs" --- src/Makefile.inc1~ Tue Jan 25 04:12:36 2000 +++ src/Makefile.inc1 Tue Jan 25 04:21:00 2000 @@ -407,17 +407,20 @@ @echo "--------------------------------------------------------------" @echo ">>> Running ${SUP}" @echo "--------------------------------------------------------------" +.if defined(FreeBSD_SUPSITE) +SITEFLAGS= -h ${FreeBSD_SUPSITE} +.endif .if defined(SUPFILE) - @${SUP} ${SUPFLAGS} ${SUPFILE} + @${SUP} ${SUPFLAGS} ${SITEFLAGS} ${SUPFILE} .endif .if defined(SUPFILE1) - @${SUP} ${SUPFLAGS} ${SUPFILE1} + @${SUP} ${SUPFLAGS} ${SITEFLAGS} ${SUPFILE1} .endif .if defined(SUPFILE2) - @${SUP} ${SUPFLAGS} ${SUPFILE2} + @${SUP} ${SUPFLAGS} ${SITEFLAGS} ${SUPFILE2} .endif .if defined(PORTSSUPFILE) - @${SUP} ${SUPFLAGS} ${PORTSSUPFILE} + @${SUP} ${SUPFLAGS} ${SITEFLAGS} ${PORTSSUPFILE} .endif .endif .if defined(CVS_UPDATE) --- src/etc/defaults/make.conf~ Tue Jan 25 04:14:36 2000 +++ src/etc/defaults/make.conf Tue Jan 25 04:16:42 2000 @@ -197,6 +197,7 @@ # #SUP= /usr/local/bin/cvsup #SUPFLAGS= -g -L 2 +#FreeBSD_SUPSITE= cvsup8.FreeBSD.ORG #SUPFILE= /usr/share/examples/cvsup/standard-supfile #SUPFILE1= /usr/share/examples/cvsup/secure-supfile #PORTSSUPFILE= /usr/share/examples/cvsup/ports-supfile --Boundary-=_nWlrBbmQBhCDarzOwKkYHIDdqSCD-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 3:47:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (pC19F5449.dip0.t-ipconnect.de [193.159.84.73]) by hub.freebsd.org (Postfix) with ESMTP id 5632014FA7; Tue, 25 Jan 2000 03:47:21 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 9A9F3AB95; Tue, 25 Jan 2000 12:48:05 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id MAA05419; Tue, 25 Jan 2000 12:47:37 +0100 (CET) (envelope-from alex) Date: Tue, 25 Jan 2000 12:47:37 +0100 From: Alexander Langer To: Michael VanLoon Cc: "David O'Brien" , ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0-release (ports) schedule Message-ID: <20000125124737.A3842@cichlids.cichlids.com> Mail-Followup-To: Michael VanLoon , David O'Brien , ports@FreeBSD.ORG, current@FreeBSD.ORG References: <8070C3A4E99ED211A63200105A19B99B3174DA@mail.edifecs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <8070C3A4E99ED211A63200105A19B99B3174DA@mail.edifecs.com>; from MichaelV@EDIFECS.COM on Mon, Jan 24, 2000 at 12:11:09PM -0800 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Michael VanLoon (MichaelV@EDIFECS.COM): > What would you do about it? The C++ standard says that's an error. So, > it's an error. It's not "too strict" -- it's exactly the right amount of > strictness to conform to the standard. Yes. That's what I meant with "Somehow, it's very good ...". BUT: Other compilers don't treat this as an error, that's why many ports fail. Ok, so far it's just the porter's thing to make stuff compile. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 3:48:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id ECEF514EFA; Tue, 25 Jan 2000 03:48:38 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id LAA92194; Tue, 25 Jan 2000 11:48:31 GMT (envelope-from joe) Date: Tue, 25 Jan 2000 11:48:30 +0000 From: Josef Karthauser To: Garance A Drosihn Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: 4.0 CODE FREEZE vs patches to lpr/lpc Message-ID: <20000125114830.E56451@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If it's easy I'll look at it. (I made a commit to lpr myself last week anyway.) Joe On Mon, Jan 24, 2000 at 05:08:56PM -0500, Garance A Drosihn wrote: > >On Mon, 24 Jan 2000, Jordan K. Hubbard wrote: > > > > > On the 29th of January, I'll be freezing the -current branch (well, > > > OK, the trunk). That means NO commits without my review first ... > > Could someone commit the 2-line bug fix in bin/15728 before yet > another system release goes out the door? > > Jan 7th, 1999: problem first reported in bin/9362 > Sep 9th, 1999: fix first described (with patch) in bin/13549 > Nov 18th, 1999: fix acknowledged by another person in bin/14975, > although the update there is "backwards" (it would > turn a FIXED source code to become the UNFIXED one, > because it's a 'diff cmds cmds.orig'). > Dec 27th, 1999: slightly prettier version of the Sept 9th patch is > sent in and becomes bin/15728. > > There some other lpr/lpd PR's which look like they should go in, > and I have more lpr/lpd patches to write up sometime, but I figure > if I can't get this damn 2-line fix committed then there isn't > much point pursuing any other printing improvements. It's a > trivial fix to an obvious and 100% reproducible bug, and yet it > just sits there. Note this is not the somewhat more controversial > change (to 'lpr -r') that I was pursuing earlier this month, as it > might be a bit too close to the code freeze to put that one in. > > Given that lpr/lpd seems to be very low priority in most committers > queues, is there any way to expedite changes like these? I'm > trying avoid any ranting or raving, but this has been pretty > exasperating. > > > --- > Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu > Senior Systems Programmer or drosih@rpi.edu > Rensselaer Polytechnic Institute -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 3:49:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id B703D151BD; Tue, 25 Jan 2000 03:49:26 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id LAA92467; Tue, 25 Jan 2000 11:49:15 GMT (envelope-from joe) Date: Tue, 25 Jan 2000 11:49:11 +0000 From: Josef Karthauser To: Matthew Dillon Cc: Garance A Drosihn , "Jordan K. Hubbard" , current@FreeBSD.org, committers@FreeBSD.org Subject: Re: 4.0 CODE FREEZE vs patches to lpr/lpc Message-ID: <20000125114911.F56451@florence.pavilion.net> References: <200001242333.PAA93308@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001242333.PAA93308@apollo.backplane.com> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 24, 2000 at 03:33:06PM -0800, Matthew Dillon wrote: > > :Could someone commit the 2-line bug fix in bin/15728 before yet > :another system release goes out the door? > > Done! Ahha, saves me doing it :) Tnx, Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 4: 0:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by hub.freebsd.org (Postfix) with ESMTP id 36E10155CE for ; Tue, 25 Jan 2000 04:00:16 -0800 (PST) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn9.imasy.or.jp [202.227.24.201]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id VAA24572; Tue, 25 Jan 2000 21:00:09 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <200001251200.VAA24572@tasogare.imasy.or.jp> To: dfr@nlsystems.com Cc: imp@village.org, n_hibma@webweaving.org, current@freebsd.org Subject: Re: APM still ignoring DEVICE_SUSPEND errors In-Reply-To: Your message of "Tue, 25 Jan 2000 09:17:05 +0000 (GMT)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 25 Jan 2000 21:00:07 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 24 Jan 2000, Warner Losh wrote: > > > In message Nick Hibma writes: > > : The following patch fixes two things: First, DEVICE_SUSPEND errors are > > : no longer ignored. Since we have defaults for methods we should no > > : longer ignore these errors. Also, DEVICE_RESUME wasn't done when the > > : apm_suspend_system event failed. > > > > I had similar patches that workede several months ago, but they have > > since been lost. > > > > : Second, in the ordering of DEVICE_* and apm_hook_* is not symmetric for > > : suspend and resume. The patch reverses the resume case as well to be > > : > > : apm_hook_resume(...) > > : DEVICE_RESUME(root) > > : > > : Send me some feedback on this. I've mailed the people mentioned in the > > : head of the file, but so far got no response. I would like to make sure > > : we get this right when USB devices are used. Some of them don't suspend > > : and the suspend should be refused in that case. > > > > Any reason to not shoot the apm_hook_{suspend,resume} in the head and > > just use newbus suspend/resume everywhere? > > Are there any non-newbus devices which need suspend/resume? I think the > i386 clock uses the apm hooks but I might be misremembering. No, it just reloads the countdown register of i8254 in apm_default_resume() for now. But once the PIT become an ordinary device like any other, this is planned to be the device's resume method. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 4:28: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (pC19F5485.dip0.t-ipconnect.de [193.159.84.133]) by hub.freebsd.org (Postfix) with ESMTP id 684F414FA7; Tue, 25 Jan 2000 04:27:59 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 11AC8AB95; Tue, 25 Jan 2000 13:28:47 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id NAA07972; Tue, 25 Jan 2000 13:28:19 +0100 (CET) (envelope-from alex) Date: Tue, 25 Jan 2000 13:28:19 +0100 From: Alexander Langer To: obrien@FreeBSD.ORG Cc: ports@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: 4.0-release (ports) schedule Message-ID: <20000125132819.B7575@cichlids.cichlids.com> Mail-Followup-To: obrien@FreeBSD.ORG, ports@FreeBSD.ORG, current@FreeBSD.ORG References: <200001241436.GAA23651@silvia.hip.berkeley.edu> <20000124103710.B75151@dragon.nuxi.com> <20000124205021.B24975@cichlids.cichlids.com> <20000124120117.N81215@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000124120117.N81215@dragon.nuxi.com>; from obrien@NUXI.com on Mon, Jan 24, 2000 at 12:01:17PM -0800 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake David O'Brien (obrien@NUXI.com): > > I noticed that many ports are broken because the compiler handles > > ANSI-C++ violations too strict. > Not too strict -- to the ratified ISO-C++ specification. Yes. Ok :-) > Nope. Those programs that aren't buildable aren't C++. I will not break > the C++ compiler to support them. Ok, I understand this. Probably I wouldn't do this, too. Though: Often a simple change from char *stuff; [..] stuff = mmap()... (fails) to stuff = (char *) mmap()... (works) does the trick. Enough on this topic. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 4:30:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from pluton.ispras.ru (pluton.ispras.ru [194.186.94.6]) by hub.freebsd.org (Postfix) with ESMTP id 555DA14FEC for ; Tue, 25 Jan 2000 04:30:09 -0800 (PST) (envelope-from grn@ispras.ru) Received: from gate.ispras.ru (gate [194.67.37.200]) by pluton.ispras.ru (8.9.3/8.9.3) with ESMTP id PAA19678 for ; Tue, 25 Jan 2000 15:27:23 +0300 (MSK) Received: from ispgate (ispgate [194.67.37.200]) by gate.ispras.ru (8.9.3/8.9.3) with ESMTP id PAA29903 for ; Tue, 25 Jan 2000 15:27:13 +0300 (MSK) Date: Tue, 25 Jan 2000 15:27:13 +0300 (MSK) From: Grigory Kljuchnikov To: current@freebsd.org Subject: How can I use current release of FreeBSD? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I'd like to use current release of 4.0 FreeBSD, because I have two PC with Ultra DMA 66 disks . I got the 4.0-20000110 directoty tree from ftp://current.freebsd.org and install this release to the first host. It work properly. But I don't install it to second one because kernel doesn't see Ultra DMA 66 disks on that machine. I went to the ftp://current.freebsd.org and got new floppy images from 4.0-20000124 release and they boot my machine properly and see all Ultra DMA 66 disks. How can I update 4.0-20000110 directoty tree to 4.0-20000124? And how do these updates do properly? Where can I see more about this? More thanks. Grigory Kljuchnikov ------------------------------------------------------------ Institute for System Programming Russian Academy of Sciences, 109004, Moscow, Russia, B.Kommunistitcheskay, 25, phone(work): +7-095-9125659 fax: +7-095-9121524 e-mail: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 4:53:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 3FB67151D5 for ; Tue, 25 Jan 2000 04:53:37 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 1460 invoked from network); 25 Jan 2000 12:53:25 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 25 Jan 2000 12:53:25 -0000 Date: Tue, 25 Jan 2000 23:53:23 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Yevmenkin, Maksim N, CSCIO" Cc: "'freebsd-current@freebsd.org'" , "'freebsd-hackers@freebsd.org'" Subject: Re: BPF bug or not? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Yevmenkin, Maksim N, CSCIO wrote: > All, > > I've just found that read from /dev/bpfX never return EAGAIN/EWOULDBLOCK. > It means that when you do a non blocking read and there is no data you will > always get 0. > > Does it suppose work this way? I think it is a bug. Perhaps applications depend on it. Untested fix: diff -c2 bpf.c~ bpf.c *** bpf.c~ Sun Jan 16 15:50:59 2000 --- bpf.c Tue Jan 25 23:44:32 2000 *************** *** 502,506 **** if (d->bd_slen == 0) { splx(s); ! return (0); } ROTATE_BUFFERS(d); --- 504,508 ---- if (d->bd_slen == 0) { splx(s); ! return (EWOULDBLOCK); } ROTATE_BUFFERS(d); Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 5:31: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from fLuFFy.iNt.tElE.dK (fw1.inet.tele.dk [193.163.158.4]) by hub.freebsd.org (Postfix) with ESMTP id 004EA14C2A for ; Tue, 25 Jan 2000 05:30:57 -0800 (PST) (envelope-from kvindeservice@FLUFFY.GETS.AN.ANALPROBE.DK) Received: from localhost (kvindeservice@localhost) by fLuFFy.iNt.tElE.dK (8.9.3/8.9.3) with SMTP id OAA53956; Tue, 25 Jan 2000 14:30:52 +0100 (CET) (envelope-from kvindeservice@FLUFFY.GETS.AN.ANALPROBE.DK) X-Authentication-Warning: fLuFFy.iNt.tElE.dK: kvindeservice owned process doing -bs Date: Tue, 25 Jan 2000 14:30:52 +0100 (CET) From: Millionaires in Underwear!!!! X-Sender: kvindeservice@fLuFFy.iNt.tElE.dK Reply-To: hackerboy@netscum.dk To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: big files, blocking in inode, kern.update, and so on... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ooops, brane fart, I meant to send this to -stable, for some reason I've been thinking that -current is production code, that's what I get for being away so long and forgetting everything On Tue, 25 Jan 19100, Matthew Dillon wrote: > Hmm. It sounds like the system is doing a huge amount of seeking to > flush the dirty buffers. Your history file may be badly fragmented on > the disk. The first thing I would do is take the system down and copy > the history file to reorder all of its block. i.e. 'cp fubar fubar.bak' > then 'mv fubar.bak fubar'. Assuming you have the space. I don't think that's the problem, for the way I set up both new machines (FreeBSD and Slowaris) in order to get the benefit of the existing huge history file, was to wget the ~1GB text file off the existing machine, then makehistory to build the index/ hash files. Nothing special was done to newfs this particular disk -- I used the standard defaults here. Then I pumped the feed into it (starting with a backlog so that it could refuse several hundred message IDs per second, and then actually get articles at ten or so times normal flow), and watched the results. And after I run `expire' so that the index/hash files are rebuilt, I'm also starting with freshly-built files. So while the amount of seeking being done is probably quite high, I don't think it's due to fragmentation. If anything, I'd guess it's within the hash/index files themselves, but I haven't actually looked closely there. > You may be able to force the system to write more smoothly by reducing > the vfs.hidirtybuffers water mark. I'll look at this, thanks... > There are other possible solutions if you can track down the piece of > code causing the most trouble. I believe that newer versions of INN > use shared R+W mmap()'s which can cause fragmented dirty pages. The > syncer will push these pages out every 30 seconds or so. If this is what > is causing the problem you can solve it under -CURRENT by adding MAP_NOSYNC > to the mmap() call in question (though I don't know which one it is, I > haven't used INN recently). I'll also look at trying -CURRENT (I've allowed myself the possibility of several OSen on the r00t disk just in case the -STABLE that I started with might have problems, as it does), as well as OSen from the Enemy Camp to see how they handle this, once I can free this machine from its present position in production. I'm also curious as to what other people who are running a news swerver, INN 2.x or otherwise, which should have pretty large database files, see. One way to time the `sync' calls is by forcing them with a `time sync' command, although with regular 30 second updates, you need to hit it just before the scheduled sync. The way to figure out just when these happen, assuming your INN is running normally, is to give repeated commands `time ctlinnd mode', which normally should return after about 0.030 secs (give or take a bit), until the actual history disk activity takes place, that for me takes perhaps ten seconds at average article flows. On the other hand, at 115MB for the hash file, and 76MB for the index file, that's some 190MB, much of which needs to be updated at 40Mbit/sec or so... I'll have to eyeball the disks on the Slowaris box now. thanks, barry bouwsma, tele danmark internet or something To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 6:30:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.qx.net (darkstar.qx.net [208.235.88.101]) by hub.freebsd.org (Postfix) with ESMTP id 7021B155EB for ; Tue, 25 Jan 2000 06:30:40 -0800 (PST) (envelope-from gchil0@pop.uky.edu) Received: from mail.qx.net (mail.qx.net [208.235.88.10]) by darkstar.qx.net (8.8.7/8.8.7) with ESMTP id JAA25145 for ; Tue, 25 Jan 2000 09:30:38 -0500 Received: from k7 ([207.246.86.12]) by mail.qx.net (Netscape Messaging Server 3.6) with ESMTP id AAA3E9C; Tue, 25 Jan 2000 09:33:27 -0500 Message-Id: <4.2.0.58.20000125092146.00961dc0@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 25 Jan 2000 09:32:03 -0500 To: Soren Schmidt From: Greg Childers Subject: Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS Cc: current@freebsd.org In-Reply-To: <200001250719.IAA61546@freebsd.dk> References: <4.2.0.58.20000124185659.0095acb0@pop.uky.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:19 AM 1/25/00 +0100, Soren Schmidt wrote: > > On some older PCI systems, including my Pentium 66, the driver still= detects > > irq 0 for ata-pci0. Hardwiring it to irq 14 in the source as suggested= recently is the >temporary fix I'm using.=20 > >Could you send that patch around me please ? > >-S=F8ren The quick fix I'm using is at the end of this email. The irq was correctly= detected before the following commit: sos 1999/10/09 12:57:15 PDT Modified files: sys/dev/ata ata-all.c ata-all.h ata-disk.c ata-disk.h=20 ata-dma.c atapi-all.c atapi-all.h=20 atapi-cd.c atapi-fd.c atapi-fd.h=20 atapi-tape.c atapi-tape.h=20 Log: Add support for the HPT366 chip, this is used on the Abit boards and their HotRod controller and on SIIG PCI ultra DMA controller. These changes also made lots of the Promise code go away, its all much more generic this way. =20 Get rid of atapi_immed_cmd, instead use the queue to move atapi commands from interrupt context if nessesary, the entire atapi layer has gotten an overhaul. =20 Lots of fixes to utililize the new features in subr_disk.c etc, and get rid of the last biots of softc arrays in the drivers, the only one left is atadevices which cannot easily go away (yet). =20 Use our own malloc names, its a lot easier to track memory usage this= way. =20 General cleanup overall. Hope this helps! Greg --- ata-all.c.orig Sun Jan 16 17:08:59 2000 +++ ata-all.c Sun Jan 16 17:09:30 2000 @@ -291,6 +291,11 @@ iobase_1 =3D pci_read_config(dev, 0x10, 4) & IOMASK; altiobase_1 =3D pci_read_config(dev, 0x14, 4) & IOMASK; irq1 =3D pci_read_config(dev, PCI_INTERRUPT_REG, 4) & 0xff; + if (irq1 !=3D 14) { + printf("Detected irq: %d ", irq1); + printf("Changing to 14!!\n"); + irq1 =3D 14; + } } =20 if (pci_get_progif(dev) & PCIP_STORAGE_IDE_MASTERDEV) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 6:34:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id AB505151FA; Tue, 25 Jan 2000 06:34:28 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id JAA68126; Tue, 25 Jan 2000 09:34:21 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001251434.JAA68126@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000124234329.C83466@dragon.nuxi.com> Date: Tue, 25 Jan 2000 09:34:21 -0500 (EST) From: John Baldwin To: "David O'Brien" Subject: Re: ascii art in hosts.allow Cc: freebsd-current@FreeBSD.org, Andy Farkas Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Jan-00 David O'Brien wrote: > On Tue, Jan 25, 2000 at 03:03:32PM +1100, Andy Farkas wrote: >> Here is a patch: (please notice the spelling correction) > > Where? I just ran ispell on src/etc/hosts.allow and it didn't catch > anything. not -> no I think.. it was more of a gramma gotcha than a misspelling. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 6:46:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 521CB1512B; Tue, 25 Jan 2000 06:46:10 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id JAA69557; Tue, 25 Jan 2000 09:46:09 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001251446.JAA69557@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001251434.JAA68126@server.baldwin.cx> Date: Tue, 25 Jan 2000 09:46:09 -0500 (EST) From: John Baldwin To: John Baldwin Subject: Re: ascii art in hosts.allow Cc: Andy Farkas , freebsd-current@FreeBSD.org, "David O'Brien" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Jan-00 John Baldwin wrote: > > On 25-Jan-00 David O'Brien wrote: >> On Tue, Jan 25, 2000 at 03:03:32PM +1100, Andy Farkas wrote: >>> Here is a patch: (please notice the spelling correction) >> >> Where? I just ran ispell on src/etc/hosts.allow and it didn't catch >> anything. > > not -> no I think.. it was more of a gramma gotcha than a misspelling. ^^^^^^ Unlike this, which is clearly a misspelling. :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 7: 2:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id E46A015186; Tue, 25 Jan 2000 07:02:40 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (andyf@localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id CAA16308; Wed, 26 Jan 2000 02:02:37 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Wed, 26 Jan 2000 02:02:36 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: ascii art in hosts.allow In-Reply-To: <20000124233834.A83466@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, David O'Brien wrote: > > What is the reason for putting a giant "Example!" in hosts.allow? > > So you'll notice that this file is an example and *demands* your > attention in configuring your system properly. Change it to hosts.allow.sample then? No hosts.allow file is essentially the same as the ALL:ALL:allow rule, no? > > I note that it was committed at 3 o'clock in the morning... > > Sounds like normal hacking time to me. Fair enough. Please note that I respect your efforts, and was not trying to insinuate anything. I just find this kind of [ascii art] thing a bit out of style with the rest of the system. This is the point I'm trying to make. > > was someone trying to make a point? > > Yes, don't shoot yourself in the foot by leaving your system wide open. Then say this in a new comment at the top of the file. It is not clear *why* you have to modify it, although the next set of comments does say "Start by allowing everything". It works out-of-the-box, so why should you change it? (yes, I know why). > > What other files have this type of gross bit-bloat in them? > > src/sys/ Again, what I was trying to say is that there aren't any other files with giant lettering in them, are there? > > -- > -- David (obrien@NUXI.com) > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 7:40:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 1CDB91522A for ; Tue, 25 Jan 2000 07:40:08 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (andyf@localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id CAA16490 for ; Wed, 26 Jan 2000 02:40:04 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Wed, 26 Jan 2000 02:40:03 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: freebsd-current@freebsd.org Subject: y2k problem? naahhh... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are some pretty funky date/times being displayed in my daily run output. Just thought I'd mention it; I've only just upgraded to 4.0-current and don't recall seeing this before. Backup passwd and group files: passwd diffs: --- /var/backups/master.passwd.bak Wed Jan 5 10:(password):41 2000 +++ /etc/master.passwd Tue Jan 25 15:(password):44 2000 @@ -1,3 +1,5 @@ +# $FreeBSD:(password):09:07 peter Exp $ +# root:(password):0:0::0:0:Charlie &:/root:/bin/csh toor:(password):0:0::0:0:Bourne-again Superuser:/root: daemon:(password):1:1::0:0:Owner of many system processes:/root:/sbin/nologin -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 7:52: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 1961914D1F for ; Tue, 25 Jan 2000 07:51:59 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id HAA90534 for ; Tue, 25 Jan 2000 07:51:55 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <388DC69A.EA4D0D73@MexComUSA.net> Date: Tue, 25 Jan 2000 07:51:54 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: This morning's make world References: <200001251540.HAA26105@local-27.local.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just found this in the log files for this morning's make worlds. Saludos, ed Charlie Root wrote: > cc -O -pipe -Wall -W -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/jot/jot.c > cc -O -pipe -Wall -W -I/usr/obj/usr/src/i386/usr/include -o jot jot.o > gzip -cn /usr/src/usr.bin/jot/jot.1 > jot.1.gz > ===> usr.bin/kdump > cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/kdump.c > cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c > In file included from ioctl.c:82: > /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined > /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition > In file included from ioctl.c:95: > /usr/obj/usr/src/i386/usr/include/sys/cdrio.h:59: warning: `CDRIOCBLANK' redefined > /usr/obj/usr/src/i386/usr/include/sys/wormio.h:102: warning: this is the location of the previous definition > In file included from ioctl.c:30: > /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:883: syntax error before `bus_dmamap_t' > /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1016: syntax error before `bus_dmamap_t' > /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1024: syntax error before `bus_space_tag_t' > /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1028: syntax error before `bus_addr_t' > /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1045: syntax error before `bus_dma_tag_t' > /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1136: syntax error before `bus_addr_t' > /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1273: syntax error before `bus_space_tag_t' > In file included from ioctl.c:33: > /usr/obj/usr/src/i386/usr/include/dev/vinum/vinumio.h:104: `MAXNAME' undeclared here (not in a function) > ioctl.c: In function `ioctlname': > ioctl.c:140: sizeof applied to an incomplete type > ioctl.c:236: sizeof applied to an incomplete type > ioctl.c:306: sizeof applied to an incomplete type > ioctl.c:374: sizeof applied to an incomplete type > ioctl.c:694: sizeof applied to an incomplete type > ioctl.c:1074: sizeof applied to an incomplete type > ioctl.c:1422: sizeof applied to an incomplete type > ioctl.c:1470: sizeof applied to an incomplete type > ioctl.c:1838: `dpt_perf_t' undeclared (first use in this function) > ioctl.c:1838: (Each undeclared identifier is reported only once > ioctl.c:1838: for each function it appears in.) > ioctl.c:1874: sizeof applied to an incomplete type > *** Error code 1 > > Stop in /usr/src/usr.bin/kdump. > *** Error code 1 > > Stop in /usr/src/usr.bin. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 7:58:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 86A291522A for ; Tue, 25 Jan 2000 07:58:28 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id KAA61595; Tue, 25 Jan 2000 10:58:25 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001251558.KAA61595@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nick Hibma Cc: FreeBSD CURRENT Mailing List From: "Louis A. Mamakos" Subject: Re: cvs commit: src/sys/dev/usb ugen.c References: In-reply-to: Your message of "Tue, 25 Jan 2000 00:54:09 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jan 2000 10:58:25 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One other lingering issue - I don't believe we install any of the USB > > header files (in particular, /sys/dev/usb/usb.h) in /usr/include. While > > I certainly have /usr/src populated on my box, we probably ought to not > > require it. > > > > Should it be installed in /usr/include/dev/usb/*.h? > > Hm, you are messing with my priorities here. Well, yes, that is supposed > to happen and nI guess it should happen before 4.0 is released I guess. Sorry about that :-) > One problem is how to limit the number of header files copied there. > Only usb.h, usbdi.h, usbdi_util.h and usbdevs.h should be copied there, > and not the other 453 header files in src/sys/dev/usb. Just as one data point, I only needed usb.h. On the other hand, I think that hid.h and usbhid.h might be useful for another class of application.. But thanks for the commit; this will surely help more outside-the-source-tree USB development along. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 7:58:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id D2DEB15234; Tue, 25 Jan 2000 07:58:29 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id PAA07636; Tue, 25 Jan 2000 15:30:52 GMT (envelope-from nik) Date: Tue, 25 Jan 2000 15:30:51 +0000 From: Nik Clayton To: Kris Kennaway Cc: current@freebsd.org, security@freebsd.org Subject: Re: OpenSSL docs for FAQ Message-ID: <20000125153051.A6364@catkin.nothing-going-on.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Kris Kennaway on Tue, Jan 25, 2000 at 12:49:04AM -0800 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 25, 2000 at 12:49:04AM -0800, Kris Kennaway wrote: > Can people please review this for style and content, for inclusion in > the FAQ? I'll also need someone to mark it up once it's ready since SGML > is currently not among my abilities :-) Is this FAQ material, or better off in the installation section of the Handbook? I'd veer towards the Handbook myself. I can't speak to the veracity of the content, but I can mark it up for the Handbook as necessary. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 8: 2: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 191A5151BA for ; Tue, 25 Jan 2000 08:01:55 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id RAA82141; Tue, 25 Jan 2000 17:01:25 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001251601.RAA82141@freebsd.dk> Subject: Re: 4.0 CODE FREEZE WILL BEGIN IN FIVE (5) DAYS In-Reply-To: <4.2.0.58.20000125092146.00961dc0@pop.uky.edu> from Greg Childers at "Jan 25, 2000 09:32:03 am" To: gchil0@pop.uky.edu (Greg Childers) Date: Tue, 25 Jan 2000 17:01:25 +0100 (CET) Cc: current@freebsd.org X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Greg Childers wrote: > Hope this helps! It may be helping you, but everyone having more than the ATA chip on the motherboard is going to be bitten severely by this as the interrupt for the primary channel on all controllers are now hardwired to irq 14. What does the Detected irq: say on your machine ?? We might do something intelligent if it is clearly out of range... > --- ata-all.c.orig Sun Jan 16 17:08:59 2000 > +++ ata-all.c Sun Jan 16 17:09:30 2000 > @@ -291,6 +291,11 @@ > iobase_1 = pci_read_config(dev, 0x10, 4) & IOMASK; > altiobase_1 = pci_read_config(dev, 0x14, 4) & IOMASK; > irq1 = pci_read_config(dev, PCI_INTERRUPT_REG, 4) & 0xff; > + if (irq1 != 14) { > + printf("Detected irq: %d ", irq1); > + printf("Changing to 14!!\n"); > + irq1 = 14; > + } > } > > if (pci_get_progif(dev) & PCIP_STORAGE_IDE_MASTERDEV) { -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 8: 6: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 77A16152A9 for ; Tue, 25 Jan 2000 08:05:39 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA06202; Tue, 25 Jan 2000 09:05:08 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA03962; Tue, 25 Jan 2000 09:04:51 -0700 (MST) Message-Id: <200001251604.JAA03962@harmony.village.org> To: Mitsuru IWASAKI Subject: Re: APM still ignoring DEVICE_SUSPEND errors Cc: dfr@nlsystems.com, n_hibma@webweaving.org, current@freebsd.org In-reply-to: Your message of "Tue, 25 Jan 2000 21:00:07 +0900." <200001251200.VAA24572@tasogare.imasy.or.jp> References: <200001251200.VAA24572@tasogare.imasy.or.jp> Date: Tue, 25 Jan 2000 09:04:51 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001251200.VAA24572@tasogare.imasy.or.jp> Mitsuru IWASAKI writes: : > > Any reason to not shoot the apm_hook_{suspend,resume} in the head and : > > just use newbus suspend/resume everywhere? : > : > Are there any non-newbus devices which need suspend/resume? I think the : > i386 clock uses the apm hooks but I might be misremembering. : : No, it just reloads the countdown register of i8254 in : apm_default_resume() for now. But once the PIT become an ordinary : device like any other, this is planned to be the device's resume : method. Sounds like a good reason to me (eg, there are still non-newbus driver users of this) to keep it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 8:19:45 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id BA27E14EB3; Tue, 25 Jan 2000 08:19:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id AB60B1CD699; Tue, 25 Jan 2000 08:19:08 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 25 Jan 2000 08:19:08 -0800 (PST) From: Kris Kennaway To: Nik Clayton Cc: current@freebsd.org, security@freebsd.org Subject: Re: OpenSSL docs for FAQ In-Reply-To: <20000125153051.A6364@catkin.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jan 2000, Nik Clayton wrote: > Is this FAQ material, or better off in the installation section of the > Handbook? I'd veer towards the Handbook myself. Seemed like a potential Frequently Asked Question to me, is all. I defer to your superior knowledge of our documentation standards :-) > I can't speak to the veracity of the content, but I can mark it up for > the Handbook as necessary. Thanks! :) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 8:21: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 15D2014DF2 for ; Tue, 25 Jan 2000 08:20:29 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id QAA08286; Tue, 25 Jan 2000 16:12:11 GMT (envelope-from n_hibma@webweaving.org) Date: Tue, 25 Jan 2000 16:12:10 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "Louis A. Mamakos" Cc: FreeBSD CURRENT Mailing List Subject: Re: cvs commit: src/sys/dev/usb ugen.c In-Reply-To: <200001251558.KAA61595@whizzo.transsys.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > One problem is how to limit the number of header files copied there. > > Only usb.h, usbdi.h, usbdi_util.h and usbdevs.h should be copied there, > > and not the other 453 header files in src/sys/dev/usb. > > Just as one data point, I only needed usb.h. On the other hand, I think > that hid.h and usbhid.h might be useful for another class of application.. There is between 3 and 5 files that should be there, hence my complaint. It is not possible to restrict the number of files there without creating a special case in the includes makefile. I guessed that CAM must have had the same problem sometime ago and just ignored it as well. Maybe that should be solved somehow. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 8:27: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.infolibria.com (mail.infolibria.com [199.103.137.198]) by hub.freebsd.org (Postfix) with ESMTP id 1790E14E81 for ; Tue, 25 Jan 2000 08:26:58 -0800 (PST) (envelope-from loverso@infolibria.com) Received: from infolibria.com (border [199.103.137.193]) by mail.infolibria.com (Postfix) with ESMTP id 3AD37DDB80; Tue, 25 Jan 2000 11:26:57 -0500 (EST) Message-ID: <388DCF1F.19385402@infolibria.com> Date: Tue, 25 Jan 2000 11:28:15 -0500 From: John LoVerso X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Alex Zepeda , freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Again, lemmie get on my soap box, and ask have you looked at the man page, > and compared the memory required when using -s to the memory required by > gzip? Actually, lemmie get on my soap box and ask have you measured the time that bunzip2 takes to run? While it does give better compression in many cases, it is just too SLOW. Using "-s" on decompression just makes it slower. I played on a test machine (PII 233MHz 192Mb, spare ST34502LW disk) with some large package binaries: 17991680 netscape-communicator-4.08.tar 19660800 netscape-communicator-4.61.tar 21934080 netscape-communicator-4.7.tar time gzip *tar 80.284u 1.608s 1:23.66 97.8% 113+616k 3+528io 0pf+0w time gunzip *gz 7.984u 1.392s 0:12.84 72.9% 115+674k 498+971io 0pf+0w time bzip2 *tar 220.777u 1.718s 3:44.74 98.9% 61+8531k 936+471io 0pf+0w time bunzip2 *bz2 64.601u 1.928s 1:07.30 98.8% 61+4855k 4+964io 0pf+0w time bzip2 -s *tar 205.854u 1.938s 3:32.95 97.5% 61+2388k 1012+492io 1pf+0w time bunzip2 -s *tar 121.860u 2.054s 2:05.65 98.6% 61+3167k 2+965io 0pf+0w A decompression time of 13 seconds vs. 67 seconds (or 125 seconds with "-s). Given that ports and packages need a multi-CD anyway, I don't think the speed penalty of bzip2 is worth it. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 8:30:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 391931522A; Tue, 25 Jan 2000 08:29:18 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id IAA17647; Tue, 25 Jan 2000 08:29:16 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id IAA24535; Tue, 25 Jan 2000 08:29:16 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 25 Jan 2000 08:29:16 -0800 (PST) Message-Id: <200001251629.IAA24535@vashon.polstra.com> To: andyf@speednet.com.au Subject: Re: y2k problem? naahhh... In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Andy Farkas wrote: > > There are some pretty funky date/times being displayed in my daily run > output. Just thought I'd mention it; I've only just upgraded to > 4.0-current and don't recall seeing this before. > > > Backup passwd and group files: > passwd diffs: > --- /var/backups/master.passwd.bak Wed Jan 5 10:(password):41 2000 > +++ /etc/master.passwd Tue Jan 25 15:(password):44 2000 > @@ -1,3 +1,5 @@ > +# $FreeBSD:(password):09:07 peter Exp $ > +# > root:(password):0:0::0:0:Charlie &:/root:/bin/csh > toor:(password):0:0::0:0:Bourne-again Superuser:/root: > daemon:(password):1:1::0:0:Owner of many system processes:/root:/sbin/nologin Heh, I'd say revision 1.5 of "src/etc/periodic/daily/200.backup-passwd" needs a bit more work. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 9:59:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 81EB715269 for ; Tue, 25 Jan 2000 09:59:33 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id MAA92935; Tue, 25 Jan 2000 12:59:20 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001251759.MAA92935@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001251629.IAA24535@vashon.polstra.com> Date: Tue, 25 Jan 2000 12:59:20 -0500 (EST) From: John Baldwin To: John Polstra Subject: Re: y2k problem? naahhh... Cc: current@FreeBSD.org, andyf@speednet.com.au Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Jan-00 John Polstra wrote: > In article > , > Andy Farkas wrote: >> >> There are some pretty funky date/times being displayed in my daily run >> output. Just thought I'd mention it; I've only just upgraded to >> 4.0-current and don't recall seeing this before. >> >> >> Backup passwd and group files: >> passwd diffs: >> --- /var/backups/master.passwd.bak Wed Jan 5 10:(password):41 2000 >> +++ /etc/master.passwd Tue Jan 25 15:(password):44 2000 >> @@ -1,3 +1,5 @@ >> +# $FreeBSD:(password):09:07 peter Exp $ >> +# >> root:(password):0:0::0:0:Charlie &:/root:/bin/csh >> toor:(password):0:0::0:0:Bourne-again Superuser:/root: >> daemon:(password):1:1::0:0:Owner of many system >> processes:/root:/sbin/nologin > > Heh, I'd say revision 1.5 of "src/etc/periodic/daily/200.backup-passwd" > needs a bit more work. :-) Doh, I tried to fix the sed expression so it would work with various diff formats (since I, for example, prefer the old format). I guess a simple: 'egrep -v '^(---|+++|@@)' inserted in the pipeline between the diff -u and the sed might fix it. Then again, we could just get rid of the '-u' option to diff. :) > John -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 10:19:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from midway.uchicago.edu (midway.uchicago.edu [128.135.12.12]) by hub.freebsd.org (Postfix) with ESMTP id 4B7761504E for ; Tue, 25 Jan 2000 10:19:31 -0800 (PST) (envelope-from charon@freethought.org) Received: from broad-208-049 (broad-208-049.rh.uchicago.edu [128.135.208.49]) by midway.uchicago.edu (8.9.3/8.9.3) with ESMTP id MAA14388; Tue, 25 Jan 2000 12:19:14 -0600 (CST) From: charon@freethought.org Message-Id: <4.2.2.20000125121223.00b36100@nsit-popmail.uchicago.edu> X-Sender: dbsypher@nsit-popmail.uchicago.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Tue, 25 Jan 2000 12:19:09 -0600 To: Bill Swingle Subject: Re: connectivity problems with current.freebsd.org Cc: current@FreeBSD.ORG In-Reply-To: <20000125010340.A19603@dub.net> References: <4.2.2.20000124233054.00b81e00@nsit-popmail.uchicago.edu> <4.2.2.20000124233054.00b81e00@nsit-popmail.uchicago.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:03 AM 1/25/00 -0800, Bill Swingle wrote: >On Mon, Jan 24, 2000 at 11:43:59PM -0600, charon@freethought.org wrote: > > By chance, playing around with the fact that current.freebsd.org is an > > alias for usw2.freebsd.org, I found that usw3.freebsd.org (209.180.6.227) > > mirrors snapshots as well. Perhaps something should be added to the > > /snapshots readme.txt on ftp.freebsd.org about the fact that > > current.freebsd.org has mirrors. That said, I've gotten the same error > > from usw3 as from usw2. > >I can't really speak to your download problems but it should be noted >that usw2 and usw3 are in the same facility at USWest, in fact they're >probably in the very same rack as each other. Noting that this other >'mirror' is available would not do much good as they both sit on the >exact same bandwidth. I'm sure this is a silly question, but then why does usw3 appear to _be_ a mirror? Why have usw3 at all? -David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 10:54: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 0EA5815271 for ; Tue, 25 Jan 2000 10:53:49 -0800 (PST) (envelope-from rajappa@mindspring.com) Received: from kamikaze.mindspring.com (user-2ivebdv.dialup.mindspring.com [165.247.45.191]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id NAA30453 for ; Tue, 25 Jan 2000 13:53:42 -0500 (EST) Received: (from rsi@localhost) by kamikaze.mindspring.com (8.9.3/8.9.3) id NAA65739; Tue, 25 Jan 2000 13:58:18 -0500 (EST) (envelope-from rajappa@mindspring.com) Message-Id: <200001251858.NAA65739@kamikaze.mindspring.com> X-Authentication-Warning: kamikaze.mindspring.com: rsi set sender to rajappa@mindspring.com using -f To: current@freebsd.org Subject: make release failure From: Rajappa Iyer Date: 25 Jan 2000 13:58:17 -0500 Reply-To: rajappa@mindspring.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG make release fails on "make world" with: + make world -------------------------------------------------------------- >>> elf make world started on Tue Jan 25 18:53:25 GMT 2000 -------------------------------------------------------------- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! >>> You must define the value of USA_RESIDENT as 'YES' or >>> 'NO' as appropriate, in the environment or /etc/make.conf >>> before building can proceed. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. The problem is that $CHROOTDIR/etc/make.conf is never created by make release. What am I missing? Thanks, Rajappa -- a.k.a. Rajappa Iyer. New York, New York. We're too busy mopping the floor to turn off the faucet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 11: 3:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from zmamail01.zma.compaq.com (zmamail01.zma.compaq.com [161.114.64.101]) by hub.freebsd.org (Postfix) with ESMTP id E43D114EC0 for ; Tue, 25 Jan 2000 11:03:40 -0800 (PST) (envelope-from bruceb@txn.cpqcorp.net) Received: by zmamail01.zma.compaq.com (Postfix, from userid 12345) id B08F2444; Tue, 25 Jan 2000 14:03:33 -0500 (EST) Received: from fedex-s1.txn.cpqcorp.net (fedex-s1.txn.cpqcorp.net [16.74.4.108]) by zmamail01.zma.compaq.com (Postfix) with ESMTP id 6C4D3411 for ; Tue, 25 Jan 2000 14:03:33 -0500 (EST) From: Bruce Burden Posted-Date: Tue, 25 Jan 2000 13:04:05 -0600 (CST) Received: (from bruceb@localhost) by panther.txn.cpqcorp.net (8.9.3/8.9.3) id MAA28792 for current@freebsd.org; Tue, 25 Jan 2000 12:59:10 -0600 (CST) Message-Id: <200001251859.MAA28792@panther.txn.cpqcorp.net> Subject: Re: make release failure To: current@freebsd.org Date: Tue, 25 Jan 2000 12:59:10 -0600 (CST) Reply-To: bruce.burden@compaq.com In-Reply-To: <200001251858.NAA65739@kamikaze.mindspring.com> from "Rajappa Iyer" at Jan 25, 2000 01:58:17 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > make release fails on "make world" with: > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > >>> You must define the value of USA_RESIDENT as 'YES' or > >>> 'NO' as appropriate, in the environment or /etc/make.conf > >>> before building can proceed. > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > The problem is that $CHROOTDIR/etc/make.conf is never created by make > release. What am I missing? > /etc files are never installed by "make installworld". You have to install these files yourself, or use something like mergemaster(8). make.conf in found in /usr/src/etc/etc.[i386,alpha]/make.conf Bruce -- ------------------------------------------------------------------------------- Bruce Burden bruceb@isd.tandem.com Tandem Computers Inc. 512-432-8944 Network Verification 14231 Tandem Blvd. Auto answer(4 rings) Austin, TX 78726 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 11:44:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id BD5E814C37 for ; Tue, 25 Jan 2000 11:44:46 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id OAA97160; Tue, 25 Jan 2000 14:44:05 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Tue, 25 Jan 2000 14:44:05 -0500 (EST) From: Chuck Robey To: Lars Eggert Cc: Ilya Zakharevich , perl5-porters@perl.org, current@FreeBSD.ORG Subject: Re: [ID 20000124.004] "perl in malloc(): warning: recursive call" on In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 24 Jan 2000, Lars Eggert wrote: > Ilya, > > thanks for the quick response. > > > Signals and Perl do not mix. Please do not use signals if a segfault > > is not a desirable form of output. > > Never? After reading perlipc I was under the impression that using signals > was okay if you keep your handlers simple. I may have to use to another form > of IPC if signals cannot be made safe. Our malloc can't be used in a signal handler. > > Lars > ____________________________________________________________________________ > Lars Eggert Information Sciences Institute > http://www.isi.edu/~larse/ University of Southern California > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 11:51:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 7696214E4E for ; Tue, 25 Jan 2000 11:51:39 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id UAA27851; Tue, 25 Jan 2000 20:51:37 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id UAA14772; Tue, 25 Jan 2000 20:51:56 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id UAA03088; Tue, 25 Jan 2000 20:51:40 +0100 (CET) Date: Tue, 25 Jan 2000 20:51:40 +0100 (CET) From: Christoph Kukulies Message-Id: <200001251951.UAA03088@gil.physik.rwth-aachen.de> To: mgetty@greenie.muc.de Subject: locking problem FreeBSD 3.4 - kermit and mgetty Cc: freebsd-current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG C-Kermit 7.0.196 Beta.11, 6 Dec 1999, for FreeBSD 3.0 mgetty: experimental test release 1.1.21-Jul24 FreeBSD 3.4 I had running kermit and mgetty running happily together, one not disturbing the other (I had a mgetty running on cuaa1 (/etc/ttys)) and when I hand dialed via kermit mgetty got politely out of the way. (never cared about it - it used to work under FreeBSD 2.2.8). Now after an upgrade to FreeBSD 3.4 I added the packages above (kermit and mgetty) to have up-to-date binaries. But as a result mgetty gets into kermit's ways such that when a modem connection is made I suddenly get a modem prompt like +FCON as if someone (mgetty) is either messing with my local or the remote modem while kermit opens the connection. Clueless. Can only do a kill -TSTP 1 , kill the last mgetty and use kermit and have to kill -HUP 1 after that. -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 12: 9:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mathserv.mps.ohio-state.edu (mathserv.mps.ohio-state.edu [128.146.111.31]) by hub.freebsd.org (Postfix) with ESMTP id 19460152BE for ; Tue, 25 Jan 2000 12:09:50 -0800 (PST) (envelope-from ilya@math.ohio-state.edu) Received: from monk.mps.ohio-state.edu (monk.mps.ohio-state.edu [128.146.111.52]) by mathserv.mps.ohio-state.edu (8.9.3+Sun/8.9.3) with ESMTP id PAA29672; Tue, 25 Jan 2000 15:09:45 -0500 (EST) Received: (from ilya@localhost) by monk.mps.ohio-state.edu (8.9.3+Sun/8.9.3) id PAA02127; Tue, 25 Jan 2000 15:09:45 -0500 (EST) Date: Tue, 25 Jan 2000 15:09:45 -0500 From: Ilya Zakharevich To: Chuck Robey Cc: Lars Eggert , perl5-porters@perl.org, current@FreeBSD.ORG Subject: Re: [ID 20000124.004] "perl in malloc(): warning: recursive call" on Message-ID: <20000125150945.C2011@monk.mps.ohio-state.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from chuckr@picnic.mat.net on Tue, Jan 25, 2000 at 02:44:05PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 25, 2000 at 02:44:05PM -0500, Chuck Robey wrote: > On Mon, 24 Jan 2000, Lars Eggert wrote: > > > Ilya, > > > > thanks for the quick response. > > > > > Signals and Perl do not mix. Please do not use signals if a segfault > > > is not a desirable form of output. > > > > Never? After reading perlipc I was under the impression that using signals > > was okay if you keep your handlers simple. I may have to use to another form > > of IPC if signals cannot be made safe. > > Our malloc can't be used in a signal handler. One can write a signal handler in such a way that no mallocs are going to be called (see my example). But this would not help: segfaults will happen anyway. Ilya To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 12:49:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 92C6015381 for ; Tue, 25 Jan 2000 12:49:13 -0800 (PST) (envelope-from rajappa@mindspring.com) Received: from kamikaze.mindspring.com (user-2ive6kv.dialup.mindspring.com [165.247.26.159]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id PAA29945 for ; Tue, 25 Jan 2000 15:49:01 -0500 (EST) Received: (from rsi@localhost) by kamikaze.mindspring.com (8.9.3/8.9.3) id PAA00478; Tue, 25 Jan 2000 15:54:23 -0500 (EST) (envelope-from rajappa@mindspring.com) Message-Id: <200001252054.PAA00478@kamikaze.mindspring.com> X-Authentication-Warning: kamikaze.mindspring.com: rsi set sender to rajappa@mindspring.com using -f To: current@freebsd.org Subject: Re: make release failure References: <200001251859.MAA28792@panther.txn.cpqcorp.net> From: Rajappa Iyer Date: 25 Jan 2000 15:54:13 -0500 Reply-To: rajappa@mindspring.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Burden writes: > > > > make release fails on "make world" with: > > > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > >>> You must define the value of USA_RESIDENT as 'YES' or > > >>> 'NO' as appropriate, in the environment or /etc/make.conf > > >>> before building can proceed. > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > > > The problem is that $CHROOTDIR/etc/make.conf is never created by make > > release. What am I missing? > > > /etc files are never installed by "make installworld". You > have to install these files yourself, or use something like > mergemaster(8). > > make.conf in found in /usr/src/etc/etc.[i386,alpha]/make.conf Yes, but $CHROOTDIR/etc is populated by "make installworld" when I do a "make release". My ``real'' /etc/make.conf exists and has the appropriate value for USA_RESIDENT. I see that /usr/src/release/Makefile does copy /etc/resolv.conf to ${CHROOTDIR}/etc. Maybe it should do the same for /etc/make.conf. What do people think of the following patch? Index: Makefile =================================================================== RCS file: /home/ncvs/src/release/Makefile,v retrieving revision 1.530 diff -c -r1.530 Makefile *** Makefile 2000/01/24 01:22:30 1.530 --- Makefile 2000/01/25 20:52:53 *************** *** 37,42 **** --- 37,46 ---- # Unless set elsewhere, indicate the object format we'll be using. OBJFORMAT?= elf + # make world needs make.conf which make installworld will not install + # in ${CHROOTDIR}/etc. + MAKECONF?= /etc/make.conf + # Uncomment this to disable the doc.1 target. It is also an ERROR # to set NOPORTS and not set NODOC since docs depend on ports. #NODOC= YES *************** *** 155,160 **** --- 159,167 ---- cd ${.CURDIR}/../etc && ${MAKE} distribution DESTDIR=${CHROOTDIR} if [ -f /etc/resolv.conf ]; then \ cp -p /etc/resolv.conf ${CHROOTDIR}/etc; \ + fi + if [ -f ${MAKECONF} ]; then \ + cp -p ${MAKECONF} ${CHROOTDIR}/etc; \ fi cd ${.CURDIR}/.. && ${MAKE} installworld DESTDIR=${CHROOTDIR} NOMAN=1 mkdir ${CHROOTDIR}/${BOOTSTRAPDIR} Thanks, Rajappa -- a.k.a. Rajappa Iyer. New York, New York. We're too busy mopping the floor to turn off the faucet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 12:58:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id 4ECE314E3F for ; Tue, 25 Jan 2000 12:58:12 -0800 (PST) (envelope-from tom@embt.com) Received: from PARANOR (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id PAA12261; Tue, 25 Jan 2000 15:05:01 -0600 (CST) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.20000125155655.00f8a1b8@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 25 Jan 2000 15:56:55 -0500 To: Soren Schmidt , anders@sanyusan.se (Anders Andersson) From: Tom Embt Subject: Re: My ATAPI CD not come ready Cc: mzaki@e-mail.ne.jp (Motomichi Matsuzaki), current@FreeBSD.ORG In-Reply-To: <200001250847.JAA82387@freebsd.dk> References: <20000125094011.A8591@enterprise.sanyusan.se> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:47 01/25/2000 +0100, Soren Schmidt wrote: >It seems Anders Andersson wrote: >> I have the same problem: >>=20 >> [anders@enterprise:anders] $ dmesg | grep ata >> ata-pci0: port 0xffa0-0xffaf at device 7.1 >> on pci0 >> ata0 at 0x01f0 irq 14 on ata-pci0 >> ata-isa0: already registered as ata0 >> ata0-slave: ata_command: timeout waiting for intr >> ata0-slave: identify failed > >Could I please have a complete dmesg from that ?? > >-S=F8ren > Don't mean to butt in here, I haven't really been following the thread - but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) on secondary master of the PIIX4 on my BP6. By going into the BIOS (the section of it where you would set CHS numbers, LBA, etc) and changing the secondary master device from "none" to "auto", I have gone from: SMP: AP CPU #1 Launched! ata1-master: ata_command: timeout waiting for intr ata1-master: identify failed ad0: 9671MB disk at ata0 as master mode UDMA33 Mounting root from ufs:/dev/ad0s1a to: SMP: AP CPU #1 Launched! ad0: 9671MB disk at ata0 as master mode UDMA33 acd0: CDROM at ata1 as master mode PIO0 Mounting root from ufs:/dev/ad0s1a I stumbled upon this quite by accident, but maybe it'll be of some help to somebody... BTW, this was on a kernel from around 20:00 GMT Jan 25 Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 12:58:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id CD96D1503D for ; Tue, 25 Jan 2000 12:58:46 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.9.3/8.9.3) id VAA09375; Tue, 25 Jan 2000 21:58:45 +0100 (CET) (envelope-from olli) Date: Tue, 25 Jan 2000 21:58:45 +0100 (CET) Message-Id: <200001252058.VAA09375@dorifer.heim3.tu-clausthal.de> From: Oliver Fromme To: freebsd-current@FreeBSD.ORG Reply-To: freebsd-current@FreeBSD.ORG Subject: Re: connectivity problems with current.freebsd.org X-Newsgroups: list.freebsd-current In-Reply-To: <86jouu$38i$1@atlantis.rz.tu-clausthal.de> User-Agent: tin/1.4.1-19991201 ("Polish") (UNIX) (FreeBSD/3.4-19991219-STABLE (i386)) MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Swingle wrote in list.freebsd-current: > On Mon, Jan 24, 2000 at 11:43:59PM -0600, charon@freethought.org wrote: >> By chance, playing around with the fact that current.freebsd.org is an >> alias for usw2.freebsd.org, I found that usw3.freebsd.org (209.180.6.227) >> mirrors snapshots as well. Perhaps something should be added to the >> /snapshots readme.txt on ftp.freebsd.org about the fact that >> current.freebsd.org has mirrors. That said, I've gotten the same error >> from usw3 as from usw2. > > I can't really speak to your download problems but it should be noted > that usw2 and usw3 are in the same facility at USWest, in fact they're > probably in the very same rack as each other. Noting that this other > 'mirror' is available would not do much good as they both sit on the > exact same bandwidth. FWIW, we're mirroring the most recent snapshots at ftp7.de.freebsd.org. There's also a nice page listing all mirror sites of FreeBSD releases and snapshots: http://www.itworks.com.au/~gavin/FBSDsites.php3 Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 13: 2: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 50AB314C0F for ; Tue, 25 Jan 2000 13:01:55 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA83248; Tue, 25 Jan 2000 22:01:13 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001252101.WAA83248@freebsd.dk> Subject: Re: My ATAPI CD not come ready In-Reply-To: <3.0.3.32.20000125155655.00f8a1b8@mail.embt.com> from Tom Embt at "Jan 25, 2000 03:56:55 pm" To: tom@embt.com (Tom Embt) Date: Tue, 25 Jan 2000 22:01:13 +0100 (CET) Cc: anders@sanyusan.se (Anders Andersson), mzaki@e-mail.ne.jp (Motomichi Matsuzaki), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Tom Embt wrote: > Don't mean to butt in here, I haven't really been following the thread - > but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) > on secondary master of the PIIX4 on my BP6. By going into the BIOS (the > section of it where you would set CHS numbers, LBA, etc) and changing the > secondary master device from "none" to "auto", I have gone from: > > BTW, this was on a kernel from around 20:00 GMT Jan 25 Interesting... What version is you ata-all.c ?? its damn close to the commit I just made, that should fix that problem... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 13:13:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from ozz.freebsd.org.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id AFDCC15158 for ; Tue, 25 Jan 2000 13:13:13 -0800 (PST) (envelope-from osa@ozz.freebsd.org.ru) Received: (from osa@localhost) by ozz.freebsd.org.ru (8.9.3/8.9.3) id AAA58220 for freebsd-current@FreeBSD.org; Wed, 26 Jan 2000 00:13:03 +0300 (MSK) (envelope-from osa) Date: Wed, 26 Jan 2000 00:13:01 +0300 From: Sergey Osokin To: freebsd-current@FreeBSD.org Subject: make world failed at usr.bin/kdump Message-ID: <20000126001301.A58205@freebsd.org.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> usr.bin/kdump cc -O2 -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/kdump.c cc -O2 -pipe -march=pentium -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:81: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition In file included from ioctl.c:95: /usr/obj/usr/src/i386/usr/include/sys/cdrio.h:59: warning: `CDRIOCBLANK' redefined /usr/obj/usr/src/i386/usr/include/sys/wormio.h:102: warning: this is the location of the previous definition In file included from ioctl.c:30: /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:883: syntax error before `bus_dmamap_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1016: syntax error before `bus_dmamap_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1024: syntax error before `bus_space_tag_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1028: syntax error before `bus_addr_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1045: syntax error before `bus_dma_tag_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1136: syntax error before `bus_addr_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1273: syntax error before `bus_space_tag_t' In file included from ioctl.c:33: /usr/obj/usr/src/i386/usr/include/dev/vinum/vinumio.h:104: `MAXNAME' undeclared here (not in a function) ioctl.c: In function `ioctlname': ioctl.c:140: sizeof applied to an incomplete type ioctl.c:236: sizeof applied to an incomplete type ioctl.c:306: sizeof applied to an incomplete type ioctl.c:374: sizeof applied to an incomplete type ioctl.c:694: sizeof applied to an incomplete type ioctl.c:1074: sizeof applied to an incomplete type ioctl.c:1422: sizeof applied to an incomplete type ioctl.c:1470: sizeof applied to an incomplete type ioctl.c:1838: `dpt_perf_t' undeclared (first use in this function) ioctl.c:1838: (Each undeclared identifier is reported only once ioctl.c:1838: for each function it appears in.) ioctl.c:1874: sizeof applied to an incomplete type *** Error code 1 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. Rgdz, Sergey A. Osokin, osa@FreeBSD.org.ru http://www.FreeBSD.org.ru/~osa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 13:20:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by hub.freebsd.org (Postfix) with ESMTP id 1BEB815337 for ; Tue, 25 Jan 2000 13:19:52 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id NAA19841 for ; Tue, 25 Jan 2000 13:19:55 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id NAA12924; Tue, 25 Jan 2000 13:21:50 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Tue, 25 Jan 2000 13:21:49 -0800 (PST) From: Brian Beattie To: current@freebsd.org Subject: building modules Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to figure out how to make a makefile to build a module and have run into something I do not understand. I am working with freshly cvsup'ed sources. When I try to build a module in /sys/modules, the command line contains a -DKERNEL, which I find in bsd.kmod.mk. This causes the wrong definitions to be defined, since the correct ones are protected by #ifdef _KERNEL. (note the _). This is the case for running make from /sys, /sys/module, or /sys/module/ I looked a buildworld log from Jan 25, unknown cvs date, and the modules are built with -D_KERNEL, as I would expect. Am I doing something wrong, did something change, or do I just not understand? Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 13:20:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E0CBB14E8F for ; Tue, 25 Jan 2000 13:20:24 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA66915; Tue, 25 Jan 2000 13:16:20 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: charon@freethought.org Cc: Bill Swingle , current@FreeBSD.ORG Subject: Re: connectivity problems with current.freebsd.org In-reply-to: Your message of "Tue, 25 Jan 2000 12:19:09 CST." <4.2.2.20000125121223.00b36100@nsit-popmail.uchicago.edu> Date: Tue, 25 Jan 2000 13:16:20 -0800 Message-ID: <66912.948834980@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm sure this is a silly question, but then why does usw3 appear to _be_ a > mirror? Why have usw3 at all? It's NOT a mirror and I really wish people would stop jumping to conclusions with tenuous data because it's really very simple and not like anyone is currently speculating: 1. There is a machine called current.freebsd.org (AKA usw2) which runs 4.0-current and builds -current snapshots. 2. There is a machine called releng3.freebsd.org (AKA usw3) which runs 3-stable and builds -stable snapshots. 3. Both of these machines share a large ccd disk volume (I don't need vinum to do what I already have ccd working just fine on) which they copy their successful snapshots to. 4. Each machine runs an ftpd and points to this common volume for exporting the bits in a way which is obviously easier for me to maintain. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 13:58:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 04CB314EB8 for ; Tue, 25 Jan 2000 13:58:48 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 8379 invoked from network); 25 Jan 2000 21:58:41 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 25 Jan 2000 21:58:41 -0000 Message-ID: <388E1C6B.489B84D2@cvzoom.net> Date: Tue, 25 Jan 2000 16:58:03 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Re: pcm - stutters References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > The output of my ESS 1869 stutters whenever there is no new data fed to > it. For example pressing Ctrl-Z, or heavy disk usage (normally making > mpg123 jump). The stuttering is repetition of one short fragment of > about a quarter of a second, indefinitely I can confirm this. Whenever there is any substantial disk activity, the output of mpg123 starts to jump and quiver (and sometimes skip). Why would disk activity do this? Must be an issue with bus latency, because the ata and sound driver are trying to access the bus at the same time. Also, it seems like certain graphics ops in XFree86 3.9.17 make mpg123 jump and skip. Strangely, RealPlayer doesn't suffer from these problems. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 14: 3:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id 7FD30155D6 for ; Tue, 25 Jan 2000 14:02:37 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS4-p92.rlz.netvision.net.il [62.0.169.216]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id AAA03846; Wed, 26 Jan 2000 00:01:47 +0200 (IST) Message-ID: <388E1D86.10D7D7F0@freenet.co.uk> Date: Tue, 25 Jan 2000 22:02:46 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: My ATAPI CD not come ready References: <20000125094011.A8591@enterprise.sanyusan.se> <3.0.3.32.20000125155655.00f8a1b8@mail.embt.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Speaking of identify failed, I get the following: ata-pci0: port 0xfcf0-0xfcff at device 1.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB disk at ata0 as master mode UDMA33 acd0: CDROM at ata1 as master mode PIO4 Why does identify fail on ata1-slave? ^^^^^ I don't have any slave devices on ata1 that I know of. I used to get this: ad0: ATA-4 disk at ata0 as master ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, PIO acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked ata_command: timeout waiting for interrupt and wonder about this timeout thing, but now it seems it has nothing to do with the actual device (ata1-master). Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 14:18:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx2.x-treme.gr (mx2.x-treme.gr [212.120.192.15]) by hub.freebsd.org (Postfix) with ESMTP id 4C83B1529B; Tue, 25 Jan 2000 14:18:17 -0800 (PST) (envelope-from keramida@diogenis.ceid.upatras.gr) Received: from hades.hell.gr (pat59.x-treme.gr [212.120.197.251]) by mx2.x-treme.gr (8.9.3/8.9.3/IPNG-ADV-ANTISPAM-0.1) with ESMTP id AAA14287; Wed, 26 Jan 2000 00:18:09 +0200 Received: (from charon@localhost) by charon.hell.gr (8.9.3/8.9.3) id FAA64435; Tue, 25 Jan 2000 05:14:19 +0200 (EET) (envelope-from keramida@diogenis.ceid.upatras.gr) Date: Tue, 25 Jan 2000 05:14:18 +0200 From: the Webslave To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: ipfilter and ipfstat Message-ID: <20000125051418.A62880@charon.hell.gr> Reply-To: keramida@ceid.upatras.gr References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Mon, Jan 24, 2000 at 12:02:26AM -0800 X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E X-Phone-Number: +30-94-6203692, +30-93-2886457 X-Address: Theodorou Kirinaiou 61, 26334 Patra, Greece Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 24, 2000 at 12:02:26AM -0800, Kris Kennaway wrote: > > Okay, so I finally decided to take the plunge and check out ipfilter. ipf > seemed to load my ruleset with no problems, but ipfstat dies with: > > ioctl(SIOCGETFS): Invalid argument And what would that ruleset be? -- Giorgos Keramidas, < keramida @ ceid . upatras . gr > "Don't let your schooling interfere with your education." [Mark Twain] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 14:23:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 30AC7151AA for ; Tue, 25 Jan 2000 14:22:58 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id XAA83537; Tue, 25 Jan 2000 23:22:45 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001252222.XAA83537@freebsd.dk> Subject: Re: My ATAPI CD not come ready In-Reply-To: <388E1D86.10D7D7F0@freenet.co.uk> from Alex at "Jan 25, 2000 10:02:46 pm" To: ak@freenet.co.uk (Alex) Date: Tue, 25 Jan 2000 23:22:45 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex wrote: > Speaking of identify failed, I get the following: > > ata-pci0: port 0xfcf0-0xfcff at device > 1.1 on pci0 > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > > ... > > ata1-slave: ata_command: timeout waiting for intr > ata1-slave: identify failed > ad0: 6194MB disk at ata0 as master mode UDMA33 > acd0: CDROM at ata1 as master mode PIO4 You need to update.. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 14:26:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 86BB31528A for ; Tue, 25 Jan 2000 14:26:09 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id RAA97734; Tue, 25 Jan 2000 17:25:41 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Tue, 25 Jan 2000 17:25:40 -0500 (EST) From: Chuck Robey To: Ilya Zakharevich Cc: Lars Eggert , perl5-porters@perl.org, current@FreeBSD.ORG Subject: Re: [ID 20000124.004] "perl in malloc(): warning: recursive call" on In-Reply-To: <20000125150945.C2011@monk.mps.ohio-state.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jan 2000, Ilya Zakharevich wrote: > On Tue, Jan 25, 2000 at 02:44:05PM -0500, Chuck Robey wrote: > > On Mon, 24 Jan 2000, Lars Eggert wrote: > > > > > Ilya, > > > > > > thanks for the quick response. > > > > > > > Signals and Perl do not mix. Please do not use signals if a segfault > > > > is not a desirable form of output. > > > > > > Never? After reading perlipc I was under the impression that using signals > > > was okay if you keep your handlers simple. I may have to use to another form > > > of IPC if signals cannot be made safe. > > > > Our malloc can't be used in a signal handler. > > One can write a signal handler in such a way that no mallocs are going > to be called (see my example). But this would not help: segfaults > will happen anyway. Do you know for a fact that perl, in the signal handler code, is not calling malloc? ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 15:57:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 81ACB152EA; Tue, 25 Jan 2000 15:57:28 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (andyf@localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id KAA17642; Wed, 26 Jan 2000 10:57:25 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Wed, 26 Jan 2000 10:57:25 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: y2k problem? naahhh... In-Reply-To: <200001251759.MAA92935@server.baldwin.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jan 2000, John Baldwin wrote: > >> Backup passwd and group files: > >> passwd diffs: > >> --- /var/backups/master.passwd.bak Wed Jan 5 10:(password):41 2000 > >> +++ /etc/master.passwd Tue Jan 25 15:(password):44 2000 > >> @@ -1,3 +1,5 @@ > >> +# $FreeBSD:(password):09:07 peter Exp $ > >> +# > >> root:(password):0:0::0:0:Charlie &:/root:/bin/csh > >> toor:(password):0:0::0:0:Bourne-again Superuser:/root: > >> daemon:(password):1:1::0:0:Owner of many system > >> processes:/root:/sbin/nologin > > > > Heh, I'd say revision 1.5 of "src/etc/periodic/daily/200.backup-passwd" > > needs a bit more work. :-) > > Doh, I tried to fix the sed expression so it would work with various diff > formats (since I, for example, prefer the old format). I guess a simple: > 'egrep -v '^(---|+++|@@)' inserted in the pipeline between the diff -u and the > sed might fix it. The $FreeBSD ID is being creamed as well. > > > John > > -- > > John Baldwin -- http://www.FreeBSD.org/~jhb/ > PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc > "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 16: 2:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7B24215006 for ; Tue, 25 Jan 2000 16:02:42 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id QAA27558; Tue, 25 Jan 2000 16:02:41 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id QAA18979; Tue, 25 Jan 2000 16:02:42 -0800 (PST) (envelope-from obrien) Date: Tue, 25 Jan 2000 16:02:42 -0800 From: "David O'Brien" To: Rajappa Iyer Cc: current@freebsd.org Subject: Re: make release failure Message-ID: <20000125160242.A18918@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200001251859.MAA28792@panther.txn.cpqcorp.net> <200001252054.PAA00478@kamikaze.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001252054.PAA00478@kamikaze.mindspring.com>; from rajappa@mindspring.com on Tue, Jan 25, 2000 at 03:54:13PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 25, 2000 at 03:54:13PM -0500, Rajappa Iyer wrote: > Yes, but $CHROOTDIR/etc is populated by "make installworld" when I do Why not just set USA_RESIDENT in your environment before starting `make release'? -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 16:31:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id D822C15434; Tue, 25 Jan 2000 16:30:40 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id TAA00209; Tue, 25 Jan 2000 19:30:38 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id TAA42220; Tue, 25 Jan 2000 19:30:08 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 25 Jan 2000 19:30:07 -0500 (EST) To: current@freebsd.org Cc: cg@freebsd.org Subject: newpcm: ESS1688, simplex problems, stuttering X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14478.15418.821563.496512@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've just upgraded my wheezing P120Mhz Dell Lattitude LM to a recent -current (Jan24 snap) & the sound *almost* works! The first problem I had was to get the card recognized. I needed to patch the sbc bridge driver to recognize the ESS 1688: Index: sys/dev/sound/isa/sbc.c =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/isa/sbc.c,v retrieving revision 1.16 diff -u -r1.16 sbc.c --- sbc.c 2000/01/12 11:16:23 1.16 +++ sbc.c 2000/01/25 04:29:06 @@ -205,6 +205,7 @@ {0x01100000, "Avance Asound 110"}, /* @@@1001 */ {0x01200000, "Avance Logic ALS120"}, /* @@@2001 */ + {0x02017316, "ESS ES1688"}, /* ESS1688 */ {0x68187316, "ESS ES1868"}, /* ESS1868 */ {0x69187316, "ESS ES1869"}, /* ESS1869 */ {0xacb0110e, "ESS ES1869 (Compaq OEM)"}, /* CPQb0ac */ The second problem I had was that this laptop gives its sound card only one DMA channel (drq 1). Newpcm seems to have horrible problems on simplex cards: The sound card is now recognized & when I run amp I don't hear any output. If I run ktrace on the amp session, it doesn't look like any writes are initiated to /dev/dsp from the child process. I don't see any interrupts on irq5 nor do I hear any sound. The problem is that in getchns() (in dsp.c), the channel is set to fakechan if the channel is simplex (eg, 1 DMA channel) and if the priority hasn't been set. It looks like SD_F_PRIO_WR is only set on the channel in dsp_write(). But apparently dsp_write() never gets called (or gets called after getchns()), so this prevents newpcm from working on a simplex channel. I have the following crude hack in place: Index: sys/dev/sound/pcm/dsp.c =================================================================== RCS file: /home/ncvs/src/sys/dev/sound/pcm/dsp.c,v retrieving revision 1.14 diff -u -r1.14 dsp.c --- dsp.c 2000/01/10 07:05:15 1.14 +++ dsp.c 2000/01/25 04:27:12 @@ -54,6 +54,8 @@ KASSERT((d->flags & SD_F_PRIO_SET) != SD_F_PRIO_SET, \ ("getchns: read and write both prioritised")); +if(!(d->flags & (SD_F_PRIO_RD | SD_F_PRIO_WR))) d->flags |= SD_F_PRIO_WR; + if (d->flags & SD_F_SIMPLEX) { *rdch = (d->flags & SD_F_PRIO_RD)? d->arec[chan] : &d->fakechan; *wrch = (d->flags & SD_F_PRIO_WR)? d->aplay[chan] : &d->fakechan; This gets me to the point where I can actually hear my laptop make noise! Unfortunately, I seem to be having the same symptoms as Nick Hibma & Donn Miller are reporting in the "pcm - stutters" thread. Since my box is dog-slow, I only hear stuttering from amp. It is a little better with RealPlayerG2, but not great. Thanks for any help! Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 16:43:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51]) by hub.freebsd.org (Postfix) with ESMTP id D69FC14DE6; Tue, 25 Jan 2000 16:41:55 -0800 (PST) (envelope-from rajappa@mindspring.com) Received: from kamikaze.mindspring.com (user-2ivea2a.dialup.mindspring.com [165.247.40.74]) by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id TAA03715; Tue, 25 Jan 2000 19:41:46 -0500 (EST) Received: (from rsi@localhost) by kamikaze.mindspring.com (8.9.3/8.9.3) id TAA47655; Tue, 25 Jan 2000 19:47:10 -0500 (EST) (envelope-from rajappa@mindspring.com) Message-Id: <200001260047.TAA47655@kamikaze.mindspring.com> X-Authentication-Warning: kamikaze.mindspring.com: rsi set sender to rajappa@mindspring.com using -f To: obrien@freebsd.org Cc: current@freebsd.org Subject: Re: make release failure References: <200001251859.MAA28792@panther.txn.cpqcorp.net> <200001252054.PAA00478@kamikaze.mindspring.com> <20000125160242.A18918@dragon.nuxi.com> From: Rajappa Iyer Date: 25 Jan 2000 19:47:09 -0500 Reply-To: rajappa@mindspring.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" writes: > On Tue, Jan 25, 2000 at 03:54:13PM -0500, Rajappa Iyer wrote: > > Yes, but $CHROOTDIR/etc is populated by "make installworld" when I do > > Why not just set USA_RESIDENT in your environment before starting > `make release'? That's certainly possible, although it might be a good idea to use a variable to point to a make.conf file. This way "make release" does not have to be too aware of what "make world" requires in /etc/make.conf. Failing that, perhaps /usr/src/release/Makefile could check for USA_RESIDENT early on to save checkouts of src, ports and docs. Rajappa -- a.k.a. Rajappa Iyer. New York, New York. We're too busy mopping the floor to turn off the faucet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 17:26:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from inet-tsb.toshiba.co.jp (inet-tsb.toshiba.co.jp [202.33.96.40]) by hub.freebsd.org (Postfix) with ESMTP id 6F1A214DB7 for ; Tue, 25 Jan 2000 17:26:30 -0800 (PST) (envelope-from shige@sitc.toshiba.co.jp) Received: from tis2.tis.toshiba.co.jp by inet-tsb.toshiba.co.jp (8.8.8/3.3W9-04/12/95) id KAA02995; Wed, 26 Jan 2000 10:26:24 +0900 (JST) Received: from mx.toshiba.co.jp by tis2.tis.toshiba.co.jp (8.8.4+2.7Wbeta4/3.3W9-95082317) id KAA18372; Wed, 26 Jan 2000 10:26:23 +0900 (JST) Received: from tas0470.sitc.toshiba.co.jp by toshiba.co.jp (8.7.1+2.6Wbeta4/3.3W9-TOSHIBA-GLOBAL SERVER) id KAA04174; Wed, 26 Jan 2000 10:26:22 +0900 (JST) Received: from athena.sitc.toshiba.co.jp.sitc.toshiba.co.jp by tas0470.sitc.toshiba.co.jp (8.9.3/sitc-1.4) with ESMTP id KAA22568; Wed, 26 Jan 2000 10:26:21 +0900 (JST) Date: Wed, 26 Jan 2000 10:26:20 +0900 Message-ID: <14478.19772.658000.78716W@athena.sitc.toshiba.co.jp> From: Shigeyuki Fukushima To: current@FreeBSD.ORG Subject: groff(troff) y2k problem User-Agent: Wanderlust/2.2.5 (Come Undone) WEMI/1.13.7 (=?ISO-2022-JP?B?GyRCRWdFRBsoQg==?=) PGPGPG FLIM/1.13.2 (=?ISO-2022-JP?B?GyRCM15LJRsoQg==?=) Emacs/20.4 (i386-*-nt5.0.2128) MULE/4.1 (=?ISO-2022-JP?B?GyRCMCobKEI=?=) Meadow/1.10 (=?ISO-2022-JP?B?GyRCTyobKEI=?=) MIME-Version: 1.0 (generated by WEMI 1.13.7 - =?ISO-2022-JP?B?IhskQkVnGyhC?= =?ISO-2022-JP?B?GyRCRUQbKEIi?=) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think, we should fix groff y2k problem before 4.0-Release time. # Also see the bottom line of `man hosts.equiv` ;), and # PRs gnu/4930, gnu/8321, bin/9502. GNU groff 1.15 has been already fixed for y2k. But groff imported in -current seems to have a y2k bug again. ;) Macros expect number register 'yr' to be the number of years since 1900. So, a fix with troff/input.cc on revision 1.2 to "perform modular division by 100 on yr number register" is harmful. The patch shown below fix this problems. ===== --- src/contrib/groff/troff/input.cc.orig Wed Jan 12 19:26:35 2000 +++ src/contrib/groff/troff/input.cc Wed Jan 26 10:19:50 2000 @@ -5558,7 +5558,7 @@ set_number_reg("dw", int(tt->tm_wday + 1)); set_number_reg("dy", int(tt->tm_mday)); set_number_reg("mo", int(tt->tm_mon + 1)); - set_number_reg("yr", int(tt->tm_year)%100); + set_number_reg("yr", int(tt->tm_year)); set_number_reg("$$", getpid()); number_reg_dictionary.define(".A", new constant_reg(ascii_output_flag ===== On the other hand, groff based on version 1.11 has had y2k bug yet on FreeBSD 3.4-RELEASE. It seems that the below patch is necessary. ===== --- src/contrib/groff/troff/input.cc.orig Sat Jul 24 09:46:32 1999 +++ src/contrib/groff/troff/input.cc Thu Jan 20 00:16:55 2000 @@ -5543,7 +5543,7 @@ set_number_reg("dw", int(tt->tm_wday + 1)); set_number_reg("dy", int(tt->tm_mday)); set_number_reg("mo", int(tt->tm_mon + 1)); - set_number_reg("yr", int(tt->tm_year)%100); + set_number_reg("yr", int(tt->tm_year)); set_number_reg("$$", getpid()); number_reg_dictionary.define(".A", new constant_reg(ascii_output_flag --- src/contrib/groff/mm/tmac.m.orig Tue May 18 12:38:35 1999 +++ src/contrib/groff/mm/tmac.m Thu Jan 20 17:38:54 2000 @@ -2620,8 +2620,8 @@ .de AE .. .\" I am planning to use mgm some time :-) -.ie \\n[yr]<50 .ds cov*new-date \\*[MO\\n[mo]] \\n[dy], 20\\n[yr] -.el .ds cov*new-date \\*[MO\\n[mo]] \\n[dy], 19\\n[yr] +.nr cov*year 1900+\n[yr] +.ds cov*new-date \*[MO\n[mo]] \n[dy], \n[cov*year] .als DT cov*new-date .de ND .ds cov*new-date \\$1 ===== --- shige To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 18:19:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 364A514E70 for ; Tue, 25 Jan 2000 18:19:34 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id VAA53639; Tue, 25 Jan 2000 21:19:16 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001260219.VAA53639@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 25 Jan 2000 21:19:16 -0500 (EST) From: John Baldwin To: Andy Farkas Subject: Re: y2k problem? naahhh... Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25-Jan-00 Andy Farkas wrote: > > On Tue, 25 Jan 2000, John Baldwin wrote: > >> >> Backup passwd and group files: >> >> passwd diffs: >> >> --- /var/backups/master.passwd.bak Wed Jan 5 10:(password):41 2000 >> >> +++ /etc/master.passwd Tue Jan 25 15:(password):44 2000 >> >> @@ -1,3 +1,5 @@ >> >> +# $FreeBSD:(password):09:07 peter Exp $ >> >> +# >> >> root:(password):0:0::0:0:Charlie &:/root:/bin/csh >> >> toor:(password):0:0::0:0:Bourne-again Superuser:/root: >> >> daemon:(password):1:1::0:0:Owner of many system >> >> processes:/root:/sbin/nologin >> > >> > Heh, I'd say revision 1.5 of "src/etc/periodic/daily/200.backup-passwd" >> > needs a bit more work. :-) >> >> Doh, I tried to fix the sed expression so it would work with various diff >> formats (since I, for example, prefer the old format). I guess a simple: >> 'egrep -v '^(---|+++|@@)' inserted in the pipeline between the diff -u and >> the >> sed might fix it. > > The $FreeBSD ID is being creamed as well. Ok then: 'egrep -v '^(---|+++|@@|[+-]#)', geez, am I the only one who knows regex? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 18:42:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 1EFF614E93 for ; Tue, 25 Jan 2000 18:41:30 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 2BCA7137F74 for ; Tue, 25 Jan 2000 21:41:25 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id VAA96090; Tue, 25 Jan 2000 21:41:24 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14478.24275.404699.65498@trooper.velocet.net> Date: Tue, 25 Jan 2000 21:41:23 -0500 (EST) To: freeBSD-current@freebsd.org Subject: scanner stopps working under stable? X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently (this morning, I believe) cvsup'd and my scanner stopped working. Usually, scanimage recognises /dev/scanner which is a link to /dev/pass4 ... which is my scanner. I noticed several interesting things. If I connect the scanner to another SCSI bus (I have two), then camcontrol rescan doesn't find new devices --- I would expect the pass device to show up (it does at boot). Another thing is the output of scanimage -L (which tries to probe the scanner): [1:7:307]dgilbert@trooper:~> scanimage -L 0: 00000000000000 ....... 0: 00000000000000 ....... 0: 00000000000000 ....... 0: 00000000000000 ....... ... I tried recompiling and reinstalling scanimage (BTW... there's a "syntax error" or two in the gimp port right now) ... but it's output didn't change. It did take slightly longer to produce the output ... I don't know if that is significant. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 20: 9:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from wireless.net (wireless.net [207.137.156.159]) by hub.freebsd.org (Postfix) with ESMTP id 589AF14C3E for ; Tue, 25 Jan 2000 20:09:33 -0800 (PST) (envelope-from dbutter@wireless.net) Received: from db.wireless.net (db.wireless.net [209.75.70.101]) by wireless.net (8.9.3/8.9.3) with ESMTP id UAA03071; Tue, 25 Jan 2000 20:22:27 -0800 (PST) Received: from dbm.wireless.net (dbm.wireless.net [192.168.0.2]) by db.wireless.net (8.9.3/8.9.3) with SMTP id UAA26781; Tue, 25 Jan 2000 20:03:04 -0800 (PST) (envelope-from dbutter@wireless.net) From: Devin Butterfield Reply-To: dbutter@wireless.net To: Donn Miller , current@FreeBSD.ORG Subject: Re: pcm - stutters Date: Tue, 25 Jan 2000 20:05:48 -0800 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <388E1C6B.489B84D2@cvzoom.net> In-Reply-To: <388E1C6B.489B84D2@cvzoom.net> MIME-Version: 1.0 Message-Id: <00012520102300.02605@dbm.wireless.net> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jan 2000, Donn Miller wrote: > Nick Hibma wrote: > > > The output of my ESS 1869 stutters whenever there is no new data fed to > > it. For example pressing Ctrl-Z, or heavy disk usage (normally making > > mpg123 jump). The stuttering is repetition of one short fragment of > > about a quarter of a second, indefinitely > > I can confirm this. Whenever there is any substantial disk activity, > the output of mpg123 starts to jump and quiver (and sometimes skip). > Why would disk activity do this? Must be an issue with bus latency, > because the ata and sound driver are trying to access the bus at the > same time. Also, it seems like certain graphics ops in XFree86 3.9.17 > make mpg123 jump and skip. Strangely, RealPlayer doesn't suffer from > these problems. I too notice these problems of mpg123 skipping during disk activity or X graphics ops but I have always had these problems, both with -STABLE and -CURRENT. I notice this with xmms too. So this is nothing new. -- Regards, Devin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 20:19: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (Postfix) with ESMTP id 1866A14C3E for ; Tue, 25 Jan 2000 20:17:39 -0800 (PST) (envelope-from fjoe@iclub.nsu.ru) Received: from localhost (fjoe@localhost) by iclub.nsu.ru (8.9.3/8.9.3) with ESMTP id KAA66799 for ; Wed, 26 Jan 2000 10:17:06 +0600 (NS) (envelope-from fjoe@iclub.nsu.ru) Date: Wed, 26 Jan 2000 10:17:05 +0600 (NS) From: Max Khon To: current@freebsd.org Subject: Re: grep --binary-files=without-match (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, there! can we merge this when it's ready before freeze? ---------- Forwarded message ---------- Date: Tue, 25 Jan 100 22:47:26 -0500 (EST) From: Alain Magloire To: Paul Eggert Cc: fjoe@iclub.nsu.ru, ru@FreeBSD.org Subject: Re: grep --binary-files=without-match Bonjour > Date: Tue, 25 Jan 2000 10:18:30 +0600 (NS) > From: Max Khon > > Sometimes I need to find all files that > contain something. Sometimes I need only text files > (e.g: vi `grep -rl xxx .` -- no binary files are desired). > > Thanks; that explains why you need a short-option equivalent to > --binary-files=without-match. Here is a proposed patch to implement > this, plus it fixes a couple of minor manual bugs I found while > documenting this. It assumes all the previous patches that I've sent > to the grep maintainer. > > 2000-01-25 Paul Eggert > > * NEWS, doc/grep.1, doc/grep.texi: Add -I option. > * src/grep.c (short_options, usage, main): Likewise. > > * doc/grep.texi: Fix some incorrect references to ASCII. Patch applied. Ruslan, there will be a beta on alpha, this weekend, grep-2.4d, I will notify you since FreeBSD'ers are the one pushing hard for the --binary-files options. -- alain To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 20:38: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from vajhost.nissho-ele.co.jp (fw.nissho-ele.co.jp [202.214.78.1]) by hub.freebsd.org (Postfix) with ESMTP id F088814C3B for ; Tue, 25 Jan 2000 20:37:58 -0800 (PST) (envelope-from shimizu@nissho-ele.co.jp) Received: from scorpion.nissho-ele.co.jp (scorpion.nissho-ele.co.jp [10.10.33.203]) by vajhost.nissho-ele.co.jp (8.9.3/3.7W-9906111656) with ESMTP id NAA22759 for ; Wed, 26 Jan 2000 13:40:51 +0900 (JST) Received: from hawk ([10.10.33.95]) by scorpion.nissho-ele.co.jp (8.9.1b+Sun/8.9.1) with SMTP id NAA17305 for ; Wed, 26 Jan 2000 13:38:14 +0900 (JST) Message-Id: <200001260438.NAA17305@scorpion.nissho-ele.co.jp> X-Sender: shimizu@nissho-ele.co.jp X-Mailer: Windows Eudora Light Version 3.0.5-Jr1 (32) Date: Wed, 26 Jan 2000 13:19:14 +0900 To: freebsd-current@freebsd.org From: Keizo Shimizu Subject: not recognize dos partition Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-2022-JP" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I made boot.flp/mfsroot.flp from 1/24/2000 snapshots. I have 50MB dos partition on top of my 20GB disk. Installing step from these stops on "Prooving Devices ..." step. Last message on console shows dos partition has founded on /dev/ad0s1, no more message shown. -- Keizo SHIMIZU ($B@6?eX*;0(B) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 21:20:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id 639A514FA2 for ; Tue, 25 Jan 2000 21:20:46 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS1-p78.rlz.netvision.net.il [62.0.168.80]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id HAA23179; Wed, 26 Jan 2000 07:20:39 +0200 (IST) Message-ID: <388E8469.322DF6AF@freenet.co.uk> Date: Wed, 26 Jan 2000 05:21:45 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: My ATAPI CD not come ready References: <200001252222.XAA83537@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > It seems Alex wrote: > > Speaking of identify failed, I get the following: > > > > ata-pci0: port 0xfcf0-0xfcff at device > > 1.1 on pci0 > > ata0 at 0x01f0 irq 14 on ata-pci0 > > ata1 at 0x0170 irq 15 on ata-pci0 > > > > ... > > > > ata1-slave: ata_command: timeout waiting for intr > > ata1-slave: identify failed > > ad0: 6194MB disk at ata0 as master mode UDMA33 > > acd0: CDROM at ata1 as master mode PIO4 > > You need to update.. OK - I've just updated. Here goes again: ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 6194MB [13424/15/63] at ata0-master using UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s2a I wouldn't be surprised if ATAPI_CMD_IDENTIFY failed on ata1-master, but why does it say ata1-slave? It's a notebook PC, so unfortunately I'm not sure how it's all connected. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 21:22:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id ABACB14DB9; Tue, 25 Jan 2000 21:22:44 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id OAA09912; Wed, 26 Jan 2000 14:22:43 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp376.kt.rim.or.jp [202.247.140.76]) by mail1.rim.or.jp (3.7W/) id OAA04305; Wed, 26 Jan 2000 14:22:42 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id OAA59200; Wed, 26 Jan 2000 14:22:41 +0900 (JST) Date: Wed, 26 Jan 2000 14:22:40 +0900 Message-ID: <14478.33952.854844.81738Z@localhost.sky.rim.or.jp> From: Jun Kuriyama To: n_hibma@FreeBSD.org To: current@FreeBSD.org Subject: panic in dev/usb/usbdi.c User-Agent: Wanderlust/1.0.3 (Notorious) SEMI/1.13.3 (Komaiko) FLIM/1.12.5 (Hirahata) MULE XEmacs/20.4 (Emerald) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found I got panic at boot time if I defined "options DIAGNOSTIC". ----- console panic: ohci_abort_req in interrput context Debugger("panic") Stopped at Debugger+0x35: movb $0,in_Debugger.354 ----- This messages is printed by usbd_do_request_flags() in line 928 of dev/usb/usbdi.c. ----- usbdi.c usbd_status usbd_do_request_flags(dev, req, data, flags, actlen) usbd_device_handle dev; usb_device_request_t *req; void *data; u_int16_t flags; int *actlen; { usbd_xfer_handle xfer; usbd_status err; #ifdef DIAGNOSTIC #if defined(__i386__) && defined(__FreeBSD__) KASSERT(intr_nesting_level == 0, ("ohci_abort_req in interrupt context")); #endif if (dev->bus->intr_context) { printf("usbd_do_request: not in process context\n"); return (USBD_INVAL); } #endif ----- I cannot get coredump for this session. Non-DIAGNOSTIC'ed kernel dmesg is here: ----- dmesg uhci0: port 0xfcc0-0xfcdf irq 9 at dev ice 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered aue0: LUA-TX MELCO LUA-TX, rev 1.10/1.01, addr 2 aue0: Ethernet address: 00:40:26:61:10:c7 miibus0: on aue0 ukphy0: on miibus0 ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto aue0: supplying EUI64: 00:40:26:ff:fe:61:10:c7 ----- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 21:23:25 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 8BBEB14D86; Tue, 25 Jan 2000 21:23:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7A73E1CD66D; Tue, 25 Jan 2000 21:23:23 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Tue, 25 Jan 2000 21:23:23 -0800 (PST) From: Kris Kennaway To: keramida@ceid.upatras.gr Cc: current@FreeBSD.ORG Subject: Re: ipfilter and ipfstat In-Reply-To: <20000125051418.A62880@charon.hell.gr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jan 2000, the Webslave wrote: > > Okay, so I finally decided to take the plunge and check out ipfilter. ipf > > seemed to load my ruleset with no problems, but ipfstat dies with: > > > > ioctl(SIOCGETFS): Invalid argument > > And what would that ruleset be? > # Default to deny block in log on tun0 from any to any # Block unroutables block in quick on tun0 from 192.168.0.0/16 to any block in quick on tun0 from 172.16.0.0/12 to any block in quick on tun0 from 10.0.0.0/8 to any block in quick on tun0 from 127.0.0.0/8 to any # Allow us to initiate any outgoing connections pass out quick on tun0 proto tcp/udp from any to any keep state pass out quick on tun0 proto icmp from any to any keep state # Allow incoming trojans pass in quick on tun0 proto tcp from any to any port = 12345 flags S keep state keep frags pass in quick on tun0 proto udp from any to any port = 31337 keep state # Allow loopback pass out quick on lo0 pass in quick on lo0 Note that I haven't been able to test this ruleset for legitimacy yet because I can't interface with ipfstat :-) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 21:38:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id BAAAB14D50 for ; Tue, 25 Jan 2000 21:38:12 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id WAA29350; Tue, 25 Jan 2000 22:38:01 -0700 (MST) Received: from ip-83-104.prc.primenet.com(207.218.83.104), claiming to be "pinyon.org" via SMTP by smtp01.primenet.com, id smtpdAAA3maaq5; Tue Jan 25 22:37:53 2000 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id 6EBC072; Wed, 26 Jan 2000 13:37:22 -0700 (MST) X-Mailer: exmh version 2.1.0 09/18/1999 To: "Rodney W. Grimes" Cc: rcarter@pinyon.org (Russell L. Carter), sos@freebsd.dk (Soren Schmidt), current@FreeBSD.ORG, rcarter@pinyon.org Subject: Re: FIC SD-11 not happy with ata In-Reply-To: Message from "Rodney W. Grimes" of "Tue, 18 Jan 2000 21:37:43 PST." <200001190537.VAA50862@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Jan 2000 13:37:21 -0700 From: "Russell L. Carter" Message-Id: <20000126203722.6EBC072@pinyon.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %> %It seems Russell L. Carter wrote: %> %> %It seems Russell L. Carter wrote: %> %> %> %> %> %> I swapped out my motherboard and am seeing this now: %... % %> %> )(*&$#%$# stupid magazine benchmarkers never actually test %> things like IO... grrrrr.... % %We in the computer hardware business have a better name for ``FIC'', %Fix It Continuously. They are not known for their quality, or should %I say they are known for their lack of quality :-). How about FIO: Fix it Once. I swapped in an ASUS K7 and now everything is back to normal: ata-pci0: port 0xffa0-0xffaf at device 4.1 on pci 0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 [...] ad0: ATA-4 disk at ata0 as master ad0: 13783MB (28229040 sectors), 28005 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 32 depth queue, UDMA33 ad1: ATA-4 disk at ata1 as master ad1: 19574MB (40088160 sectors), 39770 cyls, 16 heads, 63 S/T, 512 B/S ad1: 16 secs/int, 32 depth queue, UDMA66 I've been hammering the drives and so far no fallback. Still to go is a bonnie check. Regards, Russell % %-- %Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net % % %To Unsubscribe: send mail to majordomo@FreeBSD.org %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 21:49:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 82C4B14F32 for ; Tue, 25 Jan 2000 21:49:55 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA72834; Tue, 25 Jan 2000 21:49:45 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001260549.VAA72834@gndrsh.dnsmgr.net> Subject: Re: FIC SD-11 not happy with ata In-Reply-To: <20000126203722.6EBC072@pinyon.org> from "Russell L. Carter" at "Jan 26, 2000 01:37:21 pm" To: rcarter@pinyon.org (Russell L. Carter) Date: Tue, 25 Jan 2000 21:49:45 -0800 (PST) Cc: sos@freebsd.dk (Soren Schmidt), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > %> %It seems Russell L. Carter wrote: > %> %> %It seems Russell L. Carter wrote: > %> %> %> > %> %> %> I swapped out my motherboard and am seeing this now: > %... > % > %> > %> )(*&$#%$# stupid magazine benchmarkers never actually test > %> things like IO... grrrrr.... > % > %We in the computer hardware business have a better name for ``FIC'', > %Fix It Continuously. They are not known for their quality, or should > %I say they are known for their lack of quality :-). > > How about FIO: Fix it Once. I swapped in an ASUS K7 and now everything > is back to normal: I thought we had protected our tradesecret on how to fix the FIC problem, seems someone else figured it out too :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 22:30:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 8805F14E05 for ; Tue, 25 Jan 2000 22:30:14 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 15500 invoked from network); 26 Jan 2000 06:30:12 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 26 Jan 2000 06:30:12 -0000 Date: Wed, 26 Jan 2000 17:30:10 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Brian Beattie Cc: current@FreeBSD.ORG Subject: Re: building modules In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jan 2000, Brian Beattie wrote: > I'm trying to figure out how to make a makefile to build a module and have > run into something I do not understand. I am working with freshly > cvsup'ed sources. > > When I try to build a module in /sys/modules, the command line contains a > -DKERNEL, which I find in bsd.kmod.mk. This causes the wrong definitions Your bsd.kmod.mk (maybe the installed one) is out of date. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 23:13:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta2.snfc21.pbi.net (mta2.snfc21.pbi.net [206.13.28.123]) by hub.freebsd.org (Postfix) with ESMTP id 7256014C34 for ; Tue, 25 Jan 2000 23:13:10 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.249]) by mta2.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOX00FCLL8QEZ@mta2.snfc21.pbi.net> for current@freebsd.org; Tue, 25 Jan 2000 23:10:03 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 6FADC9163B for ; Tue, 25 Jan 2000 23:10:02 -0800 (PST) Date: Tue, 25 Jan 2000 23:10:02 -0800 (PST) From: Alex Zepeda Subject: Speaking of ATAisms... To: current Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't been able to mount an msdos (FAT16) formattted zip disk (well any FAT16 formatted zip disk) for quite a while. Currently I'm trying to mount afd0s4, but no such luck (I think the latest error is something about reading the partition table). The wd driver used to grok the same disks. Any thoughts? P.S. Soren, thanks for the burncd program. So far I've had more luck with it than the Adaptec s/w that came with the drive. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 23:22: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id 903A514EFE for ; Tue, 25 Jan 2000 23:20:53 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id IAA29193; Wed, 26 Jan 2000 08:20:50 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <388EA051.F6DC479B@fernuni-hagen.de> Date: Wed, 26 Jan 2000 08:20:49 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 Cc: current@FreeBSD.ORG Subject: Re: My ATAPI CD not come ready, (.. and no sound with cmi8330) References: <200001252222.XAA83537@freebsd.dk> <388E8469.322DF6AF@freenet.co.uk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Last weekend i tried patches from Soren Schmidt to reactivate my old cdrom which went away after the ata-update around the 18. January. This patches completely broke ata support for me (that means the kernel did not boot anymore). Of course i reported this one or two days later. Now an equivalent variant (while loop instead of goto in ata_getparam , ata-all.c,v 1.43) is committed and surprise, the new kernel does not boot anymore. The following i had to write down to paper: ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed ata0-master: timeout waiting to give command=ec s=90 e=00 ata0-master: identify failed .... no way to mount root .. After booting with a 17. January-Kernel i reverted the retry logic in ata_getparam and had a kernel that booted again but did not recognize my cdrom drive, here are lines from dmesg (some lines show detection of the on board soundcard but this is not related to it, i get the same result when i patch sound/isa/mss.c and sound/isa/sbc.c to switch the card to sb-mode): Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (262.36-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 .... ata-pci0: port 0x4000-0x400f,0x2000-0x2003,0x80400000-0x80400007,\ 0xcc880a4-0xcc880a7,0x2143200-0x2143207 \ irq 0 at device 1.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 .... pcm0: at port 0x530-0x537,0x388-0x38f irq 5 drq 0 on isa0 device_probe_and_attach: pcm0 attach returned 6 unknown0: at port 0x330-0x331 irq 9 on isa0 unknown1: at port 0x200-0x207 on isa0 unknown2: at port 0x220-0x22f irq 10 drq 1,5 on isa0 and now the failure in detection of the ata0-slave: ata_command(scp, device, command, 0, 0, 0, 0, 0, ATA_WAIT_INTR) returned with 0, but ata_wait(scp, device, ATA_S_READY|ATA_S_DSC|ATA_S_DRQ) returned with nonzero value, and so ata_getparam with -1. At last ad0 was made successfully: ad0: 14664MB disk at ata0 as master mode UDMA33 -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 23:30:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 1E77A150EA for ; Tue, 25 Jan 2000 23:30:10 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA90373; Wed, 26 Jan 2000 08:29:45 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001260729.IAA90373@freebsd.dk> Subject: Re: My ATAPI CD not come ready, (.. and no sound with cmi8330) In-Reply-To: <388EA051.F6DC479B@fernuni-hagen.de> from "F. Heinrichmeyer" at "Jan 26, 2000 08:20:49 am" To: fritz.heinrichmeyer@fernuni-hagen.de (F. Heinrichmeyer) Date: Wed, 26 Jan 2000 08:29:45 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems F. Heinrichmeyer wrote: > Last weekend i tried patches from Soren Schmidt to reactivate my old > cdrom which went away after the ata-update around the 18. January. This > patches completely broke ata support for me (that means the kernel did > not boot anymore). Of course i reported this one or two days later. I was under the impression that it was something else that caused it not to boot, you didn't tell me back then it was because of the ata driver, oh well... > Now an equivalent variant (while loop instead of goto in ata_getparam , > ata-all.c,v 1.43) is committed and surprise, the new kernel does not > boot anymore. I suggest you try out the 1.44 version that has been committed since and let me know what that brings. At any rate I'd be interested in a full verbose dmesg from the machine... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 23:31:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7A30F14D02 for ; Tue, 25 Jan 2000 23:31:24 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA90753; Wed, 26 Jan 2000 08:31:21 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001260731.IAA90753@freebsd.dk> Subject: Re: My ATAPI CD not come ready In-Reply-To: <388E8469.322DF6AF@freenet.co.uk> from Alex at "Jan 26, 2000 05:21:45 am" To: ak@freenet.co.uk (Alex) Date: Wed, 26 Jan 2000 08:31:21 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex wrote: > > You need to update.. > > > OK - I've just updated. Here goes again: > > ata1-slave: ata_command: timeout waiting for intr > ata1-slave: identify failed > ad0: 6194MB [13424/15/63] at ata0-master using > UDMA33 > acd0: CDROM at ata1-master using PIO4 > Mounting root from ufs:/dev/ad0s2a > I wouldn't be surprised if ATAPI_CMD_IDENTIFY failed on ata1-master, but > why does it say ata1-slave? It's a notebook PC, so unfortunately I'm > not sure how it's all connected. Apparently it thinks something is there, could you mail me a complete verbose bootlog (dmesg) please, and I'll try to figure out what is going wrong.. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 23:38:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0471D14CC0 for ; Tue, 25 Jan 2000 23:38:52 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA92513; Wed, 26 Jan 2000 08:38:47 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001260738.IAA92513@freebsd.dk> Subject: Re: Speaking of ATAisms... In-Reply-To: from Alex Zepeda at "Jan 25, 2000 11:10:02 pm" To: jazepeda@pacbell.net (Alex Zepeda) Date: Wed, 26 Jan 2000 08:38:47 +0100 (CET) Cc: current@FreeBSD.ORG (current) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex Zepeda wrote: > I haven't been able to mount an msdos (FAT16) formattted zip disk (well > any FAT16 formatted zip disk) for quite a while. Currently I'm trying to > mount afd0s4, but no such luck (I think the latest error is something > about reading the partition table). The wd driver used to grok the same > disks. Any thoughts? I still have that on my list, but I've not gotten down to it yet, sorry... > P.S. Soren, thanks for the burncd program. So far I've had more luck > with it than the Adaptec s/w that came with the drive. Glad to hear that _something_ works :) -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 23:45:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id 789CA14CD3 for ; Tue, 25 Jan 2000 23:45:32 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.249]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOX00859MP2T8@mta1.snfc21.pbi.net> for current@FreeBSD.ORG; Tue, 25 Jan 2000 23:41:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 1C9309163B; Tue, 25 Jan 2000 23:41:26 -0800 (PST) Date: Tue, 25 Jan 2000 23:41:26 -0800 (PST) From: Alex Zepeda Subject: Re: Speaking of ATAisms... In-reply-to: <200001260738.IAA92513@freebsd.dk> To: Soren Schmidt Cc: current Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000, Soren Schmidt wrote: > I still have that on my list, but I've not gotten down to it yet, sorry... Well as long as I've got the wd driver, I'm fine. Anything in perticular where I might be able to help in fixing this? > > P.S. Soren, thanks for the burncd program. So far I've had more luck > > with it than the Adaptec s/w that came with the drive. > > Glad to hear that _something_ works :) Well I haven't updated my kernel yet. *grin* - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 23:48:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 5E39314DAF for ; Tue, 25 Jan 2000 23:48:11 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA94712; Wed, 26 Jan 2000 08:48:08 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001260748.IAA94712@freebsd.dk> Subject: Re: Speaking of ATAisms... In-Reply-To: from Alex Zepeda at "Jan 25, 2000 11:41:26 pm" To: jazepeda@pacbell.net (Alex Zepeda) Date: Wed, 26 Jan 2000 08:48:08 +0100 (CET) Cc: current@FreeBSD.ORG (current) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex Zepeda wrote: > On Wed, 26 Jan 2000, Soren Schmidt wrote: > > > I still have that on my list, but I've not gotten down to it yet, sorry... > > Well as long as I've got the wd driver, I'm fine. > > Anything in perticular where I might be able to help in fixing this? You could try to do a dd of the first say 2 cyls of the ZIP with both drivers and check is they are different, they shouldn't be... > > > P.S. Soren, thanks for the burncd program. So far I've had more luck > > > with it than the Adaptec s/w that came with the drive. > > > > Glad to hear that _something_ works :) > > Well I haven't updated my kernel yet. *grin* Yeah, progress does have its victims :) -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Jan 25 23:59:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id E015A1513E for ; Tue, 25 Jan 2000 23:59:18 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.249]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOX00B7INE9AV@mta1.snfc21.pbi.net> for current@FreeBSD.ORG; Tue, 25 Jan 2000 23:56:34 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 2F53C9163B; Tue, 25 Jan 2000 23:56:33 -0800 (PST) Date: Tue, 25 Jan 2000 23:56:33 -0800 (PST) From: Alex Zepeda Subject: Re: Speaking of ATAisms... In-reply-to: <200001260748.IAA94712@freebsd.dk> To: Soren Schmidt Cc: current Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000, Soren Schmidt wrote: > You could try to do a dd of the first say 2 cyls of the ZIP with > both drivers and check is they are different, they shouldn't be... How many bytes is this again? > > Well I haven't updated my kernel yet. *grin* > > Yeah, progress does have its victims :) Progress is indeed overrated. I wanna play mp3s through the pca device! ;) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 0:17:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id B2F2E1511E for ; Wed, 26 Jan 2000 00:17:36 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA01531; Wed, 26 Jan 2000 09:16:44 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001260816.JAA01531@freebsd.dk> Subject: Re: Speaking of ATAisms... In-Reply-To: from Alex Zepeda at "Jan 25, 2000 11:56:33 pm" To: jazepeda@pacbell.net (Alex Zepeda) Date: Wed, 26 Jan 2000 09:16:44 +0100 (CET) Cc: current@FreeBSD.ORG (current) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex Zepeda wrote: > On Wed, 26 Jan 2000, Soren Schmidt wrote: > > > You could try to do a dd of the first say 2 cyls of the ZIP with > > both drivers and check is they are different, they shouldn't be... > > How many bytes is this again? Erhm, I've forgotten the geometry of the zip, just be sure to have the first two tracks. > > > > Well I haven't updated my kernel yet. *grin* > > > > Yeah, progress does have its victims :) > > Progress is indeed overrated. > > I wanna play mp3s through the pca device! ;) Wow! I havn't used the pca dev in years, but it should work I guess given the right bitrates etc :) -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 0:47: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by hub.freebsd.org (Postfix) with ESMTP id 7299C1541D for ; Wed, 26 Jan 2000 00:46:58 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.249]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FOX00533PDYHX@mta4.snfc21.pbi.net> for current@FreeBSD.ORG; Wed, 26 Jan 2000 00:39:40 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 63D67918CF; Wed, 26 Jan 2000 00:39:34 -0800 (PST) Date: Wed, 26 Jan 2000 00:39:34 -0800 (PST) From: Alex Zepeda Subject: Re: Speaking of ATAisms... In-reply-to: <200001260816.JAA01531@freebsd.dk> To: Soren Schmidt Cc: current Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000, Soren Schmidt wrote: > Erhm, I've forgotten the geometry of the zip, just be sure to have > the first two tracks. [counting on fingers, then toes, then kunckles ensues] afd0: 96MB (196608 sectors), 96 cyls, 64 heads, 32 S/T, 512 B/S first 16k? zippy:~#dd if=/dev/afd0c bs=1k count=16 of=afd0c.output dd: /dev/afd0c: Input/output error zippy:~#Jan 26 00:38:32 zippy /kernel: afd0: error reading primary partition table reading fsbn 0 Hmm. I know this disk works with Windows 98SE. /me goes off and compiles a kernel with the wd driver instead - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 0:54:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 73D741540E; Wed, 26 Jan 2000 00:54:13 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id KAA65575; Wed, 26 Jan 2000 10:53:55 +0200 (EET) (envelope-from ru) Date: Wed, 26 Jan 2000 10:53:54 +0200 From: Ruslan Ermilov To: Jordan Hubbard Cc: Max Khon , current@FreeBSD.org Subject: Re: grep --binary-files=without-match (fwd) Message-ID: <20000126105354.C55257@relay.ucb.crimea.ua> Mail-Followup-To: Jordan Hubbard , Max Khon , current@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Max Khon on Wed, Jan 26, 2000 at 10:17:05AM +0600 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 26, 2000 at 10:17:05AM +0600, Max Khon wrote: > hi, there! > > can we merge this when it's ready before freeze? > Of course, if Jordan approves. This will be a pretty small diff. Jordan? > ---------- Forwarded message ---------- > Date: Tue, 25 Jan 100 22:47:26 -0500 (EST) > From: Alain Magloire > To: Paul Eggert > Cc: fjoe@iclub.nsu.ru, ru@FreeBSD.org > Subject: Re: grep --binary-files=without-match > > Bonjour > > > Date: Tue, 25 Jan 2000 10:18:30 +0600 (NS) > > From: Max Khon > > > > Sometimes I need to find all files that > > contain something. Sometimes I need only text files > > (e.g: vi `grep -rl xxx .` -- no binary files are desired). > > > > Thanks; that explains why you need a short-option equivalent to > > --binary-files=without-match. Here is a proposed patch to implement > > this, plus it fixes a couple of minor manual bugs I found while > > documenting this. It assumes all the previous patches that I've sent > > to the grep maintainer. > > > > 2000-01-25 Paul Eggert > > > > * NEWS, doc/grep.1, doc/grep.texi: Add -I option. > > * src/grep.c (short_options, usage, main): Likewise. > > > > * doc/grep.texi: Fix some incorrect references to ASCII. > > Patch applied. > Ruslan, there will be a beta on alpha, this weekend, grep-2.4d, I will > notify you since FreeBSD'ers are the one pushing hard for the > --binary-files options. > > -- > alain > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 1: 4:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id F3A4414EFB for ; Wed, 26 Jan 2000 01:04:19 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id KAA12586; Wed, 26 Jan 2000 10:04:03 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001260904.KAA12586@freebsd.dk> Subject: Re: Speaking of ATAisms... In-Reply-To: from Alex Zepeda at "Jan 26, 2000 00:39:34 am" To: jazepeda@pacbell.net (Alex Zepeda) Date: Wed, 26 Jan 2000 10:04:03 +0100 (CET) Cc: current@FreeBSD.ORG (current) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex Zepeda wrote: > On Wed, 26 Jan 2000, Soren Schmidt wrote: > > > Erhm, I've forgotten the geometry of the zip, just be sure to have > > the first two tracks. > > [counting on fingers, then toes, then kunckles ensues] > > afd0: 96MB (196608 sectors), 96 cyls, 64 heads, 32 S/T, 512 B/S > > first 16k? Make that 2M just to be sure.. > zippy:~#dd if=/dev/afd0c bs=1k count=16 of=afd0c.output > dd: /dev/afd0c: Input/output error > zippy:~#Jan 26 00:38:32 zippy /kernel: afd0: error reading primary > partition table reading fsbn 0 > > Hmm. I know this disk works with Windows 98SE. Well, if it has problems with the partitions you should use /dev/afd0 and /dev/wfd0. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 3: 1:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id EBAFA15158 for ; Wed, 26 Jan 2000 03:01:12 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup2-49.iptelecom.net.ua [212.9.226.113]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id NAA23971; Wed, 26 Jan 2000 13:06:55 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id NAA08145; Wed, 26 Jan 2000 13:00:33 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <388ED3C9.4B20E139@altavista.net> Date: Wed, 26 Jan 2000 13:00:25 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: John LoVerso Cc: Alex Zepeda , freebsd-current@FreeBSD.ORG Subject: Re: bzip2 in src tree References: <388DCF1F.19385402@infolibria.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John LoVerso wrote: > > Again, lemmie get on my soap box, and ask have you looked at the man page, > > and compared the memory required when using -s to the memory required by > > gzip? > > Actually, lemmie get on my soap box and ask have you measured the time that > bunzip2 takes to run? While it does give better compression in many cases, it > is just too SLOW. Using "-s" on decompression just makes it slower. > > I played on a test machine (PII 233MHz 192Mb, spare ST34502LW disk) with some > large package binaries: > [...] > A decompression time of 13 seconds vs. 67 seconds (or 125 seconds with "-s). > Given that ports and packages need a multi-CD anyway, I don't think the speed > penalty of bzip2 is worth it. All this apply only when download cost is not considered. IMHO it is clean that CPU time nowadays is much less expensive than the online time, at least for dialup connections. Also you should take into consideration that usually you packing package ONCE, while number of users downloading this package could be very huge, so online costs savings from decreased download time multiplied by the number of downloads and divided by the costs associated with required CPU time increase will be considerable. -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 3:32:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 50F6414A1F for ; Wed, 26 Jan 2000 03:32:19 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id LAA55027 for ; Wed, 26 Jan 2000 11:03:18 GMT (envelope-from n_hibma@webweaving.org) Date: Wed, 26 Jan 2000 11:03:18 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List Subject: USB on SMP Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've had reports that a machine having USB compiled into an SMP kernel panics. Could someone try the current version of the kernel and see what that brings. Don't plug in any device, that will panic your system for sure (I am working on that one). If init of the OHCI driver fails it should now clean up after itself properly. Cheers, Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 3:33:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from cichlids.com (pC19F544C.dip0.t-ipconnect.de [193.159.84.76]) by hub.freebsd.org (Postfix) with ESMTP id 178EC1508F for ; Wed, 26 Jan 2000 03:33:24 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id BD938AB95; Wed, 26 Jan 2000 12:34:16 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id MAA05239; Wed, 26 Jan 2000 12:33:45 +0100 (CET) (envelope-from alex) Date: Wed, 26 Jan 2000 12:33:45 +0100 From: Alexander Langer To: Rajappa Iyer Cc: current@FreeBSD.ORG Subject: Re: make release failure Message-ID: <20000126123345.A5176@cichlids.cichlids.com> Mail-Followup-To: Rajappa Iyer , current@FreeBSD.ORG References: <200001251859.MAA28792@panther.txn.cpqcorp.net> <200001252054.PAA00478@kamikaze.mindspring.com> <20000125160242.A18918@dragon.nuxi.com> <200001260047.TAA47655@kamikaze.mindspring.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001260047.TAA47655@kamikaze.mindspring.com>; from rajappa@mindspring.com on Tue, Jan 25, 2000 at 07:47:09PM -0500 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Rajappa Iyer (rajappa@mindspring.com): > That's certainly possible, although it might be a good idea to use a > variable to point to a make.conf file. This way "make release" does > not have to be too aware of what "make world" requires in > /etc/make.conf. though a make release in any case should contain sendmail, as an example, and so far if you have NO_SENDMAIL in your /etc/make.conf it's somehow bad. Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 4:37:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout0.freenet.de (mout0.freenet.de [194.97.50.131]) by hub.freebsd.org (Postfix) with ESMTP id B04EB14EDC for ; Wed, 26 Jan 2000 04:37:35 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.6] (helo=mx0.01019freenet.de) by mout0.freenet.de with esmtp (Exim 3.13 #1) id 12DRhS-0004JK-00; Wed, 26 Jan 2000 13:37:30 +0100 Received: from [213.6.57.196] (helo=Magelan.Leidinger.net) by mx0.01019freenet.de with esmtp (Exim 3.13 #1) id 12DRhN-0006Sq-00; Wed, 26 Jan 2000 13:37:28 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id MAA41212; Wed, 26 Jan 2000 12:09:22 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200001261109.MAA41212@Magelan.Leidinger.net> Date: Wed, 26 Jan 2000 12:09:21 +0100 (CET) From: Alexander Leidinger Subject: Re: Speaking of ATAisms... To: jazepeda@pacbell.net Cc: current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 25 Jan, Alex Zepeda wrote: > I haven't been able to mount an msdos (FAT16) formattted zip disk (well > any FAT16 formatted zip disk) for quite a while. Currently I'm trying to > mount afd0s4, but no such luck (I think the latest error is something > about reading the partition table). The wd driver used to grok the same > disks. Any thoughts? As a workaround use mtools (it's faster than msdosfs anyway [at least I noticed this with wfd]). mtools.conf: ---snip--- drive z: file="/dev/afd0s4" partition=4 ---snip--- ^^^^^^^^^^^ This is important. Bye, Alexander. -- A PBS mind in an MTV world. http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 6:34:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 00BA714D9F; Wed, 26 Jan 2000 06:34:54 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id XAA13206; Wed, 26 Jan 2000 23:33:47 +0900 (JST) From: kuriyama@sky.rim.or.jp Received: from rhea.sky.rim.or.jp (ppp366.kt.rim.or.jp [202.247.140.66]) by mail1.rim.or.jp (3.7W/) id XAA24950; Wed, 26 Jan 2000 23:34:52 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id XAA02969; Wed, 26 Jan 2000 23:34:48 +0900 (JST) Date: Wed, 26 Jan 2000 23:34:24 +0900 Message-ID: <867lgwx5ov.wl@localhost.sky.rim.or.jp> To: n_hibma@FreeBSD.org, wpaul@FreeBSD.org.current@FreeBSD.org Subject: Re: panic in dev/usb/usbdi.c In-Reply-To: In your message of "Wed, 26 Jan 2000 14:22:40 +0900" <14478.33952.854844.81738Z@localhost.sky.rim.or.jp> References: <14478.33952.854844.81738Z@localhost.sky.rim.or.jp> User-Agent: Wanderlust/2.2.15 (More Than Words) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I copied stack trace. But this is handmade copy from console, so arguments are omitted, sorry. ----- panic() usbd_do_request_flags() csr_write_1() aue_miibus_readreg() MIIBUS_READREG() miibus_readreg() MIIBUS_READREG() ukphy_service() mii_tick() softclock() doreti_swi() link_elf_lookup_symbol() kldsym() syscall() Xint0x80_syscall() ----- Jun Kuriyama To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 7:18:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from ckmso1.proxy.att.com (ckmso1.att.com [12.20.58.69]) by hub.freebsd.org (Postfix) with ESMTP id 9822314ECA; Wed, 26 Jan 2000 07:18:15 -0800 (PST) (envelope-from myevmenkin@att.com) Received: from njb140r1.ems.att.com ([135.65.202.58]) by ckmso1.proxy.att.com (AT&T IPNS/MSO-2.2) with ESMTP id KAA13574; Wed, 26 Jan 2000 10:18:02 -0500 (EST) Received: from njb140bh1.ems.att.com by njb140r1.ems.att.com (8.8.8+Sun/ATTEMS-1.4.1 sol2) id KAA13673; Wed, 26 Jan 2000 10:17:28 -0500 (EST) Received: by njb140bh1.ems.att.com with Internet Mail Service (5.5.2448.0) id ; Wed, 26 Jan 2000 10:18:01 -0500 Message-ID: From: "Yevmenkin, Maksim N, CSCIO" To: "'Bruce Evans'" Cc: "'freebsd-current@freebsd.org'" , "'freebsd-hackers@freebsd.org'" Subject: RE: BPF bug or not? Date: Wed, 26 Jan 2000 10:17:53 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce, [...] > > I've just found that read from /dev/bpfX never return > EAGAIN/EWOULDBLOCK. > > It means that when you do a non blocking read and there is > no data you will > > always get 0. > > > > Does it suppose work this way? > > I think it is a bug. Perhaps applications depend on it. > > Untested fix: [ untested fix removed :) ] Yes, it works. But it returns EAGAIN for both O_RDONLY|O_NONBLOCK and O_RDWR|O_NONBLOCK open modes. In the same time pipe returns 0 for O_RDONLY|O_NONBLOCK mode and EAGAIN for O_RDWR|O_NONBLOCK. It there any specs for "read" system call? I have small problem with blocking read in pthreads under 3.X. Since blocking read implemented as non-blocking inside pthread (libc_r to be honest), returning 0 instead of EAGAIN from read confuses libc_r. It expects EAGAIN. BTW such "blocking" read inside thread gives almost 100% CPU utilization :( thanks, emax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 7:35:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 9344214E99 for ; Wed, 26 Jan 2000 07:35:34 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (cm-208-138-47-186.cableco-op.ispchannel.com [208.138.47.186]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id HAA67183 for ; Wed, 26 Jan 2000 07:35:33 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <388F1444.FA4629A4@MexComUSA.net> Date: Wed, 26 Jan 2000 07:35:32 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: This morning's make world. References: <200001261346.FAA71041@local-1.local.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This morning's make world > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc/../libc/net/nsap_addr.c -o nsap_addr.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc/../libc/net/rcmd.c -o rcmd.o > /usr/src/lib/libc/../libc/net/rcmd.c: In function `rresvport_af': > /usr/src/lib/libc/../libc/net/rcmd.c:337: too many arguments to function `bindresvport_sa' > *** Error code 1 > > Stop in /usr/src/lib/libc. > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. Thanks, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 7:56:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mercury.gfit.net (ns.gfit.net [209.41.124.90]) by hub.freebsd.org (Postfix) with ESMTP id CE8AF15001 for ; Wed, 26 Jan 2000 07:56:43 -0800 (PST) (envelope-from tom@embt.com) Received: from PARANOR (timembt.iinc.com [206.67.169.229]) by mercury.gfit.net (8.8.8/8.8.8) with SMTP id KAA18087; Wed, 26 Jan 2000 10:04:35 -0600 (CST) (envelope-from tom@embt.com) Message-Id: <3.0.3.32.20000126105625.00f98098@mail.embt.com> X-Sender: tembt@mail.embt.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 26 Jan 2000 10:56:25 -0500 To: Soren Schmidt From: Tom Embt Subject: Re: My ATAPI CD not come ready Cc: freebsd-current@freebsd.org In-Reply-To: <200001252101.WAA83248@freebsd.dk> References: <3.0.3.32.20000125155655.00f8a1b8@mail.embt.com> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 22:01 01/25/2000 +0100, you wrote: >It seems Tom Embt wrote: >> Don't mean to butt in here, I haven't really been following the thread - >> but I may have found a workaround/clue. I have a Sony CDU-55E (ooold 2x) >> on secondary master of the PIIX4 on my BP6. By going into the BIOS (the >> section of it where you would set CHS numbers, LBA, etc) and changing the >> secondary master device from "none" to "auto", I have gone from: >>=20 >> BTW, this was on a kernel from around 20:00 GMT Jan 25 > >Interesting... > >What version is you ata-all.c ?? its damn close to the commit I just >made, that should fix that problem... > >-S=F8ren > That was with 1.43 I just updated all the files in /usr/src/sys/dev/ata (ata-all.c v1.44) and made a new kernel. While rebooting I set the BIOS back to "none" and watched FreeBSD boot. No error :) - then I rebooted to kernel.old (1.43) without touching the BIOS and the error came back. Looks like you got it. Tom Embt tom@embt.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 8:21:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 4CED6150CB for ; Wed, 26 Jan 2000 08:21:26 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12DVBt-00041Y-00; Wed, 26 Jan 2000 18:21:09 +0200 From: Sheldon Hearn To: Edwin Culp Cc: "current@FreeBSD.ORG" Subject: Re: This morning's make world. In-reply-to: Your message of "Wed, 26 Jan 2000 07:35:32 PST." <388F1444.FA4629A4@MexComUSA.net> Date: Wed, 26 Jan 2000 18:21:09 +0200 Message-ID: <15461.948903669@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000 07:35:32 PST, Edwin Culp wrote: > This morning's make world What are you trying to achieve with these e-mail messages? If you're looking for confirmation that ``make world'' is broken, then "Yes, it is." :-) And then when you get past _that_, you'll break in the includes, for which Peter Wemm posted a tentative fix which doesn't work 100%. :-) Watch your cvs-all mail for a commit on src/include/Makefile (something more recent than rev 1.107) and try again once you've got that. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 8:29:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 0182E15001 for ; Wed, 26 Jan 2000 08:29:05 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12DVFl-00062d-00; Wed, 26 Jan 2000 18:25:09 +0200 From: Sheldon Hearn To: Grigory Kljuchnikov Cc: current@FreeBSD.org Subject: Re: How can I use current release of FreeBSD? In-reply-to: Your message of "Tue, 25 Jan 2000 15:27:13 +0300." Date: Wed, 26 Jan 2000 18:25:09 +0200 Message-ID: <23226.948903909@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jan 2000 15:27:13 +0300, Grigory Kljuchnikov wrote: > How can I update 4.0-20000110 directoty tree to 4.0-20000124? > And how do these updates do properly? Where can I see more about this? The short answer is that you don't. Just wait for 4.0-RELEASE to come out in a few weeks. The long answer is contained in the FreeBSD Handbook, available online at: http://www.freebsd.org/handbook/ In particular, see the section titled The Cutting Edge: FreeBSD-current and FreeBSD-stable Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 8:36:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 2198214CA1; Wed, 26 Jan 2000 08:36:25 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12DVQX-0006q1-00; Wed, 26 Jan 2000 18:36:17 +0200 From: Sheldon Hearn To: John Baldwin Cc: Andy Farkas , current@FreeBSD.ORG Subject: Re: y2k problem? naahhh... In-reply-to: Your message of "Tue, 25 Jan 2000 21:19:16 EST." <200001260219.VAA53639@server.baldwin.cx> Date: Wed, 26 Jan 2000 18:36:17 +0200 Message-ID: <26288.948904577@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 25 Jan 2000 21:19:16 EST, John Baldwin wrote: > Ok then: > > 'egrep -v '^(---|+++|@@|[+-]#)', geez, am I the only one who knows regex? Are you the only person who doesn't know sed? ;-) My untested guess (since we all seem to be mouthing off the first thing that comes to mind) is sed 's/^\([^:#+@-][^:]*\):[^:]*:/\1:(password):/' This assumes that empty usernames and usernames which do not begin with an alphanumeric character won't appear. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 8:53:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 1C9551578E; Wed, 26 Jan 2000 08:52:53 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12DVgL-000796-00; Wed, 26 Jan 2000 18:52:37 +0200 From: Sheldon Hearn To: Andy Farkas Cc: "David O'Brien" , freebsd-current@FreeBSD.org Subject: Re: ascii art in hosts.allow In-reply-to: Your message of "Wed, 26 Jan 2000 02:02:36 +1100." Date: Wed, 26 Jan 2000 18:52:37 +0200 Message-ID: <27471.948905557@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000 02:02:36 +1100, Andy Farkas wrote: > > So you'll notice that this file is an example and *demands* your > > attention in configuring your system properly. > > Change it to hosts.allow.sample then? No hosts.allow file is essentially > the same as the ALL:ALL:allow rule, no? No. In the absence of a hosts.allow file, hosts_access(3) denies all. Can we please move onto something else now. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 8:58:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 0A48715236; Wed, 26 Jan 2000 08:58:08 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (andyf@localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id DAA19716; Thu, 27 Jan 2000 03:57:51 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Thu, 27 Jan 2000 03:57:51 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: Sheldon Hearn Cc: "David O'Brien" , freebsd-current@FreeBSD.org Subject: Re: ascii art in hosts.allow In-Reply-To: <27471.948905557@axl.noc.iafrica.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000, Sheldon Hearn wrote: > > Change it to hosts.allow.sample then? No hosts.allow file is essentially > > the same as the ALL:ALL:allow rule, no? > > No. In the absence of a hosts.allow file, hosts_access(3) denies all. Not according to what I read in 'man 5 hosts_access' - especially the second paragraph titled "ACCESS CONTROL FILES". > > Can we please move onto something else now. :-) > But...but... ITS SUCH AN EYE-SORE!!!! IMHO. > Ciao, > Sheldon. > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 9: 1:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 2A338151E2; Wed, 26 Jan 2000 09:01:12 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12DVoM-000ALR-00; Wed, 26 Jan 2000 19:00:54 +0200 From: Sheldon Hearn To: Andy Farkas Cc: "David O'Brien" , freebsd-current@FreeBSD.org Subject: Re: ascii art in hosts.allow In-reply-to: Your message of "Thu, 27 Jan 2000 03:57:51 +1100." Date: Wed, 26 Jan 2000 19:00:54 +0200 Message-ID: <39754.948906054@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000 03:57:51 +1100, Andy Farkas wrote: > > No. In the absence of a hosts.allow file, hosts_access(3) denies all. > > Not according to what I read in 'man 5 hosts_access' - especially the > second paragraph titled "ACCESS CONTROL FILES". Wtf?! You're right. I'm frightened now. > But...but... ITS SUCH AN EYE-SORE!!!! IMHO. While this thread has been fun? C'mon, look around, there are bigger fish to fry. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 9:21:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id A1D6F14D3C for ; Wed, 26 Jan 2000 09:21:12 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (boomer.navinet.net [216.67.12.90]) by forrie.net with id e0QHLBB83453 for ; Wed, 26 Jan 2000 12:21:11 -0500 (EST) Message-Id: <4.2.2.20000126122022.00b44ee0@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 26 Jan 2000 12:20:45 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: Today's buildworld breakages Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here's the latest fault, from a cvsup just performed: cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/i386/usr/include -c /usr/src/lib/libc/../libc/net/rcmd.c -o rcmd.o /usr/src/lib/libc/../libc/net/rcmd.c: In function `rresvport_af': /usr/src/lib/libc/../libc/net/rcmd.c:337: too many arguments to function `bindresvport_sa' *** Error code 1 Stop in /usr/src/lib/libc. *** Error code 1 Stop in /usr/src/lib. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 9:29:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from Eagle.ZGIA.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with ESMTP id 89EA615390 for ; Wed, 26 Jan 2000 09:29:40 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by Eagle.ZGIA.zp.ua (8.9.3/8.9.3) with ESMTP id TAA45376 for ; Wed, 26 Jan 2000 19:26:30 +0200 (EET) (envelope-from laa@zgia.zp.ua) X-Authentication-Warning: Eagle.ZGIA.zp.ua: laa owned process doing -bs Date: Wed, 26 Jan 2000 19:26:30 +0200 (EET) From: Alexandr Listopad To: freebsd-current@freebsd.org Subject: help! need kernel! Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello! I have Abit motherboard with ATA-66 support. I try to install FreeBSD-CURRENT, all good when install, but after reboot kernel boots, but ask me a root device, when I press '?', there are no 'ad' device (this is my HDD). ;( As I understand - there are no support in that kernel for my HDD... ;( As I understand there are one way to help me - create new kernel with ata-pci0 support. If somebody can help me - please help! Thanks! P.S. I have latest cvs tree (but on the 3.4 box) and have latest kern.flp and mfsroot.flp. Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 10:38:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 2271F14C21 for ; Wed, 26 Jan 2000 10:38:50 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id NAA11807 for ; Wed, 26 Jan 2000 13:38:44 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Wed, 26 Jan 2000 13:38:44 -0500 (EST) From: Chuck Robey To: FreeBSD-current Subject: cvsup8 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What happened, it fell off the edge of the earth? Nslookup can't find it anymore. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 10:47:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from daffy.mics.net (cx965065-d.chnd1.az.home.com [24.15.53.199]) by hub.freebsd.org (Postfix) with ESMTP id 41E0A15067 for ; Wed, 26 Jan 2000 10:47:09 -0800 (PST) (envelope-from matt@daffy.mics.net) Received: by daffy.mics.net (Postfix, from userid 1001) id D36A2206BA; Wed, 26 Jan 2000 11:47:04 -0700 (MST) Date: Wed, 26 Jan 2000 11:47:04 -0700 From: Matt Miller To: freebsd-current@freebsd.org Subject: Sendmail on current Message-ID: <20000126114704.A1586@daffy.mics.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Firs tof all, I apologize if I am reasking a question, since I haven't done a good job of keeping up on my -current mail. Chastisment humbly accepted. I did check the -current archive on www.freebsd.org and have not seen a mention of this. On my last two make worlds I have had trouble with my system restarting. It hangs on the startup of sendmail. I have replaced sendmail on my system with Postfix. Addtionally, I have the following line in /etc/make.conf NO_SENDMAIL= true The only references to sendmail that I see in the UPDATING file is about the move of the sendmail.cf, which doesn't seem relevant. Since starting this email, I have created an /etc/mailer.conf. If this resolves it, I will be surprised, but feel free to let me know how stupid I am being. Reinstalling the Postfix port resolves this, as you might expect. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 10:51:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id CE01915412 for ; Wed, 26 Jan 2000 10:51:12 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 7FF93169A; Wed, 26 Jan 2000 10:49:45 -0800 (PST) Date: Wed, 26 Jan 2000 10:49:45 -0800 From: Chris Piazza To: Alexandr Listopad Cc: freebsd-current@FreeBSD.ORG Subject: Re: help! need kernel! Message-ID: <20000126104945.A4657@norn.ca.eu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from laa@zgia.zp.ua on Wed, Jan 26, 2000 at 07:26:30PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 26, 2000 at 07:26:30PM +0200, Alexandr Listopad wrote: > hello! > > I have Abit motherboard with ATA-66 support. > I try to install FreeBSD-CURRENT, all good when install, but after reboot > kernel boots, but ask me a root device, when I press '?', there are no > 'ad' device (this is my HDD). ;( As I understand - there are no support in > that kernel for my HDD... ;( > > As I understand there are one way to help me - create new kernel with > ata-pci0 support. The boot floppies have ATA in the kernel. I installed a new system on a BP6 with the hard drive on one of the HPT366 controllers just fine about two weeks ago. Sorry, but I have no idea what is going on here.. I just wanted to say that it worked for me.... ata-pci1: port 0xd400-0xd4ff,0xd000-0xd003, 0xcc00-0xcc07 irq 18 at device 19.0 on pci0 ... ad4: 12949MB disk at ata2 as master mode UDMA66 BTW, sos, if you're reading this: I like this format for reporting the hard drives present a lot better :-). -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 10:56:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (Postfix) with ESMTP id BA35A1528F for ; Wed, 26 Jan 2000 10:56:18 -0800 (PST) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.3/8.9.1) id KAA37528; Wed, 26 Jan 2000 10:56:04 -0800 (PST) (envelope-from mph) Date: Wed, 26 Jan 2000 10:56:04 -0800 From: Matthew Hunt To: Chuck Robey Cc: FreeBSD-current Subject: Re: cvsup8 Message-ID: <20000126105604.B37381@wopr.caltech.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from chuckr@picnic.mat.net on Wed, Jan 26, 2000 at 01:38:44PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 26, 2000 at 01:38:44PM -0500, Chuck Robey wrote: > What happened, it fell off the edge of the earth? Nslookup can't find it > anymore. I seem to recall an announcement from John yesterday or so, saying that it was going to fall off the edge of the earth temporarily. -- Matthew Hunt * Stay close to the Vorlon. http://www.pobox.com/~mph/ * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 10:56:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id F281C1538B for ; Wed, 26 Jan 2000 10:56:43 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12DXcE-000AQm-00; Wed, 26 Jan 2000 20:56:30 +0200 From: Sheldon Hearn To: Matt Miller Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sendmail on current In-reply-to: Your message of "Wed, 26 Jan 2000 11:47:04 MST." <20000126114704.A1586@daffy.mics.net> Date: Wed, 26 Jan 2000 20:56:30 +0200 Message-ID: <40099.948912990@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000 11:47:04 MST, Matt Miller wrote: > Chastisment humbly accepted. *chastise* :-) > The only references to sendmail that I see in the UPDATING file is > about the move of the sendmail.cf, which doesn't seem relevant. It's sorta relevant. > Since starting this email, I have created an /etc/mailer.conf. Should be /etc/mail/mailer.conf. There are two things that would have saved you from this problem (and the chastisement above :-) : 1) Reading your cvs-all mail. 2) Using mergemaster(1). Have fun. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 11: 2:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from ozz.freebsd.org.ru (ozz.etrust.ru [195.2.84.116]) by hub.freebsd.org (Postfix) with ESMTP id 1083E1524B for ; Wed, 26 Jan 2000 11:02:44 -0800 (PST) (envelope-from osa@ozz.freebsd.org.ru) Received: (from osa@localhost) by ozz.freebsd.org.ru (8.9.3/8.9.3) id VAA41969; Wed, 26 Jan 2000 21:57:12 +0300 (MSK) (envelope-from osa) Date: Wed, 26 Jan 2000 21:57:11 +0300 From: Sergey Osokin To: Alexandr Listopad Cc: freebsd-current@FreeBSD.ORG Subject: Re: help! need kernel! Message-ID: <20000126215711.B51651@freebsd.org.ru> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from laa@zgia.zp.ua on Wed, Jan 26, 2000 at 07:26:30PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 26, 2000 at 07:26:30PM +0200, Alexandr Listopad wrote: > hello! > > I have Abit motherboard with ATA-66 support. > I try to install FreeBSD-CURRENT, all good when install, but after reboot > kernel boots, but ask me a root device, when I press '?', there are no > 'ad' device (this is my HDD). ;( As I understand - there are no support in > that kernel for my HDD... ;( > > As I understand there are one way to help me - create new kernel with > ata-pci0 support. > > If somebody can help me - please help! > > Thanks! > > P.S. I have latest cvs tree (but on the 3.4 box) and have latest kern.flp > and mfsroot.flp. > > Its a simply. Install 3.4 with full sources, then use CVSup with "." tag and upgrade your sources tree. Then compile & install new kernel & do make world. Rgdz, Sergey A. Osokin, osa@FreeBSD.ORG.ru http://www.FreeBSD.ORG.ru/~osa/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 11:14:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id E97EF151E2 for ; Wed, 26 Jan 2000 11:14:41 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id OAA46066; Wed, 26 Jan 2000 14:14:27 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Wed, 26 Jan 2000 14:14:26 -0500 (EST) From: Chuck Robey To: Matthew Hunt Cc: FreeBSD-current Subject: Re: cvsup8 In-Reply-To: <20000126105604.B37381@wopr.caltech.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000, Matthew Hunt wrote: > On Wed, Jan 26, 2000 at 01:38:44PM -0500, Chuck Robey wrote: > > > What happened, it fell off the edge of the earth? Nslookup can't find it > > anymore. > > I seem to recall an announcement from John yesterday or so, saying > that it was going to fall off the edge of the earth temporarily. Yeah, now I remember, thanks guys. I'd thought that huge cvsup thread was about 8 coming on line, not going off. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 11:26:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from wint.itfs.nsk.su (wint.itfs.nsk.su [212.20.32.43]) by hub.freebsd.org (Postfix) with ESMTP id 2A06614E02 for ; Wed, 26 Jan 2000 11:26:05 -0800 (PST) (envelope-from nnd@wint.itfs.nsk.su) Received: (from nnd@localhost) by wint.itfs.nsk.su (8.9.3/8.9.3) id BAA04881; Thu, 27 Jan 2000 01:18:58 +0600 (NOVT) (envelope-from nnd) Date: Thu, 27 Jan 2000 01:18:58 +0600 (NOVT) Message-Id: <200001261918.BAA04881@wint.itfs.nsk.su> From: nnd@mail.nsk.ru To: Alexandr Listopad Cc: current@freebsd.org Subject: Re: help! need kernel! In-Reply-To: User-Agent: tin/1.4.2-20000123 ("Polish") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Alexandr Listopad wrote: > hello! > > I have Abit motherboard with ATA-66 support. > I try to install FreeBSD-CURRENT, all good when install, but after reboot > kernel boots, but ask me a root device, when I press '?', there are no > 'ad' device (this is my HDD). ;( As I understand - there are no support in > that kernel for my HDD... ;( What is the BIOS version on your motherboard ? In my case - ABIT BP6 two Celeron motherboard with HPT66 controller - there was problems with disks numbering and booting by BIOS when there are HDDs on both regular and ATA-66 controllers. Those problems was resolved by changing the BIOS to the next version (....NJ). N.Dudorov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 14:14: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from greenie.muc.de (greenie.muc.de [193.149.48.161]) by hub.freebsd.org (Postfix) with SMTP id 4C953158FA for ; Wed, 26 Jan 2000 14:13:56 -0800 (PST) (envelope-from gert@greenie.muc.de) Received: by greenie.muc.de via sendmail with stdio id for freebsd-current@freebsd.org; Wed, 26 Jan 2000 23:13:55 +0100 (MET) (Smail-3.2 1996-Jul-4 #4 built -Feb-21) Message-ID: <20000126231354.B886@greenie.muc.de> Date: Wed, 26 Jan 2000 23:13:55 +0100 From: Gert Doering To: Christoph Kukulies , mgetty@greenie.muc.de Cc: freebsd-current@freebsd.org Subject: Re: locking problem FreeBSD 3.4 - kermit and mgetty References: <200001251951.UAA03088@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <200001251951.UAA03088@gil.physik.rwth-aachen.de>; from Christoph Kukulies on Tue, Jan 25, 2000 at 08:51:40PM +0100 X-mgetty-docs: http://alpha.greenie.net/mgetty/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Tue, Jan 25, 2000 at 08:51:40PM +0100, Christoph Kukulies wrote: > But as a result mgetty gets into kermit's ways such that when a > modem connection is made I suddenly get a modem prompt like > +FCON as if someone (mgetty) is either messing with my local > or the remote modem while kermit opens the connection. The modem is in fax mode, and has established a fax connection. Have kermit send an AT+FCLASS=0 first. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert@greenie.muc.de fax: +49-89-35655025 gert.doering@physik.tu-muenchen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 14:22:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from tesla-e0.salk.edu (tesla-e0.salk.edu [198.202.70.1]) by hub.freebsd.org (Postfix) with ESMTP id 6469114DBA; Wed, 26 Jan 2000 14:22:10 -0800 (PST) (envelope-from jorge@salk.edu) Received: from axelrod.salk.edu (axelrod.salk.edu [198.202.70.121]) by tesla-e0.salk.edu (8.7.5/8.7.3) with SMTP id OAA07246; Wed, 26 Jan 2000 14:22:27 -0800 (PST) Date: Wed, 26 Jan 2000 14:21:50 -0800 (PST) From: Jorge Aldana Reply-To: Jorge Aldana To: freebsd-current@freebsd.org Cc: freebsd-stable@freebsd.org Subject: MD5 Sigs on 3.4-20000124-STABLE Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I checked the signatures on the files I downloaded from current.freebsd.org/pub/FreeBSD/snapshots/i386/3.4-20000124-STABLE/ and the following fail the MD5 check: < = from CHECKSUM.MD5 listing > = downloaded file. 68c70 < MD5 (bin.cp) = c688b821316686fb8393b52ef9af1d86 --- > MD5 (bin.cp) = 5b448c5cffd07e612873c80bd5ed6b41 93c95 < MD5 (bin.do) = f87680f6cb58bf21af6e18825e7e23a2 --- > MD5 (bin.do) = 3dd11e1748dabf91bd36add0a05b0ea5 75c77 < MD5 (scontrib.cp) = 1d19d8fd622d067a4bd6167e84357ece --- > MD5 (scontrib.cp) = 56d9a710f54b7f1ba0ab10ad0c917b79 I've downloaded several times as a group and individually is their a known problem? Jorge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 14:22:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id 3560C14E83 for ; Wed, 26 Jan 2000 14:22:12 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS1-p13.rlz.netvision.net.il [62.0.168.15]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id AAA15954; Thu, 27 Jan 2000 00:21:59 +0200 (IST) Message-ID: <388F73D0.80AD5C39@freenet.co.uk> Date: Wed, 26 Jan 2000 22:23:12 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: My ATAPI CD not come ready References: <200001260731.IAA90753@freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > > It seems Alex wrote: > > > You need to update.. > > > > > > OK - I've just updated. Here goes again: > > > > ata1-slave: ata_command: timeout waiting for intr > > ata1-slave: identify failed > > ad0: 6194MB [13424/15/63] at ata0-master using > > UDMA33 > > acd0: CDROM at ata1-master using PIO4 > > Mounting root from ufs:/dev/ad0s2a > > > I wouldn't be surprised if ATAPI_CMD_IDENTIFY failed on ata1-master, but > > why does it say ata1-slave? It's a notebook PC, so unfortunately I'm > > not sure how it's all connected. > > Apparently it thinks something is there, could you mail me a complete > verbose bootlog (dmesg) please, and I'll try to figure out what is > going wrong.. OK - here's the part relevant to ata: ata-pci0: port 0xfcf0-0xfcff at device 1.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc ata1 at 0x0170 irq 15 on ata-pci0 ... (delay) ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ata0-master: success setting up UDMA2 mode on PIIX4 chip ad0: ATA-4 disk at ata0 as master ad0: 6194MB (12685680 sectors), 13424 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 ad0: piomode=4 dmamode=2 udmamode=2 cblid=0 Creating DISK ad0 Creating DISK wd0 ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1 ata1-master: success setting up PIO4 mode on generic chip acd0: CDROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm photo disc loaded, unlocked Mounting root from ufs:/dev/ad0s2a ad0s1: type 0xb, start 63, end = 5322239, size 5322177 : OK ad0s2: type 0xa5, start 5322240, end = 12685679, size 7363440 : OK Any ideas? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 14:26:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 47CCA1538B for ; Wed, 26 Jan 2000 14:26:22 -0800 (PST) (envelope-from mestery@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 23F7536E7 for ; Wed, 26 Jan 2000 16:26:21 -0600 (CST) Received: from localhost (mestery@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id QAA09951 for ; Wed, 26 Jan 2000 16:26:20 -0600 (CST) X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs Date: Wed, 26 Jan 2000 16:26:20 -0600 (CST) From: To: freebsd-current@freebsd.org Subject: NFS /usr/src and /usr/obj? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm wondering how one can do a buildworld on a machine, and then NFS mount /usr/src and /usr/obj on a client machine and do an installworld of the freshly built sources? I've been looking in the archives without much success, and haven't figured it out by reading the makefiles yet. Can anyone shed some light on this? -- Kyle Mestery | Ancor Communications mestery@visi.com | http://www.freebsd.org/ mestery@netwinder.org | http://www.netwinder.org/ Protect your right to privacy: www.freecrypto.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 14:32:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id 1551514CCE for ; Wed, 26 Jan 2000 14:32:33 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from hamilton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 26 Jan 2000 22:32:32 +0000 (GMT) Date: Wed, 26 Jan 2000 22:32:31 +0000 From: David Malone To: mestery@visi.com Cc: freebsd-current@freebsd.org Subject: Re: NFS /usr/src and /usr/obj? Message-ID: <20000126223231.A25856@hamilton.maths.tcd.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from mestery@visi.com on Wed, Jan 26, 2000 at 04:26:20PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 26, 2000 at 04:26:20PM -0600, mestery@visi.com wrote: > I'm wondering how one can do a buildworld on a machine, and then NFS > mount /usr/src and /usr/obj on a client machine and do an installworld > of the freshly built sources? I've been looking in the archives without > much success, and haven't figured it out by reading the makefiles yet. > Can anyone shed some light on this? We've done this several times - though we often just use rdist or rsync these days ;-) David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 14:33:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 8FD8214CCA for ; Wed, 26 Jan 2000 14:33:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id XAA07349; Wed, 26 Jan 2000 23:32:58 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: mestery@visi.com Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS /usr/src and /usr/obj? In-reply-to: Your message of "Wed, 26 Jan 2000 16:26:20 CST." Date: Wed, 26 Jan 2000 23:32:58 +0100 Message-ID: <7347.948925978@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , mestery@visi.com writes: >I'm wondering how one can do a buildworld on a machine, and then NFS >mount /usr/src and /usr/obj on a client machine and do an installworld >of the freshly built sources? I've been looking in the archives without >much success, and haven't figured it out by reading the makefiles yet. >Can anyone shed some light on this? I've done it in the past, but not recently. Consider the alternative of mounting the destination on the compilehost and make install DESTDIR=/mnt -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 14:37:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.cioe.com (ns1.cioe.com [204.120.165.37]) by hub.freebsd.org (Postfix) with ESMTP id 5627114A29 for ; Wed, 26 Jan 2000 14:37:50 -0800 (PST) (envelope-from steve@virtual-voodoo.com) Received: from ny1wsh031 (tek.cioe.com [204.120.165.120]) by ns1.cioe.com (8.9.3/8.9.3) with SMTP id RAA13745; Wed, 26 Jan 2000 17:37:44 -0500 (EST) (envelope-from steve@virtual-voodoo.com) Message-ID: <01d501bf684d$eb42d760$851a050a@winstar.com> From: "Steven E. Ames" To: , References: Subject: Re: NFS /usr/src and /usr/obj? Date: Wed, 26 Jan 2000 17:37:20 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sure. This can be done with no problems. It is, in fact, a good way to put the same OS on multiple machines. -Steve ----- Original Message ----- From: To: Sent: Wednesday, January 26, 2000 5:26 PM Subject: NFS /usr/src and /usr/obj? > I'm wondering how one can do a buildworld on a machine, and then NFS > mount /usr/src and /usr/obj on a client machine and do an installworld > of the freshly built sources? I've been looking in the archives without > much success, and haven't figured it out by reading the makefiles yet. > Can anyone shed some light on this? > > -- > Kyle Mestery | Ancor Communications > mestery@visi.com | http://www.freebsd.org/ > mestery@netwinder.org | http://www.netwinder.org/ > Protect your right to privacy: www.freecrypto.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 15: 2: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx2.x-treme.gr (mx2.x-treme.gr [212.120.192.15]) by hub.freebsd.org (Postfix) with ESMTP id 8B351152BD; Wed, 26 Jan 2000 15:01:51 -0800 (PST) (envelope-from keramida@diogenis.ceid.upatras.gr) Received: from hades.hell.gr (pat40.x-treme.gr [212.120.197.232]) by mx2.x-treme.gr (8.9.3/8.9.3/IPNG-ADV-ANTISPAM-0.1) with ESMTP id BAA00618; Thu, 27 Jan 2000 01:01:36 +0200 Received: (from charon@localhost) by hades.hell.gr (8.9.3/8.9.3) id BAA03666; Thu, 27 Jan 2000 01:01:39 +0200 (EET) (envelope-from keramida@diogenis.ceid.upatras.gr) Date: Thu, 27 Jan 2000 01:01:39 +0200 From: Giorgos Keramidas To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: ipfilter and ipfstat Message-ID: <20000127010139.A3331@hades.hell.gr> Reply-To: keramida@ceid.upatras.gr References: <20000125051418.A62880@charon.hell.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Tue, Jan 25, 2000 at 09:23:23PM -0800 X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E X-Phone-Number: +30-94-6203692, +30-93-2886457 X-Address: Theodorou Kirinaiou 61, 26334 Patra, Greece Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Jan 25, 2000 at 09:23:23PM -0800, Kris Kennaway wrote: > On Tue, 25 Jan 2000, the Webslave wrote: > > > > Okay, so I finally decided to take the plunge and check out ipfilter. ipf > > > seemed to load my ruleset with no problems, but ipfstat dies with: > > > > > > ioctl(SIOCGETFS): Invalid argument > > > > And what would that ruleset be? > > > > # Default to deny > block in log on tun0 from any to any [snip] I have tested your ruleset in my ipf/ipfstat version. The one I have comes from the 4.0-20000124-CURRENT snapshot, since I haven't had the time to cvsup/make-world since. The results of the tests are shown below, and as you can see ipfstat reports the rules correctly. hades# ipf -FA hades# cd /tmp hades# ipf -f ipf.conf hades# ipfstat -nio @1 pass out quick on tun0 proto tcp/udp from any to any keep state @2 pass out quick on tun0 proto icmp from any to any keep state @3 pass out quick on lo0 from any to any @1 block in log on tun0 from any to any @2 block in quick on tun0 from 192.168.0.0/16 to any @3 block in quick on tun0 from 172.16.0.0/12 to any @4 block in quick on tun0 from 10.0.0.0/8 to any @5 block in quick on tun0 from 127.0.0.0/8 to any @6 pass in quick on tun0 proto tcp from any to any port = 12345 flags S/FSRPAU keep state keep frags @7 pass in quick on tun0 proto udp from any to any port = 31337 keep state @8 pass in quick on lo0 from any to any hades# ipf -FA hades# ipf -f /etc/ipf.conf What version of ipfilter/ipfstat are you using? I don't now if cvsup'ing your sources to a more recent version might help at all, but I don't see a problem with these rules and ipfstat... I'm sorry if that is not of any help to you, but I can't seem to find anything wrong here :/ -- Giorgos Keramidas, < keramida @ ceid . upatras . gr > "Don't let your schooling interfere with your education." [Mark Twain] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 16:31:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from relativity.student.utwente.nl (wit389306.student.utwente.nl [130.89.234.166]) by hub.freebsd.org (Postfix) with ESMTP id 4BBA115479 for ; Wed, 26 Jan 2000 16:31:13 -0800 (PST) (envelope-from djb@wit389306.student.utwente.nl) Received: by relativity.student.utwente.nl (Postfix, from userid 1001) id 3E1131E32; Thu, 27 Jan 2000 01:31:25 +0100 (CET) Date: Thu, 27 Jan 2000 01:31:25 +0100 From: "Dave J. Boers" To: Devin Butterfield Cc: Donn Miller , current@FreeBSD.ORG Subject: Re: pcm - stutters Message-ID: <20000127013125.A49548@relativity.student.utwente.nl> Reply-To: djb@relativity.student.utwente.nl References: <388E1C6B.489B84D2@cvzoom.net> <00012520102300.02605@dbm.wireless.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <00012520102300.02605@dbm.wireless.net>; from dbutter@wireless.net on Tue, Jan 25, 2000 at 08:05:48PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It is rumoured that Devin Butterfield had the courage to say: > I too notice these problems of mpg123 skipping during disk activity or X > graphics ops but I have always had these problems, both with -STABLE and > -CURRENT. I notice this with xmms too. So this is nothing new. Isn't this simply a typical issue of IDE hardware? I too notice xmms skipping on heavy disk activity (typically the find command that runs from cron at 01:59). This happens even though I have two processors and a disk that can do 16 Mb/sec on UDMA66. One would expect such a system to be able to do a find and play mp3's simultaneously. However, AFAIK the IDE hardware typically handles only one request at a time and handles all requests sequentially, contrary to scsi. It may thus happen that the read requests from xmms, small as they may be, get delayed too long and unnecessary. I'm not an expert on this, but I believe scatter/gather is the way scsi handles this problem in hardware. Perhaps the ata driver could be made to do something similar on the driver level. I have experienced significantly better responsiveness during high disk usage of much slower systems that are running with scsi disks only. In fact, I have a 486 that has better response times (it has an EISA bus and adaptec 2740 scsi with a disk that can do -- and does! -- 8 Mb/sec disk->memory) than my Abit BP6 dual celeron UDMA66 system during the cron job at 1:59. Regards, Dave Boers. -- djb@relativity.student.utwente.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 16:46:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 941FA14E61 for ; Wed, 26 Jan 2000 16:46:04 -0800 (PST) (envelope-from mestery@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 7906937F1; Wed, 26 Jan 2000 18:45:59 -0600 (CST) Received: from localhost (mestery@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id SAA18975; Wed, 26 Jan 2000 18:45:59 -0600 (CST) X-Authentication-Warning: isis.visi.com: mestery owned process doing -bs Date: Wed, 26 Jan 2000 18:45:59 -0600 (CST) From: To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS /usr/src and /usr/obj? In-Reply-To: <7347.948925978@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Wed, 26 Jan 2000, Poul-Henning Kamp wrote: > I've done it in the past, but not recently. > > Consider the alternative of mounting the destination on the compilehost > and make install DESTDIR=/mnt > Thanks to everyone for the replies. It works fine for me now. I was automounting all of the directories from the server using AMD, and then I had /usr/src and /usr/obj as symlinks to their respective automount locations. This apparently was what was causing me problems. With /usr/src and /usr/obj directly mounted themselves, the installworld is proceeding as I type this. Again, thanks for all the responses. -- Kyle Mestery | Ancor Communications mestery@visi.com | http://www.freebsd.org/ mestery@netwinder.org | http://www.netwinder.org/ Protect your right to privacy: www.freecrypto.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 17:52: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from piglet.dstc.edu.au (piglet.dstc.edu.au [130.102.176.1]) by hub.freebsd.org (Postfix) with ESMTP id 2ADBF154E1 for ; Wed, 26 Jan 2000 17:52:06 -0800 (PST) (envelope-from ggm@dstc.edu.au) Received: from azure.dstc.edu.au (azure.dstc.edu.au [130.102.176.27]) by piglet.dstc.edu.au (8.9.3/8.9.3) with ESMTP id LAA27640 for ; Thu, 27 Jan 2000 11:52:03 +1000 (EST) Received: (from ggm@localhost) by azure.dstc.edu.au (8.8.5/8.8.4) id LAA20687 for freebsd-current@freebsd.org.; Thu, 27 Jan 2000 11:52:03 +1000 (EST) Date: Thu, 27 Jan 2000 11:52:03 +1000 (EST) From: George Michaelson Message-Id: <200001270152.LAA20687@azure.dstc.edu.au> To: freebsd-current@freebsd.org Subject: namei() costs for symlink farms and big dirs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can I pick some FreeBSD experts brains off-list please? anybody who can comment on the cost(s) of running large flat directories of symlinks (eg using GNU stow for /usr/local/bin) especially over NFS? cheers -George To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 18:58:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 50D50154E9 for ; Wed, 26 Jan 2000 18:58:36 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 72283 invoked by uid 1001); 27 Jan 2000 02:58:35 -0000 Date: 26 Jan 2000 18:58:35 -0800 Date: Wed, 26 Jan 2000 18:58:35 -0800 From: Bill Swingle To: current@freebsd.org Subject: make release weirdness? Message-ID: <20000126185835.A72151@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I fianlly got -current from this morning to build and install so I started a make release this afternoon only to hit the USA_RESIDENT block. I modified /etc/make.conf to include the appropriate line and started again. After awhile it hit the same block: -------------------------------------------------------------- >>> elf make world started on Thu Jan 27 02:41:33 GMT 2000 -------------------------------------------------------------- !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! >>> You must define the value of USA_RESIDENT as 'YES' or >>> 'NO' as appropriate, in the environment or /etc/make.conf >>> before building can proceed. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src/release. root@deimos:/usr/src/release$ cat /etc/make.conf USA_RESIDENT=YES root@deimos:/usr/src/release$ Shouldn;t it be pulling the USA_RESIDENT value out of /etc/make.conf? Am I missing something here? -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 19:14:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A59531548D for ; Wed, 26 Jan 2000 19:14:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA18141; Wed, 26 Jan 2000 19:14:37 -0800 (PST) (envelope-from dillon) Date: Wed, 26 Jan 2000 19:14:37 -0800 (PST) From: Matthew Dillon Message-Id: <200001270314.TAA18141@apollo.backplane.com> To: George Michaelson Cc: freebsd-current@FreeBSD.ORG Subject: Re: namei() costs for symlink farms and big dirs References: <200001270152.LAA20687@azure.dstc.edu.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Can I pick some FreeBSD experts brains off-list please? : :anybody who can comment on the cost(s) of running large :flat directories of symlinks (eg using GNU stow for /usr/local/bin) :especially over NFS? : :cheers : -George There is definitely more overhead but you may not notice it. We ran just about everything at BEST through softlinks (1), sometimes several levels, and never noticed any problems. (1) home directories, most configuration files, htdocs, virtual host directory links. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 19:34:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from majordomo2.umd.edu (majordomo2.umd.edu [128.8.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 6862A15363 for ; Wed, 26 Jan 2000 19:34:50 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu (root@rac1.wam.umd.edu [128.8.10.141]) by majordomo2.umd.edu (8.9.3/8.9.3) with ESMTP id WAA20983 for ; Wed, 26 Jan 2000 22:34:43 -0500 (EST) Received: from rac1.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.3/8.9.3) with SMTP id WAA14516 for ; Wed, 26 Jan 2000 22:34:47 -0500 (EST) Received: from localhost (culverk@localhost) by rac1.wam.umd.edu (8.9.3/8.9.3) with ESMTP id WAA14512 for ; Wed, 26 Jan 2000 22:34:47 -0500 (EST) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Wed, 26 Jan 2000 22:34:47 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: ipsec errors Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was just wondering how to get rid of these errors in my startup: Jan 26 22:12:19 culverk inetd[739]: ftp/tcp: ipsec initialization failed; out entrust Jan 26 22:12:19 culverk inetd[739]: telnet/tcp: ipsec initialization failed; in entrust Jan 26 22:12:19 culverk inetd[739]: telnet/tcp: ipsec initialization failed; out entrust Jan 26 22:12:19 culverk inetd[739]: finger/tcp: ipsec initialization failed; in entrust Jan 26 22:12:19 culverk inetd[739]: finger/tcp: ipsec initialization failed; out entrust Jan 26 22:12:19 culverk inetd[739]: ntalk/udp: ipsec initialization failed; in entrust Jan 26 22:12:19 culverk inetd[739]: ntalk/udp: ipsec initialization failed; out entrust Maybe there was a message on here that I overlooked, I'm not sure, but how exactly do I get rid of them? ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 19:43: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 499EE1549F for ; Wed, 26 Jan 2000 19:43:00 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id e0R3gsw43382; Wed, 26 Jan 2000 22:42:54 -0500 (EST) Date: Wed, 26 Jan 2000 22:42:54 -0500 (EST) From: jack To: Bill Swingle Cc: current@FreeBSD.ORG Subject: Re: make release weirdness? In-Reply-To: <20000126185835.A72151@dub.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today Bill Swingle wrote: > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > >>> You must define the value of USA_RESIDENT as 'YES' or > >>> 'NO' as appropriate, in the environment or /etc/make.conf > >>> before building can proceed. > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > *** Error code 1 > > Stop in /usr/src/release. > root@deimos:/usr/src/release$ cat /etc/make.conf > USA_RESIDENT=YES > root@deimos:/usr/src/release$ > > > Shouldn;t it be pulling the USA_RESIDENT value out of /etc/make.conf? > Am I missing something here? It's probably looking in ${CHROOTDIR}/etc/make.conf and finding the freshly cvs co'ed copy with that commented out. :( -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 19:52:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id CF40B1552F for ; Wed, 26 Jan 2000 19:52:44 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 73685 invoked by uid 1001); 27 Jan 2000 03:52:40 -0000 Date: 26 Jan 2000 19:52:40 -0800 Date: Wed, 26 Jan 2000 19:52:40 -0800 From: Bill Swingle To: jack Cc: current@freebsd.org Subject: Re: make release weirdness? Message-ID: <20000126195240.A73644@dub.net> References: <20000126185835.A72151@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 26, 2000 at 10:42:54PM -0500, jack wrote: > Today Bill Swingle wrote: > > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > >>> You must define the value of USA_RESIDENT as 'YES' or > > >>> 'NO' as appropriate, in the environment or /etc/make.conf > > >>> before building can proceed. > > !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! > > *** Error code 1 > > > > Stop in /usr/src/release. > > root@deimos:/usr/src/release$ cat /etc/make.conf > > USA_RESIDENT=YES > > root@deimos:/usr/src/release$ > > > > > > Shouldn;t it be pulling the USA_RESIDENT value out of /etc/make.conf? > > Am I missing something here? > > It's probably looking in ${CHROOTDIR}/etc/make.conf and finding > the freshly cvs co'ed copy with that commented out. :( Yeah, this makes a lot of sense, especially it's working in a chrooted environment. Thanks :) -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 20: 5:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 7F129154B2 for ; Wed, 26 Jan 2000 20:05:32 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id NAA23430; Thu, 27 Jan 2000 13:05:18 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id NAA04047; Thu, 27 Jan 2000 13:05:17 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id NAA02341; Thu, 27 Jan 2000 13:05:16 +0900 (JST) To: culverk@wam.umd.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: ipsec errors In-Reply-To: References: X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000127130559K.shin@nd.net.fujitsu.co.jp> Date: Thu, 27 Jan 2000 13:05:59 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 31 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was just wondering how to get rid of these errors in my startup: > > Jan 26 22:12:19 culverk inetd[739]: ftp/tcp: ipsec initialization > failed; out entrust > Jan 26 22:12:19 culverk inetd[739]: telnet/tcp: ipsec initialization > failed; in entrust > Jan 26 22:12:19 culverk inetd[739]: telnet/tcp: ipsec initialization > failed; out entrust > Jan 26 22:12:19 culverk inetd[739]: finger/tcp: ipsec initialization > failed; in entrust > Jan 26 22:12:19 culverk inetd[739]: finger/tcp: ipsec initialization > failed; out entrust > Jan 26 22:12:19 culverk inetd[739]: ntalk/udp: ipsec initialization > failed; in entrust > Jan 26 22:12:19 culverk inetd[739]: ntalk/udp: ipsec initialization > failed; out entrust > > Maybe there was a message on here that I overlooked, I'm not sure, but how > exactly do I get rid of them? Now IPsec related control functionalities are added to inetd, and when kernel is not compiled with IPSEC related options, IPsec related socket initialization fails and those messages are print out. It is not harmful but I should have lower the syslog level, sorry. I'll soon fix it. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 20:31:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2C76B154B2 for ; Wed, 26 Jan 2000 20:31:24 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA03129 for ; Wed, 26 Jan 2000 21:31:22 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA93497 for ; Wed, 26 Jan 2000 21:30:58 -0700 (MST) Message-Id: <200001270430.VAA93497@harmony.village.org> To: current@freebsd.org Subject: BROKEN WORLD Date: Wed, 26 Jan 2000 21:30:58 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter, I'd like to see your world log, and the output of cd src/share/mk ; cvs diff bsd.kmod.mk. I get the following error when I try to build world as of about 2 hours ago. I just did a cvsup and only things in lib and ports updated. ===> sys/modules/vpo @ -> /home/imp/FreeBSD/src/sys machine -> /home/imp/FreeBSD/src/sys/i386/include perl @/kern/makedevops.pl -h @/kern/bus_if.m perl @/kern/makedevops.pl -h @/kern/device_if.m make: don't know how to make ppbus_if.h. Stop Yours in frustration, Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 20:34:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 83DAC1513B for ; Wed, 26 Jan 2000 20:34:31 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA03169 for ; Wed, 26 Jan 2000 21:34:25 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA93572 for ; Wed, 26 Jan 2000 21:34:01 -0700 (MST) Message-Id: <200001270434.VAA93572@harmony.village.org> Subject: Re: BROKEN WORLD To: current@freebsd.org In-reply-to: Your message of "Wed, 26 Jan 2000 21:30:58 MST." Date: Wed, 26 Jan 2000 21:34:01 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -------- Warner Losh writes: : I'd like to see your world log, and the output of : cd src/share/mk ; cvs diff bsd.kmod.mk. I get the following error : when I try to build world as of about 2 hours ago. I just did a cvsup : and only things in lib and ports updated. Ummm, I think cvs did something strange... I retract this statement until such time as I can make sure that cvs didn't do something stupid. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 20:46:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id AAFD8154E5 for ; Wed, 26 Jan 2000 20:46:07 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id NAA02142; Thu, 27 Jan 2000 13:46:06 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id NAA21359; Thu, 27 Jan 2000 13:46:06 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id NAA04321; Thu, 27 Jan 2000 13:46:05 +0900 (JST) To: culverk@wam.umd.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: ipsec errors In-Reply-To: <20000127130559K.shin@nd.net.fujitsu.co.jp> References: <20000127130559K.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000127134647Y.shin@nd.net.fujitsu.co.jp> Date: Thu, 27 Jan 2000 13:46:47 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 42 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Maybe there was a message on here that I overlooked, I'm not sure, but how > > exactly do I get rid of them? > > It is not harmful but I should have lower the syslog level, > sorry. > I'll soon fix it. I just added debug flag check instead of changing syslog level. Could you please try the following patch to usr.sbin/inetd/inetd.c ? Thanks, Yoshinobu Inoue Index: inetd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/inetd/inetd.c,v retrieving revision 1.75 diff -u -r1.75 inetd.c --- inetd.c 2000/01/25 14:52:10 1.75 +++ inetd.c 2000/01/27 04:41:15 @@ -1256,7 +1256,8 @@ buf = ipsec_set_policy(policy_in, strlen(policy_in)); if (buf != NULL) { if (setsockopt(sep->se_fd, level, opt, - buf, ipsec_get_policylen(buf)) < 0) { + buf, ipsec_get_policylen(buf)) < 0 && + debug != 0) { syslog(LOG_ERR, "%s/%s: ipsec initialization failed; %s", sep->se_service, sep->se_proto, @@ -1271,7 +1272,8 @@ buf = ipsec_set_policy(policy_out, strlen(policy_out)); if (buf != NULL) { if (setsockopt(sep->se_fd, level, opt, - buf, ipsec_get_policylen(buf)) < 0) { + buf, ipsec_get_policylen(buf)) < 0 && + debug != 0) { syslog(LOG_ERR, "%s/%s: ipsec initialization failed; %s", sep->se_service, sep->se_proto, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 21:35:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id DB87315418 for ; Wed, 26 Jan 2000 21:35:23 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 19595 invoked from network); 27 Jan 2000 05:35:20 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 27 Jan 2000 05:35:20 -0000 Date: Thu, 27 Jan 2000 16:35:16 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: "Yevmenkin, Maksim N, CSCIO" Cc: "'freebsd-current@freebsd.org'" , "'freebsd-hackers@freebsd.org'" Subject: RE: BPF bug or not? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000, Yevmenkin, Maksim N, CSCIO wrote: > > > I've just found that read from /dev/bpfX never return > > EAGAIN/EWOULDBLOCK. > > > It means that when you do a non blocking read and there is > > no data you will > > > always get 0. > [ untested fix removed :) ] > > Yes, it works. But it returns EAGAIN for both O_RDONLY|O_NONBLOCK and > O_RDWR|O_NONBLOCK open modes. In the same time pipe returns 0 for > O_RDONLY|O_NONBLOCK mode and EAGAIN for O_RDWR|O_NONBLOCK. > > It there any specs for "read" system call? Well, POSIX is very complete for read() on regular files and pipes (both ordinary pipes and fifos. read() on a pipe with no data and writers returns 0 because that case is considered to be EOF. O_RDWR for fifos gives undefined behaviour. I don't know of any legitimate use for it. It has the illegitimate use of talking to oneself using only one channel :-). This gives the EAGAIN behaviour for O_RDWR|O_NONBLOCK. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 21:40:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.6.134]) by hub.freebsd.org (Postfix) with ESMTP id 44AA315593 for ; Wed, 26 Jan 2000 21:40:30 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from daemon@localhost) by smtp04.primenet.com (8.9.3/8.9.3) id WAA23770; Wed, 26 Jan 2000 22:40:01 -0700 (MST) Received: from ip-83-087.prc.primenet.com(207.218.83.87), claiming to be "pinyon.org" via SMTP by smtp04.primenet.com, id smtpdAAASvaixU; Wed Jan 26 22:39:50 2000 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id 5BCE745; Wed, 26 Jan 2000 22:39:39 -0700 (MST) X-Mailer: exmh version 2.1.0 09/18/1999 To: "Rodney W. Grimes" Cc: sos@freebsd.dk (Soren Schmidt), current@FreeBSD.ORG Subject: Re: FIC SD-11 not happy with ata In-Reply-To: Message from "Rodney W. Grimes" of "Tue, 18 Jan 2000 21:37:43 PST." <200001190537.VAA50862@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Jan 2000 22:39:39 -0700 From: "Russell L. Carter" Message-Id: <20000127053939.5BCE745@pinyon.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG %> %It seems Russell L. Carter wrote: %> %> %It seems Russell L. Carter wrote: %> %> %> %> %> %> I swapped out my motherboard and am seeing this now: %... % %> %> )(*&$#%$# stupid magazine benchmarkers never actually test %> things like IO... grrrrr.... % %We in the computer hardware business have a better name for ``FIC'', %Fix It Continuously. They are not known for their quality, or should %I say they are known for their lack of quality :-). Yah... as before ok I fixed this by swapping in an ASUS K7M (forget the audio, I can't figure that one out) For all of the bitching on Soren's ata driver, I'd like to make this observation on a 500MHz/256MB ASUS K7 systemm, bonnie -s 500: ad0: 13783MB [28005/16/63] at ata0-master using UDMA33 Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 500 8273 27.7 7734 8.4 3009 7.6 8549 31.8 8828 7.2 134.6 1.3 ad1: 19574MB [39770/16/63] at ata1-master using UDMA66 Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU 500 20650 84.1 20805 30.8 5644 14.8 22111 86.2 21253 21.1 148.9 1.4 Um, that ad1 drive cost me $224US, direct from the IBM mothership. Best regards, Russell %-- %Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net % % %To Unsubscribe: send mail to majordomo@FreeBSD.org %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 22:35:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from rowdy.panther.net (rowdy.panther.net [209.197.223.18]) by hub.freebsd.org (Postfix) with ESMTP id 0EC211501C; Wed, 26 Jan 2000 22:35:23 -0800 (PST) (envelope-from kward@panther.net) Received: from localhost (2356 bytes) by rowdy.panther.net via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Thu, 27 Jan 2000 00:35:37 -0600 (CST) (Smail-3.2.0.109 1999-Oct-27 #2 built 1999-Dec-30) Message-Id: From: kward@panther.net (Keith Ward) Subject: Re: OpenSSL docs for FAQ In-Reply-To: from Kris Kennaway at "Jan 25, 2000 00:49:04 am" To: Kris Kennaway Date: Thu, 27 Jan 2000 00:35:37 -0600 (CST) Cc: current@freebsd.org, security@freebsd.org X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Only recommendation I might pass on is being consistant in the use of "USA" instead of "US". The document starts off with references to "USA" and then changes to "US". Following the custom used in current crypto source (i.e. "USA_RESIDENT" in make.conf) I would suggest using "USA". Keith According to the writings of Kris Kennaway > > Can people please review this for style and content, for inclusion in > the FAQ? I'll also need someone to mark it up once it's ready since SGML > is currently not among my abilities :-) > [ ... ] > > However, some of the algorithms (specifically, RSA and IDEA) included > in OpenSSL are protected by patents in the USA and elsewhere and are > not available for unrestricted use. In addition, export of > cryptographic code from the USA has (until recently) been heavily > restricted. As a result, FreeBSD has available three different > versions of OpenSSL depending on geographical location (US/non-US) and > compliance with the RSAREF license (see below). [ ... ] > People who are located outside the USA, and who obtain their crypto > sources from internat.freebsd.org (the International Crypto > Repository), will build a version of OpenSSL which includes RSA, but > does not include IDEA, because the latter is restricted in certain > locations elsewhere in the world. In the future a more flexible > identification system may allow building of IDEA in countries for > which it is not restricted. > > US USERS: ^^ (and others follow throughout the remainder of the doc) -- Keith Ward N5OOD kward@Panther.net ...!rwsys!rowdy!kward =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= I don't suffer from insanity, I enjoy every minute of it. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 22:48: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from rectorat.ac-toulouse.fr (rectorat.ac-toulouse.fr [194.254.31.193]) by hub.freebsd.org (Postfix) with ESMTP id 9AFD3154EE for ; Wed, 26 Jan 2000 22:48:03 -0800 (PST) (envelope-from jaco@titine.fr.eu.org) Received: from alex.titine.fr.eu.org ([194.254.31.185]) by rectorat.ac-toulouse.fr (8.8.8/8.8.8) with ESMTP id HAA14581; Thu, 27 Jan 2000 07:44:40 +0100 (MET) Received: by alex.titine.fr.eu.org (Postfix, from userid 1000) id 3281C5D14F; Wed, 26 Jan 2000 20:33:31 +0100 (CET) To: Matt Miller Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sendmail on current References: <20000126114704.A1586@daffy.mics.net> From: Eric Jacoboni Date: 26 Jan 2000 20:33:31 +0100 In-Reply-To: Matt Miller's message of "Wed, 26 Jan 2000 11:47:04 -0700" Message-ID: <87k8kw4ohg.fsf@alex.titine.fr.eu.org> Lines: 25 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Bryce Canyon" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Miller writes: > It hangs on the startup of sendmail. I have replaced sendmail on my > system with Postfix. Addtionally, I have the following line in > /etc/make.conf > > NO_SENDMAIL= true That's ok : the 'make replace' of the postfix port replace /usr/sbin/sendmail (see the /usr/port/mail/postfix/Makefile) but, now in CURRENT, /usr/sbin/sendmail is a symlink to /usr/sbin/mailwrapper (see man mailwrapper). In CURRENT, the command 'sendmail' runs the mailwrapper program which, in turn, runs the correct ones according to /etc/mail/mailer.conf (there's an exemple in 'man mailer.conf'). So, to take advantage of MTA wrapping, don't do a 'make replace' when installing Postfix but rather edit /etc/mail/mailer.conf. Hope this helps, -- Eric Jacoboni Ta mère, son mot de passe c'est Ğ toto ğ ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 23: 8:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from Eagle.ZGIA.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with ESMTP id A7FB2154CB for ; Wed, 26 Jan 2000 23:08:14 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by Eagle.ZGIA.zp.ua (8.9.3/8.9.3) with ESMTP id JAA32297; Thu, 27 Jan 2000 09:02:45 +0200 (EET) (envelope-from laa@zgia.zp.ua) X-Authentication-Warning: Eagle.ZGIA.zp.ua: laa owned process doing -bs Date: Thu, 27 Jan 2000 09:02:45 +0200 (EET) From: Alexandr Listopad To: Chris Piazza Cc: freebsd-current@FreeBSD.ORG Subject: Re: help! need kernel! In-Reply-To: <20000126104945.A4657@norn.ca.eu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cpiazz>> hello! cpiazz>> cpiazz>> I have Abit motherboard with ATA-66 support. cpiazz>> I try to install FreeBSD-CURRENT, all good when install, but after reboot cpiazz>> kernel boots, but ask me a root device, when I press '?', there are no cpiazz>> 'ad' device (this is my HDD). ;( As I understand - there are no support in cpiazz>> that kernel for my HDD... ;( cpiazz>> cpiazz>> As I understand there are one way to help me - create new kernel with cpiazz>> ata-pci0 support. Thanks you for your answer! cpiazz> cpiazz>The boot floppies have ATA in the kernel. I installed a new system on cpiazz>a BP6 with the hard drive on one of the HPT366 controllers just fine cpiazz>about two weeks ago. Sorry, but I have no idea what is going on cpiazz>here.. I just wanted to say that it worked for me.... I had installed FreeBSD-CURRENT on my PC, from flopppies and ftp, all ok. But after reboot and press F3 new kernel boots (!) and after test wd0 and some other devices (no ata-pci) ask me: from what partition we will boot? My root partition is ad4s3a, but its don't work... ;< I have a question - where from the kernel boots? ;) And why it don't work on ad4s3a???? cpiazz> cpiazz>ata-pci1: port 0xd400-0xd4ff,0xd000-0xd003, cpiazz>0xcc00-0xcc07 irq 18 at device 19.0 on pci0 cpiazz>... cpiazz>ad4: 12949MB disk at ata2 as master mode UDMA66 cpiazz> cpiazz>BTW, sos, if you're reading this: I like this format for reporting cpiazz>the hard drives present a lot better :-). cpiazz> What is your HPT-366 (Abit BE6) BIOS ver? Thanks. Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 23:30:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id 6E4431501C for ; Wed, 26 Jan 2000 23:30:13 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id IAA38398; Thu, 27 Jan 2000 08:30:09 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <388FF400.66CD84F8@fernuni-hagen.de> Date: Thu, 27 Jan 2000 08:30:08 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: My atapi-cdrom is back! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG with version 1.44 of ata-all.c i have my cdrom back. Last evening making world succeeded with a current system! -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 23:31:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id DC8CC15564 for ; Wed, 26 Jan 2000 23:31:30 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA32633; Thu, 27 Jan 2000 08:30:58 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001270730.IAA32633@freebsd.dk> Subject: Re: FIC SD-11 not happy with ata In-Reply-To: <20000127053939.5BCE745@pinyon.org> from "Russell L. Carter" at "Jan 26, 2000 10:39:39 pm" To: rcarter@pinyon.org (Russell L. Carter) Date: Thu, 27 Jan 2000 08:30:58 +0100 (CET) Cc: freebsd@gndrsh.dnsmgr.net (Rodney W. Grimes), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Russell L. Carter wrote: > > Yah... as before ok I fixed this by swapping in an ASUS K7M (forget the audio, > I can't figure that one out) Working on it :) > For all of the bitching on Soren's ata driver, I'd like to > make this observation on a 500MHz/256MB ASUS K7 systemm, bonnie -s 500: > > ad1: 19574MB [39770/16/63] at ata1-master using UDMA66 > > Seeker 1...Seeker 2...Seeker 3...start 'em...done...done...done... > -------Sequential Output-------- ---Sequential Input-- --Random- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks-- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CU > 500 20650 84.1 20805 30.8 5644 14.8 22111 86.2 21253 21.1 148.9 1.4 > > Um, that ad1 drive cost me $224US, direct from the IBM mothership. Yup, those new IBM drives (the DPTA series) are pretty cool.... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Jan 26 23:36:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0FB7C1542B for ; Wed, 26 Jan 2000 23:36:10 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id IAA33837; Thu, 27 Jan 2000 08:36:06 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001270736.IAA33837@freebsd.dk> Subject: Re: My ATAPI CD not come ready In-Reply-To: <388F73D0.80AD5C39@freenet.co.uk> from Alex at "Jan 26, 2000 10:23:12 pm" To: ak@freenet.co.uk (Alex) Date: Thu, 27 Jan 2000 08:36:06 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex wrote: > > OK - here's the part relevant to ata: > > > ata-pci0: port 0xfcf0-0xfcff at device > 1.1 on pci0 > ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xfcf0 > ata0: mask=03 status0=50 status1=00 > ata0: mask=03 status0=50 status1=00 > ata0: devices = 0x1 > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xfcf8 > ata1: mask=03 status0=00 status1=00 > ata1: mask=03 status0=00 status1=00 > ata1: devices = 0xc Here it sees two devices, apparently you cdrom is reacting both on master AND slave addresses :( > ata1-slave: ata_command: timeout waiting for intr > ata1-slave: identify failed But when we try to talk to it it fails... > ata0-master: success setting up UDMA2 mode on PIIX4 chip But when we try to talk to it it fails... > Any ideas? I'll try to come up with a patch that solves this... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 0:23:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9FD8D14D39 for ; Thu, 27 Jan 2000 00:23:22 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id AAA36943 for ; Thu, 27 Jan 2000 00:23:21 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id AAA52231 for current@freebsd.org; Thu, 27 Jan 2000 00:23:23 -0800 (PST) (envelope-from obrien) Date: Thu, 27 Jan 2000 00:23:23 -0800 From: "David O'Brien" To: current@freebsd.org Subject: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-passwd Message-ID: <20000127002323.B52191@dragon.nuxi.com> Reply-To: obrien@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would appreciate it if those that want things changed would please try Sheldon's `sed' expression below and report back how it worked for you. ----- Forwarded message from Sheldon Hearn ----- To: "David E. O'Brien" Date: Wed, 26 Jan 2000 18:44:47 +0200 As discussed on the freebsd-current mailing list, I think you'll find that you missed out a few characters in the new class that defines the characters that should not appear at the beginning of affected lines: > - sed 's/^\([<>] [^:]*\):[^:]*:/\1:(password):/' > + sed 's/^\([^:]*\):[^:]*:/\1:(password):/' I think what you really want is: sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/' ----- End forwarded message ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 0:39:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 4E2771538B for ; Thu, 27 Jan 2000 00:39:13 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.3/8.9.3) id JAA55820; Thu, 27 Jan 2000 09:39:11 +0100 (CET) (envelope-from des@flood.ping.uio.no) To: current@freebsd.org Subject: world breakage? From: Dag-Erling Smorgrav Date: 27 Jan 2000 09:39:10 +0100 Message-ID: Lines: 53 User-Agent: Gnus/5.0802 (Gnus v5.8.2) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sources from ~12 hours ago: ===> usr.bin/kdump cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c /usr/src/usr.bin/kdump/kdump.c cc -O -pipe -I/usr/src/usr.bin/kdump/../ktrace -I/usr/src/usr.bin/kdump/../.. -I/usr/obj/usr/src/i386/usr/include -c ioctl.c In file included from ioctl.c:79: /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined /usr/obj/usr/src/i386/usr/include/pccard/cardinfo.h:80: warning: this is the location of the previous definition In file included from ioctl.c:96: /usr/obj/usr/src/i386/usr/include/sys/cdrio.h:59: warning: `CDRIOCBLANK' redefined /usr/obj/usr/src/i386/usr/include/sys/wormio.h:102: warning: this is the location of the previous definition In file included from ioctl.c:30: /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:883: syntax error before `bus_dmamap_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1016: syntax error before `bus_dmamap_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1024: syntax error before `bus_space_tag_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1028: syntax error before `bus_addr_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1045: syntax error before `bus_dma_tag_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1136: syntax error before `bus_addr_t' /usr/obj/usr/src/i386/usr/include/dev/dpt/dpt.h:1273: syntax error before `bus_space_tag_t' In file included from ioctl.c:33: /usr/obj/usr/src/i386/usr/include/dev/vinum/vinumio.h:104: `MAXNAME' undeclared here (not in a function) ioctl.c: In function `ioctlname': ioctl.c:140: sizeof applied to an incomplete type ioctl.c:236: sizeof applied to an incomplete type ioctl.c:306: sizeof applied to an incomplete type ioctl.c:374: sizeof applied to an incomplete type ioctl.c:694: sizeof applied to an incomplete type ioctl.c:1074: sizeof applied to an incomplete type ioctl.c:1422: sizeof applied to an incomplete type ioctl.c:1470: sizeof applied to an incomplete type ioctl.c:1838: `dpt_perf_t' undeclared (first use in this function) ioctl.c:1838: (Each undeclared identifier is reported only once ioctl.c:1838: for each function it appears in.) ioctl.c:1874: sizeof applied to an incomplete type *** Error code 1 Stop in /usr/src/usr.bin/kdump. *** Error code 1 Stop in /usr/src/usr.bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 1: 3:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id BBF011555E for ; Thu, 27 Jan 2000 01:03:29 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA37151; Thu, 27 Jan 2000 01:03:27 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id BAA52482; Thu, 27 Jan 2000 01:03:29 -0800 (PST) (envelope-from obrien) Date: Thu, 27 Jan 2000 01:03:29 -0800 From: "David O'Brien" To: Dag-Erling Smorgrav Cc: current@freebsd.org Subject: Re: world breakage? Message-ID: <20000127010329.C52191@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from des@flood.ping.uio.no on Thu, Jan 27, 2000 at 09:39:10AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 09:39:10AM +0100, Dag-Erling Smorgrav wrote: > Sources from ~12 hours ago: > ===> usr.bin/kdump ... > In file included from ioctl.c:79: > /usr/obj/usr/src/i386/usr/include/sys/memrange.h:18: warning: `MDF_ACTIVE' redefined Peter Wemm fixed this as src/include/Makefile rev 1.109 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 2:24:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A73861553E; Thu, 27 Jan 2000 02:24:41 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 12Dm6P-000F7Y-00; Thu, 27 Jan 2000 12:24:37 +0200 From: Sheldon Hearn To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-passwd In-reply-to: Your message of "Thu, 27 Jan 2000 00:23:23 PST." <20000127002323.B52191@dragon.nuxi.com> Date: Thu, 27 Jan 2000 12:24:36 +0200 Message-ID: <58105.948968676@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000 00:23:23 PST, "David O'Brien" wrote: > I think what you really want is: > > sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/' Eeek, I don't know why I sent you that. It should have been: sed 's/^\([ +-][^+-][^:]*\):[^:]*:/\1:(password):/' Sorry about that. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 3:49:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 58B0214DF4 for ; Thu, 27 Jan 2000 03:49:34 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id UAA05228 for ; Thu, 27 Jan 2000 20:49:27 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id UAA25874; Thu, 27 Jan 2000 20:49:26 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id UAA23991 for ; Thu, 27 Jan 2000 20:49:25 +0900 (JST) To: freebsd-current@freebsd.org Subject: realhostname_sa bug X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000127205008V.shin@nd.net.fujitsu.co.jp> Date: Thu, 27 Jan 2000 20:50:08 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 47 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There was a bug in realhostname_sa() in lib/libutil and sometime daemon using it dies, such as telnetd. I think following patch will fix it, but now checking make world before actually committing it. If anyone experienced same problem, please try following patch. Sorry for your troubles. Yoshinobu Inoue Index: realhostname.c =================================================================== RCS file: /home/ncvs/src/lib/libutil/realhostname.c,v retrieving revision 1.4 diff -u -r1.4 realhostname.c --- realhostname.c 2000/01/25 14:51:57 1.4 +++ realhostname.c 2000/01/27 11:37:08 @@ -122,8 +122,10 @@ port = ((struct sockinet *)addr)->si_port; ((struct sockinet *)addr)->si_port = 0; if (!memcmp(sa, addr, sa->sa_len)) { - strncpy(host, res->ai_canonname, - hsize); + if (res->ai_canonname != 0) + strncpy(host, + res->ai_canonname, + hsize); result = HOSTNAME_FOUND; ((struct sockinet *)addr)->si_port = port; @@ -146,8 +148,10 @@ if (IN6_IS_ADDR_V4MAPPED(in6) && !memcmp(&in6->s6_addr[12], in, sizeof(*in))) { - strncpy(host, res->ai_canonname, - hsize); + if (res->ai_canonname != 0) + strncpy(host, + res->ai_canonname, + hsize); result = HOSTNAME_FOUND; break; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 4:11:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id D5C81155F2; Thu, 27 Jan 2000 04:11:48 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id EAA76788; Thu, 27 Jan 2000 04:11:38 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001271211.EAA76788@gndrsh.dnsmgr.net> Subject: Re: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-passwd In-Reply-To: <58105.948968676@axl.noc.iafrica.com> from Sheldon Hearn at "Jan 27, 2000 12:24:36 pm" To: sheldonh@uunet.co.za (Sheldon Hearn) Date: Thu, 27 Jan 2000 04:11:38 -0800 (PST) Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > On Thu, 27 Jan 2000 00:23:23 PST, "David O'Brien" wrote: > > > I think what you really want is: > > > > sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/' > > Eeek, I don't know why I sent you that. It should have been: > > sed 's/^\([ +-][^+-][^:]*\):[^:]*:/\1:(password):/' IMNSO sed is the wrong tool here, awk can deal with the password file much easier than sed and should handle just about any input just so long as it doesn't add any :'s to the lines that we are trying to mungle the password out of: BEGIN {FS=":"; OFS=":"; ORS=""} // {if (NF==10) { print $1,"(password):" for (n = 3; n <=NF; n++) print $n,""; } else print $0; print "\n"; Defantily works on diff, diff -u and diff -c. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 4:17:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from viper.columbus.rr.com (viper.columbus.rr.com [204.210.252.254]) by hub.freebsd.org (Postfix) with ESMTP id 7213015543 for ; Thu, 27 Jan 2000 04:17:51 -0800 (PST) (envelope-from dzerkel@columbus.rr.com) Received: from columbus.rr.com (dhcp26140113.columbus.rr.com [24.26.140.113]) by viper.columbus.rr.com (8.9.3/8.9.3) with ESMTP id HAA06108 for ; Thu, 27 Jan 2000 07:17:45 -0500 (EST) Message-ID: <38903769.38338FE4@columbus.rr.com> Date: Thu, 27 Jan 2000 07:17:45 -0500 From: "Danny J. Zerkel" Organization: Zerkular Software X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: Russian, ru, en MIME-Version: 1.0 To: FreeBSD Current Subject: pmap_remove_pages panic during installworld Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been getting panics recently while trying to do installworld while running at single user on recent kernels. Fatal trap 12: page fault while in kernel mode mp_lock = 01000002; cpuid = 1; lapic.id = 00000000 fault virtual address = 0xc15ccff0 fault code = supervisor write, page not present instruction pointer = 0x8:0xc0225250 stack pointer = 0x10:0xc767f960 frame pointer = 0x10:0xc767f970 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 19387 (sh) interrupt mask = net bio cam <- SMP: XXX kernel: tyep 12 trap, code = 0 Stopped at pmap_remove_pages+0xc4: decl 0(%ecx) db> trace pmap_remove_pages(c81df528,0,bfc00000,1,c71c2034) at pmap_remove_pages+0xc4 exec_new_vmspace(c767fe6c,1,c767fe6c,c767ff80,0) at exec_new_vmspace+0xfd execve(c81da700,c767ff80,80bf570,ffffffff,80bf5b0) at execve+0x1f5 syscall(2f,2f,2f,80bf5b0,fffffff) at syscall+0x176 Xint0x80_syscall() at Xint0x80_syscall+0x31 I don't have a dmesg from the panicing kernel and kernel.old is from 29 Dec 1999. I also don't have a crash dump (bad device name in dumpdev, now corrected). I will try to get these things, if I get a chance to try again. Things in the system: SMP on Asus P2B-DS motherboard softupdates on usb recently enabled, but no peripherals yet More information to follow... -- Danny J. Zerkel dzerkel@columbus.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 4:27: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 1FAF91558E; Thu, 27 Jan 2000 04:26:56 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12Do0Q-000PKv-00; Thu, 27 Jan 2000 14:26:34 +0200 From: Sheldon Hearn To: "Rodney W. Grimes" Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-passwd In-reply-to: Your message of "Thu, 27 Jan 2000 04:11:38 PST." <200001271211.EAA76788@gndrsh.dnsmgr.net> Date: Thu, 27 Jan 2000 14:26:33 +0200 Message-ID: <97396.948975993@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000 04:11:38 PST, "Rodney W. Grimes" wrote: > > sed 's/^\([ +-][^+-][^:]*\):[^:]*:/\1:(password):/' > > IMNSO sed is the wrong tool here, No arguments from me, since my awk skills are limited. However, I'll point out that sed is doing a decent job without turning into an invocation mess. The awk program you sent is much longer. Oh, and it produces absolutely no output whatsoever over here. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 4:39:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id 8523C15525 for ; Thu, 27 Jan 2000 04:39:44 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id NAA41260; Thu, 27 Jan 2000 13:39:39 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <38903C8A.C9A83021@fernuni-hagen.de> Date: Thu, 27 Jan 2000 13:39:38 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: ASDM and linux emulation? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to use an ASDM (backup software) with linux-emulation. I get the following in /var/log/messages: es-i2 /kernel: linux: syscall setresuid is obsoleted\ or not implemented (pid=41052) Jan 27 13:12:42 es-i2 /kernel: pid 41052 (dsm), \ uid 0: exited on signal 11 (core dumped) as netscape and acroread work quite good i think the core dump is related to the former failure. What is the problem with this syscall? This can be a show stopper for the server box ... I hate all this silly problems with mandrake-linux etc. -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 5: 5:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from golf.dax.net (golf.dax.net [193.216.69.103]) by hub.freebsd.org (Postfix) with ESMTP id B95D1156EF for ; Thu, 27 Jan 2000 05:05:11 -0800 (PST) (envelope-from telde@online.no) Received: from delta.shacknet.nu ([193.216.101.70]) by golf.dax.net (8.9.3/8.9.3) with ESMTP id OAA20428 for ; Thu, 27 Jan 2000 14:06:32 +0100 (MET) Received: by delta.shacknet.nu (Postfix, from userid 1001) id 5A1657FF3; Thu, 27 Jan 2000 14:04:57 +0100 (CET) Date: Thu, 27 Jan 2000 14:04:56 +0100 From: Terje Elde To: current@FreeBSD.ORG Subject: Re: pcm - stutters Message-ID: <20000127140456.A27386@best.xti.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from n_hibma@webweaving.org on Tue, Jan 25, 2000 at 12:33:55AM +0000 X-Mailer: Mutt http://www.mutt.org/ X-Editor: Vim http://www.vim.org/ X-IRC: ircii!epic4-2000 - prevail[1214] Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Nick Hibma (n_hibma@webweaving.org) [000125 12:42]: > The output of my ESS 1869 stutters whenever there is no new data fed to > it. For example pressing Ctrl-Z, or heavy disk usage (normally making > mpg123 jump). The stuttering is repetition of one short fragment of > about a quarter of a second, indefinitely > > Anything I can try with this machine current as of jan.24 02:00 GMT? I'm running FreeBSD 4.0-CURRENT #17: Wed Jan 26 14:30:19 CET 2000 and a laptop with a ESS1869. Prior to this kernel, it used to stutter indefinitely when I stopped the application playing, for example mpg123. It still stutters when I background it with ctrl-z, but does *not* stutter when I kill the application anymore. Terje Elde -- Ex, de... Yv oek sqd huqt jxyi jxud jxqj cuqdi oek'lu rheaud co udshofjyed. DEM te oek iuu mxo mu duut ijhedw shofje? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 5:49:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 63CCB14E20 for ; Thu, 27 Jan 2000 05:49:50 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id 61F48254F1; Thu, 27 Jan 2000 08:49:41 -0500 (EST) Received: by osaka.louisville.edu (Postfix, from userid 15) id 9797718605; Thu, 27 Jan 2000 08:49:39 -0500 (EST) Date: Thu, 27 Jan 2000 08:49:39 -0500 From: Keith Stevenson To: "F. Heinrichmeyer" Cc: "freebsd-current@FreeBSD.ORG" Subject: Re: ASDM and linux emulation? Message-ID: <20000127084939.B32579@osaka.louisville.edu> References: <38903C8A.C9A83021@fernuni-hagen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <38903C8A.C9A83021@fernuni-hagen.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 01:39:38PM +0100, F. Heinrichmeyer wrote: > I would like to use an ASDM (backup software) with linux-emulation. I > get > the following in /var/log/messages: Have you tried the SCO client with the IBCS module loaded? I've been using it with great success for a while. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 5:50: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebox.impact-online.com (freebox.impact-online.com [210.206.9.2]) by hub.freebsd.org (Postfix) with ESMTP id CC420155FB for ; Thu, 27 Jan 2000 05:49:45 -0800 (PST) (envelope-from smlee@impact-online.com) Received: from leesm (leesm.iol.co.kr [210.206.9.42]) by freebox.impact-online.com (8.9.3/8.9.3) with SMTP id WAA77335 for ; Thu, 27 Jan 2000 22:49:35 +0900 (KST) (envelope-from smlee@impact-online.com) Reply-To: From: =?ks_c_5601-1987?B?wMy787nO?= To: Subject: subscribe freebsd-current Date: Thu, 27 Jan 2000 22:49:06 +0900 Message-ID: <000b01bf68cd$49bb4fa0$2a09ced2@leesm> MIME-Version: 1.0 Content-Type: text/plain; charset="ks_c_5601-1987" Content-Transfer-Encoding: base64 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG c3Vic2NyaWJlIGZyZWVic2QtY3VycmVudA0KDQoNCg== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 6: 3:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 7833515624 for ; Thu, 27 Jan 2000 06:03:36 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12DpUX-00053o-00; Thu, 27 Jan 2000 16:01:45 +0200 From: Sheldon Hearn To: Eric Jacoboni Cc: Matt Miller , freebsd-current@FreeBSD.ORG Subject: Re: Sendmail on current In-reply-to: Your message of "26 Jan 2000 20:33:31 +0100." <87k8kw4ohg.fsf@alex.titine.fr.eu.org> Date: Thu, 27 Jan 2000 16:01:45 +0200 Message-ID: <19455.948981705@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Jan 2000 20:33:31 +0100, Eric Jacoboni wrote: > in CURRENT, /usr/sbin/sendmail is a symlink to /usr/sbin/mailwrapper > (see man mailwrapper). No, it's a hard link. I only mention this because your explanation makes it sound like mailwrapper generates much more overhead than it really does: > In CURRENT, the command 'sendmail' runs the mailwrapper program which, > in turn, runs the correct ones according to /etc/mail/mailer.conf (there's > an exemple in 'man mailer.conf'). Anyway, this guy's problem is just the location of mailer.conf, which you got right, so he should be fine. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 6:27:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id 7A87D15665 for ; Thu, 27 Jan 2000 06:26:53 -0800 (PST) (envelope-from jaco@titine.fr.eu.org) Received: from titine.fr.eu.org (toulouse-50-23.dial.proxad.net [212.27.50.23]) by postfix1.free.fr (Postfix) with ESMTP id 8907C283C7; Thu, 27 Jan 2000 15:26:39 +0100 (MET) Received: by titine.fr.eu.org (Postfix, from userid 1000) id 7C64515135; Thu, 27 Jan 2000 15:25:55 +0100 (CET) To: Sheldon Hearn Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sendmail on current References: <19455.948981705@axl.noc.iafrica.com> From: Eric Jacoboni Date: 27 Jan 2000 15:25:55 +0100 In-Reply-To: Sheldon Hearn's message of "Thu, 27 Jan 2000 16:01:45 +0200" Message-ID: <87k8kvh9qk.fsf@titine.fr.eu.org> Lines: 25 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Bryce Canyon" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sheldon Hearn writes: > On 26 Jan 2000 20:33:31 +0100, Eric Jacoboni wrote: > > > in CURRENT, /usr/sbin/sendmail is a symlink to /usr/sbin/mailwrapper > > (see man mailwrapper). > > No, it's a hard link. I only mention this because your explanation > makes it sound like mailwrapper generates much more overhead than it > really does: No, not on my box (as far as i believe 'ls' and 'file' ;-) : % ls -l /usr/sbin/sendmail lrwxr-xr-x 1 root wheel 21 26 jan 23:54 /usr/sbin/sendmail -> /usr/sbin/mailwrapper % file /usr/sbin/sendmail /usr/sbin/sendmail: symbolic link to /usr/sbin/mailwrapper The mailwrapper manpage also pretends it's a symlink... -- --------------------------------------------------------- Éric Jacoboni Ğ No sport, cigars! ğ (W. Churchill) --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 6:28:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 71F03156C5 for ; Thu, 27 Jan 2000 06:28:15 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12Dpts-0005B7-00; Thu, 27 Jan 2000 16:27:56 +0200 From: Sheldon Hearn To: Eric Jacoboni Cc: freebsd-current@FreeBSD.ORG Subject: Re: Sendmail on current In-reply-to: Your message of "27 Jan 2000 15:25:55 +0100." <87k8kvh9qk.fsf@titine.fr.eu.org> Date: Thu, 27 Jan 2000 16:27:56 +0200 Message-ID: <19908.948983276@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27 Jan 2000 15:25:55 +0100, Eric Jacoboni wrote: > No, not on my box (as far as i believe 'ls' and 'file' ;-) : > > % ls -l /usr/sbin/sendmail > lrwxr-xr-x 1 root wheel 21 26 jan 23:54 /usr/sbin/sendmail -> > /usr/sbin/mailwrapper My humble apologies. No more drugs for me. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 6:29:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from rectorat.ac-toulouse.fr (rectorat.ac-toulouse.fr [194.254.31.193]) by hub.freebsd.org (Postfix) with ESMTP id EA06515789 for ; Thu, 27 Jan 2000 06:29:07 -0800 (PST) (envelope-from jaco@titine.fr.eu.org) Received: from alex.titine.fr.eu.org (toulouse-51-26.dial.proxad.net [212.27.51.26]) by rectorat.ac-toulouse.fr (8.8.8/8.8.8) with ESMTP id PAA28932; Thu, 27 Jan 2000 15:00:55 +0100 (MET) Received: by alex.titine.fr.eu.org (Postfix, from userid 1000) id 80C6E5D14B; Thu, 27 Jan 2000 14:59:52 +0100 (CET) To: Yoshinobu Inoue Cc: culverk@wam.umd.edu, freebsd-current@FreeBSD.ORG Subject: Re: ipsec errors References: <20000127130559K.shin@nd.net.fujitsu.co.jp> <20000127134647Y.shin@nd.net.fujitsu.co.jp> From: Eric Jacoboni Date: 27 Jan 2000 14:59:52 +0100 In-Reply-To: Yoshinobu Inoue's message of "Thu, 27 Jan 2000 13:46:47 +0900" Message-ID: <87k8kvsjhj.fsf@alex.titine.fr.eu.org> Lines: 17 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Bryce Canyon" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yoshinobu Inoue writes: > I just added debug flag check instead of changing syslog > level. > Could you please try the following patch to > usr.sbin/inetd/inetd.c ? Ok, i had the same pbs with ipsec messages at startup (since my last make world, yesterday evening)... I've applied your patch : the messages have gone... thanks, -- Eric Jacoboni Ta mère, son mot de passe c'est Ğ toto ğ ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 6:52:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 7A3931566F for ; Thu, 27 Jan 2000 06:52:08 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id XAA23293; Thu, 27 Jan 2000 23:51:51 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id XAA29807; Thu, 27 Jan 2000 23:51:50 +0900 (JST) Received: from localhost ([192.168.245.186]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id XAA04337; Thu, 27 Jan 2000 23:51:49 +0900 (JST) To: jaco@titine.fr.eu.org Cc: culverk@wam.umd.edu, freebsd-current@FreeBSD.ORG Subject: Re: ipsec errors In-Reply-To: <87k8kvsjhj.fsf@alex.titine.fr.eu.org> References: <20000127130559K.shin@nd.net.fujitsu.co.jp> <20000127134647Y.shin@nd.net.fujitsu.co.jp> <87k8kvsjhj.fsf@alex.titine.fr.eu.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000127235229Y.shin@nd.net.fujitsu.co.jp> Date: Thu, 27 Jan 2000 23:52:29 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 17 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > level. > > Could you please try the following patch to > > usr.sbin/inetd/inetd.c ? > > Ok, i had the same pbs with ipsec messages at startup (since my last > make world, yesterday evening)... > > I've applied your patch : the messages have gone... > > thanks, > -- > Eric Jacoboni Thanks, I committed it. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 6:53:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 17A0914A21 for ; Thu, 27 Jan 2000 06:53:34 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:K2xeZAyHTHrJAqU+GnmcN8UdQKchYDD/@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id XAA07069; Thu, 27 Jan 2000 23:53:27 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id XAA29367; Thu, 27 Jan 2000 23:59:04 +0900 (JST) Message-Id: <200001271459.XAA29367@zodiac.mech.utsunomiya-u.ac.jp> To: Donn Miller Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Moused hanging... In-reply-to: Your message of "Mon, 24 Jan 2000 08:46:07 EST." <388C579F.835E05C0@cvzoom.net> References: <200001240503.OAA20809@zodiac.mech.utsunomiya-u.ac.jp> <388C579F.835E05C0@cvzoom.net> Date: Thu, 27 Jan 2000 23:59:04 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Well, it's an ISA bus mouse. I bought this thing back in 1994. It's >an IMSI mouse. I'll bet this stupid thing could last for 5 more >years. :-) > >> I cannot immediately see why only the mouse suddenly died, while the >> rest of the system was healthy, > >Yeah, I don't know. It happens extremely rarely. Maybe it's because >I have an ISA bus mouse. I suppose I really should be using a PS/2 or >USB mouse. (BTW, is a PS/2 mouse a type of bus mouse?) This may be "THE GREAT CASE OF LOST INTERRUPTS" :-) I haven't heard that the mse driver looses interrupts, but there may be a possibility that we loose interrupts on ISA bus under heavy load. The following patch will add a watch dog timer to the mse driver. When the bus mouse interrupt seems to be lost, it will print "mse0: lost interrupt?" and forcefully read from the bus mouse port. I hope it may get the thing going again. Kazu Index: mse.c =================================================================== RCS file: /src/CVS/src/sys/i386/isa/mse.c,v retrieving revision 1.48 diff -u -r1.48 mse.c --- mse.c 1999/10/06 13:01:55 1.48 +++ mse.c 2000/01/27 14:25:17 @@ -95,6 +95,7 @@ }; static ointhand2_t mseintr; +static timeout_t msetimeout; /* * Software control structure for mouse. The sc_enablemouse(), @@ -114,6 +115,8 @@ int sc_buttons; int sc_bytesread; u_char sc_bytes[MOUSE_SYS_PACKETSIZE]; + struct callout_handle sc_callout; + int sc_watchdog; mousehw_t hw; mousemode_t mode; mousestatus_t status; @@ -263,6 +266,7 @@ idp->id_ointr = mseintr; sc->sc_port = idp->id_iobase; + callout_handle_init(&sc->sc_callout); sc->mode.accelfactor = (idp->id_flags & MSE_CONFIG_ACCEL) >> 4; make_dev(&mse_cdevsw, unit << 1, 0, 0, 0600, "mse%d", unit); make_dev(&mse_cdevsw, (unit<<1)+1, 0, 0, 0600, "nmse%d", unit); @@ -293,6 +297,8 @@ sc->sc_obuttons = sc->sc_buttons = MOUSE_MSC_BUTTONS; sc->sc_deltax = sc->sc_deltay = 0; sc->sc_bytesread = sc->mode.packetsize = MOUSE_MSC_PACKETSIZE; + sc->sc_watchdog = FALSE; + sc->sc_callout = timeout(msetimeout, dev, hz*2); sc->mode.level = 0; sc->status.flags = 0; sc->status.button = sc->status.obutton = 0; @@ -320,6 +326,8 @@ struct mse_softc *sc = &mse_sc[MSE_UNIT(dev)]; int s; + untimeout(msetimeout, dev, sc->sc_callout); + callout_handle_init(&sc->sc_callout); s = spltty(); (*sc->sc_disablemouse)(sc->sc_port); sc->sc_flags &= ~MSESC_OPEN; @@ -545,6 +553,26 @@ } /* + * msetimeout: watchdog timer routine. + */ +static void +msetimeout(arg) + void *arg; +{ + dev_t dev; + struct mse_softc *sc; + + dev = (dev_t)arg; + sc = &mse_sc[MSE_UNIT(dev)]; + if (sc->sc_watchdog) { + printf("mse%d: lost interrupt?\n", MSE_UNIT(dev)); + mseintr(MSE_UNIT(dev)); + } + sc->sc_watchdog = TRUE; + sc->sc_callout = timeout(msetimeout, dev, hz); +} + +/* * mseintr: update mouse status. sc_deltax and sc_deltay are accumulative. */ static void @@ -602,6 +630,8 @@ sc->status.flags |= ((dx || dy) ? MOUSE_POSCHANGED : 0) | (sc->status.button ^ but); sc->status.button = but; + + sc->sc_watchdog = FALSE; /* * If mouse state has changed, wake up anyone wanting to know. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 7: 1:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 1AF2114A21; Thu, 27 Jan 2000 07:01:11 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id RAA59969; Thu, 27 Jan 2000 17:00:58 +0200 (EET) (envelope-from ru) Date: Thu, 27 Jan 2000 17:00:58 +0200 From: Ruslan Ermilov To: Peter Wemm Cc: current@FreeBSD.org Subject: src/include/Makefile,v 1.109 is broken Message-ID: <20000127170058.A57120@relay.ucb.crimea.ua> Mail-Followup-To: Peter Wemm , current@FreeBSD.org Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=opJtzjQTFsWo+cga X-Mailer: Mutt 0.95.3i X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii The latest src/include/Makefile,v 1.109 is broken. You will see what is spammed by executing the following: cd /usr/src/include; make symlinks copies DESTDIR=/FOO There should be no symlinked dirs in /FOO/usr/include after that, but... The idea was that `copies' should first undo all the things `symlinks' did, but it is broken now. An attached patch seems to fix the problem. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --opJtzjQTFsWo+cga Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=p Index: src/include/Makefile =================================================================== RCS file: /usr/FreeBSD-CVS/src/include/Makefile,v retrieving revision 1.109 diff -u -p -r1.109 Makefile --- Makefile 2000/01/26 17:38:51 1.109 +++ Makefile 2000/01/27 14:51:05 @@ -96,10 +96,13 @@ beforeinstall: ${SHARED} .endfor copies: -.for i in ${LDIRS} ${LNOHEADERDIRS} machine +.for i in ${LDIRS} ${LSYMSUBDIRS} machine if [ -h ${DESTDIR}/usr/include/$i ]; then \ rm -f ${DESTDIR}/usr/include/$i; \ fi +.endfor +.for i in ${LNOHEADERDIRS} + rm -rf ${DESTDIR}/usr/include/$i .endfor mtree -deU -f ${.CURDIR}/../etc/mtree/BSD.include.dist \ -p ${DESTDIR}/usr/include --opJtzjQTFsWo+cga-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 7:28:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from email.spcgroup.nl (email.spcgroup.nl [212.206.124.3]) by hub.freebsd.org (Postfix) with ESMTP id 46E69155F7 for ; Thu, 27 Jan 2000 07:28:51 -0800 (PST) (envelope-from e.mons@spcgroup.nl) Received: from spcgroup.nl (c187121244.telekabel.chello.nl [212.187.121.244]) by email.spcgroup.nl (8.9.3/8.9.3) with ESMTP id RAA09653 for ; Thu, 27 Jan 2000 17:39:02 +0100 Message-ID: <3890642D.F7E80EF0@spcgroup.nl> Date: Thu, 27 Jan 2000 16:28:45 +0100 From: Edwin Mons X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: ep0 incorrectly probed Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I downloaded the 2000/01/25 snapshot of current today. When I booted from floppy, this message showed up: ep0: eeprom failed to come ready (5 times) and a NIC address of 0:0:0:0:0:0 was reported back. When booting this machine with 3.4-RELEASE, the correct NIC address is reported. When ifconfiging the interface, the machine hangs. The kernel knows the right ioport/irq, and works correctly with both 3.4-RELEASE and Windows 95. I didn't install CURRENT on it, since I wanted to install it by FTP... Quick info of the machine: Pentium 100 P/I-P55SP4 rev 1.4 motherboard (SiS550x chipset) 32 MB RAM 3COM 509 ISA ethernet card (BNC) Hercules Stingray 64 video Edwin Mons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 7:29:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 673D6154A2 for ; Thu, 27 Jan 2000 07:29:17 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA18034; Thu, 27 Jan 2000 10:29:13 -0500 (EST) (envelope-from wollman) Date: Thu, 27 Jan 2000 10:29:13 -0500 (EST) From: Garrett Wollman Message-Id: <200001271529.KAA18034@khavrinen.lcs.mit.edu> To: current@freebsd.org Subject: Folks, please try to spread out your cvsups a bit better.... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I suspect I'm not the only mirror operator who sees a huge load spike early in the morning: ------- start of forwarded message (RFC 934 encapsulation) ------- From: root@xyz.lcs.mit.edu Apparently-To: Subject: xyz.lcs.mit.edu daily run output Date: Thu, 27 Jan 2000 01:59:01 -0500 (EST) [deletia] xyz up 7+10:08, 0 users, load 11.77, 9.93, 6.09 [deletia] ------- end ------- You'll probably get better service if you cvsup at 8 AM or 10 PM (ET). -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 7:35:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 7702314CE9 for ; Thu, 27 Jan 2000 07:35:35 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA07875; Thu, 27 Jan 2000 10:35:33 -0500 (EST) Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id KAA16061; Thu, 27 Jan 2000 10:35:26 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id KAA16057; Thu, 27 Jan 2000 10:35:25 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Thu, 27 Jan 2000 10:35:25 -0500 (EST) From: Kenneth Wayne Culver To: Yoshinobu Inoue Cc: freebsd-current@FreeBSD.ORG Subject: Re: ipsec errors In-Reply-To: <20000127134647Y.shin@nd.net.fujitsu.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm at work now, so I can't apply the patches till I go home again (at work I have Sun boxes and a linux box, blahh) ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= On Thu, 27 Jan 2000, Yoshinobu Inoue wrote: > > > Maybe there was a message on here that I overlooked, I'm not sure, but how > > > exactly do I get rid of them? > > > > It is not harmful but I should have lower the syslog level, > > sorry. > > I'll soon fix it. > > I just added debug flag check instead of changing syslog > level. > Could you please try the following patch to > usr.sbin/inetd/inetd.c ? > > Thanks, > Yoshinobu Inoue > > Index: inetd.c > =================================================================== > RCS file: /home/ncvs/src/usr.sbin/inetd/inetd.c,v > retrieving revision 1.75 > diff -u -r1.75 inetd.c > --- inetd.c 2000/01/25 14:52:10 1.75 > +++ inetd.c 2000/01/27 04:41:15 > @@ -1256,7 +1256,8 @@ > buf = ipsec_set_policy(policy_in, strlen(policy_in)); > if (buf != NULL) { > if (setsockopt(sep->se_fd, level, opt, > - buf, ipsec_get_policylen(buf)) < 0) { > + buf, ipsec_get_policylen(buf)) < 0 && > + debug != 0) { > syslog(LOG_ERR, > "%s/%s: ipsec initialization failed; %s", > sep->se_service, sep->se_proto, > @@ -1271,7 +1272,8 @@ > buf = ipsec_set_policy(policy_out, strlen(policy_out)); > if (buf != NULL) { > if (setsockopt(sep->se_fd, level, opt, > - buf, ipsec_get_policylen(buf)) < 0) { > + buf, ipsec_get_policylen(buf)) < 0 && > + debug != 0) { > syslog(LOG_ERR, > "%s/%s: ipsec initialization failed; %s", > sep->se_service, sep->se_proto, > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 8: 1:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 57F8A155AA for ; Thu, 27 Jan 2000 08:01:46 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id BAA15568; Fri, 28 Jan 2000 01:01:42 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id BAA17333; Fri, 28 Jan 2000 01:01:41 +0900 (JST) Received: from localhost ([192.168.245.45]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id BAA07015; Fri, 28 Jan 2000 01:01:40 +0900 (JST) To: culverk@wam.umd.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: ipsec errors In-Reply-To: References: <20000127134647Y.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000128010223Y.shin@nd.net.fujitsu.co.jp> Date: Fri, 28 Jan 2000 01:02:23 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm at work now, so I can't apply the patches till I go home again (at > work I have Sun boxes and a linux box, blahh) It is OK, because Eric Jacoboni kindly tried the patch instead. I already committed it. Thanks for taking care for it. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 8:13: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 598AA157E4 for ; Thu, 27 Jan 2000 08:12:54 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 12DrXM-0008nx-00; Thu, 27 Jan 2000 08:12:48 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Andy Farkas Cc: FreeBSD Current Subject: Re: ascii art in hosts.allow Message-Id: Date: Thu, 27 Jan 2000 08:12:48 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But...but... ITS SUCH AN EYE-SORE! all depends on what image of professionalism freebsd thinks it is trying to project. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 8:24:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from Eagle.ZGIA.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with ESMTP id AECC0156DA for ; Thu, 27 Jan 2000 08:24:33 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by Eagle.ZGIA.zp.ua (8.9.3/8.9.3) with ESMTP id SAA72089; Thu, 27 Jan 2000 18:20:08 +0200 (EET) (envelope-from laa@zgia.zp.ua) X-Authentication-Warning: Eagle.ZGIA.zp.ua: laa owned process doing -bs Date: Thu, 27 Jan 2000 18:20:08 +0200 (EET) From: Alexandr Listopad To: Chris Piazza Cc: freebsd-current@FreeBSD.ORG Subject: Re: help! need kernel! In-Reply-To: <20000126104945.A4657@norn.ca.eu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cpiazz>On Wed, Jan 26, 2000 at 07:26:30PM +0200, Alexandr Listopad wrote: cpiazz>> hello! cpiazz>> cpiazz>> I have Abit motherboard with ATA-66 support. cpiazz>> I try to install FreeBSD-CURRENT, all good when install, but after reboot cpiazz>> kernel boots, but ask me a root device, when I press '?', there are no cpiazz>> 'ad' device (this is my HDD). ;( As I understand - there are no support in cpiazz>> that kernel for my HDD... ;( cpiazz>> cpiazz>> As I understand there are one way to help me - create new kernel with cpiazz>> ata-pci0 support. cpiazz> cpiazz>The boot floppies have ATA in the kernel. I installed a new system on cpiazz>a BP6 with the hard drive on one of the HPT366 controllers just fine cpiazz>about two weeks ago. Sorry, but I have no idea what is going on cpiazz>here.. I just wanted to say that it worked for me.... cpiazz> cpiazz>ata-pci1: port 0xd400-0xd4ff,0xd000-0xd003, cpiazz>0xcc00-0xcc07 irq 18 at device 19.0 on pci0 cpiazz>... cpiazz>ad4: 12949MB disk at ata2 as master mode UDMA66 cpiazz> cpiazz>BTW, sos, if you're reading this: I like this format for reporting cpiazz>the hard drives present a lot better :-). All nice, in the install process... My disk is ad4sXX in install, but after reboot it is ad0xxx - why? Another questions in yesturdays cvsup I get full sources, but when I try to make world make says: /usr/src/tools/install.sh Can't open /usr/src/tools/install.sh *** Error code 2 ... there no tools/ dir in /usr/src - why? this is my supfile: *default host=cvsup2.ua.freebsd.org *default base=/usr/src-4.0 *default prefix=/usr/src-4.0 *default release=cvs *default tag=. *default delete use-rel-suffix doc-all src-base src-bin src-contrib src-etc src-gnu src-include src-lib src-libexec src-release src-sbin src-share src-sys src-usrbin src-usrsbin Thnaks. Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 8:34:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 02204151DA; Thu, 27 Jan 2000 08:34:14 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12Drs0-0006R1-00; Thu, 27 Jan 2000 18:34:08 +0200 From: Sheldon Hearn To: Ruslan Ermilov Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: src/include/Makefile,v 1.109 is broken In-reply-to: Your message of "Thu, 27 Jan 2000 17:00:58 +0200." <20000127170058.A57120@relay.ucb.crimea.ua> Date: Thu, 27 Jan 2000 18:34:08 +0200 Message-ID: <24738.948990848@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000 17:00:58 +0200, Ruslan Ermilov wrote: > An attached patch seems to fix the problem. Does anybody actually understand what's really going on in this file? Everyone uses the words "seems to" and "I think" when they're proposing fixes in this file. I propose that we hold out for a fix which is accompanied by comments that explain what the hell all these oddball variables are used for and why SHARED is overridden (or used at all in the buildworld case). Ruslan, if I misunderstood your words, please don't take offense. It's just that this'll be the 5th commit in this regard without comment from Marcel, who was responsible for rewriting most of this Makefile recently. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 8:53:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id EA250155C8 for ; Thu, 27 Jan 2000 08:53:13 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id e0RGr5N78703; Thu, 27 Jan 2000 11:53:05 -0500 (EST) Date: Thu, 27 Jan 2000 11:53:05 -0500 (EST) From: jack To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: Folks, please try to spread out your cvsups a bit better.... In-Reply-To: <200001271529.KAA18034@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Today Garrett Wollman wrote: > I suspect I'm not the only mirror operator who sees a huge load spike > early in the morning: I plead guilty, your honor. When are the low load times. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 8:53:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 0F6ED15750; Thu, 27 Jan 2000 08:53:31 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id SAA86537; Thu, 27 Jan 2000 18:52:26 +0200 (EET) (envelope-from ru) Date: Thu, 27 Jan 2000 18:52:26 +0200 From: Ruslan Ermilov To: Sheldon Hearn Cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: src/include/Makefile,v 1.109 is broken Message-ID: <20000127185226.A84871@relay.ucb.crimea.ua> Mail-Followup-To: Sheldon Hearn , Peter Wemm , current@FreeBSD.ORG References: <20000127170058.A57120@relay.ucb.crimea.ua> <24738.948990848@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <24738.948990848@axl.noc.iafrica.com>; from Sheldon Hearn on Thu, Jan 27, 2000 at 06:34:08PM +0200 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 06:34:08PM +0200, Sheldon Hearn wrote: > > > On Thu, 27 Jan 2000 17:00:58 +0200, Ruslan Ermilov wrote: > > > An attached patch seems to fix the problem. > > Does anybody actually understand what's really going on in this file? > Everyone uses the words "seems to" and "I think" when they're proposing > fixes in this file. > Disregard my "seems" word above, it really fixes the problem ;=) BTW, I has given a comment: | The idea was that `copies' should first undo all the | things `symlinks' did, but it is broken now. > I propose that we hold out for a fix which is accompanied by comments > that explain what the hell all these oddball variables are used for and > why SHARED is overridden (or used at all in the buildworld case). > Obviously, to speed up the building process. > Ruslan, if I misunderstood your words, please don't take offense. It's > just that this'll be the 5th commit in this regard without comment > from Marcel, who was responsible for rewriting most of this Makefile > recently. > I was told by Alexey Zelkin that Marcel was hired by some giant company, and he asked for FreeBSD vacation for some time (though I personally did not see such a message)... -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 9:12:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 3F27D1557D for ; Thu, 27 Jan 2000 09:12:29 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id MAA05036; Thu, 27 Jan 2000 12:12:15 -0500 (EST) Date: Thu, 27 Jan 2000 12:12:14 -0500 (EST) From: "Matthew N. Dodd" To: Edwin Mons Cc: current@FreeBSD.ORG Subject: Re: ep0 incorrectly probed In-Reply-To: <3890642D.F7E80EF0@spcgroup.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Edwin Mons wrote: > I downloaded the 2000/01/25 snapshot of current today. When I booted > from floppy, this message showed up: > > ep0: eeprom failed to come ready > (5 times) Humm... Please boot verbose and send me the output. This may require you to use a serial console. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 9:37: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from argon.blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 7320F1589A for ; Thu, 27 Jan 2000 09:36:56 -0800 (PST) (envelope-from will@blackdawn.com) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 1534319C0; Thu, 27 Jan 2000 12:36:49 -0500 (EST) Date: Thu, 27 Jan 2000 12:36:49 -0500 From: Will Andrews To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: Folks, please try to spread out your cvsups a bit better.... Message-ID: <20000127123648.B402@argon.blackdawn.com> References: <200001271529.KAA18034@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001271529.KAA18034@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Thu, Jan 27, 2000 at 10:29:13AM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 10:29:13AM -0500, Garrett Wollman wrote: > I suspect I'm not the only mirror operator who sees a huge load spike > early in the morning: The reason for this is probably because many people like to cron cvsup early in the morning, when they're not using the computer. You're right - they need to even it out during the day. > xyz up 7+10:08, 0 users, load 11.77, 9.93, 6.09 Wow, that high? I think xyz also does FTP mirror, doesn't it? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 9:38:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from email.spcgroup.nl (email.spcgroup.nl [212.206.124.3]) by hub.freebsd.org (Postfix) with ESMTP id 20AAF15185 for ; Thu, 27 Jan 2000 09:38:04 -0800 (PST) (envelope-from e.mons@spcgroup.nl) Received: from spcgroup.nl (c187121244.telekabel.chello.nl [212.187.121.244]) by email.spcgroup.nl (8.9.3/8.9.3) with ESMTP id TAA10591; Thu, 27 Jan 2000 19:48:04 +0100 Message-ID: <38908268.E17FFF57@spcgroup.nl> Date: Thu, 27 Jan 2000 18:37:44 +0100 From: Edwin Mons X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: current@freebsd.org Subject: Re: ep0 incorrectly probed References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > On Thu, 27 Jan 2000, Edwin Mons wrote: > > I downloaded the 2000/01/25 snapshot of current today. When I booted > > from floppy, this message showed up: > > > > ep0: eeprom failed to come ready > > (5 times) > > Humm... Please boot verbose and send me the output. This may require you > to use a serial console. Used my Palm III as console... Regards, Edwin Mons ok boot -v SMAP type=01 base=00000000 00000000 len=00000000 000a0000 SMAP type=02 base=00000000 000f0000 len=00000000 00010000 SMAP type=01 base=00000000 00100000 len=00000000 01f00000 SMAP type=02 base=00000000 fffe0000 len=00000000 00020000 Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-20000124-CURRENT #2: Mon Jan 24 16:18:58 GMT 2000 root@usw2.freebsd.org:/usr/src/sys/compile/BOOTMFS Calibrating clock(s) ... TSC clock: 99451420 Hz, i8254 clock: 1192915 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 99474313 Hz CPU: Pentium/P54C (99.47-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bf real memory = 33554432 (32768K bytes) Physical memory chunk(s): 0x00001000 - 0x0009ffff, 651264 bytes (159 pages) 0x005f9000 - 0x01ffdfff, 27283456 bytes (6661 pages) config> intro *** intro skipped *** avail memory = 26726400 (26100K bytes) bios32: Found BIOS32 Service Directory header at 0xc00fc810 bios32: Entry = 0xfcd20 (c00fcd20) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xcd50 pnpbios: Found PnP BIOS data at 0xc00fdb10 pnpbios: Entry = f0000:610 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc05e0000. Preloaded mfs_root "/mfsroot" at 0xc05e0090. Intel Pentium detected, installing workaround for F00F bug md0: Preloaded image 2949120 bytes at 0xc030e5f8 Creating DISK md0 md1: Malloc disk Creating DISK md1 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x80000084 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=55111039) npx0: on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 86318515 bytes/sec bzero() bandwidth = 43372657 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=55111039) pcib0: on motherboard found-> vendor=0x1039, dev=0x5511, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1039J, dev=0x5513, revid=0x07 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=0 map[10]: type 1, range 32, base 0000e800, size 3 map[14]: type 1, range 32, base 0000e400, size 2 map[18]: type 1, range 32, base 0000e000, size 3 map[1c]: type 1, range 32, base 0000d800, size 2 map[20]: type 1, range 32, base 0000d400, size 4 found-> vendor=0xedd8, dev=0xa099, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[10]: type 1, range 32, base fb800000, size 22 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 ata-pci0: port 0xd400-0xd40f,0xd800-0xd803,0xe000-0 xe007,0xe400-0xe403,0xe800-0xe807 irq 0 at device 1.1 on pci0 ata-pci0: Busmastering DMA supported ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xd400 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x1 ata0 at 0x01f0 irq 14 on ata-pci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xd408 ata1: mask=03 status0=00 status1=00 ata1: mask=03 status0=00 status1=00 ata1: devices = 0xc ata1 at 0x0170 irq 15 on ata-pci0 vga-pci0: mem 0xfb800000-0xfbbfffff at device 10.0 on pci0 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa0: if_ep: <3Com 3C509-BNC EtherLink III> at port 0x300-0x310 irq 10 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fe0: EEPROM(SSI): 0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 10: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 20: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 30: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 40: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 50: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 60: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 70: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 80: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): 90: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI): f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):100: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):110: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):120: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):130: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):140: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):150: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):160: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):170: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):180: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):190: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):1a0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):1b0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):1c0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):1d0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):1e0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fe0: EEPROM(SSI):1f0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 ata-isa1: already registered as ata1 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x330 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x334 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x230 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x234 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x130 bt0: Failed Status Reg Test - ff bt_isa_probe: Probe failed at 0x134 aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff aha0: status reg test failed ff atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0045 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x1d0000 psm0: current command byte:0045 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x0> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) pcic1: not probed (disabled) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A, console sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc_detect_fifo: PWord not supported ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached ppi0: on ppbus0 ep0: <3Com 3C509-BNC EtherLink III> at port 0x300-0x30f irq 10 on isa0 ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: eeprom failed to come ready. ep0: Ethernet address 00:00:00:00:00:00 bpf: ep0 attached isa_probe_children: probing PnP devices BIOS Geometries: 0:020cfe3f 0..524=525 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: sl0 attached bpf: lo0 attached ata_command: timeout waiting for interrupt ata1-slave : identify failed ata0-master: success setting up UDMA2 mode on SiS chip ad0: piomode=4 dmamode=2 udmamode=4 cblid=1 ad0: ATA-4 disk at ata0 as master ad0: 4126MB (8452080 sectors), 8944 cyls, 15 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 Creating DISK ad0 Creating DISK wd0 ata1-master: piomode=3 dmamode=1 udmamode=-1 dmaflag=1 ata1: simplex device, DMA on primary channel only acd0: CDROM drive at ata1 as master acd0: read 1377KB/s (1377KB/s), 256KB buffer, ??? acd0: Reads: CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/md0c start_init: trying /sbin/init start_init: trying /sbin/oinit start_init: trying /sbin/init.bak start_init: trying /stand/sysinstall /stand/sysinstall running as init on serial console These are the predefined terminal types available to sysinstall when running stand-alone. Please choose the closest match for your particular terminal. 1 ...................... Standard ANSI terminal. 2 ...................... VT100 or compatible terminal. 3 ...................... FreeBSD system console (color). 4 ...................... FreeBSD system console (monochrome). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 9:52:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id CEA6B156DE for ; Thu, 27 Jan 2000 09:52:50 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id MAA05614; Thu, 27 Jan 2000 12:52:48 -0500 (EST) Date: Thu, 27 Jan 2000 12:52:47 -0500 (EST) From: "Matthew N. Dodd" To: Edwin Mons Cc: current@freebsd.org Subject: Re: ep0 incorrectly probed In-Reply-To: <38908268.E17FFF57@spcgroup.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Using the boot configuration screen can you disable all devices that are not installed? I suspect something is clobbering the board after it is identified. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 9:58:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 82C7815750 for ; Thu, 27 Jan 2000 09:58:34 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id MAA05740; Thu, 27 Jan 2000 12:58:32 -0500 (EST) Date: Thu, 27 Jan 2000 12:58:32 -0500 (EST) From: "Matthew N. Dodd" To: Edwin Mons Cc: current@freebsd.org Subject: Re: ep0 incorrectly probed In-Reply-To: <38908268.E17FFF57@spcgroup.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Edwin Mons wrote: ... > isa0: if_ep: <3Com 3C509-BNC EtherLink III> at port 0x300-0x310 irq 10 ... > ep0: <3Com 3C509-BNC EtherLink III> at port 0x300-0x30f irq 10 on isa0 > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: eeprom failed to come ready. > ep0: Ethernet address 00:00:00:00:00:00 Actually, given that GENERIC contains: # grep 0x300 GENERIC device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 device fe0 at isa? port 0x300 device le0 at isa? port 0x300 irq 5 iomem 0xd0000 device cs0 at isa? port 0x300 device sn0 at isa? port 0x300 irq 10 I'm pretty sure that the device is getting annoyed with one of the above drivers. I'll add these drivers to my test kernel and see if a reset in the right place fixes things but in the mean time disable the above drivers in the visual config screen; it should work fine if you do that. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 10: 3:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from nets5.rz.rwth-aachen.de (nets5.rz.RWTH-Aachen.DE [137.226.144.13]) by hub.freebsd.org (Postfix) with ESMTP id 2879615505 for ; Thu, 27 Jan 2000 10:03:36 -0800 (PST) (envelope-from kuku@gilberto.physik.RWTH-Aachen.DE) Received: from campino.informatik.rwth-aachen.de (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by nets5.rz.rwth-aachen.de (8.9.1a/8.9.1/10) with ESMTP id TAA01742; Thu, 27 Jan 2000 19:03:32 +0100 (MET) Received: from gil.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.30.2]) by campino.informatik.rwth-aachen.de (8.9.1a/8.9.1/3) with ESMTP id TAA26569; Thu, 27 Jan 2000 19:03:52 +0100 (MET) Received: (from kuku@localhost) by gil.physik.rwth-aachen.de (8.9.3/8.6.9) id TAA14834; Thu, 27 Jan 2000 19:03:38 +0100 (CET) Date: Thu, 27 Jan 2000 19:03:38 +0100 From: Christoph Kukulies To: Gert Doering Cc: Christoph Kukulies , mgetty@greenie.muc.de, freebsd-current@freebsd.org Subject: Re: locking problem FreeBSD 3.4 - kermit and mgetty Message-ID: <20000127190338.C14674@gil.physik.rwth-aachen.de> References: <200001251951.UAA03088@gil.physik.rwth-aachen.de> <20000126231354.B886@greenie.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000126231354.B886@greenie.muc.de>; from gert@greenie.muc.de on Wed, Jan 26, 2000 at 11:13:55PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Jan 26, 2000 at 11:13:55PM +0100, Gert Doering wrote: > Hi, > > On Tue, Jan 25, 2000 at 08:51:40PM +0100, Christoph Kukulies wrote: > > But as a result mgetty gets into kermit's ways such that when a > > modem connection is made I suddenly get a modem prompt like > > +FCON as if someone (mgetty) is either messing with my local > > or the remote modem while kermit opens the connection. > > The modem is in fax mode, and has established a fax connection. Have > kermit send an AT+FCLASS=0 first. OK, this may be a repair but I'm wondering why that worked before and now I have to take special measures. Or is it perhaps kermit's fault? > > gert > -- > USENET is *not* the non-clickable part of WWW! > //www.muc.de/~gert/ > Gert Doering - Munich, Germany gert@greenie.muc.de > fax: +49-89-35655025 gert.doering@physik.tu-muenchen.de -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 10: 5: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from email.spcgroup.nl (email.spcgroup.nl [212.206.124.3]) by hub.freebsd.org (Postfix) with ESMTP id 29C3E14D11 for ; Thu, 27 Jan 2000 10:04:58 -0800 (PST) (envelope-from e.mons@spcgroup.nl) Received: from spcgroup.nl (c187121244.telekabel.chello.nl [212.187.121.244]) by email.spcgroup.nl (8.9.3/8.9.3) with ESMTP id UAA10714; Thu, 27 Jan 2000 20:15:07 +0100 Message-ID: <389088C3.C32BFEF4@spcgroup.nl> Date: Thu, 27 Jan 2000 19:04:51 +0100 From: Edwin Mons X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Matthew N. Dodd" Cc: current@freebsd.org Subject: strange ATA stuff (was: ep0 incorrectly probed) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > > Using the boot configuration screen can you disable all devices that are > not installed? > > I suspect something is clobbering the board after it is identified. > > -- > | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | > | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | > | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | I tried that. It worked. Thanks a lot! Looks like the fe0 driver was the one messing it up for my ep0. Now back to the install. Another weird thing: as you could see in the boot dump, a Seagate UDMA2 drive has been detected. After sysinstall starts, I see the following messages on vty1: ad0: ad_timeout: lost disk contact - resetting ata0: resetting devices .. ata0-master: timeout waiting for command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ad0: ad_timeout: lost disk contact - resetting ata0: resetting devices .. ata0-master: timeout waiting for command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ad0: ad_timeout: lost disk contact - resetting ata0: resetting devices .. ata0-master: timeout waiting for command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ata0-master: timeout waiting to give command=ef s=fc e=00 ad0: ad_timeout: lost disk contact - resetting ata0-master: timeout waiting for command=ef s=fc e=00 ad0: ad_timeout: trying fallback to PIO mode ata0: resetting devices .. done and the setup continues as if nothing has happened. The drive is configured as PIO mode 4 in the BIOS (the BIOS does not support UDMA, the chipset apparently does). Any pointers? Edwin Mons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 10:18:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles546.castles.com [208.214.165.110]) by hub.freebsd.org (Postfix) with ESMTP id 2A55A15562 for ; Thu, 27 Jan 2000 10:18:17 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA02470; Thu, 27 Jan 2000 10:27:02 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001271827.KAA02470@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Soren Schmidt Cc: ak@freenet.co.uk (Alex), current@FreeBSD.ORG Subject: Re: My ATAPI CD not come ready In-reply-to: Your message of "Thu, 27 Jan 2000 08:36:06 +0100." <200001270736.IAA33837@freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 27 Jan 2000 10:27:02 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG JFWIW, this sounds like something that I "fixed" in the old wd driver, = where a device 'echoed' on the bus after it was deselected. Increasing = the timeout between deselecting the device and trying to talk again to = the bus was, AFAIR, the workaround then. > It seems Alex wrote: > > = > > OK - here's the part relevant to ata: > > = > > = > > ata-pci0: port 0xfcf0-0xfcff at devic= e > > 1.1 on pci0 > > ata0: iobase=3D0x01f0 altiobase=3D0x03f6 bmaddr=3D0xfcf0 > > ata0: mask=3D03 status0=3D50 status1=3D00 > > ata0: mask=3D03 status0=3D50 status1=3D00 > > ata0: devices =3D 0x1 > > ata0 at 0x01f0 irq 14 on ata-pci0 > > ata1: iobase=3D0x0170 altiobase=3D0x0376 bmaddr=3D0xfcf8 > > ata1: mask=3D03 status0=3D00 status1=3D00 > > ata1: mask=3D03 status0=3D00 status1=3D00 > > ata1: devices =3D 0xc > = > Here it sees two devices, apparently you cdrom is reacting both on > master AND slave addresses :( > = > > ata1-slave: ata_command: timeout waiting for intr > > ata1-slave: identify failed > = > But when we try to talk to it it fails... > = > > ata0-master: success setting up UDMA2 mode on PIIX4 chip > = > But when we try to talk to it it fails... > = > > Any ideas? > = > I'll try to come up with a patch that solves this... > = > -S=F8ren > = > = > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > = -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 10:24:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 923C615202 for ; Thu, 27 Jan 2000 10:24:56 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id NAA06158; Thu, 27 Jan 2000 13:24:53 -0500 (EST) Date: Thu, 27 Jan 2000 13:24:53 -0500 (EST) From: "Matthew N. Dodd" To: Edwin Mons Cc: current@freebsd.org Subject: Re: strange ATA stuff (was: ep0 incorrectly probed) In-Reply-To: <389088C3.C32BFEF4@spcgroup.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Edwin Mons wrote: > and the setup continues as if nothing has happened. The drive is > configured as PIO mode 4 in the BIOS (the BIOS does not support UDMA, > the chipset apparently does). Any pointers? Humm... Try mode 'Auto'? Dunno. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 10:34:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 9C1F8156E6 for ; Thu, 27 Jan 2000 10:34:51 -0800 (PST) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id TAA11592; Thu, 27 Jan 2000 19:34:41 +0100 (CET) (envelope-from leifn@neland.dk) Date: Thu, 27 Jan 2000 19:34:41 +0100 (CET) From: Leif Neland To: Poul-Henning Kamp Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS /usr/src and /usr/obj? In-Reply-To: <7347.948925978@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000, Poul-Henning Kamp wrote: > In message , mestery@visi.com writes: > >I'm wondering how one can do a buildworld on a machine, and then NFS > >mount /usr/src and /usr/obj on a client machine and do an installworld > >of the freshly built sources? I've been looking in the archives without > >much success, and haven't figured it out by reading the makefiles yet. > >Can anyone shed some light on this? > > I've done it in the past, but not recently. > > Consider the alternative of mounting the destination on the compilehost > and make install DESTDIR=/mnt > A: What's the advantage? B: What do I mount? The root of the destination? Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 10:56:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 7351A15709 for ; Thu, 27 Jan 2000 10:56:41 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 806624CE1F for ; Thu, 27 Jan 2000 13:56:40 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id NAA06868 for ; Thu, 27 Jan 2000 13:56:39 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id KAA09456; Thu, 27 Jan 2000 10:56:39 -0800 (PST) Message-Id: <200001271856.KAA09456@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: current@freebsd.org Subject: Problems installing FreeBSD 4.0 20000125-CURRENT Date: Thu, 27 Jan 2000 10:56:39 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I installed 4.0 20000125-CURRENT last night on a new box, and had several problems that I wanted to share: 1. sysinstall forgot to write my hostname to /etc/rc.conf . I had gone into the options menu and selected "DHCP"; when I picked my network interface it looked for and found a DHCP server and popped up the network configuration box with most of the fields filled in (including domain name); all I did was type in a hostname. sysinstall then added the domain name to the host name and I said "OK", but that hostname never made it into rc.conf (it booted up calling itself Amnesiac). 2. motd was full of garbage. I realize now that I should have saved it but I wasn't really thinking. 3. On the first reboot after installing, the keyboard was in a funny state. Some keys would provide multiple characters, some would do none. Control-alt-del definitely didn't work, so I had to power off and reboot. This hasn't repeated itself. 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I used the expert install and picked the "Install everything" option so I assumed I'd get everything =) On the plus side, being able to use DHCP rocks, and I really like how it installed the Linux packages when I picked Linux emulation. And 4.0 seems to work well with this random hardware (emachine 400), including the onboard sound and random ethernet card (linksys something). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 11: 4:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-blue.research.att.com (mail-blue.research.att.com [135.207.30.102]) by hub.freebsd.org (Postfix) with ESMTP id 2804614E48 for ; Thu, 27 Jan 2000 11:04:51 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-blue.research.att.com (Postfix) with ESMTP id 76C1C4CE28 for ; Thu, 27 Jan 2000 14:04:50 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id OAA07258; Thu, 27 Jan 2000 14:03:28 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id LAA09566; Thu, 27 Jan 2000 11:03:28 -0800 (PST) Message-Id: <200001271903.LAA09566@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: asmodai@wxs.nl Subject: Re: With feature freeze being in place Cc: current@freebsd.org References: <20000122210136.B18600@daemon.ninth-circle.org> Date: Thu, 27 Jan 2000 11:03:28 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Test IPv6 support! You've all been asking for it, test it. Is there a quick primer on getting IPv6 up and running? I built a kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6 addresses, but no userland apps seem to be able to parse IPv6 addresses, e.g. "ping ::1" says "no such host". (This is 4.0-20000125-CURRENT). I searched the -current mail archives but couldn't find anything that seemed relevant. Thanks, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 11:10: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 614A0156DA for ; Thu, 27 Jan 2000 11:10:03 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id MAA06430; Thu, 27 Jan 2000 12:10:01 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id MAA47444; Thu, 27 Jan 2000 12:10:06 -0700 (MST) Message-Id: <200001271910.MAA47444@harmony.village.org> To: "Matthew N. Dodd" Subject: Re: ep0 incorrectly probed Cc: Edwin Mons , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 27 Jan 2000 12:52:47 EST." References: Date: Thu, 27 Jan 2000 12:10:06 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message "Matthew N. Dodd" writes: : Using the boot configuration screen can you disable all devices that are : not installed? : : I suspect something is clobbering the board after it is identified. We've had *BAD* luck with the ex driver doing this... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 11:17: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from email.spcgroup.nl (email.spcgroup.nl [212.206.124.3]) by hub.freebsd.org (Postfix) with ESMTP id 5BA4D14C94 for ; Thu, 27 Jan 2000 11:17:04 -0800 (PST) (envelope-from edwinm@email.spcgroup.nl) Received: from localhost (edwinm@localhost) by email.spcgroup.nl (8.9.3/8.9.3) with ESMTP id VAA10960; Thu, 27 Jan 2000 21:27:13 +0100 Date: Thu, 27 Jan 2000 21:27:13 +0100 (CET) From: Edwin Mons To: "Matthew N. Dodd" Cc: Edwin Mons , current@FreeBSD.ORG Subject: Re: strange ATA stuff (was: ep0 incorrectly probed) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Matthew N. Dodd wrote: > On Thu, 27 Jan 2000, Edwin Mons wrote: > > and the setup continues as if nothing has happened. The drive is > > configured as PIO mode 4 in the BIOS (the BIOS does not support UDMA, > > the chipset apparently does). Any pointers? > > Humm... Try mode 'Auto'? Did that. Didn't make any difference. Gave the same results either way. Could be a weird harddisk <-> IDE controller problem. Not a real problem, though. Everything appears to work just fine. Edwin Mons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 11:18: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 1973114C94 for ; Thu, 27 Jan 2000 11:17:54 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id OAA06858; Thu, 27 Jan 2000 14:17:44 -0500 (EST) Date: Thu, 27 Jan 2000 14:17:44 -0500 (EST) From: "Matthew N. Dodd" To: Warner Losh Cc: Edwin Mons , current@FreeBSD.ORG Subject: Re: ep0 incorrectly probed In-Reply-To: <200001271910.MAA47444@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Warner Losh wrote: > We've had *BAD* luck with the ex driver doing this... Except that the ex driver doesn't do anything destructive in its identify method now. I'm having a hell of a time getting the ex driver to attach in PnP mode but thats another story. I think the i85295 needs some special kicking or something but I don't have the manuals yet. It doesn't seem to be assigned the resources the kernel picks out for it. This is shown by 'pnpinfo'. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 11:20: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 108D2155E3 for ; Thu, 27 Jan 2000 11:19:59 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA02934; Thu, 27 Jan 2000 20:19:34 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001271919.UAA02934@freebsd.dk> Subject: Re: strange ATA stuff (was: ep0 incorrectly probed) In-Reply-To: from Edwin Mons at "Jan 27, 2000 09:27:13 pm" To: edwinm@email.spcgroup.nl (Edwin Mons) Date: Thu, 27 Jan 2000 20:19:34 +0100 (CET) Cc: winter@jurai.net (Matthew N. Dodd), e.mons@spcgroup.nl (Edwin Mons), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Edwin Mons wrote: > On Thu, 27 Jan 2000, Matthew N. Dodd wrote: > > On Thu, 27 Jan 2000, Edwin Mons wrote: > > > and the setup continues as if nothing has happened. The drive is > > > configured as PIO mode 4 in the BIOS (the BIOS does not support UDMA, > > > the chipset apparently does). Any pointers? > > > > Humm... Try mode 'Auto'? > > Did that. Didn't make any difference. Gave the same results either way. > Could be a weird harddisk <-> IDE controller problem. Not a real problem, > though. Everything appears to work just fine. it does, its harmless, its removed from the list when this happens... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 11:27: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 61E5214EF7 for ; Thu, 27 Jan 2000 11:27:00 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id EAA24330; Fri, 28 Jan 2000 04:26:46 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id EAA11678; Fri, 28 Jan 2000 04:26:45 +0900 (JST) Received: from localhost ([192.168.245.207]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id EAA11502; Fri, 28 Jan 2000 04:26:41 +0900 (JST) To: fenner@research.att.com Cc: asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: With feature freeze being in place In-Reply-To: <200001271903.LAA09566@windsor.research.att.com> References: <20000122210136.B18600@daemon.ninth-circle.org> <200001271903.LAA09566@windsor.research.att.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000128042719G.shin@nd.net.fujitsu.co.jp> Date: Fri, 28 Jan 2000 04:27:19 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 478 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Test IPv6 support! You've all been asking for it, test it. > > Is there a quick primer on getting IPv6 up and running? I built a > kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6 > addresses, but no userland apps seem to be able to parse IPv6 addresses, > e.g. "ping ::1" says "no such host". (This is 4.0-20000125-CURRENT). Please try ping6 ::1 > I searched the -current mail archives but couldn't find anything that > seemed relevant. > > Thanks, > Bill Sorry but I'll just attach some part of KAME package USAGE doc to this mail. Please check it about other tools usage. Also, usual tools, rlogin, rlogind, rsh, rshd, telnet, telnetd, ftp, ftpd, and inetd are already IPv6 capable. Wmmm, maybe I should merge ping and pin6 before code freeze... Yoshinobu Inoue ---------------------------------------------------------------------- <<>> A link-local address is automatically assigned to each interface, when the interface becomes up for the first time. Even if you find an interface without a link-local address, do not panic. The link-local address will be assigned when it becomes up (with "ifconfig IF up"). Some network drivers allow an interface to become up even without a hardware address (for example, PCMCIA network cards). In such cases, it is possible that an interface has no link-local address even if the interface is up. If you see such situation, please disable the interface once and then re-enable it (i.e. do `ifconfig IF down; ifconfig IF up'). Pseudo interfaces (like "gif" tunnel device) will borrow IPv6 interface identifier (lowermost 64bit of the address) from EUI64/IEEE802 sources, like ethernet cards. Pseudo interfaces will be able to get IPv6 link-local address, if you have other "real" interface configured beforehand. If you have no EUI64/IEEE802 sources on the node, you may need to configure link-local address manually. Though we have last-resort code in the kernel, which generates interface identifier from MD5(hostname), it may not suitable for your usage (for example, if you configure same hostname on both sides of gif tunnel, you will be doomed). If you have a router announcing Router Advertisement, global addresses will be assigned automatically. So, neither "ifconfig" nor "prefix" is necessary for your *host*. (Please refer to "sysctl" section for configuring a host to accept Router Advertisement.) If you want to set up a router, you need to assign global addresses for two or more interfaces by "ifconfig" or "prefix". (prefix command is described at next section) If you want to assign a global address by "ifconfig", don't forget to specify the "alias" argument to keep the link-local address. # ifconfig de0 inet6 3ffe:501:808:1:200:f8ff:fe01:6317 alias # ifconfig de0 de0: flags=8843 mtu 1500 inet6 fe80:1::200:f8ff:fe01:6317 prefixlen 64 inet 163.221.202.12 netmask 0xffffff00 broadcast 163.221.202.255 inet6 3ffe:501:808:1:200:f8ff:fe01:6317 prefixlen 64 ether 00:00:f8:01:63:17 media: 100baseTX status: active See also "/usr/local/v6/etc/rc.net6". <> In IPv6 architecture, an IPv6 address of an interface can be generated from a prefix assigned to it, and a link-dependent identifier for the interface. So assigning a full IPv6 address by ifconfig is not necessary anymore, because user can only take care of prefix, by letting system take care of interface identifier. The newly added "prefix" command enables user to just assign prefixes for interfaces, and let your system automatically generate IPv6 addresses. Prefixes added by the "prefix" command is maintained in the kernel consistently with prefixes assigned by Router Advertisement(in case of hosts) and with prefixes assigned by Router Renumbering(in case of routers). Manual assignment of prefixes or change of prefix properties take precedence over ones assigned by Router Advertisement or Router Renumbering. If you want to assign a prefix(and consequently address) manually, do as follows: # prefix de0 3ffe:501:808:1:: # ifconfig de0 de0: flags=8843 mtu 1500 inet6 fe80:1::200:f8ff:fe01:6317 prefixlen 64 inet 163.221.202.12 netmask 0xffffff00 broadcast 163.221.202.255 inet6 3ffe:501:808:1:200:f8ff:fe01:6317 prefixlen 64 ether 00:00:f8:01:63:17 media: 100baseTX status: active To check assigned prefix, use the "ndp" command. (See description of ndp command about its usage) # ndp -p 3ffe:501:808:1::/64 if=de0 flags=LA, vltime=2592000, pltime=604800, expire=Never No advertising router The "prefix" command also has node internal prefix renumbering ability. If you have multiple prefixes which have 3ffe:501:808:/48 at the top, and would like to renumber them to 3ffe:501:4819:/48, then use the "prefix" command with the "matchpr" argument and the "usepr" argument. Suppose that current state of before renumbering as follows: # ifconfig de0 de0: flags=8843 mtu 1500 inet6 fe80:1::200:f8ff:fe01:6317 prefixlen 64 inet 163.221.202.12 netmask 0xffffff00 broadcast 163.221.202.255 inet6 3ffe:501:808:1:200:f8ff:fe01:6317 prefixlen 64 ether 00:00:f8:01:63:17 media: 100baseTX status: active # ifconfig de1 de1: flags=8843 mtu 1500 inet6 fe80:1::200:f8ff:fe55:7011 prefixlen 64 inet 163.221.203.12 netmask 0xffffff00 broadcast 163.221.203.255 inet6 3ffe:501:808:2:200:f8ff:fe55:7011 prefixlen 64 ether 00:00:f8:55:70:11 media: 100baseTX status: active # ndp -p 3ffe:501:808:1::/64 if=de0 flags=LA, vltime=2592000, pltime=604800, expire=Never No advertising router 3ffe:501:808:2::/64 if=de1 flags=LA, vltime=2592000, pltime=604800, expire=Never No advertising router Then do as follows: # prefix -a matchpr 3ffe:501:808:: mp_len 48 usepr 3ffe:501:4819:: up_uselen 48 change If command is successful, prefixes and addresses will be renumbered as follows. # ifconfig de0 de0: flags=8843 mtu 1500 inet6 fe80:1::200:f8ff:fe01:6317 prefixlen 64 inet 163.221.202.12 netmask 0xffffff00 broadcast 163.221.202.255 inet6 3ffe:501:4819:1:200:f8ff:fe01:6317 prefixlen 64 ether 00:00:f8:01:63:17 media: 100baseTX status: active # ifconfig de1 de1: flags=8843 mtu 1500 inet6 fe80:1::200:f8ff:fe55:7011 prefixlen 64 inet 163.221.203.12 netmask 0xffffff00 broadcast 163.221.203.255 inet6 3ffe:501:4819:2:200:f8ff:fe55:7011 prefixlen 64 ether 00:00:f8:55:70:11 media: 100baseTX status: active # ndp -p 3ffe:501:4819:1::/64 if=de0 flags=LA, vltime=2592000, pltime=604800, expire=Never No advertising router 3ffe:501:4819:2::/64 if=de1 flags=LA, vltime=2592000, pltime=604800, expire=Never No advertising router See also "/usr/local/v6/etc/rc.net6". <<>> If there is a router announcing Router Advertisement on the subnet, you need not to add a default route for your host by yourself. (Please refer to "sysctl" section to accept Router Advertisement.) If you want to add a default route manually, do as follows: # route add -inet6 default fe80:2::200:a2ff:fe0e:7543 "default" means ::/0. In other cases, if "prefixlen" is omitted, 64 is assumed for "prefixlen" to get along with the aggregatable address. Note that, in IPv6, link-local address should be used as gateway ("fe80:2::200:a2ff:fe0e:7543" in the above). If you use global addresses, icmp6 redirect may not work properly. For ease of configuration we recommend you to avoid static routes and run a routing daemon (route6d for example) instead. <<>> Reachability can be checked by "ping6". This "ping6" allows multicast for its argument. % ping6 -I ed0 ff02::1 PING6(56=40+8+8 bytes) fe80::5254:ff:feda:cb7d --> ff02::1 56 bytes from fe80::5254:ff:feda:cb7d, icmp_seq=0 hlim=64 time=0.25 ms 56 bytes from fe80::2a0:c9ff:fe84:ed6c, icmp_seq=0 hlim=64 time=1.333 ms(DUP!) 56 bytes from fe80::5254:ff:feda:d161, icmp_seq=0 hlim=64 time=1.459 ms(DUP!) 56 bytes from fe80::260:97ff:fec2:80bf, icmp_seq=0 hlim=64 time=1.538 ms(DUP!) 56 bytes from 3ffe:501:4819:2000:5054:ff:fedb:aa46, icmp_seq=0 hlim=255 time=1.615 ms(DUP!) <<>> Name resolution is possible by ICMPv6 node information query message. This is very convenient for link-local addresses whose host name cannot be resolved by DNS. Specify the "-w" option to "ping6". % ping6 -I ed0 -w ff02::1 64 bytes from fe80::5254:ff:feda:cb7d: fto.kame.net 67 bytes from fe80::5254:ff:feda:d161: banana.kame.net 69 bytes from fe80::2a0:c9ff:fe84:ebd9: paradise.kame.net 66 bytes from fe80::260:8ff:fe8b:447f: taroh.kame.net 66 bytes from fe80::2a0:c9ff:fe84:ed6c: ayame.kame.net <<>> The route for a target host can be checked by "traceroute6". % traceroute6 tokyo.v6.wide.ad.jp traceroute to tokyo.v6.wide.ad.jp (3ffe:501:0:401:200:e8ff:fed5:8923), 30 hops max, 12 byte packets 1 nr60.v6.kame.net 1.239 ms 0.924 ms 0.908 ms 2 otemachi.v6.wide.ad.jp 28.953 ms 31.451 ms 26.567 ms 3 tokyo.v6.wide.ad.jp 26.549 ms 26.58 ms 26.186 ms If the -l option is specified, both address and name are shown in each line. % traceroute6 -l tokyo.v6.wide.ad.jp traceroute to tokyo.v6.wide.ad.jp (3ffe:501:0:401:200:e8ff:fed5:8923), 30 hops max, 12 byte packets 1 nr60.v6.kame.net (3ffe:501:4819:2000:260:97ff:fec2:80bf) 1.23 ms 0.952 ms 0.92 ms 2 otemachi.v6.wide.ad.jp (3ffe:501:0:1802:260:97ff:feb6:7ff0) 27.345 ms 26.706 ms 26.563 ms 3 tokyo.v6.wide.ad.jp (3ffe:501:0:401:200:e8ff:fed5:8923) 26.329 ms 26.36 ms 28.63 ms <<>> To display the current Neighbor cache, use "ndp": % ndp -a Neighbor Linklayer Address Netif Expire St Flgs Prbs nr60.v6.kame.net 0:60:97:c2:80:bf ed0 expired S R 3ffe:501:4819:2000:2c0:cff:fe 0:c0:c:10:3a:53 ed0 permanent R paradise.v6.kame.net 52:54:0:dc:52:17 ed0 expired S R fe80:1::200:eff:fe49:f929 0:0:e:49:f9:29 ed0 expired S R fe80:1::200:86ff:fe05:80da 0:0:86:5:80:da ed0 expired S fe80:1::200:86ff:fe05:c2d8 0:0:86:5:c2:d8 ed0 9s R To flush the all NDP cache, execute the following by root. # ndp -c To display the prefix list. % ndp -p 3ffe:501:4819:2000::/64 if=ed0 flags=LA, vltime=2592000, pltime=604800, expire=29d23h59m58s advertised by fe80::5254:ff:fedc:5217 fe80::260:97ff:fec2:80bf fe80::200:eff:fe49:f929 To display the default router list. % ndp -r fe80::260:97ff:fec2:80bf if=ed0, flags=, expire=29m55s fe80::5254:ff:fedc:5217 if=ed0, flags=, expire=29m7s fe80::200:eff:fe49:f929 if=ed0, flags=, expire=28m47s <<>> To generate a Router Solicitation message right now to get global addresses, use "rtsol". # ifconfig ef0 ef0: flags=8863 link type ether 0:a0:24:ab:83:9b mtu 1500 speed 10Mbps media 10baseT status active inet6 fe80:2::2a0:24ff:feab:839b prefixlen 64 # rtsol ef0 # ifconfig ef0 ef0: flags=8863 link type ether 0:a0:24:ab:83:9b mtu 1500 speed 10Mbps media 10baseT status active inet6 fe80:2::2a0:24ff:feab:839b prefixlen 64 inet6 3ffe:501:4819:2000:2a0:24ff:feab:839b prefixlen 64 <<>> rtsold is a daemon version of rtsol. If you run KAME IPv6 on a laptop computer and frequently move with it, the daemon is useful since it watches the interface and sends router solicitations when the status of the interface changes. Note, however, that the feature is disabled by default. Please add -m option when invocation of rtsold. rtsold also supports multiple interfaces. For example, you can invoke the daemon as follows: # rtsold -m ep0 cnw0 <<>> To see routing table: # netstat -nr # netstat -nrl (long format with Ref and Use) <<>> If "net.inet6.ip6.accept_rtadv" is 1, Router Advertisement is accepted. This means that global addresses and default route are automatically set up. Otherwise, the announcement is rejected. The default value is 0. To set "net.inet6.ip6.accept_rtadv" to 1, execute as follows: # sysctl -w net.inet6.ip6.accept_rtadv=1 <<>> "gif" interface enables you to perform IPv{4,6} over IPv{4,6} protocol tunneling. To use this interface, you must specify the outer IPv{4,6} address by using gifconfig, like: # gifconfig gif0 163.221.198.61 163.221.11.21 "ifconfig gif0" will configure the address pair used for inner IPv{4,6} header. It is not required to configure inner IPv{4,6} address pair. If you do not configure inner IPv{4,6} address pair, tunnel link is considered as un-numbered link and the source address of inner IPv{4,6} address pair will be borrowed from other interfaces. The following example configures un-numbered IPv6-over-IPv4 tunnel: # gifconfig gif0 10.0.0.1 10.0.0.1 netmask 255.255.255.0 The following example configures numbered IPv6-over-IPv4 tunnel: # gifconfig gif0 10.0.0.1 10.0.0.1 netmask 255.255.255.0 # ifconfig gif0 inet6 3ffe:501:808:5::1 3ffe:501:808:5::2 prefixlen 64 alias IPv6 spec allows you to use point-to-point link without global IPv6 address assigned to the interface. Routing protocol (such as RIPng) uses link-local addresses only. If you are to configure IPv6-over-IPv4 tunnel, you need not to configure an address pair for inner IPv6 header. We suggest you to use the former example (un-numbered IPv6-over-IPv4 tunnel) to connect to 6bone for simplicity. Note that it is so easy to make an infinite routing loop using gif interface, if you configure a tunnel using the same protocol family for inner and outer header (i.e. IPv4-over-IPv4). Refer to gifconfig(8) for more details. <<>> We supply two variant of inetd(8) with KAME kit. On most of OS platforms, we supply revised inetd(8) in /usr/local/v6/sbin. This supports AF_INET and AF_INET6 sockets, with IPsec policy configuration support. This is intended to replace OS-supplied inetd(8). On some of the OS platforms, inet6d(8) is supplied as well. This is designed to serve AF_INET6 services only, and you may want to use it with OS-supplied inetd(8). Consult INSTALL document in platform-dependent directory (for example, netbsd/INSTALL). <<>> The current KAME supports both transport mode and tunnel mode. However, tunnel mode comes with some restrictions. IPsec requires fairly complex configuration, so here we show transport mode only. http://www.kame.net/newsletter/ has more comprehensive examples. Let's setup security association to deploy a secure channel between HOST A (10.2.3.4) and HOST B (10.6.7.8). Here we show a little complicated example. From HOST A to HOST B, only old AH is used. From HOST B to HOST A, new AH and new ESP are combined. Now we should choose algorithm to be used corresponding to "AH"/"new AH"/"ESP"/"new ESP". Please refer to the "setkey" man page to know algorithm names. Our choice is MD5 for AH, new-HMAC-SHA1 for new AH, and new-DES-expIV with 8 byte IV for new ESP. Key length highly depends on each algorithm. For example, key length must be equal to 16 bytes for MD5, 20 for new-HMAC-SHA1, and 8 for new-DES-expIV. Now we choose "MYSECRETMYSECRET", "KAMEKAMEKAMEKAMEKAME", "PASSWORD", respectively. OK, let's assign SPI (Security Parameter Index) for each protocol. Please note that we need 3 SPIs for this secure channel since three security headers are produced (one for from HOST A to HOST B, two for from HOST B to HOST A). Please also note that SPI MUST be greater than or equal to 256. We choose, 1000, 2000, and 3000, respectively. (1) HOST A ------> HOST B (1)PROTO=AH ALG=MD5(RFC1826) KEY=MYSECRETMYSECRET SPI=1000 (2.1) HOST A <------ HOST B <------ (2.2) (2.1) PROTO=AH ALG=new-HMAC-SHA1(new AH) KEY=KAMEKAMEKAMEKAMEKAME SPI=2000 (2.2) PROTO=ESP ALG=new-DES-expIV(new ESP) IV length = 8 KEY=PASSWORD SPI=3000 Now, let's setup security association. Execute "setkey" on both HOST A and B: # setkey -c add 10.2.3.4 10.6.7.8 ah 1000 -m transport -A keyed-md5 "MYSECRETMYSECRET" ; add 10.6.7.8 10.2.3.4 ah 2000 -m transport -A hmac-sha1 "KAMEKAMEKAMEKAMEKAME" ; add 10.6.7.8 10.2.3.4 esp 3000 -m transport -E des-cbc "PASSWORD" ; ^D Actually, IPsec communication doesn't process until security policy entries will be defined. In this case, you must setup each host. At A: # setkey -c spdadd 10.2.3.4 10.6.7.8 any -P out ipsec ah/transport/10.2.3.4-10.6.7.8/require ; ^D At B: spdadd 10.6.7.8 10.2.3.4 any -P out ipsec esp/transport/10.6.7.8-10.2.3.4/require ; spdadd 10.6.7.8 10.2.3.4 any -P out ipsec ah/transport/10.6.7.8-10.2.3.4/require ; ^D To utilize the security associations installed into the kernel, you must set the socket security level by using setsockopt(). This is per-application (or per-socket) security. For example, the "ping" command has the -P option with parameter to enable AH and/or ESP. For example: % ping -P "out ipsec \ ah/transport/10.0.1.1-10.0.2.2/use \ esp/tunnel/10.0.1.1-10.0.1.2/require" 10.0.2.2 If there are proper SAs, this policy specification causes ICMP packet to be AH transport mode inner ESP tunnel mode like below. HOST C -----------> GATEWAY D ----------> HOST E 10.0.1.1 10.0.1.2 10.0.2.1 10.0.2.2 | | | | | ======= ESP ======= | ==================== AH ================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 11:44: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 749AD154A2 for ; Thu, 27 Jan 2000 11:44:03 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id OAA19277; Thu, 27 Jan 2000 14:44:00 -0500 (EST) (envelope-from wollman) Date: Thu, 27 Jan 2000 14:44:00 -0500 (EST) From: Garrett Wollman Message-Id: <200001271944.OAA19277@khavrinen.lcs.mit.edu> To: Bill Fenner Cc: asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: With feature freeze being in place In-Reply-To: <200001271903.LAA09566@windsor.research.att.com> References: <20000122210136.B18600@daemon.ninth-circle.org> <200001271903.LAA09566@windsor.research.att.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Is there a quick primer on getting IPv6 up and running? I built a > kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6 > addresses, but no userland apps seem to be able to parse IPv6 addresses, > e.g. "ping ::1" says "no such host". (This is 4.0-20000125-CURRENT). Yesterday, I tested ping6 between two hosts using link-local addresses, and it worked. The week before, however, I couldn't get a different machine to transmit packets when it had IPv6 in the kernel. I'm not sure about the relative dates involved. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 11:47:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from pogo.caustic.org (pogo.caustic.org [208.44.193.69]) by hub.freebsd.org (Postfix) with ESMTP id 2299614F19 for ; Thu, 27 Jan 2000 11:47:47 -0800 (PST) (envelope-from jan@caustic.org) Received: from localhost (jan@localhost) by pogo.caustic.org (8.9.3/ignatz) with ESMTP id LAA02928; Thu, 27 Jan 2000 11:46:47 -0800 (PST) Date: Thu, 27 Jan 2000 11:46:47 -0800 (PST) From: "f.johan.beisser" To: Garrett Wollman Cc: Bill Fenner , asmodai@wxs.nl, current@FreeBSD.ORG Subject: inet6 (was Re: With feature freeze being in place) In-Reply-To: <200001271944.OAA19277@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i've had ipv6 working with freenet6.net.. well, partially working, the full feature should work fine soon though. the tunneling through gif works, and i'm about to test IPSec with IPv4. more testing is in order though, so, i'll try to pass on some more info when i have it. -- jan On Thu, 27 Jan 2000, Garrett Wollman wrote: > < said: > > > Is there a quick primer on getting IPv6 up and running? I built a > > kernel with INET6 and the ipsec stuff, and my interfaces now have IPv6 > > addresses, but no userland apps seem to be able to parse IPv6 addresses, > > e.g. "ping ::1" says "no such host". (This is 4.0-20000125-CURRENT). > > Yesterday, I tested ping6 between two hosts using link-local > addresses, and it worked. The week before, however, I couldn't get a > different machine to transmit packets when it had IPv6 in the kernel. > I'm not sure about the relative dates involved. > > -GAWollman > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > +-----// f. johan beisser //------------------------------+ email: jan[at]caustic.org web: http://www.caustic.org/~jan "knowledge is power. power corrupts. study hard, be evil." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 12: 6:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 403CB14DE9 for ; Thu, 27 Jan 2000 12:06:22 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id B01C91E006; Thu, 27 Jan 2000 15:06:19 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id PAA09338; Thu, 27 Jan 2000 15:06:19 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id MAA10100; Thu, 27 Jan 2000 12:06:18 -0800 (PST) Message-Id: <200001272006.MAA10100@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: shin@nd.net.fujitsu.co.jp Subject: Re: With feature freeze being in place Cc: current@freebsd.org References: <20000122210136.B18600@daemon.ninth-circle.org> <200001271903.LAA09566@windsor.research.att.com> <20000128042719G.shin@nd.net.fujitsu.co.jp> Date: Thu, 27 Jan 2000 12:06:18 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Also, usual tools, rlogin, rlogind, rsh, rshd, telnet, >telnetd, ftp, ftpd, and inetd are already IPv6 capable. Hm. rlogin and rsh attempt to connect, but my inetd isn't listening; do I have to update inetd.conf to get inetd to listen on IPv6 addresses? telnet can't parse ::1: emachine% telnet ::1 ::1: Unknown host ftp prints a very odd message: emachine% ftp ::1 ftp: No control connection for command. I guess ftp parsed ::1 as a URL. What a pain. I tried putting "::1 v6-localhost" in /etc/hosts, but telnet and ftp couldn't use v6-localhost as a name while ping6, traceroute6, rlogin and rsh could. So far, the only tools I've been able to use to emit v6 packets are ping6, traceroute6, rlogin and rsh. I don't have any other v6 machines on my network, so I've just been using loopback. >Wmmm, maybe I should merge ping and pin6 before code freeze... I think it'd be very handy for the native ping (and traceroute, if possible) to be IPv4/IPv6 capable. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 12:10:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 64D5A15611 for ; Thu, 27 Jan 2000 12:10:26 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id E3E961C03; Fri, 28 Jan 2000 04:10:23 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew N. Dodd" Cc: Warner Losh , Edwin Mons , current@FreeBSD.ORG Subject: Re: ep0 incorrectly probed In-Reply-To: Message from "Matthew N. Dodd" of "Thu, 27 Jan 2000 14:17:44 EST." Date: Fri, 28 Jan 2000 04:10:23 +0800 From: Peter Wemm Message-Id: <20000127201023.E3E961C03@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > On Thu, 27 Jan 2000, Warner Losh wrote: > > We've had *BAD* luck with the ex driver doing this... > > Except that the ex driver doesn't do anything destructive in its identify > method now. > > I'm having a hell of a time getting the ex driver to attach in PnP mode > but thats another story. I think the i85295 needs some special kicking or > something but I don't have the manuals yet. It doesn't seem to be > assigned the resources the kernel picks out for it. This is shown by > 'pnpinfo'. pnpinfo doesn't have anything to do with what the kernel thinks. It's a userland program that manually resets and reconfigures the cards.. This is an absolute disaster if you happened to be using the hardware, eg: the sound driver. After running pnpinfo, the hardware essentially "disappears". pciconf(8) does it properly, it asks the kernel via /dev/pci. pnpinfo uses /dev/io to bash on the ports directly. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 12:16:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id CCE5414C82 for ; Thu, 27 Jan 2000 12:16:11 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA07614; Thu, 27 Jan 2000 15:15:50 -0500 (EST) Date: Thu, 27 Jan 2000 15:15:49 -0500 (EST) From: "Matthew N. Dodd" To: Peter Wemm Cc: Warner Losh , Edwin Mons , current@FreeBSD.ORG Subject: Re: ep0 incorrectly probed In-Reply-To: <20000127201023.E3E961C03@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jan 2000, Peter Wemm wrote: > pnpinfo doesn't have anything to do with what the kernel thinks. It's a > userland program that manually resets and reconfigures the cards.. This is > an absolute disaster if you happened to be using the hardware, eg: the sound > driver. After running pnpinfo, the hardware essentially "disappears". > > pciconf(8) does it properly, it asks the kernel via /dev/pci. pnpinfo uses > /dev/io to bash on the ports directly. Thats kinda weird seeing as how pnpinfo correctly reports the settings as detected/assigned by the kernel for all other cards. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 12:29: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id A8473158B7 for ; Thu, 27 Jan 2000 12:29:02 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id FAA09578; Fri, 28 Jan 2000 05:28:46 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id FAA17837; Fri, 28 Jan 2000 05:28:45 +0900 (JST) Received: from localhost ([192.168.245.29]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id FAA12271; Fri, 28 Jan 2000 05:28:44 +0900 (JST) To: wollman@khavrinen.lcs.mit.edu Cc: fenner@research.att.com, asmodai@wxs.nl, current@FreeBSD.ORG Subject: Re: With feature freeze being in place In-Reply-To: <200001271944.OAA19277@khavrinen.lcs.mit.edu> References: <20000122210136.B18600@daemon.ninth-circle.org> <200001271903.LAA09566@windsor.research.att.com> <200001271944.OAA19277@khavrinen.lcs.mit.edu> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000128052927V.shin@nd.net.fujitsu.co.jp> Date: Fri, 28 Jan 2000 05:29:27 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 21 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Yesterday, I tested ping6 between two hosts using link-local > addresses, and it worked. The week before, however, I couldn't get a > different machine to transmit packets when it had IPv6 in the kernel. > I'm not sure about the relative dates involved. > > -GAWollman Some driver seems to have problems with INET6 support. IPv6 addresss auto configuration packet is sent just after ifconfig up, and all such work is done at splimp(). Sometime it seems to be problem for some drivers. As I heard, -fxp driver cause problem with some driver at some timing. -de driver caused some initialization problem with INET6. I have been trying to find some time to test fxp, but not successful yet. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 12:37:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id 4355014CB9 for ; Thu, 27 Jan 2000 12:37:35 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id FAA09872; Fri, 28 Jan 2000 05:37:31 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id FAA19232; Fri, 28 Jan 2000 05:37:31 +0900 (JST) Received: from localhost ([192.168.245.52]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id FAA12379; Fri, 28 Jan 2000 05:37:29 +0900 (JST) To: fenner@research.att.com Cc: current@FreeBSD.ORG Subject: Re: With feature freeze being in place In-Reply-To: <200001272006.MAA10100@windsor.research.att.com> References: <200001271903.LAA09566@windsor.research.att.com> <20000128042719G.shin@nd.net.fujitsu.co.jp> <200001272006.MAA10100@windsor.research.att.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000128053813I.shin@nd.net.fujitsu.co.jp> Date: Fri, 28 Jan 2000 05:38:13 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 54 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Also, usual tools, rlogin, rlogind, rsh, rshd, telnet, > >telnetd, ftp, ftpd, and inetd are already IPv6 capable. > > Hm. rlogin and rsh attempt to connect, but my inetd isn't listening; > do I have to update inetd.conf to get inetd to listen on IPv6 addresses? Yes, if tcp, please specify tcp46 or tcp6 Former accept either of IPv4 and IPv6, and latter only accept IPv6. The following 2 are same. Only accept IPv4. tcp4 tcp You can also specify following 2 entries for each of services at the same time. tcp6 tcp4 Please check inetd man page for details. > telnet can't parse ::1: > > emachine% telnet ::1 > ::1: Unknown host > > ftp prints a very odd message: > > emachine% ftp ::1 > ftp: No control connection for command. telnet, ftp, and ftpd are added today.(2000/01/27 01:28:39 PST) So it might not yet be mirrored to your place. > >Wmmm, maybe I should merge ping and pin6 before code freeze... > > I think it'd be very handy for the native ping (and traceroute, if > possible) to be IPv4/IPv6 capable. > > Bill Traceroute/traceroute6 merging is somewhat more difficult because traceroute is maintenanced under contrib. :( Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13: 1:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id D094514EA5 for ; Thu, 27 Jan 2000 13:01:44 -0800 (PST) (envelope-from jaco@titine.fr.eu.org) Received: from titine.fr.eu.org (toulouse-50-151.dial.proxad.net [212.27.50.151]) by postfix1.free.fr (Postfix) with ESMTP id 427EB28207 for ; Thu, 27 Jan 2000 22:01:09 +0100 (MET) Received: by titine.fr.eu.org (Postfix, from userid 1000) id 1022514983; Thu, 27 Jan 2000 21:56:37 +0100 (CET) To: current@FreeBSD.ORG Subject: Something strange with pccard/ed0 ? From: Eric Jacoboni Date: 27 Jan 2000 21:56:37 +0100 In-Reply-To: Soren Schmidt's message of "Fri, 14 Jan 2000 12:50:19 +0100 (CET)" Message-ID: <87d7qnfd2y.fsf@titine.fr.eu.org> Lines: 46 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Bryce Canyon" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm currently running 4.0-CURRENT (Jan 27) on a Dell I3500 laptop with pccard and a D-LINK DE-660. All runs ok except that my card is not recognized as ed0 but as ed1. Here are my config params : =-=-=-= device card0 device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 =-=-=-= i'm using the genuine DE-660 pccard.conf entry. At startup, i get the following messages : =-=-=-== Jan 27 21:31:20 alex /kernel: pcic: management irq 10 Jan 27 21:31:20 alex /kernel: pcic0: at port 0x3e0 iomem 0xd0000 i rq 10 on isa0 Jan 27 21:31:20 alex /kernel: pccard0: on pcic0 Jan 27 21:31:20 alex /kernel: pccard1: on pcic0 (...) Jan 27 21:31:20 alex /kernel: pccard: card inserted, slot 0 Jan 27 21:31:28 alex /kernel: devclass_alloc_unit: ed0 already exists, using nex t available unit number Jan 27 21:31:29 alex /kernel: ed1 at port 0x240-0x25f irq 3 slot 1 on pccard1 Jan 27 21:31:29 alex /kernel: ed1: address 00:80:c8:bc:91:94, type NE2000 (16 bi t) Jan 27 21:31:29 alex /kernel: bpf: ed1 attached Jan 27 21:31:28 alex pccard:ed1: D-Link DE-660 inserted Jan 27 21:31:29 alex pccardd[44]: pccardd started =-=-=-= I don't understand this devclass_alloc_unit pb... Why does it pretend that ed0 already exists ? -- --------------------------------------------------------- Éric Jacoboni Ğ No sport, cigars! ğ (W. Churchill) --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13: 4:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id B1B33156BF for ; Thu, 27 Jan 2000 13:04:38 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 15CE61CD4; Fri, 28 Jan 2000 05:04:36 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew N. Dodd" Cc: Warner Losh , Edwin Mons , current@FreeBSD.ORG Subject: Re: ep0 incorrectly probed In-Reply-To: Message from "Matthew N. Dodd" of "Thu, 27 Jan 2000 15:15:49 EST." Date: Fri, 28 Jan 2000 05:04:36 +0800 From: Peter Wemm Message-Id: <20000127210436.15CE61CD4@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" wrote: > On Fri, 28 Jan 2000, Peter Wemm wrote: > > pnpinfo doesn't have anything to do with what the kernel thinks. It's a > > userland program that manually resets and reconfigures the cards.. This is > > an absolute disaster if you happened to be using the hardware, eg: the soun d > > driver. After running pnpinfo, the hardware essentially "disappears". > > > > pciconf(8) does it properly, it asks the kernel via /dev/pci. pnpinfo uses > > /dev/io to bash on the ports directly. > > Thats kinda weird seeing as how pnpinfo correctly reports the settings as > detected/assigned by the kernel for all other cards. Hmm, I take some of that back. I'm still not 100% sure of the implications of what I'm seeing in src/contrib/pnpinfo, but it still makes me nervous. For example: Logical device #0 IO: 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 IRQ 5 0 DMA 1 0 IO range check 0x00 activate 0x01 versus: pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 Which is right? Does the device really have all 8 IO ranges assigned to the same address? (0x534) Or is pnpinfo wrong? Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13: 6: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from greenie.muc.de (greenie.muc.de [193.149.48.161]) by hub.freebsd.org (Postfix) with SMTP id A3DF314D92 for ; Thu, 27 Jan 2000 13:06:04 -0800 (PST) (envelope-from gert@greenie.muc.de) Received: by greenie.muc.de via sendmail with stdio id for freebsd-current@freebsd.org; Thu, 27 Jan 2000 22:06:02 +0100 (MET) (Smail-3.2 1996-Jul-4 #4 built -Feb-21) Message-ID: <20000127220602.B14471@greenie.muc.de> Date: Thu, 27 Jan 2000 22:06:02 +0100 From: Gert Doering To: Christoph Kukulies , Gert Doering Cc: mgetty@greenie.muc.de, freebsd-current@freebsd.org Subject: Re: locking problem FreeBSD 3.4 - kermit and mgetty References: <200001251951.UAA03088@gil.physik.rwth-aachen.de> <20000126231354.B886@greenie.muc.de> <20000127190338.C14674@gil.physik.rwth-aachen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <20000127190338.C14674@gil.physik.rwth-aachen.de>; from Christoph Kukulies on Thu, Jan 27, 2000 at 07:03:38PM +0100 X-mgetty-docs: http://alpha.greenie.net/mgetty/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Thu, Jan 27, 2000 at 07:03:38PM +0100, Christoph Kukulies wrote: > > > But as a result mgetty gets into kermit's ways such that when a > > > modem connection is made I suddenly get a modem prompt like > > > +FCON as if someone (mgetty) is either messing with my local > > > or the remote modem while kermit opens the connection. > > > > The modem is in fax mode, and has established a fax connection. Have > > kermit send an AT+FCLASS=0 first. > > OK, this may be a repair but I'm wondering why that worked before > and now I have to take special measures. Or is it perhaps > kermit's fault? Older mgetty versions had all class 2 modems in "class 0 mode" while waiting for incoming calls, which worked very well for some Rockwell modems, and not so well for others. With class 2.0 modems, the modem always *had* to be in fax mode. Recently, I changed the settings so that some class 2 modems are also run in "class 2 mode", so maybe that triggered the problem at your end. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert@greenie.muc.de fax: +49-89-35655025 gert.doering@physik.tu-muenchen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13:27:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E3BCB14D7B for ; Thu, 27 Jan 2000 13:27:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA45275; Thu, 27 Jan 2000 13:28:10 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Bill Fenner Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 10:56:39 PST." <200001271856.KAA09456@windsor.research.att.com> Date: Thu, 27 Jan 2000 13:28:10 -0800 Message-ID: <45272.949008490@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1. sysinstall forgot to write my hostname to /etc/rc.conf . I had gone > into the options menu and selected "DHCP"; when I picked my network > interface it looked for and found a DHCP server and popped up the > network configuration box with most of the fields filled in (including > domain name); all I did was type in a hostname. sysinstall then added > the domain name to the host name and I said "OK", but that hostname > never made it into rc.conf (it booted up calling itself Amnesiac). In this case, I actually assume that the DHCP server will be providing the host name and specifically *ignore* the user-provide hostname field since our dhcp client integration is still a bit green and you'll just override the DHCP server assignment for the hostname with the user-defined one if it's written to rc.conf. > 2. motd was full of garbage. I realize now that I should have saved it > but I wasn't really thinking. Huh? > 3. On the first reboot after installing, the keyboard was in a funny > state. Urk, can't reproduce it. I need a reproducible sequence of operations before we'll have any hope of tackling this one. > Control-alt-del definitely didn't work, so I had to power off and > reboot. This hasn't repeated itself. Same here. > 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. I guess we need to build our own XF86 distribution with the a.out libraries built or we need to somehow stuff those into a compat dist. Ugh, either option is pretty ugly. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13:32:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id DBA9B14DEB for ; Thu, 27 Jan 2000 13:32:24 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id OAA25762; Thu, 27 Jan 2000 14:18:47 -0700 (MST) Date: Thu, 27 Jan 2000 14:18:47 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <200001272118.OAA25762@narnia.plutotech.com> To: Kazutaka YOKOTA Cc: current@FreeBSD.org Subject: Re: [PATCH] Please test the PS/2 mouse driver patch X-Newsgroups: pluto.freebsd.current In-Reply-To: <200001241319.WAA06932@zodiac.mech.utsunomiya-u.ac.jp> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001241319.WAA06932@zodiac.mech.utsunomiya-u.ac.jp> you wrote: > I wrote a patch for the psm driver to add support for several PS/2 mice. > It is in http://www.freebsd.org/~yokota/ps2mice-24Jan2000.tar.gz. > I am attaching README included in the patch. > > Thank you. > > Kazu Do you have specs on the Trackpoint PS/2 mice found on Thinkpads? The version on my 770X has a double click by "pushing hard on the trackpoint" feature. It also has the ability to do the scroll thing if you hold the middle mouse button and move the trackpoint. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13:43:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 3EB88154D5 for ; Thu, 27 Jan 2000 13:43:53 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA20638; Thu, 27 Jan 2000 16:43:46 -0500 (EST) (envelope-from wollman) Date: Thu, 27 Jan 2000 16:43:46 -0500 (EST) From: Garrett Wollman Message-Id: <200001272143.QAA20638@khavrinen.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: Bill Fenner , current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: <45272.949008490@zippy.cdrom.com> References: <200001271856.KAA09456@windsor.research.att.com> <45272.949008490@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: >> 3. On the first reboot after installing, the keyboard was in a funny >> state. > Urk, can't reproduce it. I need a reproducible sequence of operations > before we'll have any hope of tackling this one. >> Control-alt-del definitely didn't work, so I had to power off and >> reboot. This hasn't repeated itself. > Same here. I have on a number of occasions had my laptop boot with a non-functional keyboard. Sometimes the keyboard is just locked; other times it generates garbage. Never managed to isolate the circumstances in which this happened (but it didn't happen with a kernel from last September or there-abouts). Haven't had it happen on a desktop or server yet. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13:44:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id F246A14E66 for ; Thu, 27 Jan 2000 13:44:21 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA07077 for ; Thu, 27 Jan 2000 14:44:20 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA48475 for ; Thu, 27 Jan 2000 14:44:27 -0700 (MST) Message-Id: <200001272144.OAA48475@harmony.village.org> To: current@freebsd.org Subject: Comments on this patch? Date: Thu, 27 Jan 2000 14:44:27 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been running this for a while. I reversed the normal order to make it easier to do the math w/o having to shift columns and flip things over. BTW, I'm getting numbers that are 2x bigger than before :-(. I had makebuildworld down to around 1:20 at one point, but now it is 2:40. Comments? Warner Index: Makefile =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/Makefile,v retrieving revision 1.233 diff -u -r1.233 Makefile --- Makefile 2000/01/09 18:17:48 1.233 +++ Makefile 2000/01/27 21:42:39 @@ -130,6 +130,19 @@ @echo ">>> ${OBJFORMAT} make world started on ${STARTTIME}" @echo ">>> ${OBJFORMAT} make world completed on `LC_TIME=C date`" @echo "--------------------------------------------------------------" +# +# Timed buildworld +# +timed-buildworld: upgrade_checks + @echo "--------------------------------------------------------------" + @echo ">>> ${OBJFORMAT} make buildworld started on ${STARTTIME}" + @echo "--------------------------------------------------------------" + @cd ${.CURDIR}; ${MAKE} buildworld + @echo + @echo "--------------------------------------------------------------" + @echo ">>> ${OBJFORMAT} make buildworld completed on `LC_TIME=C date`" + @echo ">>> ${OBJFORMAT} make buildworld started on ${STARTTIME}" + @echo "--------------------------------------------------------------" # # Perform a few tests to determine if the installed tools are adequate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13:50:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id D89D2158C4 for ; Thu, 27 Jan 2000 13:50:23 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id 5EC771E00F; Thu, 27 Jan 2000 16:50:16 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id QAA13514; Thu, 27 Jan 2000 16:50:15 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id NAA11047; Thu, 27 Jan 2000 13:50:15 -0800 (PST) Message-Id: <200001272150.NAA11047@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: jkh@zippy.cdrom.com Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: current@freebsd.org Date: Thu, 27 Jan 2000 13:50:15 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In this case, I actually assume that the DHCP server will be providing >the host name In my case (which I think might actually be fairly common), the DHCP server doesn't provide a hostname. In this case, I type in a hostname which gets later ignored and sysinstall doesn't write anything to rc.conf. Perhaps if the DHCP server doesn't provide a hostname, sysinstall can use the one that the user supplied? >> 2. motd was full of garbage. I realize now that I should have saved it >> but I wasn't really thinking. > >Huh? When I logged in, I thought the machine had freaked out and locked up because there was all sorts of garbage (mostly 8-bit characters) on the screen, but on further examination it was just the contents of /etc/motd. It would be much easier to explain if I had saved it =) I can't repeat the keyboard thing, so I can't expect you to -- just something annoying that happened. I dunno what to suggest about /usr/X11R6/lib/aout. Earlier X distributions came with it; perhaps just copy the directory from an earlier one? Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13:52:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.49]) by hub.freebsd.org (Postfix) with ESMTP id 19BEC157BA for ; Thu, 27 Jan 2000 13:52:29 -0800 (PST) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA21353 for ; Thu, 27 Jan 2000 22:52:26 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.9.3) with ESMTP id WAA00762 for ; Thu, 27 Jan 2000 22:52:12 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <200001272152.WAA00762@trantor.xs4all.nl> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Par. gone missing Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 22:52:12 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just notice my par. port is no longer detected. A kernel built on Jan 21st fails to detect my par. port which has worked fine so far. In /var/log/messages I get the following: Jan 27 22:29:53 trantor /kernel: ppc0: parallel port found at 0x3bc Jan 27 22:29:53 trantor /kernel: ppc0: cannot reserve I/O port range When doing a boot -v. An older kernel booted Jan 13th showed the following : Jan 13 21:08:47 trantor /kernel: ppc0 at port 0x3bc-0x3c3 irq 7 on isa0 Jan 13 21:08:47 trantor /kernel: isa_compat: didn't get ports for ppc Jan 13 21:08:47 trantor /kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode Jan 13 21:08:47 trantor /kernel: lpt0: on ppbus 0 Jan 13 21:08:47 trantor /kernel: lpt0: Interrupt-driven port Rebooting the older kernel brings back my port so I doubt it's a hardware problem. Any hints on tracing the reason for it not being detected ?? Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13:52:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from iris.vsrc.uab.edu (iris.vsrc.uab.edu [138.26.156.231]) by hub.freebsd.org (Postfix) with ESMTP id EA19E1582C for ; Thu, 27 Jan 2000 13:52:36 -0800 (PST) (envelope-from emre@iris.vsrc.uab.edu) Received: by iris.vsrc.uab.edu (Postfix, from userid 1001) id D763D1250B; Thu, 27 Jan 2000 15:53:28 +0000 (GMT) Date: Thu, 27 Jan 2000 15:53:28 +0000 From: Emre To: freebsd-current@freebsd.org Subject: .bash_history and permissions Message-ID: <20000127155328.A32492@iris.vsrc.uab.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks! I'm running FreeBSD 4.0 from Dec. 26 1999. This should be on the "general questions" malininglist, but I thought maybe there is something that changed from -stable to -current that does this: I'm trying to limit permissions on .bash_history. There have been users on my server that have linked .bash_history to /dev/null and then been doing some cracking, and attacking other servers. To limit this (or at least trying to control it) I tried to take out write permission for group and others, thinking that will stop the users from trying to mod- ify the file. That didn't work! Even if I did "chmod 000 .bash_history" users still could delete the file or modify it. So I thought maybe if I just change the group or the owner of the file, it would fix the problem that didn't work either...now it wouldn't log the commands to the history file anymore. So I was wondering, do any of you gurus and bofh know how to fix this? This is very imporant for me, I'd be _very_ thankful if anyone could help me fix this problem. (PS: In other's OSs i.e Solaris or Linsucks, changing the perms seemd to work, just not in FreeBSD) -- DSS/DH 1024/4064: 0x5E9EE10A/0x2486FEBE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 13:53: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from MailAndNews.com (MailAndNews.com [199.29.68.160]) by hub.freebsd.org (Postfix) with ESMTP id F39CF15B3D for ; Thu, 27 Jan 2000 13:53:04 -0800 (PST) (envelope-from mheffner@mailandnews.com) Received: from muriel.penguinpowered.com [208.138.198.103] (mheffner@mailandnews.com); Thu, 27 Jan 2000 16:53:00 -0500 X-WM-Posted-At: MailAndNews.com; Thu, 27 Jan 00 16:53:00 -0500 Content-Length: 1040 Message-ID: X-Mailer: XFMail 1.4.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <45272.949008490@zippy.cdrom.com> Date: Thu, 27 Jan 2000 16:54:50 -0500 (EST) Reply-To: Mike Heffner From: Mike Heffner To: "Jordan K. Hubbard" Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: current@FreeBSD.ORG, Bill Fenner Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Jan-2000 Jordan K. Hubbard wrote: | |> 3. On the first reboot after installing, the keyboard was in a funny |> state. | | Urk, can't reproduce it. I need a reproducible sequence of operations | before we'll have any hope of tackling this one. | |> Control-alt-del definitely didn't work, so I had to power off and |> reboot. This hasn't repeated itself. | | Same here. | I seem to have this problem occasionaly, the keyboard keymap gets all screwed up somehow, and the only way to get out is to hit the reset button. But I've been having the problem for a long time, and with different boxes. It happens about every 1 out of 15 reboots but randomly. I haven't been able to connect it to any event or anything, but I notice that hitting keys during boot can increase the probability of it occurring, but again, nothing reproducible. --------------------------------- Mike Heffner Fredericksburg, VA ICQ# 882073 Date: 27-Jan-2000 Time: 16:47:01 --------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14: 3: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp01.primenet.com (smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (Postfix) with ESMTP id 9EEC514DEB for ; Thu, 27 Jan 2000 14:03:01 -0800 (PST) (envelope-from rcarter@pinyon.org) Received: (from daemon@localhost) by smtp01.primenet.com (8.9.3/8.9.3) id PAA20599; Thu, 27 Jan 2000 15:02:52 -0700 (MST) Received: from ip-83-147.prc.primenet.com(207.218.83.147), claiming to be "pinyon.org" via SMTP by smtp01.primenet.com, id smtpdAAAgiaq1N; Thu Jan 27 15:02:31 2000 Received: from chomsky.Pinyon.ORG (localhost [127.0.0.1]) by pinyon.org (Postfix) with ESMTP id E0E6270; Thu, 27 Jan 2000 15:02:28 -0700 (MST) X-Mailer: exmh version 2.1.0 09/18/1999 To: Mike Heffner Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG, Bill Fenner , rcarter@pinyon.org Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: Message from Mike Heffner of "Thu, 27 Jan 2000 16:54:50 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 15:02:28 -0700 From: "Russell L. Carter" Message-Id: <20000127220228.E0E6270@pinyon.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG % %On 27-Jan-2000 Jordan K. Hubbard wrote: % | % |> 3. On the first reboot after installing, the keyboard was in a funny % |> state. % | % | Urk, can't reproduce it. I need a reproducible sequence of operations % | before we'll have any hope of tackling this one. % | % |> Control-alt-del definitely didn't work, so I had to power off and % |> reboot. This hasn't repeated itself. % | % | Same here. % | % %I seem to have this problem occasionaly, the keyboard keymap gets all screwed %up somehow, and the only way to get out is to hit the reset button. But I've %been having the problem for a long time, and with different boxes. It happens %about every 1 out of 15 reboots but randomly. I haven't been able to connect %it to any event or anything, but I notice that hitting keys during boot can %increase the probability of it occurring, but again, nothing reproducible. Right. I've seen this when I hit Enter rapidly twice at the first loader prompt. Doesn't ever happen if I wait for the second prompt. Russell %--------------------------------- %Mike Heffner %Fredericksburg, VA %ICQ# 882073 %Date: 27-Jan-2000 Time: 16:47:01 %--------------------------------- % % %To Unsubscribe: send mail to majordomo@FreeBSD.org %with "unsubscribe freebsd-current" in the body of the message % To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14: 5:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from kronos.alcnet.com (kronos.alcnet.com [63.69.28.22]) by hub.freebsd.org (Postfix) with ESMTP id 4A579157B5 for ; Thu, 27 Jan 2000 14:05:14 -0800 (PST) (envelope-from kbyanc@posi.net) X-Provider: ALC Communications, Inc. http://www.alcnet.com/ Received: from localhost (kbyanc@localhost) by kronos.alcnet.com (8.9.3/8.9.3/antispam) with ESMTP id RAA45404; Thu, 27 Jan 2000 17:04:55 -0500 (EST) Date: Thu, 27 Jan 2000 17:04:55 -0500 (EST) From: Kelly Yancey X-Sender: kbyanc@kronos.alcnet.com To: Garrett Wollman Cc: "Jordan K. Hubbard" , Bill Fenner , current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: <200001272143.QAA20638@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Garrett Wollman wrote: > > I have on a number of occasions had my laptop boot with a > non-functional keyboard. Sometimes the keyboard is just locked; other > times it generates garbage. Never managed to isolate the > circumstances in which this happened (but it didn't happen with a > kernel from last September or there-abouts). Haven't had it happen on > a desktop or server yet. > > -GAWollman I've seen this on a Compaq Armada laptop recently (-current from about 1/10/2000). It only happens when I interrupt the boot process with a key press (I cannot recall whether it was in /boot/loader or in boot2). I suspect the latter, but have not yet tracked the problem down. Kelly -- Kelly Yancey - kbyanc@posi.net - Richmond, VA Analyst / E-business Development, Bell Industries http://www.bellind.com/ Maintainer, BSD Driver Database http://www.posi.net/freebsd/drivers/ Coordinator, Team FreeBSD http://www.posi.net/freebsd/Team-FreeBSD/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14: 5:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail-green.research.att.com (H-135-207-30-103.research.att.com [135.207.30.103]) by hub.freebsd.org (Postfix) with ESMTP id 5BFB31578B for ; Thu, 27 Jan 2000 14:05:32 -0800 (PST) (envelope-from fenner@research.att.com) Received: from alliance.research.att.com (alliance.research.att.com [135.207.26.26]) by mail-green.research.att.com (Postfix) with ESMTP id B442E1E00F; Thu, 27 Jan 2000 17:05:26 -0500 (EST) Received: from windsor.research.att.com (windsor.research.att.com [135.207.26.46]) by alliance.research.att.com (8.8.7/8.8.7) with ESMTP id RAA14129; Thu, 27 Jan 2000 17:05:26 -0500 (EST) From: Bill Fenner Received: (from fenner@localhost) by windsor.research.att.com (8.8.8+Sun/8.8.5) id OAA11110; Thu, 27 Jan 2000 14:05:26 -0800 (PST) Message-Id: <200001272205.OAA11110@windsor.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: rcarter@pinyon.org Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: current@freebsd.org Date: Thu, 27 Jan 2000 14:05:25 -0800 Versions: dmail (solaris) 2.2g/makemail 2.9a Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Right. I've seen this when I hit Enter rapidly twice at the first >loader prompt. Doesn't ever happen if I wait for the second >prompt. That's my impression too -- I've seen it on my laptop when I do that (sometimes), and I may have hit enter twice rapidly on this reboot. Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14: 6:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id 813E8157D2 for ; Thu, 27 Jan 2000 14:06:38 -0800 (PST) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA04085 for ; Thu, 27 Jan 2000 23:06:32 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.9.3) with ESMTP id XAA00935 for ; Thu, 27 Jan 2000 23:06:32 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <200001272206.XAA00935@trantor.xs4all.nl> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Parallel port gone missing (extra info) Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 23:06:32 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001272152.WAA00762@trantor.xs4all.nl>, Paul van der Zwan wrote: > >I just notice my par. port is no longer detected. A kernel built on Jan 21st >fails to detect my par. port which has worked fine so far. >In /var/log/messages I get the following: > >Jan 27 22:29:53 trantor /kernel: ppc0: parallel port found at 0x3bc >Jan 27 22:29:53 trantor /kernel: ppc0: cannot reserve I/O port range > >When doing a boot -v. >An older kernel booted Jan 13th showed the following : >Jan 13 21:08:47 trantor /kernel: ppc0 at port 0x3bc-0x3c3 irq 7 on isa0 >Jan 13 21:08:47 trantor /kernel: isa_compat: didn't get ports for ppc >Jan 13 21:08:47 trantor /kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode >Jan 13 21:08:47 trantor /kernel: lpt0: on ppbus0 >Jan 13 21:08:47 trantor /kernel: lpt0: Interrupt-driven port > >Rebooting the older kernel brings back my port so I doubt it's a hardware >problem. Any hints on tracing the reason for it not being detected ?? > Some extra info , the MB is a Chaintech 5TDM2, changing biossettings from EPP to ECP/EPP does not help. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:12:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 57C8A1578B for ; Thu, 27 Jan 2000 14:12:47 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id RAA09437; Thu, 27 Jan 2000 17:12:34 -0500 (EST) Date: Thu, 27 Jan 2000 17:12:34 -0500 (EST) From: "Matthew N. Dodd" To: Peter Wemm Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: ep0 incorrectly probed In-Reply-To: <20000127210436.15CE61CD4@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jan 2000, Peter Wemm wrote: > For example: > Logical device #0 > IO: 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 0x0534 > IRQ 5 0 > DMA 1 0 > IO range check 0x00 activate 0x01 > > versus: > pcm0: at port 0x534-0x537,0x388-0x38b,0x220-0x22f irq 5 drq 1,0 on isa0 > > Which is right? Does the device really have all 8 IO ranges assigned to > the same address? (0x534) Or is pnpinfo wrong? I dunno. Looks like pnpinfo is wrong when it comes to printing IO address ranges assigned. I do know that somehow or another the kernel PnP stuff isn't able to tell the card to use the assigned addresses but I don't get any failure messages (from the PnP code.) If you've got an Intel Etherexpress Pro/10 board you should be able to observe this. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:20:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by hub.freebsd.org (Postfix) with ESMTP id 6724215077 for ; Thu, 27 Jan 2000 14:20:32 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id OAA02574; Thu, 27 Jan 2000 14:20:40 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id OAA18497; Thu, 27 Jan 2000 14:22:46 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Thu, 27 Jan 2000 14:22:46 -0800 (PST) From: Brian Beattie To: Garrett Wollman Cc: "Jordan K. Hubbard" , Bill Fenner , current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: <200001272143.QAA20638@khavrinen.lcs.mit.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Garrett Wollman wrote: > < said: > > >> 3. On the first reboot after installing, the keyboard was in a funny > >> state. > > > Urk, can't reproduce it. I need a reproducible sequence of operations > > before we'll have any hope of tackling this one. > > >> Control-alt-del definitely didn't work, so I had to power off and > >> reboot. This hasn't repeated itself. > > > Same here. > > I have on a number of occasions had my laptop boot with a > non-functional keyboard. Sometimes the keyboard is just locked; other > times it generates garbage. Never managed to isolate the > circumstances in which this happened (but it didn't happen with a > kernel from last September or there-abouts). Haven't had it happen on > a desktop or server yet. > > -GAWollman As another sort of me-to, I use a non-standard key board from an ols lunch-box portable. It seems to have stopped working correctly in the boot-loader/visual config, although it still works fine in single-user and above. I mention this only in that it might be a useful data point, it has never been enough of a hassle for me to try to understand exactally what is going on, I just hook up a spare 101-key keyboard. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:30:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id 3EA8D14C94; Thu, 27 Jan 2000 14:30:34 -0800 (PST) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id RAA60010; Thu, 27 Jan 2000 17:34:01 -0500 (EST) From: Brian Hechinger Message-Id: <200001272234.RAA60010@entropy.tmok.com> Subject: ColdFusion 4.5 RC3 To: freebsd-questions@freebsd.org, freebsd-current@freebsd.org Date: Thu, 27 Jan 2000 17:34:01 -0500 (EST) Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I can consistantly get ColdFusion 4.5 RC3 installed on FreeBSD-current. It will not work on -stable (i didn't really mess with it too much however) i haven't gotten the Apache module to work yet (but i haven't even looked at it, so give me time) instructions are at http://users.tmok.com/~wonko/cf -wonko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:36:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 7070E150DD for ; Thu, 27 Jan 2000 14:36:24 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id RAA09780; Thu, 27 Jan 2000 17:36:21 -0500 (EST) Date: Thu, 27 Jan 2000 17:36:21 -0500 (EST) From: "Matthew N. Dodd" To: Eric Jacoboni Cc: current@FreeBSD.ORG Subject: Re: Something strange with pccard/ed0 ? In-Reply-To: <87d7qnfd2y.fsf@titine.fr.eu.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27 Jan 2000, Eric Jacoboni wrote: > All runs ok except that my card is not recognized as ed0 but as ed1. > > Here are my config params : > > =-=-=-= > device card0 > device pcic0 at isa? irq 10 port 0x3e0 iomem 0xd0000 > device pcic1 at isa? irq 11 port 0x3e2 iomem 0xd4000 > > device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 Thats correct. The kernel has assigned 'ed0' to the non-existent ISA card you've told it to expect. use 'device ed0' instead. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:37: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 7AB4B1587C; Thu, 27 Jan 2000 14:36:48 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id RAA54168; Thu, 27 Jan 2000 17:36:47 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001272236.RAA54168@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000127002323.B52191@dragon.nuxi.com> Date: Thu, 27 Jan 2000 17:36:47 -0500 (EST) From: John Baldwin To: "David O'Brien" Subject: RE: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-pass Cc: current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Jan-00 David O'Brien wrote: > I would appreciate it if those that want things changed would please try > Sheldon's `sed' expression below and report back how it worked for you. That will expose passwords of users whose entries are commented out, unfortunately. Then again, I've reverted the '-u' change on all my machines, so that doesn't apply to me all that much. Actually, since changed lines start with '+' or '-', that is going to expose passwords of changed accounts as well: > diff -u foo foo2 | sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/' --- foo Thu Jan 27 17:30:05 2000 +++ foo2 Thu Jan 27 17:30:53 2000 @@ -14,8 +14,8 @@ pop:(password):68:6::0:0:Post Office Owner:/nonexistent:/sbin/nologin nobody:(password):65534:65534::0:0:Unprivileged user:/nonexistent:/sbin/nologin ftp:(password):14:5::0:0:Anonymous FTP Admin:/var/ftp:/nonexistent -majordom:*:54:54::905054400:0:Majordomo Psuedo User:/usr/local/majordomo:/sbin/nologin -www:*:80:80::0:0:Web Server SandBox:/:/sbin/nologin +majordom:wacko:54:54::905054400:0:Majordomo Psuedo User:/usr/local/majordomo:/sbin/nologin +www:blah:80:80::0:0:Web Server SandBox:/:/sbin/nologin ccc:(password):902:902:standard:0:0:CCC CVS Repository Owner:/home/ccc:/sbin/nologin Have trouble seeing that change, btw? I find it harder to see than this: > diff foo foo2 | sed 's/^\([^:]*\):[^:]*:/\1:(password):/' 17,18c17,18 < majordom:(password):54:54::905054400:0:Majordomo Psuedo User:/usr/local/majordomo:/sbin/nologin < www:(password):80:80::0:0:Web Server SandBox:/:/sbin/nologin --- > majordom:(password):54:54::905054400:0:Majordomo Psuedo User:/usr/local/majordomo:/sbin/nologin > www:(password):80:80::0:0:Web Server SandBox:/:/sbin/nologin I agree that unified diff is more readable for things like code where context matters, but for password files, where each line is its own entity and there is no meaning in context, I see it as clutter that makes it harder to read. If 'joebob' user changes his password, I really don't care that the line in the passwd file above 'joebob's account is the account for 'billybob', I just care that 'joebob' changed his password. > ----- Forwarded message from Sheldon Hearn ----- > To: "David E. O'Brien" > Date: Wed, 26 Jan 2000 18:44:47 +0200 > > As discussed on the freebsd-current mailing list, I think you'll find > that you missed out a few characters in the new class that defines the > characters that should not appear at the beginning of affected lines: > >> - sed 's/^\([<>] [^:]*\):[^:]*:/\1:(password):/' >> + sed 's/^\([^:]*\):[^:]*:/\1:(password):/' > > I think what you really want is: > > sed 's/^\([^:#@+-]*\):[^:]*:/\1:(password):/' > > ----- End forwarded message ----- -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:38:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 5AE56156AB; Thu, 27 Jan 2000 14:38:30 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id WAA42972; Thu, 27 Jan 2000 22:38:26 GMT (envelope-from joe) Date: Thu, 27 Jan 2000 22:38:26 +0000 From: Josef Karthauser To: wonko@entropy.tmok.com Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: ColdFusion 4.5 RC3 Message-ID: <20000127223826.E97579@florence.pavilion.net> References: <200001272234.RAA60010@entropy.tmok.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001272234.RAA60010@entropy.tmok.com> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 05:34:01PM -0500, Brian Hechinger wrote: > I can consistantly get ColdFusion 4.5 RC3 installed on FreeBSD-current. > It will not work on -stable (i didn't really mess with it too much > however) > > i haven't gotten the Apache module to work yet (but i haven't even looked > at it, so give me time) > > instructions are at http://users.tmok.com/~wonko/cf > > -wonko Is this ColdFusion for Linux? Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:42:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 07C5115898 for ; Thu, 27 Jan 2000 14:42:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA40774; Thu, 27 Jan 2000 14:42:11 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA81638; Thu, 27 Jan 2000 14:42:08 -0800 (PST) (envelope-from obrien) Date: Thu, 27 Jan 2000 14:42:07 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000127144207.A81615@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001271856.KAA09456@windsor.research.att.com> <45272.949008490@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <45272.949008490@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 27, 2000 at 01:28:10PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 01:28:10PM -0800, Jordan K. Hubbard wrote: > > In this case, I actually assume that the DHCP server will be providing > the host name and specifically *ignore* the user-provide hostname IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't setup to provide hostnames to the requrestor. > > 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. > > I guess we need to build our own XF86 distribution with the a.out > libraries built or we need to somehow stuff those into a compat dist. If you want the added to src/lib/compat, let me know ASAP. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:43:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 37B9214F19 for ; Thu, 27 Jan 2000 14:43:39 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA40790; Thu, 27 Jan 2000 14:43:29 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA81651; Thu, 27 Jan 2000 14:43:30 -0800 (PST) (envelope-from obrien) Date: Thu, 27 Jan 2000 14:43:30 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000127144330.B81615@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001271856.KAA09456@windsor.research.att.com> <45272.949008490@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <45272.949008490@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 27, 2000 at 01:28:10PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 01:28:10PM -0800, Jordan K. Hubbard wrote: > > 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. > > I guess we need to build our own XF86 distribution with the a.out > libraries built or we need to somehow stuff those into a compat dist. OR we can make a [binary] port of it. This would not be hard to do. Let me know if you prefer this approach. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:45:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B47591570B for ; Thu, 27 Jan 2000 14:45:46 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id OAA40803; Thu, 27 Jan 2000 14:45:42 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id OAA81673; Thu, 27 Jan 2000 14:45:43 -0800 (PST) (envelope-from obrien) Date: Thu, 27 Jan 2000 14:45:43 -0800 From: "David O'Brien" To: Warner Losh Cc: current@freebsd.org Subject: Re: Comments on this patch? Message-ID: <20000127144543.C81615@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200001272144.OAA48475@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001272144.OAA48475@harmony.village.org>; from imp@village.org on Thu, Jan 27, 2000 at 02:44:27PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > BTW, I'm getting numbers that are 2x bigger than before :-(. I had > makebuildworld down to around 1:20 at one point, but now it is 2:40. Which compilers for both times? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:45:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by hub.freebsd.org (Postfix) with ESMTP id E87D915A30 for ; Thu, 27 Jan 2000 14:45:55 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id OAA05417; Thu, 27 Jan 2000 14:45:53 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id OAA19216; Thu, 27 Jan 2000 14:47:59 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Thu, 27 Jan 2000 14:47:59 -0800 (PST) From: Brian Beattie To: Bill Fenner Cc: rcarter@pinyon.org, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: <200001272205.OAA11110@windsor.research.att.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Bill Fenner wrote: > > >Right. I've seen this when I hit Enter rapidly twice at the first > >loader prompt. Doesn't ever happen if I wait for the second > >prompt. > > That's my impression too -- I've seen it on my laptop when I do > that (sometimes), and I may have hit enter twice rapidly on this > reboot. > > Bill Hmmm, I wonder it the boot loader is doing something funny in initializing the keyboard. Maybe something changed? Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:46:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from entropy.tmok.com (entropy.tmok.com [204.17.163.11]) by hub.freebsd.org (Postfix) with ESMTP id D42F4158C8; Thu, 27 Jan 2000 14:46:09 -0800 (PST) (envelope-from wonko@entropy.tmok.com) Received: (from wonko@localhost) by entropy.tmok.com (8.9.3/8.9.3) id RAA60178; Thu, 27 Jan 2000 17:49:39 -0500 (EST) From: Brian Hechinger Message-Id: <200001272249.RAA60178@entropy.tmok.com> Subject: Re: ColdFusion 4.5 RC3 In-Reply-To: <20000127223826.E97579@florence.pavilion.net> from Josef Karthauser at "Jan 27, 2000 10:38:26 pm" To: joe@pavilion.net (Josef Karthauser) Date: Thu, 27 Jan 2000 17:49:39 -0500 (EST) Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Reply-To: wonko@entropy.tmok.com X-Useless-Header: why? because i can. X-Organization: The Ministry of Knowledge X-Dreams: an OpenWin that is based on current MIT X11 releases X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Josef Karthauser drunkenly mumbled... > > Is this ColdFusion for Linux? yes. sorry about the confusion, i forgot to mention that. Allaire off-record said that they aren't happy with Linux and are seeking an alternative. i seem to be pushing them towards FreeBSD. but, keep in mind, this will be a huge shift in development for them, so if they ever do descide this, it still won't happen for a while. -brian -- ps: off-record means i will deny ever having said this even though you have proof. :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 14:55:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 3184F14F19; Thu, 27 Jan 2000 14:55:44 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id WAA46555; Thu, 27 Jan 2000 22:55:37 GMT (envelope-from joe) Date: Thu, 27 Jan 2000 22:55:37 +0000 From: Josef Karthauser To: wonko@entropy.tmok.com Cc: freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: ColdFusion 4.5 RC3 Message-ID: <20000127225537.F97579@florence.pavilion.net> References: <20000127223826.E97579@florence.pavilion.net> <200001272249.RAA60178@entropy.tmok.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001272249.RAA60178@entropy.tmok.com> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 05:49:39PM -0500, Brian Hechinger wrote: > Josef Karthauser drunkenly mumbled... > > > > Is this ColdFusion for Linux? > > yes. sorry about the confusion, i forgot to mention that. > Allaire off-record said that they aren't happy with Linux > and are seeking an alternative. i seem to be pushing > them towards FreeBSD. but, keep in mind, this will be a > huge shift in development for them, so if they ever do > descide this, it still won't happen for a while. Cool, I knew that if I held out long enough.... I wouldn't have to install solaris :) Cold Fusion on FreeBSD - an ISP's dream :) Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15: 0:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 71633158F2; Thu, 27 Jan 2000 15:00:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA07540; Thu, 27 Jan 2000 16:00:33 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA49240; Thu, 27 Jan 2000 16:00:40 -0700 (MST) Message-Id: <200001272300.QAA49240@harmony.village.org> To: obrien@freebsd.org Subject: Re: Comments on this patch? Cc: current@freebsd.org In-reply-to: Your message of "Thu, 27 Jan 2000 14:45:43 PST." <20000127144543.C81615@dragon.nuxi.com> References: <20000127144543.C81615@dragon.nuxi.com> <200001272144.OAA48475@harmony.village.org> Date: Thu, 27 Jan 2000 16:00:40 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000127144543.C81615@dragon.nuxi.com> "David O'Brien" writes: : > BTW, I'm getting numbers that are 2x bigger than before :-(. I had : > makebuildworld down to around 1:20 at one point, but now it is 2:40. : : Which compilers for both times? What ever was on -current as of 2.5 years ago. This is comparing the make buildworld of 3 years ago with the make buildworld of today. This was in the 8/5/97 timeframe. I got the buildworld time down to 1:20 on my machine with async mount options and two spindles. Now with the faster spindle and an even faster spindle, my buildworld times are 2:40. There may have been some things i turned off in the make.conf that I have on now. NOTCL was included before, for example. My machine was 128M in 97 and is 196M now. So I'd say this is with 2.7.3 and the compiler in today's current. There's so much that has changed in the last 2.5 years so this is more like grousing rather than pointing to a problem. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15:19:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id 6378615994 for ; Thu, 27 Jan 2000 15:19:23 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS3-p12.rlz.netvision.net.il [62.0.169.14]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id BAA01220; Fri, 28 Jan 2000 01:18:56 +0200 (IST) Message-ID: <3890D2B3.632DBE96@freenet.co.uk> Date: Thu, 27 Jan 2000 23:20:19 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Garrett Wollman Cc: "Jordan K. Hubbard" , Bill Fenner , current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT References: <200001271856.KAA09456@windsor.research.att.com> <45272.949008490@zippy.cdrom.com> <200001272143.QAA20638@khavrinen.lcs.mit.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Garrett Wollman wrote: > > < said: > > >> 3. On the first reboot after installing, the keyboard was in a funny > >> state. > > > Urk, can't reproduce it. I need a reproducible sequence of operations > > before we'll have any hope of tackling this one. > > >> Control-alt-del definitely didn't work, so I had to power off and > >> reboot. This hasn't repeated itself. > > > Same here. > > I have on a number of occasions had my laptop boot with a > non-functional keyboard. Sometimes the keyboard is just locked; other > times it generates garbage. Never managed to isolate the > circumstances in which this happened (but it didn't happen with a > kernel from last September or there-abouts). Haven't had it happen on > a desktop or server yet. > > -GAWollman Yeah, happens here too, every now and again. I boot straight into xdm, so it might have something to do with X, but any attempts to type in the username generate garbage. I can't switch to a text console, because Ctrl-Alt-Fx keys don't work either - all I can do is push the Big Red Button. The graphics card in my laptop is Chips & Technology 65555. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15:21:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (Postfix) with SMTP id 122D815892 for ; Thu, 27 Jan 2000 15:21:08 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA26648; Thu, 27 Jan 2000 18:24:53 -0500 From: Bill Paul Message-Id: <200001272324.SAA26648@skynet.ctr.columbia.edu> Subject: Re: Problems with an0 and ISA Aironet Card.. To: paul@pulsat.com.au (Paul Reece) Date: Thu, 27 Jan 2000 18:24:52 -0500 (EST) Cc: current@freebsd.org In-Reply-To: from "Paul Reece" at Jan 20, 2000 05:35:16 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3944 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Paul Reece had to walk into mine and say: > On Thu, 20 Jan 2000, Bill Paul wrote: > > > > > Back up. You're leaving out some info. > > > > - When did you buy these cards? (The firmware rev may be an issue. > > knowing when you bought the card helps me figure out if your firmware > > is newer than mine.) > > Cards were purchased in the past 6 months. Revision of the card I'm using > at the moment is 3.13 - I upgraded the firmware to the latest. (Win DGS > under 'status' reports 3.13). You can view the firmware rev with the if_an driver (when it works) by doing ancontrol -i an0 -I. The newest PCMCIA card that I have seems to be using revision 3.10. The ISA card that I have is using 2.06. The trouble is I don't have Windows machine set up to run the firmware update utility. What I tried to do today was swap the PCMCIA module on my existing ISA card with one of the new ones with the later firmware. I did this a while back when I got our first batch of cards. However, I can't do it now. One of the problems I had with the Aironet cards initially is that they were set up so that they would operate in two modes: if you applied +5volts to the vpp1 and vpp2 pins on the PCMCIA module, it would work in PCMCIA mode such that you could get at the CIS data and configure it like any other PCMCIA card. Without the +5volts, the module would work in a special 'dumb bus' mode that would allow it to interface with the ISA and PCI bridge adapter cards that Aironet uses for their ISA and PCI cards. Basically, this allows them to make just one PCMCIA module and use it in all three kinds of cards. However the latest PCMCIA cards that we just got are different: now they always work in PCMCIA mode regardless of how vpp1 and vpp2 are set. On the one hand, this is good because it means you don't have to frob sys/pccard/pccard.c to enable the vpp voltage when the card is inserted. (My older cards will not work with FreeBSD unless I apply this tweak to the kernel.) On the other hand, this means that the newer PCMCIA cards won't work in the ISA and PCI bridge adapters. This sort of stymied my attempts to duplicate your problem here in the lab. What would be nice is if you could somehow set up a scratch box with an Aironet ISA4800 card in it that I could access remotely. I'm reasonably confident I could make it work if I could just experiment with it for a while. Unfortunately, this may not be possible depending on technical on various political constraints, especially since I need to twiddle around as root in order to examine register contents and test a new driver. > pcpaul# ./testa > COMMAND: 0 > PARAM0: ff11 > PARAM0: 0x > > (still no lights on card) > if I run it again: > > pcpaul# ./testa > COMMAND: 0 > PARAM0: 1234 > PARAM0: 0x > > (and still no lights). > > > This info help at all? Well, yes. It tells me two things. First, it tells me that I made a typo on the program that I gave you. :) Second, it shows me that the card is at the I/O address that it's supposed to be, although it appears to not be responding to the 'read SSID list' command that the if_an driver issues during the probe phase. Unfortunately, as I said earlier, I need to be able to experiment on this thing in order to figure out the problem, and I can't do that unless you can somehow arrange remote access. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15:21:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 5FB7D15853 for ; Thu, 27 Jan 2000 15:21:32 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA02514; Thu, 27 Jan 2000 15:29:53 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001272329.PAA02514@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Beattie Cc: Bill Fenner , rcarter@pinyon.org, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 14:47:59 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 15:29:53 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 27 Jan 2000, Bill Fenner wrote: > > > > > >Right. I've seen this when I hit Enter rapidly twice at the first > > >loader prompt. Doesn't ever happen if I wait for the second > > >prompt. > > > > That's my impression too -- I've seen it on my laptop when I do > > that (sometimes), and I may have hit enter twice rapidly on this > > reboot. > > > > Bill > Hmmm, I wonder it the boot loader is doing something funny in initializing > the keyboard. Maybe something changed? It doesn't do anything to the keyboard, it just calls the BIOS to find out whether keys have been pressed. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15:24:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 7AF231586E for ; Thu, 27 Jan 2000 15:24:20 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id RAA20910; Thu, 27 Jan 2000 17:24:16 -0600 (CST) (envelope-from dan) Date: Thu, 27 Jan 2000 17:24:16 -0600 From: Dan Nelson To: Emre Cc: freebsd-current@FreeBSD.ORG Subject: Re: .bash_history and permissions Message-ID: <20000127172415.A19202@dan.emsphone.com> References: <20000127155328.A32492@iris.vsrc.uab.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000127155328.A32492@iris.vsrc.uab.edu>; from "Emre" on Thu Jan 27 15:53:28 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 27), Emre said: > I'm running FreeBSD 4.0 from Dec. 26 1999. This should be on the "general > questions" malininglist, but I thought maybe there is something that changed > from -stable to -current that does this: > > I'm trying to limit permissions on .bash_history. There have been users > on my server that have linked .bash_history to /dev/null and then been > doing some cracking, and attacking other servers. To limit this (or at > least trying to control it) I tried to take out write permission for > group and others, thinking that will stop the users from trying to mod- > ify the file. That didn't work! Even if I did "chmod 000 .bash_history" > users still could delete the file or modify it. So I thought maybe if I > just change the group or the owner of the file, it would fix the problem > that didn't work either...now it wouldn't log the commands to the history > file anymore. Are you also running a modified bash that removes the HISTFILE and HISTFILESIZE environment variables, and have you also removed /bin/sh and all other shells that don't log commands (* NOTE: do not remove /bin/sh *) ? > So I was wondering, do any of you gurus and bofh know how to fix this? > This is very imporant for me, I'd be _very_ thankful if anyone could > help me fix this problem. > > (PS: In other's OSs i.e Solaris or Linsucks, changing the perms seemd > to work, just not in FreeBSD) Delete permission comes from the directory, not the file. No amount of chmod'ing the file will affect it. Under FreeBSD, you can run "chflags sappnd,sunlnk .bash_history" to make the file undeletable, append-only. Under other Unixes, the user can simply do a "cp /dev/null ~/.bash_history && kill -9 $$" to log out with no history file. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15:25:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 7BEC415949; Thu, 27 Jan 2000 15:25:35 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id SAA60073; Thu, 27 Jan 2000 18:25:30 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001272325.SAA60073@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000127144207.A81615@dragon.nuxi.com> Date: Thu, 27 Jan 2000 18:25:30 -0500 (EST) From: John Baldwin To: "David O'Brien" Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: current@FreeBSD.org, "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Jan-00 David O'Brien wrote: > On Thu, Jan 27, 2000 at 01:28:10PM -0800, Jordan K. Hubbard wrote: >> >> In this case, I actually assume that the DHCP server will be providing >> the host name and specifically *ignore* the user-provide hostname > > IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't > setup to provide hostnames to the requrestor. Why not check to see what the hostname is after dhclient is run and then stick that name in the network setup dialog box. If the user does edit the hostname themselves, then you can flag that event, and use that flag when writing out /etc/rc.conf to mean that the hostname variable should be set. Actually, this doesn't work all that well because the boot floppy doesn't include /bin/hostname in the crunch so /sbin/dhclient-script can't set the hostname when it is sent out by a dhcp server. >> > 4. X didn't come with /usr/X11R6/lib/aout, so I can't run netscape. >> >> I guess we need to build our own XF86 distribution with the a.out >> libraries built or we need to somehow stuff those into a compat dist. > > If you want the added to src/lib/compat, let me know ASAP. > > -- > -- David (obrien@NUXI.com) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15:31:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (mail.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 3AFC114D8D for ; Thu, 27 Jan 2000 15:31:48 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <115205>; Fri, 28 Jan 2000 10:32:18 +1100 Content-return: prohibited From: Peter Jeremy Subject: Re: Comments on this patch? In-reply-to: <200001272300.QAA49240@harmony.village.org>; from imp@village.org on Fri, Jan 28, 2000 at 10:02:06AM +1100 To: Warner Losh Cc: current@FreeBSD.ORG Message-Id: <00Jan28.103218est.115205@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <20000127144543.C81615@dragon.nuxi.com> <200001272144.OAA48475@harmony.village.org> <20000127144543.C81615@dragon.nuxi.com> <200001272300.QAA49240@harmony.village.org> Date: Fri, 28 Jan 2000 10:32:18 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2000-Jan-28 10:02:06 +1100, Warner Losh wrote: >In message <20000127144543.C81615@dragon.nuxi.com> "David O'Brien" writes: >: > BTW, I'm getting numbers that are 2x bigger than before :-(. I had >: > makebuildworld down to around 1:20 at one point, but now it is 2:40. ... >So I'd say this is with 2.7.3 and the compiler in today's current. >There's so much that has changed in the last 2.5 years so this is more >like grousing rather than pointing to a problem. FreeBSD itself is significantly larger - at a guess, I'd say that 4.0-CURRENT is about 50% larger than 2.x. I suspect (though I haven't done any direct comparisons) that today's egcs is slower than 2.7.3. Also, following Marcel's work, buildworld is now far more careful about ensuring that tools it wants to use are built correctly for the environment they are going to be used in - which means that far more of the system is built multiple times during a buildworld. Overall, a 2:1 slowdown doesn't really surprise me. It would be nice if it was smaller though. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15:31:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id 216F715589 for ; Thu, 27 Jan 2000 15:31:54 -0800 (PST) (envelope-from jaco@titine.fr.eu.org) Received: from titine.fr.eu.org (unknown [213.228.46.207]) by postfix1.free.fr (Postfix) with ESMTP id EAA6D280F1 for ; Fri, 28 Jan 2000 00:31:50 +0100 (MET) Received: by titine.fr.eu.org (Postfix, from userid 1000) id ACF38148DC; Fri, 28 Jan 2000 00:24:57 +0100 (CET) To: current@FreeBSD.ORG Subject: Re: Something strange with pccard/ed0 ? References: From: Eric Jacoboni Date: 28 Jan 2000 00:24:56 +0100 In-Reply-To: "Matthew N. Dodd"'s message of "Thu, 27 Jan 2000 17:36:21 -0500 (EST)" Message-ID: <87zotrdrnb.fsf@titine.fr.eu.org> Lines: 18 X-Mailer: Gnus v5.6.45/XEmacs 21.1 - "Bryce Canyon" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Matthew N. Dodd" writes: > On 27 Jan 2000, Eric Jacoboni wrote: > > All runs ok except that my card is not recognized as ed0 but as ed1. > > device ed0 at isa? port 0x280 irq 5 iomem 0xd8000 > > Thats correct. The kernel has assigned 'ed0' to the non-existent ISA card > you've told it to expect. > > use 'device ed0' instead. Oops... Thanks for your help, it's ok now. -- --------------------------------------------------------- Éric Jacoboni Ğ No sport, cigars! ğ (W. Churchill) --------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15:56: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id E7BEC158A9 for ; Thu, 27 Jan 2000 15:56:00 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA07859; Thu, 27 Jan 2000 16:55:56 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA49806; Thu, 27 Jan 2000 16:56:04 -0700 (MST) Message-Id: <200001272356.QAA49806@harmony.village.org> To: Eric Jacoboni Subject: Re: Something strange with pccard/ed0 ? Cc: current@FreeBSD.ORG In-reply-to: Your message of "27 Jan 2000 21:56:37 +0100." <87d7qnfd2y.fsf@titine.fr.eu.org> References: <87d7qnfd2y.fsf@titine.fr.eu.org> Date: Thu, 27 Jan 2000 16:56:04 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <87d7qnfd2y.fsf@titine.fr.eu.org> Eric Jacoboni writes: : that ed0 already exists ? Because there is an ed0 on isa already, even if it isn't attached. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15:58:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id A1E5B158BA for ; Thu, 27 Jan 2000 15:58:25 -0800 (PST) (envelope-from leifn@neland.dk) Received: from gina (gina.neland.dk [192.168.0.14]) by arnold.neland.dk (8.9.3/8.9.3) with SMTP id AAA93139; Fri, 28 Jan 2000 00:58:17 +0100 (CET) (envelope-from leifn@neland.dk) Message-ID: <00ab01bf6922$78c8e6e0$0e00a8c0@neland.dk> Reply-To: "Leif Neland" From: "Leif Neland" To: "Emre" , References: <20000127155328.A32492@iris.vsrc.uab.edu> Subject: Re: .bash_history and permissions Date: Fri, 28 Jan 2000 00:56:48 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message -----=20 From: "Emre" To: Sent: Thursday, January 27, 2000 4:53 PM Subject: .bash_history and permissions > Hi folks! >=20 > I'm running FreeBSD 4.0 from Dec. 26 1999. This should be on the = "general > questions" malininglist, but I thought maybe there is something that = changed > from -stable to -current that does this: >=20 > I'm trying to limit permissions on .bash_history. There have been = users > on my server that have linked .bash_history to /dev/null and then been > doing some cracking, and attacking other servers. for x in `cut -d: -f1 /etc/passwd` do if [ ! -r ~$x/.bash_history ] then userdel -r $x fi done To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 15:59:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B271215986; Thu, 27 Jan 2000 15:59:20 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id QAA07888; Thu, 27 Jan 2000 16:59:05 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA49853; Thu, 27 Jan 2000 16:59:11 -0700 (MST) Message-Id: <200001272359.QAA49853@harmony.village.org> To: Mike Smith Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: Brian Beattie , Bill Fenner , rcarter@pinyon.org, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 27 Jan 2000 15:29:53 PST." <200001272329.PAA02514@mass.cdrom.com> References: <200001272329.PAA02514@mass.cdrom.com> Date: Thu, 27 Jan 2000 16:59:10 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001272329.PAA02514@mass.cdrom.com> Mike Smith writes: : It doesn't do anything to the keyboard, it just calls the BIOS to find : out whether keys have been pressed. I've been seeing the hit twice fast problem for months. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16: 5:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id E4FC714C03; Thu, 27 Jan 2000 16:05:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03163; Thu, 27 Jan 2000 16:14:48 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001280014.QAA03163@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: Mike Smith , Brian Beattie , Bill Fenner , rcarter@pinyon.org, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 16:59:10 MST." <200001272359.QAA49853@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 16:14:48 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <200001272329.PAA02514@mass.cdrom.com> Mike Smith writes: > : It doesn't do anything to the keyboard, it just calls the BIOS to find > : out whether keys have been pressed. > > I've been seeing the hit twice fast problem for months. It's always been a problem; we don't understand the mechanics of it however. Susceptibility varies widely between systems, and the best hypothesis I've been able to come up with is that there are issues with taking interrupts in vm86 mode; possibly the BIOS is being re-entered in a fashion it doesn't like. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16: 5:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8EF7E158E1; Thu, 27 Jan 2000 16:05:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA46149; Thu, 27 Jan 2000 16:06:31 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 14:42:07 PST." <20000127144207.A81615@dragon.nuxi.com> Date: Thu, 27 Jan 2000 16:06:31 -0800 Message-ID: <46146.949017991@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't > setup to provide hostnames to the requrestor. Seems they're set up incorrectly then. You can't be a good "network citizen" these days without a resolvable hostname that also matches your primary IP address or, among other things, you won't be able to send mail directly to anyone who practices traditional spam filtering techniques. This also isn't just pedantry because, as I noted before, specifying the hostname will currently cause it to override the DHCP hostname value even if it is specified (as it certainly is on *my* DHCP server :-) and result in broken behavior for the aformentioned mailers. If we were to fix that in our rc scripts, I could remove this assumption in sysinstall in good conscience. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16: 6:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2457815853; Thu, 27 Jan 2000 16:06:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA46165; Thu, 27 Jan 2000 16:07:03 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 14:43:30 PST." <20000127144330.B81615@dragon.nuxi.com> Date: Thu, 27 Jan 2000 16:07:03 -0800 Message-ID: <46162.949018023@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OR we can make a [binary] port of it. This would not be hard to do. > Let me know if you prefer this approach. I think the easiest and most POLA-friendly approach would be to add them [back] to Xbin.tgz. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16: 7:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A856115853; Thu, 27 Jan 2000 16:07:53 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA07957; Thu, 27 Jan 2000 17:07:51 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA49979; Thu, 27 Jan 2000 17:07:59 -0700 (MST) Message-Id: <200001280007.RAA49979@harmony.village.org> To: Mike Smith Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: Brian Beattie , Bill Fenner , rcarter@pinyon.org, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 27 Jan 2000 16:14:48 PST." <200001280014.QAA03163@mass.cdrom.com> References: <200001280014.QAA03163@mass.cdrom.com> Date: Thu, 27 Jan 2000 17:07:59 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001280014.QAA03163@mass.cdrom.com> Mike Smith writes: : > In message <200001272329.PAA02514@mass.cdrom.com> Mike Smith writes: : > : It doesn't do anything to the keyboard, it just calls the BIOS to find : > : out whether keys have been pressed. : > : > I've been seeing the hit twice fast problem for months. : : It's always been a problem; we don't understand the mechanics of it : however. Susceptibility varies widely between systems, and the best : hypothesis I've been able to come up with is that there are issues with : taking interrupts in vm86 mode; possibly the BIOS is being re-entered in : a fashion it doesn't like. Just wanted to make sure you acknowledged the problem. It sounded like you were saying that it wasn't a problem at all rather than the theory put forward wasn't likely the problem. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16: 8:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 284B115A80 for ; Thu, 27 Jan 2000 16:08:33 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (28-161.008.popsite.net [209.69.13.161]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id QAA17970; Thu, 27 Jan 2000 16:08:28 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 0C04D1B0D; Thu, 27 Jan 2000 19:08:26 -0500 (EST) Date: Thu, 27 Jan 2000 19:08:25 -0500 From: Will Andrews To: Bill Fenner Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000127190825.E32759@shadow.blackdawn.com> References: <200001271856.KAA09456@windsor.research.att.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001271856.KAA09456@windsor.research.att.com>; from fenner@research.att.com on Thu, Jan 27, 2000 at 10:56:39AM -0800 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 10:56:39AM -0800, Bill Fenner wrote: > never made it into rc.conf (it booted up calling itself Amnesiac). You know, I always thought that some people (well, certainly not me) would find the default name "Amnesiac" a slight bit offensive, since it implies they're forgetful. Perhaps something more like "myhost" would be a better default. Just a thought... -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16:12:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id D80E0158E1; Thu, 27 Jan 2000 16:12:15 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03272; Thu, 27 Jan 2000 16:20:54 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001280020.QAA03272@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jordan K. Hubbard" Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 16:06:31 PST." <46146.949017991@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 16:20:54 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't > > setup to provide hostnames to the requrestor. > > Seems they're set up incorrectly then. You can't be a good "network > citizen" these days without a resolvable hostname that also matches > your primary IP address or, among other things, you won't be able to > send mail directly to anyone who practices traditional spam filtering > techniques. Actually, the problem here is that our dhclient doesn't pick the hostname up the first time around. If it's set in an existing lease that is just confirmed, it works, but if you're starting without a lease, you won't get a hostname set (but it will be in the lease file, so if you restart before the lease expires you're OK). > This also isn't just pedantry because, as I noted before, specifying > the hostname will currently cause it to override the DHCP hostname > value even if it is specified (as it certainly is on *my* DHCP server :-) > and result in broken behavior for the aformentioned mailers. If we > were to fix that in our rc scripts, I could remove this assumption in > sysinstall in good conscience. Personally I'd prefer to just fix the DHCP client so that it correctly sets the hostname as obtained from the server... -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16:13:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id E481C15C2A; Thu, 27 Jan 2000 16:13:32 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA46201; Thu, 27 Jan 2000 16:14:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Baldwin Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 18:25:30 EST." <200001272325.SAA60073@server.baldwin.cx> Date: Thu, 27 Jan 2000 16:14:15 -0800 Message-ID: <46198.949018455@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why not check to see what the hostname is after dhclient is run and then > stick that name in the network setup dialog box. If the user does edit > the hostname themselves, then you can flag that event. That would work in that one specific case with that specific dhcp server. Now change the dhcp server post-install time and watch what happens. :-) What is clearly needed is some idea of "fallback hostname" vs the one you *might* be automatically assigned by "something else" (one current value for something else being DHCP) and should probably use preferentially. Split the hostname into two variables and do the appropriate rc dance magic, off ya go. Of course, this also fails to address a more fundamental failing in our rc scripts, this being that the concept of "network identity" is currently handled in too simplistic a fashion. When dealing with the "local vs on the road" scenario, many laptop users (including myself) end up hand-editing their rc.conf files or adding some cheesy menu to the rc files which say, in effect, "choose one of the following canned configurations" and then go work the appropriate variable-setting magic. The fact that I've seen so many people re-invent this particular wheel also sends a strong hint that a better, more general, mechanism is now overdue. As the original architect of FreeBSD's rc.conf (nee /etc/sysconfig) mechanism, I can also say with some assurance that it's reached its limits. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16:15:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id 80FA115798 for ; Thu, 27 Jan 2000 16:15:20 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (28-161.008.popsite.net [209.69.13.161]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id QAA18129; Thu, 27 Jan 2000 16:15:17 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 799E51AF0; Thu, 27 Jan 2000 19:15:16 -0500 (EST) Date: Thu, 27 Jan 2000 19:15:16 -0500 From: Will Andrews To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Comments on this patch? Message-ID: <20000127191516.F32759@shadow.blackdawn.com> References: <200001272144.OAA48475@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001272144.OAA48475@harmony.village.org>; from imp@village.org on Thu, Jan 27, 2000 at 02:44:27PM -0700 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 02:44:27PM -0700, Warner Losh wrote: > I've been running this for a while. I reversed the normal order to > make it easier to do the math w/o having to shift columns and flip > things over. Thanks for the patch! It'd be nice to time the buildworld only. Is there a timed installworld? (I think `make world` is the only one, but I never really cared that much for these stats anyway ;-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16:21:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id EDCB114E71; Thu, 27 Jan 2000 16:21:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA46288; Thu, 27 Jan 2000 16:22:32 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Mike Smith Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 16:20:54 PST." <200001280020.QAA03272@mass.cdrom.com> Date: Thu, 27 Jan 2000 16:22:32 -0800 Message-ID: <46285.949018952@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Personally I'd prefer to just fix the DHCP client so that it correctly > sets the hostname as obtained from the server... Yeah David, sheesh! ;) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16:32:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id C800315906 for ; Thu, 27 Jan 2000 16:32:17 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 7458 invoked from network); 28 Jan 2000 00:32:12 -0000 Received: from lcm97.cvzoom.net (208.230.69.97) by ns.cvzoom.net with SMTP; 28 Jan 2000 00:32:12 -0000 Date: Thu, 27 Jan 2000 19:31:50 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: Errors compiling kernel... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently cvsup'd the sources (around Thu Jan 27 19:30:48 EST 2000), and I'm getting these errors compiling the kernel: cc -c -mpentium -O3 -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/ata/atapi-all.c ../../dev/ata/atapi-all.c: In function `atapi_attach': ../../dev/ata/atapi-all.c:96: syntax error before `}' *** Error code 1 Stop in /usr/src/sys/compile/CUSTOM. - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16:33: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id A8AAD14E80 for ; Thu, 27 Jan 2000 16:33:00 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:Hcbz1mqLTdFrJCO3UH0kslKHyOV7NVIr@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id JAA07221; Fri, 28 Jan 2000 09:32:23 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA12998; Fri, 28 Jan 2000 09:38:01 +0900 (JST) Message-Id: <200001280038.JAA12998@zodiac.mech.utsunomiya-u.ac.jp> To: Garrett Wollman Cc: "Jordan K. Hubbard" , Bill Fenner , current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 16:43:46 EST." <200001272143.QAA20638@khavrinen.lcs.mit.edu> References: <200001271856.KAA09456@windsor.research.att.com> <45272.949008490@zippy.cdrom.com> <200001272143.QAA20638@khavrinen.lcs.mit.edu> Date: Fri, 28 Jan 2000 09:38:00 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> 3. On the first reboot after installing, the keyboard was in a funny >>> state. > >> Urk, can't reproduce it. I need a reproducible sequence of operations >> before we'll have any hope of tackling this one. > >>> Control-alt-del definitely didn't work, so I had to power off and >>> reboot. This hasn't repeated itself. > >> Same here. > >I have on a number of occasions had my laptop boot with a >non-functional keyboard. Sometimes the keyboard is just locked; other >times it generates garbage. Never managed to isolate the >circumstances in which this happened (but it didn't happen with a >kernel from last September or there-abouts). Haven't had it happen on >a desktop or server yet. I have had reports on similar lockup in both 4.0-CURRENT and 3.X. I personally have not been able to reproduce it, but now my new sand box machine exhibits this problem occasionally. The I/O access to the AT keyboard by the atkbd driver have not changed much for the last couple of years, despite massive source tree reorganization. And yes, problem reports started to pop-up since sometime around the last summer. I have not been able to track down the cause of the problem, but am suspecting possibility of the clock/timer problem. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16:35:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 88C4F1595A for ; Thu, 27 Jan 2000 16:35:18 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:2MDKfTTmyoaQcU2WpagAfCLau+aCv0OS@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id JAA07089; Fri, 28 Jan 2000 09:35:03 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id JAA13107; Fri, 28 Jan 2000 09:40:40 +0900 (JST) Message-Id: <200001280040.JAA13107@zodiac.mech.utsunomiya-u.ac.jp> To: Mike Heffner Cc: "Jordan K. Hubbard" , current@freebsd.org, Bill Fenner , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 16:54:50 EST." References: Date: Fri, 28 Jan 2000 09:40:39 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I seem to have this problem occasionaly, the keyboard keymap gets all screwed >up somehow, and the only way to get out is to hit the reset button. But I've >been having the problem for a long time, and with different boxes. It happens >about every 1 out of 15 reboots but randomly. I haven't been able to connect >it to any event or anything, but I notice that hitting keys during boot can >increase the probability of it occurring, but again, nothing reproducible. If you hit any key while the keyboard driver is trying to initialize the keyboard, there is a good possibility that the driver will be screwed. But, it mustn't show problems if you hit the keyboard during the boot loader or after the driver is attached... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16:36:13 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A3AE015942; Thu, 27 Jan 2000 16:36:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 8D0221CD6BC; Thu, 27 Jan 2000 16:36:09 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 27 Jan 2000 16:36:09 -0800 (PST) From: Kris Kennaway To: Jorge Aldana Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: MD5 Sigs on 3.4-20000124-STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000, Jorge Aldana wrote: > I checked the signatures on the files I downloaded from > current.freebsd.org/pub/FreeBSD/snapshots/i386/3.4-20000124-STABLE/ > > and the following fail the MD5 check: > > < = from CHECKSUM.MD5 listing > > = downloaded file. These all check out for me. Were the files truncated during download for you or something? Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16:42:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.ghis.net (rock.ghis.net [209.222.164.7]) by hub.freebsd.org (Postfix) with ESMTP id A88C014E80; Thu, 27 Jan 2000 16:42:52 -0800 (PST) (envelope-from will@blackdawn.com) Received: from shadow.blackdawn.com (28-161.008.popsite.net [209.69.13.161]) by rock.ghis.net (8.9.3/8.9.3) with ESMTP id QAA18880; Thu, 27 Jan 2000 16:42:29 -0800 (PST) Received: by shadow.blackdawn.com (Postfix, from userid 1000) id 025A71AF0; Thu, 27 Jan 2000 19:42:17 -0500 (EST) Date: Thu, 27 Jan 2000 19:42:17 -0500 From: Will Andrews To: Donn Miller Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: Errors compiling kernel... Message-ID: <20000127194217.H32759@shadow.blackdawn.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dmmiller@cvzoom.net on Thu, Jan 27, 2000 at 07:31:50PM -0500 X-Operating-System: FreeBSD 3.4-STABLE i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 07:31:50PM -0500, Donn Miller wrote: > I recently cvsup'd the sources (around Thu Jan 27 19:30:48 EST 2000), and > I'm getting these errors compiling the kernel: > > cc -c -mpentium -O3 -pipe -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL > -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/ata/atapi-all.c > ../../dev/ata/atapi-all.c: In function `atapi_attach': > ../../dev/ata/atapi-all.c:96: syntax error before `}' > *** Error code 1 Soren Schmidt (sos) made some recent commits to the ATA driver. Perhaps these problems are the result. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 16:56:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from tesla-e0.salk.edu (tesla-e0.salk.edu [198.202.70.1]) by hub.freebsd.org (Postfix) with ESMTP id B428915853; Thu, 27 Jan 2000 16:56:23 -0800 (PST) (envelope-from jorge@salk.edu) Received: from axelrod.salk.edu (axelrod.salk.edu [198.202.70.121]) by tesla-e0.salk.edu (8.7.5/8.7.3) with SMTP id QAA14532; Thu, 27 Jan 2000 16:56:30 -0800 (PST) Date: Thu, 27 Jan 2000 16:55:43 -0800 (PST) From: Jorge Aldana To: Kris Kennaway Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: MD5 Sigs on 3.4-20000124-STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, the ftp app (IglooFTP Alpha v0.6.1) I was using consistently corrupted/truncated the same files which made it difficult to pin point, basic ftp took care of it. Sorry for the worry. Jorge On Thu, 27 Jan 2000, Kris Kennaway wrote: > On Wed, 26 Jan 2000, Jorge Aldana wrote: > > > I checked the signatures on the files I downloaded from > > current.freebsd.org/pub/FreeBSD/snapshots/i386/3.4-20000124-STABLE/ > > > > and the following fail the MD5 check: > > > > < = from CHECKSUM.MD5 listing > > > = downloaded file. > > These all check out for me. Were the files truncated during download for > you or something? > > Kris > > ---- > "How many roads must a man walk down, before you call him a man?" > "Eight!" > "That was a rhetorical question!" > "Oh..then, seven!" -- Homer Simpson > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 17: 9: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E5D48157AD; Thu, 27 Jan 2000 17:08:05 -0800 (PST) (envelope-from fenner@FreeBSD.org) Received: (from fenner@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id RAA97194; Thu, 27 Jan 2000 17:08:05 -0800 (PST) (envelope-from fenner@FreeBSD.org) Date: Thu, 27 Jan 2000 17:08:05 -0800 (PST) From: Message-Id: <200001280108.RAA97194@freefall.freebsd.org> To: andrews@technologist.com Subject: Re: buildworld failure in "===> makeinfo" Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>whereintheworld.pl (thanxs Bill Fenner) shows ... >What does this Perl script do? :-) See http://www.freebsd.org/~fenner/ - it parses "make world" output in a way that gives slightly better progress info than just a "tail". Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 17:38:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id F08C915835; Thu, 27 Jan 2000 17:38:08 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:lql3hrOhwA+vyykbesEa19DSu3eJa7im@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id KAA08561; Fri, 28 Jan 2000 10:37:59 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id KAA15711; Fri, 28 Jan 2000 10:43:37 +0900 (JST) Message-Id: <200001280143.KAA15711@zodiac.mech.utsunomiya-u.ac.jp> To: Mike Smith Cc: Warner Losh , Brian Beattie , Bill Fenner , rcarter@pinyon.org, current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 16:14:48 PST." <200001280014.QAA03163@mass.cdrom.com> References: <200001280014.QAA03163@mass.cdrom.com> Date: Fri, 28 Jan 2000 10:43:35 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> In message <200001272329.PAA02514@mass.cdrom.com> Mike Smith writes: >> : It doesn't do anything to the keyboard, it just calls the BIOS to find >> : out whether keys have been pressed. >> >> I've been seeing the hit twice fast problem for months. > >It's always been a problem; we don't understand the mechanics of it >however. Susceptibility varies widely between systems, and the best >hypothesis I've been able to come up with is that there are issues with >taking interrupts in vm86 mode; possibly the BIOS is being re-entered in >a fashion it doesn't like. I wonder if the keyboard interrupt is blocked for a prolonged period in the boot loader because of vm86, and quite a number of (up to 16 or something) scan codes are waiting in the keyboard to be received by the host computer, when the kernel is loaded. The keyboard driver atkbd tries to flush pending scan codes, left over from the boot loader, before it starts initializing the keyboard. It may be failing to flush all the pending scan codes if there are too many of them. The following patch will make the driver wait slightly longer to flush inputs. I would like to see if this makes any difference. I should come up with something better this, though... Kazu Index: atkbd.c =================================================================== RCS file: /src/CVS/src/sys/dev/kbd/atkbd.c,v retrieving revision 1.22 diff -u -r1.22 atkbd.c --- atkbd.c 2000/01/20 13:32:53 1.22 +++ atkbd.c 2000/01/28 00:47:27 @@ -1085,7 +1098,7 @@ } /* flush any noise in the buffer */ - empty_both_buffers(kbdc, 10); + empty_both_buffers(kbdc, 200); /* save the current keyboard controller command byte */ m = kbdc_get_device_mask(kbdc) & ~KBD_KBD_CONTROL_BITS; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 17:41:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4D7A315724 for ; Thu, 27 Jan 2000 17:41:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id RAA03609; Thu, 27 Jan 2000 17:41:05 -0800 (PST) (envelope-from dillon) Date: Thu, 27 Jan 2000 17:41:05 -0800 (PST) From: Matthew Dillon Message-Id: <200001280141.RAA03609@apollo.backplane.com> To: Will Andrews Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: Comments on this patch? References: <200001272144.OAA48475@harmony.village.org> <20000127191516.F32759@shadow.blackdawn.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Thu, Jan 27, 2000 at 02:44:27PM -0700, Warner Losh wrote: :> I've been running this for a while. I reversed the normal order to :> make it easier to do the math w/o having to shift columns and flip :> things over. : :Thanks for the patch! It'd be nice to time the buildworld only. Is there :a timed installworld? (I think `make world` is the only one, but I never :really cared that much for these stats anyway ;-) : :-- :Will Andrews :GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- I just use the 'time' csh/tcsh variable: time Control automatic timing of commands. If set, then any com- mand that takes more than this many cpu seconds will cause a line giving user, system, and real times and a utilization percentage which is the ratio of user plus system times to re- al time to be printed when it terminates. I set it to something relatively high, like 15 minutes. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 17:57:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id BC74D157BA; Thu, 27 Jan 2000 17:57:17 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id UAA21728; Thu, 27 Jan 2000 20:57:08 -0500 (EST) (envelope-from wollman) Date: Thu, 27 Jan 2000 20:57:08 -0500 (EST) From: Garrett Wollman Message-Id: <200001280157.UAA21728@khavrinen.lcs.mit.edu> To: "Jordan K. Hubbard" Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: <46146.949017991@zippy.cdrom.com> References: <20000127144207.A81615@dragon.nuxi.com> <46146.949017991@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > citizen" these days without a resolvable hostname that also matches > your primary IP address or, among other things, you won't be able to > send mail directly to anyone who practices traditional spam filtering > techniques. However, there is no need to actually use the configured hostname for this purpose. `temp-4224.lcs.mit.edu' is just that, temporary -- I want my machine to know what its *real* identity is. From my perspective, when I'm installing a FreeBSD machine, the DHCP client option serves only to quick-start the installation -- the machine will eventually have a real address. It would be useful to me if sysinstall paid attention to the hostname I specified > the hostname will currently cause it to override the DHCP hostname > value even if it is specified (as it certainly is on *my* DHCP server :-) > and result in broken behavior for the aformentioned mailers. You have your mail server set to ``authenticate'' based on the HELO? That's the only thing in the SMTP protocol that the kernel's hostname setting has any impact on. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 17:57:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 88A8A157E2 for ; Thu, 27 Jan 2000 17:57:26 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA41571; Thu, 27 Jan 2000 17:57:21 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA82228; Thu, 27 Jan 2000 17:57:22 -0800 (PST) (envelope-from obrien) Date: Thu, 27 Jan 2000 17:57:21 -0800 From: "David O'Brien" To: Warner Losh Cc: current@freebsd.org Subject: Re: Comments on this patch? Message-ID: <20000127175721.A81215@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <20000127144543.C81615@dragon.nuxi.com> <200001272144.OAA48475@harmony.village.org> <20000127144543.C81615@dragon.nuxi.com> <200001272300.QAA49240@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001272300.QAA49240@harmony.village.org>; from imp@village.org on Thu, Jan 27, 2000 at 04:00:40PM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 04:00:40PM -0700, Warner Losh wrote: > So I'd say this is with 2.7.3 and the compiler in today's current. Ah. 2.95.2 is a known speed snail. The GCC developers took this to heart and 2.96 will compile much faster. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18: 3:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 72E7115401; Thu, 27 Jan 2000 18:03:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA04884; Thu, 27 Jan 2000 18:11:52 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001280211.SAA04884@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Wollman Cc: "Jordan K. Hubbard" , obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 20:57:08 EST." <200001280157.UAA21728@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 18:11:52 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > citizen" these days without a resolvable hostname that also matches > > your primary IP address or, among other things, you won't be able to > > send mail directly to anyone who practices traditional spam filtering > > techniques. > > However, there is no need to actually use the configured hostname for > this purpose. `temp-4224.lcs.mit.edu' is just that, temporary -- I > want my machine to know what its *real* identity is. > > >From my perspective, when I'm installing a FreeBSD machine, the DHCP > client option serves only to quick-start the installation -- the > machine will eventually have a real address. It would be useful to me > if sysinstall paid attention to the hostname I specified That's not correct; your DHCP configuration should reflect the hostname. Sysinstall doesn't fill in the hostname field because the crunched binary is missing the hostname(1) command. If we were to add that, it's just possible that we'd get hostnames working too. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18: 7:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9FB7215401 for ; Thu, 27 Jan 2000 18:07:08 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA41602; Thu, 27 Jan 2000 18:07:08 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA82311; Thu, 27 Jan 2000 18:07:08 -0800 (PST) (envelope-from obrien) Date: Thu, 27 Jan 2000 18:07:08 -0800 From: "David O'Brien" To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000127180708.A82262@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000127144207.A81615@dragon.nuxi.com> <46146.949017991@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <46146.949017991@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 27, 2000 at 04:06:31PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 04:06:31PM -0800, Jordan K. Hubbard wrote: > > IMHO, that is the wrong assumption. Most DHCP servers I've seen aren't > > setup to provide hostnames to the requrestor. > > Seems they're set up incorrectly then. Not at all. > You can't be a good "network citizen" these days without a resolvable > hostname that also matches your primary IP address or, among other > things, you won't be able to send mail directly to anyone who practices > traditional spam filtering techniques. I will state unequivocally that most DHCP clients use a local mail relay. And the local relay will use a "generic" hostname on the email address. Also, the DNS "name" has nothing to do with the host's name. The sites DNS admins will have both forward and reverse (A & PTR) RR's. Also I will state in large shops, they don't hardcode IPs to particular machines. Thus over time a machine has many different IPs. People would not be too happy to see their hostnames change all the time, nor to be the typical "foo-bar-dhcp-134-89" that the assigned IP will resolve to. In a Winloose network, they don't care about matching machine names with DNS hostnames. > This also isn't just pedantry because, as I noted before, specifying > the hostname will currently cause it to override the DHCP hostname > value even if it is specified (as it certainly is on *my* DHCP server :-) Yes, this behavior is ISC's ruled desire. From experience Ted Lemon and Co. knows that most shops don't handout hostnames, and when they do they are long nonsensical ones. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18: 8:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B769E15843 for ; Thu, 27 Jan 2000 18:08:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: (from jkh@localhost) by zippy.cdrom.com (8.9.3/8.9.3) id SAA86618 for current@freebsd.org; Thu, 27 Jan 2000 18:09:17 -0800 (PST) (envelope-from jkh) Date: Thu, 27 Jan 2000 18:09:17 -0800 (PST) From: "Jordan K. Hubbard" Message-Id: <200001280209.SAA86618@zippy.cdrom.com> To: current@freebsd.org Subject: -current is still broken as of 2000/01/27 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> libexec/getNAME cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/getNAME/ge tNAME.c cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o getNAME getNAME.o gzip -cn /usr/src/libexec/getNAME/getNAME.1 > getNAME.1.gz ===> libexec/getty cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/getty/main .c In file included from /usr/src/libexec/getty/main.c:71: /usr/src/libexec/getty/extern.h:61: conflicting types for `setflags' /usr/obj/usr/src/i386/usr/include/unistd.h:186: previous declaration of `setflag s' *** Error code 1 .. Guys, this is pretty bad! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18: 9:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id F267B14FA8; Thu, 27 Jan 2000 18:09:17 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA41621; Thu, 27 Jan 2000 18:09:15 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA82329; Thu, 27 Jan 2000 18:09:16 -0800 (PST) (envelope-from obrien) Date: Thu, 27 Jan 2000 18:09:16 -0800 From: "David O'Brien" To: Mike Smith Cc: "Jordan K. Hubbard" , current@freebsd.org Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000127180916.B82262@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <46146.949017991@zippy.cdrom.com> <200001280020.QAA03272@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001280020.QAA03272@mass.cdrom.com>; from msmith@freebsd.org on Thu, Jan 27, 2000 at 04:20:54PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: > > Actually, the problem here is that our dhclient doesn't pick the hostname > up the first time around. If it's set in an existing lease that is just > confirmed, it works, but if you're starting without a lease, you won't > get a hostname set (but it will be in the lease file, so if you restart > before the lease expires you're OK). Are you sure? In the case I know you experience, the server changed its behavior WRT handing out hostnames. I don't doubt that such a switch mid-stream in using DHCP would confuse things. > Personally I'd prefer to just fix the DHCP client so that it correctly > sets the hostname as obtained from the server... Nope. Poll larger shops first on their DHCP usage. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:10: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A86B315917; Thu, 27 Jan 2000 18:10:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA86643; Thu, 27 Jan 2000 18:10:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Mike Smith Cc: Garrett Wollman , obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 18:11:52 PST." <200001280211.SAA04884@mass.cdrom.com> Date: Thu, 27 Jan 2000 18:10:45 -0800 Message-ID: <86640.949025445@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That's not correct; your DHCP configuration should reflect the hostname. > > Sysinstall doesn't fill in the hostname field because the crunched binary > is missing the hostname(1) command. If we were to add that, it's just > possible that we'd get hostnames working too. Actually, that's not quite true and hasn't been for awhile now: jkh@highwing-> grep hostname /usr/src/release/*conf* /usr/src/release/boot_crunch.conf.generic:progs dhclient arp hostname - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:13:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 95E441589A; Thu, 27 Jan 2000 18:13:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA05076; Thu, 27 Jan 2000 18:22:55 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001280222.SAA05076@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: obrien@freebsd.org Cc: Mike Smith , "Jordan K. Hubbard" , current@freebsd.org Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 18:09:16 PST." <20000127180916.B82262@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 18:22:55 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: > > > > Actually, the problem here is that our dhclient doesn't pick the hostname > > up the first time around. If it's set in an existing lease that is just > > confirmed, it works, but if you're starting without a lease, you won't > > get a hostname set (but it will be in the lease file, so if you restart > > before the lease expires you're OK). > > Are you sure? In the case I know you experience, the server changed its > behavior WRT handing out hostnames. I don't doubt that such a switch > mid-stream in using DHCP would confuse things. Quite sure. I have several machines installed with the 26th snapshot that aren't setting the hostname correctly. You were present when the hostname issuing from the server problem was fixed, and the clients were still not picking them up then. > > Personally I'd prefer to just fix the DHCP client so that it correctly > > sets the hostname as obtained from the server... > > Nope. Poll larger shops first on their DHCP usage. Correct behaviour would be not to set the hostname unless: a) it is not already set or b) it was previously set by the DHCP client You could probably ignore b) and satisfy most people. At the moment, the hostname is _never_ set by the DHCP client _unless_ it finds a lease that is still valid. This is clearly a bug. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:15:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 60F5015C20; Thu, 27 Jan 2000 18:15:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA05093; Thu, 27 Jan 2000 18:24:07 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001280224.SAA05093@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jordan K. Hubbard" Cc: Mike Smith , Garrett Wollman , obrien@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 18:10:45 PST." <86640.949025445@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 18:24:07 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > That's not correct; your DHCP configuration should reflect the hostname. > > > > Sysinstall doesn't fill in the hostname field because the crunched binary > > is missing the hostname(1) command. If we were to add that, it's just > > possible that we'd get hostnames working too. > > Actually, that's not quite true and hasn't been for awhile now: > > jkh@highwing-> grep hostname /usr/src/release/*conf* > /usr/src/release/boot_crunch.conf.generic:progs dhclient arp hostname In that case I can only assume that the dhclient-script is looking for it in the wrong place. The last snap I installed was around the 25th and it still failed to pick up the hostname. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:20:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from umd5.umd.edu (umd5.umd.edu [128.8.10.5]) by hub.freebsd.org (Postfix) with ESMTP id D1F901584B; Thu, 27 Jan 2000 18:20:46 -0800 (PST) (envelope-from howardjp@wam.umd.edu) Received: from marple.umd.edu (marple.umd.edu [128.8.10.50]) by umd5.umd.edu (8.9.1/8.9.1) with ESMTP id VAA13176; Thu, 27 Jan 2000 21:20:45 -0500 (EST) Received: from localhost (howardjp@localhost) by marple.umd.edu (8.9.1/8.9.1) with SMTP id VAA00952; Thu, 27 Jan 2000 21:20:45 -0500 (EST) X-Authentication-Warning: marple.umd.edu: howardjp owned process doing -bs Date: Thu, 27 Jan 2000 21:20:45 -0500 (EST) From: James Howard X-Sender: howardjp@marple.umd.edu To: wonko@entropy.tmok.com Cc: Josef Karthauser , freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: ColdFusion 4.5 RC3 In-Reply-To: <200001272249.RAA60178@entropy.tmok.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Brian Hechinger wrote: > yes. sorry about the confusion, i forgot to mention that. > Allaire off-record said that they aren't happy with Linux > and are seeking an alternative. i seem to be pushing > them towards FreeBSD. but, keep in mind, this will be a > huge shift in development for them, so if they ever do > descide this, it still won't happen for a while. I was quite happy with Cold Fusion under NT. Significantly better than ASPs :) Anyway, I'd love to see a FreeBSD port, is there an email address where we can politely encourage them? Jamie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:22:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id 708A2158F2 for ; Thu, 27 Jan 2000 18:22:25 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.208]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FP000B6OX6ZUL@mta1.snfc21.pbi.net> for current@FreeBSD.ORG; Thu, 27 Jan 2000 18:21:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 2F66E91519; Thu, 27 Jan 2000 18:20:59 -0800 (PST) Date: Thu, 27 Jan 2000 18:20:59 -0800 (PST) From: Alex Zepeda Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: <200001272205.OAA11110@windsor.research.att.com> To: Bill Fenner Cc: rcarter@pinyon.org, current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Bill Fenner wrote: > > >Right. I've seen this when I hit Enter rapidly twice at the first > >loader prompt. Doesn't ever happen if I wait for the second > >prompt. > > That's my impression too -- I've seen it on my laptop when I do > that (sometimes), and I may have hit enter twice rapidly on this > reboot. Yup I've seen this too on my trusty Micron. I've found that hitting space, to get to the forth prompt, and then typing boot and then thwacking enter is a sure fire way to get it to boot correctly. Hitting enter twice in a row quickly occasionally screw up. Also sometimes I'll be able to catch the screwed up booter when I notice that it doesn't respond to me hitting enter (In 9 seconds... hit enter.. 8 seconds.. hit enter.. 7 seconds... hit reset). - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:24: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from iris.vsrc.uab.edu (iris.vsrc.uab.edu [138.26.156.231]) by hub.freebsd.org (Postfix) with ESMTP id 3B79E1599A for ; Thu, 27 Jan 2000 18:23:59 -0800 (PST) (envelope-from emre@iris.vsrc.uab.edu) Received: by iris.vsrc.uab.edu (Postfix, from userid 1001) id B0EFD1250B; Thu, 27 Jan 2000 20:24:54 +0000 (GMT) Date: Thu, 27 Jan 2000 20:24:54 +0000 From: Emre To: Dan Nelson Cc: freebsd-current@freebsd.org Subject: Re: .bash_history and permissions Message-ID: <20000127202454.A12343@iris.vsrc.uab.edu> References: <20000127155328.A32492@iris.vsrc.uab.edu> <20000127172415.A19202@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000127172415.A19202@dan.emsphone.com>; from dnelson@emsphone.com on Thu, Jan 27, 2000 at 05:24:16PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 05:24:16PM -0600, Dan Nelson wrote: > Delete permission comes from the directory, not the file. No amount of > chmod'ing the file will affect it. Hmm, so If I took out write permission for the directory, the user wouldn't be able to delete his .bash_history, correct? (or any file inside it for that matter) > Under FreeBSD, you can run "chflags sappnd,sunlnk .bash_history" to > make the file undeletable, append-only. Under other Unixes, the user > can simply do a "cp /dev/null ~/.bash_history && kill -9 $$" to log out > with no history file. Thanks, the chflags method worked for me... -- DSS/DH 1024/4064: 0x5E9EE10A/0x2486FEBE To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:24:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 8C551159BE for ; Thu, 27 Jan 2000 18:24:27 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 15538 invoked from network); 28 Jan 2000 02:24:15 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 28 Jan 2000 02:24:15 -0000 Date: Fri, 28 Jan 2000 13:24:11 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Peter Jeremy Cc: Warner Losh , current@FreeBSD.ORG Subject: Re: Comments on this patch? In-Reply-To: <00Jan28.103218est.115205@border.alcanet.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jan 2000, Peter Jeremy wrote: > On 2000-Jan-28 10:02:06 +1100, Warner Losh wrote: > >In message <20000127144543.C81615@dragon.nuxi.com> "David O'Brien" writes: > >: > BTW, I'm getting numbers that are 2x bigger than before :-(. I had > >: > makebuildworld down to around 1:20 at one point, but now it is 2:40. > ... > >So I'd say this is with 2.7.3 and the compiler in today's current. > >There's so much that has changed in the last 2.5 years so this is more > >like grousing rather than pointing to a problem. > > FreeBSD itself is significantly larger - at a guess, I'd say that > 4.0-CURRENT is about 50% larger than 2.x. I suspect (though I That seems about right. > haven't done any direct comparisons) that today's egcs is slower > than 2.7.3. Also, following Marcel's work, buildworld is now far gcc-2.95 is significantly slower than egcs (10%?). egcs was slightly slower than gcc-2.7.x. > more careful about ensuring that tools it wants to use are built > correctly for the environment they are going to be used in - which > means that far more of the system is built multiple times during > a buildworld. Marcel's changes actually result in many few tools being built (most of the old "tools" are too hard to build in the host environment), and less rebuilding of tools. Nevertheless, the standard makeworld has slowed down about 20-25% since last August. I attribute the slowdown to: 10%: gcc 10%: building dependencies in makeworld 2-3%: other lost optimizations in makeworld (-DNOSHARED) +epsilon: new programs and libraries -epsilon: new optimizations in buildworld (fewer tools and libraries) Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:27:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 22B6215964; Thu, 27 Jan 2000 18:26:54 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id VAA21947; Thu, 27 Jan 2000 21:26:44 -0500 (EST) (envelope-from wollman) Date: Thu, 27 Jan 2000 21:26:44 -0500 (EST) From: Garrett Wollman Message-Id: <200001280226.VAA21947@khavrinen.lcs.mit.edu> To: Mike Smith Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: <200001280211.SAA04884@mass.cdrom.com> References: <200001280157.UAA21728@khavrinen.lcs.mit.edu> <200001280211.SAA04884@mass.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > That's not correct; your DHCP configuration should reflect the hostname. No, it shouldn't. As I keep on trying to explain, the DHCP addresses are: 1) Temporary. 2) Meaningless. 3) Temporary. 4) Temporary. 5) Temporary. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:38: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 4E55714A19 for ; Thu, 27 Jan 2000 18:38:07 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 80130 invoked by uid 1001); 28 Jan 2000 02:35:33 -0000 Date: Thu, 27 Jan 2000 18:35:33 -0800 From: Jason Evans To: "Jordan K. Hubbard" Cc: current@freebsd.org Subject: Re: -current is still broken as of 2000/01/27 Message-ID: <20000127183533.O73462@sturm.canonware.com> References: <200001280209.SAA86618@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001280209.SAA86618@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Jan 27, 2000 at 06:09:17PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 06:09:17PM -0800, Jordan K. Hubbard wrote: > ===> libexec/getNAME > cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/getNAME/ge > tNAME.c > cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -o getNAME getNAME.o > gzip -cn /usr/src/libexec/getNAME/getNAME.1 > getNAME.1.gz > ===> libexec/getty > cc -O -pipe -I/usr/obj/usr/src/i386/usr/include -c /usr/src/libexec/getty/main > .c > In file included from /usr/src/libexec/getty/main.c:71: > /usr/src/libexec/getty/extern.h:61: conflicting types for `setflags' > /usr/obj/usr/src/i386/usr/include/unistd.h:186: previous declaration of `setflag > s' > *** Error code 1 > .. > > Guys, this is pretty bad! > > - Jordan From the src/include/unistd.h cvs log: ------------------------ revision 1.33 date: 2000/01/27 21:16:51; author: joe; state: Exp; lines: +3 -1 Historically file flags (schg, uschg, etc) have been converted from string to u_long and back using two functions, flags_to_string and string_to_flags, which co-existed with 'ls'. As time has progressed more and more other tools have used these private functions to manipulate the file flags. Recently I moved these functions from /usr/src/bin/ls to libutil, but after some discussion with bde it's been decided that they really ought to go in libc. There are two already existing libc functions for manipulating file modes: setmode and getmode. In keeping with these flags_to_string has been renamed getflags and string_to_flags to setflags. ------------------------ This is the same kind of breakage I caused when moving some definitions into unistd.h. I would call it bootstrapping breakage, but others who know the build system better claim it's avoidable. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:45:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 3D9EB157E7 for ; Thu, 27 Jan 2000 18:45:14 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA05541; Thu, 27 Jan 2000 18:53:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001280253.SAA05541@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 21:26:44 EST." <200001280226.VAA21947@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 18:53:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > That's not correct; your DHCP configuration should reflect the hostname. > > No, it shouldn't. As I keep on trying to explain, the DHCP addresses > are: > > 1) Temporary. > 2) Meaningless. > 3) Temporary. > 4) Temporary. > 5) Temporary. Since the hostname is simply a plain-text token for the IP address, it has to remain bound to the IP address (whether that binding is fixed or dynamic is outside the scope of this discussion). Having a hostname that doesn't map to your IP address is a misconfiguration, and not a useful one at that. The only argument for having a dysfunctional hostname of the variety you describe is vanity, which is not a valid engineering constraint. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:54:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id B3F3A15A2D for ; Thu, 27 Jan 2000 18:54:30 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id SAA41755 for ; Thu, 27 Jan 2000 18:54:28 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id SAA82671 for current@FreeBSD.ORG; Thu, 27 Jan 2000 18:54:29 -0800 (PST) (envelope-from obrien) Date: Thu, 27 Jan 2000 18:54:29 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000127185429.A82635@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <200001280157.UAA21728@khavrinen.lcs.mit.edu> <200001280211.SAA04884@mass.cdrom.com> <200001280226.VAA21947@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001280226.VAA21947@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Thu, Jan 27, 2000 at 09:26:44PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 09:26:44PM -0500, Garrett Wollman wrote: > < said: > > > That's not correct; your DHCP configuration should reflect the hostname. > > No, it shouldn't. As I keep on trying to explain, the DHCP addresses > are: ^^ usually > 1) Temporary. > 2) Meaningless. > 3) Temporary. But if one does not specify a hostname in sysinstall with the intention of having DHCP hand it out and it be used; then I do have a bug to fix. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:55:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 6D36715951 for ; Thu, 27 Jan 2000 18:55:43 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 17085 invoked from network); 28 Jan 2000 02:55:39 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 28 Jan 2000 02:55:39 -0000 Date: Fri, 28 Jan 2000 13:55:36 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Comments on this patch? In-Reply-To: <200001272144.OAA48475@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Warner Losh wrote: > I've been running this for a while. I reversed the normal order to > make it easier to do the math w/o having to shift columns and flip > things over. I plan to put timestamps on most of the "<<<" lines and remove all the ornation around the "<<" lines. Almost every large target could begin by (optionally of course) printing the time. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 18:58:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 74E6A157AD for ; Thu, 27 Jan 2000 18:58:18 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA08659; Thu, 27 Jan 2000 19:58:15 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA51268; Thu, 27 Jan 2000 19:58:25 -0700 (MST) Message-Id: <200001280258.TAA51268@harmony.village.org> To: Bruce Evans Subject: Re: Comments on this patch? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 28 Jan 2000 13:55:36 +1100." References: Date: Thu, 27 Jan 2000 19:58:24 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bruce Evans writes: : I plan to put timestamps on most of the "<<<" lines and remove all : the ornation around the "<<" lines. Almost every large target could : begin by (optionally of course) printing the time. Sounds more general than mine... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 19: 8:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 0D6B214FDD for ; Thu, 27 Jan 2000 19:08:34 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:Jqjs+2+QVBhofK/boqksOW4Bd/JkpZOn@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id MAA07602; Fri, 28 Jan 2000 12:08:21 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id MAA19744; Fri, 28 Jan 2000 12:13:59 +0900 (JST) Message-Id: <200001280313.MAA19744@zodiac.mech.utsunomiya-u.ac.jp> To: "Justin T. Gibbs" Cc: current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: [PATCH] Please test the PS/2 mouse driver patch In-reply-to: Your message of "Thu, 27 Jan 2000 14:18:47 MST." <200001272118.OAA25762@narnia.plutotech.com> References: <200001272118.OAA25762@narnia.plutotech.com> Date: Fri, 28 Jan 2000 12:13:58 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Do you have specs on the Trackpoint PS/2 mice found on Thinkpads? No. >The version on my 770X has a double click by "pushing hard on the >trackpoint" feature. It also has the ability to do the scroll >thing if you hold the middle mouse button and move the trackpoint. You mean, there features are available in W*ndoes, but not in FreeBSD? There can be two possible explanations: a) These features are implemented in the device firmware level and need to be explicitly activated by the driver software on the host computer. W*ndows driver knows it, but our psm driver doesn't. b) These features are entirely implemented by the W*ndows driver software. The TrackPoint itself is behaving just like the ordinary 2, or 3, button pointing device. The W*ndows driver is so smart, our psm driver isn't :-) Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 19:16:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 5456414C82 for ; Thu, 27 Jan 2000 19:16:08 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id TAA41877 for ; Thu, 27 Jan 2000 19:15:34 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id TAA82834 for current@freebsd.org; Thu, 27 Jan 2000 19:15:35 -0800 (PST) (envelope-from obrien) Date: Thu, 27 Jan 2000 19:15:35 -0800 From: "David O'Brien" To: current@freebsd.org Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000127191535.B82635@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <20000127180916.B82262@dragon.nuxi.com> <200001280222.SAA05076@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001280222.SAA05076@mass.cdrom.com>; from msmith@freebsd.org on Thu, Jan 27, 2000 at 06:22:55PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 06:22:55PM -0800, Mike Smith wrote: > Correct behaviour would be not to set the hostname unless: > a) it is not already set > or > b) it was previously set by the DHCP client > > You could probably ignore b) and satisfy most people. At the moment, the > hostname is _never_ set by the DHCP client _unless_ it finds a lease that > is still valid. This is clearly a bug. Agreed. I will happily accept a patch anybody that got to this before I manage do. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 19:42:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from alpha.netvision.net.il (alpha.netvision.net.il [194.90.1.13]) by hub.freebsd.org (Postfix) with ESMTP id 7A60C15144; Thu, 27 Jan 2000 19:42:43 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS3-p12.rlz.netvision.net.il [62.0.169.14]) by alpha.netvision.net.il (8.9.3/8.8.6) with ESMTP id FAA22250; Fri, 28 Jan 2000 05:42:30 +0200 (IST) Message-ID: <38911084.49CF773D@freenet.co.uk> Date: Fri, 28 Jan 2000 03:44:04 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Cc: gandalf@vilnya.demon.co.uk, dfr@freebsd.org, tanimura@freebsd.org Subject: The Commit That Broke PCM Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG PCM has been broken for me since December 1999. I would very much appreciate if someone could help me fix it before the code freeze (cg, dfr and tanimura CC'd). I have an unknown MSS-compatible non-PnP ISA sound card, which identifies itself as a CS4231. Unknown, because it's inside a laptop. Before you ask, it has always been identified as a CS4231, and always worked very well. The last kernel that I have which still works is dated 6 Dec 1999, and I'm playing mp3's with it right now. Here's its verbose boot message: mss_detect - chip revision 0x0a mss_detect() - Detected CS4231 pcm0: at port 0x530-0x53f,0x310-0x311 irq 5 drq 1 flags 0xa210 on isa0 pcm: setmap 30000, ff00; 0xc8421000 -> 30000 pcm: setmap 40000, ff00; 0xc8431000 -> 40000 isa_probe_children: probing PnP devices Kernels built after 26 Dec 1999 print the following: mss_detect - chip revision 0x0a mss_detect() - Detected CS4231 pcm0: at port 0x530-0x537,0x538-0x539 irq 5 drq 1 flags 0xa110 on isa0 pcm: setmap 30000, ff00; 0xc840e000 -> 30000 pcm: setmap 40000, ff00; 0xc841e000 -> 40000 isa_probe_children: probing PnP devices mss_intr: irq, but not from mss and screw up the card - there is no sound and the driver gets stuck in "pcmwr". Something was committed between the 6th and 26th of December that broke pcm. The question is: which commit broke it? What has changed? 1) I/O port allocation and flags in dmesg: 0x310-0x311 vs 0x538-0x539, and 0xa210 vs 0xa110 2) The "mss_intr: irq, but not from mss" line Why? My config file hasn't changed a bit, neither has my hardware or BIOS setup. I don't have "controller pnp" in my config file, so it probably has nothing to do with PnP. The list of commits that might have broken it is appended below for your convenience. Please let me know if I have missed something obvious. Thank you for your attention Alex ----------------------------- cg 1999/12/11 18:18:59 PST Modified files: sys/dev/sound/pcm datatypes.h dsp.c sound.c sound.h Log: move channel-swapping support to the hardware driver since it knows the card state best Revision Changes Path 1.6 +3 -1 src/sys/dev/sound/pcm/datatypes.h 1.11 +2 -11 src/sys/dev/sound/pcm/dsp.c 1.11 +8 -1 src/sys/dev/sound/pcm/sound.c 1.7 +2 -3 src/sys/dev/sound/pcm/sound.h cg 1999/12/12 19:29:10 PST Modified files: sys/dev/sound/pcm channel.c channel.h datatypes.h dsp.c Log: more dma underrun fixes, using a per-channel 2nd buffer Submitted by: tanimura Revision Changes Path 1.10 +247 -87 src/sys/dev/sound/pcm/channel.c 1.4 +10 -1 src/sys/dev/sound/pcm/channel.h 1.7 +2 -1 src/sys/dev/sound/pcm/datatypes.h 1.12 +2 -2 src/sys/dev/sound/pcm/dsp.c cg 1999/12/18 14:24:50 PST Modified files: sys/dev/sound/pcm channel.c Log: fix the buffer repetition on ^c problem Revision Changes Path 1.11 +10 -13 src/sys/dev/sound/pcm/channel.c cg 1999/12/19 07:27:26 PST Modified files: sys/dev/sound/pcm sound.c Log: move make_dev operations for audio channels to pcm_addchan(). in theory, with modifications to MAKEDEV this will allow use of multiple output streams on cards supporting it, eg trident 4dwave. Revision Changes Path 1.12 +12 -11 src/sys/dev/sound/pcm/sound.c cg 1999/12/19 14:32:56 PST Modified files: sys/dev/sound/pcm channel.c Log: stop playing if we underrun; if there is more data to come, the next write will restart Revision Changes Path 1.12 +3 -1 src/sys/dev/sound/pcm/channel.c cg 1999/12/19 16:56:53 PST Modified files: sys/dev/sound/pcm sound.c Log: allow (broken) apps to use mixer ioctls on dsp devices. eg: vmware Submitted by: "Vladimir N. Silyaev" Revision Changes Path 1.13 +5 -2 src/sys/dev/sound/pcm/sound.c cg 1999/12/20 06:57:46 PST Modified files: sys/dev/sound/isa sb.c sys/dev/sound/pcm channel.c Log: minor cosmetics Revision Changes Path 1.42 +1 -2 src/sys/dev/sound/isa/sb.c 1.13 +6 -7 src/sys/dev/sound/pcm/channel.c cg 1999/12/21 00:43:28 PST Modified files: sys/dev/sound/isa mss.c sys/dev/sound/pcm channel.c Log: minor cleanup Parts Submitted by: Ville-Pertti Keinonen Revision Changes Path 1.38 +20 -23 src/sys/dev/sound/isa/mss.c 1.14 +2 -13 src/sys/dev/sound/pcm/channel.c peter 1999/12/21 06:09:22 PST Modified files: sys/dev/sound/isa mss.c Log: Collapse a bunch of unused MD_CS42nn tags into a single one. This saves going to a lot of trouble to identify it and set the tag and then not use it. Convert the pnp id matching to the preferred table based system. @@@0001 (CMI8330 ldn 0) is a mss, not a SB. Revision Changes Path 1.39 +37 -90 src/sys/dev/sound/isa/mss.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 20:17:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 301B315A24 for ; Thu, 27 Jan 2000 20:17:31 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id WAA36535; Thu, 27 Jan 2000 22:17:23 -0600 (CST) (envelope-from dan) Date: Thu, 27 Jan 2000 22:17:23 -0600 From: Dan Nelson To: Emre Cc: freebsd-current@freebsd.org Subject: Re: .bash_history and permissions Message-ID: <20000127221723.A36507@dan.emsphone.com> References: <20000127155328.A32492@iris.vsrc.uab.edu> <20000127172415.A19202@dan.emsphone.com> <20000127202454.A12343@iris.vsrc.uab.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000127202454.A12343@iris.vsrc.uab.edu>; from "Emre" on Thu Jan 27 20:24:54 GMT 2000 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Jan 27), Emre said: > On Thu, Jan 27, 2000 at 05:24:16PM -0600, Dan Nelson wrote: > > Delete permission comes from the directory, not the file. No amount of > > chmod'ing the file will affect it. > > Hmm, so If I took out write permission for the directory, the user > wouldn't be able to delete his .bash_history, correct? (or any file > inside it for that matter) Right. But remember that no amount of filesystem attribute changes (even the chflags stuff) will help if the user switches shells, or simply turns off the history feature in bash. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 20:22:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id B3901157AD for ; Thu, 27 Jan 2000 20:22:45 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id XAA23653; Thu, 27 Jan 2000 23:22:43 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id XAA46942; Thu, 27 Jan 2000 23:22:12 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 27 Jan 2000 23:22:12 -0500 (EST) To: Nick Hibma Cc: FreeBSD CURRENT Mailing List Subject: Re: pcm - stutters In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14481.5856.865621.444727@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma writes: > > The output of my ESS 1869 stutters whenever there is no new data fed to > it. For example pressing Ctrl-Z, or heavy disk usage (normally making > mpg123 jump). The stuttering is repetition of one short fragment of > about a quarter of a second, indefinitely > > Anything I can try with this machine current as of jan.24 02:00 GMT? I don't know much about sound, but it seems like pcm doesn't deal very gracefully with underflow. I have a very wimpy machine (133MHz P5 laptop): CPU: Pentium/P54C (133.64-MHz 586-class CPU) <...> sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1 on isa0 pcm0: on sbc0 I cannot play anything with amp -- the song starts to stutter after a second or two of play. I can use mgp123 which (I think) uses a more efficient decoder. Using mpg123, I see the same symptoms as you report. RealPlayerG2 seems to do better than amp. Especially if I tell it to "disable custom sampling rates." But still not as good as mpg123. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 20:30:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id 1167F158F4 for ; Thu, 27 Jan 2000 20:30:08 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.117.12]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FP1003V72XG7U@mta1.snfc21.pbi.net> for current@FreeBSD.ORG; Thu, 27 Jan 2000 20:24:54 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 3B30191519; Thu, 27 Jan 2000 20:24:53 -0800 (PST) Date: Thu, 27 Jan 2000 20:24:53 -0800 (PST) From: Alex Zepeda Subject: Re: Speaking of ATAisms... In-reply-to: <200001260904.KAA12586@freebsd.dk> To: Soren Schmidt Cc: current Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Jan 2000, Soren Schmidt wrote: > > zippy:~#dd if=/dev/afd0c bs=1k count=16 of=afd0c.output > > dd: /dev/afd0c: Input/output error > > zippy:~#Jan 26 00:38:32 zippy /kernel: afd0: error reading primary > > partition table reading fsbn 0 > > > > Hmm. I know this disk works with Windows 98SE. > > Well, if it has problems with the partitions you should use /dev/afd0 > and /dev/wfd0. Well the first read (even after the little blinky light went out) after inserting a disk with afd0 gives me an i/o error. The second read works. Swapped zip disks. Same with afd0c, except when it "works" zero records are transferred. It doesn't do much predictably, except for not work. I know I got an error reading the primary partition table the first time I tried to read (forget whether it was afd0 or afd0c). /me scratches his head - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21: 3:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from sr14.nsw-remote.bigpond.net.au (sr14.nsw-remote.bigpond.net.au [24.192.3.29]) by hub.freebsd.org (Postfix) with ESMTP id 5595C14E39 for ; Thu, 27 Jan 2000 21:03:27 -0800 (PST) (envelope-from areilly@nsw.bigpond.net.au) Received: from areilly.bpc-users.org (CPE-24-192-49-170.nsw.bigpond.net.au [24.192.49.170]) by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id QAA17586 for ; Fri, 28 Jan 2000 16:03:23 +1100 (EDT) Received: (qmail 20389 invoked by uid 1000); 28 Jan 2000 05:03:21 -0000 From: "Andrew Reilly" Date: Fri, 28 Jan 2000 16:03:21 +1100 To: Mike Smith Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000128160321.A19649@gurney.reilly.home> References: <200001280226.VAA21947@khavrinen.lcs.mit.edu> <200001280253.SAA05541@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001280253.SAA05541@mass.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 06:53:51PM -0800, Mike Smith wrote: > Since the hostname is simply a plain-text token for the IP address, it > has to remain bound to the IP address (whether that binding is fixed or > dynamic is outside the scope of this discussion). Having a hostname that > doesn't map to your IP address is a misconfiguration, and not a useful > one at that. My system has two ethernet cards, and two IP addresses. One of these is assigned by DHCP and the other is fixed, on my local network. I prefer for my hostname to relate to the local address. Just another data point. -- Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21: 9: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 13B79156E0 for ; Thu, 27 Jan 2000 21:09:03 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA09135; Thu, 27 Jan 2000 22:08:58 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA52301; Thu, 27 Jan 2000 22:09:08 -0700 (MST) Message-Id: <200001280509.WAA52301@harmony.village.org> To: Alex Zepeda Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: Bill Fenner , rcarter@pinyon.org, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 27 Jan 2000 18:20:59 PST." References: Date: Thu, 27 Jan 2000 22:09:08 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Alex Zepeda writes: : in a row quickly occasionally screw up. Also sometimes I'll be able to : catch the screwed up booter when I notice that it doesn't respond to me : hitting enter (In 9 seconds... hit enter.. 8 seconds.. hit enter.. 7 : seconds... hit reset). I've also seen this on my laptop from time to time. Half the time when this happens, the scan codes are all messed up once I get to multi-user. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:10:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 967F6159DD; Thu, 27 Jan 2000 21:10:49 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA09147; Thu, 27 Jan 2000 22:10:47 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA52324; Thu, 27 Jan 2000 22:10:57 -0700 (MST) Message-Id: <200001280510.WAA52324@harmony.village.org> To: Garrett Wollman Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: Mike Smith , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 27 Jan 2000 21:26:44 EST." <200001280226.VAA21947@khavrinen.lcs.mit.edu> References: <200001280226.VAA21947@khavrinen.lcs.mit.edu> <200001280157.UAA21728@khavrinen.lcs.mit.edu> <200001280211.SAA04884@mass.cdrom.com> Date: Thu, 27 Jan 2000 22:10:57 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001280226.VAA21947@khavrinen.lcs.mit.edu> Garrett Wollman writes: : < said: : : > That's not correct; your DHCP configuration should reflect the hostname. : : No, it shouldn't. As I keep on trying to explain, the DHCP addresses : are: : : 1) Temporary. : 2) Meaningless. : 3) Temporary. : 4) Temporary. : 5) Temporary. That reminds me. sysinstall *SHOULD*NOT* hard code the IP address that it gets from dhcp into rc.conf. I've seen this in 3.2, but haven't tried since then to reproduce this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:14:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 514B1159A3; Thu, 27 Jan 2000 21:14:50 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id PAA29034; Fri, 28 Jan 2000 15:14:35 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpdb29004; Fri Jan 28 15:14:30 2000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id PAA27093; Fri, 28 Jan 2000 15:14:11 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id PAA13767; Fri, 28 Jan 2000 15:14:10 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id PAA20367; Fri, 28 Jan 2000 15:14:09 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <200001280514.PAA20367@nymph.detir.qld.gov.au> To: Brian Fundakowski Feldman Cc: freebsd-current@freebsd.org, syssgm@detir.qld.gov.au Subject: That fix for the ^T crash Date: Fri, 28 Jan 2000 15:14:09 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Brian! I'm concerned that your fix won't make it before the code freeze. Is there a problem with it? I admit I haven't actually tested it. :-( My excuse is that I assumed you had. Or should I just do a quick test on your patch (+ bde fixes) and commit it myself? Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:18:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 1B8B514FA6; Thu, 27 Jan 2000 21:18:44 -0800 (PST) (envelope-from trouble@netquick.net) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=netquick.net) by bekool.com with esmtp (Exim 3.03 #1) id 12E4O5-000GLT-00; Fri, 28 Jan 2000 00:56:05 -0500 Message-ID: <38912908.F5EED626@netquick.net> Date: Fri, 28 Jan 2000 00:28:40 -0500 From: TrouBle Reply-To: trouble@netquick.net X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Josef Karthauser Cc: wonko@entropy.tmok.com, freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: ColdFusion 4.5 RC3 References: <20000127223826.E97579@florence.pavilion.net> <200001272249.RAA60178@entropy.tmok.com> <20000127225537.F97579@florence.pavilion.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ummm just tried to install it, and i get ./start Error: performing semget() on ColdFusion Registry semaphore:File exists Abort trap - core dumped FreeBSD angelsguardian.netquick.net 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Jan 22 23:22:53 EST 2000 root@angelsguardian.netquick.net:/usr/src/sys/compile/GUARDIAN i386 with linux_base installed any ideas.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:24:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id CC03814CB2; Thu, 27 Jan 2000 21:24:27 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA01566; Thu, 27 Jan 2000 21:33:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001280533.VAA01566@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Warner Losh Cc: Garrett Wollman , Mike Smith , current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-reply-to: Your message of "Thu, 27 Jan 2000 22:10:57 MST." <200001280510.WAA52324@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 Jan 2000 21:33:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > That reminds me. sysinstall *SHOULD*NOT* hard code the IP address > that it gets from dhcp into rc.conf. I've seen this in 3.2, but > haven't tried since then to reproduce this. It doesn't do that anymore; it was a nasty hack to work around not having been able to sell BPF in the kernel in time for 3.2. Now that it's in GENERIC, we can run the DHCP client after installation. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:25:59 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 0565F14DEF; Thu, 27 Jan 2000 21:25:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id EC4891CD684; Thu, 27 Jan 2000 21:25:57 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 27 Jan 2000 21:25:57 -0800 (PST) From: Kris Kennaway To: Alexandr Listopad Cc: Chris Piazza , freebsd-current@FreeBSD.ORG Subject: Re: help! need kernel! In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, Alexandr Listopad wrote: > there no tools/ dir in /usr/src - why? Because you didn't download it? > doc-all > src-base > src-bin > src-contrib > src-etc > src-gnu > src-include > src-lib > src-libexec > src-release > src-sbin > src-share > src-sys src-tools > src-usrbin > src-usrsbin Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:27:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 9105815A64; Thu, 27 Jan 2000 21:26:54 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA09210; Thu, 27 Jan 2000 22:26:53 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA52493; Thu, 27 Jan 2000 22:27:03 -0700 (MST) Message-Id: <200001280527.WAA52493@harmony.village.org> To: Mike Smith Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: Garrett Wollman , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 27 Jan 2000 21:33:04 PST." <200001280533.VAA01566@mass.cdrom.com> References: <200001280533.VAA01566@mass.cdrom.com> Date: Thu, 27 Jan 2000 22:27:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001280533.VAA01566@mass.cdrom.com> Mike Smith writes: : > That reminds me. sysinstall *SHOULD*NOT* hard code the IP address : > that it gets from dhcp into rc.conf. I've seen this in 3.2, but : > haven't tried since then to reproduce this. : : It doesn't do that anymore; it was a nasty hack to work around not having : been able to sell BPF in the kernel in time for 3.2. Now that it's in : GENERIC, we can run the DHCP client after installation. Glad to hear it. One less thing to double check before the release... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:27:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from pop3.ids.net (pop3.ids.net [155.212.1.107]) by hub.freebsd.org (Postfix) with ESMTP id A112715ACD for ; Thu, 27 Jan 2000 21:27:09 -0800 (PST) (envelope-from CGiordano@ids.net) Received: from ids.net (dyn007g.egr-ri.ids.net [155.212.223.7]) by pop3.ids.net (8.9.3/8.9.3) with ESMTP id AAA11150 for ; Fri, 28 Jan 2000 00:27:00 -0500 (EST) Message-ID: <38912806.39F0758A@ids.net> Date: Fri, 28 Jan 2000 00:24:22 -0500 From: "Christopher M. Giordano" Reply-To: CGiordano@ids.net X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Subject: Re: newpcm (or newpnp?) Content-Type: multipart/mixed; boundary="------------3EC9B6D9F2D5458199EEAFB7" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------3EC9B6D9F2D5458199EEAFB7 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cameron Grant wrote: > would everyone who currently has an issue outstanding with newpcm please > report it to me in the next few days directly, please, so i can get an idea > of what needs work before release. i need as much detail as possible. Well, since you asked... Since rebuilding -CURRENT with newpcm and newpnp about a month ago, my soundcard, a Soundblaster AWE64, ISA PnP, will only play the first second or less of a sound file. Audio apps often claim "unable to open /dev/dsp". I notice that my modem, a Diamond SupraExpress 56i Sp, is now attaching to irq 5, and the soundcard attaches to irq 9. Previous to newpnp, I forced the modem (sio2) to irq 15 and the soundcard to irq 5 via pnp commands in my /boot/kernel.conf. I did this because I had found by experimentation that this was the only combination of the supposedly available PnP configurations which enabled both devices to work. Now that pnp attaches sio2 to irq 5, the soundcard refuses to work on irq9, even though irq9 is available and supposedly valid for that card. So I'd like to be able to get it to work on irq9 (preferably), but failing that, at least try to return to my original PnP configuration to see if that works. I don't know how to force this since the removal of pnp(4), though, and have searched the mailing list archives to no avail. I have tried configuring a kernel to force irq 5 on the soundcard with no success. Any advice would be greatly appreciated. My kernel config and other info is attached. Chris Giordano cgiordano@ids.net -------------------------------------------------------- $ /opt/home/cgiordan > uname -a FreeBSD boston 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Jan 17 02:15:15 EST 2000 root@boston:/opt/src/src/sys/compile/BOSTON i386 $ /opt/home/cgiordan > cat /dev/sndstat FreeBSD Audio Driver (newpcm) Jan 17 2000 02:13:33 Installed devices: pcm0: at io 0x220 irq 9 drq 0:5 (1p/1r channels duplex) --------------3EC9B6D9F2D5458199EEAFB7 Content-Type: text/plain; charset=us-ascii; name="BOSTON" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="BOSTON" # # BOSTON -- Generic machine with WD/AHx/NCR/BTx family disks # -- added PnP and sound support # -- added ATAPI LS-120/Zip support # -- switched over to Luigi's new sound driver # -- added SCSI/CAM devices for 3.X # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.107 1998/02/16 23:57:03 msmith Exp $ machine i386 cpu I686_CPU ident BOSTON maxusers 64 ## config kernel root on da0 dumps on da0 ## options HZ=100 #use 10 ms clock tick options INET #InterNETworking # # Implement system calls compatible with 4.3BSD and older versions of # FreeBSD. You probably do NOT want to remove this as much current code # still relies on the 4.3 emulation. # options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options USER_LDT #allow user level control of i386 LDT options MD5 options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor #options MROUTING # Multicast routing #options IPFIREWALL #firewall #options IPFIREWALL_VERBOSE #print information about # dropped packets #options IPFIREWALL_VERBOSE_LIMIT=100 #limit verbosity #options IPDIVERT #divert sockets options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options NTFS #NT File System options PROCFS #Process filesystem options CD9660 #ISO 9660 Filesystem options EXT2FS options FFS_ROOT #FFS usable as root device [keep this!] options NFS_ROOT #NFS usable as root device options CD9660_ROOT #CD-ROM usable as root device options SOFTUPDATES #in Alpha test! options NSWAPDEV=20 # Don't enable both of these in a real config. #options MATH_EMULATE #Support for x87 emulation options GPL_MATH_EMULATE #Support for x87 emulation via #new math emulator options NBUF=512 options NMBCLUSTERS=8192 #workaround for mbuf bug # This provides support for System V shared memory. # options SYSVSHM options SYSVSEM options SYSVMSG # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing options DDB #kernel debugging options DDB_UNATTENDED #don't drop into DDB for a panic # XXX Supposedly, I should be using this since 4.X-CURRENT is so new. ## options INVARIANTS ## options INVARIANT_SUPPORT # Options for POSIX priority extensions; these are # required for Linux threads in emulation mode. options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L device isa0 #device eisa0 device pci0 device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # ATA and ATAPI devices device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 #device ata2 #device atadisk0 # ATA disk drives #device atapicd0 # ATAPI CDROM drives device atapifd0 # ATAPI floppy drives (e.g., LS-120) #device atapist0 # ATAPI tape drives options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices #device wdc0 at isa? port IO_WD1 irq 14 #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 # #device wdc1 at isa? port IO_WD2 irq 15 #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 # #device wfd0 #IDE Floppy (e.g. LS-120) #device wcd0 #IDE CD-ROM # SCSI Controllers # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. #device ncr0 #device amd0 #device ahb0 device ahc0 #device bt0 at isa? port ? irq ? #device uha0 at isa? port IO_UHA0 bio irq ? drq 5 #device aha0 at isa? port ? irq ? drq 5 #device aic0 at isa? port 0x340 bio irq 11 #device nca0 at isa? port 0x1f88 bio irq 10 #device nca1 at isa? port 0x350 bio irq 5 #device sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 device scbus0 #base SCSI code device da0 #SCSI direct access devices (aka disks) device sa0 #SCSI tapes device cd0 #SCSI CD-ROMs device pass0 #CAM passthrough driver options SCSI_DELAY=10000 #Be pessimistic about Joe SCSI device #SCSI delay is in milliseconds options AHC_ALLOW_MEMIO ## options AHC_TAGENABLE ## options AHC_SCBPAGING_ENABLE # syscons is the default console driver, resembling an SCO console device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? # splash screen/screen saver pseudo-device splash # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at nexus? port IO_NPX irq 13 # keep this! # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x20 # Advanced Power Management # PCCARD (PCMCIA) support #device card0 #device pcic0 at card? #device pcic1 at card? # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 #device sio2 at isa? disable port IO_COM3 irq 15 #device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 device ppbus0 # Parallel port bus (required) device lpt0 # Printer device plip0 # TCP/IP over parallel device ppi0 # Parallel port interface device #device vpo0 # Requires scbus and da0 #device mse0 at isa? port 0x23c irq 5 # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device de0 #device fxp0 #device tx0 #device vx0 # #device ed0 at isa? port 0x280 irq 10 iomem 0xd8000 #device ie0 at isa? port 0x300 irq 10 iomem 0xd0000 #device ep0 at isa? port 0x300 irq 10 vector epintr #device ex0 at isa? port? irq? #device fe0 at isa? port 0x300 irq ? #device le0 at isa? port 0x300 irq 5 iomem 0xd0000 #device lnc0 at isa? port 0x280 irq 10 drq 0 #device ze0 at isa? port 0x300 irq 10 iomem 0xd8000 #device zp0 at isa? port 0x300 irq 10 iomem 0xd8000 pseudo-device ether pseudo-device loop pseudo-device bpf 4 #Berkeley packet filter pseudo-device disc #Discard device pseudo-device snp 3 #Snoop device - to look at pty/vty/etc.. pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker #pseudo-device log #Kernel syslog interface (/dev/klog) pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpf) # # Audio drivers: `snd', `sb', `pas', `gus', `pca' # # snd: Voxware sound support code # sb: SoundBlaster PCM - SoundBlaster, SB Pro, SB16, ProAudioSpectrum # sbxvi: SoundBlaster 16 # sbmidi: SoundBlaster 16 MIDI interface #device snd0 #device sb0 at isa? port 0x220 irq 5 drq 1 #device sbxvi0 at isa? drq 5 #device sbmidi0 at isa? port 0x330 #device pas0 at isa? port 0x388 irq 10 drq 6 #device awe0 at isa? port 0x620 # The newpcm driver (use INSTEAD of snd0 and all VOXWARE drivers!). # Note that motherboard sound devices may require options PNPBIOS. # # For non-pnp sound cards with no bridge drivers only: #device pcm0 at isa? port ? irq 10 drq 1 flags 0x0 # # For pnp sound cards: device pcm0 # The bridge drivers for sound cards. Do not forget pcm as well. # # sbc: Creative SoundBlaster ISA PnP/non-PnP # Supports ESS and Avance ISA chips as well. # gusc: Gravis UltraSound ISA PnP/non-PnP # csa: Crystal Semiconductor CS461x/428x PCI # For PnP cards: device sbc0 #device gusc0 #device csa0 # For non-PnP cards: #device sbc0 at isa? port 0x220 irq 5 drq 1 flags 0x15 #device gusc0 at isa? port 0x220 irq 5 drq 1 flags 0x13 --------------3EC9B6D9F2D5458199EEAFB7 Content-Type: text/plain; charset=us-ascii; name="dmesg.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dmesg.txt" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Mon Jan 17 02:15:15 EST 2000 root@boston:/opt/src/src/sys/compile/BOSTON Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 298730563 Hz CPU: Pentium II/Xeon/Celeron (298.73-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x650 Stepping = 0 Features=0x183fbff real memory = 67108864 (65536K bytes) avail memory = 61980672 (60528K bytes) Preloaded elf kernel "kernel" at 0xc0365000. Preloaded elf module "splash_bmp.ko" at 0xc036509c. Preloaded splash_image_data "/boot/daemon_news.bmp" at 0xc0365140. Preloaded elf module "linux.ko" at 0xc0365194. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: port 0xdc00-0xdcff mem 0xfeaf0000-0xfeafffff,0xfe000000-0xfe3fffff,0xfe400000-0xfe7fffff,0xdc800000-0xdcffffff,0xdd000000-0xdd7fffff irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 0 chip1: port 0xfcb0-0xfcbf at device 7.3 on pci0 ahc0: port 0xec00-0xecff mem 0xfebff000-0xfebfffff irq 10 at device 14.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode sio2: at port 0x3e8-0x3ef irq 5 on isa0 sio2: type 16550A sbc0: at port 0x220-0x22f,0x300-0x301,0x388-0x38b irq 9 drq 0,5 on isa0 sbc0: setting card to irq 9, drq 0, 5 pcm0: on sbc0 unknown0: at port 0x200-0x207 on isa0 unknown1: at port 0x620-0x623 on isa0 Waiting 10 seconds for SCSI devices to settle afd0: rewriteable drive at ata0 as master afd0: 120MB (246528 sectors), 963 cyls, 8 heads, 32 S/T, 512 B/S afd0: 533KB/s, PIO0 afd0: Medium: Unknown media (0x0) Mounting root from ufs:/dev/da0s3a cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4148MB (8496884 512 byte sectors: 255H 63S/T 528C) --------------3EC9B6D9F2D5458199EEAFB7 Content-Type: text/plain; charset=us-ascii; name="pnpinfo.txt" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="pnpinfo.txt" Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID SUP2084 (0x8420b04e), Serial Number 0x00003bf6 PnP Version 1.0, Vendor Version 0 Device Description: SupraExpress 56i Sp Logical Device ID: SUP2084 0x8420b04e #0 Device supports I/O Range Check Compatible Device ID: SUP2080 (8020b04e) TAG Start DF I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 4 - only one type (true/edge) TAG Start DF I/O Range 0x2f8 .. 0x2f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 - only one type (true/edge) TAG Start DF I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 4 - only one type (true/edge) TAG Start DF I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 - only one type (true/edge) TAG Start DF I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 5 - only one type (true/edge) TAG Start DF I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 5 - only one type (true/edge) TAG Start DF I/O Range 0x3e8 .. 0x3e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 7 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x2e8 .. 0x2e8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 7 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x3f8 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 7 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x2f8 .. 0x2f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 7 10 11 12 15 - only one type (true/edge) TAG Start DF I/O Range 0x200 .. 0x3f8, alignment 0x8, len 0x8 [16-bit addr] IRQ: 3 4 5 7 10 11 12 15 - only one type (true/edge) TAG End DF End Tag Successfully got 38 resources, 1 logical fdevs -- card select # 0x0001 CSN SUP2084 (0x8420b04e), Serial Number 0x00003bf6 Logical device #0 IO: 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 0x03e8 IRQ 5 0 DMA 4 0 IO range check 0x00 activate 0x01 Card assigned CSN #2 Vendor ID CTL009e (0x9e008c0e), Serial Number 0x0116a6d6 PnP Version 1.0, Vendor Version 32 Device Description: Creative SB AWE64 Gold Logical Device ID: CTL0044 0x44008c0e #0 Device Description: Audio TAG Start DF Good Configuration IRQ: 5 - only one type (true/edge) DMA: channel(s) 1 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x220, alignment 0x1, len 0x10 [16-bit addr] I/O Range 0x330 .. 0x330, alignment 0x1, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x388, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x30, len 0x2 [16-bit addr] TAG Start DF Acceptable Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] TAG Start DF Sub-optimal Configuration IRQ: 5 7 9 10 - only one type (true/edge) DMA: channel(s) 0 1 3 8-bit, not a bus master, count by byte, , Compatibility mode DMA: channel(s) 5 6 7 16-bit, not a bus master, , count by word, Compatibility mode I/O Range 0x220 .. 0x280, alignment 0x20, len 0x10 [16-bit addr] I/O Range 0x300 .. 0x330, alignment 0x10, len 0x2 [16-bit addr] I/O Range 0x388 .. 0x394, alignment 0x4, len 0x4 [16-bit addr] TAG End DF Logical Device ID: CTL7002 0x02708c0e #1 Compatible Device ID: PNPb02f (2fb0d041) Device Description: Game TAG Start DF Good Configuration I/O Range 0x200 .. 0x200, alignment 0x1, len 0x8 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x200 .. 0x208, alignment 0x8, len 0x8 [16-bit addr] TAG End DF Logical Device ID: CTL0023 0x23008c0e #2 Device Description: WaveTable TAG Start DF Good Configuration I/O Range 0x620 .. 0x620, alignment 0x1, len 0x4 [16-bit addr] TAG Start DF Acceptable Configuration I/O Range 0x620 .. 0x680, alignment 0x20, len 0x4 [16-bit addr] TAG End DF End Tag Successfully got 67 resources, 3 logical fdevs -- card select # 0x0002 CSN CTL009e (0x9e008c0e), Serial Number 0x0116a6d6 Logical device #0 IO: 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 0x0220 IRQ 9 0 DMA 0 5 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #2 IO: 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 --------------3EC9B6D9F2D5458199EEAFB7-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:27:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id BA8E715C4B for ; Thu, 27 Jan 2000 21:27:46 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA80024; Thu, 27 Jan 2000 21:27:16 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001280527.VAA80024@gndrsh.dnsmgr.net> Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: <200001272143.QAA20638@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jan 27, 2000 04:43:46 pm" To: wollman@khavrinen.lcs.mit.edu (Garrett Wollman) Date: Thu, 27 Jan 2000 21:27:16 -0800 (PST) Cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), fenner@research.att.com (Bill Fenner), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > >> 3. On the first reboot after installing, the keyboard was in a funny > >> state. > > > Urk, can't reproduce it. I need a reproducible sequence of operations > > before we'll have any hope of tackling this one. > > >> Control-alt-del definitely didn't work, so I had to power off and > >> reboot. This hasn't repeated itself. > > > Same here. > > I have on a number of occasions had my laptop boot with a > non-functional keyboard. Sometimes the keyboard is just locked; other > times it generates garbage. Never managed to isolate the > circumstances in which this happened (but it didn't happen with a > kernel from last September or there-abouts). Haven't had it happen on > a desktop or server yet. I have seen this on numerious occasion, but have never tracked it down to any one specific thing. All on desktop and servers, but thats only because we don't do laptops. I have not seen it in quite some time (about a month), so I am thinking it has probably been unknowingly fixed someplace. I'll keep an eye out for it. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:32:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id BFDDA15BA2; Thu, 27 Jan 2000 21:32:15 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id AAA04635; Fri, 28 Jan 2000 00:32:05 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001280532.AAA04635@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001280510.WAA52324@harmony.village.org> Date: Fri, 28 Jan 2000 00:32:04 -0500 (EST) From: John Baldwin To: Warner Losh Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: current@FreeBSD.org, Mike Smith , Garrett Wollman Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Jan-00 Warner Losh wrote: > In message <200001280226.VAA21947@khavrinen.lcs.mit.edu> Garrett Wollman writes: >: < said: >: >: > That's not correct; your DHCP configuration should reflect the hostname. >: >: No, it shouldn't. As I keep on trying to explain, the DHCP addresses >: are: >: >: 1) Temporary. >: 2) Meaningless. >: 3) Temporary. >: 4) Temporary. >: 5) Temporary. > > That reminds me. sysinstall *SHOULD*NOT* hard code the IP address > that it gets from dhcp into rc.conf. I've seen this in 3.2, but > haven't tried since then to reproduce this. > > Warner It doesn't do this on 3.3 or 3.4. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:32:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 4DAA815B93; Thu, 27 Jan 2000 21:32:12 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id AAA04649; Fri, 28 Jan 2000 00:32:10 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001280532.AAA04649@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001280222.SAA05076@mass.cdrom.com> Date: Fri, 28 Jan 2000 00:32:10 -0500 (EST) From: John Baldwin To: Mike Smith Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Cc: current@FreeBSD.org, "Jordan K. Hubbard" , obrien@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Jan-00 Mike Smith wrote: >> On Thu, Jan 27, 2000 at 04:20:54PM -0800, Mike Smith wrote: >> > >> > Actually, the problem here is that our dhclient doesn't pick the hostname >> > up the first time around. If it's set in an existing lease that is just >> > confirmed, it works, but if you're starting without a lease, you won't >> > get a hostname set (but it will be in the lease file, so if you restart >> > before the lease expires you're OK). >> >> Are you sure? In the case I know you experience, the server changed its >> behavior WRT handing out hostnames. I don't doubt that such a switch >> mid-stream in using DHCP would confuse things. > > Quite sure. I have several machines installed with the 26th snapshot > that aren't setting the hostname correctly. You were present when the > hostname issuing from the server problem was fixed, and the clients were > still not picking them up then. > >> > Personally I'd prefer to just fix the DHCP client so that it correctly >> > sets the hostname as obtained from the server... >> >> Nope. Poll larger shops first on their DHCP usage. > > Correct behaviour would be not to set the hostname unless: > > a) it is not already set > or > b) it was previously set by the DHCP client > > You could probably ignore b) and satisfy most people. At the moment, the > hostname is _never_ set by the DHCP client _unless_ it finds a lease that > is still valid. This is clearly a bug. Uh, no. It is set ok on the initial bootup. The lab of 30 or so FreeBSD machines I run at school use DHCP to get their hostnames and the current dhclient-script works perfectly: [0:28:21] (ttyp2) jobaldwi@raspberry:~ > grep hostname /etc/rc.conf hostname="" [0:28:27] (ttyp2) jobaldwi@raspberry:~ > grep host-name /var/db/dhclient.leases option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; option host-name "raspberry.cslab.vt.edu"; -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:38:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from green.dyndns.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 759381590E; Thu, 27 Jan 2000 21:38:44 -0800 (PST) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by green.dyndns.org (8.9.3/8.9.3) with ESMTP id AAA35535; Fri, 28 Jan 2000 00:38:41 -0500 (EST) (envelope-from green@FreeBSD.org) X-Authentication-Warning: green.dyndns.org: green owned process doing -bs Date: Fri, 28 Jan 2000 00:38:39 -0500 (EST) From: Brian Fundakowski Feldman X-Sender: green@green.dyndns.org To: Stephen McKay Cc: freebsd-current@FreeBSD.org Subject: Re: That fix for the ^T crash In-Reply-To: <200001280514.PAA20367@nymph.detir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jan 2000, Stephen McKay wrote: > Hi, Brian! > > I'm concerned that your fix won't make it before the code freeze. Is > there a problem with it? I admit I haven't actually tested it. :-( > My excuse is that I assumed you had. > > Or should I just do a quick test on your patch (+ bde fixes) and commit > it myself? The best thing to do is get on BDE's case to have it fixed very soon :) He knows what he's doing! > Stephen. -- Brian Fundakowski Feldman \ FreeBSD: The Power to Serve! / green@FreeBSD.org `------------------------------' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:41:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 2DC0D158B2; Thu, 27 Jan 2000 21:41:33 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA80096; Thu, 27 Jan 2000 21:41:29 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001280541.VAA80096@gndrsh.dnsmgr.net> Subject: Re: (FWD) Re: cvs commit: src/etc/periodic/daily 200.backup-pass In-Reply-To: <200001272236.RAA54168@server.baldwin.cx> from John Baldwin at "Jan 27, 2000 05:36:47 pm" To: jhb@FreeBSD.ORG (John Baldwin) Date: Thu, 27 Jan 2000 21:41:29 -0800 (PST) Cc: obrien@FreeBSD.ORG (David O'Brien), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 27-Jan-00 David O'Brien wrote: > > I would appreciate it if those that want things changed would please try > > Sheldon's `sed' expression below and report back how it worked for you. > > That will expose passwords of users whose entries are commented out, My awk script does not have that problem. If the line has 10 colons in it field 2 will be munged. It don't care if you give it straight password, diff -u or diff -c or even diff. It may have problems with diff -y. ... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 21:45:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 88E9114FA6; Thu, 27 Jan 2000 21:45:23 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id VAA80113; Thu, 27 Jan 2000 21:45:13 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001280545.VAA80113@gndrsh.dnsmgr.net> Subject: Re: Comments on this patch? In-Reply-To: <200001272300.QAA49240@harmony.village.org> from Warner Losh at "Jan 27, 2000 04:00:40 pm" To: imp@village.org (Warner Losh) Date: Thu, 27 Jan 2000 21:45:12 -0800 (PST) Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <20000127144543.C81615@dragon.nuxi.com> "David O'Brien" writes: > : > BTW, I'm getting numbers that are 2x bigger than before :-(. I had > : > makebuildworld down to around 1:20 at one point, but now it is 2:40. > : > : Which compilers for both times? > > What ever was on -current as of 2.5 years ago. This is comparing the > make buildworld of 3 years ago with the make buildworld of today. > This was in the 8/5/97 timeframe. I got the buildworld time down to > 1:20 on my machine with async mount options and two spindles. Now > with the faster spindle and an even faster spindle, my buildworld > times are 2:40. There may have been some things i turned off in the > make.conf that I have on now. NOTCL was included before, for > example. My machine was 128M in 97 and is 196M now. > > So I'd say this is with 2.7.3 and the compiler in today's current. > There's so much that has changed in the last 2.5 years so this is more > like grousing rather than pointing to a problem. Actually makeworld times jumped significantly with Marcels revamped make world target. For now I can live with the penality, but it should be looked at and carefully fixed^H^H^H^H^Hoptimized. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Jan 27 23:12:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from dinolt1.bing.org (adsl-63-199-30-243.dsl.snfc21.pacbell.net [63.199.30.243]) by hub.freebsd.org (Postfix) with ESMTP id 25A7815AD1 for ; Thu, 27 Jan 2000 23:12:43 -0800 (PST) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net (localhost [127.0.0.1]) by dinolt1.bing.org (8.9.3/8.9.3) with ESMTP id XAA00647; Thu, 27 Jan 2000 23:13:20 -0800 (PST) (envelope-from gdinolt@pacbell.net) Message-ID: <38914190.636BC099@pacbell.net> Date: Thu, 27 Jan 2000 23:13:20 -0800 From: "George W. Dinolt" X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.org Cc: CGiordano@ids.net Subject: Re: newpcm (or newpnp?) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Giordano wrote: > Previous to newpnp, I forced the modem (sio2) to irq 15 and the soundcard to > irq 5 via pnp commands in my /boot/kernel.conf. I did this because I had > found by experimentation that this was the only combination of the supposedly > available PnP configurations which enabled both devices to work. I can report similar problems with my US Robotics internal 56K Fax/Modem and my SoundBlaster 16 isa card. On Freebsd 3.4 I "hard wire" the cards using kernel.conf file. On -Current I found that the only way I can get the cards to work is to configure my IWILL XA100P motherboard so that irq 3 and 5 are set up for "legacy" cards and are not automagically assigned. (I disable the 2nd serial port as well so that irq 3 is available.) When I do this reconfiguration of the motherboard, the modem and sound card work together with few problems. I can play sound and do a compilation without problems. I do have 192MB of memory add a 450Mhz processor so there is plenty of spare "horsepower" for essentially a "single user" system. I do occasionally get a flutter on startup and can reliably see a cutoff of sound at the end of reading a wave or midi file. But for most things it seems to work fine. The "say" program from the rsynth port provides a good demonstration of the "cutoff" phenomena. George Dinolt (gdinolt@pacbell.net) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 0: 5:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 50A2614D93; Fri, 28 Jan 2000 00:05:09 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA83782; Fri, 28 Jan 2000 09:04:39 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001280804.JAA83782@freebsd.dk> Subject: Re: Errors compiling kernel... In-Reply-To: <20000127194217.H32759@shadow.blackdawn.com> from Will Andrews at "Jan 27, 2000 07:42:17 pm" To: andrews@technologist.com (Will Andrews) Date: Fri, 28 Jan 2000 09:04:39 +0100 (CET) Cc: dmmiller@cvzoom.net (Donn Miller), current@FreeBSD.ORG, sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Will Andrews wrote: > On Thu, Jan 27, 2000 at 07:31:50PM -0500, Donn Miller wrote: > > I recently cvsup'd the sources (around Thu Jan 27 19:30:48 EST 2000), and > > I'm getting these errors compiling the kernel: > > > > cc -c -mpentium -O3 -pipe -Wall -Wredundant-decls -Wnested-externs > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > > -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL > > -include opt_global.h -elf -mpreferred-stack-boundary=2 ../../dev/ata/atapi-all.c > > ../../dev/ata/atapi-all.c: In function `atapi_attach': > > ../../dev/ata/atapi-all.c:96: syntax error before `}' > > *** Error code 1 > > Soren Schmidt (sos) made some recent commits to the ATA driver. Perhaps > these problems are the result. Yup, braino on my part, fixed now. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 0: 5:35 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 456D915C6D; Fri, 28 Jan 2000 00:05:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D3991CD423 for ; Fri, 28 Jan 2000 00:05:21 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 28 Jan 2000 00:05:21 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: This is getting ridiculous.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG /home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_int/libcc_int.a(choose-temp.o): In function `choose_temp_base': choose-temp.c(.text+0x218): warning: mktemp() possibly used unsafely; consider using mkstemp() /home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o): In function `_gettemp': mktemp.c(.text+0x3f0): undefined reference to `_open' mktemp.c(.text+0x3f4): undefined reference to `_open' *** Error code 1 1 error This is from a freshly checked-out tree on beast, with no local mods outside of secure/. I've verified twice it's up-to-date with CVS.. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 0: 7:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8B4DF156C5 for ; Fri, 28 Jan 2000 00:07:31 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id JAA84323; Fri, 28 Jan 2000 09:06:59 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001280806.JAA84323@freebsd.dk> Subject: Re: Speaking of ATAisms... In-Reply-To: from Alex Zepeda at "Jan 27, 2000 08:24:53 pm" To: jazepeda@pacbell.net (Alex Zepeda) Date: Fri, 28 Jan 2000 09:06:59 +0100 (CET) Cc: current@FreeBSD.ORG (current) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Alex Zepeda wrote: OK, I got my junkbox back into commission today, I just need to get it update into -current, then I'll take a stab at it... -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 0:15:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id C636115BA3 for ; Fri, 28 Jan 2000 00:14:36 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 81236 invoked by uid 1001); 28 Jan 2000 08:11:56 -0000 Date: Fri, 28 Jan 2000 00:11:55 -0800 From: Jason Evans To: Kris Kennaway Cc: current@freebsd.org Subject: Re: This is getting ridiculous.. Message-ID: <20000128001155.Q73462@sturm.canonware.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Fri, Jan 28, 2000 at 12:05:21AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 28, 2000 at 12:05:21AM -0800, Kris Kennaway wrote: > /home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_int/libcc_int.a(choose-temp.o): > In function `choose_temp_base': > choose-temp.c(.text+0x218): warning: mktemp() possibly used > unsafely; consider using mkstemp() > /home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o): In > function `_gettemp': > mktemp.c(.text+0x3f0): undefined reference to `_open' > mktemp.c(.text+0x3f4): undefined reference to `_open' > *** Error code 1 > 1 error > > This is from a freshly checked-out tree on beast, with no local mods > outside of secure/. I've verified twice it's up-to-date with CVS.. I'm still trying to test this patch before committing. Jason Index: SYS.h =================================================================== RCS file: /home/ncvs/src/lib/libc/alpha/SYS.h,v retrieving revision 1.9 diff -u -r1.9 SYS.h --- SYS.h 2000/01/27 23:06:02 1.9 +++ SYS.h 2000/01/28 08:15:20 @@ -104,7 +104,7 @@ #define PSYSCALL(name) \ PLEAF(name,0); /* XXX # of args? */ \ - WEAK_ALIAS(__CONCAT(_thread_sys_,name), name); \ + WEAK_ALIAS(__CONCAT(_,name), name); \ CALLSYS_ERROR(name) #define PRSYSCALL(name) \ @@ -115,7 +115,7 @@ #define PPSEUDO(label,name) \ PLEAF(label,0); /* XXX # of args? */ \ - WEAK_ALIAS(__CONCAT(_thread_sys_,name), name); \ + WEAK_ALIAS(__CONCAT(_,name), name); \ CALLSYS_ERROR(name); \ RET; \ PEND(label) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 0:20:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from es-i2.fernuni-hagen.de (ES-i2.fernuni-hagen.de [132.176.7.81]) by hub.freebsd.org (Postfix) with ESMTP id 9BB49157C1 for ; Fri, 28 Jan 2000 00:20:29 -0800 (PST) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Received: from fernuni-hagen.de (jfh00.fernuni-hagen.de [132.176.7.6]) by es-i2.fernuni-hagen.de (8.9.3/8.9.3) with ESMTP id JAA06052; Fri, 28 Jan 2000 09:19:48 +0100 (CET) (envelope-from fritz.heinrichmeyer@fernuni-hagen.de) Message-ID: <38915126.789227C@fernuni-hagen.de> Date: Fri, 28 Jan 2000 09:19:51 +0100 From: "F. Heinrichmeyer" Organization: FernUni in Hagen X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12 i386) X-Accept-Language: German/Germany, de-DE, en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: rsh broken? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG with yesterdays kernel or rshd, something has changed. When using rsh from a friendly linux-mandrake box i get: rsh jfh00 ls poll: protocol failure in circuit setup from a friendly freebsd box i get: select: protocol failure in circuit setup -- Fritz Heinrichmeyer mailto:fritz.heinrichmeyer@fernuni-hagen.de FernUniversitaet Hagen, LG ES, 58084 Hagen (Germany) tel:+49 2331/987-1166 fax:987-355 http://www-es.fernuni-hagen.de/~jfh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 0:50:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id BC93215960 for ; Fri, 28 Jan 2000 00:50:29 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12E73h-000N7X-00; Fri, 28 Jan 2000 10:47:13 +0200 From: Sheldon Hearn To: Jason Evans Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: -current is still broken as of 2000/01/27 In-reply-to: Your message of "Thu, 27 Jan 2000 18:35:33 PST." <20000127183533.O73462@sturm.canonware.com> Date: Fri, 28 Jan 2000 10:47:13 +0200 Message-ID: <88878.949049233@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000 18:35:33 PST, Jason Evans wrote: > This is the same kind of breakage I caused when moving some definitions > into unistd.h. I would call it bootstrapping breakage, but others who know > the build system better claim it's avoidable. I think it _is_ avoidable. One way to avoid it is to try to make world and report the brekage to -committers, asking for help. This works best when you do it _before_ committing the change you're testing. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 0:50:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 8AEA215ABA for ; Fri, 28 Jan 2000 00:50:35 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id RAA01683; Fri, 28 Jan 2000 17:47:49 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id RAA15518; Fri, 28 Jan 2000 17:47:47 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id RAA00657; Fri, 28 Jan 2000 17:47:44 +0900 (JST) To: fritz.heinrichmeyer@fernuni-hagen.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: rsh broken? In-Reply-To: <38915126.789227C@fernuni-hagen.de> References: <38915126.789227C@fernuni-hagen.de> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000128174826K.shin@nd.net.fujitsu.co.jp> Date: Fri, 28 Jan 2000 17:48:26 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 21 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > with yesterdays kernel or rshd, something has changed. > When using rsh from a friendly linux-mandrake box i get: > > rsh jfh00 ls > poll: protocol failure in circuit setup > > from a friendly freebsd box i get: > select: protocol failure in circuit setup As the change to src/lib/libc/net/getaddrinfo.c 1.4 -> 1.5, there emerged a bug in realhostname_sa() in lib/libutil/realhostname.c. If your lib/libutil/realhostname.c's version is lower than 1.5, then please update it and try again. Else, I need to investigate it more.... Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 1:12:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id A6C1E14C08; Fri, 28 Jan 2000 01:12:18 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id BAA43215; Fri, 28 Jan 2000 01:08:52 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id BAA90809; Fri, 28 Jan 2000 01:08:54 -0800 (PST) (envelope-from obrien) Date: Fri, 28 Jan 2000 01:08:54 -0800 From: "David O'Brien" To: Kris Kennaway Cc: current@freebsd.org Subject: Re: This is getting ridiculous.. Message-ID: <20000128010854.A90791@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kris@hub.freebsd.org on Fri, Jan 28, 2000 at 12:05:21AM -0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > /home/kris/tmp/world/obj/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/alpha/.amd_mnt/freefall/host/c/users/kris/tmp/world/src/gnu/usr.bin/cc/cpp/../cc_fbsd/libcc_fbsd.a(mktemp.o): In > function `_gettemp': > mktemp.c(.text+0x3f0): undefined reference to `_open' > mktemp.c(.text+0x3f4): undefined reference to `_open' > *** Error code 1 > 1 error Yes, I expected this error after seeing the libc chagnes. Unfortunetly, the setflags() barfage make it so I couldn't buildworld to test a change to the compiler before committing it. :-( -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 2:15:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id E5B9E14DDD for ; Fri, 28 Jan 2000 02:15:33 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:B14dtphAPBT80KXnvRCSq3Fk1zhBANE3@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id SAA10794 for ; Fri, 28 Jan 2000 18:26:19 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id SAA04893; Fri, 28 Jan 2000 18:31:57 +0900 (JST) Message-Id: <200001280931.SAA04893@zodiac.mech.utsunomiya-u.ac.jp> To: current@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Keyboard problem (was: Re: Problems installing FreeBSD 4.0 20000125-CURRENT) Date: Fri, 28 Jan 2000 18:31:56 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, guys. This is another patch for the atkbd driver. I expect this one is better than my previous one. Remove the previous patch and try this one instead. Stress the keyboard (like hitting the Return key twice when booting the system), and see if it works. Thank you. Kazu >> I have on a number of occasions had my laptop boot with a >> non-functional keyboard. Sometimes the keyboard is just locked; other >> times it generates garbage. Never managed to isolate the >> circumstances in which this happened (but it didn't happen with a >> kernel from last September or there-abouts). Haven't had it happen on >> a desktop or server yet. > >I have seen this on numerious occasion, but have never tracked it down >to any one specific thing. All on desktop and servers, but thats >only because we don't do laptops. > >I have not seen it in quite some time (about a month), so I am thinking >it has probably been unknowingly fixed someplace. I'll keep an eye >out for it. > >-- >Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net Index: atkbd.c =================================================================== RCS file: /src/CVS/src/sys/dev/kbd/atkbd.c,v retrieving revision 1.22 diff -u -r1.22 atkbd.c --- atkbd.c 2000/01/20 13:32:53 1.22 +++ atkbd.c 2000/01/28 02:11:50 @@ -1084,8 +1097,11 @@ return ENXIO; } + /* temporarily block data transmission from the keyboard */ + write_controller_command(kbdc, KBDC_DISABLE_KBD_PORT); + /* flush any noise in the buffer */ - empty_both_buffers(kbdc, 10); + empty_both_buffers(kbdc, 100); /* save the current keyboard controller command byte */ m = kbdc_get_device_mask(kbdc) & ~KBD_KBD_CONTROL_BITS; @@ -1133,8 +1148,11 @@ return EIO; } + /* temporarily block data transmission from the keyboard */ + write_controller_command(kbdc, KBDC_DISABLE_KBD_PORT); + /* save the current controller command byte */ empty_both_buffers(kbdc, 200); c = get_controller_command_byte(kbdc); if (c == -1) { /* CONTROLLER ERROR */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 2:47:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.alpha.net.au (mail2.alpha.net.au [203.41.44.8]) by hub.freebsd.org (Postfix) with ESMTP id 934991585E; Fri, 28 Jan 2000 02:47:48 -0800 (PST) (envelope-from dannyh@idx.com.au) Received: from psych ([203.41.44.190]) by mail.alpha.net.au (8.9.3/8.9.3) with SMTP id VAA27237; Fri, 28 Jan 2000 21:24:29 +1100 Message-Id: <3.0.32.20000128212424.00755540@idx.com.au> X-Sender: dannyh@idx.com.au X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 28 Jan 2000 21:24:29 +1100 To: James Howard , wonko@entropy.tmok.com From: Danny Subject: Re: ColdFusion 4.5 RC3 Cc: Josef Karthauser , freebsd-questions@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I totally aggree. As soon as CF is ported to FreeBSD the bettter At 21:20 27/01/00 -0500, James Howard wrote: >On Thu, 27 Jan 2000, Brian Hechinger wrote: > >> yes. sorry about the confusion, i forgot to mention that. >> Allaire off-record said that they aren't happy with Linux >> and are seeking an alternative. i seem to be pushing >> them towards FreeBSD. but, keep in mind, this will be a >> huge shift in development for them, so if they ever do >> descide this, it still won't happen for a while. > >I was quite happy with Cold Fusion under NT. Significantly better than >ASPs :) Anyway, I'd love to see a FreeBSD port, is there an email address >where we can politely encourage them? > >Jamie > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 4:20:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 6F15B15645 for ; Fri, 28 Jan 2000 04:20:24 -0800 (PST) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id WAA10264; Fri, 28 Jan 2000 22:19:17 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) via SMTP by ren.detir.qld.gov.au, id smtpd010252; Fri Jan 28 22:19:13 2000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA03159; Fri, 28 Jan 2000 22:18:58 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id WAA00467; Fri, 28 Jan 2000 22:18:59 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost [127.0.0.1]) by nymph.detir.qld.gov.au (8.9.3/8.8.7) with ESMTP id WAA31121; Fri, 28 Jan 2000 22:18:56 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <200001281218.WAA31121@nymph.detir.qld.gov.au> To: "Rodney W. Grimes" Cc: wollman@khavrinen.lcs.mit.edu (Garrett Wollman), jkh@zippy.cdrom.com (Jordan K. Hubbard), fenner@research.att.com (Bill Fenner), current@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT References: <200001272143.QAA20638@khavrinen.lcs.mit.edu> <200001280527.VAA80024@gndrsh.dnsmgr.net> In-Reply-To: <200001280527.VAA80024@gndrsh.dnsmgr.net> from "Rodney W. Grimes" at "Thu, 27 Jan 2000 21:27:16 -0800" Date: Fri, 28 Jan 2000 22:18:56 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 27th January 2000, "Rodney W. Grimes" wrote: >> < said: >> >> >> 3. On the first reboot after installing, the keyboard was in a funny >> >> state. >I have seen this on numerious occasion, but have never tracked it down >to any one specific thing. All on desktop and servers, but thats >only because we don't do laptops. > >I have not seen it in quite some time (about a month), so I am thinking >it has probably been unknowingly fixed someplace. I'll keep an eye >out for it. I had this problem on several machines back around version 3.2. I assumed it was a problem between X11 and the keyboard driver. I added a 2 second delay before starting xdm and had no problems after that. I've not seen the problem without X11 being involved. I admit I just forgot about it after I got my workstation going. :-( Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 5:12:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 5834E15A25 for ; Fri, 28 Jan 2000 05:12:28 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id WAA13001; Fri, 28 Jan 2000 22:12:25 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id WAA04393; Fri, 28 Jan 2000 22:12:24 +0900 (JST) Received: from localhost (dhcp7194.nd.net.fujitsu.co.jp [10.18.7.194]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id WAA09311; Fri, 28 Jan 2000 22:12:23 +0900 (JST) To: fritz.heinrichmeyer@fernuni-hagen.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: rsh broken? In-Reply-To: <20000128174826K.shin@nd.net.fujitsu.co.jp> References: <38915126.789227C@fernuni-hagen.de> <20000128174826K.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000128221305C.shin@nd.net.fujitsu.co.jp> Date: Fri, 28 Jan 2000 22:13:05 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 35 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > When using rsh from a friendly linux-mandrake box i get: > > > > rsh jfh00 ls > > poll: protocol failure in circuit setup > > > > from a friendly freebsd box i get: > > select: protocol failure in circuit setup Woops bug was in rshd from the beginning. My test had a leakage. It only happens on AF_INET socket, and I usually use AF_INET6 socket on my environment so I didon't noticed it. Please try following patch untill I actually commmit it. Thanks for reporting it, Yoshinobu Inoue Index: rshd.c =================================================================== RCS file: /home/ncvs/src/libexec/rshd/rshd.c,v retrieving revision 1.28 diff -u -r1.28 rshd.c --- rshd.c 2000/01/25 14:52:03 1.28 +++ rshd.c 2000/01/28 12:51:13 @@ -320,7 +320,7 @@ exit(1); } fromp->su_port = htons(port); - if (connect(s, (struct sockaddr *)fromp, sizeof (*fromp)) < 0) { + if (connect(s, (struct sockaddr *)fromp, fromp->su_len) < 0) { syslog(LOG_INFO, "connect second port %d: %m", port); exit(1); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 5:43:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 4C3BA14C20 for ; Fri, 28 Jan 2000 05:43:35 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id OAA05088; Fri, 28 Jan 2000 14:42:14 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Leif Neland Cc: freebsd-current@FreeBSD.ORG Subject: Re: NFS /usr/src and /usr/obj? In-reply-to: Your message of "Thu, 27 Jan 2000 19:34:41 +0100." Date: Fri, 28 Jan 2000 14:42:14 +0100 Message-ID: <5086.949066934@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Leif Neland writes: > > >On Wed, 26 Jan 2000, Poul-Henning Kamp wrote: > >> In message , mestery@visi.com writes: >> >I'm wondering how one can do a buildworld on a machine, and then NFS >> >mount /usr/src and /usr/obj on a client machine and do an installworld >> >of the freshly built sources? I've been looking in the archives without >> >much success, and haven't figured it out by reading the makefiles yet. >> >Can anyone shed some light on this? >> >> I've done it in the past, but not recently. >> >> Consider the alternative of mounting the destination on the compilehost >> and make install DESTDIR=/mnt >> > >A: What's the advantage? That your server mounts the clients, not the other way around (security etc) >B: What do I mount? The root of the destination? All relevant filesystems of the destination, ie: /, /var, /usr -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 7:33:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id ED14F15D01 for ; Fri, 28 Jan 2000 07:33:23 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12E8wt-000Oiq-00; Fri, 28 Jan 2000 12:48:19 +0200 From: Sheldon Hearn To: Yoshinobu Inoue Cc: culverk@wam.umd.edu, freebsd-current@FreeBSD.ORG Subject: Re: ipsec errors In-reply-to: Your message of "Thu, 27 Jan 2000 13:46:47 +0900." <20000127134647Y.shin@nd.net.fujitsu.co.jp> Date: Fri, 28 Jan 2000 12:48:18 +0200 Message-ID: <95028.949056498@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000 13:46:47 +0900, Yoshinobu Inoue wrote: > I just added debug flag check instead of changing syslog > level. > Could you please try the following patch to > usr.sbin/inetd/inetd.c ? I would expect the messages to be sent to stderr in debug mode. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 7:56:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 1D2A915B67; Fri, 28 Jan 2000 07:56:23 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA24642; Fri, 28 Jan 2000 10:56:18 -0500 (EST) (envelope-from wollman) Date: Fri, 28 Jan 2000 10:56:18 -0500 (EST) From: Garrett Wollman Message-Id: <200001281556.KAA24642@khavrinen.lcs.mit.edu> To: Mike Smith Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT In-Reply-To: <200001280253.SAA05541@mass.cdrom.com> References: <200001280226.VAA21947@khavrinen.lcs.mit.edu> <200001280253.SAA05541@mass.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Since the hostname is simply a plain-text token for the IP address Wrong. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 8:16:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id F191514BF1 for ; Fri, 28 Jan 2000 08:16:06 -0800 (PST) (envelope-from ab@cage.tse-online.de) Received: (qmail 8157 invoked by uid 1000); 28 Jan 2000 16:16:18 -0000 Date: Fri, 28 Jan 2000 17:16:18 +0100 From: Andreas Braukmann To: current@freebsd.org Subject: very silent, but heavy filesystem-crash Message-ID: <20000128171618.C1305@cage.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I reported a former heavy filesystem crash recently; have a look at: http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=846852+849687+/usr/local/www/db/text/2000/freebsd-current/20000123.freebsd-current I got it again. Meanwhile my system got updated to FreeBSD abc.xyz.de 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Jan 22 11:17:16 CET 2000 The system is complete soft-updates free. This time I had no jailed processes running; the machine was idle most of the time during the last few days and was rebooted (cleanly), yesterday. The (now totally hosed) file-system was mounted thru the following fstab-entry: /dev/da1s1g /scratch ufs rw 2 2 Today I incidentally noticed that the directory /scratch was empty all of the sudden. I should have found various sub-directories, especially since I built the world on this disk a few days ago. Nonetheless 'df' showed the filesystem as 45% filled. I was able to unmount and mount the filesystem without(!!) an error. There were definately no related messages in the logs or on the console. Starting an 'fsck' results in: cage:[/] # fsck /scratch ** /dev/da1s1g ** Last Mounted on /scratch ** Phase 1 - Check Blocks and Sizes PARTIALLY TRUNCATED INODE I=16 SALVAGE? [yn] ^C ***** FILE SYSTEM MARKED DIRTY ***** I interrupted the fsck-run as soon as I decided that it might be advisable to leave it in its hosed state just for the case that there is some illuminated filesystem-hacker who would like to take a peek. (I would allow ssh-access to the box ...) Bye, Andreas -- Andreas Braukmann - private site - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 8:22:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 08FE814E19 for ; Fri, 28 Jan 2000 08:22:52 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id IAA81548; Fri, 28 Jan 2000 08:22:33 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001281622.IAA81548@gndrsh.dnsmgr.net> Subject: Re: very silent, but heavy filesystem-crash In-Reply-To: <20000128171618.C1305@cage.tse-online.de> from Andreas Braukmann at "Jan 28, 2000 05:16:18 pm" To: braukmann@tse-online.de (Andreas Braukmann) Date: Fri, 28 Jan 2000 08:22:32 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > > Starting an 'fsck' results in: > > cage:[/] # fsck /scratch > ** /dev/da1s1g > ** Last Mounted on /scratch > ** Phase 1 - Check Blocks and Sizes > PARTIALLY TRUNCATED INODE I=16 > SALVAGE? [yn] ^C > ***** FILE SYSTEM MARKED DIRTY ***** Next step is run the ``save'' fsck: fsck -n /scratch >/someplacewithspace 2>&1 Then take a look at the logfile and see just how many more errors it would have found had you let it procede... > I interrupted the fsck-run as soon as I decided that it might be > advisable to leave it in its hosed state just for the case that > there is some illuminated filesystem-hacker who would like to > take a peek. (I would allow ssh-access to the box ...) $1.00/MB for me to recover it.... if you need it. I don't do it for fun. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 8:33:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 7F07114D20 for ; Fri, 28 Jan 2000 08:33:17 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id JAA11607 for ; Fri, 28 Jan 2000 09:33:16 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA62420 for ; Fri, 28 Jan 2000 09:33:32 -0700 (MST) Message-Id: <200001281633.JAA62420@harmony.village.org> To: current@freebsd.org Subject: Makefile.inc1 change Date: Fri, 28 Jan 2000 09:33:32 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following has survived a make buildworld at least once. It optimizes buildworld a little by not building fortran as part of the build tools. This looks like a safe change to make, since we have no fortran in the tree that needs to get built. It doesn't disable building of fortran later in the build, just from building it potentially twice. Comments? Warner Index: Makefile.inc1 =================================================================== RCS file: /home/imp/FreeBSD/CVS/src/Makefile.inc1,v retrieving revision 1.133 diff -u -r1.133 Makefile.inc1 --- Makefile.inc1 2000/01/24 20:11:53 1.133 +++ Makefile.inc1 2000/01/28 09:21:39 @@ -503,10 +503,6 @@ _share= share/syscons/scrnmaps .endif -.if !defined(NO_FORTRAN) -_fortran= gnu/usr.bin/cc/f771 -.endif - .if exists(${.CURDIR}/kerberosIV) && exists(${.CURDIR}/crypto) && \ !defined(NOCRYPT) && defined(MAKE_KERBEROS4) _libroken4= kerberosIV/lib/libroken @@ -518,7 +514,7 @@ .endif build-tools: -.for _tool in bin/sh ${_games} gnu/usr.bin/cc/cc_tools ${_fortran} \ +.for _tool in bin/sh ${_games} gnu/usr.bin/cc/cc_tools \ ${_libroken4} ${_libroken5} lib/libncurses ${_share} cd ${.CURDIR}/${_tool}; ${MAKE} build-tools .endfor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 9: 9:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from dead-end.net (dead-end.net [216.15.131.2]) by hub.freebsd.org (Postfix) with ESMTP id 7AA8E15B7A for ; Fri, 28 Jan 2000 09:09:05 -0800 (PST) (envelope-from rock@dead-end.net) Received: from mailto.dead-end.net (dead-end.net [216.15.131.2]) by dead-end.net (8.9.3/DEAD-END/1999102300-Deliver) with ESMTP id SAA44840 for ; Fri, 28 Jan 2000 18:08:45 +0100 (CET) (envelope-from rock@dead-end.net) Received: from server.rock.net (p3E9C361A.dip.t-dialin.net [62.156.54.26]) by mailto.dead-end.net (8.9.3/DEAD-END/2000011500-Customer) with ESMTP id SAA44836 for ; Fri, 28 Jan 2000 18:08:44 +0100 (CET) (envelope-from rock@dead-end.net) Received: from dead-end.net (laptop [172.23.7.128]) by server.rock.net (8.9.3+Sun/8.9.3) with ESMTP id SAA25131 for ; Fri, 28 Jan 2000 18:08:55 +0100 (MET) Message-ID: <3891BF08.35C20143@dead-end.net> Date: Fri, 28 Jan 2000 17:08:40 +0100 From: "D. Rock" X-Mailer: Mozilla 4.7 [de] (Win98; U) X-Accept-Language: de, en MIME-Version: 1.0 To: current@freebsd.org Subject: ata: panic with new sysctl variable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, just noticed the new sysctl variable for ata. I just wanted to use the new way for disabling DMA on my disk (has some strange problems, even under windows). Previously I just commented out the ata_dmainit() lines in ata_disk.c, now I wanted to set it with sysctl: sysctl -w hw.atamodes="pio,dma,dma,dma" but this paniced my machine. I later discovered that there is no sanity check during setting the new modes: The machine in question didn't have a secondary IDE controller, but the variables were set without a range check. My solution was simple. Just use sysctl -w hw.atamodes="pio,dma" but I think, the ata driver should range check the settings. Daniel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 9:33:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 8C63014D36 for ; Fri, 28 Jan 2000 09:33:43 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id SAA19957; Fri, 28 Jan 2000 18:33:29 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001281733.SAA19957@freebsd.dk> Subject: Re: ata: panic with new sysctl variable In-Reply-To: <3891BF08.35C20143@dead-end.net> from "D. Rock" at "Jan 28, 2000 05:08:40 pm" To: rock@dead-end.net (D. Rock) Date: Fri, 28 Jan 2000 18:33:29 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems D. Rock wrote: > Hi, > > just noticed the new sysctl variable for ata. I just wanted to > use the new way for disabling DMA on my disk (has some strange > problems, even under windows). > > Previously I just commented out the ata_dmainit() lines in > ata_disk.c, now I wanted to set it with sysctl: > > sysctl -w hw.atamodes="pio,dma,dma,dma" > > but this paniced my machine. > > I later discovered that there is no sanity check during setting > the new modes: The machine in question didn't have a secondary > IDE controller, but the variables were set without a range check. > > My solution was simple. Just use > sysctl -w hw.atamodes="pio,dma" > > but I think, the ata driver should range check the settings. It does but not for the first two devices as the are kindof magic in some sense. I'll commit the fix asap.. -Sĝren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 9:44:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (castles525.castles.com [208.214.165.89]) by hub.freebsd.org (Postfix) with ESMTP id 13EC214FAB for ; Fri, 28 Jan 2000 09:44:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA02212; Fri, 28 Jan 2000 09:52:17 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001281752.JAA02212@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Kazutaka YOKOTA Cc: current@freebsd.org Subject: Re: Keyboard problem (was: Re: Problems installing FreeBSD 4.0 20000125-CURRENT) In-reply-to: Your message of "Fri, 28 Jan 2000 18:31:56 +0900." <200001280931.SAA04893@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Jan 2000 09:52:16 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok, guys. > > This is another patch for the atkbd driver. I expect this one is > better than my previous one. Remove the previous patch and try this > one instead. Stress the keyboard (like hitting the Return key twice > when booting the system), and see if it works. Just in case you hadn't picked it up yet; at least some of the systems that see the keyboard problems see them _before_ the kernel is loaded. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 9:50:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 273E7156DD for ; Fri, 28 Jan 2000 09:50:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA11072; Fri, 28 Jan 2000 09:50:44 -0800 (PST) (envelope-from dillon) Date: Fri, 28 Jan 2000 09:50:44 -0800 (PST) From: Matthew Dillon Message-Id: <200001281750.JAA11072@apollo.backplane.com> To: Andreas Braukmann Cc: current@FreeBSD.ORG Subject: Re: very silent, but heavy filesystem-crash References: <20000128171618.C1305@cage.tse-online.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi there, : : I reported a former heavy filesystem crash recently; have a look : at: : http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=846852+849687+/usr/local/www/db/text/2000/freebsd-current/20000123.freebsd-current : : I got it again. : Meanwhile my system got updated to : FreeBSD abc.xyz.de 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat Jan 22 11:17:16 CET 2000 : : The system is complete soft-updates free. : : This time I had no jailed processes running; the machine was idle : most of the time during the last few days and was rebooted (cleanly), : yesterday. : : The (now totally hosed) file-system was mounted thru the following : fstab-entry: : : /dev/da1s1g /scratch ufs rw 2 2 :Bye, : Andreas : Andreas Braukmann - private site - cat /etc/fstab disklabel da1s1 (so it prints out the label) There's a good chance you overlapped a partition. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 10: 4:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7E85315D83 for ; Fri, 28 Jan 2000 10:04:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA45405; Fri, 28 Jan 2000 10:04:14 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA21039; Fri, 28 Jan 2000 10:04:14 -0800 (PST) (envelope-from obrien) Date: Fri, 28 Jan 2000 10:04:14 -0800 From: "David O'Brien" To: Warner Losh Cc: current@freebsd.org Subject: Re: Makefile.inc1 change Message-ID: <20000128100414.A21021@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200001281633.JAA62420@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001281633.JAA62420@harmony.village.org>; from imp@village.org on Fri, Jan 28, 2000 at 09:33:32AM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 28, 2000 at 09:33:32AM -0700, Warner Losh wrote: > This looks like a safe change to make, since we have no fortran in the > tree that needs to get built. It doesn't disable building of fortran > later in the build, just from building it potentially twice. > > Comments? I like it. If it passes a clean and -DNOCLEAN buildworld, commit that baby! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 10: 8: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1958414C4A; Fri, 28 Jan 2000 10:08:00 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA11992; Fri, 28 Jan 2000 11:07:59 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA63334; Fri, 28 Jan 2000 11:08:16 -0700 (MST) Message-Id: <200001281808.LAA63334@harmony.village.org> To: obrien@freebsd.org Subject: Re: Makefile.inc1 change Cc: current@freebsd.org In-reply-to: Your message of "Fri, 28 Jan 2000 10:04:14 PST." <20000128100414.A21021@dragon.nuxi.com> References: <20000128100414.A21021@dragon.nuxi.com> <200001281633.JAA62420@harmony.village.org> Date: Fri, 28 Jan 2000 11:08:16 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000128100414.A21021@dragon.nuxi.com> "David O'Brien" writes: : I like it. If it passes a clean and -DNOCLEAN buildworld, commit that : baby! OK. It passes a clean buildworld + installworld. I'll crank up the -DNOCLEAN right now. Looks like the savings aren't huge. Like 3 minutes out of 140 on my fast machine. More on my slow machine. Still 2% increase in buildworld times for a 5 line hack isn't that bad, no? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 10:29: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 4D2B114D19; Fri, 28 Jan 2000 10:29:00 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id NAA90843; Fri, 28 Jan 2000 13:28:47 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001281828.NAA90843@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20000128190022.A47078@lucifer.bart.nl> Date: Fri, 28 Jan 2000 13:28:47 -0500 (EST) From: John Baldwin To: Jeroen Ruigrok van der Werven Subject: RE: More world breakage Cc: committers@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Jan-00 Jeroen Ruigrok van der Werven wrote: > ===> bin/pwd > install -c -s -o root -g wheel -m 555 pwd /bin > install -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1 > ===> bin/rcp > install -c -s -o root -g wheel -m 4555 -fschg rcp /bin > /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" > *** Error code 1 > > Stop in /usr/src/bin/rcp. > *** Error code 1 > > > This is the second or third make world to bomb on me with the same > error. I ensured sources and such were clean. > > I think David O`Brien saw the same breakage. This is indicative of a larger problem with installworld. The short version is that we need install tools just like we have build tools now. The long version is this: Problem: It would seem from Asmodai's breakage that installworld assumes that it is ok to use the existing binaries on the system in /bin /usr/bin, etc. to install the new ones. However, if you have a rare case like this where the old and new libs/progs are incompatible, then there is a window between the installation of the different parts where you can get screwed. For example, here the new libc gets installed, which doesn't have the 'strings_to_flags' call. The old install program (not yet replaced) tries to call the 'string_to_flags' function which was present in the old libc but which isn't around anymore. Boom! Solution: We need statically built install tools just like we have build tools. I think we should use the newer versions (i.e. static versions of the ones we just built under /usr/obj during buildworld that are linked against the new libraries), rather than doing some fancy footwork to make the existing binaries work. We already do this with the build tools. By using the newer binaries we only have to maintain one interface in our Makefiles to the install tools: whatever their current interface is in /usr/src. Comments, suggestions? -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 10:32:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.bart.nl (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id E879E15C32; Fri, 28 Jan 2000 10:32:31 -0800 (PST) (envelope-from asmodai@lucifer.bart.nl) Received: (from asmodai@localhost) by lucifer.bart.nl (8.9.3/8.9.3) id TAA47487; Fri, 28 Jan 2000 19:32:30 +0100 (CET) (envelope-from asmodai) Date: Fri, 28 Jan 2000 19:32:30 +0100 From: Jeroen Ruigrok van der Werven To: John Baldwin Cc: committers@FreeBSD.org, current@FreeBSD.org Subject: Re: More world breakage Message-ID: <20000128193230.B47078@lucifer.bart.nl> References: <20000128190022.A47078@lucifer.bart.nl> <200001281828.NAA90843@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001281828.NAA90843@server.baldwin.cx>; from jhb@FreeBSD.org on Fri, Jan 28, 2000 at 01:28:47PM -0500 Organisation: bART Internet Services B.V. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000128 19:30], John Baldwin (jhb@FreeBSD.org) wrote: > >> ===> bin/rcp >> install -c -s -o root -g wheel -m 4555 -fschg rcp /bin >> /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" >> *** Error code 1 >> >> Stop in /usr/src/bin/rcp. >> *** Error code 1 >> >This is indicative of a larger problem with installworld. The short >version is that we need install tools just like we have build tools now. In the meantime, should you encounter a broken make world with this use the following WORKAROUND: cd /usr/src/usr.bin/xinstall && make && make install and resume the make world. -- Jeroen Ruigrok van der Werven Network- and systemadministrator bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 11:26: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp3.xs4all.nl (smtp3.xs4all.nl [194.109.127.49]) by hub.freebsd.org (Postfix) with ESMTP id 3E93D15C57 for ; Fri, 28 Jan 2000 11:25:54 -0800 (PST) (envelope-from paulz@trantor.xs4all.nl) Received: from trantor.xs4all.nl (trantor.xs4all.nl [194.109.61.248]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA13982 for ; Fri, 28 Jan 2000 20:25:51 +0100 (CET) Received: from trantor.xs4all.nl (localhost [127.0.0.1]) by trantor.xs4all.nl (8.9.3/8.9.3) with ESMTP id UAA00668 for ; Fri, 28 Jan 2000 20:15:04 +0100 (MET) (envelope-from paulz@trantor.xs4all.nl) Message-Id: <200001281915.UAA00668@trantor.xs4all.nl> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org Subject: Parallel port back Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Jan 2000 20:15:04 +0100 From: Paul van der Zwan Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My parallel port is back. Switching the it from 3BC to 378 made the probe recognize it again. Apparently the new code doesn't like the 3BC address as much as the old code.. Paul -- Paul van der Zwan paulz @ trantor.xs4all.nl "I think I'll move to theory, everything works in theory..." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 11:42:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 0C99215C60; Fri, 28 Jan 2000 11:41:53 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=spike.adm.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 12EHHC-000B29-00; Fri, 28 Jan 2000 19:41:50 +0000 Received: from cas (cas.adm.scc.nl [192.168.1.3]) by spike.adm.scc.nl (8.9.3/8.9.3) with SMTP id UAA38149; Fri, 28 Jan 2000 20:41:48 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <002901bf69c7$b832ab40$0301a8c0@adm.scc.nl> From: "Marcel Moolenaar" To: "John Baldwin" , "Jeroen Ruigrok van der Werven" Cc: , References: <200001281828.NAA90843@server.baldwin.cx> Subject: Re: More world breakage Date: Fri, 28 Jan 2000 20:41:47 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 28-Jan-00 Jeroen Ruigrok van der Werven wrote: > > ===> bin/pwd > > install -c -s -o root -g wheel -m 555 pwd /bin > > install -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1 > > ===> bin/rcp > > install -c -s -o root -g wheel -m 4555 -fschg rcp /bin > > /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" > > *** Error code 1 > > > > Stop in /usr/src/bin/rcp. > > *** Error code 1 [snip] > This is indicative of a larger problem with installworld. The short > version is that we need install tools just like we have build tools now. > The long version is this: [snip] > It would seem from Asmodai's breakage that installworld assumes that it > is ok to use the existing binaries on the system in /bin /usr/bin, etc. [snip] > We need statically built install tools just like we have build tools. [snip] > Comments, suggestions? [snip] I already have patches (somewhere :-) that solve this problem. I choose not to apply these before the release. I will fix installworld after the release. For now, you can use the buildkernel and installkernel targets (after a buildworld) to solve the (possibly complex) dependencies between kernel, modules and world. FYI, marcel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 11:52: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 30AD915C03; Fri, 28 Jan 2000 11:51:57 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id OAA01002; Fri, 28 Jan 2000 14:51:28 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001281951.OAA01002@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <002901bf69c7$b832ab40$0301a8c0@adm.scc.nl> Date: Fri, 28 Jan 2000 14:51:28 -0500 (EST) From: John Baldwin To: Marcel Moolenaar Subject: Re: More world breakage Cc: current@FreeBSD.org, committers@FreeBSD.org, Jeroen Ruigrok van der Werven Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Jan-00 Marcel Moolenaar wrote: >> On 28-Jan-00 Jeroen Ruigrok van der Werven wrote: >> > ===> bin/pwd >> > install -c -s -o root -g wheel -m 555 pwd /bin >> > install -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1 >> > ===> bin/rcp >> > install -c -s -o root -g wheel -m 4555 -fschg rcp /bin >> > /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" >> > *** Error code 1 >> > >> > Stop in /usr/src/bin/rcp. >> > *** Error code 1 > [snip] >> This is indicative of a larger problem with installworld. The short >> version is that we need install tools just like we have build tools now. >> The long version is this: > [snip] >> It would seem from Asmodai's breakage that installworld assumes that it >> is ok to use the existing binaries on the system in /bin /usr/bin, etc. > [snip] >> We need statically built install tools just like we have build tools. > [snip] >> Comments, suggestions? > [snip] > > I already have patches (somewhere :-) that solve this problem. I choose not > to apply these before the release. I will fix installworld after the > release. For now, you can use the buildkernel and installkernel targets > (after a buildworld) to solve the (possibly complex) dependencies between > kernel, modules and world. This isn't related to the kernel though, it is a dependency within the world between libraries and binaries. Do you have those patches somewhere where I can look at them. I want to start testing them, because it _may_ (I'm only saying "may" right now) be better to fix this before 4.0 so that we don't have 4 million using cvsup to upgrade to 4.0 (despite all the warnings about 4.0 being only for early adopters) and then running into this and flooding -questions. I'd like to prevent a FAQ rather than create one, if you know what I mean. > FYI, > > marcel -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 12: 4:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id 128BB15C97; Fri, 28 Jan 2000 12:04:29 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id MAA39573; Fri, 28 Jan 2000 12:05:34 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200001282005.MAA39573@troutmask.apl.washington.edu> Subject: Re: More world breakage In-Reply-To: <002901bf69c7$b832ab40$0301a8c0@adm.scc.nl> from Marcel Moolenaar at "Jan 28, 2000 08:41:47 pm" To: Marcel Moolenaar Date: Fri, 28 Jan 2000 12:05:34 -0800 (PST) Cc: John Baldwin , Jeroen Ruigrok van der Werven , committers@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Marcel Moolenaar wrote: > > I already have patches (somewhere :-) that solve this problem. I choose not > to apply these before the release. I will fix installworld after the > release. For now, you can use the buildkernel and installkernel targets > (after a buildworld) to solve the (possibly complex) dependencies between > kernel, modules and world. > The buildkernel target seems to be broke. The following sequence was followed (starting at 0900 PST ): %cvsup supfile.current %cd /usr/src %make -j 4 buildworld %setenv KERNEL SGK %make buildkernel -- Steve cc -c -O -pipe -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I/usr/src/sys -I/usr/src/sys/../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 /usr/src/sys/net/if_ethersubr.c /usr/src/sys/net/if_ethersubr.c: In function `ether_output': /usr/src/sys/net/if_ethersubr.c:215: `ETHER_HDR_LEN' undeclared (first use in this function) /usr/src/sys/net/if_ethersubr.c:215: (Each undeclared identifier is reported only once [20 more warnings/errors deleted]. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 12:41:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (Postfix) with ESMTP id D684B15012; Fri, 28 Jan 2000 12:41:09 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.3/8.9.3) id MAA43251; Fri, 28 Jan 2000 12:42:28 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <200001282042.MAA43251@troutmask.apl.washington.edu> Subject: Re: More world breakage In-Reply-To: From "(env:" "sgk)" at "Jan 28, 2000 12:05:34 pm" To: sgk@troutmask.apl.washington.edu Date: Fri, 28 Jan 2000 12:42:28 -0800 (PST) Cc: Marcel Moolenaar , John Baldwin , Jeroen Ruigrok van der Werven , current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sgk wrote: > Marcel Moolenaar wrote: > > > > I already have patches (somewhere :-) that solve this problem. I choose not > > to apply these before the release. I will fix installworld after the > > release. For now, you can use the buildkernel and installkernel targets > > (after a buildworld) to solve the (possibly complex) dependencies between > > kernel, modules and world. > > > > The buildkernel target seems to be broke. The following sequence > was followed (starting at 0900 PST ): > > %cvsup supfile.current > %cd /usr/src > %make -j 4 buildworld > %setenv KERNEL SGK > %make buildkernel > AARGH! Please, ignore. I some how removed "options INET" from my configuration files. -- Steve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 13:16:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (Postfix) with ESMTP id C262314F35; Fri, 28 Jan 2000 13:16:09 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.166]) by smtp02.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA6E8; Fri, 28 Jan 2000 22:16:05 +0100 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id WAA36031; Fri, 28 Jan 2000 22:16:01 +0100 (CET) (envelope-from asmodai) Date: Fri, 28 Jan 2000 22:16:00 +0100 From: Jeroen Ruigrok/Asmodai To: Warner Losh Cc: obrien@freebsd.org, current@freebsd.org Subject: Re: Makefile.inc1 change Message-ID: <20000128221600.E31577@daemon.ninth-circle.org> References: <20000128100414.A21021@dragon.nuxi.com> <200001281633.JAA62420@harmony.village.org> <20000128100414.A21021@dragon.nuxi.com> <200001281808.LAA63334@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001281808.LAA63334@harmony.village.org>; from imp@village.org on Fri, Jan 28, 2000 at 11:08:16AM -0700 Organisation: Ninth-Circle Enterprises Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000128 20:00], Warner Losh (imp@village.org) wrote: >In message <20000128100414.A21021@dragon.nuxi.com> "David O'Brien" writes: >: I like it. If it passes a clean and -DNOCLEAN buildworld, commit that >: baby! > >OK. It passes a clean buildworld + installworld. I'll crank up the >-DNOCLEAN right now. > >Looks like the savings aren't huge. Like 3 minutes out of 140 on my >fast machine. More on my slow machine. Still 2% increase in >buildworld times for a 5 line hack isn't that bad, no? All the bits help. =) And anyways, as you said, compiling it twice seems a bit unnecessary. Feel free to commit when you're sure. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project How the gods kill... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 13:18:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id ADB4815AA8; Fri, 28 Jan 2000 13:18:18 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA12683; Fri, 28 Jan 2000 14:18:16 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA64568; Fri, 28 Jan 2000 14:18:35 -0700 (MST) Message-Id: <200001282118.OAA64568@harmony.village.org> To: Jeroen Ruigrok/Asmodai Subject: Re: Makefile.inc1 change Cc: obrien@freebsd.org, current@freebsd.org In-reply-to: Your message of "Fri, 28 Jan 2000 22:16:00 +0100." <20000128221600.E31577@daemon.ninth-circle.org> References: <20000128221600.E31577@daemon.ninth-circle.org> <20000128100414.A21021@dragon.nuxi.com> <200001281633.JAA62420@harmony.village.org> <20000128100414.A21021@dragon.nuxi.com> <200001281808.LAA63334@harmony.village.org> Date: Fri, 28 Jan 2000 14:18:34 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000128221600.E31577@daemon.ninth-circle.org> Jeroen Ruigrok/Asmodai writes: : All the bits help. =) : : And anyways, as you said, compiling it twice seems a bit unnecessary. : : Feel free to commit when you're sure. I'm sure. I did a make buildworld make installworld. I then did a make buildworld -DNOCLEAN. No ill effects from this change were detected. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 14:34: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id 39B9615C63; Fri, 28 Jan 2000 14:33:54 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=spike.adm.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 12EJxf-0003Gx-00; Fri, 28 Jan 2000 22:33:52 +0000 Received: from cas (cas.adm.scc.nl [192.168.1.3]) by spike.adm.scc.nl (8.9.3/8.9.3) with SMTP id XAA77310; Fri, 28 Jan 2000 23:33:49 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <002301bf69df$bd24eb00$0301a8c0@adm.scc.nl> From: "Marcel Moolenaar" To: "John Baldwin" Cc: , , "Jeroen Ruigrok van der Werven" References: <200001281951.OAA01002@server.baldwin.cx> Subject: Re: More world breakage Date: Fri, 28 Jan 2000 23:33:44 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I already have patches (somewhere :-) that solve this problem. I choose not > > to apply these before the release. I will fix installworld after the > > release. For now, you can use the buildkernel and installkernel targets > > (after a buildworld) to solve the (possibly complex) dependencies between > > kernel, modules and world. > > This isn't related to the kernel though, it is a dependency within the world > between libraries and binaries. It's also related to the kernel, where installworld is installing and subsequently running binaries that won't work with the current kernel. The same applies to installing shared binaries and running them without the proper libraries. > Do you have those patches somewhere where I > can look at them. I want to start testing them, because it _may_ (I'm only > saying "may" right now) be better to fix this before 4.0 so that we don't have > 4 million using cvsup to upgrade to 4.0 (despite all the warnings about 4.0 > being only for early adopters) and then running into this and flooding > -questions. I'd like to prevent a FAQ rather than create one, if you know > what I mean. I don't think we should change yet another thing before a release. The problem shouldn't have been created this close to a release in the first place. We have to stop somewhere, and I think we should stop "fixing" right here, right now unless there's a *really* good reason not to (IMO of course). BTW: I've posted the patches before on -committers IIRC... marcel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 14:42: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from pluto.forumone.com (host04.forumone.com [207.197.235.4]) by hub.freebsd.org (Postfix) with ESMTP id ACB9615D3A; Fri, 28 Jan 2000 14:41:48 -0800 (PST) (envelope-from adhir@forumone.com) Received: by pluto.forumone.com with Internet Mail Service (5.5.1960.3) id ; Fri, 28 Jan 2000 17:41:37 -0500 Message-ID: From: Alok Dhir To: "'wonko@entropy.tmok.com'" , "'freebsd-questions@freebsd.org'" , "'freebsd-current@freebsd.org'" Subject: RE: ColdFusion 4.5 RC3 Date: Fri, 28 Jan 2000 17:41:23 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there differences in the Linux emulation from -stable -> -current? > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Brian Hechinger > Sent: Thursday, January 27, 2000 5:34 PM > To: freebsd-questions@freebsd.org; freebsd-current@freebsd.org > Subject: ColdFusion 4.5 RC3 > > > I can consistantly get ColdFusion 4.5 RC3 installed on > FreeBSD-current. > It will not work on -stable (i didn't really mess with it too much > however) > > i haven't gotten the Apache module to work yet (but i haven't > even looked > at it, so give me time) > > instructions are at http://users.tmok.com/~wonko/cf > > -wonko > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 16: 7:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id DED3614E52 for ; Fri, 28 Jan 2000 16:07:43 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id TAA05379 for ; Fri, 28 Jan 2000 19:07:39 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001290007.TAA05379@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: current@freebsd.org From: "Louis A. Mamakos" Subject: new C++ compiler changes Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Jan 2000 19:07:39 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just put a new -current on my test machine, and watched a bunch of stuff fall over and die due to the new C++ implementation. Is it possible to bump the revision of libstdc++ (and perhaps others) so that existing programs can continue to function? I fear I will be tracking down occasional broken C++ programs for days now. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 17:31:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id A80E415DEE; Fri, 28 Jan 2000 17:31:03 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id UAA42086; Fri, 28 Jan 2000 20:30:55 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001290130.UAA42086@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <002301bf69df$bd24eb00$0301a8c0@adm.scc.nl> Date: Fri, 28 Jan 2000 20:30:55 -0500 (EST) From: John Baldwin To: Marcel Moolenaar Subject: Re: More world breakage Cc: Jeroen Ruigrok van der Werven , committers@FreeBSD.org, current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Jan-00 Marcel Moolenaar wrote: > It's also related to the kernel, where installworld is installing and > subsequently running binaries that won't work with the current kernel. The > same applies to installing shared binaries and running them without the > proper libraries. Ok, I'll buy that. :) >> Do you have those patches somewhere where I can look at them. I want to >> start testing them, because it _may_ (I'm only saying "may" right now) be >> better to fix this before 4.0 so that we don't have 4 million users using >> cvsup to upgrade to 4.0 (despite all the warnings about 4.0 >> being only for early adopters) and then running into this and flooding >> -questions. I'd like to prevent a FAQ rather than create one, if you know >> what I mean. > > I don't think we should change yet another thing before a release. The > problem shouldn't have been created this close to a release in the first > place. We have to stop somewhere, and I think we should stop "fixing" right > here, right now unless there's a *really* good reason not to (IMO of > course). You're right. I guess the proper solution is to just back these changes out until after 4.0 when you can finish fixing up install side of 'world'. I just got ahead of myself a little. > BTW: I've posted the patches before on -committers IIRC... Probably, another case of too much energy and not quite enough careful thought on my part. > marcel -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 17:37: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 7376F15D75 for ; Fri, 28 Jan 2000 17:37:00 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id RAA47539; Fri, 28 Jan 2000 17:37:00 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id RAA24311; Fri, 28 Jan 2000 17:37:00 -0800 (PST) (envelope-from obrien) Date: Fri, 28 Jan 2000 17:37:00 -0800 From: "David O'Brien" To: "Louis A. Mamakos" Cc: current@freebsd.org Subject: Re: new C++ compiler changes Message-ID: <20000128173700.A24289@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <200001290007.TAA05379@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001290007.TAA05379@whizzo.transsys.com>; from louie@TransSys.COM on Fri, Jan 28, 2000 at 07:07:39PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote: > Is it possible to bump the revision of libstdc++ (and perhaps others) so > that existing programs can continue to function? Nope. This is -CURRENT and this type of thing happens. And with a RELEASE about to happen, I don't want people continually asking for these old libs. Right now I can easily diagnose the problem and determine which libs are -fno-vtable-thunks and which are -fvtable-thunks. > I fear I will be tracking down occasional broken C++ programs for days > now. I'd rather people flushed out the old libs now, than have them haunt us in weird ways for months. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 18: 6:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 99EFB14D0C for ; Fri, 28 Jan 2000 18:06:18 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 23407 invoked from network); 29 Jan 2000 01:59:35 -0000 Received: from bde.zeta.org.au (HELO ?203.2.228.102?) (203.2.228.102) by gidora.zeta.org.au with SMTP; 29 Jan 2000 01:59:35 -0000 Date: Sat, 29 Jan 2000 12:58:07 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Makefile.inc1 change In-Reply-To: <200001281633.JAA62420@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jan 2000, Warner Losh wrote: > The following has survived a make buildworld at least once. It > optimizes buildworld a little by not building fortran as part of the > build tools. This breaks bootetrapping of fortran. Fortran is not built as a build- tool. Only a tool to build fortran is built. This tool is like the internal tools for sh and libcurses, etc. It must be built in the host environment, since the version built in the target environment may not run. Tests of tools need to test building from an old and foreign environment, e.g., 3.3 for alpha. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 18: 7:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 02C4C15C41 for ; Fri, 28 Jan 2000 18:07:43 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id TAA13566; Fri, 28 Jan 2000 19:07:41 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id TAA66170; Fri, 28 Jan 2000 19:08:01 -0700 (MST) Message-Id: <200001290208.TAA66170@harmony.village.org> To: Bruce Evans Subject: Re: Makefile.inc1 change Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 29 Jan 2000 12:58:07 +1100." References: Date: Fri, 28 Jan 2000 19:08:01 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bruce Evans writes: : This breaks bootetrapping of fortran. Fortran is not built as a build- : tool. Only a tool to build fortran is built. This tool is like the : internal tools for sh and libcurses, etc. It must be built in the host : environment, since the version built in the target environment may not : run. : : Tests of tools need to test building from an old and foreign environment, : e.g., 3.3 for alpha. So I should back this out? I didn't do a 3.3 buildworld. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 18:54:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id B07B314FB2 for ; Fri, 28 Jan 2000 18:54:01 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 26524 invoked from network); 29 Jan 2000 02:53:57 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 29 Jan 2000 02:53:57 -0000 Date: Sat, 29 Jan 2000 13:53:54 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: John Baldwin Cc: Jeroen Ruigrok van der Werven , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: RE: More world breakage In-Reply-To: <200001281828.NAA90843@server.baldwin.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jan 2000, John Baldwin wrote: >... > Solution: > > We need statically built install tools just like we have build tools. > I think we should use the newer versions (i.e. static versions of the > ones we just built under /usr/obj during buildworld that are linked > against the new libraries), rather than doing some fancy footwork to Using the newer version would be even more broken, since they may be for another arch, or may just use new syscalls that don't exist in the host kernel. > make the existing binaries work. We already do this with the build > tools. By using the newer binaries we only have to maintain one > interface in our Makefiles to the install tools: whatever their > current interface is in /usr/src. The build-tools are carefully built so that work in the host environment. Essentially the same thing needs to be done for installation tools. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 20:10:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 4E53A14DCD for ; Fri, 28 Jan 2000 20:10:33 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id FAA03547 for current@freebsd.org; Sat, 29 Jan 2000 05:10:31 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id E0C778863; Sat, 29 Jan 2000 02:35:43 +0100 (CET) Date: Sat, 29 Jan 2000 02:35:43 +0100 From: Ollivier Robert To: current@freebsd.org Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <20000129023543.A95423@keltia.freenix.fr> Mail-Followup-To: current@freebsd.org References: <19991231225535.A8004@Denninger.Net> <20000101113750.B89903@Denninger.Net> <200001011747.JAA45272@vashon.polstra.com> <20000101194118.A19381@keltia.freenix.fr> <200001012002.MAA45455@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001012002.MAA45455@vashon.polstra.com>; from jdp@polstra.com on Sat, Jan 01, 2000 at 12:02:00PM -0800 X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [I said about ntpd usage of sched_* functions:] > > We should make them standard IMO. According to John Polstra: > I agree. BTW, as the sched_* POSIX functions are now standard in GENERIC, I've decided along with the upgrade to ntpd 4.0.99b to re-enable them. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #77: Thu Dec 30 12:49:51 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 20:17:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 1EAD314F00 for ; Fri, 28 Jan 2000 20:17:49 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 30189 invoked from network); 29 Jan 2000 04:17:44 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 29 Jan 2000 04:17:43 -0000 Date: Sat, 29 Jan 2000 15:17:40 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Makefile.inc1 change In-Reply-To: <200001290208.TAA66170@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 28 Jan 2000, Warner Losh wrote: > In message Bruce Evans writes: > : This breaks bootetrapping of fortran. Fortran is not built as a build- > : tool. Only a tool to build fortran is built. This tool is like the > : internal tools for sh and libcurses, etc. It must be built in the host > : environment, since the version built in the target environment may not > : run. > : > : Tests of tools need to test building from an old and foreign environment, > : e.g., 3.3 for alpha. > > So I should back this out? I didn't do a 3.3 buildworld. Of course. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 20:19:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id C827915230; Fri, 28 Jan 2000 20:19:39 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id XAA06638; Fri, 28 Jan 2000 23:19:37 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <200001290419.XAA06638@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: obrien@FreeBSD.ORG Cc: current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: new C++ compiler changes References: <200001290007.TAA05379@whizzo.transsys.com> <20000128173700.A24289@dragon.nuxi.com> In-reply-to: Your message of "Fri, 28 Jan 2000 17:37:00 PST." <20000128173700.A24289@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 28 Jan 2000 23:19:37 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote: > > Is it possible to bump the revision of libstdc++ (and perhaps others) so > > that existing programs can continue to function? > > Nope. This is -CURRENT and this type of thing happens. And with a > RELEASE about to happen, I don't want people continually asking for these > old libs. > Well, OK, I can deal with this myself. I'm just concerned about the folks who will eventually upgrade from 3.4 to 4.0, and have their C++ programs stop working. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 20:23:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3E8C715DB3 for ; Fri, 28 Jan 2000 20:23:50 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA13988; Fri, 28 Jan 2000 21:23:48 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA00501; Fri, 28 Jan 2000 21:23:45 -0700 (MST) Message-Id: <200001290423.VAA00501@harmony.village.org> To: Bruce Evans Subject: Re: Makefile.inc1 change Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 29 Jan 2000 15:17:40 +1100." References: Date: Fri, 28 Jan 2000 21:23:45 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bruce Evans writes: : > So I should back this out? I didn't do a 3.3 buildworld. : : Of course. OK. I'm doing a 3.3 buildworld right now on a virgin 3.3R system. I'll let you know what happens with that. If it is a problem at all, then I'll back it out (since others have asked me privately to run the test and not back it out unless there are problems). The program that it was building was definitely the first pass of the fortran compiler. What in the tree needs this in order to build, even on the alpha? I could find only one .f file in the entire tree and it looked like a test file, which didn't seem to be referenced in the makefile at all. What's the alpha problem? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Jan 28 23:22:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 337B614BFA for ; Fri, 28 Jan 2000 23:22:00 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p27-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.156]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id QAA16043; Sat, 29 Jan 2000 16:21:44 +0900 (JST) Message-ID: <3891524F.1BD2820D@newsguy.com> Date: Fri, 28 Jan 2000 17:24:47 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Kazutaka YOKOTA Cc: Garrett Wollman , "Jordan K. Hubbard" , Bill Fenner , current@FreeBSD.ORG Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT References: <200001271856.KAA09456@windsor.research.att.com> <45272.949008490@zippy.cdrom.com> <200001272143.QAA20638@khavrinen.lcs.mit.edu> <200001280038.JAA12998@zodiac.mech.utsunomiya-u.ac.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kazutaka YOKOTA wrote: > > I have had reports on similar lockup in both 4.0-CURRENT and 3.X. > I personally have not been able to reproduce it, but now my new sand box > machine exhibits this problem occasionally. > > The I/O access to the AT keyboard by the atkbd driver have not changed > much for the last couple of years, despite massive source tree > reorganization. And yes, problem reports started to pop-up since > sometime around the last summer. > > I have not been able to track down the cause of the problem, but > am suspecting possibility of the clock/timer problem. It happens with me from time to time. It is NOT related to kernel, since it happens between boot0 and boot2. It will happen when I'm typing something during boot, so it's probably some sort of race. Symptons include keys having weird mappings, and some keys not mapping to anything at all, after boot. At boot2/loader, no keypress is recognized at all. Very rare. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "2 b or not to b" meaning varies depending on whether one uses the 79 or the 83 standard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 0: 5:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 9E97B15184 for ; Sat, 29 Jan 2000 00:05:49 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id AAA75913; Sat, 29 Jan 2000 00:05:41 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sat, 29 Jan 2000 00:05:41 -0800 (PST) From: Doug White To: "F. Heinrichmeyer" Cc: "freebsd-current@FreeBSD.ORG" Subject: Re: ASDM and linux emulation? In-Reply-To: <38903C8A.C9A83021@fernuni-hagen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 27 Jan 2000, F. Heinrichmeyer wrote: > I would like to use an ASDM (backup software) with linux-emulation. I > get > the following in /var/log/messages: > > es-i2 /kernel: linux: syscall setresuid is obsoleted\ > or not implemented (pid=41052) > Jan 27 13:12:42 es-i2 /kernel: pid 41052 (dsm), \ > uid 0: exited on signal 11 (core dumped) What FreeBSD is this? I've run the v3 client under linux mode without bad syscalls (just that silly pathmunging stuff that I need to renew the fight over). I have a hacked linux.ko that lets dsmc backup what you think it will back up, but the SCO version is a better fit. I should try it on my workstation. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 0: 9:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id C99F015696 for ; Sat, 29 Jan 2000 00:09:18 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@freebsd.org; Sat, 29 Jan 2000 09:09:17 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.3/8.9.3) id JAA46069 for freebsd-current@freebsd.org; Sat, 29 Jan 2000 09:04:05 +0100 (CET) (envelope-from tanis) Date: Sat, 29 Jan 2000 09:04:05 +0100 From: German Tischler To: freebsd-current@freebsd.org Subject: make release failure Message-ID: <20000129090405.A45799@gaspode.franken.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I just tried a ,make release' with USA_RESIDENT set to NO. It failed with --- crunchide -k _crunched_grep_stub grep.lo cc -static -o fixit_crunch fixit_crunch.o cat.lo chmod.lo chroot.lo cp.lo dd.lo df.lo echo.lo expr.lo kill.lo ln.lo ls.lo mkdir.lo mv.lo rm.lo rmdir.lo sleep.lo sync.lo chown.lo clri.lo disklabel.lo dmesg.lo fdisk.lo mknod.lo mount.lo reboo t.lo restore.lo swapon.lo umount.lo mount_msdos.lo mount_cd9660.lo ftp.lo more.l o telnet.lo vi.lo grep.lo -lcrypt -ltelnet -lutil -ll -lm -lcurses -ltermcap -le dit -lgnuregex -lkvm -lz telnet.lo: In function `setpolicy': telnet.lo(.text+0x22af): undefined reference to `ipsec_set_policy' telnet.lo(.text+0x22c0): undefined reference to `ipsec_strerror' telnet.lo(.text+0x2303): undefined reference to `ipsec_get_policylen' *** Error code 1 Stop in /usr/obj/usr/src/release/fixit_crunch. *** Error code 1 Stop in /usr/src/release. *** Error code 1 Stop in /usr/src/release. --- Perhaps that part of the release is not aware that something exists outside of USA_RESIDENT=YES. -- German Tischler, tanis@gaspode.franken.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 0:33: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B3CC315829 for ; Sat, 29 Jan 2000 00:32:59 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA14636; Sat, 29 Jan 2000 01:32:57 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA02007; Sat, 29 Jan 2000 01:32:55 -0700 (MST) Message-Id: <200001290832.BAA02007@harmony.village.org> To: Bruce Evans Subject: Re: Makefile.inc1 change Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 29 Jan 2000 15:17:40 +1100." References: Date: Sat, 29 Jan 2000 01:32:55 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bruce Evans writes: : > So I should back this out? I didn't do a 3.3 buildworld. : : Of course. OK. I've done the build on 3.3 and it works. It does break cross compilation. There is a tool (fini) that gets built on the host with the host libraries and run on the host to generate some files and this during the last phase of the build. Maybe the right thing to do for make depend is to somehow arrange for all things needed to build depend get built with the host compiler and if host != target they get deleted before the actual build with the tools. Of course, hours before the code freeze is an inauspicious time to make such sweeping declaration. This automates much of the tools problem... I will back it out until after 4.0 so this change can be analized in more detail. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 1:10:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 5349E15DB8 for ; Sat, 29 Jan 2000 01:10:54 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id SAA05991; Sat, 29 Jan 2000 18:10:49 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id SAA25775; Sat, 29 Jan 2000 18:10:48 +0900 (JST) Received: from localhost ([192.168.245.42]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id SAA27024; Sat, 29 Jan 2000 18:10:47 +0900 (JST) To: tanis@gaspode.franken.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: make release failure In-Reply-To: <20000129090405.A45799@gaspode.franken.de> References: <20000129090405.A45799@gaspode.franken.de> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000129181128K.shin@nd.net.fujitsu.co.jp> Date: Sat, 29 Jan 2000 18:11:28 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 55 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi. > > I just tried a ,make release' with USA_RESIDENT set to NO. It failed with > dit -lgnuregex -lkvm -lz > telnet.lo: In function `setpolicy': > telnet.lo(.text+0x22af): undefined reference to `ipsec_set_policy' > telnet.lo(.text+0x22c0): undefined reference to `ipsec_strerror' > telnet.lo(.text+0x2303): undefined reference to `ipsec_get_policylen' > *** Error code 1 > Stop in /usr/obj/usr/src/release/fixit_crunch. > *** Error code 1 > Stop in /usr/src/release. > *** Error code 1 > Stop in /usr/src/release. Sorry for the problem. Could you try with this patch for now? Yoshinobu Inoue --- usr.bin/telnet/Makefile.orig Thu Jan 27 15:04:00 2000 +++ usr.bin/telnet/Makefile Sun Jan 30 03:19:31 2000 @@ -40,12 +40,12 @@ CFLAGS+=-DENV_HACK CFLAGS+=-DSKEY CFLAGS+=-I${.CURDIR}/../../lib -CFLAGS+=-DIPSEC -DINET6 +CFLAGS+=-DINET6 #CFLAGS+= -DKRB4 -DPADD= ${LIBTERMCAP} ${LIBTELNET} ${LIBIPSEC} -LDADD= -ltermcap -ltelnet -lipsec +DPADD= ${LIBTERMCAP} ${LIBTELNET} +LDADD= -ltermcap -ltelnet #DPADD+= ${LIBKRB} ${LIBDES} #LDADD+= -lkrb -ldes @@ -57,7 +57,14 @@ CRYPT_SRC+= ring.c ring.h telnet.c terminal.c utilities.c Makefile NOCRYPT_DIR=${.CURDIR}/Nocrypt +.if !defined(RELEASE_CRUNCH) +CFLAGS+=-DIPSEC +DPADD= ${LIBIPSEC} +LDADD= -lipsec +.endif + .include nocrypt: @echo "Encryption code already removed." + To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 1:12: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id A993B15829 for ; Sat, 29 Jan 2000 01:12:02 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 9444 invoked from network); 29 Jan 2000 09:11:59 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 29 Jan 2000 09:11:59 -0000 Date: Sat, 29 Jan 2000 20:11:55 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: Makefile.inc1 change In-Reply-To: <200001290832.BAA02007@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Jan 2000, Warner Losh wrote: > In message Bruce Evans writes: > : > So I should back this out? I didn't do a 3.3 buildworld. > : > : Of course. > > OK. I've done the build on 3.3 and it works. > > It does break cross compilation. There is a tool (fini) that gets > built on the host with the host libraries and run on the host to > generate some files and this during the last phase of the build. Right. > Maybe the right thing to do for make depend is to somehow arrange for > all things needed to build depend get built with the host compiler and > if host != target they get deleted before the actual build with the > tools. Of course, hours before the code freeze is an inauspicious > time to make such sweeping declaration. This automates much of the > tools problem... David committed Marcel's workaround for the problem with make depend in f771 2 weeks ago. I don't know why you still have problems. Deleting things is another workaround. The correct fix is to build tools in separate directories and not build these directories for cross-building. > I will back it out until after 4.0 so this change can be analized in > more detail. Thanks. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 1:15: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6C51414A18 for ; Sat, 29 Jan 2000 01:15:02 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id CAA14939; Sat, 29 Jan 2000 02:15:01 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id CAA02507; Sat, 29 Jan 2000 02:15:00 -0700 (MST) Message-Id: <200001290915.CAA02507@harmony.village.org> To: Bruce Evans Subject: Re: Makefile.inc1 change Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sat, 29 Jan 2000 20:11:55 +1100." References: Date: Sat, 29 Jan 2000 02:15:00 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Bruce Evans writes: : David committed Marcel's workaround for the problem with make depend in : f771 2 weeks ago. I don't know why you still have problems. No. I'm not having problems there. I was just making observations. : Deleting things is another workaround. The correct fix is to build : tools in separate directories and not build these directories for : cross-building. Yes. The tools for building things often assume too much. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 2:14:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id 0FAAC15228 for ; Sat, 29 Jan 2000 02:14:18 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m4.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id TAA09159; Sat, 29 Jan 2000 19:14:13 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m4.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id TAA23267; Sat, 29 Jan 2000 19:14:13 +0900 (JST) Received: from localhost ([192.168.245.90]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id TAA28745; Sat, 29 Jan 2000 19:14:11 +0900 (JST) To: tanis@gaspode.franken.de Cc: freebsd-current@FreeBSD.ORG Subject: Re: make release failure In-Reply-To: <20000129181128K.shin@nd.net.fujitsu.co.jp> References: <20000129090405.A45799@gaspode.franken.de> <20000129181128K.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000129191448K.shin@nd.net.fujitsu.co.jp> Date: Sat, 29 Jan 2000 19:14:48 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 42 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sorry for the problem. Could you try with this patch for now? Last patch was bad. Please try this one instead. Yoshinobu Inoue --- usr.bin/telnet/Makefile.orig Thu Jan 27 15:04:00 2000 +++ usr.bin/telnet/Makefile Sun Jan 30 04:28:44 2000 @@ -40,12 +40,12 @@ CFLAGS+=-DENV_HACK CFLAGS+=-DSKEY CFLAGS+=-I${.CURDIR}/../../lib -CFLAGS+=-DIPSEC -DINET6 +CFLAGS+=-DINET6 #CFLAGS+= -DKRB4 -DPADD= ${LIBTERMCAP} ${LIBTELNET} ${LIBIPSEC} -LDADD= -ltermcap -ltelnet -lipsec +DPADD= ${LIBTERMCAP} ${LIBTELNET} +LDADD= -ltermcap -ltelnet #DPADD+= ${LIBKRB} ${LIBDES} #LDADD+= -lkrb -ldes @@ -57,7 +57,14 @@ CRYPT_SRC+= ring.c ring.h telnet.c terminal.c utilities.c Makefile NOCRYPT_DIR=${.CURDIR}/Nocrypt +.if !defined(RELEASE_CRUNCH) +CFLAGS+=-DIPSEC +DPADD+= ${LIBIPSEC} +LDADD+= -lipsec +.endif + .include nocrypt: @echo "Encryption code already removed." + To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 2:30:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id F2A8C15FAA for ; Sat, 29 Jan 2000 02:30:35 -0800 (PST) (envelope-from ab@cage.tse-online.de) Received: (qmail 14756 invoked by uid 1000); 29 Jan 2000 10:30:59 -0000 Date: Sat, 29 Jan 2000 11:30:59 +0100 From: Andreas Braukmann To: "Rodney W. Grimes" Cc: current@FreeBSD.ORG, dillon@backplane.com Subject: Re: very silent, but heavy filesystem-crash Message-ID: <20000129113059.F371@cage.tse-online.de> References: <20000128171618.C1305@cage.tse-online.de> <200001281622.IAA81548@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001281622.IAA81548@gndrsh.dnsmgr.net>; from freebsd@gndrsh.dnsmgr.net on Fri, Jan 28, 2000 at 08:22:32AM -0800 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, ... thanks for your assistance. I On Fri, Jan 28, 2000 at 08:22:32AM -0800, Rodney W. Grimes wrote: > Next step is run the ``save'' fsck: > fsck -n /scratch >/someplacewithspace 2>&1 > > there is some illuminated filesystem-hacker who would like to > > take a peek. (I would allow ssh-access to the box ...) > $1.00/MB for me to recover it.... ... I was used to this kind of service for hosed FAT-filesystems and hosed partition tables ;) ... (I did it by stuffing the 'hosed disks' into one of my unix-boxes and working on the raw devices ...) > if you need it. ... fortunately not. Just have a look at the mountpoint's name .... > I don't do it for fun. ... understandable :), I made the offer just for the case anybody wants to track down a potential bug. But as it comes out I had (in fact :( ) a typo in the disklabel. I checked the disklabel two times before my post to -current, but I had obviously a little problem with my 'eye-brain-interlink'. I really shouldn't admit this in this forum, should I? ... But in relabeling the disk I left the disklabel as follows: # size offset fstype [fsize bsize bps/cpg] b: 1048576 0 swap # (Cyl. 0 - 65*) c: 17912412 0 unused 0 0 # (Cyl. 0 - 1114*) g: 17912412 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 1114*) Sorry for bothering all of you, feeling soooooo stultified and the big and heavy hat (with a certain pattern on it) weighs on my head ... Thanks, Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 3:47: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id D778D151FE for ; Sat, 29 Jan 2000 03:47:07 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id DAA53544; Sat, 29 Jan 2000 03:47:02 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id DAA31982; Sat, 29 Jan 2000 03:47:04 -0800 (PST) (envelope-from obrien) Date: Sat, 29 Jan 2000 03:47:04 -0800 From: "David O'Brien" To: Yoshinobu Inoue Cc: freebsd-current@FreeBSD.ORG Subject: Re: make release failure Message-ID: <20000129034703.A26801@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000129090405.A45799@gaspode.franken.de> <20000129181128K.shin@nd.net.fujitsu.co.jp> <20000129191448K.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000129191448K.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Sat, Jan 29, 2000 at 07:14:48PM +0900 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 29, 2000 at 07:14:48PM +0900, Yoshinobu Inoue wrote: > > Sorry for the problem. Could you try with this patch for now? It might be easier to just commit it if `make buildworld' passes. With the double CVS checkout required in `make release' I don't know an easy good way to apply patches in the second checkout. Since `make release' is already broken, you cannot break it worse. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 3:59:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id A69B9160B7; Sat, 29 Jan 2000 03:59:38 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id UAA13849; Sat, 29 Jan 2000 20:59:37 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id UAA11921; Sat, 29 Jan 2000 20:59:36 +0900 (JST) Received: from localhost ([192.168.245.132]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id UAA01551; Sat, 29 Jan 2000 20:59:35 +0900 (JST) To: obrien@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: make release failure In-Reply-To: <20000129034703.A26801@dragon.nuxi.com> References: <20000129181128K.shin@nd.net.fujitsu.co.jp> <20000129191448K.shin@nd.net.fujitsu.co.jp> <20000129034703.A26801@dragon.nuxi.com> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000129210010T.shin@nd.net.fujitsu.co.jp> Date: Sat, 29 Jan 2000 21:00:10 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It might be easier to just commit it if `make buildworld' passes. OK, but now I have middle class speed machine at hand, and maybe it takes 2 or 3 hours. Also, do other apps which use libipsec will need same kind of change? (There is one under usr.bin, and several under usr.sbin.) Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 4:26:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from bg.sics.se (bg.sics.se [193.10.66.124]) by hub.freebsd.org (Postfix) with ESMTP id 0D24614D75; Sat, 29 Jan 2000 04:20:21 -0800 (PST) (envelope-from bg@bg.sics.se) Received: (from bg@localhost) by bg.sics.se (8.9.3/8.9.3) id NAA03180; Sat, 29 Jan 2000 13:18:14 +0100 (CET) (envelope-from bg) To: Doug White , "F. Heinrichmeyer" Cc: freebsd-emulation@freebsd.org, "freebsd-current@FreeBSD.ORG" Subject: Re: ASDM and linux emulation? References: From: Bjoern Groenvall Date: 29 Jan 2000 13:18:13 +0100 In-Reply-To: Doug White's message of Sat, 29 Jan 2000 00:05:41 -0800 (PST) Message-ID: Lines: 162 X-Mailer: Red Gnus v0.52/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fritz & Doug, Doug White writes: > On Thu, 27 Jan 2000, F. Heinrichmeyer wrote: > > > I would like to use an ASDM (backup software) with linux-emulation. I > > get > > the following in /var/log/messages: > > > > es-i2 /kernel: linux: syscall setresuid is obsoleted\ > > or not implemented (pid=41052) > > Jan 27 13:12:42 es-i2 /kernel: pid 41052 (dsm), \ > > uid 0: exited on signal 11 (core dumped) > > What FreeBSD is this? I've run the v3 client under linux mode without bad > syscalls (just that silly pathmunging stuff that I need to renew the fight > over). Perhaps you are running the backup as root while Fritz has a setuid root program? In any case, please find attacked a patch that implements setresuid. The patch is relative to 3.3 but should port pretty easily to current. Fritz, if this cures your problems, please drop me a note. Cheers, Björn -- _ _ ,_______________. Bjorn Gronvall (Björn Grönvall) /_______________/| Swedish Institute of Computer Science | || PO Box 1263, S-164 29 Kista, Sweden | Schroedingers || Email: bg@sics.se, Phone +46 -8 633 15 25 | Cat |/ Cellular +46 -70 768 06 35, Fax +46 -8 751 72 30 `---------------' --- linux_misc.c 2000/01/29 10:23:54 1.1 +++ linux_misc.c 2000/01/29 11:40:28 @@ -797,6 +797,44 @@ } int +linux_setresuid(p, uap) + struct proc *p; + struct linux_setresuid_args *uap; +{ + struct setreuid_args bsd_args; + + /* Allow setresuid iff the saved effective uid is left unchanged. */ + if (uap->suid != -1 && uap->suid != p->p_cred->p_svuid) { + printf("Linux-emul(%d): setresuid(%d, %d, %d) not supported\n", + p->p_pid, uap->ruid, uap->euid, uap->suid); + return ENOSYS; + } + bsd_args.ruid = uap->ruid; + bsd_args.euid = uap->euid; + /* uap->suid is unchanged */ + return setreuid(p, &bsd_args); +} + +int +linux_setresgid(p, uap) + struct proc *p; + struct linux_setresgid_args *uap; +{ + struct setregid_args bsd_args; + + /* Allow setresgid iff the saved effective gid is left unchanged. */ + if (uap->sgid != -1 && uap->sgid != p->p_cred->p_svgid) { + printf("Linux-emul(%d): setresgid(%d, %d, %d) not supported\n", + p->p_pid, uap->rgid, uap->egid, uap->sgid); + return ENOSYS; + } + bsd_args.rgid = uap->rgid; + bsd_args.egid = uap->egid; + /* uap->sgid is unchanged */ + return setregid(p, &bsd_args); +} + +int linux_msync(struct proc *p, struct linux_msync_args *args) { struct msync_args bsd_args; --- linux_proto.h 2000/01/29 10:28:59 1.1 +++ linux_proto.h 2000/01/29 11:08:53 @@ -402,6 +402,16 @@ int new_len; char new_len_[PAD_(int)]; int flags; char flags_[PAD_(int)]; }; +struct linux_setresuid_args { + int ruid; char ruid_[PAD_(int)]; + int euid; char euid_[PAD_(int)]; + int suid; char suid_[PAD_(int)]; +}; +struct linux_setresgid_args { + int rgid; char rgid_[PAD_(int)]; + int egid; char egid_[PAD_(int)]; + int sgid; char sgid_[PAD_(int)]; +}; struct linux_rt_sigaction_args { int sig; char sig_[PAD_(int)]; struct linux_new_sigaction * act; char act_[PAD_(struct linux_new_sigaction *)]; @@ -528,6 +538,8 @@ int linux_sched_setscheduler __P((struct proc *, struct linux_sched_setscheduler_args *)); int linux_sched_getscheduler __P((struct proc *, struct linux_sched_getscheduler_args *)); int linux_mremap __P((struct proc *, struct linux_mremap_args *)); +int linux_setresuid __P((struct proc *, struct linux_setresuid_args *)); +int linux_setresgid __P((struct proc *, struct linux_setresgid_args *)); int linux_rt_sigaction __P((struct proc *, struct linux_rt_sigaction_args *)); int linux_rt_sigprocmask __P((struct proc *, struct linux_rt_sigprocmask_args *)); int linux_chown __P((struct proc *, struct linux_chown_args *)); --- linux_syscall.h 2000/01/29 10:43:49 1.1 +++ linux_syscall.h 2000/01/29 11:09:30 @@ -162,7 +162,9 @@ #define LINUX_SYS_sched_rr_get_interval 161 #define LINUX_SYS_nanosleep 162 #define LINUX_SYS_linux_mremap 163 +#define LINUX_SYS_linux_setresuid 164 #define LINUX_SYS_poll 168 +#define LINUX_SYS_linux_setresgid 170 #define LINUX_SYS_linux_rt_sigaction 174 #define LINUX_SYS_linux_rt_sigprocmask 175 #define LINUX_SYS_linux_chown 182 --- linux_sysent.c 2000/01/29 10:06:22 1.1 +++ linux_sysent.c 2000/01/29 11:06:51 @@ -178,13 +178,13 @@ { 2, (sy_call_t *)sched_rr_get_interval }, /* 161 = sched_rr_get_interval */ { 2, (sy_call_t *)nanosleep }, /* 162 = nanosleep */ { 4, (sy_call_t *)linux_mremap }, /* 163 = linux_mremap */ - { 0, (sy_call_t *)nosys }, /* 164 = setresuid */ + { 0, (sy_call_t *)linux_setresuid }, /* 164 = linux_setresuid */ { 0, (sy_call_t *)nosys }, /* 165 = getresuid */ { 0, (sy_call_t *)nosys }, /* 166 = new_vm86 */ { 0, (sy_call_t *)nosys }, /* 167 = query_module */ { 3, (sy_call_t *)poll }, /* 168 = poll */ { 0, (sy_call_t *)nosys }, /* 169 = nfsservctl */ - { 0, (sy_call_t *)nosys }, /* 170 = setresgid */ + { 0, (sy_call_t *)linux_setresgid }, /* 170 = linux_setresgid */ { 0, (sy_call_t *)nosys }, /* 171 = getresgid */ { 0, (sy_call_t *)nosys }, /* 172 = prctl */ { 0, (sy_call_t *)nosys }, /* 173 = rt_sigreturn */ --- syscalls.master 2000/01/29 10:06:58 1.1 +++ syscalls.master 2000/01/29 11:07:31 @@ -238,14 +238,14 @@ 163 STD LINUX { int linux_mremap(caddr_t addr, int old_len, \ int new_len, int flags); } -164 UNIMPL LINUX setresuid +164 STD LINUX { int linux_setresuid(int ruid, int euid, int suid); } 165 UNIMPL LINUX getresuid 166 UNIMPL LINUX new_vm86 167 UNIMPL LINUX query_module 168 NOPROTO LINUX { int poll(struct pollfd*, unsigned int nfds, \ long timeout); } 169 UNIMPL LINUX nfsservctl -170 UNIMPL LINUX setresgid +170 STD LINUX { int linux_setresgid(int rgid, int egid, int sgid); } 171 UNIMPL LINUX getresgid 172 UNIMPL LINUX prctl 173 UNIMPL LINUX rt_sigreturn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 5:16: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (Postfix) with ESMTP id EF76B157F0 for ; Sat, 29 Jan 2000 05:12:19 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@freebsd.org; Sat, 29 Jan 2000 13:59:00 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.3/8.9.3) id NAA93262; Sat, 29 Jan 2000 13:55:37 +0100 (CET) (envelope-from tanis) Date: Sat, 29 Jan 2000 13:55:37 +0100 From: German Tischler To: Yoshinobu Inoue Cc: freebsd-current@freebsd.org Subject: Re: make release failure Message-ID: <20000129135537.A93021@gaspode.franken.de> References: <20000129090405.A45799@gaspode.franken.de> <20000129181128K.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000129181128K.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Sat, Jan 29, 2000 at 10:11:05AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 29, 2000 at 10:11:05AM +0100, Yoshinobu Inoue wrote: > Sorry for the problem. Could you try with this patch for now? Thank you, it worked, at least for completing the interupted release build. I have not tested in which way the patch affects building the world though. -- German Tischler, tanis@gaspode.franken.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 5:39:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-74.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.202]) by hub.freebsd.org (Postfix) with ESMTP id 4EC0615FCB; Sat, 29 Jan 2000 05:39:10 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA74632; Sat, 29 Jan 2000 13:38:38 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id NAA03154; Sat, 29 Jan 2000 13:38:38 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001291338.NAA03154@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: "Louis A. Mamakos" Cc: obrien@FreeBSD.ORG, current@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: new C++ compiler changes In-Reply-To: Message from "Louis A. Mamakos" of "Fri, 28 Jan 2000 23:19:37 EST." <200001290419.XAA06638@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Jan 2000 13:38:38 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On Fri, Jan 28, 2000 at 07:07:39PM -0500, Louis A. Mamakos wrote: > > > Is it possible to bump the revision of libstdc++ (and perhaps others) so > > > that existing programs can continue to function? > > > > Nope. This is -CURRENT and this type of thing happens. And with a > > RELEASE about to happen, I don't want people continually asking for these > > old libs. > > > > Well, OK, I can deal with this myself. I'm just concerned about the > folks who will eventually upgrade from 3.4 to 4.0, and have their > C++ programs stop working. libstdc++ is version 2 in -stable. > louie -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 5:46:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 9BF0C15A39 for ; Sat, 29 Jan 2000 05:46:50 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id FAA53826; Sat, 29 Jan 2000 05:46:45 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id FAA66226; Sat, 29 Jan 2000 05:46:44 -0800 (PST) (envelope-from obrien) Date: Sat, 29 Jan 2000 05:46:43 -0800 From: "David O'Brien" To: "Louis A. Mamakos" Cc: current@FreeBSD.ORG Subject: Re: new C++ compiler changes Message-ID: <20000129054643.A66201@dragon.nuxi.com> Reply-To: current@FreeBSD.ORG References: <200001290007.TAA05379@whizzo.transsys.com> <20000128173700.A24289@dragon.nuxi.com> <200001290419.XAA06638@whizzo.transsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001290419.XAA06638@whizzo.transsys.com>; from louie@TransSys.COM on Fri, Jan 28, 2000 at 11:19:37PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 28, 2000 at 11:19:37PM -0500, Louis A. Mamakos wrote: > > Well, OK, I can deal with this myself. I'm just concerned about the > folks who will eventually upgrade from 3.4 to 4.0, and have their > C++ programs stop working. There will be the same problem WRT C++ when upgrading from 3.4 to 4.0 either way. Both "g++-2.95.2 -fno-vtable-thunks" and "g++-2.95.2 -fvtable-thunks" are incompatible C++ platforms from G++ 2.7.x. People wishing to use C++ programs compiled on FreeBSD 3.x need to install the ``compat3x'' distribution to get the libstdc++.so.? compatibility library. For ports those same people will have to keep their 3.x compiled C++ libs (in /usr/local/lib & /usr/X11R6/lib) around how ever they like. Again, this requirement would be the same with or w/o the C++ ABI change I just made. -- -- David (obrien@NUXI.com) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 6:32:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from q4.quik.com (q4.quik.com [216.176.28.1]) by hub.freebsd.org (Postfix) with ESMTP id 0AC3D151CB for ; Sat, 29 Jan 2000 06:32:43 -0800 (PST) (envelope-from signal@reno.quik.com) Received: from snoopy2 (ip049.reno.quik.com [209.213.147.49]) by q4.quik.com (8.9.3/8.9.3) with SMTP id GAA246328 for ; Sat, 29 Jan 2000 06:32:40 -0800 Message-ID: <000801bf6a65$91f8b520$01000a0a@snoopy2> From: "Stephen Sargent" To: Subject: Date: Sat, 29 Jan 2000 06:31:43 -0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BF6A22.82229500" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BF6A22.82229500 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0005_01BF6A22.82229500 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0005_01BF6A22.82229500-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 7:33:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [24.234.53.177]) by hub.freebsd.org (Postfix) with ESMTP id C5A3715169 for ; Sat, 29 Jan 2000 07:33:41 -0800 (PST) (envelope-from freebsd@mrynet.com) Received: (from freebsd@localhost) by mrynet.com (8.9.3/8.9.3) id HAA73332 for freebsd-current@freebsd.org; Sat, 29 Jan 2000 07:33:40 -0800 (PST) (envelope-from freebsd) Posted-Date: Sat, 29 Jan 2000 07:33:40 -0800 (PST) Message-Id: <200001291533.HAA73332@mrynet.com> From: freebsd@mrynet.com (FreeBSD mailing list) Date: Sat, 29 Jan 2000 07:33:38 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: install(1) installed too late in world Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following occured during a world build after this morning's CVSUP: ===> bin/rcp install -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 An install in usr.bin/xinstall fixed the problem. Last world build was two days ago. Regards, Scott -- Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@mrynet.lv To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 7:44:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from test.tar.com (test.tar.com [204.95.187.4]) by hub.freebsd.org (Postfix) with ESMTP id ED44114FB4 for ; Sat, 29 Jan 2000 07:44:49 -0800 (PST) (envelope-from dick@test.tar.com) Received: (from dick@localhost) by test.tar.com (8.9.3/8.9.3) id JAA77516; Sat, 29 Jan 2000 09:44:31 -0600 (CST) (envelope-from dick) Date: Sat, 29 Jan 2000 09:44:31 -0600 From: "Richard Seaman, Jr." To: Ollivier Robert Cc: current@FreeBSD.ORG Subject: Re: xntpd - VERY old folks, how about updating? :-) Message-ID: <20000129094431.J46134@tar.com> References: <19991231225535.A8004@Denninger.Net> <20000101113750.B89903@Denninger.Net> <200001011747.JAA45272@vashon.polstra.com> <20000101194118.A19381@keltia.freenix.fr> <200001012002.MAA45455@vashon.polstra.com> <20000129023543.A95423@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000129023543.A95423@keltia.freenix.fr>; from roberto@keltia.freenix.fr on Sat, Jan 29, 2000 at 02:35:43AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 29, 2000 at 02:35:43AM +0100, Ollivier Robert wrote: > [I said about ntpd usage of sched_* functions:] > > > We should make them standard IMO. > > According to John Polstra: > > I agree. > > BTW, as the sched_* POSIX functions are now standard in GENERIC, I've decided > along with the upgrade to ntpd 4.0.99b to re-enable them. Be aware that the sched_* functions are somewhat broken. Peter Dufault had some patches that fixed them. I also had a later version of them. When Julian inquired about committing my later version, Peter indicated he was re-working the patches and communicating with bde about them. This was about 1-2 months ago. -- Richard Seaman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 262-367-5450 Chenequa WI 53058 fax: 262-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 8: 2:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 3F681150D9 for ; Sat, 29 Jan 2000 08:02:28 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id PAA07123; Sat, 29 Jan 2000 15:59:23 GMT (envelope-from n_hibma@webweaving.org) Date: Sat, 29 Jan 2000 15:59:22 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: "Dave J. Boers" Cc: Devin Butterfield , Donn Miller , current@FreeBSD.ORG Subject: Re: pcm - stutters In-Reply-To: <20000127013125.A49548@relativity.student.utwente.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I too notice these problems of mpg123 skipping during disk activity or X > > graphics ops but I have always had these problems, both with -STABLE and > > -CURRENT. I notice this with xmms too. So this is nothing new. > > Isn't this simply a typical issue of IDE hardware? I too notice xmms > skipping on heavy disk activity (typically the find command that runs from > cron at 01:59). This happens even though I have two processors and a disk > that can do 16 Mb/sec on UDMA66. One would expect such a system to be able > to do a find and play mp3's simultaneously. Pressing Ctrl-Z repeats the same quarter second fragment forever. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 8:36:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id F02C914C4F for ; Sat, 29 Jan 2000 08:36:22 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 13129 invoked from network); 29 Jan 2000 16:36:20 -0000 Received: from lcm97.cvzoom.net (HELO cvzoom.net) (208.230.69.97) by ns.cvzoom.net with SMTP; 29 Jan 2000 16:36:20 -0000 Message-ID: <389316EA.2BFFB38C@cvzoom.net> Date: Sat, 29 Jan 2000 11:35:54 -0500 From: Donn Miller X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: pcm - stutters References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma wrote: > Pressing Ctrl-Z repeats the same quarter second fragment forever. I know the pcm driver uses a circular buffer. Maybe a small chunk of the sound gets stuck in the buffer, and when you press ^Z, the app is unable to tell the sound driver to break out of the loop. Also, RealPlayer still repeats a small fragment over and over when the data flow is interrupted due to net congestion. This is RealPlayer 5, though... - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 8:38:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 28E2E14C17 for ; Sat, 29 Jan 2000 08:38:36 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-2.enteract.com (dscheidt@shell-2.enteract.com [207.229.143.41]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id KAA43781; Sat, 29 Jan 2000 10:38:06 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Sat, 29 Jan 2000 10:38:05 -0600 (CST) From: David Scheidt To: Nick Hibma Cc: "Dave J. Boers" , Devin Butterfield , Donn Miller , current@FreeBSD.ORG Subject: Re: pcm - stutters In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Jan 2000, Nick Hibma wrote: > > > I too notice these problems of mpg123 skipping during disk activity or X > > > graphics ops but I have always had these problems, both with -STABLE and > > > -CURRENT. I notice this with xmms too. So this is nothing new. > > > > Isn't this simply a typical issue of IDE hardware? I too notice xmms > > skipping on heavy disk activity (typically the find command that runs from > > cron at 01:59). This happens even though I have two processors and a disk > > that can do 16 Mb/sec on UDMA66. One would expect such a system to be able > > to do a find and play mp3's simultaneously. > > Pressing Ctrl-Z repeats the same quarter second fragment forever. > And 'fg' doesn't always make it continue properly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 9:54:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 57C7015246 for ; Sat, 29 Jan 2000 09:54:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA23587; Sat, 29 Jan 2000 09:54:01 -0800 (PST) (envelope-from dillon) Date: Sat, 29 Jan 2000 09:54:01 -0800 (PST) From: Matthew Dillon Message-Id: <200001291754.JAA23587@apollo.backplane.com> To: Andreas Braukmann Cc: "Rodney W. Grimes" , current@FreeBSD.ORG Subject: Re: very silent, but heavy filesystem-crash References: <20000128171618.C1305@cage.tse-online.de> <200001281622.IAA81548@gndrsh.dnsmgr.net> <20000129113059.F371@cage.tse-online.de> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :But as it comes out I had (in fact :( ) a typo in the disklabel. : :I checked the disklabel two times before my post to -current, but :I had obviously a little problem with my 'eye-brain-interlink'. : :I really shouldn't admit this in this forum, should I? ... But :in relabeling the disk I left the disklabel as follows: : :# size offset fstype [fsize bsize bps/cpg] : b: 1048576 0 swap # (Cyl. 0 - 65*) : c: 17912412 0 unused 0 0 # (Cyl. 0 - 1114*) : g: 17912412 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 1114*) : : :Sorry for bothering all of you, feeling soooooo stultified :and the big and heavy hat (with a certain pattern on it) weighs :on my head ... : : :Thanks, : Andreas Heh! Don't feel bad, the only reason I thought it was a disklabel problem is because I've done the same thing myself in the past, with similar results! What we really need to do is fix disklabel to at least warn of overlaps. The only reason I don't make the same mistakes these days is because every time I run the beast I check my calculations 6 ways from sunday, forwards and backwards. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 10:14:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1D0C014CC8 for ; Sat, 29 Jan 2000 10:14:42 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA14140; Sat, 29 Jan 2000 10:14:40 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA10881; Sat, 29 Jan 2000 10:14:40 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 29 Jan 2000 10:14:40 -0800 (PST) Message-Id: <200001291814.KAA10881@vashon.polstra.com> To: imp@village.org Subject: Re: Makefile.inc1 change In-Reply-To: <200001290832.BAA02007@harmony.village.org> References: <200001290832.BAA02007@harmony.village.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001290832.BAA02007@harmony.village.org>, Warner Losh wrote: > I will back it out until after 4.0 so this change can be analized in ^^^^^^^^ > more detail. What a perfect Freudian slip! Does this mean you plan to, er, put it where the sun don't shine? :-) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 10:20:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5C1D21524F for ; Sat, 29 Jan 2000 10:20:29 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA18248; Sat, 29 Jan 2000 11:20:24 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA07999; Sat, 29 Jan 2000 11:20:28 -0700 (MST) Message-Id: <200001291820.LAA07999@harmony.village.org> To: John Polstra Subject: Re: Makefile.inc1 change Cc: current@freebsd.org In-reply-to: Your message of "Sat, 29 Jan 2000 10:14:40 PST." <200001291814.KAA10881@vashon.polstra.com> References: <200001291814.KAA10881@vashon.polstra.com> <200001290832.BAA02007@harmony.village.org> Date: Sat, 29 Jan 2000 11:20:27 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200001291814.KAA10881@vashon.polstra.com> John Polstra writes: : In article <200001290832.BAA02007@harmony.village.org>, : Warner Losh wrote: : : > I will back it out until after 4.0 so this change can be analized in : ^^^^^^^^ : > more detail. : : What a perfect Freudian slip! Does this mean you plan to, er, put it : where the sun don't shine? :-) Ummm, errr, ahhh, no. Other members of this community may, but it was a simple typo. Honest. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 10:24:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 8D66514F68 for ; Sat, 29 Jan 2000 10:24:39 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA18270 for ; Sat, 29 Jan 2000 11:24:34 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA08046 for ; Sat, 29 Jan 2000 11:24:38 -0700 (MST) Message-Id: <200001291824.LAA08046@harmony.village.org> To: current@freebsd.org Subject: PAIN Date: Sat, 29 Jan 2000 11:24:38 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's the current wuildworld times for a 486DX2-66 + 12M RAM over NFS? I have a small box that I'd like to torture test before putting into service and thought this would make a good week long test. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 10:32:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id D40B1156BF for ; Sat, 29 Jan 2000 10:32:24 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id SAA07734 for ; Sat, 29 Jan 2000 18:31:07 GMT (envelope-from n_hibma@webweaving.org) Date: Sat, 29 Jan 2000 18:31:07 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List Subject: OHCI patch for ohci_hash_find_td panic Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY="0-1522841054-949170646=:7678" Content-ID: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1522841054-949170646=:7678 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-ID: Everyone who has seen the ohci_hash_find_td not found panic should try this one and let me know whether the machine panics or not and where. This patch is against CURRENT. It looks like the hardware kind of deviates from the OHCI spec when putting things on the Done queue in case of an error. Important: Your system will panic and completely destroy your filesystem. If it doesn't you got lucky. Cheers, Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ --0-1522841054-949170646=:7678 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII; NAME="ohci.c.diff" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: ATTACHMENT; FILENAME="ohci.c.diff" SW5kZXg6IG9oY2kuYw0KPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0KUkNTIGZp bGU6IC9ob21lL25jdnMvc3JjL3N5cy9kZXYvdXNiL29oY2kuYyx2DQpyZXRy aWV2aW5nIHJldmlzaW9uIDEuMzYNCmRpZmYgLXcgLXUgLXIxLjM2IG9oY2ku Yw0KLS0tIG9oY2kuYwkyMDAwLzAxLzI5IDE2OjI1OjU1CTEuMzYNCisrKyBv aGNpLmMJMjAwMC8wMS8yOSAxNzowNDo0NA0KQEAgLTkxLDcgKzkxLDcgQEAN CiAjaWZkZWYgT0hDSV9ERUJVRw0KICNkZWZpbmUgRFBSSU5URih4KQlpZiAo b2hjaWRlYnVnKSBsb2dwcmludGYgeA0KICNkZWZpbmUgRFBSSU5URk4obix4 KQlpZiAob2hjaWRlYnVnPihuKSkgbG9ncHJpbnRmIHgNCi1pbnQgb2hjaWRl YnVnID0gMDsNCitpbnQgb2hjaWRlYnVnID0gMTsNCiAjZWxzZQ0KICNkZWZp bmUgRFBSSU5URih4KQ0KICNkZWZpbmUgRFBSSU5URk4obix4KQ0KQEAgLTQx Nyw2ICs0MTcsNyBAQA0KIAl1c2JkX3N0YXR1cyBlcnI7DQogCWludCBpLCBv ZmZzOw0KIAl1c2JfZG1hX3QgZG1hOw0KKwlpbnQgczsNCiANCiAJaWYgKHNj LT5zY19mcmVldGRzID09IE5VTEwpIHsNCiAJCURQUklOVEZOKDIsICgib2hj aV9hbGxvY19zdGQ6IGFsbG9jYXRpbmcgY2h1bmtcbiIpKTsNCkBAIC00MzYs NiArNDM3LDExIEBADQogCXNjLT5zY19mcmVldGRzID0gc3RkLT5uZXh0dGQ7 DQogCW1lbXNldCgmc3RkLT50ZCwgMCwgc2l6ZW9mKG9oY2lfdGRfdCkpOw0K IAlzdGQtPm5leHR0ZCA9IE5VTEw7DQorDQorCXMgPSBzcGx1c2IoKTsNCisJ b2hjaV9oYXNoX2FkZF90ZChzYywgc3RkKTsNCisJc3BseChzKTsNCisNCiAJ cmV0dXJuIChzdGQpOw0KIH0NCiANCkBAIC00NDQsNiArNDUwLDEyIEBADQog CW9oY2lfc29mdGNfdCAqc2M7DQogCW9oY2lfc29mdF90ZF90ICpzdGQ7DQog ew0KKwlpbnQgczsNCisNCisJcyA9IHNwbHVzYigpOw0KKwlvaGNpX2hhc2hf cmVtX3RkKHNjLCBzdGQpOw0KKwlzcGx4KHMpOw0KKw0KIAlzdGQtPm5leHR0 ZCA9IHNjLT5zY19mcmVldGRzOw0KIAlzYy0+c2NfZnJlZXRkcyA9IHN0ZDsN CiB9DQpAQCAtMTEyNyw3ICsxMTM5LDggQEANCiAjaWZkZWYgT0hDSV9ERUJV Rw0KIAlpZiAob2hjaWRlYnVnID4gMTApIHsNCiAJCURQUklOVEYoKCJvaGNp X3Byb2Nlc3NfZG9uZTogVEQgZG9uZTpcbiIpKTsNCi0JCW9oY2lfZHVtcF90 ZHMoc2RvbmUpOw0KKwkJZm9yIChzdGQgPSBzZG9uZTsgc3RkOyBzdGQgPSBz dGQtPmRuZXh0KQ0KKwkJCW9oY2lfZHVtcF90ZChzZG9uZSk7DQogCX0NCiAj ZW5kaWYNCiANCkBAIC0xMTM1LDcgKzExNDgsMTYgQEANCiAJCXhmZXIgPSBz dGQtPnhmZXI7DQogCQlzdGRuZXh0ID0gc3RkLT5kbmV4dDsNCiAJCURQUklO VEZOKDUsICgib2hjaV9wcm9jZXNzX2RvbmU6IHN0ZD0lcCB4ZmVyPSVwIGhj cHJpdj0lcFxuIiwNCi0JCQkJc3RkLCB4ZmVyLCB4ZmVyLT5oY3ByaXYpKTsN CisJCQkJc3RkLCB4ZmVyLCAoeGZlcj8geGZlci0+aGNwcml2Ok5VTEwpKSk7 DQorCQlpZiAoeGZlciA9PSBOVUxMIHx8IChzdGQtPmZsYWdzICYgT0hDSV9U RF9IQU5ETEVEKSkgew0KKwkJCS8qIHhmZXIgPT0gTlVMTDogVGhlcmUgc2Vl bXMgdG8gYmUgbm8geGZlciBhc3NvY2lhdGVkDQorCQkJICogd2l0aCB0aGlz IFRELiBJdCBpcyB0YWlscCB0aGF0IGhhcHBlbmVkIHRvIGVuZCB1cCBvbg0K KwkJCSAqIHRoZSBkb25lIHF1ZXVlLg0KKwkJCSAqIGZsYWdzICYgT0hDSV9U RF9IQU5ETEVEOiBUaGUgVEQgaGFzIGFscmVhZHkgYmVlbg0KKwkJCSAqIGhh bmRsZWQgYnkgcHJvY2Vzc19kb25lIGFuZCBzaG91bGQgbm90IGJlIGRvbmUg YWdhaW4uDQorCQkJICovDQorCQkJY29udGludWU7DQorCQl9DQogCQljYyA9 IE9IQ0lfVERfR0VUX0NDKExFKHN0ZC0+dGQudGRfZmxhZ3MpKTsNCiAJCXVz Yl91bnRpbWVvdXQob2hjaV90aW1lb3V0LCB4ZmVyLCB4ZmVyLT50aW1vX2hh bmRsZSk7DQogCQlpZiAoeGZlci0+c3RhdHVzID09IFVTQkRfQ0FOQ0VMTEVE IHx8DQpAQCAtMTE1Niw3ICsxMTc4LDYgQEANCiAJCQkJeGZlci0+c3RhdHVz ID0gVVNCRF9OT1JNQUxfQ09NUExFVElPTjsNCiAJCQkJdXNiX3RyYW5zZmVy X2NvbXBsZXRlKHhmZXIpOw0KIAkJCX0NCi0JCQlvaGNpX2hhc2hfcmVtX3Rk KHNjLCBzdGQpOw0KIAkJCW9oY2lfZnJlZV9zdGQoc2MsIHN0ZCk7DQogCQl9 IGVsc2Ugew0KIAkJCS8qDQpAQCAtMTE3MiwxNiArMTE5MywyMyBAQA0KIAkJ CSAgT0hDSV9URF9HRVRfQ0MoTEUoc3RkLT50ZC50ZF9mbGFncykpLA0KIAkJ CSAgb2hjaV9jY19zdHJzW09IQ0lfVERfR0VUX0NDKExFKHN0ZC0+dGQudGRf ZmxhZ3MpKV0sDQogCQkJICB4ZmVyKSk7DQorDQorCQkJLyogTWFyayBhbGwg dGhlIFREcyBpbiB0aGUgZG9uZSBxdWV1ZSBmb3IgdGhlIGN1cnJlbnQNCisJ CQkgKiB4ZmVyIGFzIGhhbmRsZWQNCisJCQkgKi8NCisJCQlmb3IgKHAgPSBz dGRuZXh0OyBwOyBwID0gcC0+ZG5leHQpIHsNCisJCQkJaWYgKHAtPnhmZXIg PT0geGZlcikNCisJCQkJCXAtPmZsYWdzIHw9IE9IQ0lfVERfSEFORExFRDsN CisJCQl9DQogDQotCQkJLyogcmVtb3ZlIFREcyAqLw0KKwkJCS8qIHJlbW92 ZSBURHMgZm9yIHRoZSBjdXJyZW50IHhmZXIgZnJvbSB0aGUgRUQgKi8NCiAJ CQlmb3IgKHAgPSBzdGQ7IHAtPnhmZXIgPT0geGZlcjsgcCA9IG4pIHsNCiAJ CQkJbiA9IHAtPm5leHR0ZDsNCi0JCQkJb2hjaV9oYXNoX3JlbV90ZChzYywg cCk7ICAgICAgICAgICAgICAgICAgICAgICAgDQogCQkJCW9oY2lfZnJlZV9z dGQoc2MsIHApOw0KIAkJCX0NCi0NCi0JCQkvKiBjbGVhciBoYWx0ICovDQog CQkJb3BpcGUtPnNlZC0+ZWQuZWRfaGVhZHAgPSBMRShwLT5waHlzYWRkcik7 DQorDQorCQkJLyogWFhYIHdoeSBpcyB0aGlzIGJlaW5nIGRvbmU/IFdoeSBu b3QgT0hDSV9CTEYgdG9vICovDQogCQkJT1dSSVRFNChzYywgT0hDSV9DT01N QU5EX1NUQVRVUywgT0hDSV9DTEYpOw0KIA0KIAkJCWlmIChjYyA9PSBPSENJ X0NDX1NUQUxMKQ0KQEAgLTE0NjIsMTAgKzE0OTAsNiBAQA0KIA0KIAkvKiBJ bnNlcnQgRUQgaW4gc2NoZWR1bGUgKi8NCiAJcyA9IHNwbHVzYigpOw0KLQlv aGNpX2hhc2hfYWRkX3RkKHNjLCBzZXR1cCk7DQotCWlmIChsZW4gIT0gMCkN Ci0JCW9oY2lfaGFzaF9hZGRfdGQoc2MsIGRhdGEpOw0KLQlvaGNpX2hhc2hf YWRkX3RkKHNjLCBzdGF0KTsNCiAJc2VkLT5lZC5lZF90YWlscCA9IExFKHRh aWwtPnBoeXNhZGRyKTsNCiAJb3BpcGUtPnRhaWwudGQgPSB0YWlsOw0KIAlP V1JJVEU0KHNjLCBPSENJX0NPTU1BTkRfU1RBVFVTLCBPSENJX0NMRik7DQpA QCAtMTg3MCw3ICsxODk0LDYgQEANCiAjZW5kaWYNCiAJZm9yICg7IHAtPnhm ZXIgPT0geGZlcjsgcCA9IG4pIHsNCiAJCW4gPSBwLT5uZXh0dGQ7DQotCQlv aGNpX2hhc2hfcmVtX3RkKHNjLCBwKTsNCiAJCW9oY2lfZnJlZV9zdGQoc2Ms IHApOw0KIAl9DQogDQpJbmRleDogb2hjaXZhci5oDQo9PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09DQpSQ1MgZmlsZTogL2hvbWUvbmN2cy9zcmMvc3lzL2Rldi91 c2Ivb2hjaXZhci5oLHYNCnJldHJpZXZpbmcgcmV2aXNpb24gMS4xNQ0KZGlm ZiAtdyAtdSAtcjEuMTUgb2hjaXZhci5oDQotLS0gb2hjaXZhci5oCTIwMDAv MDEvMjcgMjM6MjU6NTgJMS4xNQ0KKysrIG9oY2l2YXIuaAkyMDAwLzAxLzI5 IDEyOjI4OjI1DQpAQCAtNTcsNiArNTcsNyBAQA0KIAl1X2ludDE2X3QgZmxh Z3M7DQogI2RlZmluZSBPSENJX0NBTExfRE9ORQkweDAwMDENCiAjZGVmaW5l IE9IQ0lfQUREX0xFTgkweDAwMDINCisjZGVmaW5lIE9IQ0lfVERfSEFORExF RAkweDAwMDQJCS8qIHNpZ25hbCBwcm9jZXNzX2RvbmUgaGFzIHNlZW4gaXQg Ki8NCiB9IG9oY2lfc29mdF90ZF90Ow0KICNkZWZpbmUgT0hDSV9TVERfU0la RSAoKHNpemVvZiAoc3RydWN0IG9oY2lfc29mdF90ZCkgKyBPSENJX1REX0FM SUdOIC0gMSkgLyBPSENJX1REX0FMSUdOICogT0hDSV9URF9BTElHTikNCiAj ZGVmaW5lIE9IQ0lfU1REX0NIVU5LIDEyOA0K --0-1522841054-949170646=:7678-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 10:38:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (Postfix) with ESMTP id 1B13C14D69 for ; Sat, 29 Jan 2000 10:38:26 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu (root@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA23998 for ; Sat, 29 Jan 2000 13:38:18 -0500 (EST) Received: from rac2.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.3/8.9.3) with SMTP id NAA13753 for ; Sat, 29 Jan 2000 13:38:24 -0500 (EST) Received: from localhost (culverk@localhost) by rac2.wam.umd.edu (8.9.3/8.9.3) with ESMTP id NAA13749 for ; Sat, 29 Jan 2000 13:38:23 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Sat, 29 Jan 2000 13:38:23 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: pcm Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just to let someone know, my ViBRA16X is still having the problem with static. Basically at random whenever xmms or any other program that uses sound opens dsp, it plays loud static instead of the actual sound. I was just wondering if anyone was looking into this problem... ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: AgRSkaterq | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 10:57:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from forrie.net (forrie.net [216.67.12.69]) by hub.freebsd.org (Postfix) with ESMTP id 7FF0E14CEB for ; Sat, 29 Jan 2000 10:57:32 -0800 (PST) (envelope-from forrie@forrie.com) Received: from Forrest (getbent@forrie.ne.mediaone.net [24.128.72.15]) by forrie.net with id e0TIvVL47312 for ; Sat, 29 Jan 2000 13:57:31 -0500 (EST) Message-Id: <4.2.2.20000129135739.00c0a140@216.67.12.69> X-Sender: forrie@216.67.12.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 29 Jan 2000 13:58:03 -0500 To: freebsd-current@freebsd.org From: Forrest Aldrich Subject: More breakages Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cc -c -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -mpreferred-stack-boundary=2 vers.c linking kernel text data bss dec hex filename 1807056 139340 115448 2061844 1f7614 kernel chflags noschg /kernel mv /kernel /kernel.old install -c -m 555 -o root -g wheel -fschg kernel /kernel /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 This is from a cvsup I just performed minutes ago, FYI. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 11:20:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from chmls05.mediaone.net (ne.mediaone.net [24.128.1.70]) by hub.freebsd.org (Postfix) with ESMTP id 1B94015214 for ; Sat, 29 Jan 2000 11:19:39 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (reyim.ne.mediaone.net [24.218.254.39]) by chmls05.mediaone.net (8.8.7/8.8.7) with ESMTP id OAA07465; Sat, 29 Jan 2000 14:19:29 -0500 (EST) Message-ID: <38933D43.7BAF88AC@acm.org> Date: Sat, 29 Jan 2000 14:19:31 -0500 From: Jim Bloom X-Mailer: Mozilla 4.7 [en]C-MOENE (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: More breakages References: <4.2.2.20000129135739.00c0a140@216.67.12.69> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It looks like your last make world or make installworld did not complete. There is an install problem with installworld bootstrapping itself. New libraries are installed before the install binary is installed. When they try to use the "-fschg" option, you get that error. (installworld aborts at rcp with the same problem.) Simple recompile and install /usr/src/usr.bin/xinstall to fix both of these problems. Jim Bloom bloom@acm.org Forrest Aldrich wrote: > > cc -c -O -Wall -Wredundant-decls -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. > -I../../../include -D_KERNEL -include opt_global.h > -elf -mpreferred-stack-boundary=2 vers.c > linking kernel > text data bss dec hex filename > 1807056 139340 115448 2061844 1f7614 kernel > chflags noschg /kernel > mv /kernel /kernel.old > install -c -m 555 -o root -g wheel -fschg kernel /kernel > /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" > *** Error code 1 > > This is from a cvsup I just performed minutes ago, FYI. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 11:29:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-30.mail.demon.net (anchor-post-30.mail.demon.net [194.217.242.88]) by hub.freebsd.org (Postfix) with ESMTP id 10AFE14F91 for ; Sat, 29 Jan 2000 11:29:22 -0800 (PST) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by anchor-post-30.mail.demon.net with esmtp (Exim 2.12 #1) id 12EdYc-0005BT-0U; Sat, 29 Jan 2000 19:29:19 +0000 Received: from nenya (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (Postfix) with SMTP id 77D33D919; Sat, 29 Jan 2000 19:30:50 +0000 (GMT) Message-ID: <002b01bf6a8f$58180520$0304020a@rings> From: "Cameron Grant" To: "Kenneth Wayne Culver" , References: Subject: Re: pcm Date: Sat, 29 Jan 2000 19:30:47 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.3825.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.3825.400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just to let someone know, my ViBRA16X is still having the problem with > static. i've replicated it, but have no idea of the cause. i'll probably rework the sb driver when i rip it and the ess driver apart, but that will wait until i get an ess card. - cameron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 11:31:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id A471F14DE3 for ; Sat, 29 Jan 2000 11:31:18 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA14537; Sat, 29 Jan 2000 11:31:17 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA11095; Sat, 29 Jan 2000 11:31:16 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 29 Jan 2000 11:31:16 -0800 (PST) Message-Id: <200001291931.LAA11095@vashon.polstra.com> To: imp@village.org Subject: Re: PAIN In-Reply-To: <200001291824.LAA08046@harmony.village.org> References: <200001291824.LAA08046@harmony.village.org> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001291824.LAA08046@harmony.village.org>, Warner Losh wrote: > > What's the current wuildworld times for a 486DX2-66 + 12M RAM over > NFS? Dunno yet. I started one in late 1997 but it's still running. I'll let you know when it finishes. :-) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 13: 3:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from queeg.ludd.luth.se (queeg.ludd.luth.se [130.240.16.109]) by hub.freebsd.org (Postfix) with ESMTP id D7AA616241 for ; Sat, 29 Jan 2000 13:03:32 -0800 (PST) (envelope-from pantzer@ludd.luth.se) Received: from speedy.ludd.luth.se (pantzer@speedy.ludd.luth.se [130.240.16.164]) by queeg.ludd.luth.se (8.9.3/8.9.3) with ESMTP id WAA16257 for ; Sat, 29 Jan 2000 22:03:29 +0100 (CET) Message-Id: <200001292103.WAA16257@queeg.ludd.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Subject: INET6 and fxp Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 29 Jan 2000 22:03:28 +0100 From: Mattias Pantzare Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for FreeBSD on an OpenBSD mailinglist :-) http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html Something better than that is probably needed in the long run. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 13:44:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx2.x-treme.gr (mx2.x-treme.gr [212.120.192.15]) by hub.freebsd.org (Postfix) with ESMTP id 6D0C8159F9 for ; Sat, 29 Jan 2000 13:44:00 -0800 (PST) (envelope-from keramida@diogenis.ceid.upatras.gr) Received: from hades.hell.gr (pat50.x-treme.gr [212.120.197.242]) by mx2.x-treme.gr (8.9.3/8.9.3/IPNG-ADV-ANTISPAM-0.1) with ESMTP id XAA02138 for ; Sat, 29 Jan 2000 23:43:55 +0200 Received: (from charon@localhost) by hades.hell.gr (8.9.3/8.9.3) id NAA55528 for freebsd-current@freebsd.org; Sat, 29 Jan 2000 13:43:30 +0200 (EET) (envelope-from keramida@diogenis.ceid.upatras.gr) Date: Sat, 29 Jan 2000 13:43:30 +0200 From: Giorgos Keramidas To: freebsd-current@freebsd.org Subject: Re: Problems installing FreeBSD 4.0 20000125-CURRENT Message-ID: <20000129134303.A55491@hades.hell.gr> Reply-To: keramida@ceid.upatras.gr References: <200001280226.VAA21947@khavrinen.lcs.mit.edu> <200001280253.SAA05541@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001280253.SAA05541@mass.cdrom.com>; from msmith@FreeBSD.ORG on Thu, Jan 27, 2000 at 06:53:51PM -0800 X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E X-Phone-Number: +30-94-6203692, +30-93-2886457 X-Address: Theodorou Kirinaiou 61, 26334 Patra, Greece Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Jan 27, 2000 at 06:53:51PM -0800, Mike Smith wrote: > > The only argument for having a dysfunctional hostname of the variety you > describe is vanity, which is not a valid engineering constraint. Or that you're behind a dialup connection that dynamically assigns IPs. -- Giorgos Keramidas, < keramida @ ceid . upatras . gr > "Don't let your schooling interfere with your education." [Mark Twain] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 15:21: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id B34DA14EAC for ; Sat, 29 Jan 2000 15:21:00 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id PAA16023 for ; Sat, 29 Jan 2000 15:20:53 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA15673 for current@freebsd.org; Sat, 29 Jan 2000 15:20:53 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 29 Jan 2000 15:20:53 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: current@freebsd.org Subject: _KPOSIX_VERSION=199309L in GENERIC is redundant Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In revision 1.230 of src/sys/i386/conf/GENERIC, jkh added: options P1003_1B #Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L But I think the definition of _KPOSIX_VERSION is redundant, because it is already the default in src/sys/sys/param.h: #ifdef P1003_1B #define _P1003_1B_VISIBLE #ifndef _KPOSIX_VERSION #define _KPOSIX_VERSION 199309L #endif #endif Am I right, or am I missing something? John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Disappointment is a good sign of basic intelligence." -- Chögyam Trungpa To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 16: 6:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from serio.al.rim.or.jp (serio.al.rim.or.jp [202.247.191.123]) by hub.freebsd.org (Postfix) with ESMTP id 8627F14E79 for ; Sat, 29 Jan 2000 16:06:35 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from mail1.rim.or.jp by serio.al.rim.or.jp (8.8.8/3.7W/HMX-12) with ESMTP id IAA03062 for ; Sun, 30 Jan 2000 08:28:13 +0900 (JST) Received: from rhea.sky.rim.or.jp (ppp382.kt.rim.or.jp [202.247.140.82]) by mail1.rim.or.jp (3.7W/) id JAA13223 for ; Sun, 30 Jan 2000 09:06:33 +0900 (JST) Received: from localhost.sky.rim.or.jp (localhost [127.0.0.1]) by rhea.sky.rim.or.jp (8.9.3/3.7W/rhea-1.2) with ESMTP id JAA54062 for ; Sun, 30 Jan 2000 09:06:33 +0900 (JST) Date: Sun, 30 Jan 2000 09:06:33 +0900 Message-ID: <86aeloo22e.wl@localhost.sky.rim.or.jp> From: Jun Kuriyama To: current@FreeBSD.org Subject: "rm -rf" behavior on readonly nfs User-Agent: Wanderlust/2.2.16 (No Son Of Mine) SEMI/1.13.7 (Awazu) FLIM/1.13.2 (Kasanui) MULE XEmacs/21.1 (patch 8) (Bryce Canyon) (i386--freebsd) MIME-Version: 1.0 (generated by SEMI 1.13.7 - "Awazu") Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found difference between "rm -rf" for non-exist file on readonly nfs and usual non-writable directory. In this example, /usr/src is readonly nfs mounted and /usr/bin is normal filesystem but not writable. And file "a" is not exist. ----- % rm /usr/bin/a rm: /usr/bin/a: No such file or directory % rm -f /usr/bin/a % rm -rf /usr/bin/a % rm /usr/src/a rm: /usr/src/a: No such file or directory % rm -f /usr/src/a % rm -rf /usr/src/a rm: /usr/src/a: Read-only file system % ----- For "-f" option, last behavior is expected one, or not? Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 16:40: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from backup.af.speednet.com.au (af.speednet.com.au [202.135.188.244]) by hub.freebsd.org (Postfix) with ESMTP id 4C0E314EDE for ; Sat, 29 Jan 2000 16:39:56 -0800 (PST) (envelope-from andyf@speednet.com.au) Received: from localhost (andyf@localhost [127.0.0.1]) by backup.af.speednet.com.au (8.9.3/8.9.3) with ESMTP id LAA32244; Sun, 30 Jan 2000 11:39:25 +1100 (EST) (envelope-from andyf@speednet.com.au) Date: Sun, 30 Jan 2000 11:39:25 +1100 (EST) From: Andy Farkas X-Sender: andyf@backup.af.speednet.com.au To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: PAIN In-Reply-To: <200001291824.LAA08046@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What's the current wuildworld times for a 486DX2-66 + 12M RAM over > NFS? I have a small box that I'd like to torture test before putting > into service and thought this would make a good week long test. 'torture test' is an understatement. This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and both src and obj on the same local disk (softupdates enabled): Script started on Thu Jan 20 01:01:00 2000 backup# cd /usr/src backup# /usr/bin/time make buildworld -------------------------------------------------------------- >>> Cleaning up the temporary elf build tree -------------------------------------------------------------- mkdir -p /usr/obj/citus/src/tmp chflags -R noschg /usr/obj/citus/src/tmp/ rm -rf /usr/obj/citus/src/tmp ... gzip -cn /citus/src/usr.sbin/wlconfig/wlconfig.8 > wlconfig.8.gz ===> etc ===> etc/sendmail rm -f freebsd.cf (cd /citus/src/etc/sendmail && m4 -D_CF_DIR_=/citus/src/etc/sendmail/../../contrib/sendmail/cf/ /citus/src/etc/sendmail/../../contrib/sendmail/cf/m4/cf.m4 freebsd.mc) > freebsd.cf chmod 444 freebsd.cf 54172.61 real 39360.42 user 6506.89 sys backup# Script done on Thu Jan 20 16:22:31 2000 > > Warner > -- :{ andyf@speednet.com.au Andy Farkas System Administrator Speednet Communications http://www.speednet.com.au/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 16:49:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D2B9B15617 for ; Sat, 29 Jan 2000 16:49:29 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id RAA19554; Sat, 29 Jan 2000 17:49:27 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id RAA10279; Sat, 29 Jan 2000 17:49:34 -0700 (MST) Message-Id: <200001300049.RAA10279@harmony.village.org> To: Andy Farkas Subject: Re: PAIN Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 30 Jan 2000 11:39:25 +1100." References: Date: Sat, 29 Jan 2000 17:49:34 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Andy Farkas writes: : This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and : both src and obj on the same local disk (softupdates enabled): I'm doing this over NFS and only have 12MB of RAM. : Script done on Thu Jan 20 16:22:31 2000 : Script started on Thu Jan 20 01:01:00 2000 15:21:31. Hmmm, no wonder things have been taking a while... The crypto file that's building now has been going for about 15 minutes now... I think that I'll get my whole week at this rate. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 16:54:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id 7F7BE15840 for ; Sat, 29 Jan 2000 16:54:47 -0800 (PST) (envelope-from trouble@netquick.net) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=netquick.net) by bekool.com with esmtp (Exim 3.03 #1) id 12EjDs-00005c-00; Sat, 29 Jan 2000 20:32:16 -0500 Message-ID: <38938E12.92EF9ABE@netquick.net> Date: Sat, 29 Jan 2000 20:04:18 -0500 From: TrouBle Reply-To: trouble@netquick.net X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Andy Farkas , current@FreeBSD.ORG Subject: Re: PAIN References: <200001300049.RAA10279@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just imagine, too bad its not an 8086 or a 286 prolly take a month or so..... Warner Losh wrote: > In message Andy Farkas writes: > : This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and > : both src and obj on the same local disk (softupdates enabled): > > I'm doing this over NFS and only have 12MB of RAM. > > : Script done on Thu Jan 20 16:22:31 2000 > : Script started on Thu Jan 20 01:01:00 2000 > > 15:21:31. Hmmm, no wonder things have been taking a while... > > The crypto file that's building now has been going for about 15 > minutes now... > > I think that I'll get my whole week at this rate. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 17:43:46 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id DF1AD14F06; Sat, 29 Jan 2000 17:43:43 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id CD0CD1CD66A for ; Sat, 29 Jan 2000 17:43:43 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 29 Jan 2000 17:43:43 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: kernel breakage from ipfw6? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I get this whenever I try and build a kernel (with or without IPFIREWALL): linking kernel.debug ip6_fw.o: In function `ip6_fw_init': /sys/compile/MORDEN/../../netinet6/ip6_fw.c(.text+0x18a4): undefined reference to `ip6_fw_chk_ptr' /sys/compile/MORDEN/../../netinet6/ip6_fw.c(.text+0x18ae): undefined reference to `ip6_fw_ctl_ptr' *** Error code 1 1 error I've just verified my sources are up-to-date from cvsup3. Kernel config: #$Id: GENERIC,v 1.130 1998/11/03 22:01:21 des Exp $ machine i386 cpu I586_CPU ident MORDEN maxusers 32 makeoptions DEBUG="-g" #Build kernel with gdb(1) debug symbols options INCLUDE_CONFIG_FILE # Include this file in kernel options MAXMEM="(48*1024)" options COMPAT_43 options USER_LDT #allow user-level control of i386 ldt options CPU_FASTER_5X86_FPU options CLK_USE_I8254_CALIBRATION options CLK_USE_TSC_CALIBRATION options MSGBUF_SIZE=65536 options SYSVSHM options SYSVSEM options SYSVMSG options INVARIANTS options INVARIANT_SUPPORT options MD5 options VESA # needs VM86 defined too!! options DDB options KTRACE #kernel tracing options UCONSOLE options INET #Internet communications protocols options INET6 options IPSEC #IP security options IPSEC_ESP #IP security (crypto; define w/ IPSEC) options IPSEC_IPV6FWD #IP security tunnel for IPv6 options IPSEC_DEBUG #debug for IP security options PPP_FILTER #enable bpf filtering (needs bpfilter) options PPP_DEFLATE #PPP zlib/deflate/gzip support options IPFIREWALL #firewall options IPFIREWALL_VERBOSE #print information about dropped #packets #options IPFILTER #options IPFILTER_LOG options ICMP_BANDLIM options FFS #Fast filesystem options MFS #Memory File System options NFS #Network File System options MSDOSFS #MS DOS File System options PROCFS #Process filesystem options FFS_ROOT #FFS usable as root device options SOFTUPDATES options NSWAPDEV=4 options MAXCONS=12 # number of virtual consoles options SC_HISTORY_SIZE=200 # number of history buffer lines options COMPAT_LINUX options P1003_1B options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L options TCP_RESTRICT_RST options TCP_DROP_SYNFIN options ICMP_BANDLIM pseudo-device loop #Network loopback device pseudo-device bpf 4 #Berkeley packet filter pseudo-device tun 2 #Tunnel driver (user process ppp(8) pseudo-device ppp 2 pseudo-device pty 32 #Pseudo ttys - can go as high as 256 pseudo-device speaker #Play IBM BASIC-style noises out your speaker pseudo-device gzip #Exec gzipped a.out's pseudo-device vn #Vnode driver (turns a file into a device) pseudo-device snp 1 #Snoop device - to look at pty/vty/etc.. pseudo-device splash #device pnp0 device isa0 device pci0 device npx0 at nexus? port IO_NPX flags 0x0 irq 13 device ata0 device atadisk0 device atapicd0 options ATA_STATIC_ID device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device scbus0 #base SCSI code device cd0 #SCSI CD-ROMs device pass0 #CAM passthrough driver device ahc0 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device pcm0 device sbc0 device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts device sc0 at isa? ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 18:11:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.254.39]) by hub.freebsd.org (Postfix) with ESMTP id D9B11152A6; Sat, 29 Jan 2000 18:10:47 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id VAA20290; Sat, 29 Jan 2000 21:10:43 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38939DA2.6338F922@acm.org> Date: Sat, 29 Jan 2000 21:10:42 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: kernel breakage from ipfw6? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The problem here is that ip6_fw.c is dependent upon INET6 instead of IPv6FIREWALL. I sent mail to shin a little while ago about the problem. If you want to compile a kernel in the interim, change the line for ip6_fw.c in sys/conf/files to netinet6/ip6_fw.c optional ipv6firewall I believe this is the correct fix in any case. Jim Bloom bloom@acm.org Kris Kennaway wrote: > > I get this whenever I try and build a kernel (with or without IPFIREWALL): > > linking kernel.debug > ip6_fw.o: In function `ip6_fw_init': > /sys/compile/MORDEN/../../netinet6/ip6_fw.c(.text+0x18a4): undefined reference to `ip6_fw_chk_ptr' > /sys/compile/MORDEN/../../netinet6/ip6_fw.c(.text+0x18ae): undefined reference to `ip6_fw_ctl_ptr' > *** Error code 1 > 1 error > > I've just verified my sources are up-to-date from cvsup3. Kernel config: > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 19:17:49 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 51A1D14FE1; Sat, 29 Jan 2000 19:17:47 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 3F5931CD80C for ; Sat, 29 Jan 2000 19:17:47 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 29 Jan 2000 19:17:47 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: USE_OPENSSL update (READ ME!) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm hearing precious little feedback about this, guys. I need to know if this works properly on your 3.x and 4.0 systems so I can get it into the tree in time for the ports freeze. This version fixes rsaref support for non-4.0 systems and has a different hack for the CFLAGS problem if we don't use a configure script. This has only been necessary so far for pipsecd and seems to fix the problem there. New patched ports (see http://www.freebsd.org/~kris/openssl): w3m-ssl pipsecd (updated) Kris Index: Mk/bsd.port.mk =================================================================== RCS file: /home/ncvs/ports/Mk/bsd.port.mk,v retrieving revision 1.326 diff -u -r1.326 bsd.port.mk --- Mk/bsd.port.mk 2000/01/21 11:08:06 1.326 +++ Mk/bsd.port.mk 2000/01/30 01:45:15 @@ -571,6 +571,47 @@ PREFIX?= ${LOCALBASE} .endif +.if defined(USE_OPENSSL) +.if ${OSVERSION} >= 400014 && exists(/usr/lib/libcrypto.a) +.if ${USE_OPENSSL} == RSA +_HASRSA= "`/usr/bin/nm /usr/lib/libcrypto.a | /usr/bin/grep RSA_free`" +.if empty(_HASRSA) +.BEGIN: + @${ECHO} "This port requires RSA crypto, which is not present in your" + @${ECHO} "version of OpenSSL. Please see Chapter XX in the FAQ for" + @${ECHO} "a description of the problem and alternative solutions." + @${FALSE} +.endif +.endif +OPENSSLBASE= /usr +OPENSSLDIR= /etc/ssl +# OpenSSL in the base system doesn't include IDEA for patent reasons. +OPENSSL_IDEA= no +# XXX Might not valways work - this is a hack +.if defined(HAS_CONFIGURE) +CFLAGS+= -DNO_IDEA +.else +OPENSSL_CFLAGS+=-DNO_IDEA +MAKE_ARGS+= OPENSSL_CFLAGS="${OPENSSL_CFLAGS}" +.endif +.else +LIB_DEPENDS+= crypto.1:${PORTSDIR}/security/openssl +OPENSSLBASE?= ${LOCALBASE} +OPENSSLDIR?= ${OPENSSLBASE}/openssl +.endif +.if ${USE_OPENSSL} == RSA && defined(USA_RESIDENT) && ${USA_RESIDENT} == YES +LIB_DEPENDS+= rsaref.2:${PORTSDIR}/security/rsaref +# We set this so ports can decide whether or not to link against librsaref +# and libRSAglue +OPENSSL_RSAREF= yes +.endif +OPENSSLLIB= ${OPENSSLBASE}/lib +OPENSSLINC= ${OPENSSLBASE}/include +MAKE_ENV+= OPENSSLLIB=${OPENSSLLIB} OPENSSLINC=${OPENSSLINC} \ + OPENSSLBASE=${OPENSSLBASE} OPENSSLDIR=${OPENSSLDIR} +RESTRICTED= "Contains cryptography." +.endif + .endif # End of pre-makefile section. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 19:18:54 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 5409B14F82; Sat, 29 Jan 2000 19:18:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 43E621CD80C for ; Sat, 29 Jan 2000 19:18:53 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 29 Jan 2000 19:18:53 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Subject: Re: USE_OPENSSL update (READ ME!) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ack, this was meant for ports, although the additional testing would certainly be welcome :) Sorry.. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 19:29:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 971231555C for ; Sat, 29 Jan 2000 19:29:37 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 74FDA137FB3 for ; Sat, 29 Jan 2000 22:29:30 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id WAA09656; Sat, 29 Jan 2000 22:29:31 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14483.45082.151986.340011@trooper.velocet.net> Date: Sat, 29 Jan 2000 22:29:30 -0500 (EST) To: freebsd-current@freebsd.org Subject: Printer fiascos. X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why is it that a properly functioning printer is such a moving target in FreeBSD? I don't mean to be argumentative, but under 3.x, the magic cookie to make printers work (it appeared to be a flow control problem) was to change device ppc0 at isa? port? flags 0x40 net irq 7 to device ppc0 at isa? port? flags 0x40 tty irq 7 Now... I've upgraded to -CURRENT, and it has a much more serious problem. The line now reads device ppc0 at isa? port? irq 7 ... so I havn't tried putting net or tty in it, but I have a printer with a particular problem --- it will often fail to pick up a sheet of paper. I suspect that this sets the paper out sense line of the parallel port (?). When this happens, the entire machine freezes until someone feeds the printer --- the momment it starts printing again, the computer unfreezes. Printer-port related things probe as: ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP Probing for PnP devices on ppbus0: ppbus0: PCL,MLC,PML lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ppi0: on ppbus0 (I have tried putting the BIOS in different parallel port modes.) Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 19:43:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id C9D5414F15 for ; Sat, 29 Jan 2000 19:42:58 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA55929; Sun, 30 Jan 2000 14:12:45 +1030 (CST) Date: Sun, 30 Jan 2000 14:12:45 +1030 From: Greg Lehey To: TrouBle Cc: Warner Losh , Andy Farkas , current@FreeBSD.ORG Subject: Re: PAIN Message-ID: <20000130141245.C55643@freebie.lemis.com> References: <200001300049.RAA10279@harmony.village.org> <38938E12.92EF9ABE@netquick.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <38938E12.92EF9ABE@netquick.net> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 29 January 2000 at 20:04:18 -0500, TrouBle wrote: > Just imagine, too bad its not an 8086 or a 286 prolly take a month or so..... > > > Warner Losh wrote: > >> In message Andy Farkas writes: >> : This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and >> : both src and obj on the same local disk (softupdates enabled): >> >> I'm doing this over NFS and only have 12MB of RAM. >> >> : Script done on Thu Jan 20 16:22:31 2000 >> : Script started on Thu Jan 20 01:01:00 2000 >> >> 15:21:31. Hmmm, no wonder things have been taking a while... >> >> The crypto file that's building now has been going for about 15 >> minutes now... >> >> I think that I'll get my whole week at this rate. I did a make world on my PDP-11 yesterday. It took less than a day. But that's 2.11BSD. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 19:48:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 24F7514CC4 for ; Sat, 29 Jan 2000 19:48:30 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA19931; Sat, 29 Jan 2000 20:48:21 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA11507; Sat, 29 Jan 2000 20:48:29 -0700 (MST) Message-Id: <200001300348.UAA11507@harmony.village.org> To: Greg Lehey Subject: Re: PAIN Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 30 Jan 2000 14:12:45 +1030." <20000130141245.C55643@freebie.lemis.com> References: <20000130141245.C55643@freebie.lemis.com> <200001300049.RAA10279@harmony.village.org> <38938E12.92EF9ABE@netquick.net> Date: Sat, 29 Jan 2000 20:48:29 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20000130141245.C55643@freebie.lemis.com> Greg Lehey writes: : I did a make world on my PDP-11 yesterday. It took less than a day. : But that's 2.11BSD. Turns out that 12MB + 30MB of swap isn't enough to build world. I ran out of swap and the machine rebooted (at least that's what I think happened, since it silently rebooted). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 19:49: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from holly.dyndns.org (adsl-216-62-157-60.dsl.hstntx.swbell.net [216.62.157.60]) by hub.freebsd.org (Postfix) with ESMTP id B0CD014D01 for ; Sat, 29 Jan 2000 19:48:59 -0800 (PST) (envelope-from chris@holly.dyndns.org) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id VAA23213; Sat, 29 Jan 2000 21:49:41 -0600 (CST) (envelope-from chris) Date: Sat, 29 Jan 2000 21:49:40 -0600 From: Chris Costello To: David Gilbert Cc: freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. Message-ID: <20000129214940.J10669@holly.calldei.com> Reply-To: chris@calldei.com References: <14483.45082.151986.340011@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.4i In-Reply-To: <14483.45082.151986.340011@trooper.velocet.net> X-URL: http://www.FreeBSD.org/~chris/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, January 29, 2000, David Gilbert wrote: > When this happens, the entire machine freezes until someone feeds the > printer --- the momment it starts printing again, the computer > unfreezes. Could it be a printer-specific (or printer-compatibility) problem? My HP DeskJet 880C does not have that problem at all: ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE/ECP Probing for PnP devices on ppbus0: ppbus0: MLC,PCL,PML plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 -- |Chris Costello |Earn cash in your spare time -- blackmail friends. `-------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 19:50:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from gizmo.internode.com.au (gizmo.internode.com.au [192.83.231.115]) by hub.freebsd.org (Postfix) with ESMTP id BE8A814D0A for ; Sat, 29 Jan 2000 19:50:44 -0800 (PST) (envelope-from newton@gizmo.internode.com.au) Received: (from newton@localhost) by gizmo.internode.com.au (8.9.3/8.9.3) id OAA42954; Sun, 30 Jan 2000 14:19:17 +1030 (CST) (envelope-from newton) Date: Sun, 30 Jan 2000 14:19:16 +1030 From: Mark Newton To: Greg Lehey Cc: TrouBle , Warner Losh , Andy Farkas , current@FreeBSD.ORG Subject: Re: PAIN Message-ID: <20000130141916.A42942@internode.com.au> References: <200001300049.RAA10279@harmony.village.org> <38938E12.92EF9ABE@netquick.net> <20000130141245.C55643@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <20000130141245.C55643@freebie.lemis.com> X-PGP-Key: http://www.on.net/~newton/pgpkey.txt Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 30, 2000 at 02:12:45PM +1030, Greg Lehey wrote: > On Saturday, 29 January 2000 at 20:04:18 -0500, TrouBle wrote: > > Just imagine, too bad its not an 8086 or a 286 prolly take a month or so..... > > I did a make world on my PDP-11 yesterday. It took less than a day. ... to parse the Makefile :-) - mark -- Mark Newton Email: newton@internode.com.au (W) Network Engineer Email: newton@atdot.dotat.org (H) Internode Systems Pty Ltd Desk: +61-8-82232999 "Network Man" - Anagram of "Mark Newton" Mobile: +61-416-202-223 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 19:56:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id F0B53160DC for ; Sat, 29 Jan 2000 19:56:00 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id OAA56066; Sun, 30 Jan 2000 14:26:08 +1030 (CST) Date: Sun, 30 Jan 2000 14:26:08 +1030 From: Greg Lehey To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: PAIN Message-ID: <20000130142608.F55643@freebie.lemis.com> References: <20000130141245.C55643@freebie.lemis.com> <200001300049.RAA10279@harmony.village.org> <38938E12.92EF9ABE@netquick.net> <20000130141245.C55643@freebie.lemis.com> <200001300348.UAA11507@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001300348.UAA11507@harmony.village.org> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 29 January 2000 at 20:48:29 -0700, Warner Losh wrote: > In message <20000130141245.C55643@freebie.lemis.com> Greg Lehey writes: > : I did a make world on my PDP-11 yesterday. It took less than a day. > : But that's 2.11BSD. > > Turns out that 12MB + 30MB of swap isn't enough to build world. I ran > out of swap and the machine rebooted (at least that's what I think > happened, since it silently rebooted). [123] root--> uname -a 2.11BSD pdp11.lemis.com 2.11BSD 2.11 BSD UNIX #3: Sat Mar 7 15:25:50 CST 1998 root@pdp11.lemis.com:/usr/src/sys/GRANDPA PDP11 [124] root--> pstat -s 15/103 swapmap entries 845 kbytes swap used, 7514 kbytes free Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 19:59:11 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 73E2C15A16; Sat, 29 Jan 2000 19:59:10 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 5D8421CD812; Sat, 29 Jan 2000 19:59:10 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 29 Jan 2000 19:59:10 -0800 (PST) From: Kris Kennaway To: Jim Bloom Cc: current@FreeBSD.ORG Subject: Re: kernel breakage from ipfw6? In-Reply-To: <38939DA2.6338F922@acm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Jan 2000, Jim Bloom wrote: > The problem here is that ip6_fw.c is dependent upon INET6 instead of > IPv6FIREWALL. I sent mail to shin a little while ago about the > problem. If you want to compile a kernel in the interim, change the > line for ip6_fw.c in sys/conf/files to > > netinet6/ip6_fw.c optional ipv6firewall > > I believe this is the correct fix in any case. Thanks, this fixes it, but I have INET6 anyway.. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 19:59:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id A06F6157A6 for ; Sat, 29 Jan 2000 19:59:19 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 52C56137F6B; Sat, 29 Jan 2000 22:59:14 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id WAA10295; Sat, 29 Jan 2000 22:59:16 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14483.46867.83713.676590@trooper.velocet.net> Date: Sat, 29 Jan 2000 22:59:15 -0500 (EST) To: chris@calldei.com Cc: David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. In-Reply-To: <20000129214940.J10669@holly.calldei.com> References: <14483.45082.151986.340011@trooper.velocet.net> <20000129214940.J10669@holly.calldei.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Chris" == Chris Costello writes: Chris> On Saturday, January 29, 2000, David Gilbert wrote: >> When this happens, the entire machine freezes until someone feeds >> the printer --- the momment it starts printing again, the computer >> unfreezes. Chris> Could it be a printer-specific (or printer-compatibility) Chris> problem? My HP DeskJet 880C does not have that problem at all: To my mind, the printer shouldn't be able to hang the comptuer ... no matter what it does. My biggest problem is that it hangs the system. To your lack of problem, all I can say is that you might not have the conditions to notice it. To see the problem, you need the printer to fail to pick up paper (or to run out of paper) while the job is still being fed by the computer (does not count if the job is entirely within the printer when it runs out of paper). Now... I'm running LPRng, and it appears that only things printed by Samba clients (as opposed to local jobs which go through a gs filter first) hang the printer --- but this may be a red herring (that is all jobs might have the possibility to hang the printer, it's simply in our experience that lpr-submitted jobs havn't ... but then the sample of lpr jobs is very small compared to the sample of samba jobs). Regardless... the fact that the printer is hard to get working is a minor problem. The fact that it hangs the whole system is a MAJOR problem. (This is a real hard hang. Durning the hang no mouse/X response and no network (not even ping) response) When the printer is given paper, this problem disappears. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 20: 1:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id DA690158EE; Sat, 29 Jan 2000 20:01:10 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id NAA04949; Sun, 30 Jan 2000 13:00:58 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id NAA20209; Sun, 30 Jan 2000 13:00:57 +0900 (JST) Received: from localhost ([192.168.245.194]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id NAA20319; Sun, 30 Jan 2000 13:00:56 +0900 (JST) To: bloom@acm.org Cc: kris@hub.freebsd.org, current@FreeBSD.ORG Subject: Re: kernel breakage from ipfw6? In-Reply-To: <38939DA2.6338F922@acm.org> References: <38939DA2.6338F922@acm.org> X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000130130139F.shin@nd.net.fujitsu.co.jp> Date: Sun, 30 Jan 2000 13:01:39 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 20 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem here is that ip6_fw.c is dependent upon INET6 instead of > IPv6FIREWALL. I sent mail to shin a little while ago about the > problem. If you want to compile a kernel in the interim, change the > line for ip6_fw.c in sys/conf/files to > > netinet6/ip6_fw.c optional ipv6firewall > > I believe this is the correct fix in any case. > > Jim Bloom > bloom@acm.org > > Kris Kennaway wrote: > > > > I get this whenever I try and build a kernel (with or without IPFIREWALL): Thanks for checking it! I fixed and committed it. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 20:10: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 1D39A1585F for ; Sat, 29 Jan 2000 20:09:42 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id NAA11976; Sun, 30 Jan 2000 13:08:55 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id NAA13092; Sun, 30 Jan 2000 13:08:54 +0900 (JST) Received: from localhost ([192.168.245.5]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id NAA20477; Sun, 30 Jan 2000 13:08:53 +0900 (JST) To: pantzer@ludd.luth.se Cc: current@FreeBSD.ORG Subject: Re: INET6 and fxp In-Reply-To: <200001292103.WAA16257@queeg.ludd.luth.se> References: <200001292103.WAA16257@queeg.ludd.luth.se> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000130130931V.shin@nd.net.fujitsu.co.jp> Date: Sun, 30 Jan 2000 13:09:31 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 16 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have > a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for > FreeBSD on an OpenBSD mailinglist :-) > > http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html > > Something better than that is probably needed in the long run. Yes, I am trying to repeat it in my environment. (But it doesn't necessarily happens on all card which use fxp driver. Also, seems to happen with some delicate timing...) I heard that changing driver not to use interrupt is complete fix, though I am not so good at driver issue. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 20:21:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7495F14E1F for ; Sat, 29 Jan 2000 20:21:49 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA28556; Sat, 29 Jan 2000 20:21:33 -0800 (PST) (envelope-from dillon) Date: Sat, 29 Jan 2000 20:21:33 -0800 (PST) From: Matthew Dillon Message-Id: <200001300421.UAA28556@apollo.backplane.com> To: David Gilbert Cc: Peter Wemm , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. References: <14483.45082.151986.340011@trooper.velocet.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When the new parallel port stuff was put several months ago, my machine stopped working. I had to set flags to 0x40 to make it work again. Flags of 0x40 force the driver to use the most basic probes possible. It was put in because a number of people's machines stopped working. It looks like Peter removed the flags 0x40 in rev 1.228 of GENERIC on Jan 14. At the time I had an argument with the author who insisted that the correct way to force 'basic' probing of the printer was to set the flags field in GENERIC rather then make the default a basic probe. * Peter, the comment in your log message makes no mention of the reason * for removing the flags. If you did this by accident could you please * set the flags back to 0x40? Now, a huge number of changes have been made since the original problem was reported, so I could be puffing smoke here. I didn't see anything in the CVS logs, though, so I am assuming that the removal of the flags field was a mistake. David, try putting flags 0x40 back in and see if that fixes your problem. -Matt Matthew Dillon :Why is it that a properly functioning printer is such a moving target :in FreeBSD? : :I don't mean to be argumentative, but under 3.x, the magic cookie to :make printers work (it appeared to be a flow control problem) was to :change : :device ppc0 at isa? port? flags 0x40 net irq 7 : :to : :device ppc0 at isa? port? flags 0x40 tty irq 7 : :Now... I've upgraded to -CURRENT, and it has a much more serious :problem. The line now reads : :device ppc0 at isa? port? irq 7 : :... so I havn't tried putting net or tty in it, but I have a printer :with a particular problem --- it will often fail to pick up a sheet of :paper. I suspect that this sets the paper out sense line of the :parallel port (?). : :When this happens, the entire machine freezes until someone feeds the :printer --- the momment it starts printing again, the computer :unfreezes. : :Printer-port related things probe as: : :ppc0: at port 0x378-0x37f irq 7 on isa0 :ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode :ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP :Probing for PnP devices on ppbus0: :ppbus0: PCL,MLC,PML :lpt0: on ppbus0 :lpt0: Interrupt-driven port :plip0: on ppbus0 :ppi0: on ppbus0 : :(I have tried putting the BIOS in different parallel port modes.) : :Dave. : :-- :============================================================================ :|David Gilbert, Velocet Communications. | Two things can only be | :|Mail: dgilbert@velocet.net | equal if and only if they | :|http://www.velocet.net/~dgilbert | are precisely opposite. | :=========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 20:59:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from FreeBSD.org (ppp17-besancon.isdnet.net [195.154.11.224]) by hub.freebsd.org (Postfix) with ESMTP id A44D615431 for ; Sat, 29 Jan 2000 20:59:20 -0800 (PST) (envelope-from jmz@FreeBSD.org) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id GAA10115; Sun, 30 Jan 2000 06:00:03 +0100 (MET) (envelope-from jmz@FreeBSD.org) Date: Sun, 30 Jan 2000 06:00:03 +0100 (MET) Message-Id: <200001300500.GAA10115@qix.jmz.org> From: Jean-Marc Zucconi To: louie@TransSys.COM Cc: current@FreeBSD.org In-reply-to: <200001290007.TAA05379@whizzo.transsys.com> (louie@TransSys.COM) Subject: Re: new C++ compiler changes References: <200001290007.TAA05379@whizzo.transsys.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> Louis A Mamakos writes: > I just put a new -current on my test machine, and watched a bunch of stuff > fall over and die due to the new C++ implementation. > Is it possible to bump the revision of libstdc++ (and perhaps others) so > that existing programs can continue to function? I fear I will be > tracking down occasional broken C++ programs for days now. The solution I adopted is to keep the old libstdc++.so.3 and rename it libstdc++.so.1. Then you just have to modify your executable so that it looks for libstdc++.so.1 instead of libstdc++.so.3 (script below :-)) Jean-Marc #!/usr/bin/perl if (!$ARGV[0] || $ARGV[0] eq "-h") { print STDERR "usage: $0 file...\n"; exit 1; } foreach (@ARGV) { if (! -f $_) { print STDERR "$_: not found\n"; } else { ($s) = `file $_`; if ($s !~ /: ELF.*dynamically linked/) { print STDERR "$_: bad format\n$s"; } else { @h = `objdump -h $_`; $done = 0; foreach $s (@h) { if ($s =~ /dynstr/) { &edit ($_, $s); $done = 1; } } if (!$done) { print STDERR "$_: no .dynstr section\n"; } } } } sub edit { $f = shift; $_ = shift; split; $len = hex ($_[2]); $skip = hex ($_[5]); if (!open (F, $f)) { print STDERR "$f: $!\n"; return; } $n = sysread (F, $a, $skip); if ($n != $skip) { print STDERR "$f: short read\n"; return; } $n = sysread (F, $_, $len); if ($n != $len) { print STDERR "$f: short read\n"; return; } if (! /libstdc\+\+.so.3/) { print STDERR "$f: libstdc++.so.3 not used\n"; return; } s/libstdc\+\+.so.3/libstdc++.so.1/; if (!open (G, ">$f.1")) { print STDERR "can't create $f.1\n"; close F; return; } syswrite (G, $a, $skip); syswrite (G, $_, $len); while ($n != 0) { $n = sysread (F, $_, 100000); if ($n < 0) { print STDERR "$f: read error\n"; close F; close G; return; } if ($n != 0) { $w = syswrite (G, $_, $n); if ($n < $w) { print STDERR "$f.1: write error\n"; close F; close G; return; } } } close F; close G; system ("mv $f $f.backup && mv $f.1 $f"); } -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 21:11:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 237A214D8F for ; Sat, 29 Jan 2000 21:11:45 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 5AD87137FB9; Sun, 30 Jan 2000 00:11:42 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id AAA11808; Sun, 30 Jan 2000 00:11:48 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14483.51219.699735.212358@trooper.velocet.net> Date: Sun, 30 Jan 2000 00:11:47 -0500 (EST) To: "Sean O'Connell" Cc: David Gilbert , freebsd-current@freebsd.org Subject: Re: Printer fiascos. In-Reply-To: <20000129231001.D20014@stat.Duke.EDU> References: <14483.45082.151986.340011@trooper.velocet.net> <20000129225511.C20014@stat.Duke.EDU> <14483.47044.423477.356428@trooper.velocet.net> <20000129231001.D20014@stat.Duke.EDU> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Sean" == Sean O'Connell writes: Sean> On 2000 Jan 29, David Gilbert opined: >> >>>>> "Sean" == Sean O'Connell writes: >> Sean> lptcontrol -p >> I will try this. It still seems that there's a misfeature that it >> just doesn't work by default. Sean> Yep. It is odd that it completely locks your box waiting for Sean> paper. I have seen other printers which end up printing garbage Sean> after this but never a locked box. That's a different problem... That problem has something to do with flow control... and I've had that happen, too. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 21:16:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from kibby.knf.beldin.net (kibby.knf.beldin.net [203.38.198.130]) by hub.freebsd.org (Postfix) with ESMTP id 2404B15353 for ; Sat, 29 Jan 2000 21:16:48 -0800 (PST) (envelope-from kibbet@kibby.knf.beldin.net) Received: (from kibbet@localhost) by kibby.knf.beldin.net (8.9.3/8.9.3) id PAA14624 for current@freebsd.org; Sun, 30 Jan 2000 15:46:43 +1030 (CST) (envelope-from kibbet) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200001300348.UAA11507@harmony.village.org> Date: Sun, 30 Jan 2000 15:46:41 +1030 (CST) From: kibbet To: current@freebsd.org Subject: Re: PAIN Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Jan-00 Warner Losh wrote: > In message <20000130141245.C55643@freebie.lemis.com> Greg Lehey writes: >: I did a make world on my PDP-11 yesterday. It took less than a day. >: But that's 2.11BSD. > > Turns out that 12MB + 30MB of swap isn't enough to build world. I ran > out of swap and the machine rebooted (at least that's what I think > happened, since it silently rebooted). > > Warner > I tried on a 486dx66, 8mb 100mb swap (I forgot to take my medication that day).. At some stage I got the slient reboot aswell. So now world builds are happily crunching away on the p90 32mb which was sitting right next to it :) The p90 is actually in a NX (Neptune) chipset board, so once I source a 2nd p90 I'll be trying dual cpu builds :) /me looks at the bunch of 386 mobo's... lets not go there.. :) Kent Ibbetson kibbet@knfpub.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 21:23:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 7C6531577E for ; Sat, 29 Jan 2000 21:23:17 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id AAA47371; Sun, 30 Jan 2000 00:22:26 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 30 Jan 2000 00:22:26 -0500 (EST) From: Chuck Robey To: David Gilbert Cc: "Sean O'Connell" , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. In-Reply-To: <14483.51219.699735.212358@trooper.velocet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, David Gilbert wrote: > >>>>> "Sean" == Sean O'Connell writes: > > Sean> On 2000 Jan 29, David Gilbert opined: > >> >>>>> "Sean" == Sean O'Connell writes: > >> > Sean> lptcontrol -p > >> I will try this. It still seems that there's a misfeature that it > >> just doesn't work by default. > > Sean> Yep. It is odd that it completely locks your box waiting for > Sean> paper. I have seen other printers which end up printing garbage > Sean> after this but never a locked box. And notice it's not for everyone. I don't know why yours locks up and mine doesn't, but my printer, in the last month, has begun to occaisonally fail to pick up a sheet of paper. It stops the print, but nothing worse than that. I haven't really investigated it, and for me, since I don't see your problem, the fix is a couple of suitably applied alcohol wipes, probably. What I'm saying is, don't start trying to over-generalize your problem. It'll make it harder for you to find, and give FreeBSD an unnecessarily bad rep over that. BTW, that lptcontrol -p means you have something wrong with your parallel interface, because it's not responding to interrupts. This often means you have some IO card you forgot (like a sound card) sitting unbeknownst to you on IRQ 7, messing up the printer. The -p means it just polls the printer to pass in new characters, instead of reacting by interrupt. If the -p thing works for you, I would go looking at hardware, myself. Sheesh. This is a FreeBSD-questions type thing, not current. > > That's a different problem... That problem has something to do with > flow control... and I've had that happen, too. > > Dave. > > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 21:26:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from FreeBSD.org (ppp11-besancon.isdnet.net [195.154.11.218]) by hub.freebsd.org (Postfix) with ESMTP id 007FE15388 for ; Sat, 29 Jan 2000 21:26:44 -0800 (PST) (envelope-from jmz@FreeBSD.org) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id GAA00406; Sun, 30 Jan 2000 06:28:14 +0100 (MET) (envelope-from jmz@FreeBSD.org) Date: Sun, 30 Jan 2000 06:28:14 +0100 (MET) Message-Id: <200001300528.GAA00406@qix.jmz.org> From: Jean-Marc Zucconi To: current@FreeBSD.org Subject: Loader.rc: unknown command X-Mailer: Emacs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, With a new installed world I get this message at boot: > \ Loader.rc Loader.rc: unknown command Fortunately this does not prevent the machine to boot :-) Any clue? Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 21:40: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 0C2DA14F15; Sat, 29 Jan 2000 21:40:00 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id AAA22714; Sun, 30 Jan 2000 00:39:57 -0500 (EST) Date: Sun, 30 Jan 2000 00:39:57 -0500 (EST) From: Bosko Milekic To: Jean-Marc Zucconi Cc: current@FreeBSD.ORG Subject: Re: Loader.rc: unknown command In-Reply-To: <200001300528.GAA00406@qix.jmz.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, Jean-Marc Zucconi wrote: >Hi, > >With a new installed world I get this message at boot: > >> \ Loader.rc >Loader.rc: unknown command > >Fortunately this does not prevent the machine to boot :-) >Any clue? > >Jean-Marc Try rebuilding and re-installing the loader. ------------------------------------------------------------------------- | Bosko Milekic | Coffee vector: 1.0i+1.0j+1.0k | | Email: bmilekic@dsuper.net | Sleep vector: -1.0i-1.0j-1.0k | | WWW: http://pages.infinit.net/bmilekic/ | Resulting life: 0i+0j+0k (DNE)| ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 21:44:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id E94401505C; Sat, 29 Jan 2000 21:44:46 -0800 (PST) (envelope-from reg@shale.csir.co.za) Received: from granite.hip.berkeley.edu (granite.hip.berkeley.edu [136.152.155.25]) by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id HAA34152; Sun, 30 Jan 2000 07:44:37 +0200 (SAT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by granite.hip.berkeley.edu (8.9.3/8.9.3) id VAA61333; Sat, 29 Jan 2000 21:44:24 -0800 (PST) (envelope-from reg) Date: Sat, 29 Jan 2000 21:44:24 -0800 From: Jeremy Lea To: Jean-Marc Zucconi Cc: current@FreeBSD.ORG Subject: Re: Loader.rc: unknown command Message-ID: <20000129214424.A61314@shale.csir.co.za> References: <200001300528.GAA00406@qix.jmz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200001300528.GAA00406@qix.jmz.org>; from jmz@FreeBSD.ORG on Sun, Jan 30, 2000 at 06:28:14AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On Sun, Jan 30, 2000 at 06:28:14AM +0100, Jean-Marc Zucconi wrote: > With a new installed world I get this message at boot: > > > \ Loader.rc > Loader.rc: unknown command > > Fortunately this does not prevent the machine to boot :-) > Any clue? Me too! The loader.* files in /boot dont seem to be the latest ones from /usr/src/...??? -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22: 2:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta4.snfc21.pbi.net (mta4.snfc21.pbi.net [206.13.28.142]) by hub.freebsd.org (Postfix) with ESMTP id 00FA514BCD for ; Sat, 29 Jan 2000 22:02:15 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.215]) by mta4.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FP4001R9WQYOS@mta4.snfc21.pbi.net> for current@FreeBSD.ORG; Sat, 29 Jan 2000 22:01:53 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id DEBAF9151F; Sat, 29 Jan 2000 22:01:45 -0800 (PST) Date: Sat, 29 Jan 2000 22:01:45 -0800 (PST) From: Alex Zepeda Subject: Re: INET6 and fxp In-reply-to: <200001292103.WAA16257@queeg.ludd.luth.se> To: Mattias Pantzare Cc: current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Jan 2000, Mattias Pantzare wrote: > If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have > a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for > FreeBSD on an OpenBSD mailinglist :-) > > http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html > > Something better than that is probably needed in the long run. FWIW this doesn't happen with my card: fxp0: port 0x1000-0x103f mem 0xf4000000-0xf40 fffff,0xf4100000-0xf4100fff irq 10 at device 15.0 on pci0 fxp0: Ethernet address 00:90:27:d1:83:6a fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a fxp0: starting DAD for fe80:0001::0290:27ff:fed1:836a fxp0: DAD complete for fe80:0001::0290:27ff:fed1:836a - no duplicates found 'course I don't actually use the card for internet access, just a local lan and the occasional IPv6 testing. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22: 6:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id D914914ED9; Sat, 29 Jan 2000 22:06:11 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id BAA46567; Sun, 30 Jan 2000 01:06:02 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001300606.BAA46567@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 30 Jan 2000 01:06:02 -0500 (EST) From: John Baldwin To: Bruce Evans Subject: RE: More world breakage Cc: current@FreeBSD.org, committers@FreeBSD.org, Jeroen Ruigrok van der Werven Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Jan-00 Bruce Evans wrote: > On Fri, 28 Jan 2000, John Baldwin wrote: > >>... >> Solution: >> >> We need statically built install tools just like we have build tools. >> I think we should use the newer versions (i.e. static versions of the >> ones we just built under /usr/obj during buildworld that are linked >> against the new libraries), rather than doing some fancy footwork to > > Using the newer version would be even more broken, since they may be > for another arch, or may just use new syscalls that don't exist in the > host kernel. Hmm, ok. I think my terminology may have been poor. I meant that the new sources should have been used to build the tools, but using the existing machine headers/libraries to build the static binaries. One question though, what architecture *should* the install-tools be? Normally, one would run installworld on the target machine and not necessarily the host machine. For example, if I was cross-building an axp world on my x86 machine, then I would want to run 'make buildworld' on the x86, but would want to run 'make installworld' on the axp. Thus, the build tools in that case need to be x86 binaries, but the install tools need to be axp binaries. Of course, in that case you can't use the build machine's header files or libraries to build the install tools. Thus, you could use the headers/binaries in the source tree, except that you might then end up linking against a newer libc that needs a newer kernel to run. The other choice is to build the install tools during installworld using the target machine's headers/libraries, but then installworld would no longer be a read-only operation. :( >> make the existing binaries work. We already do this with the build >> tools. By using the newer binaries we only have to maintain one >> interface in our Makefiles to the install tools: whatever their >> current interface is in /usr/src. > > The build-tools are carefully built so that work in the host environment. > Essentially the same thing needs to be done for installation tools. Agreed. > Bruce -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:11:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta2.snfc21.pbi.net (mta2.snfc21.pbi.net [206.13.28.123]) by hub.freebsd.org (Postfix) with ESMTP id D86E2152F0 for ; Sat, 29 Jan 2000 22:11:35 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.215]) by mta2.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FP400364WVUDT@mta2.snfc21.pbi.net> for current@FreeBSD.ORG; Sat, 29 Jan 2000 22:04:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id A17779151F; Sat, 29 Jan 2000 22:04:42 -0800 (PST) Date: Sat, 29 Jan 2000 22:04:42 -0800 (PST) From: Alex Zepeda Subject: Re: PAIN In-reply-to: To: kibbet Cc: current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, kibbet wrote: > /me looks at the bunch of 386 mobo's... lets not go there.. :) /me looks at the stack of 386sx chips he has and wonders why no-one did 8 way SMP with these! - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:14:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id CDE8715260 for ; Sat, 29 Jan 2000 22:14:41 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id PAA20617; Sun, 30 Jan 2000 15:14:35 +0900 (JST) To: Alex Zepeda Cc: current@FreeBSD.ORG In-reply-to: jazepeda's message of Sat, 29 Jan 2000 22:01:45 PST. X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: INET6 and fxp From: itojun@iijlab.net Date: Sun, 30 Jan 2000 15:14:35 +0900 Message-ID: <20615.949212875@coconut.itojun.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >FWIW this doesn't happen with my card: > >fxp0: port 0x1000-0x103f mem 0xf4000000-0xf40 >fffff,0xf4100000-0xf4100fff irq 10 at device 15.0 on pci0 >fxp0: Ethernet address 00:90:27:d1:83:6a >fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a >fxp0: starting DAD for fe80:0001::0290:27ff:fed1:836a >fxp0: DAD complete for fe80:0001::0290:27ff:fed1:836a - no duplicates found > > >'course I don't actually use the card for internet access, just a local >lan and the occasional IPv6 testing. (from what I've heard) the symptom highly depends on chip revision so you are lucky. itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:18: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from coconut.itojun.org (coconut.itojun.org [210.160.95.97]) by hub.freebsd.org (Postfix) with ESMTP id E2F3814C2D for ; Sat, 29 Jan 2000 22:17:58 -0800 (PST) (envelope-from itojun@itojun.org) Received: from kiwi.itojun.org (localhost.itojun.org [127.0.0.1]) by coconut.itojun.org (8.9.3+3.2W/3.7W) with ESMTP id PAA20658; Sun, 30 Jan 2000 15:16:49 +0900 (JST) To: Yoshinobu Inoue Cc: current@FreeBSD.ORG In-reply-to: shin's message of Sun, 30 Jan 2000 13:09:31 JST. <20000130130931V.shin@nd.net.fujitsu.co.jp> X-Template-Reply-To: itojun@itojun.org X-Template-Return-Receipt-To: itojun@itojun.org X-PGP-Fingerprint: F8 24 B4 2C 8C 98 57 FD 90 5F B4 60 79 54 16 E2 Subject: Re: INET6 and fxp From: itojun@iijlab.net Date: Sun, 30 Jan 2000 15:16:49 +0900 Message-ID: <20656.949213009@coconut.itojun.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Yes, I am trying to repeat it in my environment. >(But it doesn't necessarily happens on all card which use fxp >driver. Also, seems to happen with some delicate timing...) >I heard that changing driver not to use interrupt is complete >fix, though I am not so good at driver issue. More precisely, "changing driver not to use interrupt during multicast filter setup". netbsd - fxp driver does not use interrupt during multicast filter setup so it is not affected openbsd - includes workaround in sys/net/if.c (as referenced in the thread) itojun To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:18: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 55DDE15388 for ; Sat, 29 Jan 2000 22:18:01 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 26629 invoked from network); 30 Jan 2000 06:17:25 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 30 Jan 2000 06:17:25 -0000 Date: Sun, 30 Jan 2000 17:17:22 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: _KPOSIX_VERSION=199309L in GENERIC is redundant In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Jan 2000, John Polstra wrote: > In revision 1.230 of src/sys/i386/conf/GENERIC, jkh added: > > options P1003_1B #Posix P1003_1B real-time extentions > options _KPOSIX_PRIORITY_SCHEDULING > options _KPOSIX_VERSION=199309L > > But I think the definition of _KPOSIX_VERSION is redundant, because it > is already the default in src/sys/sys/param.h: That particular definition is redundant, but we really ought to support POSIX.1-1996, and this support should not be optional. The ifdefs are messy enough when it is non-optional. It's a historical accident that some parts of the support (sys/posix4) are controlled by twisty mazes of options while other, larger parts (vfs_aio) are standard. sys/posix4 was developed in an optional module which hasn't been committed to FreeBSD, and twisty options are obviously required to putting some features in the kernel a proper and some in the module. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:23:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 4810315364; Sat, 29 Jan 2000 22:23:38 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p25-dnz01kiryunisiki.gunma.ocn.ne.jp [210.132.6.154]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id PAA07280; Sun, 30 Jan 2000 15:23:35 +0900 (JST) Message-ID: <3893D11E.B8F95AA6@newsguy.com> Date: Sun, 30 Jan 2000 14:50:22 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Jean-Marc Zucconi Cc: current@FreeBSD.ORG Subject: Re: Loader.rc: unknown command References: <200001300528.GAA00406@qix.jmz.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jean-Marc Zucconi wrote: > > With a new installed world I get this message at boot: > > > \ Loader.rc > Loader.rc: unknown command > > Fortunately this does not prevent the machine to boot :-) > Any clue? The \ command is not working correctly, resulting in the "Loader.rc" comment being executed instead of ignored. Why? I don't have a clue. Is *ANYONE* being able to reproduce this problem? If so, please contact me ASAP, since we have almost no time to fix this before 4.0-RELEASE. Jean, I need more information about your setup. What was it running before? How did you install this new world? Did you ever touch any file in /boot? Can you give me a date of your world source? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:24:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta2.snfc21.pbi.net (mta2.snfc21.pbi.net [206.13.28.123]) by hub.freebsd.org (Postfix) with ESMTP id 0D390160F3 for ; Sat, 29 Jan 2000 22:23:57 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.215]) by mta2.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FP400FT4XIAC1@mta2.snfc21.pbi.net> for current@FreeBSD.ORG; Sat, 29 Jan 2000 22:18:12 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id B179491515; Sat, 29 Jan 2000 22:18:10 -0800 (PST) Date: Sat, 29 Jan 2000 22:18:10 -0800 (PST) From: Alex Zepeda Subject: Re: INET6 and fxp In-reply-to: <20615.949212875@coconut.itojun.org> To: itojun@iijlab.net Cc: current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000 itojun@iijlab.net wrote: > > >FWIW this doesn't happen with my card: > > > >fxp0: port 0x1000-0x103f mem 0xf4000000-0xf40 > >fffff,0xf4100000-0xf4100fff irq 10 at device 15.0 on pci0 > >fxp0: Ethernet address 00:90:27:d1:83:6a > >fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a > >fxp0: starting DAD for fe80:0001::0290:27ff:fed1:836a > >fxp0: DAD complete for fe80:0001::0290:27ff:fed1:836a - no duplicates found > > > > > >'course I don't actually use the card for internet access, just a local > >lan and the occasional IPv6 testing. > > (from what I've heard) the symptom highly depends on chip revision > so you are lucky. As it seems it's also probably quite timing dependant too. Right now I'm glad I've only got one PCI card that is giving me a hard time. - alex who hates SIIGnificantly crappy IDE controllers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:24:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 7207B16169 for ; Sat, 29 Jan 2000 22:24:03 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p25-dnz01kiryunisiki.gunma.ocn.ne.jp [210.132.6.154]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id PAA07290; Sun, 30 Jan 2000 15:23:39 +0900 (JST) Message-ID: <3893D34D.7F9C90F6@newsguy.com> Date: Sun, 30 Jan 2000 14:59:41 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Chuck Robey Cc: David Gilbert , "Sean O'Connell" , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > > Sheesh. This is a FreeBSD-questions type thing, not current. I disagree. It is obvious that something is getting locked inside the kernel in his setup. This *SHOULDN'T* happen, it's that simple. If his machine locked whenever the printer went out of paper, and *stayed* locked, I'd be willing to believe the problem was caused by hardware. That's not what was reported. What was reported is rather (better) explained by some kernel code waiting indefinitely for an event, while preventing anything else from executing. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:34:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.254.39]) by hub.freebsd.org (Postfix) with ESMTP id EEFE71536D; Sat, 29 Jan 2000 22:34:46 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id BAA21660; Sun, 30 Jan 2000 01:34:45 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <3893DB84.C20BF3DE@acm.org> Date: Sun, 30 Jan 2000 01:34:44 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: John Baldwin Cc: Bruce Evans , current@FreeBSD.ORG, committers@FreeBSD.ORG, Jeroen Ruigrok van der Werven Subject: Re: More world breakage References: <200001300606.BAA46567@server.baldwin.cx> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the cross-build case, I would guess that the 'make installworld' could be run on either machine. It would depend upon which way the mounts are done. Is the host machine mounted on the target machine or the other way around. Some people strongly believe it should be one way or the other. Optimally, both cases should be handled correctly. Jim Bloom bloom@acm.org John Baldwin wrote: > > Hmm, ok. I think my terminology may have been poor. I meant that the > new sources should have been used to build the tools, but using the > existing machine headers/libraries to build the static binaries. One > question though, what architecture *should* the install-tools be? > Normally, one would run installworld on the target machine and not > necessarily the host machine. For example, if I was cross-building an > axp world on my x86 machine, then I would want to run 'make buildworld' > on the x86, but would want to run 'make installworld' on the axp. Thus, > the build tools in that case need to be x86 binaries, but the install > tools need to be axp binaries. Of course, in that case you can't use > the build machine's header files or libraries to build the install tools. > Thus, you could use the headers/binaries in the source tree, except that > you might then end up linking against a newer libc that needs a newer > kernel to run. The other choice is to build the install tools during > installworld using the target machine's headers/libraries, but then > installworld would no longer be a read-only operation. :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:41:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 1EAC81532C; Sat, 29 Jan 2000 22:41:32 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p19-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.148]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id PAA09569; Sun, 30 Jan 2000 15:41:30 +0900 (JST) Message-ID: <3893DB53.99DB7F46@newsguy.com> Date: Sun, 30 Jan 2000 15:33:55 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Jeremy Lea Cc: Jean-Marc Zucconi , current@FreeBSD.ORG Subject: Re: Loader.rc: unknown command References: <200001300528.GAA00406@qix.jmz.org> <20000129214424.A61314@shale.csir.co.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeremy Lea wrote: > > Me too! Then, please send me the same information: how did you upgrade? what did you have before? what's the date of your present world? > The loader.* files in /boot dont seem to be the latest ones from > /usr/src/...??? /boot/loader.rc does not get updated by "make world" (though a binary upgrade does update it). This was done to avoid overwritting people's loader.rc when loader.conf was first introduced. It would have been a real annoyance then, and the new loader.rc was such that we would not _need_ to update it afterwards. It was changed, I think, when I introduced the controversial password thingy, which I later decided to back out after I introduced some necessary changes to loader, which I haven't yet. So you are better off with the previous version anyway. :-) /boot/loader, /boot/loader.4th, /boot/support.4th and /boot/defaults/loader.conf should be updated, as well as a few other files which are not actually used during boot. Anyway... nothing can actually explain the problem reported. :-( In theory, it's impossible for such a problem to happen unless someone introduced a bug in loader/FICL (or managed to disable FICL altogether). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:46: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id CE211159CA for ; Sat, 29 Jan 2000 22:46:02 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX9912-Fujitsu Gateway) id PAA19235; Sun, 30 Jan 2000 15:44:57 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-9912-Fujitsu Domain Master) id PAA02666; Sun, 30 Jan 2000 15:44:56 +0900 (JST) Received: from localhost ([192.168.245.147]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-9912) id PAA23970; Sun, 30 Jan 2000 15:44:55 +0900 (JST) To: pantzer@ludd.luth.se Cc: current@FreeBSD.ORG Subject: Re: INET6 and fxp In-Reply-To: <200001292103.WAA16257@queeg.ludd.luth.se> References: <200001292103.WAA16257@queeg.ludd.luth.se> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000130154533T.shin@nd.net.fujitsu.co.jp> Date: Sun, 30 Jan 2000 15:45:33 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 13 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have > a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for > FreeBSD on an OpenBSD mailinglist :-) > > http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html > > Something better than that is probably needed in the long run. Let me confirm it. Does this also fix your problem on your freebsd-current? Cheers, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:46:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2411115361 for ; Sat, 29 Jan 2000 22:46:33 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p19-dn03kiryunisiki.gunma.ocn.ne.jp [210.232.224.148]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id PAA10213 for ; Sun, 30 Jan 2000 15:45:36 +0900 (JST) Message-ID: <3893DDED.64F0F859@newsguy.com> Date: Sun, 30 Jan 2000 15:45:01 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: current@freebsd.org Subject: loader.rc problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found the problem, it is called "src/sys/boot/i386/loader/Makefile revision 1.39: committer forgot to remove private changes before committing". I'll keep the guilty party's name unsaid to protect the innocents (huh?). -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 22:51:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from pozo.com (pozo.com [216.101.162.50]) by hub.freebsd.org (Postfix) with ESMTP id 5816615A46; Sat, 29 Jan 2000 22:51:25 -0800 (PST) (envelope-from mantar@pacbell.net) Received: from dual (dual.pozo.com [216.101.162.51]) by pozo.com (8.9.3/8.9.3) with ESMTP id WAA00245; Sat, 29 Jan 2000 22:50:50 -0800 (PST) (envelope-from mantar@pacbell.net) Message-Id: <4.2.2.20000129224859.00ab1ca0@pozo.com> X-Sender: null@pozo.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 29 Jan 2000 22:50:49 -0800 To: "Daniel C. Sobral" , Jean-Marc Zucconi From: Manfred Antar Subject: Re: Loader.rc: unknown command Cc: current@FreeBSD.ORG In-Reply-To: <3893D11E.B8F95AA6@newsguy.com> References: <200001300528.GAA00406@qix.jmz.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:50 PM 1/30/00 +0900, Daniel C. Sobral wrote: >Jean-Marc Zucconi wrote: > > > > With a new installed world I get this message at boot: > > > > > \ Loader.rc > > Loader.rc: unknown command > > > > Fortunately this does not prevent the machine to boot :-) > > Any clue? > >The \ command is not working correctly, resulting in the "Loader.rc" >comment being executed instead of ignored. > >Why? I don't have a clue. Is *ANYONE* being able to reproduce this >problem? If so, please contact me ASAP, since we have almost no time to >fix this before 4.0-RELEASE. > >Jean, I need more information about your setup. What was it running >before? How did you install this new world? Did you ever touch any file >in /boot? Can you give me a date of your world source? I'm seeing the same thing here with current world build as of a few minutes ago. I blew away /boot/* and reinstalled fresh still the same Manfred ===================== || mantar@pacbell.net || || Ph. (415) 681-6235 || ===================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 23: 2:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta1.snfc21.pbi.net (mta1.snfc21.pbi.net [206.13.28.122]) by hub.freebsd.org (Postfix) with ESMTP id 3528314E8A; Sat, 29 Jan 2000 22:59:37 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.103]) by mta1.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FP4007Q5Z86OJ@mta1.snfc21.pbi.net>; Sat, 29 Jan 2000 22:55:20 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 6B2F191515; Sat, 29 Jan 2000 22:55:18 -0800 (PST) Date: Sat, 29 Jan 2000 22:55:18 -0800 (PST) From: Alex Zepeda Subject: Re: Loader.rc: unknown command In-reply-to: <3893DB53.99DB7F46@newsguy.com> To: "Daniel C. Sobral" Cc: Jeremy Lea , Jean-Marc Zucconi , current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, Daniel C. Sobral wrote: > Then, please send me the same information: how did you upgrade? what did > you have before? what's the date of your present world? Make installworld, dunno but it was at least a few weeks old, and the present world was built last night. > Anyway... nothing can actually explain the problem reported. :-( In > theory, it's impossible for such a problem to happen unless someone > introduced a bug in loader/FICL (or managed to disable FICL altogether). I would vote for FICL bug, as I tried updating my "scripts" too, and that didn't solve my problem. Perhaps there's a bug in reading the file off the disk. Needless to say it works, but give that strange error/warning at the beginning. - alex Experience something different With our new imported dolly She's lovely, warm, inflatable And we guarantee her joy - The Police To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 23: 3: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 453AF152E1; Sat, 29 Jan 2000 23:00:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 306681CD475; Sat, 29 Jan 2000 23:00:09 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 29 Jan 2000 23:00:09 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Cc: kato@Freebsd.org Subject: identcpu.c change causes panic Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This commit causes my P5 to panic at boot: kato 2000/01/28 23:49:03 PST Modified files: sys/i386/i386 identcpu.c Log: Simplify messages of Pentium II, Pentium II Xeon, Celeron, Pentium III and Pentium III Xeon CPUs. If a CPU is one of Pentium II, Pentium II Xeon and Celeron, the message is always "Pentium II/Pentium II Xeon/Celeron". If a CPU is one of Pentium III and Pentium III Xeon, the message is always "Pentium III/Pentium III Xeon". Revision Changes Path 1.80 +5 -12 src/sys/i386/i386/identcpu.c Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #16: Sat Jan 29 22:48:36 PST 2000 kkenn@morden.rebel.net.au:/usr5/src2/src/sys/compile/MORDEN Timecounter "i8254" frequency 1193593 Hz Timecounter "TSC" frequency 120041220 Hz CPU: Pentium/P54C (120.04-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping = 5 Features=0x1bf ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Jan 29 23: 4:30 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 1EA2A15312; Sat, 29 Jan 2000 23:04:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id F3F451CD81A; Sat, 29 Jan 2000 23:04:24 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 29 Jan 2000 23:04:24 -0800 (PST) From: Kris Kennaway To: current@freebsd.org Cc: sos@freebsd.org Subject: Still problems with latest ATA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My CDROM still refuses to work with cdcontrol, although the 30-seconds of kernel spinning is now fixed. Trying to play a track gives: acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04 One of my WDC's still falls back to PIO mode at boot time (see previous messages, nothing has changed). If anything has changed in the verbose boot I can provide a copy of it, otherwise all my relevant details are in the archives from previous messages.. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message