From owner-freebsd-stable Sun Nov 29 07:43:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09359 for freebsd-stable-outgoing; Sun, 29 Nov 1998 07:43:54 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phoenix (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA09354 for ; Sun, 29 Nov 1998 07:43:52 -0800 (PST) (envelope-from tarbert@aye.net) Received: (qmail 6938 invoked by uid 3155); 29 Nov 1998 15:41:53 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 29 Nov 1998 15:41:53 -0000 Date: Sun, 29 Nov 1998 10:41:53 -0500 (EST) From: Barrett Richardson Reply-To: Barrett Richardson To: cjclark@home.com cc: Don , freebsd-stable@FreeBSD.ORG Subject: Re: subscribe freebsd-stable In-Reply-To: <199811270312.WAA24575@cc942873-a.ewndsr1.nj.home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 26 Nov 1998, Crist J. Clark wrote: > Don wrote, > > > > subscribe freebsd-stable > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-stable" in the body of the message > > Have others noticed the increase in the number posts by people incapable > > of reading the directions on how to subscribe to a mailing list? > > > > -Don > > Me too. There are a good number of lists in internet land that can be subscribed too in the manner he attempted. After such exposure humans will frequently attempt the path of least resistance first and read the instructions later if it doesn't work. -- Barrett > > > > But remember what day it is: Thu Sep 1913 22:10:58 EST 1993 > -- > Crist J. Clark cjclark@home.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 29 09:16:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA14247 for freebsd-stable-outgoing; Sun, 29 Nov 1998 09:16:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA14240 for ; Sun, 29 Nov 1998 09:16:27 -0800 (PST) (envelope-from robinson@public.bta.net.cn) Received: (from robinson@localhost) by public.bta.net.cn (8.9.1/8.9.1) id BAA19704 for freebsd-stable@freebsd.org; Mon, 30 Nov 1998 01:16:31 +0800 (GMT) Date: Mon, 30 Nov 1998 01:16:31 +0800 (GMT) From: Michael Robinson Message-Id: <199811291716.BAA19704@public.bta.net.cn> To: freebsd-stable@FreeBSD.ORG Subject: Weird problem with nlpt Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running 2.2.7-RELEASE with ppbus on a Tecra 510CDT. The ppbus works fine with the vpo driver and my external Zip drive. However, I just added a new printer (Epson Stylus Color 800) which works fine on this hardware under Win95, but badly misbehaves with nlpt. If I run this command line: % echo -n '123^L' | lpr -lh I get a page that looks like this: +----------- | | 112233 | If I print a longer document, the printer gets a dozen or so bytes into the job and hangs. "ps -axl" shows the lpd process waiting on "nlptwr". Eventually lpd times out and dies, leaving the printer waiting for input. Comments? Suggestions? -Michael Robinson P.S. dmesg sez: ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (ECP/PS2/NIBBLE) in NIBBLE mode ppbus0: ppi0: on ppbus 0 nlpt0: on ppbus 0 nlpt0: Interrupt-driven port Probing vpo. vpo0: on ppbus 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 29 10:05:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA18886 for freebsd-stable-outgoing; Sun, 29 Nov 1998 10:05:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from calumet.infoteam.com (calumet.infoteam.com [207.2.129.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA18880 for ; Sun, 29 Nov 1998 10:05:39 -0800 (PST) (envelope-from kmartin@calumet.infoteam.com) Received: (from kmartin@localhost) by calumet.infoteam.com (8.8.8/8.8.8) id NAA01741; Sun, 29 Nov 1998 13:05:19 -0500 (EST) Message-Id: <199811291805.NAA01741@calumet.infoteam.com> From: "Kenn Martin" To: "Mike Smith" Cc: "FreeBSD Stable List" Date: Sun, 29 Nov 1998 13:06:26 -0500 Reply-To: "Kenn Martin" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows 98 (4.10.1998) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: NFS_SMALLFH Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 26 Nov 1998 07:42:56 -0800, Mike Smith wrote: >Please do; the issue is that if an NFS file handle larger than >NFS_SMALLFH is returned there is alternative code which needs to manage >the handle. If you can try reducing NFS_SMALLFH to 56 in >sys/nfs/nfsproto.h and do some NFS testing against a server in v3 mode, >that would be appreciated. I was going to suggest something smaller, but noticed a change to 52 to has already been checked in. What determines that structures greater than 256 bytes constitutes bloat? Is this specific to NFS? kenn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 29 14:19:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09264 for freebsd-stable-outgoing; Sun, 29 Nov 1998 14:19:10 -0800 (PST) (envelope-from owner-freebsd-stable@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 OAA09259 for ; Sun, 29 Nov 1998 14:19:04 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id JAA04398 for ; Mon, 30 Nov 1998 09:18:43 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd004395; Sun Nov 29 22:18:36 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id JAA23727 for ; Mon, 30 Nov 1998 09:18:39 +1100 (EST) Message-Id: <199811292218.JAA23727@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: stable@FreeBSD.ORG Subject: Can't get subscribed to current list? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 30 Nov 1998 09:18:33 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't know where else to ask. I've been trying to get a local exploder subscribed to the current@freebsd list for weeks. I got the token, responded as requested, then majordomo told me the request was being forwarded to someone else for approval. That was 3 weeks ago. Nothing! I tried a followup to current-approval a week ago, still nothing. Is there some problem, or is it just overloaded list maintainer? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 29 14:29:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10278 for freebsd-stable-outgoing; Sun, 29 Nov 1998 14:29:38 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10269 for ; Sun, 29 Nov 1998 14:29:31 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id OAA07209; Sun, 29 Nov 1998 14:29:43 -0800 (PST) Message-Id: <199811292229.OAA07209@root.com> To: "Kenn Martin" cc: "Mike Smith" , "FreeBSD Stable List" Subject: Re: NFS_SMALLFH In-reply-to: Your message of "Sun, 29 Nov 1998 13:06:26 EST." <199811291805.NAA01741@calumet.infoteam.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 29 Nov 1998 14:29:43 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >What determines that structures greater than 256 bytes constitutes >bloat? Is this specific to NFS? On systems that do lots of NFS, there can easily be many thousand nfsnode structs in use. An extra 256 bytes per struct can result in megabytes of wasted memory. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 29 14:30:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA10360 for freebsd-stable-outgoing; Sun, 29 Nov 1998 14:30:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from luomat.peak.org (port-14-ts2-gnv.da.fdt.net [209.212.132.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA10353 for ; Sun, 29 Nov 1998 14:30:02 -0800 (PST) (envelope-from luomat@luomat.peak.org) Message-Id: <199811291939.OAA23369@ocalhost> Content-Type: text/plain MIME-Version: 1.0 X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff In-Reply-To: From: Timothy J Luoma Date: Sun, 29 Nov 1998 14:39:54 -0500 To: freebsd-stable@FreeBSD.ORG Subject: Re: subscribe freebsd-stable References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Author: Barrett Richardson Date: Sun, 29 Nov 1998 10:41:53 -0500 (EST) ID: > There are a good number of lists in internet land that can be > subscribed too in the manner he attempted. After such exposure > humans will frequently attempt the path of least resistance first > and read the instructions later if it doesn't work. I've never seen a mailing list that suggesting sending un/subscribe messages to the actual list address.... There has always been another address for that. TjL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 29 17:38:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29836 for freebsd-stable-outgoing; Sun, 29 Nov 1998 17:38:46 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.fm-net.com (mail.fm-net.com [209.180.227.8]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA29830 for ; Sun, 29 Nov 1998 17:38:44 -0800 (PST) (envelope-from rryttie@fm-net.com) Received: from fm-net.com [209.180.227.132] by mail.fm-net.com with ESMTP (SMTPD32-4.06) id AB71134F00D4; Sun, 29 Nov 1998 19:57:05 CDT Message-ID: <3661F784.64BEB3AC@fm-net.com> Date: Sun, 29 Nov 1998 19:40:20 -0600 From: Ryan Reply-To: Kesuki@yahoo.com Organization: none X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: trouble configuring local network... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tried everything I can think of... here are the msgs and the configs i have and think may help. > netstat -r Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 209.180.227.6 UGSc 2 0 tun0 localhost localhost UH 0 4 lo0 192.168.1 link#1 UC 0 0 209.180.227.6 209.180.227.215 UH 3 0 tun0 Nov 29 19:04:30 rryttie /kernel: ed1 rev 0 int a irq 11 on pci0:3:0 Nov 29 19:04:30 rryttie /kernel: ed1: address 00:20:78:10:c9:be, type NE2000 (16 bit) Nov 29 19:04:30 rryttie /kernel: ed0 not found at 0x280 127.0.0.1 localhost localhost.my.domain myname.my.domain 192.168.1.1 rryttie rryttie.fm-net.com # FreeBSD System 192.168.1.2 larry larry.fm-net.com # Windows '95 Laptop System hostname="rryttie.fm-net.com" # Set this! network_interfaces="lo0 ed1 tun0" # List of network interfaces (lo0 is loopback). ifconfig_lo0="inet 127.0.0.1" # default loopback device configuration. ifconfig_ed1="inet 192.168.1.1 netmask 255.255.255.0" ### Network routing options: ### defaultrouter="NO" # Set to default gateway (or NO). static_routes="" # Set to static route list (or leave empty). gateway_enable="YES" # Set to YES if this host will be a gateway. router_enable="NO" # Set to YES to enable a routing daemon. router="NO" # Name of routing daemon to use if enabled. router_flags="-q" # Flags for routing daemon. mrouted_enable="NO" # Do multicast routing (see /etc/mrouted.conf). mrouted_flags="" # Flags for multicast routing daemon. ipxgateway_enable="NO" # Set to YES to enable IPX routing. ipxrouted_enable="NO" # Set to YES to run the IPX routing daemon. ipxrouted_flags="" # Flags for IPX routing daemon. arpproxy_all="" # replaces obsolete kernel option ARP_PROXYALL. forward_sourceroute="NO" # do source routing (only if gateway_enable is set to "YES") accept_sourceroute="NO" # accept source routed packets to us natd_enable="NO" # Enable natd if firewall_enable. natd_interface="fxp0" # Public interface to use with natd if natd_enable. natd_flags="" # Additional flags for natd. Also it may be of interest that the 'windows' netstat -e which shows the activity of the ethernet device shows that the windows ethernet controller has recieved 8401 bytes sent 552 bytes. has sent and recieved 6 unicast packets has recieved and sent 108 non-unicast packets sent 108 discards claims to have 0 errors and has recieved 117 unknown protocols. I find that interesting since absolutely nothing works and yet obviously the two ethernet cards are talking with eachother. I have tried pings, traceroute ftp and anything else I have enabled to no avail. The windows machine seems to be corectly configured. If any of my configuration files are wrong or if i left any out please let me know the correct settings --- My e-mail address is Personal and Private. Thank you for using bcc in any multiple recipient messages you send to me, and respecting my privacy. > grep FTP.EXE -e Regents @(#) Copyright (c) 1983 The Regents of the Univ- ersity of California. <-- the resuts of greping this program in C:\windows To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 29 18:01:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA01440 for freebsd-stable-outgoing; Sun, 29 Nov 1998 18:01:43 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fs1.webct.com ([209.87.17.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA01413 for ; Sun, 29 Nov 1998 18:01:37 -0800 (PST) (envelope-from varju@fs1.webct.com) Received: (from varju@localhost) by fs1.webct.com (8.9.1a/8.9.1) id SAA24949; Sun, 29 Nov 1998 18:01:23 -0800 (PST) Date: Sun, 29 Nov 1998 18:01:23 -0800 (PST) From: Alex Varju To: freebsd-stable@FreeBSD.ORG Subject: Re: subscribe freebsd-stable In-Reply-To: <199811291939.OAA23369@ocalhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Nov 1998, Timothy J Luoma wrote: > I've never seen a mailing list that suggesting sending un/subscribe messages > to the actual list address.... There has always been another address for > that. Majordomo itself has an option to forward messages that appear to be administrivia to the list owner, rather than sending it out to the list. This list should consider setting that option... Alex. -- Alex Varju "...'Surfing the Internet,' if one WebCT Educational Technologies would actually do that, would be a boring affair that involved a lot of packet header decoding." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 29 18:16:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA02748 for freebsd-stable-outgoing; Sun, 29 Nov 1998 18:16:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pi.yip.org (yip.org [142.154.6.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA02741 for ; Sun, 29 Nov 1998 18:16:38 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.8.8/8.8.8) with SMTP id VAA13713; Sun, 29 Nov 1998 21:17:04 -0500 (EST) (envelope-from melange@yip.org) Date: Sun, 29 Nov 1998 21:17:02 -0500 (EST) From: Bob K To: Alex Varju cc: freebsd-stable@FreeBSD.ORG Subject: Re: subscribe freebsd-stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Majordomo itself has an option to forward messages that appear to be > administrivia to the list owner, rather than sending it out to the list. > This list should consider setting that option... I've never found it to be picky enough; any occurrance of the word 'subscribe' in the first 15 lines (I think) is enough to bounce it to the listowner. For some smaller lists, having people say 'zubzcribe' instead works, but, well, it's a pain. Possibly more of a pain than getting the occasional misdirected subscribe/unsubscribe request... melange@yip.org - For external use only. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Nov 29 22:05:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA21297 for freebsd-stable-outgoing; Sun, 29 Nov 1998 22:05:48 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from luomat.peak.org (port-77-ts1-gnv.da.fdt.net [209.212.132.236]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA21292 for ; Sun, 29 Nov 1998 22:05:43 -0800 (PST) (envelope-from luomat@luomat.peak.org) Message-Id: <199811300605.BAA16741@ocalhost> Content-Type: text/plain MIME-Version: 1.0 X-Image-URL: http://www.peak.org/~luomat/luomat@peak.org.tiff In-Reply-To: <199811292218.JAA23727@melba.bby.com.au> From: Timothy J Luoma Date: Mon, 30 Nov 1998 01:05:15 -0500 To: Gregory Bond Subject: Re: Can't get subscribed to current list? cc: stable@FreeBSD.ORG References: <199811292218.JAA23727@melba.bby.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Author: Gregory Bond Date: Mon, 30 Nov 1998 09:18:33 +1100 ID: <199811292218.JAA23727@melba.bby.com.au> > Is there some problem, or is it just overloaded list maintainer? I think there's a small bug in the majordomo setup The lists are commonly referred to as 'stable@freebsd.org' etc but when subscribing I had to use # echo 'subscribe freebsd-stable' | Mail majordomo@freebsd.org trying to subscribe to 'stable' resulted in a message saying that it had to be approved, such as: You tried to "subscribe" to a closed list "stable" at Majordomo@FreeBSD.ORG. So 'stable' and 'freebsd-stable' are 2 different lists, as far as majordomo is concerned.... apparently. Anyway, try adding 'freebsd-' before 'stable' and see if that helps TjL ps -- I also just figured out that I could send several 'auth' replies in the same message re: different lists... a minor convenience, but helpful nonetheless. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 00:30:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA02588 for freebsd-stable-outgoing; Mon, 30 Nov 1998 00:30:25 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shell2.la.best.com (shell2.la.best.com [209.24.216.141]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA02583 for ; Mon, 30 Nov 1998 00:30:24 -0800 (PST) (envelope-from nugundam@shell2.la.best.com) Received: from localhost (nugundam@localhost) by shell2.la.best.com (8.9.0/8.9.0/best.sh) with ESMTP id AAA05867 for ; Mon, 30 Nov 1998 00:30:10 -0800 (PST) Date: Mon, 30 Nov 1998 00:30:10 -0800 (PST) From: Joseph Lee cc: freebsd-stable@FreeBSD.ORG Subject: Re: subscribe freebsd-stable In-Reply-To: <199811291939.OAA23369@ocalhost> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 29 Nov 1998, Timothy J Luoma wrote: > I've never seen a mailing list that suggesting sending un/subscribe messages > to the actual list address.... There has always been another address for > that. You can do either with SmartList. Not only that, SmartList has the option to catch subscribe sent to the list and not forward it to the rest of the list. I don't know about Majordomo though. -- Joseph nugundam =best=com==/==\=IIGS=/==\=Playstation=/==\=Civic HX CVT=/==\ # Anime Expo 1998 >> www.anime-expo.org/ > # Redline Games >> www.redlinegames.com/ > # Cal-Animage Epsilon >> www.best.com/~nugundam/epsilon/ > # EX: The Online World of Anime & Manga >> www.ex.org/ / To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 02:24:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA11764 for freebsd-stable-outgoing; Mon, 30 Nov 1998 02:24:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from send1e.yahoomail.com (send1e.yahoomail.com [205.180.60.64]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id CAA11759 for ; Mon, 30 Nov 1998 02:24:55 -0800 (PST) (envelope-from thallgren@yahoo.com) Message-ID: <19981130102043.6685.rocketmail@send1e.yahoomail.com> Received: from [131.116.188.2] by send1e; Mon, 30 Nov 1998 02:20:43 PST Date: Mon, 30 Nov 1998 02:20:43 -0800 (PST) From: Tommy Hallgren Subject: calcru: negative... (XF86_3DLabs server) To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! This weekend I upgraded my system to XFree86 3.3.3. Before that I used XFree86 3.3.2 and SuSE's XFCom_3DLabs X server for my Fire GL 1000 Pro graphics card. I also made world. After reboot, the system works just fine. But if I start X, using the XF86_3DLabs X server, my system starts to spit out "calcru: negative time" messages. Loads of them. And the system get very slow and unresponsive. If I reboot and change the server to XFCom_3DLabs, everything works just fine. Maybe this is more a XFree86 bug than a FreeBSD bug, I don't know. My system configuration: P200MMX 64MB RAM Diamond Fire Gl 1000 Pro with 8MB RAM 2 IDE driver (Fireball 1280 and IBM 4.3G) 1 ATAPI/IDE CDROM (Hitachi) N2000 card (not currently in use) ... and -STABLE from this Saturday. Regards, Tommy _________________________________________________________ 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-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 03:01:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14151 for freebsd-stable-outgoing; Mon, 30 Nov 1998 03:01:36 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from piranha.eds.ch (piranha.eds.ch [194.235.48.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA14146 for ; Mon, 30 Nov 1998 03:01:33 -0800 (PST) (envelope-from roberto.nunnari@agie.ch) Received: from helium.eds.ch by piranha.eds.ch (SMI-8.6/SMI-SVR4) id MAA02854; Mon, 30 Nov 1998 12:00:12 +0100 Received: from agie.ch ([198.132.159.194]) by helium.eds.ch (Netscape Messaging Server 3.5) with ESMTP id AAA7B1 for ; Mon, 30 Nov 1998 13:02:38 -0100 Message-ID: <36627ABF.78C30571@agie.ch> Date: Mon, 30 Nov 1998 12:00:15 +0100 From: "nunnari" X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: g++ -v --> 2.7.2.1 ??? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I was a linux user for many years, but recently decided to give a try to FreeBSD. I must say that from the very first minute, I felt I was dealing with a better unix. I very much like hacking around and with the help of some kind soul I hope to end up with a nice development environment. I don't use Xwindow because my tzeng card seems to have some trouble to restore video mode when exiting Xwindow. My hardware is not one of the most modern... 1993 486DX66, 20MB RAM, Mitzumi 1x CDROM, tzeng et4000 1MB I just installed 3.0-RELEASE for C++ develop purposes. The first thing I did after installing was: g++ -v which reported version 2.7.2.1 My question is: Are there any reason to hold on 2.7.2.1 instead of upgrading to 2.8.x ? I was told that version 2.8 added much better C++ features support ( template, exception handling, rtti, etc...) Are there any downsides on 2.8.x ? Is the 2.8 version already in the ports? If not, would my upgrading to 2.8.x impact in any way with FreeBSD environnment (I mean in building a customized kernel, or building the ports) ? How about configuring csh to bring up the previous command line pressing the uparrow? I didn't try CTRL+p yet... Any help/hints will be greatly appreciated. Best regards. Roberto Nunnari WWW : http://www.freeyellow.com/members5/noonlights/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 03:21:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15779 for freebsd-stable-outgoing; Mon, 30 Nov 1998 03:21:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mimu.msdj.com (mimu.msdj.com [210.160.169.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15774 for ; Mon, 30 Nov 1998 03:21:39 -0800 (PST) (envelope-from mimu@msdj.com) Received: from localhost (localhost [127.0.0.1]) by mimu.msdj.com (8.8.8/3.4Wbeta6) with ESMTP id UAA21699 for ; Mon, 30 Nov 1998 20:21:54 +0900 (JST) To: freebsd-stable@FreeBSD.ORG Subject: Re: g++ -v --> 2.7.2.1 ??? From: Shigeki Mimura In-Reply-To: Your message of "Mon, 30 Nov 1998 12:00:15 +0100" <36627ABF.78C30571@agie.ch> References: <36627ABF.78C30571@agie.ch> X-Mailer: Mew version 1.93b38 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19981130202153M.mimu@msdj.com> Date: Mon, 30 Nov 1998 20:21:53 +0900 X-Dispatcher: imput version 980522 Lines: 14 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In Message-ID: <36627ABF.78C30571@agie.ch> "nunnari" writes : > Is the 2.8 version already in the ports? Yes. Please see ftp://ftp.freebsd.org/pub/FreeBSD/ports-current/lang/gcc-2.8.1. ##################################### ## Shigeki Mimura ## ## MSD-JAPAN Inc. ## ## E-mail:mimu@msdj.com ## ##################################### To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 03:24:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA15981 for freebsd-stable-outgoing; Mon, 30 Nov 1998 03:24:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vega.pfts.com (vega.pfts.com [193.193.196.239]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA15877 for ; Mon, 30 Nov 1998 03:21:59 -0800 (PST) (envelope-from max@vega.pfts.com) Received: from vega.pfts.com (big_brother [192.168.1.1]) by vega.pfts.com (8.9.1/8.8.8) with ESMTP id NAA02159; Mon, 30 Nov 1998 13:23:23 +0200 (EET) (envelope-from max@vega.pfts.com) Message-ID: <36627EE0.8A370ADC@vega.pfts.com> Date: Mon, 30 Nov 1998 13:17:53 +0200 From: Maxim Sobolev X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: nunnari CC: freebsd-stable@FreeBSD.ORG Subject: Re: g++ -v --> 2.7.2.1 ??? References: <36627ABF.78C30571@agie.ch> Content-Type: text/plain; charset=x-user-defined Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi nunnari, I'm don't know exactly why default compiler is in version 2.7.2.1 but if you want you can go to /usr/ports/lang/gcc28 (of course if you have ports installed) and install 2.8 by yourself. Maxim nunnari wrote: > Hi there, > > I was a linux user for many years, but recently decided to give a try to > > FreeBSD. I must say that from the very first minute, I felt I was > dealing > with a better unix. I very much like hacking around and with the help > of some kind soul I hope to end up  with a nice development environment. > > I don't use Xwindow because my tzeng card seems to have some trouble > to restore video mode when exiting Xwindow. > > My hardware is not one of the most modern... 1993 > 486DX66, 20MB RAM, Mitzumi 1x CDROM, tzeng et4000 1MB > > I just installed 3.0-RELEASE for C++ develop purposes. > The first thing I did after installing was: >   g++ -v > which reported version 2.7.2.1 > > My question is: > Are there any reason to hold on 2.7.2.1 instead of upgrading to 2.8.x ? > I was told that version 2.8 added much better C++ features support ( > template, > exception handling, rtti, etc...) > Are there any downsides on 2.8.x ? > Is the 2.8 version already in the ports? > If not, would my upgrading to 2.8.x impact in any way with FreeBSD > environnment (I mean in building a customized kernel, or building the > ports) ? > > How about configuring csh to bring up the previous command line > pressing the uparrow? I didn't try CTRL+p yet... > > Any help/hints will be greatly appreciated. > > Best regards. > > Roberto Nunnari > WWW : http://www.freeyellow.com/members5/noonlights/ > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 04:37:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA22703 for freebsd-stable-outgoing; Mon, 30 Nov 1998 04:37:50 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ctcdist.com. ([199.3.192.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA22698 for ; Mon, 30 Nov 1998 04:37:48 -0800 (PST) (envelope-from placej@ctcdist.com) Received: (from placej@localhost) by ctcdist.com. (8.8.8/8.8.7) id HAA05837; Mon, 30 Nov 1998 07:36:24 -0500 (EST) (envelope-from placej) Message-ID: <19981130073623.A5783@ctcdist.com> Date: Mon, 30 Nov 1998 07:36:23 -0500 From: "John C. Place" To: nunnari Cc: freebsd-stable@FreeBSD.ORG Subject: Re: g++ -v --> 2.7.2.1 ??? Reply-To: "John C. Place" Mail-Followup-To: nunnari , freebsd-stable@freebsd.org References: <36627ABF.78C30571@agie.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <36627ABF.78C30571@agie.ch>; from nunnari on Mon, Nov 30, 1998 at 12:00:15PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 30, 1998 at 12:00:15PM +0100, nunnari wrote: > How about configuring csh to bring up the previous command line > pressing the uparrow? I didn't try CTRL+p yet... > csh historically uses the !! convention to repeat command lines, ether run bash or ksh (My favorite). Usually the second thing I do is install pdksh from the ports collection when setting up a new FreeBSD machine. > Any help/hints will be greatly appreciated. > Read Read Read :-) and get ready for a learning experience. You have in your hands one of the more stable OSs around but it comes with a price, you will have to get your hands dirty on a few config_files and such. Also a _great_ book is "The Complete FreeBSD" by Greg Lehey. It is worth its weight in gold. I am running stable not current (3.0) but It should still be of help. Good Luck in your Quest John C. Place To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 05:22:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25053 for freebsd-stable-outgoing; Mon, 30 Nov 1998 05:22:52 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kendra.ne.mediaone.net (kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA25048 for ; Mon, 30 Nov 1998 05:22:50 -0800 (PST) (envelope-from software@kew.com) Received: from sonata.hh.kew.com (root@sonata-dmz.hh.kew.com [192.168.205.1]) by kendra.ne.mediaone.net (8.9.1/8.9.1) with ESMTP id IAA02174 for ; Mon, 30 Nov 1998 08:22:37 -0500 (EST) Received: from kew.com (minerva.hh.kew.com [192.168.203.144]) by sonata.hh.kew.com (8.9.1/8.9.1) with ESMTP id IAA02661 for ; Mon, 30 Nov 1998 08:22:36 -0500 (EST) Message-ID: <36629C1B.2AD8BB30@kew.com> Date: Mon, 30 Nov 1998 08:22:35 -0500 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks, Stoneham, MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: minor errors in the 11/28 SNAP Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Using the latest SNAP available for stable as of yesterday morning... 1) In sysinstall, if performing an upgrade, the install can't find UPGRADE.TXT on the boot floppy to give you the standard dire warnings. This has the side effect of making once feel the entire upgrade just failed. (It didn't, but made me chicken out the first time). 2) There is a message to the effect of 'there is ... shell already running von ttyv4, shall I kill it and start a new one'? "von" should be "on" 3) The message reporting that a signal was caught and install will terminate omits the word 'down' after the word 'shutting'. [Happy to cut PR's if you want 'em.] -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9812 "While the ANSI X3J11 committee puts the beginning of all time at 1 January 1970, we now know through extensive research that time actually started much earlier than this ..." - Tools.h++ V5.1 Class Reference To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 05:24:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA25280 for freebsd-stable-outgoing; Mon, 30 Nov 1998 05:24:00 -0800 (PST) (envelope-from owner-freebsd-stable@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 FAA25259 for ; Mon, 30 Nov 1998 05:23:57 -0800 (PST) (envelope-from matt@megaweapon.zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.8.8/8.8.8) with ESMTP id IAA14803; Mon, 30 Nov 1998 08:23:10 -0500 (EST) (envelope-from matt@megaweapon.zigg.com) Date: Mon, 30 Nov 1998 08:23:09 -0500 (EST) From: Matt Behrens To: "John C. Place" cc: nunnari , freebsd-stable@FreeBSD.ORG Subject: tcsh (was Re: g++ -v --> 2.7.2.1 ???) In-Reply-To: <19981130073623.A5783@ctcdist.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG tcsh is in the ports for the hopeless csh devotees though. :) (I have one on my system...) # cd /usr/ports/shells/tcsh;make install 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. . . . . . . . . . . On Mon, 30 Nov 1998, John C. Place wrote: > On Mon, Nov 30, 1998 at 12:00:15PM +0100, nunnari wrote: > > How about configuring csh to bring up the previous command line > > pressing the uparrow? I didn't try CTRL+p yet... > csh historically uses the !! convention to repeat command lines, ether run > bash or ksh (My favorite). Usually the second thing I do is install pdksh > from the ports collection when setting up a new FreeBSD machine. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 05:41:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27104 for freebsd-stable-outgoing; Mon, 30 Nov 1998 05:41:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from piranha.eds.ch ([194.235.48.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA27098 for ; Mon, 30 Nov 1998 05:41:28 -0800 (PST) (envelope-from roberto.nunnari@agie.ch) Received: from helium.eds.ch by piranha.eds.ch (SMI-8.6/SMI-SVR4) id OAA04070; Mon, 30 Nov 1998 14:40:07 +0100 Received: from agie.ch ([198.132.159.194]) by helium.eds.ch (Netscape Messaging Server 3.5) with ESMTP id AAA11F9 for ; Mon, 30 Nov 1998 15:42:31 -0100 Message-ID: <3662A039.227E53CB@agie.ch> Date: Mon, 30 Nov 1998 14:40:10 +0100 From: "nunnari" X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: stable Subject: packages vs ports ?? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to all who answered my previous post on g++ After reading a bit of doc, I'm still not sure I understand what the difference between ports and packages is. May it be that packages are executables while ports are still to be built? Also which is the best forum for questions? I don't mean to annoy anybody by posting here... Best regards. Roberto Nunnari WWW : http://www.freeyellow.com/members5/noonlights/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 05:47:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27724 for freebsd-stable-outgoing; Mon, 30 Nov 1998 05:47:53 -0800 (PST) (envelope-from owner-freebsd-stable@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 FAA27718 for ; Mon, 30 Nov 1998 05:47:50 -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 IAA14855; Mon, 30 Nov 1998 08:47:02 -0500 (EST) (envelope-from matt@zigg.com) Date: Mon, 30 Nov 1998 08:47:01 -0500 (EST) From: Matt Behrens To: nunnari cc: stable Subject: Re: packages vs ports ?? In-Reply-To: <3662A039.227E53CB@agie.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The best forum is . A package is a precompiled binary package, usually downloaded from ftp.freebsd.org though of course anyone is free to create packages. They are found (if I recall correctly) at . Their major downside is that oft-times they are compiled requiring X or (when there was a problem recently, this was corrected) Kerberos, for example; or they just may not be optimized for your configuration. They do save time, though, and are added with the pkg_add command (it even takes a URL as a parameter if you want to fetch and install all in one step!) The ports, I think, are more popular -- they can download (from the original package site or with a fallback on ftp.freebsd.org), configure, compile, and install all in one step; and you can interrupt the process to make source changes or what not. There is more information on those in the FreeBSD Handbook at , but usually you just do cd /usr/ports/category/name;make install. :) On Mon, 30 Nov 1998, nunnari wrote: :Thanks to all who answered my previous post on g++ : :After reading a bit of doc, I'm still not sure I understand what :the difference between ports and packages is. : :May it be that packages are executables while ports are still :to be built? : :Also which is the best forum for questions? I don't mean to :annoy anybody by posting here... : :Best regards. : :Roberto Nunnari :WWW : http://www.freeyellow.com/members5/noonlights/ : : : :To Unsubscribe: send mail to majordomo@FreeBSD.org :with "unsubscribe freebsd-stable" in the body of the message : 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-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 06:21:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01157 for freebsd-stable-outgoing; Mon, 30 Nov 1998 06:21:12 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cs.Technion.AC.IL (csa.cs.technion.ac.il [132.68.32.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01141 for ; Mon, 30 Nov 1998 06:20:57 -0800 (PST) (envelope-from nadav@csa.cs.technion.ac.il) Received: from csd.csa (csd [132.68.32.8]) by cs.Technion.AC.IL (8.9.0/8.9.0) with SMTP id PAA16145; Mon, 30 Nov 1998 15:48:30 +0200 (IST) Received: from localhost by csd.csa (SMI-8.6/SMI-SVR4) id PAA23935; Mon, 30 Nov 1998 15:48:26 +0200 Date: Mon, 30 Nov 1998 15:48:26 +0200 (IST) From: Nadav Eiron X-Sender: nadav@csd To: nunnari cc: stable Subject: Re: packages vs ports ?? In-Reply-To: <3662A039.227E53CB@agie.ch> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Nov 1998, nunnari wrote: > Thanks to all who answered my previous post on g++ > > After reading a bit of doc, I'm still not sure I understand what > the difference between ports and packages is. > > May it be that packages are executables while ports are still > to be built? Correct. > > Also which is the best forum for questions? I don't mean to > annoy anybody by posting here... questions@freebsd.org You should also go through the Handbook/FAQ/mailing list archives before posting to questions. Most of these questions have been answered before, and these answers are in the archives of the questions mailing list. See: http://www.freebsd.org/search.html > > Best regards. > > Roberto Nunnari > WWW : http://www.freeyellow.com/members5/noonlights/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 06:35:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03096 for freebsd-stable-outgoing; Mon, 30 Nov 1998 06:35:52 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from bamboo.ints.ml.org (intschool.easynet.co.uk [194.72.37.214]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA03091 for ; Mon, 30 Nov 1998 06:35:49 -0800 (PST) (envelope-from stuart@ints.ml.org) Received: (from stuart@localhost) by bamboo.ints.ml.org (8.8.8/8.8.8) id OAA17255; Mon, 30 Nov 1998 14:36:17 GMT (envelope-from stuart) Message-ID: <19981130143617.A17085@helan.org> Date: Mon, 30 Nov 1998 14:36:17 +0000 From: Stuart Henderson To: Nadav Eiron , nunnari Cc: stable Subject: Re: packages vs ports ?? References: <3662A039.227E53CB@agie.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Nadav Eiron on Mon, Nov 30, 1998 at 03:48:26PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Nov 30, 1998 at 03:48:26PM +0200, Nadav Eiron wrote: > > On Mon, 30 Nov 1998, nunnari wrote: > > > May it be that packages are executables while ports are still > > to be built? > > Correct. Nearly, but see (for example) Netscape or Acrobat Reader. They're ports but they provide binaries. Packages often don't have the full documentation, for that reason ports are usually preferable. Packages however are usually much faster to install as they don't involve compilation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 07:55:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA10349 for freebsd-stable-outgoing; Mon, 30 Nov 1998 07:55:13 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mishler-pc.edwards.af.mil (ws144-30.edwards.af.mil [129.198.30.144]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA10344 for ; Mon, 30 Nov 1998 07:55:10 -0800 (PST) (envelope-from Barry.Mishler@edwards.af.mil) Received: from edwards.af.mil (localhost [127.0.0.1]) by mishler-pc.edwards.af.mil (8.8.7/8.8.7) with ESMTP id HAA00396; Mon, 30 Nov 1998 07:52:50 -0800 (PST) (envelope-from Barry.Mishler@edwards.af.mil) Message-ID: <3662BF51.A43FE5A9@edwards.af.mil> Date: Mon, 30 Nov 1998 07:52:49 -0800 From: Barry Mishler X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) MIME-Version: 1.0 To: nunnari CC: freebsd-stable@FreeBSD.ORG Subject: Re: g++ -v --> 2.7.2.1 ??? References: <36627ABF.78C30571@agie.ch> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nunnari wrote: > How about configuring csh to bring up the previous command line > pressing the uparrow? I didn't try CTRL+p yet... Install tcsh from ports/shells if you're used to csh. It probably includes most of the command line editing that you want. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 09:49:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19663 for freebsd-stable-outgoing; Mon, 30 Nov 1998 09:49:00 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from piranha.eds.ch (piranha.eds.ch [194.235.48.10]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA19654 for ; Mon, 30 Nov 1998 09:48:57 -0800 (PST) (envelope-from roberto.nunnari@agie.ch) Received: from helium.eds.ch by piranha.eds.ch (SMI-8.6/SMI-SVR4) id SAA06240; Mon, 30 Nov 1998 18:47:38 +0100 Received: from agie.ch ([198.132.159.194]) by helium.eds.ch (Netscape Messaging Server 3.5) with ESMTP id AAA1F47 for ; Mon, 30 Nov 1998 19:50:03 -0100 Message-ID: <3662DA3D.4119AA14@agie.ch> Date: Mon, 30 Nov 1998 18:47:42 +0100 From: "nunnari" X-Mailer: Mozilla 4.04 [en] (OS/2; I) MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: g++ -v --> 2.7.2.1 ??? References: <36627ABF.78C30571@agie.ch> <36627EE0.8A370ADC@vega.pfts.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to all for the useful answers. I'll play a bit this evenings.. ;-) bye. Roberto WWW : http://www.freeyellow.com/members5/noonlights/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 11:05:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29276 for freebsd-stable-outgoing; Mon, 30 Nov 1998 11:05:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from docws002.shl.com (docws002.shl.com [159.249.56.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29249 for ; Mon, 30 Nov 1998 11:05:00 -0800 (PST) (envelope-from swalczak@shl.com) Received: from ottmsooc01.ott.shl.com (ottmsooc01.ooc.shl.com [159.249.112.24]) by docws002.shl.com (8.9.1/8.9.1) with ESMTP id MAA18068 for ; Mon, 30 Nov 1998 12:13:19 -0700 (MST) Message-Id: <199811301913.MAA18068@docws002.shl.com> Received: by ottmsooc01.ooc.shl.com with Internet Mail Service (5.5.2232.9) id ; Mon, 30 Nov 1998 14:03:31 -0500 From: "WALCZAK, Stan" To: "'freebsd-stable@FreeBSD.ORG'" Subject: output of ping command looks mysterious Date: Mon, 30 Nov 1998 14:04:57 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Our network environment: Dell model Dimension XPS D333 pentium-II 333Mhz 4.5 GIG IBM ultra wide SCSI HD, ADAPTEC 2940UW controller, BIOS Phenix 4.0 release 6.0, 3-COM 905 TX network card, 8 MB Video Card AGP 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0 this machines runs Apache Server 1.3, Qmail and Radius 2.3 Pipline 75 - original bios from 1996 Portmaster 2e - ComOS 3.7.2 Output of the ping command looks like: 64 bytes from 142.77.1.1: icmp_seq=20 ttl=250 time=79.736 ms 64 bytes from 142.77.1.1: icmp_seq=21 ttl=250 time=49.781 ms 64 bytes from 142.77.1.1: icmp_seq=22 ttl=250 time=993.792 ms 64 bytes from 142.77.1.1: icmp_seq=23 ttl=250 time=795.402 ms 64 bytes from 142.77.1.1: icmp_seq=24 ttl=250 time=338.294 ms 64 bytes from 142.77.1.1: icmp_seq=25 ttl=250 time=94.049 ms 64 bytes from 142.77.1.1: icmp_seq=26 ttl=250 time=275.623 ms 64 bytes from 142.77.1.1: icmp_seq=27 ttl=250 time=359.182 ms 64 bytes from 142.77.1.1: icmp_seq=29 ttl=250 time=412.320 ms 64 bytes from 142.77.1.1: icmp_seq=30 ttl=250 time=223.237 ms 64 bytes from 142.77.1.1: icmp_seq=31 ttl=250 time=127.166 ms 64 bytes from 142.77.1.1: icmp_seq=32 ttl=250 time=687.519 ms 64 bytes from 142.77.1.1: icmp_seq=34 ttl=250 time=578.269 ms 64 bytes from 142.77.1.1: icmp_seq=35 ttl=250 time=149.857 ms 64 bytes from 142.77.1.1: icmp_seq=36 ttl=250 time=372.875 ms 64 bytes from 142.77.1.1: icmp_seq=37 ttl=250 time=133.176 ms 64 bytes from 142.77.1.1: icmp_seq=31 ttl=250 time=127.166 ms 64 bytes from 142.77.1.1: icmp_seq=32 ttl=250 time=687.519 ms 64 bytes from 142.77.1.1: icmp_seq=34 ttl=250 time=578.269 ms 64 bytes from 142.77.1.1: icmp_seq=35 ttl=250 time=149.857 ms 64 bytes from 142.77.1.1: icmp_seq=36 ttl=250 time=372.875 ms 64 bytes from 142.77.1.1: icmp_seq=37 ttl=250 time=133.176 ms 64 bytes from 142.77.1.1: icmp_seq=38 ttl=250 time=216.877 ms 64 bytes from 142.77.1.1: icmp_seq=39 ttl=250 time=504.699 ms 64 bytes from 142.77.1.1: icmp_seq=40 ttl=250 time=709.457 ms 64 bytes from 142.77.1.1: icmp_seq=41 ttl=250 time=532.827 ms 64 bytes from 142.77.1.1: icmp_seq=42 ttl=250 time=261.998 ms 64 bytes from 142.77.1.1: icmp_seq=43 ttl=250 time=186.549 ms --- ns.uunet.ca ping statistics --- 44 packets transmitted, 42 packets received, 4% packet loss round-trip min/avg/max/stddev = 46.531/249.858/993.792/242.634 ms For me it's looks suspicious. Any suggestions why there are jumps up to 993.792 ms ? The other issue (maybe related) is memory avaialbe, here is output from vmstat -m command: # vmstat -m Memory statistics by bucket size Size In Use Free Requests HighWater Couldfree 16 40 728 838 1280 0 32 92 36 4616 640 0 64 1612 52 38517 320 0 128 1814 170 71659 160 47 256 958 50 104696 80 0 512 47 17 3791 40 0 1K 28 48 195389 20 24323 2K 13 11 111 10 19 4K 7 3 234 5 0 8K 0 1 2 5 0 16K 3 0 3 5 0 Memory usage type by bucket size Size Type(s) 16 devbuf, pcb, routetbl, vnodes, proc, temp 32 devbuf, pcb, routetbl, pgrp, session, proc, subproc, temp 64 devbuf, routetbl, ifaddr, namecache, VM mapent, VM pgdata, file, lockf, in_multi, temp 128 pcb, routetbl, zombie, ifaddr, cred, vnodes, VM map, VM object, VM pgdata, file desc, proc, temp, ttys 256 devbuf, socket, pcb, routetbl, ioctlops, vnodes, VM map, VM pgdata, file desc, subproc, FFS node, NFS srvsock, NFS daemon, temp, isa_devlist, select 512 devbuf, pcb, ioctlops, mount, UFS mount, proc, temp, isa_devlist, BIO buffer 1K mbuf, devbuf, namei, UFS mount, NQNFS Lease, MSDOSFS mount, temp, BIO buffer 2K devbuf, ioctlops, NFS node, UFS quota, UFS mount, ttys, BIO buffer 4K devbuf, ioctlops, namecache, temp 8K VM pgdata, temp 16K devbuf Memory statistics by type Type Kern Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) mbuf 1 1K 1K 7942K 1 0 0 1K devbuf 45 85K 85K 7942K 91 0 0 16,32,64,256,512,1K,2K,4K,16K socket 18 5K 6K 7942K 134 0 0 256 pcb 29 6K 7K 7942K 136 0 0 16,32,128,256,512 routetbl 25 3K 4K 7942K 53 0 0 16,32,64,128,256 zombie 0 0K 1K 7942K 3653 0 0 128 ifaddr 9 2K 2K 7942K 9 0 0 64,128 namei 0 0K 4K 7942K 188245 0 0 1K ioctlops 0 0K 4K 7942K 9 0 0 256,512,2K,4K cred 13 2K 3K 7942K 695 0 0 128 pgrp 16 1K 1K 7942K 494 0 0 32 session 14 1K 1K 7942K 354 0 0 32 mount 5 3K 3K 7942K 5 0 0 512 NFS node 1 2K 2K 7942K 1 0 0 2K vnodes 878 109K 118K 7942K 1669 0 0 16,128,256 namecache 842 57K 57K 7942K 842 0 0 64,4K UFS quota 1 2K 2K 7942K 1 0 0 2K UFS mount 13 17K 17K 7942K 13 0 0 512,1K,2K VM map 33 8K 12K 7942K 3686 0 0 128,256 VM mapent 614 39K 39K 7942K 614 0 0 64 VM object 613 77K 98K 7942K 61699 0 0 128 VM pgdata 139 16K 16K 7942K 149 0 0 64,128,256,8K file 56 4K 5K 7942K 36901 0 0 64 file desc 31 5K 7K 7942K 3684 0 0 128,256 lockf 6 1K 1K 7942K 54 0 0 64 proc 34 14K 21K 7942K 3693 0 0 16,32,128,512 subproc 33 3K 4K 7942K 7339 0 0 32,256 FFS node 820 205K 210K 7942K 94530 0 0 256 NQNFS Lease 1 1K 1K 7942K 1 0 0 1K NFS srvsock 2 1K 1K 7942K 2 0 0 256 NFS daemon 1 1K 1K 7942K 1 0 0 256 in_multi 2 1K 1K 7942K 2 0 0 64 MSDOSFS mount 1 1K 1K 7942K 1 0 0 1K temp 40 5K 19K 7942K 2871 0 0 16,32,64,128,256,512,1K,4K,8K ttys 246 33K 38K 7942K 909 0 0 128,2K isa_devlist 1 1K 1K 7942K 2 0 0 256,512 BIO buffer 22 23K 68K 7942K 7278 0 0 512,1K,2K select 9 3K 3K 7942K 35 0 0 256 Memory Totals: In Use Free Requests 724K 148K 419856 Any ideas ? Thanks in advance ! s.w. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 11:06:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA29514 for freebsd-stable-outgoing; Mon, 30 Nov 1998 11:06:43 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from calis.BlackSun.org (slip-ppp-4-191.escape.com [205.160.46.191]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA29506 for ; Mon, 30 Nov 1998 11:06:40 -0800 (PST) (envelope-from don@calis.BlackSun.org) Received: from localhost (don@localhost) by calis.BlackSun.org (8.9.1/8.9.1) with ESMTP id OAA01108; Mon, 30 Nov 1998 14:04:17 -0500 (EST) (envelope-from don@calis.BlackSun.org) Date: Mon, 30 Nov 1998 14:04:17 -0500 (EST) From: Don To: Matt Behrens cc: "John C. Place" , nunnari , freebsd-stable@FreeBSD.ORG Subject: Re: tcsh (was Re: g++ -v --> 2.7.2.1 ???) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > tcsh is in the ports for the hopeless csh devotees though. :) (I have one > on my system...) Hopeless? Some of us like a real shell thank you :) -Don To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 11:46:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04802 for freebsd-stable-outgoing; Mon, 30 Nov 1998 11:46:43 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA04792 for ; Mon, 30 Nov 1998 11:46:39 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zkZH3-00012e-00; Mon, 30 Nov 1998 11:46:21 -0800 Date: Mon, 30 Nov 1998 11:46:19 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "WALCZAK, Stan" cc: "'freebsd-stable@FreeBSD.ORG'" Subject: Re: output of ping command looks mysterious In-Reply-To: <199811301913.MAA18068@docws002.shl.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Nov 1998, WALCZAK, Stan wrote: > Our network environment: > Dell model Dimension XPS D333 pentium-II 333Mhz 4.5 GIG IBM ultra wide SCSI > HD, ADAPTEC 2940UW controller, BIOS Phenix 4.0 release 6.0, 3-COM 905 TX > network card, 8 MB Video Card AGP 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0 > this machines runs Apache Server 1.3, Qmail and Radius 2.3 > Pipline 75 - original bios from 1996 You should upgrade it. It probably has known bugs. I'm assuming that this is your primary Internet connection > Portmaster 2e - ComOS 3.7.2 > Output of the ping command looks like: > 64 bytes from 142.77.1.1: icmp_seq=20 ttl=250 time=79.736 ms > 64 bytes from 142.77.1.1: icmp_seq=21 ttl=250 time=49.781 ms > 64 bytes from 142.77.1.1: icmp_seq=22 ttl=250 time=993.792 ms > 64 bytes from 142.77.1.1: icmp_seq=23 ttl=250 time=795.402 ms > 64 bytes from 142.77.1.1: icmp_seq=24 ttl=250 time=338.294 ms > 64 bytes from 142.77.1.1: icmp_seq=25 ttl=250 time=94.049 ms > 64 bytes from 142.77.1.1: icmp_seq=26 ttl=250 time=275.623 ms > 64 bytes from 142.77.1.1: icmp_seq=27 ttl=250 time=359.182 ms > 64 bytes from 142.77.1.1: icmp_seq=29 ttl=250 time=412.320 ms > 64 bytes from 142.77.1.1: icmp_seq=30 ttl=250 time=223.237 ms > 64 bytes from 142.77.1.1: icmp_seq=31 ttl=250 time=127.166 ms > 64 bytes from 142.77.1.1: icmp_seq=32 ttl=250 time=687.519 ms > 64 bytes from 142.77.1.1: icmp_seq=34 ttl=250 time=578.269 ms > 64 bytes from 142.77.1.1: icmp_seq=35 ttl=250 time=149.857 ms > 64 bytes from 142.77.1.1: icmp_seq=36 ttl=250 time=372.875 ms > 64 bytes from 142.77.1.1: icmp_seq=37 ttl=250 time=133.176 ms > 64 bytes from 142.77.1.1: icmp_seq=31 ttl=250 time=127.166 ms > 64 bytes from 142.77.1.1: icmp_seq=32 ttl=250 time=687.519 ms > 64 bytes from 142.77.1.1: icmp_seq=34 ttl=250 time=578.269 ms > 64 bytes from 142.77.1.1: icmp_seq=35 ttl=250 time=149.857 ms > 64 bytes from 142.77.1.1: icmp_seq=36 ttl=250 time=372.875 ms > 64 bytes from 142.77.1.1: icmp_seq=37 ttl=250 time=133.176 ms > 64 bytes from 142.77.1.1: icmp_seq=38 ttl=250 time=216.877 ms > 64 bytes from 142.77.1.1: icmp_seq=39 ttl=250 time=504.699 ms > 64 bytes from 142.77.1.1: icmp_seq=40 ttl=250 time=709.457 ms > 64 bytes from 142.77.1.1: icmp_seq=41 ttl=250 time=532.827 ms > 64 bytes from 142.77.1.1: icmp_seq=42 ttl=250 time=261.998 ms > 64 bytes from 142.77.1.1: icmp_seq=43 ttl=250 time=186.549 ms > --- ns.uunet.ca ping statistics --- > 44 packets transmitted, 42 packets received, 4% packet loss > round-trip min/avg/max/stddev = 46.531/249.858/993.792/242.634 ms > > For me it's looks suspicious. Any suggestions why there are jumps up to > 993.792 ms ? Too much traffic? As traffic spikes hit your ISDN link, latency will jump. > The other issue (maybe related) is memory avaialbe, here is output from > vmstat -m command: You are probably misinterpreting these results. Many of these are kernel objects, stored in kernel memory. You probably care about user memory. You don't seem to mention how much total RAM is in your system, but check "swapinfo" to make sure that you aren't using too much swap. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 11:48:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05009 for freebsd-stable-outgoing; Mon, 30 Nov 1998 11:48:23 -0800 (PST) (envelope-from owner-freebsd-stable@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 LAA04988 for ; Mon, 30 Nov 1998 11:48:14 -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 AA292064981; Mon, 30 Nov 1998 14:43:01 -0500 Date: Mon, 30 Nov 1998 14:43:01 -0500 (EST) From: Bill Fumerola To: nunnari Cc: stable Subject: Re: packages vs ports ?? In-Reply-To: <3662A039.227E53CB@agie.ch> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Nov 1998, nunnari wrote: > After reading a bit of doc, I'm still not sure I understand what > the difference between ports and packages is. > > May it be that packages are executables while ports are still > to be built? Yes. Packages are just ports that have been pre-built and placed in a central place. Ports contain the Makefile and patches required to build the package or port. Some ports can't be made into packages (copyright, commercial, crypto, etc) and a lot of people just feel better building their own binaries for optimization reasons, etc, etc.. > Also which is the best forum for questions? I don't mean to > annoy anybody by posting here... freebsd-ports@FreeBSD.org - 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-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 12:09:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08472 for freebsd-stable-outgoing; Mon, 30 Nov 1998 12:09:39 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from xylan.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA08465 for ; Mon, 30 Nov 1998 12:09:36 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com by xylan.com (8.8.7/SMI-SVR4 (xylan-mgw 2.2 [OUT])) id MAA01225; Mon, 30 Nov 1998 12:09:23 -0800 (PST) Received: from utah.XYLAN.COM by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id MAA11719; Mon, 30 Nov 1998 12:09:28 -0800 Received: from softweyr.com by utah.XYLAN.COM (SMI-8.6/SMI-SVR4 (xylan utah [SPOOL])) id NAA01702; Mon, 30 Nov 1998 13:09:22 -0700 Message-ID: <3662FB72.F5E9C14@softweyr.com> Date: Mon, 30 Nov 1998 13:09:22 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.7-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Kesuki@yahoo.com CC: freebsd-stable@FreeBSD.ORG Subject: Re: trouble configuring local network... References: <3661F784.64BEB3AC@fm-net.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ryan wrote: > > I've tried everything I can think of... here are the msgs and the configs > i have and think may help. > > > netstat -r > Routing tables > > Internet: > Destination Gateway Flags Refs Use Netif > default 209.180.227.6 UGSc 2 0 tun0 > localhost localhost UH 0 4 lo0 > 192.168.1 link#1 UC 0 0 > 209.180.227.6 209.180.227.215 UH 3 0 tun0 You are aware that you cannot route a private, i.e. 192.168.xx.xx, IP network to the internet? You will need to enable Netword Address Translation on your router box. Since you are using the user-mode PPP utility, you can have PPP do this for you; read the ppp(8) man page. You didn't include your PPP configuration, so I can't tell if you're already doing this or not. -- Where am I, and what am I doing in this handbasket? Wes Peters +1.801.915.2061 Softweyr LLC wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 12:10:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA08704 for freebsd-stable-outgoing; Mon, 30 Nov 1998 12:10:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from fig.mail.easynet.net (fig.mail.easynet.net [195.40.1.46]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA08688 for ; Mon, 30 Nov 1998 12:10:21 -0800 (PST) (envelope-from andrew@sour.cream.org) Received: (qmail 27754 invoked from network); 30 Nov 1998 20:10:08 -0000 Received: from boothman.easynet.co.uk (HELO localhost) (194.154.100.117) by fig.mail.easynet.net with SMTP; 30 Nov 1998 20:10:08 -0000 Received: from sour.cream.org (localhost [127.0.0.1]) by localhost (8.8.8/8.8.8) with ESMTP id UAA00861 for ; Mon, 30 Nov 1998 20:04:48 GMT (envelope-from andrew@sour.cream.org) Message-ID: <3662FA5F.C0F5B191@sour.cream.org> Date: Mon, 30 Nov 1998 20:04:47 +0000 From: Andrew Boothman X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: FreeBSD Stable List Subject: New CTM Users - Documentation Content-Type: multipart/mixed; boundary="------------521EAD02E6DCD626298DC125" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. --------------521EAD02E6DCD626298DC125 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! After a discussion some time ago about how new users should update their source tree to allow them to sucessfully apply new CTM deltas, my understanding of the situation is that the following is now the best way. I'll send this to doc@freebsd.org if no-one sees any problems. Thanks -- Andrew Boothman http://sour.cream.org/ http://www.boothman.easynet.co.uk/andrew/ --------------521EAD02E6DCD626298DC125 Content-Type: text/plain; charset=us-ascii; name="mychanges" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="mychanges" ## This is a complete replacement for the 18.3.2.3 part of the handbook ## Items in <>'s need a link to another handbook page ## "Starting off with CTM for the first time" ## by Andrew Boothman Before you can start using CTM deltas, you will need to get to a suitable starting point so that you can apply the deltas that came after it. First you should determine what you already have.Everyone can start from an "Empty" directory. However, since the trees are many tens of megabytes, you should try to start from something already at hand. If you have a RELEASE CD, you can copy or extract an inital source from it. This will save you from transfering a significant amount of data. To bring your source tree in line with the one that the CTM deltas are being generated from you should use the CVSup tool. A special CVSup server is available to those who want to stay up-to-date using CTM, it is called "ctm.FreeBSD.org". You should see the example supfiles in /usr/share/examples/cvsup and alter them to meet your requirements. If you are starting from scratch with no RELEASE CD or are unable or unwilling to use the CVSup tool to bring yourself in-line with the deltas currently being produced, then you should download an empty transition delta. These empty transition deltas are not 'empty'. Far from it. They contain the entire source tree as it stood when they were produced, and are intended for people who are starting from an 'empty' directory. You can recognise these empty transition deltas from the XEmpty appended to the delta number (e.g src-cur.3210XEmpty.gz). These 'empty' deltas are produced every 100 deltas or so and are very large! 25 to 30 Megabytes is the typical size for the "XEmpty" deltas. If you decide to use an 'empty' transition delta then you must also download all the deltas that came after it, to bring you up-to-date with the deltas currently being produced. However, if you used CVSup to bring yourself in-line then you are already up-to-date and must simply start to apply new CTM deltas as they are produced. --------------521EAD02E6DCD626298DC125-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 12:28:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11116 for freebsd-stable-outgoing; Mon, 30 Nov 1998 12:28:47 -0800 (PST) (envelope-from owner-freebsd-stable@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 MAA11110 for ; Mon, 30 Nov 1998 12:28:40 -0800 (PST) (envelope-from mark@grondar.za) Received: from greenpeace.grondar.za (IDENT:Q3l3rWQi9jtJGTB5O9eruBrI+fhxXx7Q@greenpeace.grondar.za [196.7.18.132]) by gratis.grondar.za (8.9.1/8.9.1) with ESMTP id WAA15575; Mon, 30 Nov 1998 22:28:22 +0200 (SAST) (envelope-from mark@grondar.za) Received: from grondar.za (IDENT:P9BjteRBQdG/M8eGQcICwlHPtEmqrjOI@localhost [127.0.0.1]) by greenpeace.grondar.za (8.9.1/8.9.1) with ESMTP id WAA25265; Mon, 30 Nov 1998 22:28:21 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199811302028.WAA25265@greenpeace.grondar.za> To: Andrew Boothman cc: FreeBSD Stable List Subject: Re: New CTM Users - Documentation In-Reply-To: Your message of " Mon, 30 Nov 1998 20:04:47 GMT." <3662FA5F.C0F5B191@sour.cream.org> References: <3662FA5F.C0F5B191@sour.cream.org> Date: Mon, 30 Nov 1998 22:28:19 +0200 From: Mark Murray Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrew Boothman wrote: > After a discussion some time ago about how new users should update their > source tree to allow them to sucessfully apply new CTM deltas, my > understanding of the situation is that the following is now the best > way. > > I'll send this to doc@freebsd.org if no-one sees any problems. I'll take this from here. Gimme a week or two (bug me!) and I'll commit it. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 14:58:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28231 for freebsd-stable-outgoing; Mon, 30 Nov 1998 14:58:04 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28224 for ; Mon, 30 Nov 1998 14:58:01 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id OAA21108; Mon, 30 Nov 1998 14:58:22 -0800 (PST) Message-Id: <199811302258.OAA21108@root.com> To: "WALCZAK, Stan" cc: "'freebsd-stable@FreeBSD.ORG'" Subject: Re: output of ping command looks mysterious In-reply-to: Your message of "Mon, 30 Nov 1998 14:04:57 EST." <199811301913.MAA18068@docws002.shl.com> From: David Greenman Reply-To: dg@root.com Date: Mon, 30 Nov 1998 14:58:22 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Our network environment: >Dell model Dimension XPS D333 pentium-II 333Mhz 4.5 GIG IBM ultra wide SCSI >HD, ADAPTEC 2940UW controller, BIOS Phenix 4.0 release 6.0, 3-COM 905 TX >network card, 8 MB Video Card AGP 2.2.7-RELEASE FreeBSD 2.2.7-RELEASE #0 ... >For me it's looks suspicious. Any suggestions why there are jumps up to >993.792 ms ? It's probably telling you that the interrupt is broken, since the driver will recover from a lost interrupt in 0-.999 seconds of time. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Nov 30 23:00:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA22571 for freebsd-stable-outgoing; Mon, 30 Nov 1998 23:00:13 -0800 (PST) (envelope-from owner-freebsd-stable@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 XAA22563 for ; Mon, 30 Nov 1998 23:00:07 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id RAA18040 for ; Tue, 1 Dec 1998 17:59:53 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd018038; Tue Dec 1 06:59:44 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id RAA08818 for ; Tue, 1 Dec 1998 17:59:48 +1100 (EST) Message-Id: <199812010659.RAA08818@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: stable@FreeBSD.ORG Subject: HP NightDIRECTOR/100 Ether card Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Dec 1998 17:59:41 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG My new flash fire-breather HP Kayak XA400 (Kayak? Who'd name a computer "Kayak"??!") came with a PCI ether card identified as "HP NightDIRECTOR/100". The chip is an AMD 79C971KC, also known in the dox as "AMD PCNet-FAST". Am I right in my suspicion that this card is not supported? (2.2.x or 3.0 at this time...) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 1 05:41:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28149 for freebsd-stable-outgoing; Tue, 1 Dec 1998 05:41:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from docws002.shl.com (docws002.shl.com [159.249.56.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28141 for ; Tue, 1 Dec 1998 05:41:40 -0800 (PST) (envelope-from swalczak@shl.com) Received: from cgymscoc02.shl.com ([159.249.92.3]) by docws002.shl.com (8.9.1/8.9.1) with ESMTP id GAA25298 for ; Tue, 1 Dec 1998 06:50:11 -0700 (MST) Message-Id: <199812011350.GAA25298@docws002.shl.com> Received: by CGYMSCOC02 with Internet Mail Service (5.5.2232.9) id ; Tue, 1 Dec 1998 06:42:47 -0700 From: "WALCZAK, Stan" To: "'freebsd-stable@FreeBSD.ORG'" Subject: unsubscribe Date: Tue, 1 Dec 1998 06:41:37 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG unsubscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 1 05:59:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA29779 for freebsd-stable-outgoing; Tue, 1 Dec 1998 05:59:14 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA29774 for ; Tue, 1 Dec 1998 05:59:11 -0800 (PST) (envelope-from dom@phmit.demon.co.uk) Received: from voodoo.pandhm.co.uk [10.100.35.12] by phmit.demon.co.uk with esmtp (Exim 1.82 #1) id 0zkqLQ-0003oO-00; Tue, 1 Dec 1998 14:00:00 +0000 Received: from dom by voodoo.pandhm.co.uk with local (Exim 1.92 #1) for freebsd-stable@freebsd.org id 0zkqLP-00007y-00; Tue, 1 Dec 1998 13:59:59 +0000 To: freebsd-stable@FreeBSD.ORG Subject: NFS problems... X-Mailer: nmh v0.26 Organization: Palmer & Harvey McLane Date: Tue, 01 Dec 1998 13:59:59 +0000 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi there, I'm seeing a curious problem with my NFS mounted home directory... Every now and again, it just hangs, in the usual NFS fashion with a message: Oct 25 14:28:09 voodoo /kernel: nfs server admin:/export/home: not responding % grep /home /etc/fstab admin:/export/home /home nfs rw,-i,-3,-T 0 0 % uname -a FreeBSD voodoo.pandhm.co.uk 2.2.8-RELEASE FreeBSD 2.2.8-RELEASE #0: Mon Nov 30 05:15:30 GMT 1998 root@voodoo.pandhm.co.uk:/usr/src/sys/compile/VOODOO i386 % ifconfig xl0 xl0: flags=8843 mtu 1500 inet 10.100.35.12 netmask 0xffff0000 broadcast 10.100.255.255 ether 00:60:08:76:7d:56 media: 100baseTX supported media: autoselect 100baseTX 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP It's running on a 100BaseT switched network to a Solaris 2.6 server. The funny thing is that when it hangs, it doesn't recover, the way that I have seen before with these problems. What is even weirder (to me) is that I can mount the problem filesystem in a different place (say, /mnt) and it works fine! The underlying network connectivity isn't going away. BTW, I've also started using the access cache which has just recently been imported. It seems to work great (aside from this slight problem, but I'm not sure if it's related). I realise that this isn't enough to go on for solving the problem. What other things can I try when the /home mount gets hung again? Can I force a crash dump to take a closer look? Thanks for any assistance. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator ``Those who do not understand Unix are condemned to reinvent it, poorly.'' -- Henry Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 1 06:12:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA01509 for freebsd-stable-outgoing; Tue, 1 Dec 1998 06:12:32 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA01504 for ; Tue, 1 Dec 1998 06:12:30 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id GAA29254; Tue, 1 Dec 1998 06:12:29 -0800 (PST) Message-Id: <199812011412.GAA29254@root.com> To: Dom Mitchell cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS problems... In-reply-to: Your message of "Tue, 01 Dec 1998 13:59:59 GMT." From: David Greenman Reply-To: dg@root.com Date: Tue, 01 Dec 1998 06:12:29 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >admin:/export/home /home nfs rw,-i,-3,-T 0 0 ... >I realise that this isn't enough to go on for solving the problem. What >other things can I try when the /home mount gets hung again? Can I >force a crash dump to take a closer look? This is a known problem with NFSv3 mounts. The work around is to use v2 mounts. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 1 17:28:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18550 for freebsd-stable-outgoing; Tue, 1 Dec 1998 17:28:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cc942873-a.ewndsr1.nj.home.com (cc942873-a.ewndsr1.nj.home.com [24.2.89.207]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18542 for ; Tue, 1 Dec 1998 17:28:04 -0800 (PST) (envelope-from cjc@cc942873-a.ewndsr1.nj.home.com) Received: (from cjc@localhost) by cc942873-a.ewndsr1.nj.home.com (8.8.8/8.8.8) id UAA00551; Tue, 1 Dec 1998 20:28:28 -0500 (EST) (envelope-from cjc) From: "Crist J. Clark" Message-Id: <199812020128.UAA00551@cc942873-a.ewndsr1.nj.home.com> Subject: Re: NFS problems... In-Reply-To: from Dom Mitchell at "Dec 1, 98 01:59:59 pm" To: dom@phmit.demon.co.uk (Dom Mitchell) Date: Tue, 1 Dec 1998 20:28:28 -0500 (EST) Cc: freebsd-stable@FreeBSD.ORG Reply-To: cjclark@home.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dom Mitchell wrote, > Hi there, > > I'm seeing a curious problem with my NFS mounted home directory... > Every now and again, it just hangs, in the usual NFS fashion with a > message: > > Oct 25 14:28:09 voodoo /kernel: nfs server admin:/export/home: not responding > > % grep /home /etc/fstab > admin:/export/home /home nfs rw,-i,-3,-T 0 0 [snip] > It's running on a 100BaseT switched network to a Solaris 2.6 server. Should you be using the '-T' flag with the Solaris server? > I realise that this isn't enough to go on for solving the problem. What > other things can I try when the /home mount gets hung again? Can I > force a crash dump to take a closer look? Can you 'umount -f admin:/export/home'? -- Crist J. Clark cjclark@home.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 1 19:24:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27937 for freebsd-stable-outgoing; Tue, 1 Dec 1998 19:24:06 -0800 (PST) (envelope-from owner-freebsd-stable@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 TAA27930 for ; Tue, 1 Dec 1998 19:24:02 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id TAA01729; Tue, 1 Dec 1998 19:25:40 -0800 (PST) To: Drew Derbyshire cc: stable@FreeBSD.ORG Subject: Re: minor errors in the 11/28 SNAP In-reply-to: Your message of "Mon, 30 Nov 1998 08:22:35 EST." <36629C1B.2AD8BB30@kew.com> Date: Tue, 01 Dec 1998 19:25:38 -0800 Message-ID: <1726.912569138@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Using the latest SNAP available for stable as of yesterday morning... > > 1) In sysinstall, if performing an upgrade, the install can't find UPGRADE.TX T > on the boot floppy to give you the standard dire warnings. This has the side > effect of making once feel the entire upgrade just failed. (It didn't, but > made me chicken out the first time). Thanks for the REALLY LATE bug report, but it was still just in time I guess. :-) I committed an 11th hour fix for this before rollign 2.2.8. > > 2) There is a message to the effect of 'there is ... shell already running vo n > ttyv4, shall I kill it and start a new one'? "von" should be "on" Ah well, typos for later. :-) Thanks. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 1 19:41:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29321 for freebsd-stable-outgoing; Tue, 1 Dec 1998 19:41:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from kendra.ne.mediaone.net (kendra.ne.mediaone.net [24.128.94.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29316 for ; Tue, 1 Dec 1998 19:41:28 -0800 (PST) (envelope-from software@kew.com) Received: from sonata.hh.kew.com (root@sonata-dmz.hh.kew.com [192.168.205.1]) by kendra.ne.mediaone.net (8.9.1/8.9.1) with ESMTP id WAA08077 for ; Tue, 1 Dec 1998 22:41:12 -0500 (EST) Received: from kew.com (minerva.hh.kew.com [192.168.203.144]) by sonata.hh.kew.com (8.9.1/8.9.1) with ESMTP id WAA04840 for ; Tue, 1 Dec 1998 22:41:11 -0500 (EST) Message-ID: <3664B6D6.8D90F744@kew.com> Date: Tue, 01 Dec 1998 22:41:10 -0500 From: Drew Derbyshire Organization: Kendra Electronic Wonderworks, Stoneham, MA 02180 (http://www.kew.com) X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: Re: minor errors in the 11/28 SNAP References: <1726.912569138@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > > Using the latest SNAP available for stable as of yesterday morning... > > > > 1) In sysinstall, if performing an upgrade, the install can't find UPGRADE.TX > T > > on the boot floppy to give you the standard dire warnings. This has the side > > effect of making once feel the entire upgrade just failed. (It didn't, but > > made me chicken out the first time). > > Thanks for the REALLY LATE bug report, but it was still just in time > I guess. :-) I committed an 11th hour fix for this before rollign 2.2.8. I figured it could be really early for 2.2.9. :-) (Okay, 3.1). Sounds like not too many people tried the upgrade option. :-) Seriously, I almost assumed it was because it was a SNAP and not the release. I almost didn't mention it. > > 2) There is a message to the effect of 'there is ... shell already running vo > n > > ttyv4, shall I kill it and start a new one'? "von" should be "on" > > Ah well, typos for later. :-) That's fine ... it took some major hoops to get the extra shell running in the first place. -- Drew Derbyshire UUPC/extended e-mail: software@kew.com Telephone: 617-279-9812 Air conditioned environment - Do not open Windows. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 01:09:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27351 for freebsd-stable-outgoing; Wed, 2 Dec 1998 01:09:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA27346 for ; Wed, 2 Dec 1998 01:09:37 -0800 (PST) (envelope-from dom@phmit.demon.co.uk) Received: from voodoo.pandhm.co.uk [10.100.35.12] by phmit.demon.co.uk with esmtp (Exim 1.82 #1) id 0zl8Ii-00046c-00; Wed, 2 Dec 1998 09:10:24 +0000 Received: from dom by voodoo.pandhm.co.uk with local (Exim 1.92 #1) id 0zl8Ig-0000Wy-00; Wed, 2 Dec 1998 09:10:22 +0000 To: cjclark@home.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: NFS problems... X-Mailer: nmh v0.26 X-Colour: Green Organization: Palmer & Harvey McLane In-reply-to: "Crist J. Clark"'s message of "Tue, 01 Dec 1998 20:28:28 EST" <199812020128.UAA00551@cc942873-a.ewndsr1.nj.home.com> Date: Wed, 02 Dec 1998 09:10:21 +0000 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1 December 1998, "Crist J. Clark" proclaimed: > Dom Mitchell wrote, > > % grep /home /etc/fstab > > admin:/export/home /home nfs rw,-i,-3,-T 0 0 > [snip] > > It's running on a 100BaseT switched network to a Solaris 2.6 server. > > Should you be using the '-T' flag with the Solaris server? I don't see why not. NFSv3 is supposed to use tcp AFAIK. > > I realise that this isn't enough to go on for solving the problem. What > > other things can I try when the /home mount gets hung again? Can I > > force a crash dump to take a closer look? > > Can you 'umount -f admin:/export/home'? Naw, it just hung saying "server not responding" again. :-( I've managed to cure my problems by switching back to nfsv2 and turning off the new access cache, in the meantime. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator ``Those who do not understand Unix are condemned to reinvent it, poorly.'' -- Henry Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 03:03:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA06320 for freebsd-stable-outgoing; Wed, 2 Dec 1998 03:03:44 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from web4.rocketmail.com (web4.rocketmail.com [205.180.57.78]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA06314 for ; Wed, 2 Dec 1998 03:03:39 -0800 (PST) (envelope-from ee123@rocketmail.com) Message-ID: <19981202110022.12032.rocketmail@web4.rocketmail.com> Received: from [195.6.245.137] by web4; Wed, 02 Dec 1998 03:00:22 PST Date: Wed, 2 Dec 1998 03:00:22 -0800 (PST) From: EE Reply-To: ee123@rocketmail.com Subject: adding a 3com 905B driver on 2.2.7 To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I need to add a 3com 905B ethernet card on a system with Freebsd 2.2.7 ( only supported on 2.2.8 ) Does anybody know how I must do to add driver? (which files, where, how...) Thanks a lot in advance. _________________________________________________________ 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-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 03:30:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA08829 for freebsd-stable-outgoing; Wed, 2 Dec 1998 03:30:18 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from csi-x.net (csi-x.net [202.184.73.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA08823 for ; Wed, 2 Dec 1998 03:30:11 -0800 (PST) (envelope-from najib@csi-x.net) Received: from csi-x.net (nobody@csi-x.net [202.184.73.5]) by csi-x.net (8.9.1/8.9.1) with SMTP id TAA16801 for ; Wed, 2 Dec 1998 19:36:11 +0800 (MYT) From: "Muhammad Najib" Reply-to: najib@csi-x.net To: freebsd-stable@FreeBSD.ORG Date: Wed, 2 Dec 1998 19:36:14 -800 Subject: Re: adding a 3com 905B driver on 2.2.7 Message-id: <3665262e.419c.0@csi-x.net> X-User-Info: 202.184.73.12 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hi, > >I need to add a 3com 905B ethernet card on a system >with Freebsd 2.2.7 ( only supported on 2.2.8 ) > >Does anybody know how I must do to add driver? >(which files, where, how...) > >Thanks a lot in advance. You need to recompile your kernel device ep0 at isa? port 0x300 net irq 10 vector epintr add that line .. perhaps you wanna change to io port to something else or use that as default.. then recompile :) cheers, ****************************************************************** MUHAMMAD NAJIB ABDUL MUKTHI member of My-Linux.ORG CO SYSTEM ADMINISTRATOR http://www.my-linux.org Kolej Damansara Utama 32, Jalan Anson najib@mrsm.org 10400, Pulau Pinang. najib@csi-x.net http://najib.csi-x.net najib@kdupg.edu.my Tel : 012-4717452 najib@my-linux.org ****************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 03:32:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09114 for freebsd-stable-outgoing; Wed, 2 Dec 1998 03:32:51 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA09108 for ; Wed, 2 Dec 1998 03:32:48 -0800 (PST) (envelope-from dom@phmit.demon.co.uk) Received: from voodoo.pandhm.co.uk [10.100.35.12] by phmit.demon.co.uk with esmtp (Exim 1.82 #1) id 0zlAXE-0004Bj-00; Wed, 2 Dec 1998 11:33:32 +0000 Received: from dom by voodoo.pandhm.co.uk with local (Exim 1.92 #1) id 0zlAXB-0001VP-00; Wed, 2 Dec 1998 11:33:29 +0000 To: ee123@rocketmail.com cc: freebsd-stable@FreeBSD.ORG Subject: Re: adding a 3com 905B driver on 2.2.7 X-Mailer: nmh v0.26 X-Colour: Green Organization: Palmer & Harvey McLane In-reply-to: EE's message of "Wed, 02 Dec 1998 03:00:22 PST" <19981202110022.12032.rocketmail@web4.rocketmail.com> Date: Wed, 02 Dec 1998 11:33:29 +0000 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2 December 1998, EE proclaimed: > I need to add a 3com 905B ethernet card on a system > with Freebsd 2.2.7 ( only supported on 2.2.8 ) > > Does anybody know how I must do to add driver? > (which files, where, how...) You shouldn't have to add anything. As far as I know, it's already supported by the xl(4) driver. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator ``Those who do not understand Unix are condemned to reinvent it, poorly.'' -- Henry Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 04:12:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA13625 for freebsd-stable-outgoing; Wed, 2 Dec 1998 04:12:15 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from multivac.fatburen.org (multivac.fatburen.org [62.20.128.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA13620 for ; Wed, 2 Dec 1998 04:12:11 -0800 (PST) (envelope-from staffanu@multivac.fatburen.org) Received: (from staffanu@localhost) by multivac.fatburen.org (8.8.8/8.8.8) id NAA09672; Wed, 2 Dec 1998 13:11:53 +0100 (CET) (envelope-from staffanu) To: freebsd-stable@FreeBSD.ORG Subject: Re: adding a 3com 905B driver on 2.2.7 References: Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII From: Staffan Ulfberg Date: 02 Dec 1998 13:11:48 +0100 In-Reply-To: Dom Mitchell's message of Wed, 02 Dec 1998 11:33:29 +0000 Message-ID: <87yaoqkakb.fsf@multivac.fatburen.org> Lines: 24 X-Mailer: Gnus v5.5/Emacs 20.2 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dom Mitchell writes: > On 2 December 1998, EE proclaimed: > > I need to add a 3com 905B ethernet card on a system > > with Freebsd 2.2.7 ( only supported on 2.2.8 ) > > > > Does anybody know how I must do to add driver? > > (which files, where, how...) > > You shouldn't have to add anything. As far as I know, it's already > supported by the xl(4) driver. The xl driver wasn't available in 2.2.7-RELEASE, but I think it was introduced some time ago in 2.2.7-STABLE, and is now part of the 2.2.8 release. Anyway, to answer the original question, go to http://www.freebsd.org/~wpaul/3Com/ to download the driver separately. Complete installation intructions are available at the above address. Staffan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 04:43:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA16380 for freebsd-stable-outgoing; Wed, 2 Dec 1998 04:43:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from csi-x.net (csi-x.net [202.184.73.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA16375 for ; Wed, 2 Dec 1998 04:43:38 -0800 (PST) (envelope-from najib@csi-x.net) Received: from csi-x.net (nobody@csi-x.net [202.184.73.5]) by csi-x.net (8.9.1/8.9.1) with SMTP id UAA23833 for ; Wed, 2 Dec 1998 20:48:40 +0800 (MYT) From: "Muhammad Najib" Reply-to: najib@csi-x.net To: freebsd-stable@FreeBSD.ORG Date: Wed, 2 Dec 1998 20:48:41 -800 Subject: Re: adding a 3com 905B driver on 2.2.7 Message-id: <36653729.5d10.0@csi-x.net> X-User-Info: 202.184.73.12 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Wed, 2 Dec 1998, Muhammad Najib wrote: > >> >Hi, >> > >> >I need to add a 3com 905B ethernet card on a system >> >with Freebsd 2.2.7 ( only supported on 2.2.8 ) >> > >> >Does anybody know how I must do to add driver? >> >(which files, where, how...) >> > >> >Thanks a lot in advance. >> >> You need to recompile your kernel >> >> device ep0 at isa? port 0x300 net irq 10 vector epintr > ^^^ > ^^^ > ^^^ > >nope, > >the right driver is xl0. This is a 2.2.7-STABLE (cvsupped after 3c905B >port). This NIC is PCI, not ISA. > >xl0 <3Com 3c905B Fast Etherlink XL 10/100BaseTX> rev 36 int a irq 12 on pci0:12:0 >xl0: Ethernet address: 00:10:4b:09:f1:70 >xl0: autoneg complete, link status good (half-duplex, 100Mbps) > Oops ... my wrong .. I thought it is 509B .. sorry :) cheers, ****************************************************************** MUHAMMAD NAJIB ABDUL MUKTHI member of My-Linux.ORG CO SYSTEM ADMINISTRATOR http://www.my-linux.org Kolej Damansara Utama 32, Jalan Anson najib@mrsm.org 10400, Pulau Pinang. najib@csi-x.net http://najib.csi-x.net najib@kdupg.edu.my Tel : 012-4717452 najib@my-linux.org ****************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 05:27:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA20928 for freebsd-stable-outgoing; Wed, 2 Dec 1998 05:27:47 -0800 (PST) (envelope-from owner-freebsd-stable@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 FAA20852 for ; Wed, 2 Dec 1998 05:27:16 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=localhost) by axl.noc.iafrica.com with local-esmtp (Exim 2.053 #1) id 0zlCIr-0006QA-00; Wed, 2 Dec 1998 15:26:49 +0200 From: Sheldon Hearn To: Staffan Ulfberg cc: freebsd-stable@FreeBSD.ORG Subject: Re: adding a 3com 905B driver on 2.2.7 In-reply-to: Your message of "02 Dec 1998 13:11:48 +0100." <87yaoqkakb.fsf@multivac.fatburen.org> Date: Wed, 02 Dec 1998 15:26:49 +0200 Message-ID: <24685.912605209@localhost> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 02 Dec 1998 13:11:48 +0100, Staffan Ulfberg wrote: > The xl driver wasn't available in 2.2.7-RELEASE, but I think it was > introduced some time ago in 2.2.7-STABLE, and is now part of the 2.2.8 > release. >From the commit log for LINT: | revision 1.286.2.58 | date: 1998/08/24 18:17:50; author: wpaul; state: Exp; lines: +8 -1 | Add XL driver and man page to the 2.2 branch. | | Update sys/conf/files to include xl driver. | Update GENERIC and LINT. | Update sys/pci/if_vx_pci.c to not probe Etherlink XL cards anymore. | Update man4/man4.i386/Makefile to install new man page (correctly this | time!). | | This version of the driver is current up to today. Both versions | should remain in sync, unless I screw up. If you don't feel comfortable with installing the driver by hand, you might consider updating your sources to anything after 1998/08/24, as indicated by the log message above. Details on updating 2.2.8 sources using CVSup, see: http://www.freebsd.org/handbook/handbook273.html http://www.freebsd.org/handbook/handbook277.html Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 10:50:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA22000 for freebsd-stable-outgoing; Wed, 2 Dec 1998 10:50:17 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from peloton.physics.montana.edu (peloton.physics.montana.edu [153.90.192.177]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA21991 for ; Wed, 2 Dec 1998 10:50:15 -0800 (PST) (envelope-from brett@peloton.physics.montana.edu) Received: from localhost (brett@localhost) by peloton.physics.montana.edu (8.8.8/8.8.7) with SMTP id LAA00339 for ; Wed, 2 Dec 1998 11:49:56 -0700 (MST) (envelope-from brett@peloton.physics.montana.edu) Date: Wed, 2 Dec 1998 11:49:56 -0700 (MST) From: Brett Taylor To: freebsd-stable@FreeBSD.ORG Subject: make world problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently tried to take two of my machines from 2.2-STABLE to the latest greatest after the 2.2.8 release. Neither can complete a make world. Machine #1: last did a make world on Sept 15th it errors out at: --- cd9660_bmap.o --- cc -nostdinc -O2 -pipe -DCD9660 -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/cd9660/../../sys -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -I/usr/obj/usr/src/tmp/usr/include -DVFS_LKM -DMODVNOPS=cd9660_modvnops -I. -c /usr/src/lkm/cd9660/../../sys/isofs/cd9660/cd9660_bmap.c In file included from /usr/src/lkm/cd9660/../../sys/isofs/cd9660/cd9660_bmap.c:52: /usr/src/lkm/cd9660/../../sys/isofs/cd9660/cd9660_node.h:122: warning: `struct vop_lookup_args' declared inside parameter list /usr/src/lkm/cd9660/../../sys/isofs/cd9660/cd9660_node.h:122: warning: its scope is only this definition or declaration, -snip- /usr/src/lkm/cd9660/../../sys/isofs/cd9660/cd9660_bmap.c:100: dereferencing pointer to incomplete type /usr/src/lkm/cd9660/../../sys/isofs/cd9660/cd9660_bmap.c:102: dereferencing pointer to incomplete type /usr/src/lkm/cd9660/../../sys/isofs/cd9660/cd9660_bmap.c:105: dereferencing pointer to incomplete type /usr/src/lkm/cd9660/../../sys/isofs/cd9660/cd9660_bmap.c:106: dereferencing pointer to incomplete type *** Error code 1 Machine #2 also last made world on 15th of Sept errors out in: --- ccd.o --- cc -nostdinc -O -I. -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/ccd/../.. /sys -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Ws trict-prototypes -Wmissing-prototypes -Wpointer-arith -I/usr/obj/usr/src/tmp/us r/include -DPSEUDO_LKM -c /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c /usr/src/lkm/ccd/../../sys/sys/vnode.h: In function `VOP_BMAP': In file included from /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c:116: /usr/src/lkm/ccd/../../sys/sys/vnode.h:383: `V' undeclared (first use this function) -snip- /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c:1489: dereferencing pointer to incomplete type /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c:1498: parse error before `static' /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c:1516: parse error before `static' /usr/src/lkm/ccd/../../sys/dev/ccd/ccd.c:1552: parse error at end of input *** Error code 1 ---------------------------------------------------------------------- Any ideas on why this is happening? Brett To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 11:59:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27696 for freebsd-stable-outgoing; Wed, 2 Dec 1998 11:59:58 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.intercom.com ([207.51.55.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27691 for ; Wed, 2 Dec 1998 11:59:55 -0800 (PST) (envelope-from jason@intercom.com) Received: from intercom.com (shagalicious.com [206.98.165.250]) by mail.intercom.com (8.9.0/8.9.0) with ESMTP id OAA20571 for ; Wed, 2 Dec 1998 14:59:36 -0500 (EST) Message-ID: <36659B88.441667ED@intercom.com> Date: Wed, 02 Dec 1998 14:56:56 -0500 From: "Jason J. Horton" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: make world problems [long] Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am having simular problems. On my freshly installed 2.2.8-RELEASE machine, I cannot get a buildworld to finish. If I do this: make -j4 -DNOCLEAN -DNOPROFILE=true buildworld it seems to fail at different points, first run failed on a cd9660 file, and then a different point each run. Here is output from my last 2 runs: --- kernfs_vnops.o --- /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_lookup': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:233: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:112: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:234: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:235: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:236: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:318: warning: implicit declaration of function `VOP_LOCK' /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_open': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:356: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:113: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:357: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:370: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_access': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:384: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:107: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:385: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:386: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:387: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_getattr': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:420: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:110: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:421: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:422: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_setattr': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:484: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:119: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_read': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:503: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:116: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:504: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:505: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_write': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:538: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:121: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:539: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:540: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_readdir': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:574: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:117: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:575: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_inactive': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:623: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:111: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:624: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_reclaim': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:642: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:118: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:643: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_pathconf': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:664: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:114: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:666: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:668: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:671: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:674: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:677: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:680: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:683: dereferencing pointer to incomplete type /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_print':^M /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:700: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:115: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: In function `kernfs_vfree': /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:714: argument `ap' doesn't match prototype /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:120: prototype declaration /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c: At top level: /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:775: `vop_default_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:775: initializer element for `kernfs_vnodeop_entries[0].opve_op' is not c onstant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:776: `vop_lookup_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:776: initializer element for `kernfs_vnodeop_entries[1].opve_op' is not c onstant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:777: `vop_create_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:777: initializer element for `kernfs_vnodeop_entries[2].opve_op' is not c onstant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:777: warning: `struct vop_create_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:778: `vop_mknod_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:778: initializer element for `kernfs_vnodeop_entries[3].opve_op' is not c onstant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:778: warning: `struct vop_mknod_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:779: `vop_open_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:779: initializer element for `kernfs_vnodeop_entries[4].opve_op' is not c onstant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:780: `vop_close_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:780: initializer element for `kernfs_vnodeop_entries[5].opve_op' is not c onstant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:780: warning: `struct vop_close_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:781: `vop_access_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:781: initializer element for `kernfs_vnodeop_entries[6].opve_op' is not c onstant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:782: `vop_getattr_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:782: initializer element for `kernfs_vnodeop_entries[7].opve_op' is not c onstant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:783: `vop_setattr_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:783: initializer element for `kernfs_vnodeop_entries[8].opve_op' is not c onstant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:784: `vop_read_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:784: initializer element for `kernfs_vnodeop_entries[9].opve_op' is not c onstant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:785: `vop_write_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:785: initializer element for `kernfs_vnodeop_entries[10].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:786: `vop_ioctl_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:786: initializer element for `kernfs_vnodeop_entries[11].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:786: warning: `struct vop_ioctl_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:787: `vop_select_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:787: initializer element for `kernfs_vnodeop_entries[12].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:787: warning: `struct vop_select_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:788: `vop_mmap_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:788: initializer element for `kernfs_vnodeop_entries[13].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:788: warning: `struct vop_mmap_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:789: `vop_fsync_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:789: initializer element for `kernfs_vnodeop_entries[14].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:789: warning: `struct vop_fsync_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:790: `vop_seek_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:790: initializer element for `kernfs_vnodeop_entries[15].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:790: warning: `struct vop_seek_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:791: `vop_remove_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:791: initializer element for `kernfs_vnodeop_entries[16].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:791: warning: `struct vop_remove_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:792: `vop_link_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:792: initializer element for `kernfs_vnodeop_entries[17].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:792: warning: `struct vop_link_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:793: `vop_rename_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:793: initializer element for `kernfs_vnodeop_entries[18].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:793: warning: `struct vop_rename_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:794: `vop_mkdir_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:794: initializer element for `kernfs_vnodeop_entries[19].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:794: warning: `struct vop_mkdir_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:795: `vop_rmdir_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:795: initializer element for `kernfs_vnodeop_entries[20].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:795: warning: `struct vop_rmdir_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:796: `vop_symlink_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:796: initializer element for `kernfs_vnodeop_entries[21].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:796: warning: `struct vop_symlink_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:797: `vop_readdir_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:797: initializer element for `kernfs_vnodeop_entries[22].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:798: `vop_readlink_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:798: initializer element for `kernfs_vnodeop_entries[23].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:798: warning: `struct vop_readlink_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:799: `vop_abortop_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:799: initializer element for `kernfs_vnodeop_entries[24].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:799: warning: `struct vop_abortop_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:800: `vop_inactive_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:800: initializer element for `kernfs_vnodeop_entries[25].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:801: `vop_reclaim_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:801: initializer element for `kernfs_vnodeop_entries[26].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:802: `vop_lock_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:802: initializer element for `kernfs_vnodeop_entries[27].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:802: warning: `struct vop_lock_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:803: `vop_unlock_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:803: initializer element for `kernfs_vnodeop_entries[28].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:803: warning: `struct vop_unlock_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:804: `vop_bmap_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:804: initializer element for `kernfs_vnodeop_entries[29].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:804: warning: `struct vop_bmap_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:805: `vop_strategy_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:805: initializer element for `kernfs_vnodeop_entries[30].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:805: warning: `struct vop_strategy_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:806: `vop_print_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:806: initializer element for `kernfs_vnodeop_entries[31].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:807: `vop_islocked_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:807: initializer element for `kernfs_vnodeop_entries[32].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:807: warning: `struct vop_islocked_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:808: `vop_pathconf_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:808: initializer element for `kernfs_vnodeop_entries[33].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:809: `vop_advlock_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:809: initializer element for `kernfs_vnodeop_entries[34].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:809: warning: `struct vop_advlock_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:810: `vop_blkatoff_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:810: initializer element for `kernfs_vnodeop_entries[35].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:810: warning: `struct vop_blkatoff_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:811: `vop_valloc_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:811: initializer element for `kernfs_vnodeop_entries[36].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:812: `vop_vfree_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:812: initializer element for `kernfs_vnodeop_entries[37].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:813: `vop_truncate_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:813: initializer element for `kernfs_vnodeop_entries[38].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:813: warning: `struct vop_truncate_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:814: `vop_update_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:814: initializer element for `kernfs_vnodeop_entries[39].opve_op' is not constant /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:814: warning: `struct vop_update_args' declared inside parameter list /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:815: `vop_bwrite_desc' undeclared here (not in a function) /usr/src/lkm/kernfs/../../sys/miscfs/kernfs/kernfs_vnops.c:815: initializer element for `kernfs_vnodeop_entries[40].opve_op' is not constant *** Error code 1 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error # Second try ===> lkm/linux --- machine --- --- linux.o --- --- linux_file.o --- --- linux_ioctl.o --- --- machine --- ln -fs /usr/src/lkm/linux/../../sys/i386/include machine --- linux.o --- cc -nostdinc -O -pipe -DLKM -I. -DCOMPAT_43 -DCOMPAT_LINUX -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/linux/../../sys -Wret urn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -I/usr/o bj/usr/src/tmp/usr/include -c /usr/src/lkm/linux/linux.c --- linux_file.o --- cc -nostdinc -O -pipe -DLKM -I. -DCOMPAT_43 -DCOMPAT_LINUX -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/linux/../../sys -Wret urn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -I/usr/o bj/usr/src/tmp/usr/include -c /usr/src/lkm/linux/../../sys/i386/linux/linux_file.c --- linux_ioctl.o --- cc -nostdinc -O -pipe -DLKM -I. -DCOMPAT_43 -DCOMPAT_LINUX -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/linux/../../sys -Wret urn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -I/usr/o bj/usr/src/tmp/usr/include -c /usr/src/lkm/linux/../../sys/i386/linux/linux_ioctl.c --- linux_misc.o --- --- linux_file.o --- In file included from /usr/src/lkm/linux/../../sys/i386/linux/linux_file.c:39: /usr/src/lkm/linux/../../sys/sys/vnode.h:378: vnode_if.h: No such file or directory --- linux_misc.o --- cc -nostdinc -O -pipe -DLKM -I. -DCOMPAT_43 -DCOMPAT_LINUX -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/linux/../../sys -Wret urn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -I/usr/o bj/usr/src/tmp/usr/include -c /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c In file included from /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:51: /usr/src/lkm/linux/../../sys/sys/vnode.h:378: vnode_if.h: No such file or directory --- linux_signal.o --- --- linux_file.o --- /usr/src/lkm/linux/../../sys/i386/linux/linux_file.c: In function `linux_fcntl': /usr/src/lkm/linux/../../sys/i386/linux/linux_file.c:299: warning: implicit declaration of function `VOP_GETATTR' /usr/src/lkm/linux/../../sys/i386/linux/linux_file.c: In function `linux_getdents': /usr/src/lkm/linux/../../sys/i386/linux/linux_file.c:450: warning: implicit declaration of function `VOP_LOCK' /usr/src/lkm/linux/../../sys/i386/linux/linux_file.c:467: warning: implicit declaration of function `VOP_READDIR' /usr/src/lkm/linux/../../sys/i386/linux/linux_file.c:564: warning: implicit declaration of function `VOP_UNLOCK' --- linux_misc.o --- /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c: In function `linux_uselib': /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:217: warning: implicit declaration of function `VOP_GETATTR' /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:238: warning: implicit declaration of function `VOP_ACCESS' /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:241: warning: implicit declaration of function `VOP_OPEN' /usr/src/lkm/linux/../../sys/i386/linux/linux_misc.c:247: warning: implicit declaration of function `VOP_UNLOCK' *** Error code 1 --- linux_file.o --- *** Error code 1 --- linux_signal.o --- cc -nostdinc -O -pipe -DLKM -I. -DCOMPAT_43 -DCOMPAT_LINUX -DKERNEL -DACTUALLY_LKM_NOT_KERNEL -I/usr/src/lkm/linux/../../sys -Wret urn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -I/usr/o bj/usr/src/tmp/usr/include -c /usr/src/lkm/linux/../../sys/i386/linux/linux_signal.c 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error # Any ideas? -J To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 12:43:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02375 for freebsd-stable-outgoing; Wed, 2 Dec 1998 12:43:33 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from csi-x.net (csi-x.net [202.184.73.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02365 for ; Wed, 2 Dec 1998 12:43:30 -0800 (PST) (envelope-from najib@csi-x.net) Received: from csi-x.net (nobody@csi-x.net [202.184.73.5]) by csi-x.net (8.9.1/8.9.1) with SMTP id EAA10925 for ; Thu, 3 Dec 1998 04:49:45 +0800 (MYT) From: "Muhammad Najib" Reply-to: najib@csi-x.net To: freebsd-stable@FreeBSD.ORG Date: Thu, 3 Dec 1998 04:49:46 -800 Subject: Re: make world problems Message-id: <3665a7ea.2aa8.0@csi-x.net> X-User-Info: 202.184.73.12 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I recently tried to take two of my machines from 2.2-STABLE to the latest >greatest after the 2.2.8 release. Neither can complete a make world. > You might wanna try make buildworld first .. then only make installworld ... cheers, ****************************************************************** MUHAMMAD NAJIB ABDUL MUKTHI member of My-Linux.ORG CO SYSTEM ADMINISTRATOR http://www.my-linux.org Kolej Damansara Utama 32, Jalan Anson najib@mrsm.org 10400, Pulau Pinang. najib@csi-x.net http://najib.csi-x.net najib@kdupg.edu.my Tel : 012-4717452 najib@my-linux.org ****************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 14:24:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA12475 for freebsd-stable-outgoing; Wed, 2 Dec 1998 14:24:08 -0800 (PST) (envelope-from owner-freebsd-stable@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 OAA12468 for ; Wed, 2 Dec 1998 14:24:05 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id JAA02828; Thu, 3 Dec 1998 09:23:50 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd002826; Wed Dec 2 22:23:44 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id JAA12546; Thu, 3 Dec 1998 09:23:50 +1100 (EST) Message-Id: <199812022223.JAA12546@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: "Jason J. Horton" Cc: stable@FreeBSD.ORG Subject: Re: make world problems [long] In-reply-to: Your message of Wed, 02 Dec 1998 14:56:56 -0500. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 09:23:40 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG jason@intercom.com said: > make -j4 -DNOCLEAN -DNOPROFILE=true buildworld Parallel makes are known to be broken on 2.x. Remove the -j4 and all should be well. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 17:15:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03832 for freebsd-stable-outgoing; Wed, 2 Dec 1998 17:15:03 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp10.portal.net.au [202.12.71.110]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03805 for ; Wed, 2 Dec 1998 17:14: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 OAA08949; Wed, 2 Dec 1998 14:58:53 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812022258.OAA08949@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Dom Mitchell cc: cjclark@home.com, freebsd-stable@FreeBSD.ORG Subject: Re: NFS problems... In-reply-to: Your message of "Wed, 02 Dec 1998 09:10:21 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 14:58:53 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On 1 December 1998, "Crist J. Clark" proclaimed: > > Dom Mitchell wrote, > > > % grep /home /etc/fstab > > > admin:/export/home /home nfs rw,-i,-3,-T 0 0 > > [snip] > > > It's running on a 100BaseT switched network to a Solaris 2.6 server. > > > > Should you be using the '-T' flag with the Solaris server? > > I don't see why not. NFSv3 is supposed to use tcp AFAIK. Rubbish. Definitely try using TCP mounts here; there's empirical evidence that tends to indicate that when working with Solaris servers there's a reasonable chance of either dropping response packets or having response packets "lost" in some other fashion. > > > I realise that this isn't enough to go on for solving the problem. What > > > other things can I try when the /home mount gets hung again? Can I > > > force a crash dump to take a closer look? > > > > Can you 'umount -f admin:/export/home'? > > Naw, it just hung saying "server not responding" again. :-( > > I've managed to cure my problems by switching back to nfsv2 and turning > off the new access cache, in the meantime. Since the access cache only affects v3 mounts, turning it off really just amounts to the waving of a dead chicken here. -- \\ 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-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 18:21:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11248 for freebsd-stable-outgoing; Wed, 2 Dec 1998 18:21:24 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from leo.pcisys.net ([207.76.102.243]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11232 for ; Wed, 2 Dec 1998 18:21:19 -0800 (PST) (envelope-from trsteins@pcisys.net) Received: from costanza17.cos.pcisys.net (costanza17.cos.pcisys.net [208.230.54.17]) by leo.pcisys.net (8.9.0/8.9.0) via SMTP id TAA11013 for ; Wed, 2 Dec 1998 19:21:04 -0700 (MST) env-from (trsteins@pcisys.net) From: trsteins@pcisys.net (Tracy Steinwand) To: FreeBSD-stable@FreeBSD.ORG Subject: mgetty help needed Date: Thu, 03 Dec 1998 02:21:16 GMT Message-ID: <3665f505.5646733@mail.pcisys.net> X-Mailer: Forte Free Agent 1.11/32.235 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running FreeBSD 2.2.7 on a PPro. When I initially installed the system, I went overboard and loaded many applications that I thought I'd get around to running/playing with. When I learned later that I was quickly running out of hard disk space, I decided to pkg_delete many of the items I felt I no longer needed. Apparently, I went overboard!!! Now when I boot my machine, I receive the following error login: Nov 29 04:26:46 steins init: Can't exec getty '/usr/local/sbin/mgetty' for port /dev/cuaa1: no such file or directory The mgetty program appears to be missing from /usr/local/sbin. My problem is that I don't know where it went or how to get it back. Any ideas? It doesn't seem to be adversly affecting my machine; I can still login, dial up my ISP, etc. Unfortunately, it keeps leaving me lots of these nagging messages on my screen. BTW, I'm planning on upgrading to 2.2.8. Will this take care of the problem? TIA Tracy Steinwand To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 18:21:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11262 for freebsd-stable-outgoing; Wed, 2 Dec 1998 18:21:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from chumbly.math.missouri.edu (chumbly.math.missouri.edu [128.206.72.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11243 for ; Wed, 2 Dec 1998 18:21:23 -0800 (PST) (envelope-from rich@chumbly.math.missouri.edu) Received: (from rich@localhost) by chumbly.math.missouri.edu (8.9.1a/8.9.1) id UAA21832 for freebsd-stable@freebsd.org; Wed, 2 Dec 1998 20:21:09 -0600 (CST) From: Rich Winkel Message-Id: <199812030221.UAA21832@chumbly.math.missouri.edu> Subject: accessing quiescent fbsd machine via network for maintenance To: freebsd-stable@FreeBSD.ORG Date: Wed, 2 Dec 1998 20:21:09 -0600 (CST) X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm running FBSD 2.2.7-stable. For various reasons I'd like to be able to upgrade fbsd machines without having to be seated in front of them. Specifically, I want to reboot into a mode where only a minimal amount of system activity is occurring, regular users are excluded, but remote root access and nfs mounts are allowed. This would allow me to login, mount a remote /usr/src & /usr/obj, run "make installworld" and install a new kernel. But this seems to be problematic. I can do it at the console by rebooting singleuser and running fsck, swapon, ifconfig and mount, but I have problems when I try to do it with a modified /etc/rc. Specifically, in /etc/rc I check for the existence of the file /etc/netmaintboot immediately after the network_pass1 call. If the file exists I execute /etc/rc.netmaint and exit 0. /etc/rc.netmaint consists of: #!/bin/sh # boot configured for maintenance from network ldconfig /usr/lib echo "Down for maintenance, try again later" > /etc/nologin TERM=cons25 clear echo "Entering maintenance mode, please don't touch" /sbin/sshd -b 1024 & exit 0 But for some reason sshd dies immediately and I can't login. But if I then login at the console and run sshd manually it works fine. Any ideas?? Do you think this kind of capability should be incorporated into a future release? Thanks!! Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 18:25:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11702 for freebsd-stable-outgoing; Wed, 2 Dec 1998 18:25:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp7.portal.net.au [202.12.71.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11693 for ; Wed, 2 Dec 1998 18:25:22 -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 SAA03218; Wed, 2 Dec 1998 18:23:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812030223.SAA03218@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: trsteins@pcisys.net (Tracy Steinwand) cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: mgetty help needed In-reply-to: Your message of "Thu, 03 Dec 1998 02:21:16 GMT." <3665f505.5646733@mail.pcisys.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Dec 1998 18:23:24 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm running FreeBSD 2.2.7 on a PPro. When I initially installed the > system, I went overboard and loaded many applications that I thought > I'd get around to running/playing with. When I learned later that I > was quickly running out of hard disk space, I decided to pkg_delete > many of the items I felt I no longer needed. Apparently, I went > overboard!!! Now when I boot my machine, I receive the following > error > > login: Nov 29 04:26:46 steins init: Can't exec getty > '/usr/local/sbin/mgetty' for port /dev/cuaa1: no such file or > directory > > The mgetty program appears to be missing from /usr/local/sbin. My > problem is that I don't know where it went or how to get it back. Any > ideas? You don't want it back, you want to restore /etc/ttys to its original state before you added the mgetty entry. -- \\ 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-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 18:33:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA12588 for freebsd-stable-outgoing; Wed, 2 Dec 1998 18:33:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA12583 for ; Wed, 2 Dec 1998 18:33:03 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zlOZP-0005As-00; Wed, 2 Dec 1998 18:32:43 -0800 Date: Wed, 2 Dec 1998 18:32:40 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Rich Winkel cc: freebsd-stable@FreeBSD.ORG Subject: Re: accessing quiescent fbsd machine via network for maintenance In-Reply-To: <199812030221.UAA21832@chumbly.math.missouri.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 2 Dec 1998, Rich Winkel wrote: > I'm running FBSD 2.2.7-stable. > For various reasons I'd like to be able to upgrade fbsd machines without > having to be seated in front of them. Specifically, I want to reboot > into a mode where only a minimal amount of system activity is > occurring, regular users are excluded, but remote root access and nfs Why bother? Just "make installworld" in full multi-user mode. "install" is quite smart. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 18:58:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA15780 for freebsd-stable-outgoing; Wed, 2 Dec 1998 18:58:37 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.double-barrel.be (mail.double-barrel.be [194.7.102.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA15726 for ; Wed, 2 Dec 1998 18:58:07 -0800 (PST) (envelope-from mvergall@mail.double-barrel.be) Received: (from uucp@localhost) by mail.double-barrel.be (8.8.8/8.8.8) id DAA00891; Thu, 3 Dec 1998 03:54:54 +0100 (CET) (envelope-from mvergall@mail.double-barrel.be) Received: from ns.double-barrel.be(194.7.102.18) via SMTP by mail.double-barrel.be, id smtpdiRC889; Thu Dec 3 03:54:52 1998 Date: Thu, 3 Dec 1998 03:54:49 +0100 (CET) From: "Michael C. Vergallen" X-Sender: mvergall@ns.double-barrel.be To: Tom cc: Rich Winkel , freebsd-stable@FreeBSD.ORG Subject: Re: accessing quiescent fbsd machine via network for maintenance In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What I do here is mount the servers / /usr /var and so on directories to /mnt on the build machine and then do a make installworld DESTDIR=/mnt and all gets installed in multiuser mode then I build a kernel for the servers and do a make install for the kernel with the DESTDIR option set. then I unmount the servers filesystems from the buildmachine and do a login to the servers to issue the reboot command. I find this reduces the machines downtime to about 2-3 minutes. Most users don't notice this or can put up with it. Michael --- Michael C. Vergallen A.k.A. Mad Mike, Sportstraat 28 http://www.double-barrel.be/mvergall/ B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ Belgium tel : 32-9-2227764 Fax : 32-9-2224976 On Wed, 2 Dec 1998, Tom wrote: > > On Wed, 2 Dec 1998, Rich Winkel wrote: > > > I'm running FBSD 2.2.7-stable. > > For various reasons I'd like to be able to upgrade fbsd machines without > > having to be seated in front of them. Specifically, I want to reboot > > into a mode where only a minimal amount of system activity is > > occurring, regular users are excluded, but remote root access and nfs > > Why bother? Just "make installworld" in full multi-user mode. > "install" is quite smart. > > Tom > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 20:51:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA27461 for freebsd-stable-outgoing; Wed, 2 Dec 1998 20:51:32 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA27455 for ; Wed, 2 Dec 1998 20:51:29 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca [204.244.186.218] by pop.uniserve.com with smtp (Exim 1.82 #4) id 0zlQhr-0004tB-00; Wed, 2 Dec 1998 20:49:35 -0800 Date: Wed, 2 Dec 1998 20:49:31 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: "Michael C. Vergallen" cc: Rich Winkel , freebsd-stable@FreeBSD.ORG Subject: Re: accessing quiescent fbsd machine via network for maintenance In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, Michael C. Vergallen wrote: > What I do here is mount the servers / /usr /var and so on directories to > /mnt on the build machine and then do a make installworld DESTDIR=/mnt and > all gets installed in multiuser mode then I build a kernel for the servers > and do a make install for the kernel with the DESTDIR option set. then I > unmount the servers filesystems from the buildmachine and do a login to > the servers to issue the reboot command. I find this reduces the machines > downtime to about 2-3 minutes. Most users don't notice this or can put up > with it. Why not just mount /usr/src and /usr/obj from the build machine on the clients? Less machines need to be setup as NFS servers. > Michael > --- > Michael C. Vergallen A.k.A. Mad Mike, > Sportstraat 28 http://www.double-barrel.be/mvergall/ > B 9000 Gent ftp://ftp.double-barrel.be/pub/linux/ > Belgium tel : 32-9-2227764 Fax : 32-9-2224976 Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 2 22:00:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA03078 for freebsd-stable-outgoing; Wed, 2 Dec 1998 22:00:59 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA03073 for ; Wed, 2 Dec 1998 22:00:57 -0800 (PST) (envelope-from fullermd@futuresouth.com) Received: (from fullermd@localhost) by shell.futuresouth.com (8.8.8/8.8.8) id XAA26225; Wed, 2 Dec 1998 23:45:16 -0600 (CST) Message-ID: <19981202234516.U4374@futuresouth.com> Date: Wed, 2 Dec 1998 23:45:16 -0600 From: "Matthew D. Fuller" To: Tom , "Michael C. Vergallen" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: accessing quiescent fbsd machine via network for maintenance References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Tom on Wed, Dec 02, 1998 at 08:49:31PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 02, 1998 at 08:49:31PM -0800, Tom woke me up to tell me: > > On Thu, 3 Dec 1998, Michael C. Vergallen wrote: > > > What I do here is mount the servers / /usr /var and so on directories to > > /mnt on the build machine and then do a make installworld DESTDIR=/mnt and > > all gets installed in multiuser mode then I build a kernel for the servers > > and do a make install for the kernel with the DESTDIR option set. then I > > unmount the servers filesystems from the buildmachine and do a login to > > the servers to issue the reboot command. I find this reduces the machines > > downtime to about 2-3 minutes. Most users don't notice this or can put up > > with it. > > Why not just mount /usr/src and /usr/obj from the build machine on the > clients? Less machines need to be setup as NFS servers. Beat me to it ;p Sticking everything under /mnt on the build machine does seem kinda bass-ackwards... and it keeps the installed files from being chflag'd too. Plus, it minimizes writes on NFS mounted partitions (ISTR that you can tweak it to have a ro /usr/src and /usr/obj, but I don't remember how). *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* | FreeBSD; the way computers were meant to be | * "The only reason I'm burning my candle at both ends, is * | that I haven't figured out how to light the middle yet."| * fullermd@futuresouth.com :-} MAtthew Fuller * | http://keystone.westminster.edu/~fullermd | *-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 00:51:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19232 for freebsd-stable-outgoing; Thu, 3 Dec 1998 00:51:42 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phmit.demon.co.uk (phmit.demon.co.uk [194.222.15.209]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA19225 for ; Thu, 3 Dec 1998 00:51:39 -0800 (PST) (envelope-from dom@phmit.demon.co.uk) Received: from voodoo.pandhm.co.uk [10.100.35.12] by phmit.demon.co.uk with esmtp (Exim 1.82 #1) id 0zlUUi-0004XB-00; Thu, 3 Dec 1998 08:52:16 +0000 Received: from dom by voodoo.pandhm.co.uk with local (Exim 1.92 #1) id 0zlUUh-0000Os-00; Thu, 3 Dec 1998 08:52:15 +0000 To: Mike Smith cc: cjclark@home.com, freebsd-stable@FreeBSD.ORG Subject: Re: NFS problems... X-Mailer: nmh v0.26 X-Colour: Green Organization: Palmer & Harvey McLane In-reply-to: Mike Smith's message of "Wed, 02 Dec 1998 14:58:53 PST" <199812022258.OAA08949@dingo.cdrom.com> Date: Thu, 03 Dec 1998 08:52:15 +0000 From: Dom Mitchell Message-Id: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 2 December 1998, Mike Smith proclaimed: > > I don't see why not. NFSv3 is supposed to use tcp AFAIK. > > Rubbish. Definitely try using TCP mounts here; there's empirical > evidence that tends to indicate that when working with Solaris servers > there's a reasonable chance of either dropping response packets or > having response packets "lost" in some other fashion. I was using TCP mounts, with NFSv3 initially. However, it realyl didn't work very well. > > I've managed to cure my problems by switching back to nfsv2 and turning > > off the new access cache, in the meantime. > > Since the access cache only affects v3 mounts, turning it off really > just amounts to the waving of a dead chicken here. Thank you. I wasn't aware of that. I wonder what was causing a difference in that case, because it certainly appeared to cause problems. Regardless, I now have a (moderately) working setup, using UDP, NFSv2. The only problems that I have had so far have been starting netscape. It caused the hang every time. Renaming my ~/.netscape directory to something else caused the problem to go away... Anyhow, thanks for your help, folks. -- Dom Mitchell -- Palmer & Harvey McLane -- Unix Systems Administrator ``Those who do not understand Unix are condemned to reinvent it, poorly.'' -- Henry Spencer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 04:44:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA06822 for freebsd-stable-outgoing; Thu, 3 Dec 1998 04:44:36 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from spooky.rwwa.com (rwwa.com [198.115.177.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA06817 for ; Thu, 3 Dec 1998 04:44:32 -0800 (PST) (envelope-from witr@rwwa.com) Received: from spooky.rwwa.com (localhost.rwwa.com [127.0.0.1]) by spooky.rwwa.com (8.8.7/8.8.7) with ESMTP id HAA21249; Thu, 3 Dec 1998 07:40:52 -0500 (EST) (envelope-from witr@rwwa.com) Message-Id: <199812031240.HAA21249@spooky.rwwa.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Dom Mitchell cc: Mike Smith , cjclark@home.com, freebsd-stable@FreeBSD.ORG Subject: Re: NFS problems... In-reply-to: Your message of "Thu, 03 Dec 1998 08:52:15 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 07:40:51 -0500 From: Robert Withrow Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG dom@phmit.demon.co.uk said: :- Regardless, I now have a (moderately) working setup, I really think this deserves a closer looking at. I have substantial NFS problems, similar to Don's, and other people have reported the same thing, with stable and current. Both of these are unusable in my environment due to unreliable NFS. I've been trying to get a sniffer on the wire to debug this for a while, but being in the last 4 weeks of a QA cycle things are kinda busy. I'll try to get it together next week. --------------------------------------------------------------------- Robert Withrow, R.W. Withrow Associates, Swampscott MA, witr@rwwa.COM To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 10:55:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07974 for freebsd-stable-outgoing; Thu, 3 Dec 1998 10:55:40 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07969 for ; Thu, 3 Dec 1998 10:55:39 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id NAA23137 for ; Thu, 3 Dec 1998 13:55:23 -0500 (EST) Date: Thu, 3 Dec 1998 13:55:23 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-stable@FreeBSD.ORG Subject: rc.shutdown and init Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone planning on backporting the changes to init and rc.shutdown to -stable? Seems like a very nice feature for those of us running sql daemons and other things that like a nice clean shutdown... Thanks, Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 13:28:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA25666 for freebsd-stable-outgoing; Thu, 3 Dec 1998 13:21:31 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from piggy.kharkiv.net (piggy.kharkiv.net [194.44.156.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA25637 for ; Thu, 3 Dec 1998 13:21:11 -0800 (PST) (envelope-from news@piggy.kharkiv.net) Received: (from news@localhost) by piggy.kharkiv.net for ; ; Thu, 3 Dec 1998 23:20:18 +0200 (EET) (envelope-from news) To: freebsd-stable@freebsd.org Subject: FAQ Date: Thu, 03 Dec 1998 23:20:17 +0200 Message-ID: <36670091.BB47CB5D@kharkiv.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-STABLE i386) X-Accept-Language: Russian, ru, en X-Via: News-To-Mail v1.0 From: "Newsgate" Reply-To: "Vadim V. Chepkov" Sender: owner-freebsd-stable@freebsd.org Precedence: bulk X-Loop: FreeBSD.ORG --> Use Reply-To: for answer to "Vadim V. Chepkov" Hello! I downloaded 2.2.8-RELEASE and installed doc/* distribution. In /usr/share/doc/FAQ/ I've got documents on Spanish. Why? -- Kind regards, Vadim V. Chepkov ------------------------------------------------------ Vadim V. Chepkov, Kharkiv State Polytechnic University 13 Frunze Str., Kharkiv, Ukraine, 310002 phone: +380 572 400478 fax: +380 572 400592 e-mail: vvc@kharkiv.net http://www.kharkiv.net/~vvc ------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 13:40:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA27923 for freebsd-stable-outgoing; Thu, 3 Dec 1998 13:40:48 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA27918 for ; Thu, 3 Dec 1998 13:40:47 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id QAA09374 for ; Thu, 3 Dec 1998 16:40:26 -0500 (EST) Date: Thu, 3 Dec 1998 16:40:26 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-stable@FreeBSD.ORG Subject: Re: rc.shutdown and init In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oops, nevermind, I checked out init, and I see the change was committed late August. The thing that threw me was that the /etc/shutdown.rc example exists only in the 3.0 branch. Could someone backport that? Thanks, Charles --- Charles Sprickman spork@super-g.com On Thu, 3 Dec 1998, spork wrote: > Is anyone planning on backporting the changes to init and rc.shutdown to > -stable? Seems like a very nice feature for those of us running sql > daemons and other things that like a nice clean shutdown... > > Thanks, > > Charles > > --- > Charles Sprickman > spork@super-g.com > --- > "...there's no idea that's so good you can't > ruin it with a few well-placed idiots." > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 15:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10873 for freebsd-stable-outgoing; Thu, 3 Dec 1998 15:17:23 -0800 (PST) (envelope-from owner-freebsd-stable@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 PAA10866 for ; Thu, 3 Dec 1998 15:17:19 -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 SAA64656; Thu, 3 Dec 1998 18:16:41 -0500 (EST) Date: Thu, 3 Dec 1998 18:16:41 -0500 (EST) From: jack To: "Vadim V. Chepkov" cc: freebsd-stable@FreeBSD.ORG Subject: Re: FAQ In-Reply-To: <36670091.BB47CB5D@kharkiv.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, Newsgate wrote: > I downloaded 2.2.8-RELEASE and installed doc/* distribution. > In /usr/share/doc/FAQ/ I've got documents on Spanish. Why? Good question. Wait until you install 3.0 and get Japanese man pages installed for you. Looks like it's time for another knob on sysinstall. :) -------------------------------------------------------------------------- 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-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 15:37:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA12628 for freebsd-stable-outgoing; Thu, 3 Dec 1998 15:37:15 -0800 (PST) (envelope-from owner-freebsd-stable@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 PAA12623 for ; Thu, 3 Dec 1998 15:37:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA35727; Thu, 3 Dec 1998 15:38:29 -0800 (PST) To: "Vadim V. Chepkov" cc: freebsd-stable@FreeBSD.ORG Subject: Re: FAQ In-reply-to: Your message of "Thu, 03 Dec 1998 23:20:17 +0200." <36670091.BB47CB5D@kharkiv.net> Date: Thu, 03 Dec 1998 15:38:29 -0800 Message-ID: <35724.912728309@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I downloaded 2.2.8-RELEASE and installed doc/* distribution. > In /usr/share/doc/FAQ/ I've got documents on Spanish. Why? "Oops." Damn - it looks like that fix for this never made it into -stable. :( If you rebuild /usr/share/doc/FAQ from sources, this problem should go away. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 15:47:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13595 for freebsd-stable-outgoing; Thu, 3 Dec 1998 15:47:26 -0800 (PST) (envelope-from owner-freebsd-stable@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 PAA13589 for ; Thu, 3 Dec 1998 15:47:25 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA35823; Thu, 3 Dec 1998 15:48:33 -0800 (PST) To: jack cc: "Vadim V. Chepkov" , freebsd-stable@FreeBSD.ORG Subject: Re: FAQ In-reply-to: Your message of "Thu, 03 Dec 1998 18:16:41 EST." Date: Thu, 03 Dec 1998 15:48:33 -0800 Message-ID: <35820.912728913@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, 3 Dec 1998, Newsgate wrote: > > > I downloaded 2.2.8-RELEASE and installed doc/* distribution. > > In /usr/share/doc/FAQ/ I've got documents on Spanish. Why? > > Good question. Wait until you install 3.0 and get Japanese man > pages installed for you. Different problem. You'll get japanese man pages but you'll also get the english ones. In this case, you *only* get the Spanish ones. Oh well, Spanish is probably the 2nd most popular language in the world after english, so I'll just tell people "we meant to do that" in the cause of promoting spanish literacy and linguistic parity. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 15:57:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA15022 for freebsd-stable-outgoing; Thu, 3 Dec 1998 15:57:50 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA15017 for ; Thu, 3 Dec 1998 15:57:49 -0800 (PST) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id PAA13074; Thu, 3 Dec 1998 15:57:23 -0800 (PST) Date: Thu, 3 Dec 1998 15:57:23 -0800 (PST) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199812032357.PAA13074@math.berkeley.edu> To: jkh@zippy.cdrom.com Subject: Re: FAQ Cc: dan@math.berkeley.edu, freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Oh well, Spanish is probably the 2nd most popular language in the > world after english, so I'll just tell people "we meant to do that" > in the cause of promoting spanish literacy and linguistic parity. The only official language of Unix OS is C. Accept no substitutes. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 16:46:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25329 for freebsd-stable-outgoing; Thu, 3 Dec 1998 16:46:41 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.intercom.com ([207.51.55.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25324 for ; Thu, 3 Dec 1998 16:46:39 -0800 (PST) (envelope-from jason@intercom.com) Received: from intercom.com (shagalicious.com [206.98.165.250]) by mail.intercom.com (8.9.0/8.9.0) with ESMTP id TAA15611 for ; Thu, 3 Dec 1998 19:46:22 -0500 (EST) Message-ID: <36673055.40EC6392@intercom.com> Date: Thu, 03 Dec 1998 19:44:05 -0500 From: "Jason J. Horton" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: 2.2.8-RELEASE and SCSI error Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I have been configuring a 2.2.8-RELEASE machine to take the place of my NetBSD 1.3.2 NFS server. The NetBSD machine has an Adaptec 2940-UW controller connected to a disk silo with an Adaptec AEC-4412BS SCSI to SCSI RAID canister with 8 9 gig drives attached, configured as RAID5 with hot spare. To the 2940-UW, the "drive" looks like one large 53 gig disk. NetBSD has not been as stable as we had hoped, and I wanted to put the FreeBSD machine in its place. When I try to mount the array like so: mount /dev/sd0a /mntwhatever I get this error: sd0: Can't deal with 201 bytes logical blocks and obviously the mount doesn't happen. My questions: 1) why is this happening? 2) what are my options (can we tweak some code to get this functional, NetBSD can handle it, why can't we? Am I going to have to backup my array and format it? Can FreeBSD even handle SCSI drives this large?) 3) Are NetBSD filesystems compatible with FreeBSD(all sources report that it is)??? Any information would be greatly appreciated. -J To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 18:27:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA05601 for freebsd-stable-outgoing; Thu, 3 Dec 1998 18:27:18 -0800 (PST) (envelope-from owner-freebsd-stable@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 SAA05590 for ; Thu, 3 Dec 1998 18:27:06 -0800 (PST) (envelope-from gaylord@gaylord.async.vt.edu) Received: (from gaylord@localhost) by gaylord.async.vt.edu (8.8.8/8.8.5) id VAA26325 for freebsd-stable@freebsd.org; Thu, 3 Dec 1998 21:26:43 -0500 (EST) From: Clark Gaylord Message-Id: <199812040226.VAA26325@gaylord.async.vt.edu> Subject: Doc on upgrading from 2.2 to 3.0 To: freebsd-stable@FreeBSD.ORG Date: Thu, 3 Dec 1998 21:26:43 -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-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just moved my CVSUP to 3.0 from 2.2-STABLE. Is there a document describing the appropriate upgrade procedure. I know there is some aout->elf issue; anything else. Will make aouttoelf (or whatever) do this? Many thanks. Clark -- Clark K. Gaylord Blacksburg, Virginia USA cgaylord@vt.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 18:46:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07476 for freebsd-stable-outgoing; Thu, 3 Dec 1998 18:46:29 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from ctcdist.com. ([199.3.192.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07465 for ; Thu, 3 Dec 1998 18:46:25 -0800 (PST) (envelope-from placej@ctcdist.com) Received: (from placej@localhost) by ctcdist.com. (8.8.8/8.8.7) id VAA01868; Thu, 3 Dec 1998 21:46:08 -0500 (EST) (envelope-from placej) Message-ID: <19981203214607.A1837@ctcdist.com> Date: Thu, 3 Dec 1998 21:46:07 -0500 From: "John C. Place" To: spork , freebsd-stable@FreeBSD.ORG Subject: Re: rc.shutdown and init Reply-To: "John C. Place" Mail-Followup-To: spork , freebsd-stable@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from spork on Thu, Dec 03, 1998 at 04:40:26PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 03, 1998 at 04:40:26PM -0500, spork wrote: > Oops, nevermind, I checked out init, and I see the change was committed > late August. The thing that threw me was that the /etc/shutdown.rc > example exists only in the 3.0 branch. Could someone backport that? > Instead of waiting why not hack in a call to it yourself fot the time being? That is teh beautiful thing about open source... don't like it? change it. L8er John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 19:09:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA10235 for freebsd-stable-outgoing; Thu, 3 Dec 1998 19:09:53 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA10230 for ; Thu, 3 Dec 1998 19:09:50 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id WAA12305; Thu, 3 Dec 1998 22:09:34 -0500 (EST) Date: Thu, 3 Dec 1998 22:09:33 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "John C. Place" cc: freebsd-stable@FreeBSD.ORG Subject: Re: rc.shutdown and init In-Reply-To: <19981203214607.A1837@ctcdist.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 3 Dec 1998, John C. Place wrote: > Instead of waiting why not hack in a call to it yourself fot the time being? > That is teh beautiful thing about open source... don't like it? change it. Well, I found out the init change is already there, it's just that the /etc/rc.shutdown file only exists in the 3.0 branch. It would be nice to have it in -stable to save a few people some head scratching and to kind of point out that the feature does indeed exist in any stable snaps (and 2.2.8) after mid August. I'll just contact the committer directly... Thanks, Charles >L8er > John > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 3 21:26:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA21502 for freebsd-stable-outgoing; Thu, 3 Dec 1998 21:26:35 -0800 (PST) (envelope-from owner-freebsd-stable@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 VAA21491 for ; Thu, 3 Dec 1998 21:26:31 -0800 (PST) (envelope-from gnb@bby.com.au) Received: (from daemon@localhost) by fw.bby.com.au (8.8.8/8.6.9) id QAA17851; Fri, 4 Dec 1998 16:25:44 +1100 (EST) Received: from melba.bby.com.au(192.43.186.1) via SMTP by fw.bby.com.au, id smtpd017849; Fri Dec 4 05:25:41 1998 Received: from lightning (lightning.bby.com.au [192.43.186.20]) by melba.bby.com.au (8.8.2/8.8.2) with ESMTP id QAA20654; Fri, 4 Dec 1998 16:25:48 +1100 (EST) Message-Id: <199812040525.QAA20654@melba.bby.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: stable@FreeBSD.ORG Cc: Mike Smith Cc: Paul Richards Subject: Re: HP NightDIRECTOR/100 Ether card In-reply-to: Your message of Tue, 01 Dec 1998 17:59:41 +1100. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Dec 1998 16:25:39 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks to the respondees. It turns out that this card is supported and works in 3.0 (at least) using the lnc device ("device lnc0" but ya gotta have PnP set up right and it turns up as lnc1 in the dmesg output). Dunno what I did wrong first time I tried it that led me to think it didn't work. Greg, somewhat red-faced. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 4 00:07:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06055 for freebsd-stable-outgoing; Fri, 4 Dec 1998 00:07:59 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from piggy.kharkiv.net (piggy.kharkiv.net [194.44.156.30]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06040 for ; Fri, 4 Dec 1998 00:07:41 -0800 (PST) (envelope-from news@piggy.kharkiv.net) Received: (from news@localhost) by piggy.kharkiv.net for ; ; Fri, 4 Dec 1998 10:07:10 +0200 (EET) (envelope-from news) To: freebsd-stable@FreeBSD.ORG Subject: Re: FAQ Date: Fri, 04 Dec 1998 10:07:08 +0200 Message-ID: <3667982C.15FB@kharkiv.net> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Mailer: Mozilla 3.01 (X11; I; AIX 2) X-Via: News-To-Mail v1.0 From: "Newsgate" Reply-To: "Vadim V. Chepkov" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --> Use Reply-To: for answer to "Vadim V. Chepkov" Jordan K. Hubbard wrote: > > > I downloaded 2.2.8-RELEASE and installed doc/* distribution. > > In /usr/share/doc/FAQ/ I've got documents on Spanish. Why? > > "Oops." Damn - it looks like that fix for this never made it > into -stable. :( > > If you rebuild /usr/share/doc/FAQ from sources, this problem > should go away. > Hello! But I have not FAQ in sources :-( (I cvsuped today with stable-supfile). su-2.01# ls -l /usr/src/share/doc/ total 6 -rw-r--r-- 1 root wheel 345 May 26 1997 Makefile drwxr-xr-x 5 root wheel 512 Dec 4 09:58 iso drwxr-xr-x 15 root wheel 512 Dec 4 09:58 papers drwxr-xr-x 18 root wheel 512 Dec 4 09:59 psd drwxr-xr-x 17 root wheel 512 Dec 4 09:59 smm drwxr-xr-x 15 root wheel 512 Dec 4 09:59 usd P.S. Why I already got this strange message. To: iSMTP@DCSG-SIN01@Servers[] Cc: Subject: FAQ Message not delivered to recipients below. Press F1 for help with VNM error codes. VNM3043: Ford Leu@Services@DCTW-TPE VNM3043 -- MAILBOX IS FULL -- Kind regards, Vadim V. Chepkov ------------------------------------------------------ Vadim V. Chepkov, Kharkiv State Polytechnic University 13 Frunze Str., Kharkiv, Ukraine, 310002 phone: +380 572 400478 fax: +380 572 400592 e-mail: vvc@kharkiv.net http://www.kharkiv.net/~vvc ------------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 4 07:09:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA09962 for freebsd-stable-outgoing; Fri, 4 Dec 1998 07:09:19 -0800 (PST) (envelope-from owner-freebsd-stable@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 HAA09950 for ; Fri, 4 Dec 1998 07:09:11 -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.053 #1) id 0zlwqj-0001q7-00 for freebsd-stable@freebsd.org; Fri, 4 Dec 1998 17:08:53 +0200 From: Sheldon Hearn To: freebsd-stable@FreeBSD.ORG Subject: ATAPI CD-ROM detected but unusable Date: Fri, 04 Dec 1998 17:08:53 +0200 Message-ID: <7074.912784133@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi folks, I can't use cdcontrol to play audio CD's. I'm experiencing the following: # cdcontrol -f wcd0c Compact Disc Control utility, version 2.0 Type `?' for command list cdcontrol> play cdcontrol: Input/output error I've statically compiled ATAPI support into my kernel. Although the CD-ROM is detected while probing wdc1, the kernel doesn't spit out anything about wcd0 as I expected, having had this working on another machine. I'm worried that the significant difference between this machine and the other is that I've enabled PnP support for my sound card. The CD-ROM runs off the mainboard's seconday controller and the sound card doesn't offer a controller, so there's no conflict there. Any help would be appreciated. Bits of dmesg output and kernel config follow. Thanks, Sheldon. kernel config bits: -------- [...] options FFS #Fast filesystem options NFS #Network filesystem options MFS #Memory filesystem options ATAPI #Enable ATAPI support for IDE bus options ATAPI_STATIC #Don't do it as an LKM options PROCFS #Process filesystem options MSDOSFS #MS DOS filesystem [...] controller isa0 controller pci0 controller pnp0 # this is required for PnP support controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x80ff80ff vector wdintr controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0x80ff80ff vector wdintr controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk wd0 at wdc0 drive 0 disk wd2 at wdc1 drive 0 disk wcd0 disk fd0 at fdc0 drive 0 dmesg bits: -------- [...] Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 [...] Probing for PnP devices: CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff pcm1 (SB16pnp sn 0xffffffff) at 0x220 irq 5 drq 1 flags 0x13 id 13 Probing for devices on the ISA bus: [...] wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-32 wd0: 1668MB (3417120 sectors), 3390 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 flags 0x80ff80ff on isa wdc1: unit 0 (wd2): , 32-bit, multi-block-32 wd2: 1668MB (3417120 sectors), 3390 cyls, 16 heads, 63 S/T, 512 B/S wdc1: unit 1 (atapi): , removable, accel, dma, iordis fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 4 08:02:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16271 for freebsd-stable-outgoing; Fri, 4 Dec 1998 08:02:04 -0800 (PST) (envelope-from owner-freebsd-stable@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 IAA16222 for ; Fri, 4 Dec 1998 08:01:50 -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.053 #1) id 0zlxfZ-000049-00 for freebsd-stable@freebsd.org; Fri, 4 Dec 1998 18:01:25 +0200 From: Sheldon Hearn To: freebsd-stable@FreeBSD.ORG Subject: Re: ATAPI CD-ROM detected but unusable In-reply-to: Your message of "Fri, 04 Dec 1998 17:08:53 +0200." <7074.912784133@axl.noc.iafrica.com> Date: Fri, 04 Dec 1998 18:01:25 +0200 Message-ID: <256.912787285@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 04 Dec 1998 17:08:53 +0200, Sheldon Hearn wrote: > cdcontrol> play > cdcontrol: Input/output error > > I've statically compiled ATAPI support into my kernel. Following up: I've just tried compiling ATAPI support as a module, instead of linking it into the kernel statically. When I do ``modload /lkm/atapi_mod.o'' and try to use cdcontrol as before , I get "no disc in drive /dev/rwcd1c" instead of "Input/output error". As before, any help would be appreciated. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 4 08:31:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20601 for freebsd-stable-outgoing; Fri, 4 Dec 1998 08:31:16 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dfw-ix7.ix.netcom.com (dfw-ix7.ix.netcom.com [206.214.98.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20595 for ; Fri, 4 Dec 1998 08:31:15 -0800 (PST) (envelope-from kjhmdjd@ix.netcom.com) Received: (from smap@localhost) by dfw-ix7.ix.netcom.com (8.8.4/8.8.4) id KAA12223 for ; Fri, 4 Dec 1998 10:30:57 -0600 (CST) Received: from chf-il9-95.ix.netcom.com(207.220.183.95) by dfw-ix7.ix.netcom.com via smap (V1.3) id rma012084; Fri Dec 4 10:30:38 1998 Message-ID: <001f01be1fa3$b8af9e80$0405a8c0@p400> From: "kjh" To: Subject: simple (?dumb) q. about ports Date: Fri, 4 Dec 1998 10:28:20 -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 4.72.3155.0 X-Mimeole: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are there separate ports trees for 2.2.7-STABLE and - CURRENT or RELEASE? The Handbook seems to indicate that the cvsup versioning tags don't apply to the ports-all collection, but the freebsd.org web site has browsing links for separate ports collections for STABLE and CURRENT. I ask 'cause I'm using 2.2.7-STABLE, and cvsup'ing regularly, but ports via ftp seem to have a *very* high rate of compile/install failures, including but not limited to ELF v. a.out problems. If I've not read something carefully enough, please point me in the right direction! Thanks for your time. Kurt Hopfensperger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 4 08:49:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA22356 for freebsd-stable-outgoing; Fri, 4 Dec 1998 08:49:35 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from clem.mscd.edu (clem.mscd.edu [147.153.1.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA22351 for ; Fri, 4 Dec 1998 08:49:31 -0800 (PST) (envelope-from baram@mscd.edu) Received: from localhost by clem.mscd.edu (PMDF V5.1-10 #D3122) with SMTP id <0F3G002019E2E3@clem.mscd.edu> for freebsd-stable@FreeBSD.ORG; Fri, 4 Dec 1998 09:49:14 -0700 (MST) Date: Fri, 04 Dec 1998 09:49:14 -0700 (MST) From: SirSparc Subject: Re: ATAPI CD-ROM detected but unusable In-reply-to: <7074.912784133@axl.noc.iafrica.com> To: Sheldon Hearn Cc: freebsd-stable@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, It looks like your cddrive is on wcd1c instead of wcd0c. Make the appropriate change to your kernel config and recompile, also one weird thing i noticed about cdcontrol is that on some occasions you *need* to specify the track # explicitly, like cdcontrol> play 1 Later.. On Fri, 4 Dec 1998, Sheldon Hearn wrote: > > Hi folks, > > I can't use cdcontrol to play audio CD's. I'm experiencing the > following: > > # cdcontrol -f wcd0c > Compact Disc Control utility, version 2.0 > Type `?' for command list > > cdcontrol> play > cdcontrol: Input/output error > > I've statically compiled ATAPI support into my kernel. Although the > CD-ROM is detected while probing wdc1, the kernel doesn't spit out > anything about wcd0 as I expected, having had this working on another > machine. > > I'm worried that the significant difference between this machine and the > other is that I've enabled PnP support for my sound card. The CD-ROM > runs off the mainboard's seconday controller and the sound card doesn't > offer a controller, so there's no conflict there. > > Any help would be appreciated. Bits of dmesg output and kernel config > follow. > > Thanks, > Sheldon. > > kernel config bits: > -------- > [...] > options FFS #Fast filesystem > options NFS #Network filesystem > options MFS #Memory filesystem > options ATAPI #Enable ATAPI support for IDE bus > options ATAPI_STATIC #Don't do it as an LKM > options PROCFS #Process filesystem > options MSDOSFS #MS DOS filesystem > [...] > controller isa0 > controller pci0 > controller pnp0 # this is required for PnP support > controller wdc0 at isa? port "IO_WD1" bio irq 14 flags 0x80ff80ff vector wdintr > controller wdc1 at isa? port "IO_WD2" bio irq 15 flags 0x80ff80ff vector wdintr > controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr > > disk wd0 at wdc0 drive 0 > disk wd2 at wdc1 drive 0 > disk wcd0 > disk fd0 at fdc0 drive 0 > > dmesg bits: > -------- > [...] > Probing for devices on PCI bus 0: > chip0 rev 2 on pci0:0:0 > chip1 rev 1 on pci0:7:0 > chip2 rev 0 on pci0:7:1 > [...] > Probing for PnP devices: > CSN 1 Vendor ID: CTL00f0 [0xf0008c0e] Serial 0xffffffff > pcm1 (SB16pnp sn 0xffffffff) at 0x220 irq 5 drq 1 flags 0x13 id 13 > Probing for devices on the ISA bus: > [...] > wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa > wdc0: unit 0 (wd0): , 32-bit, multi-block-32 > wd0: 1668MB (3417120 sectors), 3390 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 flags 0x80ff80ff on isa > wdc1: unit 0 (wd2): , 32-bit, multi-block-32 > wd2: 1668MB (3417120 sectors), 3390 cyls, 16 heads, 63 S/T, 512 B/S > wdc1: unit 1 (atapi): , removable, accel, dma, iordis > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 4 09:34:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28461 for freebsd-stable-outgoing; Fri, 4 Dec 1998 09:34:22 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from jason04.u.washington.edu (jason04.u.washington.edu [140.142.78.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28456 for ; Fri, 4 Dec 1998 09:34:21 -0800 (PST) (envelope-from jcwells@u.washington.edu) Received: from saul5.u.washington.edu (root@saul5.u.washington.edu [140.142.83.3]) by jason04.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA15250; Fri, 4 Dec 1998 09:34:06 -0800 Received: from S8-37-26.student.washington.edu (S8-37-26.student.washington.edu [128.208.37.26]) by saul5.u.washington.edu (8.8.4+UW97.07/8.8.4+UW98.06) with ESMTP id JAA00120; Fri, 4 Dec 1998 09:34:05 -0800 (PST) Date: Fri, 4 Dec 1998 09:33:36 -0800 (PST) From: "Jason C. Wells" X-Sender: jason@s8-37-26.student.washington.edu Reply-To: "Jason C. Wells" To: kjh cc: Freebsd-Stable@FreeBSD.ORG Subject: Re: simple (?dumb) q. about ports In-Reply-To: <001f01be1fa3$b8af9e80$0405a8c0@p400> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 4 Dec 1998, kjh wrote: >I ask 'cause I'm using 2.2.7-STABLE, and cvsup'ing regularly, but ports via >ftp seem to have a *very* high rate of compile/install failures, including >but not limited to ELF v. a.out problems. > >If I've not read something carefully enough, please point me in the right >direction! Thanks for your time. There is one sort of "gotcha". Read http://www.freebsd.org/pors/ closely for "upgrade kits". This might help. I don't know the full details but the include files in the upgrade kits are rather simple. If you don't go to that website often, then you might not have seen this. HTH! Catchya Later, | UW Mechanical Engineering Jason Wells | http://weber.u.washington.edu/~jcwells/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 4 10:06:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03241 for freebsd-stable-outgoing; Fri, 4 Dec 1998 10:06:08 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from mail.esigroup.com (esiwg.esigroup.com [205.218.124.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03233 for ; Fri, 4 Dec 1998 10:06:06 -0800 (PST) (envelope-from RHall@esigroup.com) Received: by mail.esigroup.com with Internet Mail Service (5.5.1960.3) id ; Fri, 4 Dec 1998 11:59:14 -0600 Message-ID: <2C10B557AEBDD011872500A0C933CDDB4D8747@mail.esigroup.com> From: Roger Hall To: freebsd-stable@FreeBSD.ORG Subject: FW: Network help Date: Fri, 4 Dec 1998 11:59:13 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.1960.3) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In /stand/sysinstall I configured the network with an IP address of > 192.30.2.125 (which is an internal virtual lan), a gateway of > 205.218.124.1 and Name Server 205.218.124.2. The 205 addresses are > public internet address. > > In /etc/rc.conf: > network_interfaces="ep0 sl0 lp0" > ifconfig_ep0="inet 192.30.2.125 netmask 255.255.255.0" > ifconfig_sl0="inet 192.30.2.125 netmask 255.255.255.0" > ifconfig_sl0="inet 192.30.2.125 netmask 255.255.255.0" (that's right, > two sl's) > ifconfig_lo0="inet 192.30.2.125 netmask 255.255.255.0" > > defaultrouter="205.218.124.1" > > But netstat -r is very short: > > localhost localhost > 192.30.2 link#2 > > I can ping any 192 address, but 205 is unreachable. Obviously there is > no route, but why, and how to fix? And isn't that route supposed to > say "192.30.2.0"? > > When I try "route add default gw" as described on page 319 of the > complete Freebsd, I get: > > route: bad address: gw > > TIA! > > Roger Hall > Webmaster > http://www.esigroup.com > 501.975.0840.296 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 4 13:42:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA24050 for freebsd-stable-outgoing; Fri, 4 Dec 1998 13:42:57 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA24045 for ; Fri, 4 Dec 1998 13:42:54 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id WAA18380; Fri, 4 Dec 1998 22:41:46 +0100 (CET) Message-ID: <19981204224145.A18363@foobar.franken.de> Date: Fri, 4 Dec 1998 22:41:45 +0100 From: Harold Gutch To: Sheldon Hearn , freebsd-stable@FreeBSD.ORG Subject: Re: ATAPI CD-ROM detected but unusable References: <7074.912784133@axl.noc.iafrica.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <7074.912784133@axl.noc.iafrica.com>; from Sheldon Hearn on Fri, Dec 04, 1998 at 05:08:53PM +0200 X-Organisation: BatmanSystemDistribution X-Mission: To free the world from the Penguin Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 04, 1998 at 05:08:53PM +0200, Sheldon Hearn wrote: [...] > disk wcd0 ^^^^ That should rather be "device wcd0". -- bye, logix Sleep is an abstinence syndrome wich occurs due to lack of caffein. Wed Mar 4 04:53:33 CET 1998 #unix, ircnet To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 4 14:52:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA02750 for freebsd-stable-outgoing; Fri, 4 Dec 1998 14:52:27 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA02745 for ; Fri, 4 Dec 1998 14:52:23 -0800 (PST) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from markab (markab [128.130.111.33]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id XAA22654; Fri, 4 Dec 1998 23:48:19 +0100 (MET) Date: Fri, 4 Dec 1998 23:48:46 +0100 (MET) From: Gerald Pfeifer To: Matt Behrens cc: "John C. Place" , nunnari , freebsd-stable@FreeBSD.ORG Subject: Re: tcsh (was Re: g++ -v --> 2.7.2.1 ???) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 30 Nov 1998, Matt Behrens wrote: > tcsh is in the ports for the hopeless csh devotees though. :) (I have > one on my system...) Problem is, the one responsible for the tcsh package doesn't seem to care. (http://www.freebsd.org/cgi/query-pr-summary.cgi?query) You'll have to compile it by yourself, if you ever decide to set LANG or LC_TYPE. Gerald -- Gerald Pfeifer (Jerry) Vienna University of Technology pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 5 09:01:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21904 for freebsd-stable-outgoing; Sat, 5 Dec 1998 09:01:55 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pwrtc.com (pwrtc.com [206.230.144.34]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21896 for ; Sat, 5 Dec 1998 09:01:53 -0800 (PST) (envelope-from pazuzu@amphigory.com) Received: from legba.pwrtc.com (legba.pwrtc.com [206.230.144.223]) by pwrtc.com (8.8.7/8.8.5) with ESMTP id MAA05268 for ; Sat, 5 Dec 1998 12:02:03 -0500 (EST) Received: from localhost (root@localhost) by legba.pwrtc.com (8.8.5/8.8.5) with SMTP id MAA12701 for ; Sat, 5 Dec 1998 12:09:19 -0500 (EST) Message-Id: <199812051709.MAA12701@legba.pwrtc.com> X-SMTP: hello erzulie from pazuzu@amphigory.com server @erzulie ip 192.168.1.2 X-Sender: pazuzu@legba (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0 Date: Sat, 05 Dec 1998 12:01:43 -0500 To: freebsd-stable@FreeBSD.ORG From: "Jon M. Craig (Pazuzu)" Subject: Problem trying to make buildworld from 2.2.2 -> 2.2.8 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been running 2.2.2 for a number of years now (how ever long it's been out :) ) and with the release of 2.2.8 being labelled as "fina" I decided to upgrade. I used CVSup to synch my source, and ran make buildworld... No problem for about 2 hours, then, while running this command: gperf -p -j1 -i 1 -g -o -t -G -N is_reserved_word -k1,3,$ /usr/src/gnu/usr.bin/cc/cc_tools/../../../../contrib/gcc/c-parse.gperf > c-gperf.h Make dies with: Bad system call - core dumped *** Error code 140 Stop. *** Error code 1 Stop ... None of my filesystems are full, the system has been rock-solid reliable for years, and I have no clue what is going on here. Any ideas? --- Fr. Pazuzu 7:7:9 - Co-Owner of Amphigory, The Gothic & Magickal Emporium Editor, Sentence ov Desire Email: pazuzu@amphigory.com WWW: http://www.amphigory.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 5 09:07:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA22462 for freebsd-stable-outgoing; Sat, 5 Dec 1998 09:07:35 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22457 for ; Sat, 5 Dec 1998 09:07:32 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.7) with SMTP id RAA05541 for ; Sat, 5 Dec 1998 17:07:29 GMT (envelope-from arg@arg1.demon.co.uk) Date: Sat, 5 Dec 1998 17:06:54 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: stable@FreeBSD.ORG Subject: Problem with CD9660 root on -stable Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1577300402-912877614=:5450" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1577300402-912877614=:5450 Content-Type: TEXT/PLAIN; charset=US-ASCII I've been playing with CD root filesystem ('-C' at the boot prompt). All seems to be OK on SCSI systems, within the limited scope of my testing. However, using an IDE/ATAPI CDROM fails to mount the root filesystem. Having traced this a bit, I find that iso_get_ssector() [in sys/isofs/cd9660/cd9660_vfsops.c] is returning bogus results; my immediate problem can be fixed by hacking it to return zero always (disabling support for multi-session CDROMs). Digging a little deeper, it appears that the wdc driver implements CDIOREADTOCENTRYS but not the related CDIOREADTOCENTRY that is needed by iso_get_ssector(). This should still be OK - iso_get_sector() traps the error and simply assumes a single-session CD in this case - but unfortunately the error test is wrong (because it is calling the driver's ioctl entry point directly, the return value is zero or an errno value). The enclosed patch fixes the problem. --0-1577300402-912877614=:5450 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="cd9660.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: SW5kZXg6IGlzb2ZzL2NkOTY2MC9jZDk2NjBfdmZzb3BzLmMNCj09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT0NClJDUyBmaWxlOiAvY3VycmVudC9yZXBvc2l0b3J5 L3NyYy9zeXMvaXNvZnMvY2Q5NjYwL2NkOTY2MF92ZnNvcHMuYyx2DQpyZXRy aWV2aW5nIHJldmlzaW9uIDEuMTUuNC4yDQpkaWZmIC1jIC1yMS4xNS40LjIg Y2Q5NjYwX3Zmc29wcy5jDQoqKiogY2Q5NjYwX3Zmc29wcy5jCTE5OTgvMDEv MDIgMTY6NDY6MTUJMS4xNS40LjINCi0tLSBjZDk2NjBfdmZzb3BzLmMJMTk5 OC8xMi8wNSAxNzowNDowNg0KKioqKioqKioqKioqKioqDQoqKiogMTI1LDEz NyAqKioqDQogIAlpZiAoaW9jdGxwID09IE5VTEwpDQogIAkJcmV0dXJuIDA7 DQogIA0KISAJaWYgKGlvY3RscChkZXYsIENESU9SRUFEVE9DSEVBREVSLCAo Y2FkZHJfdCkmaCwgRlJFQUQsIHApID09IC0xKQ0KICAJCXJldHVybiAwOw0K ICANCiAgCWZvciAoaSA9IGguZW5kaW5nX3RyYWNrOyBpID49IDA7IGktLSkg ew0KICAJCXQuYWRkcmVzc19mb3JtYXQgPSBDRF9MQkFfRk9STUFUOw0KICAJ CXQudHJhY2sgPSBpOw0KISAJCWlmIChpb2N0bHAoZGV2LCBDRElPUkVBRFRP Q0VOVFJZLCAoY2FkZHJfdCkmdCwgRlJFQUQsIHApID09IC0xKQ0KICAJCQly ZXR1cm4gMDsNCiAgCQlpZiAoKHQuZW50cnkuY29udHJvbCAmIDQpICE9IDAp DQogIAkJCS8qIGZvdW5kIGEgZGF0YSB0cmFjayAqLw0KLS0tIDEyNSwxMzcg LS0tLQ0KICAJaWYgKGlvY3RscCA9PSBOVUxMKQ0KICAJCXJldHVybiAwOw0K ICANCiEgCWlmIChpb2N0bHAoZGV2LCBDRElPUkVBRFRPQ0hFQURFUiwgKGNh ZGRyX3QpJmgsIEZSRUFELCBwKSAhPSAwKQ0KICAJCXJldHVybiAwOw0KICAN CiAgCWZvciAoaSA9IGguZW5kaW5nX3RyYWNrOyBpID49IDA7IGktLSkgew0K ICAJCXQuYWRkcmVzc19mb3JtYXQgPSBDRF9MQkFfRk9STUFUOw0KICAJCXQu dHJhY2sgPSBpOw0KISAJCWlmIChpb2N0bHAoZGV2LCBDRElPUkVBRFRPQ0VO VFJZLCAoY2FkZHJfdCkmdCwgRlJFQUQsIHApICE9IDApDQogIAkJCXJldHVy biAwOw0KICAJCWlmICgodC5lbnRyeS5jb250cm9sICYgNCkgIT0gMCkNCiAg CQkJLyogZm91bmQgYSBkYXRhIHRyYWNrICovDQo= --0-1577300402-912877614=:5450-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 5 15:06:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22272 for freebsd-stable-outgoing; Sat, 5 Dec 1998 15:06:26 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from dfw-ix9.ix.netcom.com (dfw-ix9.ix.netcom.com [206.214.98.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22265 for ; Sat, 5 Dec 1998 15:06:22 -0800 (PST) (envelope-from kjhmdjd@ix.netcom.com) Received: (from smap@localhost) by dfw-ix9.ix.netcom.com (8.8.4/8.8.4) id RAA01780 for ; Sat, 5 Dec 1998 17:06:17 -0600 (CST) Received: from chf-il5-128.ix.netcom.com(207.220.181.128) by dfw-ix9.ix.netcom.com via smap (V1.3) id rma001755; Sat Dec 5 17:05:46 1998 Message-ID: <001301be20a4$17d34640$0405a8c0@p400> From: "kjh" To: Subject: Re-phrase of simple (?dumb) q. about ports Date: Sat, 5 Dec 1998 17:07:48 -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 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Let me re-phrase my prior question: On ftp.freebsd.org, there are 4 ports directories: ports-3.0 ports ports-stable ports-current or something like that. BUT, cvsup will only allow a tag of: ports-all tag=. and won't allow you to specify which cvs branch to get ports out of; if you specify a tag such as REL_ENG_2.2 for ports, the sample file says it will delete your existing ports tree. So, my question: How do I cvsup a "stable" ports collection to go with my 2.2.8-STABLE system? Or doesn't it matter, or do I have to just ftp the port-stable directories, or ??? I can't find the answer to this in the handbook, etc. Thanks for your time! Kurt Hopfensperger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 5 15:16:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22905 for freebsd-stable-outgoing; Sat, 5 Dec 1998 15:16:30 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phluffy.fks.bt (net25-cust202.pdx.wantweb.net [24.236.25.202]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22899 for ; Sat, 5 Dec 1998 15:16:26 -0800 (PST) (envelope-from myke@ees.com) Received: from localhost (myke@localhost) by phluffy.fks.bt (8.8.8/8.8.8) with ESMTP id PAA01773; Sat, 5 Dec 1998 15:16:13 -0800 (PST) (envelope-from myke@ees.com) Date: Sat, 5 Dec 1998 15:16:13 -0800 (PST) From: Mike Holling X-Sender: myke@phluffy.fks.bt To: kjh cc: Freebsd-Stable@FreeBSD.ORG Subject: Re: Re-phrase of simple (?dumb) q. about ports In-Reply-To: <001301be20a4$17d34640$0405a8c0@p400> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, my question: How do I cvsup a "stable" ports collection to go with my > 2.2.8-STABLE system? Or doesn't it matter, or do I have to just ftp the > port-stable directories, or ??? I can't find the answer to this in the > handbook, etc. Thanks for your time! There is only one ports collection that is used for all versions of FreeBSD. The other directories are just snapshots of the ports tree when the release was made. This is documented somewhere, maybe in the cvsup tutorial? - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 5 15:24:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23554 for freebsd-stable-outgoing; Sat, 5 Dec 1998 15:24:51 -0800 (PST) (envelope-from owner-freebsd-stable@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 PAA23549 for ; Sat, 5 Dec 1998 15:24:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by zippy.cdrom.com (8.9.1/8.9.1) with ESMTP id PAA03636; Sat, 5 Dec 1998 15:24:44 -0800 (PST) To: Andrew Gordon cc: stable@FreeBSD.ORG Subject: Re: Problem with CD9660 root on -stable In-reply-to: Your message of "Sat, 05 Dec 1998 17:06:54 GMT." Date: Sat, 05 Dec 1998 15:24:44 -0800 Message-ID: <3632.912900284@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Committed, thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 5 16:05:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA28106 for freebsd-stable-outgoing; Sat, 5 Dec 1998 16:05:38 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA28077 for ; Sat, 5 Dec 1998 16:05:36 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id RAA02255; Sat, 5 Dec 1998 17:05:20 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199812060005.RAA02255@freeway.dcfinc.com> Subject: Re: Re-phrase of simple (?dumb) q. about ports In-Reply-To: from Mike Holling at "Dec 5, 98 03:16:13 pm" To: myke@ees.com (Mike Holling) Date: Sat, 5 Dec 1998 17:05:20 -0700 (MST) Cc: kjhmdjd@ix.netcom.com, Freebsd-Stable@FreeBSD.ORG Reply-to: chad@DCFinc.com X-Mailer: ELM [version 2.4ME+ PL40 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I recall, Mike Holling wrote: > > So, my question: How do I cvsup a "stable" ports collection to go with my > > 2.2.8-STABLE system? Or doesn't it matter, or do I have to just ftp the > > port-stable directories, or ??? I can't find the answer to this in the > > handbook, etc. Thanks for your time! > > There is only one ports collection that is used for all versions of > FreeBSD. The other directories are just snapshots of the ports tree when > the release was made. This is documented somewhere, maybe in the cvsup > tutorial? But the question is still a good one. If a machine is running 2.2.7 (for example), it makes sense to cvsup the ports collection as of the time that version was released. Elsewise, you're gonna run into ELF vs a.out and other such confusions. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org chad@anasazi.com larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 5 17:05:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA03155 for freebsd-stable-outgoing; Sat, 5 Dec 1998 17:05:06 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from phluffy.fks.bt (net25-cust202.pdx.wantweb.net [24.236.25.202]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA03149 for ; Sat, 5 Dec 1998 17:05:03 -0800 (PST) (envelope-from myke@ees.com) Received: from localhost (myke@localhost) by phluffy.fks.bt (8.8.8/8.8.8) with ESMTP id RAA01921; Sat, 5 Dec 1998 17:04:41 -0800 (PST) (envelope-from myke@ees.com) Date: Sat, 5 Dec 1998 17:04:41 -0800 (PST) From: Mike Holling X-Sender: myke@phluffy.fks.bt To: chad@DCFinc.com cc: kjhmdjd@ix.netcom.com, Freebsd-Stable@FreeBSD.ORG Subject: Re: Re-phrase of simple (?dumb) q. about ports In-Reply-To: <199812060005.RAA02255@freeway.dcfinc.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > But the question is still a good one. If a machine is running 2.2.7 > (for example), it makes sense to cvsup the ports collection as of the > time that version was released. > > Elsewise, you're gonna run into ELF vs a.out and other such > confusions. I've been cvsupping ports on my 2.2.6 box for a while without incident. I believe the makefiles check to see what version of FreeBSD you're running (3.x vs. 2.x), though I haven't poked at them much. - Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 5 17:23:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA04428 for freebsd-stable-outgoing; Sat, 5 Dec 1998 17:23:05 -0800 (PST) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from cerebus.nectar.com (nectar-gw.nectar.com [204.0.249.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA04423 for ; Sat, 5 Dec 1998 17:23:03 -0800 (PST) (envelope-from nectar@nectar.com) Received: (from smap@localhost) by cerebus.nectar.com (8.9.1/8.9.1) id TAA16913; Sat, 5 Dec 1998 19:22:50 -0600 (CST) (envelope-from nectar@nectar.com) Received: from spawn.nectar.com(10.0.0.101) by cerebus.nectar.com via smap (V2.1) id xma016911; Sat, 5 Dec 98 19:22:47 -0600 Received: from spawn.nectar.com (localhost [127.0.0.1]) by spawn.nectar.com (8.9.1/8.9.1) with ESMTP id TAA56506; Sat, 5 Dec 1998 19:22:47 -0600 (CST) (envelope-from nectar@spawn.nectar.com) Message-Id: <199812060122.TAA56506@spawn.nectar.com> X-Mailer: exmh version 2.0.2 2/24/98 X-PGP-RSAfprint: 00 F9 E6 A2 C5 4D 0A 76 26 8B 8B 57 73 D0 DE EE X-PGP-RSAkey: http://www.nectar.com/nectar-pgp262.txt From: Jacques Vidrine In-reply-to: <199812060005.RAA02255@freeway.dcfinc.com> References: <199812060005.RAA02255@freeway.dcfinc.com> Subject: Re: Re-phrase of simple (?dumb) q. about ports Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii To: chad@DCFinc.com cc: myke@ees.com (Mike Holling), kjhmdjd@ix.netcom.com, Freebsd-Stable@FreeBSD.ORG Date: Sat, 05 Dec 1998 19:22:47 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 5 December 1998 at 17:05, "Chad R. Larson" wrote: > But the question is still a good one. If a machine is running 2.2.7 > (for example), it makes sense to cvsup the ports collection as of the > time that version was released. > > Elsewise, you're gonna run into ELF vs a.out and other such > confusions. Not true. In fact, quite the opposite. The ports tree at the time of 2.2.7, say, may have many ports that no longer function do to changes in the applications. Often old versions don't hang around, for example. When you CVSup the ports collection, you always want the head revision. Ports should work on both a.out and ELF systems. If they don't, they are broken. Jacques Vidrine / n@nectar.com / nectar@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message