From owner-freebsd-current Sun Dec 6 00:01:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA00514 for freebsd-current-outgoing; Sun, 6 Dec 1998 00:01:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from susanna.deranged.schneider.org (susanna.deranged.schneider.org [207.126.69.146]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA00500 for ; Sun, 6 Dec 1998 00:01:26 -0800 (PST) (envelope-from rik@deranged.schneider.org) Received: from localhost (rik@localhost) by susanna.deranged.schneider.org (8.9.1/8.9.1) with ESMTP id AAA16822; Sun, 6 Dec 1998 00:00:31 -0800 (PST) (envelope-from rik@deranged.schneider.org) X-Authentication-Warning: susanna.deranged.schneider.org: rik owned process doing -bs Date: Sun, 6 Dec 1998 00:00:28 -0800 (PST) From: Rik Schneider To: "David O'Brien" cc: Mike Smith , current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-Reply-To: <19981205234209.U10572@nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 5 Dec 1998, David O'Brien wrote: > > This limitation is not that major as most current BIOSes support the > > 2.8 format. > > Current maybe.. but I think you underestimate the number of older > machines people install FreeBSD on. > I should probably have stated that as most BIOSes that support El Torito (bootable cdrom) also understand the 2.88M floppy format. > -- > -- David (obrien@NUXI.ucdavis.edu -or- obrien@FreeBSD.org) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Rik Schneider Unix Systems Administrator Net Asset LLC 1315 Van Ness Ave Suite 103 Fresno CA 93721 (559) 490-4000 / rik@deranged.schneider.org | rik@netasset.com | wookie@smartasset.com \ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 00:07:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01130 for freebsd-current-outgoing; Sun, 6 Dec 1998 00:07:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp5.portal.net.au [202.12.71.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01125 for ; Sun, 6 Dec 1998 00:07:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA03309; Sun, 6 Dec 1998 00:05:34 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812060805.AAA03309@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Rik Schneider cc: "David O'Brien" , Mike Smith , current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Sun, 06 Dec 1998 00:00:28 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Dec 1998 00:05:32 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sat, 5 Dec 1998, David O'Brien wrote: > > > > This limitation is not that major as most current BIOSes support the > > > 2.8 format. > > > > Current maybe.. but I think you underestimate the number of older > > machines people install FreeBSD on. > > > > I should probably have stated that as most BIOSes that support El Torito > (bootable cdrom) also understand the 2.88M floppy format. The "support" is often shared between eg. a SCSI controller and the system BIOS proper. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Dec 6 00:21:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA01797 for freebsd-current-outgoing; Sun, 6 Dec 1998 00:21:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pyrl.eye (ppp-121.isl.net [199.3.25.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA01792 for ; Sun, 6 Dec 1998 00:21:27 -0800 (PST) (envelope-from ortmann@sparc.isl.net) Received: (from ortmann@localhost) by pyrl.eye (8.9.1/8.9.1) id CAA00821; Sun, 6 Dec 1998 02:21:02 -0600 (CST) (envelope-from ortmann) From: Daniel Ortmann Message-Id: <199812060821.CAA00821@pyrl.eye> Subject: Re: Bug in i386/apm/apm.c? In-Reply-To: <199812040834.TAA13942@godzilla.zeta.org.au> from Bruce Evans at "Dec 4, 1998 7:34:21 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 6 Dec 1998 02:21:00 -0600 (CST) Cc: archie@whistle.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >This looks like a bug... > > > >--- apm.c Thu Dec 3 23:09:47 1998 > >+++ apm.c.new Thu Dec 3 23:09:44 1998 > >@@ -795,7 +795,7 @@ > > sc->ds_base = (apm_ds_base << 4) + APM_KERNBASE; > > sc->cs32_limit = apm_cs32_limit - 1; > > if (apm_cs16_limit == 0) > >- apm_cs16_limit == apm_cs32_limit; > >+ apm_cs16_limit = apm_cs32_limit; > > sc->cs16_limit = apm_cs16_limit - 1; > > sc->ds_limit = apm_ds_limit - 1; > > sc->cs_entry = apm_cs_entry; > > PR: 8280 Could this also be related to PR: "kern/8940"? -- Daniel Ortmann IBM Circuit Technology 2414 30 av NW, #D E315, bldg 040-2 Rochester, MN 55901 3605 Hwy 52 N 507.288.7732 (h) 507.253.6795 (w) ortmann@isl.net ortmann@us.ibm.com -- "The answers are so simple and we all know where to look, but it's easier just to avoid the question." -- Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 00:57:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA03505 for freebsd-current-outgoing; Sun, 6 Dec 1998 00:57:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA03500 for ; Sun, 6 Dec 1998 00:57:49 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id AAA13839; Sun, 6 Dec 1998 00:56:29 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma013837; Sun, 6 Dec 98 00:56:19 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id AAA11754; Sun, 6 Dec 1998 00:56:19 -0800 (PST) From: Archie Cobbs Message-Id: <199812060856.AAA11754@bubba.whistle.com> Subject: Re: Bug in i386/apm/apm.c? In-Reply-To: <199812060821.CAA00821@pyrl.eye> from Daniel Ortmann at "Dec 6, 98 02:21:00 am" To: ortmann@sparc.isl.net (Daniel Ortmann) Date: Sun, 6 Dec 1998 00:56:18 -0800 (PST) Cc: bde@zeta.org.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Daniel Ortmann writes: > > >--- apm.c Thu Dec 3 23:09:47 1998 > > >+++ apm.c.new Thu Dec 3 23:09:44 1998 > > >@@ -795,7 +795,7 @@ > > > sc->ds_base = (apm_ds_base << 4) + APM_KERNBASE; > > > sc->cs32_limit = apm_cs32_limit - 1; > > > if (apm_cs16_limit == 0) > > >- apm_cs16_limit == apm_cs32_limit; > > >+ apm_cs16_limit = apm_cs32_limit; > > > sc->cs16_limit = apm_cs16_limit - 1; > > > sc->ds_limit = apm_ds_limit - 1; > > > sc->cs_entry = apm_cs_entry; > > > > PR: 8280 > > Could this also be related to PR: "kern/8940"? Could be I guess (I don't know from apm).. can you apply the patch and see if it fixes your problem? -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 Sun Dec 6 01:27:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04987 for freebsd-current-outgoing; Sun, 6 Dec 1998 01:27:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (196-31-98-194.iafrica.com [196.31.98.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04982 for ; Sun, 6 Dec 1998 01:27:20 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA18560; Sun, 6 Dec 1998 11:20:06 +0200 (SAT) From: Robert Nordier Message-Id: <199812060920.LAA18560@ceia.nordier.com> Subject: Re: New drivers and install floppy space In-Reply-To: <199812060655.WAA02653@dingo.cdrom.com> from Mike Smith at "Dec 5, 98 10:55:36 pm" To: mike@smith.net.au (Mike Smith) Date: Sun, 6 Dec 1998 11:20:02 +0200 (SAT) Cc: jkh@zippy.cdrom.com, mike@smith.net.au, wilko@yedi.iaf.nl, wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Mike Smith wrote: > It shouldn't really require MFS_ROOT turned on (the foo_ROOT options > are IMO bogus); it should always be checking for an mfs_root type > object. But no, the mfsroot image should indeed be either a UFS > filesystem or a FAT filesystem (the latter would make adding extra > drivers to the disk easier). > > > Hmmmmm. For that matter, we could make sure that the mfsroot was also > > a bootable floppy image with a /boot/boot.4th file on it which said: > > > > : yell 7 emit ." NO, BOOT THE OTHER FLOPPY, YOU KNOB!" cr ; > > > > yell > > key drop > > reset > > > > Or something to that effect. :-) > > That's an excellent argument for making it a UFS floppy, yes. Either > that, or ask Robert for a bootsector that says the same thing... FWIW, there's existing i386 code to do this in newfs_msdos.c. Just change the message displayed. I can always oblige with a FAT filesystem bootstrap, if we want to use FAT floppies. Because of a lower metadata overhead, FAT could be a lot more space-efficient than UFS. We can lose 90% of UFS's 16K for boot + superblock, for instance. And FAT dirents are only 32 bytes. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 02:12:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07500 for freebsd-current-outgoing; Sun, 6 Dec 1998 02:12:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ayukawa.aus.org (ayukawa.aus.org [199.166.246.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07491 for ; Sun, 6 Dec 1998 02:12:03 -0800 (PST) (envelope-from lh@aus.org) Received: from bsd.aus.org (bsd.aus.org [199.166.246.189]) by ayukawa.aus.org (8.8.7/8.7.3) with ESMTP id EAA14122 for ; Sun, 6 Dec 1998 04:53:12 -0500 (EST) Message-Id: <199812060953.EAA14122@ayukawa.aus.org> X-Mailer: XFMail 1.3-beta-042198 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812060140.RAA01908@bubba.whistle.com> Date: Sun, 06 Dec 1998 05:09:17 -0500 (EST) Reply-To: lh@aus.org From: Luke To: current@FreeBSD.ORG Subject: Re: sys/compile directories... Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> IMHO it's better to use sys/ARCH/compile to denote the architecture it's >> under >> (after all we make our kernel specifications in sys/ARCH/conf, so ../compile >> would seem logical, at least in my eyes) > > FWIW, I vote for sys/compile//. > > What about this idea.. "config -d directory ..." where you specify > the directory you want to compile in. config(8) automatically > adjusts all the filenames, etc. > > -Archie as a home user, just a small thing, as long as cd ../../compile/kernel-filename works, then its a somewhat transparent change. which sys/ARCH/conf sys/ARCH/compile seems to make work ,, sys/compile/ARCH/ & sys/conf/ARCH/ means someone who has used the tree for a while could be confused by having to go ../../compile/ARCH/NAME after running config. Also if more platforms are added and have more hardware specific code added, its more logical to goto src/sys/ARCH to look through the tree for stuff fot he machine, whereas in the 2nd case I assume there would just be more ARCH things throught the tree as opposed to trying to keep them together . --- E-Mail: Luke Sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 03:26:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14745 for freebsd-current-outgoing; Sun, 6 Dec 1998 03:26:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.wxs.nl (smtp01.wxs.nl [195.121.6.61]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14727 for ; Sun, 6 Dec 1998 03:25:57 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.198]) by smtp01.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA616D; Sun, 6 Dec 1998 12:25:48 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812060235.SAA02099@bubba.whistle.com> Date: Sun, 06 Dec 1998 12:31:21 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Archie Cobbs Subject: Re: sys/compile directories... Cc: freebsd-current@FreeBSD.ORG, (Eivind Eklund) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Dec-98 Archie Cobbs wrote: > Eivind Eklund writes: >> > What about this idea.. "config -d directory ..." where you specify >> > the directory you want to compile in. config(8) automatically >> > adjusts all the filenames, etc. >> >> http://www.freebsd.org/~eivind/config-objdir-patch2 > > I think for maximum flexibility you'd perhaps need a "-p path" > (default: "../..") for specifying the pathname to the top of the > /sys directory, since config builds the Makefile. If ye would add this and make ../.. the default then ye _must_ use the /sys/ARCH/compile/CONFIG. Else we would have to strip the kernel file of the machine line which contains the architecture and prepend that to the ../.. Moreso, the directory for conf lies in /sys/ARCH/conf, so we're splitting up the kernel conf files at architecture level, why not the compilation directories? I have to say I like the extension to config with the -d though. Makes it more customizable for the sysadmins. --- Jeroen Ruigrok van der Werven/Asmodai asmodai(at)wxs.nl | Cum angelis et pueris, Junior Network/Security Specialist | fideles inveniamur *BSD & picoBSD: The Power to Serve... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 06:50:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03600 for freebsd-current-outgoing; Sun, 6 Dec 1998 06:50:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03587; Sun, 6 Dec 1998 06:50:06 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:CYetFSubuDhjxFDjR6x8tevOY+HjYn/g@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id QAA05539; Sun, 6 Dec 1998 16:50:00 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:xWHdK8ecl2Q3tszVGjeCnfACUONd81O/@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id QAA52188; Sun, 6 Dec 1998 16:49:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812061449.QAA52188@greenpeace.grondar.za> To: "Jordan K. Hubbard" cc: "John W. DeBoskey" , freebsd-current@FreeBSD.ORG, markm@FreeBSD.ORG Subject: Re: telnetd again (Kerberos & make release == very strange) In-Reply-To: Your message of " Fri, 04 Dec 1998 23:02:03 PST." <3530.912841323@zippy.cdrom.com> References: <3530.912841323@zippy.cdrom.com> Date: Sun, 06 Dec 1998 16:49:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Hmmmm. I think it's time for the release engineer and Mark Murray > to go off into a corner somewhere and have a quick discussion about > this one. :-) Yes, boss... :-) 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 Sun Dec 6 07:20:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05572 for freebsd-current-outgoing; Sun, 6 Dec 1998 07:20:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05567 for ; Sun, 6 Dec 1998 07:20:49 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id PAA13386; Sun, 6 Dec 1998 15:20:36 GMT (envelope-from rb@gid.co.uk) Date: Sun, 6 Dec 1998 15:09:59 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Sun, 6 Dec 1998 15:09:59 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19981205234209.U10572@nuxi.com> References: ; from Rik Schneider on Sat, Dec 05, 1998 at 11:38:34PM -0800 <199812060720.XAA02870@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: obrien@NUXI.com From: Bob Bishop Subject: Re: New drivers and install floppy space Cc: Rik Schneider , Mike Smith , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, A suggestion: how many people are running PCI systems with only ISA controllers? How about two versions of boot floppy. #1 supports only ISA/EISA/VLB controllers and #2 supports PCI onward. CDROM can support both using a 2.88M image. Probably have to include the full mix of network interfaces and a representative selection of the proprietary CD drivers on both floppies. I don't have a good feel for whether this would free up enough space. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 07:29:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06224 for freebsd-current-outgoing; Sun, 6 Dec 1998 07:29:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from korin.warman.org.pl (korin.nask.waw.pl [195.187.243.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06219 for ; Sun, 6 Dec 1998 07:29:35 -0800 (PST) (envelope-from abial@nask.pl) Received: from localhost (abial@localhost) by korin.warman.org.pl (8.9.1/8.8.5) with SMTP id QAA18552; Sun, 6 Dec 1998 16:33:52 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Sun, 6 Dec 1998 16:33:51 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Eivind Eklund cc: Mark Tinguely , luigi@labinfo.iet.unipi.it, freebsd-current@FreeBSD.ORG Subject: Re: 3.0 and double operations in device drivers In-Reply-To: <19981203165746.J18661@follo.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, Eivind Eklund wrote: > On Thu, Dec 03, 1998 at 09:47:46AM -0600, Mark Tinguely wrote: > > > > My question is: "Is floating point math now taboo in the kernel?" > > > > > > it has always been! > > > > I asked for that one :). remove taboo and replace with "forbidden". > > It always has been. > > (Ie, it has never worked reliably, and this has been a known property > of the design). Ok, guys, tell me what I'm missing here: if the FP math cannot be used in kernel, then what for is the FPU emulator needed for SX processors??? Andrzej Bialecki -------------------- ++-------++ ------------------------------------- ||PicoBSD|| FreeBSD in your pocket? Go and see: Research & Academic |+-------+| "Small & Embedded FreeBSD" Network in Poland | |TT~~~| | 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 Dec 6 07:43:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07728 for freebsd-current-outgoing; Sun, 6 Dec 1998 07:43:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ligeti.cns.vt.edu. (ligeti.cns.vt.edu [128.173.12.161]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA07719 for ; Sun, 6 Dec 1998 07:43:52 -0800 (PST) (envelope-from gaylord@ligeti.cns.vt.edu) Received: by ligeti.cns.vt.edu. (SMI-8.6/SMI-SVR4) id KAA13728; Sun, 6 Dec 1998 10:43:50 -0500 From: gaylord@ligeti.cns.vt.edu (Clark Gaylord) Message-Id: <199812061543.KAA13728@ligeti.cns.vt.edu.> Subject: problems with make aout-to-elf To: freebsd-current@FreeBSD.ORG Date: Sun, 6 Dec 1998 10:43:50 -0500 (EST) Reply-To: cgaylord@cns.vt.edu X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In trying to make aout-to-elf, I have the following error. Any ideas of what is wrong? ===== ===== /usr/share/man/man4/cam.4.gz -> /usr/share/man/man4/scsi.4.gz ===> share/man/man4/man4.i386 install -c -o root -g wheel -m 444 adv.4.gz adw.4.gz aha.4.gz ahb.4.gz ahc.4.gz aic.4.gz alog.4.gz apm.4.gz ar.4.gz asc.4.gz bktr.4.gz bt.4.gz cs.4.gz cx.4.gz cy.4.gz de.4.gz dgb.4.gz dpt.4.gz ed.4.gz eg.4.gz el.4.gz en.4.gz ep.4.gz ex.4.gz fdc.4.gz fe.4.gz fxp.4.gz gsc.4.gz ie.4.gz io.4.gz joy.4.gz keyboard.4.gz labpc.4.gz le.4.gz lnc.4.gz lp.4.gz lpt.4.gz matcd.4.gz mcd.4.gz mem.4.gz meteor.4.gz mouse.4.gz mse.4.gz mtio.4.gz mx.4.gz nca.4.gz ncr.4.gz npx.4.gz pcf.4.gz pcm.4.gz pcvt.4.gz perfmon.4.gz pn.4.gz pnp.4.gz ppc.4.gz psm.4.gz rl.4.gz sb.4.gz scd.4.gz screen.4.gz sea.4.gz si.4.gz sio.4.gz spkr.4.gz sr.4.gz sysmouse.4.gz tl.4.gz tw.4.gz tx.4.gz uha.4.gz vr.4.gz vx.4.gz wb.4.gz wd.4.gz wfd.4.gz wl.4.gz wt.4.gz xl.4.gz ze.4.gz zp.4.gz /usr/share/man/man4/i386 install: mx.4.gz: No such file or directory *** Error code 71 Stop. *** Error code 1 ===== ===== I also have: (gaylord)/usr/src/share/man/man4/man4.i386 # ls .. ... icmp.4 man4.i386/ scsi.4 tty.4 ... (gaylord)/usr/src/share/man/man4/man4.i386 # ls ... bktr.4 gsc.4 mx.4 si.4 ze.4 ... Is this a problem because man4.i386 is a subdir of man4, whereas all the other man4 files are in man4 itself? I am cvsup'ing nightly with: /usr/local/bin/cvsup -L 2 /usr/local/cvsup/current-supfile and current-supfile: *default host=cvsup.FreeBSD.org *default base=/big/FreeBSD-current *default prefix=/big/FreeBSD-current *default release=cvs tag=. *default delete use-rel-suffix *default compress src-all src-eBones src-secure cvs-crypto ports-all Btw, this is breaking my sendmail (and many other things), so please e-mail directly to cgaylord@cns.vt.edu, as I cannot join freebsd-current yet. -- Clark Gaylord Communications Network Services Virginia Tech, Blacksburg, Virginia 24061-0506 Voice: 540/231-2347 Fax: 540/231-3928 E-mail: cgaylord@cns.vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 07:54:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08858 for freebsd-current-outgoing; Sun, 6 Dec 1998 07:54:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08853 for ; Sun, 6 Dec 1998 07:54:39 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id QAA41882; Sun, 6 Dec 1998 16:52:12 +0100 (CET) To: Andrzej Bialecki cc: Eivind Eklund , Mark Tinguely , luigi@labinfo.iet.unipi.it, freebsd-current@FreeBSD.ORG Subject: Re: 3.0 and double operations in device drivers In-reply-to: Your message of "Sun, 06 Dec 1998 16:33:51 +0100." Date: Sun, 06 Dec 1998 16:52:11 +0100 Message-ID: <41879.912959531@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Ok, guys, tell me what I'm missing here: if the FP math cannot be used in >kernel, then what for is the FPU emulator needed for SX processors??? For userland programs. If you execute an FP instruction the CPU traps into the kernel which has to carry out the stuff (or kill the process). -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 10:05:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20272 for freebsd-current-outgoing; Sun, 6 Dec 1998 10:05:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20264 for ; Sun, 6 Dec 1998 10:05:02 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.1/8.9.1) with ESMTP id TAA39675 for ; Sun, 6 Dec 1998 19:04:50 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) id TAA11295 for freebsd-current@freebsd.org; Sun, 6 Dec 1998 19:04:45 +0100 (CET) From: Cejka Rudolf Message-Id: <199812061804.TAA11295@kazi.dcse.fee.vutbr.cz> Subject: New bootloader - better without localized time? To: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org) Date: Sun, 6 Dec 1998 19:04:45 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying new bootloader. One of first things I saw was localized time in bootloader header. I think, this is too early to display localized datas (?). Is it possible to add this patch in /sys/boot/i386/loader/newvers.sh? (It is done in similar way as it is in /sys/conf/newvers.sh for kernel where localized time isn't ?either/too/neither?) --- newvers.sh.orig Sun Dec 6 18:22:55 1998 +++ newvers.sh Sun Dec 6 18:44:10 1998 @@ -35,6 +35,7 @@ # # @(#)newvers.sh 8.1 (Berkeley) 4/20/94 +LC_TIME=C; export LC_TIME u=${USER-root} h=`hostname` t=`date` #r=`head -n 6 $1 | tail -n 1 | awk -F: ' { print $1 } '` r=`awk -F: ' /^[0-9]\.[0-9]+:/ { print $1; exit }' $1` --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Technical University of Brno, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 12:04:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29572 for freebsd-current-outgoing; Sun, 6 Dec 1998 12:04:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA29567 for ; Sun, 6 Dec 1998 12:04:15 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:oE+Hbj40H2irYdBxYmWpe7ImDg8tgfI4@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id WAA06754; Sun, 6 Dec 1998 22:04:09 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:fPxS3kLEE5J+xydWmTUkRms2063Om/3c@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id WAA55026; Sun, 6 Dec 1998 22:04:08 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812062004.WAA55026@greenpeace.grondar.za> To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Subject: Re: telnetd again (Kerberos & make release == very strange) In-Reply-To: Your message of " Fri, 04 Dec 1998 23:02:03 PST." <3530.912841323@zippy.cdrom.com> References: <3530.912841323@zippy.cdrom.com> Date: Sun, 06 Dec 1998 22:04:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Hmmmm. I think it's time for the release engineer and Mark Murray > to go off into a corner somewhere and have a quick discussion about > this one. :-) I've had a look/think about this, and as far as I can see, this (strange!) behviour has not changed significantly since 1.1 days (at least) :-). JDP had handed us the solution on a plate; PAM. Once that is in, most of the @#$%ing kerberos mess goes down the toilet, and we can look forward to a much cleaner tree. I need to constuct an analagous behaviour for traffic encryption that will allow a pluggable module to encrypt arbitrary traffic in a rsh, rlogin, telnet session, but that (given my murderous workload) will take a while. I have this dream of being able to plug SSH into telnet and have it work in an exportable/optional way. 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 Sun Dec 6 13:11:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04627 for freebsd-current-outgoing; Sun, 6 Dec 1998 13:11:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04622 for ; Sun, 6 Dec 1998 13:11:03 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id QAA06389 for ; Sun, 6 Dec 1998 16:11:00 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA19793; Sun, 6 Dec 1998 16:10:59 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id QAA26242 for freebsd-current@freebsd.org; Sun, 6 Dec 1998 16:10:59 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812062110.QAA26242@bb01f39.unx.sas.com> Subject: boot.flp too big again... To: freebsd-current@FreeBSD.ORG Date: Sun, 6 Dec 1998 16:10:59 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (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, Just fyi if you haven't seen it. -John kzip -v /R/stage/boot.std/kernel real kernel start address will be: 0x100000 real kernel end address will be: 0x401270 kzip data start address will be: 0x2ae15c kzip data end address will be: 0x4091c4 sh -e /usr/src/release/scripts/doFS.sh /R/stage /mnt 1440 /R/stage/boot.std 80000 minimum disklabel: ioctl DIOCWLABEL: Operation not supported by device Warning: Block size restricts cylinders per group to 9. /dev/rvn0c: 2880 sectors in 1 cylinders of 1 tracks, 2880 sectors 1.4MB in 1 cyl groups (9 c/g, 12.66MB/g, 32 i/g) super-block backups (for fsck -b #) at: 32, cpio: write error: No space left on device *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. --- >>> build of 3.0-19981206-SNAP was an abject failure. --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 13:23:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA06168 for freebsd-current-outgoing; Sun, 6 Dec 1998 13:23:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from top.worldcontrol.com (snblitz.sc.scruznet.com [165.227.132.84]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA06163 for ; Sun, 6 Dec 1998 13:22:59 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 358 invoked by uid 100); 6 Dec 1998 21:27:05 -0000 Date: Sun, 6 Dec 1998 13:27:05 -0800 To: freebsd-current@FreeBSD.ORG Subject: wine, xfstt, and xfree86 3.3.3 strange error Message-ID: <19981206132705.A342@top.worldcontrol.com> Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.9i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running XFree86 3.3.3 and xfstt, with the first entry in my fontpath set to to "unix/:7100" When I run wine, the wine process hangs, xfstt core dumps with a signal 8, and XF86_SVGA starts burning up the cpu: 243 brian 102 5 11472K 8900K RUN 2:40 99.02% 99.02% XF86_SVGA killing wine, and restarted xfstt does not help XF86_SVGA. However, the system is still working. though nothing relying on the font server works. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 13:40:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07779 for freebsd-current-outgoing; Sun, 6 Dec 1998 13:40:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07772 for ; Sun, 6 Dec 1998 13:40:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id NAA39551; Sun, 6 Dec 1998 13:40:16 -0800 (PST) To: "John W. DeBoskey" cc: freebsd-current@FreeBSD.ORG Subject: Re: boot.flp too big again... In-reply-to: Your message of "Sun, 06 Dec 1998 16:10:59 EST." <199812062110.QAA26242@bb01f39.unx.sas.com> Date: Sun, 06 Dec 1998 13:40:15 -0800 Message-ID: <39539.912980415@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > Just fyi if you haven't seen it. Yep, I'm working on this now. It's time to make some fundamental decisions about what types of installations to make possible with boot.flp and which will have to go over to kern.flp/mfsroot.flp. I'm right now in the process of looking at the sizes of everything and trying to figure out where the best bang/buck ratios lie in trimming the fat from boot.flp. Should have it working again by tomorrow. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 17:11:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27242 for freebsd-current-outgoing; Sun, 6 Dec 1998 17:11:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pyrl.eye (ppp-120.isl.net [199.3.25.120]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27237 for ; Sun, 6 Dec 1998 17:11:48 -0800 (PST) (envelope-from ortmann@sparc.isl.net) Received: (from ortmann@localhost) by pyrl.eye (8.9.1/8.9.1) id TAA09128; Sun, 6 Dec 1998 19:10:49 -0600 (CST) (envelope-from ortmann) From: Daniel Ortmann Message-Id: <199812070110.TAA09128@pyrl.eye> Subject: Re: Bug in i386/apm/apm.c? In-Reply-To: <199812060856.AAA11754@bubba.whistle.com> from Archie Cobbs at "Dec 6, 1998 0:56:18 am" To: archie@whistle.com (Archie Cobbs) Date: Sun, 6 Dec 1998 19:10:47 -0600 (CST) Cc: ortmann@sparc.isl.net, bde@zeta.org.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Could this also be related to PR: "kern/8940"? > Could be I guess (I don't know from apm).. can you apply the patch > and see if it fixes your problem? This fix did not affect PR kern/8940. -- Daniel Ortmann IBM Circuit Technology 2414 30 av NW, #D E315, bldg 040-2 Rochester, MN 55901 3605 Hwy 52 N 507.288.7732 (h) 507.253.6795 (w) ortmann@isl.net ortmann@us.ibm.com -- "The answers are so simple and we all know where to look, but it's easier just to avoid the question." -- Kansas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 17:47:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29997 for freebsd-current-outgoing; Sun, 6 Dec 1998 17:47:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29992 for ; Sun, 6 Dec 1998 17:47:07 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id MAA03847; Mon, 7 Dec 1998 12:16:37 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812060720.XAA02870@dingo.cdrom.com> Date: Mon, 07 Dec 1998 12:16:37 +1030 (CST) From: "Daniel O'Connor" To: Mike Smith Subject: Re: New drivers and install floppy space Cc: current@FreeBSD.ORG, "Jordan K. Hubbard" , obrien@NUXI.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Dec-98 Mike Smith wrote: > No. The way that bootable CDROMs work is that the BIOS pretends that a > 1.44MB region at the beginning of the CDROM is actually a 1.44MB floppy > disk. Or 2.88Mb.. Not a solution, but some more space.. Hmm.. actually, the El Torrito spec says you can emulate a HD as well.. Of course thats the spec, I have absolutly no idea how that is reflected in reality. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 17:52:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00626 for freebsd-current-outgoing; Sun, 6 Dec 1998 17:52:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00621 for ; Sun, 6 Dec 1998 17:52:32 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id CAA13594; Mon, 7 Dec 1998 02:48:59 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199812070148.CAA13594@ocean.campus.luth.se> Subject: Re: New drivers and install floppy space In-Reply-To: <199812060720.XAA02870@dingo.cdrom.com> from Mike Smith at "Dec 5, 98 11:20:17 pm" To: mike@smith.net.au (Mike Smith) Date: Mon, 7 Dec 1998 02:48:59 +0100 (CET) Cc: obrien@NUXI.com, jkh@zippy.cdrom.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Mike Smith: > > > When a majority can no longer be thusly accommodated, we'll just shrug > > > and ditch it completely in favor of the 2(*)-floppy solution. > > > > It is not that bad. I'm doing more and more boot off the CDROM installs. > > I assume sysinstall + boot kernel can be quite large there. > > Is the boot kernel there a full GENERIC kernel? > > No. The way that bootable CDROMs work is that the BIOS pretends that a > 1.44MB region at the beginning of the CDROM is actually a 1.44MB floppy > disk. > > I wouldn't mind finding the asshole responsible for this fiasco and > doing something traumatic to their lower digestive tract with a > petrol-powered Weed Eater. > > The only ways out of this are: > > - mandate a floppy in addition to the CDROM (sucks) > - add CDROM drivers to the bootloader (ATAPI, SCSI for Adaptec and NCR > at least) > > Both of these are painful. Less so than the Weed Eater, is my guess. :-) But... we have 1.44 MB on the CD... Since the bios manages to read the file, wouldn't there be a generic way that we could also read something from the CD? So that we could make a floppy which does a call and reads a 5 MB image from the CD, and unpacks the kernel with MFS from that, with full drivers and a nice splash image, too. :-) But, lemme guess: "Sorry... There's no way to fool the BIO to read the CD" ? /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 17:55:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01122 for freebsd-current-outgoing; Sun, 6 Dec 1998 17:55:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01112 for ; Sun, 6 Dec 1998 17:55:49 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id CAA13609; Mon, 7 Dec 1998 02:52:40 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199812070152.CAA13609@ocean.campus.luth.se> Subject: Re: New drivers and install floppy space In-Reply-To: <199812060741.XAA03107@dingo.cdrom.com> from Mike Smith at "Dec 5, 98 11:41:11 pm" To: mike@smith.net.au (Mike Smith) Date: Mon, 7 Dec 1998 02:52:40 +0100 (CET) Cc: tlambert@primenet.com, wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Mike Smith: > > o a mechanism for dumping drivers from the kernel after > > installation so that they need not be installed twice: > > once to boot, once to install; this probably implies > > driver data areas be mapped copy-on-write to maintain > > the data image integrity to allow it to be written > > back out > > This is actually fairly tough, as the entire ELF object is not loaded > in the first place. My preference is simply to track the driver(s) > that are loaded, and request the use re-provide the media from which > the driver was read when it comes time to copy it. Wouldn't the best and easiest solution here be something like this in the loader: save_drivers_in_ram = (total_ram_MB > 8); And if the variable is set, you just don't load the driver, you also store the complete file it was loaded from in a memory block which can then just be dumped to file. If you don't have enough memory to do that, you can ask for the disks again, instead. /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 17:55:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01145 for freebsd-current-outgoing; Sun, 6 Dec 1998 17:55:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01133 for ; Sun, 6 Dec 1998 17:55:54 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40339>; Mon, 7 Dec 1998 12:55:06 +1100 Date: Mon, 7 Dec 1998 12:55:37 +1100 From: Peter Jeremy Subject: Re: New drivers and install floppy space To: current@FreeBSD.ORG Message-Id: <98Dec7.125506est.40339@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > The way that bootable CDROMs work is that the BIOS pretends that a >1.44MB region at the beginning of the CDROM is actually a 1.44MB floppy >disk. I tend to support Mike's views on this stupidity. >The only ways out of this are: > > - mandate a floppy in addition to the CDROM (sucks) > - add CDROM drivers to the bootloader (ATAPI, SCSI for Adaptec and NCR > at least) Some additional ideas: - put a `mini-kernel' into the CD-ROM boot area. This kernel would really be just a protected-mode bootloader - it has all the CD-ROM drivers and minimal support code to be able to read the real kernel out of the ISO-9660 filesystem. (The reason for making it PM is to let it re-use the existing kernel code, rather than needing a 2nd set of CD-ROM drivers). - A 3.0-RELEASE kernel.GENERIC is nearly 1.9MB - far too large for a floppy, even stripped it's 1.6MB (and will only get larger as time goes by). If it's stripped and gzip'd, it's only 850KB (but a copy of gunzip will boost this somewhat). Why not just put a compressed kernel into the boot area? It doesn't need to include the /stand/* functions because they can be read out of the CD-ROM. Similarly, a normal kernel.GENERIC can be installed from the CD-ROM. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 18:35:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04665 for freebsd-current-outgoing; Sun, 6 Dec 1998 18:35:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04660 for ; Sun, 6 Dec 1998 18:35:28 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id SAA01844; Sun, 6 Dec 1998 18:35:23 -0800 (PST) (envelope-from ulf) Message-ID: <19981206183522.I27271@TelcoSucks.org> Date: Sun, 6 Dec 1998 18:35:22 -0800 From: Ulf Zimmermann To: Mike Smith , obrien@NUXI.com Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: New drivers and install floppy space Reply-To: ulf@Alameda.net References: <19981205021914.C12672@nuxi.com> <199812060720.XAA02870@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812060720.XAA02870@dingo.cdrom.com>; from Mike Smith on Sat, Dec 05, 1998 at 11:20:17PM -0800 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 05, 1998 at 11:20:17PM -0800, Mike Smith wrote: > > > When a majority can no longer be thusly accommodated, we'll just shrug > > > and ditch it completely in favor of the 2(*)-floppy solution. > > > > It is not that bad. I'm doing more and more boot off the CDROM installs. > > I assume sysinstall + boot kernel can be quite large there. > > Is the boot kernel there a full GENERIC kernel? > > No. The way that bootable CDROMs work is that the BIOS pretends that a > 1.44MB region at the beginning of the CDROM is actually a 1.44MB floppy > disk. There is also support for harddisk. I have a URL with the exact description. Building an image right now for another project. > > I wouldn't mind finding the asshole responsible for this fiasco and > doing something traumatic to their lower digestive tract with a > petrol-powered Weed Eater. > > The only ways out of this are: > > - mandate a floppy in addition to the CDROM (sucks) > - add CDROM drivers to the bootloader (ATAPI, SCSI for Adaptec and NCR > at least) > > Both of these are painful. > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 20:59:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15573 for freebsd-current-outgoing; Sun, 6 Dec 1998 20:59:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mars.ecsnet.com (mars.ecsnet.com [204.57.81.130]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA15566 for ; Sun, 6 Dec 1998 20:59:18 -0800 (PST) (envelope-from mevans@ecsnet.com) Received: (qmail 29389 invoked from network); 7 Dec 1998 04:58:43 -0000 Received: from alpha.ecsnet.com (204.57.81.131) by mars.ecsnet.com with SMTP; 7 Dec 1998 04:58:43 -0000 Date: Sun, 6 Dec 1998 23:01:33 -0600 (CST) From: Mark Evans To: current@FreeBSD.ORG Subject: Tk/Tcl Programs Freeze X Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've started having a problem in the past week on two CURRENT systems where any Tk/Tcl based program will freeze X when they exit. The system is not frozen, just X. This has happened on both XFree86 3.3.2 and XFree86 3.3.3. It happens with any Tk/Tcl based program regardless of the version of Tk/Tcl being used. TkDesk 1.1 locks, as does TkRat, etc. The kernel is up-to-date as of Dec 5th and I've done a make world as well. Nothing in the logs. But if I boot a 3.0-RELEASE kernel everything works fine. This has happened on two systems, both using the SVGA X server and both started showing this in the past week. Any advice on gaining additonal debugging info would be appreciated. Thanks! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 21:05:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA15930 for freebsd-current-outgoing; Sun, 6 Dec 1998 21:05:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from firewall.scitec.com.au (fgate.scitec.com.au [203.17.180.68]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA15922 for ; Sun, 6 Dec 1998 21:05:18 -0800 (PST) (envelope-from john.saunders@scitec.com.au) Received: by firewall.scitec.com.au; id QAA13671; Mon, 7 Dec 1998 16:05:08 +1100 (EST) Received: from mailhub.scitec.com.au(203.17.180.131) by fgate.scitec.com.au via smap (3.2) id xma013661; Mon, 7 Dec 98 16:05:00 +1100 Received: from saruman (saruman.scitec.com.au [203.17.182.108]) by mailhub.scitec.com.au (8.6.12/8.6.9) with SMTP id QAA29778 for ; Mon, 7 Dec 1998 16:04:56 +1100 From: "John Saunders" To: "FreeBSD current" Subject: RE: Booting 3.0-RELEASE in a non-standard setup Date: Mon, 7 Dec 1998 16:04:56 +1100 Message-ID: <002901be219f$21d16400$6cb611cb@saruman.scitec.com.au> 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: <199812030958.LAA14987@ceia.nordier.com> X-Mimeole: Produced By Microsoft MimeOLE V4.72.2106.4 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FYI (Information obtained from this weekends hacking) It is possible to have FreeBSD 2.2.x and 3.x co-existing on the same disk in different partitions. What makes this possible is the new boot blocks by Robert Nordier. You also need to make certain that the 2.2.x partition comes first in the partition table (although I don't think it need come first on the disk). So how is it done? Case 1: You have FreeBSD 2.2.x on your wd0 drive in the s1 slice and you have a spare partition (s2 slice) for 3.0. Simply boot off the CDROM (or floppies) and do a normal install proceedure. You will note when you get to the disklabel editor that the 2.2.x (s1 slice) partitions are listed, do not touch these. At this stage you may decide not to create swap space for 3.0 and let the 2.2.x swap space get used by both systems. Otherwise you can create a swap partition inside your s2 slice. Reboot your system into 2.2.x and mount the root 3.0 filesystem (wd0s2a) on /mnt then do "disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 wd0s2" to upgrade to the new boot blocks. Edit the /mnt/etc/fstab file to fix up the swap entries (if you are sharing swap space then no need to fix anything). Reboot your system and then using BootEasy press F2 and hopefully 3.0-RELEASE will boot up. Case 2: You have FreeBSD 2.2.x on your wd2 (second) drive in the s1 slice and you have a spare partition (s2 slice) for 3.0. Simply boot off the CDROM (or floppies) and do a normal install proceedure. You will note when you get to the disklabel editor that the 2.2.x (s1 slice) partitions are listed, do not touch these. At this stage you may decide not to create swap space for 3.0 and let the 2.2.x swap space get used by both systems. Otherwise you can create a swap partition inside your s2 slice. Reboot your system into 2.2.x and mount the root 3.0 filesystem (wd2s2a) on /mnt then do "disklabel -B -b /mnt/boot/boot1 -s /mnt/boot/boot2 wd2s2" to upgrade to the new boot blocks. Edit the /mnt/etc/fstab file to fix up the swap entries (if you are sharing swap space then no need to fix anything). Also edit the /mnt/boot.config and add a single line with "1:wd(2,2,a)kernel" but don't include the " characters. Reboot your system and then using BootEasy press F5 to switch to the second drive then F2 and hopefully 3.0-RELEASE will boot up. Sharing swap: Sysinstall notices that the slice used for 2.2.x has a swap partition and happily adds this to the /etc/fstab file. If you create swap space in your 3.0 slice then sysinstall will add both the 2.2.x swap space and the 3.0 swap space to your /etc/fstab file. If you don't create any in the 3.0 slice then only the 2.2.x swap space is added to /etc/fstab. Boot Blocks: The default boot blocks installed with 3.0 will only start 2.2.x. So no matter what function key you press, 2.2.x will get started. The new boot blocks can be written by the disklabel program with 2.2.x. disklabel -B -b boot1 -s boot2 The new boot blocks load the /boot.config file which specifies the information needed to load the kernel from the correct slice and mount the correct root filesystem. It appears to be impossible to specify this information in any way other than editing the file from another running system. The old boot blocks allowed you to enter this from the command line. We probably need a ctrl sequence to escape into a command line for this. If you press any key the /boot/loader file will be started and it won't work properly in the case where the BIOS drive number doesn't match the wd drive number. So never press a key, let the boot block load the kernel directly. Cheers. -- . +-------------------------------------------------------+ ,--_|\ | John Saunders mailto:John.Saunders@scitec.com.au | / Oz \ | SCITEC LIMITED Phone +61294289563 Fax +61294289933 | \_,--\_/ | "By the time you make ends meet, they move the ends." | v +-------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 21:46:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19636 for freebsd-current-outgoing; Sun, 6 Dec 1998 21:46:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19631 for ; Sun, 6 Dec 1998 21:46:48 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id AAA05671; Mon, 7 Dec 1998 00:46:20 -0500 (EST) Date: Mon, 7 Dec 1998 00:46:20 -0500 (EST) From: "Matthew N. Dodd" To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-Reply-To: <199812050125.RAA01279@dingo.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Dec 1998, Mike Smith wrote: > > On Wed, 2 Dec 1998, Mike Smith wrote: > > > It would certainly be feasible to arrange for the firmware images to > > > be loaded from separate files, should that be an acceptable > > > alternative. I'm open to suggestions on how to make this economical > > > and robust... > > > > Ooh! Ooh! Me Me! > > You have ideas, or you want the functionality? 8) Functionality of course. :) > > I was kind of wondering how to avoid compiling in 20 to 60 Kb of firmware > > image for support of RAM based TMS380 cards. In addition, some each > > particular card may have specific firmware it wants loaded. I'm looking > > for some way to load a really basic config file to let the driver know > > which image goes with which card. > > > > Doing this from userland isn't good as I can't do much with the card until > > the firmware is loaded. > > Are these PnP devices, ie. can you differentiate between them before > running the probe? Are they ever likely to be critical to the boot > process? ISA/ISA-PnP/EISA/PCI bards. How critical to the boot process are network cards? -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 21:57:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20370 for freebsd-current-outgoing; Sun, 6 Dec 1998 21:57:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20365 for ; Sun, 6 Dec 1998 21:57:43 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca36-54.ix.netcom.com [207.92.172.54]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id VAA15073; Sun, 6 Dec 1998 21:57:35 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id VAA08244; Sun, 6 Dec 1998 21:57:32 -0800 (PST) Date: Sun, 6 Dec 1998 21:57:32 -0800 (PST) Message-Id: <199812070557.VAA08244@silvia.hip.berkeley.edu> To: dillon@apollo.backplane.com CC: current@FreeBSD.ORG In-reply-to: <199812041952.LAA16925@apollo.backplane.com> (message from Matthew Dillon on Fri, 4 Dec 1998 11:52:56 -0800 (PST)) Subject: Re: weird rsh hang From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Try rsh mach1 -n cat file for the first rsh. You're right. I add a "-n" and it worked fine. I don't know why there were only about 10 out of 1,500, but I guess there was some kind of race condition. Again, thanks! Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 22:03:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21057 for freebsd-current-outgoing; Sun, 6 Dec 1998 22:03:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from phantasm.thekeep.org (PHANTASM.CC.CMU.EDU [128.2.35.108]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA21051 for ; Sun, 6 Dec 1998 22:03:29 -0800 (PST) (envelope-from dar@thekeep.org) Received: (qmail 77885 invoked by uid 100); 7 Dec 1998 06:03:26 -0000 Message-ID: <19981207010325.A39345@thekeep.org> Date: Mon, 7 Dec 1998 01:03:25 -0500 From: Dan Root To: current@FreeBSD.ORG Subject: status of dying daemons bug? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been watching the mailing list fairly closely for the past month or so, but don't remember seeing a definitive solution to the dying daemon problem. I'm still having the problem here, with -current sources built yesterday. I'm not quite sure why I'm ever hitting swap, given the machine's load (almost never more than 80 or 100 megs of active memory on a P6-SMP machine with 256), but the instant I do, I begin seeing the problem. It's nearly 100% reliable, even if only a few hundred kilobytes are swapped out. Right now I'm doing 'sysctl -w vm.disable_swapspace_pageouts=1' just to keep the machine up and running, but this is hardly a good long term solution. Unfortunately I lack the familiarity with the VM internals to go hunting after this myself. However, I would be more than willing to assist someone in finding the problem, including giving people access to my machine so they can poke around. I'd also be happy to post kernel config files, output from vmstat and friends, or anything else that might help. -DaR -- Dan Root - dar@thekeep.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 22:08:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21491 for freebsd-current-outgoing; Sun, 6 Dec 1998 22:08:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA21486 for ; Sun, 6 Dec 1998 22:08:02 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zmtpn-0002WR-00; Sun, 6 Dec 1998 23:07:51 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id XAA00683; Sun, 6 Dec 1998 23:06:23 -0700 (MST) Message-Id: <199812070606.XAA00683@harmony.village.org> To: Mark Evans Subject: Re: Tk/Tcl Programs Freeze X Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 06 Dec 1998 23:01:33 CST." References: Date: Sun, 06 Dec 1998 23:06:23 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Mark Evans writes: : I've started having a problem in the past week on two CURRENT systems : where any Tk/Tcl based program will freeze X when they exit. The system : is not frozen, just X. I've seen something similar. It would appear that either the window manager or the tk program is grabbing the cursor. When I kill both and restart the window manager that I'm using, the system is usable again. I'm running 3.3.2 (elf) with -current from Dec 4, qvwm and wish 4.2. However my late dec 5 kernel doesn't exhibit this behavior. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 22:28:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22802 for freebsd-current-outgoing; Sun, 6 Dec 1998 22:28:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22797 for ; Sun, 6 Dec 1998 22:28:26 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id WAA26292; Sun, 6 Dec 1998 22:28:10 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Sun, 6 Dec 1998 22:28:09 -0800 (PST) From: Doug White To: "Matthew N. Dodd" cc: Mike Smith , current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Dec 1998, Matthew N. Dodd wrote: > How critical to the boot process are network cards? Very, if you're netbooting. 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 Sun Dec 6 22:34:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA23238 for freebsd-current-outgoing; Sun, 6 Dec 1998 22:34:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA23233 for ; Sun, 6 Dec 1998 22:34:05 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id WAA79671; Sun, 6 Dec 1998 22:33:37 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812070633.WAA79671@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Evans cc: current@FreeBSD.ORG Subject: Re: Tk/Tcl Programs Freeze X In-reply-to: Your message of "Sun, 06 Dec 1998 23:01:33 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Dec 1998 22:33:37 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Try recompiling tcl and tk . When I first switched to -elf I had similar problem till I recompile tcl and tk . I use exmh (tcl/tk) as my mail reader.... Cheers, Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 6 23:00:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25044 for freebsd-current-outgoing; Sun, 6 Dec 1998 23:00:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from darkstar.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25038 for ; Sun, 6 Dec 1998 23:00:56 -0800 (PST) (envelope-from tom@darkstar.tomqnx.com) Received: (from root@localhost) by darkstar.tomqnx.com (8.9.1/8.9.1) id CAA12369 for current@freebsd.org; Mon, 7 Dec 1998 02:00:52 -0500 (EST) (envelope-from tom) Date: Mon, 7 Dec 1998 02:00:52 -0500 (EST) From: Tom Torrance Message-Id: <199812070700.CAA12369@darkstar.tomqnx.com> To: current@FreeBSD.ORG Subject: Abort trap on make world Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am totally mystified by this problem. Can anyone help me out? -------------------------------------------------------------- >>> elf make world started on Mon Dec 7 01:16:26 EST 1998 -------------------------------------------------------------- [Stuff Deleted] cc -static -O2 -pipe -Wall -I/usr/src/lib/libmytinfo -I/usr/obj/elf/usr/src/tmp/usr/include -o mkcapsort /usr/src/lib/libmytinfo/mkcapsort.c cross-caplist.o cross-compar.o ./mkcapsort > capsort.c cc -O2 -pipe -Wall -I/usr/src/lib/libmytinfo -I/usr/obj/elf/usr/src/tmp/usr/include -c -o cross-capsort.o capsort.c cc -O2 -pipe -Wall -I/usr/src/lib/libmytinfo -I/usr/obj/elf/usr/src/tmp/usr/include -c -o cross-findcap.o /usr/src/lib/libmytinfo/findcap.c cc -static -O2 -pipe -Wall -I/usr/src/lib/libmytinfo -I/usr/obj/elf/usr/src/tmp/usr/include -o mkbinorder /usr/src/lib/libmytinfo/mkbinorder.c cross-capsort.o cross-caplist.o cross-compar.o cross-findcap.o cc -static -O2 -pipe -Wall -I/usr/src/lib/libmytinfo -I/usr/obj/elf/usr/src/tmp/usr/include -o mkversion /usr/src/lib/libmytinfo/mkversion.c cd /usr/src/sys/modules/linux; /usr/obj/elf/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -D_BUILD_TOOLS build-tools Abort trap *** Error code 134 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** 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 Mon Dec 7 00:20:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02291 for freebsd-current-outgoing; Mon, 7 Dec 1998 00:20:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au ([203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02220 for ; Mon, 7 Dec 1998 00:19:58 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA23919; Mon, 7 Dec 1998 19:19:53 +1100 Date: Mon, 7 Dec 1998 19:19:53 +1100 From: Bruce Evans Message-Id: <199812070819.TAA23919@godzilla.zeta.org.au> To: current@FreeBSD.ORG, tom@tomqnx.com Subject: Re: Abort trap on make world Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >cd /usr/src/sys/modules/linux; /usr/obj/elf/usr/src/tmp/usr/bin/make -DNOINFO -DNOMAN -DNOPIC -DNOPROFILE -DNOSHARED -D_BUILD_TOOLS build-tools >Abort trap >*** Error code 134 > >Stop. This message usually means that the elf interpreter was not found. The associated message "ELF interpreter /usr/libexec/ld-elf.so.1 not found" is printed to /dev/tty, so it doesn't appear in redirected output. The kernel can't return to the user process in the usual way, so it exits directly, as if the process had been killed by a SIGABRT. The direct exit breaks ktrace. This error shouldn't happen for building worlds. All binaries used for building worlds are supposed to be built static to avoid it and other bootstrapping problems with shared libraries. This error does happen for building perl, but the perl build is so broken that the error is ignored. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 00:23:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02644 for freebsd-current-outgoing; Mon, 7 Dec 1998 00:23:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-42-dbn.dial-up.net [196.34.155.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02632 for ; Mon, 7 Dec 1998 00:22:57 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id KAA23496; Mon, 7 Dec 1998 10:22:17 +0200 (SAT) From: Robert Nordier Message-Id: <199812070822.KAA23496@ceia.nordier.com> Subject: Re: Booting 3.0-RELEASE in a non-standard setup In-Reply-To: <002901be219f$21d16400$6cb611cb@saruman.scitec.com.au> from John Saunders at "Dec 7, 98 04:04:56 pm" To: john.saunders@scitec.com.au (John Saunders) Date: Mon, 7 Dec 1998 10:22:13 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 John Saunders wrote: > FYI (Information obtained from this weekends hacking) Thanks for reporting back on this. > > It is possible to have FreeBSD 2.2.x and 3.x co-existing on > the same disk in different partitions. What makes this possible > is the new boot blocks by Robert Nordier. You also need to make > certain that the 2.2.x partition comes first in the partition > table (although I don't think it need come first on the disk). However, upgrading your 2.2.x boot blocks to new ones from -current should allow 2.2.x to occupy any slice (PC partition) as well. [ Useful stuff elided ] > The new boot blocks load the /boot.config file which > specifies the information needed to load the kernel from > the correct slice and mount the correct root filesystem. > It appears to be impossible to specify this information in > any way other than editing the file from another running > system. The old boot blocks allowed you to enter this > from the command line. We probably need a ctrl sequence > to escape into a command line for this. > > If you press any key the /boot/loader file will be started I'm a bit puzzled that you experienced this. Though I gather you're using the 3.0R new boot stuff, rather than the -current versions, and there have been a number of changes in the last 7 weeks or so. After the new boot blocks load, you should see one of the characters - \ | / displayed, while everything stops for 3 seconds. If you hit a key other than [enter] at this stage, you should get to the boot: prompt. (Though best hit a key that generates an ASCII char, if you're using older code.) > and it won't work properly in the case where the BIOS > drive number doesn't match the wd drive number. So never > press a key, let the boot block load the kernel directly. -- 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 Dec 7 02:01:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09749 for freebsd-current-outgoing; Mon, 7 Dec 1998 02:01:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09744 for ; Mon, 7 Dec 1998 02:01:47 -0800 (PST) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id UAA06728; Mon, 7 Dec 1998 20:01:41 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma006726; Mon, 7 Dec 98 20:01:36 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id UAA27965 for ; Mon, 7 Dec 1998 20:01:36 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id UAA08547 for ; Mon, 7 Dec 1998 20:01:35 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id UAA09667; Mon, 7 Dec 1998 20:01:34 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199812071001.UAA09667@nymph.dtir.qld.gov.au> To: freebsd-current@FreeBSD.ORG cc: syssgm@dtir.qld.gov.au Subject: strings - elf vs aout Date: Mon, 07 Dec 1998 20:01:33 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There's an annoying anomaly in the new version of strings. The traditional version specifically included tabs as valid characters for strings, while the new one doesn't, leading to: $ printf 'My dog has\tno nose' > foo $ strings -aout foo My dog has no nose $ strings -elf foo My dog has no nose $ I run "strings" on lots of files (eg frobnoz.doc), not just executables. This is irritating me specifically in regard to the INCLUDE_CONFIG_FILE kernel compile option which now requires "strings -aout" to recover the config file. Shall I devise and commit a fix for this behaviour? Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 04:24:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA23033 for freebsd-current-outgoing; Mon, 7 Dec 1998 04:24:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from minnie.comp.cs.gunma-u.ac.jp (minnie.comp.cs.gunma-u.ac.jp [133.8.10.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA23028 for ; Mon, 7 Dec 1998 04:24:49 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (hercules.comp.cs.gunma-u.ac.jp [133.8.10.23]) by minnie.comp.cs.gunma-u.ac.jp (8.8.8+2.7Wbeta7/3.6W03/23/98) with ESMTP id VAA22606 for ; Mon, 7 Dec 1998 21:21:55 +0900 (JST) Message-ID: <366BC9CD.304D2049@newsguy.com> Date: Mon, 07 Dec 1998 21:27:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win95; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: FICL Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just learned about the addition of FICL to FreeBSD, I decided to resubscribe (for a while, at least) to -current just to discuss this. I should have expected: I had to distance myself from both FreeBSD and Forth for a while and look what happens! :-) Ok, my two cents, though I still haven't read all the archive: > On Sat, 31 Oct 1998, Mike Smith wrote: > > I stripped LOCALS, multithreading, stack checking, but added KEY... Well, > this is still around 20k. > > > whether there's much we can strip from the core wordset; I'll leave > > that for the FORTH guruen to argue over. At 22k (plus whatever it > > As I said above, we probably can strip CORE-EXT and SEARCH - I wouldn't > touch the CORE itself, however. I have yet to check out how the source is being handled, but I here is my possibly irrelevant comments. I'll strive to get up to date before adding any more cents to the vending machine, though... :-) CORE can be stripped. There is a lot of words in ANS' CORE that are reduntant. Here, CORE represents more legacy than anything else. But I'd like this system to remain ANS in it's FreeBSD distribution. What is necessary for that is that *the source code for the words remain available*. I don't recall the specifics, but I think this refers to source code for the running system, instead of C source before generating FICL. In other words, you can remove, for instance, OVER from the base system, as long as you provide ": OVER SWAP DUP ROT ;" somewhere as source code reference for it. I'd have to check out the source, but it might well be possible (and easy) to create a word which would print the minimum required vocabulary, if such a beast one would be wanted. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com You can't modify a constant, float upstream, win an argument with the IRS, or satisfy this compiler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 05:21:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27358 for freebsd-current-outgoing; Mon, 7 Dec 1998 05:21:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27341; Mon, 7 Dec 1998 05:21:55 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id IAA67160; Mon, 7 Dec 1998 08:21:52 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: current@FreeBSD.ORG cc: alpha@FreeBSD.ORG From: "Gary Palmer" Subject: Make World failure Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Dec 1998 08:21:51 -0500 Message-ID: <67156.913036911@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From a -current supped form freefall ~6am EST this morning, and being build on an Alpha: building standard gcc library ranlib libgcc.a install -C -c -o root -g wheel -m 444 libgcc.a /usr/obj/elf/usr/src/tmp/usr/l ib install -C -c -o root -g wheel -m 444 libgcc_pic.a /usr/obj/elf/usr/src/tmp/usr/lib cd /usr/src/gnu/usr.bin/perl/libperl; /usr/obj/elf/usr/src/tmp/usr/bin/make all; /usr/obj/elf/usr/src/tmp/usr/bin/make -B install ln -sf /usr/src/gnu/usr.bin/perl/libperl/config.SH-elf.alpha config.sh ln -sf /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/config_h.SH config_h.sh sh config_h.sh Extracting config.h (with variable substitutions) sed: 1: "s!^#un-def!#undef!": bad flag in substitute command: 's' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error That looks ... bad :) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 06:10:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01393 for freebsd-current-outgoing; Mon, 7 Dec 1998 06:10:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from highwind.com (hurricane.highwind.com [209.61.45.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01388 for ; Mon, 7 Dec 1998 06:10:40 -0800 (PST) (envelope-from info@highwind.com) Received: (from info@localhost) by highwind.com (8.8.6/8.8.6) id JAA17159; Mon, 7 Dec 1998 09:10:34 -0500 (EST) Date: Mon, 7 Dec 1998 09:10:34 -0500 (EST) Message-Id: <199812071410.JAA17159@highwind.com> From: HighWind Software Information To: current@FreeBSD.ORG Subject: Re: Thread fd locking and fork() Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Terry, First, since this is POSIX thread fork() semantics, you don't get a copy of all threads when you fork(). You just get the thread that called fork(). At least, that is the way it should work and appears to work. Second, I don't see why it is bad for a threaded program to call fork(). Why not? What if you need to exec() sendmail or some other helper program? Third, I still don't see why my patch is bad. After fork(), you have one thread left. It makes no sense for the remaining fd's that are open to be locked by threads that do not exist! If they are simply unlocked/cleaned up in the child, the child is then free to close() or manipulate those fd's. This is the way it works on every other O/S. You can always: fork(), then in the child, loop over fd's to close() the one's you want to close(), then exec() a program. -Rob -- Insert in uthread_fork.c at line 122: /* * Enter a loop to remove all locks on all locked fd's */ for (i = 0; i < _thread_dtablesize; i++) { if (_thread_fd_table[i] != NULL) { memset(&_thread_fd_table[i]->lock, 0, sizeof(_thread_fd_table[i]->lock)); _thread_fd_table[i]->r_owner = NULL; _thread_fd_table[i]->w_owner = NULL; _thread_fd_table[i]->r_fname = NULL; _thread_fd_table[i]->w_fname = NULL; _thread_fd_table[i]->r_lineno = 0;; _thread_fd_table[i]->w_lineno = 0;; _thread_fd_table[i]->r_lockcount = 0; _thread_fd_table[i]->w_lockcount = 0; /* Initialise the read/write queues: */ _thread_queue_init(&_thread_fd_table[i]->r_queu\ e); _thread_queue_init(&_thread_fd_table[i]->w_queu\ e); } } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 06:41:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03599 for freebsd-current-outgoing; Mon, 7 Dec 1998 06:41:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mars.ecsnet.com (mars.ecsnet.com [204.57.81.130]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id GAA03591 for ; Mon, 7 Dec 1998 06:41:21 -0800 (PST) (envelope-from mevans@ecsnet.com) Received: (qmail 18506 invoked from network); 7 Dec 1998 14:40:50 -0000 Received: from alpha.ecsnet.com (204.57.81.131) by mars.ecsnet.com with SMTP; 7 Dec 1998 14:40:50 -0000 Date: Mon, 7 Dec 1998 08:43:41 -0600 (CST) From: "Mark R. Evans" To: Warner Losh cc: current@FreeBSD.ORG Subject: Re: Tk/Tcl Programs Freeze X In-Reply-To: <199812070606.XAA00683@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is the exact behavior that I'm seeing, both with wish 4.2 and wish8.0. I've tried recompiling all the tk/tcl ports, updated the system as of 12-7, still have the lockups. I re-cvsup'ed using a Nov 15 date, rebuilt the kernel and now everything works as it should. I guess I'll try to find the commit between 11-15 and now that is causing my problems. Thanks for the advice. On Sun, 6 Dec 1998, Warner Losh wrote: > In message Mark Evans writes: > : I've started having a problem in the past week on two CURRENT systems > : where any Tk/Tcl based program will freeze X when they exit. The system > : is not frozen, just X. > > I've seen something similar. It would appear that either the window > manager or the tk program is grabbing the cursor. When I kill both > and restart the window manager that I'm using, the system is usable > again. > > I'm running 3.3.2 (elf) with -current from Dec 4, qvwm and wish 4.2. > However my late dec 5 kernel doesn't exhibit this behavior. > > Warner > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 06:52:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04554 for freebsd-current-outgoing; Mon, 7 Dec 1998 06:52:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-50-dbn.dial-up.net [196.34.155.50]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04508 for ; Mon, 7 Dec 1998 06:52:04 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id QAA26709; Mon, 7 Dec 1998 16:50:38 +0200 (SAT) From: Robert Nordier Message-Id: <199812071450.QAA26709@ceia.nordier.com> Subject: Re: strings - elf vs aout In-Reply-To: <199812071001.UAA09667@nymph.dtir.qld.gov.au> from Stephen McKay at "Dec 7, 98 08:01:33 pm" To: syssgm@dtir.qld.gov.au (Stephen McKay) Date: Mon, 7 Dec 1998 16:50:32 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au X-Mailer: ELM [version 2.4ME+ PL31 (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 Stephen McKay wrote: > There's an annoying anomaly in the new version of strings. The traditional > version specifically included tabs as valid characters for strings, while > the new one doesn't, leading to: > > $ printf 'My dog has\tno nose' > foo > $ strings -aout foo > My dog has no nose > $ strings -elf foo > My dog has > no nose > $ > > I run "strings" on lots of files (eg frobnoz.doc), not just executables. > This is irritating me specifically in regard to the INCLUDE_CONFIG_FILE > kernel compile option which now requires "strings -aout" to recover the > config file. > > Shall I devise and commit a fix for this behaviour? If you want to do this, I'd suggest making it an option. Current standards, such as the Single UNIX Specification, apparently regard a printable string as 4 or more isprint(3) chars followed by '\n' or '\0'. -- 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 Dec 7 08:15:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13576 for freebsd-current-outgoing; Mon, 7 Dec 1998 08:15:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13569 for ; Mon, 7 Dec 1998 08:15:05 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA14285; Mon, 7 Dec 1998 11:14:49 -0500 (EST) Date: Mon, 7 Dec 1998 11:14:49 -0500 (EST) From: "Matthew N. Dodd" To: Doug White cc: Mike Smith , current@FreeBSD.ORG Subject: Re: KLD - what's the idea? 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, 6 Dec 1998, Doug White wrote: > On Mon, 7 Dec 1998, Matthew N. Dodd wrote: > > > How critical to the boot process are network cards? > > Very, if you're netbooting. If the cost to implement a solution to loading firmware code from the kernel is too high for the returns (ie: what devices are likely to require firmware code loads) then it may be sufficient to say that "Booting from some token ring cards (TMS380, SMC TokenElite) and ATM cards (FORE) is not supported." Regardless, I am still looking for any solution that would let me demand load files from the kernel depending on the devices present. For example, my textbox, having gods own assload of cards in it right now would have something like: /boot/tez.conf: MADGE_SMART_RINGNODE /boot/fw/madge.dnld PROTEON_P1990 /boot/fw/proteon.dnld PROTEON_P1392 /boot/fw/proteon.dnld COMPAQ_NETFLEX_TR /boot/fw/compaq_tr.dnld COMPAQ_NETFLEX_ENET /boot/fw/compaq_enet.dnld When the driver detectects a card that needs to be feed some firmware it reads '/boot/tez.conf', loads the file, dumps the code to the card, and unloads the file. In this case (the TMS380 family of devices) if the adapter is RAM based (no firmware onboard) the card is pretty much useless for doing anything until the code is loaded. Even reading the MAC address requires firmware. (Well, the real MAC address, not the BIA (Burned In Address) which may or may not be used as the MAC address.) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 08:41:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16553 for freebsd-current-outgoing; Mon, 7 Dec 1998 08:41:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.intercom.com ([207.51.55.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16544 for ; Mon, 7 Dec 1998 08:41:37 -0800 (PST) (envelope-from jason@intercom.com) Received: from intercom.com (shagalicious.com [206.98.165.250]) by mail.intercom.com (8.9.0/8.9.0) with ESMTP id LAA13557 for ; Mon, 7 Dec 1998 11:41:29 -0500 (EST) Message-ID: <366C04D2.2ACA7F8C@intercom.com> Date: Mon, 07 Dec 1998 11:39:46 -0500 From: "Jason J. Horton" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: New drivers and install floppy space References: <199812070148.CAA13594@ocean.campus.luth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How does Microsoft boot the full NT install(3 floppies) from CD? Can't we do simular? -J "throwing out ideas, expecting no responces" Mikael Karpberg wrote: > According to Mike Smith: > > > > When a majority can no longer be thusly accommodated, we'll just shrug > > > > and ditch it completely in favor of the 2(*)-floppy solution. > > > > > > It is not that bad. I'm doing more and more boot off the CDROM installs. > > > I assume sysinstall + boot kernel can be quite large there. > > > Is the boot kernel there a full GENERIC kernel? > > > > No. The way that bootable CDROMs work is that the BIOS pretends that a > > 1.44MB region at the beginning of the CDROM is actually a 1.44MB floppy > > disk. > > > > I wouldn't mind finding the asshole responsible for this fiasco and > > doing something traumatic to their lower digestive tract with a > > petrol-powered Weed Eater. > > > > The only ways out of this are: > > > > - mandate a floppy in addition to the CDROM (sucks) > > - add CDROM drivers to the bootloader (ATAPI, SCSI for Adaptec and NCR > > at least) > > > > Both of these are painful. > > Less so than the Weed Eater, is my guess. :-) > > But... we have 1.44 MB on the CD... Since the bios manages to read the > file, wouldn't there be a generic way that we could also read something > from the CD? So that we could make a floppy which does a call and reads a > 5 MB image from the CD, and unpacks the kernel with MFS from that, with > full drivers and a nice splash image, too. :-) > But, lemme guess: "Sorry... There's no way to fool the BIO to read the CD" ? > > /Mikael > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 08:46:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17139 for freebsd-current-outgoing; Mon, 7 Dec 1998 08:46:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galois.boolean.net (galois.boolean.net [209.133.111.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17130 for ; Mon, 7 Dec 1998 08:46:25 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (galois.boolean.net [209.133.111.74]) by galois.boolean.net (8.8.8/8.8.8) with SMTP id RAA24574; Mon, 7 Dec 1998 17:00:15 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19981207085116.00948a90@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Mon, 07 Dec 1998 08:51:16 -0800 To: HighWind Software Information From: "Kurt D. Zeilenga" Subject: Re: Thread fd locking and fork() Cc: current@FreeBSD.ORG In-Reply-To: <199812071410.JAA17159@highwind.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:10 AM 12/7/98 -0500, HighWind Software Information wrote: >Second, I don't see why it is bad for a threaded program to call >fork(). Why not? Because you have no guarantee that all thread related resources have been properly freed using atfork() handlers. Since FreeBSD doesn't support atfork handlers, you'll actually likely to have lots of thread related resources dangling. Any one of these can bite you. Doing anything other than exec()/_exit() in the child, including close(), is likely to cause deadlock. If you want to write a portable pthread application, do not use fork() after using any pthread_*() calls. >What if you need to exec() sendmail or some other helper program? Do it immediately or use a surrogate parent! >Third, I still don't see why my patch is bad. After fork(), you have >one thread left. It makes no sense for the remaining fd's that are >open to be locked by threads that do not exist! Because I may want to use an atfork handler (once pthread_atfork() is implemented) to restart threads on the child. >If they are simply unlocked/cleaned up in the child, the child is then >free to close() or manipulate those fd's. 1) because it changes the process state of the child. 2) assumes that every application wants them unlocked. >This is the way it works on every other O/S. Becareful with absolutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 08:47:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17210 for freebsd-current-outgoing; Mon, 7 Dec 1998 08:47:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oitunix.oit.umass.edu (nscs23p10.remote.umass.edu [128.119.179.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17198 for ; Mon, 7 Dec 1998 08:46:59 -0800 (PST) (envelope-from gp@oitunix.oit.umass.edu) Received: (from gp@localhost) by oitunix.oit.umass.edu (8.9.1/8.9.1) id LAA95152; Mon, 7 Dec 1998 11:46:58 -0500 (EST) (envelope-from gp) Message-ID: <19981207114657.A95139@oit.umass.edu> Date: Mon, 7 Dec 1998 11:46:57 -0500 From: Greg Pavelcak To: "Mark R. Evans" Cc: current@FreeBSD.ORG Subject: Re: Tk/Tcl Programs Freeze X References: <199812070606.XAA00683@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Mark R. Evans on Mon, Dec 07, 1998 at 08:43:41AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 07, 1998 at 08:43:41AM -0600, Mark R. Evans wrote: > This is the exact behavior that I'm seeing, both with wish 4.2 and > wish8.0. I've tried recompiling all the tk/tcl ports, updated the system > as of 12-7, still have the lockups. I re-cvsup'ed using a Nov 15 date, > rebuilt the kernel and now everything works as it should. I guess I'll > try to find the commit between 11-15 and now that is causing my problems. > Thanks for the advice. > Just to narrow it down, I experienced the same problem with sources from 11/21, I think. Certainly before Thanksgiving. I'd be happy to hear about anything you come up with. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 09:29:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21749 for freebsd-current-outgoing; Mon, 7 Dec 1998 09:29:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21744 for ; Mon, 7 Dec 1998 09:29:04 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA10589; Mon, 7 Dec 1998 10:28:42 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA02857; Mon, 7 Dec 1998 10:28:41 -0700 Date: Mon, 7 Dec 1998 10:28:41 -0700 Message-Id: <199812071728.KAA02857@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Robert Nordier Cc: syssgm@dtir.qld.gov.au (Stephen McKay), freebsd-current@FreeBSD.ORG Subject: Re: strings - elf vs aout In-Reply-To: <199812071450.QAA26709@ceia.nordier.com> References: <199812071001.UAA09667@nymph.dtir.qld.gov.au> <199812071450.QAA26709@ceia.nordier.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > There's an annoying anomaly in the new version of strings. The traditional > > version specifically included tabs as valid characters for strings, while > > the new one doesn't, leading to: > > > > $ printf 'My dog has\tno nose' > foo > > $ strings -aout foo > > My dog has no nose > > $ strings -elf foo > > My dog has > > no nose > > $ > > > > I run "strings" on lots of files (eg frobnoz.doc), not just executables. > > This is irritating me specifically in regard to the INCLUDE_CONFIG_FILE > > kernel compile option which now requires "strings -aout" to recover the > > config file. > > > > Shall I devise and commit a fix for this behaviour? > > If you want to do this, I'd suggest making it an option. Current > standards, such as the Single UNIX Specification, apparently regard a > printable string as 4 or more isprint(3) chars followed by '\n' or > '\0'. Then 'strings' for ELF is broken, since \t is not a newline of end of a string, and Steven's comments are valid. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 11:52:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06472 for freebsd-current-outgoing; Mon, 7 Dec 1998 11:52:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from uni-sb.de (uni-sb.de [134.96.252.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06462 for ; Mon, 7 Dec 1998 11:52:06 -0800 (PST) (envelope-from rock@cs.uni-sb.de) Received: from cs.uni-sb.de (cs.uni-sb.de [134.96.252.31]) by uni-sb.de (8.9.0/1998120100) with ESMTP id UAA02788 for ; Mon, 7 Dec 1998 20:52:00 +0100 (CET) Received: from cs.uni-sb.de (acc2-142.telip.uni-sb.de [134.96.112.142]) by cs.uni-sb.de (8.9.0/1998120100) with ESMTP id UAA15344 for ; Mon, 7 Dec 1998 20:51:57 +0100 (CET) Message-ID: <366C3276.E337E0F@cs.uni-sb.de> Date: Mon, 07 Dec 1998 20:54:30 +0100 From: "D. Rock" X-Mailer: Mozilla 4.5 [de] (Win98; U) X-Accept-Language: de MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Weird NFS error using Solaris 7 server References: <199811232022.VAA00480@trantor.stuyts.nl> Content-Type: multipart/mixed; boundary="------------385830322A8CC3FBC2C05EC3" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dies ist eine mehrteilige Nachricht im MIME-Format. --------------385830322A8CC3FBC2C05EC3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Paul van der Zwan schrieb: > > When I try to create a file on a FS mounted from my Sparc 5 running Solaris 7 > I get the following error: > [21:14:42 trantor:paulz:/mnt/var/tmp] > $ touch a > touch: a: Inappropriate file type or format I can confirm this error. The solution is (again) using NFSv2 mounts. Is this problem currently under investigation? It happens at least with kernels cvsup'd up to today. Below is the output of "snoop -v port 2049" on the Solaris box (The output of snoop seems much more readable by human). One output is the (succeding) call using v2 mounts, the other the (failing) using v3 mounts. Daniel --------------385830322A8CC3FBC2C05EC3 Content-Type: text/plain; charset=us-ascii; name="snoop.nfsv3" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="snoop.nfsv3" ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 1 arrived at 20:40:21.43 ETHER: Packet size = 174 bytes ETHER: Destination = 0:a0:c9:9f:30:1, ETHER: Source = 0:a0:c9:9f:49:34, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 160 bytes IP: Identification = 34637 IP: Flags = 0x0 IP: .0.. .... = may fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 64 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = b070 IP: Source address = 192.168.0.254 IP: Destination address = 192.168.0.1 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 1022 UDP: Destination port = 2049 (Sun RPC) UDP: Length = 140 UDP: Checksum = AEA9 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155955 RPC: Type = 0 (Call) RPC: RPC version = 2 RPC: Program = 100003 (NFS), version = 3, procedure = 3 RPC: Credentials: Flavor = 1 (Unix), len = 48 bytes RPC: Time = 0 RPC: Hostname = RPC: Uid = 0, Gid = 0 RPC: Groups = 0 2 3 4 5 20 31 RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 3 (Look up file name) NFS: File handle = [B800] NFS: 4600FC00020000000A000000CE600000CE0069250A000000CE600000CE006925 NFS: File name = bla NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 2 arrived at 20:40:21.43 ETHER: Packet size = 158 bytes ETHER: Destination = 0:a0:c9:9f:49:34, ETHER: Source = 0:a0:c9:9f:30:1, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 144 bytes IP: Identification = 26697 IP: Flags = 0x4 IP: .1.. .... = do not fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 255 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = c390 IP: Source address = 192.168.0.1 IP: Destination address = 192.168.0.254 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 2049 UDP: Destination port = 1022 (Sun RPC) UDP: Length = 124 UDP: Checksum = AF52 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155955 RPC: Type = 1 (Reply) RPC: This is a reply to frame 1 RPC: Status = 0 (Accepted) RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: Accept status = 0 (Success) RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 3 (Look up file name) NFS: Status = 2 (No such file or directory) NFS: Post-operation attributes: (directory) NFS: File type = 2 (Directory) NFS: Mode = 0755 NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rwx NFS: Group's permissions = r-x NFS: Other's permissions = r-x NFS: Link count = 2, User ID = 0, Group ID = 1 NFS: File size = 512, Used = 1024 NFS: Special: Major = 0, Minor = 0 NFS: File system id = 16515142, File id = 24782 NFS: Last access time = 07-Dec-98 19:37:51.535634000 GMT NFS: Modification time = 07-Dec-98 19:27:17.665634000 GMT NFS: Attribute change time = 07-Dec-98 19:27:17.665634000 GMT NFS: NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 3 arrived at 20:40:21.43 ETHER: Packet size = 174 bytes ETHER: Destination = 0:a0:c9:9f:30:1, ETHER: Source = 0:a0:c9:9f:49:34, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 160 bytes IP: Identification = 34638 IP: Flags = 0x0 IP: .0.. .... = may fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 64 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = af70 IP: Source address = 192.168.0.254 IP: Destination address = 192.168.0.1 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 1022 UDP: Destination port = 2049 (Sun RPC) UDP: Length = 140 UDP: Checksum = AEA8 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155956 RPC: Type = 0 (Call) RPC: RPC version = 2 RPC: Program = 100003 (NFS), version = 3, procedure = 3 RPC: Credentials: Flavor = 1 (Unix), len = 48 bytes RPC: Time = 0 RPC: Hostname = RPC: Uid = 0, Gid = 0 RPC: Groups = 0 2 3 4 5 20 31 RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 3 (Look up file name) NFS: File handle = [B800] NFS: 4600FC00020000000A000000CE600000CE0069250A000000CE600000CE006925 NFS: File name = bla NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 4 arrived at 20:40:21.43 ETHER: Packet size = 158 bytes ETHER: Destination = 0:a0:c9:9f:49:34, ETHER: Source = 0:a0:c9:9f:30:1, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 144 bytes IP: Identification = 26698 IP: Flags = 0x4 IP: .1.. .... = do not fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 255 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = c290 IP: Source address = 192.168.0.1 IP: Destination address = 192.168.0.254 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 2049 UDP: Destination port = 1022 (Sun RPC) UDP: Length = 124 UDP: Checksum = AF51 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155956 RPC: Type = 1 (Reply) RPC: This is a reply to frame 3 RPC: Status = 0 (Accepted) RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: Accept status = 0 (Success) RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 3 (Look up file name) NFS: Status = 2 (No such file or directory) NFS: Post-operation attributes: (directory) NFS: File type = 2 (Directory) NFS: Mode = 0755 NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rwx NFS: Group's permissions = r-x NFS: Other's permissions = r-x NFS: Link count = 2, User ID = 0, Group ID = 1 NFS: File size = 512, Used = 1024 NFS: Special: Major = 0, Minor = 0 NFS: File system id = 16515142, File id = 24782 NFS: Last access time = 07-Dec-98 19:37:51.535634000 GMT NFS: Modification time = 07-Dec-98 19:27:17.665634000 GMT NFS: Attribute change time = 07-Dec-98 19:27:17.665634000 GMT NFS: NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 5 arrived at 20:40:21.43 ETHER: Packet size = 222 bytes ETHER: Destination = 0:a0:c9:9f:30:1, ETHER: Source = 0:a0:c9:9f:49:34, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 208 bytes IP: Identification = 34639 IP: Flags = 0x0 IP: .0.. .... = may fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 64 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = 7e70 IP: Source address = 192.168.0.254 IP: Destination address = 192.168.0.1 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 1022 UDP: Destination port = 2049 (Sun RPC) UDP: Length = 188 UDP: Checksum = AC99 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155957 RPC: Type = 0 (Call) RPC: RPC version = 2 RPC: Program = 100003 (NFS), version = 3, procedure = 8 RPC: Credentials: Flavor = 1 (Unix), len = 48 bytes RPC: Time = 0 RPC: Hostname = RPC: Uid = 0, Gid = 0 RPC: Groups = 0 2 3 4 5 20 31 RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 8 (Create file) NFS: File handle = [B800] NFS: 4600FC00020000000A000000CE600000CE0069250A000000CE600000CE006925 NFS: File name = bla NFS: Method = Unchecked NFS: Mode = 0644 NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rw- NFS: Group's permissions = r-- NFS: Other's permissions = r-- NFS: User ID = (not set) NFS: Group ID = (not set) NFS: Size = (not set) NFS: Access time = -1 (set to client time) NFS: Modification time = -1 (set to client time) NFS: NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 6 arrived at 20:40:21.43 ETHER: Packet size = 186 bytes ETHER: Destination = 0:a0:c9:9f:49:34, ETHER: Source = 0:a0:c9:9f:30:1, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 172 bytes IP: Identification = 26699 IP: Flags = 0x4 IP: .1.. .... = do not fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 255 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = a590 IP: Source address = 192.168.0.1 IP: Destination address = 192.168.0.254 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 2049 UDP: Destination port = 1022 (Sun RPC) UDP: Length = 152 UDP: Checksum = 0ECE UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155957 RPC: Type = 1 (Reply) RPC: This is a reply to frame 5 RPC: Status = 0 (Accepted) RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: Accept status = 0 (Success) RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 8 (Create file) NFS: Status = 79 ((unknown error)) NFS: Pre-operation attributes: NFS: Size = 512 bytes NFS: Modification time = 07-Dec-98 19:27:17.665634000 GMT NFS: Attribute change time = 07-Dec-98 19:27:17.665634000 GMT NFS: NFS: Post-operation attributes: NFS: File type = 2 (Directory) NFS: Mode = 0755 NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rwx NFS: Group's permissions = r-x NFS: Other's permissions = r-x NFS: Link count = 2, User ID = 0, Group ID = 1 NFS: File size = 512, Used = 1024 NFS: Special: Major = 0, Minor = 0 NFS: File system id = 16515142, File id = 24782 NFS: Last access time = 07-Dec-98 19:37:51.535634000 GMT NFS: Modification time = 07-Dec-98 19:27:17.665634000 GMT NFS: Attribute change time = 07-Dec-98 19:27:17.665634000 GMT NFS: NFS: --------------385830322A8CC3FBC2C05EC3 Content-Type: text/plain; charset=us-ascii; name="snoop.nfsv2" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="snoop.nfsv2" ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 1 arrived at 20:41:14.69 ETHER: Packet size = 170 bytes ETHER: Destination = 0:a0:c9:9f:30:1, ETHER: Source = 0:a0:c9:9f:49:34, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 156 bytes IP: Identification = 34815 IP: Flags = 0x0 IP: .0.. .... = may fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 64 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = 0270 IP: Source address = 192.168.0.254 IP: Destination address = 192.168.0.1 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 1022 UDP: Destination port = 2049 (Sun RPC) UDP: Length = 136 UDP: Checksum = AEBA UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155978 RPC: Type = 0 (Call) RPC: RPC version = 2 RPC: Program = 100003 (NFS), version = 2, procedure = 4 RPC: Credentials: Flavor = 1 (Unix), len = 48 bytes RPC: Time = 0 RPC: Hostname = RPC: Uid = 0, Gid = 0 RPC: Groups = 0 2 3 4 5 20 31 RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 4 (Look up file name) NFS: File handle = [B800] NFS: 4600FC00020000000A000000CE600000CE0069250A000000CE600000CE006925 NFS: File name = bla NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 2 arrived at 20:41:14.69 ETHER: Packet size = 70 bytes ETHER: Destination = 0:a0:c9:9f:49:34, ETHER: Source = 0:a0:c9:9f:30:1, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 56 bytes IP: Identification = 26979 IP: Flags = 0x4 IP: .1.. .... = do not fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 255 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = 0190 IP: Source address = 192.168.0.1 IP: Destination address = 192.168.0.254 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 2049 UDP: Destination port = 1022 (Sun RPC) UDP: Length = 36 UDP: Checksum = 5D24 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155978 RPC: Type = 1 (Reply) RPC: This is a reply to frame 1 RPC: Status = 0 (Accepted) RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: Accept status = 0 (Success) RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 4 (Look up file name) NFS: Status = 2 (No such file or directory) NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 3 arrived at 20:41:14.69 ETHER: Packet size = 170 bytes ETHER: Destination = 0:a0:c9:9f:30:1, ETHER: Source = 0:a0:c9:9f:49:34, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 156 bytes IP: Identification = 34816 IP: Flags = 0x0 IP: .0.. .... = may fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 64 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = 0170 IP: Source address = 192.168.0.254 IP: Destination address = 192.168.0.1 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 1022 UDP: Destination port = 2049 (Sun RPC) UDP: Length = 136 UDP: Checksum = AEB9 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155979 RPC: Type = 0 (Call) RPC: RPC version = 2 RPC: Program = 100003 (NFS), version = 2, procedure = 4 RPC: Credentials: Flavor = 1 (Unix), len = 48 bytes RPC: Time = 0 RPC: Hostname = RPC: Uid = 0, Gid = 0 RPC: Groups = 0 2 3 4 5 20 31 RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 4 (Look up file name) NFS: File handle = [B800] NFS: 4600FC00020000000A000000CE600000CE0069250A000000CE600000CE006925 NFS: File name = bla NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 4 arrived at 20:41:14.69 ETHER: Packet size = 70 bytes ETHER: Destination = 0:a0:c9:9f:49:34, ETHER: Source = 0:a0:c9:9f:30:1, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 56 bytes IP: Identification = 26980 IP: Flags = 0x4 IP: .1.. .... = do not fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 255 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = 0090 IP: Source address = 192.168.0.1 IP: Destination address = 192.168.0.254 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 2049 UDP: Destination port = 1022 (Sun RPC) UDP: Length = 36 UDP: Checksum = 5D23 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155979 RPC: Type = 1 (Reply) RPC: This is a reply to frame 3 RPC: Status = 0 (Accepted) RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: Accept status = 0 (Success) RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 4 (Look up file name) NFS: Status = 2 (No such file or directory) NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 5 arrived at 20:41:14.69 ETHER: Packet size = 162 bytes ETHER: Destination = 0:a0:c9:9f:30:1, ETHER: Source = 0:a0:c9:9f:49:34, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 148 bytes IP: Identification = 34817 IP: Flags = 0x0 IP: .0.. .... = may fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 64 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = 0870 IP: Source address = 192.168.0.254 IP: Destination address = 192.168.0.1 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 1022 UDP: Destination port = 2049 (Sun RPC) UDP: Length = 128 UDP: Checksum = 723B UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155980 RPC: Type = 0 (Call) RPC: RPC version = 2 RPC: Program = 100003 (NFS), version = 2, procedure = 1 RPC: Credentials: Flavor = 1 (Unix), len = 48 bytes RPC: Time = 0 RPC: Hostname = RPC: Uid = 0, Gid = 0 RPC: Groups = 0 2 3 4 5 20 31 RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 1 (Get file attributes) NFS: File handle = [B800] NFS: 4600FC00020000000A000000CE600000CE0069250A000000CE600000CE006925 NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 6 arrived at 20:41:14.69 ETHER: Packet size = 138 bytes ETHER: Destination = 0:a0:c9:9f:49:34, ETHER: Source = 0:a0:c9:9f:30:1, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 124 bytes IP: Identification = 26981 IP: Flags = 0x4 IP: .1.. .... = do not fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 255 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = bb8f IP: Source address = 192.168.0.1 IP: Destination address = 192.168.0.254 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 2049 UDP: Destination port = 1022 (Sun RPC) UDP: Length = 104 UDP: Checksum = 8DFE UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155980 RPC: Type = 1 (Reply) RPC: This is a reply to frame 5 RPC: Status = 0 (Accepted) RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: Accept status = 0 (Success) RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 1 (Get file attributes) NFS: Status = 0 (OK) NFS: File type = 2 (Directory) NFS: Mode = 040755 NFS: Type = Directory NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rwx NFS: Group's permissions = r-x NFS: Other's permissions = r-x NFS: Link count = 2, UID = 0, GID = 1, Rdev = 0x0 NFS: File size = 512, Block size = 8192, No. of blocks = 2 NFS: File system id = 16515142, File id = 24782 NFS: Access time = 07-Dec-98 19:41:04.905635 GMT NFS: Modification time = 07-Dec-98 19:41:07.295634 GMT NFS: Inode change time = 07-Dec-98 19:41:07.295634 GMT NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 7 arrived at 20:41:14.69 ETHER: Packet size = 202 bytes ETHER: Destination = 0:a0:c9:9f:30:1, ETHER: Source = 0:a0:c9:9f:49:34, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 188 bytes IP: Identification = 34818 IP: Flags = 0x0 IP: .0.. .... = may fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 64 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = df6f IP: Source address = 192.168.0.254 IP: Destination address = 192.168.0.1 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 1022 UDP: Destination port = 2049 (Sun RPC) UDP: Length = 168 UDP: Checksum = 2CCE UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155981 RPC: Type = 0 (Call) RPC: RPC version = 2 RPC: Program = 100003 (NFS), version = 2, procedure = 9 RPC: Credentials: Flavor = 1 (Unix), len = 48 bytes RPC: Time = 0 RPC: Hostname = RPC: Uid = 0, Gid = 0 RPC: Groups = 0 2 3 4 5 20 31 RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 9 (Create file) NFS: File handle = [B800] NFS: 4600FC00020000000A000000CE600000CE0069250A000000CE600000CE006925 NFS: File name = bla NFS: Mode = 0100644 NFS: Type = Regular file NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rw- NFS: Group's permissions = r-- NFS: Other's permissions = r-- NFS: UID = -1 NFS: GID = -1 NFS: Size = 0 NFS: Access time = -1 NFS: Modification time = -1 NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 8 arrived at 20:41:14.71 ETHER: Packet size = 170 bytes ETHER: Destination = 0:a0:c9:9f:49:34, ETHER: Source = 0:a0:c9:9f:30:1, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 156 bytes IP: Identification = 26982 IP: Flags = 0x4 IP: .1.. .... = do not fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 255 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = 9a8f IP: Source address = 192.168.0.1 IP: Destination address = 192.168.0.254 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 2049 UDP: Destination port = 1022 (Sun RPC) UDP: Length = 136 UDP: Checksum = 6627 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155981 RPC: Type = 1 (Reply) RPC: This is a reply to frame 7 RPC: Status = 0 (Accepted) RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: Accept status = 0 (Success) RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 9 (Create file) NFS: Status = 0 (OK) NFS: File handle = [2E82] NFS: 4600FC00020000000A000000D260000004FE29590A000000CE600000CE006925 NFS: File type = 1 (Regular File) NFS: Mode = 0100644 NFS: Type = Regular file NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rw- NFS: Group's permissions = r-- NFS: Other's permissions = r-- NFS: Link count = 1, UID = 0, GID = 0, Rdev = 0x0 NFS: File size = 0, Block size = 8192, No. of blocks = 0 NFS: File system id = 16515142, File id = 24786 NFS: Access time = 07-Dec-98 19:41:14.685634 GMT NFS: Modification time = 07-Dec-98 19:41:14.685634 GMT NFS: Inode change time = 07-Dec-98 19:41:14.685634 GMT NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 9 arrived at 20:41:14.71 ETHER: Packet size = 162 bytes ETHER: Destination = 0:a0:c9:9f:30:1, ETHER: Source = 0:a0:c9:9f:49:34, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 148 bytes IP: Identification = 34820 IP: Flags = 0x0 IP: .0.. .... = may fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 64 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = 0570 IP: Source address = 192.168.0.254 IP: Destination address = 192.168.0.1 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 1022 UDP: Destination port = 2049 (Sun RPC) UDP: Length = 128 UDP: Checksum = 7708 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155982 RPC: Type = 0 (Call) RPC: RPC version = 2 RPC: Program = 100003 (NFS), version = 2, procedure = 1 RPC: Credentials: Flavor = 1 (Unix), len = 48 bytes RPC: Time = 0 RPC: Hostname = RPC: Uid = 0, Gid = 0 RPC: Groups = 0 2 3 4 5 20 31 RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 1 (Get file attributes) NFS: File handle = [2E82] NFS: 4600FC00020000000A000000D260000004FE29590A000000CE600000CE006925 NFS: ETHER: ----- Ether Header ----- ETHER: ETHER: Packet 10 arrived at 20:41:14.71 ETHER: Packet size = 138 bytes ETHER: Destination = 0:a0:c9:9f:49:34, ETHER: Source = 0:a0:c9:9f:30:1, ETHER: Ethertype = 0800 (IP) ETHER: IP: ----- IP Header ----- IP: IP: Version = 4 IP: Header length = 20 bytes IP: Type of service = 0x00 IP: xxx. .... = 0 (precedence) IP: ...0 .... = normal delay IP: .... 0... = normal throughput IP: .... .0.. = normal reliability IP: Total length = 124 bytes IP: Identification = 26983 IP: Flags = 0x4 IP: .1.. .... = do not fragment IP: ..0. .... = last fragment IP: Fragment offset = 0 bytes IP: Time to live = 255 seconds/hops IP: Protocol = 17 (UDP) IP: Header checksum = b98f IP: Source address = 192.168.0.1 IP: Destination address = 192.168.0.254 IP: No options IP: UDP: ----- UDP Header ----- UDP: UDP: Source port = 2049 UDP: Destination port = 1022 (Sun RPC) UDP: Length = 104 UDP: Checksum = C4A6 UDP: RPC: ----- SUN RPC Header ----- RPC: RPC: Transaction id = 1269155982 RPC: Type = 1 (Reply) RPC: This is a reply to frame 9 RPC: Status = 0 (Accepted) RPC: Verifier : Flavor = 0 (None), len = 0 bytes RPC: Accept status = 0 (Success) RPC: NFS: ----- Sun NFS ----- NFS: NFS: Proc = 1 (Get file attributes) NFS: Status = 0 (OK) NFS: File type = 1 (Regular File) NFS: Mode = 0100644 NFS: Type = Regular file NFS: Setuid = 0, Setgid = 0, Sticky = 0 NFS: Owner's permissions = rw- NFS: Group's permissions = r-- NFS: Other's permissions = r-- NFS: Link count = 1, UID = 0, GID = 0, Rdev = 0x0 NFS: File size = 0, Block size = 8192, No. of blocks = 0 NFS: File system id = 16515142, File id = 24786 NFS: Access time = 07-Dec-98 19:41:14.685634 GMT NFS: Modification time = 07-Dec-98 19:41:14.685634 GMT NFS: Inode change time = 07-Dec-98 19:41:14.685634 GMT NFS: --------------385830322A8CC3FBC2C05EC3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 12:06:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09669 for freebsd-current-outgoing; Mon, 7 Dec 1998 12:06:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-22-dbn.dial-up.net [196.34.155.86]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09398 for ; Mon, 7 Dec 1998 12:05:54 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id WAA29135; Mon, 7 Dec 1998 22:02:34 +0200 (SAT) From: Robert Nordier Message-Id: <199812072002.WAA29135@ceia.nordier.com> Subject: Re: strings - elf vs aout In-Reply-To: <199812071728.KAA02857@mt.sri.com> from Nate Williams at "Dec 7, 98 10:28:41 am" To: nate@mt.sri.com (Nate Williams) Date: Mon, 7 Dec 1998 22:02:29 +0200 (SAT) Cc: rnordier@nordier.com, syssgm@dtir.qld.gov.au, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Nate Williams wrote: > > > There's an annoying anomaly in the new version of strings. The traditional > > > version specifically included tabs as valid characters for strings, while > > > the new one doesn't, leading to: > > > > > > $ printf 'My dog has\tno nose' > foo > > > $ strings -aout foo > > > My dog has no nose > > > $ strings -elf foo > > > My dog has > > > no nose > > > $ > > > > > > I run "strings" on lots of files (eg frobnoz.doc), not just executables. > > > This is irritating me specifically in regard to the INCLUDE_CONFIG_FILE > > > kernel compile option which now requires "strings -aout" to recover the > > > config file. > > > > > > Shall I devise and commit a fix for this behaviour? > > > > If you want to do this, I'd suggest making it an option. Current > > standards, such as the Single UNIX Specification, apparently regard a > > printable string as 4 or more isprint(3) chars followed by '\n' or > > '\0'. > > Then 'strings' for ELF is broken, since \t is not a newline of end of a > string, and Steven's comments are valid. Reverting to the traditional approach would be a double-step from strict SUS conformance, as well as a single step away from standard GNU binutils behavior. However, if the consensus is that these issues are of little importance or relevance, I wouldn't object particularly. -- 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 Dec 7 12:44:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13640 for freebsd-current-outgoing; Mon, 7 Dec 1998 12:44:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xxx.video-collage.com (xxx.video-collage.com [209.122.149.226] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13635 for ; Mon, 7 Dec 1998 12:44:31 -0800 (PST) (envelope-from mi@video-collage.com) X-Relay-IP:   Received: (from mi@localhost) by xxx.video-collage.com (8.9.1a/8.9.1) id PAA14200 for current@freebsd.org; Mon, 7 Dec 1998 15:44:25 -0500 (EST) Message-Id: <199812072044.PAA14200@xxx.video-collage.com> Subject: more on aout-to-elf To: current@frebsd.org Date: Mon, 7 Dec 1998 15:43:39 -0500 (EST) From: Mikhail Teterin X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19006 for freebsd-current-outgoing; Mon, 7 Dec 1998 13:34:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dagda.sunflower.com (dagda.sunflower.com [24.124.0.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18999 for ; Mon, 7 Dec 1998 13:34:58 -0800 (PST) (envelope-from bsd-curr@artorius.sunflower.com) Received: from artorius.sunflower.com (artorius.sunflower.com [24.124.0.6]) by dagda.sunflower.com (8.9.1a/8.9.1) with ESMTP id PAA08985 for ; Mon, 7 Dec 1998 15:36:36 -0600 (CST) Date: Mon, 7 Dec 1998 15:35:04 -0600 (CST) From: "Stephen D. Spencer" Reply-To: admin@sunflower.com To: current@FreeBSD.ORG Subject: Re: Make World failure In-Reply-To: <67156.913036911@gjp.erols.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Dec 1998, Gary Palmer wrote: > >From a -current supped form freefall ~6am EST this morning, and being build on > an Alpha: > > building standard gcc library > [...] > ln -sf /usr/src/gnu/usr.bin/perl/libperl/config.SH-elf.alpha config.sh > ln -sf /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/config_h.SH > config_h.sh > sh config_h.sh > Extracting config.h (with variable substitutions) > sed: 1: "s!^#un-def!#undef!": bad flag in substitute command: 's' > *** Error code 1 > [..] > > That looks ... bad :) Indeed. Same error on the i386 version, today's sources. Stephen Spencer Lawrence, KS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 15:01:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28803 for freebsd-current-outgoing; Mon, 7 Dec 1998 15:01:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [207.149.232.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA28798 for ; Mon, 7 Dec 1998 15:01:09 -0800 (PST) (envelope-from rgrimes@GndRsh.aac.dev.com) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.8/8.8.8) id OAA26700; Mon, 7 Dec 1998 14:59:40 -0800 (PST) (envelope-from rgrimes) From: "Rodney W. Grimes" Message-Id: <199812072259.OAA26700@GndRsh.aac.dev.com> Subject: Re: sio breakage In-Reply-To: <199812010330.OAA20453@godzilla.zeta.org.au> from Bruce Evans at "Dec 1, 98 02:30:14 pm" To: bde@zeta.org.au (Bruce Evans) Date: Mon, 7 Dec 1998 14:59:40 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... > > something() > { > asm("cli"); > asm("sti"); > } > ... > > Fixes: > kernel: send a fatal signal to applications that do this. > applications: don't do this. If interrupts must be disabled, then all > critical code and data must be within one page. Do we have the equivelent of the VMS wire(memory_range) call so that programs can force thier critical code sections to be non page faultable? -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD http://www.aai.dnsmgr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 15:44:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02379 for freebsd-current-outgoing; Mon, 7 Dec 1998 15:44:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mcfs.whowhere.com (mcfs.whowhere.com [209.1.236.44]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA02374 for ; Mon, 7 Dec 1998 15:44:23 -0800 (PST) (envelope-from erkaf@my-dejanews.com) Received: from Unknown/Local ([?.?.?.?]) by my-dejanews.com; Mon Dec 7 15:31:54 1998 To: freebsd-current@FreeBSD.ORG Date: Mon, 07 Dec 1998 15:31:54 -0700 From: "Kelvin Farmer" Message-ID: Mime-Version: 1.0 X-Sent-Mail: off X-Mailer: MailCity Service Subject: Phantom hard drive detection in GENERIC? X-Sender-Ip: 192.75.12.156 Organization: Deja News Mail (http://www.my-dejanews.com:80) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, the problem goes like this: a phantom hard drive (wd3) appears to be detected when the hardware is probed. The actual harddrives and cdrom are all detected properly, and if wd3 is removed (in a custom kernel), then there are no problems. However, in the initial installation, wd3 cannot be disabled, only wdc1, which also has a CDROM connected to it, so a cdrom installation is ruled out since the detection of wd3 halts the installation process like this: wd3: can't handle 65535 heads from partition tale (truncating to 16) wd3 cannot handle 65535 sectors (max 255) wd3 wdcontrol: reca failed reading fsbn0wd3: status 7e error 4 wd3 error reading primary partition table reading fsbn 0 (wd3 bn0;cn0 tn0 sn0) The GENERIC kernel detects my system like thus: stDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled ide_pci: busmaster 0 status: 60 from port: 0000ffa2 ide_pci: ide0:0 has been configured for DMA by BIOS ide_pci: ide0:1 has been configured for DMA by BIOS intel_piix_status: secondary master sample = 3, master recovery = 3 intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: secondary slave sample = 5, slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000ffaa found-> vendor=0x5333, dev=0x883d, revid=0x02 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base 80000000, size 26 [snip] wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc0: unit 1 (wd1): wd1: 1222MB (2503872 sectors), 2484 cyls, 16 heads, 63 S/T, 512 B/S wd1: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 1 (wd3): <\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\M^?\\M^?\M^?\M^?\M^?> wd3: 95MB (196607 sectors), 65535 cyls, 65535 heads, 65535 S/T, 512 B/S wd3: ATA INQUIRE valid = ffffffff, dmamword = ffffffff, apio = ffffffff, udma = ffffffff wdc1: unit 0 (atapi): , removable, accel, dma, iordis wcd0: 1378Kb/sec, 128Kb cache, audio play, 256 volume levels, ejectable tray wcd0: 120mm photo disc loaded, unlocked Hardware: 430 HX chipset. Intel 82371 SB is the PCI Bus Master IDE controller (PIIX3) 2 Quantum harddrive correctly identified, they are master and slave on the primary IDE. 1 Matshita cdrom, master on secondary IDE. -----== Sent via Deja News, The Discussion Network ==----- http://www.dejanews.com/ Easy access to 50,000+ discussion forums To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 15:49:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02916 for freebsd-current-outgoing; Mon, 7 Dec 1998 15:49:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp6.portal.net.au [202.12.71.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02905 for ; Mon, 7 Dec 1998 15:49:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00838; Mon, 7 Dec 1998 15:46:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812072346.PAA00838@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mikael Karpberg cc: mike@smith.net.au (Mike Smith), obrien@NUXI.com, jkh@zippy.cdrom.com, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Mon, 07 Dec 1998 02:48:59 +0100." <199812070148.CAA13594@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Dec 1998 15:46:47 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But... we have 1.44 MB on the CD... Since the bios manages to read the > file, wouldn't there be a generic way that we could also read something > from the CD? So that we could make a floppy which does a call and reads a > 5 MB image from the CD, and unpacks the kernel with MFS from that, with > full drivers and a nice splash image, too. :-) > But, lemme guess: "Sorry... There's no way to fool the BIO to read the CD" ? Correct. However Daniel's point about emulating a harddisk is a good one; I checked my El Torito docco and discovered I was out of date. If we're going to go off the beaten track, we might as well do it properly. A 10M harddisk image is going to be a much better idea in that case. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Dec 7 15:50:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03228 for freebsd-current-outgoing; Mon, 7 Dec 1998 15:50:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp6.portal.net.au [202.12.71.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03222 for ; Mon, 7 Dec 1998 15:50:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00852; Mon, 7 Dec 1998 15:47:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812072347.PAA00852@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mikael Karpberg cc: mike@smith.net.au (Mike Smith), tlambert@primenet.com, wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Mon, 07 Dec 1998 02:52:40 +0100." <199812070152.CAA13609@ocean.campus.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Dec 1998 15:47:57 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > According to Mike Smith: > > > o a mechanism for dumping drivers from the kernel after > > > installation so that they need not be installed twice: > > > once to boot, once to install; this probably implies > > > driver data areas be mapped copy-on-write to maintain > > > the data image integrity to allow it to be written > > > back out > > > > This is actually fairly tough, as the entire ELF object is not loaded > > in the first place. My preference is simply to track the driver(s) > > that are loaded, and request the use re-provide the media from which > > the driver was read when it comes time to copy it. > > Wouldn't the best and easiest solution here be something like this in > the loader: save_drivers_in_ram = (total_ram_MB > 8); > And if the variable is set, you just don't load the driver, you also > store the complete file it was loaded from in a memory block which > can then just be dumped to file. If you don't have enough memory to do > that, you can ask for the disks again, instead. That sounds like a worthwhile optimisation, but since you need to support asking for the disks, it's probably better to start with that first. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Dec 7 15:57:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03894 for freebsd-current-outgoing; Mon, 7 Dec 1998 15:57:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nina.pagesz.net (nina.pagesz.net [208.194.157.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03886 for ; Mon, 7 Dec 1998 15:57:54 -0800 (PST) (envelope-from rhh@pagesz.net) Received: from stealth.dummynet. (juana-31.pagesz.net [208.213.126.31]) by nina.pagesz.net (8.8.7/8.8.7) with ESMTP id SAA14173; Mon, 7 Dec 1998 18:58:13 -0500 Received: (from rhh@localhost) by stealth.dummynet. (8.9.1/8.8.8) id SAA01972; Mon, 7 Dec 1998 18:58:40 -0500 (EST) (envelope-from rhh) Message-ID: <19981207185840.B1171@pagesz.net> Date: Mon, 7 Dec 1998 18:58:40 -0500 From: Randall Hopper To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: "ldconfig" strangeness on 3.0-RELEASE Mail-Followup-To: John Polstra , current@freebsd.org References: <19981129102800.A1657@pagesz.net> <199812041650.IAA02119@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812041650.IAA02119@vashon.polstra.com>; from John Polstra on Fri, Dec 04, 1998 at 08:50:13AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra: |> 3) Why aren't these two directories in the default $ldconfig_paths_aout |> (AOUT) in /etc/rc.conf? AFAIK, they're all AOUT: |> /usr/lib/aout /usr/lib/compat | |/usr/lib/aout is added automatically by /etc/rc. Regarding |/usr/lib/compat: it is _not_ a.out on an ELF system. On an ELF |system, a.out compat libraries are in /usr/lib/compat/aout. Must have been an oversight when 3.0-RELEASE was cooked. The paths in the compat dists are usr/lib/compat. I haven't done anything custom, and here's what's in my /usr/lib/compat: stealth : /usr/lib/compat > ls aout/ libgcc.so.1.1 libreadline.so.2.0 libc.so.1.1 libgcc.so.261.0 libresolv.so.1.1 libc.so.2.2 libgmp.so.2.0 librpcsvc.so.1.1 libcurses.so.1.1 libgnumalloc.so.1.1 libskey.so.1.1 libdialog.so.2.0 libgnuregex.so.1.1 libtelnet.so.1.1 libf2c.so.1.1 libln.so.1.1 libtermcap.so.1.1 libforms.so.2.0 libm.so.1.1 libtermlib.so.1.1 libg++.so.1.1 libmalloc.so.1.1 libutil.so.1.1 libg++.so.2.0 libncurses.so.2.0 liby.so.1.1 libg++.so.3.0 libreadline.so.1.1 stealth : /usr/lib/compat > file * aout: directory libc.so.1.1: FreeBSD/i386 compact demand paged shared library not stripped libc.so.2.2: FreeBSD/i386 compact demand paged shared library not stripped ... |> 4) Why is this directory in the default $ldconfig_paths (ELF)? It's all AOUT: |> |> /usr/lib/compat | |No, it's all ELF on an ELF system. At least, it's supposed to be. |Didn't "make move-aout-libs" move the a.out libraries down into |/usr/lib/compat/aout when you ran it? I think I just let sysinstall install from the CD. Thanks for the reply. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 16:29:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08406 for freebsd-current-outgoing; Mon, 7 Dec 1998 16:29:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp4.portal.net.au [202.12.71.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08401 for ; Mon, 7 Dec 1998 16:29:37 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01208; Mon, 7 Dec 1998 16:27:23 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812080027.QAA01208@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Rodney W. Grimes" cc: bde@zeta.org.au (Bruce Evans), freebsd-current@FreeBSD.ORG Subject: Re: sio breakage In-reply-to: Your message of "Mon, 07 Dec 1998 14:59:40 PST." <199812072259.OAA26700@GndRsh.aac.dev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Dec 1998 16:27:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... > > > > something() > > { > > asm("cli"); > > asm("sti"); > > } > > > ... > > > > Fixes: > > kernel: send a fatal signal to applications that do this. > > applications: don't do this. If interrupts must be disabled, then all > > critical code and data must be within one page. > > Do we have the equivelent of the VMS wire(memory_range) call so that > programs can force thier critical code sections to be non page faultable? mlock() -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Dec 7 16:34:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09245 for freebsd-current-outgoing; Mon, 7 Dec 1998 16:34:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp4.portal.net.au [202.12.71.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09220 for ; Mon, 7 Dec 1998 16:34:38 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA01279; Mon, 7 Dec 1998 16:32:44 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812080032.QAA01279@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daniel C. Sobral" cc: freebsd-current@FreeBSD.ORG Subject: Re: FICL In-reply-to: Your message of "Mon, 07 Dec 1998 21:27:57 +0900." <366BC9CD.304D2049@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Dec 1998 16:32:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just learned about the addition of FICL to FreeBSD, I decided to > resubscribe (for a while, at least) to -current just to discuss this. > I should have expected: I had to distance myself from both FreeBSD and > Forth for a while and look what happens! :-) 8) > Ok, my two cents, though I still haven't read all the archive: You might want to get in touch with John Saunders (is that right?) as he's been tickling a few things for us. > > > whether there's much we can strip from the core wordset; I'll leave > > > that for the FORTH guruen to argue over. At 22k (plus whatever it > > > > As I said above, we probably can strip CORE-EXT and SEARCH - I wouldn't > > touch the CORE itself, however. > > I have yet to check out how the source is being handled, but I here is > my possibly irrelevant comments. I'll strive to get up to date before > adding any more cents to the vending machine, though... :-) > > CORE can be stripped. There is a lot of words in ANS' CORE that are > reduntant. Here, CORE represents more legacy than anything else. > > But I'd like this system to remain ANS in it's FreeBSD distribution. I think that this is a good point. And in fact I think it's probably worthwhile keeping the runtime ANS unless it's *really* hurting us for space (which it isn't right now). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Dec 7 17:25:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15898 for freebsd-current-outgoing; Mon, 7 Dec 1998 17:25:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp6.portal.net.au [202.12.71.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA15888 for ; Mon, 7 Dec 1998 17:24:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00886; Mon, 7 Dec 1998 15:52:36 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812072352.PAA00886@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "John Saunders" cc: "FreeBSD current" Subject: Re: Booting 3.0-RELEASE in a non-standard setup In-reply-to: Your message of "Mon, 07 Dec 1998 16:04:56 +1100." <002901be219f$21d16400$6cb611cb@saruman.scitec.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Dec 1998 15:52:36 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you press any key the /boot/loader file will be started > and it won't work properly in the case where the BIOS > drive number doesn't match the wd drive number. So never > press a key, let the boot block load the kernel directly. It will actually work in any case where the bootstrap works; you may need to set $num_ide_disks to correct the offset in the same fashion that you set the X: parameter. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Dec 7 17:47:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19735 for freebsd-current-outgoing; Mon, 7 Dec 1998 17:47:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mars.ecsnet.com (mars.ecsnet.com [204.57.81.130]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA19730 for ; Mon, 7 Dec 1998 17:46:59 -0800 (PST) (envelope-from mevans@ecsnet.com) Received: (qmail 40061 invoked from network); 8 Dec 1998 01:46:27 -0000 Received: from alpha.ecsnet.com (204.57.81.131) by mars.ecsnet.com with SMTP; 8 Dec 1998 01:46:27 -0000 Date: Mon, 7 Dec 1998 19:49:16 -0600 (CST) From: "Mark R. Evans" To: Greg Pavelcak cc: current@FreeBSD.ORG Subject: Re: Tk/Tcl Programs Freeze X In-Reply-To: <19981207114657.A95139@oit.umass.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 7 Dec 1998, Greg Pavelcak wrote: > On Mon, Dec 07, 1998 at 08:43:41AM -0600, Mark R. Evans wrote: > > This is the exact behavior that I'm seeing, both with wish 4.2 and > > wish8.0. I've tried recompiling all the tk/tcl ports, updated the system > > as of 12-7, still have the lockups. I re-cvsup'ed using a Nov 15 date, > > rebuilt the kernel and now everything works as it should. I guess I'll > > try to find the commit between 11-15 and now that is causing my problems. > > Thanks for the advice. > > > Just to narrow it down, I experienced the same problem with > sources from 11/21, I think. Certainly before Thanksgiving. > > I'd be happy to hear about anything you come up with. OK, I've tracked down what is causing my lockups when Tk/Tcl program exit. One Nov 23, a change was made to /usr/src/sys/kern/tty.c by bde to do the following: o Handle c_ispeed = 0 to c_ispeed = c_ospeed conversion here instead of in drivers and fix drivers that write to tp->t_termios. When I backed out this change, my Tk/Tcl programs began working as normal. I reverted by to tty.c v1.107. My guess is that I'm using a driver that needs to be fixed per the comment above. Unfortunately, I don't know which one... Anyway, the system is now working much better. Thanks to all who responded! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 18:52:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26133 for freebsd-current-outgoing; Mon, 7 Dec 1998 18:52:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26127 for ; Mon, 7 Dec 1998 18:52:18 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id DAA16612; Tue, 8 Dec 1998 03:48:21 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199812080248.DAA16612@ocean.campus.luth.se> Subject: Re: New drivers and install floppy space In-Reply-To: <199812072347.PAA00852@dingo.cdrom.com> from Mike Smith at "Dec 7, 98 03:47:57 pm" To: mike@smith.net.au (Mike Smith) Date: Tue, 8 Dec 1998 03:48:21 +0100 (CET) Cc: mike@smith.net.au, tlambert@primenet.com, wpaul@skynet.ctr.columbia.edu, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Mike Smith: > > > This is actually fairly tough, as the entire ELF object is not loaded > > > in the first place. My preference is simply to track the driver(s) > > > that are loaded, and request the use re-provide the media from which > > > the driver was read when it comes time to copy it. > > > > Wouldn't the best and easiest solution here be something like this in > > the loader: save_drivers_in_ram = (total_ram_MB > 8); > > And if the variable is set, you just don't load the driver, you also > > store the complete file it was loaded from in a memory block which > > can then just be dumped to file. If you don't have enough memory to do > > that, you can ask for the disks again, instead. > > That sounds like a worthwhile optimisation, but since you need to > support asking for the disks, it's probably better to start with that > first. Ofcourse, it's an optimisation... So it's best to have something to optimize first... Just thought I'd get the idea public, so it's thought of later. :-) /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 18:55:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26332 for freebsd-current-outgoing; Mon, 7 Dec 1998 18:55:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26320 for ; Mon, 7 Dec 1998 18:55:39 -0800 (PST) (envelope-from karpen@ocean.campus.luth.se) Received: (from karpen@localhost) by ocean.campus.luth.se (8.9.1/8.9.1) id DAA16632; Tue, 8 Dec 1998 03:52:03 +0100 (CET) (envelope-from karpen) From: Mikael Karpberg Message-Id: <199812080252.DAA16632@ocean.campus.luth.se> Subject: Re: New drivers and install floppy space In-Reply-To: <199812072346.PAA00838@dingo.cdrom.com> from Mike Smith at "Dec 7, 98 03:46:47 pm" To: mike@smith.net.au (Mike Smith) Date: Tue, 8 Dec 1998 03:52:03 +0100 (CET) Cc: mike@smith.net.au, obrien@NUXI.com, jkh@zippy.cdrom.com, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG According to Mike Smith: > > But... we have 1.44 MB on the CD... Since the bios manages to read the > > file, wouldn't there be a generic way that we could also read something > > from the CD? So that we could make a floppy which does a call and reads a > > 5 MB image from the CD, and unpacks the kernel with MFS from that, with > > full drivers and a nice splash image, too. :-) > > But, lemme guess: "Sorry... There's no way to fool the BIO to read the CD" > > Correct. *sigh* Why is it that there seems not to be a single standard which doesn't have HUGE technical problems in it, which any halfsane guy with half an education in the subject, would have spotted and fixed (with an too often obvious solution, at that) right away?? > However Daniel's point about emulating a harddisk is a good one; I > checked my El Torito docco and discovered I was out of date. > > If we're going to go off the beaten track, we might as well do it > properly. A 10M harddisk image is going to be a much better idea in > that case. Probably... If all BIOSes that handle CDROM booting can handle that... /Mikael To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 19:28:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA00497 for freebsd-current-outgoing; Mon, 7 Dec 1998 19:28:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sicily.odyssey.cs.cmu.edu (SICILY.ODYSSEY.CS.CMU.EDU [128.2.185.138]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA00491 for ; Mon, 7 Dec 1998 19:28:37 -0800 (PST) (envelope-from rvb+@sicily.odyssey.cs.cmu.edu) Cc: freebsd-current@FreeBSD.ORG Subject: Sloppy uio.uio_procp initialization ... References: <4.1.19981123122653.00abfe40@206.25.93.69> <19981125142249.B38959@matti.ee> From: "Robert V. Baron" Date: 07 Dec 1998 22:28:14 -0500 In-Reply-To: "Robert V. Baron"'s message of 02 Dec 1998 10:23:01 -0500 Message-ID: Lines: 30 X-Mailer: Gnus v5.4.46/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Recently I fixed vnode_pager_input_old, because it was doing a VOP_READ into a Coda fs, but it had set the uio.uio_procp to 0 vs curproc. (Coda freaks because it vgets a vnode [and hence locks it with curproc], then tries to unlock it with a 0 process pointer.) I just noticed (the hard way) the same design happens in ktrwrite(): ktrwrite(vp, kth) struct vnode *vp; register struct ktr_header *kth; { struct uio auio; struct iovec aiov[2]; register struct proc *p = curproc; /* XXX */ int error; ... auio.uio_procp = (struct proc *)0; ... vn_lock(vp, LK_EXCLUSIVE | LK_RETRY, p); error = VOP_WRITE(vp, &auio, IO_UNIT|IO_APPEND, p->p_ucred); VOP_UNLOCK(vp, 0, p); So here the vn_locks are using the actual process pointer, but since uio_procp is 0, coda will try an unlock not with curproc and fail. I'll change ktrwrite to use auio.uio_procp = curproc, Wed Noon EST, unless anyone objects. PS For the curious, Coda is locking and unlocking a vnode associated with the Coda vnode (which caches the file data) -- not the Coda vnode. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 20:40:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA08202 for freebsd-current-outgoing; Mon, 7 Dec 1998 20:40:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08196 for ; Mon, 7 Dec 1998 20:40:48 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id XAA03200 for ; Mon, 7 Dec 1998 23:40:42 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA28280; Mon, 7 Dec 1998 23:40:42 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id XAA07974 for freebsd-current@freebsd.org; Mon, 7 Dec 1998 23:40:42 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812080440.XAA07974@bb01f39.unx.sas.com> Subject: SNAP failure: bad sed flag To: freebsd-current@FreeBSD.ORG Date: Mon, 7 Dec 1998 23:40:42 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (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 been hit by this twice, yesterday and just now. Current as of about 45 minutes ago... Any ideas on this one folks? I've seen some sed updates go by, I'll try building sed and see what happens... oh well... Thanks, John cd /usr/src/gnu/usr.bin/perl/libperl; /usr/obj/elf/usr/src/tmp/usr/bin/make all; /usr/obj/elf/usr/src/tmp/usr/bin/make -B install ln -sf /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/config_h.SH config_h.sh ln -sf /usr/src/gnu/usr.bin/perl/libperl/config.SH-elf.i386 config.sh sh config_h.sh Extracting config.h (with variable substitutions) sed: 1: "s!^#un-def!#undef!": bad flag in substitute command: 's' *** Error code 1 Stop. *** Error code 1 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 21:05:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA09882 for freebsd-current-outgoing; Mon, 7 Dec 1998 21:05:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from schizo.cdsnet.net (schizo.cdsnet.net [204.118.244.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA09872 for ; Mon, 7 Dec 1998 21:05:16 -0800 (PST) (envelope-from mrcpu@internetcds.com) Received: from localhost (mrcpu@localhost) by schizo.cdsnet.net (8.8.8/8.7.3) with SMTP id VAA25372; Mon, 7 Dec 1998 21:01:47 -0800 (PST) Date: Mon, 7 Dec 1998 21:01:47 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Billy Bath x102 cc: current@FreeBSD.ORG Subject: Re: Quad CPU's under FreeBSD 3.0. In-Reply-To: <3.0.5.32.19981207135417.0082e370@gw1.tesys.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 A Digital ZX6000 with 4 P6-200's works fine under a > 1 year old version of 3.0. Haven't had the courage to upgrade to the latest release. I would feel confident that any name-brand (HP, Digital, Compaq, etc) multi-processor would work. On Mon, 7 Dec 1998, Billy Bath x102 wrote: > Hello, Support > Could you please tell me, which MB's are supported. I need to build a > system who could use Quad CPU's.. > The word is out there,that it runs fine. I want a pointer to select right > hardware.. > thanks.. > cheers,,bb > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 21:13:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA11205 for freebsd-current-outgoing; Mon, 7 Dec 1998 21:13:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA11197 for ; Mon, 7 Dec 1998 21:13:34 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id QAA16116; Tue, 8 Dec 1998 16:13:28 +1100 Date: Tue, 8 Dec 1998 16:13:28 +1100 From: Bruce Evans Message-Id: <199812080513.QAA16116@godzilla.zeta.org.au> To: rvb@cs.cmu.edu Subject: Re: Sloppy uio.uio_procp initialization ... Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Recently I fixed vnode_pager_input_old, because it was doing a >VOP_READ into a Coda fs, but it had set the uio.uio_procp to 0 vs >curproc. (Coda freaks because it vgets a vnode [and hence locks it >with curproc], then tries to unlock it with a 0 process pointer.) >I just noticed (the hard way) the same design happens in ktrwrite(): NetBSD doesn't pass a process pointer to the locking functions. When I looked at this in connection with some problems in quotaoff(), I deciced that NetBSD is correct, for the following reason: unlocking should only be done by the same process that holds the lock, except possibly during process exit and system shutdown, since unlocking another process' locks won't actually work while that process is still alive. Unlocking on behalf of another process during process exit and system shutdown apparently isn't needed (except probably when we shoot ourself in the foot by doing sync(&proc0, NULL) in boot() even in the non-panic case). Therefore, the process to use for unlocking is always given by curproc, and there is no need to waste time passing it to unlocking functions, and no way to use wrong values for it taken from uio.uio_procp. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 22:08:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA16507 for freebsd-current-outgoing; Mon, 7 Dec 1998 22:08:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp2.andrew.cmu.edu (SMTP2.ANDREW.CMU.EDU [128.2.10.82]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA16496 for ; Mon, 7 Dec 1998 22:08:19 -0800 (PST) (envelope-from mwhite@cmu.edu) Received: from DEIMOS.REM.CMU.EDU (DEIMOS.REM.CMU.EDU [128.2.108.154]) by smtp2.andrew.cmu.edu (8.8.5/8.8.2) with ESMTP id BAA15663 for ; Tue, 8 Dec 1998 01:08:11 -0500 (EST) Date: Tue, 08 Dec 1998 01:08:12 -0500 From: Matt White To: current@FreeBSD.ORG Subject: PAO Integration? Message-ID: <2546225248.913079292@DEIMOS.REM.CMU.EDU> Originator-Info: login-id=; server=cyrus.andrew.cmu.edu X-Mailer: Mulberry (Win32) [1.4.0, s/n S-100002] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any work in progress to integrate the PAO variant of FreeBSD back into -current? If so, who do I talk to about helping? If not, is it because of philisophical or manpower issues? -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 7 22:54:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19880 for freebsd-current-outgoing; Mon, 7 Dec 1998 22:54:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp4.portal.net.au [202.12.71.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19875 for ; Mon, 7 Dec 1998 22:54:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA00628; Mon, 7 Dec 1998 22:52:13 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812080652.WAA00628@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Matt White cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Tue, 08 Dec 1998 01:08:12 EST." <2546225248.913079292@DEIMOS.REM.CMU.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Dec 1998 22:52:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any work in progress to integrate the PAO variant of FreeBSD back > into -current? If so, who do I talk to about helping? If not, is it > because of philisophical or manpower issues? Much of the PAO code is not suitable for inclusion; some parts however are indeed desirable. There is major work underway to improve our infrastructure to better support removable devices of this kind. There are both philosophical and manpower issues involved here; if you're interested in helping you should start by talking to Garrett Wollman (wollman@freebsd.org). It's also important to note that the correct list for discussing laptop-related issues is mobile@freebsd.org -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Dec 7 23:11:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21348 for freebsd-current-outgoing; Mon, 7 Dec 1998 23:11:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp4.portal.net.au [202.12.71.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21341 for ; Mon, 7 Dec 1998 23:11:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA00791; Mon, 7 Dec 1998 23:09:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812080709.XAA00791@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Matthew N. Dodd" cc: Mike Smith , current@FreeBSD.ORG Subject: Re: KLD - what's the idea? In-reply-to: Your message of "Mon, 07 Dec 1998 00:46:20 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 07 Dec 1998 23:09:03 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I was kind of wondering how to avoid compiling in 20 to 60 Kb of firmware > > > image for support of RAM based TMS380 cards. In addition, some each > > > particular card may have specific firmware it wants loaded. I'm looking > > > for some way to load a really basic config file to let the driver know > > > which image goes with which card. > > > > > > Doing this from userland isn't good as I can't do much with the card until > > > the firmware is loaded. > > > > Are these PnP devices, ie. can you differentiate between them before > > running the probe? Are they ever likely to be critical to the boot > > process? > > ISA/ISA-PnP/EISA/PCI bards. The driver/firmware for the non-PnP ISA card will have to be loaded manually. Assuming that the PnP information for the other cards is enough to determine which firmware should be loaded for them, they should all be achievable with no user intervention. > How critical to the boot process are network cards? In the case of eg. network installs, or diskless booting, critical. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Dec 8 00:03:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA26275 for freebsd-current-outgoing; Tue, 8 Dec 1998 00:03:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA26270 for ; Tue, 8 Dec 1998 00:03:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id AAA85086; Tue, 8 Dec 1998 00:02:45 -0800 (PST) To: Mikael Karpberg cc: mike@smith.net.au (Mike Smith), obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Tue, 08 Dec 1998 03:52:03 +0100." <199812080252.DAA16632@ocean.campus.luth.se> Date: Tue, 08 Dec 1998 00:02:44 -0800 Message-ID: <85082.913104164@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If we're going to go off the beaten track, we might as well do it > > properly. A 10M harddisk image is going to be a much better idea in > > that case. > > Probably... If all BIOSes that handle CDROM booting can handle that... Which is as good a time as any to make a *practical* suggestion and get us moving back in the direction of progress, I think. :-) Let's postpone this discussion for another 15 days or so, until Mike can return (to the US) from the Australian location he's currently occupying. He and I will look over his spec and see if we can't hack mkisofs into using a 10MB image rather than the 1.44MB image it uses now and I'll beat some release bits into actually using that 10MB image in some reasonably productive way, say as a super fixit disk/small X terminal, and burn about 10 copies of the resulting CD. Then I'll come back here and ask those of you who are currently able to boot the 2.2.x or 3.0 release CDs on your machines to contact me with information on your configuration. We'll pick out 10 people who seem to represent a reasonably diverse collection of CD-booters and send them a copy of of this. If it works on all 10, that will be a good sign. If it does not, it won't be and we can rethink this. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 00:22:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA28094 for freebsd-current-outgoing; Tue, 8 Dec 1998 00:22:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA28087 for ; Tue, 8 Dec 1998 00:22:31 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id AAA07810; Tue, 8 Dec 1998 00:21:42 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma007797; Tue, 8 Dec 98 00:21:31 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id AAA14591; Tue, 8 Dec 1998 00:21:30 -0800 (PST) From: Archie Cobbs Message-Id: <199812080821.AAA14591@bubba.whistle.com> Subject: Re: SNAP failure: bad sed flag In-Reply-To: <199812080440.XAA07974@bb01f39.unx.sas.com> from "John W. DeBoskey" at "Dec 7, 98 11:40:42 pm" To: jwd@unx.sas.com (John W. DeBoskey) Date: Tue, 8 Dec 1998 00:21:30 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 John W. DeBoskey writes: > I've been hit by this twice, yesterday and just now. Current as of > about 45 minutes ago... Any ideas on this one folks? > > I've seen some sed updates go by, I'll try building sed and see what > happens... oh well... ... > Extracting config.h (with variable substitutions) > sed: 1: "s!^#un-def!#undef!": bad flag in substitute command: 's' > *** Error code 1 Yesterday I fixed a bug in sed that happens when the replacement pattern is > 4090 bytes.. so it shouldn't have affected this case, but you might try sed without that change just to rule it out as a possible cause. -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 Dec 8 00:28:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29212 for freebsd-current-outgoing; Tue, 8 Dec 1998 00:28:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.scancall.no (www.scancall.no [195.139.183.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA29207 for ; Tue, 8 Dec 1998 00:28:38 -0800 (PST) (envelope-from Marius.Bendiksen@scancall.no) Received: from super2.langesund.scancall.no [195.139.183.29] by www with smtp id KQZHEVDL; Tue, 08 Dec 98 08:28:33 GMT (PowerWeb version 4.04r6) Message-Id: <3.0.5.32.19981208092807.009bb210@mail.scancall.no> X-Sender: Marius@mail.scancall.no X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 08 Dec 1998 09:28:07 +0100 To: "Kelvin Farmer" , freebsd-current@FreeBSD.ORG From: Marius Bendiksen Subject: Re: Phantom hard drive detection in GENERIC? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG FWIW, I've seen this problem for some time now. I suspected a problem in my BIOS or somesuch. --- Marius Bendiksen, IT-Trainee, ScanCall AS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 00:32:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29450 for freebsd-current-outgoing; Tue, 8 Dec 1998 00:32:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA29443 for ; Tue, 8 Dec 1998 00:32:10 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id TAA15789; Tue, 8 Dec 1998 19:01:32 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <85082.913104164@zippy.cdrom.com> Date: Tue, 08 Dec 1998 19:01:32 +1030 (CST) From: "Daniel O'Connor" To: "Jordan K. Hubbard" Subject: Re: New drivers and install floppy space Cc: current@FreeBSD.ORG, obrien@NUXI.com, (Mike Smith) , Mikael Karpberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-98 Jordan K. Hubbard wrote: > with information on your configuration. We'll pick out 10 people who > seem to represent a reasonably diverse collection of CD-booters and > send them a copy of of this. If it works on all 10, that will be a > good sign. If it does not, it won't be and we can rethink this. :-) Well, I'm about to sacrifice another virgin CD blank to the ravening CD monster to test this.. The first one I did had a broken partition table, so it would SEE it, just not boot :) OK, thats done.. and the BIOS says that it sees the parition and its moved my hard drives up a letter.. It then tries to boot, but gets 'Missing operating system' Note that this is trying to boot off a SCSI CDROM (which works for, say the 2.2.7 CD). The board is a P6SBS Supermicro job. (which has an Ami WinBIOS) On our Abit board with an Award BIOS I get the same results.. It sees the partition, but fails to boot. The procedure to make this disc was as follows -> dd if=/dev/zero of=/tmp/hd_img.raw bs=1k count=10240 vnconfig /dev/vn0 /tmp/hd_img.raw awk 'BEGIN {printf "%c%c", 85, 170}' | dd of=/tmp/hd_img.raw obs=1 seek=510 conv=notrunc disklabel -Brw -b /usr/mdec/bootwd -s /usr/mdec/bootwd vn0 auto # Note that I changed this from how make release makes a floppy (different boot blocks) mount it, put a kernel on it etc.. I then altered mkhbrid so if the boot image wasn't the size of a disk it assumed it was a HD (ie the type was set to HD, not floppy in the descriptor) I tried this but it didn't work (it saw it was bootable, but didn't use the partition), Mike suggested I run fdisk on it and make partition 1 the correct partition (before it was partition 4). This got me where I am now :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 01:16:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA03403 for freebsd-current-outgoing; Tue, 8 Dec 1998 01:16:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA03396 for ; Tue, 8 Dec 1998 01:16:42 -0800 (PST) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id CAA06787 for ; Tue, 8 Dec 1998 02:16:26 -0700 (MST) (envelope-from brett@peloton.physics.montana.edu) Date: Tue, 8 Dec 1998 02:16:26 -0700 (MST) From: Brett Taylor To: freebsd-current@FreeBSD.ORG Subject: make aout-to-world-build problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I've been trying to do a make aout-to-world-build w/ -current sources from that I cvsup'ed on the 6th of Dec. I am attempting to upgrade from 2.2.8 to -current. Whenever I try the build though I get this error: cc -O -pipe -D_GNU_SOURCE -I- -I. -I/usr/src-current/gnu/usr.bin/binutils/strip -I/usr/src-current/gnu/usr.bin/binutils/strip/../libbfd/i386 -I/usr/src-current/gnu/usr.bin/binutils/strip/../../../../contrib/ binutils/include -I/usr/src-current/gnu/usr.bin/binutils/strip/../libbinutils -I/usr/src-current/gnu/usr.bin/binutils/strip/../../../../contrib/ binutils/binutils -I/usr/obj/aout/usr/src-current/tmp/usr/include -static -o strip objcopy.o is-strip.o -L../libbinutils -lbinutils -L../libbfd -lbfd -L../libiberty -liberty cp strip maybe_stripped strip maybe_stripped strip: maybe_stripped: File format not recognized *** Error code 1 I am not sure what the problem is here. Anyone have any ideas why this is happening? Brett ****************************************************************** Brett Taylor brett@peloton.physics.montana.edu http://peloton.physics.montana.edu/brett/ On the eve of his 21st birthday, he set out on his own He was 30 years and runnin' when he found his way back home Ridin' a storm across the mountains and an achin' in his heart Said he came to turn the pages and to make a brand new start To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 01:32:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04815 for freebsd-current-outgoing; Tue, 8 Dec 1998 01:32:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from btp1da.phy.uni-bayreuth.de (btp1da.phy.uni-bayreuth.de [132.180.20.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA04798; Tue, 8 Dec 1998 01:32:06 -0800 (PST) (envelope-from werner@btp1da.phy.uni-bayreuth.de) Received: (from werner@localhost) by btp1da.phy.uni-bayreuth.de (8.8.8/8.7.3) id KAA26297; Tue, 8 Dec 1998 10:28:49 +0100 (MET) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 08 Dec 1998 10:28:49 +0100 (MET) Organization: University of bayreuth From: Werner Griessl To: "Michael C. Vergallen" , current@FreeBSD.ORG Subject: Re: problems building world Cc: jhicks@jhicks.glenatl.glenayre.com, freebsd-stable@FreeBSD.ORG, Allan Saddi , Jerry Hicks Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-98 Michael C. Vergallen wrote: > The problem must have come into the sources saturday, sunday or monday. > Because I cvsuped my code on friday and all went okey. all my systems > are okey and no build problems where encountered here. > > Michael > --- > Michael C. Vergallen A.k.A. Mad Mike, > Sportstraat 28 http://www.double-barrel.be/mvergall/ > B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ > Belgium tel : 32-9-2227764 Fax : 32-9-2224976 > > On Mon, 7 Dec 1998, Jerry Hicks wrote: > >> same here... >> >> J. Hicks >> jerry.hicks@glenayre.com >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-stable" in the body of the message >> > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---------------------------------- I believe the problem comes on monday and I have also the same problem in current: cd /F/3.0/src/gnu/usr.bin/perl/libperl; /usr/obj/elf/F/3.0/src/tmp/usr/bin/make all; /usr/obj/elf/F/3.0/src/tmp/usr/bin/make -B install ln -sf /F/3.0/src/gnu/usr.bin/perl/libperl/config.SH-elf.i386 config.sh ln -sf /F/3.0/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/config_h.SH config_h.sh sh config_h.sh Extracting config.h (with variable substitutions) sed: 1: "s!^#un-def!#undef!": bad flag in substitute command: 's' *** Error code 1 in stable: ===> gnu/usr.bin/man/lib sed -e 's,%apropos%,/usr/bin/apropos,' -e 's,%whatis%,/usr/bin/whatis,' -e 's,%pager%,more -s,' -e 's,%troff%,/usr/bin/groff -man,' -e 's,%nroff%,/usr/bin/groff -Wall -mtty-char -Tascii -man,' -e 's,%tbl%,/usr/bin/tbl,' -e 's,%col%,/usr/bin/col,' -e 's,%pic%,/usr/bin/pic,' -e 's,%eqn%,,' -e 's,%neqn%,/usr/bin/eqn -Tascii,' -e 's,%vgrind%,/usr/bin/vgrind,' -e 's,%refer%,/usr/bin/refer,' -e 's,%grap%,,' -e 's,%zcat%,/usr/bin/zcat,' -e 's,%manpath_config_file%,/etc/manpath.config,' -e 's,%compress%,/usr/bin/gzip -c,' -e 's,%compext%,.gz,' /F/2.2/src/gnu/usr.bin/man/lib/config.h_dist > config.h sed: 1: "s,%whatis%,/usr/bin/wha ...": bad flag in substitute command: 's' *** Error code 1 Werner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 02:25:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09227 for freebsd-current-outgoing; Tue, 8 Dec 1998 02:25:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ren.dtir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09222 for ; Tue, 8 Dec 1998 02:25:18 -0800 (PST) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id UAA11323; Tue, 8 Dec 1998 20:23:53 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma011316; Tue, 8 Dec 98 20:23:44 +1000 Received: from atlas.dtir.qld.gov.au (atlas.dtir.qld.gov.au [167.123.8.9]) by ogre.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id UAA17094; Tue, 8 Dec 1998 20:23:44 +1000 (EST) Received: from nymph.dtir.qld.gov.au (nymph.dtir.qld.gov.au [167.123.10.10]) by atlas.dtir.qld.gov.au (8.8.5/8.8.5) with ESMTP id UAA15800; Tue, 8 Dec 1998 20:23:44 +1000 (EST) Received: from nymph.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by nymph.dtir.qld.gov.au (8.8.8/8.8.7) with ESMTP id UAA26960; Tue, 8 Dec 1998 20:23:42 +1000 (EST) (envelope-from syssgm@nymph.dtir.qld.gov.au) Message-Id: <199812081023.UAA26960@nymph.dtir.qld.gov.au> To: Robert Nordier cc: nate@mt.sri.com (Nate Williams), freebsd-current@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: strings - elf vs aout References: <199812072002.WAA29135@ceia.nordier.com> In-Reply-To: <199812072002.WAA29135@ceia.nordier.com> from Robert Nordier at "Sat, 07 Dec 1998 22:02:29 +0200" Date: Tue, 08 Dec 1998 20:23:41 +1000 From: Stephen McKay Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 7th December 1998, Robert Nordier wrote: >Nate Williams wrote: >> > > Shall I devise and commit a fix for this behaviour? >> > >> > If you want to do this, I'd suggest making it an option. Current >> > standards, such as the Single UNIX Specification, apparently regard a >> > printable string as 4 or more isprint(3) chars followed by '\n' or >> > '\0'. >> >> Then 'strings' for ELF is broken, since \t is not a newline of end of a >> string, and Steven's comments are valid. Hmm. Strict adherence to this '\n' or '\0' rule would suck a lot. Let's not "fix" that. What idiots wrote this spec? >Reverting to the traditional approach would be a double-step from >strict SUS conformance, as well as a single step away from standard >GNU binutils behavior. It also says "Additional implementation-dependent strings may be written." So I won't feel too bad hardcoding tab. It just sucks too much otherwise. >However, if the consensus is that these issues are of little >importance or relevance, I wouldn't object particularly. I'm going to add '\t' back to strings unless I'm shouted down. But I never get anything done except on weekends, so there's plenty of time to work up a good argument... Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 03:56:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA16202 for freebsd-current-outgoing; Tue, 8 Dec 1998 03:56:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from speed.matrix.com.br (speed.matrix.com.br [200.202.17.241]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA16194 for ; Tue, 8 Dec 1998 03:56:37 -0800 (PST) (envelope-from camposr@MATRIX.COM.BR) Received: from localhost (speed@localhost) by speed.matrix.com.br (8.9.1/8.9.1) with SMTP id JAA10679 for ; Tue, 8 Dec 1998 09:56:38 -0200 (EDT) X-Authentication-Warning: speed.matrix.com.br: speed owned process doing -bs Date: Tue, 8 Dec 1998 09:56:38 -0200 (EDT) From: Rodrigo Campos X-Sender: speed@speed.matrix.com.br To: freebsd-current@FreeBSD.ORG Subject: dummynet + freebsd 3.0 Message-ID: Organization: Matrix Network MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've applied the dn-3.0-981001.diffs patch to freebsd 3.0 release in order to use dummynet. Ipfw and the kernel compiled just fine but when i try to configure a pipe the following problem occured: # ipfw pipe 1 config bw 200kbit/s ipfw: setsockopt(IP_DUMMYNET_CONFIGURE): Protocol not available any clues ? cheers, -- ________________________ Rodrigo Albani de Campos [join.the.silicon.trip] Matrix Internet - NOC To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 04:05:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19008 for freebsd-current-outgoing; Tue, 8 Dec 1998 04:05:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19003 for ; Tue, 8 Dec 1998 04:05:37 -0800 (PST) (envelope-from 0fwi@comm-plus.NET) From: 0fwi@comm-plus.NET Received: from comm-plus.net (sparc4-three.comm-plus.net [206.239.211.13]) by freefall.freebsd.org (8.8.8/8.8.5) with SMTP id EAA15914 for ; Tue, 8 Dec 1998 04:05:38 -0800 (PST) Received: from default by comm-plus.net (SMI-8.6/SMI-SVR4) id HAA10804; Tue, 8 Dec 1998 07:03:46 -0500 Date: Tue, 8 Dec 1998 07:03:46 -0500 Message-Id: <199812081203.HAA10804@comm-plus.net> To: jgurt@aol.com Subject: Hot Business You Can Work From Home Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Look, we don't want to waste your time.......or ours If you're serious about retiring in the next 2 years with enough income to live the "good life" and not afraid to work for it, we can help you. REGARDLESS OF YOUR CURRENT AGE OR YOUR DEBT LOAD! Please don't bother to call unless you are totally serious. Call today- toll free Recorded Message 1-800-320-9895 Ext 1808 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 05:38:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25837 for freebsd-current-outgoing; Tue, 8 Dec 1998 05:38:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shell2.ba.best.com (shell2.ba.best.com [206.184.139.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25825; Tue, 8 Dec 1998 05:38:35 -0800 (PST) (envelope-from asaddi@philosophysw.com) Received: from localhost (asaddi@localhost) by shell2.ba.best.com (8.9.0/8.9.0/best.sh) with ESMTP id FAA26363; Tue, 8 Dec 1998 05:38:31 -0800 (PST) X-Authentication-Warning: shell2.ba.best.com: asaddi owned process doing -bs Date: Tue, 8 Dec 1998 05:38:30 -0800 (PST) From: Allan Saddi X-Sender: asaddi@shell2.ba.best.com To: stable@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: Re: problems building world In-Reply-To: Message-ID: Organization: Philosophy SoftWorks 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, 8 Dec 1998, Werner Griessl wrote: > I believe the problem comes on monday and I have also the same problem > in current: > > [snip] > sed: 1: "s!^#un-def!#undef!": bad flag in substitute command: 's' > *** Error code 1 > > in stable: > > [snip] > sed: 1: "s,%whatis%,/usr/bin/wha ...": bad flag in substitute command: 's' > *** Error code 1 After enduring another abortive buildworld, I was able to isolate the problem to the new version of sed (which gets built into /usr/obj/usr/src/tmp/usr/bin). I just checked the CVS repository and there seems to be a recent commit in both -stable and -current to sed's compile.c by archie. I'll try out the previous revision... -- Allan Saddi "The Earth is the cradle of mankind, asaddi@philosophysw.com but we cannot live in the cradle http://www.philosophysw.com/asaddi/ forever." - K.E. Tsiolkovsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 06:29:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA00197 for freebsd-current-outgoing; Tue, 8 Dec 1998 06:29:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA00192 for ; Tue, 8 Dec 1998 06:29:50 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id JAA86478; Tue, 8 Dec 1998 09:29:37 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Archie Cobbs cc: jwd@unx.sas.com (John W. DeBoskey), freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: SNAP failure: bad sed flag In-reply-to: Your message of "Tue, 08 Dec 1998 00:21:30 PST." <199812080821.AAA14591@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 Dec 1998 09:29:37 -0500 Message-ID: <86474.913127377@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs wrote in message ID <199812080821.AAA14591@bubba.whistle.com>: > > Extracting config.h (with variable substitutions) > > sed: 1: "s!^#un-def!#undef!": bad flag in substitute command: 's' > > *** Error code 1 > > Yesterday I fixed a bug in sed that happens when the replacement > pattern is > 4090 bytes.. so it shouldn't have affected this case, > but you might try sed without that change just to rule it out as > a possible cause. >From sources CVSupped direct from freefall at 6am EST on Tuesday (i.e. today) install -C -c -o root -g wheel -m 444 libgcc.a /usr/obj/elf/usr/src/tmp/usr/l ib install -C -c -o root -g wheel -m 444 libgcc_pic.a /usr/obj/elf/usr/src/tmp/usr/lib cd /usr/src/gnu/usr.bin/perl/libperl; /usr/obj/elf/usr/src/tmp/usr/bin/make all; /usr/obj/elf/usr/src/tmp/usr/bin/make -B install ln -sf /usr/src/gnu/usr.bin/perl/libperl/config.SH-elf.alpha config.sh ln -sf /usr/src/gnu/usr.bin/perl/libperl/../../../../contrib/perl5/config_h.SH config_h.sh sh config_h.sh Extracting config.h (with variable substitutions) sed: 1: "s!^#un-def!#undef!": bad flag in substitute command: 's' *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error (This is on the Alpha, but evidence has shown its not alpha specific) Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 07:02:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02850 for freebsd-current-outgoing; Tue, 8 Dec 1998 07:02:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from o2.cs.rpi.edu (o2.cs.rpi.edu [128.113.96.156]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02845 for ; Tue, 8 Dec 1998 07:02:15 -0800 (PST) (envelope-from crossd@o2.cs.rpi.edu) Received: from localhost (crossd@localhost) by o2.cs.rpi.edu (980427.SGI.8.8.8/980728.SGI.AUTOCF) via ESMTP id KAA66020; Tue, 8 Dec 1998 10:01:35 -0500 (EST) Date: Tue, 8 Dec 1998 10:01:30 -0500 From: "David E. Cross" To: "Jordan K. Hubbard" cc: Mikael Karpberg , Mike Smith , obrien@NUXI.com, current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-Reply-To: <85082.913104164@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 8 Dec 1998, Jordan K. Hubbard wrote: > > > If we're going to go off the beaten track, we might as well do it > > > properly. A 10M harddisk image is going to be a much better idea in > > > that case. > > > > Probably... If all BIOSes that handle CDROM booting can handle that... > > Which is as good a time as any to make a *practical* suggestion and > get us moving back in the direction of progress, I think. :-) > > Let's postpone this discussion for another 15 days or so, until Mike > can return (to the US) from the Australian location he's currently > occupying. He and I will look over his spec and see if we can't hack > mkisofs into using a 10MB image rather than the 1.44MB image it uses My understanding of this has been that the BIOS treats the CDROM as a virtual floppy drive for the purposes of booting off of it (which matches my experience of specifying a floppy disk image as the boot file when using mkisofs, and having that work). I think a perhaps better solution, and more usefull to a wider variety of people would be to have a bootdisk that would then mount its root filesystem off of the CDROM in a conventional manor, and make that the 'bootfile' on the CDROM. So a person with a BIOS that cannot boot off of CDROM (they still exist in great numbers), would place the CD in the drive, have the CDboot floppy, and still be in buisness. (This of course does not address those w/o a CDROM). -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 07:22:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05132 for freebsd-current-outgoing; Tue, 8 Dec 1998 07:22:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05127 for ; Tue, 8 Dec 1998 07:22:06 -0800 (PST) (envelope-from arno@heho.snv.jussieu.fr) Received: from hall.snv.jussieu.fr (hall.snv.jussieu.fr [134.157.37.2]) by shiva.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id QAA21918 for ; Tue, 8 Dec 1998 16:21:52 +0100 (CET) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.37.22]) by hall.snv.jussieu.fr (8.8.8/jtpda-5.2) with SMTP id QAA06881 for ; Tue, 8 Dec 1998 16:23:47 +0100 (CET) Received: by heho.snv.jussieu.fr (4.1/jf930126) at Tue, 8 Dec 98 16:21:50 +0100 To: current@FreeBSD.ORG Subject: Re: problems building world References: From: arno@heho.snv.jussieu.fr (Arno J. Klaassen) Date: 08 Dec 1998 16:21:47 +0100 In-Reply-To: Allan Saddi's message of Tue, 8 Dec 1998 05:38:30 -0800 (PST) Message-Id: Lines: 11 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > [.. ] sed: 1: "s!^#un-def!#undef!": bad flag in substitute command: 's' > > *** Error code 1 > > [ .. ] > I'll try out the previous revision... cvs co -r 1.10 usr.bin/sed/compile.c makes world compile happily. Arno To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 08:37:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15921 for freebsd-current-outgoing; Tue, 8 Dec 1998 08:37:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15887 for ; Tue, 8 Dec 1998 08:37:35 -0800 (PST) (envelope-from arno@heho.snv.jussieu.fr) Received: from hall.snv.jussieu.fr (hall.snv.jussieu.fr [134.157.37.2]) by shiva.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id RAA13025 for ; Tue, 8 Dec 1998 17:37:28 +0100 (CET) Received: from heho.snv.jussieu.fr (heho.snv.jussieu.fr [134.157.37.22]) by hall.snv.jussieu.fr (8.8.8/jtpda-5.2) with SMTP id RAA08383 for ; Tue, 8 Dec 1998 17:39:22 +0100 (CET) Received: by heho.snv.jussieu.fr (4.1/jf930126) at Tue, 8 Dec 98 17:37:26 +0100 To: current@FreeBSD.ORG Subject: devfs questions From: arno@heho.snv.jussieu.fr (Arno J. Klaassen) Date: 08 Dec 1998 17:37:26 +0100 Message-Id: Lines: 34 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, for the last couple of months, I use DEVFS without any problem on a current PII-SMP system. I added the next line to my fstab: devfs /dev devfs rw 0 0 I, however, have two questions related to devfs: - `mount' gives me the following two lines: devfs on dummy_mount (local) devfs on /dev (local) where is this dummy_mount coming from? - more seriously, I just happen to add a 6th disk to the system, and devfs just provides me with 5 da devices. How do I force devfs to provide for at least a da6 device as well? Thanx a lot in advance. Amicalement, Arno J. Klaassen -- INSERM U483 Creare, University Pierre et Marie Curie, Boite 23 9, quai Saint Bernard 75 252 Paris Cedex 5 arno@ccr.jussieu.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 09:11:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19890 for freebsd-current-outgoing; Tue, 8 Dec 1998 09:11:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19882 for ; Tue, 8 Dec 1998 09:11:56 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id KAA20166; Tue, 8 Dec 1998 10:11:51 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id KAA12785; Tue, 8 Dec 1998 10:11:51 -0700 Date: Tue, 8 Dec 1998 10:11:51 -0700 Message-Id: <199812081711.KAA12785@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Matt White Cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <2546225248.913079292@DEIMOS.REM.CMU.EDU> References: <2546225248.913079292@DEIMOS.REM.CMU.EDU> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is there any work in progress to integrate the PAO variant of FreeBSD back > into -current? If so, who do I talk to about helping? If not, is it > because of philisophical or manpower issues? In the past it was for technical reasons. The laptop support would negatively impact the 'standard' desktop support, and there are a number of large bugs in the PAO code that are 'worked around' by quick fixes instead of corrected the correct way. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 10:03:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23666 for freebsd-current-outgoing; Tue, 8 Dec 1998 10:03:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23658 for ; Tue, 8 Dec 1998 10:03:10 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id KAA23476; Tue, 8 Dec 1998 10:00:09 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdV23438; Tue Dec 8 18:00:06 1998 Date: Tue, 8 Dec 1998 09:59:36 -0800 (PST) From: Julian Elischer To: "Arno J. Klaassen" cc: current@FreeBSD.ORG Subject: Re: devfs questions 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 The dummy mount is the kernel's internal copy of the devfs tree. It is the bluebrint from which other copies are made when devfs is mounted.. you cannot get to it. The reason it is in the mount list is because the mounted devices are mounted from this blueprint, and it's superblocks will never be sync'd if teh filesystem from which it was mounted is not in the mount list. This is admittedly, a hack. When devfs is used to access the ROOT device, it get's more complicated but that code was deleted, so it's less important now. I don't know why the da driver doesn't produce a 6th da device. julian On 8 Dec 1998, Arno J. Klaassen wrote: > > Hi, > > for the last couple of months, I use DEVFS without any problem > on a current PII-SMP system. I added the next line to my fstab: > > devfs /dev devfs rw 0 0 > > I, however, have two questions related to devfs: > - `mount' gives me the following two lines: > > devfs on dummy_mount (local) > devfs on /dev (local) > > where is this dummy_mount coming from? > > - more seriously, I just happen to add a 6th disk to the system, and > devfs just provides me with 5 da devices. > How do I force devfs to provide for at least a da6 device as well? > > Thanx a lot in advance. > > Amicalement, > > Arno J. Klaassen > > -- > > INSERM U483 Creare, > University Pierre et Marie Curie, Boite 23 > 9, quai Saint Bernard > 75 252 Paris Cedex 5 > arno@ccr.jussieu.fr > > > 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 Dec 8 10:27:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25700 for freebsd-current-outgoing; Tue, 8 Dec 1998 10:27:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from labinfo.iet.unipi.it (labinfo.iet.unipi.it [131.114.9.5]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA25654 for ; Tue, 8 Dec 1998 10:26:20 -0800 (PST) (envelope-from luigi@labinfo.iet.unipi.it) Received: from localhost (luigi@localhost) by labinfo.iet.unipi.it (8.6.5/8.6.5) id RAA17170; Tue, 8 Dec 1998 17:18:29 +0100 From: Luigi Rizzo Message-Id: <199812081618.RAA17170@labinfo.iet.unipi.it> Subject: Re: dummynet + freebsd 3.0 To: camposr@MATRIX.COM.BR (Rodrigo Campos) Date: Tue, 8 Dec 1998 17:18:29 +0100 (MET) Cc: freebsd-current@FreeBSD.ORG In-Reply-To: from "Rodrigo Campos" at Dec 8, 98 09:56:19 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've applied the dn-3.0-981001.diffs patch to freebsd 3.0 release in order > to use dummynet. Ipfw and the kernel compiled just fine but when i try to > configure a pipe the following problem occured: > > # ipfw pipe 1 config bw 200kbit/s > ipfw: setsockopt(IP_DUMMYNET_CONFIGURE): Protocol not available i think you forgot something (e.g. update the files in /usr/include/netinet) luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 10:28:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25818 for freebsd-current-outgoing; Tue, 8 Dec 1998 10:28:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp05.wxs.nl (smtp05.wxs.nl [195.121.6.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25691 for ; Tue, 8 Dec 1998 10:27:32 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.56.93]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5BA4; Tue, 8 Dec 1998 19:24:20 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 08 Dec 1998 19:30:02 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: (Arno J. Klaassen) Subject: Re: problems building world Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-98 Arno J. Klaassen wrote: > >> > [.. ] sed: 1: "s!^#un-def!#undef!": bad flag in substitute command: 's' >> > *** Error code 1 >> > [ .. ] >> I'll try out the previous revision... > > cvs co -r 1.10 usr.bin/sed/compile.c > > makes world compile happily. True, but it remains a problem if it ain't fixed... Someone filed a PR yet? --- Jeroen Ruigrok van der Werven Pax vobiscum... asmodai(at)wxs.nl Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 11:40:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01455 for freebsd-current-outgoing; Tue, 8 Dec 1998 11:40:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01449; Tue, 8 Dec 1998 11:40:06 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA19045; Tue, 8 Dec 1998 11:38:45 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma019039; Tue, 8 Dec 98 11:38:16 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA02380; Tue, 8 Dec 1998 11:38:16 -0800 (PST) From: Archie Cobbs Message-Id: <199812081938.LAA02380@bubba.whistle.com> Subject: Re: FreeBSD 2.2.8-stable buildworld breaks... In-Reply-To: <199812081425.JAA25501@nimbus.superior.net> from Robert Blayzor at "Dec 8, 98 09:25:24 am" To: robert@superior.net (Robert Blayzor) Date: Tue, 8 Dec 1998 11:38:16 -0800 (PST) Cc: freebsd-hackers@FreeBSD.ORG, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Robert Blayzor writes: > sed: 1: "s,%whatis%,/usr/bin/wha ...": bad flag in substitute command: 's' > *** Error code 1 This is my fault.. I'm fixing it now.. -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 Dec 8 12:14:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA04676 for freebsd-current-outgoing; Tue, 8 Dec 1998 12:14:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA04666 for ; Tue, 8 Dec 1998 12:14:43 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id VAA01935; Tue, 8 Dec 1998 21:14:36 +0100 Message-ID: <366D88AB.57FB996F@we.lc.ehu.es> Date: Tue, 08 Dec 1998 21:14:35 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: how to install the new boot manager? Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just switched to 3.0 (great job, folks!). Now I would like to try the new boot manager, but I don't know how to install it in the boot sector. I tried to use "sysinstall", but when it asks for confirmation before installing the bootmgr, it says that it would install "BootEasy". -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 13:17:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10973 for freebsd-current-outgoing; Tue, 8 Dec 1998 13:17:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10967 for ; Tue, 8 Dec 1998 13:17:52 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA20769; Tue, 8 Dec 1998 13:16:03 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma020765; Tue, 8 Dec 98 13:15:37 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA03296; Tue, 8 Dec 1998 13:15:37 -0800 (PST) From: Archie Cobbs Message-Id: <199812082115.NAA03296@bubba.whistle.com> Subject: Re: problems building world In-Reply-To: from Jeroen Ruigrok/Asmodai at "Dec 8, 98 07:30:02 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Tue, 8 Dec 1998 13:15:37 -0800 (PST) Cc: arno@heho.snv.jussieu.fr, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Jeroen Ruigrok/Asmodai writes: > > cvs co -r 1.10 usr.bin/sed/compile.c > > > > makes world compile happily. > > True, but it remains a problem if it ain't fixed... > > Someone filed a PR yet? No need, I've got a fix and will check it in whenever a problem with the repository is fixed. In the meantime, use rev 1.10. Sorry about the breakage.. :-( -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 Dec 8 13:22:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11727 for freebsd-current-outgoing; Tue, 8 Dec 1998 13:22:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11716 for ; Tue, 8 Dec 1998 13:22:31 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40350>; Wed, 9 Dec 1998 08:21:29 +1100 Date: Wed, 9 Dec 1998 08:22:08 +1100 From: Peter Jeremy Subject: Re: panic: getnewbuf inconsistent EMPTY queue in 3.0-RELEASE To: freebsd-current@FreeBSD.ORG Message-Id: <98Dec9.082129est.40350@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri Dec 4 07:47:27 1998, I wrote: >I've just upgraded a Dell OptiPlex GXi from 32MB to 96MB. When I >increase MAXUSERS from 20 to 40 and SEMMNU from 350 to 1000, the >system panics `getnewbuf: inconsistent EMPTY queue, qindex=0' >immediately after the message `changing root device to wd0s1a'. >I don't have a crashdump because (as recommended) I use dumpon(8) >to specify the dumpdev, and the system doesn't get that far :-(. I've since tried dumping to both wd0b and da1b. In both cases, I get the message `device bad' (ie XXdump() returns ENXIO). With DDB enabled, I could get some tracebacks. These show that the problem is occurring when XXopen() calls dsopen() calls dsinit() calls geteblk() to read the master boot record. If the dumpdev is configured, it occurs inside setdumpdev(), otherwise it occurs inside vfs_mountroot(). Presumably the crashdump is failing because the dsopen() hadn't completed (and hence the disk device is not open). Presumably, the real problem is that the buffer cache is either uninitialised (possibly due to lack of KVM), or has been corrupted. Unfortunately, it is not practical to have the system off-air for an extended period whilst I poke around with DDB. Can anyone suggest which knobs to tweak to resolve the problem (or even where to look for the problem). Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 13:23:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA11764 for freebsd-current-outgoing; Tue, 8 Dec 1998 13:23:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11759 for ; Tue, 8 Dec 1998 13:23:01 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.58.182]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1A10; Tue, 8 Dec 1998 22:22:54 +0100 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812082115.NAA03296@bubba.whistle.com> Date: Tue, 08 Dec 1998 22:28:36 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Archie Cobbs Subject: Re: problems building world Cc: current@FreeBSD.ORG, arno@heho.snv.jussieu.fr Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-98 Archie Cobbs wrote: > Jeroen Ruigrok/Asmodai writes: >> > cvs co -r 1.10 usr.bin/sed/compile.c >> > >> > makes world compile happily. >> >> True, but it remains a problem if it ain't fixed... >> >> Someone filed a PR yet? > > No need, I've got a fix and will check it in whenever a problem > with the repository is fixed. In the meantime, use rev 1.10. > > Sorry about the breakage.. :-( We're only human =) I'm just glad it isn't me only... *pats Archie on his back* keep up the work mate... What was the problem with sed anyways? Haven't had time to compare the revisions... It seemed like the arguments didn't pass correctly. --- Jeroen Ruigrok van der Werven Pax vobiscum... asmodai(at)wxs.nl Network/Security Specialist BSD & picoBSD: The Power to Serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 13:35:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13482 for freebsd-current-outgoing; Tue, 8 Dec 1998 13:35:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-26-dbn.dial-up.net [196.34.155.90]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13475 for ; Tue, 8 Dec 1998 13:35:45 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id XAA09381; Tue, 8 Dec 1998 23:34:49 +0200 (SAT) From: Robert Nordier Message-Id: <199812082134.XAA09381@ceia.nordier.com> Subject: Re: how to install the new boot manager? In-Reply-To: <366D88AB.57FB996F@we.lc.ehu.es> from =?ISO-8859-1?Q?Jos=E9_M=AA_Alcaide?= at "Dec 8, 98 09:14:35 pm" To: jose@we.lc.ehu.es (José Mª Alcaide) Date: Tue, 8 Dec 1998 23:34:46 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 José Mª Alcaide wrote: > I have just switched to 3.0 (great job, folks!). Now I would like > to try the new boot manager, but I don't know how to install > it in the boot sector. I tried to use "sysinstall", but when it > asks for confirmation before installing the bootmgr, it says that > it would install "BootEasy". I think the -current version of sysinstall does in fact install boot0 (the new boot manager) while claiming to install booteasy. You can also use the simple utility at http://www.freebsd.org/~rnordier/boot0inst-1.0.2.tar.gz The new boot manager has recently been updated to work much more like booteasy (F5 support, etc), and also provides the following additional functionality: o Supports more than two hard drives (if your BIOS does) o Supports booting beyond cylinder 1023 (if your BIOS does, though many don't support this properly) o Recognizes a few more recent partitions types (including extended partition type 0xf) o Allows the following to be configured on installation: o Timeout value to automatic boot o Whether to use BIOS disk extensions o Whether to avoid updating the master boot record (but not yet supported by the installation utility) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 13:38:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13999 for freebsd-current-outgoing; Tue, 8 Dec 1998 13:38:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA13983 for ; Tue, 8 Dec 1998 13:38:25 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id NAA21230; Tue, 8 Dec 1998 13:37:16 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma021222; Tue, 8 Dec 98 13:37:05 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id NAA03685; Tue, 8 Dec 1998 13:37:04 -0800 (PST) From: Archie Cobbs Message-Id: <199812082137.NAA03685@bubba.whistle.com> Subject: Re: problems building world In-Reply-To: from Jeroen Ruigrok/Asmodai at "Dec 8, 98 10:28:36 pm" To: asmodai@wxs.nl (Jeroen Ruigrok/Asmodai) Date: Tue, 8 Dec 1998 13:37:04 -0800 (PST) Cc: current@FreeBSD.ORG, arno@heho.snv.jussieu.fr X-Mailer: ELM [version 2.4ME+ PL38 (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 Jeroen Ruigrok/Asmodai writes: > What was the problem with sed anyways? Haven't had time to compare the > revisions... It seemed like the arguments didn't pass correctly. The original bug was that if the substitution pattern was 4090 bytes long, sed would substitute nothing. And > 4090 bytes you'd get a core dump, or other weirdness. The way it reads things into statically sized buffers makes it confusing. My original bug fix was tripped up by this. Ah, it looks like the commit just went through, so try it out now. I'm still afraid there's probably more obscure bugs. This stuff needs a rewrite. Thanks, -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 Dec 8 15:02:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24624 for freebsd-current-outgoing; Tue, 8 Dec 1998 15:02:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opus.cts.cwu.edu (opus.cts.cwu.edu [198.104.92.71]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24614 for ; Tue, 8 Dec 1998 15:02:24 -0800 (PST) (envelope-from skynyrd@opus.cts.cwu.edu) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.9.1/8.9.1) with SMTP id PAA00964; Tue, 8 Dec 1998 15:02:16 -0800 (PST) Date: Tue, 8 Dec 1998 15:02:16 -0800 (PST) From: Chris Timmons To: Brett Taylor cc: freebsd-current@FreeBSD.ORG Subject: Re: make aout-to-world-build problem 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 Do you mean: make aout-to-elf-build make aout-to-elf-install ? I just successfully did it from a 2.2.7 system. Make sure you start with a real -current /usr/src and have plenty of room 300+MB for /usr/obj. -Chris On Tue, 8 Dec 1998, Brett Taylor wrote: > Hi, > > I've been trying to do a make aout-to-world-build w/ -current sources from > that I cvsup'ed on the 6th of Dec. I am attempting to upgrade from 2.2.8 > to -current. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 16:51:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07924 for freebsd-current-outgoing; Tue, 8 Dec 1998 16:51:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw.bby.com.au (ns.bby.com.au [192.83.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07919 for ; Tue, 8 Dec 1998 16:51:37 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id LAA21370 for ; Wed, 9 Dec 1998 11:51:30 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd021368; Wed Dec 9 00:51:26 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id LAA09328 for ; Wed, 9 Dec 1998 11:51:37 +1100 (EST) Message-Id: <199812090051.LAA09328@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: Another keyboard freeze Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Dec 1998 11:51:24 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.0-Current as at around 19981206 0000 UTC, running on HP KAYAK XA (PII-400). I previously reported odd keyboard freezes on the virtual console when I enabled softupdates. Since then I've been running with softupdates code in the kernel but not enabled for any partition. I just experienced another strange keyboard hang. I've got X3.3.3 installed and xdm enabled in /etc/ttys so at boot it pops up an XDM on vt7 but I can ctl-alt-Fn to get a login on other vts. Then something broke. Ctl-Alt-Fn stopped working (it beeped). Everything was working fine inside X, but I couldn't get out of it. Eventually, I killed the xdm and dropped back to vt0. At that point I was stuffed: "ordinary" keys produced no effect at all, and any of the Alt-Fn keys just produced a beep. Only way out was the three-finger salute. I'd like to be able to help sort this out if anyone can give me hints what to look for! Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 18:04:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15241 for freebsd-current-outgoing; Tue, 8 Dec 1998 18:04:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from jason02.u.washington.edu (jason02.u.washington.edu [140.142.76.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15235 for ; Tue, 8 Dec 1998 18:04:53 -0800 (PST) (envelope-from jcwells@u.washington.edu) Received: from saul3.u.washington.edu (root@saul3.u.washington.edu [140.142.83.1]) by jason02.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA23484; Tue, 8 Dec 1998 18:04:42 -0800 Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul3.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id SAA09392; Tue, 8 Dec 1998 18:04:41 -0800 (PST) Date: Tue, 8 Dec 1998 18:04:15 -0800 (PST) From: "Jason C. Wells" X-Sender: jason@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: Gregory Bond cc: current@FreeBSD.ORG Subject: Re: Another keyboard freeze In-Reply-To: <199812090051.LAA09328@melba.bby.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Dec 1998, Gregory Bond wrote: >Then something broke. Ctl-Alt-Fn stopped working (it beeped). Everything was >working fine inside X, but I couldn't get out of it. Eventually, I killed the >xdm and dropped back to vt0. At that point I was stuffed: "ordinary" keys >produced no effect at all, and any of the Alt-Fn keys just produced a beep. >Only way out was the three-finger salute. I don't know if "me toos" are appropriate on -current. I have observed this same behavior. It seems to occur when I switch between x and the console quickly. Catchya Later, | UW Mechanical Engineering Jason Wells | http://weber.u.washington.edu/~jcwells/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 18:47:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19495 for freebsd-current-outgoing; Tue, 8 Dec 1998 18:47:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from snark.wizard.com (snark.wizard.com [199.171.28.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19490 for ; Tue, 8 Dec 1998 18:47:51 -0800 (PST) (envelope-from ernst@snark.wizard.com) Received: (from ernst@localhost) by snark.wizard.com (8.9.0/8.9.0) id SAA09165; Tue, 8 Dec 1998 18:47:41 -0800 (PST) Date: Tue, 8 Dec 1998 18:47:41 -0800 (PST) From: "Richard B. Ernst" To: "Jason C. Wells" cc: Gregory Bond , current@FreeBSD.ORG Subject: Re: Another keyboard freeze 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 I've seen the same thing happen waaay back in 2.2.5 when I was just playing around with X. I haven't used it since then, but perhaps knowing there is a history will help. I had the exact symptoms. Keyboard "beep" when trying to Alt-Fn, and no keyboard control after shutting down X (Ctl-Alt-Bks?). I was able to telnet in, su and reboot instead of a Ctrl-Alt-Del, though. On Tue, 8 Dec 1998, Jason C. Wells wrote: :>On Wed, 9 Dec 1998, Gregory Bond wrote: :> :>>Then something broke. Ctl-Alt-Fn stopped working (it beeped). Everything was :>>working fine inside X, but I couldn't get out of it. Eventually, I killed the :>>xdm and dropped back to vt0. At that point I was stuffed: "ordinary" keys :>>produced no effect at all, and any of the Alt-Fn keys just produced a beep. :>>Only way out was the three-finger salute. :> :>I don't know if "me toos" are appropriate on -current. I have observed :>this same behavior. It seems to occur when I switch between x and the :>console quickly. :> :>Catchya Later, | UW Mechanical Engineering :>Jason Wells | http://weber.u.washington.edu/~jcwells/ :> :> :>To Unsubscribe: send mail to majordomo@FreeBSD.org :>with "unsubscribe freebsd-current" in the body of the message :> +--[ Richard B. Ernst ]--[ Las Vegas, NV ]--[ telnet://legendz.com 1234 ]--+ | "At the source of every error which is blamed on the computer you will | | find at least two human errors, including the error of blaming it on the | | computer." {Unknown} | +---[ http://www.wizard.com/~rbernst ]----------[ rbernst@wizard.com ]-----+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 19:18:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22203 for freebsd-current-outgoing; Tue, 8 Dec 1998 19:18:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22198 for ; Tue, 8 Dec 1998 19:18:28 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:zfhdJgiXWSmApvJrYdjWcWPa39CFoqt5@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.1/8.9.1) with ESMTP id MAA28621; Wed, 9 Dec 1998 12:17:49 +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 MAA12085; Wed, 9 Dec 1998 12:19:58 +0900 (JST) Message-Id: <199812090319.MAA12085@zodiac.mech.utsunomiya-u.ac.jp> To: Gregory Bond cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Another keyboard freeze In-reply-to: Your message of "Wed, 09 Dec 1998 11:51:24 +1100." <199812090051.LAA09328@melba.bby.com.au> References: <199812090051.LAA09328@melba.bby.com.au> Date: Wed, 09 Dec 1998 12:19:47 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >3.0-Current as at around 19981206 0000 UTC, running on HP KAYAK XA (PII-400). [...] >I just experienced another strange keyboard hang. I've got X3.3.3 installed >and xdm enabled in /etc/ttys so at boot it pops up an XDM on vt7 but I can >ctl-alt-Fn to get a login on other vts. > >Then something broke. Ctl-Alt-Fn stopped working (it beeped). Everything was >working fine inside X, but I couldn't get out of it. This happens when the X server either refuses to release the screen for some reason (this is unlikely), or fails to repond in defined manner during screen switching. The problem has been around for some time both in 3.0 and 2.X. The cause (bug) of the problem may be in the console driver, in the X server, or in both. The X server may be the culprit when you cannot switch away from the X session to a vty. In contrast, the console driver must be at fault if you are still unable to switch between vtys after the X server is terminated. >Eventually, I killed the >xdm and dropped back to vt0. At that point I was stuffed: "ordinary" keys >produced no effect at all, and any of the Alt-Fn keys just produced a beep. >Only way out was the three-finger salute. The one thing I know is that the XFree86 server somehow does not respond to the screen switching protocol at some point in the server reset. You may reprodude this by doing the following: 1. Run xdm on host A. Allow access from host B. 2. Start the X server on host B by: X -query A 3. You will see the login window (for host B) on host B. Login to host A via this. You are now in a X session on host A showing windows on host B's X server. 4. On host B, switch away from the X server to a vty by pressing Ctl-Alt-Fn. 5. Login to host A from host A's X server or host A's vty. 6. And kill the X session started in 3. This will make xdm to reset the X server on host B and diplay a new login window on host B. Observe the host B; the X server was in the background and you were seeing a vty on host B's display. But now, the X server has come to the foreground automatically! And it is very likely that you cannot switch away from this X server. You get beep sound when you press Ctl-Alt-Fn on host B. Time to review screen switching code in syscons and XFree86 yet again... Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 19:56:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25274 for freebsd-current-outgoing; Tue, 8 Dec 1998 19:56:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eterna.binary.net (eterna.binary.net [12.13.120.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25265 for ; Tue, 8 Dec 1998 19:56:52 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id VAA09594; Tue, 8 Dec 1998 21:55:48 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id VAA13646; Tue, 8 Dec 1998 21:56:46 -0600 (CST) Message-ID: <19981208225646.A12605@rtfm.net> Date: Tue, 8 Dec 1998 22:56:46 -0500 From: Nathan Dorfman To: Nate Williams , Matt White Cc: current@FreeBSD.ORG Subject: Re: PAO Integration? References: <2546225248.913079292@DEIMOS.REM.CMU.EDU> <199812081711.KAA12785@mt.sri.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812081711.KAA12785@mt.sri.com>; from Nate Williams on Tue, Dec 08, 1998 at 10:11:51AM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 08, 1998 at 10:11:51AM -0700, Nate Williams wrote: > > Is there any work in progress to integrate the PAO variant of FreeBSD back > > into -current? If so, who do I talk to about helping? If not, is it > > because of philisophical or manpower issues? > > In the past it was for technical reasons. The laptop support would > negatively impact the 'standard' desktop support, and there are a number > of large bugs in the PAO code that are 'worked around' by quick fixes > instead of corrected the correct way. On a related note, since there is only a package for 2.2, has anyone tried getting it to work on 3.0? I had to use the PAO-ready floppy to install 2.2.7 over my 3.0-R installation, after being unable to get any kind of activity with 3.0's stock PCMCIA. Works without a glitch with 2.2.7 and PAO. So has anyone tried to make the 2.2.7 PAO work under 3.0? > Nate ^^^^ -Nate :-) -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 8 23:01:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA11597 for freebsd-current-outgoing; Tue, 8 Dec 1998 23:01:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA11592 for ; Tue, 8 Dec 1998 23:01:38 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id SAA09365; Wed, 9 Dec 1998 18:01:31 +1100 Date: Wed, 9 Dec 1998 18:01:31 +1100 From: Bruce Evans Message-Id: <199812090701.SAA09365@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, peter.jeremy@auss2.alcatel.com.au Subject: Re: panic: getnewbuf inconsistent EMPTY queue in 3.0-RELEASE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>I've just upgraded a Dell OptiPlex GXi from 32MB to 96MB. When I >>increase MAXUSERS from 20 to 40 and SEMMNU from 350 to 1000, the >>system panics `getnewbuf: inconsistent EMPTY queue, qindex=0' >>immediately after the message `changing root device to wd0s1a'. >... >Presumably, the real problem is that the buffer cache is either >uninitialised (possibly due to lack of KVM), or has been corrupted. >Unfortunately, it is not practical to have the system off-air for an >extended period whilst I poke around with DDB. Can anyone suggest >which knobs to tweak to resolve the problem (or even where to look for >the problem). valloc() in machdep.c isn't robust. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 00:11:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18485 for freebsd-current-outgoing; Wed, 9 Dec 1998 00:11:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18480 for ; Wed, 9 Dec 1998 00:11:22 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id RAA01908; Wed, 9 Dec 1998 17:09:35 +0900 (JST) Message-Id: <199812090809.RAA01908@chandra.eatell.msr.prug.or.jp> To: Nathan Dorfman cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Tue, 08 Dec 1998 22:56:46 EST." <19981208225646.A12605@rtfm.net> Date: Wed, 09 Dec 1998 17:09:35 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > PAO. So has anyone tried to make the 2.2.7 PAO work under 3.0? PAO for 3.0-RELEASE(PAO3) is now under development in PAO team. Now status, PCIC and some drivers works. All SCSI card, these are not yet "CAM"ed, so not work. In PAO3, changed "shutdown power off". This problem is reported in PR i386/8638. When HALT, it should not power-off unconditional. It should be use "halt -p (and shutdown -x)". PAO for 2.2.8-RELEASE, first test version is probably to the public in a few weeks. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 Dec 9 01:39:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24291 for freebsd-current-outgoing; Wed, 9 Dec 1998 01:39:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA24281 for ; Wed, 9 Dec 1998 01:39:44 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es by polaris.we.lc.ehu.es (SMI-8.6/SMI-SVR4) id KAA02950; Wed, 9 Dec 1998 10:39:04 +0100 Message-ID: <366E4538.67B487F4@we.lc.ehu.es> Date: Wed, 09 Dec 1998 10:39:04 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. de Electricidad y Electrónica X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Robert Nordier CC: freebsd-current@FreeBSD.ORG Subject: Re: how to install the new boot manager? References: <199812082134.XAA09381@ceia.nordier.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Robert Nordier wrote: > > You can also use the simple utility at > > http://www.freebsd.org/~rnordier/boot0inst-1.0.2.tar.gz > Thanks! It works. And now also I know how to use disklabel(8) for the same thing (thanks to John Saunders). One little question: why isn't your bootinst utility integrated in 3.0-CURRENT? -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 01:52:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25313 for freebsd-current-outgoing; Wed, 9 Dec 1998 01:52:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25308 for ; Wed, 9 Dec 1998 01:52:13 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id EAA09046; Wed, 9 Dec 1998 04:52:07 -0500 (EST) Message-ID: <19981209045207.A3748@netmonger.net> Date: Wed, 9 Dec 1998 04:52:07 -0500 From: Christopher Masto To: freebsd-current@FreeBSD.ORG Subject: buildworld and PAM and login and stuff Mail-Followup-To: freebsd-current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just unsuspectingly did a "make buildworld" (first time in a couple of months) and it crapped out when it got to usr.bin/login.. couldn't find the PAM include files. Of course, a "make -DCLOBBER includes" fixed it. As there has been some mumbling recently about how to make the build process a bit less likely to produce a suprise failure in the middle, I figured I'd mention this. (Didn't see anything in the archives.) -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 02:06:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA26367 for freebsd-current-outgoing; Wed, 9 Dec 1998 02:06:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA26361 for ; Wed, 9 Dec 1998 02:06:12 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:+wI0T40uWyFddcQK44cdNe6MN+gagtqS@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id MAA12914; Wed, 9 Dec 1998 12:05:59 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:p0UKwg4QJKrLq8OuihzVUoSEr8jGyrZl@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id MAA88550; Wed, 9 Dec 1998 12:05:58 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812091005.MAA88550@greenpeace.grondar.za> To: NAKAGAWA Yoshihisa cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: Your message of " Wed, 09 Dec 1998 17:09:35 +0900." <199812090809.RAA01908@chandra.eatell.msr.prug.or.jp> References: <199812090809.RAA01908@chandra.eatell.msr.prug.or.jp> Date: Wed, 09 Dec 1998 12:05:57 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG NAKAGAWA Yoshihisa wrote: > In PAO3, changed "shutdown power off". This problem is reported in > PR i386/8638. When HALT, it should not power-off unconditional. It > should be use "halt -p (and shutdown -x)". FreeBSD 3.0 will turn off the laptop (on my Libretto 70) with shutdown -h. What is wrong with this? 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 Wed Dec 9 02:50:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29643 for freebsd-current-outgoing; Wed, 9 Dec 1998 02:50:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29638 for ; Wed, 9 Dec 1998 02:50:34 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id LAA01869; Wed, 9 Dec 1998 11:48:53 +0100 (CET) Message-ID: <19981209114852.A1828@foobar.franken.de> Date: Wed, 9 Dec 1998 11:48:52 +0100 From: Harold Gutch To: Robert Nordier , =?iso-8859-1?Q?Jos=E9_M=AA_Alcaide?= Cc: freebsd-current@FreeBSD.ORG Subject: Re: how to install the new boot manager? References: <366D88AB.57FB996F@we.lc.ehu.es> <199812082134.XAA09381@ceia.nordier.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812082134.XAA09381@ceia.nordier.com>; from Robert Nordier on Tue, Dec 08, 1998 at 11:34:46PM +0200 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 08, 1998 at 11:34:46PM +0200, Robert Nordier wrote: > The new boot manager has recently been updated to work much more > like booteasy (F5 support, etc), and also provides the following > additional functionality: > > o Recognizes a few more recent partitions types (including > extended partition type 0xf) > Which reminds me that the NetBSD-folks changed their partition ID from 165 to 166 a while ago, does boot0 recognize that too ? If it does not, please ask somebody from the NetBSD-camp, as I'm not 100% sure if it was 166 :) - they did change it some time 6-8 weeks ago though. -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 04:10:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08999 for freebsd-current-outgoing; Wed, 9 Dec 1998 04:10:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bfc.dk ([194.192.110.140]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA08992 for ; Wed, 9 Dec 1998 04:10:13 -0800 (PST) (envelope-from npe@bfc.dk) From: npe@bfc.dk Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566D5.004272B1 ; Wed, 9 Dec 1998 13:05:47 +0100 X-Lotus-FromDomain: BFC-DATA@BFC To: freebsd-current@FreeBSD.ORG Message-ID: <412566D5.004241BE.00@bfc.dk> Date: Wed, 9 Dec 1998 13:06:18 +0100 Subject: Re: New drivers and install floppy space 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 been away from the mailling list the latest days and missed the bootable cd discussion.. There's a software package called bootiso2 that can modify a iso image and allow bootable images up to apprx. 600 mb.. I think it is worth checking out. That idea of functionality is to take a harddrive image to bootfrom. Best Regards, Nicolai Petri - Denmark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 04:26:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA10066 for freebsd-current-outgoing; Wed, 9 Dec 1998 04:26:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA10061 for ; Wed, 9 Dec 1998 04:26:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id EAA20248; Wed, 9 Dec 1998 04:26:14 -0800 (PST) To: npe@bfc.dk cc: freebsd-current@FreeBSD.ORG Subject: Re: New drivers and install floppy space In-reply-to: Your message of "Wed, 09 Dec 1998 13:06:18 +0100." <412566D5.004241BE.00@bfc.dk> Date: Wed, 09 Dec 1998 04:26:13 -0800 Message-ID: <20244.913206373@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have been away from the mailling list the latest days and missed the > bootable cd discussion.. There's a software package called bootiso2 that This is free software? Where do you get it from? If it's not free software then it's not of much use to use since I've always built the FreeBSD release CDs using software which could be obtained by anyone. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 04:47:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA11713 for freebsd-current-outgoing; Wed, 9 Dec 1998 04:47:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bfc.dk ([194.192.110.140]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA11707 for ; Wed, 9 Dec 1998 04:47:23 -0800 (PST) (envelope-from npe@bfc.dk) From: npe@bfc.dk Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566D5.0045D88F ; Wed, 9 Dec 1998 13:42:54 +0100 X-Lotus-FromDomain: BFC-DATA@BFC To: "Jordan K. Hubbard" cc: freebsd-current@FreeBSD.ORG Message-ID: <412566D5.00458A0A.00@bfc.dk> Date: Wed, 9 Dec 1998 13:43:24 +0100 Subject: Re: New drivers and install floppy space 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 been away from the mailling list the latest days and missed the >> bootable cd discussion.. There's a software package called bootiso2 that >This is free software? Where do you get it from? If it's not free >software then it's not of much use to use since I've always built the >FreeBSD release CDs using software which could be obtained by anyone. Check this link http://www.cdpage.com/eltoritoi.html Hmm... I think is a non-profit license so the author may be very reasonable about the FreeBSD project using the software for distribution. I'm currently very busy right now so I'm unable to look closer at this at the moment.. But I have made a FreeBSD bootable cd with this software. >- Jordan Regards, Nicolai Petri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 06:29:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA20176 for freebsd-current-outgoing; Wed, 9 Dec 1998 06:29:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-29-dbn.dial-up.net [196.34.155.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA20041 for ; Wed, 9 Dec 1998 06:28:40 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id QAA01418; Wed, 9 Dec 1998 16:13:44 +0200 (SAT) From: Robert Nordier Message-Id: <199812091413.QAA01418@ceia.nordier.com> Subject: Re: how to install the new boot manager? In-Reply-To: <366E4538.67B487F4@we.lc.ehu.es> from =?ISO-8859-1?Q?Jos=E9_M=AA_Alcaide?= at "Dec 9, 98 10:39:04 am" To: jose@we.lc.ehu.es (José Mª Alcaide) Date: Wed, 9 Dec 1998 16:13:43 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 José Mª Alcaide wrote: > Robert Nordier wrote: > > > > You can also use the simple utility at > > > > http://www.freebsd.org/~rnordier/boot0inst-1.0.2.tar.gz > > > > Thanks! It works. And now also I know how to use disklabel(8) for > the same thing (thanks to John Saunders). I wasn't aware you could trick disklabel into doing that. The disklabel command is really meant to honor slices (PC partitions) transparently, and *shouldn't* write outside a slice. > > One little question: why isn't your bootinst utility integrated > in 3.0-CURRENT? I guess it could be. A DOS version would also be handy for folks who use Windows, which tends to overwrite the boot manager without asking. Ideally, one should be able to compile both FreeBSD and DOS versions from the same code (using Bruce's C compiler in ports, for instance). But so many more exciting things (like rearranging one's sock drawer, or cleaning out the washing machine lint filter) keep coming up, where DOS is involved. :-) -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 07:37:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25752 for freebsd-current-outgoing; Wed, 9 Dec 1998 07:37:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-53-dbn.dial-up.net [196.34.155.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25563 for ; Wed, 9 Dec 1998 07:36:57 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id QAA01450; Wed, 9 Dec 1998 16:23:49 +0200 (SAT) From: Robert Nordier Message-Id: <199812091423.QAA01450@ceia.nordier.com> Subject: Re: how to install the new boot manager? In-Reply-To: <19981209114852.A1828@foobar.franken.de> from Harold Gutch at "Dec 9, 98 11:48:52 am" To: logix@foobar.franken.de (Harold Gutch) Date: Wed, 9 Dec 1998 16:23:48 +0200 (SAT) Cc: rnordier@nordier.com, jose@we.lc.ehu.es, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (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 Harold Gutch wrote: > On Tue, Dec 08, 1998 at 11:34:46PM +0200, Robert Nordier wrote: > > The new boot manager has recently been updated to work much more > > like booteasy (F5 support, etc), and also provides the following > > additional functionality: > > > > o Recognizes a few more recent partitions types (including > > extended partition type 0xf) > > > Which reminds me that the NetBSD-folks changed their partition > ID from 165 to 166 a while ago, does boot0 recognize that too ? > If it does not, please ask somebody from the NetBSD-camp, as I'm > not 100% sure if it was 166 :) - they did change it some time > 6-8 weeks ago though. A type 166 is currently reported simply as "BSD". I think OpenBSD has been using 166 for a while. However, if NetBSD are using something different, I'm sure we can find space for that too. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 09:39:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA05647 for freebsd-current-outgoing; Wed, 9 Dec 1998 09:39:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gaylord.async.vt.edu (gaylord.async.vt.edu [128.173.18.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA05637 for ; Wed, 9 Dec 1998 09:39:41 -0800 (PST) (envelope-from gaylord@gaylord.async.vt.edu) Received: (from gaylord@localhost) by gaylord.async.vt.edu (8.9.1/8.9.1) id MAA00889 for freebsd-current@freebsd.org; Wed, 9 Dec 1998 12:39:10 -0500 (EST) (envelope-from gaylord) From: Clark Gaylord Message-Id: <199812091739.MAA00889@gaylord.async.vt.edu> Subject: problem with aout-to-elf ... TOOLDIR? To: freebsd-current@FreeBSD.ORG Date: Wed, 9 Dec 1998 12:39:10 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL31 (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 Following is the error message I get when I try make aout-to-elf. The problem is apparently because objformat is not in my path. This is because the PATH=TOOLDIR.... part of the Makefile sets the PATH. How should this work? Is there something I need to do to get TOOLDIR right or should I have stuff where it thinks I have stuff. I have cvsup'ed as of yesterday afternoon (EST), and I'm running 3.0 from make world (made with ftp'ed 3.0-RELEASE binary). There is likely some cruft in my src and obj trees from failed aout-to-elf/world builds before resorting to 3.0-RELEASE (then had 2.2-STABLE). Thank you. -- Clark K. Gaylord Blacksburg, Virginia USA cgaylord@vt.edu -------------------------------------------------------------- You are about to update the installed system (or the system that your DESTDIR points to) with the elf versions of everything, replacing the aout versions. You can type Ctrl-C to abort now, leaving just the aout world installed, or press return to start the second phase of the update. -------------------------------------------------------------- Return to continue or Ctrl-C to abort: -------------------------------------------------------------- Doing an elf installworld using the aout tools in the aout obj tree. -------------------------------------------------------------- objformat: not found "/big/FreeBSD-current/src/Makefile.inc1", line 972: warning: "objformat" returned non-zero status cd /big/FreeBSD-current/src; PATH=/usr/obj/aout/big/FreeBSD-current/src/tmp/sbin:/usr/obj/aout/big/FreeBSD-current/src/tmp/usr/sbin:/usr/obj/aout/big/FreeBSD-current/src/tmp/bin:/usr/obj/aout/big/FreeBSD-current/src/tmp/usr/bin BISON_SIMPLE=/usr/obj/aout/big/FreeBSD-current/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/aout/big/FreeBSD-current/src/tmp/usr/libexec:/usr/obj/aout/big/FreeBSD-current/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/elf/big/FreeBSD-current/src/tmp/usr/lib:/usr/obj/elf/big/FreeBSD-current/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/aout/big/FreeBSD-current/src/tmp/usr/lib LIBRARY_PATH=/usr/obj/elf/big/FreeBSD-current/src/tmp/usr/lib:/usr/obj/elf/big/FreeBSD-current/src/tmp/usr/lib OBJFORMAT_PATH=/usr/obj/aout/big/FreeBSD-current/src/tmp/usr/libexec CFLAGS="-nostdinc -O -pipe" make -f Makefile.inc1 reinstall objformat: not found "/big/FreeBSD-current/src/Makefile.inc1", line 972: warning: "objformat" returned non-zero status echo: not found *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** 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 Dec 9 11:40:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18655 for freebsd-current-outgoing; Wed, 9 Dec 1998 11:40:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18650 for ; Wed, 9 Dec 1998 11:40:11 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id LAA02276; Wed, 9 Dec 1998 11:40:05 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id LAA04762; Wed, 9 Dec 1998 11:40:04 -0800 (PST) (envelope-from jdp@polstra.com) Date: Wed, 9 Dec 1998 11:40:04 -0800 (PST) Message-Id: <199812091940.LAA04762@vashon.polstra.com> To: chris@netmonger.net Subject: Re: buildworld and PAM and login and stuff Newsgroups: polstra.freebsd.current In-Reply-To: <19981209045207.A3748@netmonger.net> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19981209045207.A3748@netmonger.net>, Christopher Masto wrote: > I just unsuspectingly did a "make buildworld" (first time in a couple > of months) and it crapped out when it got to usr.bin/login.. couldn't > find the PAM include files. Before importing it, I tested it with make buildworld on virgin systems. I can't imagine why it didn't work for you, if you followed standard procedure. There weren't any other reports of problems like that. Perhaps you had non-standard options in your make.conf file. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Nobody ever went broke underestimating the taste of the American public." -- H. L. Mencken To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 11:49:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19095 for freebsd-current-outgoing; Wed, 9 Dec 1998 11:49:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19090 for ; Wed, 9 Dec 1998 11:49:18 -0800 (PST) (envelope-from mike@sentex.net) Received: from marble.sentex.ca (marble.sentex.ca [199.212.134.2]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id OAA16436 for ; Wed, 9 Dec 1998 14:48:59 -0500 (EST) Received: from leaverite (leaverite.sentex.ca [209.112.4.36]) by marble.sentex.ca (8.8.8/8.8.8) with SMTP id OAA03043 for ; Wed, 9 Dec 1998 14:48:58 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19981209145124.00927bb0@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 09 Dec 1998 14:51:24 -0500 To: current@FreeBSD.ORG From: Mike Tancsa Subject: Strange pausing problem with Current... 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 started to experiment with current these past few weeks and have run into a strange problem.... I am assuming its hardware related, but I can quite pin it down where or why. I have 2 machines, one a Dual PII 450 with 512M RAM FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 ahc0: rev 0x00 int a irq 18 on pci0.10.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs The other is a CPU: Pentium II (quarter-micron) (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff> real memory = 134217728 (131072K bytes) wdc0 at 0x1f0-0x1f7 irq 14 flags 0xff8004 on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-4 wd0: 4104MB (8406720 sectors), 8896 cyls, 15 heads, 63 S/T, 512 B/S But I have also tried machine B with da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4149MB (8498506 512 byte sectors: 255H 63S/T 529C) Both are running FreeBSD current cvsup'd as of yesterday with sysctl -w vfs.ffs.doreallocblks=0 set. Now the problem... On machine B when there is some moderate disk acitivity, the machine gets quite sluggish and unresponsive. e.g. if I telnet to it, the login prompt takes quite a while to come up. Similarly, just typing 'w' from the prompt has about a 1 to 2 second delay. Machine A), although far more 'beefy' does not exhibt this behaviour, even in the middle of a make -j 32 world, or running a few copies of bonnie. Is it a hardware problem ? BIOS settings ? Any clues/suggestions as to what it may be ? Thanks, ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator (), noc@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 11:57:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20077 for freebsd-current-outgoing; Wed, 9 Dec 1998 11:57:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20069 for ; Wed, 9 Dec 1998 11:57:12 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id OAA16450; Wed, 9 Dec 1998 14:56:58 -0500 (EST) Message-ID: <19981209145657.B14732@netmonger.net> Date: Wed, 9 Dec 1998 14:56:57 -0500 From: Christopher Masto To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: buildworld and PAM and login and stuff References: <19981209045207.A3748@netmonger.net> <199812091940.LAA04762@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812091940.LAA04762@vashon.polstra.com>; from John Polstra on Wed, Dec 09, 1998 at 11:40:04AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 09, 1998 at 11:40:04AM -0800, John Polstra wrote: > In article <19981209045207.A3748@netmonger.net>, > Christopher Masto wrote: > > I just unsuspectingly did a "make buildworld" (first time in a couple > > of months) and it crapped out when it got to usr.bin/login.. couldn't > > find the PAM include files. > > Before importing it, I tested it with make buildworld on virgin > systems. I can't imagine why it didn't work for you, if you followed > standard procedure. There weren't any other reports of problems like > that. Perhaps you had non-standard options in your make.conf file. If there are nonstandard options that cause the build to fail in the middle, perhaps they should be documented or even detected. I believe that was the gist of the recent discussion. I was only pointing out a potential place where this may happen. In any case, the build completed when -DCLOBBER was used. Whatever my mistake was, it's gone now. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 12:18:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22036 for freebsd-current-outgoing; Wed, 9 Dec 1998 12:18:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eterna.binary.net (eterna.binary.net [12.13.120.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA22029 for ; Wed, 9 Dec 1998 12:18:34 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id OAA20256; Wed, 9 Dec 1998 14:17:29 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id OAA00625; Wed, 9 Dec 1998 14:18:27 -0600 (CST) Message-ID: <19981209151827.A266@rtfm.net> Date: Wed, 9 Dec 1998 15:18:27 -0500 From: Nathan Dorfman To: NAKAGAWA Yoshihisa Cc: current@FreeBSD.ORG Subject: Re: PAO Integration? References: <19981208225646.A12605@rtfm.net> <199812090809.RAA01908@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812090809.RAA01908@chandra.eatell.msr.prug.or.jp>; from NAKAGAWA Yoshihisa on Wed, Dec 09, 1998 at 05:09:35PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 09, 1998 at 05:09:35PM +0900, NAKAGAWA Yoshihisa wrote: > > PAO. So has anyone tried to make the 2.2.7 PAO work under 3.0? > > PAO for 3.0-RELEASE(PAO3) is now under development in PAO team. > Now status, PCIC and some drivers works. All SCSI card, these are > not yet "CAM"ed, so not work. > > In PAO3, changed "shutdown power off". This problem is reported in > PR i386/8638. When HALT, it should not power-off unconditional. It > should be use "halt -p (and shutdown -x)". > Do NE2000 Compatible PCMCIA cards work under PAO3, as it is now? If so, is the development snapshot available anywhere? > -- > NAKAGAWA, Yoshihisa > y-nakaga@nwsl.mesh.ad.jp > nakagawa@jp.FreeBSD.org -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 12:30:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA23419 for freebsd-current-outgoing; Wed, 9 Dec 1998 12:30:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA23410 for ; Wed, 9 Dec 1998 12:30:02 -0800 (PST) (envelope-from mike@sentex.net) Received: from marble.sentex.ca (marble.sentex.ca [199.212.134.2]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id PAA25744 for ; Wed, 9 Dec 1998 15:29:56 -0500 (EST) Received: from leaverite (leaverite.sentex.ca [209.112.4.36]) by marble.sentex.ca (8.8.8/8.8.8) with SMTP id PAA04165 for ; Wed, 9 Dec 1998 15:29:55 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19981209153221.012d7cd0@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 09 Dec 1998 15:32:21 -0500 To: current@FreeBSD.ORG From: Mike Tancsa Subject: Current ready for prime time web server ? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG One of our 2.2.STABLE server boxes with 250+ virtals is running into the FD_SETSIZE problem [Sun Dec 6 11:28:35 1998] [warn] [csd] filedescriptor (265) larger than FD_SETSIZE (256) found, you probably need to rebuild Apache with a larger FD_SETSIZE [Sun Dec 6 11:28:41 1998] [warn] [csd] filedescriptor (265) larger than FD_SETSIZE (256) found, you probably need to rebuild Apache with a larger FD_SETSIZE Reading the docs, Current does not have this problem. We have enjoyed great stability with stable... will a current current box show similar results, or should we wait a bit more ? Thanks, ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator (), noc@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 12:58:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26433 for freebsd-current-outgoing; Wed, 9 Dec 1998 12:58:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alive.znep.com (sense-sea-MegaSub-1-222.oz.net [216.39.144.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26426 for ; Wed, 9 Dec 1998 12:58:55 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id MAA08055; Wed, 9 Dec 1998 12:57:46 -0800 (PST) (envelope-from marcs@znep.com) Date: Wed, 9 Dec 1998 12:57:45 -0800 (PST) From: Marc Slemko To: Mike Tancsa cc: current@FreeBSD.ORG Subject: Re: Current ready for prime time web server ? In-Reply-To: <3.0.5.32.19981209153221.012d7cd0@staff.sentex.ca> 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, 9 Dec 1998, Mike Tancsa wrote: > > One of our 2.2.STABLE server boxes with 250+ virtals is running into the > FD_SETSIZE problem > > [Sun Dec 6 11:28:35 1998] [warn] [csd] filedescriptor (265) larger than > FD_SETSIZE (256) found, you probably need to rebuild > Apache with a larger FD_SETSIZE Well, why not rebuild Apache with a larger FD_SETSIZE like it says? How many descriptors are you using? How many access logs, how many error logs, and how many Listen directives do you have? I wouldn't really recommend using -current for production servers right now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 13:10:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27724 for freebsd-current-outgoing; Wed, 9 Dec 1998 13:10:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nagual.pp.ru (lsd.relcom.eu.net [193.125.27.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27716 for ; Wed, 9 Dec 1998 13:10:23 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.1/8.9.1) id AAA45383; Thu, 10 Dec 1998 00:09:57 +0300 (MSK) (envelope-from ache) Message-ID: <19981210000957.A44414@nagual.pp.ru> Date: Thu, 10 Dec 1998 00:09:57 +0300 From: "Andrey A. Chernov" To: Marc Slemko , Mike Tancsa Cc: current@FreeBSD.ORG Subject: Re: Current ready for prime time web server ? Mail-Followup-To: Marc Slemko , Mike Tancsa , current@FreeBSD.ORG References: <3.0.5.32.19981209153221.012d7cd0@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from marcs@znep.com on Wed, Dec 09, 1998 at 12:57:45PM -0800 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 09, 1998 at 12:57:45PM -0800, Marc Slemko wrote: > > FD_SETSIZE (256) found, you probably need to rebuild > > Apache with a larger FD_SETSIZE > > Well, why not rebuild Apache with a larger FD_SETSIZE like it says? -current understand any FD_SETSIZE you may want to use. BTW, better way for -current is switch to poll(), it not require rebuilding when you run out of defined descriptors. > I wouldn't really recommend using -current for production servers right > now. Hmm. My server under -current have 30000 raw hits per day without any problems. -- Andrey A. Chernov ache@null.net MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 13:15:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28230 for freebsd-current-outgoing; Wed, 9 Dec 1998 13:15:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alive.znep.com (sense-sea-MegaSub-1-222.oz.net [216.39.144.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28225 for ; Wed, 9 Dec 1998 13:15:50 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id NAA08165; Wed, 9 Dec 1998 13:14:44 -0800 (PST) (envelope-from marcs@znep.com) Date: Wed, 9 Dec 1998 13:14:43 -0800 (PST) From: Marc Slemko To: "Andrey A. Chernov" cc: Mike Tancsa , current@FreeBSD.ORG Subject: Re: Current ready for prime time web server ? In-Reply-To: <19981210000957.A44414@nagual.pp.ru> 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, 10 Dec 1998, Andrey A. Chernov wrote: > On Wed, Dec 09, 1998 at 12:57:45PM -0800, Marc Slemko wrote: > > > FD_SETSIZE (256) found, you probably need to rebuild > > > Apache with a larger FD_SETSIZE > > > > Well, why not rebuild Apache with a larger FD_SETSIZE like it says? > > -current understand any FD_SETSIZE you may want to use. And so does 2.2-stable. > > BTW, better way for -current is switch to poll(), it not require > rebuilding when you run out of defined descriptors. Except that the poll() that is currently in FreeBSD is a major PITA to use because doesn't comply with the relevant standards, since it doesn't give you any way to leave an empty lot using a negative descriptor. I submitted a PR with patch on this a month or two ago, but nothing has been done with it yet AFAIK. > > I wouldn't really recommend using -current for production servers right > > now. > > Hmm. My server under -current have 30000 raw hits per day without any > problems. 30000 hits isn't any significant volume of traffic. On top of that, a lot of the "production" part is on reliability and I'm not conviced that 3.0 is there yet. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 13:37:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01022 for freebsd-current-outgoing; Wed, 9 Dec 1998 13:37:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01006 for ; Wed, 9 Dec 1998 13:37:27 -0800 (PST) (envelope-from mike@sentex.net) Received: from marble.sentex.ca (marble.sentex.ca [199.212.134.2]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id QAA11437; Wed, 9 Dec 1998 16:37:21 -0500 (EST) Received: from leaverite (leaverite.sentex.ca [209.112.4.36]) by marble.sentex.ca (8.8.8/8.8.8) with SMTP id QAA05932; Wed, 9 Dec 1998 16:37:21 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19981209163946.01287930@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 09 Dec 1998 16:39:46 -0500 To: Marc Slemko From: Mike Tancsa Subject: Re: Current ready for prime time web server ? Cc: current@FreeBSD.ORG In-Reply-To: References: <3.0.5.32.19981209153221.012d7cd0@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:57 PM 12/9/98 -0800, you wrote: >On Wed, 9 Dec 1998, Mike Tancsa wrote: > >> >> One of our 2.2.STABLE server boxes with 250+ virtals is running into the >> FD_SETSIZE problem >> >> [Sun Dec 6 11:28:35 1998] [warn] [csd] filedescriptor (265) larger than >> FD_SETSIZE (256) found, you probably need to rebuild >> Apache with a larger FD_SETSIZE > >Well, why not rebuild Apache with a larger FD_SETSIZE like it says? Hi, Thanks for responding... I thought I had to rebuild STABLE as well no ? I am just worried that would introduce other problems. Also, other recent postings in questions suggest that this is not done easily. >How many descriptors are you using? coal# pstat -f | head 582/2088 open files >How many access logs, how many error >logs, and how many Listen directives do you have? coal# grep ^TransferLog httpd.conf | wc 201 402 8077 coal# grep ^ErrorLog httpd.conf | wc 201 402 7680 coal# grep ^TransferLog httpd.conf | sort | uniq | wc 199 398 7987 coal# grep ^ErrorLog httpd.conf | sort | uniq | wc 40 80 1714 >I wouldn't really recommend using -current for production servers right >now. Hmmm... I guess for my other machine I will have to revert to Stable with the CAM patches. The machine I want to put into production is a Dual CPU machine, but it will be more IO bound than CPU for now... Perhaps Current will be more stable in a couple of months and ready for prime time. The deployed machine is currently seeing about 500,000 raw hits a day (wc httpd-access.log) and has quite a few perl scripts... ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel 01.519.651.3400 Network Administrator (), noc@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 13:50:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02658 for freebsd-current-outgoing; Wed, 9 Dec 1998 13:50:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (sj-dsl-9-129-138.dspeed.net [209.249.129.138]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02653 for ; Wed, 9 Dec 1998 13:50:33 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.1/8.8.8) with ESMTP id NAA51668; Wed, 9 Dec 1998 13:49:51 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812092149.NAA51668@rah.star-gate.com> To: Marc Slemko cc: "Andrey A. Chernov" , Mike Tancsa , current@FreeBSD.ORG, hasty@rah.star-gate.com Subject: Re: Current ready for prime time web server ? In-reply-to: Your message of "Wed, 09 Dec 1998 13:14:43 PST." Date: Wed, 09 Dec 1998 13:49:51 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG May ask why do you think that 3.0 is not ready for prime time? Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 14:10:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA04826 for freebsd-current-outgoing; Wed, 9 Dec 1998 14:10:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA04821 for ; Wed, 9 Dec 1998 14:10:39 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id QAA29009; Wed, 9 Dec 1998 16:10:01 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma029001; Wed, 9 Dec 98 16:09:53 -0600 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.1/8.9.1) with ESMTP id QAA28014; Wed, 9 Dec 1998 16:09:52 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199812092209.QAA28014@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <3.0.5.32.19981209163946.01287930@staff.sentex.ca> References: <3.0.5.32.19981209153221.012d7cd0@staff.sentex.ca> <3.0.5.32.19981209163946.01287930@staff.sentex.ca> Subject: Re: Current ready for prime time web server ? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: Mike Tancsa cc: Marc Slemko , current@FreeBSD.ORG Date: Wed, 09 Dec 1998 16:09:52 -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 9 December 1998 at 16:39, Mike Tancsa wrote: [snip] > >Well, why not rebuild Apache with a larger FD_SETSIZE like it says? > > Hi, >Thanks for responding... I thought I had to rebuild STABLE as well no ? I > am just worried that would introduce other problems. Also, other recent > postings in questions suggest that this is not done easily. You need only recompile Apache, not the OS. It is quite easily done.. just define FD_SETSIZE before including . A reasonable way to do this is to add -DFD_SETSIZE=1024 or whatever to CFLAGS. Jacques Vidrine / n@nectar.com / nectar@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 Dec 9 14:31:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06433 for freebsd-current-outgoing; Wed, 9 Dec 1998 14:31:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06419 for ; Wed, 9 Dec 1998 14:31:51 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id RAA15935 for ; Wed, 9 Dec 1998 17:31:45 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.1/8.9.1) id RAA86198; Wed, 9 Dec 1998 17:31:37 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 9 Dec 1998 17:31:36 -0500 (EST) To: freebsd-current@FreeBSD.ORG Subject: increased UDP latencies in -current X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13934.54777.633326.333061@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the process of doing some Myrinet benchmarks, I noticed that UDP latencies have increased markedly after upgrading from 2.2.5-stable to 3.0-current. On identical machines (300Mhz PII, 440lx chipset, same memory configuration) a kernel built from circa Jan. 18, 1998 2.2-stable sources yields UDP small message latencies about 10% better than a 3.0-current kernel using both the netperf UDP_RR test & HBench-OS's lat_udp. A 3.0 kernel from mid July yields slightly better results than a recent -current, but not by much. Tests run across the loopback interface for a 1 byte message: RR/sec via us/msg via OS rev netperf(1) HBench-OS(2) --------- -------- ---------- 2.2.5 15502.17 56.6806 3.0 (July 7) 13787.90 64.9367 3.0 (Dec 1) 13656.60 66.5090 (1)netperf2.1pl3, run via netperf -tUDP_RR -l60 -i 10,2 -Hlocalhost (2)hbench: lat_udp.c,v 1.4 1997/06/27 00:33:58 abrown Exp $, run as lat_udp 10000 localhost Running tests between machines with real hardware (full duplex 100Mb ethernet over the fxp interface, as well as Myrinet/Trapeze) mirrors these differences. Larger messages (tried 1k and 8k) also mirror these results (2.2.5 is ~10us faster). TCP latencies appear to be nearly identical between OS revisions, as do UDP and TCP bandwidths. Does anybody know where the increased UDP latency is coming from? I initially thought the culprit might be no longer moving pcb's to the head of the hash chain in in_pcblookup_hash (removed in in_pcb.c,1.38). I tried replacing this code, but it doesn't make much of a difference... I suppose its not terribly important in the scheme of things, but it would be interesting to know why things are slower. ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 15:30:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12438 for freebsd-current-outgoing; Wed, 9 Dec 1998 15:30:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ozz.etrust.ru ([195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12427 for ; Wed, 9 Dec 1998 15:30:01 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id CAA48502 for ; Thu, 10 Dec 1998 02:22:48 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Thu, 10 Dec 1998 02:22:47 +0300 (MSK) From: oZZ!!! To: current@FreeBSD.ORG Subject: zlib-1.1.3 ??? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! What about of new version of zlib??? why it not in -current source-tree ??? (now in my -current zlib-1.1.1) Rgdz, ïÓÏËÉÎ óÅÒÇÅÊ aka oZZ, osa@freebsd.org.ru FreeBSD - äÁ ÐÒÅÂÕÄÅÔ Ó ÎÁÍÉ ÓÉÌÁ! http://www.freebsd.org.ru áÓÓÏÃÉÁÃÉÑ ÒÕÓÓËÏÑÚÙÞÎÙÈ ÐÏÌØÚÏ×ÁÔÅÌÅÊ FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 15:56:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15289 for freebsd-current-outgoing; Wed, 9 Dec 1998 15:56:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d5.dialup.hilink.com.au [203.2.144.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15283 for ; Wed, 9 Dec 1998 15:56:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01185; Wed, 9 Dec 1998 15:54:32 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812092354.PAA01185@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nathan Dorfman cc: NAKAGAWA Yoshihisa , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 09 Dec 1998 15:18:27 EST." <19981209151827.A266@rtfm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Dec 1998 15:54:30 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Do NE2000 Compatible PCMCIA cards work under PAO3, as it is now? > If so, is the development snapshot available anywhere? They work fine under stock 2.2 and 3.0 (this message is being sent using one). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Wed Dec 9 16:25:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20488 for freebsd-current-outgoing; Wed, 9 Dec 1998 16:25:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from eterna.binary.net (eterna.binary.net [12.13.120.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20483 for ; Wed, 9 Dec 1998 16:25:11 -0800 (PST) (envelope-from nathan@rtfm.net) Received: from matrix.binary.net (nathan@matrix.binary.net [12.13.120.2]) by eterna.binary.net (8.9.1a/8.9.1) with ESMTP id SAA25249; Wed, 9 Dec 1998 18:24:01 -0600 (CST) Received: (from nathan@localhost) by matrix.binary.net (8.9.1a/8.9.1) id SAA19541; Wed, 9 Dec 1998 18:24:59 -0600 (CST) Message-ID: <19981209192459.A18996@rtfm.net> Date: Wed, 9 Dec 1998 19:24:59 -0500 From: Nathan Dorfman To: Mike Smith Cc: NAKAGAWA Yoshihisa , current@FreeBSD.ORG Subject: Re: PAO Integration? References: <19981209151827.A266@rtfm.net> <199812092354.PAA01185@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812092354.PAA01185@dingo.cdrom.com>; from Mike Smith on Wed, Dec 09, 1998 at 03:54:30PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 09, 1998 at 03:54:30PM -0800, Mike Smith wrote: > > > > Do NE2000 Compatible PCMCIA cards work under PAO3, as it is now? > > If so, is the development snapshot available anywhere? > > They work fine under stock 2.2 and 3.0 (this message is being sent > using one). I tried with no success whatsoever to get this setup to work with 3.0-R. The no-brand card didn't even have an entry in 3.0-R's pccard.conf.sample. Worked fine with PAO-2.2.7, all I had to do was tell it not to use IRQs 1-10. Also, the 3.0-R pcic would come up at IRQ 5, which is wrong. Attempts to enable the card after inferring pccard.conf values from pccardc dumpcis output would result in the box freezing up with the slot light on until I eject the card. Inserting it back again had no effect, I had to either reboot, or set PCIC_RESUME_RESET on and zzz, then wake up. Can I tell 3.0's pcmcia to force irq 9? If so, I could try again with the pccard.conf entries from PAO's file. > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > -- ________________ ___________________________________________ / Nathan Dorfman \ / "`IE4 brings the web to UNIX'? *laughing* / nathan@rtfm.net \/ Isn't that similar to Ronald McDonald bringing / finger for PGP key \ religion to the pope?" -Jamie Bowden To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 17:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28774 for freebsd-current-outgoing; Wed, 9 Dec 1998 17:22:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28769 for ; Wed, 9 Dec 1998 17:22:56 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA27790; Wed, 9 Dec 1998 17:22:12 -0800 (PST) To: Christopher Masto cc: John Polstra , current@FreeBSD.ORG Subject: Re: buildworld and PAM and login and stuff In-reply-to: Your message of "Wed, 09 Dec 1998 14:56:57 EST." <19981209145657.B14732@netmonger.net> Date: Wed, 09 Dec 1998 17:22:12 -0800 Message-ID: <27787.913252932@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If there are nonstandard options that cause the build to fail in the > middle, perhaps they should be documented or even detected. I believe How? There is a huge array of possible ways in which to hang yourself here and I'm almost certain it would be impossible to enumerate, let along detect, them all. How do you detect that someone has passed in bogus CFLAGS, for example? Or set the optimization too high? All of those things can cause the build to fail and are only examples of some of the less subtle ways of doing it. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 17:24:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29030 for freebsd-current-outgoing; Wed, 9 Dec 1998 17:24:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.its.rpi.edu (mail1.its.rpi.edu [128.113.100.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29022 for ; Wed, 9 Dec 1998 17:24:56 -0800 (PST) (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.8.8/8.8.6) with ESMTP id UAA159242; Wed, 9 Dec 1998 20:25:33 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: drosih@pop1.rpi.edu Message-Id: In-Reply-To: <199812092149.NAA51668@rah.star-gate.com> References: Your message of "Wed, 09 Dec 1998 13:14:43 PST." Date: Wed, 9 Dec 1998 20:24:50 -0500 To: Amancio Hasty , Marc Slemko From: Garance A Drosihn Subject: Re: Current ready for prime time web server ? Cc: Mike Tancsa , current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:49 PM -0800 12/9/98, Amancio Hasty wrote: > May ask why do you think that 3.0 is not ready for prime time? Isn't true that -- *by definition* -- the freebsd-current tree is not *recommended* for production servers? Not now, not ever? Marc merely said that that he would not really recommend using -current for production servers right now. He isn't necessarily casting aspersions on 3.0. I assumed that he was just stating the official freebsd position. Now, there are things in current which could be very nice to have on a web server, including a production web server. I do use an earlier snapshot of 3.0 for a production (non-web) server I have, for instance. But for the problem as described, it does seem that simply recompiling apache was the best recommendation. --- Garance Alistair Drosehn = gad@eclipse.its.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 Wed Dec 9 17:33:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00240 for freebsd-current-outgoing; Wed, 9 Dec 1998 17:33:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (kenya-158.ppp.hooked.net [206.169.227.158]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00215 for ; Wed, 9 Dec 1998 17:33:40 -0800 (PST) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost) by zippy.dyn.ml.org (8.9.1/8.8.8) with ESMTP id RAA77852; Wed, 9 Dec 1998 17:36:29 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Wed, 9 Dec 1998 17:36:28 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: "Jordan K. Hubbard" cc: Christopher Masto , John Polstra , current@FreeBSD.ORG Subject: Re: buildworld and PAM and login and stuff In-Reply-To: <27787.913252932@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Dec 1998, Jordan K. Hubbard wrote: > > If there are nonstandard options that cause the build to fail in the > > middle, perhaps they should be documented or even detected. I believe > > How? There is a huge array of possible ways in which to hang yourself > here and I'm almost certain it would be impossible to enumerate, let > along detect, them all. Just playing devil's advocate: > How do you detect that someone has passed in bogus CFLAGS Try out the compiler / CFLAGS combo and see what happens (with a small test program of course) >, for example? Or set the optimization too high? Assuming gcc is being used, what about having awk feed each argument of CFLAGS to a grep O|grep -v O2? A regexp might be more suited... > All of those things can cause the build to fail and are only examples > of some of the less subtle ways of doing it. If you really wanted to I'm sure you could come up with some way to check all of this, but doesn't your sock drawer need cleaning? ;) - alex | "Contrary to popular belief, penguins are not the salvation of modern | | technology. Neither do they throw parties for the urban proletariat." | | Powered by FreeBSD 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 Wed Dec 9 17:41:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01424 for freebsd-current-outgoing; Wed, 9 Dec 1998 17:41:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01416 for ; Wed, 9 Dec 1998 17:41:42 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.1/8.8.7) with ESMTP id UAA01033 for ; Wed, 9 Dec 1998 20:42:43 -0500 (EST) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Wed, 9 Dec 1998 20:42:42 -0500 (EST) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: current@FreeBSD.ORG Subject: ide_pci.c 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 just thought that someone in here should know this: I have a generic dual PCI IDE controller. It can support up to 4 devices. I have 2 hard drives on the first controller, and an ATAPI cdrom drive on the second. The problem is that when it boots, it says that the controller is simplex, and that there is no dma on the secondary channel, and then when it gets down to the ISA configuration, it won't find anything on the second controller. The only way I could fix it is to go to /usr/src/sys/i386/conf/files.i386 and delete the line that specifies ide_pci.c That solved the problem, and I can now use my CD-ROM drive, but I thought that you guys should know about the problem. Thanks. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 17:44:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01890 for freebsd-current-outgoing; Wed, 9 Dec 1998 17:44:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alive.znep.com (sense-sea-MegaSub-1-222.oz.net [216.39.144.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA01885 for ; Wed, 9 Dec 1998 17:44:01 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id RAA08839; Wed, 9 Dec 1998 17:42:53 -0800 (PST) (envelope-from marcs@znep.com) Date: Wed, 9 Dec 1998 17:42:52 -0800 (PST) From: Marc Slemko To: Jacques Vidrine cc: Mike Tancsa , current@FreeBSD.ORG Subject: Re: Current ready for prime time web server ? In-Reply-To: <199812092209.QAA28014@spawn.nectar.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Dec 1998, Jacques Vidrine wrote: > On 9 December 1998 at 16:39, Mike Tancsa wrote: > [snip] > > >Well, why not rebuild Apache with a larger FD_SETSIZE like it says? > > > > Hi, > >Thanks for responding... I thought I had to rebuild STABLE as well no ? I > > am just worried that would introduce other problems. Also, other recent > > postings in questions suggest that this is not done easily. > > You need only recompile Apache, not the OS. It is quite easily done.. > just define FD_SETSIZE before including . A reasonable Exactly. In Apache's case, it will reserve a few low descriptors for other libraries that may need them and shouldn't be calling any library functions that will end up with high numbered descriptors and that can't handle them. The situation is the same on 3.0, only the default is 1024 or something like that which is more reasonable. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 17:51:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02848 for freebsd-current-outgoing; Wed, 9 Dec 1998 17:51:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alive.znep.com (sense-sea-MegaSub-1-222.oz.net [216.39.144.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02828 for ; Wed, 9 Dec 1998 17:50:57 -0800 (PST) (envelope-from marcs@znep.com) Received: from localhost (marcs@localhost) by alive.znep.com (8.9.1/8.9.1) with ESMTP id RAA08856; Wed, 9 Dec 1998 17:49:54 -0800 (PST) (envelope-from marcs@znep.com) Date: Wed, 9 Dec 1998 17:49:54 -0800 (PST) From: Marc Slemko To: Amancio Hasty cc: current@FreeBSD.ORG Subject: Re: Current ready for prime time web server ? In-Reply-To: <199812092149.NAA51668@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 9 Dec 1998, Amancio Hasty wrote: > May ask why do you think that 3.0 is not ready for prime time? A few things. First, the big statement saying: This is our first release of 3.0-CURRENT and is aimed primarily at early adopters and developers. Second, the massive number of changes that were rushed into the tree soon before 3.0 came out. Things take time to settle. There are no specifics really. Well, some of the things new in 3.0 still need more work but that alone shouldn't discourage people who only need to use things that already were in 2.x. Third, I'm not aware of the dying daemons thing being fixed. I don't like it when programs randomly start dying due to vm wackyness or whatever it is. While the failure mode that appears to be typical may not normally happen on many servers, I wouldn't want to put my faith in that. My 3.0 workstation has seen this, and it has prevented me from accessing it remotely. Good thing it isn't a server. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 17:51:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02878 for freebsd-current-outgoing; Wed, 9 Dec 1998 17:51:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02873 for ; Wed, 9 Dec 1998 17:51:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA28076; Wed, 9 Dec 1998 17:50:30 -0800 (PST) To: Alex Zepeda cc: Christopher Masto , John Polstra , current@FreeBSD.ORG Subject: Re: buildworld and PAM and login and stuff In-reply-to: Your message of "Wed, 09 Dec 1998 17:36:28 PST." Date: Wed, 09 Dec 1998 17:50:30 -0800 Message-ID: <28073.913254630@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Just playing devil's advocate: Like I said, those are only the unsubtle ones. If you're able to devise a set of test cases which don't add 3 hours to the buildworld time and catch potential abuses for all the various knobs in /etc/make.conf, I'd be the first to buy you a case of beer in sheer admiration. Needless to say, I also consider it a pretty safe bet. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 18:05:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05064 for freebsd-current-outgoing; Wed, 9 Dec 1998 18:05:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05057 for ; Wed, 9 Dec 1998 18:05:36 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id NAA12509; Thu, 10 Dec 1998 13:16:03 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812100216.NAA12509@cimlogic.com.au> Subject: Re: buildworld and PAM and login and stuff In-Reply-To: <28073.913254630@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 9, 98 05:50:30 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Thu, 10 Dec 1998 13:16:02 +1100 (EST) Cc: current@FreeBSD.ORG 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 Jordan K. Hubbard wrote: > > Just playing devil's advocate: > > Like I said, those are only the unsubtle ones. If you're able to > devise a set of test cases which don't add 3 hours to the buildworld > time and catch potential abuses for all the various knobs in > /etc/make.conf, I'd be the first to buy you a case of beer in sheer > admiration. > > Needless to say, I also consider it a pretty safe bet. :-) Yup. For those who think it _is_ practical to devise a set of test cases, consider this: If I set CFLAGS in make.conf to -pipe on alpha (so that the -O is missing), and I do a `make world' that completes without error, what did I mess up? Anyone know? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 18:22:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07720 for freebsd-current-outgoing; Wed, 9 Dec 1998 18:22:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07659 for ; Wed, 9 Dec 1998 18:22:00 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id VAA12698; Wed, 9 Dec 1998 21:21:47 -0500 (EST) Message-ID: <19981209212147.A12267@netmonger.net> Date: Wed, 9 Dec 1998 21:21:47 -0500 From: Christopher Masto To: "Jordan K. Hubbard" Cc: John Polstra , current@FreeBSD.ORG Subject: Re: buildworld and PAM and login and stuff References: <19981209145657.B14732@netmonger.net> <27787.913252932@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <27787.913252932@zippy.cdrom.com>; from Jordan K. Hubbard on Wed, Dec 09, 1998 at 05:22:12PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 09, 1998 at 05:22:12PM -0800, Jordan K. Hubbard wrote: > > If there are nonstandard options that cause the build to fail in the > > middle, perhaps they should be documented or even detected. I believe > > How? There is a huge array of possible ways in which to hang yourself > here and I'm almost certain it would be impossible to enumerate, let > along detect, them all. How do you detect that someone has passed in > bogus CFLAGS, for example? Or set the optimization too high? All of > those things can cause the build to fail and are only examples of some > of the less subtle ways of doing it. Well heck, if you know that the optimization shouldn't be changed, then put a comment in /etc/make.conf, or better yet, have make buildworld check to see if CFLAGS isn't set to the "officially supported" value and tell the user. I futz with my make.conf because it's there and because it says things like "do this for better performance". Although I know better when building the world, I may have forgotten. I'm not suggesting artificial intelligence, just things like "if you don't build Perl, foo will not work", so that people don't innocently change something that bites them in the ass. In any case, this is not an original idea of mine. I just tried to help out by pointing out something that may have been a problem. I am inclined to believe that it was some weird aspect of my build environment now, so just forget about it. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 18:23:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08011 for freebsd-current-outgoing; Wed, 9 Dec 1998 18:23:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from st-lcremean.tidalwave.net (st-lcremean.tidalwave.net [208.213.203.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08003 for ; Wed, 9 Dec 1998 18:23:27 -0800 (PST) (envelope-from lee@st-lcremean.tidalwave.net) Received: (from lee@localhost) by st-lcremean.tidalwave.net (8.9.1/8.8.8) id VAA83000; Wed, 9 Dec 1998 21:23:39 -0500 (EST) (envelope-from lee) Message-ID: <19981209212339.A82984@tidalwave.net> Date: Wed, 9 Dec 1998 21:23:39 -0500 From: Lee Cremeans To: Kenneth Wayne Culver , current@FreeBSD.ORG Subject: Re: ide_pci.c Reply-To: lcremean@tidalwave.net References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kenneth Wayne Culver on Wed, Dec 09, 1998 at 08:42:42PM -0500 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 09, 1998 at 08:42:42PM -0500, Kenneth Wayne Culver wrote: > I just thought that someone in here should know this: I have a generic > dual PCI IDE controller. It can support up to 4 devices. I have 2 hard > drives on the first controller, and an ATAPI cdrom drive on the second. > The problem is that when it boots, it says that the controller is simplex, > and that there is no dma on the secondary channel, and then when it gets > down to the ISA configuration, it won't find anything on the second > controller. The only way I could fix it is to go to > /usr/src/sys/i386/conf/files.i386 and delete the line that specifies > ide_pci.c What chipset is on your motherboard, per chance? I have a motherboard with an Acer Aladdin IV+ chipset, and unless I put "options DISABLE_PCI_IDE" in my kernel config, my second channel will not work. I've been meaning to look into adding native support for the Aladdin's PCI IDE controller for a while now, but I haven't had the time (or made the time, really) to do the work. -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on DALnet and WTnet)| | lcremean@tidalwave.net| http://st-lcremean.tidalwave.net | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 18:27:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08467 for freebsd-current-outgoing; Wed, 9 Dec 1998 18:27:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08451 for ; Wed, 9 Dec 1998 18:27:33 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id LAA02369; Thu, 10 Dec 1998 11:25:40 +0900 (JST) Message-Id: <199812100225.LAA02369@chandra.eatell.msr.prug.or.jp> To: Nathan Dorfman cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 09 Dec 1998 15:18:27 EST." <19981209151827.A266@rtfm.net> Date: Thu, 10 Dec 1998 11:25:39 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Do NE2000 Compatible PCMCIA cards work under PAO3, as it is now? Yes, it works fine. > If so, is the development snapshot available anywhere? Now, not yet made "tar"ed snapshot kit, but you can get via CVSup. Example of CVSup file is: *default host=jaz.jp.FreeBSD.org *default base=/some/where/you/want *default prefix=/some/where/you/want/prefix *default release=cvs *default delete use-rel-suffix # collections jp-pao3 -- By the way, pao228 first snapshot is available. ftp://jaz.jp.FreeBSD.org/pub/FreeBSD-jp/PAO/snap/PAO-freebsd228-981208-snap.tar.gz -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 Dec 9 18:32:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09543 for freebsd-current-outgoing; Wed, 9 Dec 1998 18:32:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09538 for ; Wed, 9 Dec 1998 18:32:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id SAA28472; Wed, 9 Dec 1998 18:32:13 -0800 (PST) To: Christopher Masto cc: John Polstra , current@FreeBSD.ORG Subject: Re: buildworld and PAM and login and stuff In-reply-to: Your message of "Wed, 09 Dec 1998 21:21:47 EST." <19981209212147.A12267@netmonger.net> Date: Wed, 09 Dec 1998 18:32:13 -0800 Message-ID: <28468.913257133@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well heck, if you know that the optimization shouldn't be changed, > then put a comment in /etc/make.conf, or better yet, have make > buildworld check to see if CFLAGS isn't set to the "officially > supported" value and tell the user. I futz with my make.conf because But it's not true for all architectures and, even so, is only ONE example of potential abuse. My best recommendation based on everything you've said so far can only be to tell you simply not to mess with the contents of /etc/make.conf or any other configuration file in /etc which you don't fully understand. We picked good defaults specifically so that most people wouldn't have to mess with these files at all as a general rule, and if they DO mess with them we expect them to know exactly what they're doing. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 19:06:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA14875 for freebsd-current-outgoing; Wed, 9 Dec 1998 19:06:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA14869 for ; Wed, 9 Dec 1998 19:06:33 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id WAA01934 for ; Wed, 9 Dec 1998 22:06:26 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA17481; Wed, 9 Dec 1998 22:06:25 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id WAA16498 for freebsd-current@freebsd.org; Wed, 9 Dec 1998 22:06:25 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812100306.WAA16498@bb01f39.unx.sas.com> Subject: Nit: Just what should objdir be? To: freebsd-current@FreeBSD.ORG Date: Wed, 9 Dec 1998 22:06:25 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (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 folks, I was bitten by a surprise case of 'which objdir are you using?' Pick a program, let's say sed... :-) Hi archie! cd /usr/src/usr.bin/sed && make The objects are put into /usr/obj/usr/src/usr.bin/sed. But wait, not all the objects rebuilt, and the linker is complaining about unrecognized file formats! Well, the default object tree was never cleaned out when the aout-elf conversion took place. Well, I blew the tree away, and now objects are getting written into the src dir. What I really want is the default to be /usr/obj/elf/usr/... (those do happen to be the objects linked into my live system you know), or /usr/obj/aout/usr/... if the current objformat is aout... So the question is: Should we update make to have the default objdir match the objformat that is currently set? Should we leave /usr/obj/usr alone? (I don't like this). Of course, maybe this is already fixed and I missed a config file update or something... :-) comments, critiques, and stupid user invectives are most welcome! Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 19:11:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15486 for freebsd-current-outgoing; Wed, 9 Dec 1998 19:11:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15472 for ; Wed, 9 Dec 1998 19:11:23 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id WAA15908; Wed, 9 Dec 1998 22:11:09 -0500 (EST) Message-ID: <19981209221109.A14004@netmonger.net> Date: Wed, 9 Dec 1998 22:11:09 -0500 From: Christopher Masto To: "Jordan K. Hubbard" Cc: John Polstra , current@FreeBSD.ORG Subject: Re: buildworld and PAM and login and stuff References: <19981209212147.A12267@netmonger.net> <28468.913257133@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <28468.913257133@zippy.cdrom.com>; from Jordan K. Hubbard on Wed, Dec 09, 1998 at 06:32:13PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 09, 1998 at 06:32:13PM -0800, Jordan K. Hubbard wrote: > > Well heck, if you know that the optimization shouldn't be changed, > > then put a comment in /etc/make.conf, or better yet, have make > > buildworld check to see if CFLAGS isn't set to the "officially > > supported" value and tell the user. I futz with my make.conf because > > My best recommendation based on everything you've said so far can only > be to tell you simply not to mess with the contents of /etc/make.conf > or any other configuration file in /etc which you don't fully > understand. We picked good defaults specifically so that most people > wouldn't have to mess with these files at all as a general rule, and > if they DO mess with them we expect them to know exactly what they're > doing. Oh, don't condescend, Jordan. FreeBSD isn't Windows 95, nor should it be. When the time comes that Unix is about surrendering all control to the Bureau of Recommended Settings, I will find another operating system. The fact is that there are knobs in make.conf, and they even say things like "...probably the most common, use could be...", and "Another useful entry is...". People are going to "mess with" those things. Perhaps they have plenty of memory available for -pipe, or perhaps they compile a lot of ports and want -O2 for the majority of them. Perhaps they configured make.conf when they installed FreeBSD, and haven't looked at it since.. a few months later they go to do a buildworld and don't remember to check whether any make settings have been alterered. Sure, when it blows up after an hour of building, they'll think "Damn, I bet I changed something in make.conf". It could have saved them a bit of work if the build process had said something like: You have changed one or more of the following default build options. FreeBSD is only tested with the default settings. You may want to press ^C now to abort the build and check your settings. If you continue, the build may fail or produce incorrect output. Please do not continue unless you are sure of what you're doing. Option Default Current setting CFLAGS "" "-O -pipe" -DNOPERL unset set Build will continue automatically in 10 seconds unless aborted. I take full responsibility for messing up my system (see .sig quote). I wouldn't be hacking -current if I weren't willing to take some risks. I just thought that "this may be a predictable build failure" was germane considering the recent discussions about the new bind users and the dangers of -DNOPERL. I've been doing world builds since the early days of NetBSD on my Sun 3. I'm well aware that it's a very complex and finely balanced system that shouldn't be expected to continue working if you mess up the environment. That said, I'm inclined to agree more with the "if there are a few things that can be caught up front instead of when it fails in the middle, then catch them" philosophy than the Microsoftian "remove all of the settings that the users might hurt themselves on" dumbing down approach. Anyway, I'm done with this now. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 19:11:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15710 for freebsd-current-outgoing; Wed, 9 Dec 1998 19:11:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15704 for ; Wed, 9 Dec 1998 19:11:44 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id TAA17414; Wed, 9 Dec 1998 19:10:53 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma017409; Wed, 9 Dec 98 19:10:26 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id TAA12329; Wed, 9 Dec 1998 19:10:25 -0800 (PST) From: Archie Cobbs Message-Id: <199812100310.TAA12329@bubba.whistle.com> Subject: Re: buildworld and PAM and login and stuff In-Reply-To: <28468.913257133@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 9, 98 06:32:13 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Wed, 9 Dec 1998 19:10:25 -0800 (PST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Jordan K. Hubbard writes: > My best recommendation based on everything you've said so far can only > be to tell you simply not to mess with the contents of /etc/make.conf > or any other configuration file in /etc which you don't fully > understand. We picked good defaults specifically so that most people > wouldn't have to mess with these files at all as a general rule, and > if they DO mess with them we expect them to know exactly what they're > doing. Brings up a related question I was wondering about.. what happens if you compile the kernel -O2? I guess it must break something, otherwise that would be the default.. ? -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 Dec 9 19:19:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16602 for freebsd-current-outgoing; Wed, 9 Dec 1998 19:19:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16587 for ; Wed, 9 Dec 1998 19:19:22 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.1/8.8.7) with ESMTP id WAA01322; Wed, 9 Dec 1998 22:20:04 -0500 (EST) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Wed, 9 Dec 1998 22:20:04 -0500 (EST) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: lcremean@tidalwave.net cc: current@FreeBSD.ORG Subject: Re: ide_pci.c In-Reply-To: <19981209212339.A82984@tidalwave.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Dec 09, 1998 at 08:42:42PM -0500, Kenneth Wayne Culver wrote: > > I just thought that someone in here should know this: I have a generic > > dual PCI IDE controller. It can support up to 4 devices. I have 2 hard > > drives on the first controller, and an ATAPI cdrom drive on the second. > > The problem is that when it boots, it says that the controller is simplex, > > and that there is no dma on the secondary channel, and then when it gets > > down to the ISA configuration, it won't find anything on the second > > controller. The only way I could fix it is to go to > > /usr/src/sys/i386/conf/files.i386 and delete the line that specifies > > ide_pci.c > > What chipset is on your motherboard, per chance? I have a motherboard with > an Acer Aladdin IV+ chipset, and unless I put "options DISABLE_PCI_IDE" in > my kernel config, my second channel will not work. I've been meaning to > look into adding native support for the Aladdin's PCI IDE controller for a > while now, but I haven't had the time (or made the time, really) to do the > work. > I can't find anywhere in my doc for my motherboard what chipset I have. It is just a generic chipset as far as I can tell. I'll have to get inside the computer and take a look at the actual chip in order to tell you. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 19:30:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18770 for freebsd-current-outgoing; Wed, 9 Dec 1998 19:30:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.128.29.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18763 for ; Wed, 9 Dec 1998 19:30:42 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: (from mi@localhost) by kot.ne.mediaone.net (8.9.1a/8.9.1) id WAA20049 for current@freebsd.org; Wed, 9 Dec 1998 22:30:16 -0500 (EST) From: Mikhail Teterin Message-Id: <199812100330.WAA20049@kot.ne.mediaone.net> Subject: Re: buildworld and PAM and login and stuff In-Reply-To: <199812100310.TAA12329@bubba.whistle.com> from Archie Cobbs at "Dec 9, 1998 07:10:25 pm" To: current@FreeBSD.ORG Date: Wed, 9 Dec 1998 22:30:16 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA25922 for freebsd-current-outgoing; Wed, 9 Dec 1998 20:31:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA25917 for ; Wed, 9 Dec 1998 20:31:15 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id NAA02545; Thu, 10 Dec 1998 13:28:58 +0900 (JST) Message-Id: <199812100428.NAA02545@chandra.eatell.msr.prug.or.jp> To: Mark Murray cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 09 Dec 1998 12:05:57 +0200." <199812091005.MAA88550@greenpeace.grondar.za> Date: Thu, 10 Dec 1998 13:28:57 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > FreeBSD 3.0 will turn off the laptop (on my Libretto 70) with > shutdown -h. What is wrong with this? It is wrong. In traditional UNIX, if you want to power-off, use another command shutdown -h, example halt -p or shutdown -x. Because, anytime shutdown -h, not want to power-off, sometime want go to ROM monitor. # PC/AT arch has not ROM monitor, but it is PC/AT arch depend problem. In Linux, when shutdown -h, choice power-off or halt only by config-option. Second problem, 3.0-RELEASE's implement problem. It is hard cording in src/sys/i386/i386/machdep.c:cpu_power_down(). If you want to add new power-control mechanism, you must change that code. My patch using at_shutdown() for registration power-control routine, so change power-control driver only. See PR i386/8638. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 Dec 9 20:41:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27259 for freebsd-current-outgoing; Wed, 9 Dec 1998 20:41:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27238 for ; Wed, 9 Dec 1998 20:41:05 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-wat.sentex.net [209.167.248.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id XAA12857; Wed, 9 Dec 1998 23:47:28 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19981209234607.016420e0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 09 Dec 1998 23:46:07 -0500 To: Marc Slemko , Jacques Vidrine From: Mike Tancsa Subject: Re: Current ready for prime time web server ? Cc: current@FreeBSD.ORG In-Reply-To: References: <199812092209.QAA28014@spawn.nectar.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:42 PM 12/9/98 -0800, Marc Slemko wrote: >On Wed, 9 Dec 1998, Jacques Vidrine wrote: > >> On 9 December 1998 at 16:39, Mike Tancsa wrote: >> [snip] >> > >Well, why not rebuild Apache with a larger FD_SETSIZE like it says? >> > >> > Hi, >> >Thanks for responding... I thought I had to rebuild STABLE as well no ? I >> > am just worried that would introduce other problems. Also, other recent >> > postings in questions suggest that this is not done easily. >> >> You need only recompile Apache, not the OS. It is quite easily done.. >> just define FD_SETSIZE before including . A reasonable > >Exactly. > >In Apache's case, it will reserve a few low descriptors for other >libraries that may need them and shouldn't be calling any library >functions that will end up with high numbered descriptors and that can't >handle them. Excellent, thanks for all your help on this issue folks! I have recomplied the port on my stable box... Now the question is, how do I test this to make sure its working correctly ? I did a grep ^ServerName httpd.conf | awk '{print "lynx -dump http://"$2 " > /dev/null"}' | sh to hit all of my virtuals and there was nothing telling error logs. Is there a way to check for sure that it has solved the problem ? ---Mike ********************************************************************** Mike Tancsa, Network Admin * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 01.519.651.3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 20:41:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27352 for freebsd-current-outgoing; Wed, 9 Dec 1998 20:41:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA27346 for ; Wed, 9 Dec 1998 20:41:53 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id NAA02560; Thu, 10 Dec 1998 13:38:53 +0900 (JST) Message-Id: <199812100438.NAA02560@chandra.eatell.msr.prug.or.jp> To: Mike Smith cc: Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 09 Dec 1998 17:09:29 PST." <199812100109.RAA01612@dingo.cdrom.com> Date: Thu, 10 Dec 1998 13:38:52 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So put the pccard.conf entry that matched the card from PAO in your > stock pccard.conf, and make the same IRQ config changes. First, 3.0-RELEASE's pccard.conf.sample using fixed irq (example, ed driver use 11 or 10 or 9, sometime use '?'). In PAO, enhanced pccardd, so can use "any" and using "any" in pccard.conf.sample. Second, PAO enhanced irq-pool, dynamic irq-pool. So, pccardd get free-irq from kernel. Third, PAO changed PCIC attach ISA device. So, you want to change PCIC's irq, you can use UserConfig. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 Dec 9 20:56:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28852 for freebsd-current-outgoing; Wed, 9 Dec 1998 20:56:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28843 for ; Wed, 9 Dec 1998 20:56:21 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40382>; Thu, 10 Dec 1998 15:55:22 +1100 Date: Thu, 10 Dec 1998 15:55:53 +1100 From: Peter Jeremy Subject: Re: buildworld and PAM and login and stuff To: current@FreeBSD.ORG Message-Id: <98Dec10.155522est.40382@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Archie Cobbs wrote: >Brings up a related question I was wondering about.. what happens >if you compile the kernel -O2? I guess it must break something, >otherwise that would be the default.. ? I understand the stock gcc (2.7.2.1) generates bad code with -O2. I don't know the exact details. Mikhail Teterin wrote: >using the gcc-2.8.1 compiler. I had to add the libkern's muldi3 (I >think), to the Makefile manually. I don't recall this one (although I haven't tried using gcc-2.8.1 on -current). I _am_ aware of one (fairly subtle) problem with gcc-2.8.1 that prevents it correctly building a kernel: The cpp _does_not_ remove backslash-newline sequences from string constants (and maybe elsewhere as well). This causes problems with the DEVICE_NAMES macro defined in vector.h and used in vector.s. I have reported this to bug-gcc (in mid-June) but haven't seen any response. At this time, I don't know of any way to disable this - the only work- around is to use a gcc-2.7.x derived cpp (eg the standard cpp). This implies changing NORMAL_S and DRIVER_S in /sys/i386/conf/Makefile.i386 to explicitly use the standard (2.7.2.1-derived) cpp in front of as. [Note that according to the GNU as documentation, gas handles backslashes inside strings in the same way as C. This is not (and, according to one of the gas maintainers, has never been) true]. I have also identified 3 cases where gcc-2.8.1 generates sub-optimal code: a) A long-long variable divided by a constant power-of-2 generates an unnecessary call to __cmpdi2. This prevents a 2.x (and presumably -current) kernel from linking because __cmpdi2 is not included in the kernel support library. This may be the problem Mikhail has seen. b) The code for random() does divide and modulo operations which gcc-2.7 merges into a single idivl instruction, whilst 2.8.1 generates additional code to `optimise' the division. c) In some cases where gcc converts a loop index multiplied by a constant into a temporary variable incremented by the constant, gcc 2.8.1 unnecessarily splits the addition into two pieces. For the first problem, I have a patch (posted to freebsd-ports on 13th April) that fixes this by extending the code in the expmed.c to open-code the 64-bit compare. It's about 500 lines. Richard Kenner developed patches for the other two problems and mailed them to me. I don't know what further distribution has been made. They total about 50 lines. Peter -- Peter Jeremy (VK2PJ) peter.jeremy@alcatel.com.au Alcatel Australia Limited 41 Mandible St Phone: +61 2 9690 5019 ALEXANDRIA NSW 2015 Fax: +61 2 9690 5982 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 20:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28954 for freebsd-current-outgoing; Wed, 9 Dec 1998 20:57:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28947 for ; Wed, 9 Dec 1998 20:57:17 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id VAA04884; Wed, 9 Dec 1998 21:56:40 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id VAA21000; Wed, 9 Dec 1998 21:56:39 -0700 Date: Wed, 9 Dec 1998 21:56:39 -0700 Message-Id: <199812100456.VAA21000@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: NAKAGAWA Yoshihisa Cc: Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812100438.NAA02560@chandra.eatell.msr.prug.or.jp> References: <199812100109.RAA01612@dingo.cdrom.com> <199812100438.NAA02560@chandra.eatell.msr.prug.or.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So put the pccard.conf entry that matched the card from PAO in your > > stock pccard.conf, and make the same IRQ config changes. > > First, 3.0-RELEASE's pccard.conf.sample using fixed irq (example, > ed driver use 11 or 10 or 9, sometime use '?'). In PAO, enhanced > pccardd, so can use "any" and using "any" in pccard.conf.sample. Last I looked, "any" and '?' used the exact same code. > Third, PAO changed PCIC attach ISA device. So, you want to change > PCIC's irq, you can use UserConfig. This is wrong, because a PCIC is *NOT* an isa device. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 21:14:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00504 for freebsd-current-outgoing; Wed, 9 Dec 1998 21:14:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00499 for ; Wed, 9 Dec 1998 21:14:09 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id OAA02646; Thu, 10 Dec 1998 14:10:24 +0900 (JST) Message-Id: <199812100510.OAA02646@chandra.eatell.msr.prug.or.jp> To: Nate Williams cc: Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 09 Dec 1998 21:56:39 MST." <199812100456.VAA21000@mt.sri.com> Date: Thu, 10 Dec 1998 14:10:24 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Third, PAO changed PCIC attach ISA device. So, you want to change > > PCIC's irq, you can use UserConfig. > > This is wrong, because a PCIC is *NOT* an isa device. NO NO NO, PCIC is *true* ISA device. Some PCIC connect to PCI, it is other problem. i82365, CLPD6710, RF5C396, VG468, ... , these are *ISA* PCIC. It is available ISA card for desktop PC in market. NOT Note-PC and on mother-board only ! In kernel, it should be attach ISA device. Because, *ISA* PCIC using ISA bus only. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 Dec 9 21:42:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03541 for freebsd-current-outgoing; Wed, 9 Dec 1998 21:42:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA03527 for ; Wed, 9 Dec 1998 21:42:56 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id WAA05203; Wed, 9 Dec 1998 22:42:42 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id WAA21183; Wed, 9 Dec 1998 22:42:41 -0700 Date: Wed, 9 Dec 1998 22:42:41 -0700 Message-Id: <199812100542.WAA21183@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: NAKAGAWA Yoshihisa Cc: Nate Williams , Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812100510.OAA02646@chandra.eatell.msr.prug.or.jp> References: <199812100456.VAA21000@mt.sri.com> <199812100510.OAA02646@chandra.eatell.msr.prug.or.jp> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Third, PAO changed PCIC attach ISA device. So, you want to change > > > PCIC's irq, you can use UserConfig. > > > > This is wrong, because a PCIC is *NOT* an isa device. > > NO NO NO, PCIC is *true* ISA device. Some PCIC connect to PCI, it > is other problem. Some PCIC controllers are ISA devices. Others are not. > In kernel, it should be attach ISA device. Because, *ISA* PCIC > using ISA bus only. I disagree. Just because some are ISA doesn't mean that all are ISA. Also, this makes it harder (not eaiser) to support CardBus in the future. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 9 22:56:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10822 for freebsd-current-outgoing; Wed, 9 Dec 1998 22:56:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10817 for ; Wed, 9 Dec 1998 22:56:55 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id PAA02808; Thu, 10 Dec 1998 15:53:26 +0900 (JST) Message-Id: <199812100653.PAA02808@chandra.eatell.msr.prug.or.jp> To: Nate Williams cc: Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 09 Dec 1998 22:42:41 MST." <199812100542.WAA21183@mt.sri.com> Date: Thu, 10 Dec 1998 15:53:26 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I disagree. Just because some are ISA doesn't mean that all are ISA. > Also, this makes it harder (not eaiser) to support CardBus in the > future. I disagree 3.0-RELEASE style. ISA device, shuld be attach as ISA device. PCI PCIC, like CardBus controller, shuld be attach as PCI device. It should be separate PCIC core code from bus depend and bus independ. CardBus support, we are planning on newconfig Project in near future. Bus independ code is necessary. So, we use NetBSD(4.4BSD) style bus and device configuration code. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 Dec 10 01:08:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA24995 for freebsd-current-outgoing; Thu, 10 Dec 1998 01:08:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mailgw1.fhg.de (mailgw1.fhg.de [153.96.1.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA24981 for ; Thu, 10 Dec 1998 01:08:40 -0800 (PST) (envelope-from runge@egd.igd.fhg.de) Received: by mailgw1.fhg.de (fhg.de); Thu, 10 Dec 1998 10:08:29 +0100 (MET) X-ENV: (mailgw1.fhg.de) runge@egd.igd.fhg.de -> current@freebsd.ORG.VIA-SMTP X-BULK-CHECK-1-981210.10.04.03: egd.egd.igd.fhg.de [153.96.43.2] Received: by mailgw1.fhg.de (fhg.de) with SMTP; Thu, 10 Dec 1998 10:03:37 +0100 (MET) from brussel.egd.igd.fhg.de Received: by brussel.egd.igd.fhg.de; Thu, 10 Dec 98 10:01:18 +0100 Message-Id: <366F8DDE.C93267FB@rostock.zgdv.de> Date: Thu, 10 Dec 1998 10:01:18 +0100 From: Thomas Runge Organization: http://www.rostock.zgdv.de X-Mailer: Mozilla 4.08 [en] (X11; U; SunOS 5.6 sun4u) Mime-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: ide_pci.c References: <19981209212339.A82984@tidalwave.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lee Cremeans wrote: > > The problem is that when it boots, it says that the controller is simplex, > > and that there is no dma on the secondary channel, and then when it gets > > down to the ISA configuration, it won't find anything on the second > What chipset is on your motherboard, per chance? I have a motherboard with > an Acer Aladdin IV+ chipset, and unless I put "options in > my kernel config, my second channel will not work. I've been meaning to > look into adding native support for the Aladdin's PCI IDE controller for a > while now, but I haven't had the time (or made the time, really) to do the > work. Same problem here with my Aladdin V chipset. DISABLE_PCI_IDE helps, but what I understood reading the source is, that this option disables DMA which cant be the final solution. But after all this isnt really a new problem. I found this in the bugreports: [1998/11/07] i386/8594 ide_pci disables second channel in 3.0-CURRENT [1998/11/08] i386/8608 wdc1 is not detected on motherboards with Aladdin V chipsets -- Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 01:11:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA25385 for freebsd-current-outgoing; Thu, 10 Dec 1998 01:11:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA25380 for ; Thu, 10 Dec 1998 01:11:27 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id BAA29664; Thu, 10 Dec 1998 01:10:33 -0800 (PST) To: NAKAGAWA Yoshihisa cc: Nate Williams , Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 10 Dec 1998 15:53:26 +0900." <199812100653.PAA02808@chandra.eatell.msr.prug.or.jp> Date: Thu, 10 Dec 1998 01:10:32 -0800 Message-ID: <29660.913281032@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I disagree 3.0-RELEASE style. ISA device, shuld be attach as ISA > device. PCI PCIC, like CardBus controller, shuld be attach as PCI > device. It should be separate PCIC core code from bus depend and > bus independ. FWIW, I think Yoshihisa-san is quite correct here. There's nothing keeping one from writing a separate bus attach function for each ISA/PCI/etc PCIC just as we do for many of our "ISA" drivers which have since evolved into PCI market models. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 05:46:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22593 for freebsd-current-outgoing; Thu, 10 Dec 1998 05:46:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from boco.fee.vutbr.cz (boco.fee.vutbr.cz [147.229.9.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22587 for ; Thu, 10 Dec 1998 05:46:45 -0800 (PST) (envelope-from cejkar@dcse.fee.vutbr.cz) Received: from kazi.dcse.fee.vutbr.cz (kazi.dcse.fee.vutbr.cz [147.229.8.12]) by boco.fee.vutbr.cz (8.9.1/8.9.1) with ESMTP id OAA46535 for ; Thu, 10 Dec 1998 14:46:35 +0100 (CET) Received: (from cejkar@localhost) by kazi.dcse.fee.vutbr.cz (8.8.8/8.8.8) id OAA12755 for freebsd-current@freebsd.org; Thu, 10 Dec 1998 14:46:35 +0100 (CET) From: Cejka Rudolf Message-Id: <199812101346.OAA12755@kazi.dcse.fee.vutbr.cz> Subject: mkfifo()/select() & O_RDONLY serious bug? To: freebsd-current@FreeBSD.ORG (freebsd-current@freebsd.org) Date: Thu, 10 Dec 1998 14:46:35 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have prepared small testing program (listed at the end) with mkfifo() and select() calls. Fifo is opened as O_RDONLY or O_RDWR with O_NONBLOCK. On FreeBSD 3.0-CURRENT, its behavior is different from other systems. I think it is serious bug: select() returns that there is ready file descriptor but descriptor is not ready in fact. I'm right? Tested on systems: FreeBSD 3.0-CURRENT FreeBSD 2.2.7 Solaris 2.6 Unixware 2.1 Linux Debian 2.0 { Another bug: On FreeBSD systems I must use "#include " for FD_ZERO() because of bzero() function. Yes? (If not, we need to fix manual page for select(2) about needed includes.) } Results with "#define MODE O_RDWR": (It looks well.) test: Open... test: FD = 3 test: Read... test: read(tst.pipe): Resource temporarily unavailable test: Select... test: select(): Not ready # After timeout Results with "#define MODE O_RDONLY": (It looks bad for -current.) test: Open... test: FD = 3 test: Read... # Next line is only on FreeBSD 2.2.7: (So is it bug on FreeBSD 2.2.7?) test: read(tst.pipe): Resource temporarily unavailable test: Select... # *** Next line on all systems except FreeBSD 3.0-CURRENT: test: select(): Not ready # After timeout # *** This line is only on FreeBSD 3.0-CURRENT: # *** I think, this is next bug, because nothing is ready! test: select(): Ready 3 # *** Immediate return === test.c listing: =============================================== #define MODE O_RDONLY /* O_RDWR */ #include #include #include #include #include #include #include /* Why I need this line on _only_ FreeBSD systems? */ #include #define FILE "tst.pipe" int main(void) { fd_set set; struct timeval t; int fd; int ret; char c; unlink(FILE); if (mkfifo(FILE, S_IRUSR | S_IWUSR) != 0) err(1, "mkfifo(%s)", FILE); warnx("Open..."); if ((fd = open(FILE, MODE | O_NONBLOCK)) < 0) err(1, "open(%s)", FILE); warnx("FD = %d", fd); warnx("Read..."); if (read(fd, &c, 1) < 0) warn("read(%s)", FILE); warnx("Select..."); FD_ZERO(&set); FD_SET(fd, &set); t.tv_sec = 5; t.tv_usec = 0; ret = select(fd + 1, &set, NULL, NULL, &t); if (ret < 0) err(1, "select(%s)", FILE); else if (ret == 0) warnx("select(): Not ready"); else { if (FD_ISSET(fd, &set)) warnx("select(): Ready %d", fd); else warnx("select(): Ready unknown"); } close(fd); return 0; } =================================================================== --=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=--=-- Rudolf Cejka (cejkar@dcse.fee.vutbr.cz; http://www.fee.vutbr.cz/~cejkar) Technical University of Brno, Faculty of El. Engineering and Comp. Science Bozetechova 2, 612 66 Brno, Czech Republic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 07:07:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02267 for freebsd-current-outgoing; Thu, 10 Dec 1998 07:07:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from culverk.student.umd.edu (culverk.student.umd.edu [129.2.164.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02262 for ; Thu, 10 Dec 1998 07:07:02 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from localhost (culverk@localhost) by culverk.student.umd.edu (8.9.1/8.8.7) with ESMTP id KAA01621; Thu, 10 Dec 1998 10:07:44 -0500 (EST) (envelope-from culverk@wam.umd.edu) X-Authentication-Warning: culverk.student.umd.edu: culverk owned process doing -bs Date: Thu, 10 Dec 1998 10:07:44 -0500 (EST) From: Kenneth Wayne Culver X-Sender: culverk@culverk.student.umd.edu To: Thomas Runge cc: current@FreeBSD.ORG Subject: Re: ide_pci.c In-Reply-To: <366F8DDE.C93267FB@rostock.zgdv.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 > > > > > The problem is that when it boots, it says that the controller is simplex, > > > and that there is no dma on the secondary channel, and then when it gets > > > down to the ISA configuration, it won't find anything on the second > > > > > What chipset is on your motherboard, per chance? I have a motherboard with > > an Acer Aladdin IV+ chipset, and unless I put "options in > > my kernel config, my second channel will not work. I've been meaning to > > look into adding native support for the Aladdin's PCI IDE controller for a > > while now, but I haven't had the time (or made the time, really) to do the > > work. > > Same problem here with my Aladdin V chipset. DISABLE_PCI_IDE helps, but > what I > understood reading the source is, that this option disables DMA which > cant > be the final solution. > But after all this isnt really a new problem. I found this in the > bugreports: > > [1998/11/07] i386/8594 ide_pci disables second channel in > 3.0-CURRENT > [1998/11/08] i386/8608 wdc1 is not detected on motherboards > with Aladdin V chipsets > I knew about that, I think I put one of them there, although I don't quite remember. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 07:38:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05277 for freebsd-current-outgoing; Thu, 10 Dec 1998 07:38:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bfc.dk ([194.192.110.140]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA05271 for ; Thu, 10 Dec 1998 07:38:16 -0800 (PST) (envelope-from npe@bfc.dk) From: npe@bfc.dk Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566D6.00557D32 ; Thu, 10 Dec 1998 16:33:46 +0100 X-Lotus-FromDomain: BFC-DATA@BFC To: freebsd-current@FreeBSD.ORG Message-ID: <412566D6.005576B2.00@bfc.dk> Date: Thu, 10 Dec 1998 16:34:18 +0100 Subject: RE: bootiso - freeware Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG We can use the program... But it is for dos..... - Nicolai ---------------------- Forwarded by Nicolai Petri/BFC-DATA on 10-12-98 16:34 --------------------------- "Jason Livingston (ICQ#6100280)" on 10-12-98 05:52:06 To: Nicolai Petri/BFC-DATA cc: Subject: RE: bootiso - freeware >I was wondering how our point of views is for the license terms for bootiso. Because your program would be nice to use with the FreeBSD project to make bootable cd''s. This is a non commercial project but cd''s are still for sale, so I wondered if you have any objections to this.. It would also be very nice with a FreeBSD version of our program.. Not necessary the sourcecode. I'm not sure how you would do it without the source code (which probably isn't easily ported to Unix anyway), but if you just want to distribute the program with FreeBSD that is ok. ---------------------------------- Download ICQ at http://www.icq.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 07:40:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05530 for freebsd-current-outgoing; Thu, 10 Dec 1998 07:40:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from solaris.matti.ee (solaris.matti.ee [194.126.98.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05525 for ; Thu, 10 Dec 1998 07:40:41 -0800 (PST) (envelope-from vallo@myhakas.matti.ee) Received: from myhakas.matti.ee (myhakas [194.126.98.150]) by solaris.matti.ee (8.8.8/8.8.8.s) with ESMTP id RAA08045 for ; Thu, 10 Dec 1998 17:40:26 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id RAA04332 for current@freebsd.org; Thu, 10 Dec 1998 17:40:27 +0200 (EET) (envelope-from vallo) Message-ID: <19981210174027.A4287@matti.ee> Date: Thu, 10 Dec 1998 17:40:27 +0200 From: Vallo Kallaste To: current@FreeBSD.ORG Subject: mformat in free(): warning: junk pointer, too high to make sense. Reply-To: vallo@matti.ee Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello ! I keep getting this error while trying to mformat one faulty floppy. The procedure is: myhakas# mformat a: plain_io: Input/output error Trouble initializing a FAT sector plain_io: Input/output error ^Cplain_io: Input/output error ^C^C^Cplain_io: Input/output error mformat in free(): warning: junk pointer, too high to make sense. mformat in free(): warning: junk pointer, too high to make sense. myhakas# The event occurs while repeatedly hitting Ctrl-C. Can this be any help to identify well known junk pointer thing ? Otherwise I leave it, because it doesn't cause any other trouble. I run quite recent current from Dec. 6. I haven't seen it before and I do lot of work with dos-formatted floppies. I provide any other information if needed. Vallo Kallaste vallo@matti.ee To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 07:41:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05565 for freebsd-current-outgoing; Thu, 10 Dec 1998 07:41:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dns.webwizard.net.mx (dns.webwizard.com.mx [148.245.50.27]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05560 for ; Thu, 10 Dec 1998 07:41:00 -0800 (PST) (envelope-from eculp@webwizard.org.mx) Received: from webwizard.org.mx (dns.webwizard.com.mx [148.245.50.27]) by dns.webwizard.net.mx (8.9.1/8.9.1) with ESMTP id JAA58739 for ; Thu, 10 Dec 1998 09:40:51 -0600 (CST) (envelope-from eculp@webwizard.org.mx) Message-ID: <366FEB82.9C668E66@webwizard.org.mx> Date: Thu, 10 Dec 1998 09:40:50 -0600 From: Edwin Culp X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-current@FreeBSD.ORG" Subject: Make World Failed Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With: install -c -s -o root -g wheel -m 555 bdes /usr/bin install -c -o root -g wheel -m 444 bdes.1.gz /usr/share/man/man1 ===> etc install -c -o root -g wheel -m 644 fbtab auth.conf rc.atm rc.devfs /etc install: fbtab: No such file or directory *** Error code 71 Stop. *** 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 Thu Dec 10 08:13:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09597 for freebsd-current-outgoing; Thu, 10 Dec 1998 08:13:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09577 for ; Thu, 10 Dec 1998 08:13:30 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA16454; Fri, 11 Dec 1998 03:13:22 +1100 Date: Fri, 11 Dec 1998 03:13:22 +1100 From: Bruce Evans Message-Id: <199812101613.DAA16454@godzilla.zeta.org.au> To: freebsd-current@FreeBSD.ORG, gallatin@cs.duke.edu Subject: Re: increased UDP latencies in -current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >In the process of doing some Myrinet benchmarks, I noticed that UDP >latencies have increased markedly after upgrading from 2.2.5-stable to >3.0-current. I see the opposite of this, if anything, for -current vs 2.2.6-2.2.7. >On identical machines (300Mhz PII, 440lx chipset, same memory >configuration) a kernel built from circa Jan. 18, 1998 2.2-stable >sources yields UDP small message latencies about 10% better than a >3.0-current kernel using both the netperf UDP_RR test & HBench-OS's >lat_udp. A 3.0 kernel from mid July yields slightly better results >than a recent -current, but not by much. > >Tests run across the loopback interface for a 1 byte message: > > RR/sec via us/msg via >OS rev netperf(1) HBench-OS(2) >--------- -------- ---------- >2.2.5 15502.17 56.6806 >3.0 (July 7) 13787.90 64.9367 >3.0 (Dec 1) 13656.60 66.5090 > >(1)netperf2.1pl3, run via netperf -tUDP_RR -l60 -i 10,2 -Hlocalhost >(2)hbench: lat_udp.c,v 1.4 1997/06/27 00:33:58 abrown Exp $, run as > lat_udp 10000 localhost On a K6/233, VIA2 chipset: lmbench-1.x "lat_udp localhost" -------- 2.2.5-2.2.6 about 85 -current about 80 Other not very careful lmbench-2 tests show a 10% UDP time bloat in my version of -current over the last 18 months: *Local* Communication latencies in microseconds - smaller is better ------------------------------------------------------------------- Host OS 2p/0K Pipe AF UDP RPC/ TCP RPC/ TCP ctxsw UNIX UDP TCP conn --------- ------------- ----- ----- ---- ----- ----- ----- ----- ---- gamplex.b FreeBSD 2.2.6 9 34 41 85 155 91 199 351 gamplex.b FreeBSD 3.0-C 14 30 32 71 161 79 202 575 gamplex.b FreeBSD 3.0-C 13 28 31 70 75 190 653 gamplex.b FreeBSD 3.0-C 7 26 33 79 91 207 gamplex.b FreeBSD 3.0-C 7 27 34 74 83 209 gamplex.b FreeBSD 3.0-C 7 29 34 78 85 207 gamplex.b FreeBSD 3.0-C 7 26 35 85 80 211 gamplex.b FreeBSD 3.0-C 8 27 35 88 79 gamplex.b FreeBSD 3.0-C 5 25 36 75 161 77 217 gamplex.b FreeBSD 3.0-C 7 27 36 82 176 85 216 gamplex.b FreeBSD 3.0-C 6 27 35 80 82 210 gamplex.b Linux 2.1.128 6 28 52 74 169 92 222 Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 08:32:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA11967 for freebsd-current-outgoing; Thu, 10 Dec 1998 08:32:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA11959 for ; Thu, 10 Dec 1998 08:32:14 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id LAA28903; Thu, 10 Dec 1998 11:32:06 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.1/8.9.1) id LAA96044; Thu, 10 Dec 1998 11:31:56 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 10 Dec 1998 11:31:55 -0500 (EST) To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: increased UDP latencies in -current In-Reply-To: <199812101613.DAA16454@godzilla.zeta.org.au> References: <199812101613.DAA16454@godzilla.zeta.org.au> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13935.62856.525786.504663@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bruce Evans writes: > >In the process of doing some Myrinet benchmarks, I noticed that UDP > >latencies have increased markedly after upgrading from 2.2.5-stable to > >3.0-current. > > I see the opposite of this, if anything, for -current vs 2.2.6-2.2.7. Hmm.. Perhaps my 2.2.5 kernel was built before the change responsible for the increased latencies was committed. < .. > > > On a K6/233, VIA2 chipset: > lmbench-1.x "lat_udp localhost" > -------- > 2.2.5-2.2.6 about 85 > -current about 80 lmbench 1-x shows similar results to what I saw with hbench: 2.2.5 54 -current 65 > Other not very careful lmbench-2 tests show a 10% UDP time bloat in my > version of -current over the last 18 months: > > *Local* Communication latencies in microseconds - smaller is better > ------------------------------------------------------------------- > Host OS 2p/0K Pipe AF UDP RPC/ TCP RPC/ TCP > ctxsw UNIX UDP TCP conn > --------- ------------- ----- ----- ---- ----- ----- ----- ----- ---- > gamplex.b FreeBSD 2.2.6 9 34 41 85 155 91 199 351 > gamplex.b FreeBSD 3.0-C 14 30 32 71 161 79 202 575 > gamplex.b FreeBSD 3.0-C 13 28 31 70 75 190 653 > gamplex.b FreeBSD 3.0-C 7 26 33 79 91 207 > gamplex.b FreeBSD 3.0-C 7 27 34 74 83 209 > gamplex.b FreeBSD 3.0-C 7 29 34 78 85 207 > gamplex.b FreeBSD 3.0-C 7 26 35 85 80 211 > gamplex.b FreeBSD 3.0-C 8 27 35 88 79 > gamplex.b FreeBSD 3.0-C 5 25 36 75 161 77 217 > gamplex.b FreeBSD 3.0-C 7 27 36 82 176 85 216 > gamplex.b FreeBSD 3.0-C 6 27 35 80 82 210 > gamplex.b Linux 2.1.128 6 28 52 74 169 92 222 What are the differences between the many 'FreeBSD 3.0-C' entries? Is it is primarily the date their kernel sources were checked out? Do you have approximate dates? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 08:46:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13845 for freebsd-current-outgoing; Thu, 10 Dec 1998 08:46:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA13840 for ; Thu, 10 Dec 1998 08:46:54 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA17987; Fri, 11 Dec 1998 03:46:46 +1100 Date: Fri, 11 Dec 1998 03:46:46 +1100 From: Bruce Evans Message-Id: <199812101646.DAA17987@godzilla.zeta.org.au> To: bde@zeta.org.au, gallatin@cs.duke.edu Subject: Re: increased UDP latencies in -current Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Other not very careful lmbench-2 tests show a 10% UDP time bloat in my > > version of -current over the last 18 months: > > > > *Local* Communication latencies in microseconds - smaller is better > > ------------------------------------------------------------------- > > Host OS 2p/0K Pipe AF UDP RPC/ TCP RPC/ TCP > > ctxsw UNIX UDP TCP conn > > --------- ------------- ----- ----- ---- ----- ----- ----- ----- ---- > > gamplex.b FreeBSD 2.2.6 9 34 41 85 155 91 199 351 > > gamplex.b FreeBSD 3.0-C 14 30 32 71 161 79 202 575 > > gamplex.b FreeBSD 3.0-C 13 28 31 70 75 190 653 > > gamplex.b FreeBSD 3.0-C 7 26 33 79 91 207 > > gamplex.b FreeBSD 3.0-C 7 27 34 74 83 209 > > gamplex.b FreeBSD 3.0-C 7 29 34 78 85 207 > > gamplex.b FreeBSD 3.0-C 7 26 35 85 80 211 > > gamplex.b FreeBSD 3.0-C 8 27 35 88 79 > > gamplex.b FreeBSD 3.0-C 5 25 36 75 161 77 217 > > gamplex.b FreeBSD 3.0-C 7 27 36 82 176 85 216 > > gamplex.b FreeBSD 3.0-C 6 27 35 80 82 210 > > gamplex.b Linux 2.1.128 6 28 52 74 169 92 222 > > >What are the differences between the many 'FreeBSD 3.0-C' entries? Is >it is primarily the date their kernel sources were checked out? Do you >have approximate dates? Here are the dates. They can't actually cover 18 months since the machine is only 11 months old :-). The 3.0 results are a bit old. The dates mostly match the checkout time closely except for 2.2.6. -rw-r--r-- 1 bde wheel 13668 Jan 8 1998 results/i386-freebsd3.0/gamplex.bde.org -rw-r--r-- 1 bde wheel 13496 Jan 8 1998 results/i386-freebsd3.0/gamplex.bde.org.1 -rw-r--r-- 1 bde wheel 15131 Apr 13 1998 results/i386-freebsd3.0/gamplex.bde.org.2 -rw-r--r-- 1 bde wheel 15132 Apr 15 1998 results/i386-freebsd3.0/gamplex.bde.org.3 -rw-r--r-- 1 bde wheel 15133 Apr 15 1998 results/i386-freebsd3.0/gamplex.bde.org.4 -rw-r--r-- 1 bde wheel 15021 May 30 1998 results/i386-freebsd3.0/gamplex.bde.org.5 -rw-r--r-- 1 bde wheel 14976 May 30 1998 results/i386-freebsd3.0/gamplex.bde.org.6 -rw-r--r-- 1 bde wheel 15044 Jun 19 23:03 results/i386-freebsd3.0/gamplex.bde.org.7 -rw-r--r-- 1 bde wheel 14501 Jul 31 05:08 results/i386-freebsd2.2.6/gamplex.bde.org -rw-r--r-- 1 bde wheel 15218 Jul 31 05:21 results/i386-freebsd3.0/gamplex.bde.org.8 -rw-r--r-- 1 bde wheel 15069 Jul 31 21:39 results/i386-freebsd3.0/gamplex.bde.org.9 -rw-r--r-- 1 bde wheel 12490 Nov 17 20:38 results/i586-linux/gamplex.bde.org.5 Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 08:54:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14944 for freebsd-current-outgoing; Thu, 10 Dec 1998 08:54:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14939 for ; Thu, 10 Dec 1998 08:54:07 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id JAA09403; Thu, 10 Dec 1998 09:53:49 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id JAA22925; Thu, 10 Dec 1998 09:53:48 -0700 Date: Thu, 10 Dec 1998 09:53:48 -0700 Message-Id: <199812101653.JAA22925@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: NAKAGAWA Yoshihisa , Nate Williams , Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <29660.913281032@zippy.cdrom.com> References: <199812100653.PAA02808@chandra.eatell.msr.prug.or.jp> <29660.913281032@zippy.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I disagree 3.0-RELEASE style. ISA device, shuld be attach as ISA > > device. PCI PCIC, like CardBus controller, shuld be attach as PCI > > device. It should be separate PCIC core code from bus depend and > > bus independ. > > FWIW, I think Yoshihisa-san is quite correct here. There's nothing > keeping one from writing a separate bus attach function for each > ISA/PCI/etc PCIC just as we do for many of our "ISA" drivers which > have since evolved into PCI market models. The problem is that making it into an ISA device precludes us from doing alot of the 'IRQ' mapping, since that code is now wrapped up into the (once ISA independant) code. We (the FreeBSD laptop weenies) have been down this road in discussions before, and have rejected it as a hack. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 09:30:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18553 for freebsd-current-outgoing; Thu, 10 Dec 1998 09:30:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18448; Thu, 10 Dec 1998 09:29:50 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id SAA22887; Thu, 10 Dec 1998 18:29:40 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id SAA01144; Thu, 10 Dec 1998 18:29:39 +0100 (MET) Message-ID: <19981210182938.B371@follo.net> Date: Thu, 10 Dec 1998 18:29:38 +0100 From: Eivind Eklund To: vallo@matti.ee, current@FreeBSD.ORG Cc: dg@FreeBSD.ORG Subject: Re: mformat in free(): warning: junk pointer, too high to make sense. References: <19981210174027.A4287@matti.ee> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981210174027.A4287@matti.ee>; from Vallo Kallaste on Thu, Dec 10, 1998 at 05:40:27PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 10, 1998 at 05:40:27PM +0200, Vallo Kallaste wrote: > Hello ! > > I keep getting this error while trying to mformat one faulty floppy. > The procedure is: > > myhakas# mformat a: > plain_io: Input/output error > Trouble initializing a FAT sector > plain_io: Input/output error > ^Cplain_io: Input/output error > ^C^C^Cplain_io: Input/output error > mformat in free(): warning: junk pointer, too high to make sense. > mformat in free(): warning: junk pointer, too high to make sense. > myhakas# > > The event occurs while repeatedly hitting Ctrl-C. Can this be any > help to identify well known junk pointer thing ? Otherwise I leave > it, because it doesn't cause any other trouble. I run quite recent > current from Dec. 6. I haven't seen it before and I do lot of work > with dos-formatted floppies. I provide any other information if > needed. It occur because mtools use non-signal-safe functions in its signal handlers. The 'best' thing to do would be to identify just what is done wrong, and submit fixes back to the mtools maintainers. As for the inetd problem: We know what it is, we have a fix, and David Greenman seems to be vetoing committing it due to its "inelegance". Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 10:06:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA23261 for freebsd-current-outgoing; Thu, 10 Dec 1998 10:06:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from main.cravegames.com (main.cravegames.com [38.170.176.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23250 for ; Thu, 10 Dec 1998 10:06:30 -0800 (PST) (envelope-from tmoore@cravegames.com) Date: Thu, 10 Dec 1998 10:03:43 -0800 (PST) Message-Id: <199812101803.KAA67960@roscoe.mobile.cravegames.com> From: Tim Moore To: freebsd-current@FreeBSD.ORG Subject: NTIMECOUNTER and calcru... Reply-to: moore@wolfenet.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I had been following the negative calcru discussion with moderate interest until I got a new machine that exhibits the "calcru: negative time" problem. The machine is a 400 Mhz Dell with a Diamond Fire GL 1000 Pro video card; this sounds a lot like a machine on which the problem had been seen, so I had high hopes for the NTIMECOUNTER fix. However, it doesn't seem to make a difference, even with NTIMECOUNTER set to 2000. For testing I've been doing "sysctl -w kern.timecounter.method=1" in single user mode before going multi-user and starting X. As soon as X comes up the calcru messages start spewing. Is there hope for this machine and video card? Here's the configuration file and dmesg. Thanks, Tim # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.125 1998/10/16 01:30:11 obrien Exp $ machine "i386" cpu "I686_CPU" ident BELUSHI maxusers 32 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 controller isa0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 # Unless you know very well what you're doing, leave ft0 at drive 2, or # remove the line entirely if you don't need it. Trying to configure # it on another unit might cause surprises, see PR kern/7176. #tape ft0 at fdc0 drive 2 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 disk wd2 at wdc1 drive 0 disk wd3 at wdc1 drive 1 options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM device wcd0 #IDE CD-ROM device wfd0 #IDE Floppy (e.g. LS-120) # A single entry for any of these controllers (ncr, ahb, ahc, amd) is # sufficient for any number of installed devices. controller ahb0 controller ahc0 # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. controller scbus0 device da0 device sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows # # dano - commented out wt0, mcd0, matcd0, scd0 # #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" conflicts tty irq 1 vector pcrint #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. device xl0 pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing # This provides support for System V shared memory. # options SYSVSHM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. pseudo-device bpfilter 4 #Berkeley packet filter # These are attempts to get around the "calcru negative" problems which seem to # be caused by XFree86 and the Diamond FireGL video card. options NTIMECOUNTER=2000 options "MSGBUF_SIZE=40960" Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #8: Wed Dec 9 09:32:15 PST 1998 tmoore@roscoe.mobile.cravegames.com:/usr/src/sys/compile/BELUSHI Calibrating clock(s) ... TSC clock: 398797485 Hz, i8254 clock: 1193253 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium II (quarter-micron) (398.78-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002a4000 - 0x07ff5fff, 131407872 bytes (32082 pages) config> quit avail memory = 127598592 (124608K bytes) Found BIOS32 Service Directory header at 0xf00ffe80 Entry = 0xffe90 (0xf00ffe90) Rev = 0 Len = 1 PCI BIOS entry at 0xca9e SMIBIOS header at 0xf00fb160 Version 2.2 Table at 0xfb180, 84 entries, 2922 bytes, largest entry 179 bytes DMI header at 0xf00fb170 Version 2.2 Table at 0xfb180, 84 entries, 2922 bytes Other BIOS signatures found: ACPI: 000fdf30 $PnP: 000fe2d0 Preloaded elf kernel "kern.new" at 0xf0297000. Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x7190, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base f0000000, size 26 chip0: rev 0x02 on pci0.0.0 found-> vendor=0x8086, dev=0x7191, revid=0x02 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip1: rev 0x02 on pci0.1.0 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip2: rev 0x02 on pci0.7.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000ffa0, size 4 ide_pci0: rev 0x01 on pci0.7.1 intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: primary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: 0000ffa2 intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 20 from port: 0000ffaa ide_pci: ide1:0 has been configured for DMA by BIOS found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=14 map[0]: type 4, range 32, base 0000dce0, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip3: rev 0x02 on pci0.7.3 found-> vendor=0x10b7, dev=0x9055, revid=0x00 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[0]: type 4, range 32, base 0000dc00, size 7 map[1]: type 1, range 32, base fe000000, size 7 xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 14 on pci0.17.0 xl0: Ethernet address: 00:c0:4f:72:ed:56 xl0: media options word: a xl0: probing for a PHY xl0: checking address: 0 xl0: checking address: 1 xl0: checking address: 2 xl0: checking address: 3 xl0: checking address: 4 xl0: checking address: 5 xl0: checking address: 6 xl0: checking address: 7 xl0: checking address: 8 xl0: checking address: 9 xl0: checking address: 10 xl0: checking address: 11 xl0: checking address: 12 xl0: checking address: 13 xl0: checking address: 14 xl0: checking address: 15 xl0: checking address: 16 xl0: checking address: 17 xl0: checking address: 18 xl0: checking address: 19 xl0: checking address: 20 xl0: checking address: 21 xl0: checking address: 22 xl0: checking address: 23 xl0: checking address: 24 xl0: found PHY at address 24, vendor id: 0 device id: 0 xl0: PHY type: xl0: found 10baseT xl0: found 100baseTX xl0: autoneg complete, link status good (full-duplex, 100Mbps) bpf: xl0 attached found-> vendor=0x1011, dev=0x0024, revid=0x03 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=2 secondarybus=2 chip4: rev 0x03 on pci0.19.0 Probing for devices on PCI bus 1: found-> vendor=0x104c, dev=0x3d07, revid=0x01 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 1, range 32, base fcfe0000, size 17 map[1]: type 1, range 32, base fc000000, size 23 map[2]: type 1, range 32, base fb800000, size 23 vga0: rev 0x01 int a irq 11 on pci1.0.0 Probing for devices on PCI bus 2: found-> vendor=0x9005, dev=0x001f, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000ec00, size 8 map[1]: type 1, range 64, base f9fff000, size 12 map[2]: type 0, range 0, base 00000000, size 0 ahc0: rev 0x00 int a irq 10 on pci2.10.0 ahc0: Reading SEEPROM...done. ahc0: BIOS eeprom not present ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Resetting Channel A ahc0: Downloading Sequencer Program... 391 instructions downloaded found-> vendor=0x9004, dev=0x8078, revid=0x01 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000e800, size 8 map[1]: type 1, range 32, base f9ffe000, size 12 ahc1: rev 0x01 int a irq 10 on pci2.14.0 using shared irq10. ahc1: Reading SEEPROM...done. ahc1: internal 50 cable not present, internal 68 cable not present ahc1: external cable not present ahc1: BIOS eeprom is present ahc1: High byte termination Enabled ahc1: Low byte termination Enabled ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: Resetting Channel A ahc1: Downloading Sequencer Program... 411 instructions downloaded Probing for devices on the ISA bus: video: RTC equip. code:0x03, DCC code:0x09 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: WARNING: video mode switching is not fully supported on this adapter VGA parameters upon power-up 50 18 10 00 00 08 03 00 02 6f 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 00 08 03 00 02 6f 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: the current keyboard controller command byte 0065 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: disabled, not probed. sio3: disabled, not probed. lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached psm0: current command byte:0065 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 90 03 3c psm: status 90 03 3c psm: status 90 03 3c psm: status 00 00 28 psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, dma, iordy wcd0: 2412/5512KB/sec, 128KB cache, audio play, 256 volume levels, ejectable tray wcd0: no disc inside, unlocked npx0 on motherboard npx0: INT 16 interface apm0: disabled, not probed. imasks: bio c0088040, tty c007509a, net c007509a BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. bpf: tun0 attached bpf: sl0 attached bpf: ppp0 attached new masks: bio c0088040, tty c007509a, net c007509a bpf: lo0 attached Waiting 15 seconds for SCSI devices to settle (noperiph:ahc0:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. (noperiph:ahc1:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. ahc0: Selection Timeout on A:1. 1 SCBs aborted ahc1: Selection Timeout on A:0. 1 SCBs aborted ahc0: Selection Timeout on A:2. 1 SCBs aborted ahc1: Selection Timeout on A:1. 1 SCBs aborted ahc0: Selection Timeout on A:3. 1 SCBs aborted ahc1: Selection Timeout on A:2. 1 SCBs aborted ahc0: Selection Timeout on A:4. 1 SCBs aborted ahc1: Selection Timeout on A:3. 1 SCBs aborted ahc0: Selection Timeout on A:5. 1 SCBs aborted ahc1: Selection Timeout on A:4. 1 SCBs aborted ahc0: Selection Timeout on A:6. 1 SCBs aborted ahc1: Selection Timeout on A:5. 1 SCBs aborted ahc0: Selection Timeout on A:8. 1 SCBs aborted ahc1: Selection Timeout on A:6. 1 SCBs aborted ahc0: Selection Timeout on A:9. 1 SCBs aborted ahc1: Selection Timeout on A:8. 1 SCBs aborted ahc0: Selection Timeout on A:10. 1 SCBs aborted ahc1: Selection Timeout on A:9. 1 SCBs aborted ahc0: Selection Timeout on A:11. 1 SCBs aborted ahc1: Selection Timeout on A:10. 1 SCBs aborted ahc0: Selection Timeout on A:12. 1 SCBs aborted ahc1: Selection Timeout on A:11. 1 SCBs aborted ahc0: Selection Timeout on A:13. 1 SCBs aborted ahc1: Selection Timeout on A:12. 1 SCBs aborted ahc0: Selection Timeout on A:14. 1 SCBs aborted ahc1: Selection Timeout on A:13. 1 SCBs aborted ahc0: Selection Timeout on A:15. 1 SCBs aborted ahc0: target 0 using 16bit transfers ahc0: target 0 synchronous at 40.0MHz, offset = 0xf ahc1: Selection Timeout on A:14. 1 SCBs aborted ahc1: Selection Timeout on A:15. 1 SCBs aborted pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI2 device pass0: Serial Number LJ587842000019141CSZ pass0: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number LJ587842000019141CSZ da0: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to da0s4a da0s1: type 0x6, start 63, end = 4192964, size 4192902 : OK da0s2: type 0x82, start 4192965, end = 4289354, size 96390 : OK da0s3: type 0x83, start 4289355, end = 11454344, size 7164990 : OK da0s4: type 0xa5, start 11454345, end = 17767889, size 6313545 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 10:31:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26422 for freebsd-current-outgoing; Thu, 10 Dec 1998 10:31:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mx1.ews.uiuc.edu (mx1.ews.uiuc.edu [130.126.161.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26417 for ; Thu, 10 Dec 1998 10:31:50 -0800 (PST) (envelope-from locke@mcs.net) Received: from petedorm (isr3193.urh.uiuc.edu [130.126.64.183]) by mx1.ews.uiuc.edu (8.8.8/8.8.8) with SMTP id MAA20774; Thu, 10 Dec 1998 12:31:21 -0600 Message-Id: <3.0.5.32.19981210123121.009fd8d0@popmail.mcs.net> X-Sender: locke@popmail.mcs.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 10 Dec 1998 12:31:21 -0600 To: moore@wolfenet.com From: Peter Johnson Subject: Re: NTIMECOUNTER and calcru... 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 Get XFree 3.3.3; the patch for the XF86_3DLabs server is in it (at least the most recent releases). If your 3.3.3 doesn't include the fix, I have the patch if you need it (tiny little thing). Regards, Peter Johnson locke@mcs.net At 10:03 AM 12/10/98 -0800, you wrote: >I had been following the negative calcru discussion with moderate >interest until I got a new machine that exhibits the "calcru: negative >time" problem. The machine is a 400 Mhz Dell with a Diamond Fire GL >1000 Pro video card; this sounds a lot like a machine on which the >problem had been seen, so I had high hopes for the NTIMECOUNTER fix. >However, it doesn't seem to make a difference, even with NTIMECOUNTER >set to 2000. For testing I've been doing "sysctl -w >kern.timecounter.method=1" in single user mode before going multi-user >and starting X. As soon as X comes up the calcru messages start >spewing. > >Is there hope for this machine and video card? Here's the >configuration file and dmesg. > >Thanks, >Tim > ># ># GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks ># ># For more information read the handbook part System Administration -> ># Configuring the FreeBSD Kernel -> The Configuration File. ># The handbook is available in /usr/share/doc/handbook or online as ># latest version from the FreeBSD World Wide Web server ># ># ># An exhaustive list of options and more detailed explanations of the ># device lines is present in the ./LINT configuration file. If you are ># in doubt as to the purpose or necessity of a line, check first in LINT. ># ># $Id: GENERIC,v 1.125 1998/10/16 01:30:11 obrien Exp $ > >machine "i386" >cpu "I686_CPU" >ident BELUSHI >maxusers 32 > >options MATH_EMULATE #Support for x87 emulation >options INET #InterNETworking >options FFS #Berkeley Fast Filesystem >options FFS_ROOT #FFS usable as root device [keep this!] >options MFS #Memory Filesystem >options MFS_ROOT #MFS usable as root device, "MFS" req'ed >options NFS #Network Filesystem >options NFS_ROOT #NFS usable as root device, "NFS" req'ed >options MSDOSFS #MSDOS Filesystem >options "CD9660" #ISO 9660 Filesystem >options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed >options PROCFS #Process filesystem >options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] >options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device >options UCONSOLE #Allow users to grab the console >options FAILSAFE #Be conservative >options USERCONFIG #boot -c editor >options VISUAL_USERCONFIG #visual boot -c editor > >config kernel root on wd0 > >controller isa0 >controller eisa0 >controller pci0 > >controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 >disk fd0 at fdc0 drive 0 >disk fd1 at fdc0 drive 1 ># Unless you know very well what you're doing, leave ft0 at drive 2, or ># remove the line entirely if you don't need it. Trying to configure ># it on another unit might cause surprises, see PR kern/7176. >#tape ft0 at fdc0 drive 2 > >options "CMD640" # work around CMD640 chip deficiency >controller wdc0 at isa? port "IO_WD1" bio irq 14 >disk wd0 at wdc0 drive 0 >disk wd1 at wdc0 drive 1 > >controller wdc1 at isa? port "IO_WD2" bio irq 15 >disk wd2 at wdc1 drive 0 >disk wd3 at wdc1 drive 1 > >options ATAPI #Enable ATAPI support for IDE bus >options ATAPI_STATIC #Don't do it as an LKM >device wcd0 #IDE CD-ROM >device wfd0 #IDE Floppy (e.g. LS-120) > ># A single entry for any of these controllers (ncr, ahb, ahc, amd) is ># sufficient for any number of installed devices. >controller ahb0 >controller ahc0 > ># This controller offers a number of configuration options, too many to ># document here - see the LINT file in this directory and look up the ># dpt0 entry there for much fuller documentation on this. > >controller scbus0 > >device da0 > >device sa0 > >device pass0 > >device cd0 #Only need one of these, the code dynamically grows > ># ># dano - commented out wt0, mcd0, matcd0, scd0 ># >#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr >#device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr > >#controller matcd0 at isa? port 0x230 bio > >#device scd0 at isa? port 0x230 bio > ># syscons is the default console driver, resembling an SCO console >device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr ># Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver >#device vt0 at isa? port "IO_KBD" conflicts tty irq 1 vector pcrint >#options XSERVER # support for X server >#options FAT_CURSOR # start with block cursor ># If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines >#options PCVT_SCANSET=2 # IBM keyboards are non-std > >device npx0 at isa? port "IO_NPX" irq 13 vector npxintr > ># ># Laptop support (see LINT for more options) ># >device apm0 at isa? disable flags 0x31 # Advanced Power Management > ># PCCARD (PCMCIA) support >#controller card0 >#device pcic0 at card? >#device pcic1 at card? > >device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr >device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr >device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr >device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr > >device lpt0 at isa? port? tty irq 7 vector lptintr > >device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr > ># Order is important here due to intrusive probes, do *not* alphabetize ># this list of network interfaces until the probes have been fixed. ># Right now it appears that the ie0 must be probed before ep0. See ># revision 1.20 of this file. >device xl0 > >pseudo-device loop >pseudo-device ether >pseudo-device sl 1 >pseudo-device ppp 1 >pseudo-device tun 1 >pseudo-device pty 16 >pseudo-device gzip # Exec gzipped a.out's > ># KTRACE enables the system-call tracing facility ktrace(2). ># This adds 4 KB bloat to your kernel, and slightly increases ># the costs of each syscall. >options KTRACE #kernel tracing > ># This provides support for System V shared memory. ># >options SYSVSHM > ># The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be ># aware of the legal and administrative consequences of enabling this ># option. The number of devices determines the maximum number of ># simultaneous BPF clients programs runnable. >pseudo-device bpfilter 4 #Berkeley packet filter > ># These are attempts to get around the "calcru negative" problems which seem to ># be caused by XFree86 and the Diamond FireGL video card. > >options NTIMECOUNTER=2000 >options "MSGBUF_SIZE=40960" > >Copyright (c) 1992-1998 FreeBSD Inc. >Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. >FreeBSD 3.0-CURRENT #8: Wed Dec 9 09:32:15 PST 1998 > tmoore@roscoe.mobile.cravegames.com:/usr/src/sys/compile/BELUSHI >Calibrating clock(s) ... TSC clock: 398797485 Hz, i8254 clock: 1193253 Hz >CLK_USE_I8254_CALIBRATION not specified - using default frequency >Timecounter "i8254" frequency 1193182 Hz >CLK_USE_TSC_CALIBRATION not specified - using old calibration method >CPU: Pentium II (quarter-micron) (398.78-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping=2 > Features=0x183fbff> >real memory = 134217728 (131072K bytes) >Physical memory chunk(s): >0x00001000 - 0x0009efff, 647168 bytes (158 pages) >0x002a4000 - 0x07ff5fff, 131407872 bytes (32082 pages) >config> quit >avail memory = 127598592 (124608K bytes) >Found BIOS32 Service Directory header at 0xf00ffe80 >Entry = 0xffe90 (0xf00ffe90) Rev = 0 Len = 1 >PCI BIOS entry at 0xca9e >SMIBIOS header at 0xf00fb160 >Version 2.2 >Table at 0xfb180, 84 entries, 2922 bytes, largest entry 179 bytes >DMI header at 0xf00fb170 >Version 2.2 >Table at 0xfb180, 84 entries, 2922 bytes >Other BIOS signatures found: >ACPI: 000fdf30 >$PnP: 000fe2d0 >Preloaded elf kernel "kern.new" at 0xf0297000. >Math emulator present >pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 >pci_open(1a): mode1res=0x80000000 (0x80000000) >pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) >Probing for devices on PCI bus 0: >found-> vendor=0x8086, dev=0x7190, revid=0x02 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[0]: type 3, range 32, base f0000000, size 26 >chip0: rev 0x02 on pci0.0.0 >found-> vendor=0x8086, dev=0x7191, revid=0x02 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=1 secondarybus=1 >chip1: rev 0x02 on pci0.1.0 >found-> vendor=0x8086, dev=0x7110, revid=0x02 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 >chip2: rev 0x02 on pci0.7.0 >found-> vendor=0x8086, dev=0x7111, revid=0x01 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[0]: type 4, range 32, base 0000ffa0, size 4 >ide_pci0: rev 0x01 on pci0.7.1 >intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 >intel_piix_status: primary master fastDMAonly disabled, pre/post disabled, >intel_piix_status: IORDY sampling disabled, >intel_piix_status: fast PIO disabled >intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 >intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, >intel_piix_status: IORDY sampling disabled, >intel_piix_status: fast PIO disabled >ide_pci: busmaster 0 status: 04 from port: 0000ffa2 >intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 >intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, >intel_piix_status: IORDY sampling enabled, >intel_piix_status: fast PIO enabled >intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 >intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, >intel_piix_status: IORDY sampling disabled, >intel_piix_status: fast PIO disabled >ide_pci: busmaster 1 status: 20 from port: 0000ffaa >ide_pci: ide1:0 has been configured for DMA by BIOS >found-> vendor=0x8086, dev=0x7112, revid=0x01 > class=0c-03-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=d, irq=14 > map[0]: type 4, range 32, base 0000dce0, size 5 >found-> vendor=0x8086, dev=0x7113, revid=0x02 > class=06-80-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 >chip3: rev 0x02 on pci0.7.3 >found-> vendor=0x10b7, dev=0x9055, revid=0x00 > class=02-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=14 > map[0]: type 4, range 32, base 0000dc00, size 7 > map[1]: type 1, range 32, base fe000000, size 7 >xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 14 on pci0.17.0 >xl0: Ethernet address: 00:c0:4f:72:ed:56 >xl0: media options word: a >xl0: probing for a PHY >xl0: checking address: 0 >xl0: checking address: 1 >xl0: checking address: 2 >xl0: checking address: 3 >xl0: checking address: 4 >xl0: checking address: 5 >xl0: checking address: 6 >xl0: checking address: 7 >xl0: checking address: 8 >xl0: checking address: 9 >xl0: checking address: 10 >xl0: checking address: 11 >xl0: checking address: 12 >xl0: checking address: 13 >xl0: checking address: 14 >xl0: checking address: 15 >xl0: checking address: 16 >xl0: checking address: 17 >xl0: checking address: 18 >xl0: checking address: 19 >xl0: checking address: 20 >xl0: checking address: 21 >xl0: checking address: 22 >xl0: checking address: 23 >xl0: checking address: 24 >xl0: found PHY at address 24, vendor id: 0 device id: 0 >xl0: PHY type: >xl0: found 10baseT >xl0: found 100baseTX >xl0: autoneg complete, link status good (full-duplex, 100Mbps) >bpf: xl0 attached >found-> vendor=0x1011, dev=0x0024, revid=0x03 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=2 secondarybus=2 >chip4: rev 0x03 on pci0.19.0 >Probing for devices on PCI bus 1: >found-> vendor=0x104c, dev=0x3d07, revid=0x01 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[0]: type 1, range 32, base fcfe0000, size 17 > map[1]: type 1, range 32, base fc000000, size 23 > map[2]: type 1, range 32, base fb800000, size 23 >vga0: rev 0x01 int a irq 11 on pci1.0.0 >Probing for devices on PCI bus 2: >found-> vendor=0x9005, dev=0x001f, revid=0x00 > class=01-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=10 > map[0]: type 4, range 32, base 0000ec00, size 8 > map[1]: type 1, range 64, base f9fff000, size 12 > map[2]: type 0, range 0, base 00000000, size 0 >ahc0: rev 0x00 int a irq 10 on pci2.10.0 >ahc0: Reading SEEPROM...done. >ahc0: BIOS eeprom not present >ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs >ahc0: Resetting Channel A >ahc0: Downloading Sequencer Program... 391 instructions downloaded >found-> vendor=0x9004, dev=0x8078, revid=0x01 > class=01-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=10 > map[0]: type 4, range 32, base 0000e800, size 8 > map[1]: type 1, range 32, base f9ffe000, size 12 >ahc1: rev 0x01 int a irq 10 on pci2.14.0 > using shared irq10. >ahc1: Reading SEEPROM...done. >ahc1: internal 50 cable not present, internal 68 cable not present >ahc1: external cable not present >ahc1: BIOS eeprom is present >ahc1: High byte termination Enabled >ahc1: Low byte termination Enabled >ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs >ahc1: Resetting Channel A >ahc1: Downloading Sequencer Program... 411 instructions downloaded >Probing for devices on the ISA bus: >video: RTC equip. code:0x03, DCC code:0x09 >video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 >video: param table EGA/VGA:0, CGA/MDA:0 >video: rows_offset:1 >video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 >video#0: init mode:24, bios mode:3, current mode:24 >video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k >video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 >video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 >video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 >video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 >video#0: WARNING: video mode switching is not fully supported on this adapter >VGA parameters upon power-up >50 18 10 00 00 08 03 00 02 6f 5f 4f 50 82 55 81 >bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 >b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c >3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff >VGA parameters in BIOS for mode 24 >50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 >bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 >b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c >3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff >EGA/VGA parameters to be used for mode 24 >50 18 10 00 00 08 03 00 02 6f 5f 4f 50 82 55 81 >bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 >b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c >3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff >sc0: the current keyboard controller command byte 0065 >kbdio: DIAGNOSE status:0055 >kbdio: TEST_KBD_PORT status:0000 >kbdio: RESET_KBD return code:00fa >kbdio: RESET_KBD status:00aa >sc0: keyboard device ID: ab41 >sc0 at 0x60-0x6f irq 1 on motherboard >sc0: VGA color <16 virtual consoles, flags=0x0> >sio0: irq maps: 0x1 0x11 0x1 0x1 >sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa >sio0: type 16550A >sio1: irq maps: 0x1 0x9 0x1 0x1 >sio1 at 0x2f8-0x2ff irq 3 on isa >sio1: type 16550A >sio2: disabled, not probed. >sio3: disabled, not probed. >lpt0 at 0x378-0x37f irq 7 on isa >lpt0: Interrupt-driven port >lp0: TCP/IP capable interface >bpf: lp0 attached >psm0: current command byte:0065 >kbdio: TEST_AUX_PORT status:0000 >kbdio: RESET_AUX return code:00fa >kbdio: RESET_AUX status:00aa >kbdio: RESET_AUX ID:0000 >psm: status 00 02 64 >psm: status 90 03 3c >psm: status 90 03 3c >psm: status 90 03 3c >psm: status 00 00 28 >psm: data 08 00 00 >psm: data 08 00 00 >psm: status 00 02 64 >psm0 at 0x60-0x64 irq 12 on motherboard >psm0: model Generic PS/2 mouse, device ID 0, 3 buttons >psm0: config:00000000, flags:00000000, packet size:3 >psm0: syncmask:c0, syncbits:00 >fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa >fdc0: FIFO enabled, 8 bytes threshold >fd0: 1.44MB 3.5in >wdc0 not found at 0x1f0 >wdc1 at 0x170-0x177 irq 15 on isa >wdc1: unit 0 (atapi): , removable, dma, iordy >wcd0: 2412/5512KB/sec, 128KB cache, audio play, 256 volume levels, ejectable tray >wcd0: no disc inside, unlocked >npx0 on motherboard >npx0: INT 16 interface >apm0: disabled, not probed. >imasks: bio c0088040, tty c007509a, net c007509a >BIOS Geometries: > 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 0 accounted for >Device configuration finished. >bpf: tun0 attached >bpf: sl0 attached >bpf: ppp0 attached >new masks: bio c0088040, tty c007509a, net c007509a >bpf: lo0 attached >Waiting 15 seconds for SCSI devices to settle >(noperiph:ahc0:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. >(noperiph:ahc1:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. >ahc0: Selection Timeout on A:1. 1 SCBs aborted >ahc1: Selection Timeout on A:0. 1 SCBs aborted >ahc0: Selection Timeout on A:2. 1 SCBs aborted >ahc1: Selection Timeout on A:1. 1 SCBs aborted >ahc0: Selection Timeout on A:3. 1 SCBs aborted >ahc1: Selection Timeout on A:2. 1 SCBs aborted >ahc0: Selection Timeout on A:4. 1 SCBs aborted >ahc1: Selection Timeout on A:3. 1 SCBs aborted >ahc0: Selection Timeout on A:5. 1 SCBs aborted >ahc1: Selection Timeout on A:4. 1 SCBs aborted >ahc0: Selection Timeout on A:6. 1 SCBs aborted >ahc1: Selection Timeout on A:5. 1 SCBs aborted >ahc0: Selection Timeout on A:8. 1 SCBs aborted >ahc1: Selection Timeout on A:6. 1 SCBs aborted >ahc0: Selection Timeout on A:9. 1 SCBs aborted >ahc1: Selection Timeout on A:8. 1 SCBs aborted >ahc0: Selection Timeout on A:10. 1 SCBs aborted >ahc1: Selection Timeout on A:9. 1 SCBs aborted >ahc0: Selection Timeout on A:11. 1 SCBs aborted >ahc1: Selection Timeout on A:10. 1 SCBs aborted >ahc0: Selection Timeout on A:12. 1 SCBs aborted >ahc1: Selection Timeout on A:11. 1 SCBs aborted >ahc0: Selection Timeout on A:13. 1 SCBs aborted >ahc1: Selection Timeout on A:12. 1 SCBs aborted >ahc0: Selection Timeout on A:14. 1 SCBs aborted >ahc1: Selection Timeout on A:13. 1 SCBs aborted >ahc0: Selection Timeout on A:15. 1 SCBs aborted >ahc0: target 0 using 16bit transfers >ahc0: target 0 synchronous at 40.0MHz, offset = 0xf >ahc1: Selection Timeout on A:14. 1 SCBs aborted >ahc1: Selection Timeout on A:15. 1 SCBs aborted >pass0 at ahc0 bus 0 target 0 lun 0 >pass0: Fixed Direct Access SCSI2 device >pass0: Serial Number LJ587842000019141CSZ >pass0: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled >da0 at ahc0 bus 0 target 0 lun 0 >da0: Fixed Direct Access SCSI2 device >da0: Serial Number LJ587842000019141CSZ >da0: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled >da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) >Considering MFS root f/s. >No MFS image available as root f/s. >Considering FFS root f/s. >changing root device to da0s4a >da0s1: type 0x6, start 63, end = 4192964, size 4192902 : OK >da0s2: type 0x82, start 4192965, end = 4289354, size 96390 : OK >da0s3: type 0x83, start 4289355, end = 11454344, size 7164990 : OK >da0s4: type 0xa5, start 11454345, end = 17767889, size 6313545 : OK > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > > ------------------------------------- Peter Johnson ------------------------------------- locke@mcs.net http://locke.home.ml.org PGP Keys available from above address. ------------------------------------- Freelance C/C++/Java/Pascal/Asm programmer for DJGPP, Borland, and Watcom compilers Member of BiLogic demo group -> http://BiLogic.home.ml.org/ ------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 10:46:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28397 for freebsd-current-outgoing; Thu, 10 Dec 1998 10:46:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28069; Thu, 10 Dec 1998 10:45:32 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id SAA15259; Thu, 10 Dec 1998 18:45:23 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id JAA42419; Thu, 10 Dec 1998 09:21:55 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812100921.JAA42419@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: oZZ!!! cc: current@FreeBSD.ORG, peter@FreeBSD.ORG Subject: Re: zlib-1.1.3 ??? In-reply-to: Your message of "Thu, 10 Dec 1998 02:22:47 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Thu, 10 Dec 1998 09:21:54 +0000 From: Brian Somers Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id KAA28108 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Hello! > What about of new version of zlib??? > why it not in -current source-tree ??? > (now in my -current zlib-1.1.1) Peter (cc'd) said he'd do the update after 3.0-RELEASE :-) > Rgdz, -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 11:50:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06281 for freebsd-current-outgoing; Thu, 10 Dec 1998 11:50:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06272 for ; Thu, 10 Dec 1998 11:50:09 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.054 #18) id 0zoAvn-0000D2-00 for freebsd-current@freebsd.org; Thu, 10 Dec 1998 18:35:19 +0000 Date: Thu, 10 Dec 1998 18:35:19 +0000 From: Ben Smithurst To: freebsd-current@FreeBSD.ORG Subject: panic: ffs_blkfree: bad size Message-ID: <19981210183519.A725@scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.94.17i (FreeBSD/3.0-CURRENT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone know what could have caused this: dev = 0x40002, bno = 124, bsize = 8192, size = 8192, fs = /home panic: ffs_blkfree: bad size Also, don't know if it's relevant, but this message appeared shortly before the crash: Dec 10 16:27:06 scientia /kernel: wd0s2a: reverting to non-multi sector mode reading fsbn 23904 of 23904-23919 (wd0s2 bn 23904; cn 5 tn 59 sn 27)wd0: status 51 error 4 (Probably not relevant, since /home is wd0s3, but if that problem affected the whole of wd0 somehow it could be relevant.) FreeBSD -current, ~1 week old (not sure exactly how old). -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 12:26:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11226 for freebsd-current-outgoing; Thu, 10 Dec 1998 12:26:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA11215 for ; Thu, 10 Dec 1998 12:26:04 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id HAA15535; Fri, 11 Dec 1998 07:36:47 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812102036.HAA15535@cimlogic.com.au> Subject: Re: Make World Failed In-Reply-To: <366FEB82.9C668E66@webwizard.org.mx> from Edwin Culp at "Dec 10, 98 09:40:50 am" To: eculp@webwizard.org.mx (Edwin Culp) Date: Fri, 11 Dec 1998 07:36:46 +1100 (EST) Cc: freebsd-current@FreeBSD.ORG 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 Edwin Culp wrote: > With: > install -c -s -o root -g wheel -m 555 bdes /usr/bin > install -c -o root -g wheel -m 444 bdes.1.gz /usr/share/man/man1 > ===> etc > install -c -o root -g wheel -m 644 fbtab auth.conf rc.atm rc.devfs > /etc > install: fbtab: No such file or directory > *** Error code 71 Does that file exist in your /usr/src/etc? If so, I guess my makefile change needs `cd ${.CURDIR};' added before the ${INSTALL}. Try that. -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 12:46:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14018 for freebsd-current-outgoing; Thu, 10 Dec 1998 12:46:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nmail.devrycols.edu (nmail.devrycols.edu [199.218.238.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA14000 for ; Thu, 10 Dec 1998 12:46:13 -0800 (PST) (envelope-from jm7996@devrycols.edu) Received: from cis061 [131.187.253.210] by nmail.devrycols.edu (SMTPD32-4.07) id A2F5AC00F4; Thu, 10 Dec 1998 15:45:41 EST Message-Id: <3.0.5.32.19981210154042.0079b8e0@devrycols.edu> X-Sender: jm7996@devrycols.edu X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 10 Dec 1998 15:40:42 -0500 To: moore@wolfenet.com, freebsd-current@FreeBSD.ORG From: "James A. Mutter" Subject: Re: NTIMECOUNTER and calcru... In-Reply-To: <199812101803.KAA67960@roscoe.mobile.cravegames.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check the faq at http://www.xfree86.org/FAQ/#GLINT - It would appear that the X folks are aware of the problem and will release new binaries soon. Included in the FAQ is a patch if you are building from source. At 10:03 AM 12/10/98 -0800, Tim Moore wrote: >I had been following the negative calcru discussion with moderate >interest until I got a new machine that exhibits the "calcru: negative >time" problem. The machine is a 400 Mhz Dell with a Diamond Fire GL >1000 Pro video card; this sounds a lot like a machine on which the >problem had been seen, so I had high hopes for the NTIMECOUNTER fix. >However, it doesn't seem to make a difference, even with NTIMECOUNTER >set to 2000. For testing I've been doing "sysctl -w >kern.timecounter.method=1" in single user mode before going multi-user >and starting X. As soon as X comes up the calcru messages start >spewing. > >Is there hope for this machine and video card? Here's the >configuration file and dmesg. > >Thanks, >Tim > ># ># GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks ># ># For more information read the handbook part System Administration -> ># Configuring the FreeBSD Kernel -> The Configuration File. ># The handbook is available in /usr/share/doc/handbook or online as ># latest version from the FreeBSD World Wide Web server ># ># ># An exhaustive list of options and more detailed explanations of the ># device lines is present in the ./LINT configuration file. If you are ># in doubt as to the purpose or necessity of a line, check first in LINT. ># ># $Id: GENERIC,v 1.125 1998/10/16 01:30:11 obrien Exp $ > >machine "i386" >cpu "I686_CPU" >ident BELUSHI >maxusers 32 > >options MATH_EMULATE #Support for x87 emulation >options INET #InterNETworking >options FFS #Berkeley Fast Filesystem >options FFS_ROOT #FFS usable as root device [keep this!] >options MFS #Memory Filesystem >options MFS_ROOT #MFS usable as root device, "MFS" req'ed >options NFS #Network Filesystem >options NFS_ROOT #NFS usable as root device, "NFS" req'ed >options MSDOSFS #MSDOS Filesystem >options "CD9660" #ISO 9660 Filesystem >options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed >options PROCFS #Process filesystem >options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] >options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device >options UCONSOLE #Allow users to grab the console >options FAILSAFE #Be conservative >options USERCONFIG #boot -c editor >options VISUAL_USERCONFIG #visual boot -c editor > >config kernel root on wd0 > >controller isa0 >controller eisa0 >controller pci0 > >controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 >disk fd0 at fdc0 drive 0 >disk fd1 at fdc0 drive 1 ># Unless you know very well what you're doing, leave ft0 at drive 2, or ># remove the line entirely if you don't need it. Trying to configure ># it on another unit might cause surprises, see PR kern/7176. >#tape ft0 at fdc0 drive 2 > >options "CMD640" # work around CMD640 chip deficiency >controller wdc0 at isa? port "IO_WD1" bio irq 14 >disk wd0 at wdc0 drive 0 >disk wd1 at wdc0 drive 1 > >controller wdc1 at isa? port "IO_WD2" bio irq 15 >disk wd2 at wdc1 drive 0 >disk wd3 at wdc1 drive 1 > >options ATAPI #Enable ATAPI support for IDE bus >options ATAPI_STATIC #Don't do it as an LKM >device wcd0 #IDE CD-ROM >device wfd0 #IDE Floppy (e.g. LS-120) > ># A single entry for any of these controllers (ncr, ahb, ahc, amd) is ># sufficient for any number of installed devices. >controller ahb0 >controller ahc0 > ># This controller offers a number of configuration options, too many to ># document here - see the LINT file in this directory and look up the ># dpt0 entry there for much fuller documentation on this. > >controller scbus0 > >device da0 > >device sa0 > >device pass0 > >device cd0 #Only need one of these, the code dynamically grows > ># ># dano - commented out wt0, mcd0, matcd0, scd0 ># >#device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr >#device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr > >#controller matcd0 at isa? port 0x230 bio > >#device scd0 at isa? port 0x230 bio > ># syscons is the default console driver, resembling an SCO console >device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr ># Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver >#device vt0 at isa? port "IO_KBD" conflicts tty irq 1 vector pcrint >#options XSERVER # support for X server >#options FAT_CURSOR # start with block cursor ># If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines >#options PCVT_SCANSET=2 # IBM keyboards are non-std > >device npx0 at isa? port "IO_NPX" irq 13 vector npxintr > ># ># Laptop support (see LINT for more options) ># >device apm0 at isa? disable flags 0x31 # Advanced Power Management > ># PCCARD (PCMCIA) support >#controller card0 >#device pcic0 at card? >#device pcic1 at card? > >device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector siointr >device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr >device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr >device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr > >device lpt0 at isa? port? tty irq 7 vector lptintr > >device psm0 at isa? port "IO_KBD" conflicts tty irq 12 vector psmintr > ># Order is important here due to intrusive probes, do *not* alphabetize ># this list of network interfaces until the probes have been fixed. ># Right now it appears that the ie0 must be probed before ep0. See ># revision 1.20 of this file. >device xl0 > >pseudo-device loop >pseudo-device ether >pseudo-device sl 1 >pseudo-device ppp 1 >pseudo-device tun 1 >pseudo-device pty 16 >pseudo-device gzip # Exec gzipped a.out's > ># KTRACE enables the system-call tracing facility ktrace(2). ># This adds 4 KB bloat to your kernel, and slightly increases ># the costs of each syscall. >options KTRACE #kernel tracing > ># This provides support for System V shared memory. ># >options SYSVSHM > ># The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be ># aware of the legal and administrative consequences of enabling this ># option. The number of devices determines the maximum number of ># simultaneous BPF clients programs runnable. >pseudo-device bpfilter 4 #Berkeley packet filter > ># These are attempts to get around the "calcru negative" problems which seem to ># be caused by XFree86 and the Diamond FireGL video card. > >options NTIMECOUNTER=2000 >options "MSGBUF_SIZE=40960" > >Copyright (c) 1992-1998 FreeBSD Inc. >Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. >FreeBSD 3.0-CURRENT #8: Wed Dec 9 09:32:15 PST 1998 > tmoore@roscoe.mobile.cravegames.com:/usr/src/sys/compile/BELUSHI >Calibrating clock(s) ... TSC clock: 398797485 Hz, i8254 clock: 1193253 Hz >CLK_USE_I8254_CALIBRATION not specified - using default frequency >Timecounter "i8254" frequency 1193182 Hz >CLK_USE_TSC_CALIBRATION not specified - using old calibration method >CPU: Pentium II (quarter-micron) (398.78-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping=2 > Features=0x183fbff> >real memory = 134217728 (131072K bytes) >Physical memory chunk(s): >0x00001000 - 0x0009efff, 647168 bytes (158 pages) >0x002a4000 - 0x07ff5fff, 131407872 bytes (32082 pages) >config> quit >avail memory = 127598592 (124608K bytes) >Found BIOS32 Service Directory header at 0xf00ffe80 >Entry = 0xffe90 (0xf00ffe90) Rev = 0 Len = 1 >PCI BIOS entry at 0xca9e >SMIBIOS header at 0xf00fb160 >Version 2.2 >Table at 0xfb180, 84 entries, 2922 bytes, largest entry 179 bytes >DMI header at 0xf00fb170 >Version 2.2 >Table at 0xfb180, 84 entries, 2922 bytes >Other BIOS signatures found: >ACPI: 000fdf30 >$PnP: 000fe2d0 >Preloaded elf kernel "kern.new" at 0xf0297000. >Math emulator present >pci_open(1): mode 1 addr port (0x0cf8) is 0x80000058 >pci_open(1a): mode1res=0x80000000 (0x80000000) >pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71908086) >Probing for devices on PCI bus 0: >found-> vendor=0x8086, dev=0x7190, revid=0x02 > class=06-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[0]: type 3, range 32, base f0000000, size 26 >chip0: rev 0x02 on pci0.0.0 >found-> vendor=0x8086, dev=0x7191, revid=0x02 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=1 secondarybus=1 >chip1: rev 0x02 on pci0.1.0 >found-> vendor=0x8086, dev=0x7110, revid=0x02 > class=06-01-00, hdrtype=0x00, mfdev=1 > subordinatebus=0 secondarybus=0 >chip2: rev 0x02 on pci0.7.0 >found-> vendor=0x8086, dev=0x7111, revid=0x01 > class=01-01-80, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > map[0]: type 4, range 32, base 0000ffa0, size 4 >ide_pci0: rev 0x01 on pci0.7.1 >intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 >intel_piix_status: primary master fastDMAonly disabled, pre/post disabled, >intel_piix_status: IORDY sampling disabled, >intel_piix_status: fast PIO disabled >intel_piix_status: primary master/slave sample = 5, master/slave recovery = 4 >intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, >intel_piix_status: IORDY sampling disabled, >intel_piix_status: fast PIO disabled >ide_pci: busmaster 0 status: 04 from port: 0000ffa2 >intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 >intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, >intel_piix_status: IORDY sampling enabled, >intel_piix_status: fast PIO enabled >intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 1 >intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, >intel_piix_status: IORDY sampling disabled, >intel_piix_status: fast PIO disabled >ide_pci: busmaster 1 status: 20 from port: 0000ffaa >ide_pci: ide1:0 has been configured for DMA by BIOS >found-> vendor=0x8086, dev=0x7112, revid=0x01 > class=0c-03-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=d, irq=14 > map[0]: type 4, range 32, base 0000dce0, size 5 >found-> vendor=0x8086, dev=0x7113, revid=0x02 > class=06-80-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 >chip3: rev 0x02 on pci0.7.3 >found-> vendor=0x10b7, dev=0x9055, revid=0x00 > class=02-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=14 > map[0]: type 4, range 32, base 0000dc00, size 7 > map[1]: type 1, range 32, base fe000000, size 7 >xl0: <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 14 on pci0.17.0 >xl0: Ethernet address: 00:c0:4f:72:ed:56 >xl0: media options word: a >xl0: probing for a PHY >xl0: checking address: 0 >xl0: checking address: 1 >xl0: checking address: 2 >xl0: checking address: 3 >xl0: checking address: 4 >xl0: checking address: 5 >xl0: checking address: 6 >xl0: checking address: 7 >xl0: checking address: 8 >xl0: checking address: 9 >xl0: checking address: 10 >xl0: checking address: 11 >xl0: checking address: 12 >xl0: checking address: 13 >xl0: checking address: 14 >xl0: checking address: 15 >xl0: checking address: 16 >xl0: checking address: 17 >xl0: checking address: 18 >xl0: checking address: 19 >xl0: checking address: 20 >xl0: checking address: 21 >xl0: checking address: 22 >xl0: checking address: 23 >xl0: checking address: 24 >xl0: found PHY at address 24, vendor id: 0 device id: 0 >xl0: PHY type: >xl0: found 10baseT >xl0: found 100baseTX >xl0: autoneg complete, link status good (full-duplex, 100Mbps) >bpf: xl0 attached >found-> vendor=0x1011, dev=0x0024, revid=0x03 > class=06-04-00, hdrtype=0x01, mfdev=0 > subordinatebus=2 secondarybus=2 >chip4: rev 0x03 on pci0.19.0 >Probing for devices on PCI bus 1: >found-> vendor=0x104c, dev=0x3d07, revid=0x01 > class=03-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=11 > map[0]: type 1, range 32, base fcfe0000, size 17 > map[1]: type 1, range 32, base fc000000, size 23 > map[2]: type 1, range 32, base fb800000, size 23 >vga0: rev 0x01 int a irq 11 on pci1.0.0 >Probing for devices on PCI bus 2: >found-> vendor=0x9005, dev=0x001f, revid=0x00 > class=01-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=10 > map[0]: type 4, range 32, base 0000ec00, size 8 > map[1]: type 1, range 64, base f9fff000, size 12 > map[2]: type 0, range 0, base 00000000, size 0 >ahc0: rev 0x00 int a irq 10 on pci2.10.0 >ahc0: Reading SEEPROM...done. >ahc0: BIOS eeprom not present >ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs >ahc0: Resetting Channel A >ahc0: Downloading Sequencer Program... 391 instructions downloaded >found-> vendor=0x9004, dev=0x8078, revid=0x01 > class=01-00-00, hdrtype=0x00, mfdev=0 > subordinatebus=0 secondarybus=0 > intpin=a, irq=10 > map[0]: type 4, range 32, base 0000e800, size 8 > map[1]: type 1, range 32, base f9ffe000, size 12 >ahc1: rev 0x01 int a irq 10 on pci2.14.0 > using shared irq10. >ahc1: Reading SEEPROM...done. >ahc1: internal 50 cable not present, internal 68 cable not present >ahc1: external cable not present >ahc1: BIOS eeprom is present >ahc1: High byte termination Enabled >ahc1: Low byte termination Enabled >ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs >ahc1: Resetting Channel A >ahc1: Downloading Sequencer Program... 411 instructions downloaded >Probing for devices on the ISA bus: >video: RTC equip. code:0x03, DCC code:0x09 >video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 >video: param table EGA/VGA:0, CGA/MDA:0 >video: rows_offset:1 >video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 >video#0: init mode:24, bios mode:3, current mode:24 >video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k >video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 >video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 >video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 >video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 >video#0: WARNING: video mode switching is not fully supported on this adapter >VGA parameters upon power-up >50 18 10 00 00 08 03 00 02 6f 5f 4f 50 82 55 81 >bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 >b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c >3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff >VGA parameters in BIOS for mode 24 >50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 >bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 >b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c >3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff >EGA/VGA parameters to be used for mode 24 >50 18 10 00 00 08 03 00 02 6f 5f 4f 50 82 55 81 >bf 1f 00 4f 0d 0e 00 00 07 80 9c 8e 8f 28 1f 96 >b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c >3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff >sc0: the current keyboard controller command byte 0065 >kbdio: DIAGNOSE status:0055 >kbdio: TEST_KBD_PORT status:0000 >kbdio: RESET_KBD return code:00fa >kbdio: RESET_KBD status:00aa >sc0: keyboard device ID: ab41 >sc0 at 0x60-0x6f irq 1 on motherboard >sc0: VGA color <16 virtual consoles, flags=0x0> >sio0: irq maps: 0x1 0x11 0x1 0x1 >sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa >sio0: type 16550A >sio1: irq maps: 0x1 0x9 0x1 0x1 >sio1 at 0x2f8-0x2ff irq 3 on isa >sio1: type 16550A >sio2: disabled, not probed. >sio3: disabled, not probed. >lpt0 at 0x378-0x37f irq 7 on isa >lpt0: Interrupt-driven port >lp0: TCP/IP capable interface >bpf: lp0 attached >psm0: current command byte:0065 >kbdio: TEST_AUX_PORT status:0000 >kbdio: RESET_AUX return code:00fa >kbdio: RESET_AUX status:00aa >kbdio: RESET_AUX ID:0000 >psm: status 00 02 64 >psm: status 90 03 3c >psm: status 90 03 3c >psm: status 90 03 3c >psm: status 00 00 28 >psm: data 08 00 00 >psm: data 08 00 00 >psm: status 00 02 64 >psm0 at 0x60-0x64 irq 12 on motherboard >psm0: model Generic PS/2 mouse, device ID 0, 3 buttons >psm0: config:00000000, flags:00000000, packet size:3 >psm0: syncmask:c0, syncbits:00 >fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa >fdc0: FIFO enabled, 8 bytes threshold >fd0: 1.44MB 3.5in >wdc0 not found at 0x1f0 >wdc1 at 0x170-0x177 irq 15 on isa >wdc1: unit 0 (atapi): , removable, dma, iordy >wcd0: 2412/5512KB/sec, 128KB cache, audio play, 256 volume levels, ejectable tray >wcd0: no disc inside, unlocked >npx0 on motherboard >npx0: INT 16 interface >apm0: disabled, not probed. >imasks: bio c0088040, tty c007509a, net c007509a >BIOS Geometries: > 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors > 0 accounted for >Device configuration finished. >bpf: tun0 attached >bpf: sl0 attached >bpf: ppp0 attached >new masks: bio c0088040, tty c007509a, net c007509a >bpf: lo0 attached >Waiting 15 seconds for SCSI devices to settle >(noperiph:ahc0:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. >(noperiph:ahc1:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. >ahc0: Selection Timeout on A:1. 1 SCBs aborted >ahc1: Selection Timeout on A:0. 1 SCBs aborted >ahc0: Selection Timeout on A:2. 1 SCBs aborted >ahc1: Selection Timeout on A:1. 1 SCBs aborted >ahc0: Selection Timeout on A:3. 1 SCBs aborted >ahc1: Selection Timeout on A:2. 1 SCBs aborted >ahc0: Selection Timeout on A:4. 1 SCBs aborted >ahc1: Selection Timeout on A:3. 1 SCBs aborted >ahc0: Selection Timeout on A:5. 1 SCBs aborted >ahc1: Selection Timeout on A:4. 1 SCBs aborted >ahc0: Selection Timeout on A:6. 1 SCBs aborted >ahc1: Selection Timeout on A:5. 1 SCBs aborted >ahc0: Selection Timeout on A:8. 1 SCBs aborted >ahc1: Selection Timeout on A:6. 1 SCBs aborted >ahc0: Selection Timeout on A:9. 1 SCBs aborted >ahc1: Selection Timeout on A:8. 1 SCBs aborted >ahc0: Selection Timeout on A:10. 1 SCBs aborted >ahc1: Selection Timeout on A:9. 1 SCBs aborted >ahc0: Selection Timeout on A:11. 1 SCBs aborted >ahc1: Selection Timeout on A:10. 1 SCBs aborted >ahc0: Selection Timeout on A:12. 1 SCBs aborted >ahc1: Selection Timeout on A:11. 1 SCBs aborted >ahc0: Selection Timeout on A:13. 1 SCBs aborted >ahc1: Selection Timeout on A:12. 1 SCBs aborted >ahc0: Selection Timeout on A:14. 1 SCBs aborted >ahc1: Selection Timeout on A:13. 1 SCBs aborted >ahc0: Selection Timeout on A:15. 1 SCBs aborted >ahc0: target 0 using 16bit transfers >ahc0: target 0 synchronous at 40.0MHz, offset = 0xf >ahc1: Selection Timeout on A:14. 1 SCBs aborted >ahc1: Selection Timeout on A:15. 1 SCBs aborted >pass0 at ahc0 bus 0 target 0 lun 0 >pass0: Fixed Direct Access SCSI2 device >pass0: Serial Number LJ587842000019141CSZ >pass0: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled >da0 at ahc0 bus 0 target 0 lun 0 >da0: Fixed Direct Access SCSI2 device >da0: Serial Number LJ587842000019141CSZ >da0: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled >da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) >Considering MFS root f/s. >No MFS image available as root f/s. >Considering FFS root f/s. >changing root device to da0s4a >da0s1: type 0x6, start 63, end = 4192964, size 4192902 : OK >da0s2: type 0x82, start 4192965, end = 4289354, size 96390 : OK >da0s3: type 0x83, start 4289355, end = 11454344, size 7164990 : OK >da0s4: type 0xa5, start 11454345, end = 17767889, size 6313545 : OK > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 13:29:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20410 for freebsd-current-outgoing; Thu, 10 Dec 1998 13:29:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spook.navinet.net (spook.navinet.net [206.25.93.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20403 for ; Thu, 10 Dec 1998 13:28:58 -0800 (PST) (envelope-from forrie@forrie.com) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1/8.9.1) with SMTP id QAA00284 for ; Thu, 10 Dec 1998 16:28:17 -0500 (EST) Message-Id: <4.1.19981210162745.0094ca90@206.25.93.69> X-Sender: forrie@206.25.93.69 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 10 Dec 1998 16:28:39 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: 3.0 reboot Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was performing some floppy disk mount attempt (mount_msdos), and the system suddenly rebooted. This is FreeBSD-3.0-CURRENT (build world yesterday). FYI. Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 13:59:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24886 for freebsd-current-outgoing; Thu, 10 Dec 1998 13:59:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from send104.yahoomail.com (send104.yahoomail.com [205.180.60.122]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA24879 for ; Thu, 10 Dec 1998 13:59:45 -0800 (PST) (envelope-from osiris2002@yahoo.com) Message-ID: <19981210203123.22990.rocketmail@send104.yahoomail.com> Received: from [139.141.221.1] by send104.yahoomail.com; Fri, 11 Dec 1998 07:31:23 EST Date: Fri, 11 Dec 1998 07:31:23 +1100 (EST) From: Charlie Roots Subject: Help needed, recent cvsup won't compile To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there; I CVSUPed recently FreeBSD-Current, and the Buildworld is broken on some __error thing undeclared in many *.c files What's wrong ? I used to have a FreeBSD-current since last cvsup about 8 months back in time (using aout format then for binaries), now the new thing is elf format, do I have to recompile every single binary on the system to elf format, and I don't mean FreeBSD binaries but those from ports and other applications, I noticed that the new kernel (assuming someone will tell me how to overcome the broken SNAPSHOT), is supposed to support both aout and elf for the time being, but will end this generousity (don't know why) in the near future (release 3.1 I guess). ANY help is greatly appreciated. please reply to osiris2002@yahoo.com as I am temporarily out of the mailing lists. == MAY THE FORCE BE WITH YOU. _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 15:38:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07966 for freebsd-current-outgoing; Thu, 10 Dec 1998 15:38:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-dc.dialup.hilink.com.au [203.2.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA07939 for ; Thu, 10 Dec 1998 15:38:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA00873; Thu, 10 Dec 1998 15:35:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812102335.PAA00873@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa cc: Mark Murray , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 10 Dec 1998 13:28:57 +0900." <199812100428.NAA02545@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Dec 1998 15:35:42 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > FreeBSD 3.0 will turn off the laptop (on my Libretto 70) with > > shutdown -h. What is wrong with this? > > It is wrong. > > In traditional UNIX, if you want to power-off, use another command > shutdown -h, example halt -p or shutdown -x. Because, anytime > shutdown -h, not want to power-off, sometime want go to ROM monitor. You enter the PC "ROM monitor" equivalent by rebooting. > Second problem, 3.0-RELEASE's implement problem. It is hard > cording in src/sys/i386/i386/machdep.c:cpu_power_down(). If you > want to add new power-control mechanism, you must change that code. > > My patch using at_shutdown() for registration power-control > routine, so change power-control driver only. You're out of date; we do this already. Your point is good though; we should be testing for RB_POWEROFF, not RB_HALT. > See PR i386/8638. I've closed it. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 15:53:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09897 for freebsd-current-outgoing; Thu, 10 Dec 1998 15:53:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-dc.dialup.hilink.com.au [203.2.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09889 for ; Thu, 10 Dec 1998 15:53:45 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01612; Wed, 9 Dec 1998 17:09:29 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812100109.RAA01612@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Nathan Dorfman cc: Mike Smith , NAKAGAWA Yoshihisa , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Wed, 09 Dec 1998 19:24:59 EST." <19981209192459.A18996@rtfm.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 09 Dec 1998 17:09:29 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Wed, Dec 09, 1998 at 03:54:30PM -0800, Mike Smith wrote: > > > > > > Do NE2000 Compatible PCMCIA cards work under PAO3, as it is now? > > > If so, is the development snapshot available anywhere? > > > > They work fine under stock 2.2 and 3.0 (this message is being sent > > using one). > > I tried with no success whatsoever to get this setup to work with > 3.0-R. The no-brand card didn't even have an entry in 3.0-R's > pccard.conf.sample. Worked fine with PAO-2.2.7, all I had to do was > tell it not to use IRQs 1-10. So put the pccard.conf entry that matched the card from PAO in your stock pccard.conf, and make the same IRQ config changes. > Also, the 3.0-R pcic would come up at IRQ 5, which is wrong. What does "wrong" mean in this context? The pcic IRQ is programmable; it'll come up where the code tells it to. If you mean that IRQ 5 is occupied by another device, fine, point the pcic somewhere else. (Use userconfig to change the IRQ setting IIRQ.) -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 15:54:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10125 for freebsd-current-outgoing; Thu, 10 Dec 1998 15:54:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-dc.dialup.hilink.com.au [203.2.144.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10109; Thu, 10 Dec 1998 15:54:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id PAA01072; Thu, 10 Dec 1998 15:52:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812102352.PAA01072@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG cc: mobile@FreeBSD.ORG Subject: HEADS UP : laptop power-down change Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Dec 1998 15:52:15 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just a quick warning; the default behaviour of the "halt" flag on APM systems is now to halt, not to power down. Use the '-p' flag to halt or shutdown (the latter will be added in a moment) to power off. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 16:01:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11139 for freebsd-current-outgoing; Thu, 10 Dec 1998 16:01:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.mt.sri.com (sri-gw.MT.net [206.127.105.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11118 for ; Thu, 10 Dec 1998 16:01:20 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.8/8.8.8) with SMTP id RAA12651; Thu, 10 Dec 1998 17:01:05 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id RAA25044; Thu, 10 Dec 1998 17:01:04 -0700 Date: Thu, 10 Dec 1998 17:01:04 -0700 Message-Id: <199812110001.RAA25044@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mike Smith Cc: Nathan Dorfman , NAKAGAWA Yoshihisa , current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812100109.RAA01612@dingo.cdrom.com> References: <19981209192459.A18996@rtfm.net> <199812100109.RAA01612@dingo.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Also, the 3.0-R pcic would come up at IRQ 5, which is wrong. > > What does "wrong" mean in this context? The pcic IRQ is programmable; > it'll come up where the code tells it to. If you mean that IRQ 5 is > occupied by another device, fine, point the pcic somewhere else. (Use > userconfig to change the IRQ setting IIRQ.) There is no way to tell the PCIC which IRQ to use. See the recent discussion between me and one of the PAO developers regarding how they solved it. Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 17:07:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20296 for freebsd-current-outgoing; Thu, 10 Dec 1998 17:07:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA20280; Thu, 10 Dec 1998 17:07:42 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoH38-00010G-00; Thu, 10 Dec 1998 18:07:18 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id SAA65223; Thu, 10 Dec 1998 18:06:09 -0700 (MST) Message-Id: <199812110106.SAA65223@harmony.village.org> To: Mike Smith Subject: Re: HEADS UP : laptop power-down change Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Dec 1998 15:52:15 PST." <199812102352.PAA01072@dingo.cdrom.com> References: <199812102352.PAA01072@dingo.cdrom.com> Date: Thu, 10 Dec 1998 18:06:08 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812102352.PAA01072@dingo.cdrom.com> Mike Smith writes: : Just a quick warning; the default behaviour of the "halt" flag on APM : systems is now to halt, not to power down. Use the '-p' flag to halt : or shutdown (the latter will be added in a moment) to power off. Why the change? The current behavior seems right to me. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 17:11:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20830 for freebsd-current-outgoing; Thu, 10 Dec 1998 17:11:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA20819 for ; Thu, 10 Dec 1998 17:11:14 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoH6i-00010P-00; Thu, 10 Dec 1998 18:11:00 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id SAA65255; Thu, 10 Dec 1998 18:09:50 -0700 (MST) Message-Id: <199812110109.SAA65255@harmony.village.org> To: Mike Smith Subject: Re: PAO Integration? Cc: NAKAGAWA Yoshihisa , Mark Murray , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Dec 1998 15:35:42 PST." <199812102335.PAA00873@dingo.cdrom.com> References: <199812102335.PAA00873@dingo.cdrom.com> Date: Thu, 10 Dec 1998 18:09:50 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : > > FreeBSD 3.0 will turn off the laptop (on my Libretto 70) with : > > shutdown -h. What is wrong with this? : > : > It is wrong. Why? Traditionally Unix hasn't run on hardware that has software power off. Who can say what traditional unix is when the hardware has a new feature? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 17:41:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23053 for freebsd-current-outgoing; Thu, 10 Dec 1998 17:41:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-dd.dialup.hilink.com.au [203.2.144.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23047 for ; Thu, 10 Dec 1998 17:41:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA01409; Thu, 10 Dec 1998 17:01:56 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812110101.RAA01409@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa cc: Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 10 Dec 1998 13:38:52 +0900." <199812100438.NAA02560@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Dec 1998 17:01:56 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > So put the pccard.conf entry that matched the card from PAO in your > > stock pccard.conf, and make the same IRQ config changes. > > First, 3.0-RELEASE's pccard.conf.sample using fixed irq (example, > ed driver use 11 or 10 or 9, sometime use '?'). In PAO, enhanced > pccardd, so can use "any" and using "any" in pccard.conf.sample. Using 'any' works (for some values of works) in 3.0. > Second, PAO enhanced irq-pool, dynamic irq-pool. So, pccardd get > free-irq from kernel. This is an example of an unacceptable solution rerettably typical to the PAO project - you folks are *too*narrowly*focussed* on your needs. If you want to bring PAO up to date, you should be looking at the generic resource manager in sys/kern/subr_rman.c and the way that it is integrated within the new bus architecture. If Garrett hasn't already contacted the entire PAO group, consider this a formal request; if you're a PAO developer at all, and you're intetested in helping merge your development efforts with -current, talk to Garrett (wollman@freebsd.org) about subscribing to the new-bus mailing list. > Third, PAO changed PCIC attach ISA device. So, you want to change > PCIC's irq, you can use UserConfig. This is something that we should be doing indeed. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 17:46:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23610 for freebsd-current-outgoing; Thu, 10 Dec 1998 17:46:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23602 for ; Thu, 10 Dec 1998 17:46:35 -0800 (PST) (envelope-from peter.jeremy@auss2.alcatel.com.au) Received: by border.alcanet.com.au id <40351>; Fri, 11 Dec 1998 12:45:37 +1100 Date: Fri, 11 Dec 1998 12:46:14 +1100 From: Peter Jeremy Subject: Re: PAO Integration? To: current@FreeBSD.ORG Message-Id: <98Dec11.124537est.40351@border.alcanet.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > Traditionally Unix hasn't run on hardware that has software >power off. Who can say what traditional unix is when the hardware has >a new feature? Sun hardware has supported soft power-off for quite a while now. Solaris 2.x uses initlevel 5 to indicate power-off, with level 6 remaining `halt' (actually `go to rom monitor'). IMHO, there is a use for distinguishing `halt' and `power off'. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 17:48:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23872 for freebsd-current-outgoing; Thu, 10 Dec 1998 17:48:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from heaven.gigo.com (ppp.gigo.com [207.173.132.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23864 for ; Thu, 10 Dec 1998 17:48:36 -0800 (PST) (envelope-from jfesler@gigo.com) From: jfesler@gigo.com Received: by heaven.gigo.com (8.8.8/8.8.8) with SMTP id RAA19662; Thu, 10 Dec 1998 17:48:21 -0800 (PST) X-SMTP: helo heaven.gigo.com from jfesler@gigo.com server jfesler@heaven.gigo.com ip 207.173.133.57 Date: Thu, 10 Dec 1998 17:48:20 -0800 (PST) To: Warner Losh cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812110109.SAA65255@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Why? Traditionally Unix hasn't run on hardware that has software > power off. Who can say what traditional unix is when the hardware has > a new feature? Solaris on Sun equipment has been doing it a long time. I can telnet, shutdown with a state of 5, and bewm, buh-bye power. Workstations can be turned back on via keyboard; the servers I've used actually physically throws a power switch that has to be manually switched back on. Considering the age of the equipment and the OS level I'm using, I can safely say it's been doing it many years :-). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 18:07:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25849 for freebsd-current-outgoing; Thu, 10 Dec 1998 18:07:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-dd.dialup.hilink.com.au [203.2.144.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25830; Thu, 10 Dec 1998 18:07:52 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA00591; Thu, 10 Dec 1998 18:00:30 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812110200.SAA00591@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: Mike Smith , current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: HEADS UP : laptop power-down change In-reply-to: Your message of "Thu, 10 Dec 1998 18:06:08 MST." <199812110106.SAA65223@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Dec 1998 18:00:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199812102352.PAA01072@dingo.cdrom.com> Mike Smith writes: > : Just a quick warning; the default behaviour of the "halt" flag on APM > : systems is now to halt, not to power down. Use the '-p' flag to halt > : or shutdown (the latter will be added in a moment) to power off. > > Why the change? The current behavior seems right to me. RB_HALT means "halt", while RB_POWEROFF means "power off". On the i386 the two are a little blurred (because you don't normally halt except to power off) - this just restores some consistency. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 18:17:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26993 for freebsd-current-outgoing; Thu, 10 Dec 1998 18:17:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-dd.dialup.hilink.com.au [203.2.144.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26988 for ; Thu, 10 Dec 1998 18:17:41 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA00665; Thu, 10 Dec 1998 18:10:07 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812110210.SAA00665@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: NAKAGAWA Yoshihisa cc: Nate Williams , Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 10 Dec 1998 15:53:26 +0900." <199812100653.PAA02808@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Dec 1998 18:10:04 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I disagree. Just because some are ISA doesn't mean that all are ISA. > > Also, this makes it harder (not eaiser) to support CardBus in the > > future. > > I disagree 3.0-RELEASE style. ISA device, shuld be attach as ISA > device. PCI PCIC, like CardBus controller, shuld be attach as PCI > device. It should be separate PCIC core code from bus depend and > bus independ. PCICs are bridges, not devices. Treating a PCIC like an ISA device is a bad idea for many reasons. It's an error to confuse the physical and logical interfaces to a device. > CardBus support, we are planning on newconfig Project in near > future. Bus independ code is necessary. So, we use NetBSD(4.4BSD) > style bus and device configuration code. ... despite the fact that we have a clear roadmap which does not include the 'newconfig' model, is notably superior, and has already been deployed. If you really hope for your work to be relevant to FreeBSD in general, *please* spend some time to acquaint yourselves with the directions we're already taking. Much of the work that you still have to do on the newconfig stuff has already been done. Much more that newconfig doesn't address has also already been done, and in a fashion much more consistent with established interfaces (cf. the vnode interface). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 18:20:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27624 for freebsd-current-outgoing; Thu, 10 Dec 1998 18:20:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA27604; Thu, 10 Dec 1998 18:20:36 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoIBp-00011s-00; Thu, 10 Dec 1998 19:20:21 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id TAA65481; Thu, 10 Dec 1998 19:19:13 -0700 (MST) Message-Id: <199812110219.TAA65481@harmony.village.org> To: Mike Smith Subject: Re: HEADS UP : laptop power-down change Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Dec 1998 18:00:28 PST." <199812110200.SAA00591@dingo.cdrom.com> References: <199812110200.SAA00591@dingo.cdrom.com> Date: Thu, 10 Dec 1998 19:19:12 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812110200.SAA00591@dingo.cdrom.com> Mike Smith writes: : RB_HALT means "halt", while RB_POWEROFF means "power off". On the i386 : the two are a little blurred (because you don't normally halt except to : power off) - this just restores some consistency. Make halt generate a RB_POWEROFF and a halt -useless generate a RB_HALT. :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 18:21:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27788 for freebsd-current-outgoing; Thu, 10 Dec 1998 18:21:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA27782 for ; Thu, 10 Dec 1998 18:21:47 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoICz-00011y-00; Thu, 10 Dec 1998 19:21:33 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id TAA65513; Thu, 10 Dec 1998 19:20:24 -0700 (MST) Message-Id: <199812110220.TAA65513@harmony.village.org> To: jfesler@gigo.com Subject: Re: PAO Integration? Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Dec 1998 17:48:20 PST." References: Date: Thu, 10 Dec 1998 19:20:24 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message jfesler@gigo.com writes: : Solaris on Sun equipment has been doing it a long time. I can telnet, : shutdown with a state of 5, and bewm, buh-bye power. Workstations can be : turned back on via keyboard; the servers I've used actually physically : throws a power switch that has to be manually switched back on. : : Considering the age of the equipment and the OS level I'm using, I can : safely say it's been doing it many years :-). Solaris 2.4 or 2.5 was the first to support soft power off, if I recall correctly. In the timeline of unix, that can hardly be called "traditional." :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 18:29:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28260 for freebsd-current-outgoing; Thu, 10 Dec 1998 18:29:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-dd.dialup.hilink.com.au [203.2.144.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28255 for ; Thu, 10 Dec 1998 18:29:27 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id SAA00769; Thu, 10 Dec 1998 18:22:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812110222.SAA00769@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: current@FreeBSD.ORG Subject: Re: HEADS UP : laptop power-down change In-reply-to: Your message of "Thu, 10 Dec 1998 19:19:12 MST." <199812110219.TAA65481@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Dec 1998 18:22:09 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (I've taken this off -mobile, since it's not useful there.) > In message <199812110200.SAA00591@dingo.cdrom.com> Mike Smith writes: > : RB_HALT means "halt", while RB_POWEROFF means "power off". On the i386 > : the two are a little blurred (because you don't normally halt except to > : power off) - this just restores some consistency. > > Make halt generate a RB_POWEROFF and a halt -useless generate a > RB_HALT. :-) No. RB_POWEROFF and RB_HALT have very different meanings. The PC doesn't have a useful means for getting back to the resident firmware, but many other systems do. That's what RB_HALT is meant to do, while RB_POWEROFF is meant to power the system down. The two are mutually exclusive. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 20:04:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07430 for freebsd-current-outgoing; Thu, 10 Dec 1998 19:55:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07411 for ; Thu, 10 Dec 1998 19:55:17 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id WAA14178 for ; Thu, 10 Dec 1998 22:55:09 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA21143; Thu, 10 Dec 1998 22:55:08 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id WAA06058 for freebsd-current@freebsd.org; Thu, 10 Dec 1998 22:55:08 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812110355.WAA06058@bb01f39.unx.sas.com> Subject: inetd: realloc/free bug To: freebsd-current@freebsd.org Date: Thu, 10 Dec 1998 22:55:08 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL38 (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, Well, from reading the mail that's gone by, it appears that there is a possible fix for the inetd bug: inetd in realloc(): warning: junk pointer, too low to make sense. inetd in free(): warning: junk pointer, too low to make sense. I'm tired of seeing this and would appreciate it if someone would post the patch so we can use it until the appropriate folks make up their minds on the best way to fix it. Comments? Critiques? Pointers to a patch? Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 20:23:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA10858 for freebsd-current-outgoing; Thu, 10 Dec 1998 20:23:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA10853 for ; Thu, 10 Dec 1998 20:23:38 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoK6t-00014G-00; Thu, 10 Dec 1998 21:23:23 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id VAA65796; Thu, 10 Dec 1998 21:22:16 -0700 (MST) Message-Id: <199812110422.VAA65796@harmony.village.org> To: Mike Smith Subject: Re: HEADS UP : laptop power-down change Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Dec 1998 18:22:09 PST." <199812110222.SAA00769@dingo.cdrom.com> References: <199812110222.SAA00769@dingo.cdrom.com> Date: Thu, 10 Dec 1998 21:22:15 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812110222.SAA00769@dingo.cdrom.com> Mike Smith writes: : No. RB_POWEROFF and RB_HALT have very different meanings. The PC : doesn't have a useful means for getting back to the resident firmware, : but many other systems do. That's what RB_HALT is meant to do, while : RB_POWEROFF is meant to power the system down. The two are mutually : exclusive. I know... halt should turn the machine off. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 20:27:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11257 for freebsd-current-outgoing; Thu, 10 Dec 1998 20:27:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11250 for ; Thu, 10 Dec 1998 20:27:38 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id NAA03987; Fri, 11 Dec 1998 13:25:14 +0900 (JST) Message-Id: <199812110425.NAA03987@chandra.eatell.msr.prug.or.jp> To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 10 Dec 1998 15:35:42 PST." <199812102335.PAA00873@dingo.cdrom.com> Date: Fri, 11 Dec 1998 13:25:13 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You're out of date; we do this already. Your point is good though; we > should be testing for RB_POWEROFF, not RB_HALT. Thanks Mike, I read -current code, and I think that code is quite correct. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 Dec 10 20:55:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14189 for freebsd-current-outgoing; Thu, 10 Dec 1998 20:55:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14169 for ; Thu, 10 Dec 1998 20:55:26 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id NAA04025; Fri, 11 Dec 1998 13:52:18 +0900 (JST) Message-Id: <199812110452.NAA04025@chandra.eatell.msr.prug.or.jp> To: Warner Losh cc: jfesler@gigo.com, current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 10 Dec 1998 19:20:24 MST." <199812110220.TAA65513@harmony.village.org> Date: Fri, 11 Dec 1998 13:52:18 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Solaris 2.4 or 2.5 was the first to support soft power off, if I > recall correctly. In the timeline of unix, that can hardly be called > "traditional." :-) On SONY NEWS old WS, NEWS-OS 4.x support power-off by "shutdown -x". That OS is based on 4.3BSD. At least, "halt" and "power-off" is different mean on traditional UNIX. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 Dec 10 20:59:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14847 for freebsd-current-outgoing; Thu, 10 Dec 1998 20:59:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14832 for ; Thu, 10 Dec 1998 20:59:23 -0800 (PST) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.1/8.8.2) id WAA98890; Thu, 10 Dec 1998 22:58:40 -0600 (CST) Message-ID: <19981210225840.A98886@Denninger.Net> Date: Thu, 10 Dec 1998 22:58:40 -0600 From: Karl Denninger To: NAKAGAWA Yoshihisa , Warner Losh Cc: jfesler@gigo.com, current@FreeBSD.ORG Subject: Re: PAO Integration? References: <199812110220.TAA65513@harmony.village.org> <199812110452.NAA04025@chandra.eatell.msr.prug.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812110452.NAA04025@chandra.eatell.msr.prug.or.jp>; from NAKAGAWA Yoshihisa on Fri, Dec 11, 1998 at 01:52:18PM +0900 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 11, 1998 at 01:52:18PM +0900, NAKAGAWA Yoshihisa wrote: > > Solaris 2.4 or 2.5 was the first to support soft power off, if I > > recall correctly. In the timeline of unix, that can hardly be called > > "traditional." :-) > > On SONY NEWS old WS, NEWS-OS 4.x support power-off by "shutdown -x". > That OS is based on 4.3BSD. > > At least, "halt" and "power-off" is different mean on traditional UNIX. Uh, excuse me, but the NeXT machines were soft power-off. Including the first NeXT cubes. If you can count MACH as Unix, these qualify. -- -- Karl Denninger (karl@denninger.net) http://www.mcs.net/~karl I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 21:17:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16216 for freebsd-current-outgoing; Thu, 10 Dec 1998 21:17:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA16193; Thu, 10 Dec 1998 21:17:25 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoKwx-00018I-00; Thu, 10 Dec 1998 22:17:11 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id WAA66364; Thu, 10 Dec 1998 22:16:04 -0700 (MST) Message-Id: <199812110516.WAA66364@harmony.village.org> Subject: Re: HEADS UP : laptop power-down change To: Mike Smith , current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Dec 1998 18:06:08 MST." <199812110106.SAA65223@harmony.village.org> References: <199812110106.SAA65223@harmony.village.org> <199812102352.PAA01072@dingo.cdrom.com> Date: Thu, 10 Dec 1998 22:16:04 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Why the change? The current behavior seems right to me. Actually, rather than argue this into the ground, would you object to my implementing a options APM_MAP_HALT_TO_POWER_OFF and checking it in to apm.c and LINT? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 21:44:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18425 for freebsd-current-outgoing; Thu, 10 Dec 1998 21:44:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18419 for ; Thu, 10 Dec 1998 21:44:42 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id VAA09229; Thu, 10 Dec 1998 21:44:33 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma009225; Thu, 10 Dec 98 21:44:25 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id VAA21634; Thu, 10 Dec 1998 21:44:24 -0800 (PST) From: Archie Cobbs Message-Id: <199812110544.VAA21634@bubba.whistle.com> Subject: Re: inetd: realloc/free bug In-Reply-To: <199812110355.WAA06058@bb01f39.unx.sas.com> from "John W. DeBoskey" at "Dec 10, 98 10:55:08 pm" To: jwd@unx.sas.com (John W. DeBoskey) Date: Thu, 10 Dec 1998 21:44:24 -0800 (PST) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 John W. DeBoskey writes: > Well, from reading the mail that's gone by, it appears that there > is a possible fix for the inetd bug: > > inetd in realloc(): warning: junk pointer, too low to make sense. > inetd in free(): warning: junk pointer, too low to make sense. > > I'm tired of seeing this and would appreciate it if someone would > post the patch so we can use it until the appropriate folks make up > their minds on the best way to fix it. http://www.freebsd.org/cgi/query-pr.cgi?pr=8183 -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 Thu Dec 10 21:46:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18762 for freebsd-current-outgoing; Thu, 10 Dec 1998 21:46:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp ([202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18755 for ; Thu, 10 Dec 1998 21:46:41 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id OAA04099; Fri, 11 Dec 1998 14:43:38 +0900 (JST) Message-Id: <199812110543.OAA04099@chandra.eatell.msr.prug.or.jp> To: Mike Smith cc: Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 10 Dec 1998 17:01:56 PST." <199812110101.RAA01409@dingo.cdrom.com> Date: Fri, 11 Dec 1998 14:43:37 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If you want to bring PAO up to date, you should be looking at the > generic resource manager in sys/kern/subr_rman.c and the way that it > is integrated within the new bus architecture. I looked sys/kern/subr_rman.c, generic resource manager is quite correct. It is very necessary. Today's resource manager on PAO is quick and dirty hack, I agree. Because, until now we development 2.2-stable base and resource manager is necessary soon. In the future, we want to change generic resource manager base code. Does other PAO developer has different opinion? > If Garrett hasn't already contacted the entire PAO group, consider this > a formal request; if you're a PAO developer at all, and you're Sorry, I don't know. I will ask other PAO developer. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.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 Dec 10 21:47:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA18823 for freebsd-current-outgoing; Thu, 10 Dec 1998 21:47:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA18818; Thu, 10 Dec 1998 21:47:48 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id VAA09255; Thu, 10 Dec 1998 21:46:33 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma009251; Thu, 10 Dec 98 21:46:12 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id VAA21648; Thu, 10 Dec 1998 21:46:11 -0800 (PST) From: Archie Cobbs Message-Id: <199812110546.VAA21648@bubba.whistle.com> Subject: Re: mformat in free(): warning: junk pointer, too high to make sense. In-Reply-To: <19981210182938.B371@follo.net> from Eivind Eklund at "Dec 10, 98 06:29:38 pm" To: eivind@yes.no (Eivind Eklund) Date: Thu, 10 Dec 1998 21:46:11 -0800 (PST) Cc: vallo@matti.ee, current@FreeBSD.ORG, dg@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Eivind Eklund writes: > As for the inetd problem: We know what it is, we have a fix, and David > Greenman seems to be vetoing committing it due to its "inelegance". So let's see his version. -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 Thu Dec 10 21:50:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19015 for freebsd-current-outgoing; Thu, 10 Dec 1998 21:50:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19009; Thu, 10 Dec 1998 21:50:39 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA02927; Thu, 10 Dec 1998 21:49:48 -0800 (PST) To: Archie Cobbs cc: eivind@yes.no (Eivind Eklund), vallo@matti.ee, current@FreeBSD.ORG, dg@FreeBSD.ORG Subject: Re: mformat in free(): warning: junk pointer, too high to make sense. In-reply-to: Your message of "Thu, 10 Dec 1998 21:46:11 PST." <199812110546.VAA21648@bubba.whistle.com> Date: Thu, 10 Dec 1998 21:49:48 -0800 Message-ID: <2923.913355388@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > As for the inetd problem: We know what it is, we have a fix, and David > > Greenman seems to be vetoing committing it due to its "inelegance". > > So let's see his version. Why doesn't someone just commit it? David's already in hot water over his filesystem destroying fragmentation changes and I don't think anyone will side with him if you just bring the inetd change into -current at this point. :-) :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 22:00:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19387 for freebsd-current-outgoing; Thu, 10 Dec 1998 22:00:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19380; Thu, 10 Dec 1998 22:00:17 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id VAA09388; Thu, 10 Dec 1998 21:59:03 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma009386; Thu, 10 Dec 98 21:59:00 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id VAA21753; Thu, 10 Dec 1998 21:59:00 -0800 (PST) From: Archie Cobbs Message-Id: <199812110559.VAA21753@bubba.whistle.com> Subject: Re: mformat in free(): warning: junk pointer, too high to make sense. In-Reply-To: <199812110546.VAA21648@bubba.whistle.com> from Archie Cobbs at "Dec 10, 98 09:46:11 pm" To: archie@whistle.com (Archie Cobbs) Date: Thu, 10 Dec 1998 21:59:00 -0800 (PST) Cc: eivind@yes.no, vallo@matti.ee, current@FreeBSD.ORG, dg@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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: > Eivind Eklund writes: > > As for the inetd problem: We know what it is, we have a fix, and David > > Greenman seems to be vetoing committing it due to its "inelegance". > > So let's see his version. Well, I take that back.. :-) I'm reading into that discussion which I'm not part of. My point is let's not stray too far to the 'right' on the spectrum between purity and getting sh*t done... -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 Thu Dec 10 22:08:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20351 for freebsd-current-outgoing; Thu, 10 Dec 1998 22:08:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20346; Thu, 10 Dec 1998 22:08:49 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA09469; Thu, 10 Dec 1998 22:07:04 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma009463; Thu, 10 Dec 98 22:06:52 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA22141; Thu, 10 Dec 1998 22:06:52 -0800 (PST) From: Archie Cobbs Message-Id: <199812110606.WAA22141@bubba.whistle.com> Subject: Re: mformat in free(): warning: junk pointer, too high to make sense. In-Reply-To: <2923.913355388@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 10, 98 09:49:48 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Thu, 10 Dec 1998 22:06:52 -0800 (PST) Cc: eivind@yes.no, vallo@matti.ee, current@FreeBSD.ORG, dg@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Jordan K. Hubbard writes: > > > As for the inetd problem: We know what it is, we have a fix, and David > > > Greenman seems to be vetoing committing it due to its "inelegance". > > > > So let's see his version. > > Why doesn't someone just commit it? David's already in hot water over > his filesystem destroying fragmentation changes and I don't think > anyone will side with him if you just bring the inetd change into > -current at this point. :-) :-) Well, this brings up an unrelated question. I've written a little library that comes in very handy in situations like this (I have heard there are similar things out there but this was a custom job). Basically, it allows you to write an event driven program, where each event is handled atomically from all others, without resorting to threads and libc_r. An event is a file descriptor read/write condition, a timer timeout, or a signal receipt. The header file looks like this.. /* Types of events */ enum { EVENT_READ, /* value = file descriptor */ EVENT_WRITE, /* value = file descriptor */ EVENT_EXCEPTION, /* value = file descriptor */ EVENT_TIMEOUT, /* value = time in miliseconds */ EVENT_SIGNAL, /* value = signal number */ EVENT_USER, /* value = user defined */ }; typedef u_int EventRef; typedef void (*EventHdlr)(int type, void *cookie); /* Register a new event */ extern int EventRegister(EventRef *ref, int type, int value, int prio, EventHdlr action, void *cookie); /* Unregister a pending event */ extern int EventUnRegister(EventRef *ref); /* Check if an event is pending */ extern int EventIsRegistered(EventRef ref); /* Check time remaining on a timeout event */ extern int EventTimerRemain(EventRef ref); /* Trigger a user defined event */ extern int EventUserEvent(int value); /* Begin servicing events */ extern int EventStart(void); /* Stop servicing events */ extern void EventStop(void); Is this something possibly worth it's own little library? I'd be willing to refine it and write a man page. Then maybe the inetd problem could be solved more 'elegantly'. -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 Thu Dec 10 22:26:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22118 for freebsd-current-outgoing; Thu, 10 Dec 1998 22:26:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22113 for ; Thu, 10 Dec 1998 22:26:06 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA34705; Thu, 10 Dec 1998 22:25:53 -0800 (PST) (envelope-from dillon) Date: Thu, 10 Dec 1998 22:25:53 -0800 (PST) From: Matthew Dillon Message-Id: <199812110625.WAA34705@apollo.backplane.com> To: Archie Cobbs Cc: jwd@unx.sas.com (John W. DeBoskey), freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812110544.VAA21634@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> Well, from reading the mail that's gone by, it appears that there :> is a possible fix for the inetd bug: :> :> inetd in realloc(): warning: junk pointer, too low to make sense. :> inetd in free(): warning: junk pointer, too low to make sense. :> :> I'm tired of seeing this and would appreciate it if someone would :> post the patch so we can use it until the appropriate folks make up :> their minds on the best way to fix it. : :http://www.freebsd.org/cgi/query-pr.cgi?pr=8183 : :-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 Ick. character flags through a pipe? Ick. Ick. Let me fix this thing, guys, I'm getting tired of all the arguing and non-action for such a simple bug. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 22:28:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22239 for freebsd-current-outgoing; Thu, 10 Dec 1998 22:28:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22234 for ; Thu, 10 Dec 1998 22:28:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id WAA03249; Thu, 10 Dec 1998 22:27:54 -0800 (PST) To: Matthew Dillon cc: Archie Cobbs , jwd@unx.sas.com (John W. DeBoskey), freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug In-reply-to: Your message of "Thu, 10 Dec 1998 22:25:53 PST." <199812110625.WAA34705@apollo.backplane.com> Date: Thu, 10 Dec 1998 22:27:53 -0800 Message-ID: <3244.913357673@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ick. character flags through a pipe? Ick. Ick. Let me fix this > thing, guys, I'm getting tired of all the arguing and non-action for > such a simple bug. You won't get any argument from me. :-) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 22:29:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22327 for freebsd-current-outgoing; Thu, 10 Dec 1998 22:29:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22318 for ; Thu, 10 Dec 1998 22:29:21 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA09769; Thu, 10 Dec 1998 22:28:38 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma009767; Thu, 10 Dec 98 22:28:36 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA23665; Thu, 10 Dec 1998 22:28:36 -0800 (PST) From: Archie Cobbs Message-Id: <199812110628.WAA23665@bubba.whistle.com> Subject: Re: inetd: realloc/free bug In-Reply-To: <199812110625.WAA34705@apollo.backplane.com> from Matthew Dillon at "Dec 10, 98 10:25:53 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 10 Dec 1998 22:28:36 -0800 (PST) Cc: archie@whistle.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Matthew Dillon writes: > :> inetd in realloc(): warning: junk pointer, too low to make sense. > :> inetd in free(): warning: junk pointer, too low to make sense. > :> > : > :http://www.freebsd.org/cgi/query-pr.cgi?pr=8183 > : > Ick. character flags through a pipe? Ick. Ick. Let me fix this > thing, guys, I'm getting tired of all the arguing and non-action for > such a simple bug. It's not trivial if you want to guarantee that no signals are missed. There's no way atomically to: unblock signals and call select(). -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 Thu Dec 10 22:51:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24761 for freebsd-current-outgoing; Thu, 10 Dec 1998 22:51:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24753 for ; Thu, 10 Dec 1998 22:51:32 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA34943; Thu, 10 Dec 1998 22:51:20 -0800 (PST) (envelope-from dillon) Date: Thu, 10 Dec 1998 22:51:20 -0800 (PST) From: Matthew Dillon Message-Id: <199812110651.WAA34943@apollo.backplane.com> To: Archie Cobbs Cc: archie@whistle.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812110628.WAA23665@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Matthew Dillon writes: :> :> inetd in realloc(): warning: junk pointer, too low to make sense. :> :> inetd in free(): warning: junk pointer, too low to make sense. :> :> :> : :> :http://www.freebsd.org/cgi/query-pr.cgi?pr=8183 :> : :> Ick. character flags through a pipe? Ick. Ick. Let me fix this :> thing, guys, I'm getting tired of all the arguing and non-action for :> such a simple bug. : :It's not trivial if you want to guarantee that no signals are missed. :There's no way atomically to: unblock signals and call select(). : :-Archie If you put a time limit on select(), it doesn't matter if there is a race condition there. How does select() cause a signal to be missed ? -Matt :___________________________________________________________________________ :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 : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 22:52:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24922 for freebsd-current-outgoing; Thu, 10 Dec 1998 22:52:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay1.pptus.ru (relay1.pptus.ru [194.84.13.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24888 for ; Thu, 10 Dec 1998 22:52:04 -0800 (PST) (envelope-from romanp@wuppy.rcs.ru) Received: from room101.wuppy.rcs.ru (room101.wuppy.rcs.ru [194.84.206.44]) by relay1.pptus.ru (8.9.0/8.9.0) with ESMTP id JAA26354; Fri, 11 Dec 1998 09:51:35 +0300 (MSK) Received: from room101.wuppy.rcs.ru (peer cross-checked as room101.wuppy.rcs.ru [194.84.206.44]) by room101.wuppy.rcs.ru with ESMTP id JAA04217; Fri, 11 Dec 1998 09:52:44 +0300 (MSK) (envelope-from romanp@wuppy.rcs.ru) Date: Fri, 11 Dec 1998 09:52:43 +0300 (MSK) From: "Roman V. Palagin" To: Ben Smithurst cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size In-Reply-To: <19981210183519.A725@scientia.demon.co.uk> 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, 10 Dec 1998, Ben Smithurst wrote: > Anyone know what could have caused this: > > dev = 0x40002, bno = 124, bsize = 8192, size = 8192, fs = /home > panic: ffs_blkfree: bad size > > FreeBSD -current, ~1 week old (not sure exactly how old). Check your version of /sys/kern/vfs_cluster.c. It should be 1.75 (1998/12/05) > > -- > Ben Smithurst > ben@scientia.demon.co.uk > > send a blank message to ben+pgp@scientia.demon.co.uk for PGP key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ------------------------------------------------------------------------- Roman V. Palagin | RVP1-6BONE | Just because you're paranoid Network Administrator | RP40-RIPE | doesn't mean they AREN'T after you To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 22:55:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25187 for freebsd-current-outgoing; Thu, 10 Dec 1998 22:55:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25181 for ; Thu, 10 Dec 1998 22:55:23 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id WAA10092; Thu, 10 Dec 1998 22:54:38 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma010090; Thu, 10 Dec 98 22:54:29 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id WAA25455; Thu, 10 Dec 1998 22:54:28 -0800 (PST) From: Archie Cobbs Message-Id: <199812110654.WAA25455@bubba.whistle.com> Subject: Re: inetd: realloc/free bug In-Reply-To: <199812110651.WAA34943@apollo.backplane.com> from Matthew Dillon at "Dec 10, 98 10:51:20 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Thu, 10 Dec 1998 22:54:28 -0800 (PST) Cc: jwd@unx.sas.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Matthew Dillon writes: > :It's not trivial if you want to guarantee that no signals are missed. > :There's no way atomically to: unblock signals and call select(). > > If you put a time limit on select(), it doesn't matter if there is a > race condition there. How does select() cause a signal to be missed ? Well, sure.. :-) but then you don't service signals in real time and spend extra cycles timing out all the time. By the way, from man select(2): BUGS select() should probably return the time remaining from the original timeout, if any, by modifying the time value in place. This may be im- plemented in future versions of the system. Thus, it is unwise to assume that the timeout value will be unmodified by the select() call. Is this ever going to be implemented? I think this warning's been around for at least 10 years now.. -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 Thu Dec 10 22:56:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25463 for freebsd-current-outgoing; Thu, 10 Dec 1998 22:56:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25457 for ; Thu, 10 Dec 1998 22:56:39 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA35034; Thu, 10 Dec 1998 22:56:24 -0800 (PST) (envelope-from dillon) Date: Thu, 10 Dec 1998 22:56:24 -0800 (PST) From: Matthew Dillon Message-Id: <199812110656.WAA35034@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: Archie Cobbs , jwd@unx.sas.com (John W. DeBoskey), freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <3244.913357673@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think we can get this fixed pretty quickly, there really isn't much to it. A couple of minor race conditions in select() as Archie pointed out, but there is so little left that can go wrong I expect we'll cover all our bases in short order. My current proposed diff is included below. This is off the top of my head and barely tested (yet), but ... -Matt : :> Ick. character flags through a pipe? Ick. Ick. Let me fix this :> thing, guys, I'm getting tired of all the arguing and non-action for :> such a simple bug. : :You won't get any argument from me. :-) : :- Jordan : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) Index: inetd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/inetd/inetd.c,v retrieving revision 1.41 diff -c -r1.41 inetd.c *** inetd.c 1998/11/04 19:39:46 1.41 --- inetd.c 1998/12/11 06:54:48 *************** *** 431,449 **** (void)setenv("inetd_dummy", dummy, 1); } for (;;) { int n, ctrl; fd_set readable; if (nsock == 0) { - (void) sigblock(SIGBLOCK); while (nsock == 0) sigpause(0L); - (void) sigsetmask(0L); } readable = allsock; ! if ((n = select(maxsock + 1, &readable, (fd_set *)0, ! (fd_set *)0, (struct timeval *)0)) <= 0) { if (n < 0 && errno != EINTR) { syslog(LOG_WARNING, "select: %m"); sleep(1); --- 431,467 ---- (void)setenv("inetd_dummy", dummy, 1); } + (void) sigblock(SIGBLOCK); + for (;;) { int n, ctrl; fd_set readable; + struct timeval tv = { 5, 0 }; + + + /* + * Handle signal masking and select. Signals are unmasked and + * we pause if we have no active descriptors. If we do have + * active descriptors, leave signals unmasked through the select() + * call. + * + * Signals are masked at all other times. + */ if (nsock == 0) { while (nsock == 0) sigpause(0L); } + + (void) sigsetmask(0L); + + readable = allsock; ! n = select(maxsock + 1, &readable, NULL, NULL, &tv); ! ! (void) sigblock(SIGBLOCK); ! ! if (n <= 0) { if (n < 0 && errno != EINTR) { syslog(LOG_WARNING, "select: %m"); sleep(1); *************** *** 490,496 **** } } else ctrl = sep->se_fd; ! (void) sigblock(SIGBLOCK); pid = 0; dofork = (sep->se_bi == 0 || sep->se_bi->bi_fork); if (dofork) { --- 508,514 ---- } } else ctrl = sep->se_fd; ! /* (void) sigblock(SIGBLOCK); */ pid = 0; dofork = (sep->se_bi == 0 || sep->se_bi->bi_fork); if (dofork) { *************** *** 509,515 **** "%s/%s server failing (looping), service terminated", sep->se_service, sep->se_proto); close_sep(sep); ! sigsetmask(0L); if (!timingout) { timingout = 1; alarm(RETRYTIME); --- 527,533 ---- "%s/%s server failing (looping), service terminated", sep->se_service, sep->se_proto); close_sep(sep); ! /* sigsetmask(0L); */ if (!timingout) { timingout = 1; alarm(RETRYTIME); *************** *** 524,536 **** if (sep->se_accept && sep->se_socktype == SOCK_STREAM) close(ctrl); ! sigsetmask(0L); sleep(1); continue; } if (pid) addchild(sep, pid); ! sigsetmask(0L); if (pid == 0) { if (dofork) { if (debug) --- 542,554 ---- if (sep->se_accept && sep->se_socktype == SOCK_STREAM) close(ctrl); ! /* sigsetmask(0L); */ sleep(1); continue; } if (pid) addchild(sep, pid); ! /* sigsetmask(0L); */ if (pid == 0) { if (dofork) { if (debug) *************** *** 713,719 **** int signo; { struct servtab *sep, *new, **sepp; ! long omask; if (!setconfig()) { syslog(LOG_ERR, "%s: %m", CONFIG); --- 731,737 ---- int signo; { struct servtab *sep, *new, **sepp; ! /* long omask; */ if (!setconfig()) { syslog(LOG_ERR, "%s: %m", CONFIG); *************** *** 751,757 **** int i; #define SWAP(a, b) { typeof(a) c = a; a = b; b = c; } ! omask = sigblock(SIGBLOCK); /* copy over outstanding child pids */ if (sep->se_maxchild && new->se_maxchild) { new->se_numchild = sep->se_numchild; --- 769,775 ---- int i; #define SWAP(a, b) { typeof(a) c = a; a = b; b = c; } ! /* omask = sigblock(SIGBLOCK); */ /* copy over outstanding child pids */ if (sep->se_maxchild && new->se_maxchild) { new->se_numchild = sep->se_numchild; *************** *** 784,790 **** SWAP(sep->se_server, new->se_server); for (i = 0; i < MAXARGV; i++) SWAP(sep->se_argv[i], new->se_argv[i]); ! sigsetmask(omask); freeconfig(new); if (debug) print_service("REDO", sep); --- 802,808 ---- SWAP(sep->se_server, new->se_server); for (i = 0; i < MAXARGV; i++) SWAP(sep->se_argv[i], new->se_argv[i]); ! /* sigsetmask(omask); */ freeconfig(new); if (debug) print_service("REDO", sep); *************** *** 839,845 **** /* * Purge anything not looked at above. */ ! omask = sigblock(SIGBLOCK); sepp = &servtab; while ((sep = *sepp)) { if (sep->se_checked) { --- 857,863 ---- /* * Purge anything not looked at above. */ ! /* omask = sigblock(SIGBLOCK); */ sepp = &servtab; while ((sep = *sepp)) { if (sep->se_checked) { *************** *** 856,862 **** freeconfig(sep); free((char *)sep); } ! (void) sigsetmask(omask); } void --- 874,880 ---- freeconfig(sep); free((char *)sep); } ! /* (void) sigsetmask(omask); */ } void *************** *** 865,873 **** { int i; struct servtab *sepp; ! long omask; ! omask = sigblock(SIGBLOCK); for (sepp = servtab; sepp; sepp = sepp->se_next) { if (sepp == sep) continue; --- 883,891 ---- { int i; struct servtab *sepp; ! /* long omask; */ ! /* omask = sigblock(SIGBLOCK); */ for (sepp = servtab; sepp; sepp = sepp->se_next) { if (sepp == sep) continue; *************** *** 884,890 **** if (sep->se_fd != -1) (void) close(sep->se_fd); sep->se_fd = -1; ! (void) sigsetmask(omask); } void --- 902,908 ---- if (sep->se_fd != -1) (void) close(sep->se_fd); sep->se_fd = -1; ! /* (void) sigsetmask(omask); */ } void *************** *** 997,1003 **** struct servtab *cp; { struct servtab *sep; ! long omask; sep = (struct servtab *)malloc(sizeof (*sep)); if (sep == (struct servtab *)0) { --- 1015,1021 ---- struct servtab *cp; { struct servtab *sep; ! /* long omask; */ sep = (struct servtab *)malloc(sizeof (*sep)); if (sep == (struct servtab *)0) { *************** *** 1006,1015 **** } *sep = *cp; sep->se_fd = -1; ! omask = sigblock(SIGBLOCK); sep->se_next = servtab; servtab = sep; ! sigsetmask(omask); return (sep); } --- 1024,1033 ---- } *sep = *cp; sep->se_fd = -1; ! /* omask = sigblock(SIGBLOCK); */ sep->se_next = servtab; servtab = sep; ! /* sigsetmask(omask); */ return (sep); } *************** *** 1783,1788 **** --- 1801,1809 ---- /* * Based on TCPMUX.C by Mark K. Lottor November 1988 * sri-nic::ps:tcpmux.c + * + * signals are masked on call, we have to unmask SIGALRM for the + * duration of the read. */ *************** *** 1794,1812 **** { int count = 0, n; struct sigaction sa; sa.sa_flags = 0; sigemptyset(&sa.sa_mask); sa.sa_handler = SIG_DFL; sigaction(SIGALRM, &sa, (struct sigaction *)0); do { alarm(10); n = read(fd, buf, len-count); alarm(0); if (n == 0) ! return (count); ! if (n < 0) ! return (-1); while (--n >= 0) { if (*buf == '\r' || *buf == '\n' || *buf == '\0') return (count); --- 1815,1839 ---- { int count = 0, n; struct sigaction sa; + long omask; sa.sa_flags = 0; sigemptyset(&sa.sa_mask); sa.sa_handler = SIG_DFL; sigaction(SIGALRM, &sa, (struct sigaction *)0); + + omask = sigsetmask(SIGBLOCK & ~sigmask(SIGALRM)); + do { alarm(10); n = read(fd, buf, len-count); alarm(0); if (n == 0) ! break; ! if (n < 0) { ! count = -1; ! break; ! } while (--n >= 0) { if (*buf == '\r' || *buf == '\n' || *buf == '\0') return (count); *************** *** 1814,1819 **** --- 1841,1848 ---- buf++; } } while (count < len); + + sigsetmask(omask); return (count); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 22:59:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25654 for freebsd-current-outgoing; Thu, 10 Dec 1998 22:59:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25647 for ; Thu, 10 Dec 1998 22:59:21 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA35073; Thu, 10 Dec 1998 22:59:07 -0800 (PST) (envelope-from dillon) Date: Thu, 10 Dec 1998 22:59:07 -0800 (PST) From: Matthew Dillon Message-Id: <199812110659.WAA35073@apollo.backplane.com> To: Archie Cobbs Cc: jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812110654.WAA25455@bubba.whistle.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :> If you put a time limit on select(), it doesn't matter if there is a :> race condition there. How does select() cause a signal to be missed ? : :Well, sure.. :-) but then you don't service signals in real time :and spend extra cycles timing out all the time. You do serve signals in real time... the signals are *unmasked* during the select() :-) ... the race condition is that the unmasked signal may cause the descriptor set to be changed just prior to the select() call, causing select() to wait forever. The timeout on the select() handles the race condition without effecting the realtime delivery of signals. -Matt :By the way, from man select(2): : : BUGS : select() should probably return the time remaining from the original : timeout, if any, by modifying the time value in place. This may be im- : plemented in future versions of the system. Thus, it is unwise to assume : that the timeout value will be unmodified by the select() call. : :Is this ever going to be implemented? I think this warning's been :around for at least 10 years now.. : :-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 : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 23:04:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26000 for freebsd-current-outgoing; Thu, 10 Dec 1998 23:04:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25993 for ; Thu, 10 Dec 1998 23:04:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA35167; Thu, 10 Dec 1998 23:03:55 -0800 (PST) (envelope-from dillon) Date: Thu, 10 Dec 1998 23:03:55 -0800 (PST) From: Matthew Dillon Message-Id: <199812110703.XAA35167@apollo.backplane.com> To: Archie Cobbs , jwd@unx.sas.com (John W. DeBoskey), freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812110544.VAA21634@bubba.whistle.com> <199812110625.WAA34705@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (more changes to my diff: get rid of the LOG_WARNING syslog on select() failure, since this would occur every 5 seconds :-), or perhaps pre-set errno to 0 and check for errno = 0 and not log a warning if a timeout occurs) -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 23:11:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26843 for freebsd-current-outgoing; Thu, 10 Dec 1998 23:11:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from unix.tfs.net (as2-p109.tfs.net [139.146.205.109] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26838 for ; Thu, 10 Dec 1998 23:11:18 -0800 (PST) (envelope-from jbryant@unix.tfs.net) Received: (from jbryant@localhost) by unix.tfs.net (8.9.1/8.8.5) id BAA00395 for freebsd-current@freebsd.org; Fri, 11 Dec 1998 01:11:08 -0600 (CST) From: Jim Bryant Message-Id: <199812110711.BAA00395@unix.tfs.net> Subject: nfsstat negative value... To: freebsd-current@FreeBSD.ORG Date: Fri, 11 Dec 1998 01:11:06 -0600 (CST) Reply-to: jbryant@unix.tfs.net X-Windows: R00LZ!@# MS-Winbl0wz DR00LZ!@# X-files: The truth is that the X-Files is fiction X-Republican: The best kind!!! X-Operating-System: FreeBSD 3.0-CURRENT #0: Sat Jun 20 11:57:05 CDT 1998 X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm running a kernel from Dec. 6, 1998 what follows is the output of nfsstat. note the negative value. ------------------------------------------------------------------ 1:07:08am wahoo(76): nfsstat Client Info: Rpc Counts: Getattr Setattr Lookup Readlink Read Write Create Remove 4327 1294 4626 0 2532 7633 305 328 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 2 0 22 177 177 190 0 14494 Mknod Fsstat Fsinfo PathConf Commit GLease Vacate Evict 0 247 1 0 2421 0 0 0 Rpc Info: TimedOut Invalid X Replies Retries Requests 0 0 1 15 38776 Cache Info: Attr Hits Misses Lkup Hits Misses BioR Hits Misses BioW Hits Misses 88201 4327 13389 4624 72829 2532 -2302 7633 BioRLHits Misses BioD Hits Misses DirE Hits Misses 0 0 294 190 236 0 Server Info: Getattr Setattr Lookup Readlink Read Write Create Remove 0 0 0 0 0 0 0 0 Rename Link Symlink Mkdir Rmdir Readdir RdirPlus Access 0 0 0 0 0 0 0 0 Mknod Fsstat Fsinfo PathConf Commit GLease Vacate Evict 0 0 0 0 0 0 0 0 Server Ret-Failed 0 Server Faults 0 Server Cache Stats: Inprog Idem Non-idem Misses 0 0 0 0 Server Lease Stats: Leases PeakL GLeases 0 0 0 Server Write Gathering: WriteOps WriteRPC Opsaved 0 0 0 ------------------------------------------------------------------ jim -- All opinions expressed are mine, if you | "I will not be pushed, stamped, think otherwise, then go jump into turbid | briefed, debriefed, indexed, or radioactive waters and yell WAHOO !!! | numbered!" - #1, "The Prisoner" ------------------------------------------------------------------------------ Inet: jbryant@tfs.net AX.25: kc5vdj@wv0t.#neks.ks.usa.noam grid: EM28pw voice: KC5VDJ - 6 & 2 Meters AM/FM/SSB, 70cm FM. http://www.tfs.net/~jbryant ------------------------------------------------------------------------------ HF/6M/2M: IC-706-MkII, 2M: HTX-212, 2M: HTX-202, 70cm: HTX-404, Packet: KPC-3+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 23:13:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27170 for freebsd-current-outgoing; Thu, 10 Dec 1998 23:13:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA27157 for ; Thu, 10 Dec 1998 23:13:37 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoMks-0001CK-00; Fri, 11 Dec 1998 00:12:50 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id AAA00506; Fri, 11 Dec 1998 00:11:15 -0700 (MST) Message-Id: <199812110711.AAA00506@harmony.village.org> To: Matthew Dillon Subject: Re: inetd: realloc/free bug Cc: Archie Cobbs , jwd@unx.sas.com, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Dec 1998 22:59:07 PST." <199812110659.WAA35073@apollo.backplane.com> References: <199812110659.WAA35073@apollo.backplane.com> <199812110654.WAA25455@bubba.whistle.com> Date: Fri, 11 Dec 1998 00:11:14 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812110659.WAA35073@apollo.backplane.com> Matthew Dillon writes: : :By the way, from man select(2): : : : : BUGS : : select() should probably return the time remaining from the original : : timeout, if any, by modifying the time value in place. This may be im- : : plemented in future versions of the system. Thus, it is unwise to assume : : that the timeout value will be unmodified by the select() call. : : : :Is this ever going to be implemented? I think this warning's been : :around for at least 10 years now.. No. It breaks too many things. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 23:17:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27443 for freebsd-current-outgoing; Thu, 10 Dec 1998 23:17:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27418 for ; Thu, 10 Dec 1998 23:17:29 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA35358; Thu, 10 Dec 1998 23:17:13 -0800 (PST) (envelope-from dillon) Date: Thu, 10 Dec 1998 23:17:13 -0800 (PST) From: Matthew Dillon Message-Id: <199812110717.XAA35358@apollo.backplane.com> To: Warner Losh Cc: Archie Cobbs , jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812110659.WAA35073@apollo.backplane.com> <199812110654.WAA25455@bubba.whistle.com> <199812110711.AAA00506@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I seem to recall linux returning the time remaining a long time ago, but I think they ripped it out. I don't have a linux box handy to test the linux current kernel. I definitely think it's a mistake to change select()'s timeout operation, too many programs pre-set the timeval and assume it will not be changed on multiple calls to select(). If we were to implement a returned-time it would have to be with a new system call. -Matt : :In message <199812110659.WAA35073@apollo.backplane.com> Matthew Dillon writes: :: :By the way, from man select(2): :: : :: : BUGS :: : select() should probably return the time remaining from the original :: : timeout, if any, by modifying the time value in place. This may be im- :: : plemented in future versions of the system. Thus, it is unwise to assume :: : that the timeout value will be unmodified by the select() call. :: : :: :Is this ever going to be implemented? I think this warning's been :: :around for at least 10 years now.. : :No. It breaks too many things. : :Warner : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 23:22:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27980 for freebsd-current-outgoing; Thu, 10 Dec 1998 23:22:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27971 for ; Thu, 10 Dec 1998 23:22:43 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id XAA35442; Thu, 10 Dec 1998 23:22:26 -0800 (PST) (envelope-from dillon) Date: Thu, 10 Dec 1998 23:22:26 -0800 (PST) From: Matthew Dillon Message-Id: <199812110722.XAA35442@apollo.backplane.com> To: Warner Losh Cc: Archie Cobbs , jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: inetd commit candidate (was Re: inetd: realloc/free bug ) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (diff relative to current cvs version) I've done some testing of this patch on one of our more heavily loaded shell machines and it seems to hold up, so it is now a commit candidate. However, since I do not get the realloc/free errors it would be good if some of the people who do test this patch on their own systems. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) Index: inetd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/inetd/inetd.c,v retrieving revision 1.41 diff -c -r1.41 inetd.c *** inetd.c 1998/11/04 19:39:46 1.41 --- inetd.c 1998/12/11 07:19:18 *************** *** 431,450 **** (void)setenv("inetd_dummy", dummy, 1); } for (;;) { int n, ctrl; fd_set readable; if (nsock == 0) { - (void) sigblock(SIGBLOCK); while (nsock == 0) sigpause(0L); - (void) sigsetmask(0L); } readable = allsock; ! if ((n = select(maxsock + 1, &readable, (fd_set *)0, ! (fd_set *)0, (struct timeval *)0)) <= 0) { ! if (n < 0 && errno != EINTR) { syslog(LOG_WARNING, "select: %m"); sleep(1); } --- 431,472 ---- (void)setenv("inetd_dummy", dummy, 1); } + (void) sigblock(SIGBLOCK); + for (;;) { int n, ctrl; fd_set readable; + struct timeval tv = { 5, 0 }; + + + /* + * Handle signal masking and select. Signals are unmasked and + * we pause if we have no active descriptors. If we do have + * active descriptors, leave signals unmasked through the select() + * call. The select() call is inclusive of a timeout in order + * to handle the race condition where a signal occurs just prior + * to the select() call and potentially changes the allsock + * fd_set, to prevent select() from potentially blocking forever. + * + * Signals are masked at all other times. + */ if (nsock == 0) { while (nsock == 0) sigpause(0L); } + + (void) sigsetmask(0L); + + readable = allsock; ! errno = 0; ! n = select(maxsock + 1, &readable, NULL, NULL, &tv); ! ! (void) sigblock(SIGBLOCK); ! ! if (n <= 0) { ! if (n < 0 && errno && errno != EINTR) { syslog(LOG_WARNING, "select: %m"); sleep(1); } *************** *** 490,496 **** } } else ctrl = sep->se_fd; ! (void) sigblock(SIGBLOCK); pid = 0; dofork = (sep->se_bi == 0 || sep->se_bi->bi_fork); if (dofork) { --- 512,518 ---- } } else ctrl = sep->se_fd; ! /* (void) sigblock(SIGBLOCK); */ pid = 0; dofork = (sep->se_bi == 0 || sep->se_bi->bi_fork); if (dofork) { *************** *** 509,515 **** "%s/%s server failing (looping), service terminated", sep->se_service, sep->se_proto); close_sep(sep); ! sigsetmask(0L); if (!timingout) { timingout = 1; alarm(RETRYTIME); --- 531,537 ---- "%s/%s server failing (looping), service terminated", sep->se_service, sep->se_proto); close_sep(sep); ! /* sigsetmask(0L); */ if (!timingout) { timingout = 1; alarm(RETRYTIME); *************** *** 524,536 **** if (sep->se_accept && sep->se_socktype == SOCK_STREAM) close(ctrl); ! sigsetmask(0L); sleep(1); continue; } if (pid) addchild(sep, pid); ! sigsetmask(0L); if (pid == 0) { if (dofork) { if (debug) --- 546,558 ---- if (sep->se_accept && sep->se_socktype == SOCK_STREAM) close(ctrl); ! /* sigsetmask(0L); */ sleep(1); continue; } if (pid) addchild(sep, pid); ! /* sigsetmask(0L); */ if (pid == 0) { if (dofork) { if (debug) *************** *** 713,719 **** int signo; { struct servtab *sep, *new, **sepp; ! long omask; if (!setconfig()) { syslog(LOG_ERR, "%s: %m", CONFIG); --- 735,741 ---- int signo; { struct servtab *sep, *new, **sepp; ! /* long omask; */ if (!setconfig()) { syslog(LOG_ERR, "%s: %m", CONFIG); *************** *** 751,757 **** int i; #define SWAP(a, b) { typeof(a) c = a; a = b; b = c; } ! omask = sigblock(SIGBLOCK); /* copy over outstanding child pids */ if (sep->se_maxchild && new->se_maxchild) { new->se_numchild = sep->se_numchild; --- 773,779 ---- int i; #define SWAP(a, b) { typeof(a) c = a; a = b; b = c; } ! /* omask = sigblock(SIGBLOCK); */ /* copy over outstanding child pids */ if (sep->se_maxchild && new->se_maxchild) { new->se_numchild = sep->se_numchild; *************** *** 784,790 **** SWAP(sep->se_server, new->se_server); for (i = 0; i < MAXARGV; i++) SWAP(sep->se_argv[i], new->se_argv[i]); ! sigsetmask(omask); freeconfig(new); if (debug) print_service("REDO", sep); --- 806,812 ---- SWAP(sep->se_server, new->se_server); for (i = 0; i < MAXARGV; i++) SWAP(sep->se_argv[i], new->se_argv[i]); ! /* sigsetmask(omask); */ freeconfig(new); if (debug) print_service("REDO", sep); *************** *** 839,845 **** /* * Purge anything not looked at above. */ ! omask = sigblock(SIGBLOCK); sepp = &servtab; while ((sep = *sepp)) { if (sep->se_checked) { --- 861,867 ---- /* * Purge anything not looked at above. */ ! /* omask = sigblock(SIGBLOCK); */ sepp = &servtab; while ((sep = *sepp)) { if (sep->se_checked) { *************** *** 856,862 **** freeconfig(sep); free((char *)sep); } ! (void) sigsetmask(omask); } void --- 878,884 ---- freeconfig(sep); free((char *)sep); } ! /* (void) sigsetmask(omask); */ } void *************** *** 865,873 **** { int i; struct servtab *sepp; ! long omask; ! omask = sigblock(SIGBLOCK); for (sepp = servtab; sepp; sepp = sepp->se_next) { if (sepp == sep) continue; --- 887,895 ---- { int i; struct servtab *sepp; ! /* long omask; */ ! /* omask = sigblock(SIGBLOCK); */ for (sepp = servtab; sepp; sepp = sepp->se_next) { if (sepp == sep) continue; *************** *** 884,890 **** if (sep->se_fd != -1) (void) close(sep->se_fd); sep->se_fd = -1; ! (void) sigsetmask(omask); } void --- 906,912 ---- if (sep->se_fd != -1) (void) close(sep->se_fd); sep->se_fd = -1; ! /* (void) sigsetmask(omask); */ } void *************** *** 997,1003 **** struct servtab *cp; { struct servtab *sep; ! long omask; sep = (struct servtab *)malloc(sizeof (*sep)); if (sep == (struct servtab *)0) { --- 1019,1025 ---- struct servtab *cp; { struct servtab *sep; ! /* long omask; */ sep = (struct servtab *)malloc(sizeof (*sep)); if (sep == (struct servtab *)0) { *************** *** 1006,1015 **** } *sep = *cp; sep->se_fd = -1; ! omask = sigblock(SIGBLOCK); sep->se_next = servtab; servtab = sep; ! sigsetmask(omask); return (sep); } --- 1028,1037 ---- } *sep = *cp; sep->se_fd = -1; ! /* omask = sigblock(SIGBLOCK); */ sep->se_next = servtab; servtab = sep; ! /* sigsetmask(omask); */ return (sep); } *************** *** 1783,1788 **** --- 1805,1813 ---- /* * Based on TCPMUX.C by Mark K. Lottor November 1988 * sri-nic::ps:tcpmux.c + * + * signals are masked on call, we have to unmask SIGALRM for the + * duration of the read. */ *************** *** 1794,1812 **** { int count = 0, n; struct sigaction sa; sa.sa_flags = 0; sigemptyset(&sa.sa_mask); sa.sa_handler = SIG_DFL; sigaction(SIGALRM, &sa, (struct sigaction *)0); do { alarm(10); n = read(fd, buf, len-count); alarm(0); if (n == 0) ! return (count); ! if (n < 0) ! return (-1); while (--n >= 0) { if (*buf == '\r' || *buf == '\n' || *buf == '\0') return (count); --- 1819,1843 ---- { int count = 0, n; struct sigaction sa; + long omask; sa.sa_flags = 0; sigemptyset(&sa.sa_mask); sa.sa_handler = SIG_DFL; sigaction(SIGALRM, &sa, (struct sigaction *)0); + + omask = sigsetmask(SIGBLOCK & ~sigmask(SIGALRM)); + do { alarm(10); n = read(fd, buf, len-count); alarm(0); if (n == 0) ! break; ! if (n < 0) { ! count = -1; ! break; ! } while (--n >= 0) { if (*buf == '\r' || *buf == '\n' || *buf == '\0') return (count); *************** *** 1814,1819 **** --- 1845,1852 ---- buf++; } } while (count < len); + + sigsetmask(omask); return (count); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 23:24:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28290 for freebsd-current-outgoing; Thu, 10 Dec 1998 23:24:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA28281 for ; Thu, 10 Dec 1998 23:24:25 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoMvq-0001Cq-00; Fri, 11 Dec 1998 00:24:10 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id AAA00650; Fri, 11 Dec 1998 00:22:35 -0700 (MST) Message-Id: <199812110722.AAA00650@harmony.village.org> To: Matthew Dillon Subject: Re: inetd: realloc/free bug Cc: Archie Cobbs , jwd@unx.sas.com, freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 10 Dec 1998 23:17:13 PST." <199812110717.XAA35358@apollo.backplane.com> References: <199812110717.XAA35358@apollo.backplane.com> <199812110659.WAA35073@apollo.backplane.com> <199812110654.WAA25455@bubba.whistle.com> <199812110711.AAA00506@harmony.village.org> Date: Fri, 11 Dec 1998 00:22:35 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812110717.XAA35358@apollo.backplane.com> Matthew Dillon writes: : I seem to recall linux returning the time remaining a long time ago, : but I think they ripped it out. I don't have a linux box handy to : test the linux current kernel. Linux implemented the timeval stomping version of select. It was the first OS to do this. At the time they claimed that BSD 4.4 would be doing this and that they were going to be compatible with that, plus it was listed as a bug. BSD 4.4 came out, and it didn't change this part of the interface. There were boatloads of programs that were inexpertly ported to Linux that exhibited cpu eating problems. Turns out that they weren't robust enough to deal with the timeval stomping interface. In time they created a bsd_select, which was what all user progams used. I think it is possible to get the "new" linux behavior, but I don't know how. : I definitely think it's a mistake to change select()'s timeout : operation, too many programs pre-set the timeval and assume it will : not be changed on multiple calls to select(). If we were to : implement a returned-time it would have to be with a new system : call. Agreed. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 10 23:25:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28424 for freebsd-current-outgoing; Thu, 10 Dec 1998 23:25:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28403 for ; Thu, 10 Dec 1998 23:25:31 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id RAA00741; Fri, 11 Dec 1998 17:54:42 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199812110717.XAA35358@apollo.backplane.com> Date: Fri, 11 Dec 1998 17:54:38 +1030 (CST) From: "Daniel O'Connor" To: Matthew Dillon Subject: Re: inetd: realloc/free bug Cc: freebsd-current@FreeBSD.ORG, jwd@unx.sas.com, Archie Cobbs , Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Dec-98 Matthew Dillon wrote: > I definitely think it's a mistake to change select()'s timeout operation, > too many programs pre-set the timeval and assume it will not be changed > on multiple calls to select(). If we were to implement a returned-time it > would have to be with a new system call. Which would be useful.. I would like to have this functionality when I write code :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 00:00:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01602 for freebsd-current-outgoing; Thu, 10 Dec 1998 23:55:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01596 for ; Thu, 10 Dec 1998 23:55:53 -0800 (PST) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id QAA28227; Fri, 11 Dec 1998 16:55:34 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98111120) with ESMTP id QAA10039; Fri, 11 Dec 1998 16:55:33 +0900 (JST) Message-Id: <199812110755.QAA10039@hotaka.csl.sony.co.jp> To: Mike Smith cc: NAKAGAWA Yoshihisa , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 10 Dec 1998 17:01:56 PST." <199812110101.RAA01409@dingo.cdrom.com> Date: Fri, 11 Dec 1998 16:55:32 +0900 From: Kenjiro Cho Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Second, PAO enhanced irq-pool, dynamic irq-pool. So, pccardd get > free-irq from kernel. >> This is an example of an unacceptable solution rerettably typical to >> the PAO project - you folks are *too*narrowly*focussed* on your needs. It seems to me that the two parties don't communicate well. The new-bus people talk from the view of the entire architecture, but the focus of the PAO people is how to face the reality *NOW*. There are too many problematic laptops, pc-cards and bioses. Many people, especially in Japan, need a solution that works now. PAO is admittedly a collection of workarounds built from a huge knowledgebase of everyday-laptop-users. But these problems can't be solved just from a clean design. The two parties should respect differences in their positions. I for one feel that both efforts are very important for laptop users. --Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 00:02:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02074 for freebsd-current-outgoing; Fri, 11 Dec 1998 00:02:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d2.dialup.hilink.com.au [203.2.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02067 for ; Fri, 11 Dec 1998 00:02:12 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id XAA00468; Thu, 10 Dec 1998 23:59:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812110759.XAA00468@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: Mike Smith , current@FreeBSD.ORG Subject: Re: HEADS UP : laptop power-down change In-reply-to: Your message of "Thu, 10 Dec 1998 21:22:15 MST." <199812110422.VAA65796@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Dec 1998 23:59:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199812110222.SAA00769@dingo.cdrom.com> Mike Smith writes: > : No. RB_POWEROFF and RB_HALT have very different meanings. The PC > : doesn't have a useful means for getting back to the resident firmware, > : but many other systems do. That's what RB_HALT is meant to do, while > : RB_POWEROFF is meant to power the system down. The two are mutually > : exclusive. > > I know... halt should turn the machine off. halt(8) does a variety of things. In one case, it will turn the machine off. In another, it will return the system to the boot monitor. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 00:06:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02393 for freebsd-current-outgoing; Fri, 11 Dec 1998 00:06:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d2.dialup.hilink.com.au [203.2.144.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02376; Fri, 11 Dec 1998 00:06:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA00533; Fri, 11 Dec 1998 00:03:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812110803.AAA00533@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: Mike Smith , current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: HEADS UP : laptop power-down change In-reply-to: Your message of "Thu, 10 Dec 1998 22:16:04 MST." <199812110516.WAA66364@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Dec 1998 00:03:55 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > : Why the change? The current behavior seems right to me. > > Actually, rather than argue this into the ground, would you object to > my implementing a > > options APM_MAP_HALT_TO_POWER_OFF > > and checking it in to apm.c and LINT? Yes. There is a perfectly good set of run-time options which allow you to determine at any time whether you want to power-off or halt; having a kernel option override this would be stupid. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 00:48:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06696 for freebsd-current-outgoing; Fri, 11 Dec 1998 00:48:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bright.fx.genx.net (bright.fx.genx.net [206.64.4.154]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06691 for ; Fri, 11 Dec 1998 00:48:35 -0800 (PST) (envelope-from bright@hotjobs.com) Received: from localhost (bright@localhost) by bright.fx.genx.net (8.9.1/8.9.1) with ESMTP id DAA01216; Fri, 11 Dec 1998 03:52:27 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Fri, 11 Dec 1998 03:52:27 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Warner Losh cc: Matthew Dillon , Archie Cobbs , jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug In-Reply-To: <199812110722.AAA00650@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 Dec 1998, Warner Losh wrote: > In message <199812110717.XAA35358@apollo.backplane.com> Matthew Dillon writes: > : I seem to recall linux returning the time remaining a long time ago, > : but I think they ripped it out. I don't have a linux box handy to > : test the linux current kernel. > > Linux implemented the timeval stomping version of select. It was the > first OS to do this. At the time they claimed that BSD 4.4 would be > doing this and that they were going to be compatible with that, plus > it was listed as a bug. BSD 4.4 came out, and it didn't change this > part of the interface. There were boatloads of programs that were > inexpertly ported to Linux that exhibited cpu eating problems. Turns > out that they weren't robust enough to deal with the timeval stomping > interface. In time they created a bsd_select, which was what all user > progams used. I think it is possible to get the "new" linux behavior, > but I don't know how. > > : I definitely think it's a mistake to change select()'s timeout > : operation, too many programs pre-set the timeval and assume it will > : not be changed on multiple calls to select(). If we were to > : implement a returned-time it would have to be with a new system > : call. > > Agreed. ugh, all my wasted cycles resetting the timeval "just in case" select2() anyone? Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 00:51:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07119 for freebsd-current-outgoing; Fri, 11 Dec 1998 00:51:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA07103 for ; Fri, 11 Dec 1998 00:51:26 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 2492 invoked by uid 1001); 11 Dec 1998 08:51:16 +0000 (GMT) To: archie@whistle.com Cc: jkh@zippy.cdrom.com, eivind@yes.no, vallo@matti.ee, current@FreeBSD.ORG, dg@FreeBSD.ORG Subject: Re: mformat in free(): warning: junk pointer, too high to make sense. In-Reply-To: Your message of "Thu, 10 Dec 1998 22:06:52 -0800 (PST)" References: <199812110606.WAA22141@bubba.whistle.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Date: Fri, 11 Dec 1998 09:51:16 +0100 Message-ID: <2490.913366276@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, this brings up an unrelated question. I've written a little > library that comes in very handy in situations like this (I have > heard there are similar things out there but this was a custom job). > > Basically, it allows you to write an event driven program, where > each event is handled atomically from all others, without resorting > to threads and libc_r. An event is a file descriptor read/write > condition, a timer timeout, or a signal receipt. This would be good to have in the system. Have you compared your lib with Paul Vixie's eventlib, part of BIND 8.1.x? The man page is in src/lib/isc/eventlib.mdoc in the 8.1.2 source. A small part is included below. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- NAME evConnFunc, evFileFunc, evStreamFunc, evTimerFunc, evWaitFunc, evCreate, evDestroy, evGetNext, evDispatch, evDrop, evMainLoop, evConsTime, evTimeSpec, evTimeVal, evAddTime, evSubTime, evCmpTime, evNowTime, evLastEventTime, evSetTimer, evResetTimer, evClearTimer, evSetIdleTimer, evTouchIdleTimer, evClearIdleTimer, evWaitFor, evDo, evUnwait, evDefer, evSelectFD, evDeselectFD, evWrite, evRead, evCancelRW, evTimeRW, evUntimeRW, evListen, evConnect, evCancelConn, evHold, evUnhold, evTryAccept, evConsIovec, evSetDebug, evPrintf - event handling library ... DESCRIPTION This library provides multiple outstanding asynchronous timers and I/O to a cooperating application. The model is similar to that of the X Toolk­ it, in that events are registered with the library and the application spends most of its time in the evMainLoop() function. If an application already has a main loop, it can safely register events with this library as long as it periodically calls the evGetNext() and evDispatch() func­ tions. (Note that evGetNext() has both polling and blocking modes.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 01:21:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09926 for freebsd-current-outgoing; Fri, 11 Dec 1998 01:21:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09919 for ; Fri, 11 Dec 1998 01:21:39 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id UAA28085; Fri, 11 Dec 1998 20:21:18 +1100 Date: Fri, 11 Dec 1998 20:21:18 +1100 From: Bruce Evans Message-Id: <199812110921.UAA28085@godzilla.zeta.org.au> To: cejkar@dcse.fee.vutbr.cz, freebsd-current@FreeBSD.ORG Subject: Re: mkfifo()/select() & O_RDONLY serious bug? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have prepared small testing program (listed at the end) with mkfifo() >and select() calls. Fifo is opened as O_RDONLY or O_RDWR with O_NONBLOCK. >On FreeBSD 3.0-CURRENT, its behavior is different from other systems. >I think it is serious bug: select() returns that there is ready file >descriptor but descriptor is not ready in fact. I'm right? I think it's a feature :-). The descriptor is ready for reading. read() will succeed and return 0 (EOF) because the mode is O_NONBLOCK and there are no writers. This is as specified by POSIX.1. POSIX.1 doesn't specify select(), and the FreeBSD implementation is simply that select() returns success if read() would succeed immediately. >Tested on systems: > FreeBSD 3.0-CURRENT > FreeBSD 2.2.7 > Solaris 2.6 > Unixware 2.1 > Linux Debian 2.0 I think your program works like you want in 2.2.7 because read() on a fifo is broken in 2.2.7 -- it sometimes blocks in O_NONBLOCK mode, and select() just folliows read(). IIRC, this only affects the case where there have never been any writers. In Linux, I thought that this was related to the FIFO_SUNOS_BRAINDAMAGE option -- if this option is configuted, select() on fifos is specially broken to behave differently from select() on nameless pipes. However, `#undef FIFO_SUNOS_BRAINDAMAGE' seems to be the default in linux-2.1.128, and your program works like you want there. I don't know about the other systems. >Another bug: On FreeBSD systems I must use "#include " for >FD_ZERO() because of bzero() function. Yes? (If not, we need to fix >manual page for select(2) about needed includes.) Linux accidentially (?) avoids this problem by using an asm statement. It would be better to use memset(). >Results with "#define MODE O_RDWR": (It looks well.) This works because O_RDWR gives a writer, so the read descriptor is never ready. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 01:50:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12383 for freebsd-current-outgoing; Fri, 11 Dec 1998 01:50:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sparky.isocor.com (sparky.isocor.com [198.6.228.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12378 for ; Fri, 11 Dec 1998 01:50:49 -0800 (PST) (envelope-from peter.edwards@isocor.ie) Received: from isocor.ie (198.6.229.204) by sparky.isocor.com (NPlex 4.0.000); Fri, 11 Dec 1998 01:50:03 -0800 Message-ID: <3670EC02.D35D99CC@isocor.ie> Date: Fri, 11 Dec 1998 01:55:14 -0800 From: Peter Edwards Organization: ISOCOR X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Archie Cobbs CC: Matthew Dillon , jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812110628.WAA23665@bubba.whistle.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > It's not trivial if you want to guarantee that no signals are missed. > There's no way atomically to: unblock signals and call select(). Hmm. I must be twisted. What horror results from doing this in a signal handler? On e-paper, it seems to give the desired effect, but does a return from a signal handler implicitly call sigreturn(2) when it returns? And if so, is there anything that requires this to happen? ... sigusr1handler() { longjmp(jump_buf,1); } selecting_func() { if (setjmp(jump_buf) == 0) { sigprocmask(SIG_UNBLOCK, {...SIGUSR1...}, 0) /* Signal arriving now returns after the select call. */ select(...); sigprocmask(SIG_BLOCK, {...SIGUSR1...}, 0); } /* select finished, or signal arrived after the sigprocmask(SIG_UNBLOCK). */ } -- Peter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 02:16:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13992 for freebsd-current-outgoing; Fri, 11 Dec 1998 02:16:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bfc.dk ([194.192.110.140]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA13982 for ; Fri, 11 Dec 1998 02:16:45 -0800 (PST) (envelope-from npe@bfc.dk) From: npe@bfc.dk Received: by bfc.dk(Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) id 412566D7.00380D63 ; Fri, 11 Dec 1998 11:12:14 +0100 X-Lotus-FromDomain: BFC-DATA@BFC To: freebsd-current@FreeBSD.ORG Message-ID: <412566D7.0037C51A.00@bfc.dk> Date: Fri, 11 Dec 1998 11:12:41 +0100 Subject: Aout to ELF Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm wondering if there's any documentation on how to change from aout to elf kernels ?? I thought that a make aout-to-elf world do the trick.. But it fails with a missing script... Help needed :) Please.. - Nicolai Petri To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 02:47:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA17434 for freebsd-current-outgoing; Fri, 11 Dec 1998 02:47:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from finmarket.relis.ru (temp.relis.ru [193.125.152.75]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA17409; Fri, 11 Dec 1998 02:47:16 -0800 (PST) (envelope-from guardian@relis.ru) Received: from lightning (lightning.relcom.ru [193.125.152.92]) by finmarket.relis.ru (8.8.8/8.8.8) with SMTP id NAA01592; Fri, 11 Dec 1998 13:47:01 +0300 (MSK) (envelope-from guardian@relis.ru) Message-ID: <002401be24f3$0e58b520$5c987dc1@lightning.relcom.ru> Reply-To: "Igor Lidin" From: "Igor Lidin" To: Cc: Subject: xterm input is in cp866, not in koi8-r Date: Fri, 11 Dec 1998 13:43:14 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can anyone help me? Environment: FreeBSD 3.0-Current as of 1 Dec 1998 XFree86 3.3.3 built from ports collection as of 4 Dec 1998 /ports/russian/X.language port installed I have LANG and MM_CHARSET environment variables set to ru_RU.KOI8-R. Russian fonts are first in my FontPath. This is a part of my XF86Config: Section "Keyboard" Protocol "Standard" AutoRepeat 500 30 LeftAlt Meta RightAlt Meta ScrollLock Compose RightCtl Control XkbKeycodes "xfree86" XkbTypes "default" XkbCompat "default" XkbSymbols "us(pc105)+ru" XkbGeometry "pc(pc105)" XkbRules "xfree86" XkbModel "pc105" XkbLayout "ru" XkbOptions "" XkbKeymap "xfree86(ru)" EndSection Russian keyboard switching via Caps-Lock works well in WindowMaker Conf, Netscape, others, but not in XTerm. When I switch kbd with caps-lock to russian mode in xterm it appears that input is going in CP866 codepage, but not in KOI8-R, as it should be. Can anyone help me or point me to information about this problem? p.s. Please CC your replies to guardian@relis.ru Thanks, Igor Lidin, guardian@relis.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 03:27:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21364 for freebsd-current-outgoing; Fri, 11 Dec 1998 03:27:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lenka.ph.ipex.cz (lenka.ph.ipex.cz [62.168.16.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21352; Fri, 11 Dec 1998 03:27:11 -0800 (PST) (envelope-from kan@sti.cz) Received: from linux.sti.cz (linux.sti.cz [62.168.16.129]) by lenka.ph.ipex.cz (8.8.5/IPEX) with ESMTP id MAA25012; Fri, 11 Dec 1998 12:27:01 +0100 Received: from sti.cz (kan.sti.cz [192.168.0.18]) by linux.sti.cz (8.8.7/8.7.3) with ESMTP id NAA00498; Fri, 11 Dec 1998 13:32:03 +0100 Message-ID: <367101CF.B8420FF9@sti.cz> Date: Fri, 11 Dec 1998 12:28:15 +0100 From: "Alexander N. Kabaev" X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Igor Lidin CC: current@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: xterm input is in cp866, not in koi8-r References: <002401be24f3$0e58b520$5c987dc1@lightning.relcom.ru> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I looked into this problem and found out that XFree86 3.3.3 introduced a bug in their XmbLookupText function. I found the cause of the problem and sent a bug report along with patch to XFree86. We'll see if it will have any effect :) In the meantime, you could put the following patch in your /usr/ports/x11/XFree86/patches directory and recompile XFree86 port. This patch works perfectly for me. --- lib/X11/imConv.c Sat Oct 24 09:50:13 1998 +++ lib/X11/imConv.c.new Thu Dec 3 18:20:07 1998 @@ -429,7 +429,7 @@ #endif {sUTF8, "utf8", "\033%B"}, /* Non-standard */ - {sCyrillic, "KOI8-R", "\033%/1\200\210koi8-r\002"}, + {sKoi8, "KOI8-R", "\033%/1\200\210koi8-r\002"}, {sLatin9, "ISO8859-15", "\033%/1\200\213iso8859-15\002"},/* a.k.a. Latin-0 */ }; It would be also perfect if someone with appropriate rights will commit this patch into FreeBSD ports repository until official patch will appear from XFree86. Hope, this will help. Alexander Kabaev, kan@sti.cz Igor Lidin wrote: > Can anyone help me? > > Environment: > FreeBSD 3.0-Current as of 1 Dec 1998 > XFree86 3.3.3 built from ports collection as of 4 Dec 1998 > /ports/russian/X.language port installed > > I have LANG and MM_CHARSET environment variables > set to ru_RU.KOI8-R. Russian fonts are first in my FontPath. > > This is a part of my XF86Config: > Section "Keyboard" > Protocol "Standard" > AutoRepeat 500 30 > LeftAlt Meta > RightAlt Meta > ScrollLock Compose > RightCtl Control > XkbKeycodes "xfree86" > XkbTypes "default" > XkbCompat "default" > XkbSymbols "us(pc105)+ru" > XkbGeometry "pc(pc105)" > XkbRules "xfree86" > XkbModel "pc105" > XkbLayout "ru" > XkbOptions "" > XkbKeymap "xfree86(ru)" > EndSection > > Russian keyboard switching via Caps-Lock works well in > WindowMaker Conf, Netscape, others, but not in XTerm. > When I switch kbd with caps-lock to russian mode in xterm > it appears that input is going in CP866 codepage, but not > in KOI8-R, as it should be. > > Can anyone help me or point me to information about this > problem? > > p.s. > Please CC your replies to guardian@relis.ru > > Thanks, > Igor Lidin, guardian@relis.ru > > 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 Dec 11 03:29:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21529 for freebsd-current-outgoing; Fri, 11 Dec 1998 03:29:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sraigw.sra.co.jp (sraigw.sra.co.jp [202.32.10.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21524 for ; Fri, 11 Dec 1998 03:29:01 -0800 (PST) (envelope-from furuta@sra.co.jp) Received: from sramhc.sra.co.jp (sramhc [133.137.20.31]) by sraigw.sra.co.jp (8.8.7/3.6Wbeta7-sraigw) with ESMTP id UAA26502; Fri, 11 Dec 1998 20:28:36 +0900 (JST) Received: from sramhc.sra.co.jp (furuta@localhost [127.0.0.1]) by sramhc.sra.co.jp (8.8.7/3.6Wbeta7-srambox) with ESMTP id UAA26264; Fri, 11 Dec 1998 20:28:50 +0900 (JST) Message-Id: <199812111128.UAA26264@sramhc.sra.co.jp> To: mike@smith.net.au Cc: y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: Your message of "Thu, 10 Dec 1998 18:10:04 -0800" References: <199812110210.SAA00665@dingo.cdrom.com> X-Mailer: Mew version 1.70 on Emacs 19.28.7 / Mule 2.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 11 Dec 1998 20:28:50 +0900 From: Atsushi Furuta Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I am Atsushi Furuta, a member of the newcofig. >> In article <199812110210.SAA00665@dingo.cdrom.com>, Mike Smith writes: > Much of the work that you still have to do on > the newconfig stuff has already been done. For example, itojun-san's point of Date: Tue, 09 Jun 1998 13:21:42 +0900 From: Jun-ichiro Itoh Subject: new config Message-ID: <9929.897366102@cardamom.itojun.org> - Cannot pass "flags" field to pci devices. - Having foo_softc[NFOO] is A BAD THING, thinking about pci/isapnp devices. We must avoid this. is not implemented in the current FreeBSD. Many dirty ISA hack such as static softc, isa_devtab_wdc, is still holded. The newconfig cleard up much of them. Our stance is that such problems should be cleared up as soon as possible. It seems to me that the roadmap is not intended to solve these problem. For me, the newconfig is only a step to do so. BTW, I agree with Cho-san's opinion. I want to discuss with new-bus poeple to solve these problem. Please tell me about the new-bus ML. It is first time that I hear the new-bus ML. -- furuta@sra.co.jp (Atsushi Furuta) Advanced Technology Group. Software Research Associates, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 03:31:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21892 for freebsd-current-outgoing; Fri, 11 Dec 1998 03:31:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rf900.physics.usyd.edu.au (rf900.physics.usyd.edu.au [129.78.129.109]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21874; Fri, 11 Dec 1998 03:31:12 -0800 (PST) (envelope-from dawes@rf900.physics.usyd.edu.au) Received: (from dawes@localhost) by rf900.physics.usyd.edu.au (8.8.5/8.8.2) id WAA10434; Fri, 11 Dec 1998 22:30:48 +1100 (EST) Message-ID: <19981211223048.K6124@rf900.physics.usyd.edu.au> Date: Fri, 11 Dec 1998 22:30:48 +1100 From: David Dawes To: Igor Lidin , current@FreeBSD.ORG Cc: questions@FreeBSD.ORG Subject: Re: xterm input is in cp866, not in koi8-r References: <002401be24f3$0e58b520$5c987dc1@lightning.relcom.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <002401be24f3$0e58b520$5c987dc1@lightning.relcom.ru>; from Igor Lidin on Fri, Dec 11, 1998 at 01:43:14PM +0300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 11, 1998 at 01:43:14PM +0300, Igor Lidin wrote: >Can anyone help me? > >Environment: >FreeBSD 3.0-Current as of 1 Dec 1998 >XFree86 3.3.3 built from ports collection as of 4 Dec 1998 >/ports/russian/X.language port installed > >I have LANG and MM_CHARSET environment variables >set to ru_RU.KOI8-R. Russian fonts are first in my FontPath. There is a bug in the 3.3.3 Xlib code that results in an iso8859-6 table being used instead of the koi8-r table. Here's the fix. Let me know if it helps. David -- --- imConv.c 1998/10/21 06:40:38 1.5.2.5 +++ xc/lib/X11/imConv.c 1998/12/06 05:40:33 1.5.2.6 @@ -429,7 +429,7 @@ #endif {sUTF8, "utf8", "\033%B"}, /* Non-standard */ - {sCyrillic, "KOI8-R", "\033%/1\200\210koi8-r\002"}, + {sKoi8, "KOI8-R", "\033%/1\200\210koi8-r\002"}, {sLatin9, "ISO8859-15", "\033%/1\200\213iso8859-15\002"},/* a.k.a. Latin-0 */ }; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 04:26:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29593 for freebsd-current-outgoing; Fri, 11 Dec 1998 04:26:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29588 for ; Fri, 11 Dec 1998 04:26:32 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id HAA29472; Fri, 11 Dec 1998 07:25:50 -0500 (EST) Date: Fri, 11 Dec 1998 07:25:50 -0500 (EST) From: Daniel Eischen Message-Id: <199812111225.HAA29472@pcnet1.pcnet.com> To: bde@zeta.org.au, cejkar@dcse.fee.vutbr.cz, freebsd-current@FreeBSD.ORG Subject: Re: mkfifo()/select() & O_RDONLY serious bug? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >I have prepared small testing program (listed at the end) with mkfifo() > >and select() calls. Fifo is opened as O_RDONLY or O_RDWR with O_NONBLOCK. > >On FreeBSD 3.0-CURRENT, its behavior is different from other systems. > >I think it is serious bug: select() returns that there is ready file > >descriptor but descriptor is not ready in fact. I'm right? > > I think it's a feature :-). The descriptor is ready for reading. > read() will succeed and return 0 (EOF) because the mode is O_NONBLOCK and > there are no writers. This is as specified by POSIX.1. POSIX.1 doesn't > specify select(), and the FreeBSD implementation is simply that select() > returns success if read() would succeed immediately. I just caught this thread, so I may have missed something... This seems wrong. How do you wait for data availability from a file [descriptor] in non-blocking mode? You continuously spin in a select/read loop? If the file is opened in non-blocking mode, then a select (with timeout) is not needed to avoid blocking indefinitely because read() can do that. So if someone uses select with a non-blocking file descriptor, then you've got to assume that they want to know when data is ready and waiting; they don't want select to tell them that there isn't any data. Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 05:47:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA07723 for freebsd-current-outgoing; Fri, 11 Dec 1998 05:47:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.tar.com (ns.tar.com [204.95.187.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA07718 for ; Fri, 11 Dec 1998 05:47:25 -0800 (PST) (envelope-from lists@tar.com) Received: from ppro.tar.com (ppro.tar.com [204.95.187.9]) by ns.tar.com (8.9.1/8.9.1) with SMTP id HAA32824; Fri, 11 Dec 1998 07:47:13 -0600 (CST) (envelope-from lists@tar.com) Message-Id: <199812111347.HAA32824@ns.tar.com> From: "Richard Seaman, Jr." To: "Brian Feldman" Cc: "current@freebsd.org" Date: Fri, 11 Dec 98 07:47:12 -0600 Reply-To: "Richard Seaman, Jr." X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Linux Threads( was Re: RFSIGSHARE ready?) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 18 Nov 1998 22:17:02 -0500 (EST), Brian Feldman wrote: > Please try some LinuxThreads Linux native programs, I'd love to announce that >with all your help I have LinuxThreads programs working on FreeBSD! Thanks, >you're the greatest :) I've made a number of changes and additions to your patches. At this point the example programs that come with linux threads appear to run correctly in linux emulation mode, and I can get StarOffice 5.0 for Linux running, though there are occasional problems when closing windows. I suspect each window may be a thread, and that there may still be problems with thread exit processing in some cases. If you are interested in working on this, I'll try to put the patches into shape and send them to you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 07:50:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA20353 for freebsd-current-outgoing; Fri, 11 Dec 1998 07:50:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oitunix.oit.umass.edu (nscs44p1.remote.umass.edu [128.119.179.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA20347 for ; Fri, 11 Dec 1998 07:50:30 -0800 (PST) (envelope-from gp@oitunix.oit.umass.edu) Received: (from gp@localhost) by oitunix.oit.umass.edu (8.9.1/8.9.1) id KAA00469 for freebsd-current@freebsd.org; Fri, 11 Dec 1998 10:50:36 -0500 (EST) (envelope-from gp) Message-ID: <19981211105035.A230@oit.umass.edu> Date: Fri, 11 Dec 1998 10:50:35 -0500 From: Greg Pavelcak To: freebsd-current@FreeBSD.ORG Subject: Build Fails with Signal 4 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With sources supped last night, cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/com5.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/com6.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/com7.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/init.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/cypher.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/getcom.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/parse.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/room.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/save.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/fly.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/misc.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/globals.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/dayfile.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/nightfile.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/dayobjs.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/nightobjs.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/battlestar/words.c cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -o battlestar battlestar.o com1.o com2.o com3.o com4.o com5.o com6.o com7.o init.o cypher.o getcom.o parse.o room.o save.o fly.o misc.o globals.o dayfile.o nightfile.o dayobjs.o nightobjs.o words.o -lcurses -ltermcap -lcompat gzip -cn /usr/src/games/battlestar/battlestar.6 > battlestar.6.gz ===> games/bcd cc -nostdinc -O -pipe -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/games/bcd/bcd.c cc: Internal compiler error: program cc1 got fatal signal 4 *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. However, this may not be a -current problem, since I got these on my last several build attempts in different places. I'm hoping someone can shed some light though. Thanks. Greg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 09:41:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA03685 for freebsd-current-outgoing; Fri, 11 Dec 1998 09:41:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA03668; Fri, 11 Dec 1998 09:41:05 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoWYb-0001Ss-00; Fri, 11 Dec 1998 10:40:49 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id KAA03402; Fri, 11 Dec 1998 10:39:20 -0700 (MST) Message-Id: <199812111739.KAA03402@harmony.village.org> To: Mike Smith Subject: Re: HEADS UP : laptop power-down change Cc: current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 11 Dec 1998 00:03:55 PST." <199812110803.AAA00533@dingo.cdrom.com> References: <199812110803.AAA00533@dingo.cdrom.com> Date: Fri, 11 Dec 1998 10:39:19 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812110803.AAA00533@dingo.cdrom.com> Mike Smith writes: : > : Why the change? The current behavior seems right to me. : Yes. There is a perfectly good set of run-time options which allow you : to determine at any time whether you want to power-off or halt; having : a kernel option override this would be stupid. But the i386 code doesn't *HAVE* a rom monitor to drop back into... We just go into a loop that says press any key to reboot. Not exactly useful. The apm code is i386 specific, by definition. There are many places where we have kernel options that override stuff, I fail to see how this is different. At the very least I'd like to make it a sysctl so I can set it in my boot scripts. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 11:29:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA15676 for freebsd-current-outgoing; Fri, 11 Dec 1998 11:29:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from galea.com (Odie.Galea.Com [205.237.227.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA15668 for ; Fri, 11 Dec 1998 11:29:56 -0800 (PST) (envelope-from sepotvin@videotron.ca) Received: from gotlib.galea.com (Gotlib.Galea.Com [205.237.227.60]) by galea.com (8.6.11/8.6.9) with SMTP id OAA29196 for ; Fri, 11 Dec 1998 14:47:38 -0500 Received: from videotron.ca ([205.237.227.166]) by gotlib.galea.com (Lotus SMTP MTA SMTP v4.6 (462.2 9-3-1997)) with SMTP id 852566D7.006AFE16; Fri, 11 Dec 1998 14:28:38 -0500 Message-ID: <3671729F.9CF2280D@videotron.ca> Date: Fri, 11 Dec 1998 14:29:35 -0500 From: "Stephane E. Potvin" Organization: Galea Network Security X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: [Fwd: HEADS UP : laptop power-down change] Content-Type: multipart/mixed; boundary="------------A956BC19BDFC058CBEB4F161" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------A956BC19BDFC058CBEB4F161 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Well, it seems that in my rush to sent this to the list I actually sent it only to Mike. So here it goes. Stephane E. Potvin Galea Network Security --------------A956BC19BDFC058CBEB4F161 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-ID: <36711F4B.556039DF@videotron.ca> Date: Fri, 11 Dec 1998 08:34:03 -0500 From: "Stephane E. Potvin" Organization: Galea Network Security X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: Mike Smith Subject: Re: HEADS UP : laptop power-down change References: <199812110803.AAA00533@dingo.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mike Smith wrote: > > > : Why the change? The current behavior seems right to me. > > > > Actually, rather than argue this into the ground, would you object to > > my implementing a > > > > options APM_MAP_HALT_TO_POWER_OFF > > > > and checking it in to apm.c and LINT? > > Yes. There is a perfectly good set of run-time options which allow you > to determine at any time whether you want to power-off or halt; having > a kernel option override this would be stupid. > It's not stupid at all in the current context. The majority of us that have laptop uses i386 compatible processors that don't have the system monitor you mention. Changing the behavior of the halt command is gratuitious in our context and will only break current applications like kdm (part of kde) that expect the -h flag to shutdown the laptop, not halting it. At least could you put an option in the kernel config file until such applications are changed to expect the new flag? Just my 0.02, I don't really want a flame war over this so if you don't add the knob it's ok, I'll just add it locally. Stephane E. Potvin Galea Network Security --------------A956BC19BDFC058CBEB4F161-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 11:42:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17450 for freebsd-current-outgoing; Fri, 11 Dec 1998 11:42:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17445 for ; Fri, 11 Dec 1998 11:42:01 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA19098; Fri, 11 Dec 1998 11:41:10 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma019093; Fri, 11 Dec 98 11:40:58 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA27652; Fri, 11 Dec 1998 11:40:58 -0800 (PST) From: Archie Cobbs Message-Id: <199812111940.LAA27652@bubba.whistle.com> Subject: Re: inetd: realloc/free bug In-Reply-To: <3670EC02.D35D99CC@isocor.ie> from Peter Edwards at "Dec 11, 98 01:55:14 am" To: peter.edwards@isocor.ie (Peter Edwards) Date: Fri, 11 Dec 1998 11:40:58 -0800 (PST) Cc: dillon@apollo.backplane.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Edwards writes: > > It's not trivial if you want to guarantee that no signals are missed. > > There's no way atomically to: unblock signals and call select(). > > Hmm. I must be twisted. > What horror results from doing this in a signal handler? On e-paper, it > seems to give the desired effect, but does a return from a signal > handler implicitly call sigreturn(2) when it returns? And if so, is > there anything that requires this to happen? I guess I was thinking in terms of the event library model; that is, you don't handle the signal event in the signal handler (because in general the event handler could call malloc(), etc), but rather you simply set a flag (call it "signalFlag"). The race condition is getting a signal between the first and second lines below: sigprocmask(SIG_UNBLOCK ..) /* unblock signals */ r = select(...) /* wait for event */ sigprocmask(SIG_BLOCK ..) /* block signals */ if (signalFlag || r > 0) { ... /* handle event(s) */ } But there are probably smarter ways to do it than this. -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 Fri Dec 11 11:44:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17960 for freebsd-current-outgoing; Fri, 11 Dec 1998 11:44:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17951 for ; Fri, 11 Dec 1998 11:44:30 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA06676; Fri, 11 Dec 1998 11:42:46 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdmT6668; Fri Dec 11 19:42:40 1998 Message-ID: <367175AB.695678E2@whistle.com> Date: Fri, 11 Dec 1998 11:42:35 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Warner Losh CC: Matthew Dillon , Archie Cobbs , jwd@unx.sas.com, freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812110659.WAA35073@apollo.backplane.com> <199812110654.WAA25455@bubba.whistle.com> <199812110711.AAA00506@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <199812110659.WAA35073@apollo.backplane.com> Matthew Dillon writes: > : :By the way, from man select(2): > : : > : : BUGS > : : select() should probably return the time remaining from the original > : : timeout, if any, by modifying the time value in place. This may be im- > : : plemented in future versions of the system. Thus, it is unwise to assume > : : that the timeout value will be unmodified by the select() call. > : : > : :Is this ever going to be implemented? I think this warning's been > : :around for at least 10 years now.. > > No. It breaks too many things. less and less all the time, as Linux does this.. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 11:53:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18861 for freebsd-current-outgoing; Fri, 11 Dec 1998 11:53:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lamb.sas.com (lamb.sas.com [192.35.83.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18856 for ; Fri, 11 Dec 1998 11:53:22 -0800 (PST) (envelope-from jwd@unx.sas.com) Received: from mozart (mozart.unx.sas.com [192.58.184.8]) by lamb.sas.com (8.9.1/8.9.1) with SMTP id OAA09724; Fri, 11 Dec 1998 14:53:04 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA15086; Fri, 11 Dec 1998 14:53:04 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id OAA19914; Fri, 11 Dec 1998 14:53:04 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812111953.OAA19914@bb01f39.unx.sas.com> Subject: Re: inetd: realloc/free bug In-Reply-To: <199812111940.LAA27652@bubba.whistle.com> from Archie Cobbs at "Dec 11, 98 11:40:58 am" To: archie@whistle.com (Archie Cobbs) Date: Fri, 11 Dec 1998 14:53:04 -0500 (EST) Cc: peter.edwards@isocor.ie, dillon@apollo.backplane.com, jwd@unx.sas.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 just had to say in front of me: > Peter Edwards writes: > > > It's not trivial if you want to guarantee that no signals are missed. > > > There's no way atomically to: unblock signals and call select(). > > > > Hmm. I must be twisted. > > What horror results from doing this in a signal handler? On e-paper, it > > seems to give the desired effect, but does a return from a signal > > handler implicitly call sigreturn(2) when it returns? And if so, is > > there anything that requires this to happen? > > I guess I was thinking in terms of the event library model; that is, > you don't handle the signal event in the signal handler (because in > general the event handler could call malloc(), etc), but rather you > simply set a flag (call it "signalFlag"). > > The race condition is getting a signal between the first and second > lines below: > > sigprocmask(SIG_UNBLOCK ..) /* unblock signals */ > r = select(...) /* wait for event */ > sigprocmask(SIG_BLOCK ..) /* block signals */ > > if (signalFlag || r > 0) { > ... /* handle event(s) */ > } > > But there are probably smarter ways to do it than this. > > -Archie Oh, I don't know. I have a task management system where I feed all signals back through pipes. My process is basically one large state machine, and using select() to determine that a sigchld just occurred let's me deal with children as a state which can then forward to other states as required depending on exit status, etc. It let's me treat remote children death the same as local children death (ie: The remote signal handler simply write()s to a pipe that points back to the task manager). Overall, I believe this to be a rather elegant solution to handling out-of-band transaction information. -John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 11:56:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19216 for freebsd-current-outgoing; Fri, 11 Dec 1998 11:56:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19198; Fri, 11 Dec 1998 11:56:28 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA19368; Fri, 11 Dec 1998 11:55:10 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma019361; Fri, 11 Dec 98 11:54:51 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA27864; Fri, 11 Dec 1998 11:54:51 -0800 (PST) From: Archie Cobbs Message-Id: <199812111954.LAA27864@bubba.whistle.com> Subject: Re: HEADS UP : laptop power-down change In-Reply-To: <199812111739.KAA03402@harmony.village.org> from Warner Losh at "Dec 11, 98 10:39:19 am" To: imp@village.org (Warner Losh) Date: Fri, 11 Dec 1998 11:54:51 -0800 (PST) Cc: mike@smith.net.au, current@FreeBSD.ORG, mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (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 Warner Losh writes: > In message <199812110803.AAA00533@dingo.cdrom.com> Mike Smith writes: > : > : Why the change? The current behavior seems right to me. > : Yes. There is a perfectly good set of run-time options which allow you > : to determine at any time whether you want to power-off or halt; having > : a kernel option override this would be stupid. > > But the i386 code doesn't *HAVE* a rom monitor to drop back into... > We just go into a loop that says press any key to reboot. Not exactly > useful. The apm code is i386 specific, by definition. The theory is that halt != power down. Anyone can understand this because there are real world examples of (non i386) computers that drop into a monitor upon halt. No argument there. FreeBSD is (ideally) independent of specific architectures/hardware. Therefore, to be consistent and non-hardware-specific FreeBSD should support both -h and -p. Now in the subcase that you're running FreeBSD on i386 with no monitor ROM, then I don't what's wrong with making '-h' and '-p' degenerate, ie, they both do the same thing: halt the system and cause a power off. -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 Fri Dec 11 11:58:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19581 for freebsd-current-outgoing; Fri, 11 Dec 1998 11:58:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19568 for ; Fri, 11 Dec 1998 11:58:21 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id LAA19435 for ; Fri, 11 Dec 1998 11:58:10 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma019428; Fri, 11 Dec 98 11:57:59 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id LAA27876 for freebsd-current@FreeBSD.ORG; Fri, 11 Dec 1998 11:57:59 -0800 (PST) From: Archie Cobbs Message-Id: <199812111957.LAA27876@bubba.whistle.com> Subject: Re: inetd: realloc/free bug In-Reply-To: <199812111940.LAA27652@bubba.whistle.com> from Archie Cobbs at "Dec 11, 98 11:40:58 am" To: freebsd-current@FreeBSD.ORG Date: Fri, 11 Dec 1998 11:57:59 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL38 (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: > > What horror results from doing this in a signal handler? On e-paper, it > > seems to give the desired effect, but does a return from a signal > > handler implicitly call sigreturn(2) when it returns? And if so, is > > there anything that requires this to happen? > > I guess I was thinking in terms of the event library model; that is, > you don't handle the signal event in the signal handler (because in > general the event handler could call malloc(), etc), but rather you > simply set a flag (call it "signalFlag"). > > The race condition is getting a signal between the first and second > lines below: > > sigprocmask(SIG_UNBLOCK ..) /* unblock signals */ > r = select(...) /* wait for event */ > sigprocmask(SIG_BLOCK ..) /* block signals */ > > if (signalFlag || r > 0) { > ... /* handle event(s) */ > } OK, if you call the signal "event" handler from within the actual signal handler because of a signal received bewtween lines 1 and 2, that's OK because you know you're not in a recursive malloc() situation. So I guess that would work. -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 Fri Dec 11 12:10:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21297 for freebsd-current-outgoing; Fri, 11 Dec 1998 12:10:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21290; Fri, 11 Dec 1998 12:10:49 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id MAA19600; Fri, 11 Dec 1998 12:08:10 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma019596; Fri, 11 Dec 98 12:08:02 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id MAA28016; Fri, 11 Dec 1998 12:08:02 -0800 (PST) From: Archie Cobbs Message-Id: <199812112008.MAA28016@bubba.whistle.com> Subject: Re: mformat in free(): warning: junk pointer, too high to make sense. In-Reply-To: <2490.913366276@verdi.nethelp.no> from "sthaug@nethelp.no" at "Dec 11, 98 09:51:16 am" To: sthaug@nethelp.no Date: Fri, 11 Dec 1998 12:08:02 -0800 (PST) Cc: jkh@zippy.cdrom.com, eivind@yes.no, vallo@matti.ee, current@FreeBSD.ORG, dg@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 X-MIME-Autoconverted: from 8bit to quoted-printable by bubba.whistle.com id MAA28016 Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA21291 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no writes: > > Well, this brings up an unrelated question. I've written a little > > library that comes in very handy in situations like this (I have > > heard there are similar things out there but this was a custom job). > > This would be good to have in the system. Have you compared your lib > with Paul Vixie's eventlib, part of BIND 8.1.x? The man page is in > src/lib/isc/eventlib.mdoc in the 8.1.2 source. A small part is > included below. ... > DESCRIPTION > This library provides multiple outstanding asynchronous timers and I/O to > a cooperating application. The model is similar to that of the X Toolk­ > it, in that events are registered with the library and the application > spends most of its time in the evMainLoop() function. If an application > already has a main loop, it can safely register events with this library > as long as it periodically calls the evGetNext() and evDispatch() func­ > tions. (Note that evGetNext() has both polling and blocking modes.) Looks like the same idea but much more complete (and probably faster, better tested, etc..) I'd love to break this out into it's own library in src/lib. I think lots of people would find it useful. What kind of backlash could I expect? :-) The other libraries look interesting too: "heap", "tree", "logging", etc. -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 Fri Dec 11 12:18:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA22421 for freebsd-current-outgoing; Fri, 11 Dec 1998 12:18:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA22411 for ; Fri, 11 Dec 1998 12:18:47 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 13552 invoked by uid 1001); 11 Dec 1998 20:18:35 +0000 (GMT) To: archie@whistle.com Cc: jkh@zippy.cdrom.com, eivind@yes.no, vallo@matti.ee, current@FreeBSD.ORG, dg@FreeBSD.ORG Subject: Re: mformat in free(): warning: junk pointer, too high to make sense. In-Reply-To: Your message of "Fri, 11 Dec 1998 12:08:02 -0800 (PST)" References: <199812112008.MAA28016@bubba.whistle.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Fri, 11 Dec 1998 21:18:35 +0100 Message-ID: <13550.913407515@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > This would be good to have in the system. Have you compared your lib > > with Paul Vixie's eventlib, part of BIND 8.1.x? The man page is in > > src/lib/isc/eventlib.mdoc in the 8.1.2 source. A small part is > > included below. > ... > Looks like the same idea but much more complete (and probably faster, > better tested, etc..) I'd love to break this out into it's own library > in src/lib. I think lots of people would find it useful. What kind of > backlash could I expect? :-) I suggest looking at the copyright notice and see if it is agreeable, and probably sending a notice to Paul Vixie/ISC about your intentions. They're pretty reasonable people. We used eventlib in a reasonably large project a year and a half ago. Worked rather well for us. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 12:33:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24337 for freebsd-current-outgoing; Fri, 11 Dec 1998 12:33:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24318; Fri, 11 Dec 1998 12:33:26 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id VAA02263; Fri, 11 Dec 1998 21:29:52 +0100 (CET) To: Archie Cobbs cc: imp@village.org (Warner Losh), mike@smith.net.au, current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: HEADS UP : laptop power-down change In-reply-to: Your message of "Fri, 11 Dec 1998 11:54:51 PST." <199812111954.LAA27864@bubba.whistle.com> Date: Fri, 11 Dec 1998 21:29:50 +0100 Message-ID: <2261.913408190@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not to pick on anybody in particular, but... WHY is it, that AGAIN and AGAIN, without any end is sight, minor changes which everybody and his aunt will be able to live with, generate endless filibustering sagas on the mailing lists ? If you guys have so much time on your hands, why don't you go close a PR or ten ? Poul-Henning In message <199812111954.LAA27864@bubba.whistle.com>, Archie Cobbs writes: >Warner Losh writes: >> In message <199812110803.AAA00533@dingo.cdrom.com> Mike Smith writes: >> : > : Why the change? The current behavior seems right to me. >> : Yes. There is a perfectly good set of run-time options which allow you >> : to determine at any time whether you want to power-off or halt; having >> : a kernel option override this would be stupid. >> >> But the i386 code doesn't *HAVE* a rom monitor to drop back into... >> We just go into a loop that says press any key to reboot. Not exactly >> useful. The apm code is i386 specific, by definition. > > > >The theory is that halt != power down. Anyone can understand this >because there are real world examples of (non i386) computers that >drop into a monitor upon halt. No argument there. > >FreeBSD is (ideally) independent of specific architectures/hardware. >Therefore, to be consistent and non-hardware-specific FreeBSD should >support both -h and -p. > >Now in the subcase that you're running FreeBSD on i386 with no monitor >ROM, then I don't what's wrong with making '-h' and '-p' degenerate, >ie, they both do the same thing: halt the system and cause a power off. > > > >-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 > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 13:06:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA29709 for freebsd-current-outgoing; Fri, 11 Dec 1998 13:06:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA29671 for ; Fri, 11 Dec 1998 13:06:39 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.8.7/8.8.7) with UUCP id VAA04150; Fri, 11 Dec 1998 21:06:00 GMT (envelope-from rb@gid.co.uk) Date: Fri, 11 Dec 1998 21:04:13 GMT Received: from [194.32.164.2] by seagoon.gid.co.uk; Fri, 11 Dec 1998 21:04:13 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <199812110220.TAA65513@harmony.village.org> References: Your message of "Thu, 10 Dec 1998 17:48:20 PST." Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" To: Warner Losh From: Bob Bishop Subject: Re: PAO Integration? Cc: jfesler@gigo.com, current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 7:20 pm -0700 10/12/98, Warner Losh wrote: >Solaris 2.4 or 2.5 was the first to support soft power off, if I >recall correctly. In the timeline of unix, that can hardly be called >"traditional." :-) FWIW, the 3b2 had soft poweroff / enter firmware implemented via runlevels 6 & 7 IIRC. Under SysVr3.2 yet. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 13:14:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01098 for freebsd-current-outgoing; Fri, 11 Dec 1998 13:14:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA01074; Fri, 11 Dec 1998 13:14:47 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoZtO-0001aB-00; Fri, 11 Dec 1998 14:14:30 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id OAA04488; Fri, 11 Dec 1998 14:13:02 -0700 (MST) Message-Id: <199812112113.OAA04488@harmony.village.org> To: Poul-Henning Kamp Subject: Re: HEADS UP : laptop power-down change Cc: Archie Cobbs , mike@smith.net.au, current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 11 Dec 1998 21:29:50 +0100." <2261.913408190@critter.freebsd.dk> References: <2261.913408190@critter.freebsd.dk> Date: Fri, 11 Dec 1998 14:13:02 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <2261.913408190@critter.freebsd.dk> Poul-Henning Kamp writes: : If you guys have so much time on your hands, why don't you go close a PR : or ten ? I'd file a PR on this and close it, but I want to make sure that Mike and I don't get into a checkin stalemate. Put another way, why aren't more serious problems being solved? Yes, it is a minor change, but why make it to the kernel? having halt and halt -p map to the same thing on i386 seems reasonable to me. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 13:16:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01460 for freebsd-current-outgoing; Fri, 11 Dec 1998 13:16:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA01437; Fri, 11 Dec 1998 13:16:52 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zoZvO-0001aN-00; Fri, 11 Dec 1998 14:16:34 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id OAA04520; Fri, 11 Dec 1998 14:15:06 -0700 (MST) Message-Id: <199812112115.OAA04520@harmony.village.org> To: Archie Cobbs Subject: Re: HEADS UP : laptop power-down change Cc: mike@smith.net.au, current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Fri, 11 Dec 1998 11:54:51 PST." <199812111954.LAA27864@bubba.whistle.com> References: <199812111954.LAA27864@bubba.whistle.com> Date: Fri, 11 Dec 1998 14:15:06 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812111954.LAA27864@bubba.whistle.com> Archie Cobbs writes: : FreeBSD is (ideally) independent of specific architectures/hardware. : Therefore, to be consistent and non-hardware-specific FreeBSD should : support both -h and -p. Agreed. : Now in the subcase that you're running FreeBSD on i386 with no monitor : ROM, then I don't what's wrong with making '-h' and '-p' degenerate, : ie, they both do the same thing: halt the system and cause a power off. Also agreed. For a power managed i386 system, I see no benefit from not mapping the two to the same thing. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 13:27:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02763 for freebsd-current-outgoing; Fri, 11 Dec 1998 13:27:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02757 for ; Fri, 11 Dec 1998 13:27:40 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.054 #18) id 0zoVH5-0006HK-00; Fri, 11 Dec 1998 16:18:39 +0000 Date: Fri, 11 Dec 1998 16:18:39 +0000 From: Ben Smithurst To: "Roman V. Palagin" Cc: freebsd-current@FreeBSD.ORG Subject: Re: panic: ffs_blkfree: bad size Message-ID: <19981211161839.B24115@scientia.demon.co.uk> References: <19981210183519.A725@scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: User-Agent: Mutt/0.94.17i (FreeBSD/3.0-CURRENT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Roman V. Palagin wrote: > On Thu, 10 Dec 1998, Ben Smithurst wrote: > > > Anyone know what could have caused this: > > > > dev = 0x40002, bno = 124, bsize = 8192, size = 8192, fs = /home > > panic: ffs_blkfree: bad size > > > > FreeBSD -current, ~1 week old (not sure exactly how old). > Check your version of /sys/kern/vfs_cluster.c. It should be 1.75 > (1998/12/05) Yep, done that. Also been pointed at the thread about a week ago about this... *grumble* I really must start paying more attention to this list :-) -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 13:28:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02860 for freebsd-current-outgoing; Fri, 11 Dec 1998 13:28:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02853 for ; Fri, 11 Dec 1998 13:28:20 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from ben by scientia.demon.co.uk with local (Exim 2.054 #18) id 0zoYNG-0006mk-00; Fri, 11 Dec 1998 19:37:14 +0000 Date: Fri, 11 Dec 1998 19:37:14 +0000 From: Ben Smithurst To: npe@bfc.dk Cc: freebsd-current@FreeBSD.ORG Subject: Re: Aout to ELF Message-ID: <19981211193714.A26080@scientia.demon.co.uk> References: <412566D7.0037C51A.00@bfc.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <412566D7.0037C51A.00@bfc.dk> User-Agent: Mutt/0.94.17i (FreeBSD/3.0-CURRENT) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG npe@bfc.dk wrote: > I'm wondering if there's any documentation on how to change from aout to > elf kernels ?? I thought that a make aout-to-elf world do the trick.. But > it fails with a missing script... If you told us what script was missing someone may be able to work out what you've done wrong. -- Ben Smithurst ben@scientia.demon.co.uk send a blank message to ben+pgp@scientia.demon.co.uk for PGP key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 13:38:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03892 for freebsd-current-outgoing; Fri, 11 Dec 1998 13:38:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pox.remarque.org (pox.remarque.org [206.80.1.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03876; Fri, 11 Dec 1998 13:38:38 -0800 (PST) (envelope-from rob@remarque.org) Received: from anthrax.hotwired.com ([206.15.78.67]) by pox.remarque.org (8.9.1a/8.9.1) with ESMTP id NAA05568; Fri, 11 Dec 1998 13:31:27 -0800 (PST) Message-Id: <199812112131.NAA05568@pox.remarque.org> To: Warner Losh cc: Poul-Henning Kamp , Archie Cobbs , mike@smith.net.au, current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: HEADS UP : laptop power-down change In-reply-to: Your message of "Fri, 11 Dec 1998 14:13:02 MST." <199812112113.OAA04488@harmony.village.org> From: rob@remarque.org (Rob Robertson) Date: Fri, 11 Dec 1998 13:31:23 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG having halt and halt -p map to the same thing on i386 seems reasonable to me. ok, so how do you halt the processor without turning off the machine? create another command or option if you want to power off the machine [ or just use the -p option, which is pretty specific ]. rob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 15:10:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13291 for freebsd-current-outgoing; Fri, 11 Dec 1998 15:10:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from osiris.kuniv.edu.kw ([139.141.220.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13278 for ; Fri, 11 Dec 1998 15:10:37 -0800 (PST) (envelope-from root@isis.dynip.com) Received: from osiris.kuniv.edu.kw (localhost.kuniv.edu.kw [127.0.0.1]) by osiris.kuniv.edu.kw (8.8.8/8.8.8) with SMTP id BAA10783 for ; Sat, 12 Dec 1998 01:56:14 +0200 (EET) From: Charlie Roots To: freebsd-current@FreeBSD.ORG Subject: Errors During make buildworld Reply-To: root@isis.dynip.com X-Mailer: KMail [version 0.4.3] Date: Sat, 12 Dec 1998 01:50:33 +0200 MIME-Version: 1.0 Message-Id: <98121201561401.10521@osiris.kuniv.edu.kw> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there Newly cvsuped source files, as of today, fail to compile Apparenly the defective branch is /usr/src/usr.bin/make/lst.lib compat.o: Job.o: main.o: They all give Undefined Symbol '__error' referenced from text segment the interesting thing that newly compiled ports also fail for the same reason WOW man , this new elf stuff is really dangerous I am doing all this on my ONLY machine if YOU --> kill it next time I'll be loggin in with my 'old, but not so risky' MS-SHIT 95 Help GUYS, GO FreeBSD TEAM, KILL US ALL :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 15:14:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13641 for freebsd-current-outgoing; Fri, 11 Dec 1998 15:14:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13636 for ; Fri, 11 Dec 1998 15:14:08 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.9.1/8.8.5) with SMTP id XAA03029; Fri, 11 Dec 1998 23:12:45 GMT Date: Fri, 11 Dec 1998 23:12:45 +0000 (GMT) From: Doug Rabson To: Atsushi Furuta cc: mike@smith.net.au, y-nakaga@nwsl.mesh.ad.jp, nate@mt.sri.com, nathan@rtfm.net, current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812111128.UAA26264@sramhc.sra.co.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 11 Dec 1998, Atsushi Furuta wrote: > Hi, I am Atsushi Furuta, a member of the newcofig. > > >> In article <199812110210.SAA00665@dingo.cdrom.com>, > Mike Smith writes: > > > Much of the work that you still have to do on > > the newconfig stuff has already been done. > > For example, itojun-san's point of > > Date: Tue, 09 Jun 1998 13:21:42 +0900 > From: Jun-ichiro Itoh > Subject: new config > Message-ID: <9929.897366102@cardamom.itojun.org> > > - Cannot pass "flags" field to pci devices. > - Having foo_softc[NFOO] is A BAD THING, thinking about pci/isapnp > devices. We must avoid this. > > is not implemented in the current FreeBSD. Many dirty ISA hack such > as static softc, isa_devtab_wdc, is still holded. The newconfig cleard > up much of them. The softc issue is addressed by the new device framework. The pci support code has not yet been updated to the new interface but when it is, it will get this for free. The flags field can also be easily added. > > Our stance is that such problems should be cleared up as soon as > possible. It seems to me that the roadmap is not intended to solve > these problem. For me, the newconfig is only a step to do so. > > BTW, I agree with Cho-san's opinion. I want to discuss with new-bus > poeple to solve these problem. Please tell me about the new-bus ML. It > is first time that I hear the new-bus ML. There is a list hosted by majordomo@bostonradio.org which Garrett set up. There isn't a list at freebsd.org specifically for this subject but I guess freebsd-arch would be suitable. -- 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 Fri Dec 11 16:15:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19901 for freebsd-current-outgoing; Fri, 11 Dec 1998 16:15:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sparky.isocor.com (sparky.isocor.com [198.6.228.217]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA19886 for ; Fri, 11 Dec 1998 16:15:04 -0800 (PST) (envelope-from peter.edwards@isocor.ie) Received: from isocor.ie (198.6.229.204) by sparky.isocor.com (NPlex 4.0.000); Fri, 11 Dec 1998 16:14:54 -0800 Message-ID: <3671B6B6.792BA595@isocor.ie> Date: Fri, 11 Dec 1998 16:20:06 -0800 From: Peter Edwards Organization: ISOCOR X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Archie Cobbs CC: freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812111957.LAA27876@bubba.whistle.com> 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 wrote: > > > sigprocmask(SIG_UNBLOCK ..) /* unblock signals */ > > r = select(...) /* wait for event */ > > sigprocmask(SIG_BLOCK ..) /* block signals */ > > > > if (signalFlag || r > 0) { > > ... /* handle event(s) */ > > } > > OK, if you call the signal "event" handler from within the actual > signal handler because of a signal received bewtween lines 1 and 2, > that's OK because you know you're not in a recursive malloc() situation. > So I guess that would work. I think someone else mentioned the problem where the select() timeout can delay processing if the signal arrives inside the race window. That's what I was suggesting getting around with the setjmp/longjmp from signal handler. I know its pretty horrendous, but I just got side-tracked into thinking about what happens normally between the time you return from a signal handler and the synchronous program flow resumes. Can anyone synopsize? Cheers, Peter. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 17:09:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24899 for freebsd-current-outgoing; Fri, 11 Dec 1998 17:09:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24894 for ; Fri, 11 Dec 1998 17:09:31 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA41407; Fri, 11 Dec 1998 16:31:02 -0800 (PST) (envelope-from dillon) Date: Fri, 11 Dec 1998 16:31:02 -0800 (PST) From: Matthew Dillon Message-Id: <199812120031.QAA41407@apollo.backplane.com> To: Peter Edwards Cc: Archie Cobbs , freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812111957.LAA27876@bubba.whistle.com> <3671B6B6.792BA595@isocor.ie> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've commited my fix to inetd. As I said before, there really isn't much to it. You simply allow signal operation around the select() code and block signals at all other times and you are done. No fancy pipes, no fancy global flags, insignificantly delayed signal operation (and nominally not delayed at all), inherent event serialization, etc etc etc. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 18:21:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01193 for freebsd-current-outgoing; Fri, 11 Dec 1998 18:21:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from NS1.HomeMortgageUSA.Com (Shell.Bourg.Net [207.229.69.135]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01150; Fri, 11 Dec 1998 18:21:08 -0800 (PST) (envelope-from gus@Bourg.Net) Received: from localhost (gus@localhost) by NS1.HomeMortgageUSA.Com (8.9.1/8.8.7) with SMTP id SAA21764; Fri, 11 Dec 1998 18:25:50 -0800 (PST) (envelope-from gus@Bourg.Net) Date: Fri, 11 Dec 1998 18:25:50 -0800 (PST) From: Gus Bourg X-Sender: gus@NS1.HomeMortgageUSA.Com To: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: gettimeofday/named 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 some FreeBSD-Current machines running named. I'm having a little bit of a challenege with them, though. Named is taking up all of the CPU on the machine. Some of these machines are running SMP kernels and some aren't. 79892 root 105 0 15348K 15128K CPU1 0 18.9H 98.63% 98.63% named 15816 root 93 0 9772K 9512K RUN 176:14 99.22% 99.22% named As you can see here, named isn't being very nice. :-) I did a ktrace on it, and then a dump. Heres what I got: 79892 named CALL gettimeofday(0xefbfda84,0) 79892 named RET gettimeofday 0 79892 named CALL sendto(0x4,0x83fba80,0x1e,0,0x850d07c,0x10) 79892 named GIO fd 4 wrote 30 bytes "\M^B\^T\0\0\0\^A\0\0\0\0\0\0\bnocharge\^Cnet\0\0\^O\0\^A" 79892 named RET sendto 30/0x1e 79892 named CALL gettimeofday(0x8084b04,0) 79892 named RET gettimeofday 0 79892 named CALL gettimeofday(0xefbfda84,0) 79892 named RET gettimeofday 0 79892 named CALL sendto(0x4,0x83efe80,0x1e,0,0x8bcebec,0x10) 79892 named GIO fd 4 wrote 30 bytes "\M^B\^S\0\0\0\^A\0\0\0\0\0\0\bnocharge\^Cnet\0\0\^O\0\^A" Anyone know whats wrong? Thanks Gus Bourg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 22:16:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA20616 for freebsd-current-outgoing; Fri, 11 Dec 1998 22:16:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-da.dialup.hilink.com.au [203.2.144.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA20593; Fri, 11 Dec 1998 22:16:50 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA00825; Fri, 11 Dec 1998 22:14:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812120614.WAA00825@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: Mike Smith , current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: HEADS UP : laptop power-down change In-reply-to: Your message of "Fri, 11 Dec 1998 10:39:19 MST." <199812111739.KAA03402@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Dec 1998 22:14:19 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <199812110803.AAA00533@dingo.cdrom.com> Mike Smith writes: > : > : Why the change? The current behavior seems right to me. > : Yes. There is a perfectly good set of run-time options which allow you > : to determine at any time whether you want to power-off or halt; having > : a kernel option override this would be stupid. > > But the i386 code doesn't *HAVE* a rom monitor to drop back into... > We just go into a loop that says press any key to reboot. Not exactly > useful. The apm code is i386 specific, by definition. The APM code is i386 specific, and the Sun power-management code (should it exist) would be Sparc specific, and if there's an Alpha box with power control, code for that will be Alpha-specific. So what? Power down means power down. Halt means halt. The two are different things, even if one or the other doesn't have a significant meaning in a given special case. There are good reasons to halt an i386 system rather than power cycle it, even if APM is active. > There are many places where we have kernel options that override > stuff, I fail to see how this is different. At the very least I'd > like to make it a sysctl so I can set it in my boot scripts. How hard is it to change _one_commandline_option_ when you call shutdown(8)? Come on... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 22:26:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21660 for freebsd-current-outgoing; Fri, 11 Dec 1998 22:23:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-da.dialup.hilink.com.au [203.2.144.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21650 for ; Fri, 11 Dec 1998 22:23:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id AAA00831; Fri, 11 Dec 1998 00:56:08 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812110856.AAA00831@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kenjiro Cho cc: NAKAGAWA Yoshihisa , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Fri, 11 Dec 1998 16:55:32 +0900." <199812110755.QAA10039@hotaka.csl.sony.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Dec 1998 00:56:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Second, PAO enhanced irq-pool, dynamic irq-pool. So, pccardd get > > free-irq from kernel. > > >> This is an example of an unacceptable solution rerettably typical to > >> the PAO project - you folks are *too*narrowly*focussed* on your needs. > > It seems to me that the two parties don't communicate well. I'd have to agree with that; there are important points about direction that certainly haven't been communicated adequately. > The new-bus people talk from the view of the entire architecture, but > the focus of the PAO people is how to face the reality *NOW*. If that was all they were doing, that'd be ideal. The real problems arising at the moment however stem from the PAO team laying plans for long-term development without considering the directions that other groups are taking. > The two parties should respect differences in their positions. > I for one feel that both efforts are very important for laptop users. I think this is a sentiment that we all share; I'm not entirely sure how to go about improving the situation so that the PAO folks can concentrate on finding and fixing specific issues while remaining inside the ongoing development framework. We had hoped that making Tatsumi a committer would provide a means for the groups to come together, but this hasn't happened. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 22:59:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25206 for freebsd-current-outgoing; Fri, 11 Dec 1998 22:59:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [128.120.56.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25199 for ; Fri, 11 Dec 1998 22:59:15 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id WAA02480; Fri, 11 Dec 1998 22:59:00 -0800 (PST) (envelope-from obrien) Message-ID: <19981211225900.C2440@nuxi.com> Date: Fri, 11 Dec 1998 22:59:00 -0800 From: "David O'Brien" To: Archie Cobbs Cc: current@FreeBSD.ORG Subject: Re: buildworld and PAM and login and stuff Reply-To: obrien@NUXI.com References: <28468.913257133@zippy.cdrom.com> <199812100310.TAA12329@bubba.whistle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812100310.TAA12329@bubba.whistle.com>; from Archie Cobbs on Wed, Dec 09, 1998 at 07:10:25PM -0800 X-Operating-System: FreeBSD 3.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 > Brings up a related question I was wondering about.. what happens > if you compile the kernel -O2? All my FreeBSD kernels for the past two years have been compiled with: COPTFLAGS= -O2 -m486 -pipe -fno-strength-reduce (Two years ago I had 486's. Today I don't know if the -m486 helps or hurts performance on my K6's and K5's) -- -- David (obrien@NUXI.ucdavis.edu -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 Fri Dec 11 23:08:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26465 for freebsd-current-outgoing; Fri, 11 Dec 1998 23:08:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from titanium.yy.ics.keio.ac.jp (titanium.yy.ics.keio.ac.jp [131.113.47.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA26438 for ; Fri, 11 Dec 1998 23:08:48 -0800 (PST) (envelope-from sanpei@sanpei.org) Received: from lavender.sanpei.org (u4168.seaple.icc.ne.jp [203.140.32.168]) by titanium.yy.ics.keio.ac.jp (8.8.8+3.0Wbeta13/3.7W) with ESMTP id QAA04867; Sat, 12 Dec 1998 16:06:56 +0900 (JST) Received: (from sanpei@localhost) by lavender.sanpei.org (8.8.8/3.6W) id QAA22991; Sat, 12 Dec 1998 16:06:54 +0900 (JST) Message-Id: <199812120706.QAA22991@lavender.sanpei.org> To: mike@smith.net.au Cc: current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: Your message of "Thu, 10 Dec 1998 08:54:30 JST". <199812092354.PAA01185@dingo.cdrom.com> Date: Sat, 12 Dec 1998 16:06:54 +0900 From: MIHIRA Sanpei Yoshiro Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG mike@smith.net.au wrote: >> > >> > Do NE2000 Compatible PCMCIA cards work under PAO3, as it is now? >> > If so, is the development snapshot available anywhere? >> >> They work fine under stock 2.2 and 3.0 (this message is being sent >> using one). Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit I have three NE2000 compatible PCMCIA cards. I can use two cards with FreeBSD-current which added some lines to /etc/pccard.conf, but can't use another one. Under PAO, I can use all these cards. I compare these CIS via pccardc dumpcis command. o unusable cards has memory descriptor. o usable cards does not have it. Tuple #6, code = 0x1b (Configuration entry), length = 25 000: c1 81 78 ca 61 00 03 0f 10 03 0f 30 fc be c9 04 010: 00 00 40 0d 40 40 00 40 0d Config index = 0x1(default) Interface byte = 0x81 (I/O) wait signal supported Card decodes 10 address lines, limited 8/16 Bit I/O I/O address # 1: block start = 0x300 block length = 0x10 I/O address # 2: block start = 0x310 block length = 0x10 IRQ modes: Level IRQs: 2 3 4 5 6 7 9 10 11 12 13 15 Memory descriptor 1 <------------------- blk length = 0x400 card addr = 0x000 host addr = 0xd4000 Memory descriptor 2 <------------------- blk length = 0x4000 card addr = 0x4000 host addr = 0xd4000 ---------- Review pccardd. PAO's assign_io function in pccardd/cardd.c has related code but it's comment is ``XXX -- dirty hack for some 'ed' cards that have incomplete iomem CIS tupples.'' But FreeBSD-current's assign_io function does not have it. I think that Mike's card does not have Memory descriptor.. Is that right? Thank you. MIHIRA Yoshiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Dec 11 23:52:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA00209 for freebsd-current-outgoing; Fri, 11 Dec 1998 23:52:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA00193; Fri, 11 Dec 1998 23:52:54 -0800 (PST) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id BAA07702; Sat, 12 Dec 1998 01:52:05 -0600 (CST) From: Kevin Day Message-Id: <199812120752.BAA07702@home.dragondata.com> Subject: Re: HEADS UP : laptop power-down change In-Reply-To: <199812120614.WAA00825@dingo.cdrom.com> from Mike Smith at "Dec 11, 1998 10:14:19 pm" To: mike@smith.net.au (Mike Smith) Date: Sat, 12 Dec 1998 01:52:05 -0600 (CST) Cc: imp@village.org, mike@smith.net.au, current@FreeBSD.ORG, mobile@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > But the i386 code doesn't *HAVE* a rom monitor to drop back into... > > We just go into a loop that says press any key to reboot. Not exactly > > useful. The apm code is i386 specific, by definition. > > The APM code is i386 specific, and the Sun power-management code > (should it exist) would be Sparc specific, and if there's an Alpha box > with power control, code for that will be Alpha-specific. > So what? Power down means power down. Halt means halt. The two are > different things, even if one or the other doesn't have a significant > meaning in a given special case. There are good reasons to halt an > i386 system rather than power cycle it, even if APM is active. > One good use: When changing some pcmcia cards that must be present at bootup for me to use, I: shutdown -h put the card in press a key to reboot. I don't want it to power off in this case. Can we please not make -h power off? :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 01:00:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA04233 for freebsd-current-outgoing; Sat, 12 Dec 1998 01:00:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA04226 for ; Sat, 12 Dec 1998 01:00:21 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 24046 invoked by uid 1001); 12 Dec 1998 09:00:10 +0000 (GMT) To: gus@Bourg.Net Cc: current@FreeBSD.ORG, smp@FreeBSD.ORG Subject: Re: gettimeofday/named In-Reply-To: Your message of "Fri, 11 Dec 1998 18:25:50 -0800 (PST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 12 Dec 1998 10:00:10 +0100 Message-ID: <24044.913453210@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I have some FreeBSD-Current machines running named. I'm having a little > bit of a challenege with them, though. Named is taking up all of the CPU > on the machine. Some of these machines are running SMP kernels and some > aren't. Are you running the standard FreeBSD named (ie 8.1.2) from -current? How many zones do you have? > As you can see here, named isn't being very nice. :-) I did a ktrace on > it, and then a dump. Heres what I got: > 79892 named CALL gettimeofday(0xefbfda84,0) > 79892 named RET gettimeofday 0 > 79892 named CALL sendto(0x4,0x83fba80,0x1e,0,0x850d07c,0x10) > 79892 named GIO fd 4 wrote 30 bytes > "\M^B\^T\0\0\0\^A\0\0\0\0\0\0\bnocharge\^Cnet\0\0\^O\0\^A" > 79892 named RET sendto 30/0x1e > 79892 named CALL gettimeofday(0x8084b04,0) > 79892 named RET gettimeofday 0 > 79892 named CALL gettimeofday(0xefbfda84,0) > 79892 named RET gettimeofday 0 > 79892 named CALL sendto(0x4,0x83efe80,0x1e,0,0x8bcebec,0x10) > 79892 named GIO fd 4 wrote 30 bytes > "\M^B\^S\0\0\0\^A\0\0\0\0\0\0\bnocharge\^Cnet\0\0\^O\0\^A" I see long sequences of gettimeofday() right after a named restart - that's when it tries do get the SOA of every zone it's secondary for, to check that the zone is current. After it's finished verifying the zones, things get nice and quiet. You need to look at some longer traces, I think. Is named spending its time on system calls, or in userland? How many gettimeofday() calls do you have per second? Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 02:33:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA09688 for freebsd-current-outgoing; Sat, 12 Dec 1998 02:33:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ha1.rdc2.occa.home.com (ha1.rdc2.occa.home.com [24.2.8.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA09683 for ; Sat, 12 Dec 1998 02:33:56 -0800 (PST) (envelope-from shadey@home.com) Received: from shadey ([24.1.169.119]) by ha1.rdc2.occa.home.com (Post.Office MTA v3.5 release 217 ID# 0-53853L0S0V35) with SMTP id com for ; Sat, 12 Dec 1998 02:33:56 -0800 Message-ID: <003401be25ba$7c545940$0201a8c0@shadey.oow.com> From: "Enoch Ceshkovsky" To: Subject: NATD/Libalias leaks Date: Sat, 12 Dec 1998 02:30:48 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have noticed that the 3.0 & up version of NATD leaks away on mem (usually growing to about 17MB in 5 days) I remember -stable having this problem right after they merged with -current (pre 3.0) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 04:05:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA17817 for freebsd-current-outgoing; Sat, 12 Dec 1998 04:05:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pa.scotland.net (pa1.scotland.net [194.247.64.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA17812 for ; Sat, 12 Dec 1998 04:05:19 -0800 (PST) (envelope-from freebsd@timog.prestel.co.uk) Received: from [148.176.237.8] (helo=timog.prestel.co.uk) by pa.scotland.net with esmtp (Exim 1.90 #4) for freebsd-current@FreeBSD.ORG id 0zonnQ-0006P0-00; Sat, 12 Dec 1998 12:05:17 +0000 Received: (qmail 689 invoked by uid 1002); 12 Dec 1998 09:56:18 -0000 Message-ID: <19981212095617.A670@prestel.co.uk> Date: Sat, 12 Dec 1998 09:56:17 +0000 From: Timo Geusch To: freebsd-current@FreeBSD.ORG Subject: Re: Errors During make buildworld References: <98121201561401.10521@osiris.kuniv.edu.kw> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <98121201561401.10521@osiris.kuniv.edu.kw>; from Charlie Roots on Sat, Dec 12, 1998 at 01:50:33AM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, if you'd checked the mailing list archive before updating (or read -current between your last cvsup and the one that break stuff) you'd have noticed that there were some changes to the way errno is handled (has to be a macro for correct handling in threaded programs) which give exactly the symptoms you describe. You'd also see that this horse has already been flogged to death and back. BTW, simply attributing that problem to 'elf' really shows that you did some proper research before contacting the mailing list. Sheesh. T. On Sat, Dec 12, 1998 at 01:50:33AM +0200, Charlie Roots wrote: > Hi there > Newly cvsuped source files, as of today, fail to compile > Apparenly the defective branch is > > /usr/src/usr.bin/make/lst.lib > > compat.o: > Job.o: > main.o: > They all give > > Undefined Symbol '__error' referenced from text segment > > the interesting thing that newly compiled ports also fail for the same reason > > WOW man , this new elf stuff is really dangerous > I am doing all this on my ONLY machine > if YOU --> kill it > next time I'll be loggin in with my 'old, but not so risky' MS-SHIT 95 > > Help GUYS, GO FreeBSD TEAM, KILL US ALL :-) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 05:25:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA23536 for freebsd-current-outgoing; Sat, 12 Dec 1998 05:25:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from widefw.csl.sony.co.jp (widefw.csl.sony.co.jp [133.138.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA23531 for ; Sat, 12 Dec 1998 05:25:40 -0800 (PST) (envelope-from kjc@csl.sony.co.jp) Received: from hotaka.csl.sony.co.jp (root@hotaka.csl.sony.co.jp [43.27.98.57]) by widefw.csl.sony.co.jp (8.8.8/3.6W) with ESMTP id WAA04154; Sat, 12 Dec 1998 22:25:34 +0900 (JST) Received: from localhost (kjc@[127.0.0.1]) by hotaka.csl.sony.co.jp (8.8.8/3.6W/hotaka/98111120) with ESMTP id WAA08728; Sat, 12 Dec 1998 22:25:33 +0900 (JST) Message-Id: <199812121325.WAA08728@hotaka.csl.sony.co.jp> To: Mike Smith cc: NAKAGAWA Yoshihisa , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Fri, 11 Dec 1998 00:56:06 PST." <199812110856.AAA00831@dingo.cdrom.com> Date: Sat, 12 Dec 1998 22:25:33 +0900 From: Kenjiro Cho Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith said: > The new-bus people talk from the view of the entire architecture, but > the focus of the PAO people is how to face the reality *NOW*. >> If that was all they were doing, that'd be ideal. The real problems >> arising at the moment however stem from the PAO team laying plans for >> long-term development without considering the directions that other >> groups are taking. This is a communication problem. I did some research on this issue in the -hackers archive. When itojun brought up "newconfig" back in June, you said you would support it if it works. Jordan encouraged them to give it a try. Then, the PAO team decided to go for "newconfig". Apperently, new-bus has evolved a lot since then and the situation has changed, but the PAO folks are unaware of the directions that other groups are taking. The following messages are found in the archive. Mike Smith said (08 Jun): > If something is already decided about this topic, please give me > some pointer for the discussion archive. I do not want to spend > my time to this, if it will never be merged into. From an entirely pragmatic perspective, "new" config is better than "old" config. It's not the solution we are looking for, but it's a step in the right direction. If the integration will be carried through to completion, then I would be inclined to offer my support (whatever that's worth 8). Then, Jordan said (08 Jun): Well, every time this comes up, a number of folks chime in with "but config(8) is fundamentally WRONG! We must get rid of it entirely, not upgrade it!" and it is my suggestion that you simply ignore all of those people and go right on ahead with this idea. The reason I suggest ignoring them has to do with the fact that it's exceedingly easy to point out the flaws in config(8) but obviously not so easy to architect a complete replacement or someone would have done so by now. Note that I'm not even talking about an implementation, I'm talking about a reasonable attempt to even _architect_ such a thing. I've seen many a pie-in-the-sky treatise go by about how things ought to work, but not much which really went into significant detail on how a migration away from config(8) should be done and a sample timeline showing which tasks will need to be done and in what order. If the NetBSD/BSDI folks have improved config(8) to the point where it's signficantly more usable, I don't see the harm in going in that direction. If the new-paradigm weenies also want to use that as a sufficient goad to get them to really implement a complete replacement, then that's pretty much a win too since nothing else seems to be motivating them these days. DG also said that he was neutral on the issue. --Kenjiro To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 05:51:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25424 for freebsd-current-outgoing; Sat, 12 Dec 1998 05:51:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ozz.etrust.ru ([195.2.84.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25419 for ; Sat, 12 Dec 1998 05:51:18 -0800 (PST) (envelope-from osa@etrust.ru) Received: from localhost (localhost [127.0.0.1]) by ozz.etrust.ru (8.9.1/8.9.1) with ESMTP id QAA00744 for ; Sat, 12 Dec 1998 16:46:27 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Sat, 12 Dec 1998 16:46:26 +0300 (MSK) From: oZZ!!! To: current@FreeBSD.ORG Subject: ELF-programms under -current... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=KOI8-R Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! How i may run SCO's ELF programms under -current? Rgdz, ïÓÏËÉÎ óÅÒÇÅÊ aka oZZ, osa@etrust.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 07:41:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02991 for freebsd-current-outgoing; Sat, 12 Dec 1998 07:41:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from miris.lcs.mit.edu (miris.lcs.mit.edu [18.111.0.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02973; Sat, 12 Dec 1998 07:41:16 -0800 (PST) (envelope-from beng@miris.lcs.mit.edu) Received: from miris.lcs.mit.edu (beng@localhost [127.0.0.1]) by miris.lcs.mit.edu (8.8.7/8.8.7) with ESMTP id KAA02595; Sat, 12 Dec 1998 10:41:03 -0500 (EST) Message-Id: <199812121541.KAA02595@miris.lcs.mit.edu> X-Mailer: exmh version 2.0.1 12/23/97 To: Warner Losh cc: Mike Smith , current@FreeBSD.ORG, mobile@FreeBSD.ORG Subject: Re: HEADS UP : laptop power-down change In-reply-to: Your message of "Fri, 11 Dec 1998 10:39:19 MST." <199812111739.KAA03402@harmony.village.org> From: Benjamin Greenwald X-Sender: beng@lcs.mit.edu Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Dec 1998 10:41:02 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Might I suggest that if you are so desperate for the old semantics: alias halt='/sbin/halt -p' -Ben > In message <199812110803.AAA00533@dingo.cdrom.com> Mike Smith writes: > : > : Why the change? The current behavior seems right to me. > : Yes. There is a perfectly good set of run-time options which allow you > : to determine at any time whether you want to power-off or halt; having > : a kernel option override this would be stupid. > > But the i386 code doesn't *HAVE* a rom monitor to drop back into... > We just go into a loop that says press any key to reboot. Not exactly > useful. The apm code is i386 specific, by definition. > > There are many places where we have kernel options that override > stuff, I fail to see how this is different. At the very least I'd > like to make it a sysctl so I can set it in my boot scripts. > > Warner > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 10:11:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13291 for freebsd-current-outgoing; Sat, 12 Dec 1998 10:11:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA13286 for ; Sat, 12 Dec 1998 10:11:10 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id NAA61368; Sat, 12 Dec 1998 13:10:52 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: jfesler@gigo.com cc: Warner Losh , current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: PAO Integration? In-reply-to: Your message of "Thu, 10 Dec 1998 17:48:20 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Dec 1998 13:10:52 -0500 Message-ID: <61364.913486252@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jfesler@gigo.com wrote in message ID : > > Why? Traditionally Unix hasn't run on hardware that has software > > power off. Who can say what traditional unix is when the hardware has > > a new feature? > > Solaris on Sun equipment has been doing it a long time. I can telnet, > shutdown with a state of 5, and bewm, buh-bye power. Workstations can be > turned back on via keyboard; the servers I've used actually physically > throws a power switch that has to be manually switched back on. > > Considering the age of the equipment and the OS level I'm using, I can > safely say it's been doing it many years :-). Also consider that it has some serious bugs ... do shutdown -g0 -i5 -y on a UltraSPARC 5 and it'll power down quite happily. If its headless, you're also screwed as it needs a *keyboard* which has the power switch in the corner before it'll switch back on. The power button on the front is useless. *sigh* But you are right, shutdown -i5 is nice. On the other hand, it is *not* the default action of halt or shutdown.... Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 10:44:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15662 for freebsd-current-outgoing; Sat, 12 Dec 1998 10:44:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15653 for ; Sat, 12 Dec 1998 10:44:31 -0800 (PST) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id MAA18141 for freebsd-current@freebsd.org; Sat, 12 Dec 1998 12:44:29 -0600 (CST) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id MAA89952; Sat, 12 Dec 1998 12:43:37 -0600 (CST) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13938.47448.324592.152079@zuhause.zuhause.mn.org> Date: Sat, 12 Dec 1998 12:43:36 -0600 (CST) To: freebsd-current@FreeBSD.ORG Subject: Make world fails in /usr.sbin/usbd X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just cvsupped about an hour ago, and as near as I can tell, the usr/include/dev directory containing dsb.h is not getting created. For the moment, I'm just going to remove the usb programs from the usr.sbin Makefile until I can figure out where the Makefiles would normally create and populate this subdirectory. ===> usr.sbin/usbd cc -O -pipe -I../../sys -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.sbin/usbd/usbd.c gzip -cn /usr/src/usr.sbin/usbd/usbd.8 > usbd.8.gz /usr/src/usr.sbin/usbd/usbd.c:50: dev/usb/usb.h: No such file or directory /usr/src/usr.sbin/usbd/usbd.c: In function `main': /usr/src/usr.sbin/usbd/usbd.c:152: `USB_DISCOVER' undeclared (first use this function) /usr/src/usr.sbin/usbd/usbd.c:152: (Each undeclared identifier is reported only once /usr/src/usr.sbin/usbd/usbd.c:152: for each function it appears in.) *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 11:02:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17117 for freebsd-current-outgoing; Sat, 12 Dec 1998 11:02:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17112 for ; Sat, 12 Dec 1998 11:02:10 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id OAA62038; Sat, 12 Dec 1998 14:01:49 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Enoch Ceshkovsky" cc: current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: NATD/Libalias leaks In-reply-to: Your message of "Sat, 12 Dec 1998 02:30:48 PST." <003401be25ba$7c545940$0201a8c0@shadey.oow.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Dec 1998 14:01:49 -0500 Message-ID: <62034.913489309@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Enoch Ceshkovsky" wrote in message ID <003401be25ba$7c545940$0201a8c0@shadey.oow.com>: > I have noticed that the 3.0 & up version of NATD leaks away on mem (usually > growing to about 17MB in 5 days) I remember -stable having this problem > right after they merged with -current (pre 3.0) Yep. I've also seen it coredump ... see the PR database for a stack backtrace from a recent crash that I got. http://www.freebsd.org/cgi/query-pr.cgi?pr=8962 Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 11:05:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17769 for freebsd-current-outgoing; Sat, 12 Dec 1998 11:05:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17764; Sat, 12 Dec 1998 11:05:31 -0800 (PST) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id NAA19805; Sat, 12 Dec 1998 13:05:30 -0600 (CST) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id NAA21258; Sat, 12 Dec 1998 13:03:37 -0600 (CST) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13938.48647.433050.667678@zuhause.zuhause.mn.org> Date: Sat, 12 Dec 1998 13:03:35 -0600 (CST) To: Nick Hibma Subject: Re: Make world fails in /usr.sbin/usbd In-Reply-To: <13938.47448.324592.152079@zuhause.zuhause.mn.org> References: <13938.47448.324592.152079@zuhause.zuhause.mn.org> X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My guess is that this is your responsibility. I think it needs the following changes: diff -u /usr/src/etc/mtree/BSD.include.dist /tmp/BSD.include.dist --- /usr/src/etc/mtree/BSD.include.dist Sat Dec 5 10:36:23 1998 +++ /tmp/BSD.include.dist Sat Dec 12 12:52:58 1998 @@ -9,6 +9,7 @@ scsi .. .. + dev g++ std .. diff -u /usr/src/Makefile.inc1 /tmp/Makefile.inc1 --- /usr/src/Makefile.inc1 Sat Dec 5 10:34:09 1998 +++ /tmp/Makefile.inc1 Sat Dec 12 13:02:14 1998 @@ -476,7 +476,7 @@ rm -f ${DESTDIR}/usr/src/sys ln -s ${.CURDIR}/sys ${DESTDIR}/usr/src cd ${.CURDIR}/include; find -dx . | cpio -dump ${DESTDIR}/usr/include -.for d in net netatm netinet posix4 sys vm machine +.for d in dev net netatm netinet posix4 sys vm machine if [ -h ${DESTDIR}/usr/include/$d ]; then \ rm -f ${DESTDIR}/usr/include/$d ; \ fi Bruce Albrecht writes: > I just cvsupped about an hour ago, and as near as I can tell, the > usr/include/dev directory containing dsb.h is not getting created. > For the moment, I'm just going to remove the usb programs from the > usr.sbin Makefile until I can figure out where the Makefiles would > normally create and populate this subdirectory. > > ===> usr.sbin/usbd > cc -O -pipe -I../../sys -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.sbin/usbd/usbd.c > gzip -cn /usr/src/usr.sbin/usbd/usbd.8 > usbd.8.gz > /usr/src/usr.sbin/usbd/usbd.c:50: dev/usb/usb.h: No such file or directory > /usr/src/usr.sbin/usbd/usbd.c: In function `main': > /usr/src/usr.sbin/usbd/usbd.c:152: `USB_DISCOVER' undeclared (first use this function) > /usr/src/usr.sbin/usbd/usbd.c:152: (Each undeclared identifier is reported only once > /usr/src/usr.sbin/usbd/usbd.c:152: for each function it appears in.) > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 11:13:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18516 for freebsd-current-outgoing; Sat, 12 Dec 1998 11:13:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA18493; Sat, 12 Dec 1998 11:13:02 -0800 (PST) (envelope-from imp@village.org) Received: from harmony [10.0.0.6] by rover.village.org with esmtp (Exim 1.71 #1) id 0zouTA-0002hV-00; Sat, 12 Dec 1998 12:12:48 -0700 Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.1/8.8.3) with ESMTP id MAA12887; Sat, 12 Dec 1998 12:11:31 -0700 (MST) Message-Id: <199812121911.MAA12887@harmony.village.org> To: Benjamin Greenwald Subject: Re: HEADS UP : laptop power-down change Cc: Mike Smith , current@FreeBSD.ORG, mobile@FreeBSD.ORG In-reply-to: Your message of "Sat, 12 Dec 1998 10:41:02 EST." <199812121541.KAA02595@miris.lcs.mit.edu> References: <199812121541.KAA02595@miris.lcs.mit.edu> Date: Sat, 12 Dec 1998 12:11:31 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812121541.KAA02595@miris.lcs.mit.edu> Benjamin Greenwald writes: : Might I suggest that if you are so desperate for the old semantics: : : alias halt='/sbin/halt -p' sadly that doesn't work with sudo. I'm starting to see that there are reasons for doing the way mike has. I've hacked my apm.c so that I can turn it off, but I've been convinced that Mike's way makes more sense. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 11:15:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19040 for freebsd-current-outgoing; Sat, 12 Dec 1998 11:15:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19034; Sat, 12 Dec 1998 11:15:32 -0800 (PST) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id NAA20669; Sat, 12 Dec 1998 13:15:30 -0600 (CST) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id NAA21331; Sat, 12 Dec 1998 13:10:33 -0600 (CST) (envelope-from bruce) From: Bruce Albrecht MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13938.49064.837111.285479@zuhause.zuhause.mn.org> Date: Sat, 12 Dec 1998 13:10:32 -0600 (CST) To: Nick Hibma , freebsd-current@FreeBSD.ORG Subject: Re: Make world fails in /usr.sbin/usbd In-Reply-To: <13938.48647.433050.667678@zuhause.zuhause.mn.org> References: <13938.47448.324592.152079@zuhause.zuhause.mn.org> <13938.48647.433050.667678@zuhause.zuhause.mn.org> X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, missed one. My guess is that this is your responsibility. I think it needs the following changes: diff -u /usr/src/etc/mtree/BSD.include.dist /tmp/BSD.include.dist --- /usr/src/etc/mtree/BSD.include.dist Sat Dec 5 10:36:23 1998 +++ /tmp/BSD.include.dist Sat Dec 12 12:52:58 1998 @@ -9,6 +9,7 @@ scsi .. .. + dev g++ std .. diff -u /usr/src/Makefile.inc1 /tmp/Makefile.inc1 --- /usr/src/Makefile.inc1 Sat Dec 5 10:34:09 1998 +++ /tmp/Makefile.inc1 Sat Dec 12 13:09:30 1998 @@ -476,13 +476,13 @@ rm -f ${DESTDIR}/usr/src/sys ln -s ${.CURDIR}/sys ${DESTDIR}/usr/src cd ${.CURDIR}/include; find -dx . | cpio -dump ${DESTDIR}/usr/include -.for d in net netatm netinet posix4 sys vm machine +.for d in dev net netatm netinet posix4 sys vm machine if [ -h ${DESTDIR}/usr/include/$d ]; then \ rm -f ${DESTDIR}/usr/include/$d ; \ fi .endfor cd ${.CURDIR}/sys; \ - find -dx net netatm netinet posix4 sys vm -name '*.h' -o -type d | \ + find -dx dev net netatm netinet posix4 sys vm -name '*.h' -o -type d | \ cpio -dump ${DESTDIR}/usr/include mkdir -p ${DESTDIR}/usr/include/machine cd ${.CURDIR}/sys/${MACHINE_ARCH}/include; find -dx . -name '*.h' -o -type d | \ --- Bruce Albrecht writes: > I just cvsupped about an hour ago, and as near as I can tell, the > usr/include/dev directory containing dsb.h is not getting created. > For the moment, I'm just going to remove the usb programs from the > usr.sbin Makefile until I can figure out where the Makefiles would > normally create and populate this subdirectory. > > ===> usr.sbin/usbd > cc -O -pipe -I../../sys -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.sbin/usbd/usbd.c > gzip -cn /usr/src/usr.sbin/usbd/usbd.8 > usbd.8.gz > /usr/src/usr.sbin/usbd/usbd.c:50: dev/usb/usb.h: No such file or directory > /usr/src/usr.sbin/usbd/usbd.c: In function `main': > /usr/src/usr.sbin/usbd/usbd.c:152: `USB_DISCOVER' undeclared (first use this function) > /usr/src/usr.sbin/usbd/usbd.c:152: (Each undeclared identifier is reported only once > /usr/src/usr.sbin/usbd/usbd.c:152: for each function it appears in.) > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 11:25:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19702 for freebsd-current-outgoing; Sat, 12 Dec 1998 11:25:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19696 for ; Sat, 12 Dec 1998 11:25:36 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.1/8.9.1) id OAA05227; Sat, 12 Dec 1998 14:25:30 -0500 (EST) (envelope-from wollman) Date: Sat, 12 Dec 1998 14:25:30 -0500 (EST) From: Garrett Wollman Message-Id: <199812121925.OAA05227@khavrinen.lcs.mit.edu> To: Nate Williams Cc: NAKAGAWA Yoshihisa , Mike Smith , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-Reply-To: <199812100542.WAA21183@mt.sri.com> References: <199812100456.VAA21000@mt.sri.com> <199812100510.OAA02646@chandra.eatell.msr.prug.or.jp> <199812100542.WAA21183@mt.sri.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I disagree. Just because some are ISA doesn't mean that all are ISA. > Also, this makes it harder (not eaiser) to support CardBus in the > future. Not at all. Please join new-bus-arch. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 11:31:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19982 for freebsd-current-outgoing; Sat, 12 Dec 1998 11:31:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ha1.rdc2.occa.home.com (ha1.rdc2.occa.home.com [24.2.8.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19977; Sat, 12 Dec 1998 11:31:49 -0800 (PST) (envelope-from shadey@home.com) Received: from shadey ([24.1.169.119]) by ha1.rdc2.occa.home.com (Post.Office MTA v3.5 release 217 ID# 0-53853L0S0V35) with SMTP id com; Sat, 12 Dec 1998 11:31:48 -0800 Message-ID: <000e01be2605$9f11fa00$0201a8c0@shadey.oow.com> From: "Enoch Ceshkovsky" To: "Gary Palmer" Cc: Subject: Re: NATD/Libalias leaks Date: Sat, 12 Dec 1998 11:28:39 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsup'ed the latest -stable libalias & natd to a separate directory, just compiled both & installed. Problem solved, no leaks plus its much faster. (lower ping times on quake, etc) Perhaps the -current team can just copy the -stable over since it seems that -stable has done quite a bit of work to it. > >Yep. I've also seen it coredump ... see the PR database for a stack backtrace >from a recent crash that I got. > >http://www.freebsd.org/cgi/query-pr.cgi?pr=8962 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 11:40:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA20796 for freebsd-current-outgoing; Sat, 12 Dec 1998 11:40:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from abby.skypoint.net (abby.skypoint.net [199.86.32.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA20790; Sat, 12 Dec 1998 11:40:49 -0800 (PST) (envelope-from bruce@zuhause.mn.org) Received: (from uucp@localhost) by abby.skypoint.net (8.8.7/jl 1.3) with UUCP id NAA22536; Sat, 12 Dec 1998 13:40:48 -0600 (CST) Received: (from bruce@localhost) by zuhause.mn.org (8.9.1/8.9.1) id NAA69877; Sat, 12 Dec 1998 13:35:03 -0600 (CST) (envelope-from bruce) From: Bruce Albrecht Message-ID: <13938.50532.845226.978382@zuhause.zuhause.mn.org> Date: Sat, 12 Dec 1998 13:35:00 -0600 (CST) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nick Hibma , freebsd-current@FreeBSD.ORG Subject: Re: Make world fails in /usr.sbin/usbd In-Reply-To: <13938.48647.433050.667678@zuhause.zuhause.mn.org> References: <13938.47448.324592.152079@zuhause.zuhause.mn.org> <13938.48647.433050.667678@zuhause.zuhause.mn.org> X-Mailer: VM 6.62 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bleah, I should have tried to run it first. The mtree was wrong, and I don't think the Makefile.inc1 is right, either, because it's creating a set of include/dev subdirectories. I'm not sure what the right way to just pull in sys/dev/usb/usb.h into include/dev. I guess I'll let the Makefile experts handle this one... My guess is that this is your responsibility. I think it needs the following changes: diff -u /usr/src/etc/mtree/BSD.include.dist /tmp/BSD.include.dist --- /usr/src/etc/mtree/BSD.include.dist Sat Dec 5 10:36:23 1998 +++ /tmp/BSD.include.dist Sat Dec 12 12:52:58 1998 @@ -9,6 +9,8 @@ scsi .. .. + dev + .. g++ std .. diff -u /usr/src/Makefile.inc1 /tmp/Makefile.inc1 --- /usr/src/Makefile.inc1 Sat Dec 5 10:34:09 1998 +++ /tmp/Makefile.inc1 Sat Dec 12 13:09:30 1998 @@ -476,7 +476,7 @@ rm -f ${DESTDIR}/usr/src/sys ln -s ${.CURDIR}/sys ${DESTDIR}/usr/src cd ${.CURDIR}/include; find -dx . | cpio -dump ${DESTDIR}/usr/include -.for d in net netatm netinet posix4 sys vm machine +.for d in dev net netatm netinet posix4 sys vm machine if [ -h ${DESTDIR}/usr/include/$d ]; then \ rm -f ${DESTDIR}/usr/include/$d ; \ fi --- Bruce Albrecht writes: > I just cvsupped about an hour ago, and as near as I can tell, the > usr/include/dev directory containing dsb.h is not getting created. > For the moment, I'm just going to remove the usb programs from the > usr.sbin Makefile until I can figure out where the Makefiles would > normally create and populate this subdirectory. > > ===> usr.sbin/usbd > cc -O -pipe -I../../sys -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/usr.sbin/usbd/usbd.c > gzip -cn /usr/src/usr.sbin/usbd/usbd.8 > usbd.8.gz > /usr/src/usr.sbin/usbd/usbd.c:50: dev/usb/usb.h: No such file or directory > /usr/src/usr.sbin/usbd/usbd.c: In function `main': > /usr/src/usr.sbin/usbd/usbd.c:152: `USB_DISCOVER' undeclared (first use this function) > /usr/src/usr.sbin/usbd/usbd.c:152: (Each undeclared identifier is reported only once > /usr/src/usr.sbin/usbd/usbd.c:152: for each function it appears in.) > *** Error code 1 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 15:20:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09814 for freebsd-current-outgoing; Sat, 12 Dec 1998 15:20:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09800; Sat, 12 Dec 1998 15:20:54 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id AAA08713; Sun, 13 Dec 1998 00:20:45 +0100 (CET) To: current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: if_sppp is BROKEN!!! From: Poul-Henning Kamp Date: Sun, 13 Dec 1998 00:20:42 +0100 Message-ID: <8711.913504842@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think I have finally found out what the problem is with the state machine in the if_sppp implementation. Whoever wrote the implementation didn't carefully consider the inter-layer calls tls and tlf. If one applies a lot of patches like this one: case STATE_OPENED: - (cp->tld)(sp); sp->rst_counter[cp->protoidx] = 0; sppp_cp_change_state(cp, sp, STATE_STOPPING); + (cp->tld)(sp); goto sta; break; Then things actually start to make sense... The problem is that the tld and tlf functions often just call the pp_up and pp_down routines directly, and therefore most if not all of the expected up and down events happen in the previous state as opposed to the next state. Flipping it around like I have done above, on the other hand, may not be a good idea either, since it means we can nest another layer on the stack and get somewhat confused on the way down. It is quite obvious that this will need some more work to sort out, anybody interested in participating ? -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 16:11:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15983 for freebsd-current-outgoing; Sat, 12 Dec 1998 16:11:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp-d9.dialup.hilink.com.au [203.2.144.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15954 for ; Sat, 12 Dec 1998 16:11:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id WAA00877; Fri, 11 Dec 1998 22:22:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812120622.WAA00877@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Stephane E. Potvin" cc: current@FreeBSD.ORG Subject: Re: [Fwd: HEADS UP : laptop power-down change] In-reply-to: Your message of "Fri, 11 Dec 1998 14:29:35 EST." <3671729F.9CF2280D@videotron.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 11 Dec 1998 22:22:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please format your messages in a fashion conducive to replies if you expect same. > > Yes. There is a perfectly good set of run-time options which allow you > > to determine at any time whether you want to power-off or halt; having > > a kernel option override this would be stupid. > > It's not stupid at all in the current context. The majority of us that > have laptop uses i386 compatible processors that don't have the system > monitor you mention. Fine. Please note that we now run on systems that do. Keeping the functional difference between platforms as small as possible is a desirable goal. Notwithstanding this, it is useful to be able to halt rather than shut down an i386 system, and mandating a disable of APM before doing this is not a usable solution. > Changing the behavior of the halt command is > gratuitious in our context and will only break current applications like > kdm (part of kde) that expect the -h flag to shutdown the laptop, not > halting it. At least could you put an option in the kernel config file > until such applications are changed to expect the new flag? No; such options tend to rot. If you're really so concerned about this, it's easier still for you to wrap shutdown in a script to do your translation for you. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Sat Dec 12 16:33:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17862 for freebsd-current-outgoing; Sat, 12 Dec 1998 16:33:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17856 for ; Sat, 12 Dec 1998 16:33:05 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA10714; Sat, 12 Dec 1998 16:33:04 -0800 (PST) (envelope-from dillon) Date: Sat, 12 Dec 1998 16:33:04 -0800 (PST) From: Matthew Dillon Message-Id: <199812130033.QAA10714@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: rc.local changes commited Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (heads up!) /usr/share/etc/rc.local's minimal functionality has been moved to /usr/share/etc/rc and rc.local has been removed from the CVS tree. Various manual pages and comments have also been updated. rc.local is, of course, still supported by rc. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 17:27:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23205 for freebsd-current-outgoing; Sat, 12 Dec 1998 17:27:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23196 for ; Sat, 12 Dec 1998 17:27:02 -0800 (PST) (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 LAA18032; Sun, 13 Dec 1998 11:56:40 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA00507; Sun, 13 Dec 1998 11:56:37 +1030 (CST) Message-ID: <19981213115637.A483@freebie.lemis.com> Date: Sun, 13 Dec 1998 11:56:37 +1030 From: Greg Lehey To: FreeBSD current users Cc: "Justin T. Gibbs" , "Kenneth D. Merry" Subject: Can't access tapes with scsi_sa.c r1.7 Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=liOOAslEiF7prFVr X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog 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 --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii I built a new kernel yesterday with the latest cam mods, including scsi_sa.c revision 1.7. With this version I was not able to access my Exabyte 8505XL: a read failed with EIO and no console message. I backed out the revision, and it works fine now. What should I do to narrow down the problem? I'm attaching a -v dmesg output. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key --liOOAslEiF7prFVr Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.boot.2" Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #122: Sat Dec 12 14:51:55 CST 1998 grog@freebie.lemis.com:/T/src/FREEBIE/src/sys/compile/FREEBIE Calibrating clock(s) ... TSC clock: 233839897 Hz, i8254 clock: 1193060 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 233839897 Hz CPU: AMD-K6tm w/ multimedia extensions (233.84-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping=2 Features=0x8001bf Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 160M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable real memory = 167772160 (163840K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002cc000 - 0x09ff7fff, 164806656 bytes (40236 pages) config> quit avail memory = 159858688 (156112K bytes) Found BIOS32 Service Directory header at 0xf00fb060 Entry = 0xfb4e0 (0xf00fb4e0) Rev = 0 Len = 1 PCI BIOS entry at 0xb510 DMI header at 0xf00f5e30 Version 2.0 Table at 0xf0800, 30 entries, 673 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000fc080 pci_open(1): mode 1 addr port (0x0cf8) is 0x80000074 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=80] is there (id=55911039) Probing for devices on PCI bus 0: found-> vendor=0x1039, dev=0x5591, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base e0000000, size 26 chip0: rev 0x02 on pci0.0.0 found-> vendor=0x1039, dev=0x5513, revid=0xd0 class=01-01-8a, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=14 map[0]: type 4, range 32, base 000001f0, size 3 map[1]: type 4, range 32, base 000003f4, size 2 map[2]: type 4, range 32, base 00000170, size 3 map[3]: type 4, range 32, base 00000374, size 2 map[4]: type 4, range 32, base 00004000, size 4 ide_pci0: rev 0xd0 int a irq 14 on pci0.0.1 generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 0 status: 04 from port: 00004002 generic_status: no PCI IDE timing info available generic_status: no PCI IDE timing info available ide_pci: busmaster 1 status: 04 from port: 0000400a found-> vendor=0x1039, dev=0x0008, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x01 on pci0.1.0 found-> vendor=0x1039, dev=0x0009, revid=0x00 class=ff-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x1039, dev=0x7001, revid=0x11 class=0c-03-10, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 1, range 32, base ea000000, size 12 found-> vendor=0x1039, dev=0x0001, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip2: rev 0x00 on pci0.2.0 found-> vendor=0x9004, dev=0x7178, revid=0x03 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 4, range 32, base 0000e000, size 8 map[1]: type 1, range 32, base ea001000, size 12 ahc0: rev 0x03 int a irq 11 on pci0.9.0 ahc0: Reading SEEPROM...done. ahc0: High byte termination Enabled ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs ahc0: Resetting Channel A ahc0: Downloading Sequencer Program... 410 instructions downloaded found-> vendor=0x102b, dev=0x0519, revid=0x01 class=03-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 1, range 32, base e5000000, size 14 map[1]: type 3, range 32, base e6000000, size 23 vga0: rev 0x01 int a irq 10 on pci0.10.0 found-> vendor=0x1002, dev=0x4354, revid=0x09 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base e7000000, size 24 vga1: rev 0x09 on pci0.11.0 found-> vendor=0x11f6, dev=0x1401, revid=0x0a class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000e400, size 5 ed2: rev 0x0a int a irq 10 on pci0.12.0 ed2: address 00:80:48:e6:a0:61, type NE2000 (16 bit) bpf: ed2 attached Probing for devices on PCI bus 1: Probing for devices on the ISA bus: video: RTC equip. code:0x0f, DCC code:0xf9 video: CRTC:0x3d4, video option:0x60, rows:80, cols:25, font height:16 video: param table EGA/VGA:0xf00c02d4, CGA/MDA:0 video: rows_offset:1 video#0: adapter type:VGA (5), flags:0x7f, CRTC:0x3d4 video#0: init mode:24, bios mode:3, current mode:24 video#0: window:0xf00b8000 size:32k gran:32k, buf:0xf0000000 size:0k video#0: mode:0, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:1, flags:0x1 T 40x25, font:8x8, win:0xb8000 video#0: mode:2, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:3, flags:0x1 T 80x25, font:8x8, win:0xb8000 video#0: mode:19, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:20, flags:0x1 T 40x25, font:8x14, win:0xb8000 video#0: mode:21, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:22, flags:0x1 T 80x25, font:8x14, win:0xb8000 video#0: mode:23, flags:0x1 T 40x25, font:8x16, win:0xb8000 video#0: mode:25, flags:0x0 T 80x25, font:8x16, win:0xb0000 video#0: mode:24, flags:0x1 T 80x25, font:8x16, win:0xb8000 video#0: mode:7, flags:0x0 T 80x25, font:8x14, win:0xb0000 video#0: mode:112, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:113, flags:0x1 T 80x43, font:8x8, win:0xb8000 video#0: mode:33, flags:0x0 T 80x30, font:8x16, win:0xb0000 video#0: mode:32, flags:0x1 T 80x30, font:8x16, win:0xb8000 video#0: mode:31, flags:0x0 T 80x50, font:8x8, win:0xb0000 video#0: mode:30, flags:0x1 T 80x50, font:8x8, win:0xb8000 video#0: mode:35, flags:0x0 T 80x60, font:8x8, win:0xb0000 video#0: mode:34, flags:0x1 T 80x60, font:8x8, win:0xb8000 video#0: mode:4, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:5, flags:0x3 G 320x200x2, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:6, flags:0x3 G 640x200x1, 1 plane(s), font:8x8, win:0xb8000 video#0: mode:13, flags:0x3 G 320x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:14, flags:0x3 G 640x200x4, 4 plane(s), font:8x8, win:0xa0000 video#0: mode:15, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:17, flags:0x2 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:16, flags:0x3 G 640x350x2, 2 plane(s), font:8x14, win:0xa0000 video#0: mode:18, flags:0x3 G 640x350x4, 4 plane(s), font:8x14, win:0xa0000 video#0: mode:26, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:27, flags:0x3 G 640x480x4, 4 plane(s), font:8x16, win:0xa0000 video#0: mode:28, flags:0x3 G 320x200x8, 1 plane(s), font:8x8, win:0xa0000 video#0: mode:37, flags:0x3 G 320x240x8, 1 plane(s), font:8x8, win:0xa0000 VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: the current keyboard controller command byte 0047 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0: keyboard device ID: ab41 sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 ed1 not found at 0x300 sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2: irq maps: 0x1 0x21 0x1 0x1 sio2 at 0x3e8-0x3ef irq 5 on isa sio2: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached psm0: current command byte:0047 kbdio: TEST_AUX_PORT status:0000 kbdio: RESET_AUX return code:00fa kbdio: RESET_AUX status:00aa kbdio: RESET_AUX ID:0000 psm: status 00 02 64 psm: status b1 03 c8 psm: status b1 03 c8 psm: status b1 03 c8 psm: status 00 00 3c psm: data 08 00 00 psm: data 08 00 00 psm: status 00 02 64 psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa ide_pci: generic_dmainit 01f0:1: warning, IDE controller timing not set wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-32 wd0: 1223MB (2504880 sectors), 2485 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0003, dmamword = 0107, apio = 0003, udma = 0000 wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa ide_pci: generic_dmainit 0170:1: warning, IDE controller timing not set wdc1: unit 0 (wd2): , DMA, 32-bit, multi-block-16 wd2: 6197MB (12692736 sectors), 12592 cyls, 16 heads, 63 S/T, 512 B/S wd2: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 ide_pci: generic_dmainit 0170:1: warning, IDE controller timing not set wdc1: unit 1 (wd3): , DMA, 32-bit, multi-block-16 wd3: 8063MB (16514064 sectors), 16383 cyls, 16 heads, 63 S/T, 512 B/S wd3: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 ep0 not found at 0x300 npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 66220780 bytes/sec bzero() bandwidth = 74239049 bytes/sec imasks: bio c008c040, tty c00714ba, net c00714ba BIOS Geometries: 0:01fe1f3f 0..510=511 cylinders, 0..31=32 heads, 1..63=63 sectors 1:01fe1f3f 0..510=511 cylinders, 0..31=32 heads, 1..63=63 sectors 2:03fefe3f 0..1022=1023 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. bpf: tun0 attached bpf: tun1 attached bpf: tun2 attached bpf: tun3 attached bpf: sl0 attached bpf: ppp0 attached bpf: ppp1 attached new masks: bio c008c040, tty c00714ba, net c00714ba bpf: lo0 attached Waiting 3 seconds for SCSI devices to settle (noperiph:ahc0:0:X:X): SCSI bus reset delivered. 0 SCBs aborted. ahc0: Selection Timeout on A:1. 1 SCBs aborted (probe4:ahc0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe4:ahc0:0:4:0): ILLEGAL REQUEST asc:24,0 (probe4:ahc0:0:4:0): Invalid field in CDB (probe5:ahc0:0:5:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe5:ahc0:0:5:0): ILLEGAL REQUEST field replaceable unit: 20 ahc0: target 3 synchronous at 5.0MHz, offset = 0xb ahc0: target 4 synchronous at 5.0MHz, offset = 0xf ahc0: target 0 synchronous at 10.0MHz, offset = 0xf (probe1:ahc0:0:4:1): INQUIRY. CDB: 12 21 80 0 ff 0 (probe1:ahc0:0:4:1): ILLEGAL REQUEST asc:24,0 (probe1:ahc0:0:4:1): Invalid field in CDB sa0 at ahc0 bus 0 target 3 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: Serial Number 06746337 sa0: 5.0MB/s transfers (5.0MHz, offset 11) sa1 at ahc0 bus 0 target 4 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: 5.0MB/s transfers (5.0MHz, offset 15) sa2 at ahc0 bus 0 target 5 lun 0 sa2: Removable Sequential Access SCSI-CCS device sa2: 3.300MB/s transfers pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number 5U2X6149 pass0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled pass1 at ahc0 bus 0 target 2 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number DX007NE pass1: 3.300MB/s transfers, Tagged Queueing Enabled pass2 at ahc0 bus 0 target 3 lun 0 pass2: Removable Sequential Access SCSI-2 device pass2: Serial Number 06746337 pass2: 5.0MB/s transfers (5.0MHz, offset 11) pass3 at ahc0 bus 0 target 4 lun 0 pass3: Removable Sequential Access SCSI-2 device pass3: 5.0MB/s transfers (5.0MHz, offset 15) pass4 at ahc0 bus 0 target 4 lun 1 pass4: Removable Changer SCSI-2 device pass4: 5.0MB/s transfers (5.0MHz, offset 15) pass5 at ahc0 bus 0 target 5 lun 0 pass5: Removable Sequential Access SCSI-CCS device pass5: 3.300MB/s transfers pass6 at ahc0 bus 0 target 6 lun 0 pass6: Removable CD-ROM SCSI-2 device pass6: 3.300MB/s transfers pass7 at ahc0 bus 0 target 6 lun 1 pass7: Removable CD-ROM SCSI-2 device pass7: 3.300MB/s transfers pass8 at ahc0 bus 0 target 6 lun 2 pass8: Removable CD-ROM SCSI-2 device pass8: 3.300MB/s transfers pass9 at ahc0 bus 0 target 6 lun 3 pass9: Removable CD-ROM SCSI-2 device pass9: 3.300MB/s transfers pass10 at ahc0 bus 0 target 6 lun 4 pass10: Removable CD-ROM SCSI-2 device pass10: 3.300MB/s transfers pass11 at ahc0 bus 0 target 6 lun 5 pass11: Removable CD-ROM SCSI-2 device pass11: 3.300MB/s transfers pass12 at ahc0 bus 0 target 6 lun 6 pass12: Removable CD-ROM SCSI-2 device pass12: 3.300MB/s transfers pass4 at ahc0 bus 0 target 4 lun 1 pass4: Removable Changer SCSI-2 device pass4: 5.0MB/s transfers (5.0MHz, offset 15) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number DX007NE da1: 3.300MB/s transfers, Tagged Queueing Enabled da1: 4096MB (8388608 512 byte sectors: 64H 32S/T 4096C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [322273 x 2048 byte records] da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number 5U2X6149 da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 2063MB (4226725 512 byte sectors: 64H 32S/T 2063C) Considering FFS root f/s. changing root device to wd0s1a wd0s1: type 0xa5, start 63, end = 2504879, size 2504817 : OK da0: invalid primary partition table: no magic wd2s1: type 0xa5, start 63, end = 12692735, size 12692673 : OK da1s1: type 0xa5, start 0, end = 8388607, size 8388608 da1s1: C/H/S end 522/42/32 (719647) != end 8388607: invalid wd3: invalid primary partition table: no magic wd2s1: type 0xa5, start 63, end = 12692735, size 12692673 : OK da1s1: type 0xa5, start 0, end = 8388607, size 8388608 da1s1: C/H/S end 522/42/32 (719647) != end 8388607: invalid wd3: invalid primary partition table: no magic cd1 at ahc0 bus 0 target 6 lun 1 cd1: Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: cd present [328327 x 2048 byte records] Linux-ELF exec handler installed cd2 at ahc0 bus 0 target 6 lun 2 cd2: Removable CD-ROM SCSI-2 device cd2: 3.300MB/s transfers cd2: cd present [304767 x 2048 byte records] cd3 at ahc0 bus 0 target 6 lun 3 cd3: Removable CD-ROM SCSI-2 device cd3: 3.300MB/s transfers cd3: cd present [327689 x 2048 byte records] cd4 at ahc0 bus 0 target 6 lun 4 cd4: Removable CD-ROM SCSI-2 device cd4: 3.300MB/s transfers cd4: cd present [265441 x 2048 byte records] cd5 at ahc0 bus 0 target 6 lun 5 cd5: Removable CD-ROM SCSI-2 device cd5: 3.300MB/s transfers cd5: cd present [326322 x 2048 byte records] cd6 at ahc0 bus 0 target 6 lun 6 cd6: Removable CD-ROM SCSI-2 device cd6: 3.300MB/s transfers cd6: cd present [295879 x 2048 byte records] pid 333 (Xaccel): trap 12 with interrupts disabled --liOOAslEiF7prFVr-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 17:29:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23558 for freebsd-current-outgoing; Sat, 12 Dec 1998 17:29:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23546; Sat, 12 Dec 1998 17:29:27 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id BAA01271; Sun, 13 Dec 1998 01:29:10 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id AAA16396; Sun, 13 Dec 1998 00:08:39 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812130008.AAA16396@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: "Enoch Ceshkovsky" cc: "Gary Palmer" , current@FreeBSD.ORG, Eivind Eklund Subject: Re: NATD/Libalias leaks In-reply-to: Your message of "Sat, 12 Dec 1998 11:28:39 PST." <000e01be2605$9f11fa00$0201a8c0@shadey.oow.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 00:08:39 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I cvsup'ed the latest -stable libalias & natd to a separate directory, just > compiled both & installed. Problem solved, no leaks plus its much faster. > (lower ping times on quake, etc) Perhaps the -current team can just copy > the -stable over since it seems that -stable has done quite a bit of work to > it. It's the other way 'round. Libalias in -current has three modifications that have not been committed to -stable, and a few fixes besides. > Version 2.5: December, 1997 (ee) > - Added PKT_ALIAS_PUNCH_FW mode for firewall > bypass of FTP/IRC DCC data connections. Also added > improved TCP connection monitoring. > > Version 2.6: May, 1998 (amurai) > - Added supporting routine for NetBios over TCP/IP. I added alias_cuseeme.c It looks like Matt's going to have a crack at alias_nbt according to his followup to bin/8962. Can you try building the -current version of libalias with -DNO_FW_PUNCH and see if that makes a difference ? If it does, we can point the finger at Eivind (cc'd, hi;) Cheers. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 17:38:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA24313 for freebsd-current-outgoing; Sat, 12 Dec 1998 17:38:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24308 for ; Sat, 12 Dec 1998 17:38:32 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id RAA27546; Sat, 12 Dec 1998 17:38:19 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id RAA01794; Sat, 12 Dec 1998 17:38:18 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id RAA22963; Sat, 12 Dec 1998 17:38:16 -0800 (PST) From: Don Lewis Message-Id: <199812130138.RAA22963@salsa.gv.tsc.tdk.com> Date: Sat, 12 Dec 1998 17:38:16 -0800 In-Reply-To: Matthew Dillon "Re: inetd: realloc/free bug" (Dec 11, 4:31pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Matthew Dillon , Peter Edwards Subject: Re: inetd: realloc/free bug Cc: Archie Cobbs , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 11, 4:31pm, Matthew Dillon wrote: } Subject: Re: inetd: realloc/free bug } I've commited my fix to inetd. As I said before, there } really isn't much to it. You simply allow signal operation } around the select() code and block signals at all other } times and you are done. No fancy pipes, no fancy global } flags, insignificantly delayed signal operation (and } nominally not delayed at all), inherent event serialization, } etc etc etc. It also has the downside of keeping inetd "active", so it can't be totally swapped out if it's not in use. This might be a bit of a concern to some folks, like those who run FreeBSD on their laptops. Your implementation is also more syscall intensive than some of the alternatives. Your patch also doesn't eliminate all the race conditions. When a signal handler is invoked, it blocks reception of the signal that triggered it, but not the reception of other signals, so it is possible for one of the signal handlers to be active when another one is invoked. This is fixable by blocking the other signals from within the handlers, at the expense of more syscalls. I hadn't thought of writing the signals to a pipe and in the past I've always used global flags. I think the pipe idea is kind of elegant because it avoids having to fiddle with the signal masks to avoid race conditions between testing and clearing the flags. Oh yeah, there is another race condition that I've never seen mentioned. In the case of TCP services where we do something like ctrl = accept(...); pid = fork(); if (pid == 0) { fiddle with fds exec(...); } close(ctrl); there is a problem if the child process runs, writes a bunch of data to the socket and exits before the parent process executes the close(). If this happens, the close() in the parent can hang for an indefinite period of time, until the client consumes the buffered data on the socket. I fixed this in BIND 4.x a few years ago using a pipe to synchronize the parent and child processes. This fix would roughly translate as the following (ignoring error checking): int pipefd[2]; char c; ctrl = accept(...); pipe(pipefd); pid = fork(); if (pid == 0) { close(pipefd[1]); /* close the write end */ /* wait for EOF */ while (read(pipefd[0], &c, 1) == -1 && errno == EINTR) ; /* nothing */ close(pipefd[0]); fiddle with fds exec(...); } close(pipefd[0]); /* close the read end */ close(ctrl); close(pipefd[1]); /* close the write end to release the child */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 17:58:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25885 for freebsd-current-outgoing; Sat, 12 Dec 1998 17:58:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25880 for ; Sat, 12 Dec 1998 17:58:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id RAA14315; Sat, 12 Dec 1998 17:58:42 -0800 (PST) (envelope-from dillon) Date: Sat, 12 Dec 1998 17:58:42 -0800 (PST) From: Matthew Dillon Message-Id: <199812130158.RAA14315@apollo.backplane.com> To: Don Lewis Cc: Peter Edwards , Archie Cobbs , freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812130138.RAA22963@salsa.gv.tsc.tdk.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It also has the downside of keeping inetd "active", so it can't :be totally swapped out if it's not in use. This might be a bit :of a concern to some folks, like those who run FreeBSD on their :laptops. Your implementation is also more syscall intensive than :some of the alternatives. We may be able to remove the timeout from the select(), but someone else is going to have to go through the code (as I indicated earlier) to determine that this is the case before removing the timeout. :Your patch also doesn't eliminate all the race conditions. When :a signal handler is invoked, it blocks reception of the signal that :triggered it, but not the reception of other signals, so it is possible Sure it does. Look at the code. Line 410 or so of inetd.c :Oh yeah, there is another race condition that I've never seen mentioned. :In the case of TCP services where we do something like : ctrl = accept(...); : pid = fork(); : if (pid == 0) { : fiddle with fds : exec(...); : } : close(ctrl); :there is a problem if the child process runs, writes a bunch of data :to the socket and exits before the parent process executes the close(). :If this happens, the close() in the parent can hang for an indefinite :period of time, until the client consumes the buffered data on the socket. :I fixed this in BIND 4.x a few years ago using a pipe to synchronize I'm not sure I follow. close() on a socket descriptor does not block. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 18:03:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA26553 for freebsd-current-outgoing; Sat, 12 Dec 1998 18:03:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA26546 for ; Sat, 12 Dec 1998 18:03:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA14359; Sat, 12 Dec 1998 18:03:02 -0800 (PST) (envelope-from dillon) Date: Sat, 12 Dec 1998 18:03:02 -0800 (PST) From: Matthew Dillon Message-Id: <199812130203.SAA14359@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: minor vipw/pwd_mkdb changes commited Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've made a few minor fixes to vipw and pwd_mkdb to handle a master.passwd race condition (note: there are no security issues with the race). Also, pwd_mkdb has been slightly modified to lock the source file. This file is typically a temporary file when pwd_mkdb is run from vipw (etc...). However, when pwd_mkdb is run manually (say, from a script), a race between pwd_mkdb and someone editing master.passwd, running passwd, chpass, etc... can ensue whereby the latter programs replace master.passwd and regenerate the .db files while the original pwd_mkdb is still running, causing the db files to reflect an out-of-date master.passwd. Again, minor bugs but worth fixing. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 18:07:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA27138 for freebsd-current-outgoing; Sat, 12 Dec 1998 18:07:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA27110; Sat, 12 Dec 1998 18:06:57 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA14397; Sat, 12 Dec 1998 18:06:42 -0800 (PST) (envelope-from dillon) Date: Sat, 12 Dec 1998 18:06:42 -0800 (PST) From: Matthew Dillon Message-Id: <199812130206.SAA14397@apollo.backplane.com> To: Brian Somers Cc: "Enoch Ceshkovsky" , "Gary Palmer" , current@FreeBSD.ORG, Eivind Eklund Subject: Re: NATD/Libalias leaks References: <199812130008.AAA16396@keep.lan.Awfulhak.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :It looks like Matt's going to have a crack at alias_nbt according to :his followup to bin/8962. Well, I tried... but after staring at my old windows box (which I haven't turned on in a month) for a few minutes, I decided that actually trying to test the damn thing would be too stressful on my delicate constitution :-) We're going to need someone with a cable modem (like the original bug poster) who regularly gets malformed netbios packets to test it. I'm considering just comitting it (I don't think it will get adequate testing, else). :Brian Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 18:18:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28142 for freebsd-current-outgoing; Sat, 12 Dec 1998 18:18:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28137 for ; Sat, 12 Dec 1998 18:18:48 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id SAA08537; Sat, 12 Dec 1998 18:18:26 -0800 Date: Sat, 12 Dec 1998 18:18:26 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Greg Lehey cc: FreeBSD current users Subject: Re: Can't access tapes with scsi_sa.c r1.7 In-Reply-To: <19981213115637.A483@freebie.lemis.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 Yes, that'd be my change. Whups! It worked for me! Could you build a CAMDEBUG kernel, use camcontrol to turn on debugging for that device and do whatever it is you did and send me the output, or send me what it is you tried first? I'll be in my shop tomorrow morning to work on this! Sorry! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 18:30:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29026 for freebsd-current-outgoing; Sat, 12 Dec 1998 18:30:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp (ykh28DS09.kng.mesh.ad.jp [133.205.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29021 for ; Sat, 12 Dec 1998 18:30:04 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id CAA08579; Sun, 13 Dec 1998 02:40:58 +0900 (JST) Message-Id: <199812121740.CAA08579@chandra.eatell.msr.prug.or.jp> To: mike@smith.net.au, current@FreeBSD.ORG cc: MIHIRA Sanpei Yoshiro Subject: Re: PAO Integration? In-reply-to: Your message of "Sat, 12 Dec 1998 16:06:54 JST." <199812120706.QAA22991@lavender.sanpei.org> Date: Sun, 13 Dec 1998 02:40:58 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > PAO's assign_io function in pccardd/cardd.c has related code but > it's comment is ``XXX -- dirty hack for some 'ed' cards that have > incomplete iomem CIS tupples.'' > But FreeBSD-current's assign_io function does not have it. This PAO enhancement is dirty hack, but some PC-Card has these broken CIS. So, we need it. Another problem, some PC-Card has non-ascii charactor in CIS Version 1 info. So, -current pccardd can't match pccard.conf of this card. PAO enhace pccardd, can use regex in pccard.conf. I think, "PAO is not best answer. But it is necessary." Is PAO Integration necessary? Yes, some PAO enhancement is very useful and needs in some case. Some patch of PAO, it shuld be merge to -current. -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 18:30:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29273 for freebsd-current-outgoing; Sat, 12 Dec 1998 18:30:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp (ykh28DS09.kng.mesh.ad.jp [133.205.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29267 for ; Sat, 12 Dec 1998 18:30:31 -0800 (PST) (envelope-from y-nakaga@nwsl.mesh.ad.jp) Received: from nwsl.mesh.ad.jp (localhost.eatell.msr.prug.or.jp [127.0.0.1]) by chandra.eatell.msr.prug.or.jp (8.8.8/8.8.5) with ESMTP id CAA08603; Sun, 13 Dec 1998 02:57:27 +0900 (JST) Message-Id: <199812121757.CAA08603@chandra.eatell.msr.prug.or.jp> To: Mike Smith cc: Kenjiro Cho , Nathan Dorfman , current@FreeBSD.ORG Subject: Re: PAO Integration? In-reply-to: Your message of "Fri, 11 Dec 1998 00:56:06 PST." <199812110856.AAA00831@dingo.cdrom.com> Date: Sun, 13 Dec 1998 02:57:27 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If that was all they were doing, that'd be ideal. The real problems > arising at the moment however stem from the PAO team laying plans for > long-term development without considering the directions that other > groups are taking. This point, PAO team was wrong. But many Japanese developer have language problem, me too. We are not native speaker of English. English is my weak point. So we have communication problem. I want to change this situation, so I am using many power for communication. It is very hard for me. :-( -- NAKAGAWA, Yoshihisa y-nakaga@nwsl.mesh.ad.jp nakagawa@jp.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 19:00:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA01631 for freebsd-current-outgoing; Sat, 12 Dec 1998 19:00:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA01616; Sat, 12 Dec 1998 19:00:43 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id BAA02248; Sun, 13 Dec 1998 01:48:23 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.1/8.9.1) with ESMTP id BAA00784; Sun, 13 Dec 1998 01:49:37 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199812130149.BAA00784@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Poul-Henning Kamp cc: current@FreeBSD.ORG, isdn@FreeBSD.ORG Subject: Re: if_sppp is BROKEN!!! In-reply-to: Your message of "Sun, 13 Dec 1998 00:20:42 +0100." <8711.913504842@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Dec 1998 01:49:37 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I think I have finally found out what the problem is with the state > machine in the if_sppp implementation. Whoever wrote the implementation > didn't carefully consider the inter-layer calls tls and tlf. > > If one applies a lot of patches like this one: > > case STATE_OPENED: > - (cp->tld)(sp); > sp->rst_counter[cp->protoidx] = 0; > sppp_cp_change_state(cp, sp, STATE_STOPPING); > + (cp->tld)(sp); > goto sta; > break; > > Then things actually start to make sense... > > The problem is that the tld and tlf functions often just call the > pp_up and pp_down routines directly, and therefore most if not all > of the expected up and down events happen in the previous state > as opposed to the next state. > > Flipping it around like I have done above, on the other hand, may > not be a good idea either, since it means we can nest another layer > on the stack and get somewhat confused on the way down. > > It is quite obvious that this will need some more work to sort out, > anybody interested in participating ? I haven't got much time before Christmas, but if you're still looking for volunteers in the new year I'll be interested. I had similar problems with user-ppp, and ended up having the state machine call the TLU/TLS/TLD/TLF, then tweak the state before calling the same function for the parent.... case ST_OPENED: (*fp->fn->LayerDown)(fp); FsmInitRestartCounter(fp); FsmSendTerminateReq(fp); NewState(fp, ST_CLOSING); (*fp->parent->LayerDown)(fp->parent->object, fp); break; A given layer never calls another layer, it just gets called from the state machine. Things aren't as important on the way up, although the TLU has to tell the FSM if it should proceed and call the parent TLU.... if ((*fp->fn->LayerUp)(fp)) (*fp->parent->LayerUp)(fp->parent->object, fp); else { (*fp->fn->LayerDown)(fp); FsmInitRestartCounter(fp); FsmSendTerminateReq(fp); NewState(fp, ST_CLOSING); } Doing it this way certainly confused me less :-) > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 19:32:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA03819 for freebsd-current-outgoing; Sat, 12 Dec 1998 19:32:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA03813 for ; Sat, 12 Dec 1998 19:32:18 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id TAA28023; Sat, 12 Dec 1998 19:32:12 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id TAA03457; Sat, 12 Dec 1998 19:32:10 -0800 (PST) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id TAA23232; Sat, 12 Dec 1998 19:32:09 -0800 (PST) From: Don Lewis Message-Id: <199812130332.TAA23232@salsa.gv.tsc.tdk.com> Date: Sat, 12 Dec 1998 19:32:09 -0800 In-Reply-To: Matthew Dillon "Re: inetd: realloc/free bug" (Dec 12, 5:58pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Matthew Dillon , Don Lewis Subject: Re: inetd: realloc/free bug Cc: Peter Edwards , Archie Cobbs , freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 12, 5:58pm, Matthew Dillon wrote: } Subject: Re: inetd: realloc/free bug } :Your patch also doesn't eliminate all the race conditions. When } :a signal handler is invoked, it blocks reception of the signal that } :triggered it, but not the reception of other signals, so it is possible } } Sure it does. Look at the code. Line 410 or so of inetd.c You appear to be correct. } :Oh yeah, there is another race condition that I've never seen mentioned. } :In the case of TCP services where we do something like } : ctrl = accept(...); } : pid = fork(); } : if (pid == 0) { } : fiddle with fds } : exec(...); } : } } : close(ctrl); } :there is a problem if the child process runs, writes a bunch of data } :to the socket and exits before the parent process executes the close(). } :If this happens, the close() in the parent can hang for an indefinite } :period of time, until the client consumes the buffered data on the socket. } :I fixed this in BIND 4.x a few years ago using a pipe to synchronize } } I'm not sure I follow. close() on a socket descriptor does not block. In the case of BIND, close() blocks because SO_LINGER is set. As long as nothing run from inetd does this, we're probably OK. The reason that BIND uses SO_LINGER is: /* kernels that map pages for IO end up failing if the pipe is full * at exit and we take away the final buffer. this is really a kernel * bug but it's harmless on systems that are not broken, so... */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 19:33:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04113 for freebsd-current-outgoing; Sat, 12 Dec 1998 19:33:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Server785 (ip11.moorestown2.nj.pub-ip.psi.net [38.26.74.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA04105 for ; Sat, 12 Dec 1998 19:33:34 -0800 (PST) (envelope-from william.kuppler@gte.net) From: william.kuppler@gte.net Message-Id: <199812130333.TAA04105@hub.freebsd.org> To: Subject: Family Reunion T Shirts & More Date: Sun, 6 Dec 1998 07:06:57 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Message sent by: Kuppler Graphics, 32 West Main Street, Maple Shade, New Jersey, 08052, 1-800-810-4330. To be removed click reply with remove as the subject. Hello. My name is Bill from Kuppler Graphics. We do screenprinting on T Shirts, Sweatshirts, Jackets, Hats, Tote Bags and more! Do you or someone you know have a Family Reunion coming up? Kuppler Graphics would like to provide you with some great looking T Shirts for your Reunion. Kuppler Graphics can also provide you with custom T's and promotional items such as imprinted magnets, keychains, pens, mugs, hats, etc. for your business or any fundraising activity (church, school, business etc.) You may e mail us at william.kuppler@gte.net if you would like to see the designs that we offer.(That is a dot between William and Kuppler) We are a family owned company with over 15 years of experience located at 32 West Main Street in Maple Shade, New Jersey 08052. All work is done at this location. No middle man. Our prices are great! Please call 1-800-810-4330 to speak with a representative if you have any questions or e mail us at william.kuppler@gte.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 19:59:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06980 for freebsd-current-outgoing; Sat, 12 Dec 1998 19:59:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06975 for ; Sat, 12 Dec 1998 19:59:40 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id TAA15601; Sat, 12 Dec 1998 19:59:37 -0800 (PST) (envelope-from dillon) Date: Sat, 12 Dec 1998 19:59:37 -0800 (PST) From: Matthew Dillon Message-Id: <199812130359.TAA15601@apollo.backplane.com> To: Don Lewis Cc: Peter Edwards , Archie Cobbs , freebsd-current@FreeBSD.ORG Subject: Re: inetd: realloc/free bug References: <199812130332.TAA23232@salsa.gv.tsc.tdk.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :} :I fixed this in BIND 4.x a few years ago using a pipe to synchronize :} :} I'm not sure I follow. close() on a socket descriptor does not block. : :In the case of BIND, close() blocks because SO_LINGER is set. As long :as nothing run from inetd does this, we're probably OK. The reason that :BIND uses SO_LINGER is: Ah. inetd does not use SO_LINGER. I know very few programs that do. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 20:03:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07447 for freebsd-current-outgoing; Sat, 12 Dec 1998 20:03:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA07442 for ; Sat, 12 Dec 1998 20:03:53 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA15675; Sat, 12 Dec 1998 20:03:52 -0800 (PST) (envelope-from dillon) Date: Sat, 12 Dec 1998 20:03:52 -0800 (PST) From: Matthew Dillon Message-Id: <199812130403.UAA15675@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: PR bin/8665 proposed fix (very minor) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a very minor bug report, but I think worth fixing. However, it does slightly change the operation of /bin/mail in the case where the $MAIL environment exists and the 'u' option is also used. I weighed the operation before and after and I think the after operation is more correct. Before $MAIL would always override the mailbox filename even if -u was given to /bin/mail. This is counter to the manual page which basically says that -u basically sets the mailbox file according to the specified user. Afterwords, the -u option overrides $MAIL. The -f option, of course, overrides both. If anybody is rabid about not making the below change, speak up. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) Index: main.c =================================================================== RCS file: /home/ncvs/src/usr.bin/mail/main.c,v retrieving revision 1.5 diff -c -r1.5 main.c *** main.c 1998/01/02 16:43:50 1.5 --- main.c 1998/12/13 03:56:57 *************** *** 63,69 **** --- 63,71 ---- struct name *to, *cc, *bcc, *smopts; char *subject, *replyto; char *ef, *cp; + int have_fopt = 0; char nosrc = 0; + char xname[PATHSIZE]; void hdrstop(); sig_t prevint; void sigchild(); *************** *** 107,115 **** break; case 'u': /* ! * Next argument is person to pretend to be. */ myname = optarg; break; case 'i': /* --- 109,131 ---- break; case 'u': /* ! * Next argument is person to pretend to be. ! * Unfortunately, this seriously confuses the $MAIL ! * environment variable. Since $MAIL is probably ! * wrong, we override it here. If the user really ! * cares he can use -f to specify the actual path. */ myname = optarg; + if (have_fopt == 0) { + snprintf( + xname, + sizeof(xname), + "%s/%s", + _PATH_MAILDIR, + myname + ); + ef = xname; + } break; case 'i': /* *************** *** 142,147 **** --- 158,164 ---- ef = argv[optind++]; else ef = "&"; + have_fopt = 1; break; case 'n': /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 20:25:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA09124 for freebsd-current-outgoing; Sat, 12 Dec 1998 20:25:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA09115 for ; Sat, 12 Dec 1998 20:25:38 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id UAA16020; Sat, 12 Dec 1998 20:25:32 -0800 (PST) (envelope-from dillon) Date: Sat, 12 Dec 1998 20:25:32 -0800 (PST) From: Matthew Dillon Message-Id: <199812130425.UAA16020@apollo.backplane.com> To: freebsd-current@FreeBSD.ORG Subject: PR bin/8637 fgetpos()/fsetpos() limited to 32 bits Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is an interesting one. fgetpos() and fsetpos() utilizes fpos_t holding storage, which is 64 bits. However, both of these routines use ftell() and fseek() internally which truncate offsets to 32 bits. I've also examined the FILE structure which appears to store the offset as an fpos_t, a 64 bit quantity. It should therefore be relatively easy to fix fgetpos() and fsetpos() to operate with > 32 bit quantities (as, I think, they were meant to) without changing any critical structures. It would also be great if we could generate quad versions for fseek and ftell as well (since they'd have to be written anyway to support fgetpos() and fsetpos()). I would put forth fqtell() and fqseek() unless there is some defacto standard already in place. These functions would use the same typing as lseek(). i.e. off_t. -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 21:16:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12787 for freebsd-current-outgoing; Sat, 12 Dec 1998 21:16:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12781 for ; Sat, 12 Dec 1998 21:16:27 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id XAA02461; Sat, 12 Dec 1998 23:16:14 -0600 (CST) Date: Sat, 12 Dec 1998 23:16:13 -0600 From: Dan Nelson To: Matthew Dillon , freebsd-current@FreeBSD.ORG Subject: Re: PR bin/8637 fgetpos()/fsetpos() limited to 32 bits Message-ID: <19981212231613.A2323@emsphone.com> References: <199812130425.UAA16020@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <199812130425.UAA16020@apollo.backplane.com>; from "Matthew Dillon" on Sat Dec 12 20:25:32 GMT 1998 X-OS: FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Dec 12), Matthew Dillon said: > It should therefore be relatively easy to fix fgetpos() and fsetpos() > to operate with > 32 bit quantities (as, I think, they were meant to) > without changing any critical structures. I have been working on this on and off, and am almost done. The patches will add X/OPen standard fseeko() and ftello(), fix fgetpos/fsetpos, add an EOVERFLOW errno, and add the pathconf variable _PC_FILESIZEBITS. The only thing left to do is the pathconf changes for ufs and ext2fs. -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 21:22:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA13389 for freebsd-current-outgoing; Sat, 12 Dec 1998 21:22:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA13384 for ; Sat, 12 Dec 1998 21:22:55 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA17753; Sat, 12 Dec 1998 21:22:51 -0800 (PST) (envelope-from dillon) Date: Sat, 12 Dec 1998 21:22:51 -0800 (PST) From: Matthew Dillon Message-Id: <199812130522.VAA17753@apollo.backplane.com> To: Dan Nelson Cc: freebsd-current@FreeBSD.ORG Subject: Re: PR bin/8637 fgetpos()/fsetpos() limited to 32 bits References: <199812130425.UAA16020@apollo.backplane.com> <19981212231613.A2323@emsphone.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ah, cool. If you get tired of it, just let me know. Else I'm waiting with baited breath :-) -Matt : :In the last episode (Dec 12), Matthew Dillon said: :> It should therefore be relatively easy to fix fgetpos() and fsetpos() :> to operate with > 32 bit quantities (as, I think, they were meant to) :> without changing any critical structures. : :I have been working on this on and off, and am almost done. The :patches will add X/OPen standard fseeko() and ftello(), fix :fgetpos/fsetpos, add an EOVERFLOW errno, and add the pathconf variable :_PC_FILESIZEBITS. The only thing left to do is the pathconf changes :for ufs and ext2fs. : : -Dan Nelson : dnelson@emsphone.com : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Dec 12 22:11:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17641 for freebsd-current-outgoing; Sat, 12 Dec 1998 22:11:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from apollo.backplane.com (apollo.backplane.com [209.157.86.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17622; Sat, 12 Dec 1998 22:11:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id WAA00663; Sat, 12 Dec 1998 22:11:21 -0800 (PST) (envelope-from dillon) Date: Sat, 12 Dec 1998 22:11:21 -0800 (PST) From: Matthew Dillon Message-Id: <199812130611.WAA00663@apollo.backplane.com> To: freebsd-bugs@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: bin/5572 (critial, high priority cron bug never fixed) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... that I submitted all the way back on Jan 26th. It even included a patch. And nobody read it. Nobody fixed it. It's still sitting there in the critical list, untouched. Well, now that I have commit privs I'm damn well going to fix this one! -Matt Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet Communications & God knows what else. (Please include original email in any response) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message