From owner-freebsd-current Sun Aug 1 0:44:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id C7C8315070 for ; Sun, 1 Aug 1999 00:44:06 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id IAA65542; Sun, 1 Aug 1999 08:48:52 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 1 Aug 1999 08:48:52 +0100 (BST) From: Doug Rabson To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@freebsd.org Subject: Re: Assembler capable of supporting 3dnow! In-Reply-To: <199908010650.OAA13313@ariadne.tensor.pgs.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, 1 Aug 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > I'm messing around with the latest mesa and have discovered (suprise)that our > assembler doesn't support 3dnow instructions. Are there any plans to update to > a version of binutils that does? Linux's stuff appears to support it. I will import binutils-2.9.2 when it is released. I don't want to try to use an alpha-level patch to 2.9.1 in FreeBSD (since I don't have the time to spend debugging binutils). -- 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 Sun Aug 1 2:26:48 1999 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 654D914CD5 for ; Sun, 1 Aug 1999 02:26:42 -0700 (PDT) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.196.244]) by smtp05.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA43AD for ; Sun, 1 Aug 1999 11:25:36 +0200 Received: (from asmodai@localhost) by daemon.ninth-circle.org (8.9.3/8.9.3) id LAA04730 for current@freebsd.org; Sun, 1 Aug 1999 11:25:27 +0200 (CEST) (envelope-from asmodai) Date: Sun, 1 Aug 1999 11:25:27 +0200 From: Jeroen Ruigrok/Asmodai To: current@freebsd.org Subject: Audio notice Message-ID: <19990801112527.B4048@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, before the newbus changes I used to get a ton of: Sorry, read DMA channel unavailable. Now playing mp3's under CURRENT from yesterday I only get about three of those messages per 10 minutes. That's better ;) cheers! -- Jeroen Ruigrok van der Werven asmodai(at)wxs.nl The BSD Programmer's Documentation Project Network/Security Specialist BSD: Technical excellence at its best Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 7:21: 0 1999 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 6517114CAC for ; Sun, 1 Aug 1999 07:20:56 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id QAA19810 for ; Sun, 1 Aug 1999 16:19:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: current@freebsd.org Subject: junior-hacker task: "prepdisk" From: Poul-Henning Kamp Date: Sun, 01 Aug 1999 16:19:52 +0200 Message-ID: <19808.933517192@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that our new boot blocks doesn't like the taste of disks prepared according to the meagre information we have in the handbook. The following script seems to DTRT for me, and should really be either integrated into a "fdisk -A" flag or maybe as a stand alone script. Either way: manpage & handbook needs updated too. It will not make it to the top of my todo list in this geological period, so if somebody wants to pick up here I think a lot of people will come to appreciate it... Poul-Henning #!/bin/sh dev=fla0 grep "$dev.*sectors" /var/run/dmesg | tr -d '(:)' | awk ' { v = $3 c = $5 h = $7 s = $9 ss = c * h * s - s print "#",$0 > "_" print "g c"c" h"h" s"s > "_" print "p 1 165",s,ss > "_" print "a 1" > "_" print "#",$0 > "__" print "type: ESDI" > "__" print "disk:", $1 > "__" print "label:" > "__" print "flags:" > "__" print "bytes/sector: 512" > "__" print "sectors/track:", s > "__" print "tracks/cylinder:", h > "__" print "sectors/cylinder:", s * h > "__" print "cylinders:", c > "__" print "sectors/unit:", ss > "__" print "rpm: 3600" > "__" print "interleave: 1" > "__" print "trackskew: 0" > "__" print "cylinderskew: 0" > "__" print "headswitch: 0 # milliseconds" > "__" print "track-to-track seek: 0 # milliseconds" > "__" print "drivedata: 0 " > "__" print "8 partitions:" > "__" print "# size offset fstype [fsize bsize bps/cpg]" > "__" print "a:",ss,"0 4.2BSD 512 4096 " > "__" print "c:",ss,"0 unused 0 0" > "__" } ' fdisk -f _ -i -v $dev disklabel -BrR ${dev} __ newfs /dev/r${dev}a -- 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 Sun Aug 1 8:23:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (Postfix) with ESMTP id DEA5E14D46 for ; Sun, 1 Aug 1999 08:23:45 -0700 (PDT) (envelope-from green@FreeBSD.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.9.3/8.8.7) with ESMTP id LAA81513; Sun, 1 Aug 1999 11:23:15 -0400 (EDT) X-Authentication-Warning: janus.syracuse.net: green owned process doing -bs Date: Sun, 1 Aug 1999 11:23:15 -0400 (EDT) From: "Brian F. Feldman" X-Sender: green@janus.syracuse.net To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@FreeBSD.org Subject: Re: Assembler capable of supporting 3dnow! In-Reply-To: <199908010650.OAA13313@ariadne.tensor.pgs.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, 1 Aug 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > I'm messing around with the latest mesa and have discovered (suprise)that our > assembler doesn't support 3dnow instructions. Are there any plans to update to > a version of binutils that does? Linux's stuff appears to support it. > According to dfr, no, since the releases are in "beta" now or something. I think it's worth updating. And no, it would be too hard to get 3DNow! wihtouut updating gas. However: you can use the linux_devutils gcc/as/ld etc. to build the parts of whatever you need with 3dnow instructions. > > Stephen > -- > The views expressed above are not those of PGS Tensor. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Fundakowski Feldman _ __ ___ ____ ___ ___ ___ green@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 Aug 1 11: 1:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id 46DBC14BDC for ; Sun, 1 Aug 1999 11:01:13 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id UAA05953; Sun, 1 Aug 1999 20:01:12 +0200 (CEST) Date: Sun, 1 Aug 1999 20:01:12 +0200 (CEST) From: Martin Blapp To: freebsd-current@freebsd.org Cc: dillon@apollo.backplane.com Subject: mountpoint locking with fbsd-nfs 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 a little bit astonished that's now possible to mount via nfs several times at the same mountpoint with freebsd nfs clients: normal behaviour (Linux 2.2, Solaris): -------------------------------------- magma:/ # mount magma:/cdrom /mnt magma:/ # mount magma:/cdrom /mnt mount: magma:/cdrom already mounted or /mnt busy freebsd behaviour (stable and current): --------------------------------------- # mount magma:/cdrom /mnt # mount magma:/cdrom /mnt # mount magma:/cdrom /mnt #mount /dev/sd0s2a on / (NFS exported, local, soft-updates, writes: sync 9 async 1508) /dev/sd0s2e on /var (local, soft-updates, writes: sync 160 async 1695) procfs on /proc (local) magma:/cdrom on /mnt magma:/cdrom on /mnt magma:/cdrom on /mnt I think this is a very strange behaviour ... any ideas ? And as I know loopback mounts are not possible with fbsd. Am I mistaken ? Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 12:44: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 41AE414E06; Sun, 1 Aug 1999 12:43:54 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id VAA23130; Sun, 1 Aug 1999 21:43:50 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.2) id VAA80209; Sun, 1 Aug 1999 21:43:35 +0200 (CEST) (envelope-from andreas) Date: Sun, 1 Aug 1999 21:43:35 +0200 From: Andreas Klemm To: current@FreeBSD.ORG Cc: jmz@FreeBSD.ORG, nectar@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Kerberos 5, how to build whole system including X11R6 with it ? Message-ID: <19990801214335.A79922@titan.klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi ! Have a Cisco Router and want to play a bit with Kerberos support. As far as I know Cisco router support Kerberos 5 and I'm not sure, if it works with Kerberos 4 as well. So I though that it might perhaps be a good idea to re-build my FreeBSD 4.0 system and X11 with Kerberos5 support. Is it possible, to replace Kerberos4 support in FreeBSD with Kerberos 5 by simply defining KRB5_HOME=/usr in /etc/make.conf ? Would a make world then use Kerberos5 for FreeBSD ? Are the Kerberos 4 patches included in the XFree86 port Kerberos 4 specific or is there any chance to get it compiled and running with Kerberos 5 Support ??? What would you suggest ??? Try to replace systems Kerberos 4 with Kerberos 5 or build Kerberos 5 in /usr/local/krb5 like prepared in /etc/make.conf and then only link XFree86 with Kerberos 5 under /usr/local/krb5 (which surely make some patches necessary) ?! Thanks for any help Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Latest song from our band: http://www.freebsd.org/~andreas/mp3/schaukel.mp3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 12:57: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id 0C6B6150E5; Sun, 1 Aug 1999 12:56:50 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id VAA64225; Sun, 1 Aug 1999 21:55:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199908011955.VAA64225@gratis.grondar.za> To: Andreas Klemm Cc: current@FreeBSD.ORG, jmz@FreeBSD.ORG, nectar@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: Kerberos 5, how to build whole system including X11R6 with it ? Date: Sun, 01 Aug 1999 21:55:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have kerberos5 waiting in the wings for a compatible version (Heimdal will be coming out Real Soon Now). In the meanwhile - Kerberos 5 is available as a port, and as far as I know, X11R6.n K5 is broken, as it is based on a very early beta of MIT K5. M > Hi ! > > Have a Cisco Router and want to play a bit with Kerberos support. > As far as I know Cisco router support Kerberos 5 and I'm not sure, > if it works with Kerberos 4 as well. > > So I though that it might perhaps be a good idea to re-build my > FreeBSD 4.0 system and X11 with Kerberos5 support. > > Is it possible, to replace Kerberos4 support in FreeBSD with > Kerberos 5 by simply defining > KRB5_HOME=/usr > in /etc/make.conf ? > > Would a make world then use Kerberos5 for FreeBSD ? > > Are the Kerberos 4 patches included in the XFree86 port > Kerberos 4 specific or is there any chance to get it compiled > and running with Kerberos 5 Support ??? > > What would you suggest ??? Try to replace systems Kerberos 4 > with Kerberos 5 or build Kerberos 5 in /usr/local/krb5 like > prepared in /etc/make.conf and then only link XFree86 with > Kerberos 5 under /usr/local/krb5 (which surely make some > patches necessary) ?! > > Thanks for any help > > Andreas /// > > -- > Andreas Klemm http://www.FreeBSD.ORG/~andreas > http://www.freebsd.org/~fsmp/SMP/SMP.html > powered by Symmetric MultiProcessor FreeBSD > Latest song from our band: http://www.freebsd.org/~andreas/mp3/schaukel.mp3 -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 13:13:16 1999 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 B35A314C3E; Sun, 1 Aug 1999 13:13:10 -0700 (PDT) (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 VAA41613; Sun, 1 Aug 1999 21:04:41 +0100 (BST) (envelope-from nik) Date: Sun, 1 Aug 1999 21:04:41 +0100 From: Nik Clayton To: Poul-Henning Kamp Cc: current@freebsd.org Subject: Re: junior-hacker task: "prepdisk" Message-ID: <19990801210441.A41429@catkin.nothing-going-on.org> References: <19808.933517192@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19808.933517192@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Aug 01, 1999 at 04:19:52PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 01, 1999 at 04:19:52PM +0200, Poul-Henning Kamp wrote: > The following script seems to DTRT for me, and should really be > either integrated into a "fdisk -A" flag or maybe as a stand alone > script. Either way: manpage & handbook needs updated too. What, specifically, is wrong with them? N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 13:18:41 1999 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 A1DBE14CC2; Sun, 1 Aug 1999 13:18:35 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id WAA20906; Sun, 1 Aug 1999 22:17:45 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nik Clayton Cc: current@freebsd.org Subject: Re: junior-hacker task: "prepdisk" In-reply-to: Your message of "Sun, 01 Aug 1999 21:04:41 BST." <19990801210441.A41429@catkin.nothing-going-on.org> Date: Sun, 01 Aug 1999 22:17:44 +0200 Message-ID: <20904.933538664@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990801210441.A41429@catkin.nothing-going-on.org>, Nik Clayton writes: >On Sun, Aug 01, 1999 at 04:19:52PM +0200, Poul-Henning Kamp wrote: >> The following script seems to DTRT for me, and should really be >> either integrated into a "fdisk -A" flag or maybe as a stand alone >> script. Either way: manpage & handbook needs updated too. > >What, specifically, is wrong with them? Well, the suggested example in the handbook doesn't work for a boot disk, and if options or commands are added a manpage should be too :-) -- 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 Sun Aug 1 13:45:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from picalon.gun.de (picalon.gun.de [194.77.0.18]) by hub.freebsd.org (Postfix) with ESMTP id 6D91B14CC0; Sun, 1 Aug 1999 13:45:07 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id WAA24955; Sun, 1 Aug 1999 22:43:52 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.2) id WAA90795; Sun, 1 Aug 1999 22:23:29 +0200 (CEST) (envelope-from andreas) Date: Sun, 1 Aug 1999 22:23:29 +0200 From: Andreas Klemm To: Mark Murray Cc: Andreas Klemm , current@FreeBSD.ORG, jmz@FreeBSD.ORG, nectar@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: Kerberos 5, how to build whole system including X11R6 with it ? Message-ID: <19990801222329.B90770@titan.klemm.gtn.com> References: <199908011955.VAA64225@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908011955.VAA64225@gratis.grondar.za>; from Mark Murray on Sun, Aug 01, 1999 at 09:55:56PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Aug 01, 1999 at 09:55:56PM +0200, Mark Murray wrote: > I have kerberos5 waiting in the wings for a compatible version > (Heimdal will be coming out Real Soon Now). > > In the meanwhile - Kerberos 5 is available as a port, and as > far as I know, X11R6.n K5 is broken, as it is based on a very > early beta of MIT K5. Ok, then a good strategy would be to use version 4 now, try it with Cisos and wait for some time ... Thanks ! Have a nice day (or evening) Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Latest song from our band: http://www.freebsd.org/~andreas/mp3/schaukel.mp3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 14:33:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from freja.webgiro.com (freja.webgiro.com [212.209.29.10]) by hub.freebsd.org (Postfix) with ESMTP id CF08814DE0 for ; Sun, 1 Aug 1999 14:33:24 -0700 (PDT) (envelope-from abial@webgiro.com) Received: by freja.webgiro.com (Postfix, from userid 1001) id B82901911; Sun, 1 Aug 1999 23:33:11 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by freja.webgiro.com (Postfix) with ESMTP id B4FF749DD; Sun, 1 Aug 1999 23:33:11 +0200 (CEST) Date: Sun, 1 Aug 1999 23:33:07 +0200 (CEST) From: Andrzej Bialecki To: Jeroen Ruigrok/Asmodai Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: Panic plus advice needed In-Reply-To: <19990731121442.C378@daemon.ninth-circle.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, 31 Jul 1999, Jeroen Ruigrok/Asmodai wrote: > > No, just options DDB. > This bt was obtained after doing gdb -k kernel.0 vmcore.0 > I still have the DDB trace on paper which I can type in if needed/wanted. > > > What you do with the results depends a lot on what you find. On the > > whole, I wouldn't think it worth the pain of debugging without > > symbols. > > No it isn't... Another handful tricks of the trade: * if you still have exactly the same source tree and config file, recompile the kernel with -g to obtain the version with debugging symbols * if you managed to crash it once, you perhaps can do it again, but this time having the debugging kernel handy * if you can't for the life of you get the crash dump to examine what went wrong, do remember of remote GDB option under DDB - that is, if you have another machine with the same sources and kenel. But if the problem is repeatable you can prepare it beforehand... Remote GDB works miracles then. Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 18:39:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id 3C9B214C40; Sun, 1 Aug 1999 18:39:07 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id DAA87904; Mon, 2 Aug 1999 03:36:31 +0200 (CEST) To: Mark Murray Cc: Andreas Klemm , current@FreeBSD.ORG, jmz@FreeBSD.ORG, nectar@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: Kerberos 5, how to build whole system including X11R6 with it ? References: <199908011955.VAA64225@gratis.grondar.za> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 02 Aug 1999 03:36:30 +0200 In-Reply-To: Mark Murray's message of "Sun, 01 Aug 1999 21:55:56 +0200" Message-ID: <5lg1237yld.fsf@assaris.sics.se> Lines: 13 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray writes: > far as I know, X11R6.n K5 is broken, as it is based on a very > early beta of MIT K5. To many knowledge, the code that's in X11R6 is still based on a really old beta of MIT k5 and it would take some work to get it to work with some modern code. And besides, the protocol doesn't do what you want (IMNSHO), because it only authenticates the initial connection and doesn't do anything to authenticate or protect the X session after that. If somebody is working on adding some better mechanism of using K5 in X11 I would be interested. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 19: 8:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 1BB3D14C40; Sun, 1 Aug 1999 19:08:13 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id MAA23787; Mon, 2 Aug 1999 12:07:12 +1000 Date: Mon, 2 Aug 1999 12:07:12 +1000 From: Bruce Evans Message-Id: <199908020207.MAA23787@godzilla.zeta.org.au> To: current@FreeBSD.ORG, phk@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >It seems that our new boot blocks doesn't like the taste of disks >prepared according to the meagre information we have in the handbook. > >The following script seems to DTRT for me, and should really be >either integrated into a "fdisk -A" flag or maybe as a stand alone >script. Either way: manpage & handbook needs updated too. >... >#!/bin/sh > >dev=fla0 > >grep "$dev.*sectors" /var/run/dmesg | tr -d '(:)' | awk ' > { > v = $3 > c = $5 > h = $7 > s = $9 > ss = c * h * s - s > > print "#",$0 > "_" > print "g c"c" h"h" s"s > "_" > print "p 1 165",s,ss > "_" > print "a 1" > "_" > > print "#",$0 > "__" > print "type: ESDI" > "__" > print "disk:", $1 > "__" > print "label:" > "__" > print "flags:" > "__" > print "bytes/sector: 512" > "__" > print "sectors/track:", s > "__" > print "tracks/cylinder:", h > "__" > print "sectors/cylinder:", s * h > "__" > print "cylinders:", c > "__" > print "sectors/unit:", ss > "__" > print "rpm: 3600" > "__" > print "interleave: 1" > "__" > print "trackskew: 0" > "__" > print "cylinderskew: 0" > "__" > print "headswitch: 0 # milliseconds" > "__" > print "track-to-track seek: 0 # milliseconds" > "__" > print "drivedata: 0 " > "__" > print "8 partitions:" > "__" > print "# size offset fstype [fsize bsize bps/cpg]" > "__" > print "a:",ss,"0 4.2BSD 512 4096 " > "__" > print "c:",ss,"0 unused 0 0" > "__" > } >' >fdisk -f _ -i -v $dev >disklabel -BrR ${dev} __ >newfs /dev/r${dev}a This fails for SCSI disks, since the "sectors" line is formatted differently. The disklabel parts of it are mostly a bad way to write: disklabel -BrR ${dev} auto disklabel -e ${dev} # Editing steps in above disklabel -e: # (1) Change "type" to ESDI if it is an ESDI disk. It is a bug that # the wd driver doesn't set label.d_type = DTYPE_ESDI. The da # driver doesn't have this problem. # (2) Add "a:" and any other desired/required partitions. It is a # bug if the bootstrap can't find boot2 in the 'c' partition # where it has just been written. or disklabel /dev/r${dev} | sed ... | disklabel -BrR ${dev} /dev/stdin # Editing steps in the sed command are as above. All of the above only work for the easy case where the whole disk is being labelled. In general, the disk size must be reduced to the slice size before applying a label to a slice. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 19:42:43 1999 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 3A38614C8A; Sun, 1 Aug 1999 19:42:40 -0700 (PDT) (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.8.8) with ESMTP id TAA03275; Sun, 1 Aug 1999 19:39:46 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199908020239.TAA03275@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Assar Westerlund Cc: Mark Murray , Andreas Klemm , current@FreeBSD.ORG, jmz@FreeBSD.ORG, nectar@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: Kerberos 5, how to build whole system including X11R6 with it ? In-reply-to: Your message of "02 Aug 1999 03:36:30 +0200." <5lg1237yld.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Aug 1999 19:39:46 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would starrt by looking at the api and making the mods to X11R6 and if you can do a net search on xdm and kerberos -- there is an X11R6 xdm for kerberos 5 floating around. -- 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 Sun Aug 1 19:53:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id 0363C14C8A; Sun, 1 Aug 1999 19:53:17 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id EAA88008; Mon, 2 Aug 1999 04:53:32 +0200 (CEST) To: Amancio Hasty Cc: Mark Murray , Andreas Klemm , current@FreeBSD.ORG, jmz@FreeBSD.ORG, nectar@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: Kerberos 5, how to build whole system including X11R6 with it ? References: <199908020239.TAA03275@rah.star-gate.com> Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 02 Aug 1999 04:53:31 +0200 In-Reply-To: Amancio Hasty's message of "Sun, 01 Aug 1999 19:39:46 -0700" Message-ID: <5lr9lm51w4.fsf@assaris.sics.se> Lines: 12 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty writes: > I would starrt by looking at the api and making the mods to X11R6 No, the protocol used in the X11R6 code is wrong. You would need to design and implement a new one. > and if you can do a net search on xdm and kerberos -- there is an > X11R6 xdm for kerberos 5 floating around. That's quite different. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 20:17:50 1999 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 8877314C8F for ; Sun, 1 Aug 1999 20:17:31 -0700 (PDT) (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 VAA85355; Sun, 1 Aug 1999 21:15:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA00655; Sun, 1 Aug 1999 21:17:35 -0600 (MDT) Message-Id: <199908020317.VAA00655@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: sysinstall network performance Cc: "G. Adam Stanislav" , Dag-Erling Smorgrav , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Fri, 30 Jul 1999 02:59:22 +0900." <37A09679.88910EFD@newsguy.com> References: <37A09679.88910EFD@newsguy.com> <199907281524.LAA61875@dean.pc.sas.com> <199907281539.LAA09614@khavrinen.lcs.mit.edu> <379F4390.950D08FA@newsguy.com> <19990729125245.A224@whizkidtech.net> Date: Sun, 01 Aug 1999 21:17:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37A09679.88910EFD@newsguy.com> "Daniel C. Sobral" writes: : > Jordan exists. : : Don't go there. This whole existance-of-perl-scripts thingy is : dangerous territory. I've met jordan's cats, does that count :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 20:36:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id B258D14D88 for ; Sun, 1 Aug 1999 20:36:41 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA07214; Sun, 1 Aug 1999 20:19:50 -0700 (PDT) (envelope-from dillon) Date: Sun, 1 Aug 1999 20:19:50 -0700 (PDT) From: Matthew Dillon Message-Id: <199908020319.UAA07214@apollo.backplane.com> To: Martin Blapp Cc: freebsd-current@FreeBSD.ORG Subject: Re: mountpoint locking with fbsd-nfs References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm a little bit astonished that's now possible to mount via nfs :several times at the same mountpoint with freebsd nfs clients: : :normal behaviour (Linux 2.2, Solaris): :-------------------------------------- : :magma:/ # mount magma:/cdrom /mnt :magma:/ # mount magma:/cdrom /mnt :mount: magma:/cdrom already mounted or /mnt busy : :freebsd behaviour (stable and current): :--------------------------------------- : :# mount magma:/cdrom /mnt :# mount magma:/cdrom /mnt :# mount magma:/cdrom /mnt : :#mount :/dev/sd0s2a on / (NFS exported, local, soft-updates, writes: sync 9 async 1508) :/dev/sd0s2e on /var (local, soft-updates, writes: sync 160 async 1695) :procfs on /proc (local) :magma:/cdrom on /mnt :magma:/cdrom on /mnt :magma:/cdrom on /mnt : :I think this is a very strange behaviour ... any ideas ? And as I know :loopback mounts are not possible with fbsd. Am I mistaken ? : :Martin Well, theoretically there is nothing wrong going on since you can mount things on top of an NFS directory. Mount only complains about duplicate normal partition mounts because it can't open the buffered block device the second time. NFS doesn't care how many times a directory is imported or exported. -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 Aug 1 20:40:47 1999 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 1E7E514E48; Sun, 1 Aug 1999 20:40:42 -0700 (PDT) (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.8.8) with ESMTP id UAA03509; Sun, 1 Aug 1999 20:38:31 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199908020338.UAA03509@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Assar Westerlund Cc: Mark Murray , Andreas Klemm , current@FreeBSD.ORG, jmz@FreeBSD.ORG, nectar@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: Kerberos 5, how to build whole system including X11R6 with it ? In-reply-to: Your message of "02 Aug 1999 04:53:31 +0200." <5lr9lm51w4.fsf@assaris.sics.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Aug 1999 20:38:30 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Fine , take it up with the kerberos group over at MIT -- it is hard to believe that they would not have patches for X11R6 and proper protocol. > Amancio Hasty writes: > > I would starrt by looking at the api and making the mods to X11R6 > > No, the protocol used in the X11R6 code is wrong. You would need to > design and implement a new one. > > > and if you can do a net search on xdm and kerberos -- there is an > > X11R6 xdm for kerberos 5 floating around. > > That's quite different. > > /assar -- 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 Sun Aug 1 20:47:10 1999 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 C77D714D11 for ; Sun, 1 Aug 1999 20:47:07 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id WAA51467; Sun, 1 Aug 1999 22:47:12 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199908020347.WAA51467@celery.dragondata.com> Subject: Re: mountpoint locking with fbsd-nfs To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 1 Aug 1999 22:47:12 -0500 (CDT) Cc: blapp@attic.ch (Martin Blapp), freebsd-current@FreeBSD.ORG In-Reply-To: <199908020319.UAA07214@apollo.backplane.com> from "Matthew Dillon" at Aug 01, 1999 08:19:50 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 > Well, theoretically there is nothing wrong going on since you can mount > things on top of an NFS directory. Mount only complains about > duplicate normal partition mounts because it can't open the buffered > block device the second time. NFS doesn't care how many times a > directory is imported or exported. > > -Matt > Matthew Dillon > > > You sure about you can export a directory multiple times? I can't even export two directories under the same filesystem. su-2.03# mount /dev/wd0s1a on / (NFS exported, local, noatime, soft-updates, writes: sync 3945 async 1317317) procfs on /proc (local) su-2.03# cat /etc/exports /var home /var/tmp home su-2.03# mountd Aug 1 22:43:01 celery mountd[46042]: can't change attributes for /var/tmp Aug 1 22:43:01 celery mountd[46042]: bad exports list line /var/tmp home It actually exported /, which may not have been what i wanted. :) Or did I misunderstand you? Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 20:53:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 9389114F14 for ; Sun, 1 Aug 1999 20:53:12 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id XAA65204; Sun, 1 Aug 1999 23:52:42 -0400 (EDT) Message-Id: <199908020352.XAA65204@cs.rpi.edu> To: Kevin Day Cc: dillon@apollo.backplane.com (Matthew Dillon), blapp@attic.ch (Martin Blapp), freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: mountpoint locking with fbsd-nfs In-Reply-To: Message from Kevin Day of "Sun, 01 Aug 1999 22:47:12 CDT." <199908020347.WAA51467@celery.dragondata.com> Date: Sun, 01 Aug 1999 23:52:39 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To export a single filesystem multiple times, *all* of the attributes must be the same. If they aren't the only person you are fooling is yourself, since once a filesystem is NFS exported, it is open to the world. anyway the syntax for what you want is: /var /var/mail some.machine -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 20:55:41 1999 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 41B1214E7D for ; Sun, 1 Aug 1999 20:55:29 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id WAA61605; Sun, 1 Aug 1999 22:55:23 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199908020355.WAA61605@celery.dragondata.com> Subject: Re: mountpoint locking with fbsd-nfs To: crossd@cs.rpi.edu (David E. Cross) Date: Sun, 1 Aug 1999 22:55:23 -0500 (CDT) Cc: toasty@dragondata.com (Kevin Day), dillon@apollo.backplane.com (Matthew Dillon), blapp@attic.ch (Martin Blapp), freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu In-Reply-To: <199908020352.XAA65204@cs.rpi.edu> from "David E. Cross" at Aug 01, 1999 11:52:39 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 > > To export a single filesystem multiple times, *all* of the attributes must > be the same. If they aren't the only person you are fooling is yourself, > since once a filesystem is NFS exported, it is open to the world. > > anyway the syntax for what you want is: > > /var /var/mail some.machine > Ahh.. That was a bad example I gave anyway... I wanted to have say... /a exported to a few machines, and /b exported to only one machine... Couldn't do it, which was kinda annoying. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 20:58:40 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 5975914C21 for ; Sun, 1 Aug 1999 20:58:34 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA07543; Sun, 1 Aug 1999 20:57:30 -0700 (PDT) (envelope-from dillon) Date: Sun, 1 Aug 1999 20:57:30 -0700 (PDT) From: Matthew Dillon Message-Id: <199908020357.UAA07543@apollo.backplane.com> To: Kevin Day Cc: blapp@attic.ch (Martin Blapp), freebsd-current@FreeBSD.ORG Subject: Re: mountpoint locking with fbsd-nfs References: <199908020347.WAA51467@celery.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :You sure about you can export a directory multiple times? I can't even :export two directories under the same filesystem. : :su-2.03# mount :/dev/wd0s1a on / (NFS exported, local, noatime, soft-updates, writes: sync 3945 async 1317317) :procfs on /proc (local) :su-2.03# cat /etc/exports : :/var home :/var/tmp home :su-2.03# mountd :Aug 1 22:43:01 celery mountd[46042]: can't change attributes for /var/tmp :Aug 1 22:43:01 celery mountd[46042]: bad exports list line /var/tmp home : :It actually exported /, which may not have been what i wanted. :) : :Or did I misunderstand you? : :Kevin You misunderstood me. The problem you have is the fact that NFS exports are usually limited to the physical mount point of the filesystem being exported. Thus it thinks that /var above is the same as /, or that /var/tmp is the same as /var if both happen to be in the same partition. Mount gets confused by that when you specify what it believes to be the same partition several times in the exports list. You can use the '-alldirs' flag in the exports list to export a partition and allow any subdirectory within that partition to be mounted instead of the partition itself. There may be a way to export several specific subdirectories in the same partition but I'm not sure. I was talking about things like: mount apollo:/usr m1 mount apollo:/usr m2 mount apollo:/usr m3 mount apollo:/usr m3 mount apollo:/usr m3 I can import a filesystem as many times as I want, and even overlay mount 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 Aug 1 21: 1:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from users.anet-stl.com (users.anet-stl.com [209.145.150.20]) by hub.freebsd.org (Postfix) with ESMTP id 1F86714E83 for ; Sun, 1 Aug 1999 21:01:37 -0700 (PDT) (envelope-from doogie@anet-stl.com) Received: from earth.anet-stl.com (earth.anet-stl.com [209.83.128.12]) by users.anet-stl.com (8.9.3/8.8.5) with SMTP id XAA16187; Sun, 1 Aug 1999 23:01:01 -0500 (CDT) Date: Sun, 1 Aug 1999 23:01:01 -0500 (CDT) From: Jason Young To: Kevin Day Cc: Matthew Dillon , Martin Blapp , freebsd-current@FreeBSD.ORG Subject: Re: mountpoint locking with fbsd-nfs In-Reply-To: <199908020347.WAA51467@celery.dragondata.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 IIRC, mount permissions (i.e., what IP addresses, root UID mangling, etc) are set per filesystem. Given a filesystem structure like this: > df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 127023 27151 89711 23% / /dev/ccd0c 8321099 2391764 5263648 31% /home /dev/da0s1e 2032623 732806 1137208 39% /usr /dev/da1s1f 2032623 816051 1053963 44% /var /dev/ccd1c 4001742 1571210 2110393 43% /var/mail procfs 4 4 0 100% /proc You can only set IP addresses to be exported to and other options only once for the /usr filesystem, once for the /var filesystem, etc. This doesn't mean if I export /home/doogie to 192.168.40.1 that that IP address can mount /home. Mount still controls the mountpoints allowed. If you want to export multiple mountpoints of the same filesystem, you need to specify them all on one line with one options set. Like this: /home/doogie /home/joebob /home/luser -maproot=0:0 testbox.accessus.net Jason Young accessUS Chief Network Engineer PS: I just realized the manpage disagrees with this; it has multiple exports lines for the same filesystem. I believe the manpage is wrong, at least in that it doesn't reflect reality. Comments from anybody? On Sun, 1 Aug 1999, Kevin Day wrote: > > Well, theoretically there is nothing wrong going on since you can mount > > things on top of an NFS directory. Mount only complains about > > duplicate normal partition mounts because it can't open the buffered > > block device the second time. NFS doesn't care how many times a > > directory is imported or exported. > > > > -Matt > > Matthew Dillon > > > > > > > > You sure about you can export a directory multiple times? I can't even > export two directories under the same filesystem. > > su-2.03# mount > /dev/wd0s1a on / (NFS exported, local, noatime, soft-updates, writes: sync 3945 async 1317317) > procfs on /proc (local) > su-2.03# cat /etc/exports > > /var home > /var/tmp home > su-2.03# mountd > Aug 1 22:43:01 celery mountd[46042]: can't change attributes for /var/tmp > Aug 1 22:43:01 celery mountd[46042]: bad exports list line /var/tmp home > > > > It actually exported /, which may not have been what i wanted. :) > > Or did I misunderstand you? > > Kevin > > > 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 Aug 1 21: 8:35 1999 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 D3BA714E9F for ; Sun, 1 Aug 1999 21:08:30 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id XAA76817; Sun, 1 Aug 1999 23:08:16 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199908020408.XAA76817@celery.dragondata.com> Subject: Re: mountpoint locking with fbsd-nfs To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 1 Aug 1999 23:08:16 -0500 (CDT) Cc: toasty@dragondata.com (Kevin Day), blapp@attic.ch (Martin Blapp), freebsd-current@FreeBSD.ORG In-Reply-To: <199908020357.UAA07543@apollo.backplane.com> from "Matthew Dillon" at Aug 01, 1999 08:57:30 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 > > You misunderstood me. The problem you have is the fact that NFS exports > are usually limited to the physical mount point of the filesystem being > exported. Thus it thinks that /var above is the same as /, or that > /var/tmp is the same as /var if both happen to be in the same partition. > Mount gets confused by that when you specify what it believes to be the > same partition several times in the exports list. > > You can use the '-alldirs' flag in the exports list to export a partition > and allow any subdirectory within that partition to be mounted instead of > the partition itself. There may be a way to export several specific > subdirectories in the same partition but I'm not sure. > > I was talking about things like: > > mount apollo:/usr m1 > mount apollo:/usr m2 > mount apollo:/usr m3 > mount apollo:/usr m3 > mount apollo:/usr m3 > > I can import a filesystem as many times as I want, and even overlay mount > points. > Yeah, I know about -alldirs... The problem was that we had customers who wanted us to export their home directories, and unless I gave them their own filesystem, I couldn't restrict it in the manner i wanted. :) Just checking to see that I wasn't missing a way to do this. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 21:12:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 3B8A414E82 for ; Sun, 1 Aug 1999 21:12:29 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id VAA08088; Sun, 1 Aug 1999 21:12:03 -0700 (PDT) (envelope-from dillon) Date: Sun, 1 Aug 1999 21:12:03 -0700 (PDT) From: Matthew Dillon Message-Id: <199908020412.VAA08088@apollo.backplane.com> To: Kevin Day Cc: toasty@dragondata.com (Kevin Day), blapp@attic.ch (Martin Blapp), freebsd-current@FreeBSD.ORG Subject: Re: mountpoint locking with fbsd-nfs References: <199908020408.XAA76817@celery.dragondata.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Yeah, I know about -alldirs... The problem was that we had customers who :wanted us to export their home directories, and unless I gave them their own :filesystem, I couldn't restrict it in the manner i wanted. :) : :Just checking to see that I wasn't missing a way to do this. :) : :Kevin I've never in my life tried this - it probably won't work, but ... use the null device maybe to create a mount point for each home dir and then export that? -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 Aug 1 21:22:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 9665B14E82 for ; Sun, 1 Aug 1999 21:22:14 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (phoenix.cs.rpi.edu [128.113.96.153]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id AAA65570; Mon, 2 Aug 1999 00:21:46 -0400 (EDT) Message-Id: <199908020421.AAA65570@cs.rpi.edu> To: Jason Young Cc: Kevin Day , Matthew Dillon , Martin Blapp , freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: mountpoint locking with fbsd-nfs In-Reply-To: Message from Jason Young of "Sun, 01 Aug 1999 23:01:01 CDT." Date: Mon, 02 Aug 1999 00:21:43 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > IIRC, mount permissions (i.e., what IP addresses, root UID mangling, etc) > are set per filesystem. Given a filesystem structure like this: > > > df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 127023 27151 89711 23% / > /dev/ccd0c 8321099 2391764 5263648 31% /home > /dev/da0s1e 2032623 732806 1137208 39% /usr > /dev/da1s1f 2032623 816051 1053963 44% /var > /dev/ccd1c 4001742 1571210 2110393 43% /var/mail > procfs 4 4 0 100% /proc > > You can only set IP addresses to be exported to and other options only > once for the /usr filesystem, once for the /var filesystem, etc. > > This doesn't mean if I export /home/doogie to 192.168.40.1 that that IP > address can mount /home. Mount still controls the mountpoints allowed. > > If you want to export multiple mountpoints of the same filesystem, you > need to specify them all on one line with one options set. Like this: > > /home/doogie /home/joebob /home/luser -maproot=0:0 testbox.accessus.net > > Jason Young > accessUS Chief Network Engineer > > PS: I just realized the manpage disagrees with this; it has multiple > exports lines for the same filesystem. I believe the manpage is wrong, at > least in that it doesn't reflect reality. Comments from anybody? If you have /home as a filesystem and you export /home/userj to the machine 'foo'. 'foo', in reality has access to all of home, it is the reality of how NFS "works". In reflecting this, it kinda makes sense to place the access controls on the filesystem itself, since that is the only thing that is realistically determinable to the nfs "daemon" <-- term used lightly. I believe that it is OK to have the following: /usr -ro badhost /usr goodhost (as long as the permissions are not contradictory it is ok)... In fact we use that alot here. We run into problems here because we use netgroups and will have a single machine in multiple netgroups... ala: /share -ro freebsd3 /share trusted where trusted and freebsd3 share a couple of memebers, and the mountd chokes trying to resolve the conflict. -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 21:23:18 1999 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 2A2AA14BC9 for ; Sun, 1 Aug 1999 21:23:14 -0700 (PDT) (envelope-from toasty@celery.dragondata.com) Received: (from toasty@localhost) by celery.dragondata.com (8.9.3/8.9.3) id XAA95716; Sun, 1 Aug 1999 23:23:12 -0500 (CDT) (envelope-from toasty) From: Kevin Day Message-Id: <199908020423.XAA95716@celery.dragondata.com> Subject: Re: mountpoint locking with fbsd-nfs To: dillon@apollo.backplane.com (Matthew Dillon) Date: Sun, 1 Aug 1999 23:23:12 -0500 (CDT) Cc: toasty@dragondata.com (Kevin Day), blapp@attic.ch (Martin Blapp), freebsd-current@FreeBSD.ORG In-Reply-To: <199908020412.VAA08088@apollo.backplane.com> from "Matthew Dillon" at Aug 01, 1999 09:12:03 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 > > :Yeah, I know about -alldirs... The problem was that we had customers who > :wanted us to export their home directories, and unless I gave them their own > :filesystem, I couldn't restrict it in the manner i wanted. :) > : > :Just checking to see that I wasn't missing a way to do this. :) > : > :Kevin > > I've never in my life tried this - it probably won't work, but ... > use the null device maybe to create a mount point for each home > dir and then export that? > I think it sees through this. su-2.03# cat /etc/exports /var home /mnt home su-2.03# mount /dev/wd0s1a on / (NFS exported, local, noatime, soft-updates, writes: sync 3970 async 1321097) procfs on /proc (local) nfs:/home on /usr/home (noatime) nfs:/var/mail on /var/mail (noatime) /var/tmp on /mnt (local) su-2.03# mountd Aug 1 23:17:48 celery mountd[89177]: can't change attributes for /mnt That was a very good idea though, i'd never have thought of it. :) I'll have to play with this more. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 22:23:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles505.castles.com [208.214.165.69]) by hub.freebsd.org (Postfix) with ESMTP id 8ADD914E62; Sun, 1 Aug 1999 22:23:08 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA01494; Sun, 1 Aug 1999 22:17:52 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908020517.WAA01494@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: FreeBSD current users , FreeBSD Committers Subject: Re: Recent -CURRENT doesn't show process times on some hardware In-reply-to: Your message of "Sun, 01 Aug 1999 13:27:51 +0930." <19990801132751.S64532@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Aug 1999 22:17:51 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What makes this all the more puzzling is that it happens only on one > machine. Hint: it's a laptop (Dell Latitude CPi). panic is a normal > Pentium machine of no particular lineage. Does this ring a bell with > anybody? Do you have APM enabled? Do you have the "broken statclock" option enabled? Have you tried permuting these two? -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Sun Aug 1 22:26: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles505.castles.com [208.214.165.69]) by hub.freebsd.org (Postfix) with ESMTP id B1F6714EFE; Sun, 1 Aug 1999 22:25:54 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id WAA01521; Sun, 1 Aug 1999 22:20:38 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908020520.WAA01521@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Maxim Sobolev Cc: current@FreeBSD.ORG, jlemon@FreeBSD.ORG Subject: Re: APM related panic In-reply-to: Your message of "Sat, 31 Jul 1999 01:32:57 +0300." <37A22819.DD36695B@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Aug 1999 22:20:38 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jonathan; just some context, this is with your old 16-bit-protmode patches, spiffed up for -current, which I committed late last week. > Finally I back from my work, suped, builded kernel with APM_DEBUG and > managed to get my computer booted using serial console, however due to > unknown for me problem it works only in one direction, i.e. I see boot > messages on my notebook, but when I press any key on it it has absolutely no > effect. Also after panic cu on notebook is hanging, so I have to kill it. > Following is the log, bit if you think that it is not sufficien and I could > do something more to shade light on this proble please do not hesitate to > contact me. > > -Maxim > > > Script started on Sat Jul 31 00:56:04 1999 > sh-2.03# cu -l '/dev/cuaa0' > Connected. > Console: serial port > BIOS drive A: is disk0 > BIOS drive C: is disk1 > > FreeBSD/i386 bootstrap loader, Revision 0.7 640/64448kB > (root@home, Sun Jul 25 04:04:09 EEST 1999) > Booting [kernel]... > Copyright (c) 1992-1999 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #0: Sat Jul 31 00:29:40 EEST 1999 > root@home:/usr/src/sys/compile/MBSD > Timecounter "i8254" frequency 1193027 Hz > CPU: AMD-K6(tm) 3D processor (300.64-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x580 Stepping = 0 > Features=0x8001bf > AMD Features=0x80000800 > real memory = 67043328 (65472K bytes) > avail memory = 62607360 (61140K bytes) > Preloaded elf kernel "kernel" at 0xc0265000. > Probing for PnP devices: > CSN 1 Vendor ID: CTL0028 [0x28008c0e] Serial 0x1013c276 Comp ID: PNP0600 > [0x0006d041] > npx0: on motherboard > npx0: INT 16 interface > apm0: on motherboard > apm: APM BIOS version 0102 > apm: Code16 0xc00f0000, Data 0xc00fdfa0 > apm: Code entry 0x00008010, Idling CPU enabled, Management enabled > apm: CS_limit=0x0, DS_limit=0x0 These limits look pretty suspect, although the code segment below looks OK. > Fatal trap 9: general protection fault while in kernel mode > instruction pointer = 0x48:0x8034 > stack pointer = 0x10:0xc0279e98 > frame pointer = 0x10:0x67890000 > code segment = base 0xc00f0000, limit 0xffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 0 > processor eflags = interrupt enabled, resume, IOPL = 0 Why is IOPL zero? I've also noted that making a bios16 call also results in IOPL being zero (I have more that I want to take up with you on that at some stage, since it's got me stumped, but one thing at a time). Do I need to tweak something in the segment descriptors to change IOPL? -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Sun Aug 1 22:27:52 1999 Delivered-To: freebsd-current@freebsd.org Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by hub.freebsd.org (Postfix) with ESMTP id 6E0A614EFE for ; Sun, 1 Aug 1999 22:27:45 -0700 (PDT) (envelope-from blapp@attic.ch) Received: from bastian.attic.ch (bastian.attic.ch [194.235.45.178]) by bastian.attic.ch (8.9.1a/8.9.1a) with SMTP id HAA07086; Mon, 2 Aug 1999 07:26:12 +0200 (CEST) Date: Mon, 2 Aug 1999 07:26:12 +0200 (CEST) From: Martin Blapp To: Matthew Dillon Cc: freebsd-current@FreeBSD.ORG Subject: Re: mountpoint locking with fbsd-nfs In-Reply-To: <199908020319.UAA07214@apollo.backplane.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, 1 Aug 1999, Matthew Dillon wrote: > Well, theoretically there is nothing wrong going on since you can mount > things on top of an NFS directory. Mount only complains about > duplicate normal partition mounts because it can't open the buffered > block device the second time. NFS doesn't care how many times a > directory is imported or exported. Ok, theoretically there may be nothing wrong. But it is just not standard. And what sense could it have to mount on top of an existing mount-point a second time ? This could probably only happen by mistake. Martin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 23:16:57 1999 Delivered-To: freebsd-current@freebsd.org Received: from holonet.net (zen.holonet.net [198.207.169.5]) by hub.freebsd.org (Postfix) with ESMTP id 2C2AB14F57 for ; Sun, 1 Aug 1999 23:16:31 -0700 (PDT) (envelope-from adamw@holonet.net) Received: from DialupEudora (adamw@localhost) by holonet.net (Adam Wight) with SMTP id XAA11969; Sun, 1 Aug 1999 23:15:56 -0700 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 1 Aug 1999 22:16:15 -0800 To: freebsd-current@FreeBSD.org From: adamw@holonet.net (Adam Wight) Subject: PCMCIA drivers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just started hacking the zp driver to support the 3Com 3C562 dual-function ether/modem card, and I wanted to make sure I'm not duplicating effort. While I'm at it, there are two significant design issues that I could use input on: First, the current zp driver cannot be configured if the pccard services are being used, since it uses its own pccard code. Very Bad. Then, the PCMCIA model that we use now makes it impossible to use both functions of a doubly useful card. This too is Very Bad. Is anyone addressing these problems? -Adam Wight To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Aug 1 23:32:14 1999 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 AB2C714F6B for ; Sun, 1 Aug 1999 23:32:10 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA22730; Mon, 2 Aug 1999 08:30:52 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-reply-to: Your message of "Mon, 02 Aug 1999 12:07:12 +1000." <199908020207.MAA23787@godzilla.zeta.org.au> Date: Mon, 02 Aug 1999 08:30:52 +0200 Message-ID: <22728.933575452@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908020207.MAA23787@godzilla.zeta.org.au>, Bruce Evans writes: >All of the above only work for the easy case where the whole disk is >being labelled. In general, the disk size must be reduced to the slice >size before applying a label to a slice. And that is the problem, it seems that "dangerously dedicated" doesn't boot anymore... -- 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 Sun Aug 1 23:35:53 1999 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 4F78414F6B for ; Sun, 1 Aug 1999 23:35:46 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA22783; Mon, 2 Aug 1999 08:33:26 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: "Daniel C. Sobral" , "G. Adam Stanislav" , Dag-Erling Smorgrav , freebsd-current@FreeBSD.ORG Subject: Re: sysinstall network performance In-reply-to: Your message of "Sun, 01 Aug 1999 21:17:35 MDT." <199908020317.VAA00655@harmony.village.org> Date: Mon, 02 Aug 1999 08:33:26 +0200 Message-ID: <22781.933575606@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908020317.VAA00655@harmony.village.org>, Warner Losh writes: >In message <37A09679.88910EFD@newsguy.com> "Daniel C. Sobral" writes: >: > Jordan exists. >: >: Don't go there. This whole existance-of-perl-scripts thingy is >: dangerous territory. > >I've met jordan's cats, does that count :-) Only if you can prove that it was Jordans and not Schroedingers :-) -- 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 Sun Aug 1 23:36:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles505.castles.com [208.214.165.69]) by hub.freebsd.org (Postfix) with ESMTP id 1C1B315039 for ; Sun, 1 Aug 1999 23:36:11 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA01845; Sun, 1 Aug 1999 23:30:49 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908020630.XAA01845@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-reply-to: Your message of "Mon, 02 Aug 1999 08:30:52 +0200." <22728.933575452@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Aug 1999 23:30:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199908020207.MAA23787@godzilla.zeta.org.au>, Bruce Evans writes: > > >All of the above only work for the easy case where the whole disk is > >being labelled. In general, the disk size must be reduced to the slice > >size before applying a label to a slice. > > And that is the problem, it seems that "dangerously dedicated" doesn't > boot anymore... It never did, on many hardware variants. Use "truly dedicated" instead, which should still work fine. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Sun Aug 1 23:41: 4 1999 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 7437E14F49 for ; Sun, 1 Aug 1999 23:40:58 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA22944; Mon, 2 Aug 1999 08:38:56 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-reply-to: Your message of "Sun, 01 Aug 1999 23:30:48 PDT." <199908020630.XAA01845@dingo.cdrom.com> Date: Mon, 02 Aug 1999 08:38:56 +0200 Message-ID: <22942.933575936@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908020630.XAA01845@dingo.cdrom.com>, Mike Smith writes: >> In message <199908020207.MAA23787@godzilla.zeta.org.au>, Bruce Evans writes: >> >> >All of the above only work for the easy case where the whole disk is >> >being labelled. In general, the disk size must be reduced to the slice >> >size before applying a label to a slice. >> >> And that is the problem, it seems that "dangerously dedicated" doesn't >> boot anymore... > >It never did, on many hardware variants. Use "truly dedicated" >instead, which should still work fine. My semantics may be wrong on these two: what I'm talking about is what is in handbook chapter 8 "Using command line utilities " gives you a disk which doesn't boot. -- 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 Sun Aug 1 23:45: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (castles512.castles.com [208.214.165.76]) by hub.freebsd.org (Postfix) with ESMTP id 78C4814F49 for ; Sun, 1 Aug 1999 23:45:01 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id XAA01900; Sun, 1 Aug 1999 23:39:48 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908020639.XAA01900@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp Cc: Mike Smith , Bruce Evans , current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-reply-to: Your message of "Mon, 02 Aug 1999 08:38:56 +0200." <22942.933575936@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 01 Aug 1999 23:39:48 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199908020630.XAA01845@dingo.cdrom.com>, Mike Smith writes: > >> In message <199908020207.MAA23787@godzilla.zeta.org.au>, Bruce Evans writes: > >> > >> >All of the above only work for the easy case where the whole disk is > >> >being labelled. In general, the disk size must be reduced to the slice > >> >size before applying a label to a slice. > >> > >> And that is the problem, it seems that "dangerously dedicated" doesn't > >> boot anymore... > > > >It never did, on many hardware variants. Use "truly dedicated" > >instead, which should still work fine. > > My semantics may be wrong on these two: what I'm talking about is > what is in handbook chapter 8 "Using command line utilities " gives > you a disk which doesn't boot. Ok; of those two examples, the first should give you a truly dedicated disk. (You can only generate a "dangerously dedicated" disk with sysinstall.) What fails? Can you be more specific? How recent are your boot1/boot2 blocks? I would be inclined to dd at least 8k over the front of the disk myself, but I don't think that's relevant in your case. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Sun Aug 1 23:53:32 1999 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 C91FE14F57 for ; Sun, 1 Aug 1999 23:53:29 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA23042; Mon, 2 Aug 1999 08:49:53 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Mike Smith Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-reply-to: Your message of "Sun, 01 Aug 1999 23:39:48 PDT." <199908020639.XAA01900@dingo.cdrom.com> Date: Mon, 02 Aug 1999 08:49:53 +0200 Message-ID: <23040.933576593@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908020639.XAA01900@dingo.cdrom.com>, Mike Smith writes: >> My semantics may be wrong on these two: what I'm talking about is >> what is in handbook chapter 8 "Using command line utilities " gives >> you a disk which doesn't boot. > >Ok; of those two examples, the first should give you a truly dedicated >disk. (You can only generate a "dangerously dedicated" disk with >sysinstall.) > >What fails? Can you be more specific? How recent are your boot1/boot2 >blocks? I would be inclined to dd at least 8k over the front of the >disk myself, but I don't think that's relevant in your case. Disk error #1 while trying to load boot/loader. I think the bios in this case trust the 50000 in the length field of the mbr. We really need commandline tools that can do this... And without too much magic please... -- 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 Mon Aug 2 0:50:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from metriclient-1.uoregon.edu (metriclient-1.uoregon.edu [128.223.172.1]) by hub.freebsd.org (Postfix) with ESMTP id 28EC014F04 for ; Mon, 2 Aug 1999 00:50:37 -0700 (PDT) (envelope-from gurney_j@efn.org) Received: (from jmg@localhost) by metriclient-1.uoregon.edu (8.9.1/8.8.7) id AAA21168; Mon, 2 Aug 1999 00:50:14 -0700 (PDT) Message-ID: <19990802005014.12408@hydrogen.fircrest.net> Date: Mon, 2 Aug 1999 00:50:14 -0700 From: John-Mark Gurney To: Matthew Dillon Cc: Kevin Day , freebsd-current@FreeBSD.ORG Subject: Re: mountpoint locking with fbsd-nfs References: <199908020408.XAA76817@celery.dragondata.com> <199908020412.VAA08088@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199908020412.VAA08088@apollo.backplane.com>; from Matthew Dillon on Sun, Aug 01, 1999 at 09:12:03PM -0700 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 3.0-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon scribbled this message on Aug 1: > :Yeah, I know about -alldirs... The problem was that we had customers who > :wanted us to export their home directories, and unless I gave them their own > :filesystem, I couldn't restrict it in the manner i wanted. :) > : > :Just checking to see that I wasn't missing a way to do this. :) > > I've never in my life tried this - it probably won't work, but ... > use the null device maybe to create a mount point for each home > dir and then export that? do you guys ever read the man page?? read the following about 10 times... it is hard to understand, but make sure you know what it says, not what you THINK is says... this is from exports(5): A host may be specified only once for each local filesystem on the server and there may be only one default en- try for each server filesystem that applies to all other hosts. The lat- ter exports the filesystem to the ``world'' and should be used only when the filesystem contains public information. so, if you want to export /var and /var/tmp both on the same file system to the same host, it would be: /var /var/tmp somehost because of this, I organize my /etc/exports file by file system and then by host... so I do stuff like: #all of my /usr exports /usr /usr/local hosta /usr /usr/X11R6 hostb /usr/local -ro #all of my /a exports /a hostc /a /a/datadir hostd -- John-Mark Gurney Voice: +1 541 684 8449 Cu Networking P.O. Box 5693, 97405 "The soul contains in itself the event that shall presently befall it. The event is only the actualizing of its thought." -- Ralph Waldo Emerson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 0:59:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from cygnus.rush.net (cygnus.rush.net [209.45.245.133]) by hub.freebsd.org (Postfix) with ESMTP id 12DF914F04 for ; Mon, 2 Aug 1999 00:59:46 -0700 (PDT) (envelope-from bright@rush.net) Received: from localhost (bright@localhost) by cygnus.rush.net (8.9.3/8.9.3) with SMTP id DAA22179; Mon, 2 Aug 1999 03:58:20 -0400 (EDT) Date: Mon, 2 Aug 1999 03:58:18 -0400 (EDT) From: Alfred Perlstein To: Kevin Day Cc: Matthew Dillon , Martin Blapp , freebsd-current@FreeBSD.ORG Subject: Re: mountpoint locking with fbsd-nfs In-Reply-To: <199908020423.XAA95716@celery.dragondata.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, 1 Aug 1999, Kevin Day wrote: > > > > :Yeah, I know about -alldirs... The problem was that we had customers who > > :wanted us to export their home directories, and unless I gave them their own > > :filesystem, I couldn't restrict it in the manner i wanted. :) > > : > > :Just checking to see that I wasn't missing a way to do this. :) > > : > > :Kevin > > > > I've never in my life tried this - it probably won't work, but ... > > use the null device maybe to create a mount point for each home > > dir and then export that? > > > > I think it sees through this. > > su-2.03# cat /etc/exports > /var home > /mnt home > su-2.03# mount > /dev/wd0s1a on / (NFS exported, local, noatime, soft-updates, writes: sync > 3970 async 1321097) > procfs on /proc (local) > nfs:/home on /usr/home (noatime) > nfs:/var/mail on /var/mail (noatime) > /var/tmp on /mnt (local) > su-2.03# mountd > Aug 1 23:17:48 celery mountd[89177]: can't change attributes for /mnt > > That was a very good idea though, i'd never have thought of it. :) > > I'll have to play with this more. :) It cannot ever work properly. NFS is stateless, the nfs filehandles refer to inodes, you may be able to get this to actually export files, however i'm pretty sure without other measures someone would be able to cons up a fake nfs handle for files he doesn't own. (I think) Here's two things that may work: exporting -alldirs to specific hosts using the -mapall option in /exports /home -mapall=robert roberts.machine /home -mapall=julian julains.machine using a vn device, creating a ufs on it and then mounting it, then exporting it. this gives you nice per-user quotas as well :) -Alfred Perlstein - [bright@rush.net|bright@wintelcom.net] systems administrator and programmer Wintelcom - http://www.wintelcom.net/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 1: 1:21 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 68AA214F49; Mon, 2 Aug 1999 01:01:09 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id RAA23245; Mon, 2 Aug 1999 17:29:47 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id RAA60091; Mon, 2 Aug 1999 17:29:46 +0930 (CST) Date: Mon, 2 Aug 1999 17:29:45 +0930 From: Greg Lehey To: Mike Smith Cc: FreeBSD current users , FreeBSD Committers Subject: Re: Recent -CURRENT doesn't show process times on some hardware Message-ID: <19990802172945.V64532@freebie.lemis.com> References: <19990801132751.S64532@freebie.lemis.com> <199908020517.WAA01494@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199908020517.WAA01494@dingo.cdrom.com>; from Mike Smith on Sun, Aug 01, 1999 at 10:17:51PM -0700 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 Sunday, 1 August 1999 at 22:17:51 -0700, Mike Smith wrote: >> What makes this all the more puzzling is that it happens only on one >> machine. Hint: it's a laptop (Dell Latitude CPi). panic is a normal >> Pentium machine of no particular lineage. Does this ring a bell with >> anybody? > > Do you have APM enabled? Do you have the "broken statclock" option > enabled? I do now :-) > Have you tried permuting these two? Yes. I needed apm and broken statclock, and that did it. Thanks. (And why did it only happen in the past couple of weeks? Probably because I migrated from 3.2 to -CURRENT a little while before that, and didn't realise that there were problems until some time later). Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 1:15:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id BE48B1500D; Mon, 2 Aug 1999 01:15:11 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id JAA77736; Mon, 2 Aug 1999 09:20:03 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 2 Aug 1999 09:20:02 +0100 (BST) From: Doug Rabson To: "Brian F. Feldman" Cc: Stephen Hocking-Senior Programmer PGS Tensor Perth , current@freebsd.org Subject: Re: Assembler capable of supporting 3dnow! 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, 1 Aug 1999, Brian F. Feldman wrote: > On Sun, 1 Aug 1999, Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > > > I'm messing around with the latest mesa and have discovered (suprise)that our > > assembler doesn't support 3dnow instructions. Are there any plans to update to > > a version of binutils that does? Linux's stuff appears to support it. > > > > According to dfr, no, since the releases are in "beta" now or something. > I think it's worth updating. And no, it would be too hard to get 3DNow! > wihtouut updating gas. However: you can use the linux_devutils gcc/as/ld > etc. to build the parts of whatever you need with 3dnow instructions. There are no public betas that I can find. The only updates to binutils publically available seem to be the Linux patchsets :-(. -- 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 Mon Aug 2 1:59:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from m2-4-dbn.dial-up.net (c2-25-dbn.dial-up.net [196.34.155.153]) by hub.freebsd.org (Postfix) with ESMTP id 09E4814F6B for ; Mon, 2 Aug 1999 01:59:15 -0700 (PDT) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by m2-4-dbn.dial-up.net (8.8.7/8.6.12) id KAA20495; Mon, 2 Aug 1999 10:55:46 +0200 (SAST) From: Robert Nordier Message-Id: <199908020855.KAA20495@m2-4-dbn.dial-up.net> Subject: Re: junior-hacker task: "prepdisk" In-Reply-To: <23040.933576593@critter.freebsd.dk> from Poul-Henning Kamp at "Aug 2, 1999 08:49:53 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Mon, 2 Aug 1999 10:55:44 +0200 (SAST) Cc: mike@smith.net.au (Mike Smith), bde@zeta.org.au (Bruce Evans), 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 > >What fails? Can you be more specific? How recent are your boot1/boot2 > >blocks? I would be inclined to dd at least 8k over the front of the > >disk myself, but I don't think that's relevant in your case. > > Disk error #1 while trying to load boot/loader. I think the bios > in this case trust the 50000 in the length field of the mbr. Any better luck after enabling "LBA access" in boot1 as a build option (added back a few weeks ago), or does the BIOS not support this? BTW: Is this a genuine hard drive, or some form of disk-on-a-chip? I seem to recall the BIOS geometry in some cases uses a small number of sectors per track, which may push part of the 'a' partition beyond the 1023 CHS limit. Anyway, if some debugging code would help here, let me know. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 2: 1:37 1999 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 2E63314F6B for ; Mon, 2 Aug 1999 02:01:29 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id KAA23590; Mon, 2 Aug 1999 10:59:10 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Robert Nordier Cc: mike@smith.net.au (Mike Smith), bde@zeta.org.au (Bruce Evans), current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-reply-to: Your message of "Mon, 02 Aug 1999 10:55:44 +0200." <199908020855.KAA20495@m2-4-dbn.dial-up.net> Date: Mon, 02 Aug 1999 10:59:10 +0200 Message-ID: <23588.933584350@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908020855.KAA20495@m2-4-dbn.dial-up.net>, Robert Nordier writes: >> >What fails? Can you be more specific? How recent are your boot1/boot2 >> >blocks? I would be inclined to dd at least 8k over the front of the >> >disk myself, but I don't think that's relevant in your case. >> >> Disk error #1 while trying to load boot/loader. I think the bios >> in this case trust the 50000 in the length field of the mbr. > >Any better luck after enabling "LBA access" in boot1 as a build >option (added back a few weeks ago), or does the BIOS not support >this? > >BTW: Is this a genuine hard drive, or some form of disk-on-a-chip? >I seem to recall the BIOS geometry in some cases uses a small number >of sectors per track, which may push part of the 'a' partition >beyond the 1023 CHS limit. I've seen this on both flash disks and real disks. The flash disks have geometries which put them firmly inside 1023 cyls: fla0 maddr 0xd0000 msize 8192 on isa fla0: fla0: 39.1MB (80144 sectors), 1001 cyls, 16 heads, 5 S/T, 512 B/S fla1 maddr 0xd2000 msize 8192 on isa fla1: fla1: 70.5MB (144320 sectors), 1002 cyls, 16 heads, 9 S/T, 512 B/S fla2 maddr 0xd4000 msize 8192 on isa fla2: fla2: 39.1MB (80144 sectors), 1001 cyls, 16 heads, 5 S/T, 512 B/S fla3 maddr 0xd6000 msize 8192 on isa fla3: fla3: 141.0MB (288832 sectors), 1002 cyls, 16 heads, 18 S/T, 512 B/S fla4 maddr 0xd8000 msize 8192 on isa fla4: fla4: 7.8MB (15920 sectors), 995 cyls, 16 heads, 1 S/T, 512 B/S So cyl 1024 should not even enter in the equation... My real beef here is not with the boot failure but with the fact that our command line tools stink when I bring in a new blank disk... -- 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 Mon Aug 2 5:43:42 1999 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.108]) by hub.freebsd.org (Postfix) with ESMTP id F17F114BE5; Mon, 2 Aug 1999 05:43:38 -0700 (PDT) (envelope-from assar@sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.7.3) id OAA01715; Mon, 2 Aug 1999 14:44:15 +0200 (CEST) To: Doug Rabson Cc: "Brian F. Feldman" , Stephen Hocking-Senior Programmer PGS Tensor Perth , current@FreeBSD.ORG Subject: Re: Assembler capable of supporting 3dnow! References: Mime-Version: 1.0 (generated by tm-edit 7.68) Content-Type: text/plain; charset=US-ASCII From: Assar Westerlund Date: 02 Aug 1999 14:44:14 +0200 In-Reply-To: Doug Rabson's message of "Mon, 2 Aug 1999 09:20:02 +0100 (BST)" Message-ID: <5loggqtkrl.fsf@assaris.sics.se> Lines: 10 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson writes: > There are no public betas that I can find. The only updates to binutils > publically available seem to be the Linux patchsets :-(. Try (or the CVS tree at :pserver:anoncvs@anoncvs.cygnus.com:/cvs/binutils. That might not fit your definition of `beta' but it's publicly available and has 3Dnow support it in (I haven't tested it...). /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 6:19:48 1999 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 961DF150E5 for ; Mon, 2 Aug 1999 06:19:43 -0700 (PDT) (envelope-from iwasaki@jp.FreeBSD.org) Received: from localhost (isdn51.imasy.or.jp [202.227.24.243]) by tasogare.imasy.or.jp (8.9.3+3.2W/3.7W-tasogare/smtpfeed 1.01) with ESMTP id WAA14239; Mon, 2 Aug 1999 22:18:59 +0900 (JST) (envelope-from iwasaki@jp.FreeBSD.org) Message-Id: <199908021318.WAA14239@tasogare.imasy.or.jp> To: Maxim Sobolev Cc: Mike Smith , FreeBSD-current@FreeBSD.ORG, iwasaki@jp.freebsd.org Subject: Re: APM related panic 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: Mon, 02 Aug 1999 22:22:51 +0900 From: Mitsuru IWASAKI X-Dispatcher: imput version 980905(IM100) Lines: 55 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG # sorry to break the thread, I'm a digest reader... Hi, > > apm0: on motherboard > > apm: APM BIOS version 0102 > > apm: Code16 0xc00f0000, Data 0xc00fdfa0 > > apm: Code entry 0x00008010, Idling CPU enabled, Management enabled > > apm: CS_limit=0x0, DS_limit=0x0 > > These limits look pretty suspect, although the code segment below looks > OK. I suspect too, especially ds limit. I've seen such bogus 1.2 APM BIOSes before. I hope attached patch help you (for /sys/i386/apm/apm.c). P.S. Thank you for enhanced APM code, mike. I had enjoy last week end to study the new code. Some of my concerns about APM gone :-) --- apm.c- Mon Aug 2 21:31:20 1999 +++ apm.c Mon Aug 2 21:49:52 1999 @@ -773,6 +773,30 @@ sc->bios.seg.code16.limit = 0xffff; sc->bios.seg.data.limit = 0xffff; } + + /* + * Segment limits fixup: + * Some bogus APM V1.1 (even if V1.2) BIOSes do not return + * any size limits in the registers they are supposed to. + * if we see zero limits here, we assume that means they + * should be 64k. + */ + + /* code segment (16 bit) */ + if (sc->bios.seg.code16.limit == 0) { +#ifdef APM_DEBUG + printf("apm_probe: APM bios gave zero len code16, pegged to 64K\n"); +#endif + sc->bios.seg.code16.limit = 0xffff; + } + /* data segment */ + if (sc->bios.seg.data.limit == 0) { +#ifdef APM_DEBUG + printf("apm_probe: APM bios gave zero len data, tentative 64K\n"); +#endif + sc->bios.seg.data.limit = 0xffff; + } + return(0); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 9:38:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 9ADF415134 for ; Mon, 2 Aug 1999 09:38:49 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA08098; Tue, 3 Aug 1999 02:37:50 +1000 Date: Tue, 3 Aug 1999 02:37:50 +1000 From: Bruce Evans Message-Id: <199908021637.CAA08098@godzilla.zeta.org.au> To: mike@smith.net.au, phk@critter.freebsd.dk Subject: Re: junior-hacker task: "prepdisk" Cc: bde@zeta.org.au, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>> My semantics may be wrong on these two: what I'm talking about is >>> what is in handbook chapter 8 "Using command line utilities " gives >>> you a disk which doesn't boot. >> >>Ok; of those two examples, the first should give you a truly dedicated >>disk. (You can only generate a "dangerously dedicated" disk with >>sysinstall.) The first gives a vanilla dangerously dedicated disk (one with a historical bogus DOSpartition table of size 50000). Terminology for variants is less standard, e.g.: very dangerously dedicated:= dangerously dedicated with the DOSpartition table and/or boot signature zeroed or otherwise clobbered. undangerously dedicated:= dangerously dedicated with the DOSpartition table fixed to cover the whole disk (including the MBR). This is very easy to generate without sysinstall (just enter the start (0) and size for one partition in fdisk(8)). The second example is equivalent to the first except for bugs. Adding a `disklabel -e' step would fix it but then it would be too equivalent to be useful. The point of it is that the editing step can be inserted in the pipeline. This is necessary to handle all cases except dedicated ones. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 10: 0:55 1999 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 63A5614DD8 for ; Mon, 2 Aug 1999 10:00:41 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id JAA75533; Mon, 2 Aug 1999 09:59:15 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 2 Aug 1999 09:59:15 -0700 (PDT) From: Doug White To: Poul-Henning Kamp Cc: Mike Smith , Bruce Evans , current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-Reply-To: <22942.933575936@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 Mon, 2 Aug 1999, Poul-Henning Kamp wrote: > In message <199908020630.XAA01845@dingo.cdrom.com>, Mike Smith writes: > >> In message <199908020207.MAA23787@godzilla.zeta.org.au>, Bruce Evans writes: > >> > >> >All of the above only work for the easy case where the whole disk is > >> >being labelled. In general, the disk size must be reduced to the slice > >> >size before applying a label to a slice. > >> > >> And that is the problem, it seems that "dangerously dedicated" doesn't > >> boot anymore... > > > >It never did, on many hardware variants. Use "truly dedicated" > >instead, which should still work fine. > > My semantics may be wrong on these two: what I'm talking about is > what is in handbook chapter 8 "Using command line utilities " gives > you a disk which doesn't boot. What BIOS do you have? Did you try the tutorial version? I know machines that won't boot disks missing MS partition tables. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | 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 Aug 2 10: 2:52 1999 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 E6F081519F for ; Mon, 2 Aug 1999 10:02:35 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id KAA76468; Mon, 2 Aug 1999 10:02:06 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 2 Aug 1999 10:02:05 -0700 (PDT) From: Doug White To: Bruce Evans Cc: mike@smith.net.au, phk@critter.freebsd.dk, current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-Reply-To: <199908021637.CAA08098@godzilla.zeta.org.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, 3 Aug 1999, Bruce Evans wrote: > >>> My semantics may be wrong on these two: what I'm talking about is > >>> what is in handbook chapter 8 "Using command line utilities " gives > >>> you a disk which doesn't boot. > >> > >>Ok; of those two examples, the first should give you a truly dedicated > >>disk. (You can only generate a "dangerously dedicated" disk with > >>sysinstall.) > > The first gives a vanilla dangerously dedicated disk (one with a historical > bogus DOSpartition table of size 50000). Terminology for variants is less > standard, e.g.: > > very dangerously dedicated:= dangerously dedicated with the DOSpartition > table and/or boot signature zeroed or otherwise clobbered. > undangerously dedicated:= dangerously dedicated with the DOSpartition table > fixed to cover the whole disk (including the MBR). This is very easy > to generate without sysinstall (just enter the start (0) and size for > one partition in fdisk(8)). I've been looking for that tidbit forever! If you can build up a sample session, I'll docify it pronto. I don't have a disk to clobber or else I'd be writing docs right now :) Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | 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 Aug 2 10:22:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id B0C331522B for ; Mon, 2 Aug 1999 10:22:26 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA11711; Tue, 3 Aug 1999 03:20:50 +1000 Date: Tue, 3 Aug 1999 03:20:50 +1000 From: Bruce Evans Message-Id: <199908021720.DAA11711@godzilla.zeta.org.au> To: bde@zeta.org.au, dwhite@resnet.uoregon.edu Subject: Re: junior-hacker task: "prepdisk" Cc: current@FreeBSD.ORG, mike@smith.net.au, phk@critter.freebsd.dk Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> very dangerously dedicated:= dangerously dedicated with the DOSpartition >> table and/or boot signature zeroed or otherwise clobbered. >> undangerously dedicated:= dangerously dedicated with the DOSpartition table >> fixed to cover the whole disk (including the MBR). This is very easy >> to generate without sysinstall (just enter the start (0) and size for >> one partition in fdisk(8)). >I've been looking for that tidbit forever! If you can build up a sample >session, I'll docify it pronto. I don't have a disk to clobber or else >I'd be writing docs right now :) Make one using vnconfig(8) :-). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 11:53:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id EB8C714CC6 for ; Mon, 2 Aug 1999 11:53:14 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA04585; Mon, 2 Aug 1999 09:37:43 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908021637.JAA04585@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey Cc: FreeBSD current users Subject: Re: Recent -CURRENT doesn't show process times on some hardware In-reply-to: Your message of "Mon, 02 Aug 1999 17:29:45 +0930." <19990802172945.V64532@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Aug 1999 09:29:37 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sunday, 1 August 1999 at 22:17:51 -0700, Mike Smith wrote: > >> What makes this all the more puzzling is that it happens only on one > >> machine. Hint: it's a laptop (Dell Latitude CPi). panic is a normal > >> Pentium machine of no particular lineage. Does this ring a bell with > >> anybody? > > > > Do you have APM enabled? Do you have the "broken statclock" option > > enabled? > > I do now :-) > > > Have you tried permuting these two? > > Yes. I needed apm and broken statclock, and that did it. Thanks. > > (And why did it only happen in the past couple of weeks? Probably > because I migrated from 3.2 to -CURRENT a little while before that, > and didn't realise that there were problems until some time later). Until I pessimised it a little while back, the system would still try to keep time on an APM machine the same as it would on a desktop, with the sort of results you were seeing. We broke this a while before by changing the way that APM support is initialised. -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Aug 2 12: 8:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id F26C514CCD for ; Mon, 2 Aug 1999 12:08:00 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup3-60.iptelecom.net.ua [212.42.69.251]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id WAA08052; Mon, 2 Aug 1999 22:14:07 +0300 (EEST) Message-ID: <37A5ED08.F2441B45@altavista.net> Date: Mon, 02 Aug 1999 22:10:00 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Mitsuru IWASAKI Cc: Mike Smith , FreeBSD-current@FreeBSD.ORG Subject: Re: APM related panic Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Thanks, seems your patch did the trick (panic gone). Following is dmesd: apm_probe: APM bios gave zero len code16, pegged to 64K apm_probe: APM bios gave zero len data, tentative 64K apm0: on motherboard apm: APM BIOS version 0102 apm: Code16 0xc00f0000, Data 0xc00fdfa0 apm: Code entry 0x00008010, Idling CPU enabled, Management enabled apm: CS_limit=0xffff, DS_limit=0xffff apm: Engaged control enabled apm: found APM BIOS v1.2, connected at v1.2 apm: Slow Idling CPU enabled Add hook "default suspend" Add hook "default resume" Sincerely, Maxim > # sorry to break the thread, I'm a digest reader... > > Hi, > > > > apm0: on motherboard > > > apm: APM BIOS version 0102 > > > apm: Code16 0xc00f0000, Data 0xc00fdfa0 > > > apm: Code entry 0x00008010, Idling CPU enabled, Management enabled > > > apm: CS_limit=0x0, DS_limit=0x0 > > > These limits look pretty suspect, although the code segment below looks > > OK. > > I suspect too, especially ds limit. > I've seen such bogus 1.2 APM BIOSes before. I hope attached patch > help you (for /sys/i386/apm/apm.c). > > P.S. > Thank you for enhanced APM code, mike. I had enjoy last week end to > study the new code. Some of my concerns about APM gone :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 12:12:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id DCDB814CCD for ; Mon, 2 Aug 1999 12:12:16 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00672; Mon, 2 Aug 1999 12:05:04 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908021905.MAA00672@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Maxim Sobolev Cc: Mitsuru IWASAKI , Mike Smith , FreeBSD-current@FreeBSD.ORG Subject: Re: APM related panic In-reply-to: Your message of "Mon, 02 Aug 1999 22:10:00 +0300." <37A5ED08.F2441B45@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Aug 1999 12:05:04 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi! > > Thanks, seems your patch did the trick (panic gone). Following is dmesd: Thanks for the confirmation; I've made an even more pessimistic patch that should cover your situation. Please let me know if your next CTM works correctly. Thanks for the quick bug report too! > apm_probe: APM bios gave zero len code16, pegged to 64K > apm_probe: APM bios gave zero len data, tentative 64K > apm0: on motherboard > apm: APM BIOS version 0102 > apm: Code16 0xc00f0000, Data 0xc00fdfa0 > apm: Code entry 0x00008010, Idling CPU enabled, Management enabled > apm: CS_limit=0xffff, DS_limit=0xffff > apm: Engaged control enabled > apm: found APM BIOS v1.2, connected at v1.2 > apm: Slow Idling CPU enabled > Add hook "default suspend" > Add hook "default resume" > > Sincerely, > > Maxim > > # sorry to break the thread, I'm a digest reader... > > > > Hi, > > > > > > apm0: on motherboard > > > > apm: APM BIOS version 0102 > > > > apm: Code16 0xc00f0000, Data 0xc00fdfa0 > > > > apm: Code entry 0x00008010, Idling CPU enabled, Management enabled > > > > > apm: CS_limit=0x0, DS_limit=0x0 > > > > > These limits look pretty suspect, although the code segment below > looks > > > OK. > > > > I suspect too, especially ds limit. > > I've seen such bogus 1.2 APM BIOSes before. I hope attached patch > > help you (for /sys/i386/apm/apm.c). > > > > P.S. > > Thank you for enhanced APM code, mike. I had enjoy last week end to > > study the new code. Some of my concerns about APM gone :-) > > > -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Aug 2 12:13:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id E316E14C3A; Mon, 2 Aug 1999 12:13:02 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA78992; Mon, 2 Aug 1999 20:17:53 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Mon, 2 Aug 1999 20:17:53 +0100 (BST) From: Doug Rabson To: Assar Westerlund Cc: "Brian F. Feldman" , Stephen Hocking-Senior Programmer PGS Tensor Perth , current@FreeBSD.ORG Subject: Re: Assembler capable of supporting 3dnow! In-Reply-To: <5loggqtkrl.fsf@assaris.sics.se> 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 2 Aug 1999, Assar Westerlund wrote: > Doug Rabson writes: > > There are no public betas that I can find. The only updates to binutils > > publically available seem to be the Linux patchsets :-(. > > Try (or the CVS > tree at :pserver:anoncvs@anoncvs.cygnus.com:/cvs/binutils. That might > not fit your definition of `beta' but it's publicly available and has > 3Dnow support it in (I haven't tested it...). Thanks for the pointer. I won't be able to look at it for a while but it should be useful. -- 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 Mon Aug 2 12:13:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 0CE3C15191 for ; Mon, 2 Aug 1999 12:13:32 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id MAA00697; Mon, 2 Aug 1999 12:07:36 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908021907.MAA00697@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mitsuru IWASAKI Cc: FreeBSD-current@FreeBSD.ORG Subject: Re: APM related panic In-reply-to: Your message of "Mon, 02 Aug 1999 22:22:51 +0900." <199908021318.WAA14239@tasogare.imasy.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Aug 1999 12:07:36 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > # sorry to break the thread, I'm a digest reader... Not a problem at all. > > > apm0: on motherboard > > > apm: APM BIOS version 0102 > > > apm: Code16 0xc00f0000, Data 0xc00fdfa0 > > > apm: Code entry 0x00008010, Idling CPU enabled, Management enabled > > > apm: CS_limit=0x0, DS_limit=0x0 > > > > These limits look pretty suspect, although the code segment below looks > > OK. > > I suspect too, especially ds limit. > I've seen such bogus 1.2 APM BIOSes before. I hope attached patch > help you (for /sys/i386/apm/apm.c). Gotcha. I've decided to just completely ignore all of the segment limit values the BIOS returns and assume 64k for the lot. This is basically the same conclusion that the Linux folks have come to, and its a harmless option. > P.S. > Thank you for enhanced APM code, mike. I had enjoy last week end to > study the new code. Some of my concerns about APM gone :-) You should thank Jonathan Lemon, as the bulk of the code is his; I just did the scutwork to get it in... -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Aug 2 12:32: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id 22DC514F22 for ; Mon, 2 Aug 1999 12:31:51 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup3-60.iptelecom.net.ua [212.42.69.251]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id WAA09672 for ; Mon, 2 Aug 1999 22:38:14 +0300 (EEST) Message-ID: <37A5F2BB.9AC7A089@altavista.net> Date: Mon, 02 Aug 1999 22:34:19 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Sh still is not working for MAKEDEV Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, Does anybody investigating what wrong with the sh in the -current? As I reported earlier it still fails to correctly process MAKEDEV script. Sincerely, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 14:18:45 1999 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 6237A14A0B for ; Mon, 2 Aug 1999 14:18:36 -0700 (PDT) (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 PAA88744; Mon, 2 Aug 1999 15:17:28 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA08820; Mon, 2 Aug 1999 15:17:35 -0600 (MDT) Message-Id: <199908022117.PAA08820@harmony.village.org> To: adamw@holonet.net (Adam Wight) Subject: Re: PCMCIA drivers Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Sun, 01 Aug 1999 22:16:15 -0800." References: Date: Mon, 02 Aug 1999 15:17:35 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Adam Wight writes: : First, the current zp driver cannot be configured if the pccard services : are being used, since it uses its own pccard code. Very Bad. : : Then, the PCMCIA model that we use now makes it impossible to use both : functions of a doubly useful card. This too is Very Bad. : : Is anyone addressing these problems? Yes. I'm working on porting the newconfig based pccard/cardbus code to -current. zp is evil and will die. The current pccard code is evil and must die. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 14:21:39 1999 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 67CD214C36 for ; Mon, 2 Aug 1999 14:21:36 -0700 (PDT) (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 PAA88755; Mon, 2 Aug 1999 15:21:02 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA08843; Mon, 2 Aug 1999 15:21:09 -0600 (MDT) Message-Id: <199908022121.PAA08843@harmony.village.org> To: Poul-Henning Kamp Subject: Re: junior-hacker task: "prepdisk" Cc: Robert Nordier , mike@smith.net.au (Mike Smith), bde@zeta.org.au (Bruce Evans), current@FreeBSD.ORG In-reply-to: Your message of "Mon, 02 Aug 1999 10:59:10 +0200." <23588.933584350@critter.freebsd.dk> References: <23588.933584350@critter.freebsd.dk> Date: Mon, 02 Aug 1999 15:21:09 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <23588.933584350@critter.freebsd.dk> Poul-Henning Kamp writes: : My real beef here is not with the boot failure but with the fact that our : command line tools stink when I bring in a new blank disk... Yes. Several times I've hit this problem, but have never been PO'd enough to fix it... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 15:53:17 1999 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 8DFB714FE0; Mon, 2 Aug 1999 15:52:59 -0700 (PDT) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA25513; Mon, 2 Aug 1999 18:54:53 -0400 From: Bill Paul Message-Id: <199908022254.SAA25513@skynet.ctr.columbia.edu> Subject: FYI for those with 3Com 3c905C cards To: current@freebsd.org, stable@freebsd.org Date: Mon, 2 Aug 1999 18:54:52 -0400 (EDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 3767 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've gotten a couple of reports from people claiming to have trouble with the 3c905C, usually along the lines of "the autonegotiation works and I can bring the card up, but I can't receive or send any packets." (For those who don't know, the 3c905C differes from the 3c905B in that it has a new 3Com XL ASIC revision called the "Tornado," plus has management features including wake on LAN and SMBUS interfaces, and it has a built-in boot ROM with support for BOOTP, DHCP, PXE, and a bunch of other acronyms.) First off, this is not entirely correctly: in the few cases where I've been able to squeeze information out of people, I've found that running tcpdump on the interface shows that the 3c905C does at least receive some traffic, so "can't send or receive any packets" is not entirely correctly. I haven't gotten anyone to do proper transmitter testing. Diagnosing this has been hard, largely due to the fact that I haven't been able to duplicate the problem with my hardware: I've tried a Dell PowerEdge 2300/400 dual PII 400 SMP box, a P200 GW2K box, a 486/66 and my alphastation 200, and in each case I was able to send and receive traffic without any apparent problems. The only peculiarity I encountered was with the PowerEdge system. The two cards I have were sent to me by 3Com; when the first one arrived, I plugged it into one of the primary PCI slots in the Dell (one of the same slots I'd used before with several other cards) and the machine refused to power on. Initially, I thought the card was hosed, and 3Com sent me a second one, which exhibited the same behavior. Finally I discovered that if I put the card in one of the secondary PCI slots (which turns out to be PCI bus 2, connected to PCI bus 0 via a DEC PCI-PCI bridge), the machine would power on fine and the card would work correctly in FreeBSD. (For all you armchair technicians out there, no, it's not a problem with the card drawing too much power or a shorted trace on the card. I don't know what it is, though I suspect some PCI BIOS weirdness.) Today I was experimenting with another machine, a Dell PowerEdge 4300/500 dual PIII 500Mhz system, and I did finally encounter a problem: for some reason, the 3c905C refused to receive certain NFS packets (in particular NFS create requests). I don't know why this happened exactly, however I fixed the problem by modifying the xl driver code to issue individual "reset TX block" and "reset RX block" command after issuing the global reset command in xl_reset(). Now that the transmitter and receiver are reset as part of the card initialization, everything seems to work correctly. I committed this changed to the xl driver in both the current and stable branches today, plus I updated the code at http://www.freebsd.org/~wpaul/3Com. If you have a 3c905C card and have been having trouble getting it to work with FreeBSD, I would appreciate it if you could cvsup to the latest -stable or -current or download the driver from the web server and give it a try. I'm not positive that this will fix all the problems people have been seeing, but I'm very curious to see what effect it has. If you notice any improvements (or not), please let me know at wpaul@skynet.ctr.columbia.edu. -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 Mon Aug 2 17:16:55 1999 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 994B214F1D for ; Mon, 2 Aug 1999 17:16:39 -0700 (PDT) (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.02 #1) id 11BSFV-000M7u-00; Tue, 03 Aug 1999 02:16:09 +0200 From: Sheldon Hearn To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: Sh still is not working for MAKEDEV In-reply-to: Your message of "Mon, 02 Aug 1999 22:34:19 +0300." <37A5F2BB.9AC7A089@altavista.net> Date: Tue, 03 Aug 1999 02:16:09 +0200 Message-ID: <85057.933639369@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 02 Aug 1999 22:34:19 +0300, Maxim Sobolev wrote: > Does anybody investigating what wrong with the sh in the -current? As I > reported earlier it still fails to correctly process MAKEDEV script. Perhaps someone should have come out and said this last time: I can't reproduce the problem. A buddy of mine in the office says this is exactly what he got a little while ago after compiling with -O2, but you've already stated that you're sure you didn't do this. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 17:33:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 2452014FAE for ; Mon, 2 Aug 1999 17:33:35 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id JAA27135; Tue, 3 Aug 1999 09:25:28 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA62622; Tue, 3 Aug 1999 09:25:26 +0930 (CST) Date: Tue, 3 Aug 1999 09:25:26 +0930 From: Greg Lehey To: Andrzej Bialecki Cc: Jeroen Ruigrok/Asmodai , current@FreeBSD.ORG Subject: Re: Panic plus advice needed Message-ID: <19990803092526.Z64532@freebie.lemis.com> References: <19990731121442.C378@daemon.ninth-circle.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Andrzej Bialecki on Sun, Aug 01, 1999 at 11:33:07PM +0200 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 Sunday, 1 August 1999 at 23:33:07 +0200, Andrzej Bialecki wrote: > On Sat, 31 Jul 1999, Jeroen Ruigrok/Asmodai wrote: > >> >> No, just options DDB. >> This bt was obtained after doing gdb -k kernel.0 vmcore.0 >> I still have the DDB trace on paper which I can type in if needed/wanted. >> >>> What you do with the results depends a lot on what you find. On the >>> whole, I wouldn't think it worth the pain of debugging without >>> symbols. >> >> No it isn't... > > Another handful tricks of the trade: > > * if you still have exactly the same source tree and config file, > recompile the kernel with -g to obtain the version with debugging symbols bde has reported that the code may not be identical when compiling for debugging. It should be, but for obscure reasons it doesn't quite make it. > * if you can't for the life of you get the crash dump to examine what went > wrong, do remember of remote GDB option under DDB - that is, if you have > another machine with the same sources and kenel. But if the problem is > repeatable you can prepare it beforehand... Remote GDB works miracles > then. When it works. It's very temperamental. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 18: 5:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 5814314F8A for ; Mon, 2 Aug 1999 18:05:01 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip144.houston3.tx.pub-ip.psi.net [38.12.169.144]) by leap.innerx.net (Postfix) with ESMTP id 2435D370CB; Mon, 2 Aug 1999 21:04:41 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id UAA42352; Mon, 2 Aug 1999 20:04:45 -0500 (CDT) (envelope-from chris) Date: Mon, 2 Aug 1999 20:04:32 -0500 From: Chris Costello To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: Sh still is not working for MAKEDEV Message-ID: <19990802200432.B41547@holly.dyndns.org> Reply-To: chris@calldei.com References: <37A5F2BB.9AC7A089@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <37A5F2BB.9AC7A089@altavista.net>; from Maxim Sobolev on Mon, Aug 02, 1999 at 10:34:19PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 02, 1999, Maxim Sobolev wrote: > Hi folks, > > Does anybody investigating what wrong with the sh in the -current? As I > reported earlier it still fails to correctly process MAKEDEV script. Are you sure you are not running bash instead of sh? -- |Chris Costello |Microwave: Signal from a friendly micro... `------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 18:29:46 1999 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 92AB414EEC for ; Mon, 2 Aug 1999 18:29:38 -0700 (PDT) (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.8.8) with ESMTP id SAA09463; Mon, 2 Aug 1999 18:28:33 -0700 (PDT) (envelope-from hasty@rah.star-gate.com) Message-Id: <199908030128.SAA09463@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: chris@calldei.com Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Sh still is not working for MAKEDEV In-reply-to: Your message of "Mon, 02 Aug 1999 20:04:32 CDT." <19990802200432.B41547@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 02 Aug 1999 18:28:33 -0700 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, he can run "ktrace -di ./MAKEDEV " then kdump >foo.dump Or compile sh with debug symbols and trace down the failure. -- 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 Aug 2 22:28:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.42.68.2]) by hub.freebsd.org (Postfix) with ESMTP id A4F7014FD6 for ; Mon, 2 Aug 1999 22:28:30 -0700 (PDT) (envelope-from sobomax@altavista.net) Received: from altavista.net (dialup1-31.iptelecom.net.ua [212.42.68.158]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id IAA07503; Tue, 3 Aug 1999 08:35:15 +0300 (EEST) Message-ID: <37A67EA2.A0A3F37C@altavista.net> Date: Tue, 03 Aug 1999 08:31:14 +0300 From: Maxim Sobolev X-Mailer: Mozilla 4.6 [en] (Win95; I) X-Accept-Language: en MIME-Version: 1.0 To: Amancio Hasty Cc: chris@calldei.com, current@FreeBSD.ORG Subject: Re: Sh still is not working for MAKEDEV References: <199908030128.SAA09463@rah.star-gate.com> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty wrote: > Well, he can run "ktrace -di ./MAKEDEV " then > kdump >foo.dump > > Or compile sh with debug symbols and trace down the failure. Thanks to all for prompt replies. It seems like a bug in egcs which broke sh when "-march=pentium" option is used while -O? level doesn't really matter. Any ideas on how to track it down? Bests, Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Aug 2 23:38:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (Postfix) with ESMTP id C791414C1E for ; Mon, 2 Aug 1999 23:38:15 -0700 (PDT) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA71274; Tue, 3 Aug 1999 08:37:09 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199908030637.IAA71274@gratis.grondar.za> To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: PCMCIA drivers Date: Tue, 03 Aug 1999 08:37:08 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The current pccard code is evil and must die. Be that as it may, it is a huge improvement today over what it was a month ago. Thanks!! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 2: 2:16 1999 Delivered-To: freebsd-current@freebsd.org Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (Postfix) with ESMTP id 0BCD414FB5; Tue, 3 Aug 1999 02:02:10 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id KAA03681; Tue, 3 Aug 1999 10:44:35 +0200 (MET DST) Date: Tue, 3 Aug 1999 10:44:32 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: FreeBSD current mailing list , FreeBSD hackers mailing list , FreeBSD hardware mailing list Subject: Support for ez USB chips, anchorchips 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 A down-/uploader for the EZ USB chip is available from http://www.etla.net/~ezload.tar.gz See also the AnchorChips home page http://www.anchorchips.com/ The utility is courtesy of Dirk van Gulik, WebWeaving Consultancy and ActiveWire, Inc. (prototype board, http://www.activewireinc.com/) Cheers, Nick Hibma FreeBSD USB Project mailing list: usb-bsd@egroups.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 6:37:35 1999 Delivered-To: freebsd-current@freebsd.org Received: from web109.yahoomail.com (web109.yahoomail.com [205.180.60.76]) by hub.freebsd.org (Postfix) with SMTP id 00A7614EB7 for ; Tue, 3 Aug 1999 06:37:33 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19990803133657.24827.rocketmail@web109.yahoomail.com> Received: from [147.226.112.101] by web109.yahoomail.com; Tue, 03 Aug 1999 06:36:57 PDT Date: Tue, 3 Aug 1999 06:36:57 -0700 (PDT) From: "Valentin S. Chopov" Subject: problem with last src/sys/pccard changes 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 After cvsup of src/sys/pccard and src/usr.sbin/pccard from Aug 1, PCMCIA net card is not working. Te message from pccardd is : Aug 3 02:28:42 valsho pccardd[256]: driver allocation failed for IC-CARD(IC-CARD): Inappropriate ioctl for device Also new pccardd is working with old kernel code... So, may be te problem is in src/sys/pccard. Thanks, Val _____________________________________________________________ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 7:41:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.189]) by hub.freebsd.org (Postfix) with SMTP id 72E9214D85 for ; Tue, 3 Aug 1999 07:41:15 -0700 (PDT) (envelope-from ejc@bazzle.com) Received: (qmail 71439 invoked from network); 3 Aug 1999 14:40:57 -0000 Received: from gargoyle.bazzle.com (206.103.246.189) by gargoyle.bazzle.com with SMTP; 3 Aug 1999 14:40:57 -0000 Date: Tue, 3 Aug 1999 10:40:57 -0400 (EDT) From: "Eric J. Chet" To: marcel@FreeBSD.org Cc: phk@FreeBSD.org, current@FreeBSD.org Subject: VMware X11 and -current Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-169768575-933691257=:71237" 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-169768575-933691257=:71237 Content-Type: TEXT/PLAIN; charset=US-ASCII Hello I have been using FreeBSD under vmware for a few weeks now, running 3.2R. Everything has been running good including X11. I upgraded to -current and the linux XF86_vmware server stopped working. When I try and start the xserver I get an error "xf86OpenConsole: cannot open /dev/tty0. I'm running -current as of 8/1/99 with the latest linux_base port. I have been reading the linux emulation code, it looks like the major changes since 3.2R are the internal kernel device struct changes. I'm CCing Poul-Henning and Marcel I hope you don't mind, it looks like both of you have been in this code lately. Any hints on fixing this would be great,if you happen to understand why this might be happening. BTW: VMware seems faster under -current than 3.2R. Time stands still under 3.2R(gettimeofday), under current it runs 1.3 times to fast. Thanks, Eric Chet -> ejc@bazzle.com ejc@FreeBSD.ORG echet@cms.cendant.com --0-169768575-933691257=:71237 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="truss.out" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="truss.out" c3lzY2FsbCBfX3N5c2N0bCgweGJmYmZkYTcwLDB4MiwweDI4MDVhMjY4LDB4 YmZiZmRhNmMsMHgwLDB4MCkNCglyZXR1cm5zIDAgKDB4MCkNCnN5c2NhbGwg bW1hcCgweDAsMzI3NjgsMHgzLDB4MTAwMiwtMSwweDApDQoJcmV0dXJucyA2 NzE0NjEzNzYgKDB4MjgwNWIwMDApDQpzeXNjYWxsIGdldGV1aWQoKQ0KCXJl dHVybnMgMTAwMSAoMHgzZTkpDQpzeXNjYWxsIGdldHVpZCgpDQoJcmV0dXJu cyAxMDAxICgweDNlOSkNCnN5c2NhbGwgZ2V0ZWdpZCgpDQoJcmV0dXJucyAx MDAxICgweDNlOSkNCnN5c2NhbGwgZ2V0Z2lkKCkNCglyZXR1cm5zIDEwMDEg KDB4M2U5KQ0Kc3lzY2FsbCBhY2Nlc3MoMHgyODA1YzAyMCwweDApDQoJcmV0 dXJucyAwICgweDApDQpzeXNjYWxsIG9wZW4oIi91c3IvWDExUjYvbGliL2xp YlhtdS5zby42IiwwLDA1MDAxMzE2NzUwKQ0KCXJldHVybnMgMyAoMHgzKQ0K c3lzY2FsbCByZWFkKDB4MywweGJmYmZjYTk4LDB4MTAwMCkNCglyZXR1cm5z IDQwOTYgKDB4MTAwMCkNCnN5c2NhbGwgbW1hcCgweDAsNjk2MzIsMHg1LDB4 MiwzLDB4MCkNCglyZXR1cm5zIDY3MTQ5NDE0NCAoMHgyODA2MzAwMCkNCnN5 c2NhbGwgbW1hcCgweDI4MDcyMDAwLDgxOTIsMHgzLDB4MTIsMywweGUwMDAp DQoJcmV0dXJucyA2NzE1NTU1ODQgKDB4MjgwNzIwMDApDQpzeXNjYWxsIGNs b3NlKDMpDQoJcmV0dXJucyAwICgweDApDQpzeXNjYWxsIGFjY2VzcygweDI4 MDVjMDQwLDB4MCkNCglyZXR1cm5zIDAgKDB4MCkNCnN5c2NhbGwgb3Blbigi L3Vzci9YMTFSNi9saWIvbGliWHQuc28uNiIsMCwwNTAwMTMxNjc1MCkNCgly ZXR1cm5zIDMgKDB4MykNCnN5c2NhbGwgcmVhZCgweDMsMHhiZmJmY2E5OCww eDEwMDApDQoJcmV0dXJucyA0MDk2ICgweDEwMDApDQpzeXNjYWxsIG1tYXAo MHgwLDI2MjE0NCwweDUsMHgyLDMsMHgwKQ0KCXJldHVybnMgNjcxNTYzNzc2 ICgweDI4MDc0MDAwKQ0Kc3lzY2FsbCBtbWFwKDB4MjgwYjAwMDAsMTIyODgs MHgzLDB4MTIsMywweDNiMDAwKQ0KCXJldHVybnMgNjcxODA5NTM2ICgweDI4 MGIwMDAwKQ0Kc3lzY2FsbCBtbWFwKDB4MjgwYjMwMDAsNDA5NiwweDMsMHgx MDEyLC0xLDB4MCkNCglyZXR1cm5zIDY3MTgyMTgyNCAoMHgyODBiMzAwMCkN CnN5c2NhbGwgY2xvc2UoMykNCglyZXR1cm5zIDAgKDB4MCkNCnN5c2NhbGwg YWNjZXNzKDB4MjgwNWMwNjAsMHgwKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lz Y2FsbCBvcGVuKCIvdXNyL1gxMVI2L2xpYi9saWJTTS5zby42IiwwLDA1MDAx MzE2NzUwKQ0KCXJldHVybnMgMyAoMHgzKQ0Kc3lzY2FsbCByZWFkKDB4Myww eGJmYmZjYTk4LDB4MTAwMCkNCglyZXR1cm5zIDQwOTYgKDB4MTAwMCkNCnN5 c2NhbGwgbW1hcCgweDAsMzI3NjgsMHg1LDB4MiwzLDB4MCkNCglyZXR1cm5z IDY3MTgyNTkyMCAoMHgyODBiNDAwMCkNCnN5c2NhbGwgbW1hcCgweDI4MGJi MDAwLDQwOTYsMHgzLDB4MTIsMywweDYwMDApDQoJcmV0dXJucyA2NzE4NTQ1 OTIgKDB4MjgwYmIwMDApDQpzeXNjYWxsIGNsb3NlKDMpDQoJcmV0dXJucyAw ICgweDApDQpzeXNjYWxsIGFjY2VzcygweDI4MDVjMDgwLDB4MCkNCglyZXR1 cm5zIDAgKDB4MCkNCnN5c2NhbGwgb3BlbigiL3Vzci9YMTFSNi9saWIvbGli SUNFLnNvLjYiLDAsMDUwMDEzMTY3NTApDQoJcmV0dXJucyAzICgweDMpDQpz eXNjYWxsIHJlYWQoMHgzLDB4YmZiZmNhOTgsMHgxMDAwKQ0KCXJldHVybnMg NDA5NiAoMHgxMDAwKQ0Kc3lzY2FsbCBtbWFwKDB4MCw4NjAxNiwweDUsMHgy LDMsMHgwKQ0KCXJldHVybnMgNjcxODU4Njg4ICgweDI4MGJjMDAwKQ0Kc3lz Y2FsbCBtbWFwKDB4MjgwY2UwMDAsNDA5NiwweDMsMHgxMiwzLDB4MTEwMDAp DQoJcmV0dXJucyA2NzE5MzI0MTYgKDB4MjgwY2UwMDApDQpzeXNjYWxsIG1t YXAoMHgyODBjZjAwMCw4MTkyLDB4MywweDEwMTIsLTEsMHgwKQ0KCXJldHVy bnMgNjcxOTM2NTEyICgweDI4MGNmMDAwKQ0Kc3lzY2FsbCBjbG9zZSgzKQ0K CXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBhY2Nlc3MoMHgyODA1YzBhMCww eDApDQoJcmV0dXJucyAwICgweDApDQpzeXNjYWxsIG9wZW4oIi91c3IvWDEx UjYvbGliL2xpYlhleHQuc28uNiIsMCwwNTAwMTMxNjc1MCkNCglyZXR1cm5z IDMgKDB4MykNCnN5c2NhbGwgcmVhZCgweDMsMHhiZmJmY2E5OCwweDEwMDAp DQoJcmV0dXJucyA0MDk2ICgweDEwMDApDQpzeXNjYWxsIG1tYXAoMHgwLDQw OTYwLDB4NSwweDIsMywweDApDQoJcmV0dXJucyA2NzE5NDQ3MDQgKDB4Mjgw ZDEwMDApDQpzeXNjYWxsIG1tYXAoMHgyODBkYTAwMCw0MDk2LDB4MywweDEy LDMsMHg4MDAwKQ0KCXJldHVybnMgNjcxOTgxNTY4ICgweDI4MGRhMDAwKQ0K c3lzY2FsbCBjbG9zZSgzKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBh Y2Nlc3MoMHgyODA1YzBjMCwweDApDQoJcmV0dXJucyAwICgweDApDQpzeXNj YWxsIG9wZW4oIi91c3IvWDExUjYvbGliL2xpYlgxMS5zby42IiwwLDA1MDAx MzE2NzUwKQ0KCXJldHVybnMgMyAoMHgzKQ0Kc3lzY2FsbCByZWFkKDB4Myww eGJmYmZjYTk4LDB4MTAwMCkNCglyZXR1cm5zIDQwOTYgKDB4MTAwMCkNCnN5 c2NhbGwgbW1hcCgweDAsNjE0NDAwLDB4NSwweDIsMywweDApDQoJcmV0dXJu cyA2NzE5ODU2NjQgKDB4MjgwZGIwMDApDQpzeXNjYWxsIG1tYXAoMHgyODE2 YjAwMCwyNDU3NiwweDMsMHgxMiwzLDB4OGYwMDApDQoJcmV0dXJucyA2NzI1 NzU0ODggKDB4MjgxNmIwMDApDQpzeXNjYWxsIGNsb3NlKDMpDQoJcmV0dXJu cyAwICgweDApDQpzeXNjYWxsIGFjY2VzcygweDI4MDVjMGUwLDB4MCkNCgll cnJubyAyICdObyBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5Jw0Kc3lzY2FsbCBv cGVuKCIvdmFyL3J1bi9sZC1lbGYuc28uaGludHMiLDAsMDUwMDEzMTY3NTAp DQoJcmV0dXJucyAzICgweDMpDQpzeXNjYWxsIHJlYWQoMHgzLDB4YmZiZmRh MWMsMHg4MCkNCglyZXR1cm5zIDEyOCAoMHg4MCkNCnN5c2NhbGwgbHNlZWso MywweDgwLDApDQoJcmV0dXJucyAxMjggKDB4ODApDQpzeXNjYWxsIHJlYWQo MHgzLDB4MjgwNWYwMDAsMHg1MikNCglyZXR1cm5zIDgyICgweDUyKQ0Kc3lz Y2FsbCBjbG9zZSgzKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBhY2Nl c3MoMHgyODA1YzBlMCwweDApDQoJcmV0dXJucyAwICgweDApDQpzeXNjYWxs IG9wZW4oIi91c3IvbGliL2xpYnhwZzQuc28uMiIsMCwwNTAwMTMxNjc1MCkN CglyZXR1cm5zIDMgKDB4MykNCnN5c2NhbGwgcmVhZCgweDMsMHhiZmJmY2E5 OCwweDEwMDApDQoJcmV0dXJucyA0MDk2ICgweDEwMDApDQpzeXNjYWxsIG1t YXAoMHgwLDE2Mzg0LDB4NSwweDIsMywweDApDQoJcmV0dXJucyA2NzI2MDAw NjQgKDB4MjgxNzEwMDApDQpzeXNjYWxsIG1tYXAoMHgyODE3MzAwMCw4MTky LDB4MywweDEyLDMsMHgxMDAwKQ0KCXJldHVybnMgNjcyNjA4MjU2ICgweDI4 MTczMDAwKQ0Kc3lzY2FsbCBjbG9zZSgzKQ0KCXJldHVybnMgMCAoMHgwKQ0K c3lzY2FsbCBhY2Nlc3MoMHgyODA1YzEwMCwweDApDQoJZXJybm8gMiAnTm8g c3VjaCBmaWxlIG9yIGRpcmVjdG9yeScNCnN5c2NhbGwgYWNjZXNzKDB4Mjgw NWMxMDAsMHgwKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBvcGVuKCIv dXNyL2xpYi9saWJjLnNvLjMiLDAsMDUwMDEzMTY3NTApDQoJcmV0dXJucyAz ICgweDMpDQpzeXNjYWxsIHJlYWQoMHgzLDB4YmZiZmNhOTgsMHgxMDAwKQ0K CXJldHVybnMgNDA5NiAoMHgxMDAwKQ0Kc3lzY2FsbCBtbWFwKDB4MCw1MzI0 ODAsMHg1LDB4MiwzLDB4MCkNCglyZXR1cm5zIDY3MjYxNjQ0OCAoMHgyODE3 NTAwMCkNCnN5c2NhbGwgbW1hcCgweDI4MWU0MDAwLDE2Mzg0LDB4MywweDEy LDMsMHg2ZTAwMCkNCglyZXR1cm5zIDY3MzA3MTEwNCAoMHgyODFlNDAwMCkN CnN5c2NhbGwgbW1hcCgweDI4MWU4MDAwLDYxNDQwLDB4MywweDEwMTIsLTEs MHgwKQ0KCXJldHVybnMgNjczMDg3NDg4ICgweDI4MWU4MDAwKQ0Kc3lzY2Fs bCBjbG9zZSgzKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBhY2Nlc3Mo MHgyODA1YzEyMCwweDApDQoJcmV0dXJucyAwICgweDApDQpzeXNjYWxsIGFj Y2VzcygweDI4MDVjMTIwLDB4MCkNCglyZXR1cm5zIDAgKDB4MCkNCnN5c2Nh bGwgYWNjZXNzKDB4MjgwNWMxMjAsMHgwKQ0KCXJldHVybnMgMCAoMHgwKQ0K c3lzY2FsbCBhY2Nlc3MoMHgyODA1YzEyMCwweDApDQoJcmV0dXJucyAwICgw eDApDQpzeXNjYWxsIGFjY2VzcygweDI4MDVjMTIwLDB4MCkNCglyZXR1cm5z IDAgKDB4MCkNCnN5c2NhbGwgYWNjZXNzKDB4MjgwNWMxMjAsMHgwKQ0KCXJl dHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBhY2Nlc3MoMHgyODA1YzEyMCwweDAp DQoJcmV0dXJucyAwICgweDApDQpzeXNjYWxsIGFjY2VzcygweDI4MDVjMTIw LDB4MCkNCglyZXR1cm5zIDAgKDB4MCkNCnN5c2NhbGwgYWNjZXNzKDB4Mjgw NWMxMjAsMHgwKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBhY2Nlc3Mo MHgyODA1YzEyMCwweDApDQoJcmV0dXJucyAwICgweDApDQpzeXNjYWxsIGFj Y2VzcygweDgwNDk5NmEsMHgxKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lzY2Fs bCBhY2Nlc3MoMHg4MDRjMTIwLDB4MCkNCglyZXR1cm5zIDAgKDB4MCkNCnN5 c2NhbGwgYWNjZXNzKDB4ODA0YzAyMCwweDApDQoJZXJybm8gMiAnTm8gc3Vj aCBmaWxlIG9yIGRpcmVjdG9yeScNCnN5c2NhbGwgcmVhZGxpbmsoIi9ldGMv bWFsbG9jLmNvbmYiLDB4YmZiZmRhODQsNjMpDQoJZXJybm8gMiAnTm8gc3Vj aCBmaWxlIG9yIGRpcmVjdG9yeScNCnN5c2NhbGwgbW1hcCgweDAsNDA5Niww eDMsMHgxMDAyLC0xLDB4MCkNCglyZXR1cm5zIDY3MzE0ODkyOCAoMHgyODFm NzAwMCkNCnN5c2NhbGwgYnJlYWsoMHg4MDRlMDAwKQ0KCXJldHVybnMgMCAo MHgwKQ0Kc3lzY2FsbCBicmVhaygweDgwNGYwMDApDQoJcmV0dXJucyAwICgw eDApDQpzeXNjYWxsIHNpZ2FjdGlvbigweDE0LDB4YmZiZmRhZTQsMHhiZmJm ZGFkOCkNCglyZXR1cm5zIDAgKDB4MCkNCnN5c2NhbGwgc2lnYWN0aW9uKDB4 MywweGJmYmZkYWRjLDB4YmZiZmRhZDApDQoJcmV0dXJucyAwICgweDApDQpz eXNjYWxsIHNpZ2FjdGlvbigweDIsMHhiZmJmZGFkNCwweGJmYmZkYWM4KQ0K CXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBzaWdhY3Rpb24oMHgxLDB4YmZi ZmRhY2MsMHhiZmJmZGFjMCkNCglyZXR1cm5zIDAgKDB4MCkNCnN5c2NhbGwg c2lnYWN0aW9uKDB4ZCwweGJmYmZkYWU0LDB4YmZiZmRhZDgpDQoJcmV0dXJu cyAwICgweDApDQpzeXNjYWxsIHNpZ2FjdGlvbigweGUsMHhiZmJmZGFkYyww eGJmYmZkYWQwKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBzaWdhY3Rp b24oMHgxZSwweGJmYmZkYWQ0LDB4YmZiZmRhYzgpDQoJcmV0dXJucyAwICgw eDApDQpzeXNjYWxsIHNpZ3Byb2NtYXNrKDB4MSwweDIwMDAwMDAwKQ0KCXJl dHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBmb3JrKCkNCglyZXR1cm5zIDMxNiAo MHgxM2MpDQpzeXNjYWxsIHdhaXQ0KDB4ZmZmZmZmZmYsMHg4MDRjMjI0LDB4 MSwweDApDQoJcmV0dXJucyAwICgweDApDQoNCnN5c2NhbGwgd3JpdGUoMiww eDgwNGJjZWIsMSkNCglyZXR1cm5zIDEgKDB4MSkNCnN5c2NhbGwgc2V0aXRp bWVyKDB4MCwweGJmYmZkYWIwLDB4YmZiZmRhYTApDQoJcmV0dXJucyAwICgw eDApDQpTSUdOQUwgMzANClNJR05BTCAzMA0KU0lHTkFMIDMwDQpzeXNjYWxs IHNpZ3N1c3BlbmQoMHgwKQ0KCWVycm5vIDQgJ0ludGVycnVwdGVkIHN5c3Rl bSBjYWxsJw0Kc3lzY2FsbCBzaWdyZXR1cm4oMHhiZmJmZGE2MCkNCgllcnJu byA0ICdJbnRlcnJ1cHRlZCBzeXN0ZW0gY2FsbCcNCg0KWEZyZWU4NiBWZXJz aW9uIDMuMy4zLjEgLyBYIFdpbmRvdyBTeXN0ZW0NCihwcm90b2NvbCBWZXJz aW9uIDExLCByZXZpc2lvbiAwLCB2ZW5kb3IgcmVsZWFzZSA2MzAwKQ0KUmVs ZWFzZSBEYXRlOiBKYW51YXJ5IDQgMTk5OQ0KCUlmIHRoZSBzZXJ2ZXIgaXMg b2xkZXIgdGhhbiA2LTEyIG1vbnRocywgb3IgaWYgeW91ciBjYXJkIGlzIG5l d2VyDQoJdGhhbiB0aGUgYWJvdmUgZGF0ZSwgbG9vayBmb3IgYSBuZXdlciB2 ZXJzaW9uIGJlZm9yZSByZXBvcnRpbmcNCglwcm9ibGVtcy4gIChzZWUgaHR0 cDovL3d3dy5YRnJlZTg2Lk9yZy9GQVEpDQpPcGVyYXRpbmcgU3lzdGVtOiBM aW51eCAyLjAuMzIgaTY4NiBbRUxGXSANCkNvbmZpZ3VyZWQgZHJpdmVyczoN CiAgVk13YXJlOiBzZXJ2ZXIgZm9yIFZNd2FyZSB2aXJ0dWFsIGdyYXBoaWNz IGFkYXB0b3JzIChQYXRjaGxldmVsIDApDQoNCkZhdGFsIHNlcnZlciBlcnJv cjoNCnhmODZPcGVuQ29uc29sZTogQ2Fubm90IG9wZW4gL2Rldi90dHkwIChO byBzdWNoIGZpbGUgb3IgZGlyZWN0b3J5KQ0KDQoNCldoZW4gcmVwb3J0aW5n IGEgcHJvYmxlbSByZWxhdGVkIHRvIGEgc2VydmVyIGNyYXNoLCBwbGVhc2Ug c2VuZA0KdGhlIGZ1bGwgc2VydmVyIG91dHB1dCwgbm90IGp1c3QgdGhlIGxh c3QgbWVzc2FnZXMNCg0Kc3lzY2FsbCBzZXRpdGltZXIoMHgwLDB4YmZiZmRh YTgsMHhiZmJmZGE5OCkNCglyZXR1cm5zIDAgKDB4MCkNCnN5c2NhbGwgc2ln cHJvY21hc2soMHgzLDB4MCkNCglyZXR1cm5zIDUzNjg3MDkxMiAoMHgyMDAw MDAwMCkNCnN5c2NhbGwgYnJlYWsoMHg4MDUwMDAwKQ0KCXJldHVybnMgMCAo MHgwKQ0Kc3lzY2FsbCBicmVhaygweDgwNTEwMDApDQoJcmV0dXJucyAwICgw eDApDQpzeXNjYWxsIF9fc3lzY3RsKDB4YmZiZmQ3MDgsMHgyLDB4YmZiZmQ3 NTgsMHhiZmJmZDcwNCwweDAsMHgwKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lz Y2FsbCBicmVhaygweDgwNTIwMDApDQoJcmV0dXJucyAwICgweDApDQpzeXNj YWxsIHNvY2tldCgweDEsMHgxLDB4MCkNCglyZXR1cm5zIDMgKDB4MykNCnN5 c2NhbGwgX19zeXNjdGwoMHhiZmJmZDcyYywweDIsMHhiZmJmZDc3YywweGJm YmZkNzI4LDB4MCwweDApDQoJcmV0dXJucyAwICgweDApDQpzeXNjYWxsIF9f c3lzY3RsKDB4YmZiZmQ2NTQsMHgyLDB4YmZiZmQ2ZjAsMHhiZmJmZDY1MCww eDAsMHgwKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBjb25uZWN0KDB4 MywweGJmYmZkODE0LDB4MTMpDQoJcmV0dXJucyAwICgweDApDQpzeXNjYWxs IF9fc3lzY3RsKDB4YmZiZmQ3NDQsMHgyLDB4YmZiZmQ3ODgsMHhiZmJmZDc0 MCwweDAsMHgwKQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCBmY250bCgw eDMsMHgyLDB4MSkNCglyZXR1cm5zIDAgKDB4MCkNCnN5c2NhbGwgYWNjZXNz KDB4ODA0ZDEwMCwweDQpDQoJZXJybm8gMiAnTm8gc3VjaCBmaWxlIG9yIGRp cmVjdG9yeScNCnN5c2NhbGwgd3JpdGV2KDB4MywweGJmYmZkOTcwLDB4MSkN CglyZXR1cm5zIDEyICgweGMpDQpzeXNjYWxsIGZjbnRsKDB4MywweDQsMHg0 KQ0KCXJldHVybnMgMCAoMHgwKQ0Kc3lzY2FsbCByZWFkKDB4MywweGJmYmZk YTJjLDB4OCkNCgllcnJubyAzNSAnUmVzb3VyY2UgdGVtcG9yYXJpbHkgdW5h dmFpbGFibGUnDQpTSUdOQUwgMjANCnN5c2NhbGwgc2VsZWN0KDB4NCwweGJm YmZkOTA4LDB4MCwweDAsMHgwKQ0KCXJldHVybnMgMSAoMHgxKQ0Kc3lzY2Fs bCByZWFkKDB4MywweGJmYmZkYTJjLDB4OCkNCglyZXR1cm5zIDAgKDB4MCkN ClggY29ubmVjdGlvbiB0byA6MC4wIGJyb2tlbiAoZXhwbGljaXQga2lsbCBv ciBzZXJ2ZXIgc2h1dGRvd24pLg0NCnN5c2NhbGwgd3JpdGUoMiwweGJmYmZk MjMwLDY1KQ0KCXJldHVybnMgNjUgKDB4NDEpDQpzeXNjYWxsIGV4aXQoMHgx KQ0KCXByb2Nlc3MgZXhpdCwgcnZhbCA9IDI1Ng0K --0-169768575-933691257=:71237-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 8: 9: 2 1999 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 8C97C14F51 for ; Tue, 3 Aug 1999 08:08:54 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-7.ucdavis.edu [169.237.16.135]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA69511; Tue, 3 Aug 1999 08:08:12 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA36225; Tue, 3 Aug 1999 08:08:09 -0700 (PDT) (envelope-from obrien) Date: Tue, 3 Aug 1999 08:08:09 -0700 From: "David O'Brien" To: Maxim Sobolev Cc: current@FreeBSD.ORG Subject: Re: Sh still is not working for MAKEDEV Message-ID: <19990803080809.A36200@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <199908030128.SAA09463@rah.star-gate.com> <37A67EA2.A0A3F37C@altavista.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <37A67EA2.A0A3F37C@altavista.net>; from Maxim Sobolev on Tue, Aug 03, 1999 at 08:31:14AM +0300 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 > It seems like a bug in egcs which broke sh when "-march=pentium" option > is used while -O? level doesn't really matter. Any ideas on how to > track it down? Wait. GCC-2.95 (what would have been EGCS-1.2) will be released RSN. There has been *major* changes from EGCS-1.1.2 (the version in our base src tree). To spend time finding bugs in EGCS-1.1.2 would be a serious waste of time. You can install the latest ``egcs-devel'' and see if the bug remains. If so, then a bug report to the GCC people would be appropriate (but find a small example that shows the bug). -- -- David (obrien@NUXI.com -or- obrien@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 Aug 3 8:59:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id E4281152D4; Tue, 3 Aug 1999 08:59:35 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id KAA25560; Tue, 3 Aug 1999 10:58:49 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.8.5/8.6.4) id KAA17356; Tue, 3 Aug 1999 10:58:46 -0500 (CDT) Message-ID: <19990803105845.19595@right.PCS> Date: Tue, 3 Aug 1999 10:58:45 -0500 From: Jonathan Lemon To: Mike Smith Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: APM related panic References: <37A22819.DD36695B@altavista.net> <199908020520.WAA01521@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199908020520.WAA01521@dingo.cdrom.com>; from Mike Smith on Aug 08, 1999 at 10:20:38PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 08, 1999 at 10:20:38PM -0700, Mike Smith wrote: > > Jonathan; just some context, this is with your old 16-bit-protmode > patches, spiffed up for -current, which I committed late last week. Heh. I had just about forgotten about this patchset. I was somwehat under the impression it wasn't needed any more, what with the capabilities of the new loader. > > apm: CS_limit=0x0, DS_limit=0x0 > > These limits look pretty suspect, although the code segment below looks > OK. Yea, I see the later commits that force it to 0xffff; that is probably for the best, rather than trusting the BIOS. > > Fatal trap 9: general protection fault while in kernel mode > > instruction pointer = 0x48:0x8034 > > stack pointer = 0x10:0xc0279e98 > > frame pointer = 0x10:0x67890000 > > code segment = base 0xc00f0000, limit 0xffff, type 0x1b > > = DPL 0, pres 1, def32 1, gran 0 > > processor eflags = interrupt enabled, resume, IOPL = 0 > > Why is IOPL zero? I've also noted that making a bios16 call also > results in IOPL being zero (I have more that I want to take up with you > on that at some stage, since it's got me stumped, but one thing at a > time). The IOPL should be zero, in order to virtualize interrupts. If it's more than zero, the BIOS code can turn off interrupts, which isn't something we want to do. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 9:20:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 7B617152C7; Tue, 3 Aug 1999 09:20:19 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA22028; Tue, 3 Aug 1999 09:18:34 -0700 (PDT) (envelope-from dillon) Date: Tue, 3 Aug 1999 09:18:34 -0700 (PDT) From: Matthew Dillon Message-Id: <199908031618.JAA22028@apollo.backplane.com> To: "Eric J. Chet" Cc: marcel@FreeBSD.ORG, phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VMware X11 and -current References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :--0-169768575-933691257=:71237 :Content-Type: TEXT/PLAIN; charset=US-ASCII : :Hello : I have been using FreeBSD under vmware for a few weeks now, :running 3.2R. Everything has been running good including X11. I upgraded :to -current and the linux XF86_vmware server stopped working. When I try :and start the xserver I get an error "xf86OpenConsole: cannot open :/dev/tty0. I'm running -current as of 8/1/99 with the latest linux_base :port. Try creating a softlink from /dev/console to /dev/tty0. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 9:31: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.189]) by hub.freebsd.org (Postfix) with SMTP id 97BEB14C42 for ; Tue, 3 Aug 1999 09:31:04 -0700 (PDT) (envelope-from ejc@bazzle.com) Received: (qmail 72160 invoked from network); 3 Aug 1999 16:30:26 -0000 Received: from gargoyle.bazzle.com (206.103.246.189) by gargoyle.bazzle.com with SMTP; 3 Aug 1999 16:30:26 -0000 Date: Tue, 3 Aug 1999 12:30:25 -0400 (EDT) From: "Eric J. Chet" To: Matthew Dillon Cc: marcel@FreeBSD.ORG, phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VMware X11 and -current In-Reply-To: <199908031618.JAA22028@apollo.backplane.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 Tue, 3 Aug 1999, Matthew Dillon wrote: > > :--0-169768575-933691257=:71237 > :Content-Type: TEXT/PLAIN; charset=US-ASCII > : > :Hello > : I have been using FreeBSD under vmware for a few weeks now, > :running 3.2R. Everything has been running good including X11. I upgraded > :to -current and the linux XF86_vmware server stopped working. When I try > :and start the xserver I get an error "xf86OpenConsole: cannot open > :/dev/tty0. I'm running -current as of 8/1/99 with the latest linux_base > :port. > > Try creating a softlink from /dev/console to /dev/tty0. > > -Matt > Hello Matt I tried that, it then can't find /dev/tty4. If I also symlink tty4 it will panic. Lets see if I can get a dump. Ideas? Eric Chet -> ejc@bazzle.com ejc@FreeBSD.ORG echet@cms.cendant.com Senior Object Oriented Developer - Specializing in OOA, OOD, C++, Java, CORBA Kenpo JuJitsu the Ultimate in Self Defense, Tai Chi for Life cat man du : where UNIX geeks go when they die To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 9:47: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A4A521505C; Tue, 3 Aug 1999 09:46:46 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id JAA22272; Tue, 3 Aug 1999 09:45:46 -0700 (PDT) (envelope-from dillon) Date: Tue, 3 Aug 1999 09:45:46 -0700 (PDT) From: Matthew Dillon Message-Id: <199908031645.JAA22272@apollo.backplane.com> To: "Eric J. Chet" Cc: marcel@FreeBSD.ORG, phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VMware X11 and -current References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :to -current and the linux XF86_vmware server stopped working. When I try :> :and start the xserver I get an error "xf86OpenConsole: cannot open :> :/dev/tty0. I'm running -current as of 8/1/99 with the latest linux_base :> :port. :> :> Try creating a softlink from /dev/console to /dev/tty0. :> :> -Matt :> :Hello Matt : : I tried that, it then can't find /dev/tty4. If I also symlink :tty4 it will panic. Lets see if I can get a dump. : :Ideas? Symlinking /dev/tty4 to what? You should be symlinking /dev/tty4 to /dev/ttyv4. I'm not up on the linux emulation so the best I can do is provide general ideas. -Matt Matthew Dillon :Eric Chet -> ejc@bazzle.com ejc@FreeBSD.ORG echet@cms.cendant.com :Senior Object Oriented Developer - Specializing in OOA, OOD, C++, Java, CORBA :Kenpo JuJitsu the Ultimate in Self Defense, Tai Chi for Life :cat man du : where UNIX geeks go when they die : : : :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 Aug 3 9:54: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rp-plus.de (clubserv.rp-online.de [149.221.232.11]) by hub.freebsd.org (Postfix) with ESMTP id 88EDD14DD3 for ; Tue, 3 Aug 1999 09:53:59 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from neutron.cichlids.com (as5-040.rp-plus.de [149.221.239.104]) by mail.rp-plus.de (8.9.1a/8.9.1) with ESMTP id SAA01069 for ; Tue, 3 Aug 1999 18:54:01 +0200 (METDST) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (8.9.3/8.9.1) with ESMTP id OAA62938 for ; Tue, 3 Aug 1999 14:31:38 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id OAA01797 for freebsd-current@freebsd.org; Tue, 3 Aug 1999 14:30:48 +0200 (CEST) (envelope-from alex) From: Alexander Langer Date: Tue, 3 Aug 1999 14:30:47 +0200 To: freebsd-current@freebsd.org Subject: "w" date Message-ID: <19990803143047.A1776@cichlids.cichlids.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95i X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! bash-2.02# w 2:26PM up 30 days, 4:13, 4 users, load averages: 2.85, 2.25, 2.09 USER TTY FROM LOGIN@ IDLE WHAT root v0 - Mon07PM 2:14 (bash) root v1 - 18Jul99 16days (bash) alex v2 - Tue05PM 6days (bash) root p0 0.10 04Nov35 - (w) bash-2.02# date Tue Aug 3 14:26:47 CEST 1999 Take a look at the last one: p0. I logged in ~5 min before. The date confuses me. It´s a FreeBSD neutron.cichlids.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sun Jul 4 12:04:20 CEST 1999 root@:/usr/src/current/src/sys/compile/neutron i386 it doesn´t matter for me, maybe it´s already fixed. I was just wondering. Alex -- ************** I doubt, therefore I might be. ************** *** Send email to to get PGP-Key *** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 10:43:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.189]) by hub.freebsd.org (Postfix) with SMTP id ABE3914E9B for ; Tue, 3 Aug 1999 10:43:20 -0700 (PDT) (envelope-from ejc@bazzle.com) Received: (qmail 72852 invoked from network); 3 Aug 1999 17:42:58 -0000 Received: from gargoyle.bazzle.com (206.103.246.189) by gargoyle.bazzle.com with SMTP; 3 Aug 1999 17:42:58 -0000 Date: Tue, 3 Aug 1999 13:42:58 -0400 (EDT) From: "Eric J. Chet" To: Matthew Dillon Cc: marcel@FreeBSD.ORG, phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VMware X11 and -current In-Reply-To: <199908031645.JAA22272@apollo.backplane.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 Tue, 3 Aug 1999, Matthew Dillon wrote: > :> :to -current and the linux XF86_vmware server stopped working. When I try > :> :and start the xserver I get an error "xf86OpenConsole: cannot open > :> :/dev/tty0. I'm running -current as of 8/1/99 with the latest linux_base > :> :port. > :> > :> Try creating a softlink from /dev/console to /dev/tty0. > :> > :> -Matt > :> > :Hello Matt > : > : I tried that, it then can't find /dev/tty4. If I also symlink > :tty4 it will panic. Lets see if I can get a dump. > : > :Ideas? > > Symlinking /dev/tty4 to what? You should be symlinking /dev/tty4 to > /dev/ttyv4. It will panic if I symlink tty4 to ttyv4 or console. > > I'm not up on the linux emulation so the best I can do is provide > general ideas. Thanks for your help, this is the first time I have had to look at the linux emulation code. Thanks, ejc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 11: 4:15 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 97CDE152E1 for ; Tue, 3 Aug 1999 11:04:08 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id NAA26197; Tue, 3 Aug 1999 13:03:29 -0500 (CDT) Received: (from jlemon@localhost) by right.PCS (8.8.5/8.6.4) id NAA08991; Tue, 3 Aug 1999 13:03:27 -0500 (CDT) Message-ID: <19990803130326.56771@right.PCS> Date: Tue, 3 Aug 1999 13:03:26 -0500 From: Jonathan Lemon To: Mike Smith Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: APM related panic References: <19990803105845.19595@right.PCS> <199908031657.JAA03722@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 In-Reply-To: <199908031657.JAA03722@dingo.cdrom.com>; from Mike Smith on Aug 08, 1999 at 09:57:10AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Aug 08, 1999 at 09:57:10AM -0700, Mike Smith wrote: > > > > Fatal trap 9: general protection fault while in kernel mode > > > > instruction pointer = 0x48:0x8034 > > > > stack pointer = 0x10:0xc0279e98 > > > > frame pointer = 0x10:0x67890000 > > > > code segment = base 0xc00f0000, limit 0xffff, type 0x1b > > > > = DPL 0, pres 1, def32 1, gran 0 > > > > processor eflags = interrupt enabled, resume, IOPL = 0 > > > > > > Why is IOPL zero? I've also noted that making a bios16 call also > > > results in IOPL being zero (I have more that I want to take up with you > > > on that at some stage, since it's got me stumped, but one thing at a > > > time). > > > > The IOPL should be zero, in order to virtualize interrupts. If it's > > more than zero, the BIOS code can turn off interrupts, which isn't > > something we want to do. > > Ok. I'm presuming then that we have a tss in place that allows I/O > operations? That was my major concern... Nevermind, I was thinking of vm86 mode. In vm86 mode, the IOPL doesn't have anything to do with I/O, and we use the I/O permission bitmaps. There isn't an I/O bitmap for the kernel (only user processes), so the kernel isn't able to make vm86 I/O calls at this point. This could be fixed, but I haven't seen the need for it yet. However, this is 16-bit protected mode, which (other than the addressing size) is exactly the same as 32-bit kernel mode. Thus the IOPL doesn't really matter, since all the bios selectors are set up with kernel privs (in ring 0). -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 11:10:57 1999 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 611ED152D2; Tue, 3 Aug 1999 11:10:41 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id TAA84037; Tue, 3 Aug 1999 19:04:20 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id QAA47237; Tue, 3 Aug 1999 16:42:07 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Tue, 3 Aug 1999 16:42:07 +0100 From: Nik Clayton To: Poul-Henning Kamp Cc: stable@freebsd.org, current@freebsd.org Subject: Re: Sitting inside, looking out... Message-ID: <19990803164207.A46171@kilt.nothing-going-on.org> References: <14964.933450146.1@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <14964.933450146.1@critter.freebsd.dk>; from Poul-Henning Kamp on Sat, Jul 31, 1999 at 09:42:26PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just for completeness; On Sat, Jul 31, 1999 at 09:42:26PM +0200, Poul-Henning Kamp wrote: > 2. Who are the committers anyway ? > ---------------------------------- > > All the noise about Matt Dillons commit bit have generated a lot > of questions about who gets to be committers, so here is a little > insight into the process of appointing a committer: > > Generally we in core operate with three kinds of committers: > > Ports committers > These are people who maintain one or more ports. > > If Asami-san wants to glue a bit on somebody, we will > generally let him. > > Limited scope committers > These are people who maintain some specific bit of the tree, > typically a subsystem they are (co-)authors of. A good example > is the HARP ATM stack, which Mike Spengler is taking care of > (and many thanks for that Mike!) > > Since these people are taken on board with a explicitly > stated limited scope, we are more relaxed about them than > we are about the last category. People have been known > to successfully sneak out from this category and into: > > Committers at large > These are the people who persist in sending well documented > PRs containing correct patches. The only way we have > devised so far for ridding ourselves of this kind of > annoying behaviour is to say "Here! you're a committer, > now close your own PRs!" :-) Doc committers Contributors to the Documentation Project. Generally stick within doc/ and www/, but have been known to wander in to the src/ hierarchy when manual pages need fixing up. There are generally two ways to become a doc committer. The first is the same as "Committers at large". Send enough good quality doc/ PRs and I'll get bored of committing them soon enough. The second is if you are maintaining a particular language translation of the FreeBSD docs (FAQ, Handbook, man pages, and so on). At least, that's my take on it. > NOTE: If somebody can find a sponsor for it, I would really > like to offer an "official FreeBSD Committer sweat-shirt" > to each and every single committer. Luxury cars, free > vacations and suitcases filled with cash would also do. What an excellent idea. How about the FreeBSD Project coming up with the artwork, and then 'licensing' it to each user group? The user groups handle the printing and distribution of the shirts as necessary (with appropriate local modifications as necessary) and probably charge $LOCAL_CURRENCY 1.00 or 2.00 more than the cost of the shirts, which gets punted back to the Project. I know I'd pay. Hmm. "I submitted a PR to FreeBSD, and all I got was this lousy t-shirt." > PS: See you all at the FreeBSD-con in October! http://www.freebsdcon.org/ Absolutely. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 11:16:39 1999 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 68B67152F8 for ; Tue, 3 Aug 1999 11:16:34 -0700 (PDT) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1002) id 02D9B75D; Tue, 3 Aug 1999 11:15:12 -0700 (PDT) Date: Tue, 3 Aug 1999 11:15:12 -0700 From: Chris Piazza To: David O'Brien Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: Sh still is not working for MAKEDEV Message-ID: <19990803111512.G27630@norn.ca.eu.org> References: <199908030128.SAA09463@rah.star-gate.com> <37A67EA2.A0A3F37C@altavista.net> <19990803080809.A36200@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990803080809.A36200@dragon.nuxi.com>; from David O'Brien on Tue, Aug 03, 1999 at 08:08:09AM -0700 X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 03, 1999 at 08:08:09AM -0700, David O'Brien wrote: > > It seems like a bug in egcs which broke sh when "-march=pentium" option > > is used while -O? level doesn't really matter. Any ideas on how to > > track it down? > > Wait. GCC-2.95 (what would have been EGCS-1.2) will be released RSN. It already was, wasn't it? http://egcs.cygnus.com/gcc-2.95/gcc-2.95.html "July 31, 1999 The GNU project and the GCC/EGCS developers are pleased to announce the release of GCC version 2.95." ftp://ftp.gnu.org/pub/gnu/gcc/gcc-2.95.tar.gz -Chris -- cpiazza@home.net cpiazza@FreeBSD.org "It's better to be quotable than to be honest." --Tom Stoppard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 11:17:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from pop3-3.enteract.com (pop3-3.enteract.com [207.229.143.32]) by hub.freebsd.org (Postfix) with SMTP id 7631815329 for ; Tue, 3 Aug 1999 11:17:20 -0700 (PDT) (envelope-from dscheidt@enteract.com) Received: (qmail 56123 invoked from network); 3 Aug 1999 18:17:05 -0000 Received: from shell-3.enteract.com (dscheidt@207.229.143.42) by pop3-3.enteract.com with SMTP; 3 Aug 1999 18:17:05 -0000 Date: Tue, 3 Aug 1999 13:17:05 -0500 (CDT) From: David Scheidt To: Nik Clayton Cc: Poul-Henning Kamp , stable@freebsd.org, current@freebsd.org Subject: Re: Sitting inside, looking out... In-Reply-To: <19990803164207.A46171@kilt.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 [moved to -chat] On Tue, 3 Aug 1999, Nik Clayton wrote: > > Hmm. "I submitted a PR to FreeBSD, and all I got was this lousy t-shirt." Wouldn't we rather have "I fixed a PR in FreeBSD..."? David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 11:19:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 08F90152FC; Tue, 3 Aug 1999 11:19:41 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id LAA73177; Tue, 3 Aug 1999 11:18:37 -0700 (PDT) From: Archie Cobbs Message-Id: <199908031818.LAA73177@bubba.whistle.com> Subject: Re: Panic plus advice needed In-Reply-To: <19990803092526.Z64532@freebie.lemis.com> from Greg Lehey at "Aug 3, 1999 09:25:26 am" To: grog@lemis.com (Greg Lehey) Date: Tue, 3 Aug 1999 11:18:37 -0700 (PDT) Cc: current@FreeBSD.ORG, bde@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 Greg Lehey writes: > > * if you still have exactly the same source tree and config file, > > recompile the kernel with -g to obtain the version with debugging symbols > > bde has reported that the code may not be identical when compiling for > debugging. It should be, but for obscure reasons it doesn't quite > make it. I'd be interested in seeing a pointer to those reasons, if you have one.. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 11:23:18 1999 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 37D9B152E0; Tue, 3 Aug 1999 11:23:10 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id UAA30737; Tue, 3 Aug 1999 20:22:55 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Nik Clayton Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... In-reply-to: Your message of "Tue, 03 Aug 1999 16:42:07 BST." <19990803164207.A46171@kilt.nothing-going-on.org> Date: Tue, 03 Aug 1999 20:22:55 +0200 Message-ID: <30735.933704575@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990803164207.A46171@kilt.nothing-going-on.org>, Nik Clayton writes: >Just for completeness; Yeah, sorry for leaving you gang out , but I didn't want to make it too long, the important thing was to get the three main kinds down, doc committers are pretty much the same story as the other two "limited scope" types. >At least, that's my take on it. > >> NOTE: If somebody can find a sponsor for it, I would really >> like to offer an "official FreeBSD Committer sweat-shirt" >> to each and every single committer. Luxury cars, free >> vacations and suitcases filled with cash would also do. > >How about the FreeBSD Project coming up with the >artwork, and then 'licensing' it to each user group? For it to have significance for the committers, it should be done in such a manner that only the committers get their hands on them. >Hmm. "I submitted a PR to FreeBSD, and all I got was this lousy t-shirt." Now, there's an idea :-) -- 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 Tue Aug 3 12: 2:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (Postfix) with ESMTP id CE4A714C06 for ; Tue, 3 Aug 1999 12:01:57 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id for ; Tue, 3 Aug 1999 15:00:35 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Tue, 3 Aug 1999 12:00:32 -0700 (PDT) Received: from localhost.pfcs.com [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Tue, 3 Aug 1999 15:00:31 -0400 (EDT) To: current@FreeBSD.ORG Subject: Re: Sh still is not working for MAKEDEV In-Reply-To: "David O'Brien"'s (obrien@NUXI.com) message dated Tue, 03 Aug 1999 08:08:09. <19990803080809.A36200@dragon.nuxi.com> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (20 Minutes to Nikko) (i386-unknown-freebsd2.2.8) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Tue, 03 Aug 1999 15:00:31 -0400 Message-ID: <15747.933706831@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG gcc-2.95 was released a couple of days ago. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 12: 9: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from kiwi.datasys.net (kiwi.datasys.net [209.119.145.2]) by hub.freebsd.org (Postfix) with ESMTP id E1A7315104 for ; Tue, 3 Aug 1999 12:08:42 -0700 (PDT) (envelope-from ayan@kiwi.datasys.net) Received: (from ayan@localhost) by kiwi.datasys.net (8.9.3/8.9.3) id PAA01343 for current@FreeBSD.org; Tue, 3 Aug 1999 15:08:39 -0400 (EDT) (envelope-from ayan) Date: Tue, 3 Aug 1999 15:08:39 -0400 (EDT) From: Ayan George Message-Id: <199908031908.PAA01343@kiwi.datasys.net> X-Mailer: Mail User's Shell (7.2.6 beta(5) 10/07/98) To: current@FreeBSD.org Subject: Re: VMware X11 and -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been wondering -- are there any plans for a FreeBSD version of VMware? -Ayan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 12:20:40 1999 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 410A015314 for ; Tue, 3 Aug 1999 12:20:38 -0700 (PDT) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1002) id 2988075D; Tue, 3 Aug 1999 12:20:06 -0700 (PDT) Date: Tue, 3 Aug 1999 12:20:06 -0700 From: Chris Piazza To: Ayan George Cc: current@FreeBSD.ORG Subject: Re: VMware X11 and -current Message-ID: <19990803122006.H27630@norn.ca.eu.org> References: <199908031908.PAA01343@kiwi.datasys.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908031908.PAA01343@kiwi.datasys.net>; from Ayan George on Tue, Aug 03, 1999 at 03:08:39PM -0400 X-Operating-System: FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 03, 1999 at 03:08:39PM -0400, Ayan George wrote: > I've been wondering -- are there any plans for a FreeBSD version > of VMware? > It's not us you should be asking. Ask the makers of VMWare. -Chris -- cpiazza@home.net cpiazza@FreeBSD.org "It's better to be quotable than to be honest." --Tom Stoppard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 12:21:49 1999 Delivered-To: freebsd-current@freebsd.org Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (Postfix) with ESMTP id 978A4152D3 for ; Tue, 3 Aug 1999 12:21:42 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id JAA03722; Tue, 3 Aug 1999 09:57:10 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199908031657.JAA03722@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jonathan Lemon Cc: Maxim Sobolev , current@FreeBSD.ORG Subject: Re: APM related panic In-reply-to: Your message of "Tue, 03 Aug 1999 10:58:45 CDT." <19990803105845.19595@right.PCS> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 03 Aug 1999 09:57:10 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Fatal trap 9: general protection fault while in kernel mode > > > instruction pointer = 0x48:0x8034 > > > stack pointer = 0x10:0xc0279e98 > > > frame pointer = 0x10:0x67890000 > > > code segment = base 0xc00f0000, limit 0xffff, type 0x1b > > > = DPL 0, pres 1, def32 1, gran 0 > > > processor eflags = interrupt enabled, resume, IOPL = 0 > > > > Why is IOPL zero? I've also noted that making a bios16 call also > > results in IOPL being zero (I have more that I want to take up with you > > on that at some stage, since it's got me stumped, but one thing at a > > time). > > The IOPL should be zero, in order to virtualize interrupts. If it's > more than zero, the BIOS code can turn off interrupts, which isn't > something we want to do. Ok. I'm presuming then that we have a tss in place that allows I/O operations? That was my major concern... -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 Tue Aug 3 13:25:58 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 6071C15110 for ; Tue, 3 Aug 1999 13:25:50 -0700 (PDT) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail1.its.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA47410; Tue, 3 Aug 1999 16:25:32 -0400 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <199908031908.PAA01343@kiwi.datasys.net> References: <199908031908.PAA01343@kiwi.datasys.net> Date: Tue, 3 Aug 1999 16:25:40 -0400 To: Ayan George , current@FreeBSD.ORG From: Garance A Drosihn Subject: Re: VMware X11 and -current Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:08 PM -0400 8/3/99, Ayan George wrote: >I've been wondering -- are there any plans for a FreeBSD version >of VMware? The makers of VMware are probably wondering if they would sell enough copies of a FreeBSD-based version. If you would buy such a product, then let them know. Check www.vmware.com for the email address that would be interested. If you're asking for a freely-available open-source BSD-license product which does the same things vmware does, I am afraid I don't know what projects are underway. --- 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 Tue Aug 3 13:59:18 1999 Delivered-To: freebsd-current@freebsd.org Received: from lcremeans.erols.com (lcremeans.erols.com [216.164.87.29]) by hub.freebsd.org (Postfix) with ESMTP id DD205150AD for ; Tue, 3 Aug 1999 13:59:10 -0700 (PDT) (envelope-from lee@lcremeans.erols.com) Received: (from lee@localhost) by lcremeans.erols.com (8.9.3/8.9.3) id QAA55896; Tue, 3 Aug 1999 16:56:54 -0400 (EDT) (envelope-from lee) Message-ID: <19990803165654.A55879@erols.com> Date: Tue, 3 Aug 1999 16:56:54 -0400 From: Lee Cremeans To: Garance A Drosihn , Ayan George , current@FreeBSD.ORG Subject: Re: VMware X11 and -current References: <199908031908.PAA01343@kiwi.datasys.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Garance A Drosihn on Tue, Aug 03, 1999 at 04:25:40PM -0400 X-OS: FreeBSD 3.0-STABLE Organization: My room? Are you crazy? :) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 03, 1999 at 04:25:40PM -0400, Garance A Drosihn wrote: > If you're asking for a freely-available open-source BSD-license > product which does the same things vmware does, I am afraid I > don't know what projects are underway. The only one I know of at all is freemware (www.freemware.org), which was started by the author of Bochs and is still very much pre-alpha. It's under LGPL. -lee -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | | lcremeans@erols.com | http://wakky.dyndns.org/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 14:15: 5 1999 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 7F43914F75; Tue, 3 Aug 1999 14:14:54 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 3 Aug 1999 22:14:33 +0100 (BST) Date: Tue, 3 Aug 1999 22:14:33 +0100 From: David Malone To: Archie Cobbs Cc: grog@lemis.com, current@FreeBSD.ORG, bde@FreeBSD.ORG Subject: Re: Panic plus advice needed Message-ID: <19990803221433.A36019@walton.maths.tcd.ie> References: <19990803092526.Z64532@freebie.lemis.com> <199908031818.LAA73177@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <199908031818.LAA73177@bubba.whistle.com>; from Archie Cobbs on Tue, Aug 03, 1999 at 11:18:37AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 03, 1999 at 11:18:37AM -0700, Archie Cobbs wrote: > Greg Lehey writes: > > > * if you still have exactly the same source tree and config file, > > > recompile the kernel with -g to obtain the version with debugging symbols > > > > bde has reported that the code may not be identical when compiling for > > debugging. It should be, but for obscure reasons it doesn't quite > > make it. > > I'd be interested in seeing a pointer to those reasons, if you have one.. One reason adding -g doesn't work at times is if the kernel is recompiled by a person with a different length username. vers.c is produced with a string which is a different length which screws up the offsets. Maybe newvers.sh should pad usernames to the legal max? Maybe we should warn people to touch vers.c after editing the Makefile? David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 14:33:34 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id A0A0314BE9; Tue, 3 Aug 1999 14:33:27 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id OAA76026; Tue, 3 Aug 1999 14:31:36 -0700 (PDT) From: Archie Cobbs Message-Id: <199908032131.OAA76026@bubba.whistle.com> Subject: Re: Panic plus advice needed In-Reply-To: <19990803221433.A36019@walton.maths.tcd.ie> from David Malone at "Aug 3, 1999 10:14:33 pm" To: dwmalone@maths.tcd.ie (David Malone) Date: Tue, 3 Aug 1999 14:31:36 -0700 (PDT) Cc: archie@whistle.com (Archie Cobbs), grog@lemis.com, current@FreeBSD.ORG, bde@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 David Malone writes: > > > bde has reported that the code may not be identical when compiling for > > > debugging. It should be, but for obscure reasons it doesn't quite > > > make it. > > > > I'd be interested in seeing a pointer to those reasons, if you have one.. > > One reason adding -g doesn't work at times is if the kernel is > recompiled by a person with a different length username. vers.c > is produced with a string which is a different length which screws > up the offsets. > > Maybe newvers.sh should pad usernames to the legal max? Maybe we should > warn people to touch vers.c after editing the Makefile? That would be really helpful to us actually and I imagine lots of people. In fact, you don't need to pad the username, just add the right number of zeroes to the end of the string, eg. const char *uname = "..blah username blah.." "\0\0\0\0\0"; -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 15:11:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 7E2A114E03; Tue, 3 Aug 1999 15:11:37 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id AAA29671; Wed, 4 Aug 1999 00:03:31 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id AAA54268; Wed, 4 Aug 1999 00:02:59 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id AAA25546; Wed, 4 Aug 1999 00:03:50 +0200 (CEST) (envelope-from ticso) Date: Wed, 4 Aug 1999 00:03:49 +0200 From: Bernd Walter To: "Eric J. Chet" Cc: Matthew Dillon , marcel@FreeBSD.ORG, phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VMware X11 and -current Message-ID: <19990804000348.A25514@cicely8.cicely.de> References: <199908031618.JAA22028@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Eric J. Chet on Tue, Aug 03, 1999 at 12:30:25PM -0400 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Aug 03, 1999 at 12:30:25PM -0400, Eric J. Chet wrote: > On Tue, 3 Aug 1999, Matthew Dillon wrote: > > > > > :--0-169768575-933691257=:71237 > > :Content-Type: TEXT/PLAIN; charset=US-ASCII > > : > > :Hello > > : I have been using FreeBSD under vmware for a few weeks now, > > :running 3.2R. Everything has been running good including X11. I upgraded > > :to -current and the linux XF86_vmware server stopped working. When I try > > :and start the xserver I get an error "xf86OpenConsole: cannot open > > :/dev/tty0. I'm running -current as of 8/1/99 with the latest linux_base > > :port. > > > > Try creating a softlink from /dev/console to /dev/tty0. > > > > -Matt > > > Hello Matt > > I tried that, it then can't find /dev/tty4. If I also symlink > tty4 it will panic. Lets see if I can get a dump. It needs ttyp0 as tty0 and so on. I tried it myself under current and got the X11 window. but it complained that it can't find /proc/cpuinfo. I never beleaved that it would work after that. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 16: 3:32 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id A74B514F38; Tue, 3 Aug 1999 16:03:27 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA24144; Tue, 3 Aug 1999 16:02:32 -0700 (PDT) (envelope-from dillon) Date: Tue, 3 Aug 1999 16:02:32 -0700 (PDT) From: Matthew Dillon Message-Id: <199908032302.QAA24144@apollo.backplane.com> To: Poul-Henning Kamp Cc: Nik Clayton , stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... References: <30735.933704575@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would recommend simply having a 'FreeBSD' T-Shirt. None of this 'committers' or 'core' stuff. -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 Tue Aug 3 16:22:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 455F014F7D; Tue, 3 Aug 1999 16:22:40 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id QAA80191; Tue, 3 Aug 1999 16:21:53 -0700 (PDT) From: Archie Cobbs Message-Id: <199908032321.QAA80191@bubba.whistle.com> Subject: Re: Panic plus advice needed In-Reply-To: <199908032131.OAA76026@bubba.whistle.com> from Archie Cobbs at "Aug 3, 1999 02:31:36 pm" To: archie@whistle.com (Archie Cobbs) Date: Tue, 3 Aug 1999 16:21:53 -0700 (PDT) Cc: dwmalone@maths.tcd.ie (David Malone), grog@lemis.com, current@FreeBSD.ORG, bde@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 Archie Cobbs writes: > > One reason adding -g doesn't work at times is if the kernel is > > recompiled by a person with a different length username. vers.c > > is produced with a string which is a different length which screws > > up the offsets. > > > > Maybe newvers.sh should pad usernames to the legal max? Maybe we should > > warn people to touch vers.c after editing the Makefile? > > That would be really helpful to us actually and I imagine lots of people. > In fact, you don't need to pad the username, just add the right number of > zeroes to the end of the string, eg. Any objections to the patch below? And a related question: why not define ostype[], et.al. as "const" ? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com Index: newvers.sh =================================================================== RCS file: /home/ncvs/src/sys/conf/newvers.sh,v retrieving revision 1.42 diff -u -r1.42 newvers.sh --- newvers.sh 1999/01/21 03:07:33 1.42 +++ newvers.sh 1999/08/03 23:20:32 @@ -34,6 +34,13 @@ # @(#)newvers.sh 8.1 (Berkeley) 4/20/94 # $Id: newvers.sh,v 1.42 1999/01/21 03:07:33 jkh Exp $ +# We use fixed size buffers so that the symbol table will remain the same +# no matter who does the build. These should be big enough to hold the +# corresponding strings, plus NUL. +TYPE_MAXBUF="8" +RELEASE_MAXBUF="32" +VERSION_MAXBUF="256" + TYPE="FreeBSD" REVISION="4.0" BRANCH="CURRENT" @@ -44,6 +51,20 @@ fi VERSION="${TYPE} ${RELEASE}" +# Check for overflow of fixed size string buffers +if [ ${#TYPE} -ge ${TYPE_MAXBUF} ]; then + echo "Error: increase TYPE_MAXBUF" + exit 1 +fi +if [ ${#RELEASE} -ge ${RELEASE_MAXBUF} ]; then + echo "Error: increase RELEASE_MAXBUF" + exit 1 +fi +if [ ${#VERSION} -ge ${VERSION_MAXBUF} ]; then + echo "Error: increase VERSION_MAXBUF" + exit 1 +fi + if [ "X${PARAMFILE}" != "X" ]; then RELDATE=$(awk '/__FreeBSD_version.*propagated to newvers/ {print $3}' \ ${PARAMFILE}) @@ -91,11 +112,11 @@ touch version v=`cat version` u=${USER-root} d=`pwd` h=`hostname` t=`date` echo "$COPYRIGHT" > vers.c -echo "char ostype[] = \"${TYPE}\";" >> vers.c -echo "char osrelease[] = \"${RELEASE}\";" >> vers.c +echo "char ostype[${TYPE_MAXBUF}] = \"${TYPE}\";" >> vers.c +echo "char osrelease[${RELEASE_MAXBUF}] = \"${RELEASE}\";" >> vers.c echo "int osreldate = ${RELDATE};" >> vers.c echo "char sccs[4] = { '@', '(', '#', ')' };" >>vers.c -echo "char version[] = \ +echo "char version[${VERSION_MAXBUF}] = \ \"${VERSION} #${v}: ${t}\\n ${u}@${h}:${d}\\n\";" >>vers.c echo `expr ${v} + 1` > version To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 17:28: 6 1999 Delivered-To: freebsd-current@freebsd.org Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.189]) by hub.freebsd.org (Postfix) with SMTP id B797B1538E for ; Tue, 3 Aug 1999 17:27:42 -0700 (PDT) (envelope-from ejc@bazzle.com) Received: (qmail 75680 invoked from network); 4 Aug 1999 00:27:35 -0000 Received: from gargoyle.bazzle.com (206.103.246.189) by gargoyle.bazzle.com with SMTP; 4 Aug 1999 00:27:35 -0000 Date: Tue, 3 Aug 1999 20:27:35 -0400 (EDT) From: "Eric J. Chet" To: Bernd Walter Cc: Matthew Dillon , marcel@FreeBSD.ORG, phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VMware X11 and -current In-Reply-To: <19990804000348.A25514@cicely8.cicely.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 Wed, 4 Aug 1999, Bernd Walter wrote: > It needs ttyp0 as tty0 and so on. > I tried it myself under current and got the X11 window. > but it complained that it can't find /proc/cpuinfo. > I never beleaved that it would work after that. Hello It should work, I used it under fbsd-3.2R for over two weeks with X11 without any problems. I guess I might have to down grade to 3.2R. Thanks, > > -- > B.Walter COSMO-Project http://www.cosmo-project.de > ticso@cicely.de Usergroup info@cosmo-project.de > Eric Chet -> ejc@bazzle.com ejc@FreeBSD.ORG echet@cms.cendant.com Senior Object Oriented Developer - Specializing in OOA, OOD, C++, Java, CORBA Kenpo JuJitsu the Ultimate in Self Defense, Tai Chi for Life cat man du : where UNIX geeks go when they die To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 18: 9:48 1999 Delivered-To: freebsd-current@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 79B6815114; Tue, 3 Aug 1999 18:09:44 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA17458; Tue, 3 Aug 1999 18:08:22 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199908040108.SAA17458@freeway.dcfinc.com> Subject: Re: Sitting inside, looking out... In-Reply-To: <199908032302.QAA24144@apollo.backplane.com> from Matthew Dillon at "Aug 3, 99 04:02:32 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 3 Aug 1999 18:08:22 -0700 (MST) Cc: phk@critter.freebsd.dk, nik@FreeBSD.ORG, stable@FreeBSD.ORG, current@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (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 As I recall, Matthew Dillon wrote: > I would recommend simply having a 'FreeBSD' T-Shirt. None of this > 'committers' or 'core' stuff. > > -Matt > Matthew Dillon > No, I think you missed the point. The T-shirt (or sweatshirt, or baseball cap or whatever) should be special, easily identified as special and available only to the group you're trying to incent/reward. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 18:23: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 943B715159; Tue, 3 Aug 1999 18:23:00 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id SAA25112; Tue, 3 Aug 1999 18:21:03 -0700 (PDT) (envelope-from dillon) Date: Tue, 3 Aug 1999 18:21:03 -0700 (PDT) From: Matthew Dillon Message-Id: <199908040121.SAA25112@apollo.backplane.com> To: "Chad R. Larson" Cc: phk@critter.freebsd.dk, nik@FreeBSD.ORG, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... References: <199908040108.SAA17458@freeway.dcfinc.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :As I recall, Matthew Dillon wrote: :> I would recommend simply having a 'FreeBSD' T-Shirt. None of this :> 'committers' or 'core' stuff. :> :> -Matt :> Matthew Dillon :> : :No, I think you missed the point. The T-shirt (or sweatshirt, or :baseball cap or whatever) should be special, easily identified as :special and available only to the group you're trying to :incent/reward. : : -crl :-- :Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? I understand the point. It's a bad idea. -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 Tue Aug 3 19:15: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 45FCA151EE; Tue, 3 Aug 1999 19:15:04 -0700 (PDT) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id TAA17617; Tue, 3 Aug 1999 19:14:22 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199908040214.TAA17617@freeway.dcfinc.com> Subject: Re: Sitting inside, looking out... In-Reply-To: <199908040121.SAA25112@apollo.backplane.com> from Matthew Dillon at "Aug 3, 99 06:21:03 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Tue, 3 Aug 1999 19:14:22 -0700 (MST) Cc: phk@critter.freebsd.dk, nik@FreeBSD.ORG, stable@FreeBSD.ORG, current@FreeBSD.ORG Reply-To: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (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 As I recall, Matthew Dillon wrote: > :No, I think you missed the point. The T-shirt (or sweatshirt, or > :baseball cap or whatever) should be special, easily identified as > :special and available only to the group you're trying to > :incent/reward. > : > : -crl > :-- > :Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? > > I understand the point. It's a bad idea. I disagree. I've used exactly that kind of incentive for my guys a number of times. The most coveted apparel around REZsolutions for a while was the undyed denem shirt with our logo and the phrase "REZsolutions Life Support Team" embroidered above the pocket, that we gave the SysAdm staff after a particularly long, hard implementation. Other departments would say, "Keen, how can I get one of those?" and the answer was, "You can't." The guys are proud to wear them. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 19:31:50 1999 Delivered-To: freebsd-current@freebsd.org Received: from snafu.adept.org (adsl-63-193-112-19.dsl.snfc21.pacbell.net [63.193.112.19]) by hub.freebsd.org (Postfix) with ESMTP id 53E8414E2A; Tue, 3 Aug 1999 19:31:44 -0700 (PDT) (envelope-from mike@snafu.adept.org) Received: from localhost (mike@localhost) by snafu.adept.org (8.9.3/8.9.3) with ESMTP id TAA13573; Tue, 3 Aug 1999 19:30:37 -0700 (PDT) Date: Tue, 3 Aug 1999 19:30:37 -0700 (PDT) From: Mike Hoskins To: Matthew Dillon Cc: "Chad R. Larson" , phk@critter.freebsd.dk, nik@FreeBSD.ORG, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... In-Reply-To: <199908040121.SAA25112@apollo.backplane.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 Tue, 3 Aug 1999, Matthew Dillon wrote: > :No, I think you missed the point. The T-shirt (or sweatshirt, or > :baseball cap or whatever) should be special, easily identified as > :special and available only to the group you're trying to > :incent/reward. > I understand the point. It's a bad idea. I understand both points... First, I think everyone seriously involved with development effort(s) deserves a big 'Thank you' and a pat on the back for putting up with a lot of the BS that goes on and spending sleepless nights tackling problems the rest of us can barely imagine solutions to... In this regard, something that makes these individuals 'special' is good... because they are special. Second, by making select individuals 'special' in an attempt to provide incentive, you may do just the opposite... You may alienate individuals by making them feel like they're not a member of the 'chosen few'. I can see both sides of this argument... Which is why I think the best action would be to simply make FreeBSD shirts as available as possible, rather than risking the alienation specialized products could lead to. I wouldn't feel alienated... I'd very gladly pitch in money for shirts, hats, jkh-signature-edition love ewes *wink*, etc... but some people may... *shrug* Later, --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 20: 8: 3 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id F3558151C6; Tue, 3 Aug 1999 20:07:58 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id NAA02945; Wed, 4 Aug 1999 13:06:56 +1000 Date: Wed, 4 Aug 1999 13:06:56 +1000 From: Bruce Evans Message-Id: <199908040306.NAA02945@godzilla.zeta.org.au> To: archie@whistle.com Subject: Re: Panic plus advice needed Cc: bde@FreeBSD.ORG, current@FreeBSD.ORG, dwmalone@maths.tcd.ie, grog@lemis.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> > One reason adding -g doesn't work at times is if the kernel is >> > recompiled by a person with a different length username. vers.c >> > is produced with a string which is a different length which screws >> > up the offsets. >> > >> > Maybe newvers.sh should pad usernames to the legal max? Maybe we should >> > warn people to touch vers.c after editing the Makefile? >> >> That would be really helpful to us actually and I imagine lots of people. >> In fact, you don't need to pad the username, just add the right number of >> zeroes to the end of the string, eg. > >Any objections to the patch below? Yes. It bloats the kernel and only fixed one cause of the problem. >And a related question: why not define ostype[], et.al. as "const" ? It would cause a cast-qual warning when SYSCTL_STRING() casts away the "const". Casting away the "const" is OK for the CTLFLG_RD case but not for the CTLFLAG_RW case. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 20:49:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (Postfix) with ESMTP id 0751C14D52 for ; Tue, 3 Aug 1999 20:49:18 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id for ; Tue, 3 Aug 1999 23:48:14 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Tue, 3 Aug 1999 20:48:12 -0700 (PDT) Received: from localhost.pfcs.com [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Tue, 3 Aug 1999 23:48:11 -0400 (EDT) To: current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... In-Reply-To: "Chad R. Larson"'s (chad@DCFinc.com) message dated Tue, 03 Aug 1999 19:14:22. <199908040214.TAA17617@freeway.dcfinc.com> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (20 Minutes to Nikko) (i386-unknown-freebsd2.2.8) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Tue, 03 Aug 1999 23:48:11 -0400 Message-ID: <16277.933738491@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To avoid the crosspost police, I've removed -stable from the thread. Speaking of incentives, prizes, etc. you might want to read the book: "Punished by Rewards" by Alfie Kohn. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 21:32:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id CBB9714FC7 for ; Tue, 3 Aug 1999 21:32:41 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id VAA96411; Tue, 3 Aug 1999 21:32:07 -0700 (PDT) From: Archie Cobbs Message-Id: <199908040432.VAA96411@bubba.whistle.com> Subject: Re: Panic plus advice needed In-Reply-To: <199908040306.NAA02945@godzilla.zeta.org.au> from Bruce Evans at "Aug 4, 1999 01:06:56 pm" To: bde@zeta.org.au (Bruce Evans) Date: Tue, 3 Aug 1999 21:32:07 -0700 (PDT) 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 Bruce Evans writes: > >Any objections to the patch below? > > Yes. It bloats the kernel and only fixed one cause of the problem. What are the others..? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Aug 3 22:25:23 1999 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 5D10A15300 for ; Tue, 3 Aug 1999 22:25:06 -0700 (PDT) (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 XAA93374; Tue, 3 Aug 1999 23:24:46 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA00996; Tue, 3 Aug 1999 23:24:42 -0600 (MDT) Message-Id: <199908040524.XAA00996@harmony.village.org> To: "Valentin S. Chopov" Subject: Re: problem with last src/sys/pccard changes Cc: current@FreeBSD.ORG In-reply-to: Your message of "Tue, 03 Aug 1999 06:36:57 PDT." <19990803133657.24827.rocketmail@web109.yahoomail.com> References: <19990803133657.24827.rocketmail@web109.yahoomail.com> Date: Tue, 03 Aug 1999 23:24:42 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990803133657.24827.rocketmail@web109.yahoomail.com> "Valentin S. Chopov" writes: : : After cvsup of src/sys/pccard and src/usr.sbin/pccard : from Aug 1, PCMCIA net card is not working. Te message : from pccardd is : : : Aug 3 02:28:42 valsho pccardd[256]: driver allocation : failed for IC-CARD(IC-CARD): Inappropriate ioctl for : device : : Also new pccardd is working with old kernel code... : So, may be te problem is in src/sys/pccard. Read UPDATING. You must recompile pccardd for the new kernel. The ioctl changed to pass the length of the io port range into the kernel rather than just the bottom end of the range. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 2:38:56 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 5282614D74 for ; Wed, 4 Aug 1999 02:38:52 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA13368; Wed, 4 Aug 1999 19:36:59 +1000 Date: Wed, 4 Aug 1999 19:36:59 +1000 From: Bruce Evans Message-Id: <199908040936.TAA13368@godzilla.zeta.org.au> To: archie@whistle.com, bde@zeta.org.au Subject: Re: Panic plus advice needed Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >Any objections to the patch below? >> >> Yes. It bloats the kernel and only fixed one cause of the problem. > >What are the others..? The only one I can find now is naming the debugging kernel with a name of different length. This causes different string lengths in config.c and vers.c. I once thought I saw a problem related to linker sets, but I was probably mistaken. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 4:42: 4 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp05.primenet.com (smtp05.primenet.com [206.165.6.135]) by hub.freebsd.org (Postfix) with ESMTP id CF31714D21; Wed, 4 Aug 1999 04:42:01 -0700 (PDT) (envelope-from kbock@pop.primenet.com) Received: (from daemon@localhost) by smtp05.primenet.com (8.9.1/8.9.1) id EAA23892; Wed, 4 Aug 1999 04:41:51 -0700 Received: from ip-17-060.prc.primenet.com(207.218.17.60), claiming to be "kevin" via SMTP by smtp05.primenet.com, id smtpdJ2kAUa; Wed Aug 4 04:41:43 1999 Message-Id: <3.0.6.32.19990804044121.007c0e80@pop.primenet.com> X-Sender: kbock@pop.primenet.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Wed, 04 Aug 1999 04:41:21 -0700 To: freebsd-hardware@freebsd.org From: Kevin Subject: Tekram DC-390U2W support (80Mb/sec operation) Cc: 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 Hey all, I purchased a Tekram DC-390U2W scsi controller to use with a FreeBSD server of mine. It uses the NCR 53c141 (and 53c895?) chipset(s). I see that ncr.c supports the NCR 53c8xx family of chipsets.. which the controller is seen as having a 53c895, which only supports 40Mb/sec operation(?) {NCR_895_ID, 0x00, "ncr 53c895 fast40 wide scsi", 7, 31, 7, FE_WIDE|FE_ULTRA2|FE_QUAD|FE_CACHE_SET|FE_DFS|FE_LDSTR|FE_PFEN|FE_RAM} I am assuming that it only supports 40Mb/sec operation.. could someone prove me wrong? I just want to get 80Mb/sec operation (would I need to have support for the 53c141 driver? are there any out there, is it in the works?). Tekram has FreeBSD drivers on their site but they say it is supported in 3.0, I can't find anything newer. They are working on a new one.. They already have support for the DC-390U2W on various Linux's of course :( Could anyone *please* enlighten me? I would be grateful. Please reply to my email address, as I am not subsribed to these lists. Thanks a lot, Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 5:48:38 1999 Delivered-To: freebsd-current@freebsd.org Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (Postfix) with ESMTP id 1F0C61537E for ; Wed, 4 Aug 1999 05:48:36 -0700 (PDT) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.3/8.9.1) with SMTP id IAA12766 for ; Wed, 4 Aug 1999 08:48:24 -0400 (EDT) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA29347; Wed, 4 Aug 1999 08:47:54 -0400 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id IAA72224 for freebsd-current@freebsd.org; Wed, 4 Aug 1999 08:47:54 -0400 (EDT) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199908041247.IAA72224@bb01f39.unx.sas.com> Subject: 'make release' doc problem (lynx) To: freebsd-current@freebsd.org Date: Wed, 4 Aug 1999 08:47:54 -0400 (EDT) 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 Hi, I've noticed the following the last few days... Not a big problem, but it eventually needs some attention... Thanks, John rm -f /usr/local/share/lynx_help/help_files.sed Updating /usr/local/etc/lynx.cfg /bin/sh -c 'if test -f /usr/local/etc/lynx.cfg ; then mv /usr/local/etc/lynx.cfg /usr/local/etc/lynx.tmp ; else cp ./lynx.cfg /usr/local/etc/lynx.tmp ; fi' Updating /usr/local/etc/lynx.cfg to point to installed help-files sed -e '/^HELPFILE:http/s@^@#@' -e '/^#HELPFILE:file/s@#@@' -e '/^HELPFILE:file/s@/PATH_TO/lynx_help@/usr/local/share/lynx_help@' -e '/^[A-Z_]*:/s@/PATH_TO/lynx_doc@/usr/local/share/lynx_doc@' -e '/^HELPFILE:file/s@$@@' -e '/^HELPFILE:file/s@$@@' /usr/local/etc/lynx.tmp >/usr/local/etc/lynx.cfg chmod 644 /usr/local/etc/lynx.cfg rm -f /usr/local/etc/lynx.tmp /bin/sh -c 'for name in COPYING COPYHEADER; do cd /usr/local/share/lynx_doc && cp $name /usr/local/share/lynx_help/; done' cp: COPYING: No such file or directory cp: COPYHEADER: No such file or directory *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 7:55:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by hub.freebsd.org (Postfix) with ESMTP id E0B1B15153 for ; Wed, 4 Aug 1999 07:55:03 -0700 (PDT) (envelope-from jhay@zibbi.mikom.csir.co.za) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.9.3/8.9.3) id QAA91735; Wed, 4 Aug 1999 16:53:53 +0200 (SAT) (envelope-from jhay) From: John Hay Message-Id: <199908041453.QAA91735@zibbi.mikom.csir.co.za> Subject: Re: 'make release' doc problem (lynx) In-Reply-To: <199908041247.IAA72224@bb01f39.unx.sas.com> from "John W. DeBoskey" at "Aug 4, 1999 08:47:54 am" To: jwd@unx.sas.com (John W. DeBoskey) Date: Wed, 4 Aug 1999 16:53:53 +0200 (SAT) Cc: freebsd-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 Yip, it has been breaking "make release" here the past few nights. John -- John Hay -- John.Hay@mikom.csir.co.za > Hi, > > I've noticed the following the last few days... Not a big problem, but > it eventually needs some attention... > > Thanks, > John > > rm -f /usr/local/share/lynx_help/help_files.sed > Updating /usr/local/etc/lynx.cfg > /bin/sh -c 'if test -f /usr/local/etc/lynx.cfg ; then mv /usr/local/etc/lynx.cfg /usr/local/etc/lynx.tmp ; else cp ./lynx.cfg /usr/local/etc/lynx.tmp ; fi' > Updating /usr/local/etc/lynx.cfg to point to installed help-files > sed -e '/^HELPFILE:http/s@^@#@' -e '/^#HELPFILE:file/s@#@@' -e '/^HELPFILE:file/s@/PATH_TO/lynx_help@/usr/local/share/lynx_help@' -e '/^[A-Z_]*:/s@/PATH_TO/lynx_doc@/usr/local/share/lynx_doc@' -e '/^HELPFILE:file/s@$@@' -e '/^HELPFILE:file/s@$@@' /usr/local/etc/lynx.tmp >/usr/local/etc/lynx.cfg > chmod 644 /usr/local/etc/lynx.cfg > rm -f /usr/local/etc/lynx.tmp > /bin/sh -c 'for name in COPYING COPYHEADER; do cd /usr/local/share/lynx_doc && cp $name /usr/local/share/lynx_help/; done' > cp: COPYING: No such file or directory > cp: COPYHEADER: No such file or directory > *** Error code 1 > > Stop. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 9:12:59 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 16845150DD for ; Wed, 4 Aug 1999 09:12:57 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id JAA98396; Wed, 4 Aug 1999 09:12:43 -0700 (PDT) From: Archie Cobbs Message-Id: <199908041612.JAA98396@bubba.whistle.com> Subject: Re: Panic plus advice needed In-Reply-To: <199908040936.TAA13368@godzilla.zeta.org.au> from Bruce Evans at "Aug 4, 1999 07:36:59 pm" To: bde@zeta.org.au (Bruce Evans) Date: Wed, 4 Aug 1999 09:12:43 -0700 (PDT) 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 Bruce Evans writes: > >> >Any objections to the patch below? > >> > >> Yes. It bloats the kernel and only fixed one cause of the problem. > > > >What are the others..? > > The only one I can find now is naming the debugging kernel with a name > of different length. This causes different string lengths in config.c > and vers.c. I once thought I saw a problem related to linker sets, but > I was probably mistaken. So... IMHO, if we can fix this as well, it would be worth it for all the people who get core dumps but didn't build debug kernels. Do you disagree? -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 12: 0: 6 1999 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 3CE6C15405; Wed, 4 Aug 1999 11:59:46 -0700 (PDT) (envelope-from nik@nothing-going-on.demon.co.uk) Received: from kilt.nothing-going-on.org (kilt.nothing-going-on.org [192.168.1.18]) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) with ESMTP id TAA66852; Wed, 4 Aug 1999 19:50:28 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Received: (from nik@localhost) by kilt.nothing-going-on.org (8.9.3/8.9.3) id QAA15669; Wed, 4 Aug 1999 16:39:23 +0100 (BST) (envelope-from nik@catkin.nothing-going-on.org) Date: Wed, 4 Aug 1999 16:39:23 +0100 From: Nik Clayton To: Poul-Henning Kamp Cc: Nik Clayton , stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Sitting inside, looking out... Message-ID: <19990804163923.A13708@kilt.nothing-going-on.org> Reply-To: chat@freebsd.org References: <19990803164207.A46171@kilt.nothing-going-on.org> <30735.933704575@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <30735.933704575@critter.freebsd.dk>; from Poul-Henning Kamp on Tue, Aug 03, 1999 at 08:22:55PM +0200 Organization: FreeBSD Project Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [Reply-to set to -chat] On Tue, Aug 03, 1999 at 08:22:55PM +0200, Poul-Henning Kamp wrote: > In message <19990803164207.A46171@kilt.nothing-going-on.org>, Nik Clayton writes: > >Just for completeness; > > Yeah, sorry for leaving you gang out , but I didn't want to make > it too long, the important thing was to get the three main kinds > down, doc committers are pretty much the same story as the other > two "limited scope" types. Oh, absolutely. But you have to understand that the -doc committers are a rough crowd, and if I don't speak up for them every so they often they start saying rude things about my parentage. What's worse is the translation teams -- they say rude things about my parentage and I can't even understand what they're saying. . . [ Hmm, there's a thought -- could someone who speaks Japanese, Spanish, or one of the other languages we've got translated please check out the different translations of the FAQ, and make sure it doesn't just consist of "Nik's mother wears army boots" repeated again and again. Thanks ] > >At least, that's my take on it. > > > >> NOTE: If somebody can find a sponsor for it, I would really > >> like to offer an "official FreeBSD Committer sweat-shirt" > >> to each and every single committer. Luxury cars, free > >> vacations and suitcases filled with cash would also do. > > > >How about the FreeBSD Project coming up with the > >artwork, and then 'licensing' it to each user group? > > For it to have significance for the committers, it should be done in > such a manner that only the committers get their hands on them. As Matt points out, this has room to backfire. You can see the commit log now; Modified files: CVSROOT avail Log: John Smith is no longer a committer. He's promised to burn his t-shirt in private, and never mention this again. Given that (by and large) the committers are just a subset of a much larger developer base, and that we have developers who, for their own reasons, have declined to become committers, something that's limited to committers is probably not so great. But for patches that closed PRs, absolutely. We could maybe have a generic design that's registered as a copyright (or a trademark, or whatever) with the project, and the project can license this design out to user groups, or individuals, as necessary, and for a small fee. So, if the UK user group wanted to put out 'official UK FreeBSD user group' t-shirts then they can do so, for (say $20 licensing for the design, and $1 per t-shirt). And to pick another example at random, Matt could have a "FreeBSD VM God" t-shirt (and richly deserved it is too). But why stop at t-shirts? FreeBSD boxer shorts? Bra and panties? Anoraks? OK, maybe not the last one. N -- [intentional self-reference] can be easily accommodated using a blessed, non-self-referential dummy head-node whose own object destructor severs the links. -- Tom Christiansen in <375143b5@cs.colorado.edu> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 14:14: 0 1999 Delivered-To: freebsd-current@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id C824414D7D for ; Wed, 4 Aug 1999 14:13:55 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40327>; Thu, 5 Aug 1999 06:54:09 +1000 Date: Thu, 5 Aug 1999 07:13:32 +1000 From: Peter Jeremy Subject: Re: Panic plus advice needed In-reply-to: <199908040936.TAA13368@godzilla.zeta.org.au> To: archie@whistle.com, bde@zeta.org.au Cc: current@FreeBSD.ORG Message-Id: <99Aug5.065409est.40327@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans wrote: >>> >Any objections to the patch below? >>> >>> Yes. It bloats the kernel and only fixed one cause of the problem. >> >>What are the others..? > >The only one I can find now is naming the debugging kernel with a name >of different length. Also, if your kernel was previously version 9 (or 99 or 999 or ...), the incremented version number will increase the length of the version string in vers.c. Someone with some free time on their hands might like to check thru the egcs code to see if enabling debug can affect the code generation. A quick check suggests that the relevant globals are write_symbols, use_gnu_debug_info_extensions and debug_info_level. Generating SDB debugging information (for COFF) definitely can change code alignment, but working out if generating DBX debugging information has any effect on the generated code would take more time than I can justify right now. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 16:43:41 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id D46DE1516E for ; Wed, 4 Aug 1999 16:43:39 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id QAA23501; Wed, 4 Aug 1999 16:42:50 -0700 (PDT) From: Archie Cobbs Message-Id: <199908042342.QAA23501@bubba.whistle.com> Subject: Re: Panic plus advice needed In-Reply-To: <99Aug5.065409est.40327@border.alcanet.com.au> from Peter Jeremy at "Aug 5, 1999 07:13:32 am" To: jeremyp@gsmx07.alcatel.com.au (Peter Jeremy) Date: Wed, 4 Aug 1999 16:42:50 -0700 (PDT) Cc: bde@zeta.org.au, 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 Peter Jeremy writes: > >>> Yes. It bloats the kernel and only fixed one cause of the problem. > >> > >>What are the others..? > > > >The only one I can find now is naming the debugging kernel with a name > >of different length. > > Also, if your kernel was previously version 9 (or 99 or 999 or ...), > the incremented version number will increase the length of the version > string in vers.c. That's the same thing as we're already talking about (see patch). -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 17:41:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 9E3F315451 for ; Wed, 4 Aug 1999 17:41:40 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA08955; Thu, 5 Aug 1999 10:11:03 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA71379; Thu, 5 Aug 1999 10:10:49 +0930 (CST) Date: Thu, 5 Aug 1999 10:10:49 +0930 From: Greg Lehey To: Archie Cobbs Cc: Bruce Evans , current@FreeBSD.ORG Subject: Re: Panic plus advice needed Message-ID: <19990805101049.W62948@freebie.lemis.com> References: <199908040936.TAA13368@godzilla.zeta.org.au> <199908041612.JAA98396@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199908041612.JAA98396@bubba.whistle.com>; from Archie Cobbs on Wed, Aug 04, 1999 at 09:12:43AM -0700 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 Wednesday, 4 August 1999 at 9:12:43 -0700, Archie Cobbs wrote: > Bruce Evans writes: >>>>> Any objections to the patch below? >>>> >>>> Yes. It bloats the kernel and only fixed one cause of the problem. >>> >>> What are the others..? >> >> The only one I can find now is naming the debugging kernel with a name >> of different length. This causes different string lengths in config.c >> and vers.c. I once thought I saw a problem related to linker sets, but >> I was probably mistaken. > > So... IMHO, if we can fix this as well, it would be worth it for all > the people who get core dumps but didn't build debug kernels. > Do you disagree? I disagree that this should even be necessary. This kind of detail was exactly the reason why I put the short-lived default debug kernel into config. There aren't too many systems any more that don't have an additional 30 MB for the time it takes to build the kernel, and it solves a whole lot of potential problems. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 19:58:26 1999 Delivered-To: freebsd-current@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 3B05614D40 for ; Wed, 4 Aug 1999 19:58:25 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.2/8.9.2) id TAA24382; Wed, 4 Aug 1999 19:57:30 -0700 (PDT) From: Archie Cobbs Message-Id: <199908050257.TAA24382@bubba.whistle.com> Subject: Re: Panic plus advice needed In-Reply-To: <19990805101049.W62948@freebie.lemis.com> from Greg Lehey at "Aug 5, 1999 10:10:49 am" To: grog@lemis.com (Greg Lehey) Date: Wed, 4 Aug 1999 19:57:30 -0700 (PDT) Cc: archie@whistle.com (Archie Cobbs), bde@zeta.org.au (Bruce Evans), 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 Greg Lehey writes: > >> The only one I can find now is naming the debugging kernel with a name > >> of different length. This causes different string lengths in config.c > >> and vers.c. I once thought I saw a problem related to linker sets, but > >> I was probably mistaken. > > > > So... IMHO, if we can fix this as well, it would be worth it for all > > the people who get core dumps but didn't build debug kernels. > > Do you disagree? > > I disagree that this should even be necessary. This kind of detail > was exactly the reason why I put the short-lived default debug kernel > into config. There aren't too many systems any more that don't have > an additional 30 MB for the time it takes to build the kernel, and it > solves a whole lot of potential problems. Sounds OK to me. Was this kernel.debug thing merged into -stable? If not it might be a good thing to do. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 20:57:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id 450FB15241 for ; Wed, 4 Aug 1999 20:57:19 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id LAA27918; Thu, 5 Aug 1999 11:55:38 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id LAA01307; Thu, 5 Aug 1999 11:56:58 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id LAA20002; Thu, 5 Aug 1999 11:57:00 +0800 Message-Id: <199908050357.LAA20002@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@freebsd.org Cc: dillon@apollo.backplane.com Subject: Interesting NFS hangs under current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 05 Aug 1999 11:56:59 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On my home network, I make world on one machine and install it (from an NFS mounted directory) on another. Some time ago (I've griped about this before - the problem's been around for a while) it started to occasionally hang just after or during installing libc.so.3. It will then hang solidly - no response to keyboard, net or whatever, but it does allow me to break into the debugger and take a dump. Below is the stack trace (hurrah for debugging kernels!). I will not that after rebooting fscking the disks, usr/lib/libc.so.3 is often a multiple of 64k in size. If I don't boot single user and copy an old libc over the top of the partially written one, subsequent boots will of course have programs crapping out all over the place. (kgdb) # gdb -k /sys/compile/bleep/kernel.debug /var/crash/vmcore.2 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 3063808 initial pcb at 277c20 panicstr: from debugger panic messages: --- panic: from debugger syncing disks... 254 254 251 244 231 207 178 123 107 53 4 2 2 2 2 2 2 2 2 2 done dumping to dev (116,1), offset 483456 dump 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 boot (howto=256) at ../../kern/kern_shutdown.c:291 291 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:291 #1 0xc0145519 in panic (fmt=0xc0234e14 "from debugger") at ../../kern/kern_shutdown.c:505 #2 0xc012cbc9 in db_panic (addr=-1071579017, have_addr=0, count=-1, modif=0xc5f45afc "") at ../../ddb/db_command.c:434 #3 0xc012cb69 in db_command (last_cmdp=0xc025b370, cmd_table=0xc025b1d0, aux_cmd_tablep=0xc0274cc4) at ../../ddb/db_command.c:334 #4 0xc012cc2e in db_command_loop () at ../../ddb/db_command.c:456 #5 0xc012ecb3 in db_trap (type=3, code=0) at ../../ddb/db_trap.c:71 #6 0xc020fe34 in kdb_trap (type=3, code=0, regs=0xc5f45bf0) at ../../i386/i386/db_interface.c:157 #7 0xc021c3ec in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 2, tf_esi = -1071082528, tf_ebp = -973841352, tf_isp = -973841380, tf_ebx = 134, tf_edx = -1071320177, tf_ecx = 1920, tf_eax = 38, tf_trapno = 3, tf_err = 0, tf_eip = -1071579017, tf_cs = 8, tf_eflags = 582, tf_esp = -1071320193, tf_ss = -1071333302}) at ../../i386/i386/trap.c:534 #8 0xc0210077 in Debugger (msg=0xc024c04a "manual escape to debugger") at machine/cpufunc.h:64 #9 0xc020cb76 in scgetc (sc=0xc0273520, flags=2) at ../../dev/syscons/syscons.c:3813 #10 0xc02087dd in sckbdevent (thiskbd=0xc0287c00, event=0, arg=0xc0273520) at ../../dev/syscons/syscons.c:688 ---Type to continue, or q to quit--- #11 0xc0201e13 in atkbd_intr (kbd=0xc0287c00, arg=0x0) at ../../dev/kbd/atkbd.c:535 #12 0xc0229f7f in atkbd_isa_intr (arg=0xc05ab3f0) at ../../isa/atkbd_isa.c:125 #13 0xc01f1d88 in vm_page_lookup (object=0xc5f6fbb8, pindex=62247042) at ../../vm/vm_page.c:526 #14 0xc0219ac4 in pmap_object_init_pt (pmap=0xc5e4cf24, addr=672055296, object=0xc5f6fbb8, pindex=110, size=16384, limit=16) at ../../i386/i386/pmap.c:2434 #15 0xc01ec220 in vm_map_insert (map=0xc5e4cec0, object=0xc5f6fbb8, offset=450560, start=672055296, end=672071680, prot=7 '\a', max=7 '\a', cow=18) at ../../vm/vm_map.c:550 #16 0xc01ec3a3 in vm_map_find (map=0xc5e4cec0, object=0xc5f6fbb8, offset=450560, addr=0xc5f45ed4, length=16384, find_space=0, prot=7 '\a', max=7 '\a', cow=18) at ../../vm/vm_map.c:654 #17 0xc01efc49 in vm_mmap (map=0xc5e4cec0, addr=0xc5f45ed4, size=16384, prot=7 '\a', maxprot=7 '\a', flags=18, handle=0xc5f5da80, foff=450560) at ../../vm/vm_mmap.c:1058 #18 0xc01ef2d6 in mmap (p=0xc5e49020, uap=0xc5f45f80) at ../../vm/vm_mmap.c:330 #19 0xc021cc2a in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = 0, tf_esi = 450560, tf_ebp = -1077949324, tf_isp = -973840428, tf_ebx = 671456744, tf_edx = 6, tf_ecx = 450560, tf_eax = 198, tf_trapno = 0, tf_err = 2, tf_eip = 671436440, tf_cs = 31, tf_eflags = 518, tf_esp = -1077949380, tf_ss = 47}) ---Type to continue, or q to quit--- at ../../i386/i386/trap.c:1056 #20 0xc0210726 in Xint0x80_syscall () #21 0x2804dfb1 in ?? () #22 0x2804cfa6 in ?? () #23 0x2804ce76 in ?? () #24 0x2804c291 in ?? () (kgdb) -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 21:43:56 1999 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 4057615451 for ; Wed, 4 Aug 1999 21:43:53 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-3-57.ucdavis.edu [169.237.17.57]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id VAA00554; Wed, 4 Aug 1999 21:43:26 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id VAA87393; Wed, 4 Aug 1999 21:43:23 -0700 (PDT) (envelope-from obrien) Date: Wed, 4 Aug 1999 21:43:21 -0700 From: "David O'Brien" To: Archie Cobbs Cc: current@FreeBSD.ORG Subject: Re: Panic plus advice needed Message-ID: <19990804214321.A87373@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19990805101049.W62948@freebie.lemis.com> <199908050257.TAA24382@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199908050257.TAA24382@bubba.whistle.com>; from Archie Cobbs on Wed, Aug 04, 1999 at 07:57:30PM -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 > > I disagree that this should even be necessary. This kind of detail > > was exactly the reason why I put the short-lived default debug kernel > > into config. There aren't too many systems any more that don't have > > an additional 30 MB for the time it takes to build the kernel, and it > > solves a whole lot of potential problems. > > Sounds OK to me. Was this kernel.debug thing merged into -stable? Nope. I've requested grog to MFC, another person requesting couldn't hurt. :-) -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 23:11:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id 1963614DF8 for ; Wed, 4 Aug 1999 23:11:15 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA33711; Wed, 4 Aug 1999 23:10:49 -0700 (PDT) (envelope-from dillon) Date: Wed, 4 Aug 1999 23:10:49 -0700 (PDT) From: Matthew Dillon Message-Id: <199908050610.XAA33711@apollo.backplane.com> To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@freebsd.org Subject: Re: Interesting NFS hangs under current References: <199908050357.LAA20002@ariadne.tensor.pgs.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Could you print out *p and *uap in frame 18? frame 18 print *p print *uap Also, do: ps -axl -N /sys/compile/bleep/kernel.debug -M /var/crash/vmcore.2 This is very odd. There is no way it should be looping in supervisor mode in that call chain. -Matt Matthew Dillon :On my home network, I make world on one machine and install it (from an NFS :mounted directory) on another. Some time ago (I've griped about this before - :the problem's been around for a while) it started to occasionally hang just :after or during installing libc.so.3. It will then hang solidly - no response :to keyboard, net or whatever, but it does allow me to break into the debugger :and take a dump. Below is the stack trace (hurrah for debugging kernels!). I :will not that after rebooting fscking the disks, usr/lib/libc.so.3 is often a :multiple of 64k in size. If I don't boot single user and copy an old libc over :the top of the partially written one, subsequent boots will of course have :programs crapping out all over the place. : :(kgdb) # gdb -k /sys/compile/bleep/kernel.debug /var/crash/vmcore.2 :... : at ../../dev/syscons/syscons.c:688 :---Type to continue, or q to quit--- :#11 0xc0201e13 in atkbd_intr (kbd=0xc0287c00, arg=0x0) : at ../../dev/kbd/atkbd.c:535 :#12 0xc0229f7f in atkbd_isa_intr (arg=0xc05ab3f0) at ../../isa/atkbd_isa.c:125 :#13 0xc01f1d88 in vm_page_lookup (object=0xc5f6fbb8, pindex=62247042) : at ../../vm/vm_page.c:526 :#14 0xc0219ac4 in pmap_object_init_pt (pmap=0xc5e4cf24, addr=672055296, : object=0xc5f6fbb8, pindex=110, size=16384, limit=16) : at ../../i386/i386/pmap.c:2434 :#15 0xc01ec220 in vm_map_insert (map=0xc5e4cec0, object=0xc5f6fbb8, : offset=450560, start=672055296, end=672071680, prot=7 '\a', max=7 '\a', : cow=18) at ../../vm/vm_map.c:550 :#16 0xc01ec3a3 in vm_map_find (map=0xc5e4cec0, object=0xc5f6fbb8, : offset=450560, addr=0xc5f45ed4, length=16384, find_space=0, prot=7 '\a', : max=7 '\a', cow=18) at ../../vm/vm_map.c:654 :#17 0xc01efc49 in vm_mmap (map=0xc5e4cec0, addr=0xc5f45ed4, size=16384, : prot=7 '\a', maxprot=7 '\a', flags=18, handle=0xc5f5da80, foff=450560) : at ../../vm/vm_mmap.c:1058 :#18 0xc01ef2d6 in mmap (p=0xc5e49020, uap=0xc5f45f80) at ../../vm/vm_mmap.c:330 : :... : (Stephen Hocking-Senior Programmer PGS Tensor Perth ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 23:24:32 1999 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 D08E714D69 for ; Wed, 4 Aug 1999 23:24:29 -0700 (PDT) (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 AAA97118; Thu, 5 Aug 1999 00:22:46 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA09178; Thu, 5 Aug 1999 00:22:54 -0600 (MDT) Message-Id: <199908050622.AAA09178@harmony.village.org> To: Peter Jeremy Subject: Re: Panic plus advice needed Cc: archie@whistle.com, bde@zeta.org.au, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 05 Aug 1999 07:13:32 +1000." <99Aug5.065409est.40327@border.alcanet.com.au> References: <99Aug5.065409est.40327@border.alcanet.com.au> Date: Thu, 05 Aug 1999 00:22:53 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <99Aug5.065409est.40327@border.alcanet.com.au> Peter Jeremy writes: : Someone with some free time on their hands might like to check thru : the egcs code to see if enabling debug can affect the code generation. : A quick check suggests that the relevant globals are write_symbols, : use_gnu_debug_info_extensions and debug_info_level. Generating SDB : debugging information (for COFF) definitely can change code alignment, : but working out if generating DBX debugging information has any effect : on the generated code would take more time than I can justify right : now. It is my belief that gcc 2.7.3.2 generates different code when -g is on the command line.... At least that's what I've seen from time to time with kernels. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 23:26:12 1999 Delivered-To: freebsd-current@freebsd.org Received: from bilby.prth.tensor.pgs.com (bilby.prth.tensor.pgs.com [157.147.232.237]) by hub.freebsd.org (Postfix) with ESMTP id E490414E0A for ; Wed, 4 Aug 1999 23:26:01 -0700 (PDT) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by bilby.prth.tensor.pgs.com (8.9.3/8.8.8) with ESMTP id OAA28385; Thu, 5 Aug 1999 14:24:03 +0800 (WST) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.9.3/8.8.8) with SMTP id OAA08100; Thu, 5 Aug 1999 14:25:26 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id OAA20277; Thu, 5 Aug 1999 14:25:27 +0800 Message-Id: <199908050625.OAA20277@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matthew Dillon Cc: shocking@bandicoot.prth.tensor.pgs.com, current@freebsd.org Subject: Re: Interesting NFS hangs under current In-reply-to: Your message of "Wed, 04 Aug 1999 23:10:49 MST." <199908050610.XAA33711@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Thu, 05 Aug 1999 14:25:26 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Could you print out *p and *uap in frame 18? > = > frame 18 > print *p > print *uap > = > Also, do: > = > ps -axl -N /sys/compile/bleep/kernel.debug -M /var/crash/vmcore.2 > = > This is very odd. There is no way it should be looping in superviso= r > mode in that call chain. > = No sooner received than done.... (kgdb) frame 18 #18 0xc01ef2d6 in mmap (p=3D0xc5e49020, uap=3D0xc5f45f80) at ../../vm/vm_= mmap.c:330 330 error =3D vm_mmap(&p->p_vmspace->vm_map, &addr, size, pro= t, maxprot, (kgdb) print *p $2 =3D {p_procq =3D {tqe_next =3D 0xc0290ed0, tqe_prev =3D 0x0}, p_list =3D= { le_next =3D 0xc5e492e0, le_prev =3D 0xc0290f60}, p_cred =3D 0xc0a42b2= 0, = p_fd =3D 0xc0a23c80, p_stats =3D 0xc5f44230, p_limit =3D 0xc099a600, = p_upages_obj =3D 0xc5ea59c4, p_procsig =3D 0xc0a3eaa0, p_flag =3D 16388= , = p_stat =3D 2 '\002', p_pad1 =3D "\000\000", p_pid =3D 4672, p_hash =3D = { le_next =3D 0xc5e4a8e0, le_prev =3D 0xc05ad780}, p_pglist =3D {le_nex= t =3D 0x0, = le_prev =3D 0xc0a42ae8}, p_pptr =3D 0xc58c6ec0, p_sibling =3D {le_nex= t =3D 0x0, = le_prev =3D 0xc58c6f10}, p_children =3D {lh_first =3D 0x0}, p_ithandl= e =3D { callout =3D 0xc1b86108}, p_oppid =3D 0, p_dupfd =3D 0, p_vmspace =3D = 0xc5e4cec0, = p_estcpu =3D 1502, p_cpticks =3D 1247, p_pctcpu =3D 1791, p_wchan =3D 0= x0, = p_wmesg =3D 0x0, p_swtime =3D 20, p_slptime =3D 0, p_realtimer =3D {it_= interval =3D { tv_sec =3D 0, tv_usec =3D 0}, it_value =3D {tv_sec =3D 0, tv_usec =3D= 0}}, = p_runtime =3D 10333, p_uticks =3D 0, p_sticks =3D 2437, p_iticks =3D 19= 91, = p_traceflag =3D 0, p_tracep =3D 0x0, p_siglist =3D 0, p_textvp =3D 0xc5= dfbcc0, = p_lock =3D 0 '\000', p_oncpu =3D 0 '\000', p_lastcpu =3D 0 '\000', = p_pad2 =3D 0 '\000', p_locks =3D 0, p_simple_locks =3D 0, p_stops =3D 0= , = p_stype =3D 0, p_step =3D 0 '\000', p_pfsflags =3D 0 '\000', p_pad3 =3D= "\000", = p_retval =3D {0, 6}, p_sigiolst =3D {slh_first =3D 0x0}, p_sigparent =3D= 20, = p_oldsigmask =3D 0, p_sig =3D 0, p_code =3D 0, p_sigmask =3D 0, = p_priority =3D 127 '\177', p_usrpri =3D 127 '\177', p_nice =3D 0 '\000'= , = p_comm =3D "rpc.rstatd\000\000\000\000\000\000", p_pgrp =3D 0xc0a42ae0,= = p_sysent =3D 0xc025bbc0, p_rtprio =3D {type =3D 1, prio =3D 0}, p_priso= n =3D 0x0, = p_addr =3D 0xc5f44000, p_md =3D {md_regs =3D 0xc5f45fa8}, p_xstat =3D 0= , = ---Type to continue, or q to quit--- p_acflag =3D 2, p_ru =3D 0x0, p_nthreads =3D 0, p_aioinfo =3D 0x0, p_wa= keup =3D 0, = p_peers =3D 0x0, p_leader =3D 0xc5e49020, p_asleep =3D {as_priority =3D= 0, = as_timo =3D 0}, p_emuldata =3D 0x0} (kgdb) print *uap $3 =3D {addr =3D 0xc07a8180 "", addr_ =3D 0xc0a41744 "=C0\206z=C0\001", = len =3D 3229255360, len_ =3D 0xc0a41748 "\001", prot =3D 65537, = prot_ =3D 0xc0a4174c "\001", flags =3D 1, flags_ =3D 0xc0a41750 "\200>=A2= =C0=C4#&=C0\002", = fd =3D -1063108992, fd_ =3D 0xc0a41754 "=C4#&=C0\002", pad =3D -1071242= 300, = pad_ =3D 0xc0a41758 "\002", pos =3D 17592186044418, pos_ =3D 0xc0a41760= ""} (kgdb) = # ps -axl -N /sys/compile/bleep/kernel.debug -M /var/crash/vmcore.2 UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAN= D 0 259 1 32 10 0 508 0 wait I #C1- 0:00.00 (sh) 88 276 259 0 2 0 11132 0 - R #C1- 0:00.00 (mysq= ld) 0 282 1 32 10 0 512 0 wait I #C1- 0:00.00 (sh) 65534 289 282 0 2 0 3308 0 - R #C1- 0:00.00 (squi= d) 65534 307 289 0 -6 0 756 0 piperd I #C1- 0:00.00 (unli= nkd) 0 3428 3424 0 10 0 608 0 wait Is #C1 0:00.00 (sh) 0 3454 3428 4 10 0 928 0 wait I+ #C1 0:00.00 (make= ) 0 3457 3454 4 10 0 504 0 wait I+ #C1 0:00.00 (sh) 0 3458 3457 5 10 0 920 0 wait I+ #C1 0:00.00 (make= ) 0 3461 3458 5 10 0 504 0 wait I+ #C1 0:00.00 (sh) 0 3462 3461 5 10 0 1176 0 wait I+ #C1 0:00.00 (make= ) 0 3466 3462 5 10 0 508 0 wait I+ #C1 0:00.00 (sh) 0 3467 3466 49 10 0 628 0 wait I+ #C1 0:00.00 (make= ) 0 3534 3467 49 10 0 504 0 wait I+ #C1 0:00.00 (sh) 0 3535 3534 49 10 0 564 0 wait I+ #C1 0:00.00 (make= ) 0 3538 3535 51 10 0 508 0 wait I+ #C1 0:00.00 (sh) 0 3671 3538 54 10 0 392 0 wait I+ #C1 0:00.00 (make= ) 0 3676 3671 29 10 0 508 0 wait I+ #C1 0:00.00 (sh) 0 4659 3676 14 10 0 2712 0 wait I+ #C1 0:00.00 (make= ) 0 4667 4659 14 -2 0 340 0 getblk I+ #C1 0:00.00 (inst= all) 1000 3436 3433 6 10 0 608 0 wait Is #C1 0:00.00 (sh) 1000 3442 3436 0 3 0 1292 0 - R+ #C1 0:00.00 (syst= at) 0 3491 3486 0 3 0 608 0 ttyin Is+ #C1 0:00.00 (sh) 0 325 1 0 3 0 604 0 ttyin Is+ #C9 0:00.00 (sh) 0 327 1 0 3 0 840 0 ttyin Is+ #C2 0:00.00 (gett= y) 1000 326 1 1 10 0 604 0 wait Is #C2 0:00.00 (sh) 0 338 326 0 2 0 1576 0 select I+ #C2 0:00.00 (ssh1= ) 0 0 0 0 -18 0 0 0 - RLs ?? 0:00.00 (swap= per) 0 1 0 0 10 0 500 0 wait ILs ?? 0:00.00 (init= ) 0 2 0 0 -18 0 0 0 - RL ?? 0:00.00 (page= daemon 0 3 0 0 18 0 0 0 psleep DL ?? 0:00.00 (vmda= emon) 0 4 0 0 -18 0 0 0 - RL ?? 0:00.00 (bufd= aemon) 0 5 0 0 18 0 0 0 - RL ?? 0:00.00 (sync= er) 0 32 1 0 18 0 204 0 pause Is ?? 0:00.00 (adjk= erntz) 0 127 1 0 2 0 828 0 - Rs ?? 0:00.00 (sysl= ogd) 0 135 1 0 2 0 1528 0 select Is ?? 0:00.00 (name= d) 1 141 1 0 2 0 836 0 select Is ?? 0:00.00 (port= map) 0 144 1 0 2 0 1512 0 - Rs ?? 0:00.00 (ypse= rv) 0 147 1 0 2 0 832 0 select I ?? 0:00.00 (rpc.= ypxfrd 0 150 1 0 2 0 960 0 select Is ?? 0:00.00 (rpc.= yppass 0 153 1 0 2 0 812 0 select Is ?? 0:00.00 (ypbi= nd) 0 160 1 0 2 0 836 0 select Is ?? 0:00.00 (rpc.= ypupda 0 166 1 0 2 0 516 0 select Is ?? 0:00.00 (moun= td) 0 169 1 0 2 0 316 0 accept Is ?? 0:00.00 (nfsd= ) 0 171 169 0 2 0 296 0 - R ?? 0:00.00 (nfsd= ) 0 172 169 0 2 0 296 0 - R ?? 0:00.00 (nfsd= ) 0 173 169 0 2 0 296 0 - R ?? 0:00.00 (nfsd= ) 0 174 169 0 2 0 296 0 - R ?? 0:00.00 (nfsd= ) 0 177 1 0 2 0 262976 0 select Is ?? 0:00.00 (rpc= =2Estatd) 0 182 1 0 -1 0 208 0 nfsrcv I ?? 0:00.00 (nfsi= od) 0 183 1 0 2 0 208 0 - R ?? 0:00.00 (nfsi= od) 0 184 1 0 10 0 208 0 nfsidl I ?? 0:00.00 (nfsi= od) 0 185 1 0 10 0 208 0 nfsidl I ?? 0:00.00 (nfsi= od) 0 199 1 12 2 0 908 0 select Is ?? 0:00.00 (inet= d) 0 202 1 0 10 0 1000 0 nanslp Is ?? 0:00.00 (cron= ) 0 207 1 0 2 0 1300 0 select Is ?? 0:00.00 (send= mail) 0 242 1 0 2 0 1452 0 - Rs ?? 0:00.00 (ppp)= 8 277 1 1 2 0 17444 0 select Is ?? 0:00.00 (nntp= cached 0 292 1 0 2 0 1248 0 select Is ?? 0:00.00 (sshd= 1) 65534 319 289 5 2 0 992 0 sbwait I ?? 0:00.00 (dnss= erver) 65534 320 289 5 2 0 992 0 sbwait I ?? 0:00.00 (dnss= erver) 65534 321 289 5 2 0 992 0 sbwait I ?? 0:00.00 (dnss= erver) 65534 322 289 5 2 0 992 0 sbwait I ?? 0:00.00 (dnss= erver) 65534 323 289 5 2 0 992 0 sbwait I ?? 0:00.00 (dnss= erver) 65534 324 289 5 2 0 1016 0 select Is ?? 0:00.00 (ftpg= et) 0 351 1 1 -6 0 476 0 vinum Ds ?? 0:00.00 (vinu= m) 0 3424 292 0 2 0 1296 0 select I ?? 0:00.00 (sshd= 1) 0 3433 292 0 2 0 1300 0 select I ?? 0:00.00 (sshd= 1) 0 3486 292 0 2 0 1296 0 - R ?? 0:00.00 (sshd= 1) 0 4672 199 1502 105 0 868 0 - Rs ?? 0:00.00 (rpc= =2Erstatd # = -- = The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could prod= uce the Complete Works of Shakespeare; now, thanks to the Internet, we k= now this is not true." Robert Wilensky, University of Califor= nia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Aug 4 23:40:27 1999 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (Postfix) with ESMTP id C685514D69 for ; Wed, 4 Aug 1999 23:40:25 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA33933; Wed, 4 Aug 1999 23:40:06 -0700 (PDT) (envelope-from dillon) Date: Wed, 4 Aug 1999 23:40:06 -0700 (PDT) From: Matthew Dillon Message-Id: <199908050640.XAA33933@apollo.backplane.com> To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@freebsd.org Subject: Re: Interesting NFS hangs under current References: <199908050625.OAA20277@ariadne.tensor.pgs.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :No sooner received than done.... : :(kgdb) frame 18 :#18 0xc01ef2d6 in mmap (p=0xc5e49020, uap=0xc5f45f80) at ../../vm/vm_mmap.c:330 :330 error = vm_mmap(&p->p_vmspace->vm_map, &addr, size, prot, maxprot, :(kgdb) print *p :$2 = {p_procq = {tqe_next = 0xc0290ed0, tqe_prev = 0x0}, p_list = { :... : p_comm = "rpc.rstatd\000\000\000\000\000\000", p_pgrp = 0xc0a42ae0, :... : p_sysent = 0xc025bbc0, p_rtprio = {type = 1, prio = 0}, p_prison = 0x0, : p_addr = 0xc5f44000, p_md = {md_regs = 0xc5f45fa8}, p_xstat = 0, :---Type to continue, or q to quit--- : p_acflag = 2, p_ru = 0x0, p_nthreads = 0, p_aioinfo = 0x0, p_wakeup = 0, : p_peers = 0x0, p_leader = 0xc5e49020, p_asleep = {as_priority = 0, : as_timo = 0}, p_emuldata = 0x0} :... :(kgdb) print *uap :$3 = {addr = 0xc07a8180 "", addr_ = 0xc0a41744 "À\206zÀ\001", : len = 3229255360, len_ = 0xc0a41748 "\001", prot = 65537, : prot_ = 0xc0a4174c "\001", flags = 1, flags_ = 0xc0a41750 "\200>¢ÀÄ#&À\002", : fd = -1063108992, fd_ = 0xc0a41754 "Ä#&À\002", pad = -1071242300, : pad_ = 0xc0a41758 "\002", pos = 17592186044418, pos_ = 0xc0a41760 ""} :(kgdb) Uh oh, this is rpc.statd. I don't get it. How can rpc.statd be in an mmap() call at this point? rpc.statd should have been running long before you even started the link. Are you running rpc.statd from inetd.conf by any chance? If so, try removing it from inetd.conf and run it manually. :# ps -axl -N /sys/compile/bleep/kernel.debug -M /var/crash/vmcore.2 : UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND : 0 259 1 32 10 0 508 0 wait I #C1- 0:00.00 (sh) : 88 276 259 0 2 0 11132 0 - R #C1- 0:00.00 (mysqld) :... The large number of processes in "R"un state indicates that the machine is stuck in a supervisor loop in the mmap() code. i.e. interrupts have woken up these processes but they have been unable to actually get any cpu. Nothing else seems to be an issue. I see you are running vinum. I do not know if that is an issue. : 0 4667 4659 14 -2 0 340 0 getblk I+ #C1 0:00.00 (install) : 0 182 1 0 -1 0 208 0 nfsrcv I ?? 0:00.00 (nfsiod) : 0 183 1 0 2 0 208 0 - R ?? 0:00.00 (nfsiod) : 0 242 1 0 2 0 1452 0 - Rs ?? 0:00.00 (ppp) : 0 351 1 1 -6 0 476 0 vinum Ds ?? 0:00.00 (vinum) : 0 3486 292 0 2 0 1296 0 - R ?? 0:00.00 (sshd1) : 0 4672 199 1502 105 0 868 0 - Rs ?? 0:00.00 (rpc.rstatd :# :... -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 Aug 5 2:49:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from mbox.net96.it (mbox.net96.it [194.244.102.152]) by hub.freebsd.org (Postfix) with ESMTP id 49ACE154A3 for ; Thu, 5 Aug 1999 02:49:34 -0700 (PDT) (envelope-from ccau@itsyn.it) Received: by mbox.net96.it from localhost (router,SLMail V2.6); Thu, 05 Aug 1999 11:47:29 +0200 Received: by mbox.net96.it from 0 (151.4.19.5::mail daemon; unverified,SLMail V2.6); Thu, 05 Aug 1999 11:47:28 +0200 Message-ID: <002801bedf27$c162f880$050aa8c0@0> Reply-To: "Corrado Cau" From: "Corrado Cau" To: Subject: Packages Date: Thu, 5 Aug 1999 11:48:57 +0200 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 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently downloaded and installed the most recent FreeBSD 4.0 -CURRENT, skipping the packages' download because of the size (I have the latest 3.2 CDROMs). The problem is that some packages (linux_base, in example), are missing from the 3.2 CDs and also that every time FreeBSD 4.0 complains about a previous release packages being used. I'm curios about packages compatibility, 'cause they look almost the same comparing 3.2 and 4.0 1) Can I use the 3.2 packages with FreeBSD 4.0 or am I doing a stupid thing? 2) In case I decide downloading the 4.0-current packages, how can I modify the INDEX file given I'd have to split the packages on a couple of CDs? No Rockridge extensions, please: I don't know how to use it. I don't have any internet link at home on the FreeBSD machine, so I can't simply download what I need when I need it. I have to do that beforehand, then burn a CD and fetch from it. No DOS partitions. BTW, the dependencies among packages are quite difficult to be guessed off-line :-) Thanks in advance, Corrado To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 5 3: 7:17 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.rp-plus.de (clubserv.rp-online.de [149.221.232.11]) by hub.freebsd.org (Postfix) with ESMTP id D84F2154A3 for ; Thu, 5 Aug 1999 03:07:10 -0700 (PDT) (envelope-from alex@cichlids.com) Received: from neutron.cichlids.com (as10-033.rp-plus.de [149.221.236.97]) by mail.rp-plus.de (8.9.1a/8.9.1) with ESMTP id MAA28655 for ; Thu, 5 Aug 1999 12:06:58 +0200 (METDST) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by neutron.cichlids.com (8.9.3/8.9.1) with ESMTP id MAA92684 for ; Thu, 5 Aug 1999 12:05:49 +0200 (CEST) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id MAA01475 for freebsd-current@FreeBSD.ORG; Thu, 5 Aug 1999 12:04:54 +0200 (CEST) (envelope-from alex) Date: Thu, 5 Aug 1999 12:04:53 +0200 From: Alexander Langer To: freebsd-current@FreeBSD.ORG Subject: Re: "w" date Message-ID: <19990805120453.A1374@cichlids.cichlids.com> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <19990803143047.A1776@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95i In-Reply-To: <19990803143047.A1776@cichlids.cichlids.com> X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake Alexander Langer (alex@cichlids.com): > root p0 0.10 04Nov35 - (w) > bash-2.02# date > Tue Aug 3 14:26:47 CEST 1999 > Take a look at the last one: p0. I logged in ~5 min before. > The date confuses me. I took a further look into the sources. usr.bin/w/* is not the problem, I´d say. It probably read the time wrong from /var/run/utmp if ((ut = fopen(_PATH_UTMP, "r")) == NULL) err(1, "%s", _PATH_UTMP); for (nusers = 0; fread(&utmp, sizeof(utmp), 1, ut);) { ... I don´t know, which daemon writes to /var/run/utmp. Maybe I should notice, that I´m logged in via ssh. Any ideas? BTW: My machine, that is some newer, told me a login @ 01Jan71 (or 72 or 70? I forgot, but it doesn´t matter. it´s wrong at all) just a minute ago. That´s also wrong but exactly the opposite of year 2035. Now, it tells me something wrong, AGAIN. But not so worse at all: I typed the following without any breaks, it took only ~5 seconds. bash-2.02# ssh cichlids root@cichlids's password: You have mail. bash-2.02# date Do 5 Aug 1999 12:02:59 CEST bash-2.02# w 12:02pm up 1:29, 2 users, load averages: 1.13, 1.11, 1.08 USER TTY FROM LOGIN@ IDLE WHAT alex v7 - 10:36am 1:26 -bash (bash) ttyp4 - 12:00pm 1:28 - bash-2.02# Strange. the login is at 12:02 and not at 12:00 ! What´s wrong with /var/run/utmp? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 5 3:13:40 1999 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 E76C714C58 for ; Thu, 5 Aug 1999 03:13:36 -0700 (PDT) (envelope-from dwmalone@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 5 Aug 1999 11:12:59 +0100 (BST) Date: Thu, 5 Aug 1999 11:12:58 +0100 From: David Malone To: Greg Lehey Cc: Archie Cobbs , Bruce Evans , current@FreeBSD.ORG Subject: Re: Panic plus advice needed Message-ID: <19990805111258.A70089@walton.maths.tcd.ie> References: <199908040936.TAA13368@godzilla.zeta.org.au> <199908041612.JAA98396@bubba.whistle.com> <19990805101049.W62948@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <19990805101049.W62948@freebie.lemis.com>; from Greg Lehey on Thu, Aug 05, 1999 at 10:10:49AM +0930 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Aug 05, 1999 at 10:10:49AM +0930, Greg Lehey wrote: > > So... IMHO, if we can fix this as well, it would be worth it for all > > the people who get core dumps but didn't build debug kernels. > > Do you disagree? > > I disagree that this should even be necessary. This kind of detail > was exactly the reason why I put the short-lived default debug kernel > into config. There aren't too many systems any more that don't have > an additional 30 MB for the time it takes to build the kernel, and it > solves a whole lot of potential problems. It does cause problems when you keep the kernels for 8 different machines in one /usr/src. I've never had any problems with -g generating different code as long as the stuff in vers.c doesn't change length. Being able to reproduce a kernel with debugging symbols seems like a reasonable aim to me. David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 5 3:23:10 1999 Delivered-To: freebsd-current@freebsd.org Received: from grisu.bik-gmbh.de (grisu.bik-gmbh.de [194.233.237.82]) by hub.freebsd.org (Postfix) with ESMTP id ED5FE14C58 for ; Thu, 5 Aug 1999 03:22:59 -0700 (PDT) (envelope-from cracauer@counter.bik-gmbh.de) Received: from counter.bik-gmbh.de (counter.bik-gmbh.de [194.233.237.131]) by grisu.bik-gmbh.de (8.8.8/8.6.9) with ESMTP id MAA14734; Thu, 5 Aug 1999 12:22:26 +0200 (MEST) Received: (from cracauer@localhost) by counter.bik-gmbh.de (8.9.3/8.8.8) id MAA87910; Thu, 5 Aug 1999 12:21:32 +0200 (CEST) (envelope-from cracauer) Date: Thu, 5 Aug 1999 12:21:32 +0200 From: Martin Cracauer To: Stephen Hocking-Senior Programmer PGS Tensor Perth Cc: current@FreeBSD.ORG Subject: Re: Assembler capable of supporting 3dnow! Message-ID: <19990805122131.A87591@cons.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Stephen Hocking-Senior Programmer PGS Tensor Perth on Sun, Aug 01, 1999 at 09:30:23AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In , Stephen Hocking-Senior Programmer PGS Tensor Perth wrote: > I'm messing around with the latest mesa and have discovered (suprise)that our > assembler doesn't support 3dnow instructions. Are there any plans to update to > a version of binutils that does? Linux's stuff appears to support it. > A build-time dependecy on ports/devel/nasm? Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.bik-gmbh.de/~cracauer/ "Where do you want to do today?" Hard to tell running your calendar program on a junk operating system, eh? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 5 5:55:53 1999 Delivered-To: freebsd-current@freebsd.org Received: from snafu.adept.org (adsl-63-193-112-19.dsl.snfc21.pacbell.net [63.193.112.19]) by hub.freebsd.org (Postfix) with ESMTP id F1A3C151DA for ; Thu, 5 Aug 1999 05:55:47 -0700 (PDT) (envelope-from mike@snafu.adept.org) Received: from localhost (mike@localhost) by snafu.adept.org (8.9.3/8.9.3) with ESMTP id FAA04106; Thu, 5 Aug 1999 05:55:30 -0700 (PDT) Date: Thu, 5 Aug 1999 05:55:30 -0700 (PDT) From: Mike Hoskins To: freebsd-current@freebsd.org Cc: mike@snafu.adept.org Subject: Promise/IDE 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, Just cvsup'd and running... FreeBSD snafu.adept.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Thu Aug 5 04:51:08 PDT 1999 root@snafu.adept.org:/usr/src/sys/compile/SNAFU i386 I have the following onboard... ide_pci0: at device 7.1 on pci0 and I just installed a Promise Ultra66. Here's my relevant kernel config stuff (following LINT's example): controller wdc0 at isa? port IO_WD1 irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port IO_WD2 irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 controller wdc2 at isa? port 0 irq ? flags 0xa0ffa0ff disk wd4 at wdc2 drive 0 disk wd5 at wdc2 drive 1 controller wdc3 at isa? port 0 irq ? flags 0xa0ffa0ff disk wd6 at wdc3 drive 0 disk wd7 at wdc3 drive 1 Dmesg shows my onboard controller, and all attached devices. Nothing seems to be shown for the Promise card, or the attached drives (two IBM 10GXPs)... Here's dmesg: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Aug 5 04:51:08 PDT 1999 root@snafu.adept.org:/usr/src/sys/compile/SNAFU Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 299942803 Hz CPU: Pentium II (299.94-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Features=0x80f9ff real memory = 134217728 (131072K bytes) avail memory = 127565824 (124576K bytes) Pentium Pro MTRR support enabled Probing for PnP devices: CSN 1 Vendor ID: CTL00c7 [0xc7008c0e] Serial 0x1c422c08 Comp ID: PNPb02f [0x2fb0d041] 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: irq 9 at device 0.0 on pci1 isab0: at device 7.0 on pci0 ide_pci0: at device 7.1 on pci0 chip1: irq 11 at device 7.2 on pci0 chip2: at device 7.3 on pci0 pci0: unknown card DBZ4d38 (vendor=0x105a, dev=0x4d38) at 14.0 irq 9 xl0: <3Com 3c900-COMBO Etherlink XL> irq 11 at device 16.0 on pci0 xl0: Ethernet address: 00:60:08:a0:55:09 xl0: selecting 10baseT transceiver, half duplex isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 wdc0 at port 0x1f0-0x1f7 irq 14 on isa0 wdc0: unit 0 (wd0): wd0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at port 0x170-0x177 irq 15 on isa0 wdc1: unit 0 (atapi): , removable, accel, ovlap, dma, iordy wcd0: drive speed 4133 - 4134KB/sec, 256KB cache wcd0: supported read types: CD-R, CD-RW, CD-DA wcd0: Audio: play, 255 volume levels wcd0: Mechanism: ejectable tray wcd0: Medium: no/blank disc inside, unlocked atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 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: configured irq 3 not in bitmap of probed irqs 0 ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 changing root device to wd0s1a I can decipher my AWE64 clearly from pnpinfo, but that's about it, here's the output: Checking for Plug-n-Play devices... Card assigned CSN #1 Vendor ID CTL00c7 (0xc7008c0e), Serial Number 0x1c422c08 PnP Version 1.0, Vendor Version 16 Device Description: Creative AWE64 PnP *** Small Vendor Tag Detected Logical Device ID: CTL0045 0x45008c0e #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: CTL0022 0x22008c0e #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 *** Small Vendor Tag Detected End Tag Successfully got 69 resources, 3 logical fdevs -- card select # 0x0001 CSN CTL00c7 (0xc7008c0e), Serial Number 0x1c422c08 Logical device #0 IO: 0x0220 0x0330 0x0388 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 5 0 DMA 1 5 IO range check 0x00 activate 0x01 Logical device #1 IO: 0x0200 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 Logical device #2 IO: 0x0620 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 IRQ 0 0 DMA 4 4 IO range check 0x00 activate 0x01 I'm placing a harddrive on the onboard controller's primary master port, CD-ROM on the secondary master, and a harddrive on each of the Promise's master ports... so as not to run any slaved drives. Maybe my mistake is obvious somewhere where it's not 6AM. -Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 5 8:28:24 1999 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 2048A14D32 for ; Thu, 5 Aug 1999 08:28:20 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-5.ucdavis.edu [169.237.16.133]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA02983; Thu, 5 Aug 1999 08:24:40 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA80572; Thu, 5 Aug 1999 08:24:38 -0700 (PDT) (envelope-from obrien) Date: Thu, 5 Aug 1999 08:24:36 -0700 From: "David O'Brien" To: Corrado Cau Cc: freebsd-current@freebsd.org Subject: Re: Packages Message-ID: <19990805082436.A78080@dragon.nuxi.com> Reply-To: obrien@freebsd.org References: <002801bedf27$c162f880$050aa8c0@0> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <002801bedf27$c162f880$050aa8c0@0>; from Corrado Cau on Thu, Aug 05, 1999 at 11:48:57AM +0200 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 > 1) Can I use the 3.2 packages with FreeBSD 4.0 or am I doing a stupid thing? Kinda. We provide different versions at ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/ because of there are some library difference between 3.x and 4.0. Not to mention anything that grubs around in the kernel. > 2) In case I decide downloading the 4.0-current packages, how can I modify > the INDEX file given I'd have to split the packages on a couple of CDs? No > Rockridge extensions, please: I don't know how to use it. AFAIK, you will need Rockridge extensions if you want any of the automatic dependencies loading to work. It isn't that hard. Just use the "-r" switch to ``mkisofs'' when you burn the image. > BTW, the dependencies among packages are quite difficult to be guessed > off-line :-) The INDEX files tells the dependencies. -- -- David (obrien@NUXI.com -or- obrien@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 Aug 5 8:29:33 1999 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 D6D2B14F3B for ; Thu, 5 Aug 1999 08:29:30 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-2-5.ucdavis.edu [169.237.16.133]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA02990; Thu, 5 Aug 1999 08:26:14 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA80827; Thu, 5 Aug 1999 08:26:11 -0700 (PDT) (envelope-from obrien) Date: Thu, 5 Aug 1999 08:26:08 -0700 From: "David O'Brien" To: Alexander Langer Cc: freebsd-current@FreeBSD.ORG Subject: Re: "w" date Message-ID: <19990805082608.B78080@dragon.nuxi.com> Reply-To: obrien@NUXI.com References: <19990803143047.A1776@cichlids.cichlids.com> <19990805120453.A1374@cichlids.cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.3i In-Reply-To: <19990805120453.A1374@cichlids.cichlids.com>; from Alexander Langer on Thu, Aug 05, 1999 at 12:04:53PM +0200 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 don´t know, which daemon writes to /var/run/utmp. > > Maybe I should notice, that I´m logged in via ssh. Was this version of ssh built on a 4.0 system, or 2.x? Usernames went from 8 chars to 16 chars. I was experiencing simular problems when I upgraded from 2.2.x to 3.0. -- -- David (obrien@NUXI.com -or- obrien@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 Aug 5 8:31: 2 1999 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 313F8151C1 for ; Thu, 5 Aug 1999 08:30:54 -0700 (PDT) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (iras-3-58.ucdavis.edu [169.237.17.58]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id IAA03010; Thu, 5 Aug 1999 08:29:31 -0700 (PDT) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id IAA82345; Thu, 5 Aug 1999 08:29:29 -0700 (PDT) (envelope-from obrien) Date: Thu, 5 Aug 1999 08:29:27 -0700 From: "David O'Brien" To: David Malone Cc: current@FreeBSD.ORG Subject: Re: Panic plus advice needed Message-ID: <19990805082926.C78080@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <199908040936.TAA13368@godzilla.zeta.org.au> <199908041612.JAA98396@bubba.whistle.com> <19990805101049.W62948@freebie.lemis.com> <19990805111258.A70089@walton.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <19990805111258.A70089@walton.maths.tcd.ie>; from David Malone on Thu, Aug 05, 1999 at 11:12:58AM +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 > > There aren't too many systems any more that don't have an additional > > 30 MB for the time it takes to build the kernel, and it solves a > > whole lot of potential problems. > > It does cause problems when you keep the kernels for 8 different machines > in one /usr/src. You are obiviously know what you are doing (since you are doing this AND running -CURRENT to boot). So you can easily make the partition you are using for this larger when you create it. Also since you have 8 different machines (presumable of differe types, or you'd use the same kernel on all of them), you have a little $$ that you could buy a cheap 4gig drive just for kernel building. -- -- David (obrien@NUXI.com -or- obrien@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 Aug 5 11:17:11 1999 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id EAACE15280 for ; Thu, 5 Aug 1999 11:16:59 -0700 (PDT) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id UAA41276; Thu, 5 Aug 1999 20:16:55 +0200 (CEST) (envelope-from sos) From: Soren Schmidt Message-Id: <199908051816.UAA41276@freebsd.dk> Subject: Re: Promise/IDE In-Reply-To: from Mike Hoskins at "Aug 5, 1999 5:55:30 am" To: mike@snafu.adept.org (Mike Hoskins) Date: Thu, 5 Aug 1999 20:16:55 +0200 (CEST) Cc: freebsd-current@FreeBSD.ORG, mike@snafu.adept.org X-Mailer: ELM [version 2.4ME+ PL43 (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 Mike Hoskins wrote: > and I just installed a Promise Ultra66. Here's my relevant kernel config > stuff (following LINT's example): > > pci0: unknown card DBZ4d38 (vendor=0x105a, dev=0x4d38) at 14.0 irq 9 Thats the promise controller, try the ata driver instead an use the following patch, let me know if it works... Index: ata-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.15 diff -u -r1.15 ata-all.c --- ata-all.c 1999/06/25 09:02:56 1.15 +++ ata-all.c 1999/08/05 18:14:11 @@ -184,6 +184,8 @@ return "Intel PIIX4 IDE controller"; case 0x4d33105a: return "Promise Ultra/33 IDE controller"; + case 0x4d38105a: + return "Promise Ultra/66 IDE controller"; case 0x522910b9: return "AcerLabs Aladdin IDE controller"; #if 0 @@ -241,7 +243,7 @@ #endif /* if this is a Promise controller handle it specially */ - if (type == 0x4d33105a) { + if (type == 0x4d33105a || type == 0x4d38105a) { iobase_1 = pci_read_config(dev, 0x10, 4) & 0xfffc; altiobase_1 = pci_read_config(dev, 0x14, 4) & 0xfffc; iobase_2 = pci_read_config(dev, 0x18, 4) & 0xfffc; @@ -318,7 +320,7 @@ if (!irq) printf("ata_pciattach: Unable to alloc interrupt\n"); - if (type == 0x4d33105a) + if (type == 0x4d33105a || type == 0x4d38105a) bus_setup_intr(dev, irq, INTR_TYPE_BIO, promise_intr, scp, &ih); else bus_setup_intr(dev, irq, INTR_TYPE_BIO, ataintr, scp, &ih); @@ -342,7 +344,7 @@ int rid = 0; void *ih; - if (type != 0x4d33105a) { + if (type != 0x4d33105a && type != 0x4d38105a) { irq = bus_alloc_resource(dev, SYS_RES_IRQ, &rid, 0, ~0, 1, RF_SHAREABLE | RF_ACTIVE); if (!irq) Index: ata-dma.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-dma.c,v retrieving revision 1.8 diff -u -r1.8 ata-dma.c --- ata-dma.c 1999/05/26 23:01:57 1.8 +++ ata-dma.c 1999/08/05 18:14:55 @@ -168,6 +168,7 @@ break; case 0x4d33105a: /* Promise Ultra/33 / FastTrack controllers */ + case 0x4d38105a: /* Promise Ultra/66 controllers */ devno = (scp->unit << 1) + (device ? 1 : 0); if (udmamode >=2) { printf("ata%d: %s: setting up UDMA2 mode on Promise chip ", -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 Aug 5 12:22:31 1999 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 8419415517 for ; Thu, 5 Aug 1999 12:22:19 -0700 (PDT) (envelope-from plm@smtp3.xs4all.nl) Received: from localhost. (dc2-isdn39.dial.xs4all.nl [194.109.148.39]) by smtp3.xs4all.nl (8.9.3/8.9.3) with ESMTP id VAA13792 for ; Thu, 5 Aug 1999 21:22:13 +0200 (CEST) Received: (from plm@localhost) by localhost. (8.9.3/8.9.3) id VAA00209; Thu, 5 Aug 1999 21:22:11 +0200 To: freebsd-current@freebsd.org Subject: recent apm changes From: Peter Mutsaers Date: 05 Aug 1999 07:27:01 +0200 Message-ID: <87n1w6hk62.fsf@muon.xs4all.nl> X-Mailer: Gnus v5.6.45/Emacs 20.3 Lines: 35 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, After Linux I gave FreeBSD a try again, when I saw some improvements to APM had been committed. I hoped for a real suspend mode, but alas. Now I'm wondering what makes the difference, and whether I could do it myself. Let me explain: I run my (desktop) computer in the living room. I don't want to shut it down all the time, but it must be 100% quiet when I'm not using it. In Linux, when suspend mode is activated (either through a short press on the power button or by the (BIOS) timer ), the disks also spin down (immediately, not waiting for their timer, which I disabled) and also the CPU fan and/or the FAN of the box switches off. In FreeBSD, when I activate suspend mode, I see the light on my computer blinking, indicating it has gone into suspend mode, but still there is no reduction in noise whatsoever. The disks keep spinning, the CPU fan (or whatever) too. I could activate the BIOS spindown timer on the HDD's, but I'd rather not (since then I also get spindowns while I'm normally working with the computer) but still the other fan will always continue to run. What can I do to change this behaviour? Can anyone explain what Linux (or Win95 for that matter) are doing to make it 100% quiet in suspend mode? Then I could give it a try to have FreeBSD do the same. Currently this prevents me from using FreeBSD alas. Thanks, -- Peter Mutsaers | Abcoude (Utrecht), | Trust me, I know plm@xs4all.nl | the Netherlands | what I'm doing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 5 13:19:36 1999 Delivered-To: freebsd-current@freebsd.org Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (Postfix) with ESMTP id 8712014D7C for ; Thu, 5 Aug 1999 13:19:28 -0700 (PDT) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (monica.cs.rpi.edu [128.213.7.2]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id QAA40383 for ; Thu, 5 Aug 1999 16:18:16 -0400 (EDT) Message-Id: <199908052018.QAA40383@cs.rpi.edu> To: freebsd-current@freebsd.org Subject: SMP and threads... Date: Thu, 05 Aug 1999 16:18:15 -0400 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a threaded appilcation that is only running on one processor. I remember there was discussion about this in the past, and there was a solution, I think it involved a patch. Any pointers? -- David Cross | email: crossd@cs.rpi.edu Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 5 13:34: 5 1999 Delivered-To: freebsd-current@freebsd.org Received: from sumatra.americantv.com (sumatra.americantv.com [208.139.222.227]) by hub.freebsd.org (Postfix) with ESMTP id 09D7B1554F for ; Thu, 5 Aug 1999 13:33:54 -0700 (PDT) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id PAA05734; Thu, 5 Aug 1999 15:33:47 -0500 (CDT) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.8.5/8.6.4) with ESMTP id PAA03199; Thu, 5 Aug 1999 15:33:46 -0500 (CDT) Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id PAA16082; Thu, 5 Aug 1999 15:33:45 -0500 (CDT) Date: Thu, 5 Aug 1999 15:33:45 -0500 (CDT) From: Jonathan Lemon Message-Id: <199908052033.PAA16082@free.pcs> To: plm@xs4all.nl, current@freebsd.org Subject: Re: recent apm changes X-Newsgroups: local.mail.freebsd-current In-Reply-To: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >In FreeBSD, when I activate suspend mode, I see the light on my >computer blinking, indicating it has gone into suspend mode, but still >there is no reduction in noise whatsoever. The disks keep spinning, >the CPU fan (or whatever) too. I could activate the BIOS spindown >timer on the HDD's, but I'd rather not (since then I also get >spindowns while I'm normally working with the computer) but still the >other fan will always continue to run. > >What can I do to change this behaviour? Can anyone explain what Linux >(or Win95 for that matter) are doing to make it 100% quiet in suspend >mode? Then I could give it a try to have FreeBSD do the >same. Currently this prevents me from using FreeBSD alas. FreeBSD's APM suspend works by sending the BIOS a suspend event for all BIOS managed devices, and the BIOS is supposed to put all devices under it's control into the "low-power suspend" state. I'd guess that this isn't the same as "off". You can't tell the BIOS to turn off all devices, you need to specify which devices to turn off. You could play around with adding something like this to apm_suspend_system (for your hdd:): sc->bios.r.eax = (APM_BIOS << 8) | APM_SETPWSTATE; sc->bios.r.ebx = 0x02ff; sc->bios.r.ecx = state ? PMST_APMENABLED : PMST_OFF; sc->bios.r.edx = 0; if (apm_bioscall()) printf("Failed to turn off HDD: errcode = %d\n", 0xff & (sc->bios.r.eax >> 8)); Of course, you'd probably also need a corresponding "turn on", call somewhere. As for your fan, I'm not sure what the deviceid for the fan would be, the "0x02ff" above means "all 2ndary storage devices". Perhaps "0x80FF", for all OEM devices. At the moment, there isn't the ability to control individual devices, but at some point, I can see this being added to the new-bus architecture; each device can register callbacks for various power management events. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 5 13:55:23 1999 Delivered-To: freebsd-current@freebsd.org Received: from exegrnnts001.seattleu.edu (exegrnnts001.seattleu.edu [206.81.198.91]) by hub.freebsd.org (Postfix) with ESMTP id E2AD814C57 for ; Thu, 5 Aug 1999 13:55:21 -0700 (PDT) (envelope-from hodeleri@seattleu.edu) Received: from seattleu.edu (ppp7.pm2a.wport.com [206.129.99.57]) by exegrnnts001.seattleu.edu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2448.0) id PKDHWS7R; Thu, 5 Aug 1999 13:53:15 -0700 Message-ID: <37A9FA33.426D35FC@seattleu.edu> Date: Thu, 05 Aug 1999 13:55:15 -0700 From: Eric Hodel Organization: Dis X-Mailer: Mozilla 4.51 [en] (X11; I; FreeBSD 3.2-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Peter Mutsaers Cc: freebsd-current@freebsd.org Subject: Re: recent apm changes References: <87n1w6hk62.fsf@muon.xs4all.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Peter Mutsaers wrote: > > Hello, > > After Linux I gave FreeBSD a try again, when I saw some improvements > to APM had been committed. > > I hoped for a real suspend mode, but alas. Now I'm wondering what > makes the difference, and whether I could do it myself. > > Let me explain: I run my (desktop) computer in the living room. I > don't want to shut it down all the time, but it must be 100% quiet > when I'm not using it. > > In Linux, when suspend mode is activated (either through a short press > on the power button or by the (BIOS) timer ), the disks also spin down > (immediately, not waiting for their timer, which I disabled) and also > the CPU fan and/or the FAN of the box switches off. > > In FreeBSD, when I activate suspend mode, I see the light on my > computer blinking, indicating it has gone into suspend mode, but still > there is no reduction in noise whatsoever. The disks keep spinning, > the CPU fan (or whatever) too. I could activate the BIOS spindown > timer on the HDD's, but I'd rather not (since then I also get > spindowns while I'm normally working with the computer) but still the > other fan will always continue to run. > > What can I do to change this behaviour? Can anyone explain what Linux > (or Win95 for that matter) are doing to make it 100% quiet in suspend > mode? Then I could give it a try to have FreeBSD do the > same. Currently this prevents me from using FreeBSD alas. Have you looked at PAO at all? http://www.jp.freebsd.org/PAO/ I've got a -current machine (no cvsups in a few months) that wakes up immediately after suspending. (sleeps 0 seconds) -- Eric Hodel hodeleri@seattleu.edu "They cook your gonies" -Terry Lambert's uncle on why he doesn't have a microwave To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 5 15:35:57 1999 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 1393014D9B; Thu, 5 Aug 1999 15:35:54 -0700 (PDT) (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 QAA99655; Thu, 5 Aug 1999 16:17:40 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id QAA12736; Thu, 5 Aug 1999 16:17:56 -0600 (MDT) Message-Id: <199908052217.QAA12736@harmony.village.org> To: Poul-Henning Kamp Subject: Re: junior-hacker task: "prepdisk" Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 01 Aug 1999 16:19:52 +0200." <19808.933517192@critter.freebsd.dk> References: <19808.933517192@critter.freebsd.dk> Date: Thu, 05 Aug 1999 16:17:56 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19808.933517192@critter.freebsd.dk> Poul-Henning Kamp writes: : It seems that our new boot blocks doesn't like the taste of disks : prepared according to the meagre information we have in the handbook. How does this script differ from 'disklabel -w wd0 auto'? It does do the fdisk stuff (your script, not the disklabel command). Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Aug 5 23:40:33 1999 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 6714314D20 for ; Thu, 5 Aug 1999 23:40:28 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA03127; Fri, 6 Aug 1999 08:38:12 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Warner Losh Cc: current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-reply-to: Your message of "Thu, 05 Aug 1999 16:17:56 MDT." <199908052217.QAA12736@harmony.village.org> Date: Fri, 06 Aug 1999 08:38:12 +0200 Message-ID: <3125.933921492@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908052217.QAA12736@harmony.village.org>, Warner Losh writes: >In message <19808.933517192@critter.freebsd.dk> Poul-Henning Kamp writes: >: It seems that our new boot blocks doesn't like the taste of disks >: prepared according to the meagre information we have in the handbook. > >How does this script differ from 'disklabel -w wd0 auto'? It does do >the fdisk stuff (your script, not the disklabel command). It differs in that you can boot from the disk afterwards with my script, you cant with disklabel -w wd0 auto. -- 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 Aug 6 0:18: 8 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 4063714E9C for ; Fri, 6 Aug 1999 00:18:03 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id RAA09944; Fri, 6 Aug 1999 17:18:01 +1000 Date: Fri, 6 Aug 1999 17:18:01 +1000 From: Bruce Evans Message-Id: <199908060718.RAA09944@godzilla.zeta.org.au> To: imp@village.org, phk@critter.freebsd.dk Subject: Re: junior-hacker task: "prepdisk" Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>: It seems that our new boot blocks doesn't like the taste of disks >>: prepared according to the meagre information we have in the handbook. >> >>How does this script differ from 'disklabel -w wd0 auto'? It does do >>the fdisk stuff (your script, not the disklabel command). > >It differs in that you can boot from the disk afterwards with my script, >you cant with disklabel -w wd0 auto. That may be because you forgot to supply the -r or -B args to disklabel, or forgot to edit the label using disklabel -e. I think no editing is required to boot from the 'c' partition (the missing d_type initialisation doesn't matter because the `d_type != DTYPE_SCSI' case defaults to DTYPE_ESDI (aka IDE)). The 'a' partition produced by `disklabel -Brw wd0 auto ' is obviosuly unbootable and unnewfsable, etc., since it is empty. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 0:23:36 1999 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 ECE1F14E9C for ; Fri, 6 Aug 1999 00:23:27 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id JAA03522; Fri, 6 Aug 1999 09:22:32 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans Cc: imp@village.org, current@FreeBSD.ORG Subject: Re: junior-hacker task: "prepdisk" In-reply-to: Your message of "Fri, 06 Aug 1999 17:18:01 +1000." <199908060718.RAA09944@godzilla.zeta.org.au> Date: Fri, 06 Aug 1999 09:22:31 +0200 Message-ID: <3520.933924151@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199908060718.RAA09944@godzilla.zeta.org.au>, Bruce Evans writes: >>>: It seems that our new boot blocks doesn't like the taste of disks >>>: prepared according to the meagre information we have in the handbook. >>> >>>How does this script differ from 'disklabel -w wd0 auto'? It does do >>>the fdisk stuff (your script, not the disklabel command). >> >>It differs in that you can boot from the disk afterwards with my script, >>you cant with disklabel -w wd0 auto. > >That may be because you forgot to supply the -r or -B args to disklabel, >[...] No it is because the fool BIOS belives the 50000 in the MBR. -- 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 Aug 6 1: 2:20 1999 Delivered-To: freebsd-current@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 6BAB4150CE for ; Fri, 6 Aug 1999 01:02:16 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA14585; Fri, 6 Aug 1999 18:01:51 +1000 Date: Fri, 6 Aug 1999 18:01:51 +1000 From: Bruce Evans Message-Id: <199908060801.SAA14585@godzilla.zeta.org.au> To: bde@zeta.org.au, phk@critter.freebsd.dk Subject: Re: junior-hacker task: "prepdisk" Cc: current@FreeBSD.ORG, imp@village.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>It differs in that you can boot from the disk afterwards with my script, >>>you cant with disklabel -w wd0 auto. > >>That may be because you forgot to supply the -r or -B args to disklabel, >>[...] > >No it is because the fool BIOS belives the 50000 in the MBR. This problem can be avoided by using fdisk to install a proper MBR before running disklabel. disklabel will then avoid writing to the MBR. fdisk even has reasonable defaults, but not what you want. Its default seems to be to create a proper MBR with slice 4 starting at sector 1 (0-based) and having size (size of disk rounded down to a fdisk's idea of a cylinder boundary) - 1. You want start 0 and size (size of disk). Of course, BIOSes could reasonably consider this partition as garbage since it overlaps the MBR. Similarly for partitions with start 1, since they overlap the first track. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 2: 3:47 1999 Delivered-To: freebsd-current@freebsd.org Received: from snafu.adept.org (adsl-63-193-112-19.dsl.snfc21.pacbell.net [63.193.112.19]) by hub.freebsd.org (Postfix) with ESMTP id 425B415005 for ; Fri, 6 Aug 1999 02:03:42 -0700 (PDT) (envelope-from mike@snafu.adept.org) Received: from localhost (mike@localhost) by snafu.adept.org (8.9.3/8.9.3) with ESMTP id CAA00369; Fri, 6 Aug 1999 02:01:47 -0700 (PDT) Date: Fri, 6 Aug 1999 02:01:47 -0700 (PDT) From: Mike Hoskins To: Soren Schmidt Cc: freebsd-current@FreeBSD.ORG Subject: Re: Promise/IDE (and NICs too!) In-Reply-To: <199908051816.UAA41276@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 Thu, 5 Aug 1999, Soren Schmidt wrote: > Thats the promise controller, try the ata driver instead an use the > following patch, let me know if it works... The patch applied cleanly... I still get: Copyright (c) 1992-1999 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Aug 6 01:12:13 PDT 1999 mike@snafu.adept.org:/usr/src/sys/compile/SNAFU Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 299942752 Hz CPU: Pentium II (299.94-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping = 3 Features=0x80f9ff real memory = 134217728 (131072K bytes) avail memory = 127594496 (124604K bytes) Pentium Pro MTRR support enabled Probing for PnP devices: CSN 1 Vendor ID: CTL00c7 [0xc7008c0e] Serial 0x1c422c08 Comp ID: PNPb02f [0x2fb0d041] 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: irq 9 at device 0.0 on pci1 isab0: at device 7.0 on pci0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 chip1: irq 11 at device 7.2 on pci0 chip2: at device 7.3 on pci0 pci0: unknown card DBZ4d38 (vendor=0x105a, dev=0x4d38) at 14.0 irq 9 pn0: <82c169 PNIC 10/100BaseTX> irq 11 at device 16.0 on pci0 pn0: Ethernet address: 00:c0:f0:48:18:51 pn0: autoneg complete, link status good (half-duplex, 10Mbps) isa0: on motherboard fdc0: at port 0x3f0-0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model IntelliMouse, device ID 3 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: configured irq 3 not in bitmap of probed irqs 0 ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 ata1: unwanted interrupt 1 status = ff ata0: master: setting up UDMA2 mode on PIIX4 chip OK ad0: ATA-3 disk at ata0 as master ad0: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S ad0: piomode=4, dmamode=2, udmamode=2 ad0: 16 secs/int, 0 depth queue, DMA mode acd0: CDROM drive at ata1 as master acd0: drive speed 4133 - 4134KB/sec, 256KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked changing root device to wd0s1a I'm seeing the onboard controller and its devices, but nothing from the Promise card. Out of curiosity, is this all I really need in my kernel config: controller ata0 device atadisk0 # ATA disk drives device atapicd0 # ATAPI CDROM drives Just double checking... although I must admit, I've toyed with every permutation imaginable. Oh, on a side note, the NIC's been changed from xl0 to pn0 (yes, I know, both are crapy cards - someday maybe an Intel will fall into my poor lap)... reason is my network connection seems to 'come and go'. By that I mean I'll be fine (IRC, mail, ping, etc.) one minute, then *boom* I loose all connectivity - can't even ping my gateway... This happened with xl0, so I tried pn0... still happens... is my DSL provider to blame, or is something up with -current? Traceroutes from outside boxes to me during these times die at my box, not within my provider's network... -Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 3:55: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from gaia.euronet.nl (gaia.euronet.nl [194.134.0.10]) by hub.freebsd.org (Postfix) with ESMTP id D2C0514DB4; Fri, 6 Aug 1999 03:54:57 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from mail.scc.nl (i441.ztm.euronet.nl [194.134.67.162]) by gaia.euronet.nl (8.8.8/8.8.8) with ESMTP id MAA17989; Fri, 6 Aug 1999 12:54:03 +0200 (MET DST) Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by mail.scc.nl (8.9.3/8.9.3) with ESMTP id MAA47198; Fri, 6 Aug 1999 12:53:30 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <37AABEAA.7A5A1D86@scc.nl> Date: Fri, 06 Aug 1999 12:53:30 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Eric J. Chet" Cc: Bernd Walter , Matthew Dillon , marcel@FreeBSD.ORG, phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VMware X11 and -current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Eric J. Chet" wrote: > > On Wed, 4 Aug 1999, Bernd Walter wrote: > > > It needs ttyp0 as tty0 and so on. > > I tried it myself under current and got the X11 window. > > but it complained that it can't find /proc/cpuinfo. > > I never beleaved that it would work after that. > > Hello > It should work, I used it under fbsd-3.2R for over two weeks with > X11 without any problems. I guess I might have to down grade to 3.2R. From the X server truss file: . . . syscall open("/var/run/ld-elf.so.hints",0,05001316750) returns 3 (0x3) . . . syscall open("/usr/lib/libc.so.3",0,05001316750) returns 3 (0x3) . . . You say it's a Linux binary. What is it doing with these FreeBSD files/libraries then? -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ Amsterdam, The Netherlands tel: +31 20 4200655 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 4: 9: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from gaia.euronet.nl (gaia.euronet.nl [194.134.0.10]) by hub.freebsd.org (Postfix) with ESMTP id CCA5F14DB4 for ; Fri, 6 Aug 1999 04:08:56 -0700 (PDT) (envelope-from marcel@scc.nl) Received: from mail.scc.nl (i439.ztm.euronet.nl [194.134.67.160]) by gaia.euronet.nl (8.8.8/8.8.8) with ESMTP id NAA24416; Fri, 6 Aug 1999 13:07:45 +0200 (MET DST) Received: from scc.nl (scones.sup.scc.nl [192.168.2.4]) by mail.scc.nl (8.9.3/8.9.3) with ESMTP id NAA47781; Fri, 6 Aug 1999 13:07:13 +0200 (CEST) (envelope-from marcel@scc.nl) Message-ID: <37AAC1E1.CF444850@scc.nl> Date: Fri, 06 Aug 1999 13:07:13 +0200 From: Marcel Moolenaar Organization: SCC vof X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Bernd Walter Cc: "Eric J. Chet" , current@FreeBSD.ORG Subject: Re: VMware X11 and -current References: <199908031618.JAA22028@apollo.backplane.com> <19990804000348.A25514@cicely8.cicely.de> Content-Type: multipart/mixed; boundary="------------3403E37D16C0767EF09D4EE0" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------3403E37D16C0767EF09D4EE0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Bernd Walter wrote: > It needs ttyp0 as tty0 and so on. > I tried it myself under current and got the X11 window. > but it complained that it can't find /proc/cpuinfo. > I never beleaved that it would work after that. I assume you didn't try to make a regular file called cpuinfo in /compat/linux/proc with the proper contents? An example is attached. -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ Amsterdam, The Netherlands tel: +31 20 4200655 --------------3403E37D16C0767EF09D4EE0 Content-Type: text/plain; charset=us-ascii; name="cpuinfo" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="cpuinfo" processor : 0 vendor_id : AuthenticAMD cpu family : 4 model : 14 model name : Am5x86-WT stepping : 4 fdiv_bug : no hlt_bug : no sep_bug : no f00f_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu bogomips : 65.74 --------------3403E37D16C0767EF09D4EE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 5:53:54 1999 Delivered-To: freebsd-current@freebsd.org Received: from web106.yahoomail.com (web106.yahoomail.com [205.180.60.73]) by hub.freebsd.org (Postfix) with SMTP id 0AF9614D65 for ; Fri, 6 Aug 1999 05:53:49 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19990806125321.9809.rocketmail@web106.yahoomail.com> Received: from [147.226.112.101] by web106.yahoomail.com; Fri, 06 Aug 1999 05:53:21 PDT Date: Fri, 6 Aug 1999 05:53:21 -0700 (PDT) From: "Valentin S. Chopov" Subject: Re: problem with last src/sys/pccard changes To: Warner Losh Cc: 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 wrote, I cvsuped both src/sys/pccard and src/usr.sbin/pccard and compiled and installed of course. Problem appears with new kernel code and new pccardd code, but is is OK with old kernel code an new pccardd code. But I already wrote this... BTW , my notebook is ISA only, w/o compiled PCI code. Val --- Warner Losh wrote: > In message > <19990803133657.24827.rocketmail@web109.yahoomail.com> > "Valentin S. Chopov" writes: > : > : After cvsup of src/sys/pccard and > src/usr.sbin/pccard > : from Aug 1, PCMCIA net card is not working. Te > message > : from pccardd is : > : > : Aug 3 02:28:42 valsho pccardd[256]: driver > allocation > : failed for IC-CARD(IC-CARD): Inappropriate ioctl > for > : device > : > : Also new pccardd is working with old kernel > code... > : So, may be te problem is in src/sys/pccard. > > Read UPDATING. You must recompile pccardd for the > new kernel. The > ioctl changed to pass the length of the io port > range into the kernel > rather than just the bottom end of the range. > > Warner > === Valentin S. Chopov 2301 West Bethel Ave., #53 Muncie, IN 47304-2112 Phone/Fax: (765)-214-0504 E-Mail: valsho@yahoo.com URL: http://profiles.yahoo.com/valsho _____________________________________________________________ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 6:31:33 1999 Delivered-To: freebsd-current@freebsd.org Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.189]) by hub.freebsd.org (Postfix) with SMTP id 4B0E015027 for ; Fri, 6 Aug 1999 06:31:28 -0700 (PDT) (envelope-from ejc@bazzle.com) Received: (qmail 94989 invoked from network); 6 Aug 1999 13:31:14 -0000 Received: from gargoyle.bazzle.com (206.103.246.189) by gargoyle.bazzle.com with SMTP; 6 Aug 1999 13:31:14 -0000 Date: Fri, 6 Aug 1999 09:31:14 -0400 (EDT) From: "Eric J. Chet" To: Marcel Moolenaar Cc: Bernd Walter , Matthew Dillon , phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VMware X11 and -current In-Reply-To: <37AABEAA.7A5A1D86@scc.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 Fri, 6 Aug 1999, Marcel Moolenaar wrote: > "Eric J. Chet" wrote: > > > > On Wed, 4 Aug 1999, Bernd Walter wrote: > > > > > It needs ttyp0 as tty0 and so on. > > > I tried it myself under current and got the X11 window. > > > but it complained that it can't find /proc/cpuinfo. > > > I never beleaved that it would work after that. > > > > Hello > > It should work, I used it under fbsd-3.2R for over two weeks with > > X11 without any problems. I guess I might have to down grade to 3.2R. > > >From the X server truss file: > . > . > . > syscall open("/var/run/ld-elf.so.hints",0,05001316750) > returns 3 (0x3) > . > . > . > syscall open("/usr/lib/libc.so.3",0,05001316750) > returns 3 (0x3) > . > . > . > > You say it's a Linux binary. What is it doing with these FreeBSD > files/libraries then? > At this point we must still be in freebsd xinit, then XF86_VMware(linux server) get started. I'm running a linux X server under freebsd. Under 3.2R all I had to do was change the symlink for X to point to XF86_VMware, under -current /dev/tty0 can't be found. Where was linux "/dev/tty0" coming from under emulation in 3.2R, the kernel device struct changed under -current? I made these symlinks as suggested, ttyp0 -> tty0 and ttyp4 -> tty4 gave me errors with VT_ACTIVE, VT_WAITACTIVE, VT_GETMODE. I should have to make these symlinks they should be handled under emulation, just like 3.2R. BTW: Another release of vmware for NT is out today. Thanks for your help, ejc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 6:55:51 1999 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 3D08115284; Fri, 6 Aug 1999 06:55:48 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:8VOxCRfqQ1SM9jHYKjI/TxcbV+L6OJ+N@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id WAA04284; Fri, 6 Aug 1999 22:55:09 +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 WAA23751; Fri, 6 Aug 1999 22:59:28 +0900 (JST) Message-Id: <199908061359.WAA23751@zodiac.mech.utsunomiya-u.ac.jp> To: "Eric J. Chet" Cc: Marcel Moolenaar , Bernd Walter , Matthew Dillon , phk@freebsd.org, current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VMware X11 and -current In-reply-to: Your message of "Fri, 06 Aug 1999 09:31:14 -0400." References: Date: Fri, 06 Aug 1999 22:59:28 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >At this point we must still be in freebsd xinit, then XF86_VMware(linux >server) get started. I'm running a linux X server under freebsd. Under >3.2R all I had to do was change the symlink for X to point to XF86_VMware, >under -current /dev/tty0 can't be found. > >Where was linux "/dev/tty0" coming from under emulation in 3.2R, the >kernel device struct changed under -current? > >I made these symlinks as suggested, ttyp0 -> tty0 and ttyp4 -> tty4 gave ~~~~~ ~~~~~ Symlinks should be ttyv0 -> tty0 and ttyv4 -> tty4. Notice ttyv*, not ttyp* ~ ~ Kazu >me errors with VT_ACTIVE, VT_WAITACTIVE, VT_GETMODE. I should have to >make these symlinks they should be handled under emulation, just like >3.2R. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 7:27:46 1999 Delivered-To: freebsd-current@freebsd.org Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.189]) by hub.freebsd.org (Postfix) with SMTP id 8BFA615573 for ; Fri, 6 Aug 1999 07:27:42 -0700 (PDT) (envelope-from ejc@bazzle.com) Received: (qmail 95440 invoked from network); 6 Aug 1999 14:27:07 -0000 Received: from gargoyle.bazzle.com (206.103.246.189) by gargoyle.bazzle.com with SMTP; 6 Aug 1999 14:27:07 -0000 Date: Fri, 6 Aug 1999 10:27:06 -0400 (EDT) From: "Eric J. Chet" To: Kazutaka YOKOTA Cc: Marcel Moolenaar , Bernd Walter , Matthew Dillon , phk@freebsd.org, current@freebsd.org Subject: Re: VMware X11 and -current In-Reply-To: <199908061359.WAA23751@zodiac.mech.utsunomiya-u.ac.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 On Fri, 6 Aug 1999, Kazutaka YOKOTA wrote: > > >At this point we must still be in freebsd xinit, then XF86_VMware(linux > >server) get started. I'm running a linux X server under freebsd. Under > >3.2R all I had to do was change the symlink for X to point to XF86_VMware, > >under -current /dev/tty0 can't be found. > > > >Where was linux "/dev/tty0" coming from under emulation in 3.2R, the > >kernel device struct changed under -current? > > > >I made these symlinks as suggested, ttyp0 -> tty0 and ttyp4 -> tty4 gave > ~~~~~ ~~~~~ > Symlinks should be ttyv0 -> tty0 and ttyv4 -> tty4. > > Notice ttyv*, not ttyp* > ~ ~ Hello I had tried it both ways, when I said having them symlinked to ttyv0 and ttyv4 would panic with "fatal trap 12" It was suggested that I use ttyp0 and ttyp4 respectfully. Are you running a linux Xserver under freebsd, XF86_VMware? Why arn't these needed under emulation with freebsd 3.2R? This is the main thing I'm looking for in the code. Thanks, Eric > Kazu > > >me errors with VT_ACTIVE, VT_WAITACTIVE, VT_GETMODE. I should have to > >make these symlinks they should be handled under emulation, just like > >3.2R. > Eric Chet -> ejc@bazzle.com ejc@FreeBSD.ORG echet@cms.cendant.com Senior Object Oriented Developer - Specializing in OOA, OOD, C++, Java, CORBA Kenpo JuJitsu the Ultimate in Self Defense, Tai Chi for Life cat man du : where UNIX geeks go when they die To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 7:32: 1 1999 Delivered-To: freebsd-current@freebsd.org Received: from fanf.noc.demon.net (fanf.noc.demon.net [195.11.55.83]) by hub.freebsd.org (Postfix) with ESMTP id 335AE15569 for ; Fri, 6 Aug 1999 07:31:52 -0700 (PDT) (envelope-from fanf@demon.net) Received: from fanf by fanf.noc.demon.net with local (Exim 3.02 #13) id 11Cl27-000Iov-00; Fri, 06 Aug 1999 15:31:43 +0100 To: crossd@cs.rpi.edu From: Tony Finch Cc: current@freebsd.org Subject: Re: SMP and threads... In-Reply-To: <199908052018.QAA40383@cs.rpi.edu> Message-Id: Date: Fri, 06 Aug 1999 15:31:43 +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David E. Cross" wrote: >I have a threaded appilcation that is only running on one processor. >I remember there was discussion about this in the past, and there was a >solution, I think it involved a patch. > >Any pointers? http://lt.tar.com Tony. -- f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 7:49: 8 1999 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 450FC14D29; Fri, 6 Aug 1999 07:49:02 -0700 (PDT) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:ONF7echp0SGvEqBBd5bZsHpEs7JU5hkQ@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id XAA04500; Fri, 6 Aug 1999 23:46: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 XAA24818; Fri, 6 Aug 1999 23:50:09 +0900 (JST) Message-Id: <199908061450.XAA24818@zodiac.mech.utsunomiya-u.ac.jp> To: "Eric J. Chet" Cc: Marcel Moolenaar , Bernd Walter , Matthew Dillon , phk@freebsd.org, current@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VMware X11 and -current In-reply-to: Your message of "Fri, 06 Aug 1999 10:27:06 -0400." References: Date: Fri, 06 Aug 1999 23:49:33 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> >At this point we must still be in freebsd xinit, then XF86_VMware(linux >> >server) get started. I'm running a linux X server under freebsd. Under >> >3.2R all I had to do was change the symlink for X to point to XF86_VMware, >> >under -current /dev/tty0 can't be found. >> > >> >Where was linux "/dev/tty0" coming from under emulation in 3.2R, the >> >kernel device struct changed under -current? >> > >> >I made these symlinks as suggested, ttyp0 -> tty0 and ttyp4 -> tty4 gave >> ~~~~~ ~~~~~ >> Symlinks should be ttyv0 -> tty0 and ttyv4 -> tty4. >> >> Notice ttyv*, not ttyp* >> ~ ~ >Hello > > I had tried it both ways, when I said having them symlinked to >ttyv0 and ttyv4 would panic with "fatal trap 12" It was suggested that I >use ttyp0 and ttyp4 respectfully. I don't think ttyp* will work. I don't know who suggested it to you. I have never run Linux X server binaries on FreeBSD, but, I can assure you that ttyp* won't work. The ttyp* refers to the "pseudo" tty. The Linux X server opens tty0 and tty4 which are "virtual terminals" in Linux. Virtual terminals are named ttyv* in FreeBSD. If the Linux X server are ever made to work in FreeBSD, it must be ttyv* which the X server should be fooled to access. VT_ACTIVATE, VT_WAITACTIVE and VT_GETMODE ioctls are valid only for virtual terminals ttyv* and certainly result in error for pseudo ttys. I suspect that the fatal trap you are seeing has little to do with ttyv* symlinks and the real culprit lies somewhere else. Kazu >Are you running a linux Xserver under freebsd, XF86_VMware? Why arn't >these needed under emulation with freebsd 3.2R? This is the main thing >I'm looking for in the code. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 8: 3: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.189]) by hub.freebsd.org (Postfix) with SMTP id 22EC614CF2 for ; Fri, 6 Aug 1999 08:02:54 -0700 (PDT) (envelope-from ejc@bazzle.com) Received: (qmail 95712 invoked from network); 6 Aug 1999 15:02:51 -0000 Received: from gargoyle.bazzle.com (206.103.246.189) by gargoyle.bazzle.com with SMTP; 6 Aug 1999 15:02:51 -0000 Date: Fri, 6 Aug 1999 11:02:51 -0400 (EDT) From: "Eric J. Chet" To: Kazutaka YOKOTA Cc: Marcel Moolenaar , Bernd Walter , Matthew Dillon , phk@freebsd.org, current@freebsd.org Subject: Re: VMware X11 and -current In-Reply-To: <199908061450.XAA24818@zodiac.mech.utsunomiya-u.ac.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 On Fri, 6 Aug 1999, Kazutaka YOKOTA wrote: > >Hello > > > > I had tried it both ways, when I said having them symlinked to > >ttyv0 and ttyv4 would panic with "fatal trap 12" It was suggested that I > >use ttyp0 and ttyp4 respectfully. > > I don't think ttyp* will work. I don't know who suggested it to you. > I have never run Linux X server binaries on FreeBSD, but, I can assure > you that ttyp* won't work. > > The ttyp* refers to the "pseudo" tty. The Linux X server opens tty0 > and tty4 which are "virtual terminals" in Linux. Virtual terminals > are named ttyv* in FreeBSD. If the Linux X server are ever made to > work in FreeBSD, it must be ttyv* which the X server should be fooled > to access. > > VT_ACTIVATE, VT_WAITACTIVE and VT_GETMODE ioctls are valid only for > virtual terminals ttyv* and certainly result in error for pseudo ttys. > > I suspect that the fatal trap you are seeing has little to do with > ttyv* symlinks and the real culprit lies somewhere else. > > Kazu Hello Kazu This I understand, as I believe it's somewhere else in the emulation changes between 3.2R and -current. The devices are what we see as the result of the error. Major changes I see to the emulation code from 3.2 to -current: 1. A number of ioctl and VT_ changes 2. divorce dev_t from major|minor bitmap. I would expect one of these change is causing the problem. Thanks again, Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 8:28:52 1999 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 52BF314E2E for ; Fri, 6 Aug 1999 08:28:46 -0700 (PDT) (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 JAA01966; Fri, 6 Aug 1999 09:28:17 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id JAA02414; Fri, 6 Aug 1999 09:28:16 -0600 (MDT) Message-Id: <199908061528.JAA02414@harmony.village.org> To: "Valentin S. Chopov" Subject: Re: problem with last src/sys/pccard changes Cc: current@FreeBSD.ORG In-reply-to: Your message of "Fri, 06 Aug 1999 05:53:21 PDT." <19990806125321.9809.rocketmail@web106.yahoomail.com> References: <19990806125321.9809.rocketmail@web106.yahoomail.com> Date: Fri, 06 Aug 1999 09:28:16 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19990806125321.9809.rocketmail@web106.yahoomail.com> "Valentin S. Chopov" writes: : I wrote, I cvsuped both src/sys/pccard and : src/usr.sbin/pccard and compiled and installed of : course. Problem appears with new kernel code and new : pccardd code, but is is OK with old kernel code an new : pccardd code. But I already wrote this... : BTW , my notebook is ISA only, w/o compiled PCI code. You may need to do a make includes as well to get the proper include files (or if you are afraid of that, you can copy src/sys/pccard/cardinfo.h to /usr/include/pccard/cardinfo.h) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 8:37:37 1999 Delivered-To: freebsd-current@freebsd.org Received: from web135.yahoomail.com (web135.yahoomail.com [205.180.60.20]) by hub.freebsd.org (Postfix) with SMTP id 2564214D00 for ; Fri, 6 Aug 1999 08:37:34 -0700 (PDT) (envelope-from valsho@yahoo.com) Message-ID: <19990806153740.6918.rocketmail@web135.yahoomail.com> Received: from [147.226.112.101] by web135.yahoomail.com; Fri, 06 Aug 1999 08:37:40 PDT Date: Fri, 6 Aug 1999 08:37:40 -0700 (PDT) From: "Valentin S. Chopov" Subject: Re: problem with last src/sys/pccard changes To: Warner Losh Cc: 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 It was my fault :( Now it's working. Thanks a lot! Val --- Warner Losh wrote: > You may need to do a make includes as well to get > the proper include > files (or if you are afraid of that, you can copy > src/sys/pccard/cardinfo.h to > /usr/include/pccard/cardinfo.h) > > Warner > === Valentin S. Chopov 2301 West Bethel Ave., #53 Muncie, IN 47304-2112 Phone/Fax: (765)-214-0504 E-Mail: valsho@yahoo.com URL: http://profiles.yahoo.com/valsho _____________________________________________________________ Do You Yahoo!? Free instant messaging and more at http://messenger.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 9:10:24 1999 Delivered-To: freebsd-current@freebsd.org Received: from vip.consys.com (VIP.ConSys.COM [209.141.107.6]) by hub.freebsd.org (Postfix) with ESMTP id 8BB7A155FF for ; Fri, 6 Aug 1999 09:10:20 -0700 (PDT) (envelope-from rcarter@pinyon.org) Received: (from pinyon@localhost) by vip.consys.com (8.9.3/8.9.1) id JAA38882; Fri, 6 Aug 1999 09:09:46 -0700 (MST) Date: Fri, 6 Aug 1999 09:09:46 -0700 (MST) From: "Russell L. Carter" Message-Id: <199908061609.JAA38882@vip.consys.com> To: crossd@cs.rpi.edu, dot@dotat.at Subject: Re: SMP and threads... Cc: current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |"David E. Cross" wrote: |>I have a threaded appilcation that is only running on one processor. |>I remember there was discussion about this in the past, and there was a |>solution, I think it involved a patch. |> |>Any pointers? | |http://lt.tar.com And don't be turned off by the "outdated" tunnel Richard stuck up there, delete the two references to deferred signals in the libc_r code that gets copied over into the port. Then you get a thread implementation that still works better than libc_r for things like TAO. (Although I haven't had a chance to rerun the tests with the libc_r changes this week). Russell | |Tony. |-- |f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix | | |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 Aug 6 10:21: 7 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.forumone.com (orion.forumone.com [207.197.141.10]) by hub.freebsd.org (Postfix) with ESMTP id 313B11556A for ; Fri, 6 Aug 1999 10:21:00 -0700 (PDT) (envelope-from adhir@forumone.com) Received: from adhir (unknown [216.181.56.84]) by mail.forumone.com (Postfix) with SMTP id 9FD30A8D5; Fri, 6 Aug 1999 13:20:33 -0400 (EDT) Reply-To: To: "'Russell L. Carter'" , , Cc: Subject: RE: SMP and threads... Date: Fri, 6 Aug 1999 13:21:56 -0400 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-reply-to: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal From: adhir@forumone.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why haven't changes like these been committed? > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of > Russell L. Carter > Sent: Friday, August 06, 1999 12:10 PM > To: crossd@cs.rpi.edu; dot@dotat.at > Cc: current@FreeBSD.ORG > Subject: Re: SMP and threads... > > > > |"David E. Cross" wrote: > |>I have a threaded appilcation that is only running on one > processor. > |>I remember there was discussion about this in the past, and > there was a > |>solution, I think it involved a patch. > |> > |>Any pointers? > | > |http://lt.tar.com > > And don't be turned off by the "outdated" tunnel Richard stuck > up there, delete the two references to deferred signals in > the libc_r code that gets copied over into the port. > Then you get a thread implementation that still works better > than libc_r for things like TAO. (Although I haven't had > a chance to rerun the tests with the libc_r changes this > week). > > Russell > > | > |Tony. > |-- > |f.a.n.finch dot@dotat.at fanf@demon.net e pluribus unix > | > | > |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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 10:22:25 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 2A3B4156B5 for ; Fri, 6 Aug 1999 10:22:15 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id TAA25481; Fri, 6 Aug 1999 19:20:02 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id TAA64172; Fri, 6 Aug 1999 19:19:37 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id TAA31975; Fri, 6 Aug 1999 19:20:27 +0200 (CEST) (envelope-from ticso) Date: Fri, 6 Aug 1999 19:20:27 +0200 From: Bernd Walter To: Marcel Moolenaar Cc: Bernd Walter , "Eric J. Chet" , current@FreeBSD.ORG Subject: Re: VMware X11 and -current Message-ID: <19990806192027.B31936@cicely8.cicely.de> References: <199908031618.JAA22028@apollo.backplane.com> <19990804000348.A25514@cicely8.cicely.de> <37AAC1E1.CF444850@scc.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <37AAC1E1.CF444850@scc.nl>; from Marcel Moolenaar on Fri, Aug 06, 1999 at 01:07:13PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 06, 1999 at 01:07:13PM +0200, Marcel Moolenaar wrote: > Bernd Walter wrote: > > > It needs ttyp0 as tty0 and so on. > > I tried it myself under current and got the X11 window. > > but it complained that it can't find /proc/cpuinfo. > > I never beleaved that it would work after that. > > I assume you didn't try to make a regular file called cpuinfo in > /compat/linux/proc with the proper contents? Damnit no - I was afraid that it was searching in /proc ... I will try it on monday. Thanks for the info and file contents. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 10:22:28 1999 Delivered-To: freebsd-current@freebsd.org Received: from mail.du.gtn.com (mail.du.gtn.com [194.77.9.57]) by hub.freebsd.org (Postfix) with ESMTP id 7E2211570C; Fri, 6 Aug 1999 10:22:15 -0700 (PDT) (envelope-from ticso@cicely8.cicely.de) Received: from cicely7.cicely.de (cicely.de [194.231.9.142]) by mail.du.gtn.com (8.8.6/8.8.6) with ESMTP id TAA25426; Fri, 6 Aug 1999 19:17:59 +0200 (MET DST) Received: from cicely8.cicely.de (cicely8.cicely.de [10.1.2.10]) by cicely7.cicely.de (8.9.0/8.9.0) with ESMTP id TAA64146; Fri, 6 Aug 1999 19:17:30 +0200 (CEST) Received: (from ticso@localhost) by cicely8.cicely.de (8.9.3/8.9.2) id TAA31960; Fri, 6 Aug 1999 19:18:20 +0200 (CEST) (envelope-from ticso) Date: Fri, 6 Aug 1999 19:18:20 +0200 From: Bernd Walter To: Kazutaka YOKOTA Cc: "Eric J. Chet" , Marcel Moolenaar , Bernd Walter , Matthew Dillon , phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: VMware X11 and -current Message-ID: <19990806191819.A31936@cicely8.cicely.de> References: <199908061450.XAA24818@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <199908061450.XAA24818@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Fri, Aug 06, 1999 at 11:49:33PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Aug 06, 1999 at 11:49:33PM +0900, Kazutaka YOKOTA wrote: > > >> >At this point we must still be in freebsd xinit, then XF86_VMware(linux > >> >server) get started. I'm running a linux X server under freebsd. Under > >> >3.2R all I had to do was change the symlink for X to point to XF86_VMware, > >> >under -current /dev/tty0 can't be found. > >> > > >> >Where was linux "/dev/tty0" coming from under emulation in 3.2R, the > >> >kernel device struct changed under -current? > >> > > >> >I made these symlinks as suggested, ttyp0 -> tty0 and ttyp4 -> tty4 gave > >> ~~~~~ ~~~~~ > >> Symlinks should be ttyv0 -> tty0 and ttyv4 -> tty4. > >> > >> Notice ttyv*, not ttyp* > >> ~ ~ > >Hello > > > > I had tried it both ways, when I said having them symlinked to > >ttyv0 and ttyv4 would panic with "fatal trap 12" It was suggested that I > >use ttyp0 and ttyp4 respectfully. > > I don't think ttyp* will work. I don't know who suggested it to you. > I have never run Linux X server binaries on FreeBSD, but, I can assure > you that ttyp* won't work. I dont know what tty0 is in linux - but why should vmware need a virtual terminal? > > The ttyp* refers to the "pseudo" tty. The Linux X server opens tty0 > and tty4 which are "virtual terminals" in Linux. Virtual terminals > are named ttyv* in FreeBSD. If the Linux X server are ever made to > work in FreeBSD, it must be ttyv* which the X server should be fooled > to access. > > VT_ACTIVATE, VT_WAITACTIVE and VT_GETMODE ioctls are valid only for > virtual terminals ttyv* and certainly result in error for pseudo ttys. > > I suspect that the fatal trap you are seeing has little to do with > ttyv* symlinks and the real culprit lies somewhere else. > I agree - even with the maybe wrong symlinks to ttyp* I was able to get the vmware window. -- B.Walter COSMO-Project http://www.cosmo-project.de ticso@cicely.de Usergroup info@cosmo-project.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 17:53:36 1999 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 E0FBB14CF1 for ; Fri, 6 Aug 1999 17:53:32 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id UAA48521 for ; Fri, 6 Aug 1999 20:51:18 -0400 (EDT) (envelope-from chuckr@picnic.mat.net) Date: Fri, 6 Aug 1999 20:51:18 -0400 (EDT) From: Chuck Robey To: FreeBSD-current@freebsd.org Subject: anoncvs 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 have anoncvs working now (straight anoncvs, not pserver): setenv CVSROOT anoncvs@anoncvs.freebsd.org:/cvs cvs get [some path] I wasn't aware of anyone using pserver method. Any users of anoncvs, could you please test this for me? IMPORTANT!! Reply directly to me, anyone scragging the list will be anathematized!! ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic and jaunt, both FreeBSD-current. (301) 220-2114 | ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Aug 6 23:41: 2 1999 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 2768114E6C for ; Fri, 6 Aug 1999 23:40:58 -0700 (PDT) (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 AAA04186; Sat, 7 Aug 1999 00:40:33 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id AAA07992; Sat, 7 Aug 1999 00:40:39 -0600 (MDT) Message-Id: <199908070640.AAA07992@harmony.village.org> To: Eric Hodel Subject: Re: recent apm changes Cc: Peter Mutsaers , freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 05 Aug 1999 13:55:15 PDT." <37A9FA33.426D35FC@seattleu.edu> References: <37A9FA33.426D35FC@seattleu.edu> <87n1w6hk62.fsf@muon.xs4all.nl> Date: Sat, 07 Aug 1999 00:40:38 -0600 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <37A9FA33.426D35FC@seattleu.edu> Eric Hodel writes: : I've got a -current machine (no cvsups in a few months) that wakes up : immediately after suspending. (sleeps 0 seconds) Hmmm, some laptops will wakeup on a keyboard interrupt. The interrupt that is waking you up may be the key up from the return you hit to make the event happen. PAO has a small sleep in the apm driver, while -current didn't the last time I looked. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 7 17:19: 2 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailhost.netbenefit.co.uk (fred.netbenefit.co.uk [212.53.64.13]) by hub.freebsd.org (Postfix) with ESMTP id 870A514C1B for ; Sat, 7 Aug 1999 17:18:55 -0700 (PDT) (envelope-from pierre.dampure@k2c.co.uk) Received: from userbl18.uk.uudial.com (k2c.co.uk) [62.188.144.125] by mailhost.netbenefit.co.uk with esmtp (NetBenefit 1.4) id 11DGdw-00062d-00; Sun, 8 Aug 1999 01:16:52 +0100 Message-ID: <37ACCB92.E48E7852@k2c.co.uk> Date: Sun, 08 Aug 1999 01:13:06 +0100 From: "Pierre Y. Dampure" Organization: K2C Ltd X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@freebsd.org Subject: Problem using XFree86 3.3.4 w/ VESA kernel option 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 There have been a few posts on -misc and on the XFree86 newsgroup reporting problems when using certain video adapters (The Voodoo 3 was one of them) w/ XFree86 3.3.4 on CURRENT. Symptoms varied from "pixelisation" when switching back to text mode, to "ghost" white lines when dragging windows, etc... After a bit of digging, I found that removing the VESA kernel option cured the problem on my Voodoo 3 2000 PCI adapter. I would be interesting to know whether this is the case for all other hardware? Cheers, PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Aug 7 18:22:43 1999 Delivered-To: freebsd-current@freebsd.org Received: from tele-post-20.mail.demon.net (tele-post-20.mail.demon.net [194.217.242.20]) by hub.freebsd.org (Postfix) with ESMTP id 2D30A14BD6; Sat, 7 Aug 1999 18:22:35 -0700 (PDT) (envelope-from gandalf@vilnya.demon.co.uk) Received: from vilnya.demon.co.uk ([158.152.19.238]) by tele-post-20.mail.demon.net with esmtp (Exim 2.12 #2) id 11DHdl-000KwG-0K; Sun, 8 Aug 1999 01:20:46 +0000 Received: from nenya (nenya.rings [10.2.4.3]) by vilnya.demon.co.uk (8.9.3/8.9.1) with SMTP id CAA19381; Sun, 8 Aug 1999 02:25:55 +0100 (BST) (envelope-from gandalf@vilnya.demon.co.uk) Message-ID: <000901bee13c$b1831dc0$0304020a@rings> From: "Cameron Grant" To: , Subject: it's time... Date: Sun, 8 Aug 1999 02:23:59 +0100 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.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 to let newpcm out of the cage so you can all get your grubby little hands on it. http://www.vilnya.demon.co.uk/newpcm+dfrpnp-19990807.diff.gz this is a patch against a recent -current. if you have a pci or isapnp soundcard, you should have pnp0 and pcm0 in your kernel config as appropriate. isapnp cards should not need any pnp lines in kernel.conf. the list of supported cards is as for luigi's driver, with the addition of a couple more mss-clones, and trident 4dwave. there is a part done aureal vortex driver which is as yet nonfunctional. mmap() is supported but not well tested. format conversions are supported. the code seems to be stable. please test it and email me success and failure reports. - cameron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message