From owner-freebsd-current Sun Dec 27 02:10:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29229 for freebsd-current-outgoing; Sun, 27 Dec 1998 02:10:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from crap.31337.net (node1484.a2000.nl [62.108.20.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29224 for ; Sun, 27 Dec 1998 02:10:51 -0800 (PST) (envelope-from alexlh@funk.org) Received: from p.funk.org (nose.funk.org [194.109.86.229]) by crap.31337.net (8.9.1/8.9.1) with ESMTP id KAA16412 for ; Sun, 27 Dec 1998 10:11:09 GMT (envelope-from alexlh@funk.org) Received: from funk.org (localhost.a2000.nl [127.0.0.1]) by p.funk.org (8.9.1/8.9.1) with ESMTP id WAA72701 for ; Sat, 26 Dec 1998 22:42:25 +0100 (CET) (envelope-from alexlh@funk.org) Message-ID: <36855840.E1286D95@funk.org> Date: Sat, 26 Dec 1998 22:42:24 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: HD LED doesn't go off Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On my recently-installed -current box the hd led doesn't ever seem to go off. I know it doesn't do this under win98 or when it was still (briefly) 3.0-RELEASE. Anyone has a clue what might cause this? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 02:26:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29990 for freebsd-current-outgoing; Sun, 27 Dec 1998 02:26:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from crap.31337.net (node1484.a2000.nl [62.108.20.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA29984 for ; Sun, 27 Dec 1998 02:26:21 -0800 (PST) (envelope-from alexlh@funk.org) Received: from p.funk.org (nose.funk.org [194.109.86.229]) by crap.31337.net (8.9.1/8.9.1) with ESMTP id KAA16477 for ; Sun, 27 Dec 1998 10:26:44 GMT (envelope-from alexlh@funk.org) Received: from funk.org (localhost.a2000.nl [127.0.0.1]) by p.funk.org (8.9.1/8.9.1) with ESMTP id LAA73586 for ; Sun, 27 Dec 1998 11:26:09 +0100 (CET) (envelope-from alexlh@funk.org) Message-ID: <36860B40.352CE7F4@funk.org> Date: Sun, 27 Dec 1998 11:26:08 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: help Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG help To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 02:36:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA00595 for freebsd-current-outgoing; Sun, 27 Dec 1998 02:36: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 CAA00584; Sun, 27 Dec 1998 02:36:12 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id CAA07049; Sun, 27 Dec 1998 02:35:56 -0800 (PST) To: current@FreeBSD.ORG cc: dillon@FreeBSD.ORG Subject: inetd "junk pointer too low" problem. Date: Sun, 27 Dec 1998 02:35:56 -0800 Message-ID: <7045.914754956@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is still not fixed, just FYI... I've seen several reports now from people who still see it with this morning's -current. - 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 27 02:42:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01009 for freebsd-current-outgoing; Sun, 27 Dec 1998 02:42:59 -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 CAA01004 for ; Sun, 27 Dec 1998 02:42:55 -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 VAA23388; Sun, 27 Dec 1998 21:12:07 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id VAA28673; Sun, 27 Dec 1998 21:12:09 +1030 (CST) Message-ID: <19981227211209.L12346@freebie.lemis.com> Date: Sun, 27 Dec 1998 21:12:09 +1030 From: Greg Lehey To: Alex Le Heux , freebsd-current@FreeBSD.ORG Subject: Re: HD LED doesn't go off References: <36855840.E1286D95@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <36855840.E1286D95@funk.org>; from Alex Le Heux on Sat, Dec 26, 1998 at 10:42:24PM +0100 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 On Saturday, 26 December 1998 at 22:42:24 +0100, Alex Le Heux wrote: > Hi, > > On my recently-installed -current box the hd led doesn't ever seem to go > off. > > I know it doesn't do this under win98 or when it was still (briefly) > 3.0-RELEASE. > > Anyone has a clue what might cause this? Does everything else work? If so, let's see the dmesg output. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 02:49:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA01348 for freebsd-current-outgoing; Sun, 27 Dec 1998 02:49:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from crap.31337.net (node1484.a2000.nl [62.108.20.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA01343 for ; Sun, 27 Dec 1998 02:49:05 -0800 (PST) (envelope-from alexlh@funk.org) Received: from p.funk.org (nose.funk.org [194.109.86.229]) by crap.31337.net (8.9.1/8.9.1) with ESMTP id KAA16504; Sun, 27 Dec 1998 10:49:25 GMT (envelope-from alexlh@funk.org) Received: from funk.org (localhost.a2000.nl [127.0.0.1]) by p.funk.org (8.9.1/8.9.1) with ESMTP id LAA73632; Sun, 27 Dec 1998 11:48:50 +0100 (CET) (envelope-from alexlh@funk.org) Message-ID: <36861091.A8AE07D8@funk.org> Date: Sun, 27 Dec 1998 11:48:49 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG Subject: Re: help References: <7081.914755202@zippy.cdrom.com> 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: > > What?! > > > help Arghhhhh That was before I had my coffee.... That was meant to go to majordomo :-) We've had a major meltdown of the local NAP here, plus we had some sendmail problems at home, so I wanted to check whatever came from my subscribe message to freebsd-current and I couldn't quite remember the command... The lesson learned here is never to send email while the coffee's not ready yet. Sorry about that people... Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 02:55:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA02041 for freebsd-current-outgoing; Sun, 27 Dec 1998 02:55:01 -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 CAA02032 for ; Sun, 27 Dec 1998 02:54:59 -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 JAA08636; Sun, 27 Dec 1998 09:44:12 +0100 From: Luigi Rizzo Message-Id: <199812270844.JAA08636@labinfo.iet.unipi.it> Subject: Re: Broken ipfw? To: mike@smith.net.au (Mike Smith) Date: Sun, 27 Dec 1998 09:44:11 +0100 (MET) Cc: seggers@semyam.dinoco.de, erikf@visi.com, freebsd-current@FreeBSD.ORG In-Reply-To: <199812262157.NAA01523@dingo.cdrom.com> from "Mike Smith" at Dec 26, 98 01:57:18 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > After cvsuping on saturday natd has suddenly stopped working with the kernel ... > > > After executing an ipfw rule it responds with: > > > > > > ip_fw_ctl: empty interface name > > > /sbin/ipfw: setsockopt(IP_FW_ADD): Invalid Argument you need to rebuild ipfw as well, because of the dummynet changes. > > Using a kernel module for ipfw? I used it preloaded by /boot/loader > > and with a world (and kernel, of course) from last weekend the kernel > > did see there was a preloaded ELF module but it never got integrated that was my mistake when i first committed dummynet patches, but i think i fixed it on Dec.21-22 cheers luigi > That's quite interesting. > > > See PR kern/9178. If anybody needs more details for this I can easily > > reproduce the problem. I still have a kernel w/o ipfw and could test > > it. > > Please do. It would be very useful to know if the SYSINIT for ipfw is > being called correctly. > > -- > \\ 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 04:53:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA20333 for freebsd-current-outgoing; Sun, 27 Dec 1998 04:53:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA20328 for ; Sun, 27 Dec 1998 04:53:49 -0800 (PST) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id NAA06486; Sun, 27 Dec 1998 13:51:34 +0100 (MET) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id NAA01891; Sun, 27 Dec 1998 13:49:41 +0100 (CET) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199812271249.NAA01891@semyam.dinoco.de> To: Mike Smith cc: "Erik Funkenbusch" , freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Broken ipfw? In-reply-to: Your message of "Sat, 26 Dec 1998 13:57:37 PST." <199812262157.NAA01523@dingo.cdrom.com> Date: Sun, 27 Dec 1998 13:49:40 +0100 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Please do. It would be very useful to know if the SYSINIT for ipfw is > being called correctly. For further investigation I added printf's to ipfw_load and ipfw_mod as their first statement to see if they get called. Nothing from them though the SYSINIT should call module_register_init which should then call ipfw_load. So either the SYSINIT doesn't get recognized or it might go wrong in module_register_init. I haven't investigated that further, yet as I first had to find out who does the SYSINIT and how. I also modified kern_linker.c to give me debug output. Comparing it to what other kernel modules produce this looks normal. Due to the length of the logged data I don't want to append it here. Everyone asking for a copy can get one by private mail. What I noticed was that during startup /etc/rc.firewall tries to determine if there is an ipfw module loaded or something in the kernel it sees nothing, tries to load the module and the result is that it gets reported along the lines "module already loaded, incrementing use counter." So far what I got by now. Stefan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 05:46:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24561 for freebsd-current-outgoing; Sun, 27 Dec 1998 05:46:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from finland.ispro.net.tr (finland.ispro.net.tr [195.174.18.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24549; Sun, 27 Dec 1998 05:46:44 -0800 (PST) (envelope-from yurtesen@ispro.net.tr) Received: from localhost (yurtesen@localhost) by finland.ispro.net.tr (8.9.1/8.9.1) with ESMTP id PAA17201; Sun, 27 Dec 1998 15:46:11 +0200 (EET) (envelope-from yurtesen@ispro.net.tr) Date: Sun, 27 Dec 1998 15:46:11 +0200 (EET) From: Evren Yurtesen To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG, announce@FreeBSD.ORG Subject: Re: Proposed date for creation of 3.0-stable In-Reply-To: <13929.914336174@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 will freebsd 3.0 go out of -current branch and getting into -stable ? if so, how will I get the sources for 3.0 stable with cvsup? +-------------------------------------------------+ | Name : Evren Yurtesen - yurtesen@ispro.net.tr | | S-mail: Talikkokatu 6B 26, 20540 Turku/FINLAND | | Home:+358-2-2379095 Work:+358-40-5185215 | +-------------------------------------------------+ On Tue, 22 Dec 1998, Jordan K. Hubbard wrote: > Since everyone is going to be off at Christmas or New Years parties > and such for the next 10 days or so, it would be impractical to > schedule the branch date any earlier than mid-January and so that is > what I'm going to do. Unless circumstances dictate otherwise, 3.0 > will depart the -current branch on January 15th, 1999 (sometime in the > evening, west coast time). The 3.0.1 release will follow 30 days > later, on Feb 15th. 1999. > > So, all you developers, please consider this your ADVANCE NOTICE of > these events and don't come crying to me on January 14th about how you > weren't given enough time to get your changes into 3.0. :-) > > Thanks! > > - Jordan > > This is the moderated mailing list freebsd-announce. > The list contains announcements of new FreeBSD capabilities, > important events and project milestones. > See also the FreeBSD Web pages at http://www.freebsd.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-announce" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 06:11:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA26275 for freebsd-current-outgoing; Sun, 27 Dec 1998 06:11:08 -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 GAA26270 for ; Sun, 27 Dec 1998 06:11:01 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.198]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA4F51; Sun, 27 Dec 1998 15:10:44 +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: Sun, 27 Dec 1998 15:17:26 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Evren Yurtesen Subject: Re: Proposed date for creation of 3.0-stable Cc: current@FreeBSD.ORG, "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27-Dec-98 Evren Yurtesen wrote: > will freebsd 3.0 go out of -current branch and getting into -stable ? > if so, how will I get the sources for 3.0 stable with cvsup? As Jordan said: CURRENT will stay CURRENT, but the 3.0.x branch will be split of to -stable with the start of 3.0.1 as a real release. Most likely with new tags, which will be announced at that time I guess. Correct me if wrong Jordan... --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... 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 Sun Dec 27 07:04:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA00920 for freebsd-current-outgoing; Sun, 27 Dec 1998 07:04:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA00915 for ; Sun, 27 Dec 1998 07:04:26 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA02272; Sun, 27 Dec 1998 10:04:04 -0500 (EST) Date: Sun, 27 Dec 1998 10:04:04 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mike Smith cc: current@FreeBSD.ORG Subject: Re: K6-2 (3?) CPU_WT_ALLOC In-Reply-To: <199812262155.NAA01495@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 Sat, 26 Dec 1998, Mike Smith wrote: > > Can anyone else using this patch speak up about their experiences? > It'd be good to see it committed, but I have no hardware on which to > test it... In a dmesg, if this line looks as such: Origin = "AuthenticAMD" Id = 0x58c Stepping=12 where Id = 0x58X, this is a K6-2 model 8/[F:8]+, or on Id = 0x59X a K6-3 (just guessing here, but I think it'll be right :) in which case enable_K6_2_wt_alloc will be called rather than enable_K6_wt_alloc. So for K6-2 machines, the (cpu_id & 0xff0) > 0x570 will be the enabling variable, and the new wt_alloc routine will take effect; if anyone wants to test this out (actually, to use it permanently really!) try it on a K6-2 described as above. If anyone does need to check my work, look for doc 21326e on www.amd.com, "Implementation of Write Allocation in the K86 Processors", where the WHCR differences between models are fully defined. > -- > \\ 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 Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 07:18:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02081 for freebsd-current-outgoing; Sun, 27 Dec 1998 07:18:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02075 for ; Sun, 27 Dec 1998 07:18:08 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id KAA02649 for ; Sun, 27 Dec 1998 10:17:55 -0500 (EST) Date: Sun, 27 Dec 1998 10:17:54 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: "ICMP_BANDLIM" 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 Does anyone have an aversion to options "ICMP_BANDLIM" going into GENERIC? I think it's very justifiable, and doesn't bloat the kernel unnecessarily (also, Solaris and Linux, that I know of so far, also do this, so it's a pretty standard thing). And how about using an option "ICMP_BANDLIM_SILENT" as well? Sometimes you don't really want to see your message buffer filling up with ICMP_BANDLIM messages, and option "ICMP_BANDLIM_SILENT" would probably go into GENERIC too. If everyone thinks this is a good idea, I'll make the patches to src/sys/netinet/ip_input.c src/sys/{i386,alpha}/conf/GENERIC src/sys/i386/conf/options.i386 src/sys/alpha/conf/options.alpha and maybe PC98? PC98 should probably be left alone... Comments? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 07:22:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02538 for freebsd-current-outgoing; Sun, 27 Dec 1998 07:22:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02531 for ; Sun, 27 Dec 1998 07:22:21 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id QAA09428 for freebsd-current@freebsd.org; Sun, 27 Dec 1998 16:22:05 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id PAA17569; Sun, 27 Dec 1998 15:56:59 +0100 (MET) (envelope-from j) Date: Sun, 27 Dec 1998 15:56:59 +0100 (MET) Message-Id: <199812271456.PAA17569@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <008601be3989$48cf4ac0$4d18b9c2@oma.linet.it> <30164.914431322@zippy.cdrom.com> In-Reply-To: <30164.914431322@zippy.cdrom.com> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: PPTP and FreeBSD X-Original-Newsgroups: local.freebsd.current To: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: >> There's any PPTP 'driver' for FreeBSD is it comaptible with the M$ one? > > There is not, I'm afraid. I don't see the original mail here, nor do i know who wrote it. In any case: M$ PPTP is a sad joke, and nothing else. Nobody who's concerned the slightest about security (and after all, improving security is the designated purpose of PPTP) should ever use the M$ implementation. There is a cryptoanalysis of M$ PPTP available on the Web, and the outcome was that they made a bunch of `cryptographic kindergarten errors' (original quote of the analysis) which even a simple code review of someone knowledgable should have made apparent. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 07:22:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA02565 for freebsd-current-outgoing; Sun, 27 Dec 1998 07:22:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA02552 for ; Sun, 27 Dec 1998 07:22:25 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id QAA09429 for freebsd-current@freebsd.org; Sun, 27 Dec 1998 16:22:09 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id QAA17580; Sun, 27 Dec 1998 16:02:22 +0100 (MET) (envelope-from j) Date: Sun, 27 Dec 1998 16:02:22 +0100 (MET) Message-Id: <199812271502.QAA17580@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <13952.37524.42627.187779@avalon.east> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: un-hexdump? X-Original-Newsgroups: local.freebsd.current To: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tony Kimball wrote: > If I am not mistaken on this point, and it is deemed > desirable, I will provide a basic utility of this sort. This could be easily done with a little perl script, but i doubt it's of that much general interest. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 07:53:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05022 for freebsd-current-outgoing; Sun, 27 Dec 1998 07:53: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 HAA05008 for ; Sun, 27 Dec 1998 07:53:05 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id PAA02315; Sun, 27 Dec 1998 15:51:49 GMT Date: Sun, 27 Dec 1998 15:51:42 +0000 (GMT) From: Doug Rabson To: Stefan Eggers cc: Mike Smith , Erik Funkenbusch , freebsd-current@FreeBSD.ORG Subject: Re: Broken ipfw? In-Reply-To: <199812271249.NAA01891@semyam.dinoco.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Dec 1998, Stefan Eggers wrote: > > Please do. It would be very useful to know if the SYSINIT for ipfw is > > being called correctly. > > For further investigation I added printf's to ipfw_load and ipfw_mod as > their first statement to see if they get called. Nothing from them > though the SYSINIT should call module_register_init which should then > call ipfw_load. So either the SYSINIT doesn't get recognized or it > might go wrong in module_register_init. I haven't investigated that > further, yet as I first had to find out who does the SYSINIT and how. > > I also modified kern_linker.c to give me debug output. Comparing it > to what other kernel modules produce this looks normal. Due to the > length of the logged data I don't want to append it here. Everyone > asking for a copy can get one by private mail. > > What I noticed was that during startup /etc/rc.firewall tries to > determine if there is an ipfw module loaded or something in the kernel > it sees nothing, tries to load the module and the result is that it > gets reported along the lines "module already loaded, incrementing use > counter." > > So far what I got by now. > > Stefan. Is the module being correctly linked with setdef0.o and setdef1.c to define the linker sets? It should be if its built using the standard bsd.kmod.mk but its worth checking. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 08:02:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA05799 for freebsd-current-outgoing; Sun, 27 Dec 1998 08:02:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from crap.31337.net (node1484.a2000.nl [62.108.20.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA05757 for ; Sun, 27 Dec 1998 08:01:59 -0800 (PST) (envelope-from alexlh@funk.org) Received: from p.funk.org ([194.109.86.229]) by crap.31337.net (8.9.1/8.9.1) with ESMTP id QAA16997 for ; Sun, 27 Dec 1998 16:02:32 GMT (envelope-from alexlh@funk.org) Received: from funk.org (localhost.a2000.nl [127.0.0.1]) by p.funk.org (8.9.1/8.9.1) with ESMTP id RAA01307 for ; Sun, 27 Dec 1998 17:01:42 +0100 (CET) (envelope-from alexlh@funk.org) Message-ID: <368659E5.71D710B7@funk.org> Date: Sun, 27 Dec 1998 17:01:41 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: PPTP and FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [snip] > > There is a cryptoanalysis of M$ PPTP available on the Web, and the > outcome was that they made a bunch of `cryptographic kindergarten > errors' (original quote of the analysis) which even a simple code > review of someone knowledgable should have made apparent. > You can find it at http://www.counterpane.com/pptp.html AFAIK there were some PPTP hotfixes from Microsoft after this, so it might not apply to the current state of MS PPTP. Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 08:54:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10744 for freebsd-current-outgoing; Sun, 27 Dec 1998 08:54:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10737; Sun, 27 Dec 1998 08:54:31 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA05206; Sun, 27 Dec 1998 11:54:18 -0500 (EST) Date: Sun, 27 Dec 1998 11:54:18 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG cc: sos@FreeBSD.ORG, phk@FreeBSD.ORG Subject: wanton Atticizing is bad 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 In the cleanups today, things were broken and irreplacable things deleted. For instance, why was softmodem support deleted, ft support, and the if_eg 3c505 driver? If there's no replacement, unless it's an old SCSI driver, why should it be deleted? Pcvt was deleted, but I'm willing to bet some people use it, even though the syscons driver is going to be rewritten soon. When wcd was removed, atapi.c broke, so the old WCD cruft should be removed and the line #include "wcd.h" should as well. This is a good replacement though, as I've had nothing but good experience with acd on my ATAPI CD-ROM drives, and wcd is deprecated. However, sound is not deprecated. Luigi's snd requires the header ulaw.h from the old VoxWare driver, but this can be easily moved over. The more important things are: lack of probing printf, that all other hardware drivers have, however the sndstat support which has the correct kernel printfs is already implemented in sound.c:1309 (i.e. "pcm0: at 0x220 irq 5 dma 1:6") certain drivers with no replacement in VoxWare: MIDI and FM are both unimplemented. I cannot now use OPL/3 like I could before, nor the MIDI port So for at least the VoxWare drivers, please reverse the removal. They are NOT deprecated. As for the others, were there good reasons to remove them? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 09:21:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA13107 for freebsd-current-outgoing; Sun, 27 Dec 1998 09:21: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 JAA13097; Sun, 27 Dec 1998 09:21:25 -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 SAA68201; Sun, 27 Dec 1998 18:20:00 +0100 (CET) To: Brian Feldman cc: current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Sun, 27 Dec 1998 11:54:18 EST." Date: Sun, 27 Dec 1998 18:20:00 +0100 Message-ID: <68199.914779200@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The cleanups have been discussed in -core. -committers is a notorious unproductive and flame-prone place to discuss code removal. The criteria used is one along the lines of "Would we import this code today if it hadn't been in the tree?" with a healthy fudge factor. Some examples of this process in action: if_eg: The driver never worked very well (I know, I have three cards for it!) and nobody cares enough to fix it. softmodem: It could never run faster then 14.4, the company went broke and I ever only knew of one other user. pcvt: We would never import another console today, just to gain VT* emulation, we would tell people to develop it for syscons, something which has until now not happened, primarily because of the existence of pcvt in the tree. and so on... And >>>ONLY<<< if somebody feels strongly enough about some of this, to go and actively maintain it, is reintroduction open to discussion And don't forget: the code can be found in the Attic. Further hitlist candidates are: X-ten IPFILTER alog gp asc gsc mse spigot spkr lpt (ppbus will be standard) ctx (Suggestions welcome!) If you consider yourself maintainer of one of these, and therefore think that the driver should be spared, please send me email. In the future we >may< require that sufficent hardware is available at the FreeBSD Test Labs (contact: msmith@freebsd.org) to test the vital life signs of a driver before it gets imported into FreeBSD. Mandatory historical perspective section: Find out why the ship Wasa was built such that it sank before it even made it out of the harbour. If we keep adding to FreeBSD and never weed out, it will sink under its own weight. Poul-Henning In message , Brian Feldman writes: > In the cleanups today, things were broken and irreplacable things deleted. -- 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 27 09:43:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA15107 for freebsd-current-outgoing; Sun, 27 Dec 1998 09:43:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-sfx201--110.sirius.net [205.134.235.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA15102 for ; Sun, 27 Dec 1998 09:43:44 -0800 (PST) (envelope-from parag@cgt.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.1/8.8.8) with ESMTP id JAA80834; Sun, 27 Dec 1998 09:43:22 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199812271743.JAA80834@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: garman@earthling.net cc: current@FreeBSD.ORG Subject: Re: PR filed on dying daemons bug In-Reply-To: Message from garman@earthling.net of "Sun, 27 Dec 1998 01:10:03 EST." <199812270610.WAA15223@hub.freebsd.org> X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Dec 1998 09:43:21 -0800 From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I upgraded from an Oct23 kernel to Dec18 kernel, I couldn't get "make -j8 buildworld" to run to completion. Things were just sort of dying without much of a clue. I finally noticed that dmesg was reporting file: table is full errors but oddly they were not being displayed in the main xconsole window (which was correctly displaying other console messages). Anyway, I bumped up kern.maxfiles and kern.maxfilesperproc and things seem fine now. (I also bumped maxusers in my kernel config file from 10 to 32 for future kernel builds.) Perhaps the current dying daemons problem is simply that the kernel is running out of file descriptors? Perhaps the default calculations for these changed recently? -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 10:01:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17335 for freebsd-current-outgoing; Sun, 27 Dec 1998 10:01:49 -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 KAA17325 for ; Sun, 27 Dec 1998 10:01:45 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id UAA00405; Sun, 27 Dec 1998 20:01:25 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id UAA38580; Sun, 27 Dec 1998 20:01:22 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812271801.UAA38580@greenpeace.grondar.za> To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: Your message of " Sun, 27 Dec 1998 18:20:00 +0100." <68199.914779200@critter.freebsd.dk> References: <68199.914779200@critter.freebsd.dk> Date: Sun, 27 Dec 1998 20:01:20 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > -committers is a notorious unproductive and flame-prone place to > discuss code removal. 100% agreement. > The criteria used is one along the lines of "Would we import this > code today if it hadn't been in the tree?" with a healthy fudge > factor. This is a _really_ clear test. I'll use this from now on. We now need (tr: I would like) some kind of "ports-like" mechanism for kernel bits, such as example kld so devices can be written by the general population _and_maintained_ as ports code (kinda like the commercial sound driver). 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 27 10:09:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18219 for freebsd-current-outgoing; Sun, 27 Dec 1998 10:09:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18210; Sun, 27 Dec 1998 10:08:55 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id NAA08158; Sun, 27 Dec 1998 13:03:37 -0500 (EST) Date: Sun, 27 Dec 1998 13:03:37 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Poul-Henning Kamp cc: current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: <68199.914779200@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Dec 1998, Poul-Henning Kamp wrote: > And >>>ONLY<<< if somebody feels strongly enough about some of > this, to go and actively maintain it, is reintroduction open to > discussion Even with timidity, there should DEFINITELY be an OPL/3 driver. I would like to take over the VoxWare driver. > > And don't forget: the code can be found in the Attic. > > Further hitlist candidates are: > > X-ten > IPFILTER Wasn't this _just_recently_ committed? Why commit it in the first place if noone really wants it? Personally, I use IPFW. > alog > gp > asc > gsc > mse IIRC I've seen people who used this. > spigot > spkr Good riddance. > lpt (ppbus will be standard) Good, and (you should) make the change in GENERIC. Ppbus works exceptionally well, lpt is really deprecated. > ctx > (Suggestions welcome!) What was the reasoning behind ft though? Anyway, I think that taking suggestions for driver removal should be done on a MUCH larger basis, not just asking -core and -current list reasers. We should try to assess the hardware and software usage of a WIDE range, not just the smaller amount who read the mailing lists. Perhaps some sort of poll on www.freebsd.org for a few months voting for what drivers to keep? For now, I think that sound and probably ft should be back in, at least for 3.0.1. But we need more opinions of course :) > > If you consider yourself maintainer of one of these, and therefore > think that the driver should be spared, please send me email. > > In the future we >may< require that sufficent hardware is available > at the FreeBSD Test Labs (contact: msmith@freebsd.org) to test the > vital life signs of a driver before it gets imported into FreeBSD. > > Mandatory historical perspective section: Find out why the ship > Wasa was built such that it sank before it even made it out of the > harbour. If we keep adding to FreeBSD and never weed out, it will > sink under its own weight. > > Poul-Henning > > > In message , Brian > Feldman writes: > > In the cleanups today, things were broken and irreplacable things deleted. > > -- > 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 Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 10:12:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18784 for freebsd-current-outgoing; Sun, 27 Dec 1998 10:12:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18779 for ; Sun, 27 Dec 1998 10:12:39 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id NAA08237; Sun, 27 Dec 1998 13:07:08 -0500 (EST) Date: Sun, 27 Dec 1998 13:07:07 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mark Murray cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: <199812271801.UAA38580@greenpeace.grondar.za> 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, 27 Dec 1998, Mark Murray wrote: > Poul-Henning Kamp wrote: > > -committers is a notorious unproductive and flame-prone place to > > discuss code removal. > > 100% agreement. > > > The criteria used is one along the lines of "Would we import this > > code today if it hadn't been in the tree?" with a healthy fudge > > factor. > > This is a _really_ clear test. I'll use this from now on. > > We now need (tr: I would like) some kind of "ports-like" mechanism > for kernel bits, such as example kld so devices can be written by > the general population _and_maintained_ as ports code (kinda like Agree, MORE than wholeheartedly! I was thinking of proposing converting these older drivers to modules in ports, with the associated utilities, but I thought it would be too risque to propose. It probably is, seeing as noone wants to maintain these drivers let alone modularize them. The ports idea brings a question though: what do we do about device majors? > the commercial sound driver). OSS is horrible. > > M > -- > Mark Murray > Join the anti-SPAM movement: http://www.cauce.org Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 10:18:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19178 for freebsd-current-outgoing; Sun, 27 Dec 1998 10:18:11 -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 KAA19173 for ; Sun, 27 Dec 1998 10:18:07 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id UAA14514; Sun, 27 Dec 1998 20:17:48 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id UAA38656; Sun, 27 Dec 1998 20:17:44 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812271817.UAA38656@greenpeace.grondar.za> To: Brian Feldman cc: current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: Your message of " Sun, 27 Dec 1998 13:07:07 EST." References: Date: Sun, 27 Dec 1998 20:17:39 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote: > > We now need (tr: I would like) some kind of "ports-like" mechanism > > for kernel bits, such as example kld so devices can be written by > > the general population _and_maintained_ as ports code (kinda like > > Agree, MORE than wholeheartedly! I was thinking of proposing > converting these older drivers to modules in ports, with the > associated utilities, but I thought it would be too risque to > propose. It probably is, seeing as noone wants to maintain these > drivers let alone modularize them. The ports idea brings a question > though: what do we do about device majors? I suppose DEVFS will really fix that problem; if the lkd has some mechanism to request a major number out of a pool set aside for the purpose, and DEVFS could make it visible. > > the commercial sound driver). > > OSS is horrible. Sure, but it is separately maintained - that is the point. We do not have or need its code in the kernel, it is an LKM written by "outsiders" IIRC. 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 27 10:21:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19587 for freebsd-current-outgoing; Sun, 27 Dec 1998 10:21:50 -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 KAA19571 for ; Sun, 27 Dec 1998 10:21:37 -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 TAA68576; Sun, 27 Dec 1998 19:19:59 +0100 (CET) To: Mark Murray cc: current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Sun, 27 Dec 1998 20:01:20 +0200." <199812271801.UAA38580@greenpeace.grondar.za> Date: Sun, 27 Dec 1998 19:19:58 +0100 Message-ID: <68574.914782798@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >We now need (tr: I would like) some kind of "ports-like" mechanism >for kernel bits, such as example kld so devices can be written by >the general population _and_maintained_ as ports code (kinda like >the commercial sound driver). The major bit of this would be either the hopefully soon mature kld, or alternatively a hack to config so that you could add sys/i386/conf/files.d/files.foo sys/i386/conf/options.d/options.foo for some stuff named "foo", so that it would not involve editing system files. I agree that it is needed, and has been for a long time. Somebody working out something would be a great development. -- 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 27 10:26:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19886 for freebsd-current-outgoing; Sun, 27 Dec 1998 10:26:26 -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 KAA19876; Sun, 27 Dec 1998 10:26:15 -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 TAA68608; Sun, 27 Dec 1998 19:24:46 +0100 (CET) To: Brian Feldman cc: current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Sun, 27 Dec 1998 13:03:37 EST." Date: Sun, 27 Dec 1998 19:24:46 +0100 Message-ID: <68606.914783086@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Brian Feldman writes: >On Sun, 27 Dec 1998, Poul-Henning Kamp wrote: >> And >>>ONLY<<< if somebody feels strongly enough about some of >> this, to go and actively maintain it, is reintroduction open to >> discussion > >Even with timidity, there should DEFINITELY be an OPL/3 driver. I would like to >take over the VoxWare driver. Then go for it! For sound, try to work with Luigi so that we only have one sound system. >> IPFILTER > >Wasn't this _just_recently_ committed? Why commit it in the first place if >noone really wants it? Personally, I use IPFW. Yeah, the jury is still out on this one... Any users out there ? >> mse > >IIRC I've seen people who used this. well, lets hear it from them then... >> lpt (ppbus will be standard) > >Good, and (you should) make the change in GENERIC. Ppbus works exceptionally >well, lpt is really deprecated. There is some outstanding hacks missing for PLIP, but otherwise yes. >What was the reasoning behind ft though? It's badly implemented and many capable persons have failed to find a way to solve the rather serious problems it suffers from. ATAPI tapes seems to be the way of the future for cheap tapes. Any scheme asking users permission for removal will always prevent even the slightest weeding out. The criteria needs to be on maintenance status, since money cannot be used as a gauge. -- 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 27 10:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA19993 for freebsd-current-outgoing; Sun, 27 Dec 1998 10:28:12 -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 KAA19987 for ; Sun, 27 Dec 1998 10:28:07 -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 TAA68623; Sun, 27 Dec 1998 19:25:44 +0100 (CET) To: Brian Feldman cc: Mark Murray , current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Sun, 27 Dec 1998 13:07:07 EST." Date: Sun, 27 Dec 1998 19:25:44 +0100 Message-ID: <68621.914783144@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> We now need (tr: I would like) some kind of "ports-like" mechanism >> for kernel bits, such as example kld so devices can be written by >> the general population _and_maintained_ as ports code (kinda like > >Agree, MORE than wholeheartedly! I was thinking of proposing converting these >older drivers to modules in ports, with the associated utilities, but I thought >it would be too risque to propose. It probably is, seeing as noone wants to >maintain these drivers let alone modularize them. The ports idea brings a >question though: what do we do about device majors? Make DEVFS standard. -- 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 27 11:22:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA24837 for freebsd-current-outgoing; Sun, 27 Dec 1998 11:22:39 -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 LAA24832 for ; Sun, 27 Dec 1998 11:22:37 -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 LAA44858; Sun, 27 Dec 1998 11:21:24 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812271921.LAA44858@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray cc: Brian Feldman , current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Sun, 27 Dec 1998 20:17:39 +0200." <199812271817.UAA38656@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Dec 1998 11:21:24 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Sure, but it is separately maintained - that is the point. We do not have > or need its code in the kernel, it is an LKM written by "outsiders" IIRC. An a kld is a perfect tool for some to write kernel drivers or modules and not have to deal with -core . 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 27 11:27:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25393 for freebsd-current-outgoing; Sun, 27 Dec 1998 11:27:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp1.andrew.cmu.edu (SMTP1.ANDREW.CMU.EDU [128.2.10.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25388 for ; Sun, 27 Dec 1998 11:27:06 -0800 (PST) (envelope-from mwhite@cmu.edu) Received: from FRAUGHT.NET.CMU.EDU (FRAUGHT.NET.CMU.EDU [128.2.6.66]) by smtp1.andrew.cmu.edu (8.8.5/8.8.2) with ESMTP id OAA02382 for ; Sun, 27 Dec 1998 14:26:48 -0500 (EST) Date: Sun, 27 Dec 1998 14:26:49 -0500 From: Matt White To: freebsd-current@FreeBSD.ORG Subject: Re: PPTP and FreeBSD Message-ID: <4235743047.914768809@FRAUGHT.NET.CMU.EDU> In-Reply-To: <199812271456.PAA17569@uriah.heep.sax.de> 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 --On Sunday, December 27, 1998, 3:56 PM +0100 J Wunsch wrote: > In any case: M$ PPTP is a sad joke, and nothing else. Nobody who's > concerned the slightest about security (and after all, improving > security is the designated purpose of PPTP) should ever use the M$ > implementation. Could this have anything to do with the fact that the Win9x version of the PPTP client doesn't even support encryption of the data stream? Regardless, we would like a PPTP server running under FreeBSD/Linux/Solaris at this site because we subscribe to a number of services that do security by IP address. Our desire would be more to be able to assign IPs from our address space to roaming users. Since we don't consider our local wire to be secure in any way shape or form, we encrypt all sensitive traffic in the application. IMO, this is the only sane way to do things. -Matt ---------- Matt White Network Systems Designer Canegie Mellon Computing Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 11:36:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA26268 for freebsd-current-outgoing; Sun, 27 Dec 1998 11:36:34 -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 LAA26263 for ; Sun, 27 Dec 1998 11:36:31 -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 UAA68861; Sun, 27 Dec 1998 20:35:33 +0100 (CET) To: Matt White cc: freebsd-current@FreeBSD.ORG Subject: Re: PPTP and FreeBSD In-reply-to: Your message of "Sun, 27 Dec 1998 14:26:49 EST." <4235743047.914768809@FRAUGHT.NET.CMU.EDU> Date: Sun, 27 Dec 1998 20:35:33 +0100 Message-ID: <68859.914787333@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Since we don't consider our local wire to be secure in any way shape or >form, we encrypt all sensitive traffic in the application. IMO, this is >the only sane way to do things. We used to have a war-chant we used against the OSI people, it went something like: "Anything but end-to-end ACKs is a waste of time" I pressume that it would be equally valid if you did a: s/ACKs/encryption/ -- 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 27 12:17: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, 27 Dec 1998 12:17:20 -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 MAA29566 for ; Sun, 27 Dec 1998 12:17:18 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA51694; Sun, 27 Dec 1998 12:16:55 -0800 (PST) (envelope-from dillon) Date: Sun, 27 Dec 1998 12:16:55 -0800 (PST) From: Matthew Dillon Message-Id: <199812272016.MAA51694@apollo.backplane.com> To: Brian Feldman Cc: current@FreeBSD.ORG Subject: Re: "ICMP_BANDLIM" References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Does anyone have an aversion to options "ICMP_BANDLIM" going into GENERIC? I :think it's very justifiable, and doesn't bloat the kernel unnecessarily (also, :Solaris and Linux, that I know of so far, also do this, so it's a pretty :standard thing). And how about using an option "ICMP_BANDLIM_SILENT" as well? :Sometimes you don't really want to see your message buffer filling up with :ICMP_BANDLIM messages, and option "ICMP_BANDLIM_SILENT" would probably go into :GENERIC too. If everyone thinks this is a good idea, I'll make the patches to :src/sys/netinet/ip_input.c src/sys/{i386,alpha}/conf/GENERIC :src/sys/i386/conf/options.i386 src/sys/alpha/conf/options.alpha and maybe PC98? :PC98 should probably be left alone... : :Comments? I was planning on waiting a release but it does appear to be solid, I think we can enable it permanently. The bandlim error messages are rate limited, it should not create a burden on the log files, but I suppose a silent option could be added - no skin off the code's nose :-) The only problem is that I do not have time to do it right now and my code tree is sitting on the floor in pieces while I work on the swap system. If a committer wants to commit the appropriate changes please feel free! -Matt : Brian Feldman _ __ ___ ___ ___ : green@unixhelp.org _ __ ___ | _ ) __| \ : http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | : FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ : : :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 Sun Dec 27 12:19:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29878 for freebsd-current-outgoing; Sun, 27 Dec 1998 12:19:52 -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 MAA29873 for ; Sun, 27 Dec 1998 12:19:51 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA51775; Sun, 27 Dec 1998 12:19:33 -0800 (PST) (envelope-from dillon) Date: Sun, 27 Dec 1998 12:19:33 -0800 (PST) From: Matthew Dillon Message-Id: <199812272019.MAA51775@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: inetd "junk pointer too low" problem. References: <7045.914754956@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Grrrr. -Matt : :Is still not fixed, just FYI... I've seen several reports now from :people who still see it with this morning's -current. : :- Jordan : :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 Sun Dec 27 12:33:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00860 for freebsd-current-outgoing; Sun, 27 Dec 1998 12:33:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00852; Sun, 27 Dec 1998 12:33:13 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA025439359; Sun, 27 Dec 1998 09:35:59 -0500 Date: Sun, 27 Dec 1998 09:35:59 -0500 (EST) From: Bill Fumerola To: Poul-Henning Kamp Cc: Brian Feldman , current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: <68199.914779200@critter.freebsd.dk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Dec 1998, Poul-Henning Kamp wrote: > Further hitlist candidates are: > IPFILTER This is _not_ my volunteering to maintain it, but a lot of people prefer ipfilter to ipfw. Portability seems to be a high factor of its use. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 27 12:51:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02214 for freebsd-current-outgoing; Sun, 27 Dec 1998 12:51:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm510-01.dialip.mich.net [131.118.249.223]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA02203 for ; Sun, 27 Dec 1998 12:51:17 -0800 (PST) (envelope-from garman@earthling.net) From: garman@earthling.net Message-Id: <199812272051.MAA02203@hub.freebsd.org> Received: (qmail 40302 invoked from smtpd); 27 Dec 1998 20:50:57 -0000 Received: from localhost.garman.net (HELO earthling.net) (127.0.0.1) by localhost.garman.net with SMTP; 27 Dec 1998 20:50:57 -0000 Date: Sun, 27 Dec 1998 15:50:56 -0500 (EST) Reply-To: garman@earthling.net Subject: Re: PR filed on dying daemons bug To: parag@cgt.com cc: current@FreeBSD.ORG In-Reply-To: <199812271743.JAA80834@pinhead.parag.codegen.com> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 27 Dec, Parag Patel wrote: > > Perhaps the current dying daemons problem is simply that the kernel is > running out of file descriptors? Perhaps the default calculations for > these changed recently? > alas, this does not seem to be the problem. I have more than enough file descriptors left: bash$ pstat -T 225/1960 files 52M/147M swap space enjoy -- Jason Garman http://fs.sso.sytexinc.com/~jgarman/ Student, University of Maryland garman@earthling.net Words of Wisdom from the Simpsons: Whois: JAG145 "'The President did it' is not an excuse" -- Bart Simpson's punishment To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 13:16:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04320 for freebsd-current-outgoing; Sun, 27 Dec 1998 13:16:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.calweb.com (mail.calweb.com [208.131.56.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04311 for ; Sun, 27 Dec 1998 13:16:53 -0800 (PST) (envelope-from jkf@calweb.com) Received: by mail.calweb.com (8.8.6/8.8.6) with SMTP id NAA00348 for ; Sun, 27 Dec 1998 13:16:37 -0800 (PST) X-SMTP: helo web2.calweb.com from jkf@calweb.com server jkf@web2.calweb.com ip 208.131.56.52 Date: Sun, 27 Dec 1998 13:16:37 -0800 (PST) From: "Jason K. Fritcher" To: current@FreeBSD.ORG Subject: pidentd 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 Hello. I have run into an interesting problem with the pidentd port. When it runs from inetd in nowait mode, and someone connects to port 113, identd starts, and then immediately dies and dumps core. When looking at a stack trace on the core file, this is what I get. Script started on Sat Dec 26 22:17:50 1998 [root@monitor:/]# gdb /usr/local/sbin/identd.so /identd.so.core GDB is free software and you are welcome to distribute copies of it under certain conditions; type "show copying" to see the conditions. There is absolutely no warranty for GDB; type "show warranty" for details. GDB 4.16 (i386-unknown-freebsd), Copyright 1996 Free Software Foundation, Inc... Core was generated by `identd.so'. Program terminated with signal 11, Segmentation fault. #0 0x4000b5a5 in ?? () (gdb) bt #0 0x4000b5a5 in ?? () #1 0x4000f938 in ?? () #2 0x40004534 in ?? () #3 0x40002160 in ?? () (gdb) quit [root@monitor:/]# exit Script done on Sat Dec 26 22:18:13 1998 Don't ask about the .so, I'll explain later. I can not find a way to get gdb to show what functions those are. I have compiled a debug copy of the libc shared library and had it load that upon startup instead of the non-debug copy but it still will not show the function names. Any pointers of how I can figure out what library and what functions those are? I also went so far as to compile a statically linked version of identd and it works almost perfectly. By almost I mean I still can't run identd in wait mode from inetd. This led me to play around with the dynamically linked version. I can get it to work when run in daemon mode, and I can also get it to work when I run it in debug mode. But it just will not work when run from inetd. My main concern here is figuring out how to determine what functions the pointers in the core dump point to. Am I missing a command to read in the symbols for the libraries, or is there something else? I included the part about the static file just so everyone would know what I have done so far. Any insight to this problem is much appriciated! -------------------------------------------------------------------------- Jason K. Fritcher System Administrator jkf@calweb.com CalWeb Internet Services http://www.calweb.com/ 916-641-9320 -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 13:19:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA04504 for freebsd-current-outgoing; Sun, 27 Dec 1998 13:19:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA04499 for ; Sun, 27 Dec 1998 13:19:58 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from o2.cs.rpi.edu (root@o2.cs.rpi.edu [128.113.96.156]) by cs.rpi.edu (8.9.1/8.9.1) with ESMTP id QAA04372 for ; Sun, 27 Dec 1998 16:19:41 -0500 (EST) From: "David E. Cross" Received: (from crossd@localhost) by o2.cs.rpi.edu (8.9.1a/8.9.1) id QAA13600 for freebsd-current@FreeBSD.ORG; Sun, 27 Dec 1998 16:19:39 -0500 (EST) Date: Sun, 27 Dec 1998 16:19:39 -0500 (EST) Message-Id: <199812272119.QAA13600@o2.cs.rpi.edu> To: freebsd-current@FreeBSD.ORG Subject: Re: PPTP and FreeBSD Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Regardless, we would like a PPTP server running under FreeBSD/Linux/Solaris > at this site because we subscribe to a number of services that do security > by IP address. Our desire would be more to be able to assign IPs from our > address space to roaming users. I had looked into this at the past, and read the relavent RFCs and MS documentation on it. It is a bad joke, all the way arround. First it uses a modified version of the GRE protocol (that is why I asked about GRE support in the kernel way back when), as an encapsulation around the PPP packets. It also must have a TCP connection between the client and the server to act as a controll connection. If that control connection is lost for whatever reason , the tunel is closed. Oh yes, one last thing, the GRE portion of the tunel, where the data actually goes, has an ack/nak, sliding window and retransmit system (again, outlined in the MS documentation). While I think this would be a good thing to have, just to be compatible, and ideally as a part of a larger 'iptunel' packagel; it is *alot* of work. -- David Cross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 13:37:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05846 for freebsd-current-outgoing; Sun, 27 Dec 1998 13:37:34 -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 NAA05841; Sun, 27 Dec 1998 13:37:23 -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 QAA01039; Sun, 27 Dec 1998 16:33:20 -0500 (EST) (envelope-from lee) Message-ID: <19981227163320.A998@tidalwave.net> Date: Sun, 27 Dec 1998 16:33:20 -0500 From: Lee Cremeans To: Poul-Henning Kamp , Brian Feldman Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: wanton Atticizing is bad Reply-To: lcremean@tidalwave.net References: <68606.914783086@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <68606.914783086@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Dec 27, 1998 at 07:24:46PM +0100 X-OS: FreeBSD 3.0-CURRENT X-Evil: microsoft.com Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 27, 1998 at 07:24:46PM +0100, Poul-Henning Kamp wrote: > In message , Brian > Feldman writes: > >What was the reasoning behind ft though? > > It's badly implemented and many capable persons have failed to find a > way to solve the rather serious problems it suffers from. ATAPI tapes > seems to be the way of the future for cheap tapes. If ft were as nice as the SCSI tape driver, then I'd say keep it, but ft is extremely crocky (I know, I tried using it once) and very, _very_ slow since it has to use the floppy drive controller. Personally, I'd like PCs to be able to just get rid of the old uPD765/WD37C65-based FDC completely, and use ATAPI, USB, or SCSI floppies (like my ATAPI LS-120) and tapes, but I guess that's a few years off... -- lee, who's had his floppy-drive port turned off for at least a month now. -- +--------------------------------------------------------------------+ | 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 Sun Dec 27 13:53:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07180 for freebsd-current-outgoing; Sun, 27 Dec 1998 13:53:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07172 for ; Sun, 27 Dec 1998 13:53:47 -0800 (PST) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id WAA09053; Sun, 27 Dec 1998 22:51:09 +0100 (MET) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id WAA00683; Sun, 27 Dec 1998 22:37:59 +0100 (CET) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199812272137.WAA00683@semyam.dinoco.de> To: Luigi Rizzo cc: mike@smith.net.au (Mike Smith), seggers@semyam.dinoco.de, erikf@visi.com, freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Broken ipfw? In-reply-to: Your message of "Sun, 27 Dec 1998 09:44:11 +0100." <199812270844.JAA08636@labinfo.iet.unipi.it> Date: Sun, 27 Dec 1998 22:37:58 +0100 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > that was my mistake when i first committed dummynet patches, but i > think i fixed it on Dec.21-22 Thanks. That fixed it. Now I have a new world though I planned to do it the next time end of January for lack of time till then. ;-) Stefan. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 14:48:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12077 for freebsd-current-outgoing; Sun, 27 Dec 1998 14:48:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from helios.dnttm.ru (dnttm-gw.rssi.ru [193.232.0.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA12058 for ; Sun, 27 Dec 1998 14:48:19 -0800 (PST) (envelope-from dima@tejblum.dnttm.rssi.ru) Received: (from uucp@localhost) by helios.dnttm.ru (8.9.1/8.9.1/IP-3) with UUCP id BAA14946; Mon, 28 Dec 1998 01:19:36 +0300 Received: from tejblum.dnttm.rssi.ru (localhost [127.0.0.1]) by tejblum.dnttm.rssi.ru (8.9.1/8.9.1) with ESMTP id BAA00733; Mon, 28 Dec 1998 01:22:33 +0300 (MSK) (envelope-from dima@tejblum.dnttm.rssi.ru) Message-Id: <199812272222.BAA00733@tejblum.dnttm.rssi.ru> X-Mailer: exmh version 2.0gamma 1/27/96 To: garman@earthling.net cc: current@FreeBSD.ORG Subject: Re: PR filed on dying daemons bug In-reply-to: Your message of "Sun, 27 Dec 1998 01:10:03 EST." <199812270610.WAA15223@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Dec 1998 01:22:33 +0300 From: Dmitrij Tejblum Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I upgraded to a recent -current (as of two days ago) and found the > dying daemons bug still exists :( > > I filed a PR on the subject since I couldn't find another which already > addressed the issue. It's kern/9195. I'm more than willing to give > people accounts, test patches, etc for the cause of trying to fix this > bug, as myself as well as many others are still experiencing it on a > regular basis. I once suggested this patch: --- sys/vm/swap_pager.c Mon Dec 28 00:21:12 1998 +++ sys/vm/swap_pager.c Mon Dec 28 00:21:52 1998 @@ -1130,4 +1130,5 @@ swap_pager_getpages(object, m, count, re m[reqpage]->object->last_read = m[count-1]->pindex; +#if 0 /* * If we're out of swap space, then attempt to free @@ -1144,4 +1145,5 @@ swap_pager_getpages(object, m, count, re m[0]->pindex + paging_offset, count); } +#endif } else { I remember 1 positive response on it, and 0 negative responses. Feel free to try this patch. As a side note, IMO the code (that the patch ifdef out) is not a very good idea, whether it is related to the "daemon dying" bug or not. There is usually some amount of allocated but unused swap space (20-50%, I think), and this space apparently left allocated but unused forever, and the code free used swap space instead.... Dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 14:54:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA13079 for freebsd-current-outgoing; Sun, 27 Dec 1998 14:54:43 -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 OAA13065; Sun, 27 Dec 1998 14:54:34 -0800 (PST) (envelope-from asami@sunrise.cs.berkeley.edu) Received: from bubble.didi.com (sji-ca32-59.ix.netcom.com [209.109.239.59]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id OAA23390; Sun, 27 Dec 1998 14:54:07 -0800 (PST) Received: (from asami@localhost) by bubble.didi.com (8.8.8/8.8.8) id OAA23572; Sun, 27 Dec 1998 14:53:30 -0800 (PST) (envelope-from asami) Date: Sun, 27 Dec 1998 14:53:30 -0800 (PST) Message-Id: <199812272253.OAA23572@bubble.didi.com> To: phk@critter.freebsd.dk CC: green@unixhelp.org, current@FreeBSD.ORG, sos@FreeBSD.ORG In-reply-to: <68199.914779200@critter.freebsd.dk> (message from Poul-Henning Kamp on Sun, 27 Dec 1998 18:20:00 +0100) Subject: Re: wanton Atticizing is bad From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * The cleanups have been discussed in -core. There was no agreement about pcvt. 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 27 15:00:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13742 for freebsd-current-outgoing; Sun, 27 Dec 1998 15:00:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13722 for ; Sun, 27 Dec 1998 15:00:28 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id SAA17349; Sun, 27 Dec 1998 18:00:15 -0500 (EST) Date: Sun, 27 Dec 1998 18:00:15 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Matthew Dillon cc: current@FreeBSD.ORG Subject: Re: "ICMP_BANDLIM" In-Reply-To: <199812272016.MAA51694@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Dec 1998, Matthew Dillon wrote: > : Does anyone have an aversion to options "ICMP_BANDLIM" going into GENERIC? I > :think it's very justifiable, and doesn't bloat the kernel unnecessarily (also, > :Solaris and Linux, that I know of so far, also do this, so it's a pretty > :standard thing). And how about using an option "ICMP_BANDLIM_SILENT" as well? > :Sometimes you don't really want to see your message buffer filling up with > :ICMP_BANDLIM messages, and option "ICMP_BANDLIM_SILENT" would probably go into > :GENERIC too. If everyone thinks this is a good idea, I'll make the patches to > :src/sys/netinet/ip_input.c src/sys/{i386,alpha}/conf/GENERIC > :src/sys/i386/conf/options.i386 src/sys/alpha/conf/options.alpha and maybe PC98? > :PC98 should probably be left alone... > : > :Comments? > > I was planning on waiting a release but it does appear to be solid, I > think we can enable it permanently. The bandlim error messages are > rate limited, it should not create a burden on the log files, but I > suppose a silent option could be added - no skin off the code's nose :-) > > The only problem is that I do not have time to do it right now and my Taken care of. I've been doing a lot of fixing lately! In the patches lying around I've got a CPU_WT_ALLOC patch, DDB patch, patch to add ICMP_BANDLIM_\ SILENT, preventing revocation of VFIFO's, a USB major fix, and a fix to USB crashing if you attempt access certain dev_t's. :) > code tree is sitting on the floor in pieces while I work on the swap > system. If a committer wants to commit the appropriate changes > please feel free! > > -Matt > > : Brian Feldman _ __ ___ ___ ___ > : green@unixhelp.org _ __ ___ | _ ) __| \ > : http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > : FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > : > > Matthew Dillon Engineering, HiWay Technologies, Inc. & BEST Internet > Communications & God knows what else. > (Please include original email in any response) > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 15:01:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13996 for freebsd-current-outgoing; Sun, 27 Dec 1998 15:01:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fep1-orange.clear.net.nz (fep1-orange.clear.net.nz [203.97.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13988 for ; Sun, 27 Dec 1998 15:01:19 -0800 (PST) (envelope-from jabley@buddha.clear.net.nz) Received: from buddha.clear.net.nz (buddha.clear.net.nz [192.168.24.106]) by fep1-orange.clear.net.nz (1.5/1.11) with ESMTP id MAA12245; Mon, 28 Dec 1998 12:00:57 +1300 (NZDT) Received: (from jabley@localhost) by buddha.clear.net.nz (8.9.1/8.9.1) id MAA28942; Mon, 28 Dec 1998 12:00:57 +1300 (NZDT) Date: Mon, 28 Dec 1998 12:00:57 +1300 From: Joe Abley To: "David E. Cross" Cc: freebsd-current@FreeBSD.ORG, jabley@clear.co.nz Subject: Re: PPTP and FreeBSD Message-ID: <19981228120057.A28852@clear.co.nz> References: <199812272119.QAA13600@o2.cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199812272119.QAA13600@o2.cs.rpi.edu>; from David E. Cross on Sun, Dec 27, 1998 at 04:19:39PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 27, 1998 at 04:19:39PM -0500, David E. Cross wrote: > I had looked into this at the past, and read the relavent RFCs and MS > documentation on it. It is a bad joke, all the way arround. First it uses a > modified version of the GRE protocol (that is why I asked about GRE support > in the kernel way back when), as an encapsulation around the PPP packets. But, to be fair, GRE has been extended in a reasonable-looking and backward- compatible way. I don't personally agree with the methodology either, and would have preferred to see sequence numbers present in a further protocol header between GRE and PPP, leaving GRE as it is, but oh well... > It > also must have a TCP connection between the client and the server to act as > a controll connection. If that control connection is lost for whatever reason > , the tunel is closed. I don't really see why this is such a bad thing. The use of the TCP session is a bit clunky, but if the network is unstable enough that a TCP connection carrying minimal data cannot survive, then the tunnel probably _ought_ to be closed. > Oh yes, one last thing, the GRE portion of the tunel, > where the data actually goes, has an ack/nak, sliding window and retransmit > system (again, outlined in the MS documentation). The tunnel end-points do _not_ do retransmissions, but they do operate some (barely-specified) end-to-end flow control. > While I think this would > be a good thing to have, just to be compatible, and ideally as a part of a > larger 'iptunel' packagel; it is *alot* of work. I agree - it is a pretty nasty protocol, but has the advantage of widespread userbase support - show me one other tunnelling client which is ready and waiting on as many desktops as PPTP (even if the users don't know it's there). I've been looking at draft-ietf-pppext-pptp-07.txt and I don't thing that the PPTP elements look particularly difficult to code. A high-performance PPTP Network Server (PNS) implementation on FreeBSD could be made using existing PPP stacks, with the proviso that the tunnel creation/teardown would involve process switching (for the userland portions of PPP), and a server that was required to support a large number of simultaneously-active tunnels would correspondingly need a large number of kernel ppp/tun interfaces available (one per tunnel). A generic kernel tunnel interface would make this easier. Just some thoughts :) Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 15:04:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14151 for freebsd-current-outgoing; Sun, 27 Dec 1998 15:04:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles315.castles.com [208.214.167.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14146 for ; Sun, 27 Dec 1998 15:04:19 -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 OAA05423; Sun, 27 Dec 1998 14:57:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812272257.OAA05423@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mark Murray cc: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Sun, 27 Dec 1998 20:01:20 +0200." <199812271801.UAA38580@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Dec 1998 14:57:24 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > We now need (tr: I would like) some kind of "ports-like" mechanism > for kernel bits, such as example kld so devices can be written by > the general population _and_maintained_ as ports code (kinda like > the commercial sound driver). The "ultimate goal" for KLD modules is for them to be able to be built standalone. If your KLD doesn't require intimate knowledge of the internals of the kernel, then that's already quite feasible. -- \\ 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 27 15:52:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA17759 for freebsd-current-outgoing; Sun, 27 Dec 1998 15:52:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm510-06.dialip.mich.net [131.118.249.228]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA17754 for ; Sun, 27 Dec 1998 15:52:19 -0800 (PST) (envelope-from garman@earthling.net) From: garman@earthling.net Message-Id: <199812272352.PAA17754@hub.freebsd.org> Received: (qmail 1113 invoked from smtpd); 27 Dec 1998 23:52:10 -0000 Received: from localhost.garman.net (HELO earthling.net) (127.0.0.1) by localhost.garman.net with SMTP; 27 Dec 1998 23:52:10 -0000 Date: Sun, 27 Dec 1998 18:52:09 -0500 (EST) Reply-To: garman@earthling.net Subject: Re: HD LED doesn't go off To: alexlh@funk.org cc: freebsd-current@FreeBSD.ORG In-Reply-To: <36855840.E1286D95@funk.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 26 Dec, Alex Le Heux wrote: > Hi, > > On my recently-installed -current box the hd led doesn't ever seem to go > off. > > I know it doesn't do this under win98 or when it was still (briefly) > 3.0-RELEASE. > > Anyone has a clue what might cause this? > This might not be whats causing it for you, but I have the same problem, and one day while i was real bored, I decided to find out why. It turns out that my real old 2x IDE cdrom drive (it's a sony) causes this. When this drive is removed, the hd light operates as normal. Otherwise, it just stays on. Strange. It doesn't cause any problems, just FYI. enjoy -- Jason Garman http://fs.sso.sytexinc.com/~jgarman/ Student, University of Maryland garman@earthling.net Words of Wisdom from the Simpsons: Whois: JAG145 "'The President did it' is not an excuse" -- Bart Simpson's punishment To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 16:19:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22868 for freebsd-current-outgoing; Sun, 27 Dec 1998 16:19:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from garman.dyn.ml.org (pm510-06.dialip.mich.net [131.118.249.228]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA22862 for ; Sun, 27 Dec 1998 16:19:39 -0800 (PST) (envelope-from garman@earthling.net) From: garman@earthling.net Message-Id: <199812280019.QAA22862@hub.freebsd.org> Received: (qmail 2101 invoked from smtpd); 28 Dec 1998 00:19:34 -0000 Received: from localhost.garman.net (HELO earthling.net) (127.0.0.1) by localhost.garman.net with SMTP; 28 Dec 1998 00:19:34 -0000 Date: Sun, 27 Dec 1998 19:19:32 -0500 (EST) Reply-To: garman@earthling.net Subject: Re: PR filed on dying daemons bug To: dima@tejblum.dnttm.rssi.ru cc: current@FreeBSD.ORG In-Reply-To: <199812272222.BAA00733@tejblum.dnttm.rssi.ru> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Dec, Dmitrij Tejblum wrote: > I once suggested this patch: > [ patch snipped ] > > Dima > My, I forgot about that patch. It is working so far right now (I've managed to bring the swap usage to levels which would trigger the bug before, and nothing has happened yet) Thank you very much for that patch, please consider this a premature positive response :) I haven't had any negative side-effects as a result of this patch, and it might just be my imagination but it seemed to take much more work to get the machine to swap than before. enjoy -- Jason Garman http://fs.sso.sytexinc.com/~jgarman/ Student, University of Maryland garman@earthling.net Words of Wisdom from the Simpsons: Whois: JAG145 "'The President did it' is not an excuse" -- Bart Simpson's punishment To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 16:34:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26093 for freebsd-current-outgoing; Sun, 27 Dec 1998 16:34:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26088 for ; Sun, 27 Dec 1998 16:34:07 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA20406 for ; Sun, 27 Dec 1998 19:33:56 -0500 (EST) Date: Sun, 27 Dec 1998 19:33:56 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: current@FreeBSD.ORG Subject: debugger_on_panic behavior changes (for the better) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There's something that's been bugging me for a while, so I decided to fix it. FreeBSD now will DTRT WRT DDB and DDB_UNATTENDED (!debugger_on_panic), at least in my opinion. The behavior change is such that: 1. Nothing changes when debugger_on_panic != 0. 2. When DDB_UNATTENDED (!debugger_on_panic), if a panic occurs, the machine will reboot. Also, if a trap occurs, the machine will panic and reboot, unlike how it broke to DDB before. HOWEVER, a trap inside DDB will not cause a panic, allowing full use of DDB without having to worry about the machine being stuck at a DDB prompt if something goes wrong during the day. Patches for this behavior follow my signature, and it would be a boon to anyone (like me) who uses DDB_UNATTENDED, but actually wants the machine to panic on a trap (otherwise, what's the use, if the machine causes a fatal trap rather than a true panic, of debugger_on_panic?). The changes cause no adverse behavior, but do involve two symbols becoming global (shouldn't be that bad of pollution). Comments? Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ --- src/sys/kern/kern_shutdown.c.orig Sun Dec 27 15:00:08 1998 +++ src/sys/kern/kern_shutdown.c Sun Dec 27 15:01:51 1998 @@ -80,9 +80,9 @@ #ifdef DDB #ifdef DDB_UNATTENDED -static int debugger_on_panic = 0; +int debugger_on_panic = 0; #else -static int debugger_on_panic = 1; +int debugger_on_panic = 1; #endif SYSCTL_INT(_debug, OID_AUTO, debugger_on_panic, CTLFLAG_RW, &debugger_on_panic, 0, ""); --- src/sys/i386/i386/trap.c.orig Sun Dec 27 14:47:39 1998 +++ src/sys/i386/i386/trap.c Sun Dec 27 15:01:01 1998 @@ -93,6 +93,10 @@ #include #endif +#ifdef DDB + extern int in_Debugger, debugger_on_panic; +#endif + #include "isa.h" #include "npx.h" @@ -901,7 +905,7 @@ return; #endif #ifdef DDB - if (kdb_trap (type, 0, frame)) + if ((debugger_on_panic || in_Debugger) && kdb_trap(type, 0, frame)) return; #endif printf("trap number = %d\n", type); --- src/sys/i386/i386/db_interface.c.orig Sun Dec 27 14:45:51 1998 +++ src/sys/i386/i386/db_interface.c Sun Dec 27 14:56:54 1998 @@ -295,11 +295,12 @@ * Move this to machdep.c and allow it to be called if any debugger is * installed. */ +volatile int in_Debugger = 0; + void Debugger(msg) const char *msg; { - static volatile u_char in_Debugger; /* * XXX To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 16:38:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26636 for freebsd-current-outgoing; Sun, 27 Dec 1998 16:38:06 -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 QAA26603; Sun, 27 Dec 1998 16:37:58 -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 LAA25758; Mon, 28 Dec 1998 11:07:23 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA29613; Mon, 28 Dec 1998 11:07:25 +1030 (CST) Message-ID: <19981228110724.V12346@freebie.lemis.com> Date: Mon, 28 Dec 1998 11:07:24 +1030 From: Greg Lehey To: Poul-Henning Kamp , Brian Feldman Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: wanton Atticizing is bad References: <68199.914779200@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <68199.914779200@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Dec 27, 1998 at 06:20:00PM +0100 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 On Sunday, 27 December 1998 at 18:20:00 +0100, Poul-Henning Kamp wrote: > > The cleanups have been discussed in -core. > > -committers is a notorious unproductive and flame-prone place to > discuss code removal. Your opinion. Certainly a bit of information would have been useful, considering that the majority of the people affected are in -committers and not in -core. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 16:41:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26890 for freebsd-current-outgoing; Sun, 27 Dec 1998 16:41:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from easeway.com (ns1.easeway.com [209.69.71.100]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26883; Sun, 27 Dec 1998 16:41:53 -0800 (PST) (envelope-from mwlucas@easeway.com) Received: (from mwlucas@localhost) by easeway.com (8.8.8/8.8.5) id TAA13827; Sun, 27 Dec 1998 19:18:44 -0500 (EST) Message-Id: <199812280018.TAA13827@easeway.com> Subject: Re: wanton Atticizing is bad In-Reply-To: <68606.914783086@critter.freebsd.dk> from Poul-Henning Kamp at "Dec 27, 98 07:24:46 pm" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sun, 27 Dec 1998 19:18:44 -0500 (EST) Cc: green@unixhelp.org, current@FreeBSD.ORG, sos@FreeBSD.ORG From: mwlucas@exceptionet.com 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 > >> IPFILTER > > > >Wasn't this _just_recently_ committed? Why commit it in the first place if > >noone really wants it? Personally, I use IPFW. > > Yeah, the jury is still out on this one... Any users out there ? I occasionally use IPFilter. It's trivial to install from source, however, provided that the user can follow instructions. ==ml -- Michael Lucas | Exceptionet, Inc. | www.exceptionet.com "Exceptional Networking" | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 16:42:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27161 for freebsd-current-outgoing; Sun, 27 Dec 1998 16:42:59 -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 QAA27156 for ; Sun, 27 Dec 1998 16:42:58 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: from dragon.nuxi.com (IDENT:WHAT_THE_HELL_YOU_LOOKING_AT_@d60-077.leach.ucdavis.edu [169.237.60.77]) by relay.nuxi.com (8.9.1/8.9.1) with ESMTP id QAA25024 for ; Sun, 27 Dec 1998 16:42:41 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.1/8.9.1) id AAA21621 for current@freebsd.org; Mon, 28 Dec 1998 00:42:34 GMT (envelope-from obrien) Date: Sun, 27 Dec 1998 16:42:34 -0800 From: "David O'Brien" To: current@FreeBSD.ORG Subject: How to convert from LKMs to modules? (was Re: cvs commit: src/lkm/atapi .. ) Message-ID: <19981227164233.A21585@dragon.nuxi.com> Reply-To: obrien@nuxi.ucdavis.edu References: <199812271938.LAA10037@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: =?iso-8859-1?Q?=3C199812271938=2ELAA10037=40freefall=2Efreebsd=2Eorg=3E?= =?iso-8859-1?Q?=3B_from_S=F8ren_Schmidt_on_Sun=2C_Dec_27=2C_1998_at_11:3?= =?iso-8859-1?Q?8:15AM_-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 > Log: > Remove LKM's depricated by modules. Ok, now that LKM's are gone, can someone please explain what this means to me on my next ``make world''? I'm 3.0-CURRENT (very current) but still a.out. Do modules even work for a.out? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 16:46:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27399 for freebsd-current-outgoing; Sun, 27 Dec 1998 16:46:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles315.castles.com [208.214.167.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27392 for ; Sun, 27 Dec 1998 16:46:04 -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 QAA06079; Sun, 27 Dec 1998 16:43:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812280043.QAA06079@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: obrien@nuxi.ucdavis.edu cc: current@FreeBSD.ORG Subject: Re: How to convert from LKMs to modules? (was Re: cvs commit: src/lkm/atapi .. ) In-reply-to: Your message of "Sun, 27 Dec 1998 16:42:34 PST." <19981227164233.A21585@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Dec 1998 16:43:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Log: > > Remove LKM's depricated by modules. > > Ok, now that LKM's are gone, can someone please explain what this means > to me on my next ``make world''? I'm 3.0-CURRENT (very current) but > still a.out. > > Do modules even work for a.out? Yes. -- \\ 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 27 16:46:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27450 for freebsd-current-outgoing; Sun, 27 Dec 1998 16:46:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from elusive.suspicion.org (ELUSIVE.SUSPICION.ORG [216.27.37.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27440 for ; Sun, 27 Dec 1998 16:46:53 -0800 (PST) (envelope-from tstromberg@rtci.com) Received: from rtci.com (bromma.it.kth.se [130.237.14.242]) by elusive.suspicion.org (8.9.1b+Sun/8.9.1) with ESMTP id TAA00978; Sun, 27 Dec 1998 19:31:29 -0500 (EST) Message-ID: <3686D125.49EBFD9@rtci.com> Date: Mon, 28 Dec 1998 01:30:29 +0100 From: Thomas Stromberg Organization: Research Triangle Consultants, Inc. X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Poul-Henning Kamp , freebsd-current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad References: <68606.914783086@critter.freebsd.dk> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote:>> IPFILTER > > > >Wasn't this _just_recently_ committed? Why commit it in the first place if > >noone really wants it? Personally, I use IPFW. > > Yeah, the jury is still out on this one... Any users out there ? If anyone on this list has never used ipfilter, I highly recommend it over ipfw. http://cheops.anu.edu.au/~avalon/ for more information on it. I personally just switched from ipfw (after over a year of usage) on all of our firewalls to ipfilter. Why the switch? I heard its acclaim after it was committed into -CURRENT, and also read up on some sites like http://www.freebsddairy.com .. I think these are the reasons why I prefer ipfilter over ipfw 1. I felt a larger range of control in its setup. Although I don't particularly like the rules mechanism and shortcut it all with the "quick" operand; I find the rule definition to be finer tuned. 2. Cross-platformness. I have a full intention to deploy ipfilter on some IRIX and Solaris boxes in the near future (as a "personal" firewall hack). I find it extremely pleasing that I can use ipfilter on our IRIX, Solaris, BSD/OS, and FreeBSD machines. It gives me the ability to template everything out. IPFilter is now also a part of OpenBSD and NetBSD, and works in Linux as well as the aforementioned operating systems. 3. The primary reason for the switch: More descriptive logging. While this could be changed in ipfw easily, it was here for me in ipfilter already. Why limit yourself to seeing "ipfw: denied ICMP type x.x from x to x" when you can have ipfilter say: Dec 27 19:18:31 under ipmon[341]: 19:18:30.453472 xl0 @0:29 p 206.115.158.181 -> 216.27.37.14 PR icmp len 20 56 icmp 3/1 for 216.27.37.14,21 - 208.251.56.92,1228 PR tcp len 20 24576 4. Not only does it log those, but if needed, also keeps 128 bytes of the packet. I'll give you that it is a highly unreadable output, but that's what parsers are for.. which is why I wrote syslogcat to parse and or monitor in tail -f style ipfilter/ipfw/everything else into english. ftp://ftp.suspicion.org/pub/projects/syslogcat/ For me the question isn't "Why keep ipfilter?", the question for me on my LAN is "Why bother with IPFW and all of the proprietary packet filtering systems each OS has when I can just standardize on ipfilter?". While IPFW is fine and all, I don't see any advantage to it over ipfilter at this point. While ipfilter is very easy to compile if its not included in the core OS, I think it would be a shame, because if it was never committed, I for one would of never found how nice it is. If anyone is interested, I have a "personal" ipfilter ruleset used on my 3.0-CURRENT testing station available on ftp://ftp.suspicion.org/pub/misc/myconfig/ and the old ipfw ruleset that it replaced. -- --------------------------------------------------------------------- Thomas Stromberg thomas@stromberg.org Senior Systems Administrator, (919) 380-9771 ext. 3210 Research Triangle Consultants, Inc. FreeBSD: 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 27 16:47:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA27478 for freebsd-current-outgoing; Sun, 27 Dec 1998 16:47:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA27470 for ; Sun, 27 Dec 1998 16:47:13 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA20867; Sun, 27 Dec 1998 19:46:57 -0500 (EST) Date: Sun, 27 Dec 1998 19:46:57 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "David O'Brien" cc: current@FreeBSD.ORG Subject: Re: How to convert from LKMs to modules? (was Re: cvs commit: src/lkm/atapi .. ) In-Reply-To: <19981227164233.A21585@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Dec 1998, David O'Brien wrote: > > Log: > > Remove LKM's depricated by modules. > > Ok, now that LKM's are gone, can someone please explain what this means > to me on my next ``make world''? I'm 3.0-CURRENT (very current) but > still a.out. It means /lkm won't be populated nor built. > > Do modules even work for a.out? I've never tried it, but all the a.out kernel linker code is there, so I'll say "yes" almost definitely ;) Go ahead and try it, of course. If you kldstat and modstat, I wouldn't be surprised if your system's kldstat had entries and modstat didn't, already. > > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 16:59:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28100 for freebsd-current-outgoing; Sun, 27 Dec 1998 16:59:25 -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 QAA28090 for ; Sun, 27 Dec 1998 16:59:21 -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 LAA25867 for ; Mon, 28 Dec 1998 11:28:49 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA29683; Mon, 28 Dec 1998 11:28:51 +1030 (CST) Message-ID: <19981228112851.Y12346@freebie.lemis.com> Date: Mon, 28 Dec 1998 11:28:51 +1030 From: Greg Lehey To: FreeBSD current users Subject: Thanks, Core Team Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit 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 OK, I'll try to summarize what I understand of the latest changes in -CURRENT: 1. LKMs are gone. 2. This was decided by the core team. 3. Nobody else was informed. 4. In my case, my Vinum product just got dumped from the repository. The first thing I heard was a laconic comment from Søren saying ``Sorry for the mess, but it was overdue...'', followed by a commit message showing them all gone. Well, thanks a lot. Suddenly, without any warning (but still overdue...), my project is gone, and I have an unknown amount of work to get back on track. The least I would have expected would be a bit of advance warning. Instead, what do I get? On Sunday, 27 December 1998 at 18:20:00 +0100, Poul-Henning Kamp wrote: > > The cleanups have been discussed in -core. > > -committers is a notorious unproductive and flame-prone place to > discuss code removal. Well, this is certainly an unproductive and flame-prone way to perform code removal. I'd consider it a slap in the eye for all non-core committers. I'd be interested in knowing how you would perform it if you were deliberately trying to annoy us. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 17:03:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28695 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:03:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28690 for ; Sun, 27 Dec 1998 17:03:19 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu ((IDENT root)@rac2.wam.umd.edu [128.8.10.142]) by po3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id UAA00115; Sun, 27 Dec 1998 20:02:53 -0500 (EST) Received: from rac2.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id UAA24176; Sun, 27 Dec 1998 20:02:52 -0500 (EST) Received: from localhost by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id UAA24171; Sun, 27 Dec 1998 20:02:51 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Sun, 27 Dec 1998 20:02:50 -0500 (EST) From: Kenneth Wayne Culver To: Greg Lehey cc: FreeBSD current users Subject: Re: Thanks, Core Team In-Reply-To: <19981228112851.Y12346@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id RAA28691 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Dec 1998, Greg Lehey wrote: > OK, I'll try to summarize what I understand of the latest changes in -CURRENT: > > 1. LKMs are gone. > 2. This was decided by the core team. > 3. Nobody else was informed. > 4. In my case, my Vinum product just got dumped from the repository. > The first thing I heard was a laconic comment from Søren saying > ``Sorry for the mess, but it was overdue...'', followed by a > commit message showing them all gone. > > Well, thanks a lot. Suddenly, without any warning (but still > overdue...), my project is gone, and I have an unknown amount of work > to get back on track. The least I would have expected would be a bit > of advance warning. Instead, what do I get? > > On Sunday, 27 December 1998 at 18:20:00 +0100, Poul-Henning Kamp wrote: > > > > The cleanups have been discussed in -core. > > > > -committers is a notorious unproductive and flame-prone place to > > discuss code removal. > > Well, this is certainly an unproductive and flame-prone way to perform > code removal. I'd consider it a slap in the eye for all non-core > committers. I'd be interested in knowing how you would perform it if > you were deliberately trying to annoy us. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > I've got a question, if LKM's are gone, how are OSS/FreeBSD, and arla, and all the other LKM dependent FreeBSD addons going to work?? Kenneth culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 17:05:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28890 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:05:58 -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 RAA28885 for ; Sun, 27 Dec 1998 17:05:54 -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 LAA25903; Mon, 28 Dec 1998 11:35:21 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA29706; Mon, 28 Dec 1998 11:35:23 +1030 (CST) Message-ID: <19981228113523.Z12346@freebie.lemis.com> Date: Mon, 28 Dec 1998 11:35:23 +1030 From: Greg Lehey To: Kenneth Wayne Culver Cc: FreeBSD current users Subject: Re: Thanks, Core Team References: <19981228112851.Y12346@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Kenneth Wayne Culver on Sun, Dec 27, 1998 at 08:02:50PM -0500 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 On Sunday, 27 December 1998 at 20:02:50 -0500, Kenneth Wayne Culver wrote: > On Mon, 28 Dec 1998, Greg Lehey wrote: >> 1. LKMs are gone. >> > I've got a question, if LKM's are gone, how are OSS/FreeBSD, and arla, and > all the other LKM dependent FreeBSD addons going to work?? They've been replaced by klds. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 17:08:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29237 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:08:26 -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 RAA29231 for ; Sun, 27 Dec 1998 17:08:24 -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 UAA71341; Sun, 27 Dec 1998 20:07:56 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Greg Lehey cc: FreeBSD current users From: "Gary Palmer" Subject: Re: Thanks, Core Team In-reply-to: Your message of "Mon, 28 Dec 1998 11:28:51 +1030." <19981228112851.Y12346@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sun, 27 Dec 1998 20:07:55 -0500 Message-ID: <71337.914807275@gjp.erols.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA29232 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote in message ID <19981228112851.Y12346@freebie.lemis.com>: > 2. This was decided by the core team. s/decided/discussed/ There was no vote called on this. I'll leave the Danish contingent to support their actions, because I personally don't. Gary To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 17:09:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29441 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:09:55 -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 RAA29436 for ; Sun, 27 Dec 1998 17:09:54 -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 UAA71365; Sun, 27 Dec 1998 20:09:25 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Kenneth Wayne Culver cc: Greg Lehey , FreeBSD current users From: "Gary Palmer" Subject: Re: Thanks, Core Team In-reply-to: Your message of "Sun, 27 Dec 1998 20:02:50 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Sun, 27 Dec 1998 20:09:25 -0500 Message-ID: <71362.914807365@gjp.erols.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA29437 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote in message ID : > I've got a question, if LKM's are gone, how are OSS/FreeBSD, and arla, and > all the other LKM dependent FreeBSD addons going to work?? Unless I missed a commit, then you can still load modules, just that /lkm will no longer be populated on a make world. 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 Sun Dec 27 17:46:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05652 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:46:08 -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 RAA05647 for ; Sun, 27 Dec 1998 17:46:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA12443; Sun, 27 Dec 1998 17:45:37 -0800 (PST) To: Greg Lehey cc: FreeBSD current users Subject: Re: Thanks, Core Team In-reply-to: Your message of "Mon, 28 Dec 1998 11:28:51 +1030." <19981228112851.Y12346@freebie.lemis.com> Date: Sun, 27 Dec 1998 17:45:37 -0800 Message-ID: <12439.914809537@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1. LKMs are gone. > 2. This was decided by the core team. > 3. Nobody else was informed. Actually, while some of the recent events came as much as a surprise to core as anyone else, the transition from LKMs to KLD modules is not and should not come as a surprise to anyone. We've been talking about it for ages now in -current and the only way you could possibly fail to be informed about this transition would be if you had simply deleted every mail received from -current for at least the last 3 months. - 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 27 17:46:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05719 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:46:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05699; Sun, 27 Dec 1998 17:46:41 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id UAA22595; Sun, 27 Dec 1998 20:46:23 -0500 (EST) Message-ID: <19981227204623.I1333@ns1.adsu.bellsouth.com> Date: Sun, 27 Dec 1998 20:46:23 -0500 From: Christian Kuhtz To: Gary Palmer , Kenneth Wayne Culver Cc: Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team References: <71362.914807365@gjp.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <71362.914807365@gjp.erols.com>; from Gary Palmer on Sun, Dec 27, 1998 at 08:09:25PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Why is there no transition period like in any other reasonable software engineering period in which case both things still work? Not populating /lkm is sabotage. Regardless of the merits of kldm. On Sun, Dec 27, 1998 at 08:09:25PM -0500, Gary Palmer wrote: > Kenneth Wayne Culver wrote in message ID > : > > I've got a question, if LKM's are gone, how are OSS/FreeBSD, and arla, and > > all the other LKM dependent FreeBSD addons going to work?? > > Unless I missed a commit, then you can still load modules, just that /lkm will > no longer be populated on a make world. -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 17:49:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA05885 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:49:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fourier.physics.purdue.edu (fourier.physics.purdue.edu [128.210.146.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA05879 for ; Sun, 27 Dec 1998 17:49:17 -0800 (PST) (envelope-from jonsmith@fourier.physics.purdue.edu) Received: from localhost (jonsmith@localhost) by fourier.physics.purdue.edu (8.8.8/8.8.8) with SMTP id UAA16103; Sun, 27 Dec 1998 20:43:33 GMT (envelope-from jonsmith@fourier.physics.purdue.edu) Date: Sun, 27 Dec 1998 20:43:33 +0000 (GMT) From: Jonathan Smith To: "Jordan K. Hubbard" cc: Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team In-Reply-To: <12439.914809537@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 Both arguments here are sweeping and clearly no true. I read about 1/3 of the messages I receive (mostly because the rest I've never heard of and are over my head at this point) and I did not know until about and hour and a half ago. -j "If kisses could kill (gulp), that one would have flattened several small towns...." Vir Cotto, Babylon 5 "Tu was du willst." Die Unendliche Geschichte, von Michael Ende "Do as you wish." The Neverending Story, by Michael Ende The Microsoft Soloution, "newfs && make reinstall" Jon C. Smith (765)49-48628 PHYS 31h jonsmith@fourier.physics.purdue.edu 1396 Physics Building, West lafayette Purdue Univesity, Indiana 47906-1396 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 17:50:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06106 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:50:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06101 for ; Sun, 27 Dec 1998 17:50:57 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id UAA22657; Sun, 27 Dec 1998 20:50:32 -0500 (EST) Message-ID: <19981227205032.J1333@ns1.adsu.bellsouth.com> Date: Sun, 27 Dec 1998 20:50:32 -0500 From: Christian Kuhtz To: "Jordan K. Hubbard" , Greg Lehey Cc: FreeBSD current users Subject: Re: Thanks, Core Team References: <19981228112851.Y12346@freebie.lemis.com> <12439.914809537@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <12439.914809537@zippy.cdrom.com>; from Jordan K. Hubbard on Sun, Dec 27, 1998 at 05:45:37PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 27, 1998 at 05:45:37PM -0800, Jordan K. Hubbard wrote: > > 1. LKMs are gone. > > 2. This was decided by the core team. > > 3. Nobody else was informed. > > Actually, while some of the recent events came as much as a surprise > to core as anyone else, the transition from LKMs to KLD modules is not > and should not come as a surprise to anyone. We've been talking about > it for ages now in -current and the only way you could possibly fail > to be informed about this transition would be if you had simply > deleted every mail received from -current for at least the last 3 > months. Jordan, And three months is considered to be a suitable transition period? With all due respect, give me a break. *hrmph* If the old facility still works, why not leave both enabled? Does it hurt anything in the meantime? Developments take time, and particularly since very few of us actually get paid to do any work on this source if find a period of 3 months a relatively short recoding/"forklift" period. Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 17:53:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06246 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:53:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06241 for ; Sun, 27 Dec 1998 17:53:45 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id RAA16721; Sun, 27 Dec 1998 17:53:26 -0800 (PST) Date: Sun, 27 Dec 1998 17:53:26 -0800 (PST) From: "Steven P. Donegan" To: "Jordan K. Hubbard" cc: Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team In-Reply-To: <12439.914809537@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 Sun, 27 Dec 1998, Jordan K. Hubbard wrote: > > 1. LKMs are gone. > > 2. This was decided by the core team. > > 3. Nobody else was informed. > > Actually, while some of the recent events came as much as a surprise > to core as anyone else, the transition from LKMs to KLD modules is not > and should not come as a surprise to anyone. We've been talking about > it for ages now in -current and the only way you could possibly fail > to be informed about this transition would be if you had simply > deleted every mail received from -current for at least the last 3 > months. > I read every email on this forum - the above statement is BS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 17:56:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06462 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:56:05 -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 RAA06456 for ; Sun, 27 Dec 1998 17:56:01 -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 MAA26121; Mon, 28 Dec 1998 12:25:29 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA29819; Mon, 28 Dec 1998 12:25:31 +1030 (CST) Message-ID: <19981228122531.C12346@freebie.lemis.com> Date: Mon, 28 Dec 1998 12:25:31 +1030 From: Greg Lehey To: "Jordan K. Hubbard" Cc: FreeBSD current users Subject: Re: Thanks, Core Team References: <19981228112851.Y12346@freebie.lemis.com> <12439.914809537@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <12439.914809537@zippy.cdrom.com>; from Jordan K. Hubbard on Sun, Dec 27, 1998 at 05:45:37PM -0800 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 On Sunday, 27 December 1998 at 17:45:37 -0800, Jordan K. Hubbard wrote: >> 1. LKMs are gone. >> 2. This was decided by the core team. >> 3. Nobody else was informed. > > Actually, while some of the recent events came as much as a surprise > to core as anyone else, the transition from LKMs to KLD modules is not > and should not come as a surprise to anyone. We've been talking about > it for ages now in -current Sure, but that's not what I'm talking about. I've been gathering a lot of information about KLDs, and I've been meaning to move some time. But until this morning there was nothing to indicate that LKMs were going away in a hurry. It's interesting that recent events surprised you too, though. > and the only way you could possibly fail to be informed about this > transition would be if you had simply deleted every mail received > from -current for at least the last 3 months. This would be the same way that you could possibly fail to notice that I took a lively part in the discussions. That's not the point. Do *you* know how to get kld symbols into the kernel debugger? Peter gave me a pointer, but as they say, ``some assembly needed''. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 17:56:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06485 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:56:20 -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 RAA06479 for ; Sun, 27 Dec 1998 17:56:18 -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 CAA70845 for ; Mon, 28 Dec 1998 02:55:32 +0100 (CET) To: current@FreeBSD.ORG Subject: LKMs From: Poul-Henning Kamp Date: Mon, 28 Dec 1998 02:55:31 +0100 Message-ID: <70843.914810131@critter.freebsd.dk> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg: I think Soren was surprised by the fact that vinum sources lived under src/lkm, they shouldn't have, in particular not because klds were already on the way when vinum came in, but that aside, a repository copy (as noted in the commit message) will put the sources back in action the right place in the tree, and vinum will be with us again. Everybody: LKMs can still be loaded, we just don't produce any as part of make world anymore, klds are the future in that respect. The flurry of emails we see here now is the very reason why so little advance notice was given: It is impossible to delete anything from the tree based on concensus. We even had people complaining when we deleted some X.25 code (because they had >dreamed about< being able to use it for!!) If at least people would read their >ENTIRE< mailbox before starting to send more or less carefully thought out emails, things would be a lot better around here, and maybe a more democratic process could work. After 4 years, I have little or no hope that this will ever happen. But, let's reiterate the criteria we used today: 0. All this code can be found in the Attic. (Along with NETISO, NETCCITT, the old ISDN code, and God knows what we have up there with the old 5" irons and the xmas decorations.) 1. "It is in the tree" is not sufficient reason for it to stay there. Examples: if_eg, DSI_SOFTMODEM 2. All code should pass the "We would import it today if it was offered to us" test (with a decent margin of hysteresis) Example: pcvt, if_eg, DSI_SOFTMODEM 3. If it is unmaintained and need maintenance, it will be a hindrance to further (possibly independent) development. Examples: ft, pcvt, sea, nca0, uha0 4. If circumstances change (for instance: somebody hacks the code into better shape or makes a better implementation) reevaluation will take place. Example: isdn4bsd. And notice number 4: Can anybody by any chance remember the storm that was raised when the old junky isdn code was yanked ? Well, look at the result: now we have WORKING isdn & a maintainer. The dynamics of FreeBSD is not only addition, it is also subtraction. -- 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 27 17:56:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06509 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:56:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06502 for ; Sun, 27 Dec 1998 17:56:28 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id SAA15388; Sun, 27 Dec 1998 18:03:58 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812280203.SAA15388@troutmask.apl.washington.edu> Subject: Re: Thanks, Core Team In-Reply-To: <12439.914809537@zippy.cdrom.com> from "Jordan K. Hubbard" at "Dec 27, 1998 5:45:37 pm" To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Sun, 27 Dec 1998 18:03:58 -0800 (PST) Cc: grog@lemis.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 According to Jordan K. Hubbard: > > 1. LKMs are gone. > > 2. This was decided by the core team. > > 3. Nobody else was informed. > > Actually, while some of the recent events came as much as a surprise > to core as anyone else, the transition from LKMs to KLD modules is not > and should not come as a surprise to anyone. We've been talking about > it for ages now in -current and the only way you could possibly fail > to be informed about this transition would be if you had simply > deleted every mail received from -current for at least the last 3 > months. > > - Jordan > I was going to stay out of this, but this is bullshit. Soren and Poul are performing some major surgery such that a HEADS UP should have been given. I applaud their intentions, but abhor their method. -- Steve [Scrambling to deal with the deletion of Voxware on old hardware] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 17:57:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06578 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:57:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles315.castles.com [208.214.167.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA06567 for ; Sun, 27 Dec 1998 17:57:07 -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 RAA06527; Sun, 27 Dec 1998 17:54:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812280154.RAA06527@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christian Kuhtz cc: "Jordan K. Hubbard" , Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team In-reply-to: Your message of "Sun, 27 Dec 1998 20:50:32 EST." <19981227205032.J1333@ns1.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Dec 1998 17:54:02 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Dec 27, 1998 at 05:45:37PM -0800, Jordan K. Hubbard wrote: > > > 1. LKMs are gone. > > > 2. This was decided by the core team. > > > 3. Nobody else was informed. > > > > Actually, while some of the recent events came as much as a surprise > > to core as anyone else, the transition from LKMs to KLD modules is not > > and should not come as a surprise to anyone. We've been talking about > > it for ages now in -current and the only way you could possibly fail > > to be informed about this transition would be if you had simply > > deleted every mail received from -current for at least the last 3 > > months. > > And three months is considered to be a suitable transition period? With all > due respect, give me a break. *hrmph* This was discussed at length for some time; and in Greg's case as one of the LKM-laggers we've been trying to encourage him to switch for some time, and that was in fact on the agenda before the jackboots arrived. Three months is actually not at all unreasonable, especially given how trivial the actual code changes required are. > If the old facility still works, why not leave both enabled? Because LKMs don't work for ELF kernels, and we should be making the ELF kernel cutover before we branch. Again, this is something that should have been understood by the folks following -current, although we haven't necessarily been making enough loud noise about it to keep it a constant discussion topic. -- \\ 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 27 17:58:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA06677 for freebsd-current-outgoing; Sun, 27 Dec 1998 17:58:34 -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 RAA06667; Sun, 27 Dec 1998 17:58:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id RAA12589; Sun, 27 Dec 1998 17:58:06 -0800 (PST) To: Christian Kuhtz cc: Gary Palmer , Kenneth Wayne Culver , Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team In-reply-to: Your message of "Sun, 27 Dec 1998 20:46:23 EST." <19981227204623.I1333@ns1.adsu.bellsouth.com> Date: Sun, 27 Dec 1998 17:58:06 -0800 Message-ID: <12586.914810286@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Not populating /lkm is sabotage. Regardless of the merits of kldm. Please explain the precise meaning if your statement. This strikes me as just more ignorant speculation by someone who hasn't even bothered to do a feature-by-feature comparison of /modules and the old /kld. - 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 27 18:00:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06869 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:00:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06862 for ; Sun, 27 Dec 1998 18:00:20 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id SAA16763; Sun, 27 Dec 1998 18:00:04 -0800 (PST) Date: Sun, 27 Dec 1998 18:00:04 -0800 (PST) From: "Steven P. Donegan" To: "Jordan K. Hubbard" , Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team 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, 27 Dec 1998, Steven P. Donegan wrote: > > I read every email on this forum - the above statement is BS. > Sorry to be short - my point was I have seen no discussion on committing this (major) change - some comments pro/con yes - doing it no. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 18:04:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07137 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:04:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles315.castles.com [208.214.167.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07132 for ; Sun, 27 Dec 1998 18:04:42 -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 SAA06590; Sun, 27 Dec 1998 18:01:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812280201.SAA06590@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Steven P. Donegan" cc: "Jordan K. Hubbard" , Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team In-reply-to: Your message of "Sun, 27 Dec 1998 18:00:04 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Dec 1998 18:01:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 27 Dec 1998, Steven P. Donegan wrote: > > > > > I read every email on this forum - the above statement is BS. > > Sorry to be short - my point was I have seen no discussion on committing > this (major) change - some comments pro/con yes - doing it no. That makes more sense; I was going to point out that we've been actively discussing the migration for months. The suddenness of the cutover was indeed alarming, but all that was really missing was a HEADS UP. -- \\ 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 27 18:05:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07392 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:05:43 -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 SAA07387 for ; Sun, 27 Dec 1998 18:05:40 -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 DAA70938; Mon, 28 Dec 1998 03:03:09 +0100 (CET) To: Steve Kargl cc: jkh@zippy.cdrom.com (Jordan K. Hubbard), grog@lemis.com, FreeBSD-current@FreeBSD.ORG Subject: Re: Thanks, Core Team In-reply-to: Your message of "Sun, 27 Dec 1998 18:03:58 PST." <199812280203.SAA15388@troutmask.apl.washington.edu> Date: Mon, 28 Dec 1998 03:03:09 +0100 Message-ID: <70936.914810589@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I was going to stay out of this, but this is bullshit. Soren >and Poul are performing some major surgery such that a HEADS UP >should have been given. I applaud their intentions, but abhor >their method. Well, if people had a more civilized way with email, such as considering carefully if the email adds anything of substance or just clutter mailboxes, then maybe such a HEADS UP would have a value. With the current level of communications skills (as you can see right now!) on the list, a HEADS UP doesn't accomplish anything productive. -- 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 27 18:09:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07651 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:09:06 -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 SAA07646 for ; Sun, 27 Dec 1998 18:09:04 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id SAA12684; Sun, 27 Dec 1998 18:08:34 -0800 (PST) To: Christian Kuhtz cc: Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team In-reply-to: Your message of "Sun, 27 Dec 1998 20:50:32 EST." <19981227205032.J1333@ns1.adsu.bellsouth.com> Date: Sun, 27 Dec 1998 18:08:33 -0800 Message-ID: <12680.914810913@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And three months is considered to be a suitable transition period? With all > due respect, give me a break. *hrmph* Again, I don't believe that the "transition" question here is adequately understood by the parties arguing it and we're likely not even having the same argument. As Gary has pointed out, old lkms will continue to work and I'm still waiting for you to indicate just what what in /lkm has not been adequately supplanted by /modules. - 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 27 18:10:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07964 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:10:35 -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 SAA07959 for ; Sun, 27 Dec 1998 18:10:32 -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 DAA70987; Mon, 28 Dec 1998 03:08:17 +0100 (CET) To: Greg Lehey cc: "Jordan K. Hubbard" , FreeBSD current users Subject: Re: Thanks, Core Team In-reply-to: Your message of "Mon, 28 Dec 1998 12:25:31 +1030." <19981228122531.C12346@freebie.lemis.com> Date: Mon, 28 Dec 1998 03:08:17 +0100 Message-ID: <70985.914810897@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19981228122531.C12346@freebie.lemis.com>, Greg Lehey writes: >On Sunday, 27 December 1998 at 17:45:37 -0800, Jordan K. Hubbard wrote: >>> 1. LKMs are gone. >>> 2. This was decided by the core team. >>> 3. Nobody else was informed. >> >> Actually, while some of the recent events came as much as a surprise >> to core as anyone else, the transition from LKMs to KLD modules is not >> and should not come as a surprise to anyone. We've been talking about >> it for ages now in -current > >Sure, but that's not what I'm talking about. I've been gathering a >lot of information about KLDs, and I've been meaning to move some >time. But until this morning there was nothing to indicate that LKMs >were going away in a hurry. It's interesting that recent events >surprised you too, though. Notice my friends (and foes) that we have less than 3 weeks to get the tree into a shape which we're going to be STUCK with for at least a year in the form of the monster which drains our energies: "-STABLE" We don't want to carry all this old stuff around for another year... That is why something had to happen, and it had to happen NOW, not after several weeks of fruitless flamefests in the mailing lists! -- 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 27 18:10:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07977 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:10:37 -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 SAA07958 for ; Sun, 27 Dec 1998 18:10:31 -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 MAA26220; Mon, 28 Dec 1998 12:39:46 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA29841; Mon, 28 Dec 1998 12:39:48 +1030 (CST) Message-ID: <19981228123948.D12346@freebie.lemis.com> Date: Mon, 28 Dec 1998 12:39:48 +1030 From: Greg Lehey To: Mike Smith , Christian Kuhtz Cc: "Jordan K. Hubbard" , FreeBSD current users Subject: Re: Thanks, Core Team References: <19981227205032.J1333@ns1.adsu.bellsouth.com> <199812280154.RAA06527@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812280154.RAA06527@dingo.cdrom.com>; from Mike Smith on Sun, Dec 27, 1998 at 05:54:02PM -0800 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 On Sunday, 27 December 1998 at 17:54:02 -0800, Mike Smith wrote: >> On Sun, Dec 27, 1998 at 05:45:37PM -0800, Jordan K. Hubbard wrote: >>>> 1. LKMs are gone. >>>> 2. This was decided by the core team. >>>> 3. Nobody else was informed. >>> >>> Actually, while some of the recent events came as much as a surprise >>> to core as anyone else, the transition from LKMs to KLD modules is not >>> and should not come as a surprise to anyone. We've been talking about >>> it for ages now in -current and the only way you could possibly fail >>> to be informed about this transition would be if you had simply >>> deleted every mail received from -current for at least the last 3 >>> months. >> >> And three months is considered to be a suitable transition period? With all >> due respect, give me a break. *hrmph* > > This was discussed at length for some time; and in Greg's case as one > of the LKM-laggers we've been trying to encourage him to switch for > some time, and that was in fact on the agenda before the jackboots > arrived. Now so far the discussion has been reasonable. But this is utter bullshit. Nobody has given me any warning that there was any pressing need to change. I keep all these messages, and what I have is: 15 August: You tell me that 3.0 will be using kld instead of lkm. 2 October: You send me an example. 9 October: Peter tells me (copying -current) that the code and tools are incomplete. Round the same time, he committed a number of fixes, but there was nothing to indicate that klds were ready for prime time. 2 December: You send a message, not copying me, explaining some details of how to perform the conversion to klds. No mention of urgency. And that's it. Do you have anything I've missed? Sure, I knew it was on the agenda, and if you had told me even three weeks ago, I wouldn't have complained. But it's not reasonable to wake up one morning and find LKMs dead and Vinum gone from the repository. > Three months is actually not at all unreasonable, especially given how > trivial the actual code changes required are. > >> If the old facility still works, why not leave both enabled? > > Because LKMs don't work for ELF kernels, and we should be making the > ELF kernel cutover before we branch. Which IIRC was slated for mid-January, as Jordan warned us (see, Jordan, I *do* read these things). > Again, this is something that should have been understood by the > folks following -current, although we haven't necessarily been > making enough loud noise about it to keep it a constant discussion > topic. Let me rephrase that: although we forgot to tell people that things were going to go away, and just removed them. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 18:11:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08008 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:11:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07993; Sun, 27 Dec 1998 18:11:04 -0800 (PST) (envelope-from psalzman@gamefish.pcola.gulf.net) Received: from localhost (psalzman@localhost) by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id UAA09898; Sun, 27 Dec 1998 20:06:33 -0600 (CST) (envelope-from psalzman@gamefish.pcola.gulf.net) Date: Sun, 27 Dec 1998 20:06:33 -0600 (CST) From: Phillip Salzman To: mwlucas@exceptionet.com cc: Poul-Henning Kamp , green@unixhelp.org, current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: <199812280018.TAA13827@easeway.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 I seem to remember IPFILTER being required for running a proxy server such as squid transparently, I could be mistaken though. If it is, why would something such as this be dumped from the tree -- some places need transparent proxy serving, do we really want to lose market share by making it confusing for them to set it up? -- Phillip Salzman On Sun, 27 Dec 1998 mwlucas@exceptionet.com wrote: > > >> IPFILTER > > > > > >Wasn't this _just_recently_ committed? Why commit it in the first place if > > >noone really wants it? Personally, I use IPFW. > > > > Yeah, the jury is still out on this one... Any users out there ? > > I occasionally use IPFilter. It's trivial to install from source, > however, provided that the user can follow instructions. > > ==ml > > -- > Michael Lucas | > Exceptionet, Inc. | www.exceptionet.com > "Exceptional Networking" | > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 18:12:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08109 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:12:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08103 for ; Sun, 27 Dec 1998 18:12:13 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id SAA16812; Sun, 27 Dec 1998 18:11:45 -0800 (PST) Date: Sun, 27 Dec 1998 18:11:45 -0800 (PST) From: "Steven P. Donegan" To: Mike Smith cc: "Jordan K. Hubbard" , Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team In-Reply-To: <199812280201.SAA06590@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 Sun, 27 Dec 1998, Mike Smith wrote: > > On Sun, 27 Dec 1998, Steven P. Donegan wrote: > > > > > > > > I read every email on this forum - the above statement is BS. > > > > Sorry to be short - my point was I have seen no discussion on committing > > this (major) change - some comments pro/con yes - doing it no. > > That makes more sense; I was going to point out that we've been > actively discussing the migration for months. The suddenness of the > cutover was indeed alarming, but all that was really missing was a > HEADS UP. > Sorry to be a bother - but I believe quite a few folks had negative comments on this transition, some still outstanding/unanswered. To me personally this will be a non-event, but to those folks it may be a problem. The only point I was making was that it was a significant change that didn't seem to have been talked out. No problem - I'll drop back to lurker mode and shut up now. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 18:12:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08124 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:12:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08118 for ; Sun, 27 Dec 1998 18:12:16 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA23822; Sun, 27 Dec 1998 21:11:52 -0500 (EST) Date: Sun, 27 Dec 1998 21:11:52 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Steven P. Donegan" cc: "Jordan K. Hubbard" , Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team 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, 27 Dec 1998, Steven P. Donegan wrote: > On Sun, 27 Dec 1998, Jordan K. Hubbard wrote: > > > > 1. LKMs are gone. > > > 2. This was decided by the core team. > > > 3. Nobody else was informed. > > > > Actually, while some of the recent events came as much as a surprise > > to core as anyone else, the transition from LKMs to KLD modules is not > > and should not come as a surprise to anyone. We've been talking about > > it for ages now in -current and the only way you could possibly fail > > to be informed about this transition would be if you had simply > > deleted every mail received from -current for at least the last 3 > > months. > > > > I read every email on this forum - the above statement is BS. > I don't know what YOU'VE been reading, but I've heard MANY times, from core members no less, that we'd be switching from LKM to KLD, for a long time. Ask Peter Wemm, he's been doing most of the work. Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 18:12:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08142 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:12:27 -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 SAA08134; Sun, 27 Dec 1998 18:12:21 -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 DAA71019; Mon, 28 Dec 1998 03:10:49 +0100 (CET) To: "Jordan K. Hubbard" cc: Christian Kuhtz , Gary Palmer , Kenneth Wayne Culver , Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team In-reply-to: Your message of "Sun, 27 Dec 1998 17:58:06 PST." <12586.914810286@zippy.cdrom.com> Date: Mon, 28 Dec 1998 03:10:49 +0100 Message-ID: <71017.914811049@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <12586.914810286@zippy.cdrom.com>, "Jordan K. Hubbard" writes: >> Not populating /lkm is sabotage. Regardless of the merits of kldm. > >Please explain the precise meaning if your statement. This strikes >me as just more ignorant speculation by someone who hasn't even bothered >to do a feature-by-feature comparison of /modules and the old /kld. Not to mention ever contributed anything to FreeBSD (-- that I can remember at least, correct me if I'm wrong!) -- 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 27 18:14:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08315 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:14:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08310 for ; Sun, 27 Dec 1998 18:14:49 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id VAA23188; Sun, 27 Dec 1998 21:13:58 -0500 (EST) Message-ID: <19981227211358.M1333@ns1.adsu.bellsouth.com> Date: Sun, 27 Dec 1998 21:13:58 -0500 From: Christian Kuhtz To: "Jordan K. Hubbard" Cc: Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team References: <19981227205032.J1333@ns1.adsu.bellsouth.com> <12680.914810913@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <12680.914810913@zippy.cdrom.com>; from Jordan K. Hubbard on Sun, Dec 27, 1998 at 06:08:33PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 27, 1998 at 06:08:33PM -0800, Jordan K. Hubbard wrote: > > And three months is considered to be a suitable transition period? With all > > due respect, give me a break. *hrmph* > > Again, I don't believe that the "transition" question here is > adequately understood by the parties arguing it and we're likely not > even having the same argument. As Gary has pointed out, old lkms will > continue to work and I'm still waiting for you to indicate just what > what in /lkm has not been adequately supplanted by /modules. I responded to some of the other emails in private, but.. Where is the info on how to convert from lkm to modules? Perhaps, assuming it is reasonably comprehensive and usable, this would 'entice' the bystanders who happen to be running current and have cycles left (pah, yeah right ;) to help move the code.. -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 18:19:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08506 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:19:22 -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 SAA08501 for ; Sun, 27 Dec 1998 18:19:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id SAA12839; Sun, 27 Dec 1998 18:18:44 -0800 (PST) To: Christian Kuhtz cc: Greg Lehey , FreeBSD current users Subject: Re: Thanks, Core Team In-reply-to: Your message of "Sun, 27 Dec 1998 21:13:58 EST." <19981227211358.M1333@ns1.adsu.bellsouth.com> Date: Sun, 27 Dec 1998 18:18:44 -0800 Message-ID: <12835.914811524@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Where is the info on how to convert from lkm to modules? Which lkm of yours are you trying to convert? - 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 27 18:21:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08721 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:21:23 -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 SAA08712 for ; Sun, 27 Dec 1998 18:21:18 -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 MAA26325; Mon, 28 Dec 1998 12:50:25 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA29860; Mon, 28 Dec 1998 12:50:19 +1030 (CST) Message-ID: <19981228125019.E12346@freebie.lemis.com> Date: Mon, 28 Dec 1998 12:50:19 +1030 From: Greg Lehey To: Poul-Henning Kamp , Steve Kargl Cc: "Jordan K. Hubbard" , FreeBSD-current@FreeBSD.ORG Subject: Re: Thanks, Core Team References: <199812280203.SAA15388@troutmask.apl.washington.edu> <70936.914810589@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <70936.914810589@critter.freebsd.dk>; from Poul-Henning Kamp on Mon, Dec 28, 1998 at 03:03:09AM +0100 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 On Monday, 28 December 1998 at 3:03:09 +0100, Poul-Henning Kamp wrote: > >> I was going to stay out of this, but this is bullshit. Soren >> and Poul are performing some major surgery such that a HEADS UP >> should have been given. I applaud their intentions, but abhor >> their method. > > Well, if people had a more civilized way with email, such as > considering carefully if the email adds anything of substance > or just clutter mailboxes, then maybe such a HEADS UP would > have a value. With the current level of communications skills > (as you can see right now!) on the list, a HEADS UP doesn't > accomplish anything productive. I'm sorry, this doesn't make any sense. The only lack of communication seems to have come from you. We regularly get ``heads up'' messages, most of which are presented correctly and thus work fine. We have this ``level of communication'' now because a large number of people feel that this significant change has been mismanaged. If you disagree, you should explain why you think the heads up would not be productive, bearing in mind that you will need to convince most readers of your opinion. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 18:21:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08751 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:21:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08738; Sun, 27 Dec 1998 18:21:30 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id MAA01260; Mon, 28 Dec 1998 12:51:11 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA12261; Mon, 28 Dec 1998 12:51:09 +1030 Date: Mon, 28 Dec 1998 12:51:07 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Poul-Henning Kamp Cc: Brian Feldman , current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: <68606.914783086@critter.freebsd.dk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Dec 1998, Poul-Henning Kamp wrote: > In message , Brian > Feldman writes: > >> IPFILTER > > > >Wasn't this _just_recently_ committed? Why commit it in the first place if > >noone really wants it? Personally, I use IPFW. > > Yeah, the jury is still out on this one... Any users out there ? I have been meaning to play around with it: IPFILTER has capabilities which ipfw does not have (the one in particular I'm thinking of is the ability to log packet contents). Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 18:26:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA08941 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:26:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA08936 for ; Sun, 27 Dec 1998 18:26:07 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA145550550; Sun, 27 Dec 1998 15:29:10 -0500 Date: Sun, 27 Dec 1998 15:29:10 -0500 (EST) From: Bill Fumerola To: Poul-Henning Kamp Cc: Greg Lehey , "Jordan K. Hubbard" , FreeBSD current users Subject: Re: Thanks, Core Team In-Reply-To: <70985.914810897@critter.freebsd.dk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Dec 1998, Poul-Henning Kamp wrote: > Notice my friends (and foes) that we have less than 3 weeks to get > the tree into a shape which we're going to be STUCK with for at least > a year in the form of the monster which drains our energies: "-STABLE" > > We don't want to carry all this old stuff around for another year... Vinum _is_ something we want to carry around. Deleting bitrotted drivers is noble, and I'm glad it happened before the branch. Deleting works in progress that have attracted users and added great functionality is not something that I would consider a step in the right direction. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 27 18:27:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09145 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:27:08 -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 SAA09140; Sun, 27 Dec 1998 18:27:00 -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 MAA26360; Mon, 28 Dec 1998 12:56:28 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA29884; Mon, 28 Dec 1998 12:56:31 +1030 (CST) Message-ID: <19981228125631.G12346@freebie.lemis.com> Date: Mon, 28 Dec 1998 12:56:31 +1030 From: Greg Lehey To: Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: LKMs References: <70843.914810131@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <70843.914810131@critter.freebsd.dk>; from Poul-Henning Kamp on Mon, Dec 28, 1998 at 02:55:31AM +0100 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 On Monday, 28 December 1998 at 2:55:31 +0100, Poul-Henning Kamp wrote: > > Greg: > > I think Soren was surprised by the fact that vinum sources lived > under src/lkm, they shouldn't have, in particular not because klds > were already on the way when vinum came in, but that aside, a > repository copy (as noted in the commit message) will put the > sources back in action the right place in the tree, and vinum will > be with us again. Correct. Maybe I should have made it clear that there was no intention of removing vinum permanently. But the lack of warning compounded the problem. And vinum came in before klds were in any really usable state (no kernel debug support, for example). I was expecting this change, and I do have a Vinum kld here, and with a bit more work I'll have it up and running, but it would have been nice to have a little warning (hell, even 2 days would have been enough). > Everybody: > > LKMs can still be loaded, we just don't produce any as part of make > world anymore, klds are the future in that respect. > > The flurry of emails we see here now is the very reason why so little > advance notice was given: It is impossible to delete anything from > the tree based on concensus. I wasn't asking for consensus, I was asking for forewarning. > We even had people complaining when we deleted some X.25 code > (because they had >dreamed about< being able to use it for!!) > > If at least people would read their >ENTIRE< mailbox before starting > to send more or less carefully thought out emails, things would be > a lot better around here, and maybe a more democratic process could > work. I don't know if you're referring to me here. But I certainly did read my mailbox. That's how I know there was no ``heads up'' message. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 18:27:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09192 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:27:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09183; Sun, 27 Dec 1998 18:27:43 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA24285; Sun, 27 Dec 1998 21:22:09 -0500 (EST) Date: Sun, 27 Dec 1998 21:22:09 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Phillip Salzman cc: mwlucas@exceptionet.com, Poul-Henning Kamp , current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: wanton Atticizing is bad 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, 27 Dec 1998, Phillip Salzman wrote: > > I seem to remember IPFILTER being required for running > a proxy server such as squid transparently, I could be > mistaken though. I don't see how THIS specific firewall/packet filter/packet forwarder/Salad Shooter is in any way rooted to a specific proxying/caching package such as Squid. With IPFIREWALL, IPFIREWALL_FORWARD, and IPDIVERT, I do not see how IPFILTER adds any new specific abilities (NOT configureabilites, core abilites) that aren't already here in ipfw form. > > If it is, why would something such as this be dumped from > the tree -- some places need transparent proxy serving, do > we really want to lose market share by making it confusing > for them to set it up? > > -- > Phillip Salzman > > > On Sun, 27 Dec 1998 mwlucas@exceptionet.com wrote: > > > > >> IPFILTER > > > > > > > >Wasn't this _just_recently_ committed? Why commit it in the first place if > > > >noone really wants it? Personally, I use IPFW. > > > > > > Yeah, the jury is still out on this one... Any users out there ? > > > > I occasionally use IPFilter. It's trivial to install from source, > > however, provided that the user can follow instructions. > > > > ==ml > > > > -- > > Michael Lucas | > > Exceptionet, Inc. | www.exceptionet.com > > "Exceptional Networking" | Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 18:29:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09275 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:29:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09269 for ; Sun, 27 Dec 1998 18:29:18 -0800 (PST) (envelope-from psalzman@gamefish.pcola.gulf.net) Received: from localhost (psalzman@localhost) by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id UAA10015; Sun, 27 Dec 1998 20:28:36 -0600 (CST) (envelope-from psalzman@gamefish.pcola.gulf.net) Date: Sun, 27 Dec 1998 20:28:36 -0600 (CST) From: Phillip Salzman To: Steve Kargl cc: "Jordan K. Hubbard" , grog@lemis.com, FreeBSD-current@FreeBSD.ORG Subject: Re: Thanks, Core Team In-Reply-To: <199812280203.SAA15388@troutmask.apl.washington.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 > > -- > Steve [Scrambling to deal with the deletion of Voxware on old hardware] > It is very relieving to know that Voxware has been replaced by an incomplete driver set that does not even support standard musical features such as MIDI. I remember some discussion about this in the past, where a certain core member said Voxware will stay in the kernel until it rotts. I would actually like to have seen that happen. Maybe someone should start a seperate archive of the Voxware drivers for FreeBSD. Maybe I will. -- Phillip Salzman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 18:33:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA09513 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:33:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA09508 for ; Sun, 27 Dec 1998 18:33:12 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA24653; Sun, 27 Dec 1998 21:32:46 -0500 (EST) Date: Sun, 27 Dec 1998 21:32:46 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Phillip Salzman cc: Steve Kargl , "Jordan K. Hubbard" , grog@lemis.com, FreeBSD-current@FreeBSD.ORG Subject: Re: Thanks, Core Team 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, 27 Dec 1998, Phillip Salzman wrote: > > > > -- > > Steve [Scrambling to deal with the deletion of Voxware on old hardware] > > > > It is very relieving to know that Voxware has been replaced > by an incomplete driver set that does not even support > standard musical features such as MIDI. > > I remember some discussion about this in the past, where a certain core > member said Voxware will stay in the kernel until it rotts. I would > actually like to have seen that happen. > > Maybe someone should start a seperate archive of the Voxware drivers > for FreeBSD. Maybe I will. I most certainly did NOT want VoxWare to leave, and volunteered to take over its' maintenance. However, from the reply I got, Poul must think I want to break VoxWare out into a separate OPL/3 driver. I want to keep the entire VoxWare package and maintain it. > > -- > Phillip Salzman > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 18:41:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10655 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:41:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10650 for ; Sun, 27 Dec 1998 18:41:06 -0800 (PST) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.9.1/8.9.1) id SAA15763; Sun, 27 Dec 1998 18:45:12 -0800 (PST) (envelope-from sgk) From: Steve Kargl Message-Id: <199812280245.SAA15763@troutmask.apl.washington.edu> Subject: Re: Thanks, Core Team In-Reply-To: <70936.914810589@critter.freebsd.dk> from Poul-Henning Kamp at "Dec 28, 1998 3: 3: 9 am" To: phk@critter.freebsd.dk (Poul-Henning Kamp) Date: Sun, 27 Dec 1998 18:45:12 -0800 (PST) Cc: jkh@zippy.cdrom.com, grog@lemis.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 According to Poul-Henning Kamp: > > >I was going to stay out of this, but this is bullshit. Soren > >and Poul are performing some major surgery such that a HEADS UP > >should have been given. I applaud their intentions, but abhor > >their method. > > Well, if people had a more civilized way with email, such as > considering carefully if the email adds anything of substance > or just clutter mailboxes, then maybe such a HEADS UP would > have a value. With the current level of communications skills > (as you can see right now!) on the list, a HEADS UP doesn't > accomplish anything productive. > I think the source tree reorganization is overdue. But, I also believe that everyone who uses FreeBSD respects the decisions of the core. To: freebsd-current@freebsd.org Subject: HEADS UP: source tree reorganization After lengthy discussion by core members, it has been decided that the source tree should be reorganized before the branching of 3.0-stable. To carry out these changes, the following are scheduled to be moved into the ATTIC: xxx, yyy, and zzz. The current time schedule severely limits the possibility of an overlong transition. THIS IS NOT OPEN TO DISCUSSION. THE CHANGES WILL START TO OCCUR ON 27 DEC 98. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~clesceri/kargl.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 18:43:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10777 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:43:14 -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 SAA10771 for ; Sun, 27 Dec 1998 18:43:12 -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 SAA49695; Sun, 27 Dec 1998 18:42:26 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812280242.SAA49695@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Feldman cc: FreeBSD-current@FreeBSD.ORG Subject: Re: Thanks, Core Team In-reply-to: Your message of "Sun, 27 Dec 1998 21:32:46 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Dec 1998 18:42:26 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Brian, Don't worry about the Voxware driver leaving the core source tree. What we do have to worry about is a different mechanism to support the driver for instance converting the driver to a kld module and a web server to distribute the voxware driver along with similar multimedia related kernel modules. At the very least the voxware driver will work for quite while on my system because I depend on its functionality. 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 27 18:48:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11046 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:48:09 -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 SAA10999; Sun, 27 Dec 1998 18:47:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id SAA12978; Sun, 27 Dec 1998 18:47:34 -0800 (PST) To: current@FreeBSD.ORG cc: committers@FreeBSD.ORG Subject: The recent fracas involving danes, war axes and wounded developers Date: Sun, 27 Dec 1998 18:47:34 -0800 Message-ID: <12974.914813254@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, clearly this has blown up into a problem which requires dealing with and so please consider this my attempt to at least communicate with all of you and put together some "behind the scenes" information for those who haven't had the benefit(?) of being on the core mailing alias over the last week. The chronology of this is as follows: pre-3.0-RELEASE: A decision is made to switch to KLD from KLM format modules just as soon as the kernel goes ELF, for various interoperability reasons and the fact that KLD modules are simply cleaner. Work is also undertaken to convert the existing LKMs to KLDs in the tree. 3.0-RELEASE "Yay" post-3.0-RELEASE I announce that the 3.0 branch will be created on Jan 15th. Dec 24th Poul-Henning asks whether or not now would be a good time to "clean up", before we actually do the branch and end up with duplicated garbage that needs to be thrown out twice. This seems a reasonable suggestion and a short list of potential candidates is floated before core and various items voted on. Dec 26th The Danes, grumbing about how it's always them who get the hangman's duty on account of the fact that they have their own axes, begin putting various things on the chopping block and cutting their bits off. Dec 27th Core notices that some of the items which have been beheaded during the night weren't actually on the list and that the Danes have chosen to add a few items of their own at the last minute. later that day.. All hell breaks loose as various developers wonder what the hell is going on and why no heads-up message was ever sent out. Core is also muttering about unauthorized assasinations and CIA operatives doing embarassing freelance work involving popular Bostonian presidents and such. So anyway, just to put the minds of those who might be thinking that core has suddenly suffered an attack of Josef Stalin disease ("I want the entire country taken out and shot") more at ease, let me just be the first to say that this was a cleanup expedition which was overcome by an excess of zeal and we apologise to any developers who suddenly felt their worlds crumbling underneath them. Even the most hardened members of core are not much pleased about how this was actually done and you may all rest assured that we've learned from this experience. - 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 27 18:49:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11247 for freebsd-current-outgoing; Sun, 27 Dec 1998 18:49:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11242 for ; Sun, 27 Dec 1998 18:49:44 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id SAA16934; Sun, 27 Dec 1998 18:49:26 -0800 (PST) Date: Sun, 27 Dec 1998 18:49:26 -0800 (PST) From: "Steven P. Donegan" To: Steve Kargl cc: Poul-Henning Kamp , jkh@zippy.cdrom.com, grog@lemis.com, FreeBSD-current@FreeBSD.ORG Subject: Re: Thanks, Core Team In-Reply-To: <199812280245.SAA15763@troutmask.apl.washington.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 This is the part I have heartburn about :-) > THIS IS NOT OPEN TO DISCUSSION. THE CHANGES WILL START TO OCCUR ON > 27 DEC 98. > And this seems to be the tude' behind the recent changes. I agree with the direction, but not the method. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 19:32:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13905 for freebsd-current-outgoing; Sun, 27 Dec 1998 19:32:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lohi.clinet.fi (lohi.clinet.fi [194.100.0.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13888; Sun, 27 Dec 1998 19:32:31 -0800 (PST) (envelope-from hsu@mail.clinet.fi) Received: from katiska.clinet.fi (katiska.clinet.fi [194.100.0.4]) by lohi.clinet.fi (8.9.1/8.9.0) with ESMTP id FAA05998; Mon, 28 Dec 1998 05:32:11 +0200 (EET) Received: (from hsu@localhost) by katiska.clinet.fi (8.9.0/8.9.0) id FAA10980; Mon, 28 Dec 1998 05:32:05 +0200 (EET) To: asami@FreeBSD.ORG (Satoshi Asami) Cc: freebsd-current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad References: <199812272253.OAA23572@bubble.didi.com.newsgate.clinet.fi> From: Heikki Suonsivu Date: 28 Dec 1998 05:32:03 +0200 In-Reply-To: asami@FreeBSD.ORG's message of 28 Dec 1998 01:11:54 +0200 Message-ID: Lines: 20 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG asami@FreeBSD.ORG (Satoshi Asami) writes: > * The cleanups have been discussed in -core. > > There was no agreement about pcvt. I do not mind removing pcvt *after* vt220 emulation is supported by syscons. I do mind it now, when there is no replacement for the functionality. Managing single-os-oddity terminal emulation in a large multios environment is a nightmare, and pcvt has been working fine, so there should be no reason for its removal. > Satoshi > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Heikki Suonsivu / Clinet Oy / Tekniikantie 12 / FI-02150 Espoo / FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 19:46:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15295 for freebsd-current-outgoing; Sun, 27 Dec 1998 19:46:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from as5200-01-254.no.neosoft.com (as5200-01-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA15290 for ; Sun, 27 Dec 1998 19:46:28 -0800 (PST) (envelope-from conrads@as5200-01-254.no.neosoft.com) Received: (from conrads@localhost) by as5200-01-254.no.neosoft.com (8.9.1/8.8.7) id VAA37869 for current@freebsd.org; Sun, 27 Dec 1998 21:45:35 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sun, 27 Dec 1998 21:45:35 -0600 (CST) Reply-To: conrads@neosoft.com From: Conrad Sabatier To: current@FreeBSD.ORG Subject: So we're stuck with using timidity now? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Here I am with an AWE 64 doing fabulous-sounding wavetable-based MIDI playback using the Voxware driver, and now I don't dare try to build a new kernel and be stuck with the (comparitively) rinky-dink sound of timidity. I certainly can appreciate the desire to clean up the system and have a single audio driver, but this represents a major loss of functionality (at least for now). Guess I'll have to rewrite (or maybe just trash altogether) the AWE setup tutorial I just put up on my web page the other day. Very disappointed here, to say the least. -- Conrad Sabatier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 19:53:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA15855 for freebsd-current-outgoing; Sun, 27 Dec 1998 19:53:24 -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 TAA15849 for ; Sun, 27 Dec 1998 19:53:22 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id TAA13228; Sun, 27 Dec 1998 19:52:58 -0800 (PST) To: conrads@neosoft.com cc: current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? In-reply-to: Your message of "Sun, 27 Dec 1998 21:45:35 CST." Date: Sun, 27 Dec 1998 19:52:58 -0800 Message-ID: <13225.914817178@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Here I am with an AWE 64 doing fabulous-sounding wavetable-based MIDI > playback using the Voxware driver, and now I don't dare try to build a new > kernel and be stuck with the (comparitively) rinky-dink sound of timidity. Don't jump to conclusions just yet. There's every possibility right now that both voxware and pcvt will be brought BACK from the dead, we just need to finish discussing this in core first before deciding what aspects of our recent bloodletting to try and rectify. - 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 27 19:54:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16139 for freebsd-current-outgoing; Sun, 27 Dec 1998 19:54:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16134 for ; Sun, 27 Dec 1998 19:54:11 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu ((IDENT root)@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id WAA07539; Sun, 27 Dec 1998 22:53:55 -0500 (EST) Received: from rac2.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id WAA00999; Sun, 27 Dec 1998 22:53:02 -0500 (EST) Received: from localhost by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id WAA00993; Sun, 27 Dec 1998 22:53:01 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Sun, 27 Dec 1998 22:53:01 -0500 (EST) From: Kenneth Wayne Culver To: Poul-Henning Kamp cc: Greg Lehey , "Jordan K. Hubbard" , FreeBSD current users Subject: Re: Thanks, Core Team In-Reply-To: <70985.914810897@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <19981228122531.C12346@freebie.lemis.com>, Greg Lehey writes: > >On Sunday, 27 December 1998 at 17:45:37 -0800, Jordan K. Hubbard wrote: > >>> 1. LKMs are gone. > >>> 2. This was decided by the core team. > >>> 3. Nobody else was informed. > >> > >> Actually, while some of the recent events came as much as a surprise > >> to core as anyone else, the transition from LKMs to KLD modules is not > >> and should not come as a surprise to anyone. We've been talking about > >> it for ages now in -current > > > >Sure, but that's not what I'm talking about. I've been gathering a > >lot of information about KLDs, and I've been meaning to move some > >time. But until this morning there was nothing to indicate that LKMs > >were going away in a hurry. It's interesting that recent events > >surprised you too, though. > > Notice my friends (and foes) that we have less than 3 weeks to get > the tree into a shape which we're going to be STUCK with for at least > a year in the form of the monster which drains our energies: "-STABLE" > > We don't want to carry all this old stuff around for another year... > > That is why something had to happen, and it had to happen NOW, not > after several weeks of fruitless flamefests in the mailing lists! > This is the _first_ good reason that I've seen for the "suddeness" of the change from LKMs to KLDs. I am personally happy as long as LKMs (such as Arla's afs client, or OSS/FreeBSD) can be loaded and used. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 20:02:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16646 for freebsd-current-outgoing; Sun, 27 Dec 1998 20:02:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA16641 for ; Sun, 27 Dec 1998 20:02:45 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu ((IDENT root)@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id XAA07757; Sun, 27 Dec 1998 23:03:05 -0500 (EST) Received: from rac2.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id XAA01627; Sun, 27 Dec 1998 23:02:13 -0500 (EST) Received: from localhost by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id XAA01622; Sun, 27 Dec 1998 23:02:11 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Sun, 27 Dec 1998 23:02:11 -0500 (EST) From: Kenneth Wayne Culver To: Phillip Salzman cc: Steve Kargl , "Jordan K. Hubbard" , grog@lemis.com, FreeBSD-current@FreeBSD.ORG Subject: Re: Thanks, Core Team 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 > > > > -- > > Steve [Scrambling to deal with the deletion of Voxware on old hardware] > > > > It is very relieving to know that Voxware has been replaced > by an incomplete driver set that does not even support > standard musical features such as MIDI. > > I remember some discussion about this in the past, where a certain core > member said Voxware will stay in the kernel until it rotts. I would > actually like to have seen that happen. > > Maybe someone should start a seperate archive of the Voxware drivers > for FreeBSD. Maybe I will. > Well, I personally think that someone should talk to Dev over at 4-front tech about developing an OSS/Free for FreeBSD (currently only available for Linux) and putting that in the source tree. OSS is what all the major sound apps require anyway. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 20:05:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16954 for freebsd-current-outgoing; Sun, 27 Dec 1998 20:05:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA16949 for ; Sun, 27 Dec 1998 20:05:39 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.9.1/8.9.1) with ESMTP id XAA22260; Sun, 27 Dec 1998 23:05:16 -0500 (EST) Date: Sun, 27 Dec 1998 23:05:16 -0500 (EST) From: jack To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? In-Reply-To: <13225.914817178@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 Sun, 27 Dec 1998, Jordan K. Hubbard wrote: > Don't jump to conclusions just yet. There's every possibility right > now that both voxware and pcvt will be brought BACK from the dead, we > just need to finish discussing this in core first before deciding what > aspects of our recent bloodletting to try and rectify. If lkms stay dead, share/examples/lkm and sys/i386/conf/LKM look like candidates for the Attic. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 20:09:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17278 for freebsd-current-outgoing; Sun, 27 Dec 1998 20:09:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17270 for ; Sun, 27 Dec 1998 20:09:17 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac2.wam.umd.edu ((IDENT root)@rac2.wam.umd.edu [128.8.10.142]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id XAA07877; Sun, 27 Dec 1998 23:09:50 -0500 (EST) Received: from rac2.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id XAA02284; Sun, 27 Dec 1998 23:08:57 -0500 (EST) Received: from localhost by rac2.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id XAA02277; Sun, 27 Dec 1998 23:08:56 -0500 (EST) X-Authentication-Warning: rac2.wam.umd.edu: culverk owned process doing -bs Date: Sun, 27 Dec 1998 23:08:56 -0500 (EST) From: Kenneth Wayne Culver To: Conrad Sabatier cc: current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? 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 > Here I am with an AWE 64 doing fabulous-sounding wavetable-based MIDI > playback using the Voxware driver, and now I don't dare try to build a new > kernel and be stuck with the (comparitively) rinky-dink sound of timidity. > > I certainly can appreciate the desire to clean up the system and have a > single audio driver, but this represents a major loss of functionality (at > least for now). > > Guess I'll have to rewrite (or maybe just trash altogether) the AWE setup > tutorial I just put up on my web page the other day. > Like I said before... Just use OSS/FreeBSD... It is better than VoxWare anyway. And with some talking to Dev at 4-front tech, I'm sure an agreement could be made. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 20:14:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17296 for freebsd-current-outgoing; Sun, 27 Dec 1998 20:09:22 -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 UAA17282 for ; Sun, 27 Dec 1998 20:09:20 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id UAA13350; Sun, 27 Dec 1998 20:08:44 -0800 (PST) To: Kenneth Wayne Culver cc: Phillip Salzman , Steve Kargl , grog@lemis.com, FreeBSD-current@FreeBSD.ORG Subject: Re: Thanks, Core Team In-reply-to: Your message of "Sun, 27 Dec 1998 23:02:11 EST." Date: Sun, 27 Dec 1998 20:08:43 -0800 Message-ID: <13346.914818123@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I personally think that someone should talk to Dev over at 4-front > tech about developing an OSS/Free for FreeBSD (currently only available I think they already have more than enough to do over there, and tracking our tree has historically been a pain in the ass for them. I'm certainly not going to be the one to listen to 5 minutes of Dev going "Hahahahahahahahahahahaha!" over the phone - be my most welcome guest, Kenneth! :-) - 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 27 20:29:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18542 for freebsd-current-outgoing; Sun, 27 Dec 1998 20:29:44 -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 UAA18533 for ; Sun, 27 Dec 1998 20:29:41 -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 OAA26845 for ; Mon, 28 Dec 1998 14:59:08 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id OAA30255; Mon, 28 Dec 1998 14:59:10 +1030 (CST) Message-ID: <19981228145909.R12346@freebie.lemis.com> Date: Mon, 28 Dec 1998 14:59:09 +1030 From: Greg Lehey To: FreeBSD current users Subject: How do I build an a.out kld? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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 I find I have to change to klds in a hurry, and have just run across a number of problems. I'm running an a.out kernel, which loads ELF klds quite happily (once you know that there's an undocumented search path, but that you can win by specifying a full pathname). The problem is that there are two versions of gdb, one of which recognizes only a.out (the kernel), and the other only ELF (the kld). I appear to have three choices: 1. I can build an ELF kernel. My understanding is that this will also require me to install the new style boot blocks. Correct? If so, is there any documentation on what to do here? 2. I could build an a.out kld. Unfortunately, there's an (undocumented) program called gensetdefs which runs against the objects, and expects only ELF files. It doesn't understand an -aout flag. Can I get past this problem? 3. I could fix gdb to understand both a.out and ELF formats, but I don't think I'll do it today. Any comments? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 20:32:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18963 for freebsd-current-outgoing; Sun, 27 Dec 1998 20:32:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18954 for ; Sun, 27 Dec 1998 20:32:40 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA191028413; Sun, 27 Dec 1998 17:40:13 -0500 Date: Sun, 27 Dec 1998 17:40:13 -0500 (EST) From: Bill Fumerola To: Kenneth Wayne Culver Cc: Conrad Sabatier , current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? 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, 27 Dec 1998, Kenneth Wayne Culver wrote: > Like I said before... Just use OSS/FreeBSD... It is better than VoxWare > anyway. And with some talking to Dev at 4-front tech, I'm sure an > agreement could be made. OSS is better. Better at panicing my system. Lets use the homegrown solutions before we start implementing a _known_ buggy module. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 27 20:34:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19201 for freebsd-current-outgoing; Sun, 27 Dec 1998 20:34:08 -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 UAA19196 for ; Sun, 27 Dec 1998 20:34:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id UAA14086; Sun, 27 Dec 1998 20:33:38 -0800 (PST) To: Greg Lehey cc: FreeBSD current users Subject: Re: How do I build an a.out kld? In-reply-to: Your message of "Mon, 28 Dec 1998 14:59:09 +1030." <19981228145909.R12346@freebie.lemis.com> Date: Sun, 27 Dec 1998 20:33:38 -0800 Message-ID: <14069.914819618@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1. I can build an ELF kernel. My understanding is that this will > also require me to install the new style boot blocks. Correct? > If so, is there any documentation on what to do here? Correct. 1. cd /sys/boot && make all install 2. disklabel -B da0 (or whatever your boot disk is). Make sure you're also running a -current disklabel. Set KERNFORMAT=elf in /etc/make.conf if you want to turn this on by default. - 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 27 21:05:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21212 for freebsd-current-outgoing; Sun, 27 Dec 1998 21:05:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA21186 for ; Sun, 27 Dec 1998 21:04:59 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu ((IDENT root)@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id AAA09450; Mon, 28 Dec 1998 00:05:27 -0500 (EST) Received: from rac1.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA24215; Mon, 28 Dec 1998 00:04:34 -0500 (EST) Received: from localhost by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA24210; Mon, 28 Dec 1998 00:04:33 -0500 (EST) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Mon, 28 Dec 1998 00:04:33 -0500 (EST) From: Kenneth Wayne Culver To: Bill Fumerola cc: freebsd-current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? 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 > > Like I said before... Just use OSS/FreeBSD... It is better than VoxWare > > anyway. And with some talking to Dev at 4-front tech, I'm sure an > > agreement could be made. > > OSS is better. Better at panicing my system. Lets use the homegrown > solutions before we start implementing a _known_ buggy module. Are you using the newest OSS? Also, Dev at 4-front tech has told me that the problem with his software panicing the kernel is because of problems with FreeBSD's virtual memory system. So do we need to fix that, or do we need to make Dev find a non-existant workaround (he has already looked for one)?? Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 21:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22498 for freebsd-current-outgoing; Sun, 27 Dec 1998 21:17:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22490 for ; Sun, 27 Dec 1998 21:17:19 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id NAA62868; Mon, 28 Dec 1998 13:16:40 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812280516.NAA62868@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: Greg Lehey , FreeBSD current users Subject: Re: How do I build an a.out kld? In-reply-to: Your message of "Sun, 27 Dec 1998 20:33:38 PST." <14069.914819618@zippy.cdrom.com> Date: Mon, 28 Dec 1998 13:16:39 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > 1. I can build an ELF kernel. My understanding is that this will > > also require me to install the new style boot blocks. Correct? > > If so, is there any documentation on what to do here? > > Correct. > > 1. cd /sys/boot && make all install > 2. disklabel -B da0 (or whatever your boot disk is). Not neccessarily necessary. :-) Just try typing: /boot/loader at the boot: prompt of your existing bootblocks. All things being equal, it should work. If it does, and your bootblocks are new enough to know about /boot.config, you can tell the bootblocks to load the /boot/loader ``kernel'' instead. :-) Apparently, the older 2.1 and maybe 2.2.[12] bootblocks don't like the /boot/loader for some reason - I'd like to know why so this can be fixed. Any ideas anyone? :-) When you get to the loader, you have a command prompt. You can do things like this: boot /kernel # load and start /kernel boot /kernel.old -s # load /kernel.old and start it in single user load kernel # load /kernel load vinum # then load /modules/vinum.ko boot -s # then start in single user. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 21:18:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22641 for freebsd-current-outgoing; Sun, 27 Dec 1998 21:18:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22634 for ; Sun, 27 Dec 1998 21:18:26 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id NAA62889; Mon, 28 Dec 1998 13:17:47 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812280517.NAA62889@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Kenneth Wayne Culver cc: Bill Fumerola , freebsd-current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? In-reply-to: Your message of "Mon, 28 Dec 1998 00:04:33 EST." Date: Mon, 28 Dec 1998 13:17:47 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kenneth Wayne Culver wrote: > > > Like I said before... Just use OSS/FreeBSD... It is better than VoxWare > > > anyway. And with some talking to Dev at 4-front tech, I'm sure an > > > agreement could be made. > > > > OSS is better. Better at panicing my system. Lets use the homegrown > > solutions before we start implementing a _known_ buggy module. > > Are you using the newest OSS? Also, Dev at 4-front tech has told me that > the problem with his software panicing the kernel is because of problems > with FreeBSD's virtual memory system. So do we need to fix that, or do we > need to make Dev find a non-existant workaround (he has already looked for > one)?? I think that problem has been fixed, a month or two ago. contigmalloc() was doing some silly things. > Kenneth Culver Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 21:22:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23049 for freebsd-current-outgoing; Sun, 27 Dec 1998 21:22:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23043 for ; Sun, 27 Dec 1998 21:22:34 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id AAA00425; Mon, 28 Dec 1998 00:17:11 -0500 (EST) Date: Mon, 28 Dec 1998 00:17:10 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Kenneth Wayne Culver cc: Poul-Henning Kamp , Greg Lehey , "Jordan K. Hubbard" , FreeBSD current users Subject: Re: Thanks, Core Team 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, 27 Dec 1998, Kenneth Wayne Culver wrote: > > In message <19981228122531.C12346@freebie.lemis.com>, Greg Lehey writes: > > >On Sunday, 27 December 1998 at 17:45:37 -0800, Jordan K. Hubbard wrote: > > >>> 1. LKMs are gone. > > >>> 2. This was decided by the core team. > > >>> 3. Nobody else was informed. > > >> > > >> Actually, while some of the recent events came as much as a surprise > > >> to core as anyone else, the transition from LKMs to KLD modules is not > > >> and should not come as a surprise to anyone. We've been talking about > > >> it for ages now in -current > > > > > >Sure, but that's not what I'm talking about. I've been gathering a > > >lot of information about KLDs, and I've been meaning to move some > > >time. But until this morning there was nothing to indicate that LKMs > > >were going away in a hurry. It's interesting that recent events > > >surprised you too, though. > > > > Notice my friends (and foes) that we have less than 3 weeks to get > > the tree into a shape which we're going to be STUCK with for at least > > a year in the form of the monster which drains our energies: "-STABLE" > > > > We don't want to carry all this old stuff around for another year... > > > > That is why something had to happen, and it had to happen NOW, not > > after several weeks of fruitless flamefests in the mailing lists! > > > This is the _first_ good reason that I've seen for the "suddeness" of the > change from LKMs to KLDs. I am personally happy as long as LKMs (such as > Arla's afs client, or OSS/FreeBSD) can be loaded and used. The truth is, they CAN be loaded and used PROVIDED you are using an a.out kernel. LKMs work using ld magic to relink the object file, the kernel, etc. and ioctl it on into the kernel, basically. It's strongly tied to a.out, and there's no reason at all to ever make LKMs ELFable, since KLDs already work, and work well for ELF and a.out, requiring no black magic of ld and /dev/lkm, just a simple int kldload(char *ko) syscall. LKMs die now, especially since 3.0.1 will by default (I'm pretty sure) have an ELF kernel. > > Kenneth Culver > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 27 21:23:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23119 for freebsd-current-outgoing; Sun, 27 Dec 1998 21:23:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23114 for ; Sun, 27 Dec 1998 21:23:41 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu ((IDENT root)@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id AAA09818; Mon, 28 Dec 1998 00:23:30 -0500 (EST) Received: from rac1.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA25100; Mon, 28 Dec 1998 00:22:37 -0500 (EST) Received: from localhost by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA25095; Mon, 28 Dec 1998 00:22:36 -0500 (EST) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Mon, 28 Dec 1998 00:22:36 -0500 (EST) From: Kenneth Wayne Culver To: Brian Feldman cc: Poul-Henning Kamp , Greg Lehey , "Jordan K. Hubbard" , FreeBSD current users Subject: Re: Thanks, Core Team 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 > > > > In message <19981228122531.C12346@freebie.lemis.com>, Greg Lehey writes: > > > >On Sunday, 27 December 1998 at 17:45:37 -0800, Jordan K. Hubbard wrote: > > > >>> 1. LKMs are gone. > > > >>> 2. This was decided by the core team. > > > >>> 3. Nobody else was informed. > > > >> > > > >> Actually, while some of the recent events came as much as a surprise > > > >> to core as anyone else, the transition from LKMs to KLD modules is not > > > >> and should not come as a surprise to anyone. We've been talking about > > > >> it for ages now in -current > > > > > > > >Sure, but that's not what I'm talking about. I've been gathering a > > > >lot of information about KLDs, and I've been meaning to move some > > > >time. But until this morning there was nothing to indicate that LKMs > > > >were going away in a hurry. It's interesting that recent events > > > >surprised you too, though. > > > > > > Notice my friends (and foes) that we have less than 3 weeks to get > > > the tree into a shape which we're going to be STUCK with for at least > > > a year in the form of the monster which drains our energies: "-STABLE" > > > > > > We don't want to carry all this old stuff around for another year... > > > > > > That is why something had to happen, and it had to happen NOW, not > > > after several weeks of fruitless flamefests in the mailing lists! > > > > > This is the _first_ good reason that I've seen for the "suddeness" of the > > change from LKMs to KLDs. I am personally happy as long as LKMs (such as > > Arla's afs client, or OSS/FreeBSD) can be loaded and used. > > The truth is, they CAN be loaded and used PROVIDED you are using an a.out > kernel. LKMs work using ld magic to relink the object file, the kernel, etc. > and ioctl it on into the kernel, basically. It's strongly tied to a.out, and > there's no reason at all to ever make LKMs ELFable, since KLDs already work, > and work well for ELF and a.out, requiring no black magic of ld and /dev/lkm, > just a simple int kldload(char *ko) syscall. LKMs die now, especially since > 3.0.1 will by default (I'm pretty sure) have an ELF kernel. That is cool, I understand that perfectly, I just wanted to make sure that for the time being, my OSS and AFS will work until the respective developers have time to re-develop their software to work with the new setup. Kenneth culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 21:26:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA23314 for freebsd-current-outgoing; Sun, 27 Dec 1998 21:26:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA23309 for ; Sun, 27 Dec 1998 21:26:09 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu ((IDENT root)@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id AAA03866; Mon, 28 Dec 1998 00:25:38 -0500 (EST) Received: from rac1.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA25120; Mon, 28 Dec 1998 00:25:37 -0500 (EST) Received: from localhost by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA25115; Mon, 28 Dec 1998 00:25:36 -0500 (EST) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Mon, 28 Dec 1998 00:25:35 -0500 (EST) From: Kenneth Wayne Culver To: Peter Wemm cc: Bill Fumerola , freebsd-current@FreeBSD.ORG Subject: Re: So we're stuck with using timidity now? In-Reply-To: <199812280517.NAA62889@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > anyway. And with some talking to Dev at 4-front tech, I'm sure an > > > > agreement could be made. > > > > > > OSS is better. Better at panicing my system. Lets use the homegrown > > > solutions before we start implementing a _known_ buggy module. > > > > Are you using the newest OSS? Also, Dev at 4-front tech has told me that > > the problem with his software panicing the kernel is because of problems > > with FreeBSD's virtual memory system. So do we need to fix that, or do we > > need to make Dev find a non-existant workaround (he has already looked for > > one)?? > > I think that problem has been fixed, a month or two ago. contigmalloc() > was doing some silly things. Yeah, I think I was one of the ones that helped with that. However, there are other problems, and Dev says they are not his. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 21:39:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24449 for freebsd-current-outgoing; Sun, 27 Dec 1998 21:39:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA24433 for ; Sun, 27 Dec 1998 21:39:34 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id WAA22644 for ; Sun, 27 Dec 1998 22:42:42 -0700 (MST) Message-Id: <199812280542.WAA22644@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Sun, 27 Dec 1998 18:20:00 +0100." <68199.914779200@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 27 Dec 1998 22:42:42 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, My 2cents worth: I use /dev/speaker on many small machines that have no sound card, its very useful for getting someone's attention at the end of a job. Please keep it. Voxware should come back, or at least be made a port. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Dec 27 22:15:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA27327 for freebsd-current-outgoing; Sun, 27 Dec 1998 22:15:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [36.118.0.70]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA27322 for ; Sun, 27 Dec 1998 22:15:37 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.1a/8.9.1) id WAA02984; Sun, 27 Dec 1998 22:15:12 -0800 (PST) Date: Sun, 27 Dec 1998 22:15:12 -0800 (PST) From: Bob Vaughan Message-Id: <199812280615.WAA02984@tantivy.stanford.edu> To: donegan@quick.net, sgk@troutmask.apl.washington.edu Subject: Re: Thanks, Core Team Cc: FreeBSD-current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok.. I'll jump into this fray.. I'd like to see a summary of the following: what has been removed (or is scheduled to be removed) what replacement is available (or not) -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 00:11:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05532 for freebsd-current-outgoing; Mon, 28 Dec 1998 00:11:24 -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 AAA05527 for ; Mon, 28 Dec 1998 00:11:22 -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 DAA06517 for ; Mon, 28 Dec 1998 03:10:58 -0500 (EST) Date: Mon, 28 Dec 1998 03:10:39 -0500 From: Matt White To: freebsd-current@FreeBSD.ORG Subject: Re: PPTP and FreeBSD Message-ID: <4281573128.914814639@DEIMOS.REM.CMU.EDU> In-Reply-To: <199812272119.QAA13600@o2.cs.rpi.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 L2TP is much the same way. The reason for this is that these protocols are not really designed for what we are using them for. Both PPTP and L2TP are ways of tunneling traffic received from a client by an ISP's remote access device back to a corporate network. There is only one control connection per corporate network endpoint. This has the advantage that the end user doesn't have to set anything up on their computer to take advantage of the tunneling...it is done automatically by the RAS. The difficulty is, of course, that arrangements for these tunnels must be made at all possible access points so I wonder how much L2TP is actually ever going to be used as intended. As far as the amount of work required to implement L2TP or PPTP, I'm not sure about how bad it would be. Keep in mind that a good portion of both of these protocols are implemented elsewhere. It might be more of an issue of sewing the right modules together. Not that I'm going to spend the time to do it. My personal feeling is that VPNs are evil and yet another excuse to not properly secure one's systems (firewalls being the last excuse). -Matt --On Sunday, December 27, 1998, 4:19 PM -0500 "David E. Cross" wrote: >> Regardless, we would like a PPTP server running under >> FreeBSD/Linux/Solaris at this site because we subscribe to a number of >> services that do security by IP address. Our desire would be more to be >> able to assign IPs from our address space to roaming users. > > I had looked into this at the past, and read the relavent RFCs and MS > documentation on it. It is a bad joke, all the way arround. First it > uses a modified version of the GRE protocol (that is why I asked about > GRE support in the kernel way back when), as an encapsulation around the > PPP packets. It also must have a TCP connection between the client and > the server to act as a controll connection. If that control connection > is lost for whatever reason , the tunel is closed. Oh yes, one last > thing, the GRE portion of the tunel, where the data actually goes, has an > ack/nak, sliding window and retransmit system (again, outlined in the MS > documentation). While I think this would be a good thing to have, just > to be compatible, and ideally as a part of a larger 'iptunel' packagel; > it is *alot* of work. > > -- > David Cross > > > 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 28 00:27:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06543 for freebsd-current-outgoing; Mon, 28 Dec 1998 00:27:11 -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 AAA06536 for ; Mon, 28 Dec 1998 00:27:02 -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 KAA27990; Mon, 28 Dec 1998 10:26:30 +0200 (EET) Received: (from vallo@localhost) by myhakas.matti.ee (8.9.1/8.9.1) id KAA02644; Mon, 28 Dec 1998 10:26:31 +0200 (EET) (envelope-from vallo) Message-ID: <19981228102631.B2468@matti.ee> Date: Mon, 28 Dec 1998 10:26:31 +0200 From: Vallo Kallaste To: Mike Smith Cc: FreeBSD current users Subject: Re: Thanks, Core Team Reply-To: vallo@matti.ee References: <19981227205032.J1333@ns1.adsu.bellsouth.com> <199812280154.RAA06527@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812280154.RAA06527@dingo.cdrom.com>; from Mike Smith on Sun, Dec 27, 1998 at 05:54:02PM -0800 Organization: =?iso-8859-1?Q?AS_Matti_B=FCrootehnika?= Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 27, 1998 at 05:54:02PM -0800, Mike Smith wrote: > should have been understood by the folks following -current, although > we haven't necessarily been making enough loud noise about it to keep > it a constant discussion topic. Probably. I haven't seen any HEADS UP like message recently. I suspect that's a official way to warn users before making major changes. Personally I track messages like this very carefully, but it's possible to forget, thought, as I don't have an automated procedure for tracking. 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 Mon Dec 28 00:40:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07261 for freebsd-current-outgoing; Mon, 28 Dec 1998 00:40:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from scotty.masternet.it (scotty.masternet.it [194.184.65.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA07256 for ; Mon, 28 Dec 1998 00:39:56 -0800 (PST) (envelope-from gmarco@scotty.masternet.it) Received: from suzy (modem00.masternet.it [194.184.65.10]) by scotty.masternet.it (8.8.8/8.8.8) with SMTP id JAA12236 for ; Mon, 28 Dec 1998 09:39:38 +0100 (CET) (envelope-from gmarco@scotty.masternet.it) Message-Id: <199812280839.JAA12236@scotty.masternet.it> From: "Gianmarco Giovannelli" To: current@FreeBSD.ORG Date: Thu, 28 Jan 1999 09:47:45 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: wanton Atticizing is bad Reply-to: gmarco@giovannelli.it References: In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I seem to remember IPFILTER being required for running > > a proxy server such as squid transparently, I could be > > mistaken though. Here it is : transproxy-0.3, transparent www proxy driver for IPFILTER (NOT ipfw!!) "transproxy - transparently proxy HTTP and other requests. This program is used with Darren Reed's IPFILTER package and used to intercept things like http requests and divert them to a www proxy server (eg: squid), without requiring user intervention or configuration." Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 01:10:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09809 for freebsd-current-outgoing; Mon, 28 Dec 1998 01:10:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from www.giovannelli.it (www.giovannelli.it [194.184.65.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09802 for ; Mon, 28 Dec 1998 01:10:42 -0800 (PST) (envelope-from gmarco@giovannelli.it) Received: from suzy (modem00.masternet.it [194.184.65.10]) by www.giovannelli.it (8.8.8/8.8.5) with SMTP id KAA02316 for ; Mon, 28 Dec 1998 10:10:20 +0100 (MET) Message-Id: <199812280910.KAA02316@www.giovannelli.it> From: "Gianmarco Giovannelli" To: current@FreeBSD.ORG Date: Thu, 28 Jan 1999 10:18:30 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: So we're stuck with using timidity now? Reply-to: gmarco@giovannelli.it In-reply-to: <199812280517.NAA62889@spinner.netplex.com.au> References: Your message of "Mon, 28 Dec 1998 00:04:33 EST." X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kenneth Wayne Culver wrote: > > > > Like I said before... Just use OSS/FreeBSD... It is better than VoxWare > > > > anyway. And with some talking to Dev at 4-front tech, I'm sure an > > > > agreement could be made. > > > > > > OSS is better. Better at panicing my system. Lets use the homegrown > > > solutions before we start implementing a _known_ buggy module. I am a registred users of OSS, which I use on a box. On others boxes I use Voxware and Luigi's one. The problem of an average FreeBSD user is he doesn't have a sound driver that has everything he need. One driver lacks midi support (luigi), another that has midi support (oss) fails in linux emulation (i.e. you play Quake2 without no sound at all) and so on... Thanks for attention. Best Regards, Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) "Unix expert since yesterday" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 01:13:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA09997 for freebsd-current-outgoing; Mon, 28 Dec 1998 01:13:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA09991 for ; Mon, 28 Dec 1998 01:13:39 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id RAA64069; Mon, 28 Dec 1998 17:12:46 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812280912.RAA64069@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: gmarco@giovannelli.it cc: current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Thu, 28 Jan 1999 09:47:45 +0100." <199812280839.JAA12236@scotty.masternet.it> Date: Mon, 28 Dec 1998 17:12:44 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Gianmarco Giovannelli" wrote: > > > > I seem to remember IPFILTER being required for running > > > a proxy server such as squid transparently, I could be > > > mistaken though. > > Here it is : > > transproxy-0.3, transparent www proxy driver for IPFILTER (NOT ipfw!!) > > "transproxy - transparently proxy HTTP and other requests. > This program is used with Darren Reed's IPFILTER package and used > to intercept things like http requests and divert them to a www proxy server > (eg: squid), without requiring user intervention or configuration." ipfw supports this functionality natively now. transproxy and squid require special IPFILTER patches, while both work with ipfw without special support. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 02:02:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12851 for freebsd-current-outgoing; Mon, 28 Dec 1998 02:02:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA12846 for ; Mon, 28 Dec 1998 02:02:38 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (1727 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Mon, 28 Dec 1998 11:02:04 +0100 (MET) (Smail-3.2.0.101 1997-Dec-17 #2 built 1998-Jun-26) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m0zuZYC-00001KC; Mon, 28 Dec 98 11:05 MET Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: future of syscons In-Reply-To: <199812241256.VAA06222@zodiac.mech.utsunomiya-u.ac.jp> from Kazutaka YOKOTA at "Dec 24, 98 09:55:01 pm" To: yokota@zodiac.mech.utsunomiya-u.ac.jp (Kazutaka YOKOTA) Date: Mon, 28 Dec 1998 11:05:23 +0100 (MET) Cc: hm@hcs.de, mike@smith.net.au, current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (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 >From the keyboard of Kazutaka YOKOTA: > Not much has been designed or decided about terminal emulation code > yet. I have just a vague idea that the terminal emulator code shall > write to the vty's internal buffer, rather than directly to the > screen, and a timer routine will periodically render it to screen. > > Let's work together in designing this, shall we? Yes, i'd like to participate in this effort to be able to move the pcvt functionality to this new design! hellmuth -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 02:20:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14429 for freebsd-current-outgoing; Mon, 28 Dec 1998 02:20:13 -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 CAA14424 for ; Mon, 28 Dec 1998 02:20:11 -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 JAA11969; Mon, 28 Dec 1998 09:09:29 +0100 From: Luigi Rizzo Message-Id: <199812280809.JAA11969@labinfo.iet.unipi.it> Subject: Re: So we're stuck with using timidity now? To: gmarco@giovannelli.it Date: Mon, 28 Dec 1998 09:09:28 +0100 (MET) Cc: current@FreeBSD.ORG In-Reply-To: <199812280910.KAA02316@www.giovannelli.it> from "Gianmarco Giovannelli" at Jan 28, 99 10:18:11 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem of an average FreeBSD user is he doesn't have a sound driver > that has everything he need. the problem of an average human being is he doesn't have everything (health, money, free time...) he needs. Unfortunately pointing out well known problems does not solve them. cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 02:22:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA14816 for freebsd-current-outgoing; Mon, 28 Dec 1998 02:22:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA14807 for ; Mon, 28 Dec 1998 02:22:12 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id LAA53350; Mon, 28 Dec 1998 11:21:23 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199812281021.LAA53350@freebsd.dk> Subject: Re: future of syscons In-Reply-To: from Hellmuth Michaelis at "Dec 28, 1998 11: 5:23 am" To: hm@hcs.de Date: Mon, 28 Dec 1998 11:21:23 +0100 (CET) Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp, hm@hcs.de, mike@smith.net.au, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Hellmuth Michaelis wrote: > >From the keyboard of Kazutaka YOKOTA: > > > Not much has been designed or decided about terminal emulation code > > yet. I have just a vague idea that the terminal emulator code shall > > write to the vty's internal buffer, rather than directly to the > > screen, and a timer routine will periodically render it to screen. > > > > Let's work together in designing this, shall we? > > Yes, i'd like to participate in this effort to be able to move the pcvt > functionality to this new design! Great, I'm very glad to hear that, and welcome in the comitter team !! -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 02:46:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16015 for freebsd-current-outgoing; Mon, 28 Dec 1998 02:46:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA16004 for ; Mon, 28 Dec 1998 02:46:05 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id SAA64604; Mon, 28 Dec 1998 18:42:42 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812281042.SAA64604@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Soren Schmidt cc: hm@hcs.de, yokota@zodiac.mech.utsunomiya-u.ac.jp, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: future of syscons In-reply-to: Your message of "Mon, 28 Dec 1998 11:21:23 +0100." <199812281021.LAA53350@freebsd.dk> Content-Transfer-Encoding: quoted-printable Date: Mon, 28 Dec 1998 18:42:41 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Soren Schmidt wrote: > It seems Hellmuth Michaelis wrote: > > >From the keyboard of Kazutaka YOKOTA: > > = > > > Not much has been designed or decided about terminal emulation code= > > > yet. I have just a vague idea that the terminal emulator code shal= l > > > write to the vty's internal buffer, rather than directly to the > > > screen, and a timer routine will periodically render it to screen. > > > = > > > Let's work together in designing this, shall we? > > = > > Yes, i'd like to participate in this effort to be able to move the pc= vt > > functionality to this new design! > = > Great, I'm very glad to hear that, and welcome in the comitter team !! Hey, this sounds rather interesting! :-) This sounds like a mini curses-like arrangement, except that there is no = need for cursor move optimization. What would make it really *really* interesting would be if it were = possible to mmap() the virtual buffer and draw directly into it from user= = mode, thus bypassing terminal emulation altogether... Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 02:53:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA16533 for freebsd-current-outgoing; Mon, 28 Dec 1998 02:53:26 -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 ESMTP id CAA16526 for ; Mon, 28 Dec 1998 02:53:21 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id LAA28035; Mon, 28 Dec 1998 11:48:15 +0100 (MET) Message-ID: <368761EF.23641D79@we.lc.ehu.es> Date: Mon, 28 Dec 1998 11:48:15 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. de Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Nicolas Souchu CC: Stephen Palmer , gp@oitunix.oit.umass.edu, freebsd-current@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] References: <19981219130349.11043.qmail@www0f.netaddress.usa.net> <367E88FB.B9F0D79@we.lc.ehu.es> <19981222010450.23781@breizh.prism.uvsq.fr> <368171FF.B8A5B268@we.lc.ehu.es> <19981224181948.61645@breizh.prism.uvsq.fr> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Souchu wrote: > > Sorry, I'm wrong, it's ok here with December, 22th. So I can't really > help you from there :( > > You may retry previous sys/ releases Dec, 1st, Nov, 15th to find out the bogus > submit. > Parallel ZIP doesn't work here, using sources CVSupped today (Dec 28th). Perhaps the cause isn't in the ppc/ppbus/vpo code; the problem I see is that da0 isn't initialized, so I think that scbus0 doesn't get attached to vpo0 for some reason. Some parts of the CAM code have changed in the last month... These are my kernel config lines related to the parallel bus: controller scbus0 # Lo necesita el ZIP paralelo. device da0 # Y esto también. controller ppbus0 # Bus paralelo controller vpo0 at ppbus? # ZIP paralelo device nlpt0 at ppbus? # Impresora controller ppc0 at isa? port ? tty irq 7 flags 0x04 I think that this config is OK. I have no SCSI adapter in this machine. These are the boot messages (boot -v): ppc: parallel port found at 0x378 ppc0: ppc0 at 0x378 irq 7 flags 0x4 on isa ppc0: Generic chipset (EPP-only) in EPP mode (EPP 1.9) nlpt0: on ppbus 0 nlpt0: Interrupt-driven port vpo0: on ppbus 0 vpo0: EPP 1.9 mode After that, there is no mention to any "da" device. This is very odd, indeed. -- 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 Mon Dec 28 03:13:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18518 for freebsd-current-outgoing; Mon, 28 Dec 1998 03:13:50 -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 DAA18513 for ; Mon, 28 Dec 1998 03:13:47 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id KAA03237; Mon, 28 Dec 1998 10:45:56 GMT Date: Mon, 28 Dec 1998 10:45:56 +0000 (GMT) From: Doug Rabson To: Greg Lehey cc: FreeBSD current users Subject: Re: How do I build an a.out kld? In-Reply-To: <19981228145909.R12346@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 On Mon, 28 Dec 1998, Greg Lehey wrote: > I find I have to change to klds in a hurry, and have just run across a > number of problems. I'm running an a.out kernel, which loads ELF klds > quite happily (once you know that there's an undocumented search path, > but that you can win by specifying a full pathname). The problem is > that there are two versions of gdb, one of which recognizes only a.out > (the kernel), and the other only ELF (the kld). I appear to have > three choices: > > 1. I can build an ELF kernel. My understanding is that this will > also require me to install the new style boot blocks. Correct? > If so, is there any documentation on what to do here? Mostly. If you have fairly recent boot blocks, you can try typing '/boot/loader' to your existing bootblocks which should leave you in the third stage boot. > > 2. I could build an a.out kld. Unfortunately, there's an > (undocumented) program called gensetdefs which runs against the > objects, and expects only ELF files. It doesn't understand an > -aout flag. Can I get past this problem? Are you using bsd.kmod.mk? If you look at it, gensetdefs is only used for elf. Linking an a.out module is even simpler: ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} ${OBJS} ${KMODDEPS} Try 'make OBJFORMAT=aout' and see what happens. > > 3. I could fix gdb to understand both a.out and ELF formats, but I > don't think I'll do it today. I looked at this when I made it work for ELF and it was going to be hard to support both elf and a.out shared libs. Its easy to build an a.out gdb and keep it around for odd jobs which require a.out support. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 03:45:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21265 for freebsd-current-outgoing; Mon, 28 Dec 1998 03:45:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21255 for ; Mon, 28 Dec 1998 03:45:41 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id TAA65000; Mon, 28 Dec 1998 19:45:00 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812281145.TAA65000@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Doug Rabson cc: Greg Lehey , FreeBSD current users Subject: Re: How do I build an a.out kld? In-reply-to: Your message of "Mon, 28 Dec 1998 10:45:56 GMT." Date: Mon, 28 Dec 1998 19:44:59 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Rabson wrote: > On Mon, 28 Dec 1998, Greg Lehey wrote: [..] > > 2. I could build an a.out kld. Unfortunately, there's an > > (undocumented) program called gensetdefs which runs against the > > objects, and expects only ELF files. It doesn't understand an > > -aout flag. Can I get past this problem? > > Are you using bsd.kmod.mk? If you look at it, gensetdefs is only used for > elf. Linking an a.out module is even simpler: > > ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} ${OBJS} ${KMODDEPS} > > Try 'make OBJFORMAT=aout' and see what happens. Err, my recollection was that it needed to be in the environment, ie more like: env OBJFORMAT=aout make Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 03:49:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21475 for freebsd-current-outgoing; Mon, 28 Dec 1998 03:49:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ice.cold.org (cold.org [206.81.134.103]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21462 for ; Mon, 28 Dec 1998 03:49:12 -0800 (PST) (envelope-from brandon@ice.cold.org) Received: (from root@localhost) by ice.cold.org (8.8.8/8.8.5) id EAA00711; Mon, 28 Dec 1998 04:48:56 -0700 (MST) Date: Mon, 28 Dec 1998 04:48:56 -0700 (MST) Message-Id: <199812281148.EAA00711@ice.cold.org> Subject: ERRATA NOTICE: FreeBSD 3.0-RELEASE From: freebsd-errata-update@roguetrader.com To: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ****************************************************************** ** THIS IS AN AUTOMATIC ERRATA UPDATE FOR FREEBSD 3.0-RELEASE ** ****************************************************************** You can retrieve the complete ERRATA from: ftp://ftp.freebsd.org/pub/FreeBSD/3.0-RELEASE/ERRATA.TXT The last update was sent: Mon Dec 28 04:45:51 1998 This update is sent: Mon Dec 28 04:48:56 1998 ------------------------------------------------------------------ ---- SYSTEM ERRATA INFORMATION: o The GPL_MATH_EMULATE kernel option causes a fatal trap during system startup. Fix: Replace the GPL_MATH_EMULATE option with the default math emulation option MATH_EMULATE. This will only affect users who have modified their kernel configuration file. The problem is corrected in revision 1.16 of the file /usr/src/sys/gnu/i386/fpemul/fpu_entry.c. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 04:07:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25097 for freebsd-current-outgoing; Mon, 28 Dec 1998 04:07:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from idefix.omnix.net (idefix.omnix.net [194.183.217.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25092 for ; Mon, 28 Dec 1998 04:07:23 -0800 (PST) (envelope-from didier@omnix.net) Received: from localhost (localhost [127.0.0.1]) by idefix.omnix.net (Postfix) with SMTP id 4AC785D7E8; Mon, 28 Dec 1998 13:07:07 +0100 (CET) Date: Mon, 28 Dec 1998 13:07:07 +0100 (CET) From: Didier Derny X-Sender: didier@idefix To: Peter Wemm Cc: Soren Schmidt , hm@hcs.de, yokota@zodiac.mech.utsunomiya-u.ac.jp, mike@smith.net.au, current@FreeBSD.ORG Subject: Re: future of syscons In-Reply-To: <199812281042.SAA64604@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it looks msdos in the old ages with all the problems linked to the direct access to the screen On Mon, 28 Dec 1998, Peter Wemm wrote: > Soren Schmidt wrote: > > It seems Hellmuth Michaelis wrote: > > > >From the keyboard of Kazutaka YOKOTA: > > > = > > > > > Not much has been designed or decided about terminal emulation code= > > > > > yet. I have just a vague idea that the terminal emulator code shal= > l > > > > write to the vty's internal buffer, rather than directly to the > > > > screen, and a timer routine will periodically render it to screen. > > > > = > > > > > Let's work together in designing this, shall we? > > > = > > > > Yes, i'd like to participate in this effort to be able to move the pc= > vt > > > functionality to this new design! > > = > > > Great, I'm very glad to hear that, and welcome in the comitter team !! > > Hey, this sounds rather interesting! :-) > > This sounds like a mini curses-like arrangement, except that there is no = > > need for cursor move optimization. > > What would make it really *really* interesting would be if it were = > > possible to mmap() the virtual buffer and draw directly into it from user= > = > > mode, thus bypassing terminal emulation altogether... > > Cheers, > -Peter > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ---------------------------------------------------------------------------- Didier Derny | FreeBSD 3.0-CURRENT Site Email: didier@omnix.net | Microsoft Free Computer. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 04:13:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25704 for freebsd-current-outgoing; Mon, 28 Dec 1998 04:13:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25699 for ; Mon, 28 Dec 1998 04:13:13 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id HAA29939; Mon, 28 Dec 1998 07:12:55 -0500 (EST) Message-ID: <19981228071255.S1333@ns1.adsu.bellsouth.com> Date: Mon, 28 Dec 1998 07:12:55 -0500 From: Christian Kuhtz To: Matt White , freebsd-current@FreeBSD.ORG Subject: Re: PPTP and FreeBSD References: <199812272119.QAA13600@o2.cs.rpi.edu> <4281573128.914814639@DEIMOS.REM.CMU.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <4281573128.914814639@DEIMOS.REM.CMU.EDU>; from Matt White on Mon, Dec 28, 1998 at 03:10:39AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt, With all due respect, I have rarely read such complete rubbish. Further note that I am making these statements not as a representative for BellSouth in my function as Sr.Network Architect and designer of many advanced VPN services among other thing, although IMHO many of the reasons cited below might apply to us. Now that we got that out of the way, let me address the issue: L2TP is a functional merger of L2F and PPTP. It is essentially extending a layer 2 connection service over layer 3. It is far far more than a corporate VPN service. In fact, it is of immense value to service providers. L2TP is not interoperable with L2F or PPTP. On Mon, Dec 28, 1998 at 03:10:39AM -0500, Matt White wrote: > L2TP is much the same way. The reason for this is that these protocols are > not really designed for what we are using them for. Both PPTP and L2TP are > ways of tunneling traffic received from a client by an ISP's remote access > device back to a corporate network. There is only one control connection > per corporate network endpoint. There is at least one 'PPP over IP' (ergo L2F/L2TP) connection per NAS (LAC) per HG (LNS), over which multiple users can ride. A lot of it has to do with the exact fault-tolerance and/or load-sharing setup. For what precisely is L2TP design to be used for that we aren't using it for? That statement is complete garbage. L2F is in widespread use by service providers to provide VPDN services to customers. Yes, there happen to be several very large providers who are running a very successful commercial offering and have major customers using the service. It requires absolutely no changes on the client (because it is NAS initiated). One of the possible uses is to allow people to outsource their high cost high maintenance corporate dial pools to us, without having to make any changes in their network design (addressing, authentication, etc) It can also be used by wholesale dial providers to provide wholesale dial pools to their customers, the LNS being on the provider's premises and the LAC being in the wholesale dial provider's hands. How else would you provide this service, considering that the last thing you want to do as a wholesale dial provider is getting involved in somebody's layer 3 addressing etc. In fact, all you have to do is maintain the pool for a given DNIS, and the authentication (since it is all PPP) is done by the LNS.. > This has the advantage that the end user doesn't have to set anything up on > their computer to take advantage of the tunneling...it is done > automatically by the RAS. Since it is PPP, that statement is a false. The LNS and LAC negotiate the connection. The LNS terminates a tunnel per LAC, which (can, but usually always does) contain multiple users, from multiple NAS, which are bonded via MCMLPPP to originate a tunnel from the LAC to the LNS. > The difficulty is, of course, that arrangements > for these tunnels must be made at all possible access points so I wonder > how much L2TP is actually ever going to be used as intended. That is complete BS. Several service provider VPN services, for instance, is available in its entire territory, which contains a great many number of NAS and even more dial up ports. L2F is in very wide spread use today, in the process of migrating to L2TP, and will most likely grow massively in '99. A lot of the reasons are regulatory on one hand, and on the other hand, advanced VPN services, which may for instance consist of MPLS based infrastructures, need L2TP for integration with roaming users as well as plain integration with other networks which do not have capabilities such as MPLS. > As far as the amount of work required to implement L2TP or PPTP, I'm not > sure about how bad it would be. Keep in mind that a good portion of both > of these protocols are implemented elsewhere. It might be more of an issue > of sewing the right modules together. > > Not that I'm going to spend the time to do it. My personal feeling is that > VPNs are evil and yet another excuse to not properly secure one's systems > (firewalls being the last excuse). L2F/L2TP is the only large scale service provider way of providing VPN services. In fact, because of regulatory restrictions, it is often the only way for the 'phone company' part of an RBOC to provide certain services (because they can't and don't want to over layer 3 services, but can (by virtue of the FCC allowing them to) offer layer 2 services, at which point L2F/L2TP comes in). We have been struggling with supporting PPTP for some time now, and have tried to avoid it like the plague because NT is your only option for termination which is clearly not a service provider product at the present time not does it offer a scalable solution methodology wise. L2TP is the way to go. And having LNS functionality would be *VERY* interesting to have. Nice to read such BS in here every so often, though. Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 04:44:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28082 for freebsd-current-outgoing; Mon, 28 Dec 1998 04:44:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28077 for ; Mon, 28 Dec 1998 04:44:51 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id HAA00351; Mon, 28 Dec 1998 07:44:29 -0500 (EST) Message-ID: <19981228074429.V1333@ns1.adsu.bellsouth.com> Date: Mon, 28 Dec 1998 07:44:29 -0500 From: Christian Kuhtz To: Joe Abley , "David E. Cross" Cc: freebsd-current@FreeBSD.ORG Subject: Re: PPTP and FreeBSD References: <199812272119.QAA13600@o2.cs.rpi.edu> <19981228120057.A28852@clear.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981228120057.A28852@clear.co.nz>; from Joe Abley on Mon, Dec 28, 1998 at 12:00:57PM +1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 12:00:57PM +1300, Joe Abley wrote: > > documentation on it. It is a bad joke, all the way arround. First it uses a > > modified version of the GRE protocol (that is why I asked about GRE support > > in the kernel way back when), as an encapsulation around the PPP packets. > > But, to be fair, GRE has been extended in a reasonable-looking and backward- > compatible way. I don't personally agree with the methodology either, and > would have preferred to see sequence numbers present in a further protocol > header between GRE and PPP, leaving GRE as it is, but oh well... Why do you need sequence numbers in the tunneling protocol when you're doing IP over MCMLPPP? > > It > > also must have a TCP connection between the client and the server to act as > > a controll connection. If that control connection is lost for whatever reason > > , the tunel is closed. That is nonsense. A TCP connection adds latency that you *DO NOT* want. And today we have and use technology already which does provide full redundancy and load sharing regardless of whether it is TCP or UDP. In fact, TCP doesn't by you squat. Think of what the stack looks like: TCP/UDP TCP/UDP IP IP PPP or PPP L2TP L2TP [IPSec] [IPSec] IP IP PPP [..] FR/ATM How many layers of ack would you like? > I don't really see why this is such a bad thing. The use of the TCP session > is a bit clunky, but if the network is unstable enough that a TCP connection > carrying minimal data cannot survive, then the tunnel probably _ought_ to > be closed. PPP is what's inside of L2F and L2TP, therefore you already got all those things covered. You guys are worrying about non-issues. PPTP is braindead use L2TP. > > Oh yes, one last thing, the GRE portion of the tunel, > > where the data actually goes, has an ack/nak, sliding window and retransmit > > system (again, outlined in the MS documentation). > > The tunnel end-points do _not_ do retransmissions, but they do operate > some (barely-specified) end-to-end flow control. It's the responsibility of the payload, which is IP afterall. Not an issue. Further, your latency overhead would be much worse (and gain nothing) if you had tunneling protocol retransmits. > I agree - it is a pretty nasty protocol, but has the advantage of widespread > userbase support - show me one other tunnelling client which is ready and > waiting on as many desktops as PPTP (even if the users don't know it's > there). L2TP will make it to those desktops very quickly. Just try to trust me on that one. > I've been looking at draft-ietf-pppext-pptp-07.txt and I don't thing that > the PPTP elements look particularly difficult to code. Don't waste your time. L2TP is to replace PPTP. Cisco and Microsoft sponsored the L2TP development (and merger of L2F (cisco) and PPTP (Microsoft)). The L2TP backoffs have also finished and you will see much more L2TP than PPTP has ever seen very soon (not counting existing L2F services converted to L2TP). PPTP sucks because it is a session per use (do to the fact that they are all client initiated, and not NAS initiated like L2F/L2TP) > A high-performance PPTP Network Server (PNS) implementation on FreeBSD > could be made using existing PPP stacks, with the proviso that the tunnel > creation/teardown would involve process switching (for the userland > portions of PPP), and a server that was required to support a large number > of simultaneously-active tunnels would correspondingly need a large number > of kernel ppp/tun interfaces available (one per tunnel). I don't see what the issue is. With L2TP, you have one session per LAC/LNS association. What's the issue with supporting, say, 64 concurrent sessions? > A generic kernel tunnel interface would make this easier. tun? Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 04:45:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA28335 for freebsd-current-outgoing; Mon, 28 Dec 1998 04:45:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA28330 for ; Mon, 28 Dec 1998 04:45:39 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id HAA00158; Mon, 28 Dec 1998 07:31:49 -0500 (EST) Message-ID: <19981228073149.U1333@ns1.adsu.bellsouth.com> Date: Mon, 28 Dec 1998 07:31:49 -0500 From: Christian Kuhtz To: Poul-Henning Kamp , Matt White Cc: freebsd-current@FreeBSD.ORG Subject: Re: PPTP and FreeBSD References: <4235743047.914768809@FRAUGHT.NET.CMU.EDU> <68859.914787333@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <68859.914787333@critter.freebsd.dk>; from Poul-Henning Kamp on Sun, Dec 27, 1998 at 08:35:33PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 27, 1998 at 08:35:33PM +0100, Poul-Henning Kamp wrote: > >Since we don't consider our local wire to be secure in any way shape or > >form, we encrypt all sensitive traffic in the application. IMO, this is > >the only sane way to do things. > > We used to have a war-chant we used against the OSI people, it went > something like: > "Anything but end-to-end ACKs is a waste of time" > > I pressume that it would be equally valid if you did a: > > s/ACKs/encryption/ Encryption comes at a cost. Particularly obvious when you're talking about encrypting the bandwidth equivalent of what might be user session inside an OC-3 (short term) or OC-12 (mid term) circuit. It is a question of whether you can afford to pay for it. Although I'd opt for encryption, too, (just to be paranoid) if I got the choice, once somebody actually places $$$ figures on it, the whole story changes quickly. Think of all the people who are using frame-relay today and don't have a problem with it. Very few are actually using bricks or application layer encryption to provide security. And then ask yourself how many companies have had problems with that? Even though it is admittedly trivial to acquire and use a protocol analyzer. And there's nothing that says that you couldn't run IPSec tunnel mode around L2TP or GRE for that matter. Voila, encryption of a layer 2 service of IP. Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 05:36:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA01669 for freebsd-current-outgoing; Mon, 28 Dec 1998 05:36:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.hsonline.net (mail.hsonline.net [205.243.33.25]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA01662; Mon, 28 Dec 1998 05:36:45 -0800 (PST) (envelope-from zamy27@hsonline.net) Received: from hsonline.net [208.10.214.201] by mail.hsonline.net with ESMTP (SMTPD32-4.07) id A25F21270066; Mon, 28 Dec 1998 08:31:27 -0500 Message-ID: <36872715.78C80676@hsonline.net> Date: Mon, 28 Dec 1998 08:37:09 +0200 From: Scott Myron X-Mailer: Mozilla 4.03 [en] (Win95; I) MIME-Version: 1.0 To: "freebsd-questions@FreeBSD.org" , freebsd-current@FreeBSD.ORG Subject: after make buildworld..... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, i just did make buildworld, make installworld, and i built the kernel(3.0-CURRENT). now i have a few questions. When i reboot and go to log in it complains about not having an /etc/pam.conf. it does that each time i try to login. Any reason for that? So. Will someone please gzip and send me their pam.conf, cause i don't have one. and it wants one. Another question, i was in X, using kde, under one rxvt i su'ed to root(to remove alot of stuff from the make buildworld). i was rm'ing it, and i was also on IRC, the next thing i knew, it froze and reboot. Is that just a freak thing that will probably not happen again? or do you think something is messed up? Thanks for everything. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 05:40:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02113 for freebsd-current-outgoing; Mon, 28 Dec 1998 05:40:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02108 for ; Mon, 28 Dec 1998 05:40:20 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id IAA15205; Mon, 28 Dec 1998 08:39:37 -0500 (EST) Date: Mon, 28 Dec 1998 08:39:37 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: gmarco@giovannelli.it cc: current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: <199812280839.JAA12236@scotty.masternet.it> 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, 28 Jan 1999, Gianmarco Giovannelli wrote: > > > > I seem to remember IPFILTER being required for running > > > a proxy server such as squid transparently, I could be > > > mistaken though. > > Here it is : > > transproxy-0.3, transparent www proxy driver for IPFILTER (NOT ipfw!!) > > "transproxy - transparently proxy HTTP and other requests. > This program is used with Darren Reed's IPFILTER package and used > to intercept things like http requests and divert them to a www proxy server > (eg: squid), without requiring user intervention or configuration." You can do that with natd. > > > > Best Regards, > Gianmarco Giovannelli (http://www.giovannelli.it/~gmarco) > "Unix expert since yesterday" Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Mon Dec 28 05:53:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02664 for freebsd-current-outgoing; Mon, 28 Dec 1998 05:53:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02654; Mon, 28 Dec 1998 05:53:35 -0800 (PST) (envelope-from osa@etrust.ru) Received: from sunny.aha.ru (sunny.aha.ru [195.2.83.112]) by ns1.aha.ru (8.9.1/8.9.1/aha-r/0.04B) with ESMTP id QAA07394; Mon, 28 Dec 1998 16:53:05 +0300 (MSK) Received: by sunny.aha.ru id QAA03591; (8.8.8/vak/1.9) Mon, 28 Dec 1998 16:52:03 +0300 (MSK) Received: from unknown(195.2.84.114) by sunny.aha.ru via smap (V1.3) id sma003438; Mon Dec 28 16:51:40 1998 Received: from serv.etrust.ru (serv.etrust.ru [195.2.84.114]) by serv.etrust.ru (8.9.1/8.9.1) with SMTP id QAA21696; Mon, 28 Dec 1998 16:46:10 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Mon, 28 Dec 1998 16:46:09 +0300 (MSK) From: =?KOI8-R?B?88XSx8XKIO/Tz8vJzg==?= To: Scott Myron cc: "freebsd-questions@FreeBSD.org" , freebsd-current@FreeBSD.ORG Subject: Re: after make buildworld..... In-Reply-To: <36872715.78C80676@hsonline.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 28 Dec 1998, Scott Myron wrote: > Hello, i just did make buildworld, make installworld, and i built the > kernel(3.0-CURRENT). now i have a few questions. When i reboot and go to > log in it complains about not having an /etc/pam.conf. it does that each > time i try to login. Any reason for that? So. Will someone please gzip > and send me their pam.conf, cause i don't have one. and it wants one. > Another question, i was in X, using kde, under one rxvt i su'ed to > root(to remove alot of stuff from the make buildworld). i was rm'ing it, > and i was also on IRC, the next thing i knew, it froze and reboot. Is > that just a freak thing that will probably not happen again? or do you > think something is messed up? Thanks for everything. Do following: # cp /usr/src/etc/pam.conf /etc > > > > Scott > > > 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 28 05:55:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA02979 for freebsd-current-outgoing; Mon, 28 Dec 1998 05:55:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA02973 for ; Mon, 28 Dec 1998 05:55:53 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.8) with ESMTP id IAA01201; Mon, 28 Dec 1998 08:54:56 -0500 (EST) (envelope-from matt@zigg.com) Date: Mon, 28 Dec 1998 08:54:56 -0500 (EST) From: Matt Behrens To: Brian Feldman cc: gmarco@giovannelli.it, current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad 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, 28 Dec 1998, Brian Feldman wrote: : > "transproxy - transparently proxy HTTP and other requests. : > This program is used with Darren Reed's IPFILTER package and used : > to intercept things like http requests and divert them to a www proxy server : > (eg: squid), without requiring user intervention or configuration." : You can do that with natd. You can create the same effect, but lose all of squid's extra benefits like caching. I have also noticed that ppp -alias (which uses the same code as natd, AFAIR) fails to submit some forms properly using Netscape on a Windows box (probably Netscape's fault). This bug might be long-gone though :) Matt Behrens | If only I could learn Japanese and get my Servant of Karen Behrens | hands on all 200 Sailor Moon episodes and Engineer, Nameless IRC Network | all the movies, I think my life would I eat Penguins for breakfast. | finally be complete. . . . . . . . . . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 06:03:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03280 for freebsd-current-outgoing; Mon, 28 Dec 1998 06:03:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ernie.wmht.org (ernie.wmht.org [205.247.144.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03275 for ; Mon, 28 Dec 1998 06:03:03 -0800 (PST) (envelope-from bruth@wmht.org) Received: from bruth (gateway.wmht.org [205.247.144.10]) by ernie.wmht.org (8.8.8/8.8.8) with SMTP id JAA20300 for ; Mon, 28 Dec 1998 09:02:29 -0500 (EST) (envelope-from bruth@wmht.org) Message-Id: <199812281402.JAA20300@ernie.wmht.org> From: "Brian Ruth" To: freebsd-current@FreeBSD.ORG Date: Mon, 28 Dec 1998 09:05:43 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: types.h/controller ahc broken? Reply-to: bruth@ernie.wmht.org X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following smp kernel compiles fine on 3.0-RELEASE but not under -CURRENT as of 8:30am. Below is the config file and the error output from a make depend after a make clean. Kernel Config File: machine "i386" cpu "I686_CPU" ident ernie-smp maxusers 32 options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O options NBUS=5 options NCPU=2 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options MFS #Memory Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem 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 options "MD5" options QUOTA config kernel root on da0 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 controller ahc0 controller scbus0 device da0 device cd0 #Only need one of these, the code dynamically grows # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector sioin tr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device fxp0 pseudo-device loop pseudo-device ether pseudo-device vn pseudo-device snp 3 pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's # This provides support for System V shared memory. # options SYSVSHM options SYSVSEM options SYSVMSG pseudo-device bpfilter 4 #Berkeley packet filter Make Depend: gateway# make depend cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitializ ed -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../ ../../include -DKERNEL -include opt_global.h ../../i386/i386/genassym.c cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Ws trict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../ ../include -DKERNEL -include opt_global.h genassym.o -o genassym ./genassym >assym.s ym.s rm -f param.c cp ../../conf/param.c . sh ../../kern/vnode_if.sh ../../kern/vnode_if.src make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx Warning: Object directory not changed from original /big/FreeBSD/src/sys/compile /ernie-smp yacc -d ../../dev/aic7xxx/aicasm_gram.y mv y.tab.c aicasm_gram.c cc -O -pipe -I. -c aicasm_gram.c In file included from aicasm_gram.c:4: /usr/include/stdlib.h:136: parse error before `arc4random' /usr/include/stdlib.h:136: warning: data definition has no type or storage class /usr/include/stdlib.h:173: parse error before `strtoq' /usr/include/stdlib.h:173: warning: data definition has no type or storage class /usr/include/stdlib.h:175: parse error before `strtouq' /usr/include/stdlib.h:175: warning: data definition has no type or storage class In file included from ../../dev/aic7xxx/aicasm_gram.y:37: /usr/include/sys/types.h:60: parse error before `u_quad_t' /usr/include/sys/types.h:60: warning: data definition has no type or storage cla ss /usr/inclu class /usr/incluude/sys/types.h:61: parse error before `quad_t' /usr/include/sys/types.h:61: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:62: parse error before `*' /usr/include/sys/types.h:62: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:65: parse error before `daddr_t' /usr/include/sys/types.h:65: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:66: parse error before `dev_t' /usr/include/sys/types.h:66: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:67: parse error before `fixpt_t' /usr/include/sys/types.h:67: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:68: parse error before `gid_t' /usr/include/sys/types.h:68: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:69: parse error before `ino_t' /usr/include/sys/types.h:69: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:71: parse error beforse error before `mode_t' /usr/include/sys/types.h:71: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:72: parse error before `nlink_t' /usr/include/sys/types.h:72: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:75: parse error before `rlim_t' /usr/include/sys/types.h:75: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:79: parse error before `segsz_t' /usr/include/sys/types.h:79: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:81: parse error before `swblk_t' /usr/include/sys/types.h:81: warning: data definition has no type or storage cla ss /usr/include/sys/types.h:82: parse error before `uid_t' /usr/include/sys/types.h:82: warning: data definition has no type or storage cla ss In file included from ../../dev/aic7xxx/aicasm_gram.y:41: ../../dev/aic7xxx/aicasm_symbol.h:54: parse error before `u_int8_t' ../../dev/aic7xxx/aicasm_symbol.h:54: warning: no semicolon at end of struct or union .uct or union .../../dev/aic7xxx/aicasm_symbol.h:57: parse error before `valid_bitmask' ../../dev/aic7xxx/aicasm_symbol.h:57: warning: data definition has no type or st orage class ../../dev/aic7xxx/aicasm_symbol.h:59: parse error before `}' ../../dev/aic7xxx/aicasm_symbol.h:65: parse error before `u_int8_t' ../../dev/aic7xxx/aicasm_symbol.h:65: warning: no semicolon at end of struct or union ../../dev/aic7xxx/aicasm_symbol.h:69: parse error before `u_int8_t' ../../dev/aic7xxx/aicasm_symbol.h:69: warning: no semicolon at end of struct or union ../../dev/aic7xxx/aicasm_symbol.h:71: parse error before `}' In file included from ../../dev/aic7xxx/aicasm_gram.y:42: ../../dev/aic7xxx/sequencer.h:40: parse error before `u_int32_t' ../../dev/aic7xxx/sequencer.h:40: warning: no semicolon at end of struct or unio n ../../dev/aic7xxx/sequencer.h:49: parse error before `u_int32_t' ../../dev/aic7xxx/sequencer.h:49: warning: no semicolon at end of struct or unio n ../../dev/aic7xxx/sequencer.h:58: parse error before `u_int32_t'^M `u_int32_t'^M ../../dev/aic7xxx/sequencer.h:58: warning: no semicolon at end of struct or unio n ../../dev/aic7xxx/sequencer.h:66: field `format1' has incomplete type ../../dev/aic7xxx/sequencer.h:67: field `format2' has incomplete type ../../dev/aic7xxx/sequencer.h:68: field `format3' has incomplete type ../../dev/aic7xxx/sequencer.h:69: parse error before `u_int8_t' ../../dev/aic7xxx/sequencer.h:69: warning: no semicolon at end of struct or unio n ../../dev/aic7xxx/sequencer.h:70: warning: data definition has no type or storag e class ../../dev/aic7xxx/sequencer.h:73: field `format' has incomplete type ../../dev/aic7xxx/aicasm_gram.y: In function `process_bitmask': ../../dev/aic7xxx/aicasm_gram.y:1000: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1005: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1010: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1015: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:101sm_gram.y:1017: dereferencing pointer to inco mplete type ../../dev/aic7xxx/aicasm_gram.y:1018: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y: In function `initialize_symbol': ../../dev/aic7xxx/aicasm_gram.y:1035: sizeof applied to an incomplete type ../../dev/aic7xxx/aicasm_gram.y:1041: sizeof applied to an incomplete type ../../dev/aic7xxx/aicasm_gram.y:1056: sizeof applied to an incomplete type ../../dev/aic7xxx/aicasm_gram.y:1061: sizeof applied to an incomplete type ../../dev/aic7xxx/aicasm_gram.y:1062: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1067: sizeof applied to an incomplete type ../../dev/aic7xxx/aicasm_gram.y:1073: sizeof applied to an incomplete type ../../dev/aic7xxx/aicasm_gram.y: In function `format_1_instr': ../../dev/aic7xxx/aicasm_gram.y:1151: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1152: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1153: dereferencing pointer to incomplet to inco mplete type ../../dev/aic7xxx/aicasm_gram.y:1153: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1155: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1155: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1157: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1160: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y: In function `format_2_instr': ../../dev/aic7xxx/aicasm_gram.y:1176: `u_int8_t' undeclared (first use this func tion) ../../dev/aic7xxx/aicasm_gram.y:1176: (Each undeclared identifier is reported on ly once ../../dev/aic7xxx/aicasm_gram.y:1176: for each function it appears in.) ../../dev/aic7xxx/aicasm_gram.y:1176: parse error before `shift_control' ../../dev/aic7xxx/aicasm_gram.y:1188: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1189: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1190: dereferencing pointer to incompter to inco mplete type ../../dev/aic7xxx/aicasm_gram.y:1190: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1192: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1192: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1201: `shift_control' undeclared (first use this function) ../../dev/aic7xxx/aicasm_gram.y:1226: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y: In function `format_3_instr': ../../dev/aic7xxx/aicasm_gram.y:1260: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1261: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1262: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1262: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1264: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1267: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y: In function `test_readab `test_readable_symbol' : ../../dev/aic7xxx/aicasm_gram.y:1277: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y: In function `test_writable_symbol': ../../dev/aic7xxx/aicasm_gram.y:1288: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y: In function `type_check': ../../dev/aic7xxx/aicasm_gram.y:1315: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1318: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1328: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:1334: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y: In function `yyparse': ../../dev/aic7xxx/aicasm_gram.y:216: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:217: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:219: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:220: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_graxxx/aicasm_gram.y:226: dereferencing pointer to inco mplete type ../../dev/aic7xxx/aicasm_gram.y:227: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:230: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:258: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:265: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:272: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:423: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:427: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:431: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:461: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:462: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:478: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:479: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_c7xxx/aicasm_gram.y:509: dereferencing pointer to incom plete type ../../dev/aic7xxx/aicasm_gram.y:533: dereferencing pointer to incomplete type ../../dev/aic7xxx/aicasm_gram.y:557: dereferencing pointer to incomplete type *** Error code 1 Stop. *** Error code 1 Stop. --- Brian Ruth bruth@wmht.org (518)357-1700 WMHT Educational Telecommunications - MIS Department P.O. Box 17, Schenectady, NY 12301 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 06:12:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04293 for freebsd-current-outgoing; Mon, 28 Dec 1998 06:12:02 -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 GAA04279 for ; Mon, 28 Dec 1998 06:12:00 -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 PAA73473; Mon, 28 Dec 1998 15:10:40 +0100 (CET) To: bruth@ernie.wmht.org cc: freebsd-current@FreeBSD.ORG Subject: Re: types.h/controller ahc broken? In-reply-to: Your message of "Mon, 28 Dec 1998 09:05:43 EST." <199812281402.JAA20300@ernie.wmht.org> Date: Mon, 28 Dec 1998 15:10:40 +0100 Message-ID: <73471.914854240@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812281402.JAA20300@ernie.wmht.org>, "Brian Ruth" writes: >The following smp kernel compiles fine on 3.0-RELEASE but not >under -CURRENT as of 8:30am. Below is the config file and the >error output from a make depend after a make clean. cd /usr/src make includes -- 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 Mon Dec 28 06:16:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04673 for freebsd-current-outgoing; Mon, 28 Dec 1998 06:16:49 -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 GAA04667 for ; Mon, 28 Dec 1998 06:16:46 -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 PAA14041; Mon, 28 Dec 1998 15:16:28 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id PAA59774; Mon, 28 Dec 1998 15:16:28 +0100 (MET) Message-ID: <19981228151627.D53810@follo.net> Date: Mon, 28 Dec 1998 15:16:27 +0100 From: Eivind Eklund To: Poul-Henning Kamp , bruth@ernie.wmht.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: types.h/controller ahc broken? References: <199812281402.JAA20300@ernie.wmht.org> <73471.914854240@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <73471.914854240@critter.freebsd.dk>; from Poul-Henning Kamp on Mon, Dec 28, 1998 at 03:10:40PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 03:10:40PM +0100, Poul-Henning Kamp wrote: > In message <199812281402.JAA20300@ernie.wmht.org>, "Brian Ruth" writes: > >The following smp kernel compiles fine on 3.0-RELEASE but not > >under -CURRENT as of 8:30am. Below is the config file and the > >error output from a make depend after a make clean. > > cd /usr/src > make includes This should not be necessary in a normal source tree (if the kernel is built from src/sys, with src/include checked out and up to date). In this case, the includes should be gotten from src/include and src/sys, and if they're not, something in the kernel build is broken. Besides, 'make includes' shouldn't be used unless the person doing it knows exactly what he's doing - it can break a lot of things, so 'make world' and a re-built kernel should be used instead, to keep things in sync. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 06:25:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05717 for freebsd-current-outgoing; Mon, 28 Dec 1998 06:25:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp1.andrew.cmu.edu (SMTP1.ANDREW.CMU.EDU [128.2.10.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05710 for ; Mon, 28 Dec 1998 06:25:23 -0800 (PST) (envelope-from mwhite@cmu.edu) Received: from DEIMOS.REM.CMU.EDU (DEIMOS.REM.CMU.EDU [128.2.108.154]) by smtp1.andrew.cmu.edu (8.8.5/8.8.2) with ESMTP id JAA01835; Mon, 28 Dec 1998 09:25:04 -0500 (EST) Date: Mon, 28 Dec 1998 09:24:20 -0500 From: Matt White To: freebsd-current@FreeBSD.ORG cc: Christian Kuhtz Subject: Re: PPTP and FreeBSD Message-ID: <9026692.914837060@DEIMOS.REM.CMU.EDU> In-Reply-To: <19981228071255.S1333@ns1.adsu.bellsouth.com> 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 *quenches flames* I guess I didn't read the drafts closely enough four months ago when I was last looking at this. Since you obviously think you know all about these protocols, perhaps you can set me straight. My impression from looking at the protocols and the products that have been built around them is that the following is the expected case: A client dials up to a remote access server at some ISP. There has been some arrangement made between the client's company and said ISP to have the client's traffic tunneled back to their site. The remote access server creates a tunnel back to a configured endpoint at the client's company's site on behalf of the client. The client needs no software to do this and may not even know that such tunneling is taking place on it's behalf. Obviously there are other similar situations where this is useful, such as an ISP that wants to manage all of its POPs from a single IP space, but does not want to set up physical circuits for each POP. I am sure you can list many other situations, but these are really the ones that most affect me on a day to day. Now, what we were talking about is having the client itself initiate the tunnel on its own behalf. This is what the MS VPN clients do. However, from looking at the protocol spec, it seems that quite a bit goes into making the above case work properly. It seems that a protocol that only did client tunneling could be made easier to implement. That is the source of the statement that we are not exactly considering L2TP/PPTP for what they were intended. Will they work? Of course. This has already been demonstrated. As to whether to implement PPTP or L2TP first, that largely remains dependant on the application. For a client, L2TP is obviously the way to go. However, I still want a PPTP server that authenticates to radius (or better yet, uses PAM). If said PPTP server also supported L2TP, that would make me just that much happier. So anyway, where did I go horribly wrong? -Matt ---------- Matt White Network Systems Designer Canegie Mellon Computing Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 06:31:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06130 for freebsd-current-outgoing; Mon, 28 Dec 1998 06:31:03 -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 GAA06125 for ; Mon, 28 Dec 1998 06:31:00 -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 PAA73574; Mon, 28 Dec 1998 15:29:02 +0100 (CET) To: Eivind Eklund cc: bruth@ernie.wmht.org, freebsd-current@FreeBSD.ORG Subject: Re: types.h/controller ahc broken? In-reply-to: Your message of "Mon, 28 Dec 1998 15:16:27 +0100." <19981228151627.D53810@follo.net> Date: Mon, 28 Dec 1998 15:29:01 +0100 Message-ID: <73572.914855341@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19981228151627.D53810@follo.net>, Eivind Eklund writes: >On Mon, Dec 28, 1998 at 03:10:40PM +0100, Poul-Henning Kamp wrote: >> In message <199812281402.JAA20300@ernie.wmht.org>, "Brian Ruth" writes: >> >The following smp kernel compiles fine on 3.0-RELEASE but not >> >under -CURRENT as of 8:30am. Below is the config file and the >> >error output from a make depend after a make clean. >> >> cd /usr/src >> make includes > >This should not be necessary in a normal source tree (if the kernel is >built from src/sys, with src/include checked out and up to date). In >this case, the includes should be gotten from src/include and src/sys, >and if they're not, something in the kernel build is broken. It is because the aic assembler picks up stuff here and there as far as I could figure out when I had the problem. try to mv /usr/include /usr/_include and see if you can compile LINT... -- 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 Mon Dec 28 06:44:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06994 for freebsd-current-outgoing; Mon, 28 Dec 1998 06:44:16 -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 GAA06983 for ; Mon, 28 Dec 1998 06:44:13 -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 JAA01532 for ; Mon, 28 Dec 1998 09:43:56 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA20344; Mon, 28 Dec 1998 09:43:55 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id JAA16653 for freebsd-current@freebsd.org; Mon, 28 Dec 1998 09:43:45 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812281443.JAA16653@bb01f39.unx.sas.com> Subject: The Great FreeBSD Purge: A suggestion To: freebsd-current@FreeBSD.ORG Date: Mon, 28 Dec 1998 09:43:45 -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 Hello, As an outside observer of the recent events in -current, I have a suggestion which will (could) benefit both developers and the user community.... Before purging code from the system, that code should be tagged as to be deleted, and messages at boot time should be displayed warning the user about what will be happenning with the NEXT release of the software... Assuming the psm device was targetted for removal: psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 psm0: WARNING: this device is scheduled for removal in release x.y.z. psm0: WARNING: Please see 'man 4 abc' for a replacement. Basically, what it boils down to, is none of you (us, though I am not a committer) knows how people use FreeBSD, what devices they have configured into their kernels, and which they don't. Those benefits I spoke of? The user community (all of us, even you the developers) will know what code is scheduled for removal from the system. You will not take those users by surprise when they install the latest release only to discover that their xyz0 hardware nolonger works. To the developer? You now have a well scheduled date/release at which you may purge code. Your target user audience knows the code will be removed, and the amount of hassle associated with that removal is reduced. I am not the only person who uses FreeBSD in a production environment. You have purged working code from the system which I will now have to figure out how to replace and then validate in our processes. Making sure new code doesn't fall over under heavy load or stress conditions is not a simple process. I would think that many of you with your experience over the years would realize this. Just my .02 cents worth, John ps: Why not have a freebsd-kernelconf mailing list which is a frontend to a service which reads a mailed in kernel configuration file and keeps a tally of which devices are used and in what percentages? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 06:53:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07627 for freebsd-current-outgoing; Mon, 28 Dec 1998 06:53:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA07618 for ; Mon, 28 Dec 1998 06:53:16 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id JAA01917; Mon, 28 Dec 1998 09:52:26 -0500 (EST) Message-ID: <19981228095226.B1333@ns1.adsu.bellsouth.com> Date: Mon, 28 Dec 1998 09:52:26 -0500 From: Christian Kuhtz To: Matt Behrens , Brian Feldman Cc: gmarco@giovannelli.it, current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Matt Behrens on Mon, Dec 28, 1998 at 08:54:56AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 08:54:56AM -0500, Matt Behrens wrote: > : > "transproxy - transparently proxy HTTP and other requests. > : > This program is used with Darren Reed's IPFILTER package and used > : > to intercept things like http requests and divert them to a www proxy server > : > (eg: squid), without requiring user intervention or configuration." > > : You can do that with natd. > > You can create the same effect, but lose all of squid's extra > benefits like caching. I have also noticed that ppp -alias (which > uses the same code as natd, AFAIR) fails to submit some forms > properly using Netscape on a Windows box (probably Netscape's > fault). This bug might be long-gone though :) So, the feature you're really looking for is 'transparent redirection', correct? Very much like all the other (supposedly) 'layer 4 switching' widgets out there (e.g., Alteon, etc). 'Transparent redirection' is disjoint from 'transparent proxy'. You can have a 'transparent proxy' which does not do 'transparent redirection'. Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 07:17:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09460 for freebsd-current-outgoing; Mon, 28 Dec 1998 07:17:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09451 for ; Mon, 28 Dec 1998 07:17:42 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.1/8.9.1) id QAA00168; Mon, 28 Dec 1998 16:17:24 +0100 (CET) (envelope-from des) To: current@FreeBSD.ORG Subject: CALL FOR FEEDBACK: inetd From: Dag-Erling Smorgrav Date: 28 Dec 1998 16:17:24 +0100 Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just committed a patch to inetd (rev. 1.44 of inetd.c) which I hope fixes the "junk pointer: too low to make sense" bug mentioned in PR bin/8183. I'd appreciate if those of you who have experienced problems with inetd would tell me as quickly as possible if the patch alleviates those problems. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 07:36:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11679 for freebsd-current-outgoing; Mon, 28 Dec 1998 07:36:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from host.phc.igs.net (host.phc.igs.net [207.210.17.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11669 for ; Mon, 28 Dec 1998 07:36:02 -0800 (PST) (envelope-from eagle@phc.igs.net) Received: from bsd.home ([207.210.17.116]) by host.phc.igs.net (8.8.5/8.8.5) with ESMTP id KAA13326; Mon, 28 Dec 1998 10:42:48 -0500 (EST) Received: (from eagle@localhost) by bsd.home (8.9.1/8.9.1) id KAA31863; Sun, 27 Dec 1998 10:09:03 -0500 (EST) (envelope-from eagle) Message-Id: <199812271509.KAA31863@bsd.home> Date: Sun, 27 Dec 1998 10:07:43 -0500 (EST) From: eagle Subject: Re: types.h/controller ahc broken? To: bruth@ernie.wmht.org cc: bruth@wmht.org, freebsd-current@FreeBSD.ORG In-Reply-To: <199812281402.JAA20300@ernie.wmht.org> MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28 Dec, Brian Ruth wrote: > The following smp kernel compiles fine on 3.0-RELEASE but not > under -CURRENT as of 8:30am. Below is the config file and the > error output from a make depend after a make clean. > > Kernel Config File: > machine "i386" > cpu "I686_CPU" > > ident ernie-smp > maxusers 32 > options SMP # Symmetric MultiProcessor Kernel > options APIC_IO # Symmetric (APIC) I/O > options NBUS=5 > options NCPU=2 > > options INET #InterNETworking > options FFS #Berkeley Fast Filesystem > options MFS #Memory Filesystem > options NFS #Network Filesystem > options MSDOSFS #MSDOS Filesystem > options "CD9660" #ISO 9660 Filesystem > 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 > options "MD5" > options QUOTA > config kernel root on da0 > > controller isa0 > controller pci0 > > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr > disk fd0 at fdc0 drive 0 > > controller ahc0 > controller scbus0 > device da0 > device cd0 #Only need one of these, the code dynamically grows > > # syscons is the default console driver, resembling an SCO console > device sc0 at isa? port "IO_KBD" conflicts tty irq 1 vector scintr > > device npx0 at isa? port "IO_NPX" irq 13 vector npxintr > > device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 vector sioin > tr > device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr > > device lpt0 at isa? port? tty irq 7 vector lptintr > device fxp0 > > pseudo-device loop > pseudo-device ether > pseudo-device vn > pseudo-device snp 3 > pseudo-device pty 16 > pseudo-device gzip # Exec gzipped a.out's > > # This provides support for System V shared memory. > # > options SYSVSHM > options SYSVSEM > options SYSVMSG > > pseudo-device bpfilter 4 #Berkeley packet filter > > Make Depend: > gateway# make depend > cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitializ > ed -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../ > ../../include -DKERNEL -include opt_global.h ../../i386/i386/genassym.c > cc -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Ws > trict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized > -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../ > ../include -DKERNEL -include opt_global.h genassym.o -o genassym > ./genassym >assym.s > ym.s > > rm -f param.c > cp ../../conf/param.c . > sh ../../kern/vnode_if.sh ../../kern/vnode_if.src > make -f ../../dev/aic7xxx/Makefile MAKESRCPATH=../../dev/aic7xxx > Warning: Object directory not changed from original /big/FreeBSD/src/sys/compile > /ernie-smp > yacc -d ../../dev/aic7xxx/aicasm_gram.y > mv y.tab.c aicasm_gram.c > cc -O -pipe -I. -c aicasm_gram.c > In file included from aicasm_gram.c:4: > /usr/include/stdlib.h:136: parse error before `arc4random' > /usr/include/stdlib.h:136: warning: data definition has no type or storage class > /usr/include/stdlib.h:173: parse error before `strtoq' > /usr/include/stdlib.h:173: warning: data definition has no type or storage class > /usr/include/stdlib.h:175: parse error before `strtouq' > /usr/include/stdlib.h:175: warning: data definition has no type or storage class > In file included from ../../dev/aic7xxx/aicasm_gram.y:37: > /usr/include/sys/types.h:60: parse error before `u_quad_t' > /usr/include/sys/types.h:60: warning: data definition has no type or storage cla > ss > /usr/inclu class > /usr/incluude/sys/types.h:61: parse error before `quad_t' > /usr/include/sys/types.h:61: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:62: parse error before `*' > /usr/include/sys/types.h:62: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:65: parse error before `daddr_t' > /usr/include/sys/types.h:65: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:66: parse error before `dev_t' > /usr/include/sys/types.h:66: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:67: parse error before `fixpt_t' > /usr/include/sys/types.h:67: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:68: parse error before `gid_t' > /usr/include/sys/types.h:68: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:69: parse error before `ino_t' > /usr/include/sys/types.h:69: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:71: parse error beforse error before `mode_t' > /usr/include/sys/types.h:71: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:72: parse error before `nlink_t' > /usr/include/sys/types.h:72: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:75: parse error before `rlim_t' > /usr/include/sys/types.h:75: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:79: parse error before `segsz_t' > /usr/include/sys/types.h:79: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:81: parse error before `swblk_t' > /usr/include/sys/types.h:81: warning: data definition has no type or storage cla > ss > /usr/include/sys/types.h:82: parse error before `uid_t' > /usr/include/sys/types.h:82: warning: data definition has no type or storage cla > ss > In file included from ../../dev/aic7xxx/aicasm_gram.y:41: > ../../dev/aic7xxx/aicasm_symbol.h:54: parse error before `u_int8_t' > ../../dev/aic7xxx/aicasm_symbol.h:54: warning: no semicolon at end of struct or > union > .uct or union > .../../dev/aic7xxx/aicasm_symbol.h:57: parse error before `valid_bitmask' > ../../dev/aic7xxx/aicasm_symbol.h:57: warning: data definition has no type or st > orage class > ../../dev/aic7xxx/aicasm_symbol.h:59: parse error before `}' > ../../dev/aic7xxx/aicasm_symbol.h:65: parse error before `u_int8_t' > ../../dev/aic7xxx/aicasm_symbol.h:65: warning: no semicolon at end of struct or > union > ../../dev/aic7xxx/aicasm_symbol.h:69: parse error before `u_int8_t' > ../../dev/aic7xxx/aicasm_symbol.h:69: warning: no semicolon at end of struct or > union > ../../dev/aic7xxx/aicasm_symbol.h:71: parse error before `}' > In file included from ../../dev/aic7xxx/aicasm_gram.y:42: > ../../dev/aic7xxx/sequencer.h:40: parse error before `u_int32_t' > ../../dev/aic7xxx/sequencer.h:40: warning: no semicolon at end of struct or unio > n > ../../dev/aic7xxx/sequencer.h:49: parse error before `u_int32_t' > ../../dev/aic7xxx/sequencer.h:49: warning: no semicolon at end of struct or unio > n > ../../dev/aic7xxx/sequencer.h:58: parse error before `u_int32_t'^M `u_int32_t'^M > ../../dev/aic7xxx/sequencer.h:58: warning: no semicolon at end of struct or unio > n > ../../dev/aic7xxx/sequencer.h:66: field `format1' has incomplete type > ../../dev/aic7xxx/sequencer.h:67: field `format2' has incomplete type > ../../dev/aic7xxx/sequencer.h:68: field `format3' has incomplete type > ../../dev/aic7xxx/sequencer.h:69: parse error before `u_int8_t' > ../../dev/aic7xxx/sequencer.h:69: warning: no semicolon at end of struct or unio > n > ../../dev/aic7xxx/sequencer.h:70: warning: data definition has no type or storag > e class > ../../dev/aic7xxx/sequencer.h:73: field `format' has incomplete type > ../../dev/aic7xxx/aicasm_gram.y: In function `process_bitmask': > ../../dev/aic7xxx/aicasm_gram.y:1000: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1005: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1010: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1015: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:101sm_gram.y:1017: dereferencing pointer to inco > mplete type > ../../dev/aic7xxx/aicasm_gram.y:1018: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y: In function `initialize_symbol': > ../../dev/aic7xxx/aicasm_gram.y:1035: sizeof applied to an incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1041: sizeof applied to an incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1056: sizeof applied to an incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1061: sizeof applied to an incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1062: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1067: sizeof applied to an incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1073: sizeof applied to an incomplete type > ../../dev/aic7xxx/aicasm_gram.y: In function `format_1_instr': > ../../dev/aic7xxx/aicasm_gram.y:1151: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1152: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1153: dereferencing pointer to incomplet to inco > mplete type > ../../dev/aic7xxx/aicasm_gram.y:1153: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1155: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1155: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1157: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1160: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y: In function `format_2_instr': > ../../dev/aic7xxx/aicasm_gram.y:1176: `u_int8_t' undeclared (first use this func > tion) > ../../dev/aic7xxx/aicasm_gram.y:1176: (Each undeclared identifier is reported on > ly once > ../../dev/aic7xxx/aicasm_gram.y:1176: for each function it appears in.) > ../../dev/aic7xxx/aicasm_gram.y:1176: parse error before `shift_control' > ../../dev/aic7xxx/aicasm_gram.y:1188: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1189: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1190: dereferencing pointer to incompter to inco > mplete type > ../../dev/aic7xxx/aicasm_gram.y:1190: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1192: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1192: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1201: `shift_control' undeclared (first use this > function) > ../../dev/aic7xxx/aicasm_gram.y:1226: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y: In function `format_3_instr': > ../../dev/aic7xxx/aicasm_gram.y:1260: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1261: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1262: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1262: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1264: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1267: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y: In function `test_readab `test_readable_symbol' > : > ../../dev/aic7xxx/aicasm_gram.y:1277: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y: In function `test_writable_symbol': > ../../dev/aic7xxx/aicasm_gram.y:1288: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y: In function `type_check': > ../../dev/aic7xxx/aicasm_gram.y:1315: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1318: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1328: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:1334: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y: In function `yyparse': > ../../dev/aic7xxx/aicasm_gram.y:216: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:217: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:219: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:220: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_graxxx/aicasm_gram.y:226: dereferencing pointer to inco > mplete type > ../../dev/aic7xxx/aicasm_gram.y:227: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:230: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:258: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:265: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:272: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:423: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:427: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:431: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:461: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:462: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:478: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:479: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_c7xxx/aicasm_gram.y:509: dereferencing pointer to incom > plete type > ../../dev/aic7xxx/aicasm_gram.y:533: dereferencing pointer to incomplete type > ../../dev/aic7xxx/aicasm_gram.y:557: dereferencing pointer to incomplete type > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > --- > Brian Ruth bruth@wmht.org (518)357-1700 > WMHT Educational Telecommunications - MIS Department > P.O. Box 17, Schenectady, NY 12301 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > i thought at least the options FFS_ROOT line needed to be defined not sure this is your problem. but its the only thing i noticed.. Bob To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 07:48:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12617 for freebsd-current-outgoing; Mon, 28 Dec 1998 07:48:26 -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 HAA12607 for ; Mon, 28 Dec 1998 07:48:23 -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 KAA10870 for ; Mon, 28 Dec 1998 10:48:06 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA24969; Mon, 28 Dec 1998 10:48:05 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id KAA16807 for freebsd-current@freebsd.org; Mon, 28 Dec 1998 10:47:55 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812281547.KAA16807@bb01f39.unx.sas.com> Subject: make world (aout lkm broken) To: freebsd-current@FreeBSD.ORG Date: Mon, 28 Dec 1998 10:47:55 -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 think the following says it all... current as of 10:20am EST. I don't see any commits to fix this in the last hour... -------------------------------------------------------------- >>> Rebuilding the aout obj tree -------------------------------------------------------------- cd /usr/src; PATH=/usr/obj/elf/usr/src/tmp/sbin:/usr/obj/elf/usr/src/tmp/usr/sbin:/usr/obj/elf/usr/src/tmp/bin:/usr/obj/elf/usr/src/tmp/usr/bin BISON_SIMPLE=/usr/obj/elf/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/elf/usr/src/tmp/usr/libexec:/usr/obj/elf/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/elf/usr/src/tmp/usr/lib/aout LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib OBJFORMAT_PATH=/usr/obj/elf/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O -pipe" /usr/obj/elf/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/aout/usr/src/tmp -f Makefile.inc1 par-obj ===> share/info . . . . ===> secure/usr.bin ===> secure/usr.bin/bdes ===> lkm cd: can't cd to /usr/src/lkm *** Error code 2 Stop. *** Error code 1 Thanks! John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 10:00:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26064 for freebsd-current-outgoing; Mon, 28 Dec 1998 10:00:32 -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 KAA26059 for ; Mon, 28 Dec 1998 10:00:31 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id KAA28492; Mon, 28 Dec 1998 10:00:11 -0800 (PST) (envelope-from obrien) Message-ID: <19981228100010.B28404@nuxi.com> Date: Mon, 28 Dec 1998 10:00:10 -0800 From: "David O'Brien" To: Heikki Suonsivu Cc: freebsd-current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad Reply-To: obrien@nuxi.ucdavis.edu References: <199812272253.OAA23572@bubble.didi.com.newsgate.clinet.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Heikki Suonsivu on Mon, Dec 28, 1998 at 05:32:03AM +0200 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 On Mon, Dec 28, 1998 at 05:32:03AM +0200, Heikki Suonsivu wrote: > > asami@FreeBSD.ORG (Satoshi Asami) writes: > > * The cleanups have been discussed in -core. > > > > There was no agreement about pcvt. > > I do not mind removing pcvt *after* vt220 emulation is supported by Or doing it 1st thing in 3.1-CURRENT, after 3.0-STABLE is branched. This makes our intentions clear, and gives pcvt people time to realize they either need to write vt100 emulation in syscons or loss the functionality. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 10:18:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28736 for freebsd-current-outgoing; Mon, 28 Dec 1998 10:18:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw0.transarc.com (xfw.transarc.com [192.54.226.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28729 for ; Mon, 28 Dec 1998 10:18:19 -0800 (PST) (envelope-from pat@transarc.com) Received: from mailhost2.transarc.com (mailhost2.transarc.com [158.98.14.14]) by fw0.transarc.com (AIX4.2/UCB 8.7/8.7) with ESMTP id NAA27222 for ; Mon, 28 Dec 1998 13:16:28 -0500 (EST) Received: from smithfield.transarc.com (smithfield.transarc.com [158.98.16.10]) by mailhost2.transarc.com (8.8.0/8.8.0) with SMTP id NAA23202 for ; Mon, 28 Dec 1998 13:17:59 -0500 (EST) Date: Mon, 28 Dec 1998 13:17:59 -0500 (EST) From: Pat Barron To: current@FreeBSD.ORG Subject: So, exactly what *was* purged? 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 know someone asked this, but I have not seen an answer: Could someone provide a list of exactly what was purged? It would be handy to know things like, "this was purged, and is absolutely *not* coming back", or "this was purged, but is being considered for reinstatement", but what I really want to know is *exactly* what is now (today) gone, that used to be there. BTW, I note that these items were said to be moved "to the attic"? My apologies if this is in a FAQ somewhere, but is this mythical "attic" of cast-off FreeBSD pieces accessible to the public? If so, how/where? Thanks, --Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 10:26:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29294 for freebsd-current-outgoing; Mon, 28 Dec 1998 10:26:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29287 for ; Mon, 28 Dec 1998 10:26:55 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id TAA06809; Mon, 28 Dec 1998 19:25:01 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id SAA01845; Mon, 28 Dec 1998 18:02:32 GMT (envelope-from son) Message-ID: <19981228180232.58123@breizh.prism.uvsq.fr> Date: Mon, 28 Dec 1998 18:02:32 +0000 From: Nicolas Souchu To: =?iso-8859-1?Q?Jos=E9_M=AA_Alcaide?= Cc: Stephen Palmer , gp@oitunix.oit.umass.edu, freebsd-current@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] References: <19981219130349.11043.qmail@www0f.netaddress.usa.net> <367E88FB.B9F0D79@we.lc.ehu.es> <19981222010450.23781@breizh.prism.uvsq.fr> <368171FF.B8A5B268@we.lc.ehu.es> <19981224181948.61645@breizh.prism.uvsq.fr> <368761EF.23641D79@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e In-Reply-To: =?iso-8859-1?Q?=3C368761EF=2E23641D79=40we=2Elc=2Eehu=2Ees=3E=3B_from_Jo?= =?iso-8859-1?Q?s=E9_M=AA_Alcaide_on_Mon=2C_Dec_28=2C_1998_at_11=3A48=3A1?= =?iso-8859-1?Q?5AM_+0100?= X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 11:48:15AM +0100, José Mª Alcaide wrote: > >Nicolas Souchu wrote: >> >> Sorry, I'm wrong, it's ok here with December, 22th. So I can't really >> help you from there :( >> >> You may retry previous sys/ releases Dec, 1st, Nov, 15th to find out the bogus >> submit. >> > >Parallel ZIP doesn't work here, using sources CVSupped today (Dec 28th). >Perhaps the cause isn't in the ppc/ppbus/vpo code; the problem >I see is that da0 isn't initialized, so I think that scbus0 doesn't >get attached to vpo0 for some reason. Some parts of the CAM code >have changed in the last month... > >These are my kernel config lines related to the parallel bus: > >controller scbus0 # Lo necesita el ZIP paralelo. >device da0 # Y esto también. >controller ppbus0 # Bus paralelo >controller vpo0 at ppbus? # ZIP paralelo >device nlpt0 at ppbus? # Impresora >controller ppc0 at isa? port ? tty irq 7 flags 0x04 > >I think that this config is OK. I have no SCSI adapter in this >machine. These are the boot messages (boot -v): > >ppc: parallel port found at 0x378 >ppc0: >ppc0 at 0x378 irq 7 flags 0x4 on isa >ppc0: Generic chipset (EPP-only) in EPP mode (EPP 1.9) >nlpt0: on ppbus 0 >nlpt0: Interrupt-driven port >vpo0: on ppbus 0 >vpo0: EPP 1.9 mode > >After that, there is no mention to any "da" device. >This is very odd, indeed. Ooops, I've added some detection code October, 31th. It may break your hardware. Detection of your ZIP is done in NIBBLE mode, then according to your boot flags, EPP mode is required for transfer. First, try to set your bootflags to 0x3 to force PS2/NIBBLE mode and see if it works. Then try 0x1. Secondly, set 0x44 to your bootflags to force your chipset generic and avoid NS chips detection code execution. I completly forgot all this... please, give me some feedback. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 10:27:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29533 for freebsd-current-outgoing; Mon, 28 Dec 1998 10:27:10 -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 KAA29488 for ; Mon, 28 Dec 1998 10:27:08 -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 NAA43185; Mon, 28 Dec 1998 13:30:54 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 28 Dec 1998 13:30:54 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Pat Barron cc: current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? 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, 28 Dec 1998, Pat Barron wrote: > I know someone asked this, but I have not seen an answer: Could someone > provide a list of exactly what was purged? It would be handy to know > things like, "this was purged, and is absolutely *not* coming back", or > "this was purged, but is being considered for reinstatement", but what I > really want to know is *exactly* what is now (today) gone, that used to be > there. voxware, lkms, vinum(an lkm) voxware may come back, vinum is definetly coming back as kld basically klms which have been deemed bad by -core are gone, as well as voxware. (there may be more i missed) vinum which i think is REALLY nifty should be back in a few days from what it looks like. > BTW, I note that these items were said to be moved "to the attic"? My > apologies if this is in a FAQ somewhere, but is this mythical "attic" of > cast-off FreeBSD pieces accessible to the public? If so, how/where? "The attic" refers to CVS attic: http://www.freebsd.org/cgi/cvsweb.cgi/src/ the things with "(in the Attic)" next to them are no longer in the tree, but are in the cvs archive. you can still get them, however most likely eventually they will become "stale" and not compile on a -current system. note to yourself, logging cvsup activity is a good thing, and if you are trully interested in such things you should subscribe to the cvs-freebsd mailing lists, or search them. hope this helps. -Alfred > > Thanks, > --Pat. > > > > 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 28 10:30:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29713 for freebsd-current-outgoing; Mon, 28 Dec 1998 10:30:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29708 for ; Mon, 28 Dec 1998 10:30:23 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id NAA25807; Mon, 28 Dec 1998 13:30:02 -0500 (EST) Date: Mon, 28 Dec 1998 13:30:02 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Pat Barron cc: current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? 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, 28 Dec 1998, Pat Barron wrote: > I know someone asked this, but I have not seen an answer: Could someone > provide a list of exactly what was purged? It would be handy to know > things like, "this was purged, and is absolutely *not* coming back", or > "this was purged, but is being considered for reinstatement", but what I > really want to know is *exactly* what is now (today) gone, that used to be > there. Off the top of my head, it was: VoxWare floppy tape driver 3c905 driver old ATAPI CD driver PCVT I have no idea if any are coming back, although there's a great amount of people wanting VoxWare if nothing else. > > BTW, I note that these items were said to be moved "to the attic"? My > apologies if this is in a FAQ somewhere, but is this mythical "attic" of > cast-off FreeBSD pieces accessible to the public? If so, how/where? > When something is deleted in CVS, it is moved to the Attic, where it's no longer checked out, but still accessible. Nothing is ever truly purged, usually. > Thanks, > --Pat. > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Mon Dec 28 10:31:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29998 for freebsd-current-outgoing; Mon, 28 Dec 1998 10:31:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29990 for ; Mon, 28 Dec 1998 10:31:51 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id NAA05256; Mon, 28 Dec 1998 13:30:17 -0500 (EST) Date: Mon, 28 Dec 1998 13:30:17 -0500 (EST) From: Chuck Robey To: Pat Barron cc: current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? 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, 28 Dec 1998, Pat Barron wrote: > I know someone asked this, but I have not seen an answer: Could someone > provide a list of exactly what was purged? It would be handy to know > things like, "this was purged, and is absolutely *not* coming back", or > "this was purged, but is being considered for reinstatement", but what I > really want to know is *exactly* what is now (today) gone, that used to be > there. > > BTW, I note that these items were said to be moved "to the attic"? My > apologies if this is in a FAQ somewhere, but is this mythical "attic" of > cast-off FreeBSD pieces accessible to the public? If so, how/where? If you're tracking current, then you're supposed to also monitor the FreeBSD-committers list (it says this in the Handbook, and it's a real requirement). All the things taken out were detailed in that list. Attic (with the capital A) is the directory created by cvs to store stuff that's been deleted. cvs itself never forgets anything, it just no longer retrieves that, when you check out a copy of current from your archive. cvs will happily give out the older stuff, if you use the right date or release code. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 10:44:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01443 for freebsd-current-outgoing; Mon, 28 Dec 1998 10:44:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from fw0.transarc.com (xfw.transarc.com [192.54.226.51]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA01438 for ; Mon, 28 Dec 1998 10:44:48 -0800 (PST) (envelope-from pat@transarc.com) Received: from mailhost2.transarc.com (mailhost2.transarc.com [158.98.14.14]) by fw0.transarc.com (AIX4.2/UCB 8.7/8.7) with ESMTP id NAA52582; Mon, 28 Dec 1998 13:42:58 -0500 (EST) Received: from smithfield.transarc.com (smithfield.transarc.com [158.98.16.10]) by mailhost2.transarc.com (8.8.0/8.8.0) with SMTP id NAA23599; Mon, 28 Dec 1998 13:44:30 -0500 (EST) Date: Mon, 28 Dec 1998 13:44:29 -0500 (EST) From: Pat Barron To: Chuck Robey cc: current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? 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, 28 Dec 1998, Chuck Robey wrote: > If you're tracking current, then you're supposed to also monitor the > FreeBSD-committers list (it says this in the Handbook, and it's a real > requirement). All the things taken out were detailed in that list. I'll confess to having not looked at the Handbook in some time, and thought the -committers list was only for those with commit privs (which is, not me); thanks for the info. I've been relying on stuff sent to -current to tell me when it's safe to do a "make world"... :-) I did get to the CVS repository via the web, and found what I was looking for, though it'd be cool if I could just say "show me a list of everything that's been deleted". Thanks, --Pat. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 10:49:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01983 for freebsd-current-outgoing; Mon, 28 Dec 1998 10:49:52 -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 KAA01978 for ; Mon, 28 Dec 1998 10:49:51 -0800 (PST) (envelope-from ixkatl@yahoo.com) Message-ID: <19981228185035.9544.rocketmail@send104.yahoomail.com> Received: from [166.97.171.242] by send104.yahoomail.com; Mon, 28 Dec 1998 10:50:35 PST Date: Mon, 28 Dec 1998 10:50:35 -0800 (PST) From: Andrew Sherrod Subject: Re: So, exactly what *was* purged? 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 Out of curiosity, how does one subscribe to -commit? Majordomo says it is a closed list and provides a contact email address which rejects my messages. ---Chuck Robey wrote: > > On Mon, 28 Dec 1998, Pat Barron wrote: > > > I know someone asked this, but I have not seen an answer: Could someone > > provide a list of exactly what was purged? It would be handy to know > > things like, "this was purged, and is absolutely *not* coming back", or > > "this was purged, but is being considered for reinstatement", but what I > > really want to know is *exactly* what is now (today) gone, that used to be > > there. > > > > BTW, I note that these items were said to be moved "to the attic"? My > > apologies if this is in a FAQ somewhere, but is this mythical "attic" of > > cast-off FreeBSD pieces accessible to the public? If so, how/where? > > If you're tracking current, then you're supposed to also monitor the > FreeBSD-committers list (it says this in the Handbook, and it's a real > requirement). All the things taken out were detailed in that list. > > Attic (with the capital A) is the directory created by cvs to store > stuff that's been deleted. cvs itself never forgets anything, it just > no longer retrieves that, when you check out a copy of current from your > archive. cvs will happily give out the older stuff, if you use the > right date or release code. > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (NetBSD). > ----------------------------+----------------------------------------------- > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > _________________________________________________________ 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 Mon Dec 28 11:00:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03071 for freebsd-current-outgoing; Mon, 28 Dec 1998 11:00:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03030 for ; Mon, 28 Dec 1998 11:00:26 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id CAA67283; Tue, 29 Dec 1998 02:59:48 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812281859.CAA67283@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Alfred Perlstein cc: Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? In-reply-to: Your message of "Mon, 28 Dec 1998 13:30:54 EST." Date: Tue, 29 Dec 1998 02:59:47 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > On Mon, 28 Dec 1998, Pat Barron wrote: > > > I know someone asked this, but I have not seen an answer: Could someone > > provide a list of exactly what was purged? It would be handy to know > > things like, "this was purged, and is absolutely *not* coming back", or > > "this was purged, but is being considered for reinstatement", but what I > > really want to know is *exactly* what is now (today) gone, that used to be > > there. > > voxware, lkms, vinum(an lkm) - DSI_SOFT_MODEM - bqu driver - 3c505 (note, *NOT* 3c905) - pcvt - broken (not updated for CAM) scsi drivers: nca, sea, wds, uha - ft - wcd (use acd instead) - voxware - lkm building (all lkm's have a corresponding kld) The vinum KLD module was accidently broken - it shared it's sources with the LKM. And 10 points to the first person who can tell me what 'bqu' was without looking it up. :-) > voxware may come back, vinum is definetly coming back as kld The jury is out on pcvt and voxware.. My feeling is that there's more than enough support for both to revive them. Vinum is already fixed (I hope), and should also now support being compiled into the kernel ("pseudo-device vinum") as well. > basically klms which have been deemed bad by -core are gone, as well as > voxware. LKM's have been deemed sub-optimal by just about everyone. We are in a situation where the KLD system is a superset of LKM's and it's a lot of work duplicating effort to keep LKM's working. LKM's are a.out only while KLD's are a.out and ELF, and both formats work on either format kernel.. KLD's work with DDB, KLD's can be auto-loaded by the kernel (and are already for filesystems). While I'd have liked the LKM retirement to be a little more peaceful and with more warning, I'm not all that sad that support has gone for building new LKMs that have already got *working* KLD equivalents. I for one would like to remove kernel support for LKM's as well. Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 11:01:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03535 for freebsd-current-outgoing; Mon, 28 Dec 1998 11:01:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03476 for ; Mon, 28 Dec 1998 11:01:07 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA185350525; Mon, 28 Dec 1998 08:08:45 -0500 Date: Mon, 28 Dec 1998 08:08:45 -0500 (EST) From: Bill Fumerola To: Chuck Robey Cc: Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? 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, 28 Dec 1998, Chuck Robey wrote: > If you're tracking current, then you're supposed to also monitor the > FreeBSD-committers list (it says this in the Handbook, and it's a real > requirement). All the things taken out were detailed in that list. s/FreeBSD-committers/cvs-all > Attic (with the capital A) is the directory created by cvs to store > stuff that's been deleted. cvs itself never forgets anything, it just > no longer retrieves that, when you check out a copy of current from your > archive. cvs will happily give out the older stuff, if you use the > right date or release code. True. Contrary to the original post, there is no mystic voodoo chant to retrieve these files. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 11:01:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03798 for freebsd-current-outgoing; Mon, 28 Dec 1998 11:01:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03750 for ; Mon, 28 Dec 1998 11:01:52 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA185400580; Mon, 28 Dec 1998 08:09:40 -0500 Date: Mon, 28 Dec 1998 08:09:39 -0500 (EST) From: Bill Fumerola To: Andrew Sherrod Cc: current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? In-Reply-To: <19981228185035.9544.rocketmail@send104.yahoomail.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 You don't. He meant the 'cvs-all', which -committers is subscribed to. On Mon, 28 Dec 1998, Andrew Sherrod wrote: > Out of curiosity, how does one subscribe to -commit? > Majordomo says it is a closed list and provides a contact email > address which rejects my messages. - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 11:10:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05006 for freebsd-current-outgoing; Mon, 28 Dec 1998 11:10:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04919 for ; Mon, 28 Dec 1998 11:09:59 -0800 (PST) (envelope-from girgen@partitur.se) Received: from partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id UAA20052; Mon, 28 Dec 1998 20:09:29 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <3687D766.A56CB6F0@partitur.se> Date: Mon, 28 Dec 1998 20:09:26 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: sv,en MIME-Version: 1.0 To: "John W. DeBoskey" CC: freebsd-current@FreeBSD.ORG Subject: Re: make world (aout lkm broken) References: <199812281547.KAA16807@bb01f39.unx.sas.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! I removed /usr/src/lkm, re-cvsupped, made clean, amd remade. It walks past the lkm (it's removed completely in current as of a few days ago). I have other problems, though: cc -O -pipe -DYP -I/usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc -I/usr/obj/aout/disk3/src/tmp/usr/include -I/usr/obj/aout/disk3/src/tmp/usr/include -c nfs_prot_xdr.c -o nfs_prot_xdr.o In file included from nfs_prot_xdr.c:6: /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse error before `uint64' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: parse error before `int64' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: parse error before `fileid3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: parse error before `cookie3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:291: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:291: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:293: parse error before `offset3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:293: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:369: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:369: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:370: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:372: parse error before `fsid' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:372: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:373: parse error before `fileid' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:373: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:376: `ctime' redeclared as different kind of symbol /usr/obj/aout/disk3/src/tmp/usr/include/time.h:126: previous declaration of `ctime' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:377: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:383: field `attributes' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:389: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:389: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:392: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:398: field `attributes' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:452: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:453: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:476: field `size' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:494: field `obj_attributes' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:625: parse error before `offset3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:625: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:627: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:664: parse error before `offset3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:664: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:671: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:945: parse error before `cookie3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:945: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:948: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:952: parse error before `fileid3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:952: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:954: parse error before `cookie' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:954: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:956: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:988: parse error before `cookie3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:988: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:992: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:996: parse error before `fileid3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:996: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:998: parse error before `cookie' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:998: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1001: conflicting types for `nextentry' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:955: previous declaration of `nextentry' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1002: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1039: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1039: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1040: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1041: parse error before `abytes' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1041: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1042: parse error before `tfiles' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1042: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1043: parse error before `ffiles' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1043: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1044: parse error before `afiles' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1044: warning: data definition has no type or storage class /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1046: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1057: field `resok' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1081: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1081: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1084: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1095: field `resok' has incomplete type /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1133: parse error before `offset3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1133: warning: no semicolon at end of struct or union /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1135: parse error before `}' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1450: parse error before `uint64' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1451: parse error before `int64' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1456: parse error before `fileid3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1457: parse error before `cookie3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1463: parse error before `size3' /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:1464: parse error before `offset3' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 "John W. DeBoskey" wrote: > > Hi, > > I think the following says it all... current as of 10:20am EST. > I don't see any commits to fix this in the last hour... > > -------------------------------------------------------------- > >>> Rebuilding the aout obj tree > -------------------------------------------------------------- > cd /usr/src; PATH=/usr/obj/elf/usr/src/tmp/sbin:/usr/obj/elf/usr/src/tmp/usr/sbin:/usr/obj/elf/usr/src/tmp/bin:/usr/obj/elf/usr/src/tmp/usr/bin BISON_SIMPLE=/usr/obj/elf/usr/src/tmp/usr/share/misc/bison.simple COMPILER_PATH=/usr/obj/elf/usr/src/tmp/usr/libexec:/usr/obj/elf/usr/src/tmp/usr/bin GCC_EXEC_PREFIX=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib/ LD_LIBRARY_PATH=/usr/obj/elf/usr/src/tmp/usr/lib/aout LIBRARY_PATH=/usr/obj/aout/usr/src/tmp/usr/lib/aout:/usr/obj/aout/usr/src/tmp/usr/lib OBJFORMAT_PATH=/usr/obj/elf/usr/src/tmp/usr/libexec CFLAGS="-nostdinc -O -pipe" /usr/obj/elf/usr/src/tmp/usr/bin/make DESTDIR=/usr/obj/aout/usr/src/tmp -f Makefile.inc1 par-obj > ===> share/info > . > . > . > . > ===> secure/usr.bin > ===> secure/usr.bin/bdes > ===> lkm > cd: can't cd to /usr/src/lkm > *** Error code 2 > > Stop. > *** Error code 1 > > Thanks! > John > > 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 28 11:32:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07304 for freebsd-current-outgoing; Mon, 28 Dec 1998 11:32:24 -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 LAA07295 for ; Mon, 28 Dec 1998 11:32:22 -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 0zuiOU-00068H-00; Mon, 28 Dec 1998 12:31:58 -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 MAA09739; Mon, 28 Dec 1998 12:30:03 -0700 (MST) Message-Id: <199812281930.MAA09739@harmony.village.org> To: Greg Lehey Subject: Re: Thanks, Core Team Cc: FreeBSD current users In-reply-to: Your message of "Mon, 28 Dec 1998 11:28:51 +1030." <19981228112851.Y12346@freebie.lemis.com> References: <19981228112851.Y12346@freebie.lemis.com> Date: Mon, 28 Dec 1998 12:30:03 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : > -committers is a notorious unproductive and flame-prone place to : > discuss code removal. I have to ***STRONGLY*** disagree with this sentement. -committers has been, at times, flame prone. However, many times when I have asked for feedback in -committers there is enough good information generated, even if there is some flamage. -current is by far much worse than -committers. Personally, I think that *ANY* major changes should be talked about in at least -committers. It is a small enough group to have a high enough signal to noise ratio, and a large enough group to get a meaningfully good responses. And if people start to flame or get off into the weeds on -committers, then other committers should tell them so. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 11:37:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07961 for freebsd-current-outgoing; Mon, 28 Dec 1998 11:37:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07954; Mon, 28 Dec 1998 11:37:11 -0800 (PST) (envelope-from jmb) Date: Mon, 28 Dec 1998 11:37:11 -0800 (PST) Message-Id: <199812281937.LAA07954@hub.freebsd.org> From: "Jonathan M. Bresler" To: ixkatl@yahoo.com CC: current@FreeBSD.ORG In-reply-to: <19981228185035.9544.rocketmail@send104.yahoomail.com> (message from Andrew Sherrod on Mon, 28 Dec 1998 10:50:35 -0800 (PST)) Subject: Re: So, exactly what *was* purged? References: <19981228185035.9544.rocketmail@send104.yahoomail.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Mon, 28 Dec 1998 10:50:35 -0800 (PST) > From: Andrew Sherrod > Content-Type: text/plain; charset=us-ascii > Sender: owner-freebsd-current@FreeBSD.ORG > Precedence: bulk > X-Loop: FreeBSD.ORG > > Out of curiosity, how does one subscribe to -commit? > Majordomo says it is a closed list and provides a contact email > address which rejects my messages. one does not subscribe to -commit. one subscribes to cvs-all. jmb -- Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG FreeBSD--The Power to Serve JMB193 http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 11:53:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09941 for freebsd-current-outgoing; Mon, 28 Dec 1998 11:53:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09935 for ; Mon, 28 Dec 1998 11:53:44 -0800 (PST) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id UAA20960 for freebsd-current@FreeBSD.ORG; Mon, 28 Dec 1998 20:51:23 +0100 (MET) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id UAA27627; Mon, 28 Dec 1998 20:43:23 +0100 (CET) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199812281943.UAA27627@semyam.dinoco.de> To: freebsd-current@FreeBSD.ORG cc: seggers@semyam.dinoco.de Subject: New boot2 able to boot old -stable from 2nd BSD partition? Date: Mon, 28 Dec 1998 20:43:22 +0100 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! I'd like to use the new boot2 to boot a -stable kernel from the *second* FreeBSD partition. If need be I will modify it to grab the second (active) one instead of the first but what I saw today looks like it can do that already. (*) The interesting questions is if that will work at all. If so I guess /boot/loader will work in that situation, too. As I am at modifying the boot process I can then do it the 3.0 way to give a small taste of the things to come. ;-) Stefan. (*) In case it is already able to do the right thing we should modify boot(8) as soon as we use the new boot blocks as default as that man page says it will boot from the first one only. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 11:56:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11099 for freebsd-current-outgoing; Mon, 28 Dec 1998 11:56:53 -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 LAA11091 for ; Mon, 28 Dec 1998 11:56:51 -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 0zuimB-000698-00; Mon, 28 Dec 1998 12:56:27 -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 MAA10192; Mon, 28 Dec 1998 12:54:28 -0700 (MST) Message-Id: <199812281954.MAA10192@harmony.village.org> To: Poul-Henning Kamp Subject: Re: wanton Atticizing is bad Cc: current@FreeBSD.ORG In-reply-to: Your message of "Sun, 27 Dec 1998 19:25:44 +0100." <68621.914783144@critter.freebsd.dk> References: <68621.914783144@critter.freebsd.dk> Date: Mon, 28 Dec 1998 12:54:28 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <68621.914783144@critter.freebsd.dk> Poul-Henning Kamp writes: : Make DEVFS standard. I'd love to see this happen, but there are problems with the current DEVFS which makes it impossible to use with CAM. It can't handle devices comeing and going at interrupt time, which is how CAM does probing and device removal. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 11:58:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11219 for freebsd-current-outgoing; Mon, 28 Dec 1998 11:58:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from igarber.radical.net (nyc-ip-2-246.ziplink.net [208.196.105.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA11208; Mon, 28 Dec 1998 11:58:27 -0800 (PST) (envelope-from mi@igarber.radical.net) Received: (from mi@localhost) by igarber.radical.net (8.9.1/8.9.1) id TAA07027; Mon, 28 Dec 1998 19:55:11 GMT (envelope-from mi) From: Mikhail Teterin Message-Id: <199812281955.TAA07027@igarber.radical.net> Subject: DSI_SOFT_MODEM!! To: phk@FreeBSD.ORG, current@FreeBSD.ORG Date: Mon, 28 Dec 1998 19:55:07 +0000 (GMT) Reply-To: mi@aldan.algebra.com 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 LAA11265 for freebsd-current-outgoing; Mon, 28 Dec 1998 11:59: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 LAA11253; Mon, 28 Dec 1998 11:59:17 -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 0zuioY-00069L-00; Mon, 28 Dec 1998 12:58:54 -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 MAA10318; Mon, 28 Dec 1998 12:56:59 -0700 (MST) Message-Id: <199812281956.MAA10318@harmony.village.org> Subject: Re: wanton Atticizing is bad To: Poul-Henning Kamp , current@FreeBSD.ORG, sos@FreeBSD.ORG In-reply-to: Your message of "Sun, 27 Dec 1998 13:03:37 EST." References: Date: Mon, 28 Dec 1998 12:56:59 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : > X-ten I'm curious as to why xten is on this list. It appears to be actively maintained and is useful to people. It appears to work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 12:10:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12191 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:10: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 MAA12162 for ; Mon, 28 Dec 1998 12:10:03 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id MAA65389; Mon, 28 Dec 1998 12:09:46 -0800 (PST) (envelope-from dillon) Date: Mon, 28 Dec 1998 12:09:46 -0800 (PST) From: Matthew Dillon Message-Id: <199812282009.MAA65389@apollo.backplane.com> To: FreeBSD current users Subject: Re: Thanks, Core Team Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good god, the freebsd mailing lists have gone insane! And for once it isn't my fault :-) (happily working on a new vm/swap_pager) -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 Mon Dec 28 12:14:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12817 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:14:24 -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 MAA12812 for ; Mon, 28 Dec 1998 12:14:22 -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 PAA87169; Mon, 28 Dec 1998 15:13:52 -0500 (EST) (envelope-from gjp@gjp.erols.com) To: Brian Feldman cc: Pat Barron , current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: So, exactly what *was* purged? In-reply-to: Your message of "Mon, 28 Dec 1998 13:30:02 EST." Date: Mon, 28 Dec 1998 15:13:52 -0500 Message-ID: <87165.914876032@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Feldman wrote in message ID : > 3c905 driver I hope you mean 3c505. Otherwise a certain Bill Paul is going to be rightly pissed. 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 28 12:20:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13443 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:20:47 -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 MAA13436 for ; Mon, 28 Dec 1998 12:20:41 -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 VAA18599; Mon, 28 Dec 1998 21:20:15 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA63274; Mon, 28 Dec 1998 21:20:14 +0100 (MET) Message-ID: <19981228212013.J53810@follo.net> Date: Mon, 28 Dec 1998 21:20:13 +0100 From: Eivind Eklund To: Poul-Henning Kamp Cc: bruth@ernie.wmht.org, freebsd-current@FreeBSD.ORG Subject: Re: types.h/controller ahc broken? References: <19981228151627.D53810@follo.net> <73572.914855341@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <73572.914855341@critter.freebsd.dk>; from Poul-Henning Kamp on Mon, Dec 28, 1998 at 03:29:01PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 03:29:01PM +0100, Poul-Henning Kamp wrote: > In message <19981228151627.D53810@follo.net>, Eivind Eklund writes: > >On Mon, Dec 28, 1998 at 03:10:40PM +0100, Poul-Henning Kamp wrote: > >> In message <199812281402.JAA20300@ernie.wmht.org>, "Brian Ruth" writes: > >> >The following smp kernel compiles fine on 3.0-RELEASE but not > >> >under -CURRENT as of 8:30am. Below is the config file and the > >> >error output from a make depend after a make clean. > >> > >> cd /usr/src > >> make includes > > > >This should not be necessary in a normal source tree (if the kernel is > >built from src/sys, with src/include checked out and up to date). In > >this case, the includes should be gotten from src/include and src/sys, > >and if they're not, something in the kernel build is broken. > > It is because the aic assembler picks up stuff here and there as > far as I could figure out when I had the problem. You are right. I now have patches that fix this; I'll throw 'em at Justin as soon as I've verified that nothing is broken (which will happen after I've fixed the rest of the bogosity blocking my builds; parts our build system seems to be falling over under its own weight). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 12:22:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13757 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:22:23 -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 MAA13744 for ; Mon, 28 Dec 1998 12:22:10 -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 VAA18620; Mon, 28 Dec 1998 21:21:49 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA63289; Mon, 28 Dec 1998 21:21:49 +0100 (MET) Message-ID: <19981228212148.K53810@follo.net> Date: Mon, 28 Dec 1998 21:21:48 +0100 From: Eivind Eklund To: Warner Losh , Poul-Henning Kamp Cc: current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad References: <68621.914783144@critter.freebsd.dk> <199812281954.MAA10192@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812281954.MAA10192@harmony.village.org>; from Warner Losh on Mon, Dec 28, 1998 at 12:54:28PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 12:54:28PM -0700, Warner Losh wrote: > In message <68621.914783144@critter.freebsd.dk> Poul-Henning Kamp writes: > > Make DEVFS standard. > > I'd love to see this happen, but there are problems with the current > DEVFS which makes it impossible to use with CAM. It can't handle > devices comeing and going at interrupt time, which is how CAM does > probing and device removal. Julian claimed to have fixed this (but not yet committed the fixes) at the time phk and sos last bloodied their axes (by murdering the partially working version of SLICE). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 12:28:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14345 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:28:59 -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 MAA14337 for ; Mon, 28 Dec 1998 12:28:57 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.0]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAAF2E; Mon, 28 Dec 1998 21:28:39 +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: <3687D766.A56CB6F0@partitur.se> Date: Mon, 28 Dec 1998 21:35:26 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Palle Girgensohn Subject: Re: make world (aout lkm broken) Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Dec-98 Palle Girgensohn wrote: > Hi! > > I removed /usr/src/lkm, re-cvsupped, made clean, amd remade. It walks > past the lkm (it's removed completely in current as of a few days ago). > I have other problems, though: > > cc -O -pipe -DYP -I/usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc > -I/usr/obj/aout/disk3/src/tmp/usr/include > -I/usr/obj/aout/disk3/src/tmp/usr/include -c nfs_prot_xdr.c -o > nfs_prot_xdr.o > In file included from nfs_prot_xdr.c:6: > /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse > error before `uint64' Either rm the file and cvsup again or try to make && make install lex and yacc by hand. I solved a similar problem with it... HTH, --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... 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 Mon Dec 28 12:36:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15124 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:36:17 -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 MAA15117 for ; Mon, 28 Dec 1998 12:36:15 -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 VAA18807; Mon, 28 Dec 1998 21:35:54 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA63353; Mon, 28 Dec 1998 21:35:54 +0100 (MET) Message-ID: <19981228213553.N53810@follo.net> Date: Mon, 28 Dec 1998 21:35:53 +0100 From: Eivind Eklund To: Jeroen Ruigrok/Asmodai , Palle Girgensohn Cc: freebsd-current@FreeBSD.ORG Subject: Re: make world (aout lkm broken) References: <3687D766.A56CB6F0@partitur.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Mon, Dec 28, 1998 at 09:35:26PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 09:35:26PM +0100, Jeroen Ruigrok/Asmodai wrote: > On 28-Dec-98 Palle Girgensohn wrote: > > Hi! > > > > I removed /usr/src/lkm, re-cvsupped, made clean, amd remade. It walks > > past the lkm (it's removed completely in current as of a few days ago). > > I have other problems, though: > > > > cc -O -pipe -DYP -I/usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc > > -I/usr/obj/aout/disk3/src/tmp/usr/include > > -I/usr/obj/aout/disk3/src/tmp/usr/include -c nfs_prot_xdr.c -o > > nfs_prot_xdr.o > > In file included from nfs_prot_xdr.c:6: > > /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse > > error before `uint64' > > Either rm the file and cvsup again > > or try to make && make install lex and yacc by hand. I solved a > similar problem with it... This problem is due to rpcgen being severely out of date, and somebody breaking the search for the freshly built rpcgen in 'make buildworld'. I've not yet traced down exactly why or when the search was broken, but it probably needs to be fixed if upgrades from old -currents or from -stable are to work. Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 12:40:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15778 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:40:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA15748 for ; Mon, 28 Dec 1998 12:40:36 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.0/8.9.0) with SMTP id XAA21297; Mon, 28 Dec 1998 23:39:43 +0300 (MSK) Date: Mon, 28 Dec 1998 23:39:43 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: Brian Feldman cc: Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? 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, 28 Dec 1998, Brian Feldman wrote: > Date: Mon, 28 Dec 1998 13:30:02 -0500 (EST) > From: Brian Feldman > To: Pat Barron > Cc: current@FreeBSD.ORG > Subject: Re: So, exactly what *was* purged? > > On Mon, 28 Dec 1998, Pat Barron wrote: > > > I know someone asked this, but I have not seen an answer: Could someone > > provide a list of exactly what was purged? It would be handy to know > > things like, "this was purged, and is absolutely *not* coming back", or > > "this was purged, but is being considered for reinstatement", but what I > > really want to know is *exactly* what is now (today) gone, that used to be > > there. > > Off the top of my head, it was: > VoxWare > floppy tape driver ^^^^^^^^^^^^^^^^^^^ ft*? Why? I'am still using it. > 3c905 driver ^^^^^^ Really??? > old ATAPI CD driver > PCVT > > I have no idea if any are coming back, although there's a great amount of > people wanting VoxWare if nothing else. > > > > > BTW, I note that these items were said to be moved "to the attic"? My > > apologies if this is in a FAQ somewhere, but is this mythical "attic" of > > cast-off FreeBSD pieces accessible to the public? If so, how/where? > > > > When something is deleted in CVS, it is moved to the Attic, where it's no > longer checked out, but still accessible. Nothing is ever truly purged, usually. > > > Thanks, > > --Pat. > > > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > 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 28 12:44:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16922 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:44:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thor.pcc.edu (thor.oci.pcc.edu [198.106.46.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16917 for ; Mon, 28 Dec 1998 12:44:56 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from c063.beaverton.stream.com ([208.13.191.137]) by thor.pcc.edu (8.8.5/8.8.5) with SMTP id NAA28676; Mon, 28 Dec 1998 13:52:09 -0800 Message-ID: <004701be32a2$5de60900$f301040a@c063.beaverton.stream.com> From: "Wiliam Woods" To: "Dmitry Valdov" , "Brian Feldman" Cc: "Pat Barron" , Subject: Re: So, exactly what *was* purged? Date: Mon, 28 Dec 1998 12:40:34 -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.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> floppy tape driver > > ^^^^^^^^^^^^^^^^^^^ >ft*? Why? I'am still using it. As am I whats with this..... >> 3c905 driver > > ^^^^^^ >Really??? And here to, what now, buy a new card??? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 12:50:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17614 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:50:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp02.wxs.nl (smtp02.wxs.nl [195.121.6.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17609 for ; Mon, 28 Dec 1998 12:50:56 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.0]) by smtp02.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA4A45; Mon, 28 Dec 1998 21:50:32 +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: <199812281443.JAA16653@bb01f39.unx.sas.com> Date: Mon, 28 Dec 1998 21:57:17 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: "John W. DeBoskey" Subject: RE: The Great FreeBSD Purge: A suggestion Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Dec-98 John W. DeBoskey wrote: > Before purging code from the system, that code should be tagged > as to be deleted, and messages at boot time should be displayed > warning the user about what will be happenning with the NEXT > release of the software... Sorry, this will either be very annoying as some people do a make world every day, others once in the month. Imagine looking at the warnings again and again for a month. Not to mention the extra effort and overhead this will generate. > Assuming the psm device was targetted for removal: > > psm0 at 0x60-0x64 irq 12 on motherboard > psm0: model Generic PS/2 mouse, device ID 0 > psm0: WARNING: this device is scheduled for removal in release x.y.z. > psm0: WARNING: Please see 'man 4 abc' for a replacement. > > Basically, what it boils down to, is none of you (us, though > I am not a committer) knows how people use FreeBSD, what devices > they have configured into their kernels, and which they don't. Well, most of the drivers that were removed were either drivers that were outdated, or suffering from bitrot... > Those benefits I spoke of? The user community (all of us, even > you the developers) will know what code is scheduled for removal > from the system. You will not take those users by surprise when > they install the latest release only to discover that their > xyz0 hardware nolonger works. > > To the developer? You now have a well scheduled date/release > at which you may purge code. Your target user audience knows the > code will be removed, and the amount of hassle associated with > that removal is reduced. Then I would be in favor of something on the web. Much easier to change around for all to see... > I am not the only person who uses FreeBSD in a production > environment. You have purged working code from the system which > I will now have to figure out how to replace and then validate > in our processes. Making sure new code doesn't fall over under > heavy load or stress conditions is not a simple process. I would > think that many of you with your experience over the years would > realize this. Production machines almost never run CURRENT =P > ps: Why not have a freebsd-kernelconf mailing list which is a frontend > to a service which reads a mailed in kernel configuration file and > keeps a tally of which devices are used and in what percentages? Now that's a more interesting idea, if it were only for the tallying of what systems FreeBSD runs on... Mayhaps adding a detailed setup as well? --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... 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 Mon Dec 28 12:53:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17886 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:53:22 -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 MAA17877 for ; Mon, 28 Dec 1998 12:53:19 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.0]) by smtp04.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA1FA4; Mon, 28 Dec 1998 21:52:52 +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: <004701be32a2$5de60900$f301040a@c063.beaverton.stream.com> Date: Mon, 28 Dec 1998 21:59:39 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Wiliam Woods Subject: Re: So, exactly what *was* purged? Cc: current@FreeBSD.ORG, Pat Barron , Brian Feldman , Dmitry Valdov Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Dec-98 Wiliam Woods wrote: >>> 3c905 driver >> >> ^^^^^^ >>Really??? No, 3c505 --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... 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 Mon Dec 28 12:53:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17938 for freebsd-current-outgoing; Mon, 28 Dec 1998 12:53:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17929 for ; Mon, 28 Dec 1998 12:53:37 -0800 (PST) (envelope-from erikf@visi.com) Received: from odin (h-176-169.mn.mediaone.net [209.32.176.169]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id PAA05866 for ; Mon, 28 Dec 1998 15:53:17 -0500 (EST) Message-ID: <00fc01be32a4$7346d5c0$0200a8c0@mn.mediaone.net> From: "Erik Funkenbusch" To: Subject: comsat and sendmail msgs Date: Mon, 28 Dec 1998 14:55:49 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently started getting messages showing up of the type: inetd[152]: /usr/libexec/comsat[3629]: exit status 0xb I've also been getting messages such as this: inetd[152]: comsat/udp server failing (looping), service terminated I've also seen some similar messages relating to sendmail and inetd: /kernel: pid (sendmail), uid 0, exited on signal 11 finally, maillog contains this message: sendmail[3047]: alias database /etc/aliases.db out of date I can't seem to find any references t aliases.db and it doesn't exist in /usr/src/etc. Any ideas about these issues? I'm not sure when they started, but it hasn't been too long (probably a week or two). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 13:06:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19614 for freebsd-current-outgoing; Mon, 28 Dec 1998 13:06:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19517 for ; Mon, 28 Dec 1998 13:06:01 -0800 (PST) (envelope-from girgen@partitur.se) Received: from partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id WAA20809; Mon, 28 Dec 1998 22:05:40 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <3687F2A1.B5012D48@partitur.se> Date: Mon, 28 Dec 1998 22:05:37 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.5 [en] (X11; I; SunOS 5.6 sun4u) X-Accept-Language: sv,en MIME-Version: 1.0 To: Jeroen Ruigrok/Asmodai CC: freebsd-current@FreeBSD.ORG Subject: Re: make world (aout lkm broken) References: 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 wrote: > > On 28-Dec-98 Palle Girgensohn wrote: > > Hi! > > > > I removed /usr/src/lkm, re-cvsupped, made clean, amd remade. It walks > > past the lkm (it's removed completely in current as of a few days ago). > > I have other problems, though: > > > > cc -O -pipe -DYP -I/usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc > > -I/usr/obj/aout/disk3/src/tmp/usr/include > > -I/usr/obj/aout/disk3/src/tmp/usr/include -c nfs_prot_xdr.c -o > > nfs_prot_xdr.o > > In file included from nfs_prot_xdr.c:6: > > /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse > > error before `uint64' > > Either rm the file and cvsup again > > or try to make && make install lex and yacc by hand. I solved a similar problem > with it... > > HTH, > Thanks for the suggestion. Problem is I'm trying to make this system go from 2.2.7 stable as of mid-October, directly to current as of today (so I can't do manual installs as suggested right now...). My move just *might* be to too optimistic, though :-) so I'll to get the 3_0_0_RELEASE installed first, and move on from there... I did try removing and cvsupping, and it didn't help me. /Palle > --- > Jeroen Ruigrok van der Werven Life is the only Pain > asmodai(at)wxs.nl we endeavour... > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 13:10:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20374 for freebsd-current-outgoing; Mon, 28 Dec 1998 13:10:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20349; Mon, 28 Dec 1998 13:10:21 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id QAA01592; Mon, 28 Dec 1998 16:10:08 -0500 (EST) Date: Mon, 28 Dec 1998 16:10:08 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Gary Palmer cc: Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? In-Reply-To: <87165.914876032@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, 28 Dec 1998, Gary Palmer wrote: > Brian Feldman wrote in message ID > : > > 3c905 driver > > I hope you mean 3c505. Otherwise a certain Bill Paul is going to be > rightly pissed. Whoops, I mistyped ;) My goof! > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Mon Dec 28 13:14:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20959 for freebsd-current-outgoing; Mon, 28 Dec 1998 13:14:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp03.wxs.nl (smtp03.wxs.nl [195.121.6.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20954 for ; Mon, 28 Dec 1998 13:14:16 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.0]) by smtp03.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA125B for ; Mon, 28 Dec 1998 22:13:58 +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 Date: Mon, 28 Dec 1998 22:20:46 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: FreeBSD Current Subject: ZIP driver Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ehm, while we're on the subject, whatever did happen with the ZIP(+) driver? Somewhere along the line of commits did it break and unfortunately I only noticed this when I needed it... The boot reports all the devices getting probed alright, except for da2 which was normally my ZIP drive (and yes, it's on and has a disk in it ;) thanks, --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... 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 Mon Dec 28 13:17:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21318 for freebsd-current-outgoing; Mon, 28 Dec 1998 13:17:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21313 for ; Mon, 28 Dec 1998 13:17:07 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id QAA01757; Mon, 28 Dec 1998 16:16:49 -0500 (EST) Date: Mon, 28 Dec 1998 16:16:49 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Dmitry Valdov cc: Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? 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, 28 Dec 1998, Dmitry Valdov wrote: > > > On Mon, 28 Dec 1998, Brian Feldman wrote: > > > Date: Mon, 28 Dec 1998 13:30:02 -0500 (EST) > > From: Brian Feldman > > To: Pat Barron > > Cc: current@FreeBSD.ORG > > Subject: Re: So, exactly what *was* purged? > > > > On Mon, 28 Dec 1998, Pat Barron wrote: > > > > > I know someone asked this, but I have not seen an answer: Could someone > > > provide a list of exactly what was purged? It would be handy to know > > > things like, "this was purged, and is absolutely *not* coming back", or > > > "this was purged, but is being considered for reinstatement", but what I > > > really want to know is *exactly* what is now (today) gone, that used to be > > > there. > > > > Off the top of my head, it was: > > VoxWare > > floppy tape driver > > ^^^^^^^^^^^^^^^^^^^ > ft*? Why? I'am still using it. > > > 3c905 driver > > ^^^^^^ > Really??? No, my fault for the BAD typo! I meant to type 3c505 :) > > > old ATAPI CD driver > > PCVT > > > > I have no idea if any are coming back, although there's a great amount of > > people wanting VoxWare if nothing else. > > > > > > > > BTW, I note that these items were said to be moved "to the attic"? My > > > apologies if this is in a FAQ somewhere, but is this mythical "attic" of > > > cast-off FreeBSD pieces accessible to the public? If so, how/where? > > > > > > > When something is deleted in CVS, it is moved to the Attic, where it's no > > longer checked out, but still accessible. Nothing is ever truly purged, usually. > > > > > Thanks, > > > --Pat. > > > > > > > Brian Feldman _ __ ___ ___ ___ > > green@unixhelp.org _ __ ___ | _ ) __| \ > > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > > FreeBSD: The Power to Serve! _ __ ___ ____ _____ |___/___/___/ > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Mon Dec 28 13:23:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA22394 for freebsd-current-outgoing; Mon, 28 Dec 1998 13:23:49 -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 NAA22384 for ; Mon, 28 Dec 1998 13:23:45 -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 QAA19953 for ; Mon, 28 Dec 1998 16:27:32 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 28 Dec 1998 16:27:32 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: current@FreeBSD.ORG Subject: make buildworld broken on /usr/src/sys/modules/syscons/logo/ 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 make buildworld -j4 -DNOAOUT -DNOPROFILE -DNOSENDMAIL -DNOGAMES breaks while compiling /usr/src/sys/modules/syscons/logo/logo_saver.c it's unable to find "logo.c" which is in the same directory. as a side note, looking at logo.c, it seems to be some bitmap graphics wouldn't it make more sense to include those as .uu (uuencoded files) and then something like: cat skel_1.c > outfile uudecode < file.format | hexdump -v -e ' 8/1 "0x%02x, " "\n"' >> outfile cat skel_2.c >> outfile uudecode < file2.format | hexdump -v -e ' 8/1 "0x%02x, " "\n"' >> outfile cat skel_3.c >> outfile ? in case someone wanted to customize the graphic. there's probably a better way to do this, but i haven't figured it out. if it's a hand done array i apologize, but it seems to be the output of _some_ image program and i've noticed that when binary data is needed it's usually uudecoded.... it's also smaller in uuencode format :) on a side note, why are screensavers of all things being made into kernel modules, can't syscons exec a userland program? "ugh my screensaver crashed my machine" :) thanks, Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 13:29:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23507 for freebsd-current-outgoing; Mon, 28 Dec 1998 13:29:35 -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 NAA23498 for ; Mon, 28 Dec 1998 13:29:31 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from chronias.ninth-circle.org ([195.121.57.0]) by smtp05.wxs.nl (Netscape Messaging Server 3.6) with ESMTP id AAA5C54; Mon, 28 Dec 1998 22:29:13 +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: Mon, 28 Dec 1998 22:36:01 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Alfred Perlstein Subject: RE: make buildworld broken on /usr/src/sys/modules/syscons/logo/ Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Dec-98 Alfred Perlstein wrote: > > make buildworld -j4 -DNOAOUT -DNOPROFILE -DNOSENDMAIL -DNOGAMES > > breaks while compiling > /usr/src/sys/modules/syscons/logo/logo_saver.c > > it's unable to find "logo.c" which is in the same directory. That was commited by DES somewhere around 17:00 here (GMT+1). Ye might want to cvsup again as ye might be caught between updates... --- Jeroen Ruigrok van der Werven Life is the only Pain asmodai(at)wxs.nl we endeavour... 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 Mon Dec 28 13:41:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25945 for freebsd-current-outgoing; Mon, 28 Dec 1998 13:41:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from seerajeane.ia.cp (redion.nttmcl.com [216.69.69.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25931 for ; Mon, 28 Dec 1998 13:41:04 -0800 (PST) (envelope-from gene@nttmcl.com) Received: from localhost (gene@localhost) by seerajeane.ia.cp (8.9.1/8.9.1) with ESMTP id NAA06293 for ; Mon, 28 Dec 1998 13:39:30 -0800 (PST) (envelope-from gene@nttmcl.com) X-Authentication-Warning: seerajeane.ia.cp: gene owned process doing -bs Date: Mon, 28 Dec 1998 13:39:28 -0800 (PST) From: "Eugene M. Kim" X-Sender: gene@seerajeane.ia.cp To: FreeBSD-current Mailing List Subject: Setting securelevel Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, In init(8) it is said that init can lower the security level, and src/sbin/init/init.c has the code to lower the security level back to zero in single-user mode. However, it doesn't seem that the kernel allows the security level to be lowered even if init requests it. (See (rev 1.16 of) src/sys/kern/kern_mib.c around line 130 -- the caller's pid isn't checked.) This, in consequence, prohibits the kernel from returning to the insecure mode even in the single-user mode. Is this a known problem, or did I miss something? I tried searching through the PR database but couldn't find any relevant records. Thank you, Eugene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 13:51:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27673 for freebsd-current-outgoing; Mon, 28 Dec 1998 13:51:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gilgamesch.bik-gmbh.de (gilgamesch.bik-gmbh.de [194.233.237.91]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27645 for ; Mon, 28 Dec 1998 13:51:03 -0800 (PST) (envelope-from cracauer@gilgamesch.bik-gmbh.de) Received: (from cracauer@localhost) by gilgamesch.bik-gmbh.de (8.8.8/8.7.3) id WAA12053; Mon, 28 Dec 1998 22:50:33 +0100 (MET) Message-ID: <19981228225033.A12045@cons.org> Date: Mon, 28 Dec 1998 22:50:33 +0100 From: Martin Cracauer To: Warner Losh Cc: FreeBSD current users Subject: Re: Thanks, Core Team References: <19981228112851.Y12346@freebie.lemis.com> <199812281930.MAA09739@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: <199812281930.MAA09739@harmony.village.org>; from Warner Losh on Mon, Dec 28, 1998 at 12:30:03PM -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In <199812281930.MAA09739@harmony.village.org>, Warner Losh wrote: > : > -committers is a notorious unproductive and flame-prone place to > : > discuss code removal. > > I have to ***STRONGLY*** disagree with this sentement. -committers > has been, at times, flame prone. However, many times when I have > asked for feedback in -committers there is enough good information > generated, even if there is some flamage. What about our new moderated list, freebsd-arch? So far noone ever prooved if Eivind can take the load :-] Martin -- %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Martin Cracauer http://www.cons.org/cracauer BSD User Group Hamburg, Germany http://www.bsdhh.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 13:55:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27989 for freebsd-current-outgoing; Mon, 28 Dec 1998 13:55:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27979 for ; Mon, 28 Dec 1998 13:55:03 -0800 (PST) (envelope-from erikf@visi.com) Received: from odin (h-178-79.mn.mediaone.net [209.32.178.79]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id QAA08488 for ; Mon, 28 Dec 1998 16:54:43 -0500 (EST) Message-ID: <002b01be32ad$08556de0$0200a8c0@mn.mediaone.net> From: "Erik Funkenbusch" To: Subject: sendmail.cf? Date: Mon, 28 Dec 1998 15:57:14 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I guess sendmail was updated recently and now supports a new version of the sendmail.cf file. I've been trying to figure out how to rebuild this file, but can't seem to find the original source file that it is created from. sendmail.cf seems to indicate it was built out of directory /usr/src/usr.sbin/sendmail/cf/cf but there is no cf directory under sendmail in the tree. Anyone know where the default .m4 file is that sendmail.cf is built from? (I suppose this would be better asked in freebsd-questions, but since this is a recent -current related problem i figured there be more help here) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 13:58:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA28401 for freebsd-current-outgoing; Mon, 28 Dec 1998 13:58:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ywing.creative.net.au (flannan.keble.ox.ac.uk [163.1.137.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA28385 for ; Mon, 28 Dec 1998 13:58:18 -0800 (PST) (envelope-from adrian@ywing.creative.net.au) Received: from ywing.creative.net.au (localhost.speedport.net [127.0.0.1] (may be forged)) by ywing.creative.net.au (8.8.8/8.8.8) with ESMTP id WAA01206 for ; Mon, 28 Dec 1998 22:57:37 +0100 (CET) Message-Id: <199812282157.WAA01206@ywing.creative.net.au> To: freebsd-current@FreeBSD.ORG Subject: Re: IPFILTER/IPFW (was Re: wanton Atticizing is bad) In-reply-to: Your message of "Mon, 28 Dec 1998 09:52:26 EST." <19981228095226.B1333@ns1.adsu.bellsouth.com> Date: Mon, 28 Dec 1998 22:57:33 +0100 From: Adrian Chadd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Kuhtz writes: >On Mon, Dec 28, 1998 at 08:54:56AM -0500, Matt Behrens wrote: >> : > "transproxy - transparently proxy HTTP and other requests. >> : > This program is used with Darren Reed's IPFILTER package and used >> : > to intercept things like http requests and divert them to a www proxy server >> : > (eg: squid), without requiring user intervention or configuration." >> >> : You can do that with natd. >> >> You can create the same effect, but lose all of squid's extra >> benefits like caching. I have also noticed that ppp -alias (which >> uses the same code as natd, AFAIR) fails to submit some forms >> properly using Netscape on a Windows box (probably Netscape's >> fault). This bug might be long-gone though :) > >So, the feature you're really looking for is 'transparent redirection', >correct? Very much like all the other (supposedly) 'layer 4 switching' widgets >out there (e.g., Alteon, etc). > >'Transparent redirection' is disjoint from 'transparent proxy'. You can have >a 'transparent proxy' which does not do 'transparent redirection'. You can do transparent redirection in -current . Take a look at the ipfw command 'fw', which lets you map a connection to another IP/port. its the same as the linux transparent redirection, which squid supports right. And yes, you can cache too with it. And yes, its a damn sight neater than using natd :) Just look at the squid FAQ on how to configure transparent redirection, there might even be a section in there for FreeBSD w/ ipfw 'fw' if memory serves right. -- Adrian Chadd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 14:03:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28964 for freebsd-current-outgoing; Mon, 28 Dec 1998 14:03:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28955; Mon, 28 Dec 1998 14:03:54 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id RAA07254; Mon, 28 Dec 1998 17:03:36 -0500 (EST) Message-ID: <19981228170336.Z1333@ns1.adsu.bellsouth.com> Date: Mon, 28 Dec 1998 17:03:36 -0500 From: Christian Kuhtz To: Adrian Chadd , freebsd-current@FreeBSD.ORG Subject: Re: IPFILTER/IPFW (was Re: wanton Atticizing is bad) References: <19981228095226.B1333@ns1.adsu.bellsouth.com> <199812282157.WAA01206@ywing.creative.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812282157.WAA01206@ywing.creative.net.au>; from Adrian Chadd on Mon, Dec 28, 1998 at 10:57:33PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 10:57:33PM +0100, Adrian Chadd wrote: > its the same as the linux transparent redirection, which squid supports > right. And yes, you can cache too with it. And yes, its a damn sight neater > than using natd :) Well, it doesn't matter what sits at the backend, whether it is squid, Inktomi, NetApp, NetWare5, CacheFlow, what have you.. > Just look at the squid FAQ on how to configure transparent redirection, there > might even be a section in there for FreeBSD w/ ipfw 'fw' if memory serves > right. In other words, we don't need IPFILTER then... Those of you who still think they need IPFILTER, speak up if you disagree. Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 14:05:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29322 for freebsd-current-outgoing; Mon, 28 Dec 1998 14:05:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29316 for ; Mon, 28 Dec 1998 14:05:16 -0800 (PST) (envelope-from psalzman@gamefish.pcola.gulf.net) Received: from localhost (psalzman@localhost) by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id QAA13605; Mon, 28 Dec 1998 16:04:16 -0600 (CST) (envelope-from psalzman@gamefish.pcola.gulf.net) Date: Mon, 28 Dec 1998 16:04:16 -0600 (CST) From: Phillip Salzman To: Brian Feldman cc: gmarco@giovannelli.it, current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad 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 > > You can do that with natd. That is possible, but not logical. Say you have 2000 dialup users attempting to access the web at the same time... all coming from different IP addresses -- would you want the packet scanning to go at the Cisco, or at the NATd? Its simple to do a transparent proxy from the cisco, and does not require too much on the squid side (IPFILTER), with less on the router. -- Phillip Salzman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 14:09:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29890 for freebsd-current-outgoing; Mon, 28 Dec 1998 14:09:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA29881 for ; Mon, 28 Dec 1998 14:09:33 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id RAA03406; Mon, 28 Dec 1998 17:09:04 -0500 (EST) Date: Mon, 28 Dec 1998 17:09:04 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Phillip Salzman cc: gmarco@giovannelli.it, current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad 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, 28 Dec 1998, Phillip Salzman wrote: > > > > You can do that with natd. > > That is possible, but not logical. Say you have 2000 > dialup users attempting to access the web at the same time... all > coming from different IP addresses -- would you want the packet > scanning to go at the Cisco, or at the NATd? Its simple to do > a transparent proxy from the cisco, and does not require too much on > the squid side (IPFILTER), with less on the router. I meant that natd could be used along with squid and ipfw divert, handling the packet translation and forwarding/reception. > > -- > Phillip Salzman > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Mon Dec 28 14:12:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00393 for freebsd-current-outgoing; Mon, 28 Dec 1998 14:12:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00346 for ; Mon, 28 Dec 1998 14:12:02 -0800 (PST) (envelope-from psalzman@gamefish.pcola.gulf.net) Received: from localhost (psalzman@localhost) by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id QAA13652; Mon, 28 Dec 1998 16:11:25 -0600 (CST) (envelope-from psalzman@gamefish.pcola.gulf.net) Date: Mon, 28 Dec 1998 16:11:25 -0600 (CST) From: Phillip Salzman To: Brian Feldman cc: Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? 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 > Off the top of my head, it was: > VoxWare > floppy tape driver > 3c905 driver > old ATAPI CD driver > PCVT > IPFILTER too -- Phillip Salzman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 14:15:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00776 for freebsd-current-outgoing; Mon, 28 Dec 1998 14:15:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00771 for ; Mon, 28 Dec 1998 14:15:24 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id RAA07417; Mon, 28 Dec 1998 17:14:01 -0500 (EST) Message-ID: <19981228171401.B1333@ns1.adsu.bellsouth.com> Date: Mon, 28 Dec 1998 17:14:01 -0500 From: Christian Kuhtz To: Phillip Salzman , Brian Feldman Cc: gmarco@giovannelli.it, current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Phillip Salzman on Mon, Dec 28, 1998 at 04:04:16PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 04:04:16PM -0600, Phillip Salzman wrote: > > You can do that with natd. > > That is possible, but not logical. Say you have 2000 > dialup users attempting to access the web at the same time... all > coming from different IP addresses -- would you want the packet > scanning to go at the Cisco, or at the NATd? Its simple to do > a transparent proxy from the cisco, and does not require too much on > the squid side (IPFILTER), with less on the router. I thought the issue was, given IPFILTER or IPFW, can we do everything with IPFW that IPFILTER and other kludges did? So that we can start to phase out IPFILTER. Cisco's can't do transparent redirection at the present time. The do speak WCCP however. No, source routing is not an option. IMHO, we can argue all day long whether we want a FreeBSD or a Cisco in the datapath. Knowing both network stacks quite well, I'd vote for a Cisco anytime. But others may not feel the same way (for whatever reason) and want the FreeBSD box to do it. Anyone ever done any performance benchmarking on natd/IPFILTER/IPFW? Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 14:25:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA01939 for freebsd-current-outgoing; Mon, 28 Dec 1998 14:25:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.twcny.rr.com (mail1-1.twcny.rr.com [24.92.226.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA01932 for ; Mon, 28 Dec 1998 14:25:49 -0800 (PST) (envelope-from klmac@twcny.rr.com) Received: from [192.168.0.2] ([24.92.243.36]) by mail1.twcny.rr.com (Post.Office MTA v3.5.2 release 221 ID# 0-53939U80000L80000S0V35) with ESMTP id com for ; Mon, 28 Dec 1998 17:22:27 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: klmac@pop-server Message-Id: In-Reply-To: <19981228171401.B1333@ns1.adsu.bellsouth.com> References: ; from Phillip Salzman on Mon, Dec 28, 1998 at 04:04:16PM -0600 Date: Mon, 28 Dec 1998 17:25:32 -0500 To: freebsd-current@FreeBSD.ORG From: Ken McKittrick Subject: keeping IPFILTER (was Re: wanton Atticizing is bad) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello I don't see how dumping IPFILTER would be a good thing. It is actively supported by the developer and runs on Linux, Solaris, *BSD, etc. Ken >On Mon, Dec 28, 1998 at 04:04:16PM -0600, Phillip Salzman wrote: >> > You can do that with natd. >> >> That is possible, but not logical. Say you have 2000 >> dialup users attempting to access the web at the same time... all >> coming from different IP addresses -- would you want the packet >> scanning to go at the Cisco, or at the NATd? Its simple to do >> a transparent proxy from the cisco, and does not require too much on >> the squid side (IPFILTER), with less on the router. > >I thought the issue was, given IPFILTER or IPFW, can we do everything with >IPFW that IPFILTER and other kludges did? So that we can start to phase >out IPFILTER. > >Cisco's can't do transparent redirection at the present time. The do speak >WCCP however. No, source routing is not an option. > >IMHO, we can argue all day long whether we want a FreeBSD or a Cisco in the >datapath. Knowing both network stacks quite well, I'd vote for a Cisco >anytime. But others may not feel the same way (for whatever reason) and >want the FreeBSD box to do it. > >Anyone ever done any performance benchmarking on natd/IPFILTER/IPFW? > >Cheers, >Chris > >-- >Frisbeetarianism, n.: > The belief that when you die, your soul goes up on the roof and gets >stuck. > >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 28 14:30:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02772 for freebsd-current-outgoing; Mon, 28 Dec 1998 14:30:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02763 for ; Mon, 28 Dec 1998 14:30:33 -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 OAA13094; Mon, 28 Dec 1998 14:27:42 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812282227.OAA13094@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Ken McKittrick cc: freebsd-current@FreeBSD.ORG Subject: Re: keeping IPFILTER (was Re: wanton Atticizing is bad) In-reply-to: Your message of "Mon, 28 Dec 1998 17:25:32 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Dec 1998 14:27:41 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello > > I don't see how dumping IPFILTER would be a good thing. It is actively > supported by the developer and runs on Linux, Solaris, *BSD, etc. The manifest problem with ipfilter is that the copy in our tree is not being maintained by the author. The obvious solution is to remove that copy, and provide a mechanism for the author-distributed version to neatly integrate. Provided all the correct hooks are in place, all it would take is the build/load of the ipfilter KLD. I can't work out what would make you think that we would abandon the ability to use ipfilter. Do we look suicidally stupid or something? -- \\ 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 28 14:38:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA03958 for freebsd-current-outgoing; Mon, 28 Dec 1998 14:38:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA03913 for ; Mon, 28 Dec 1998 14:37:58 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id XAA20301; Mon, 28 Dec 1998 23:37:21 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id AAA03332; Tue, 29 Dec 1998 00:33:51 GMT (envelope-from son) Message-ID: <19981229003351.05206@breizh.prism.uvsq.fr> Date: Tue, 29 Dec 1998 00:33:51 +0000 From: Nicolas Souchu To: Jeroen Ruigrok/Asmodai Cc: FreeBSD Current Subject: Re: ZIP driver References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Jeroen Ruigrok/Asmodai on Mon, Dec 28, 1998 at 10:20:46PM +0100 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 10:20:46PM +0100, Jeroen Ruigrok/Asmodai wrote: > >Ehm, > >while we're on the subject, whatever did happen with the ZIP(+) driver? > >Somewhere along the line of commits did it break and unfortunately I only noticed >this when I needed it... > >The boot reports all the devices getting probed alright, except for da2 which was >normally my ZIP drive (and yes, it's on and has a disk in it ;) > ZIP is detected, then no da? You have generic chipset? Try 0x40 as 'ppc' boot flags. This avoids specific detection code that may break your hardware. Let me now. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 15:01:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA07706 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:01:55 -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 PAA07674; Mon, 28 Dec 1998 15:01:46 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id OAA14145; Mon, 28 Dec 1998 14:56:20 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdF14140; Mon Dec 28 22:56:12 1998 Date: Mon, 28 Dec 1998 14:56:09 -0800 (PST) From: Julian Elischer To: mi@aldan.algebra.com cc: phk@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: DSI_SOFT_MODEM!! In-Reply-To: <199812281955.TAA07027@igarber.radical.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 good luck... teh fact that it s users and is functional, useful code doesn't seem to be much of a factor these days. On Mon, 28 Dec 1998, Mikhail Teterin wrote: > The DSI_SOFT_MODEM support was removed from sio.c on the 27th > by phk. > > I hope, it was just done to check if anybody cares :). Well, > yes, I do, please, put it back. Yours, > > -mi > > 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 28 15:13:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09127 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:13:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09122 for ; Mon, 28 Dec 1998 15:13:51 -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 PAA13485; Mon, 28 Dec 1998 15:10:40 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812282310.PAA13485@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA cc: Mike Smith , des@flood.ping.uio.no, current@FreeBSD.ORG Subject: Re: future of syscons In-reply-to: Your message of "Thu, 24 Dec 1998 14:32:56 +0900." <199812240533.OAA25068@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Dec 1998 15:10:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > >No, you're right. But there's nothing stopping you have atkbdc do that > >right now; it should never take an interrupt from it's configuration - > >if it detects a kbdc, it should always take both implicitly. > > I think it's dangerous to take both interrupts "automatically" when > the keyboard controller is detected. I don't. We know with absolute certainty which interrupts it will use. > It is true that IRQ 1 is always assigned to the keyboard controller on > the AT motherboard and no device can claim it because IRQ 1 line is > not available in expansion slots. > > The PS/2 mouse interrupt IRQ 12 is another story. IRQ 12 is available > to ISA and PCI bus slots and you can assign it to a device! We > shouldn't make the keyboard controller code to claim IRQ 12 when > either 1) a PS/2 mouse is not detected, or 2) another device is using > or going to use IRQ 12. Sure; by all means disable the interrupt handler if a ps/2 mouse is not found, but it's important to claim the interrupt in the keyboard controller code if one *is* found, or even just expected to be found (eg. attached after bootup). > I expect all these chores will be solved by decent config(8) and bus > code...Then, we should do everything right :-) 8) One step at a time. PCI next. -- \\ 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 28 15:18:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09887 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:18:55 -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 PAA09882 for ; Mon, 28 Dec 1998 15:18:53 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA14617; Mon, 28 Dec 1998 15:15:42 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdq14615; Mon Dec 28 23:15:39 1998 Date: Mon, 28 Dec 1998 15:15:36 -0800 (PST) From: Julian Elischer To: Greg Lehey cc: FreeBSD current users Subject: Re: Thanks, Core Team In-Reply-To: <19981228112851.Y12346@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id PAA09883 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG join the club.... On Mon, 28 Dec 1998, Greg Lehey wrote: > OK, I'll try to summarize what I understand of the latest changes in -CURRENT: > > 1. LKMs are gone. > 2. This was decided by the core team. > 3. Nobody else was informed. > 4. In my case, my Vinum product just got dumped from the repository. > The first thing I heard was a laconic comment from Søren saying > ``Sorry for the mess, but it was overdue...'', followed by a > commit message showing them all gone. > > Well, thanks a lot. Suddenly, without any warning (but still > overdue...), my project is gone, and I have an unknown amount of work > to get back on track. The least I would have expected would be a bit > of advance warning. Instead, what do I get? > > On Sunday, 27 December 1998 at 18:20:00 +0100, Poul-Henning Kamp wrote: > > > > The cleanups have been discussed in -core. > > > > -committers is a notorious unproductive and flame-prone place to > > discuss code removal. > > Well, this is certainly an unproductive and flame-prone way to perform > code removal. I'd consider it a slap in the eye for all non-core > committers. I'd be interested in knowing how you would perform it if > you were deliberately trying to annoy us. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 15:19:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09931 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:19: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 PAA09923 for ; Mon, 28 Dec 1998 15:19:09 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA14506; Mon, 28 Dec 1998 15:11:37 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdJ14504; Mon Dec 28 23:11:34 1998 Date: Mon, 28 Dec 1998 15:11:31 -0800 (PST) From: Julian Elischer To: Peter Wemm cc: Alfred Perlstein , Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? In-Reply-To: <199812281859.CAA67283@spinner.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Transputer co-processor board... what do I win? julian On Tue, 29 Dec 1998, Peter Wemm wrote: > Alfred Perlstein wrote: > > > > On Mon, 28 Dec 1998, Pat Barron wrote: > > > > > I know someone asked this, but I have not seen an answer: Could someone > > > provide a list of exactly what was purged? It would be handy to know > > > things like, "this was purged, and is absolutely *not* coming back", or > > > "this was purged, but is being considered for reinstatement", but what I > > > really want to know is *exactly* what is now (today) gone, that used to be > > > there. > > > > voxware, lkms, vinum(an lkm) > > - DSI_SOFT_MODEM > - bqu driver > - 3c505 (note, *NOT* 3c905) > - pcvt > - broken (not updated for CAM) scsi drivers: nca, sea, wds, uha > - ft > - wcd (use acd instead) > - voxware > - lkm building (all lkm's have a corresponding kld) > > The vinum KLD module was accidently broken - it shared it's sources with > the LKM. > > And 10 points to the first person who can tell me what 'bqu' was without > looking it up. :-) > > > voxware may come back, vinum is definetly coming back as kld > > The jury is out on pcvt and voxware.. My feeling is that there's more than > enough support for both to revive them. > > Vinum is already fixed (I hope), and should also now support being > compiled into the kernel ("pseudo-device vinum") as well. > > > basically klms which have been deemed bad by -core are gone, as well as > > voxware. > > LKM's have been deemed sub-optimal by just about everyone. We are in a > situation where the KLD system is a superset of LKM's and it's a lot of > work duplicating effort to keep LKM's working. LKM's are a.out only while > KLD's are a.out and ELF, and both formats work on either format kernel.. > KLD's work with DDB, KLD's can be auto-loaded by the kernel (and are > already for filesystems). > > While I'd have liked the LKM retirement to be a little more peaceful and > with more warning, I'm not all that sad that support has gone for > building new LKMs that have already got *working* KLD equivalents. I for > one would like to remove kernel support for LKM's as well. > > Cheers, > -Peter > -- > Peter Wemm Netplex Consulting > "No coffee, No workee!" :-) > > > > 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 28 15:28:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11199 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:28:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from esmeralda.xaa.iae.nl (esmeralda.xaa.iae.nl [194.151.75.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11192 for ; Mon, 28 Dec 1998 15:28:42 -0800 (PST) (envelope-from freebsd@xaa.iae.nl) Received: from ariel.xaa.iae.nl (ariel.xaa.iae.nl [194.151.75.10]) by esmeralda.xaa.iae.nl (Postfix) with ESMTP id 40FC0148; Tue, 29 Dec 1998 00:28:22 +0100 (MET) Received: by ariel.xaa.iae.nl (Postfix, from userid 1008) id C4FEA3E8F; Tue, 29 Dec 1998 00:28:21 +0100 (CET) Date: Tue, 29 Dec 1998 00:28:21 +0100 From: Mark Huizer To: current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? Message-ID: <19981229002821.A620@ariel.xaa.iae.nl> References: <199812281859.CAA67283@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Julian Elischer on Mon, Dec 28, 1998 at 03:11:31PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 28, 1998 at 03:11:31PM -0800, Julian Elischer wrote: > Transputer co-processor board... > > what do I win? > > julian > > > And 10 points to the first person who can tell me what 'bqu' was without > > looking it up. :-) > > 10 points?? Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 15:29:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11294 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:29:47 -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 PAA11265 for ; Mon, 28 Dec 1998 15:29:31 -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 AAA75940; Tue, 29 Dec 1998 00:25:48 +0100 (CET) To: Julian Elischer cc: Peter Wemm , Alfred Perlstein , Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? In-reply-to: Your message of "Mon, 28 Dec 1998 15:11:31 PST." Date: Tue, 29 Dec 1998 00:25:47 +0100 Message-ID: <75938.914887547@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A T405 with 64k RAM :-) Poul-Henning In message , Jul ian Elischer writes: >Transputer co-processor board... > >what do I win? > >julian > > >On Tue, 29 Dec 1998, Peter Wemm wrote: > >> Alfred Perlstein wrote: >> > >> > On Mon, 28 Dec 1998, Pat Barron wrote: >> > >> > > I know someone asked this, but I have not seen an answer: Could someone >> > > provide a list of exactly what was purged? It would be handy to know >> > > things like, "this was purged, and is absolutely *not* coming back", or >> > > "this was purged, but is being considered for reinstatement", but what I >> > > really want to know is *exactly* what is now (today) gone, that used to be >> > > there. >> > >> > voxware, lkms, vinum(an lkm) >> >> - DSI_SOFT_MODEM >> - bqu driver >> - 3c505 (note, *NOT* 3c905) >> - pcvt >> - broken (not updated for CAM) scsi drivers: nca, sea, wds, uha >> - ft >> - wcd (use acd instead) >> - voxware >> - lkm building (all lkm's have a corresponding kld) >> >> The vinum KLD module was accidently broken - it shared it's sources with >> the LKM. >> >> And 10 points to the first person who can tell me what 'bqu' was without >> looking it up. :-) >> >> > voxware may come back, vinum is definetly coming back as kld >> >> The jury is out on pcvt and voxware.. My feeling is that there's more than >> enough support for both to revive them. >> >> Vinum is already fixed (I hope), and should also now support being >> compiled into the kernel ("pseudo-device vinum") as well. >> >> > basically klms which have been deemed bad by -core are gone, as well as >> > voxware. >> >> LKM's have been deemed sub-optimal by just about everyone. We are in a >> situation where the KLD system is a superset of LKM's and it's a lot of >> work duplicating effort to keep LKM's working. LKM's are a.out only while >> KLD's are a.out and ELF, and both formats work on either format kernel.. >> KLD's work with DDB, KLD's can be auto-loaded by the kernel (and are >> already for filesystems). >> >> While I'd have liked the LKM retirement to be a little more peaceful and >> with more warning, I'm not all that sad that support has gone for >> building new LKMs that have already got *working* KLD equivalents. I for >> one would like to remove kernel support for LKM's as well. >> >> Cheers, >> -Peter >> -- >> Peter Wemm Netplex Consulting >> "No coffee, No workee!" :-) >> >> >> >> 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 > -- 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 Mon Dec 28 15:30:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11466 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:30:37 -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 PAA11461 for ; Mon, 28 Dec 1998 15:30:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA02795; Mon, 28 Dec 1998 15:30:05 -0800 (PST) To: Phillip Salzman cc: Brian Feldman , Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? In-reply-to: Your message of "Mon, 28 Dec 1998 16:11:25 CST." Date: Mon, 28 Dec 1998 15:30:04 -0800 Message-ID: <2791.914887804@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > IPFILTER too Nope. Only proposed, not done. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 15:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11534 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:31:02 -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 PAA11523 for ; Mon, 28 Dec 1998 15:30:59 -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 KAA00488; Tue, 29 Dec 1998 10:00:23 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA32202; Tue, 29 Dec 1998 10:00:25 +1030 (CST) Message-ID: <19981229100025.K12346@freebie.lemis.com> Date: Tue, 29 Dec 1998 10:00:25 +1030 From: Greg Lehey To: Peter Wemm , Doug Rabson Cc: FreeBSD current users Subject: Re: How do I build an a.out kld? References: <199812281145.TAA65000@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812281145.TAA65000@spinner.netplex.com.au>; from Peter Wemm on Mon, Dec 28, 1998 at 07:44:59PM +0800 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 On Monday, 28 December 1998 at 19:44:59 +0800, Peter Wemm wrote: > Doug Rabson wrote: >> On Mon, 28 Dec 1998, Greg Lehey wrote: > [..] >>> 2. I could build an a.out kld. Unfortunately, there's an >>> (undocumented) program called gensetdefs which runs against the >>> objects, and expects only ELF files. It doesn't understand an >>> -aout flag. Can I get past this problem? >> >> Are you using bsd.kmod.mk? If you look at it, gensetdefs is only used for >> elf. Linking an a.out module is even simpler: >> >> ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} ${OBJS} ${KMODDEPS} >> >> Try 'make OBJFORMAT=aout' and see what happens. > > Err, my recollection was that it needed to be in the environment, ie more > like: env OBJFORMAT=aout make Neither of these answer the original question: how to I get gensetdefs to work on a.out objects? It's now a moot point: I've just about finished migrating to ELF, which I had to do anyway at some point. Thanks to you and Jordan for the details on that. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 15:46:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13576 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:46:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13556 for ; Mon, 28 Dec 1998 15:46:33 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id AAA07249; Tue, 29 Dec 1998 00:45:46 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id AAA24203; Tue, 29 Dec 1998 00:33:15 +0100 (MET) (envelope-from j) Date: Tue, 29 Dec 1998 00:33:15 +0100 (MET) Message-Id: <199812282333.AAA24203@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Setting securelevel X-Original-Newsgroups: local.freebsd.current To: freebsd-current@FreeBSD.ORG cc: "Eugene M. Kim" Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Eugene M. Kim" wrote: > This, in consequence, prohibits the kernel from returning to the > insecure mode even in the single-user mode. Intentionally. There was at least one CERT advisory by that time that turned out to abuse this security hole (something like abusing a buffer overflow in init(8) in a way so securelevel could be lowered while the system is running -- something that should _never_ happen). We finally decided that a securelevel is simply and only secure if it cannot be lowered again. If i'm not totally mistaken, i've been the one who did the deed... yep: revision 1.9 date: 1997/06/25 07:31:47; author: joerg; state: Exp; lines: +2 -2 Don't ever allow lowering the securelevel at all. Allowing it does nothing good except of opening a can of (potential or real) security holes. People maintaining a machine with higher security requirements need to be on the console anyway, so there's no point in not forcing them to reboot before starting maintenance. Agreed by: hackers, guido So it doesn't always require a Dane to do a bloody deed. ;-) Well, the only thing you lose by this change is your uptime record. You trade it for security. In case you are ready to go down to single-user, you already need access to the console anyway, so you can reboot first as well. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 15:49:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13903 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:49:16 -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 PAA13895 for ; Mon, 28 Dec 1998 15:49:11 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id XAA15548; Mon, 28 Dec 1998 23:48:08 GMT Date: Mon, 28 Dec 1998 23:48:08 +0000 (GMT) From: Doug Rabson To: Greg Lehey cc: Peter Wemm , FreeBSD current users Subject: Re: How do I build an a.out kld? In-Reply-To: <19981229100025.K12346@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 On Tue, 29 Dec 1998, Greg Lehey wrote: > On Monday, 28 December 1998 at 19:44:59 +0800, Peter Wemm wrote: > > Doug Rabson wrote: > >> On Mon, 28 Dec 1998, Greg Lehey wrote: > > [..] > >>> 2. I could build an a.out kld. Unfortunately, there's an > >>> (undocumented) program called gensetdefs which runs against the > >>> objects, and expects only ELF files. It doesn't understand an > >>> -aout flag. Can I get past this problem? > >> > >> Are you using bsd.kmod.mk? If you look at it, gensetdefs is only used for > >> elf. Linking an a.out module is even simpler: > >> > >> ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} ${OBJS} ${KMODDEPS} > >> > >> Try 'make OBJFORMAT=aout' and see what happens. > > > > Err, my recollection was that it needed to be in the environment, ie more > > like: env OBJFORMAT=aout make > > Neither of these answer the original question: how to I get gensetdefs > to work on a.out objects? > > It's now a moot point: I've just about finished migrating to ELF, > which I had to do anyway at some point. Thanks to you and Jordan for > the details on that. I thought I did answer it. Gensetdefs is not needed (and should not be used) for a.out. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 15:54:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14680 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:54:31 -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 PAA14669 for ; Mon, 28 Dec 1998 15:54:27 -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 PAA29046 for ; Mon, 28 Dec 1998 15:50:13 -0800 (PST) Date: Mon, 28 Dec 1998 15:50:13 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: Anybody having luck with upgrading *old* 3.0 SMP installs to new? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just want to find out if there's a reasonable chance of success before I take the plunge. I have a 3 processor SMP box running an jan/feb or so release of 3.0, wich a may kernel. Working fine, but want to get current. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 15:55:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14771 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:55:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14766 for ; Mon, 28 Dec 1998 15:55:52 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id AAA07267 for freebsd-current@freebsd.org; Tue, 29 Dec 1998 00:46:41 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id AAA24246; Tue, 29 Dec 1998 00:43:54 +0100 (MET) (envelope-from j) Date: Tue, 29 Dec 1998 00:43:54 +0100 (MET) Message-Id: <199812282343.AAA24246@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: So, exactly what *was* purged? X-Original-Newsgroups: local.freebsd.current To: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dmitry Valdov wrote: >> Off the top of my head, it was: >> VoxWare >> floppy tape driver > > ^^^^^^^^^^^^^^^^^^^ > ft*? Why? I'am still using it. Because it's a bad hack... well, all those drives actually are, to be honest. However, i'm in the opinion that no working driver should be removed between 3.0 and the 3.0.1 branch point, since it's contradictionary to the `minor version number bump'. I'm not sure whether my opinion will find a majority on _this_ one (ft, namely), however. Whether now or later, ft will die some day. (pcvt will, too, but most likely only after a replacement is available for a good VTxxx emulation.) The fd driver is overdue for a rewrite as well, but i haven't found the time and energy so far (and apparently nobody else). If it wasn't now, this rewrite would have been the deadline for ft(4) anyway. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 15:55:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14805 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:55:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA14780 for ; Mon, 28 Dec 1998 15:55:55 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id AAA07260; Tue, 29 Dec 1998 00:46:22 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id AAA24212; Tue, 29 Dec 1998 00:34:25 +0100 (MET) (envelope-from j) Date: Tue, 29 Dec 1998 00:34:25 +0100 (MET) Message-Id: <199812282334.AAA24212@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <00fc01be32a4$7346d5c0$0200a8c0@mn.mediaone.net> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: comsat and sendmail msgs X-Original-Newsgroups: local.freebsd.current To: freebsd-current@FreeBSD.ORG cc: "Erik Funkenbusch" Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Erik Funkenbusch" wrote: > I recently started getting messages showing up of the type: > > inetd[152]: /usr/libexec/comsat[3629]: exit status 0xb ``exit status 0xb'' == ``exited with signal 11'' > Any ideas about these issues? Bad RAM. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 15:57:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA14926 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:57:22 -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 PAA14920 for ; Mon, 28 Dec 1998 15:57:21 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA15272; Mon, 28 Dec 1998 15:45:18 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdy15270; Mon Dec 28 23:45:11 1998 Date: Mon, 28 Dec 1998 15:45:07 -0800 (PST) From: Julian Elischer To: Eivind Eklund cc: Warner Losh , Poul-Henning Kamp , current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: <19981228212148.K53810@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 Mon, 28 Dec 1998, Eivind Eklund wrote: > On Mon, Dec 28, 1998 at 12:54:28PM -0700, Warner Losh wrote: > > In message <68621.914783144@critter.freebsd.dk> Poul-Henning Kamp writes: > > > Make DEVFS standard. > > > > I'd love to see this happen, but there are problems with the current > > DEVFS which makes it impossible to use with CAM. It can't handle > > devices comeing and going at interrupt time, which is how CAM does > > probing and device removal. > > Julian claimed to have fixed this (but not yet committed the fixes) at > the time phk and sos last bloodied their axes (by murdering the > partially working version of SLICE). More truthfully, I was working on getting it to work with CAM. and had created a kernel thread to take charge of such events as new devices appearing, and the creation of the new nodes. I hadn't committed anything because I was waiting for cam to be imported. but surprise surprise. my code was deleted before CAM made it in.. > > Eivind. > > 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 28 15:58:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15026 for freebsd-current-outgoing; Mon, 28 Dec 1998 15:58:06 -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 PAA15020 for ; Mon, 28 Dec 1998 15:58:01 -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 TAA95944; Mon, 28 Dec 1998 19:01:25 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Mon, 28 Dec 1998 19:01:25 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Jaye Mathisen cc: current@FreeBSD.ORG Subject: Re: Anybody having luck with upgrading *old* 3.0 SMP installs to new? 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, 28 Dec 1998, Jaye Mathisen wrote: > > > Just want to find out if there's a reasonable chance of success before I > take the plunge. > > I have a 3 processor SMP box running an jan/feb or so release of 3.0, wich > a may kernel. Working fine, but want to get current. > there's been a lot of changes since then, check the hardware lists, and definetly do a full backup, test the backup 2 or 3 times. :) Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 16:00:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15319 for freebsd-current-outgoing; Mon, 28 Dec 1998 16:00:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15291 for ; Mon, 28 Dec 1998 16:00:28 -0800 (PST) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.1/8.9.1) id PAA08319; Mon, 28 Dec 1998 15:59:45 -0800 (PST) (envelope-from mph) Message-ID: <19981228155945.B7980@wopr.caltech.edu> Date: Mon, 28 Dec 1998 15:59:45 -0800 From: Matthew Hunt To: Joerg Wunsch , freebsd-current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? References: <199812282343.AAA24246@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812282343.AAA24246@uriah.heep.sax.de>; from J Wunsch on Tue, Dec 29, 1998 at 12:43:54AM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 29, 1998 at 12:43:54AM +0100, J Wunsch wrote: > Whether now or later, ft will die some day. (pcvt will, too, but most > likely only after a replacement is available for a good VTxxx > emulation.) I assume that "run screen" is not a suitable solution for people wishing to run VT applications at the console? -- Matthew Hunt * Inertia is a property of matter. http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 16:01:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15397 for freebsd-current-outgoing; Mon, 28 Dec 1998 16:01:22 -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 QAA15376 for ; Mon, 28 Dec 1998 16:01:16 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca32-59.ix.netcom.com [209.109.239.59]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id QAA24920 for ; Mon, 28 Dec 1998 16:00:57 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id QAA26160; Mon, 28 Dec 1998 16:00:52 -0800 (PST) Date: Mon, 28 Dec 1998 16:00:52 -0800 (PST) Message-Id: <199812290000.QAA26160@silvia.hip.berkeley.edu> To: freebsd-current@FreeBSD.ORG In-reply-to: <199812282343.AAA24246@uriah.heep.sax.de> (j@uriah.heep.sax.de) Subject: Re: So, exactly what *was* purged? From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: j@uriah.heep.sax.de (J Wunsch) * The fd driver is overdue for a rewrite as well, but i haven't found I think Jesus Monroy Jr. had it already done. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 16:18:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA19242 for freebsd-current-outgoing; Mon, 28 Dec 1998 16:18:32 -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 QAA19237 for ; Mon, 28 Dec 1998 16:18:30 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA15953 for ; Mon, 28 Dec 1998 16:08:37 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdR15940; Tue Dec 29 00:08:34 1998 Date: Mon, 28 Dec 1998 16:08:27 -0800 (PST) From: Julian Elischer To: current@FreeBSD.ORG Subject: A quick clarification 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 Some people have mentionned to me in private email that my mail indicates a 'dislike' for certain danes.. :-) I would like to point out that having met several danes, and in particular, the danes in question, I do not dislike them or even have any major disagreements with them. I have some specific problems with some specific actions, but in general I have seen them to be highly competant people with a very great passion to see the best happen for FreeBSD. "Professional disagreements" are something that we all have to "get over" in then real world. I would rather have these people involved with FreeBSD than not, and feel that as we are all fairly logical people, we will be able to move forward, despite disagreements. julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 16:46:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22402 for freebsd-current-outgoing; Mon, 28 Dec 1998 16:46:11 -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 QAA22396 for ; Mon, 28 Dec 1998 16:46:06 -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 QAA29361 for ; Mon, 28 Dec 1998 16:41:51 -0800 (PST) Date: Mon, 28 Dec 1998 16:41:51 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: Argh, can't get -current to build under 2.2.8+ 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 Trying to upgrade my box from 2.2.8 to 3.0 supped from a few minutes ago: ===> librpcsvc rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/klm_prot.x -o klm_prot_xdr.c cc -O -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/usr/src/tmp/ usr/include -c klm_prot_xdr.c -o klm_prot_xdr.o rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/mount.x -o mount_xdr.c cc -O -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/usr/src/tmp/ usr/include -c mount_xdr.c -o mount_xdr.o rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.x -o nfs_prot_xdr.c cc -O -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/usr/src/tmp/ usr/include -c nfs_prot_xdr.c -o nfs_prot_xdr.o In file included from nfs_prot_xdr.c:6: /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse error before `uint64' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: parse error before `int64' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: parse error before `fileid3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: parse error before `cookie3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:291: parse error before `size3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:291: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:293: parse error before `offset3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:293: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:369: parse error before `size3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:369: warning: no semicolon at end of struct or union /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:370: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:372: parse error before `fsid' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:372: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:373: parse error before `fileid' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:373: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:376: `ctime' redeclared as different kind of symbol /usr/obj/aout/usr/src/tmp/usr/include/time.h:126: previous declaration of `ctime' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:377: parse error before `}' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:383: field `attributes' has incomplete type /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:389: parse error before `size3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:389: warning: no semicolon at end of struct or union /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:392: parse error before `}' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:398: field `attributes' has incomplete type /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: parse error before `size3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: warning: no semicolon at end of struct or union /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: warning: no semicolon at end of struct or union /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:452: warning: data definition has no type or storage class /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:453: parse error before `}' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:476: field `size' has incomplete type /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:494: field `obj_attributes' has incomplete type /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:625: parse error before `offset3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:625: warning: no semicolon at end of struct or union /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:627: parse error before `}' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:664: parse error before `offset3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:664: warning: no semicolon at end of struct or union /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:671: parse error before `}' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:945: parse error before `cookie3' /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:945: warning: no semicolon at end of struct or union and so on, and then it dies horribly... I tried building lex and yacc per some other email, but it didn't help. Resupping didn't fix it either. What to do, what to do... Thanks in advance. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 16:51:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22947 for freebsd-current-outgoing; Mon, 28 Dec 1998 16:51:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA22940 for ; Mon, 28 Dec 1998 16:51:47 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id UAA24649; Mon, 28 Dec 1998 20:50:52 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 28 Dec 1998 20:50:52 -0400 (AST) From: The Hermit Hacker To: Jaye Mathisen cc: current@FreeBSD.ORG Subject: Re: Argh, can't get -current to build under 2.2.8+ 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 Its been awhile, but I *believe* you have to do a 'make bootstrap' first, which builds all the ancilliary programs you will require to go to 3.0 ... Don't hold me to this, I'm working on little sleep, and, as I said, its been awhile... On Mon, 28 Dec 1998, Jaye Mathisen wrote: > > > Trying to upgrade my box from 2.2.8 to 3.0 supped from a few minutes ago: > > ===> librpcsvc > rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/klm_prot.x -o > klm_prot_xdr.c > cc -O -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc > -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/usr/src/tmp/ > usr/include -c klm_prot_xdr.c -o klm_prot_xdr.o > rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/mount.x -o > mount_xdr.c > cc -O -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc > -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/usr/src/tmp/ > usr/include -c mount_xdr.c -o mount_xdr.o > rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.x -o > nfs_prot_xdr.c > cc -O -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc > -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/usr/src/tmp/ > usr/include -c nfs_prot_xdr.c -o nfs_prot_xdr.o > In file included from nfs_prot_xdr.c:6: > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse error > before `uint64' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: warning: data > definition has no type or storage class > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: parse error > before `int64' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: warning: data > definition has no type or storage class > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: parse error > before `fileid3' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: warning: data > definition has no type or storage class > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: parse error > before `cookie3' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: warning: data > definition has no type or storage class > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:291: parse error > before `size3' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:291: warning: data > definition has no type or storage class > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:293: parse error > before `offset3' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:293: warning: data > definition has no type or storage class > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:369: parse error > before `size3' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:369: warning: no > semicolon at end of struct or union > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:370: warning: data > definition has no type or storage class > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:372: parse error > before `fsid' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:372: warning: data > definition has no type or storage class > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:373: parse error > before `fileid' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:373: warning: data > definition has no type or storage class > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:376: `ctime' > redeclared as different kind of symbol > /usr/obj/aout/usr/src/tmp/usr/include/time.h:126: previous declaration of > `ctime' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:377: parse error > before `}' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:383: field > `attributes' has incomplete type > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:389: parse error > before `size3' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:389: warning: no > semicolon at end of struct or union > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:392: parse error > before `}' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:398: field > `attributes' has incomplete type > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: parse error > before `size3' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: warning: no > semicolon at end of struct or union > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: warning: no > semicolon at end of struct or union > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:452: warning: data > definition has no type or storage class > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:453: parse error > before `}' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:476: field `size' > has incomplete type > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:494: field > `obj_attributes' has incomplete type > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:625: parse error > before `offset3' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:625: warning: no > semicolon at end of struct or union > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:627: parse error > before `}' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:664: parse error > before `offset3' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:664: warning: no > semicolon at end of struct or union > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:671: parse error > before `}' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:945: parse error > before `cookie3' > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:945: warning: no > semicolon at end of struct or union > > > and so on, and then it dies horribly... > > > I tried building lex and yacc per some other email, but it didn't help. > Resupping didn't fix it either. > > What to do, what to do... > > Thanks in advance. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 17:13:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25227 for freebsd-current-outgoing; Mon, 28 Dec 1998 17:13:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA24990; Mon, 28 Dec 1998 17:12:59 -0800 (PST) (envelope-from shocking@ariadne.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id JAA25567; Tue, 29 Dec 1998 09:12:34 +0800 (WST) Received: from ariadne by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id JAA09976; Tue, 29 Dec 1998 09:12:34 +0800 Message-Id: <199812290112.JAA09976@ariadne.tensor.pgs.com> X-Mailer: exmh version 2.0.2 2/24/98 To: cvs-committers@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: Re: The recent fracas involving danes, war axes and wounded developers Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Dec 1998 09:12:33 +0800 From: Stephen Hocking-Senior Programmer PGS Tensor Perth Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Regarding VOXware - please bring it back. PCM doesn't support two important things for me, these being a) my PAS-16 card and b) mmap'd sound buffers, as used by certain Linux 3D applications (and yes Jordan, these things do matter to some people) Stephen -- The views expressed above are not those of PGS Tensor. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 17:21:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25749 for freebsd-current-outgoing; Mon, 28 Dec 1998 17:21:01 -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 RAA25744 for ; Mon, 28 Dec 1998 17:21:00 -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 RAA14426; Mon, 28 Dec 1998 17:20:41 -0800 (PST) Date: Mon, 28 Dec 1998 17:20:41 -0800 (PST) From: Chris Timmons To: Jaye Mathisen cc: current@FreeBSD.ORG Subject: Re: Argh, can't get -current to build under 2.2.8+ 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 Are you doing a 'make aout-to-elf-build'? Or simply a buildworld on 2.2.8-stable with -current /usr/src? If the former, it worked not so long ago; you might want to back up your -current sources to about 12/18. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 17:21:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25978 for freebsd-current-outgoing; Mon, 28 Dec 1998 17:21:14 -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 RAA25887 for ; Mon, 28 Dec 1998 17:21:09 -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 RAA29491; Mon, 28 Dec 1998 17:16:53 -0800 (PST) Date: Mon, 28 Dec 1998 17:16:52 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: The Hermit Hacker cc: current@FreeBSD.ORG Subject: Re: Argh, can't get -current to build under 2.2.8+ 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 Nope. No bootstrap target: apocalypse# make bootstrap make: don't know how to make bootstrap. Stop apocalypse# (Little did I know how apropos the machine name would become). >From reading the makefile, it appears that it tries to build the minimal toolset first, installs it, then uses it. Maybe rpcgen is screwed up, didn't try rebuilding that. On Mon, 28 Dec 1998, The Hermit Hacker wrote: > > Its been awhile, but I *believe* you have to do a 'make bootstrap' first, > which builds all the ancilliary programs you will require to go to 3.0 ... > > Don't hold me to this, I'm working on little sleep, and, as I said, its > been awhile... > > On Mon, 28 Dec 1998, Jaye Mathisen wrote: > > > > > > > Trying to upgrade my box from 2.2.8 to 3.0 supped from a few minutes ago: > > > > ===> librpcsvc > > rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/klm_prot.x -o > > klm_prot_xdr.c > > cc -O -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc > > -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/usr/src/tmp/ > > usr/include -c klm_prot_xdr.c -o klm_prot_xdr.o > > rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/mount.x -o > > mount_xdr.c > > cc -O -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc > > -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/usr/src/tmp/ > > usr/include -c mount_xdr.c -o mount_xdr.o > > rpcgen -C -c /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.x -o > > nfs_prot_xdr.c > > cc -O -pipe -DYP -I/usr/obj/aout/usr/src/tmp/usr/include/rpcsvc > > -I/usr/obj/aout/usr/src/tmp/usr/include -I/usr/obj/aout/usr/src/tmp/ > > usr/include -c nfs_prot_xdr.c -o nfs_prot_xdr.o > > In file included from nfs_prot_xdr.c:6: > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse error > > before `uint64' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: warning: data > > definition has no type or storage class > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: parse error > > before `int64' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:267: warning: data > > definition has no type or storage class > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: parse error > > before `fileid3' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:277: warning: data > > definition has no type or storage class > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: parse error > > before `cookie3' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:279: warning: data > > definition has no type or storage class > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:291: parse error > > before `size3' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:291: warning: data > > definition has no type or storage class > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:293: parse error > > before `offset3' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:293: warning: data > > definition has no type or storage class > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:369: parse error > > before `size3' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:369: warning: no > > semicolon at end of struct or union > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:370: warning: data > > definition has no type or storage class > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:372: parse error > > before `fsid' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:372: warning: data > > definition has no type or storage class > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:373: parse error > > before `fileid' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:373: warning: data > > definition has no type or storage class > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:376: `ctime' > > redeclared as different kind of symbol > > /usr/obj/aout/usr/src/tmp/usr/include/time.h:126: previous declaration of > > `ctime' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:377: parse error > > before `}' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:383: field > > `attributes' has incomplete type > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:389: parse error > > before `size3' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:389: warning: no > > semicolon at end of struct or union > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:392: parse error > > before `}' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:398: field > > `attributes' has incomplete type > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: parse error > > before `size3' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: warning: no > > semicolon at end of struct or union > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:451: warning: no > > semicolon at end of struct or union > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:452: warning: data > > definition has no type or storage class > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:453: parse error > > before `}' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:476: field `size' > > has incomplete type > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:494: field > > `obj_attributes' has incomplete type > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:625: parse error > > before `offset3' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:625: warning: no > > semicolon at end of struct or union > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:627: parse error > > before `}' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:664: parse error > > before `offset3' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:664: warning: no > > semicolon at end of struct or union > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:671: parse error > > before `}' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:945: parse error > > before `cookie3' > > /usr/obj/aout/usr/src/tmp/usr/include/rpcsvc/nfs_prot.h:945: warning: no > > semicolon at end of struct or union > > > > > > and so on, and then it dies horribly... > > > > > > I tried building lex and yacc per some other email, but it didn't help. > > Resupping didn't fix it either. > > > > What to do, what to do... > > > > Thanks in advance. > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Marc G. Fournier > Systems Administrator @ hub.org > primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 17:26:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26260 for freebsd-current-outgoing; Mon, 28 Dec 1998 17:26:19 -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 RAA26255 for ; Mon, 28 Dec 1998 17:26:17 -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 RAA29508; Mon, 28 Dec 1998 17:20:35 -0800 (PST) Date: Mon, 28 Dec 1998 17:20:35 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Chris Timmons cc: current@FreeBSD.ORG Subject: Re: Argh, can't get -current to build under 2.2.8+ 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 Just: make world on a 2.2.8 box, with -current supped today. As I read the makefile, that's the proper method, the aout to elf is for converting from a 3.0 aout system to a 3.0 elf system. If you're on a really old 2.x system, then the Makefile.upgrade is used to build a few things that won't work w/o it... But since I'm fairly current in the stable branch (how's that for mixing tags, labels, and versions? :)), I should be OK. On Mon, 28 Dec 1998, Chris Timmons wrote: > > Are you doing a 'make aout-to-elf-build'? Or simply a buildworld on > 2.2.8-stable with -current /usr/src? If the former, it worked not so long > ago; you might want to back up your -current sources to about 12/18. > > -Chris > > > > 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 28 17:32:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26633 for freebsd-current-outgoing; Mon, 28 Dec 1998 17:32:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assurance.rstcorp.com ([206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26627 for ; Mon, 28 Dec 1998 17:32:31 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id UAA17538 for ; Mon, 28 Dec 1998 20:32:14 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma017536; Mon, 28 Dec 98 20:31:22 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id UAA15812 for ; Mon, 28 Dec 1998 20:31:21 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id UAA16173; Mon, 28 Dec 1998 20:31:21 -0500 (EST) Date: Mon, 28 Dec 1998 20:31:21 -0500 (EST) Message-Id: <199812290131.UAA16173@jabberwock.rstcorp.com> MIME-Version: 1.0 From: "Viren R. Shah" To: freebsd-current@FreeBSD.ORG Subject: VESA kld question X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So far, I've been using[1] the VESA kld (with VM86 compiled into the kernel) by loading it thru the /boot/boot.conf file. I tried using the new logo kld screensaver, and it wouldn't work saying that the particular VESA mode wasn't supported. This seemed ridiculous to me since the screensaver was only looking for 800x600. So, I compiled a new kernel with "options VESA", rebooted, and voila! the screensaver worked. Is there a known problem with using the VESA kld, as oppossed to compiling it statically into the kernel? I discovered that when I was using the VESA kld, I wasn't getting the following lines upon bootup, which I do get with VESA compiled into the kernel: VESA: v3.0, 4096k memory, flags:0x1, mode table:0xf021652a (1000022) VESA: STB Velocity 128 (RIVA 128) My boot.conf file looks like (or looked like): load kernel load atapi load cd9660 load vesa load linux load if_tun load kernfs load procfs load portal autoboot 5 Any ideas as to why the kld module wouldn't work? [1]: When I say "using" here, I mean loading it without really trying to use it for anything. :-) Thanks Viren -- Viren R. Shah | "For oft, when on my couch I lie viren@rstcorp.com | In vacant or in pensive mood, Research Associate | They flash upon that inward eye RST Inc. | Which is the bliss of solitude;" --WW To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 17:37:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27134 for freebsd-current-outgoing; Mon, 28 Dec 1998 17:37:08 -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 RAA27123 for ; Mon, 28 Dec 1998 17:37:05 -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 RAA15111; Mon, 28 Dec 1998 17:36:39 -0800 (PST) Date: Mon, 28 Dec 1998 17:36:39 -0800 (PST) From: Chris Timmons Reply-To: Chris Timmons To: Jaye Mathisen cc: current@FreeBSD.ORG Subject: Re: Argh, can't get -current to build under 2.2.8+ 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 No, John Birrell spent a lot of time working on the upgrade so that you could get to 3.0-current.elf from 2.2.x. I've done this recently and was impressed that all of my 2.2.6 era applications continued to work flawlessly under 3.0/elf. Even XF86_SVGA! Of course I went back and rebuilt everything in order to get rid of the aout libraries, but it will work. Don't forget to update /etc files, which include some ldconfig parameters for aout in rc.conf. -Chris On Mon, 28 Dec 1998, Jaye Mathisen wrote: > > Just: > > make world > > on a 2.2.8 box, with -current supped today. > > As I read the makefile, that's the proper method, the aout to elf is for > converting from a 3.0 aout system to a 3.0 elf system. > > If you're on a really old 2.x system, then the Makefile.upgrade is used to > build a few things that won't work w/o it... But since I'm fairly current > in the stable branch (how's that for mixing tags, labels, and versions? > :)), I should be OK. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 18:09:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA29967 for freebsd-current-outgoing; Mon, 28 Dec 1998 18:09:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [156.46.203.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA29962 for ; Mon, 28 Dec 1998 18:09:38 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [156.46.203.13]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id UAA22687; Mon, 28 Dec 1998 20:07:57 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <00e501be32d0$1018ce00$0dcb2e9c@westbend.net> From: "Scot W. Hetzel" To: "Erik Funkenbusch" Cc: References: <002b01be32ad$08556de0$0200a8c0@mn.mediaone.net> Subject: Re: sendmail.cf? Date: Mon, 28 Dec 1998 20:07:56 -0600 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.1012.1001 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.1012.1001 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From: Erik Funkenbusch > Ok, I guess sendmail was updated recently and now supports a new version of > the sendmail.cf file. > > I've been trying to figure out how to rebuild this file, but can't seem to > find the original source file that it is created from. > > sendmail.cf seems to indicate it was built out of directory > /usr/src/usr.sbin/sendmail/cf/cf but there is no cf directory under sendmail > in the tree. Anyone know where the default .m4 file is that sendmail.cf is > built from? > sendmail was moved out of that directory and into the contrib directory. Try /usr/src/contrib/sendmail/cf instead. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 18:18:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA00754 for freebsd-current-outgoing; Mon, 28 Dec 1998 18:18:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chandra.eatell.msr.prug.or.jp (dhcp421.6bone.nec.co.jp [202.247.4.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA00746; Mon, 28 Dec 1998 18:18:19 -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 CAA20742; Tue, 29 Dec 1998 02:09:03 GMT Message-Id: <199812290209.CAA20742@chandra.eatell.msr.prug.or.jp> To: Stephen Hocking-Senior Programmer PGS Tensor Perth cc: cvs-committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: The recent fracas involving danes, war axes and wounded developers In-reply-to: Your message of "Tue, 29 Dec 1998 09:12:33 +0800." <199812290112.JAA09976@ariadne.tensor.pgs.com> Date: Tue, 29 Dec 1998 11:09:02 +0900 From: NAKAGAWA Yoshihisa Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Regarding VOXware - please bring it back. PCM doesn't support two important me too. pcm driver is good; but PCM only, not yet support MIDI, FM synth, .... -- 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 Mon Dec 28 18:47:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02981 for freebsd-current-outgoing; Mon, 28 Dec 1998 18:47:53 -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 SAA02976 for ; Mon, 28 Dec 1998 18:47:50 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:gSFMTGLk9dAh04oibIknkxGAwcOtfbIa@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 LAA29836; Tue, 29 Dec 1998 11:47:21 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA25902; Tue, 29 Dec 1998 11:49:32 +0900 (JST) Message-Id: <199812290249.LAA25902@zodiac.mech.utsunomiya-u.ac.jp> To: "Viren R. Shah" cc: freebsd-current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: VESA kld question In-reply-to: Your message of "Mon, 28 Dec 1998 20:31:21 EST." <199812290131.UAA16173@jabberwock.rstcorp.com> References: <199812290131.UAA16173@jabberwock.rstcorp.com> Date: Tue, 29 Dec 1998 11:49:31 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >So far, I've been using[1] the VESA kld (with VM86 compiled into the >kernel) by loading it thru the /boot/boot.conf file. I tried using the >new logo kld screensaver, and it wouldn't work saying that the >particular VESA mode wasn't supported. This seemed ridiculous to me >since the screensaver was only looking for 800x600. So, I compiled a >new kernel with "options VESA", rebooted, and voila! the screensaver >worked. Well, sorry. It now appears that the VESA module has not been fully converted from LKM to KLD. I will fix it soon. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 19:03:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04811 for freebsd-current-outgoing; Mon, 28 Dec 1998 19:03:53 -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 TAA04801 for ; Mon, 28 Dec 1998 19:03:51 -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 SAA29897; Mon, 28 Dec 1998 18:58:21 -0800 (PST) Date: Mon, 28 Dec 1998 18:58:21 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Chris Timmons cc: current@FreeBSD.ORG Subject: Partially fixed. Re: Argh, can't get -current to build under 2.2.8+ 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 Building and installing a 3.0-current rpcgen into my main tree worked, and it now gets further. (perhaps rpcgen should be added to the toolchain along with make and friends). Now I"m dying in syscons: @ -> /usr/src/sys machine -> /usr/src/sys/i386/include cc -O -pipe -I/usr/src/sys/modules/syscons/green/.. -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -DK LD_MODULE -nostdinc -I- -I/usr/src/sys/modules/syscons/green/.. -I/usr/obj/aout/usr/src/sys/modules/syscons/green -I/usr/obj/aout/us r/src/sys/modules/syscons/green/@ -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/sys/modules/syscons/green/green_saver.c /usr/src/sys/modules/syscons/green/green_saver.c:121: warning: initialization from incompatible pointer type ld -Bshareable -o green_saver.ko green_saver.o ===> sys/modules/syscons/logo @ -> /usr/src/sys machine -> /usr/src/sys/i386/include cc -O -pipe -I/usr/src/sys/modules/syscons/logo/.. -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -DKL D_MODULE -nostdinc -I- -I/usr/src/sys/modules/syscons/logo/.. -I/usr/obj/aout/usr/src/sys/modules/syscons/logo -I/usr/obj/aout/usr/s rc/sys/modules/syscons/logo/@ -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/sys/modules/syscons/logo/logo_saver.c /usr/src/sys/modules/syscons/logo/logo_saver.c:48: logo.c: No such file or directory /usr/src/sys/modules/syscons/logo/logo_saver.c: In function `logo_blit': /usr/src/sys/modules/syscons/logo/logo_saver.c:61: `logo_img' undeclared (first use this function) /usr/src/sys/modules/syscons/logo/logo_saver.c:61: (Each undeclared identifier is reported only once /usr/src/sys/modules/syscons/logo/logo_saver.c:61: for each function it appears in.) /usr/src/sys/modules/syscons/logo/logo_saver.c:61: `logo_w' undeclared (first use this function) /usr/src/sys/modules/syscons/logo/logo_saver.c: In function `logo_update': /usr/src/sys/modules/syscons/logo/logo_saver.c:87: `logo_w' undeclared (first use this function) /usr/src/sys/modules/syscons/logo/logo_saver.c:88: `logo_h' undeclared (first use this function) /usr/src/sys/modules/syscons/logo/logo_saver.c: In function `logo_saver': /usr/src/sys/modules/syscons/logo/logo_saver.c:111: `logo_pal' undeclared (first use this function) /usr/src/sys/modules/syscons/logo/logo_saver.c: At top level: /usr/src/sys/modules/syscons/logo/logo_saver.c:159: warning: initialization from incompatible pointer type *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 On Mon, 28 Dec 1998, Chris Timmons wrote: > > No, John Birrell spent a lot of time working on the > upgrade so that you could get to 3.0-current.elf from 2.2.x. I've done > this recently and was impressed that all of my 2.2.6 era applications > continued to work flawlessly under 3.0/elf. Even XF86_SVGA! Of course I > went back and rebuilt everything in order to get rid of the aout > libraries, but it will work. Don't forget to update /etc files, which > include some ldconfig parameters for aout in rc.conf. > > -Chris > > On Mon, 28 Dec 1998, Jaye Mathisen wrote: > > > > > Just: > > > > make world > > > > on a 2.2.8 box, with -current supped today. > > > > As I read the makefile, that's the proper method, the aout to elf is for > > converting from a 3.0 aout system to a 3.0 elf system. > > > > If you're on a really old 2.x system, then the Makefile.upgrade is used to > > build a few things that won't work w/o it... But since I'm fairly current > > in the stable branch (how's that for mixing tags, labels, and versions? > > :)), I should be OK. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 19:31:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA07392 for freebsd-current-outgoing; Mon, 28 Dec 1998 19:31:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA07386 for ; Mon, 28 Dec 1998 19:31:40 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id LAA70165; Tue, 29 Dec 1998 11:31:07 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812290331.LAA70165@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: Ken McKittrick , freebsd-current@FreeBSD.ORG Subject: Re: keeping IPFILTER (was Re: wanton Atticizing is bad) In-reply-to: Your message of "Mon, 28 Dec 1998 14:27:41 PST." <199812282227.OAA13094@dingo.cdrom.com> Date: Tue, 29 Dec 1998 11:31:05 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > > Hello > > > > I don't see how dumping IPFILTER would be a good thing. It is actively > > supported by the developer and runs on Linux, Solaris, *BSD, etc. > > The manifest problem with ipfilter is that the copy in our tree is not > being maintained by the author. > > The obvious solution is to remove that copy, and provide a mechanism > for the author-distributed version to neatly integrate. Provided all > the correct hooks are in place, all it would take is the build/load of > the ipfilter KLD. Exactly.. I really think this could really be better handled as a port that does a modload/kldload at boot time. Cheers, -Peter -- Peter Wemm Netplex Consulting "No coffee, No workee!" :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 19:35:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08100 for freebsd-current-outgoing; Mon, 28 Dec 1998 19:35:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08094 for ; Mon, 28 Dec 1998 19:35:35 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id LAA70186; Tue, 29 Dec 1998 11:34:55 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812290334.LAA70186@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Doug Rabson , FreeBSD current users Subject: Re: How do I build an a.out kld? In-reply-to: Your message of "Tue, 29 Dec 1998 10:00:25 +1030." <19981229100025.K12346@freebie.lemis.com> Date: Tue, 29 Dec 1998 11:34:54 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Monday, 28 December 1998 at 19:44:59 +0800, Peter Wemm wrote: > > Doug Rabson wrote: > >> On Mon, 28 Dec 1998, Greg Lehey wrote: > > [..] > >>> 2. I could build an a.out kld. Unfortunately, there's an > >>> (undocumented) program called gensetdefs which runs against the > >>> objects, and expects only ELF files. It doesn't understand an > >>> -aout flag. Can I get past this problem? > >> > >> Are you using bsd.kmod.mk? If you look at it, gensetdefs is only used for > >> elf. Linking an a.out module is even simpler: > >> > >> ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} ${OBJS} ${KMODDEPS} > >> > >> Try 'make OBJFORMAT=aout' and see what happens. > > > > Err, my recollection was that it needed to be in the environment, ie more > > like: env OBJFORMAT=aout make > > Neither of these answer the original question: how to I get gensetdefs > to work on a.out objects? You shouldn't.. It's elf-only by design - it's an emulation for linker sets that the a.out ld did. bsd.kmod.mk should be handling all this for you already: .if defined(KLDMOD) .if ${OBJFORMAT} == elf gensetdefs ${OBJS} ${CC} ${CFLAGS} -c setdef0.c ${CC} ${CFLAGS} -c setdef1.c ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} setdef0.o ${OBJS} setdef1.o ${KMODDEPS} .else ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} ${OBJS} ${KMODDEPS} .endif .else ${LD} -r ${LDFLAGS:N-static} -o tmp.o ${OBJS} [..] Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 19:45:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09007 for freebsd-current-outgoing; Mon, 28 Dec 1998 19:45:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lohi.clinet.fi (lohi.clinet.fi [194.100.0.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08996 for ; Mon, 28 Dec 1998 19:45:31 -0800 (PST) (envelope-from hsu@mail.clinet.fi) Received: from katiska.clinet.fi (katiska.clinet.fi [194.100.0.4]) by lohi.clinet.fi (8.9.1/8.9.0) with ESMTP id FAA12768; Tue, 29 Dec 1998 05:45:24 +0200 (EET) Received: (from hsu@localhost) by katiska.clinet.fi (8.9.0/8.9.0) id FAA12591; Tue, 29 Dec 1998 05:45:12 +0200 (EET) From: Heikki Suonsivu MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13960.20551.6406.312531@katiska.clinet.fi> Date: Tue, 29 Dec 1998 05:45:11 +0200 (EET) To: obrien@nuxi.ucdavis.edu Cc: Heikki Suonsivu , freebsd-current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: <19981228100010.B28404@nuxi.com> References: <199812272253.OAA23572@bubble.didi.com.newsgate.clinet.fi> <19981228100010.B28404@nuxi.com> X-Mailer: VM 6.47 under Emacs 19.34.1 Organization: Clinet Ltd, Espoo, Finland Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien writes: > On Mon, Dec 28, 1998 at 05:32:03AM +0200, Heikki Suonsivu wrote: > > > > asami@FreeBSD.ORG (Satoshi Asami) writes: > > > * The cleanups have been discussed in -core. > > > > > > There was no agreement about pcvt. > > > > I do not mind removing pcvt *after* vt220 emulation is supported by > > Or doing it 1st thing in 3.1-CURRENT, after 3.0-STABLE is branched. This > makes our intentions clear, and gives pcvt people time to realize they > either need to write vt100 emulation in syscons or loss the > functionality. This still does not answer the issue. Why it has to be removed ? > -- > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) -- Heikki Suonsivu / Clinet Oy / Tekniikantie 12 / FI-02150 Espoo / FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 19:47:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA09218 for freebsd-current-outgoing; Mon, 28 Dec 1998 19:47:12 -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 TAA09190 for ; Mon, 28 Dec 1998 19:47:07 -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 OAA01768; Tue, 29 Dec 1998 14:16:15 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id OAA32890; Tue, 29 Dec 1998 14:16:17 +1030 (CST) Message-ID: <19981229141616.C32696@freebie.lemis.com> Date: Tue, 29 Dec 1998 14:16:16 +1030 From: Greg Lehey To: Peter Wemm Cc: Doug Rabson , FreeBSD current users Subject: Re: How do I build an a.out kld? References: <19981229100025.K12346@freebie.lemis.com> <199812290334.LAA70186@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812290334.LAA70186@spinner.netplex.com.au>; from Peter Wemm on Tue, Dec 29, 1998 at 11:34:54AM +0800 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 X-Mutt-References: <199812290334.LAA70186@spinner.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tuesday, 29 December 1998 at 11:34:54 +0800, Peter Wemm wrote: > Greg Lehey wrote: >> On Monday, 28 December 1998 at 19:44:59 +0800, Peter Wemm wrote: >>> Doug Rabson wrote: >>>> On Mon, 28 Dec 1998, Greg Lehey wrote: >>> [..] >>>>> 2. I could build an a.out kld. Unfortunately, there's an >>>>> (undocumented) program called gensetdefs which runs against the >>>>> objects, and expects only ELF files. It doesn't understand an >>>>> -aout flag. Can I get past this problem? >>>> >>>> Are you using bsd.kmod.mk? If you look at it, gensetdefs is only used for >>>> elf. Linking an a.out module is even simpler: >>>> >>>> ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} ${OBJS} ${KMODDEPS} >>>> >>>> Try 'make OBJFORMAT=aout' and see what happens. >>> >>> Err, my recollection was that it needed to be in the environment, ie more >>> like: env OBJFORMAT=aout make >> >> Neither of these answer the original question: how to I get gensetdefs >> to work on a.out objects? > > You shouldn't.. It's elf-only by design - it's an emulation for linker > sets that the a.out ld did. > > bsd.kmod.mk should be handling all this for you already: > > .if defined(KLDMOD) > .if ${OBJFORMAT} == elf > gensetdefs ${OBJS} > ${CC} ${CFLAGS} -c setdef0.c > ${CC} ${CFLAGS} -c setdef1.c > ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} setdef0.o ${OBJS} setdef1.o > ${KMODDEPS} > .else > ${LD} -Bshareable ${LDFLAGS} -o ${.TARGET} ${OBJS} ${KMODDEPS} > .endif > .else > ${LD} -r ${LDFLAGS:N-static} -o tmp.o ${OBJS} > [..] Well, something didn't work, but it's not important, since I've now moved to ELF (and almost have things working). Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 20:02:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11131 for freebsd-current-outgoing; Mon, 28 Dec 1998 20:02:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles205.castles.com [208.214.165.205]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11062 for ; Mon, 28 Dec 1998 20:01:59 -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 TAA15263; Mon, 28 Dec 1998 19:58:46 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812290358.TAA15263@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Heikki Suonsivu cc: obrien@nuxi.ucdavis.edu, freebsd-current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Tue, 29 Dec 1998 05:45:11 +0200." <13960.20551.6406.312531@katiska.clinet.fi> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Dec 1998 19:58:45 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > David O'Brien writes: > > On Mon, Dec 28, 1998 at 05:32:03AM +0200, Heikki Suonsivu wrote: > > > > > > asami@FreeBSD.ORG (Satoshi Asami) writes: > > > > * The cleanups have been discussed in -core. > > > > > > > > There was no agreement about pcvt. > > > > > > I do not mind removing pcvt *after* vt220 emulation is supported by > > > > Or doing it 1st thing in 3.1-CURRENT, after 3.0-STABLE is branched. This > > makes our intentions clear, and gives pcvt people time to realize they > > either need to write vt100 emulation in syscons or loss the > > functionality. > > This still does not answer the issue. Why it has to be removed ? The author has abandoned it, and nobody else serious has stepped forward to maintain it. We need to have a single console driver, and syscons is 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 Mon Dec 28 20:08:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA11734 for freebsd-current-outgoing; Mon, 28 Dec 1998 20:08:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gamefish.pcola.gulf.net (gamefish.pcola.gulf.net [198.69.72.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA11729 for ; Mon, 28 Dec 1998 20:08:26 -0800 (PST) (envelope-from psalzman@gamefish.pcola.gulf.net) Received: from localhost (psalzman@localhost) by gamefish.pcola.gulf.net (8.9.1/8.9.1) with ESMTP id WAA14804; Mon, 28 Dec 1998 22:07:43 -0600 (CST) (envelope-from psalzman@gamefish.pcola.gulf.net) Date: Mon, 28 Dec 1998 22:07:43 -0600 (CST) From: Phillip Salzman To: "Jordan K. Hubbard" cc: Brian Feldman , Pat Barron , current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? In-Reply-To: <2791.914887804@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 Ahh, goodie On Mon, 28 Dec 1998, Jordan K. Hubbard wrote: > > IPFILTER too > > Nope. Only proposed, not done. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 20:33:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14144 for freebsd-current-outgoing; Mon, 28 Dec 1998 20:33:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Chuska.ConSys.COM (Chuska.ConSys.COM [209.141.107.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14132 for ; Mon, 28 Dec 1998 20:33:19 -0800 (PST) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (ip-17-196.prc.primenet.com [207.218.17.196]) by Chuska.ConSys.COM (8.9.1/8.9.1) with ESMTP id VAA17862 for ; Mon, 28 Dec 1998 21:33:00 -0700 (MST) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.1/8.8.7) with ESMTP id VAA46406 for ; Mon, 28 Dec 1998 21:29:55 -0700 (MST) Message-Id: <199812290429.VAA46406@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: Re: Partially fixed. Re: Argh, can't get -current to build under 2.2.8+ In-reply-to: Your message of "Mon, 28 Dec 1998 18:58:21 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Dec 1998 21:29:54 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Building and installing a 3.0-current rpcgen into my main tree worked, and > it now gets further. (perhaps rpcgen should be added to the toolchain > along with make and friends). And for a slighter different version with the same flu... Following Eivind's diagnosis earlier today I did a make all install in src/usr.bin/rpcgen, then an aout make buildworld, and that fixed the "~August"-current aout-build-world to "recent"-current failure. Thanks! Russell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 20:39:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA14886 for freebsd-current-outgoing; Mon, 28 Dec 1998 20:39:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA14881 for ; Mon, 28 Dec 1998 20:39:01 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id PAA08379 for ; Tue, 29 Dec 1998 15:08:43 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA25894; Tue, 29 Dec 1998 15:08:43 +1030 Date: Tue, 29 Dec 1998 15:08:42 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: current@FreeBSD.ORG Subject: MSDOS filesystems being corrupted? 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 Recently (past few months, unable to be more specific, sorry) I've noticed my msdos partitions being declared "damaged" by Nortun Utilities under win95 after I've been writing to them under freebsd (specifically, disk doctor will find lost clusters and "repair" them by removing the file.) All I usually need to do is create a few (large? The last one which got reaped was about 40MB) files on the DOS partition - I don't notice any problems accessing them under bsd. Has anyone else seen this behaviour? Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 21:09:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA17610 for freebsd-current-outgoing; Mon, 28 Dec 1998 21:09:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA17597 for ; Mon, 28 Dec 1998 21:09:48 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu ((IDENT root)@rac1.wam.umd.edu [128.8.10.141]) by po4.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id AAA13443; Tue, 29 Dec 1998 00:10:16 -0500 (EST) Received: from rac1.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA27118; Tue, 29 Dec 1998 00:09:21 -0500 (EST) Received: from localhost by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id AAA27113; Tue, 29 Dec 1998 00:09:20 -0500 (EST) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Tue, 29 Dec 1998 00:09:19 -0500 (EST) From: Kenneth Wayne Culver To: Kris Kennaway cc: current@FreeBSD.ORG Subject: Re: MSDOS filesystems being corrupted? 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 > Recently (past few months, unable to be more specific, sorry) I've noticed my > msdos partitions being declared "damaged" by Nortun Utilities under win95 > after I've been writing to them under freebsd (specifically, disk doctor will > find lost clusters and "repair" them by removing the file.) All I usually need > to do is create a few (large? The last one which got reaped was about 40MB) > files on the DOS partition - I don't notice any problems accessing them under > bsd. > > Has anyone else seen this behaviour? > I have seen this behavior, but only on floppies, that's wierd about your norton, Scandisk doesn't give me any problems on my msdos partition, but I don't put large files there. I mostly just read from that disk. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Dec 28 21:52:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21256 for freebsd-current-outgoing; Mon, 28 Dec 1998 21:52:10 -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 VAA21250 for ; Mon, 28 Dec 1998 21:52:06 -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 IAA10320 for ; Tue, 29 Dec 1998 08:46:11 +0300 (MSK) (envelope-from osa@etrust.ru) Date: Tue, 29 Dec 1998 08:46:11 +0300 (MSK) From: oZZ!!! To: current@FreeBSD.ORG Subject: make buildworld fail... 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! Today make buildworld fail... .................. ===> sys/modules/syscons/logo @ -> /usr/src/sys machine -> /usr/src/sys/i386/include cc -O2 -pipe -m486 -I/usr/src/sys/modules/syscons/logo/.. -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/src/sys/modules/syscons/logo/.. -I/usr/obj/elf/usr/src/sys/modules/syscons/logo -I/usr/obj/elf/usr/src/sys/modules/syscons/logo/@ -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/sys/modules/syscons/logo/logo_saver.c /usr/src/sys/modules/syscons/logo/logo_saver.c:48: logo.c: No such file or directory /usr/src/sys/modules/syscons/logo/logo_saver.c: In function `logo_blit': /usr/src/sys/modules/syscons/logo/logo_saver.c:61: `logo_img' undeclared (first use this function) /usr/src/sys/modules/syscons/logo/logo_saver.c:61: (Each undeclared identifier is reported only once /usr/src/sys/modules/syscons/logo/logo_saver.c:61: for each function it appears in.) /usr/src/sys/modules/syscons/logo/logo_saver.c:61: `logo_w' undeclared (first use this function) /usr/src/sys/modules/syscons/logo/logo_saver.c: In function `logo_update': /usr/src/sys/modules/syscons/logo/logo_saver.c:87: `logo_w' undeclared (first use this function) /usr/src/sys/modules/syscons/logo/logo_saver.c:88: `logo_h' undeclared (first use this function) /usr/src/sys/modules/syscons/logo/logo_saver.c: In function `logo_saver': /usr/src/sys/modules/syscons/logo/logo_saver.c:111: `logo_pal' undeclared (first use this function) /usr/src/sys/modules/syscons/logo/logo_saver.c: At top level: /usr/src/sys/modules/syscons/logo/logo_saver.c:159: warning: initialization from incompatible pointer type *** Error code 1 Stop. *** Error code 1 Stop. 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 Mon Dec 28 22:56:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29146 for freebsd-current-outgoing; Mon, 28 Dec 1998 22:56:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vanessa.eliuk.org (pme37.sunshine.net [209.17.178.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29138 for ; Mon, 28 Dec 1998 22:56:55 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.1/8.8.8) with SMTP id WAA00469; Mon, 28 Dec 1998 22:55:39 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Mon, 28 Dec 1998 22:54:59 -0800 (PST) From: "Kevin G. Eliuk" Reply-To: "Kevin G. Eliuk" To: Kenneth Wayne Culver cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: MSDOS filesystems being corrupted? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Dec 1998, Kenneth Wayne Culver wrote: > > Recently (past few months, unable to be more specific, sorry) I've noticed my > > msdos partitions being declared "damaged" by Nortun Utilities under win95 > > after I've been writing to them under freebsd (specifically, disk doctor will > > find lost clusters and "repair" them by removing the file.) All I usually need > > to do is create a few (large? The last one which got reaped was about 40MB) > > files on the DOS partition - I don't notice any problems accessing them under > > bsd. > > > > Has anyone else seen this behaviour? > > > I have seen this behavior, but only on floppies, that's wierd about your > norton, Scandisk doesn't give me any problems on my msdos partition, but I > don't put large files there. I mostly just read from that disk. After a recent botch with partition magic I was able to recover 1.5MB of files, reformat the partition and replace them. Other than some serious fragmentation as far as I know nothing was lost, actually I think the performance improved :) I believe this was after a Dec22 build. Could it be something in NU. -- Regards, Kevin G. Eliuk Discover Rock Solid, Discover 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 Mon Dec 28 23:00:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29647 for freebsd-current-outgoing; Mon, 28 Dec 1998 23:00:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vanessa.eliuk.org (pme37.sunshine.net [209.17.178.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29642 for ; Mon, 28 Dec 1998 23:00:48 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.1/8.8.8) with SMTP id XAA00497; Mon, 28 Dec 1998 23:00:05 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Mon, 28 Dec 1998 22:59:42 -0800 (PST) From: "Kevin G. Eliuk" Reply-To: "Kevin G. Eliuk" To: Kenneth Wayne Culver cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: MSDOS filesystems being corrupted? 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, 28 Dec 1998, Kevin G. Eliuk wrote: > After a recent botch with partition magic I was able to recover 1.5GB of ^^ Oops! -- Regards, Kevin G. Eliuk Discover Rock Solid, Discover 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 Mon Dec 28 23:53:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA04571 for freebsd-current-outgoing; Mon, 28 Dec 1998 23:53:01 -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 XAA04564 for ; Mon, 28 Dec 1998 23:52:59 -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 XAA01107 for ; Mon, 28 Dec 1998 23:48:45 -0800 (PST) Date: Mon, 28 Dec 1998 23:48:45 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: OK, 99% success. Re: Argh, can't get -current to build under 2.2.8+ 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 syscons logo screensaver doesn't compile for me. After building rpcgen and installing it, then a make -k world (to skip the problems with syscons), my upgrade from 2.2.8 to 3.0-current as of 12/28/98 is complete. OK, 1 reboot to check that the merges from /usr/src/etc were OK, and moving the libraries to the aout subdirs... Frankly, that makes me feel bad that I didn't just trust it, and run ldconfig manually, but I figure the score is still, NT reboots, 8977, FreeBSD reboots 5, so I'm still ahead of the game... Thanks to those of you that tossed out ideas on how to make the upgrade go as smoothly as possible... So it seems a quick hack to make sure that rpcgen is built and used as part of the toolchain will pretty much fix up anybody who wants to upgrade... On Mon, 28 Dec 1998, Chris Timmons wrote: > > Are you doing a 'make aout-to-elf-build'? Or simply a buildworld on > 2.2.8-stable with -current /usr/src? If the former, it worked not so long > ago; you might want to back up your -current sources to about 12/18. > > -Chris > > > > 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 29 00:02:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05332 for freebsd-current-outgoing; Tue, 29 Dec 1998 00:02:31 -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 AAA05324 for ; Tue, 29 Dec 1998 00:02:27 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id TAA18299; Tue, 29 Dec 1998 19:04:57 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812290804.TAA18299@cimlogic.com.au> Subject: Re: OK, 99% success. Re: Argh, can't get -current to build under 2.2.8+ In-Reply-To: from Jaye Mathisen at "Dec 28, 98 11:48:45 pm" To: mrcpu@internetcds.com (Jaye Mathisen) Date: Tue, 29 Dec 1998 19:04:57 +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 Jaye Mathisen wrote: > So it seems a quick hack to make sure that rpcgen is built and used as > part of the toolchain will pretty much fix up anybody who wants to > upgrade... The problem isn't with rpcgen. It is that the object directories were mangled by ache when he attempted to make the buildworld use the same directories as a manual make. I plan to fix that by teaching `make' to use getobjformat(3). Since it's the bushfire season, I don't expect that change to be readily accepted. Sigh. -- 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 Tue Dec 29 00:41:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08891 for freebsd-current-outgoing; Tue, 29 Dec 1998 00:41:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PACIFICO.mail.telepac.pt (mail2.telepac.pt [194.65.3.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08885 for ; Tue, 29 Dec 1998 00:41:02 -0800 (PST) (envelope-from jpedras@mail.telepac.pt) Received: from maneca.tafkap.priv ([194.65.203.16]) by PACIFICO.mail.telepac.pt (Intermail v3.1 117 241) with ESMTP id <19981229084043.UCB8145@maneca.tafkap.priv>; Tue, 29 Dec 1998 08:40:43 +0000 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, 29 Dec 1998 08:42:05 -0000 (GMT) From: Joao Pedras To: oZZ!!! Subject: RE: make buildworld fail... Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm having exactly the same problem... : | On 29-Dec-98 oZZ!!! wrote: > Today make buildworld fail... > .................. > ===> sys/modules/syscons/logo > @ -> /usr/src/sys > machine -> /usr/src/sys/i386/include > cc -O2 -pipe -m486 -I/usr/src/sys/modules/syscons/logo/.. -DKERNEL > -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -DKLD_MODULE > -nostdinc -I- -I/usr/src/sys/modules/syscons/logo/.. > -I/usr/obj/elf/usr/src/sys/modules/syscons/logo > -I/usr/obj/elf/usr/src/sys/modules/syscons/logo/@ > -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/sys/modules/syscons/logo/lo > go_s > aver.c > /usr/src/sys/modules/syscons/logo/logo_saver.c:48: logo.c: No such file or > directory > /usr/src/sys/modules/syscons/logo/logo_saver.c: In function `logo_blit': ---------------------------------------------- Sent using XFMail on 29-Dec-98 at 08:41:13 GMT This message was sent by XFMail proudly powered by FreeBSD-Stable ---------------------------------------------- "Life to you is a bold and dashing responsibility" -- a Mary Chung's fortune cookie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 00:56:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09966 for freebsd-current-outgoing; Tue, 29 Dec 1998 00:56:12 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rossel.saarnet.de (rossel.saarnet.de [145.253.240.29]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA09959 for ; Tue, 29 Dec 1998 00:56:03 -0800 (PST) (envelope-from doehrm@aubi.de) Received: from igate.aubi.de (root@igate.aubi.de [145.253.242.249]) by rossel.saarnet.de (8.8.8/8.8.8) with ESMTP id JAA19842; Tue, 29 Dec 1998 09:57:53 +0100 (MET) Received: from soraya.aubi.de ([170.56.121.252]) by igate.aubi.de (8.8.7/8.8.7) with ESMTP id LAA28078; Tue, 29 Dec 1998 11:07:53 +0100 Received: from exchange.aubi.de (EXCHANGE.aubi.de [170.56.121.91]) by soraya.aubi.de (8.9.1/8.9.1) with ESMTP id KAA27477; Tue, 29 Dec 1998 10:01:28 +0100 (CET) Received: by EXCHANGE.aubi.de with Internet Mail Service (5.5.2232.9) id ; Tue, 29 Dec 1998 09:48:52 +0100 Message-ID: From: =?iso-8859-1?Q?Markus_D=F6hr?= To: "'Joao Pedras'" , oZZ!!! Cc: current@FreeBSD.ORG Subject: RE: make buildworld fail... Date: Tue, 29 Dec 1998 09:47:52 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id AAA09960 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ===> sys/modules/syscons/logo @ -> /usr/src/sys machine -> /usr/src/sys/i386/include cc -nostdinc -O -pipe -I/usr/src/sys/modules/syscons/logo/.. -DKERNEL -Wreturn- type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototype s -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunus ed -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/src/sys/modules/ syscons/logo/.. -I/usr/obj/elf/usr/src/sys/modules/syscons/logo -I/usr/obj/elf/u sr/src/sys/modules/syscons/logo/@ -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr /src/sys/modules/syscons/logo/logo_saver.c /usr/src/sys/modules/syscons/logo/logo_saver.c:48: logo.c: No such file or direc tory /usr/src/sys/modules/syscons/logo/logo_saver.c: In function `logo_blit': /usr/src/sys/modules/syscons/logo/logo_saver.c:61: `logo_img' undeclared (first use this function) looks like the same too... .CURRENT - supped an hour ago... -- Markus Doehr IT Admin AUBI Baubeschläge GmbH Tel.: +49 6503 917 152 Fax : +49 6503 917 119 e-Mail: doehrm@aubi.de MD1139-RIPE ************************* > -----Original Message----- > From: Joao Pedras [mailto:jpedras@mail.telepac.pt] > Sent: Tuesday, December 29, 1998 9:42 AM > To: oZZ!!! > Cc: current@FreeBSD.ORG > Subject: RE: make buildworld fail... > > > I'm having exactly the same problem... : | > > On 29-Dec-98 oZZ!!! wrote: > > Today make buildworld fail... > > .................. > > ===> sys/modules/syscons/logo > > @ -> /usr/src/sys > > machine -> /usr/src/sys/i386/include > > cc -O2 -pipe -m486 -I/usr/src/sys/modules/syscons/logo/.. -DKERNEL > > -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit > -Wnested-externs > > -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline > > -Wuninitialized -Wformat -Wunused -fformat-extensions > -ansi -DKLD_MODULE > > -nostdinc -I- -I/usr/src/sys/modules/syscons/logo/.. > > -I/usr/obj/elf/usr/src/sys/modules/syscons/logo > > -I/usr/obj/elf/usr/src/sys/modules/syscons/logo/@ > > -I/usr/obj/elf/usr/src/tmp/usr/include -c > /usr/src/sys/modules/syscons/logo/lo > > go_s > > aver.c > > /usr/src/sys/modules/syscons/logo/logo_saver.c:48: logo.c: > No such file or > > directory > > /usr/src/sys/modules/syscons/logo/logo_saver.c: In function > `logo_blit': > > ---------------------------------------------- > Sent using XFMail on 29-Dec-98 at 08:41:13 GMT > This message was sent by XFMail > proudly powered by FreeBSD-Stable > ---------------------------------------------- > > "Life to you is a bold and dashing responsibility" > -- a Mary Chung's fortune cookie > > > 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 29 01:13:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11073 for freebsd-current-outgoing; Tue, 29 Dec 1998 01:13:27 -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 BAA11067; Tue, 29 Dec 1998 01:13:25 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA49423; Tue, 29 Dec 1998 09:13:01 GMT Date: Tue, 29 Dec 1998 09:13:01 +0000 (GMT) From: Doug Rabson To: Satoshi Asami cc: freebsd-current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? In-Reply-To: <199812290000.QAA26160@silvia.hip.berkeley.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, 28 Dec 1998, Satoshi Asami wrote: > * From: j@uriah.heep.sax.de (J Wunsch) > > * The fd driver is overdue for a rewrite as well, but i haven't found > > I think Jesus Monroy Jr. had it already done. Now that brings back memories... Happy days.. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 01:20:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11793 for freebsd-current-outgoing; Tue, 29 Dec 1998 01:20:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA11778 for ; Tue, 29 Dec 1998 01:20:53 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id KAA12545 for freebsd-current@FreeBSD.ORG; Tue, 29 Dec 1998 10:20:32 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id KAA26645; Tue, 29 Dec 1998 10:13:59 +0100 (MET) (envelope-from j) Message-ID: <19981229101359.02508@uriah.heep.sax.de> Date: Tue, 29 Dec 1998 10:13:59 +0100 From: J Wunsch To: freebsd-current@FreeBSD.ORG Subject: Re: So, exactly what *was* purged? Reply-To: Joerg Wunsch References: <199812282343.AAA24246@uriah.heep.sax.de> <19981228155945.B7980@wopr.caltech.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19981228155945.B7980@wopr.caltech.edu>; from Matthew Hunt on Mon, Dec 28, 1998 at 03:59:45PM -0800 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Matthew Hunt wrote: > > Whether now or later, ft will die some day. (pcvt will, too, but most > > likely only after a replacement is available for a good VTxxx > > emulation.) > > I assume that "run screen" is not a suitable solution for people > wishing to run VT applications at the console? It wouldn't, given that the alternative (to have your console behaving like a VT100) is already easy at hand. No additional process involved, no port/package to install, just a kernel recompilation. Right now, it seems the `Grand Unified Console Driver' dream from almost 6 years ago is about to happen anytime soon... -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 02:20:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15240 for freebsd-current-outgoing; Tue, 29 Dec 1998 02:20:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15220 for ; Tue, 29 Dec 1998 02:20:43 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id LAA13153 for freebsd-current@freebsd.org; Tue, 29 Dec 1998 11:20:22 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id LAA26748; Tue, 29 Dec 1998 11:14:21 +0100 (MET) (envelope-from j) Date: Tue, 29 Dec 1998 11:14:21 +0100 (MET) Message-Id: <199812291014.LAA26748@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <13960.20551.6406.312531@katiska.clinet.fi> <199812290358.TAA15263@dingo.cdrom.com> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: wanton Atticizing is bad X-Original-Newsgroups: local.freebsd.current To: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: (pcvt) >> This still does not answer the issue. Why it has to be removed ? > > The author has abandoned it, and nobody else serious has stepped > forward to maintain it. Sorry, but that's completely untrue. The author has never abandoned it. Just the opposite, since the author joined the committer's crew a few days ago, he even offered to maintain it himself now for the time being. I've been in charge of maintenance until now, and pending one still unanswered mostly cosmetic fix submitted by Bruce, and pending an overdue unifdef sweep, you can follow the commitlogs and see that pcvt actually _is_ maintained. However, the last known (to me, at least) bugs have already been fixed somewhere in 1996. It's just that it has a stable feature set, but that shouldn't be confused with total lack of maintenance. Sure, the days of pcvt are counted. But more about this can be read in another thread. > We need to have a single console driver, and syscons is it. While it will probably keep the name `syscons', it can't and won't be the current syscons (*). Again, see another thread in this mailinglist. (*) I have mentioned it more than once that the design of the current syscons cannot house a decent VT220 emulation, since 256 characters are way too few for this. What pcvt did is trading colors (only 8 instead of 16) for character cells (512 instead of 256). This suffices mostly, albeit i think it's still not enough for something like supporting Cyrillic charactersets simultaneously with ISO8859-1. The latter probably requires to keep the graphics card in graphics mode all the time. That's a little slower, but given the today's graphics cards probably doable (unlike 6 years ago). Hopefully the new console driver that's currently in its design stage might allow for all this. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 02:21:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15468 for freebsd-current-outgoing; Tue, 29 Dec 1998 02:21:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15312 for ; Tue, 29 Dec 1998 02:21:00 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id LAA13154 for freebsd-current@freebsd.org; Tue, 29 Dec 1998 11:20:39 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id LAA26761; Tue, 29 Dec 1998 11:18:04 +0100 (MET) (envelope-from j) Date: Tue, 29 Dec 1998 11:18:04 +0100 (MET) Message-Id: <199812291018.LAA26761@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <199812282343.AAA24246@uriah.heep.sax.de> <199812290000.QAA26160@silvia.hip.berkeley.edu> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: So, exactly what *was* purged? X-Original-Newsgroups: local.freebsd.current To: freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG asami@FreeBSD.ORG (Satoshi Asami) wrote: > * The fd driver is overdue for a rewrite as well, but i haven't found > > I think Jesus Monroy Jr. had it already done. :-)) Well, but that rewrite didn't gain much, to the best of my knowledge. I'm not sure whether i've still got a copy of his work at all... In addition to a general cleanup, there are exactly two items on the wishlist for a floppy driver rewrite, and i wouldn't consider the task successful unless those goald have been met: support for 2.88 MB floppies, as rare as they might be, but they should be supported, and an automatic format detection, something even my CP/M floppy driver already had. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 02:21:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA15498 for freebsd-current-outgoing; Tue, 29 Dec 1998 02:21:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA15489 for ; Tue, 29 Dec 1998 02:21:12 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id LAA13155; Tue, 29 Dec 1998 11:20:45 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id LAA26775; Tue, 29 Dec 1998 11:20:11 +0100 (MET) (envelope-from j) Date: Tue, 29 Dec 1998 11:20:11 +0100 (MET) Message-Id: <199812291020.LAA26775@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Anybody having luck with upgrading *old* 3.0 SMP installs to new? X-Original-Newsgroups: local.freebsd.current To: freebsd-current@FreeBSD.ORG cc: Jaye Mathisen Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaye Mathisen wrote: > I have a 3 processor SMP box running an jan/feb or so release of 3.0, wich > a may kernel. Working fine, but want to get current. I've got a box at work that was about the same age, and i upgraded it to -current a few weeks ago. Upgrading way older systems (> ~ 1 year) from source however is virtually impossible due to a ton of bootstrap problems. It's probably easier to install the binaries from a 3.0 CD then. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 03:20:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA18977 for freebsd-current-outgoing; Tue, 29 Dec 1998 03:20:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA18971 for ; Tue, 29 Dec 1998 03:20:29 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id VAA09793; Tue, 29 Dec 1998 21:50:10 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA07747; Tue, 29 Dec 1998 21:50:09 +1030 Date: Tue, 29 Dec 1998 21:50:08 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: "Kevin G. Eliuk" Cc: Kenneth Wayne Culver , current@FreeBSD.ORG Subject: Re: MSDOS filesystems being corrupted? 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, 28 Dec 1998, Kevin G. Eliuk wrote: > Could it be something in NU. It is possible. I'll see if I can get scandisk to find any damage. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 03:33:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA20131 for freebsd-current-outgoing; Tue, 29 Dec 1998 03:33:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Guard.PolyNet.Lviv.UA (Guard.PolyNet.Lviv.UA [194.44.138.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA20114 for ; Tue, 29 Dec 1998 03:33:27 -0800 (PST) (envelope-from pam@polynet.lviv.ua) From: pam@polynet.lviv.ua Received: (qmail 14002 invoked by alias); 29 Dec 1998 11:32:28 -0000 Received: (qmail 13997 invoked from network); 29 Dec 1998 11:32:28 -0000 Received: from postoffice.polynet.lviv.ua (194.44.138.1) by guard.polynet.lviv.ua with SMTP; 29 Dec 1998 11:32:28 -0000 Received: (qmail 25893 invoked by uid 1001); 29 Dec 1998 11:32:27 -0000 Date: 29 Dec 1998 13:32:27 +0200 Date: Tue, 29 Dec 1998 13:32:27 +0200 (EET) X-Sender: pam@NetSurfer.lp.lviv.ua To: current@FreeBSD.ORG Subject: Transproxy: IPFilter or IPFW (was RE:wanton atticizing ...) In-Reply-To: <199812281827.KAA29541@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everybody, In the discussion about transparent proxy support everybody should remember about transparent support of other protocols besides HTTP. It is only use of Host headers, that gives Squid ability to do transparency without patching the source. Taking into consideration other protocols - Telnet, FTP, POP3, etc proxy needs to get information about connection destination and THAT is specific for redirection scheme. E.g IPFilter has a ioctl to get destination. I haven't seen any sample code for doing that under IPFW, should I use getsockname or what? For me, it is extremely inconvinient to have two filtering solutions on FreeBSD each having some unique features - Luigi's Dummynet for IPFW and platform independence and supported by other applications like FWTK, transparent proxy support of IPFilter :-( Just my 0.02 cents Adrian Pavlykevych email: System Administrator phone/fax: +380 (322) 742041 State University "Lvivska Polytechnica" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 03:52:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA21182 for freebsd-current-outgoing; Tue, 29 Dec 1998 03:52:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lion.plab.ku.dk (lion.plab.ku.dk [130.225.105.49]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA21177 for ; Tue, 29 Dec 1998 03:52:37 -0800 (PST) (envelope-from tobez@lion.plab.ku.dk) Received: from localhost (3315 bytes) by lion.plab.ku.dk via sendmail with P:stdio/R:bind_hosts/T:inet_zone_bind_smtp (sender: ) (ident using unix) id for ; Tue, 29 Dec 1998 12:53:12 +0100 (CET) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Nov-8) To: Eivind Eklund Cc: Jeroen Ruigrok/Asmodai , Palle Girgensohn , freebsd-current@FreeBSD.ORG Subject: Re: make world (aout lkm broken) References: <3687D766.A56CB6F0@partitur.se> <19981228213553.N53810@follo.net> From: Anton Berezin Date: 29 Dec 1998 12:53:12 +0100 In-Reply-To: Eivind Eklund's message of Mon, 28 Dec 1998 21:35:53 +0100 Message-ID: <867lvbw4ev.fsf@lion.plab.ku.dk> Lines: 77 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Eivind Eklund writes: > On Mon, Dec 28, 1998 at 09:35:26PM +0100, Jeroen Ruigrok/Asmodai wrote: > > On 28-Dec-98 Palle Girgensohn wrote: > > > Hi! > > > > > > I removed /usr/src/lkm, re-cvsupped, made clean, amd remade. It walks > > > past the lkm (it's removed completely in current as of a few days ago). > > > I have other problems, though: > > > > > > cc -O -pipe -DYP -I/usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc > > > -I/usr/obj/aout/disk3/src/tmp/usr/include > > > -I/usr/obj/aout/disk3/src/tmp/usr/include -c nfs_prot_xdr.c -o > > > nfs_prot_xdr.o > > > In file included from nfs_prot_xdr.c:6: > > > /usr/obj/aout/disk3/src/tmp/usr/include/rpcsvc/nfs_prot.h:265: parse > > > error before `uint64' > > > This problem is due to rpcgen being severely out of date, and somebody > breaking the search for the freshly built rpcgen in 'make buildworld'. > > I've not yet traced down exactly why or when the search was broken, > but it probably needs to be fixed if upgrades from old -currents or > from -stable are to work. Thanks for the implicit suggestion. ;-) Seriously, for those of you who like me had this nfs_prot.h problems trying to upgrade from 2.2.7 --- it helps: # cd /usr/src/usr.bin/rpcgen # make && make install # cd ../.. # make aout-to-elf-build Unfortunately, there is another problem further ahead: cc -O -pipe -I/usr/src/usr.sbin/i4b/isdnd/../isdnmonitor -I/usr/src/usr.sbin/i4b /isdnd/../isdntel -I/usr/obj/elf/usr/src/usr.sbin/i4b/isdnd -DDEBUG -DUSE_RTPRIO -DUSE_CURSES -DI4B_EXTERNAL_MONITOR -I/usr/obj/elf/usr/src/tmp/usr/include -o isdnd rc_parse.o rc_scan.o main.o rc_config.o log.o curses.o process.o rates.o msghdl.o fsm.o support.o timer.o exec.o dial.o monitor.o pcause.o controller.o a lias.o -lcurses /usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libtermcap.so.2, needed b y /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so, not found (try using --rpath) /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetnum' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgoto' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetflag' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tputs' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetent' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetstr' *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -- Anton Berezin The Protein Laboratory, University of Copenhagen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 04:06:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24413 for freebsd-current-outgoing; Tue, 29 Dec 1998 04:06:45 -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 EAA24380 for ; Tue, 29 Dec 1998 04:06:36 -0800 (PST) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Received: from Old-Man.Home (acc2-205.telip.uni-sb.de [134.96.112.205]) by uni-sb.de (8.9.1a/1998121400) with ESMTP id NAA24583 for ; Tue, 29 Dec 1998 13:06:06 +0100 (CET) Received: from wurzelausix.cs.uni-sb.de (localhost [127.0.0.1]) by Old-Man.Home (8.9.1/8.9.1) with ESMTP id MAA03723 for ; Tue, 29 Dec 1998 12:43:46 +0100 (CET) (envelope-from netchild@wurzelausix.cs.uni-sb.de) Message-Id: <199812291143.MAA03723@Old-Man.Home> Date: Tue, 29 Dec 1998 12:43:44 +0100 (CET) From: Alexander Leidinger Subject: nlpt & polling mode didn't work 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, $Subject anymore after cvsup (98.12.24). The working one is around release (sorry, can't be more specific). The problem: It takes a looooong time to send data to the printer. config: controller ppbus1 device nlpt1 at ppbus1 device ppc1 at isa? port 0x3bc tty Bye, Alexander. -- "Darth Vader sleeps with a Teddywookie." Fortune cookie http://netchild.home.pages.de/ A.Leidinger @ wurzelausix.cs.uni-sb.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 04:08:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA24625 for freebsd-current-outgoing; Tue, 29 Dec 1998 04:08:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from relay.linet.it (relay.linet.it [194.185.24.71]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA24619 for ; Tue, 29 Dec 1998 04:08:34 -0800 (PST) (envelope-from staff@linet.it) Received: from oma.linet.it (unverified [194.185.24.77]) by relay.linet.it (EMWAC SMTPRS 0.83) with SMTP id ; Tue, 29 Dec 1998 12:57:12 +0100 Message-ID: <007301be3e21$b2102d00$4d18b9c2@oma.linet.it> Reply-To: "andrea" From: "andrea" To: Subject: Upgrading from 2.1..X. Date: Tue, 12 Jan 1999 12:50:05 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all! I need to upgrade my pre-2.2 FreeBSD system to current distrib. There are many services on this system (like named,squid,httpd and so on)and i wonder if is possible to upgrade it in a 'soft' way (e.g. without have to stop the services for a long time) So if i first upgrade the kernel,can i still use older binaries or i must recompile the whole tree in one shot? Bye To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 04:28:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25919 for freebsd-current-outgoing; Tue, 29 Dec 1998 04:28:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25914 for ; Tue, 29 Dec 1998 04:28:12 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id WAA10642; Tue, 29 Dec 1998 22:57:53 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA30026; Tue, 29 Dec 1998 22:57:52 +1030 Date: Tue, 29 Dec 1998 22:57:51 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: andrea Cc: current@FreeBSD.ORG Subject: Re: Upgrading from 2.1..X. In-Reply-To: <007301be3e21$b2102d00$4d18b9c2@oma.linet.it> 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, 12 Jan 1999, andrea wrote: > I need to upgrade my pre-2.2 FreeBSD system to current distrib. > There are many services on this system (like named,squid,httpd and so on)and > i wonder if is possible > to upgrade it in a 'soft' way (e.g. without have to stop the services for a > long time) > > So if i first upgrade the kernel,can i still use older binaries or i must > recompile the whole tree in one shot? It is unlikely to work upgrading from source from such an old system (there are even problems upgrading from 2.2 systems, as witnessed by recent mailing list traffic). Your best bet by far is to do a binary upgrade (either from a 3.0 CD, or using the distribution off the net). The big change between 3.0 and older versions is in the executable format (ELF vs. a.out for the older versions). This should not affect you unless you recompile software, in which case it will be produced in ELF format instead of a.out (in particular. ELF libraries are not linkable against a.out executables and vice versa). If you haven't updated your ports in a while then you might want to do this, however. If you are upgrading a production server, you may want to reconsider; 3.0-CURRENT is not a suitable environment for "critical" servers, and should only be used by the experienced (please see the handbook). 3.0.1-RELEASE (and with it, the 3.0-STABLE branch) is due for release in late January - you might be better off postponing your upgrade until then. Kris ------ (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 04:45:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA27048 for freebsd-current-outgoing; Tue, 29 Dec 1998 04:45:51 -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 ESMTP id EAA27038 for ; Tue, 29 Dec 1998 04:45:30 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id NAA00439; Tue, 29 Dec 1998 13:40:12 +0100 (MET) Message-ID: <3688CDAB.35B7C35F@we.lc.ehu.es> Date: Tue, 29 Dec 1998 13:40:11 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. de Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Nicolas Souchu CC: freebsd-current@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] References: <19981219130349.11043.qmail@www0f.netaddress.usa.net> <367E88FB.B9F0D79@we.lc.ehu.es> <19981222010450.23781@breizh.prism.uvsq.fr> <368171FF.B8A5B268@we.lc.ehu.es> <19981224181948.61645@breizh.prism.uvsq.fr> <368761EF.23641D79@we.lc.ehu.es> <19981228180232.58123@breizh.prism.uvsq.fr> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nicolas Souchu wrote: > > Ooops, I've added some detection code October, 31th. It may break your > hardware. Detection of your ZIP is done in NIBBLE mode, then according to your > boot flags, EPP mode is required for transfer. > > First, try to set your bootflags to 0x3 to force PS2/NIBBLE mode and see > if it works. Then try 0x1. > > Secondly, set 0x44 to your bootflags to force your chipset generic and > avoid NS chips detection code execution. > > I completly forgot all this... please, give me some feedback. I have tried all combinations of flags, to no avail. Also, I have tried two parallel port BIOS settings: "normal" and "EPP". I don't know whether the BIOS settings are important or not. I am not a parallel port guru! :-) In all cases, the vpo controller is initialized at boot (given that the ZIP drive is on and attached), but the "da" device is not initialized. Perhaps the problem resides in the interaction between CAM (scbus/da) and the vpo controller. BTW, when booting verbosely, the ppc driver is very little verbose! I have examined ppc.c and it is plenty of "if (bootverbose) ..."; however, all these "printf"s do not show while booting. -- 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 29 06:36:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA05769 for freebsd-current-outgoing; Tue, 29 Dec 1998 06:36:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA05763 for ; Tue, 29 Dec 1998 06:36:45 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id KAA29317 for ; Tue, 29 Dec 1998 10:36:26 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 29 Dec 1998 10:36:25 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: Older 3.0-CURRENT just ... hangs? 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 Morning... This is starting to get annoying...every 15-20hrs, my server just *hangs*...no errors on the serial console, nothing... My experiences with SCSI bus hangs are generally that you can still ping the machine...this isn't the case. I'm running a 3.0-CURRENT as of a few days past -RELEASE, and am in the process of acquiring a new drive to use to upgrade to the newer -CURRENT and then swap in the drive, but that won't happen for another two weeks or so... I'm at a total loss for ideas on where to look...if anyone can point me in the right direction, maybe? A dmesg of the current system follows, in case maybe its something hardware related that will stand out for someone? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org =================================================== 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 #0: Tue Dec 22 08:09:26 EST 1998 root@hub.org:/usr/src/sys/compile/hub_org Timecounter "i8254" frequency 1193182 Hz cost 3362 ns Timecounter "TSC" frequency 267273751 Hz cost 180 ns CPU: Pentium II (267.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping=3 Features=0x80f9ff real memory = 268435456 (262144K bytes) avail memory = 258572288 (252512K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x01 int d irq 12 on pci0.4.2 chip4: rev 0x02 on pci0.4.3 ahc0: rev 0x01 int a irq 12 on pci0.9.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x01 int a irq 10 on pci0.10.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs xl0: <3Com 3c905 Fast Etherlink XL 10/100BaseTX> rev 0x00 int a irq 11 on pci0.12.0 xl0: Ethernet address: 00:60:97:d0:3c:f5 xl0: autoneg complete, link status good (full-duplex, 100Mbps) Probing for devices on PCI bus 1: Probing for PnP devices: Probing for devices on the ISA bus: sc0 not found at 0x60 ed0 at 0x280-0x29f irq 5 maddr 0xd8000 msize 8192 on isa ed0: address 00:00:c0:f0:41:c2, type SMC8416C/SMC8416BT (16 bit) lpt0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry ccd0-3: Concatenated disk drivers Waiting 2 seconds for SCSI devices to settle Sending WDTR! (probe1:ahc0:0:1:0): Sending SDTR!! Sending WDTR! (probe4:ahc0:0:4:0): Sending SDTR!! da3 at ahc0 bus 0 target 5 lun 0 da3: Fixed Direct Access SCSI2 device da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da2 at ahc0 bus 0 target 4 lun 0 da2: Fixed Direct Access SCSI3 device da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8678MB (17773500 512 byte sectors: 255H 63S/T 1106C) da9 at ahc1 bus 0 target 5 lun 0 da9: Fixed Direct Access SCSI2 device da9: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled da9: 4101MB (8399520 512 byte sectors: 255H 63S/T 522C) da4 at ahc0 bus 0 target 6 lun 0 da4: Fixed Direct Access SCSI2 device da4: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da6 at ahc1 bus 0 target 1 lun 0 da6: Fixed Direct Access SCSI2 device da6: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled da6: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI3 device da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da5 at ahc0 bus 0 target 8 lun 0 da5: Fixed Direct Access SCSI2 device da5: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da5: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da8 at ahc1 bus 0 target 4 lun 0 da8: Fixed Direct Access SCSI2 device da8: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled da8: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C) da7 at ahc1 bus 0 target 2 lun 0 da7: Fixed Direct Access SCSI2 device da7: 5.0MB/s transfers (5.0MHz, offset 15), Tagged Queueing Enabled da7: 4106MB (8410200 512 byte sectors: 255H 63S/T 523C) changing root device to da0s1a WARNING: / was not properly dismounted rtinit: wrong ifa (0xf1191100) was (0xf1157200) xl0: promiscuous mode enabled ed0: promiscuous mode enabled pid 772 (nmbd), uid 0: exited on signal 11 (core dumped) (da0:ahc0:0:0:0): tagged openings now 63 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 07:06:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08174 for freebsd-current-outgoing; Tue, 29 Dec 1998 07:06:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ywing.creative.net.au (flannan.keble.ox.ac.uk [163.1.137.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08153 for ; Tue, 29 Dec 1998 07:05:58 -0800 (PST) (envelope-from adrian@ywing.creative.net.au) Received: from ywing.creative.net.au (localhost.speedport.net [127.0.0.1] (may be forged)) by ywing.creative.net.au (8.8.8/8.8.8) with ESMTP id QAA03260 for ; Tue, 29 Dec 1998 16:05:09 +0100 (CET) Message-Id: <199812291505.QAA03260@ywing.creative.net.au> To: freebsd-current@FreeBSD.ORG Subject: Re: Transproxy: IPFilter or IPFW (was RE:wanton atticizing ...) In-reply-to: Your message of "Tue, 29 Dec 1998 13:32:27 +0200." Date: Tue, 29 Dec 1998 16:05:05 +0100 From: Adrian Chadd Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG pam@polynet.lviv.ua writes: >Hi everybody, > >In the discussion about transparent proxy support everybody should >remember about transparent support of other protocols besides HTTP. It is >only use of Host headers, that gives Squid ability to do transparency >without patching the source. > >Taking into consideration other protocols - Telnet, FTP, POP3, etc proxy >needs to get information about connection destination and THAT is specific >for redirection scheme. E.g IPFilter has a ioctl to get destination. > >I haven't seen any sample code for doing that under IPFW, should I use >getsockname or what? > >For me, it is extremely inconvinient to have two filtering solutions on >FreeBSD each having some unique features - Luigi's Dummynet for IPFW and >platform independence and supported by other applications like FWTK, >transparent proxy support of IPFilter :-( Erm, have you used the 'fw' hook yet? It behaves the same as Linux's transparent redirection facility. If you call getsockname() it will tell you where it was trying to connect to. From there you can do all sorts of useful things. IPFilter would be nice by default in a kernel *if* it was default with linux and all the other *bsd derivatives out there. To my knowledge (putting on flame proof bits here of course..) under those platforms you still have to grab IPFilter and compile it, why should it be any different in FreeBSD? (Although again, I'm not sure whether all the other *BSDs use ipfilter by default these days...) Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 07:35:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10570 for freebsd-current-outgoing; Tue, 29 Dec 1998 07:35:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from po3.wam.umd.edu (po3.wam.umd.edu [128.8.10.165]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10562 for ; Tue, 29 Dec 1998 07:35:12 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac1.wam.umd.edu ((IDENT root)@rac1.wam.umd.edu [128.8.10.141]) by po3.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with ESMTP id KAA01517; Tue, 29 Dec 1998 10:34:32 -0500 (EST) Received: from rac1.wam.umd.edu ((IDENT sendmail)@localhost [127.0.0.1]) by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id KAA15908; Tue, 29 Dec 1998 10:34:31 -0500 (EST) Received: from localhost by rac1.wam.umd.edu (8.9.0.Beta6/8.9.0.Beta6) with SMTP id KAA15903; Tue, 29 Dec 1998 10:34:30 -0500 (EST) X-Authentication-Warning: rac1.wam.umd.edu: culverk owned process doing -bs Date: Tue, 29 Dec 1998 10:34:30 -0500 (EST) From: Kenneth Wayne Culver To: Joerg Wunsch cc: freebsd-current@FreeBSD.ORG, Jaye Mathisen Subject: Re: Anybody having luck with upgrading *old* 3.0 SMP installs to new? In-Reply-To: <199812291020.LAA26775@uriah.heep.sax.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 > Upgrading way older systems (> ~ 1 year) from source however is > virtually impossible due to a ton of bootstrap problems. It's > probably easier to install the binaries from a 3.0 CD then. My system is older than that, and I have had no problem whatsoever upgrading from source. However, it is easier to use binaries. Kenneth Culver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 07:50:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12111 for freebsd-current-outgoing; Tue, 29 Dec 1998 07:50:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12085 for ; Tue, 29 Dec 1998 07:50: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 HAA00459; Tue, 29 Dec 1998 07:47:25 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812291547.HAA00459@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) cc: freebsd-current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Tue, 29 Dec 1998 11:14:21 +0100." <199812291014.LAA26748@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Dec 1998 07:47:25 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith wrote: > > (pcvt) > > >> This still does not answer the issue. Why it has to be removed ? > > > > The author has abandoned it, and nobody else serious has stepped > > forward to maintain it. > > Sorry, but that's completely untrue. The author has never abandoned > it. That's funny; Hellmuth appears to be talking with Kazu about writing a vt emulation module for syscons. You might want to check the last few messages that were exchanged on the topic. Frankly, I don't really care one way or the other when pcvt goes. But at least stick to the facts. -- \\ 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 29 07:57:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12834 for freebsd-current-outgoing; Tue, 29 Dec 1998 07:57:44 -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 HAA12823 for ; Tue, 29 Dec 1998 07:57:35 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:m6EwNtcSnfkU+MWp3xJOVJxizp1Mfyap@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 AAA30583; Wed, 30 Dec 1998 00:56:09 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id AAA16643; Wed, 30 Dec 1998 00:58:21 +0900 (JST) Message-Id: <199812291558.AAA16643@zodiac.mech.utsunomiya-u.ac.jp> To: Mike Smith cc: current@FreeBSD.ORG, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: future of syscons In-reply-to: Your message of "Mon, 28 Dec 1998 15:10:39 PST." <199812282310.PAA13485@dingo.cdrom.com> References: <199812282310.PAA13485@dingo.cdrom.com> Date: Wed, 30 Dec 1998 00:58:06 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> It is true that IRQ 1 is always assigned to the keyboard controller on >> the AT motherboard and no device can claim it because IRQ 1 line is >> not available in expansion slots. >> >> The PS/2 mouse interrupt IRQ 12 is another story. IRQ 12 is available >> to ISA and PCI bus slots and you can assign it to a device! We >> shouldn't make the keyboard controller code to claim IRQ 12 when >> either 1) a PS/2 mouse is not detected, or 2) another device is using >> or going to use IRQ 12. > >Sure; by all means disable the interrupt handler if a ps/2 mouse is not >found, I think that "disabling the interrupt handler" is not enough, the IRQ 12 resource must be released and made available to other devices to claim. >but it's important to claim the interrupt in the keyboard >controller code if one *is* found, Yes. > or even just expected to be found (eg. attached after bootup). Well, as I wrote before, ISA cards can be set to use IRQ 12, or the PCI interrupt may be mapped to this IRQ. Therefore, when no PS/2 mouse is detected at boot time, it can safely claim the IRQ 12 only if the IRQ is not used by any other devices. # The PS/2 mouse port is generally not designed for "hot plugging". # Thus, in general it is very little use reserving the IRQ 12 if the mouse # is not detected at boot time; the mouse won't be connected later. 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 29 07:59:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13195 for freebsd-current-outgoing; Tue, 29 Dec 1998 07:59:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13190 for ; Tue, 29 Dec 1998 07:59:41 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id KAA20910; Tue, 29 Dec 1998 10:59:00 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199812291559.KAA20910@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: John Birrell cc: mrcpu@internetcds.com (Jaye Mathisen), current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: OK, 99% success. Re: Argh, can't get -current to build under 2.2.8+ References: <199812290804.TAA18299@cimlogic.com.au> In-reply-to: Your message of "Tue, 29 Dec 1998 19:04:57 +1100." <199812290804.TAA18299@cimlogic.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Dec 1998 10:58:59 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The problem isn't with rpcgen. It is that the object directories were > mangled by ache when he attempted to make the buildworld use the > same directories as a manual make. I plan to fix that by teaching > `make' to use getobjformat(3). Since it's the bushfire season, I don't > expect that change to be readily accepted. Sigh. I think getting this change included before the branching will be important. I think that people running -stable expect that they can manually run make in the same place the previously did 'make world', and expect the right thing to happen. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 08:04:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA13582 for freebsd-current-outgoing; Tue, 29 Dec 1998 08:04:27 -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 IAA13572 for ; Tue, 29 Dec 1998 08:04:23 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id IAA06707 for ; Tue, 29 Dec 1998 08:04:19 -0800 (PST) To: current@FreeBSD.ORG Subject: On recent events and pending resurrections. Date: Tue, 29 Dec 1998 08:04:18 -0800 Message-ID: <6702.914947458@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Guess it's time for another state of the union announcement on this topic - sorry for keeping folks in the dark. To summarize a very long debate, we're currently considering bringing back pcvt, voxware and SOFTMODEM support and will have a vote on this in the core team shortly, the results of which we will implement by Jan 1st. If anyone has additional items from the "hit list" that they'd like to consider, please send me mail and I'll add them to the list. There has also been a fair amount of fall-out from this, with unhappiness both inside and outside the core team on how all of this came down, and one of the conclusions to come out of this is that perhaps the core team is finally in need of reconstitituion. That is a matter we'll take up for the new year, and I'll be sending more mail out on this topic as we decide how we're going to work 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 29 08:08:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14167 for freebsd-current-outgoing; Tue, 29 Dec 1998 08:08:52 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles247.castles.com [208.214.165.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14147 for ; Tue, 29 Dec 1998 08:08: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 IAA00584; Tue, 29 Dec 1998 08:04:57 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812291604.IAA00584@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Kazutaka YOKOTA cc: Mike Smith , current@FreeBSD.ORG Subject: Re: future of syscons In-reply-to: Your message of "Wed, 30 Dec 1998 00:58:06 +0900." <199812291558.AAA16643@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Dec 1998 08:04:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> It is true that IRQ 1 is always assigned to the keyboard controller on > >> the AT motherboard and no device can claim it because IRQ 1 line is > >> not available in expansion slots. > >> > >> The PS/2 mouse interrupt IRQ 12 is another story. IRQ 12 is available > >> to ISA and PCI bus slots and you can assign it to a device! We > >> shouldn't make the keyboard controller code to claim IRQ 12 when > >> either 1) a PS/2 mouse is not detected, or 2) another device is using > >> or going to use IRQ 12. > > > >Sure; by all means disable the interrupt handler if a ps/2 mouse is not > >found, > > I think that "disabling the interrupt handler" is not enough, the IRQ > 12 resource must be released and made available to other devices to claim. Poor choice of words on my part; indeed, if there is no chance of a mouse being connected, IRQ 12 is free for other uses. In most cases, there will be PnP information available to support this decision. > # The PS/2 mouse port is generally not designed for "hot plugging". > # Thus, in general it is very little use reserving the IRQ 12 if the mouse > # is not detected at boot time; the mouse won't be connected later. Ok; I get the impression that many systems don't support hot-plugged PS/2 mice, so we can probably go with the same. -- \\ 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 29 08:11:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14408 for freebsd-current-outgoing; Tue, 29 Dec 1998 08:11:02 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14403 for ; Tue, 29 Dec 1998 08:10:59 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id LAA07509; Tue, 29 Dec 1998 11:10:31 -0500 (EST) Date: Tue, 29 Dec 1998 11:10:31 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: On recent events and pending resurrections. In-Reply-To: <6702.914947458@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, 29 Dec 1998, Jordan K. Hubbard wrote: > Guess it's time for another state of the union announcement on this > topic - sorry for keeping folks in the dark. > > To summarize a very long debate, we're currently considering bringing > back pcvt, voxware and SOFTMODEM support and will have a vote on this > in the core team shortly, the results of which we will implement by > Jan 1st. If anyone has additional items from the "hit list" that > they'd like to consider, please send me mail and I'll add them to the > list. Some people also want ft back. If you'd like, I'll work on the update files that will go out for 3.0.1-RELEASE (HARDWARE.TXT, RELNOTES.TXT, UPGRADE.TXT) to make sure they reflect the current state. Let me know the final decisions and I'll fix up the docs. > > There has also been a fair amount of fall-out from this, with > unhappiness both inside and outside the core team on how all of this > came down, and one of the conclusions to come out of this is that > perhaps the core team is finally in need of reconstitituion. That is > a matter we'll take up for the new year, and I'll be sending more mail > out on this topic as we decide how we're going to work this. Uh oh! > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 29 08:33:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15909 for freebsd-current-outgoing; Tue, 29 Dec 1998 08:33:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15904 for ; Tue, 29 Dec 1998 08:33:18 -0800 (PST) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5692) with SMTP id RAA13954; Tue, 29 Dec 1998 17:33:56 +0100 (MET) Date: Tue, 29 Dec 1998 17:32:52 +0100 (MET) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: brian@worldcontrol.com cc: freebsd-current@FreeBSD.ORG Subject: Re: SANE, USB, -current step 2 In-Reply-To: <19981222144525.A334@top.worldcontrol.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 Lennart Augustsson (NetBSD) is at the moment writing a much improved and flexible Generic driver for USB. That one should give you more of a plain access to the device from user land. No date on its release though. Haven't checked his current either. Nick On Tue, 22 Dec 1998 brian@worldcontrol.com wrote: > Ok I plugged my wife's HP 4100cxi and booted with the USB extensions. > The last line look promising: > > Dec 22 22:28:40 top /kernel: ugen0: Hewlett-Packard HP ScanJet 4100C (rev 1.00/1.00) addr 2 (device class 0/0) > > Now does anyone have a primer on using the ugen device to talk to the > device? > > Perhaps /dev/ugen0 is dynamically created and I can talk serially to the > device via read/write? > > Dec 22 22:28:39 top /kernel: usbd_match > Dec 22 22:28:39 top /kernel: usb0: > Dec 22 22:28:39 top /kernel: usbd_attach > Dec 22 22:28:39 top /kernel: usbd_new_device bus=0xf07ba000 depth=0 lowspeed=0 > Dec 22 22:28:39 top /kernel: usbd_setup_pipe: dev=0xf05ac780 iface=0 ep=0xf05ac79c pipe=0xf05ac788 > Dec 22 22:28:39 top /kernel: uhci_open: pipe=0xf05ac700, addr=0, endpt=0 (0) > Dec 22 22:28:39 top /kernel: usbd_new_device: adding unit addr=1, rev=100, class=9, subclass=1, protocol=0, maxpacket=64, ls=0 > Dec 22 22:28:39 top /kernel: usbd_new_device: new dev (addr 1), dev=0xf05ac780, parent=0xf07b8780 > Dec 22 22:28:39 top /kernel: usb1 at usb0 > Dec 22 22:28:39 top /kernel: usb1: Intel UHCI root hub (class 9/1) (rev 1.00/1.00) addr 1 > Dec 22 22:28:39 top /kernel: usbd_set_config_no: (addr 1) attr=0x40, selfpowered=1, power=0, powerquirk=0 > Dec 22 22:28:39 top /kernel: usbd_set_config_no: setting new config 1 > Dec 22 22:28:39 top /kernel: usb_init_hub: getting hub descriptor > Dec 22 22:28:39 top /kernel: usbhub_init_hub: selfpowered=1, parent=0, parent->selfpowered=0 > Dec 22 22:28:39 top /kernel: usbd_setup_pipe: dev=0xf05ac780 iface=0xf07b6da0 ep=0xf07b7ea0 pipe=0xf0283a14 > Dec 22 22:28:39 top /kernel: uhci_open: pipe=0xf05ac600, addr=1, endpt=129 (1) > Dec 22 22:28:39 top /kernel: usbd_init_port: adding hub port=1 status=0x0100 change=0x0000 > Dec 22 22:28:39 top /kernel: usbd_init_port: adding hub port=2 status=0x0101 change=0x0001 > Dec 22 22:28:39 top /kernel: uhub_explore: st > Dec 22 22:28:39 top /kernel: atus change hub=1 port=2 > Dec 22 22:28:39 top /kernel: usbd_reset_port: port 2 reset done, error=0 > Dec 22 22:28:39 top /kernel: usbd_new_device bus=0xf07ba000 depth=1 lowspeed=0 > Dec 22 22:28:39 top /kernel: usbd_setup_pipe: dev=0xf05ac500 iface=0 ep=0xf05ac51c pipe=0xf05ac508 > Dec 22 22:28:39 top /kernel: uhci_open: pipe=0xf05ac480, addr=0, endpt=0 (1) > Dec 22 22:28:39 top /kernel: usbd_new_device: adding unit addr=2, rev=100, class=0, subclass=0, protocol=0, maxpacket=8, ls=0 > Dec 22 22:28:39 top /kernel: usbd_new_device: new dev (addr 2), dev=0xf05ac500, parent=0xf07b7eb0 > Dec 22 22:28:39 top /kernel: usbd_new_device: no device driver found > Dec 22 22:28:39 top /kernel: usbd_set_config_no: (addr 2) attr=0x60, selfpowered=1, power=0, powerquirk=0 > Dec 22 22:28:39 top /kernel: usbd_set_config_no: setting new config 1 > Dec 22 22:28:39 top /kernel: usbd_set_config_no: free old config > Dec 22 22:28:40 top /kernel: usbd_set_config_no: (addr 2) attr=0x60, selfpowered=1, power=0, powerquirk=0 > Dec 22 22:28:40 top /kernel: usbd_set_config_no: setting new config 1 > Dec 22 22:28:40 top /kernel: usbd_new_device: no interface drivers found > Dec 22 22:28:40 top /kernel: ugen0 > Dec 22 22:28:40 top /kernel: ugen0: Hewlett-Packard HP ScanJet 4100C (rev 1.00/1.00) addr 2 (device class 0/0) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- ISIS/STA, T.P.270, Joint Research Centre, 21020 Ispra, Italy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 08:40:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16899 for freebsd-current-outgoing; Tue, 29 Dec 1998 08:40:29 -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 IAA16894 for ; Tue, 29 Dec 1998 08:40:26 -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 PAA15307; Tue, 29 Dec 1998 15:30:29 +0100 From: Luigi Rizzo Message-Id: <199812291430.PAA15307@labinfo.iet.unipi.it> Subject: Re: On recent events and pending resurrections. To: jkh@zippy.cdrom.com (Jordan K. Hubbard) Date: Tue, 29 Dec 1998 15:30:28 +0100 (MET) Cc: current@FreeBSD.ORG In-Reply-To: <6702.914947458@zippy.cdrom.com> from "Jordan K. Hubbard" at Dec 29, 98 08:03:59 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > To summarize a very long debate, we're currently considering bringing > back pcvt, voxware and SOFTMODEM support and will have a vote on this > in the core team shortly, the results of which we will implement by > Jan 1st. an ideal date with everybody drunk and asleep after the midnight parties :) cheers 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 29 08:48:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17663 for freebsd-current-outgoing; Tue, 29 Dec 1998 08:48:34 -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 IAA17655 for ; Tue, 29 Dec 1998 08:48:33 -0800 (PST) (envelope-from forrie@navinet.net) Received: from forrie (black.navinet.net [206.25.93.86]) by spook.navinet.net (8.9.1a/8.9.1) with SMTP id LAA21341 for ; Tue, 29 Dec 1998 11:50:33 -0500 (EST) Message-Id: <4.1.19981229113057.0098e590@206.25.93.69> X-Sender: forrie@206.25.93.8 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 29 Dec 1998 11:31:46 -0500 To: freebsd-current@FreeBSD.ORG From: Forrest Aldrich Subject: CVS issues In-Reply-To: <9026692.914837060@DEIMOS.REM.CMU.EDU> References: <19981228071255.S1333@ns1.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What's up with this recurring problem with buildworld on 3.0 and with cvsup.freebsd.org refusing connections? Is the mafia taking over? :) Forrest To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 08:52:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18228 for freebsd-current-outgoing; Tue, 29 Dec 1998 08:52:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hcshh.hcs.de (hcshh.hcs.de [194.123.40.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA18221 for ; Tue, 29 Dec 1998 08:52:56 -0800 (PST) (envelope-from hm@hcs.de) Received: from hcswork.hcs.de([192.76.124.5]) (3040 bytes) by hcshh.hcs.de via sendmail with P:smtp/R:inet_hosts/T:smtp (sender: ) id for ; Tue, 29 Dec 1998 17:52:21 +0100 (MET) (Smail-3.2.0.101 1997-Dec-17 #2 built 1998-Jun-26) Received: by hcswork.hcs.de (Smail3.1.29.0 #12) id m0zv2QQ-00001KC; Tue, 29 Dec 98 17:55 MET Message-Id: From: hm@hcs.de (Hellmuth Michaelis) Subject: Re: wanton Atticizing is bad In-Reply-To: <199812291547.HAA00459@dingo.cdrom.com> from Mike Smith at "Dec 29, 98 07:47:25 am" To: mike@smith.net.au (Mike Smith) Date: Tue, 29 Dec 1998 17:55:18 +0100 (MET) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG Reply-To: hm@hcs.de Organization: HCS Hanseatischer Computerservice GmbH X-Mailer: ELM [version 2.4ME+ PL39 (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 >From the keyboard of Mike Smith: > > (pcvt) > > > > > The author has abandoned it, and nobody else serious has stepped > > > forward to maintain it. > > > > Sorry, but that's completely untrue. The author has never abandoned > > it. > > That's funny; Hellmuth appears to be talking with Kazu about writing a > vt emulation module for syscons. You might want to check the last few > messages that were exchanged on the topic. I am talking to Kazu, because i understand and acknowledge the need for a single console driver for FreeBSD, because i am too lazy (and too busy) to always reinvent the wheel for pcvt, and syscons has some good things i'd like to have and use use (i.e. scrollback). I made a mistake in not seeing that i have to more actively caring about the things i need in FreeBSD, but i rely for many reasons on pcvt's functionality (!, not pcvt itself) in a FreeBSD kernel, so i were really stupid if i were abandoning something i need that much. Things would be so much easier for everyone involved if syscons could be "split up" into an environment where new emulators can be added on the fly, and this aspect alone is worth to talk to Kazu and Soeren. I always wanted to work on a "pcvt-NT", but the sheer amount of (doubled) work prevented me from proceeding, so this is a chance for me to concentrate on the things i like to do and the things i need, and get done what i had in mind all the time. If Kazu really wants it and is persistent enough and gets the necessary support from the core and the community, there is a chance that we get this long overdue thing done, and my public talking to Kazu was just meant as a hearable offer to contribute my part to that project and let pcvt rest in peace when there is a replacement available. hellmuth (hopeing he has not jumped on anybodys foot with this) -- Hellmuth Michaelis Tel +49 40 559747-70 HCS Hanseatischer Computerservice GmbH Fax +49 40 559747-77 Oldesloer Strasse 97-99 Mail hm [at] hcs.de 22457 Hamburg WWW http://www.hcs.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 08:57:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18676 for freebsd-current-outgoing; Tue, 29 Dec 1998 08:57: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 IAA18671 for ; Tue, 29 Dec 1998 08:57:37 -0800 (PST) (envelope-from jfesler@gigo.com) From: jfesler@gigo.com Received: from heaven.gigo.com (heaven.gigo.com [207.173.133.57]) by heaven.gigo.com (Postfix) with SMTP id 098491171; Tue, 29 Dec 1998 08:57:18 -0800 (PST) Date: Tue, 29 Dec 1998 08:57:17 -0800 (PST) To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: <199812291547.HAA00459@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 > That's funny; Hellmuth appears to be talking with Kazu about writing a > vt emulation module for syscons. You might want to check the last few > messages that were exchanged on the topic. Sad part is, is that I'm not sure much of this matters. When _I_ need vtXXX emulation, I don't rebuilt a pcvt kernel. I simply run "screen" :-). That fixes many problems, as well as offers cut-and-paste and its other unique features.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 09:05:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19468 for freebsd-current-outgoing; Tue, 29 Dec 1998 09:05:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from horst.bfd.com (horst.bfd.com [12.9.219.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19461 for ; Tue, 29 Dec 1998 09:05:36 -0800 (PST) (envelope-from ejs@bfd.com) Received: from HARLIE.bfd.com (bastion.bfd.com [12.9.219.14]) by horst.bfd.com (8.9.1/8.9.1) with ESMTP id JAA21977 for ; Tue, 29 Dec 1998 09:05:18 -0800 (PST) (envelope-from ejs@bfd.com) Date: Tue, 29 Dec 1998 09:05:18 -0800 (PST) From: "Eric J. Schwertfeger" To: current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-Reply-To: <199812290121.RAA25987@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Mon, 28 Dec 1998 17:14:01 -0500 > From: Christian Kuhtz > Subject: Re: wanton Atticizing is bad > > On Mon, Dec 28, 1998 at 04:04:16PM -0600, Phillip Salzman wrote: > > > You can do that with natd. > > > > That is possible, but not logical. Say you have 2000 > > dialup users attempting to access the web at the same time... all > > coming from different IP addresses -- would you want the packet > > scanning to go at the Cisco, or at the NATd? Its simple to do > > a transparent proxy from the cisco, and does not require too much on > > the squid side (IPFILTER), with less on the router. > > I thought the issue was, given IPFILTER or IPFW, can we do everything with > IPFW that IPFILTER and other kludges did? So that we can start to phase > out IPFILTER. There's two areas that IPFILTER seems to work better than IPFW, and both are NAT-related. The first is that we are seeing problems with large FTP's through natd. I hadn't had the chance to debug this before switching to IPFILTER due to the second reason. natd and SKIP just don't play well together. SKIP marks packets it has seen in the kernel memory copy of the packet, and natd, being a userspace program, doesn't see this marking, so it gets reinjected without the marking, so SKIP rejects the packet on the second pass, because it thinks it's seeing an unencrypted packet from a host that should only be sending encrypted packets. Aside from these two issues, I'd never use IPFILTER as IPFW is more natural, and I feel like I have much more control over what gets NAT'ed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 10:01:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24457 for freebsd-current-outgoing; Tue, 29 Dec 1998 10:01:29 -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 KAA24451 for ; Tue, 29 Dec 1998 10:01:27 -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 KAA21013; Tue, 29 Dec 1998 10:01:05 -0800 (PST) Date: Tue, 29 Dec 1998 10:01:05 -0800 (PST) From: Chris Timmons To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: CVS issues In-Reply-To: <4.1.19981229113057.0098e590@206.25.93.69> 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 cvsupd process on cvsup.freebsd.org was wedged for a while this morning. Try now. -Chris On Tue, 29 Dec 1998, Forrest Aldrich wrote: > What's up with this recurring problem with buildworld on 3.0 and > with cvsup.freebsd.org refusing connections? Is the mafia taking over? :) > > > Forrest > > > 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 29 10:12:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25891 for freebsd-current-outgoing; Tue, 29 Dec 1998 10:12:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25886 for ; Tue, 29 Dec 1998 10:12:16 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id OAA32342 for ; Tue, 29 Dec 1998 14:11:57 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 29 Dec 1998 14:11:57 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: more on hangs... 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 Jus curious, but has anyone had any *known* problems with an ASUS P2B motherboard? Anything that I might want to look at? We're pretty much down to the only thing that has changed is the motherboard, so either its a BIOS problem(?), or possibly memory...but everything was working reasonably well prior to the upgrade, except a few -CURRENT related things that I really have to upgrade for :( Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 10:19:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26514 for freebsd-current-outgoing; Tue, 29 Dec 1998 10:19:36 -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 KAA26506 for ; Tue, 29 Dec 1998 10:19:33 -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 KAA06771; Tue, 29 Dec 1998 10:19:15 -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 KAA11513; Tue, 29 Dec 1998 10:19:15 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 29 Dec 1998 10:19:15 -0800 (PST) Message-Id: <199812291819.KAA11513@vashon.polstra.com> To: forrie@navinet.net Subject: Re: CVS issues Newsgroups: polstra.freebsd.current In-Reply-To: <4.1.19981229113057.0098e590@206.25.93.69> References: <19981228071255.S1333@ns1.adsu.bellsouth.com> Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <4.1.19981229113057.0098e590@206.25.93.69>, Forrest Aldrich wrote: > What's up with this recurring problem with buildworld on 3.0 and > with cvsup.freebsd.org refusing connections? Is the mafia taking over? :) Why do you insist on using cvsup.freebsd.org? There are dozens of mirror sites listed in the FreeBSD Handbook. If you're having trouble getting into one of them, then try a different one. This is the Internet. Take advantage of what it can do for you. -- 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 Tue Dec 29 10:21:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26708 for freebsd-current-outgoing; Tue, 29 Dec 1998 10:21:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lohi.clinet.fi (lohi.clinet.fi [194.100.0.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26687 for ; Tue, 29 Dec 1998 10:21:05 -0800 (PST) (envelope-from hsu@mail.clinet.fi) Received: from katiska.clinet.fi (katiska.clinet.fi [194.100.0.4]) by lohi.clinet.fi (8.9.1/8.9.0) with ESMTP id UAA12349; Tue, 29 Dec 1998 20:21:02 +0200 (EET) Received: (from hsu@localhost) by katiska.clinet.fi (8.9.0/8.9.0) id UAA27560; Tue, 29 Dec 1998 20:20:45 +0200 (EET) To: Mike Smith Cc: freebsd-current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad References: <199812290358.TAA15263@dingo.cdrom.com.newsgate.clinet.fi> From: Heikki Suonsivu Date: 29 Dec 1998 20:20:44 +0200 In-Reply-To: Mike Smith's message of 29 Dec 1998 06:20:28 +0200 Message-ID: Lines: 38 X-Mailer: Gnus v5.3/Emacs 19.34 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: ... > > > Or doing it 1st thing in 3.1-CURRENT, after 3.0-STABLE is branched. This > > > makes our intentions clear, and gives pcvt people time to realize they > > > either need to write vt100 emulation in syscons or loss the > > > functionality. > > > > This still does not answer the issue. Why it has to be removed ? > > The author has abandoned it, and nobody else serious has stepped > forward to maintain it. Deadlocks in NFS (?) have been around for years, but I still do not think NFS should be removed. Whether the code has a maintainer or not does not mean that it does or does not work for some purpose or be useful even with its limitations. > We need to have a single console driver, and syscons is it. Why there has to be a single console driver ? Why pcvt's existence bothers people who are not using 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 -- Heikki Suonsivu / Clinet Oy / Tekniikantie 12 / FI-02150 Espoo / FINLAND, hsu@clinet.fi mobile +358-40-5519679 work +358-9-43542270 fax -4555276 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 10:21:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA26740 for freebsd-current-outgoing; Tue, 29 Dec 1998 10:21:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mortar.carlson.com (mortar.carlson.com [208.240.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA26730 for ; Tue, 29 Dec 1998 10:21:24 -0800 (PST) (envelope-from veldy@visi.com) Received: from mortar.carlson.com (root@localhost) by mortar.carlson.com with ESMTP id MAA03344 for ; Tue, 29 Dec 1998 12:20:19 -0600 (CST) Received: from w142844 ([172.25.99.35]) by mortar.carlson.com with SMTP id MAA03340 for ; Tue, 29 Dec 1998 12:20:18 -0600 (CST) Message-ID: <01b401be3357$fe88c4a0$236319ac@w142844.carlson.com> From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: /dev/acd - anybody know how to use with CD-RW? Date: Tue, 29 Dec 1998 12:21:03 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_01B1_01BE3325.B3A823E0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_01B1_01BE3325.B3A823E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Does anybody know how to configure and use the new /dev/acd device for = use with a CD-RW (HP7200i - Internal ATAPI CD-Writer)? Tom Veldhouse veldy@visi.com ------=_NextPart_000_01B1_01BE3325.B3A823E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Does anybody know how to configure = and use the=20 new /dev/acd device for use with a CD-RW (HP7200i - Internal ATAPI=20 CD-Writer)?
 
Tom Veldhouse
veldy@visi.com
 
------=_NextPart_000_01B1_01BE3325.B3A823E0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 10:26:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27212 for freebsd-current-outgoing; Tue, 29 Dec 1998 10:26:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27190 for ; Tue, 29 Dec 1998 10:25:58 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA077154811; Tue, 29 Dec 1998 07:33:31 -0500 Date: Tue, 29 Dec 1998 07:33:31 -0500 (EST) From: Bill Fumerola To: John Polstra Cc: forrie@navinet.net, current@FreeBSD.ORG Subject: Re: CVS issues In-Reply-To: <199812291819.KAA11513@vashon.polstra.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Dec 1998, John Polstra wrote: > > What's up with this recurring problem with buildworld on 3.0 and > > with cvsup.freebsd.org refusing connections? Is the mafia taking over? :) > > Why do you insist on using cvsup.freebsd.org? There are dozens of > mirror sites listed in the FreeBSD Handbook. If you're having trouble > getting into one of them, then try a different one. This is the > Internet. Take advantage of what it can do for you. I know this may have been suggested before, but why doesn't cvsup.FreeBSD.org become cvsup1.FreeBSD.org and cvsup.FreeBSD.org become round robin DNS for the (north american) mirrors? - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 10:28:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27407 for freebsd-current-outgoing; Tue, 29 Dec 1998 10:28:53 -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 KAA27402 for ; Tue, 29 Dec 1998 10:28:52 -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 KAA06889; Tue, 29 Dec 1998 10:28:31 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id KAA11548; Tue, 29 Dec 1998 10:28:31 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 29 Dec 1998 10:28:31 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Bill Fumerola Subject: Re: CVS issues Cc: current@FreeBSD.ORG, forrie@navinet.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 29-Dec-98 Bill Fumerola wrote: > > I know this may have been suggested before, but why doesn't > cvsup.FreeBSD.org become cvsup1.FreeBSD.org and cvsup.FreeBSD.org become > round robin DNS for the (north american) mirrors? That is probably what we'll do, once the dust settles from the holidays. These particular holidays are so dusty that it could take 11 months. ;-) 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 Tue Dec 29 12:11:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05563 for freebsd-current-outgoing; Tue, 29 Dec 1998 12:11:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05550 for ; Tue, 29 Dec 1998 12:11:05 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id VAA09553; Tue, 29 Dec 1998 21:10:24 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id WAA02733; Tue, 29 Dec 1998 22:12:04 GMT (envelope-from son) Message-ID: <19981229221203.55044@breizh.prism.uvsq.fr> Date: Tue, 29 Dec 1998 22:12:03 +0000 From: Nicolas Souchu To: Alexander Leidinger Cc: current@FreeBSD.ORG Subject: Re: nlpt & polling mode didn't work References: <199812291143.MAA03723@Old-Man.Home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199812291143.MAA03723@Old-Man.Home>; from Alexander Leidinger on Tue, Dec 29, 1998 at 12:43:44PM +0100 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 29, 1998 at 12:43:44PM +0100, Alexander Leidinger wrote: > >Hi, > >$Subject anymore after cvsup (98.12.24). >The working one is around release (sorry, can't be more specific). September, October...? > >The problem: >It takes a looooong time to send data to the printer. Printing is ok? This is polling... and interrupts? >config: >controller ppbus1 >device nlpt1 at ppbus1 >device ppc1 at isa? port 0x3bc tty > What's your chipset? -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 12:12:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA05729 for freebsd-current-outgoing; Tue, 29 Dec 1998 12:12:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA05707 for ; Tue, 29 Dec 1998 12:11:59 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id EAA82011; Wed, 30 Dec 1998 04:11:25 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812292011.EAA82011@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: "Eric J. Schwertfeger" cc: current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Tue, 29 Dec 1998 09:05:18 PST." Date: Wed, 30 Dec 1998 04:11:24 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Eric J. Schwertfeger" wrote: > > > Date: Mon, 28 Dec 1998 17:14:01 -0500 > > From: Christian Kuhtz > > Subject: Re: wanton Atticizing is bad > > > > On Mon, Dec 28, 1998 at 04:04:16PM -0600, Phillip Salzman wrote: > > > > You can do that with natd. > > > > > > That is possible, but not logical. Say you have 2000 > > > dialup users attempting to access the web at the same time... all > > > coming from different IP addresses -- would you want the packet > > > scanning to go at the Cisco, or at the NATd? Its simple to do > > > a transparent proxy from the cisco, and does not require too much on > > > the squid side (IPFILTER), with less on the router. > > > > I thought the issue was, given IPFILTER or IPFW, can we do everything with > > IPFW that IPFILTER and other kludges did? So that we can start to phase > > out IPFILTER. > > There's two areas that IPFILTER seems to work better than IPFW, and both > are NAT-related. I've been discussing this with various folks. What I see as the "best" solution to overcome the problem of a poorly maintained (and old) copy in the tree is to make a port out of it and remove the bulk of the code from the tree. What this gets us: - upgrading to the latest release becomes easier. - getting ipfilter in the src tree was like fitting a square peg into a round hole. It's an unhappy arrangement to say the least. - using a loadable kernel module from the port at startup time gets us pretty much the same functionality as the in-kernel version. - hopefully a clean cutover from the old to the current ipfilter. The only folks directly inconvenienced would be router floppy type people. Of course there will be bumps along the way, but I think this is the best outcome considering that the copy in the tree is getting stale quickly, and leaving the hooks there (or implementing pfil) makes modules the job of the pot a lot easier. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 12:23:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07295 for freebsd-current-outgoing; Tue, 29 Dec 1998 12:23:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA07288 for ; Tue, 29 Dec 1998 12:23:38 -0800 (PST) (envelope-from brian@hyperreal.org) Received: (qmail 8651 invoked by uid 24); 29 Dec 1998 20:23:20 -0000 Message-Id: <4.1.19981229121528.03d98ed0@hyperreal.org> X-Sender: brian@hyperreal.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 29 Dec 1998 12:20:03 -0800 To: "Jordan K. Hubbard" , Greg Lehey From: Brian Behlendorf Subject: Re: How do I build an a.out kld? Cc: FreeBSD current users In-Reply-To: <14069.914819618@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:33 PM 12/27/98 -0800, Jordan K. Hubbard wrote: >> 1. I can build an ELF kernel. My understanding is that this will >> also require me to install the new style boot blocks. Correct? >> If so, is there any documentation on what to do here? > >Correct. > >1. cd /sys/boot && make all install >2. disklabel -B da0 (or whatever your boot disk is). > >Make sure you're also running a -current disklabel. Set KERNFORMAT=elf >in /etc/make.conf if you want to turn this on by default. I just upgraded to an ELF kernel, updated the boot blocks, and everything boots up great, except the new boot loader appears to be looking for a /boot/boot.conf (fails, then waits for 8 seconds, then boots /kernel). I noticed I have a zero-length /boot.config file - should I move that to /boot/boot.conf? I also noticed that although I had KERNFORMAT set to elf in my environment and KERNFORMAT=elf in /etc/make.conf, while configing and then building the kernel I had to set KERNFORMAT in the compile directory's Makefile before it would actually build an elf kernel. Perhaps a "make KERNFORMAT=elf" was necessary? Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- History is made at night; brian@hyperreal.org character is what you are in the dark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 12:25:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07684 for freebsd-current-outgoing; Tue, 29 Dec 1998 12:25:27 -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 MAA07674 for ; Tue, 29 Dec 1998 12:25:22 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id HAA20067; Wed, 30 Dec 1998 07:27:49 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812292027.HAA20067@cimlogic.com.au> Subject: Re: OK, 99% success. Re: Argh, can't get -current to build under 2.2.8+ In-Reply-To: <199812291559.KAA20910@whizzo.transsys.com> from "Louis A. Mamakos" at "Dec 29, 98 10:58:59 am" To: louie@TransSys.COM (Louis A. Mamakos) Date: Wed, 30 Dec 1998 07:27:48 +1100 (EST) Cc: jb@cimlogic.com.au, mrcpu@internetcds.com, 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 Louis A. Mamakos wrote: > > > The problem isn't with rpcgen. It is that the object directories were > > mangled by ache when he attempted to make the buildworld use the > > same directories as a manual make. I plan to fix that by teaching > > `make' to use getobjformat(3). Since it's the bushfire season, I don't > > expect that change to be readily accepted. Sigh. > > I think getting this change included before the branching will be > important. I think that people running -stable expect that they can > manually run make in the same place the previously did 'make world', > and expect the right thing to happen. I asked someone who always has an opinion on this stuff how strongly he'd object to me doing that to `make'. His answer was "very strongly", so I've decided not to commit the changes. I received enough "don't do that" email during the elf conversion time to last me for the rest of this century, at least. Sorry. -- 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 Tue Dec 29 12:46:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10228 for freebsd-current-outgoing; Tue, 29 Dec 1998 12:46:55 -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 MAA10223 for ; Tue, 29 Dec 1998 12:46:54 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id MAA08073; Tue, 29 Dec 1998 12:46:39 -0800 (PST) To: Brian Behlendorf cc: Greg Lehey , FreeBSD current users Subject: Re: How do I build an a.out kld? In-reply-to: Your message of "Tue, 29 Dec 1998 12:20:03 PST." <4.1.19981229121528.03d98ed0@hyperreal.org> Date: Tue, 29 Dec 1998 12:46:38 -0800 Message-ID: <8069.914964398@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just upgraded to an ELF kernel, updated the boot blocks, and everything > boots up great, except the new boot loader appears to be looking for a > /boot/boot.conf (fails, then waits for 8 seconds, then boots /kernel). I > noticed I have a zero-length /boot.config file - should I move that to > /boot/boot.conf? Yeah, /boot.config is basically obsolete though it can still be used for its old purpose, I in fact still use it to set my rootdev since I haven't grok'd how to do that yet with the new scheme. /boot/boot.conf is supposed to contain any boot commands you'd like to have run (boot.conf is actually a bad name, now that I think about it, since it implies configuration variables rather than actions - boot.rc would have been better, oh well!). After the forth system initializes, it also looks for a /boot/boot.4th which contains straight forth code to run. Andrzej Bialecki has done some really neat stuff where this is concerned, giving the forth environment a screen emulator and standard ANSI graphics capability. He shows it off in the example code, which you can enable by simply doing a: cp /usr/share/examples/bootforth/*.4th /boot > I also noticed that although I had KERNFORMAT set to elf in my environment > and KERNFORMAT=elf in /etc/make.conf, while configing and then building the Hmmm.. That's really weird! You should only need to set it in /etc/make.conf - that certainly works for me. You sure there aren't any typos in the line? :-) - 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 29 13:12:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA13605 for freebsd-current-outgoing; Tue, 29 Dec 1998 13:12:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.eecis.udel.edu (louie.udel.edu [128.175.2.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA13595 for ; Tue, 29 Dec 1998 13:12:09 -0800 (PST) (envelope-from alexandr@mail.eecis.udel.edu) Date: Tue, 29 Dec 1998 13:12:09 -0800 (PST) From: alexandr@mail.eecis.udel.edu Message-Id: <199812292112.NAA13595@hub.freebsd.org> Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa28255; 29 Dec 1998 16:09 EST To: "Jordan K. Hubbard" Cc: Brian Behlendorf , Greg Lehey , FreeBSD current users Subject: RE: How do I build an a.out kld? Organization: Mos Eisley Candy Store Reply-To: alexandr@mail.eecis.udel.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Reply to Your Message of Tue, 29 Dec 1998 12: 46:38 PST Date: Tue, 29 Dec 1998 16:09:05 -0500 From: Jerry Alexandratos Message-ID: <199812291609.aa28255@mail.eecis.udel.edu> : > I also noticed that although I had KERNFORMAT set to elf in my environment : > and KERNFORMAT=elf in /etc/make.conf, while configing and then building the : : Hmmm.. That's really weird! You should only need to set it in : /etc/make.conf - that certainly works for me. You sure there aren't : any typos in the line? :-) Just an idea. Did you do a "config -r" or a "make clean" before you built your new kernel? --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 13:56:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA17951 for freebsd-current-outgoing; Tue, 29 Dec 1998 13:56:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from assurance.rstcorp.com (assurance.rstcorp.com [206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA17944 for ; Tue, 29 Dec 1998 13:56:55 -0800 (PST) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance.rstcorp.com (8.8.8/8.8.8) id QAA01480; Tue, 29 Dec 1998 16:56:36 -0500 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma001472; Tue, 29 Dec 98 16:55:59 -0500 Received: from jabberwock.rstcorp.com (jabberwock [206.29.49.98]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id QAA01731; Tue, 29 Dec 1998 16:55:58 -0500 (EST) Received: (from vshah@localhost) by jabberwock.rstcorp.com (8.9.1/8.8.8) id QAA06411; Tue, 29 Dec 1998 16:55:57 -0500 (EST) Date: Tue, 29 Dec 1998 16:55:57 -0500 (EST) Message-Id: <199812292155.QAA06411@jabberwock.rstcorp.com> From: "Viren R. Shah" To: "Thomas T. Veldhouse" Cc: "FreeBSD-Current" Subject: Re:/dev/acd - anybody know how to use with CD-RW? In-Reply-To: <01b401be3357$fe88c4a0$236319ac@w142844.carlson.com> References: <01b401be3357$fe88c4a0$236319ac@w142844.carlson.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG TV> Does anybody know how to configure and use the new /dev/acd device TV> for use with a CD-RW (HP7200i - Internal ATAPI CD-Writer)? [BTW: I just looked at MAKEDEV, and there isn't a /dev/acd device in the script. What does the acd driver use?] In the same vein, can the acd driver be used to read CD DA (i.e. convert audio CD tracks to mp3s?) or is it still only possible with SCSI CDROMs? The reason I ask is that I get the following on boot: acd0: drive speed 2412 - 5512KB/sec, 256KB cache acd0: supported read types: CD-R, CD-RW, CD-DA ^^^^^^^ acd0: Audio: play, 256 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM unknown medium, unlocked Thanks Viren -- Viren R. Shah "I merely note, if you want to catch something, running after it isn't always the best way." -- Miles Vorkosigan (Lois McMaster Bujold, "The Mountains of Mourning") To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 14:04:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA18572 for freebsd-current-outgoing; Tue, 29 Dec 1998 14:04:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA18567 for ; Tue, 29 Dec 1998 14:04:23 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id XAA93597; Tue, 29 Dec 1998 23:03:46 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199812292203.XAA93597@freebsd.dk> Subject: Re: /dev/acd - anybody know how to use with CD-RW? In-Reply-To: <199812292155.QAA06411@jabberwock.rstcorp.com> from "Viren R. Shah" at "Dec 29, 1998 4:55:57 pm" To: viren@rstcorp.com Date: Tue, 29 Dec 1998 23:03:46 +0100 (CET) Cc: veldy@visi.com, freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Viren R. Shah wrote: > > TV> Does anybody know how to configure and use the new /dev/acd device > TV> for use with a CD-RW (HP7200i - Internal ATAPI CD-Writer)? > > [BTW: I just looked at MAKEDEV, and there isn't a /dev/acd device in > the script. What does the acd driver use?] For now use the wcd device is the same major, it will probably be changed too, but for the time being this is undecided. > In the same vein, can the acd driver be used to read CD DA > (i.e. convert audio CD tracks to mp3s?) or is it still only possible > with SCSI CDROMs? The reason I ask is that I get the following on > boot: > > acd0: drive speed 2412 - 5512KB/sec, 256KB cache > acd0: supported read types: CD-R, CD-RW, CD-DA > ^^^^^^^ > acd0: Audio: play, 256 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: CD-ROM unknown medium, unlocked You can read CDDA disk with the acd driver, I have a patched cdd that can do this on my ftp site: ftp://freebsd.dk/pub/ATAPI/cdd-* -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 14:13:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19767 for freebsd-current-outgoing; Tue, 29 Dec 1998 14:13:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19676 for ; Tue, 29 Dec 1998 14:13:14 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id WAA93567; Tue, 29 Dec 1998 22:59:09 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199812292159.WAA93567@freebsd.dk> Subject: Re: /dev/acd - anybody know how to use with CD-RW? In-Reply-To: <01b401be3357$fe88c4a0$236319ac@w142844.carlson.com> from "Thomas T. Veldhouse" at "Dec 29, 1998 12:21: 3 pm" To: veldy@visi.com (Thomas T. Veldhouse) Date: Tue, 29 Dec 1998 22:59:09 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Thomas T. Veldhouse wrote: > Does anybody know how to configure and use the new /dev/acd device for use with a CD-RW (HP7200i - Internal ATAPI CD-Writer)? You can use the scripts in /usr/share/examples/atapi to burn audio & data discs. You can use wormcontrol -f /dev/bla blank to erase CDRW discs... We have no support for a true RW filesystem on CDRW (yet). -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 14:21:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20659 for freebsd-current-outgoing; Tue, 29 Dec 1998 14:21:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from PACIFICO.mail.telepac.pt (mail2.telepac.pt [194.65.3.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20653 for ; Tue, 29 Dec 1998 14:21:18 -0800 (PST) (envelope-from jpedras@mail.telepac.pt) Received: from maneca.tafkap.priv ([194.65.203.11]) by PACIFICO.mail.telepac.pt (Intermail v3.1 117 241) with ESMTP id <19981229222058.BGIU15593@maneca.tafkap.priv>; Tue, 29 Dec 1998 22:20:58 +0000 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, 29 Dec 1998 22:22:18 -0000 (GMT) From: Joao Pedras To: =?iso-8859-1?Q?Markus_D=F6hr?= Subject: RE: make buildworld fail... Cc: current@FreeBSD.ORG, oZZ!!! Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I supped a couple hours again and it's ok now. ---------------------------------------------- Sent using XFMail on 29-Dec-98 at 22:21:08 GMT This message was sent by XFMail proudly powered by FreeBSD-Stable ---------------------------------------------- James Joyce -- an essentially private man who wished his total indifference to public notice to be universally recognized. -- Tom Stoppard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 14:23:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20893 for freebsd-current-outgoing; Tue, 29 Dec 1998 14:23:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA20884 for ; Tue, 29 Dec 1998 14:23:33 -0800 (PST) (envelope-from brian@hyperreal.org) Received: (qmail 15529 invoked by uid 24); 29 Dec 1998 22:23:15 -0000 Message-Id: <4.1.19981229135446.03d958f0@hyperreal.org> X-Sender: brian@hyperreal.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 29 Dec 1998 14:06:15 -0800 To: alexandr@mail.eecis.udel.edu, "Jordan K. Hubbard" From: Brian Behlendorf Subject: RE: How do I build an a.out kld? Cc: FreeBSD current users In-Reply-To: <199812291609.aa28255@mail.eecis.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:09 PM 12/29/98 -0500, Jerry Alexandratos wrote: >: > I also noticed that although I had KERNFORMAT set to elf in my environment >: > and KERNFORMAT=elf in /etc/make.conf, while configing and then building the >: >: Hmmm.. That's really weird! You should only need to set it in >: /etc/make.conf - that certainly works for me. You sure there aren't >: any typos in the line? :-) > >Just an idea. Did you do a "config -r" or a "make clean" before you >built your new kernel? Didn't do a config -r, but did do a "make clean" after I started getting "cannot load bioscall.o" errors at the last stage of "make". After that "make clean", a "make" did produce an elf executable. This is after, though, I changed "KERNFORMAT? = aout" to "... = elf" in /sys/i386/conf/Makefile.i386 to see if that made a difference, since I noticed that the same line was in /sys/i386/compile/pez/Makefile. I've switched it back to "aout", and did a "config -r pez", and I still see the line "KERNFORMAT?= aout" in /sys/i386/compile/pez/Makefile... but ultimately that doesn't matter, since an ELF kernel is now produced anyways. So, sorry about the false alarm. It'll be good to see some of the aout-related cruft start to dribble out of the source as the switch-over to ELF is now more-or-less mandatory for the casual -current follower (if there is such a thing). Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- History is made at night; brian@hyperreal.org character is what you are in the dark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 14:23:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20915 for freebsd-current-outgoing; Tue, 29 Dec 1998 14:23:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA20890 for ; Tue, 29 Dec 1998 14:23:34 -0800 (PST) (envelope-from brian@hyperreal.org) Received: (qmail 15543 invoked by uid 24); 29 Dec 1998 22:23:17 -0000 Message-Id: <4.1.19981229140706.048df410@hyperreal.org> X-Sender: brian@hyperreal.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 29 Dec 1998 14:10:05 -0800 To: "Jordan K. Hubbard" From: Brian Behlendorf Subject: Re: How do I build an a.out kld? Cc: FreeBSD current users In-Reply-To: <8069.914964398@zippy.cdrom.com> References: 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:46 PM 12/29/98 -0800, Jordan K. Hubbard wrote: >> I just upgraded to an ELF kernel, updated the boot blocks, and everything >> boots up great, except the new boot loader appears to be looking for a >> /boot/boot.conf (fails, then waits for 8 seconds, then boots /kernel). I >> noticed I have a zero-length /boot.config file - should I move that to >> /boot/boot.conf? > >Yeah, /boot.config is basically obsolete though it can still be used >for its old purpose, I in fact still use it to set my rootdev since I >haven't grok'd how to do that yet with the new scheme. > >/boot/boot.conf is supposed to contain any boot commands you'd like to >have run (boot.conf is actually a bad name, now that I think about it, >since it implies configuration variables rather than actions - boot.rc >would have been better, oh well!). So would a blank file tell it to boot the default immediately, or should I put "boot /kernel" in there? It's not that I really NEED those 8 seconds, it just seems like it'd be cleaner to boot directly. Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- History is made at night; brian@hyperreal.org character is what you are in the dark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 14:28:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA21529 for freebsd-current-outgoing; Tue, 29 Dec 1998 14:28:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.atl.bellsouth.net (mail.atl.bellsouth.net [205.152.0.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA21476 for ; Tue, 29 Dec 1998 14:28:00 -0800 (PST) (envelope-from wghicks@bellsouth.net) Received: from bellsouth.net (host-209-214-69-223.atl.bellsouth.net [209.214.69.223]) by mail.atl.bellsouth.net (8.8.8-spamdog/8.8.5) with ESMTP id QAA10484; Tue, 29 Dec 1998 16:45:22 -0500 (EST) Message-ID: <36895118.E8C57354@bellsouth.net> Date: Tue, 29 Dec 1998 17:00:56 -0500 From: W Gerald Hicks Organization: Fair Play, Uninc. 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 CC: jkh@zippy.cdrom.com Subject: Re: How do I build an a.out kld? Content-Type: multipart/mixed; boundary="------------78624E7EE9410BFCC358DF80" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------78624E7EE9410BFCC358DF80 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit [snips] > /boot/boot.conf is supposed to contain any boot commands you'd like to > have run (boot.conf is actually a bad name, now that I think about it, > since it implies configuration variables rather than actions - boot.rc > would have been better, oh well!). After the forth system initializes, > it also looks for a /boot/boot.4th which contains straight forth code > to run. Andrzej Bialecki has done some really neat stuff where this > is concerned, giving the forth environment a screen emulator and > standard ANSI graphics capability. He shows it off in the example > code, which you can enable by simply doing a: > > cp /usr/share/examples/bootforth/*.4th /boot > We've been having loads of fun with BootForth too. Thanks Andrzej! I tried generating console beeps (7 emit) and noticed them going to the screen. Patch attached :) Cheers, Jerry Hicks wghicks@bellsouth.net --------------78624E7EE9410BFCC358DF80 Content-Type: text/plain; charset=us-ascii; name="diffs" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="diffs" Index: src/sys/boot/i386/libi386/vidconsole.c =================================================================== RCS file: /home/ncvs/src/sys/boot/i386/libi386/vidconsole.c,v retrieving revision 1.9 diff -u -r1.9 vidconsole.c --- vidconsole.c 1998/12/22 11:51:25 1.9 +++ vidconsole.c 1998/12/29 21:37:31 @@ -119,7 +119,19 @@ return(0); /* XXX reinit? */ } +#ifdef TERM_EMU static void +vidc_biosrawputchar(int c) +{ + v86.ctl = 0; + v86.addr = 0x10; + v86.eax = 0xe00 | c; + v86.ebx = 0x7; + v86int(); +} +#endif + +static void vidc_rawputchar(int c) { int i; @@ -138,6 +150,9 @@ #else /* Emulate AH=0eh (teletype output) */ switch(c) { + case '\a': + vidc_biosrawputchar(c); + return; case '\r': curx=0; curs_move(curx,cury); --------------78624E7EE9410BFCC358DF80-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 14:36:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22479 for freebsd-current-outgoing; Tue, 29 Dec 1998 14:36:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from crap.31337.net (node1484.a2000.nl [62.108.20.132]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22474 for ; Tue, 29 Dec 1998 14:36:40 -0800 (PST) (envelope-from alexlh@funk.org) Received: from p.funk.org (nose.funk.org [194.109.86.229]) by crap.31337.net (8.9.1/8.9.1) with ESMTP id WAA22223 for ; Tue, 29 Dec 1998 22:38:39 GMT (envelope-from alexlh@funk.org) Received: from funk.org (localhost.a2000.nl [127.0.0.1]) by p.funk.org (8.9.1/8.9.1) with ESMTP id XAA00576 for ; Tue, 29 Dec 1998 23:36:11 +0100 (CET) (envelope-from alexlh@funk.org) Message-ID: <3689595A.F554B158@funk.org> Date: Tue, 29 Dec 1998 23:36:10 +0100 From: Alex Le Heux X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD current users Subject: Re: How do I build an a.out kld? References: <8069.914964398@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [various things about booting freebsd cut] Is there a detailed description of the current bootprocess available anywhere? Something that tells me exactly which bits go where and why? Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 14:57:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24777 for freebsd-current-outgoing; Tue, 29 Dec 1998 14:57:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles88.castles.com [208.214.165.88]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24749 for ; Tue, 29 Dec 1998 14:56:54 -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 OAA02396; Tue, 29 Dec 1998 14:53:43 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812292253.OAA02396@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: hm@hcs.de cc: mike@smith.net.au (Mike Smith), joerg_wunsch@uriah.heep.sax.de, freebsd-current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad In-reply-to: Your message of "Tue, 29 Dec 1998 17:55:18 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Dec 1998 14:53:43 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > If Kazu really wants it and is persistent enough and gets the necessary > support from the core and the community, there is a chance that we get > this long overdue thing done, and my public talking to Kazu was just > meant as a hearable offer to contribute my part to that project and let > pcvt rest in peace when there is a replacement available. He is, he will, and I think we're all happy to hear this. > hellmuth (hopeing he has not jumped on anybodys foot with this) Not at all. -- \\ 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 29 16:48:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06458 for freebsd-current-outgoing; Tue, 29 Dec 1998 16:48:23 -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 QAA06450 for ; Tue, 29 Dec 1998 16:48:20 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 26786 invoked by uid 1001); 30 Dec 1998 00:48:00 +0000 (GMT) To: nsouch@teaser.fr Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] In-Reply-To: Your message of "Mon, 28 Dec 1998 18:02:32 +0000" References: <19981228180232.58123@breizh.prism.uvsq.fr> 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: Wed, 30 Dec 1998 01:48:00 +0100 Message-ID: <26784.914978880@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Parallel ZIP doesn't work here, using sources CVSupped today (Dec 28th). > >Perhaps the cause isn't in the ppc/ppbus/vpo code; the problem > >I see is that da0 isn't initialized, so I think that scbus0 doesn't > >get attached to vpo0 for some reason. Some parts of the CAM code > >have changed in the last month... > > > >These are my kernel config lines related to the parallel bus: > > > >controller scbus0 # Lo necesita el ZIP paralelo. > >device da0 # Y esto también. > >controller ppbus0 # Bus paralelo > >controller vpo0 at ppbus? # ZIP paralelo > >device nlpt0 at ppbus? # Impresora > >controller ppc0 at isa? port ? tty irq 7 flags 0x04 ... > >After that, there is no mention to any "da" device. I had the same problem when I tried to use a ZIP drive (bought more than a year ago but never used before). The interface was detected as vpo0: on ppbus 0 but no da device showed up. > First, try to set your bootflags to 0x3 to force PS2/NIBBLE mode and see > if it works. Then try 0x1. > > Secondly, set 0x44 to your bootflags to force your chipset generic and > avoid NS chips detection code execution. What finally made it work for me was: EPP mode in the BIOS, and controller ppc0 at isa? port ? tty irq 7 in the kernel config. Ie. no flags at all. With this setup, my Zip drive is detected as da1 at vpo0 bus 0 target 6 lun 0 da1: Removable Direct Access SCSI-2 device da1: 196608 512 byte sectors: 64H 32S/T 96C (the size printout is non-standard, more on this below). During my testing of this, I attempted to use CAMDEBUG, with options CAMDEBUG options "CAM_DEBUG_BUS=-1" options "CAM_DEBUG_TARGET=-1" options "CAM_DEBUG_LUN=-1" options "CAM_DEBUG_FLAGS=CAM_DEBUG_INFOøCAM_DEBUG_TRACEøCAM_DEBUG_CDB" in the kernel config. With these options and "normal" parallel port mode in the BIOS (no EPP), the Zip drive is detected as: da1 at vpo0 bus 0 target 6 lun 0 da1: < > Fixed Direct Access SCSI-0 device da1: 1 0 byte sectors: 0H 0S/T 0C and the 0 byte sector size leads to a divide by zero and corresponding panic at dadone() line 1290 in sys/cam/scsi/scsi_da.c: snprintf(announce_buf, sizeof(announce_buf), "%ldMB (%d %d byte sectors: %dH %dS/T %dC)", dp->sectors / ((1024L * 1024L) / dp->secsize), dp->sectors, dp->secsize, dp->heads, dp->secs_per_track, dp->cylinders); I removed the MB printout and the corresponding calculation to avoid the divide by zero and continue testing. Maybe the sector size should be forced to 1 if it is detected as zero, to avoid the divide by zero panic? 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 Tue Dec 29 16:50:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06945 for freebsd-current-outgoing; Tue, 29 Dec 1998 16:50:06 -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 QAA06823 for ; Tue, 29 Dec 1998 16:49:10 -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 LAA05975; Wed, 30 Dec 1998 11:18:23 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA35277; Wed, 30 Dec 1998 11:18:25 +1030 (CST) Message-ID: <19981230111824.B32696@freebie.lemis.com> Date: Wed, 30 Dec 1998 11:18:24 +1030 From: Greg Lehey To: John Polstra , Bill Fumerola Cc: current@FreeBSD.ORG, forrie@navinet.net Subject: Re: CVS issues References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from John Polstra on Tue, Dec 29, 1998 at 10:28:31AM -0800 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 On Tuesday, 29 December 1998 at 10:28:31 -0800, John Polstra wrote: > On 29-Dec-98 Bill Fumerola wrote: >> >> I know this may have been suggested before, but why doesn't >> cvsup.FreeBSD.org become cvsup1.FreeBSD.org and cvsup.FreeBSD.org become >> round robin DNS for the (north american) mirrors? > > That is probably what we'll do, once the dust settles from the > holidays. These particular holidays are so dusty that it could take > 11 months. ;-) I've tended to use cvsup.FreeBSD.org because I assume that commits get there faster. How much lag is there on the other sites? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 16:56:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07547 for freebsd-current-outgoing; Tue, 29 Dec 1998 16:56:26 -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 QAA07542 for ; Tue, 29 Dec 1998 16:56:25 -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 QAA08237; Tue, 29 Dec 1998 16:56:04 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id QAA12884; Tue, 29 Dec 1998 16:56:03 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19981230111824.B32696@freebie.lemis.com> Date: Tue, 29 Dec 1998 16:56:03 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Greg Lehey Subject: Re: CVS issues Cc: forrie@navinet.net, current@FreeBSD.ORG, Bill Fumerola Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Dec-98 Greg Lehey wrote: > > I've tended to use cvsup.FreeBSD.org because I assume that commits get > there faster. How much lag is there on the other sites? Ah, I'm glad you spoke up. I didn't realize that people had that idea. Actually, practically all of the mirror sites update themselves hourly directly from freefall. In particular, cvsup{,2,3}.freebsd.org do that. So they're completely equivalent in terms of lag time. The maximum is 1 hour, and the average is 30 minutes. Note, cvsup.freebsd.org != freefall. It suffers the same lag as the other mirrors. 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 Tue Dec 29 16:59:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07982 for freebsd-current-outgoing; Tue, 29 Dec 1998 16:59: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 QAA07971 for ; Tue, 29 Dec 1998 16:59:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id QAA09099; Tue, 29 Dec 1998 16:58:55 -0800 (PST) To: John Polstra cc: Greg Lehey , forrie@navinet.net, current@FreeBSD.ORG, Bill Fumerola Subject: Re: CVS issues In-reply-to: Your message of "Tue, 29 Dec 1998 16:56:03 PST." Date: Tue, 29 Dec 1998 16:58:55 -0800 Message-ID: <9096.914979535@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ah, I'm glad you spoke up. I didn't realize that people had that > idea. Actually, practically all of the mirror sites update themselves Yep, most do actually. Definitely time to go to the round-robin DNS scheme. - 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 29 17:12:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA09057 for freebsd-current-outgoing; Tue, 29 Dec 1998 17:12:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA09047 for ; Tue, 29 Dec 1998 17:12:13 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id UAA57190; Tue, 29 Dec 1998 20:10:31 -0500 (EST) Date: Tue, 29 Dec 1998 20:10:30 -0500 (EST) From: Chuck Robey To: Forrest Aldrich cc: freebsd-current@FreeBSD.ORG Subject: Re: CVS issues In-Reply-To: <4.1.19981229113057.0098e590@206.25.93.69> 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, 29 Dec 1998, Forrest Aldrich wrote: > What's up with this recurring problem with buildworld on 3.0 and > with cvsup.freebsd.org refusing connections? Is the mafia taking over? :) Maybe folks ought to do as suggested, and use cvsup2.freebsd.org ... since I switched a while back, never once been turned away, and sessions go at twice the speed. > > > Forrest > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 17:24:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10400 for freebsd-current-outgoing; Tue, 29 Dec 1998 17:24:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10389 for ; Tue, 29 Dec 1998 17:24:55 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id RAA21875; Tue, 29 Dec 1998 17:24:23 -0800 (PST) Date: Tue, 29 Dec 1998 17:24:23 -0800 (PST) From: "Steven P. Donegan" To: Chuck Robey cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: CVS issues 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 seriously doubt I'm the only one who has shell scripted cvsup access? How about doing a DNS round robin on all cvsup sites - literally 10 minutes of work on the DNS side of things and this will no longer be any issue at all. From what I've seen over the last few days this has generated mucho man-hours of email :-) On Tue, 29 Dec 1998, Chuck Robey wrote: > On Tue, 29 Dec 1998, Forrest Aldrich wrote: > > > What's up with this recurring problem with buildworld on 3.0 and > > with cvsup.freebsd.org refusing connections? Is the mafia taking over? :) > > > Maybe folks ought to do as suggested, and use cvsup2.freebsd.org ... > since I switched a while back, never once been turned away, and sessions > go at twice the speed. > > > > > > > Forrest > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (NetBSD). > ----------------------------+----------------------------------------------- > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Steven P. Donegan email: donegan@quick.net Sr. Network Infrastructure Engineer ICBM: N 33' 47.538/W 117' 59.687 WANG Global (within 1 meter - 133 ASL) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 17:26:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10770 for freebsd-current-outgoing; Tue, 29 Dec 1998 17:26:44 -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 RAA10761 for ; Tue, 29 Dec 1998 17:26:42 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id RAA08401; Tue, 29 Dec 1998 17:25:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.1/8.9.1) id RAA13024; Tue, 29 Dec 1998 17:25:38 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <9096.914979535@zippy.cdrom.com> Date: Tue, 29 Dec 1998 17:25:38 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: "Jordan K. Hubbard" Subject: Re: CVS issues Cc: Bill Fumerola , current@FreeBSD.ORG, forrie@navinet.net, Greg Lehey Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Dec-98 Jordan K. Hubbard wrote: > Definitely time to go to the round-robin DNS scheme. The reason I haven't done it so far is because the mirrors differ in some of the little-used collections that they carry. They all carry the main source tree, but some don't carry the mailing list archives, for example. Before I can institute round-robin DNS, I need to either arrange for the relevant mirrors to carry exactly the same collections, or I need to document exactly what they carry in common. 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 Tue Dec 29 17:31:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11056 for freebsd-current-outgoing; Tue, 29 Dec 1998 17:31:11 -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 RAA11046 for ; Tue, 29 Dec 1998 17:31:08 -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 RAA05509; Tue, 29 Dec 1998 17:26:22 -0800 (PST) Date: Tue, 29 Dec 1998 17:26:22 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: Chuck Robey cc: Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: CVS issues 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 Nah, need to get some layer 4 switches running, and a FreeBSD cvsup farm going... On Tue, 29 Dec 1998, Chuck Robey wrote: > On Tue, 29 Dec 1998, Forrest Aldrich wrote: > > > What's up with this recurring problem with buildworld on 3.0 and > > with cvsup.freebsd.org refusing connections? Is the mafia taking over? :) > > > Maybe folks ought to do as suggested, and use cvsup2.freebsd.org ... > since I switched a while back, never once been turned away, and sessions > go at twice the speed. > > > > > > > Forrest > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@glue.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (NetBSD). > ----------------------------+----------------------------------------------- > > > > > > 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 29 17:40:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11634 for freebsd-current-outgoing; Tue, 29 Dec 1998 17:40:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA11629 for ; Tue, 29 Dec 1998 17:40:13 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id RAA21907; Tue, 29 Dec 1998 17:39:51 -0800 (PST) Date: Tue, 29 Dec 1998 17:39:51 -0800 (PST) From: "Steven P. Donegan" To: Jaye Mathisen cc: Chuck Robey , Forrest Aldrich , freebsd-current@FreeBSD.ORG Subject: Re: CVS issues In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Dec 1998, Jaye Mathisen wrote: > > Nah, need to get some layer 4 switches running, and a FreeBSD cvsup farm > going... > Or one of Cisco's load-distributing goodies running :-) But simple (current) bind round-robbin DNS will more than suffice in the short term. The ultimate would be a bunch of FreeBSD-SMP servers with Network Appliance NFS back-ends. More I/O and compute than anyone should enjoy :-) This is not a complex problem. If mirror sites are not true mirrors then don't put them in the round robbin. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 17:43:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12287 for freebsd-current-outgoing; Tue, 29 Dec 1998 17:43:38 -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 RAA12220 for ; Tue, 29 Dec 1998 17:43:29 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 27333 invoked by uid 1001); 30 Dec 1998 01:43:10 +0000 (GMT) To: nsouch@teaser.fr Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] In-Reply-To: Your message of "Wed, 30 Dec 1998 01:48:00 +0100" References: <26784.914978880@verdi.nethelp.no> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Wed, 30 Dec 1998 02:43:10 +0100 Message-ID: <27331.914982190@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > What finally made it work for me was: EPP mode in the BIOS, and > > controller ppc0 at isa? port ? tty irq 7 > > in the kernel config. Ie. no flags at all. With this setup, my Zip drive > is detected as > > da1 at vpo0 bus 0 target 6 lun 0 > da1: Removable Direct Access SCSI-2 device > da1: 196608 512 byte sectors: 64H 32S/T 96C A followup: There is probably a timing-related issue here. If I remove the various CAMDEBUG options, the Zip drive isn't detected. With the CAMDEBUG options (and thus lots of extra printout), it is detected. Verbose boot or not makes no difference. A diff between the boot -v messages: 211a212,222 > (probe7:vpo0:0:6:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe7:vpo0:0:6:0): ILLEGAL REQUEST asc:24,0 > (probe7:vpo0:0:6:0): Invalid field in CDB > (noperiph:xpt0:0:X:X): xpt_compile_path > (noperiph:xpt0:0:X:X): xpt_setup_ccb > (noperiph:xpt0:0:X:X): xpt_action > (noperiph:xpt0:0:X:X): xpt_free_path > (noperiph:xpt0:0:X:X): xpt_release_path > (noperiph:xpt0:0:X:X): xpt_compile_path > (noperiph:xpt0:0:X:X): xpt_setup_ccb > (noperiph:xpt0:0:X:X): xpt_action 215a227,231 > (noperiph:xpt0:0:X:X): xpt_free_path > (noperiph:xpt0:0:X:X): xpt_release_path > (noperiph:xpt0:0:X:X): xpt_compile_path > (noperiph:xpt0:0:X:X): xpt_setup_ccb > (noperiph:xpt0:0:X:X): xpt_action 224,225c240,243 < Considering FFS root f/s. < changing root device to da0s1a --- > pass2 at vpo0 bus 0 target 6 lun 0 > pass2: Removable Direct Access SCSI-2 device > (noperiph:xpt0:0:X:X): xpt_free_path > (noperiph:xpt0:0:X:X): xpt_release_path 230a249,253 > da1 at vpo0 bus 0 target 6 lun 0 > da1: Removable Direct Access SCSI-2 device > da1: 96MB (196608 512 byte sectors: 64H 32S/T 96C) > Considering FFS root f/s. > changing root device to da0s1a Below is the complete boot -v output from a kernel with the CAMDEBUG options. Steinar Haug, Nethelp consulting, sthaug@nethelp.no ---------------------------------------------------------------------- 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 #2: Wed Dec 30 02:23:08 CET 1998 sthaug@overdi.nethelp.no:/local/freebsd/src/sys/compile/OVERDI Calibrating clock(s) ... TSC clock: 133278140 Hz, i8254 clock: 1193692 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 133221833 Hz CPU: Pentium/P54C (133.22-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52b Stepping=11 Features=0x1bf real memory = 67108864 (65536K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00270000 - 0x03ff7fff, 64520192 bytes (15752 pages) config> quit avail memory = 62771200 (61300K bytes) Found BIOS32 Service Directory header at 0xf00fb2e0 Entry = 0xfb790 (0xf00fb790) Rev = 0 Len = 1 PCI BIOS entry at 0xb7c0 Other BIOS signatures found: ACPI: 00000000 $PnP: 000fc040 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=122d8086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x122d, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x02 on pci0.0.0 CPU Inactivity timer: clocks Peer Concurrency: enabled CPU-to-PCI Write Bursting: enabled PCI Streaming: enabled Bus Concurrency: enabled Cache: 512K dual-bank pipelined-burst secondary; L1 enabled DRAM: no memory hole, 66 MHz refresh Read burst timing: x-2-2-2/x-3-3-3 Write burst timing: x-2-2-2 RAS-CAS delay: 3 clocks found-> vendor=0x8086, dev=0x122e, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x02 on pci0.7.0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: enabled Lower BIOS: enabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: IRQ10, B: IRQ11, C: disabled, D: IRQ9 MB0: IRQ15, MB1: IRQ7 found-> vendor=0x8086, dev=0x1230, revid=0x02 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 00003000, size 4 ide_pci0: rev 0x02 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: 00003002 intel_piix_status: secondary master/slave sample = 5, master/slave recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary master/slave sample = 5, master/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: 0000300a found-> vendor=0x1000, dev=0x0001, revid=0x02 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 00006000, size 8 map[1]: type 1, range 32, base f1100000, size 8 ncr0: rev 0x02 int a irq 10 on pci0.17.0 ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver found-> vendor=0x1011, dev=0x0009, revid=0x22 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 4, range 32, base 00006100, size 7 map[1]: type 1, range 32, base f1102000, size 7 de0: rev 0x22 int a irq 11 on pci0.18.0 de0: ACCTON EN1207 21140A [10-100Mb/s] pass 2.2 de0: address 00:00:e8:3a:b8:a9 bpf: de0 attached found-> vendor=0x1002, dev=0x4758, revid=0x03 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 1, range 32, base f0000000, size 24 vga0: rev 0x03 on pci0.19.0 found-> vendor=0x8086, dev=0x1229, revid=0x02 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 3, range 32, base f1101000, size 12 map[1]: type 4, range 32, base 00006200, size 5 map[2]: type 1, range 32, base f1000000, size 20 fxp0: rev 0x02 int a irq 9 on pci0.20.0 fxp0: Ethernet address 00:a0:c9:42:b7:5a bpf: fxp0 attached 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> ppc: parallel port found at 0x378 ppc0: SMC registers CR1=0xb6 CR4=0x1 EPP SPP ppc0 at 0x378 irq 7 on isa ppc0: SMC FDC37C665GT chipset (EPP/PS2/NIBBLE) in COMPATIBLE mode vpo0: on ppbus 0 vpo0: EPP 1.9 mode sio0: irq maps: 0x9 0x19 0x9 0x9 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 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 wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 4134MB (8467200 sectors), 8400 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 174428745 bytes/sec bzero() bandwidth = 87588683 bytes/sec imasks: bio c0084040, tty c003009a, net c0060a00 BIOS Geometries: 0:020efe3f 0..526=527 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. Intel Pentium detected, installing workaround for F00F bug bpf: tun0 attached bpf: ppp0 attached new masks: bio c0084040, tty c003009a, net c0070a9a bpf: lo0 attached Waiting 2 seconds for SCSI devices to settle ncr0: restart (scsi reset). (probe7:vpo0:0:6:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe7:vpo0:0:6:0): ILLEGAL REQUEST asc:24,0 (probe7:vpo0:0:6:0): Invalid field in CDB (noperiph:xpt0:0:X:X): xpt_compile_path (noperiph:xpt0:0:X:X): xpt_setup_ccb (noperiph:xpt0:0:X:X): xpt_action (noperiph:xpt0:0:X:X): xpt_free_path (noperiph:xpt0:0:X:X): xpt_release_path (noperiph:xpt0:0:X:X): xpt_compile_path (noperiph:xpt0:0:X:X): xpt_setup_ccb (noperiph:xpt0:0:X:X): xpt_action sa0 at ncr0 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: Serial Number sa0: 5.0MB/s transfers (5.0MHz, offset 8) (noperiph:xpt0:0:X:X): xpt_free_path (noperiph:xpt0:0:X:X): xpt_release_path (noperiph:xpt0:0:X:X): xpt_compile_path (noperiph:xpt0:0:X:X): xpt_setup_ccb (noperiph:xpt0:0:X:X): xpt_action pass0 at ncr0 bus 0 target 0 lun 0 pass0: Removable Sequential Access SCSI-2 device pass0: Serial Number pass0: 5.0MB/s transfers (5.0MHz, offset 8) pass1 at ncr0 bus 0 target 2 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number B3FS9312 pass1: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled pass2 at vpo0 bus 0 target 6 lun 0 pass2: Removable Direct Access SCSI-2 device (noperiph:xpt0:0:X:X): xpt_free_path (noperiph:xpt0:0:X:X): xpt_release_path da0 at ncr0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number B3FS9312 da0: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at vpo0 bus 0 target 6 lun 0 da1: Removable Direct Access SCSI-2 device da1: 96MB (196608 512 byte sectors: 64H 32S/T 96C) Considering FFS root f/s. changing root device to da0s1a da0s1: type 0xa5, start 63, end = 8466254, size 8466192 : OK ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 17:47:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12845 for freebsd-current-outgoing; Tue, 29 Dec 1998 17:47:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12840 for ; Tue, 29 Dec 1998 17:47:12 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id RAA21937; Tue, 29 Dec 1998 17:46:54 -0800 (PST) Date: Tue, 29 Dec 1998 17:46:53 -0800 (PST) From: "Steven P. Donegan" To: freebsd-current@FreeBSD.ORG Subject: NOW/MOSIX/Beowulf 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 a completely different subject :-) Given FreeBSD-current's performance, and SMP capabilities, has anyone addressed using FreeBSD in a Network-Of-Workstations/MOSIX/Beowulf style baby supercomputer? MOSIX (last time I checked) was BSDI only. Any thoughts? I'm looking at highly scalable email/ldap applications. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 17:57:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13910 for freebsd-current-outgoing; Tue, 29 Dec 1998 17:57:19 -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 RAA13899 for ; Tue, 29 Dec 1998 17:57:15 -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 RAA05633 for ; Tue, 29 Dec 1998 17:52:59 -0800 (PST) Date: Tue, 29 Dec 1998 17:52:58 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: Buildworld failure in -current aout-to-elf build. 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 OK, step 2 was to convert to elf. Close, but no banana. cc -O -pipe -I/usr/src/usr.sbin/i4b/isdnd/../isdnmonitor -I/usr/src/usr.sbin/i4b/isdnd/../isdntel -I/usr/obj/elf/usr/src/usr.sbin/i4b/isdnd -DDEBUG -DUSE_RTPRIO -DUSE_CURSES -DI4B_EXTERNAL_MONITOR -I/usr/obj/elf/usr/src/tmp/usr/include -o isdnd rc_parse.o rc_scan.o main.o rc_config.o log.o curses.o process.o rates.o msghdl.o fsm.o support.o timer.o exec.o dial.o monitor.o pcause.o controller.o alias.o -lcurses /usr/obj/aout/usr/src/tmp/usr/libexec/elf/ld: warning: libtermcap.so.2, needed by /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so, not found (try using --rpath) /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetnum' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgoto' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetflag' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tputs' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetent' /usr/obj/elf/usr/src/tmp/usr/lib/libcurses.so: undefined reference to `tgetstr' and so on, and so forth... What to do? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 18:33:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17156 for freebsd-current-outgoing; Tue, 29 Dec 1998 18:33:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17150 for ; Tue, 29 Dec 1998 18:33:16 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id NAA14245; Wed, 30 Dec 1998 13:02:38 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA21953; Wed, 30 Dec 1998 13:02:37 +1030 Date: Wed, 30 Dec 1998 13:02:37 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: =?X-UNKNOWN?Q?S=F8ren_Schmidt?= Cc: freebsd-current@FreeBSD.ORG Subject: Re: /dev/acd - anybody know how to use with CD-RW? In-Reply-To: <199812292203.XAA93597@freebsd.dk> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id SAA17152 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Dec 1998, Søren Schmidt wrote: > You can read CDDA disk with the acd driver, I have a patched cdd > that can do this on my ftp site: > > ftp://freebsd.dk/pub/ATAPI/cdd-* The source no longer compiles..I don't think it's been CAMified. It hangs off the now non-existant scsi.h and didnt seem completely trivial to patch. Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 18:35:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA17492 for freebsd-current-outgoing; Tue, 29 Dec 1998 18:35:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA17487 for ; Tue, 29 Dec 1998 18:35:51 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id TAA29911; Tue, 29 Dec 1998 19:39:34 -0700 (MST) Message-Id: <199812300239.TAA29911@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: "Steven P. Donegan" cc: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-reply-to: Your message of "Tue, 29 Dec 1998 17:46:53 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Dec 1998 19:39:34 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > On a completely different subject :-) > > Given FreeBSD-current's performance, and SMP capabilities, has anyone > addressed using FreeBSD in a Network-Of-Workstations/MOSIX/Beowulf style > baby supercomputer? MOSIX (last time I checked) was BSDI only. Any > thoughts? I'm looking at highly scalable email/ldap applications. checkout: http://www.sarnoff.com:8000/docs/metacomputing.html I've been thinking that modifying our make to be "cluster aware" would be a useful project. Put 2 or 3 dual SMP machines together with an NFS mounted /usr/src & /usr/obj and we might aproach 10 minute buildworlds... -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 18:45:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18074 for freebsd-current-outgoing; Tue, 29 Dec 1998 18:45:48 -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 SAA18057 for ; Tue, 29 Dec 1998 18:45:09 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.1/8.9.1) with ESMTP id SAA08576; Tue, 29 Dec 1998 18:44:37 -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 SAA13476; Tue, 29 Dec 1998 18:44:36 -0800 (PST) (envelope-from jdp@polstra.com) Date: Tue, 29 Dec 1998 18:44:36 -0800 (PST) Message-Id: <199812300244.SAA13476@vashon.polstra.com> To: donegan@quick.net Subject: Re: CVS issues Newsgroups: polstra.freebsd.current In-Reply-To: Organization: Polstra & Co., Seattle, WA Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Steven P. Donegan wrote: > > This is not a complex problem. If mirror sites are not true mirrors then > don't put them in the round robbin. There are only 3 US mirrors, so a round robin would be kind of silly without all of them. (Note, I am not going to round robin the non-US mirrors at this time.) Therefore I need to make them carry exactly the same collections, or at least document the variances. No, it's not a complex problem. But I've got a backlog of more important problems to deal with first. Sorry, that's just life. 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 Tue Dec 29 18:46:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18182 for freebsd-current-outgoing; Tue, 29 Dec 1998 18:46:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18174 for ; Tue, 29 Dec 1998 18:46:45 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id SAA22033; Tue, 29 Dec 1998 18:46:01 -0800 (PST) Date: Tue, 29 Dec 1998 18:46:01 -0800 (PST) From: "Steven P. Donegan" To: Steve Passe cc: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-Reply-To: <199812300239.TAA29911@Ilsa.StevesCafe.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, 29 Dec 1998, Steve Passe wrote: > Hi, > > > On a completely different subject :-) > > > > Given FreeBSD-current's performance, and SMP capabilities, has anyone > > addressed using FreeBSD in a Network-Of-Workstations/MOSIX/Beowulf style > > baby supercomputer? MOSIX (last time I checked) was BSDI only. Any > > thoughts? I'm looking at highly scalable email/ldap applications. > > checkout: > http://www.sarnoff.com:8000/docs/metacomputing.html > Will do... > I've been thinking that modifying our make to be "cluster aware" > would be a useful project. Put 2 or 3 dual SMP machines together > with an NFS mounted /usr/src & /usr/obj and we might aproach 10 > minute buildworlds... > Here's the beef :-) 1) SMP base 2) NOW aware (MOSIX migration under load model is good) 3) The network is king - so Cisco or Beowulf style etherchannel or gigabit or gigabit etherchannel is good. 4) Network switching fabric - HP and Cisco both support etherchannel - 400 megabits full duplex is a decent backbone :-) 4 gigs in Cisco only environs but I doubt any PCI card can do much with that :-) 5) Storage - Network Appliances support gig ethernet - and can actually serve that bandwidth :-) I'm just a power monger with a commercial application, and a home overkill desire :-) Cheers... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 18:52:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18621 for freebsd-current-outgoing; Tue, 29 Dec 1998 18:52:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18613 for ; Tue, 29 Dec 1998 18:52:09 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA04852; Tue, 29 Dec 1998 21:51:31 -0500 (EST) Date: Tue, 29 Dec 1998 21:51:30 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: John Polstra cc: Greg Lehey , forrie@navinet.net, current@FreeBSD.ORG, Bill Fumerola Subject: Re: CVS issues In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Dec 1998, John Polstra wrote: > On 30-Dec-98 Greg Lehey wrote: > > > > I've tended to use cvsup.FreeBSD.org because I assume that commits get > > there faster. How much lag is there on the other sites? > > Ah, I'm glad you spoke up. I didn't realize that people had that > idea. Actually, practically all of the mirror sites update themselves > hourly directly from freefall. In particular, cvsup{,2,3}.freebsd.org > do that. So they're completely equivalent in terms of lag time. The > maximum is 1 hour, and the average is 30 minutes. Thanks for telling me this, I thought so too! > > Note, cvsup.freebsd.org != freefall. It suffers the same lag as the > other mirrors. > > 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 > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 29 19:24:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21184 for freebsd-current-outgoing; Tue, 29 Dec 1998 19:24:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21177 for ; Tue, 29 Dec 1998 19:24:47 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id XAA00671 for ; Tue, 29 Dec 1998 23:24:28 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 29 Dec 1998 23:24:28 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG Subject: hang 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 Altho its only been up a few minutes, we think we *might* have found it... We had 2x2940UW SCSI controllers, 1x3Com PCI ethernet and 1xSMC ISA...we booted it up with a video card and went into the BIOS, to check voltages...all of them reported 'zero'...removed the ISA card, all of them reported what we considered more normal values (ie. non-zero)... Again, we just brought things back up again, so this could just be wishful thinking on our part, so we'll see what happens over the next little while... Now, we had that same combination on the old motherboard, no problems...just curious as to whether anyone has experienced similar problems with ISA cards and the voltages problem we saw? Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 19:43:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22781 for freebsd-current-outgoing; Tue, 29 Dec 1998 19:43:47 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [156.46.203.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22762; Tue, 29 Dec 1998 19:43:43 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [156.46.203.13]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id VAA27851; Tue, 29 Dec 1998 21:43:23 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <001601be33a6$8da151e0$0dcb2e9c@westbend.net> From: "Scot W. Hetzel" To: "FreeBSD-Ports" , Cc: "FreeBSD-Current" , "FreeBSD-Stable" Subject: Fw: apache_fp-1.3.3 Date: Tue, 29 Dec 1998 21:43:23 -0600 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0013_01BE3374.42250D60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.1012.1001 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.1012.1001 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0013_01BE3374.42250D60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Since creating the Apache-FP port, I have received a few requests on how to install the libdescrypt library, and where it is located. I usually advise them to use either cvsup (w/src-crypto & src-secure in cvsupfile) and a make world to install it, or to use the pre-compiled binary for their release (-CURRENT, -STABLE, -SNAP or -RELEASE). Should the attached patches for des/install.sh be added so that the they can choose if kerberos is to be installed? The DES section of the Handbook doesn't mention how to install this library or where to obtain it (US/CA, International). The following information needs to be added to the FreeBSD Handbook possibly in a new section (i.e. 6.1.2 How to install the DES library) and written a little better. Scot From: Scot W. Hetzel > > Frontpage requires libdescrypt (as an .so?). I've scoured the web and > > can't find it. Any suggestions? > > > > jim... > > > You need to install the descrypt library from the FreeBSD sources. You can > do this 2 ways: > > 1. update yours sources via cvsup making sure to include src-crypto and > src-secure in your cvsup file. And selecting the appropriate cvsup server > (US/CA - cvsup.freebsd.org, International - cvsup.internat.freebsd.org). And > perform a buildworld. > > 2. use ftp to retrieve the compiled binaries > (US/CA - ftp://ftp.freebsd.org/pub/FreeBSD//des , > International - ftp://ftp.internat.freebsd.org/pub/FreeBSD//des). > You'll need to retrieve a minimum of install.sh, des.*, and optionally the source > (ssecure.* scrypto.*). Then you need to edit the install.sh script to > remove any lines containing krb.* and skerbero.*. Theses lines are used to > install the kerberos support and is not needed to compile Apache-FP. > > Then you need to check that libcrypt* is a link to libdescrypt* in /usr/lib. > If it is pointing to the wrong library you need to remove all libcrypt* > links and recreate them so that they are pointing to the libdescrypt* > libraries. > > The reason Apache_FP requires the descrypt library is because the pre-built > binary fpadmsrv.exe was compiled statically with the DES library. When it > creates the passwords for the user, author, or administrator web users, it > encrypts it using DES. When the Apache server then tries to use the > password, it rejects the user. > > Scot > > ------=_NextPart_000_0013_01BE3374.42250D60 Content-Type: application/octet-stream; name="30.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="30.diff" --- des/install.sh.orig Tue Dec 29 20:41:21 1998=0A= +++ des/install.sh Tue Dec 29 20:45:22 1998=0A= @@ -10,12 +10,22 @@=0A= echo -n "otherwise hit return to continue. "=0A= read junk=0A= cat des.?? | tar --unlink -xpzf - -C ${_DEST}=0A= -cat krb.?? | tar --unlink -xpzf - -C ${_DEST}=0A= +echo -n "Do you want to install support for Kerbero (y/n)? "=0A= +read ans1=0A= +if [ "$ans" =3D "y" ]; then=0A= + cat krb.?? | tar --unlink -xpzf - -C ${_DEST}=0A= +fi=0A= echo -n "Do you want to install the DES sources (y/n)? "=0A= read ans=0A= if [ "$ans" =3D "y" ]; then=0A= cat scrypto.?? | tar --unlink -xpzf - -C ${_DEST}/usr/src=0A= - cat skerbero.?? | tar --unlink -xpzf - -C ${_DEST}/usr/src=0A= cat ssecure.?? | tar --unlink -xpzf - -C ${_DEST}/usr/src=0A= +fi=0A= +if [ "$ans1" =3D "y" ]; then=0A= + echo -n "Do you want to install the Kerbero sources (y/n)? "=0A= + read ans2=0A= + if [ "$ans2" =3D "y" ]; then=0A= + cat skerbero.?? | tar --unlink -xpzf - -C ${_DEST}/usr/src=0A= + fi=0A= fi=0A= exit 0=0A= ------=_NextPart_000_0013_01BE3374.42250D60 Content-Type: application/octet-stream; name="228.diff" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="228.diff" --- des/install.sh.orig Tue Dec 29 20:31:00 1998=0A= +++ des/install.sh Tue Dec 29 20:38:10 1998=0A= @@ -8,12 +8,22 @@=0A= echo "you want to do this over your installed system? If not, hit ^C = now!"=0A= read junk=0A= cat des.?? | tar --unlink -xpzf - -C /=0A= -cat krb.?? | tar --unlink -xpzf - -C /=0A= +echo -n "Do you want to install support for Kerbero (y/n)? "=0A= +read ans1=0A= +if [ "$ans" =3D "y" ]; then=0A= + cat krb.?? | tar --unlink -xpzf - -C /=0A= +fi=0A= echo -n "Do you want to install the DES sources (y/n)? "=0A= read ans=0A= if [ "$ans" =3D "y" ]; then=0A= cat scrypto.?? | tar --unlink -xpzf - -C /usr/src=0A= - cat skerbero.?? | tar --unlink -xpzf - -C /usr/src=0A= cat ssecure.?? | tar --unlink -xpzf - -C /usr/src=0A= +fi=0A= +if [ "$ans1" =3D "y" ]; then=0A= + echo -n "Do you want to install the Kerbero sources (y/n)? "=0A= + read ans2=0A= + if [ "$ans2" =3D "y" ]; then=0A= + cat skerbero.?? | tar --unlink -xpzf - -C /usr/src=0A= + fi=0A= fi=0A= exit 0=0A= ------=_NextPart_000_0013_01BE3374.42250D60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 20:13:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA26397 for freebsd-current-outgoing; Tue, 29 Dec 1998 20:13:11 -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 UAA26392 for ; Tue, 29 Dec 1998 20:13:10 -0800 (PST) (envelope-from obrien@nuxi.ucdavis.edu) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id UAA21770 for freebsd-current@FreeBSD.ORG; Tue, 29 Dec 1998 20:12:52 -0800 (PST) (envelope-from obrien) Message-ID: <19981229201252.C6713@nuxi.com> Date: Tue, 29 Dec 1998 20:12:52 -0800 From: "David O'Brien" To: freebsd-current@FreeBSD.ORG Subject: Re: CVS issues Reply-To: obrien@nuxi.ucdavis.edu References: <4.1.19981229113057.0098e590@206.25.93.69> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chuck Robey on Tue, Dec 29, 1998 at 08:10:30PM -0500 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 > Maybe folks ought to do as suggested, and use cvsup2.freebsd.org ... Those at universities should traceroute to cvsup3 (xyz.lcs.mit.edu) and compare the route with other CVSup servers. If your Univ. has connected to VBNS.net you may be surprised how short the hop count is, and how much unused bandwidth there is. 9!! hops from my my lab in California to this server in Massachusetts. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 20:50:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29817 for freebsd-current-outgoing; Tue, 29 Dec 1998 20:50:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA29748 for ; Tue, 29 Dec 1998 20:50:00 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id XAA06549; Tue, 29 Dec 1998 23:49:37 -0500 (EST) Message-ID: <19981229234937.N477@ns1.adsu.bellsouth.com> Date: Tue, 29 Dec 1998 23:49:37 -0500 From: Christian Kuhtz To: "Steven P. Donegan" , Steve Passe Cc: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: <199812300239.TAA29911@Ilsa.StevesCafe.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Steven P. Donegan on Tue, Dec 29, 1998 at 06:46:01PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > 1) SMP base Actually, it wouldn't really matter whether the node is SMP or not. You're talking about building a distributed memory multiprocessor and a design goal for the cluster should be that it is irrelevant whether SMP is there or not. Make it machine architecture independant. Who knows, maybe somebody will port FreeBSD to a distributed memory multiprocessor and then what? > 2) NOW aware (MOSIX migration under load model is good) Hmm. Yeah, certainly would be nice. > 3) The network is king - so Cisco or Beowulf style etherchannel or > gigabit or gigabit etherchannel is good. .. do we have GE supported cards in the code base today? > 4) Network switching fabric - HP and Cisco both support etherchannel - > 400 megabits full duplex is a decent backbone :-) 4 gigs in Cisco only > environs but I doubt any PCI card can do much with that :-) Why bother doing EtherChannel? You need special PCI cards and all that. It would make much more sense to use GE. Money no object, Catalyst 550x's work great. We got the GE stuff in the lab. You also need to think about what your overall node architecture looks like. Do you want to build a hypercube perhaps? An any to any matrix over an Ethernet fabric? > 5) Storage - Network Appliances support gig ethernet - and can actually > serve that bandwidth :-) Why not use FreeBSD as a storage subsystem? NetApps aren't exactly cheap. A real supercomputer wannabe needs an HMS, too. And another item to your list should be 6) APIs What good is this if you can't write to it? PVM comes to mind (or its successor), and MPI. I think I (and many others) would be happy if they had a system similiar to an RS/6000 SP2, which is essentially the same as what you're talking about. And I don't need the OS to do thread migration (which particularly in a distributed memory model is expensive). It depends very much on what you want this box to do. Most supercomputer architectures (and clusters) are designed for particular application characteristics. You need to think about your scope. Are you trying to solve the avid hacker's cluster dream with a hodge podge array of machinery or are you building a cluster consisting of n # of nodes doing parallel processing, which each node being pretty much a standard config.. Trying to be the be all end all usually isn't a good idea for massively parallel situations. My $.02, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 20:56:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA00515 for freebsd-current-outgoing; Tue, 29 Dec 1998 20:56:43 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from opi.flirtbox.ch ([62.48.0.50]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA00510 for ; Tue, 29 Dec 1998 20:56:41 -0800 (PST) (envelope-from oppermann@pipeline.ch) Received: (qmail 4645 invoked from network); 30 Dec 1998 04:56:21 -0000 Received: from unknown (HELO pipeline.ch) (4.13.175.193) by opi.flirtbox.ch with SMTP; 30 Dec 1998 04:56:21 -0000 Message-ID: <3689B28A.E73F3B5E@pipeline.ch> Date: Wed, 30 Dec 1998 05:56:42 +0100 From: Andre Oppermann Organization: Internet Business Solutions Ltd. X-Mailer: Mozilla 4.07 [en] (Win98; U) MIME-Version: 1.0 To: "Steven P. Donegan" CC: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steven P. Donegan wrote: > > On a completely different subject :-) > > Given FreeBSD-current's performance, and SMP capabilities, has anyone > addressed using FreeBSD in a Network-Of-Workstations/MOSIX/Beowulf style > baby supercomputer? MOSIX (last time I checked) was BSDI only. Any > thoughts? I'm looking at highly scalable email/ldap applications. Check out our work: http://www.nrg4u.com It's an LDAP enabling Qmail patch and qmail in itself is highly scalable. A new patch release is on the way. -- Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 21:27:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02779 for freebsd-current-outgoing; Tue, 29 Dec 1998 21:27:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02771 for ; Tue, 29 Dec 1998 21:27:44 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id BAA01530; Wed, 30 Dec 1998 01:27:13 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 30 Dec 1998 01:27:13 -0400 (AST) From: The Hermit Hacker To: Andre Oppermann cc: "Steven P. Donegan" , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-Reply-To: <3689B28A.E73F3B5E@pipeline.ch> 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, 30 Dec 1998, Andre Oppermann wrote: > Steven P. Donegan wrote: > > > > On a completely different subject :-) > > > > Given FreeBSD-current's performance, and SMP capabilities, has anyone > > addressed using FreeBSD in a Network-Of-Workstations/MOSIX/Beowulf style > > baby supercomputer? MOSIX (last time I checked) was BSDI only. Any > > thoughts? I'm looking at highly scalable email/ldap applications. > > Check out our work: http://www.nrg4u.com > > It's an LDAP enabling Qmail patch and qmail in itself is highly > scalable. A new patch release is on the way. Okay, I'll bite...*what* does this have to do with the question posed? Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 22:31:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09357 for freebsd-current-outgoing; Tue, 29 Dec 1998 22:31:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail1.twcny.rr.com (mail1-0.twcny.rr.com [24.92.226.74]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA09350 for ; Tue, 29 Dec 1998 22:31:31 -0800 (PST) (envelope-from klmac@twcny.rr.com) Received: from [192.168.0.2] ([24.92.243.29]) by mail1.twcny.rr.com (Post.Office MTA v3.5.2 release 221 ID# 0-53939U80000L80000S0V35) with ESMTP id com for ; Wed, 30 Dec 1998 01:28:09 -0500 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Sender: klmac@pop-server Message-Id: Date: Wed, 30 Dec 1998 01:31:17 -0500 To: freebsd-current@FreeBSD.ORG From: Ken McKittrick Subject: How do you actually use vinum? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello How do you mount a volume created with vinum? I have rtfm'd the man pages several times and am at a loss. 1. modload /lkm/vinum_mod.o 2. vinum create /etc/rc.vinum what's next to actualy mount the volume as /www? Sincerely Ken Here are the details This is a 3.0-19981225-SNAP system with 2 IDE drives /dev/wd0 and /dev/wd2. These are 2 Maxtor 8.4 gig EIDE drives. /etc/rc.vinum # drives drive drive1 device /dev/wd0c drive drive2 device /dev/wd2c # volumes volume bigvol plex org striped 512b sd length 8000m drive drive1 sd length 8000m drive drive2 running vinum create /etc/rc.vinum gives me this: Configuration summary Drives: 2 (4 configured) Volumes: 1 (4 configured) Plexes: 1 (8 configured) Subdisks: 2 (16 configured) D drive1 State: up Device /dev/wd0c D drive2 State: up Device /dev/wd2c V bigvol State: up Plexes: 1 Size: 15 GB P bigvol.p0 S State: up Subdisks: 2 Size: 15 GB S bigvol.p0.s0 State: up PO: 0 B Size: 8000 MB S bigvol.p0.s1 State: up PO: 8000 MB Size: 8000 MB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 22:38:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09863 for freebsd-current-outgoing; Tue, 29 Dec 1998 22:38:34 -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 WAA09847 for ; Tue, 29 Dec 1998 22:38:29 -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 RAA07532; Wed, 30 Dec 1998 17:07:43 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id RAA36219; Wed, 30 Dec 1998 17:07:46 +1030 (CST) Message-ID: <19981230170746.O32696@freebie.lemis.com> Date: Wed, 30 Dec 1998 17:07:46 +1030 From: Greg Lehey To: Ken McKittrick , freebsd-current@FreeBSD.ORG Subject: Re: How do you actually use vinum? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Ken McKittrick on Wed, Dec 30, 1998 at 01:31:17AM -0500 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 On Wednesday, 30 December 1998 at 1:31:17 -0500, Ken McKittrick wrote: > Hello > > How do you mount a volume created with vinum? I have rtfm'd the man pages > several times and am at a loss. > > 1. modload /lkm/vinum_mod.o > 2. vinum create /etc/rc.vinum > what's next to actualy mount the volume as /www? 3. newfs -v /dev/vinum/rbigvol 4. mount /dev/vinum/bigvol /www > Here are the details > > This is a 3.0-19981225-SNAP system with 2 IDE drives /dev/wd0 and > /dev/wd2. These are 2 Maxtor 8.4 gig EIDE drives. > > /etc/rc.vinum > > # drives > drive drive1 device /dev/wd0c > drive drive2 device /dev/wd2c > # volumes > volume bigvol > plex org striped 512b > sd length 8000m drive drive1 > sd length 8000m drive drive2 > > running vinum create /etc/rc.vinum gives me this: > > Configuration summary > > Drives: 2 (4 configured) > Volumes: 1 (4 configured) > Plexes: 1 (8 configured) > Subdisks: 2 (16 configured) > > D drive1 State: up Device /dev/wd0c > D drive2 State: up Device /dev/wd2c > > V bigvol State: up Plexes: 1 Size: 15 GB > > P bigvol.p0 S State: up Subdisks: 2 Size: 15 GB > > S bigvol.p0.s0 State: up PO: 0 B Size: 8000 MB > S bigvol.p0.s1 State: up PO: 8000 MB Size: 8000 MB What are you using for your system disk? Vinum doesn't care if you use /dev/wd0c and /dev/wd2c for its drives, but if your file systems are also on this area, you're going to crash most horribly when you start. In general, it's not a good idea to use the c partition for vinum. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 22:38:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA09883 for freebsd-current-outgoing; Tue, 29 Dec 1998 22:38:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hyperreal.org (taz.hyperreal.org [209.133.83.16]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA09877 for ; Tue, 29 Dec 1998 22:38:35 -0800 (PST) (envelope-from brian@hyperreal.org) Received: (qmail 24750 invoked by uid 24); 30 Dec 1998 06:38:17 -0000 Message-Id: <4.1.19981229222419.03d929f0@hyperreal.org> X-Sender: brian@hyperreal.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 29 Dec 1998 22:26:28 -0800 To: The Hermit Hacker From: Brian Behlendorf Subject: Re: NOW/MOSIX/Beowulf Cc: freebsd-current@FreeBSD.ORG In-Reply-To: References: <3689B28A.E73F3B5E@pipeline.ch> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 01:27 AM 12/30/98 -0400, The Hermit Hacker wrote: >On Wed, 30 Dec 1998, Andre Oppermann wrote: > >> Steven P. Donegan wrote: >> > >> > On a completely different subject :-) >> > >> > Given FreeBSD-current's performance, and SMP capabilities, has anyone >> > addressed using FreeBSD in a Network-Of-Workstations/MOSIX/Beowulf style >> > baby supercomputer? MOSIX (last time I checked) was BSDI only. Any >> > thoughts? I'm looking at highly scalable email/ldap applications. >> >> Check out our work: http://www.nrg4u.com >> >> It's an LDAP enabling Qmail patch and qmail in itself is highly >> scalable. A new patch release is on the way. > >Okay, I'll bite...*what* does this have to do with the question posed? "highly scalable email/ldap applications" wasn't part of the question, granted, but it was his end goal... Brian --=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-- History is made at night; brian@hyperreal.org character is what you are in the dark. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 23:42:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15306 for freebsd-current-outgoing; Tue, 29 Dec 1998 23:42:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtpott1.nortel.ca (smtpott1.nortel.ca [192.58.194.78]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15301 for ; Tue, 29 Dec 1998 23:42:48 -0800 (PST) (envelope-from Andrew.Atrens.atrens@nortelnetworks.com) Received: from zcars01t by smtpott1; Wed, 30 Dec 1998 02:42:13 -0500 Received: from wmerh01z.ca.nortel.com by zcars01t; Wed, 30 Dec 1998 02:41:36 -0500 Received: from hcarp00g.ca.nortel.com (atrens@hcarp00g.ca.nortel.com@wmerh01z) by wmerh01z.ca.nortel.com with ESMTP (8.7.1/8.7.1) id CAA05539; Wed, 30 Dec 1998 02:41:35 -0500 (EST) Date: Wed, 30 Dec 1998 02:50:16 -0500 (EST) From: "Andrew Atrens" Reply-To: "Andrew Atrens" To: Poul-Henning Kamp cc: current@FreeBSD.ORG Subject: X-ten In-Reply-To: <68199.914779200@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 27 Dec 1998, Poul-Henning Kamp wrote: > Further hitlist candidates are: > > X-ten Please record my vote for keeping x-ten _functionality_. It's probably a good candidate to be kld-omized, but in the meantime works just fine as is. The TW-523 device that this driver talks to is central to many home automation projects and is sold today as it was when the driver was written. As far as `maintenance' is concerned, is it spelled out anywhere exactly what this entails - kind of a roles and responsibilities thing? If no one else is willing to ( are you listening Gene? ) then I'm willing to look after this baby provided you have reasonable r&r's. Cheers, Andrew. +----------------------------------------------------+ = Andrew Atrens - Nortel Networks (atrens@nortel.ca) = = P.O. Box 3511, Station C Ottawa, Canada = = = = All opinions expressed are mine, not Nortel's. = +----------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Tue Dec 29 23:54:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16503 for freebsd-current-outgoing; Tue, 29 Dec 1998 23:54:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bandicoot.prth.tensor.pgs.com (bandicoot.prth.tensor.pgs.com [157.147.224.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16495 for ; Tue, 29 Dec 1998 23:54:41 -0800 (PST) (envelope-from shocking@bandicoot.prth.tensor.pgs.com) Received: from ariadne.tensor.pgs.com (ariadne [157.147.227.36]) by bandicoot.prth.tensor.pgs.com (8.8.8/8.8.8) with SMTP id PAA21405 for ; Wed, 30 Dec 1998 15:54:16 +0800 (WST) Received: by ariadne.tensor.pgs.com (SMI-8.6/SMI-SVR4) id PAA11978; Wed, 30 Dec 1998 15:54:15 +0800 Date: Wed, 30 Dec 1998 15:54:15 +0800 From: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) Message-Id: <199812300754.PAA11978@ariadne.tensor.pgs.com> To: current@FreeBSD.ORG Subject: Oi! When's the Voxware stuff coming back into current? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This peasant is getting restless...... Stephen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 00:01:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17129 for freebsd-current-outgoing; Wed, 30 Dec 1998 00:01: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 AAA17116 for ; Wed, 30 Dec 1998 00:01:42 -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 DAA16091; Wed, 30 Dec 1998 03:01:13 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Jaye Mathisen cc: freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: CVS issues In-reply-to: Your message of "Tue, 29 Dec 1998 17:26:22 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 03:01:13 -0500 Message-ID: <16087.915004873@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaye Mathisen wrote in message ID : > > Nah, need to get some layer 4 switches running, and a FreeBSD cvsup farm > going... I think a distributed-director type setup would work much better. Having L4 switches implies that all your servers are in one facility. That implies the network problems such as wcarchive experiences with lack of peering (or simply the peering pipes are too small). Having distributed servers is *much* preferable, even from a redundancy standpoint if nothing else. 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 Wed Dec 30 00:04:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA17435 for freebsd-current-outgoing; Wed, 30 Dec 1998 00:04:22 -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 AAA17430 for ; Wed, 30 Dec 1998 00:04:19 -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 DAA16118; Wed, 30 Dec 1998 03:03:44 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: John Polstra cc: donegan@quick.net, current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: CVS issues In-reply-to: Your message of "Tue, 29 Dec 1998 18:44:36 PST." <199812300244.SAA13476@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 03:03:44 -0500 Message-ID: <16114.915005024@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra wrote in message ID <199812300244.SAA13476@vashon.polstra.com>: > There are only 3 US mirrors cvsup4 seems to exist.... 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 Wed Dec 30 00:11:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA18481 for freebsd-current-outgoing; Wed, 30 Dec 1998 00:11:59 -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 AAA18466 for ; Wed, 30 Dec 1998 00:11:56 -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 DAA16302; Wed, 30 Dec 1998 03:11:29 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: Brian Behlendorf cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: NOW/MOSIX/Beowulf In-reply-to: Your message of "Tue, 29 Dec 1998 22:26:28 PST." <4.1.19981229222419.03d929f0@hyperreal.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 03:11:29 -0500 Message-ID: <16298.915005489@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "highly scalable email/ldap applications" wasn't part of the question, > granted, but it was his end goal... Two comments: I dont count `LDAP' as a highly-scalable service. Sure, it is one that is very supportive of horizontal scaling (throwing more servers at it), but from all the indications I've seen/heard its a lot more resource intensive than it needs to be, and likely will not be deployed large scale where I work for that very reason (we'll grow a distributed password system inhouse) Second is that while qmail has a lot of supporters, there are faster solutions out there ... PostFix comes to mind. 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 Wed Dec 30 01:20:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23049 for freebsd-current-outgoing; Wed, 30 Dec 1998 01:20:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-41-dbn.dial-up.net [196.34.155.105]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA23012; Wed, 30 Dec 1998 01:20:14 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id LAA10457; Wed, 30 Dec 1998 11:19:11 +0200 (SAT) From: Robert Nordier Message-Id: <199812300919.LAA10457@ceia.nordier.com> Subject: Re: New boot2 able to boot old -stable from 2nd BSD partition? In-Reply-To: <199812281943.UAA27627@semyam.dinoco.de> from Stefan Eggers at "Dec 28, 98 08:43:22 pm" To: seggers@semyam.dinoco.de (Stefan Eggers) Date: Wed, 30 Dec 1998 11:19:09 +0200 (SAT) Cc: freebsd-current@FreeBSD.ORG, rnordier@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 Stefan Eggers wrote: > I'd like to use the new boot2 to boot a -stable kernel from the > *second* FreeBSD partition. If need be I will modify it to grab the > second (active) one instead of the first but what I saw today looks > like it can do that already. (*) Yes, the new boot2 will prefer an active FreeBSD slice over the first FreeBSD slice. You can also specify the slice, eg. "da(0,2,a)", either at the "boot:" prompt or in /boot.config. > (*) In case it is already able to do the right thing we should modify > boot(8) as soon as we use the new boot blocks as default as that man > page says it will boot from the first one only. The new boot blocks are already the default in -current. Though you're right, the man page does need revision. -- 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 30 01:24:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA23482 for freebsd-current-outgoing; Wed, 30 Dec 1998 01:24:43 -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 BAA23477 for ; Wed, 30 Dec 1998 01:24:41 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id JAA27763; Wed, 30 Dec 1998 09:24:29 GMT Date: Wed, 30 Dec 1998 09:24:28 +0000 (GMT) From: Doug Rabson To: Brian Behlendorf cc: "Jordan K. Hubbard" , FreeBSD current users Subject: Re: How do I build an a.out kld? In-Reply-To: <4.1.19981229140706.048df410@hyperreal.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 29 Dec 1998, Brian Behlendorf wrote: > At 12:46 PM 12/29/98 -0800, Jordan K. Hubbard wrote: > >> I just upgraded to an ELF kernel, updated the boot blocks, and everything > >> boots up great, except the new boot loader appears to be looking for a > >> /boot/boot.conf (fails, then waits for 8 seconds, then boots /kernel). I > >> noticed I have a zero-length /boot.config file - should I move that to > >> /boot/boot.conf? > > > >Yeah, /boot.config is basically obsolete though it can still be used > >for its old purpose, I in fact still use it to set my rootdev since I > >haven't grok'd how to do that yet with the new scheme. > > > >/boot/boot.conf is supposed to contain any boot commands you'd like to > >have run (boot.conf is actually a bad name, now that I think about it, > >since it implies configuration variables rather than actions - boot.rc > >would have been better, oh well!). > > So would a blank file tell it to boot the default immediately, or should I > put "boot /kernel" in there? It's not that I really NEED those 8 seconds, > it just seems like it'd be cleaner to boot directly. If /boot/boot.conf doesn't exist, it defaults to running the autoboot command (which waits as you have seen). You can put autoboot in your config file with a different timeout. If you use 'boot', there is no possibility of selecting a different kernel for disaster recovery. -- 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 Wed Dec 30 02:42:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA29894 for freebsd-current-outgoing; Wed, 30 Dec 1998 02:42:54 -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 ESMTP id CAA29874; Wed, 30 Dec 1998 02:42:29 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id LAA02191; Wed, 30 Dec 1998 11:41:11 +0100 (MET) Message-ID: <368A0347.CA79A1BD@we.lc.ehu.es> Date: Wed, 30 Dec 1998 11:41:11 +0100 From: "José Mª Alcaide" Organization: Universidad del País Vasco - Dept. de Electricidad y Electrónica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: sthaug@nethelp.no CC: nsouch@teaser.fr, freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] References: <26784.914978880@verdi.nethelp.no> <27331.914982190@verdi.nethelp.no> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG sthaug@nethelp.no wrote: > > A followup: There is probably a timing-related issue here. If I remove > the various CAMDEBUG options, the Zip drive isn't detected. With the > CAMDEBUG options (and thus lots of extra printout), it is detected. > Verbose boot or not makes no difference. > YES!!!!! I have added the CAM_DEBUG options, and now the da0 is initialized. Now I have: - parallel port in EPP mode in the BIOS. - ppc flags 0x7 (NIBBLE/PS2/EPP) - CAM_DEBUG options ... and it does work! I also think that there is a timing problem, so I did a little test: I removed the CAM_DEBUG options and added the SCSI_DELAY one. I was expecting that the delay introduced by this option might have the same effect that CAM_DEBUG. However, when I rebooted the new kernel I saw that there was not any delay after the "Waiting 5 seconds for SCSI devices to settle" message (and the da0 device was not initialized). Why? -- 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 30 03:36:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA03891 for freebsd-current-outgoing; Wed, 30 Dec 1998 03:36:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from freebsd.dk (sos.freebsd.dk [212.242.42.180]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03860 for ; Wed, 30 Dec 1998 03:35:59 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.1/8.9.1) id MAA95546; Wed, 30 Dec 1998 12:35:29 +0100 (CET) (envelope-from sos) From: Søren Schmidt Message-Id: <199812301135.MAA95546@freebsd.dk> Subject: Re: /dev/acd - anybody know how to use with CD-RW? In-Reply-To: from Kris Kennaway at "Dec 30, 1998 1: 2:37 pm" To: kkennawa@physics.adelaide.edu.au (Kris Kennaway) Date: Wed, 30 Dec 1998 12:35:29 +0100 (CET) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kris Kennaway wrote: >> You can read CDDA disk with the acd driver, I have a patched cdd >> that can do this on my ftp site: >> >> ftp://freebsd.dk/pub/ATAPI/cdd-* > >The source no longer compiles..I don't think it's been CAMified.o Use the bin then for now... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Søren Schmidt (sos@freebsd.org) FreeBSD Core Team member To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 03:38:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04335 for freebsd-current-outgoing; Wed, 30 Dec 1998 03:38:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04327 for ; Wed, 30 Dec 1998 03:38:47 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id UAA26486; Wed, 30 Dec 1998 20:38:22 +0900 (JST) Message-ID: <368A0FE6.55408324@newsguy.com> Date: Wed, 30 Dec 1998 20:35:02 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: Buildworld failure in -current aout-to-elf build. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jaye Mathisen wrote: > > OK, step 2 was to convert to elf. Close, but no banana. Most likely, it is a trade issue with EU... :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 03:42:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA04551 for freebsd-current-outgoing; Wed, 30 Dec 1998 03:42:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA04546 for ; Wed, 30 Dec 1998 03:42:42 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id MAA30832; Wed, 30 Dec 1998 12:42:01 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id LAA00325; Wed, 30 Dec 1998 11:59:33 GMT (envelope-from son) Message-ID: <19981230115932.64403@breizh.prism.uvsq.fr> Date: Wed, 30 Dec 1998 11:59:32 +0000 From: Nicolas Souchu To: =?iso-8859-1?Q?Jos=E9_M=AA_Alcaide?= Cc: freebsd-current@FreeBSD.ORG, "Justin T. Gibbs" Subject: Re: Request fo help with Zip Drive on vpo0 in -current] References: <19981219130349.11043.qmail@www0f.netaddress.usa.net> <367E88FB.B9F0D79@we.lc.ehu.es> <19981222010450.23781@breizh.prism.uvsq.fr> <368171FF.B8A5B268@we.lc.ehu.es> <19981224181948.61645@breizh.prism.uvsq.fr> <368761EF.23641D79@we.lc.ehu.es> <19981228180232.58123@breizh.prism.uvsq.fr> <3688CDAB.35B7C35F@we.lc.ehu.es> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.81e In-Reply-To: =?iso-8859-1?Q?=3C3688CDAB=2E35B7C35F=40we=2Elc=2Eehu=2Ees=3E=3B_from_Jo?= =?iso-8859-1?Q?s=E9_M=AA_Alcaide_on_Tue=2C_Dec_29=2C_1998_at_01=3A40=3A1?= =?iso-8859-1?Q?1PM_+0100?= X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 29, 1998 at 01:40:11PM +0100, José Mª Alcaide wrote: [...] >I have tried all combinations of flags, to no avail. Also, I have >tried two parallel port BIOS settings: "normal" and "EPP". I don't >know whether the BIOS settings are important or not. I am not >a parallel port guru! :-) > >In all cases, the vpo controller is initialized at boot (given that >the ZIP drive is on and attached), but the "da" device is not >initialized. Perhaps the problem resides in the interaction >between CAM (scbus/da) and the vpo controller. Yes, I think. CAMDEBUG option makes all run correctly here. When CAMDEBUG is not set, VP0_DEBUG reports no XPT_SCSI_IO request. Justin? -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 30 03:57:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06229 for freebsd-current-outgoing; Wed, 30 Dec 1998 03:57:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06160; Wed, 30 Dec 1998 03:57:08 -0800 (PST) (envelope-from jmb) Date: Wed, 30 Dec 1998 03:57:08 -0800 (PST) From: "Jonathan M. Bresler" Message-Id: <199812301157.DAA06160@hub.freebsd.org> To: committers, current Subject: HEADS UP: Postfix is coming. new uid, gid required. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Starting later today, I will import Postfix (aka VMailer aka SecureMailer from IBM) into the tree under /usr/src/contrib. Postfix was written by Wietse Venema (tcp_wrappers, satan, etc). Postfix is a mail transfer agent. Postfix runs as its own user. We will be adding a new system uid and gid (user mta, uid 25, group mta, gid 25). You will need to add this user and group by hand using the /usr/src/etc/{group,master.passwd} files as a template. You will be able to choose between Sendmail and Postfix as your mail transfer agent. Therefore, you can ignore Postfix, if you choose. For a sneak preview take a look at http://www.postfix.org and http://www.alphaWorks.ibm.com/formula/securemailer. Postfix is still under development as so is labelled "beta". However, the FreeBSD mailing lists have been using Postfix for more than 4 months without incident. Wietse's beta is better than many "finished" products ;) jmb -- Jonathan M. Bresler FreeBSD Core Team, Postmaster jmb@FreeBSD.ORG FreeBSD--The Power to Serve JMB193 http://www.freebsd.org/ PGP 2.6.2 Fingerprint: 31 57 41 56 06 C1 40 13 C5 1C E3 E5 DC 62 0E FB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 04:59:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA12663 for freebsd-current-outgoing; Wed, 30 Dec 1998 04:59:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from maulwurf.franken.de (maulwurf.franken.de [193.141.110.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA12657 for ; Wed, 30 Dec 1998 04:59:32 -0800 (PST) (envelope-from gaspode.franken.de!tanis@maulwurf.franken.de) Received: by maulwurf.franken.de via rmail with stdio id for freebsd-current@freebsd.org; Wed, 30 Dec 1998 13:59:09 +0100 (MET) (Smail-3.2 1996-Jul-4 #1 built DST-May-30) Received: (from tanis@localhost) by gaspode.franken.de (8.9.1/8.8.8) id NAA10267 for freebsd-current@freebsd.org; Wed, 30 Dec 1998 13:57:10 +0100 (CET) (envelope-from tanis) Message-ID: <19981230135710.A9990@gaspode.franken.de> Date: Wed, 30 Dec 1998 13:57:10 +0100 From: German Tischler To: freebsd-current@FreeBSD.ORG Subject: cdrecord/cam 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 Hi. I'm getting the following error when trying to write a cdrw with cdrecord 1.8a14 with current from yesterday: cam_periph_mapmem: attempt to map 66560 bytes, which is greater than DFLTPHYS(65536) Can I increase DFLTPHYS in /sys/i386/include/param.h without problems, to avoid this ? -- German Tischler tanis@gaspode.franken.de Apple eaten (core dumped) tanis@cip.informatik.uni-wuerzburg.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 05:23:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14645 for freebsd-current-outgoing; Wed, 30 Dec 1998 05:23:45 -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 FAA14640 for ; Wed, 30 Dec 1998 05:23:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id FAA11019; Wed, 30 Dec 1998 05:23:21 -0800 (PST) To: shocking@prth.pgs.com (Stephen Hocking-Senior Programmer PGS Tensor Perth) cc: current@FreeBSD.ORG Subject: Re: Oi! When's the Voxware stuff coming back into current? In-reply-to: Your message of "Wed, 30 Dec 1998 15:54:15 +0800." <199812300754.PAA11978@ariadne.tensor.pgs.com> Date: Wed, 30 Dec 1998 05:23:21 -0800 Message-ID: <11015.915024201@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This peasant is getting restless...... The peasant should finish reading to the end of his mailbox. :) As I've already announced, we'll be resurrecting stuff on the 1st. We needed to give discussion a chance to die down first. - 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 30 06:17:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA18444 for freebsd-current-outgoing; Wed, 30 Dec 1998 06:17:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA18436 for ; Wed, 30 Dec 1998 06:17:32 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id GAA23596; Wed, 30 Dec 1998 06:17:00 -0800 (PST) Date: Wed, 30 Dec 1998 06:17:00 -0800 (PST) From: "Steven P. Donegan" To: Christian Kuhtz cc: Steve Passe , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-Reply-To: <19981229234937.N477@ns1.adsu.bellsouth.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 The two (different, but similar) goals I'm looking at are: Hobby level (ie commodity hardware and 'cheap') NOW plaything Commercially usable NOW tool ($ not as much a factor) MOSIX provides for up to 6 BSDI nodes, using any available network path(s) and provides transparent load distribution/migration - no specialized programming/API's needed to use it - it appears as if it's one computer. Beowulf requires PVM style programming, but runs today on Linux SMP platforms and supports network card trunking in the kernel drivers (like, but not compatable with, Cisco's etherchannel). Both have interface support for Myrinet - a proprietary crossbar switch based gig speed LAN. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 07:26:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA24673 for freebsd-current-outgoing; Wed, 30 Dec 1998 07:26:19 -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 HAA24668 for ; Wed, 30 Dec 1998 07:26:17 -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 HAA10274; Wed, 30 Dec 1998 07:25:57 -0800 (PST) Date: Wed, 30 Dec 1998 07:25:57 -0800 (PST) From: Chris Timmons To: John Polstra cc: current@FreeBSD.ORG Subject: Re: CVS issues In-Reply-To: <199812300244.SAA13476@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Different CVSup servers allow different numbers of connections. I can't remember what you said would happen when the client gets connection refused and has more A records to try; will it go to the next one? -Chris On Tue, 29 Dec 1998, John Polstra wrote: > In article , > Steven P. Donegan wrote: > > > > This is not a complex problem. If mirror sites are not true mirrors then > > don't put them in the round robbin. > > There are only 3 US mirrors, so a round robin would be kind of silly > without all of them. (Note, I am not going to round robin the non-US > mirrors at this time.) Therefore I need to make them carry exactly > the same collections, or at least document the variances. > > No, it's not a complex problem. But I've got a backlog of more > important problems to deal with first. Sorry, that's just life. > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 07:33:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA25179 for freebsd-current-outgoing; Wed, 30 Dec 1998 07:33:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA25161; Wed, 30 Dec 1998 07:33:42 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id QAA24347; Wed, 30 Dec 1998 16:32:52 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id OAA00796; Wed, 30 Dec 1998 14:25:34 GMT (envelope-from son) Message-ID: <19981230142534.16952@breizh.prism.uvsq.fr> Date: Wed, 30 Dec 1998 14:25:34 +0000 From: Nicolas Souchu To: sthaug@nethelp.no Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Request fo help with Zip Drive on vpo0 in -current] References: <26784.914978880@verdi.nethelp.no> <27331.914982190@verdi.nethelp.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <27331.914982190@verdi.nethelp.no>; from sthaug@nethelp.no on Wed, Dec 30, 1998 at 02:43:10AM +0100 X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 30, 1998 at 02:43:10AM +0100, sthaug@nethelp.no wrote: > >> What finally made it work for me was: EPP mode in the BIOS, and >> >> controller ppc0 at isa? port ? tty irq 7 >> >> in the kernel config. Ie. no flags at all. With this setup, my Zip drive >> is detected as >> >> da1 at vpo0 bus 0 target 6 lun 0 >> da1: Removable Direct Access SCSI-2 device >> da1: 196608 512 byte sectors: 64H 32S/T 96C > >A followup: There is probably a timing-related issue here. If I remove >the various CAMDEBUG options, the Zip drive isn't detected. With the >CAMDEBUG options (and thus lots of extra printout), it is detected. >Verbose boot or not makes no difference. The problem is the 'CAMDEBUG' option itself. Without it, no I/O request is ever sent to the vpo driver. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - 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 30 08:07:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA28400 for freebsd-current-outgoing; Wed, 30 Dec 1998 08:07:41 -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 IAA28393 for ; Wed, 30 Dec 1998 08:07:36 -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 OAA17779 for current@freebsd.org; Wed, 30 Dec 1998 14:58:13 +0100 From: Luigi Rizzo Message-Id: <199812301358.OAA17779@labinfo.iet.unipi.it> Subject: -DKERNEL option when compiling kernels ? To: current@FreeBSD.ORG Date: Wed, 30 Dec 1998 14:58:13 +0100 (MET) X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, i see that now -DKERNEL is the only define left in the command line, most things being in opt_global.h Couldn't it also go into opt_global.h ? luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 08:28:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00191 for freebsd-current-outgoing; Wed, 30 Dec 1998 08:28:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00186 for ; Wed, 30 Dec 1998 08:28:49 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id LAA26381; Wed, 30 Dec 1998 11:23:24 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199812301623.LAA26381@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Andrew Atrens" cc: Poul-Henning Kamp , current@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: X-ten References: In-reply-to: Your message of "Wed, 30 Dec 1998 02:50:16 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 11:23:23 -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Further hitlist candidates are: > > > > X-ten > > Please record my vote for keeping x-ten _functionality_. It's probably a > good candidate to be kld-omized, but in the meantime works just fine as > is. The TW-523 device that this driver talks to is central to many > home automation projects and is sold today as it was when the driver was > written. I don't know what the installed base of users for the TW-523 driver in FreeBSD, but it seems rather doubtful that many new instances of these are popping up. There are a newer generation of X-10 powerline computer interfaces that plug into a serial ports, and this seems to be the more popular alternative these days. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 08:31:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00634 for freebsd-current-outgoing; Wed, 30 Dec 1998 08:31:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00620 for ; Wed, 30 Dec 1998 08:31:17 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id RAA07431; Wed, 30 Dec 1998 17:30:56 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA20751 (5.67b/IDA-1.5); Wed, 30 Dec 1998 17:27:01 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id QAA01475; Wed, 30 Dec 1998 16:54:28 +0100 (CET) From: Wilko Bulte Message-Id: <199812301554.QAA01475@yedi.iaf.nl> Subject: Re: Buildworld failure in -current aout-to-elf build. In-Reply-To: <368A0FE6.55408324@newsguy.com> from "Daniel C. Sobral" at "Dec 30, 98 08:35:02 pm" To: dcs@newsguy.com (Daniel C. Sobral) Date: Wed, 30 Dec 1998 16:54:28 +0100 (CET) Cc: current@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.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 As Daniel C. Sobral wrote... > Jaye Mathisen wrote: > > > > OK, step 2 was to convert to elf. Close, but no banana. > > Most likely, it is a trade issue with EU... :-) Banana? Wasn't the proverb: "Close, but no cigar" ? Or do we have to thank Mr Starr for ruining this one? ;-) ;-) Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by 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 30 08:32:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00838 for freebsd-current-outgoing; Wed, 30 Dec 1998 08:32:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00829 for ; Wed, 30 Dec 1998 08:32:14 -0800 (PST) (envelope-from smp@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost.StevesCafe.com [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.8/8.8.5) with ESMTP id JAA02401; Wed, 30 Dec 1998 09:35:56 -0700 (MST) Message-Id: <199812301635.JAA02401@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: "Steven P. Donegan" cc: Christian Kuhtz , Steve Passe , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-reply-to: Your message of "Wed, 30 Dec 1998 06:17:00 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 09:35:55 -0700 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > The two (different, but similar) goals I'm looking at are: > > Hobby level (ie commodity hardware and 'cheap') NOW plaything This is what I'm looking at. I have a dual p5, dual p6, and 3 dual PII that I would like to clucster. Obviously not a mix that promotes commercial efficiency. But a good cross section for concept development. IMHO this "hobby level" model is what would best serve the free community. > MOSIX provides for up to 6 BSDI nodes, using any available network > path(s) and provides transparent load distribution/migration - no > specialized programming/API's needed to use it - it appears as if it's > one computer. This appeals to me, when I went to the MOSIX site I only saw linux code, can anyone point me at bsdi code? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor 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 30 08:49:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA03108 for freebsd-current-outgoing; Wed, 30 Dec 1998 08:49:09 -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 IAA03103 for ; Wed, 30 Dec 1998 08:49:07 -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 PAA17904; Wed, 30 Dec 1998 15:37:07 +0100 From: Luigi Rizzo Message-Id: <199812301437.PAA17904@labinfo.iet.unipi.it> Subject: Re: /dev/acd - anybody know how to use with CD-RW? To: sos@freebsd.dk (Søren Schmidt) Date: Wed, 30 Dec 1998 15:37:07 +0100 (MET) Cc: kkennawa@physics.adelaide.edu.au, freebsd-current@FreeBSD.ORG In-Reply-To: <199812301135.MAA95546@freebsd.dk> from "Søren Schmidt" at Dec 30, 98 12:35:10 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It seems Kris Kennaway wrote: > > >> You can read CDDA disk with the acd driver, I have a patched cdd > >> that can do this on my ftp site: > >> > >> ftp://freebsd.dk/pub/ATAPI/cdd-* > > > >The source no longer compiles..I don't think it's been CAMified.o i am looking at this now, trying to make a cdd port. How hard is to convert from libscsi to libcam ? Is there some already-written glue ? cheers luigi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 08:58:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA04329 for freebsd-current-outgoing; Wed, 30 Dec 1998 08:58:27 -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 IAA04324 for ; Wed, 30 Dec 1998 08:58:25 -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 LAA29928; Wed, 30 Dec 1998 11:57:54 -0500 (EST) (envelope-from wollman) Date: Wed, 30 Dec 1998 11:57:54 -0500 (EST) From: Garrett Wollman Message-Id: <199812301657.LAA29928@khavrinen.lcs.mit.edu> To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: CVS issues In-Reply-To: <19981230111824.B32696@freebie.lemis.com> References: <19981230111824.B32696@freebie.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > I've tended to use cvsup.FreeBSD.org because I assume that commits get > there faster. How much lag is there on the other sites? No more than an hour. -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 Wed Dec 30 09:01:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA04708 for freebsd-current-outgoing; Wed, 30 Dec 1998 09:01:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA04693; Wed, 30 Dec 1998 09:01:00 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id MAA02474; Wed, 30 Dec 1998 12:00:15 -0500 (EST) Date: Wed, 30 Dec 1998 12:00:15 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Robert Nordier cc: Stefan Eggers , freebsd-current@FreeBSD.ORG, rnordier@FreeBSD.ORG Subject: Re: New boot2 able to boot old -stable from 2nd BSD partition? In-Reply-To: <199812300919.LAA10457@ceia.nordier.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, 30 Dec 1998, Robert Nordier wrote: > Stefan Eggers wrote: > > > I'd like to use the new boot2 to boot a -stable kernel from the > > *second* FreeBSD partition. If need be I will modify it to grab the > > second (active) one instead of the first but what I saw today looks > > like it can do that already. (*) > > Yes, the new boot2 will prefer an active FreeBSD slice over the first > FreeBSD slice. > > You can also specify the slice, eg. "da(0,2,a)", either at the "boot:" > prompt or in /boot.config. > > > (*) In case it is already able to do the right thing we should modify > > boot(8) as soon as we use the new boot blocks as default as that man > > page says it will boot from the first one only. > > The new boot blocks are already the default in -current. Though you're > right, the man page does need revision. I _still_ can't get the new bootblocks to work, the computer just resets on boot before I get a prompt. This is with a new motherboard, and it didn't work on the old one either. > > -- > Robert Nordier > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Wed Dec 30 09:35:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08577 for freebsd-current-outgoing; Wed, 30 Dec 1998 09:35:39 -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 JAA08572 for ; Wed, 30 Dec 1998 09:35:36 -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 MAA13608; Wed, 30 Dec 1998 12:35:16 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.1/8.9.1) id MAA09875; Wed, 30 Dec 1998 12:34:35 -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, 30 Dec 1998 12:34:35 -0500 (EST) To: "Steven P. Donegan" Cc: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-Reply-To: References: <19981229234937.N477@ns1.adsu.bellsouth.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13962.21666.37548.990651@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Steven P. Donegan writes: > Both have interface support for Myrinet - a proprietary crossbar switch > based gig speed LAN. > The URL for people to read more about Myrinet is http://www.myri.com. I'd like to chime in with the opinion that if you have the money for a high-speed cluster interconnect, Myrinet is an excellent choice. In many respects, Myrinet much more flexible than Gigabit Ethernet. This is primarily because the Myrinet NIC is programmable via downloadble firmware and there are few hardware standards to follow (eg, no hardware imposed MTU, the smallest message can be just 4 bytes, you can design custom header info so messages can be DMA'ed by the NIC to pre-determined memory locations for zero-copy protocols, etc). This flexibility comes at the price of being willing to get your hands dirty & write your own messaging system for Myrinet. Locally, we've done just this -- see http://www.cs.duke.edu/ari/trapeze. Trapeze consists of a messaging library and custom firmware for Myrinet. Trapeze currently hosts kernel to kernel RPC communications and zero-copy page migration traffic for network storage, a user-level communications layer for MPI on Digital UNIX, a low-overhead kernel logging and profiling system, and TCP/IP device drivers for FreeBSD and Digital UNIX. I emphasize that Trapeze itself is not a MOSIX or Beowulf equivalent. Rather, Trapeze is a building block that such a parallel NOW cluster could be built on. Our focus is network storage, not parallel processing, so we haven't done so ourselves. Trapeze is essentially the FreeBSD equivalent to the Linux BIP package (http://lhpca.univ-lyon1.fr). Trapeze is available in source form with a BSD style copyright. Trapeze supports FreeBSD (i386 & alpha) as well as Digital UNIX. Note that the release of Trapeze available at the above URL is rather old & we are currently preparing a new release (should be available shortly after the holidays). 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 Wed Dec 30 10:09:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA13291 for freebsd-current-outgoing; Wed, 30 Dec 1998 10:09:30 -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 KAA13277; Wed, 30 Dec 1998 10:09:24 -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 NAA25102; Wed, 30 Dec 1998 13:09:00 -0500 (EST) Received: from bb01f39.unx.sas.com by mozart (5.65c/SAS/Domains/5-6-90) id AA03719; Wed, 30 Dec 1998 13:09:00 -0500 Received: (from jwd@localhost) by bb01f39.unx.sas.com (8.9.1/8.9.1) id NAA04262; Wed, 30 Dec 1998 13:08:49 -0500 (EST) (envelope-from jwd) From: "John W. DeBoskey" Message-Id: <199812301808.NAA04262@bb01f39.unx.sas.com> Subject: Failure building dsssl/modular To: kuriyama@FreeBSD.ORG Date: Wed, 30 Dec 1998 13:08:49 -0500 (EST) 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 Hi, (-current & maintainer) The following is failing during a make release: >> db130jpja-981223.diff.gz doesn't seem to exist on this system. >> Attempting to fetch from http://www.freebsd.org/~kuriyama/distfiles/. fetch: reading reply from www.freebsd.org: Connection refused >> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//. fetch: pub/FreeBSD/distfiles//db130jpja-981223.diff.gz: cannot get remote modification time fetch: ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//db130jpja-981223.diff.gz: FTP error: fetch: File unavailable (e.g., file not found, no access) >> Couldn't fetch it - please try to retrieve this >> port manually into /usr/ports/distfiles/ and try again. *** Error code 1 The .gz files does not exist in ~kuriyama/distfiles/ though their is a .diff file there. The file simply does not exist at: ftp://ftp.freebsd.org/pub/FreeBSD/distfiles/ 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 30 10:52:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA17584 for freebsd-current-outgoing; Wed, 30 Dec 1998 10:52: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 KAA17576 for ; Wed, 30 Dec 1998 10:52:50 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id KAA90467; Wed, 30 Dec 1998 10:52:26 -0800 (PST) (envelope-from dillon) Date: Wed, 30 Dec 1998 10:52:26 -0800 (PST) From: Matthew Dillon Message-Id: <199812301852.KAA90467@apollo.backplane.com> To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: -DKERNEL option when compiling kernels ? References: <199812301358.OAA17779@labinfo.iet.unipi.it> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Hi, : :i see that now -DKERNEL is the only define left in the command line, :most things being in opt_global.h : :Couldn't it also go into opt_global.h ? : : luigi No, else how do source moduels know whether to #include opt_global.h or not ? If they aren't being compiled as part of the kernel no opt_global.h would exist. -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 Wed Dec 30 11:09:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19963 for freebsd-current-outgoing; Wed, 30 Dec 1998 11:09: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 LAA19955 for ; Wed, 30 Dec 1998 11:09:46 -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 0zvQzg-0007Up-00; Wed, 30 Dec 1998 12:09:20 -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 MAA00595; Wed, 30 Dec 1998 12:07:17 -0700 (MST) Message-Id: <199812301907.MAA00595@harmony.village.org> To: "Louis A. Mamakos" Subject: Re: X-ten Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 30 Dec 1998 11:23:23 EST." <199812301623.LAA26381@whizzo.transsys.com> References: <199812301623.LAA26381@whizzo.transsys.com> Date: Wed, 30 Dec 1998 12:07:17 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812301623.LAA26381@whizzo.transsys.com> "Louis A. Mamakos" writes: : I don't know what the installed base of users for the TW-523 driver in : FreeBSD, but it seems rather doubtful that many new instances of these : are popping up. There are a newer generation of X-10 powerline computer : interfaces that plug into a serial ports, and this seems to be the more : popular alternative these days. While it is an alternative these days, it is still a more costly alternative. When I was looking at X-10 hardware this past fall, I noticed that the TW-523 interface ran approx $30-$40 assembled, while the serial versions ran more like $80 (kit) or $120 (assembled). There is nothing wrong with the TW-523 interface, and given its cost advantage, I suspect it will be around for a long time to come. I've sent mail to phk privately, but will say here publicly that if the current xten maintainer were to go missing, I'd gladly step into the breach. Until such time as we have a good build environment for loadable drivers, a good devfs implementation that is default and some way to have ports for kernel hunks, I think it premature to remove a working, used and maintained driver from the tree. While source tree cleanup is a luadable goal, there needs to be more infrastructure in place before drivers are cut loose. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 11:40:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA23176 for freebsd-current-outgoing; Wed, 30 Dec 1998 11:40:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-57-dbn.dial-up.net [196.34.155.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA23121 for ; Wed, 30 Dec 1998 11:39:57 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id VAA12903; Wed, 30 Dec 1998 21:38:38 +0200 (SAT) From: Robert Nordier Message-Id: <199812301938.VAA12903@ceia.nordier.com> Subject: Re: New boot2 able to boot old -stable from 2nd BSD partition? In-Reply-To: from Brian Feldman at "Dec 30, 98 12:00:15 pm" To: green@unixhelp.org (Brian Feldman) Date: Wed, 30 Dec 1998 21:38:35 +0200 (SAT) Cc: rnordier@nordier.com, seggers@semyam.dinoco.de, 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 Brian Feldman wrote: > I _still_ can't get the new bootblocks to work, the computer just > resets on boot before I get a prompt. This is with a new motherboard, > and it didn't work on the old one either. I'd suggest installing the new boot blocks and then sending along the following output: #!/bin/sh DRIVE=da0 # Change as required fdisk /dev/r${DRIVE} dd if=/dev/r${DRIVE} count=1 | hexdump -C dd if=/dev/r${DRIVE}a count=32 | hexdump -C If that doesn't turn up anything, and you want to pursue this, I'll prepare a debug version to indicate at what stage things are going wrong. -- 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 30 11:59:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25339 for freebsd-current-outgoing; Wed, 30 Dec 1998 11:59:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles147.castles.com [208.214.165.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25326; Wed, 30 Dec 1998 11:59:04 -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 LAA05421; Wed, 30 Dec 1998 11:56:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812301956.LAA05421@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Gary Palmer" cc: Brian Behlendorf , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-reply-to: Your message of "Wed, 30 Dec 1998 03:11:29 EST." <16298.915005489@gjp.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 11:56:10 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I dont count `LDAP' as a highly-scalable service. Sure, it is one that > is very supportive of horizontal scaling (throwing more servers at it), > but from all the indications I've seen/heard its a lot more resource > intensive than it needs to be, and likely will not be deployed large > scale where I work for that very reason (we'll grow a distributed > password system inhouse) Have you actually evaulated it, or are you just going on word-of-mouth? -- \\ 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 30 12:11:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26366 for freebsd-current-outgoing; Wed, 30 Dec 1998 12:11:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail2.tor.accglobal.net (mail2.tor.accglobal.net [204.92.55.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26360; Wed, 30 Dec 1998 12:11:21 -0800 (PST) (envelope-from josh@ican.net) Received: from staff.tor.acc.ca ([204.92.55.27]) by mail2.tor.accglobal.net with esmtp (Exim 2.02 #1) id 0zvRxI-0005ou-02; Wed, 30 Dec 1998 15:10:56 -0500 Received: from josh by staff.tor.acc.ca with local (Exim 1.92 #1) id 0zvRxI-0001q2-00; Wed, 30 Dec 1998 15:10:56 -0500 Message-ID: <19981230151056.00820@ican.net> Date: Wed, 30 Dec 1998 15:10:56 -0500 From: Josh Tiefenbach To: Mike Smith Cc: Gary Palmer , Brian Behlendorf , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: <16298.915005489@gjp.erols.com> <199812301956.LAA05421@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199812301956.LAA05421@dingo.cdrom.com>; from Mike Smith on Wed, Dec 30, 1998 at 11:56:10AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I dont count `LDAP' as a highly-scalable service. Sure, it is one that > > is very supportive of horizontal scaling (throwing more servers at it), > > but from all the indications I've seen/heard its a lot more resource > > intensive than it needs to be, and likely will not be deployed large > > scale where I work for that very reason (we'll grow a distributed > > password system inhouse) > > Have you actually evaulated it, or are you just going on word-of-mouth? We've actually evaluated it, are actually using it, and was one of the ones who described it as being a `pig' to Gary at LISA. For a small-medium size site, the scaling issues arent all that severe. However, once you expand to something like the size of Worldnet or Earthlink's user base, things get really unwieldly, really fast (extrapolations based on my own experiences). Granted, my observations are based on Netscape's implementation on a non-FreeBSD platform, but from what I've seen, the conclusions do extend to the general case. josh -- Josh Tiefenbach - Member - ACC Corps of Internet Engineers - josh@ican.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 30 12:42:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29238 for freebsd-current-outgoing; Wed, 30 Dec 1998 12:42:49 -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 MAA29233 for ; Wed, 30 Dec 1998 12:42:48 -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 MAA86050; Wed, 30 Dec 1998 12:41:57 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199812302041.MAA86050@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin cc: "Steven P. Donegan" , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-reply-to: Your message of "Wed, 30 Dec 1998 12:34:35 EST." <13962.21666.37548.990651@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 12:41:57 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > dirty & write your own messaging system for Myrinet. Locally, we've > done just this -- see http://www.cs.duke.edu/ari/trapeze. > I think Intel should loan your a couple xeon 450 based systems . Curious does anyone know if Myrinet is making an AGP version of their board? Cheers, 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 30 12:58:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00541 for freebsd-current-outgoing; Wed, 30 Dec 1998 12:58:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles147.castles.com [208.214.165.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00535 for ; Wed, 30 Dec 1998 12:58:03 -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 MAA05735; Wed, 30 Dec 1998 12:55:03 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812302055.MAA05735@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Josh Tiefenbach cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-reply-to: Your message of "Wed, 30 Dec 1998 15:10:56 EST." <19981230151056.00820@ican.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 12:55:02 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I dont count `LDAP' as a highly-scalable service. Sure, it is one that > > > is very supportive of horizontal scaling (throwing more servers at it), > > > but from all the indications I've seen/heard its a lot more resource > > > intensive than it needs to be, and likely will not be deployed large > > > scale where I work for that very reason (we'll grow a distributed > > > password system inhouse) > > > > Have you actually evaulated it, or are you just going on word-of-mouth? > > We've actually evaluated it, are actually using it, and was one of the ones > who described it as being a `pig' to Gary at LISA. > > For a small-medium size site, the scaling issues arent all that severe. > However, once you expand to something like the size of Worldnet or Earthlink's > user base, things get really unwieldly, really fast (extrapolations based on > my own experiences). > > Granted, my observations are based on Netscape's implementation on a > non-FreeBSD platform, but from what I've seen, the conclusions do extend to > the general case. Cool; thanks for the review. Anyone else using either the Netscape server or experimenting with the OpenLDAP implementation are invited to speak up; this sort of input's really useful. -- \\ 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 30 13:33:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03654 for freebsd-current-outgoing; Wed, 30 Dec 1998 13:33:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03649 for ; Wed, 30 Dec 1998 13:33:06 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id QAA01085; Wed, 30 Dec 1998 16:32:35 -0500 (EST) Message-ID: <19981230163235.C828@ns1.adsu.bellsouth.com> Date: Wed, 30 Dec 1998 16:32:35 -0500 From: Christian Kuhtz To: Mike Smith , Josh Tiefenbach Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: <19981230151056.00820@ican.net> <199812302055.MAA05735@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812302055.MAA05735@dingo.cdrom.com>; from Mike Smith on Wed, Dec 30, 1998 at 12:55:02PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Have you actually evaulated it, or are you just going on word-of-mouth? > > > > We've actually evaluated it, are actually using it, and was one of the ones > > who described it as being a `pig' to Gary at LISA. Slightly off-topic, but if you are looking for a fast and very solid LDAP server, you may want to take a very serious look at NetWare5 (particularly with SKADS). I can't publish performance numbers because of NDAs, other than to say that it is *significantly* faster (and more robust) than anything else out there. This applies to reads as well as inserts. Before you break out into a laughter, being a UNIX geek, I have to admit that this piece of code rocks. They do things like XFree86 on NetWare5 and it is no longer an alien entity in the network. Can you imagine launching an xterm off a NetWare server to admin it? :) It has one thing that we're particularly keen on is multimaster directory services; a must for any large scale deployment (the whole notion of having to commit all writes in one places is ridiculous). Without that, LDAP is useless IMHO. (mind you, LDAP itself doesn't do multimaster, but by virtue of having NDS underneath, you get LDAP multimaster for free). The evaluation here was for very large scale deployment purposes. If I had to deploy today, NetWare5 would be my choice, with a major gap between it and the next one done. And I am not a NetWare believer by any means. But this is serious code. I agree that pretty much all other directory services suck rocks. Disclaimer: I don't speak for BellSouth Corporation, and the views expressed here are soly my own. Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 13:54:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05355 for freebsd-current-outgoing; Wed, 30 Dec 1998 13:54:34 -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 NAA05350 for ; Wed, 30 Dec 1998 13:54:29 -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 UAA18533; Wed, 30 Dec 1998 20:45:12 +0100 From: Luigi Rizzo Message-Id: <199812301945.UAA18533@labinfo.iet.unipi.it> Subject: Re: -DKERNEL option when compiling kernels ? To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 30 Dec 1998 20:45:12 +0100 (MET) Cc: current@FreeBSD.ORG In-Reply-To: <199812301852.KAA90467@apollo.backplane.com> from "Matthew Dillon" at Dec 30, 98 10:52:07 am X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > :Hi, > : > :i see that now -DKERNEL is the only define left in the command line, > :most things being in opt_global.h > : > :Couldn't it also go into opt_global.h ? > : > : luigi > > No, else how do source moduels know whether to #include opt_global.h > or not ? If they aren't being compiled as part of the kernel no > opt_global.h would exist. perhaps i wasn't clear. It is just a cosmetic issue. A kernel compile is now run as cc ... -DKERNEL -include opt_global.h ... so opt_global.h is not explicitly included by any file, and one could as well put a #define KERNEL into it. Now the only thing would be that opt_global.h contains almost nothing, which makes me think that it could also disappear at some point... luigi -----------------------------------+------------------------------------- Luigi RIZZO . EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) -----------------------------------+------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 14:13:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA06793 for freebsd-current-outgoing; Wed, 30 Dec 1998 14:13:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA06788 for ; Wed, 30 Dec 1998 14:13:47 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id OAA24245; Wed, 30 Dec 1998 14:13:21 -0800 (PST) Date: Wed, 30 Dec 1998 14:13:20 -0800 (PST) From: "Steven P. Donegan" To: Mike Smith cc: Josh Tiefenbach , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-Reply-To: <199812302055.MAA05735@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 > > Cool; thanks for the review. Anyone else using either the Netscape > server or experimenting with the OpenLDAP implementation are invited to > speak up; this sort of input's really useful. > I 'vampired' my corporate LDAP directory (roughly 15k entries) and populated a FreeBSD and Netscape system with it (FreeBSD was the ldap in the ports directory). Both systems were basically identical as far as hardware goes. The FreeBSD response to queries was roughly twice as fast as the Netscape under NT. Since the database was very small (5 meg or so) I would see no reason why this couldn't scale indefinitely... (round robin DNS or Cisco load director etc.). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 14:30:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08693 for freebsd-current-outgoing; Wed, 30 Dec 1998 14:30:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.westbend.net (ns1.westbend.net [156.46.203.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08688 for ; Wed, 30 Dec 1998 14:30:17 -0800 (PST) (envelope-from hetzels@westbend.net) Received: from admin (admin.westbend.net [156.46.203.13]) by mail.westbend.net (8.8.8/8.8.8) with SMTP id QAA01364 for ; Wed, 30 Dec 1998 16:29:53 -0600 (CST) (envelope-from hetzels@westbend.net) Message-ID: <002d01be3443$ec1c8da0$0dcb2e9c@westbend.net> From: "Scot W. Hetzel" To: "FreeBSD-Current" Subject: Fw: Fw: apache_fp-1.3.3 (Apology for the Cross Post) Date: Wed, 30 Dec 1998 16:29:53 -0600 Organization: West Bend Internet MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.1012.1001 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.1012.1001 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am sorry about the crossposting. But my reasoning for sending it to each list was: 1. The HandBook needs to have a section on where to get the DES library, and how to install it. (FreeBSD-Doc) 2. I wanted to get this message into the ports mailing list archive. Since most people will search for port issues there. (FreeBSD-ports) 3. I had included a couple of patches for the des/install.sh script for Current & Stable (FreeBSD-Current, FreeBSD-Stable). I should have submitted these patches in a PR instead of crossposting to the Stable & Current mailing lists. I know these reasoning doesn't excuse the crossposting, and I should have never have sent it to the current or stable mailing lists. For that I am extremely sorry. Scot To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 14:32:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09357 for freebsd-current-outgoing; Wed, 30 Dec 1998 14:32:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09347 for ; Wed, 30 Dec 1998 14:32:46 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id RAA01918; Wed, 30 Dec 1998 17:32:10 -0500 (EST) Message-ID: <19981230173210.F828@ns1.adsu.bellsouth.com> Date: Wed, 30 Dec 1998 17:32:10 -0500 From: Christian Kuhtz To: "Steven P. Donegan" , Mike Smith Cc: Josh Tiefenbach , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: <199812302055.MAA05735@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Steven P. Donegan on Wed, Dec 30, 1998 at 02:13:20PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 30, 1998 at 02:13:20PM -0800, Steven P. Donegan wrote: > I 'vampired' my corporate LDAP directory (roughly 15k entries) and > populated a FreeBSD and Netscape system with it (FreeBSD was the ldap in > the ports directory). Both systems were basically identical as far as > hardware goes. The FreeBSD response to queries was roughly twice as fast > as the Netscape under NT. Since the database was very small (5 meg or so) > I would see no reason why this couldn't scale indefinitely... (round > robin DNS or Cisco load director etc.). Well, for starters, where are you going to commit your writes? Your assumption is that the directory won't be written much and is primarily read. In large scale deployments writes become nearly as important as reads. And most servers bomb on that (except for the one described in my previous message). We have another bake-off coming up and I might be able to share some experience data. Anyone interested? Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 15:06:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12881 for freebsd-current-outgoing; Wed, 30 Dec 1998 15:06:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp3.erols.com (smtp3.erols.com [207.172.3.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA12874 for ; Wed, 30 Dec 1998 15:06:51 -0800 (PST) (envelope-from shmit@natasya.noc.erols.net) Received: from natasya.noc.erols.net (natasya.noc.erols.net [207.172.25.236]) by smtp3.erols.com (8.8.8/8.8.5) with ESMTP id SAA12921; Wed, 30 Dec 1998 18:05:42 -0500 (EST) Received: (from shmit@localhost) by natasya.noc.erols.net (8.9.1/8.9.1) id SAA18244; Wed, 30 Dec 1998 18:05:42 -0500 (EST) Message-ID: <19981230180542.D2451@kublai.com> Date: Wed, 30 Dec 1998 18:05:42 -0500 From: Brian Cully To: John Polstra , "Jordan K. Hubbard" Cc: Bill Fumerola , current@FreeBSD.ORG, forrie@navinet.net, Greg Lehey Subject: Re: CVS issues Reply-To: shmit@kublai.com References: <9096.914979535@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from John Polstra on Tue, Dec 29, 1998 at 05:25:38PM -0800 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 29, 1998 at 05:25:38PM -0800, John Polstra wrote: > On 30-Dec-98 Jordan K. Hubbard wrote: > > > Definitely time to go to the round-robin DNS scheme. > > The reason I haven't done it so far is because the mirrors differ > in some of the little-used collections that they carry. They all > carry the main source tree, but some don't carry the mailing list > archives, for example. Before I can institute round-robin DNS, I need > to either arrange for the relevant mirrors to carry exactly the same > collections, or I need to document exactly what they carry in common. FWIW, cvsup4 carries all the collections, and is mirrored hourly off of freefall. -- Brian Cully You think you're queer? I'll tell you something: we're all queer. If you get befuddled by a middle class morality, get shut of it. Shut it out.... Is there an absolute morality? I don't think so. You think that? Act that way. -- Glengarry Glen Ross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 15:15:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13636 for freebsd-current-outgoing; Wed, 30 Dec 1998 15:15:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp4.erols.com (smtp4.erols.com [207.172.3.237]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13627 for ; Wed, 30 Dec 1998 15:15:07 -0800 (PST) (envelope-from shmit@natasya.noc.erols.net) Received: from natasya.noc.erols.net (natasya.noc.erols.net [207.172.25.236]) by smtp4.erols.com (8.8.8/smtp-v1) with ESMTP id SAA04901; Wed, 30 Dec 1998 18:14:41 -0500 (EST) Received: (from shmit@localhost) by natasya.noc.erols.net (8.9.1/8.9.1) id SAA18286; Wed, 30 Dec 1998 18:14:41 -0500 (EST) Message-ID: <19981230181441.E2451@kublai.com> Date: Wed, 30 Dec 1998 18:14:41 -0500 From: Brian Cully To: Mike Smith , Josh Tiefenbach Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf Reply-To: shmit@kublai.com References: <19981230151056.00820@ican.net> <199812302055.MAA05735@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812302055.MAA05735@dingo.cdrom.com>; from Mike Smith on Wed, Dec 30, 1998 at 12:55:02PM -0800 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 30, 1998 at 12:55:02PM -0800, Mike Smith wrote: > Cool; thanks for the review. Anyone else using either the Netscape > server or experimenting with the OpenLDAP implementation are invited to > speak up; this sort of input's really useful. I've done the evaluation here for the Netscape server, and was fairly unimpressed even though we had a simple setup (no distributed servers, for example, and from what I understand, this is where Netscape's main problems lie). I've heard some very good things about OpenLDAP, but we haven't recieved our eval copy yet. But from reading the literature about the design and implementation, it sounds really sweet. But then again, we've been bitten by sweet-sounding literature before, really really badly (*pokes Gary* :-)). -- Brian Cully You think you're queer? I'll tell you something: we're all queer. If you get befuddled by a middle class morality, get shut of it. Shut it out.... Is there an absolute morality? I don't think so. You think that? Act that way. -- Glengarry Glen Ross To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 15:32:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15408 for freebsd-current-outgoing; Wed, 30 Dec 1998 15:32:33 -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 PAA15401 for ; Wed, 30 Dec 1998 15:32:32 -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 SAA19586; Wed, 30 Dec 1998 18:32:10 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.1/8.9.1) id SAA13350; Wed, 30 Dec 1998 18:31:28 -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, 30 Dec 1998 18:31:28 -0500 (EST) To: Amancio Hasty Cc: "Steven P. Donegan" , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-Reply-To: <199812302041.MAA86050@rah.star-gate.com> References: <13962.21666.37548.990651@grasshopper.cs.duke.edu> <199812302041.MAA86050@rah.star-gate.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13962.46346.872709.715074@grasshopper.cs.duke.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Amancio Hasty writes: > > > > dirty & write your own messaging system for Myrinet. Locally, we've > > done just this -- see http://www.cs.duke.edu/ari/trapeze. > > > I think Intel should loan your a couple xeon 450 based systems . That would be nice ;-). > Curious does anyone know if Myrinet is making an AGP version of their > board? Unfortunately, I don't think they are. But they are planning to offer 64-bit PCI soon. It also features much nicer DMA engines & IP checksum offloading. See http://www.myri.com/myrinet/PCI/pci64.html We're slated to get some beta-test boards as soon as they come back from fab. This is rather off topic, but does anybody know what the cheapest route to a 64-bit PCI slot on an Intel platform is? I know the 450NX chipset supports 64-bit PCI, but the last time I checked, machines using the 450NX chipset were only available in high-margin servers from Dell. Does anybody know of any 3rd-party x86 motherboard that has a 64-bit slot? 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 Wed Dec 30 15:41:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA16441 for freebsd-current-outgoing; Wed, 30 Dec 1998 15:41:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA16434 for ; Wed, 30 Dec 1998 15:41:52 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id PAA24409; Wed, 30 Dec 1998 15:41:25 -0800 (PST) Date: Wed, 30 Dec 1998 15:41:24 -0800 (PST) From: "Steven P. Donegan" To: Christian Kuhtz cc: Mike Smith , Josh Tiefenbach , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-Reply-To: <19981230173210.F828@ns1.adsu.bellsouth.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, 30 Dec 1998, Christian Kuhtz wrote: > > Well, for starters, where are you going to commit your writes? Your assumption > is that the directory won't be written much and is primarily read. > > In large scale deployments writes become nearly as important as reads. And > most servers bomb on that (except for the one described in my previous > message). > > We have another bake-off coming up and I might be able to share some > experience data. Anyone interested? > A very cornerstone assumption in LDAP is reads will outweigh writes, but I didn't find any real issue with write performance anyway. The farm of FreeBSD front ends would talk to an NFS backend (like a Network Appliance) so 'where' you commit your writes would be a moot point. If you are going to use this for a password database (I think that was your use) then why do you think writes will be so significant? (just curious). Our use is for username/location,phone number,email address lookups - which I beleive is probably the most frequent use of LDAP in a commercial environment. That environment is extremely stable - very little change occurs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 16:13:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21677 for freebsd-current-outgoing; Wed, 30 Dec 1998 16:13:34 -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 QAA21672 for ; Wed, 30 Dec 1998 16:13:33 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id QAA91777; Wed, 30 Dec 1998 16:13:07 -0800 (PST) (envelope-from dillon) Date: Wed, 30 Dec 1998 16:13:07 -0800 (PST) From: Matthew Dillon Message-Id: <199812310013.QAA91777@apollo.backplane.com> To: Luigi Rizzo Cc: current@FreeBSD.ORG Subject: Re: -DKERNEL option when compiling kernels ? References: <199812301945.UAA18533@labinfo.iet.unipi.it> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> :most things being in opt_global.h :> : :> :Couldn't it also go into opt_global.h ? :> : :> : luigi :> :> No, else how do source moduels know whether to #include opt_global.h :> or not ? If they aren't being compiled as part of the kernel no :> opt_global.h would exist. : :perhaps i wasn't clear. It is just a cosmetic issue. : :A kernel compile is now run as : : cc ... -DKERNEL -include opt_global.h ... : :so opt_global.h is not explicitly included by any file, and one could :as well put a #define KERNEL into it. :Now the only thing would be that opt_global.h contains almost nothing, :which makes me think that it could also disappear at some point... Ah! I understand. I'll be damned... didn't even notice that it was doing that! -Matt : luigi : :-----------------------------------+------------------------------------- : Luigi RIZZO . : EMAIL: luigi@iet.unipi.it . Dip. di Ing. dell'Informazione : HTTP://www.iet.unipi.it/~luigi/ . Universita` di Pisa : TEL/FAX: +39-050-568.533/522 . via Diotisalvi 2, 56126 PISA (Italy) :-----------------------------------+------------------------------------- : 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 Wed Dec 30 16:25:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA22894 for freebsd-current-outgoing; Wed, 30 Dec 1998 16:25:56 -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 QAA22889 for ; Wed, 30 Dec 1998 16:25:52 -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 TAA28840; Wed, 30 Dec 1998 19:25:14 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Steven P. Donegan" cc: Mike Smith , Josh Tiefenbach , The Hermit Hacker , freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: NOW/MOSIX/Beowulf In-reply-to: Your message of "Wed, 30 Dec 1998 14:13:20 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 19:25:13 -0500 Message-ID: <28835.915063913@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Steven P. Donegan" wrote in message ID : > I 'vampired' my corporate LDAP directory (roughly 15k entries) and > populated a FreeBSD and Netscape system with it (FreeBSD was the ldap in > the ports directory). Both systems were basically identical as far as > hardware goes. The FreeBSD response to queries was roughly twice as fast > as the Netscape under NT. Since the database was very small (5 meg or so) > I would see no reason why this couldn't scale indefinitely... (round > robin DNS or Cisco load director etc.). In my application (ISP), the point of any network based information system (i.e. LDAP) is to provide local caches of information on the machines which need them, with near-real-time updates, so users can get near-instant password changes across 20+ machines, new accounts created before they hang up, etc. My interpretation, and I'm sorry if I'm a bit blunt, of what you're suggesting is more akin to redefining the problem and then throwing hardware at it to scale it horizontally. Not making the application or the software faster & more reliable, but rather just plain throwing hardware at it. Now, you have to understand that my opinions of LDAP aren't for everybody. One of the speakers at LISA earlier this month was very eloquent about the benefits of LDAP in a MIS-type environment, where you are easily centralizing configuration management. My observations come from the standpoint of an ISP, where having local information (preferably read by the querying application straight out of memory) is much preferable to having to traverse the network stack (and possibly a physical network also) a minimum of two times to get the information they are after. Now LDAP looks on the outside very attractive. A network based query API which is meant to have servers which are tuned for reads, but can handle the occasional update. You can toss any data you want into it. It handles replication between servers, so no more custom scripts to handle distribution of locally required information. But, as Josh pointed out, there are downsides. In his case, the schema his legacy system forced him into required that there be multiple LDAP queries to retrieve a single piece of data. This greately increases the resources required to run a local LDAP replica (lets face it, most of the free LDAP servers use DBM as a backend, and I believe Netscapes directory server does also, which isn't the fastest product on the planet) So I guess it all depends what you want. For what this thread started on (a highly scalable mail delivery/processing system), I think with a bit of eblow grease and some understand of the problem, a faster solution which is more tailored to the query needs of your environment, without breaking the bank on adding hardware to support LDAP, is attainable. 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 Wed Dec 30 16:29:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23576 for freebsd-current-outgoing; Wed, 30 Dec 1998 16:29:23 -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 QAA23571 for ; Wed, 30 Dec 1998 16:29:21 -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 TAA28906; Wed, 30 Dec 1998 19:28:57 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: shmit@kublai.com cc: freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: NOW/MOSIX/Beowulf In-reply-to: Your message of "Wed, 30 Dec 1998 18:14:41 EST." <19981230181441.E2451@kublai.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 19:28:56 -0500 Message-ID: <28903.915064136@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Cully wrote in message ID <19981230181441.E2451@kublai.com>: > I've heard some very good things about OpenLDAP, but we haven't > recieved our eval copy yet. But from reading the literature about > the design and implementation, it sounds really sweet. OpenLDAP is freeware. Are you meaning the one which is backended into Oracle and costs 5 figures/CPU? (and no, I don't remember the name either) > But then again, we've been bitten by sweet-sounding literature > before, really really badly (*pokes Gary* :-)). This is indeed true. Beware vendors bearing glossies. 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 Wed Dec 30 16:35:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24169 for freebsd-current-outgoing; Wed, 30 Dec 1998 16:35:15 -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 QAA24161 for ; Wed, 30 Dec 1998 16:35:13 -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 TAA28981; Wed, 30 Dec 1998 19:34:36 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Steven P. Donegan" cc: Christian Kuhtz , Mike Smith , Josh Tiefenbach , The Hermit Hacker , freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: NOW/MOSIX/Beowulf In-reply-to: Your message of "Wed, 30 Dec 1998 15:41:24 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 19:34:36 -0500 Message-ID: <28977.915064476@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Steven P. Donegan" wrote in message ID : > The farm of FreeBSD front ends would talk to an NFS backend (like a > Network Appliance) so 'where' you commit your writes would be a moot point. Sharing LDAP caches like that doesn't work. You have to have either single-master or multi-master distribution. To my knowledge, no shipping product today (save perhaps one from M$, I can't remember offhand) supports multi-master replication. Which means that all writes to *any* LDAP replica in the network get a `pointer' back to the `master' LDAP server (sort of like a HTTP redirect) which is where the write is comitted, then replicated out to the other servers. > If you are going to use this for a password database (I think that was > your use) then why do you think writes will be so significant? (just > curious). There are sometimes requirements in ISPs to support rapid updates of large numbers of users in a short period of time. So commit time, and also distribution time, become critical. > Our use is for username/location,phone number,email address lookups - > which I beleive is probably the most frequent use of LDAP in a commercial > environment. That environment is extremely stable - very little change > occurs. I agree. MIS shops should love LDAP. I think there should be an alternative for ISPs, which is more tailored for their needs. 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 Wed Dec 30 16:40:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24760 for freebsd-current-outgoing; Wed, 30 Dec 1998 16:40:16 -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 QAA24668 for ; Wed, 30 Dec 1998 16:39:48 -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 LAA10815; Thu, 31 Dec 1998 11:08:31 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA38779; Thu, 31 Dec 1998 11:08:32 +1030 (CST) Message-ID: <19981231110831.E32696@freebie.lemis.com> Date: Thu, 31 Dec 1998 11:08:31 +1030 From: Greg Lehey To: Alex Le Heux , FreeBSD current users Subject: Re: How do I build an a.out kld? References: <8069.914964398@zippy.cdrom.com> <3689595A.F554B158@funk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <3689595A.F554B158@funk.org>; from Alex Le Heux on Tue, Dec 29, 1998 at 11:36:10PM +0100 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 On Tuesday, 29 December 1998 at 23:36:10 +0100, Alex Le Heux wrote: > [various things about booting freebsd cut] > > Is there a detailed description of the current bootprocess available > anywhere? Something that tells me exactly which bits go where and why? Good question. The answer should be ``boot(8)'', but it isn't. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 16:40:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24846 for freebsd-current-outgoing; Wed, 30 Dec 1998 16:40:32 -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 QAA24828 for ; Wed, 30 Dec 1998 16:40:27 -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 TAA29077; Wed, 30 Dec 1998 19:39:56 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 cc: "Steven P. Donegan" , Christian Kuhtz , Mike Smith , Josh Tiefenbach , The Hermit Hacker , freebsd-current@FreeBSD.ORG From: "Gary Palmer" Subject: Re: NOW/MOSIX/Beowulf In-reply-to: Your message of "Wed, 30 Dec 1998 19:34:36 EST." <28977.915064476@gjp.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 19:39:56 -0500 Message-ID: <29073.915064796@gjp.erols.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Gary Palmer" wrote in message ID <28977.915064476@gjp.erols.com>: > "Steven P. Donegan" wrote in message ID > : > > The farm of FreeBSD front ends would talk to an NFS backend (like a > > Network Appliance) so 'where' you commit your writes would be a moot point. > > Sharing LDAP caches like that doesn't work. Whoops. Guess I should say a bit more about *why* shouldn't I? If you think about it, each LDAP `replica' (even if they share the same DBM backend over NFS, and you could find an LDAP server which supported read-only operation like that), you still could run into troubles. Since each replica has in-core state about the file, have differet replicas write different updates to different parts of the file could lead to some interesting results ... even with good file/record locking, I think that is a path full of risk. 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 Wed Dec 30 16:56:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26303 for freebsd-current-outgoing; Wed, 30 Dec 1998 16:56:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26292; Wed, 30 Dec 1998 16:56:28 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id TAA25946; Wed, 30 Dec 1998 19:55:30 -0500 (EST) Message-ID: <19981230195530.J828@ns1.adsu.bellsouth.com> Date: Wed, 30 Dec 1998 19:55:30 -0500 From: Christian Kuhtz To: Gary Palmer , "Steven P. Donegan" Cc: Mike Smith , Josh Tiefenbach , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: <28977.915064476@gjp.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <28977.915064476@gjp.erols.com>; from Gary Palmer on Wed, Dec 30, 1998 at 07:34:36PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 30, 1998 at 07:34:36PM -0500, Gary Palmer wrote: > Sharing LDAP caches like that doesn't work. You have to have either > single-master or multi-master distribution. To my knowledge, no shipping > product today (save perhaps one from M$, I can't remember offhand) supports > multi-master replication. Which means that all writes to *any* LDAP replica in > the network get a `pointer' back to the `master' LDAP server (sort of like a > HTTP redirect) which is where the write is comitted, then replicated out to > the other servers. NetWare5 has been shipping production code since September '98 (NDS with LDAPv2 since much before then, and plain NDS even longer). In fact, Novell was the one who offered their multimaster technology to the IETF when LDAPv3 was standardized, and the IETF decided that it wasn't worth their trouble (a major blunder which I will never understand). NT5 is in beta2, and not expected to ship in volume until 2nd half of 1999 as Windows2000. NT5 beta2's AD is in unusable state, constantly blowing up and otherwise hideous. When we went to Microsoft to get an eval they said they needed to bring an 8 way PIIXeon in to show it off. Thanks, but no thanks. Take a serious look at NetWare5 if you're shopping for a fast scalable (and may I add proven) multimaster LDAP directory. I don't trust slides either. That's why I am beating the crap out of directories in the lab. Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 17:00:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA26807 for freebsd-current-outgoing; Wed, 30 Dec 1998 17:00:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA26801; Wed, 30 Dec 1998 17:00:42 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id UAA26014; Wed, 30 Dec 1998 20:00:22 -0500 (EST) Message-ID: <19981230200022.K828@ns1.adsu.bellsouth.com> Date: Wed, 30 Dec 1998 20:00:22 -0500 From: Christian Kuhtz To: Gary Palmer Cc: "Steven P. Donegan" , Mike Smith , Josh Tiefenbach , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: <28977.915064476@gjp.erols.com> <29073.915064796@gjp.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <29073.915064796@gjp.erols.com>; from Gary Palmer on Wed, Dec 30, 1998 at 07:39:56PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 30, 1998 at 07:39:56PM -0500, Gary Palmer wrote: > > Sharing LDAP caches like that doesn't work. > > Whoops. Guess I should say a bit more about *why* shouldn't I? > > If you think about it, each LDAP `replica' (even if they share the same DBM > backend over NFS, and you could find an LDAP server which supported read-only > operation like that), you still could run into troubles. Since each replica > has in-core state about the file, have differet replicas write different > updates to different parts of the file could lead to some interesting results > ... even with good file/record locking, I think that is a path full of risk. Gary is very much correct. That is why most vendors didn't want the IETF to implement multimaster, because their backend databases couldn't handle complex state maintenance (particularly Netscape's Berkeley DB based implementation). So, time to market was gained by sacrificing architecture, yielding a cute but unusable architecture for large scale deployment. A lot of the vendors use a Berkeley db (cute, but not really what we need) or an RDBMS (yuck). Directories are object databases, which is different from DB(M) or RDBMS. And also the reason why most implementations based on the latter suck. ;^) So, multimaster is tricky, unless you're running another multimaster directory technology underneath and LDAP becomes little more than an 'API'. Nothing wrong with that, I might add. Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 17:09:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27695 for freebsd-current-outgoing; Wed, 30 Dec 1998 17:09:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA27688; Wed, 30 Dec 1998 17:09:54 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id UAA26119; Wed, 30 Dec 1998 20:09:34 -0500 (EST) Message-ID: <19981230200933.L828@ns1.adsu.bellsouth.com> Date: Wed, 30 Dec 1998 20:09:33 -0500 From: Christian Kuhtz To: Gary Palmer , "Steven P. Donegan" Cc: Mike Smith , Josh Tiefenbach , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: <28977.915064476@gjp.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <28977.915064476@gjp.erols.com>; from Gary Palmer on Wed, Dec 30, 1998 at 07:34:36PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 30, 1998 at 07:34:36PM -0500, Gary Palmer wrote: > There are sometimes requirements in ISPs to support rapid updates of large > numbers of users in a short period of time. So commit time, and also > distribution time, become critical. This is precisely what we were struggling with. > I agree. MIS shops should love LDAP. I think there should be an alternative > for ISPs, which is more tailored for their needs. SPs need multimaster directories for one thing. They need highly sophisticated convergence mechanisms. This is neccessary since network topologies do get fragmented at times and when they come back together, I would like a warm quick welcome thrashing instead of a lengthy, thrashing convergence. Further, I need to be able to make changes from multiple places during these fragementation times, because I have multiple Ops centers across a given area, and when a CSR answers a call and needs to make a change to a customer profile, they need to be able to make that change. Regardless of whether the network is converged yet or not. I need information to be available everywhere (if desired) in form of a local copy. When you start thinking about keeping things like E911 info in a directory, the thing MUST NOT go down. EVER. Multimaster helps. The neat side effects are: You never need to back anything up, because as long as one complete copy survives somewhere, it will always redistribute itself automagically. All in all, non-trivial, but solvable. Having the right software widget in your hands helps. Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 17:10:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27970 for freebsd-current-outgoing; Wed, 30 Dec 1998 17:10:08 -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 RAA27901 for ; Wed, 30 Dec 1998 17:10:06 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 10552 invoked by uid 1001); 31 Dec 1998 01:09:44 +0000 (GMT) To: gallatin@cs.duke.edu Cc: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf In-Reply-To: Your message of "Wed, 30 Dec 1998 18:31:28 -0500 (EST)" References: <13962.46346.872709.715074@grasshopper.cs.duke.edu> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 31 Dec 1998 02:09:44 +0100 Message-ID: <10550.915066584@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is rather off topic, but does anybody know what the cheapest > route to a 64-bit PCI slot on an Intel platform is? I know the 450NX > chipset supports 64-bit PCI, but the last time I checked, machines > using the 450NX chipset were only available in high-margin servers > from Dell. Does anybody know of any 3rd-party x86 motherboard that > has a 64-bit slot? Micron Powerdigm XSU has a 64 bit PCI slot, see http://www.zdnet.com/products/content/pcmg/1704/269178.html for some info. (No recommendation - I have no experience with this system.) As far as I know, you can't buy the motherboard only. 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 Wed Dec 30 17:17:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28354 for freebsd-current-outgoing; Wed, 30 Dec 1998 17:17:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28347; Wed, 30 Dec 1998 17:17:05 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id UAA26206; Wed, 30 Dec 1998 20:16:45 -0500 (EST) Message-ID: <19981230201645.M828@ns1.adsu.bellsouth.com> Date: Wed, 30 Dec 1998 20:16:45 -0500 From: Christian Kuhtz To: Gary Palmer , "Steven P. Donegan" Cc: Mike Smith , Josh Tiefenbach , The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: <28835.915063913@gjp.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <28835.915063913@gjp.erols.com>; from Gary Palmer on Wed, Dec 30, 1998 at 07:25:13PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 30, 1998 at 07:25:13PM -0500, Gary Palmer wrote: > "Steven P. Donegan" wrote in message ID > : > > I 'vampired' my corporate LDAP directory (roughly 15k entries) and > > populated a FreeBSD and Netscape system with it (FreeBSD was the ldap in > > the ports directory). Both systems were basically identical as far as > > hardware goes. The FreeBSD response to queries was roughly twice as fast > > as the Netscape under NT. Since the database was very small (5 meg or so) > > I would see no reason why this couldn't scale indefinitely... (round > > robin DNS or Cisco load director etc.). > > In my application (ISP), the point of any network based information system > (i.e. LDAP) is to provide local caches of information on the machines which > need them, with near-real-time updates, so users can get near-instant password > changes across 20+ machines, new accounts created before they hang up, etc. Try customer bases with millions of users making changes to their accounts (either passively by using their accounts or actively through a CSR or customer account self management). This might include a customers session count, billing preferences, CoS categories, geographic info. And whatever else you can think of. This goes for service offerings such as plain old dial-up access, VoX (X=IP,ATM,FR) or whatever else, such a E911 info to be fed back into an IP/SS7 SCP. I am scared of keeping real time account info in it because this will take away transaction cycles from other (more vital?) tasks, with the concern that by the time the real time info actually propagates, it no longer is real time. Cheers, Chris -- Frisbeetarianism, n.: The belief that when you die, your soul goes up on the roof and gets stuck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 17:43:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA01086 for freebsd-current-outgoing; Wed, 30 Dec 1998 17:43:36 -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 RAA01075 for ; Wed, 30 Dec 1998 17:43:25 -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 RAA11036 for ; Wed, 30 Dec 1998 17:39:06 -0800 (PST) Date: Wed, 30 Dec 1998 17:39:06 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: New aout-to-elf build failures. 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 Another day, another no workee. :) building shared curses library (version 2) ===> libdevstat cc -O -pipe -I/usr/src/lib/libdevstat -I/usr/src/lib/libdevstat/../../sys -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdevstat/devstat.c -o devstat.o building standard devstat library ranlib libdevstat.a cc -fpic -DPIC -O -pipe -I/usr/src/lib/libdevstat -I/usr/src/lib/libdevstat/../../sys -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdevstat/devstat.c -o devstat.so building shared devstat library (version 2) ===> libdisk cc -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdisk/blocks.c -o blocks.o cc -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdisk/disklabel.c -o disklabel.o cc -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdisk/../../sbin/disklabel/dkcksum.c -o dkcksum.o cc -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdisk/chunk.c -o chunk.o cc -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdisk/disk.c -o disk.o /usr/src/lib/libdisk/disk.c:55: warning: `Write_Int32' defined but not used cc -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdisk/change.c -o change.o cc -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdisk/create_chunk.c -o create_chunk.o cc -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdisk/rules.c -o rules.o cc -O -pipe -Wall -I/usr/obj/elf/usr/src/tmp/usr/include -c /usr/src/lib/libdisk/write_disk.c -o write_disk.o make: don't know how to make /boot/boot1. Stop *** Error code 2 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 Wed Dec 30 18:11:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03922 for freebsd-current-outgoing; Wed, 30 Dec 1998 18:11:14 -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 SAA03917 for ; Wed, 30 Dec 1998 18:11:11 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id NAA24128; Thu, 31 Dec 1998 13:14:07 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199812310214.NAA24128@cimlogic.com.au> Subject: Re: New aout-to-elf build failures. In-Reply-To: from Jaye Mathisen at "Dec 30, 98 05:39:06 pm" To: mrcpu@internetcds.com (Jaye Mathisen) Date: Thu, 31 Dec 1998 13:14:07 +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 Jaye Mathisen wrote: > > > Another day, another no workee. :) People aren't sufficiently committed to keeping the upgrade process in working order. It's now broken in several ways. Looks like a binary upgrade is the only feasible option. Sigh. -- 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 30 18:23:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05403 for freebsd-current-outgoing; Wed, 30 Dec 1998 18:23:23 -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 SAA05393 for ; Wed, 30 Dec 1998 18:23:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id SAA13304; Wed, 30 Dec 1998 18:22:53 -0800 (PST) To: John Birrell cc: mrcpu@internetcds.com (Jaye Mathisen), current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-reply-to: Your message of "Thu, 31 Dec 1998 13:14:07 +1100." <199812310214.NAA24128@cimlogic.com.au> Date: Wed, 30 Dec 1998 18:22:53 -0800 Message-ID: <13301.915070973@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > People aren't sufficiently committed to keeping the upgrade process in > working order. It's now broken in several ways. Looks like a binary > upgrade is the only feasible option. Sigh. Sorry, I wasn't fully cognizant of the woes caused by missing things in /boot with a.out only systems. Seems I "broke" both libdisk and disklabel in the process, but this only underscores an important point which I've already made to core, and that's that we can't really stay "dual headed" like this for much longer if we don't wish to slowly accumulate cruft which is there for no other purpose than to keep 3.0/a.out systems alive. On January 6th, I think we're going to throw the switch completely to ELF and start recommending certain procedures to existing -current folks who haven't willingly crossed the divide yet. I would of course love to see the aout-to-elf target continue to work in this migration process but I can only go after the /boot problems, which I have a few ideas on (mostly copying stuff into there on a.out systems using the contents of /usr/mdec). If more than this is broken, I suggest tugging on the sleeves of those responsible and asking them how we're going to get everyone forcefully migrated to ELF on the 6th of Jan if there's no real mechanism for the -current folks to do 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 30 18:26:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05591 for freebsd-current-outgoing; Wed, 30 Dec 1998 18:26:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (pm35-20.image.dk [194.234.182.148]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA05574 for ; Wed, 30 Dec 1998 18:25:59 -0800 (PST) (envelope-from root@swimsuit.internet.dk) Received: from gina.swimsuit.internet.dk (gina.swimsuit.internet.dk [192.168.0.14]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id BAA79003 for ; Thu, 31 Dec 1998 01:45:12 +0100 (CET) (envelope-from root@swimsuit.internet.dk) Date: Thu, 31 Dec 1998 01:45:12 +0100 (CET) From: Leif Neland To: current@FreeBSD.ORG Subject: Upgrading slave Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running current on "master", a pentium II, and want to uprade "slave", a 486 to the same level. It also runs 3.0, but a few weeks earlier. I have done make world on "master", and then did mount_nfs master:/usr/src /usr/src mount_nfs master:/usr/obj /usr/obj cd /usr/src make installworld However, it fails: ===> include/rpcsvc install -C -o root -g wheel -m 444 /usr/src/include/rpcsvc/yp_prot.h /usr/src/include/rpcsvc/ypclnt.h /usr/src/include/rpcsvc/nis_db.h /usr/src/include/rpcsvc/nis_tags.h /usr/src/include/rpcsvc/nislib.h /usr/src/include/rpcsvc/bootparam_prot.x /usr/src/include/rpcsvc/key_prot.x /usr/src/include/rpcsvc/klm_prot.x /usr/src/include/rpcsvc/mount.x /usr/src/include/rpcsvc/nfs_prot.x /usr/src/include/rpcsvc/nlm_prot.x /usr/src/include/rpcsvc/rex.x /usr/src/include/rpcsvc/rnusers.x /usr/src/include/rpcsvc/rquota.x /usr/src/include/rpcsvc/rstat.x /usr/src/include/rpcsvc/rwall.x /usr/src/include/rpcsvc/sm_inter.x /usr/src/include/rpcsvc/spray.x /usr/src/include/rpcsvc/yppasswd.x /usr/src/include/rpcsvc/yp.x /usr/src/include/rpcsvc/ypxfrd.x /usr/src/include/rpcsvc/ypupdate_prot.x /usr/src/include/rpcsvc/nis.x /usr/src/include/rpcsvc/nis_cache.x /usr/src/include/rpcsvc/nis_object.x /usr/src/include/rpcsvc/nis_callback.x /usr/src/include/rpcsvc/crypt.x key_prot.h klm_prot.h mount.h nfs! _prot.h nlm_prot.h rex.h rnusers.h rquota.h rstat.h rwall.h sm_inter.h spray.h yppasswd.h yp.h ypxfrd.h ypupdate_prot.h nis.h nis_cache.h nis_callback.h bootparam_prot.h crypt.h /usr/include/rpcsvc install -C -o root -g wheel -m 444 key_prot.h /usr/include/rpc ===> lib ===> lib/csu/i386-elf install -c -o root -g wheel -m 444 crt1.o /usr/lib/crt1.o install -c -o root -g wheel -m 444 crtbegin.o /usr/lib/crtbegin.o install -c -o root -g wheel -m 444 crtend.o /usr/lib/crtend.o install -c -o root -g wheel -m 444 crti.o /usr/lib/crti.o install -c -o root -g wheel -m 444 crtn.o /usr/lib/crtn.o install -c -o root -g wheel -m 444 gcrt1.o /usr/lib/gcrt1.o install -c -o root -g wheel -m 444 crtbegin.so /usr/lib/crtbeginS.o install -c -o root -g wheel -m 444 crtend.so /usr/lib/crtendS.o ===> lib/libcom_err install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/com_err.h /usr/include install -c -o root -g wheel -m 444 libcom_err.a /usr/lib install -c -o root -g wheel -m 444 libcom_err_p.a /usr/lib install: libcom_err_p.a: No such file or directory *** Error code 71 Stop. *** Error code 1 Script done on Thu Dec 31 01:29:04 1998 I have even in desperation done rdist -c /usr root@slave (it took a few hours), but it fails the same place. The kernel is out of sync, because I get "ps: proc size mismatch", but I can't seem to get it in sync, when installworld fails. I'd rather not do a make world on "slave", because it is a 486 with 8MB ram... I am a little hesitant to upgrade it, because I don't think I can use a VLB Adaptec in the newer motherboards... Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 19:15:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10534 for freebsd-current-outgoing; Wed, 30 Dec 1998 19:15:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10526 for ; Wed, 30 Dec 1998 19:15:00 -0800 (PST) (envelope-from root@swimsuit.internet.dk) Received: from gina.swimsuit.internet.dk (gina.swimsuit.internet.dk [192.168.0.14]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id EAA66146 for ; Thu, 31 Dec 1998 04:13:34 +0100 (CET) (envelope-from root@swimsuit.internet.dk) Date: Thu, 31 Dec 1998 04:13:34 +0100 (CET) From: Leif Neland To: current@FreeBSD.ORG Subject: Viewtop 3D Titan 4000 (Trio 3D) Palette error 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 When I return from X, or from the new "graphical" screensavers, the blue colours are gone, leaving a black/yellow instead of black/white. Cvsupped to latest current 3.0 Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 19:21:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11209 for freebsd-current-outgoing; Wed, 30 Dec 1998 19:21:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11116 for ; Wed, 30 Dec 1998 19:21:37 -0800 (PST) (envelope-from root@swimsuit.internet.dk) Received: from gina.swimsuit.internet.dk (gina.swimsuit.internet.dk [192.168.0.14]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id EAA73372 for ; Thu, 31 Dec 1998 04:19:14 +0100 (CET) (envelope-from root@swimsuit.internet.dk) Date: Thu, 31 Dec 1998 04:19:12 +0100 (CET) From: Leif Neland To: current@FreeBSD.ORG Subject: more ppp-troubles 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 the isdnmodem on the machine "slave". When I telnet to slave from master, and start ppp, the ppp chatting stops after the phonenumber is sent. No "expect CONNECT". If I then walk out to slave, I can see the CD-light on. If I instead start ppp from slave's console, the chatting continues normally with expecting CONNECT afte sending the phonenumber. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 19:25:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11564 for freebsd-current-outgoing; Wed, 30 Dec 1998 19:25:14 -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 TAA11559 for ; Wed, 30 Dec 1998 19:25:12 -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 TAA07814; Wed, 30 Dec 1998 19:24:33 -0800 (PST) Date: Wed, 30 Dec 1998 19:24:33 -0800 (PST) From: Chris Timmons To: John Birrell cc: Jaye Mathisen , current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-Reply-To: <199812310214.NAA24128@cimlogic.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 Well you can always use CVSup or CVS to go back to the bad old days of around 12-18-1998 or so, then it worked fine :) On Thu, 31 Dec 1998, John Birrell wrote: > Jaye Mathisen wrote: > > > > > > Another day, another no workee. :) > > People aren't sufficiently committed to keeping the upgrade process in > working order. It's now broken in several ways. Looks like a binary > upgrade is the only feasible option. Sigh. > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 19:28:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA11761 for freebsd-current-outgoing; Wed, 30 Dec 1998 19:28:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA11754 for ; Wed, 30 Dec 1998 19:28:16 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id WAA75355 for ; Wed, 30 Dec 1998 22:26:42 -0500 (EST) Date: Wed, 30 Dec 1998 22:26:42 -0500 (EST) From: Chuck Robey To: freebsd-current@FreeBSD.ORG Subject: groff 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'd like some advice here. I want everyone else to be able to use the same groff upgrades I've been using in my own academic papers, but I'm uncertain how to go about doing it. Let me give you the background first, then the question. mm refers to the memorandum macros (groff/mm), which are used in conjunction with groff for papers. There are other macro sets, like ms and man, but this deals with mm. mm is not written by James Clark, but he includes a version with groff, by agreement with mm's author. The version included with groff is 1.27, but the latest version of mm that I've been using is 1.29. The difference (the main difference that you'd notice) between 1.27 and 1.29 is with tables of contents that run more than one page. mm version 1.27 massacres them, adding a page with a single line in it, and it turns out unuseable TOCs. The fix in version 1.29 seems really well done, and believe me, I've exercised it pretty hard. (I could include a sample of code that makes this happen, but since it only occurs with papers with a TOC larger than one page, it'd have to be a somewhat large example. Write me if you want to see this, I can certainly oblige). pst has left dire instructions in the contrib/groff directory on how to upgrade groff, but he doesn't seem to have contemplated someone only wanting to upgrade one subdirectory (it's a one for one replacement of maybe 8 files). The changes are pretty large, so the diff would be bigger, I think, than just doing a remove on each old file, then an add on each new one, but this seems to go against those instruction left by pst. I asked here once before on this, more than 6 months ago, when I first wanted to make the change. I got no clear response. I know how to do an import, but when I've done that in the past, it's always been an import to a place that was currently empty; mm is there now, I want to replace it with mm. Could someone give me a hint as what a technically, and stylistically correct way to do this is? (After, please, taking a look at pst's groff/FREEBSD-upgrade file). (BTW, don't tell me to upgrade groff, it still has the old mm in it, and we've already got a recent version of groff in the tree. Groff doesn't need upgrading, just groff/mm). ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 19:32:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12215 for freebsd-current-outgoing; Wed, 30 Dec 1998 19:32:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from geocities.com (mail8.geocities.com [209.1.224.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12210 for ; Wed, 30 Dec 1998 19:32:08 -0800 (PST) (envelope-from bhaskin@geocities.com) Received: from brianjr (220R1.infinitecom.com [199.176.148.87] (may be forged)) by geocities.com (8.9.1/8.9.1) with SMTP id TAA08141; Wed, 30 Dec 1998 19:31:46 -0800 (PST) From: "Brian Haskin" To: "Jordan K. Hubbard" Cc: Subject: RE: New aout-to-elf build failures. Date: Wed, 30 Dec 1998 22:32:32 -0500 Message-ID: <000001be346e$3365a960$0b00000a@brianjr.haskin.org> 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: <13301.915070973@zippy.cdrom.com> X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Jordan K. Hubbard > Sent: Wednesday, December 30, 1998 9:23 PM > To: John Birrell > Cc: Jaye Mathisen; current@FreeBSD.ORG > Subject: Re: New aout-to-elf build failures. > [SNIP] > Seems I "broke" both libdisk and disklabel in the process, but this > only underscores an important point which I've already made to core, > and that's that we can't really stay "dual headed" like this for much > longer if we don't wish to slowly accumulate cruft which is there for > no other purpose than to keep 3.0/a.out systems alive. On January > 6th, I think we're going to throw the switch completely to ELF and > start recommending certain procedures to existing -current folks who > haven't willingly crossed the divide yet. > [SNIP] Ok, as I'm not and haven't done any of the work I certainly don't have any say, but just to add something that you might want to consider. I've been thinking that it would be nice if the aout to elf build would be supported till a little after the branch split. This would allow people following stable the option of source upgrades the whole way through. But maybe this adds to much "cruft" to the start of the new stable branch? Brian Haskin haskin@ptway.com Home page: http://www.geocities.com/ResearchTriangle/4333/ Always remember money is simply a level of indirection. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 20:30:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA17480 for freebsd-current-outgoing; Wed, 30 Dec 1998 20:30:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from Chuska.ConSys.COM (Chuska.ConSys.COM [209.141.107.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA17473 for ; Wed, 30 Dec 1998 20:30:49 -0800 (PST) (envelope-from rcarter@psf.Pinyon.ORG) Received: from psf.Pinyon.ORG (ip-17-112.prc.primenet.com [207.218.17.112]) by Chuska.ConSys.COM (8.9.1/8.9.1) with ESMTP id VAA04529; Wed, 30 Dec 1998 21:30:26 -0700 (MST) Received: from psf.Pinyon.ORG (localhost [127.0.0.1]) by psf.Pinyon.ORG (8.9.1/8.8.7) with ESMTP id UAA28368; Wed, 30 Dec 1998 20:54:01 -0700 (MST) Message-Id: <199812310354.UAA28368@psf.Pinyon.ORG> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jordan K. Hubbard" cc: John Birrell , mrcpu@internetcds.com (Jaye Mathisen), current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-reply-to: Your message of "Wed, 30 Dec 1998 18:22:53 PST." <13301.915070973@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 30 Dec 1998 20:54:00 -0700 From: "Russell L. Carter" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > People aren't sufficiently committed to keeping the upgrade process in > > working order. It's now broken in several ways. Looks like a binary > > upgrade is the only feasible option. Sigh. > [...] > > I would of course love to see the aout-to-elf target continue to work > in this migration process but I can only go after the /boot problems, > which I have a few ideas on (mostly copying stuff into there on a.out > systems using the contents of /usr/mdec). If more than this is broken, > I suggest tugging on the sleeves of those responsible and asking them > how we're going to get everyone forcefully migrated to ELF on the 6th > of Jan if there's no real mechanism for the -current folks to do it. First: I agree with the sentiments entirely. Second: Why not start shouting now, with a HEADSUP storm converging on Jan 6 to get people off their butts? I started my aout-to-elf process on the three work systems I maintain for orthogonal reasons, but it has still taken a couple of weeks (as a background process) to move three operational systems providing important (but not mission critical) services more or less transparently to elf. Including sorting through the aout-vs-elf bugs which are the start of this thread. It's another danes with axes kinda problem, and communication helps. Ignore the whiners who would rather type than switch. Russell > > - Jordan > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 20:44:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18328 for freebsd-current-outgoing; Wed, 30 Dec 1998 20:44:20 -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 UAA18309 for ; Wed, 30 Dec 1998 20:44:13 -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 UAA11914; Wed, 30 Dec 1998 20:39:34 -0800 (PST) Date: Wed, 30 Dec 1998 20:39:33 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: "Russell L. Carter" cc: "Jordan K. Hubbard" , John Birrell , current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-Reply-To: <199812310354.UAA28368@psf.Pinyon.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 I don't dispute any of this, as long as when all is said and done, there is a relatively simple way for people to upgrade from 2.2.x to 3.0-pickyourflavor. Failure to provide this mechanism seems counter productive. However, there are a lot of 3.x systems out there that need updating, and the existing tools don't work... On Wed, 30 Dec 1998, Russell L. Carter wrote: > > > People aren't sufficiently committed to keeping the upgrade process in > > > working order. It's now broken in several ways. Looks like a binary > > > upgrade is the only feasible option. Sigh. > > > > [...] > > > > > I would of course love to see the aout-to-elf target continue to work > > in this migration process but I can only go after the /boot problems, > > which I have a few ideas on (mostly copying stuff into there on a.out > > systems using the contents of /usr/mdec). If more than this is broken, > > I suggest tugging on the sleeves of those responsible and asking them > > how we're going to get everyone forcefully migrated to ELF on the 6th > > of Jan if there's no real mechanism for the -current folks to do it. > > First: I agree with the sentiments entirely. Second: Why not start > shouting now, with a HEADSUP storm converging on Jan 6 to get people > off their butts? I started my aout-to-elf process on the three work > systems I maintain for orthogonal reasons, but it has still taken > a couple of weeks (as a background process) > to move three operational systems providing important > (but not mission critical) services more or less transparently to > elf. Including sorting through the aout-vs-elf bugs which are > the start of this thread. > > It's another danes with axes kinda problem, and communication helps. > Ignore the whiners who would rather type than switch. > > Russell > > > > > > > - Jordan > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 20:57:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA19123 for freebsd-current-outgoing; Wed, 30 Dec 1998 20:57: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 UAA19118 for ; Wed, 30 Dec 1998 20:57: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 AAA37799; Thu, 31 Dec 1998 00:00:51 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 31 Dec 1998 00:00:51 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: "Jordan K. Hubbard" cc: current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 30 Dec 1998, Jaye Mathisen wrote: > > I don't dispute any of this, as long as when all is said and done, there > is a relatively simple way for people to upgrade from 2.2.x to > 3.0-pickyourflavor. > > Failure to provide this mechanism seems counter productive. > > However, there are a lot of 3.x systems out there that need updating, and > the existing tools don't work... If you are tracking -current then you _should_ be tracking -current, not current-aout-noncam-etc, the project shouldn't suffer so that everyone who've been, uh scratching themselves, :) can upgrade. It's been some number of months now, people should either do it now (build) or smash it later (clobber install via sysinstall) I'm sure many commiters would love not to have to walk on eggshells anymore to avoid breaking the pecarious (sp) build tree that has been effective for the last 2(?) months. One important thing, obviously keeping around a X11 and system aout lib package should definetly be done for legacy binary only programs. (just a binary snap to instal via sysinstall/ports) :) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 21:00:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA19501 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:00:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA19496 for ; Wed, 30 Dec 1998 21:00:16 -0800 (PST) (envelope-from girgen@partitur.se) Received: from partitur.se (balalaika.partitur.se [193.219.246.232]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id FAA11084; Thu, 31 Dec 1998 05:58:35 +0100 (CET) (envelope-from girgen@partitur.se) Message-ID: <368B047B.B4FE92B1@partitur.se> Date: Thu, 31 Dec 1998 05:58:35 +0100 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Leif Neland CC: current@FreeBSD.ORG Subject: Re: Upgrading slave References: 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 saw this. I had: NOPROFILE= true in make.conf, but only one master machine. Putting it on the slave fixes it (libblahblah_p.a is the profiled library) HTH /Palle Leif Neland wrote: > > I'm running current on "master", a pentium II, and want to uprade "slave", > a 486 to the same level. It also runs 3.0, but a few weeks earlier. > > I have done make world on "master", and then did > mount_nfs master:/usr/src /usr/src > mount_nfs master:/usr/obj /usr/obj > cd /usr/src > make installworld > > However, it fails: > > ===> include/rpcsvc > install -C -o root -g wheel -m 444 /usr/src/include/rpcsvc/yp_prot.h /usr/src/include/rpcsvc/ypclnt.h /usr/src/include/rpcsvc/nis_db.h /usr/src/include/rpcsvc/nis_tags.h /usr/src/include/rpcsvc/nislib.h /usr/src/include/rpcsvc/bootparam_prot.x /usr/src/include/rpcsvc/key_prot.x /usr/src/include/rpcsvc/klm_prot.x /usr/src/include/rpcsvc/mount.x /usr/src/include/rpcsvc/nfs_prot.x /usr/src/include/rpcsvc/nlm_prot.x /usr/src/include/rpcsvc/rex.x /usr/src/include/rpcsvc/rnusers.x /usr/src/include/rpcsvc/rquota.x /usr/src/include/rpcsvc/rstat.x /usr/src/include/rpcsvc/rwall.x /usr/src/include/rpcsvc/sm_inter.x /usr/src/include/rpcsvc/spray.x /usr/src/include/rpcsvc/yppasswd.x /usr/src/include/rpcsvc/yp.x /usr/src/include/rpcsvc/ypxfrd.x /usr/src/include/rpcsvc/ypupdate_prot.x /usr/src/include/rpcsvc/nis.x /usr/src/include/rpcsvc/nis_cache.x /usr/src/include/rpcsvc/nis_object.x /usr/src/include/rpcsvc/nis_callback.x /usr/src/include/rpcsvc/crypt.x key_prot.h klm_prot.h mount.h n! fs! > _prot.h nlm_prot.h rex.h rnusers.h rquota.h rstat.h rwall.h sm_inter.h spray.h yppasswd.h yp.h ypxfrd.h ypupdate_prot.h nis.h nis_cache.h nis_callback.h bootparam_prot.h crypt.h /usr/include/rpcsvc > install -C -o root -g wheel -m 444 key_prot.h /usr/include/rpc > ===> lib > ===> lib/csu/i386-elf > install -c -o root -g wheel -m 444 crt1.o /usr/lib/crt1.o > install -c -o root -g wheel -m 444 crtbegin.o /usr/lib/crtbegin.o > install -c -o root -g wheel -m 444 crtend.o /usr/lib/crtend.o > install -c -o root -g wheel -m 444 crti.o /usr/lib/crti.o > install -c -o root -g wheel -m 444 crtn.o /usr/lib/crtn.o > install -c -o root -g wheel -m 444 gcrt1.o /usr/lib/gcrt1.o > install -c -o root -g wheel -m 444 crtbegin.so /usr/lib/crtbeginS.o > install -c -o root -g wheel -m 444 crtend.so /usr/lib/crtendS.o > ===> lib/libcom_err > install -C -o root -g wheel -m 444 /usr/src/lib/libcom_err/com_err.h /usr/include > install -c -o root -g wheel -m 444 libcom_err.a /usr/lib > install -c -o root -g wheel -m 444 libcom_err_p.a /usr/lib > install: libcom_err_p.a: No such file or directory > *** Error code 71 > > Stop. > *** Error code 1 > > Script done on Thu Dec 31 01:29:04 1998 > > I have even in desperation done > rdist -c /usr root@slave (it took a few hours), but it fails the same > place. > > The kernel is out of sync, because I get "ps: proc size mismatch", but I > can't seem to get it in sync, when installworld fails. > > I'd rather not do a make world on "slave", because it is a 486 with 8MB > ram... I am a little hesitant to upgrade it, because I don't think I can > use a VLB Adaptec in the newer motherboards... > > Leif > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 21:11:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20489 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:11: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 VAA20484 for ; Wed, 30 Dec 1998 21:11:40 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA14247; Wed, 30 Dec 1998 21:11:23 -0800 (PST) To: "Brian Haskin" cc: current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-reply-to: Your message of "Wed, 30 Dec 1998 22:32:32 EST." <000001be346e$3365a960$0b00000a@brianjr.haskin.org> Date: Wed, 30 Dec 1998 21:11:22 -0800 Message-ID: <14243.915081082@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok, as I'm not and haven't done any of the work I certainly don't have any > say, but just to add something that you might want to consider. I've been > thinking that it would be nice if the aout to elf build would be supported > till a little after the branch split. This would allow people following > stable the option of source upgrades the whole way through. But maybe this > adds to much "cruft" to the start of the new stable branch? I don't mind them following -current up to and after the branch, but they need to go ELF before that. It's just getting too difficult to support both worlds and I no longer even have a 3.0/a.out box handy here for testing such an environment. - 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 30 21:11:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20719 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:11:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa15-47.ix.netcom.com [207.93.148.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20362 for ; Wed, 30 Dec 1998 21:09:29 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id VAA18502; Wed, 30 Dec 1998 21:05:39 -0800 (PST) (envelope-from tomdean) Date: Wed, 30 Dec 1998 21:05:39 -0800 (PST) Message-Id: <199812310505.VAA18502@ix.netcom.com> From: Thomas Dean To: current@FreeBSD.ORG Subject: Prospects for fixing aout-to-elf build? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been watching this thread with interest. I have an SMP system that I want to upgrade to ELF, when the process appears to work. This system is not a mission-critical one, but, I would like to keep it working. I have been dragging my feet, waiting for ports, etc. Will the aout-to-elf upgrade process be fixed? tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 21:13:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20852 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:13: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 VAA20844 for ; Wed, 30 Dec 1998 21:13:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA14279; Wed, 30 Dec 1998 21:13:17 -0800 (PST) To: "Russell L. Carter" cc: John Birrell , mrcpu@internetcds.com (Jaye Mathisen), current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-reply-to: Your message of "Wed, 30 Dec 1998 20:54:00 MST." <199812310354.UAA28368@psf.Pinyon.ORG> Date: Wed, 30 Dec 1998 21:13:17 -0800 Message-ID: <14276.915081197@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > First: I agree with the sentiments entirely. Second: Why not start > shouting now, with a HEADSUP storm converging on Jan 6 to get people > off their butts? I started my aout-to-elf process on the three work OK, starting now: HEADS UP! -current will going exclusively to ELF on January 6th, 1999! Install those new boot blocks now, before it becomes even more imperative! :-) - 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 30 21:17:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21144 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:17:00 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cbgw1.lucent.com (cbgw1.lucent.com [207.24.196.51]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id VAA21139 for ; Wed, 30 Dec 1998 21:16:58 -0800 (PST) (envelope-from dmobrien@cbgw1.lucent.com) Cc: Eric Chet Received: from llama.bazzle.com by cbig1.firewall.lucent.com (SMI-8.6/EMS-L sol2) id AAA24164; Thu, 31 Dec 1998 00:13:55 -0500 Received: from localhost (dob@localhost) by llama.bazzle.com (8.8.8/8.6.12) with SMTP id AAA14363; Thu, 31 Dec 1998 00:16:27 -0500 (EST) X-Authentication-Warning: llama.bazzle.com: dob owned process doing -bs Date: Thu, 31 Dec 1998 00:16:25 -0500 (EST) From: "Dan O'Brien" X-Sender: dmobrien@localhost To: current@FreeBSD.ORG Original-cc: Eric Chet Subject: current buildworld supped today failed in libdisk In-Reply-To: <199812281827.KAA29541@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A buildworld of current supped (12/30 EST) failed in libdisk. I'm a little out of day (June 12) and wanted to "catch up". cc -O -malign-loops=2 -malign-jumps=2 -malign-functions=2 -pipe -Wall -I/usr/obj/aout/usr/src/tmp/usr/include -c /usr/src/lib/libdisk/write_disk.c -o write_disk.o make: don't know how to make /boot/boot1. Stop *** Error code 2 Looks like /usr/src/lib/libdisk/Makefile is looking for /boot/boot1 and /boot/boot2, but I have neither of these on my system. I searched www.freebsd.org for some insight but didn't find anything specific. There was a lot of discussion a few months back about /boot, but I wasn't paying attention (sorry, was busy with other stuff). How do I get past this chicken/egg thing? Copy /usr/mdec/boot[12] to /boot? (I'm still an aout system.) Thanks, Dan O'Brien Work: 614-860-2392 Page: 614-520-5001 Home: 740-927-2178 Home2: 740-927-2955 ---------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 21:25:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21743 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:25:56 -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 VAA21738 for ; Wed, 30 Dec 1998 21:25:53 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id QAA06547 for ; Thu, 31 Dec 1998 16:25:32 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd006544; Thu Dec 31 05:25:28 1998 Received: from lightning (lightning.itga.com.au [192.168.71.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id QAA20771 for ; Thu, 31 Dec 1998 16:25:58 +1100 (EST) Message-Id: <199812310525.QAA20771@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: SMC EtherEZ PnP Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Dec 1998 16:25:26 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG G'day. I've got an SMC EtherEZ 8416 PnP card in an oldish P-100 system with a PnP BIOS. Neither the GENERIC kernel nor the boot floppy nor any kernel I can compile recognise this card. AFAICT from the mail list archives, this card (in a non-PnP version) should be supported by the ed driver. There are no jumpers or anything to turn off Prug-n-pray or to set ports/irqs etc. [As an aside: is there some easy way of mapping ethernet card or chipset to driver name without "just knowing"?!?] What do I need to do to get this going? I'm interested in aquiring a deeper understanding, not just a fix-up! (The PnP Soundblaster probed fine using the pcm driver, tho.) [As an aside #2, where is a good spot to look for general PnP info? The pnp man page assumes you already know enough about PnP to know what CSN and LDNs etc are and how to determine them for your system.] I tried editing if_ed.c to add the correct PnP id to the ed_pnpids struct, but at probe time I get the messages from boot -v: [...] vga0: rev 0x00 int a irq 12 on pci0.10.0 Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 PnP: CSN 2 COMP_DEVICE_ID = 0x0006d041 CSN 1 Vendor ID: SMC8416 [0x1684a34d] Serial 0xc95830c0 Comp ID: @@@0000 [0x00000000] port 0x0240 0x0000 0x0000 0x0000 irq 11:0 drq 0:0 en 1 port 0x0240 0x0000 0x0000 0x0000 irq 11:0 drq 0:0 en 1 ed1: Invalid ISA memory address range configured: 0x0 - 0x2000 ed1: probe failed ed1 (edpnp sn 0xc95830c0) failed to attach CSN 2 Vendor ID: CTL0024 [0x24008c0e] Serial 0x100904fe Comp ID: PNP0600 [0x0006d041] Called nullpnp_probe with tag 0x00000002, type 0x24008c0e Called nullpnp_probe with tag 0x00000002, type 0x0006d041 port 0x0220 0x0330 0x0388 0x0000 irq 5:0 drq 1:5 en 1 port 0x0220 0x0330 0x0388 0x0000 irq 5:0 drq 1:5 en 1 pcm1 (SB16pnp sn 0x100904fe) at 0x220-0x22f irq 5 drq 1 flags 0x15 on isa Probing for devices on the ISA bus: [...] which if I understand things means it found the right PnP id, but the PnP-derived config had 0 for a memory address.... No doubt Dave Greenman will jump in here -> TIA, Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 21:29:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22246 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:29:00 -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 VAA22240 for ; Wed, 30 Dec 1998 21:28: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 QAA05885; Thu, 31 Dec 1998 16:28:37 +1100 Date: Thu, 31 Dec 1998 16:28:37 +1100 From: Bruce Evans Message-Id: <199812310528.QAA05885@godzilla.zeta.org.au> To: current@FreeBSD.ORG, luigi@labinfo.iet.unipi.it Subject: Re: -DKERNEL option when compiling kernels ? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >i see that now -DKERNEL is the only define left in the command line, >most things being in opt_global.h > >Couldn't it also go into opt_global.h ? It could, but it doesn't belong there since it is not optional. 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 30 21:30:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22357 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:30:45 -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 VAA22352 for ; Wed, 30 Dec 1998 21:30:42 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id QAA06578 for ; Thu, 31 Dec 1998 16:30:22 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd006576; Thu Dec 31 05:30:20 1998 Received: from lightning (lightning.itga.com.au [192.168.71.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id QAA20816 for ; Thu, 31 Dec 1998 16:30:50 +1100 (EST) Message-Id: <199812310530.QAA20816@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-reply-to: Your message of Wed, 30 Dec 1998 21:13:17 -0800. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Dec 1998 16:30:18 +1100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, starting now: HEADS UP! -current will going exclusively to ELF > on January 6th, 1999! Install those new boot blocks now, before it > becomes even more imperative! :-) Erm, I joined -current from the 3.0R CDs. AFAI knew I -was- exclusively ELF, but seeing as I have the same old boot blocks as 2.2.6, I guess not. What do I have to do to go "exclusively to ELF" and "install those new boot blocks"? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 21:48:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA24241 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:48:27 -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 VAA24229 for ; Wed, 30 Dec 1998 21:48: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 0zvaxi-0007nP-00; Wed, 30 Dec 1998 22:47:58 -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 WAA00555; Wed, 30 Dec 1998 22:45:54 -0700 (MST) Message-Id: <199812310545.WAA00555@harmony.village.org> To: "Jordan K. Hubbard" Subject: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) Cc: current@FreeBSD.ORG In-reply-to: Your message of "Wed, 30 Dec 1998 21:13:17 PST." <14276.915081197@zippy.cdrom.com> References: <14276.915081197@zippy.cdrom.com> Date: Wed, 30 Dec 1998 22:45:53 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <14276.915081197@zippy.cdrom.com> "Jordan K. Hubbard" writes: : OK, starting now: HEADS UP! -current will going exclusively to ELF : on January 6th, 1999! Install those new boot blocks now, before it : becomes even more imperative! :-) Might not be a bad idea to have heads ups like this have a subject line more like the above, so people don't miss it so easily. Does this mean that we must be using ELF kernels by Jan 6? Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 21:54:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA25175 for freebsd-current-outgoing; Wed, 30 Dec 1998 21:54:32 -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 VAA25170 for ; Wed, 30 Dec 1998 21:54:28 -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 QAA11873; Thu, 31 Dec 1998 16:23:47 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA39520; Thu, 31 Dec 1998 16:23:52 +1030 (CST) Message-ID: <19981231162352.E32696@freebie.lemis.com> Date: Thu, 31 Dec 1998 16:23:52 +1030 From: Greg Lehey To: Warner Losh , "Jordan K. Hubbard" Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) References: <14276.915081197@zippy.cdrom.com> <199812310545.WAA00555@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812310545.WAA00555@harmony.village.org>; from Warner Losh on Wed, Dec 30, 1998 at 10:45:53PM -0700 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 On Wednesday, 30 December 1998 at 22:45:53 -0700, Warner Losh wrote: > In message <14276.915081197@zippy.cdrom.com> "Jordan K. Hubbard" writes: > : OK, starting now: HEADS UP! -current will going exclusively to ELF > : on January 6th, 1999! Install those new boot blocks now, before it > : becomes even more imperative! :-) > > Might not be a bad idea to have heads ups like this have a subject > line more like the above, so people don't miss it so easily. Indeed. Thanks, now I saw it. > Does this mean that we must be using ELF kernels by Jan 6? Well, after last weekend's axing, I suddenly find I'm there :-) Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 22:02:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25521 for freebsd-current-outgoing; Wed, 30 Dec 1998 22:02:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from lambic.physics.montana.edu (lambic.physics.montana.edu [153.90.192.128]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25515 for ; Wed, 30 Dec 1998 22:02:25 -0800 (PST) (envelope-from handy@lambic.physics.montana.edu) Received: from localhost (handy@localhost) by lambic.physics.montana.edu (8.8.8/8.8.7) with ESMTP id XAA16857; Wed, 30 Dec 1998 23:01:50 -0700 (MST) (envelope-from handy@lambic.physics.montana.edu) Date: Wed, 30 Dec 1998 23:01:50 -0700 (MST) From: Brian Handy To: Warner Losh cc: current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: <199812310545.WAA00555@harmony.village.org> Message-ID: X-files: The truth is out there MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Does this mean that we must be using ELF kernels by Jan 6? I started getting worked up over this about how I needed to get all my machines caught up (I run -STABLE all over the place here), then realized: hey, CVSup can be taught to grab a snapshot from any date I feel like. For those of us happy running -STABLE, I don't see any particular need to panic. When I have time and inclination, I'll probably bootstrap to some-date-in-the-last-half-of-December-that-worked and then make the jump to the new burgening -STABLE when the time's right for me. Calm...everyone, calm... Brian "That's my theory, anyway" Handy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 22:08:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA25952 for freebsd-current-outgoing; Wed, 30 Dec 1998 22:08:11 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA25947 for ; Wed, 30 Dec 1998 22:08:06 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id OAA89665; Thu, 31 Dec 1998 14:07:20 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812310607.OAA89665@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Warner Losh cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-reply-to: Your message of "Wed, 30 Dec 1998 22:45:53 MST." <199812310545.WAA00555@harmony.village.org> Date: Thu, 31 Dec 1998 14:07:19 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > In message <14276.915081197@zippy.cdrom.com> "Jordan K. Hubbard" writes: > : OK, starting now: HEADS UP! -current will going exclusively to ELF > : on January 6th, 1999! Install those new boot blocks now, before it > : becomes even more imperative! :-) > > Might not be a bad idea to have heads ups like this have a subject > line more like the above, so people don't miss it so easily. > > Does this mean that we must be using ELF kernels by Jan 6? > > Warner Well.. I think it'll be possibe to use a.out for a while, at least as long as there is a source-only upgrade path from a.out to elf, simply because there is an a.out buildworld and a.out upgrade kernel installed in the process. What will most likely happen is that the do-nothing option will be taken away. Note that some sort of a.out support will need to be buried in there as long as we try to support a source-only upgrade. Other options include a small binary toolchain "kit" to enable an elf 'make world' to work on an otherwise a.out system. It seems the cat is out of the bag now already.. I was trying to put together a more complete HEADS UP message, but it looks like I missed out by about 10 minutes. I'll attach a copy on the end. Hopefully it'll head off a few riots and pre-answer a heap of questions and concerns. BEWARE, I've attached it as-is, it's not complete, has not been run past people who should approve it, etc. Although it says that it's been decided, it hasn't been run past the people who are going to have to help make it work. Major showstoppers (referred to in the draft below) include things like Mafia hit squads hunting us down. :-] Sorry to drop this on folks like this, but we really do need to light a few fires under our collective backsides and get this over and done with. (All things being equal, the voxware/pcvt issue should be well and truely settled by then too. Lack of voxware/pcvt should not be an issue for jumping on board this when the time comes). Cheers, -Peter === INCOMPLETE DRAFT === The time to complete the ELF transition has come. More to the point, progress has stopped and there is no sign of things getting going and finishing off the remaining rough edges without a bit more of a shove. Please read this through carefully before getting out the flamethrowers or starting a reply. There are some known problems and rough edges still. They are not getting fixed because not enough of the *developers* are using it. Note that people installing 3.0-RELEASE get ELF by default, and 3.0.1 will have an ELF kernel too. We *need* to get the remaining developers (kicking and screaming if necessary) onto the bandwagon or the current outstanding problems are going to be present in 3.0.1 as well. The state of the ELF world today is that just about everything important works for just about everybody. Specifically: - The userland builds, installs and runs "just fine" as ELF, and has done so for a long time (I believe over a year). - a.out binaries and libraries work unmodified. There is no need to toss out /usr/local/bin. The libraries get moved to /usr/local/lib/aout so there are no naming conflicts and the ldconfig paths can handle this. - The kernel builds and runs as an ELF file. - /boot/loader can load static aout and elf kernels, as well as do KLD preloading for ELF. a.out and ELF kernels have had KLD enabled in them for over a month. - The new bootblocks default to /boot/loader, but there are some problems for some people still. This needs to be fixed, and either the new bootblocks need fixing or the old bootblocks need a cutdown and modified to fire up /boot/loader by default. - The new bootblocks can load an a.out and ELF /kernel directly without /boot/loader. (handy if you happen to break it or want to revert to /boot/loader.old :-). - KLD's work and are a superset of LKM's. You can build a.out and ELF KLD modules. You can load a.out KLD's on an ELF kernel and ELF KLD's on an a.out kernel without noticing the difference. In all, we're about as ready as we're ever going to be without getting more people bashing at the code. However, the problems and risks: - OLD bootblocks apparently cannot load /boot/loader. We do not yet know why. We need to know why and preferably what to change in /boot/loader's headers to make it work. This seems to affect only systems installed with 2.0.x, 2.1.x and early 2.2.x bootblocks that have never had them upgraded. - 'make aout-to-elf' is known to have a few bumps when coming from some versions of 2.2.x and some -current builds from the last few months. There are other ways of ELF bootstrapping if building the source proves too difficult or takes too much space. I personally have upgraded two machines by installing a new binary bindist and then doing a normal 'make world' on the now ELF system to clean up the loose ends and bring it up to date. I didn't have a.out binaries to worry about though. - currently existing a.out LKM's will be truely dead. This may be a problem for the one known 3rd party binary LKM, namely OSS. (No, we don't have something against sound drivers, in spite of what it looks like :-). - A 'make install' by an unwary -current user could install an ELF /kernel and strand themselves if they have got OLD bootblocks that cannot load /boot/loader, or if they do not know to just type "/boot/loader" at the boot: prompt to get out of the jam. The plan: January 6 becomes The Day. (E2-day? E-squared day? :-) On that day, 'make world' to build an a.out would will be blocked. Not destroyed, not removed, just blocked. I would like it to be sufficiently crippled so that it isn't too hard to get going again in an emergency or if somebody is really badly affected. Perhaps something like: 'make -DYES_I_KNOW_THIS_IS_ON_BORROWED_TIME world' or requiring the src/Makefile* file to be edited to remove the block. It would be a waste if 95% of people reflexively turned on a hook in /etc/make.conf out of laziness, resistance to change, whatever, if it's too easy to take the 'do nothing' option. People must then do a 'make aout-to-elf' or install an ELF binary dist or something. On the same day, the default kernel format would get changed to ELF.. People can do a 'echo /boot/loader > /boot.config' or install new bootblocks (disklabel -B da0 / wd0 etc). As insurance to try and avoid feet getting blown off and people getting stranded with unbootable systems, either use a small bootblock reader to check that new bootblocks are in place, or force the user to manually set a flag to signify that they have done something about the bootstrap issue. Barring any *really*major* showstoppers, this will go ahead in the early hours of January 6 (in the USA) and later in the day for the rest of the world due to timezone differences. What you can do right now: 1: Test the /boot/loader on your system from the boot: prompt to make sure it loads up and doesn't crash or reboot on the spot. 2: Prepare some emergency boot floppies *now* in case. Get the 3.0 boot and fixit floppies from CD or from ftp.freebsd.org. 3: Build a new floppy with the new bootblocks, new boot loader and see that it works on your system. To do this: 1: get a formatted floppy ready 2: disklabel -Brw -b /boot/boot1 -s /boot/boot2 /dev/rfd0.1440 fd1440 3: newfs -T fd1440 /dev/rfd0.1440 4: mount /dev/fd0.1440 /mnt 5: mkdir /mnt/boot 6: cp /boot/loader /mnt/boot/loader 7: cp /kernel /mnt/kernel 8: touch /mnt/boot/boot.conf 9: umount /mnt And try it out. You should see the "FreeBSD/i386 BOOT" message and a boot: prompt. It should initiate /boot/loader a few seconds later, and the 3rd stage loader should start. It should say "starting /kernel in 10 seconds" and do a countdown. If this works and it loads the kernel from floppy, then you are clear. (Yes, the kernel is expected to panic since it doesn't have a real rootfs or /sbin/init). You can abort the autostart and have a play around. You can do things like: set currdev=disk1s1a (hard disk root) load /kernel (your real kernel) boot -s (start in single user). You can also try typing "/kernel" at the first boot: prompt. You may also like to try building an ELF kernel (cd compile/FOO; make KERNFORMAT=elf depend; make KERNFORMAT=elf) and copy that somewhere that you can try it out. 4: If you are happy that the new bootblocks work, update your bootblocks on your hard disk. MAKE SURE YOU HAVE A FALLBACK IF YOU GET STRANDED! Ideally have the sysinstall boot/fixit floppy handy at all times. This is what a successful boot looks like using the new bootblocks and /boot/loader. (Yes, this kernel is a little old) >> FreeBSD/i386 BOOT Default: 0:da(0,a)/boot/loader boot: text=0x1000 data=0x1b000 bss=0x0 symbols=[+0x0] entry=0x100000 Console: serial port BIOS drive A: is disk0 BIOS drive C: is disk1 FreeBSD/i386 bootstrap loader, Revision 0.2 639/64512kB (root@beast.netplex.com.au, Fri Oct 16 23:15:13 WST 1998) > set bootfile=/kernel > autoboot 10 Hit [Enter] to boot immediately, or any other key for command prompt. Booting [/kernel] in 9 seconds... Booting [/kernel]... /kernel text=0xe1348 data=0x12994+0x1b9f0 syms=[0x4+0x191b0+0x4+0x14fa5] BIOS basemem: 639K, extmem: 64512K (from 0xe801 call) 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 #263: Sat Dec 5 18:29:39 WST 1998 peter@beast.netplex.com.au:/home/src/sys/compile/BEAST Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 67108864 (65536K bytes) config> quit avail memory = 62861312 (61388K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfec08000 cpu1 (AP): apic id: 12, version: 0x00040011, at 0xfec08000 io0 (APIC): apic id: 13, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xf0240000. Probing for devices on PCI bus 0: [..] Note the 'preloaded elf kernel' bit. This is the in-kernel linker (KLD) finding itself in the tables that the /boot/loader prepared for it. Finally.. Try a 'make aout-to-elf-build' and make sure it works. If it does, make sure you've backed up any critical data and try a 'make aout-to-elf-install' and see how you go. Note that on a pre-3.0 system you will need to convert your kernel config to 3.0 level and place it as src/sys/i386/conf/GENERICupgrade. copy plain GENERIC and start from that if necessary. Note that aout-to-elf will not install an ELF kernel for you. Just do one thing at a time and build an updated ELF kernel later. == END OF INCOMPLETE DRAFT == To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 22:10:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26285 for freebsd-current-outgoing; Wed, 30 Dec 1998 22:10:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26279 for ; Wed, 30 Dec 1998 22:10:38 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id WAA21574; Wed, 30 Dec 1998 22:10:12 -0800 (PST) Message-Id: <199812310610.WAA21574@implode.root.com> To: Gregory Bond cc: current@FreeBSD.ORG Subject: Re: SMC EtherEZ PnP In-reply-to: Your message of "Thu, 31 Dec 1998 16:25:26 +1100." <199812310525.QAA20771@melba.bby.com.au> From: David Greenman Reply-To: dg@root.com Date: Wed, 30 Dec 1998 22:10:12 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I've got an SMC EtherEZ 8416 PnP card in an oldish P-100 system with a PnP >BIOS. Neither the GENERIC kernel nor the boot floppy nor any kernel I can >compile recognise this card. AFAICT from the mail list archives, this card (in >a non-PnP version) should be supported by the ed driver. There are no jumpers >or anything to turn off Prug-n-pray or to set ports/irqs etc. > >[As an aside: is there some easy way of mapping ethernet card or chipset to >driver name without "just knowing"?!?] > >What do I need to do to get this going? I'm interested in aquiring a deeper >understanding, not just a fix-up! >port 0x0240 0x0000 0x0000 0x0000 irq 11:0 drq 0:0 en 1 >port 0x0240 0x0000 0x0000 0x0000 irq 11:0 drq 0:0 en 1 >ed1: Invalid ISA memory address range configured: 0x0 - 0x2000 >ed1: probe failed >ed1 (edpnp sn 0xc95830c0) failed to attach Well, the above looks like the setting for shared memory address isn't configured correctly in the kernel. What do you have for the "ed1" device in your kernel config file? -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 22:19:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA26795 for freebsd-current-outgoing; Wed, 30 Dec 1998 22:19:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp4.nwnexus.com (smtp4.nwnexus.com [206.63.63.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA26790 for ; Wed, 30 Dec 1998 22:19:08 -0800 (PST) (envelope-from wrsomsky@halcyon.com) Received: from gramarye (evt-lx101-ip44.nwnexus.net [204.57.235.94]) by smtp4.nwnexus.com (8.8.8/8.8.8) with ESMTP id WAA30988; Wed, 30 Dec 1998 22:18:41 -0800 (PST) Received: (from wrsomsky@localhost) by gramarye (8.9.1/8.8.8) id SAA00388; Sun, 20 Dec 1998 18:53:39 -0800 (PST) (envelope-from wrsomsky) Message-ID: <19981220185338.A363@halcyon.com> Date: Sun, 20 Dec 1998 18:53:38 -0800 From: "William R. Somsky" To: John Polstra , nwestfal@Vorlon.odc.net Cc: current@FreeBSD.ORG Subject: Re: syncing 3.0-src tree with current References: <199812170539.VAA21583@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812170539.VAA21583@vashon.polstra.com>; from John Polstra on Wed, Dec 16, 1998 at 09:39:36PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article , > Neal Westfall wrote: > > > Is there an easy way to get a 3.0 source tree up to current? I will be > > doing this with CTM. Can I start with my 3.0 source tree or do I need > > to wipe it out and start clean with the fat delta? I didn't see any > > info on how to do this without starting from an empty src dir. Can > > this be done? On Wed, Dec 16, 1998 at 09:39:36PM -0800, John Polstra replied: > > I'll let others answer about CTM. But you can do it with CVSup. The > technique is described in the CVSup FAQ, at: > > http://www.polstra.com/projects/freeware/CVSup/ I'll follow up with this comment: It's mentioned in the handbook that you may want to use CTM instead of CVSup if you're running dialup, but I've found that in practice, CVSup works quite well over a dialup line. I was running CVSup happily w/ a 28.8K modem for quite a while. Now, the first time you run, esp if you have a far-divergent, or even empty /usr/src, it may take several hours, but once you're in sync, it only takes approx 5-15 minutes each time if you update once a week or so. CVSup is also nice in that it will easily handle arbitrary file deletions/changes/manglations of your /usr/src, whereas CTM, I believe, gets out of sync if something like that happens. The one thing I wish CVSup had was a way for it to tell you when there are _extra_ files in /usr/src (or whatever it's syncing) that it's not touching. CVSup will, as I understand it, delete a file if it's got a record that it's the one that created it, but if you add an arbitrary file, it gets completely ignored by CVSup. However, I've written a perl script to list for me any files in the /usr/src tree that list any such files for me. (It's be nice if cvsup itself had an option for this built in though). ________________________________________________________________________ William R. Somsky wrsomsky@halcyon.com Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 22:33:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA28249 for freebsd-current-outgoing; Wed, 30 Dec 1998 22:33:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA28244 for ; Wed, 30 Dec 1998 22:33:42 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id RAA22050; Thu, 31 Dec 1998 17:03:20 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA18903; Thu, 31 Dec 1998 17:03:20 +1030 Date: Thu, 31 Dec 1998 17:03:19 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: "William R. Somsky" Cc: current@FreeBSD.ORG Subject: Re: syncing 3.0-src tree with current In-Reply-To: <19981220185338.A363@halcyon.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Dec 1998, William R. Somsky wrote: > The one thing I wish CVSup had was a way for it to tell you when > there are _extra_ files in /usr/src (or whatever it's syncing) that > it's not touching. CVSup will, as I understand it, delete a file > if it's got a record that it's the one that created it, but if you > add an arbitrary file, it gets completely ignored by CVSup. However, > I've written a perl script to list for me any files in the /usr/src > tree that list any such files for me. (It's be nice if cvsup itself > had an option for this built in though). I'd be interested to see this script - I'm sure I've got a ton of old crap in my source tree :-) Kris > ________________________________________________________________________ > William R. Somsky wrsomsky@halcyon.com > Physicist, Baritone, Guitarist http://www.halcyon.com/wrsomsky ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Dec 30 22:40:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29115 for freebsd-current-outgoing; Wed, 30 Dec 1998 22:40:49 -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 WAA29110 for ; Wed, 30 Dec 1998 22:40:45 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id AAA17413; Thu, 31 Dec 1998 00:56:40 -0500 (EST) Date: Thu, 31 Dec 1998 00:56:40 -0500 (EST) From: Daniel Eischen Message-Id: <199812310556.AAA17413@pcnet1.pcnet.com> To: imp@village.org, jkh@zippy.cdrom.com Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In message <14276.915081197@zippy.cdrom.com> "Jordan K. Hubbard" writes: > : OK, starting now: HEADS UP! -current will going exclusively to ELF > : on January 6th, 1999! Install those new boot blocks now, before it > : becomes even more imperative! :-) > > Might not be a bad idea to have heads ups like this have a subject > line more like the above, so people don't miss it so easily. > > Does this mean that we must be using ELF kernels by Jan 6? And if so, can we put something somewhere that tells us how to install the new boot blocks, what problems might be encountered in the process, etc? 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 Wed Dec 30 22:44:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA29561 for freebsd-current-outgoing; Wed, 30 Dec 1998 22:44:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA29556 for ; Wed, 30 Dec 1998 22:44:32 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id OAA89872; Thu, 31 Dec 1998 14:44:07 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812310644.OAA89872@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Gregory Bond cc: current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-reply-to: Your message of "Thu, 31 Dec 1998 16:30:18 +1100." <199812310530.QAA20816@melba.bby.com.au> Date: Thu, 31 Dec 1998 14:44:05 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gregory Bond wrote: > > OK, starting now: HEADS UP! -current will going exclusively to ELF > > on January 6th, 1999! Install those new boot blocks now, before it > > becomes even more imperative! :-) > > Erm, I joined -current from the 3.0R CDs. AFAI knew I -was- exclusively ELF, > but seeing as I have the same old boot blocks as 2.2.6, I guess not. > > What do I have to do to go "exclusively to ELF" and "install those new boot > blocks"? Not quite.. The 3.0 CD shipped with an ELF world, but an a.out kernel and 3.0-level a.out bootblocks. You should be able to type a "/boot/loader" at the boot prompt and be able to use the ELF-aware bootloader without any problems. Assuming this works, you can type: echo /boot/loader > /boot.config And you're elf kernel capable. To update your installed bootblocks, do this: disklabel -B wd0 (or da0, whatever). Although, make sure you have a fallback in case. :-) The boot/fixit floppy from the 3.0 CD should be fine. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 00:26:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA07873 for freebsd-current-outgoing; Thu, 31 Dec 1998 00:26:46 -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 AAA07868 for ; Thu, 31 Dec 1998 00:26:45 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id AAA14752; Thu, 31 Dec 1998 00:26:21 -0800 (PST) To: Brian Handy cc: Warner Losh , current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-reply-to: Your message of "Wed, 30 Dec 1998 23:01:50 MST." Date: Thu, 31 Dec 1998 00:26:20 -0800 Message-ID: <14748.915092780@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I started getting worked up over this about how I needed to get all my > machines caught up (I run -STABLE all over the place here), then realized: -stable people don't need to care about any of the above right now anyway. :-) - 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 31 01:21:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11082 for freebsd-current-outgoing; Thu, 31 Dec 1998 01:21:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.eecis.udel.edu (louie.udel.edu [128.175.2.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA11045; Thu, 31 Dec 1998 01:21:09 -0800 (PST) (envelope-from alexandr@mail.eecis.udel.edu) Date: Thu, 31 Dec 1998 01:21:09 -0800 (PST) From: alexandr@mail.eecis.udel.edu Message-Id: <199812310921.BAA11045@hub.freebsd.org> Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa09620; 31 Dec 1998 04:02 EST To: "Jonathan M. Bresler" Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: RE: HEADS UP: Postfix is coming. new uid, gid required. Organization: Mos Eisley Candy Store Reply-To: alexandr@mail.eecis.udel.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Reply to Your Message of Wed, 30 Dec 1998 03: 57:08 PST Date: Thu, 31 Dec 1998 04:02:31 -0500 From: Jerry Alexandratos Message-ID: <199812310402.aa09620@mail.eecis.udel.edu> "Jonathan M. Bresler" says: : : Starting later today, I will import Postfix (aka VMailer : aka SecureMailer from IBM) into the tree under /usr/src/contrib. : Postfix was written by Wietse Venema (tcp_wrappers, satan, etc). Just to play "devil's advocate" I have a question. Why put Postfix in the tree instead of making it a port? The only reason I ask is because exim and qmail are ports instead of being in the tree. --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 01:21:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA11114 for freebsd-current-outgoing; Thu, 31 Dec 1998 01:21:40 -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 BAA11106 for ; Thu, 31 Dec 1998 01:21:36 -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 BAA12911 for ; Thu, 31 Dec 1998 01:17:16 -0800 (PST) Date: Thu, 31 Dec 1998 01:17:16 -0800 (PST) From: Jaye Mathisen X-Sender: mrcpu@schizo.cdsnet.net To: current@FreeBSD.ORG Subject: OK, if you're caught in the middle... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The following worked for me to finish getting from aout to elf. vi /etc/make.conf, uncomment NOSENDMAIL and NOPERL (perl fails in aout-to-elf install with some problem with gv.h. I uncommented NOSENDMAIL since I could, onthe assumptiong I would get an elf sendmail and perl later). make -k aout-to-elf-build make -k aout-to-elf-install cp /usr/mdec/boot? /boot echo '/boot/loader' > /boot.config disklabel -B bootdevices build and install elf kernel reboot Rebuilding the rest of the world now in elf format just to be absolutely paranoid. I mean absolutely sure. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 01:40:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12032 for freebsd-current-outgoing; Thu, 31 Dec 1998 01:40:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.oeno.com (ns.oeno.com [194.100.99.145]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA12027 for ; Thu, 31 Dec 1998 01:40:06 -0800 (PST) (envelope-from will@ns.oeno.com) Received: (qmail 16325 invoked by uid 1001); 31 Dec 1998 09:39:44 -0000 To: John Polstra Cc: current@FreeBSD.ORG Subject: Re: CVS issues References: From: Ville-Pertti Keinonen Date: 31 Dec 1998 11:39:21 +0200 In-Reply-To: John Polstra's message of "30 Dec 1998 03:44:06 +0200" Message-ID: <86lnjoabw5.fsf@not.oeno.com> Lines: 20 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Polstra writes: > The reason I haven't done it so far is because the mirrors differ > in some of the little-used collections that they carry. They all Are you sure there are no other reasons for not doing it? What happens if you cvsup from a site that has an older version of the tree than you do? Does it do nothing in both repository mode and in checked-out mode? CVS removes changes and gives you an older version if you update from an old repository (at least if you're on the main branch). Which is the right thing for CVS to do because with CVS the only way you should end up with an old repository is if you restore an old backup after you've lost the one that's up-to-date. But if cvsup ever removes changes, a DNS round-robin entry could cause problems that don't occur when always syncing from a specific server. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 01:46:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12591 for freebsd-current-outgoing; Thu, 31 Dec 1998 01:44:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from gina.swimsuit.internet.dk (mail.swimsuit.internet.dk [194.255.12.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12586 for ; Thu, 31 Dec 1998 01:44:47 -0800 (PST) (envelope-from leifn@swimsuit.internet.dk) Received: from localhost (localhost [127.0.0.1]) by gina.swimsuit.internet.dk (8.9.1/8.9.1) with ESMTP id KAA75284; Thu, 31 Dec 1998 10:42:56 +0100 (CET) (envelope-from leifn@swimsuit.internet.dk) Date: Thu, 31 Dec 1998 10:42:53 +0100 (CET) From: Leif Neland To: Palle Girgensohn cc: Leif Neland , current@FreeBSD.ORG Subject: Re: Upgrading slave In-Reply-To: <368B047B.B4FE92B1@partitur.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Palle Girgensohn wrote: > I just saw this. > > I had: > NOPROFILE= true > > in make.conf, but only one master machine. Putting it on the slave fixes > it (libblahblah_p.a is the profiled library) > Thanks, I rsync'ed /etc/make.conf, and slave is instalworld'ing happily now. Leif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 01:46:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12817 for freebsd-current-outgoing; Thu, 31 Dec 1998 01:46:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (spain-24.ppp.hooked.net [206.169.228.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA12810 for ; Thu, 31 Dec 1998 01:46:28 -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 BAA48722 for ; Thu, 31 Dec 1998 01:49:12 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 31 Dec 1998 01:49:11 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: current Subject: egcs chokes on netinet/in.h.. 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 /usr/include/netinet/in.h:291: ANSI C++ forbids data member `ip_opts' with same name as enclosing class In upgrading my egcs (to get around some rather annoying bugs), this seems to have been changed from a warning to a fatal error. Is there any possibility that the ip_opts member could be named _ip_opts or somesuch? struct ip_opts { struct in_addr ip_dst; /* first hop, 0 w/o src rt */ char ip_opts[40]; /* actually variable in size */ }; - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 01:52:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA13115 for freebsd-current-outgoing; Thu, 31 Dec 1998 01:52:01 -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 BAA13101 for ; Thu, 31 Dec 1998 01:52:00 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 1390 invoked by uid 100); 31 Dec 1998 10:03:49 -0000 Date: Thu, 31 Dec 1998 02:03:49 -0800 To: freebsd-current@FreeBSD.ORG Subject: threads, linuxthreads, breaks include files Message-ID: <19981231020349.A1376@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.95i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After installing all the cool stuff from lt.tar.com I found this situation in the unix (non-linux) pthread headers: /usr/include/pthread.h: #ifndef _PTHREAD_H_ #define _PTHREAD_H_ #ifdef LINUXTHREADS #include #else #include #endif #endif /usr/include/pthread/uthread/pthread.h: ... #ifndef _PTHREAD_H_ #define _PTHREAD_H_ ... Basically, this means that the real unix pthread data will not be included from /usr/include/pthread/uthread/pthread.h because _PTHREAD_H_ is defined by the /usr/include/pthread.h wrapper. I apologize if my system is simply out of date/sync but I try to keep up. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 03:34:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA19348 for freebsd-current-outgoing; Thu, 31 Dec 1998 03:34:22 -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 DAA19343 for ; Thu, 31 Dec 1998 03:34:20 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from localhost (dfr@localhost) by nlsystems.com (8.9.1/8.8.5) with SMTP id LAA17995; Thu, 31 Dec 1998 11:34:07 GMT Date: Thu, 31 Dec 1998 11:34:07 +0000 (GMT) From: Doug Rabson To: John Birrell cc: Jaye Mathisen , current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-Reply-To: <199812310214.NAA24128@cimlogic.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 Thu, 31 Dec 1998, John Birrell wrote: > Jaye Mathisen wrote: > > > > > > Another day, another no workee. :) > > People aren't sufficiently committed to keeping the upgrade process in > working order. It's now broken in several ways. Looks like a binary > upgrade is the only feasible option. Sigh. I just successfully upgraded a machine running stock 2.2.6 like this: cvs co src cd src cvs up -r RELENG_3_0_0_RELEASE make aout-to-elf ... grind build install reboot etc ... cd /usr/src cvs up -A make world -- 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 Thu Dec 31 04:13:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA25052 for freebsd-current-outgoing; Thu, 31 Dec 1998 04:13:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m2-15-dbn.dial-up.net [196.34.155.79]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA25044 for ; Thu, 31 Dec 1998 04:13:49 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id OAA17631; Thu, 31 Dec 1998 14:12:19 +0200 (SAT) From: Robert Nordier Message-Id: <199812311212.OAA17631@ceia.nordier.com> Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: <199812310607.OAA89665@spinner.netplex.com.au> from Peter Wemm at "Dec 31, 98 02:07:19 pm" To: peter@netplex.com.au (Peter Wemm) Date: Thu, 31 Dec 1998 14:12:16 +0200 (SAT) Cc: 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 Peter Wemm wrote: > === INCOMPLETE DRAFT === > - The new bootblocks default to /boot/loader, but there are some problems > for some people still. This needs to be fixed, and either the new > bootblocks need fixing or the old bootblocks need a cutdown and > modified to fire up /boot/loader by default. Since early November (and up to and including an issue reported on -current yesterday), all apparent show-stopping problems with the new bootblocks have turned out to be due to configuration and/or pilot errors: where it has been possible to get further details. So if anyone still can't use the new bootblocks, there's almost certainly some simple and painless solution which doesn't require code fixes to sort out; and anyone who needs help is more than welcome to contact me. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 04:47:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26653 for freebsd-current-outgoing; Thu, 31 Dec 1998 04:47:11 -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 EAA26645 for ; Thu, 31 Dec 1998 04:47:06 -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 NAA11358; Thu, 31 Dec 1998 13:52:14 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 31 Dec 1998 13:52:13 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Robert Nordier cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: <199812311212.OAA17631@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Robert Nordier wrote: > Peter Wemm wrote: > > > === INCOMPLETE DRAFT === > > > - The new bootblocks default to /boot/loader, but there are some problems > > for some people still. This needs to be fixed, and either the new > > bootblocks need fixing or the old bootblocks need a cutdown and > > modified to fire up /boot/loader by default. > > Since early November (and up to and including an issue reported on > -current yesterday), all apparent show-stopping problems with the > new bootblocks have turned out to be due to configuration and/or > pilot errors: where it has been possible to get further details. > > So if anyone still can't use the new bootblocks, there's almost > certainly some simple and painless solution which doesn't require > code fixes to sort out; and anyone who needs help is more than > welcome to contact me. Ok, here's my question: how do you replace functionality of kzip (which doesn't work for ELF kernels) without loosing 120kB of disk space for /boot/loader? In case of normal installations it doesn't matter, but in case of a floppy... Thus far I was able to use kzip with a.out kernels to save space on the floppy. Since we're going ELF with kernel, and kzip doesn't work there, I'm now forced to use gzip and /boot/loader, which takes about 100kB more than simply boot2 and kzipped (a.out) kernel. 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 Thu Dec 31 05:05:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27840 for freebsd-current-outgoing; Thu, 31 Dec 1998 05:05:05 -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 FAA27833 for ; Thu, 31 Dec 1998 05:05:02 -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 OAA17585 for ; Thu, 31 Dec 1998 14:11:12 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 31 Dec 1998 14:11:12 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: freebsd-current@FreeBSD.ORG Subject: login.conf and time limits 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, Several people reported to me that time limits set in /etc/login.conf don't work, so after eliminating most probable errors (such as wrong format, or forgetting to do cap_mkdb) I went to look into sources. And I must admit that I can't find any place in the whole src/* which reads these capabilities and makes any use of them. So, is this broken, or am I (hopefully) wrong? 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 Thu Dec 31 05:30:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29874 for freebsd-current-outgoing; Thu, 31 Dec 1998 05:30:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29862; Thu, 31 Dec 1998 05:30:42 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 05:30:42 -0800 (PST) Message-Id: <199812311330.FAA29862@hub.freebsd.org> From: "Jonathan M. Bresler" To: alexandr@mail.eecis.udel.edu CC: committers@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <199812310921.BAA11045@hub.freebsd.org> (alexandr@mail.eecis.udel.edu) Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199812310921.BAA11045@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 31 Dec 1998 01:21:09 -0800 (PST) > From: alexandr@mail.eecis.udel.edu > > Just to play "devil's advocate" I have a question. Why put Postfix in > the tree instead of making it a port? The only reason I ask is because > exim and qmail are ports instead of being in the tree. well....that's a sticky question, we quickly get into the realm of opinion, opinion based upon running the FreeBSD mailing lists for several years (and other sources) but opinion none the less. Postfix is the only one of the three that I believe may become a standard mailer with the robustness, efficiency and support that is required. Postfix has proven to be an excellent mta for the FreeBSD mailing lists (you've been soaking in it for months). jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 06:03:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA02819 for freebsd-current-outgoing; Thu, 31 Dec 1998 06:03:32 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA02586; Thu, 31 Dec 1998 06:03:15 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 2.10 #1) id 0zvieE-0006Pb-00; Thu, 31 Dec 1998 16:00:22 +0200 From: Sheldon Hearn To: "Jonathan M. Bresler" cc: alexandr@mail.eecis.udel.edu, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-reply-to: Your message of "Thu, 31 Dec 1998 05:30:42 PST." <199812311330.FAA29862@hub.freebsd.org> Date: Thu, 31 Dec 1998 16:00:22 +0200 Message-ID: <24650.915112822@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998 05:30:42 PST, "Jonathan M. Bresler" wrote: > well....that's a sticky question, we quickly get into the realm of > opinion You're right, and I have no wish to pour fuel on menacing embers. However, I would like to suggest that it might be more appropriate as a port until FreeBSD starts shipping _without_ sendmail. It seems silly to have both in the src tree. If this comment does not generate a "Wow, he's absolutely right", I beseech fellow list members to leave it alone altogether. It's only an opinion and doesn't require discussion if it isn't massively supported by people who count. :-) Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 06:24:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA04761 for freebsd-current-outgoing; Thu, 31 Dec 1998 06:24:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-30-dbn.dial-up.net [196.34.155.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA04756 for ; Thu, 31 Dec 1998 06:24:21 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id QAA18260; Thu, 31 Dec 1998 16:09:30 +0200 (SAT) From: Robert Nordier Message-Id: <199812311409.QAA18260@ceia.nordier.com> Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: from Andrzej Bialecki at "Dec 31, 98 01:52:13 pm" To: abial@nask.pl (Andrzej Bialecki) Date: Thu, 31 Dec 1998 16:09:28 +0200 (SAT) Cc: rnordier@nordier.com, peter@netplex.com.au, 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 Andrzej Bialecki wrote: > On Thu, 31 Dec 1998, Robert Nordier wrote: > > > Peter Wemm wrote: > > > > > === INCOMPLETE DRAFT === > > > > > - The new bootblocks default to /boot/loader, but there are some problems > > > for some people still. This needs to be fixed, and either the new > > > bootblocks need fixing or the old bootblocks need a cutdown and > > > modified to fire up /boot/loader by default. > > > > Since early November (and up to and including an issue reported on > > -current yesterday), all apparent show-stopping problems with the > > new bootblocks have turned out to be due to configuration and/or > > pilot errors: where it has been possible to get further details. > > > > So if anyone still can't use the new bootblocks, there's almost > > certainly some simple and painless solution which doesn't require > > code fixes to sort out; and anyone who needs help is more than > > welcome to contact me. > > Ok, here's my question: how do you replace functionality of kzip (which > doesn't work for ELF kernels) without loosing 120kB of disk space for > /boot/loader? In case of normal installations it doesn't matter, but in > case of a floppy... Thus far I was able to use kzip with a.out kernels to > save space on the floppy. Since we're going ELF with kernel, and kzip > doesn't work there, I'm now forced to use gzip and /boot/loader, which > takes about 100kB more than simply boot2 and kzipped (a.out) kernel. We can't fit gunzip code into boot2 because we have a 7K limit (8K - boot1 - label). So you need either a self-extracting kernel, or a stripped-down /boot/loader, or a /boot/loader replacement. Having looked at the kzip and kzipboot code, I don't think all that much revision would be needed to handle an ELF kernel. Though I'd probably be inclined to write a standalone BTX application (around 16K) which would just function as a non-interactive gzipped ELF loader, if I had to do this myself. This seems one of those cases where the aims of PicoBSD and FreeBSD itself diverge to the extent that optimum results require some custom development. -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 06:39:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06098 for freebsd-current-outgoing; Thu, 31 Dec 1998 06:39:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA06092; Thu, 31 Dec 1998 06:39:37 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id XAA21888; Thu, 31 Dec 1998 23:39:07 +0900 (JST) Message-ID: <368B8CD8.7737E622@newsguy.com> Date: Thu, 31 Dec 1998 23:40:24 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Jonathan M. Bresler" CC: alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199812310921.BAA11045@hub.freebsd.org> <199812311330.FAA29862@hub.freebsd.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jonathan M. Bresler" wrote: > > > Just to play "devil's advocate" I have a question. Why put Postfix in > > the tree instead of making it a port? The only reason I ask is because > > exim and qmail are ports instead of being in the tree. > > well....that's a sticky question, we quickly get into the realm of > opinion, opinion based upon running the FreeBSD mailing lists for > several years (and other sources) but opinion none the less. > > Postfix is the only one of the three that I believe may become a > standard mailer with the robustness, efficiency and support that is > required. Postfix has proven to be an excellent mta for the FreeBSD > mailing lists (you've been soaking in it for months). Well, I guess that kind of skirts the question. Why not just a port? Ok, let's assume Postfix is the best one of them, I still can't see why it would need to be committed to the tree, unless as a replacement for Sendmail (meaning, sendmail gets the kick). This just looks live the pcvt/syscons vs unified console issue. As horrible as sendmail is, I doubt we could remove it from the source without a major riot. So, what it is GAINED by having Postfix in the contrib instead of the ports? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 06:43:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA06601 for freebsd-current-outgoing; Thu, 31 Dec 1998 06:43:42 -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 GAA06596 for ; Thu, 31 Dec 1998 06:43:39 -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 PAA17088; Thu, 31 Dec 1998 15:48:54 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 31 Dec 1998 15:48:54 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Robert Nordier cc: peter@netplex.com.au, current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: <199812311409.QAA18260@ceia.nordier.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Robert Nordier wrote: > This seems one of those cases where the aims of PicoBSD and FreeBSD > itself diverge to the extent that optimum results require some > custom development. ??? And what about the boot floppies? As I understand, they were using a.out kernels up to this point, weren't they? Andrzej Bialecki (going to read the src/release/Makefile once more...) -------------------- ++-------++ ------------------------------------- ||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 Thu Dec 31 06:57:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07648 for freebsd-current-outgoing; Thu, 31 Dec 1998 06:57:48 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA07641; Thu, 31 Dec 1998 06:57:45 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 06:57:45 -0800 (PST) Message-Id: <199812311457.GAA07641@hub.freebsd.org> From: "Jonathan M. Bresler" To: dcs@newsguy.com CC: alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <368B8CD8.7737E622@newsguy.com> (dcs@newsguy.com) Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199812310921.BAA11045@hub.freebsd.org> <199812311330.FAA29862@hub.freebsd.org> <368B8CD8.7737E622@newsguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 31 Dec 1998 23:40:24 +0900 > From: "Daniel C. Sobral" > > As horrible as sendmail is, I doubt we could remove it from the > source without a major riot. So, what it is GAINED by having Postfix > in the contrib instead of the ports? for many of our users sendmail.cf is a major hurdle. i know i have made money customizing sendmail.cf for people. postfix does the common sendmail.cf reconfiguration issues and does them in a way that people can roll their own and wont have to pay people like me. (hey....wait a minute....why am i doing this. ;) canonicalization, virtual hosts, spam control, etc. the .mc files go a long way to making this easier, but people still flounder. sendmail is a necessity for many sites. FreeBSD is very popular in the ISP segment and arbitrary re-writing and locally defined mailers are important to them. Sendmail is GREAT....achieving greatness takes dedicated effort. not everyone is up to the task or even wants to be great. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 07:06:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08366 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:06:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ceia.nordier.com (m1-23-dbn.dial-up.net [196.34.155.23]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA08359 for ; Thu, 31 Dec 1998 07:06:32 -0800 (PST) (envelope-from rnordier@nordier.com) Received: (from rnordier@localhost) by ceia.nordier.com (8.8.7/8.6.12) id RAA18843; Thu, 31 Dec 1998 17:05:04 +0200 (SAT) From: Robert Nordier Message-Id: <199812311505.RAA18843@ceia.nordier.com> Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: from Andrzej Bialecki at "Dec 31, 98 03:48:54 pm" To: abial@nask.pl (Andrzej Bialecki) Date: Thu, 31 Dec 1998 17:05:01 +0200 (SAT) Cc: rnordier@nordier.com, peter@netplex.com.au, 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 Andrzej Bialecki wrote: > On Thu, 31 Dec 1998, Robert Nordier wrote: > > > This seems one of those cases where the aims of PicoBSD and FreeBSD > > itself diverge to the extent that optimum results require some > > custom development. > > ??? And what about the boot floppies? As I understand, they were using > a.out kernels up to this point, weren't they? > > Andrzej Bialecki (going to read the src/release/Makefile once more...) >From reading the archives, I got the impression no-one was too worried about the idea of going to a two-disk install. (By moving away from a monolithic kernel, less "likely" drivers could be moved to a second floppy -- or could be loaded from CDROM, etc -- so a lot of the time just a single floppy would be the norm.) As I mentioned, I don't think that fixing kzip to handle a monolithic ELF kernel is much work. We're just likely to want /boot/loader around anyway, so there's not much point in doing that (for FreeBSD itself). -- Robert Nordier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 07:11:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA08892 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:11:05 -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 HAA08742; Thu, 31 Dec 1998 07:10:53 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id RAA80610; Thu, 31 Dec 1998 17:10:28 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id RAA00728; Thu, 31 Dec 1998 17:10:26 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812311510.RAA00728@greenpeace.grondar.za> To: "Daniel C. Sobral" cc: "Jonathan M. Bresler" , alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: Your message of " Thu, 31 Dec 1998 23:40:24 +0900." <368B8CD8.7737E622@newsguy.com> References: <199812310921.BAA11045@hub.freebsd.org> <199812311330.FAA29862@hub.freebsd.org> <368B8CD8.7737E622@newsguy.com> Date: Thu, 31 Dec 1998 17:10:22 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Daniel C. Sobral" wrote: > As horrible as sendmail is, I doubt we could remove it from the > source without a major riot. So, what it is GAINED by having Postfix > in the contrib instead of the ports? We gain the ability to emphasise Postfix and de-emphasise Sendmail. After an appropriate period, we gain the ability to nuke Sendmail as Postfix has been solidly tested/used/ported/integrated for "long enough". No combustion over definitions of "long enough", please :-). 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 Thu Dec 31 07:12:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09061 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:12:17 -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 HAA09055 for ; Thu, 31 Dec 1998 07:12:16 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id JAA25997 for freebsd-current@freebsd.org; Thu, 31 Dec 1998 09:11:55 -0600 (CST) (envelope-from dick) Date: Thu, 31 Dec 1998 09:11:55 -0600 From: "Richard Seaman, Jr." To: freebsd-current@FreeBSD.ORG Subject: Re: threads, linuxthreads, breaks include files Message-ID: <19981231091155.F2783@tar.com> References: <19981231020349.A1376@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19981231020349.A1376@top.worldcontrol.com>; from brian@worldcontrol.com on Thu, Dec 31, 1998 at 02:03:49AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 02:03:49AM -0800, brian@worldcontrol.com wrote: > After installing all the cool stuff from lt.tar.com I found this > situation in the unix (non-linux) pthread headers: > > /usr/include/pthread.h: > > #ifndef _PTHREAD_H_ > #define _PTHREAD_H_ > #ifdef LINUXTHREADS > #include > #else > #include > #endif > #endif > > > > /usr/include/pthread/uthread/pthread.h: > ... > #ifndef _PTHREAD_H_ > #define _PTHREAD_H_ > ... > > Basically, this means that the real unix pthread data will not > be included from /usr/include/pthread/uthread/pthread.h because > _PTHREAD_H_ is defined by the /usr/include/pthread.h wrapper. > > I apologize if my system is simply out of date/sync but I try > to keep up. You're right. This is a bug. I'll fix it. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 07:17:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09340 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:17:42 -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 HAA09335 for ; Thu, 31 Dec 1998 07:17:37 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id RAA82684; Thu, 31 Dec 1998 17:17:12 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id RAA00802; Thu, 31 Dec 1998 17:17:11 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812311517.RAA00802@greenpeace.grondar.za> To: Chuck Robey cc: freebsd-current@FreeBSD.ORG Subject: Re: groff In-Reply-To: Your message of " Wed, 30 Dec 1998 22:26:42 EST." References: Date: Thu, 31 Dec 1998 17:17:07 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chuck Robey wrote: > (BTW, don't tell me to upgrade groff, it still has the old mm in it, and > we've already got a recent version of groff in the tree. Groff doesn't > need upgrading, just groff/mm). Considering the overwhelming response you seem to have had, ;-), I reckon you vendor-import your new mm-macros and then merge them. The command line is nasty, and I can help if you wish. Happy new year! 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 Thu Dec 31 07:18:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09687 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:18:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA09670; Thu, 31 Dec 1998 07:18:32 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id AAA25717; Fri, 1 Jan 1999 00:17:28 +0900 (JST) Message-ID: <368B957A.AF6A49ED@newsguy.com> Date: Fri, 01 Jan 1999 00:17:14 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: Mark Murray CC: "Jonathan M. Bresler" , alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199812310921.BAA11045@hub.freebsd.org> <199812311330.FAA29862@hub.freebsd.org> <368B8CD8.7737E622@newsguy.com> <199812311510.RAA00728@greenpeace.grondar.za> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > We gain the ability to emphasise Postfix and de-emphasise Sendmail. > After an appropriate period, we gain the ability to nuke Sendmail > as Postfix has been solidly tested/used/ported/integrated for > "long enough". No combustion over definitions of "long enough", > please :-). Well, be my guest, and please send prvt mail to me warning you are going to announce this decision, so I can unsubscribe from the lists first. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 07:27:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10376 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:27:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mcfeely.interaccess.com (mcfeely.interaccess.com [207.208.133.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10371 for ; Thu, 31 Dec 1998 07:27:44 -0800 (PST) (envelope-from ras@interaccess.com) Received: from mis2 (fbsd.admis.com [208.192.111.12]) by mcfeely.interaccess.com (8.9.0/8.9.0) with SMTP id JAA10026 for ; Thu, 31 Dec 1998 09:27:15 -0600 (CST) From: "Chris Silva" To: Subject: Upgrade from 2.2.8 --> 3.0 Date: Thu, 31 Dec 1998 09:29:39 -0600 Message-ID: <000601be34d2$61301470$ddb5a8b6@mis2> 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 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi everyone, What's the proper way, and or the easiest way to upgrade from my 2.2.8 to the release of 3.0 in Jan? I'm a newbie, and I went from 2.2.6 to 2.2.8 by just wiping out everything. I figured, there has to be an easier way, and will still retain my users configs etc. TIA Chris _____________________________________________________________________ RSA Key Fingerprint = 6D0B 5536 7825 3D09 9093 384A 9694 FDB6 RSA Key Fingerprint = 4390 44E5 E316 F2AA A11E 5755 F3F9 D69B DH/DSS Fingerprint = 089B 0B5C 75C7 A7B4 B050 DD14 2D65 5DD6 E87D 239A PGP Mail encouraged / preferred - keys available on common keyservers _____________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 07:32:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11072 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:32:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns.uninet.ee (ns.uninet.ee [194.204.0.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11067 for ; Thu, 31 Dec 1998 07:32:29 -0800 (PST) (envelope-from taavi@uninet.ee) Received: from localhost (taavi@localhost) by ns.uninet.ee (8.8.8/8.7.3) with SMTP id RAA10682 for ; Thu, 31 Dec 1998 17:32:08 +0200 (EET) Date: Thu, 31 Dec 1998 17:32:08 +0200 (EET) From: Taavi Talvik To: current@FreeBSD.ORG Subject: Pointer to Postfix distribution.. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello ! After seeing long discussions about Postfix, can someone post poiunters to its distribution, web pages, etc. Altavista turned out a lot on postfix notation but nothing on mailer... best regards, taavi ----------------------------------------------------------- Taavi Talvik | Internet: taavi@uninet.ee Unineti Andmeside AS | phone: +372 6405150 Ravala pst. 10-412 | fax: +372 6405151 EE0001, Tallinn, Estonia | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 07:34:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11443 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:34:50 -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 HAA11437 for ; Thu, 31 Dec 1998 07:34:45 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id JAA26165 for freebsd-current@FreeBSD.ORG; Thu, 31 Dec 1998 09:34:23 -0600 (CST) (envelope-from dick) Date: Thu, 31 Dec 1998 09:34:23 -0600 From: "Richard Seaman, Jr." To: freebsd-current@FreeBSD.ORG Subject: Re: threads, linuxthreads, breaks include files Message-ID: <19981231093423.I2783@tar.com> References: <19981231020349.A1376@top.worldcontrol.com> <19981231091155.F2783@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19981231091155.F2783@tar.com>; from Richard Seaman, Jr. on Thu, Dec 31, 1998 at 09:11:55AM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 09:11:55AM -0600, Richard Seaman, Jr. wrote: > > Basically, this means that the real unix pthread data will not > > be included from /usr/include/pthread/uthread/pthread.h because > > _PTHREAD_H_ is defined by the /usr/include/pthread.h wrapper. > > > > I apologize if my system is simply out of date/sync but I try > > to keep up. > > You're right. This is a bug. I'll fix it. Ok, revised patches to fix this are now posted on http://lt.tar.com . -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 07:37:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11606 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:37:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11600; Thu, 31 Dec 1998 07:37:19 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id LAA13996; Thu, 31 Dec 1998 11:36:28 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 31 Dec 1998 11:36:28 -0400 (AST) From: The Hermit Hacker To: "Daniel C. Sobral" cc: Mark Murray , "Jonathan M. Bresler" , alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <368B957A.AF6A49ED@newsguy.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, 1 Jan 1999, Daniel C. Sobral wrote: > Mark Murray wrote: > > > > We gain the ability to emphasise Postfix and de-emphasise Sendmail. > > After an appropriate period, we gain the ability to nuke Sendmail > > as Postfix has been solidly tested/used/ported/integrated for > > "long enough". No combustion over definitions of "long enough", > > please :-). > > Well, be my guest, and please send prvt mail to me warning you are > going to announce this decision, so I can unsubscribe from the lists > first. :-) Here here...I trust and like sendmail, and have no intentions of switching from it... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 31 07:46:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA12423 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:46:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA12393 for ; Thu, 31 Dec 1998 07:45:59 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id KAA03700; Thu, 31 Dec 1998 10:44:01 -0500 (EST) Date: Thu, 31 Dec 1998 10:44:01 -0500 (EST) From: Chuck Robey To: Taavi Talvik cc: current@FreeBSD.ORG Subject: Re: Pointer to Postfix distribution.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Taavi Talvik wrote: > > hello ! > > After seeing long discussions about Postfix, can someone > post poiunters to its distribution, web pages, etc. > > Altavista turned out a lot on postfix notation but nothing > on mailer... Copying directly from Jon Bresler's recent mail on it: For a sneak preview take a look at http://www.postfix.org and http://www.alphaWorks.ibm.com/formula/securemailer. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 07:53:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13135 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:53:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13129 for ; Thu, 31 Dec 1998 07:53:42 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id LAA14068; Thu, 31 Dec 1998 11:53:19 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 31 Dec 1998 11:53:19 -0400 (AST) From: The Hermit Hacker To: Taavi Talvik cc: current@FreeBSD.ORG Subject: Re: Pointer to Postfix distribution.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Taavi Talvik wrote: > > hello ! > > After seeing long discussions about Postfix, can someone > post poiunters to its distribution, web pages, etc. > > Altavista turned out a lot on postfix notation but nothing > on mailer... Wow, that sounds like just the thing we want to replace sendmail with...something nobody can find *roll eyes* Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 31 07:58:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13542 for freebsd-current-outgoing; Thu, 31 Dec 1998 07:58:47 -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 HAA13534 for ; Thu, 31 Dec 1998 07:58:44 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 15809 invoked by uid 1001); 31 Dec 1998 15:58:23 +0000 (GMT) To: scrappy@hub.org Cc: jmb@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: Your message of "Thu, 31 Dec 1998 11:36:28 -0400 (AST)" References: X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 31 Dec 1998 16:58:23 +0100 Message-ID: <15807.915119903@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > We gain the ability to emphasise Postfix and de-emphasise Sendmail. > > > After an appropriate period, we gain the ability to nuke Sendmail > > > as Postfix has been solidly tested/used/ported/integrated for > > > "long enough". No combustion over definitions of "long enough", > > > please :-). ... > Here here...I trust and like sendmail, and have no intentions of > switching from it... I have worked with sendmail for a long time, and have made consulting money helping companies to configure their sendmail systems. But "like" and "trust" are words I'd never use together with sendmail. Even after having worked with sendmail for a long time, I found qmail considerably easier to get started with (and easier to configure in general). If Postfix can help us get away from sendmail as the default, I'd say it's definitely a good thing. But I fear this discussion is going in the religious direction... 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 Thu Dec 31 08:10:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14908 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:10:57 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14763; Thu, 31 Dec 1998 08:10:49 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id IAA26621; Thu, 31 Dec 1998 08:10:26 -0800 (PST) Date: Thu, 31 Dec 1998 08:10:26 -0800 (PST) From: "Steven P. Donegan" To: The Hermit Hacker cc: "Daniel C. Sobral" , Mark Murray , "Jonathan M. Bresler" , alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, The Hermit Hacker wrote: > > Here here...I trust and like sendmail, and have no intentions of > switching from it... > Not to flame at all - but what wonderful things does postfix bring that would induce anyone to move away from sendmail? Move from something that works in the millions of systems, is understood by vast numbers of sys admins, etc? If postfix can do something sendmail can't what is it? And an answer that it's easier to configure isn't really valid for us lifer sendmail folks :-) My 'vote' on this subject is leave postfix in ports, not in the contrib tree. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 08:16:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15311 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:16:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15286; Thu, 31 Dec 1998 08:15:54 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 08:15:54 -0800 (PST) Message-Id: <199812311615.IAA15286@hub.freebsd.org> From: "Jonathan M. Bresler" To: mark@grondar.za CC: dcs@newsguy.com, alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <199812311510.RAA00728@greenpeace.grondar.za> (message from Mark Murray on Thu, 31 Dec 1998 17:10:22 +0200) Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199812310921.BAA11045@hub.freebsd.org> <199812311330.FAA29862@hub.freebsd.org> <368B8CD8.7737E622@newsguy.com> <199812311510.RAA00728@greenpeace.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 31 Dec 1998 17:10:22 +0200 > From: Mark Murray > > We gain the ability to emphasise Postfix and de-emphasise Sendmail. > After an appropriate period, we gain the ability to nuke Sendmail > as Postfix has been solidly tested/used/ported/integrated for > "long enough". No combustion over definitions of "long enough", > please :-). WHOA!!!!! what if no one else likes postfix. postfix is coming into the tree as /usr/src/contrib. sendmail is the default mail transfer agent. individual users can switch either machines to use postfix as the mta. there is no intention of removing sendmail from the tree. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 08:18:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15614 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:18:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15608; Thu, 31 Dec 1998 08:18:18 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 08:18:18 -0800 (PST) Message-Id: <199812311618.IAA15608@hub.freebsd.org> From: "Jonathan M. Bresler" To: taavi@uninet.ee CC: current@FreeBSD.ORG In-reply-to: (message from Taavi Talvik on Thu, 31 Dec 1998 17:32:08 +0200 (EET)) Subject: Re: Pointer to Postfix distribution.. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 31 Dec 1998 17:32:08 +0200 (EET) > From: Taavi Talvik > > After seeing long discussions about Postfix, can someone > post poiunters to its distribution, web pages, etc. that information was sent to the list yesterday. short form: www.postfix.org jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 08:19:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15670 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:19:00 -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 IAA15661 for ; Thu, 31 Dec 1998 08:18:58 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id IAA19678; Thu, 31 Dec 1998 08:16:14 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdX19668; Thu Dec 31 16:16:05 1998 Date: Thu, 31 Dec 1998 08:16:02 -0800 (PST) From: Julian Elischer To: Robert Nordier cc: Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: <199812311212.OAA17631@ceia.nordier.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 as long as the old (2.0) Bootblocks can load a new a.out encoded boot loader, We are ok, but if it can't then I guess I'll need to be spending time to figure out why and fix it.. asking our clients to replace the bootblocks is not an option, but supplying a 3rd stage loader called 'kernel' will work for us.. It would REALLY be nice if FreeBSD would now with this change, do what NetBSD did, and make the kernel name /FreeBSD rather than 'kernel'. On Thu, 31 Dec 1998, Robert Nordier wrote: > Peter Wemm wrote: > > > === INCOMPLETE DRAFT === > > > - The new bootblocks default to /boot/loader, but there are some problems > > for some people still. This needs to be fixed, and either the new > > bootblocks need fixing or the old bootblocks need a cutdown and > > modified to fire up /boot/loader by default. > > Since early November (and up to and including an issue reported on > -current yesterday), all apparent show-stopping problems with the > new bootblocks have turned out to be due to configuration and/or > pilot errors: where it has been possible to get further details. > > So if anyone still can't use the new bootblocks, there's almost > certainly some simple and painless solution which doesn't require > code fixes to sort out; and anyone who needs help is more than > welcome to contact me. > > -- > Robert Nordier > > 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 31 08:23:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16155 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:23:39 -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 IAA16125; Thu, 31 Dec 1998 08:23:28 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id SAA32924; Thu, 31 Dec 1998 18:23:02 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id SAA60127; Thu, 31 Dec 1998 18:22:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812311622.SAA60127@greenpeace.grondar.za> To: "Steven P. Donegan" cc: The Hermit Hacker , "Daniel C. Sobral" , "Jonathan M. Bresler" , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: Your message of " Thu, 31 Dec 1998 08:10:26 PST." References: Date: Thu, 31 Dec 1998 18:22:55 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Steven P. Donegan" wrote: > Not to flame at all - but what wonderful things does postfix bring that > would induce anyone to move away from sendmail? Move from something that > works in the millions of systems, is understood by vast numbers of sys > admins, etc? If postfix can do something sendmail can't what is it? And > an answer that it's easier to configure isn't really valid for us lifer > sendmail folks :-) 1) Vastly easier to configure :-). (Very valid for newbies). 2) A heck of a lot more efficient. Sendmail is designed to work; this is designed to work _fast_. 3) More secure. The author is security-paranoid. This is good. 4) So far (apart from myself) I have seen no rumblings at all about removing Sendmail. 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 Thu Dec 31 08:26:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16481 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:26:03 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16433 for ; Thu, 31 Dec 1998 08:25:58 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id AAA92031; Fri, 1 Jan 1999 00:25:26 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199812311625.AAA92031@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: The Hermit Hacker cc: current@FreeBSD.ORG Subject: Re: Pointer to Postfix distribution.. In-reply-to: Your message of "Thu, 31 Dec 1998 11:53:19 -0400." Date: Fri, 01 Jan 1999 00:25:25 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > On Thu, 31 Dec 1998, Taavi Talvik wrote: > > > > > hello ! > > > > After seeing long discussions about Postfix, can someone > > post poiunters to its distribution, web pages, etc. > > > > Altavista turned out a lot on postfix notation but nothing > > on mailer... > > Wow, that sounds like just the thing we want to replace sendmail > with...something nobody can find *roll eyes* Don't sweat it Marc.. Postfix was formerly known as VMailer, and has had a good year or two of development by a rather well respected person with a pretty good security track record. The reason altavista doesn't see it is because the postfix.org thing is rather recent, as is the name (to avoid a potential trademark conflict). I regularly see stuff that's months out of date from altavista. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 08:42:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18203 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:42:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18058; Thu, 31 Dec 1998 08:42:07 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id IAA26697; Thu, 31 Dec 1998 08:41:34 -0800 (PST) Date: Thu, 31 Dec 1998 08:41:33 -0800 (PST) From: "Steven P. Donegan" To: Mark Murray cc: The Hermit Hacker , "Daniel C. Sobral" , "Jonathan M. Bresler" , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199812311622.SAA60127@greenpeace.grondar.za> 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, 31 Dec 1998, Mark Murray wrote: > > 1) Vastly easier to configure :-). (Very valid for newbies). For me and vast numbers of 'old' hands this is not any form of plus, if anything it's a minus (new, unneccessary to learn change). > 2) A heck of a lot more efficient. Sendmail is designed to work; > this is designed to work _fast_. A possible plus for the (I think) minority where sendmail poses any performance issues - I found sendmail to be quite capable of a hundred thousand or so transactions per hour - for the few who need more - make it a port - not the default... > 3) More secure. The author is security-paranoid. This is good. I appreciate that - however, the vast amount of sendmail literate folks tend to make security fixes to bugs real-time, how many postfix internals literate folks are there besides the author? > 4) So far (apart from myself) I have seen no rumblings at all > about removing Sendmail. > I have a definite rumble about removing sendmail - making postfix a port is great, making it the default and/or removing sendmail is IMHO a really non-smart idea until postfix proves itself. What's the rush? If it's such a great thing the masses will start asking for it, let it mature in the ports area until enough people ask for it to be the default. Don't remove something that everyone uses and don't bloat the distribution without a good reason. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 08:46:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18335 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:43:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smarter.than.nu (thought.calbbs.com [207.71.213.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18330 for ; Thu, 31 Dec 1998 08:43:25 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Received: from localhost (localhost [127.0.0.1]) by smarter.than.nu (8.9.1/8.9.1) with ESMTP id IAA00566; Thu, 31 Dec 1998 08:43:00 -0800 (PST) (envelope-from brian@CSUA.Berkeley.EDU) Date: Thu, 31 Dec 1998 08:43:00 -0800 (PST) From: "Brian W. Buchanan" X-Sender: brian@smarter.than.nu To: Alex Zepeda cc: current Subject: Re: egcs chokes on netinet/in.h.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Alex Zepeda wrote: > /usr/include/netinet/in.h:291: ANSI C++ forbids data member `ip_opts' with > same name as enclosing class > > In upgrading my egcs (to get around some rather annoying bugs), this seems > to have been changed from a warning to a fatal error. Is there any > possibility that the ip_opts member could be named _ip_opts or somesuch? > > struct ip_opts { > struct in_addr ip_dst; /* first hop, 0 w/o src rt */ > char ip_opts[40]; /* actually variable in size */ > }; This seems like a rather stupid restriction of ANSI C++, and in any case, the compiler shouldn't treat it as a fatal error unless you specified -ansi -pedantic. To fix this without hacking the compiler to fix the bug, perhaps try wrapping the include directive: extern "C" { #include } -- Brian Buchanan brian@smarter.than.nu brian@CSUA.Berkeley.EDU "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." -- Benjamin Franklin, 1759 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 08:48:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18746 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:48:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18736; Thu, 31 Dec 1998 08:48:05 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.1/8.9.1) with SMTP id QAA02013; Thu, 31 Dec 1998 16:49:45 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19981231084851.00979830@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 31 Dec 1998 08:48:51 -0800 To: "Jonathan M. Bresler" From: "Kurt D. Zeilenga" Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. Cc: mark@grondar.za, dcs@newsguy.com, alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199812311615.IAA15286@hub.freebsd.org> References: <199812311510.RAA00728@greenpeace.grondar.za> <199812310921.BAA11045@hub.freebsd.org> <199812311330.FAA29862@hub.freebsd.org> <368B8CD8.7737E622@newsguy.com> <199812311510.RAA00728@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:15 AM 12/31/98 -0800, Jonathan M. Bresler wrote: >there is no intention of removing sendmail from the tree. >jmb IMHO, Postfix should only be added to the tree if the intention is to remove sendmail. Since the intention is not to remove sendmail, postfix should be a port. Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 08:56:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19530 for freebsd-current-outgoing; Thu, 31 Dec 1998 08:56:41 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19524 for ; Thu, 31 Dec 1998 08:56:39 -0800 (PST) (envelope-from son@teaser.fr) Received: from teaser.fr (ppp1087-ft.teaser.fr [194.206.156.40]) by reliam.teaser.fr (8.9.1a/8.9.1a) with ESMTP id RAA25683; Thu, 31 Dec 1998 17:55:57 +0100 (MET) Received: (from son@localhost) by teaser.fr (8.9.1/8.9.1) id SAA04309; Thu, 31 Dec 1998 18:57:21 GMT (envelope-from son) Message-ID: <19981231185721.37546@breizh.prism.uvsq.fr> Date: Thu, 31 Dec 1998 18:57:21 +0000 From: Nicolas Souchu To: freebsd-current@FreeBSD.ORG Cc: Mike Smith Subject: ppbus: last patch before major commit! Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e X-Operating-System: FreeBSD breizh 3.0-CURRENT FreeBSD 3.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks! Here I propose a patch for the ppbus system before a major commit: - FIFO+DMA support (with lptcontrol -e) - Printer status read in NIBBLE IEEE1284 mode (with cat /dev/ppi0) - IEEE1284 BYTE mode read/write between two computers You may fetch the code + some info at http://www.freebsd.org/~nsouch/ppbus.html Don't forget to recompile lptcontrol. Have Fun. Thanks for your feedback :) Nicholas. -- nsouch@teaser.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 09:00:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20049 for freebsd-current-outgoing; Thu, 31 Dec 1998 09:00:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20011; Thu, 31 Dec 1998 09:00:10 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 09:00:10 -0800 (PST) Message-Id: <199812311700.JAA20011@hub.freebsd.org> From: "Jonathan M. Bresler" To: donegan@quick.net CC: mark@grondar.za, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG In-reply-to: (donegan@quick.net) Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 31 Dec 1998 08:41:33 -0800 (PST) > From: "Steven P. Donegan" > > A possible plus for the (I think) minority where sendmail poses any > performance issues - I found sendmail to be quite capable of a hundred > thousand or so transactions per hour - for the few who need more - make > it a port - not the default... rob kolstad found sendmail to be limited to 120k emails per hour (eph?). its in a LISA paper he did recently. see www.usenix.org. moving mailing list delivery from sendmail to postfix has resulted in noticeably faster service at lower loads and less memory usage. can you tell me about the sendmail configuration you are referencing? jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 09:01:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20152 for freebsd-current-outgoing; Thu, 31 Dec 1998 09:01:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from oldnews.quick.net ([207.212.170.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20119; Thu, 31 Dec 1998 09:01:24 -0800 (PST) (envelope-from donegan@oldnews.quick.net) Received: (from donegan@localhost) by oldnews.quick.net (8.8.5/8.6.9) id JAA26749; Thu, 31 Dec 1998 09:00:49 -0800 (PST) Date: Thu, 31 Dec 1998 09:00:49 -0800 (PST) From: "Steven P. Donegan" To: Mark Murray cc: The Hermit Hacker , "Daniel C. Sobral" , "Jonathan M. Bresler" , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199812311622.SAA60127@greenpeace.grondar.za> 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, 31 Dec 1998, Mark Murray wrote: > "Steven P. Donegan" wrote: > > Not to flame at all OK, now I think I'm going to put a mild heat on... neither postfix, nor it's 'older' name vmailer - appear to exist in ports, so I see no possibility that any significant number of FreeBSD users has played with this code - thus it's definitely not ready to replace anything. Add to ports - yes. the errata on the code on the postfix site indicates that it is beta, has definite known bugs (of what significance I don't know). And, although the author is well known and respected, I won't want to run such mission critical code without a long-term tire-kicking process. A definite no to this code replacing anything for a while... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 09:05:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA20570 for freebsd-current-outgoing; Thu, 31 Dec 1998 09:05:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from chmls11.mediaone.net (chmls11.mediaone.net [24.128.1.112]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA20563 for ; Thu, 31 Dec 1998 09:05:28 -0800 (PST) (envelope-from veldy@visi.com) Received: from rover (h-181-13.mn.mediaone.net [209.32.181.13]) by chmls11.mediaone.net (8.8.7/8.8.7) with SMTP id MAA04761 for ; Thu, 31 Dec 1998 12:05:06 -0500 (EST) From: "Thomas T. Veldhouse" To: "FreeBSD-Current" Subject: ELF Kernel and /boot/loader Date: Thu, 31 Dec 1998 11:05:43 -0600 Message-ID: <000001be34df$ccff7e40$0264a8c0@rover.mn.mediaone.net> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0001_01BE34AD.82650E40" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0001_01BE34AD.82650E40 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit All, How do I get my ELF kernel to boot. I was able to install it OK, and I told it to load "/boot/loader" at the prompt, but the kernel loaded and then went into a panic when it couldn't mount the root partition. Can anybody send me some simple instructions on how to boot the ELF kernel? Thank you in advance, Tom Veldhouse veldy@visi.com ------=_NextPart_000_0001_01BE34AD.82650E40 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
All,
 
    How do I get my ELF kernel to boot.  I = was able=20 to install it OK, and I told it to load "/boot/loader" at the = prompt,=20 but the kernel loaded and then went into a panic when it couldn't mount = the root=20 partition.  Can anybody send me some simple instructions on how to = boot the=20 ELF kernel?
 
Thank=20 you in advance,
 
Tom=20 Veldhouse
veldy@visi.com
------=_NextPart_000_0001_01BE34AD.82650E40-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 09:15:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21670 for freebsd-current-outgoing; Thu, 31 Dec 1998 09:15:30 -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 JAA21465; Thu, 31 Dec 1998 09:15:12 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id TAA72989; Thu, 31 Dec 1998 19:14:48 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id TAA09136; Thu, 31 Dec 1998 19:14:47 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199812311714.TAA09136@greenpeace.grondar.za> To: "Jonathan M. Bresler" cc: dcs@newsguy.com, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: Your message of " Thu, 31 Dec 1998 08:15:54 PST." <199812311615.IAA15286@hub.freebsd.org> References: <199812310921.BAA11045@hub.freebsd.org> <199812311330.FAA29862@hub.freebsd.org> <368B8CD8.7737E622@newsguy.com> <199812311510.RAA00728@greenpeace.grondar.za> <199812311615.IAA15286@hub.freebsd.org> Date: Thu, 31 Dec 1998 19:14:45 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jonathan M. Bresler" wrote: > > Date: Thu, 31 Dec 1998 17:10:22 +0200 > > From: Mark Murray > > > > We gain the ability to emphasise Postfix and de-emphasise Sendmail. > > After an appropriate period, we gain the ability to nuke Sendmail > > as Postfix has been solidly tested/used/ported/integrated for > > "long enough". No combustion over definitions of "long enough", > > please :-). > > WHOA!!!!! *Screech!* OK - what I said came out all wrong; Sorry! I was attempting to answer the question, and I got a bit too literal and ahead of myself. 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 Thu Dec 31 09:19:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21963 for freebsd-current-outgoing; Thu, 31 Dec 1998 09:19:53 -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 JAA21955 for ; Thu, 31 Dec 1998 09:19:51 -0800 (PST) (envelope-from sthaug@nethelp.no) From: sthaug@nethelp.no Received: (qmail 16412 invoked by uid 1001); 31 Dec 1998 17:19:30 +0000 (GMT) To: donegan@quick.net Cc: mark@grondar.za, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: Your message of "Thu, 31 Dec 1998 08:41:33 -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: Thu, 31 Dec 1998 18:19:30 +0100 Message-ID: <16410.915124770@verdi.nethelp.no> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > 3) More secure. The author is security-paranoid. This is good. > > I appreciate that - however, the vast amount of sendmail literate folks > tend to make security fixes to bugs real-time, how many postfix internals > literate folks are there besides the author? Personally, I think it's painfully obvious that the vast amount of sendmail admins in the world are *not* sendmail literate, and also not security conscious. They have simply used the default mailer that came with their Unix systems. Improvements in the ease of configuration *and* security, which Postfix appears to offer, can only be a good thing. 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 Thu Dec 31 09:21:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22137 for freebsd-current-outgoing; Thu, 31 Dec 1998 09:21:05 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22128; Thu, 31 Dec 1998 09:21:03 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id CAA04620; Fri, 1 Jan 1999 02:20:17 +0900 (JST) Message-ID: <368BB247.886FB8DA@newsguy.com> Date: Fri, 01 Jan 1999 02:20:07 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: "Steven P. Donegan" CC: Mark Murray , The Hermit Hacker , "Jonathan M. Bresler" , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Steven P. Donegan" wrote: > > I have a definite rumble about removing sendmail - making postfix a port > is great, making it the default and/or removing sendmail is IMHO a really > non-smart idea until postfix proves itself. > > What's the rush? If it's such a great thing the masses will start asking > for it, let it mature in the ports area until enough people ask for it to > be the default. Don't remove something that everyone uses and don't bloat > the distribution without a good reason. Sigh. I ought to have kept my mouth shut about this. Anyway, it is *not* being proposed to make Postfix default or removing sendmail. Though, from what I have heard so far, that is the *LONG TERM* plan. The idea is putting Postfix on the contrib as a way to make it further easier to choose Postfix during installation, and thus "push" Postfix as an alternative. Since Postfix is compatible to some extent with Sendmail, that is not entirely evil, IMHO. :-) Now, someone mentioned to me in prvt mail about on-coming sendmail license changes. If that's true, then it *is* imperative for FreeBSD to find an alternative. And try it. BEFORE sendmail gets stale. Mmmm.... I wonder if I'm not throwing more wood in the fire... Oh, well, better get the abestos out of the closet. :-) -- Daniel C. Sobral (8-DCS) dcs@newsguy.com "Heart like a Gabriel, pure and white as ivory, soul like a lucifer, black and cold as a piece of lead." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 09:31:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22949 for freebsd-current-outgoing; Thu, 31 Dec 1998 09:31:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22930 for ; Thu, 31 Dec 1998 09:31:07 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id MAA11141; Thu, 31 Dec 1998 12:30:26 -0500 (EST) Message-ID: <19981231123026.Q4306@ns1.adsu.bellsouth.com> Date: Thu, 31 Dec 1998 12:30:26 -0500 From: Christian Kuhtz To: Peter Wemm , Gregory Bond Cc: current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. References: <199812310530.QAA20816@melba.bby.com.au> <199812310644.OAA89872@spinner.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812310644.OAA89872@spinner.netplex.com.au>; from Peter Wemm on Thu, Dec 31, 1998 at 02:44:05PM +0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 02:44:05PM +0800, Peter Wemm wrote: > Not quite.. The 3.0 CD shipped with an ELF world, but an a.out kernel and > 3.0-level a.out bootblocks. You should be able to type a "/boot/loader" at > the boot prompt and be able to use the ELF-aware bootloader without any > problems. Assuming this works, you can type: > echo /boot/loader > /boot.config > And you're elf kernel capable. Appears this should be /boot/boot.config according to what the BIX messages say. My /boot/boot.config contains the following line /boot/loader And the message before the 10 second wait is that it can't find a /boot/boot.config file. Placing boot.config in / yields the same result. The ELF kernel boots fine after the timeout and even loads all my kld modules just fine (conversion to kld from lkm was indeed fairly simple once it was described how to do it). I now have an MPLS'ing & H.323'ing ELF kernel. Thanks to everyone for all the hard work! Yeeha! ;^) Happy new year, Chris -- "Economics is extremely useful as a form of employment for economists." -- John Kenneth Galbraith [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 09:44:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24403 for freebsd-current-outgoing; Thu, 31 Dec 1998 09:44:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from coleridge.kublai.com (coleridge.kublai.com [207.96.1.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24395; Thu, 31 Dec 1998 09:44:17 -0800 (PST) (envelope-from shmit@coleridge.kublai.com) Received: (from shmit@localhost) by coleridge.kublai.com (8.9.1/8.9.1) id MAA29215; Thu, 31 Dec 1998 12:43:51 -0500 (EST) Message-ID: <19981231124350.C6962@kublai.com> Date: Thu, 31 Dec 1998 12:43:50 -0500 From: Brian Cully To: Gary Palmer Cc: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf Reply-To: shmit@kublai.com References: <19981230181441.E2451@kublai.com> <28903.915064136@gjp.erols.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <28903.915064136@gjp.erols.com>; from Gary Palmer on Wed, Dec 30, 1998 at 07:28:56PM -0500 X-Sender: If your mailer pays attention to this, it's broken. X-PGP-Info: finger shmit@kublai.com for my public key. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 30, 1998 at 07:28:56PM -0500, Gary Palmer wrote: > Brian Cully wrote in message ID > <19981230181441.E2451@kublai.com>: > > I've heard some very good things about OpenLDAP, but we haven't > > recieved our eval copy yet. But from reading the literature about > > the design and implementation, it sounds really sweet. > > OpenLDAP is freeware. Are you meaning the one which is backended into Oracle > and costs 5 figures/CPU? (and no, I don't remember the name either) You are correct, I was thinking of OpenDirectory, if memory serves, but their web site isn't responding for some reason, so I can't verify. -bjc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:03:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27121 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:03:26 -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 KAA27116 for ; Thu, 31 Dec 1998 10:03:24 -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 LAA28386; Thu, 31 Dec 1998 11:02:48 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id LAA10202; Thu, 31 Dec 1998 11:02:47 -0700 Date: Thu, 31 Dec 1998 11:02:47 -0700 Message-Id: <199812311802.LAA10202@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Julian Elischer Cc: Robert Nordier , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: References: <199812311212.OAA17631@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 > It would REALLY be nice if FreeBSD would now with this change, do what > NetBSD did, and make the kernel name /FreeBSD rather than > 'kernel'. *YUCK* Change for the sake of change is what that would be.... 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 31 10:07:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27834 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:07:40 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.eecis.udel.edu (louie.udel.edu [128.175.2.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA27750; Thu, 31 Dec 1998 10:07:32 -0800 (PST) (envelope-from alexandr@mail.eecis.udel.edu) Date: Thu, 31 Dec 1998 10:07:32 -0800 (PST) From: alexandr@mail.eecis.udel.edu Message-Id: <199812311807.KAA27750@hub.freebsd.org> Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa06349; 31 Dec 1998 12:55 EST To: "Jonathan M. Bresler" Cc: dcs@newsguy.com, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: RE: HEADS UP: Postfix is coming. new uid, gid required. Organization: Mos Eisley Candy Store Reply-To: alexandr@mail.eecis.udel.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Reply to Your Message of Thu, 31 Dec 1998 06: 57:45 PST Date: Thu, 31 Dec 1998 12:55:20 -0500 From: Jerry Alexandratos Message-ID: <199812311255.aa06349@mail.eecis.udel.edu> "Jonathan M. Bresler" says: : > Date: Thu, 31 Dec 1998 23:40:24 +0900 : > From: "Daniel C. Sobral" : > : > As horrible as sendmail is, I doubt we could remove it from the : > source without a major riot. So, what it is GAINED by having Postfix : > in the contrib instead of the ports? : : for many of our users sendmail.cf is a major hurdle. i know i have : made money customizing sendmail.cf for people. postfix does the : common sendmail.cf reconfiguration issues and does them in a way : that people can roll their own and wont have to pay people like me. : (hey....wait a minute....why am i doing this. ;) : : canonicalization, virtual hosts, spam control, etc. the .mc files : go a long way to making this easier, but people still flounder. I'm not disagreeing with any of the "benefits" of postfix. However, everything you just mentioned about postfix (sendmail drop-in compatible, human-readable configuration files, scales well to large installations, etc...) is being done and has been done by exim over the past few years. Hey, except for the "sendmail drop-in" even qmail has met all of the other qualifications. So why did we never think of putting these mailers in the tree? However, here's my real bone of contention. The FreeBSD project has always been precise and deliberate with what is placed in the source tree, with the emphasis being stability. Look, we're still using what everyone and their grandmother calls "a way old compiler" (and yes, we've almost always been a major version behind). It took forever to get perl5 into the tree. We still haven't upgraded to the latest version of CVS. Yada, yada, yada... And now... Now we want to put a *beta* mailer for which new security holes and bugs are being found every day in the source tree instead of the ports tree. I swear, it's almost like we've become victims of IBM's marketing machine. Personally, I think we should focus our efforts on putting either gcc28 or egcs in the tree. 8) --Jerry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:15:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28842 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:15:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28834 for ; Thu, 31 Dec 1998 10:15:40 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id UAA24943 for current@freebsd.org; Wed, 30 Dec 1998 20:47:01 GMT (envelope-from nik) Date: Wed, 30 Dec 1998 20:47:01 +0000 From: Nik Clayton To: current@FreeBSD.ORG Subject: Going from 2.x to 3.x using 'make world' Message-ID: <19981230204701.B6797@catkin.nothing-going-on.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, Has anyone successfully gone from 2.x to 3.x using 'make world'? If so, did you write down what you did? I'm looking to update my tutorial, but until I get my system properly backed up (problems with a SCSI tape drive locking up at the moment) I'm going nowhere near -current, so I can't try this myself. Or is the recommended method just to backup, wipe the disk, install 3.0 and start tracking -current that way? If it is, I'll document that approach instead. N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:16:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29178 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:16:38 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29163 for ; Thu, 31 Dec 1998 10:16:34 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id UAA21012; Wed, 30 Dec 1998 20:14:32 GMT (envelope-from nik) Date: Wed, 30 Dec 1998 20:14:32 +0000 From: Nik Clayton To: Kazutaka YOKOTA Cc: current@FreeBSD.ORG Subject: Re: future of syscons Message-ID: <19981230201432.A6797@catkin.nothing-going-on.org> References: <199812221331.WAA09326@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199812221331.WAA09326@zodiac.mech.utsunomiya-u.ac.jp>; from Kazutaka YOKOTA on Tue, Dec 22, 1998 at 10:31:07PM +0900 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 22, 1998 at 10:31:07PM +0900, Kazutaka YOKOTA wrote: > I wrote some notes on the future development plan of our console > driver syscons. > > I would appriciate if you could give me some comments. I know very little about the architectural issues. I'd like to suggest a feature though -- I'd like some mechanism for userland programs to get a dump of the current screen (as text if it's a textmode screen, as an image if it isn't). I've got patches from Joel Ray Holveck against -current and -stable that do this (which I'll submit properly as soon as I've found the time to update the man pages) and some userland code that uses a new ioctl to get a copy of the current screen image, and then convert it to a GIF file. This will prove to be useful for the Doc. Proj. N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:16:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29216 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:16:49 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29187; Thu, 31 Dec 1998 10:16:39 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.8.8/8.8.8) id UAA26465; Wed, 30 Dec 1998 20:59:31 GMT (envelope-from nik) Date: Wed, 30 Dec 1998 20:59:31 +0000 From: Nik Clayton To: "Jonathan M. Bresler" Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. Message-ID: <19981230205931.D6797@catkin.nothing-going-on.org> References: <199812301157.DAA06160@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199812301157.DAA06160@hub.freebsd.org>; from Jonathan M. Bresler on Wed, Dec 30, 1998 at 03:57:08AM -0800 Organization: Nik at home, where there's nothing going on Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 30, 1998 at 03:57:08AM -0800, Jonathan M. Bresler wrote: > Starting later today, I will import Postfix (aka VMailer > aka SecureMailer from IBM) into the tree under /usr/src/contrib. > Postfix was written by Wietse Venema (tcp_wrappers, satan, etc). Probably a stupid question, but why not pull Sendmail *out* of the tree, and then create a Sendmail and a PostFix port instead? N -- C.R.F. Consulting -- we're run to make me richer. . . To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:24:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29883 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:24:24 -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 KAA29869; Thu, 31 Dec 1998 10:24:19 -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 KAA06709; Thu, 31 Dec 1998 10:23:59 -0800 (PST) Date: Thu, 31 Dec 1998 10:23:58 -0800 (PST) From: Chris Timmons To: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: cvsup.freebsd.org Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ... is temporarily down while the repository moves to a cheetah. cvsup2 and cvsup3 are updated just as frequently, so give them a try. your path to them might be better than to cvsup.freebsd.org.... -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:32:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01025 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:32:37 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01002; Thu, 31 Dec 1998 10:32:29 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 10:32:29 -0800 (PST) Message-Id: <199812311832.KAA01002@hub.freebsd.org> From: "Jonathan M. Bresler" To: alexandr@mail.eecis.udel.edu CC: dcs@newsguy.com, committers@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: <199812311807.KAA27750@hub.freebsd.org> (alexandr@mail.eecis.udel.edu) Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199812311807.KAA27750@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 31 Dec 1998 10:07:32 -0800 (PST) > From: alexandr@mail.eecis.udel.edu > > However, here's my real bone of contention. The FreeBSD project has at last! > always been precise and deliberate with what is placed in the source > tree, with the emphasis being stability. Look, we're still using what > everyone and their grandmother calls "a way old compiler" (and yes, > we've almost always been a major version behind). It took forever to > get perl5 into the tree. We still haven't upgraded to the latest > version of CVS. Yada, yada, yada... > > And now... Now we want to put a *beta* mailer for which new security > holes and bugs are being found every day in the source tree instead of > the ports tree. 1. Wietse Venema's beta is better then many finished products. We have been using it to deliver the FreeBSD mailing lists for months. 2. "new security holes and bugs are being found every day" is false. the only "security holes and bugs" found recently are along the lines of "world writeable directories are bad". 3. IBM's marketing machine is picking up on a program what Wietse started quite a while ago. His current employer wants to capitalize on it. so be it. 4. if you believe that there is a problem with postfix, please tell me what it is. the problem must be one with postfix, not how its labelled or who is hyping it. jmb > I swear, it's almost like we've become victims of IBM's marketing > machine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:33:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01131 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:33:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from luke.srtc.com (luke.srtc.com [208.132.236.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA01124 for ; Thu, 31 Dec 1998 10:33:08 -0800 (PST) (envelope-from jdeppen@ruby.srtc.com) Received: from SRTC (ruby [208.132.236.2]) by luke.srtc.com (8.6.12/8.6.9) with ESMTP id NAA04962 for ; Thu, 31 Dec 1998 13:29:32 -0500 Received: from uraninite.srtc.com by SRTC (950413.SGI.8.6.12/SRTC-Client) id NAA05463; Thu, 31 Dec 1998 13:32:19 -0500 Received: from uraninite by uraninite.srtc.com (SMI-8.6/SMI-SVR4) id NAA15987; Thu, 31 Dec 1998 13:32:54 -0500 Message-Id: <199812311832.NAA15987@uraninite.srtc.com> Date: Thu, 31 Dec 1998 13:32:54 -0500 (EST) From: John Deppen Reply-To: John Deppen To: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: YdY0zQi+Q5fpdFvYSklbUg== X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4u sparc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is there any way around the following problem? When the pthreads are linked I get an undefined reference to 'poll'. (Called from within a thread) In the Makefile: CFLAGS+= -pthreads However, when this is removed I obviously get undefined references to all of the pthread_.. functions. Thanks in advance for any help, J. Deppen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:35:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA01371 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:35:08 -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 KAA01363 for ; Thu, 31 Dec 1998 10:35:05 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id KAA17997; Thu, 31 Dec 1998 10:34:36 -0800 (PST) (envelope-from obrien) Message-ID: <19981231103436.A17976@nuxi.com> Date: Thu, 31 Dec 1998 10:34:36 -0800 From: "David O'Brien" To: "Richard Seaman, Jr." , freebsd-current@FreeBSD.ORG Subject: Re: threads, linuxthreads, breaks include files Reply-To: obrien@NUXI.com References: <19981231020349.A1376@top.worldcontrol.com> <19981231091155.F2783@tar.com> <19981231093423.I2783@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981231093423.I2783@tar.com>; from Richard Seaman, Jr. on Thu, Dec 31, 1998 at 09:34:23AM -0600 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 > > You're right. This is a bug. I'll fix it. > > Ok, revised patches to fix this are now posted on http://lt.tar.com . Isn't Linuxthreads in the CVS tree now? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:40:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02157 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:40:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hp9000.chc-chimes.com (hp9000.chc-chimes.com [206.67.97.84]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02143 for ; Thu, 31 Dec 1998 10:40:12 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: from localhost by hp9000.chc-chimes.com with SMTP (1.39.111.2/16.2) id AA293858498; Thu, 31 Dec 1998 07:48:18 -0500 Date: Thu, 31 Dec 1998 07:48:18 -0500 (EST) From: Bill Fumerola To: John Deppen Cc: current@FreeBSD.ORG Subject: Re: your mail In-Reply-To: <199812311832.NAA15987@uraninite.srtc.com> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, John Deppen wrote: > Is there any way around the following problem? > > When the pthreads are linked I get an undefined reference to 'poll'. (Called > from within a thread) > > In the Makefile: > CFLAGS+= -pthreads > > However, when this is removed I obviously get undefined references to > all of the pthread_.. functions. > > Thanks in advance for any help, Are you linking the correct libraries as well? - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@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 31 10:44:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02659 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:44:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from vanessa.eliuk.org (pme31.sunshine.net [209.17.178.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA02652 for ; Thu, 31 Dec 1998 10:44:52 -0800 (PST) (envelope-from kevin_eliuk@sunshine.net) Received: from localhost (cagey@localhost) by vanessa.eliuk.org (8.9.1/8.8.8) with SMTP id KAA00986; Thu, 31 Dec 1998 10:44:29 -0800 (PST) (envelope-from cagey@vanessa.eliuk.org) Date: Thu, 31 Dec 1998 10:43:58 -0800 (PST) From: "Kevin G. Eliuk" Reply-To: "Kevin G. Eliuk" To: current@FreeBSD.ORG cc: Richard Seaman Subject: Trouble with Staroffice5.0 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 have been trying for the last week or so to install StarOffice5.0 as described in the documentation , and have yet to be successful. I get as far as: ... $ cd /home/cagey/so50/office50_inst $ export LD_LIBRARY_PATH=/tmp/sv001.tmp:$LD_LIBRARY_PATH $ ./setup It gives the the message: ./setup: Window manager didn't set icon sizes - using default. After a lot of disk activity after which a full screen frame appears with "Installation" in the title bar(no window just the frame). A smaller window appears with "Star Office Setup" in the title bar, the mouse cursor changes, and a 3D button labelled "Next". This is where the whole thing freezes. The only activity that I can make happen at that point is some disk activity with moving the mouse. Later I thought I would try and see what kind of usage was going on by hot keying to a different tty and running top. It appears that it does take a lot of resources up to that point. And in this mode it completes the process of creating the setup screen. When I hot key back to the window session and use the mouse or keyboard it again freezes everything up again. I toyed with lowering the depth to 8 bit which allows the filling in of the "Installation" window, but it still locks up. I seen the post about the patch for the pthread code and will bring it in on my next build. I also tried this with a twm session a root with no different result. One other note, I had to manually patch "/usr/src/lib/libc_r/Makefile" Any ideas on where I can go from here. Thanx:) -- HappyNewYear, Kevin G. Eliuk Discover Rock Solid, Discover FreeBSD | http://www.FreeBSD.Org Build date same as kernel recently cvsup'd Applied patches from lt.tar.com Built with -DCOMPAT_LINUX_THREADS -DVM_STACK and the POSIX options in the kernel. kern.ostype: FreeBSD kern.osrelease: 3.0-CURRENT kern.osrevision: 199506 kern.version: FreeBSD 3.0-CURRENT #0: Wed Dec 30 23:22:57 PST 1998 root@vanessa.eliuk.org:/usr/src/sys/compile/CATHERNA kern.maxvnodes: 2410 kern.maxproc: 532 kern.maxfiles: 1064 kern.argmax: 65536 kern.securelevel: -1 kern.hostname: vanessa.eliuk.org kern.hostid: 0 kern.clockrate: { hz = 100, tick = 10000, tickadj = 5, profhz = 1024, \ stathz = 128 } kern.posix1version: 199309 kern.ngroups: 16 kern.job_control: 1 kern.saved_ids: 0 kern.boottime: { sec = 915106154, usec = 577330 } Thu Dec 31 04:09:14 1998 kern.domainname: kern.osreldate: 300006 kern.bootfile: /kernel kern.maxfilesperproc: 1064 kern.maxprocperuid: 531 kern.dumpdev: { major = 255, minor = -65281 } kern.ipc.maxsockbuf: 262144 kern.ipc.sockbuf_waste_factor: 8 kern.ipc.somaxconn: 128 kern.ipc.max_linkhdr: 16 kern.ipc.max_protohdr: 40 kern.ipc.max_hdr: 56 kern.ipc.max_datalen: 40 kern.ipc.nmbclusters: 1024 kern.ipc.maxsockets: 1064 kern.dummy: 0 kern.ps_strings: -272637968 kern.usrstack: -272637952 kern.logsigexit: 1 kern.shutdown_timeout: 120 kern.module_path: /;/boot/;/modules/ kern.acct_suspend: 2 kern.acct_resume: 4 kern.acct_chkfreq: 15 kern.timecounter.method: 0 kern.timecounter.frequency: 99878100 kern.timecounter.adjustment: 0 kern.fast_vfork: 1 kern.sugid_coredump: 0 kern.corefile: %N.core kern.quantum: 10 kern.ccpu: 1948 kern.fscale: 2048 kern.devstat.numdevs: 3 kern.devstat.generation: 3 kern.devstat.version: 2 kern.consmute: 0 vm.loadavg: { 0.00 0.01 0.00 } vm.v_free_min: 223 vm.v_free_target: 856 vm.v_free_reserved: 187 vm.v_inactive_target: 1284 vm.v_cache_min: 856 vm.v_cache_max: 1712 vm.v_pageout_free_min: 34 vm.pageout_algorithm: 0 vm.swap_enabled: 1 vm.swap_idle_threshold1: 2 vm.swap_idle_threshold2: 10 vm.stats.sys.v_swtch: 1780145 vm.stats.sys.v_trap: 91802 vm.stats.sys.v_syscall: 5153773 vm.stats.sys.v_intr: 5372666 vm.stats.sys.v_soft: 1449614 vm.stats.vm.v_vm_faults: 88040 vm.stats.vm.v_cow_faults: 32425 vm.stats.vm.v_cow_optim: 5363 vm.stats.vm.v_zfod: 27242 vm.stats.vm.v_ozfod: 10117 vm.stats.vm.v_swapin: 1047 vm.stats.vm.v_swapout: 1432 vm.stats.vm.v_swappgsin: 2593 vm.stats.vm.v_swappgsout: 4018 vm.stats.vm.v_vnodein: 2098 vm.stats.vm.v_vnodeout: 0 vm.stats.vm.v_vnodepgsin: 12028 vm.stats.vm.v_vnodepgsout: 0 vm.stats.vm.v_intrans: 76 vm.stats.vm.v_reactivated: 5197 vm.stats.vm.v_pdwakeups: 130 vm.stats.vm.v_pdpages: 381994 vm.stats.vm.v_dfree: 149 vm.stats.vm.v_pfree: 902 vm.stats.vm.v_tfree: 71936 vm.stats.vm.v_page_size: 4096 vm.stats.vm.v_page_count: 7514 vm.stats.vm.v_free_reserved: 187 vm.stats.vm.v_free_target: 856 vm.stats.vm.v_free_min: 223 vm.stats.vm.v_free_count: 612 vm.stats.vm.v_wire_count: 1663 vm.stats.vm.v_active_count: 2504 vm.stats.vm.v_inactive_target: 1284 vm.stats.vm.v_inactive_count: 1552 vm.stats.vm.v_cache_count: 1158 vm.stats.vm.v_cache_min: 856 vm.stats.vm.v_cache_max: 1712 vm.stats.vm.v_pageout_free_min: 34 vm.stats.vm.v_interrupt_free_min: 2 vm.stats.misc.zero_page_count: 544 vm.stats.misc.cnt_prezero: 42222 vm.pageout_stats_max: 856 vm.pageout_full_stats_interval: 20 vm.pageout_stats_interval: 5 vm.pageout_stats_free_max: 5 vm.swap_idle_enabled: 0 vm.defer_swapspace_pageouts: 0 vm.disable_swapspace_pageouts: 0 vm.max_page_launder: 32 vm.zone: ITEM SIZE LIMIT USED FREE REQUESTS PIPE: 160, 0, 21, 81, 697 unpcb: 64, 0, 29, 99, 110 ripcb: 96, 1064, 0, 42, 0 tcpcb: 288, 1064, 13, 29, 50 udpcb: 96, 1064, 2, 82, 603 socket: 160, 1064, 44, 56, 789 AIOLIO: 704, 0, 0, 0, 0 AIOL: 64, 0, 0, 0, 0 AIOCB: 128, 0, 0, 0, 0 AIOP: 32, 0, 0, 0, 0 AIO: 96, 0, 0, 0, 0 NFSNODE: 288, 0, 0, 0, 0 NFSMOUNT: 544, 0, 0, 0, 0 VNODE: 192, 0, 954, 106, 944 NAMEI: 1024, 0, 0, 16, 58802 VMSPACE: 192, 0, 34, 30, 970 PROC: 352, 0, 37, 21, 975 DP fakepg: 64, 0, 6, 122, 11 PV ENTRY: 28, 122778, 5085, 5002, 308202 MAP ENTRY: 40, 0, 645, 299, 82015 KMAP ENTRY: 40, 2006, 61, 169, 530 MAP: 100, 0, 7, 3, 7 VM OBJECT: 136, 0, 1075, 231, 19159 vm.zone_kmem_pages: 24 vm.zone_kmem_kvaspace: 3973120 vm.zone_kern_pages: 113 vfs.nfs.nfs_privport: 0 vfs.nfs.async: 0 vfs.nfs.gatherdelay: 10000 vfs.nfs.gatherdelay_v3: 0 vfs.nfs.defect: 0 vfs.nfs.diskless_valid: 0 vfs.nfs.diskless_rootpath: vfs.nfs.diskless_swappath: vfs.nfs.access_cache_timeout: 2 vfs.nfs.access_cache_hits: 0 vfs.nfs.access_cache_fills: 0 vfs.lkm0: 0 vfs.lkm1: 0 vfs.numdirtybuffers: 11 vfs.lodirtybuffers: 63 vfs.hidirtybuffers: 127 vfs.numfreebuffers: 845 vfs.lofreebuffers: 52 vfs.hifreebuffers: 104 vfs.maxbufspace: 3538944 vfs.bufspace: 3533824 vfs.maxvmiobufspace: 2359296 vfs.vmiospace: 3236864 vfs.maxmallocbufspace: 176947 vfs.bufmallocspace: 169984 vfs.kvafreespace: 1712128 vfs.cache.numneg: 61 vfs.cache.numcache: 978 vfs.cache.numcalls: 182151 vfs.cache.dothits: 508 vfs.cache.dotdothits: 662 vfs.cache.numchecks: 224780 vfs.cache.nummiss: 7329 vfs.cache.nummisszap: 718 vfs.cache.numposzaps: 579 vfs.cache.numposhits: 167247 vfs.cache.numnegzaps: 224 vfs.cache.numneghits: 4884 vfs.cache.numcwdcalls: 261 vfs.cache.numcwdfail1: 0 vfs.cache.numcwdfail2: 0 vfs.cache.numcwdfail3: 0 vfs.cache.numcwdfail4: 0 vfs.cache.numcwdfound: 261 vfs.mod0: 0 vfs.mod1: 0 vfs.usermount: 0 vfs.aio.max_aio_per_proc: 32 vfs.aio.max_aio_queue_per_proc: 256 vfs.aio.max_aio_procs: 32 vfs.aio.num_aio_procs: 0 vfs.aio.num_queue_count: 0 vfs.aio.max_aio_queue: 1024 vfs.aio.target_aio_procs: 0 vfs.aio.max_buf_aio: 16 vfs.aio.num_buf_aio: 0 vfs.aio.aiod_lifetime: 3000 vfs.aio.aiod_timeout: 1000 vfs.ffs.doreallocblks: 1 vfs.ffs.doasyncfree: 1 net.local.stream.sendspace: 8192 net.local.stream.recvspace: 8192 net.local.dgram.maxdgram: 2048 net.local.dgram.recvspace: 4096 net.local.inflight: 0 net.inet.ip.portrange.lowfirst: 1023 net.inet.ip.portrange.lowlast: 600 net.inet.ip.portrange.first: 1024 net.inet.ip.portrange.last: 5000 net.inet.ip.portrange.hifirst: 49152 net.inet.ip.portrange.hilast: 65535 net.inet.ip.forwarding: 0 net.inet.ip.redirect: 1 net.inet.ip.ttl: 64 net.inet.ip.rtexpire: 3600 net.inet.ip.rtminexpire: 10 net.inet.ip.rtmaxcache: 128 net.inet.ip.sourceroute: 0 net.inet.ip.intr_queue_maxlen: 50 net.inet.ip.intr_queue_drops: 0 net.inet.ip.accept_sourceroute: 0 net.inet.ip.fastforwarding: 0 net.inet.ip.subnets_are_local: 0 net.inet.icmp.maskrepl: 0 net.inet.icmp.icmplim: -1 net.inet.icmp.bmcastecho: 0 net.inet.tcp.rfc1323: 0 net.inet.tcp.rfc1644: 0 net.inet.tcp.mssdflt: 512 net.inet.tcp.rttdflt: 3 net.inet.tcp.keepidle: 14400 net.inet.tcp.keepintvl: 150 net.inet.tcp.sendspace: 16384 net.inet.tcp.recvspace: 16384 net.inet.tcp.keepinit: 150 net.inet.tcp.log_in_vain: 0 net.inet.tcp.delayed_ack: 1 net.inet.tcp.pcbcount: 13 net.inet.tcp.always_keepalive: 0 net.inet.udp.checksum: 1 net.inet.udp.maxdgram: 9216 net.inet.udp.recvspace: 41600 net.inet.udp.log_in_vain: 0 net.inet.raw.maxdgram: 8192 net.inet.raw.recvspace: 8192 net.link.generic.system.ifcount: 4 net.link.ether.inet.prune_intvl: 300 net.link.ether.inet.max_age: 1200 net.link.ether.inet.host_down_time: 20 net.link.ether.inet.maxtries: 5 net.link.ether.inet.useloopback: 1 net.link.ether.inet.proxyall: 0 debug.elf_trace: 0 debug.fdexpand: 0 debug.debugger_on_panic: 0 debug.ttydebug: 0 debug.nchash: 4095 debug.ncnegfactor: 16 debug.numneg: 61 debug.numcache: 978 debug.vfscache: 1 debug.vnsize: 164 debug.ncsize: 36 debug.numvnodes: 954 debug.wantfreevnodes: 25 debug.freevnodes: 462 debug.busyprt: 0 debug.disablecwd: 0 debug.bpf_bufsize: 4096 debug.if_tun_debug: 0 debug.max_softdeps: 19280 debug.tickdelay: 2 debug.max_limit_hit: 0 debug.rush_requests: 0 hw.machine: i386 hw.model: Pentium/P54C hw.ncpu: 1 hw.byteorder: 1234 hw.physmem: 31277056 hw.usermem: 24465408 hw.pagesize: 4096 hw.floatingpoint: 1 hw.machine_arch: i386 hw.availpages: 7476 machdep.consdev: { major = 0, minor = 0 } machdep.adjkerntz: 28800 machdep.disable_rtc_set: 0 machdep.wall_cmos_clock: 1 machdep.do_dump: 1 machdep.ispc98: 0 machdep.msgbuf: 00 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 < .. snip .. > 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VESA: v1.2, 4096k memory, flags:0x0, mode table:0xf00c4ab5 (c0004ab5) VESA: S3 Incorporated. 86C325 VESA: mode:0x100, flags:0x001b, G 640x400x8 1, font:8x16 VESA: window A:0xa000 (7), window B:0xa000 (0), size:64k, gran:64k < .. snip .. > VESA: mode:0x101, flags:0x001b, G 640x480x8 1, font:8x16 VESA: window A:0xa000 (7), window B:0xa000 (0), size:64k, gran:64k sc0: the current keyboard controller command byte 0065 <7>kbdio: DIAGNOSE status:0055 <7>kbdio: TEST_KBD_PORT status:0000 <7>kbdio: RESET_KBD return code:00fa <7>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 on isa sio0: type 16550A sio1: disabled, not probed. sio2: disabled, not probed. sio3: irq maps: 0x1 0x9 0x1 0x1 sio3 at 0x2e8-0x2ef irq 3 on isa sio3: type 16550A ppc: parallel port found at 0x378 ppc0: EPP SPP ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode nlpt0: on ppbus 0 nlpt0: Interrupt-driven port plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached mss_detect - chip revision 0x0a ... try to identify the yamaha mss_detect() - Detected CS4231 pcm0 at 0x530 irq 5 drq 0 flags 0xc113 on isa mss_attach 0 at 0x530 irq 5 dma 0:3 flags 0xc113 setting up yamaha registers set yamaha master volume to max 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 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 8010MB (16406208 sectors), 16276 cyls, 16 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 wdc0: unit 1 (wd1): , 32-bit, multi-block-32 wd1: 1036MB (2121840 sectors), 2105 cyls, 16 heads, 63 S/T, 512 B/S wd1: ATA INQUIRE valid = 0003, dmamword = 0407, apio = 0003, udma = 0000 wdc1: disabled, not probed. npx0 on motherboard npx0: INT 16 interface i586_bzero() bandwidth = 162022034 bytes/sec bzero() bandwidth = 88105726 bytes/sec imasks: bio c0084040, tty c00700ba, net c00700ba 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. Intel Pentium detected, installing workaround for F00F bug bpf: tun0 attached bpf: sl0 attached bpf: lo0 attached Linux-ELF exec handler installed Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to wd0s2a wd0s1: type 0xb, start 63, end = 5253254, size 5253192 : OK wd0s2: type 0xa5, start 5253255, end = 16402364, size 11149110 wd0s2: C/H/S end 1019/254/63 (16386299) != end 16402364: invalid WARNING: / was not properly dismounted Start pid=2 Start pid=3 Start pid=4 wd1s1: type 0xa5, start 63, end = 1842623, size 1842561 : OK wd1s1: type 0xa5, start 63, end = 1842623, size 1842561 : OK ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates wd1s1: type 0xa5, start 63, end = 1842623, size 1842561 : OK ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates machdep.msgbuf_clear: 0 machdep.i8254_freq: 1193289 machdep.tsc_freq: 99878100 machdep.conspeed: 9600 user.cs_path: /usr/bin:/bin:/usr/sbin:/sbin: user.bc_base_max: 99 user.bc_dim_max: 2048 user.bc_scale_max: 99 user.bc_string_max: 1000 user.coll_weights_max: 0 user.expr_nest_max: 32 user.line_max: 2048 user.re_dup_max: 255 user.posix2_version: 199212 user.posix2_c_bind: 0 user.posix2_c_dev: 0 user.posix2_char_term: 0 user.posix2_fort_dev: 0 user.posix2_fort_run: 0 user.posix2_localedef: 0 user.posix2_sw_dev: 0 user.posix2_upe: 0 user.stream_max: 20 user.tzname_max: 255 p1003_1b.asynchronous_io: 0 p1003_1b.mapped_files: 0 p1003_1b.memlock: 0 p1003_1b.memlock_range: 0 p1003_1b.memory_protection: 0 p1003_1b.message_passing: 0 p1003_1b.prioritized_io: 0 p1003_1b.priority_scheduling: 1 p1003_1b.realtime_signals: 0 p1003_1b.semaphores: 0 p1003_1b.fsync: 0 p1003_1b.shared_memory_objects: 0 p1003_1b.synchronized_io: 0 p1003_1b.timers: 0 p1003_1b.aio_listio_max: 0 p1003_1b.aio_max: 0 p1003_1b.aio_prio_delta_max: 0 p1003_1b.delaytimer_max: 0 p1003_1b.mq_open_max: 0 p1003_1b.pagesize: 4096 p1003_1b.rtsig_max: 0 p1003_1b.sem_nsems_max: 0 p1003_1b.sem_value_max: 0 p1003_1b.sigqueue_max: 0 p1003_1b.timer_max: 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:46:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02807 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:46:23 -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 KAA02802 for ; Thu, 31 Dec 1998 10:46:21 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id KAA18058 for freebsd-current@FreeBSD.ORG; Thu, 31 Dec 1998 10:45:57 -0800 (PST) (envelope-from obrien) Message-ID: <19981231104557.C17976@nuxi.com> Date: Thu, 31 Dec 1998 10:45:57 -0800 From: "David O'Brien" To: freebsd-current@FreeBSD.ORG Subject: Re: groff Reply-To: obrien@NUXI.com References: <199812311517.RAA00802@greenpeace.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812311517.RAA00802@greenpeace.grondar.za>; from Mark Murray on Thu, Dec 31, 1998 at 05:17:07PM +0200 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 > The command line is nasty, and I can help if you wish. It is also documented in the Handbook. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:46:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA02833 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:46:35 -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 KAA02824 for ; Thu, 31 Dec 1998 10:46:30 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id KAA18048; Thu, 31 Dec 1998 10:45:28 -0800 (PST) (envelope-from obrien) Message-ID: <19981231104528.B17976@nuxi.com> Date: Thu, 31 Dec 1998 10:45:28 -0800 From: "David O'Brien" To: Chuck Robey , freebsd-current@FreeBSD.ORG Subject: Re: groff Reply-To: obrien@NUXI.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Chuck Robey on Wed, Dec 30, 1998 at 10:26:42PM -0500 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 > (BTW, don't tell me to upgrade groff, it still has the old mm in it, and > we've already got a recent version of groff in the tree. Groff doesn't > need upgrading, just groff/mm). CVS nuke groff/mm CVS import the mm macros from the current groff into contrib/mm-macros on a VENDOR branch (name of which is the author of the mm macros). Add the authors current offering on the same vendor branch. Make any FreeBSD hacks to mm and then mundge the Makefiles in gnu/usr.bin/groff to install the updated mm macros rather than the one you nuked from groff/mm. This way would make it clear the division in maintance and authorship of the macros. -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:50:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03301 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:50:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles121.castles.com [208.214.165.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03291 for ; Thu, 31 Dec 1998 10:50:51 -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 KAA00785; Thu, 31 Dec 1998 10:47:35 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812311847.KAA00785@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans cc: current@FreeBSD.ORG, luigi@labinfo.iet.unipi.it Subject: Re: -DKERNEL option when compiling kernels ? In-reply-to: Your message of "Thu, 31 Dec 1998 16:28:37 +1100." <199812310528.QAA05885@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Dec 1998 10:47:34 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >i see that now -DKERNEL is the only define left in the command line, > >most things being in opt_global.h > > > >Couldn't it also go into opt_global.h ? > > It could, but it doesn't belong there since it is not optional. ... but it is a global option for the files in question. -- \\ 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 31 10:53:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03582 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:53:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id KAA03567 for ; Thu, 31 Dec 1998 10:53:24 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id NAA05191 for current@freebsd.org; Thu, 31 Dec 1998 13:58:07 -0500 From: Bill Paul Message-Id: <199812311858.NAA05191@skynet.ctr.columbia.edu> Subject: bus_space_foo and bus_dmamap_foo To: current@FreeBSD.ORG Date: Thu, 31 Dec 1998 13:58:06 -0500 (EST) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For those of you dying for a change of pace, here's a purely technical posting rather than a political one. At some point, somebody brought over a bunch of machine-independent bus support from NetBSD, in the form of the bus_space_foo() and bus_dmamap_foo() code. Unfortunately, it seems whoever did it left the job half done: - While we have things like bus_space_read_1(), which takes bus_space_handle_t and bus_space_tag_t arguments, we do not have the necessary functions to create the bus space handle and tag in the first place. From what I can tell, drivers manually assign them by setting them to I386_BUS_SPACE_MEM or I386_BUS_SPACE_PIO (for the tag) or the iobase or membase address (for the handle). This obviously is not machine independent. - There is no bus_dmamap_load_mbuf(). This makes it very hard to use the bus_dmamap stuff for network interface drivers. (A good example of how to use this stuff in general would be nice too.) - There are no man pages. Is anybody actually working on filling in these gaps? (No, _I'm_ not going to do it; I have enough to worry about.) If so, could somebody tell me when (in specific terms) it will be done? I'd very much like to be able to make all of the drivers that I've written machine independent, at least enough to have them compile on both the i386 and alpha architectures. We now return you to your regularly scheduled sabre-rattling. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 10:55:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03838 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:55:06 -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 KAA03833 for ; Thu, 31 Dec 1998 10:55:04 -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 NAA38699; Thu, 31 Dec 1998 13:58:17 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 31 Dec 1998 13:58:17 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Nik Clayton cc: current@FreeBSD.ORG Subject: Re: Going from 2.x to 3.x using 'make world' In-Reply-To: <19981230204701.B6797@catkin.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG someone just posted that he was successful "cvs up" to 3_0_RELEASE, doing a make aout_to_elf, then rebooting, then vvsupping the rest of the way to and make world. Alfred Perlstein - Programmer, HotJobs Inc. - www.hotjobs.com -- There are operating systems, and then there's FreeBSD. -- http://www.freebsd.org/ 3.0-current On Wed, 30 Dec 1998, Nik Clayton wrote: > Folks, > > Has anyone successfully gone from 2.x to 3.x using 'make world'? If so, did > you write down what you did? > > I'm looking to update my tutorial, but until I get my system properly > backed up (problems with a SCSI tape drive locking up at the moment) I'm > going nowhere near -current, so I can't try this myself. > > Or is the recommended method just to backup, wipe the disk, install 3.0 > and start tracking -current that way? If it is, I'll document that > approach instead. > > N > -- > C.R.F. Consulting -- we're run to make me richer. . . > > 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 31 10:56:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03958 for freebsd-current-outgoing; Thu, 31 Dec 1998 10:56:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03941; Thu, 31 Dec 1998 10:56:09 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id NAA12412; Thu, 31 Dec 1998 13:55:47 -0500 (EST) Message-ID: <19981231135547.W4306@ns1.adsu.bellsouth.com> Date: Thu, 31 Dec 1998 13:55:47 -0500 From: Christian Kuhtz To: "Jonathan M. Bresler" , alexandr@mail.eecis.udel.edu Cc: dcs@newsguy.com, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199812311807.KAA27750@hub.freebsd.org> <199812311832.KAA01002@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812311832.KAA01002@hub.freebsd.org>; from Jonathan M. Bresler on Thu, Dec 31, 1998 at 10:32:29AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 10:32:29AM -0800, Jonathan M. Bresler wrote: [..] > 1. Wietse Venema's beta is better then many finished products. > We have been using it to deliver the FreeBSD mailing lists for > months. [..] Does it really make our product better if we deploy beta code in it? There is a reason why Wietse is so highly regarded, and that is because of the fact that he is so careful. So, if we trust his reputation, shouldn't we at least have the grace to follow his footsteps? If it's good stuff, it'll be around in a few months, and people who are clamoring to get Sendmail relief will most certainly be able to survive a few months longer. They have thus far. It is great that hub.freebsd.org has been running on it very succesfully. Wietse doesn't appear to care about it to move it to released stage? > 4. if you believe that there is a problem with postfix, please tell > me what it is. the problem must be one with postfix, not how its > labelled or who is hyping it. [..] Labels do make a difference. Many corporations have written Q&A rules according to which you cannot/must not deploy any product and run production on it that is labeled as beta. It is completely irrelevant if it passes the internal Q&A if it is labeled as beta. We're one of them. And you can very well get fired for doing it anyway. I like vmailer^H^H^H^H^H^H^Hpostfix a lot and use it for lab purposes. But neither I nor anyone else anywhere in this huge organization can deploy it currently for that very reason. We should be conservative in released components, particularly with regards to commercial use. I am not against Postfix, I believe in Postfix. Yes, I am very unhappy with Sendmail's state at the present time. Sendmail is not part of the equasion, it is how we do releases and how carefully we maintain the code base. Introducing something that's labeled as beta into a release is not a part of careful code base maintenance, IMHO. If memory serves, Postfix would indeed be the only thing in /usr/src/contrib which is beta. We are setting what might be a perhaps dangerous precedent. Even though I like the idea of having Postfix around. Cheers, Chris -- "Economics is extremely useful as a form of employment for economists." -- John Kenneth Galbraith [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 11:05:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05394 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:05:18 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from netscape.com (h-205-217-237-47.netscape.com [205.217.237.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05383 for ; Thu, 31 Dec 1998 11:05:17 -0800 (PST) (envelope-from dboreham@netscape.com) Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by netscape.com (8.8.5/8.8.5) with ESMTP id LAA17017 for ; Thu, 31 Dec 1998 11:04:56 -0800 (PST) Received: from netscape.com ([208.12.63.45]) by dredd.mcom.com (Netscape Messaging Server 4.0) with ESMTP id F4UFO800.QMV for ; Thu, 31 Dec 1998 11:04:56 -0800 Message-ID: <368BCBE7.BCC1FFB5@netscape.com> Date: Thu, 31 Dec 1998 11:09:27 -0800 From: dboreham@netscape.com (David Boreham) X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <76ec7v$1rh$1@FreeBSD.csie.NCTU.edu.tw>, shmit@kublai.com (Brian Cully) wrote: > On Wed, Dec 30, 1998 at 12:55:02PM -0800, Mike Smith wrote: > > Cool; thanks for the review. Anyone else using either the Netscape > > server or experimenting with the OpenLDAP implementation are invited to > > speak up; this sort of input's really useful. This is an interesting thread. One point which should be made, and I've not seen made is that the protocol (LDAP) needs to be discussed separately from the server implementation (e.g. Netscape, Novell). One might argue that LDAP server implementation XYZ is inefficient in some respect, but that an efficient LDAP server for the task at hand could be build. For example, those planning to roll their own authentication service might be well served by using a subset of the LDAP protocol, but building their own server, rather than inventing a new world from scratch. > I've done the evaluation here for the Netscape server, and was > fairly unimpressed even though we had a simple setup (no distributed > servers, for example, and from what I understand, this is where > Netscape's main problems lie). The current Netscape LDAP server supports multi-server replication where each distinct DIT subtree must be mastered on one and only one server. Thus read load can be distributed across multiple replication consumers easily. To partition the data, in order to for example constrain the size of the working set of each server, you currently need to have an intelligent client. The client needs to have some knowledge of the partitioning scheme in order to locate the server which contains the target entry. Perhaps this is what you mean ? > I've heard some very good things about OpenLDAP, but we haven't > recieved our eval copy yet. But from reading the literature about > the design and implementation, it sounds really sweet. Curious. OpenLDAP represents ongoing development of the University of Michigan LDAP server code base. This was also the basis for the Netscape product. Essentially the two share the same design and implementation (albeit diverged over a period of three 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 31 11:15:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06686 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:15:26 -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 LAA06678 for ; Thu, 31 Dec 1998 11:15:24 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id NAA01936; Thu, 31 Dec 1998 13:14:56 -0600 (CST) (envelope-from dick) Date: Thu, 31 Dec 1998 13:14:56 -0600 From: "Richard Seaman, Jr." To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: threads, linuxthreads, breaks include files Message-ID: <19981231131456.C391@tar.com> References: <19981231020349.A1376@top.worldcontrol.com> <19981231091155.F2783@tar.com> <19981231093423.I2783@tar.com> <19981231103436.A17976@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19981231103436.A17976@nuxi.com>; from David O'Brien on Thu, Dec 31, 1998 at 10:34:36AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 10:34:36AM -0800, David O'Brien wrote: > Isn't Linuxthreads in the CVS tree now? Yes, if you're running in linux emulation mode, and if you compile kernel/world with COMPAT_LINUX_THREADS, and if your app is compiled on a linux machine (or, if you can figure out how to do it, cross-compiled for linux on a FreeBSD machine). The question addressed some patches that allow a linuxthreads "port" to run. In other words, you want to compile a FreeBSD app, or a port of a linux app, to run in FreeBSD native (no Linux emulation) using the ported linux threads that also run in FreeBSD native. The linux threads "port" is realistically just a 1-1 kernel pthread implementation. The idea is that some people might want a kernel thread library, and this is a quick and easy way to get one. -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 11:19:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07216 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:19:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07208 for ; Thu, 31 Dec 1998 11:19:32 -0800 (PST) (envelope-from dboreham@netscape.com) Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by netscape.com (8.8.5/8.8.5) with ESMTP id LAA24532 for ; Thu, 31 Dec 1998 11:19:10 -0800 (PST) Received: from netscape.com ([208.12.63.45]) by dredd.mcom.com (Netscape Messaging Server 4.0) with ESMTP id F4UGBX00.DNB for ; Thu, 31 Dec 1998 11:19:09 -0800 Message-ID: <368BCF3D.B6ACC60D@netscape.com> Date: Thu, 31 Dec 1998 11:23:41 -0800 From: dboreham@netscape.com (David Boreham) X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <76egdr$50r$1@FreeBSD.csie.NCTU.edu.tw>, gpalmer@FreeBSD.ORG ("Gary Palmer") wrote: > greately increases the resources required to run a local LDAP replica (lets > face it, most of the free LDAP servers use DBM as a backend, and I believe > Netscapes directory server does also, which isn't the fastest product on the > planet) Netscape's server uses Berkeley DB2, not DBM. I find it to be quite fast enough. The protocol encode/decode and access control rule evaluation code is the current bottleneck on searches. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 11:22:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07720 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:22:42 -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 LAA07707 for ; Thu, 31 Dec 1998 11:22:39 -0800 (PST) (envelope-from gaylord@gaylord.async.vt.edu) Received: (from gaylord@localhost) by gaylord.async.vt.edu (8.9.1/8.8.5) id OAA39518 for freebsd-current@freebsd.org; Thu, 31 Dec 1998 14:24:43 -0500 (EST) From: Clark Gaylord Message-Id: <199812311924.OAA39518@gaylord.async.vt.edu> Subject: Re: New aout-to-elf build failures. To: freebsd-current@FreeBSD.ORG Date: Thu, 31 Dec 1998 14:24:42 -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 > Subject: Re: New aout-to-elf build failures. > Date: Wed, 30 Dec 1998 21:11:22 -0800 > From: "Jordan K. Hubbard" > > > Ok, as I'm not and haven't done any of the work I certainly don't have any > > say, but just to add something that you might want to consider. I've been > > thinking that it would be nice if the aout to elf build would be supported > > till a little after the branch split. This would allow people following > > stable the option of source upgrades the whole way through. But maybe this > > adds to much "cruft" to the start of the new stable branch? > > I don't mind them following -current up to and after the branch, but > they need to go ELF before that. It's just getting too difficult to > support both worlds and I no longer even have a 3.0/a.out box handy > here for testing such an environment. I have a stupid question: how do I know if I have an elf box? Maybe this is really trivial, but when I explain my confusion maybe it won't make me look quite so stupid (more foolish maybe, but hopefully not so stupid ;-): I tried aout-to-elf rather prematurely and it failed miserably; I then did a number of especially stupid things to try to kludge around the problem; finally, with a barely hobbling system I dl'ed a binary distribution, did a make world, make aout-to-elf, etc. Interestingly, /etc/objformat still said AOUT, but all the .../lib stuff seemed to be elf, so I just manually overwrote that. Anyway... But I still have a bunch of stuff in .../lib/aout (and maybe some aout stuff in .../lib ... I told you I did some stupid stuff). Do I have an "elf" system in the Hubbard sense of the word? I've tried moving stuff out of .../lib/aout when there were updated libs in .../lib, but there's a lot of "hey, I need blah.k (notwithstanding that blah.l is in elf for some l>k)" and subsequent rebuilds of almost everything on my system. But I can't build netscape (which seems to want the older libs I have in a.out). I also use X in binary; is that a.out or elf (I use the 3.0 binaries; don't have room for sources anymore). Can I transliterate the aout stuff and get it to work? (Maybe this was supposed to have been done by aout-to-elf, but my numerous fuddlings probably fubar'ed it.) Part of my problem is that I really don't understand a.out vs elf. Is there something I can read to better describe the different formats and how libraries are located (e.g., why do I need to have blah.k when I now have blah.l?) I'm not really much of a hacker, just a user that doesn't mind getting a little bloody every now and then. Thanks, CLark -- Clark K. Gaylord Blacksburg, Virginia USA cgaylord@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 11:23:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA07927 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:23:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.nowhere (ppp18389.on.bellglobal.com [206.172.130.69]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA07916; Thu, 31 Dec 1998 11:23:10 -0800 (PST) (envelope-from vanderh@ecf.toronto.edu) Received: (from tim@localhost) by localhost.nowhere (8.9.1/8.9.1) id OAA04697; Thu, 31 Dec 1998 14:22:36 -0500 (EST) (envelope-from tim) Message-ID: <19981231142235.A4687@mad> Date: Thu, 31 Dec 1998 14:22:35 -0500 From: Tim Vanderhoek To: alexandr@mail.eecis.udel.edu, "Jonathan M. Bresler" Cc: dcs@newsguy.com, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199812311807.KAA27750@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199812311807.KAA27750@hub.freebsd.org>; from alexandr@mail.eecis.udel.edu on Thu, Dec 31, 1998 at 10:07:32AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 10:07:32AM -0800, alexandr@mail.eecis.udel.edu wrote: > > we've almost always been a major version behind). It took forever to > get perl5 into the tree. We still haven't upgraded to the latest > version of CVS. Yada, yada, yada... And there are some really old PRs about tar, etc. being out-of-date. You sound like a potential volunteer! :-) -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 11:30:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08716 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:30:57 -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 LAA08711 for ; Thu, 31 Dec 1998 11:30:55 -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 0zvnng-0000TI-00; Thu, 31 Dec 1998 12:30:28 -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 MAA00612; Thu, 31 Dec 1998 12:28:23 -0700 (MST) Message-Id: <199812311928.MAA00612@harmony.village.org> To: Bill Paul Subject: Re: bus_space_foo and bus_dmamap_foo Cc: current@FreeBSD.ORG In-reply-to: Your message of "Thu, 31 Dec 1998 13:58:06 EST." <199812311858.NAA05191@skynet.ctr.columbia.edu> References: <199812311858.NAA05191@skynet.ctr.columbia.edu> Date: Thu, 31 Dec 1998 12:28:23 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812311858.NAA05191@skynet.ctr.columbia.edu> Bill Paul writes: : For those of you dying for a change of pace, here's a purely technical : posting rather than a political one. The attempted no commit zone enforcemnt getting to you? : At some point, somebody brought over a bunch of machine-independent bus : support from NetBSD, in the form of the bus_space_foo() and : bus_dmamap_foo() code. Unfortunately, it seems whoever did it left the : job half done: Somebody == Justin Gibbs. He did it for an older version of NetBSD's bus space stuff. It needs to be updated. Just did add the ability to have a memory mapped only driver (or an I/O mapped only driver) rather than always going through the if statement to get better performance. There were also some minor improvements to the DMA interface which allowed better performance on some machines. : - While we have things like bus_space_read_1(), which takes : bus_space_handle_t and bus_space_tag_t arguments, we do not have : the necessary functions to create the bus space handle and tag : in the first place. From what I can tell, drivers manually assign : them by setting them to I386_BUS_SPACE_MEM or I386_BUS_SPACE_PIO : (for the tag) or the iobase or membase address (for the handle). : This obviously is not machine independent. True. Likely the NetBSD interface should be adopted, unless there is a compelling reason not to do this. : - There is no bus_dmamap_load_mbuf(). This makes it very hard to use : the bus_dmamap stuff for network interface drivers. (A good example : of how to use this stuff in general would be nice too.) Hmmm, how does NetBSD do this stuff? It has been a while since I've looked. : - There are no man pages. That is an easy gap to fill. I'll see about committing man pages soon. : Is anybody actually working on filling in these gaps? (No, _I'm_ not : going to do it; I have enough to worry about.) If so, could somebody : tell me when (in specific terms) it will be done? I'd very much like to : be able to make all of the drivers that I've written machine independent, : at least enough to have them compile on both the i386 and alpha : architectures. Looking at them just now, I see that you are absolutely correct. I believe that Justin was looking at filling the gaps when he had time, but I think he's rather busy these days. So I don't think there is a specific timeline for these improvements. : We now return you to your regularly scheduled sabre-rattling. "The no commit zones are an illegal usurption of our sovereign rights. We will continue to commit in the no commit zone in protest." Warner "No elves were harming in the making of this message" Losh To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 11:31:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA08954 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:31:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from geocities.com (mail11.geocities.com [209.1.224.139]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA08948 for ; Thu, 31 Dec 1998 11:31:32 -0800 (PST) (envelope-from bhaskin@geocities.com) Received: from brianjr (220R1.infinitecom.com [199.176.148.87] (may be forged)) by geocities.com (8.9.1/8.9.1) with SMTP id LAA00177; Thu, 31 Dec 1998 11:29:44 -0800 (PST) From: "Brian Haskin" To: "Jordan K. Hubbard" Cc: Subject: RE: New aout-to-elf build failures. Date: Thu, 31 Dec 1998 14:30:31 -0500 Message-ID: <000601be34f4$0789f9a0$0b00000a@brianjr.haskin.org> 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: <14243.915081082@zippy.cdrom.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: Jordan K. Hubbard [mailto:jkh@zippy.cdrom.com] > Sent: Thursday, December 31, 1998 12:11 AM > To: Brian Haskin > Cc: current@FreeBSD.ORG > Subject: Re: New aout-to-elf build failures. > > > > Ok, as I'm not and haven't done any of the work I certainly > don't have any > > say, but just to add something that you might want to consider. > I've been > > thinking that it would be nice if the aout to elf build would > be supported > > till a little after the branch split. This would allow people following > > stable the option of source upgrades the whole way through. But > maybe this > > adds to much "cruft" to the start of the new stable branch? > > I don't mind them following -current up to and after the branch, but > they need to go ELF before that. It's just getting too difficult to > support both worlds and I no longer even have a 3.0/a.out box handy > here for testing such an environment. > > - Jordan > I must have stated this wrong. Let me pull in another of your messages: > > I started getting worked up over this about how I needed to get all my > > machines caught up (I run -STABLE all over the place here), then realized: > > -stable people don't need to care about any of the above right now > anyway. :-) > > - Jordan Ok, what you've stated above along with the additional thought that they will care come Jan. 16 or whenever it is that the 3.0 branch splits into a new stable and current branch is the point I was trying to make. To state it another way, will there be an easy (source not binary) route for people at the end off the 2.2-stable branch to get to the beginning 3.0-stable branch? Also I just upgraded to -current using the 12/24 snap and then cvsuping the rest of the way. I see via /etc/objformat that I'm, by default, using elf for the binary format. Are the elf boot blocks and kernel being used by default also; how do I tell? Brian Haskin haskin@ptway.com Home page: http://www.geocities.com/ResearchTriangle/4333/ Always remember money is simply a level of indirection. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 11:31:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09019 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:31:59 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09010 for ; Thu, 31 Dec 1998 11:31:58 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id OAA12752; Thu, 31 Dec 1998 14:24:00 -0500 (EST) Message-ID: <19981231142400.X4306@ns1.adsu.bellsouth.com> Date: Thu, 31 Dec 1998 14:24:00 -0500 From: Christian Kuhtz To: David Boreham , freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: <368BCBE7.BCC1FFB5@netscape.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <368BCBE7.BCC1FFB5@netscape.com>; from David Boreham on Thu, Dec 31, 1998 at 11:09:27AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 11:09:27AM -0800, David Boreham wrote: > This is an interesting thread. > One point which should be made, and I've not seen > made is that the protocol (LDAP) needs to be > discussed separately from the server implementation > (e.g. Netscape, Novell). Yep. I'm guilty of that, too. ;( > > I've done the evaluation here for the Netscape server, and was > > fairly unimpressed even though we had a simple setup (no distributed > > servers, for example, and from what I understand, this is where > > Netscape's main problems lie). > > The current Netscape LDAP server supports multi-server > replication where each distinct DIT subtree must be > mastered on one and only one server. But you don't support multimaster. Which is a crucial in almost all of our applications. Replicating read-only tries is only good if the directory is used as a reference, but not when the intention is to make it an active container of information. > Thus read load can be distributed across multiple > replication consumers easily. But no commits/writes. All commits on a Netscape DS have to be made on a 'central' server (the owner/master of the tree). I think that's what the previous poster might've meant. > To partition the data, in order to for example > constrain the size of the working set of each > server, you currently need to have an intelligent > client. The client needs to have some knowledge > of the partitioning scheme in order to locate > the server which contains the target entry. > Perhaps this is what you mean ? That's a theoretical possibility.. Or you teach the directory multimaster and you can still have dumb clients. Assuming a lot of different devices, I don't think it is realistic to expect that all clients are equally intelligent or use the same algorithm to decide where to go. Particularly since, to my knowledge, there isn't even a notion of any type of standard for such behavior. And then there's the issue of me changing the directory and then what (short of going around and telling each client what to do). Use a directory find out where my tree lives? :) The index of all indeces? :) And then you still haven't solved the problem of what happens when your network gets partitioned and you lose access to the central site. Particularly in a SP network, it is by design that the operation keeps on running, even if you lose half your network. SP networks are usually designed to cope with at least 2 point if not 3 point failure. Sure, you can (again) go and teach the client. But then the client has to figure out which server to use and how to respond on failure and convergence. (two affinities: the affinity to cease a resource and the affinity to release a resource). Otherwise all load balancing goes to heck and you have to overengineer everything. That particular kind of overengineering is not an option. :) For instance, SS7 is designed so that the 'protocol' (read: the client) statically knows what to do in failure scenarios. It has no way of automagically learning. And it is very cumbersome to manage and work with. No, I will not let such technology invade my network. ;^) Cheers, Chris -- "Economics is extremely useful as a form of employment for economists." -- John Kenneth Galbraith [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 11:34:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09406 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:34:23 -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 LAA09400; Thu, 31 Dec 1998 11:34:20 -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 0zvnqz-0000TS-00; Thu, 31 Dec 1998 12:33:53 -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 MAA00653; Thu, 31 Dec 1998 12:31:48 -0700 (MST) Message-Id: <199812311931.MAA00653@harmony.village.org> To: "Jonathan M. Bresler" Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. Cc: committers@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 31 Dec 1998 10:32:29 PST." <199812311832.KAA01002@hub.freebsd.org> References: <199812311832.KAA01002@hub.freebsd.org> <199812311807.KAA27750@hub.freebsd.org> Date: Thu, 31 Dec 1998 12:31:48 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812311832.KAA01002@hub.freebsd.org> "Jonathan M. Bresler" writes: : 2. "new security holes and bugs are being found every day" is : false. the only "security holes and bugs" found recently are : along the lines of "world writeable directories are bad". If they are being found everyday, they aren't making it to bugtraq. A whole class of problems exist with the world writable directories, but it appears that a small, setgid program is going to close that void. I've not seen any other security related problems for postfix. And I've been looking closely... 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 31 11:39:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10016 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:39: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 LAA10011 for ; Thu, 31 Dec 1998 11:39:26 -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 0zvnvp-0000Tk-00; Thu, 31 Dec 1998 12:38:53 -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 MAA00744; Thu, 31 Dec 1998 12:36:48 -0700 (MST) Message-Id: <199812311936.MAA00744@harmony.village.org> To: Clark Gaylord Subject: Re: New aout-to-elf build failures. Cc: freebsd-current@FreeBSD.ORG In-reply-to: Your message of "Thu, 31 Dec 1998 14:24:42 EST." <199812311924.OAA39518@gaylord.async.vt.edu> References: <199812311924.OAA39518@gaylord.async.vt.edu> Date: Thu, 31 Dec 1998 12:36:48 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812311924.OAA39518@gaylord.async.vt.edu> Clark Gaylord writes: : I have a stupid question: how do I know if I have an elf box? file /bin/ls. If it says ELF blah blah blah, then it is highly likely that your system is ELF. : Can I transliterate the aout stuff and get it to work? (Maybe this : was supposed to have been done by aout-to-elf, but my numerous : fuddlings probably fubar'ed it.) No. : Part of my problem is that I really don't understand a.out vs elf. : Is there something I can read to better describe the different : formats and how libraries are located (e.g., why do I need to have : blah.k when I now have blah.l?) There is information about this in the handbook. I know there is a slightly revisionist history of object formats in it written by 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 31 11:39:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10031 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:39:31 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles121.castles.com [208.214.165.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10026 for ; Thu, 31 Dec 1998 11:39:29 -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 LAA01161; Thu, 31 Dec 1998 11:34:47 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812311934.LAA01161@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Jaye Mathisen cc: current@FreeBSD.ORG Subject: Re: OK, if you're caught in the middle... In-reply-to: Your message of "Thu, 31 Dec 1998 01:17:16 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Dec 1998 11:34:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > The following worked for me to finish getting from aout to elf. > > vi /etc/make.conf, uncomment NOSENDMAIL and NOPERL (perl fails in > aout-to-elf install with some problem with gv.h. I uncommented NOSENDMAIL > since I could, onthe assumptiong I would get an elf sendmail and perl > later). Build the world first, to make sure that /boot is up to date. > echo '/boot/loader' > /boot.config > disklabel -B bootdevices Do one of these or the other, but _not_both_. Having a /boot.config file with the new boot1/boot2 is not required, and makes the boot process much more noisy than it needs to be. -- \\ 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 31 11:40:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10184 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:40:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (tibet-29.ppp.hooked.net [206.80.9.157]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10167 for ; Thu, 31 Dec 1998 11:40:16 -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 LAA03203; Thu, 31 Dec 1998 11:42:33 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 31 Dec 1998 11:42:33 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: "Brian W. Buchanan" cc: current Subject: Re: egcs chokes on netinet/in.h.. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Brian W. Buchanan wrote: > This seems like a rather stupid restriction of ANSI C++, and in any case, > the compiler shouldn't treat it as a fatal error unless you specified > -ansi -pedantic. To fix this without hacking the compiler to fix the > bug, perhaps try wrapping the include directive: Perhaps, but it's still technically broken code, and the "correct" fix would only affect a few programs? But the thing is egcs is supposed to be an ANSI C++ compiler, so -ansi shouldn't be required (and it isn't). You've obviously not used a recent version of egcs have you. Watching const -> non const being treated as a fatal error as long as there's no cast... boy that was fun! > extern "C" { > #include > } I'd rather not "fix" our code, *sigh*. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 11:48:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10816 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:48:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from luke.srtc.com (luke.srtc.com [208.132.236.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA10802 for ; Thu, 31 Dec 1998 11:48:35 -0800 (PST) (envelope-from jdeppen@ruby.srtc.com) Received: from SRTC (ruby [208.132.236.2]) by luke.srtc.com (8.6.12/8.6.9) with ESMTP id OAA05494; Thu, 31 Dec 1998 14:44:21 -0500 Received: from uraninite.srtc.com by SRTC (950413.SGI.8.6.12/SRTC-Client) id OAA07146; Thu, 31 Dec 1998 14:47:08 -0500 Received: from uraninite by uraninite.srtc.com (SMI-8.6/SMI-SVR4) id OAA16045; Thu, 31 Dec 1998 14:47:44 -0500 Message-Id: <199812311947.OAA16045@uraninite.srtc.com> Date: Thu, 31 Dec 1998 14:47:44 -0500 (EST) From: John Deppen Reply-To: John Deppen Subject: pthreads or linuxthreads To: billf@chc-chimes.com, dick@tar.com Cc: current@FreeBSD.ORG MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Content-MD5: 6UxvpenT8m9KIl5GsZJOkQ== X-Mailer: dtmail 1.2.1 CDE Version 1.2.1 SunOS 5.6 sun4u sparc Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Is there any way around the following problem? > > > > When the pthreads are linked I get an undefined reference to 'poll'. (Called > > from within a thread) > > However, when this is removed I obviously get undefined references to > > all of the pthread_.. functions. > > > > Thanks in advance for any help, > Are you linking the correct libraries as well? >From the makefile: FLAGS+=-DTERMCAP -DKLUDGELINEMODE -DUSE_TERMIO #-DAUTHENTICATION -DENCRYPTION CFLAGS+=-DENV_HACK CFLAGS+=-DSKEY CFLAGS+=-I/usr/src/lib -Wall #CFLAGS+=-I/usr/src/lib -pthread -Wall ( <- when using thread functions ) CC=gcc The application compiles/links/executes OK when threads are not used. >> Isn't Linuxthreads in the CVS tree now? > >Yes, if you're running in linux emulation mode, and if you compile >kernel/world with COMPAT_LINUX_THREADS, and if your app is compiled >on a linux machine (or, if you can figure out how to do it, cross-compiled >for linux on a FreeBSD machine). > >The question addressed some patches that allow a linuxthreads "port" >to run. In other words, you want to compile a FreeBSD app, or a >port of a linux app, to run in FreeBSD native (no Linux emulation) >using the ported linux threads that also run in FreeBSD native. > >The linux threads "port" is realistically just a 1-1 kernel pthread >implementation. The idea is that some people might want a kernel >thread library, and this is a quick and easy way to get one. Is there any effort being made to fix the problems with pthreads? Or is there any other way around the problems other than converting the application to Linux? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 11:57:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11605 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:57:04 -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 LAA11598 for ; Thu, 31 Dec 1998 11:57:02 -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 VAA26053; Thu, 31 Dec 1998 21:02:30 +0100 (CET) X-Authentication-Warning: korin.warman.org.pl: abial owned process doing -bs Date: Thu, 31 Dec 1998 21:02:30 +0100 (CET) From: Andrzej Bialecki X-Sender: abial@korin.warman.org.pl To: Nik Clayton cc: Kazutaka YOKOTA , current@FreeBSD.ORG Subject: Re: future of syscons In-Reply-To: <19981230201432.A6797@catkin.nothing-going-on.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 30 Dec 1998, Nik Clayton wrote: > On Tue, Dec 22, 1998 at 10:31:07PM +0900, Kazutaka YOKOTA wrote: > > I wrote some notes on the future development plan of our console > > driver syscons. > > > > I would appriciate if you could give me some comments. > > I know very little about the architectural issues. I'd like to suggest a > feature though -- I'd like some mechanism for userland programs to get a > dump of the current screen (as text if it's a textmode screen, as an > image if it isn't). And I for my part (having implemented recently a terminal emulator for bootloader) would suggest perhaps obvious thing: it would be nice to implement screen manipulation routines in terms of termcap capabilities, i.e. to have functions that do "ho", "cl", "cd", "cm", "AF" etc, etc... Then, writing actual terminal emulator module would be sweet and painless, because you'd only decode escape sequences differently, and the rest of the code would be the same. As I said - perhaps it's obvious, but I thought I'd better mention it... :-) 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 Thu Dec 31 11:58:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA11922 for freebsd-current-outgoing; Thu, 31 Dec 1998 11:58:23 -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 LAA11913 for ; Thu, 31 Dec 1998 11:58:20 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id NAA02256; Thu, 31 Dec 1998 13:57:53 -0600 (CST) (envelope-from dick) Date: Thu, 31 Dec 1998 13:57:53 -0600 From: "Richard Seaman, Jr." To: John Deppen Cc: billf@chc-chimes.com, current@FreeBSD.ORG Subject: Re: pthreads or linuxthreads Message-ID: <19981231135753.A1968@tar.com> References: <199812311947.OAA16045@uraninite.srtc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199812311947.OAA16045@uraninite.srtc.com>; from John Deppen on Thu, Dec 31, 1998 at 02:47:44PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 02:47:44PM -0500, John Deppen wrote: > > > > Is there any way around the following problem? > > > > > > When the pthreads are linked I get an undefined reference to 'poll'. (Called > > > from within a thread) > > > However, when this is removed I obviously get undefined references to > > > all of the pthread_.. functions. > > > > > > Thanks in advance for any help, > > > Are you linking the correct libraries as well? > > >From the makefile: > > FLAGS+=-DTERMCAP -DKLUDGELINEMODE -DUSE_TERMIO #-DAUTHENTICATION -DENCRYPTION > CFLAGS+=-DENV_HACK > CFLAGS+=-DSKEY > CFLAGS+=-I/usr/src/lib -Wall > #CFLAGS+=-I/usr/src/lib -pthread -Wall ( <- when using thread functions ) > CC=gcc > > The application compiles/links/executes OK when threads are not used. When you link with -pthread, you are linking in the library libc_r which brings in the "user thread" pthread library. AFAIK, the poll call is not yet implemented in this library. I don't know if this is being worked on at present. > >The linux threads "port" is realistically just a 1-1 kernel pthread > >implementation. The idea is that some people might want a kernel > >thread library, and this is a quick and easy way to get one. > > Is there any effort being made to fix the problems with pthreads? Or is there > any other way around the problems other than converting the application > to Linux? If you link with the linuxthreads pthreads library, you should be able to get a poll function. However, its still experimental (the linux threads port, that is), and its not part of the standard FreeBSD distribution. If you want to try to play around with it, look at http://lt.tar.com . -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 12:00:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12164 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:00:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from netscape.com (h-205-217-237-46.netscape.com [205.217.237.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12155 for ; Thu, 31 Dec 1998 12:00:40 -0800 (PST) (envelope-from dboreham@netscape.com) Received: from dredd.mcom.com (dredd.mcom.com [205.217.237.54]) by netscape.com (8.8.5/8.8.5) with ESMTP id MAA26869 for ; Thu, 31 Dec 1998 12:00:19 -0800 (PST) Received: from netscape.com ([208.12.63.45]) by dredd.mcom.com (Netscape Messaging Server 4.0) with ESMTP id F4UI8I00.ANH for ; Thu, 31 Dec 1998 12:00:18 -0800 Message-ID: <368BD8DF.C478B885@netscape.com> Date: Thu, 31 Dec 1998 12:04:47 -0800 From: dboreham@netscape.com (David Boreham) X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Re: NOW/MOSIX/Beowulf References: <368BCBE7.BCC1FFB5@netscape.com> <19981231142400.X4306@ns1.adsu.bellsouth.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Christian Kuhtz wrote: > > The current Netscape LDAP server supports multi-server > > replication where each distinct DIT subtree must be > > mastered on one and only one server. > > But you don't support multimaster. Which is a crucial in almost all of our > applications. Replicating read-only tries is only good if the directory is > used as a reference, but not when the intention is to make it an active > container of information. Multimaster replication will be in the next major release. Note that MMR does not solve all the problems associated with distributed databases. For example, a client performs an update on one master. It then queries the directory service to read back the modified entry. Due to load balancing it reads from a different server which has not yet received the update. Client therefore sees inconsistent data. In the end there are fundamental laws of physics involved, which no fancy protocol and no army of wizzard coders can transgress. > > Thus read load can be distributed across multiple > > replication consumers easily. > > But no commits/writes. All commits on a Netscape DS have to be made on a > 'central' server (the owner/master of the tree). I think that's what the > previous poster might've meant. Not quite true. For a given subtree, all writes must be made on a particular designated server. Provided the data is partitioned across the tree, multiple masters are a reality. > That's a theoretical possibility.. Yes, I agree. A client should not need knowledge of the service topology. Various extensions to the LDAP protocol, the X.500 information model, and our server implementation have been considered to "solve" this problem. Generically it's termed "the distribution problem" in Directory circles. Prototype implementations are in use on my.netscape.com and www.netscape.com and webmail.netscape.com Current product supports LDAPv3 referrals. Clients may connect to an LDAP server of their choice (perhaps determined by DHCP or DNS) and submit a query. That server may refer the client to one or more other servers, which the client may contact in order to resolve the query. Network traffic could potentially be optimized by forwarding the query from server to server rather than having the client re-submit to referenced servers. This forwarding is termed "chaining" in Directory parlance, and could be implemented by any LDAP server transparently to the client. We have an in-house custom server which does chaining, but the current product does not. In any event, the mechanisms for client query interaction in a distributed environment are present in LDAPv3. However, in order to make distribution practical, some additions are needed on the server side. Currently referrals are statically configured. Referral decisions should be made by the server based on a real understanding by it of the service topology and partitioning schemes employed. Clients also need a way to ask a server for the distinguished name of a new entry they wish to add to the service. These are areas in which work is ongoing. Anyway, fascinating as this is, it's going well off topic. Follow-ups should goto to ietf-ldapext@netscape.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 31 12:09:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12973 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:09:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles121.castles.com [208.214.165.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12962; Thu, 31 Dec 1998 12:09:15 -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 MAA01368; Thu, 31 Dec 1998 12:06:19 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812312006.MAA01368@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jonathan M. Bresler" cc: mark@grondar.za, dcs@newsguy.com, alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-reply-to: Your message of "Thu, 31 Dec 1998 08:15:54 PST." <199812311615.IAA15286@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Dec 1998 12:06:18 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Date: Thu, 31 Dec 1998 17:10:22 +0200 > > From: Mark Murray > > > > We gain the ability to emphasise Postfix and de-emphasise Sendmail. > > After an appropriate period, we gain the ability to nuke Sendmail > > as Postfix has been solidly tested/used/ported/integrated for > > "long enough". No combustion over definitions of "long enough", > > please :-). > > WHOA!!!!! > > what if no one else likes postfix. > > postfix is coming into the tree as /usr/src/contrib. > sendmail is the default mail transfer agent. > individual users can switch either machines to use postfix as > the mta. > there is no intention of removing sendmail from the tree. This clearly demonstrates that there is no mandate, nor no technical justification for bringing postfix in. Please make a port of it and stay with convention. Now is not a good time for a -core member to be demonstrating personal bias over established convention with regards to the FreeBSD source tree. -- \\ 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 31 12:09:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13087 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:09:28 -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 MAA13040 for ; Thu, 31 Dec 1998 12:09:26 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.1/8.9.1) id MAA26610; Thu, 31 Dec 1998 12:09:03 -0800 (PST) (envelope-from obrien) Message-ID: <19981231120902.D17976@nuxi.com> Date: Thu, 31 Dec 1998 12:09:02 -0800 From: "David O'Brien" To: "Richard Seaman, Jr." Cc: freebsd-current@FreeBSD.ORG Subject: Re: threads, linuxthreads, breaks include files Reply-To: obrien@NUXI.com References: <19981231020349.A1376@top.worldcontrol.com> <19981231091155.F2783@tar.com> <19981231093423.I2783@tar.com> <19981231103436.A17976@nuxi.com> <19981231131456.C391@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19981231131456.C391@tar.com>; from Richard Seaman, Jr. on Thu, Dec 31, 1998 at 01:14:56PM -0600 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 > The linux threads "port" is realistically just a 1-1 kernel pthread > implementation. The idea is that some people might want a kernel > thread library, and this is a quick and easy way to get one. Sounds useful. Have you packaged it up as a port and sent a PR to get it committed? -- -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 12:15:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13657 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:15:20 -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 MAA13649; Thu, 31 Dec 1998 12:15:18 -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 VAA96478; Thu, 31 Dec 1998 21:11:28 +0100 (CET) To: "Steven P. Donegan" cc: The Hermit Hacker , "Daniel C. Sobral" , Mark Murray , "Jonathan M. Bresler" , alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-reply-to: Your message of "Thu, 31 Dec 1998 08:10:26 PST." Date: Thu, 31 Dec 1998 21:11:27 +0100 Message-ID: <96476.915135087@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , "Steven P. Donegan" writes: >On Thu, 31 Dec 1998, The Hermit Hacker wrote: > >> >> Here here...I trust and like sendmail, and have no intentions of >> switching from it... >> > >Not to flame at all - but what wonderful things does postfix bring that >would induce anyone to move away from sendmail? Simplicity. Now, stop this discussion please, you still have sendmail if that makes you happy, others have postfix if that makes them happy. You're wasting email bandwidth discussing taste, that is pointless. Happy new year! -- 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 Thu Dec 31 12:16:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13976 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:16:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles121.castles.com [208.214.165.121]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13971 for ; Thu, 31 Dec 1998 12:16:20 -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 MAA01416; Thu, 31 Dec 1998 12:13:04 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812312013.MAA01416@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christian Kuhtz cc: Peter Wemm , Gregory Bond , current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-reply-to: Your message of "Thu, 31 Dec 1998 12:30:26 EST." <19981231123026.Q4306@ns1.adsu.bellsouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Dec 1998 12:13:03 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Dec 31, 1998 at 02:44:05PM +0800, Peter Wemm wrote: > > Not quite.. The 3.0 CD shipped with an ELF world, but an a.out kernel and > > 3.0-level a.out bootblocks. You should be able to type a "/boot/loader" at > > the boot prompt and be able to use the ELF-aware bootloader without any > > problems. Assuming this works, you can type: > > echo /boot/loader > /boot.config > > And you're elf kernel capable. > > Appears this should be /boot/boot.config according to what the BIX messages > say. That's BTX, and /boot/boot.conf (very soon to become /boot/loader.rc I suspect) > My /boot/boot.config contains the following line > > /boot/loader That's fortunate; it would be ignored. > And the message before the 10 second wait is that it can't find a > /boot/boot.config file. Placing boot.config in / yields the same result. /boot.config is read by the boot1/boot2 code. -- \\ 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 31 12:24:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14465 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:24:31 -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 MAA14460 for ; Thu, 31 Dec 1998 12:24:29 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id OAA02399; Thu, 31 Dec 1998 14:24:05 -0600 (CST) (envelope-from dick) Date: Thu, 31 Dec 1998 14:24:05 -0600 From: "Richard Seaman, Jr." To: "David O'Brien" Cc: freebsd-current@FreeBSD.ORG Subject: Re: threads, linuxthreads, breaks include files Message-ID: <19981231142405.C1968@tar.com> References: <19981231020349.A1376@top.worldcontrol.com> <19981231091155.F2783@tar.com> <19981231093423.I2783@tar.com> <19981231103436.A17976@nuxi.com> <19981231131456.C391@tar.com> <19981231120902.D17976@nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <19981231120902.D17976@nuxi.com>; from David O'Brien on Thu, Dec 31, 1998 at 12:09:02PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 12:09:02PM -0800, David O'Brien wrote: > > The linux threads "port" is realistically just a 1-1 kernel pthread > > implementation. The idea is that some people might want a kernel > > thread library, and this is a quick and easy way to get one. > > Sounds useful. Have you packaged it up as a port and sent a PR to get it > committed? Its in the works. I was hoping a few people might tinker with it first. Plus, it needs the same kernel patches that the linux threads emulation needs. Plus, to make it truely useable, there are some patches to the posix priority scheduler that need to be made (I think these are in the works), and some patches to libc that need to be made (I'm working on some). -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 12:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14949 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:28:12 -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 MAA14943 for ; Thu, 31 Dec 1998 12:28:11 -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 PAA06948; Thu, 31 Dec 1998 15:27:48 -0500 (EST) (envelope-from wollman) Date: Thu, 31 Dec 1998 15:27:48 -0500 (EST) From: Garrett Wollman Message-Id: <199812312027.PAA06948@khavrinen.lcs.mit.edu> To: Alex Zepeda Cc: "Brian W. Buchanan" , current Subject: Re: egcs chokes on netinet/in.h.. In-Reply-To: References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Perhaps, but it's still technically broken code No. It is perfectly correct, Standard C code. It is not C++ code, nor does it claim to be. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 12:33:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA15743 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:33:36 -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 MAA15738 for ; Thu, 31 Dec 1998 12:33:34 -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 PAA06966; Thu, 31 Dec 1998 15:33:11 -0500 (EST) (envelope-from wollman) Date: Thu, 31 Dec 1998 15:33:11 -0500 (EST) From: Garrett Wollman Message-Id: <199812312033.PAA06966@khavrinen.lcs.mit.edu> To: Warner Losh Cc: Bill Paul , current@FreeBSD.ORG Subject: Re: bus_space_foo and bus_dmamap_foo In-Reply-To: <199812311928.MAA00612@harmony.village.org> References: <199812311858.NAA05191@skynet.ctr.columbia.edu> <199812311928.MAA00612@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > True. Likely the NetBSD interface should be adopted, unless there is > a compelling reason not to do this. A significant problem with all of this stuff is that it pre-dates DFR's bus code. This is a problem because it recapitulates the bus hierarchy which new-bus is there to construct for us. What would be preferable would be for this mechanism to be integrated with new-bus and the resource manager, so that when a driver requests a resource, it automatically gets any other context necessary to access that resource. The resource manager already has some hooks, in particular the r_vaddr member in struct resource, for that purpose, as well as the entire distinction between allocating and activating a resource. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 12:37:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16236 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:37:33 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16228; Thu, 31 Dec 1998 12:37:29 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id QAA16204; Thu, 31 Dec 1998 16:36:45 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 31 Dec 1998 16:36:44 -0400 (AST) From: The Hermit Hacker To: Mark Murray cc: "Steven P. Donegan" , "Daniel C. Sobral" , "Jonathan M. Bresler" , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199812311622.SAA60127@greenpeace.grondar.za> 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, 31 Dec 1998, Mark Murray wrote: > "Steven P. Donegan" wrote: > > Not to flame at all - but what wonderful things does postfix bring that > > would induce anyone to move away from sendmail? Move from something that > > works in the millions of systems, is understood by vast numbers of sys > > admins, etc? If postfix can do something sendmail can't what is it? And > > an answer that it's easier to configure isn't really valid for us lifer > > sendmail folks :-) > > 1) Vastly easier to configure :-). (Very valid for newbies). > 2) A heck of a lot more efficient. Sendmail is designed to work; > this is designed to work _fast_. > 3) More secure. The author is security-paranoid. This is good. > 4) So far (apart from myself) I have seen no rumblings at all > about removing Sendmail. I've seen a couple, myself included...today was the first I clued into the fact that ppl were suggesting *replacing* sendmail with postfix... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 31 12:41:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16747 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:41:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from burka.rdy.com (burka.rdy.com [205.149.163.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16741; Thu, 31 Dec 1998 12:41:18 -0800 (PST) (envelope-from dima@burka.rdy.com) Received: (from dima@localhost) by burka.rdy.com (8.9.1/RDY&DVV) id MAA78569; Thu, 31 Dec 1998 12:40:53 -0800 (PST) Message-Id: <199812312040.MAA78569@burka.rdy.com> Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199812311832.KAA01002@hub.freebsd.org> from "Jonathan M. Bresler" at "Dec 31, 1998 10:32:29 am" To: jmb@FreeBSD.ORG (Jonathan M. Bresler) Date: Thu, 31 Dec 1998 12:40:52 -0800 (PST) Cc: alexandr@mail.eecis.udel.edu, dcs@newsguy.com, committers@FreeBSD.ORG, current@FreeBSD.ORG X-Class: Fast Organization: HackerDome Reply-To: dima@best.net From: dima@best.net (Dima Ruban) 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 Jonathan M. Bresler writes: > > 4. if you believe that there is a problem with postfix, please tell > me what it is. the problem must be one with postfix, not how its > labelled or who is hyping it. The only potential problem is "do we really need it to be part of the standard system?" So far I don't see any real advantages in it. And unless we're about to switch to postfix and get rid of sendmail - I'm against this commit. > > jmb > > > I swear, it's almost like we've become victims of IBM's marketing > > machine. > -- dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 12:46:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17366 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:46:24 -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 MAA17361 for ; Thu, 31 Dec 1998 12:46:22 -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 0zvoyg-0000Vh-00; Thu, 31 Dec 1998 13:45:54 -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 NAA01055; Thu, 31 Dec 1998 13:43:50 -0700 (MST) Message-Id: <199812312043.NAA01055@harmony.village.org> To: Garrett Wollman Subject: Re: bus_space_foo and bus_dmamap_foo Cc: Bill Paul , current@FreeBSD.ORG In-reply-to: Your message of "Thu, 31 Dec 1998 15:33:11 EST." <199812312033.PAA06966@khavrinen.lcs.mit.edu> References: <199812312033.PAA06966@khavrinen.lcs.mit.edu> <199812311858.NAA05191@skynet.ctr.columbia.edu> <199812311928.MAA00612@harmony.village.org> Date: Thu, 31 Dec 1998 13:43:50 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199812312033.PAA06966@khavrinen.lcs.mit.edu> Garrett Wollman writes: : < said: : : > True. Likely the NetBSD interface should be adopted, unless there is : > a compelling reason not to do this. : : A significant problem with all of this stuff is that it pre-dates : DFR's bus code. This is a problem because it recapitulates the bus : hierarchy which new-bus is there to construct for us. It was my understanding from talking to Justin that these areas were basically orthoginal. busspace and busdma are used to talk to the hardware, while DFR's new bus stuff is more a configuration thing rather than talking to the actual hardware. : What would be preferable would be for this mechanism to be integrated : with new-bus and the resource manager, so that when a driver requests : a resource, it automatically gets any other context necessary to : access that resource. The resource manager already has some hooks, in : particular the r_vaddr member in struct resource, for that purpose, as : well as the entire distinction between allocating and activating a : resource. How do you view this integration? I'm confused... What needs to be integrated? 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 31 12:52:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18137 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:52:43 -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 MAA18132 for ; Thu, 31 Dec 1998 12:52:39 -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 0zvp4m-0000Vr-00; Thu, 31 Dec 1998 13:52:12 -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 NAA01102; Thu, 31 Dec 1998 13:50:08 -0700 (MST) Message-Id: <199812312050.NAA01102@harmony.village.org> To: Alex Zepeda Subject: Re: egcs chokes on netinet/in.h.. Cc: current In-reply-to: Your message of "Thu, 31 Dec 1998 11:42:33 PST." References: Date: Thu, 31 Dec 1998 13:50:08 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Alex Zepeda writes: : > extern "C" { : > #include : > } : : I'd rather not "fix" our code, *sigh*. Does the proposed fix fix the problem? I'd be surprised if it actually fixed the problem. extern "C" doesn't mean treat the following as having C semantics, just that the following has C linkage and calling conventions (which are two different things in this case). About the only thing that I could suggest would be to have a member that is named differently for C++, like motif and Xt do for a member named 'class'. Actually, I could see something like: struct ip_opts { struct in_addr ip_dst; /* first hop, 0 w/o src rt */ char ipopts[40]; /* actually variable in size */ }; #ifndef __cplusplus #define ip_opts ipopts #endif But that runs into problems when you say struct ip_opts, so that wouldn't work. I fear the best solution would be: struct ip_opts { struct in_addr ip_dst; /* first hop, 0 w/o src rt */ #ifdef __cplusplus char ipopts[40]; /* actually variable in size */ #else char ip_opts[40]; #endif }; And then in your code you could say something gross like: #ifndef __FreeBSD #define ioopts io_ipts #endif But then it will fail in the same way with newer compilers on other systems. 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 31 12:58:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA18834 for freebsd-current-outgoing; Thu, 31 Dec 1998 12:58:43 -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 MAA18829 for ; Thu, 31 Dec 1998 12:58:41 -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 PAA07052; Thu, 31 Dec 1998 15:58:18 -0500 (EST) (envelope-from wollman) Date: Thu, 31 Dec 1998 15:58:18 -0500 (EST) From: Garrett Wollman Message-Id: <199812312058.PAA07052@khavrinen.lcs.mit.edu> To: Warner Losh Cc: Garrett Wollman , Bill Paul , current@FreeBSD.ORG Subject: Re: bus_space_foo and bus_dmamap_foo In-Reply-To: <199812312043.NAA01055@harmony.village.org> References: <199812312033.PAA06966@khavrinen.lcs.mit.edu> <199812311858.NAA05191@skynet.ctr.columbia.edu> <199812311928.MAA00612@harmony.village.org> <199812312043.NAA01055@harmony.village.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > It was my understanding from talking to Justin that these areas were > basically orthoginal. busspace and busdma are used to talk to the > hardware, while DFR's new bus stuff is more a configuration thing > rather than talking to the actual hardware. How you talk to the hardware depends on where it is in the configuration graph. > How do you view this integration? I'm confused... What needs to be > integrated? When you activate a memory or I/O resource, the appropriate magic should happen such that included in the stuff you get back is something which can be used to access that resource quickly. Stuff like bus_space_alloc should be handled by the bus driver in coordination with the resource manager. (It should be implemented as a method call on the device's parent, so that it has all the necessary context pre-computed.) -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 13:00:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19233 for freebsd-current-outgoing; Thu, 31 Dec 1998 13:00:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from hawaii.conterra.com (hawaii.conterra.com [209.12.164.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19208; Thu, 31 Dec 1998 13:00:14 -0800 (PST) (envelope-from dmaddox@scsn.net) Received: from rhiannon.conterra.com (ppp107.conterra.com [209.12.169.107]) by hawaii.conterra.com (8.8.8/8.8.7) with ESMTP id PAA22553; Thu, 31 Dec 1998 15:59:47 -0500 (EST) Received: (from dmaddox@localhost) by rhiannon.conterra.com (8.9.1/8.9.1) id PAA01104; Thu, 31 Dec 1998 15:59:39 -0500 (EST) (envelope-from dmaddox) Date: Thu, 31 Dec 1998 15:59:39 -0500 From: "Donald J . Maddox" To: Poul-Henning Kamp Cc: "Steven P. Donegan" , The Hermit Hacker , "Daniel C. Sobral" , Mark Murray , "Jonathan M. Bresler" , alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. Message-ID: <19981231155939.A1068@rhiannon.conterra.com> Reply-To: dmaddox@conterra.com References: <96476.915135087@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <96476.915135087@critter.freebsd.dk>; from Poul-Henning Kamp on Thu, Dec 31, 1998 at 09:11:27PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's an interesting point, coming as it does from someone who just _took away_ choice from many of us by ripping functionality out of the tree without providing a replacement(e.g. VoxWare)... On Thu, Dec 31, 1998 at 09:11:27PM +0100, Poul-Henning Kamp wrote: > Now, stop this discussion please, you still have sendmail if that makes > you happy, others have postfix if that makes them happy. > > You're wasting email bandwidth discussing taste, that is pointless. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 13:06:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19783 for freebsd-current-outgoing; Thu, 31 Dec 1998 13:06:09 -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 NAA19777; Thu, 31 Dec 1998 13:06:07 -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 QAA38811; Thu, 31 Dec 1998 16:08:26 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 31 Dec 1998 16:08:26 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Mike Smith cc: "Jonathan M. Bresler" , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199812312006.MAA01368@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 Thu, 31 Dec 1998, Mike Smith wrote: > > > Date: Thu, 31 Dec 1998 17:10:22 +0200 > > > From: Mark Murray > > > > > > We gain the ability to emphasise Postfix and de-emphasise Sendmail. > > > After an appropriate period, we gain the ability to nuke Sendmail > > > as Postfix has been solidly tested/used/ported/integrated for > > > "long enough". No combustion over definitions of "long enough", > > > please :-). > > > > WHOA!!!!! > > > > what if no one else likes postfix. > > > > postfix is coming into the tree as /usr/src/contrib. > > sendmail is the default mail transfer agent. > > individual users can switch either machines to use postfix as > > the mta. > > there is no intention of removing sendmail from the tree. > > This clearly demonstrates that there is no mandate, nor no technical > justification for bringing postfix in. Please make a port of it and > stay with convention. I think Sun and many other distributions are chiming in that they WILL switch to postfix pretty soon, perhaps doing as jmb says and having both systems in place would be a good idea for a while, i'm sure if postfix gets a lot of bad press people will want it removed, but it's nice to have the latest and greatest, instead of a year later everyone whining about NOT having postfix in the base system. -Alfred oh, btw, how do i figure the size passed into an ioctl from the handler? :) > > Now is not a good time for a -core member to be demonstrating personal > bias over established convention with regards to the FreeBSD source tree. > > -- > \\ 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 13:12:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20433 for freebsd-current-outgoing; Thu, 31 Dec 1998 13:12:28 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20425 for ; Thu, 31 Dec 1998 13:12:26 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (832 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Thu, 31 Dec 1998 13:12:06 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Thu, 31 Dec 1998 13:12:06 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-current@FreeBSD.ORG Subject: dummy's guide to flag day, please? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG let's make it simple for us dummies. i am an a.outer who updates from current every few weeks. i usually backup update make buildworld go single user make installworld mergemaster -cv make a new kernel install kernel reboot let's hypothesize that on the 10th or so the messages have died down and i decide to give the wonderful new elf world a try. what are the steps (after backing up something awful:-)? i know, for example, there will be hidden gotchas in the ldconfig stuff in rc.conf.local. so please don't be too glib. thanks randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 13:21:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21169 for freebsd-current-outgoing; Thu, 31 Dec 1998 13:21:23 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21161; Thu, 31 Dec 1998 13:21:19 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id QAA04149; Thu, 31 Dec 1998 16:19:35 -0500 (EST) Date: Thu, 31 Dec 1998 16:19:35 -0500 (EST) From: Chuck Robey To: "Jonathan M. Bresler" cc: alexandr@mail.eecis.udel.edu, dcs@newsguy.com, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199812311832.KAA01002@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Jonathan M. Bresler wrote: > > Date: Thu, 31 Dec 1998 10:07:32 -0800 (PST) > > From: alexandr@mail.eecis.udel.edu > > > > However, here's my real bone of contention. The FreeBSD project has > > at last! Don't cheer too much, I think he's just going to change his story. He basically wants to dismember lots of the FreeBSD tree, and this is just a convenient excuse. One thing does kinda get me, tho. IBM, like Sun, has made several moves recently that have been friendly to open software. I'm not saying they're giving the store away, but things have changed at IBM since the 80's, and I don't think he's noticed it. > > I swear, it's almost like we've become victims of IBM's marketing > > machine. Jikes is just one of a hoard of software that IBM has been making public. All companies that do that should be clearly cheered for it, not taken to task because they're not totally perfect, nor because of rather poor, decade-old records. Times are changing, and IBM is not the boogie-man they used to be. You honestly ought to web-surf the IBM site, all the free and technically extremely interesting stuff there will take a good long while to read through. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 13:50:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23725 for freebsd-current-outgoing; Thu, 31 Dec 1998 13:50:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zippy.dyn.ml.org (spain-40.ppp.hooked.net [206.169.228.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23712 for ; Thu, 31 Dec 1998 13:50:51 -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 NAA40785; Thu, 31 Dec 1998 13:53:27 -0800 (PST) (envelope-from garbanzo@hooked.net) X-Authentication-Warning: zippy.dyn.ml.org: garbanzo owned process doing -bs Date: Thu, 31 Dec 1998 13:53:27 -0800 (PST) From: Alex Zepeda X-Sender: garbanzo@zippy.dyn.ml.org To: Warner Losh cc: current Subject: Re: egcs chokes on netinet/in.h.. In-Reply-To: <199812312050.NAA01102@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 > I fear the best solution would be: > struct ip_opts { > struct in_addr ip_dst; /* first hop, 0 w/o src rt */ > #ifdef __cplusplus > char ipopts[40]; /* actually variable in size */ > #else > char ip_opts[40]; > #endif > }; > > And then in your code you could say something gross like: [..] > But then it will fail in the same way with newer compilers on other > systems. The code itself doesn't access struct ip_opts anywhere, so I assume I'll just stick an appropiate #ifdef _cplusplus. *grumble* - 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 Thu Dec 31 14:28:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27734 for freebsd-current-outgoing; Thu, 31 Dec 1998 14:28:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa15-47.ix.netcom.com [207.93.148.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27495; Thu, 31 Dec 1998 14:28:45 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id OAA28553; Thu, 31 Dec 1998 14:28:14 -0800 (PST) (envelope-from tomdean) Date: Thu, 31 Dec 1998 14:28:14 -0800 (PST) Message-Id: <199812312228.OAA28553@ix.netcom.com> From: Thomas Dean To: scrappy@hub.org CC: mark@grondar.za, donegan@quick.net, dcs@newsguy.com, jmb@FreeBSD.ORG, committers@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: (message from The Hermit Hacker on Thu, 31 Dec 1998 16:36:44 -0400 (AST)) Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG KEEP SENDMAIL! If people want postfix, myspecialemail, etc., put them in ports. Sendmail is a MUST. Sendmail should be in the mainline of the source tree. If you don't know why, I am sorry! tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 14:55:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29750 for freebsd-current-outgoing; Thu, 31 Dec 1998 14:55:42 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA29744 for ; Thu, 31 Dec 1998 14:55:39 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA05644; Thu, 31 Dec 1998 18:00:10 -0500 From: Bill Paul Message-Id: <199812312300.SAA05644@skynet.ctr.columbia.edu> Subject: Re: bus_space_foo and bus_dmamap_foo To: imp@village.org (Warner Losh) Date: Thu, 31 Dec 1998 18:00:08 -0500 (EST) Cc: current@FreeBSD.ORG In-Reply-To: <199812311928.MAA00612@harmony.village.org> from "Warner Losh" at Dec 31, 98 12:28:23 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Of all the gin joints in all the towns in all the world, Warner Losh had to walk into mine and say: > : - There is no bus_dmamap_load_mbuf(). This makes it very hard to use > : the bus_dmamap stuff for network interface drivers. (A good example > : of how to use this stuff in general would be nice too.) > > Hmmm, how does NetBSD do this stuff? It has been a while since I've > looked. The idea behind the bus_dmamap stuff (I think) is that you can use it to obtain buffers for DMA that are properly positioned and/or aligned as required by a given architecture without each driver having to deal with such issues itself. It also deals with bounce buffering in those cases where it's needed. You use call an init routine of some sort and tell it what parent bus you're attached to, and it works out what limitations/requirements are involved. You also allocate special mapping structures. When you have data to DMA, you use bus_dmamap_load() to attach or copy the data to the bus mappings. The problem is that doing this with mbufs is cumbersome because you have may have an mbuf chain to deal with and you have to chase down all the mbufs in the chain and set them up correctly: bus_dmamap_load_mbuf() is supposed to handle most of the gruntwork for you. I don't claim to understand all of how it works, but I can't even begin to experiment with it unless a) everything is implemented and working properly and b) there's proper documentation (e.g. man pages). I think the best thing would be if somebody were to prepare a sample driver skeleton that actually makes proper use of all the new framework(s). -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 15:12:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00999 for freebsd-current-outgoing; Thu, 31 Dec 1998 15:12:00 -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 PAA00994 for ; Thu, 31 Dec 1998 15:11:58 -0800 (PST) (envelope-from dick@ns.tar.com) Received: (from dick@localhost) by ns.tar.com (8.9.1/8.9.1) id QAA03007; Thu, 31 Dec 1998 16:54:47 -0600 (CST) (envelope-from dick) Date: Thu, 31 Dec 1998 16:54:47 -0600 From: Richard Seaman To: "Kevin G. Eliuk" Cc: current@FreeBSD.ORG Subject: Re: Trouble with Staroffice5.0 Message-ID: <19981231165447.A2862@tar.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: ; from Kevin G. Eliuk on Thu, Dec 31, 1998 at 10:43:58AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 10:43:58AM -0800, Kevin G. Eliuk wrote: > ~Hi, > > I have been trying for the last week or so to install StarOffice5.0 as > described in the documentation , and have yet to be > successful. > > I get as far as: > > ... > $ cd /home/cagey/so50/office50_inst > $ export LD_LIBRARY_PATH=/tmp/sv001.tmp:$LD_LIBRARY_PATH > $ ./setup > > It gives the the message: > > ./setup: Window manager didn't set icon sizes - using default. > > After a lot of disk activity after which a full screen frame appears > with "Installation" in the title bar(no window just the frame). A > smaller window appears with "Star Office Setup" in the title bar, the > mouse cursor changes, and a 3D button labelled "Next". Well, you certainly got past all the problem areas I know about, if you get this far. > This is where the whole thing freezes. > > The only activity that I can make happen at that point is some disk > activity with moving the mouse. > > Later I thought I would try and see what kind of usage was going on by > hot keying to a different tty and running top. It appears that it does > take a lot of resources up to that point. And in this mode it completes > the process of creating the setup screen. When I hot key back to the > window session and use the mouse or keyboard it again freezes everything > up again. > > I toyed with lowering the depth to 8 bit which allows the filling in of > the "Installation" window, but it still locks up. > > I seen the post about the patch for the pthread code and will bring it > in on my next build. The linux threads "port" isn't necessary for emulation, and therefore not necessary for StarOffice. > One other note, I had to manually patch "/usr/src/lib/libc_r/Makefile" Hmm... I'll look at this. But, the patches that deal with libc_r don't relate to linux emulation, only to the linux threads "port", so again this isn't necessary for StarOffice. > Any ideas on where I can go from here. Only one. I should note that I'm not a StarOffice guru by any means. I've only tried it out as a test case of the linux threads emulation code. The idea is that StarOffice is a resource hog, and you don't have much RAM. I'm not smart enought to read the output you sent to find how much swap space you have. Is is possible you're just running out of resources? When I run soffice, just the initial program, without actually doing anything, shows 24MB of resident memory and 32MB of total vm memory under "top". And, this is with my vm stack patches applied. I'd guess the vm memory would jump another 10MB without them. You presumably have an X server running, plus whatever else, so is it possible you just need more RAM? I've only tried it on a machine with 256MB of RAM and 512MB of swap. :) -- Richard Seamman, Jr. email: dick@tar.com 5182 N. Maple Lane phone: 414-367-5450 Chenequa WI 53058 fax: 414-367-5852 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 15:40:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA02944 for freebsd-current-outgoing; Thu, 31 Dec 1998 15:40:37 -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 PAA02926 for ; Thu, 31 Dec 1998 15:40:32 -0800 (PST) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 2639 invoked by uid 100); 31 Dec 1998 23:50:17 -0000 Date: Thu, 31 Dec 1998 15:50:16 -0800 To: Thomas Dean Cc: scrappy@hub.org, mark@grondar.za, donegan@quick.net, dcs@newsguy.com, jmb@FreeBSD.ORG, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. Message-ID: <19981231155016.A2630@top.worldcontrol.com> References: <199812312228.OAA28553@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199812312228.OAA28553@ix.netcom.com>; from Thomas Dean on Thu, Dec 31, 1998 at 02:28:14PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 02:28:14PM -0800, Thomas Dean wrote: > KEEP SENDMAIL! > > If people want postfix, myspecialemail, etc., put them in ports. > > Sendmail is a MUST. Sendmail should be in the mainline of the source > tree. If you don't know why, I am sorry! I was thankful the day NO_SENDMAIL= true became an option in /etc/make.conf -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 15:42:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03251 for freebsd-current-outgoing; Thu, 31 Dec 1998 15:42:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy.vvm.com (proxy.vvm.com [204.71.94.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03245 for ; Thu, 31 Dec 1998 15:42:22 -0800 (PST) (envelope-from sbarron@vvm.com) Received: from ns.vvm.com (IDENT:root@ns.vvm.com [204.71.94.1]) by proxy.vvm.com (8.9.1/8.9.1) with ESMTP id RAA27803; Thu, 31 Dec 1998 17:43:35 -0600 Received: from avalon.abalonesoft.com (kain@206-97-175-236.vvm.com [206.97.175.236]) by ns.vvm.com (8.8.8/8.9.1) with ESMTP id RAA25759; Thu, 31 Dec 1998 17:41:57 -0600 Message-ID: X-Mailer: XFMail 1.3 [p0] on Linux X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19981231165447.A2862@tar.com> Date: Thu, 31 Dec 1998 17:44:03 -0600 (CST) From: Scott Barron To: Richard Seaman Subject: Re: Trouble with Staroffice5.0 Cc: current@FreeBSD.ORG, "Kevin G. Eliuk" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Dec-98 Richard Seaman wrote: > On Thu, Dec 31, 1998 at 10:43:58AM -0800, Kevin G. Eliuk wrote: > [SNIP] >> Any ideas on where I can go from here. > > Only one. I should note that I'm not a StarOffice guru by any means. > I've only tried it out as a test case of the linux threads emulation > code. > > The idea is that StarOffice is a resource hog, and you don't have much > RAM. I'm not smart enought to read the output you sent to find how > much swap space you have. Is is possible you're just running out of > resources? When I run soffice, just the initial program, without > actually doing anything, shows 24MB of resident memory and 32MB of > total vm memory under "top". And, this is with my vm stack patches > applied. I'd guess the vm memory would jump another 10MB without > them. > > You presumably have an X server running, plus whatever else, so is > it possible you just need more RAM? I've only tried it on a > machine with 256MB of RAM and 512MB of swap. :) > > -- I would like to add a note here. I had the same problem described while running Linux. My box has 96M RAM and about 130M of swap space. Star Office would freeze in about the same place, but I was not so lucky to have regained control of my keyboard and hence had to do a cold boot. After doing it twice I decided to heck with it and downloaded word perfect 8. I have not tried anything on FreeBSD yet. Has anyone attempted running WP8 on FreeBSD? It was a lot less resource hungry than SO4 on Linux. -Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 16:16:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07528 for freebsd-current-outgoing; Thu, 31 Dec 1998 16:16:19 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07523 for ; Thu, 31 Dec 1998 16:16:17 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA05263; Thu, 31 Dec 1998 19:15:37 -0500 (EST) Date: Thu, 31 Dec 1998 19:15:36 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Julian Elischer cc: Robert Nordier , Peter Wemm , current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Julian Elischer wrote: > as long as the old (2.0) Bootblocks can load a new a.out encoded boot > loader, We are ok, but if it can't then I guess I'll need to be spending > time to figure out why and fix it.. > > asking our clients to replace the bootblocks is not an option, but > supplying a 3rd stage loader called 'kernel' will work for us.. > It would REALLY be nice if FreeBSD would now with this change, do what > NetBSD did, and make the kernel name /FreeBSD rather than > 'kernel'. Why make such a facetious change? OpenBSD renamed the kernel to bsd, NetBSD to NetBSD, why make such a change ourselves? It's simply unnecessary. Kernel is self-explanatory. You suggesting BTX (of course, what we'd use for a 3rd stage loader) as /kernel is a hack anyway, /boot/loader isn't quite a kenrel. > > > On Thu, 31 Dec 1998, Robert Nordier wrote: > > > Peter Wemm wrote: > > > > > === INCOMPLETE DRAFT === > > > > > - The new bootblocks default to /boot/loader, but there are some problems > > > for some people still. This needs to be fixed, and either the new > > > bootblocks need fixing or the old bootblocks need a cutdown and > > > modified to fire up /boot/loader by default. > > > > Since early November (and up to and including an issue reported on > > -current yesterday), all apparent show-stopping problems with the > > new bootblocks have turned out to be due to configuration and/or > > pilot errors: where it has been possible to get further details. > > > > So if anyone still can't use the new bootblocks, there's almost > > certainly some simple and painless solution which doesn't require > > code fixes to sort out; and anyone who needs help is more than > > welcome to contact me. > > > > -- > > Robert Nordier > > > > 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 > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Thu Dec 31 16:17:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07794 for freebsd-current-outgoing; Thu, 31 Dec 1998 16:17:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07788; Thu, 31 Dec 1998 16:17:12 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA05307; Thu, 31 Dec 1998 19:16:34 -0500 (EST) Date: Thu, 31 Dec 1998 19:16:34 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Mark Murray cc: "Steven P. Donegan" , The Hermit Hacker , "Daniel C. Sobral" , "Jonathan M. Bresler" , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199812311622.SAA60127@greenpeace.grondar.za> 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, 31 Dec 1998, Mark Murray wrote: > "Steven P. Donegan" wrote: > > Not to flame at all - but what wonderful things does postfix bring that > > would induce anyone to move away from sendmail? Move from something that > > works in the millions of systems, is understood by vast numbers of sys > > admins, etc? If postfix can do something sendmail can't what is it? And > > an answer that it's easier to configure isn't really valid for us lifer > > sendmail folks :-) > > 1) Vastly easier to configure :-). (Very valid for newbies). > 2) A heck of a lot more efficient. Sendmail is designed to work; > this is designed to work _fast_. > 3) More secure. The author is security-paranoid. This is good. > 4) So far (apart from myself) I have seen no rumblings at all > about removing Sendmail. After seeing all these points, I'm yet to see why not to use exim instead. It's a wonderful MTA! > > 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 > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Thu Dec 31 16:23:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08113 for freebsd-current-outgoing; Thu, 31 Dec 1998 16:23:17 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from anthrax.speck (cx19313-a.nwptn1.va.home.com [24.2.49.151]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08108 for ; Thu, 31 Dec 1998 16:23:16 -0800 (PST) (envelope-from jedgar@speck.ml.org) Received: from localhost (jedgar@localhost) by anthrax.speck (8.9.1/8.9.1) with ESMTP id TAA01686; Thu, 31 Dec 1998 19:22:42 -0500 (EST) (envelope-from jedgar@speck.ml.org) X-Authentication-Warning: anthrax.speck: jedgar owned process doing -bs Date: Thu, 31 Dec 1998 19:22:41 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@anthrax.speck To: Scott Barron cc: current@FreeBSD.ORG Subject: Re: Trouble with Staroffice5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Scott Barron wrote: [SNIP] > it twice I decided to heck with it and downloaded word perfect 8. I have not > tried anything on FreeBSD yet. Has anyone attempted running WP8 on FreeBSD? > It was a lot less resource hungry than SO4 on Linux. > > -Scott Actually, WP8 is _very_ well-behaved. It installed quickly (it's in the ports now, too) with the basic Linux libs. -Chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 16:28:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08554 for freebsd-current-outgoing; Thu, 31 Dec 1998 16:28:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ix.netcom.com (sil-wa15-47.ix.netcom.com [207.93.148.47]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08549 for ; Thu, 31 Dec 1998 16:28:21 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: (from tomdean@localhost) by ix.netcom.com (8.9.1/8.8.8) id QAA28879; Thu, 31 Dec 1998 16:27:49 -0800 (PST) (envelope-from tomdean) Date: Thu, 31 Dec 1998 16:27:49 -0800 (PST) Message-Id: <199901010027.QAA28879@ix.netcom.com> From: Thomas Dean To: freebsd-current@FreeBSD.ORG Subject: aout-elf broke, won't be fixed, purchased red hat Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-current unsubscribe freebsd-smp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 16:34:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09121 for freebsd-current-outgoing; Thu, 31 Dec 1998 16:34:10 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA09113; Thu, 31 Dec 1998 16:34:05 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id TAA06009; Thu, 31 Dec 1998 19:33:48 -0500 (EST) Date: Thu, 31 Dec 1998 19:33:48 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: alexandr@mail.eecis.udel.edu cc: "Jonathan M. Bresler" , dcs@newsguy.com, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: RE: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199812311807.KAA27750@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998 alexandr@mail.eecis.udel.edu wrote: > In Reply to Your Message of Thu, 31 Dec 1998 06: 57:45 PST > Date: Thu, 31 Dec 1998 12:55:20 -0500 > From: Jerry Alexandratos > Message-ID: <199812311255.aa06349@mail.eecis.udel.edu> > > "Jonathan M. Bresler" says: > : > Date: Thu, 31 Dec 1998 23:40:24 +0900 > : > From: "Daniel C. Sobral" > : > > : > As horrible as sendmail is, I doubt we could remove it from the > : > source without a major riot. So, what it is GAINED by having Postfix > : > in the contrib instead of the ports? > : > : for many of our users sendmail.cf is a major hurdle. i know i have > : made money customizing sendmail.cf for people. postfix does the > : common sendmail.cf reconfiguration issues and does them in a way > : that people can roll their own and wont have to pay people like me. > : (hey....wait a minute....why am i doing this. ;) > : > : canonicalization, virtual hosts, spam control, etc. the .mc files > : go a long way to making this easier, but people still flounder. > > I'm not disagreeing with any of the "benefits" of postfix. However, > everything you just mentioned about postfix (sendmail drop-in > compatible, human-readable configuration files, scales well to large > installations, etc...) is being done and has been done by exim over the > past few years. Hey, except for the "sendmail drop-in" even qmail has > met all of the other qualifications. > > So why did we never think of putting these mailers in the tree? > > However, here's my real bone of contention. The FreeBSD project has > always been precise and deliberate with what is placed in the source > tree, with the emphasis being stability. Look, we're still using what > everyone and their grandmother calls "a way old compiler" (and yes, > we've almost always been a major version behind). It took forever to > get perl5 into the tree. We still haven't upgraded to the latest > version of CVS. Yada, yada, yada... > > And now... Now we want to put a *beta* mailer for which new security > holes and bugs are being found every day in the source tree instead of > the ports tree. > > I swear, it's almost like we've become victims of IBM's marketing > machine. > > Personally, I think we should focus our efforts on putting either gcc28 > or egcs in the tree. 8) You neglect to understand how "we" works. For certain things, implementing something as a team works: when you have a large project and a clear direction stated. Things will intercorrelate correctly. But on a small project, such as a port (or merge) usually is, a single person with many testers who bash on is best. Testing things is what takes many people, developing a finely-grained project is something for a single person. > > --Jerry > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Thu Dec 31 16:44:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA09739 for freebsd-current-outgoing; Thu, 31 Dec 1998 16:44:02 -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 QAA09724; Thu, 31 Dec 1998 16:43:58 -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 LAA15361; Fri, 1 Jan 1999 11:13:16 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA41684; Fri, 1 Jan 1999 11:13:19 +1030 (CST) Message-ID: <19990101111319.U39598@freebie.lemis.com> Date: Fri, 1 Jan 1999 11:13:19 +1030 From: Greg Lehey To: "Jonathan M. Bresler" , donegan@quick.net Cc: current@FreeBSD.ORG Subject: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199812311700.JAA20011@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199812311700.JAA20011@hub.freebsd.org>; from Jonathan M. Bresler on Thu, Dec 31, 1998 at 09:00:10AM -0800 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 On Thursday, 31 December 1998 at 9:00:10 -0800, Jonathan M. Bresler wrote: >> Date: Thu, 31 Dec 1998 08:41:33 -0800 (PST) >> From: "Steven P. Donegan" >> >> A possible plus for the (I think) minority where sendmail poses any >> performance issues - I found sendmail to be quite capable of a hundred >> thousand or so transactions per hour - for the few who need more - make >> it a port - not the default... > > rob kolstad found sendmail to be limited to 120k emails per hour > (eph?). its in a LISA paper he did recently. see www.usenix.org. Any suggestions about how to search for it? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 16:52:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10462 for freebsd-current-outgoing; Thu, 31 Dec 1998 16:52:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10457 for ; Thu, 31 Dec 1998 16:52:20 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA00619; Thu, 31 Dec 1998 16:49:11 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901010049.QAA00619@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Thomas T. Veldhouse" cc: "FreeBSD-Current" Subject: Re: ELF Kernel and /boot/loader In-reply-to: Your message of "Thu, 31 Dec 1998 11:05:43 CST." <000001be34df$ccff7e40$0264a8c0@rover.mn.mediaone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Dec 1998 16:49:11 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > How do I get my ELF kernel to boot. I was able to install it OK, and I > told it to load "/boot/loader" at the prompt, but the kernel loaded and then > went into a panic when it couldn't mount the root partition. Can anybody > send me some simple instructions on how to boot the ELF kernel? You need to supply (many) more details. It's likely that you're booting from an IDE or SCSI disk that's not the first disk in your system, but you will need to detail your exact previous boot process to determine this. -- \\ 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 31 16:56:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11044 for freebsd-current-outgoing; Thu, 31 Dec 1998 16:56:46 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11028; Thu, 31 Dec 1998 16:56:19 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 16:56:19 -0800 (PST) Message-Id: <199901010056.QAA11028@hub.freebsd.org> From: "Jonathan M. Bresler" To: green@unixhelp.org CC: mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG In-reply-to: (message from Brian Feldman on Thu, 31 Dec 1998 19:16:34 -0500 (EST)) Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 31 Dec 1998 19:16:34 -0500 (EST) > From: Brian Feldman > On Thu, 31 Dec 1998, Mark Murray wrote: > > > 1) Vastly easier to configure :-). (Very valid for newbies). > > 2) A heck of a lot more efficient. Sendmail is designed to work; > > this is designed to work _fast_. > > 3) More secure. The author is security-paranoid. This is good. > > 4) So far (apart from myself) I have seen no rumblings at all > > about removing Sendmail. > > After seeing all these points, I'm yet to see why not to use exim instead. It's > a wonderful MTA! exim is GPL. (stated explicitly at http://www.exim.org) if i remember correctly, whenever possible FreeBSD strives to use tools that are either under Berkeley copyright, or as close to Berkely copyright as possible. qmail has different license terms. (quoted from ftp://koobera.math.uic.edu/www/qmail/dist.html) If you want to distribute modified versions of qmail (including ports, no matter how minor the changes are) you'll have to get my approval. This does not mean approval of your distribution method, your intentions, your e-mail address, your haircut, or any other irrelevant information. It means a detailed review of the exact package that you want to distribute. an exception clause allows us to port qmail, if and only if, we port dot-forward-0.71.tar.gz, fastforward-0.51.tar.gz, and qmail-1.03.tar.gz. we must not break these out into separate parts. the FreeBSD post of qmail seems to be in violation of the above restriction. the port fetch qmail-1.03 only. i will notify the maintainer. perhaps this restrictin was added after the port was created. Postfix license requires that IF you provide "any feedback, including materials, error corrections, Software Derivatives, enhancements, suggestions and the like" to IBM then "You grant IBM a world-wide, royalty-free right to use, copy, distribute, sublicense and prepare derivative works". IF you dont provide it to IBM, they have no claim to your work. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 17:06:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11722 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:06:34 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA11716; Thu, 31 Dec 1998 17:06:30 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 17:06:30 -0800 (PST) Message-Id: <199901010106.RAA11716@hub.freebsd.org> From: "Jonathan M. Bresler" To: grog@lemis.com CC: donegan@quick.net, current@FreeBSD.ORG In-reply-to: <19990101111319.U39598@freebie.lemis.com> (message from Greg Lehey on Fri, 1 Jan 1999 11:13:19 +1030) Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199812311700.JAA20011@hub.freebsd.org> <19990101111319.U39598@freebie.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Fri, 1 Jan 1999 11:13:19 +1030 > From: Greg Lehey > Cc: current@FreeBSD.ORG > Content-Type: text/plain; charset=us-ascii > 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 > > On Thursday, 31 December 1998 at 9:00:10 -0800, Jonathan M. Bresler wrote: > >> Date: Thu, 31 Dec 1998 08:41:33 -0800 (PST) > >> From: "Steven P. Donegan" > >> > >> A possible plus for the (I think) minority where sendmail poses any > >> performance issues - I found sendmail to be quite capable of a hundred > >> thousand or so transactions per hour - for the few who need more - make > >> it a port - not the default... > > > > rob kolstad found sendmail to be limited to 120k emails per hour > > (eph?). its in a LISA paper he did recently. see www.usenix.org. > > Any suggestions about how to search for it? http://www.usenix.org/publications/library/search.html keywords: lisa kolstad sendmail Author: Rob Kolstad Title: Tuning Sendmail for Large Mailing Lists Pages: 195 Publisher: USENIX Proceedings: Eleventh Systems Administration Conference (LISA '97) Date: October 26-31, 1997 Location: San Diego, California Institution: Berkeley Software Design, Inc. ;) jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 17:09:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12929 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:09:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.eecis.udel.edu (louie.udel.edu [128.175.2.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA12860; Thu, 31 Dec 1998 17:09:13 -0800 (PST) (envelope-from alexandr@mail.eecis.udel.edu) Date: Thu, 31 Dec 1998 17:09:13 -0800 (PST) From: alexandr@mail.eecis.udel.edu Message-Id: <199901010109.RAA12860@hub.freebsd.org> Received: from ren.eecis.udel.edu by mail.eecis.udel.edu id aa00435; 31 Dec 1998 19:50 EST To: Brian Feldman Cc: alexandr@mail.eecis.udel.edu, "Jonathan M. Bresler" , dcs@newsguy.com, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: RE: HEADS UP: Postfix is coming. new uid, gid required. Organization: Mos Eisley Candy Store Reply-To: alexandr@mail.eecis.udel.edu Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Reply to Your Message of Thu, 31 Dec 1998 19: 33:48 EST Date: Thu, 31 Dec 1998 19:50:08 -0500 From: Jerry Alexandratos Message-ID: <199812311950.aa00435@mail.eecis.udel.edu> Brian Feldman says: : On Thu, 31 Dec 1998 alexandr@mail.eecis.udel.edu wrote: : > : > Personally, I think we should focus our efforts on putting either gcc28 : > or egcs in the tree. 8) : : You neglect to understand how "we" works. For certain things, implementing : something as a team works: when you have a large project and a clear : direction stated. Things will intercorrelate correctly. But on a small projec t, : such as a port (or merge) usually is, a single person with many testers who : bash on is best. Testing things is what takes many : people, developing a finely-grained project is something for a single person. Actually, please notice the smiley. I was trying (miserably) to make a funny about in reference to the slw of e-mails that flew around for what to do about a toolchain and compiler (specifically in reference to the sparc64-elf port). As Dennis Miller once said, "stop me before I sub-reference again." However, that discussion brought out lots of good points. Things like not using egcs because it's still relatively beta software and a "moving target." So once again, I ask my original question (which hasn't been answered yet), why not make postfix a port? All of the benefits that it provides vs sendmail have been done previously in other mailers and those mailers are in the ports tree. Likewise, postfix falls under every reason (from a development/code stage POV) that I can recall over the past 4 years for not putting something into the main source tree but rather making it a port. Anyway, like anything and everything else, this is not worth taking personally and getting into a tizzy. I never meant to start a "features war" and apologize since this is what my question turned into. Everyone, have a Happy New Year and I'll see you all in 1999! --Jerry 8) Jerry Alexandratos % - % "Nothing inhabits my (8 8) alexandr@louie.udel.edu % - % thoughts, and oblivion (8 8) darkstar@strauss.udel.edu % - % drives my desires." (8 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 17:09:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13079 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:09:43 -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 RAA13044; Thu, 31 Dec 1998 17:09:37 -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 LAA15476; Fri, 1 Jan 1999 11:38:50 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA41798; Fri, 1 Jan 1999 11:38:53 +1030 (CST) Message-ID: <19990101113853.A39598@freebie.lemis.com> Date: Fri, 1 Jan 1999 11:38:53 +1030 From: Greg Lehey To: "Jonathan M. Bresler" Cc: donegan@quick.net, current@FreeBSD.ORG Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199812311700.JAA20011@hub.freebsd.org> <19990101111319.U39598@freebie.lemis.com> <199901010106.RAA11716@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199901010106.RAA11716@hub.freebsd.org>; from Jonathan M. Bresler on Thu, Dec 31, 1998 at 05:06:30PM -0800 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 On Thursday, 31 December 1998 at 17:06:30 -0800, Jonathan M. Bresler wrote: >> Date: Fri, 1 Jan 1999 11:13:19 +1030 >> From: Greg Lehey >> Cc: current@FreeBSD.ORG >> Content-Type: text/plain; charset=us-ascii >> 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 >> >> On Thursday, 31 December 1998 at 9:00:10 -0800, Jonathan M. Bresler wrote: >>>> Date: Thu, 31 Dec 1998 08:41:33 -0800 (PST) >>>> From: "Steven P. Donegan" >>>> >>>> A possible plus for the (I think) minority where sendmail poses any >>>> performance issues - I found sendmail to be quite capable of a hundred >>>> thousand or so transactions per hour - for the few who need more - make >>>> it a port - not the default... >>> >>> rob kolstad found sendmail to be limited to 120k emails per hour >>> (eph?). its in a LISA paper he did recently. see www.usenix.org. >> >> Any suggestions about how to search for it? > > > http://www.usenix.org/publications/library/search.html > > keywords: lisa kolstad sendmail > > Author: Rob Kolstad > Title: Tuning Sendmail for Large Mailing Lists > Pages: 195 > Publisher: USENIX > Proceedings: Eleventh Systems Administration Conference (LISA '97) > Date: October 26-31, 1997 > Location: San Diego, California > Institution: Berkeley Software Design, Inc. Oh. I was expecting an online document. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 17:13:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA14359 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:13:21 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA14327 for ; Thu, 31 Dec 1998 17:13:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA00815; Thu, 31 Dec 1998 17:09:06 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901010109.RAA00815@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Brian Behlendorf cc: "Jordan K. Hubbard" , FreeBSD current users Subject: Re: How do I build an a.out kld? In-reply-to: Your message of "Tue, 29 Dec 1998 14:10:05 PST." <4.1.19981229140706.048df410@hyperreal.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 31 Dec 1998 17:09:06 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >/boot/boot.conf is supposed to contain any boot commands you'd like to > >have run (boot.conf is actually a bad name, now that I think about it, > >since it implies configuration variables rather than actions - boot.rc > >would have been better, oh well!). > > So would a blank file tell it to boot the default immediately, or should I > put "boot /kernel" in there? It's not that I really NEED those 8 seconds, > it just seems like it'd be cleaner to boot directly. If you want to shorten the delay, you can set $autoboot_delay lower; 10 seconds is just a conservative default, eg: set autoboot_delay=3 will bring it down to 3 seconds. -- \\ 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 31 17:18:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15930 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:18:01 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA15913; Thu, 31 Dec 1998 17:17:57 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 17:17:57 -0800 (PST) Message-Id: <199901010117.RAA15913@hub.freebsd.org> From: "Jonathan M. Bresler" To: grog@lemis.com CC: donegan@quick.net, current@FreeBSD.ORG In-reply-to: <19990101113853.A39598@freebie.lemis.com> (message from Greg Lehey on Fri, 1 Jan 1999 11:38:53 +1030) Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199812311700.JAA20011@hub.freebsd.org> <19990101111319.U39598@freebie.lemis.com> <199901010106.RAA11716@hub.freebsd.org> <19990101113853.A39598@freebie.lemis.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG it is online in the library http://www.usenix.org/publications/library/proceedings/lisa97/full_papers/21.kolstad/21.pdf jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 17:21:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16203 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:21:22 -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 RAA16193; Thu, 31 Dec 1998 17:21:17 -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 LAA15546; Fri, 1 Jan 1999 11:50:29 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA41858; Fri, 1 Jan 1999 11:50:32 +1030 (CST) Message-ID: <19990101115032.A41841@freebie.lemis.com> Date: Fri, 1 Jan 1999 11:50:32 +1030 From: Greg Lehey To: "Jonathan M. Bresler" Cc: donegan@quick.net, current@FreeBSD.ORG Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199812311700.JAA20011@hub.freebsd.org> <19990101111319.U39598@freebie.lemis.com> <199901010106.RAA11716@hub.freebsd.org> <19990101113853.A39598@freebie.lemis.com> <199901010117.RAA15913@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199901010117.RAA15913@hub.freebsd.org>; from Jonathan M. Bresler on Thu, Dec 31, 1998 at 05:17:57PM -0800 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 On Thursday, 31 December 1998 at 17:17:57 -0800, Jonathan M. Bresler wrote: > > it is online in the library > > http://www.usenix.org/publications/library/proceedings/lisa97/full_papers/21.kolstad/21.pdf Thanks. I'm not a USENIX member, and it's not that big a deal. Besides, I didn't realize what an enormous document it is. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 17:23:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16299 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:23:00 -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 RAA16291; Thu, 31 Dec 1998 17:22:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id RAA05674; Thu, 31 Dec 1998 17:22:22 -0800 (PST) (envelope-from dillon) Date: Thu, 31 Dec 1998 17:22:22 -0800 (PST) From: Matthew Dillon Message-Id: <199901010122.RAA05674@apollo.backplane.com> To: Greg Lehey Cc: "Jonathan M. Bresler" , donegan@quick.net, current@FreeBSD.ORG Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :>> A possible plus for the (I think) minority where sendmail poses any :>> performance issues - I found sendmail to be quite capable of a hundred :>> thousand or so transactions per hour - for the few who need more - make :>> it a port - not the default... :> :> rob kolstad found sendmail to be limited to 120k emails per hour :> (eph?). its in a LISA paper he did recently. see www.usenix.org. : :Any suggestions about how to search for it? : :Greg This is not a good argument for replacing sendmail, considering the fact that 100,000 messages an hour is sufficient to handle the needs of a userbase of 100,000 users or more. BEST has two incoming mail servers, running sendmail, to support it's 30,000+ users and the mail rate is only 150 messages a minute (per server) at peak. BEST's outgoing mailing lists machine is our busiest mail box. The outgoing mail rate, doing the mailing lists for all best users (a few thousand mailing lists) is, at peak, around 1000 messages a minute at peak (around 60,000 an hour). Sendmail is not the lightest weight program in the world, but it is the most mature and it is relatively easy to configure it to resist all sorts of potential blowups, attacks, or whatnot. I think it's a bad idea to replace it in the base distribution and an even worse idea to put both sendmail and something else in the base distribution. This new mail program thingy should be a port. I would like to point out that there is nothing wrong with ports... hell, even 'less' is a port! -Matt :-- :See complete headers for address, home page and phone numbers :finger grog@lemis.com for PGP public key : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-current" in the body of the message : 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 31 17:37:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA17351 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:37:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from xwin.nmhtech.com (xwin.nmhtech.com [208.138.46.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17345 for ; Thu, 31 Dec 1998 17:37:21 -0800 (PST) (envelope-from nicole@xwin.nmhtech.com) Received: by xwin.nmhtech.com (Postfix, from userid 1001) id 20F782EE1A; Thu, 31 Dec 1998 17:36:59 -0800 (PST) Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 In-Reply-To: Date: Thu, 31 Dec 1998 17:36:59 -0800 (PST) From: Nicole Harrington To: Randy Bush Subject: RE: dummy's guide to flag day, please? Cc: freebsd-current@FreeBSD.ORG Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA17346 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 31-Dec-98 Randy Bush wisely wrote: > let's make it simple for us dummies. > > i am an a.outer who updates from current every few weeks. i usually > backup > update > make buildworld > go single user > make installworld > mergemaster -cv <--- > make a new kernel > install kernel > reboot > > let's hypothesize that on the 10th or so the messages have died down and i > decide to give the wonderful new elf world a try. what are the steps (after > backing up something awful:-)? > > i know, for example, there will be hidden gotchas in the ldconfig stuff in > rc.conf.local. so please don't be too glib. > > thanks > > randy > Maybe I'm missing something but what does "mergemaster -cv" Mean/stand for? Thanks Nicole nicole@webweaver.net - http://www.webweaver.net/ webmistress@dangermouse.org - http://www.dangermouse.org/ ------------------------------------------------- -- Powered by Coka Cola and FreeBSD -- - Stong enough for a man - But made for a Woman -- -- Microsoft: What bug would you like today? -- - I'm not ADD - I'm just MultiThreaded -- --------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 17:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18099 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:52:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from localhost.nowhere (ppp18324.on.bellglobal.com [206.172.130.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18092; Thu, 31 Dec 1998 17:52:06 -0800 (PST) (envelope-from vanderh@ecf.toronto.edu) Received: (from tim@localhost) by localhost.nowhere (8.9.1/8.9.1) id UAA08099; Thu, 31 Dec 1998 20:51:53 -0500 (EST) (envelope-from tim) Message-ID: <19981231205153.A6127@mad> Date: Thu, 31 Dec 1998 20:51:53 +875500 From: Tim Vanderhoek To: "Jonathan M. Bresler" , green@unixhelp.org Cc: mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199901010056.QAA11028@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199901010056.QAA11028@hub.freebsd.org>; from Jonathan M. Bresler on Thu, Dec 31, 1998 at 04:56:19PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 04:56:19PM -0800, Jonathan M. Bresler wrote: > > the FreeBSD post of qmail seems to be in violation of the above > restriction. the port fetch qmail-1.03 only. i will notify the > maintainer. perhaps this restrictin was added after the port was > created. The FreeBSD port of qmail is not in violation of the above restriction. I contacted Bernstein before committing the port. He offered some suggestions, I made some changes, and it was committed. -- This .sig is not innovative, witty, or profund. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 17:54:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18532 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:54:50 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18527 for ; Thu, 31 Dec 1998 17:54:49 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (3525 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Thu, 31 Dec 1998 17:54:28 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Thu, 31 Dec 1998 17:54:28 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Nicole Harrington Cc: freebsd-current@FreeBSD.ORG Subject: RE: dummy's guide to flag day, please? References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Maybe I'm missing something but what does "mergemaster -cv" Mean/stand for? MERGEMASTER(8) FreeBSD System Manager's Manual MERGEMASTER(8) NAME mergemaster - Merge configuration files, et al during an upgrade SYNOPSIS mergemaster [-scrvah] [-t /path/to/temp/root] [-d] [-u N] [-w N] DESCRIPTION mergemaster is a Bourne shell script which is designed to aid you in up- dating the various configuration and other files associated with FreeBSD. It is HIGHLY recommended that you back up your /etc directory before be- ginning this process. The script uses /usr/src/etc/Makefile to build a temporary root environ- ment from / down, populating that environment with the various files. It then compares each file in that environment to its installed counterpart. When the script finds a change in the new file, or there is no installed version of the new file it gives you four options to deal with it. You can install the new file as is, delete the new file, merge the old and new files (as appropriate) using sdiff(1) or leave the file in the tempo- rary root environment to merge by hand later. By default it creates the temporary root in /var/tmp/temproot and com- pares the cvs(1) version $Id strings for files that have them, deleting the temporary file if the strings match. If there is no $Id string, or if the strings are different it compares the files themselves. You can also specify that the script ignore the $Id strings and compare every file. mergemaster checks your umask and issues a warning for anything other than 022. While it is not mandatory to grant world permissions for most configuration files, you may run into problems without them. If you choose a umask other than 022 and run into trouble later this could be the cause. /etc/master.passwd is treated as a special case. If you choose to install this file or a merged version of it the file permis- sions are always 600 (rw-------) for security reasons. The script uses the owner and group id's that the files are created with by /usr/src/etc/Makefile, and file permissions as specified by the umask. Unified diffs are used by default to display any differences unless you choose context diffs. The options are as follows: -s Perform a strict comparison, diff'ing every pair of files. -c Use context diffs instead of unified diffs. -r Re-run mergemaster on a previously cleaned directory, skip- ping the creation of the temporary root environment. This op- tion is compatible with all other options. -v Be more verbose about the process. You should probably use this option the first time you run mergemaster. -a Run automatically. This option will leave all the files that differ from the installed versions in the temporary directory to be dealt with by hand. If the temproot directory exists, ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 17:55:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18623 for freebsd-current-outgoing; Thu, 31 Dec 1998 17:55:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18618 for ; Thu, 31 Dec 1998 17:55:18 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id UAA09351; Thu, 31 Dec 1998 20:54:48 -0500 (EST) Date: Thu, 31 Dec 1998 20:54:48 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: Scott Barron cc: Richard Seaman , current@FreeBSD.ORG, "Kevin G. Eliuk" Subject: Re: Trouble with Staroffice5.0 In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Scott Barron wrote: > > On 31-Dec-98 Richard Seaman wrote: > > On Thu, Dec 31, 1998 at 10:43:58AM -0800, Kevin G. Eliuk wrote: > > > > [SNIP] > > >> Any ideas on where I can go from here. > > > > Only one. I should note that I'm not a StarOffice guru by any means. > > I've only tried it out as a test case of the linux threads emulation > > code. > > > > The idea is that StarOffice is a resource hog, and you don't have much > > RAM. I'm not smart enought to read the output you sent to find how > > much swap space you have. Is is possible you're just running out of > > resources? When I run soffice, just the initial program, without > > actually doing anything, shows 24MB of resident memory and 32MB of > > total vm memory under "top". And, this is with my vm stack patches > > applied. I'd guess the vm memory would jump another 10MB without > > them. > > > > You presumably have an X server running, plus whatever else, so is > > it possible you just need more RAM? I've only tried it on a > > machine with 256MB of RAM and 512MB of swap. :) > > > > -- > > I would like to add a note here. I had the same problem described > while running Linux. My box has 96M RAM and about 130M of swap space. Star > Office would freeze in about the same place, but I was not so lucky to have > regained control of my keyboard and hence had to do a cold boot. After doing > it twice I decided to heck with it and downloaded word perfect 8. I have not > tried anything on FreeBSD yet. Has anyone attempted running WP8 on FreeBSD? > It was a lot less resource hungry than SO4 on Linux. The Beta of WP8 ran fine, although I tended to just plain not like the word processor at all. > > -Scott > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Thu Dec 31 18:01:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18923 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:01:58 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18917; Thu, 31 Dec 1998 18:01:46 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA09684; Thu, 31 Dec 1998 21:01:32 -0500 (EST) Date: Thu, 31 Dec 1998 21:01:32 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Jonathan M. Bresler" cc: mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199901010056.QAA11028@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Jonathan M. Bresler wrote: > > Date: Thu, 31 Dec 1998 19:16:34 -0500 (EST) > > From: Brian Feldman > > On Thu, 31 Dec 1998, Mark Murray wrote: > > > > > 1) Vastly easier to configure :-). (Very valid for newbies). > > > 2) A heck of a lot more efficient. Sendmail is designed to work; > > > this is designed to work _fast_. > > > 3) More secure. The author is security-paranoid. This is good. > > > 4) So far (apart from myself) I have seen no rumblings at all > > > about removing Sendmail. > > > > After seeing all these points, I'm yet to see why not to use exim instead. It's > > a wonderful MTA! > > exim is GPL. (stated explicitly at http://www.exim.org) > > if i remember correctly, whenever possible FreeBSD strives to use > tools that are either under Berkeley copyright, or as close to > Berkely copyright as possible. The GPL works fine with FreeBSD, we have a src/gnu, if you don't remember. The only major caveats with GPL are (as I see it) that: 1. We don't want GPL stuff in the kernel, hence the EXTREMELY few GPL drivers. (the GPL'd math emulator, and one other...) 2. GPL does not necessarily mean good. Not all the standard GNU utilities are good, nor even as good as the BSD predecessors. The GPL does not prevent us from including exim because: 1. We keep the source open, and changes public. 2. We don't change the license (we can't), so we don't violate the GPL. If you can find any fault in including exim, state it. > > qmail has different license terms. > (quoted from ftp://koobera.math.uic.edu/www/qmail/dist.html) > > If you want to distribute modified versions of qmail > (including ports, no matter how minor the changes are) you'll > have to get my approval. This does not mean approval of your > distribution method, your intentions, your e-mail address, > your haircut, or any other irrelevant information. It means a > detailed review of the exact package that you want to > distribute. > > an exception clause allows us to port qmail, if and only if, we > port dot-forward-0.71.tar.gz, fastforward-0.51.tar.gz, and > qmail-1.03.tar.gz. we must not break these out into separate parts. > > the FreeBSD post of qmail seems to be in violation of the above > restriction. the port fetch qmail-1.03 only. i will notify the > maintainer. perhaps this restrictin was added after the port was > created. > > Postfix license requires that IF you provide "any feedback, > including materials, error corrections, Software Derivatives, > enhancements, suggestions and the like" to IBM then "You grant IBM a > world-wide, royalty-free right to use, copy, distribute, sublicense > and prepare derivative works". > > IF you dont provide it to IBM, they have no claim to your work. > > jmb > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Thu Dec 31 18:06:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19351 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:06:09 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19303; Thu, 31 Dec 1998 18:05:56 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 18:05:56 -0800 (PST) Message-Id: <199901010205.SAA19303@hub.freebsd.org> From: "Jonathan M. Bresler" To: dillon@apollo.backplane.com CC: grog@lemis.com, donegan@quick.net, current@FreeBSD.ORG In-reply-to: <199901010122.RAA05674@apollo.backplane.com> (message from Matthew Dillon on Thu, 31 Dec 1998 17:22:22 -0800 (PST)) Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199901010122.RAA05674@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 31 Dec 1998 17:22:22 -0800 (PST) > From: Matthew Dillon > > This is not a good argument for replacing sendmail, considering the fact > that 100,000 messages an hour is sufficient to handle the needs of a > userbase of 100,000 users or more. 1 message per user per hour. please read the paper. rob kolstad wrote it after contending with mail lists that we taking hours to deliver a single message to all the subscribers. FreeBSD mail list subscribers seem to want instantaneous delivery...sometimes 30 minutes is just too long for some poeple ;) postfix delivers the mail to more people faster. thats what they awnt. that make me happy ;) and the queue directories are smaller (without loading up the queues on the mail-relays...thats just shifting the problem elsewhere and hiding it so i cant tell if there is a big backlog or not.) with postfix hte need for the mail-relays has decreased dramtically. > BEST has two incoming mail servers, running sendmail, to support it's > 30,000+ users and the mail rate is only 150 messages a minute (per server) > at peak. > > BEST's outgoing mailing lists machine is our busiest mail box. The > outgoing mail rate, doing the mailing lists for all best users (a few > thousand mailing lists) is, at peak, around 1000 messages a minute at > peak (around 60,000 an hour). current has 1411 subscribers. each wonts to get the message first! if we do 100 messages a day that's only 141,100 messages, nothing....but to deliver them all in 3 minutes boosts the effective rate to 2.8 million message per hour. i am not saying that postfix is delivering that rate. the closer the better. hub is currently delivering ~100k messages per hour (400 - 430 in 15 seconds reporting periods) for the last 75 seconds. then it drops to nearly nothing. that message has made it out. i would have preferred to do it in 15 seconds. that was just one message jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 18:08:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19750 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:08:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19722; Thu, 31 Dec 1998 18:07:45 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 18:07:45 -0800 (PST) Message-Id: <199901010207.SAA19722@hub.freebsd.org> From: "Jonathan M. Bresler" To: vanderh@ecf.utoronto.ca CC: green@unixhelp.org, mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG In-reply-to: <19981231205153.A6127@mad> (message from Tim Vanderhoek on Thu, 31 Dec 1998 20:51:53 +875500) Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199901010056.QAA11028@hub.freebsd.org> <19981231205153.A6127@mad> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 31 Dec 1998 20:51:53 +875500 > From: Tim Vanderhoek > > The FreeBSD port of qmail is not in violation of the above > restriction. I contacted Bernstein before committing the port. He > offered some suggestions, I made some changes, and it was committed. ahhh...i was not aware of that. mea cupla. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 18:12:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19956 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:12:56 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cantor.boolean.net (cantor.boolean.net [209.133.111.73]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19950; Thu, 31 Dec 1998 18:12:55 -0800 (PST) (envelope-from Kurt@OpenLDAP.Org) Received: from gypsy (localhost [127.0.0.1]) by cantor.boolean.net (8.9.1/8.9.1) with SMTP id CAA10938; Fri, 1 Jan 1999 02:14:43 GMT (envelope-from Kurt@OpenLDAP.Org) Message-Id: <3.0.5.32.19981231181341.0098e880@localhost> X-Sender: guru@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 31 Dec 1998 18:13:41 -0800 To: "Jonathan M. Bresler" From: "Kurt D. Zeilenga" Subject: postfix's copyright (Re: HEADS UP: Postfix is coming. new uid, gid required.) Cc: green@unixhelp.org, mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG In-Reply-To: <199901010056.QAA11028@hub.freebsd.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:56 PM 12/31/98 -0800, Jonathan M. Bresler wrote: > exim is GPL. (stated explicitly at http://www.exim.org) > qmail has different license terms. > Postfix license requires that IF you provide "any feedback, > including materials, error corrections, Software Derivatives, > enhancements, suggestions and the like" to IBM then "You grant IBM a > world-wide, royalty-free right to use, copy, distribute, sublicense > and prepare derivative works". > > IF you dont provide it to IBM, they have no claim to your work. But what are the claims of the authors and their employers! I just downloaded the 19981222 snapshot and I cannot find a single copyright notice. As such, I don't know what restrictions, if any, there might be under copyright of any of the authors or their employers. Yes, there is a license file... but nothing binding me to it (no contract or copyright notice). It also appears that non-IBM identies may have rights to this software to which IBM is cannot grant rights for. Note: true software licenses are bound by contract, most so called 'public licenses' (GPL, MozillaPL, NPL, OpenLDAP PL) are NOT 'licenses' but restrictions held under copyright law. (note, I'm not a lawyer, but I have a fair amount of experience with legalese). I only point this out because without a copyright notice, this license in meaningless. For items to be OpenLDAP contributed software we require the copyright holder to place appropriate copyright notices within the package and to clear state what rights are held by their employers. Without such a notice, one must assume that "All Rights Reserved." I strong recommend that you have the author of postfix, at a minimum, create a COPYRIGHT file at the top level of distribution clarifying the use and redistribution restrictions. As currently packaged, the postfix is not freely redistributable. I strongly recommend that someone close to the postfix project point out these issues. (You are welcomed to forward this message to INDIVIDUALS responsible for the development of postfix). I still think postfix should be a port... at least until it's out of BETA. I do not think it wise to import somthing which has not been widely tested (FreeBSD.org use isn't wide enough testing). Making it a port will allow others to test it. If it does prove to be suitable as a replacement (and/or suitable to coexist), great! Kurt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 18:17:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20275 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:17:55 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20264; Thu, 31 Dec 1998 18:17:33 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 18:17:33 -0800 (PST) Message-Id: <199901010217.SAA20264@hub.freebsd.org> From: "Jonathan M. Bresler" To: green@unixhelp.org CC: mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG In-reply-to: (message from Brian Feldman on Thu, 31 Dec 1998 21:01:32 -0500 (EST)) Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Date: Thu, 31 Dec 1998 21:01:32 -0500 (EST) > From: Brian Feldman > > The GPL works fine with FreeBSD, we have a src/gnu, if you don't remember. The > only major caveats with GPL are (as I see it) that: > 1. We don't want GPL stuff in the kernel, hence the EXTREMELY few > GPL drivers. (the GPL'd math emulator, and one other...) > 2. GPL does not necessarily mean good. Not all the standard GNU > utilities are good, nor even as good as the BSD predecessors. > The GPL does not prevent us from including exim because: > 1. We keep the source open, and changes public. > 2. We don't change the license (we can't), so we don't violate the GPL. > > If you can find any fault in including exim, state it. can a company take FreeBSD, including exim, make modifications and sell the result. several companies to this. the gnat box, nokia, whistle and others. if they can, i have misunderstood, that would be my fault. jmb ps. my lst message to current was delivered in 30 seconds 600 and 624 messages in the two 15 second intervals. thats 144k and 150k messages per hour. for those that are counting. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 18:23:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20704 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:23:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA20698; Thu, 31 Dec 1998 18:23:52 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id WAA17495; Thu, 31 Dec 1998 22:23:05 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 31 Dec 1998 22:23:04 -0400 (AST) From: The Hermit Hacker To: brian@worldcontrol.com cc: Thomas Dean , mark@grondar.za, donegan@quick.net, dcs@newsguy.com, jmb@FreeBSD.ORG, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <19981231155016.A2630@top.worldcontrol.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998 brian@worldcontrol.com wrote: > On Thu, Dec 31, 1998 at 02:28:14PM -0800, Thomas Dean wrote: > > KEEP SENDMAIL! > > > > If people want postfix, myspecialemail, etc., put them in ports. > > > > Sendmail is a MUST. Sendmail should be in the mainline of the source > > tree. If you don't know why, I am sorry! > > I was thankful the day > > NO_SENDMAIL= true > > became an option in /etc/make.conf then make neither standard and both ports...I personally feel the opposite, and rue the day that sendmail is removed... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 31 18:24:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20972 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:24:15 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20693; Thu, 31 Dec 1998 18:23:45 -0800 (PST) (envelope-from jmb) Date: Thu, 31 Dec 1998 18:23:45 -0800 (PST) Message-Id: <199901010223.SAA20693@hub.freebsd.org> From: "Jonathan M. Bresler" To: Kurt@OpenLDAP.Org CC: green@unixhelp.org, mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG In-reply-to: <3.0.5.32.19981231181341.0098e880@localhost> (Kurt@OpenLDAP.Org) Subject: Re: postfix's copyright (Re: HEADS UP: Postfix is coming. new uid, gid required.) References: <3.0.5.32.19981231181341.0098e880@localhost> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG you know copyright better than i. i will send your comments on to wietse vemena. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 18:24:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA20996 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:24:26 -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 SAA20968; Thu, 31 Dec 1998 18:24:12 -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 MAA15726; Fri, 1 Jan 1999 12:52:16 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA41961; Fri, 1 Jan 1999 12:51:56 +1030 (CST) Message-ID: <19990101125155.B41841@freebie.lemis.com> Date: Fri, 1 Jan 1999 12:51:55 +1030 From: Greg Lehey To: Tim Vanderhoek , "Jonathan M. Bresler" , green@unixhelp.org Cc: mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <199901010056.QAA11028@hub.freebsd.org> <19981231205153.A6127@mad> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981231205153.A6127@mad>; from Tim Vanderhoek on Tue, Dec 29, 1998 at 04:51:53AM +2355 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 On Tuesday, 29 December 1998 at 4:51:53 +2355, Tim Vanderhoek wrote: Date: Thu, 31 Dec 1998 20:51:53 +875500 This is the second message today I got with a completely crazy time zone offset (which put you back two days in my inbox listing). Does anybody have any idea why? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 18:26:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21165 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:26:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.cybcon.com (mail.cybcon.com [205.147.64.46]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21160 for ; Thu, 31 Dec 1998 18:26:14 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: from cybcon.com (wwoods@cybcon.com [205.147.64.49]) by mail.cybcon.com (8.9.0/8.9.0) with ESMTP id SAA15890 for ; Thu, 31 Dec 1998 18:25:52 -0800 (PST) Date: Thu, 31 Dec 1998 18:25:46 -0800 (PST) From: Bill Woods To: current@FreeBSD.ORG Subject: make world dies....whats up??? 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 am, from a clean install of 2.2.6 trying to do a make world to go to 3.0-current. I just cvsupped the latest source a few mins ago and on a make world I get... ---------------------------- c -O -pipe -I/usr/local/src/usr.bin/make -I/usr/obj/aout/usr/local/src/tmp/usr/include -c /usr/local/src/usr.bin/make/lst.lib/lstLast.c cc -O -pipe -I/usr/local/src/usr.bin/make -I/usr/obj/aout/usr/local/src/tmp/usr/include -c /usr/local/src/usr.bin/make/lst.lib/lstMember.c cc -O -pipe -I/usr/local/src/usr.bin/make -I/usr/obj/aout/usr/local/src/tmp/usr/include -c /usr/local/src/usr.bin/make/lst.lib/lstNext.c cc -O -pipe -I/usr/local/src/usr.bin/make -I/usr/obj/aout/usr/local/src/tmp/usr/include -c /usr/local/src/usr.bin/make/lst.lib/lstOpen.c cc -O -pipe -I/usr/local/src/usr.bin/make -I/usr/obj/aout/usr/local/src/tmp/usr/include -c /usr/local/src/usr.bin/make/lst.lib/lstRemove.c cc -O -pipe -I/usr/local/src/usr.bin/make -I/usr/obj/aout/usr/local/src/tmp/usr/include -c /usr/local/src/usr.bin/make/lst.lib/lstReplace.c cc -O -pipe -I/usr/local/src/usr.bin/make -I/usr/obj/aout/usr/local/src/tmp/usr/include -c /usr/local/src/usr.bin/make/lst.lib/lstSucc.c cc -O -pipe -I/usr/local/src/usr.bin/make -I/usr/obj/aout/usr/local/src/tmp/usr/include -static -o make arch.o buf.o compat.o cond.o dir.o for.o hash.o job.o main.o make.o parse.o str.o suff.o targ.o var.o util.o lstAppend.o lstAtEnd.o lstAtFront.o lstClose.o lstConcat.o lstDatum.o lstDeQueue.o lstDestroy.o lstDupl.o lstEnQueue.o lstFind.o lstFindFrom.o lstFirst.o lstForEach.o lstForEachFrom.o lstInit.o lstInsert.o lstIsAtEnd.o lstIsEmpty.o lstLast.o lstMember.o lstNext.o lstOpen.o lstRemove.o lstReplace.o lstSucc.o compat.o: Undefined symbol `___error' referenced from text segment job.o: Undefined symbol `___error' referenced from text segment job.o: Undefined symbol `___error' referenced from text segment job.o: Undefined symbol `___error' referenced from text segment job.o: Undefined symbol `___error' referenced from text segment job.o: Undefined symbol `___error' referenced from text segment job.o: Undefined symbol `___error' referenced from text segment main.o: Undefined symbol `___error' referenced from text segment main.o: Undefined symbol `___error' referenced from text segment *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. -------------------------- Someone want to shed some light on this.... Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 18:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21250 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:28:12 -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 SAA21242; Thu, 31 Dec 1998 18:28:05 -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 MAA15754; Fri, 1 Jan 1999 12:56:52 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id MAA41974; Fri, 1 Jan 1999 12:56:56 +1030 (CST) Message-ID: <19990101125656.C41841@freebie.lemis.com> Date: Fri, 1 Jan 1999 12:56:56 +1030 From: Greg Lehey To: "Jonathan M. Bresler" , green@unixhelp.org Cc: mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG Subject: GPL (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199901010217.SAA20264@hub.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199901010217.SAA20264@hub.freebsd.org>; from Jonathan M. Bresler on Thu, Dec 31, 1998 at 06:17:33PM -0800 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 On Thursday, 31 December 1998 at 18:17:33 -0800, Jonathan M. Bresler wrote: >> Date: Thu, 31 Dec 1998 21:01:32 -0500 (EST) >> From: Brian Feldman >> >> The GPL works fine with FreeBSD, we have a src/gnu, if you don't remember. The >> only major caveats with GPL are (as I see it) that: >> 1. We don't want GPL stuff in the kernel, hence the EXTREMELY few >> GPL drivers. (the GPL'd math emulator, and one other...) >> 2. GPL does not necessarily mean good. Not all the standard GNU >> utilities are good, nor even as good as the BSD predecessors. >> The GPL does not prevent us from including exim because: >> 1. We keep the source open, and changes public. >> 2. We don't change the license (we can't), so we don't violate the GPL. >> >> If you can find any fault in including exim, state it. > > can a company take FreeBSD, including exim, make modifications and > sell the result. several companies to this. the gnat box, nokia, > whistle and others. > > if they can, i have misunderstood, that would be my fault. The only way to have any kind of certainty about this would be a court decision, and even that would be valid only for a certain geographical area. The way I see it, the decision is whether the GPL'd part of the software is indivisible from the rest. Otherwise you take FreeBSD, including exim, make modifications and sell the result, explicitly excluding exim from the part of the software which has been bought (``also includes--*free*--exim and all those GNU packages you know and love''). Last September, Stallman was bitching about people like Caldera who sell their product and put GNU utilities on the same CD-ROM. But I don't see anybody getting sued for this kind of thing, and I think it's rather unlikely that they will. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 18:30:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA21424 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:30:35 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA21411; Thu, 31 Dec 1998 18:30:31 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id WAA17519; Thu, 31 Dec 1998 22:29:44 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 31 Dec 1998 22:29:44 -0400 (AST) From: The Hermit Hacker To: sthaug@nethelp.no cc: jmb@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <15807.915119903@verdi.nethelp.no> 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, 31 Dec 1998 sthaug@nethelp.no wrote: > > > > We gain the ability to emphasise Postfix and de-emphasise Sendmail. > > > > After an appropriate period, we gain the ability to nuke Sendmail > > > > as Postfix has been solidly tested/used/ported/integrated for > > > > "long enough". No combustion over definitions of "long enough", > > > > please :-). > ... > > Here here...I trust and like sendmail, and have no intentions of > > switching from it... > > I have worked with sendmail for a long time, and have made consulting > money helping companies to configure their sendmail systems. But "like" > and "trust" are words I'd never use together with sendmail. Even after > having worked with sendmail for a long time, I found qmail considerably > easier to get started with (and easier to configure in general). > > If Postfix can help us get away from sendmail as the default, I'd say > it's definitely a good thing. > > But I fear this discussion is going in the religious direction... Hasn't it been such since the beginning? The problem is that its being proposed to take the *established* religion (sendmail) and replacing it with someone else's idea of "the perfect religion" (postfix)... If -core feels that this is the right thing to do, there isn't a thing any of us are going to do to stop this (as has been seen at least once in the recent past?). The *most* appropriate solution to this whole thing, so far, that has been proposed, is to remove both and make then *both* ports... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 31 18:42:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22067 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:42:23 -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 SAA22061; Thu, 31 Dec 1998 18:42:22 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id SAA07866; Thu, 31 Dec 1998 18:42:00 -0800 (PST) (envelope-from dillon) Date: Thu, 31 Dec 1998 18:42:00 -0800 (PST) From: Matthew Dillon Message-Id: <199901010242.SAA07866@apollo.backplane.com> To: "Jonathan M. Bresler" Cc: grog@lemis.com, donegan@quick.net, current@FreeBSD.ORG Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199901010122.RAA05674@apollo.backplane.com> <199901010205.SAA19303@hub.freebsd.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : : current has 1411 subscribers. each wonts to get the message : first! if we do 100 messages a day that's only 141,100 What, only 1411? The sendmail limitation you are discussing is a basic queueing / DNS resolver limitation that is relatively easy to solve. Postfix is almost certainly faster, but it makes no sense to put postfix in our base distribution just because you have a 1400 user mailing list and your list software doesn't break them up a little before starting up sendmail! -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 31 18:43:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22346 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:43:24 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from janus.syracuse.net (janus.syracuse.net [205.232.47.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22339; Thu, 31 Dec 1998 18:43:20 -0800 (PST) (envelope-from green@unixhelp.org) Received: from localhost (green@localhost) by janus.syracuse.net (8.8.8/8.8.7) with ESMTP id VAA11619; Thu, 31 Dec 1998 21:43:05 -0500 (EST) Date: Thu, 31 Dec 1998 21:43:05 -0500 (EST) From: Brian Feldman X-Sender: green@janus.syracuse.net To: "Jonathan M. Bresler" cc: mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199901010217.SAA20264@hub.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Jonathan M. Bresler wrote: > > Date: Thu, 31 Dec 1998 21:01:32 -0500 (EST) > > From: Brian Feldman > > > > The GPL works fine with FreeBSD, we have a src/gnu, if you don't remember. The > > only major caveats with GPL are (as I see it) that: > > 1. We don't want GPL stuff in the kernel, hence the EXTREMELY few > > GPL drivers. (the GPL'd math emulator, and one other...) > > 2. GPL does not necessarily mean good. Not all the standard GNU > > utilities are good, nor even as good as the BSD predecessors. > > The GPL does not prevent us from including exim because: > > 1. We keep the source open, and changes public. > > 2. We don't change the license (we can't), so we don't violate the GPL. > > > > If you can find any fault in including exim, state it. > > > can a company take FreeBSD, including exim, make modifications and > sell the result. several companies to this. the gnat box, nokia, > whistle and others. They seem to have, seeing as we already HAVE GPL software included in the base distribution. Maybe you should ask Julian Elischer :) > > if they can, i have misunderstood, that would be my fault. > > jmb > > ps. my lst message to current was delivered in 30 seconds 600 and > 624 messages in the two 15 second intervals. thats 144k and > 150k messages per hour. for those that are counting. > Brian Feldman _ __ ___ ___ ___ green@unixhelp.org _ __ ___ | _ ) __| \ http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | FreeBSD: 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 Thu Dec 31 18:44:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22422 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:44:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from ns1.adsu.bellsouth.com (ns1.adsu.bellsouth.com [205.152.173.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22412 for ; Thu, 31 Dec 1998 18:44:39 -0800 (PST) (envelope-from ck@ns1.adsu.bellsouth.com) Received: (from ck@localhost) by ns1.adsu.bellsouth.com (8.9.1a/8.9.1) id VAA17825; Thu, 31 Dec 1998 21:44:12 -0500 (EST) Message-ID: <19981231214412.C4306@ns1.adsu.bellsouth.com> Date: Thu, 31 Dec 1998 21:44:12 +875500 From: Christian Kuhtz To: Scott Barron Cc: current@FreeBSD.ORG Subject: Re: Trouble with Staroffice5.0 References: <19981231165447.A2862@tar.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Scott Barron on Thu, Dec 31, 1998 at 05:44:03PM -0600 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 31, 1998 at 05:44:03PM -0600, Scott Barron wrote: > I would like to add a note here. I had the same problem described > while running Linux. My box has 96M RAM and about 130M of swap space. Star > Office would freeze in about the same place, but I was not so lucky to have > regained control of my keyboard and hence had to do a cold boot. After doing > it twice I decided to heck with it and downloaded word perfect 8. I have not > tried anything on FreeBSD yet. Has anyone attempted running WP8 on FreeBSD? > It was a lot less resource hungry than SO4 on Linux. WordPerfect8 works like a charm on a recent 3.0-CURRENT box. Cheers, Chris -- "Economics is extremely useful as a form of employment for economists." -- John Kenneth Galbraith [Disclaimer: I speak for myself and my views are my own and not in any way to be construed as the views of BellSouth Corporation. ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 18:48:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22671 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:48:16 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cis.ohio-state.edu (mail.cis.ohio-state.edu [164.107.115.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA22665; Thu, 31 Dec 1998 18:48:14 -0800 (PST) (envelope-from cmcurtin@cis.ohio-state.edu) Received: from gold.cis.ohio-state.edu (gold.cis.ohio-state.edu [164.107.112.16]) by cis.ohio-state.edu (8.9.1/8.9.1) with ESMTP id VAA28769; Thu, 31 Dec 1998 21:47:40 -0500 (EST) Received: (from cmcurtin@localhost) by gold.cis.ohio-state.edu (8.9.1/8.9.1) id VAA10705; Thu, 31 Dec 1998 21:47:39 -0500 (EST) To: Matthew Dillon Cc: Greg Lehey , "Jonathan M. Bresler" , donegan@quick.net, current@FreeBSD.ORG Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199901010122.RAA05674@apollo.backplane.com> X-Face: L"IcL.b%SDN]0Kql2b`e.}+i05V9fi\yX#H1+Xl)3!+n/3?5`%-SA-HDgPk9uTk<3dv^J5DCgal)-E{`zN#*o6F|y>r)\< Date: 31 Dec 1998 21:47:39 -0500 In-Reply-To: Matthew Dillon's message of "Thu, 31 Dec 1998 17:22:22 -0800 (PST)" Message-ID: Lines: 27 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon writes: > This new mail program thingy should be a port. I would like to > point out that there is nothing wrong with ports... hell, even > 'less' is a port! Agreed. Sendmail has its problems, and other MTAs, especially Postfix, do solve some of these problems. But I think it would be *much* more prudent to introduce Postfix to FreeBSD in the form of a port. It just hasn't been in the open long enough to have its bugs shaken out. It was only in the last week that some changes were made after some folks took a peek at how Postfix is implemented. The few sites who actually do need the sort of performance increases (or any other advantage) offered by Postfix could easily get it working from the ports collection. The vast majority of sites are more likely to want to err on the side of stability. Give Postfix more time to be more thoroughly reviewed before making it the standard MTA. -- Matt Curtin cmcurtin@interhack.net http://www.interhack.net/people/cmcurtin/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 18:50:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA22844 for freebsd-current-outgoing; Thu, 31 Dec 1998 18:50:25 -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 SAA22838 for ; Thu, 31 Dec 1998 18:50:21 -0800 (PST) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.9.1/8.9.1) id NAA27971; Fri, 1 Jan 1999 13:53:42 +1100 (EST) (envelope-from jb) From: John Birrell Message-Id: <199901010253.NAA27971@cimlogic.com.au> Subject: Re: make world dies....whats up??? In-Reply-To: from Bill Woods at "Dec 31, 98 06:25:46 pm" To: wwoods@cybcon.com (Bill Woods) Date: Fri, 1 Jan 1999 13:53:42 +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 Bill Woods wrote: > I am, from a clean install of 2.2.6 trying to do a make world to go to > 3.0-current. I just cvsupped the latest source a few mins ago and on a > make world I get... Your build is failing because of a problem with src/Makefile.inc1 which tries to use the current headers before certain tools are bootstrapped. If you have either cvsupped the cvs repository or sufficient net bandwidth, checkout the 3.0-RELEASE sources and theb do a make aout-to-elf. -- 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 31 19:10:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA23586 for freebsd-current-outgoing; Thu, 31 Dec 1998 19:10:25 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA23576; Thu, 31 Dec 1998 19:10:24 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id XAA17711; Thu, 31 Dec 1998 23:09:59 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 31 Dec 1998 23:09:59 -0400 (AST) From: The Hermit Hacker To: Matthew Dillon cc: "Jonathan M. Bresler" , grog@lemis.com, donegan@quick.net, current@FreeBSD.ORG Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) In-Reply-To: <199901010242.SAA07866@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Matthew Dillon wrote: > : > : current has 1411 subscribers. each wonts to get the message > : first! if we do 100 messages a day that's only 141,100 > > What, only 1411? > > The sendmail limitation you are discussing is a basic queueing / DNS > resolver limitation that is relatively easy to solve. Postfix is > almost certainly faster, but it makes no sense to put postfix > in our base distribution just because you have a 1400 user mailing > list and your list software doesn't break them up a little before > starting up sendmail! have to agree there...I run one list that is 9k+ subscribers, through sendmail, and use jbl(?) to break them up into smaller, more manageable and faster to process chunks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 31 19:26:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA24599 for freebsd-current-outgoing; Thu, 31 Dec 1998 19:26:39 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail13.svr.pol.co.uk (mail13.svr.pol.co.uk [195.92.193.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA24591 for ; Thu, 31 Dec 1998 19:26:37 -0800 (PST) (envelope-from pierre.dampure@k2c.co.uk) Received: from modem-91.doxycycline.dialup.pol.co.uk ([62.136.63.219] helo=bladerunner.k2c.co.uk) by mail13.svr.pol.co.uk with esmtp (Exim 2.10 #1) id 0zvvE3-0007vJ-00 for current@FreeBSD.ORG; Fri, 1 Jan 1999 03:26:11 +0000 Received: from k2c.co.uk (localhost [127.0.0.1]) by bladerunner.k2c.co.uk (8.9.1/8.9.1) with ESMTP id DAA00944 for ; Fri, 1 Jan 1999 03:21:54 GMT (envelope-from pierre.dampure@k2c.co.uk) Message-ID: <368C3F52.D343F827@k2c.co.uk> Date: Fri, 01 Jan 1999 03:21:54 +0000 From: "Pierre Y. Dampure" Organization: K2C Ltd X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: current@FreeBSD.ORG Subject: Re: sendmail throughput (was: HEADS UP: Postfix is coming. new uid, gid required.) References: <199901010122.RAA05674@apollo.backplane.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My two cents (or "mes deux francs", or whatever... and I should most probably stay put about it): I currently contract for Barclays Capital (investment bank). Our "mother" company, Barclays Bank Plc, relies on sendmail for Internet mail traffic and uses FreeBSD as the external mail hub. All in-house Un*x boxen use sendmail as their MTA (HP, Sun). The Un*x support staff swears and breathes by the Bat Book. So does the staff in all other major City banks I know of. I have NO problems seing Postfix brought up as a port -- we already do so for other MTAs and the /etc/make.conf option makes it easy -- but, up until we have a RELEASED version (as opposed to a beta, even if it's better than most releases), I think we should not bring it into the contrib tree -- for risk of losing credibility. Don't get me wrong, most of us here in BC (and elsewhere I guess) are already looking at Postfix -- we are painfully aware of sendmail's deficiencies and would love to use a better tool. The point is: it will take some time for Postfix to get recognised / accepted, let's not jump the gun. Best Regards, PYD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 19:34:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA25435 for freebsd-current-outgoing; Thu, 31 Dec 1998 19:34:26 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from proxy.vvm.com (proxy.vvm.com [204.71.94.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA25430 for ; Thu, 31 Dec 1998 19:34:25 -0800 (PST) (envelope-from sbarron@vvm.com) Received: from ns.vvm.com (IDENT:root@ns.vvm.com [204.71.94.1]) by proxy.vvm.com (8.9.1/8.9.1) with ESMTP id VAA32679; Thu, 31 Dec 1998 21:35:40 -0600 Received: from avalon.abalonesoft.com (ka02-187.vvm.com [206.97.170.187]) by ns.vvm.com (8.8.8/8.9.1) with ESMTP id VAA00337; Thu, 31 Dec 1998 21:33:57 -0600 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: <19981231214412.C4306@ns1.adsu.bellsouth.com> Date: Thu, 31 Dec 1998 21:36:05 -0600 (CST) From: Scott Barron To: Christian Kuhtz Subject: WordPerfect8 (Was Re: Trouble with Staroffice5.0) Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 28-Dec-98 Christian Kuhtz wrote: > > WordPerfect8 works like a charm on a recent 3.0-CURRENT box. > > Cheers, > Chris > Does it have to be an ELF system? The install is failing here with errors of ELF binary type not known. Ah well, regardless its time I get rid of a.out anyway. Good thing its a long weekend :) -Scott > -- > "Economics is extremely useful as a form of employment for economists." > -- John Kenneth Galbraith > > [Disclaimer: I speak for myself and my views are my own and not in any way to > be construed as the views of BellSouth Corporation. ] > ------------------------------------------------------------------------------- Brought to you by: FreeBSD avalon 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Thu Dec 31 20:54:12 CST 1998 root@vvm.com:/usr/src/sys/compile/AENIMA i386 Up and running for: 9:35PM up 37 mins, 3 users, load averages: 0.32, 0.32, 0.30 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 20:46:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA29895 for freebsd-current-outgoing; Thu, 31 Dec 1998 20:46:18 -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 UAA29888; Thu, 31 Dec 1998 20:46:16 -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 XAA39209; Thu, 31 Dec 1998 23:49:41 -0500 (EST) (envelope-from bright@hotjobs.com) X-Authentication-Warning: bright.fx.genx.net: bright owned process doing -bs Date: Thu, 31 Dec 1998 23:49:41 -0500 (EST) From: Alfred Perlstein X-Sender: bright@bright.fx.genx.net To: Brian Feldman cc: "Jonathan M. Bresler" , mark@grondar.za, donegan@quick.net, scrappy@hub.org, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Brian Feldman wrote: > > > Date: Thu, 31 Dec 1998 21:01:32 -0500 (EST) > > > From: Brian Feldman > > > > > > The GPL works fine with FreeBSD, we have a src/gnu, if you don't remember. The [...] > > > If you can find any fault in including exim, state it. > > > > > > can a company take FreeBSD, including exim, make modifications and > > sell the result. several companies to this. the gnat box, nokia, > > whistle and others. > > They seem to have, seeing as we already HAVE GPL software included in the > base distribution. Maybe you should ask Julian Elischer :) Brian, perhaps instead of flooding my mailbox with your ramblings you could: 1) Wait a couple of years and manage a few lists of this volume like our friend Jonathan has. 2) Perform a 2 year (hell 5 year) study on the various mailers, it'll keep you busy, trust me. 3) Realize that exim isn't bundled with any system and would be a big step backwards in making FreeBSD a choice for a homeogenous shop and that it's in the ports if you need it. 4) Realize that there is news that several commercial Unix vendors are quite possibly moving to Postfix. It would be to FreeBSD's advantage to roll with them into this. And I really wish everyone would realize that jmb is only adding postfix, HE IS NOT REMOVING SENDMAIL. All you m4 freaks settle down a bit, get off his back, and step out of the way of progress, thanks. :) -Alfred "my MTA is netcat" Perlstein > > Brian Feldman _ __ ___ ___ ___ > green@unixhelp.org _ __ ___ | _ ) __| \ > http://www.freebsd.org/ _ __ ___ ____ | _ \__ \ |) | > FreeBSD: 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 Thu Dec 31 21:17:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02369 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:17:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mich.bolingbroke.com (mich.bolingbroke.com [206.253.250.210]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02363 for ; Thu, 31 Dec 1998 21:17:01 -0800 (PST) (envelope-from ken@bolingbroke.com) Received: from localhost (ken@localhost) by mich.bolingbroke.com (8.9.0/8.9.0) with ESMTP id WAA14726 for ; Thu, 31 Dec 1998 22:16:29 -0700 (MST) Date: Thu, 31 Dec 1998 22:16:28 -0700 (MST) From: Ken Bolingbroke X-Sender: ken@mich To: FreeBSD-current@FreeBSD.ORG Subject: subscribe 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 subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 21:22:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA02884 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:22:51 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from bugs.us.dell.com (bugs.us.dell.com [143.166.169.147]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA02877 for ; Thu, 31 Dec 1998 21:22:49 -0800 (PST) (envelope-from tony@dell.com) Received: from ant (ant.us.dell.com [143.166.12.34]) by bugs.us.dell.com (8.8.8/8.8.8) with SMTP id XAA15750 for ; Thu, 31 Dec 1998 23:22:27 -0600 (CST) (envelope-from tony@dell.com) Message-Id: <3.0.6.32.19981231232223.00a116a0@bugs.us.dell.com> X-Sender: tony@bugs.us.dell.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Thu, 31 Dec 1998 23:22:23 -0600 To: current@FreeBSD.ORG From: Tony Overfield Subject: processes hanging in "inode" state? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lately, I have been playing with -current on a test system. When I do a "make -j 8 world", everything always works fine with small to moderate amounts of swap usage. When I do a "make -j 32 world", as expected, I encounter a greatly increased amount of swap usage. However, it doesn't ever finish. After a long time, everything simply stops and it cannot start any new programs. If I happen to have top already running, I can switch to it and see numerous processes stuck in the "inode" state. I have no reason to suspect hardware trouble and I think I have plenty of swap space for this to complete, if only it didn't hang. What should I do to find (or help somebody find) the problem? P5/MMX 233MHz, 430FX/PIIX3, 64MB EDO DRAM, 2940U, Quantum/DEC DSP3210. - Tony To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 21:30:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA03292 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:30:04 -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 VAA03279 for ; Thu, 31 Dec 1998 21:30:01 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.1/8.9.1) id VAA09794; Thu, 31 Dec 1998 21:29:34 -0800 (PST) (envelope-from dillon) Date: Thu, 31 Dec 1998 21:29:34 -0800 (PST) From: Matthew Dillon Message-Id: <199901010529.VAA09794@apollo.backplane.com> To: Tony Overfield Cc: current@FreeBSD.ORG Subject: Re: processes hanging in "inode" state? Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Lately, I have been playing with -current on a test system. When :I do a "make -j 8 world", everything always works fine with small :to moderate amounts of swap usage. When I do a "make -j 32 world", :as expected, I encounter a greatly increased amount of swap usage. :However, it doesn't ever finish. After a long time, everything :simply stops and it cannot start any new programs. If I happen to :have top already running, I can switch to it and see numerous :... : :I have no reason to suspect hardware trouble and I think I have :plenty of swap space for this to complete, if only it didn't hang. : :What should I do to find (or help somebody find) the problem? : :P5/MMX 233MHz, 430FX/PIIX3, 64MB EDO DRAM, 2940U, Quantum/DEC DSP3210. : :- Tony It's probably a memory deadlock somewhere. If you have DDB configured, you can control-alt-escape into the debugger and do a 'ps' to see what various processes are waiting on. That kind of dump would be very helpful. Most of the memory related deadlock issues will be resolved after the 3.0.1 release and the tree split, assuming David Greenman and I can come to agreement (which I think is likely). I've been working on a nearly complete replacement for the swap pager and along with that comes a whole slew of fixes for various low-memory deadlock conditions. I'm using a diskless bootp workstation with MFS filesystems and NFS swap as a testbed - a combination that tends to bring out the worse in the kernel :-) -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 31 21:44:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA04854 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:44:10 -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 VAA04845 for ; Thu, 31 Dec 1998 21:44:07 -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 QAA02013; Fri, 1 Jan 1999 16:43:43 +1100 Date: Fri, 1 Jan 1999 16:43:43 +1100 From: Bruce Evans Message-Id: <199901010543.QAA02013@godzilla.zeta.org.au> To: current@FreeBSD.ORG, nik@nothing-going-on.demon.co.uk Subject: Re: Going from 2.x to 3.x using 'make world' Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Has anyone successfully gone from 2.x to 3.x using 'make world'? If so, did >you write down what you did? How about unsucessfully? :-) I tried going from 2.1.5 to -current and noticed the following problems: (1) The 2.1.5 install was very buggy. (2) The bootstrap of `make' failed because of bitrot in the portability of `make' (`make' it now calls sysctlbyname()). (3) The bootstrap of `mtree' failed because unportabilities in `mtree' moved (`mtree' references timespecs in struct stat, and the spelling of the fields changed from ts_* to tv_*). (4) The bootstrap installs new headers early in an attempt to reduce problems like the one in (3), although this is wrong. This is fatal for the bootstrap from 2.1.5 because the 2.1.5 compiler (gcc-2.2.6) doesn't understand the __attribute__ stuff in . (5) The bootstrap installs new libraries early in an attempt to reduce problems like the one in (2) and to be consistent with the wrong headers in (4), although this is wrong. (a) Early building of libraries (bootstrap-libraries) was broken some time ago by moving it after the build of the tools that are necessarry to build the libraries (lib-tools). This is fatal for the bootstrap from 2.1.5. (b) Building lib-tools first doesn't work because of some old bugs bootstrapping libgcc (the wrong compiler apparently gets used and doesn't understand new __attribute__ stuff in libgcc2.c). 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 31 21:44:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05153 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:44:45 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from adelphi.physics.adelaide.edu.au (adelphi.physics.adelaide.edu.au [129.127.36.247]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05127 for ; Thu, 31 Dec 1998 21:44:33 -0800 (PST) (envelope-from kkennawa@physics.adelaide.edu.au) Received: from bragg (bragg [129.127.36.34]) by adelphi.physics.adelaide.edu.au (8.8.8/8.8.8/UofA-1.5) with SMTP id QAA27761; Fri, 1 Jan 1999 16:14:05 +1030 (CST) Received: from localhost by bragg; (5.65/1.1.8.2/05Aug95-0227PM) id AA25396; Fri, 1 Jan 1999 16:14:05 +1030 Date: Fri, 1 Jan 1999 16:14:04 +1030 (CST) From: Kris Kennaway X-Sender: kkennawa@bragg To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <19990101125155.B41841@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 On Fri, 1 Jan 1999, Greg Lehey wrote: > Date: Thu, 31 Dec 1998 20:51:53 +875500 > > This is the second message today I got with a completely crazy time > zone offset (which put you back two days in my inbox listing). Does > anybody have any idea why? Y2K? :-) Kris ----- (ASP) Microsoft Corporation (MSFT) announced today that the release of its productivity suite, Office 2000, will be delayed until the first quarter of 1901. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 21:47:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05502 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:47:08 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from thelab.hub.org (nat1262.mpoweredpc.net [142.177.186.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05494; Thu, 31 Dec 1998 21:47:07 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id BAA19109; Fri, 1 Jan 1999 01:46:40 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Fri, 1 Jan 1999 01:46:40 -0400 (AST) From: The Hermit Hacker To: Alfred Perlstein cc: Brian Feldman , "Jonathan M. Bresler" , mark@grondar.za, donegan@quick.net, dcs@newsguy.com, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 31 Dec 1998, Alfred Perlstein wrote: > > On Thu, 31 Dec 1998, Brian Feldman wrote: > > > > > Date: Thu, 31 Dec 1998 21:01:32 -0500 (EST) > > > > From: Brian Feldman > > > > > > > > The GPL works fine with FreeBSD, we have a src/gnu, if you don't remember. The > [...] > > > > If you can find any fault in including exim, state it. > > > > > > > > > can a company take FreeBSD, including exim, make modifications and > > > sell the result. several companies to this. the gnat box, nokia, > > > whistle and others. > > > > They seem to have, seeing as we already HAVE GPL software included in the > > base distribution. Maybe you should ask Julian Elischer :) > > Brian, perhaps instead of flooding my mailbox with your ramblings you could: > > 1) Wait a couple of years and manage a few lists of this volume like our > friend Jonathan has. If 1411 is the worst he's dealing with, then I can count myself as complying with your first "rambling" here...and i use sendmail/majordomo/tlb to manage it...quite painlessly... > 4) Realize that there is news that several commercial Unix vendors are > quite possibly moving to Postfix. It would be to FreeBSD's advantage > to roll with them into this. Wow, you don't say? News? So, like, ppl are considering adopting it, but nobody is actually *moving* towards it? Interesting...sounds like we should be *considering* adopting it by putting it into ports first, and evaluate it from there... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 31 21:49:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05723 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:49:44 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from zeus.theinternet.com.au (zeus.theinternet.com.au [203.34.176.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05718 for ; Thu, 31 Dec 1998 21:49:41 -0800 (PST) (envelope-from akm@zeus.theinternet.com.au) Received: (from akm@localhost) by zeus.theinternet.com.au (8.8.7/8.8.7) id PAA06472 for freebsd-current@freebsd.org; Fri, 1 Jan 1999 15:51:00 +1000 (EST) (envelope-from akm) From: Andrew Kenneth Milton Message-Id: <199901010551.PAA06472@zeus.theinternet.com.au> Subject: Buildworld fails in chpass To: freebsd-current@FreeBSD.ORG Date: Fri, 1 Jan 1999 15:51:00 +1000 (EST) 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 This has been happening to me for about a week... First time I thought I cvsupped between updates, and I let it go, next time I got the logo.c thing, then I got the bootblocks thing, now I'm back here again... :-) Haven't seen anything on the list about it, so I guess it only effects non-US people? I nearly always cvsup from cvsup2 ===> usr.bin/chpass cc -O -pipe -Wall -I/export/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb -I/export/src/usr.bin/chpass/../../usr.sbin/vipw -DYP -I. -I/export/src/usr.bin/chpass/../../libexec/ypxfr -I/export/src/usr.bin/chpass/../../usr.sbin/rpc.yppasswdd -Dyp_error=warnx -I/usr/obj/elf/export/src/tmp/usr/include -c /export/src/usr.bin/chpass/chpass.c cc -O -pipe -Wall -I/export/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb -I/export/src/usr.bin/chpass/../../usr.sbin/vipw -DYP -I. -I/export/src/usr.bin/chpass/../../libexec/ypxfr -I/export/src/usr.bin/chpass/../../usr.sbin/rpc.yppasswdd -Dyp_error=warnx -I/usr/obj/elf/export/src/tmp/usr/include -c /export/src/usr.bin/chpass/edit.c cc -O -pipe -Wall -I/export/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb -I/export/src/usr.bin/chpass/../../usr.sbin/vipw -DYP -I. -I/export/src/usr.bin/chpass/../../libexec/ypxfr -I/export/src/usr.bin/chpass/../../usr.sbin/rpc.yppasswdd -Dyp_error=warnx -I/usr/obj/elf/export/src/tmp/usr/include -c /export/src/usr.bin/chpass/field.c cc -O -pipe -Wall -I/export/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb -I/export/src/usr.bin/chpass/../../usr.sbin/vipw -DYP -I. -I/export/src/usr.bin/chpass/../../libexec/ypxfr -I/export/src/usr.bin/chpass/../../usr.sbin/rpc.yppasswdd -Dyp_error=warnx -I/usr/obj/elf/export/src/tmp/usr/include -c /export/src/usr.bin/chpass/pw_copy.c cc -O -pipe -Wall -I/export/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb -I/export/src/usr.bin/chpass/../../usr.sbin/vipw -DYP -I. -I/export/src/usr.bin/chpass/../../libexec/ypxfr -I/export/src/usr.bin/chpass/../../usr.sbin/rpc.yppasswdd -Dyp_error=warnx -I/usr/obj/elf/export/src/tmp/usr/include -c /export/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb/pw_scan.c cc -O -pipe -Wall -I/export/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb -I/export/src/usr.bin/chpass/../../usr.sbin/vipw -DYP -I. -I/export/src/usr.bin/chpass/../../libexec/ypxfr -I/export/src/usr.bin/chpass/../../usr.sbin/rpc.yppasswdd -Dyp_error=warnx -I/usr/obj/elf/export/src/tmp/usr/include -c /export/src/usr.bin/chpass/../../usr.sbin/vipw/pw_util.c cc -O -pipe -Wall -I/export/src/usr.bin/chpass/../../usr.sbin/pwd_mkdb -I/export/src/usr.bin/chpass/../../usr.sbin/vipw -DYP -I. -I/export/src/usr.bin/chpass/../../libexec/ypxfr -I/export/src/usr.bin/chpass/../../usr.sbin/rpc.yppasswdd -Dyp_error=warnx -I/usr/obj/elf/export/src/tmp/usr/include -c /export/src/usr.bin/chpass/pw_yp.c /export/src/usr.bin/chpass/pw_yp.c:68: yppasswd_private.h: No such file or directory /export/src/usr.bin/chpass/pw_yp.c: In function `get_yp_master': /export/src/usr.bin/chpass/pw_yp.c:341: `YP_SOCKNAME' undeclared (first use this function) /export/src/usr.bin/chpass/pw_yp.c:341: (Each undeclared identifier is reported only once /export/src/usr.bin/chpass/pw_yp.c:341: for each function it appears in.) /export/src/usr.bin/chpass/pw_yp.c: In function `yp_submit': /export/src/usr.bin/chpass/pw_yp.c:419: storage size of `master_yppasswd' isn't known /export/src/usr.bin/chpass/pw_yp.c:424: `YP_SOCKNAME' undeclared (first use this function) /export/src/usr.bin/chpass/pw_yp.c:477: `MASTER_YPPASSWDPROG' undeclared (first use this function) /export/src/usr.bin/chpass/pw_yp.c:478: `MASTER_YPPASSWDVERS' undeclared (first use this function) /export/src/usr.bin/chpass/pw_yp.c:498: warning: implicit declaration of function `yppasswdproc_update_master_1' /export/src/usr.bin/chpass/pw_yp.c:498: warning: assignment makes pointer from integer without a cast /export/src/usr.bin/chpass/pw_yp.c:419: warning: unused variable `master_yppasswd' *** Error code 1 Stop. -- Totally Holistic Enterprises Internet| P:+61 7 3870 0066 | Andrew The Internet (Aust) Pty Ltd | F:+61 7 3870 4477 | Milton ACN: 082 081 472 | M:+61 416 022 411 |72 Col .Sig PO Box 837 Indooroopilly QLD 4068 |akm@theinternet.com.au|Specialist To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 21:50:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06018 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:50:55 -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 VAA06013 for ; Thu, 31 Dec 1998 21:50:54 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA18424; Thu, 31 Dec 1998 21:50:04 -0800 (PST) To: Andrzej Bialecki cc: Robert Nordier , peter@netplex.com.au, current@FreeBSD.ORG Subject: Re: HEADS UP: FLAG DAY COMING (was Re: New aout-to-elf build failures.) In-reply-to: Your message of "Thu, 31 Dec 1998 15:48:54 +0100." Date: Thu, 31 Dec 1998 21:50:03 -0800 Message-ID: <18420.915169803@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ??? And what about the boot floppies? As I understand, they were using > a.out kernels up to this point, weren't they? I guess we'll have to make up the space somewhere else. - 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 31 21:52:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06166 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:52:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from prefetch-atm.san.rr.com (ns1.san.rr.com [204.210.0.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06159 for ; Thu, 31 Dec 1998 21:52:52 -0800 (PST) (envelope-from Studded@san.rr.com) Received: from san.rr.com (dt087nac.san.rr.com [24.94.19.172]) by prefetch-atm.san.rr.com (8.8.7/8.8.8) with ESMTP id VAA26144; Thu, 31 Dec 1998 21:51:44 -0800 (PST) Message-ID: <368B10FA.9D87CD46@san.rr.com> Date: Wed, 30 Dec 1998 21:51:54 -0800 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Chris Timmons CC: John Polstra , current@FreeBSD.ORG Subject: Re: CVS issues References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris Timmons wrote: > > Different CVSup servers allow different numbers of connections. I can't > remember what you said would happen when the client gets connection > refused and has more A records to try; will it go to the next one? All well written network clients of any kind should do just that. :) Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 21:58:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06672 for freebsd-current-outgoing; Thu, 31 Dec 1998 21:58:08 -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 VAA06667 for ; Thu, 31 Dec 1998 21:58:07 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id VAA18464; Thu, 31 Dec 1998 21:57:44 -0800 (PST) To: "Brian Haskin" cc: current@FreeBSD.ORG Subject: Re: New aout-to-elf build failures. In-reply-to: Your message of "Thu, 31 Dec 1998 14:30:31 EST." <000601be34f4$0789f9a0$0b00000a@brianjr.haskin.org> Date: Thu, 31 Dec 1998 21:57:44 -0800 Message-ID: <18460.915170264@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > new stable and current branch is the point I was trying to make. To state it > another way, will there be an easy (source not binary) route for people at > the end off the 2.2-stable branch to get to the beginning 3.0-stable branch? The answer to that question is fuzzy at the moment. It's being worked on and one hopes that it will be possible using only sources. If not, there will be some sort of binary transition kit provided. > Also I just upgraded to -current using the 12/24 snap and then cvsuping the > rest of the way. I see via /etc/objformat that I'm, by default, using elf > for the binary format. Are the elf boot blocks and kernel being used by > default also; how do I tell? file /kernel If it says it's ELF, it's elf, otherwise not. Check /etc/make.conf for other flags. - 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 31 22:20:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08222 for freebsd-current-outgoing; Thu, 31 Dec 1998 22:20:00 -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 WAA08217 for ; Thu, 31 Dec 1998 22:19:57 -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 QAA16529; Fri, 1 Jan 1999 16:49:15 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id QAA42541; Fri, 1 Jan 1999 16:49:20 +1030 (CST) Message-ID: <19990101164920.O41841@freebie.lemis.com> Date: Fri, 1 Jan 1999 16:49:20 +1030 From: Greg Lehey To: Kris Kennaway Cc: current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. References: <19990101125155.B41841@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Kris Kennaway on Fri, Jan 01, 1999 at 04:14:04PM +1030 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 On Friday, 1 January 1999 at 16:14:04 +1030, Kris Kennaway wrote: > On Fri, 1 Jan 1999, Greg Lehey wrote: > >> Date: Thu, 31 Dec 1998 20:51:53 +875500 >> >> This is the second message today I got with a completely crazy time >> zone offset (which put you back two days in my inbox listing). Does >> anybody have any idea why? > > Y2K? :-) Y1.999K. Turns out it was a bug in mutt. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 22:50:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10399 for freebsd-current-outgoing; Thu, 31 Dec 1998 22:50:30 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from prefetch-atm.san.rr.com (ns1.san.rr.com [204.210.0.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10392 for ; Thu, 31 Dec 1998 22:50:28 -0800 (PST) (envelope-from Studded@san.rr.com) Received: from san.rr.com (dt087nac.san.rr.com [24.94.19.172]) by prefetch-atm.san.rr.com (8.8.7/8.8.8) with ESMTP id WAA03131; Thu, 31 Dec 1998 22:49:55 -0800 (PST) Message-ID: <368B1E9D.C367BED1@san.rr.com> Date: Wed, 30 Dec 1998 22:50:05 -0800 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Matt Behrens CC: Brian Feldman , gmarco@giovannelli.it, current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matt Behrens wrote: > You can create the same effect, but lose all of squid's extra > benefits like caching. I have also noticed that ppp -alias (which > uses the same code as natd, AFAIR) fails to submit some forms > properly using Netscape on a Windows box (probably Netscape's > fault). This bug might be long-gone though :) I recently set up a 2.2.8 natd box with apache and several vhosts on it. When I try to access the vhosts directly via windows netscape from behind the natd box I get only the document root. I haven't dug into this in detail yet, but I believe you're describing the same problem I'm seeing. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 22:53:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA10730 for freebsd-current-outgoing; Thu, 31 Dec 1998 22:53:06 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from prefetch-atm.san.rr.com (ns1.san.rr.com [204.210.0.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA10725 for ; Thu, 31 Dec 1998 22:53:05 -0800 (PST) (envelope-from Studded@san.rr.com) Received: from san.rr.com (dt087nac.san.rr.com [24.94.19.172]) by prefetch-atm.san.rr.com (8.8.7/8.8.8) with ESMTP id WAA03407; Thu, 31 Dec 1998 22:52:39 -0800 (PST) Message-ID: <368B1F41.62B93784@san.rr.com> Date: Wed, 30 Dec 1998 22:52:49 -0800 From: Doug Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: obrien@nuxi.ucdavis.edu CC: freebsd-current@FreeBSD.ORG Subject: Re: wanton Atticizing is bad References: <199812272253.OAA23572@bubble.didi.com.newsgate.clinet.fi> <19981228100010.B28404@nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > Or doing it 1st thing in 3.1-CURRENT, after 3.0-STABLE is branched. This > makes our intentions clear, and gives pcvt people time to realize they > either need to write vt100 emulation in syscons or loss the > functionality. Deleting something that *doesn't* work and has no maintainer makes sense. Deleting something that *DOES* work (like voxware or pcvt) is simply foolish. I'm a vocal advocate of deleting and/or port'ifying some of the cruft in our tree, but deleting something that works without providing a suitable substitute gains you nothing and pisses off your customers. Doug To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 22:59:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11213 for freebsd-current-outgoing; Thu, 31 Dec 1998 22:59:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11208 for ; Thu, 31 Dec 1998 22:59:53 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id XAA02320; Thu, 31 Dec 1998 23:59:14 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199901010659.XAA02320@pluto.plutotech.com> To: Nicolas Souchu cc: =?iso-8859-1?Q?Jos=E9_M=AA_Alcaide?= , freebsd-current@FreeBSD.ORG, "Justin T. Gibbs" Subject: Re: Request fo help with Zip Drive on vpo0 in -current] In-reply-to: Your message of "Wed, 30 Dec 1998 11:59:32 GMT." <19981230115932.64403@breizh.prism.uvsq.fr> Date: Thu, 31 Dec 1998 23:51:29 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Yes, I think. CAMDEBUG option makes all run correctly here. > >When CAMDEBUG is not set, VP0_DEBUG reports no XPT_SCSI_IO request. > >Justin? This is odd. I'm away for the holidays so I will not be able to look into this until I return on January 4th. I can't think of any reason why CAMDEBUG would have an effect on this. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 23:20:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12822 for freebsd-current-outgoing; Thu, 31 Dec 1998 23:20:07 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.kt.rim.or.jp (mail.kt.rim.or.jp [202.247.130.53]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12587 for ; Thu, 31 Dec 1998 23:20:00 -0800 (PST) (envelope-from kuriyama@sky.rim.or.jp) Received: from moon.sky.rim.or.jp (ppp382.kt.rim.or.jp [202.247.140.82]) by mail.kt.rim.or.jp (8.8.5/3.6W-RIMNET-98-06-09) with ESMTP id QAA07852; Fri, 1 Jan 1999 16:19:38 +0900 (JST) Received: from sky.rim.or.jp (earth.sky.rim.or.jp [192.168.1.2]) by moon.sky.rim.or.jp (8.8.8/3.5Wpl4/moon-1.0) with ESMTP id QAA25752; Fri, 1 Jan 1999 16:18:07 +0900 (JST) Message-ID: <368C75F7.AD836511@sky.rim.or.jp> Date: Fri, 01 Jan 1999 16:15:03 +0900 From: Jun Kuriyama X-Mailer: Mozilla 4.06 [ja] (Win95; I) MIME-Version: 1.0 To: "John W. DeBoskey" CC: freebsd-current@FreeBSD.ORG Subject: Re: Failure building dsssl/modular References: <199812301808.NAA04262@bb01f39.unx.sas.com> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John W. DeBoskey wrote: > >> Attempting to fetch from ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//. > fetch: pub/FreeBSD/distfiles//db130jpja-981223.diff.gz: cannot get remote modification time > fetch: ftp://ftp.freebsd.org/pub/FreeBSD/distfiles//db130jpja-981223.diff.gz: FTP error: > fetch: File unavailable (e.g., file not found, no access) > >> Couldn't fetch it - please try to retrieve this > >> port manually into /usr/ports/distfiles/ and try again. > *** Error code 1 Yes, ftp.freebsd.org does not have distfile for v1.30 yet. This will be done after Satoshi making package. > >> db130jpja-981223.diff.gz doesn't seem to exist on this system. > >> Attempting to fetch from http://www.freebsd.org/~kuriyama/distfiles/. > fetch: reading reply from www.freebsd.org: Connection refused > > The .gz files does not exist in ~kuriyama/distfiles/ though their > is a .diff file there. The file simply does not exist at: Hmmm, I can see db130jpja-981223.diff.gz in my ~kuriyama/public_html/distfiles/. Is there another person who cannot see my distfile? -- Jun Kuriyama // kuriyama@sky.rim.or.jp // kuriyama@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 23:29:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA13266 for freebsd-current-outgoing; Thu, 31 Dec 1998 23:29:22 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA13260; Thu, 31 Dec 1998 23:29:19 -0800 (PST) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id CAA04656; Fri, 1 Jan 1999 02:22:45 -0500 (EST) Date: Fri, 1 Jan 1999 02:22:44 -0500 (EST) From: Chuck Robey To: Mike Smith cc: "Jonathan M. Bresler" , mark@grondar.za, dcs@newsguy.com, alexandr@mail.eecis.udel.eud, committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-Reply-To: <199812312006.MAA01368@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 Thu, 31 Dec 1998, Mike Smith wrote: > > what if no one else likes postfix. > > > > postfix is coming into the tree as /usr/src/contrib. > > sendmail is the default mail transfer agent. > > individual users can switch either machines to use postfix as > > the mta. > > there is no intention of removing sendmail from the tree. > > This clearly demonstrates that there is no mandate, nor no technical > justification for bringing postfix in. Please make a port of it and > stay with convention. > > Now is not a good time for a -core member to be demonstrating personal > bias over established convention with regards to the FreeBSD source tree. Mike may be right, essentially, but it's too darn bad. Jon is extremely qualified to tell what a good mailer is, he's been in a unique position both to test *and* to benchmark the heck out of a mailer, he's found a mailer that is a huge improvement over sendmail in more ways than I care to list here and avoids future license problems, but politics isn't going to let this happen. Mike may be right, but it's depressing just the same. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 23:50:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14524 for freebsd-current-outgoing; Thu, 31 Dec 1998 23:50:04 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from mail.gtn.com (mail.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA14512 for ; Thu, 31 Dec 1998 23:50:01 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by mail.gtn.com (8.8.6/8.8.6) with UUCP id IAA12303 for current@FreeBSD.ORG; Fri, 1 Jan 1999 08:45:20 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.1/8.9.1) id OAA36394 for current@FreeBSD.ORG; Thu, 31 Dec 1998 14:33:16 +0100 (CET) (envelope-from andreas) Message-ID: <19981231143316.A36387@klemm.gtn.com> Date: Thu, 31 Dec 1998 14:33:16 +0100 From: Andreas Klemm To: current@FreeBSD.ORG Subject: make release broken Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -------------------------------------------------------------- >>> Installing legacy boot -------------------------------------------------------------- cd /usr/src/sys/i386/boot && make -DNOMAN install ===> biosboot install -c -o root -g wheel -m 444 boot1 boot2 /R/stage/trees/bin/usr/mdec/ ===> cdboot install -c -o root -g wheel -m 444 boot.img /R/stage/trees/bin/usr/mdec/cdboot ===> dosboot install -c -o root -g wheel -m 444 fbsdboot.exe /R/stage/trees/bin/usr/mdec ===> kzipboot install -c -o root -g wheel -m 444 kztail.o kzhead.o /R/stage/trees/bin/usr/l ib/aout ===> netboot install -c -o root -g wheel -m 555 nb8390.com nb3c509.com nb8390.rom nb3c509. rom /R/stage/trees/bin/usr/mdec ===> rawboot install -c -o root -g wheel -m 444 rawboot /R/stage/trees/bin/usr/mdec/rawboot chflags -R noschg /R/stage/trees touch release.2 for i in textproc/docproj; do cd /usr/ports/$i && make all install clean FORCE_ PKG_REGISTER=yes; done ===> Extracting for docproj-1.0 >> No MD5 checksum file. ===> Patching for docproj-1.0 ===> Configuring for docproj-1.0 ===> Installing for docproj-1.0 ===> docproj-1.0 depends on executable: instant - not found ===> Verifying install for instant in /usr/ports/textproc/sgmlformat ===> Extracting for sgmlformat-1.7 >> Checksum OK for sgmlformat-1.7.tar.gz. ===> Patching for sgmlformat-1.7 ===> Configuring for sgmlformat-1.7 ===> Building for sgmlformat-1.7 ===> instant Warning: Object directory not changed from original /usr/ports/textproc/sgmlform at/work/sgmlformat-1.7/instant cc -O -pipe -DTRANSPEC_DIR=\"/usr/local/share/sgml/transpec\" -c browse.c cc -O -pipe -DTRANSPEC_DIR=\"/usr/local/share/sgml/transpec\" -c info.c cc -O -pipe -DTRANSPEC_DIR=\"/usr/local/share/sgml/transpec\" -c main.c cc -O -pipe -DTRANSPEC_DIR=\"/usr/local/share/sgml/transpec\" -c tables.c cc -O -pipe -DTRANSPEC_DIR=\"/usr/local/share/sgml/transpec\" -c traninit.c cc -O -pipe -DTRANSPEC_DIR=\"/usr/local/share/sgml/transpec\" -c translate.c cc -O -pipe -DTRANSPEC_DIR=\"/usr/local/share/sgml/transpec\" -c tranvar.c cc -O -pipe -DTRANSPEC_DIR=\"/usr/local/share/sgml/transpec\" -c util.c cc -O -pipe -DTRANSPEC_DIR=\"/usr/local/share/sgml/transpec\" -c sgmls.c cc -O -pipe -DTRANSPEC_DIR=\"/usr/local/share/sgml/transpec\" -o instant brow se.o info.o main.o tables.o traninit.o translate.o tranvar.o util.o sgmls.o -lc ompat gzip -cn instant.1 > instant.1.gz gzip -cn transpec.5 > transpec.5.gz ===> transpec ===> sgmlfmt sed -e 's|##PERL##|/usr/bin/perl|' -e 's|##PREFIX##|/usr/local|' < sgmlfmt.pl > sgmlfmt Warning: Object directory not changed from original /usr/ports/textproc/sgmlform at/work/sgmlformat-1.7/sgmlfmt gzip -cn sgmlfmt.1 > sgmlfmt.1.gz ===> Installing for sgmlformat-1.7 ===> sgmlformat-1.7 depends on executable: nsgmls - not found ===> Verifying install for nsgmls in /usr/ports/textproc/jade /bin/sh: not found *** Error code 1 (ignored) ===> Extracting for jade-1.2 >> Checksum OK for jade1_2.zip. ===> jade-1.2 depends on executable: unzip - not found ===> Verifying install for unzip in /usr/ports/archivers/unzip /bin/sh: not found /bin/sh: not found *** Error code 1 (ignored) *** Error code 1 (ignored) *** Error code 1 (ignored) ===> Returning to build of jade-1.2 unzip: not found *** Error code 1 (ignored) ===> Patching for jade-1.2 ===> Applying FreeBSD patches for jade-1.2 File to patch: (END) BTW, I noticed, that make release now copies all distfiles from /usr/ports/distfiles to /disk2/release/usr/ports/distfiles Well, my 900MB large partition on /disk2 would have been unable to stand a make release. During the make release progress I removed the source in /disk2/release/usr/ports/distfiles and copied the needed one with a script into that location ... Is this build behaviour intended ? The solution months ago, where the actually needed sources have been fetched was better regarding space consumption. I'd suggest to copy the needed sources for ports very early to the destdir .../release/usr/ports/distfiles just before doing the chroot command ... This would prevent such unneeded space consumption. Or is this needed for another purpose ??? Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 23:52:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA14865 for freebsd-current-outgoing; Thu, 31 Dec 1998 23:52:22 -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 XAA14858 for ; Thu, 31 Dec 1998 23:52:19 -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 SAA16703; Fri, 1 Jan 1999 18:21:30 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id SAA42683; Fri, 1 Jan 1999 18:21:34 +1030 (CST) Message-ID: <19990101182134.P41841@freebie.lemis.com> Date: Fri, 1 Jan 1999 18:21:34 +1030 From: Greg Lehey To: Andreas Klemm , current@FreeBSD.ORG Subject: Re: make release broken References: <19981231143316.A36387@klemm.gtn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19981231143316.A36387@klemm.gtn.com>; from Andreas Klemm on Thu, Dec 31, 1998 at 02:33:16PM +0100 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 On Thursday, 31 December 1998 at 14:33:16 +0100, Andreas Klemm wrote: > -------------------------------------------------------------- > >>> Installing legacy boot > -------------------------------------------------------------- > ... > ===> Verifying install for nsgmls in /usr/ports/textproc/jade > /bin/sh: not found > *** Error code 1 (ignored) I had this recently on a ``make install''. It turned out that /bin/sh was secured 600. What do you have? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Dec 31 23:55:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA15035 for freebsd-current-outgoing; Thu, 31 Dec 1998 23:55:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from spinner.netplex.com.au (spinner.netplex.com.au [202.12.86.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA15026 for ; Thu, 31 Dec 1998 23:55:51 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from spinner.netplex.com.au (peter@localhost [127.0.0.1]) by spinner.netplex.com.au (8.9.1/8.9.1/Netplex) with ESMTP id PAA95330; Fri, 1 Jan 1999 15:55:09 +0800 (WST) (envelope-from peter@spinner.netplex.com.au) Message-Id: <199901010755.PAA95330@spinner.netplex.com.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Greg Lehey cc: Kris Kennaway , current@FreeBSD.ORG Subject: Re: HEADS UP: Postfix is coming. new uid, gid required. In-reply-to: Your message of "Fri, 01 Jan 1999 16:49:20 +1030." <19990101164920.O41841@freebie.lemis.com> Date: Fri, 01 Jan 1999 15:55:07 +0800 From: Peter Wemm Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lehey wrote: > On Friday, 1 January 1999 at 16:14:04 +1030, Kris Kennaway wrote: > > On Fri, 1 Jan 1999, Greg Lehey wrote: > > > >> Date: Thu, 31 Dec 1998 20:51:53 +875500 > >> > >> This is the second message today I got with a completely crazy time > >> zone offset (which put you back two days in my inbox listing). Does > >> anybody have any idea why? > > > > Y2K? :-) > > Y1.999K. Turns out it was a bug in mutt. Ewww... It's started already... :-O I think I'll try to arrange to be at least 100 kilometers from the nearest computer in about 12 months time... > Greg Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message