From owner-freebsd-stable Sun Dec 5 1: 2:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id A1CDF1543A for ; Sun, 5 Dec 1999 01:02:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA43285; Sun, 5 Dec 1999 01:01:46 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: leclaire@switzcpl.lib.in.us Cc: stable@FreeBSD.ORG Subject: Re: Anticipated release date for 3.4 In-reply-to: Your message of "Sat, 04 Dec 1999 20:39:10 EST." Date: Sun, 05 Dec 1999 01:01:46 -0800 Message-ID: <43282.944384506@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG That's a good question - I need to discuss the next update with some people at Walnut Creek CDROM. - Jordan > Just wondering, does this mean there will be a 3.3 Toolkit release soon? > > Andre > > > > Will be December 15th. The traditional code slush will go into effect > > on the 1st. November would be an excellent month for merging your > > changes, after which I'll be exercising my usual perogative of > > inspecting all potential changes with a more jaundiced eye. :) > > > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 2:14: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id E7F301503B; Sun, 5 Dec 1999 02:13:57 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:KcDgLg877IhVzcVTxd8WFWKbhI2uYTxt@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id TAA25546; Sun, 5 Dec 1999 19:11:51 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id TAA28697; Sun, 5 Dec 1999 19:16:42 +0900 (JST) Message-Id: <199912051016.TAA28697@zodiac.mech.utsunomiya-u.ac.jp> To: stable@freebsd.org Cc: sobomax@altavista.net, jhb@freebsd.org, ticso@cicely.de, Alexander@leidinger.net, Cejka Rudolf , yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problem with syscons in VESA mode In-reply-to: Your message of "Fri, 03 Dec 1999 13:32:45 +0200." <3847AA5D.5947E0EE@altavista.net> References: <19991203105728.A68768@dcse.fee.vutbr.cz> <3847AA5D.5947E0EE@altavista.net> Date: Sun, 05 Dec 1999 19:16:41 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I modified Cejka Rudolf's patch for -STABLE. Would people care to test this in your -STABLE boxes? I don't have a -STABLE test box handy right now. Kazu Index: syscons.c =================================================================== RCS file: /src/CVS/src/sys/dev/syscons/syscons.c,v retrieving revision 1.293.2.9 diff -u -r1.293.2.9 syscons.c --- syscons.c 1999/11/29 02:38:39 1.293.2.9 +++ syscons.c 1999/12/05 07:02:04 @@ -3368,11 +3368,12 @@ case 0x09: /* non-destructive tab */ mark_for_update(scp, scp->cursor_pos - scp->scr_buf); scp->cursor_pos += (8 - scp->xpos % 8u); - mark_for_update(scp, scp->cursor_pos - scp->scr_buf); if ((scp->xpos += (8 - scp->xpos % 8u)) >= scp->xsize) { scp->xpos = 0; scp->ypos++; + scp->cursor_pos = scp->scr_buf + scp->ypos * scp->xsize; } + mark_for_update(scp, scp->cursor_pos - scp->scr_buf); break; case 0x0a: /* newline, same pos */ >Cejka Rudolf wrote: > >> Kazutaka YOKOTA wrote (1999/12/03): >> > This strange behavior was reported several times in the past. It must >> > be related to screen update logic in syscons. But, I don't think we >> > have successfully fixed it at that time :-( >> > It's time to analyze the problem again... >> >> Yes. I know about this problem too but I have no time to fix and test >> it. Is anybody interested in bug reports? ;-) >> >> * Left margin moving to the right is related to the screen width not >> divisible by 8 and an use of tabulators at the end of line after the >> last valid tab position. So the same problem could be seen for >> example with screen width 90, which is accessible for all >> -current users: Let's suppose that cursor range is 0..89: If the >> cursor is on 80..87, it will move to position 88 and everything is ok. >> If the cursor is on 88..89, the position is calculated properly (you >> can switch to another console then return and cursor will be on >> the right position on column 0), but cursor is moved incorrectly >> on column 8 on the next line and next lines are moved to the left too >> until you switch between consoles. >> I think the fix should be trivial (syscons.c,v 1.327) - but it is >> speculated right now without testing: >> >> -- >> *** syscons.c Sun Nov 28 15:29:28 1999 >> --- /tmp/syscons.c Fri Dec 3 10:28:59 1999 >> *************** >> *** 2946,2956 **** >> [...] > >Thanks! It seems fixed my problems with syscons. > >-Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 5:48: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 600C014EE3 for ; Sun, 5 Dec 1999 05:48:02 -0800 (PST) (envelope-from willwong@anime.ca) Received: from mail.anime.ca ([24.112.80.104]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991205134518.PLGT21594.mail.rdc3.on.home.com@mail.anime.ca> for ; Sun, 5 Dec 1999 05:45:18 -0800 Received: from localhost (willwong@localhost) by mail.anime.ca (8.9.3/8.9.3) with ESMTP id IAA92798 for ; Sun, 5 Dec 1999 08:47:17 -0500 (EST) (envelope-from willwong@anime.ca) Date: Sun, 5 Dec 1999 08:47:16 -0500 (EST) From: William Wong To: freebsd-stable@freebsd.org Subject: netgraph broken in stable? 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, While trying to compile a kernel with netgraph support I got the following: I had cvsup'd earlier today. My compile dir was clean, did a textbook kernel config. I also did a "touch opt_netgraph.h" just in case. cc -c -O -pipe -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf vers.c loading kernel ng_base.o: In function `ng_generic_msg': ng_base.o(.text+0x1513): undefined reference to `ng_unparse' ng_base.o(.text+0x16f7): undefined reference to `ng_parse' ng_base.o(.rodata+0x18): undefined reference to `ng_parse_typebuf_type' ng_base.o(.rodata+0x24): undefined reference to `ng_parse_hookbuf_type' ng_base.o(.rodata+0x30): undefined reference to `ng_parse_hookbuf_type' ng_base.o(.rodata+0x5c): undefined reference to `ng_parse_struct_type' ng_base.o(.rodata+0x7c): undefined reference to `ng_parse_pathbuf_type' ng_base.o(.rodata+0x88): undefined reference to `ng_parse_hookbuf_type' ng_base.o(.rodata+0x94): undefined reference to `ng_parse_hookbuf_type' ng_base.o(.rodata+0xb0): undefined reference to `ng_parse_struct_type' ng_base.o(.rodata+0xd0): undefined reference to `ng_parse_nodebuf_type' ng_base.o(.rodata+0xec): undefined reference to `ng_parse_struct_type' ng_base.o(.rodata+0x10c): undefined reference to `ng_parse_hookbuf_type' ng_base.o(.rodata+0x128): undefined reference to `ng_parse_struct_type' ng_base.o(.rodata+0x148): undefined reference to `ng_parse_nodebuf_type' ng_base.o(.rodata+0x154): undefined reference to `ng_parse_typebuf_type' ng_base.o(.rodata+0x160): undefined reference to `ng_parse_int32_type' ng_base.o(.rodata+0x16c): undefined reference to `ng_parse_int32_type' ng_base.o(.rodata+0x18c): undefined reference to `ng_parse_struct_type' ng_base.o(.rodata+0x1ac): undefined reference to `ng_parse_typebuf_type' ng_base.o(.rodata+0x1b8): undefined reference to `ng_parse_int32_type' ng_base.o(.rodata+0x1e0): undefined reference to `ng_parse_struct_type' ng_base.o(.rodata+0x200): undefined reference to `ng_parse_hookbuf_type' ng_base.o(.rodata+0x20c): undefined reference to `ng_parse_hookbuf_type' ng_base.o(.rodata+0x238): undefined reference to `ng_parse_struct_type' ng_base.o(.rodata+0x260): undefined reference to `ng_parse_array_type' ng_base.o(.rodata+0x288): undefined reference to `ng_parse_array_type' ng_base.o(.rodata+0x2b0): undefined reference to `ng_parse_array_type' ng_base.o(.rodata+0x2d0): undefined reference to `ng_parse_int32_type' ng_base.o(.rodata+0x2fc): undefined reference to `ng_parse_struct_type' ng_base.o(.rodata+0x348): undefined reference to `ng_parse_struct_type' ng_base.o(.rodata+0x368): undefined reference to `ng_parse_int32_type' ng_base.o(.rodata+0x394): undefined reference to `ng_parse_struct_type' ng_base.o(.rodata+0x488): undefined reference to `ng_parse_string_type' ng_base.o(.rodata+0x498): undefined reference to `ng_parse_ng_mesg_type' ng_base.o(.rodata+0x49c): undefined reference to `ng_parse_ng_mesg_type' ng_base.o(.rodata+0x4ac): undefined reference to `ng_parse_ng_mesg_type' ng_base.o(.rodata+0x4b0): undefined reference to `ng_parse_ng_mesg_type' ng_async.o(.rodata+0x4): undefined reference to `ng_parse_int8_type' ng_async.o(.rodata+0x10): undefined reference to `ng_parse_int16_type' ng_async.o(.rodata+0x1c): undefined reference to `ng_parse_int16_type' ng_async.o(.rodata+0x28): undefined reference to `ng_parse_int32_type' ng_async.o(.rodata+0x54): undefined reference to `ng_parse_struct_type' ng_async.o(.rodata+0x74): undefined reference to `ng_parse_int32_type' ng_async.o(.rodata+0x80): undefined reference to `ng_parse_int32_type' ng_async.o(.rodata+0x8c): undefined reference to `ng_parse_int32_type' ng_async.o(.rodata+0x98): undefined reference to `ng_parse_int32_type' ng_async.o(.rodata+0xa4): undefined reference to `ng_parse_int32_type' ng_async.o(.rodata+0xb0): more undefined references to `ng_parse_int32_type' follow ng_async.o(.rodata+0x144): undefined reference to `ng_parse_struct_type' ng_cisco.o(.rodata+0x4): undefined reference to `ng_parse_ipaddr_type' ng_cisco.o(.rodata+0x10): undefined reference to `ng_parse_ipaddr_type' ng_cisco.o(.rodata+0x34): undefined reference to `ng_parse_struct_type' ng_cisco.o(.rodata+0x54): undefined reference to `ng_parse_int32_type' ng_cisco.o(.rodata+0x60): undefined reference to `ng_parse_int32_type' ng_cisco.o(.rodata+0x90): undefined reference to `ng_parse_struct_type' ng_ppp.o(.rodata+0x9c): undefined reference to `ng_parse_int8_type' ng_ppp.o(.rodata+0xa8): undefined reference to `ng_parse_int8_type' ng_ppp.o(.rodata+0xb4): undefined reference to `ng_parse_int8_type' ng_ppp.o(.rodata+0xc0): undefined reference to `ng_parse_int16_type' ng_ppp.o(.rodata+0xcc): undefined reference to `ng_parse_int32_type' ng_ppp.o(.rodata+0xd8): undefined reference to `ng_parse_int32_type' ng_ppp.o(.rodata+0x11c): undefined reference to `ng_parse_struct_type' ng_ppp.o(.rodata+0x138): undefined reference to `ng_parse_fixedarray_type' ng_ppp.o(.rodata+0x158): undefined reference to `ng_parse_int16_type' ng_ppp.o(.rodata+0x164): undefined reference to `ng_parse_int8_type' ng_ppp.o(.rodata+0x170): undefined reference to `ng_parse_int8_type' ng_ppp.o(.rodata+0x17c): undefined reference to `ng_parse_int8_type' ng_ppp.o(.rodata+0x188): undefined reference to `ng_parse_int8_type' ng_wng_ppp.o(.ronpp.o(.rodata+0x2bc): undefinedparse_int32_type' ng_ppp.o(.rodata+0x2c8): undefined reference to `ng_parse_int32_tye' ng_ppp.o(.rodeference to `ng_parse_int32_type' ng_ppp.o(.rodata+0x2e0): undefined refppp.o(.rodata+0x3a8): undefierence to `ng_par ------------------------------------------- William Wong Edirol on IRC EFNET willwong@anime.ca ANIME...MANGA...MIDI...PSX...RPGs...RULE!!! ------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 7:13:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 052BB14BF6 for ; Sun, 5 Dec 1999 07:13:37 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.092 #1) id 11ucoa-0000Fi-00; Sun, 05 Dec 1999 14:39:04 +0000 Date: Sun, 5 Dec 1999 14:39:04 +0000 From: Ben Smithurst To: matt Cc: FreeBSD-Stable@FreeBSD.ORG Subject: Re: Little whois patch. Message-ID: <19991205143904.D18336@strontium.scientia.demon.co.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG matt wrote: > I noticed that the Canadian Internic was being left out of the > whois command line opts, so I thought I'd add it to the options. I really > have no clue who to send this to, or if I should use send-pr maybe, but > it's technically not a problem. Hopefully one of the committers can give > me feedback on where this should go. It's diffed against 3.3-stable, does > nothing but give 'whois -c' for whois.internic.ca, us Canadians feel left > out, cheers. =) Can we (the UK) have a -u option too? :-) The host is whois.nic.uk. Anyway, what happens when China want their own option, and find that -c is taken? Wouldn't a more generic option make more sense, something like -c , eg `whois -c ca ...' or `whois -c uk ...' ? -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 7:17:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from phoenix.kurgan.ru (phoenix.kurgan.ru [195.54.28.21]) by hub.freebsd.org (Postfix) with ESMTP id BB15E14BF6 for ; Sun, 5 Dec 1999 07:17:32 -0800 (PST) (envelope-from Martin@McFlySr.Kurgan.Ru) Received: from hilldale.kurgan.ru (hilldale.kurgan.ru [195.54.28.11]) by phoenix.kurgan.ru (8.9.3/8.9.3) with ESMTP id UAA05758 for ; Sun, 5 Dec 1999 20:17:30 +0500 (ES) Date: Sun, 5 Dec 1999 20:17:22 +0500 From: Martin McFlySr Reply-To: Martin McFlySr Organization: Back To The Future X-Priority: 3 (Normal) Message-ID: <11845.991205@McFlySr.Kurgan.Ru> To: freebsd-stable@FreeBSD.ORG Subject: simple question - make world without named 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 Hello freebsd-stable@FreeBSD.ORG, How can i run (or what i must do) make world, for no update (re-install), for example, named? Last stable version from ISC - 8.2.2-P5, but after "make world" named 8.1.2 version going back :( simple edit /usr/src/usr.sbin/Makefile and comment directories with named? or exis better way? Thank you. -- Sunday, December 05, 1999, 20:13 Best regards from future, Martin McFlySr, HillDale. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 9:54: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id 2017B153C7 for ; Sun, 5 Dec 1999 09:53:55 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 28606 invoked from network); 5 Dec 1999 17:53:53 -0000 Received: from userau27.uk.uudial.com (HELO marder-1.) (62.188.137.229) by smtp.dial.pipex.com with SMTP; 5 Dec 1999 17:53:53 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.8.8) id RAA00821 for stable@freebsd.org; Sun, 5 Dec 1999 17:53:54 GMT (envelope-from mark) Date: Sun, 5 Dec 1999 17:53:54 +0000 From: Mark Ovens To: stable@freebsd.org Subject: Non-root mounting of CD-ROMs Message-ID: <19991205175354.B696@marder-1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A thread on the UK User Group mailing list about non-root users mounting CD-ROMs included posts from a couple of people running -STABLE who could do this. I tried and it doesn't work for me. A ktrace(1) showed the call to mount(2) returning EPERM, which is what I would expect. After several posts we established that the only differences we could find between my setup and theirs is that I'm using a SCSI CD-ROM and they both have IDE. Additionally, their systems were cvsup'd more recently than mine (mine was around the end of September) and no-one has made /sbin/mount* setuid. A look through the CVS logs on the web-site shows that there have been quite a few changes to mount in the last couple of months. So, the question is, should a non-root user be able to mount a CD-ROM (without making /sbin/mount* setuid)? -- PERL has been described as "the duct tape of the Internet" and "the Unix Swiss Army chainsaw" - Computer Shopper 12/99 ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 10: 0:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from neptune.1webpage.net (neptune.1webpage.net [208.244.164.17]) by hub.freebsd.org (Postfix) with SMTP id D2E36153C8 for ; Sun, 5 Dec 1999 10:00:57 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: (qmail 24713 invoked from network); 5 Dec 1999 18:00:55 -0000 Received: from harlan.fred.net (HELO pcpsj.pfcs.com) (?Ancs6jSYxphVQ/KDf22OCGhgZuM9YFCW?@208.238.64.78) by neptune.1webpage.net with SMTP; 5 Dec 1999 18:00:55 -0000 Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id ; Sun, 5 Dec 1999 13:00:47 -0500 (EST) Received: from pcnbs.pfcs.com [192.52.69.42] (HELO pcnbs.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Sun, 5 Dec 1999 10:00:45 -0800 (PST) Received: from localhost [127.0.0.1] (HELO pcnbs.pfcs.com) by pcnbs.pfcs.com (8.9.3/8.8.8) via ESMTP id ; Sun, 5 Dec 1999 13:00:44 -0500 (EST) To: Randy Bush Cc: FreeBSD Stable Subject: Re: -stable of 99.12.2 hoistile to ntpd? In-Reply-To: Randy Bush's (randy@psg.com) message dated Sat, 04 Dec 1999 13:05:35. X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (20 Minutes to Nikko) (i386-unknown-freebsd3.2) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Sun, 05 Dec 1999 13:00:44 -0500 Message-ID: <94409.944416844@pcnbs.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The core dump is a problem - I'd like to see that fixed. It might even be fixed, as 4.0.98f has been out there for weeks, and I'm about to roll 4.0.98g. I can't easily tell, as my 3-STABLE boxes all have POSIX scheduling enabled and I an crunched for time these days. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 10:20:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 4619715409 for ; Sun, 5 Dec 1999 10:20:37 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 14-111.008.popsite.net ([209.69.195.111] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.03 #1) id 11ugGo-0003SE-00; Sun, 05 Dec 1999 11:20:31 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id NAA16924; Sun, 5 Dec 1999 13:19:33 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991205175354.B696@marder-1> Date: Sun, 05 Dec 1999 13:19:24 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: Mark Ovens Subject: RE: Non-root mounting of CD-ROMs Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 05-Dec-99 Mark Ovens wrote: > A thread on the UK User Group mailing list about non-root users > mounting CD-ROMs included posts from a couple of people running > -STABLE who could do this. I tried and it doesn't work for me. A > ktrace(1) showed the call to mount(2) returning EPERM, which is what I > would expect. > > After several posts we established that the only differences we could > find between my setup and theirs is that I'm using a SCSI CD-ROM and > they both have IDE. Additionally, their systems were cvsup'd more > recently than mine (mine was around the end of September) and no-one > has made /sbin/mount* setuid. > > A look through the CVS logs on the web-site shows that there have been > quite a few changes to mount in the last couple of months. > > So, the question is, should a non-root user be able to mount a CD-ROM > (without making /sbin/mount* setuid)? sudo? -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 10:35:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relax.dreamfire.net (relax.dreamfire.net [207.113.154.29]) by hub.freebsd.org (Postfix) with ESMTP id 6D26814BD0 for ; Sun, 5 Dec 1999 10:35:41 -0800 (PST) (envelope-from sean@dreamfire.net) Received: from dreamfire.net (indigo.dreamfire.net [192.168.10.8]) by relax.dreamfire.net (Postfix) with ESMTP id 3118C47 for ; Sun, 5 Dec 1999 10:35:36 -0800 (PST) Message-ID: <384AB0A7.75379294@dreamfire.net> Date: Sun, 05 Dec 1999 10:36:23 -0800 From: Sean-Paul Rees Organization: The Dreamfire Solutions Group X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Cleaning /tmp during boot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it safe to clean /tmp during the boot process, before all of the packages and daemons and stuff load? Cheers, Sean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 10:38:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wzrd.com (mail.wzrd.com [206.99.165.3]) by hub.freebsd.org (Postfix) with ESMTP id A2999153FB for ; Sun, 5 Dec 1999 10:38:31 -0800 (PST) (envelope-from danh@wzrd.com) Received: by mail.wzrd.com (Postfix, from userid 91) id B76BD5D05A; Sun, 5 Dec 1999 13:38:30 -0500 (EST) Subject: Re: Non-root mounting of CD-ROMs In-Reply-To: <19991205175354.B696@marder-1> from Mark Ovens at "Dec 5, 1999 5:53:54 pm" To: mark@ukug.uk.freebsd.org (Mark Ovens) Date: Sun, 5 Dec 1999 13:38:30 -0500 (EST) Cc: freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 1810 Message-Id: <19991205183830.B76BD5D05A@mail.wzrd.com> From: danh@wzrd.com (Dan Harnett) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You should be able to allow anyone to mount anything without setting the setuid bit on /sbin/mount*. First, the permissions on the actual device need to be changed so a user can access that device. Second, a simple sysctl will let the user mount a device: sysctl -w vfs.usermount=1 As an alternative, you could put the user into the operator group, but this will give the user more privileges than probably intended. Dan Harnett > A thread on the UK User Group mailing list about non-root users > mounting CD-ROMs included posts from a couple of people running > -STABLE who could do this. I tried and it doesn't work for me. A > ktrace(1) showed the call to mount(2) returning EPERM, which is what I > would expect. > > After several posts we established that the only differences we could > find between my setup and theirs is that I'm using a SCSI CD-ROM and > they both have IDE. Additionally, their systems were cvsup'd more > recently than mine (mine was around the end of September) and no-one > has made /sbin/mount* setuid. > > A look through the CVS logs on the web-site shows that there have been > quite a few changes to mount in the last couple of months. > > So, the question is, should a non-root user be able to mount a CD-ROM > (without making /sbin/mount* setuid)? > > -- > PERL has been described as "the duct tape of the Internet" > and "the Unix Swiss Army chainsaw" > - Computer Shopper 12/99 > ________________________________________________________________ > FreeBSD - The Power To Serve http://www.freebsd.org > My Webpage http://ukug.uk.freebsd.org/~mark/ > mailto:mark@ukug.uk.freebsd.org http://www.radan.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 Dec 5 12: 9:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id B8EA115415 for ; Sun, 5 Dec 1999 12:09:11 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id MAA40447; Sun, 5 Dec 1999 12:09:11 -0800 (PST) Date: Sun, 5 Dec 1999 12:09:11 -0800 (PST) From: David Wolfskill Message-Id: <199912052009.MAA40447@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG, sean@dreamfire.net Subject: Re: Cleaning /tmp during boot In-Reply-To: <384AB0A7.75379294@dreamfire.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Sun, 05 Dec 1999 10:36:23 -0800 >From: Sean-Paul Rees >Is it safe to clean /tmp during the boot process, before all of the >packages and daemons and stuff load? Well, I normally configure machines running FreeBSD to use mfs for /tmp. Among other attributes, that tends to enforce the "cleaning" of /tmp fairly aggressively. I've not noticed anything unpleasant that could be attributed to that "aggressive" cleaning.... Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 12:56:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from monsoon.mail.pipex.net (monsoon.mail.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id 70ADB15452 for ; Sun, 5 Dec 1999 12:56:28 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 3652 invoked from network); 5 Dec 1999 20:56:26 -0000 Received: from useraf59.uk.uudial.com (HELO marder-1.) (62.188.132.46) by smtp.dial.pipex.com with SMTP; 5 Dec 1999 20:56:26 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.8.8) id UAA01912; Sun, 5 Dec 1999 20:56:23 GMT (envelope-from mark) Date: Sun, 5 Dec 1999 20:56:23 +0000 From: Mark Ovens To: Dan Harnett Cc: freebsd-stable@freebsd.org Subject: Re: Non-root mounting of CD-ROMs Message-ID: <19991205205623.B1071@marder-1> References: <19991205175354.B696@marder-1> <19991205183830.B76BD5D05A@mail.wzrd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991205183830.B76BD5D05A@mail.wzrd.com> Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 05, 1999 at 01:38:30PM -0500, Dan Harnett wrote: > You should be able to allow anyone to mount anything without setting > the setuid bit on /sbin/mount*. First, the permissions on the actual > device need to be changed so a user can access that device. Doh! That was it. The one thing no-one checked. > Second, a simple sysctl will let the user mount a device: > > sysctl -w vfs.usermount=1 > > As an alternative, you could put the user into the operator group, > but this will give the user more privileges than probably intended. > It seems that you *must* use ``sysctl -w vfs.usermount=1'', even if the user in the operator group else it still gives "Operation not permitted", although it is possible for the user to umount(8) it :-/ Thanks for the help. > Dan Harnett > > > > A thread on the UK User Group mailing list about non-root users > > mounting CD-ROMs included posts from a couple of people running > > -STABLE who could do this. I tried and it doesn't work for me. A > > ktrace(1) showed the call to mount(2) returning EPERM, which is what I > > would expect. > > > > After several posts we established that the only differences we could > > find between my setup and theirs is that I'm using a SCSI CD-ROM and > > they both have IDE. Additionally, their systems were cvsup'd more > > recently than mine (mine was around the end of September) and no-one > > has made /sbin/mount* setuid. > > > > A look through the CVS logs on the web-site shows that there have been > > quite a few changes to mount in the last couple of months. > > > > So, the question is, should a non-root user be able to mount a CD-ROM > > (without making /sbin/mount* setuid)? > > > > -- > > PERL has been described as "the duct tape of the Internet" > > and "the Unix Swiss Army chainsaw" > > - Computer Shopper 12/99 > > ________________________________________________________________ > > FreeBSD - The Power To Serve http://www.freebsd.org > > My Webpage http://ukug.uk.freebsd.org/~mark/ > > mailto:mark@ukug.uk.freebsd.org http://www.radan.com > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > -- PERL has been described as "the duct tape of the Internet" and "the Unix Swiss Army chainsaw" - Computer Shopper 12/99 ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 13: 7:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id D0D74152A9 for ; Sun, 5 Dec 1999 13:07:40 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id VAA92967; Sun, 5 Dec 1999 21:07:34 GMT (envelope-from joe) Date: Sun, 5 Dec 1999 21:07:34 +0000 From: Josef Karthauser To: Ben Smithurst Cc: matt , FreeBSD-Stable@FreeBSD.ORG Subject: Re: Little whois patch. Message-ID: <19991205210734.A90126@florence.pavilion.net> References: <19991205143904.D18336@strontium.scientia.demon.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991205143904.D18336@strontium.scientia.demon.co.uk> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 05, 1999 at 02:39:04PM +0000, Ben Smithurst wrote: > matt wrote: > > > I noticed that the Canadian Internic was being left out of the > > whois command line opts, so I thought I'd add it to the options. I really > > have no clue who to send this to, or if I should use send-pr maybe, but > > it's technically not a problem. Hopefully one of the committers can give > > me feedback on where this should go. It's diffed against 3.3-stable, does > > nothing but give 'whois -c' for whois.internic.ca, us Canadians feel left > > out, cheers. =) > > Can we (the UK) have a -u option too? :-) The host is whois.nic.uk. > Anyway, what happens when China want their own option, and find that -c > is taken? Wouldn't a more generic option make more sense, something like > -c , eg `whois -c ca ...' or `whois -c uk ...' ? The whois in -current has a fix for this. I'm working to get it mfc'd to the 3.x for sometime after 3.4 hits the press. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 14: 1:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from neptune.1webpage.net (neptune.1webpage.net [208.244.164.17]) by hub.freebsd.org (Postfix) with SMTP id 0FC2F15464 for ; Sun, 5 Dec 1999 14:01:27 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: (qmail 24845 invoked from network); 5 Dec 1999 22:01:18 -0000 Received: from harlan.fred.net (HELO pcpsj.pfcs.com) (?itp0GZiaRarXmsVK4BBLTZSSwslNoWV2?@208.238.64.78) by neptune.1webpage.net with SMTP; 5 Dec 1999 22:01:18 -0000 Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id for ; Sun, 5 Dec 1999 17:00:59 -0500 (EST) Received: from pcnbs.pfcs.com [192.52.69.42] (HELO pcnbs.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Sun, 5 Dec 1999 14:00:23 -0800 (PST) Received: from localhost [127.0.0.1] (HELO pcnbs.pfcs.com) by pcnbs.pfcs.com (8.9.3/8.8.8) via ESMTP id for ; Sun, 5 Dec 1999 17:00:22 -0500 (EST) To: stable@freebsd.org Subject: buildworld problem with usr.sbin/lpr/filters.ru X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (patch 8) (Bryce Canyon) (i386-unknown-freebsd3.3) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Sun, 05 Dec 1999 17:00:22 -0500 Message-ID: <70669.944431222@pcnbs.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a cvsup copy of the build tree, which gets updated reasonably often. I have a -STABLE copy of the tree checked out (RELENG_3 tag), and it gives me a broken subtree of usr.sbin/lpr/filters.ru/ . This is happening The Makefile is 1.4, and the problem is that there is a koi2alt/ subdir and a koi2alt.c file in there. The problem is that the "make clean" step fails because koi2alt is a directory, not a regular file. Any ideas? H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 14:10:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dbitech.bc.ca (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (Postfix) with SMTP id 18C1115474 for ; Sun, 5 Dec 1999 14:10:47 -0800 (PST) (envelope-from darcy@ok-connect.com) Received: (qmail 6280 invoked from network); 5 Dec 1999 22:10:46 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 5 Dec 1999 22:10:46 -0000 Message-Id: <3.0.32.19991205141139.009a1d50@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 05 Dec 1999 14:11:39 -0800 To: FreeBSD-Stable@FreeBSD.ORG From: Darcy Buskermolen Subject: Re: Little whois patch. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The feature I'd find a bit more usefull would be a -f (or soemthing like it) that would allow an auto follow. Meaning that now that there are 12 appoved signing auths for .com,net,org you have to do 2 howis queries to find out the contact info, not handy for some things, currently this is what I use to acmplish the same thing, however I can't tell the diffrence between no such domain, and network timeout.. (ok well I could, but... :-) ) #!/bin/sh WHOISSERVER=`whois $1 | grep "Whois Server:" | awk '{printf($3)}'` whois -h $WHOISSERVER $1 I have a shell script that I'm using for this now, but it's a bit clunky. At 09:07 PM 12/5/99 +0000, Josef Karthauser wrote: >On Sun, Dec 05, 1999 at 02:39:04PM +0000, Ben Smithurst wrote: >> matt wrote: >> >> > I noticed that the Canadian Internic was being left out of the >> > whois command line opts, so I thought I'd add it to the options. I really >> > have no clue who to send this to, or if I should use send-pr maybe, but >> > it's technically not a problem. Hopefully one of the committers can give >> > me feedback on where this should go. It's diffed against 3.3-stable, does >> > nothing but give 'whois -c' for whois.internic.ca, us Canadians feel left >> > out, cheers. =) >> >> Can we (the UK) have a -u option too? :-) The host is whois.nic.uk. >> Anyway, what happens when China want their own option, and find that -c >> is taken? Wouldn't a more generic option make more sense, something like >> -c , eg `whois -c ca ...' or `whois -c uk ...' ? > >The whois in -current has a fix for this. I'm working to get it mfc'd >to the 3.x for sometime after 3.4 hits the press. > >Joe >-- >Josef Karthauser FreeBSD: How many times have you booted today? >Technical Manager Viagra for your server (http://www.uk.freebsd.org) >Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] > > >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 Dec 5 14:56: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id A56DE14C3C for ; Sun, 5 Dec 1999 14:56:01 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA88072; Sun, 5 Dec 1999 14:54:36 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912052254.OAA88072@gndrsh.dnsmgr.net> Subject: Re: Little whois patch. In-Reply-To: <19991205143904.D18336@strontium.scientia.demon.co.uk> from Ben Smithurst at "Dec 5, 1999 02:39:04 pm" To: ben@scientia.demon.co.uk (Ben Smithurst) Date: Sun, 5 Dec 1999 14:54:35 -0800 (PST) Cc: matt@S02.ARPA-CANADA.NET (matt), FreeBSD-Stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > matt wrote: > > > I noticed that the Canadian Internic was being left out of the > > whois command line opts, so I thought I'd add it to the options. I really > > have no clue who to send this to, or if I should use send-pr maybe, but > > it's technically not a problem. Hopefully one of the committers can give > > me feedback on where this should go. It's diffed against 3.3-stable, does > > nothing but give 'whois -c' for whois.internic.ca, us Canadians feel left > > out, cheers. =) > > Can we (the UK) have a -u option too? :-) The host is whois.nic.uk. > Anyway, what happens when China want their own option, and find that -c > is taken? Wouldn't a more generic option make more sense, something like > -c , eg `whois -c ca ...' or `whois -c uk ...' ? How about a much more elegant solution in that this data should not be coded in the program at all. Use of an external data file that maps regex's to whois servers living in /usr/share someplace would mean we could stop fussing with the binary and just fix the data file such that it DTRT for folks: .*\.{com,net,org}$ whois.networksolutions.com .*\.{mil}$ ??? .*\.{edu}$ ??? .*\.{ca}$ whois.internic.ca .*\.{uk}$ ??? etc, etc.... And -h would override even looking at this file... And for folks like me who do lots of rr queries I could locally add things like ^AS[0-9]* whois.ra.net ^MAINT-.* whois.ra.net ^RTR-.* whois.ra.net ^[1-9]*\.[0-9]*\.[0-9]*\.[0-9]* whois.arin.net Infact you could go one step further and even allow a ~/.whoisrc, so my users whouldn't get confused when whois gave them data from a routing registry :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 15: 5:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 5B6E414C9D for ; Sun, 5 Dec 1999 15:05:50 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id XAA05975; Sun, 5 Dec 1999 23:04:51 GMT (envelope-from joe) Date: Sun, 5 Dec 1999 23:04:50 +0000 From: Josef Karthauser To: "Rodney W. Grimes" Cc: Ben Smithurst , matt , FreeBSD-Stable@FreeBSD.ORG Subject: Re: Little whois patch. Message-ID: <19991205230450.D90126@florence.pavilion.net> References: <19991205143904.D18336@strontium.scientia.demon.co.uk> <199912052254.OAA88072@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912052254.OAA88072@gndrsh.dnsmgr.net> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 05, 1999 at 02:54:35PM -0800, Rodney W. Grimes wrote: > > Infact you could go one step further and even allow a ~/.whoisrc, > so my users whouldn't get confused when whois gave them data from > a routing registry :-) > That was my thinking too, but it really does look like that version in -current which utilises .whois-servers.net guesses correctly for domains. Kinda neet. Have you used it Rod? Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 15: 8:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from clapton.atgsystems.com (clapton.atgsystems.com [207.122.162.32]) by hub.freebsd.org (Postfix) with ESMTP id 5468C14C2F for ; Sun, 5 Dec 1999 15:08:33 -0800 (PST) (envelope-from bob@clapton.atgsystems.com) Received: from madman (root@joplin.atgsystems.com [207.122.162.33]) by clapton.atgsystems.com (8.8.8/8.8.8) with SMTP id RAA16013; Sun, 5 Dec 1999 17:07:46 -0600 (CST) (envelope-from bob@clapton.atgsystems.com) Message-ID: <005e01bf3f76$32bd2290$01000000@madman> From: "Bob Madden" To: "Rodney W. Grimes" , "FreeBSD-Stable" Cc: "Bob Madden" Subject: Re: Little whois patch. Date: Sun, 5 Dec 1999 17:12:26 -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.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, the day that Network Solutions turned over authority of Internic.net, etc, to the DOC, I found this source, and compiled it on FreeBSD just fine, although I do note that it was originally written for Linux: ***** BEGIN PASTE **************** /* * whois.c: * * whois - Internet user name directory service * * whois [ -h server ] name * * the -h option specifies the hostname or IP address of a whois server. * (see the README file for details) * * Copyright (c) 1980 Regents of the University of California. * All rights reserved. The Berkeley software License Agreement * specifies the terms and conditions for redistribution. */ /* Minor hack to support accessing arin.net by default for non-alpha queries */ #ifndef lint char copyright[] = "@(#) Copyright (c) 1980 Regents of the University of California.\n\ All rights reserved.\n"; #endif not lint #ifndef lint static char sccsid[] = "@(#)whois.c 5.3 (Berkeley) 2/8/88"; #endif not lint #include #include #include #include #include #define NICHOST "whois.networksolutions.com" #define IPHOST "whois.arin.net" main(argc, argv) int argc; char *argv[]; { int s; register FILE *sfi, *sfo; register int c; char *host = IPHOST; struct sockaddr_in sin; struct hostent *hp; struct servent *sp; char *p; argc--, argv++; if (argc > 2 && strcmp(*argv, "-h") == 0) { argv++, argc--; host = *argv++; argc--; } if (argc != 1) { fprintf(stderr, "usage: whois [ -h host ] name\n"); exit(1); } /* Use NICHOST if any character is alpha */ if(host == IPHOST) { p = *argv; while(*p) { if(isalpha(*p++)) host = NICHOST; } } hp = gethostbyname(host); if (hp == NULL) { fprintf(stderr, "whois: "); herror(host); exit(1); } host = hp->h_name; s = socket(hp->h_addrtype, SOCK_STREAM, 0); if (s < 0) { perror("whois: socket"); exit(2); } bzero((caddr_t)&sin, sizeof (sin)); sin.sin_family = hp->h_addrtype; if (bind(s, &sin, sizeof (sin)) < 0) { perror("whois: bind"); exit(3); } bcopy(hp->h_addr, &sin.sin_addr, hp->h_length); sp = getservbyname("whois", "tcp"); if (sp == NULL) { fprintf(stderr, "whois: whois/tcp: unknown service\n"); exit(4); } sin.sin_port = sp->s_port; if (connect(s, &sin, sizeof (sin)) < 0) { perror("whois: connect"); exit(5); } sfi = fdopen(s, "r"); sfo = fdopen(s, "w"); if (sfi == NULL || sfo == NULL) { perror("fdopen"); close(s); exit(1); } fprintf(sfo, "%s\r\n", *argv); fflush(sfo); while ((c = getc(sfi)) != EOF) putchar(c); exit(0); } *********** END PASTE ************ Bob Madden >,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,< --This Message Composed By: Bob Madden -- bob@CLAPTON.ATGSYSTEMS.COM Sys Admin /Network Engineer -----Original Message----- From: Rodney W. Grimes To: Ben Smithurst Cc: matt ; FreeBSD-Stable@FreeBSD.ORG Date: Sunday, December 05, 1999 4:55 PM Subject: Re: Little whois patch. >> matt wrote: >> >> > I noticed that the Canadian Internic was being left out of the >> > whois command line opts, so I thought I'd add it to the options. I really >> > have no clue who to send this to, or if I should use send-pr maybe, but >> > it's technically not a problem. Hopefully one of the committers can give >> > me feedback on where this should go. It's diffed against 3.3-stable, does >> > nothing but give 'whois -c' for whois.internic.ca, us Canadians feel left >> > out, cheers. =) >> >> Can we (the UK) have a -u option too? :-) The host is whois.nic.uk. >> Anyway, what happens when China want their own option, and find that -c >> is taken? Wouldn't a more generic option make more sense, something like >> -c , eg `whois -c ca ...' or `whois -c uk ...' ? > >How about a much more elegant solution in that this data should not >be coded in the program at all. Use of an external data file that >maps regex's to whois servers living in /usr/share someplace would >mean we could stop fussing with the binary and just fix the data >file such that it DTRT for folks: > >.*\.{com,net,org}$ whois.networksolutions.com >.*\.{mil}$ ??? >.*\.{edu}$ ??? >.*\.{ca}$ whois.internic.ca >.*\.{uk}$ ??? > >etc, etc.... > >And -h would override even looking at this file... > >And for folks like me who do lots of rr queries I could locally add >things like >^AS[0-9]* whois.ra.net >^MAINT-.* whois.ra.net >^RTR-.* whois.ra.net >^[1-9]*\.[0-9]*\.[0-9]*\.[0-9]* whois.arin.net > >Infact you could go one step further and even allow a ~/.whoisrc, >so my users whouldn't get confused when whois gave them data from >a routing registry :-) > >-- >Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net > > >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 Dec 5 15:27:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 0D6E014D24 for ; Sun, 5 Dec 1999 15:27:26 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id PAA88161; Sun, 5 Dec 1999 15:27:15 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912052327.PAA88161@gndrsh.dnsmgr.net> Subject: Re: Little whois patch. In-Reply-To: <19991205230450.D90126@florence.pavilion.net> from Josef Karthauser at "Dec 5, 1999 11:04:50 pm" To: joe@pavilion.net (Josef Karthauser) Date: Sun, 5 Dec 1999 15:27:15 -0800 (PST) Cc: ben@scientia.demon.co.uk (Ben Smithurst), matt@S02.ARPA-CANADA.NET (matt), FreeBSD-Stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Dec 05, 1999 at 02:54:35PM -0800, Rodney W. Grimes wrote: > > > > Infact you could go one step further and even allow a ~/.whoisrc, > > so my users whouldn't get confused when whois gave them data from > > a routing registry :-) > > > > That was my thinking too, but it really does look like that version > in -current which utilises .whois-servers.net guesses correctly for domains. > Kinda neet. Have you used it Rod? No, I haven't used it, I don't do much day to day production work from the 4.x-current playpen box. I'm heading that way now to take a look at it and probably smash it onto my production desktop box if it does what you say it does. This latest set of changes to all the whois stuff has me a bit in an uproar, with NSI and the RA screwing around with output formats all in the same month breaking lots of little shell scripts for me my life has been misserable. :-( At least with RA I just had to smash in a ripe181 to get the old format back until I can update the tools to rpsl :-) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 15:36:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 7BCE714C1D for ; Sun, 5 Dec 1999 15:36:24 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id XAA09183; Sun, 5 Dec 1999 23:36:19 GMT (envelope-from joe) Date: Sun, 5 Dec 1999 23:36:19 +0000 From: Josef Karthauser To: "Rodney W. Grimes" Cc: Ben Smithurst , matt , FreeBSD-Stable@FreeBSD.ORG Subject: Re: Little whois patch. Message-ID: <19991205233618.A8928@florence.pavilion.net> References: <19991205230450.D90126@florence.pavilion.net> <199912052327.PAA88161@gndrsh.dnsmgr.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912052327.PAA88161@gndrsh.dnsmgr.net> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 05, 1999 at 03:27:15PM -0800, Rodney W. Grimes wrote: > No, I haven't used it, I don't do much day to day production work from > the 4.x-current playpen box. I'm heading that way now to take a look > at it and probably smash it onto my production desktop box if it does > what you say it does. This latest set of changes to all the whois stuff > has me a bit in an uproar, with NSI and the RA screwing around with output > formats all in the same month breaking lots of little shell scripts for > me my life has been misserable. :-( At least with RA I just had to > smash in a ripe181 to get the old format back until I can update the > tools to rpsl :-) I'm interested in your comments. I'm trying to tie up all the outstanding PRs against it, and then I'll merge into -stable. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 15:44:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dbitech.bc.ca (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (Postfix) with SMTP id AA39314DC1 for ; Sun, 5 Dec 1999 15:44:32 -0800 (PST) (envelope-from darcy@ok-connect.com) Received: (qmail 10107 invoked from network); 5 Dec 1999 23:44:31 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 5 Dec 1999 23:44:31 -0000 Message-Id: <3.0.32.19991205154524.00b16690@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Sun, 05 Dec 1999 15:45:25 -0800 To: FreeBSD-Stable@FreeBSD.ORG From: Darcy Buskermolen Subject: Re: Little whois patch. Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Now that you mentioned it, my other point about a follow is mute :-) I've played with it, queried over 500 domains with it with excellent results. my only issue with it is since it does everything else automagicly, can we also have it do arpa's as well? Just my solomon comments. At 11:36 PM 12/5/99 +0000, Josef Karthauser wrote: >On Sun, Dec 05, 1999 at 03:27:15PM -0800, Rodney W. Grimes wrote: > >> No, I haven't used it, I don't do much day to day production work from >> the 4.x-current playpen box. I'm heading that way now to take a look >> at it and probably smash it onto my production desktop box if it does >> what you say it does. This latest set of changes to all the whois stuff >> has me a bit in an uproar, with NSI and the RA screwing around with output >> formats all in the same month breaking lots of little shell scripts for >> me my life has been misserable. :-( At least with RA I just had to >> smash in a ripe181 to get the old format back until I can update the >> tools to rpsl :-) > >I'm interested in your comments. I'm trying to tie up all the >outstanding PRs against it, and then I'll merge into -stable. > >Joe >-- >Josef Karthauser FreeBSD: How many times have you booted today? >Technical Manager Viagra for your server (http://www.uk.freebsd.org) >Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] > > >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 Dec 5 19:51:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcom.com (netcom14.netcom.com [199.183.9.114]) by hub.freebsd.org (Postfix) with ESMTP id 3ED5A14E1E for ; Sun, 5 Dec 1999 19:51:52 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id TAA08799 for freebsd-stable@freebsd.org; Sun, 5 Dec 1999 19:51:52 -0800 (PST) From: Stan Brown Message-Id: <199912060351.TAA08799@netcom.com> Subject: How to satrt gnome? To: freebsd-stable@freebsd.org (FreeBSD Stable List) Date: Sun, 5 Dec 1999 22:51:51 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Finally got the Gnome port to build on my laptop. Now, how do I set up a given acount to use it? -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 19:53:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcom.com (netcom14.netcom.com [199.183.9.114]) by hub.freebsd.org (Postfix) with ESMTP id 006D614E1E for ; Sun, 5 Dec 1999 19:53:55 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id TAA08832 for freebsd-stable@freebsd.org; Sun, 5 Dec 1999 19:53:55 -0800 (PST) From: Stan Brown Message-Id: <199912060353.TAA08832@netcom.com> Subject: Parallel port ZIP drive? To: freebsd-stable@freebsd.org (FreeBSD Stable List) Date: Sun, 5 Dec 1999 22:53:55 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Went out and bought a new hard drive from Staples today. The price was too good to pass up!. Anyway, it came with a free parallel port zip drive. Needless to say this only included windoze drivers :-( Can I use this with FreeBSD? If so how? Thanks. -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 19:59: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 3089A14E1E for ; Sun, 5 Dec 1999 19:59:02 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id OAA23637; Mon, 6 Dec 1999 14:28:53 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912060353.TAA08832@netcom.com> Date: Mon, 06 Dec 1999 14:28:52 +1030 (CST) From: "Daniel O'Connor" To: Stan Brown Subject: RE: Parallel port ZIP drive? Cc: (FreeBSD Stable List) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Dec-99 Stan Brown wrote: > Anyway, it came with a free parallel port zip drive. Needless to say > this only included windoze drivers :-( Can I use this with FreeBSD? If > so how? The LINT kernel config file will give you more information.. It tells you about the vpo0 controller and ppbus.. (Which is the limit of my knowledge since I don't have a parallel zip drive) BTW this sort of question belongs on freebsd-questions. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 22: 2:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from azazel.zer0.org (azazel.zer0.org [209.133.53.200]) by hub.freebsd.org (Postfix) with ESMTP id 2BF3814DDA for ; Sun, 5 Dec 1999 22:02:08 -0800 (PST) (envelope-from gsutter@azazel.zer0.org) Received: (from gsutter@localhost) by azazel.zer0.org (8.9.3/8.9.2) id WAA44301; Sun, 5 Dec 1999 22:00:39 -0800 (PST) (envelope-from gsutter) Date: Sun, 5 Dec 1999 22:00:39 -0800 From: Gregory Sutter To: matt Cc: FreeBSD-Stable@FreeBSD.ORG Subject: Re: Little whois patch. Message-ID: <19991205220039.Z94590@azazel.zer0.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Organization: Zer0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 04, 1999 at 09:44:42PM -0500, matt wrote: > > I noticed that the Canadian Internic was being left out of the > whois command line opts, so I thought I'd add it to the options. I really > have no clue who to send this to, or if I should use send-pr maybe, but > it's technically not a problem. Hopefully one of the committers can give > me feedback on where this should go. It's diffed against 3.3-stable, does > nothing but give 'whois -c' for whois.internic.ca, us Canadians feel left > out, cheers. =) For a while now, I've been using a whois wrapper written by Greg Woods. It works very well, querying the appropriate registrars for .com, .net, .org, etc., as well as country-specific TLDs. IP requests are handled as well. Using this would solve all the problems that I've read in this thread, without requiring modifications to 'whois' itself. ftp://ftp.weird.com/pub/local/awhois.sh Examples (output snipped): scapegoat gsutter ~ $awhois mircosoft.com Registrant: YELLOW AGENCY (MIRCOSOFT7-DOM) Domain Name: MIRCOSOFT.COM scapegoat gsutter ~ $awhois internic.ca Subdomain: internic.ca Organization: Internic.ca Inc. scapegoat gsutter ~ $awhois come.to Tonic whoisd V1.0 come ns.come.to 193.79.64.100 ns1.fortunecity.com 204.198.135.24 scapegoat gsutter ~ $awhois 204.71.200 Cable & Wireless USA (NETBLK-CW-PROVIDER) CW-PROVIDER 204.71.0.0 - 204.71.255.255 Internet Systems, Inc. (NETBLK-CW-BLK-INTERNET-CONN) CW-BLK-INTERNET-CONN 204.71.176.0 - 204.71.207.0 Yahoo (NETBLK-NET-SNV-YAHOO1) NET-SNV-YAHOO1 204.71.200.0 - 204.71.201.255 Greg -- Gregory S. Sutter Cole's Law: Thinly sliced cabbage. mailto:gsutter@pobox.com http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 22:51:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zgia.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with SMTP id D778715088 for ; Sun, 5 Dec 1999 22:51:14 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by zgia.zp.ua (8.9.3/8.9.3) with ESMTP id JAA03665; Mon, 6 Dec 1999 09:49:37 GMT Date: Mon, 6 Dec 1999 09:49:37 +0000 (GMT) From: Alexandr Listopad To: "Daniel J. O'Connor" Cc: Kent Boortz , freebsd-stable@FreeBSD.ORG Subject: RE: Out of swap hangs machine 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 darius> darius>How much RAM do you have? darius> darius>It should be of the order of 2x your RAM.. darius> hi! I have 128Megs of RAM and 130M of swap. 11M free of mem, and 130M free of swap.... ;) And my FreeBSD never used swap... as I see on "top". Question: why it should be "...2x your RAM.." ??? Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 22:54:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id 4249D14DEE for ; Sun, 5 Dec 1999 22:54:08 -0800 (PST) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.1b+Sun/SMI-SVR4) id HAA01334; Mon, 6 Dec 1999 07:54:28 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 2.05 #1 (Debian)) id 11urbG-0001cT-00; Mon, 6 Dec 1999 07:26:18 +0100 Date: Mon, 6 Dec 1999 07:26:18 +0100 From: Szilveszter Adam To: FreeBSD-Stable@FreeBSD.ORG Subject: Re: Little whois patch. Message-ID: <19991206072618.A5763@petra.hos.u-szeged.hu> Mail-Followup-To: FreeBSD-Stable@FreeBSD.ORG References: <19991205230450.D90126@florence.pavilion.net> <199912052327.PAA88161@gndrsh.dnsmgr.net> <19991205233618.A8928@florence.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In-Reply-To: <19991205233618.A8928@florence.pavilion.net>; from joe@pavilion.net on Sun, Dec 05, 1999 at 11:36:19PM +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 05, 1999 at 11:36:19PM +0000, Josef Karthauser wrote: > On Sun, Dec 05, 1999 at 03:27:15PM -0800, Rodney W. Grimes wrote: > > > No, I haven't used it, I don't do much day to day production work from > > the 4.x-current playpen box. I'm heading that way now to take a look > > at it and probably smash it onto my production desktop box if it does > > what you say it does. This latest set of changes to all the whois stuff > > has me a bit in an uproar, with NSI and the RA screwing around with output > > formats all in the same month breaking lots of little shell scripts for > > me my life has been misserable. :-( At least with RA I just had to > > smash in a ripe181 to get the old format back until I can update the > > tools to rpsl :-) > > I'm interested in your comments. I'm trying to tie up all the > outstanding PRs against it, and then I'll merge into -stable. > Hi! I have succesfully compiled and used the -CURRENT version on my -STABLE box, it handles automagic domain recognition very well. (Well, it had to, I am in Europe so NSI was not the only one for me here:-) But as I had stated several times, the man page is incorrrect. I have also submitted a patch for it but it was ignored. The core of the problem is that a) it still says "Network Solutions InterNIC database" which is *NOT* true. NSI and InterNIC are totally independent now. b) The prog still provides the -i option to query the NSI server directly but does not bother to mention that they are no longer the only registrants. We must consider that not every user reads news as much as we do but learns the use of the Internet from old books...(1-2 years old etc) So, I am sending the man page patch again...it is against whois.1 ver 1.9 but should apply to 1.10 as well... --- whois.1.orig Fri Dec 3 11:08:49 1999 +++ whois.1 Sun Dec 5 08:09:23 1999 @@ -81,7 +81,7 @@ to whois.crsnic.net provided. .It Fl i Use the Network Solutions Registry for Internet Numbers -.Pq Tn InterNIC +.Pq Tn whois.networksolutions.com database. It contains network numbers and domain contact information for most of .Tn \&.COM , @@ -89,7 +89,13 @@ .Tn \&.ORG and .Tn \&.EDU -domains. +domains. NOTE! The registration of these doamins is now done by a number of +independent and competing registrars and this database holds no information +on the domains registered by organizations other than Network Solutions, Inc. +Also, note that the InterNIC database +.Pq Tn whois.internic.net +is no longer handled by Network Solutions, Inc. For details, see: +http://www.internic.net/. .It Fl m Use the Route Arbiter Database .Pq Tn RADB Have a nice day! Szilveszter ADAM -- ------------------------------------------------------------------------------- * Szilveszter ADAM * JATE Szeged * email: sziszi@petra.hos.u-szeged.hu * * Homepage : none * alternate email: cc@flanker.itl.net.ua * * Finger sziszi@petra.hos.u-szeged.hu for PGP key. * * I prefer using the door instead of Windows(tm)... * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 22:55:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9F22214DEE for ; Sun, 5 Dec 1999 22:55:50 -0800 (PST) (envelope-from doconnor@gsoft.com.au) Received: from cain.gsoft.com.au (doconnor@cain [203.38.152.97]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id RAA26034; Mon, 6 Dec 1999 17:24:24 +1030 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 06 Dec 1999 17:24:24 +1030 (CST) From: "Daniel O'Connor" To: Alexandr Listopad Subject: RE: Out of swap hangs machine Cc: freebsd-stable@FreeBSD.ORG, Kent Boortz Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Dec-99 Alexandr Listopad wrote: > 11M free of mem, and 130M free of swap.... ;) And my FreeBSD never used > swap... as I see on "top". > > Question: why it should be "...2x your RAM.." ??? Well if it doesn't use it them don't worry. 2x RAM seems fine for me, but I run a lot of junk which generally gets swapped out :) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 22:58:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from s02.arpa-canada.net (s02.arpa-canada.net [209.104.118.66]) by hub.freebsd.org (Postfix) with SMTP id 35B1014DEE for ; Sun, 5 Dec 1999 22:58:10 -0800 (PST) (envelope-from matt@S02.ARPA-CANADA.NET) Received: (qmail 45781 invoked by uid 1000); 6 Dec 1999 06:58:09 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Dec 1999 06:58:09 -0000 Date: Mon, 6 Dec 1999 01:58:09 -0500 (EST) From: matt To: FreeBSD-STABLE Subject: whois patch. 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 agree that a wrapper is the more 'practical' answer, however this was something I would love to see done by default. To hear of -current's whois solution, it's much better than mine. I'm glad to see I wasn't the only one thinking along the lines of whois being too narrow minded. Sorry for the mail this has generated, had I know it was something already done in -current, I never would have done anything, but I don't track -current, so I didn't know. Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 23: 7:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sol.cc.u-szeged.hu (sol.cc.u-szeged.hu [160.114.8.24]) by hub.freebsd.org (Postfix) with ESMTP id D72D914C0C for ; Sun, 5 Dec 1999 23:07:52 -0800 (PST) (envelope-from sziszi@petra.hos.u-szeged.hu) Received: from petra.hos.u-szeged.hu by sol.cc.u-szeged.hu (8.9.1b+Sun/SMI-SVR4) id IAA02342; Mon, 6 Dec 1999 08:08:12 +0100 (MET) Received: from sziszi by petra.hos.u-szeged.hu with local (Exim 2.05 #1 (Debian)) id 11uroY-0001fk-00; Mon, 6 Dec 1999 07:40:02 +0100 Date: Mon, 6 Dec 1999 07:40:02 +0100 From: Szilveszter Adam To: freebsd-stable@FreeBSD.ORG Subject: Re: Out of swap hangs machine Message-ID: <19991206074002.B5763@petra.hos.u-szeged.hu> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0i In-Reply-To: ; from doconnor@gsoft.com.au on Mon, Dec 06, 1999 at 05:24:24PM +1030 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Dec-99 Alexandr Listopad wrote: > 11M free of mem, and 130M free of swap.... ;) And my FreeBSD never used > swap... as I see on "top". > > Question: why it should be "...2x your RAM.." ??? It is essentially an old rule of thumb but it should be adjusted according to your site's requirements. It was also said that above 64M RAM swap is not strictly necessary... and if you want to see examples of it being used, well, fire up Star Office and watch your free memory disappear:-) And this is only one user... I would imagine what it meant if 10 users tried to use it in the lab at the same time from the same machine... So much for applications being used over the Net:-) Cheers! Szilveszter ADAM -- ------------------------------------------------------------------------------- * Szilveszter ADAM * JATE Szeged * email: sziszi@petra.hos.u-szeged.hu * * Homepage : none * alternate email: cc@flanker.itl.net.ua * * Finger sziszi@petra.hos.u-szeged.hu for PGP key. * * I prefer using the door instead of Windows(tm)... * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 23: 8:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 0030B14C0C for ; Sun, 5 Dec 1999 23:08:43 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA01437 for stable@FreeBSD.ORG; Mon, 6 Dec 1999 00:08:43 -0700 (MST) (envelope-from ken) Message-Id: <199912060708.AAA01437@panzer.kdm.org> Subject: small PCI change, need review To: stable@FreeBSD.ORG Date: Mon, 6 Dec 1999 00:08:43 -0700 (MST) From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Since I don't have a -stable test box, I'd appreciate it if someone could try this patch. (I've been running it on a number of older stable systems for a few months.) This should prevent the "garbage" output from 'pciconf -l' that some folks may see if you've got PCI cards with no driver assigned. (Peter Wemm brought this fix into -current with the new-bus import in rev 1.95 of pci.c.) To try the patch, just apply it to pci.c, recompile, reinstall, reboot, and then run 'pciconf -l' and make sure it looks okay. Thanks, Ken -- Kenneth Merry ken@kdm.org ==== //depot/FreeBSD-ken-stable/src/sys/pci/pci.c#1 - /a/ken/perforce/FreeBSD-ken-stable/src/sys/pci/pci.c ==== *** /tmp/tmp.1405.0 Mon Dec 6 00:03:50 1999 --- /a/ken/perforce/FreeBSD-ken-stable/src/sys/pci/pci.c Mon Dec 6 00:03:06 1999 *************** *** 339,347 **** if (devlist_entry == NULL) return (NULL); ! cfg = &devlist_entry->cfg; ! bzero(cfg, sizeof *cfg); cfg->bus = probe->bus; cfg->slot = probe->slot; --- 339,347 ---- if (devlist_entry == NULL) return (NULL); ! bzero(devlist_entry, sizeof(*devlist_entry)); ! cfg = &devlist_entry->cfg; cfg->bus = probe->bus; cfg->slot = probe->slot; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 23:28:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from web1401.mail.yahoo.com (web1401.mail.yahoo.com [128.11.23.165]) by hub.freebsd.org (Postfix) with SMTP id 73779150F6 for ; Sun, 5 Dec 1999 23:28:40 -0800 (PST) (envelope-from gwq_uk@yahoo.com) Received: (qmail 13364 invoked by uid 60001); 6 Dec 1999 07:28:39 -0000 Message-ID: <19991206072839.13363.qmail@web1401.mail.yahoo.com> Received: from [203.17.53.202] by web1401.mail.yahoo.com; Sun, 05 Dec 1999 23:28:39 PST Date: Sun, 5 Dec 1999 23:28:39 -0800 (PST) From: =?iso-8859-1?q?Greg=20Quinlan?= Subject: make buildworld broken? To: FreeBSD-Stable@freebsd.org Cc: greg@swlct.sthames.nhs.uk MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Went to do a "make buildworld" and it appears to be broken??? (cvsup-ed 6/12/99) Any comments Greg /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_base.c:613: warning: passing arg 2 of `strtoul' from incompatible pointer type cc -nostdinc -O -pipe -Wall -DKERNEL -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -DKLD_MODULE -nostdinc -I- -I/usr/obj/usr/src/sys/modules/netgraph/netgraph -I/usr/obj/usr/src/sys/modules/netgraph/netgraph/@ -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_parse.c /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_parse.c:50: sys/ctype.h: No such file or directory /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_parse.c: In function `ng_int8_parse': /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_parse.c:337: warning: implicit declaration of function `strtol' /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_parse.c: In function `ng_parse_composite': /usr/src/sys/modules/netgraph/netgraph/../../../netgraph/ng_parse.c:1022: warning: passing arg 2 of `strtoul' from incompatible pointer type *** Error code 1 Stop. *** Error code 1 Stop. __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 5 23:34:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id AC0C515114 for ; Sun, 5 Dec 1999 23:34:37 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id XAA89078; Sun, 5 Dec 1999 23:34:25 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912060734.XAA89078@gndrsh.dnsmgr.net> Subject: Re: Little whois patch. In-Reply-To: <19991205233618.A8928@florence.pavilion.net> from Josef Karthauser at "Dec 5, 1999 11:36:19 pm" To: joe@pavilion.net (Josef Karthauser) Date: Sun, 5 Dec 1999 23:34:25 -0800 (PST) Cc: ben@scientia.demon.co.uk (Ben Smithurst), matt@S02.ARPA-CANADA.NET (matt), FreeBSD-Stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, Dec 05, 1999 at 03:27:15PM -0800, Rodney W. Grimes wrote: > > > No, I haven't used it, I don't do much day to day production work from > > the 4.x-current playpen box. I'm heading that way now to take a look > > at it and probably smash it onto my production desktop box if it does > > what you say it does. This latest set of changes to all the whois stuff > > has me a bit in an uproar, with NSI and the RA screwing around with output > > formats all in the same month breaking lots of little shell scripts for > > me my life has been misserable. :-( At least with RA I just had to > > smash in a ripe181 to get the old format back until I can update the > > tools to rpsl :-) > > I'm interested in your comments. I'm trying to tie up all the > outstanding PRs against it, and then I'll merge into -stable. A couple of quick comments, first run some queries on IP addresses only, this use DTRT for ARIN registered addresses, it now returns useless output, and doesn't even point you at anything useful. Second, NIC handle quieries don't work, try \!rwg25. It has far too many options for doing specific registries, granted this is probably better than having to know -h whois.ripe.net or whois -h whois.apnic.net. A lot of this could probably be fixed by fixing data at whois-servers.net, but without further digging into the code and yet another whois server dataset I can't really say. I can say I don't like having: #define NICHOST "whois.crsnic.net" #define INICHOST "whois.networksolutions.com" #define DNICHOST "whois.nic.mil" #define GNICHOST "whois.nic.gov" #define ANICHOST "whois.arin.net" #define RNICHOST "whois.ripe.net" #define PNICHOST "whois.apnic.net" #define RUNICHOST "whois.ripn.net" #define MNICHOST "whois.ra.net" #define QNICHOST_TAIL ".whois-servers.net" that much hard coded DNS data in a binary. A better architecture needs to be found. What is the IETF planning to do about this? Things are getting out of hand in a hurry and finding the right data is getting harder and harder as each day go's buy :-(. I have no problem with an MFC, this code is no more and perhaps even slightly less broken than the code thier now. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 6: 2:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 2920B154E7 for ; Mon, 6 Dec 1999 06:02:21 -0800 (PST) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 5AE8F373C; Mon, 6 Dec 1999 08:02:20 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id IAA07207; Mon, 6 Dec 1999 08:02:20 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Mon, 6 Dec 1999 08:02:20 -0600 (CST) From: Thomas Veldhouse To: Stan Brown Cc: FreeBSD Stable List Subject: Re: How to satrt gnome? In-Reply-To: <199912060351.TAA08799@netcom.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 This really is something that belongs in freebsd-questions, but, you simply have to create an .xsession (if using xdm) or .xinitrc file with "exec gnome-session" in it. Tom Veldhouse veldy@visi.com On Sun, 5 Dec 1999, Stan Brown wrote: > Finally got the Gnome port to build on my laptop. > > Now, how do I set up a given acount to use it? > > -- > Stan Brown stanb@netcom.com 404-996-6955 > Factory Automation Systems > Atlanta Ga. > -- > Look, look, see Windows 95. Buy, lemmings, buy! > Pay no attention to that cliff ahead... Henry Spencer > (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. > > > 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 Dec 6 6:18:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cloudbase.sixforty.co.uk (cloudbase.sixforty.co.uk [194.207.180.10]) by hub.freebsd.org (Postfix) with ESMTP id 3A4AE14A05; Mon, 6 Dec 1999 06:18:37 -0800 (PST) (envelope-from l.farr@epcdirect.co.uk) Received: from monkey (pepe.sixforty.co.uk [194.207.180.202]) by cloudbase.sixforty.co.uk (8.9.3/8.8.7) with SMTP id OAA29576; Mon, 6 Dec 1999 14:02:11 GMT Reply-To: From: "Lawrence Farr" To: Cc: Subject: Samba Performance Date: Mon, 6 Dec 1999 14:17:33 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have installed a couple of FreeBSD machines using 3.3-Release, which have Appletalk over IP and samba access to them. On a write to a shared disk, the Macs can write at about 9000kb/sec (Measured with Helios LAN test). From a P3-500 via samba over switched fast ethernet I get about 100Kb/sec. to the same disk. I have added the usual socket options, and upped the recieve buffer size. On a read from the same machine, it is comparable to the Mac. The same machine running Linux was about equal on both. I have also made samba from source, which made no difference. Any bright ideas? Lawrence Farr EPC Direct T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 6:28:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from atlantis.corbe.net (surf945.pompano.net [24.129.31.45]) by hub.freebsd.org (Postfix) with ESMTP id 9D56114F99 for ; Mon, 6 Dec 1999 06:28:32 -0800 (PST) (envelope-from corbe@corbe.net) Received: from localhost (corbe@localhost) by atlantis.corbe.net (8.9.3/8.9.3) with ESMTP id JAA53966 for ; Mon, 6 Dec 1999 09:28:30 -0500 (EST) (envelope-from corbe@corbe.net) Date: Mon, 6 Dec 1999 09:28:30 -0500 (EST) From: Daniel Corbe To: freebsd-stable@freebsd.org Subject: Gnome in -STABLE 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 tried to install gnome on a workstation running 3.3-STABLE and configure via dhclient. When I go to start gnome via gnome-session I get the following errors, what can I do to correct this? Dec 6 09:24:25 /kernel: arplookup 127.0.0.1 failed: could not allocate llinfo Dec 6 09:24:25 /kernel: arpresolve: can't allocate llinfo for 127.0.0.1rt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 7:21:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ipt2.iptelecom.net.ua (ipt2.iptelecom.net.ua [212.9.224.2]) by hub.freebsd.org (Postfix) with ESMTP id 7A6E314DA6; Mon, 6 Dec 1999 07:21:25 -0800 (PST) (envelope-from sobomax@altavista.net) Received: from vega.vega.com (dialup7-8.iptelecom.net.ua [212.9.227.136]) by ipt2.iptelecom.net.ua (8.9.3/8.9.3) with ESMTP id QAA26623; Mon, 6 Dec 1999 16:59:03 +0200 (EET) Received: from altavista.net (big_brother.vega.com [192.168.1.1]) by vega.vega.com (8.9.3/8.9.3) with ESMTP id QAA55100; Mon, 6 Dec 1999 16:52:38 +0200 (EET) (envelope-from sobomax@altavista.net) Message-ID: <384BCDB1.BD599C68@altavista.net> Date: Mon, 06 Dec 1999 16:52:33 +0200 From: Maxim Sobolev Reply-To: sobomax@altavista.net Organization: Vega International Capital X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: uk,ru,en MIME-Version: 1.0 To: l.farr@epcdirect.co.uk Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Samba Performance References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lawrence Farr wrote: > I have installed a couple of FreeBSD machines using 3.3-Release, which have > Appletalk over IP and samba access to them. On a write to a shared disk, the > Macs can write at about 9000kb/sec (Measured with Helios LAN test). From a > P3-500 via samba over switched fast ethernet I get about 100Kb/sec. to the > same disk. > > I have added the usual socket options, and upped the recieve buffer size. On > a read from the same machine, it is comparable to the Mac. > > The same machine running Linux was about equal on both. I have also made > samba from source, which made no difference. > > Any bright ideas? Try to look into the ports/samba/patches for the patch-ah file (which provided to resolve such misbehaviour). If that file doesn't exist than either try to cvsup your ports, or manually add following patch and recompile/reinstall samba: -----patch.ah. Cut Here------------ --- lib/util_sock.c.orig Wed Sep 22 10:52:50 1999 +++ lib/util_sock.c Wed Sep 22 11:30:18 1999 @@ -28,6 +28,9 @@ extern int sslFd; #endif /* WITH_SSL */ +#undef MSG_WAITALL +#define MSG_WAITALL 0 + extern int DEBUGLEVEL; BOOL passive = False; -----patch.ah. Cut Here------------ -Maxim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 8: 6: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id 2AC9014D3F for ; Mon, 6 Dec 1999 08:06:04 -0800 (PST) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id LAA49823; Mon, 6 Dec 1999 11:05:34 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Mon, 6 Dec 1999 11:05:34 -0500 (EST) From: Adam To: Lawrence Farr Cc: stable@FreeBSD.ORG Subject: Re: Samba Performance 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 (current crossposting removed from cc because it has no relevance) What version of samba? On Mon, 6 Dec 1999, Lawrence Farr wrote: >I have installed a couple of FreeBSD machines using 3.3-Release, which have >Appletalk over IP and samba access to them. On a write to a shared disk, the >Macs can write at about 9000kb/sec (Measured with Helios LAN test). From a >P3-500 via samba over switched fast ethernet I get about 100Kb/sec. to the >same disk. > >I have added the usual socket options, and upped the recieve buffer size. On >a read from the same machine, it is comparable to the Mac. > >The same machine running Linux was about equal on both. I have also made >samba from source, which made no difference. > >Any bright ideas? > >Lawrence Farr >EPC Direct T:01179666123 F:01179666111 M:07970780901 > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 11:15:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from atlantis.corbe.net (surf945.pompano.net [24.129.31.45]) by hub.freebsd.org (Postfix) with ESMTP id 21708153AE for ; Mon, 6 Dec 1999 11:14:42 -0800 (PST) (envelope-from corbe@corbe.net) Received: from localhost (corbe@localhost) by atlantis.corbe.net (8.9.3/8.9.3) with ESMTP id MAA54208; Mon, 6 Dec 1999 12:01:57 -0500 (EST) (envelope-from corbe@corbe.net) Date: Mon, 6 Dec 1999 12:01:57 -0500 (EST) From: Daniel Corbe To: Kalle Andersson Cc: freebsd-stable@freebsd.org Subject: Re: Gnome in -STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How do I go about fixing it though? On Mon, 6 Dec 1999, Kalle Andersson wrote: > It seems like it's trying to resolve the MAC adress of your loopback > device... Which probably ain't what you want. >=20 > -- > Med v=E4nlig h=E4lsning > Kalle Andersson > kalle@sslug.dk >=20 >=20 > On Mon, 6 Dec 1999, Daniel Corbe wrote: >=20 > >=20 > > I tried to install gnome on a workstation running 3.3-STABLE and > > configure via dhclient. When I go to start gnome via gnome-session I g= et > > the following errors, what can I do to correct this? > >=20 > > Dec 6 09:24:25 /kernel: arplookup 127.0.0.1 failed: could not allocat= e llinfo > > Dec 6 09:24:25 /kernel: arpresolve: can't allocate llinfo for 127.0.0= =2E1rt > >=20 > >=20 > >=20 > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > >=20 >=20 >=20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 12: 1: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 1336E1508A for ; Mon, 6 Dec 1999 11:59:40 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id TAA29393; Mon, 6 Dec 1999 19:59:31 GMT (envelope-from joe) Date: Mon, 6 Dec 1999 19:59:30 +0000 From: Josef Karthauser To: Szilveszter Adam Cc: FreeBSD-Stable@FreeBSD.ORG Subject: Re: Little whois patch. Message-ID: <19991206195930.A28224@florence.pavilion.net> References: <19991205230450.D90126@florence.pavilion.net> <199912052327.PAA88161@gndrsh.dnsmgr.net> <19991205233618.A8928@florence.pavilion.net> <19991206072618.A5763@petra.hos.u-szeged.hu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991206072618.A5763@petra.hos.u-szeged.hu> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 06, 1999 at 07:26:18AM +0100, Szilveszter Adam wrote: > > So, I am sending the man page patch again...it is against whois.1 ver 1.9 > but should apply to 1.10 as well... > Applied, thanks. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 12:54:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sslug.dk (sslug.imm.dtu.dk [192.38.71.98]) by hub.freebsd.org (Postfix) with SMTP id B280915F9C for ; Mon, 6 Dec 1999 12:50:21 -0800 (PST) (envelope-from kalle@sslug.dk) Received: (qmail 20515 invoked from network); 6 Dec 1999 16:50:19 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 6 Dec 1999 16:50:19 -0000 Date: Mon, 6 Dec 1999 17:50:19 +0100 (CET) From: Kalle Andersson To: Daniel Corbe Cc: freebsd-stable@freebsd.org Subject: Re: Gnome in -STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems like it's trying to resolve the MAC adress of your loopback device... Which probably ain't what you want. -- Med vänlig hälsning Kalle Andersson kalle@sslug.dk On Mon, 6 Dec 1999, Daniel Corbe wrote: > > I tried to install gnome on a workstation running 3.3-STABLE and > configure via dhclient. When I go to start gnome via gnome-session I get > the following errors, what can I do to correct this? > > Dec 6 09:24:25 /kernel: arplookup 127.0.0.1 failed: could not allocate llinfo > Dec 6 09:24:25 /kernel: arpresolve: can't allocate llinfo for 127.0.0.1rt > > > > 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 Dec 6 13: 2:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sstar.com (sstar.com [209.102.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 5603E15C03 for ; Mon, 6 Dec 1999 13:02:20 -0800 (PST) (envelope-from king@sstar.com) Received: from JKING ([134.132.75.164]) by sstar.com with ESMTP (IPAD 2.52) id 8820300; Mon, 06 Dec 1999 15:02:19 -0600 Message-Id: <4.2.0.58.19991206150137.00a47428@mail.sstar.com> X-Sender: king@mail.sstar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 06 Dec 1999 15:02:18 -0600 To: Kalle Andersson , Daniel Corbe From: Jim King Subject: Re: Gnome in -STABLE Cc: freebsd-stable@freebsd.org In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1"; format=flowed Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG More probably, lo0 isn't configured in /etc/rc.conf. Make sure lo0 is=20 included in the list of network interfaces in /etc/rc.conf. Jim At 05:50 PM 12/6/1999 +0100, Kalle Andersson wrote: >It seems like it's trying to resolve the MAC adress of your loopback >device... Which probably ain't what you want. > >-- >Med v=E4nlig h=E4lsning >Kalle Andersson >kalle@sslug.dk > > >On Mon, 6 Dec 1999, Daniel Corbe wrote: > > > > > I tried to install gnome on a workstation running 3.3-STABLE and > > configure via dhclient. When I go to start gnome via gnome-session I= get > > the following errors, what can I do to correct this? > > > > Dec 6 09:24:25 /kernel: arplookup 127.0.0.1 failed: could not=20 > allocate llinfo > > Dec 6 09:24:25 /kernel: arpresolve: can't allocate llinfo for= 127.0.0.1rt > > > > > > > > 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 13: 9:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from www.pramool.com (pramool.com [203.150.3.216]) by hub.freebsd.org (Postfix) with ESMTP id 893D914A1E for ; Mon, 6 Dec 1999 13:09:46 -0800 (PST) (envelope-from yongy@www.pramool.com) Received: (from yongy@localhost) by www.pramool.com (8.9.3/8.9.3) id DAA18451 for freebsd-stable@FreeBSD.org; Tue, 7 Dec 1999 03:20:46 +0700 (ICT) (envelope-from yongy) Date: Tue, 7 Dec 1999 03:20:46 +0700 (ICT) From: "Nartpong A." Message-Id: <199912062020.DAA18451@www.pramool.com> To: freebsd-stable@FreeBSD.org Subject: subscribe Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: 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 Dec 6 13:50:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id 95B8114FA0 for ; Mon, 6 Dec 1999 13:50:50 -0800 (PST) (envelope-from rb@gid.co.uk) Received: from gid.co.uk (uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id VAA83347; Mon, 6 Dec 1999 21:50:49 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] by seagoon.gid.co.uk; Mon, 6 Dec 1999 21:37:33 GMT X-Sender: rb@194.32.164.1 Message-Id: In-Reply-To: <19991206074002.B5763@petra.hos.u-szeged.hu> References: ; from doconnor@gsoft.com.au on Mon, Dec 06, 1999 at 05:24:24PM +1030 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 6 Dec 1999 21:37:31 +0000 To: Szilveszter Adam From: Bob Bishop Subject: Re: Out of swap hangs machine Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, At 7:40 am +0100 6/12/99, Szilveszter Adam wrote: >On 06-Dec-99 Alexandr Listopad wrote: >> 11M free of mem, and 130M free of swap.... ;) And my FreeBSD never used >> swap... as I see on "top". >> >> Question: why it should be "...2x your RAM.." ??? >It is essentially an old rule of thumb but it should be adjusted according >to your site's requirements. It was also said that above 64M RAM swap is not >strictly necessary[etc] But bear in mind that swap > RAM is required if you ever want to take a crash dump. -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 15:34:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from scrabble.freeuk.net (scrabble.freeuk.net [212.126.144.6]) by hub.freebsd.org (Postfix) with ESMTP id 83F8D14F96 for ; Mon, 6 Dec 1999 15:34:04 -0800 (PST) (envelope-from andrew@ukug.uk.FreeBSD.org) Received: from [212.126.147.248] (helo=cream.org) by scrabble.freeuk.net with esmtp (Exim 2.11 #1) id 11v7dh-00042A-00; Mon, 6 Dec 1999 23:33:53 +0000 Content-Length: 553 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 06 Dec 1999 23:33:30 -0000 (GMT) From: Andrew Boothman To: jkh@zippy.cdrom.com Subject: Re: Anticipated release date for 3.4 Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan, Do we have an estimated date for the shipping of the CD Sets from Walnut Creek, for 3.4-R? Thanks! On 05-Dec-99 Andre LeClaire wrote: > Will be December 15th. The traditional code slush will go into effect > on the 1st. November would be an excellent month for merging your > changes, after which I'll be exercising my usual perogative of > inspecting all potential changes with a more jaundiced eye. :) --- Andrew Boothman FreeBSD UK User Group http://ukug.uk.FreeBSD.org/~andrew/ http://ukug.uk.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 Dec 6 15:34:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from scrabble.freeuk.net (scrabble.freeuk.net [212.126.144.6]) by hub.freebsd.org (Postfix) with ESMTP id EFC4915081 for ; Mon, 6 Dec 1999 15:34:09 -0800 (PST) (envelope-from andrew@ukug.uk.FreeBSD.org) Received: from [212.126.147.248] (helo=cream.org) by scrabble.freeuk.net with esmtp (Exim 2.11 #1) id 11v7dj-00042C-00; Mon, 6 Dec 1999 23:33:56 +0000 Content-Length: 329 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 06 Dec 1999 23:33:32 -0000 (GMT) From: Andrew Boothman To: "Daniel O'Connor" Subject: RE: Parallel port ZIP drive? Cc: (FreeBSD Stable List) , Cc: (FreeBSD Stable List) , Stan Brown Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 06-Dec-99 Daniel O'Connor wrote: > BTW this sort of question belongs on freebsd-questions. And is also in the FAQ. Where everyone should really check before asking a question on any list. --- Andrew Boothman FreeBSD UK User Group http://ukug.uk.FreeBSD.org/~andrew/ http://ukug.uk.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 Dec 6 17:15:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id DE73415129 for ; Mon, 6 Dec 1999 17:15:49 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02342; Mon, 6 Dec 1999 17:14:43 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Andrew Boothman Cc: stable@FreeBSD.ORG Subject: Re: Anticipated release date for 3.4 In-reply-to: Your message of "Mon, 06 Dec 1999 23:33:30 GMT." Date: Mon, 06 Dec 1999 17:14:43 -0800 Message-ID: <2339.944529283@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Estimated? December 23rd. Or maybe December 27th, depending on how we do at getting it in before the holidays start. - Jordan > Jordan, > > Do we have an estimated date for the shipping of the CD Sets from Walnut Cree k, > for 3.4-R? > > Thanks! > > On 05-Dec-99 Andre LeClaire wrote: > > Will be December 15th. The traditional code slush will go into effect > > on the 1st. November would be an excellent month for merging your > > changes, after which I'll be exercising my usual perogative of > > inspecting all potential changes with a more jaundiced eye. :) > > --- > Andrew Boothman > FreeBSD UK User Group > http://ukug.uk.FreeBSD.org/~andrew/ > http://ukug.uk.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 Dec 6 18:26:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ln.edu.hk (mail.ln.edu.hk [202.40.192.253]) by hub.freebsd.org (Postfix) with ESMTP id C3F5314BC4 for ; Mon, 6 Dec 1999 18:26:32 -0800 (PST) (envelope-from ttdsuen@ln.edu.hk) Received: from descartes (descartes.ln.edu.hk [202.40.193.49]) by mail.ln.edu.hk (8.9.3/8.9.3) with SMTP id KAA10777 for ; Tue, 7 Dec 1999 10:26:08 +0800 Message-ID: <000801bf405a$8339c9a0$31c128ca@ln.edu.hk> From: "Daniel Suen" To: Subject: Date: Tue, 7 Dec 1999 10:26:41 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01BF409D.8D771CE0" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_0005_01BF409D.8D771CE0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable ------=_NextPart_000_0005_01BF409D.8D771CE0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
 
------=_NextPart_000_0005_01BF409D.8D771CE0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 19:55:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.sprawlnet.com (ns1.sprawlnet.com [208.224.169.130]) by hub.freebsd.org (Postfix) with ESMTP id AF0BF14F12 for ; Mon, 6 Dec 1999 19:55:14 -0800 (PST) (envelope-from mike@sprawlnet.com) Received: from bsd.unixvillain.com (mikes@1Cust13.tnt9.atl2.da.uu.net [63.20.23.13]) by ns1.sprawlnet.com (8.9.3/8.9.2) with SMTP id LAA12870 for ; Tue, 7 Dec 1999 11:57:11 -0500 (EST) (envelope-from mike@sprawlnet.com) From: Mike Steinfeld To: freebsd-stable@freebsd.org Subject: ppp seems to disconnect every 10 minutes? Date: Mon, 6 Dec 1999 16:53:48 -0500 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99120616580900.12599@bsd.unixvillain.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, I have multiple dialup accounts and it does not matter which one i am using after about being connected fro aprx 10 minutes, my connection keep dropping and its really starting to get on ym nerves. Anyone have any ideas what maybe the cause of this. I has never happened before on any other of my freeBSd box's jsut this one imarticular. any suggestions or help would greatly be appreciated, thanks, mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 20:11:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.sprawlnet.com (ns1.sprawlnet.com [208.224.169.130]) by hub.freebsd.org (Postfix) with ESMTP id 5BBDC14BE7 for ; Mon, 6 Dec 1999 20:11:29 -0800 (PST) (envelope-from mike@freebsdbox.com) Received: from freebsdbox.com (mikes@1Cust13.tnt9.atl2.da.uu.net [63.20.23.13]) by ns1.sprawlnet.com (8.9.3/8.9.2) with ESMTP id MAA12900 for ; Tue, 7 Dec 1999 12:13:27 -0500 (EST) (envelope-from mike@freebsdbox.com) Message-ID: <384C3631.FFB9121E@freebsdbox.com> Date: Mon, 06 Dec 1999 17:18:26 -0500 From: Mike Steinfeld X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: ppp connection drops after 10 minutes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, I have multiple dialup accounts and it does not matter which one i am using after about being connected for aprox 10 minutes, my connection keep dropping and its really starting to get on my nerves. Anyone have any ideas what maybe the cause of this. I has never happened before on any other of my freeBSd box's just this one imparticular. any suggestions or help would greatly be appreciated, oh on another note it started happening about a week or so a go. This box has been up for at least 3 weeks. thanks, mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 6 20:13:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id A683A14BE7 for ; Mon, 6 Dec 1999 20:13:17 -0800 (PST) (envelope-from brameld@twave.net) Received: from [208.219.234.30] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id da289695 for ; Mon, 6 Dec 1999 23:12:55 -0500 Message-ID: <384C8969.4333AF1C@twave.net> Date: Mon, 06 Dec 1999 23:13:29 -0500 From: Walter Brameld X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Steinfeld Cc: freebsd-stable@freebsd.org Subject: Re: ppp seems to disconnect every 10 minutes? References: <99120616580900.12599@bsd.unixvillain.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Steinfeld wrote: > hi all, > > I have multiple dialup accounts and it does not matter which one i am using > after about being connected fro aprx 10 minutes, my connection keep dropping > and its really starting to get on ym nerves. > > Anyone have any ideas what maybe the cause of this. I has never happened before > on any other of my freeBSd box's jsut this one imarticular. > > any suggestions or help would greatly be appreciated, > > thanks, > mike > > In your /etc/ppp/ppp.conf file in the #defaults section, make sure you have a line that says "set timeout 0". I think the default is set to disconnect your connection after ten minutes. Walter Brameld To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 1:14:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id C294714D79 for ; Tue, 7 Dec 1999 01:14:53 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id BAA03221; Tue, 7 Dec 1999 01:13:37 -0800 (PST) Date: Tue, 7 Dec 1999 01:13:37 -0800 (PST) From: Annelise Anderson To: Martin McFlySr Cc: freebsd-stable@FreeBSD.ORG Subject: Re: simple question - make world without named In-Reply-To: <11845.991205@McFlySr.Kurgan.Ru> 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, 5 Dec 1999, Martin McFlySr wrote: > Hello freebsd-stable@FreeBSD.ORG, > > How can i run (or what i must do) make world, for no update (re-install), > for example, named? > > Last stable version from ISC - 8.2.2-P5, but after "make world" named 8.1.2 > version going back :( > > simple edit /usr/src/usr.sbin/Makefile and comment directories with named? > or exis better way? You could try commenting those directories. It might be safer to delete those lines altogether, however, since the \ at the end of the lines continues the listing as if the directories were all on a line. A comment might therefore include everything to the end of the entire listing. You would probably want to comment ndc as well as the three named directories, as this is the control program for named and might be different in this version from the one you have. If this answer isn't quite right, someone else will no doubt jump in to correct it. Annelise > > Thank you. > > -- > Sunday, December 05, 1999, > 20:13 > > Best regards from future, > Martin McFlySr, HillDale. > > > > > 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 Tue Dec 7 2:57:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gate.criticalsoftware.com (gate.criticalsoftware.com [195.23.8.69]) by hub.freebsd.org (Postfix) with ESMTP id 1802A14C4F for ; Tue, 7 Dec 1999 02:57:17 -0800 (PST) (envelope-from raposo@criticalsoftware.com) Received: from milmi (milmi.critical.pt [192.168.3.100]) by gate.criticalsoftware.com (8.9.0/8.9.0) with SMTP id KAA15091 for ; Tue, 7 Dec 1999 10:52:07 GMT Received: by localhost with Microsoft MAPI; Tue, 7 Dec 1999 10:57:44 -0000 Message-ID: <01BF40A1.E3D73F30.raposo@criticalsoftware.com> From: Antonio Raposo Reply-To: "raposo@criticalsoftware.com" To: "'freebsd-stable@FreeBSD.ORG'" Subject: Date: Tue, 7 Dec 1999 10:57:42 -0000 Organization: Critical Software X-Mailer: Microsoft Internet E-mail/MAPI - 8.0.0.4211 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG auth ecb28cf7 subscribe freebsd-stable raposo@criticalsoftware.com Ant=F3nio Raposo Critical Software Rua Pedro Nunes Instituto Pedro Nunes 3030 - 199 Coimbra, Portugal Tel: +351 (239) 700945 / Fax: +351 (239) 700905 mailto:raposo@criticalsoftware.com http://www.criticalsoftware.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 7 3:51:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from albedo1.sio.ecp.fr (sio-gw.ens.ecp.fr [138.195.50.52]) by hub.freebsd.org (Postfix) with ESMTP id E1BA714E49 for ; Tue, 7 Dec 1999 03:51:21 -0800 (PST) (envelope-from dgt@srv-sio.sio.ecp.fr) Received: from srv-sio.sio.ecp.fr (srv-sio.sio.ecp.fr [138.195.52.3]) by albedo1.sio.ecp.fr (8.8.7/8.8.7) with ESMTP id MAA29249 for ; Tue, 7 Dec 1999 12:52:56 +0100 Received: (from dgt@localhost) by srv-sio.sio.ecp.fr (8.9.3/8.9.3) id MAA69597 for freebsd-stable@FreeBSD.ORG; Tue, 7 Dec 1999 12:53:31 +0100 (CET) (envelope-from dgt) Date: Tue, 7 Dec 1999 12:53:31 +0100 From: Didier GILLET To: freebsd-stable@FreeBSD.ORG Subject: question about make installworld Message-ID: <19991207125331.A69583@srv-sio.sio.ecp.fr> Reply-To: gilletd9@cti.ecp.fr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD srv-sio.sio.ecp.fr 3.3-STABLE FreeBSD 3.3-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hello, after a make buildworld, how can i change the root target directory for making an installworld not on / but somewhere else (let's say /test) TIA Didier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 4: 3: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mx.nkm.lt (mx.nkm.lt [193.219.211.9]) by hub.freebsd.org (Postfix) with SMTP id 409EE14CA3 for ; Tue, 7 Dec 1999 04:02:57 -0800 (PST) (envelope-from midom@dammit.lt) Received: (qmail 16725 invoked by uid 1073); 7 Dec 1999 12:02:55 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 7 Dec 1999 12:02:55 -0000 Date: Tue, 7 Dec 1999 14:02:55 +0200 (EET) From: Domas Mituzas X-Sender: midom@mx.nkm.lt To: Bob Bishop Cc: Szilveszter Adam , freebsd-stable@FreeBSD.ORG Subject: Re: Out of swap hangs machine 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 Hello to all, maybe I missed some discussion, but out-of-swap can occur during large email delivery (e.g. if you accept huge email messages, you should know, that for example procmail uses ~twice the memory the message takes). So one or several email messages can cause your system crash, if you do not have enough swap. Even mail servers, that have 64megs of ram should have at least 200 megs of swap. If the out of memory occurs, such proccesses will stop working properly, even if memory usage decreases: qmail (qmail-lspawn hangs) apache (root process core dump) inetd (dumb errors in front of every connection :-) mysqld (core dump - malloc not working) etc So, just few words about stability. I reported to apache and made a small patch for inetd, as error messages as "inetd in realloc()" will make POP3 and other protocols not working. With respect, Domas Mituzas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 4:19:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from www.menzor.org (themoonismadeofgreenchease.dk [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id A492514CC1 for ; Tue, 7 Dec 1999 04:19:47 -0800 (PST) (envelope-from morten@seeberg.dk) Received: from SOS (gw.danadata.com [194.239.79.3]) by www.menzor.org (8.8.8/8.8.8) with SMTP id OAA17964 for ; Tue, 7 Dec 1999 14:37:50 +0100 (CET) (envelope-from morten@seeberg.dk) Message-ID: <030001bf40ad$2febddd0$1600a8c0@SOS> Reply-To: "Morten Seeberg" From: "Morten Seeberg" To: Subject: is -STABLE really stable? Date: Tue, 7 Dec 1999 13:18:29 +0100 Organization: SWAMP MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (When I write STABLE im referring to the STABLE branc of FBSD, when writing stable i mean running stable). From what I understand about STABLE, it´s a branch of RELEASE, but with bugfixes, newly added features, which has been tested in CURRENT? But from my experience, STABLE is often is more unstable than RELEASEs, can this be true? Is it due to the changes which are made on a day-to-day basis on STABLE?? One of my friends said, that the best way to know which STABLE version is truly stable was to follow the stable@freebsd.org mailinglist and watch for which STABLE version there weren´t any problems with. This is very time consuming, so I was wondering, whether there is a way you could let us know, when there is a "good"/"better" STABLE out? Or should I just look at the snapshots, and then whenever there are a larger number of days between 2 snapshots => a stable one, fx: 3.3-19991103-STABLE 3.3-19991104-STABLE 3.3-19991109-STABLE 3.3-19991110-STABLE There is 5 days between 1104 and 1109 and only 1 day between 1109 and 1110, does this mean that 1109 is more stable than 1110? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /\/\orten $eeberg, Systems Consultant @ Merkantildata - Enterprise Solutions #echo 'System Administrators suck :)' > /dev/console To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 4:20: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from www.menzor.org (themoonismadeofgreenchease.dk [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id 5B2AF15038 for ; Tue, 7 Dec 1999 04:19:55 -0800 (PST) (envelope-from ml@seeberg.dk) Received: from SOS (gw.danadata.com [194.239.79.3]) by www.menzor.org (8.8.8/8.8.8) with SMTP id OAA17968 for ; Tue, 7 Dec 1999 14:37:59 +0100 (CET) (envelope-from ml@seeberg.dk) Message-ID: <030101bf40ad$3524d770$1600a8c0@SOS> Reply-To: "Morten Seeberg" From: "Morten Seeberg" To: Subject: is -STABLE really stable? Date: Tue, 7 Dec 1999 13:18:36 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (When I write STABLE im referring to the STABLE branc of FBSD, when writing stable i mean running stable). From what I understand about STABLE, it´s a branch of RELEASE, but with bugfixes, newly added features, which has been tested in CURRENT? But from my experience, STABLE is often is more unstable than RELEASEs, can this be true? Is it due to the changes which are made on a day-to-day basis on STABLE?? One of my friends said, that the best way to know which STABLE version is truly stable was to follow the stable@freebsd.org mailinglist and watch for which STABLE version there weren´t any problems with. This is very time consuming, so I was wondering, whether there is a way you could let us know, when there is a "good"/"better" STABLE out? Or should I just look at the snapshots, and then whenever there are a larger number of days between 2 snapshots => a stable one, fx: 3.3-19991103-STABLE 3.3-19991104-STABLE 3.3-19991109-STABLE 3.3-19991110-STABLE There is 5 days between 1104 and 1109 and only 1 day between 1109 and 1110, does this mean that 1109 is more stable than 1110? ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /\/\orten $eeberg, Systems Consultant @ Merkantildata - Enterprise Solutions #echo 'System Administrators suck :)' > /dev/console To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 4:31:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 7AC5514CC1 for ; Tue, 7 Dec 1999 04:31:16 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id MAA00430; Tue, 7 Dec 1999 12:32:00 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <030101bf40ad$3524d770$1600a8c0@SOS> Date: Tue, 07 Dec 1999 12:31:59 -0000 (GMT) From: "Steve O'Hara-Smith" To: Morten Seeberg Subject: RE: is -STABLE really stable? Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Dec-99 Morten Seeberg wrote: > From what I understand about STABLE, it´s a branch of RELEASE, but with > bugfixes, newly added features, which has been tested in CURRENT? Not quite. Each release is (apart from the N.0 release) is a fixed point on the -stable branch (the N.0 release was off -current for 3.0 and I guess will be for 4.0 too). > But from my experience, STABLE is often is more unstable than RELEASEs, can > this be true? Is it due to the changes which are made on a day-to-day basis > on STABLE?? It can be true, RELEASEs usually follow a beta test period during which the commits are constrained somewhat. STABLE usually contains bug fixes and features merged from current. > One of my friends said, that the best way to know which STABLE version is > truly stable was to follow the stable@freebsd.org mailinglist and watch for > which STABLE version there weren´t any problems with. > This is very time consuming, so I was wondering, whether there is a way you > could let us know, when there is a "good"/"better" STABLE out? Usually it is getting old by the time anybody could know. In theory every checkin should make -stable better (but this is not a perfect world). > There is 5 days between 1104 and 1109 and only 1 day between 1109 and 1110, > does this mean that 1109 is more stable than 1110? No it just means that the snapshot didn't get made for a few days. ------------------------------------------------------- Tell a computer to WIN and ... ... You lose ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 4:40:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from www.menzor.org (themoonismadeofgreenchease.dk [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id 8592514F4E for ; Tue, 7 Dec 1999 04:40:20 -0800 (PST) (envelope-from ml@seeberg.dk) Received: from SOS (gw.danadata.com [194.239.79.3]) by www.menzor.org (8.8.8/8.8.8) with SMTP id OAA18054; Tue, 7 Dec 1999 14:57:08 +0100 (CET) (envelope-from ml@seeberg.dk) Message-ID: <033d01bf40af$e217ac80$1600a8c0@SOS> Reply-To: "Morten Seeberg" From: "Morten Seeberg" To: "Steve O'Hara-Smith" , References: Subject: Re: is -STABLE really stable? Date: Tue, 7 Dec 1999 13:37:48 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----- Original Message ----- From: "Steve O'Hara-Smith" To: "Morten Seeberg" Cc: Sent: Tuesday, December 07, 1999 1:31 PM Subject: RE: is -STABLE really stable? > > But from my experience, STABLE is often is more unstable than RELEASEs, can > > this be true? Is it due to the changes which are made on a day-to-day basis > > on STABLE?? > It can be true, RELEASEs usually follow a beta test period during which > the commits are constrained somewhat. STABLE usually contains bug fixes and > features merged from current. So there is actually really no easy way to stay updated on a production machine (which has to be stable at every cost), because RELEASE is the only actual stable system known the everyday users? Since 3.0 has been out for about a year, why not make more "RELEASE" versions during a year? Or just freeze a few snapshots during the STABLE branch? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 4:51:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from oskar.dev.nanoteq.co.za (oskar.dev.nanoteq.co.za [196.7.114.5]) by hub.freebsd.org (Postfix) with ESMTP id D9A6614F4E for ; Tue, 7 Dec 1999 04:51:39 -0800 (PST) (envelope-from rbezuide@oskar.dev.nanoteq.co.za) Received: (from rbezuide@localhost) by oskar.dev.nanoteq.co.za (8.9.3/8.9.0) id OAA15528; Tue, 7 Dec 1999 14:49:15 +0200 (SAT) From: Reinier Bezuidenhout Message-Id: <199912071249.OAA15528@oskar.dev.nanoteq.co.za> Subject: Re: is -STABLE really stable? In-Reply-To: <033d01bf40af$e217ac80$1600a8c0@SOS> from Morten Seeberg at "Dec 7, 99 01:37:48 pm" To: morten@seeberg.dk Date: Tue, 7 Dec 1999 14:49:15 +0200 (SAT) Cc: steve@pooh.elsevier.nl, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (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 > > > on STABLE?? > > It can be true, RELEASEs usually follow a beta test period during > which > > the commits are constrained somewhat. STABLE usually contains bug fixes > and > > features merged from current. > > So there is actually really no easy way to stay updated on a production > machine (which has to be stable at every cost), because RELEASE is the only > actual stable system known the everyday users? > > Since 3.0 has been out for about a year, why not make more "RELEASE" > versions during a year? Or just freeze a few snapshots during the STABLE > branch? There is a 3.3-RELEASE out ... which is a release :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 4:55:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 8E73914F4E for ; Tue, 7 Dec 1999 04:55:42 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id MAA00451; Tue, 7 Dec 1999 12:56:34 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <033d01bf40af$e217ac80$1600a8c0@SOS> Date: Tue, 07 Dec 1999 12:56:33 -0000 (GMT) From: "Steve O'Hara-Smith" To: Morten Seeberg Subject: Re: is -STABLE really stable? Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Dec-99 Morten Seeberg wrote: > So there is actually really no easy way to stay updated on a production > machine (which has to be stable at every cost), because RELEASE is the only > actual stable system known the everyday users? This is an interesting topic in it's own right. There is a fairly large body of opinion that the right way to treat a production system is never to upgrade it at all, rather to periodically replace it with a well tested replacement using later software. Another view is to track the release stream before -stable (right now that would be 2.x) which continues to get major bug fixes and security fixes for quite a long time after it stops getting features. Another option is to watch the CVS commits on -stable and decide which ones you need and apply them. > Since 3.0 has been out for about a year, why not make more "RELEASE" > versions during a year? Or just freeze a few snapshots during the STABLE > branch? Given a 30 day beta period on each release I think that time does not permit more than three or four releases per year. Freezing snapshots doesn't really help unless they are also heavily tested. ------------------------------------------------------- Tell a computer to WIN and ... ... You lose ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 5:12:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from www.menzor.org (themoonismadeofgreenchease.dk [195.249.147.160]) by hub.freebsd.org (Postfix) with ESMTP id 9DD2014F4E for ; Tue, 7 Dec 1999 05:12:11 -0800 (PST) (envelope-from morten@seeberg.dk) Received: from SOS (gw.danadata.com [194.239.79.3]) by www.menzor.org (8.8.8/8.8.8) with SMTP id PAA18173; Tue, 7 Dec 1999 15:29:01 +0100 (CET) (envelope-from morten@seeberg.dk) Message-ID: <036901bf40b4$5573b300$1600a8c0@SOS> Reply-To: "Morten Seeberg" From: "Morten Seeberg" To: "Steve O'Hara-Smith" , References: Subject: Re: is -STABLE really stable? Date: Tue, 7 Dec 1999 14:09:37 +0100 Organization: SWAMP MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.5600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.5600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Since 3.0 has been out for about a year, why not make more "RELEASE" > > versions during a year? Or just freeze a few snapshots during the STABLE > > branch? > Given a 30 day beta period on each release I think that time does not > permit more than three or four releases per year. Freezing snapshots doesn't > really help unless they are also heavily tested. Revising the release times for 3.0, 3.1, 3.2, 3.3 I know realise that I´ve just misunderstood the way -STABLE works :) And that I should just start using RELEASE on my production machines, instead of -STABLE, which I thought was "better"/"more stable" than RELEASE. Thanx to Steve and Reinier. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 5:20:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 7FBBF15289 for ; Tue, 7 Dec 1999 05:20:24 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id NAA00561; Tue, 7 Dec 1999 13:21:16 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <036901bf40b4$5573b300$1600a8c0@SOS> Date: Tue, 07 Dec 1999 13:21:16 -0000 (GMT) From: "Steve O'Hara-Smith" To: Morten Seeberg Subject: Re: is -STABLE really stable? Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 07-Dec-99 Morten Seeberg wrote: > Revising the release times for 3.0, 3.1, 3.2, 3.3 I know realise that I´ve > just misunderstood the way -STABLE works :) And that I should just start > using RELEASE on my production machines, instead of -STABLE, which I thought > was "better"/"more stable" than RELEASE. Not a bad policy (IMHO). I would suggest looking at the errata files for your chosen release (somtimes problems are found in the first few days of a releases life) and keeping an eye out for security announcements. ------------------------------------------------------- Tell a computer to WIN and ... ... You lose ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 6:30:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from isds.duke.edu (davinci.isds.duke.edu [152.3.22.1]) by hub.freebsd.org (Postfix) with ESMTP id 9B34F14F44 for ; Tue, 7 Dec 1999 06:30:49 -0800 (PST) (envelope-from sto@stat.Duke.EDU) Received: from cayenne.isds.duke.edu (cayenne.isds.duke.edu [152.3.22.11]) by isds.duke.edu (8.8.8/8.8.8) with ESMTP id JAA08182 for ; Tue, 7 Dec 1999 09:30:49 -0500 (EST) Received: (from sto@localhost) by cayenne.isds.duke.edu (8.8.8/8.8.8) id JAA03892 for freebsd-stable@FreeBSD.ORG; Tue, 7 Dec 1999 09:30:49 -0500 (EST) Date: Tue, 7 Dec 1999 09:30:48 -0500 From: "Sean O'Connell" To: FreeBSD stable Subject: /sbin/dhclient-script and llinfo error Message-ID: <19991207093048.W1667@stat.Duke.EDU> Reply-To: "Sean O'Connell" Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Organization: Institute of Statistics and Decision Sciences Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi- There was an email on -current regarding the /sbin/dhclient-script which can cause an llinfo error because the script tries to set a route to localhost--which according to the email is automagically handled by the kernel. The way to solve this problem was to delete the references to "route add xxx 127.0.0.1". The author is Luoqi Chen and the Message-ID is <199911192156.QAA02988@lor.watermarkgroup.com>. Is there any chance of this making 3.4? I looked at the latest versions of sys/contrib/isc-dhcp/client/scripts/freebsd and the route statements are still there. I recommended commenting out the references to 127.1 to the author of the email with subject "Gnome in -STABLE", and it seemed to have helped. Oddly enough, this doesn't seem to affect my home machine (a not so -current box as of November) at all. Thanks, S ----------------------------------------------------------------------- Sean O'Connell Email: sean@stat.Duke.EDU Institute of Statistics and Decision Sciences Phone: (919) 684-5419 Duke University Fax: (919) 684-8594 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 8:24:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from po3.glue.umd.edu (po3.glue.umd.edu [128.8.10.123]) by hub.freebsd.org (Postfix) with ESMTP id 621A1154D5 for ; Tue, 7 Dec 1999 08:24:26 -0800 (PST) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.220.99]) by po3.glue.umd.edu (8.9.3/8.9.3) with ESMTP id LAA14910; Tue, 7 Dec 1999 11:24:22 -0500 (EST) Message-ID: <384D349A.10B7CC4C@glue.umd.edu> Date: Tue, 07 Dec 1999 11:23:54 -0500 From: Brandon Fosdick X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Sean O'Connell" Cc: FreeBSD stable Subject: Re: /sbin/dhclient-script and llinfo error References: <19991207093048.W1667@stat.Duke.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean O'Connell wrote: > > Hi- > > There was an email on -current regarding the /sbin/dhclient-script which > can cause an llinfo error because the script tries to set a route to > localhost--which according to the email is automagically handled by > the kernel. > > The way to solve this problem was to delete the references > to "route add xxx 127.0.0.1". > > The author is Luoqi Chen and > the Message-ID is <199911192156.QAA02988@lor.watermarkgroup.com>. > > Is there any chance of this making 3.4? I looked at the latest > versions of sys/contrib/isc-dhcp/client/scripts/freebsd and the > route statements are still there. > > I recommended commenting out the references to 127.1 to the author > of the email with subject "Gnome in -STABLE", and it seemed to have > helped. > > Oddly enough, this doesn't seem to affect my home machine > (a not so -current box as of November) at all. > > Thanks, > S I asked the same question abot a month ago and didn't get an answer. A quick search of the archives will find some others with the same problem. It seems to be a very old problem, I wonder why no one has fixed it. Maybe it needs to be send-pr'd... -Brandon -- bfoz@glue.umd.edu "Lead, follow, or get run over" "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 9:54:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id C2F0114C99; Tue, 7 Dec 1999 09:54:48 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id MAA215194; Tue, 7 Dec 1999 12:54:46 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Tue, 7 Dec 1999 13:00:33 -0500 To: current@FreeBSD.ORG, stable@FreeBSD.ORG From: Garance A Drosihn Subject: [PATCHES] Two fixes for lpd/lpc for review and test Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, here's my third attempt to get someone to at least acknowledge some minor patches for lpd. The patches are also covered in PR's, as noted in the previous attempts. My theory is that my previous attempts had a subject which made it sound like I was looking for someone to *make* some fixes, as opposed to the fact that I already have fixes for these known bugs and I thought someone with commit privs might want to apply them to the official distribution. In my next installment, I'm going to try a subject of "Make Money Fast via Sex With Green Card Lawyers" Although with this crowd I'd probably have better luck with something like: "I have vmware running native on FreeBSD 3.2-release"... While I'm at it, I'd like to note another patch for lpd which looked interesting. This one might be a bit too risky to get into 3.4-release, but it would be nice to at least add it to current. To quote from another message: - - - Date: Mon, 22 Nov 1999 20:08:13 +0100 From: Andre Albsmeier Subject: Enhancement for lpr (maybe for STABLE-3.4) A while ago I sent a PR containing an enhancement for lpr -r for the case that the file to be printed is on the same filesystem as lpd's spooling directory. The PR is bin/11997 and can be found at: http://www.freebsd.org/cgi/query-pr.cgi?pr=11997 Maybe someone can look at it, review it and eventually commit it to -STABLE (and current, of course). The patch now runs nearly 2 years without problems and saves quite a lot of time when printing large temporay files. - - - Note that the above patch not only saves time, but reduces the amount of disk space needed in a print-spooling partition. That may not seem like much of an issue when you're printing 10-Kbyte files, but when you're throwing around 200-Meg files (for color plotters, for instance), then it can be very nice. The text from my previous attempts follow. - - - - - - - - - - - - - - - - - - - - - - - - - At 5:04 PM -0500 11/20/99, Garance A Drosihn wrote: >Back when we were closing in on the release date for 3.3, I sent >the following message. As we now close in on the release date >for 3.4, I thought I'd send it again, seeing that both of the >problem reports are still marked "open", and neither of the two >patches have been applied yet. (not even to current) > >These are both pretty tiny minor lovable cuddly changes... Any >chance of getting them in for 3.4? > >Note that problem report bin/12912 probably depends on what >umask is set when lpd starts up. The pr says "the problem >doesn't seem to be reproducible", but reproducing the problem >may depend on someone making a change elsewhere. Given that >lpd uses the actual access-bit settings to govern it's behavior, >then it should make sure the exactly-correct bit settings are >set up when it creates the file. > >Also note that the fix for bin/9362, sent in as bin/13549, >is also confirmed in bin/14975. > >>Date: Mon, 6 Sep 1999 18:14:55 -0500 >>To: current@FreeBSD.org >>From: Garance A Drosihn >>Subject: Two fixes for lpd/lpc (printing) >>Cc: kheuer@gwdu60.gwdg.de >> >>I noticed problem-report bin/9362, which reported that the >>'lpc start' command no longer works. (it claims to start >>the queue, but it doesn't actually start it). >> >>I came up with a two or three line fix for that bug, and >>sent it in as problem-report bin/13549. This patch should >>work on both freebsd-current and freebsd-stable. >> >>I also noticed problem report bin/12912. This PR includes >>a patch to make sure that if a lockfile does not already >>exist, then it will be created such that the queue is both >>"enabled" and "started". I have not tried this exact patch >>yet, but here at RPI we've had a similar patch to lpd for a >>long time. We add printer queues to a master printcap file, >>which is then copied to a few hundred workstations. We really >>don't want to have to run around all those workstations to >>'enable' and 'start' a queue that we have just added. Perhaps >>we have a different 'umask' setting when lpd starts up than >>most freebsd sites do... >> >>Could some other people try these simple patches, and see >>how well they work? I am hoping these could make it into >>the next official release, although I realize that time is >>rapidly running out for that! :-) > >--- >Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu >Senior Systems Programmer or drosih@rpi.edu >Rensselaer Polytechnic Institute --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 10:30: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 7E3E914E3E for ; Tue, 7 Dec 1999 10:30:00 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id KAA04748 for ; Tue, 7 Dec 1999 10:26:17 -0800 (PST) X-Received: from phoenix.kurgan.ru (phoenix.kurgan.ru [195.54.28.21]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id CAA03452 for ; Tue, 7 Dec 1999 02:38:32 -0800 (PST) X-Received: from hilldale.kurgan.ru (hilldale.kurgan.ru [195.54.28.11]) by phoenix.kurgan.ru (8.9.3/8.9.3) with ESMTP id PAA12394 for ; Tue, 7 Dec 1999 15:38:24 +0500 (ES) Date: Tue, 7 Dec 1999 15:37:26 +0500 From: Martin McFlySr Reply-To: Martin McFlySr Organization: Back To The Future X-Priority: 3 (Normal) Message-ID: <3651.991207@McFlySr.Kurgan.Ru> To: Annelise Anderson Subject: Re[2]: simple question - make world without named In-reply-To: References: 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 Hello Annelise Anderson, Tuesday, December 07, 1999, 14:13:37, you wrote: AA> You could try commenting those directories. But after "cvsup" this directories is back in /usr/src/usr.sbin/Makefile :((( And automitic "cvsup"/"make world" lost him "automatic" property :((( This question still actually ... Anybody know, how i can do this? Thank you, -- Tuesday, December 07, 1999, 15:34 Best regards from future, Martin McFlySr, HillDale. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 12:22:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 8B8A014BFC; Tue, 7 Dec 1999 12:22:42 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id MAA28281; Tue, 7 Dec 1999 12:22:24 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda28279; Tue Dec 7 12:22:17 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id MAA02186; Tue, 7 Dec 1999 12:22:16 -0800 (PST) Message-Id: <199912072022.MAA02186@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdzo2178; Tue Dec 7 12:21:36 1999 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.3-RELEASE X-Sender: cschuber To: Garance A Drosihn Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: [PATCHES] Two fixes for lpd/lpc for review and test In-reply-to: Your message of "Tue, 07 Dec 1999 13:00:33 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 07 Dec 1999 12:21:35 -0800 From: Cy Schubert Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Garance A Drosihn writes: I've been using the patch from PR 13549 on 4 -stable stable machines for about 3 weeks with no ill effects -- and it fixes the problem. > In my next installment, I'm going to try a subject of > "Make Money Fast via Sex With Green Card Lawyers" You can get screwed by a lawyer without sex. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 13: 6:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id B097F14CCC; Tue, 7 Dec 1999 13:06:51 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id OAA43444; Tue, 7 Dec 1999 14:06:49 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id OAA44391; Tue, 7 Dec 1999 14:06:49 -0700 (MST) Message-Id: <199912072106.OAA44391@harmony.village.org> To: Garance A Drosihn Subject: Re: [PATCHES] Two fixes for lpd/lpc for review and test Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 07 Dec 1999 13:00:33 EST." References: Date: Tue, 07 Dec 1999 14:06:49 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been reviewing this patch with someone and I think the last version is ready to commit. I'll take a look at my tree to make sure. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 13:44:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ares.maths.adelaide.edu.au (ares.maths.adelaide.edu.au [129.127.246.5]) by hub.freebsd.org (Postfix) with ESMTP id A017514D0E; Tue, 7 Dec 1999 13:44:25 -0800 (PST) (envelope-from glewis@ares.maths.adelaide.edu.au) Received: (from glewis@localhost) by ares.maths.adelaide.edu.au (8.9.3/8.9.3) id IAA47852; Wed, 8 Dec 1999 08:14:02 +1030 (CST) (envelope-from glewis) From: Greg Lewis Message-Id: <199912072144.IAA47852@ares.maths.adelaide.edu.au> Subject: Re: Samba Performance In-Reply-To: <384BCDB1.BD599C68@altavista.net> from Maxim Sobolev at "Dec 6, 1999 04:52:33 pm" To: sobomax@altavista.net Date: Wed, 8 Dec 1999 08:14:02 +1030 (CST) Cc: l.farr@epcdirect.co.uk, stable@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL56 (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 > Try to look into the ports/samba/patches for the patch-ah file (which provided > to resolve such misbehaviour). If that file doesn't exist than either try to > cvsup your ports, or manually add following patch and recompile/reinstall samba: This patch is only relevant for Samba 2.0.5a. If you look at the Changelog for 2.0.6 you'll see that MSG_WAITALL was removed specifically because of the performance problems under FreeBSD it caused. -- Greg Lewis glewis@trc.adelaide.edu.au Computing Officer +61 8 8303 5083 Teletraffic Research Centre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 14:16:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from modemcable156.106-200-24.mtl.mc.videotron.net (modemcable126.102-200-24.mtl.mc.videotron.net [24.200.102.126]) by hub.freebsd.org (Postfix) with SMTP id CD6FC14A09 for ; Tue, 7 Dec 1999 14:15:54 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 91459 invoked from network); 7 Dec 1999 22:15:53 -0000 Received: from patrak.local.mindstep.com (HELO patrak) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 7 Dec 1999 22:15:53 -0000 Message-ID: <00bc01bf4100$a00ee780$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: "\"Sean O'Connell\"" Cc: References: <19991207093048.W1667@stat.Duke.EDU> Subject: Re: /sbin/dhclient-script and llinfo error Date: Tue, 7 Dec 1999 17:15:52 -0500 Organization: MindStep Corporation MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_00B9_01BF40D6.B6FD5D20" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_00B9_01BF40D6.B6FD5D20 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, I wrote a replacement for "/sbin/dhclient-script". I had a couple of issues with the existing one and I needed to be able to call some scripts whenever the state of the interfaced changed because of DHCP. Anyway, the old script was buggy and obscure (to say the least) so here is a new version. Following your suggestion, I disabled all call to "route add xxx 127.0.0.1". I will submit this script in a PR later today, in the mean time, try it and let me know how it goes... Patrick. -- www.mindstep.com ------=_NextPart_000_00B9_01BF40D6.B6FD5D20 Content-Type: application/octet-stream; name="dhclient-script" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="dhclient-script" #!/bin/sh #########################################################################= #### # # (c) 1999, MindStep Corporation. All rights reserved. # # Redistribution and use in source and binary forms, with or without # modification, are permitted provided that the following conditions # are met: # 1. Redistributions of source code must retain the above copyright # notice, this list of conditions and the following disclaimer. # 2. Redistributions in binary form must reproduce the above copyright # notice, this list of conditions and the following disclaimer in the # documentation and/or other materials provided with the = distribution. # 3. All advertising materials mentioning features or use of this = software # must display the following acknowledgement: # This product includes software developed by the University of # California, Berkeley and its contributors. # 4. Neither the name of the University nor the names of its = contributors # may be used to endorse or promote products derived from this = software # without specific prior written permission. # # THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' = AND # ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR = PURPOSE # ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE = LIABLE # FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR = CONSEQUENTIAL # DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE = GOODS # OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) # HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, = STRICT # LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY = WAY # OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF # SUCH DAMAGE. # #########################################################################= #### # # This script was written by Patrick Bihan-Faou, patrick@mindstep.com, # Please contact us for bug reports, etc. # #########################################################################= #### # Rev: $Id: dhclient-script.sh,v 1.8 1999/12/07 22:11:08 patrick Exp $ # $MindStep_Tag: CONTRIB_19991207 $ #########################################################################= #### #########################################################################= #### # hook functions prototypes # # The "pre_state_XXX_hook" functions are called before the main # work is done for the state XXX # # The "post_state_XXX_hook" functions are called after the main # work is done for the state XXX # # These functions are meant to be overridden by the user's # dhclient-enter-hooks file #########################################################################= #### pre_state_MEDIUM_hook () { } pre_state_PREINIT_hook () { } pre_state_ARPCHECK_hook () { } pre_state_ARPSEND_hook () { } pre_state_RENEW_hook () { } pre_state_REBIND_hook () { } pre_state_BOUND_hook () { } pre_state_REBOOT_hook () { } pre_state_EXPIRE_hook () { } pre_state_FAIL_hook () { } pre_state_TIMEOUT_hook () { } post_state_MEDIUM_hook () { } post_state_PREINIT_hook () { } post_state_ARPCHECK_hook () { } post_state_ARPSEND_hook () { } post_state_RENEW_hook () { } post_state_REBIND_hook () { } post_state_BOUND_hook () { } post_state_REBOOT_hook () { } post_state_EXPIRE_hook () { } post_state_FAIL_hook () { } post_state_TIMEOUT_hook () { } #########################################################################= #### # make_resolv_conf # # This function is called to update the information related to the # DNS configuration (the resolver part) #########################################################################= #### make_resolv_conf ()=20 { echo search $new_domain_name >/etc/resolv.conf for nameserver in $new_domain_name_servers; do echo nameserver $nameserver >>/etc/resolv.conf done } # Must be used on exit. Invokes the local dhcp client exit hooks, if = any. exit_with_hooks () { exit_status=3D$1 if [ -x /etc/dhclient-exit-hooks ]; then . /etc/dhclient-exit-hooks fi # probably should do something with exit status of the local script return $exit_status } #########################################################################= #### # set_XXX # unset_XXX # # These function each deal with one particular setting. # They are OS dependent and may be overridden in the=20 # dhclient-enter-hooks file if needed. # # These functions are called with either "new" or "old" to indicate = which # set of variables to use (new_ip_address or old_ip_address...) # #########################################################################= #### update_hostname () { local current_hostname=3D`/bin/hostname` if [ "$current_hostname" =3D "" ] || \ [ "$current_hostname" =3D "$old_host_name" ] then if [ "$new_host_name" !=3D "$old_host_name" ] then $LOGGER "New Hostname: $new_host_name" hostname $new_host_name fi fi } set_ip_address ()=20 { local ip local mask local bcast if [ $# -lt 1 ] then return 1 fi eval ip=3D"\$${1}_ip_address" eval mask=3D"\$${1}_subnet_mask" eval bcast=3D"\$${1}_broadcast_address" if [ "$ip" !=3D "" ] then ifconfig $interface inet $ip netmask $mask broadcast $bcast $medium # route add $ip 127.0.0.1 > /dev/null 2>&1 fi } unset_ip_address ()=20 { local ip if [ $# -lt 1 ] then return 1 fi eval ip=3D"\$${1}_ip_address" if [ "$ip" !=3D "" ] then ifconfig $interface inet -alias $ip $medium # route delete $ip 127.0.0.1 > /dev/null 2>&1 fi } set_ip_alias ()=20 { if [ "$alias_ip_address" !=3D "" ] then ifconfig $interface inet alias $alias_ip_address netmask = $alias_subnet_mask # route add $alias_ip_address 127.0.0.1 fi } unset_ip_alias ()=20 { if [ "$alias_ip_address" !=3D "" ] then ifconfig $interface inet -alias $alias_ip_address > /dev/null 2>&1 # route delete $alias_ip_address 127.0.0.1 > /dev/null 2>&1 fi } set_routers ()=20 { local router_list if [ $# -lt 1 ] then return 1 fi eval router_list=3D"\$${1}_routers" for router in $router_list do route add default $router >/dev/null 2>&1 done } unset_routers ()=20 { local router_list if [ $# -lt 1 ] then return 1 fi eval router_list=3D"\$${1}_routers" for router in $router_list do route delete default $router >/dev/null 2>&1 done } set_static_routes ()=20 { local static_routes if [ $# -lt 1 ] then return 1 fi eval static_routes=3D"\$${1}_static_routes" set static_routes while [ $# -ge 2 ] do $LOGGER "New Static Route: $1 -> $2" route add $1 $2 shift; shift done } unset_static_routes ()=20 { local static_routes if [ $# -lt 1 ] then return 1 fi eval static_routes=3D"\$${1}_static_routes" set static_routes while [ $# -ge 2 ] do route delete $1 $2 shift; shift done } #########################################################################= #### # # utility functions grouping what needs to be done in logical units. # #########################################################################= #### set_all () { set_ip_address new set_routers new set_static_routes new if [ "$new_ip_address" !=3D "$alias_ip_address" ] then set_ip_alias fi } set_others () { update_hostname make_resolv_conf } clear_arp_table ()=20 { arp -d -a } unset_all () { if [ "$alias_ip_address" !=3D "$old_ip_address" ] then unset_ip_alias fi if [ "$old_ip_address" !=3D "" ]=20 then unset_ip_address old unset_routers old unset_static_routes old clear_arp_table fi } test_new_lease ()=20 { local rc set $new_routers if [ $# -ge 1 ] then set_ip_address new if ping -q -c 1 $1 then rc=3D0 else rc=3D1 fi unset_ip_address new else rc=3D1 fi return $rc } #########################################################################= #### # Main State functions. # # There is a state function for each state of the DHCP client # These functions are OS specific and should be be tampered with. #########################################################################= #### in_state_MEDIUM ()=20 { ifconfig $interface $medium ifconfig $interface inet -alias 0.0.0.0 $medium >/dev/null 2>&1 sleep 1 exit_status=3D0 } in_state_PREINIT ()=20 { unset_ip_alias ifconfig $interface inet 0.0.0.0 netmask 0.0.0.0 \ broadcast 255.255.255.255 up exit_status=3D0 } in_state_ARPCHECK ()=20 { exit_status=3D0 } in_state_ARPSEND ()=20 { exit_status=3D0 } in_state_RENEW ()=20 { if [ "$old_ip_address" !=3D "$new_ip_address" ] then unset_all set_all fi set_others } in_state_REBIND () { in_state_RENEW } in_state_BOUND () { unset_all set_all set_others } in_state_REBOOT () { in_state_BOUND } in_state_EXPIRE ()=20 { unset_all set_ip_alias exit_status=3D0 } in_state_FAIL () { in_state_EXPIRE } in_state_TIMEOUT ()=20 { unset_all if test_new_lease then set_all set_others else $LOGGER "No good lease information in TIMEOUT state"=09 set_ip_alias exit_status=3D1 fi } #########################################################################= #### # Main functions: # # dhclient_script_init() parses the optional "enter_hooks" script which = can # override any of the state functions # # This function also parses the variables and notifies the detected = changes. #########################################################################= #### dhclient_script_init () { if [ -x /usr/bin/logger ]; then LOGGER=3D"/usr/bin/logger -s -p user.notice -t dhclient" else LOGGER=3Decho fi # Invoke the local dhcp client enter hooks, if they exist. if [ -x /etc/dhclient-enter-hooks ] then exit_status=3D0 . /etc/dhclient-enter-hooks # allow the local script to abort processing of this state # local script must set exit_status variable to nonzero. if [ $exit_status -ne 0 ] then exit $exit_status fi fi if [ "$new_network_number" !=3D "" ] then $LOGGER "New Network Number: $new_network_number" fi if [ "$new_ip_address" !=3D "" ] then $LOGGER "New IP Address: $new_ip_address" fi if [ "$new_broadcast_address" !=3D "" ] then $LOGGER "New Broadcast Address: $new_broadcast_address" fi if [ "$new_subnet_mask" !=3D "" ] then $LOGGER "New Subnet Mask for $interface: $new_subnet_mask" fi if [ "$alias_subnet_mask" !=3D "" ] then fi } #########################################################################= #### # dhclient_main() does the appropriate work depending on the state of # the dhcp client #########################################################################= #### dhclient_script_main () { # set -x exit_status=3D0 case $reason in MEDIUM|\ PREINIT|\ ARPCHECK|\ ARPSEND|\ RENEW|\ REBIND|\ BOUND|\ REBOOT|\ EXPIRE|\ FAIL|\ TIMEOUT) pre_state_${reason}_hook in_state_${reason} post_state_${reason}_hook ;; *) $LOGGER "dhclient-script called with invalid reason $reason" exit_status=3D1 ;; esac exit_with_hooks $exit_status } #########################################################################= #### # Let's do the work... #########################################################################= #### dhclient_script_init dhclient_script_main exit $exit_status #########################################################################= #### # That's all folks #########################################################################= #### ------=_NextPart_000_00B9_01BF40D6.B6FD5D20-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 14:18:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from natsoft.com.au (natsoft.com.au [203.39.138.130]) by hub.freebsd.org (Postfix) with ESMTP id 9E98014A09; Tue, 7 Dec 1999 14:18:46 -0800 (PST) (envelope-from craig@natsoft.com.au) Received: from Win95.natsoft.com.au (Win95 [203.39.138.131]) by natsoft.com.au (8.8.5/8.8.5) with SMTP id JAA04493; Wed, 8 Dec 1999 09:22:08 GMT Message-ID: <384D869D.6093@natsoft.com.au> Date: Wed, 08 Dec 1999 09:13:49 +1100 From: Craig Wilson Organization: National Software Pty Ltd X-Mailer: Mozilla 3.04 (Win95; I) MIME-Version: 1.0 To: Greg Lewis Cc: sobomax@altavista.net, l.farr@epcdirect.co.uk, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Samba Performance References: <199912072144.IAA47852@ares.maths.adelaide.edu.au> 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 FreeBSD 3.3-RELEASE on a computer that is having Samba performance problems. Using an Intel EtherExpress Pro100 (100MBit) it takes 10 times as long to copy the same large file from a Win98 computer to the FreeBSD computer than it takes to copy from a Win98 to Win98 computer. On looking at the Samba man page I see that FeeBSD 3.3-RELEASE is using Samba 2.0.5a. This Samba was installed as a precompiled package from the 3.3-RELEASE CD-ROM. Could someone please advise me if the Samba package on the CD-ROM contains this problem. If so I assume it is best to download Samba 2.0.6. Thanks in advance Craig Wilson National software Pty Ltd Greg Lewis wrote: > > > Try to look into the ports/samba/patches for the patch-ah file (which provided > > to resolve such misbehaviour). If that file doesn't exist than either try to > > cvsup your ports, or manually add following patch and recompile/reinstall samba: > > This patch is only relevant for Samba 2.0.5a. If you look at the Changelog > for 2.0.6 you'll see that MSG_WAITALL was removed specifically because of > the performance problems under FreeBSD it caused. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 14:19: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 2D68B154B1 for ; Tue, 7 Dec 1999 14:18:50 -0800 (PST) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id XAA23667; Tue, 7 Dec 1999 23:18:25 +0100 (MET) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id XAA00957; Tue, 7 Dec 1999 23:18:10 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <036901bf40b4$5573b300$1600a8c0@SOS> References: <036901bf40b4$5573b300$1600a8c0@SOS> Date: Tue, 7 Dec 1999 23:17:43 +0100 To: "Morten Seeberg" , "Steve O'Hara-Smith" , From: Brad Knowles Subject: Re: is -STABLE really stable? Content-Type: text/plain; charset="iso-8859-1" ; format="flowed" Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:09 PM +0100 1999/12/7, Morten Seeberg wrote: >=20 Revising the release times for 3.0, 3.1, 3.2, 3.3 I know realise that I= =B4ve >=20 just misunderstood the way -STABLE works :) And that I should just star= t >=20 using RELEASE on my production machines, instead of -STABLE, which I th= ought >=20 was "better"/"more stable" than RELEASE. Considering some of the comments I recall seeing from Jordan, I'd=20 actually be inclined to use -STABLE a couple weeks newer than the=20 latest -RELEASE. The reason is that there is a strong tendency=20 amongst many people to wait until there's a -RELEASE version before=20 they consider it "safe" to download and try out, and they inevitably=20 find a few bugs which then need to be fixed. However, once you've got a box installed, I'd suggest not=20 updating it unless you see a bug fix or a security issue that=20 directly addresses something that you're actually seeing as an issue=20 on that machine. --=20 =20 These are my opinions -- not to be taken as official Skynet policy =20 ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ =20 Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. =20 Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 14:26:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E0A1714E4A; Tue, 7 Dec 1999 14:26:12 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id OAA17645; Tue, 7 Dec 1999 14:55:38 -0800 (PST) Date: Tue, 7 Dec 1999 14:55:37 -0800 (PST) From: Alfred Perlstein To: Warner Losh Cc: Garance A Drosihn , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test In-Reply-To: <199912072106.OAA44391@harmony.village.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 On Tue, 7 Dec 1999, Warner Losh wrote: > I've been reviewing this patch with someone and I think the last > version is ready to commit. I'll take a look at my tree to make > sure. please do not, the patch in PR 11997 introduces a major security flaw. someone can hardlink to any file and clobber it with a file owned by them: try this: as root: # cd /var/tmp ; touch rootfile ; chown root:wheel rootfile ; chmod 600 rootfile as a user: % cd /var/tmp ; echo foo > foo % lpr -r foo sleeping in another session as user: % rm foo ; ln rootfile foo wait a second... # ls -l rootfile -rw-rw---- 3 user daemon 5 Dec 7 13:38 rootfile # cat rootfile foo # ouch! -Alfred use this patch to make the race condition apparrent: Index: usr.sbin/lpr/lpr/lpr.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/lpr/lpr/lpr.c,v retrieving revision 1.27.2.2 diff -u -u -r1.27.2.2 lpr.c --- lpr.c 1999/08/29 15:43:29 1.27.2.2 +++ lpr.c 1999/12/08 01:47:47 @@ -370,6 +370,27 @@ } if (sflag) printf("%s: %s: not linked, copying instead\n", name, arg); + if( f ) { /* means that the file should be deleted */ + printf("sleeping\n"); + sleep(5); + printf("done.\n"); + seteuid(euid); /* needed for rename() to succeed */ + if( ! rename( arg, dfname ) ) { + register int i; + chmod( dfname, S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP ); + chown( dfname, userid, getgrnam("daemon")->gr_gid ); + seteuid(uid); + if (format == 'p') + card('T', title ? title : arg); + for (i = 0; i < ncopies; i++) + card(format, &dfname[inchar-2]); + card('U', &dfname[inchar-2]); + card('N', arg); + nact++; + continue; + } + seteuid(uid); + } if ((i = open(arg, O_RDONLY)) < 0) { printf("%s: cannot open %s\n", name, arg); } else { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 17: 8:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 85AAC14BC3 for ; Tue, 7 Dec 1999 17:08:48 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA23073; Tue, 7 Dec 1999 18:07:25 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912080107.SAA23073@freeway.dcfinc.com> Subject: Re: is -STABLE really stable? In-Reply-To: from Steve O'Hara-Smith at "Dec 7, 99 12:56:33 pm" To: steve@pooh.elsevier.nl (Steve O'Hara-Smith) Date: Tue, 7 Dec 1999 18:07:25 -0700 (MST) Cc: morten@seeberg.dk, 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, Steve O'Hara-Smith wrote: > This is an interesting topic in it's own right. There is a fairly > large body of opinion that the right way to treat a production system > is never to upgrade it at all, rather to periodically replace it with > a well tested replacement using later software. The best way, if you can afford the time and hardware. > Another view is to track the release stream before -stable (right now > that would be 2.x) which continues to get major bug fixes and security > fixes for quite a long time after it stops getting features. The one I use. Using CVSup to fetch RELENG_2_2 gets you what is (IMHO) a wonderfully stable, high performance system. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 18:39:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp1.ihug.co.nz (tk1.ihug.co.nz [203.29.160.13]) by hub.freebsd.org (Postfix) with ESMTP id 45E8114CFD for ; Tue, 7 Dec 1999 18:39:23 -0800 (PST) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (p59-max6.dun.ihug.co.nz [209.77.130.123]) by smtp1.ihug.co.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id PAA06062; Wed, 8 Dec 1999 15:39:18 +1300 Message-ID: <384DC4D4.99AB4960@es.co.nz> Date: Wed, 08 Dec 1999 15:39:16 +1300 From: Mike Muir X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Greg Lewis , stable@FreeBSD.ORG Subject: Re: Samba Performance References: <199912080048.LAA49651@ares.maths.adelaide.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greg Lewis wrote: > > I have no idea of the actual traffic speed, but I find we get throughput > which appears qualitatively to be respectable with these socket options: > > socket options = IPTOS_LOWDELAY TCP_NODELAY > > Without these options the performance wasn't nearly as good. YMMV. I already had TCP_NODELAY...but... smb: \incoming\> put #math.xchatlog putting file #math.xchatlog as \incoming\#math.xchatlog (107.262 kb/s) (average 107.262 kb/s) smb: \incoming\> get #math.xchatlog getting file #math.xchatlog of size 2692307 as #math.xchatlog (1021.84 kb/s) (average 1021.84 kb/s) From speeds increased (quite a bit.. now we're talking :) but upload (incoming) speeds still suck ass.. hrmph. mike. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 19:43:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.sprawlnet.com (ns1.sprawlnet.com [208.224.169.130]) by hub.freebsd.org (Postfix) with ESMTP id 2C31B14EAD for ; Tue, 7 Dec 1999 19:43:34 -0800 (PST) (envelope-from mike@sprawlnet.com) Received: from bsd.unixvillain.com (mikes@2Cust31.tnt10.atl2.da.uu.net [63.22.60.159]) by ns1.sprawlnet.com (8.9.3/8.9.2) with SMTP id LAA53390 for ; Wed, 8 Dec 1999 11:45:33 -0500 (EST) (envelope-from mike@sprawlnet.com) From: Mike Steinfeld To: freebsd-stable@freebsd.org Subject: ppp seems to disconnect every 10 minutes? Date: Mon, 6 Dec 1999 16:53:48 -0500 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99120616580900.12599@bsd.unixvillain.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi all, I have multiple dialup accounts and it does not matter which one i am using after about being connected fro aprx 10 minutes, my connection keep dropping and its really starting to get on ym nerves. Anyone have any ideas what maybe the cause of this. I has never happened before on any other of my freeBSd box's jsut this one imarticular. any suggestions or help would greatly be appreciated, thanks, mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 21: 4:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from puffer.quadrunner.com (puffer.quadrunner.com [205.166.195.4]) by hub.freebsd.org (Postfix) with ESMTP id 72EF114EDC for ; Tue, 7 Dec 1999 21:04:27 -0800 (PST) (envelope-from manek@quadrunner.com) Received: from after (root@puffer.quadrunner.com [205.166.195.4]) by puffer.quadrunner.com (8.9.2/QUAD-2.1) with SMTP id VAA28458 for ; Tue, 7 Dec 1999 21:04:27 -0800 (PST) From: "Sameer R. Manek" To: Subject: RE: is -STABLE really stable? Date: Tue, 7 Dec 1999 21:05:38 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <199912080107.SAA23073@freeway.dcfinc.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Chad R. Larson > Sent: Tuesday, December 07, 1999 5:07 PM=20 >=20 > As I recall, Steve O'Hara-Smith wrote: > > This is an interesting topic in it's own right. There is a fairly > > large body of opinion that the right way to treat a production = system > > is never to upgrade it at all, rather to periodically replace it = with > > a well tested replacement using later software. >=20 > The best way, if you can afford the time and hardware. All it really needs is 1 spare box. Assuming upgrades are performed = every release, that's only 3 upgrades a year. And the cost of the extra = hardware will be about $100/month for a lease. Most business can afford = the hardware, it's the labor that's expensive. Even then having a spare = system is justifable. The cost of downtime for a failed upgrade can be expensive compared to = the tested replacement machine path. Granted smaller companies, = especially one and two employee companies might not be able to afford = the extra hardware, but they have a different business model. Sameer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 21:10: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c1870039.telekabel.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 201BC14F9F for ; Tue, 7 Dec 1999 21:09:56 -0800 (PST) (envelope-from roelof@nisser.com) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id GAA00803 for ; Wed, 8 Dec 1999 06:09:56 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <384DE84E.8285191E@nisser.com> Date: Wed, 08 Dec 1999 06:10:38 +0100 From: Roelof Osinga Organization: eboa - engineering buro Office Automation X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Stable Subject: ifpw forwarding problem 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 trying to do redirect incoming connections on port 8080 to an external port 80 on machine 10.0.0.3 nisser:/root/bin$ ifconfig -a ep0: flags=8843 mtu 1500 inet 10.0.0.55 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:60:97:14:31:a7 ep1: flags=8843 mtu 1500 inet 212.187.0.39 netmask 0xfffff800 broadcast 212.187.7.255 inet 194.134.130.170 netmask 0xffffffff broadcast 194.134.130.170 ether 00:60:97:e4:98:db lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 nisser:/root/bin$ uname -a FreeBSD nisser.com 3.3-STABLE FreeBSD 3.3-STABLE #11: Wed Dec 8 04:54:50 CET 19 99 toor@nisser.com:/usr/src/sys/compile/FORSETI i386 The kernel options in use are #options MROUTING # Multicast routing options IPFIREWALL #firewall #options IPFIREWALL_VERBOSE #print information about # dropped packets options IPFIREWALL_FORWARD #enable transparent proxy support #options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity #options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets options IPFILTER #kernel ipfilter support #options IPFILTER_LOG #ipfilter logging #options IPFILTER_LKM #kernel support for ip_fil.o LKM #options TCPDEBUG natd is running with -same_ports -use_sockets on ep1 The command I'm issuing is: ipfw add 2000 fwd 10.0.0.3,80 tcp from any to 10.0.0.55 8080 in via ep0 Though accepted it will not redirect. The 10.0.0.3:80 does answer when queried directly: nisser:/root/bin$ telnet 10.0.0.55 8080 Trying 10.0.0.55... telnet: Unable to connect to remote host: Connection refused nisser:~# ipfw list 00100 divert 8668 ip from any to any via ep1 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 01000 deny tcp from any to any 23,143,110,79,111 in recv ep1 01000 deny tcp from any to any 5800,5801,5802,5900,5901,5902 in recv ep1 02000 fwd 10.0.0.3,80 tcp from any to 10.0.0.55 8080 in recv ep0 65000 allow ip from any to any 65535 deny ip from any to any What am I missing here? Roelof -- Home is where the (@) http://eboa.com/ is. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 22: 4:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-108.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.236]) by hub.freebsd.org (Postfix) with ESMTP id EE7B714C48 for ; Tue, 7 Dec 1999 22:04:34 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id GAA89168; Wed, 8 Dec 1999 06:20:40 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id GAA02753; Wed, 8 Dec 1999 06:03:14 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912080603.GAA02753@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Mike Steinfeld Cc: freebsd-stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ppp seems to disconnect every 10 minutes? In-Reply-To: Message from Mike Steinfeld of "Mon, 06 Dec 1999 16:53:48 EST." <99120616580900.12599@bsd.unixvillain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Dec 1999 06:03:14 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > hi all, > > I have multiple dialup accounts and it does not matter which one i am using > after about being connected fro aprx 10 minutes, my connection keep dropping > and its really starting to get on ym nerves. > > Anyone have any ideas what maybe the cause of this. I has never happened before > on any other of my freeBSd box's jsut this one imarticular. > > any suggestions or help would greatly be appreciated, Your first step should be to turn up your logging - maybe ``set log phase ipcp lcp command''. You need to determine which side is dropping the connection. Also, take a look at http://www.FreeBSD.org/FAQ/userppp.html > thanks, > mike -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 7 22:39:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from crash.ab.videon.ca (crash.ab.videon.ca [206.75.216.220]) by hub.freebsd.org (Postfix) with ESMTP id 3F67414FF7 for ; Tue, 7 Dec 1999 22:39:10 -0800 (PST) (envelope-from cwasser@v-wave.com) Received: from area51.v-wave.com (area51.v-wave.com [24.108.26.39]) by crash.ab.videon.ca (8.9.2/8.9.2) with ESMTP id XAA22111; Tue, 7 Dec 1999 23:38:55 -0700 (MST) Date: Tue, 7 Dec 1999 23:37:16 -0700 From: Chris Wasser X-Mailer: The Bat! (v1.36) S/N FBA00CBA Reply-To: Chris Wasser X-Priority: 3 (Normal) Message-ID: <16984.991207@v-wave.com> To: Mike Muir Cc: Greg Lewis , stable@FreeBSD.ORG Subject: Re[2]: Samba Performance In-reply-To: <384DC4D4.99AB4960@es.co.nz> References: <384DC4D4.99AB4960@es.co.nz> 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 on 12/7/1999 7:39 PM, mmuir@es.co.nz wrote: > From speeds increased (quite a bit.. now we're talking :) but upload > (incoming) speeds still suck ass.. hrmph. I did a little research on this and posted results about it to the mailing list quite a while back (as I'm sure others did) but for a direct link to my post go to: http://www.freebsd.org/cgi/getmsg.cgi?fetch=808688+813213+/usr/local/www/db/text /1999/freebsd-questions/19991121.freebsd-questions It covers the issues you are having. Hope it helps. -----BEGIN PGP SIGNATURE----- Version: PGP 6.5i iQA/AwUBOE38nHkOgeFubyAgEQIetACg4LkHNRPsUyKYbilDljB1THG/ug0AnRg4 wQQsXhbr5N8YNt7XMyMze3Wr =KpoV -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 0:33: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from io.freibergnet.de (io.freibergnet.de [194.123.255.3]) by hub.freebsd.org (Postfix) with ESMTP id 9C3ED154C5 for ; Wed, 8 Dec 1999 00:32:56 -0800 (PST) (envelope-from mw@io.freibergnet.de) Received: (from mw@localhost) by io.freibergnet.de (8.9.3/8.9.1) id JAA21313; Wed, 8 Dec 1999 09:32:43 +0100 (CET) (envelope-from mw) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <384DE84E.8285191E@nisser.com> Date: Wed, 08 Dec 1999 09:32:43 +0100 (CET) Reply-To: mw@freibergnet.de Organization: FreibergNet Systemhaus / Liebscher & Partner From: Martin Welk To: Roelof Osinga Subject: RE: ifpw forwarding problem Cc: FreeBSD Stable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Roelof, on 08-Dec-99 Roelof Osinga wrote: () natd is running with -same_ports -use_sockets on ep1 This seems to be right. () The command I'm issuing is: () () ipfw add 2000 fwd 10.0.0.3,80 tcp from any to 10.0.0.55 8080 in via ep0 () () Though accepted it will not redirect. The 10.0.0.3:80 does answer () when queried directly: () () nisser:/root/bin$ telnet 10.0.0.55 8080 () Trying 10.0.0.55... () telnet: Unable to connect to remote host: Connection refused () () nisser:~# ipfw list () 00100 divert 8668 ip from any to any via ep1 () 00100 allow ip from any to any via lo0 () 00200 deny ip from any to 127.0.0.0/8 () 01000 deny tcp from any to any 23,143,110,79,111 in recv ep1 () 01000 deny tcp from any to any 5800,5801,5802,5900,5901,5902 in recv ep1 () 02000 fwd 10.0.0.3,80 tcp from any to 10.0.0.55 8080 in recv ep0 () 65000 allow ip from any to any () 65535 deny ip from any to any Your problem is, that forwarding packets by rules to other hosts is not the same as forwarding packets to hosts through a NAT environment. Look at the natd man page, search for the redirect options mentioned there. In my case, there's a FreeBSD machine doing NAT here. It has two IP addresses on the outer world interface, but this shouldn't be a significant difference. I have a file named natd.conf that's loaded on startup doing a "natd -f natd.conf" - you may put it somewhere in the file system where you like it and use the absolute path, I've chosen /etc. use_sockets same_ports port 8668 deny_incoming no alias_address aaa.aaa.aaa.aaa redirect_port tcp bbb.bbb.bbb.bbb:5900 aaa.aaa.aaa.aaa:5900 In this case, the port 5900 (which is by default used for a first VNC session) is redirected to an interal Windows box that can be accessed this way. aaa.aaa.aaa.aaa is the external network address of the router, bbb.bbb.bbb.bbb the internal host (192.168...) You need to do that this way in a NAT'ed environment because someone has to change the IP addresses as they are needed to make it work properly. For the ipfw setup, a directive like divert 8668 all from any to any allow ip from any to any will do the job, allthough all packets pass natd this way. But if it works in this case, you have now a good starting point to do more :-) No RTFM intended, but I found the following man pages very helpful when I started with ipfw/natd and so on: divert(4), dummynet(4), ipfw(8), ipfirewall(4). Although dummynet has to do with bandwidth limiting and delaying (this is integrated into the IPFW functionality), it gives some further information that helps to understand how packets pass through the firewall. Regards, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 0:36:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from io.freibergnet.de (io.freibergnet.de [194.123.255.3]) by hub.freebsd.org (Postfix) with ESMTP id C6BE414EBD for ; Wed, 8 Dec 1999 00:36:54 -0800 (PST) (envelope-from mw@io.freibergnet.de) Received: (from mw@localhost) by io.freibergnet.de (8.9.3/8.9.1) id JAA21452; Wed, 8 Dec 1999 09:36:40 +0100 (CET) (envelope-from mw) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <384DC4D4.99AB4960@es.co.nz> Date: Wed, 08 Dec 1999 09:36:39 +0100 (CET) Reply-To: mw@freibergnet.de Organization: FreibergNet Systemhaus / Liebscher & Partner From: Martin Welk To: Mike Muir Subject: Re: Samba Performance Cc: stable@FreeBSD.ORG, Greg Lewis Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-99 Mike Muir wrote: () smb: \incoming\> put #math.xchatlog () putting file #math.xchatlog as \incoming\#math.xchatlog (107.262 kb/s) () (average 107.262 kb/s) () smb: \incoming\> get #math.xchatlog () getting file #math.xchatlog of size 2692307 as #math.xchatlog (1021.84 () kb/s) () (average 1021.84 kb/s) Somewhere in the Usenet somebody said, that the generic answer to such a question is to always increase the receive/send buffers for the socket. Look at [g|s]etockopt(2) for more information. I have added socket options = IPTOS_LOWDELAY TCP_NODELAY SO_SNDBUF=262144 \ SO_RCVBUF=262144 (I'm not sure if 256k is really needed, I left it because there are some Windows boxes connected to the Samba server and I haven't tried if there's a difference - with 128k I experienced same speed as it's now with only one machine. But the raising speed was highly noticeable, especially when copying many many small files!) () >From speeds increased (quite a bit.. now we're talking :) but upload () (incoming) speeds still suck ass.. hrmph. That's it without increased buffers. Gruß, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 6:23:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 3B27814C11; Wed, 8 Dec 1999 06:23:43 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id IAA59277; Wed, 8 Dec 1999 08:23:36 -0600 (CST) From: Joe Greco Message-Id: <199912081423.IAA59277@aurora.sol.net> Subject: Re: Route table leaks In-Reply-To: from John Polstra at "Nov 21, 1999 11:55:24 pm" To: jdp@polstra.com (John Polstra) Date: Wed, 8 Dec 1999 08:23:35 -0600 (CST) Cc: current@freebsd.org, stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Have any of you been seeing route table leaks in -current? I noticed > this week that cvsup-master.freebsd.org is suffering from them. I > actually had to reboot it because it couldn't allocate any more. From > the "vmstat -m" output: > > Memory statistics by type Type Kern > Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) > [...] > routetbl150907 21221K 21221K 21221K 462184 0 0 16,32,64,128,256 > [...] > I can think of some experiments to try in order to start to diagnose > it. But first, have any of you seen this problem? Hell, I've been seeing this for well over a year. The last time I mentioned it, everybody seemed to think I was nuts. :-) FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 When it gets like that, it starts losing the ability to add further ARP table entries and essentially starts going randomly deaf to local hosts (and to a lesser extent remote hosts). I've also seen it on a 3.3-RELEASE box, but it's not currently happening to any of them right now. Machines in question are SMP boxes, and get hit fairly heavily in various Usenet news server roles. Seems to happen quite a bit more often on boxes that talk to a wide variety of host types, and I can't recall having seen it on boxes that only talk to other FreeBSD boxes. But that could also be because the network environment is much more controlled internally. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 6:46:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id C584914C92; Wed, 8 Dec 1999 06:46:05 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id JAA23041; Wed, 8 Dec 1999 09:46:04 -0500 (EST) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id JAA11510; Wed, 8 Dec 1999 09:46:04 -0500 (EST) Message-Id: <3.0.5.32.19991208094433.01610ac0@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 08 Dec 1999 09:44:33 -0500 To: Joe Greco , jdp@polstra.com (John Polstra) From: Mike Tancsa Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199912081423.IAA59277@aurora.sol.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Hell, I've been seeing this for well over a year. The last time I mentioned >it, everybody seemed to think I was nuts. :-) > >FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 Well, I havent seen problems of this nature (yet), but for reference, netstat -nr | wc 69585 419164 4875822 routetbl143718 19653K 21229K 21229K 6527152 0 0 16,32,64,128,256 FreeBSD 3.3-RC #0: Wed Sep 8 13:37:19 EDT 1999 uptime 9:44AM up 90 days, 20:35, 2 users, load averages: 0.00, 0.01, 0.00 This is a border router with 2 views of the net running defaultless. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 6:51:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 15DF514BDC; Wed, 8 Dec 1999 06:51:20 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id IAA61233; Wed, 8 Dec 1999 08:51:03 -0600 (CST) From: Joe Greco Message-Id: <199912081451.IAA61233@aurora.sol.net> Subject: Re: Route table leaks In-Reply-To: <3.0.5.32.19991208094433.01610ac0@staff.sentex.ca> from Mike Tancsa at "Dec 8, 1999 9:44:33 am" To: mike@sentex.net (Mike Tancsa) Date: Wed, 8 Dec 1999 08:51:03 -0600 (CST) Cc: jgreco@ns.sol.net, jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Hell, I've been seeing this for well over a year. The last time I mentioned > >it, everybody seemed to think I was nuts. :-) > > > >FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > > > routetbl289178 40961K 40961K 40960K 435741 0 0 > 16,32,64,128,256 > > Well, I havent seen problems of this nature (yet), but for reference, > > > netstat -nr | wc > 69585 419164 4875822 > > routetbl143718 19653K 21229K 21229K 6527152 0 0 16,32,64,128,256 > > FreeBSD 3.3-RC #0: Wed Sep 8 13:37:19 EDT 1999 > uptime > 9:44AM up 90 days, 20:35, 2 users, load averages: 0.00, 0.01, 0.00 > > This is a border router with 2 views of the net running defaultless. Yeah, nice :-), but the machine I'm looking at is one with a default route and > netstat -rn | wc -l 16 Most of which are routes pointing at the 3 private-net interfaces on the machine. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 8: 1:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 0E92D151B9 for ; Wed, 8 Dec 1999 08:01:14 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id IAA52774 for freebsd-stable@FreeBSD.ORG; Wed, 8 Dec 1999 08:01:14 -0800 (PST) Date: Wed, 8 Dec 1999 08:01:14 -0800 (PST) From: David Wolfskill Message-Id: <199912081601.IAA52774@pau-amma.whistle.com> To: freebsd-stable@FreeBSD.ORG Subject: RE: is -STABLE really stable? In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >From: "Sameer R. Manek" >Date: Tue, 7 Dec 1999 21:05:38 -0800 >> As I recall, Steve O'Hara-Smith wrote: >> > This is an interesting topic in it's own right. There is a fairly >> > large body of opinion that the right way to treat a production system >> > is never to upgrade it at all, rather to periodically replace it with >> > a well tested replacement using later software. >> The best way, if you can afford the time and hardware. >All it really needs is 1 spare box. Assuming upgrades are performed every release, that's only 3 upgrades a year. And the cost of the extra hardware will be about $100/month for a lease. Most business can afford the hardware, it's the labor that's expensive. Even then having a spare system is justifable. Unless I'm confused rather more than is usual -- which is by no means especially unlikely -- that also assumes that the "spare box" hardware is sufficiently close to that of the "production systems" that the resulting system can be tested with sufficient confidence (for some value of "sufficient") that the results will apply to the production system -- or, better yet, that the "spare box" can actually *become* the (new) "production system". (Then the just-retired system becomes the "spare box"... after sufficient burn-in....) Of course, this also presumes that the sysadmin(s) can tell when one set of hardware is "sufficiently close" to some other (sometimes arbitrary) set of hardware, which is certainly not the case with my dealings with PC hardware. :-( Others may well have different perspectives, certainly. And that count of "3 upgrades/year" is per machine; I doubt that I'm all that unusual in having some dozen or so servers and about 30 desktops to cope with, as well as a few other tasks to occupy my time. (In practice, I'm upgrading *far* less often than 3/year for any machine that I rely on. Not, of course, that I'm happy with the upgrade schedule I've been accomplishing; I'm working in "triage" mode.) Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 8: 9:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id 3153E15532 for ; Wed, 8 Dec 1999 08:09:17 -0800 (PST) (envelope-from Cy.Schubert@uumail.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id IAA31254; Wed, 8 Dec 1999 08:09:16 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda31251; Wed Dec 8 08:08:59 1999 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id IAA06632; Wed, 8 Dec 1999 08:08:59 -0800 (PST) Message-Id: <199912081608.IAA06632@passer.osg.gov.bc.ca> Received: from localhost.osg.gov.bc.ca(127.0.0.1), claiming to be "passer.osg.gov.bc.ca" via SMTP by localhost.osg.gov.bc.ca, id smtpdye6628; Wed Dec 8 08:08:42 1999 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.3-RELEASE X-Sender: cy To: Randy Bush Cc: FreeBSD Stable Subject: Re: -stable of 99.12.2 hoistile to ntpd? In-reply-to: Your message of "Fri, 03 Dec 1999 17:36:41 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Dec 1999 08:08:42 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC "e**(i*pi)+1=0" In message , Randy Bush writes: > built new -stable, running old ntpd 93a. now i get ... > > Dec 3 04:55:18 /kernel: cmd ntpd pid 303 tried to use non-present sched_get_ > priority_max > Dec 3 04:55:18 /kernel: cmd ntpd pid 303 tried to use non-present sched_sets > cheduler > Dec 3 04:55:18 ntpd[303]: sched_setscheduler(): Function not implemented > Dec 3 05:02:56 ntpd[303]: kernel pll status change 2041 > Dec 3 06:40:54 /kernel: cmd ntpd pid 303 tried to use non-present sched_get_ > priority_max > Dec 3 06:40:54 /kernel: cmd ntpd pid 303 tried to use non-present sched_sets > cheduler > Dec 3 06:40:54 ntpd[303]: sched_setscheduler(): Function not implemented > Dec 3 06:48:41 ntpd[303]: kernel pll status change 2041 > Dec 3 07:11:20 /kernel: pid 303 (ntpd), uid 0: exited on signal 8 (core dump > ed) > > and it is reproducable > > Dec 3 16:40:26 /kernel: cmd ntpd pid 37008 tried to use non-present sched_ge > t_priority_max > Dec 3 16:40:26 /kernel: cmd ntpd pid 37008 tried to use non-present sched_se > tscheduler > Dec 3 16:40:26 ntpd[37008]: sched_setscheduler(): Function not implemented > Dec 3 16:48:16 ntpd[37008]: kernel pll status change 2041 > Dec 3 17:10:56 /kernel: pid 37008 (ntpd), uid 0: exited on signal 8 (core du > mped) The port does not detect whether you have POSIX Priority Scheduling enabled in the kernel, therefore it will not use rtprio(2) and instead try to use the POSIX sched_setscheduler(2). To fix, rebuild your kernel with, options "P1003_1B" options "_KPOSIX_PRIORITY_SCHEDULING" options "_KPOSIX_VERSION=199309L" Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Cy.Schubert@gems8.gov.bc.ca Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 8:19:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id D473B14BD4 for ; Wed, 8 Dec 1999 08:19:33 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id QAA00773; Wed, 8 Dec 1999 16:20:23 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912081601.IAA52774@pau-amma.whistle.com> Date: Wed, 08 Dec 1999 16:20:22 -0000 (GMT) From: "Steve O'Hara-Smith" To: David Wolfskill Subject: RE: is -STABLE really stable? Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-99 David Wolfskill wrote: >>From: "Sameer R. Manek" >>Date: Tue, 7 Dec 1999 21:05:38 -0800 > Unless I'm confused rather more than is usual -- which is by no means > especially unlikely -- that also assumes that the "spare box" hardware is > sufficiently close to that of the "production systems" that the resulting > system can be tested with sufficient confidence (for some value of > "sufficient") that the results will apply to the production system -- or, > better yet, that the "spare box" can actually *become* the (new) > "production system". (Then the just-retired system becomes the "spare > box"... after sufficient burn-in....) Indeed the latter scenario is ideal (ideal is that the spare box and the production box are identical). > Of course, this also presumes that the sysadmin(s) can tell when one set > of hardware is "sufficiently close" to some other (sometimes arbitrary) > set of hardware, which is certainly not the case with my dealings with > PC hardware. :-( Others may well have different perspectives, certainly. Two identical boxes is IMHO the only way to be sure. > And that count of "3 upgrades/year" is per machine; I doubt that I'm all > that unusual in having some dozen or so servers and about 30 desktops to > cope with, as well as a few other tasks to occupy my time. (In > practice, I'm upgrading *far* less often than 3/year for any machine > that I rely on. Not, of course, that I'm happy with the upgrade > schedule I've been accomplishing; I'm working in "triage" mode.) This kind of conservative approach is most appropriate to critical servers. For workstations I just tend ------------------------------------------------------- Tell a computer to WIN and ... ... You lose ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 9:19:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from neptune.1webpage.net (neptune.1webpage.net [208.244.164.17]) by hub.freebsd.org (Postfix) with SMTP id B58B015176 for ; Wed, 8 Dec 1999 09:19:37 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: (qmail 30126 invoked from network); 8 Dec 1999 17:19:35 -0000 Received: from harlan.fred.net (HELO pcpsj.pfcs.com) (?jkvLpe4X6HSdaqnZbfIWwb1Se8nurIDR?@208.238.64.78) by neptune.1webpage.net with SMTP; 8 Dec 1999 17:19:35 -0000 Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id ; Wed, 8 Dec 1999 12:19:25 -0500 (EST) Received: from pcnbs.pfcs.com [192.52.69.42] (HELO pcnbs.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Wed, 8 Dec 1999 09:19:20 -0800 (PST) Received: from localhost [127.0.0.1] (HELO pcnbs.pfcs.com) by pcnbs.pfcs.com (8.9.3/8.8.8) via ESMTP id ; Wed, 8 Dec 1999 12:19:20 -0500 (EST) To: Cy Schubert - ITSD Open Systems Group Cc: Randy Bush , FreeBSD Stable Subject: Re: -stable of 99.12.2 hoistile to ntpd? In-Reply-To: Cy Schubert - ITSD Open Systems Group's (Cy.Schubert@uumail.gov.bc.ca) message dated Wed, 08 Dec 1999 08:08:42. <199912081608.IAA06632@passer.osg.gov.bc.ca> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (patch 8) (Bryce Canyon) (i386-unknown-freebsd3.3) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Wed, 08 Dec 1999 12:19:20 -0500 Message-ID: <29921.944673560@pcnbs.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The latest release of ntpd will try the POSIX sched stuff, and if those do not work, fall back to rtprio(), and if that does not work, nice() (more or less - I'm not looking at the code). H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 10:23:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 535D8155B3 for ; Wed, 8 Dec 1999 10:22:12 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id JAA17432; Wed, 8 Dec 1999 09:33:17 -0800 (PST) (envelope-from obrien) Date: Wed, 8 Dec 1999 09:33:17 -0800 From: "David O'Brien" To: Brandon Fosdick Cc: "Sean O'Connell" , FreeBSD stable Subject: Re: /sbin/dhclient-script and llinfo error Message-ID: <19991208093317.A30043@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991207093048.W1667@stat.Duke.EDU> <384D349A.10B7CC4C@glue.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <384D349A.10B7CC4C@glue.umd.edu> X-Operating-System: FreeBSD 3.3-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 07, 1999 at 11:23:54AM -0500, Brandon Fosdick wrote: > > I asked the same question abot a month ago and didn't get an answer. A > quick search of the archives will find some others with the same > problem. It seems to I got the report, but got busy and forgot about it (as it has never caused me problems). Let me try to revisit the patch for 3.4. -- -- David (obrien@NUXI.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 8 10:23:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from po4.glue.umd.edu (po4.glue.umd.edu [128.8.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 83E1B1592E; Wed, 8 Dec 1999 10:22:34 -0800 (PST) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.220.99]) by po4.glue.umd.edu (8.9.3/8.9.3) with ESMTP id NAA19275; Wed, 8 Dec 1999 13:22:26 -0500 (EST) Message-ID: <384EA1C3.97CFB385@glue.umd.edu> Date: Wed, 08 Dec 1999 13:21:55 -0500 From: Brandon Fosdick X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: "Sean O'Connell" , FreeBSD stable Subject: Re: /sbin/dhclient-script and llinfo error References: <19991207093048.W1667@stat.Duke.EDU> <384D349A.10B7CC4C@glue.umd.edu> <19991208093317.A30043@relay.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Tue, Dec 07, 1999 at 11:23:54AM -0500, Brandon Fosdick wrote: > > > > I asked the same question abot a month ago and didn't get an answer. A > > quick search of the archives will find some others with the same > > problem. It seems to > > I got the report, but got busy and forgot about it (as it has never > caused me problems). Let me try to revisit the patch for 3.4. > > -- > -- David (obrien@NUXI.com) Thanks. -- bfoz@glue.umd.edu "Lead, follow, or get run over" "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 10:43: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from po4.glue.umd.edu (po4.glue.umd.edu [128.8.10.124]) by hub.freebsd.org (Postfix) with ESMTP id 83E1B1592E; Wed, 8 Dec 1999 10:22:34 -0800 (PST) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.220.99]) by po4.glue.umd.edu (8.9.3/8.9.3) with ESMTP id NAA19275; Wed, 8 Dec 1999 13:22:26 -0500 (EST) Message-ID: <384EA1C3.97CFB385@glue.umd.edu> Date: Wed, 08 Dec 1999 13:21:55 -0500 From: Brandon Fosdick X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: obrien@FreeBSD.ORG Cc: "Sean O'Connell" , FreeBSD stable Subject: Re: /sbin/dhclient-script and llinfo error References: <19991207093048.W1667@stat.Duke.EDU> <384D349A.10B7CC4C@glue.umd.edu> <19991208093317.A30043@relay.nuxi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David O'Brien wrote: > > On Tue, Dec 07, 1999 at 11:23:54AM -0500, Brandon Fosdick wrote: > > > > I asked the same question abot a month ago and didn't get an answer. A > > quick search of the archives will find some others with the same > > problem. It seems to > > I got the report, but got busy and forgot about it (as it has never > caused me problems). Let me try to revisit the patch for 3.4. > > -- > -- David (obrien@NUXI.com) Thanks. -- bfoz@glue.umd.edu "Lead, follow, or get run over" "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 10:43:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 535D8155B3 for ; Wed, 8 Dec 1999 10:22:12 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id JAA17432; Wed, 8 Dec 1999 09:33:17 -0800 (PST) (envelope-from obrien) Date: Wed, 8 Dec 1999 09:33:17 -0800 From: "David O'Brien" To: Brandon Fosdick Cc: "Sean O'Connell" , FreeBSD stable Subject: Re: /sbin/dhclient-script and llinfo error Message-ID: <19991208093317.A30043@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <19991207093048.W1667@stat.Duke.EDU> <384D349A.10B7CC4C@glue.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: <384D349A.10B7CC4C@glue.umd.edu> X-Operating-System: FreeBSD 3.3-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 07, 1999 at 11:23:54AM -0500, Brandon Fosdick wrote: > > I asked the same question abot a month ago and didn't get an answer. A > quick search of the archives will find some others with the same > problem. It seems to I got the report, but got busy and forgot about it (as it has never caused me problems). Let me try to revisit the patch for 3.4. -- -- David (obrien@NUXI.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 8 10:58:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id F1C861516D; Wed, 8 Dec 1999 10:51:38 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id NAA56966; Wed, 8 Dec 1999 13:51:35 -0500 (EST) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id NAA10224; Wed, 8 Dec 1999 13:51:35 -0500 (EST) Message-Id: <3.0.5.32.19991208135002.01d82140@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 08 Dec 1999 13:50:02 -0500 To: Joe Greco From: Mike Tancsa Subject: Re: Route table leaks Cc: jgreco@ns.sol.net, jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: <199912081451.IAA61233@aurora.sol.net> References: <3.0.5.32.19991208094433.01610ac0@staff.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 08:51 AM 12/8/99 -0600, Joe Greco wrote: >Most of which are routes pointing at the 3 private-net interfaces on the >machine. The info was provided more as a comparison, that quantity of routes do not necessary mean leak ? Or perhaps it does. But after 90 days, you would think the problem would have been hit no ? ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 10:58:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id D93641578C; Wed, 8 Dec 1999 10:54:09 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C0AFC1CD623; Wed, 8 Dec 1999 10:54:09 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Dec 1999 10:54:09 -0800 (PST) From: Kris Kennaway To: Morten Seeberg Cc: Steve O'Hara-Smith , stable@freebsd.org Subject: Re: is -STABLE really stable? In-Reply-To: <036901bf40b4$5573b300$1600a8c0@SOS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 7 Dec 1999, Morten Seeberg wrote: > Revising the release times for 3.0, 3.1, 3.2, 3.3 I know realise that I= =B4ve > just misunderstood the way -STABLE works :) And that I should just start > using RELEASE on my production machines, instead of -STABLE, which I thou= ght > was "better"/"more stable" than RELEASE. Probably a 'safer' policy if you don't want to worry about whether or not some committer has just temporarily broken -stable (bad committer! No biscuit!) is to wait for a -release, subscribe to this list and watch what problems people find with it, WAIT say two or three weeks, and then install -stable as of that date. Unfortunately a lot of people only jump on -release once it's already out the door instead of properly helping to beta-test, which means that the bug reports only come in after it's too late. These get immediately fixed in -stable, of course, which means that there's often a substantial improvement over the first few weeks after a release. Having said that, -stable doesn't change very much over time anyway (by definition), so whichever day you pick isn't likely to make much difference (in theory, only minor changes are made to -stable, so only minor things should break :-). Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 11:29: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id E348915D2E; Wed, 8 Dec 1999 11:26:38 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id NAA80612; Wed, 8 Dec 1999 13:26:17 -0600 (CST) From: Joe Greco Message-Id: <199912081926.NAA80612@aurora.sol.net> Subject: Re: Route table leaks In-Reply-To: <3.0.5.32.19991208135002.01d82140@staff.sentex.ca> from Mike Tancsa at "Dec 8, 1999 1:50: 2 pm" To: mike@sentex.net (Mike Tancsa) Date: Wed, 8 Dec 1999 13:26:16 -0600 (CST) Cc: jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 08:51 AM 12/8/99 -0600, Joe Greco wrote: > >Most of which are routes pointing at the 3 private-net interfaces on the > >machine. > > The info was provided more as a comparison, that quantity of routes do not > necessary mean leak ? Or perhaps it does. But after 90 days, you would > think the problem would have been hit no ? My _point_ was that this issue (or some variant) has been around for some time. I suspect it doesn't have to do with packet forwarding, but does somehow have to do with machines that actually establish or receive TCP connections. Why this only affects certain types of systems, I don't know. Certainly a large number of routes doesn't mean anything. However, > vmstat -m | grep routetbl|grep K routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 > netstat -rn | wc -l 16 289178 blocks (and 40960K - that's 40MB) in use to support 16 routes (that is 2.5MB of memory used per listed route) is a bit on the excessive side. Your example was more along the lines of 20MB to support 65000 routes, only a few hundred bytes per route, which is roughly on the order of what I'd expect per route. I'd think that inbound connections are less likely to be an issue than outbound ones, as inbound connections get really heavily exercised on things like web servers. But that is off-the-top-of-my-head speculation, and I've nothing to support that theory. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 11:29:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 01BEA15D6C; Wed, 8 Dec 1999 11:27:31 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA98301; Wed, 8 Dec 1999 11:25:44 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912081925.LAA98301@gndrsh.dnsmgr.net> Subject: Re: Route table leaks In-Reply-To: <199912081423.IAA59277@aurora.sol.net> from Joe Greco at "Dec 8, 1999 08:23:35 am" To: jgreco@ns.sol.net (Joe Greco) Date: Wed, 8 Dec 1999 11:25:43 -0800 (PST) Cc: jdp@polstra.com (John Polstra), current@FreeBSD.ORG, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Have any of you been seeing route table leaks in -current? I noticed > > this week that cvsup-master.freebsd.org is suffering from them. I > > actually had to reboot it because it couldn't allocate any more. From > > the "vmstat -m" output: > > > > Memory statistics by type Type Kern > > Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) > > [...] > > routetbl150907 21221K 21221K 21221K 462184 0 0 16,32,64,128,256 > > [...] > > I can think of some experiments to try in order to start to diagnose > > it. But first, have any of you seen this problem? > > Hell, I've been seeing this for well over a year. The last time I mentioned > it, everybody seemed to think I was nuts. :-) :-) > FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 > Mine has leeked very much, and this is on a bgp4 gated box: routetbl143395 19599K 21961K 32768K 2344966 0 0 16,32,64,128,256 Note the request counts vs total table size, oh and: {104}% netstat -ran | wc 69398 418030 4862684 {105}% uptime 11:20AM up 7 days, 8:15, 1 user, load averages: 0.21, 0.06, 0.02 {106}% uname -a FreeBSD br1 3.3-STABLE FreeBSD 3.3-STABLE #0: Tue Nov 23 20:15:59 PST 1999 I haven't leaked away as much as you have, so it seems that actually having the full routing table reduces it :-) > When it gets like that, it starts losing the ability to add further ARP > table entries and essentially starts going randomly deaf to local hosts > (and to a lesser extent remote hosts). Thats what I have seen on 3 occassions now, you get a can't allocate llinfo error from arpresolve/arplookup: /var/log/messages.1.gz:Dec 1 18:01:18 br1 /kernel: arpresolve: can't allocate llinfo for 205.238.40.30rt Note the bad printf output, that ``rt'' really is in my syslogs :-( > > I've also seen it on a 3.3-RELEASE box, but it's not currently happening > to any of them right now. > > Machines in question are SMP boxes, and get hit fairly heavily in various > Usenet news server roles. Seems to happen quite a bit more often on boxes > that talk to a wide variety of host types, and I can't recall having seen > it on boxes that only talk to other FreeBSD boxes. But that could also be > because the network environment is much more controlled internally. > Running a few full blown IBGP and EBGP sessions carrying 2 or more view of the full 68K internet route routing table and it takes about 7 to 10 days of route churn on a large KVM space kernel to cause it to have the llinfo problem... or at least I think this is what I have been seeing since I upgraded our 3.2 systems to 3.3-stable about 3 weeks ago... before this we where getting at least 30 day uptimes (about all I'd let it get before some other change had has rebooting, not due to a problem on the boxes) -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 11:37:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B2EDA15A83; Wed, 8 Dec 1999 11:37:10 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id LAA98324; Wed, 8 Dec 1999 11:35:33 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912081935.LAA98324@gndrsh.dnsmgr.net> Subject: Re: Route table leaks In-Reply-To: <3.0.5.32.19991208094433.01610ac0@staff.sentex.ca> from Mike Tancsa at "Dec 8, 1999 09:44:33 am" To: mike@sentex.net (Mike Tancsa) Date: Wed, 8 Dec 1999 11:35:33 -0800 (PST) Cc: jgreco@ns.sol.net (Joe Greco), jdp@polstra.com (John Polstra), stable@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >Hell, I've been seeing this for well over a year. The last time I mentioned > >it, everybody seemed to think I was nuts. :-) > > > >FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > > > routetbl289178 40961K 40961K 40960K 435741 0 0 > 16,32,64,128,256 > > Well, I havent seen problems of this nature (yet), but for reference, > > > netstat -nr | wc > 69585 419164 4875822 > > routetbl143718 19653K 21229K 21229K 6527152 0 0 16,32,64,128,256 > > FreeBSD 3.3-RC #0: Wed Sep 8 13:37:19 EDT 1999 > uptime > 9:44AM up 90 days, 20:35, 2 users, load averages: 0.00, 0.01, 0.00 > > This is a border router with 2 views of the net running defaultless. See my other email, and now upon further though having full routes without a default means the clonning code doesn't get used much, since you already have real routes :-). Thus your problem would be less. Hummmm.... let me go to a box running ``defaulted'' yet producing several 100k connections/day and see how bad it's route space looks. routetbl 329 45K 1532K 42709K 504060 0 0 16,32,64,128,256 :rgrimes{100}% netstat -ran | wc 69 403 4675 Yep... looks like it leaked 329-69==260 in 17 days uptime :-( -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 12: 9:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nohow.demon.co.uk (nohow.demon.co.uk [212.228.18.189]) by hub.freebsd.org (Postfix) with ESMTP id 923F81612F for ; Wed, 8 Dec 1999 11:57:11 -0800 (PST) (envelope-from noway@nohow.demon.co.uk) Received: from localhost (noway@localhost) by nohow.demon.co.uk (8.9.3/8.9.3) with ESMTP id TAA01772 for ; Wed, 8 Dec 1999 19:56:50 GMT (envelope-from noway@nohow.demon.co.uk) Date: Wed, 8 Dec 1999 19:56:49 +0000 (GMT) From: Jose Marques To: freebsd-stable@freebsd.org Subject: 3.2 -> 3.3-stable Message-ID: X-No-Archive: yes MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would like to use CVSup to bring a machine currently running FreeBSD 3.2-RELEASE up to 3.3-stable. Are there any "gotchas" that I should be aware of? -- Jose Marques To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 12:29:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 6B80814BDC; Wed, 8 Dec 1999 12:27:19 -0800 (PST) (envelope-from root@foxbert.skynet.be) Received: from foxbert.skynet.be (foxbert.skynet.be [195.238.1.45]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id VAA22995; Wed, 8 Dec 1999 21:27:07 +0100 (MET) Received: (from root@localhost) by foxbert.skynet.be (8.9.1/jovi-pop-2.1) id VAA01416; Wed, 8 Dec 1999 21:27:02 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912081926.NAA80612@aurora.sol.net> References: <199912081926.NAA80612@aurora.sol.net> Date: Wed, 8 Dec 1999 21:26:05 +0100 To: Joe Greco , mike@sentex.net (Mike Tancsa) From: Brad Knowles Subject: Re: Route table leaks Cc: jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:26 PM -0600 1999/12/8, Joe Greco wrote: >> vmstat -m | grep routetbl|grep K > routetbl289178 40961K 40961K 40960K 435741 0 0 >16,32,64,128,256 >> netstat -rn | wc -l > 16 I had never looked at this on my machines (main news peering server in the Top 100, one Intel EtherExpress Pro 10/100+ 100-Base-TX interface with a default route, running 3.2-RELEASE): $ vmstat -m | grep routetbl | grep K routetbl 246 34K 36K 40960K 920 0 0 16,32,64,128,256 $ netstat -nr | wc -l 13 $ uptime 9:07PM up 7 days, 8:06, 1 user, load averages: 2.87, 3.14, 3.15 $ ps axl | grep ':' | wc -l 379 > 289178 blocks (and 40960K - that's 40MB) in use to support 16 routes (that > is 2.5MB of memory used per listed route) is a bit on the excessive side. This machine hasn't been up very long, is running an application profile that I assume is somewhat similar to yours (although I'm sure yours is much more heavily tuned, as well as loaded), but 2,835.692 bytes per route (26K/13) still seems a bit excessive. I've got another machine (an internal mailing list server, very very lightly loaded, one Intel EtherExpress Pro 10/100+ 100-Base-TX interface with a default route, running 3.0-RELEASE) that looks much more reasonable: $ vmstat -m | grep routetbl | grep K routetbl 32 4K 8K 10400K 13212 0 0 16,32,64,128,256 $ netstat -nr | wc -l 11 $ uptime 9:25PM up 135 days, 11:04, 1 user, load averages: 0.02, 0.01, 0.00 $ ps axl | grep ':' | wc -l 30 However, even 744.727 bytes per route (8K/11) seems a little higher than what I would expect, although this is *much* better than almost 3KB/route, and especially better than 2,621,504.000 bytes/route (40MB/16). The 312.402 bytes/route (20.731MB/69585) that Mike reported seems much more realistic. > I'd think that inbound connections are less likely to be an issue than > outbound ones, as inbound connections get really heavily exercised on > things like web servers. But that is off-the-top-of-my-head speculation, > and I've nothing to support that theory. Unfortunately, I don't have any FreeBSD web servers here that I can test that theory with. I'm trying to get more FreeBSD production servers installed here, but progress has been rather slow -- I can only roll them in as old servers need to be replaced, and as FreeBSD supports the hardware & software I need to use in order to support the application. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 13:21: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from puffer.quadrunner.com (puffer.quadrunner.com [205.166.195.4]) by hub.freebsd.org (Postfix) with ESMTP id 91EA515670 for ; Wed, 8 Dec 1999 13:20:53 -0800 (PST) (envelope-from manek@ecst.csuchico.edu) Received: from after (root@puffer.quadrunner.com [205.166.195.4]) by puffer.quadrunner.com (8.9.2/QUAD-2.1) with SMTP id NAA08023; Wed, 8 Dec 1999 13:19:34 -0800 (PST) From: "Sameer R. Manek" To: "Jose Marques" , Subject: RE: 3.2 -> 3.3-stable Date: Wed, 8 Dec 1999 13:20:47 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Jose Marques > Sent: Wednesday, December 08, 1999 11:57 AM > > I would like to use CVSup to bring a machine currently running FreeBSD > 3.2-RELEASE up to 3.3-stable. Are there any "gotchas" that I should be > aware of? Biggest one would be if you cvsup tonight, you'll jump to 3.4-RC. 3.4-RC is a release canidate, aka beta for 3.4-RELEASE. You might want to wait until 3.4-RELEASE, the source tree can get a little unstable just before -RELEASE, as the developers scramble to get patches commited before the code freeze. 3.4-RELEASE is scheduled to come out right around the same time Santa does, so might as well wait a few days, and have some eggnog. Sameer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 13:26:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dbitech.bc.ca (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (Postfix) with SMTP id 8010215227 for ; Wed, 8 Dec 1999 13:26:12 -0800 (PST) (envelope-from darcy@ok-connect.com) Received: (qmail 12268 invoked from network); 8 Dec 1999 21:26:10 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 8 Dec 1999 21:26:10 -0000 Message-Id: <3.0.32.19991208132705.009969d0@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 08 Dec 1999 13:27:05 -0800 To: stable@FreeBSD.ORG From: Darcy Buskermolen Subject: Re: Route table leaks Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'll add in my 2ct's worth about a similar router I've admind. bash-2.01$ uname -r 2.2.6-RELEASE bash-2.01$ vmstat -m | grep routetbl | grep K routetbl 394 46K 239K 18528K 4649348 0 0 16,32,64,128,256 bash-2.01$ netstat -nr | wc -l 123 bash-2.01$ uptime 1:16PM up 276 days, 4:53, 2 users, load averages: 0.00, 0.00, 0.00 bash-2.01$ ps axl | grep ':' | wc -l 24 At 09:26 PM 12/8/99 +0100, Brad Knowles wrote: >At 1:26 PM -0600 1999/12/8, Joe Greco wrote: > >>> vmstat -m | grep routetbl|grep K >> routetbl289178 40961K 40961K 40960K 435741 0 0 >>16,32,64,128,256 >>> netstat -rn | wc -l >> 16 > > I had never looked at this on my machines (main news peering >server in the Top 100, one Intel EtherExpress Pro 10/100+ 100-Base-TX >interface with a default route, running 3.2-RELEASE): > >$ vmstat -m | grep routetbl | grep K > routetbl 246 34K 36K 40960K 920 0 0 16,32,64,128,256 >$ netstat -nr | wc -l > 13 >$ uptime > 9:07PM up 7 days, 8:06, 1 user, load averages: 2.87, 3.14, 3.15 >$ ps axl | grep ':' | wc -l > 379 > >> 289178 blocks (and 40960K - that's 40MB) in use to support 16 routes (that >> is 2.5MB of memory used per listed route) is a bit on the excessive side. > > This machine hasn't been up very long, is running an application >profile that I assume is somewhat similar to yours (although I'm sure >yours is much more heavily tuned, as well as loaded), but 2,835.692 >bytes per route (26K/13) still seems a bit excessive. > > I've got another machine (an internal mailing list server, very >very lightly loaded, one Intel EtherExpress Pro 10/100+ 100-Base-TX >interface with a default route, running 3.0-RELEASE) that looks much >more reasonable: > >$ vmstat -m | grep routetbl | grep K > routetbl 32 4K 8K 10400K 13212 0 0 16,32,64,128,256 >$ netstat -nr | wc -l > 11 >$ uptime > 9:25PM up 135 days, 11:04, 1 user, load averages: 0.02, 0.01, 0.00 >$ ps axl | grep ':' | wc -l > 30 > > However, even 744.727 bytes per route (8K/11) seems a little >higher than what I would expect, although this is *much* better than >almost 3KB/route, and especially better than 2,621,504.000 >bytes/route (40MB/16). The 312.402 bytes/route (20.731MB/69585) that >Mike reported seems much more realistic. > >> I'd think that inbound connections are less likely to be an issue than >> outbound ones, as inbound connections get really heavily exercised on >> things like web servers. But that is off-the-top-of-my-head speculation, >> and I've nothing to support that theory. > > Unfortunately, I don't have any FreeBSD web servers here that I >can test that theory with. I'm trying to get more FreeBSD production >servers installed here, but progress has been rather slow -- I can >only roll them in as old servers need to be replaced, and as FreeBSD >supports the hardware & software I need to use in order to support >the application. > >-- > These are my opinions -- not to be taken as official Skynet policy > ____________________________________________________________________ >|o| Brad Knowles, Belgacom Skynet NV/SA |o| >|o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| >|o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| >|o| http://www.skynet.be Belgium |o| >\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ > Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. > Unix is very user-friendly. It's just picky who its friends are. > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-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 8 14: 5: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c1870039.telekabel.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id ECD8614C1D for ; Wed, 8 Dec 1999 14:04:58 -0800 (PST) (envelope-from roelof@nisser.com) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id XAA03998; Wed, 8 Dec 1999 23:04:52 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <384ED624.5EA4E41D@nisser.com> Date: Wed, 08 Dec 1999 23:05:24 +0100 From: Roelof Osinga Organization: eboa - engineering buro Office Automation X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: mw@freibergnet.de Cc: FreeBSD Stable Subject: Re: ifpw forwarding problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Welk wrote: > > Your problem is, that forwarding packets by rules to other hosts is not > the same as forwarding packets to hosts through a NAT environment. Look > at the natd man page, search for the redirect options mentioned there. Thanks. I did do that, but for testing purposes I tried to redirect it through the other NIC as well. The natd has been told to listen only on the ep1 NIC. > In my case, there's a FreeBSD machine doing NAT here. It has two IP > addresses on the outer world interface, but this shouldn't be a > significant difference. Actually it is identical to what I have. > I have a file named natd.conf that's loaded on startup doing a > "natd -f natd.conf" - you may put it somewhere in the file system > where you like it and use the absolute path, I've chosen /etc. Dito. > use_sockets > same_ports > port 8668 > deny_incoming no > alias_address aaa.aaa.aaa.aaa > redirect_port tcp bbb.bbb.bbb.bbb:5900 aaa.aaa.aaa.aaa:5900 Second thing I tried, but with the difference that I rely on "deny incoming no" to be the default. In my case though I would probably should be using proxy_rule with type encode_ip_hdr since it's intended for webtraffic. It would be nice to know where the hits are coming from. > In this case, the port 5900 (which is by default used for a first VNC > session) is redirected to an interal Windows box that can be accessed > this way. That's why I explicitly drop them . > aaa.aaa.aaa.aaa is the external network address of the router, > bbb.bbb.bbb.bbb the internal host (192.168...) Funny in that I did try with nisser:/home/www/Slak$ cat /etc/natd.conf # as used in rc.conf.local -use_sockets -same_ports #-redirect_port tcp 212.187.0.39:8080 10.0.0.3:80 redirection enabled. It didn't work when accessing that IP address from within. Which is why I tried the internal NIC. > You need to do that this way in a NAT'ed environment because someone > has to change the IP addresses as they are needed to make it work > properly. Yeah, but this is the internal NIC . > For the ipfw setup, a directive like > ... Same as the one I listed. > But if it works in this case, you have now a good starting point to > do more :-) Alas it did not work in my case. However, that was with IPFIREWALL_FORWARD enabled. Turned out that made my system quit unstable, or rather erratic. After a couple of hours I switched back to the previous kernel. Didn't matter whether or not I had redirection rules active either for ipfw or natd. So maybe that is why natd redirection failed. Don't know, can't try yet since it's a live system. Which reminds me, do you happen to know if natd responds to HUP? The manpage doesn't mention it. > No RTFM intended, but I found the following man pages very helpful when > I started with ipfw/natd and so on: divert(4), dummynet(4), ipfw(8), > ipfirewall(4). Although dummynet has to do with bandwidth limiting > and delaying (this is integrated into the IPFW functionality), it gives > some further information that helps to understand how packets pass > through the firewall. All of which I've read one time or another. Most multiple times . Anyway, since my rules mimick your (barring the "deny_incoming no") and yours do work, I know at least it's not the rules. The natd rules, that is. I'll try with the kernel as is at the next opportunity. Thanks. Roelof -- Home is where the (@) http://eboa.com/ is. Telekabel home http://nisser.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 8 14: 6:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A334D151C1; Wed, 8 Dec 1999 14:06:26 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA43590; Wed, 8 Dec 1999 14:06:14 -0800 (PST) (envelope-from dillon) Date: Wed, 8 Dec 1999 14:06:14 -0800 (PST) From: Matthew Dillon Message-Id: <199912082206.OAA43590@apollo.backplane.com> To: Brad Knowles Cc: Joe Greco , mike@sentex.net (Mike Tancsa), jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Route table leaks References: <199912081926.NAA80612@aurora.sol.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :At 1:26 PM -0600 1999/12/8, Joe Greco wrote: : :>> vmstat -m | grep routetbl|grep K :> routetbl289178 40961K 40961K 40960K 435741 0 0 :>16,32,64,128,256 :>> netstat -rn | wc -l :> 16 Please use 'netstat -rna' to get a listing of *all* the routes, including the temporary ones, not just the non-temporary routes. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 14:37:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 864EF152AD; Wed, 8 Dec 1999 14:37:25 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id QAA94094; Wed, 8 Dec 1999 16:37:04 -0600 (CST) From: Joe Greco Message-Id: <199912082237.QAA94094@aurora.sol.net> Subject: Re: Route table leaks In-Reply-To: <199912082206.OAA43590@apollo.backplane.com> from Matthew Dillon at "Dec 8, 1999 2: 6:14 pm" To: dillon@apollo.backplane.com (Matthew Dillon) Date: Wed, 8 Dec 1999 16:37:04 -0600 (CST) Cc: blk@skynet.be, jgreco@ns.sol.net, mike@sentex.net, jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > : > :At 1:26 PM -0600 1999/12/8, Joe Greco wrote: > : > :>> vmstat -m | grep routetbl|grep K > :> routetbl289178 40961K 40961K 40960K 435741 0 0 > :>16,32,64,128,256 > :>> netstat -rn | wc -l > :> 16 > > Please use 'netstat -rna' to get a listing of *all* the routes, including > the temporary ones, not just the non-temporary routes. > > -Matt > netstat -rna |wc -l 17 > netstat -rn | wc -l 16 > arp -an |wc -l 0 (yes, really) I'm not sure a more recent box would be different. ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 14:44: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailhotel.chrillesen.dk (vax.chrillesen.dk [193.88.12.35]) by hub.freebsd.org (Postfix) with ESMTP id 779B915274; Wed, 8 Dec 1999 14:43:38 -0800 (PST) (envelope-from barry@NetScum.dK) Received: by mailhotel.chrillesen.dk (Postfix, from userid 1009) id 03F52B780; Wed, 8 Dec 1999 23:43:31 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mailhotel.chrillesen.dk (Postfix) with ESMTP id 8F7CAB77F; Wed, 8 Dec 1999 23:43:31 +0100 (CET) Date: Wed, 8 Dec 1999 23:43:31 +0100 (CET) From: Anonymous Coward X-Sender: barry@vax.chrillesen.dk Reply-To: luserboy@netscum.dk To: current@freebsd.org, stable@freebsd.org Subject: Console mouse cut'n'paste sometimes is ... well... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hellø¸ ãll ýøu kewl hãcker ð00ðZ! Mãý Ï reþørt this ãs ã bug¸ ør wøulð ýøu ãgree thãt this is better ðescribeð ãs ãn unðøcumenteð Feãture? Ýesterðãý´s instãll fløþþies øf -STÃBLË ãnð -©Û®®ËNT... Ï think this line in /etc/rc.cønf is the þrøblem: scrnmãþ=¨isø-8859-¹_tø_cþ4³7¨ Ï´m nøt cømþlãining¸ Ï ÃM ³L³³T¸ ÞHËî M˸ ØKÃÝ? bãrrý bøuwsmã (use reþlý-tø heãðer før ãný such) --  >cliþ< es¹: <ÃuðiøÞ©Ï ËS¹³70> rev 0x0¹ int ã irq 9 øn þci0.8.0 þcm¹: using Ï/Ø sþãce register mãþþing ãt 0x¹000 es2: <ÃuðiøÞ©Ï ËS¹³7¹> rev 0x06 int ã irq ¹5 øn þci0.9.0 þcm2: using Ï/Ø sþãce register mãþþing ãt 0x¹080 es¹³7¹: cøðec venðør T®Ã revisiøn ³ es¹³7¹: cøðec feãtures Bãss & Treble es¹³7¹: stereø enhãncement: nø ³à stereø enhãncement vgã0: <©irrus Løgic Gà5446 SVGàcøntrøller> rev 0x45 øn þci0.¹³.0 Þrøbing før ðevices øn Þ©Ï bus ¹: fxþ0: <Ïntel ËtherËxþress Þrø ¹0/¹00B Ëthernet> rev 0x05 int ã irq ¹¹ øn þci¹.³. 0 fxþ0: Ëthernet ãððress 00:90:27:³ð:³5:8e ncr0:  rev 0x0¹ int ã irq ¹0 øn þci¹.4.0 Þrøbing før ÞnÞ ðevices: Þrøbing før ðevices øn the ÏSàbus: sc0 øn isã sc0: VGàcølør <¹2 virtuãl cønsøles¸ flãgs=0x0> ãtkbðc0 ãt 0x60-0x6f øn møtherbøãrð ãtkbð0 irq ¹ øn isã þsm0 irq ¹2 øn isã >©LÏÞ< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 15:51:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from stingray.ivision.co.uk (avengers.ivision.co.uk [195.50.91.40]) by hub.freebsd.org (Postfix) with ESMTP id 4A2AB152EF; Wed, 8 Dec 1999 15:51:39 -0800 (PST) (envelope-from jasper@ivision.co.uk) Received: from stingray.ivision.co.uk ([195.50.91.40]) by stingray.ivision.co.uk with esmtp (Exim 2.04 #1) id 11vqpC-00055N-00; Wed, 8 Dec 1999 23:48:46 +0000 Date: Wed, 8 Dec 1999 23:48:45 +0000 (BST) From: Jasper Wallace To: Joe Greco Cc: Matthew Dillon , blk@skynet.be, mike@sentex.net, jdp@polstra.com, stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Route table leaks In-Reply-To: <199912082237.QAA94094@aurora.sol.net> Message-ID: X-NCC-RegID: uk.instant-web 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, 8 Dec 1999, Joe Greco wrote: > > > > : > > :At 1:26 PM -0600 1999/12/8, Joe Greco wrote: > > : > > :>> vmstat -m | grep routetbl|grep K > > :> routetbl289178 40961K 40961K 40960K 435741 0 0 > > :>16,32,64,128,256 > > :>> netstat -rn | wc -l > > :> 16 > > > > Please use 'netstat -rna' to get a listing of *all* the routes, including > > the temporary ones, not just the non-temporary routes. > > > > -Matt > > > netstat -rna |wc -l > 17 > > netstat -rn | wc -l > 16 > > arp -an |wc -l > 0 quite heavily loaded web server: # netstat -ran | wc -l 106 (that was 177 a few mins ago). # vmstat -m | grep routetbl|grep K routetbl 228 32K 649K 19661K 1120980 0 0 16,32,64,128,256 # uname -r 2.2.2-RELEASE # uptime 11:55PM up 23 days, 12:31, 1 user, load averages: 0.04, 0.03, 0.00 # Slightly more atomic mesurament: # netstat -ran | wc -l ; vmstat -m | grep routetbl | grep '[0-9]K' 175 routetbl 354 49K 649K 19661K 1121106 0 0 16,32,64,128,256 -- Internet Vision Internet Consultancy Tel: 0171 589 4500 60 Albert Court & Web development Fax: 0171 589 4522 Prince Consort Road vision@ivision.co.uk London SW7 2BE http://www.ivision.co.uk/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 17:20: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from beebite.ugh.net.au (beebite.ugh.net.au [203.31.238.37]) by hub.freebsd.org (Postfix) with ESMTP id 188D114A2D for ; Wed, 8 Dec 1999 17:19:58 -0800 (PST) (envelope-from andrew@ugh.net.au) Received: by beebite.ugh.net.au (Postfix, from userid 1000) id 22A8753; Thu, 9 Dec 1999 12:19:54 +1100 (EST) Received: from localhost (localhost [127.0.0.1]) by beebite.ugh.net.au (Postfix) with ESMTP id 0DB004C for ; Thu, 9 Dec 1999 11:19:54 +1000 (EST) Date: Thu, 9 Dec 1999 11:19:53 +1000 (EST) From: andrew@ugh.net.au To: freebsd-stable@freebsd.org Subject: CRON in malloc(): warning: pointer to wrong page. Message-ID: X-WonK: *wibble* MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Every time a cron job runs it produces the output: CRON in malloc(): warning: pointer to wrong page. which gets mailed to root. I searched the archives but didn't come up with anything. Nothing seems to produce that error when run interactively. We're running 3.3-STABLE from November the 29th on an IBM 686 200 with 32MB RAM and an IDE drive. On a probably related matter we had a lot of processes die with signal 4 (one or two a day). We swapped the RAM and I thought it had stopped but one died yesterday (telnetd). Previously running make index in /usr/ports would always die with sig4 but since the RAM swap its been fine... Any suggestions? I assume sig4 indicates that there is corruption in either the memory, cache or bus but I have no idea why or what causes the CRON error. Thanks, Andrew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 17:49:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 11AC21558C for ; Wed, 8 Dec 1999 17:49:25 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id UAA30213; Wed, 8 Dec 1999 20:49:15 -0500 (EST) Date: Wed, 8 Dec 1999 20:49:15 -0500 (EST) From: Bosko Milekic To: andrew@ugh.net.au Cc: freebsd-stable@FreeBSD.ORG Subject: Re: CRON in malloc(): warning: pointer to wrong page. 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, 9 Dec 1999 andrew@ugh.net.au wrote: !>On a probably related matter we had a lot of processes die with signal 4 !>(one or two a day). We swapped the RAM and I thought it had stopped but !>one died yesterday (telnetd). Previously running make index in /usr/ports !>would always die with sig4 but since the RAM swap its been fine... !> !>Any suggestions? I assume sig4 indicates that there is corruption in !>either the memory, cache or bus but I have no idea why or what causes the !>CRON error. !> Well, are the processes dying with signal 4 dumping core? If so, have you tried debugging from the core dump? Your malloc() problem could be related to something that you discover this way. After all, the default action on receipt of signal 4 would be to dump core. --Bosko -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 17:50:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 454A315102; Wed, 8 Dec 1999 17:50:41 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 13C001CD736; Wed, 8 Dec 1999 17:50:41 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Wed, 8 Dec 1999 17:50:40 -0800 (PST) From: Kris Kennaway To: "Sameer R. Manek" Cc: Jose Marques , freebsd-stable@freebsd.org Subject: RE: 3.2 -> 3.3-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 On Wed, 8 Dec 1999, Sameer R. Manek wrote: > Biggest one would be if you cvsup tonight, you'll jump to 3.4-RC. 3.4-RC is > a release canidate, aka beta for 3.4-RELEASE. You might want to wait until > 3.4-RELEASE, the source tree can get a little unstable just before -RELEASE, > as the developers scramble to get patches commited before the code freeze. > > 3.4-RELEASE is scheduled to come out right around the same time Santa does, > so might as well wait a few days, and have some eggnog. Or you could do it now, and help with the beta-testing, instead of doing it later and finding a bug which could have been prevented from shipping :) For general updating issues, see /usr/src/UPDATING after cvsup (or use the cvsweb page on freebsd.org and find the most recent 3.x version). Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 18:35:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id F082A15148 for ; Wed, 8 Dec 1999 18:35:12 -0800 (PST) (envelope-from dragon.s@ix.netcom.com) Received: from ix.netcom.com (gra-mi13-219.ix.netcom.com [206.214.128.219]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id VAA18942 for ; Wed, 8 Dec 1999 21:35:02 -0500 (EST) Message-ID: <384F13CD.1A1395A0@ix.netcom.com> Date: Wed, 08 Dec 1999 21:28:30 -0500 From: Dan Diephouse X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: slight PPP problems Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello everyone. I have set up PPP over an ISDN modem and it appears to work well. Unfortunately looks aren't everything. We have to pay for each time we dial out on our ISDN modem. I have ppp set on -ddial so the conection automatically stays up. In my logs it appears to be disconnecting after a number of packets. I don't know what to make of. I've attached the logs so you can see for yourself. If anything else needs to be include, just notify me. Also I have a message at the end of my dmesg conerning "rtinit" that I haven't investigated yet if anyone would like to enlighten me :) Thank You, Dan Diephouse DMESG: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-STABLE #8: Tue Nov 16 13:10:51 EST 1999 root@owl.grbs.org:/usr/src/sys/compile/OWL Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 134217728 (131072K bytes) config> avail memory = 126787584 (123816K bytes) Programming 28 pins in IOAPIC #0 EISA INTCONTROL = 00000e20 IOAPIC #0 intpint 24 -> irq 13 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x001b0011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc02d6000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02d609c. Pentium Pro MTRR support enabled eisa0: Probing for devices on the EISA bus Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.13.0 chip2: rev 0x01 on pci0.15.0 chip3: rev 0x07 on pci0.20.0 Probing for devices on PCI bus 1: vga0: rev 0x22 int a irq 255 on pci1.6.0 tl0: rev 0x10 int a irq 10 on pci1.7.0 tl0: Ethernet address: 00:80:5f:a6:29:6f tl0: autoneg not complete, no carrier ncr0: rev 0x03 int a irq 11 on pci1.9.0 xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x24 int a irq 5 on pci1.13.0 xl0: Ethernet address: 00:10:4b:66:b4:3b xl0: autoneg not complete, no carrier (forcing half-duplex, 10Mbps) Probing for devices on PCI bus 2: ida0: rev 0x02 int a irq 9 on pci2.0.0 ida0: drvs=2 firm_rev=1.36 ida0: unit 0 (id0): id0: 8024MB (16434495 total sec), 1023 cyl, 255 head, 63 sec, bytes/sec 512 ida0: unit 1 (id1): id1: 4257MB (8719950 total sec), 953 cyl, 183 head, 50 sec, bytes/sec 512 ida: wdc vector stealing on (mode = always, boot major = 0) Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in ida0 not found at 0x0 ppc0 at 0x3bc irq 7 flags 0x40 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: Broken MP table detected: 8254 is not connected to IO APIC int pin 2 APIC_IO: routing 8254 via 8259 on pin 0 IP packet filtering initialized, divert disabled, rule-based forwarding disabled, unlimited logging Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to wd0s1a rtinit: wrong ifa (0xc19c2000) was (0xc1230380) rtinit: wrong ifa (0xc1231d00) was (0xc1230080) Daily Output for the tun0 device day 1: Network interface status: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll tl0 1500 00.80.5f.a6.29.6f 439078 0 427924 0 0 tl0 1500 192.168 192.168.0.3 439078 0 427924 0 0 xl0* 1500 00.10.4b.66.b4.3b 0 0 0 0 0 lp0* 1500 0 0 0 0 0 tun0 1500 340470 0 325940 0 0 tun0 1500 gr-ppp142.tri gr-ppp142.trito 340470 0 325940 0 0 tun0 1500 gr-ppp158.tri gr-ppp158.trito 340470 0 325940 0 0 tun0 1500 gr-ppp209.tri gr-ppp209.trito 340470 0 325940 0 0 tun0 1500 gr-ppp214.tri gr-ppp214.trito 340470 0 325940 0 0 tun0 1500 gr-ppp183.tri gr-ppp183.trito 340470 0 325940 0 0 tun0 1500 gr-ppp107.tri gr-ppp107.trito 340470 0 325940 0 0 tun0 1500 gr-ppp53.trit gr-ppp53.triton 340470 0 325940 0 0 tun0 1500 gr-ppp9.trito gr-ppp9.triton. 340470 0 325940 0 0 tun0 1500 gr-ppp188.tri gr-ppp188.trito 340470 0 325940 0 0 tun0 1500 gr-ppp97.trit gr-ppp97.triton 340470 0 325940 0 0 tun0 1500 gr-ppp136.tri gr-ppp136.trito 340470 0 325940 0 0 tun0 1500 gr-ppp109.tri gr-ppp109.trito 340470 0 325940 0 0 tun0 1500 gr-ppp67.trit gr-ppp67.triton 340470 0 325940 0 0 tun0 1500 gr-ppp144.tri gr-ppp144.trito 340470 0 325940 0 0 tun0 1500 gr-ppp23.trit gr-ppp23.triton 340470 0 325940 0 0 tun0 1500 gr-ppp98.trit gr-ppp98.triton 340470 0 325940 0 0 tun0 1500 gr-ppp196.tri gr-ppp196.trito 340470 0 325940 0 0 tun0 1500 gr-ppp112.tri gr-ppp112.trito 340470 0 325940 0 0 tun0 1500 gr-ppp210.tri gr-ppp210.trito 340470 0 325940 0 0 tun0 1500 gr-ppp99.trit gr-ppp99.triton 340470 0 325940 0 0 tun0 1500 gr-ppp177.tri gr-ppp177.trito 340470 0 325940 0 0 tun0 1500 gr-ppp204.tri gr-ppp204.trito 340470 0 325940 0 0 tun0 1500 gr-ppp52.trit gr-ppp52.triton 340470 0 325940 0 0 tun0 1500 gr-ppp129.tri gr-ppp129.trito 340470 0 325940 0 0 tun0 1500 gr-ppp205.tri gr-ppp205.trito 340470 0 325940 0 0 tun0 1500 gr-ppp24.trit gr-ppp24.triton 340470 0 325940 0 0 tun0 1500 gr-ppp92.trit gr-ppp92.triton 340470 0 325940 0 0 tun0 1500 gr-ppp126.tri gr-ppp126.trito 340470 0 325940 0 0 tun0 1500 gr-ppp172.tri gr-ppp172.trito 340470 0 325940 0 0 tun0 1500 gr-ppp213.tri gr-ppp213.trito 340470 0 325940 0 0 tun0 1500 gr-ppp54.trit gr-ppp54.triton 340470 0 325940 0 0 tun0 1500 gr-ppp86.trit gr-ppp86.triton 340470 0 325940 0 0 tun0 1500 gr-ppp119.tri gr-ppp119.trito 340470 0 325940 0 0 tun0 1500 gr-ppp151.tri gr-ppp151.trito 340470 0 325940 0 0 tun0 1500 gr-ppp193.tri gr-ppp193.trito 340470 0 325940 0 0 tun0 1500 gr-ppp211.tri gr-ppp211.trito 340470 0 325940 0 0 tun0 1500 gr-ppp14.trit gr-ppp14.triton 340470 0 325940 0 0 tun0 1500 gr-ppp28.trit gr-ppp28.triton 340470 0 325940 0 0 tun0 1500 gr-ppp38.trit gr-ppp38.triton 340470 0 325940 0 0 tun0 1500 gr-ppp58.trit gr-ppp58.triton 340470 0 325940 0 0 tun0 1500 gr-ppp84.trit gr-ppp84.triton 340470 0 325940 0 0 tun0 1500 gr-ppp101.tri gr-ppp101.trito 340470 0 325940 0 0 tun0 1500 gr-ppp122.tri gr-ppp122.trito 340470 0 325940 0 0 tun0 1500 gr-ppp137.tri gr-ppp137.trito 340470 0 325940 0 0 tun0 1500 gr-ppp155.tri gr-ppp155.trito 340470 0 325940 0 0 tun0 1500 gr-ppp168.tri gr-ppp168.trito 340470 0 325940 0 0 tun0 1500 gr-ppp185.tri gr-ppp185.trito 340470 0 325940 0 0 tun0 1500 triton.net gr-ppp202.trito 340470 0 325940 0 0 sl0* 552 0 0 0 0 0 ppp0* 1500 0 0 0 0 0 lo0 16384 927 0 927 0 0 lo0 16384 127 localhost 927 0 927 0 0 Daily Output for the tun0 device day 2: Network interface status: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll tl0 1500 00.80.5f.a6.29.6f 584870 1 566357 0 0 tl0 1500 192.168 192.168.0.3 584870 1 566357 0 0 xl0* 1500 00.10.4b.66.b4.3b 0 0 0 0 0 lp0* 1500 0 0 0 0 0 tun0 1500 449324 0 429181 0 0 tun0 1500 gr-ppp209.tri gr-ppp209.trito 449324 0 429181 0 0 tun0 1500 gr-ppp214.tri gr-ppp214.trito 449324 0 429181 0 0 tun0 1500 gr-ppp107.tri gr-ppp107.trito 449324 0 429181 0 0 tun0 1500 gr-ppp53.trit gr-ppp53.triton 449324 0 429181 0 0 tun0 1500 gr-ppp9.trito gr-ppp9.triton. 449324 0 429181 0 0 tun0 1500 gr-ppp188.tri gr-ppp188.trito 449324 0 429181 0 0 tun0 1500 gr-ppp109.tri gr-ppp109.trito 449324 0 429181 0 0 tun0 1500 gr-ppp67.trit gr-ppp67.triton 449324 0 429181 0 0 tun0 1500 gr-ppp196.tri gr-ppp196.trito 449324 0 429181 0 0 tun0 1500 gr-ppp112.tri gr-ppp112.trito 449324 0 429181 0 0 tun0 1500 gr-ppp210.tri gr-ppp210.trito 449324 0 429181 0 0 tun0 1500 gr-ppp99.trit gr-ppp99.triton 449324 0 429181 0 0 tun0 1500 gr-ppp177.tri gr-ppp177.trito 449324 0 429181 0 0 tun0 1500 gr-ppp204.tri gr-ppp204.trito 449324 0 429181 0 0 tun0 1500 gr-ppp129.tri gr-ppp129.trito 449324 0 429181 0 0 tun0 1500 gr-ppp205.tri gr-ppp205.trito 449324 0 429181 0 0 tun0 1500 gr-ppp92.trit gr-ppp92.triton 449324 0 429181 0 0 tun0 1500 gr-ppp126.tri gr-ppp126.trito 449324 0 429181 0 0 tun0 1500 gr-ppp172.tri gr-ppp172.trito 449324 0 429181 0 0 tun0 1500 gr-ppp54.trit gr-ppp54.triton 449324 0 429181 0 0 tun0 1500 gr-ppp119.tri gr-ppp119.trito 449324 0 429181 0 0 tun0 1500 gr-ppp151.tri gr-ppp151.trito 449324 0 429181 0 0 tun0 1500 gr-ppp211.tri gr-ppp211.trito 449324 0 429181 0 0 tun0 1500 gr-ppp14.trit gr-ppp14.triton 449324 0 429181 0 0 tun0 1500 gr-ppp28.trit gr-ppp28.triton 449324 0 429181 0 0 tun0 1500 gr-ppp38.trit gr-ppp38.triton 449324 0 429181 0 0 tun0 1500 gr-ppp84.trit gr-ppp84.triton 449324 0 429181 0 0 tun0 1500 gr-ppp101.tri gr-ppp101.trito 449324 0 429181 0 0 tun0 1500 gr-ppp155.tri gr-ppp155.trito 449324 0 429181 0 0 tun0 1500 gr-ppp185.tri gr-ppp185.trito 449324 0 429181 0 0 tun0 1500 gr-ppp202.tri gr-ppp202.trito 449324 0 429181 0 0 tun0 1500 gr-ppp2.trito gr-ppp2.triton. 449324 0 429181 0 0 tun0 1500 gr-ppp12.trit gr-ppp12.triton 449324 0 429181 0 0 tun0 1500 gr-ppp31.trit gr-ppp31.triton 449324 0 429181 0 0 tun0 1500 gr-ppp40.trit gr-ppp40.triton 449324 0 429181 0 0 tun0 1500 gr-ppp43.trit gr-ppp43.triton 449324 0 429181 0 0 tun0 1500 gr-ppp60.trit gr-ppp60.triton 449324 0 429181 0 0 tun0 1500 gr-ppp68.trit gr-ppp68.triton 449324 0 429181 0 0 tun0 1500 gr-ppp79.trit gr-ppp79.triton 449324 0 429181 0 0 tun0 1500 gr-ppp91.trit gr-ppp91.triton 449324 0 429181 0 0 tun0 1500 gr-ppp97.trit gr-ppp97.triton 449324 0 429181 0 0 tun0 1500 gr-ppp103.tri gr-ppp103.trito 449324 0 429181 0 0 tun0 1500 gr-ppp108.tri gr-ppp108.trito 449324 0 429181 0 0 tun0 1500 gr-ppp114.tri gr-ppp114.trito 449324 0 429181 0 0 tun0 1500 gr-ppp122.tri gr-ppp122.trito 449324 0 429181 0 0 tun0 1500 gr-ppp128.tri gr-ppp128.trito 449324 0 429181 0 0 tun0 1500 gr-ppp144.tri gr-ppp144.trito 449324 0 429181 0 0 tun0 1500 gr-ppp152.tri gr-ppp152.trito 449324 0 429181 0 0 tun0 1500 gr-ppp157.tri gr-ppp157.trito 449324 0 429181 0 0 tun0 1500 gr-ppp168.tri gr-ppp168.trito 449324 0 429181 0 0 tun0 1500 gr-ppp176.tri gr-ppp176.trito 449324 0 429181 0 0 tun0 1500 gr-ppp187.tri gr-ppp187.trito 449324 0 429181 0 0 tun0 1500 gr-ppp193.tri gr-ppp193.trito 449324 0 429181 0 0 tun0 1500 gr-ppp212.tri gr-ppp212.trito 449324 0 429181 0 0 tun0 1500 gr-ppp217.tri gr-ppp217.trito 449324 0 429181 0 0 tun0 1500 gr-ppp13.trit gr-ppp13.triton 449324 0 429181 0 0 tun0 1500 gr-ppp22.trit gr-ppp22.triton 449324 0 429181 0 0 tun0 1500 gr-ppp35.trit gr-ppp35.triton 449324 0 429181 0 0 tun0 1500 gr-ppp52.trit gr-ppp52.triton 449324 0 429181 0 0 tun0 1500 gr-ppp94.trit gr-ppp94.triton 449324 0 429181 0 0 tun0 1500 gr-ppp113.tri gr-ppp113.trito 449324 0 429181 0 0 tun0 1500 gr-ppp137.tri gr-ppp137.trito 449324 0 429181 0 0 tun0 1500 gr-ppp162.tri gr-ppp162.trito 449324 0 429181 0 0 tun0 1500 gr-ppp98.trit gr-ppp98.triton 449324 0 429181 0 0 tun0 1500 gr-ppp138.tri gr-ppp138.trito 449324 0 429181 0 0 tun0 1500 gr-ppp24.trit gr-ppp24.triton 449324 0 429181 0 0 tun0 1500 gr-ppp192.tri gr-ppp192.trito 449324 0 429181 0 0 tun0 1500 gr-ppp41.trit gr-ppp41.triton 449324 0 429181 0 0 tun0 1500 gr-ppp17.trit gr-ppp17.triton 449324 0 429181 0 0 tun0 1500 gr-ppp200.tri gr-ppp200.trito 449324 0 429181 0 0 tun0 1500 gr-ppp142.tri gr-ppp142.trito 449324 0 429181 0 0 tun0 1500 gr-ppp158.tri gr-ppp158.trito 449324 0 429181 0 0 tun0 1500 gr-ppp46.trit gr-ppp46.triton 449324 0 429181 0 0 tun0 1500 gr-ppp154.tri gr-ppp154.trito 449324 0 429181 0 0 tun0 1500 gr-ppp51.trit gr-ppp51.triton 449324 0 429181 0 0 tun0 1500 gr-ppp183.tri gr-ppp183.trito 449324 0 429181 0 0 tun0 1500 gr-ppp72.trit gr-ppp72.triton 449324 0 429181 0 0 tun0 1500 gr-ppp164.tri gr-ppp164.trito 449324 0 429181 0 0 tun0 1500 gr-ppp82.trit gr-ppp82.triton 449324 0 429181 0 0 tun0 1500 gr-ppp184.tri gr-ppp184.trito 449324 0 429181 0 0 tun0 1500 gr-ppp66.trit gr-ppp66.triton 449324 0 429181 0 0 tun0 1500 gr-ppp198.tri gr-ppp198.trito 449324 0 429181 0 0 tun0 1500 gr-ppp86.trit gr-ppp86.triton 449324 0 429181 0 0 tun0 1500 gr-ppp213.tri gr-ppp213.trito 449324 0 429181 0 0 tun0 1500 gr-ppp102.tri gr-ppp102.trito 449324 0 429181 0 0 tun0 1500 gr-ppp23.trit gr-ppp23.triton 449324 0 429181 0 0 tun0 1500 gr-ppp104.tri gr-ppp104.trito 449324 0 429181 0 0 tun0 1500 gr-ppp173.tri gr-ppp173.trito 449324 0 429181 0 0 tun0 1500 gr-ppp5.trito gr-ppp5.triton. 449324 0 429181 0 0 tun0 1500 gr-ppp58.trit gr-ppp58.triton 449324 0 429181 0 0 tun0 1500 gr-ppp111.tri gr-ppp111.trito 449324 0 429181 0 0 tun0 1500 gr-ppp136.tri gr-ppp136.trito 449324 0 429181 0 0 tun0 1500 triton.net gr-ppp150.trito 449324 0 429181 0 0 sl0* 552 0 0 0 0 0 ppp0* 1500 0 0 0 0 0 lo0 16384 1225 0 1225 0 0 lo0 16384 127 localhost 1225 0 1225 0 0 And my ppp.conf file: default: # # Make sure that "device" references the correct serial port # for your modem. (cuaa0 = COM1, cuaa1 = COM2) # set device /dev/cuaa0 set log Phase Chat LCP IPCP CCP tun command set speed 115200 set dial "ABORT BUSY ABORT NO\\sCARRIER TIMEOUT 5 \"\" AT OK-AT-OK \\dATDT\\T TIMEOUT 40 CONNECT" set timeout 0 set ifaddr 10.0.0.1/0 10.0.0.2/0 255.255.255.0 0.0.0.0 add default HISADDR enable dns papchap: set phone xxxxxxx set authname xxxxxx set authkey xxxxxx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 19:11:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relax.dreamfire.net (relax.dreamfire.net [207.113.154.29]) by hub.freebsd.org (Postfix) with ESMTP id 20E8314D57 for ; Wed, 8 Dec 1999 19:11:35 -0800 (PST) (envelope-from sean@dreamfire.net) Received: from dreamfire.net (indigo.dreamfire.net [192.168.10.8]) by relax.dreamfire.net (Postfix) with ESMTP id 2ADE374 for ; Wed, 8 Dec 1999 19:11:28 -0800 (PST) Message-ID: <384F1E08.F88A4528@dreamfire.net> Date: Wed, 08 Dec 1999 19:12:08 -0800 From: Sean-Paul Rees Organization: The Dreamfire Solutions Group X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: MFS Speed 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 a MFS mounted at /tmp, at 32MB. Is it really faster than regular disks? I haven't really seen any improvement, and I'm not sure if I am doing it right. In /etc/fstab, I have: /dev/da1s1f none swap sw 0 0 /dev/da1s1f /tmp mfs rw,nosuid,nodev,noatime,async 0 0 /dev/da1s1f is a 32MB disklabel on a 9.1GB UltraWide (40MB/sec) drive. Cheers, Sean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 19:29: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191]) by hub.freebsd.org (Postfix) with ESMTP id A56031526E; Wed, 8 Dec 1999 19:28:52 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id XAA10564; Wed, 8 Dec 1999 23:28:51 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 8 Dec 1999 23:28:51 -0400 (AST) From: The Hermit Hacker To: freebsd-scsi@freebsd.org Cc: mackley@tht.net, freebsd-stable@freebsd.org Subject: SCSI problem ... OS or just bus? 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 did two upgrades in the course of a few days...upgraded my 3.3-STABLE to a more recent version, and added hard drives onto the system...now I'm getting SCSI problems that make no sense :( The machine just hung once more, which its doing every few hours...I can get down to the debugger, but a 'trace' doesn't appear to show anyting, so I panic... ========== (da4:ahc0:0:8:0): Other SCB Timeout (da4:ahc0:0:8:0): SCB 0xeb - timed out in dataout phase, SEQADDR == 0x10f (da4:ahc0:0:8:0): Other SCB Timeout (da2:ahc0:0:5:0): SCB 0x24 - timed out in dataout phase, SEQADDR == 0x10f (da2:ahc0:0:5:0): BDR message in message buffer (da2:ahc0:0:5:0): SCB 0x92 - timed out in dataout phase, SEQADDR == 0x10f (da2:ahc0:0:5:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 98 SCBs aborted ^C^C^CStopped at siointr1+0xc5: jmp siointr1+0x1c9 db> where No such command db> list No such command db> ? Bad character ? db> help print p examine x search set write w delete d break dwatch watch step s continue c until next match trace call show ps gdb panic db> trace siointr1(c225d000,0,c021dc47,0,d6030010) at siointr1+0xc5 siointr(0,d6030010,77,d6034000,0) at siointr+0x13 Xfastintr4() at Xfastintr4+0x17 db> continue ^C^CStopped at siointr1+0xc5: jmp siointr1+0x1c9 db> trace siointr1(c225d000,0,c021dc47,0,d6030010) at siointr1+0xc5 siointr(0,d6030010,65,d6031000,0) at siointr+0x13 Xfastintr4() at Xfastintr4+0x17 db> panic panic: from debugger syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01ec14c stack pointer = 0x10:0xc025a5fc frame pointer = 0x10:0xc025a600 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault (da0:ahc0:0:0:0): Synchronize cache failed, status == 0xb, scsi status == 0x0 ====== I'm going to upgrade to the newest kernel, but none of the recent commit messages *sound* like they are applicable... A dmesg of the machine looks like, just in case either anything about the controller/drives pops out at anyone? ====== Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-STABLE #0: Wed Dec 1 09:53:53 EST 1999 root@hub.org:/usr/src/sys/compile/hub_org Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 501139140 Hz CPU: Pentium III (501.14-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x673 Stepping = 3 Features=0x387f9ff,MMX,FXSR,> real memory = 805306368 (786432K bytes) avail memory = 780460032 (762168K bytes) Preloaded elf kernel "kernel" at 0xc02df000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x02 on pci0.4.3 ahc0: rev 0x01 int a irq 14 on pci0.9.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x01 int a irq 15 on pci0.10.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs xl0: <3Com 3c905-TX Fast Etherlink XL> rev 0x00 int a irq 12 on pci0.11.0 xl0: Ethernet address: 00:60:08:c8:36:05 xl0: autoneg complete, link status good (half-duplex, 10Mbps) xl1: <3Com 3c905-TX Fast Etherlink XL> rev 0x00 int a irq 10 on pci0.12.0 xl1: Ethernet address: 00:60:97:d0:3c:f5 xl1: autoneg complete, link status good (half-duplex, 10Mbps) Probing for devices on PCI bus 1: vga0: rev 0x01 int a irq 10 on pci1.0.0 Probing for PnP devices: CSN 1 Vendor ID: UMC9008 [0x0890a355] Serial 0xab8d1af0 Comp ID: PNP80d6 [0xd680d041] ed1: address 00:c0:f0:1a:8d:ab, type NE2000 (16 bit) ed1 (edpnp sn 0xab8d1af0) at 0x220-0x23f irq 11 on isa Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <4 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface IP packet filtering initialized, divert enabled, rule-based forwarding disabled, default to accept, logging limited to 100 packets/entry by default Waiting 2 seconds for SCSI devices to settle cda2 at ahc0 bus 0 target 5 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da3 at ahc0 bus 0 target 6 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4350MB (8910423 512 byte sectors: 255H 63S/T 554C) da4 at ahc0 bus 0 target 8 lun 0 da4: Fixed Direct Access SCSI-3 device da4: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4095MB (8386733 512 byte sectors: 255H 63S/T 522C) da8 at ahc0 bus 0 target 12 lun 0 da8: Fixed Direct Access SCSI-3 device da8: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da8: 17366MB (35566000 512 byte sectors: 255H 63S/T 2213C) da5 at ahc0 bus 0 target 9 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da5: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da7 at ahc0 bus 0 target 11 lun 0 da7: Fixed Direct Access SCSI-2 device da7: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da7: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) da6 at ahc0 bus 0 target 10 lun 0 da6: Fixed Direct Access SCSI-2 device da6: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da6: 17366MB (35566480 512 byte sectors: 255H 63S/T 2213C) hanging root device to da0s1a WARNING: / was not properly dismounted ======= The QUANTUMs above have been in the machine for >1yr now and have worked, from what I can tell, without a hitch...its only since we added da4+ that we've seeing the problems...interaction problem between drive manufacturers? I seem to recall this sort of thing being a problem on older drives, but.. Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.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 8 19:42: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id D298115552; Wed, 8 Dec 1999 19:41:53 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA36152; Wed, 8 Dec 1999 20:41:41 -0700 (MST) (envelope-from ken) Message-Id: <199912090341.UAA36152@panzer.kdm.org> Subject: Re: SCSI problem ... OS or just bus? In-Reply-To: from The Hermit Hacker at "Dec 8, 1999 11:28:51 pm" To: scrappy@hub.org (The Hermit Hacker) Date: Wed, 8 Dec 1999 20:41:41 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, mackley@tht.net, freebsd-stable@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote... > > I recently did two upgrades in the course of a few days...upgraded my > 3.3-STABLE to a more recent version, and added hard drives onto the > system...now I'm getting SCSI problems that make no sense :( > > The machine just hung once more, which its doing every few hours...I can > get down to the debugger, but a 'trace' doesn't appear to show anyting, so > I panic... > > ========== > (da4:ahc0:0:8:0): Other SCB Timeout > (da4:ahc0:0:8:0): SCB 0xeb - timed out in dataout phase, SEQADDR == 0x10f > (da4:ahc0:0:8:0): Other SCB Timeout > (da2:ahc0:0:5:0): SCB 0x24 - timed out in dataout phase, SEQADDR == 0x10f > (da2:ahc0:0:5:0): BDR message in message buffer > (da2:ahc0:0:5:0): SCB 0x92 - timed out in dataout phase, SEQADDR == 0x10f > (da2:ahc0:0:5:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 98 SCBs aborted [ ... ] > The QUANTUMs above have been in the machine for >1yr now and have worked, > from what I can tell, without a hitch...its only since we added da4+ that > we've seeing the problems...interaction problem between drive > manufacturers? I seem to recall this sort of thing being a problem on > older drives, but.. You have a cabling or termination problem. Ken -- Kenneth Merry ken@kdm.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 8 19:49:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 26DFB155B3 for ; Wed, 8 Dec 1999 19:49:31 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 11vua3-000Nvt-00; Wed, 08 Dec 1999 19:49:23 -0800 Date: Wed, 8 Dec 1999 19:49:18 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Sean-Paul Rees Cc: stable@freebsd.org Subject: Re: MFS Speed In-Reply-To: <384F1E08.F88A4528@dreamfire.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 Wed, 8 Dec 1999, Sean-Paul Rees wrote: > I have a MFS mounted at /tmp, at 32MB. Is it really faster than regular > disks? I haven't really seen any improvement, and I'm not sure if I am > doing it right. > > In /etc/fstab, I have: > /dev/da1s1f none swap sw 0 0 > /dev/da1s1f /tmp mfs rw,nosuid,nodev,noatime,async 0 0 > > /dev/da1s1f is a 32MB disklabel on a 9.1GB UltraWide (40MB/sec) drive. Well, if you don't have extra RAM, mfs will no faster than regular disk, because it will be regular disk. > Cheers, > Sean 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 8 20: 1:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fastlane.net (fastlane.net [209.197.224.10]) by hub.freebsd.org (Postfix) with ESMTP id C324714BC6 for ; Wed, 8 Dec 1999 20:01:52 -0800 (PST) (envelope-from def@fastlane.net) Received: from myname.my.domain (ftworth.tx.tnt1.130.fastlane.net [209.197.193.130]) by fastlane.net (8.9.3/8.9.3) with SMTP id WAA03995; Wed, 8 Dec 1999 22:01:26 -0600 (CST) Message-ID: <384F1CA3.41C67EA6@fastlane.net> Date: Wed, 08 Dec 1999 21:06:11 -0600 From: DuckMan X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 3.2-RELEASE i386) MIME-Version: 1.0 To: FreeBSD-stable@FreeBSD.ORG Subject: subscribe Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe -- "Whatthehellareyoustarin'at?" DuckMan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 20:26:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from set.spradley.org (set.spradley.tmi.net [207.170.107.99]) by hub.freebsd.org (Postfix) with ESMTP id 9F07214BFE; Wed, 8 Dec 1999 20:26:10 -0800 (PST) (envelope-from tsprad@set.spradley.org) Received: from set.spradley.org (localhost.spradley.tmi.net [127.0.0.1]) by set.spradley.org (8.9.3/8.9.2) with ESMTP id WAA33754; Wed, 8 Dec 1999 22:26:04 -0600 (CST) (envelope-from tsprad@set.spradley.org) Message-Id: <199912090426.WAA33754@set.spradley.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: stable@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Route table leaks In-reply-to: Your message of "Wed, 08 Dec 1999 23:48:45 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Dec 1999 22:26:03 -0600 From: Ted Spradley Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Please use 'netstat -rna' to get a listing of *all* the routes, including > > > the temporary ones, not just the non-temporary routes. FWIW, another datapoint: set$ netstat -ran | wc -l 15 set$ vmstat -m | grep routetbl|grep K routetbl 35 5K 18K 26535K 511 0 0 16,32,64,128,256 set$ uname -a FreeBSD set.spradley.org 3.3-STABLE FreeBSD 3.3-STABLE #2: Wed Oct 6 19:10:52 CDT 1999 tsprad@set.spradley.tmi.net:/scratch/source/src/sys/ compile/Set i386 set$ uptime 10:21PM up 9 days, 3:24, 0 users, load averages: 0.05, 0.11, 0.06 This is my desktop at home, used for reading mail and surfing the web, no routed or gated, mostly idle. 26.5 Mbytes looks kinda high to me... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 20:59: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relax.dreamfire.net (relax.dreamfire.net [207.113.154.29]) by hub.freebsd.org (Postfix) with ESMTP id D73F2152DA for ; Wed, 8 Dec 1999 20:58:54 -0800 (PST) (envelope-from sean@dreamfire.net) Received: from dreamfire.net (indigo.dreamfire.net [192.168.10.8]) by relax.dreamfire.net (Postfix) with ESMTP id 86A89110 for ; Wed, 8 Dec 1999 20:58:50 -0800 (PST) Message-ID: <384F3735.F1109EB4@dreamfire.net> Date: Wed, 08 Dec 1999 20:59:33 -0800 From: Sean-Paul Rees Organization: The Dreamfire Solutions Group X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: MFS Speed References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Tom wrote: > Well, if you don't have extra RAM, mfs will no faster than regular disk, > because it will be regular disk. I do have the extra RAM. I wrote roughly 30M of /dev/urandom into a file on /tmp, I immediately saw another 30M of ram in use. Cheers, Sean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 20:59:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id B1A301559F; Wed, 8 Dec 1999 20:58:52 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id UAA01426; Wed, 8 Dec 1999 20:58:28 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912090458.UAA01426@gndrsh.dnsmgr.net> Subject: Re: Route table leaks In-Reply-To: <199912090426.WAA33754@set.spradley.org> from Ted Spradley at "Dec 8, 1999 10:26:03 pm" To: tsprad@set.spradley.org (Ted Spradley) Date: Wed, 8 Dec 1999 20:58:28 -0800 (PST) Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > > Please use 'netstat -rna' to get a listing of *all* the routes, including > > > > the temporary ones, not just the non-temporary routes. > > FWIW, another datapoint: > > set$ netstat -ran | wc -l > 15 > set$ vmstat -m | grep routetbl|grep K Type InUse MemUse HighUse Limit Requests Limit Limit Size(s) > routetbl 35 5K 18K 26535K 511 0 0 > 16,32,64,128,256 > set$ uname -a > FreeBSD set.spradley.org 3.3-STABLE FreeBSD 3.3-STABLE #2: Wed Oct 6 > 19:10:52 CDT 1999 tsprad@set.spradley.tmi.net:/scratch/source/src/sys/ > compile/Set i386 > set$ uptime > 10:21PM up 9 days, 3:24, 0 users, load averages: 0.05, 0.11, 0.06 > > > This is my desktop at home, used for reading mail and surfing the web, > no routed or gated, mostly idle. 26.5 Mbytes looks kinda high to me... Go back and read the headings of vmstat -m, your only using 5K for routes, the 26.5M is the limit on the vmspace. The 18K was the highest usage. So you look pretty normal at 5K/35 -> 146 bytes/route. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 21:13:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 2C5171556D; Wed, 8 Dec 1999 21:12:59 -0800 (PST) (envelope-from igiveup@ix.netcom.com) Received: from ix.netcom.com (user-2ini8pe.dialup.mindspring.com [165.121.35.46]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id AAA28198; Thu, 9 Dec 1999 00:12:51 -0500 (EST) Message-ID: <384F3A52.23868C19@ix.netcom.com> Date: Wed, 08 Dec 1999 21:12:50 -0800 From: Ben Speirs X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: The Hermit Hacker Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: SCSI problem ... OS or just bus? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The Hermit Hacker wrote: > > I recently did two upgrades in the course of a few days...upgraded my > 3.3-STABLE to a more recent version, and added hard drives onto the > system...now I'm getting SCSI problems that make no sense :( > > The machine just hung once more, which its doing every few hours...I can > get down to the debugger, but a 'trace' doesn't appear to show anyting, so > I panic... > > ========== > (da4:ahc0:0:8:0): Other SCB Timeout > (da4:ahc0:0:8:0): SCB 0xeb - timed out in dataout phase, SEQADDR == 0x10f > (da4:ahc0:0:8:0): Other SCB Timeout > (da2:ahc0:0:5:0): SCB 0x24 - timed out in dataout phase, SEQADDR == 0x10f > (da2:ahc0:0:5:0): BDR message in message buffer > (da2:ahc0:0:5:0): SCB 0x92 - timed out in dataout phase, SEQADDR == 0x10f > (da2:ahc0:0:5:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 98 SCBs aborted Just another data point - A similar thing happened to me. I rebuilt the kernel and world back in September and my previously happy SCSI system started issuing the same type of messages. I saved the output of the system log. Portions of it are listed below: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.3-STABLE #3: Fri Sep 24 21:00:39 PDT 1999 root@sloth:/usr/src/sys/compile/SLOTH [...trim...] ahc0: rev 0x00 int a irq 9 on pci0.9.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs [...trim...] Waiting 8 seconds for SCSI devices to settle changing root device to da0s3a da0 at ahc0 bus 0 target 15 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4149MB (8498506 512 byte sectors: 255H 63S/T 529C) cd0 at ahc0 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 3.300MB/s transfers cd1: Attempt to query device size failed: NOT READY, Medium not present Unexpected busfree. LASTPHASE == 0x1 SEQADDR == 0x153 ahc0:A:0: no active SCB for reconnecting target - issuing BUS DEVICE RESET SAVED_TCL == 0x0, ARG_1 == 0xff, SEQ_FLAGS == 0x0 (cd0:ahc0:0:0:0): SCB 0x16 - timed out in datain phase, SEQADDR == 0x153 (cd0:ahc0:0:0:0): Other SCB Timeout (da0:ahc0:0:15:0): SCB 0x3 - timed out in datain phase, SEQADDR == 0x153 (da0:ahc0:0:15:0): BDR message in message buffer (da0:ahc0:0:15:0): SCB 0x3 - timed out in datain phase, SEQADDR == 0x153 (da0:ahc0:0:15:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted fd0c: hard error reading fsbn 0 (No status) The problem occurred while accessing the da0 device and cd0 device at the same time. I could reproduce it at will, and almost instantly by copying a file from the CD-ROM to the hard drive. I could not reproduce the error with the older, slower NEC cd1 CD-ROM device. I rechecked all my termination and unplugged one device after another without any success. My guess was that the cd0 drive had gone goofy on me. The only thing I have not tried is replacing the cables. Since I had the other CD available my fix was to yank out the suspect device. It has been near the bottom of my 'things to do' list. Maybe we both got bit by the same "fix" that uncovered hidden hardware problems. Maybe not, it looks like you have problems with only Wide channel devices. -- -Ben Speirs To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 8 23:45:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [36.118.0.70]) by hub.freebsd.org (Postfix) with ESMTP id 29508155B4; Wed, 8 Dec 1999 23:45:32 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id XAA19457; Wed, 8 Dec 1999 23:43:34 -0800 (PST) Date: Wed, 8 Dec 1999 23:43:34 -0800 (PST) From: Bob Vaughan Message-Id: <199912090743.XAA19457@tantivy.stanford.edu> To: freebsd@gndrsh.dnsmgr.net, mike@sentex.net Subject: Re: Route table leaks Cc: current@FreeBSD.ORG, jdp@polstra.com, jgreco@ns.sol.net, stable@FreeBSD.ORG In-Reply-To: <199912081935.LAA98324@gndrsh.dnsmgr.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG here's mine.. this is from a single homed machine, with a default route. it's also a IRC server (irc.stanford.edu), with a LOT of filtering of inbound traffic. FreeBSD 3.3-STABLE #8: Sat Nov 27 17:15:49 PST 1999 11:33PM up 2 days, 20:41, 1 user, load averages: 0.03, 0.03, 0.00 routetbl 205 29K 10489K 10489K 3479960 0 0 16,32,64,128,256 note that the table maxed out at some point (during a DoS attack.) root-irc.stanford.edu-[11:34pm-52]#t> netstat -ran | wc 70 409 4741 looks like it leaked 135 in 2.8 days.. -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 9792, Stanford, Ca 94309-9792 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 1: 6:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from oxmail.ox.ac.uk (oxmail4.ox.ac.uk [163.1.2.33]) by hub.freebsd.org (Postfix) with ESMTP id 7C4691557D for ; Thu, 9 Dec 1999 01:06:21 -0800 (PST) (envelope-from roger.crawford@queen-elizabeth-house.oxford.ac.uk) Received: from wing1.herald.ox.ac.uk ([163.1.0.225] ident=exim) by oxmail.ox.ac.uk with esmtp (Exim 2.10 #1) id 11vzWm-0000dN-00 for FreeBSD-stable@freebsd.org; Thu, 9 Dec 1999 09:06:20 +0000 Received: from httpd by wing1.herald.ox.ac.uk with local (Exim 2.02 #1) id 11vzWm-0004Nq-00 for FreeBSD-stable@freebsd.org; Thu, 9 Dec 1999 09:06:20 +0000 Content-Type: text/plain Content-Disposition: inline Mime-Version: 1.0 X-Mailer: MIME-tools 4.103 (Entity 4.115) From: Roger Crawford To: FreeBSD-stable@freebsd.org Subject: Failed buildworld Message-Id: Date: Thu, 9 Dec 1999 09:06:20 +0000 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am running FreeBSD 3.3-STABLE. I CVSUPed yesterday and did make buildworld which terminated as follows. (If it would help you to have the entire record I can send the complete script.) Suggestions much appreciated [cut]----- cc -nostdinc -O -pipe -funsigned-char -I/usr/src/gnu/usr.bin/diff/../../../contrib/diff -DHAVE_CONF\ IG_H -DPR_PROGRAM=\"/usr/bin/pr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/diff\ /../../../contrib/diff/version.c^M cc -nostdinc -O -pipe -funsigned-char -I/usr/src/gnu/usr.bin/diff/../../../contrib/diff -DHAVE_CONF\ IG_H -DPR_PROGRAM=\"/usr/bin/pr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/diff\ /../../../contrib/diff/getopt.c^M cc -nostdinc -O -pipe -funsigned-char -I/usr/src/gnu/usr.bin/diff/../../../contrib/diff -DHAVE_CONF\ IG_H -DPR_PROGRAM=\"/usr/bin/pr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/diff\ /../../../contrib/diff/getopt1.c^M cc -nostdinc -O -pipe -funsigned-char -I/usr/src/gnu/usr.bin/diff/../../../contrib/diff -DHAVE_CONF\ IG_H -DPR_PROGRAM=\"/usr/bin/pr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/diff\ /../../../contrib/diff/side.c^M cc -nostdinc -O -pipe -funsigned-char -I/usr/src/gnu/usr.bin/diff/../../../contrib/diff -DHAVE_CONF\ IG_H -DPR_PROGRAM=\"/usr/bin/pr\" -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/gnu/usr.bin/diff\ /../../../contrib/diff/cmpbuf.c^M cc -nostdinc -O -pipe -funsigned-char -I/usr/src/gnu/usr.bin/diff/../../../contrib/diff -DHAVE_CONF\ IG_H -DPR_PROGRAM=\"/usr/bin/pr\" -I/usr/obj/usr/src/tmp/usr/include -o diff diff.o analyze.o io\ .o context.o ed.o normal.o ifdef.o util.o dir.o version.o getopt.o getopt1.o side.o cmpbuf.o -lgnu\ regex^M diff.o: In function `main':^M diff.o(.text+0x293): undefined reference to `prepend_default_options'^M *** Error code 1^M ^M Stop.^M *** Error code 1^M ^M Stop.^M *** Error code 1^M ^M Stop.^M *** Error code 1^M ^M Stop.^M -- Roger Crawford Queen Elizabeth House roger.crawford@qeh.ox.ac.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 1:17: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from io.freibergnet.de (io.freibergnet.de [194.123.255.3]) by hub.freebsd.org (Postfix) with ESMTP id 171C115344 for ; Thu, 9 Dec 1999 01:16:33 -0800 (PST) (envelope-from mw@io.freibergnet.de) Received: (from mw@localhost) by io.freibergnet.de (8.9.3/8.9.1) id KAA58717; Thu, 9 Dec 1999 10:15:40 +0100 (CET) (envelope-from mw) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <384ED624.5EA4E41D@nisser.com> Date: Thu, 09 Dec 1999 10:15:40 +0100 (CET) Reply-To: mw@freibergnet.de Organization: FreibergNet Systemhaus / Liebscher & Partner From: Martin Welk To: Roelof Osinga Subject: Re: ifpw forwarding problem Cc: FreeBSD Stable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-99 Roelof Osinga wrote: () Thanks. I did do that, but for testing purposes I tried to redirect it () through the other NIC as well. The natd has been told to listen only () on the ep1 NIC. As I understood it, you tell natd the interface it's going to work on for the purpose that it get's is (probably dynamic) IP address from this interface (the IP address it should use for translated packets). You still have to pass the packets from the IP firewall to natd by divert rules in the firewall ruleset. () > use_sockets () > same_ports () > port 8668 () > deny_incoming no () > alias_address aaa.aaa.aaa.aaa () > redirect_port tcp bbb.bbb.bbb.bbb:5900 aaa.aaa.aaa.aaa:5900 () () Second thing I tried, but with the difference that I rely () on "deny incoming no" to be the default. Take care at the spelling. I'm not sure about how tolerant natd is in reading the options from a config file, they are slightly different. My example is correct and the option is really called "deny_incoming" (with the value "no"). () In my case though I would probably should be using proxy_rule with () type encode_ip_hdr since it's intended for webtraffic. It would be () nice to know where the hits are coming from. You need this if you are going to setup rules for a transparent proxy, but with redirect_address the packet should arrive with the original address at the host in the internal network. () Funny in that I did try with () () nisser:/home/www/Slak$ cat /etc/natd.conf () # as used in rc.conf.local () -use_sockets () -same_ports () #-redirect_port tcp 212.187.0.39:8080 10.0.0.3:80 Write it as use_sockets yes same_ports redirect_port ... () redirection enabled. It didn't work when accessing that IP address () from within. Which is why I tried the internal NIC. Argh! You're right, from the internal network I can't access the host with it's external address. The same bug here! (This machines offers some web services and FTP via NATD to the outside and obviously nobody tried to use these services from our internal network :-) ) () Alas it did not work in my case. However, that was with () IPFIREWALL_FORWARD () enabled. Turned out that made my system quit unstable, or rather () erratic. Woah! Never really experienced such trouble. options IPFIREWALL IPFIREWALL_DEFAULT_TO_ACCEPT * IPFIREWALL_FORWARD * IPFIREWALL_VERBOSE "IPFIREWALL_VERBOSE_LIMIT=100" IPDIVERT "ICMP_BANDLIM" DUMMYNET * All except those marked with * are running on our primary server that doesn NAT for the internal network, the others are in my desktop machine's kernel. Both run rock-stable with 3.3-STABLE. Did you include IPDIVERT? () Which reminds me, do you happen to know if natd responds to HUP? The () manpage doesn't mention it. No, it doesn't. I usually kill it before (re-) starting it. If this behaviour has changed, I haven't noticed. (I made the experience that in some circumstances starting a new natd after killing the older one something didn't work properly anymore, especially on a machine here with six Ethernet interfaces and three natd's running parallel. I had to reboot it after doing very heavy changes :-) ) () Anyway, since my rules mimick your (barring the "deny_incoming no") and () yours do work, I know at least it's not the rules. The natd rules, that () is. I'll try with the kernel as is at the next opportunity. Which version of FreeBSD are you running? Regards, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 2:51:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.powertech.no (intentia.powertech.no [195.159.0.220]) by hub.freebsd.org (Postfix) with ESMTP id 19C4F155C4; Thu, 9 Dec 1999 02:51:51 -0800 (PST) (envelope-from shamz@login2.powertech.no) Received: from login2.powertech.no (IDENT:root@login2.powertech.no [195.159.0.152]) by mail.powertech.no (8.9.3/8.8.5) with ESMTP id LAA20855; Thu, 9 Dec 1999 11:51:11 +0100 Received: (from shamz@localhost) by login2.powertech.no (8.9.3/8.9.3) id LAA11857; Thu, 9 Dec 1999 11:51:48 +0100 Date: Thu, 9 Dec 1999 11:51:48 +0100 From: Shaun Jurrens To: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: SCSI problem ... OS or just bus? Message-ID: <19991209115148.A10267@shamz.net> Mail-Followup-To: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, Sorry if this breaks the thread, because it is a little cut and paste from the html version. I also have had numerous problems with my wide drives. I have even updated the firmware and thought things were better, but last week a cvsup brought a screen full of scb timeouts. The termination is correct. The cables are ok. The firmware is updated. The version running is 3.3-Stable #0 or #1 (don't have the box in front of me). The logs are the same as everyone elses. The drives are two Quantum WideSCSI drives in sizes of ca. 1.0 and 4.3 GB. The controller is a pci card Adaptec 2940W. I would love to just change the hardware, but as I see IBM drives often have the same problem and I don't have $300 to spare right now, I am hoping the bug will be found before I fsck myself silly. The drives have caused a couple of crashes and clobbered everthing from logs to src to my X-server binaries, so it is more than a nuisance. BTW, the drives have no new bad sectors either. Sorry for the terseness in respect to the logs, but the last 10 mails with the same logs haven't lead to a resolution. They can be provided, but don't seem to be being used. -- Yours truly, Shaun D. Jurrens shaun@shamz.net IRCnick: shamz #chillout #unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 3:22: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.powertech.no (intentia.powertech.no [195.159.0.220]) by hub.freebsd.org (Postfix) with ESMTP id 0E74514DE8; Thu, 9 Dec 1999 03:21:58 -0800 (PST) (envelope-from shamz@login2.powertech.no) Received: from login2.powertech.no (IDENT:root@login2.powertech.no [195.159.0.152]) by mail.powertech.no (8.9.3/8.8.5) with ESMTP id MAA26361; Thu, 9 Dec 1999 12:21:19 +0100 Received: (from shamz@localhost) by login2.powertech.no (8.9.3/8.9.3) id MAA14172; Thu, 9 Dec 1999 12:21:56 +0100 Date: Thu, 9 Dec 1999 12:21:55 +0100 From: Shaun Jurrens To: Harlan Stenn Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: SCSI problem ... OS or just bus? Message-ID: <19991209122155.B10267@shamz.net> Mail-Followup-To: Harlan Stenn , freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org References: <19991209115148.A10267@shamz.net> <707.944736910@brown.pfcs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us In-Reply-To: <707.944736910@brown.pfcs.com>; from Harlan Stenn on Thu, Dec 09, 1999 at 05:55:10AM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 05:55:10AM -0500, Harlan Stenn wrote: #> Is the SCSI chain too long? #> #> H There are only three drives internally with extra cooling on the flat band cable connected to the wide bus. The cable is ca. 30cm long. AFAIK, the scsi wide bus will work up to 1.3m, or maybe it was 3m, in any case the cable isn't too long. It all worked perfectly up until about the end of June, actually. The bugs seemed too random to put my finger on it, although I have really tried everything. I unfortunately don't have equipent to test what actually goes out from the bus or if everything there is ok, electronically speaking. I know the drives work reliably with winbloze (or at least did, since I don't use it very often anymore). -- Yours truly, Shaun D. Jurrens shaun@shamz.net IRCnick: shamz #chillout #unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 5:12:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from m0.cs.berkeley.edu (m0.CS.Berkeley.EDU [128.32.45.176]) by hub.freebsd.org (Postfix) with ESMTP id 1167214DE8 for ; Thu, 9 Dec 1999 05:12:14 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca36-25.ix.netcom.com [207.92.172.25]) by m0.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id FAA12182; Thu, 9 Dec 1999 05:11:53 -0800 (PST) (envelope-from asami@stampede.cs.berkeley.edu) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.9.3/8.6.9) id FAA07900; Thu, 9 Dec 1999 05:10:54 -0800 (PST) To: Roger Crawford Cc: FreeBSD-stable@freebsd.org Subject: Re: Failed buildworld References: From: asami@freebsd.org (Satoshi - Ports Wraith - Asami) Date: 09 Dec 1999 05:10:49 -0800 In-Reply-To: Roger Crawford's message of "Thu, 9 Dec 1999 09:06:20 +0000" Message-ID: Lines: 16 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Roger Crawford * I am running FreeBSD 3.3-STABLE. I CVSUPed yesterday and did make buildworld * which terminated as follows. (If it would help you to have the entire record * I can send the complete script.) Suggestions much appreciated * cc -nostdinc -O -pipe -funsigned-char -I/usr/src/gnu/usr.bin/diff/../../../contrib/diff -DHAVE_CONFIG_H -DPR_PROGRAM=\"/usr/bin/pr\" -I/usr/obj/usr/src/tmp/usr/include -o diff diff.o analyze.o io.o context.o ed.o normal.o ifdef.o util.o dir.o version.o getopt.o getopt1.o side.o cmpbuf.o -lgnuregex * diff.o: In function `main': * diff.o(.text+0x293): undefined reference to `prepend_default_options' * *** Error code 1 * * Stop. I saw this one too. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 5:35:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.vitts.com (mail.vitts.com [216.64.31.74]) by hub.freebsd.org (Postfix) with ESMTP id C154515359 for ; Thu, 9 Dec 1999 05:35:44 -0800 (PST) (envelope-from michaelremski@ellacoya.com) Received: from ellacoya.com ([216.64.109.139]) by mail.vitts.com (InterMail v4.01.00 201-232-112) with ESMTP id <19991209133703.HIII6347.mail.vitts.com@ellacoya.com> for ; Thu, 9 Dec 1999 08:37:03 -0500 Message-ID: <384FB021.1BBAA035@ellacoya.com> Date: Thu, 09 Dec 1999 08:35:29 -0500 From: Michael Remski X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.2.13-7mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-Stable@freebsd.org Subject: Re: failed buildworld Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Roger Crawford * I am running FreeBSD 3.3-STABLE. I CVSUPed yesterday and did make buildworld * which terminated as follows. (If it would help you to have the entire record * I can send the complete script.) Suggestions much appreciated * cc -nostdinc -O -pipe -funsigned-char -I/usr/src/gnu/usr.bin/diff/../../../contrib/diff -DHAVE_CONFIG_H -DPR_PROGRAM=\"/usr/bin/pr\" -I/usr/obj/usr/src/tmp/usr/include -o diff diff.o analyze.o io.o context.o ed.o normal.o ifdef.o util.o dir.o version.o getopt.o getopt1.o side.o cmpbuf.o -lgnuregex * diff.o: In function `main': * diff.o(.text+0x293): undefined reference to `prepend_default_options' * *** Error code 1 Saw this too last night, but resupped from cvsup5 at about 4am EST and problem was fixed. m To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 6: 9:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 2A72615521; Thu, 9 Dec 1999 06:09:15 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from imap.gv.tsc.tdk.com (imap.gv.tsc.tdk.com [192.168.241.198]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id GAA20200; Thu, 9 Dec 1999 06:09:08 -0800 (PST) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by imap.gv.tsc.tdk.com (8.9.3/8.9.3) with ESMTP id GAA34058; Thu, 9 Dec 1999 06:09:07 -0800 (PST) (envelope-from Don.Lewis@tsc.tdk.com) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id GAA05595; Thu, 9 Dec 1999 06:09:07 -0800 (PST) From: Don Lewis Message-Id: <199912091409.GAA05595@salsa.gv.tsc.tdk.com> Date: Thu, 9 Dec 1999 06:09:06 -0800 In-Reply-To: Michael Remski "Re: failed buildworld" (Dec 9, 8:35am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Michael Remski , FreeBSD-Stable@FreeBSD.ORG, sheldonh@FreeBSD.ORG Subject: Re: failed buildworld Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Dec 9, 8:35am, Michael Remski wrote: } Subject: Re: failed buildworld } * From: Roger Crawford } } * diff.o(.text+0x293): undefined reference to `prepend_default_options' } * *** Error code 1 } } } Saw this too last night, but resupped from cvsup5 at about 4am EST and } problem was fixed. You just squeaked in under the wire. Stable was broken again just about that time by MFC to libc/stdtime/strptime.c: cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/lib/libc/../libc/stdtime/strptime.c -o strptime.o /usr/src/lib/libc/../libc/stdtime/strptime.c: In function `_strptime': /usr/src/lib/libc/../libc/stdtime/strptime.c:173: structure has no member named `Ef_fmt' /usr/src/lib/libc/../libc/stdtime/strptime.c:173: structure has no member named `EF_fmt' /usr/src/lib/libc/../libc/stdtime/strptime.c:414: structure has no member named `alt_month' /usr/src/lib/libc/../libc/stdtime/strptime.c:416: structure has no member named `alt_month' *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 6:28:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id D92EA14BFE for ; Thu, 9 Dec 1999 06:28:48 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11w4YV-000NNM-00; Thu, 09 Dec 1999 16:28:27 +0200 From: Sheldon Hearn To: Don Lewis Cc: Michael Remski , FreeBSD-Stable@FreeBSD.ORG Subject: Re: failed buildworld In-reply-to: Your message of "Thu, 09 Dec 1999 06:09:06 PST." <199912091409.GAA05595@salsa.gv.tsc.tdk.com> Date: Thu, 09 Dec 1999 16:28:27 +0200 Message-ID: <89859.944749707@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 09 Dec 1999 06:09:06 PST, Don Lewis wrote: > You just squeaked in under the wire. Stable was broken again just about > that time by MFC to libc/stdtime/strptime.c: Ugh! I could have been more stupid, but that would have required some serious effort. I've backed out the commit for now, because I have to go home. I'll do it properly tomorrow. Thanks, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 6:33:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from thoth.mch.sni.de (thoth.mch.sni.de [192.35.17.2]) by hub.freebsd.org (Postfix) with ESMTP id CFBC8155DA for ; Thu, 9 Dec 1999 06:33:41 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer thoth.mch.sni.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by thoth.mch.sni.de (8.9.3/8.9.3) with ESMTP id PAA09795 for ; Thu, 9 Dec 1999 15:33:22 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.9.3/8.9.3) with ESMTP id PAA00103 for ; Thu, 9 Dec 1999 15:33:21 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id PAA98462 for ; Thu, 9 Dec 1999 15:33:21 +0100 (CET) Date: Thu, 9 Dec 1999 15:33:20 +0100 From: Andre Albsmeier To: Alfred Perlstein Cc: Warner Losh , Garance A Drosihn , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Message-ID: <19991209153320.A62121@internal> References: <199912072106.OAA44391@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from bright@wintelcom.net on Tue, Dec 07, 1999 at 02:55:37PM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 07-Dec-1999 at 14:55:37 -0800, Alfred Perlstein wrote: I think the (really big) security hole can be closed by not doing the chown/chmod commands. I inserted them because I wanted the file in the spool directory to appear exactly as if lpr would have copied it. I am currently running the patch with the chown/chmod removed and lpd doesn't seem to have any problems with it. The side effect now is that the file in the spool directory keeps it's permissions. I don't think that this is a problem because if the file was set to 666 by the creator before, he doesn't care a lot about it anyway :-) What do people think about this? Alfred, Warner ? For better reference, here is the current patch: *** lpr.c.ORI Thu Dec 9 15:30:18 1999 --- lpr.c Thu Dec 9 15:30:35 1999 *************** *** 370,375 **** --- 370,405 ---- } if (sflag) printf("%s: %s: not linked, copying instead\n", name, arg); + /* + * If lpr was invoked with -r we try to move the file to + * be printed instead of copying and deleting it later. + * This works if the file and lpd's spool directory are + * on the same filesystem as it is often the case for files + * printed by samba or pcnfsd. In this case, a lot of I/O + * and temporary disk space can be avoided. Otherwise, we + * will continue normally. + */ + if (f) { /* file should be deleted */ + seteuid(euid); /* needed for rename() */ + if (!rename(arg, dfname)) { + int i; + #if 0 + chown(dfname, userid, getegid()); + chmod(dfname, S_IRUSR | S_IWUSR | + S_IRGRP | S_IWGRP); + #endif + seteuid(uid); /* restore old uid */ + if (format == 'p') + card('T', title ? title : arg); + for (i = 0; i < ncopies; i++) + card(format, &dfname[inchar-2]); + card('U', &dfname[inchar-2]); + card('N', arg); + nact++; + continue; + } + seteuid(uid); /* restore old uid */ + } if ((i = open(arg, O_RDONLY)) < 0) { printf("%s: cannot open %s\n", name, arg); } else { > On Tue, 7 Dec 1999, Warner Losh wrote: > > > I've been reviewing this patch with someone and I think the last > > version is ready to commit. I'll take a look at my tree to make > > sure. > > please do not, the patch in PR 11997 introduces a major security flaw. > > someone can hardlink to any file and clobber it with a file owned by > them: > > try this: > > as root: > > # cd /var/tmp ; touch rootfile ; chown root:wheel rootfile ; chmod 600 rootfile > > as a user: > > % cd /var/tmp ; echo foo > foo > % lpr -r foo > sleeping > > in another session as user: > > % rm foo ; ln rootfile foo > > wait a second... > > # ls -l rootfile > -rw-rw---- 3 user daemon 5 Dec 7 13:38 rootfile > # cat rootfile > foo > # > > ouch! > > -Alfred > > use this patch to make the race condition apparrent: > > > Index: usr.sbin/lpr/lpr/lpr.c > =================================================================== > RCS file: /home/ncvs/src/usr.sbin/lpr/lpr/lpr.c,v > retrieving revision 1.27.2.2 > diff -u -u -r1.27.2.2 lpr.c > --- lpr.c 1999/08/29 15:43:29 1.27.2.2 > +++ lpr.c 1999/12/08 01:47:47 > @@ -370,6 +370,27 @@ > } > if (sflag) > printf("%s: %s: not linked, copying instead\n", name, arg); > + if( f ) { /* means that the file should be deleted */ > + printf("sleeping\n"); > + sleep(5); > + printf("done.\n"); > + seteuid(euid); /* needed for rename() to succeed */ > + if( ! rename( arg, dfname ) ) { > + register int i; > + chmod( dfname, S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP ); > + chown( dfname, userid, getgrnam("daemon")->gr_gid ); > + seteuid(uid); > + if (format == 'p') > + card('T', title ? title : arg); > + for (i = 0; i < ncopies; i++) > + card(format, &dfname[inchar-2]); > + card('U', &dfname[inchar-2]); > + card('N', arg); > + nact++; > + continue; > + } > + seteuid(uid); > + } > if ((i = open(arg, O_RDONLY)) < 0) { > printf("%s: cannot open %s\n", name, arg); > } else { > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- "In a world without walls and fences, who needs windows and gates?" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 7:18:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from anarcat.dyndns.org (phobos.IRO.UMontreal.CA [132.204.20.20]) by hub.freebsd.org (Postfix) with ESMTP id E6FAC15623 for ; Thu, 9 Dec 1999 07:18:54 -0800 (PST) (envelope-from spidey@anarcat.dyndns.org) Received: by anarcat.dyndns.org (Postfix, from userid 1000) id 273381AC3; Wed, 8 Dec 1999 14:02:55 -0500 (EST) From: Spidey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14414.43871.194476.234167@anarcat.dyndns.org> Date: Wed, 8 Dec 1999 14:02:55 -0500 (EST) To: gilletd9@cti.ecp.fr Cc: freebsd-stable@FreeBSD.ORG Subject: Re: question about make installworld References: <19991207125331.A69583@srv-sio.sio.ecp.fr> X-Mailer: VM 6.72 under 21.1 (patch 7) "Biscayne" XEmacs Lucid Reply-To: Spidey Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This has been discussed before. I think it looks like make DESTDIR=/test installworld You might also like to do the buildworld the same way, just to be sure... AnarCat --- Big Brother told Didier GILLET to write, at 12:53 of December 7: > hello, > > after a make buildworld, how can i change the root target directory for making an installworld not on / but somewhere else (let's say /test) > > TIA > Didier > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 7:56:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from thelab.hub.org (nat196.191.mpoweredpc.net [142.177.196.191]) by hub.freebsd.org (Postfix) with ESMTP id AE8341570E; Thu, 9 Dec 1999 07:56:28 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id LAA16335; Thu, 9 Dec 1999 11:56:26 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 9 Dec 1999 11:56:25 -0400 (AST) From: The Hermit Hacker To: Ben Speirs Cc: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: Re: SCSI problem ... OS or just bus? In-Reply-To: <384F3A52.23868C19@ix.netcom.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 As an update, so far...without turning news back on again, and after upgrading the kernel and doing a make world 12hrs ago, things have been stable *so far*...the first time this happened after we added the drives, it took about 17hrs or so...subsequent ones generally took 2-4hrs... I'm going to re-enable news this afternoon and see if adding that extra thrashing to the system causes a repeat of the problem or not... On Wed, 8 Dec 1999, Ben Speirs wrote: > The Hermit Hacker wrote: > > > > I recently did two upgrades in the course of a few days...upgraded my > > 3.3-STABLE to a more recent version, and added hard drives onto the > > system...now I'm getting SCSI problems that make no sense :( > > > > The machine just hung once more, which its doing every few hours...I can > > get down to the debugger, but a 'trace' doesn't appear to show anyting, so > > I panic... > > > > ========== > > (da4:ahc0:0:8:0): Other SCB Timeout > > (da4:ahc0:0:8:0): SCB 0xeb - timed out in dataout phase, SEQADDR == 0x10f > > (da4:ahc0:0:8:0): Other SCB Timeout > > (da2:ahc0:0:5:0): SCB 0x24 - timed out in dataout phase, SEQADDR == 0x10f > > (da2:ahc0:0:5:0): BDR message in message buffer > > (da2:ahc0:0:5:0): SCB 0x92 - timed out in dataout phase, SEQADDR == 0x10f > > (da2:ahc0:0:5:0): no longer in timeout, status = 34b > > ahc0: Issued Channel A Bus Reset. 98 SCBs aborted > > Just another data point - A similar thing happened to me. I rebuilt the > kernel and world back in September and my previously happy SCSI system > started issuing the same type of messages. I saved the output of the > system log. Portions of it are listed below: > > Copyright (c) 1992-1999 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights > reserved. > FreeBSD 3.3-STABLE #3: Fri Sep 24 21:00:39 PDT 1999 > root@sloth:/usr/src/sys/compile/SLOTH > [...trim...] > ahc0: rev 0x00 int a irq 9 on pci0.9.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > [...trim...] > Waiting 8 seconds for SCSI devices to settle > changing root device to da0s3a > da0 at ahc0 bus 0 target 15 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing > Enabled > da0: 4149MB (8498506 512 byte sectors: 255H 63S/T 529C) > cd0 at ahc0 bus 0 target 0 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 8) > cd0: Attempt to query device size failed: NOT READY, Medium not present > cd1 at ahc0 bus 0 target 1 lun 0 > cd1: Removable CD-ROM SCSI-2 device > cd1: 3.300MB/s transfers > cd1: Attempt to query device size failed: NOT READY, Medium not present > > > Unexpected busfree. LASTPHASE == 0x1 > SEQADDR == 0x153 > ahc0:A:0: no active SCB for reconnecting target - issuing BUS DEVICE > RESET > SAVED_TCL == 0x0, ARG_1 == 0xff, SEQ_FLAGS == 0x0 > (cd0:ahc0:0:0:0): SCB 0x16 - timed out in datain phase, SEQADDR == 0x153 > (cd0:ahc0:0:0:0): Other SCB Timeout > (da0:ahc0:0:15:0): SCB 0x3 - timed out in datain phase, SEQADDR == 0x153 > (da0:ahc0:0:15:0): BDR message in message buffer > (da0:ahc0:0:15:0): SCB 0x3 - timed out in datain phase, SEQADDR == 0x153 > (da0:ahc0:0:15:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 2 SCBs aborted > fd0c: hard error reading fsbn 0 (No status) > > > The problem occurred while accessing the da0 device and cd0 device at > the same time. I could reproduce it at will, and almost instantly by > copying a file from the CD-ROM to the hard drive. I could not reproduce > the error with the older, slower NEC cd1 CD-ROM device. I rechecked all > my termination and unplugged one device after another without any > success. My guess was that the cd0 drive had gone goofy on me. The > only thing I have not tried is replacing the cables. Since I had the > other CD available my fix was to yank out the suspect device. It has > been near the bottom of my 'things to do' list. > > Maybe we both got bit by the same "fix" that uncovered hidden hardware > problems. Maybe not, it looks like you have problems with only Wide > channel devices. > > -- > -Ben Speirs > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 9:19:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5EC5A155AC for ; Thu, 9 Dec 1999 09:19:42 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA29296 for ; Thu, 9 Dec 1999 09:19:41 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA37804; Thu, 9 Dec 1999 09:19:40 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 9 Dec 1999 09:19:40 -0800 (PST) Message-Id: <199912091719.JAA37804@vashon.polstra.com> To: stable@freebsd.org Subject: Re: Route table leaks In-Reply-To: <199912090458.UAA01426@gndrsh.dnsmgr.net> References: <199912090458.UAA01426@gndrsh.dnsmgr.net> Organization: Polstra & Co., Seattle, WA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have just now committed the fix in -current for the route table leaks that started this thread. It is in revision 1.57 of "src/sys/net/route.c" and it should appear on the mirror sites within an hour. Below is the equivalent patch for -stable. I would appreciate it if those of you who think you have been experiencing leaks in -stable would try the patch and let me know whether it fixes the leaks for you. If you can let me know within a couple days then maybe I can persuade Jordan to let me merge it in time for 3.4-RELEASE. John Index: route.c =================================================================== RCS file: /home/ncvs/src/sys/net/route.c,v retrieving revision 1.50.2.1 diff -u -r1.50.2.1 route.c --- route.c 1999/08/29 16:28:32 1.50.2.1 +++ route.c 1999/12/09 17:11:57 @@ -87,9 +87,7 @@ rtalloc(ro) register struct route *ro; { - if (ro->ro_rt && ro->ro_rt->rt_ifp && (ro->ro_rt->rt_flags & RTF_UP)) - return; /* XXX */ - ro->ro_rt = rtalloc1(&ro->ro_dst, 1, 0UL); + rtalloc_ign(ro, 0UL); } void @@ -97,8 +95,17 @@ register struct route *ro; u_long ignore; { - if (ro->ro_rt && ro->ro_rt->rt_ifp && (ro->ro_rt->rt_flags & RTF_UP)) - return; /* XXX */ + struct rtentry *rt; + int s; + + if ((rt = ro->ro_rt) != NULL) { + if (rt->rt_ifp != NULL && rt->rt_flags & RTF_UP) + return; + /* XXX - We are probably always at splnet here already. */ + s = splnet(); + RTFREE(rt); + splx(s); + } ro->ro_rt = rtalloc1(&ro->ro_dst, 1, ignore); } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 9:33:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 9B27D15692 for ; Thu, 9 Dec 1999 09:33:11 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id SAA04496; Thu, 9 Dec 1999 18:33:02 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912091719.JAA37804@vashon.polstra.com> References: <199912090458.UAA01426@gndrsh.dnsmgr.net> <199912091719.JAA37804@vashon.polstra.com> Date: Thu, 9 Dec 1999 18:32:23 +0100 To: John Polstra , stable@FreeBSD.ORG From: Brad Knowles Subject: Re: Route table leaks Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:19 AM -0800 1999/12/9, John Polstra wrote: > Below is the equivalent patch for -stable. I would > appreciate it if those of you who think you have been experiencing > leaks in -stable would try the patch and let me know whether it > fixes the leaks for you. I've applied the patch and am rebuilding now. I presume that once this is installed, I'll need to reboot the machine? -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 9:36:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 5D4AA14EBD for ; Thu, 9 Dec 1999 09:36:16 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id JAA29394; Thu, 9 Dec 1999 09:36:12 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id JAA37850; Thu, 9 Dec 1999 09:36:11 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 09 Dec 1999 09:36:11 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Brad Knowles Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > I've applied the patch and am rebuilding now. I presume that > once this is installed, I'll need to reboot the machine? That's right. You don't even need to do a make world. Just apply the patch, build and install a new kernel, and reboot. John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 9:41:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 9CC11156A0 for ; Thu, 9 Dec 1999 09:41:40 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id SAA06890; Thu, 9 Dec 1999 18:41:36 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 9 Dec 1999 18:40:45 +0100 To: John Polstra From: Brad Knowles Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:36 AM -0800 1999/12/9, John Polstra wrote: > That's right. You don't even need to do a make world. Just apply the > patch, build and install a new kernel, and reboot. Blargh. ;-) I figured it was changing the system call (not something as simple as changing route(8)), so that world would need to be rebuilt in addition to the new kernel. I guess that'll teach me. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 9:50:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 0C4551564C for ; Thu, 9 Dec 1999 09:50:18 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id SAA09269 for ; Thu, 9 Dec 1999 18:50:18 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: Date: Thu, 9 Dec 1999 18:48:56 +0100 To: freebsd-stable@freebsd.org From: Brad Knowles Subject: Kinda weird warning about NTP... Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Folks, I recall recent posts regarding changes in NTP under 3.3-STABLE, but I'm running 3.2-RELEASE on one of my machines, which I'm currently rebuilding the kernel on to test a patch to /usr/src/sys/net/route.c. However, I noticed the following warning during the kernel build process: cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../kern/kern_ntptime.c ../../kern/kern_ntptime.c:533: warning: initialization from incompatible pointer type Now, maybe this has been there all along, maybe this has been discussed prior to when I subscribed to the list in September, or maybe I missed some threads since then, but I didn't see anything that appeared to be related to this in my private archive of this mailing list. I hope this isn't something I need to be worried about? -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 9:55:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.tvol.com (mail.wgate.com [38.219.83.4]) by hub.freebsd.org (Postfix) with ESMTP id 4E65E155E5; Thu, 9 Dec 1999 09:55:39 -0800 (PST) (envelope-from rjesup@wgate.com) Received: from jesup.eng.tvol.net (jesup.eng.tvol.net [10.32.2.26]) by mail.tvol.com (8.8.8/8.8.3) with ESMTP id MAA14412; Thu, 9 Dec 1999 12:55:05 -0500 (EST) Reply-To: Randell Jesup To: Shaun Jurrens Cc: Harlan Stenn , freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: SCSI problem ... OS or just bus? References: <19991209115148.A10267@shamz.net> <707.944736910@brown.pfcs.com> <19991209122155.B10267@shamz.net> From: Randell Jesup Date: 09 Dec 1999 12:55:34 -0500 In-Reply-To: Shaun Jurrens's message of "Thu, 9 Dec 1999 12:21:55 +0100" Message-ID: X-Mailer: Gnus v5.6.43/Emacs 20.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Shaun Jurrens writes: >On Thu, Dec 09, 1999 at 05:55:10AM -0500, Harlan Stenn wrote: >#> Is the SCSI chain too long? >#> >#> H >There are only three drives internally with extra cooling on the flat band >cable connected to the wide bus. The cable is ca. 30cm long. AFAIK, the scsi >wide bus will work up to 1.3m, or maybe it was 3m, in any case the cable isn't >too long. It all worked perfectly up until about the end of June, actually. >The bugs seemed too random to put my finger on it, although I have really >tried everything. I've seen SCSI cables go bad (usually after handling/plugging/etc, but sometimes apparently randomly, even in the days of 5MB/s 8-bit SCSI). The effects can be very strange. Also, active terminators could go bad or get damaged, etc (quite less likely). Another common often-forgotten failure mode is a power-supply problem. I've seen drives that will spin up and talk, and when you try to get them to read/seek, they'd reset or even head-crash - until you moved them to another power supply. -- Randell Jesup, Worldgate Communications, ex-Scala, ex-Amiga OS team ('88-94) rjesup@wgate.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 9 10: 1: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 0E04414A03 for ; Thu, 9 Dec 1999 10:01:05 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id TAA15926; Thu, 9 Dec 1999 19:00:53 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 9 Dec 1999 19:00:11 +0100 To: John Polstra From: Brad Knowles Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 9:36 AM -0800 1999/12/9, John Polstra wrote: > That's right. You don't even need to do a make world. Just apply the > patch, build and install a new kernel, and reboot. Kernel is rebuilt and the machine has come back up. I've got a script running to monitor the leakage. However, I obviously haven't been running very long, and there's been no chance to see the leak. Do you have any suggestion on how I can try to force some leakage? Thanks! -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 10:10:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 2027614D0D for ; Thu, 9 Dec 1999 10:10:24 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA29559; Thu, 9 Dec 1999 10:10:23 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA37991; Thu, 9 Dec 1999 10:10:22 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 9 Dec 1999 10:10:22 -0800 (PST) Message-Id: <199912091810.KAA37991@vashon.polstra.com> To: blk@skynet.be Subject: Re: Route table leaks In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brad Knowles wrote: > > Kernel is rebuilt and the machine has come back up. I've got a > script running to monitor the leakage. However, I obviously haven't > been running very long, and there's been no chance to see the leak. > Do you have any suggestion on how I can try to force some leakage? Yep, but I don't want to taint the results since I'm interested in finding out whether it fixes _your_ leaks, not mine. :-) John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 10:25:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 3B697155E5 for ; Thu, 9 Dec 1999 10:25:48 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id TAA22784; Thu, 9 Dec 1999 19:25:38 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912091810.KAA37991@vashon.polstra.com> References: <199912091810.KAA37991@vashon.polstra.com> Date: Thu, 9 Dec 1999 19:24:33 +0100 To: John Polstra From: Brad Knowles Subject: Re: Route table leaks Cc: stable@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:10 AM -0800 1999/12/9, John Polstra wrote: > Yep, but I don't want to taint the results since I'm interested in > finding out whether it fixes _your_ leaks, not mine. :-) Some big help you are. ;-) Seriously, I appreciate the patch, and I'll leave my monitoring script running for at least a couple of days or so to see if I find any leaks. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 10:29:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9E50C150F8 for ; Thu, 9 Dec 1999 10:29:27 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id KAA29689; Thu, 9 Dec 1999 10:29:26 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id KAA38057; Thu, 9 Dec 1999 10:29:26 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 9 Dec 1999 10:29:26 -0800 (PST) Message-Id: <199912091829.KAA38057@vashon.polstra.com> To: blk@skynet.be Subject: Re: Route table leaks In-Reply-To: References: <199912091810.KAA37991@vashon.polstra.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brad Knowles wrote: > > Some big help you are. ;-) Thank you thank you. It was nothing, really. :-) > Seriously, I appreciate the patch, and I'll leave my monitoring > script running for at least a couple of days or so to see if I find > any leaks. Thanks for helping me test it! John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 10:31:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id BCCC1156D2 for ; Thu, 9 Dec 1999 10:31:32 -0800 (PST) (envelope-from T.Pagtzis@cs.ucl.ac.uk) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 9 Dec 1999 18:30:53 +0000 X-Mailer: exmh version 2.0.2 To: "Sameer R. Manek" Cc: Jose Marques , freebsd-stable Subject: Re: 3.2 -> 3.3-stable In-reply-to: Your message of "Wed, 08 Dec 1999 13:20:47 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Dec 1999 18:30:51 +0000 Message-ID: <13867.944764251@cs.ucl.ac.uk> From: Theo PAGTZIS Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi guys, I did a cvsup on the the 8th and the world build trashed on main and in particular on diff.o giving me undefined ref to prepend_default_options Is there a reason for that? Theo >> [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Jose Marques >> Sent: Wednesday, December 08, 1999 11:57 AM >> >> I would like to use CVSup to bring a machine currently running FreeBSD >> 3.2-RELEASE up to 3.3-stable. Are there any "gotchas" that I should be >> aware of? > >Biggest one would be if you cvsup tonight, you'll jump to 3.4-RC. 3.4-RC is >a release canidate, aka beta for 3.4-RELEASE. You might want to wait until >3.4-RELEASE, the source tree can get a little unstable just before -RELEASE, >as the developers scramble to get patches commited before the code freeze. > >3.4-RELEASE is scheduled to come out right around the same time Santa does, >so might as well wait a few days, and have some eggnog. > >Sameer > > > >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 9 10:37:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 69A7D153C4 for ; Thu, 9 Dec 1999 10:37:11 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id TAA19473; Thu, 9 Dec 1999 19:37:06 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912091829.KAA38057@vashon.polstra.com> References: <199912091810.KAA37991@vashon.polstra.com> <199912091829.KAA38057@vashon.polstra.com> Date: Thu, 9 Dec 1999 19:35:46 +0100 To: John Polstra From: Brad Knowles Subject: Re: Route table leaks Cc: stable@freebsd.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:29 AM -0800 1999/12/9, John Polstra wrote: > Thanks for helping me test it! I'm just glad I can finally do something useful! -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 10:43: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 9D68914D0D for ; Thu, 9 Dec 1999 10:43:02 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 507ED9B1C; Thu, 9 Dec 1999 13:43:00 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 46EFCBA0C; Thu, 9 Dec 1999 13:43:00 -0500 (EST) Date: Thu, 9 Dec 1999 13:43:00 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Theo PAGTZIS Cc: freebsd-stable Subject: Re: 3.2 -> 3.3-stable In-Reply-To: <13867.944764251@cs.ucl.ac.uk> 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, 9 Dec 1999, Theo PAGTZIS wrote: > Hi guys, > > I did a cvsup on the the 8th and the world build trashed on main and in > particular on diff.o giving me undefined ref to prepend_default_options > > Is there a reason for that? > Because -stable world was broken for a while...re-cvsup and try again. ----- Chris D. Faulhaber | All the true gurus I've met never System/Network Administrator, | claimed they were one, and always Reality Check Information, Inc. | pointed to someone better. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 11: 7:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 1D4B314C0F for ; Thu, 9 Dec 1999 11:07:11 -0800 (PST) (envelope-from mvh@ix.netcom.com) Received: from netcom1.netcom.com (lai-ca4b-20.ix.netcom.com [209.110.245.20]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id OAA02628; Thu, 9 Dec 1999 14:07:06 -0500 (EST) Received: by netcom1.netcom.com (Postfix, from userid 1000) id 1064BA5B78; Thu, 9 Dec 1999 11:05:44 -0800 (PST) From: Mike Harding To: andrew@ugh.net.au Cc: freebsd-stable@freebsd.org In-reply-to: (andrew@ugh.net.au) Subject: Re: CRON in malloc(): warning: pointer to wrong page. References: Message-Id: <19991209190544.1064BA5B78@netcom1.netcom.com> Date: Thu, 9 Dec 1999 11:05:44 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I saw this behavior today as well - my -STABLE is dated FreeBSD 3.4-RC #0: Tue Dec 7 09:15:50 PST 1999 mvh@netcom1.netcom.com:/usr/src/sys/compile/MIKEIPF Date: Thu, 9 Dec 1999 11:19:53 +1000 (EST) From: andrew@ugh.net.au X-WonK: *wibble* Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Precedence: bulk X-RULES: lists Hi, Every time a cron job runs it produces the output: CRON in malloc(): warning: pointer to wrong page. which gets mailed to root. I searched the archives but didn't come up with anything. Nothing seems to produce that error when run interactively. We're running 3.3-STABLE from November the 29th on an IBM 686 200 with 32MB RAM and an IDE drive. On a probably related matter we had a lot of processes die with signal 4 (one or two a day). We swapped the RAM and I thought it had stopped but one died yesterday (telnetd). Previously running make index in /usr/ports would always die with sig4 but since the RAM swap its been fine... Any suggestions? I assume sig4 indicates that there is corruption in either the memory, cache or bus but I have no idea why or what causes the CRON error. Thanks, Andrew 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 9 11:10:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nisser.com (c1870039.telekabel.chello.nl [212.187.0.39]) by hub.freebsd.org (Postfix) with ESMTP id BDECB14CF6 for ; Thu, 9 Dec 1999 11:10:33 -0800 (PST) (envelope-from roelof@nisser.com) Received: from nisser.com (roelof [10.0.0.2]) by nisser.com (8.9.3/8.9.2) with ESMTP id UAA10084; Thu, 9 Dec 1999 20:10:36 +0100 (CET) (envelope-from roelof@nisser.com) Message-ID: <384FFEC6.276F4A1E@nisser.com> Date: Thu, 09 Dec 1999 20:11:02 +0100 From: Roelof Osinga Organization: eboa - engineering buro Office Automation X-Mailer: Mozilla 4.7 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: mw@freibergnet.de Cc: FreeBSD Stable Subject: Re: ifpw forwarding problem References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Welk wrote: > > As I understood it, you tell natd the interface it's going to work on for > the purpose that it get's is (probably dynamic) IP address from this > interface (the IP address it should use for translated packets). You can either give it the interface or its IP address. In my case they're equal since I've got a static IP address. > You still have to pass the packets from the IP firewall to natd by divert > rules in the firewall ruleset. Did too! . I'll paste the configs at the end. > Take care at the spelling. I'm not sure about how tolerant natd is in > reading the options from a config file, they are slightly different. > My example is correct and the option is really called "deny_incoming" > (with the value "no"). Not very. However, I was referring to: ... actioned. If no other action can be made, and if -deny_incoming is not specified, the packet is delivered to the local machine and port as specified in the packet. From which I've gathered that deny incoming is not the default. As for the options, the best source is the error output. > You need this if you are going to setup rules for a transparent proxy, > but with redirect_address the packet should arrive with the original > address at the host in the internal network. When it works I'll see if it does. Doesn't get mentioned in the man page whereas it does for proxe_rule. > use_sockets yes > same_ports > redirect_port ... I ended up by looking at the error output for hints and just fiddling till it got accepted. > Argh! You're right, from the internal network I can't access the host with > it's external address. The same bug here! (This machines offers some web > services and FTP via NATD to the outside and obviously nobody tried to use > these services from our internal network :-) ) I'm not sure. I currently run the ports/net/bounce program. That listens to the external interface and redirects traffic from the inside. But presumably it does not do it transparently. > Woah! Never really experienced such trouble. Unfortunately I did. Gone now that I reverted to the pre-FORWARD kernel. > options IPFIREWALL > > All except those marked with * are running on our primary server that doesn > NAT for the internal network, the others are in my desktop machine's kernel. > > Both run rock-stable with 3.3-STABLE. It didn't crash or anything. Networking just became erratic. Things (TCP/IP things, that is) stopped. Had to kill natd and restart it to get it going again. Lost telnet en news sessions. Webbrowsers stopped browsing. Things like that. I believe it had been running for some 75 days flawlessly before I put in that option. It occurs in conjunction with natd since I can't remember those effects when I was fiddling with ipfw in that kernel. > Did you include IPDIVERT? Oh yes, see below. > No, it doesn't. I usually kill it before (re-) starting it. If this > behaviour has changed, I haven't noticed. It hasn't. I looked at the source. SIGHUP signals a change in IP address or something. It only handles SIGTERM and SIGHUP. > (I made the experience that in some circumstances starting a new natd after > killing the older one something didn't work properly anymore, especially on > a machine here with six Ethernet interfaces and three natd's running > parallel. I had to reboot it after doing very heavy changes :-) ) Same thing happens with but two NICs . Bit bothersome in that they don't always seem to stay dead when you kill them. Maybe this was the cause for that erratic behavior and GOTCHA! in that you evidently also have experienced erratic behavior ;). I blame the combination with IPFIREWALL_FORWARD. It's not the first time I've fiddled with natd, but it *is* the first time I've experienced such behaviour. > Which version of FreeBSD are you running? OK, here it comes. A fresh set of data. This is how it is *now*. Thus with FORWARD disabled. Some testscripts are at the end. Maybe you can spot the error, I sure can't. Roelof nisser:~$ uname -a FreeBSD nisser.com 3.3-STABLE FreeBSD 3.3-STABLE #12: Wed Dec 8 08:24:55 CET 1999 root@nisser.com:/usr/src/sys/compile/FORSETI i386 nisser:~$ grep IP /usr/src/sys/i386/conf/FORSETI #options IPX #IPX/SPX communications protocols options IPFIREWALL #firewall #options IPFIREWALL_VERBOSE #print information about #options IPFIREWALL_FORWARD #enable transparent proxy support #options "IPFIREWALL_VERBOSE_LIMIT=100" #limit verbosity #options IPFIREWALL_DEFAULT_TO_ACCEPT #allow everything by default options IPDIVERT #divert sockets options IPFILTER #kernel ipfilter support #options IPFILTER_LOG #ipfilter logging #options IPFILTER_LKM #kernel support for ip_fil.o LKM nisser:~$ ifconfig -a ep0: flags=8843 mtu 1500 inet 10.0.0.55 netmask 0xffffff00 broadcast 10.0.0.255 ether 00:60:97:14:31:a7 ep1: flags=8843 mtu 1500 inet 212.187.0.39 netmask 0xfffff800 broadcast 212.187.7.255 inet 194.134.130.170 netmask 0xffffffff broadcast 194.134.130.170 ether 00:60:97:e4:98:db lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 nisser:~$ cat /etc/rc.conf | grep -v ^# moused_type="mousesystems" moused_enable="YES" gateway_enable="YES" network_interfaces="ep0 ep1 lo0" ifconfig_ep0="inet 10.0.0.55 netmask 255.255.255.0" ifconfig_ep1="inet 212.187.0.39 netmask 255.255.248.0" ifconfig_ep1_alias0="inet 194.134.130.170 netmask 255.255.255.255" defaultrouter="212.187.0.1" hostname="nisser.com" saver="blank" blanktime="300" keyrate="fast" ntpdate_flags="ntp0.nl.net" ntpdate_enable="YES" named_enable="YES" nisser:~$ cat /etc/rc.conf.local | grep -v ^# firewall_enable=YES firewall_type=open natd_enable=YES natd_interface=ep1 natd_flags=-f /etc/natd.conf nisser:~$ cat /etc/natd.conf # as used in rc.conf.local use_sockets yes same_ports #redirect_port tcp 212.187.0.39:8080 10.0.0.3:80 #proxy_rule type encode_ip_hdr port 8080 server 10.0.0.3:80 nisser:~# ipfw list 00100 divert 8668 ip from any to any via ep1 00100 allow ip from any to any via lo0 00200 deny ip from any to 127.0.0.0/8 01000 deny tcp from any to any 23,143,110,79,111 in recv ep1 01000 deny tcp from any to any 5800,5801,5802,5900,5901,5902 in recv ep1 65000 allow ip from any to any 65535 deny ip from any to any nisser:~$ cat /root/bin/locHans ipfw add 2000 fwd 10.0.0.3,80 tcp from any to 10.0.0.55 8080 in via ep0 nisser:~$ cat /root/bin/redirHans natd -n ep1 -use_sockets -same_ports -redirect_port tcp 212.187.0.39:8080 10.0.0.3:80 -- Home is where the (@) http://eboa.com/ is. Telekabel home http://nisser.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 9 11:30:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zgia.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with SMTP id 7CC5E15719 for ; Thu, 9 Dec 1999 11:30:00 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by zgia.zp.ua (8.9.3/8.9.3) with ESMTP id WAA70476 for ; Thu, 9 Dec 1999 22:29:30 GMT Date: Thu, 9 Dec 1999 22:29:29 +0000 (GMT) From: Alexandr Listopad To: freebsd-stable@FreeBSD.org Subject: netgraph - need more info. 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! I want to know more about netgraph in -STABLE. I saw a web-page about it. But I want to know more... If you had tested it - please mail about your experience. And if you can mail your examples - please do it... Thanks. Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 11:36:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from bells.cs.ucl.ac.uk (bells.cs.ucl.ac.uk [128.16.5.31]) by hub.freebsd.org (Postfix) with SMTP id D504F14C0F for ; Thu, 9 Dec 1999 11:36:45 -0800 (PST) (envelope-from T.Pagtzis@cs.ucl.ac.uk) Received: from ginger.cs.ucl.ac.uk by bells.cs.ucl.ac.uk with local SMTP id ; Thu, 9 Dec 1999 19:36:20 +0000 X-Mailer: exmh version 2.0.2 To: "Chris D. Faulhaber" Cc: Theo PAGTZIS , freebsd-stable Subject: Re: 3.2 -> 3.3-stable In-reply-to: Your message of "Thu, 09 Dec 1999 13:43:00 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Dec 1999 19:36:19 +0000 Message-ID: <13992.944768179@cs.ucl.ac.uk> From: Theo PAGTZIS Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is definetely a paradox... A stable which is not stable...what is it (enigma) ? This definitely proves once more my thought about the erroneous of the naming convention and the semantics behind it..... My impression of a stable is that one develops something which has been tested to the extent that is stable, i.e won't crash unless you stress it to the limits (whatever the limits are). Obviously this stable should need more testing before one can promote it to RC or release candidate..It is only when the release candidate has matured in terms of bug fixes that it could move up to a RELEASE merging with the master branch and setting there a revertable milestone. From release one could then spawn a new branch that would move for the next version of stable---RC-----Release. In other words: 1) ----- (proposed) REL 3.2-----Stable 3.3-----RC 3.3----REL 3.3---Stable 3.4---RC 3.4---REL 3.4---etc.. with a new branch spawning at REL 3.X and merging back on REL 3.Y for new developments while the master REL 3 is kept only with getting more bugs fixed not new development unless a merge with REL 3.Z is imminent (and even that should be branch-layered) if you want to really keep the REL master branch intact from merge waves.. whereas now the scheme is 2) ------ (currently) REL 3.2----Stable 3.2---RC 3.3---REL 3.3---Stable 3.3----RC 3.4---REL 3.4---Stable 3.4----etc.. Now look the situation of the crash of the stable 3.3 and try to place it in one of the two schemes...which one is more reasonable for you...?????? Consider now again the existing convention....is it really sound????? Theodore CS dept. UCL >On Thu, 9 Dec 1999, Theo PAGTZIS wrote: > >> Hi guys, >> >> I did a cvsup on the the 8th and the world build trashed on main and in >> particular on diff.o giving me undefined ref to prepend_default_options >> >> Is there a reason for that? >> > >Because -stable world was broken for a while...re-cvsup and try again. > >----- >Chris D. Faulhaber | All the true gurus I've met never >System/Network Administrator, | claimed they were one, and always >Reality Check Information, Inc. | pointed to someone better. > > > > >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 9 11:57:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 8E441156B6 for ; Thu, 9 Dec 1999 11:56:58 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id UAA20121; Thu, 9 Dec 1999 20:56:47 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912091829.KAA38057@vashon.polstra.com> References: <199912091810.KAA37991@vashon.polstra.com> <199912091829.KAA38057@vashon.polstra.com> Date: Thu, 9 Dec 1999 20:56:34 +0100 To: John Polstra From: Brad Knowles Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:29 AM -0800 1999/12/9, John Polstra wrote: > Thanks for helping me test it! So far, it looks like it might have fixed the problem. At least, the "InUse" count goes down when a route goes away: Thu Dec 9 20:14:03 CET 1999 netstat -ran | wc -l 123 vmstat -m | grep routetbl | grep K routetbl 250 35K 35K 40960K 260 0 0 16,32,64,128,256 uptime 8:14PM up 1:23, 1 user, load averages: 1.67, 2.34, 3.27 Thu Dec 9 20:15:03 CET 1999 netstat -ran | wc -l 122 vmstat -m | grep routetbl | grep K routetbl 248 34K 35K 40960K 260 0 0 16,32,64,128,256 uptime 8:15PM up 1:24, 1 user, load averages: 1.60, 2.19, 3.15 I'll let you know if/when I get any more results. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 13:29: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ulstu.ru (ns.ulstu.ru [62.76.34.36]) by hub.freebsd.org (Postfix) with ESMTP id 3346614F05 for ; Thu, 9 Dec 1999 13:28:47 -0800 (PST) (envelope-from vlad@high.net.ru) Received: from siemens.ulstu.ru (siemens.ulstu.ru [62.76.34.44]) by mail.ulstu.ru (8.8.5-MVC-230198/8.8.7) with ESMTP id AAA90264 for ; Fri, 10 Dec 1999 00:28:37 +0300 (MSK) (envelope-from vlad@high.net.ru) Received: from hq.spc.high (ip181.link-ul.ru [195.151.42.181]) by siemens.ulstu.ru (Postfix) with ESMTP id D638C1741D for ; Fri, 10 Dec 1999 00:27:41 +0300 (MSK) Received: by hq.spc.high (Postfix, from userid 1000) id 73A873FB; Thu, 9 Dec 1999 12:10:52 +0300 (MSK) Date: Thu, 9 Dec 1999 12:10:52 +0300 From: Vlad Skvortsov To: freebsd-stable@FreeBSD.ORG Subject: Re: CRON in malloc(): warning: pointer to wrong page. Message-ID: <19991209121051.B1277@high.net.ru> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 08, 1999 at 08:49:15PM -0500, Bosko Milekic wrote: > !>On a probably related matter we had a lot of processes die with signal 4 > !>(one or two a day). We swapped the RAM and I thought it had stopped but > !>one died yesterday (telnetd). Previously running make index in /usr/ports > !>would always die with sig4 but since the RAM swap its been fine... > !> > !>Any suggestions? I assume sig4 indicates that there is corruption in > !>either the memory, cache or bus but I have no idea why or what causes the > !>CRON error. > !> > Well, are the processes dying with signal 4 dumping core? If so, have > you tried debugging from the core dump? > Your malloc() problem could be related to something that you discover > this way. After all, the default action on receipt of signal 4 would be > to dump core. I've got similar problem with CRON, but the system itself is definintively stable with good uptime and no processes dying even at high load rates. I've swapped everything starting from motherboard and ending with RAM - nothing helps. Kinda weird. Any suggestions ? -- Vlad Skvortsov, vss@ulstu.ru, vlad@high.net.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 13:29:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell13.ba.best.com (shell13.ba.best.com [206.184.139.144]) by hub.freebsd.org (Postfix) with ESMTP id 77C08156EA for ; Thu, 9 Dec 1999 13:29:19 -0800 (PST) (envelope-from rone@ennui.org) Received: (from rone@localhost) by shell13.ba.best.com (8.9.3/8.9.2/best.sh) id NAA13087 for stable@freebsd.org; Thu, 9 Dec 1999 13:29:10 -0800 (PST) From: remorse code Message-Id: <199912092129.NAA13087@shell13.ba.best.com> Subject: Re: 3.2 -> 3.3-stable In-Reply-To: <13992.944768179@cs.ucl.ac.uk> from Theo PAGTZIS at "Dec 9, 99 07:36:19 pm" To: stable@freebsd.org Date: Thu, 9 Dec 1999 13:29:08 -0800 (PST) X-URL: http://ennui.org/rone/ X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Theo PAGTZIS writes: This is definetely a paradox... A stable which is not stable...what is it (enigma) ? Give me a break. Everyone makes mistakes. rone -- Insultant: n. Contract worker who gets paid an obscene hourly wage to insult full-time company employees. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 13:46:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 69A61151F9; Thu, 9 Dec 1999 13:45:55 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id PAA91916; Thu, 9 Dec 1999 15:44:05 -0600 (CST) From: Joe Greco Message-Id: <199912092144.PAA91916@aurora.sol.net> Subject: Re: Route table leaks In-Reply-To: <199912090743.XAA19457@tantivy.stanford.edu> from Bob Vaughan at "Dec 8, 1999 11:43:34 pm" To: techie@tantivy.stanford.edu (Bob Vaughan) Date: Thu, 9 Dec 1999 15:44:05 -0600 (CST) Cc: freebsd@gndrsh.dnsmgr.net, mike@sentex.net, current@FreeBSD.ORG, jdp@polstra.com, jgreco@ns.sol.net, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The patch previously mentioned has completely fixed my problem, as far as I can tell. routetbl 131 17K 25K 40960K 93624 0 0 16,32,64,128,256 after a day of uptime. > here's mine.. > this is from a single homed machine, with a default route. it's also a IRC > server (irc.stanford.edu), with a LOT of filtering of inbound traffic. > > FreeBSD 3.3-STABLE #8: Sat Nov 27 17:15:49 PST 1999 > > 11:33PM up 2 days, 20:41, 1 user, load averages: 0.03, 0.03, 0.00 > > routetbl 205 29K 10489K 10489K 3479960 0 0 16,32,64,128,256 > > note that the table maxed out at some point (during a DoS attack.) > > root-irc.stanford.edu-[11:34pm-52]#t> netstat -ran | wc > 70 409 4741 > > looks like it leaked 135 in 2.8 days.. > > > -- Welcome My Son, Welcome To The Machine -- > Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org > | P.O. Box 9792, Stanford, Ca 94309-9792 > -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- > -- ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 14:12:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.clientlogic.com (ns.clientlogic.com [207.51.66.75]) by hub.freebsd.org (Postfix) with ESMTP id 9F7E714FDF for ; Thu, 9 Dec 1999 14:12:14 -0800 (PST) (envelope-from ChrisMic@clientlogic.com) Received: by site0s1 with Internet Mail Service (5.5.2650.21) id ; Thu, 9 Dec 1999 17:12:16 -0500 Message-ID: <6C37EE640B78D2118D2F00A0C90FCB4401105DF3@site2s1> From: Christopher Michaels To: freebsd-stable@freebsd.org Subject: RE: 3.2 -> 3.3-stable Date: Thu, 9 Dec 1999 17:12:24 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Which reminds me. Now that -RC is coming. I remember someone was trying to co-ordinate some beta testing. Alas, I forgot who that was an if he (or she) was still co-ordinating it? If so, I wonder if there is anything I could do, other than "make world" that would be of use? -Chris > -----Original Message----- > From: Kris Kennaway [SMTP:kris@hub.freebsd.org] > Sent: Wednesday, December 08, 1999 8:51 PM > To: Sameer R. Manek > Cc: Jose Marques; freebsd-stable@freebsd.org > Subject: RE: 3.2 -> 3.3-stable > > On Wed, 8 Dec 1999, Sameer R. Manek wrote: > > > Biggest one would be if you cvsup tonight, you'll jump to 3.4-RC. 3.4-RC > is > > a release canidate, aka beta for 3.4-RELEASE. You might want to wait > until > > 3.4-RELEASE, the source tree can get a little unstable just before > -RELEASE, > > as the developers scramble to get patches commited before the code > freeze. > > > > 3.4-RELEASE is scheduled to come out right around the same time Santa > does, > > so might as well wait a few days, and have some eggnog. > > Or you could do it now, and help with the beta-testing, instead of doing > it later and finding a bug which could have been prevented from shipping > :) > > For general updating issues, see /usr/src/UPDATING after cvsup (or use > the cvsweb page on freebsd.org and find the most recent 3.x version). > > Kris > > > > 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 9 14:33: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id A1D4715206 for ; Thu, 9 Dec 1999 14:32:59 -0800 (PST) (envelope-from bright@wintelcom.net) Received: from localhost (bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) with ESMTP id PAA28780; Thu, 9 Dec 1999 15:02:41 -0800 (PST) Date: Thu, 9 Dec 1999 15:02:41 -0800 (PST) From: Alfred Perlstein To: Andre Albsmeier Cc: Warner Losh , Garance A Drosihn , stable@FreeBSD.ORG Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test In-Reply-To: <19991209153320.A62121@internal> 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, 9 Dec 1999, Andre Albsmeier wrote: > > On Tue, 7 Dec 1999, Warner Losh wrote: > > > > > I've been reviewing this patch with someone and I think the last > > > version is ready to commit. I'll take a look at my tree to make > > > sure. > > > On Tue, 07-Dec-1999 at 14:55:37 -0800, Alfred Perlstein wrote: > > please do not, the patch in PR 11997 introduces a major security flaw. > > > > someone can hardlink to any file and clobber it with a file owned by > > them: > > > > I think the (really big) security hole can be closed by not doing > the chown/chmod commands. I inserted them because I wanted the > file in the spool directory to appear exactly as if lpr would > have copied it. > I am currently running the patch with the chown/chmod removed and > lpd doesn't seem to have any problems with it. The side effect now > is that the file in the spool directory keeps it's permissions. > I don't think that this is a problem because if the file was > set to 666 by the creator before, he doesn't care a lot about > it anyway :-) > > What do people think about this? Alfred, Warner ? > > For better reference, here is the current patch: > > *** lpr.c.ORI Thu Dec 9 15:30:18 1999 > --- lpr.c Thu Dec 9 15:30:35 1999 > *************** > *** 370,375 **** > --- 370,405 ---- > } > if (sflag) > printf("%s: %s: not linked, copying instead\n", name, arg); > + /* > + * If lpr was invoked with -r we try to move the file to > + * be printed instead of copying and deleting it later. > + * This works if the file and lpd's spool directory are > + * on the same filesystem as it is often the case for files > + * printed by samba or pcnfsd. In this case, a lot of I/O > + * and temporary disk space can be avoided. Otherwise, we > + * will continue normally. > + */ > + if (f) { /* file should be deleted */ > + seteuid(euid); /* needed for rename() */ > + if (!rename(arg, dfname)) { > + int i; > + #if 0 > + chown(dfname, userid, getegid()); > + chmod(dfname, S_IRUSR | S_IWUSR | > + S_IRGRP | S_IWGRP); > + #endif > + seteuid(uid); /* restore old uid */ > + if (format == 'p') > + card('T', title ? title : arg); > + for (i = 0; i < ncopies; i++) > + card(format, &dfname[inchar-2]); > + card('U', &dfname[inchar-2]); > + card('N', arg); > + nact++; > + continue; > + } > + seteuid(uid); /* restore old uid */ > + } > if ((i = open(arg, O_RDONLY)) < 0) { > printf("%s: cannot open %s\n", name, arg); > } else { > > I don't have too much time to think about this, argue me this: why should I allow a user to print any file on the system? the race condition is still there. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 14:33:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id 7A53815033 for ; Thu, 9 Dec 1999 14:33:15 -0800 (PST) (envelope-from bsd@a.servers.aozilla.com) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id RAA12695; Thu, 9 Dec 1999 17:32:58 -0500 (EST) Date: Thu, 9 Dec 1999 17:32:58 -0500 (EST) From: "Mr. K." X-Sender: bsd@inbox.org To: Christopher Michaels Cc: freebsd-stable@FreeBSD.ORG Subject: RE: 3.2 -> 3.3-stable In-Reply-To: <6C37EE640B78D2118D2F00A0C90FCB4401105DF3@site2s1> 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 there somewhere I can download disk images and to a full network install? I have a cablemodem so minimal install should be quick and painless. On Thu, 9 Dec 1999, Christopher Michaels wrote: > Which reminds me. Now that -RC is coming. I remember someone was trying to > co-ordinate some beta testing. Alas, I forgot who that was an if he (or > she) was still co-ordinating it? > > If so, I wonder if there is anything I could do, other than "make world" > that would be of use? > > -Chris > > > -----Original Message----- > > From: Kris Kennaway [SMTP:kris@hub.freebsd.org] > > Sent: Wednesday, December 08, 1999 8:51 PM > > To: Sameer R. Manek > > Cc: Jose Marques; freebsd-stable@freebsd.org > > Subject: RE: 3.2 -> 3.3-stable > > > > On Wed, 8 Dec 1999, Sameer R. Manek wrote: > > > > > Biggest one would be if you cvsup tonight, you'll jump to 3.4-RC. 3.4-RC > > is > > > a release canidate, aka beta for 3.4-RELEASE. You might want to wait > > until > > > 3.4-RELEASE, the source tree can get a little unstable just before > > -RELEASE, > > > as the developers scramble to get patches commited before the code > > freeze. > > > > > > 3.4-RELEASE is scheduled to come out right around the same time Santa > > does, > > > so might as well wait a few days, and have some eggnog. > > > > Or you could do it now, and help with the beta-testing, instead of doing > > it later and finding a bug which could have been prevented from shipping > > :) > > > > For general updating issues, see /usr/src/UPDATING after cvsup (or use > > the cvsweb page on freebsd.org and find the most recent 3.x version). > > > > Kris > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 15: 4: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id D8F32156B0; Thu, 9 Dec 1999 15:03:57 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id PAA02150; Thu, 9 Dec 1999 15:00:31 -0800 (PST) Date: Thu, 9 Dec 1999 15:00:30 -0800 (PST) From: Julian Elischer To: Joe Greco Cc: Bob Vaughan , freebsd@gndrsh.dnsmgr.net, mike@sentex.net, current@FreeBSD.ORG, jdp@polstra.com, stable@FreeBSD.ORG Subject: Re: Route table leaks In-Reply-To: <199912092144.PAA91916@aurora.sol.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 so can it be committed? On Thu, 9 Dec 1999, Joe Greco wrote: > The patch previously mentioned has completely fixed my problem, as far as I > can tell. > > routetbl 131 17K 25K 40960K 93624 0 0 16,32,64,128,256 > > after a day of uptime. > > > here's mine.. > > this is from a single homed machine, with a default route. it's also a IRC > > server (irc.stanford.edu), with a LOT of filtering of inbound traffic. > > > > FreeBSD 3.3-STABLE #8: Sat Nov 27 17:15:49 PST 1999 > > > > 11:33PM up 2 days, 20:41, 1 user, load averages: 0.03, 0.03, 0.00 > > > > routetbl 205 29K 10489K 10489K 3479960 0 0 16,32,64,128,256 > > > > note that the table maxed out at some point (during a DoS attack.) > > > > root-irc.stanford.edu-[11:34pm-52]#t> netstat -ran | wc > > 70 409 4741 > > > > looks like it leaked 135 in 2.8 days.. > > > > > > -- Welcome My Son, Welcome To The Machine -- > > Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org > > | P.O. Box 9792, Stanford, Ca 94309-9792 > > -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 15:17:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 352B414C1F for ; Thu, 9 Dec 1999 15:17:53 -0800 (PST) (envelope-from blk@skynet.be) Received: from [194.78.238.58] (dialup890.brussels2.skynet.be [194.78.238.58]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id AAA10833; Fri, 10 Dec 1999 00:17:34 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: <199912091810.KAA37991@vashon.polstra.com> <199912091829.KAA38057@vashon.polstra.com> Date: Fri, 10 Dec 1999 00:16:21 +0100 To: John Polstra From: Brad Knowles Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:56 PM +0100 1999/12/9, Brad Knowles wrote: > So far, it looks like it might have fixed the problem. At least, > the "InUse" count goes down when a route goes away: Things continue to look good: Thu Dec 9 20:59:15 CET 1999 netstat -ran | wc -l 122 vmstat -m | grep routetbl | grep K routetbl 248 34K 35K 40960K 260 0 0 16,32,64,128,256 uptime 8:59PM up 2:08, 0 users, load averages: 2.13, 2.11, 2.16 Thu Dec 9 21:00:16 CET 1999 netstat -ran | wc -l 121 vmstat -m | grep routetbl | grep K routetbl 246 34K 35K 40960K 260 0 0 16,32,64,128,256 uptime 9:00PM up 2:09, 0 users, load averages: 3.18, 2.50, 2.31 [ ... deletia ... ] Thu Dec 9 21:56:40 CET 1999 netstat -ran | wc -l 121 vmstat -m | grep routetbl | grep K routetbl 246 34K 35K 40960K 260 0 0 16,32,64,128,256 uptime 9:56PM up 3:05, 0 users, load averages: 2.79, 2.87, 3.08 Thu Dec 9 21:57:40 CET 1999 netstat -ran | wc -l 120 vmstat -m | grep routetbl | grep K routetbl 244 34K 35K 40960K 260 0 0 16,32,64,128,256 uptime 9:57PM up 3:06, 0 users, load averages: 2.90, 2.93, 3.09 -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 15:18:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id BAF7C14CC8; Thu, 9 Dec 1999 15:18:18 -0800 (PST) (envelope-from blk@skynet.be) Received: from [194.78.238.58] (dialup890.brussels2.skynet.be [194.78.238.58]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id AAA10851; Fri, 10 Dec 1999 00:17:42 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Fri, 10 Dec 1999 00:17:26 +0100 To: Julian Elischer , Joe Greco From: Brad Knowles Subject: Re: Route table leaks Cc: Bob Vaughan , freebsd@gndrsh.dnsmgr.net, mike@sentex.net, current@FreeBSD.ORG, jdp@polstra.com, stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:00 PM -0800 1999/12/9, Julian Elischer wrote: > so can it be committed? In -CURRENT, I would say that this could probably be committed, if John feels safe. I am not yet convinced that it should be committed to -STABLE, although things do look good so far. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 15:19: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 3D64F1575B for ; Thu, 9 Dec 1999 15:19:04 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA81926; Thu, 9 Dec 1999 18:18:55 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Thu, 9 Dec 1999 18:24:45 -0500 To: Alfred Perlstein , Andre Albsmeier From: Garance A Drosihn Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Cc: Warner Losh , stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Note: I'm sending this to just the -current list, since it's pretty clear that this change won't be ready for -stable anytime this year... (hopefully Alfred is in -current?) At 3:02 PM -0800 12/9/99, Alfred Perlstein wrote: >On Thu, 9 Dec 1999, Andre Albsmeier wrote: > > On Tue, 07-Dec-1999 at 14:55:37 -0800, Alfred Perlstein wrote: > > > please do not, the patch in PR 11997 introduces a major security flaw. > > > > > > someone can hardlink to any file and clobber it with a file owned by > > > them: > > > > I think the (really big) security hole can be closed by not doing > > the chown/chmod commands. I inserted them because I wanted the > > file in the spool directory to appear exactly as if lpr would > > have copied it. > >I don't have too much time to think about this, argue me this: > > why should I allow a user to print any file on the system? > >the race condition is still there. I think the general goal of the patch is a good idea (ie, doing a 'mv' instead of a 'cp & rm' when we can). And, in fact, I'd like the chown/chmod's to be done so the file is owned and permitted the same way as if it was cp'ed. I don't have any time to really look at the patch right now though (it's end-of-semester, things breaking, students around here in a frenzy, etc, etc). I might try to suggest something this weekend, depending on how things go. I think we can afford to do whatever checking is necessary to get this right, as the checking can't possibly be more expensive than copying the whole file and removing the old one. (in my environment we have people printing thru samba or CAP, and who are sending >100meg files. If I can use 'mv' instead of 'cp', that has to save a lot of cpu time!). Of course, the security implications of such a change are also pretty important in our environment here... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 15:24: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 91FD614D17; Thu, 9 Dec 1999 15:23:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 7E4D01CD742; Thu, 9 Dec 1999 15:23:57 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Thu, 9 Dec 1999 15:23:57 -0800 (PST) From: Kris Kennaway To: "Mr. K." Cc: Christopher Michaels , freebsd-stable@FreeBSD.ORG Subject: RE: 3.2 -> 3.3-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 On Thu, 9 Dec 1999, Mr. K. wrote: > Is there somewhere I can download disk images and to a full network > install? I have a cablemodem so minimal install should be quick and > painless. ftp.freebsd.org? :) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 15:32:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 9606E14D29; Thu, 9 Dec 1999 15:32:39 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id PAA01254; Thu, 9 Dec 1999 15:32:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA39382; Thu, 9 Dec 1999 15:32:38 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 09 Dec 1999 15:32:38 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Brad Knowles Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG, current@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > In -CURRENT, I would say that this could probably be committed, > if John feels safe. I am not yet convinced that it should be > committed to -STABLE, although things do look good so far. Just to clarify, I committed it to -current already this morning. 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 9 15:39:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-29.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.157]) by hub.freebsd.org (Postfix) with ESMTP id 1DE2414CB6 for ; Thu, 9 Dec 1999 15:39:35 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA01918; Thu, 9 Dec 1999 23:39:31 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id HAA00425; Thu, 9 Dec 1999 07:54:48 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912090754.HAA00425@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Dan Diephouse Cc: freebsd-stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: slight PPP problems In-Reply-To: Message from Dan Diephouse of "Wed, 08 Dec 1999 21:28:30 EST." <384F13CD.1A1395A0@ix.netcom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Dec 1999 07:54:48 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello everyone. I have set up PPP over an ISDN modem and it appears to > work well. Unfortunately looks aren't everything. We have to pay for > each > time we dial out on our ISDN modem. I have ppp set on -ddial so the > conection automatically stays up. In my logs it appears to be > disconnecting after a number of packets. I don't know what to make of. > I've attached the logs so you can see for yourself. If anything else > needs > to be include, just notify me. Your logs :-I You forgot to attach them. > Also I have a message at the end of my dmesg conerning "rtinit" that I > haven't investigated yet if anyone would like to enlighten me :) > > Thank You, > > Dan Diephouse > > DMESG: [.....] > rtinit: wrong ifa (0xc19c2000) was (0xc1230380) > rtinit: wrong ifa (0xc1231d00) was (0xc1230080) [.....] This is now fixed in -current. It can safely be ignored. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 16: 0:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 87DA215071 for ; Thu, 9 Dec 1999 16:00:35 -0800 (PST) (envelope-from drosih@rpi.edu) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.9.3/8.9.3) with ESMTP id SAA106814; Thu, 9 Dec 1999 18:57:15 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Thu, 9 Dec 1999 19:03:03 -0500 To: Alfred Perlstein , Andre Albsmeier From: Garance A Drosihn Subject: Re: NO! Re: [PATCHES] Two fixes for lpd/lpc for review and test Cc: Warner Losh , stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 6:24 PM -0500 12/9/99, Garance A Drosihn wrote: >Note: I'm sending this to just the -current list, since it's pretty >clear that this change won't be ready for -stable anytime this year... > >(hopefully Alfred is in -current?) And hopefully my brain will be working this weekend.... The above message was SUPPOSED to go to current, honest! Seems to me that's where it should be discussed, at this point. Arg. I can't believe I wrote that up only to send to the wrong list... --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 9 22:15: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from web1403.mail.yahoo.com (web1403.mail.yahoo.com [128.11.23.167]) by hub.freebsd.org (Postfix) with SMTP id 7249D14FCF for ; Thu, 9 Dec 1999 22:14:58 -0800 (PST) (envelope-from gwq_uk@yahoo.com) Received: (qmail 5579 invoked by uid 60001); 9 Dec 1999 22:39:56 -0000 Message-ID: <19991209223956.5578.qmail@web1403.mail.yahoo.com> Received: from [139.130.59.227] by web1403.mail.yahoo.com; Thu, 09 Dec 1999 14:39:56 PST Date: Thu, 9 Dec 1999 14:39:56 -0800 (PST) From: =?iso-8859-1?q?Greg=20Quinlan?= Subject: Bad Floppy causes Kernel Panic (3.4-RC) To: FreeBSD-stable@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi All, Operating on a cvsup-ed 3.4-RC 10-12-99: I had a bad floppy which I was trying to "tar" to but my server kernel panic-ed with the message: fd0c: hard error writing fsbn .... Dirty Buffers kernel panic etc.... When I have tried to reproduce it (ie. damage a floppy and "tar" to it) I got a similar message but NO panic. I put the original floppy back and "tar"-ed to it again, and the system panic-ed and rebooted. So it was unique to this floppy. When I tried formating the floppy (fdformat) I got: EVVVVVVVVV...... So it appears to be that the very first part of the floppy was bad and this caused the kernel panic. ALSO: The more annoying problem was when I tried tar-ing to the floppy I delibrately damaged. The tar program could not be killed and I was forced to reboot. Thanks Greg __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 0:21:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from lcremeans.erols.com (lcremeans.erols.com [216.164.87.29]) by hub.freebsd.org (Postfix) with ESMTP id 2DD5615085 for ; Fri, 10 Dec 1999 00:21:51 -0800 (PST) (envelope-from lee@lcremeans.erols.com) Received: (from lee@localhost) by lcremeans.erols.com (8.9.3/8.9.3) id DAA03161; Fri, 10 Dec 1999 03:21:38 -0500 (EST) (envelope-from lee) Date: Fri, 10 Dec 1999 03:21:38 -0500 From: Lee Cremeans To: Greg Quinlan Cc: FreeBSD-stable@FreeBSD.ORG Subject: Re: Bad Floppy causes Kernel Panic (3.4-RC) Message-ID: <19991210032138.A3133@lcremeans.erols.com> References: <19991209223956.5578.qmail@web1403.mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991209223956.5578.qmail@web1403.mail.yahoo.com>; from gwq_uk@yahoo.com on Thu, Dec 09, 1999 at 02:39:56PM -0800 X-OS: FreeBSD 3.0-STABLE Organization: My room? Are you crazy? :) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 09, 1999 at 02:39:56PM -0800, Greg Quinlan wrote: > Hi All, > > Operating on a cvsup-ed 3.4-RC 10-12-99: > > I had a bad floppy which I was trying to "tar" to but > my server kernel panic-ed with the message: > > fd0c: hard error writing fsbn .... > Dirty Buffers > > kernel panic > > etc.... > > When I have tried to reproduce it (ie. damage a floppy > and "tar" to it) I got a similar message but NO panic. > > I put the original floppy back and "tar"-ed to it > again, and the system panic-ed and rebooted. So it > was unique to this floppy. > > When I tried formating the floppy (fdformat) I got: > > EVVVVVVVVV...... > > So it appears to be that the very first part of the > floppy was bad and this caused the kernel panic. I've also noticed this when I use bad 1.44MB floppies with my LS-120 drive. THe panic I get, in particular, is panic: vinvalbuf: dirty bufs and my theory is that it's choking because it has dirty bufs it can't write to disk (because of the hard errors). What do people think? I'm running 3.3-STABLE as of about 2 weeks ago. -lee -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | | lcremeans@erols.com | http://wakky.dyndns.org/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 1:24:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 4F9DC15085 for ; Fri, 10 Dec 1999 01:24:31 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id JAA00333; Fri, 10 Dec 1999 09:25:13 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <13992.944768179@cs.ucl.ac.uk> Date: Fri, 10 Dec 1999 09:25:11 -0000 (GMT) From: "Steve O'Hara-Smith" To: Theo PAGTZIS Subject: Re: 3.2 -> 3.3-stable Cc: freebsd-stable , "Chris D. Faulhaber" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 09-Dec-99 Theo PAGTZIS wrote: > > This is definetely a paradox... > > A stable which is not stable...what is it (enigma) ? > > This definitely proves once more my thought about the erroneous of the naming > convention and the semantics behind it..... > > My impression of a stable is that one develops something which has been > tested > to the extent that is stable, i.e won't crash unless you stress it to the > limits (whatever the limits are). Obviously this stable should need more > testing before one can promote it to RC or release candidate..It is only when > the release candidate has matured in terms of bug fixes that it could move up > to a RELEASE merging with the master branch and setting there a revertable > milestone. From release one could then spawn a new branch that would move for > the next version of stable---RC-----Release. In other words: > > 1) ----- (proposed) REL 3.2-----Stable 3.3-----RC 3.3----REL 3.3---Stable > 3.4---RC 3.4---REL 3.4---etc.. > whereas now the scheme is > > 2) ------ (currently) REL 3.2----Stable 3.2---RC 3.3---REL 3.3---Stable > 3.3----RC 3.4---REL 3.4---Stable 3.4----etc.. > Now look the situation of the crash of the stable 3.3 and try to place it in > one of the two schemes...which one is more reasonable for you...?????? The two schemes are identical apart from the name used between release and subsequent release candidate. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 1:40:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id E998115217 for ; Fri, 10 Dec 1999 01:40:21 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id EAA02248; Fri, 10 Dec 1999 04:40:18 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id EAA04222; Fri, 10 Dec 1999 04:40:16 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id EAA74144; Fri, 10 Dec 1999 04:40:16 -0500 (EST) Date: Fri, 10 Dec 1999 04:40:16 -0500 (EST) From: Thomas David Rivers Message-Id: <199912100940.EAA74144@lakes.dignus.com> To: FreeBSD-stable@FreeBSD.ORG, gwq_uk@yahoo.com Subject: Re: Bad Floppy causes Kernel Panic (3.4-RC) In-Reply-To: <19991209223956.5578.qmail@web1403.mail.yahoo.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm... I was just thinking - BAD144 had been (or will be) removed from 4.0. But, as floppy sizes increase, with say, an LS120 - does it make sense to keep bad144 to handle filesystems here? - Just a thought - - Dave Rivers - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 2:29:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 1299E15372; Fri, 10 Dec 1999 02:29:30 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id LAA20403; Fri, 10 Dec 1999 11:28:59 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Fri, 10 Dec 1999 11:28:43 +0100 To: Julian Elischer , Joe Greco From: Brad Knowles Subject: Re: Route table leaks Cc: Bob Vaughan , freebsd@gndrsh.dnsmgr.net, mike@sentex.net, current@FreeBSD.ORG, jdp@polstra.com, stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:17 AM +0100 1999/12/10, Brad Knowles wrote: > In -CURRENT, I would say that this could probably be committed, > if John feels safe. I am not yet convinced that it should be > committed to -STABLE, although things do look good so far. Well, things continue to look good: Fri Dec 10 10:59:55 CET 1999 netstat -ran | wc -l 121 vmstat -m | grep routetbl | grep K routetbl 246 34K 35K 40960K 275 0 0 16,32,64,128,256 uptime 10:59AM up 16:08, 0 users, load averages: 3.49, 3.83, 3.61 Fri Dec 10 11:00:56 CET 1999 netstat -ran | wc -l 120 vmstat -m | grep routetbl | grep K routetbl 244 34K 35K 40960K 275 0 0 16,32,64,128,256 uptime 11:00AM up 16:09, 0 users, load averages: 3.41, 3.81, 3.62 Looking at our stats for yesterday on this machine, we came pretty close to setting some new records for volume, and did quite a lot of articles. At this stage, given that this patch has fixed John's problems, that the previous patch appears to have fixed Joe's problems, and that I seem to be running fine after almost a day, I'd feel more comfortable if John decides he wants to commit this patch to -STABLE. When that happens, I'll cvsup & rebuild all the machines I can, so that they can all get the benefit of this patch and the other changes that have gone in recently. Thanks! -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 4:57:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id AEA3A1528B for ; Fri, 10 Dec 1999 04:57:40 -0800 (PST) (envelope-from will@blackdawn.com) Received: (from will@localhost) by blackdawn.com (8.9.3/8.9.3) id HAA00451; Fri, 10 Dec 1999 07:57:32 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 10 Dec 1999 07:57:32 -0500 (EST) From: will andrews To: luserboy@NetScum.dK Subject: RE: Console mouse cut'n'paste sometimes is ... well... Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 08-Dec-99 Anonymous Coward wrote: > > Hellø¸_ãll_ýøu_kewl_hãcker_ð00ðZ! You know, I'm not even going to bother reading the rest of this email. Perhaps next time you will make it legible. I could kick your ass in ebonics any day, anyway. :-) -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? P.S. This is hackerville, not crackerville. Go back where you belong. ;> To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 5:15:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from thoth.mch.sni.de (thoth.mch.sni.de [192.35.17.2]) by hub.freebsd.org (Postfix) with ESMTP id CF6AE1539D for ; Fri, 10 Dec 1999 05:15:45 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer thoth.mch.sni.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by thoth.mch.sni.de (8.9.3/8.9.3) with ESMTP id OAA04627 for ; Fri, 10 Dec 1999 14:15:43 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.9.3/8.9.3) with ESMTP id OAA12499 for ; Fri, 10 Dec 1999 14:15:42 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.9.3/8.9.3) id OAA23654 for ; Fri, 10 Dec 1999 14:15:42 +0100 (CET) Date: Fri, 10 Dec 1999 14:15:41 +0100 From: Andre Albsmeier To: freebsd-stable@freebsd.org Subject: /kernel: dscheck: negative b_blkno -222114604 Message-ID: <19991210141541.A17098@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Found the following error messages today on 3.4-RC: Dec 10 13:58:20 paul /kernel: dscheck: negative b_blkno -222114604 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -222114604 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -1297179414 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -222114604 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -1297179414 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -222114604 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -1297179414 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -222114604 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -1297179414 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -222114604 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -1297179414 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -222114604 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -1297179414 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -222114604 Dec 10 13:58:21 paul /kernel: dscheck: negative b_blkno -1297179414 Unfortunately, I don't know what this is realted to (apart from that the message is generated in sys/kern/subr_diskslice.c). I there something wrong with my partitions ?!? The machine runs well for quite a long time now. Can someone enlighten me where I have to start digging ? The dmesg is appended but I doubt it will help... Thanks, -Andre Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.4-RC #1: Thu Dec 9 19:22:48 CET 1999 root@bali.ofw.tld:/src/src-3/sys/compile/PAUL Timecounter "i8254" frequency 1193195 Hz Timecounter "TSC" frequency 463556016 Hz CPU: Pentium III (463.56-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x672 Stepping = 2 Features=0x383f9ff> real memory = 268435456 (262144K bytes) avail memory = 258519040 (252460K bytes) Preloaded elf kernel "kernel" at 0xc02a3000. Pentium Pro MTRR support enabled Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x02 on pci0.1.0 chip2: rev 0x02 on pci0.4.0 chip3: rev 0x02 on pci0.4.3 fxp0: rev 0x05 int a irq 10 on pci0.7.0 fxp0: Ethernet address 00:e0:18:90:93:4f ahc0: rev 0x00 int a irq 12 on pci0.9.0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 11 on pci0.11.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <9 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface ccd0: Concatenated disk driver sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) da14 at ahc1 bus 0 target 4 lun 0 da14: Fixed Direct Access SCSI-2 device da14: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da14: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) changing root device to da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 1034MB (2118144 512 byte sectors: 255H 63S/T 131C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 22130MB (45322644 512 byte sectors: 255H 63S/T 2821C) ch0 at ahc0 bus 0 target 4 lun 1 ch0: Removable Changer SCSI-2 device ch0: 10.000MB/s transfers (10.000MHz, offset 15) ch0: 7 slots, 1 drive, 1 picker, 0 portals cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da10 at ahc1 bus 0 target 0 lun 0 da10: Fixed Direct Access SCSI-2 device da10: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da10: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da12 at ahc1 bus 0 target 2 lun 0 da12: Fixed Direct Access SCSI-2 device da12: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da12: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da13 at ahc1 bus 0 target 3 lun 0 da13: Fixed Direct Access SCSI-2 device da13: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da13: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) da11 at ahc1 bus 0 target 1 lun 0 da11: Fixed Direct Access SCSI-2 device da11: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da11: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 dscheck: negative b_blkno -222114604 dscheck: negative b_blkno -1297179414 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 5:41:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id AA97215499; Fri, 10 Dec 1999 05:41:16 -0800 (PST) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-p2-68.hitter.net [207.192.76.68]) by pawn.primelocation.net (Postfix) with ESMTP id 834129B1C; Fri, 10 Dec 1999 08:41:13 -0500 (EST) Date: Fri, 10 Dec 1999 08:41:12 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: jkh@freebsd.org, stable@freebsd.org Subject: 3.4-RC sysinstall oddity 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 While playing with /stand/sysinstall this morning, I noticed the following oddity: wd0s1 3004MB DOS d0s2a 256MB * d0s2b swap 256MB SWAP d0s2e 512MB * d0s2f 1533MB * d0s3e /mnt/tmp 2494MB UFS Y The first character of the first column (after the first row) is always missing... Verified on multiple machines by executing /stand/sysinstall and installing from the floppies from 'make release'. This is from sources as of 18:30 EST last two nights. This does not occur from sources as of Dec 1, 00:00 (prior to last RELENG_3 commit to /usr/src/release/sysinstall). ----- Chris D. Faulhaber | You can ISO9001 certify the process of System/Network Administrator, | shooting yourself in the foot, so long Reality Check Information, Inc. | as the process is documented and reliably | produces the proper result. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 7:18: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns1.sprawlnet.com (ns1.sprawlnet.com [208.224.169.130]) by hub.freebsd.org (Postfix) with ESMTP id F0D4815026 for ; Fri, 10 Dec 1999 07:17:58 -0800 (PST) (envelope-from mike@sprawlnet.com) Received: from jedi (jedi.sprawlnet.com [208.224.169.134]) by ns1.sprawlnet.com (8.9.3/8.9.2) with SMTP id XAA70121; Fri, 10 Dec 1999 23:19:58 -0500 (EST) (envelope-from mike@sprawlnet.com) Message-ID: <001601bf4321$75312500$86a9e0d0@sprawlnet.com> From: "Michael Steinfeld" To: Cc: References: Subject: Re: Console mouse cut'n'paste sometimes is ... well... Date: Fri, 10 Dec 1999 10:15:56 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG No shit, it just makes think of whats to become seeing more and more idiots subscribing to this list. or running FreeBSD for that matter. you cant steal away my innocense, but you can't take away my pride. ----- Original Message ----- From: will andrews To: Cc: Sent: Friday, December 10, 1999 7:57 AM Subject: RE: Console mouse cut'n'paste sometimes is ... well... > On 08-Dec-99 Anonymous Coward wrote: > > > > Hellø¸_ãll_ýøu_kewl_hãcker_ð00ðZ! > > You know, I'm not even going to bother reading the rest of this email. Perhaps > next time you will make it legible. I could kick your ass in ebonics any day, > anyway. :-) > > -- > Will Andrews > GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- > ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ > G++>+++ e->++++ h! r-->+++ y? > > P.S. This is hackerville, not crackerville. Go back where you belong. ;> > > > 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 10 7:28:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from localhost.cproject.com (premium129.dnvr.uswest.net [206.196.132.129]) by hub.freebsd.org (Postfix) with SMTP id 539CD1503B for ; Fri, 10 Dec 1999 07:28:52 -0800 (PST) (envelope-from jhanna@cproject.com) Received: (qmail 872 invoked by uid 83); 10 Dec 1999 15:28:25 -0000 Received: from unknown (HELO dv2000.omfus.org) (10.1.1.43) by larryboy with SMTP; 10 Dec 1999 15:28:25 -0000 Message-ID: <002201bf4323$37982f20$2b01010a@omfus.org> From: "John Hanna" To: References: Subject: Dump locked up my FreeBSD 3.3 Date: Fri, 10 Dec 1999 08:28:27 -0700 Organization: Caleb Project MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I run dump nightly to backup my files to a second disk, something like this: dump -0 -a -f - / |gzip >/backup/larryboy/larryboy.root.dump.gz dump -0 -a -f - /usr |gzip >/backup/larryboy/larryboy.usr.dump.gz Last night in the middle of this process the system locked up. I had to push the reset key this morning to bring it back. UUCICO was also running about the same time as the backup. Anyone heard of this before? Is fileaccess in the middle of a dump bad? Thanks, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 8: 6: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id E631B1508F; Fri, 10 Dec 1999 08:06:03 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 0A2ED1C4A; Fri, 10 Dec 1999 11:05:58 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id F024A381B; Fri, 10 Dec 1999 11:05:58 -0500 (EST) Date: Fri, 10 Dec 1999 11:05:58 -0500 (EST) From: Bill Fumerola To: "Chris D. Faulhaber" Cc: jkh@freebsd.org, stable@freebsd.org Subject: Re: 3.4-RC sysinstall oddity 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 Fri, 10 Dec 1999, Chris D. Faulhaber wrote: > The first character of the first column (after the first row) is always > missing... Verified on multiple machines by executing /stand/sysinstall > and installing from the floppies from 'make release'. This is from sources > as of 18:30 EST last two nights. This behavior occurs in 4.0-CURRENT as well. -- - bill fumerola - billf@chc-chimes.com - BF1560 - computer horizons corp - - ph:(800) 252-2421 - bfumerol@computerhorizons.com - billf@FreeBSD.org - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 8:22: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from unicorn.blackhats.org (unicorn.blackhats.org [194.109.83.155]) by hub.freebsd.org (Postfix) with ESMTP id C88DC158CC; Fri, 10 Dec 1999 08:21:52 -0800 (PST) (envelope-from unicorn@blackhats.org) Received: by unicorn.blackhats.org (Postfix, from userid 1002) id A71D212C24; Fri, 10 Dec 1999 17:19:56 +0100 (CET) Date: Fri, 10 Dec 1999 17:19:56 +0100 From: The Unicorn To: freebsd-stable@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Some (minor) problems with ports on 3.4-RC Message-ID: <19991210171956.Y528@unicorn.blackhats.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i X-Files: The Truth Is Out There! Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Guys (F/M), I guess this must go to both stable and ports, since it is also important to include a properly working ports collection on the next CDROM Release. While updating some ports I came across the following: l0pht-watch 1.1 MD5 checksum mismatch and Makefile not working at all. Can be installed by hand. lsof 4.48A Makefile refers to 4.47 version and 3.4(-RC) not recognised. Wanted to build 2.x version. Some minor hacking enabled me to install a 3.3 version without problems. xpdf 0.90 Depends on t1lib. The configure script wants to check if an underscore is needed for external symbols. LIB variable is (temp) changed, but instead of adding an object (.o) the assembly (.s) file name is added. xwhois 0.3.9 MD5 checksum mismatch and Makefile not working at all. Can be installed by hand. Ciao, Unicorn. -- ======= _ __,;;;/ TimeWaster ================================================ ,;( )_, )~\| A Truly Wise Man Never Plays PGP: 64 07 5D 4C 3F 81 22 73 ;; // `--; Leapfrog With A Unicorn... 52 9D 87 08 51 AA 35 F0 ==='= ;\ = | ==== Youth is Not a Time in Life, It is a State of Mind! ======= Echelon Teasers: NSA CIA FBI Mossad BVD MI5 Cocaine Cuba Revolution Espionage To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 8:43:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtpc.casema.net (smtpc.casema.net [195.96.96.200]) by hub.freebsd.org (Postfix) with SMTP id 70BBD15839 for ; Fri, 10 Dec 1999 08:43:11 -0800 (PST) (envelope-from djmuggs@casema.net) Received: (qmail 398 invoked by uid 0); 10 Dec 1999 16:43:05 -0000 Received: from 1dyn203.maarssen.casema.net (HELO casema.net) (212.64.52.203) by smtpc.casema.net with SMTP; 10 Dec 1999 16:43:05 -0000 Message-ID: <38512C1E.1B8EDC26@casema.net> Date: Fri, 10 Dec 1999 17:36:46 +0100 From: DJMuggs X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-stable@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=iso-8859-15 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 9:15:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 8269E14DC7; Fri, 10 Dec 1999 09:15:45 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 7BDF11C4A; Fri, 10 Dec 1999 12:15:40 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 6D9B9381B; Fri, 10 Dec 1999 12:15:40 -0500 (EST) Date: Fri, 10 Dec 1999 12:15:40 -0500 (EST) From: Bill Fumerola To: The Unicorn Cc: freebsd-stable@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: Some (minor) problems with ports on 3.4-RC In-Reply-To: <19991210171956.Y528@unicorn.blackhats.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 On Fri, 10 Dec 1999, The Unicorn wrote: > xwhois 0.3.9 MD5 checksum mismatch and Makefile not working at all. > Can be installed by hand. This was already fixed by me, please update your tree. -- - 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 Fri Dec 10 13: 5:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id B39BF14BC3; Fri, 10 Dec 1999 13:05:20 -0800 (PST) (envelope-from will@blackdawn.com) Received: (from will@localhost) by blackdawn.com (8.9.3/8.9.3) id QAA51359; Fri, 10 Dec 1999 16:03:29 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991210171956.Y528@unicorn.blackhats.org> Date: Fri, 10 Dec 1999 16:03:29 -0500 (EST) From: will andrews To: The Unicorn Subject: RE: Some (minor) problems with ports on 3.4-RC Cc: freebsd-ports@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 10-Dec-99 The Unicorn wrote: > l0pht-watch 1.1 MD5 checksum mismatch and Makefile not working at all. > Can be installed by hand. I think I saw a commit on cvs-all for this.. > lsof 4.48A Makefile refers to 4.47 version and 3.4(-RC) not > recognised. Wanted to build 2.x version. Some minor > hacking enabled me to install a 3.3 version without > problems. I believe David O'Brien already updated this port. You need to update your ports tree, methinks. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 13:33:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id 4B5CE14DAD for ; Fri, 10 Dec 1999 13:33:10 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id NAA10060 for ; Fri, 10 Dec 1999 13:32:53 -0800 (PST) Date: Fri, 10 Dec 1999 13:32:53 -0800 (PST) From: Annelise Anderson To: freebsd-stable@freebsd.org Subject: 3.4-RC ISO? 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 suppose the 3.3-19991210-STABLE.iso at cvsup.freebsd.org is equivalent to the latest available 3.4-RC, if someone wanted to try downloading it, burning it, and installing? Isn't this the sort of thing that needs to be tested? Annelise To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 13:36:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from andrsn.stanford.edu (andrsn.Stanford.EDU [36.33.0.163]) by hub.freebsd.org (Postfix) with ESMTP id EF5B2153E2 for ; Fri, 10 Dec 1999 13:36:43 -0800 (PST) (envelope-from andrsn@andrsn.stanford.edu) Received: from localhost (andrsn@localhost.stanford.edu [127.0.0.1]) by andrsn.stanford.edu (8.9.3/8.9.1) with ESMTP id NAA10079 for ; Fri, 10 Dec 1999 13:36:22 -0800 (PST) Date: Fri, 10 Dec 1999 13:36:22 -0800 (PST) From: Annelise Anderson To: freebsd-stable@freebsd.org Subject: Re: 3.4-RC ISO? 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 Sorry, it's at current.freebsd.org. A On Fri, 10 Dec 1999, Annelise Anderson wrote: > I suppose the 3.3-19991210-STABLE.iso at cvsup.freebsd.org > is equivalent to the latest available 3.4-RC, if someone wanted to > try downloading it, burning it, and installing? Isn't this the sort > of thing that needs to be tested? > > Annelise > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 14:26:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 3713D152A9 for ; Fri, 10 Dec 1999 14:26:47 -0800 (PST) (envelope-from pekkas@netcore.fi) Received: from localhost (pekkas@localhost) by netcore.fi (8.9.3/8.9.3) with ESMTP id AAA11858 for ; Sat, 11 Dec 1999 00:26:46 +0200 Date: Sat, 11 Dec 1999 00:26:46 +0200 (EET) From: Pekka Savola To: freebsd-stable@freebsd.org Subject: /usr/src/contrib/ipfilter way outdated 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 Hello all, After installing 3.3-release yesterday, I ran cvsup today to upgrade it to 3.3-stable. That went fine. Make world, however, crashed the whole process: -------- ===> usr.sbin/ipfstat cc -nostdinc -O -pipe -DIPL_NAME=\"/dev/ipl\" -I- -I/usr/src/usr.sbin/ipfstat/../../sys/netinet -I/usr/src/usr.sbin/ipfstat/../../sys -I/usr/src/usr.sbin/ipfstat/../../contrib/ipfilter -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/ipfstat/../../contrib/ipfilter/fils.c In file included from /usr/src/usr.sbin/ipfstat/../../contrib/ipfilter/fils.c:35: /usr/src/usr.sbin/ipfstat/../../sys/netinet/ip_fil.h:427: warning: `struct ifnet' declared inside parameter list /usr/src/usr.sbin/ipfstat/../../sys/netinet/ip_fil.h:427: warning: its scope is only this definition or declaration, /usr/src/usr.sbin/ipfstat/../../sys/netinet/ip_fil.h:427: warning: which is probably not what you want. /usr/src/usr.sbin/ipfstat/../../sys/netinet/ip_fil.h:428: warning: `struct ifnet' declared inside parameter list /usr/src/usr.sbin/ipfstat/../../contrib/ipfilter/fils.c: In function `showipstates': /usr/src/usr.sbin/ipfstat/../../contrib/ipfilter/fils.c:395: structure has no member named `is_seq' /usr/src/usr.sbin/ipfstat/../../contrib/ipfilter/fils.c:395: structure has no member named `is_ack' /usr/src/usr.sbin/ipfstat/../../contrib/ipfilter/fils.c:396: structure has no member named `is_swin' /usr/src/usr.sbin/ipfstat/../../contrib/ipfilter/fils.c:396: structure has no member named `is_dwin' /usr/src/usr.sbin/ipfstat/../../contrib/ipfilter/fils.c: In function `showfrstates': /usr/src/usr.sbin/ipfstat/../../contrib/ipfilter/fils.c:477: structure has no member named `ipfr_pass' ----------- When I went around to poke /usr/src/usr.sbin/ipfstat and friends plus /usr/src/contrib/ipfilter (to which those referred to), I noticed these were from May 1998 (ipfilter 3.2.7)! What is the point of not updating this at all ?? I tried replacing /usr/src/contrib/ipfilter with the latest version, but it wouldn't compile from /usr/src/usr.sbin/ipf* (using the commands as described in ipfilter documentation it worked fine), so I guess those Makefiles should have been changed too. Btw, ipfilter's ipmon coredumps on me right in the beginning - has anyone else experienced this ? HTH, Regards, Pekka Savola To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 15:33:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id A3F0B15454; Fri, 10 Dec 1999 15:33:27 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 8BE0C1CD7A3; Fri, 10 Dec 1999 15:33:27 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 10 Dec 1999 15:33:27 -0800 (PST) From: Kris Kennaway To: Pekka Savola Cc: freebsd-stable@freebsd.org Subject: Re: /usr/src/contrib/ipfilter way outdated 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 Sat, 11 Dec 1999, Pekka Savola wrote: > /usr/src/contrib/ipfilter (to which those referred to), I noticed these > were from May 1998 (ipfilter 3.2.7)! > > What is the point of not updating this at all ?? There was no-one willing/able to maintain it for a very long time. This has now changed and -current has the latest version in it, which might make it back to 3.x after the release of 3.4. Talk to Guido van Rooij (guido@freebsd.org) if you want to know his plans. However, it should still compile in -stable: I'd suspect there's something wrong with your source tree. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 15:33:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 975A914DE5; Fri, 10 Dec 1999 15:33:57 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 84F7D1CD425; Fri, 10 Dec 1999 15:33:57 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Fri, 10 Dec 1999 15:33:57 -0800 (PST) From: Kris Kennaway To: Annelise Anderson Cc: freebsd-stable@freebsd.org Subject: Re: 3.4-RC ISO? 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 Fri, 10 Dec 1999, Annelise Anderson wrote: > I suppose the 3.3-19991210-STABLE.iso at cvsup.freebsd.org > is equivalent to the latest available 3.4-RC, if someone wanted to > try downloading it, burning it, and installing? Isn't this the sort > of thing that needs to be tested? Yep and yep. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 15:40:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from red.juniper.net (red.juniper.net [208.197.169.254]) by hub.freebsd.org (Postfix) with ESMTP id 875711541F for ; Fri, 10 Dec 1999 15:39:58 -0800 (PST) (envelope-from laotzu@juniper.net) Received: from leaf.juniper.net (leaf.juniper.net [208.197.169.211]) by red.juniper.net (8.8.8/8.8.5) with ESMTP id PAA05105 for ; Fri, 10 Dec 1999 15:39:58 -0800 (PST) Received: (from laotzu@localhost) by leaf.juniper.net (8.9.3/8.9.3) id PAA63774 for stable@freebsd.org; Fri, 10 Dec 1999 15:39:57 -0800 (PST) (envelope-from laotzu) Date: Fri, 10 Dec 1999 15:39:57 -0800 From: Chris Parry To: stable@freebsd.org Subject: make world woes Message-ID: <19991210153957.C97629@juniper.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i X-Operating-System: FreeBSD leaf.juniper.net 3.2-STABLE FreeBSD 3.2-STABLE Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, just a sanity check, has anyone done a recent (last 24 hours) make buildworld? I crash at: cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 isofs/cd9660/*.h /usr/obj/usr/src/tmp/usr/include/isofs/cd9660 cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 ufs/ffs/*.h /usr/obj/usr/src/tmp/usr/include/ufs/ffs install: ufs/ffs/softdep.h: No such file or directory *** Error code 71 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. Thanks! -chris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 15:43:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.alpha1.net (mail.alpha1.net [216.88.112.3]) by hub.freebsd.org (Postfix) with ESMTP id 27A3E14A14 for ; Fri, 10 Dec 1999 15:42:12 -0800 (PST) (envelope-from marius@alpha1.net) Received: from beaker.alpha1.net (beaker.alpha1.net [216.88.237.14]) by mail.alpha1.net (8.9.3/8.9.3) with ESMTP id RAA21610; Fri, 10 Dec 1999 17:42:09 -0600 Date: Fri, 10 Dec 1999 17:42:09 -0600 (CST) From: Marius Strom To: Chris Parry Cc: stable@FreeBSD.ORG Subject: Re: make world woes In-Reply-To: <19991210153957.C97629@juniper.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 Look at the README.softupdates as denoted by the LINT file, you're answer is there. -- Marius Strom Professional Geek/Unix System Administrator Alpha1 Internet http://www.marius.org/marius.pgp 0x5645C228 In theory, there is no difference between theory and practice... ...In practice, there is a big difference. On Fri, 10 Dec 1999, Chris Parry wrote: > Hi all, just a sanity check, has anyone done a recent (last 24 hours) make > buildworld? I crash at: > > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 > isofs/cd9660/*.h /usr/obj/usr/src/tmp/usr/include/isofs/cd9660 > cd /usr/src/include/../sys; install -C -o root -g wheel -m 444 > ufs/ffs/*.h /usr/obj/usr/src/tmp/usr/include/ufs/ffs > install: ufs/ffs/softdep.h: No such file or directory > *** Error code 71 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Stop. > > > Thanks! > > -chris > > > 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 10 16:55:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 88F72153FB for ; Fri, 10 Dec 1999 16:55:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA01676; Fri, 10 Dec 1999 16:57:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912110057.QAA01676@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Thomas David Rivers Cc: FreeBSD-stable@FreeBSD.ORG, gwq_uk@yahoo.com Subject: Re: Bad Floppy causes Kernel Panic (3.4-RC) In-reply-to: Your message of "Fri, 10 Dec 1999 04:40:16 EST." <199912100940.EAA74144@lakes.dignus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 10 Dec 1999 16:57:12 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > Hmm... I was just thinking - BAD144 had been (or will be) removed > from 4.0. > > But, as floppy sizes increase, with say, an LS120 - does it make > sense to keep bad144 to handle filesystems here? No. LS120 drives do their own defect management. (So do the Zip drives, before anyone asks.) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 17: 2:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 4431014E10 for ; Fri, 10 Dec 1999 17:01:13 -0800 (PST) (envelope-from brameld@twave.net) Received: from [208.219.234.42] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id la349217 for ; Fri, 10 Dec 1999 20:00:44 -0500 Message-ID: <3851A26A.3C52FCCA@twave.net> Date: Fri, 10 Dec 1999 20:01:30 -0500 From: Walter Brameld X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: Michael Steinfeld Cc: luserboy@NetScum.dk, stable@freebsd.org Subject: Re: Console mouse cut'n'paste sometimes is ... well... References: <001601bf4321$75312500$86a9e0d0@sprawlnet.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Steinfeld wrote: > No shit, it just makes think of whats to become seeing more and more idiots > subscribing to this list. > or running FreeBSD for that matter. > > you cant steal away my innocense, but you can't take away my pride. > > ----- Original Message ----- > From: will andrews > To: > Cc: > Sent: Friday, December 10, 1999 7:57 AM > Subject: RE: Console mouse cut'n'paste sometimes is ... well... > > > On 08-Dec-99 Anonymous Coward wrote: > > > > > > Hellø¸_ãll_ýøu_kewl_hãcker_ð00ðZ! > > > > You know, I'm not even going to bother reading the rest of this email. > Perhaps > > next time you will make it legible. I could kick your ass in ebonics any > day, > > anyway. :-) > > > > -- > > Will Andrews > > GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- > > ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ > > G++>+++ e->++++ h! r-->+++ y? > > > > P.S. This is hackerville, not crackerville. Go back where you belong. ;> > > > > > > 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 But.....but.....I'm an idiot! The whole point in moving to FreeBSD was to try and become less of one. So far, no good 8-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 23:27:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id 2EF4114F43 for ; Fri, 10 Dec 1999 23:27:32 -0800 (PST) (envelope-from williamsl@Home.Com) Received: from RELIABLE ([24.4.115.31]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991211072730.OIKH17996.mail.rdc1.tn.home.com@RELIABLE> for ; Fri, 10 Dec 1999 23:27:30 -0800 Date: Sat, 11 Dec 1999 02:25:35 -0500 From: Ben WIlliams X-Mailer: The Bat! (v1.34a) UNREG / CD5BF9353B3B7091 Reply-To: Ben WIlliams X-Priority: 3 (Normal) Message-ID: <7101.991211@Home.Com> To: freebsd-stable@FreeBSD.ORG Subject: pidentd 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 freebsd-stable, Saturday, December 11, 1999 I am trying to get pidentd (or any other ident daemon) to work for masqueraded hosts on a private LAN connected to the internet via a 3.2-RELEASE box. I've managed to successfully compile and install pidentd which works as a standard ident daemon but I am having difficulty figuring out how to make it work for masq'd hosts. Any ideas? -- Ben mailto:williamsl@Home.Com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 10 23:47:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 7230314E01 for ; Fri, 10 Dec 1999 23:47:19 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA02916; Sat, 11 Dec 1999 02:33:57 -0500 Date: Sat, 11 Dec 1999 02:33:57 -0500 (EST) From: Mike Nowlin To: "Jordan K. Hubbard" Cc: Andrew Boothman , stable@FreeBSD.ORG Subject: Re: Anticipated release date for 3.4 In-Reply-To: <2339.944529283@zippy.cdrom.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 > Estimated? December 23rd. Or maybe December 27th, depending on > how we do at getting it in before the holidays start. Naaahh.... December 25th -- Santa's gonna leave a CD in my stocking... :) 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 11 3:54:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 75A1D14EE0; Sat, 11 Dec 1999 03:54:32 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA90412; Sat, 11 Dec 1999 03:54:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Chris D. Faulhaber" Cc: jkh@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 3.4-RC sysinstall oddity In-reply-to: Your message of "Fri, 10 Dec 1999 08:41:12 EST." Date: Sat, 11 Dec 1999 03:54:50 -0800 Message-ID: <90408.944913290@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > While playing with /stand/sysinstall this morning, I noticed the following > oddity: Reproduced, thanks, I must have been more sleepy than usual there. :) I'll commit a fix shortly. I'm a bit sleepy right now, too. - 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 11 6: 5:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id CB68814DF1 for ; Sat, 11 Dec 1999 06:05:37 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id GAA12929; Sat, 11 Dec 1999 06:05:36 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id GAA00409; Sat, 11 Dec 1999 06:05:35 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 11 Dec 1999 06:05:35 -0800 (PST) Message-Id: <199912111405.GAA00409@vashon.polstra.com> To: blk@skynet.be Subject: Re: Route table leaks In-Reply-To: References: <199912091829.KAA38057@vashon.polstra.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Brad Knowles wrote: > > Things continue to look good: Thanks for testing it, guys. Jordan gave me permission, and I merged the fix into the -stable branch. It will be in 3.4-RELEASE. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 6: 7:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 1650D14FC6 for ; Sat, 11 Dec 1999 06:07:42 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id GAA12941; Sat, 11 Dec 1999 06:07:38 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id GAA00429; Sat, 11 Dec 1999 06:07:38 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 11 Dec 1999 06:07:38 -0800 (PST) Message-Id: <199912111407.GAA00429@vashon.polstra.com> To: noway@nohow.demon.co.uk Subject: Re: 3.2 -> 3.3-stable In-Reply-To: References: Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article , Jose Marques wrote: > I would like to use CVSup to bring a machine currently running FreeBSD > 3.2-RELEASE up to 3.3-stable. Are there any "gotchas" that I should be > aware of? Yes. Read the CVSup FAQ, especially the "Recipes" section. http://www.polstra.com/projects/freeware/CVSup/faq.html John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 7:20:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hemorrhage.mindcrash.com (hemorrhage.mindcrash.com [209.51.189.194]) by hub.freebsd.org (Postfix) with ESMTP id CD5B714A0B for ; Sat, 11 Dec 1999 07:20:54 -0800 (PST) (envelope-from sheepman@mindcrash.com) Received: from localhost (sheepman@localhost) by hemorrhage.mindcrash.com (8.9.3/MindCrash-Custom-v2.4) with ESMTP id KAA22349; Sat, 11 Dec 1999 10:22:30 -0500 (EST) Date: Sat, 11 Dec 1999 10:22:30 -0500 (EST) From: Sheepman To: Ben WIlliams Cc: freebsd-stable@FreeBSD.ORG Subject: Re: pidentd In-Reply-To: <7101.991211@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 Ben, When I set up masq'ing awhile back I used a different ident daemon. I did not use pidentd. I think maybe it was cidentd, but I am not sure. It was specifically for ip masqing. Hope this helps a smidge. :) Al On Sat, 11 Dec 1999, Ben WIlliams wrote: > freebsd-stable, Saturday, December 11, 1999 > > I am trying to get pidentd (or any other ident daemon) to work for > masqueraded hosts on a private LAN connected to the internet via a > 3.2-RELEASE box. I've managed to successfully compile and install > pidentd which works as a standard ident daemon but I am having > difficulty figuring out how to make it work for masq'd hosts. Any > ideas? > > -- > Ben mailto:williamsl@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 Sat Dec 11 10:26: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [130.126.8.20]) by hub.freebsd.org (Postfix) with ESMTP id B94A214FB0 for ; Sat, 11 Dec 1999 10:26:03 -0800 (PST) (envelope-from igor@alecto.physics.uiuc.edu) Received: (from igor@localhost) by alecto.physics.uiuc.edu (8.9.0/8.9.0) id MAA01536 for stable@freebsd.org; Sat, 11 Dec 1999 12:26:02 -0600 (CST) From: Igor Roshchin Message-Id: <199912111826.MAA01536@alecto.physics.uiuc.edu> Subject: problem with wtmp in 3.x family To: stable@freebsd.org Date: Sat, 11 Dec 1999 12:26:02 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I am not sure if this problem has been discussed here, but I could not find it in the archives, although I know a few people besides me who observed this problem. There is a bug which seems to exist in the 3.x family of FreeBSD. I haven't seen it in 2.x, and I observe it on a 3.1-stable (19990412) box, as well as on a 3.3-RELEASE box. The problem observed is as follows: 1. The record in wtmp file is not updated properly. This seems to be happening when the connection dies (e.g. "reset by peer"), say, when a people connected from a ppp-via-dialup host gets kicked off by a modem, and the connection is not disconneted properly. Initial connection could be established via ssh or via telnet - this does not seem to play any role, although I did not do a detailed research on this issue. 2. The utmp record is not updated either. So, "w" shows a person being logged in, even though there are no processes running on that tty. (accordingly w shows "-" as a current process). When somebody else logs in on that tty, the utmp record is updated, but not the wtmp one. In most cases, if not in all, the users use "screen". I am not sure if the use of screen is necessary condition or just a coinsidence. Please, Cc: to me, because I am not currently subscribed to this list. Regards, Igor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 11: 1:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from posgate.acis.com.au (posgate.acis.com.au [203.14.230.14]) by hub.freebsd.org (Postfix) with ESMTP id 24A4B150AC for ; Sat, 11 Dec 1999 11:01:29 -0800 (PST) (envelope-from andymac@bullseye.apana.org.au) Received: from bullseye.apana.org.au (uucp@localhost) by posgate.acis.com.au (8.9.3/8.9.3) with UUCP id GAA04191; Sun, 12 Dec 1999 06:01:11 +1100 Received: from bullseye.apana.org.au (central.apana.org.au [203.9.107.245]) by bullseye.apana.org.au (8.8.8/8.8.8) with SMTP id WAA11460; Sat, 11 Dec 1999 22:11:35 +1100 (EST) (envelope-from andymac@bullseye.apana.org.au) Date: Sat, 11 Dec 1999 21:05:08 +1100 (EDT) From: Andrew MacIntyre To: Thomas David Rivers Cc: FreeBSD-stable@FreeBSD.ORG, gwq_uk@yahoo.com Subject: Re: Bad Floppy causes Kernel Panic (3.4-RC) In-Reply-To: <199912100940.EAA74144@lakes.dignus.com> Message-ID: X-X-Sender: andymac@bullseye.apana.org.au 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, 10 Dec 1999, Thomas David Rivers wrote: > But, as floppy sizes increase, with say, an LS120 - does it make > sense to keep bad144 to handle filesystems here? Won't help if floppy is accessed as raw media (such as the original poster's tar problem situation appeared to be). -- Andrew I MacIntyre "These thoughts are mine alone..." E-mail: andrew.macintyre@aba.gov.au (work) | Snail: PO Box 370 andymac@bullseye.apana.org.au (play) | Belconnen ACT 2616 Fido: Andrew MacIntyre, 3:620/243.18 | Australia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 11:37:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id D330015139; Sat, 11 Dec 1999 11:37:22 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id MAA06773; Sat, 11 Dec 1999 12:32:04 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912111932.MAA06773@freeway.dcfinc.com> Subject: Re: Route table leaks In-Reply-To: <199912081423.IAA59277@aurora.sol.net> from Joe Greco at "Dec 8, 99 08:23:35 am" To: jgreco@ns.sol.net (Joe Greco) Date: Sat, 11 Dec 1999 12:32:03 -0700 (MST) Cc: jdp@polstra.com, current@FreeBSD.ORG, 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, Joe Greco wrote: > Hell, I've been seeing this for well over a year. The last time I mentioned > it, everybody seemed to think I was nuts. :-) > > FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 Doesn't happen on 2.2... -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= chad> uname -v FreeBSD 2.2.8-STABLE #5: Sun Sep 19 19:18:11 MST 1999 toor@freeway.dcfinc.com:/usr/src/sys/compile/freeway chad> uptime 12:26PM up 80 days, 13:51, 3 users, load averages: 1.06, 1.03, 1.00 chad> vmstat -m | grep routetbl routetbl 46 6K 19K 18468K 2386 0 0 16,32,64,128,256 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 11:38: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id BB31A15312 for ; Sat, 11 Dec 1999 11:38:02 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id MAA06804; Sat, 11 Dec 1999 12:36:41 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912111936.MAA06804@freeway.dcfinc.com> Subject: Re: is -STABLE really stable? In-Reply-To: from Steve O'Hara-Smith at "Dec 8, 99 04:20:22 pm" To: steve@pooh.elsevier.nl (Steve O'Hara-Smith) Date: Sat, 11 Dec 1999 12:36:40 -0700 (MST) Cc: dhw@whistle.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, Steve O'Hara-Smith wrote: > Indeed the latter scenario is ideal (ideal is that the spare box and > the production box are identical). > [...] > Two identical boxes is IMHO the only way to be sure. Of course, that means you have to buy all the boxen, including the spare, in the same order. At least in the PC world, it is basically not possible to buy identical PCs seperated by more than a couple of weeks. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 11:52:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E5A7714C8E for ; Sat, 11 Dec 1999 11:52:23 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA13979; Sat, 11 Dec 1999 11:52:22 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA01097; Sat, 11 Dec 1999 11:52:22 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sat, 11 Dec 1999 11:52:22 -0800 (PST) Message-Id: <199912111952.LAA01097@vashon.polstra.com> To: chad@DCFinc.com Subject: Re: Route table leaks In-Reply-To: <199912111932.MAA06773@freeway.dcfinc.com> References: <199912111932.MAA06773@freeway.dcfinc.com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <199912111932.MAA06773@freeway.dcfinc.com>, Chad R. Larson wrote: > As I recall, Joe Greco wrote: > > Hell, I've been seeing this for well over a year. The last time I mentioned > > it, everybody seemed to think I was nuts. :-) > > > > FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > > > routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 > > Doesn't happen on 2.2... It doesn't happen on most 3.x or 4.x systems either. For starters, you won't see it unless you're running routed. Even then, you may or may not see it. I don't know whether the bug is present in 2.2 or not. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 12:11:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id B1BAB14CFE for ; Sat, 11 Dec 1999 12:10:59 -0800 (PST) (envelope-from pekkas@netcore.fi) Received: from localhost (pekkas@localhost) by netcore.fi (8.9.3/8.9.3) with ESMTP id WAA15690; Sat, 11 Dec 1999 22:10:22 +0200 Date: Sat, 11 Dec 1999 22:10:22 +0200 (EET) From: Pekka Savola To: John Polstra Cc: stable@FreeBSD.ORG Subject: Re: Route table leaks In-Reply-To: <199912111952.LAA01097@vashon.polstra.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 Sat, 11 Dec 1999, John Polstra wrote: > > > FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > > > > > routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 > > > > Doesn't happen on 2.2... > > It doesn't happen on most 3.x or 4.x systems either. For starters, > you won't see it unless you're running routed. Even then, you may > or may not see it. I don't know whether the bug is present in 2.2 > or not. Speaking of which, would someone please explain to me why the heck routed is started by default (/etc/rc.conf) ? I can't believe that many people would need it.. Regards, Pekka Savola To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 12:13:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 6CEC914DA3 for ; Sat, 11 Dec 1999 12:13:20 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id dBBKDGZ17014 for ; Sat, 11 Dec 1999 15:13:16 -0500 (EST) Date: Sat, 11 Dec 1999 15:13:15 -0500 (EST) From: jack To: stable@FreeBSD.ORG Subject: 3.4-RC Success Story 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 rolled a release on Tuesday. Thursday I put the CD in a brand new Dell PowerEdge 6300 and turned it on. It booted, saw all the devices and memory, installed, and rebooted without a hitch. Built a kernel, cvsup'd, then built the world in under fifty minutes. The box has been happily serving up web pages for the past thirty hours. -------------------------------------------------------------------------- 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 Sat Dec 11 12:29:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id F1BF315121 for ; Sat, 11 Dec 1999 12:29:48 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id MAA10532; Sat, 11 Dec 1999 12:29:37 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912112029.MAA10532@gndrsh.dnsmgr.net> Subject: Re: Route table leaks In-Reply-To: <199912111952.LAA01097@vashon.polstra.com> from John Polstra at "Dec 11, 1999 11:52:22 am" To: jdp@polstra.com (John Polstra) Date: Sat, 11 Dec 1999 12:29:37 -0800 (PST) Cc: chad@DCFinc.com, stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > In article <199912111932.MAA06773@freeway.dcfinc.com>, > Chad R. Larson wrote: > > As I recall, Joe Greco wrote: > > > Hell, I've been seeing this for well over a year. The last time I mentioned > > > it, everybody seemed to think I was nuts. :-) > > > > > > FreeBSD 3.0-19981015-BETA #1: Tue Jan 12 03:30:56 CST 1999 > > > > > > routetbl289178 40961K 40961K 40960K 435741 0 0 16,32,64,128,256 > > > > Doesn't happen on 2.2... > > It doesn't happen on most 3.x or 4.x systems either. For starters, > you won't see it unless you're running routed. Even then, you may ^^^^^^^^^^^^^^ I haven't run routed in 5 years, I see it. You meant ``a dynamic routing daemon'', and/or doing manual route delete's. Either of those can cause the leak. > or may not see it. I don't know whether the bug is present in 2.2 > or not. > > John > -- > John Polstra jdp@polstra.com > John D. Polstra & Co., Inc. Seattle, Washington USA > "No matter how cynical I get, I just can't keep up." -- Nora Ephron > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 12:45:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 6EB5415008 for ; Sat, 11 Dec 1999 12:45:25 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id NAA07371; Sat, 11 Dec 1999 13:45:19 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912112045.NAA07371@freeway.dcfinc.com> Subject: Re: Bad Floppy causes Kernel Panic (3.4-RC) In-Reply-To: <199912100940.EAA74144@lakes.dignus.com> from Thomas David Rivers at "Dec 10, 99 04:40:16 am" To: rivers@dignus.com (Thomas David Rivers) Date: Sat, 11 Dec 1999 13:45:19 -0700 (MST) Cc: FreeBSD-stable@FreeBSD.ORG, gwq_uk@yahoo.com 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, Thomas David Rivers wrote: > Hmm... I was just thinking - BAD144 had been (or will be) removed > from 4.0. > > But, as floppy sizes increase, with say, an LS120 - does it make > sense to keep bad144 to handle filesystems here? Get a few more miles out of a lightly damaged piece of $10 media? Hmm... I like it! Where do we vote? -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 14: 6:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id BD64114DB6 for ; Sat, 11 Dec 1999 14:06:56 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 17-044.008.popsite.net ([209.69.196.44] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.03 #1) id 11wufG-0005cW-00; Sat, 11 Dec 1999 15:06:55 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id RAA22500; Sat, 11 Dec 1999 17:06:51 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912111826.MAA01536@alecto.physics.uiuc.edu> Date: Sat, 11 Dec 1999 17:06:51 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: Igor Roshchin Subject: RE: problem with wtmp in 3.x family Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Dec-99 Igor Roshchin wrote: > I am not sure if this problem has been discussed here, > but I could not find it in the archives, although I know > a few people besides me who observed this problem. > There is a bug which seems to exist in the 3.x family of FreeBSD. > I haven't seen it in 2.x, and I observe it on a 3.1-stable > (19990412) box, as well as on a 3.3-RELEASE box. I see a similar problem in 3.3-STABLE (Nov 16) & 4.0-CURRENT (Sept 29). > 1. The record in wtmp file is not updated properly. > This seems to be happening when the connection dies (e.g. "reset by peer"), > say, when a people connected from a ppp-via-dialup host gets kicked > off by a modem, and the connection is not disconneted properly. > > 2. The utmp record is not updated either. > So, "w" shows a person being logged in, even though there are no processes > running on that tty. (accordingly w shows "-" as a current process). > When somebody else logs in on that tty, the utmp record is updated, > but not the wtmp one. > > In most cases, if not in all, the users use "screen". > I am not sure if the use of screen is necessary condition or just > a coinsidence. In my case, things are a little different. I have X11 + WindowMaker setup to run a rxvt w/ top & xtail /var/log whenever it starts up. I never kill these apps, so WindowMaker does the job. Unfortunately, the utmp & wtmp logs are affected as you say above: <2 5001-0> (99-12-11 17:02:42) [will@shadow ~]% w 5:02PM up 6 days, 19:40, 9 users, load averages: 1.02, 1.08, 1.07 USER TTY FROM LOGIN@ IDLE WHAT will v0 - 12:59PM 4:03 xinit /home/will/.xini will p0 unix:0 12:59PM 6days top will p1 unix:0 12:59PM 27days xtail /var/log Note that ttyp1's idle time is 27 days whereas my system uptime is only 6 days. Also note that I've only been running X for 4 hours. Because WindowMaker unconditionally kills these rxvt's, the utmp & wtmp files are not cleaned up properly, and I get a result like the above. Seems rather peculiar.. and you now know it's not restricted to `screen`. I'm almost 100% certain that the cause here is the improper writing of certain utmp and wtmp functions. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 14:39:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 5995714D03 for ; Sat, 11 Dec 1999 14:39:30 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA10823 for freebsd-stable@FreeBSD.org; Sat, 11 Dec 1999 14:39:29 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912112239.OAA10823@gndrsh.dnsmgr.net> Subject: Kernel compile warnings in 3.4-RC To: freebsd-stable@FreeBSD.org Date: Sat, 11 Dec 1999 14:39:29 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Time to clean these up, they have been coming out for a very long time and been ignored... In file included from ../../kern/init_sysent.c:11: ../../sys/sysent.h:72: warning: `struct vnode' declared inside parameter list ../../sys/sysent.h:72: warning: its scope is only this definition or declaration, ../../sys/sysent.h:72: warning: which is probably not what you want. ../../kern/kern_ntptime.c:542: warning: initialization from incompatible pointer type ../../pci/ncr.c:3248: warning: `ncr_info' defined but not used ../../pci/ncr.c:3236: warning: `ncr_min_phys' defined but not used ../../ufs/mfs/mfs_vfsops.c: In function `mfs_mount': ../../ufs/mfs/mfs_vfsops.c:181: warning: unused variable `base' ../../ufs/mfs/mfs_vfsops.c:347: warning: label `dostatfs' defined but not used ../../ufs/mfs/mfs_vfsops.c: At top level: ../../ufs/mfs/mfs_vfsops.c:67: warning: `mfs_rootbase' defined but not used ../../ufs/mfs/mfs_vfsops.c:68: warning: `mfs_rootsize' defined but not used ../../i386/i386/identcpu.c: In function `printcpuinfo': ../../i386/i386/identcpu.c:129: warning: `nreg' might be used uninitialized in this function ../../i386/isa/clock.c: In function `calibrate_clocks': ../../i386/isa/clock.c:595: warning: `old_tsc' might be used uninitialized in this function ../../i386/isa/npx.c:126: warning: `timezero' declared `static' but never defined -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 14:43:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 4FB7D14EFD for ; Sat, 11 Dec 1999 14:43:40 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.092 #1) id 11wuw4-000AqW-00; Sat, 11 Dec 1999 22:24:16 +0000 Date: Sat, 11 Dec 1999 22:24:16 +0000 From: Ben Smithurst To: Pekka Savola Cc: John Polstra , stable@FreeBSD.ORG Subject: Re: Route table leaks Message-ID: <19991211222416.A714@strontium.scientia.demon.co.uk> References: <199912111952.LAA01097@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pekka Savola wrote: > Speaking of which, would someone please explain to me why the heck routed > is started by default (/etc/rc.conf) ? I can't believe that many people > would need it.. You would appear to be mistaken: ben@strontium:~$ grep router_enable /usr/src/etc/defaults/rc.conf router_enable="NO" # Set to YES to enable a routing daemon. Has this changed in the last two months since I cvsupped? -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 15:32:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 7923914D0F for ; Sat, 11 Dec 1999 15:32:37 -0800 (PST) (envelope-from Pekka.Savola@netcore.fi) Received: from unf (netcore.fi [193.94.160.1]) by netcore.fi (8.9.3/8.9.3) with SMTP id BAA16058; Sun, 12 Dec 1999 01:32:32 +0200 Message-Id: <3.0.6.32.19991212013310.008feca0@netcore.home> X-Sender: pekkas@netcore.home X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 12 Dec 1999 01:33:10 +0200 To: Ben Smithurst From: Pekka Savola Subject: Re: Route table leaks Cc: stable@freebsd.org In-Reply-To: <19991211222416.A714@strontium.scientia.demon.co.uk> References: <199912111952.LAA01097@vashon.polstra.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Speaking of which, would someone please explain to me why the heck routed >> is started by default (/etc/rc.conf) ? I can't believe that many people >> would need it.. > >You would appear to be mistaken: > >ben@strontium:~$ grep router_enable /usr/src/etc/defaults/rc.conf >router_enable="NO" # Set to YES to enable a routing daemon. > >Has this changed in the last two months since I cvsupped? I installed 3.3-RELEASE two days ago on a blank disk, and the first thing I did was changing router_enable to NO. I'm not sure if choosing certain options and/or answering in a certain way to questions in the installation causes this to be sometimes enabled or disabled. When I tried 4.0-CURRENT in June, it had the same configuration. I wondered about the same thing. Pekka Savola pekkas@netcore.fi --- Across the nations the stories spread like spiderweb laid upon spiderweb, and men and women planned the future, believing they knew truth. They planned, and the Pattern absorbed their plans, weaving toward the future foretold. -- Robert Jordan: The Path of Daggers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 15:58:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 871B514F8A for ; Sat, 11 Dec 1999 15:58:18 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id dBBNwE536798 for ; Sat, 11 Dec 1999 18:58:15 -0500 (EST) Date: Sat, 11 Dec 1999 18:58:14 -0500 (EST) From: jack To: stable@FreeBSD.ORG Subject: Re: Route table leaks In-Reply-To: <3.0.6.32.19991212013310.008feca0@netcore.home> 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 > >> Speaking of which, would someone please explain to me why the heck routed > >> is started by default (/etc/rc.conf) ? I can't believe that many people > >> would need it.. Defaults have been in /etc/default/rc.conf since 3.0-stable, anything in /etc/rc.conf was locally added or the result of your choices in sysinstall. The default for routed has been NO for all of the 3.x branch and continiues into -current. 1.1.2.46 Wed Sep 23 11:37:06 1998 UTC by jkh Branch: RELENG_2_2 Diffs to 1.1.2.45 ; Diffs to 1.59 Don't start routed by default; it messes with ppp folks, for one thing. RELENG_3_0_0_RELEASE # $Id: rc.conf,v 1.60 1998/10/06 19:24:14 phk Exp $ router_enable="NO" # Set to YES to enable a routing daemon. -current # $FreeBSD: src/etc/defaults/rc.conf,v 1.44 1999/12/02 19:48:16 imp Exp $ router_enable="NO" # Set to YES to enable a routing daemon. -stable # $FreeBSD: src/etc/defaults/rc.conf,v 1.1.2.17 1999/11/24 03:52:02 jkoshy Exp $ router_enable="NO" # Set to YES to enable a routing daemon. -------------------------------------------------------------------------- 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 Sat Dec 11 16:38:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 489BD14C97 for ; Sat, 11 Dec 1999 16:38:21 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id QAA14977; Sat, 11 Dec 1999 16:38:19 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id QAA01308; Sat, 11 Dec 1999 16:38:19 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912112029.MAA10532@gndrsh.dnsmgr.net> Date: Sat, 11 Dec 1999 16:38:19 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: "Rodney W. Grimes" Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Rodney W. Grimes wrote: >> >> It doesn't happen on most 3.x or 4.x systems either. For starters, >> you won't see it unless you're running routed. Even then, you may > ^^^^^^^^^^^^^^ > > I haven't run routed in 5 years, I see it. You meant ``a dynamic routing > daemon'', and/or doing manual route delete's. Either of those can cause > the leak. Damn. Caught me oversimplifying again ... :-) John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 17: 3:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mta3.rcsntx.swbell.net (mta3.rcsntx.swbell.net [151.164.30.27]) by hub.freebsd.org (Postfix) with ESMTP id 56A4B15011 for ; Sat, 11 Dec 1999 17:03:18 -0800 (PST) (envelope-from noslenj@swbell.net) Received: from swbell.net ([207.193.26.36]) by mta3.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FML00KEYS89LR@mta3.rcsntx.swbell.net> for freebsd-stable@freebsd.org; Sat, 11 Dec 1999 19:02:36 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by swbell.net (8.9.3/8.9.3) with ESMTP id SAA01954 for ; Sat, 11 Dec 1999 18:58:39 -0600 (CST envelope-from noslenj@swbell.net) Date: Sat, 11 Dec 1999 18:58:39 -0600 (CST) From: Jay Nelson Subject: PS/2 mouse troubles? To: 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 I'm running: FreeBSD acp 3.3-STABLE FreeBSD 3.3-STABLE #4: Sun Nov 28 16:30:05 CST 1999 root@acp:/usr/src/sys/compile/ACP i386 My Xserver died with: /kernel: psmintr: out of sync (00c0 != 0000) I'm using a Logitech 3 button mouse in twm under XFree86-3.3.3.1. I had a freeze a couple of days ago with sources supped on 11/26 running olvwm -- though I didn't see any messages. dmsg output this time shows: psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 psmintr: out of sync (0080 != 0000). psmintr: out of sync (00c0 != 0000). psmintr: out of sync (00c0 != 0000). Is this a familiar problem, X out of sync or do I have a mouse on the fritz? -- Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 17:17:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 612791505F for ; Sat, 11 Dec 1999 17:17:25 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id RAA11100; Sat, 11 Dec 1999 17:17:21 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912120117.RAA11100@gndrsh.dnsmgr.net> Subject: Re: Route table leaks In-Reply-To: from John Polstra at "Dec 11, 1999 04:38:19 pm" To: jdp@polstra.com (John Polstra) Date: Sat, 11 Dec 1999 17:17:21 -0800 (PST) Cc: stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Rodney W. Grimes wrote: > >> > >> It doesn't happen on most 3.x or 4.x systems either. For starters, > >> you won't see it unless you're running routed. Even then, you may > > ^^^^^^^^^^^^^^ > > > > I haven't run routed in 5 years, I see it. You meant ``a dynamic routing > > daemon'', and/or doing manual route delete's. Either of those can cause > > the leak. > > Damn. Caught me oversimplifying again ... :-) :-) I just didn't walk folks getting the idea that this was really a bug in routed, and since they don't run routed they needn't worry about it. It takes a bgp/gated router about 7 to 10 days to suffer catastrophic failure from this leak problem depending on the global route churn rate, or at least thats what _was_ happening to us here. I'll know for sure in another day or two when I compare kernel route table size to object counts. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 17:27:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles535.castles.com [208.214.165.99]) by hub.freebsd.org (Postfix) with ESMTP id 2A4BB1504B for ; Sat, 11 Dec 1999 17:27:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA00818; Sat, 11 Dec 1999 17:30:01 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912120130.RAA00818@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Pekka Savola Cc: John Polstra , stable@FreeBSD.ORG Subject: Re: Route table leaks In-reply-to: Your message of "Sat, 11 Dec 1999 22:10:22 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Dec 1999 17:30:01 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Speaking of which, would someone please explain to me why the heck routed > is started by default (/etc/rc.conf) ? I can't believe that many people > would need it.. Bug in sysinstall; if you don't visit the 'networking' menu, it's not. Pester Jordan about it. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 17:33:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 16B0314EDE; Sat, 11 Dec 1999 17:33:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA00709; Sat, 11 Dec 1999 17:33:36 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Mike Smith Cc: Pekka Savola , John Polstra , stable@FreeBSD.ORG Subject: Re: Route table leaks In-reply-to: Your message of "Sat, 11 Dec 1999 17:30:01 PST." <199912120130.RAA00818@mass.cdrom.com> Date: Sat, 11 Dec 1999 17:33:36 -0800 Message-ID: <705.944962416@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are you sure? I can't see anythink in the current code path to imply that, nor have I seen this happen in practice anytime lately. Is there a PR filed for it I can look at? - Jordan > > Speaking of which, would someone please explain to me why the heck routed > > is started by default (/etc/rc.conf) ? I can't believe that many people > > would need it.. > > Bug in sysinstall; if you don't visit the 'networking' menu, it's not. > > Pester Jordan about it. > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 Sat Dec 11 19:52: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 9895C14EEC; Sat, 11 Dec 1999 19:51:53 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id dBC3pfE57138; Sat, 11 Dec 1999 22:51:42 -0500 (EST) Date: Sat, 11 Dec 1999 22:51:41 -0500 (EST) From: jack To: "Jordan K. Hubbard" Cc: Mike Smith , Pekka Savola , stable@FreeBSD.ORG Subject: Re: Route table leaks In-Reply-To: <705.944962416@zippy.cdrom.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 I just did two installs from the 3.3-R CD to a test box. First I selected only Gateway from the network menu, the second everything except routed. In neither case was routed enabled. On the 3.4-RC install I did the other day I enabled gateway from that menu and did not end up with routed turned on. ???????? Today Jordan K. Hubbard wrote: > Are you sure? I can't see anythink in the current code path to imply > that, nor have I seen this happen in practice anytime lately. Is > there a PR filed for it I can look at? > > - Jordan > > > > Speaking of which, would someone please explain to me why the heck routed > > > is started by default (/etc/rc.conf) ? I can't believe that many people > > > would need it.. > > > > Bug in sysinstall; if you don't visit the 'networking' menu, it's not. > > > > Pester Jordan about it. > > > > -- > > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-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 > -------------------------------------------------------------------------- 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 Sat Dec 11 22:33:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from helium.singnet.com.sg (helium.singnet.com.sg [165.21.101.212]) by hub.freebsd.org (Postfix) with ESMTP id 3BC4F14EFF for ; Sat, 11 Dec 1999 22:33:37 -0800 (PST) (envelope-from alvin@singnet.com.sg) Received: from arrakis (qtas2328.singnet.com.sg [165.21.54.158]) by helium.singnet.com.sg (8.9.3/8.9.3) with SMTP id OAA27517 for ; Sun, 12 Dec 1999 14:33:19 +0800 (SGT) Message-Id: <3.0.6.32.19991212143214.00b32200@pop.ajiang.com> X-Sender: alvin@pop.ajiang.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 12 Dec 1999 14:32:14 To: freebsd-stable@FreeBSD.ORG From: Alvin Jiang Subject: Re: PS/2 mouse troubles? In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmm, I just solved this problem last night. It took me all of 5 mins to search "psmintr" and find the solution at: http://www.freebsd.org/FAQ/x.html#AEN2255 You'd probably save a lot of time if you read the FAQ, rather than post and wait for a reply. At 06:58 PM 12/11/99 -0600, Jay Nelson wrote: >I'm running: > >FreeBSD acp 3.3-STABLE FreeBSD 3.3-STABLE #4: Sun Nov 28 16:30:05 CST >1999 root@acp:/usr/src/sys/compile/ACP i386 > >My Xserver died with: > >/kernel: psmintr: out of sync (00c0 != 0000) > >I'm using a Logitech 3 button mouse in twm under XFree86-3.3.3.1. I >had a freeze a couple of days ago with sources supped on 11/26 running >olvwm -- though I didn't see any messages. > >dmsg output this time shows: > >psm0 irq 12 on isa >psm0: model Generic PS/2 mouse, device ID 0 >psmintr: out of sync (0080 != 0000). >psmintr: out of sync (00c0 != 0000). >psmintr: out of sync (00c0 != 0000). > >Is this a familiar problem, X out of sync or do I have a mouse on the >fritz? > >-- Jay > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message > > Regards, -- Alvin Jiang http://www.ajiang.com "Information - the currency of a computerised future" - Cyberpunk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 23:35:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 24F10150B4; Sat, 11 Dec 1999 23:35:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA70827; Sat, 11 Dec 1999 23:35:19 -0800 (PST) (envelope-from dillon) Date: Sat, 11 Dec 1999 23:35:19 -0800 (PST) From: Matthew Dillon Message-Id: <199912120735.XAA70827@apollo.backplane.com> To: freebsd-stable@freebsd.org, freebsd-hackers@freebsd.org Reply-To: freebsd-hackers@freebsd.org Subject: Recent NFS commits, plus Heads up to 2.2.x users Hello everyone. There have been a number of recent NFS commits to fix bugs. Everything is hunky dory, but I do not have a 2.2.x box to test the MFC to 2.2.x so this is a head's up to 2.2.x users who are using NFS that these (relatively simple) bug fixes have been MFC'd, but not tested. It would be nice if I could get confirmation that 2.2.x hasn't blow up :-) -Matt Matthew Dillon dillon 1999/12/11 19:19:33 PST Modified files: sys/kern vfs_subr.c vfs_syscalls.c sys/vm vm_fault.c vm_map.c vm_map.h vm_mmap.c vm_object.c vm_object.h vm_page.c vm_page.h sys/sys mman.h lib/libc/sys madvise.2 mmap.2 Log: Add MAP_NOSYNC feature to mmap(), and MADV_NOSYNC and MADV_AUTOSYNC to madvise(). This feature prevents the update daemon from gratuitously flushing dirty pages associated with a mapped file-backed region of memory. The system pager will still page the memory as necessary and the VM system will still be fully coherent with the filesystem. Modifications made by other means to the same area of memory, for example by write(), are unaffected. The feature works on a page-granularity basis. MAP_NOSYNC allows one to use mmap() to share memory between processes without incuring any significant filesystem overhead, putting it in the same performance category as SysV Shared memory and anonymous memory. Reviewed by: julian, alc, dg Revision Changes Path 1.239 +2 -2 src/sys/kern/vfs_subr.c 1.147 +3 -2 src/sys/kern/vfs_syscalls.c 1.108 +17 -3 src/sys/vm/vm_fault.c 1.184 +16 -3 src/sys/vm/vm_map.c 1.52 +3 -2 src/sys/vm/vm_map.h 1.105 +5 -4 src/sys/vm/vm_mmap.c 1.171 +32 -5 src/sys/vm/vm_object.c 1.62 +4 -3 src/sys/vm/vm_object.h 1.147 +8 -4 src/sys/vm/vm_page.c 1.74 +5 -5 src/sys/vm/vm_page.h 1.27 +4 -1 src/sys/sys/mman.h 1.16 +28 -1 src/lib/libc/sys/madvise.2 1.18 +30 -1 src/lib/libc/sys/mmap.2 dillon 1999/12/11 19:28:15 PST Modified files: sys/kern vfs_syscalls.c Log: Remove accidental pollution unrelated to previous commit. The issue here is real but has not yet been discussed with Eivind. Revision Changes Path 1.148 +2 -3 src/sys/kern/vfs_syscalls.c dillon 1999/12/11 22:09:58 PST Modified files: sys/nfs nfs_bio.c nfs_subs.c nfs_vnops.c sys/sys buf.h Log: Synopsis of problem being fixed: Dan Nelson originally reported that blocks of zeros could wind up in a file written to over NFS by a client. The problem only occurs a few times per several gigabytes of data. This problem turned out to be bug #3 below. bug #1: B_CLUSTEROK must be cleared when an NFS buffer is reverted from stage 2 (ready for commit rpc) to stage 1 (ready for write). Reversions can occur when a dirty NFS buffer is redirtied with new data. Otherwise the VFS/BIO system may end up thinking that a stage 1 NFS buffer is clusterable. Stage 1 NFS buffers are not clusterable. bug #2: B_CLUSTEROK was inappropriately set for a 'short' NFS buffer (short buffers only occur near the EOF of the file). Change to only set when the buffer is a full biosize (usually 8K). This bug has no effect but should be fixed in -current anyway. It need not be backported. bug #3: B_NEEDCOMMIT was inappropriately set in nfs_flush() (which is typically only called by the update daemon). nfs_flush() does a multi-pass loop but due to the lack of vnode locking it is possible for new buffers to be added to the dirtyblkhd list while a flush operation is going on. This may result in nfs_flush() setting B_NEEDCOMMIT on a buffer which has *NOT* yet gone through its stage 1 write, causing only the commit rpc to be made and thus causing the contents of the buffer to be thrown away (never sent to the server). The patch also contains some cleanup, which only applies to the commit into -current. Reviewed by: dg, julian Originally Reported by: Dan Nelson Revision Changes Path 1.81 +27 -11 src/sys/nfs/nfs_bio.c 1.86 +15 -7 src/sys/nfs/nfs_subs.c 1.148 +3 -27 src/sys/nfs/nfs_vnops.c 1.85 +8 -1 src/sys/sys/buf.h dillon 1999/12/11 22:52:35 PST Modified files: (Branch: RELENG_3) sys/nfs nfs_bio.c nfs_subs.c nfs_vnops.c Log: MFC nfs_bio.c 1.81, nfs_subs.c 1.86, nfs_vnops.c 1.148. Fixed two rare-occuring bugs in NFS. First, B_CLUSTEROK must be cleared when B_NEEDCOMMIT is cleared since uncommitted dirty buffers may not be clustered. Second, B_NEEDCOMMIT cannot be gratuitously set in nfs_flush(). Due to lack of locking a buffer may be added to the dirtyblkhd list during the flush and setting B_NEEDCOMMIT can result in the buffer's data being thrown away rather then written to the server. Reviewed by: dg Approved by: jkh Revision Changes Path 1.65.2.3 +4 -4 src/sys/nfs/nfs_bio.c 1.70.2.4 +2 -2 src/sys/nfs/nfs_subs.c 1.116.2.8 +4 -4 src/sys/nfs/nfs_vnops.c dillon 1999/12/11 23:06:40 PST Modified files: sys/nfs nfs_nqlease.c nfs_serv.c nfs_subs.c Log: Fix a number of server-side issues related to aborting badly formed NFS packets, mainly initializing structure pointers to NULL which are conditionally freed prior to return. PR: kern/15249 Submitted by: Ian Dowse Revision Changes Path 1.47 +4 -2 src/sys/nfs/nfs_nqlease.c 1.89 +5 -5 src/sys/nfs/nfs_serv.c 1.87 +4 -1 src/sys/nfs/nfs_subs.c dillon 1999/12/11 23:16:21 PST Modified files: (Branch: RELENG_3) sys/nfs nfs_nqlease.c nfs_serv.c nfs_subs.c Log: MFC nfs_nqlease 1.47, nfs_serv.c 1.89, nfs_subs.c 1.87. Prevent panics in server side abort code when dealing with malformed NFS packets. Approved by: jkh Revision Changes Path 1.39.2.3 +4 -2 src/sys/nfs/nfs_nqlease.c 1.72.2.6 +5 -5 src/sys/nfs/nfs_serv.c 1.70.2.5 +4 -1 src/sys/nfs/nfs_subs.c dillon 1999/12/11 23:25:12 PST Modified files: (Branch: RELENG_2_2) sys/nfs nfs_nqlease.c nfs_subs.c Log: MFC nfs_nqlease 1.47, nfs_serv.c 1.89, nfs_subs.c 1.87. Note that no changes to nfs_serv.c were required, the bugs in that routine were introduced after 2.2.x. Revision Changes Path 1.20.2.2 +4 -2 src/sys/nfs/nfs_nqlease.c 1.33.2.4 +3 -1 src/sys/nfs/nfs_subs.c dillon 1999/12/11 23:28:52 PST Modified files: (Branch: RELENG_2_2) sys/nfs nfs_bio.c nfs_subs.c nfs_vnops.c Log: MFC nfs_bio.c 1.81, nfs_subs.c 1.86, nfs_vnops.c 1.148 Revision Changes Path 1.28.2.11 +3 -3 src/sys/nfs/nfs_bio.c 1.33.2.5 +2 -2 src/sys/nfs/nfs_subs.c 1.36.2.12 +4 -4 src/sys/nfs/nfs_vnops.c Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 11 23:38:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id E8A2B14CDE; Sat, 11 Dec 1999 23:38:47 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id XAA70877; Sat, 11 Dec 1999 23:38:47 -0800 (PST) (envelope-from dillon) Date: Sat, 11 Dec 1999 23:38:47 -0800 (PST) From: Matthew Dillon Message-Id: <199912120738.XAA70877@apollo.backplane.com> To: freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: Recent NFS commits, plus Heads up to 2.2.x users Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Holy formatting! Sorry about that. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 0: 2:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 151B015095 for ; Sun, 12 Dec 1999 00:02:49 -0800 (PST) (envelope-from Pekka.Savola@netcore.fi) Received: from unf (netcore.fi [193.94.160.1]) by netcore.fi (8.9.3/8.9.3) with SMTP id KAA16967; Sun, 12 Dec 1999 10:01:56 +0200 Message-Id: <3.0.6.32.19991212100236.0080aba0@netcore.home> X-Sender: pekkas@netcore.home X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 12 Dec 1999 10:02:36 +0200 To: jack From: Pekka Savola Subject: Re: Route table leaks Cc: jkh@zippy.cdrom.com, stable@freebsd.org In-Reply-To: References: <705.944962416@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I just did two installs from the 3.3-R CD to a test box. First I >selected only Gateway from the network menu, the second >everything except routed. In neither case was routed enabled. >On the 3.4-RC install I did the other day I enabled gateway from >that menu and did not end up with routed turned on. ???????? > >Today Jordan K. Hubbard wrote: > >> Are you sure? I can't see anythink in the current code path to imply >> that, nor have I seen this happen in practice anytime lately. Is >> there a PR filed for it I can look at? I have only used FreeBSD a couple of days and installed it twice, so I can't really remember what I did in sysinstall. However, the both times routed got enabled I installed either "Devel" or "Everything" and configured networking. Even though routed would get installed by either of those, I don't think it should be enabled without user intervention. HTH, Pekka Savola pekkas@netcore.fi --- Across the nations the stories spread like spiderweb laid upon spiderweb, and men and women planned the future, believing they knew truth. They planned, and the Pattern absorbed their plans, weaving toward the future foretold. -- Robert Jordan: The Path of Daggers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 2:17:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.hanarotel.net (mail.hananet.net [210.180.98.70]) by hub.freebsd.org (Postfix) with ESMTP id 634BC1508E; Sun, 12 Dec 1999 02:16:59 -0800 (PST) (envelope-from cjh@kr.FreeBSD.ORG) Received: from gradius.myhome ([210.205.33.54]) by mail.hanarotel.net (Post.Office MTA v3.5.3 release 223 ID# 200-56547U100000L100000S0V35) with ESMTP id net; Sun, 12 Dec 1999 19:23:21 +0900 Received: (from cjh@localhost) by gradius.myhome (8.9.3/8.9.3) id TAA02970; Sun, 12 Dec 1999 19:16:52 +0900 (KST) (envelope-from cjh) To: Jon Hamilton Cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: ppp over pty: trying to detect CD References: <19991212032201.5BF1150@woodstock.monkey.net> From: "CHOI, Junho" Date: 12 Dec 1999 19:16:52 +0900 In-Reply-To: Jon Hamilton's message of "Sat, 11 Dec 1999 21:22:01 -0600" Message-ID: <86bt7wlazv.fsf@gradius.myhome> Lines: 32 X-Mailer: Gnus v5.7/Emacs 20.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "JH" == Jon Hamilton writes: JH> Running -current from this afternoon, I am having a strange JH> symptom with ppp over a pty; ppp does not detect that the pty JH> does not support carrier, and will cycle once per second JH> waiting for CD to appear. Putting ``set cd off'' in my JH> ppp.conf for that target fixed the problem, but I thought I'd JH> mention it nonetheless, since that didn't used to be JH> required. Certainly not all that big a deal, but I thought it JH> was worth a mention. JH> FreeBSD 4.0-CURRENT #13: Sat Dec 11 20:31:42 CST 1999 I am using 3-STABLE but I have the same problem with you. I think it comes after adding pppoe support in pppd(after 3.3-RELEASE). I am -STABLE user but I had to back to 3.3-RELEASE's ppp... I am using ADSL service with pptpclient. JH> and the syslog with debugging turned on, with no "set cd" in the config: JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: Waiting for carrier JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: Waiting for carrier JH> [ and on and on and on ] -- +++ Any opinions in this posting are my own and not those of my employers +++ CHOI, Junho - Korea FreeBSD Users Group - Public Service, Youido Post Office - Web Data Bank To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 2:45:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id D3E0314E77; Sun, 12 Dec 1999 02:45:23 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C0EFF1CD79B; Sun, 12 Dec 1999 02:45:23 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 12 Dec 1999 02:45:23 -0800 (PST) From: Kris Kennaway To: The Unicorn Cc: freebsd-stable@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: Some (minor) problems with ports on 3.4-RC In-Reply-To: <19991210171956.Y528@unicorn.blackhats.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 On Fri, 10 Dec 1999, The Unicorn wrote: > l0pht-watch 1.1 MD5 checksum mismatch and Makefile not working at all. > Can be installed by hand. This one was an aliasing bug: the distfile is just l0pht-watch.tar.gz, which has no version information and so your system thought it already had the newer version. It builds fine, according to bento.freebsd.org > lsof 4.48A Makefile refers to 4.47 version and 3.4(-RC) not > recognised. Wanted to build 2.x version. Some minor > hacking enabled me to install a 3.3 version without > problems. This one has been fixed. > xpdf 0.90 Depends on t1lib. The configure script wants to check > if an underscore is needed for external symbols. LIB > variable is (temp) changed, but instead of adding an > object (.o) the assembly (.s) file name is added. Not sure if this one was fixed, but I think so. > xwhois 0.3.9 MD5 checksum mismatch and Makefile not working at all. > Can be installed by hand. This one was fixed. Thanks for the feedback! Hope you enjoy 3.4-REL :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 4:17:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 2673E15006 for ; Sun, 12 Dec 1999 04:17:17 -0800 (PST) (envelope-from Pekka.Savola@netcore.fi) Received: from unf (netcore.fi [193.94.160.1]) by netcore.fi (8.9.3/8.9.3) with SMTP id OAA17223; Sun, 12 Dec 1999 14:16:20 +0200 Message-Id: <3.0.6.32.19991212141700.007e2ac0@netcore.home> X-Sender: pekkas@netcore.home X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 12 Dec 1999 14:17:00 +0200 To: Sheepman From: Pekka Savola Subject: Re: pidentd Cc: williamsl@home.com, freebsd-stable@freebsd.org In-Reply-To: References: <7101.991211@Home.Com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > When I set up masq'ing awhile back I used a different ident daemon. I >did not use pidentd. I think maybe it was cidentd, but I am not sure. It >was specifically for ip masqing. Hope this helps a smidge. :) > >> I am trying to get pidentd (or any other ident daemon) to work for >> masqueraded hosts on a private LAN connected to the internet via a >> 3.2-RELEASE box. I've managed to successfully compile and install >> pidentd which works as a standard ident daemon but I am having >> difficulty figuring out how to make it work for masq'd hosts. Any >> ideas? Hi, I encountered the similar problem myself - and asked around for solutions. I have come to the conclusion that there are _no_ identd implementations for FreeBSD that would support NAT/Masq'ed connections. There are plenty of them for Linux, but they seem to use proc filesystem and are of no use.. Pidentd doesn't support masqed connections. There is patch for it to do that, but it is Linux only (http://www.manpages.org/pidentd/pidentd+fm-1.1.patch.gz). Midentd and Oidentd support masqed connections in Linux, but not in *BSD. There are more like these, just check e.g. freshmeat. Ident2 doesn't seem to do masqed connections at all (http://www.nyct.net/~defile/programs/ident2/). Cidentd doesn't seem to have been updated since 1996, and there is a nasty buffer overflow in it. Regards, Pekka Savola pekkas@netcore.fi --- Across the nations the stories spread like spiderweb laid upon spiderweb, and men and women planned the future, believing they knew truth. They planned, and the Pattern absorbed their plans, weaving toward the future foretold. -- Robert Jordan: The Path of Daggers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 7:41:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 4BB7414D34; Sun, 12 Dec 1999 07:41:31 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id QAA19005; Sun, 12 Dec 1999 16:38:29 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id PAA03904; Sun, 12 Dec 1999 15:59:33 +0100 (CET) From: Juergen Lock Date: Sun, 12 Dec 1999 15:59:32 +0100 To: Mike Smith Cc: zzhang@cs.binghamton.edu, freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: loader hacks (was: Re: easyboot far into disk) Message-ID: <19991212155932.A1107@saturn.kn-bremen.de> References: <19991107035454.B59629@saturn.kn-bremen.de> <199911071957.LAA13619@dingo.cdrom.com> <19991111224730.A739@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <19991111224730.A739@saturn.kn-bremen.de> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Cc'd to -hackers because, well, it contains hacks...) On Thu, Nov 11, 1999 at 10:47:30PM +0100, nox wrote: > On Sun, Nov 07, 1999 at 11:57:26AM -0800, Mike Smith wrote: > > > > Rootdev ought to work, actually. But if you get it wrong, the loader > > > > will fall back to using currdev. > > > > > > Hmm then thats strange. I first tried rootdev, which didn't work, and > > > then later currdev, which did work, and i believe i used the same value > > > both times! Or was rootdev fixed only recently, the boot floppies i > > > had lying around and tested this on weren't the latest... > > > > I thought rootdev was fixed a long time back. If it's not, please tell > > me and I'll fix it again. 8) > > Alright I finally got around testing this with a later kern.flp > (3.3-R actually), and it still didn't work. ... Well i played with this once more yesterday and now i know what was wrong: Unlike currdev, rootdev needs a `:' at the end... So either I'm blind or the manpage needs fixing. :) I also actually started making that FAQ entry (yeah!), and then wondered if you could also make an automagic boot floppy for a root disk that is entirely invisible to the BIOS, like when its on a BIOS-less (but otherwise supported) SCSI controller. I didn't find a way to do it with the original (-stable) loader, but when i made this patch, Index: biosdisk.c =================================================================== RCS file: /home/cvs/cvs/src/sys/boot/i386/libi386/biosdisk.c,v retrieving revision 1.20.2.7 diff -u -u -r1.20.2.7 biosdisk.c --- biosdisk.c 1999/08/29 16:20:59 1.20.2.7 +++ biosdisk.c 1999/12/12 00:14:52 @@ -785,23 +785,45 @@ int bd_getdev(struct i386_devdesc *dev) { - struct open_disk *od; + struct open_disk *od = NULL; int biosdev; int major; int rootdev; char *nip, *cp; int unitofs = 0, i, unit; + /* XXX kludge to allow the type of the root disk to be specified */ + cp = getenv("root_disk_type"); biosdev = bd_unit2bios(dev->d_kind.biosdisk.unit); DEBUG("unit %d BIOS device %d", dev->d_kind.biosdisk.unit, biosdev); - if (biosdev == -1) /* not a BIOS device */ + if (biosdev == -1) { /* not a BIOS device */ + int lastbiosdev; + /* + * BIOS doesn't know about this disk, this is not an error + * when root_disk_type is set unless the number is + * completely bogus + * (set root_disk_type=da and you may e.g. have the root + * disk hanging off a BIOS-less SCSI controller...) + */ + if (!cp || dev->d_kind.biosdisk.unit < 0 || + dev->d_kind.biosdisk.unit >= 256) + return(-1); + /* + * numbering of unknown-to-BIOS units starts with the first + * hard disk above the last one the BIOS saw, this is 0x80 + * if the BIOS only saw floppies + */ + lastbiosdev = bd_unit2bios(nbdinfo - 1); + biosdev = dev->d_kind.biosdisk.unit - nbdinfo + + (lastbiosdev < 0x80 ? 0x80 : lastbiosdev + 1); + } else if (bd_opendisk(&od, dev) != 0) /* oops, not a viable device */ return(-1); - if (bd_opendisk(&od, dev) != 0) /* oops, not a viable device */ - return(-1); - if (biosdev < 0x80) { + /* only assume floppy if root_disk_type is not set or is *fd* */ + if ((biosdev < 0x80 && !cp) || strstr(cp, "fd")) { /* floppy (or emulated floppy) or ATAPI device */ - if (bdinfo[dev->d_kind.biosdisk.unit].bd_type == DT_ATAPI) { + if ((cp && !strcmp(cp, "wfd")) || + bdinfo[dev->d_kind.biosdisk.unit].bd_type == DT_ATAPI) { /* is an ATAPI disk */ major = WFDMAJOR; } else { @@ -810,8 +832,10 @@ } } else { /* harddisk */ - if ((od->od_flags & BD_LABELOK) && (od->od_disklabel.d_type == DTYPE_SCSI)) { - /* label OK, disk labelled as SCSI */ + if ((cp && !strcmp(cp, "da")) || + (od && (od->od_flags & BD_LABELOK) && + (od->od_disklabel.d_type == DTYPE_SCSI))) { + /* label OK or root_disk_type set, disk labelled as SCSI */ major = DAMAJOR; /* check for unit number correction hint, now deprecated */ if ((nip = getenv("num_ide_disks")) != NULL) { @@ -820,23 +844,24 @@ if ((cp != nip) && (*cp == 0)) unitofs = i; } - } else if ((od->od_flags & BD_LABELOK) && - (od->od_disklabel.d_type == DTYPE_DOC2K)) { + } else if ((cp && !strcmp(cp, "fla")) || + (od && (od->od_flags & BD_LABELOK) && + (od->od_disklabel.d_type == DTYPE_DOC2K))) { major = FLAMAJOR; } else { /* assume an IDE disk */ major = WDMAJOR; } } + /* allow for #wd compenstation in da case */ + unit = (biosdev & 0x7f) - unitofs; + /* XXX a better kludge to set the root disk unit number */ if ((nip = getenv("root_disk_unit")) != NULL) { i = strtol(nip, &cp, 0); /* check for parse error */ if ((cp != nip) && (*cp == 0)) unit = i; - } else { -/* allow for #wd compenstation in da case */ - unit = (biosdev & 0x7f) - unitofs; } rootdev = MAKEBOOTDEV(major, Index: bootinfo.c =================================================================== RCS file: /home/cvs/cvs/src/sys/boot/i386/libi386/bootinfo.c,v retrieving revision 1.15.2.3 diff -u -u -r1.15.2.3 bootinfo.c --- bootinfo.c 1999/08/29 16:21:01 1.15.2.3 +++ bootinfo.c 1999/12/11 20:12:40 @@ -262,6 +262,7 @@ default: printf("aout_exec: WARNING - don't know how to boot from device type %d\n", rootdev->d_type); + return(EINVAL); } free(rootdev); *bootdevp = bootdevnr; (the last changes are actually fixes for what looked like genuine bugs, tho they don't seem to matter much.) I was then able to boot from a floppy with the SCSI BIOS turned off: set root_disk_type=da set root_disk_unit=2 set rootdev=disk0s1a: although when i tried a cold boot i got a panic because apparently the kernel didn't expect to have to `start unit' some disks and wait for them to come online. (well it did send the start unit to one, paniced, then the at the next boot started another... until when all were up, so in the end the boot `just' took longer...) Should i try to make a proper bugreport for that or is it to be expected? And note how you still have to split the actual device name up (da2s1a here) if you don't want to depend on how the BIOS numbers the disks which often differs from the kernel. (`da' goes into root_disk_type, `2' goes into root_disk_unit und the slice/partition `s1a' goes into rootdev. at least the 0 in disk0 should not matter anymore now when both of the others are set so these three lines could then also be generated by e.g. sysinstall without any additional knowledge about the BIOS.) I believe -current now also has a fix for this although i don't know if the way its been done there would still work with older kernels. With this you should be able to boot even pre-loader systems if you put the old kernel on the floppy... Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 7:51:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ak00.krascience.rssi.ru (ak0.krascience.rssi.ru [193.232.19.65]) by hub.freebsd.org (Postfix) with ESMTP id 14BC514BE5 for ; Sun, 12 Dec 1999 07:51:06 -0800 (PST) (envelope-from aleks@post.krascience.rssi.ru) Received: from ALEKS (ak11.krascience.rssi.ru [193.232.203.66]) by ak00.krascience.rssi.ru (8.8.5/8.8.5) with ESMTP id WAA01805; Sun, 12 Dec 1999 22:50:11 +0700 (KRS) Date: Sun, 12 Dec 1999 22:48:28 +0700 From: Alexei Sokolski X-Mailer: The Bat! (v1.36) UNREG / CD5BF9353B3B7091 Reply-To: Alexei Sokolski Organization: ICM of SB RAS X-Priority: 3 (Normal) Message-ID: <2950.991212@cc.krascience.rssi.ru> To: Roelof Osinga Cc: freebsd-stable@freebsd.org Subject: Re[2]: ifpw forwarding problem In-reply-To: <384FFEC6.276F4A1E@nisser.com> References: <384FFEC6.276F4A1E@nisser.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="----------F12555BA795BC" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ------------F12555BA795BC Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hello, 10 Dec 1999 , Roelof Osinga wrote: > OK, here it comes. A fresh set of data. This is how it is *now*. Thus > with FORWARD disabled. Some testscripts are at the end. Maybe you > can spot the error, I sure can't. I can`n find error in YOUR scripts. But I find something wrong at work of ipfw... (or not ?) I have FreeBSD gateway with natd and two interface: First is public de0 - 193.x.x.121. Second is local rl0 - 172.16.0.14. One web-server at 172.16.0.101:80 and http-client (172.16.0.2). All of them has connection to 10Base-T hub. I run network analyser at client machine with capture filter: "catch from any_ether to any_ether" I am try make redirection from my gateway to my local web-server from Internet and local network. Don`t asked me why I did it :^( I have several small experiment: 1) for redirection from Internet I add rule at natd configuration: -redirect_port tcp 193.x.x.121:80 172.16.0.101:80 And this work. 2) I make forward as Roelof Osinga: ipfw add 1 fwd 172.16.0.101,80 tcp from any to 172.16.0.14 8080 in via rl0 At this case analyser show series of packets : a) from client to dateway for open tcp connection in port 8080 b) and my gateway write in log_file: Connection attempt to TCP 172.16.0.14:8080 from 172.16.0.2:some_ports 3) I make forward: ipfw add 1 fwd 172.16.0.101,80 tcp from any to 172.16.0.14 8080 At this case analyser show packets a) from client to gateway - open connection in port 8080 b) from gateway to web-server for open tcp connection to port 8080 (!!!). No service at web-server on port 8080 therefore client has timeout :^(( 4) In man ipfw(8) write ... fwd ipaddr [,port] ... This is intended for use with transparent proxy servers. ... And I decide tried make forward like this (from 80 to 80 port): ipfw add 1 fwd 172.16.0.101,80 tcp from any to 172.16.0.14 80 in via rl0 At this case analyser show series of packets : a) from client to dateway for open tcp connection in port 80 b) and my gateway write in log_file: Connection attempt to TCP 172.16.0.14:80 from 172.16.0.2:some_ports 5) Then I make forward (may be it work): ipfw add 1 fwd 172.16.0.101,80 tcp from any to 172.16.0.14 80 At this case analyser show series of packets a) from client to gateway - open connection in port 80 b) from gateway to web-server for open tcp connection to port 80. c) from gateway to client - icmp: Redirect, Use Gateway 172.16.00.14, to reach 172.16.00.14 (!!!) It is repeat many a time without success therefore client has timeout :^(( So, I have a problem (I or all?): Can I make redirect from IP1:port1 to IP2:port2 with "ipfw..fwd..."? Or I must use one more natd for that? All information about machine in files: $uname -a uname-a $ifconfig -a ifconfig-a $ipfw list ipfw_list file KERNEL ICMSBRAS P.S. One more questions In FreeBSD 2.2.6 with natd at port 8668 in my machine I had: $netstat -an Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 *.xxx *.* LISTEN divert 0 0 *.8668 *.* LISTEN Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr Now when I run natd I have string with icmp: $netstat -an Proto Recv-Q Send-Q Local Address Foreign Address (state) icmp 0 0 *.* *.* tcp 0 0 *.XXX *.* LISTEN Active UNIX domain sockets Address Type Recv-Q Send-Q Inode Conn Refs Nextref Addr Can you say why??? ----------- Thank you for your help, Sokolski Alexei engineer of technical laboratory ICM SB RAS ------------F12555BA795BC Content-Type: application/octet-stream; name="uname-a" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="uname-a" RnJlZUJTRCBhazExLmtyYXNjaWVuY2UucnNzaS5ydSAzLjMtUkVMRUFTRSBGcmVlQlNEIDMuMy1S RUxFQVNFICMwOiBNb24gRGVjICA2IDIxOjI2OjQxIEtSQVQgMTk5OSAgICAgYWxla3NAa3NjLmty YXNuLnJ1Oi91c3Ivc3JjL3N5cy9jb21waWxlL0lDTVNCUkFTICBpMzg2DQo= ------------F12555BA795BC Content-Type: application/octet-stream; name="ifconfig-a" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="ifconfig-a" ZGUwOiBmbGFncz04OTQzPFVQLEJST0FEQ0FTVCxSVU5OSU5HLFBST01JU0MsU0lNUExFWCxNVUxU SUNBU1Q+IG10dSAxNTAwDQoJaW5ldCAxOTMueHgueHguNjYgbmV0bWFzayAweGZmZmZmZmMwIGJy b2FkY2FzdCAxOTMueHgueHguMTI3DQoJaW5ldCAxOTMueHgueHguMTIxIG5ldG1hc2sgMHhmZmZm ZmZmZiBicm9hZGNhc3QgMTkzLnh4Lnh4LjEyMQ0KCWV0aGVyIDA4OjAwOjJiOmU0OjA2OjhhIA0K CW1lZGlhOiBhdXRvc2VsZWN0ICgxMGJhc2VUL1VUUCkgc3RhdHVzOiBhY3RpdmUNCglzdXBwb3J0 ZWQgbWVkaWE6IGF1dG9zZWxlY3QgMTBiYXNlNS9BVUkgbWFudWFsIDEwYmFzZVQvVVRQIDxmdWxs LWR1cGxleD4gMTBiYXNlVC9VVFANCnJsMDogZmxhZ3M9ODg0MzxVUCxCUk9BRENBU1QsUlVOTklO RyxTSU1QTEVYLE1VTFRJQ0FTVD4gbXR1IDE1MDANCglpbmV0IDE3Mi4xNi4wLjE0IG5ldG1hc2sg MHhmZmZmMDAwMCBicm9hZGNhc3QgMTcyLjE2LjI1NS4yNTUNCglldGhlciAwMDpjMDpkZjoyNTpi NDoxMiANCgltZWRpYTogYXV0b3NlbGVjdA0KCXN1cHBvcnRlZCBtZWRpYTogYXV0b3NlbGVjdCAx MDBiYXNlVFggPGZ1bGwtZHVwbGV4PiAxMDBiYXNlVFggPGhhbGYtZHVwbGV4PiAxMDBiYXNlVFgg MTBiYXNlVC9VVFAgPGZ1bGwtZHVwbGV4PiAxMGJhc2VUL1VUUCAxMGJhc2VUL1VUUCA8aGFsZi1k dXBsZXg+DQpzbDA6IGZsYWdzPWMwMTA8UE9JTlRPUE9JTlQsTElOSzIsTVVMVElDQVNUPiBtdHUg NTUyDQpwcHAwOiBmbGFncz04MDEwPFBPSU5UT1BPSU5ULE1VTFRJQ0FTVD4gbXR1IDE1MDANCnBw cDE6IGZsYWdzPTgwMTA8UE9JTlRPUE9JTlQsTVVMVElDQVNUPiBtdHUgMTUwMA0KcHBwMjogZmxh Z3M9ODAxMDxQT0lOVE9QT0lOVCxNVUxUSUNBU1Q+IG10dSAxNTAwDQpwcHAzOiBmbGFncz04MDEw PFBPSU5UT1BPSU5ULE1VTFRJQ0FTVD4gbXR1IDE1MDANCmxvMDogZmxhZ3M9ODA0OTxVUCxMT09Q QkFDSyxSVU5OSU5HLE1VTFRJQ0FTVD4gbXR1IDE2Mzg0DQoJaW5ldCAxMjcuMC4wLjEgbmV0bWFz ayAweGZmMDAwMDAwIA0K ------------F12555BA795BC Content-Type: application/octet-stream; name="ipfw_list" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="ipfw_list" MDAxMDAgZGl2ZXJ0IDkwMDkgaXAgZnJvbSBhbnkgdG8gYW55IHZpYSBkZTANCjAwMTAwIGFsbG93 IGlwIGZyb20gYW55IHRvIGFueSB2aWEgbG8wDQowMDIwMCBkZW55IGlwIGZyb20gYW55IHRvIDEy Ny4wLjAuMC84DQo2NTAwMCBhbGxvdyBpcCBmcm9tIGFueSB0byBhbnkNCjY1NTM1IGRlbnkgaXAg ZnJvbSBhbnkgdG8gYW55DQo= ------------F12555BA795BC Content-Type: application/octet-stream; name="Icmsbras" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="Icmsbras" bWFjaGluZQkJImkzODYiDQpjcHUJCSJJNjg2X0NQVSINCmlkZW50CQlJQ01TQlJBUw0KbWF4dXNl cnMJNTEyDQoNCmNvbmZpZwkJa2VybmVsCXJvb3Qgb24gd2QwDQoNCm9wdGlvbnMgCSJDT01QQVRf NDMiCQkjQ29tcGF0aWJsZSB3aXRoIEJTRCA0LjMgW0tFRVAgVEhJUyFdDQpvcHRpb25zIAlGRlMJ CQkjQmVya2VsZXkgRmFzdCBGaWxlc3lzdGVtDQpvcHRpb25zIAlGRlNfUk9PVAkJI0ZGUyB1c2Fi bGUgYXMgcm9vdCBkZXZpY2UgW2tlZXAgdGhpcyFdDQpvcHRpb25zIAlQUk9DRlMJCQkjUHJvY2Vz cyBmaWxlc3lzdGVtDQpvcHRpb25zIAlNRlMJCQkjTWVtb3J5IEZpbGVzeXN0ZW0NCm9wdGlvbnMJ CVFVT1RBCQkJI0VuYWJsZSBkaXNrIHF1b3Rhcw0KDQpjb250cm9sbGVyCWlzYTANCmNvbnRyb2xs ZXIJcG5wMAkJCSMgUG5QIHN1cHBvcnQgZm9yIElTQQ0KY29udHJvbGxlcglwY2kwDQoNCmNvbnRy b2xsZXIJd2RjMAlhdCBpc2E/IHBvcnQgIklPX1dEMSIgYmlvIGlycSAxNA0KZGlzawkJd2QwCWF0 IHdkYzAgZHJpdmUgMCBmbGFncyAweGIwZmYgIz8/Pz8gZm9yIExCQSAoMHhiIG9yIDB4YSkNCmRp c2sJCXdkMQlhdCB3ZGMwIGRyaXZlIDENCg0KY29udHJvbGxlcgl3ZGMxCWF0IGlzYT8gcG9ydCAi SU9fV0QyIiBiaW8gaXJxIDE1DQpkaXNrCQl3ZDIJYXQgd2RjMSBkcml2ZSAwIGZsYWdzIDB4YjBm ZiAjPz8/PyBmb3IgTEJBICgweGIgb3IgMHhhKQ0KZGlzawkJd2QzCWF0IHdkYzEgZHJpdmUgMQ0K DQojIEZsb2F0aW5nIHBvaW50IHN1cHBvcnQgLSBkbyBub3QgZGlzYWJsZS4NCmRldmljZQkJbnB4 MAlhdCBpc2E/IHBvcnQgSU9fTlBYIGlycSAxMw0KDQojIHN5c2NvbnMgaXMgdGhlIGRlZmF1bHQg Y29uc29sZSBkcml2ZXIsIHJlc2VtYmxpbmcgYW4gU0NPIGNvbnNvbGUNCmRldmljZQkJc2MwCWF0 IGlzYT8gdHR5DQpvcHRpb25zCQlTQ19ISVNUT1JZX1NJWkU9NjAwCSMgbnVtYmVyIG9mIGhpc3Rv cnkgYnVmZmVyIGxpbmVzDQoNCmRldmljZQkJdmdhMAlhdCBpc2E/IHBvcnQgPyBjb25mbGljdHMN Cg0KIyBhdGtiZGMwIGNvbnRyb2xzIGJvdGggdGhlIGtleWJvYXJkIGFuZCB0aGUgUFMvMiBtb3Vz ZQ0KY29udHJvbGxlcglhdGtiZGMwCWF0IGlzYT8gcG9ydCBJT19LQkQgdHR5DQpkZXZpY2UJCWF0 a2JkMAlhdCBpc2E/IHR0eSBpcnEgMQ0KDQojIFNlcmlhbCAoQ09NKSBwb3J0cw0KZGV2aWNlCQlz aW8wCWF0IGlzYT8gcG9ydCAiSU9fQ09NMSIgZmxhZ3MgMHgyMDAwMCB0dHkgaXJxIDQNCmRldmlj ZQkJc2lvMQlhdCBpc2E/IHBvcnQgIklPX0NPTTIiIGZsYWdzIDB4MjAwMDAgdHR5IGlycSAzDQpk ZXZpY2UJCXNpbzIJYXQgaXNhPyBkaXNhYmxlIHBvcnQgIklPX0NPTTMiIGZsYWdzIDB4MjAwMDAg dHR5IGlycSA1DQpkZXZpY2UJCXNpbzMJYXQgaXNhPyBkaXNhYmxlIHBvcnQgIklPX0NPTTQiIGZs YWdzIDB4MjAwMDAgdHR5IGlycSA5DQoNCm9wdGlvbnMgCUlORVQJCQkjSW50ZXJORVR3b3JraW5n DQoNCiMgUENJIEV0aGVybmV0IE5JQ3MuDQpkZXZpY2UJCWRlMAkJIyBERUMvSW50ZWwgREMyMXg0 eCAoYGBUdWxpcCcnKQ0KZGV2aWNlCQlybDAJCSMgUmVhbFRlayA4MTI5LzgxMzkNCnBzZXVkby1k ZXZpY2UgbG9vcA0KcHNldWRvLWRldmljZSBldGhlcg0KcHNldWRvLWRldmljZSBzbCAxDQpwc2V1 ZG8tZGV2aWNlIGJwZmlsdGVyIDMyDQpwc2V1ZG8tZGV2aWNlIGd6aXANCnBzZXVkby1kZXZpY2Ug bG9nDQpwc2V1ZG8tZGV2aWNlIHB0eSA4DQpwc2V1ZG8tZGV2aWNlIHNucCAyNA0KcHNldWRvLWRl dmljZSB2bg0KcHNldWRvLWRldmljZSBjY2QgMg0KcHNldWRvLWRldmljZSBwcHAgNA0Kb3B0aW9u cyBQUFBfQlNEQ09NUAkJCSNQUFAgQlNELWNvbXByZXNzIHN1cHBvcnQNCm9wdGlvbnMgUFBQX0RF RkxBVEUJCQkjUFBQIHpsaWIvZGVmbGF0ZS9nemlwIHN1cHBvcnQNCm9wdGlvbnMgUFBQX0ZJTFRF UgkJCSNlbmFibGUgYnBmIGZpbHRlcmluZyAobmVlZHMgYnBmaWx0ZXIpDQoNCm9wdGlvbnMgCUZB SUxTQUZFCQkjQmUgY29uc2VydmF0aXZlDQpvcHRpb25zIAlVU0VSQ09ORklHCQkjYm9vdCAtYyBl ZGl0b3INCm9wdGlvbnMgCVZJU1VBTF9VU0VSQ09ORklHCSN2aXN1YWwgYm9vdCAtYyBlZGl0b3IN Cm9wdGlvbnMgCUtUUkFDRQkJCSNrdHJhY2UoMSkgc3lzY2FsbCB0cmFjZSBzdXBwb3J0DQoNCm9w dGlvbnMJCSJNQVhEU0laPSgyNTYqMTAyNCoxMDI0KSINCm9wdGlvbnMJCSJERkxEU0laPSgyNTYq MTAyNCoxMDI0KSINCg0Kb3B0aW9ucyAgICAgICAgIElQRklSRVdBTEwgICAgICAgICAgICAgICNm aXJld2FsbA0Kb3B0aW9ucyAgICAgICAgIElQRklSRVdBTExfVkVSQk9TRSAgICAgICNwcmludCBp bmZvcm1hdGlvbiBhYm91dA0KCQkJCQkjIGRyb3BwZWQgcGFja2V0cw0Kb3B0aW9ucyAgICAgICAg IElQRklSRVdBTExfRk9SV0FSRCAgICAgICNlbmFibGUgdHJhbnNwYXJlbnQgcHJveHkgc3VwcG9y dA0Kb3B0aW9ucwkJSVBESVZFUlQJCSNkaXZlcnQgc29ja2V0cw0Kb3B0aW9ucwkJSVBGSUxURVIJ CSNrZXJuZWwgaXBmaWx0ZXIgc3VwcG9ydA0Kb3B0aW9ucwkJSVBGSUxURVJfTE9HCQkjaXBmaWx0 ZXIgbG9nZ2luZw0Kb3B0aW9ucwkJVENQREVCVUcNCg0Kb3B0aW9ucyAgICAgICAgICJJQ01QX0JB TkRMSU0iDQoNCiMgRFVNTVlORVQgZW5hYmxlcyB0aGUgImR1bW15bmV0IiBiYW5kd2lkdGggbGlt aXRlci4gWW91IG5lZWQNCiMgSVBGSVJFV0FMTCBhcyB3ZWxsLiBTZWUgdGhlIGR1bW15bmV0KDQp IG1hbnBhZ2UgZm9yIG1vcmUgaW5mby4NCm9wdGlvbnMJRFVNTVlORVQNCg0Kb3B0aW9ucwlORlNf Tk9TRVJWRVIJCSNEaXNhYmxlIHRoZSBORlMtc2VydmVyIGNvZGUuDQoNCiMgQWxsb3cgdGhpcyBt YW55IHN3YXAtZGV2aWNlcy4NCm9wdGlvbnMJCU5TV0FQREVWPTUNCg0Kb3B0aW9ucwkJU1VJRERJ Ug0KDQo= ------------F12555BA795BC-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 8:12: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id 180FA14D19 for ; Sun, 12 Dec 1999 08:12:00 -0800 (PST) (envelope-from papalia@UDel.Edu) Received: from morgaine (host75-157.student.udel.edu [128.175.75.157]) by copland.udel.edu (8.9.3/8.9.3) with SMTP id LAA27037; Sun, 12 Dec 1999 11:11:54 -0500 (EST) Message-Id: <4.1.19991212111055.009552e0@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 12 Dec 1999 11:11:58 -0500 To: Pekka Savola , Sheepman From: John Subject: Re: pidentd Cc: williamsl@home.com, freebsd-stable@FreeBSD.ORG In-Reply-To: <3.0.6.32.19991212141700.007e2ac0@netcore.home> References: <7101.991211@Home.Com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Are the boxes that you're trying to ident on FreeBSD boxes or windows boxes or mac boxes? --John >> When I set up masq'ing awhile back I used a different ident daemon. I >>did not use pidentd. I think maybe it was cidentd, but I am not sure. It >>was specifically for ip masqing. Hope this helps a smidge. :) >> >>> I am trying to get pidentd (or any other ident daemon) to work for >>> masqueraded hosts on a private LAN connected to the internet via a >>> 3.2-RELEASE box. I've managed to successfully compile and install >>> pidentd which works as a standard ident daemon but I am having >>> difficulty figuring out how to make it work for masq'd hosts. Any >>> ideas? > >Hi, > >I encountered the similar problem myself - and asked around for solutions. >I have come to the conclusion that there are _no_ identd implementations >for FreeBSD that would support NAT/Masq'ed connections. There are plenty >of them for Linux, but they seem to use proc filesystem and are of no use.. > >Pidentd doesn't support masqed connections. There is patch for it to do >that, but it is Linux only >(http://www.manpages.org/pidentd/pidentd+fm-1.1.patch.gz). > >Midentd and Oidentd support masqed connections in Linux, but not in *BSD. >There are more like these, just check e.g. freshmeat. > >Ident2 doesn't seem to do masqed connections at all >(http://www.nyct.net/~defile/programs/ident2/). > >Cidentd doesn't seem to have been updated since 1996, and there is a nasty >buffer overflow in it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 8:40:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id 1C5D014F4E for ; Sun, 12 Dec 1999 08:40:51 -0800 (PST) (envelope-from Pekka.Savola@netcore.fi) Received: from unf (netcore.fi [193.94.160.1]) by netcore.fi (8.9.3/8.9.3) with SMTP id SAA17507; Sun, 12 Dec 1999 18:39:43 +0200 Message-Id: <3.0.6.32.19991212184024.0097fa70@netcore.home> X-Sender: pekkas@netcore.home X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 12 Dec 1999 18:40:24 +0200 To: John From: Pekka Savola Subject: Re: pidentd Cc: williamsl@home.com, Sheepman , freebsd-stable@FreeBSD.ORG In-Reply-To: <4.1.19991212111055.009552e0@mail.udel.edu> References: <3.0.6.32.19991212141700.007e2ac0@netcore.home> <7101.991211@Home.Com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Are the boxes that you're trying to ident on FreeBSD boxes or windows boxes >or mac boxes? > >>I encountered the similar problem myself - and asked around for solutions. >>I have come to the conclusion that there are _no_ identd implementations >>for FreeBSD that would support NAT/Masq'ed connections. There are plenty >>of them for Linux, but they seem to use proc filesystem and are of no use.. In my case, the NAT'ed box I want to ident is running Windows. I don't see any difference which OS is installed there, however, as long as it is able to run an identd server. The obvious reason for this is (among other things) IRC. It'd be nice to have an idented name+host. :) Pekka Savola pekkas@netcore.fi --- Across the nations the stories spread like spiderweb laid upon spiderweb, and men and women planned the future, believing they knew truth. They planned, and the Pattern absorbed their plans, weaving toward the future foretold. -- Robert Jordan: The Path of Daggers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 8:45:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id EFB0414F2B for ; Sun, 12 Dec 1999 08:45:53 -0800 (PST) (envelope-from papalia@UDel.Edu) Received: from morgaine (host75-157.student.udel.edu [128.175.75.157]) by copland.udel.edu (8.9.3/8.9.3) with SMTP id LAA16431; Sun, 12 Dec 1999 11:45:46 -0500 (EST) Message-Id: <4.1.19991212114203.00959100@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 12 Dec 1999 11:45:51 -0500 To: Pekka Savola From: John Subject: Re: pidentd Cc: williamsl@home.com, Sheepman , freebsd-stable@FreeBSD.ORG In-Reply-To: <3.0.6.32.19991212184024.0097fa70@netcore.home> References: <4.1.19991212111055.009552e0@mail.udel.edu> <3.0.6.32.19991212141700.007e2ac0@netcore.home> <7101.991211@Home.Com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>Are the boxes that you're trying to ident on FreeBSD boxes or windows boxes >>or mac boxes? >> >>>I encountered the similar problem myself - and asked around for solutions. >>>I have come to the conclusion that there are _no_ identd implementations >>>for FreeBSD that would support NAT/Masq'ed connections. There are plenty >>>of them for Linux, but they seem to use proc filesystem and are of no >use.. > >In my case, the NAT'ed box I want to ident is running Windows. I don't see >any difference which OS is installed there, however, as long as it is able >to run an identd server. > >The obvious reason for this is (among other things) IRC. It'd be nice to >have an idented name+host. :) If you're running windows boxen behind your FreeBSD server, then (at least I think) the EASIEST way to solve your problem is to run IRC clients on yoru windows boxen which contain identd servers to themselves. This includes the latest versions of mIRC. You just need to search through the settings and preferences and actually turn the option on. I'm sure there are others too, but that's the only one coming to mind right now. That takes care of the problem of extending your freebsd identd out to your masq'ed boxes. Also, a quick search of www.shareware.com came up with three Windows Identd programs: kidentd, t-ide211, and widentd. I've never used any of them (cuz I don't irc through windows), but they're there, and the first two are labeled as being "free". Hope that helps you out. Regards, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 9: 6:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id D445A14EAC for ; Sun, 12 Dec 1999 09:06:09 -0800 (PST) (envelope-from Pekka.Savola@netcore.fi) Received: from unf (netcore.fi [193.94.160.1]) by netcore.fi (8.9.3/8.9.3) with SMTP id TAA17553; Sun, 12 Dec 1999 19:04:54 +0200 Message-Id: <3.0.6.32.19991212190534.007ec9b0@netcore.home> X-Sender: pekkas@netcore.home X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 12 Dec 1999 19:05:34 +0200 To: John From: Pekka Savola Subject: Re: pidentd Cc: williamsl@home.com, Sheepman , freebsd-stable@FreeBSD.ORG In-Reply-To: <4.1.19991212114203.00959100@mail.udel.edu> References: <3.0.6.32.19991212184024.0097fa70@netcore.home> <4.1.19991212111055.009552e0@mail.udel.edu> <3.0.6.32.19991212141700.007e2ac0@netcore.home> <7101.991211@Home.Com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >If you're running windows boxen behind your FreeBSD server, then (at least >I think) the EASIEST way to solve your problem is to run IRC clients on >yoru windows boxen which contain identd servers to themselves. This This is correct, but doesn't help the actual problem because internal boxes never get those ident requests. The scenario here is that upon connecting to an irc server, the server asks from your BSD server's identd who the heck that user is. FreeBSD's identd server has no way of knowing that this request should be forwarded to a NAT'ed windows box X. So, there will never be an identd request from irc server to MIRC to respond to. The working behaviour could probably be achieves so that the identd server on FreeBSD examined NAT state data and forwarded requests appropriately (if the server was configured to forward them - this could be security risk too). You could, of course, redirect all identd requests coming on your FreeBSD box to the internal windows box, but this would break the BSD box pretty badly. (e.g. login timeouts when using FTP) - and there could be only one computer in your private LAN that'd use ident. One solution might be to use an appropriate proxy/bouncer in the FreeBSD box and connect to it using IRC clients, but I wouldn't want to do that. Pekka Savola pekkas@netcore.fi --- Across the nations the stories spread like spiderweb laid upon spiderweb, and men and women planned the future, believing they knew truth. They planned, and the Pattern absorbed their plans, weaving toward the future foretold. -- Robert Jordan: The Path of Daggers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 10: 1:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from netcore.fi (netcore.fi [193.94.160.1]) by hub.freebsd.org (Postfix) with ESMTP id D44D414C80 for ; Sun, 12 Dec 1999 10:01:45 -0800 (PST) (envelope-from Pekka.Savola@netcore.fi) Received: from unf (netcore.fi [193.94.160.1]) by netcore.fi (8.9.3/8.9.3) with SMTP id UAA17693 for ; Sun, 12 Dec 1999 20:01:41 +0200 Message-Id: <3.0.6.32.19991212200222.00798800@netcore.home> X-Sender: pekkas@netcore.home X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 12 Dec 1999 20:02:22 +0200 To: freebsd-stable@freebsd.org From: Pekka Savola Subject: Selecting which programs to have in the base system Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I posted this to freebsd-newbies (this seems like a newbie/faq question to me) a day or two ago but got no answer. So let's try this list.. How can I manipulate -easily- which base system files (in e.g. /bin, /sbin, /usr/bin, /usr/sbin) will be installed/compiled when I cvsup the sources and make world ? The problem is, according to /var/log/setuid.today, I have ~70 files (some of them just symbolic links though) which are setuid root (95% of them from base system). Talk about security! I'd like to remove the ones I don't need and never hear of them again (like ppp*, r*, yp*). Also, having stuff like this along just takes some HDD space too. I couldn't care less of having e.g. some games in my system. So, are there any utilities to keep track which base programs/sources are installed and which are not - and how to keep them that way so that upgrading the sources, 'make world', etc. won't mess those up? Btw, regarding setuid.today.. are there any good "master" references which files in the base system really need to be +s ? I can't believe all ~70 of them have to be... Regards, Pekka Savola Pekka Savola pekkas@netcore.fi --- Across the nations the stories spread like spiderweb laid upon spiderweb, and men and women planned the future, believing they knew truth. They planned, and the Pattern absorbed their plans, weaving toward the future foretold. -- Robert Jordan: The Path of Daggers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 10: 2:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2C84F14C80 for ; Sun, 12 Dec 1999 10:02:56 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p27-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.124]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id DAA02887; Mon, 13 Dec 1999 03:02:17 +0900 (JST) Message-ID: <3853E284.3C8B67F4@newsguy.com> Date: Mon, 13 Dec 1999 02:59:32 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: Pekka Savola Cc: John , williamsl@home.com, Sheepman , freebsd-stable@FreeBSD.ORG Subject: Re: pidentd References: <3.0.6.32.19991212184024.0097fa70@netcore.home> <4.1.19991212111055.009552e0@mail.udel.edu> <3.0.6.32.19991212141700.007e2ac0@netcore.home> <7101.991211@Home.Com> <3.0.6.32.19991212190534.007ec9b0@netcore.home> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pekka Savola wrote: > > This is correct, but doesn't help the actual problem because internal boxes > never get those ident requests. _This_ is the problem, and the correct solution is NAT understanding identd protocol. It's not even that difficult. -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 12:16:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id E30DE14C30 for ; Sun, 12 Dec 1999 12:16:21 -0800 (PST) (envelope-from greg@snickers.org) Received: from cs219478a ([24.66.4.247]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with SMTP id <19991212201620.YRCU9271.mail.rdc2.on.home.com@cs219478a> for ; Sun, 12 Dec 1999 12:16:20 -0800 Reply-To: From: "Greg Prosser" To: "freebsd" Subject: SYN Hardening patches? / SYN Code in 3.4-RC Date: Sun, 12 Dec 1999 15:16:18 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey guys, sorry to throw off your weekends, but I have a few quick questions that I'd like answers to, and searches turn up fairly little. First of all, I operate a machine that frequently comes under heavy denial of service attacks, which often include SYN attacks. This often causes kernel panics and reboots with messages logged as '/kernel: Out of mbuf clusters - adjust NMBCLUSTERS or increase maxusers!'. I had maxusers at 256 at that point, and had 'options NMBCLUSTERS=2048' in the kernel as well -- it still failed. I'm hoping that increasing maxusers to 512, and bumping NMBCLUSTERS to 4096 is going to provide some help, but somehow I doubt it. (1MB/s of SYN packets coming in does not fare well, and the unplanned boots are wreaking havok on my filesystems). I don't know what mbuf clusters even are, so any light on the situation there could help too. As far as I've found, mbuf clusters are simply the 'backlog' created by sending syn packets? For open sockets and the like.. I've explored LINT, and come across these options: # TCP_DROP_SYNFIN adds support for ignoring TCP packets with SYN+FIN. This # prevents nmap et al. from identifying the TCP/IP stack, but breaks support # for RFC1644 extensions and is not recommended for web servers. # # TCP_RESTRICT_RST adds support for blocking the emission of TCP RST packets. # This is useful on systems which are exposed to SYN floods (e.g. IRC servers) # or any system which one does not want to be easily portscannable. # options TCP_DROP_SYNFIN #drop TCP packets with SYN+FIN options TCP_RESTRICT_RST #restrict emission of TCP RST I added the second to the last kernel that did fault, and omitted the first because we do run a webserver, and it just had that spooky sound with it that rm -rf / gives off :) I've also come across a patch posted to a mailing list for FreeBSD 3.1, for SYN_RATELIM'ing, sounds like this could also help. I'm at a complete loss for what to do here -- I'd like the reboots to stop. Any help you could give me at all would be appreciated, whacks with clue-by-fours aren't that bad either. Thanks in advance! . . . ... .. . .. .... . x y s t @ s t r a y n e t . c o m __ senior administrator, straynet online .--.--.--.--.-----.| |_ it was designed to do that. honest. |_ _| | |__ --|| _| icq: 10405504 aol im: xysters |__.__|___ |_____||____| |_____| Jennifer Lopez? -- Now THAT's big endian! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 12:23:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id 7EF7014C2C for ; Sun, 12 Dec 1999 12:23:08 -0800 (PST) (envelope-from greg@snickers.org) Received: from cs219478a ([24.66.4.247]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with SMTP id <19991212202307.YVAM9271.mail.rdc2.on.home.com@cs219478a> for ; Sun, 12 Dec 1999 12:23:07 -0800 Reply-To: From: "Greg Prosser" To: "freebsd" Subject: RE: SYN Hardening patches? / SYN Code in 3.4-RC Date: Sun, 12 Dec 1999 15:23:07 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Erm, Oopsy-daisy, the SYN_RATELIM patch is at: http://www2.merton.ox.ac.uk/~security/archive-199905/0282.html . . . ... .. . .. .... . x y s t @ s t r a y n e t . c o m __ senior administrator, straynet online .--.--.--.--.-----.| |_ it was designed to do that. honest. |_ _| | |__ --|| _| icq: 10405504 aol im: xysters |__.__|___ |_____||____| |_____| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 13: 7: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id B752E154B5 for ; Sun, 12 Dec 1999 13:06:58 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 11xGCn-000EbQ-00; Sun, 12 Dec 1999 13:06:57 -0800 Date: Sun, 12 Dec 1999 13:06:53 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Greg Prosser Cc: freebsd Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC 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 Sun, 12 Dec 1999, Greg Prosser wrote: > clusters - adjust NMBCLUSTERS or increase maxusers!'. I had maxusers at 256 > at that point, and had 'options NMBCLUSTERS=2048' in the kernel as well -- I hope you realize that 2048 is quite a small number of mbufs. I'm not surprised your servers runs out so quickly. You won't be able to handle any serious amount of network traffic with so few mbufs. Setting maxusers to 256 isn't help you any at all, btw. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 13:52:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id CA77014D23 for ; Sun, 12 Dec 1999 13:52:15 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.24.242] (dialup498.brussels2.skynet.be [195.238.24.242]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id WAA22995; Sun, 12 Dec 1999 22:51:56 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912111952.LAA01097@vashon.polstra.com> References: <199912111932.MAA06773@freeway.dcfinc.com> <199912111952.LAA01097@vashon.polstra.com> Date: Sun, 12 Dec 1999 22:21:22 +0100 To: John Polstra , chad@DCFinc.com From: Brad Knowles Subject: Re: Route table leaks Cc: stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:52 AM -0800 1999/12/11, John Polstra wrote: > It doesn't happen on most 3.x or 4.x systems either. For starters, > you won't see it unless you're running routed. Even then, you may > or may not see it. I don't know whether the bug is present in 2.2 > or not. I wasn't running routed (or gated, or anything else like either of these) on any of the boxes I reported on. It was the default route that was nailing me (found on both 3.0-RELEASE and 3.2-RELEASE). -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 13:52:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id DB6F3151F6 for ; Sun, 12 Dec 1999 13:52:22 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.24.242] (dialup498.brussels2.skynet.be [195.238.24.242]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id WAA23045; Sun, 12 Dec 1999 22:52:08 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912112029.MAA10532@gndrsh.dnsmgr.net> References: <199912112029.MAA10532@gndrsh.dnsmgr.net> Date: Sun, 12 Dec 1999 22:22:01 +0100 To: "Rodney W. Grimes" , jdp@polstra.com (John Polstra) From: Brad Knowles Subject: Re: Route table leaks Cc: chad@DCFinc.com, stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:29 PM -0800 1999/12/11, Rodney W. Grimes wrote: > I haven't run routed in 5 years, I see it. You meant ``a dynamic routing > daemon'', and/or doing manual route delete's. Either of those can cause > the leak. Right -- manual such as setting up a default route. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 13:52:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 86A9A15234 for ; Sun, 12 Dec 1999 13:52:23 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.24.242] (dialup498.brussels2.skynet.be [195.238.24.242]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id WAA23082; Sun, 12 Dec 1999 22:52:16 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Sun, 12 Dec 1999 22:27:48 +0100 To: , "freebsd" From: Brad Knowles Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 3:16 PM -0500 1999/12/12, Greg Prosser wrote: > I'm hoping that increasing maxusers to 512, and bumping NMBCLUSTERS to 4096 > is going to provide some help, but somehow I doubt it. (1MB/s of SYN packets > coming in does not fare well, and the unplanned boots are wreaking havok on > my filesystems). It was my understanding that there was a problem with setting maxusers above 128 (at least on 3.2-RELEASE). I haven't exceeded 128 on any of my boxes, although I have increased NMBCLUSTERS to 16384 on the one box where I got those kind of errors under heavy load. > # TCP_DROP_SYNFIN adds support for ignoring TCP packets with SYN+FIN. This > # prevents nmap et al. from identifying the TCP/IP stack, but breaks support > # for RFC1644 extensions and is not recommended for web servers. Huh. I'd be real interested to know how ignoring SYN+FIN breaks support for RFC1644 or causes problems for web servers. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 14: 8:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from radio.bicnet.net (radio.bicnet.net [199.190.243.202]) by hub.freebsd.org (Postfix) with ESMTP id BA77814D8F for ; Sun, 12 Dec 1999 14:08:17 -0800 (PST) (envelope-from john@loverso.southborough.ma.us) Received: from loverso.southborough.ma.us (dial-pop2-80.bicnet.net [208.220.71.80]) by radio.bicnet.net (8.8.5/8.6.12) with ESMTP id RAA23974; Sun, 12 Dec 1999 17:11:57 -0500 (EST) Received: from loverso.southborough.ma.us (localhost [127.0.0.1]) by loverso.southborough.ma.us (8.9.3/8.6.9) with ESMTP id RAA09606; Sun, 12 Dec 1999 17:08:13 -0500 (EST) Message-Id: <199912122208.RAA09606@loverso.southborough.ma.us> To: Brad Knowles Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC In-reply-to: Message from Brad Knowles . X-Face: "UZ!}1W2N?eJdN(`1%|/OOPqJ).Idk?UyvWw'W-%`Gto8^IkEm>.g1O$[.;~}8E=Ire0|lO .o>:NlJS1@vO9bVmswRoq3j DdX9YGSeJ5a(mfX[1u>Z63G5_^+'8LVqjqvn X-Url: http://surf.to/loverso Date: Sun, 12 Dec 1999 17:08:13 -0500 From: John Robert LoVerso Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Huh. I'd be real interested to know how ignoring SYN+FIN breaks > support for RFC1644 or causes problems for web servers. RFC 1644 defines "T/TCP: TCP Extensions for Transactions", which describes a way to to a complete transactional TCP session with as little as two total datagrams. The first datagram has both SYN and FIN flags set. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 14:11: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id D79E414D68 for ; Sun, 12 Dec 1999 14:10:59 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.24.242] (dialup498.brussels2.skynet.be [195.238.24.242]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id XAA07958; Sun, 12 Dec 1999 23:10:54 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912122208.RAA09606@loverso.southborough.ma.us> References: <199912122208.RAA09606@loverso.southborough.ma.us> Date: Sun, 12 Dec 1999 23:09:55 +0100 To: John Robert LoVerso From: Brad Knowles Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 5:08 PM -0500 1999/12/12, John Robert LoVerso wrote: > RFC 1644 defines "T/TCP: TCP Extensions for Transactions", which describes > a way to to a complete transactional TCP session with as little as two total > datagrams. The first datagram has both SYN and FIN flags set. Thanks! Looks like I need to do some readin'.... -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 14:46:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 7E1C714BE2 for ; Sun, 12 Dec 1999 14:46:21 -0800 (PST) (envelope-from noslenj@swbell.net) Received: from swbell.net ([207.193.26.182]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMN00G2SGKUWK@mta1.rcsntx.swbell.net> for freebsd-stable@FreeBSD.ORG; Sun, 12 Dec 1999 16:46:08 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by swbell.net (8.9.3/8.9.3) with ESMTP id QAA00556; Sun, 12 Dec 1999 16:33:01 -0600 (CST envelope-from noslenj@swbell.net) Date: Sun, 12 Dec 1999 16:33:01 -0600 (CST) From: Jay Nelson Subject: Re: PS/2 mouse troubles? In-reply-to: <3.0.6.32.19991212143214.00b32200@pop.ajiang.com> To: Alvin Jiang 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 On Sun, 12 Dec 1999, Alvin Jiang wrote: >Hmm, I just solved this problem last night. It took me all of 5 mins to >search "psmintr" and find the solution at: > >http://www.freebsd.org/FAQ/x.html#AEN2255 > >You'd probably save a lot of time if you read the FAQ, rather than post and >wait for a reply. Unfortunately, the suggested remedy only compounded the problem. Setting the psm0 flags to 0x100 killed X when the mouse lost sync. Running moused and using sysmouse caused extremely eratic behavior. Without moused and using /dev/psm0 for X simply froze the mouse -- although switching to another console and back seemed to work. It appears to be an old problem resurfacing. Were it not for the fact that I've had no problems before I built world from sources supped Saturday morning -- and there have been syscons changes since my previous sup, I would write it off to a dying mouse and go on. Given the changes and a new release coming up, I though it would be worth raising the flag. -- Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 15: 1:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 093FD14DE4 for ; Sun, 12 Dec 1999 15:01:46 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id SAA04361; Sun, 12 Dec 1999 18:01:38 -0500 (EST) Date: Sun, 12 Dec 1999 18:01:38 -0500 (EST) From: Bosko Milekic To: Tom Cc: Greg Prosser , freebsd Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC 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 Sun, 12 Dec 1999, Tom wrote: !> !> Setting maxusers to 256 isn't help you any at all, btw. !> !>Tom !> This is simply untrue. MAXUSERS directly influences the number of mbufs which, in turn, influence the size of mb_map. Bumping up MAXUSERS in reasonable amounts will, in fact, contribute to a larger mb_map. -- Bosko Milekic http://pages.infinit.net/bmilekic/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 15:10:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id CC12A14EF8 for ; Sun, 12 Dec 1999 15:10:32 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id PAA04846; Sun, 12 Dec 1999 15:08:41 -0800 (PST) Message-Id: <199912122308.PAA04846@implode.root.com> To: greg@snickers.org Cc: "freebsd" Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC In-reply-to: Your message of "Sun, 12 Dec 1999 15:16:18 EST." From: David Greenman Reply-To: dg@root.com Date: Sun, 12 Dec 1999 15:08:41 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >clusters - adjust NMBCLUSTERS or increase maxusers!'. I had maxusers at 256 >at that point, and had 'options NMBCLUSTERS=2048' in the kernel as well -- >it still failed. > I'm hoping that increasing maxusers to 512, and bumping NMBCLUSTERS to 4096 >is going to provide some help, but somehow I doubt it. (1MB/s of SYN packets >coming in does not fare well, and the unplanned boots are wreaking havok on >my filesystems). Leave maxusers at 256 and increase NMBCLUSTERS even more. Depending on how much physical memory the machine has you could increase it to 10X what you have now, but keep in mind that each one consumes 2KB of RAM, so you could end up using a lot of memory for buffers after the attack occurs. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 15:11:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from implode.root.com (root.com [209.102.106.178]) by hub.freebsd.org (Postfix) with ESMTP id DC3E414DA2 for ; Sun, 12 Dec 1999 15:11:55 -0800 (PST) (envelope-from dg@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id PAA04823; Sun, 12 Dec 1999 15:06:19 -0800 (PST) Message-Id: <199912122306.PAA04823@implode.root.com> To: Bosko Milekic Cc: Tom , Greg Prosser , freebsd Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC In-reply-to: Your message of "Sun, 12 Dec 1999 18:01:38 EST." From: David Greenman Reply-To: dg@root.com Date: Sun, 12 Dec 1999 15:06:19 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >On Sun, 12 Dec 1999, Tom wrote: > >!> >!> Setting maxusers to 256 isn't help you any at all, btw. >!> >!>Tom >!> > > This is simply untrue. > > MAXUSERS directly influences the number of mbufs which, in turn, > influence the size of mb_map. Bumping up MAXUSERS in reasonable amounts > will, in fact, contribute to a larger mb_map. Only if you don't specify NMBCLUSTERS, which the original poster did. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org Creator of high-performance Internet servers - http://www.terasolutions.com Pave the road of life with opportunities. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 15:37:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 89D5714CF3 for ; Sun, 12 Dec 1999 15:37:49 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id PAA19622; Sun, 12 Dec 1999 15:37:44 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id PAA03667; Sun, 12 Dec 1999 15:37:44 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 12 Dec 1999 15:37:44 -0800 (PST) Message-Id: <199912122337.PAA03667@vashon.polstra.com> To: unicorn@blackhats.org Subject: Re: SetAttrs src/contrib/diff/diff3.c,v In-Reply-To: <19991203214401.H33150@unicorn.blackhats.org> References: <19991203214401.H33150@unicorn.blackhats.org> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991203214401.H33150@unicorn.blackhats.org>, The Unicorn wrote: > > Just wondering why I see a *LOT* (as in one for each source file on the > system) of SetAttrs messages coming over my screen, when I am cvsupping > 3.3-STABLE on one system I own. While other systems act normally > (loading delta's and other stuff)... Make sure you run cvsup as the same user and with the same umask each time. You can specify the umask in the supfile if you want to be sure about that. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 16:19:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles552.castles.com [208.214.165.116]) by hub.freebsd.org (Postfix) with ESMTP id 0CB1114E32; Sun, 12 Dec 1999 16:19:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA04346; Sun, 12 Dec 1999 16:21:15 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130021.QAA04346@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Juergen Lock Cc: Mike Smith , zzhang@cs.binghamton.edu, freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: loader hacks (was: Re: easyboot far into disk) In-reply-to: Your message of "Sun, 12 Dec 1999 15:59:32 +0100." <19991212155932.A1107@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Dec 1999 16:21:15 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I thought rootdev was fixed a long time back. If it's not, please tell > > > me and I'll fix it again. 8) > > > > Alright I finally got around testing this with a later kern.flp > > (3.3-R actually), and it still didn't work. ... > > Well i played with this once more yesterday and now i know what was > wrong: Unlike currdev, rootdev needs a `:' at the end... So either > I'm blind or the manpage needs fixing. :) The manpage is probably wrong. $rootdev is obsolete and will be removed for 4.x (if I remember). > I also actually started making that FAQ entry (yeah!), and then > wondered if you could also make an automagic boot floppy for a root > disk that is entirely invisible to the BIOS, like when its on a > BIOS-less (but otherwise supported) SCSI controller. I didn't find > a way to do it with the original (-stable) loader, but when i made > this patch, 4.x does this differently (better) by passing in a complete identifier. I need to update the online help and manpage for it. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 16:35:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.eclipse.net (mail.eclipse.net [207.207.192.13]) by hub.freebsd.org (Postfix) with ESMTP id 2464D14F1A for ; Sun, 12 Dec 1999 16:35:50 -0800 (PST) (envelope-from spiffer@eclipse.net) Received: from phil1-02-132.eclipse.net (phil1-02-132.eclipse.net [207.207.238.132]) by mail.eclipse.net (8.9.1a/8.9.1) with ESMTP id TAA28376 for ; Sun, 12 Dec 1999 19:35:48 -0500 (EST) Date: Sun, 12 Dec 1999 19:19:33 -0500 (EST) From: "Roger W." X-Sender: spiffer@deepthought.invalid To: freebsd-stable@FreeBSD.org Subject: printer problems using 3.4RC kernel 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 Hello everyone, I've just finished cvsup'ing 3.3-stable, to bring my 3.3-Release system up to date. Everything went fine and seems to be working except for my laser jet printer. Its a NEC SuperScript 870 which emulates to a HPLJ IIP. The printer gets recognized fine during bootup and everthing appears to be OK until I try to send roughly more than 1 page of data to it. The page can be sent by cat 'filename' | lpr, using a2ps, or just dumping from a webpage with html, it doesn't seem to matter. What happens is I only get a small amout of data on each page, and then the next page is sucked into the printer and again only a small amount of data is placed on it. I am using apsfilter as the printers textfilter. I compared my boot logs with the new kernel to the GENERIC 3.3R kernel I was using previously, and there isn't a bit of difference in them. All I did was eliminate devices that weren't getting found anyways. I'm sure it has to do with the kernel, or its config, as if I boot off my old GENERIC kernel my printer functions properly. The one thing I've noticed is when the printer is working correctly, there is significantly more delay from when I send the printjob to the printer, and when it starts printing. Booting off of the kernel I compiled, there is almost no delay between when I tell the system to print, and when the printer starts to suck in the paper and print out small portions of what it should be printing spread out over many pages. If anyone else is seeing this problem and has any ideas, I would love to hear them. thank you, Roger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 17: 3:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id 5131514E36 for ; Sun, 12 Dec 1999 17:03:32 -0800 (PST) (envelope-from papalia@UDel.Edu) Received: from morgaine (host75-157.student.udel.edu [128.175.75.157]) by copland.udel.edu (8.9.3/8.9.3) with SMTP id UAA09810; Sun, 12 Dec 1999 20:03:23 -0500 (EST) Message-Id: <4.1.19991212200211.0093e390@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 12 Dec 1999 20:03:32 -0500 To: Pekka Savola From: John Subject: Re: pidentd Cc: williamsl@home.com, Sheepman , freebsd-stable@FreeBSD.ORG In-Reply-To: <3.0.6.32.19991212190534.007ec9b0@netcore.home> References: <4.1.19991212114203.00959100@mail.udel.edu> <3.0.6.32.19991212184024.0097fa70@netcore.home> <4.1.19991212111055.009552e0@mail.udel.edu> <3.0.6.32.19991212141700.007e2ac0@netcore.home> <7101.991211@Home.Com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>If you're running windows boxen behind your FreeBSD server, then (at least >>I think) the EASIEST way to solve your problem is to run IRC clients on >>yoru windows boxen which contain identd servers to themselves. This > >This is correct, but doesn't help the actual problem because internal boxes >never get those ident requests. > >The scenario here is that upon connecting to an irc server, the server asks >from your BSD server's identd who the heck that user is. FreeBSD's identd >server has no way of knowing that this request should be forwarded to a >NAT'ed windows box X. So, there will never be an identd request from irc >server to MIRC to respond to. The working behaviour could probably be >achieves so that the identd server on FreeBSD examined NAT state data and >forwarded requests appropriately (if the server was configured to forward >them - this could be security risk too). > >You could, of course, redirect all identd requests coming on your FreeBSD >box to the internal windows box, but this would break the BSD box pretty >badly. (e.g. login timeouts when using FTP) - and there could be only one >computer in your private LAN that'd use ident. > >One solution might be to use an appropriate proxy/bouncer in the FreeBSD >box and connect to it using IRC clients, but I wouldn't want to do that. I went back through my notes from earlier this year, and alas discovered that I never did solve the problem you're describing. And at the time of my posting a response to your answer, I guess I wasn't awake enough to fully absorb the question. Simply put, I'd like to apologize for posting a useless answer that didn't help in the slightest :) Regards, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 17: 4:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id A034A14D39 for ; Sun, 12 Dec 1999 17:04:22 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:fAw5mWEucg7JR5eZHjKXL+qVL97tsFNq@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id JAA23247; Mon, 13 Dec 1999 09:56:59 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id KAA12934; Mon, 13 Dec 1999 10:02:00 +0900 (JST) Message-Id: <199912130102.KAA12934@zodiac.mech.utsunomiya-u.ac.jp> To: Jay Nelson Cc: Alvin Jiang , freebsd-stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: PS/2 mouse troubles? In-reply-to: Your message of "Sun, 12 Dec 1999 16:33:01 CST." References: Date: Mon, 13 Dec 1999 10:01:59 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Unfortunately, the suggested remedy only compounded the problem. >Setting the psm0 flags to 0x100 killed X when the mouse lost sync. >Running moused and using sysmouse caused extremely eratic behavior. >Without moused and using /dev/psm0 for X simply froze the mouse -- >although switching to another console and back seemed to work. Would you please provide the following information. 1. The model of your Logitech PS/2 mouse. 2. When booting the system, give "boot -v" at the loader prompt to obtain verbose messages, and send us /var/log/dmesg.boot. 3. Run `moused' as follows and show us the output. moused -i all -d -p /dev/psm0 4. Tell me if you are using some sort of console switch. (We have had a lot of troubles with consoles switches.) 5. How did you start `moused'? What options did you gave? >It appears to be an old problem resurfacing. Were it not for the fact >that I've had no problems before I built world from sources supped >Saturday morning -- and there have been syscons changes since my >previous sup, I would write it off to a dying mouse and go on. When the X server is directly accessing /dev/psm0, syscons has nothing to do with mouse data stream. Syscons/sysmouse see mouse data only when you run moused. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 17:33:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id 53D9A14C7F for ; Sun, 12 Dec 1999 17:33:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA04626; Sun, 12 Dec 1999 17:35:56 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912130135.RAA04626@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Roger W." Cc: freebsd-stable@FreeBSD.org Subject: Re: printer problems using 3.4RC kernel In-reply-to: Your message of "Sun, 12 Dec 1999 19:19:33 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 12 Dec 1999 17:35:56 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You're not clear about what you're printing, where you're printing it to, or what the actual output looks like, but these symptoms are entirely consistent with you trying to print plain text or some other encoding to the printer. You need to ensure that you're actually printing to the correct printer device. > Hello everyone, > > I've just finished cvsup'ing 3.3-stable, to bring my 3.3-Release system up > to date. Everything went fine and seems to be working except for my laser > jet printer. Its a NEC SuperScript 870 which emulates to a HPLJ IIP. The > printer gets recognized fine during bootup and everthing appears to be OK > until I try to send roughly more than 1 page of data to it. The page can > be sent by cat 'filename' | lpr, using a2ps, or just dumping from a > webpage with html, it doesn't seem to matter. What happens is I only get > a small amout of data on each page, and then the next page is sucked into > the printer and again only a small amount of data is placed on it. I am > using apsfilter as the printers textfilter. > > I compared my boot logs with the new kernel to the GENERIC 3.3R kernel I > was using previously, and there isn't a bit of difference in them. All I > did was eliminate devices that weren't getting found anyways. I'm sure it > has to do with the kernel, or its config, as if I boot off my old GENERIC > kernel my printer functions properly. > > The one thing I've noticed is when the printer is working correctly, there > is significantly more delay from when I send the printjob to the printer, > and when it starts printing. Booting off of the kernel I compiled, there > is almost no delay between when I tell the system to print, and when the > printer starts to suck in the paper and print out small portions of what > it should be printing spread out over many pages. > > If anyone else is seeing this problem and has any ideas, I would love to > hear them. > > thank you, > > Roger > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 17:48:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 8C79B14CF3 for ; Sun, 12 Dec 1999 17:48:08 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id UAA01580; Sun, 12 Dec 1999 20:48:03 -0500 (EST) Date: Sun, 12 Dec 1999 20:48:03 -0500 (EST) From: Bosko Milekic To: David Greenman Cc: Tom , Greg Prosser , freebsd Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC In-Reply-To: <199912122306.PAA04823@implode.root.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 Sun, 12 Dec 1999, David Greenman wrote: !>>On Sun, 12 Dec 1999, Tom wrote: !>> !>>!> !>>!> Setting maxusers to 256 isn't help you any at all, btw. !>>!> !>>!>Tom !>>!> !>> !>> This is simply untrue. !>> !>> MAXUSERS directly influences the number of mbufs which, in turn, !>> influence the size of mb_map. Bumping up MAXUSERS in reasonable amounts !>> will, in fact, contribute to a larger mb_map. !> !> Only if you don't specify NMBCLUSTERS, which the original poster did. !> !>-DG !> !>David Greenman !>Co-founder/Principal Architect, The FreeBSD Project - http://www.freebsd.org !>Creator of high-performance Internet servers - http://www.terasolutions.com !>Pave the road of life with opportunities. !> Even at that, MAXUSERS still contributes to the mb_map size. I see your point, though, in the sense that by setting up NMBCLUSTERS, the overall size of mb_map will be affected by that setting, and not MAXUSERS, in general. So here's the question: Why not remove MAXUSERS' influence over the size of the mb_map, and just have it influenced by a single option? -- Bosko Milekic http://pages.infinit.net/bmilekic/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 17:49:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from elektron.elka.pw.edu.pl (elektron.elka.pw.edu.pl [148.81.63.249]) by hub.freebsd.org (Postfix) with ESMTP id BBC6B14C7F for ; Sun, 12 Dec 1999 17:49:29 -0800 (PST) (envelope-from M.Rzepkowski@casablanca.com.pl) Received: from beta.ire.pw.edu.pl ([148.81.68.100]:4770 "HELO alien") by elektron.elka.pw.edu.pl with SMTP id ; Mon, 13 Dec 1999 02:49:01 +0100 Message-ID: <004901bf450c$2bfa20c0$0f02000a@alien> From: "Rzepkowski Maciej" To: Subject: Date: Mon, 13 Dec 1999 02:48:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2615.200 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2615.200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 18: 7: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id F298214E36 for ; Sun, 12 Dec 1999 18:07:03 -0800 (PST) (envelope-from noslenj@swbell.net) Received: from swbell.net ([207.193.25.216]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMN0000ZPVF0J@mta4.rcsntx.swbell.net> for freebsd-stable@freebsd.org; Sun, 12 Dec 1999 20:06:57 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by swbell.net (8.9.3/8.9.3) with ESMTP id UAA00471; Sun, 12 Dec 1999 20:02:19 -0600 (CST envelope-from noslenj@swbell.net) Date: Sun, 12 Dec 1999 20:02:19 -0600 (CST) From: Jay Nelson Subject: Re: PS/2 mouse troubles? In-reply-to: <199912130102.KAA12934@zodiac.mech.utsunomiya-u.ac.jp> To: Kazutaka YOKOTA Cc: freebsd-stable@freebsd.org Message-id: MIME-version: 1.0 Content-type: MULTIPART/MIXED; BOUNDARY="0-244944148-945050539=:318" 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-244944148-945050539=:318 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 13 Dec 1999, Kazutaka YOKOTA wrote: >>Unfortunately, the suggested remedy only compounded the problem. >>Setting the psm0 flags to 0x100 killed X when the mouse lost sync. >>Running moused and using sysmouse caused extremely eratic behavior. >>Without moused and using /dev/psm0 for X simply froze the mouse -- >>although switching to another console and back seemed to work. > >Would you please provide the following information. > >1. The model of your Logitech PS/2 mouse. MouseMan Serial-MousePort Model M-CQ38 >2. When booting the system, give "boot -v" at the loader prompt > to obtain verbose messages, and send us /var/log/dmesg.boot. It's attached. I've had some problems recently with attachments disappearing. If this doesn't come through, let me know and I'll mail it direct. Without the mime header, things seem to work as expected. >3. Run `moused' as follows and show us the output. > moused -i all -d -p /dev/psm0 moused: proto params: f8 80 00 00 8 00 ff /dev/psm0 ps/2 sysmouse generic >4. Tell me if you are using some sort of console switch. > (We have had a lot of troubles with consoles switches.) No switch. Plugged directly into an Asus T2P4. >5. How did you start `moused'? What options did you gave? This was the setting used successfully for over a year and the one that originally was in effect the problem first came up. I did add '-d' to the flags and did not try "all" for moused_type. From /etc/rc.conf: moused_enable="YES" moused_port="/dev/psm0" moused_type="ps/2" moused_flags="" allscreens_flags="-m on" >When the X server is directly accessing /dev/psm0, syscons has nothing >to do with mouse data stream. Syscons/sysmouse see mouse data only >when you run moused. I'm not sure it has much to do with moused, either. If I run moused, I get erratic behavior just before the freeze -- but without moused, I simply get a freeze. I still can't tell whether this is a software problem -- or I've got a mouse going out coincidentally with my last sup. For the record, I did not clean out /usr/obj before the last makeworld. The -d switch to moused hasn't yielded any noticable information except: Dec 12 15:03:30 acp /kernel: sc0: sc_switch_scr() 4 Dec 12 15:03:32 acp /kernel: sc0: sc_switch_scr() 1 But since I was leaving X, these didn't seem out of line. As additional information, which may not be relevant, I've been using kshisen to test this (which hasn't been rebuilt since about 3.1) and the problem only seems to occur with high mouse activity. Normal xterm activity doesn't seem to show the problem. I've also had some problems with pppd and the serial port (where userland ppp works fine) but so far, I haven't been able to log anything that sheds any light. I'm using the same scripts I've used successfully since 2.2.5. The only real connecton I've seen is that some of the time, the erratic mouse behavior occurs at the time pppd tries to connect. I don't know whether the pppd problem is related or not, but it's the only other external symptom that I've noticed that I can pass on. -- Jay --0-244944148-945050539=:318 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.boot" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg.boot" LCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTANCglzdWJvcmRpbmF0ZWJ1cz0wIAlz ZWNvbmRhcnlidXM9MA0KY2hpcDA6IDxJbnRlbCA4MjQzOUhYIFBDSSBjYWNo ZSBtZW1vcnkgY29udHJvbGxlcj4gcmV2IDB4MDMgb24gcGNpMC4wLjANCmZv dW5kLT4JdmVuZG9yPTB4ODA4NiwgZGV2PTB4NzAwMCwgcmV2aWQ9MHgwMQ0K CWNsYXNzPTA2LTAxLTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTENCglzdWJv cmRpbmF0ZWJ1cz0wIAlzZWNvbmRhcnlidXM9MA0KY2hpcDE6IDxJbnRlbCA4 MjM3MVNCIFBDSSB0byBJU0EgYnJpZGdlPiByZXYgMHgwMSBvbiBwY2kwLjcu MA0KCUkvTyBSZWNvdmVyeSBUaW1pbmc6IDgtYml0IDMuNSBjbG9ja3MsIDE2 LWJpdCAzLjUgY2xvY2tzDQoJRXh0ZW5kZWQgQklPUzogZGlzYWJsZWQNCglM b3dlciBCSU9TOiBkaXNhYmxlZA0KCUNvcHJvY2Vzc29yIElSUTEzOiBlbmFi bGVkDQoJTW91c2UgSVJRMTI6IGRpc2FibGVkDQoJSW50ZXJydXB0IFJvdXRp bmc6IEE6IGRpc2FibGVkLCBCOiBJUlExMSwgQzogZGlzYWJsZWQsIEQ6IGRp c2FibGVkDQoJCU1CMDogZGlzYWJsZWQsIE1CMTogDQpmb3VuZC0+CXZlbmRv cj0weDgwODYsIGRldj0weDcwMTAsIHJldmlkPTB4MDANCgljbGFzcz0wMS0w MS04MCwgaGRydHlwZT0weDAwLCBtZmRldj0wDQoJc3Vib3JkaW5hdGVidXM9 MCAJc2Vjb25kYXJ5YnVzPTANCgltYXBbMF06IHR5cGUgNCwgcmFuZ2UgMzIs IGJhc2UgMDAwMGU4MDAsIHNpemUgIDQNCmlkZV9wY2kwOiA8SW50ZWwgUElJ WDMgQnVzLW1hc3RlciBJREUgY29udHJvbGxlcj4gcmV2IDB4MDAgb24gcGNp MC43LjENCmZvdW5kLT4JdmVuZG9yPTB4MTAwMiwgZGV2PTB4NDc1OCwgcmV2 aWQ9MHgwMQ0KCWNsYXNzPTAzLTAwLTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2 PTANCglzdWJvcmRpbmF0ZWJ1cz0wIAlzZWNvbmRhcnlidXM9MA0KCW1hcFsw XTogdHlwZSAxLCByYW5nZSAzMiwgYmFzZSBlNzAwMDAwMCwgc2l6ZSAyMw0K dmdhMDogPEFUSSBNYWNoNjQtR1ggZ3JhcGhpY3MgYWNjZWxlcmF0b3I+IHJl diAweDAxIG9uIHBjaTAuOS4wDQpmb3VuZC0+CXZlbmRvcj0weDEwMDAsIGRl dj0weDAwMDQsIHJldmlkPTB4MDQNCgljbGFzcz0wMS0wMC0wMCwgaGRydHlw ZT0weDAwLCBtZmRldj0wDQoJc3Vib3JkaW5hdGVidXM9MCAJc2Vjb25kYXJ5 YnVzPTANCglpbnRwaW49YSwgaXJxPTExDQoJbWFwWzBdOiB0eXBlIDQsIHJh bmdlIDMyLCBiYXNlIDAwMDBlMDAwLCBzaXplICA4DQoJbWFwWzFdOiB0eXBl IDEsIHJhbmdlIDMyLCBiYXNlIGU2ODAwMDAwLCBzaXplICA4DQpuY3IwOiA8 bmNyIDUzYzgxNSBmYXN0MTAgc2NzaT4gcmV2IDB4MDQgaW50IGEgaXJxIDEx IG9uIHBjaTAuMTEuMA0KbmNyMDogbWluc3luYz0yNSwgbWF4c3luYz0yMDYs IG1heG9mZnM9OCwgMTYgZHdvcmRzIGJ1cnN0LCBub3JtYWwgZG1hIGZpZm8N Cm5jcjA6IHNpbmdsZS1lbmRlZCwgb3BlbiBkcmFpbiBJUlEgZHJpdmVyDQpQ cm9iaW5nIGZvciBkZXZpY2VzIG9uIHRoZSBJU0EgYnVzOg0KYXRrYmQ6IHRo ZSBjdXJyZW50IGtiZCBjb250cm9sbGVyIGNvbW1hbmQgYnl0ZSAwMDQ3DQph dGtiZDoga2V5Ym9hcmQgSUQgMHg0MWFiICgyKQ0Ka2JkYzogUkVTRVRfS0JE IHJldHVybiBjb2RlOjAwZmENCmtiZGM6IFJFU0VUX0tCRCBzdGF0dXM6MDBh YQ0Kc2MwIG9uIGlzYQ0Kc2MwOiBmYjAga2JkMA0Kc2MwOiBWR0EgY29sb3Ig PDE2IHZpcnR1YWwgY29uc29sZXMsIGZsYWdzPTB4MD4NCmVkMCBhdCAweDI4 MC0weDI5ZiBpcnEgMTAgb24gaXNhDQplZDA6IGFkZHJlc3MgMDA6NDA6MzM6 YTc6ZGM6MjMsIHR5cGUgTkUyMDAwICgxNiBiaXQpIA0KYnBmOiBlZDAgYXR0 YWNoZWQNCmF0a2JkYzAgYXQgMHg2MC0weDZmIG9uIG1vdGhlcmJvYXJkDQph dGtiZDAgaXJxIDEgb24gaXNhDQprYmQwOiBhdGtiZDAsIEFUIDEwMS8xMDIg KDIpLCBjb25maWc6MHgwLCBmbGFnczoweDNkMDAwMA0KcHNtMDogY3VycmVu dCBjb21tYW5kIGJ5dGU6MDA0Nw0Ka2JkYzogVEVTVF9BVVhfUE9SVCBzdGF0 dXM6MDAwMA0Ka2JkYzogUkVTRVRfQVVYIHJldHVybiBjb2RlOjAwZmENCmti ZGM6IFJFU0VUX0FVWCBzdGF0dXM6MDBhYQ0Ka2JkYzogUkVTRVRfQVVYIElE OjAwMDANCnBzbTogc3RhdHVzIDAwIDAyIDY0DQpwc206IHN0YXR1cyBiMSAw MyBjOA0KcHNtOiBzdGF0dXMgYjEgMDMgYzgNCnBzbTogc3RhdHVzIGIxIDAz IGM4DQpwc206IHN0YXR1cyAwMCAwMCAzYw0KcHNtOiBkYXRhIDA4IDAwIDAw DQpwc206IHN0YXR1cyAwMCAwMiA2NA0KcHNtOiBkYXRhIDA4IDAwIDAwDQpw c206IHN0YXR1cyAwMCAwMiA2NA0KcHNtMCBpcnEgMTIgb24gaXNhDQpwc20w OiBtb2RlbCBHZW5lcmljIFBTLzIgbW91c2UsIGRldmljZSBJRCAwLTAwLCAz IGJ1dHRvbnMNCnBzbTA6IGNvbmZpZzowMDAwMDAwMCwgZmxhZ3M6MDAwMDAw MDAsIHBhY2tldCBzaXplOjMNCnBzbTA6IHN5bmNtYXNrOmMwLCBzeW5jYml0 czowMA0Kc2lvMDogaXJxIG1hcHM6IDB4MSAweDExIDB4MSAweDENCnNpbzAg YXQgMHgzZjgtMHgzZmYgaXJxIDQgZmxhZ3MgMHgxMCBvbiBpc2ENCnNpbzA6 IHR5cGUgMTY1NTBBDQpzaW8xOiBpcnEgbWFwczogMHgxIDB4OSAweDEgMHgx DQpzaW8xIGF0IDB4MmY4LTB4MmZmIGlycSAzIG9uIGlzYQ0Kc2lvMTogdHlw ZSAxNjU1MEENCnNpbzI6IGRpc2FibGVkLCBub3QgcHJvYmVkLg0Kc2lvMzog ZGlzYWJsZWQsIG5vdCBwcm9iZWQuDQpmZGMwIGF0IDB4M2YwLTB4M2Y3IGly cSA2IGRycSAyIG9uIGlzYQ0KZmRjMDogRklGTyBlbmFibGVkLCA4IGJ5dGVz IHRocmVzaG9sZA0KZmQwOiAxLjQ0TUIgMy41aW4NCndkYzAgbm90IGZvdW5k IGF0IDB4MWYwDQp3ZGMxIG5vdCBmb3VuZCBhdCAweDE3MA0KcHBjOiBwYXJh bGxlbCBwb3J0IGZvdW5kIGF0IDB4Mzc4DQpwcGMwOiAweDg3IC0gMHhjIDB4 MCAweGZmIDB4MTAgMHgwIDB4MCAweDUgMHgwIDB4MCAweDhhIDB4MWYgMHhj IDB4MjggMHhhYiAweDAgMHgwIDB4MCAweDAgMHgwIDB4MCAweDcgMHgwIDB4 MCAweGZjIDB4MCAweDEgMHhkZSAweGZlIDB4YmUgMHgyMyAweDI1IDB4NDMg MHg2MiANCnBwYzA6IEVDUCtFUFAgU1BQDQpwcGMwIGF0IDB4Mzc4IGlycSA3 IG9uIGlzYQ0KcHBjMDogVzgzODc3RiBjaGlwc2V0IChFQ1AvRVBQL1BTMi9O SUJCTEUpIGluIENPTVBBVElCTEUgbW9kZQ0KcHBjMDogRklGTyB3aXRoIDE2 LzE2LzE2IGJ5dGVzIHRocmVzaG9sZA0KbHB0MDogPGdlbmVyaWMgcHJpbnRl cj4gb24gcHBidXMgMA0KbHB0MDogSW50ZXJydXB0LWRyaXZlbiBwb3J0DQpw cGkwOiA8Z2VuZXJpYyBwYXJhbGxlbCBpL28+IG9uIHBwYnVzIDANCnBsaXA6 IGlycSA3DQpwbGlwMDogPFBMSVAgbmV0d29yayBpbnRlcmZhY2U+IG9uIHBw YnVzIDANCmJwZjogbHAwIGF0dGFjaGVkDQp2Z2EwIGF0IDB4M2IwLTB4M2Rm IG1hZGRyIDB4YTAwMDAgbXNpemUgMTMxMDcyIG9uIGlzYQ0KZmIwOiB2Z2Ew LCB2Z2EsIHR5cGU6VkdBICg1KSwgZmxhZ3M6MHg3MDA3Zg0KZmIwOiBwb3J0 OjB4M2IwLTB4M2RmLCBjcnRjOjB4M2Q0LCBtZW06MHhhMDAwMCAweDIwMDAw DQpmYjA6IGluaXQgbW9kZToyNCwgYmlvcyBtb2RlOjMsIGN1cnJlbnQgbW9k ZToyNA0KZmIwOiB3aW5kb3c6MHhjMDBiODAwMCBzaXplOjMyayBncmFuOjMy aywgYnVmOjB4MCBzaXplOjBrDQpWR0EgcGFyYW1ldGVycyB1cG9uIHBvd2Vy LXVwDQo1MCAxOCAxMCAwMCAwMCAwMCAwMyAwMCAwMiA2NyA1ZiA0ZiA1MCA4 MiA1NSA4MSANCmJmIDFmIDAwIDRmIDBlIDBmIDAwIDAwIDA3IDgwIDljIDhl IDhmIDI4IDFmIDk2IA0KYjkgYTMgZmYgMDAgMDEgMDIgMDMgMDQgMDUgMTQg MDcgMzggMzkgM2EgM2IgM2MgDQozZCAzZSAzZiAwYyAwMCAwZiAwOCAwMCAw MCAwMCAwMCAwMCAxMCAwZSAwMCBmZiANClZHQSBwYXJhbWV0ZXJzIGluIEJJ T1MgZm9yIG1vZGUgMjQNCjUwIDE4IDEwIDAwIDEwIDAwIDAzIDAwIDAyIDY3 IDVmIDRmIDUwIDgyIDU1IDgxIA0KYmYgMWYgMDAgNGYgMGQgMGUgMDAgMDAg MDAgMDAgOWMgOGUgOGYgMjggMWYgOTYgDQpiOSBhMyBmZiAwMCAwMSAwMiAw MyAwNCAwNSAxNCAwNyAzOCAzOSAzYSAzYiAzYyANCjNkIDNlIDNmIDBjIDAw IDBmIDA4IDAwIDAwIDAwIDAwIDAwIDEwIDBlIDAwIGZmIA0KRUdBL1ZHQSBw YXJhbWV0ZXJzIHRvIGJlIHVzZWQgZm9yIG1vZGUgMjQNCjUwIDE4IDEwIDAw IDEwIDAwIDAzIDAwIDAyIDY3IDVmIDRmIDUwIDgyIDU1IDgxIA0KYmYgMWYg MDAgNGYgMGQgMGUgMDAgMDAgMDAgMDAgOWMgOGUgOGYgMjggMWYgOTYgDQpi OSBhMyBmZiAwMCAwMSAwMiAwMyAwNCAwNSAxNCAwNyAzOCAzOSAzYSAzYiAz YyANCjNkIDNlIDNmIDBjIDAwIDBmIDA4IDAwIDAwIDAwIDAwIDAwIDEwIDBl IDAwIGZmIA0KbnB4MCBvbiBtb3RoZXJib2FyZA0KbnB4MDogSU5UIDE2IGlu dGVyZmFjZQ0KaTU4Nl9iemVybygpIGJhbmR3aWR0aCA9IDE1MTA1NzQwMSBi eXRlcy9zZWMNCmJ6ZXJvKCkgYmFuZHdpZHRoID0gNDA0MjAzNzE4IGJ5dGVz L3NlYw0KYXBtMDogZGlzYWJsZWQsIG5vdCBwcm9iZWQuDQppbWFza3M6IGJp byBjMDA4MDA0MCwgdHR5IGMwMDcxNDlhLCBuZXQgYzAwNzE0OWENCkJJT1Mg R2VvbWV0cmllczoNCiAwOjAzZjIyMDNlIDAuLjEwMTA9MTAxMSBjeWxpbmRl cnMsIDAuLjMyPTMzIGhlYWRzLCAxLi42Mj02MiBzZWN0b3JzDQogMTowM2Y1 MjAzZiAwLi4xMDEzPTEwMTQgY3lsaW5kZXJzLCAwLi4zMj0zMyBoZWFkcywg MS4uNjM9NjMgc2VjdG9ycw0KIDI6MDNmNjA3M2IgMC4uMTAxND0xMDE1IGN5 bGluZGVycywgMC4uNz04IGhlYWRzLCAxLi41OT01OSBzZWN0b3JzDQogMCBh Y2NvdW50ZWQgZm9yDQpEZXZpY2UgY29uZmlndXJhdGlvbiBmaW5pc2hlZC4N CmJwZjogdHVuMCBhdHRhY2hlZA0KYnBmOiBzbDAgYXR0YWNoZWQNCmJwZjog cHBwMCBhdHRhY2hlZA0KbmV3IG1hc2tzOiBiaW8gYzAwODAwNDAsIHR0eSBj MDA3MTQ5YSwgbmV0IGMwMDcxNDlhDQpicGY6IGxvMCBhdHRhY2hlZA0KV2Fp dGluZyAxNSBzZWNvbmRzIGZvciBTQ1NJIGRldmljZXMgdG8gc2V0dGxlDQpu Y3IwOiByZXN0YXJ0IChzY3NpIHJlc2V0KS4NCihwcm9iZTI6bmNyMDowOjI6 MCk6IElOUVVJUlkuIENEQjogMTIgMSA4MCAwIGZmIDAgDQoocHJvYmUyOm5j cjA6MDoyOjApOiBJTExFR0FMIFJFUVVFU1QgYXNjOjI0LDANCihwcm9iZTI6 bmNyMDowOjI6MCk6IEludmFsaWQgZmllbGQgaW4gQ0RCIHNrczpjOCwxDQoo cHJvYmU1Om5jcjA6MDo1OjApOiBJTlFVSVJZLiBDREI6IDEyIDEgODAgMCBm ZiAwIA0KKHByb2JlNTpuY3IwOjA6NTowKTogSUxMRUdBTCBSRVFVRVNUIGNz aTo0MCwwLDAsMA0KKHByb2JlNjpuY3IwOjA6NjowKTogSU5RVUlSWS4gQ0RC OiAxMiAxIDgwIDAgZmYgMCANCihwcm9iZTY6bmNyMDowOjY6MCk6IElMTEVH QUwgUkVRVUVTVCBhc2M6MjQsMA0KKHByb2JlNjpuY3IwOjA6NjowKTogSW52 YWxpZCBmaWVsZCBpbiBDREINCnNhMCBhdCBuY3IwIGJ1cyAwIHRhcmdldCA1 IGx1biAwDQpzYTA6IDxXQU5HVEVLIDU1MjVFUyBTQ1NJIFJFVjcgM1I0PiBS ZW1vdmFibGUgU2VxdWVudGlhbCBBY2Nlc3MgU0NTSS1DQ1MgZGV2aWNlIA0K c2EwOiAzLjMwME1CL3MgdHJhbnNmZXJzDQpwYXNzMCBhdCBuY3IwIGJ1cyAw IHRhcmdldCAwIGx1biAwDQpwYXNzMDogPFNFQUdBVEUgU1QzMTIzME4gMDUx MD4gRml4ZWQgRGlyZWN0IEFjY2VzcyBTQ1NJLTIgZGV2aWNlIA0KcGFzczA6 IFNlcmlhbCBOdW1iZXIgMDAyMjAxNTQNCnBhc3MwOiAxMC4wMDBNQi9zIHRy YW5zZmVycyAoMTAuMDAwTUh6LCBvZmZzZXQgOCksIFRhZ2dlZCBRdWV1ZWlu ZyBFbmFibGVkDQpwYXNzMSBhdCBuY3IwIGJ1cyAwIHRhcmdldCAxIGx1biAw DQpwYXNzMTogPFNFQUdBVEUgU1Q1MTA4ME4gMDk0Mz4gRml4ZWQgRGlyZWN0 IEFjY2VzcyBTQ1NJLTIgZGV2aWNlIA0KcGFzczE6IFNlcmlhbCBOdW1iZXIg UkowNTMyODANCnBhc3MxOiAxMC4wMDBNQi9zIHRyYW5zZmVycyAoMTAuMDAw TUh6LCBvZmZzZXQgOCksIFRhZ2dlZCBRdWV1ZWluZyBFbmFibGVkDQpwYXNz MiBhdCBuY3IwIGJ1cyAwIHRhcmdldCAyIGx1biAwDQpwYXNzMjogPFFVQU5U VU0gTFAyNDBTIEdNMjQwUzAxWCA2LjM+IEZpeGVkIERpcmVjdCBBY2Nlc3Mg U0NTSS0yIGRldmljZSANCnBhc3MyOiAxMC4wMDBNQi9zIHRyYW5zZmVycyAo MTAuMDAwTUh6LCBvZmZzZXQgOCkNCnBhc3MzIGF0IG5jcjAgYnVzIDAgdGFy Z2V0IDUgbHVuIDANCnBhc3MzOiA8V0FOR1RFSyA1NTI1RVMgU0NTSSBSRVY3 IDNSND4gUmVtb3ZhYmxlIFNlcXVlbnRpYWwgQWNjZXNzIFNDU0ktQ0NTIGRl dmljZSANCnBhc3MzOiAzLjMwME1CL3MgdHJhbnNmZXJzDQpwYXNzNCBhdCBu Y3IwIGJ1cyAwIHRhcmdldCA2IGx1biAwDQpwYXNzNDogPFNPTlkgQ0QtUk9N IENEVS01NVMgMS4wdD4gUmVtb3ZhYmxlIENELVJPTSBTQ1NJLTIgZGV2aWNl IA0KcGFzczQ6IDQuMDMyTUIvcyB0cmFuc2ZlcnMgKDQuMDMyTUh6LCBvZmZz ZXQgOCkNCmRhMiBhdCBuY3IwIGJ1cyAwIHRhcmdldCAyIGx1biAwDQpkYTI6 IDxRVUFOVFVNIExQMjQwUyBHTTI0MFMwMVggNi4zPiBGaXhlZCBEaXJlY3Qg QWNjZXNzIFNDU0ktMiBkZXZpY2UgDQpkYTI6IDEwLjAwME1CL3MgdHJhbnNm ZXJzICgxMC4wMDBNSHosIG9mZnNldCA4KQ0KZGEyOiAyMzRNQiAoNDc5MzUw IDUxMiBieXRlIHNlY3RvcnM6IDY0SCAzMlMvVCAyMzRDKQ0KZGExIGF0IG5j cjAgYnVzIDAgdGFyZ2V0IDEgbHVuIDANCmRhMTogPFNFQUdBVEUgU1Q1MTA4 ME4gMDk0Mz4gRml4ZWQgRGlyZWN0IEFjY2VzcyBTQ1NJLTIgZGV2aWNlIA0K ZGExOiBTZXJpYWwgTnVtYmVyIFJKMDUzMjgwDQpkYTE6IDEwLjAwME1CL3Mg dHJhbnNmZXJzICgxMC4wMDBNSHosIG9mZnNldCA4KSwgVGFnZ2VkIFF1ZXVl aW5nIEVuYWJsZWQNCmRhMTogMTAzME1CICgyMTA5ODQwIDUxMiBieXRlIHNl Y3RvcnM6IDI1NUggNjNTL1QgMTMxQykNCmRhMCBhdCBuY3IwIGJ1cyAwIHRh cmdldCAwIGx1biAwDQpkYTA6IDxTRUFHQVRFIFNUMzEyMzBOIDA1MTA+IEZp eGVkIERpcmVjdCBBY2Nlc3MgU0NTSS0yIGRldmljZSANCmRhMDogU2VyaWFs IE51bWJlciAwMDIyMDE1NA0KZGEwOiAxMC4wMDBNQi9zIHRyYW5zZmVycyAo MTAuMDAwTUh6LCBvZmZzZXQgOCksIFRhZ2dlZCBRdWV1ZWluZyBFbmFibGVk DQpkYTA6IDEwMTBNQiAoMjA2OTg2MCA1MTIgYnl0ZSBzZWN0b3JzOiA2NEgg MzJTL1QgMTAxMEMpDQpDb25zaWRlcmluZyBNRlMgcm9vdCBmL3MuDQpObyBN RlMgaW1hZ2UgYXZhaWxhYmxlIGFzIHJvb3QgZi9zLg0KQ29uc2lkZXJpbmcg RkZTIHJvb3QgZi9zLg0KY2hhbmdpbmcgcm9vdCBkZXZpY2UgdG8gZGEwczFh DQooY2QwOm5jcjA6MDo2OjApOiBSRUFEIENEIFJFQ09SREVEIENBUEFDSVRZ LiBDREI6IDI1IDAgMCAwIDAgMCAwIDAgMCAwIA0KKGNkMDpuY3IwOjA6Njow KTogTk9UIFJFQURZIGFzYzozYSwwDQooY2QwOm5jcjA6MDo2OjApOiBNZWRp dW0gbm90IHByZXNlbnQNCmNkMCBhdCBuY3IwIGJ1cyAwIHRhcmdldCA2IGx1 biAwDQpjZDA6IDxTT05ZIENELVJPTSBDRFUtNTVTIDEuMHQ+IFJlbW92YWJs ZSBDRC1ST00gU0NTSS0yIGRldmljZSANCmNkMDogNC4wMzJNQi9zIHRyYW5z ZmVycyAoNC4wMzJNSHosIG9mZnNldCA4KQ0KY2QwOiBBdHRlbXB0IHRvIHF1 ZXJ5IGRldmljZSBzaXplIGZhaWxlZDogTk9UIFJFQURZLCBNZWRpdW0gbm90 IHByZXNlbnQNCmRhMHMxOiB0eXBlIDB4YTUsIHN0YXJ0IDAsIGVuZCA9IDIw Njk4NTksIHNpemUgMjA2OTg2MCANCmRhMHMxOiBDL0gvUyBlbmQgMTI4LzIx NC81OCAoMTYwODYyOSkgIT0gZW5kIDIwNjk4NTk6IGludmFsaWQNCnN0YXJ0 X2luaXQ6IHRyeWluZyAvc2Jpbi9pbml0DQpkYTFzMTogdHlwZSAweGE1LCBz dGFydCAwLCBlbmQgPSAyMTA5ODM5LCBzaXplIDIxMDk4NDAgDQpkYTFzMTog Qy9IL1MgZW5kIDEzMS84NC8zMyAoMzcwMjU5KSAhPSBlbmQgMjEwOTgzOTog aW52YWxpZA0KZGEyczE6IHR5cGUgMHhhNSwgc3RhcnQgMCwgZW5kID0gNDc5 MzQ5LCBzaXplIDQ3OTM1MCANCmRhMnMxOiBDL0gvUyBlbmQgNDc1LzgvNDYg KDE5NzA2MykgIT0gZW5kIDQ3OTM0OTogaW52YWxpZA0KZGExczE6IHR5cGUg MHhhNSwgc3RhcnQgMCwgZW5kID0gMjEwOTgzOSwgc2l6ZSAyMTA5ODQwIA0K ZGExczE6IEMvSC9TIGVuZCAxMzEvODQvMzMgKDM3MDI1OSkgIT0gZW5kIDIx MDk4Mzk6IGludmFsaWQNCmRhMnMxOiB0eXBlIDB4YTUsIHN0YXJ0IDAsIGVu ZCA9IDQ3OTM0OSwgc2l6ZSA0NzkzNTAgDQpkYTJzMTogQy9IL1MgZW5kIDQ3 NS84LzQ2ICgxOTcwNjMpICE9IGVuZCA0NzkzNDk6IGludmFsaWQNCg== --0-244944148-945050539=:318-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 20: 1:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from anarchy.io.com (anarchy.io.com [199.170.88.101]) by hub.freebsd.org (Postfix) with ESMTP id 94DAF14E11 for ; Sun, 12 Dec 1999 20:01:48 -0800 (PST) (envelope-from csm@io.com) Received: from io.com (aus-as4-027.io.com [208.2.105.27]) by anarchy.io.com (8.9.3/8.9.3) with ESMTP id WAA23993 for ; Sun, 12 Dec 1999 22:01:44 -0600 Message-ID: <38541B2A.B48B23D0@io.com> Date: Sun, 12 Dec 1999 22:01:14 +0000 From: Clint McCulloch X-Mailer: Mozilla 4.6 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 21:30: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 8151314CCF for ; Sun, 12 Dec 1999 21:29:58 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 11xO3X-000Msc-00; Sun, 12 Dec 1999 21:29:55 -0800 Date: Sun, 12 Dec 1999 21:29:49 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Bosko Milekic Cc: Greg Prosser , freebsd Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC 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 Sun, 12 Dec 1999, Bosko Milekic wrote: > On Sun, 12 Dec 1999, Tom wrote: > > !> > !> Setting maxusers to 256 isn't help you any at all, btw. > !> > !>Tom > !> > > This is simply untrue. > > MAXUSERS directly influences the number of mbufs which, in turn, > influence the size of mb_map. Bumping up MAXUSERS in reasonable amounts > will, in fact, contribute to a larger mb_map. Yes, but if you override NMBCLUSTERS, MAXUSERS isn't able to do that. If you look at the original post, you will see that seeting maxusers to 256 does not help if you also set NMBCLUSTERS to 2048. > -- > Bosko Milekic > http://pages.infinit.net/bmilekic/ Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 12 22:18: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from clapton.atgsystems.com (clapton.atgsystems.com [207.122.162.32]) by hub.freebsd.org (Postfix) with ESMTP id 31EDC14C47 for ; Sun, 12 Dec 1999 22:18:04 -0800 (PST) (envelope-from bob@clapton.atgsystems.com) Received: from madman (root@joplin.atgsystems.com [207.122.162.33]) by clapton.atgsystems.com (8.8.8/8.8.8) with SMTP id AAA08193; Mon, 13 Dec 1999 00:18:40 -0600 (CST) (envelope-from bob@clapton.atgsystems.com) Message-ID: <002001bf4532$7a056b00$01000000@madman> From: "Bob Madden" To: "Pekka Savola" , "Daniel C. Sobral" Cc: Subject: Re: pidentd Date: Mon, 13 Dec 1999 00:22:47 -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.3612.1700 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3612.1700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----Original Message----- From: Daniel C. Sobral To: Pekka Savola Cc: John ; williamsl@home.com ; Sheepman ; freebsd-stable@FreeBSD.ORG Date: Sunday, December 12, 1999 12:04 PM Subject: Re: pidentd >Pekka Savola wrote: >> >> This is correct, but doesn't help the actual problem because internal boxes >> never get those ident requests. > >_This_ is the problem, and the correct solution is NAT understanding >identd protocol. It's not even that difficult. > Another solution is to run a Socks5 Server on the FreeBSD box and the SocksCap32 client on all thw WinX boxes. This way all the clients will appear to be the Socks5 Server hostname, and assuming you have an A record and PTR record for that servers hostname/ip address, all the WinX clients will get properly identified both through forward and reverse lookups. You can obtain the Socks5 source at http://www.socks.nec.com/ along with all documentation necessary to set it up. Bob Madden >,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,< --This Message Composed By: Bob Madden -- bob@CLAPTON.ATGSYSTEMS.COM Sys Admin /Network Engineer >-- >Daniel C. Sobral (8-DCS) >who is as social as a wampas > >dcs@newsguy.com >dcs@freebsd.org > > >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 Dec 12 22:43:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from manor.msen.com (manor.msen.com [148.59.4.13]) by hub.freebsd.org (Postfix) with ESMTP id 2EFF714CAE for ; Sun, 12 Dec 1999 22:43:54 -0800 (PST) (envelope-from wayne@staff.msen.com) Received: from manor.msen.com (LOCALHOST [127.0.0.1]) by manor.msen.com (8.8.8/8.8.8) with ESMTP id BAA01109 for ; Mon, 13 Dec 1999 01:43:52 -0500 (EST) (envelope-from wayne@manor.msen.com) Message-Id: <199912130643.BAA01109@manor.msen.com> To: freebsd-stable@freebsd.org From: "Michael R. Wayne" Date: Mon, 13 Dec 1999 01:43:52 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: 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 Dec 13 2: 6:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fep9.mail.ozemail.net (fep9.mail.ozemail.net [203.2.192.103]) by hub.freebsd.org (Postfix) with ESMTP id 59A0B15083 for ; Mon, 13 Dec 1999 02:06:50 -0800 (PST) (envelope-from death@southcom.com.au) Received: from windows (1Cust155.tnt1.hba1.da.uu.net [210.84.240.155]) by fep9.mail.ozemail.net (8.9.0/8.6.12) with ESMTP id VAA02090; Mon, 13 Dec 1999 21:06:27 +1100 (EST) Message-Id: <4.2.1.19991213205944.00c55ac0@mail.southcom.com.au> X-Sender: death@mail.southcom.com.au X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.1 Date: Mon, 13 Dec 1999 21:05:50 +1100 To: Ben WIlliams From: death Subject: Re: pidentd Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <7101.991211@Home.Com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:25 AM 11/12/1999 -0500, Ben WIlliams wrote: >freebsd-stable, Saturday, December 11, 1999 > > I am trying to get pidentd (or any other ident daemon) to work for >masqueraded hosts on a private LAN connected to the internet via a >3.2-RELEASE box. I've managed to successfully compile and install >pidentd which works as a standard ident daemon but I am having >difficulty figuring out how to make it work for masq'd hosts. Any >ideas? My solution was to either: a) NAT all identd stuff to windows using: ipfw add 30000 divert 666 tcp from any 113 to any via ppp0 ipfw add 30000 divert 666 tcp from any to any 113 via ppp0 natd -port 666 -redirect_address 192.168.1.2 0.0.0.0 -interface ppp0 -dynamic 666 being just a port i picked because the natd port is being used by another nat. port 113 being ident. ppp0 being the interface that i'm on the net with. and 192.168.1.2 being the address of my windows box. this assumes that you don't need identd on your freebsd box, and that you only have 1 machine you want identd running on. b) Use a socks5 server. This is the best option - but i couldn't get ident working in socks5 though. Eventually got it compiled in by fixing some broken code, but then it still did nothing. Cheers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 2:13:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles516.castles.com [208.214.165.80]) by hub.freebsd.org (Postfix) with ESMTP id BB8231509F for ; Mon, 13 Dec 1999 02:13:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id CAA21812 for ; Mon, 13 Dec 1999 02:16:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912131016.CAA21812@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-stable@FreeBSD.ORG Subject: Re: pidentd In-reply-to: Your message of "Mon, 13 Dec 1999 21:05:50 +1100." <4.2.1.19991213205944.00c55ac0@mail.southcom.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 02:16:21 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 02:25 AM 11/12/1999 -0500, Ben WIlliams wrote: > >freebsd-stable, Saturday, December 11, 1999 > > > > I am trying to get pidentd (or any other ident daemon) to work for > >masqueraded hosts on a private LAN connected to the internet via a > >3.2-RELEASE box. I've managed to successfully compile and install > >pidentd which works as a standard ident daemon but I am having > >difficulty figuring out how to make it work for masq'd hosts. Any > >ideas? The right answer, of course, is to use an IRC server that doesn't insist on ident. Much easier than all this running around like a headless chicken, and much easier on our mail bandwidth, thanks. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 8:24:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id AD6DF157AE for ; Mon, 13 Dec 1999 08:24:45 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id IAA78352; Mon, 13 Dec 1999 08:24:38 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 13 Dec 1999 08:24:38 -0800 (PST) From: Doug White To: death Cc: Ben WIlliams , freebsd-stable@FreeBSD.ORG Subject: Re: pidentd In-Reply-To: <4.2.1.19991213205944.00c55ac0@mail.southcom.com.au> 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, 13 Dec 1999, death wrote: > a) NAT all identd stuff to windows using: > > ipfw add 30000 divert 666 tcp from any 113 to any via ppp0 > ipfw add 30000 divert 666 tcp from any to any 113 via ppp0 > natd -port 666 -redirect_address 192.168.1.2 0.0.0.0 -interface ppp0 -dynamic Icky. Just add another -redirect_port command to your existing NAT and restart it. Or better, start using /etc/natd.conf and the -f option to natd. > b) Use a socks5 server. This is the best option - but i couldn't get ident > working in socks5 though. Eventually got it compiled in by fixing some > broken code, but then it still did nothing. Beyond using sockscap, do any worthwhile IRC clients use Socks? Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 8:26:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 4317F14E9B; Mon, 13 Dec 1999 08:26:51 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id IAA79064; Mon, 13 Dec 1999 08:26:50 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 13 Dec 1999 08:26:50 -0800 (PST) From: Doug White To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: pidentd In-Reply-To: <199912131016.CAA21812@mass.cdrom.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, 13 Dec 1999, Mike Smith wrote: > > At 02:25 AM 11/12/1999 -0500, Ben WIlliams wrote: > > >freebsd-stable, Saturday, December 11, 1999 > > > > > > I am trying to get pidentd (or any other ident daemon) to work for > > >masqueraded hosts on a private LAN connected to the internet via a > > >3.2-RELEASE box. I've managed to successfully compile and install > > >pidentd which works as a standard ident daemon but I am having > > >difficulty figuring out how to make it work for masq'd hosts. Any > > >ideas? > > The right answer, of course, is to use an IRC server that doesn't insist > on ident. Much easier than all this running around like a headless > chicken, and much easier on our mail bandwidth, thanks. If you can furnish me with a list of the EFNet IRC servers that don't subscribe to ident bigotry I'd be really happy. :-) I finally gave up and pushed ident through to my workstation since trying to find a decently peered server was getting really hard. freei was the last one and Sprynet ate it and put it under communist control. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 8:29:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 9CF4314C86 for ; Mon, 13 Dec 1999 08:29:48 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id IAA79769; Mon, 13 Dec 1999 08:29:45 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 13 Dec 1999 08:29:44 -0800 (PST) From: Doug White To: Pekka Savola Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Selecting which programs to have in the base system In-Reply-To: <3.0.6.32.19991212200222.00798800@netcore.home> 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, 12 Dec 1999, Pekka Savola wrote: > I posted this to freebsd-newbies (this seems like a newbie/faq question to > me) a day or two ago but got no answer. So let's try this list.. > > How can I manipulate -easily- which base system files (in e.g. /bin, > /sbin, /usr/bin, /usr/sbin) will be installed/compiled when I cvsup the > sources and make world ? You don't, because if you muddle with what binaries are installed you'll shoot yourself in the foot in a matter of minutes. > The problem is, according to /var/log/setuid.today, I have ~70 files (some > of them just symbolic links though) which are setuid root (95% of them from > base system). Talk about security! I'd like to remove the ones I don't > need and never hear of them again (like ppp*, r*, yp*). Also, having stuff > like this along just takes some HDD space too. I couldn't care less of > having e.g. some games in my system. Develop a patchset that removes them from the appropriate Makefiles. Myself, just delete those security messages after glancing at the top of them to make sure noone's added themselves to the password file when I wasn't looking. You could disable the suid binary check but that has its problems. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 8:39:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 9CE7C15131 for ; Mon, 13 Dec 1999 08:39:32 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id IAA82847; Mon, 13 Dec 1999 08:39:18 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Mon, 13 Dec 1999 08:39:18 -0800 (PST) From: Doug White To: Bosko Milekic Cc: David Greenman , Tom , Greg Prosser , freebsd Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC 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 Sun, 12 Dec 1999, Bosko Milekic wrote: > Even at that, MAXUSERS still contributes to the mb_map size. I see > your point, though, in the sense that by setting up NMBCLUSTERS, the > overall size of mb_map will be affected by that setting, and not > MAXUSERS, in general. > So here's the question: Why not remove MAXUSERS' influence over the > size of the mb_map, and just have it influenced by a single option? Because it doesn't make sense to separate it out? maxusers is a good general sizing knob; it should size everything that's related to server capacity. You should override the maxuser-based calculations IFF you know the calculated number isn't enough, even at maxusers 128. We have hard-core MDAs that get a 'options NMBCLUSTERS=16384' and 'maxusers 128' based on real-world statistics. These machines routinely peak out at 10K mbuf clusters and 22MBytes of network memory. With the default settings they wouldn't last 10 minutes. And even with 16K mbufs they still die when large parts of the Net go away. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 9:46:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 96EEF15199 for ; Mon, 13 Dec 1999 09:46:16 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 11xZY2-0000eA-00 for freebsd-stable@FreeBSD.ORG; Mon, 13 Dec 1999 12:46:10 -0500 Date: Mon, 13 Dec 1999 12:46:09 -0500 From: Peter Radcliffe To: freebsd-stable@FreeBSD.ORG Subject: Re: pidentd Message-ID: <19991213124609.A1355@pir.net> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <199912131016.CAA21812@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dwhite@resnet.uoregon.edu on Mon, Dec 13, 1999 at 08:26:50AM -0800 X-fish: < Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug White probably said: > If you can furnish me with a list of the EFNet IRC servers that don't > subscribe to ident bigotry I'd be really happy. :-) I finally gave up and > pushed ident through to my workstation since trying to find a decently > peered server was getting really hard. cat stupid.identd.pl #!/usr/bin/perl $| = 1; while (<>) { $_ =~ s/\r\n$//; print STDOUT "$_ : USERID : UNIX : bite-me\r\n"; exit 0; } HTH. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 10: 5:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CA21315525 for ; Mon, 13 Dec 1999 10:05:26 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA68394; Mon, 13 Dec 1999 11:05:25 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA45050; Mon, 13 Dec 1999 11:05:25 -0700 (MST) Message-Id: <199912131805.LAA45050@harmony.village.org> To: Peter Radcliffe Subject: Re: pidentd Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 13 Dec 1999 12:46:09 EST." <19991213124609.A1355@pir.net> References: <19991213124609.A1355@pir.net> <199912131016.CAA21812@mass.cdrom.com> Date: Mon, 13 Dec 1999 11:05:24 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991213124609.A1355@pir.net> Peter Radcliffe writes: : cat stupid.identd.pl This is far too long. #!/usr/bin/perl ($a, $b) = split(/[,\n\r ]+/,<>); print "$a , $b : USERID : UNIX : Warm-Fuzzy\r\n"; Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 10:20:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from electricrain.com (electricrain.com [166.90.54.240]) by hub.freebsd.org (Postfix) with SMTP id A9A5D152A8 for ; Mon, 13 Dec 1999 10:20:13 -0800 (PST) (envelope-from daniel@electricrain.com) Received: (qmail 26072 invoked by uid 501); 13 Dec 1999 18:20:04 -0000 From: "Daniel Sully" Date: Mon, 13 Dec 1999 10:20:04 -0800 To: Warner Losh Cc: Peter Radcliffe , freebsd-stable@FreeBSD.ORG Subject: Re: pidentd Message-ID: <19991213102004.D25035@electricrain.com> References: <19991213124609.A1355@pir.net> <199912131016.CAA21812@mass.cdrom.com> <19991213124609.A1355@pir.net> <199912131805.LAA45050@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912131805.LAA45050@harmony.village.org>; from imp@village.org on Mon, Dec 13, 1999 at 11:05:24AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Once upon a time Warner Losh shaped the electrons to say... > In message <19991213124609.A1355@pir.net> Peter Radcliffe writes: > : cat stupid.identd.pl > > This is far too long. > > #!/usr/bin/perl > ($a, $b) = split(/[,\n\r ]+/,<>); > print "$a , $b : USERID : UNIX : Warm-Fuzzy\r\n"; That is also far too long. perl -ne 'printf "%s , %s : USERID : UNIX : Bob\r\n",(split /[,\n\r ]+/)' =) -D -- Change? We fear change. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 10:30:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id 3F5EF15167 for ; Mon, 13 Dec 1999 10:30:38 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 11xaEx-0000tv-00 for freebsd-stable@FreeBSD.ORG; Mon, 13 Dec 1999 13:30:31 -0500 Date: Mon, 13 Dec 1999 13:30:31 -0500 From: Peter Radcliffe To: freebsd-stable@FreeBSD.ORG Subject: Re: pidentd Message-ID: <19991213133031.C1355@pir.net> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <19991213124609.A1355@pir.net> <199912131016.CAA21812@mass.cdrom.com> <19991213124609.A1355@pir.net> <199912131805.LAA45050@harmony.village.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912131805.LAA45050@harmony.village.org>; from imp@village.org on Mon, Dec 13, 1999 at 11:05:24AM -0700 X-fish: < Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh probably said: > This is far too long. Give a perl geek a bit of code, it becomes different. I'm not aperl geek and care little :) > #!/usr/bin/perl > ($a, $b) = split(/[,\n\r ]+/,<>); > print "$a , $b : USERID : UNIX : Warm-Fuzzy\r\n"; 1) Speaking of too long, the userid gets truncated to 8 chars, IIRC, hence "bite-me" being short. 2) Also IIRC the spec allows for multiple requests per connection. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 10:59:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-25.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.153]) by hub.freebsd.org (Postfix) with ESMTP id B0DA11517A; Mon, 13 Dec 1999 10:59:10 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id SAA00803; Mon, 13 Dec 1999 18:59:08 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id RAA00338; Mon, 13 Dec 1999 17:59:24 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912131759.RAA00338@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: "CHOI, Junho" Cc: Jon Hamilton , current@FreeBSD.ORG, stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: ppp over pty: trying to detect CD In-Reply-To: Message from "CHOI, Junho" of "12 Dec 1999 19:16:52 +0900." <86bt7wlazv.fsf@gradius.myhome> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 17:59:24 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ah, I see the problem. I have a fix - I'm about to apply it to -current and ask jkh for permission to MFC. I've attached the -stable patch for your viewing enjoyment.... > >>>>> "JH" == Jon Hamilton writes: > > JH> Running -current from this afternoon, I am having a strange > JH> symptom with ppp over a pty; ppp does not detect that the pty > JH> does not support carrier, and will cycle once per second > JH> waiting for CD to appear. Putting ``set cd off'' in my > JH> ppp.conf for that target fixed the problem, but I thought I'd > JH> mention it nonetheless, since that didn't used to be > JH> required. Certainly not all that big a deal, but I thought it > JH> was worth a mention. > > JH> FreeBSD 4.0-CURRENT #13: Sat Dec 11 20:31:42 CST 1999 > > I am using 3-STABLE but I have the same problem with you. I think it > comes after adding pppoe support in pppd(after 3.3-RELEASE). I am > -STABLE user but I had to back to 3.3-RELEASE's ppp... I am using ADSL > service with pptpclient. > > JH> and the syslog with debugging turned on, with no "set cd" in the config: > > JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] > JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: Waiting for carrier > JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] > JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: Waiting for carrier > > JH> [ and on and on and on ] > > -- > +++ Any opinions in this posting are my own and not those of my employers +++ > CHOI, Junho > - Korea FreeBSD Users Group > - Public Service, Youido Post Office - Web Data Bank -- Brian Don't _EVER_ lose your sense of humour ! Index: tty.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/ppp/tty.c,v retrieving revision 1.12.2.3 diff -u -r1.12.2.3 tty.c --- tty.c 1999/11/19 23:48:04 1.12.2.3 +++ tty.c 1999/12/13 07:30:44 @@ -112,6 +112,7 @@ log_Printf(LogDEBUG, "%s: ioctl error (%s)!\n", p->link.name, strerror(errno)); timer_Stop(&dev->Timer); + dev->mbits = TIOCM_CD; return; } } else @@ -187,8 +188,7 @@ return CARRIER_PENDING; /* Not yet ! */ } - return Online(dev) || !p->cfg.cd.necessity == CD_REQUIRED ? - CARRIER_OK : CARRIER_LOST; + return Online(dev) ? CARRIER_OK : CARRIER_LOST; } static int To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 11: 0: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 8124F1518A; Mon, 13 Dec 1999 11:00:01 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 6C0D71C4A; Mon, 13 Dec 1999 13:59:36 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 5DF4D381B; Mon, 13 Dec 1999 13:59:36 -0500 (EST) Date: Mon, 13 Dec 1999 13:59:36 -0500 (EST) From: Bill Fumerola To: Doug White Cc: Mike Smith , freebsd-stable@FreeBSD.ORG Subject: Re: pidentd 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, 13 Dec 1999, Doug White wrote: > If you can furnish me with a list of the EFNet IRC servers that don't > subscribe to ident bigotry I'd be really happy. :-) I finally gave up and > pushed ident through to my workstation since trying to find a decently > peered server was getting really hard. > > freei was the last one and Sprynet ate it and put it under communist > control. core.com -- - 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 Dec 13 11:12:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 77F3115327 for ; Mon, 13 Dec 1999 11:12:38 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA24672 for ; Mon, 13 Dec 1999 11:12:37 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id LAA05995 for stable@freebsd.org; Mon, 13 Dec 1999 11:12:36 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Mon, 13 Dec 1999 11:12:36 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: stable@freebsd.org Subject: Build of debugging kernel broken in -stable for Alpha Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think the building of debugging kernels is broken on FreeBSD-stable/Alpha systems. I configured with "config -g", but the make terminates with: make: don't know how to make kernel.debug. Stop Could somebody please confirm this? My system is a bit screwy -- it's really a -stable chroot environment inside a -current system. (Don't ask.) The entire userland in the chroot environment is pure -stable, so I think the breakage is real and not just an artifact of my setup here. It would be a shame to have this broken in 3.4-RELEASE. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 11:17:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kiwi.mail.easynet.net (kiwi.mail.easynet.net [195.40.1.40]) by hub.freebsd.org (Postfix) with ESMTP id 3A531151A9 for ; Mon, 13 Dec 1999 11:17:41 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (alister.w.easynet.co.uk [212.212.251.86]) by kiwi.mail.easynet.net (Postfix) with ESMTP id C70BDDAFE4; Mon, 13 Dec 1999 19:17:26 +0000 (GMT) Message-ID: <38554782.E3F6901A@freenet.co.uk> Date: Mon, 13 Dec 1999 19:22:42 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Pekka Savola Cc: Sheepman , williamsl@home.com, freebsd-stable@freebsd.org Subject: Re: pidentd References: <7101.991211@Home.Com> <3.0.6.32.19991212141700.007e2ac0@netcore.home> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Pekka Savola wrote: > > > When I set up masq'ing awhile back I used a different ident daemon. I > >did not use pidentd. I think maybe it was cidentd, but I am not sure. It > >was specifically for ip masqing. Hope this helps a smidge. :) > > > >> I am trying to get pidentd (or any other ident daemon) to work for > >> masqueraded hosts on a private LAN connected to the internet via a > >> 3.2-RELEASE box. I've managed to successfully compile and install > >> pidentd which works as a standard ident daemon but I am having > >> difficulty figuring out how to make it work for masq'd hosts. Any > >> ideas? > > Hi, > > I encountered the similar problem myself - and asked around for solutions. > I have come to the conclusion that there are _no_ identd implementations > for FreeBSD that would support NAT/Masq'ed connections. There are plenty > of them for Linux, but they seem to use proc filesystem and are of no use.. $ grep ident /etc/services auth 113/tcp ident tap #Authentication Service auth 113/udp ident tap #Authentication Service Why can't you just tell natd to redirect all incoming connections (UDP and TCP) on port 113 to a machine behind the firewall? redirect_port tcp 192.168.1.2:113 113 redirect_port udp 192.168.1.2:113 113 ^^^^^^^^^^^ IP address of the machine you want to respond Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 11:41:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from anarcat.dyndns.org (phobos.IRO.UMontreal.CA [132.204.20.20]) by hub.freebsd.org (Postfix) with ESMTP id 88781150C5 for ; Mon, 13 Dec 1999 11:41:37 -0800 (PST) (envelope-from spidey@anarcat.dyndns.org) Received: by anarcat.dyndns.org (Postfix, from userid 1000) id 2081319AC; Mon, 13 Dec 1999 14:41:28 -0500 (EST) From: Spidey MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14421.19431.833872.458577@anarcat.dyndns.org> Date: Mon, 13 Dec 1999 14:41:27 -0500 (EST) To: Pekka Savola Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Selecting which programs to have in the base system References: <3.0.6.32.19991212200222.00798800@netcore.home> X-Mailer: VM 6.72 under 21.1 (patch 7) "Biscayne" XEmacs Lucid Reply-To: Spidey Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --- Big Brother told Pekka Savola to write, at 20:02 of December 12: > Hello all, > > I posted this to freebsd-newbies (this seems like a newbie/faq question to > me) a day or two ago but got no answer. So let's try this list.. > > How can I manipulate -easily- which base system files (in e.g. /bin, > /sbin, /usr/bin, /usr/sbin) will be installed/compiled when I cvsup the > sources and make world ? I don't think that's a really good idea. It's not really 'made' that way. > The problem is, according to /var/log/setuid.today, I have ~70 files (some > of them just symbolic links though) which are setuid root (95% of them from > base system). Talk about security! I'd like to remove the ones I don't > need and never hear of them again (like ppp*, r*, yp*). Also, having stuff > like this along just takes some HDD space too. I couldn't care less of > having e.g. some games in my system. Well, I don't think these things take so much space... If you're talking serious about HDD space, your games will take a much bigger place than the, say, /usr/bin dir, that you won't even notice... (8622 Kb for my /usr/bin... that's not that big compare to my WarCraft install (22Mb! :)) > So, are there any utilities to keep track which base programs/sources are > installed and which are not - and how to keep them that way so that > upgrading the sources, 'make world', etc. won't mess those up? None that I know of. Would be nice to do though. Ready to code? :) > Btw, regarding setuid.today.. are there any good "master" references which > files in the base system really need to be +s ? I can't believe all ~70 > of them have to be... It's not a 'master' ref, but I built up a list of the suid files on FBSD and their use at: http://www.iro.umontreal.ca/~beaupran/FreeBSD/setugid.txt Tell me what you think of it! The AnarCat -- Si l'image donne l'illusion de savoir C'est que l'adage pretend que pour croire, L'important ne serait que de voir Lofofora To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 11:45:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by hub.freebsd.org (Postfix) with ESMTP id 11550151A1 for ; Mon, 13 Dec 1999 11:45:19 -0800 (PST) (envelope-from bmilekic@dsuper.net) Received: from oracle.dsuper.net (oracle.dsuper.net [205.205.255.1]) by oracle.dsuper.net (8.9.3/8.9.3) with ESMTP id OAA30486; Mon, 13 Dec 1999 14:45:06 -0500 (EST) Date: Mon, 13 Dec 1999 14:45:05 -0500 (EST) From: Bosko Milekic To: Doug White Cc: David Greenman , Tom , Greg Prosser , freebsd Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC 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, 13 Dec 1999, Doug White wrote: !> !>Because it doesn't make sense to separate it out? maxusers is a good !>general sizing knob; it should size everything that's related to server !>capacity. You should override the maxuser-based calculations IFF you know !>the calculated number isn't enough, even at maxusers 128. !> !>We have hard-core MDAs that get a 'options NMBCLUSTERS=16384' and !>'maxusers 128' based on real-world statistics. These machines routinely !>peak out at 10K mbuf clusters and 22MBytes of network memory. With the !>default settings they wouldn't last 10 minutes. !> !>And even with 16K mbufs they still die when large parts of the Net go !>away. !> !>Doug White | FreeBSD: The Power to Serve !>dwhite@resnet.uoregon.edu | www.FreeBSD.org !> Well, it appears I missed a TUNABLE_INT_DECL which twiddles with nmbufs as opposed to MAXUSERS, when NMBCLUSTERS is defined. My mistake! Thanks to all who pointed it out. Bosko. -- Bosko Milekic To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 12:23:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dnvrpop1.dnvr.uswest.net (dnvrpop1.dnvr.uswest.net [206.196.128.3]) by hub.freebsd.org (Postfix) with SMTP id 9F25A15170 for ; Mon, 13 Dec 1999 12:23:42 -0800 (PST) (envelope-from Davec@unforgettable.com) Received: (qmail 7055 invoked by alias); 13 Dec 1999 20:23:40 -0000 Delivered-To: fixup-freebsd-stable@freebsd.org@fixme Received: (qmail 7043 invoked by uid 0); 13 Dec 1999 20:23:40 -0000 Received: from odsl228.dnvr.uswest.net (HELO Amber.XtremeDev.com) (209.181.79.228) by dnvrpop1.dnvr.uswest.net with SMTP; 13 Dec 1999 20:23:40 -0000 From: Davec Reply-To: Davec@unforgettable.com To: freebsd-ports@freebsd.org, freebsd-stable@freebsd.org, ipfilter@coombs.anu.edu.au Subject: Re: pidentd Date: Mon, 13 Dec 1999 13:22:47 -0700 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <7101.991211@Home.Com> <3.0.6.32.19991212141700.007e2ac0@netcore.home> In-Reply-To: <3.0.6.32.19991212141700.007e2ac0@netcore.home> MIME-Version: 1.0 Message-Id: <99121216534200.40553@Amber.XtremeDev.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 12 Dec 1999, Pekka Savola wrote: > Hi, > > I encountered the similar problem myself - and asked around for solutions. > I have come to the conclusion that there are _no_ identd implementations > for FreeBSD that would support NAT/Masq'ed connections. There are plenty > of them for Linux, but they seem to use proc filesystem and are of no use.. > > Pidentd doesn't support masqed connections. There is patch for it to do > that, but it is Linux only > (http://www.manpages.org/pidentd/pidentd+fm-1.1.patch.gz). > > Midentd and Oidentd support masqed connections in Linux, but not in *BSD. > There are more like these, just check e.g. freshmeat. > > Ident2 doesn't seem to do masqed connections at all > (http://www.nyct.net/~defile/programs/ident2/). > > Cidentd doesn't seem to have been updated since 1996, and there is a nasty > buffer overflow in it. > > Regards, > > Pekka Savola pekkas@netcore.fi > --- Hello, my setup is as follows: FreeBSD server running IPFIlter/IPNat on DSL for my Win98SE workstation. Now, I've modified ident2 server (very very slight, one line only) to answer for all ident requests, including nat'd connections. If I irc from FreeBSD, ident2 would give the irc server whatever ident I choose (.ident file in my home dir) or my real user name, as it should be doing. But if I irc from the Win98 machine ident2 would give a random ident reply. That was the best I could do right now, as I still don't know (YET) how to get ident2 to query IPNat for the current mappings (ipnat -l shows all current table mappings, and I can theoretically parse through that list to match the port numbers sent by the irc server), and then turn around and have ident2 query the mIRC or Xircon client for ident requests to send back to the irc server. Hopefully someone with more knowledge of IPNat or ipfw programming could give some pointers. Theoretically the events that happen should be: 1. Irc server sends request (of form 6666, 5125) to FreeBSD ident2 2. ident2 checks user and sees that no one is irc'ing from the FreeBSD box. 3. ident2 then checks IPNat's table mappings to match any current ports requested by the irc server (don't know how safe this step is...) 4. If it finds the port ident2 would send out a request of it's own to 113 ip of the mapped ports and query for an ident response. 5. mIRC or whatever irc client is running on the Windows box would reply to the ident request. 6. ident2 would take that reply and bounce it to the irc server on the outside. Hopefully this is understandable. Right now I can get the mapping (system("ipnat -l")) and parse it (if I run ident2 as root user and keep it from dropping to a lesser id), but it's all very insecure. And I'm hoping a better way of interfacing with IPNat, and might work something out when I have more time on my hands. This is all preliminary and I don't even know if this would work or not, just thought I'd toss in my 2 cents and get feedback/help. Please, if this is just a lame brained idea that you know for certain won't work, don't hesitate to let me know. d:) Otherwise I would be wasting mine and everyone else's time. Davec P.S. Oh, and let me know if anyone wants the modified ident2, I have it shar'd as a port, with the added patch. And yes, one of these days I will remember to contact the author to let him know how I've mangled his program... -- Davec@unforgettable.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 12:30:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id BBDF415324 for ; Mon, 13 Dec 1999 12:30:50 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id UAA15317 for ; Mon, 13 Dec 1999 20:32:10 GMT (envelope-from arg@arg1.demon.co.uk) Date: Mon, 13 Dec 1999 20:32:09 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: stable@freebsd.org Subject: Problem with psm0 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 have two systems, both now running 3.4-RC (built from the most recent source I had via CTM a couple of hours ago). I also have two very similar mice. However: system1 with mouse1: psm0 not found system1 with mouse2: psm0: model NetScroll Mouse, device ID 0 system2 with mouse1: psm0: model Generic PS/2 mouse, device ID 0 This isn't a real problem for me, as I can swap my mice over, but if anyone is interested in fixing this I can supply further info as required. system1 is a Gigabyte 71X Athlon motherboard (AMD chipset) system2 is a PC-Chips socket-7 motherboard (SiS chipset) mouse1 is a MouseSystems M5 PS/2 optical mouse (model 403011-001) mouse2 is a MouseSystems type 2544 PS/2 optical mouse (model 404273-001) Both have been in use for some time on FreeBSD 2.2 systems (the main difference between mouse1 and mouse2 is that mouse1 cost about 4 times as much and has slightly better buttons!). boot -v messages: System1/Mouse1: Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:ffffffff kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. psm0 not found System1/Mouse2: Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 03 06 psm: status 00 33 44 psm: status 00 33 44 psm: status 00 03 06 psm: data 08 00 00 psm: status 00 02 3c psm0 irq 12 on isa psm0: model NetScroll Mouse, device ID 0-00, 4 buttons psm0: config:00000000, flags:00000000, packet size:6 psm0: syncmask:c8, syncbits:08 (note that this mouse has only 3 buttons, not 4!). Mouse1/System2: Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID:0000 psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: status 10 00 64 psm: data 18 90 00 psm: status 00 02 64 psm: data 18 90 00 psm: status 00 02 64 psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:c0, syncbits:00 (Again, this mouse has 3 buttons). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 13:14:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id C6996151E0; Mon, 13 Dec 1999 13:14:08 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id WAA20095; Mon, 13 Dec 1999 22:11:13 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id WAA12495; Mon, 13 Dec 1999 22:09:41 +0100 (CET) From: Juergen Lock Date: Mon, 13 Dec 1999 22:09:41 +0100 To: Mike Smith Cc: Mike Smith , zzhang@cs.binghamton.edu, freebsd-stable@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG Subject: Re: loader hacks (was: Re: easyboot far into disk) Message-ID: <19991213220941.C8035@saturn.kn-bremen.de> References: <19991212155932.A1107@saturn.kn-bremen.de> <199912130021.QAA04346@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <199912130021.QAA04346@mass.cdrom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 12, 1999 at 04:21:15PM -0800, Mike Smith wrote: > > > > I thought rootdev was fixed a long time back. If it's not, please tell > > > > me and I'll fix it again. 8) > > > > > > Alright I finally got around testing this with a later kern.flp > > > (3.3-R actually), and it still didn't work. ... > > > > Well i played with this once more yesterday and now i know what was > > wrong: Unlike currdev, rootdev needs a `:' at the end... So either > > I'm blind or the manpage needs fixing. :) > > The manpage is probably wrong. $rootdev is obsolete and will be removed > for 4.x (if I remember). > > > I also actually started making that FAQ entry (yeah!), and then > > wondered if you could also make an automagic boot floppy for a root > > disk that is entirely invisible to the BIOS, like when its on a > > BIOS-less (but otherwise supported) SCSI controller. I didn't find > > a way to do it with the original (-stable) loader, but when i made > > this patch, > > 4.x does this differently (better) by passing in a complete identifier. > I need to update the online help and manpage for it. Ah, but that does need changes in the kernel right? The way i did it should even work with an old 2.x kernel, you just have to put it on the floppy... Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 13:46:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from bolero-x.rahul.net (bolero.rahul.net [192.160.13.1]) by hub.freebsd.org (Postfix) with SMTP id 3D9D714FB9 for ; Mon, 13 Dec 1999 13:46:32 -0800 (PST) (envelope-from dhesi@rahul.net) Received: from bolero.rahul.net by bolero-x.rahul.net with SMTP id AA07879 (5.67b8/IDA-1.5 for ); Mon, 13 Dec 1999 13:45:58 -0800 Received: from q.bolero.rahul.net (bolero.rahul.net [192.160.13.1]) by bolero.rahul.net (Postfix) with SMTP id 609873FF03 for ; Mon, 13 Dec 1999 13:45:57 -0800 (PST) Received: (qmail 7874 invoked from network); 13 Dec 1999 21:45:57 -0000 Received: from waltz.rahul.net (192.160.13.9) by bolero.rahul.net with SMTP; 13 Dec 1999 21:45:57 -0000 To: freebsd-stable@freebsd.org Subject: how to rewrite the data field replaceable unit? Date: Mon, 13 Dec 1999 13:45:56 -0800 From: Rahul Dhesi Message-Id: <19991213214557.609873FF03@bolero.rahul.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ FreeBSD 3.0 Release ] I have a scsi disk with two unreadable blocks. The error messages generated by the kernel include this: (da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data field replaceable unit: 20 sks:80,a0 I would like to follow the recommendation. How do I rewrite the data field replaceable unit? What exactly is a data field replaceable unit? I did check with 'camcontrol modepage -m 1 -P 3' and confirmed that the values of AWRE and ARRE are both 1. So the SCSI disk is already doing all the bad block mapping that it can. No response from freebsd-questions, hence I try here. Also, after I sent the above message, I tried using the 'badsect' program. The partition containing the bad blocks is a ccd device, so I did: cd / mkdir BAD badsect BAD n ... where the list of bad blocks was as reported by fsck. One of the bad blocks did get converted into a file, but for the rest, 'badsect' reported that it was a non-data area and could not be attached. So now I have a ccd filesystem with some bad blocks that can't be collected by badsect, but which do generate read errors during normal operation. Is there any workaround for this? Rahul Dhesi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 14: 6:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6B02014C87 for ; Mon, 13 Dec 1999 14:06:37 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id PAA69075; Mon, 13 Dec 1999 15:06:35 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id PAA46640; Mon, 13 Dec 1999 15:06:35 -0700 (MST) Message-Id: <199912132206.PAA46640@harmony.village.org> To: Peter Radcliffe Subject: Re: pidentd Cc: freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Mon, 13 Dec 1999 13:30:31 EST." <19991213133031.C1355@pir.net> References: <19991213133031.C1355@pir.net> <19991213124609.A1355@pir.net> <199912131016.CAA21812@mass.cdrom.com> <19991213124609.A1355@pir.net> <199912131805.LAA45050@harmony.village.org> Date: Mon, 13 Dec 1999 15:06:35 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991213133031.C1355@pir.net> Peter Radcliffe writes: : 2) Also IIRC the spec allows for multiple requests per connection. It does not, or at least the first version certainly didn't. I've not checked the latest version to see if it was added or not. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 14:33:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 5858C15190 for ; Mon, 13 Dec 1999 14:33:39 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id PAA13285; Mon, 13 Dec 1999 15:33:28 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912132233.PAA13285@freeway.dcfinc.com> Subject: Re: SYN Hardening patches? / SYN Code in 3.4-RC In-Reply-To: from Brad Knowles at "Dec 12, 99 11:09:55 pm" To: blk@skynet.be (Brad Knowles) Date: Mon, 13 Dec 1999 15:33:28 -0700 (MST) Cc: john@loverso.southborough.ma.us, 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, Brad Knowles wrote: > At 5:08 PM -0500 1999/12/12, John Robert LoVerso wrote: > > > RFC 1644 defines "T/TCP: TCP Extensions for Transactions", which describes > > a way to to a complete transactional TCP session with as little as two total > > datagrams. The first datagram has both SYN and FIN flags set. > > Thanks! Looks like I need to do some readin'.... I'd recommend "TCP/IP Illustrated, Volume 3" by W. Richard Stevens (ISBN 0-201-63495-3) as a starting place. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 14:58: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id C6B0814C16 for ; Mon, 13 Dec 1999 14:58:06 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id PAA13504; Mon, 13 Dec 1999 15:58:03 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912132258.PAA13504@freeway.dcfinc.com> Subject: Re: pidentd In-Reply-To: <19991213124609.A1355@pir.net> from Peter Radcliffe at "Dec 13, 99 12:46:09 pm" To: pir@pir.net (Peter Radcliffe) Date: Mon, 13 Dec 1999 15:58:03 -0700 (MST) Cc: 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, Peter Radcliffe wrote: > > #!/usr/bin/perl > $| = 1; > while (<>) { > $_ =~ s/\r\n$//; > print STDOUT "$_ : USERID : UNIX : bite-me\r\n"; > exit 0; > } Actually, TFM has a specific recommendation for a non-informative response. Check this: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Script started on Mon Dec 13 15:53:37 1999 % telnet firewall 113 Trying 192.168.1.254... Connected to firewall.dcfinc.com. Escape character is '^]'. :ERROR:HIDDEN-USER Connection closed by foreign host. % exit Script done on Mon Dec 13 15:54:06 1999 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 15:24:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id B15FE151ED for ; Mon, 13 Dec 1999 15:24:18 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 11xepF-0002Ma-00 for freebsd-stable@FreeBSD.ORG; Mon, 13 Dec 1999 18:24:17 -0500 Date: Mon, 13 Dec 1999 18:24:16 -0500 From: Peter Radcliffe To: freebsd-stable@FreeBSD.ORG Subject: Re: pidentd Message-ID: <19991213182416.J1355@pir.net> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <19991213124609.A1355@pir.net> <199912132258.PAA13504@freeway.dcfinc.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912132258.PAA13504@freeway.dcfinc.com>; from chad@DCFinc.com on Mon, Dec 13, 1999 at 03:58:03PM -0700 X-fish: < Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Chad R. Larson" probably said: > Actually, TFM has a specific recommendation for a non-informative > response. I know, and use this on my machines, but I believe that the specific question - irc servers that require ident responses - don't like the standard non-informative responses either so if you don't want to give that information you have to provide something that doesn't follow the RFC. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 17: 9:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from daemon.best.ca (cr262311-a.lngly1.bc.wave.home.com [24.113.173.186]) by hub.freebsd.org (Postfix) with ESMTP id DF885151C6; Mon, 13 Dec 1999 17:09:11 -0800 (PST) (envelope-from riso@best.ca) Received: by daemon.best.ca (Postfix, from userid 1000) id E386AD7211; Mon, 13 Dec 1999 17:09:08 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by daemon.best.ca (Postfix) with ESMTP id C9DE1C989F; Mon, 13 Dec 1999 17:09:08 -0800 (PST) Date: Mon, 13 Dec 1999 17:09:08 -0800 (PST) From: Richard Furda To: FreeBSD-stable@freebsd.org Cc: FreeBSD-current@freebsd.org Subject: QIC 40/80 floppy tape drive controller 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 Hello, I have a QIC 40/80 clone floppy tape drive controller (running 3.3-stable) and wondering if anyone is working/thinking about porting the ft driver to 3.X/4.X branch. I understand the driver was "removed" in 2.2.8 due to incompatibility issues. I'd like to help out, thus give access to a machine with the QIC 40/80 floppy tape controller. Thanks, Rich To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 17:40:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 7973A14E1A for ; Mon, 13 Dec 1999 17:40:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02097; Mon, 13 Dec 1999 17:43:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912140143.RAA02097@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Rahul Dhesi Cc: freebsd-stable@freebsd.org Subject: Re: how to rewrite the data field replaceable unit? In-reply-to: Your message of "Mon, 13 Dec 1999 13:45:56 PST." <19991213214557.609873FF03@bolero.rahul.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 17:43:29 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > [ FreeBSD 3.0 Release ] > I have a scsi disk with two unreadable blocks. The error messages > generated by the kernel include this: > > (da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data field replaceable unit: 20 sks:80,a0 > > I would like to follow the recommendation. How do I rewrite the data > field replaceable unit? What exactly is a data field replaceable unit? That's two things, 'data' and 'field replaceable unit'. The FRU code tells you which part of the drive is failing - in this case the vendor code for the broken bit is '20'. > I did check with 'camcontrol modepage -m 1 -P 3' and confirmed that the > values of AWRE and ARRE are both 1. So the SCSI disk is already doing > all the bad block mapping that it can. The error message actually makes more sense once you understand how bad-block forwarding works. The drive will never forward a block if it involves losing the data that it can't get out of the block. ie. Error while writing -> write data to replacement block, forward block Recovered read error -> move data to replacement block, forward block Unrecovered read error -> return read error, do not forward block In order to have the block forwarded (replaced), you need to put the drive in a situation where it can guarantee that no data loss will occur. The easiest way to do this is to work out which file contains the bad block, and copy it somewhere else, then delete the original. Things are a bit harder if the bad block is buried in some metadata somewhere. You can also unmount the drive and write to the block manually (write a small program that seeks to the bad block and then writes to it). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 18:30:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-4.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.132]) by hub.freebsd.org (Postfix) with ESMTP id 5729B1537B; Mon, 13 Dec 1999 18:30:35 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA01373; Mon, 13 Dec 1999 23:03:36 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA02922; Mon, 13 Dec 1999 23:05:14 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912132305.XAA02922@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Brian Somers Cc: "CHOI, Junho" , Jon Hamilton , current@FreeBSD.org, stable@FreeBSD.org, brian@hak.lan.Awfulhak.org, brian@hak.lan.Awfulhak.org Subject: Re: ppp over pty: trying to detect CD In-Reply-To: Message from Brian Somers of "Mon, 13 Dec 1999 17:59:24 GMT." <199912131759.RAA00338@hak.lan.Awfulhak.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Dec 1999 23:05:14 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is now fixed in -stable (and -current). > > >>>>> "JH" == Jon Hamilton writes: > > > > JH> Running -current from this afternoon, I am having a strange > > JH> symptom with ppp over a pty; ppp does not detect that the pty > > JH> does not support carrier, and will cycle once per second > > JH> waiting for CD to appear. Putting ``set cd off'' in my > > JH> ppp.conf for that target fixed the problem, but I thought I'd > > JH> mention it nonetheless, since that didn't used to be > > JH> required. Certainly not all that big a deal, but I thought it > > JH> was worth a mention. > > > > JH> FreeBSD 4.0-CURRENT #13: Sat Dec 11 20:31:42 CST 1999 > > > > I am using 3-STABLE but I have the same problem with you. I think it > > comes after adding pppoe support in pppd(after 3.3-RELEASE). I am > > -STABLE user but I had to back to 3.3-RELEASE's ppp... I am using ADSL > > service with pptpclient. > > > > JH> and the syslog with debugging turned on, with no "set cd" in the config: > > > > JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] > > JH> Dec 11 20:48:20 woodstock ppp[3106]: tun1: Debug: Waiting for carrier > > JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: deflink: Using tty_Timeout [0x8072d44] > > JH> Dec 11 20:48:21 woodstock ppp[3106]: tun1: Debug: Waiting for carrier > > > > JH> [ and on and on and on ] > > > > -- > > +++ Any opinions in this posting are my own and not those of my employers +++ > > CHOI, Junho > > - Korea FreeBSD Users Group > > - Public Service, Youido Post Office - Web Data Bank -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 19: 2:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mta4.rcsntx.swbell.net (mta4.rcsntx.swbell.net [151.164.30.28]) by hub.freebsd.org (Postfix) with ESMTP id CEEF615505 for ; Mon, 13 Dec 1999 19:02:30 -0800 (PST) (envelope-from noslenj@swbell.net) Received: from swbell.net ([207.193.26.219]) by mta4.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FMP0086CN41XP@mta4.rcsntx.swbell.net> for freebsd-stable@freebsd.org; Mon, 13 Dec 1999 21:02:27 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by swbell.net (8.9.3/8.9.3) with ESMTP id TAA00497 for ; Mon, 13 Dec 1999 19:10:33 -0600 (CST envelope-from noslenj@swbell.net) Date: Mon, 13 Dec 1999 19:10:33 -0600 (CST) From: Jay Nelson Subject: Shame (Was: Re: PS/2 mouse troubles?) In-reply-to: To: 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 My apologies to everyone. My mouse freezing and behavior problems appear to have been caused by not cleaning out my compile directory prior to building a new kernel. I added: options KBDIO_DEBUG=2 options PSM_DEBUG=2 per suggestion from Kazu and deleted the compile directory as I used to do. So far, since rebuilding a clean, new kernel, I've experienced no problems. It looks, at this point, to be a self-induced problem. -- Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 22:55:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 2A2D515310 for ; Mon, 13 Dec 1999 22:55:42 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id BAA31411 for ; Tue, 14 Dec 1999 01:55:40 -0500 Date: Tue, 14 Dec 1999 01:55:40 -0500 (EST) From: Mike Nowlin To: freebsd-stable@freebsd.org Subject: getty & "ic" chat scripts 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've been fighting with getty's "ic" modem init scripts for the last two hours, and I'm getting really upset with it (attitude toned down a few degrees for the sake of the mailing list). Does this actually work, or is it one of those things that is so infrequently used that it broke seven versions ago, and nobody's noticed? I'm half-inclined to believe the latter, since setting the "dc" variable (to turn on chat-script debugging) didn't seem to do anything -- modifying the source to set chat_debug=15 in chat.c:getty_chat() did start the debugging. (I'm willing to fix the source if it turns out to be a bug, but I'd like some input first if anybody's successfully using it.) This is on 3.4-RC as of Dec 11, and also on an older 3.2 box. BTW - I'm testing with the :ic="" ATE0Q0V1\r OK\r ATS0=0\r OK\r: string out of the gettytab manpage, and the modem's programmed to respond accordingly. (Plus several variations.) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 13 22:56:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 2692315252; Mon, 13 Dec 1999 22:56:30 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA70819; Mon, 13 Dec 1999 23:56:23 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA50727; Mon, 13 Dec 1999 23:56:23 -0700 (MST) Message-Id: <199912140656.XAA50727@harmony.village.org> To: Richard Furda Subject: Re: QIC 40/80 floppy tape drive controller Cc: FreeBSD-stable@FreeBSD.ORG, FreeBSD-current@FreeBSD.ORG In-reply-to: Your message of "Mon, 13 Dec 1999 17:09:08 PST." References: Date: Mon, 13 Dec 1999 23:56:22 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Richard Furda writes: : I have a QIC 40/80 clone floppy tape drive controller (running : 3.3-stable) and wondering if anyone is working/thinking about porting the : ft driver to 3.X/4.X branch. I understand the driver was "removed" : in 2.2.8 due to incompatibility issues. I'd like to help out, thus give : access to a machine with the QIC 40/80 floppy tape controller. At this point, if you aren't writing it, it ain't happening. There are plentty of people who have the hardware, but none have made them work. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 0:14:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id A87B115570 for ; Tue, 14 Dec 1999 00:14:46 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:KWzmZoDS+mpoh9TzqLWAeWeCd5HGWciw@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id RAA02613; Tue, 14 Dec 1999 17:14:34 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id RAA06349; Tue, 14 Dec 1999 17:19:36 +0900 (JST) Message-Id: <199912140819.RAA06349@zodiac.mech.utsunomiya-u.ac.jp> To: Andrew Gordon Cc: stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problem with psm0 In-reply-to: Your message of "Mon, 13 Dec 1999 20:32:09 GMT." References: Date: Tue, 14 Dec 1999 17:19:35 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I have two systems, both now running 3.4-RC (built from the most recent >source I had via CTM a couple of hours ago). I also have two very similar >mice. However: [...] >system1 is a Gigabyte 71X Athlon motherboard (AMD chipset) >system2 is a PC-Chips socket-7 motherboard (SiS chipset) > >mouse1 is a MouseSystems M5 PS/2 optical mouse (model 403011-001) >mouse2 is a MouseSystems type 2544 PS/2 optical mouse (model 404273-001) >Both have been in use for some time on FreeBSD 2.2 systems (the main >difference between mouse1 and mouse2 is that mouse1 cost about 4 times as >much and has slightly better buttons!). When you were running FreeBSD 2.2, were you using the above motherboards? >System1/Mouse1: [...] >psm0: current command byte:0047 >kbdc: TEST_AUX_PORT status:0000 >kbdc: RESET_AUX return code:00fa >kbdc: RESET_AUX status:ffffffff >kbdc: DIAGNOSE status:0055 >kbdc: TEST_KBD_PORT status:0000 >psm0: failed to reset the aux device. >psm0 not found Do you by any chance use any console switch? We may have a timing problem here. Would you send us the full dmesg output? In the meantime, try adding the following options in your kernel configuration file. options KBDIO_MAXWAIT 10 The default value is 5. Increase the value if your mouse is not still recognized. >System1/Mouse2: [...] >psm0: model NetScroll Mouse, device ID 0-00, 4 buttons >psm0: config:00000000, flags:00000000, packet size:6 >psm0: syncmask:c8, syncbits:08 > >(note that this mouse has only 3 buttons, not 4!). The psm driver is not necessarily able to detect the number of buttons correctly. But, it doesn't matter. Even if it gets the number wrong, it works without any problem. >Mouse1/System2: [...] >psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons >psm0: config:00000000, flags:00000000, packet size:3 >psm0: syncmask:c0, syncbits:00 > >(Again, this mouse has 3 buttons). Ditto. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 4: 0:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from waltz.rahul.net (waltz.rahul.net [192.160.13.9]) by hub.freebsd.org (Postfix) with ESMTP id 9B45E14EC0 for ; Tue, 14 Dec 1999 04:00:45 -0800 (PST) (envelope-from dhesi@rahul.net) Received: by waltz.rahul.net (Postfix, from userid 104) id 10BC021C; Tue, 14 Dec 1999 04:00:34 -0800 (PST) To: freebsd-stable@freebsd.org Subject: Re: how to rewrite the data field replaceable unit? References: X-Newsreader: NN version 6.5.1 (NOV) Message-Id: <19991214120034.10BC021C@waltz.rahul.net> Date: Tue, 14 Dec 1999 04:00:34 -0800 (PST) From: dhesi@rahul.net (Rahul Dhesi) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith writes: >> (da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data field replaceable unit: 20 sks:80,a0 ... >That's two things, 'data' and 'field replaceable unit'. The FRU code >tells you which part of the drive is failing - in this case the vendor >code for the broken bit is '20'. Thanks. A suggestion to the Device Driver Gods: Please make error messages understandable to the rest of us. >...The drive will never forward a block if it >involves losing the data that it can't get out of the block. >Unrecovered read error -> return read error, do not forward block Which makes sense. Thanks. >In order to have the block forwarded (replaced), you need to put the drive >in a situation where it can guarantee that no data loss will occur. The >easiest way to do this is to work out which file contains the bad block, >and copy it somewhere else, then delete the original.... This confuses me. Even if I have deleted the file that contains the bad block, how is the disk hardware to know that? >You can also unmount the drive and write to the block manually (write a >small program that seeks to the bad block and then writes to it). This seems promising. If I succeed in writing to that bad block, and later cause a read from it, and a recoverable error occurs during the read, the disk will likely remap the block. One more question: fsck reports some unreadable block numbers. What is the block size assumed by fsck when it reports that block n is bad? Is it the same as the block size of the filesystem (in this case 8192 bytes)? And if so, then to rewrite the block, would I seek to (block no. * 8192) and then write 8192 bytes? And yet another question: When 'badsect' reports that a bad block cannot be attached because it is in a a non-data area, what does this mean? -- Rahul Dhesi See my UUNET spam mini-faq at: http://www.rahul.net/dhesi/uunet.faq.txt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 4:20:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 57B8D14F77 for ; Tue, 14 Dec 1999 04:20:36 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11xqgA-000Ak2-00; Tue, 14 Dec 1999 14:03:42 +0200 From: Sheldon Hearn To: Pekka Savola Cc: Spidey , freebsd-stable@FreeBSD.ORG Subject: Re: Selecting which programs to have in the base system In-reply-to: Your message of "Mon, 13 Dec 1999 14:41:27 EST." <14421.19431.833872.458577@anarcat.dyndns.org> Date: Tue, 14 Dec 1999 14:03:42 +0200 Message-ID: <41293.945173022@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 13 Dec 1999 14:41:27 EST, Spidey wrote: > > How can I manipulate -easily- which base system files (in e.g. /bin, > > /sbin, /usr/bin, /usr/sbin) will be installed/compiled when I cvsup the > > sources and make world ? > > I don't think that's a really good idea. It's not really 'made' that > way. Hi Pekka, "Spidey" is right. FreeBSD is an integral operating system, not a collection of bits and pieces. The advantage of having a single, known base system is that support is simplified and migrating administrators find it fairly easy to merge solutions across from one FreeBSD host to the next. There are two cases where it's understandable that you'd want to remove certain components from the base system: * For embedded systems, where space is a serious issue. * For secure/specialty systems where only that which is needed for a specific taks should be made available to users. FreeBSD caters for these two scenarios by providing a mechanism through which you can engineer your own release with the ``release'' target. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 5: 4:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (pooh.elsevier.nl [145.36.9.32]) by hub.freebsd.org (Postfix) with ESMTP id 8BB5F14E1D for ; Tue, 14 Dec 1999 05:04:12 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id NAA00416; Tue, 14 Dec 1999 13:04:27 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <41293.945173022@axl.noc.iafrica.com> Date: Tue, 14 Dec 1999 13:04:27 -0000 (GMT) From: "Steve O'Hara-Smith" To: Sheldon Hearn Subject: Re: Selecting which programs to have in the base system Cc: freebsd-stable@FreeBSD.ORG, Spidey , Pekka Savola Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 14-Dec-99 Sheldon Hearn wrote: > FreeBSD caters for these two scenarios by providing a mechanism through > which you can engineer your own release with the ``release'' target. The release/picobsd part of the source tree is probably a good place to start looking for ideas if you want to do this sort of thing yourself. ------------------------------------------------------- Tell a computer to WIN and ... ... You lose ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 5:26:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from test4.ipf.de (test2.ipf.de [195.211.170.112]) by hub.freebsd.org (Postfix) with SMTP id 86E4114EF5 for ; Tue, 14 Dec 1999 05:26:09 -0800 (PST) (envelope-from C.Jachmann@gigabell.net) Received: (qmail 21548 invoked from network); 14 Dec 1999 13:26:07 -0000 Received: from stng.ipf.de (HELO gigabell.net) (195.211.170.10) by test4.ipf.de with SMTP; 14 Dec 1999 13:26:07 -0000 Message-ID: <3856456F.BC978766@gigabell.net> Date: Tue, 14 Dec 1999 14:26:07 +0100 From: Christian Jachmann Organization: Gigabell AG X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -- Christian Jachmann Gigabell AG / Technik 069/17084-0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 8: 6:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id C05A614E5C for ; Tue, 14 Dec 1999 08:06:14 -0800 (PST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id RAA04344 for ; Tue, 14 Dec 1999 17:07:40 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Tue, 14 Dec 1999 17:07:40 +0100 (CET) From: "O. Hartmann" To: freebsd-stable@freebsd.org Subject: Parallelport 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 Dear Sirs. I administer several FreeBSD boxes (now FBSD 3.4-RC). One of them plays the role of our printserver of our institute. This box is equippted with AMD K6-2 500 MHz CPU, GigaByte GA-5AA main PCB with ALi 1542 100MHz Aladin-V chipset, NIC is 3COM 3C905B 100Mbit fullduplex mode, memory 128 MB FSB100, Adaptec 2940U controller and an additional parallel port card, made in china! This additional parallelport card seems to be the troublesome unit on ISA bus but the problem occurs with other multi i/o cards running the parallelport. One of our printers is attached to this port an whenever a printjob is queued and sent to the printer via parallelport, the server is unreachable over the network. Ping latencies pushes up from 0.200 ms to 16 ms and higher. Printing over the built in parallelport does not reveal this phenomenon. Both ports are using IRQs and DMA, port 1 has IRQ 7, dirq 1, port 2 has IRQ 5, dirq 7. The additional card is capable of EPP 1.9 and I set the flag for this in kernel config file. So far all things seems to be all right. But why is the usage of any IO card, especially the parallel port on additional cards blocking the PCI bus? Is this a misconfiguartion? I tried all possibilities in BIOS configuration, I used the most moderate options but with no effect. Then I used the fastest modes, no effect. STill the same, printing or sending data over parallel port 2 blocks the NIC and slows maybe down SCSI controller. Maybe this problem is related to the chipset. I was said that the VIA chipset for Socket7 was the most popular chipset and I suggested for myself to order a new main PCB with this chipset but who can guarantee that this problem is not occuring on this chipset as it does on ALi chipset? Is anybody out there who has an idea? Hints, tips? Does anyone know what the problem is caused by? Well, any tips, hints, suggestions are appreciated and highly welcome! Thanks in advance, Oliver Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 8:53:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from manor.msen.com (manor.msen.com [148.59.4.13]) by hub.freebsd.org (Postfix) with ESMTP id A90F41520C for ; Tue, 14 Dec 1999 08:53:10 -0800 (PST) (envelope-from wayne@staff.msen.com) Received: from manor.msen.com (LOCALHOST [127.0.0.1]) by manor.msen.com (8.8.8/8.8.8) with ESMTP id LAA10196 for ; Tue, 14 Dec 1999 11:53:09 -0500 (EST) (envelope-from wayne@manor.msen.com) Message-Id: <199912141653.LAA10196@manor.msen.com> To: freebsd-stable@FreeBSD.ORG Subject: What all does installworld fail to install? From: "Michael R. Wayne" Date: Tue, 14 Dec 1999 11:53:08 -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Goal is to upgrade a box by building from source from, say, 3.2 to 3.4RC, using NFS and a box which has already had "make buildworld ; make installworld" done on it. What am I missing: install 3.4RC kernel on box to be upgraded reboot mount /usr/src and /usr/obj make installworld /stand is not upgraded - what ELSE is missing? (BTW, doing a make in release/sysinstall yields JUST a /stand/sysinstall, which is half the size. /\/\ \/\/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 9:27:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by hub.freebsd.org (Postfix) with ESMTP id 504A114ED7 for ; Tue, 14 Dec 1999 09:27:30 -0800 (PST) (envelope-from jeffrl@wantabe.com) Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by cutter.wantabe.com (8.9.3/8.9.3) with ESMTP id LAA15525 for ; Tue, 14 Dec 1999 11:27:29 -0600 (CST) (envelope-from jeffrl@wantabe.com) Date: Tue, 14 Dec 1999 11:27:29 -0600 (CST) From: "Jeffrey J. Libman" To: freebsd-stable@freebsd.org Subject: mountd and rpc.statd won't run 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 have 2 freeBSD systems, both running from an oct 11 cvsup and build. both were running fine up until this weekend. then on one, i moved a number of virtual web sites and ip's aliased to lo0 to it, and now rpc.statd and mountd will not run. i don't know if the failure is related to the ip changes. rpc.statd hangs and won't run at boot time. the message i get from mountd is: mountd[pidno]: can't register mount when i try to run it without the -r (rpc) switch. any suggestions or ideas will be greatly appreciated. cheers, jeff -- | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 9:45:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by hub.freebsd.org (Postfix) with ESMTP id 27D6114E6E for ; Tue, 14 Dec 1999 09:45:49 -0800 (PST) (envelope-from jeffrl@wantabe.com) Received: from localhost (jeffrl@localhost) by cutter.wantabe.com (8.9.3/8.9.3) with ESMTP id GAA13902 for ; Tue, 14 Dec 1999 06:39:31 -0600 (CST) (envelope-from jeffrl@wantabe.com) Date: Tue, 14 Dec 1999 06:39:31 -0600 (CST) From: "Jeffrey J. Libman" To: freebsd-stable@freebsd.org Subject: mountd and rpc.statd won't run 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 have 2 freeBSD systems, both running from an oct 11 cvsup and build. both were running fine up until this weekend. then on one, i moved a number of virtual web sites and ip's aliased to lo0 to it, and now rpc.statd and mountd will not run. i don't know if the failure is related to the ip changes. rpc.statd hangs and won't run at boot time. the message i get from mountd is: mountd[pidno]: can't register mount when i try to run it without the -r (rpc) switch. any suggestions or ideas will be greatly appreciated. cheers, jeff -- | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 9:56: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles505.castles.com [208.214.165.69]) by hub.freebsd.org (Postfix) with ESMTP id 6125814A2F for ; Tue, 14 Dec 1999 09:55:57 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA03135; Tue, 14 Dec 1999 09:57:11 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912141757.JAA03135@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: dhesi@rahul.net (Rahul Dhesi) Cc: freebsd-stable@freebsd.org Subject: Re: how to rewrite the data field replaceable unit? In-reply-to: Your message of "Tue, 14 Dec 1999 04:00:34 PST." <19991214120034.10BC021C@waltz.rahul.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Dec 1999 09:57:11 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith writes: > > >> (da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data field replaceable unit: 20 sks:80,a0 > ... > > >That's two things, 'data' and 'field replaceable unit'. The FRU code > >tells you which part of the drive is failing - in this case the vendor > >code for the broken bit is '20'. > > Thanks. > > A suggestion to the Device Driver Gods: Please make error messages > understandable to the rest of us. That's kinda difficult, actually. Error messages need to be accurate and understandable to people that understand what's really going on. It's not the job of an error message to explain how the hardware works. > >In order to have the block forwarded (replaced), you need to put the drive > >in a situation where it can guarantee that no data loss will occur. The > >easiest way to do this is to work out which file contains the bad block, > >and copy it somewhere else, then delete the original.... > > This confuses me. Even if I have deleted the file that contains the bad > block, how is the disk hardware to know that? It doesn't. But now the block is free and won't be referenced, and next time it's referenced it's going to be written to, which will give the drive a chance to forward it. > >You can also unmount the drive and write to the block manually (write a > >small program that seeks to the bad block and then writes to it). > > This seems promising. If I succeed in writing to that bad block, > and later cause a read from it, and a recoverable error occurs during > the read, the disk will likely remap the block. Either that, or if the block is so badly damaged that the write fails it will be forwarded immediately. > One more question: > > fsck reports some unreadable block numbers. What is the block size > assumed by fsck when it reports that block n is bad? Is it the same > as the block size of the filesystem (in this case 8192 bytes)? > And if so, then to rewrite the block, would I seek to > (block no. * 8192) and then write 8192 bytes? No; to the best of my knowledge blocks are always reported in the device block size (typically 512 bytes). > And yet another question: > > When 'badsect' reports that a bad block cannot be attached because it is > in a a non-data area, what does this mean? It means that the block is being used for metadata (ie. a directory, cylinder group data, etc). Recovering from this sort of bad block is very difficult. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 10:50:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 7AD9A15272 for ; Tue, 14 Dec 1999 10:50:22 -0800 (PST) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 1FF913834; Tue, 14 Dec 1999 12:50:19 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id MAA28943; Tue, 14 Dec 1999 12:50:18 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Tue, 14 Dec 1999 12:50:18 -0600 (CST) From: Thomas Veldhouse To: "Jeffrey J. Libman" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run 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 I used to have this problem with the de0 interface. I posted about it here and I never recieved a single response. Something was indeed broken! However, I finally found that if I removed "auto" from the list of interfaces in rc.conf - everything worked as it was supposed to. I hope this solves you problem. As an FYI - the same problem existed in CURRENT. I have not tried it since on a newer build. Tom Veldhouse veldy@visi.com On Tue, 14 Dec 1999, Jeffrey J. Libman wrote: > i have 2 freeBSD systems, both running from an oct 11 cvsup and > build. both were running fine up until this weekend. then on one, i moved > a number of virtual web sites and ip's aliased to lo0 to it, and now > rpc.statd and mountd will not run. > > i don't know if the failure is related to the ip changes. > > rpc.statd hangs and won't run at boot time. > > the message i get from mountd is: > > mountd[pidno]: can't register mount > > when i try to run it without the -r (rpc) switch. > > any suggestions or ideas will be greatly appreciated. > > cheers, > jeff > > -- > | > |\ +------------------------------+ > Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | > Wantabe, Inc. |__\ +------------------------------+ > jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ > > > > 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 Tue Dec 14 11: 1:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by hub.freebsd.org (Postfix) with ESMTP id 6870C14DE8 for ; Tue, 14 Dec 1999 11:01:17 -0800 (PST) (envelope-from jeffrl@wantabe.com) Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by cutter.wantabe.com (8.9.3/8.9.3) with ESMTP id NAA16214; Tue, 14 Dec 1999 13:01:12 -0600 (CST) (envelope-from jeffrl@wantabe.com) Date: Tue, 14 Dec 1999 13:01:12 -0600 (CST) From: "Jeffrey J. Libman" To: Thomas Veldhouse Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run 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 i have an ed0 not de0 interface...could that be it? it is a realtek ne2000 clone. i do not have auto in the interace list. mebbe i need to replace the realtek...i've read other things bad about it as well. thanks. jeff -- | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ On Tue, 14 Dec 1999, Thomas Veldhouse wrote: > I used to have this problem with the de0 interface. I posted about it > here and I never recieved a single response. Something was indeed broken! > However, I finally found that if I removed "auto" from the list of > interfaces in rc.conf - everything worked as it was supposed to. > > I hope this solves you problem. As an FYI - the same problem existed in > CURRENT. I have not tried it since on a newer build. > > Tom Veldhouse > veldy@visi.com > > On Tue, 14 Dec 1999, Jeffrey J. Libman wrote: > > > i have 2 freeBSD systems, both running from an oct 11 cvsup and > > build. both were running fine up until this weekend. then on one, i moved > > a number of virtual web sites and ip's aliased to lo0 to it, and now > > rpc.statd and mountd will not run. > > > > i don't know if the failure is related to the ip changes. > > > > rpc.statd hangs and won't run at boot time. > > > > the message i get from mountd is: > > > > mountd[pidno]: can't register mount > > > > when i try to run it without the -r (rpc) switch. > > > > any suggestions or ideas will be greatly appreciated. > > > > cheers, > > jeff > > > > -- > > | > > |\ +------------------------------+ > > Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | > > Wantabe, Inc. |__\ +------------------------------+ > > jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | > > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ > > > > > > > > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 11:11:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail-out.visi.com (kauket.visi.com [209.98.98.22]) by hub.freebsd.org (Postfix) with ESMTP id 162B815327 for ; Tue, 14 Dec 1999 11:11:14 -0800 (PST) (envelope-from veldy@visi.com) Received: from isis.visi.com (isis.visi.com [209.98.98.8]) by mail-out.visi.com (Postfix) with ESMTP id 5A8EF390C; Tue, 14 Dec 1999 13:11:09 -0600 (CST) Received: from localhost (veldy@localhost) by isis.visi.com (8.8.8/8.8.8) with ESMTP id NAA00422; Tue, 14 Dec 1999 13:11:09 -0600 (CST) X-Authentication-Warning: isis.visi.com: veldy owned process doing -bs Date: Tue, 14 Dec 1999 13:11:09 -0600 (CST) From: Thomas Veldhouse To: "Jeffrey J. Libman" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run 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 I believe that ed0 is appropriate for ne2000. de0 is for "tulip" cards. It seems alot DEC (or Intel) support is included under tulip. Tom Veldhouse veldy@visi.com On Tue, 14 Dec 1999, Jeffrey J. Libman wrote: > i have an ed0 not de0 interface...could that be it? it is a realtek ne2000 > clone. i do not have auto in the interace list. > > mebbe i need to replace the realtek...i've read other things bad about it > as well. > > thanks. > > jeff > > -- > | > |\ +------------------------------+ > Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | > Wantabe, Inc. |__\ +------------------------------+ > jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ > > On Tue, 14 Dec 1999, Thomas Veldhouse wrote: > > > I used to have this problem with the de0 interface. I posted about it > > here and I never recieved a single response. Something was indeed broken! > > However, I finally found that if I removed "auto" from the list of > > interfaces in rc.conf - everything worked as it was supposed to. > > > > I hope this solves you problem. As an FYI - the same problem existed in > > CURRENT. I have not tried it since on a newer build. > > > > Tom Veldhouse > > veldy@visi.com > > > > On Tue, 14 Dec 1999, Jeffrey J. Libman wrote: > > > > > i have 2 freeBSD systems, both running from an oct 11 cvsup and > > > build. both were running fine up until this weekend. then on one, i moved > > > a number of virtual web sites and ip's aliased to lo0 to it, and now > > > rpc.statd and mountd will not run. > > > > > > i don't know if the failure is related to the ip changes. > > > > > > rpc.statd hangs and won't run at boot time. > > > > > > the message i get from mountd is: > > > > > > mountd[pidno]: can't register mount > > > > > > when i try to run it without the -r (rpc) switch. > > > > > > any suggestions or ideas will be greatly appreciated. > > > > > > cheers, > > > jeff > > > > > > -- > > > | > > > |\ +------------------------------+ > > > Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | > > > Wantabe, Inc. |__\ +------------------------------+ > > > jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | > > > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ > > > > > > > > > > > > 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 > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 11:14:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from diarmadhi.mushhaven.net (diarmadhi.mushhaven.net [63.75.111.197]) by hub.freebsd.org (Postfix) with ESMTP id D91311530F for ; Tue, 14 Dec 1999 11:14:16 -0800 (PST) (envelope-from mistwolf@diarmadhi.mushhaven.net) Received: (from mistwolf@localhost) by diarmadhi.mushhaven.net (8.9.3/8.9.3) id LAA25102; Tue, 14 Dec 1999 11:13:29 -0800 (PST) (envelope-from mistwolf) Date: Tue, 14 Dec 1999 11:13:29 -0800 From: Jamie Norwood To: Thomas Veldhouse Cc: "Jeffrey J. Libman" , freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run Message-ID: <19991214111328.A25086@mushhaven.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, wouldn't he want rl0, for realtek cards? Jamie On Tue, Dec 14, 1999 at 01:11:09PM -0600, Thomas Veldhouse wrote: > I believe that ed0 is appropriate for ne2000. de0 is for "tulip" cards. > It seems alot DEC (or Intel) support is included under tulip. > > Tom Veldhouse > veldy@visi.com > > On Tue, 14 Dec 1999, Jeffrey J. Libman wrote: > > > i have an ed0 not de0 interface...could that be it? it is a realtek ne2000 > > clone. i do not have auto in the interace list. > > > > mebbe i need to replace the realtek...i've read other things bad about it > > as well. > > > > thanks. > > > > jeff > > > > -- > > | > > |\ +------------------------------+ > > Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | > > Wantabe, Inc. |__\ +------------------------------+ > > jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | > > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ > > > > On Tue, 14 Dec 1999, Thomas Veldhouse wrote: > > > > > I used to have this problem with the de0 interface. I posted about it > > > here and I never recieved a single response. Something was indeed broken! > > > However, I finally found that if I removed "auto" from the list of > > > interfaces in rc.conf - everything worked as it was supposed to. > > > > > > I hope this solves you problem. As an FYI - the same problem existed in > > > CURRENT. I have not tried it since on a newer build. > > > > > > Tom Veldhouse > > > veldy@visi.com > > > > > > On Tue, 14 Dec 1999, Jeffrey J. Libman wrote: > > > > > > > i have 2 freeBSD systems, both running from an oct 11 cvsup and > > > > build. both were running fine up until this weekend. then on one, i moved > > > > a number of virtual web sites and ip's aliased to lo0 to it, and now > > > > rpc.statd and mountd will not run. > > > > > > > > i don't know if the failure is related to the ip changes. > > > > > > > > rpc.statd hangs and won't run at boot time. > > > > > > > > the message i get from mountd is: > > > > > > > > mountd[pidno]: can't register mount > > > > > > > > when i try to run it without the -r (rpc) switch. > > > > > > > > any suggestions or ideas will be greatly appreciated. > > > > > > > > cheers, > > > > jeff > > > > > > > > -- > > > > | > > > > |\ +------------------------------+ > > > > Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | > > > > Wantabe, Inc. |__\ +------------------------------+ > > > > jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | > > > > (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ > > > > > > > > > > > > > > > > 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 > > > > > > > > > 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 Tue Dec 14 11:44:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.omnilink.net (mail.omnilink.net [194.64.25.6]) by hub.freebsd.org (Postfix) with ESMTP id 7111614C31 for ; Tue, 14 Dec 1999 11:44:10 -0800 (PST) (envelope-from ob@omnilink.net) Received: from ntsrv2 (my.jav.net [212.255.14.194]) by mail.omnilink.net (8.9.3/8.9.3) with SMTP id UAA04352; Tue, 14 Dec 1999 20:45:00 +0100 (CET) (envelope-from ob@omnilink.net) Message-ID: <008b01bf466b$71d1c0c0$c20effd4@jav.net> From: "Oliver Blasnik" To: "Jeffrey J. Libman" , References: Subject: Re: mountd and rpc.statd won't run Date: Tue, 14 Dec 1999 20:43:06 +0100 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2014.211 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi Jeff, > a number of virtual web sites and ip's aliased to lo0 to it, and now > rpc.statd and mountd will not run. I've had a similar problem last week ... > i don't know if the failure is related to the ip changes. > mountd[pidno]: can't register mount Check out ifconfig for lo0. Is localhost 127.0.0.1 bound to it? No? Then: edit rc.conf, change: network_interfaces="ed0 lo0" (or whatever card you have). If this doesn't help, go the hard way an add ifconfig_lo0="inet 127.0.0.1 netmask 255.0.0.0" as a primary adress. I did both to get shure and rebooted. Did work very well after that. > cheers, > jeff Cu, Oliver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 11:49:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id F1C5914CA4 for ; Tue, 14 Dec 1999 11:49:32 -0800 (PST) (envelope-from mw@theatre.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id UAA07938; Tue, 14 Dec 1999 20:49:28 +0100 (CET) Received: by theatre.sax.de (8.9.3/8.6.12-s1) id UAA34356; Tue, 14 Dec 1999 20:40:40 +0100 (CET) Date: Tue, 14 Dec 1999 20:40:40 +0100 From: Martin Welk To: "Michael R. Wayne" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: What all does installworld fail to install? Message-ID: <19991214204039.I13327@theatre.sax.de> References: <199912141653.LAA10196@manor.msen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912141653.LAA10196@manor.msen.com>; from wayne@staff.msen.com on Tue, Dec 14, 1999 at 11:53:08AM -0500 Organization: Private UUCP/Usenet site. X-Phone: +49 3731 458867 X-Operating-System: FreeBSD http://www.freebsd.org/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 11:53:08AM -0500, Michael R. Wayne wrote: > 3.4RC, using NFS and a box which has already had > "make buildworld ; make installworld" > done on it. What am I missing: You need to do ``make reinstall'' instead of ``make installworld''. Check for the pathnames, if you have /usr/src symlinked somewhere, you need to create that similar on the boxes where you do the NFS mounts. The pathnames are stored in /usr/obj extended to the original names, not as the symlinks. Regards, Martin -- /| /| | /| / ,,You know, there's a lot of opportunities, / |/ | artin |/ |/ elk if you're knowing to take them, you know, there's a lot of opportunities, Freiberg/Saxony, Germany if there aren't you can make them, mw@sax.de / mw@theatre.sax.de make or break them!'' (Tennant/Lowe) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 11:51:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 507A514C31; Tue, 14 Dec 1999 11:51:18 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA14283; Tue, 14 Dec 1999 19:55:21 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01242; Tue, 14 Dec 1999 20:11:21 +0100 (CET) (envelope-from wilko) Date: Tue, 14 Dec 1999 20:11:21 +0100 From: Wilko Bulte To: Mike Smith Cc: Rahul Dhesi , freebsd-stable@FreeBSD.ORG Subject: Re: how to rewrite the data field replaceable unit? Message-ID: <19991214201120.F1003@yedi.iaf.nl> References: <19991214120034.10BC021C@waltz.rahul.net> <199912141757.JAA03135@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912141757.JAA03135@mass.cdrom.com>; from msmith@FreeBSD.ORG on Tue, Dec 14, 1999 at 09:57:11AM -0800 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 14, 1999 at 09:57:11AM -0800, Mike Smith wrote: > > Mike Smith writes: > > > > >> (da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data field replaceable unit: 20 sks:80,a0 > > ... > > > > >That's two things, 'data' and 'field replaceable unit'. The FRU code > > >tells you which part of the drive is failing - in this case the vendor > > >code for the broken bit is '20'. > > > > Thanks. > > > > A suggestion to the Device Driver Gods: Please make error messages > > understandable to the rest of us. > > That's kinda difficult, actually. Error messages need to be accurate and > understandable to people that understand what's really going on. It's > not the job of an error message to explain how the hardware works. To add to that: FRU codes are vendor/product unique. So in this case you cannot be more specific from the driver's point of view. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 12:56:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id EBB2914E6C for ; Tue, 14 Dec 1999 12:56:42 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id VAA01304 for freebsd-stable@FreeBSD.ORG; Tue, 14 Dec 1999 21:56:14 +0100 (CET) (envelope-from olli) Date: Tue, 14 Dec 1999 21:56:14 +0100 (CET) From: Oliver Fromme Message-Id: <199912142056.VAA01304@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: how to rewrite the data field replaceable unit? Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote in list.freebsd-stable: > > A suggestion to the Device Driver Gods: Please make error messages > > understandable to the rest of us. > > That's kinda difficult, actually. Error messages need to be accurate and > understandable to people that understand what's really going on. It's > not the job of an error message to explain how the hardware works. Is it really that difficult to (at least) insert a comma or something before "field replaceable unit"? I got bitten by that unrecognizable error message once, too... Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 13:25:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 7DAE115259 for ; Tue, 14 Dec 1999 13:25:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01774 for ; Tue, 14 Dec 1999 13:28:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912142128.NAA01774@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: stable@freebsd.org Subject: Bugfixed AMI MegaRAID driver for -stable available Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Dec 1999 13:28:28 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Due to a programming error, the previous release of the AMI MegaRAID driver for FreeBSD 3.x would not work with Enterprise 418 and 428 series controllers. This has been corrected, and the new driver is available at http://www.freebsd.org/~msmith/RAID/ami/amr-stable-991214.tar.gz There are no other changes in this release. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 17:10:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id 99F7E152F8 for ; Tue, 14 Dec 1999 17:10:28 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id BAA18271; Wed, 15 Dec 1999 01:10:57 GMT (envelope-from arg@arg1.demon.co.uk) Date: Wed, 15 Dec 1999 01:10:52 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Kazutaka YOKOTA Cc: stable@freebsd.org Subject: Re: Problem with psm0 In-Reply-To: <199912140819.RAA06349@zodiac.mech.utsunomiya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-439363126-945220252=:18262" 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-439363126-945220252=:18262 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 14 Dec 1999, Kazutaka YOKOTA wrote: > > >I have two systems, both now running 3.4-RC (built from the most recent > >source I had via CTM a couple of hours ago). I also have two very similar > >mice. However: > [...] > >system1 is a Gigabyte 71X Athlon motherboard (AMD chipset) > >system2 is a PC-Chips socket-7 motherboard (SiS chipset) > > > >mouse1 is a MouseSystems M5 PS/2 optical mouse (model 403011-001) > >mouse2 is a MouseSystems type 2544 PS/2 optical mouse (model 404273-001) > >Both have been in use for some time on FreeBSD 2.2 systems (the main > >difference between mouse1 and mouse2 is that mouse1 cost about 4 times as > >much and has slightly better buttons!). > > When you were running FreeBSD 2.2, were you using the above > motherboards? No, system 1 is brand-new (when upgrading from 2.2 to 3.x I replaced the whole machine, just keeping the kbd/mouse/screen). I just tried booting a 2.2.8-RELEASE CD in the problem machine, and it didn't detect psm0 either, so this is a red herring. I then went looking for a hardware problem. I thought I was onto something when I measured the +5V on-load voltage at the PS/2 keyboard/mouse ports as only 4.71V: this motherboard seems to have a high-resistance fuse. However, soldering a wire to bypass the fuse gave me a solid 5.01V but no change in the behaviour. I suppose I ought to try installing Windows and see if the mouse works there, though that will take some time as this is currently an all-SCSI machine. > >System1/Mouse1: > [...] > >psm0: current command byte:0047 > >kbdc: TEST_AUX_PORT status:0000 > >kbdc: RESET_AUX return code:00fa > >kbdc: RESET_AUX status:ffffffff > >kbdc: DIAGNOSE status:0055 > >kbdc: TEST_KBD_PORT status:0000 > >psm0: failed to reset the aux device. > >psm0 not found > > Do you by any chance use any console switch? We may have a timing > problem here. Would you send us the full dmesg output? I do not have a switch: the mouse is plugged directly into the motherboard mouse port. Full dmesg output is attached. > In the meantime, try adding the following options in your kernel > configuration file. > > options KBDIO_MAXWAIT 10 > > The default value is 5. Increase the value if your mouse is not still > recognized. I assume you mean "options KBD_MAXWAIT=10" ? I tried this, but it had no effect. I also tried other values, including: options KBD_MAXWAIT=10 options KBD_RESETDELAY=1000 options KBD_MAXRETRY=10 but again no obvious effect (other than a noticeable delay at that point in the boot sequence). --0-439363126-945220252=:18262 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="dmesg.nogood3" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="dmesg.nogood3" Q29weXJpZ2h0IChjKSAxOTkyLTE5OTkgRnJlZUJTRCBJbmMuDQpDb3B5cmln aHQgKGMpIDE5ODIsIDE5ODYsIDE5ODksIDE5OTEsIDE5OTMNCglUaGUgUmVn ZW50cyBvZiB0aGUgVW5pdmVyc2l0eSBvZiBDYWxpZm9ybmlhLiBBbGwgcmln aHRzIHJlc2VydmVkLg0KRnJlZUJTRCAzLjQtUkMgIzc6IFdlZCBEZWMgMTUg MDA6NDY6NTcgR01UIDE5OTkNCiAgICBhcmdAcm9ja2V0LmFyZy5zai5jby51 azovdXNyL3NyYy9zeXMvY29tcGlsZS9ST0NLRVQNCkNhbGlicmF0aW5nIGNs b2NrKHMpIC4uLiBUU0MgY2xvY2s6IDU5ODg5NjQ0NCBIeiwgaTgyNTQgY2xv Y2s6IDExOTMzMDEgSHoNCkNMS19VU0VfSTgyNTRfQ0FMSUJSQVRJT04gbm90 IHNwZWNpZmllZCAtIHVzaW5nIGRlZmF1bHQgZnJlcXVlbmN5DQpUaW1lY291 bnRlciAiaTgyNTQiICBmcmVxdWVuY3kgMTE5MzE4MiBIeg0KQ0xLX1VTRV9U U0NfQ0FMSUJSQVRJT04gbm90IHNwZWNpZmllZCAtIHVzaW5nIG9sZCBjYWxp YnJhdGlvbiBtZXRob2QNCkNQVTogQU1ELUs3KHRtKSBQcm9jZXNzb3IgKDU5 OC44NC1NSHogNjg2LWNsYXNzIENQVSkNCiAgT3JpZ2luID0gIkF1dGhlbnRp Y0FNRCIgIElkID0gMHg2MTIgIFN0ZXBwaW5nID0gMg0KICBGZWF0dXJlcz0w eDgxZjlmZjxGUFUsVk1FLERFLFBTRSxUU0MsTVNSLFBBRSxNQ0UsQ1g4LFNF UCxNVFJSLFBHRSxNQ0EsQ01PVixQQVQsTU1YPg0KICBBTUQgRmVhdHVyZXM9 MHhjMDQwMDAwMDw8YjIyPiw8YjMwPiwzRE5vdyE+DQpEYXRhIFRMQjogMjQg ZW50cmllcywgZnVsbHkgYXNzb2NpYXRpdmUNCkluc3RydWN0aW9uIFRMQjog MTYgZW50cmllcywgZnVsbHkgYXNzb2NpYXRpdmUNCkwxIGRhdGEgY2FjaGU6 IDY0IGtieXRlcywgNjQgYnl0ZXMvbGluZSwgMSBsaW5lcy90YWcsIDItd2F5 IGFzc29jaWF0aXZlDQpMMSBpbnN0cnVjdGlvbiBjYWNoZTogNjQga2J5dGVz LCA2NCBieXRlcy9saW5lLCAxIGxpbmVzL3RhZywgMi13YXkgYXNzb2NpYXRp dmUNCkwyIGludGVybmFsIGNhY2hlOiA1MTIga2J5dGVzLCA2NCBieXRlcy9s aW5lLCAxIGxpbmVzL3RhZywgMi13YXkgYXNzb2NpYXRpdmUNCnJlYWwgbWVt b3J5ICA9IDEzNDIxNzcyOCAoMTMxMDcySyBieXRlcykNClBoeXNpY2FsIG1l bW9yeSBjaHVuayhzKToNCjB4MDAwMDEwMDAgLSAweDAwMDllZmZmLCA2NDcx NjggYnl0ZXMgKDE1OCBwYWdlcykNCjB4MDAyZTgwMDAgLSAweDA3ZmY1ZmZm LCAxMzExMjkzNDQgYnl0ZXMgKDMyMDE0IHBhZ2VzKQ0KYXZhaWwgbWVtb3J5 ID0gMTI3NTE2NjcyICgxMjQ1MjhLIGJ5dGVzKQ0KRm91bmQgQklPUzMyIFNl cnZpY2UgRGlyZWN0b3J5IGhlYWRlciBhdCAweGMwMGZhZmMwDQpFbnRyeSA9 IDB4ZmI0MzAgKDB4YzAwZmI0MzApICBSZXYgPSAwICBMZW4gPSAxDQpQQ0kg QklPUyBlbnRyeSBhdCAweGI0NjANClNNSUJJT1MgaGVhZGVyIGF0IDB4YzAw ZjUwNDANClZlcnNpb24gMi4xDQpUYWJsZSBhdCAweGYwODAwLCAzOSBlbnRy aWVzLCA5NTggYnl0ZXMsIGxhcmdlc3QgZW50cnkgNzQgYnl0ZXMNCkRNSSBo ZWFkZXIgYXQgMHhjMDBmNTA1MA0KVmVyc2lvbiAyLjENClRhYmxlIGF0IDB4 ZjA4MDAsIDM5IGVudHJpZXMsIDk1OCBieXRlcw0KT3RoZXIgQklPUyBzaWdu YXR1cmVzIGZvdW5kOg0KQUNQSTogMDAwMDAwMDANCiRQblA6IDAwMGZjMGEw DQpQcmVsb2FkZWQgZWxmIGtlcm5lbCAia2VybmVsIiBhdCAweGMwMmNmMDAw Lg0KVkVTQTogaW5mb3JtYXRpb24gYmxvY2sNCjU2IDQ1IDUzIDQxIDAwIDAy IDAwIDAxIDAwIDAxIDAwIDAwIDAwIDAwIDIyIDAwIA0KMDAgMDEgODAgMDAg MDAgMDEgMGIgMDEgMDAgMDEgMjEgMDEgMDAgMDEgMmEgMDEgDQowMCAwMSAw MCAwMSAwMSAwMSAxMCAwMSAxMSAwMSAxMiAwMSAwMyAwMSAxMyAwMSANCjE0 IDAxIDE1IDAxIDA1IDAxIDE2IDAxIDE3IDAxIDE4IDAxIDA3IDAxIDE5IDAx IA0KVkVTQTogMyBtb2RlKHMpIGZvdW5kDQpQZW50aXVtIFBybyBNVFJSIHN1 cHBvcnQgZW5hYmxlZA0KTWF0aCBlbXVsYXRvciBwcmVzZW50DQpwY2lfb3Bl bigxKToJbW9kZSAxIGFkZHIgcG9ydCAoMHgwY2Y4KSBpcyAweDgwMDAzODQw DQpwY2lfb3BlbigxYSk6CW1vZGUxcmVzPTB4ODAwMDAwMDAgKDB4ODAwMDAw MDApDQpwY2lfY2ZnY2hlY2s6CWRldmljZSAwIFtjbGFzcz0wNjAwMDBdIFto ZHI9ODBdIGlzIHRoZXJlIChpZD03MDA2MTAyMikNClByb2JpbmcgZm9yIGRl dmljZXMgb24gUENJIGJ1cyAwOg0KZm91bmQtPgl2ZW5kb3I9MHgxMDIyLCBk ZXY9MHg3MDA2LCByZXZpZD0weDIzDQoJY2xhc3M9MDYtMDAtMDAsIGhkcnR5 cGU9MHgwMCwgbWZkZXY9MQ0KCXN1Ym9yZGluYXRlYnVzPTAgCXNlY29uZGFy eWJ1cz0wDQoJbWFwWzBdOiB0eXBlIDMsIHJhbmdlIDMyLCBiYXNlIGQ4MDAw MDAwLCBzaXplIDI2DQoJbWFwWzFdOiB0eXBlIDMsIHJhbmdlIDMyLCBiYXNl IGUzMTAxMDAwLCBzaXplIDEyDQoJbWFwWzJdOiB0eXBlIDQsIHJhbmdlIDMy LCBiYXNlIDAwMDBlMDAwLCBzaXplICAyDQpjaGlwMDogPEhvc3QgdG8gUENJ IGJyaWRnZSAodmVuZG9yPTEwMjIgZGV2aWNlPTcwMDYpPiByZXYgMHgyMyBv biBwY2kwLjAuMA0KZm91bmQtPgl2ZW5kb3I9MHgxMDIyLCBkZXY9MHg3MDA3 LCByZXZpZD0weDAxDQoJY2xhc3M9MDYtMDQtMDAsIGhkcnR5cGU9MHgwMSwg bWZkZXY9MQ0KCXN1Ym9yZGluYXRlYnVzPTEgCXNlY29uZGFyeWJ1cz0xDQpj aGlwMTogPFBDSSB0byBQQ0kgYnJpZGdlICh2ZW5kb3I9MTAyMiBkZXZpY2U9 NzAwNyk+IHJldiAweDAxIG9uIHBjaTAuMS4wDQpmb3VuZC0+CXZlbmRvcj0w eDEwMjIsIGRldj0weDc0MDgsIHJldmlkPTB4MDENCgljbGFzcz0wNi0wMS0w MCwgaGRydHlwZT0weDAwLCBtZmRldj0xDQoJc3Vib3JkaW5hdGVidXM9MCAJ c2Vjb25kYXJ5YnVzPTANCmNoaXAyOiA8UENJIHRvIElTQSBicmlkZ2UgKHZl bmRvcj0xMDIyIGRldmljZT03NDA4KT4gcmV2IDB4MDEgb24gcGNpMC43LjAN CmZvdW5kLT4JdmVuZG9yPTB4MTAyMiwgZGV2PTB4NzQwOSwgcmV2aWQ9MHgw Mw0KCWNsYXNzPTAxLTAxLThhLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTANCglz dWJvcmRpbmF0ZWJ1cz0wIAlzZWNvbmRhcnlidXM9MA0KCW1hcFswXTogdHlw ZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAwZjAwMCwgc2l6ZSAgNA0KZm91bmQt Pgl2ZW5kb3I9MHgxMDIyLCBkZXY9MHg3NDBiLCByZXZpZD0weDAzDQoJY2xh c3M9MDYtODAtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MA0KCXN1Ym9yZGlu YXRlYnVzPTAgCXNlY29uZGFyeWJ1cz0wDQpjaGlwMzogPFBDSSB0byAweDgw IGJyaWRnZSAodmVuZG9yPTEwMjIgZGV2aWNlPTc0MGIpPiByZXYgMHgwMyBv biBwY2kwLjcuMw0KZm91bmQtPgl2ZW5kb3I9MHgxMDIyLCBkZXY9MHg3NDBj LCByZXZpZD0weDA2DQoJY2xhc3M9MGMtMDMtMTAsIGhkcnR5cGU9MHgwMCwg bWZkZXY9MA0KCXN1Ym9yZGluYXRlYnVzPTAgCXNlY29uZGFyeWJ1cz0wDQoJ aW50cGluPWQsIGlycT0xMQ0KCW1hcFswXTogdHlwZSAxLCByYW5nZSAzMiwg YmFzZSBlMzEwMjAwMCwgc2l6ZSAxMg0KZm91bmQtPgl2ZW5kb3I9MHgxMDll LCBkZXY9MHgwMzZlLCByZXZpZD0weDAyDQoJY2xhc3M9MDQtMDAtMDAsIGhk cnR5cGU9MHgwMCwgbWZkZXY9MQ0KCXN1Ym9yZGluYXRlYnVzPTAgCXNlY29u ZGFyeWJ1cz0wDQoJaW50cGluPWEsIGlycT05DQoJbWFwWzBdOiB0eXBlIDMs IHJhbmdlIDMyLCBiYXNlIGUzMTA1MDAwLCBzaXplIDEyDQpia3RyMDogPEJy b29rVHJlZSA4Nzg+IHJldiAweDAyIGludCBhIGlycSA5IG9uIHBjaTAuOC4w DQpidGkyYzA6IDxidDg0OCBIYXJkL1NvZnQgSTJDIGNvbnRyb2xsZXI+DQpp aWNiYjA6IDxJMkMgZ2VuZXJpYyBiaXQtYmFuZ2luZyBkcml2ZXI+IG9uIGJ0 aTJjMA0KaWljYnVzMDogPFBoaWxpcHMgSTJDIGJ1cz4gb24gaWljYmIwIG1h c3Rlci1vbmx5DQppaWNidXM6IGlpYyBkZXZjbGFzcyBub3QgZm91bmQNCnNt YnVzMDogPFN5c3RlbSBNYW5hZ2VtZW50IEJ1cz4gb24gYnRpMmMwDQpzbWJ1 czogc21iIGRldmNsYXNzIG5vdCBmb3VuZA0KYnJvb2t0cmVlMDogUENJIGJ1 cyBsYXRlbmN5IGlzIDMyLg0KYmt0cjA6IGJ1ZmZlciBzaXplIDM1NTUzMjgs IGFkZHIgMHg1MDAwMDAwDQpia3RyOiBHUElPIGlzIDB4MDBmZmZmZGINCnN1 YnN5dGVtIDB4MDA3MCAweDEzZWINCmJrdHIwOiBIYXVwcGF1Z2UgTW9kZWwg NjEzMjQgRDIyOQ0KYmt0cjA6IERldGVjdGVkIGEgTVNQMzQxNUQtQTIgYXQg MHg4MA0KSGF1cHBhdWdlIFdpbkNhc3QvVFYsIFBoaWxpcHMgUEFMIEkgdHVu ZXIsIG1zcDM0MDBjIHN0ZXJlbywgcmVtb3RlIGNvbnRyb2wuDQpmb3VuZC0+ CXZlbmRvcj0weDEwOWUsIGRldj0weDA4NzgsIHJldmlkPTB4MDINCgljbGFz cz0wNC04MC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0xDQoJc3Vib3JkaW5h dGVidXM9MCAJc2Vjb25kYXJ5YnVzPTANCglpbnRwaW49YSwgaXJxPTkNCglt YXBbMF06IHR5cGUgMywgcmFuZ2UgMzIsIGJhc2UgZTMxMDgwMDAsIHNpemUg MTINCmZvdW5kLT4JdmVuZG9yPTB4ODA4NiwgZGV2PTB4MTIyOSwgcmV2aWQ9 MHgwOA0KCWNsYXNzPTAyLTAwLTAwLCBoZHJ0eXBlPTB4MDAsIG1mZGV2PTAN CglzdWJvcmRpbmF0ZWJ1cz0wIAlzZWNvbmRhcnlidXM9MA0KCWludHBpbj1h LCBpcnE9NQ0KCW1hcFswXTogdHlwZSAxLCByYW5nZSAzMiwgYmFzZSBlMzEw MDAwMCwgc2l6ZSAxMg0KCW1hcFsxXTogdHlwZSA0LCByYW5nZSAzMiwgYmFz ZSAwMDAwZTQwMCwgc2l6ZSAgNg0KCW1hcFsyXTogdHlwZSAxLCByYW5nZSAz MiwgYmFzZSBlMzAwMDAwMCwgc2l6ZSAyMA0KZnhwMDogPEludGVsIEV0aGVy RXhwcmVzcyBQcm8gMTAvMTAwQiBFdGhlcm5ldD4gcmV2IDB4MDggaW50IGEg aXJxIDUgb24gcGNpMC45LjANCmZ4cDA6IEV0aGVybmV0IGFkZHJlc3MgMDA6 OTA6Mjc6YzE6ZTE6MzQNCmJwZjogZnhwMCBhdHRhY2hlZA0KZm91bmQtPgl2 ZW5kb3I9MHgxMDAwLCBkZXY9MHgwMDBjLCByZXZpZD0weDAxDQoJY2xhc3M9 MDEtMDAtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MA0KCXN1Ym9yZGluYXRl YnVzPTAgCXNlY29uZGFyeWJ1cz0wDQoJaW50cGluPWEsIGlycT0xMA0KCW1h cFswXTogdHlwZSA0LCByYW5nZSAzMiwgYmFzZSAwMDAwZTgwMCwgc2l6ZSAg OA0KCW1hcFsxXTogdHlwZSAxLCByYW5nZSAzMiwgYmFzZSBlMzEwMzAwMCwg c2l6ZSAgOA0KCW1hcFsyXTogdHlwZSAxLCByYW5nZSAzMiwgYmFzZSBlMzEw NDAwMCwgc2l6ZSAxMg0KbmNyMDogPG5jciA1M2M4OTUgZmFzdDQwIHdpZGUg c2NzaT4gcmV2IDB4MDEgaW50IGEgaXJxIDEwIG9uIHBjaTAuMTAuMA0KbmNy MDogbWluc3luYz0xMCwgbWF4c3luYz0xMzcsIG1heG9mZnM9MzEsIDEyOCBk d29yZHMgYnVyc3QsIGxhcmdlIGRtYSBmaWZvDQpuY3IwOiBzaW5nbGUtZW5k ZWQsIG9wZW4gZHJhaW4gSVJRIGRyaXZlciwgdXNpbmcgb24tY2hpcCBTUkFN DQpmb3VuZC0+CXZlbmRvcj0weDEwMDAsIGRldj0weDAwMGYsIHJldmlkPTB4 MDMNCgljbGFzcz0wMS0wMC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0wDQoJ c3Vib3JkaW5hdGVidXM9MCAJc2Vjb25kYXJ5YnVzPTANCglpbnRwaW49YSwg aXJxPTExDQoJbWFwWzBdOiB0eXBlIDQsIHJhbmdlIDMyLCBiYXNlIDAwMDBl YzAwLCBzaXplICA4DQoJbWFwWzFdOiB0eXBlIDEsIHJhbmdlIDMyLCBiYXNl IGUzMTA2MDAwLCBzaXplICA4DQoJbWFwWzJdOiB0eXBlIDEsIHJhbmdlIDMy LCBiYXNlIGUzMTA3MDAwLCBzaXplIDEyDQpuY3IxOiA8bmNyIDUzYzg3NSBm YXN0MjAgd2lkZSBzY3NpPiByZXYgMHgwMyBpbnQgYSBpcnEgMTEgb24gcGNp MC4xMS4wDQpuY3IxOiBtaW5zeW5jPTEyLCBtYXhzeW5jPTEzNywgbWF4b2Zm cz0xNiwgMTI4IGR3b3JkcyBidXJzdCwgbGFyZ2UgZG1hIGZpZm8NCm5jcjE6 IHNpbmdsZS1lbmRlZCwgb3BlbiBkcmFpbiBJUlEgZHJpdmVyLCB1c2luZyBv bi1jaGlwIFNSQU0NClByb2JpbmcgZm9yIGRldmljZXMgb24gUENJIGJ1cyAx Og0KZm91bmQtPgl2ZW5kb3I9MHgxMDAyLCBkZXY9MHg0NzQyLCByZXZpZD0w eDVjDQoJY2xhc3M9MDMtMDAtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MA0K CXN1Ym9yZGluYXRlYnVzPTAgCXNlY29uZGFyeWJ1cz0wDQoJaW50cGluPWEs IGlycT01DQoJbWFwWzBdOiB0eXBlIDEsIHJhbmdlIDMyLCBiYXNlIGRjMDAw MDAwLCBzaXplIDI0DQoJbWFwWzFdOiB0eXBlIDQsIHJhbmdlIDMyLCBiYXNl IDAwMDBkMDAwLCBzaXplICA4DQoJbWFwWzJdOiB0eXBlIDEsIHJhbmdlIDMy LCBiYXNlIGRlMDAwMDAwLCBzaXplIDEyDQp2Z2EwOiA8QVRJIG1vZGVsIDQ3 NDIgZ3JhcGhpY3MgYWNjZWxlcmF0b3I+IHJldiAweDVjIGludCBhIGlycSA1 IG9uIHBjaTEuNS4wDQpJbml0aWFsaXppbmcgUG5QIG92ZXJyaWRlIHRhYmxl DQpQcm9iaW5nIGZvciBQblAgZGV2aWNlczoNClRyeWluZyBSZWFkX1BvcnQg YXQgMjAzDQpUcnlpbmcgUmVhZF9Qb3J0IGF0IDI0Mw0KVHJ5aW5nIFJlYWRf UG9ydCBhdCAyODMNClRyeWluZyBSZWFkX1BvcnQgYXQgMmMzDQpUcnlpbmcg UmVhZF9Qb3J0IGF0IDMwMw0KVHJ5aW5nIFJlYWRfUG9ydCBhdCAzNDMNClRy eWluZyBSZWFkX1BvcnQgYXQgMzgzDQpUcnlpbmcgUmVhZF9Qb3J0IGF0IDNj Mw0KTm8gUGx1Zy1uLVBsYXkgZGV2aWNlcyB3ZXJlIGZvdW5kDQpQcm9iaW5n IGZvciBkZXZpY2VzIG9uIHRoZSBJU0EgYnVzOg0KYXRrYmQ6IHRoZSBjdXJy ZW50IGtiZCBjb250cm9sbGVyIGNvbW1hbmQgYnl0ZSAwMDQ3DQphdGtiZDog a2V5Ym9hcmQgSUQgMHg0MWFiICgyKQ0Ka2JkYzogUkVTRVRfS0JEIHJldHVy biBjb2RlOjAwZmENCmtiZGM6IFJFU0VUX0tCRCBzdGF0dXM6MDBhYQ0Kc2Mw IG9uIGlzYQ0Kc2MwOiBmYjAga2JkMA0Kc2MwOiBWR0EgY29sb3IgPDE2IHZp cnR1YWwgY29uc29sZXMsIGZsYWdzPTB4MD4NCmF0a2JkYzAgYXQgMHg2MC0w eDZmIG9uIG1vdGhlcmJvYXJkDQphdGtiZDAgaXJxIDEgb24gaXNhDQprYmQw OiBhdGtiZDAsIEFUIDEwMS8xMDIgKDIpLCBjb25maWc6MHgwLCBmbGFnczow eDNkMDAwMA0KcHNtMDogY3VycmVudCBjb21tYW5kIGJ5dGU6MDA0Nw0Ka2Jk YzogVEVTVF9BVVhfUE9SVCBzdGF0dXM6MDAwMA0Ka2JkYzogUkVTRVRfQVVY IHJldHVybiBjb2RlOjAwZmENCmtiZGM6IFJFU0VUX0FVWCBzdGF0dXM6ZmZm ZmZmZmYNCmtiZGM6IERJQUdOT1NFIHN0YXR1czowMDU1DQprYmRjOiBURVNU X0tCRF9QT1JUIHN0YXR1czowMDAwDQpwc20wOiBmYWlsZWQgdG8gcmVzZXQg dGhlIGF1eCBkZXZpY2UuDQpwc20wIG5vdCBmb3VuZA0Kc2lvMDogaXJxIG1h cHM6IDB4MTAwMSAweDEwMTEgMHgxMDAxIDB4MTAwMQ0Kc2lvMCBhdCAweDNm OC0weDNmZiBpcnEgNCBmbGFncyAweDEwIG9uIGlzYQ0Kc2lvMDogdHlwZSAx NjU1MEENCnNpbzE6IGlycSBtYXBzOiAweDEwMDEgMHgxMDA5IDB4MTAwMSAw eDEwMDENCnNpbzEgYXQgMHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhDQpzaW8x OiB0eXBlIDE2NTUwQQ0KbXNzX3Byb2JlOiBubyBhZGRyZXNzIHN1cHBsaWVk LCB0cnkgZGVmYXVsdCAweDUzMA0KbXNzX2RldGVjdCBlcnJvciwgYnVzeSBz dGlsbCBzZXQgKDB4ZmYpDQpzYl9wcm9iZTogbm8gYWRkcmVzcyBzdXBwbGll ZCwgdHJ5IGRlZmF1bHRzICgweDIyMCwweDI0MCkNCnBjbTAgbm90IGZvdW5k DQpmZGMwIGF0IDB4M2YwLTB4M2Y3IGlycSA2IGRycSAyIG9uIGlzYQ0KZmRj MDogRklGTyBlbmFibGVkLCA4IGJ5dGVzIHRocmVzaG9sZA0KZmQwOiAxLjQ0 TUIgMy41aW4NCnBwYzogcGFyYWxsZWwgcG9ydCBmb3VuZCBhdCAweDM3OA0K cHBjOiBjaGlwc2V0IGZvcmNlZCB0byBnZW5lcmljDQpwcGMwOiBFQ1AgU1BQ IEVDUCtFUFAgU1BQDQpwcGMwIGF0IDB4Mzc4IGlycSA3IGZsYWdzIDB4NDAg b24gaXNhDQpwcGMwOiBTTUMtbGlrZSBjaGlwc2V0IChFQ1AvRVBQL1BTMi9O SUJCTEUpIGluIENPTVBBVElCTEUgbW9kZQ0KcHBjMDogRklGTyB3aXRoIDE2 LzE2LzE2IGJ5dGVzIHRocmVzaG9sZA0KbHB0MDogPGdlbmVyaWMgcHJpbnRl cj4gb24gcHBidXMgMA0KbHB0MDogSW50ZXJydXB0LWRyaXZlbiBwb3J0DQpw cGkwOiA8Z2VuZXJpYyBwYXJhbGxlbCBpL28+IG9uIHBwYnVzIDANCnBsaXA6 IGlycSA3DQpwbGlwMDogPFBMSVAgbmV0d29yayBpbnRlcmZhY2U+IG9uIHBw YnVzIDANCmJwZjogbHAwIGF0dGFjaGVkDQp2Z2EwIGF0IDB4M2IwLTB4M2Rm IG1hZGRyIDB4YTAwMDAgbXNpemUgMTMxMDcyIG9uIGlzYQ0KZmIwOiB2Z2Ew LCB2Z2EsIHR5cGU6VkdBICg1KSwgZmxhZ3M6MHg3MDBmZg0KZmIwOiBwb3J0 OjB4M2IwLTB4M2RmLCBjcnRjOjB4M2Q0LCBtZW06MHhhMDAwMCAweDIwMDAw DQpmYjA6IGluaXQgbW9kZToyNCwgYmlvcyBtb2RlOjMsIGN1cnJlbnQgbW9k ZToyNA0KZmIwOiB3aW5kb3c6MHhjMDBiODAwMCBzaXplOjMyayBncmFuOjMy aywgYnVmOjB4MCBzaXplOjBrDQpWR0EgcGFyYW1ldGVycyB1cG9uIHBvd2Vy LXVwDQo1MCAxOCAxMCAwMCAwMCAwMCAwMyAwMCAwMiA2NyA1ZiA0ZiA1MCA4 MiA1NSA4MSANCmJmIDFmIDAwIDRmIDBlIDBmIDAwIDAwIDA3IDgwIDljIDhl IDhmIDI4IDFmIDk2IA0KYjkgYTMgZmYgMDAgMDEgMDIgMDMgMDQgMDUgMTQg MDcgMzggMzkgM2EgM2IgM2MgDQozZCAzZSAzZiAwYyAwMCAwZiAwOCAwMCAw MCAwMCAwMCAwMCAxMCAwZSAwMCBmZiANClZHQSBwYXJhbWV0ZXJzIGluIEJJ T1MgZm9yIG1vZGUgMjQNCjUwIDE4IDEwIDAwIDEwIDAwIDAzIDAwIDAyIDY3 IDVmIDRmIDUwIDgyIDU1IDgxIA0KYmYgMWYgMDAgNGYgMGQgMGUgMDAgMDAg MDAgMDAgOWMgOGUgOGYgMjggMWYgOTYgDQpiOSBhMyBmZiAwMCAwMSAwMiAw MyAwNCAwNSAxNCAwNyAzOCAzOSAzYSAzYiAzYyANCjNkIDNlIDNmIDBjIDAw IDBmIDA4IDAwIDAwIDAwIDAwIDAwIDEwIDBlIDAwIGZmIA0KRUdBL1ZHQSBw YXJhbWV0ZXJzIHRvIGJlIHVzZWQgZm9yIG1vZGUgMjQNCjUwIDE4IDEwIDAw IDEwIDAwIDAzIDAwIDAyIDY3IDVmIDRmIDUwIDgyIDU1IDgxIA0KYmYgMWYg MDAgNGYgMGQgMGUgMDAgMDAgMDAgMDAgOWMgOGUgOGYgMjggMWYgOTYgDQpi OSBhMyBmZiAwMCAwMSAwMiAwMyAwNCAwNSAxNCAwNyAzOCAzOSAzYSAzYiAz YyANCjNkIDNlIDNmIDBjIDAwIDBmIDA4IDAwIDAwIDAwIDAwIDAwIDEwIDBl IDAwIGZmIA0KVkVTQTogdjIuMCwgODE5MmsgbWVtb3J5LCBmbGFnczoweDAs IG1vZGUgdGFibGU6MHhjMDI3ZWM0MiAoMTAwMDAyMikNClZFU0E6IEFUSSBN QUNINjQNClZFU0E6IEFUSSBUZWNobm9sb2dpZXMgSW5jLg0KVkVTQTogTUFD SDY0R1QNClZFU0E6IDAxLjAwDQpucHgwIG9uIG1vdGhlcmJvYXJkDQpucHgw OiBJTlQgMTYgaW50ZXJmYWNlDQphcG0wIGZsYWdzIDB4MzEgb24gaXNhDQph cG06IGZvdW5kIEFQTSBCSU9TIHZlcnNpb24gMS4yDQppbWFza3M6IGJpbyBj MDA4MDA0MCwgdHR5IGMwMDcwMmJhLCBuZXQgYzAwNzAyYmENCkJJT1MgR2Vv bWV0cmllczoNCiAwOjAzZmZmZTNmIDAuLjEwMjM9MTAyNCBjeWxpbmRlcnMs IDAuLjI1ND0yNTUgaGVhZHMsIDEuLjYzPTYzIHNlY3RvcnMNCiAwIGFjY291 bnRlZCBmb3INCkRldmljZSBjb25maWd1cmF0aW9uIGZpbmlzaGVkLg0KYnBm OiB0dW4wIGF0dGFjaGVkDQpicGY6IHR1bjEgYXR0YWNoZWQNCmJwZjogc2ww IGF0dGFjaGVkDQpicGY6IGxvMCBhdHRhY2hlZA0KV2FpdGluZyAxNSBzZWNv bmRzIGZvciBTQ1NJIGRldmljZXMgdG8gc2V0dGxlDQpuY3IwOiByZXN0YXJ0 IChzY3NpIHJlc2V0KS4NCm5jcjE6IHJlc3RhcnQgKHNjc2kgcmVzZXQpLg0K KHByb2JlMTg6bmNyMTowOjM6MCk6IElOUVVJUlkuIENEQjogMTIgMSA4MCAw IGZmIDAgDQoocHJvYmUxODpuY3IxOjA6MzowKTogSUxMRUdBTCBSRVFVRVNU IGFzYzoyNCwwDQoocHJvYmUxODpuY3IxOjA6MzowKTogSW52YWxpZCBmaWVs ZCBpbiBDREINCihwcm9iZTE5Om5jcjE6MDo0OjApOiBJTlFVSVJZLiBDREI6 IDEyIDEgODAgMCBmZiAwIA0KKHByb2JlMTk6bmNyMTowOjQ6MCk6IElMTEVH QUwgUkVRVUVTVCBjc2k6NDAsMCwwLDANCnNhMCBhdCBuY3IxIGJ1cyAwIHRh cmdldCA0IGx1biAwDQpzYTA6IDxXQU5HVEVLIDU1MjVFUyBTQ1NJIFJFVjcg MFc+IFJlbW92YWJsZSBTZXF1ZW50aWFsIEFjY2VzcyBTQ1NJLUNDUyBkZXZp Y2UgDQpzYTA6IDMuMzAwTUIvcyB0cmFuc2ZlcnMNCnBhc3MwIGF0IG5jcjAg YnVzIDAgdGFyZ2V0IDAgbHVuIDANCnBhc3MwOiA8SUJNIERSVlMwOVYgMDI3 MD4gRml4ZWQgRGlyZWN0IEFjY2VzcyBTQ1NJLTMgZGV2aWNlIA0KcGFzczA6 IFNlcmlhbCBOdW1iZXIgICAgICAgNjgwMjEwQjdIQQ0KcGFzczA6IDQwLjAw ME1CL3MgdHJhbnNmZXJzICgyMC4wMDBNSHosIG9mZnNldCAxNSwgMTZiaXQp LCBUYWdnZWQgUXVldWVpbmcgRW5hYmxlZA0KcGFzczEgYXQgbmNyMSBidXMg MCB0YXJnZXQgMyBsdW4gMA0KcGFzczE6IDxQTEVYVE9SIENELVJPTSBQWC0z MlRTIDEuMDM+IFJlbW92YWJsZSBDRC1ST00gU0NTSS0yIGRldmljZSANCnBh c3MxOiAyMC4wMDBNQi9zIHRyYW5zZmVycyAoMjAuMDAwTUh6LCBvZmZzZXQg MTUpDQpwYXNzMiBhdCBuY3IxIGJ1cyAwIHRhcmdldCA0IGx1biAwDQpwYXNz MjogPFdBTkdURUsgNTUyNUVTIFNDU0kgUkVWNyAwVz4gUmVtb3ZhYmxlIFNl cXVlbnRpYWwgQWNjZXNzIFNDU0ktQ0NTIGRldmljZSANCnBhc3MyOiAzLjMw ME1CL3MgdHJhbnNmZXJzDQpkYTAgYXQgbmNyMCBidXMgMCB0YXJnZXQgMCBs dW4gMA0KZGEwOiA8SUJNIERSVlMwOVYgMDI3MD4gRml4ZWQgRGlyZWN0IEFj Y2VzcyBTQ1NJLTMgZGV2aWNlIA0KZGEwOiBTZXJpYWwgTnVtYmVyICAgICAg IDY4MDIxMEI3SEENCmRhMDogNDAuMDAwTUIvcyB0cmFuc2ZlcnMgKDIwLjAw ME1Ieiwgb2Zmc2V0IDE1LCAxNmJpdCksIFRhZ2dlZCBRdWV1ZWluZyBFbmFi bGVkDQpkYTA6IDg3NTRNQiAoMTc5Mjg2OTggNTEyIGJ5dGUgc2VjdG9yczog MjU1SCA2M1MvVCAxMTE2QykNCkNvbnNpZGVyaW5nIEZGUyByb290IGYvcy4N CmNoYW5naW5nIHJvb3QgZGV2aWNlIHRvIGRhMHMxYQ0KKGNkMDpuY3IxOjA6 MzowKTogUkVBRCBDRCBSRUNPUkRFRCBDQVBBQ0lUWS4gQ0RCOiAyNSAwIDAg MCAwIDAgMCAwIDAgMCANCihjZDA6bmNyMTowOjM6MCk6IE5PVCBSRUFEWSBh c2M6M2EsMA0KKGNkMDpuY3IxOjA6MzowKTogTWVkaXVtIG5vdCBwcmVzZW50 DQpjZDAgYXQgbmNyMSBidXMgMCB0YXJnZXQgMyBsdW4gMA0KY2QwOiA8UExF WFRPUiBDRC1ST00gUFgtMzJUUyAxLjAzPiBSZW1vdmFibGUgQ0QtUk9NIFND U0ktMiBkZXZpY2UgDQpjZDA6IDIwLjAwME1CL3MgdHJhbnNmZXJzICgyMC4w MDBNSHosIG9mZnNldCAxNSkNCmNkMDogQXR0ZW1wdCB0byBxdWVyeSBkZXZp Y2Ugc2l6ZSBmYWlsZWQ6IE5PVCBSRUFEWSwgTWVkaXVtIG5vdCBwcmVzZW50 DQpkYTBzMTogdHlwZSAweGE1LCBzdGFydCA2MywgZW5kID0gMTc5Mjg1Mzks IHNpemUgMTc5Mjg0NzcgOiBPSw0Kc3RhcnRfaW5pdDogdHJ5aW5nIC9zYmlu L2luaXQNCg== --0-439363126-945220252=:18262 Content-Type: TEXT/PLAIN; charset=US-ASCII; name=ROCKET Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename=ROCKET Iw0KIyBHRU5FUklDIC0tIEdlbmVyaWMgbWFjaGluZSB3aXRoIFdEL0FIeC9O Q1IvQlR4IGZhbWlseSBkaXNrcw0KIw0KIyBGb3IgbW9yZSBpbmZvcm1hdGlv biBvbiB0aGlzIGZpbGUsIHBsZWFzZSByZWFkIHRoZSBoYW5kYm9vayBzZWN0 aW9uIG9uDQojIEtlcm5lbCBDb25maWd1cmF0aW9uIEZpbGVzOg0KIw0KIyAg ICBodHRwOi8vd3d3LmZyZWVic2Qub3JnL2hhbmRib29rL2tlcm5lbGNvbmZp Zy1jb25maWcuaHRtbA0KIw0KIyBUaGUgaGFuZGJvb2sgaXMgYWxzbyBhdmFp bGFibGUgbG9jYWxseSBpbiAvdXNyL3NoYXJlL2RvYy9oYW5kYm9vaw0KIyBp ZiB5b3UndmUgaW5zdGFsbGVkIHRoZSBkb2MgZGlzdHJpYnV0aW9uLCBvdGhl cndpc2UgYWx3YXlzIHNlZSB0aGUNCiMgRnJlZUJTRCBXb3JsZCBXaWRlIFdl YiBzZXJ2ZXIgKGh0dHA6Ly93d3cuRnJlZUJTRC5PUkcvKSBmb3IgdGhlDQoj IGxhdGVzdCBpbmZvcm1hdGlvbi4NCiMNCiMgQW4gZXhoYXVzdGl2ZSBsaXN0 IG9mIG9wdGlvbnMgYW5kIG1vcmUgZGV0YWlsZWQgZXhwbGFuYXRpb25zIG9m IHRoZQ0KIyBkZXZpY2UgbGluZXMgaXMgYWxzbyBwcmVzZW50IGluIHRoZSAu L0xJTlQgY29uZmlndXJhdGlvbiBmaWxlLiBJZiB5b3UgYXJlDQojIGluIGRv dWJ0IGFzIHRvIHRoZSBwdXJwb3NlIG9yIG5lY2Vzc2l0eSBvZiBhIGxpbmUs IGNoZWNrIGZpcnN0IGluIExJTlQuDQojDQojICRGcmVlQlNEOiBzcmMvc3lz L2kzODYvY29uZi9HRU5FUklDLHYgMS4xNDMuMi4yMyAxOTk5LzEwLzEwIDIz OjA0OjU2IHdwYXVsIEV4cCAkDQoNCm1hY2hpbmUJCSJpMzg2Ig0KY3B1CQki STU4Nl9DUFUiDQpjcHUJCSJJNjg2X0NQVSINCmlkZW50CQlHRU5FUklDDQpt YXh1c2Vycwk2NA0KDQpvcHRpb25zCQlLQkRfTUFYV0FJVD0xMA0Kb3B0aW9u cwkJS0JEX1JFU0VUREVMQVk9MTAwMA0Kb3B0aW9ucwkJS0JEX01BWFJFVFJZ PTEwDQpvcHRpb25zCQkiTVNHQlVGX1NJWkU9NDA5NjAiDQoNCm9wdGlvbnMg CU1BVEhfRU1VTEFURQkJI1N1cHBvcnQgZm9yIHg4NyBlbXVsYXRpb24NCm9w dGlvbnMgCUlORVQJCQkjSW50ZXJORVR3b3JraW5nDQpvcHRpb25zIAlGRlMJ CQkjQmVya2VsZXkgRmFzdCBGaWxlc3lzdGVtDQpvcHRpb25zIAlGRlNfUk9P VAkJI0ZGUyB1c2FibGUgYXMgcm9vdCBkZXZpY2UgW2tlZXAgdGhpcyFdDQpv cHRpb25zIAlNRlMJCQkjTWVtb3J5IEZpbGVzeXN0ZW0NCm9wdGlvbnMgCU5G UwkJCSNOZXR3b3JrIEZpbGVzeXN0ZW0NCm9wdGlvbnMgCU5GU19ST09UCQkj TkZTIHVzYWJsZSBhcyByb290IGRldmljZSwgIk5GUyIgcmVxJ2VkDQpvcHRp b25zIAlNU0RPU0ZTCQkJI01TRE9TIEZpbGVzeXN0ZW0NCm9wdGlvbnMgCSJD RDk2NjAiCQkjSVNPIDk2NjAgRmlsZXN5c3RlbQ0Kb3B0aW9ucyAJUFJPQ0ZT CQkJI1Byb2Nlc3MgZmlsZXN5c3RlbQ0Kb3B0aW9ucyAJIkNPTVBBVF80MyIJ CSNDb21wYXRpYmxlIHdpdGggQlNEIDQuMyBbS0VFUCBUSElTIV0NCm9wdGlv bnMgCVNDU0lfREVMQVk9MTUwMDAJI0JlIHBlc3NpbWlzdGljIGFib3V0IEpv ZSBTQ1NJIGRldmljZQ0Kb3B0aW9ucyAJVUNPTlNPTEUJCSNBbGxvdyB1c2Vy cyB0byBncmFiIHRoZSBjb25zb2xlDQpvcHRpb25zIAlVU0VSQ09ORklHCQkj Ym9vdCAtYyBlZGl0b3INCm9wdGlvbnMgCUtUUkFDRQkJCSNrdHJhY2UoMSkg c3lzY2FsbCB0cmFjZSBzdXBwb3J0DQpvcHRpb25zIAlTWVNWU0hNCQkJI1NZ U1Ytc3R5bGUgc2hhcmVkIG1lbW9yeQ0Kb3B0aW9ucyAJU1lTVk1TRwkJCSNT WVNWLXN0eWxlIG1lc3NhZ2UgcXVldWVzDQpvcHRpb25zIAlTWVNWU0VNCQkJ I1NZU1Ytc3R5bGUgc2VtYXBob3Jlcw0KDQpjb25maWcJCWtlcm5lbAlyb290 IG9uIHdkMA0KDQpjb250cm9sbGVyCWlzYTANCmNvbnRyb2xsZXIJcG5wMAkJ CSMgUG5QIHN1cHBvcnQgZm9yIElTQQ0KY29udHJvbGxlcglwY2kwDQoNCiMg RmxvcHB5IGRyaXZlcw0KY29udHJvbGxlcglmZGMwCWF0IGlzYT8gcG9ydCAi SU9fRkQxIiBiaW8gaXJxIDYgZHJxIDINCmRpc2sJCWZkMAlhdCBmZGMwIGRy aXZlIDANCg0KIyBJREUgY29udHJvbGxlciBhbmQgZGlza3MNCiNjb250cm9s bGVyCXdkYzAJYXQgaXNhPyBwb3J0ICJJT19XRDEiIGJpbyBpcnEgMTQNCiNk aXNrCQl3ZDAJYXQgd2RjMCBkcml2ZSAwDQojZGlzawkJd2QxCWF0IHdkYzAg ZHJpdmUgMQ0KDQojY29udHJvbGxlcgl3ZGMxCWF0IGlzYT8gcG9ydCAiSU9f V0QyIiBiaW8gaXJxIDE1DQojZGlzawkJd2QyCWF0IHdkYzEgZHJpdmUgMA0K I2Rpc2sJCXdkMwlhdCB3ZGMxIGRyaXZlIDENCg0KIyBBVEFQSSBkZXZpY2Vz DQojb3B0aW9ucwkJQVRBUEkJCSNFbmFibGUgQVRBUEkgc3VwcG9ydCBmb3Ig SURFIGJ1cw0KI29wdGlvbnMJCUFUQVBJX1NUQVRJQwkjRG9uJ3QgZG8gaXQg YXMgYW4gTEtNDQojZGV2aWNlCQlhY2QwCQkjSURFIENELVJPTQ0KI2Rldmlj ZQkJd2ZkMAkJI0lERSBGbG9wcHkgKGUuZy4gTFMtMTIwKQ0KDQojIFNDU0kg Q29udHJvbGxlcnMNCiMgQSBzaW5nbGUgZW50cnkgZm9yIGFueSBvZiB0aGVz ZSBjb250cm9sbGVycyAobmNyLCBhaGIsIGFoYykgaXMNCiMgc3VmZmljaWVu dCBmb3IgYW55IG51bWJlciBvZiBpbnN0YWxsZWQgZGV2aWNlcy4NCmNvbnRy b2xsZXIJbmNyMAkJIyBOQ1IvU3ltYmlvcyBMb2dpYw0KDQojIFNDU0kgcGVy aXBoZXJhbHMNCiMgT25seSBvbmUgb2YgZWFjaCBvZiB0aGVzZSBpcyBuZWVk ZWQsIHRoZXkgYXJlIGR5bmFtaWNhbGx5IGFsbG9jYXRlZC4NCmNvbnRyb2xs ZXIJc2NidXMwCQkjIFNDU0kgYnVzIChyZXF1aXJlZCkNCmRldmljZQkJZGEw CQkjIERpcmVjdCBBY2Nlc3MgKGRpc2tzKQ0KZGV2aWNlCQlzYTAJCSMgU2Vx dWVudGlhbCBBY2Nlc3MgKHRhcGUgZXRjKQ0KZGV2aWNlCQljZDAJCSMgQ0QN CmRldmljZQkJcGFzczAJCSMgUGFzc3Rocm91Z2ggZGV2aWNlIChkaXJlY3Qg U0NTSSkNCg0KIyBhdGtiZGMwIGNvbnRyb2xzIGJvdGggdGhlIGtleWJvYXJk IGFuZCB0aGUgUFMvMiBtb3VzZQ0KY29udHJvbGxlcglhdGtiZGMwCWF0IGlz YT8gcG9ydCBJT19LQkQgdHR5DQpkZXZpY2UJCWF0a2JkMAlhdCBpc2E/IHR0 eSBpcnEgMQ0KZGV2aWNlCQlwc20wCWF0IGlzYT8gdHR5IGlycSAxMg0KDQpk ZXZpY2UJCXZnYTAJYXQgaXNhPyBwb3J0ID8gY29uZmxpY3RzDQoNCiMgc3lz Y29ucyBpcyB0aGUgZGVmYXVsdCBjb25zb2xlIGRyaXZlciwgcmVzZW1ibGlu ZyBhbiBTQ08gY29uc29sZQ0KZGV2aWNlCQlzYzAJYXQgaXNhPyB0dHkNCg0K IyBGbG9hdGluZyBwb2ludCBzdXBwb3J0IC0gZG8gbm90IGRpc2FibGUuDQpk ZXZpY2UJCW5weDAJYXQgaXNhPyBwb3J0IElPX05QWCBpcnEgMTMNCg0KIyBQ b3dlciBtYW5hZ2VtZW50IHN1cHBvcnQgKHNlZSBMSU5UIGZvciBtb3JlIG9w dGlvbnMpDQpkZXZpY2UJCWFwbTAgICAgYXQgaXNhPwlmbGFncyAweDMxICMg QWR2YW5jZWQgUG93ZXIgTWFuYWdlbWVudA0KDQojIFNlcmlhbCAoQ09NKSBw b3J0cw0KZGV2aWNlCQlzaW8wCWF0IGlzYT8gcG9ydCAiSU9fQ09NMSIgZmxh Z3MgMHgxMCB0dHkgaXJxIDQNCmRldmljZQkJc2lvMQlhdCBpc2E/IHBvcnQg IklPX0NPTTIiIHR0eSBpcnEgMw0KI2RldmljZQkJc2lvMglhdCBpc2E/IGRp c2FibGUgcG9ydCAiSU9fQ09NMyIgdHR5IGlycSA1DQojZGV2aWNlCQlzaW8z CWF0IGlzYT8gZGlzYWJsZSBwb3J0ICJJT19DT000IiB0dHkgaXJxIDkNCg0K IyBQYXJhbGxlbCBwb3J0DQpkZXZpY2UJCXBwYzAJYXQgaXNhPyBwb3J0PyBm bGFncyAweDQwIG5ldCBpcnEgNw0KY29udHJvbGxlcglwcGJ1czAJCQkjIFBh cmFsbGVsIHBvcnQgYnVzIChyZXF1aXJlZCkNCmRldmljZQkJbHB0MAlhdCBw cGJ1cz8JIyBQcmludGVyDQpkZXZpY2UJCXBsaXAwCWF0IHBwYnVzPwkjIFRD UC9JUCBvdmVyIHBhcmFsbGVsDQpkZXZpY2UJCXBwaTAJYXQgcHBidXM/CSMg UGFyYWxsZWwgcG9ydCBpbnRlcmZhY2UgZGV2aWNlDQojY29udHJvbGxlcgl2 cG8wCWF0IHBwYnVzPwkjIFJlcXVpcmVzIHNjYnVzIGFuZCBkYTANCg0KIyBQ Q0kgRXRoZXJuZXQgTklDcy4NCmRldmljZQkJZnhwMAkJIyBJbnRlbCBFdGhl ckV4cHJlc3MgUFJPLzEwMEIgKDgyNTU3LCA4MjU1OCkNCg0KIyBQc2V1ZG8g ZGV2aWNlcyAtIHRoZSBudW1iZXIgaW5kaWNhdGVzIGhvdyBtYW55IHVuaXRz IHRvIGFsbG9jYXRlZC4NCnBzZXVkby1kZXZpY2UJbG9vcAkJIyBOZXR3b3Jr IGxvb3BiYWNrDQpwc2V1ZG8tZGV2aWNlCWV0aGVyCQkjIEV0aGVybmV0IHN1 cHBvcnQNCnBzZXVkby1kZXZpY2UJc2wJMQkjIEtlcm5lbCBTTElQDQpwc2V1 ZG8tZGV2aWNlCXR1bgkyCSMgUGFja2V0IHR1bm5lbA0KcHNldWRvLWRldmlj ZQlwdHkJMTYJIyBQc2V1ZG8tdHR5cyAodGVsbmV0IGV0YykNCnBzZXVkby1k ZXZpY2UJZ3ppcAkJIyBFeGVjIGd6aXBwZWQgYS5vdXQncw0KDQojIFRoZSBg YnBmaWx0ZXInIHBzZXVkby1kZXZpY2UgZW5hYmxlcyB0aGUgQmVya2VsZXkg UGFja2V0IEZpbHRlci4NCiMgQmUgYXdhcmUgb2YgdGhlIGFkbWluaXN0cmF0 aXZlIGNvbnNlcXVlbmNlcyBvZiBlbmFibGluZyB0aGlzIQ0KIyBUaGUgbnVt YmVyIG9mIGRldmljZXMgZGV0ZXJtaW5lcyB0aGUgbWF4aW11bSBudW1iZXIg b2YNCiMgc2ltdWx0YW5lb3VzIEJQRiBjbGllbnRzIHByb2dyYW1zIHJ1bm5h YmxlLg0KcHNldWRvLWRldmljZQlicGZpbHRlciAxNgkjQmVya2VsZXkgcGFj a2V0IGZpbHRlcg0KDQoNCmNvbnRyb2xsZXIJc21idXMwDQpjb250cm9sbGVy CWlpY2J1czANCmNvbnRyb2xsZXIJaWljYmIwDQpkZXZpY2UJCWJrdHIwDQoN Cm9wdGlvbnMJCSJWTTg2Ig0Kb3B0aW9ucwkJVkVTQQkJCSMgbmVlZHMgVk04 NiBkZWZpbmVkIHRvbyEhDQpkZXZpY2UgcGNtMCBhdCBpc2E/IHBvcnQgPyB0 dHkgaXJxIDEwIGRycSAxIGZsYWdzIDB4MA0Kb3B0aW9ucwkJU09GVFVQREFU RVMNCg== --0-439363126-945220252=:18262-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 17:32:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from lunatic.oneinsane.net (lunatic.oneinsane.net [207.113.133.231]) by hub.freebsd.org (Postfix) with ESMTP id 8EA131546C for ; Tue, 14 Dec 1999 17:32:50 -0800 (PST) (envelope-from insane@lunatic.oneinsane.net) Received: by lunatic.oneinsane.net (Postfix, from userid 1000) id D6AF3194; Tue, 14 Dec 1999 17:32:48 -0800 (PST) Date: Tue, 14 Dec 1999 17:32:48 -0800 From: Ron 'The InSaNe One' Rosson To: freebsd-stable@freebsd.org Subject: Netgear FA410TXc Message-ID: <19991214173248.A6483@lunatic.oneinsane.net> Reply-To: Ron Rosson Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD lunatic.oneinsane.net 3.3-STABLE X-Moon: The Moon is Waxing Crescent (41% of Full) X-Opinion: What you read here is my IMHO X-Disclaimer: I am a firm believer in RTFM X-WWW: http://www.oneinsane.net X-PGP-KEY: http://www.oneinsane.net/~insane/insane2-pgp5i.txt X-Uptime: 5:29PM up 34 days, 19:52, 2 users, load averages: 0.05, 0.04, 0.00 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone now if the this PCMCIA ethernet card is going to make it in to the main source tree. I have a laptop with this card and am currently running OpenBSD which is supported. The problem is that my habits and openbsd arre not the same. I know the card is supported in PAO but I like staying with STABLE more than release. If anyone has any way of knowing if this is going to happen or if there is a way to stay STABLE with PAO I am all ears. TIA -- ------------------------------------------------------------------- Ron Rosson ... and a UNIX user said ... The InSaNe One rm -rf * insane@oneinsane.net and all was /dev/null and *void() ------------------------------------------------------------------- Q: Best way to secure a Linux box? A: Place it behind a FreeBSD firewall. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 19:11:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 4C26F151D2 for ; Tue, 14 Dec 1999 19:11:15 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA06584; Tue, 14 Dec 1999 19:14:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912150314.TAA06584@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Ron Rosson Cc: freebsd-stable@freebsd.org Subject: Re: Netgear FA410TXc In-reply-to: Your message of "Tue, 14 Dec 1999 17:32:48 PST." <19991214173248.A6483@lunatic.oneinsane.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Dec 1999 19:14:16 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Anyone now if the this PCMCIA ethernet card is going to make it in to > the main source tree. I have a laptop with this card and am currently > running OpenBSD which is supported. The problem is that my habits and > openbsd arre not the same. I know the card is supported in PAO but I > like staying with STABLE more than release. > > If anyone has any way of knowing if this is going to happen or if there > is a way to stay STABLE with PAO I am all ears. I'm using one right now under -current; it should probably work on -stable as well. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 23:23:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 5DA291539C for ; Tue, 14 Dec 1999 23:23:36 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id XAA56359; Tue, 14 Dec 1999 23:23:34 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 14 Dec 1999 23:23:34 -0800 (PST) From: Doug White To: Rahul Dhesi Cc: freebsd-stable@FreeBSD.ORG Subject: Re: how to rewrite the data field replaceable unit? In-Reply-To: <19991214120034.10BC021C@waltz.rahul.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 Tue, 14 Dec 1999, Rahul Dhesi wrote: > Mike Smith writes: > > >> (da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data field replaceable unit: 20 sks:80,a0 > ... > > >That's two things, 'data' and 'field replaceable unit'. The FRU code > >tells you which part of the drive is failing - in this case the vendor > >code for the broken bit is '20'. > > Thanks. > > A suggestion to the Device Driver Gods: Please make error messages > understandable to the rest of us. How is this not understandable? It presents the problem, "Unrecovered read error," and even is nice enough to suggest a solution, "recommend rewrite the data." How would you rewrite this to be more "understandable", yet still provide the same amount of information? This is like the newbies that ask "What does it mean when it says '/usr: file system full'?" :-/ Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org PS: If you like terse error messages, try Linux. Things go wrong and you *might* get a message. And if you do, it *might* bother to decode the ASC for you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 23:26:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 97510151BC; Tue, 14 Dec 1999 23:26:14 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id XAA56378; Tue, 14 Dec 1999 23:26:14 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 14 Dec 1999 23:26:14 -0800 (PST) From: Doug White To: Mike Smith Cc: stable@FreeBSD.ORG Subject: Re: Bugfixed AMI MegaRAID driver for -stable available In-Reply-To: <199912142128.NAA01774@mass.cdrom.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 Tue, 14 Dec 1999, Mike Smith wrote: > > Due to a programming error, the previous release of the AMI MegaRAID > driver for FreeBSD 3.x would not work with Enterprise 418 and 428 > series controllers. This has been corrected, and the new driver is > available at > > http://www.freebsd.org/~msmith/RAID/ami/amr-stable-991214.tar.gz Will this make it into 3.4? Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 14 23:33:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zgia.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with SMTP id 2C8A914C19 for ; Tue, 14 Dec 1999 23:33:21 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by zgia.zp.ua (8.9.3/8.9.3) with ESMTP id KAA35983 for ; Wed, 15 Dec 1999 10:32:41 GMT Date: Wed, 15 Dec 1999 10:32:41 +0000 (GMT) From: Alexandr Listopad Cc: freebsd-stable@FreeBSD.ORG Subject: cvsup and src/contrib/bind. 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 Hi! Is there are an error in this sources? I try to make - but get error!.. cd: can't cd to bsd *** Error code 2 Stop. *** Error code 1 Stop. # :-[ Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 0:18:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 4811715484 for ; Wed, 15 Dec 1999 00:18:17 -0800 (PST) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id DAA09785; Wed, 15 Dec 1999 03:17:38 -0500 Date: Wed, 15 Dec 1999 03:17:38 -0500 (EST) From: Mike Nowlin To: Doug White Cc: Rahul Dhesi , freebsd-stable@FreeBSD.ORG Subject: Re: how to rewrite the data field replaceable unit? 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 > How is this not understandable? It presents the problem, "Unrecovered > read error," and even is nice enough to suggest a solution, "recommend > rewrite the data." How would you rewrite this to be more > "understandable", yet still provide the same amount of information? The message was: (da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data field replaceable unit: 20 sks:80,a0 He's referring to the punctuation, which I agree with -- it could be misunderstood quite easily -- the message could be "recommend rewrite the data field replaceable unit", and the argument could be "20 sks:80,a0". Hence his question: "How do you rewrite the data field replacable unit?" "Data field" isn't that uncommon of an expression in computer terms... :) I do know what those messages mean, and the first time I ran into them a quick grep through the source revealed that it was two different messages, but a comma would be useful in there: (da2:ahc0:0:2:0) Unrecovered read error - recommend rewrite the data, field replaceable unit: 20 sks:80,a0 --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 1:41:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id C4CF7153B0; Wed, 15 Dec 1999 01:41:19 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id KAA03032; Wed, 15 Dec 1999 10:41:16 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912142128.NAA01774@mass.cdrom.com> References: <199912142128.NAA01774@mass.cdrom.com> Date: Wed, 15 Dec 1999 10:03:56 +0100 To: Mike Smith , stable@FreeBSD.ORG From: Brad Knowles Subject: Re: Bugfixed AMI MegaRAID driver for -stable available Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 1:28 PM -0800 1999/12/14, Mike Smith wrote: > http://www.freebsd.org/~msmith/RAID/ami/amr-stable-991214.tar.gz I'm curious. I know that the current version of the handbook only mentions the DPT SmartRAID controllers (up to the "IV" model) as being supported, although there clearly are now drivers coming up for the AMI MegaRAID controllers, I know you're working on the Mylex drivers, and I know that the first DPT SmartRAID VI was supposed to roll off the production line last Friday with drivers that will soon be released for it and the previous SmartRAID V model. Are there any plans to update any of the handbook to match the more recent state of affairs in this area? -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 3:16:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 93D591534E for ; Wed, 15 Dec 1999 03:16:27 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA53559 for ; Wed, 15 Dec 1999 03:16:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: stable@freebsd.org Subject: 3.4-RELEASE moved forward 24 hours. Date: Wed, 15 Dec 1999 03:16:21 -0800 Message-ID: <53555.945256581@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There are still a few more things to be worked out which I know already are more than 12 hour projects, so please consider the release date delayed by a full day. Heh. Sorry, slippage... :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 5:46:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from scientia.demon.co.uk (scientia.demon.co.uk [212.228.14.13]) by hub.freebsd.org (Postfix) with ESMTP id 497C61538B for ; Wed, 15 Dec 1999 05:46:18 -0800 (PST) (envelope-from ben@scientia.demon.co.uk) Received: from strontium.scientia.demon.co.uk ([192.168.0.4] ident=ben) by scientia.demon.co.uk with smtp (Exim 3.092 #1) id 11yEjS-000Acn-00; Wed, 15 Dec 1999 13:44:42 +0000 Date: Wed, 15 Dec 1999 13:44:42 +0000 From: Ben Smithurst To: Jamie Norwood Cc: Thomas Veldhouse , "Jeffrey J. Libman" , freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run Message-ID: <19991215134442.A7473@strontium.scientia.demon.co.uk> References: <19991214111328.A25086@mushhaven.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991214111328.A25086@mushhaven.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jamie Norwood wrote: > Actually, wouldn't he want rl0, for realtek cards? Not if it's like the NE2000 clones I use, based around the 8029 chip - ed is the correct driver for this. rl's manpage only mentions 8129 and 8139. -- Ben Smithurst | PGP: 0x99392F7D ben@scientia.demon.co.uk | key available from keyservers and | ben+pgp@scientia.demon.co.uk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 7:12: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.bna.bellsouth.net (mail1.bna.bellsouth.net [205.152.150.13]) by hub.freebsd.org (Postfix) with ESMTP id CA64D14F48 for ; Wed, 15 Dec 1999 07:11:57 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-216-78-82-215.cha.bellsouth.net [216.78.82.215]) by mail1.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id KAA08754 for ; Wed, 15 Dec 1999 10:11:44 -0500 (EST) Message-ID: <3857AFC2.398188F0@siteplus.com> Date: Wed, 15 Dec 1999 10:12:03 -0500 From: SitePlus Web Services X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i486) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: /var full Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, I am new to this. My web server is beginning to get pretty busy and I noticed today that /var was at 90% I moved and linked log and mail to /usr/log and /usr/mail but it is still pretty full. When I set up the server I allotted / and /var both 100megs. I suppose that was not enough for /var. Any more suggestions, Thanks, Jim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 7:26: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sol.freibergnet.de (sol.freibergnet.de [194.123.255.4]) by hub.freebsd.org (Postfix) with ESMTP id A45E515292 for ; Wed, 15 Dec 1999 07:26:00 -0800 (PST) (envelope-from mw@sol.freibergnet.de) Received: (from mw@localhost) by sol.freibergnet.de (8.9.3/8.9.3) id QAA29253; Wed, 15 Dec 1999 16:25:07 +0100 (CET) (envelope-from mw) Date: Wed, 15 Dec 1999 16:25:07 +0100 From: Martin Welk To: SitePlus Web Services Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: /var full Message-ID: <19991215162507.D63732@sol.freibergnet.de> Reply-To: mw@freibergnet.de References: <3857AFC2.398188F0@siteplus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <3857AFC2.398188F0@siteplus.com>; from jim@siteplus.com on Wed, Dec 15, 1999 at 10:12:03AM -0500 Organization: FreibergNet Systemhaus GbR, D-09599 Freiberg X-Operating-System: FreeBSD http://www.freebsd.org/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 10:12:03AM -0500, SitePlus Web Services wrote: > I am new to this. My web server is beginning to get pretty busy and I > noticed today that /var was at 90% I moved and linked log and mail to > /usr/log and /usr/mail but it is still pretty full. When I set up the > server I allotted / and /var both 100megs. I suppose that was not > enough for /var. I'm not really sure what this has to do with FreeBSD-stable and why you don't have a full real name, but if you tell us you have a busy web site it may be a very cool trick to look for those web server's log files and cut them off regularly. When you're using Apache from the ports, they could reside at /var/log/[apache|httpd]-access /var/log/[apache|httpd]-error Take care when you try to simply move them, you will have to send the httpd a SIGHUP to re-open his log files, otherwise they won't be unlinked. Regards, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 7:26:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id EEC1815261 for ; Wed, 15 Dec 1999 07:26:15 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id KAA19957; Wed, 15 Dec 1999 10:26:07 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <199912151526.KAA19957@blackhelicopters.org> Subject: Re: /var full In-Reply-To: <3857AFC2.398188F0@siteplus.com> from SitePlus Web Services at "Dec 15, 1999 10:12: 3 am" To: jim@siteplus.com (SitePlus Web Services) Date: Wed, 15 Dec 1999 10:26:07 -0500 (EST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You can set some of your web sites to log to another file, rather than the default /var/log/apache-*. You could add another hard drive to your system. Lastly, check your /etc/syslog.conf to be sure log files are discarded in a timely manner. See man syslog for details. ==ml > Hi all, > > I am new to this. My web server is beginning to get pretty busy and I > noticed today that /var was at 90% I moved and linked log and mail to > /usr/log and /usr/mail but it is still pretty full. When I set up the > server I allotted / and /var both 100megs. I suppose that was not > enough for /var. > > Any more suggestions, > > Thanks, Jim > > > > 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 15 7:35:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id 5F1791539C for ; Wed, 15 Dec 1999 07:35:52 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.11 1999/11/10 17:27:15 spurcell Exp $) with ESMTP id PAA27111; Wed, 15 Dec 1999 15:33:41 GMT Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.8 1999/04/16 15:25:49 steved Exp steved $) with ESMTP id IAA18760; Wed, 15 Dec 1999 08:34:16 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id KAA17250; Wed, 15 Dec 1999 10:34:16 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14423.46328.180570.18317@hip186.ch.intel.com> Date: Wed, 15 Dec 1999 08:34:16 -0700 (MST) To: Alexandr Listopad Cc: freebsd-stable@freebsd.org Subject: Re: cvsup and src/contrib/bind. In-Reply-To: References: X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Wednesday, December 15, Alexandr Listopad wrote: ] > Hi! > Is there are an error in this sources? > I try to make - but get error!.. > > cd: can't cd to bsd > *** Error code 2 > > Stop. > *** Error code 1 > If you give us some more information, we might be able to help. What were you exactly trying to build? Your subject suggests src/contrib/bind but also says "cvsup". What were you trying to do that gave you an error? Please mail back this information along with all the output that the command gives you to the list and we might have a better chance at helping. If something croaked in a "make buildworld" w.r.t. "bind" then re CVSup your sources and try again. I rebuilt world last night with the new bind placed into the tree and all went without a hitch (as usual :). regards, -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds CEG, CCE, Next Generation Flows, HLA | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 7:47:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zgia.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with SMTP id 055B7154A9 for ; Wed, 15 Dec 1999 07:47:13 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by zgia.zp.ua (8.9.3/8.9.3) with ESMTP id SAA53313; Wed, 15 Dec 1999 18:59:37 +0200 (EET) Date: Wed, 15 Dec 1999 18:59:37 +0200 (EET) From: Alexandr Listopad To: John Reynolds~ Cc: freebsd-stable@FreeBSD.ORG Subject: Re: cvsup and src/contrib/bind. In-Reply-To: <14423.46328.180570.18317@hip186.ch.intel.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 jreyno> jreyno>If you give us some more information, we might be able to help. What were you jreyno>exactly trying to build? Your subject suggests src/contrib/bind but also says jreyno>"cvsup". What were you trying to do that gave you an error? Please mail back jreyno>this information along with all the output that the command gives you to the jreyno>list and we might have a better chance at helping. jreyno> jreyno>If something croaked in a "make buildworld" w.r.t. "bind" then re CVSup your jreyno>sources and try again. I rebuilt world last night with the new bind placed jreyno>into the tree and all went without a hitch (as usual :). jreyno> jreyno>regards, jreyno> root@Eagle$ cd contrib/bind/ root@Eagle$ make .... .... cc -O2 -g -I../../port/freebsd/include -I../../include -c ev_streams.c ld -x -r ev_streams.o -o a.out && mv a.out ev_streams.o if test ! -d threaded ; then mkdir threaded ; fi cc -O2 -g -I../../port/freebsd/include -I../../include -D_REENTRANT -c ev_wait s.c -o threaded/ev_waits.o ld -x -r threaded/ev_waits.o -o a.out && mv a.out threaded/ev_waits.o cc -O2 -g -I../../port/freebsd/include -I../../include -c ev_waits.c ld -x -r ev_waits.o -o a.out && mv a.out ev_waits.o ( cd threaded ; ar cru ../../../lib/libbind_r.a tree.o base64.o bitncmp.o asse rtions.o memcluster.o logging.o heap.o ctl_p.o ctl_srvr.o ctl_clnt.o eventlib .o ev_connects.o ev_files.o ev_timers.o ev_streams.o ev_waits.o ; : ../../../ lib/libbind_r.a ) ar cru ../../lib/libbind.a tree.o base64.o bitncmp.o assertions.o memcluster.o logging.o heap.o ctl_p.o ctl_srvr.o ctl_clnt.o eventlib.o ev_connects.o ev_fi les.o ev_timers.o ev_streams.o ev_waits.o : ../../lib/libbind.a cd: can't cd to bsd *** Error code 2 Stop. *** Error code 1 Stop. This is that error... ;-| Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 7:51: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.bna.bellsouth.net (mail1.bna.bellsouth.net [205.152.150.13]) by hub.freebsd.org (Postfix) with ESMTP id 2E4061542C for ; Wed, 15 Dec 1999 07:51:05 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-216-78-82-215.cha.bellsouth.net [216.78.82.215]) by mail1.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id KAA16344; Wed, 15 Dec 1999 10:50:51 -0500 (EST) Message-ID: <3857B8EF.15897975@siteplus.com> Date: Wed, 15 Dec 1999 10:51:11 -0500 From: SitePlus Web Services X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i486) X-Accept-Language: en MIME-Version: 1.0 To: Mikhail Teterin Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: /var full References: <199912151529.KAA32510@rtfm.newton> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks, I had a lot of good suggestions. This one was most helpful. Remember that I had already moved mail and logs, so it turns out that the locate data base was the culprit. It will have a new home also. du -k -s -x * | sort -n 0 log 0 mail 1 account 1 preserve 1 rwho 2 crash 2 msgs 3 at 5 games 14 spool 15 backups 19 yp 45 tmp 51 run 84 cron 1374 db Thanks again, Jim Mikhail Teterin wrote: > SitePlus Web Services once stated: > > =Hi all, > > Please, ask this questions at questions@freebsd.org next time. > > =I am new to this. My web server is beginning to get pretty busy and I > =noticed today that /var was at 90% I moved and linked log and mail to > =/usr/log and /usr/mail but it is still pretty full. When I set up the > =server I allotted / and /var both 100megs. I suppose that was not > =enough for /var. > > Find out where the space is used: > > cd /var > du -k -s -x * | sort -n > > This will give you the sorted list. The last items will be the most > space consuming... Examine the last couple of items in the list with the > same commands. Have fun! > > -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 8: 4:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.bna.bellsouth.net (mail2.bna.bellsouth.net [205.152.150.14]) by hub.freebsd.org (Postfix) with ESMTP id 67B5B153C9 for ; Wed, 15 Dec 1999 08:04:40 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-216-78-82-215.cha.bellsouth.net [216.78.82.215]) by mail2.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id KAA29208; Wed, 15 Dec 1999 10:52:58 -0500 (EST) Message-ID: <3857BC29.53ADA94E@siteplus.com> Date: Wed, 15 Dec 1999 11:04:57 -0500 From: SitePlus Web Services X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i486) X-Accept-Language: en MIME-Version: 1.0 To: mw@freibergnet.de Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: /var full References: <3857AFC2.398188F0@siteplus.com> <19991215162507.D63732@sol.freibergnet.de> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG What this has to do with stable is that I run FreeBSD-stable, and I installed most things with defaults. I only stated that the server had become busy because I thought the http logs were the problem. Other users are the main reason that it is busy. I don't consider my site as anything special. After I moved the logs and mail I still had the problem so I was asking for help with a FreeBSD machine. I thought that was what the mailing list was for. And the reason for the name is that Netscape mail only allows one identity. Since I answer customer mail most often, I have found it easier to leave it generic, however I changed it this time just for you. James W. Weeks, alias Jim Martin Welk wrote: > > I'm not really sure what this has to do with FreeBSD-stable and why you > don't have a full real name, but if you tell us you have a busy web site > it may be a very cool trick to look for those web server's log files > and cut them off regularly. > > When you're using Apache from the ports, they could reside at > > /var/log/[apache|httpd]-access > /var/log/[apache|httpd]-error > > Take care when you try to simply move them, you will have to send the > httpd a SIGHUP to re-open his log files, otherwise they won't be > unlinked. > > Regards, > > Martin > -- > FreibergNet Systemhaus GbR Martin Welk * Sales, Support > Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 > Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 > D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ > > 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 15 8: 7:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cichlids.com (as15-095.rp-plus.de [149.221.237.95]) by hub.freebsd.org (Postfix) with ESMTP id E87EF154BF for ; Wed, 15 Dec 1999 08:07:10 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 4ACA4AB89; Wed, 15 Dec 1999 16:41:13 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id QAA04538; Wed, 15 Dec 1999 16:41:01 +0100 (CET) (envelope-from alex) Date: Wed, 15 Dec 1999 16:41:01 +0100 From: Alexander Langer To: SitePlus Web Services Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: /var full Message-ID: <19991215164101.B3427@cichlids.cichlids.com> Mail-Followup-To: SitePlus Web Services , "freebsd-stable@FreeBSD.ORG" References: <3857AFC2.398188F0@siteplus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3857AFC2.398188F0@siteplus.com>; from jim@siteplus.com on Wed, Dec 15, 1999 at 10:12:03AM -0500 X-PGP-Fingerprint: 44 28 CA 4C 46 5B D3 A8 A8 E3 BA F3 4E 60 7D 7F X-Verwirrung: Dieser Header dient der allgemeinen Verwirrung. Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thus spake SitePlus Web Services (jim@siteplus.com): > /usr/log and /usr/mail but it is still pretty full. When I set up the > server I allotted / and /var both 100megs. I suppose that was not > enough for /var. Take a look at /var/account/* if these are the big files, then turn of accounting in rc.conf Alex -- I doubt, therefore I might be. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 8:22:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 47B251529A for ; Wed, 15 Dec 1999 08:22:19 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id RAA17429; Wed, 15 Dec 1999 17:21:57 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <3857BC29.53ADA94E@siteplus.com> References: <3857AFC2.398188F0@siteplus.com> <19991215162507.D63732@sol.freibergnet.de> <3857BC29.53ADA94E@siteplus.com> Date: Wed, 15 Dec 1999 17:21:45 +0100 To: SitePlus Web Services , mw@freibergnet.de From: Brad Knowles Subject: Re: /var full Cc: "freebsd-stable@FreeBSD.ORG" Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:04 AM -0500 1999/12/15, SitePlus Web Services wrote: > What this has to do with stable is that I run FreeBSD-stable, and I > installed most things with defaults. Generally speaking, if you've got a question, you should first look in the "FreeBSD Handbook" at to see if it has already been addressed. If not, then check the FAQ at . If it's still not addressed, then search the archives of the FreeBSD mailing lists via the interface at . If you haven't found any answers there, I'd suggest going to Deja.com (or some other news-via-web site) and doing a search on the comp.unix.bsd.freebsd.* newsgroups to see if anyone else has recently discussed this issue there. After doing all the above, if you *still* can't find any answers, then your questions should be sent to freebsd-questions@freebsd.org. Only if you're subscribed to a particular FreeBSD mailing list *other* than -questions, you're tracking that particular version of the OS on one of your servers (or otherwise actively participating in the furtherance of that activity), and you know for a fact that it's relevant to the list in question, should you then post it to that list. If you should happen to post something to -questions and it really belongs somewhere else, appropriate people will be glad to help you find the right list. All of this information and more is available at the FreeBSD site, most with appropriate links from the main page at . Of course, these are all things that everyone who is subscribed to the -stable mailing list already knows, which is almost certainly the reason why you got the rather testy responses from other people along the lines of "Why are you posting this here?" -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 8:32:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wzrd.com (mail.wzrd.com [206.99.165.3]) by hub.freebsd.org (Postfix) with ESMTP id 1B29F151FF for ; Wed, 15 Dec 1999 08:32:51 -0800 (PST) (envelope-from danh@wzrd.com) Received: by mail.wzrd.com (Postfix, from userid 91) id 2B4C95D018; Wed, 15 Dec 1999 11:32:50 -0500 (EST) Subject: Re: cvsup and src/contrib/bind. In-Reply-To: from Alexandr Listopad at "Dec 15, 1999 6:59:37 pm" To: laa@ZGIA.zp.ua (Alexandr Listopad) Date: Wed, 15 Dec 1999 11:32:50 -0500 (EST) Cc: freebsd-stable@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2242 Message-Id: <19991215163250.2B4C95D018@mail.wzrd.com> From: danh@wzrd.com (Dan Harnett) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cd /usr/src/usr.sbin/named && make cd /usr/src/libexec/named-xfer && make etc ... > > > jreyno> > jreyno>If you give us some more information, we might be able to help. What were you > jreyno>exactly trying to build? Your subject suggests src/contrib/bind but also says > jreyno>"cvsup". What were you trying to do that gave you an error? Please mail back > jreyno>this information along with all the output that the command gives you to the > jreyno>list and we might have a better chance at helping. > jreyno> > jreyno>If something croaked in a "make buildworld" w.r.t. "bind" then re CVSup your > jreyno>sources and try again. I rebuilt world last night with the new bind placed > jreyno>into the tree and all went without a hitch (as usual :). > jreyno> > jreyno>regards, > jreyno> > > root@Eagle$ cd contrib/bind/ > root@Eagle$ make > .... > .... > cc -O2 -g -I../../port/freebsd/include -I../../include -c ev_streams.c > ld -x -r ev_streams.o -o a.out && mv a.out ev_streams.o > if test ! -d threaded ; then mkdir threaded ; fi > cc -O2 -g -I../../port/freebsd/include -I../../include -D_REENTRANT -c > ev_wait > s.c -o threaded/ev_waits.o > ld -x -r threaded/ev_waits.o -o a.out && mv a.out threaded/ev_waits.o > cc -O2 -g -I../../port/freebsd/include -I../../include -c ev_waits.c > ld -x -r ev_waits.o -o a.out && mv a.out ev_waits.o > ( cd threaded ; ar cru ../../../lib/libbind_r.a tree.o base64.o > bitncmp.o asse > rtions.o memcluster.o logging.o heap.o ctl_p.o ctl_srvr.o ctl_clnt.o > eventlib > .o ev_connects.o ev_files.o ev_timers.o ev_streams.o ev_waits.o ; : > ../../../ > lib/libbind_r.a ) > ar cru ../../lib/libbind.a tree.o base64.o bitncmp.o assertions.o > memcluster.o > logging.o heap.o ctl_p.o ctl_srvr.o ctl_clnt.o eventlib.o ev_connects.o > ev_fi > les.o ev_timers.o ev_streams.o ev_waits.o > : ../../lib/libbind.a > cd: can't cd to bsd > *** Error code 2 > > Stop. > *** Error code 1 > > Stop. > > This is that error... ;-| > > Regards, > Listopad Alexandr > (laa@zgia.zp.ua), LAA7-RIPE > ZGIA, Zaporozhye, Ukraine. > http://www.zgia.zp.ua. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 15 8:42:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zgia.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with SMTP id 76ED7152DB for ; Wed, 15 Dec 1999 08:42:07 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by zgia.zp.ua (8.9.3/8.9.3) with ESMTP id SAA92005; Wed, 15 Dec 1999 18:41:42 +0200 (EET) Date: Wed, 15 Dec 1999 18:41:42 +0200 (EET) From: Alexandr Listopad To: Dan Harnett Cc: freebsd-stable@FreeBSD.ORG Subject: Re: cvsup and src/contrib/bind. In-Reply-To: <19991215163250.2B4C95D018@mail.wzrd.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 danh>cd /usr/src/usr.sbin/named && make danh>cd /usr/src/libexec/named-xfer && make danh>etc ... danh> heh... I'm re-buildworld... "20 minutes - fly is good!"... ;> Thanks! danh>> root@Eagle$ cd contrib/bind/ danh>> root@Eagle$ make danh>> .... danh>> .... danh>> cc -O2 -g -I../../port/freebsd/include -I../../include -c ev_streams.c danh>> ld -x -r ev_streams.o -o a.out && mv a.out ev_streams.o danh>> if test ! -d threaded ; then mkdir threaded ; fi danh>> cc -O2 -g -I../../port/freebsd/include -I../../include -D_REENTRANT -c danh>> ev_wait danh>> s.c -o threaded/ev_waits.o danh>> ld -x -r threaded/ev_waits.o -o a.out && mv a.out threaded/ev_waits.o danh>> cc -O2 -g -I../../port/freebsd/include -I../../include -c ev_waits.c danh>> ld -x -r ev_waits.o -o a.out && mv a.out ev_waits.o danh>> ( cd threaded ; ar cru ../../../lib/libbind_r.a tree.o base64.o danh>> bitncmp.o asse danh>> rtions.o memcluster.o logging.o heap.o ctl_p.o ctl_srvr.o ctl_clnt.o danh>> eventlib danh>> .o ev_connects.o ev_files.o ev_timers.o ev_streams.o ev_waits.o ; : danh>> ../../../ danh>> lib/libbind_r.a ) danh>> ar cru ../../lib/libbind.a tree.o base64.o bitncmp.o assertions.o danh>> memcluster.o danh>> logging.o heap.o ctl_p.o ctl_srvr.o ctl_clnt.o eventlib.o ev_connects.o danh>> ev_fi danh>> les.o ev_timers.o ev_streams.o ev_waits.o danh>> : ../../lib/libbind.a danh>> cd: can't cd to bsd danh>> *** Error code 2 danh>> danh>> Stop. danh>> *** Error code 1 danh>> danh>> Stop. danh>> danh>> This is that error... ;-| danh>> danh>> Regards, danh>> Listopad Alexandr danh>> (laa@zgia.zp.ua), LAA7-RIPE danh>> ZGIA, Zaporozhye, Ukraine. danh>> http://www.zgia.zp.ua. danh>> danh>> danh>> danh>> To Unsubscribe: send mail to majordomo@FreeBSD.org danh>> with "unsubscribe freebsd-stable" in the body of the message danh>> danh> danh> danh> danh>To Unsubscribe: send mail to majordomo@FreeBSD.org danh>with "unsubscribe freebsd-stable" in the body of the message danh> Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 9:33: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sol.freibergnet.de (sol.freibergnet.de [194.123.255.4]) by hub.freebsd.org (Postfix) with ESMTP id 278BD154D3 for ; Wed, 15 Dec 1999 09:33:02 -0800 (PST) (envelope-from mw@sol.freibergnet.de) Received: (from mw@localhost) by sol.freibergnet.de (8.9.3/8.9.3) id SAA81463; Wed, 15 Dec 1999 18:32:11 +0100 (CET) (envelope-from mw) Date: Wed, 15 Dec 1999 18:32:11 +0100 From: Martin Welk To: SitePlus Web Services Cc: mw@freibergnet.de, "freebsd-stable@FreeBSD.ORG" Subject: Re: /var full Message-ID: <19991215183211.A74422@sol.freibergnet.de> Reply-To: mw@freibergnet.de References: <3857AFC2.398188F0@siteplus.com> <19991215162507.D63732@sol.freibergnet.de> <3857BC29.53ADA94E@siteplus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: <3857BC29.53ADA94E@siteplus.com>; from jim@siteplus.com on Wed, Dec 15, 1999 at 11:04:57AM -0500 Organization: FreibergNet Systemhaus GbR, D-09599 Freiberg X-Operating-System: FreeBSD http://www.freebsd.org/ Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 15, 1999 at 11:04:57AM -0500, SitePlus Web Services wrote: > What this has to do with stable is that I run FreeBSD-stable, and I > installed most things with defaults. I only stated that the server had > become busy because I thought the http logs were the problem. Other users > are the main reason that it is busy. I don't consider my site as anything > special. After I moved the logs and mail I still had the problem so I was > asking for help with a FreeBSD machine. I thought that was what the mailing > list was for. And the reason for the name is that Netscape mail only allows > one identity. Since I answer customer mail most often, I have found it > easier to leave it generic, however I changed it this time just for you. You could use a mailer where that From: header is changeable by the user :-) Okay, let's not get into mailer discussion, I've just converted from xfmail to mutt :-) (xfmail is so slooooow over a non-local network connection :-) ) If you think, your /var file system is too small because you're running out of space, just check what's in there. You neither gave the people reading the list an information how much space your /var file system has actually neither what your primary doing with. We have a /var file system at a customer's server that runs sometimes out of space although it has more than three gigabyte avaiable, and it's just for e-mail. You ask why? Because sometimes they get e-mails of sizes larger than 50 megabytes and they are spread across 10 mailboxes and more and not every user takes away his monstermails every 15 minutes. Don't tell me that we shouldn't do this that way, it's the customer's special wish and he knows about the difficulties. OTOH, I know /var file systems not larger than 50 megabytes, because nobody uses e-mail on that machine and there are almost no interactive users and the logs are circled by newsyslog regularly and so on, because it's primary purpose is to run as an NFS server. Perhaps I was a little rude in first e-mail but I found it very astonishing that you asked for help with that little description for a problem you could easily solve by looking and planning what you are going to do with your box. I know somebody who set up a news server (INN) a while ago. We had technical difficulties with the machine and reading news via NNRP was constantly getting slower the longer that machine ran. Okay, for that technical reasons, the news server was reinstalled and it was constantly getting slower after four or five weeks. It receives only a small feed, the "de" hiercharchy. When that news server was re- installed, I said one should remember to setup expire. Yes, that machine is using cycbuffs for the news spool, but the news overview (needed for faster NNRP client access) has to run through an expire anyway. So that good old ufs was the bottleneck and after expiring more than 900,000 entries it was as fast as it was the first days and is still as expire is now called by crontab daily. What I want to say: this has nothing to do with FreeBSD itself, but with a not completely configured software doing its thing. However, with further information it could at least be possible for me to help you. How much is your /var now and what are you doing with it? (Perhaps something like ``cd /var; du *'' can give enlightment - mentally, not the window manager :-) ) Regards, Martin -- FreibergNet Systemhaus GbR Martin Welk * Sales, Support Systemhaus für Daten- und Netzwerktechnik phone +49 3731 781387 Unternehmensgruppe Liebscher & Partner fax +49 3731 781377 D-09599 Freiberg * Am St. Niclas Schacht 13 http://www.freibergnet.de/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 10: 3:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tornado.cisco.com (tornado.cisco.com [171.69.104.22]) by hub.freebsd.org (Postfix) with ESMTP id 0BBB315494 for ; Wed, 15 Dec 1999 10:03:09 -0800 (PST) (envelope-from bmcgover@bmcgover-pc.cisco.com) Received: from bmcgover-pc.cisco.com (root@bmcgover-pc.cisco.com [171.69.104.147]) by tornado.cisco.com (8.8.5-Cisco.1/8.6.5) with ESMTP id NAA28829; Wed, 15 Dec 1999 13:03:07 -0500 (EST) Received: from bmcgover-pc.cisco.com (bmcgover@localhost.pa.dtd.cisco.com [127.0.0.1]) by bmcgover-pc.cisco.com (8.9.3/8.9.3) with ESMTP id NAA06965; Wed, 15 Dec 1999 13:02:58 -0500 (EST) (envelope-from bmcgover@bmcgover-pc.cisco.com) Message-Id: <199912151802.NAA06965@bmcgover-pc.cisco.com> To: jeffrl@wantabe.com, veldy@visi.com Cc: stable@freebsd.org Subject: Re: mountd and rpc.statd won't run... Date: Wed, 15 Dec 1999 13:02:58 -0500 From: Brian McGovern Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Check to make sure you're lo0 interfaces are in fact set up properly. Up until recently (like the last couple of days), there were problems with "auto", dhcp and the like, and it wouldn't configure lo0 correctly. If lo0 is not properly configured, these daemons won't run. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 14: 0:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 63C6115063; Wed, 15 Dec 1999 14:00:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01120; Wed, 15 Dec 1999 14:03:02 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912152203.OAA01120@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Doug White Cc: Mike Smith , stable@FreeBSD.ORG Subject: Re: Bugfixed AMI MegaRAID driver for -stable available In-reply-to: Your message of "Tue, 14 Dec 1999 23:26:14 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Dec 1999 14:03:02 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 14 Dec 1999, Mike Smith wrote: > > > > > Due to a programming error, the previous release of the AMI MegaRAID > > driver for FreeBSD 3.x would not work with Enterprise 418 and 428 > > series controllers. This has been corrected, and the new driver is > > available at > > > > http://www.freebsd.org/~msmith/RAID/ami/amr-stable-991214.tar.gz > > Will this make it into 3.4? Obviously, no, since the code freeze was a long time ago. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 14:58:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ramstind.gtf.ol.no (ramstind.gtf.ol.no [128.39.174.16]) by hub.freebsd.org (Postfix) with ESMTP id 053131519B for ; Wed, 15 Dec 1999 14:58:28 -0800 (PST) (envelope-from trond@ramstind.gtf.ol.no) Received: from localhost (trond@localhost) by ramstind.gtf.ol.no (8.9.3/8.9.3) with ESMTP id XAA75063; Wed, 15 Dec 1999 23:58:20 +0100 (CET) (envelope-from trond@ramstind.gtf.ol.no) Date: Wed, 15 Dec 1999 23:58:20 +0100 (CET) From: Trond Endrestol To: SitePlus Web Services Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: /var full In-Reply-To: <3857AFC2.398188F0@siteplus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 15 Dec 1999, SitePlus Web Services wrote: > Hi all, > > I am new to this. My web server is beginning to get pretty busy and I > noticed today that /var was at 90% I moved and linked log and mail to > /usr/log and /usr/mail but it is still pretty full. When I set up the > server I allotted / and /var both 100megs. I suppose that was not > enough for /var. > > Any more suggestions, May I suggest enabling rotation of the web server log files. In /etc/newsyslog.conf add the following lines (I assume you are running Apache): /var/log/httpd-access.log 644 5 100 * Z /var/run/httpd.pid /var/log/httpd-error.log 644 5 100 * Z /var/run/httpd.pid This will give you 5 generations of the previous log files in addition to the current ones. Each rotation will be performed on the hour by newsyslog (engaged by cron) when the current log file exceeds 100 kB. Apache will also be notified with a SIGHUP and the PID is obtained from /var/run/httpd.pid. Take a look at the manpage for newsyslog(8) and look in /etc/newsyslog.conf for more details. You may need to adjust the lines for /etc/newsyslog.conf if you run a different web server. ---------------------------------------------------------------------- Trond Endrestøl | trond@gtf.ol.no Merkantilvegen 59HB7, | trond@ramstind.gtf.ol.no N-2815 GJØVIK, NORWAY |+47 61139424 || +47 63874242 Patron of The Art of Computer Programming| FreeBSD 3.3 & Pine 4.10 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 16:18: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail0.aimnet.ne.jp (mail0.aimnet.ne.jp [210.189.152.231]) by hub.freebsd.org (Postfix) with ESMTP id 0CE2915257 for ; Wed, 15 Dec 1999 16:17:59 -0800 (PST) (envelope-from yuzi-s@aimnet.ne.jp) Received: from suzucom ([210.189.152.253]) by mail0.aimnet.ne.jp (8.9.3/3.7W-aimnet) with SMTP id JAA04961 for ; Thu, 16 Dec 1999 09:17:56 +0900 (JST) Message-Id: <199912160017.JAA04961@mail0.aimnet.ne.jp> To: freebsd-stable@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Content-Transfer-Encoding: 7bit From: yuzi-s@aimnet.ne.jp Date: Thu, 16 Dec 1999 09:21:21 +0900 X-Mailer: WeMail32[1.52] ID:1A1049 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 18: 4: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 92AB214D35 for ; Wed, 15 Dec 1999 18:03:45 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:TEpjfCmt/0ImNgeA+YkFLC937dZMYGjQ@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id LAA04180; Thu, 16 Dec 1999 11:03:31 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id LAA24802; Thu, 16 Dec 1999 11:08:34 +0900 (JST) Message-Id: <199912160208.LAA24802@zodiac.mech.utsunomiya-u.ac.jp> To: Andrew Gordon Cc: Kazutaka YOKOTA , stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problem with psm0 In-reply-to: Your message of "Wed, 15 Dec 1999 01:10:52 GMT." References: Date: Thu, 16 Dec 1999 11:08:33 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >I just tried booting a 2.2.8-RELEASE CD in the problem machine, and it >didn't detect psm0 either, so this is a red herring. > >I then went looking for a hardware problem. I thought I was onto >something when I measured the +5V on-load voltage at the PS/2 >keyboard/mouse ports as only 4.71V: this motherboard seems to have a >high-resistance fuse. However, soldering a wire to bypass the fuse gave >me a solid 5.01V but no change in the behaviour. Wow, you didn't need to go that far... [...] >I assume you mean "options KBD_MAXWAIT=10" ? Oops, you are absolutely right. >I tried this, but it had no effect. I also tried other values, including: > >options KBD_MAXWAIT=10 >options KBD_RESETDELAY=1000 >options KBD_MAXRETRY=10 > >but again no obvious effect (other than a noticeable delay at that point >in the boot sequence). [...] >psm0: current command byte:0047 >kbdc: TEST_AUX_PORT status:0000 >kbdc: RESET_AUX return code:00fa The mouse has accepted the reset command. It should be sending reset status and device ID soon. >kbdc: RESET_AUX status:ffffffff But, we don't see any data coming from the mouse. As you said, this mouse is detected and working on another machine, we must assume the mouse does send something, and somehow it's disappeared.... >kbdc: DIAGNOSE status:0055 >kbdc: TEST_KBD_PORT status:0000 >psm0: failed to reset the aux device. >psm0 not found Would you try setting `flags 0x400' to the psm driver in the kernel configuration file? This flag will bypass mouse device reset. Boot the system again with `boot -v' and see if the mouse is detected. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 20:47:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id C08AE1546A; Wed, 15 Dec 1999 20:47:56 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:+SR5Di8+kUClgIlhhPXevfIhS+3qcA66@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id NAA11198; Thu, 16 Dec 1999 13:47:52 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id NAA00984; Thu, 16 Dec 1999 13:52:50 +0900 (JST) Message-Id: <199912160452.NAA00984@zodiac.mech.utsunomiya-u.ac.jp> To: jkh@freebsd.org, Brooks Davis Cc: stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: cvs commit: src/usr.sbin/moused moused.8 moused.c In-reply-to: Your message of "Wed, 15 Dec 1999 11:20:57 PST." <19991215112057.A16725@orion.ac.hmc.edu> References: <199912151258.EAA02374@freefall.freebsd.org> <19991215112057.A16725@orion.ac.hmc.edu> Date: Thu, 16 Dec 1999 13:52:44 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Should this last minutes MFC be allowed? On the one hand, I am slightly uneasy, because I don't think we have had sufficiently long test period. On the other hand, this fix affects only the 3 button emulation. Even if it breaks something, it SHOULD happen only when the user uses the 3 button emulation. Hmm, the thing is, I don't have a -STABLE box at hand for testing, and am not convinced yet that I haven't broken anything in -STABLE. Yes, I believe this fix is OK in -CURRENT, but,... I am not sure it is safe to MFC. Kazu >I've been running this patch on stable since it was first posted for >review. It moved my laptop's mouse from virtually useless to almost >always working. Any chance of a MFC for 3.4? > >Thanks, >Brooks > >On Wed, Dec 15, 1999 at 04:58:59AM -0800, Kazutaka YOKOTA wrote: >> yokota 1999/12/15 04:58:59 PST >> >> Modified files: >> usr.sbin/moused moused.8 moused.c >> Log: >> - Improve the three button emulation by introdusing a small state >> machine. The three-button emulation of moused has been somewhat >> difficult to use for many people. I hope this update fixes it. >> - Add a new option, -E, to set timeout value to detect two buttons >> are pressed down simulteneously. The default value for this timeout >> is 200msec. >> >> Revision Changes Path >> 1.25 +13 -2 src/usr.sbin/moused/moused.8 >> 1.34 +241 -44 src/usr.sbin/moused/moused.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 23: 3:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 104D2153B0 for ; Wed, 15 Dec 1999 23:03:42 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 11yUwv-0006QX-00 for freebsd-stable@freebsd.org; Wed, 15 Dec 1999 23:03:41 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Stable Subject: sb128 Message-Id: Date: Wed, 15 Dec 1999 23:03:41 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG am i correct that the soundblaster 128 is not supported? particularly in luigi's driver? not a problem, as i can use it in a billybox. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 15 23:33:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from 226-129.adsl2.avtel.net (226-129.adsl2.avtel.net [207.71.226.129]) by hub.freebsd.org (Postfix) with ESMTP id E0B2A14FA6 for ; Wed, 15 Dec 1999 23:33:24 -0800 (PST) (envelope-from ml@226-129.adsl2.avtel.net) Received: from localhost (ml@localhost) by 226-129.adsl2.avtel.net (8.9.3/8.9.3) with ESMTP id AAA09098; Thu, 16 Dec 1999 00:31:06 GMT (envelope-from ml@226-129.adsl2.avtel.net) Date: Thu, 16 Dec 1999 00:31:05 +0000 (GMT) From: Chad Page To: Randy Bush Cc: FreeBSD Stable Subject: Re: sb128 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 The soundblaster pci128 should have the es1370 chip which is supported. I don't know if creative toyed with the board enuff to break it though. - Chad, who wishes Creative hadn't bought Ensoniq. On Wed, 15 Dec 1999, Randy Bush wrote: > am i correct that the soundblaster 128 is not supported? particularly in > luigi's driver? > > not a problem, as i can use it in a billybox. > > randy > > > 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 16 2:24:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 54B5F15569; Thu, 16 Dec 1999 02:24:26 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id LAA17722; Thu, 16 Dec 1999 11:24:25 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <199912152203.OAA01120@mass.cdrom.com> References: <199912152203.OAA01120@mass.cdrom.com> Date: Thu, 16 Dec 1999 11:15:36 +0100 To: Mike Smith , Doug White From: Brad Knowles Subject: Re: Bugfixed AMI MegaRAID driver for -stable available Cc: Mike Smith , stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:03 PM -0800 1999/12/15, Mike Smith wrote: >> Will this make it into 3.4? > > Obviously, no, since the code freeze was a long time ago. What would the options be for documenting that this is now available, so that people with 3.4 and wanting to use AMI MegaRAID drivers could put them together? And can we assume that this will go into 3.5? -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 2:59:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cloudbase.sixforty.co.uk (cloudbase.sixforty.co.uk [194.207.180.10]) by hub.freebsd.org (Postfix) with ESMTP id 540AB1562E for ; Thu, 16 Dec 1999 02:59:20 -0800 (PST) (envelope-from l.farr@epcdirect.co.uk) Received: from monkey (pepe.sixforty.co.uk [194.207.180.202]) by cloudbase.sixforty.co.uk (8.9.3/8.8.7) with SMTP id KAA02380 for ; Thu, 16 Dec 1999 10:41:42 GMT Reply-To: From: "Lawrence Farr" To: Subject: Mylex DAC Driver Date: Thu, 16 Dec 1999 10:59:15 -0000 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have 3 or 4 Mylex controllers hanging around which I would like to use on some FreeBSD machines that I am going to build. I would prefer to boot from the RAID, as opposed to a single disc, which I know is not the best way of working but I need solidity of data over speed. Did the DAC driver make it into 3.4, or should I use CURRENT?. They will not be Mission Critical, but the data is. Thanks! Lawrence Farr EPC Direct T:01179666123 F:01179666111 M:07970780901 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 3:18:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 97B4F14EDD; Thu, 16 Dec 1999 03:17:52 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id DAA61897; Thu, 16 Dec 1999 03:17:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kazutaka YOKOTA Cc: jkh@freebsd.org, Brooks Davis , stable@freebsd.org Subject: Re: cvs commit: src/usr.sbin/moused moused.8 moused.c In-reply-to: Your message of "Thu, 16 Dec 1999 13:52:44 +0900." <199912160452.NAA00984@zodiac.mech.utsunomiya-u.ac.jp> Date: Thu, 16 Dec 1999 03:17:26 -0800 Message-ID: <61892.945343046@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, it sounds like it has already had the benefit of 3rd party testing in 3.x-stable? If you're confident enough, I'm willing to say yes. - Jordan > Should this last minutes MFC be allowed? > > On the one hand, I am slightly uneasy, because I don't think we have > had sufficiently long test period. > > On the other hand, this fix affects only the 3 button emulation. Even > if it breaks something, it SHOULD happen only when the user uses the 3 > button emulation. > > Hmm, the thing is, I don't have a -STABLE box at hand for testing, and > am not convinced yet that I haven't broken anything in -STABLE. Yes, > I believe this fix is OK in -CURRENT, but,... > > I am not sure it is safe to MFC. > > Kazu > > >I've been running this patch on stable since it was first posted for > >review. It moved my laptop's mouse from virtually useless to almost > >always working. Any chance of a MFC for 3.4? > > > >Thanks, > >Brooks > > > >On Wed, Dec 15, 1999 at 04:58:59AM -0800, Kazutaka YOKOTA wrote: > >> yokota 1999/12/15 04:58:59 PST > >> > >> Modified files: > >> usr.sbin/moused moused.8 moused.c > >> Log: > >> - Improve the three button emulation by introdusing a small state > >> machine. The three-button emulation of moused has been somewhat > >> difficult to use for many people. I hope this update fixes it. > >> - Add a new option, -E, to set timeout value to detect two buttons > >> are pressed down simulteneously. The default value for this timeout > >> is 200msec. > >> > >> Revision Changes Path > >> 1.25 +13 -2 src/usr.sbin/moused/moused.8 > >> 1.34 +241 -44 src/usr.sbin/moused/moused.c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 3:59:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 2513F155D6 for ; Thu, 16 Dec 1999 03:59:37 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id MAA04688; Thu, 16 Dec 1999 12:59:30 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 16 Dec 1999 12:58:35 +0100 To: , From: Brad Knowles Subject: Re: Mylex DAC Driver Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:59 AM +0000 1999/12/16, Lawrence Farr wrote: > I have 3 or 4 Mylex controllers hanging around which I would like to use on > some FreeBSD machines that I am going to build. I would prefer to boot from > the RAID, as opposed to a single disc, which I know is not the best way of > working but I need solidity of data over speed. > Did the DAC driver make it into 3.4, or should I use CURRENT?. They will not > be Mission Critical, but the data is. You'd have to talk to Mike, but it's my understanding that the drivers are still under development, and not all the Mylex controllers are covered (the older ones are, but not the newer ones -- of course, I don't believe you can buy the older ones anymore, unless you buy them second-hand). Personally, I'd put this in the same category as vinum -- safe enough to use in certain modes (in the case of vinum, combinations of striping and mirroring, but not RAID-5), but not yet safe enough to use across the board for everything. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 4: 2:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 0276514E7D for ; Thu, 16 Dec 1999 04:02:16 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id NAA05129; Thu, 16 Dec 1999 13:02:14 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: References: Date: Thu, 16 Dec 1999 13:01:55 +0100 To: , From: Brad Knowles Subject: Re: Mylex DAC Driver Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ Sorry about the re-transmit -- I hit "send", then thought of one more thing, and couldn't stop it in time. Sigh.... I hate single-processing boxes. -BK ] At 10:59 AM +0000 1999/12/16, Lawrence Farr wrote: > I have 3 or 4 Mylex controllers hanging around which I would like to use on > some FreeBSD machines that I am going to build. I would prefer to boot from > the RAID, as opposed to a single disc, which I know is not the best way of > working but I need solidity of data over speed. > Did the DAC driver make it into 3.4, or should I use CURRENT?. They will not > be Mission Critical, but the data is. You'd have to talk to Mike, but it's my understanding that the drivers are still under development, and not all the Mylex controllers are covered (the older ones are, but not the newer ones -- of course, I don't believe you can buy the older ones anymore, unless you buy them second-hand). Personally, I'd put this in the same category as vinum -- safe enough to use in certain modes (in the case of vinum, combinations of striping and mirroring, but not RAID-5), but not yet safe enough to use across the board for everything. I'd also put this in the same category of using a -CURRENT box for production (i.e., "Mission Critical") purposes. Not recommended, but if you're willing to take the risk, then I guess you can do whatever you like. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 4:44:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sand2.sentex.ca (sand2.sentex.ca [209.167.248.3]) by hub.freebsd.org (Postfix) with ESMTP id 27D5C14D0A for ; Thu, 16 Dec 1999 04:44:46 -0800 (PST) (envelope-from mike@sentex.net) Received: from gravel (ospf-mdt.sentex.net [205.211.164.81]) by sand2.sentex.ca (8.8.8/8.8.8) with SMTP id HAA14535; Thu, 16 Dec 1999 07:45:15 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <4.1.19991216074325.04641db0@granite.sentex.ca> X-Sender: mdtancsa@granite.sentex.ca X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Thu, 16 Dec 1999 07:44:35 -0500 To: , From: Mike Tancsa Subject: Re: Mylex DAC Driver In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:59 AM 12/16/99 , Lawrence Farr wrote: >I have 3 or 4 Mylex controllers hanging around which I would like to use on >some FreeBSD machines that I am going to build. I would prefer to boot from Mike Smith is developing the drivers. See http://www.freebsd.org/~msmith/RAID for patches against STABLE. They are already in the source tree for CURRENT. ---Mike ********************************************************************** Mike Tancsa * mike@sentex.net Sentex Communications Corp, * http://www.sentex.net/mike Cambridge, Ontario * 519 651 3400 Canada * To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 8: 1:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.bna.bellsouth.net (mail2.bna.bellsouth.net [205.152.150.14]) by hub.freebsd.org (Postfix) with ESMTP id 0FB6114DFB for ; Thu, 16 Dec 1999 08:01:11 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-216-78-3-118.jan.bellsouth.net [216.78.3.118]) by mail2.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id KAA02096 for ; Thu, 16 Dec 1999 10:49:08 -0500 (EST) Message-ID: <38590CBB.49971208@siteplus.com> Date: Thu, 16 Dec 1999 11:00:59 -0500 From: Jim Weeks X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i586) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: /var full...Apology Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings, Season and otherwise. This is not actually a stable issue either, but I feel compelled to apologize to those of you that saw my post yesterday. I received a lot of help as well as a well deserved criticism. I agree that the post was not appropriate, and in the future I WILL do better. I believe in FreeBSD-stable and especially appreciate the efforts of all those contributing to this list. It is an invaluable resource. Thanks again, Jim Weeks jim@siteplus.com http://siteplus.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 16 9:36: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from modemcable156.106-200-24.mtl.mc.videotron.net (modemcable126.102-200-24.mtl.mc.videotron.net [24.200.102.126]) by hub.freebsd.org (Postfix) with SMTP id 1D87A1562D for ; Thu, 16 Dec 1999 09:35:59 -0800 (PST) (envelope-from patrick@mindstep.com) Received: (qmail 52776 invoked from network); 16 Dec 1999 17:35:56 -0000 Received: from patrak.local.mindstep.com (HELO patrak) (192.168.10.4) by jacuzzi.local.mindstep.com with SMTP; 16 Dec 1999 17:35:56 -0000 Message-ID: <00c501bf47ec$01fee840$040aa8c0@local.mindstep.com> From: "Patrick Bihan-Faou" To: Cc: Subject: Status of the netatalk stack Date: Thu, 16 Dec 1999 12:35:55 -0500 Organization: MindStep Corporation MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was looking at the netatalk package and the appletalk support in the kernel source code and I realized that they are based on the same code originally (the code from netatalk). The kernel code however is quite out of date from what can be found in the netatalk-asun package. I was wondering if anybody is planning on integrating the latest changes ? If not is it something that I should undertake ? Are there any major reasons why the code in freebsd should be left alone ? PS. I cross-posted in current and stable because it affects both stream in the same way, however I guess the discussion should be kept in "current", so please try to reply to the correct address. Thanks. Patrick. -- www.mindstep.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 16 10:31:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pasteur.EECS.Berkeley.EDU (pasteur.EECS.Berkeley.EDU [128.32.138.75]) by hub.freebsd.org (Postfix) with ESMTP id 3E08E15665 for ; Thu, 16 Dec 1999 10:31:19 -0800 (PST) (envelope-from sowings@pasteur.EECS.Berkeley.EDU) Received: from mamba.CS.Berkeley.EDU (mamba.CS.Berkeley.EDU [128.32.42.159]) by pasteur.EECS.Berkeley.EDU (8.9.3+Sun/8.9.1) with ESMTP id KAA28558; Thu, 16 Dec 1999 10:31:18 -0800 (PST) Received: from mamba.CS.Berkeley.EDU (localhost [127.0.0.1]) by mamba.CS.Berkeley.EDU (8.9.3+Sun/8.9.1) with ESMTP id KAA16276; Thu, 16 Dec 1999 10:31:18 -0800 (PST) Message-Id: <199912161831.KAA16276@mamba.CS.Berkeley.EDU> To: Chad Page Cc: freebsd-stable@freebsd.org Subject: Re: sb128 In-Reply-To: Your message of "Thu, 16 Dec 1999 00:31:05 GMT." Date: Thu, 16 Dec 1999 10:31:18 -0800 From: Sanford Owings Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The soundblaster pci128 should have the es1370 chip which is > supported. I don't know if creative toyed with the board enuff to break > it though. Newer versions of the card have the es1371 chipset, which is also supported under FBSD (though I'm running -current). Be aware, though, that there are a few of these cards out there with a codec that FBSD still doesn't understand, but support is coming. -- Sanford Owings EECS Instructional Group Staff University of California at Berkeley To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 12:29: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id C670314FDA; Thu, 16 Dec 1999 12:29:02 -0800 (PST) (envelope-from brdavis@orion.ac.hmc.edu) Received: (from brdavis@localhost) by orion.ac.hmc.edu (8.8.8/8.8.8) id MAA04772; Thu, 16 Dec 1999 12:28:54 -0800 (PST) Date: Thu, 16 Dec 1999 12:28:54 -0800 From: Brooks Davis To: "Jordan K. Hubbard" Cc: Kazutaka YOKOTA , jkh@freebsd.org, stable@freebsd.org Subject: Re: cvs commit: src/usr.sbin/moused moused.8 moused.c Message-ID: <19991216122854.B10717@orion.ac.hmc.edu> References: <199912160452.NAA00984@zodiac.mech.utsunomiya-u.ac.jp> <61892.945343046@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: <61892.945343046@zippy.cdrom.com>; from jkh@zippy.cdrom.com on Thu, Dec 16, 1999 at 03:17:26AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I said, I've been running it for a few weeks. I've noticed no difference when used with my MS wheelie mouse and dramatic improvement when trying to paste with the laptop mouse buttons. My HP OmniBook 4150's builtin touchpad practialy didn't work until I applied this patch. Now it works correctly pretty much every time. I'd like to see it comitted for the release, but I'd certaintly understand if it wasn't. -- Brooks On Thu, Dec 16, 1999 at 03:17:26AM -0800, Jordan K. Hubbard wrote: > Well, it sounds like it has already had the benefit of 3rd party > testing in 3.x-stable? If you're confident enough, I'm willing > to say yes. > > - Jordan > > > Should this last minutes MFC be allowed? > > > > On the one hand, I am slightly uneasy, because I don't think we have > > had sufficiently long test period. > > > > On the other hand, this fix affects only the 3 button emulation. Even > > if it breaks something, it SHOULD happen only when the user uses the 3 > > button emulation. > > > > Hmm, the thing is, I don't have a -STABLE box at hand for testing, and > > am not convinced yet that I haven't broken anything in -STABLE. Yes, > > I believe this fix is OK in -CURRENT, but,... > > > > I am not sure it is safe to MFC. > > > > Kazu > > > > >I've been running this patch on stable since it was first posted for > > >review. It moved my laptop's mouse from virtually useless to almost > > >always working. Any chance of a MFC for 3.4? > > > > > >Thanks, > > >Brooks > > > > > >On Wed, Dec 15, 1999 at 04:58:59AM -0800, Kazutaka YOKOTA wrote: > > >> yokota 1999/12/15 04:58:59 PST > > >> > > >> Modified files: > > >> usr.sbin/moused moused.8 moused.c > > >> Log: > > >> - Improve the three button emulation by introdusing a small state > > >> machine. The three-button emulation of moused has been somewhat > > >> difficult to use for many people. I hope this update fixes it. > > >> - Add a new option, -E, to set timeout value to detect two buttons > > >> are pressed down simulteneously. The default value for this timeout > > >> is 200msec. > > >> > > >> Revision Changes Path > > >> 1.25 +13 -2 src/usr.sbin/moused/moused.8 > > >> 1.34 +241 -44 src/usr.sbin/moused/moused.c -- "Those who desire to give up freedom in order to gain security, will not have, nor do they deserve, either one" --Thomas Jefferson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 12:46:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 1C557156B2 for ; Thu, 16 Dec 1999 12:46:37 -0800 (PST) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-u1-29.hitter.net [207.192.78.29]) by pawn.primelocation.net (Postfix) with ESMTP id 22C689B4D for ; Thu, 16 Dec 1999 15:46:29 -0500 (EST) Date: Thu, 16 Dec 1999 15:46:28 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: stable@freebsd.org Subject: smb/intpm-related panic 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 Today I was working on one of my projects, lmmon (http://www.fxp.org/~jedgar/lmmon-0.61.tar.gz). Normally I run wmlmmon in /dev/io mode so I had not compiled 'controller intpm' support in the kernel. During testing of lmmon, I found that, without intpm support, lmmon causes a panic (running as root). Is there a way to test if intpm is enabled before attempting to use it through /dev/smb0 ? The following items are in the kernel config: controller smbus0 device smb0 at smbus? controller iicbus0 controller iicbb0 device ic0 at iicbus? device iic0 at iicbus? device iicsmb0 at iicbus? device bktr0 Most of the above is necessary for my Brooktree card. Backtrace of the panic is as follows: Script started on Thu Dec 16 15:21:53 1999 root@earth:~# gdb -k /sys/compile/EARTH/kernel.debug /var/crash/vmcore.0 GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... IdlePTD 3166208 initial pcb at 288e88 panicstr: from debugger panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x38 fault code = supervisor read, page not present instruction pointer = 0x8:0xc015920e stack pointer = 0x10:0xc77e1ca8 frame pointer = 0x10:0xc77e1ca8 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = 953 (lmmon) interrupt mask = panic: from debugger panic: from debugger dumping to dev 20401, offset 786432 dump 128 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) bt #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xc0153099 in panic (fmt=0xc024aefc "from debugger") at ../../kern/kern_shutdown.c:446 #2 0xc012c0d1 in db_panic (addr=-1072328178, have_addr=0, count=-1, modif=0xc77e1b2c "") at ../../ddb/db_command.c:432 #3 0xc012c071 in db_command (last_cmdp=0xc026d54c, cmd_table=0xc026d3ac, aux_cmd_tablep=0xc0286adc) at ../../ddb/db_command.c:332 #4 0xc012c136 in db_command_loop () at ../../ddb/db_command.c:454 #5 0xc012e5af in db_trap (type=12, code=0) at ../../ddb/db_trap.c:71 #6 0xc0215b6e in kdb_trap (type=12, code=0, regs=0xc77e1c6c) at ../../i386/i386/db_interface.c:157 #7 0xc02208e8 in trap_fatal (frame=0xc77e1c6c, eva=56) at ../../i386/i386/trap.c:937 #8 0xc02205c7 in trap_pfault (frame=0xc77e1c6c, usermode=0, eva=56) at ../../i386/i386/trap.c:835 #9 0xc0220226 in trap (frame={tf_es = -1071710192, tf_ds = -948699120, tf_edi = 0, tf_esi = -1059494272, tf_ebp = -948036440, tf_isp = -948036460, tf_ebx = -1059500352, tf_edx = -948036268, tf_ecx = 9, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1072328178, tf_cs = 8, tf_eflags = 66118, tf_esp = -948036416, tf_ss = -1072444101}) at ../../i386/i386/trap.c:437 #10 0xc015920e in device_get_softc (dev=0x0) at ../../kern/subr_bus.c:735 #11 0xc013cd3b in smbus_request_bus (bus=0x0, dev=0xc0d96680, how=3) at ../../dev/smbus/smbconf.c:131 ---Type to continue, or q to quit--- #12 0xc01d9898 in bti2c_iic_callback (dev=0xc0d96680, index=1, data=0xc77e1d54) at ../../dev/bktr/bktr_i2c.c:249 #13 0xc013d7b8 in IICBB_CALLBACK (dev=0xc0d96680, index=1, data=0xc77e1d54 "\003") at iicbb_if.c:24 #14 0xc013d5c6 in iicbb_callback (dev=0xc0d96640, index=1, data=0xc77e1d54 "\003") at ../../dev/iicbus/iicbb.c:236 #15 0xc013e034 in IICBUS_CALLBACK (dev=0xc0d96640, index=1, data=0xc77e1d54 "\003") at iicbus_if.c:34 #16 0xc013e239 in iicbus_request_bus (bus=0xc0d96600, dev=0xc0d965c0, how=3) at ../../dev/iicbus/iiconf.c:108 #17 0xc013da21 in iicsmb_callback (dev=0xc0d965c0, index=1, data=0xc77e1dac "\003") at ../../dev/iicbus/iicsmb.c:252 #18 0xc013c950 in SMBUS_CALLBACK (dev=0xc0d965c0, index=1, data=0xc77e1dac "\003") at smbus_if.c:34 #19 0xc013cd55 in smbus_request_bus (bus=0xc0d96540, dev=0xc0d96500, how=3) at ../../dev/smbus/smbconf.c:136 #20 0xc013d037 in smbioctl (dev=27136, cmd=2148821255, data=0xc77e1ee0 "G", flags=3, p=0xc774b520) at ../../dev/smbus/smb.c:188 #21 0xc0183673 in spec_ioctl (ap=0xc77e1e1c) at ../../miscfs/specfs/spec_vnops.c:424 #22 0xc0182f85 in spec_vnoperate (ap=0xc77e1e1c) at ../../miscfs/specfs/spec_vnops.c:129 #23 0xc01f6ea9 in ufs_vnoperatespec (ap=0xc77e1e1c) at ../../ufs/ufs/ufs_vnops.c:2318 ---Type to continue, or q to quit--- #24 0xc017ddf1 in vn_ioctl (fp=0xc0e20ec0, com=2148821255, data=0xc77e1ee0 "G", p=0xc774b520) at vnode_if.h:395 #25 0xc015e268 in ioctl (p=0xc774b520, uap=0xc77e1f94) at ../../kern/sys_generic.c:564 #26 0xc0220b57 in syscall (frame={tf_es = 39, tf_ds = 39, tf_edi = -1077945236, tf_esi = 134516392, tf_ebp = -1077945388, tf_isp = -948035612, tf_ebx = -1077945408, tf_edx = -1077945409, tf_ecx = 0, tf_eax = 54, tf_trapno = 12, tf_err = 2, tf_eip = 671754492, tf_cs = 31, tf_eflags = 582, tf_esp = -1077945444, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #27 0xc02164bc in Xint0x80_syscall () #28 0x80489f5 in ?? () #29 0x8048789 in ?? () (kgdb) root@earth:~# Script done on Thu Dec 16 15:22:12 1999 ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@freebsd.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 13: 5:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 0641115697; Thu, 16 Dec 1999 13:05:47 -0800 (PST) (envelope-from julian@whistle.com) Received: from current1.whiste.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id NAA27445; Thu, 16 Dec 1999 13:05:37 -0800 (PST) Date: Thu, 16 Dec 1999 13:05:36 -0800 (PST) From: Julian Elischer To: Patrick Bihan-Faou Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: Status of the netatalk stack In-Reply-To: <00c501bf47ec$01fee840$040aa8c0@local.mindstep.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 the kernel code for appletalk is 'out of date' but it is also somewhat modified.. If you want to work with it, let me know and I can help as I did the original integration into our tree, Julian On Thu, 16 Dec 1999, Patrick Bihan-Faou wrote: > Hi, > > > I was looking at the netatalk package and the appletalk support in the > kernel source code and I realized that they are based on the same code > originally (the code from netatalk). > > The kernel code however is quite out of date from what can be found in the > netatalk-asun package. I was wondering if anybody is planning on integrating > the latest changes ? If not is it something that I should undertake ? Are > there any major reasons why the code in freebsd should be left alone ? > > > PS. I cross-posted in current and stable because it affects both stream in > the same way, however I guess the discussion should be kept in "current", so > please try to reply to the correct address. Thanks. > > > > Patrick. > > -- > www.mindstep.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 15:12:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 8EFBE14FC4 for ; Thu, 16 Dec 1999 15:12:35 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id 6B6D224D55 for ; Thu, 16 Dec 1999 18:12:25 -0500 (EST) Received: by osaka.louisville.edu (Postfix, from userid 15) id 5D2BA18605; Thu, 16 Dec 1999 18:12:25 -0500 (EST) Date: Thu, 16 Dec 1999 18:12:25 -0500 From: Keith Stevenson To: freebsd-stable@freebsd.org Subject: Softupdates panic in 3.3-STABLE Message-ID: <19991216181225.B10015@osaka.louisville.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is from an older STABLE, but I haven't seen any softupdates commits in a while. # uname -a FreeBSD erouter0.it-datacntr.louisville.edu 3.3-STABLE FreeBSD 3.3-STABLE #1: Mon Sep 27 14:32:45 EDT 1999 syskts@erouter0.it-datacntr.louisville.edu:/usr/src/sys/compile/EROUTER i386 # gdb -k GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd". (kgdb) symbol file /kernel.debug Reading symbols from file...(no debugging symbols found)...done. Reading symbols from /kernel.debug...done. (kgdb) exec-file /var/crash/kernel.0 (kgdb) core-file /var/crash/vmcore.0 IdlePTD 2617344 initial pcb at 219920 panicstr: softdep_disk_write_complete: lock is held panic messages: --- panic: softdep_fsync: pending ops syncing disks... panic: softdep_disk_write_complete: lock is held dumping to dev 20001, offset 4096 dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 --- #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) where #0 boot (howto=260) at ../../kern/kern_shutdown.c:285 #1 0xc0145e0c in at_shutdown ( function=0xc01f91b2 <__set_sysctl__debug_sym_sysctl___debug_rush_requests+2002>, arg=0xc3418270, queue=-1062528000) at ../../kern/kern_shutdown.c:446 #2 0xc01a1ef8 in softdep_disk_write_complete (bp=0xc3418270) at ../../ufs/ffs/ffs_softdep.c:2898 #3 0xc0165a36 in biodone (bp=0xc3418270) at ../../kern/vfs_bio.c:1925 #4 0xc01e3fde in wdintr (unitnum=0x0) at ../../i386/isa/wd.c:1275 #5 0xc01cb39a in vec14 () #6 0xc0165047 in getblk (vp=0xc61d3540, blkno=1245280, size=8192, slpflag=0, slptimeo=0) at ../../kern/vfs_bio.c:1437 #7 0xc01639c5 in bread (vp=0xc61d3540, blkno=1245280, size=8192, cred=0x0, bpp=0xc64d9de0) at ../../kern/vfs_bio.c:282 #8 0xc019dfac in ffs_update (vp=0xc642b1c0, waitfor=0) at ../../ufs/ffs/ffs_inode.c:98 #9 0xc01a7436 in ffs_fsync (ap=0xc64d9e68) at ../../ufs/ffs/ffs_vnops.c:258 #10 0xc01a580f in ffs_sync (mp=0xc0b06a00, waitfor=2, cred=0xc0752300, p=0xc022d468) at vnode_if.h:499 #11 0xc016cb8b in sync (p=0xc022d468, uap=0x0) at ../../kern/vfs_syscalls.c:549 #12 0xc01459cd in boot (howto=256) at ../../kern/kern_shutdown.c:203 #13 0xc0145e0c in at_shutdown ( function=0xc01f9522 <__set_sysctl__debug_sym_sysctl___debug_rush_requests+2882>, arg=0xc6324600, queue=0) at ../../kern/kern_shutdown.c:446 #14 0xc01a2baa in softdep_fsync (vp=0xc6324600) at ../../ufs/ffs/ffs_softdep.c:3567 #15 0xc016f462 in fsync (p=0xc6484c80, uap=0xc64d9f94) at ../../kern/vfs_syscalls.c:2449 #16 0xc01d3a73 in syscall (frame={tf_es = 39, tf_ds = -1078001625, tf_edi = -1077946040, tf_esi = 0, tf_ebp = -1077946280, tf_isp = -967991324, tf_ebx = 134684296, tf_edx = 36, tf_ecx = 36, tf_eax = 95, tf_trapno = 7, tf_err = 2, tf_eip = 671813520, tf_cs = 31, tf_eflags = 598, tf_esp = -1077946296, tf_ss = 39}) at ../../i386/i386/trap.c:1100 #17 0xc01c9fac in Xint0x80_syscall () #18 0x804e9d0 in ?? () #19 0x8049f65 in ?? () #20 0x804be69 in ?? () #21 0x804bf7a in ?? () #22 0x8052ba9 in ?? () #23 0x804c6eb in ?? () #24 0x804a276 in ?? () #25 0x8049d65 in ?? () The system in question is an email hub. Softupdates are enabled on /usr, /var, and /var/log. This has only happened once, but I thought that one of the filesystem gurus would like to know. Here's the kernel config for your reference: ##################### # Basic Configuration ##################### machine "i386" ident erouter maxusers 50 options FAILSAFE #Be conservative config kernel root on wd0 ############# # CPU Options ############# cpu "I686_CPU" options "NO_F00F_HACK" ####################### # Compatibility Options ####################### options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SYSVSHM options SYSVSEM options SYSVMSG options "MD5" ############## # Misc Options ############## options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor #################### # Networking Options #################### options INET #InterNETworking pseudo-device loop #Loopback device (mandatory) pseudo-device ether #Generic ethernet pseudo-device bpfilter 2 #Berkeley Packet Filter #################### # Filesystem Options #################### options FFS #Berkeley Fast Filesystem #options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options MFS #Memory filesystem (ramdisk) options SOFTUPDATES #Softupdates support ############## # SCSI Devices ############## controller scbus0 device da0 device sa0 device cd0 ############## # Misc Devices ############## pseudo-device pty 16 pseudo-device gzip # Exec gzipped a.out's (mandatory) pseudo-device snp 1 # Snoop device ######################## # Hardware Configuration ######################## controller isa0 controller pci0 # Default ANSI console (looks like SCO) device sc0 at isa? tty options MAXCONS=16 #number of virtual consoles options SC_HISTORY_SIZE=200 #history buffer size options SC_DISABLE_REBOOT #Disable -- controller atkbdc0 at isa? port IO_KBD tty # AT keyboard controller device atkbd0 at isa? tty irq1 # AT keyboard device vga0 at isa? port ? conflicts # VGA driver pseudo-device splash # Required by screen savers # Mandatory, don't remove device npx0 at isa? port "IO_NPX" flags 0x1 irq 13 vector npxintr # SCSI Controller controller ahc0 #Adaptech 2940UW # IDE Controllers options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr disk wd2 at wdc1 drive 0 # Floppy controller controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # Parallel Port device ppc0 at isa? port? net irq 7 controller ppbus0 device lpt0 at ppbus? # Serial Ports device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr # Network interfaces device xl0 # 3Com 3C905 Thanks for taking a look! Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 15:33:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kleopatra.acc.umu.se (kleopatra.acc.umu.se [130.239.18.150]) by hub.freebsd.org (Postfix) with ESMTP id 2209C14F2D for ; Thu, 16 Dec 1999 15:33:24 -0800 (PST) (envelope-from saska@acc.umu.se) Received: from shaka.acc.umu.se (saska@shaka-fddi.acc.umu.se [192.168.18.148]) by kleopatra.acc.umu.se (8.9.3/8.9.3) with ESMTP id AAA40488; Fri, 17 Dec 1999 00:33:09 +0100 Received: (from saska@localhost) by shaka.acc.umu.se (8.9.3/8.9.3) id AAA26373; Fri, 17 Dec 1999 00:33:08 +0100 (MET) Date: Fri, 17 Dec 1999 00:33:08 +0100 From: Markus Holmberg To: freebsd-stable@freebsd.org Cc: jdp@polstra.com Subject: bringing dlopen() fix from -CURRENT to -STABLE? (mozilla blocker) Message-ID: <19991217003307.A26322@shaka.acc.umu.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello.. A while ago a bug was revealed (and fixed) regarding dlopen() and symbols behaviour in FreeBSD when loading shared libraries. This was (as far as I've understood it) fixed in -CURRENT, but never brought into -STABLE. This bug is a blocker for Mozilla on FreeBSD 3.x (which is the current FreeBSD stable branch). Mozilla simply won't run without it. Is there by any chance that someone, pretty pretty please with sugar on top, would bring this fix back into -STABLE? This FreeBSD PR has all info needed: http://www.freebsd.org/cgi/query-pr.cgi?pr=12438 This bug filed in Bugzilla describes why Mozilla depends on this fix: http://bugzilla.mozilla.org/show_bug.cgi?id=14676 I'm volunteering to help with my limited skills! Markus -- Markus Holmberg | Give me UNIX or give me a typewriter. saska@acc.umu.se | http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 15:39:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id AB72314D2C for ; Thu, 16 Dec 1999 15:39:16 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA01846; Thu, 16 Dec 1999 15:42:37 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912162342.PAA01846@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brad Knowles Cc: stable@FreeBSD.ORG Subject: Re: Bugfixed AMI MegaRAID driver for -stable available In-reply-to: Your message of "Thu, 16 Dec 1999 11:15:36 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Dec 1999 15:42:37 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 2:03 PM -0800 1999/12/15, Mike Smith wrote: > > >> Will this make it into 3.4? > > > > Obviously, no, since the code freeze was a long time ago. > > What would the options be for documenting that this is now > available, so that people with 3.4 and wanting to use AMI MegaRAID > drivers could put them together? And can we assume that this will go > into 3.5? So far I think I'm content to post occasionally to the -stable list, although if someone were to update whatever other resources there are out there that point to -stable stuff, that would be OK with me. I wouldn't want to assume anything about 3.5 just yet. Making the Mylex and AMI controllers bootable there is feasible but just a bit icky. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 15:42: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 7971515643 for ; Thu, 16 Dec 1999 15:41:08 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA01906; Thu, 16 Dec 1999 15:44:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912162344.PAA01906@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: l.farr@epcdirect.co.uk Cc: stable@FreeBSD.ORG Subject: Re: Mylex DAC Driver In-reply-to: Your message of "Thu, 16 Dec 1999 10:59:15 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Dec 1999 15:44:29 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You will need a 4.x snapshot, or some patience. > I have 3 or 4 Mylex controllers hanging around which I would like to use on > some FreeBSD machines that I am going to build. I would prefer to boot from > the RAID, as opposed to a single disc, which I know is not the best way of > working but I need solidity of data over speed. > Did the DAC driver make it into 3.4, or should I use CURRENT?. They will not > be Mission Critical, but the data is. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 15:42:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 23D6215641 for ; Thu, 16 Dec 1999 15:42:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA01922; Thu, 16 Dec 1999 15:45:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912162345.PAA01922@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Brad Knowles Cc: l.farr@epcdirect.co.uk, stable@FreeBSD.ORG Subject: Re: Mylex DAC Driver In-reply-to: Your message of "Thu, 16 Dec 1999 12:58:35 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Dec 1999 15:45:40 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > You'd have to talk to Mike, but it's my understanding that the > drivers are still under development, and not all the Mylex > controllers are covered (the older ones are, but not the newer ones > -- of course, I don't believe you can buy the older ones anymore, > unless you buy them second-hand). -current supports all of the controllers that Mylex are currently selling. I'll be updating the -stable patchkit shortly. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 15:55: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id 1C4891517B for ; Thu, 16 Dec 1999 15:54:59 -0800 (PST) (envelope-from arg@arg1.demon.co.uk) Received: from localhost (arg@localhost) by arg1.demon.co.uk (8.8.8/8.8.8) with ESMTP id XAA03041; Thu, 16 Dec 1999 23:54:23 GMT (envelope-from arg@arg1.demon.co.uk) Date: Thu, 16 Dec 1999 23:54:23 +0000 (GMT) From: Andrew Gordon X-Sender: arg@server.arg.sj.co.uk To: Kazutaka YOKOTA Cc: stable@freebsd.org Subject: Re: Problem with psm0 In-Reply-To: <199912160208.LAA24802@zodiac.mech.utsunomiya-u.ac.jp> 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, 16 Dec 1999, Kazutaka YOKOTA wrote: > > > Would you try setting `flags 0x400' to the psm driver in the kernel > configuration file? This flag will bypass mouse device reset. > Boot the system again with `boot -v' and see if the mouse is detected. Success at last! With "flags 0x400" in the config, I get: Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 psm: status ffffffff c0262384 c02e3f68 psm: status ffffffff c0b32800 c02e3f48 psm: status ffffffff c0b32800 c02e3f48 psm: status ffffffff c0b32800 c02e3f48 psm: data ffffffff c0262384 c02e3f68 psm0: failed to get data. psm0: failed to get status. psm0 irq 12 flags 0x400 on isa psm0: model Generic PS/2 mouse, device ID 255-ffffffff, 2 buttons psm0: config:00000400, flags:00000000, packet size:3 psm0: syncmask:00, syncbits:00 sio0: irq maps: 0x1 0x11 0x1 0x1 And the mouse then works! I also discovered that, with the old kernel, I could boot the system with the 'good' mouse, and then unplug that mouse and plug in the 'bad' one. Often it would fail with "psmintr: out of sync", but sometimes it would then work OK. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 19:55:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id F3472150CF for ; Thu, 16 Dec 1999 19:55:26 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:RaVvwH0d00dOzrBSU5OaN25fytJgQnpY@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id MAA12481; Fri, 17 Dec 1999 12:55:22 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id NAA11490; Fri, 17 Dec 1999 13:00:25 +0900 (JST) Message-Id: <199912170400.NAA11490@zodiac.mech.utsunomiya-u.ac.jp> To: Andrew Gordon Cc: stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: Problem with psm0 In-reply-to: Your message of "Thu, 16 Dec 1999 23:54:23 GMT." References: Date: Fri, 17 Dec 1999 13:00:25 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Success at last! With "flags 0x400" in the config, I get: [...] >psm: status ffffffff c0262384 c02e3f68 >psm: status ffffffff c0b32800 c02e3f48 >psm: status ffffffff c0b32800 c02e3f48 >psm: status ffffffff c0b32800 c02e3f48 >psm: data ffffffff c0262384 c02e3f68 >psm0: failed to get data. >psm0: failed to get status. This is still a worring situation. The above lines indicate that we are not getting anything when the mouse is expected to send us something. As you said that the same mouse is correctly recognized and works when connected to another motherboard, we assume the mouse is not faulty at all and should be sending back data. >psm0 irq 12 flags 0x400 on isa >psm0: model Generic PS/2 mouse, device ID 255-ffffffff, 2 buttons >psm0: config:00000400, flags:00000000, packet size:3 >psm0: syncmask:00, syncbits:00 >sio0: irq maps: 0x1 0x11 0x1 0x1 > >And the mouse then works! So long as you don't experience any visible problem, we have to leave it this way. But, when you see anything strange, please report problems again. For the time being, I cannot think of a way to invesitgate this strange problem further. Kazu >I also discovered that, with the old kernel, I could boot the system with >the 'good' mouse, and then unplug that mouse and plug in the 'bad' >one. Often it would fail with "psmintr: out of sync", but sometimes it >would then work OK. Um, in general, it is not recommended to unplug and replug the AT keyboard or the PS/2 mouse while the system is running. The mouse interface and the keyboard controller may be electrically "fried". I have a couple of friends who learned this lessen in a hard way. Notebook computers and recent motherboards MAY be resistant to this problem, but you had better not do it unless you are sure that your system can stand it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 16 21:36:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 50E8E14A24 for ; Thu, 16 Dec 1999 21:36:24 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id VAA16906; Thu, 16 Dec 1999 21:36:23 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id VAA21304; Thu, 16 Dec 1999 21:36:23 -0800 (PST) (envelope-from jdp@polstra.com) Date: Thu, 16 Dec 1999 21:36:23 -0800 (PST) Message-Id: <199912170536.VAA21304@vashon.polstra.com> To: saska@acc.umu.se Subject: Re: bringing dlopen() fix from -CURRENT to -STABLE? (mozilla blocker) In-Reply-To: <19991217003307.A26322@shaka.acc.umu.se> References: <19991217003307.A26322@shaka.acc.umu.se> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19991217003307.A26322@shaka.acc.umu.se>, Markus Holmberg wrote: > Hello.. > > A while ago a bug was revealed (and fixed) regarding dlopen() and > symbols behaviour in FreeBSD when loading shared libraries. This was (as > far as I've understood it) fixed in -CURRENT, but never brought into > -STABLE. > This bug is a blocker for Mozilla on FreeBSD 3.x (which is the current > FreeBSD stable branch). Mozilla simply won't run without it. > > Is there by any chance that someone, pretty pretty please with sugar on > top, would bring this fix back into -STABLE? Yep! Jordan and I discussed it, and he did the deed. The fix is in 3.4-RELEASE. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 1:40:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 286CB14E69; Fri, 17 Dec 1999 01:40:41 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:ffxgGWHdJg117Q+OeV9VPzHWgkUyNj2M@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id SAA16393; Fri, 17 Dec 1999 18:40:36 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id SAA24542; Fri, 17 Dec 1999 18:45:31 +0900 (JST) Message-Id: <199912170945.SAA24542@zodiac.mech.utsunomiya-u.ac.jp> To: jkh@freebsd.org, stable@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: URGENT! SHOW STOPPER! moused is broken! Date: Fri, 17 Dec 1999 18:45:25 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am sorry. A report just came in, and I now have to conclude that the last minutes MFC of moused was ill-conceived. That supposed improvement on the 3 button emulation actually broke the wheel/roller support in moused ;-< (Moused is now broken in both -CURRENT and -STABLE.) I don't think I can fix this in a short while. I need a few days to rethink the algorithm. If we can stop 3.4R now, we should back out the following MFC immediately. ---------------------------------------------------------------------- yokota 1999/12/16 13:20:17 PST Modified files: (Branch: RELENG_3) usr.sbin/moused moused.8 moused.c Log: MFC: fix the three button emulation. Approved by:jkh Revision Changes Path 1.18.2.6 +13 -2 src/usr.sbin/moused/moused.8 1.24.2.4 +241 -42 src/usr.sbin/moused/moused.c ---------------------------------------------------------------------- I am very sorry for the disturbance this is causing. Kazu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 2: 0: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 74BA314BF5; Fri, 17 Dec 1999 01:59:54 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 11yuAl-0007pj-00; Fri, 17 Dec 1999 11:59:39 +0200 From: Sheldon Hearn To: Kazutaka YOKOTA Cc: jkh@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: URGENT! SHOW STOPPER! moused is broken! In-reply-to: Your message of "Fri, 17 Dec 1999 18:45:25 +0900." <199912170945.SAA24542@zodiac.mech.utsunomiya-u.ac.jp> Date: Fri, 17 Dec 1999 11:59:39 +0200 Message-ID: <30114.945424779@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 17 Dec 1999 18:45:25 +0900, Kazutaka YOKOTA wrote: > I don't think I can fix this in a short while. I need a few days to > rethink the algorithm. If we can stop 3.4R now, we should back out > the following MFC immediately. I've done this in RELENG_3. Do you want it backed out in CURRENT as well? 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 17 2: 3:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id D72E61504D; Fri, 17 Dec 1999 02:03:49 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:JYYgOUMEg8HLTtHF9cOUuQWQvIqsRkRa@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id TAA17107; Fri, 17 Dec 1999 19:03:05 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id TAA25176; Fri, 17 Dec 1999 19:08:09 +0900 (JST) Message-Id: <199912171008.TAA25176@zodiac.mech.utsunomiya-u.ac.jp> To: Sheldon Hearn Cc: jkh@freebsd.org, stable@freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: URGENT! SHOW STOPPER! moused is broken! In-reply-to: Your message of "Fri, 17 Dec 1999 11:59:39 +0200." <30114.945424779@axl.noc.iafrica.com> References: <30114.945424779@axl.noc.iafrica.com> Date: Fri, 17 Dec 1999 19:08:08 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> I don't think I can fix this in a short while. I need a few days to >> rethink the algorithm. If we can stop 3.4R now, we should back out >> the following MFC immediately. > >I've done this in RELENG_3. Do you want it backed out in CURRENT as >well? Yes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 5:25: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 9F63F1573F for ; Fri, 17 Dec 1999 05:24:55 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id IAA79686 for ; Fri, 17 Dec 1999 08:24:54 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id IAA60384 for stable@freebsd.org; Fri, 17 Dec 1999 08:24:54 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912171324.IAA60384@rtfm.newton> Subject: buildworld dies in i4b/isdnd To: stable@freebsd.org Date: Fri, 17 Dec 1999 08:24:54 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Fri, 17 Dec 1999 05:39:14 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id IAA79724 for ; Fri, 17 Dec 1999 08:39:14 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id IAA86316 for stable@freebsd.org; Fri, 17 Dec 1999 08:39:13 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912171339.IAA86316@rtfm.newton> Subject: vinum overwrites optimization options in CFLAGS To: stable@freebsd.org Date: Fri, 17 Dec 1999 08:39:12 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Cc: jkh@freebsd.org, stable@freebsd.org Subject: Re: URGENT! SHOW STOPPER! moused is broken! In-reply-to: Your message of "Fri, 17 Dec 1999 18:45:25 +0900." <199912170945.SAA24542@zodiac.mech.utsunomiya-u.ac.jp> Date: Fri, 17 Dec 1999 10:36:36 -0800 Message-ID: <68002.945455796@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am sorry. A report just came in, and I now have to conclude > that the last minutes MFC of moused was ill-conceived. That supposed > improvement on the 3 button emulation actually broke the wheel/roller > support in moused ;-< (Moused is now broken in both -CURRENT and > -STABLE.) Eek. OK, well, the release just finished this morning after laying the tag down tonite but I haven't copied it anywhere yet. I'll slide the tags forward in -stable and start the build over again. It won't result in more than a 6 hour delay and 4 or 5 messages in my mailbox wondering where 3.4-RELEASE is. :-) Don't worry about it, mistakes happen and we caught this one before it became a real problem. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 10:42:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 544FF14EBE; Fri, 17 Dec 1999 10:42:04 -0800 (PST) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-152.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FMW002MYELKW8@mail.uni-bielefeld.de>; Fri, 17 Dec 1999 19:41:46 +0100 (MET) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id TAA01714; Fri, 17 Dec 1999 19:21:11 +0100 (CET envelope-from bjoern) Date: Fri, 17 Dec 1999 19:21:11 +0100 From: Bjoern Fischer Subject: Re: Mylex DAC Driver In-reply-to: <199912162345.PAA01922@mass.cdrom.com>; from msmith@FreeBSD.ORG on Thu, Dec 16, 1999 at 03:45:40PM -0800 To: Mike Smith Cc: stable@FreeBSD.ORG Message-id: <19991217192111.B403@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable References: <199912162345.PAA01922@mass.cdrom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 16, 1999 at 03:45:40PM -0800, Mike Smith wrote: [...] > -current supports all of the controllers that Mylex are currently=20 > selling. I'll be updating the -stable patchkit shortly. Is this also true for the old Buslogic FlashPoint series? Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 12:14:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 78D90157B9 for ; Fri, 17 Dec 1999 12:14:09 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00934; Fri, 17 Dec 1999 12:17:07 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912172017.MAA00934@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bjoern Fischer Cc: stable@FreeBSD.ORG Subject: Re: Mylex DAC Driver In-reply-to: Your message of "Fri, 17 Dec 1999 19:21:11 +0100." <19991217192111.B403@frolic.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Fri, 17 Dec 1999 12:17:07 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Thu, Dec 16, 1999 at 03:45:40PM -0800, Mike Smith wrote: > [...] > > -current supports all of the controllers that Mylex are currently = > > selling. I'll be updating the -stable patchkit shortly. > = > Is this also true for the old Buslogic FlashPoint series? The FlashPoint controllers are not RAID controllers. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 12:42:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id 0604415732; Fri, 17 Dec 1999 12:42:29 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id PAA01558; Fri, 17 Dec 1999 15:42:27 -0500 (EST) (envelope-from mi) Message-Id: <199912172042.PAA01558@misha.cisco.com> Subject: URGENT (?) booting from CD on Atapi To: stable@freebsd.org Date: Fri, 17 Dec 1999 15:42:27 -0500 (EST) Cc: jkh@freebsd.org Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (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 Hello! This may be a bit late :-| A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would not boot from 3.3 CD if the SCSI disks are online. It would say: "Read Error" on the upper left of the screen -- where you'd normally see the spinning dash. I suspect, this is a loader's bug :(, which may make it to 3.4 ... The workaround is to disconnect the SCSI chain at the boot time and connect it back when the /boot/loader gives the prompt -- the kernel will find the disks nicely. -mi The devices: wdc1: unit 0 (atapi): , removable, accel, dma, iordis acd0: drive speed 5512KB/sec, 256KB cache acd0: supported read types: CD-R, CD-RW, CD-DA [...] ahc0: rev 0x00 int a irq 11 on pci0.13.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs Waiting 2 seconds for SCSI devices to settle sa0: Removable Sequential Access SCSI-2 device da0: Fixed Direct Access SCSI-2 device da1: Fixed Direct Access SCSI-2 device To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 12:48:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 0D52314FDD; Fri, 17 Dec 1999 12:48:19 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA01425; Fri, 17 Dec 1999 12:51:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912172051.MAA01425@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mi@aldan.algebra.com Cc: stable@freebsd.org, jkh@freebsd.org Subject: Re: URGENT (?) booting from CD on Atapi In-reply-to: Your message of "Fri, 17 Dec 1999 15:42:27 EST." <199912172042.PAA01558@misha.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Dec 1999 12:51:18 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > > This may be a bit late :-| > > A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would not > boot from 3.3 CD if the SCSI disks are online. It would say: "Read > Error" on the upper left of the screen -- where you'd normally see the > spinning dash. I suspect, this is a loader's bug :(, which may make it > to 3.4 ... This is a bug in your BIOS, or your configuration of your system. The loader is not running at that point; the 'Read Error' message is boot1 trying to load boot2 and failing, typically due to a bad value in %dl passed by the BIOS. > The workaround is to disconnect the SCSI chain at the boot time and > connect it back when the /boot/loader gives the prompt -- the kernel > will find the disks nicely. I assume that the system boots correctly from disk once FreeBSD is installed? -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 12:51:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from prserv.net (out2.prserv.net [165.87.194.229]) by hub.freebsd.org (Postfix) with ESMTP id 4CB5314CC7; Fri, 17 Dec 1999 12:51:07 -0800 (PST) (envelope-from jsachs@iclick.com) Received: from iclick.com ([166.72.10.16]) by prserv.net (out2) with SMTP id <1999121720510522900r7akue>; Fri, 17 Dec 1999 20:51:06 +0000 Message-ID: <385AA18A.D0AFFF6A@iclick.com> Date: Fri, 17 Dec 1999 15:48:10 -0500 From: Jay Sachs Organization: iClick, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 Cc: stable@freebsd.org, ports@freebsd.org Subject: just-supped stable requires zsh-devel port rebuilt? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Not sure why. Unfortunately, those messages have scrolled into buffer obvlivion. They were to the effect that zsh couldn't autoload (or even find?) defintions of internal functions, like compctl and bindkey. This was during processing of my .zshrc file, and wasn't fatal to the shell. Nothing changed in the port since my last worldbuild (~ month ago), according to timestamps. The system CVSup-ped this AM, just made world, kernel and mergemastered and rebooted. Anyhow, rebuilding and installing the port cleared it up. jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 13: 4:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.mt.sri.com (ns.mt.sri.com [206.127.79.91]) by hub.freebsd.org (Postfix) with ESMTP id BF02714D75; Fri, 17 Dec 1999 13:04:44 -0800 (PST) (envelope-from nate@mt.sri.com) Received: from mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.9.3/8.9.3) with SMTP id OAA20793; Fri, 17 Dec 1999 14:04:35 -0700 (MST) (envelope-from nate@rocky.mt.sri.com) Received: by mt.sri.com (SMI-8.6/SMI-SVR4) id OAA28099; Fri, 17 Dec 1999 14:04:33 -0700 Date: Fri, 17 Dec 1999 14:04:33 -0700 Message-Id: <199912172104.OAA28099@mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Jordan K. Hubbard" Cc: Kazutaka YOKOTA , jkh@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: URGENT! SHOW STOPPER! moused is broken! In-Reply-To: <68002.945455796@zippy.cdrom.com> References: <199912170945.SAA24542@zodiac.mech.utsunomiya-u.ac.jp> <68002.945455796@zippy.cdrom.com> X-Mailer: VM 6.34 under 19.16 "Lille" XEmacs Lucid Reply-To: nate@mt.sri.com (Nate Williams) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am sorry. A report just came in, and I now have to conclude > > that the last minutes MFC of moused was ill-conceived. That supposed > > improvement on the 3 button emulation actually broke the wheel/roller > > support in moused ;-< (Moused is now broken in both -CURRENT and > > -STABLE.) > > Eek. OK, well, the release just finished this morning after laying > the tag down tonite but I haven't copied it anywhere yet. I'll slide > the tags forward in -stable and start the build over again. It won't > result in more than a 6 hour delay and 4 or 5 messages in my mailbox > wondering where 3.4-RELEASE is. :-) > > Don't worry about it, mistakes happen and we caught this one before > it became a real problem. Thanks for doing this Jordan! Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 13:20:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from misha.cisco.com (misha.cisco.com [171.69.206.50]) by hub.freebsd.org (Postfix) with ESMTP id B0F5814FBC; Fri, 17 Dec 1999 13:20:39 -0800 (PST) (envelope-from mi@misha.cisco.com) Received: (from mi@localhost) by misha.cisco.com (8.9.3/8.9.1) id QAA01726; Fri, 17 Dec 1999 16:20:37 -0500 (EST) (envelope-from mi) Message-Id: <199912172120.QAA01726@misha.cisco.com> Subject: Re: URGENT (?) booting from CD on Atapi In-Reply-To: <199912172051.MAA01425@mass.cdrom.com> from Mike Smith at "Dec 17, 1999 12:51:18 pm" To: Mike Smith Date: Fri, 17 Dec 1999 16:20:37 -0500 (EST) Cc: stable@freebsd.org, jkh@freebsd.org Reply-To: mi@aldan.algebra.com From: Mikhail Teterin X-Mailer: ELM [version 2.4ME+ PL60 (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 Mike Smith once wrote: > > A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would > > not boot from 3.3 CD if the SCSI disks are online. It would say: > > "Read Error" on the upper left of the screen -- where you'd normally > > see the spinning dash. I suspect, this is a loader's bug :(, which > > may make it to 3.4 ... > This is a bug in your BIOS, or your configuration of your system. The > loader is not running at that point; the 'Read Error' message is boot1 > trying to load boot2 and failing, typically due to a bad value in %dl > passed by the BIOS. Well, I figured, it is not the BIOS, who says "Read Error", but did not know which part of the boot process :) I was hoping to shed some light on the problem, that was reported shortly after the 3.3RELEASE, when some people were and some were not able to boot from their CD-ROMs. May be this (common?) BIOS' brokennes can be worked around in boot1? > > The workaround is to disconnect the SCSI chain at the boot time and > > connect it back when the /boot/loader gives the prompt -- the kernel > > will find the disks nicely. > > I assume that the system boots correctly from disk once FreeBSD is > installed? Yes. -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 14:42: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from outmail.utsunomiya-u.ac.jp (outmail.utsunomiya-u.ac.jp [160.12.196.3]) by hub.freebsd.org (Postfix) with ESMTP id 95AE114E39 for ; Fri, 17 Dec 1999 14:41:54 -0800 (PST) (envelope-from yokota@zodiac.mech.utsunomiya-u.ac.jp) Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:kv4GMTV9We27RG7tB0mtLXEIKG4HKecA@zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by outmail.utsunomiya-u.ac.jp (8.9.3/3.7Wpl2) with ESMTP id HAA16938 for ; Sat, 18 Dec 1999 07:41:52 +0900 (JST) Received: from zodiac.mech.utsunomiya-u.ac.jp (zodiac.mech.utsunomiya-u.ac.jp [160.12.42.1]) by zodiac.mech.utsunomiya-u.ac.jp (8.7.6+2.6Wbeta7/3.4W/zodiac-May96) with ESMTP id HAA06272; Sat, 18 Dec 1999 07:46:56 +0900 (JST) Message-Id: <199912172246.HAA06272@zodiac.mech.utsunomiya-u.ac.jp> To: stable@freebsd.org Cc: yokota@zodiac.mech.utsunomiya-u.ac.jp Subject: Re: URGENT! SHOW STOPPER! moused is broken! In-reply-to: Your message of "Fri, 17 Dec 1999 14:04:33 MST." <199912172104.OAA28099@mt.sri.com> References: <199912170945.SAA24542@zodiac.mech.utsunomiya-u.ac.jp> <68002.945455796@zippy.cdrom.com> <199912172104.OAA28099@mt.sri.com> Date: Sat, 18 Dec 1999 07:46:55 +0900 From: Kazutaka YOKOTA Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I apologize again to anybody who have been waiting for 3.4-RELEASE for causing this delay. It was my fault that my last-minute MFC actually broke something. I will be more cautious in the future. Sorry. Kazu >> Eek. OK, well, the release just finished this morning after laying >> the tag down tonite but I haven't copied it anywhere yet. I'll slide >> the tags forward in -stable and start the build over again. It won't >> result in more than a 6 hour delay and 4 or 5 messages in my mailbox >> wondering where 3.4-RELEASE is. :-) >> >> Don't worry about it, mistakes happen and we caught this one before >> it became a real problem. > >Thanks for doing this Jordan! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 14:59: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail4.nycap.rr.com (mail4-1.nyroc.rr.com [24.92.33.20]) by hub.freebsd.org (Postfix) with ESMTP id 258DE15785 for ; Fri, 17 Dec 1999 14:58:51 -0800 (PST) (envelope-from dqureshi@cyvox.com) Received: from cnchq-1 ([24.25.144.240]) by mail4.nycap.rr.com (Post.Office MTA v3.5.3 release 223 ID# 0-59787U250000L250000S0V35) with SMTP id com for ; Fri, 17 Dec 1999 18:00:48 -0500 From: "Danish A. Qureshi" To: Subject: Date: Fri, 17 Dec 1999 17:58:45 -0500 Message-ID: <000201bf48e2$45833a20$f0901918@cnchq-1.nycap.rr.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 17:34:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 74BE01530C; Fri, 17 Dec 1999 17:34:17 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 11z8l8-000IJL-00; Fri, 17 Dec 1999 17:34:10 -0800 Date: Fri, 17 Dec 1999 17:34:06 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Mikhail Teterin Cc: stable@freebsd.org, jkh@freebsd.org Subject: Re: URGENT (?) booting from CD on Atapi In-Reply-To: <199912172042.PAA01558@misha.cisco.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 Fri, 17 Dec 1999, Mikhail Teterin wrote: > Hello! > > This may be a bit late :-| > > A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would not > boot from 3.3 CD if the SCSI disks are online. It would say: "Read > Error" on the upper left of the screen -- where you'd normally see the > spinning dash. I suspect, this is a loader's bug :(, which may make it > to 3.4 ... Don't see a problem with that here. I just booted the 3.3-R CD on an ATAPI CD ROM with no other IDE devices, and everything was fine. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 17:55:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pemaquid.safeport.com (pemaquid.safeport.com [204.156.12.58]) by hub.freebsd.org (Postfix) with ESMTP id 6ECC414DF0 for ; Fri, 17 Dec 1999 17:55:48 -0800 (PST) (envelope-from doug@pemaquid.safeport.com) Received: by pemaquid.safeport.com (8.9.3/8.9.3) id UAA00342 for freebsd-stable@FreeBSD.org; Fri, 17 Dec 1999 20:55:42 -0500 (EST) (envelope-from doug) From: Douglas Denault To: freebsd-stable@FreeBSD.org Subject: Join FreeBSD Stable Date: Fri, 17 Dec 1999 20:52:28 -0500 X-Mailer: KMail [version 1.0.21] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <99121720554100.00332@pemaquid.safeport.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable -- doug@pemiquid.safeport.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 18: 7:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 8080A14DF7 for ; Fri, 17 Dec 1999 18:07:14 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id VAA84536; Fri, 17 Dec 1999 21:07:13 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id VAA00624; Fri, 17 Dec 1999 21:07:12 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912180207.VAA00624@rtfm.newton> Subject: Re: URGENT (?) booting from CD on Atapi In-Reply-To: from Tom at "Dec 17, 1999 06:05:08 pm" To: Tom Date: Fri, 17 Dec 1999 21:07:12 -0500 (EST) Cc: stable@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Tom once stated: => => =On Fri, 17 Dec 1999, Mikhail Teterin wrote: => = => => A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would => => not boot from 3.3 CD if the SCSI disks are online. It would say: => => "Read Error" on the upper left of the screen -- where you'd => => normally see the spinning dash. I suspect, this is a loader's bug => => :(, which may make it to 3.4 ... => = => = Don't see a problem with that here. I just booted the 3.3-R CD on => =an ATAPI CD ROM with no other IDE devices, and everything was fine. => => Do you have SCSI disks online at the boot time? = = Yes. Lucky you... Are the SCSI disks otherwise bootable? Is the CD on the primary or the secondary IDE channel? -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 18:50:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 77F1D14A03 for ; Fri, 17 Dec 1999 18:50:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA06364; Fri, 17 Dec 1999 18:53:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912180253.SAA06364@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mi@aldan.algebra.com Cc: stable@freebsd.org Subject: Re: URGENT (?) booting from CD on Atapi In-reply-to: Your message of "Fri, 17 Dec 1999 16:20:37 EST." <199912172120.QAA01726@misha.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Dec 1999 18:53:40 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith once wrote: > > > > A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would > > > not boot from 3.3 CD if the SCSI disks are online. It would say: > > > "Read Error" on the upper left of the screen -- where you'd normally > > > see the spinning dash. I suspect, this is a loader's bug :(, which > > > may make it to 3.4 ... > > > This is a bug in your BIOS, or your configuration of your system. The > > loader is not running at that point; the 'Read Error' message is boot1 > > trying to load boot2 and failing, typically due to a bad value in %dl > > passed by the BIOS. > > Well, I figured, it is not the BIOS, who says "Read Error", but did not > know which part of the boot process :) I was hoping to shed some light > on the problem, that was reported shortly after the 3.3RELEASE, when > some people were and some were not able to boot from their CD-ROMs. May > be this (common?) BIOS' brokennes can be worked around in boot1? No. The 3.3-RELEASE issue (which was also detailed here) was another BIOS bug which prevented the CDROM from being recognised as bootable at all. If your code is never run, you can't 'work around' anything. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 19:40: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id 7254814E48 for ; Fri, 17 Dec 1999 19:39:58 -0800 (PST) (envelope-from williamsl@Home.Com) Received: from RELIABLE ([24.4.115.31]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991218033957.PDZX17996.mail.rdc1.tn.home.com@RELIABLE> for ; Fri, 17 Dec 1999 19:39:57 -0800 Date: Fri, 17 Dec 1999 22:21:51 -0500 From: Ben WIlliams X-Mailer: The Bat! (v1.34a) UNREG / CD5BF9353B3B7091 Reply-To: Ben WIlliams X-Priority: 3 (Normal) Message-ID: <13931.991217@Home.Com> To: freebsd-stable@FreeBSD.ORG Subject: ld.so failed: Can't find shared library.. 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 One of the servers I now manage is a 2.2.5-RELEASE server. I recently tried running cvsup from a shell and got: ld.so failed: Can't find shared library "libset.so.6.0" What is libset.so.6.0 a part of? I have also been having difficulty making the openssh port due to what appears to be a new flag to ld (--whole-archive) since the birth of this machine. What are my upgrade options? This is a production server with little tolerance for downtime and I haven't been a FreeBSD'er for long enough to know exactly how to fix these problems. -- Ben mailto:williamsl@Home.Com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 21:21:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 9A3EE14C4A; Fri, 17 Dec 1999 21:21:25 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id AAA85663; Sat, 18 Dec 1999 00:21:23 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id AAA01029; Sat, 18 Dec 1999 00:21:23 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912180521.AAA01029@rtfm.newton> Subject: Re: URGENT (?) booting from CD on Atapi In-Reply-To: <199912180303.TAA06533@mass.cdrom.com> from Mike Smith at "Dec 17, 1999 07:03:44 pm" To: Mike Smith Date: Sat, 18 Dec 1999 00:21:23 -0500 (EST) Cc: stable@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Ok... So this is a different one, then... What information do I need => to provide for someone to be able to make a "work around" for _it_? = =It's not clear that you can; it's possible that your setup is just "too =broken" for us. = =A good start would be to test some other supposedly bootable CDROMs =(W96, NT4.0, RedHat 6.1) and see if they work. No, I can not afford rebooting this box :( It is a "production" machine. Only what I can get during run-time. But it can boot from the CDROM if there are no disks attached. Oh, yeah, the boot disk's SCSI id is set in the adapter's BIOS as 6, and the second disk has the id 8... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 22:33: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.psn.net (pluto.psn.net [207.211.58.12]) by hub.freebsd.org (Postfix) with ESMTP id 5B94114A0D for ; Fri, 17 Dec 1999 22:33:04 -0800 (PST) (envelope-from will@shadow.blackdawn.com) Received: from 17-031.008.popsite.net ([209.69.196.31] helo=shadow.blackdawn.com) by pluto.psn.net with esmtp (PSN Internet Service 3.12 #1) id 11zDQM-000058-00; Fri, 17 Dec 1999 23:33:03 -0700 Received: (from will@localhost) by shadow.blackdawn.com (8.9.3/8.9.3) id BAA58964; Sat, 18 Dec 1999 01:32:59 -0500 (EST) (envelope-from will) Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <13931.991217@Home.Com> Date: Sat, 18 Dec 1999 01:32:59 -0500 (EST) Reply-To: Will Andrews From: Will Andrews To: Ben WIlliams Subject: RE: ld.so failed: Can't find shared library.. Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Dec-99 Ben WIlliams wrote: > One of the servers I now manage is a 2.2.5-RELEASE server. I This system is excessively old.. you should upgrade it to a newer version, say, at least 3.1-RELEASE or later. > recently tried running cvsup from a shell and got: > > ld.so failed: Can't find shared library "libset.so.6.0" That looks like an a.out library.. > What is libset.so.6.0 a part of? I have also been having difficulty > making the openssh port due to what appears to be a new flag to ld > (--whole-archive) since the birth of this machine. Ports are not really guaranteed to work on any version of FreeBSD other than the latest -STABLE (and there are exceptions for that) and -CURRENT. Try upgrading this system to a newer version of FreeBSD. > What are my upgrade options? This is a production server with > little tolerance for downtime and I haven't been a FreeBSD'er for long > enough to know exactly how to fix these problems. That is understandable. I'd actually guessed it was a production server. You can minimize downtime by building the 3.x world and then dropping to single user mode to install the world. However, I've never really tried to upgrade from 2.2.x to 3.x. I just backup the machine and format and reinstall using 3.x CDs. 2.x -> 3.x is a HUGE upgrade.. your best bet would be to load balance the server's services among other servers while you upgrade it. Or to load a copy of 3.x on a new server, set it up, and transfer sensitive data to the new server, test it, then when it's ready, take the old one off and put the new one on. Sorry, I really can't offer any better ideas without further information. -- Will Andrews GCS/E/S @d- s+:+>+:- a--->+++ C++ UB++++ P+ L- E--- W+++ !N !o ?K w--- ?O M+ V-- PS+ PE++ Y+ PGP+>+++ t++ 5 X++ R+ tv+ b++>++++ DI+++ D+ G++>+++ e->++++ h! r-->+++ y? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 17 22:35:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id A3B1514EEE for ; Fri, 17 Dec 1999 22:35:10 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 11zDSO-000Nam-00; Fri, 17 Dec 1999 22:35:08 -0800 Date: Fri, 17 Dec 1999 22:35:01 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Mikhail Teterin Cc: stable@freebsd.org Subject: Re: URGENT (?) booting from CD on Atapi In-Reply-To: <199912180207.VAA00624@rtfm.newton> 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, 17 Dec 1999, Mikhail Teterin wrote: > Tom once stated: > > =On Fri, 17 Dec 1999, Mikhail Teterin wrote: > = > => Tom once stated: > => > => =On Fri, 17 Dec 1999, Mikhail Teterin wrote: > => = > => => A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) would > => => not boot from 3.3 CD if the SCSI disks are online. It would say: > => => "Read Error" on the upper left of the screen -- where you'd > => => normally see the spinning dash. I suspect, this is a loader's bug > => => :(, which may make it to 3.4 ... > => = > => = Don't see a problem with that here. I just booted the 3.3-R CD on > => =an ATAPI CD ROM with no other IDE devices, and everything was fine. > => > => Do you have SCSI disks online at the boot time? > = > = Yes. > > Lucky you... Are the SCSI disks otherwise bootable? Is the CD on the > primary or the secondary IDE channel? The SCSI disk is bootable in that set in the BIOS to boot (I used "A: CD C:" boot order), but I don't think it has an OS on it. You could just have a boot order issue. Maybe the SCSI disk has a screwed up boot sector, and SCSI disk is earlier in the boot order ("A: C: CD"), so it never gets to the CD. > -mi > > Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 0:56:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id EF33E14A19 for ; Sat, 18 Dec 1999 00:56:31 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id DAA88723; Sat, 18 Dec 1999 03:56:30 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id DAA02633; Sat, 18 Dec 1999 03:56:30 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912180856.DAA02633@rtfm.newton> Subject: Re: URGENT (?) booting from CD on Atapi In-Reply-To: from Tom at "Dec 17, 1999 10:35:01 pm" To: Tom Date: Sat, 18 Dec 1999 03:56:30 -0500 (EST) Cc: stable@freebsd.org X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" => => A machine with SCSI disks and an ATAPI CD-ROM (no IDE disks) => => => would not boot from 3.3 CD if the SCSI disks are online. It => => => would say: "Read Error" on the upper left of the screen -- => => => where you'd normally see the spinning dash. I suspect, this is => => => a loader's bug :(, which may make it to 3.4 ... => => = => => = Don't see a problem with that here. I just booted the 3.3-R CD => => =on an ATAPI CD ROM with no other IDE devices, and everything was => => =fine. [...] => Lucky you... Are the SCSI disks otherwise bootable? Is the CD on the => primary or the secondary IDE channel? = = The SCSI disk is bootable in that set in the BIOS to boot (I used "A: =CD C:" boot order), but I don't think it has an OS on it. = = You could just have a boot order issue. Maybe the SCSI disk has a =screwed up boot sector, and SCSI disk is earlier in the boot order ("A: =C: CD"), so it never gets to the CD. Nope. If I take the CD out of the drive, the machine will nicely boot from the SCSI disk... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 1: 8: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 60F7614D6A for ; Sat, 18 Dec 1999 01:08:02 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id EAA88782 for ; Sat, 18 Dec 1999 04:08:01 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id EAA02812 for stable@freebsd.org; Sat, 18 Dec 1999 04:08:01 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912180908.EAA02812@rtfm.newton> Subject: StarOffice5 and SMP To: stable@freebsd.org Date: Sat, 18 Dec 1999 04:08:01 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli"; Sat, 18 Dec 1999 07:57:01 -0800 (PST) (envelope-from stanb@netcom.com) Received: (from stanb@localhost) by netcom.com (8.9.3/8.9.3) id HAA22996 for freebsd-stable@freebsd.org; Sat, 18 Dec 1999 07:57:00 -0800 (PST) From: Stan Brown Message-Id: <199912181557.HAA22996@netcom.com> Subject: Sys Admin article on Linux emulation To: freebsd-stable@freebsd.org (FreeBSD Stable List) Date: Sat, 18 Dec 1999 10:57:00 -0500 (EST) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This months _Sy Admin_ magazine has a nice aritcle on Linux emulation under FreeBSD. The author says he is running CURRENT> He rcomends several options to be set in ones kernel config file. Are these option appropriate for a machine runing STABLE? Thanks. -- Stan Brown stanb@netcom.com 404-996-6955 Factory Automation Systems Atlanta Ga. -- Look, look, see Windows 95. Buy, lemmings, buy! Pay no attention to that cliff ahead... Henry Spencer (c) 1998 Stan Brown. Redistribution via the Microsoft Network is prohibited. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 8: 0:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ipamzlx.physik.uni-mainz.de (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by hub.freebsd.org (Postfix) with ESMTP id 56EC215030 for ; Sat, 18 Dec 1999 08:00:22 -0800 (PST) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Received: from ipamzlx.Physik.Uni-Mainz.DE (ipamzlx.Physik.Uni-Mainz.DE [134.93.180.54]) by ipamzlx.physik.uni-mainz.de (8.9.3/8.9.3) with ESMTP id RAA26535 for ; Sat, 18 Dec 1999 17:01:50 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Sat, 18 Dec 1999 17:01:50 +0100 (CET) From: "O. Hartmann" To: freebsd-stable@freebsd.org Subject: Parallelport problems, ALI 1554 chipset 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 Dear Sirs. I posted a question before in one of the related newsgroup for this problem but it seems that nobody wants to give an answer or nobody has an answer. I'll try it here again and hope it will have success. I have a printserver, based on FreeBSD 3.4. Hardware is: Gigabyte 5GAA main PCB, based on ALi Chipset 1542-100 (Aladdin-V AGPset Chip) CPU AMD K6-2 500MHz memory 128MBytes PC100 RAM NIC 3COM 3C905B-TX (at 100MB/full duplex) Adaptec 2940U Controller Matrox G200 graphics device noname 8 bit additional parallel port card on ISA bus, EPP capabilities. Phenomenon: this system is our printserver, operating with two laser printers. When printing via lpt0 (built in port) I recognize no performance losses of the system, but whenever someone prints out via lpt1, the additional parallel port interface, this system crashes in performance and for the time the spooler is copying data via lpt1 the server is not accessible via network. Working on console of this machine I realise nothing, but performance of diskdevice seems to be compromised. Accessing this machine via network is impossible! Whenever someone prints out, ping latency pushes up to >16, >25 ms (nomrally 0.200 - 0.500 on our LAN). I changed this additional parallelport card against an older type board (16 bit multi I/O adaptor) - and realized the same! Before I used a GigaByte board based on SiS chipset and I never realized those performance losses so it seems to be a problem of the internal driver of FreeBSD or generally a problem of the PCI-ISA bridge of ALi chips. Before posting my kernel configurations it would be nice whether you can give me hints and tips or discuss this problem. If you're sure it was related to the mainboard/chipset please report me! But ordering a new main PCB could run me into the same problems so I would like to be informed prior to avoid mistakes. Additional, I must say that I configured the additional port like this: controller ppbus0 controller ppbus1 controller ppc0 at isa? port "IO_LPT1" flags 0x08 tty irq 7 drq 1 controller ppc1 at isa? port "IO_LPT2" flags 0x04 tty irq 5 drq 3 device lpt0 at ppbus0 device lpt1 at ppbus1 Hope that is enough information to make any decissions ... Best wishes and thanks in advance, O. Hartmann Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 8:41:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from finland.ispro.net.tr (finland.ispro.net.tr [212.174.120.1]) by hub.freebsd.org (Postfix) with ESMTP id 87D6E14D6A for ; Sat, 18 Dec 1999 08:41:28 -0800 (PST) (envelope-from yurtesen@ispro.net.tr) Received: from localhost (yurtesen@localhost) by finland.ispro.net.tr (8.9.3/8.9.3) with ESMTP id SAA96494; Sat, 18 Dec 1999 18:40:06 +0200 (EET) (envelope-from yurtesen@ispro.net.tr) Date: Sat, 18 Dec 1999 18:40:06 +0200 (EET) From: Evren Yurtesen To: "O. Hartmann" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Parallelport problems, ALI 1554 chipset 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 Are you sure of the DMA and IRQ settings of this extra parallel port interface? Did you try to use this interface in compatible mode with flags 0x0 ? If you have felt performance decrease on disk accesses when you are using the computer from console did you try to use an ide interface card? (If you can still find one.) Evren On Sat, 18 Dec 1999, O. Hartmann wrote: > > Dear Sirs. > I posted a question before in one of the related newsgroup for this problem > but it seems that nobody wants to give an answer or nobody has an answer. I'll > try it here again and hope it will have success. > > I have a printserver, based on FreeBSD 3.4. Hardware is: > Gigabyte 5GAA main PCB, based on ALi Chipset 1542-100 (Aladdin-V AGPset Chip) > CPU AMD K6-2 500MHz > memory 128MBytes PC100 RAM > NIC 3COM 3C905B-TX (at 100MB/full duplex) > Adaptec 2940U Controller > Matrox G200 graphics device > noname 8 bit additional parallel port card on ISA bus, EPP capabilities. > > Phenomenon: this system is our printserver, operating with two laser printers. > When printing via lpt0 (built in port) I recognize no performance losses of the > system, but whenever someone prints out via lpt1, the additional parallel port > interface, this system crashes in performance and for the time the spooler is > copying data via lpt1 the server is not accessible via network. Working on console > of this machine I realise nothing, but performance of diskdevice seems to be > compromised. Accessing this machine via network is impossible! Whenever someone > prints out, ping latency pushes up to >16, >25 ms (nomrally 0.200 - 0.500 on our LAN). > > I changed this additional parallelport card against an older type board (16 bit multi I/O > adaptor) - and realized the same! Before I used a GigaByte board based on SiS chipset and > I never realized those performance losses so it seems to be a problem of the internal driver > of FreeBSD or generally a problem of the PCI-ISA bridge of ALi chips. Before posting my > kernel configurations it would be nice whether you can give me hints and tips or discuss this > problem. If you're sure it was related to the mainboard/chipset please report me! But ordering > a new main PCB could run me into the same problems so I would like to be informed prior to avoid > mistakes. > > Additional, I must say that I configured the additional port like this: > > controller ppbus0 > controller ppbus1 > > controller ppc0 at isa? port "IO_LPT1" flags 0x08 tty irq 7 drq 1 > controller ppc1 at isa? port "IO_LPT2" flags 0x04 tty irq 5 drq 3 > > device lpt0 at ppbus0 > device lpt1 at ppbus1 > > Hope that is enough information to make any decissions ... > > Best wishes and thanks in advance, > > O. Hartmann > > Gruss O. Hartmann > ------------------------------------------------------------------- > ohartman@ipamzlx.physik.uni-mainz.de > > Klimadatenserver des IPA, Universitaet Mainz > > > > 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 Sat Dec 18 8:58:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (Postfix) with ESMTP id 8BB1F14EE5 for ; Sat, 18 Dec 1999 08:58:06 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id LAA71049; Sat, 18 Dec 1999 11:57:32 -0500 (EST) (envelope-from matt@zigg.com) Date: Sat, 18 Dec 1999 11:57:27 -0500 (EST) From: Matt Behrens To: Stan Brown Cc: FreeBSD Stable List Subject: Re: Sys Admin article on Linux emulation In-Reply-To: <199912181557.HAA22996@netcom.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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sat, 18 Dec 1999, Stan Brown wrote: > This months _Sy Admin_ magazine has a nice aritcle on Linux emulation > under FreeBSD. > > The author says he is running CURRENT> He rcomends several options to > be set in ones kernel config file. Are these option appropriate for a > machine runing STABLE? Well, the first thing to do would be to see if said options are present in - -STABLE's LINT. :-) Is there a link to the article so we could tell just what options the author is referring to? Matt Behrens Owner/Administrator, zigg.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE4W7z7+xq4JbgNGlMRAmQBAJ9ptK6pAw15tVviSL+/vw6BviWt9QCfV2nk ZQDl730tG2zwjiFY2acgrtQ= =lgT4 -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 11:14:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 926C414E45 for ; Sat, 18 Dec 1999 11:14:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA75287 for ; Sat, 18 Dec 1999 11:14:15 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: stable@freebsd.org Subject: code freeze is lifted. Date: Sat, 18 Dec 1999 11:14:15 -0800 Message-ID: <75284.945544455@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I haven't released 3.4 yet since I'm still chasing some last cosmetic problems and I've got until Monday morning to cut the CD, so I'm going to put the extra time to good use. Nonetheless, there's no reason for 3.4 to remain frozen at this point, so please consider the freeze in the 3.4-stable branch lifted. - 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 18 12:10:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id 3F03414E53 for ; Sat, 18 Dec 1999 12:10:21 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id VAA01390 for ; Sat, 18 Dec 1999 21:10:11 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id VAA21534 for ; Sat, 18 Dec 1999 21:10:10 +0100 (MEZ) Date: Sat, 18 Dec 1999 21:10:09 +0100 From: Martin Blapp To: stable@freebsd.org Subject: upgrade problem from 3.2 -> 3.4 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 Compiling GENERIC fails ! I get the following errors while compiling kernel : loading kernel vfs_bio.o: In function `vfs_buf_set_valid': vfs_bio.o(.text+0x25d9): undefined reference to `__cmpdi2' msdosfs_vnops.o: In function `msdosfs_readdir': msdosfs_vnops.o(.text+0x23f9): undefined reference to `__cmpdi2' ffs_vnops.o: In function `ffs_getpages': ffs_vnops.o(.text+0xeae): undefined reference to `__cmpdi2' *** Error code 1 I made the following steps before: cvsup to the newest 3.X sources .. cd /usr/src && make buildworld && make installworld cd /usr/src/includes && make depend && make && make install config -r GENERIC Martin Anyone knows more ? Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 12:16:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles522.castles.com [208.214.165.86]) by hub.freebsd.org (Postfix) with ESMTP id 1358614EB4 for ; Sat, 18 Dec 1999 12:16:15 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00644; Sat, 18 Dec 1999 12:19:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912182019.MAA00644@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mikhail Teterin Cc: stable@freebsd.org Subject: Re: URGENT (?) booting from CD on Atapi In-reply-to: Your message of "Sat, 18 Dec 1999 00:21:23 EST." <199912180521.AAA01029@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Dec 1999 12:19:47 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mike Smith once stated: > > => Ok... So this is a different one, then... What information do I need > => to provide for someone to be able to make a "work around" for _it_? > = > =It's not clear that you can; it's possible that your setup is just "too > =broken" for us. > = > =A good start would be to test some other supposedly bootable CDROMs > =(W96, NT4.0, RedHat 6.1) and see if they work. > > No, I can not afford rebooting this box :( It is a "production" machine. > Only what I can get during run-time. But it can boot from the CDROM if > there are no disks attached. Well, without this extra information, it's not possible to diagnose your problem let alone work around it. I'm afraid I just have to pronounce it "misconfigured or Truly Broken" (deem wand-waving motion included). -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 12:24:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 825C114EBC for ; Sat, 18 Dec 1999 12:24:10 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id MAA27241 for ; Sat, 18 Dec 1999 12:24:09 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id MAA26899 for stable@freebsd.org; Sat, 18 Dec 1999 12:24:09 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 18 Dec 1999 12:24:09 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: stable@freebsd.org Subject: Strange transient filesystem failures Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have been seeing some baffling errors on freefall, and I'd like to know if anybody has a clue about what could be causing them. There is a CVSup server running on freefall, and it constantly mirrors the entire repository over to cvsup-master.freebsd.org. A new update is run every 6 minutes, or as fast as it can go when it takes longer than that. Occasionally, I am seeing updates fail because opendir() failed with ENOENT on the server (freefall). For example: Cannot read directory "/usr/local/etc/cvsup/prefixes/FreeBSD.cvs/src/sys/nwfs": No such file or directory But from looking at the timestamps of the directory and its parent directory, it's clear that that directory _did_ exist and was not being modified at that time. Also, the commit logs don't show any commits going on around that time. Nothing unusual appears in the system logs, either. These failures are transient and short-lived; the next update always works fine. The failures also seem to be clustered. In one case there happened to be three updates running at once (two from committers), and all three failed within a 5-second interval on different directories: /usr/local/etc/cvsup/prefixes/FreeBSD.cvs/ports/x11-toolkits/v /usr/local/etc/cvsup/prefixes/FreeBSD.cvs/src/sys/nwfs /usr/local/etc/cvsup/prefixes/FreeBSD.cvs/ports/sysutils/afio/pkg At first I suspected that the file table was full, as there are two messages in the dmesg output to that effect. But now I don't think that's it. I have seen several of these failures and have immediately checked the dmesg output, but no new "file: table was full" messages have appeared. Soft-updates are not in use. FWIW, the paths in question involve a few symlinks: /usr/local -> /d/usr.local /d/usr.local/etc/cvsup/prefixes/FreeBSD.cvs -> /home/ncvs /home/ncvs -> /x/ncvs The system is running -stable from October 30. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 12:38:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles522.castles.com [208.214.165.86]) by hub.freebsd.org (Postfix) with ESMTP id AE42114EBC for ; Sat, 18 Dec 1999 12:38:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00736; Sat, 18 Dec 1999 12:41:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912182041.MAA00736@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "O. Hartmann" Cc: freebsd-stable@freebsd.org Subject: Re: Parallelport Problems In-reply-to: Your message of "Tue, 14 Dec 1999 17:07:40 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Dec 1999 12:41:24 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Dear Sirs. > I administer several FreeBSD boxes (now FBSD 3.4-RC). One of them plays > the role of our printserver of our institute. This box is equippted with > AMD K6-2 500 MHz CPU, GigaByte GA-5AA main PCB with ALi 1542 100MHz Aladin-V > chipset, NIC is 3COM 3C905B 100Mbit fullduplex mode, memory 128 MB FSB100, > Adaptec 2940U controller and an additional parallel port card, made in china! > This additional parallelport card seems to be the troublesome unit on ISA bus > but the problem occurs with other multi i/o cards running the parallelport. > One of our printers is attached to this port an whenever a printjob is > queued and sent to the printer via parallelport, the server is unreachable > over the network. Ping latencies pushes up from 0.200 ms to 16 ms and higher. > Printing over the built in parallelport does not reveal this phenomenon. Parallel ports on PC hardware are extremely problematic. I can't recommend using more than one port per machine. You should consider either purchasing a couple of inexpensive USB to parallel adapter cables and using the USB printer support in FreeBSD, or look at obtaining network interface cards for your printers. > Both ports are using IRQs and DMA, port 1 has IRQ 7, dirq 1, port 2 has > IRQ 5, dirq 7. The additional card is capable of EPP 1.9 and I set the > flag for this in kernel config file. So far all things seems to be all > right. But why is the usage of any IO card, especially the parallel port > on additional cards blocking the PCI bus? The system is spending too much time spinning waiting for your printer to respond. See above inre. PC parallel port hardware. The only real "fix" for this is to not use the parallel port on your server for talking to your printers. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 12:42: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles522.castles.com [208.214.165.86]) by hub.freebsd.org (Postfix) with ESMTP id D9E4714D59; Sat, 18 Dec 1999 12:42:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00760; Sat, 18 Dec 1999 12:45:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912182045.MAA00760@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Smith Cc: "O. Hartmann" , freebsd-stable@freebsd.org Subject: Re: Parallelport Problems In-reply-to: Your message of "Sat, 18 Dec 1999 12:41:24 PST." <199912182041.MAA00736@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 18 Dec 1999 12:45:43 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Both ports are using IRQs and DMA, port 1 has IRQ 7, dirq 1, port 2 has > > IRQ 5, dirq 7. The additional card is capable of EPP 1.9 and I set the > > flag for this in kernel config file. So far all things seems to be all > > right. But why is the usage of any IO card, especially the parallel port > > on additional cards blocking the PCI bus? I should have noted that it's also possible that you haven't routed the IRQ for the second port correctly, so you're not getting any interrupts for the port. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 12:55:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.eclipse.net (mail.eclipse.net [207.207.192.13]) by hub.freebsd.org (Postfix) with ESMTP id BEE7A14FB8; Sat, 18 Dec 1999 12:55:41 -0800 (PST) (envelope-from spiffer@eclipse.net) Received: from phil1-02-175.eclipse.net (phil1-02-175.eclipse.net [207.207.238.175]) by mail.eclipse.net (8.9.1a/8.9.1) with ESMTP id PAA23150; Sat, 18 Dec 1999 15:55:39 -0500 (EST) Date: Sat, 18 Dec 1999 15:39:26 -0500 (EST) From: "Roger W." X-Sender: spiffer@deepthought.invalid To: Mike Smith Cc: freebsd-stable@FreeBSD.org Subject: Re: printer problems using 3.4RC kernel In-Reply-To: <199912130135.RAA04626@mass.cdrom.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 Sorry I wasn't able to respond sooner to this Mike, I was called away on business suddenly and couldn't get my emails. After hacking with this for a number of hours today, I was able to determine what was causing the problem with my kernel configuration file. The line: pseudo-device tun 1 #Packet Filtering I had #'d out this line, and it was the cause of all my problems, so the problem, was as usual, PEBKAC. I had a feeling it was in my configuration and not the kernel, but was centering my attention in parallel port area. Thank you for the help, Roger On Sun, 12 Dec 1999, Mike Smith wrote: > > You're not clear about what you're printing, where you're printing it to, > or what the actual output looks like, but these symptoms are entirely > consistent with you trying to print plain text or some other encoding to > the printer. You need to ensure that you're actually printing to the > correct printer device. > > > > Hello everyone, > > > > I've just finished cvsup'ing 3.3-stable, to bring my 3.3-Release system up > > to date. Everything went fine and seems to be working except for my laser > > jet printer. Its a NEC SuperScript 870 which emulates to a HPLJ IIP. The > > printer gets recognized fine during bootup and everthing appears to be OK > > until I try to send roughly more than 1 page of data to it. The page can > > be sent by cat 'filename' | lpr, using a2ps, or just dumping from a > > webpage with html, it doesn't seem to matter. What happens is I only get > > a small amout of data on each page, and then the next page is sucked into > > the printer and again only a small amount of data is placed on it. I am > > using apsfilter as the printers textfilter. > > > > I compared my boot logs with the new kernel to the GENERIC 3.3R kernel I > > was using previously, and there isn't a bit of difference in them. All I > > did was eliminate devices that weren't getting found anyways. I'm sure it > > has to do with the kernel, or its config, as if I boot off my old GENERIC > > kernel my printer functions properly. > > > > The one thing I've noticed is when the printer is working correctly, there > > is significantly more delay from when I send the printjob to the printer, > > and when it starts printing. Booting off of the kernel I compiled, there > > is almost no delay between when I tell the system to print, and when the > > printer starts to suck in the paper and print out small portions of what > > it should be printing spread out over many pages. > > > > If anyone else is seeing this problem and has any ideas, I would love to > > hear them. > > > > thank you, > > > > Roger > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 13:59:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.nifty.ne.jp (smtp2.nifty.ne.jp [202.219.63.54]) by hub.freebsd.org (Postfix) with ESMTP id 70F1914E44 for ; Sat, 18 Dec 1999 13:59:22 -0800 (PST) (envelope-from RXM02755@nifty.ne.jp) Received: from nifty.ne.jp (cs66130.ppp.infoweb.ne.jp [202.219.145.46]) by smtp2.nifty.ne.jp (8.9.3+3.2W/3.7W-991025) with ESMTP id GAA15933 for ; Sun, 19 Dec 1999 06:59:20 +0900 (JST) Message-ID: <385BFC72.7BB6282E@nifty.ne.jp> Date: Sun, 19 Dec 1999 06:28:18 +0900 From: Akihiko Hayasaka X-Mailer: Mozilla 4.61 [ja_JP.EUC] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: ja, en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: majordomo@FreeBSD.org Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable subscribe cvs-all end To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 14:33:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from raven.a001.sprintmail.com (raven.prod.itd.earthlink.net [209.178.63.9]) by hub.freebsd.org (Postfix) with ESMTP id B3F9314F3C for ; Sat, 18 Dec 1999 14:33:46 -0800 (PST) (envelope-from leclaire@sprintmail.com) Received: from [192.168.0.2] (dialup-63.210.227.27.Cincinnati1.Level3.net [63.210.227.27]) by raven.a001.sprintmail.com (8.8.7/8.8.5) with ESMTP id OAA26367; Sat, 18 Dec 1999 14:33:40 -0800 (PST) Date: Sat, 18 Dec 1999 17:33:31 -0500 (EST) From: Andre LeClaire Reply-To: leclaire@switzcpl.lib.in.us To: Martin Blapp Cc: stable@FreeBSD.ORG Subject: Re: upgrade problem from 3.2 -> 3.4 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 Martin, Have you tried doing a make clean in the kernel compile directory (probably in your case /usr/src/sys/compile/GENERIC)? I've had similar failures after doing a cvsup upgrade from 3.2 toolkit installs to -STABLE, and that's always fixed it. Andre > Compiling GENERIC fails ! > > I get the following errors while compiling kernel : > > loading kernel > vfs_bio.o: In function `vfs_buf_set_valid': > vfs_bio.o(.text+0x25d9): undefined reference to `__cmpdi2' > msdosfs_vnops.o: In function `msdosfs_readdir': > msdosfs_vnops.o(.text+0x23f9): undefined reference to `__cmpdi2' > ffs_vnops.o: In function `ffs_getpages': > ffs_vnops.o(.text+0xeae): undefined reference to `__cmpdi2' > *** Error code 1 > > > I made the following steps before: > > cvsup to the newest 3.X sources .. > cd /usr/src && make buildworld && make installworld > cd /usr/src/includes && make depend && make && make install > config -r GENERIC > > Martin > > Anyone knows more ? > > Martin Blapp, mb@imp.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 14:48:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.imp.ch (mail.imp.ch [157.161.1.2]) by hub.freebsd.org (Postfix) with ESMTP id F13FD14E60 for ; Sat, 18 Dec 1999 14:48:14 -0800 (PST) (envelope-from mb@imp.ch) Received: from mephisto.imp.ch (mb@mephisto.imp.ch [157.161.1.22]) by mail.imp.ch (8.9.3/8.9.3) with ESMTP id XAA02692; Sat, 18 Dec 1999 23:48:06 +0100 (MET) Received: from localhost (mb@localhost) by mephisto.imp.ch (8.9.3/8.9.3) with ESMTP id XAA29325; Sat, 18 Dec 1999 23:48:04 +0100 (MEZ) Date: Sat, 18 Dec 1999 23:48:04 +0100 From: Martin Blapp To: Andre LeClaire Cc: stable@freebsd.org Subject: Re: upgrade problem from 3.2 -> 3.4 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 Hi, > Martin, > Have you tried doing a make clean in the kernel compile directory > (probably in your case /usr/src/sys/compile/GENERIC)? I've had similar I did a config -r, so this will not help. Can anyone else with a 3.2 system try to upgrade to 3.4RC ? I'm sure it is a general problem. Anyways - thanks for your suggestion :) Martin Martin Blapp, mb@imp.ch ------------------------------------------------ Improware AG, UNIX solution and service provider Zurlindenstrasse 29, 4133 Pratteln, Switzerland Phone: +41 79 370 26 05, Fax: +41 61 826 93 01 ------------------------------------------------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 16:23:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from roam.psg.com (roam.psg.com [147.28.4.2]) by hub.freebsd.org (Postfix) with ESMTP id C568A14D95 for ; Sat, 18 Dec 1999 16:23:48 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by roam.psg.com with local (Exim 3.12 #1) id 11zU8S-0000HE-00; Sat, 18 Dec 1999 16:23:40 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Kazutaka YOKOTA Cc: FreeBSD Stable Subject: Re: URGENT! SHOW STOPPER! moused is broken! Message-Id: Date: Sat, 18 Dec 1999 16:23:40 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I apologize again to anybody who have been waiting for 3.4-RELEASE > for causing this delay. > > It was my fault that my last-minute MFC actually broke something. > I will be more cautious in the future. i demand a full refund! :-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 16:24:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from roam.psg.com (roam.psg.com [147.28.4.2]) by hub.freebsd.org (Postfix) with ESMTP id 49B7914D48 for ; Sat, 18 Dec 1999 16:24:25 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by roam.psg.com with local (Exim 3.12 #1) id 11zU95-0000HI-00; Sat, 18 Dec 1999 16:24:19 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mikhail Teterin Cc: FreeBSD Stable Subject: Re: StarOffice5 and SMP Message-Id: Date: Sat, 18 Dec 1999 16:24:19 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So, the combination in subject is still incompatible on -stable? still? don't tell my desktop! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 17: 0:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id D4ED015168; Sat, 18 Dec 1999 17:00:24 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id C75CF1CD739; Sat, 18 Dec 1999 17:00:24 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 18 Dec 1999 17:00:24 -0800 (PST) From: Kris Kennaway To: Stan Brown Cc: FreeBSD Stable List Subject: Re: Sys Admin article on Linux emulation In-Reply-To: <199912181557.HAA22996@netcom.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 Sat, 18 Dec 1999, Stan Brown wrote: > The author says he is running CURRENT> He rcomends several options to > be set in ones kernel config file. Are these option appropriate for a > machine runing STABLE? Uh, what are the options? :-) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 17: 4:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id F0ED814A0D; Sat, 18 Dec 1999 17:04:15 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E42A01CD739; Sat, 18 Dec 1999 17:04:15 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 18 Dec 1999 17:04:15 -0800 (PST) From: Kris Kennaway To: Martin Blapp Cc: stable@freebsd.org Subject: Re: upgrade problem from 3.2 -> 3.4 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 Sat, 18 Dec 1999, Martin Blapp wrote: > cvsup to the newest 3.X sources .. > cd /usr/src && make buildworld && make installworld > cd /usr/src/includes && make depend && make && make install This is done as part of make world - no need to do it twice. 'make world' is exactly the same as your make buildworld && make installworld, so you can save yourself a few keystrokes there :-) I don't know about your problem, I'm afraid. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 17:16:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 27FDF14C08 for ; Sat, 18 Dec 1999 17:16:48 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id SAA09237; Sat, 18 Dec 1999 18:16:46 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912190116.SAA09237@freeway.dcfinc.com> Subject: Re: ld.so failed: Can't find shared library.. In-Reply-To: <13931.991217@Home.Com> from Ben WIlliams at "Dec 17, 99 10:21:51 pm" To: williamsl@Home.Com Date: Sat, 18 Dec 1999 18:16:45 -0700 (MST) Cc: 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, Ben WIlliams wrote: > One of the servers I now manage is a 2.2.5-RELEASE server. I > recently tried running cvsup from a shell and got: [snip] > What are my upgrade options? This is a production server with > little tolerance for downtime and I haven't been a FreeBSD'er for long > enough to know exactly how to fix these problems. I've got several production machines running 2.2-STABLE. The upgrade to that should be fairly easy. CVSup RELENG_2_2, make world, run mergemaster to update your /etc files. I don't know if that will solve your build problems, though. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 18:14:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from po3.glue.umd.edu (po3.glue.umd.edu [128.8.10.123]) by hub.freebsd.org (Postfix) with ESMTP id EF2481519D for ; Sat, 18 Dec 1999 18:14:37 -0800 (PST) (envelope-from bfoz@glue.umd.edu) Received: from glue.umd.edu (poseidon.student.umd.edu [129.2.220.99]) by po3.glue.umd.edu (8.9.3/8.9.3) with ESMTP id VAA26562; Sat, 18 Dec 1999 21:14:13 -0500 (EST) Message-ID: <385C3F5E.576DC7C0@glue.umd.edu> Date: Sat, 18 Dec 1999 21:13:50 -0500 From: Brandon Fosdick X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Martin Blapp Cc: Andre LeClaire , stable@FreeBSD.ORG Subject: Re: upgrade problem from 3.2 -> 3.4 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Martin Blapp wrote: > > Hi, > > > Martin, > > Have you tried doing a make clean in the kernel compile directory > > (probably in your case /usr/src/sys/compile/GENERIC)? I've had similar > > I did a config -r, so this will not help. Can anyone else with a 3.2 > system try to upgrade to 3.4RC ? I'm sure it is a general problem. > > Anyways - thanks for your suggestion :) > > Martin I just did it this morning without any problems. I did a developer install from a 3.2 cd and then cvsup'd to -stable. worked fine. -Brandon -- bfoz@glue.umd.edu "Lead, follow, or get run over" "In life there are those who steer, and those who push" "I'm not impatient, the world is too slow" "Life is short, so have fun, play hard, and leave a good looking corpse" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 18:55:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id E36F51503C for ; Sat, 18 Dec 1999 18:55:13 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id VAA95853; Sat, 18 Dec 1999 21:55:12 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id VAA17874; Sat, 18 Dec 1999 21:55:12 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912190255.VAA17874@rtfm.newton> Subject: Re: StarOffice5 and SMP In-Reply-To: from Randy Bush at "Dec 18, 1999 04:24:19 pm" To: Randy Bush Date: Sat, 18 Dec 1999 21:55:12 -0500 (EST) Cc: Mikhail Teterin , FreeBSD Stable X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" So, the combination in subject is still incompatible on -stable? = =still? don't tell my desktop! Did you have to boot a single cpu kernel to finish the install? For me, the /net-install works fine, but the personal then hangs at the end, and soffice then simply hangs at startup... Did not try it with a non-SMP kernel yet... -mi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 19:24:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from roam.psg.com (roam.psg.com [206.163.43.51]) by hub.freebsd.org (Postfix) with ESMTP id 5918015166 for ; Sat, 18 Dec 1999 19:24:46 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by roam.psg.com with local (Exim 3.12 #1) id 11zWxh-0000LE-00; Sat, 18 Dec 1999 19:24:45 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Mikhail Teterin Cc: FreeBSD Stable Subject: Re: StarOffice5 and SMP References: <199912190255.VAA17874@rtfm.newton> Message-Id: Date: Sat, 18 Dec 1999 19:24:45 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > => So, the combination in subject is still incompatible on -stable? > = > =still? don't tell my desktop! > > Did you have to boot a single cpu kernel to finish the install? i think so. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 20:28: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 4424D14DEA for ; Sat, 18 Dec 1999 20:28:01 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-1-145.dialup.rdu.ipass.net [209.170.132.145]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id XAA24075 for ; Sat, 18 Dec 1999 23:27:56 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id XAA40096 for stable@freebsd.org; Sat, 18 Dec 1999 23:28:38 -0500 (EST) (envelope-from rhh) Date: Sat, 18 Dec 1999 23:28:38 -0500 From: Randall Hopper To: stable@freebsd.org Subject: Help -stable users: where is "mkstemps()" Message-ID: <19991218232837.A39838@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone with a -stable system run this in their src/lib tree?: find /usr/src/lib | xargs grep -l mkstemps Thanks a bunch! I pulled the latest gcc295, and won't even dynamically link on my system since I have no mkstemps in my libc. From past posts, I see mkstemps was added to libc recently. But which libc source file defines this symbol? I want to grab it, patch it into my libc, and rebuild, but I need to know which source file. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 18 20:51:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from team7.cba.ualr.edu (team7.cba.ualr.edu [144.167.120.24]) by hub.freebsd.org (Postfix) with ESMTP id BB13914BDE for ; Sat, 18 Dec 1999 20:51:46 -0800 (PST) (envelope-from joe@team7.cba.ualr.edu) Received: from access18.mod1.ualr.edu (access18.mod1.ualr.edu [144.167.7.18]) by team7.cba.ualr.edu (8.8.8/8.8.8) with ESMTP id WAA25974; Sat, 18 Dec 1999 22:52:04 -0600 (CST) Date: Sat, 18 Dec 1999 22:51:43 -0600 (CST) From: Joe X-Sender: joe@njal.ualr.edu To: Randall Hopper Cc: stable@FreeBSD.ORG Subject: Re: Help -stable users: where is "mkstemps()" In-Reply-To: <19991218232837.A39838@ipass.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 Sat, 18 Dec 1999, Randall Hopper wrote: > Can someone with a -stable system run this in their src/lib tree?: > > find /usr/src/lib | xargs grep -l mkstemps > > Thanks a bunch! > > I pulled the latest gcc295, and won't even dynamically link on my system > since I have no mkstemps in my libc. From past posts, I see mkstemps was > added to libc recently. But which libc source file defines this symbol? I > want to grab it, patch it into my libc, and rebuild, but I need to know > which source file. > > Randall > Is this what you are looking for? bash-2.03$ find /usr/src/lib | xargs grep -l mkstemps /usr/src/lib/libc/stdio/Makefile.inc /usr/src/lib/libc/stdio/mktemp.3 /usr/src/lib/libc/stdio/mktemp.c -Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 0:50:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from poseidon.atomicmatrix.net (poseidon.atomicmatrix.net [146.115.71.116]) by hub.freebsd.org (Postfix) with ESMTP id C01B01522C for ; Sun, 19 Dec 1999 00:50:34 -0800 (PST) (envelope-from ben-lists@atomicmatrix.net) Received: from energizer (energizer.atomicmatrix.net [146.115.71.106]) by poseidon.atomicmatrix.net (8.9.3/8.9.0/1.0-bcg) with SMTP id DAA00377; Sun, 19 Dec 1999 03:49:46 -0500 (EST) Message-ID: <00a501bf49fe$46cc7af0$6a477392@dsg.atomicmatrix.net> From: "Ben Goodwin" To: "Oliver Blasnik" , "Jeffrey J. Libman" , References: <008b01bf466b$71d1c0c0$c20effd4@jav.net> Subject: Re: mountd and rpc.statd won't run Date: Sun, 19 Dec 1999 03:51:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Indeed I ran into this problem just yesterday. I have found that all my 3.3-RELEASE boxes didn't configure a lo0 by default! I'd consider that a bug :-) I used the 'custom' configuration of the sysinstall program for all my 3.3-R installs which didn't end up with a configged lo0.. I don't know if other install types would have done it. FWIW There were NO references to lo0 in /etc/rc.conf. -=| Ben > Check out ifconfig for lo0. Is localhost 127.0.0.1 bound to it? > > No? Then: edit rc.conf, change: > network_interfaces="ed0 lo0" (or whatever card you have). > > If this doesn't help, go the hard way an add > ifconfig_lo0="inet 127.0.0.1 netmask 255.0.0.0" > as a primary adress. > > I did both to get shure and rebooted. Did work very well after that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 1:32: 0 1999 Delivered-To: freebsd-stable@freebsd.org Received: from picalon.gun.de (picalon.gun.de [192.109.159.1]) by hub.freebsd.org (Postfix) with ESMTP id 6184F14C12 for ; Sun, 19 Dec 1999 01:31:58 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.9.3/8.9.3) with ESMTP id KAA29649; Sun, 19 Dec 1999 10:31:44 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.3/8.9.3) id KAA70489; Sun, 19 Dec 1999 10:31:15 +0100 (CET) (envelope-from andreas) Date: Sun, 19 Dec 1999 10:31:14 +0100 From: Andreas Klemm To: Mikhail Teterin Cc: Randy Bush , FreeBSD Stable Subject: Re: StarOffice5 and SMP Message-ID: <19991219103114.B69804@titan.klemm.gtn.com> References: <199912190255.VAA17874@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912190255.VAA17874@rtfm.newton>; from mi@kot.ne.mediaone.net on Sat, Dec 18, 1999 at 09:55:12PM -0500 X-Operating-System: FreeBSD 3.4-STABLE SMP X-Disclaimer: A free society is one where it is safe to be unpopular Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 18, 1999 at 09:55:12PM -0500, Mikhail Teterin wrote: > Randy Bush once stated: > > => So, the combination in subject is still incompatible on -stable? > = > =still? don't tell my desktop! > > Did you have to boot a single cpu kernel to finish the install? For me, > the /net-install works fine, but the personal then hangs at the end, and > soffice then simply hangs at startup... > > Did not try it with a non-SMP kernel yet... I wasn't unable to finish the user installation part successfully make install-user using a SMP kernel. After having copied 99% the staroffice window freezes. I have to do a kill -15, to let it finish. In the console window I see messages like: shared address space fork attempted pid=xxxxx With an uniprocessor kernel installation went o.k. Well, next to try is, if the completely installed staroffice can run on a SMP kernel. But I couldn't test it because of space restrictions when building a FreeBSD 3.4 release. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas http://www.freebsd.org/~fsmp/SMP/SMP.html powered by Symmetric MultiProcessor FreeBSD Get new songs from our band: http://www.freebsd.org/~andreas/64bits/index.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 1:38:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51]) by hub.freebsd.org (Postfix) with ESMTP id D586B1517A for ; Sun, 19 Dec 1999 01:38:55 -0800 (PST) (envelope-from marisombra@pop.mindspring.com) Received: from mindspring (user-2iveeos.dialup.mindspring.com [165.247.59.28]) by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id EAA06547; Sun, 19 Dec 1999 04:38:37 -0500 (EST) Message-Id: <4.2.2.19991219042243.00b3de70@pop.mindspring.com> X-Sender: marisombra@pop.mindspring.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sun, 19 Dec 1999 04:24:07 -0500 To: "Ben Goodwin" , "Oliver Blasnik" , "Jeffrey J. Libman" , From: Trilce Subject: Re: mountd and rpc.statd won't run In-Reply-To: <00a501bf49fe$46cc7af0$6a477392@dsg.atomicmatrix.net> References: <008b01bf466b$71d1c0c0$c20effd4@jav.net> Mime-Version: 1.0 Content-Type: text/plain Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I installed 3.3-Release and lo0 was (still is) working. I also did custom install. At 03:51 AM 12/19/99 , Ben Goodwin wrote: >Indeed I ran into this problem just yesterday. I have found that all my >3.3-RELEASE boxes didn't configure a lo0 by default! I'd consider that a >bug :-) >I used the 'custom' configuration of the sysinstall program for all my 3.3-R >installs which didn't end up with a configged lo0.. I don't know if other >install types would have done it. >FWIW There were NO references to lo0 in /etc/rc.conf. > > -=| Ben > > > Check out ifconfig for lo0. Is localhost 127.0.0.1 bound to it? > > > > No? Then: edit rc.conf, change: > > network_interfaces="ed0 lo0" (or whatever card you have). > > > > If this doesn't help, go the hard way an add > > ifconfig_lo0="inet 127.0.0.1 netmask 255.0.0.0" > > as a primary adress. > > > > I did both to get shure and rebooted. Did work very well after that. > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-stable" in the body of the message -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.5.2 for non-commercial use iQA/AwUBOFykN/PJ9x2Gbj/sEQKAyACg7pSCTnzyzlgjg0S17UgigriUPzwAoOBh ClujpkDJqc2GhDcFtp+9z60/ =M3pn -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 5:21:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id CFD6414E72 for ; Sun, 19 Dec 1999 05:21:35 -0800 (PST) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-p2-83.hitter.net [207.192.76.83]) by pawn.primelocation.net (Postfix) with ESMTP id 204EE9B4C; Sun, 19 Dec 1999 08:21:05 -0500 (EST) Date: Sun, 19 Dec 1999 08:20:52 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Ben Goodwin Cc: Oliver Blasnik , "Jeffrey J. Libman" , freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-Reply-To: <00a501bf49fe$46cc7af0$6a477392@dsg.atomicmatrix.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 Sun, 19 Dec 1999, Ben Goodwin wrote: > Indeed I ran into this problem just yesterday. I have found that all my > 3.3-RELEASE boxes didn't configure a lo0 by default! I'd consider that a > bug :-) > I used the 'custom' configuration of the sysinstall program for all my 3.3-R > installs which didn't end up with a configged lo0.. I don't know if other > install types would have done it. > FWIW There were NO references to lo0 in /etc/rc.conf. > Yes, see http://www.freebsd.org/releases/3.3R/errata.html (aka ERRATA.TXT) for this and other possible problems. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@freebsd.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 5:36:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id BA4B715099 for ; Sun, 19 Dec 1999 05:36:40 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-4-248.dialup.rdu.ipass.net [209.170.134.248]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id IAA04095; Sun, 19 Dec 1999 08:36:32 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id IAA12917; Sun, 19 Dec 1999 08:37:11 -0500 (EST) (envelope-from rhh) Date: Sun, 19 Dec 1999 08:37:11 -0500 From: Randall Hopper To: Joe , Mikhail Teterin Cc: stable@FreeBSD.ORG Subject: Re: Help -stable users: where is "mkstemps()" Message-ID: <19991219083711.A12831@ipass.net> References: <19991218232837.A39838@ipass.net> <19991218232837.A39838@ipass.net> <199912190456.XAA18639@rtfm.newton> <19991218232837.A39838@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG |Is this what you are looking for? | |bash-2.03$ find /usr/src/lib | xargs grep -l mkstemps |/usr/src/lib/libc/stdio/Makefile.inc |/usr/src/lib/libc/stdio/mktemp.3 |/usr/src/lib/libc/stdio/mktemp.c Thanks, that's what I needed! Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 6:39:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.bna.bellsouth.net (mail1.bna.bellsouth.net [205.152.150.13]) by hub.freebsd.org (Postfix) with ESMTP id 67D1414FD5 for ; Sun, 19 Dec 1999 06:39:08 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-209-214-40-124.cha.bellsouth.net [209.214.40.124]) by mail1.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id JAA09319 for ; Sun, 19 Dec 1999 09:39:08 -0500 (EST) Message-ID: <385CEE54.A644A358@siteplus.com> Date: Sun, 19 Dec 1999 09:40:20 -0500 From: Jim Weeks X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i486) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: 3.4-19991218-STABLE kernel build fails Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I installed fresh on an old machine yesterday and when I try to make the new kernel I get this message, In file included from ../../msdosfs/msdosfs_denode.c:66: ../../msdosfs/denode.h:282: macro '__P' used with too many (2) args *** Error code 1 The only thing I have added to the system at this point is /usr/src/sys/i386/isa/sio.c with two additional pnp entries. Jim Weeeks jim@siteplus.com http://siteplus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 8:40:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from erouter0.it-datacntr.louisville.edu (erouter0.it-datacntr.louisville.edu [136.165.1.36]) by hub.freebsd.org (Postfix) with ESMTP id 049B0151BE for ; Sun, 19 Dec 1999 08:40:07 -0800 (PST) (envelope-from k.stevenson@louisville.edu) Received: from osaka.louisville.edu (osaka.louisville.edu [136.165.1.114]) by erouter0.it-datacntr.louisville.edu (Postfix) with ESMTP id B6EF324D29; Sun, 19 Dec 1999 11:40:06 -0500 (EST) Received: by osaka.louisville.edu (Postfix, from userid 15) id 64AD418605; Sun, 19 Dec 1999 11:39:56 -0500 (EST) Date: Sun, 19 Dec 1999 11:39:56 -0500 From: Keith Stevenson To: Rob King Cc: freebsd-stable@freebsd.org Subject: Re: XDM, KDM, PAM, FreeBSD, and a partridge in a pear tree... Message-ID: <19991219113956.A16911@osaka.louisville.edu> References: <199912191156.FAA21939@mail.pernet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912191156.FAA21939@mail.pernet.net> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Follow-ups redirected to freebsd-stable) On Sun, Dec 19, 1999 at 05:56:13AM -0600, Rob King wrote: > > Here's the problem: I'm running a fresh install of 3.3-STABLE, and trying to > get the nice graphical login, with either XDM or KDM. Unfortunantly, I get an > 'incorrect password' error no matter what I type. I also get a "pam: no > modules loaded for xdm service" or kdm service, depending. I have a line in my > /etc/pam.conf: > > xdm auth required pam_unix.so try_first_pass > > Unfortunantly, no matter what happens, neither KDM nor XDM will recognize me. > Any ideas, anyone? Have you tweaked your /etc/pam.conf? My copy of /etc/pam.conf doesn't have an xdm line and I login via XDM all the time. I'm using /etc/pam.conf version # $FreeBSD: src/etc/pam.conf,v 1.1 1998/11/20 23:20:01 jdp Exp $ which is the most recent version on the RELENG_3 branch. (FreeBSD 3.4-STABLE) From looking at the tags on the file, this file hasn't changed since at least 3.1. Regards, --Keith Stevenson-- -- Keith Stevenson System Programmer - Data Center Services - University of Louisville k.stevenson@louisville.edu PGP key fingerprint = 4B 29 A8 95 A8 82 EA A2 29 CE 68 DE FC EE B6 A0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 9: 6:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc2.on.home.com (ha1.rdc2.on.home.com [24.9.0.15]) by hub.freebsd.org (Postfix) with ESMTP id B559E14FB2 for ; Sun, 19 Dec 1999 09:06:53 -0800 (PST) (envelope-from greg@snickers.org) Received: from cs219478a ([24.66.4.247]) by mail.rdc2.on.home.com (InterMail v4.01.01.07 201-229-111-110) with SMTP id <19991219170653.LAJS18919.mail.rdc2.on.home.com@cs219478a>; Sun, 19 Dec 1999 09:06:53 -0800 Reply-To: From: "Greg Prosser" To: "Martin Blapp" , Subject: RE: upgrade problem from 3.2 -> 3.4 Date: Sun, 19 Dec 1999 12:07:02 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've cvsup'd and rebuilt systems before, following the instructions in the handbook at first, now committed to memory, but I've never heard of make install from within /usr/src/include. I would believe that would be covered under the make buildworld/installworld targets under /usr/src? > I made the following steps before: > > cvsup to the newest 3.X sources .. > cd /usr/src && make buildworld && make installworld > cd /usr/src/includes && make depend && make && make install > config -r GENERIC . . . ... .. . .. .... . g r e g @ s n i c k e r s . o r g .-----.----.-----.-----. lack of planning on your part does =not= | _ | _| -__| _ | consitute an emergency on my part. |___ |__| |_____|___ | icq: 10405504 aol im: xysters |_____| |_____| To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 10:12:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles510.castles.com [208.214.165.74]) by hub.freebsd.org (Postfix) with ESMTP id CC1D715137 for ; Sun, 19 Dec 1999 10:12:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA02792; Sun, 19 Dec 1999 10:16:09 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912191816.KAA02792@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Ben Goodwin" Cc: "Oliver Blasnik" , "Jeffrey J. Libman" , freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-reply-to: Your message of "Sun, 19 Dec 1999 03:51:43 EST." <00a501bf49fe$46cc7af0$6a477392@dsg.atomicmatrix.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Dec 1999 10:16:09 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Indeed I ran into this problem just yesterday. I have found that all my > 3.3-RELEASE boxes didn't configure a lo0 by default! I'd consider that a > bug :-) You'd be wrong. There's an ifconfig_lo0 entry in the defaults file. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 11:19:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 33E9E14E40; Sun, 19 Dec 1999 11:19:57 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 57C551C2B; Sun, 19 Dec 1999 14:19:30 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 4A96B381B; Sun, 19 Dec 1999 14:19:30 -0500 (EST) Date: Sun, 19 Dec 1999 14:19:30 -0500 (EST) From: Bill Fumerola To: Mike Smith Cc: Ben Goodwin , Oliver Blasnik , "Jeffrey J. Libman" , freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-Reply-To: <199912191816.KAA02792@mass.cdrom.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 Sun, 19 Dec 1999, Mike Smith wrote: > > Indeed I ran into this problem just yesterday. I have found that all my > > 3.3-RELEASE boxes didn't configure a lo0 by default! I'd consider that a > > bug :-) > > You'd be wrong. There's an ifconfig_lo0 entry in the defaults file. Don't be so sure that he's wrong. We installed a lot of 3.3 machines here when it first came out and some of them had NIS issues which actually were the result of lo0 not being configured by default. It didn't happen on every machine which led me to believe it was probably different sysinstall incantations that did it, unfortunatly I didn't have time to track down exactly what those incantations were. -- - 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 Sun Dec 19 11:29:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 1BA7B14FB2 for ; Sun, 19 Dec 1999 11:29:51 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991219192950.KNWM9446.mail.rdc1.ct.home.com@home.com> for ; Sun, 19 Dec 1999 11:29:50 -0800 Message-ID: <385D322B.373B6738@home.com> Date: Sun, 19 Dec 1999 14:29:47 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: FreeBSD-stable@FreeBSD.ORG Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe FreeBSD-stable To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 11:32:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles510.castles.com [208.214.165.74]) by hub.freebsd.org (Postfix) with ESMTP id E3B01151D7 for ; Sun, 19 Dec 1999 11:32:30 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA03084; Sun, 19 Dec 1999 11:36:11 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912191936.LAA03084@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bill Fumerola Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-reply-to: Your message of "Sun, 19 Dec 1999 14:19:30 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Dec 1999 11:36:11 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Sun, 19 Dec 1999, Mike Smith wrote: > > > > Indeed I ran into this problem just yesterday. I have found that all my > > > 3.3-RELEASE boxes didn't configure a lo0 by default! I'd consider that a > > > bug :-) > > > > You'd be wrong. There's an ifconfig_lo0 entry in the defaults file. > > Don't be so sure that he's wrong. We installed a lot of 3.3 machines here > when it first came out and some of them had NIS issues which actually > were the result of lo0 not being configured by default. > > It didn't happen on every machine which led me to believe it was probably > different sysinstall incantations that did it, unfortunatly I didn't have > time to track down exactly what those incantations were. That's called "inadmissible evidence". Unless you can come up with something that categorically suggests that your testing is more valid than ours, I don't think you're helping. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 11:38:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id E2E26151B2; Sun, 19 Dec 1999 11:38:25 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 2B4BF1C2B; Sun, 19 Dec 1999 14:37:59 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 1D5F5381B; Sun, 19 Dec 1999 14:37:59 -0500 (EST) Date: Sun, 19 Dec 1999 14:37:59 -0500 (EST) From: Bill Fumerola To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-Reply-To: <199912191936.LAA03084@mass.cdrom.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 Sun, 19 Dec 1999, Mike Smith wrote: > That's called "inadmissible evidence". Unless you can come up with > something that categorically suggests that your testing is more valid > than ours, I don't think you're helping. And this is is "selective concern" that is being shown. I know that the machines didn't config lo0 by default, I was there. I'm not complaining or calling for a fix, because my recent batch of installations (5 or so Dell PowerEdge 4350s with 4.0-CURRENT snapshots) didn't display this behavior. I'm just suggesting we not just discredit the original poster, because it did happen. It's been about 3 months, but I think the original cause was network_interfaces only containing the ethernet card after installation. -- - 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 Sun Dec 19 11:38:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vkhdib01.hda.hydro.com (vkhdib01.hda.hydro.com [136.164.216.55]) by hub.freebsd.org (Postfix) with ESMTP id 4FEA915179; Sun, 19 Dec 1999 11:38:49 -0800 (PST) (envelope-from Terje.Mathisen@hda.hydro.com) Received: from no115350p4 ([136.164.13.19]) by vkhdib01.hda.hydro.com (8.8.8/8.8.7) with SMTP id UAA146920; Sun, 19 Dec 1999 20:38:47 +0100 Message-ID: <385D3445.25D2@hda.hydro.com> Date: Sun, 19 Dec 1999 20:38:45 +0100 From: Terje Mathisen Organization: Hydro X-Mailer: Mozilla 3.04Gold (WinNT; I) MIME-Version: 1.0 To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run References: <199912191936.LAA03084@mass.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 Mike Smith wrote: > > It didn't happen on every machine which led me to believe it was probably > > different sysinstall incantations that did it, unfortunatly I didn't have > > time to track down exactly what those incantations were. > > That's called "inadmissible evidence". Unless you can come up with > something that categorically suggests that your testing is more valid > than ours, I don't think you're helping. This probably won't help either, but I had exactly the same problems after doing a (from scratch) plain vanilla installation of 3.3-RELEASE. Manually configuring lo0 was needed to bring it up. This happened on an old Dell Optiplex (Pentium-133) with a 1GB IDE disk, and a 3COM PCI ethernet card. The same installation on a Compaq Presario (PII-300) was fine. Terje -- - Using self-discipline, see http://www.eiffel.com/discipline "almost all programming can be viewed as an exercise in caching" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 12: 2:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from grey.cloud.rain.com (c1029014-a.bvrtn1.or.home.com [24.12.160.67]) by hub.freebsd.org (Postfix) with ESMTP id 4719F14EBD for ; Sun, 19 Dec 1999 12:02:24 -0800 (PST) (envelope-from trost@grey.cloud.rain.com) Received: (qmail 38964 invoked from network); 19 Dec 1999 20:02:23 -0000 Received: from localhost.cloud.rain.com (HELO grey.cloud.rain.com) (@127.0.0.1) by localhost.cloud.rain.com with SMTP; 19 Dec 1999 20:02:23 -0000 To: stable@freebsd.org Subject: 3.4-19991219-STABLE upgrade crash MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <38960.945633742.1@grey.cloud.rain.com> Date: Sun, 19 Dec 1999 12:02:22 -0800 Message-ID: <38961.945633742@grey.cloud.rain.com> From: Bill Trost Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to upgrade my Fujitsu 635Tx from an a.out version of FreeBSD to the above-mentioned snapshot, and when I select "Custom" to identify the distribution sets I want, I get a signal 11 notification. I turned debugging on (at least, I think I did -- the options screen was largely black-on-black) and saw the following debug output on vty1: DEBUG: Command `/stand/gunzip < /stand/help/distributions.hlp.gz > /tmp/.doc/doc.tmp' returns status of 0 DEBUG: Signal 11 caught! That's bad! (Oh, really? :-) Thoughts, anyone? Thanks. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 14:15:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.ihug.co.nz (tk2.ihug.co.nz [203.29.160.14]) by hub.freebsd.org (Postfix) with ESMTP id 71FE615233 for ; Sun, 19 Dec 1999 14:15:49 -0800 (PST) (envelope-from mmuir@es.co.nz) Received: from es.co.nz (p45-max4.dun.ihug.co.nz [209.76.100.236]) by smtp2.ihug.co.nz (8.9.3/8.9.3/Debian/GNU) with ESMTP id LAA01392 for ; Mon, 20 Dec 1999 11:15:44 +1300 Message-ID: <385D590E.D948E3F0@es.co.nz> Date: Sun, 19 Dec 1999 22:15:42 +0000 From: Mike Muir X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Fumerola wrote: > I'm just suggesting we not just discredit the original poster, because it > did happen. It's been about 3 months, but I think the original cause was > network_interfaces only containing the ethernet card after installation. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ That was most certainly the case for me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 14:21:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id C33E315248 for ; Sun, 19 Dec 1999 14:21:54 -0800 (PST) (envelope-from billf@chc-chimes.com) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id 8FC781C4A; Sun, 19 Dec 1999 17:21:27 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by jade.chc-chimes.com (Postfix) with ESMTP id 8C87F381B; Sun, 19 Dec 1999 17:21:27 -0500 (EST) Date: Sun, 19 Dec 1999 17:21:27 -0500 (EST) From: Bill Fumerola To: Mike Muir Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-Reply-To: <385D590E.D948E3F0@es.co.nz> 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, 19 Dec 1999, Mike Muir wrote: > > I'm just suggesting we not just discredit the original poster, because it > > did happen. It's been about 3 months, but I think the original cause was > > network_interfaces only containing the ethernet card after installation. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > That was most certainly the case for me. Just to put an end to this thread: this problem is even in the 3.3 ERRATA, so it is a well known problem. -- - 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 Sun Dec 19 14:29:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from timber-wolf.Bushong.NET (c128625-a.frmt1.sfba.home.com [24.5.196.12]) by hub.freebsd.org (Postfix) with ESMTP id 3CEF8152A8 for ; Sun, 19 Dec 1999 14:29:35 -0800 (PST) (envelope-from dbushong@timber-wolf.Bushong.NET) Received: (from dbushong@localhost) by timber-wolf.Bushong.NET (8.9.3/8.9.3) id OAA13882 for freebsd-stable@freebsd.org; Sun, 19 Dec 1999 14:29:34 -0800 (PST) (envelope-from dbushong) Date: Sun, 19 Dec 1999 14:29:34 -0800 From: David Bushong To: freebsd-stable@freebsd.org Subject: CVS directories in /usr/ports/*/* ? Message-ID: <19991219142934.A13865@Bushong.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been writing a freshmeat clone that works off of the ports tree (and my nightly cvsups of it) and was originally using some information gleaned from doing things like cvs log on /usr/ports/category/portname/Makefile. As I've been cvsupping though, I've noticed that fewer and fewer (all?) new ports have no CVS subdirectory. In fact, doing an ls -lrdt /usr/ports/*/*/CVS, it looks like the last time a new one was created was July 10th or so. Anyone know what happened to these? They're handy to have, since I in fact have a ports CVS mirror.. --David Bushong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 14:35:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 55BE2151A6 for ; Sun, 19 Dec 1999 14:35:10 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id CA3B49B4D; Sun, 19 Dec 1999 17:35:08 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id C0C83BA0C; Sun, 19 Dec 1999 17:35:08 -0500 (EST) Date: Sun, 19 Dec 1999 17:35:08 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: David Bushong Cc: freebsd-stable@freebsd.org Subject: Re: CVS directories in /usr/ports/*/* ? In-Reply-To: <19991219142934.A13865@Bushong.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 Sun, 19 Dec 1999, David Bushong wrote: > As I've been cvsupping though, I've noticed that fewer and fewer (all?) new > ports have no CVS subdirectory. In fact, doing an ls -lrdt /usr/ports/*/*/CVS, > it looks like the last time a new one was created was July 10th or so. Anyone > know what happened to these? They're handy to have, since I in fact have a > ports CVS mirror.. > The CVS directories are used by cvs, not cvsup. If you want to use them, updates your ports tree using cvs. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@freebsd.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 15: 5:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 37CC414CC4 for ; Sun, 19 Dec 1999 15:05:34 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-4-228.dialup.rdu.ipass.net [209.170.134.228]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id SAA15777 for ; Sun, 19 Dec 1999 18:05:16 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id SAA58263 for stable@freebsd.org; Sun, 19 Dec 1999 18:05:57 -0500 (EST) (envelope-from rhh) Date: Sun, 19 Dec 1999 18:05:57 -0500 From: Randall Hopper To: stable@freebsd.org Subject: AMD 3DNow instructions on FreeBSD Message-ID: <19991219180557.A58177@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. Is there a FreeBSD assembler out there which supports the AMD 3DNow instruction set? Why I ask: I attempted to build GLX/Mesa3.1 with 3DNow support, and it bombed since our assembler isn't 3DNow-knowledgable (femms, pfmul, etc. undefined). The assembler in -stable has the same shortcoming AFAICT. Facts? Rumors? I'm interested in anything you may know. Thanks, Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 15:24: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id 2F22314F05 for ; Sun, 19 Dec 1999 15:24:08 -0800 (PST) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn1021.bossig.com [208.26.241.21]) by corinth.bossig.com (Rockliffe SMTPRA 3.4.5) with ESMTP id for ; Sun, 19 Dec 1999 15:31:02 -0800 Message-ID: <385D68FF.58570580@3-cities.com> Date: Sun, 19 Dec 1999 15:23:43 -0800 From: Kent Stewart X-Mailer: Mozilla 4.61 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: User-ppp on 3.4-Stable Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I ran into a problem today with user-ppp. I was reading about ppp and that is when I got into trouble :). The message log keeps taking about -alias being depricated and so I was trying to get aliasing to work with NAT. That is when I started getting the following message Dec 19 14:36:45 ruby ppp[454]: Warning: No available tunnel devices found (Device busy) This didn't occur on 3.3S, when I used pppctl to close down user-ppp. At least, I don't remember ever seeing that message before. User-ppp seems to be very sensitive to rebooting the system while it is still running. I have it configured, from the sample.conf, to use /var/run/internet and that local domain socket is left around if it shuts down badly. User-ppp won't start if it already exists. It is a simple matter to cd to /var/run and rm it, which will allow ppp to start. It is easy to make ppp leave /var/run/internet. All you have to do is use top to kill the process. The system was cvsup'ed on 18 Dec (19 Dec UTC) and the make world was done on 19 Dec. When I tried starting user-ppp with the -nat option, I didn't get aliasing for my other systems. I figure I am missing something but don't know what. The -alias still works but I want to switch to the curent style. Thanks. Kent To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 15:33:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail0.bna.bellsouth.net (mail0.bna.bellsouth.net [205.152.150.12]) by hub.freebsd.org (Postfix) with ESMTP id D372B14D0D for ; Sun, 19 Dec 1999 15:33:52 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-216-78-83-89.cha.bellsouth.net [216.78.83.89]) by mail0.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id SAA11865 for ; Sun, 19 Dec 1999 18:33:41 -0500 (EST) Message-ID: <385D6B6D.3F343EED@siteplus.com> Date: Sun, 19 Dec 1999 18:34:05 -0500 From: Jim Weeks X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i486) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: 3.4-19991218-STABLE kernel build fails References: <385CEE54.A644A358@siteplus.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, I didn't get any response to this post and have since tried numerous things to correct this error. I have now installed 3.4-19991219-STABLE from snapshots and receive a different error when I try building a new kernel. Everything seemed to install ok and make depend went well, but when doing make I get this error. sentinel# make cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../cam/scsi/scsi_cd.c In file included from ../../cam/scsi/scsi_cd.c:60: ../../sys/cdio.h:91: warning: useless keyword or type name in empty declaration ../../sys/cdio.h:91: warning: empty declaration ../../sys/cdio.h:91: parse error before `_' ../../sys/cdio.h:91: warning: no semicolon at end of struct or union ../../sys/cdio.h:92: warning: data definition has no type or storage class ../../sys/cdio.h:92: parse error before `}' ../../sys/cdio.h:96: syntax error before `{' ../../sys/cdio.h:98: warning: data definition has no type or storage class ../../sys/cdio.h:98: parse error before `osiricn' ../../sys/cdio.h:100: warning: data definition has no type or storage class ../../sys/cdio.h:100: parse error before `rscr_cn' ../../sys/cdio.h:100: warning: data definition has no type or storage class ../../sys/cdio.h:100: parse error before `t' ../../sys/cdio.h:101: warning: data definition has no type or storage class ../../sys/cdio.h:102: parse error before `/' ../../sys/cdio.h:103: warning: data definition has no type or storage class ../../sys/cdio.h:104: parse error before `}' ../../cam/scsi/scsi_cd.c: In function `cdioctl': ../../cam/scsi/scsi_cd.c:1966: sizeof applied to an incomplete type ../../cam/scsi/scsi_cd.c:1969: sizeof applied to an incomplete type ../../cam/scsi/scsi_cd.c:1991: dereferencing pointer to incomplete type ../../cam/scsi/scsi_cd.c:1992: dereferencing pointer to incomplete type ../../cam/scsi/scsi_cd.c:1993: dereferencing pointer to incomplete type ../../cam/scsi/scsi_cd.c:1994: dereferencing pointer to incomplete type ../../sys/libkern.h:57: warning: inlining failed in call to `min' ../../cam/scsi/scsi_cd.c:1995: warning: called from here *** Error code 1 Any suggestions would be appreciated. Jim Weeks wrote: > I installed fresh on an old machine yesterday and when I try to make the > new kernel I get this message, > > In file included from ../../msdosfs/msdosfs_denode.c:66: > ../../msdosfs/denode.h:282: macro '__P' used with too many (2) args > *** Error code 1 > > The only thing I have added to the system at this point is > /usr/src/sys/i386/isa/sio.c with two additional pnp entries. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 15:42:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id A6E6D15278 for ; Sun, 19 Dec 1999 15:42:20 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 11zpxy-0004Zu-00; Sun, 19 Dec 1999 15:42:18 -0800 Date: Sun, 19 Dec 1999 15:42:14 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Jim Weeks Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: 3.4-19991218-STABLE kernel build fails In-Reply-To: <385D6B6D.3F343EED@siteplus.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 Sun, 19 Dec 1999, Jim Weeks wrote: > Hi again, > > I didn't get any response to this post and have since tried numerous things > to correct this error. I have now installed 3.4-19991219-STABLE from ... Yes, but obviously the kernel does compile, otherwise the snapshot could not have been built. I would try building a GENERIC kernel first. If that works, your config file is junk. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 16:14:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 5664714C04 for ; Sun, 19 Dec 1999 16:14:09 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id AAA53530; Mon, 20 Dec 1999 00:14:08 GMT (envelope-from joe) Date: Mon, 20 Dec 1999 00:14:08 +0000 From: Josef Karthauser To: Mikhail Teterin Cc: stable@FreeBSD.ORG Subject: Re: buildworld dies in i4b/isdnd Message-ID: <19991220001408.C51712@florence.pavilion.net> References: <199912171324.IAA60384@rtfm.newton> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912171324.IAA60384@rtfm.newton> X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you remove your /usr/src/usr.sbin/i4b directory and cvsup again. I'm guessing that you've previously installed a version of i4b 0.83 over the top of the source tree and there's some files that aren't required still in your source tree. Every case so far of failure to compile i4b has been for a reason similar to this. Joe On Fri, Dec 17, 1999 at 08:24:54AM -0500, Mikhail Teterin wrote: > Cvsup-ed 7 hours ago: > > cc -O2 -fexpensive-optimizations -pipe -I/usr/src/usr.sbin/i4b/isdnd/../isdnmonitor -I/usr/src/usr.sbin/i4b/isdnd/../isdntel -I/usr/obj/usr/src/usr.sbin/i4b/isdnd -DDEBUG -DUSE_RTPRIO -DUSE_CURSES -I/usr/obj/usr/src/tmp/usr/include -c /usr/src/usr.sbin/i4b/isdnd/curses.c > /usr/src/usr.sbin/i4b/isdnd/rc_config.c: In function `cfg_setval': > /usr/src/usr.sbin/i4b/isdnd/rc_config.c:269: `BEEPCONNECT' undeclared (first use this function) > /usr/src/usr.sbin/i4b/isdnd/rc_config.c:269: (Each undeclared identifier is reported only once > /usr/src/usr.sbin/i4b/isdnd/rc_config.c:269: for each function it appears in.) > /usr/src/usr.sbin/i4b/isdnd/rc_config.c:380: `IDLE_ALG_OUT' undeclared (first use this function) > /usr/src/usr.sbin/i4b/isdnd/rc_config.c:632: `ROTATESUFFIX' undeclared (first use this function) > /usr/src/usr.sbin/i4b/isdnd/rc_config.c:654: `TINAINITPROG' undeclared (first use this function) > [...] > > -mi > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 16:32:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles501.castles.com [208.214.165.65]) by hub.freebsd.org (Postfix) with ESMTP id 95B24151FB for ; Sun, 19 Dec 1999 16:32:22 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03928; Sun, 19 Dec 1999 16:35:57 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912200035.QAA03928@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Muir Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-reply-to: Your message of "Sun, 19 Dec 1999 22:15:42 GMT." <385D590E.D948E3F0@es.co.nz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Dec 1999 16:35:57 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Bill Fumerola wrote: > > > I'm just suggesting we not just discredit the original poster, because it > > did happen. It's been about 3 months, but I think the original cause was > > network_interfaces only containing the ethernet card after installation. > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > That was most certainly the case for me. It would be _so_ much more helpful for someone to actually detail the steps they had followed to get into this state. So far, it's literally easier to believe in mass hallucinations. Give us something more to work on. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 16:38: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles501.castles.com [208.214.165.65]) by hub.freebsd.org (Postfix) with ESMTP id 3F5E014FC5 for ; Sun, 19 Dec 1999 16:38:00 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA03976 for ; Sun, 19 Dec 1999 16:41:42 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912200041.QAA03976@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-reply-to: Your message of "Sun, 19 Dec 1999 16:35:57 PST." <199912200035.QAA03928@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 19 Dec 1999 16:41:42 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Bill Fumerola wrote: > > > > > I'm just suggesting we not just discredit the original poster, because it > > > did happen. It's been about 3 months, but I think the original cause was > > > network_interfaces only containing the ethernet card after installation. > > ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ > > > > That was most certainly the case for me. > > It would be _so_ much more helpful for someone to actually detail the > steps they had followed to get into this state. So far, it's literally > easier to believe in mass hallucinations. Give us something more to work > on. 8) Bah. This is a 3.3-RELEASE not a 3-STABLE issue, never mind. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 16:53:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail0.bna.bellsouth.net (mail0.bna.bellsouth.net [205.152.150.12]) by hub.freebsd.org (Postfix) with ESMTP id 2F50514F47 for ; Sun, 19 Dec 1999 16:53:47 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-216-78-83-89.cha.bellsouth.net [216.78.83.89]) by mail0.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id TAA16706; Sun, 19 Dec 1999 19:53:32 -0500 (EST) Message-ID: <385D7E11.7C1C3350@siteplus.com> Date: Sun, 19 Dec 1999 19:53:37 -0500 From: Jim Weeks X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i486) X-Accept-Language: en MIME-Version: 1.0 To: Tom Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: 3.4-19991218-STABLE kernel build fails References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wrong, GENERIC will not build either. I still get the same errors. The only thing I had changed in my config file was to comment out the devices I do not have, and to change the parameter of ed0. Not much to screw up there. Tom wrote: > On Sun, 19 Dec 1999, Jim Weeks wrote: > > > Hi again, > > > > I didn't get any response to this post and have since tried numerous things > > to correct this error. I have now installed 3.4-19991219-STABLE from > ... > > Yes, but obviously the kernel does compile, otherwise the snapshot could > not have been built. > > I would try building a GENERIC kernel first. If that works, your config > file is junk. > > 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 Sun Dec 19 16:59:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 8A85114F30 for ; Sun, 19 Dec 1999 16:59:57 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 11zrB5-0005iM-00; Sun, 19 Dec 1999 16:59:55 -0800 Date: Sun, 19 Dec 1999 16:59:51 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Jim Weeks Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: 3.4-19991218-STABLE kernel build fails In-Reply-To: <385D7E11.7C1C3350@siteplus.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 Sun, 19 Dec 1999, Jim Weeks wrote: > Wrong, > > GENERIC will not build either. > > I still get the same errors. The only thing I had changed in my config file was > to comment out the devices I do not have, and to change the parameter of ed0. > Not much to screw up there. Then your source tree is screwed up, or you aren't building the kernel properly. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 17:26: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail0.bna.bellsouth.net (mail0.bna.bellsouth.net [205.152.150.12]) by hub.freebsd.org (Postfix) with ESMTP id DD6D814D29 for ; Sun, 19 Dec 1999 17:26:06 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-216-78-83-48.cha.bellsouth.net [216.78.83.48]) by mail0.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id UAA12817; Sun, 19 Dec 1999 20:25:29 -0500 (EST) Message-ID: <385D8591.70E10832@siteplus.com> Date: Sun, 19 Dec 1999 20:25:37 -0500 From: Jim Weeks X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i486) X-Accept-Language: en MIME-Version: 1.0 To: Tom Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: 3.4-19991218-STABLE kernel build fails References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks Tom, I appreciate the input. No one else has had any ideas. I built the kernel as I have built many before. Copy GENERIC to a new name, make changes to fit my hardware, do /usr/sbin/config on the new file. cd to ../../compile/newname and then make depend, make, and eventually make install. This is the first time I have not made it to make install. I have screwed around with this machine all day and need to get it back on line. I installed 19991125 on another machine and had no problems, so I will try that to get things back up. Have a good evening and a great holiday season, Jim Tom wrote: > Then your source tree is screwed up, or you aren't building the kernel > properly. > > 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 Sun Dec 19 17:33: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mta1.rcsntx.swbell.net (mta1.rcsntx.swbell.net [151.164.30.25]) by hub.freebsd.org (Postfix) with ESMTP id 7895315206 for ; Sun, 19 Dec 1999 17:33:03 -0800 (PST) (envelope-from noslenj@swbell.net) Received: from swbell.net ([207.193.44.202]) by mta1.rcsntx.swbell.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FN00048KMYYM8@mta1.rcsntx.swbell.net> for freebsd-stable@FreeBSD.ORG; Sun, 19 Dec 1999 19:33:00 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by swbell.net (8.9.3/8.9.3) with ESMTP id TAA01464; Sun, 19 Dec 1999 19:25:02 -0600 (CST envelope-from noslenj@swbell.net) Date: Sun, 19 Dec 1999 19:25:02 -0600 (CST) From: Jay Nelson Subject: Re: 3.4-19991218-STABLE kernel build fails In-reply-to: <385D6B6D.3F343EED@siteplus.com> To: Jim Weeks 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 On Sun, 19 Dec 1999, Jim Weeks wrote: >Hi again, > >I didn't get any response to this post and have since tried numerous things >to correct this error. I have now installed 3.4-19991219-STABLE from >snapshots and receive a different error when I try building a new kernel. >Everything seemed to install ok and make depend went well, but when doing >make I get this error. [snip] >Any suggestions would be appreciated. I haven't been following this, so this may have been answered. I supped new sources this morning. Everything worked fine. I _did_ delete everything under /usr/src/sys/compile before id did a configon my kernel. (This was after a make depend; make buildworld and a make installworld.) Try deleting /usr/src/sys/compile/ and do a new config and make depend. This has always worked for me -- and I've been bitten when I didn't;) -- Jay To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 17:38:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wcn4.wcnet.net (mail.wcnet.net [216.88.248.234]) by hub.freebsd.org (Postfix) with ESMTP id 1D006151F9 for ; Sun, 19 Dec 1999 17:38:16 -0800 (PST) (envelope-from jestess@wcnet.net) Received: from wcnet.net [216.88.250.140] by wcn4.wcnet.net with ESMTP (SMTPD32-5.05) id A8877FFC0056; Sun, 19 Dec 1999 19:38:15 -0600 Message-ID: <385D8697.D237F7B7@wcnet.net> Date: Sun, 19 Dec 1999 19:29:59 -0600 From: John Estess Organization: compulsive or none, depending on the day X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: freebsd-stable wannabe tester 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 been shamed into becoming a -stable tester (read comp.unix.bsd.freebsd.misc if you care how) and wonder what kind of help you need. Just download and compile latest kernel? Anything else? -- _/ _/_/_/ || John Estess _/ _/ _/_/ || jestess@wcnet.net _/_/_/ _/_/_/ || C- FAQ: http://www.eskimo.com/~scs/C-faq/top.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 18:35: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from grace.speakeasy.org (grace.speakeasy.net [216.254.0.2]) by hub.freebsd.org (Postfix) with ESMTP id 73A9B15125 for ; Sun, 19 Dec 1999 18:34:22 -0800 (PST) (envelope-from seanj@speakeasy.org) Received: from localhost (seanj@localhost) by grace.speakeasy.org (8.9.3/8.9.3) with ESMTP id SAA12672; Sun, 19 Dec 1999 18:34:20 -0800 Date: Sun, 19 Dec 1999 18:34:20 -0800 (PST) From: Sean Jensen-Grey To: freebsd-stable@freebsd.org Cc: jdp@polstra.com Subject: make world breakage at /usr/src/libexec/rtld-elf/rtld.c 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 Its probably something I did wrong but ... I just cvsup'd tonight and did a make in /usr/src Where is STAILQ_FOREACH() defined? This appears to be the culprit, at least on my system. It also looks like its usage is new to this version of the file. Sean. ** cut ** ===> libexec/ypxfr ===> libexec/named-xfer ===> libexec/mail.local ===> libexec/smrsh ===> libexec/rtld-elf cc -O -pipe -Wall -DFREEBSD_ELF -I/usr/src/libexec/rtld-elf/i386 -I/usr/src/libexec/rtld-elf -elf -fpic -DPIC -c /usr/src/libexec/rtld-elf/rtld.c /usr/src/libexec/rtld-elf/rtld.c: In function `find_symdef': /usr/src/libexec/rtld-elf/rtld.c:757: warning: implicit declaration of function `STAILQ_FOREACH' /usr/src/libexec/rtld-elf/rtld.c:757: parse error before `{' /usr/src/libexec/rtld-elf/rtld.c:726: warning: `elm' might be used uninitialized in this function /usr/src/libexec/rtld-elf/rtld.c:766: warning: control reaches end of non-void function /usr/src/libexec/rtld-elf/rtld.c: At top level: /usr/src/libexec/rtld-elf/rtld.c:769: parse error before `if' /usr/src/libexec/rtld-elf/rtld.c:774: `obj' undeclared here (not in a function) /usr/src/libexec/rtld-elf/rtld.c:774: warning: data definition has no type or storage class /usr/src/libexec/rtld-elf/rtld.c:775: parse error before `}' /usr/src/libexec/rtld-elf/rtld.c:788: redefinition of `defobj' /usr/src/libexec/rtld-elf/rtld.c:774: `defobj' previously defined here /usr/src/libexec/rtld-elf/rtld.c:788: warning: initialization makes integer from pointer without a cast /usr/src/libexec/rtld-elf/rtld.c:788: warning: data definition has no type or storage class /usr/src/libexec/rtld-elf/rtld.c:789: parse error before `}' /usr/src/libexec/rtld-elf/rtld.c:798: redefinition of `defobj' /usr/src/libexec/rtld-elf/rtld.c:788: `defobj' previously defined here /usr/src/libexec/rtld-elf/rtld.c:798: warning: initialization makes integer from pointer without a cast /usr/src/libexec/rtld-elf/rtld.c:798: initializer element is not constant /usr/src/libexec/rtld-elf/rtld.c:798: warning: data definition has no type or storage class /usr/src/libexec/rtld-elf/rtld.c:799: parse error before `}' /usr/src/libexec/rtld-elf/rtld.c: In function `objlist_find': /usr/src/libexec/rtld-elf/rtld.c:1097: parse error before `if' /usr/src/libexec/rtld-elf/rtld.c: In function `dlopen': /usr/src/libexec/rtld-elf/rtld.c:1266: `RTLD_GLOBAL' undeclared (first use this function) /usr/src/libexec/rtld-elf/rtld.c:1266: (Each undeclared identifier is reported only once /usr/src/libexec/rtld-elf/rtld.c:1266: for each function it appears in.) /usr/src/libexec/rtld-elf/rtld.c:1268: `RTLD_MODEMASK' undeclared (first use this function) /usr/src/libexec/rtld-elf/rtld.c: In function `symlook_list': /usr/src/libexec/rtld-elf/rtld.c:1491: parse error before `{' /usr/src/libexec/rtld-elf/rtld.c:1500: break statement not within loop or switch /usr/src/libexec/rtld-elf/rtld.c:1487: warning: `elm' might be used uninitialized in this function /usr/src/libexec/rtld-elf/rtld.c:1503: warning: control reaches end of non-void function /usr/src/libexec/rtld-elf/rtld.c: At top level: /usr/src/libexec/rtld-elf/rtld.c:1504: parse error before `if' /usr/src/libexec/rtld-elf/rtld.c: In function `unload_object': /usr/src/libexec/rtld-elf/rtld.c:1654: parse error before `objlist_remove' /usr/src/libexec/rtld-elf/rtld.c: At top level: /usr/src/libexec/rtld-elf/rtld.c:919: warning: `is_exported' defined but not used *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 18:39:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 30533150C9 for ; Sun, 19 Dec 1999 18:39:33 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA03780; Sun, 19 Dec 1999 18:39:30 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA30265; Sun, 19 Dec 1999 18:39:29 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 19 Dec 1999 18:39:27 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: Sean Jensen-Grey Subject: RE: make world breakage at /usr/src/libexec/rtld-elf/rtld.c Cc: freebsd-stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean Jensen-Grey wrote: > Its probably something I did wrong but ... I just cvsup'd tonight > and did a make in /usr/src You should have done a "make world", or a "make buildworld" followed by a "make installworld". Just plain "make" in /usr/src is almost never the right thing to do. > Where is STAILQ_FOREACH() defined? It's defined in . If you use "make world" or "make buildworld" then the most up-to-date version will be used rather than the old version in your /usr/include tree. John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 18:50:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 7E84215104 for ; Sun, 19 Dec 1999 18:50:48 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 11zsuL-0007Fs-00; Sun, 19 Dec 1999 18:50:46 -0800 Date: Sun, 19 Dec 1999 18:50:40 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: John Estess Cc: freebsd-stable@freebsd.org Subject: Re: freebsd-stable wannabe tester In-Reply-To: <385D8697.D237F7B7@wcnet.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 Sun, 19 Dec 1999, John Estess wrote: > I'm been shamed into becoming a -stable tester (read > comp.unix.bsd.freebsd.misc if you care how) and wonder what kind of help > you need. Just download and compile latest kernel? Anything else? Well, you should look at the handbook in regards to keeping your system up to date. It is always the best place to start. If you just want to stable itself, cvsup, do a "make world", and then make a new kernel. BTW, stable is much more than a new kernel. If you want to test installation of stable, there are places you can download install snapshots. Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 18:59:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 90E6C150ED for ; Sun, 19 Dec 1999 18:59:18 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id SAA03850; Sun, 19 Dec 1999 18:59:17 -0800 (PST) (envelope-from jdp@polstra.com) From: John Polstra Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id SAA30382; Sun, 19 Dec 1999 18:59:16 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 19 Dec 1999 18:59:16 -0800 (PST) Message-Id: <199912200259.SAA30382@vashon.polstra.com> To: williamsl@Home.Com Subject: Re: ld.so failed: Can't find shared library.. In-Reply-To: <13931.991217@Home.Com> References: <13931.991217@Home.Com> Organization: Polstra & Co., Seattle, WA Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <13931.991217@Home.Com>, Ben WIlliams wrote: > One of the servers I now manage is a 2.2.5-RELEASE server. I > recently tried running cvsup from a shell and got: > > ld.so failed: Can't find shared library "libset.so.6.0" > > What is libset.so.6.0 a part of? It is part of the modula-3-lib port, which is used by CVSup. It should be installed in /usr/local/lib/m3/FreeBSD2. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 19:15:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wcn4.wcnet.net (mail.wcnet.net [216.88.248.234]) by hub.freebsd.org (Postfix) with ESMTP id ADB081501D for ; Sun, 19 Dec 1999 19:15:27 -0800 (PST) (envelope-from jestess@wcnet.net) Received: from wcnet.net [216.88.251.84] by wcn4.wcnet.net with ESMTP (SMTPD32-5.05) id AF4C8740270; Sun, 19 Dec 1999 21:15:24 -0600 Message-ID: <385D9D5C.7CA03233@wcnet.net> Date: Sun, 19 Dec 1999 21:07:08 -0600 From: John Estess Organization: compulsive or none, depending on the day X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: freebsd-stable wannabe tester References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, you should look at the handbook in regards to keeping your system > up to date. It is always the best place to start. I'm sure my mail header read 3.4-stable :-) > If you just want to stable itself, cvsup, do a "make world", and then > make a new kernel. BTW, stable is much more than a new kernel. I know. Poor terminology on my part. > If you want to test installation of stable, there are places you can > download install snapshots. I have a 26400 bps connection to the world. No kidding. I can CVSup, but downloading images is not an option in my current environment. I CVSup and make world every week (boredom, I guess), so I'll be glad to increase the frequency and provide feedback. Why does "Reply" send back to the address of the person and not the mailing list? _/ _/_/_/ || John Estess _/ _/ _/_/ || jestess@wcnet.net _/_/_/ _/_/_/ || C- FAQ: http://www.eskimo.com/~scs/C-faq/top.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 20:51:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id 2060615295 for ; Sun, 19 Dec 1999 20:51:37 -0800 (PST) (envelope-from papalia@UDel.Edu) Received: from morgaine (host75-157.student.udel.edu [128.175.75.157]) by copland.udel.edu (8.9.3/8.9.3) with SMTP id XAA06779; Sun, 19 Dec 1999 23:47:41 -0500 (EST) Message-Id: <4.1.19991219234511.0094b150@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sun, 19 Dec 1999 23:47:38 -0500 To: John Polstra , unicorn@blackhats.org From: John Subject: Re: SetAttrs src/contrib/diff/diff3.c,v Cc: stable@FreeBSD.ORG In-Reply-To: <199912122337.PAA03667@vashon.polstra.com> References: <19991203214401.H33150@unicorn.blackhats.org> <19991203214401.H33150@unicorn.blackhats.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> Just wondering why I see a *LOT* (as in one for each source file on the >> system) of SetAttrs messages coming over my screen, when I am cvsupping >> 3.3-STABLE on one system I own. While other systems act normally >> (loading delta's and other stuff)... > >Make sure you run cvsup as the same user and with the same umask >each time. You can specify the umask in the supfile if you want to >be sure about that. I was looking at the docs for cvsup, and I might have missed it, but what is the structure of the line in your supfile to specify a umask? I was toying with the idea of making the entire /usr/src tree mode 600, just to make sure I knew who/what was writing/reading it (especially the custom kernel file), but I don't think I've hit on the correct syntax of the line. Thanks, John Papalia To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 21:13:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id C183C151A2 for ; Sun, 19 Dec 1999 21:13:35 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.8.8/8.8.8) with SMTP id WAA10817 for ; Sun, 19 Dec 1999 22:06:19 -0700 (MST) Date: Sun, 19 Dec 1999 22:06:19 -0700 (MST) From: "Forrest W. Christian" To: stable@freebsd.org Subject: edquota problem 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'm not sure exactly what list this should really be on. Please enlighten me for next time. I just got nailed by an "implementation detail" in edquota. Specifically the code which determines whether the parameter is a username or a range of uids only checks for a) whether the first character of the parameter is a number and b) whether there is a dash in the parameter. Of course, I have a system with a user with the username of 2-xhibit (no I can't get the user to change), which makes edquota think that that username parameter is actually a uid range which it interprets as meaning the range of 2-0, which it errors out on. IMHO, I think that either fixing this to actually check to see if the parameter is ONLY numbers and a single hyphen would be a good idea. Of course, this then doesn't permit usernames of like 10-4 or something like that. The other option would be to check the parameter FIRST against the password file and if the parameter is a valid username, then use it as a username instead of a range. Alternatively, providing a switch to force one way or the other would be ok also. I would patch the code and submit a fix if I knew what people thought the best way to fix this is, or if even people think that it should be changed at all. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 21:18:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id E0C29151A2 for ; Sun, 19 Dec 1999 21:18:24 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id VAA04244; Sun, 19 Dec 1999 21:18:23 -0800 (PST) (envelope-from jdp@polstra.com) Received: (from jdp@localhost) by vashon.polstra.com (8.9.3/8.9.1) id VAA30838; Sun, 19 Dec 1999 21:18:23 -0800 (PST) (envelope-from jdp@polstra.com) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <4.1.19991219234511.0094b150@mail.udel.edu> Date: Sun, 19 Dec 1999 21:18:23 -0800 (PST) Organization: Polstra & Co., Inc. From: John Polstra To: John Subject: Re: SetAttrs src/contrib/diff/diff3.c,v Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John wrote: > I was looking at the docs for cvsup, and I might have missed it, > but what is the structure of the line in your supfile to specify a > umask? I was toying with the idea of making the entire /usr/src > tree mode 600, just to make sure I knew who/what was writing/reading > it (especially the custom kernel file), but I don't think I've hit > on the correct syntax of the line. If you want it to apply to all your collections, put it at the top of the supfile like this: *default umask=077 If you want it to apply just to a single collection, put it on the collection line: src-all umask=077 John --- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "No matter how cynical I get, I just can't keep up." -- Nora Ephron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 21:20:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mercury.jorsm.com (mercury.jorsm.com [207.112.128.9]) by hub.freebsd.org (Postfix) with ESMTP id A896814F77 for ; Sun, 19 Dec 1999 21:20:02 -0800 (PST) (envelope-from jer@jorsm.com) Received: by mercury.jorsm.com (Postfix, from userid 1850) id 68927E4A6A; Sun, 19 Dec 1999 23:20:01 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by mercury.jorsm.com (Postfix) with ESMTP id 5F3E4E0C02; Sun, 19 Dec 1999 23:20:01 -0600 (CST) Date: Sun, 19 Dec 1999 23:20:01 -0600 (CST) From: Jeremy Shaffner To: John Estess Cc: freebsd-stable@freebsd.org Subject: Re: freebsd-stable wannabe tester In-Reply-To: <385D9D5C.7CA03233@wcnet.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 Sun, 19 Dec 1999, John Estess wrote: > > If you want to test installation of stable, there are places you can > > download install snapshots. > > I have a 26400 bps connection to the world. No kidding. I can CVSup, but > downloading images is not an option in my current environment. He wasn't talking images. He means you can do an FTP install of a snapshot just like you can for a full -RELEASE. -Jeremy -=========================================================================- Jeremy Shaffner JORSM Internet, Regional Internet Services System Administrator 7 Area Codes in Chicagoland and NW Indiana jer@jorsm.com 100Mbps+ Connectivity, 56K-DS3, V.90, ISDN support@jorsm.com Quality Service, Affordable Prices http://www.jorsm.com Serving Gov't, Business, Individuals Since 1995 -=========================================================================- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 21:20:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 0CECB152CD for ; Sun, 19 Dec 1999 21:20:29 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id GAA00363 for freebsd-stable@FreeBSD.ORG; Mon, 20 Dec 1999 06:20:28 +0100 (CET) (envelope-from olli) Date: Mon, 20 Dec 1999 06:20:28 +0100 (CET) From: Oliver Fromme Message-Id: <199912200520.GAA00363@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: 3.4-19991219-STABLE upgrade crash Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Bill Trost wrote in list.freebsd-stable: > I'm trying to upgrade my Fujitsu 635Tx from an a.out version of FreeBSD > to the above-mentioned snapshot, and when I select "Custom" to identify > the distribution sets I want, I get a signal 11 notification. I turned > debugging on (at least, I think I did -- the options screen was largely > black-on-black) and saw the following debug output on vty1: > > DEBUG: Command `/stand/gunzip < /stand/help/distributions.hlp.gz > /tmp/.doc/doc.tmp' returns status of 0 > DEBUG: Signal 11 caught! That's bad! I can reproduce that problem (a.k.a. "me too!"). Yesterday I wanted to install FreeBSD on a virgin harddisk, so I booted from the latest -stable snapshot floppies (19991219). In sysinstall I selected "custom" in the distributions screen (like I always do, because I don't like any of the predefined sets, although "Developer" comes pretty close). Well, sysinstall reported a signal 11 as soon as I selected "custom" and died. This was repeatable at the exactly same place, so it's not a hardware problem. I ended up doing a "minimal" install and then installing the rest manually. The problem is trivially repeatable even on a running system: Run /stand/sysinstall, go to the custom/expert menu, select "distributions", then "custom" --> bang. It even drops a nice coredump. :) (I'm very sorry -- At that time I had only kernel sources installed, so I couldn't debug it. But it's really trivial to reproduce, so someone else can certainly look into this.) There have been other issues with sysinstall during that installation which almost made me go mad, but I don't complain, knowing that sysinstall is a dead end anyway and going to be replaced... :-) Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 21:27:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 6B065152C0 for ; Sun, 19 Dec 1999 21:26:49 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id GAA03080 for freebsd-stable@FreeBSD.ORG; Mon, 20 Dec 1999 06:26:48 +0100 (CET) (envelope-from olli) Date: Mon, 20 Dec 1999 06:26:48 +0100 (CET) From: Oliver Fromme Message-Id: <199912200526.GAA03080@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Randall Hopper wrote in list.freebsd-stable: > Hi. Is there a FreeBSD assembler out there which supports the AMD 3DNow > instruction set? NASM (in the ports) supports the older ones, but not the newer ones supported by the Athlon/K7. I sent patches to the author to support those, too, but nothing happened. > Why I ask: I attempted to build GLX/Mesa3.1 with 3DNow support, and it > bombed since our assembler isn't 3DNow-knowledgable (femms, pfmul, > etc. undefined). The assembler in -stable has the same shortcoming AFAICT. > > Facts? Rumors? I'm interested in anything you may know. Well, when I added 3DNow support to the Seti@home client, I assembled the 3DNow instructions "manually", i.e. I created small gas macros for that purpose. It's ugly, but it works. The 3DNow specification (with instruction codes) is available from www.amd.com. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 21:53: 8 1999 Delivered-To: freebsd-stable@freebsd.org Received: from copland.udel.edu (copland.udel.edu [128.175.13.92]) by hub.freebsd.org (Postfix) with ESMTP id 2DC6814E8C for ; Sun, 19 Dec 1999 21:53:06 -0800 (PST) (envelope-from papalia@UDel.Edu) Received: from morgaine (host75-157.student.udel.edu [128.175.75.157]) by copland.udel.edu (8.9.3/8.9.3) with SMTP id AAA26723; Mon, 20 Dec 1999 00:53:02 -0500 (EST) Message-Id: <4.1.19991220005245.0099f900@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 20 Dec 1999 00:53:00 -0500 To: John Polstra From: John Subject: Re: SetAttrs src/contrib/diff/diff3.c,v Cc: stable@FreeBSD.ORG In-Reply-To: References: <4.1.19991219234511.0094b150@mail.udel.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Works great. Thank you kindly :) Regards, John >> I was looking at the docs for cvsup, and I might have missed it, >> but what is the structure of the line in your supfile to specify a >> umask? I was toying with the idea of making the entire /usr/src >> tree mode 600, just to make sure I knew who/what was writing/reading >> it (especially the custom kernel file), but I don't think I've hit >> on the correct syntax of the line. > >If you want it to apply to all your collections, put it at the top >of the supfile like this: > > *default umask=077 > >If you want it to apply just to a single collection, put it on the >collection line: > > src-all umask=077 > >John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sun Dec 19 22:41:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [194.58.85.161]) by hub.freebsd.org (Postfix) with ESMTP id 2739F14C0E for ; Sun, 19 Dec 1999 22:41:15 -0800 (PST) (envelope-from eugen@svzserv.kemerovo.su) Received: from svzserv.kemerovo.su (kost.svzserv.kemerovo.su [194.58.85.163]) by www.svzserv.kemerovo.su (8.9.2/8.9.2) with ESMTP id NAA15010 for ; Mon, 20 Dec 1999 13:41:11 +0700 (NKZ) Message-ID: <385DCFED.85742D2E@svzserv.kemerovo.su> Date: Mon, 20 Dec 1999 13:42:53 +0700 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.7 [en] (Win95; I) X-Accept-Language: ru,en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: 3.3-STABLE & aout Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! How do I make aout binary on -STABLE? I installed compat20, compat21 and compat22, then tried # cc -aout -o hello hello.c (it's "Hello world"-program :) I get 'ld: crt0.o: no such file or directory' error message. It seems there is no crt0.o file at all. Please help. Eugene Grosbein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 1:12:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5ED6D15100 for ; Mon, 20 Dec 1999 01:12:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id BAA45843 for ; Mon, 20 Dec 1999 01:11:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: freebsd-stable@FreeBSD.ORG Subject: Re: 3.4-19991219-STABLE upgrade crash In-reply-to: Your message of "Mon, 20 Dec 1999 06:20:28 +0100." <199912200520.GAA00363@dorifer.heim3.tu-clausthal.de> Date: Mon, 20 Dec 1999 01:11:44 -0800 Message-ID: <45840.945681104@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All of these issues have been addressed today. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 5:22:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 8242B14A05 for ; Mon, 20 Dec 1999 05:22:19 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id IAA44500; Mon, 20 Dec 1999 08:22:15 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <199912201322.IAA44500@blackhelicopters.org> Subject: Re: Sys Admin article on Linux emulation In-Reply-To: <199912181557.HAA22996@netcom.com> from Stan Brown at "Dec 18, 1999 10:57: 0 am" To: stanb@netcom.com (Stan Brown) Date: Mon, 20 Dec 1999 08:22:15 -0500 (EST) Cc: freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This months _Sy Admin_ magazine has a nice aritcle on Linux emulation > under FreeBSD. > > The author says he is running CURRENT> He rcomends several options to > be set in ones kernel config file. Are these option appropriate for a > machine runing STABLE? Uh, as the outhor, I *hope* I didn't say I'm running -current... if I did, it is a definite error and I should be taken out and shot. Those options are appropriate for stable. BTW, in the future, it would be a good idea to include the options in question in a query to the mailing list. You aren't always going to have someone on hand who has read the same third-party article you have, even when it's on the Web. Any if anyone still cares, the mysterious options are: options "P1003_1B" #POSIX infrastructure options "_KPOSIX_PRIORITY_SCHEDULING" #Built-in POSIX priority scheduling options "_KPOSIX_VERSION=199309L" #POSIX version kernel is built for options SYSVSHM #System V shared memory options SYSVMSG #System V semaphores options SYSVSEM #System V messaging options USER_LDT #allow user-level control of i386 ldt My only complaint is the positioning of Tux and Beastie in the picture; if they had been reversed, the damn penguin would be getting a beakful of pitchfork. ;) Glad you liked it. ==ml To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 5:27:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from milf18.bus.net (milf18.bus.net [207.41.25.18]) by hub.freebsd.org (Postfix) with ESMTP id AC7BD15030 for ; Mon, 20 Dec 1999 05:27:51 -0800 (PST) (envelope-from cao@milf18.bus.net) Received: (from cao@localhost) by milf18.bus.net (8.8.8/8.8.8) id IAA19270; Mon, 20 Dec 1999 08:27:37 -0500 (EST) (envelope-from cao) Date: Mon, 20 Dec 1999 08:27:37 -0500 From: "Chuck O'Donnell" To: "Forrest W. Christian" Cc: stable@FreeBSD.ORG Subject: Re: edquota problem Message-ID: <19991220082737.A19220@bus.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: ; from Forrest W. Christian on Sun, Dec 19, 1999 at 10:06:19PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Dec 19, 1999 at 10:06:19PM -0700, Forrest W. Christian wrote: > I'm not sure exactly what list this should really be on. Please enlighten > me for next time. > > I just got nailed by an "implementation detail" in edquota. > > Specifically the code which determines whether the parameter is a username > or a range of uids only checks for a) whether the first character of the > parameter is a number and b) whether there is a dash in the parameter. > > Of course, I have a system with a user with the username of 2-xhibit (no I > can't get the user to change), which makes edquota think that that > username parameter is actually a uid range which it interprets as meaning > the range of 2-0, which it errors out on. > > IMHO, I think that either fixing this to actually check to see if the > parameter is ONLY numbers and a single hyphen would be a good idea. Of > course, this then doesn't permit usernames of like 10-4 or something like > that. > > The other option would be to check the parameter FIRST against the > password file and if the parameter is a valid username, then use it as a > username instead of a range. > > Alternatively, providing a switch to force one way or the other would be > ok also. > > I would patch the code and submit a fix if I knew what people thought the > best way to fix this is, or if even people think that it should be changed > at all. did you try `edquota -- 2-xhibit' ? chuck > > - Forrest W. Christian (forrestc@imach.com) KD7EHZ > ---------------------------------------------------------------------- > iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com > Solutions for your high-tech problems. (406)-442-6648 > ---------------------------------------------------------------------- > > > > 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 Dec 20 5:47:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from milf18.bus.net (milf18.bus.net [207.41.25.18]) by hub.freebsd.org (Postfix) with ESMTP id 5DD0D14C02 for ; Mon, 20 Dec 1999 05:47:22 -0800 (PST) (envelope-from cao@milf18.bus.net) Received: (from cao@localhost) by milf18.bus.net (8.8.8/8.8.8) id IAA19373; Mon, 20 Dec 1999 08:47:06 -0500 (EST) (envelope-from cao) Date: Mon, 20 Dec 1999 08:47:05 -0500 From: "Chuck O'Donnell" To: Eugene Grosbein Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.3-STABLE & aout Message-ID: <19991220084705.B19220@bus.net> References: <385DCFED.85742D2E@svzserv.kemerovo.su> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: <385DCFED.85742D2E@svzserv.kemerovo.su>; from Eugene Grosbein on Mon, Dec 20, 1999 at 01:42:53PM +0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 01:42:53PM +0700, Eugene Grosbein wrote: > Hello! > > How do I make aout binary on -STABLE? > I installed compat20, compat21 and compat22, then tried > # cc -aout -o hello hello.c > (it's "Hello world"-program :) > > I get 'ld: crt0.o: no such file or directory' error message. > It seems there is no crt0.o file at all. > The compat distributions only install the dynamic libraries for you. You also need the static libs to compile aout. You can either grab these from a running 2.2.x system, or untar the lib distribution from a 2.2.8 CD into /usr/lib/compat/aout. The lib dist is `/cdrom/bin/bin.??' (on a 2.2.8 cdrom anyway). It's one big tar file broken into smaller chunks, so you have to cat it together before untarring it. Try something like: cat /cdrom/bin/bin.?? | tar xzpf - -C /tmp 'usr/lib/*' for lib in `find /tmp/usr/lib -type f`; do if ! test -f /usr/lib/compat/aout/`basename $lib`; then cp -p $lib /usr/lib/compat/aout/ fi done rm -rf /tmp/usr You may need to rerun ldconfig at this point, but I could be mistaken. If you can afford it, a reboot isn't a bad idea, as the rc files call ldconfig for you at boot time with the correct paths. good luck. chuck p.s. i think freebsd-questions may be a better forum for these types of questions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 8:47:51 1999 Delivered-To: freebsd-stable@freebsd.org Received: from klentaq.com (klentaq1.emergingtech.org [199.217.151.234]) by hub.freebsd.org (Postfix) with ESMTP id 5853C15261 for ; Mon, 20 Dec 1999 08:47:48 -0800 (PST) (envelope-from stabilizer@klentaq.com) Received: (from stabilizer@localhost) by klentaq.com (8.9.3/8.9.2) id KAA85652 for freebsd-stable@freebsd.org; Mon, 20 Dec 1999 10:49:44 -0600 (CST) (envelope-from stabilizer) From: Wayne M Barnes Message-Id: <199912201649.KAA85652@klentaq.com> Subject: PCI internal modem To: freebsd-stable@freebsd.org (FreeBSD Stable) Date: Mon, 20 Dec 1999 10:49:44 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Folks, How do I get my PCI modem card to work with FreeBSD 3.4? I have spent several hours reading about ppp in the handbook section 15, and trying things, and I still have the following questions, since I am getting nowhere: 1. controller pnp0 in my KERNEL config file resulted in dmesg line with 'Serial' in it, but which device in /dev would that be? Here is the message line: CSN 1 Vendor ID: CSC4236 [0x3642630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] 2. Do I need options "EXTRA_SIO=2" in my KERNEL config file? 3. Do I need pseudodevice ppp 2 in my KERNEL config file, or is tun0 enough by itself? Thanks for any help. Wayne M Barnes stabilizer@klentaq.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 9:23: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 68CD115388 for ; Mon, 20 Dec 1999 09:22:58 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA11815; Mon, 20 Dec 1999 10:22:56 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA17015; Mon, 20 Dec 1999 10:22:55 -0700 (MST) Message-Id: <199912201722.KAA17015@harmony.village.org> To: Wayne M Barnes Subject: Re: PCI internal modem Cc: freebsd-stable@FreeBSD.ORG (FreeBSD Stable) In-reply-to: Your message of "Mon, 20 Dec 1999 10:49:44 CST." <199912201649.KAA85652@klentaq.com> References: <199912201649.KAA85652@klentaq.com> Date: Mon, 20 Dec 1999 10:22:55 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912201649.KAA85652@klentaq.com> Wayne M Barnes writes: : How do I get my PCI modem card to work with FreeBSD 3.4? *IF* it isn't a win modem, soft modem, etc, then you can apply the following patch, rebuild your kernel and create /dev/cua4, et al in /dev. If it is a win modem, you lose. Sell it to some sucker and buy a real pci modem. Patch: http://www.freebsd.org/~imp/Psio Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 10: 3:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by hub.freebsd.org (Postfix) with ESMTP id C503514A27 for ; Mon, 20 Dec 1999 10:03:01 -0800 (PST) (envelope-from jeffrl@wantabe.com) Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by cutter.wantabe.com (8.9.3/8.9.3) with ESMTP id NAA58975 for ; Sun, 19 Dec 1999 13:06:44 -0600 (CST) (envelope-from jeffrl@wantabe.com) Date: Sun, 19 Dec 1999 13:06:44 -0600 (CST) From: "Jeffrey J. Libman" To: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-Reply-To: <199912191816.KAA02792@mass.cdrom.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 in an effort to get back on track on this issue: i have been thru several "solutions" as per responsed from freebsd-stable, to no avail. i am running freeBSD 3.3-stable, oct 11 cvsup and build. after moving 54 virtual hosts to this machine, rpc.statd will not run: it hangs; mountd runs (-r or not -r), but will not serve up mounts and dies. when i let rpc.statd time out, i get this error message: Cannot register service: RPC: Timed out rpc.statd: unable to register (SM_PROG, SM_VERS, udp) this was working until a week ago when i moved about 45 virtual domains to this machine. solutions suggested and tried so far: 1) i have a realsys ne2000 clone nic; was told this inferior card was a problem. i have now installed a linksys etherfast 10/100tx card. 2) configure the loopback interface properly. (i assign all virtual ip's to the lo0 interface). a) 127.0.0.1 is properly assigned to lo0. b) it has been claimed that the virtual ip's need netmask 0xffffffff rather than 0xffffff00. i have tried it both ways. none of these are the fix...i still have the original problem. any help will be greatly appreciated. cheers, jeff -- | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 10:20:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 3757A14A05 for ; Mon, 20 Dec 1999 10:20:34 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id SAA23154 for freebsd-stable@FreeBSD.ORG; Mon, 20 Dec 1999 18:31:38 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id RAA00612 for freebsd-stable@FreeBSD.ORG; Mon, 20 Dec 1999 17:37:08 +0100 (CET) (envelope-from wilko) Date: Mon, 20 Dec 1999 17:37:08 +0100 From: Wilko Bulte To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Message-ID: <19991220173708.B544@yedi.iaf.nl> References: <199912200526.GAA03080@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912200526.GAA03080@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Mon, Dec 20, 1999 at 06:26:48AM +0100 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 06:26:48AM +0100, Oliver Fromme wrote: > Randall Hopper wrote in list.freebsd-stable: > > Hi. Is there a FreeBSD assembler out there which supports the AMD 3DNow > > instruction set? > > NASM (in the ports) supports the older ones, but not the newer > ones supported by the Athlon/K7. I sent patches to the author > to support those, too, but nothing happened. > > > Why I ask: I attempted to build GLX/Mesa3.1 with 3DNow support, and it > > bombed since our assembler isn't 3DNow-knowledgable (femms, pfmul, > > etc. undefined). The assembler in -stable has the same shortcoming AFAICT. > > > > Facts? Rumors? I'm interested in anything you may know. > > Well, when I added 3DNow support to the Seti@home client, I > assembled the 3DNow instructions "manually", i.e. I created > small gas macros for that purpose. It's ugly, but it works. Being the curious kind: what speed difference did you observe? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.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 Dec 20 10:22:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.bna.bellsouth.net (mail1.bna.bellsouth.net [205.152.150.13]) by hub.freebsd.org (Postfix) with ESMTP id 6A23E14A11 for ; Mon, 20 Dec 1999 10:22:30 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-216-78-82-14.cha.bellsouth.net [216.78.82.14]) by mail1.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id NAA29069 for ; Mon, 20 Dec 1999 13:22:22 -0500 (EST) Message-ID: <385E7407.2191102E@siteplus.com> Date: Mon, 20 Dec 1999 13:23:03 -0500 From: Jim Weeks X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i486) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: 3.4-19991218-STABLE snapshot kernel build Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Has anyone besides me installed a fresh copy of 3.4-19991218-STABLE or 3.4-19991219-STABLE from snapshots and rebuilt the kernel. The installs went without a hitch, but when trying to build a new kernel I got these errors. Script started on Sun Dec 19 17:28:14 1999 sentinel# make cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wuninitialized -Wformat -Wunused -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I/usr/include -DKERNEL -DVM_STACK -include opt_global.h -elf ../../cam/scsi/scsi_cd.c In file included from ../../cam/scsi/scsi_cd.c:60: ../../sys/cdio.h:91: warning: useless keyword or type name in empty declaration ../../sys/cdio.h:91: warning: empty declaration ../../sys/cdio.h:91: parse error before `_' ../../sys/cdio.h:91: warning: no semicolon at end of struct or union ../../sys/cdio.h:92: warning: data definition has no type or storage class ../../sys/cdio.h:92: parse error before `}' ../../sys/cdio.h:96: syntax error before `{' ../../sys/cdio.h:98: warning: data definition has no type or storage class ../../sys/cdio.h:98: parse error before `osiricn' ../../sys/cdio.h:100: warning: data definition has no type or storage class ../../sys/cdio.h:100: parse error before `rscr_cn' ../../sys/cdio.h:100: warning: data definition has no type or storage class ../../sys/cdio.h:100: parse error before `t' ../../sys/cdio.h:101: warning: data definition has no type or storage class ../../sys/cdio.h:102: parse error before `/' ../../sys/cdio.h:103: warning: data definition has no type or storage class ../../sys/cdio.h:104: parse error before `}' ../../cam/scsi/scsi_cd.c: In function `cdioctl': ../../cam/scsi/scsi_cd.c:1966: sizeof applied to an incomplete type ../../cam/scsi/scsi_cd.c:1969: sizeof applied to an incomplete type ../../cam/scsi/scsi_cd.c:1991: dereferencing pointer to incomplete type ../../cam/scsi/scsi_cd.c:1992: dereferencing pointer to incomplete type ../../cam/scsi/scsi_cd.c:1993: dereferencing pointer to incomplete type ../../cam/scsi/scsi_cd.c:1994: dereferencing pointer to incomplete type ../../sys/libkern.h:57: warning: inlining failed in call to `min' ../../cam/scsi/scsi_cd.c:1995: warning: called from here *** Error code 1 I messed with this all day sunday and was unable to resolve the problem. I needed to get the machine back on line, so I installed a copy of 3.3-19991125-STABLE since I had installed this on another machine with no problems. I installed it, built the new kernel and it is online :) Is there something wrong with the kernel source on 3.4 snapshots? Jim Weeks jim@siteplus.com http://siteplus.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 10:23:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id BC06A150D1 for ; Mon, 20 Dec 1999 10:23:41 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.8.8/8.8.8) with SMTP id LAA15803; Mon, 20 Dec 1999 11:16:12 -0700 (MST) Date: Mon, 20 Dec 1999 11:16:12 -0700 (MST) From: "Forrest W. Christian" To: "Chuck O'Donnell" Cc: stable@FreeBSD.ORG Subject: Re: edquota problem In-Reply-To: <19991220082737.A19220@bus.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 Mon, 20 Dec 1999, Chuck O'Donnell wrote: > did you try `edquota -- 2-xhibit' ? No, but now I did and it doesn't help. Specifically, I used: edquota -- -p usrtmplt 2-xhibit edquota -p usrtmplt -- 2-xhibit I think this problem really only shows up when you are using a prototype user ala -p. - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 10:36:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 4368F14EAE for ; Mon, 20 Dec 1999 10:36:32 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id TAA27912 for freebsd-stable@FreeBSD.ORG; Mon, 20 Dec 1999 19:36:31 +0100 (CET) (envelope-from olli) Date: Mon, 20 Dec 1999 19:36:31 +0100 (CET) From: Oliver Fromme Message-Id: <199912201836.TAA27912@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote in list.freebsd-stable: > On Mon, Dec 20, 1999 at 06:26:48AM +0100, Oliver Fromme wrote: > [...] > > Well, when I added 3DNow support to the Seti@home client, I > > assembled the 3DNow instructions "manually", i.e. I created > > small gas macros for that purpose. It's ugly, but it works. > > Being the curious kind: what speed difference did you observe? About 50%, that is, about 4.5 hours (instead of 9) on average per work unit, on an Athlon-500. And I did only optimize the FFT and didn't touch the rest. With a bit more effort, further improvements would be certainly possible. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 10:52: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alecto.physics.uiuc.edu (alecto.physics.uiuc.edu [130.126.8.20]) by hub.freebsd.org (Postfix) with ESMTP id D205615120 for ; Mon, 20 Dec 1999 10:52:00 -0800 (PST) (envelope-from igor@alecto.physics.uiuc.edu) Received: (from igor@localhost) by alecto.physics.uiuc.edu (8.9.0/8.9.0) id MAA00734 for stable@freebsd.org; Mon, 20 Dec 1999 12:52:00 -0600 (CST) From: Igor Roshchin Message-Id: <199912201852.MAA00734@alecto.physics.uiuc.edu> Subject: xl0 question To: stable@freebsd.org Date: Mon, 20 Dec 1999 12:51:59 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! After installation of 3.3-STABLE (snapshot of 19991216) on a few computers I noticed messages about tx underrun in xl0: xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x24 int a irq 11 on pci0.11.0 xl0: Ethernet address: 00:10:5a:a9:fa:91 xl0: autoneg complete, link status good (full-duplex, 100Mbps) xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 120 bytes xl0: transmission error: 90 xl0: tx underrun, increasing tx start threshold to 180 bytes This is noticed on computers with PPRO (180) and Pentium (150) cpus. I haven't seen such messages on either 3.1-STABLE or 2.x on the same computers. Is there anything to worry about ? Thanks, Igor PS. please respond to my address, I am not subscribed to the list at the moment. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 10:57:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from milf18.bus.net (milf18.bus.net [207.41.25.18]) by hub.freebsd.org (Postfix) with ESMTP id 263D714C49 for ; Mon, 20 Dec 1999 10:57:44 -0800 (PST) (envelope-from cao@milf18.bus.net) Received: (from cao@localhost) by milf18.bus.net (8.8.8/8.8.8) id NAA20571; Mon, 20 Dec 1999 13:57:36 -0500 (EST) (envelope-from cao) Date: Mon, 20 Dec 1999 13:57:36 -0500 From: "Chuck O'Donnell" To: "Forrest W. Christian" Cc: stable@FreeBSD.ORG Subject: Re: edquota problem Message-ID: <19991220135736.B20394@bus.net> References: <19991220082737.A19220@bus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: ; from Forrest W. Christian on Mon, Dec 20, 1999 at 11:16:12AM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 11:16:12AM -0700, Forrest W. Christian wrote: > On Mon, 20 Dec 1999, Chuck O'Donnell wrote: > > > did you try `edquota -- 2-xhibit' ? > > No, but now I did and it doesn't help. > > Specifically, I used: > > edquota -- -p usrtmplt 2-xhibit > edquota -p usrtmplt -- 2-xhibit > > I think this problem really only shows up when you are using a prototype > user ala -p. I gotcha. At first look I thought it was a getopt(3) problem, but that can't be anyway since the username doesn't start with a `-'. I looked at edquota.c and you're right, if the username supplied to edquota starts with a digit and contains a `-', it is interpreted as a range. I'm not sure what the best answer is for the long term. Would a perl one-liner help the immediate need? e.g., edquota -p usrtmpl `perl -e '$u=getpwnam($ARGV[0]);print "$u-$u"' 2-xhibit` good luck, chuck > > - Forrest W. Christian (forrestc@imach.com) KD7EHZ > ---------------------------------------------------------------------- > iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com > Solutions for your high-tech problems. (406)-442-6648 > ---------------------------------------------------------------------- > > > > 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 Dec 20 11:35:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id C498A14BD3 for ; Mon, 20 Dec 1999 11:35:36 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA26407 for freebsd-stable@FreeBSD.ORG; Mon, 20 Dec 1999 19:37:14 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA02429 for freebsd-stable@FreeBSD.ORG; Mon, 20 Dec 1999 20:10:00 +0100 (CET) (envelope-from wilko) Date: Mon, 20 Dec 1999 20:10:00 +0100 From: Wilko Bulte To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Message-ID: <19991220201000.A2302@yedi.iaf.nl> References: <199912201836.TAA27912@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912201836.TAA27912@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Mon, Dec 20, 1999 at 07:36:31PM +0100 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 07:36:31PM +0100, Oliver Fromme wrote: > Wilko Bulte wrote in list.freebsd-stable: > > On Mon, Dec 20, 1999 at 06:26:48AM +0100, Oliver Fromme wrote: > > [...] > > > Well, when I added 3DNow support to the Seti@home client, I > > > assembled the 3DNow instructions "manually", i.e. I created > > > small gas macros for that purpose. It's ugly, but it works. > > > > Being the curious kind: what speed difference did you observe? > > About 50%, that is, about 4.5 hours (instead of 9) on average > per work unit, on an Athlon-500. And I did only optimize the > FFT and didn't touch the rest. With a bit more effort, further > improvements would be certainly possible. Wow! Quite a difference. Not having an Athlon but CPU: AMD-K6(tm) 3D processor (399.81-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 AMD Features=0x80000800 would that also make such a difference on the K6-2? Athlon has different 3Dnow I think ?? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.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 Dec 20 11:39:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 429CD14CCA for ; Mon, 20 Dec 1999 11:39:50 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.8.8/8.8.8) with SMTP id MAA16506; Mon, 20 Dec 1999 12:32:24 -0700 (MST) Date: Mon, 20 Dec 1999 12:32:24 -0700 (MST) From: "Forrest W. Christian" To: "Chuck O'Donnell" Cc: stable@FreeBSD.ORG Subject: Re: edquota problem In-Reply-To: <19991220135736.B20394@bus.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 Mon, 20 Dec 1999, Chuck O'Donnell wrote: > I'm not sure what the best answer is for the long term. Would a perl > one-liner help the immediate need? e.g., > > edquota -p usrtmpl `perl -e '$u=getpwnam($ARGV[0]);print "$u-$u"' 2-xhibit` You know, every once in a while someone comes up with a solution I look at and say to myself "Duuuuuuh!" I already have the uid available. (This is being ran from a custom perl add-user script). I will fix my script accordingly. That will be more reliable than the username anyways. However, this might be something someone should look at fixing long-term. Who "owns" this code? And/or where should this be discussed? - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 11:57:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from milf18.bus.net (milf18.bus.net [207.41.25.18]) by hub.freebsd.org (Postfix) with ESMTP id CF07B14D37 for ; Mon, 20 Dec 1999 11:57:47 -0800 (PST) (envelope-from cao@milf18.bus.net) Received: (from cao@localhost) by milf18.bus.net (8.8.8/8.8.8) id OAA20790; Mon, 20 Dec 1999 14:57:40 -0500 (EST) (envelope-from cao) Date: Mon, 20 Dec 1999 14:57:39 -0500 From: "Chuck O'Donnell" To: "Forrest W. Christian" Cc: stable@FreeBSD.ORG Subject: Re: edquota problem Message-ID: <19991220145739.C20394@bus.net> References: <19991220135736.B20394@bus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.3i In-Reply-To: ; from Forrest W. Christian on Mon, Dec 20, 1999 at 12:32:24PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 12:32:24PM -0700, Forrest W. Christian wrote: > On Mon, 20 Dec 1999, Chuck O'Donnell wrote: > > > I'm not sure what the best answer is for the long term. Would a perl > > one-liner help the immediate need? e.g., > > > > edquota -p usrtmpl `perl -e '$u=getpwnam($ARGV[0]);print "$u-$u"' 2-xhibit` > > You know, every once in a while someone comes up with a solution I look at > and say to myself "Duuuuuuh!" > > I already have the uid available. (This is being ran from a custom perl > add-user script). I will fix my script accordingly. That will be more > reliable than the username anyways. > > However, this might be something someone should look at fixing long-term. > Who "owns" this code? And/or where should this be discussed? $ ident /usr/sbin/edquota /usr/sbin/edquota: $Id: edquota.c,v 1.8 1999/01/01 13:15:02 bde Exp $ looks like the last person to work on the code was Bruce Evans . but that doesn't necessarily mean he wants to do the modification :) i'd look for interest starting with freebsd-questions, and then maybe on freebsd-hackers if no response. you may want to look around to see what freebsd considers to be a valid username first though... if names like `2-xhibit' fall out of that spec, then you're probably less likely to gain support for acceptance of a change. note the following from `adduser(8)': username Login name. May contain only lowercase characters or digits. that's probably why this hasn't come up before. good luck, chuck To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 12:15:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id AF47514E52 for ; Mon, 20 Dec 1999 12:15:30 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40331>; Tue, 21 Dec 1999 07:05:26 +1100 Content-return: prohibited Date: Tue, 21 Dec 1999 07:14:08 +1100 From: Peter Jeremy Subject: Re: edquota problem In-reply-to: ; from forrestc@iMach.com on Mon, Dec 20, 1999 at 04:06:19PM +1100 To: "Forrest W. Christian" Cc: stable@FreeBSD.ORG Message-Id: <99Dec21.070526est.40331@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-20 16:06:19 +1100, "Forrest W. Christian" wrote: >Specifically the code which determines whether the parameter is a username >or a range of uids only checks for a) whether the first character of the >parameter is a number and b) whether there is a dash in the parameter. This is definitely wrong. Input parameters should be properly checked for validity. IMHO, checking the parameter against the password file first, and then checking if it's all numeric (or a range) is probably the more reasonable approach, though this is a more complex fix. >Alternatively, providing a switch to force one way or the other would be >ok also. I don't like this idea. >I would patch the code and submit a fix if I knew what people thought the >best way to fix this is, or if even people think that it should be changed >at all. It _should_ be fixed. The simpler fix would replace the existing test and atoi()'s with something like: if (isdigit(*argv[0]) && (startuid = strtol(*argv, &cp, 10)) >= 0 && *cp++ == '-' && isdigit(*cp) && (enduid = strtol(cp, &cp, 10)) >= 0 && !*cp) { I'd pick whichever option you prefer and include it in a PR. If whoever looks at the PR doesn't agree, they can always do it another way. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 13:24:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 685D715281 for ; Mon, 20 Dec 1999 13:24:38 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.8.8/8.8.8) with SMTP id OAA20949; Mon, 20 Dec 1999 14:17:08 -0700 (MST) Date: Mon, 20 Dec 1999 14:17:07 -0700 (MST) From: "Forrest W. Christian" To: Peter Jeremy Cc: stable@FreeBSD.ORG Subject: Re: edquota problem In-Reply-To: <99Dec21.070526est.40331@border.alcanet.com.au> 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 Tue, 21 Dec 1999, Peter Jeremy wrote: > >Specifically the code which determines whether the parameter is a username > >or a range of uids only checks for a) whether the first character of the > >parameter is a number and b) whether there is a dash in the parameter. > > This is definitely wrong. Input parameters should be properly checked > for validity. I fully agree. In fact, I was rather shocked to see the code written that way. ESPECIALLY when setting something like: 0plus-num as a username equates to setting uid 0's quota. > IMHO, checking the parameter against the password file first, and > then checking if it's all numeric (or a range) is probably the more > reasonable approach, though this is a more complex fix. This seems the MOST reasonable way to do this. The only gotcha is that there may be a situation where a username exists which matches the uid range you're looking for, such as 10-20 or something like that. However, I figure that is much more rare than a uname starting with a number and having a dash. > >Alternatively, providing a switch to force one way or the other would be > >ok also. > > I don't like this idea. The only thing I would maybe say is if I do (I'm leaning strongly that way) fix the code to look for the uname first, then maybe a switch should be added to FORCE the code to treat the argument as a range of uid's. > It _should_ be fixed. The simpler fix would replace the existing test > and atoi()'s with something like: > > if (isdigit(*argv[0]) && > (startuid = strtol(*argv, &cp, 10)) >= 0 && *cp++ == '-' && > isdigit(*cp) && (enduid = strtol(cp, &cp, 10)) >= 0 && !*cp) { > I'll probably fix the code so that it looks at the argument and determines if it is a valid user, and if not, submits it to the above evaluation for a proper uid range. Any other comments? - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 13:34:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mppsystems.com (dslmpp.pro-ns.net [208.210.148.205]) by hub.freebsd.org (Postfix) with ESMTP id AC6D7152FB for ; Mon, 20 Dec 1999 13:34:10 -0800 (PST) (envelope-from mpp@mppsystems.com) Received: (from mpp@localhost) by mppsystems.com (8.9.3/8.9.3) id OAA05696; Mon, 20 Dec 1999 14:00:35 -0600 (CST) (envelope-from mpp) Date: Mon, 20 Dec 1999 14:00:35 -0600 From: Mike Pritchard To: "Forrest W. Christian" Cc: "Chuck O'Donnell" , stable@FreeBSD.ORG Subject: Re: edquota problem Message-ID: <19991220140035.A5659@mppsystems.com> References: <19991220135736.B20394@bus.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 12:32:24PM -0700, Forrest W. Christian wrote: > On Mon, 20 Dec 1999, Chuck O'Donnell wrote: > > > I'm not sure what the best answer is for the long term. Would a perl > > one-liner help the immediate need? e.g., > > > > edquota -p usrtmpl `perl -e '$u=getpwnam($ARGV[0]);print "$u-$u"' 2-xhibit` > > You know, every once in a while someone comes up with a solution I look at > and say to myself "Duuuuuuh!" > > I already have the uid available. (This is being ran from a custom perl > add-user script). I will fix my script accordingly. That will be more > reliable than the username anyways. > > However, this might be something someone should look at fixing long-term. > Who "owns" this code? And/or where should this be discussed? I orignally added the uid range stuff to edquota. I'll add it to my list of things to look at, but if someone else wants to do something with it, feel free. -Mike -- Mike Pritchard mpp@FreeBSD.org or mpp@mppsystems.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 13:54:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 4EE88152FB for ; Mon, 20 Dec 1999 13:54:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA00717; Mon, 20 Dec 1999 13:57:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912202157.NAA00717@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Jeffrey J. Libman" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-reply-to: Your message of "Sun, 19 Dec 1999 13:06:44 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Dec 1999 13:57:47 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > after moving 54 virtual hosts to this machine, rpc.statd will not run: it > hangs; mountd runs (-r or not -r), but will not serve up mounts and dies. Sounds like you may have DNS issues with one or more of the virtual IPs. > 2) configure the loopback interface properly. (i assign all virtual ip's > to the lo0 interface). That's actually not really a good idea. Bind them to the interface that they'll be communicating on; that way you don't need to route them. > b) it has been claimed that the virtual ip's need netmask > 0xffffffff rather than 0xffffff00. i have tried it both ways. That's also not correct. The virtual addresses need to be configured _correctly_, where all the normal rules regarding netmask overlap are followed. ie. if you have three 'virtual' addresses 10.0.0.1, 10.0.0.2 and 10.0.0.3, you would add them as: 10.0.0.1 / 255.0.0.0 10.0.0.2 / 255.255.255.255 10.0.0.3 / 255.255.255.255 In other words, you add an aliased address with the correct netmask, unless it overlaps a network previously established by another address, in which case you add it with an all-ones netmask. This is the way it's always worked on FreeBSD. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 14:14:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id E8FE514A08; Mon, 20 Dec 1999 14:14:24 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id OAA44113; Mon, 20 Dec 1999 14:14:23 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912202214.OAA44113@gndrsh.dnsmgr.net> Subject: Re: mountd and rpc.statd won't run In-Reply-To: <199912202157.NAA00717@mass.cdrom.com> from Mike Smith at "Dec 20, 1999 01:57:47 pm" To: msmith@FreeBSD.ORG (Mike Smith) Date: Mon, 20 Dec 1999 14:14:23 -0800 (PST) Cc: jeffrl@wantabe.com (Jeffrey J. Libman), freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > after moving 54 virtual hosts to this machine, rpc.statd will not run: it > > hangs; mountd runs (-r or not -r), but will not serve up mounts and dies. > > Sounds like you may have DNS issues with one or more of the virtual IPs. > > > 2) configure the loopback interface properly. (i assign all virtual ip's > > to the lo0 interface). > > That's actually not really a good idea. Bind them to the interface that > they'll be communicating on; that way you don't need to route them. That one is actually a double edge sword. Binding them to the ethernet interface leads to arp table explosion on your routers and/or any other boxes on the network. We prefer to route them to lo0 in subnet chunks, but then we also run ospf on these boxes so that routing is a non-issue, we can also move a virtual from one server to another very easily. Also if you are managing large chunks of virtuals you have to go to supernetted ethernet IP addresses, and _lots_ of boxes can't cope with that. > > > b) it has been claimed that the virtual ip's need netmask > > 0xffffffff rather than 0xffffff00. i have tried it both ways. > > That's also not correct. The virtual addresses need to be configured > _correctly_, where all the normal rules regarding netmask overlap are > followed. > > ie. if you have three 'virtual' addresses 10.0.0.1, 10.0.0.2 and > 10.0.0.3, you would add them as: > > 10.0.0.1 / 255.0.0.0 > 10.0.0.2 / 255.255.255.255 > 10.0.0.3 / 255.255.255.255 Actually 10.0.0.1/32 10.0.0.2/32 10.0.0.3/32 works just fine... and I can have another box that has 10.0.0.4/32 10.0.0.5/32 on it without a bit of problem. If one uses the /8 you have above it can create some interesting routing problems for the box that it lives on if you have 10/8 variablly subnetted and or other viruals on other boxes in that IP space. > > In other words, you add an aliased address with the correct netmask, > unless it overlaps a network previously established by another address, > in which case you add it with an all-ones netmask. We _always_ use /32 (all ones) and aggregate a route if a box has a large enough chunk of virtuals to be able to create a /30 or larger. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 14:14:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by hub.freebsd.org (Postfix) with ESMTP id 4188315369; Mon, 20 Dec 1999 14:14:52 -0800 (PST) (envelope-from jeffrl@wantabe.com) Received: from cutter.wantabe.com (cutter.wantabe.com [209.16.8.8]) by cutter.wantabe.com (8.9.3/8.9.2) with ESMTP id QAA88481; Mon, 20 Dec 1999 16:14:33 -0600 (CST) (envelope-from jeffrl@wantabe.com) Date: Mon, 20 Dec 1999 16:14:33 -0600 (CST) From: "Jeffrey J. Libman" To: Mike Smith Cc: freebsd-stable@FreeBSD.ORG Subject: Re: mountd and rpc.statd won't run In-Reply-To: <199912202157.NAA00717@mass.cdrom.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 actually...my apologies to all! the issue has been resolved. somehow, the 'portmap_program' item in /etc/defaults/rc.conf for this system was removed! thus, portmap was not running, and rpc.statd could not register. *sigh* my apologies for the wasted time/effort/bandwidth...though this has spawned some interesting, if questionable discussioins about virtual hosting. cheers, jeff -- | |\ +------------------------------+ Jeffrey J. Libman, ops. mgr. | \ | Wantabe Internet Services | Wantabe, Inc. |__\ +------------------------------+ jeffrl@wantabe.com <-----|------> | access web cgi ftp news mail | (281) 493-0718 __,.-=\'`^`'~=-../__,.-= +------------------------------+ On Mon, 20 Dec 1999, Mike Smith wrote: > > > > after moving 54 virtual hosts to this machine, rpc.statd will not run: it > > hangs; mountd runs (-r or not -r), but will not serve up mounts and dies. > > Sounds like you may have DNS issues with one or more of the virtual IPs. > > > 2) configure the loopback interface properly. (i assign all virtual ip's > > to the lo0 interface). > > That's actually not really a good idea. Bind them to the interface that > they'll be communicating on; that way you don't need to route them. > > > b) it has been claimed that the virtual ip's need netmask > > 0xffffffff rather than 0xffffff00. i have tried it both ways. > > That's also not correct. The virtual addresses need to be configured > _correctly_, where all the normal rules regarding netmask overlap are > followed. > > ie. if you have three 'virtual' addresses 10.0.0.1, 10.0.0.2 and > 10.0.0.3, you would add them as: > > 10.0.0.1 / 255.0.0.0 > 10.0.0.2 / 255.255.255.255 > 10.0.0.3 / 255.255.255.255 > > In other words, you add an aliased address with the correct netmask, > unless it overlaps a network previously established by another address, > in which case you add it with an all-ones netmask. > > This is the way it's always worked on FreeBSD. > > > -- > \\ Give a man a fish, and you feed him for a day. \\ Mike Smith > \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org > \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 Dec 20 14:25:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pluto.ipass.net (pluto.ipass.net [198.79.53.5]) by hub.freebsd.org (Postfix) with ESMTP id 179831538F for ; Mon, 20 Dec 1999 14:25:48 -0800 (PST) (envelope-from rhh@ipass.net) Received: from stealth.ipass.net. (ppp-4-75.dialup.rdu.ipass.net [209.170.134.75]) by pluto.ipass.net (8.9.3/8.9.3) with ESMTP id RAA14328 for ; Mon, 20 Dec 1999 17:25:38 -0500 (EST) Received: (from rhh@localhost) by stealth.ipass.net. (8.9.3/8.8.8) id RAA01159 for freebsd-stable@FreeBSD.ORG; Mon, 20 Dec 1999 17:26:20 -0500 (EST) (envelope-from rhh) Date: Mon, 20 Dec 1999 17:26:20 -0500 From: Randall Hopper To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Message-ID: <19991220172619.A1071@ipass.net> References: <199912201836.TAA27912@dorifer.heim3.tu-clausthal.de> <199912200526.GAA03080@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <199912200526.GAA03080@dorifer.heim3.tu-clausthal.de> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme: |Randall Hopper wrote in list.freebsd-stable: | > Hi. Is there a FreeBSD assembler out there which supports the AMD 3DNow | > instruction set? | |NASM (in the ports) supports the older ones, but not the newer |ones supported by the Athlon/K7. I sent patches to the author |to support those, too, but nothing happened. Ok, thanks I'll look into NASM. The question I need to answer is whether the K6-III's 3DNow is an older or newer one. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 14:39:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id E896915082 for ; Mon, 20 Dec 1999 14:39:24 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id RAA01784; Mon, 20 Dec 1999 17:39:20 -0500 (EST) Date: Mon, 20 Dec 1999 17:39:19 -0500 (EST) From: "Matthew N. Dodd" To: "Forrest W. Christian" Cc: "Chuck O'Donnell" , stable@FreeBSD.ORG Subject: Re: edquota problem 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, 20 Dec 1999, Forrest W. Christian wrote: > I already have the uid available. (This is being ran from a custom perl > add-user script). I will fix my script accordingly. That will be more > reliable than the username anyways. > > However, this might be something someone should look at fixing long-term. > Who "owns" this code? And/or where should this be discussed? Not to toot my own horn but if you want a quota tool thats easily useful in a script you should check out the setquota util in ports. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 14:46: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 47EDE14A08 for ; Mon, 20 Dec 1999 14:46:07 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 120BZ8-0000Yi-00 for freebsd-stable@freebsd.org; Mon, 20 Dec 1999 14:46:06 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Stable Subject: alias ip addresses not pingable Message-Id: Date: Mon, 20 Dec 1999 14:46:06 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 3.4.-stable-9912201156 this is new and exciting. it used to work, and still does over on a 3.3-RC system. i imagine i have fumbled something, but don't know what. in /etc/rc.conf network_interfaces="fxp0 lo0" # List of network interfaces (lo0 is loopback). ifconfig_fxp0="inet 147.28.0.39 netmask 255.255.255.0" ifconfig_fxp0_alias0="inet 147.28.0.3 netmask 255.255.255.0" ifconfig_fxp0_alias1="inet 147.28.0.4 netmask 255.255.255.0" but rip.psg.com:/etc# ping 147.28.0.3 PING 147.28.0.3 (147.28.0.3): 56 data bytes ^C --- 147.28.0.3 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss rip.psg.com:/etc# ping 147.28.0.4 PING 147.28.0.4 (147.28.0.4): 56 data bytes ^C --- 147.28.0.4 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss rip.psg.com:/etc# ping 147.28.0.39 PING 147.28.0.39 (147.28.0.39): 56 data bytes 64 bytes from 147.28.0.39: icmp_seq=0 ttl=255 time=0.065 ms 64 bytes from 147.28.0.39: icmp_seq=1 ttl=255 time=0.057 ms 64 bytes from 147.28.0.39: icmp_seq=2 ttl=255 time=0.051 ms ^C --- 147.28.0.39 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.051/0.058/0.065/0.006 ms rip.psg.com:/etc# ifconfig fxp0 fxp0: flags=8843 mtu 1500 inet 147.28.0.39 netmask 0xffffff00 broadcast 147.28.0.255 inet 147.28.0.3 netmask 0xffffff00 broadcast 147.28.0.255 inet 147.28.0.4 netmask 0xffffff00 broadcast 147.28.0.255 ether 00:a0:c9:df:c8:4e media: 100baseTX status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP rip.psg.com:/etc# netstat -in Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll fxp0 1500 00.a0.c9.df.c8.4e 43340 0 42350 0 0 fxp0 1500 147.28/24 147.28.0.39 43340 0 42350 0 0 fxp0 1500 147.28/24 147.28.0.3 43340 0 42350 0 0 fxp0 1500 147.28/24 147.28.0.4 43340 0 42350 0 0 wl0* 1500 08.00.6a.2b.dd.cb 0 0 1 0 0 wl0* 1500 147.28.2/24 147.28.2.1 0 0 1 0 0 lo0 16384 1632 0 1632 0 0 lo0 16384 127 127.0.0.1 1632 0 1632 0 0 rip.psg.com:/etc# netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 147.28.0.58 UGSc 1558 28452 fxp0 127.0.0.1 127.0.0.1 UH 1 11 lo0 147.28/24 link#1 UC 0 0 fxp0 147.28.0.32 0:a0:6e:4:1:22 UHLW 0 14 fxp0 544 147.28.0.34 0:e0:18:98:63:22 UHLW 0 10 fxp0 546 147.28.0.39 0:a0:c9:df:c8:4e UHLW 5 1600 lo0 147.28.0.58 0:90:f2:fd:54:1c UHLW 1556 0 fxp0 1083 147.28.0.62 0:e0:18:98:63:22 UHLW 4 1927 fxp0 471 147.28.0.255 ff:ff:ff:ff:ff:ff UHLWb 1 51 fxp0 147.28.3/24 147.28.0.62 UGSc 0 0 fxp0 147.28.4/24 147.28.0.62 UGSc 0 0 fxp0 147.28.255.1/32 147.28.0.58 UGSc 0 0 fxp0 note that i have tried the aliases with a /32 netmask. same non-result. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 14:52: 1 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 02E711523D for ; Mon, 20 Dec 1999 14:51:55 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id AB1749B4D; Mon, 20 Dec 1999 17:51:46 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id A1AEEBA0C; Mon, 20 Dec 1999 17:51:46 -0500 (EST) Date: Mon, 20 Dec 1999 17:51:46 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Randy Bush Cc: FreeBSD Stable Subject: Re: alias ip addresses not pingable 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, 20 Dec 1999, Randy Bush wrote: > 3.4.-stable-9912201156 > > this is new and exciting. it used to work, and still does over on a 3.3-RC > system. i imagine i have fumbled something, but don't know what. > > in /etc/rc.conf > network_interfaces="fxp0 lo0" # List of network interfaces (lo0 is loopback). > ifconfig_fxp0="inet 147.28.0.39 netmask 255.255.255.0" > ifconfig_fxp0_alias0="inet 147.28.0.3 netmask 255.255.255.0" > ifconfig_fxp0_alias1="inet 147.28.0.4 netmask 255.255.255.0" > aliases should have a netmask of 255.255.255.255, as seen in ifconfig(8) ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@freebsd.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 14:53: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 38734153D5 for ; Mon, 20 Dec 1999 14:53:04 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 120Bfl-0000f6-00; Mon, 20 Dec 1999 14:52:57 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Chris D. Faulhaber" Cc: FreeBSD Stable Subject: Re: alias ip addresses not pingable References: Message-Id: Date: Mon, 20 Dec 1999 14:52:57 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> 3.4.-stable-9912201156 >> >> this is new and exciting. it used to work, and still does over on a 3.3-RC >> system. i imagine i have fumbled something, but don't know what. >> >> in /etc/rc.conf >> network_interfaces="fxp0 lo0" # List of network interfaces (lo0 is loopback). >> ifconfig_fxp0="inet 147.28.0.39 netmask 255.255.255.0" >> ifconfig_fxp0_alias0="inet 147.28.0.3 netmask 255.255.255.0" >> ifconfig_fxp0_alias1="inet 147.28.0.4 netmask 255.255.255.0" >> > > aliases should have a netmask of 255.255.255.255, as seen in ifconfig(8) and, at the bottom my message to which you are replying, the careful reader will find that i reported trying that with the same result. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 14:58:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.twave.net (twave.net [206.100.228.5]) by hub.freebsd.org (Postfix) with SMTP id 9FA2814EAE for ; Mon, 20 Dec 1999 14:58:21 -0800 (PST) (envelope-from brameld@twave.net) Received: from [208.219.234.24] by mail.twave.net (NTMail 3.03.0018/1.abwg) with ESMTP id ba480247 for ; Mon, 20 Dec 1999 17:57:45 -0500 Message-ID: <385EB4B6.6158B5D@twave.net> Date: Mon, 20 Dec 1999 17:59:02 -0500 From: Walter Brameld X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jeremy Shaffner Cc: John Estess , freebsd-stable@freebsd.org Subject: Re: freebsd-stable wannabe tester References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jeremy Shaffner wrote: > On Sun, 19 Dec 1999, John Estess wrote: > > > > If you want to test installation of stable, there are places you can > > > download install snapshots. > > > > I have a 26400 bps connection to the world. No kidding. I can CVSup, but > > downloading images is not an option in my current environment. > > He wasn't talking images. He means you can do an FTP install of a > snapshot just like you can for a full -RELEASE. > > -Jeremy > > -=========================================================================- > Jeremy Shaffner JORSM Internet, Regional Internet Services > System Administrator 7 Area Codes in Chicagoland and NW Indiana > jer@jorsm.com 100Mbps+ Connectivity, 56K-DS3, V.90, ISDN > support@jorsm.com Quality Service, Affordable Prices > http://www.jorsm.com Serving Gov't, Business, Individuals Since 1995 > -=========================================================================- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message I did a full install at 28,800. Being a newbie I had to do a number of installs, so I found the best thing to do was ftp all the files to my MSDOS disk, and use that for the installation media. cvsup took care of the rest. (If you're interested, I think the ftp install took about 7 or 8 hours.) Walter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 15: 3:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kit.isi.edu (kit.isi.edu [128.9.160.207]) by hub.freebsd.org (Postfix) with ESMTP id 5495914CCA for ; Mon, 20 Dec 1999 15:03:42 -0800 (PST) (envelope-from eddy@kit.isi.edu) Received: (from eddy@localhost) by kit.isi.edu (8.9.2/8.8.7) id PAA01712; Mon, 20 Dec 1999 15:02:14 -0800 (PST) (envelope-from eddy) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 20 Dec 1999 15:02:14 -0800 (PST) From: eddy@isi.edu To: "Chris D. Faulhaber" Cc: Randy Bush , FreeBSD Stable Subject: Re: alias ip addresses not pingable In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14430.46214.317449.778405@kit.isi.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Chris D. Faulhaber states: > On Mon, 20 Dec 1999, Randy Bush wrote: > > > 3.4.-stable-9912201156 > > > > this is new and exciting. it used to work, and still does over on a 3.3-RC > > system. i imagine i have fumbled something, but don't know what. > > > > in /etc/rc.conf > > network_interfaces="fxp0 lo0" # List of network interfaces (lo0 is loopback). > > ifconfig_fxp0="inet 147.28.0.39 netmask 255.255.255.0" > > ifconfig_fxp0_alias0="inet 147.28.0.3 netmask 255.255.255.0" > > ifconfig_fxp0_alias1="inet 147.28.0.4 netmask 255.255.255.0" > > > > aliases should have a netmask of 255.255.255.255, as seen in ifconfig(8) > why? i regularly use aliases with masks smaller than /32, on a 3.1 system e.g: [183] FreeBSD tik:eddy > ifconfig -a xl0: flags=8843 mtu 1500 inet 128.9.160.70 netmask 0xfffff000 broadcast 128.9.175.255 inet 10.3.2.1 netmask 0xffffff00 broadcast 10.3.2.255 ether 00:c0:4f:68:43:c1 media: 10baseT/UTP supported media: autoselect 100baseTX 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP [184] FreeBSD tik:eddy > ping 10.3.2.1 PING 10.3.2.1 (10.3.2.1): 56 data bytes 64 bytes from 10.3.2.1: icmp_seq=0 ttl=255 time=0.066 ms ^C - rusty To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 15: 5:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 708A9153B1 for ; Mon, 20 Dec 1999 15:05:55 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 120BsC-0000Fh-00; Mon, 20 Dec 1999 15:05:48 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: eddy@isi.edu Cc: FreeBSD Stable Subject: Re: alias ip addresses not pingable References: <14430.46214.317449.778405@kit.isi.edu> Message-Id: Date: Mon, 20 Dec 1999 15:05:48 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> aliases should have a netmask of 255.255.255.255, as seen in ifconfig(8) > why? i regularly use aliases with masks smaller than /32, on a 3.1 > system e.g: well, it turned out that if i boot with the alias netmask of 255.255.255.0 it does not work delete the alias ifconfig the alias with a /32 it still does not work but if i boot with a /32 alias, it works! randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 15: 7:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 49CED14DEC for ; Mon, 20 Dec 1999 15:07:51 -0800 (PST) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1003) id 58C529B4D; Mon, 20 Dec 1999 18:07:47 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 4DD17BA0C; Mon, 20 Dec 1999 18:07:47 -0500 (EST) Date: Mon, 20 Dec 1999 18:07:47 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@pawn.primelocation.net To: eddy@isi.edu Cc: Randy Bush , FreeBSD Stable Subject: Re: alias ip addresses not pingable In-Reply-To: <14430.46214.317449.778405@kit.isi.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 Mon, 20 Dec 1999 eddy@isi.edu wrote: > > Chris D. Faulhaber states: > > On Mon, 20 Dec 1999, Randy Bush wrote: > > > > > 3.4.-stable-9912201156 > > > > > > this is new and exciting. it used to work, and still does over on a 3.3-RC > > > system. i imagine i have fumbled something, but don't know what. > > > > > > in /etc/rc.conf > > > network_interfaces="fxp0 lo0" # List of network interfaces (lo0 is loopback). > > > ifconfig_fxp0="inet 147.28.0.39 netmask 255.255.255.0" > > > ifconfig_fxp0_alias0="inet 147.28.0.3 netmask 255.255.255.0" > > > ifconfig_fxp0_alias1="inet 147.28.0.4 netmask 255.255.255.0" > > > > > > > aliases should have a netmask of 255.255.255.255, as seen in ifconfig(8) > > > > why? i regularly use aliases with masks smaller than /32, on a 3.1 > system e.g: > > [183] FreeBSD tik:eddy > ifconfig -a > xl0: flags=8843 mtu 1500 > inet 128.9.160.70 netmask 0xfffff000 broadcast 128.9.175.255 > inet 10.3.2.1 netmask 0xffffff00 broadcast 10.3.2.255 > ether 00:c0:4f:68:43:c1 > media: 10baseT/UTP > supported media: autoselect 100baseTX 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP > In this case, it would be correct since they are on different subnets. The original question shows the aliases on the same subnet, so I would expect a 'correct' configuration to be shown if he is having a problem and would like help (and, yes, I did see the /32 at the bottom, but would like to see those results instead of the results from an incorrect config). ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@freebsd.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 15: 9: 2 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 34D14153AD for ; Mon, 20 Dec 1999 15:08:56 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id PAA44335; Mon, 20 Dec 1999 15:08:31 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912202308.PAA44335@gndrsh.dnsmgr.net> Subject: Re: alias ip addresses not pingable In-Reply-To: from Randy Bush at "Dec 20, 1999 03:05:48 pm" To: randy@psg.com (Randy Bush) Date: Mon, 20 Dec 1999 15:08:31 -0800 (PST) Cc: eddy@isi.edu, freebsd-stable@FreeBSD.ORG (FreeBSD Stable) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> aliases should have a netmask of 255.255.255.255, as seen in ifconfig(8) > > why? i regularly use aliases with masks smaller than /32, on a 3.1 > > system e.g: > > well, it turned out that > > if i > boot with the alias netmask of 255.255.255.0 > it does not work > delete the alias > ifconfig the alias with a /32 > it still does not work > > but if i boot with a /32 alias, it works! Take a look at netstat -rn in the 2 different situations you describe above. Your probably getting an error during the boot with alias /24 that has to do with the fact it can't add the route to the address as the route already exists. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 15:17:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-60.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.188]) by hub.freebsd.org (Postfix) with ESMTP id A92A214A2B for ; Mon, 20 Dec 1999 15:17:50 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA15126; Mon, 20 Dec 1999 23:17:13 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id XAA25413; Mon, 20 Dec 1999 23:19:12 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912202319.XAA25413@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Kent Stewart Cc: freebsd-stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: User-ppp on 3.4-Stable In-Reply-To: Message from Kent Stewart of "Sun, 19 Dec 1999 15:23:43 PST." <385D68FF.58570580@3-cities.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Dec 1999 23:19:11 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I ran into a problem today with user-ppp. I was reading about ppp and > that is when I got into trouble :). The message log keeps taking about > -alias being depricated and so I was trying to get aliasing to work with > NAT. That is when I started getting the following message Check your release notes. They mention that -alias is now -nat. -alias continues to work, but it issues a warning. > Dec 19 14:36:45 ruby ppp[454]: Warning: No available tunnel devices > found (Device busy) > > This didn't occur on 3.3S, when I used pppctl to close down user-ppp. At > least, I don't remember ever seeing that message before. Ppp is still running - ps will tell you its process id.... > User-ppp seems > to be very sensitive to rebooting the system while it is still running. > I have it configured, from the sample.conf, to use /var/run/internet and > that local domain socket is left around if it shuts down badly. What do you mean by ``badly'' ? Ppp only handles certain signals (see the man page). If you start sending other signals, ppp will take the default action. > User-ppp > won't start if it already exists. It is a simple matter to cd to > /var/run and rm it, which will allow ppp to start. Ppp will start, it'll just fail to create a diagnostic socket. > It is easy to make > ppp leave /var/run/internet. All you have to do is use top to kill the > process. The system was cvsup'ed on 18 Dec (19 Dec UTC) and the make > world was done on 19 Dec. And how are you killing it (see above) ? > When I tried starting user-ppp with the -nat option, I didn't get > aliasing for my other systems. I figure I am missing something but don't > know what. The -alias still works but I want to switch to the curent > style. -nat and -alias are synonymous - except that -alias warns that it's deprecated. > Thanks. > > Kent -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 15:21:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ruhr.de (ns.ruhr.de [141.39.224.34]) by hub.freebsd.org (Postfix) with SMTP id B2D37153FD for ; Mon, 20 Dec 1999 15:21:09 -0800 (PST) (envelope-from ue@nathan.ruhr.de) Received: (qmail 37263 invoked by alias); 20 Dec 1999 23:21:05 -0000 Received: (from ue@localhost) by nathan.ruhr.de (8.9.3/8.9.2) id AAA01888; Tue, 21 Dec 1999 00:22:40 +0100 (CET) (envelope-from ue) Date: Tue, 21 Dec 1999 00:22:40 +0100 From: Udo Erdelhoff To: stable@FreeBSD.ORG Cc: "Forrest W. Christian" Subject: Re: edquota problem Message-ID: <19991221002240.A1273@nathan.ruhr.de> References: <99Dec21.070526est.40331@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Forrest W. Christian on Mon, Dec 20, 1999 at 02:17:07PM -0700 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 02:17:07PM -0700, Forrest W. Christian wrote: > 0plus-num What happend to the rule that a username must not begin with a digit? Sometimes, I do miss the good old days :) >>IMHO, checking the parameter against the password file first > This seems the MOST reasonable way to do this. What about systems with a lot of users and/or centralized databases (NIS and friends)? I'm afraid that this change may cause unneccessary delays. I'd prefer to do a "is this an uid range"-check first and the "could this be a username"-check second. In other words, along these lines: if (((cp = strchr(*argv, '-')) != NULL) && (strspn(*argv, "0123456789") == (size_t)(cp - *argv)) && (strspn(++cp, "0123456789") == strlen(*argv) - (size_t)(cp - *argv)) && (getpwnam (*argv) == NULL)) { /* uid range entered, use it */ } else { /* Not an uid range */ } Comments? /s/Udo -- "After the night I've had, on top of the year that I've had, what I really want is a nice vile kill. But since that's currently off the menu, I'll have to settle for a few stiff drinks." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 15:23:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 158B315377 for ; Mon, 20 Dec 1999 15:23:34 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id KAA22122 for ; Tue, 21 Dec 1999 10:23:28 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id KAA13024; Tue, 21 Dec 1999 10:23:27 +1100 (EST) Message-Id: <199912202323.KAA13024@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: stable@freebsd.org Subject: xl0 won't autoneg full duplex Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Dec 1999 10:23:27 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've got a <3Com 3c905B-TX Fast Etherlink XL> plugged into a Cisco Cat5500 100Mbps switch, and I'm been running various 3.x versions from 3.0-RELEASE up to the 3.4-RC from 13/12. This card is happy to run in Full Duplex mode if I force it with ifconfig. If left to autonegotiate with the switch, the xl0 comes up 100Mbps/half-duplex, but the switch comes up full duplex. Hence I get lotsa collisions (~20%). Anything I can do to try to sort this out? This is my personal w/s so I am happy to try experimental kernels, printf debugging etc. [Yes, I know I can force it by changing ifconfig_xl0 in rc.conf...] wpaul? xl0: <3Com 3c905B-TX Fast Etherlink XL> rev 0x00 int a irq 11 on pci0.17.0 xl0: Ethernet address: 00:10:5a:a9:84:33 xl0: autoneg complete, link status good (half-duplex, 100Mbps) Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 15:36:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from moek.pir.net (moek.pir.net [209.192.237.190]) by hub.freebsd.org (Postfix) with ESMTP id B55A315062 for ; Mon, 20 Dec 1999 15:36:04 -0800 (PST) (envelope-from pir@pir.net) Received: from pir by moek.pir.net with local (Exim) id 120CLO-0006aS-00 for stable@freebsd.org; Mon, 20 Dec 1999 18:35:58 -0500 Date: Mon, 20 Dec 1999 18:35:57 -0500 From: Peter Radcliffe To: stable@freebsd.org Subject: Re: xl0 won't autoneg full duplex Message-ID: <19991220183557.F14045@pir.net> Mail-Followup-To: stable@freebsd.org References: <199912202323.KAA13024@lightning.itga.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912202323.KAA13024@lightning.itga.com.au>; from gnb@itga.com.au on Tue, Dec 21, 1999 at 10:23:27AM +1100 X-fish: < Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gregory Bond probably said: > I've got a <3Com 3c905B-TX Fast Etherlink XL> plugged into a Cisco > Cat5500 100Mbps switch, and I'm been running various 3.x versions > from 3.0-RELEASE up to the 3.4-RC from 13/12. > This card is happy to run in Full Duplex mode if I force it with ifconfig. If > left to autonegotiate with the switch, the xl0 comes up 100Mbps/half-duplex, > but the switch comes up full duplex. Hence I get lotsa collisions (~20%). Catalysts have had famously bad 100Mbit negotiation. They often won't negotiate correctly with _other_ _cisco_ products, let alone anything else (I had this problem with sparcs plugged into catalysts). Make sure your catalyst is running the most recent software ... it got a bit better. Oh, and next time, go buy foundry switches, they're nicer and cheaper. P. -- pir pir@pir.net pir@net.tufts.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 15:39:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id 4BC7F15165 for ; Mon, 20 Dec 1999 15:39:17 -0800 (PST) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn2236.bossig.com [208.26.242.236]) by corinth.bossig.com (Rockliffe SMTPRA 3.4.5) with ESMTP id ; Mon, 20 Dec 1999 15:46:13 -0800 Message-ID: <385EBE53.E3D44A4@3-cities.com> Date: Mon, 20 Dec 1999 15:40:03 -0800 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Brian Somers Cc: freebsd-stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: User-ppp on 3.4-Stable References: <199912202319.XAA25413@hak.lan.Awfulhak.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Somers wrote: > > > I ran into a problem today with user-ppp. I was reading about ppp and > > that is when I got into trouble :). The message log keeps taking about > > -alias being depricated and so I was trying to get aliasing to work with > > NAT. That is when I started getting the following message > > Check your release notes. They mention that -alias is now -nat. > -alias continues to work, but it issues a warning. I did read them but when I substituted -nat for -alias my Windows 2000 systems, which use FreeBSD as the gateway, wouldn't connect. I stopped ppp and restarted it with -alias and they connected. That is what I meant by trying to get -nat to work. I went back and carefully closed the session, killed ppp, restarted it with -nat instead of -alias, and -nat worked. Murphy is playing with my mind :). > > > Dec 19 14:36:45 ruby ppp[454]: Warning: No available tunnel devices > > found (Device busy) > > > > This didn't occur on 3.3S, when I used pppctl to close down user-ppp. At > > least, I don't remember ever seeing that message before. > > Ppp is still running - ps will tell you its process id.... > > > User-ppp seems > > to be very sensitive to rebooting the system while it is still running. > > I have it configured, from the sample.conf, to use /var/run/internet and > > that local domain socket is left around if it shuts down badly. > > What do you mean by ``badly'' ? Ppp only handles certain signals > (see the man page). If you start sending other signals, ppp will > take the default action. I wondered if that was the reason but not having encountered it before, I didn't recognize the symptom. Kent > > > User-ppp > > won't start if it already exists. It is a simple matter to cd to > > /var/run and rm it, which will allow ppp to start. > > Ppp will start, it'll just fail to create a diagnostic socket. > > > It is easy to make > > ppp leave /var/run/internet. All you have to do is use top to kill the > > process. The system was cvsup'ed on 18 Dec (19 Dec UTC) and the make > > world was done on 19 Dec. > > And how are you killing it (see above) ? > > > When I tried starting user-ppp with the -nat option, I didn't get > > aliasing for my other systems. I figure I am missing something but don't > > know what. The -alias still works but I want to switch to the curent > > style. > > -nat and -alias are synonymous - except that -alias warns that it's > deprecated. > > > Thanks. > > > > Kent > > -- > Brian > > Don't _EVER_ lose your sense of humour ! > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ Hunting Archibald Stewart, b 1802 in Ballymena, Antrim Co., NIR http://www.3-cities.com/~kstewart/genealogy/archibald_stewart.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 16:20:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 29915152B2 for ; Mon, 20 Dec 1999 16:20:08 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 120D25-0001ED-00; Mon, 20 Dec 1999 16:20:05 -0800 Date: Mon, 20 Dec 1999 16:20:00 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Peter Radcliffe Cc: stable@freebsd.org Subject: Re: xl0 won't autoneg full duplex In-Reply-To: <19991220183557.F14045@pir.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 Mon, 20 Dec 1999, Peter Radcliffe wrote: > Gregory Bond probably said: > > I've got a <3Com 3c905B-TX Fast Etherlink XL> plugged into a Cisco > > Cat5500 100Mbps switch, and I'm been running various 3.x versions > > from 3.0-RELEASE up to the 3.4-RC from 13/12. > > > This card is happy to run in Full Duplex mode if I force it with ifconfig. If > > left to autonegotiate with the switch, the xl0 comes up 100Mbps/half-duplex, > > but the switch comes up full duplex. Hence I get lotsa collisions (~20%). > > Catalysts have had famously bad 100Mbit negotiation. There are so many different kinds of Catalyst's that isn't even meaningful. For instance, Catalyst 19XX/29XX run _completely_ different software from the Catalyst 5XXX stuff. > They often won't negotiate correctly with _other_ _cisco_ products, > let alone anything else (I had this problem with sparcs plugged into > catalysts). > > Make sure your catalyst is running the most recent software ... it got > a bit better. Oh, and next time, go buy foundry switches, they're > nicer and cheaper. I find that Foundry is more expensive. If you want a basic L2 switch, the Catalyst 3524XL can't be beat, and it real simple. For more sophisticated L3/L4 stuff, the Cabletron SSR 8X00 series is nice. It can do full BGP too, for much less than a Cisco 75XX. > P. > > -- > pir pir@pir.net pir@net.tufts.edu Tom Uniserve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 16:20:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from wcn4.wcnet.net (mail.wcnet.net [216.88.248.234]) by hub.freebsd.org (Postfix) with ESMTP id 2E024153DE for ; Mon, 20 Dec 1999 16:20:54 -0800 (PST) (envelope-from jestess@wcnet.net) Received: from wcnet.net [216.88.250.116] by wcn4.wcnet.net with ESMTP (SMTPD32-5.05) id A7E22CD8009A; Mon, 20 Dec 1999 18:20:50 -0600 Message-ID: <385EC71E.725FC43@wcnet.net> Date: Mon, 20 Dec 1999 18:17:34 -0600 From: John Estess Organization: compulsive or none, depending on the day X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Re: freebsd-stable wannabe tester References: <385D9D5C.7CA03233@wcnet.net> <19991220154158.O11805@speedy.gsinet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerhard Sittig wrote: > > On Sun, Dec 19, 1999 at 21:07 -0600, John Estess wrote: > > > > Why does "Reply" send back to the address of the person and not > > the mailing list? > > Because you have a poor mail frontend, no matter what others tell > you :> I've used the lynx/tin/pine tandem in Linux for a couple years when I was stuck with a Diamond card before Xfree86 supported it, and I noticed that when sorting through my mail, I sometimes missed jpeg attachments and discarded messages before seeing the attachments. Since I use Netscape anyway for browsing, using the mailer isn't a leap. At least it doesn't core dump every five minutes like the browser. It's only a mail program. Push the button somewhat longer OR (this is what I > suggest) go ahead and find a real mail program instead of a > supplement to a browser. I'm using mutt and many others in the > know do so, too (hint, hint :). Look out for those X-Mailer > Lines and compare them to what you think how experienced the > authors are wrt computers and what they expect in terms of > functionality or flexibility or suitability ... Elitism by X-mailer headings. I never thought of that one. I never thought I'd have to resort to Pine again to get any respect :-) By the way, I'm been on many mailing list and this is the only one that I have to correct the address for. Hmmmmmmmmmmm. > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. I'm probably old enough to be your parent. [profanity deleted] -- _/ _/_/_/ || John Estess _/ _/ _/_/ || jestess@wcnet.net _/_/_/ _/_/_/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 16:23:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dbitech.bc.ca (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (Postfix) with SMTP id 4BA9E15292 for ; Mon, 20 Dec 1999 16:23:44 -0800 (PST) (envelope-from darcy@ok-connect.com) Received: (qmail 19692 invoked from network); 21 Dec 1999 00:23:42 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 21 Dec 1999 00:23:42 -0000 Message-Id: <3.0.32.19991220162448.009c6d30@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 20 Dec 1999 16:24:48 -0800 To: freebsd-stable@FreeBSD.ORG From: Darcy Buskermolen Subject: kde & top 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 just noticed something interesting. If I start KDE on my workstation, I loose the processor states ie: CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle This problem dosn't disapear if I close KDE/Xfree, the only way to get the processor states back it sot reboot the worstation. I've just done a recient CVSup/Buildworld (Yesterday) This problem may have been happeing before Just I never noticed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 16:43:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dbitech.bc.ca (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (Postfix) with SMTP id 0C4DC153C2 for ; Mon, 20 Dec 1999 16:42:51 -0800 (PST) (envelope-from darcy@ok-connect.com) Received: (qmail 20288 invoked from network); 21 Dec 1999 00:42:47 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 21 Dec 1999 00:42:47 -0000 Message-Id: <3.0.32.19991220164353.00aeae20@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 20 Dec 1999 16:43:53 -0800 To: stable@freebsd.org From: Darcy Buskermolen Subject: Re: xl0 won't autoneg full duplex Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:23 AM 12/21/99 +1100, Gregory Bond wrote: >I've got a <3Com 3c905B-TX Fast Etherlink XL> plugged into a Cisco Cat5500 >100Mbps switch, and I'm been running various 3.x versions from 3.0-RELEASE up >to the 3.4-RC from 13/12. > >This card is happy to run in Full Duplex mode if I force it with ifconfig. If >left to autonegotiate with the switch, the xl0 comes up 100Mbps/half-duplex, >but the switch comes up full duplex. Hence I get lotsa collisions (~20%). > I see the same kind of details connecting the 3c905B to a catalist 1900 series, however I can't force it into Full duplex mode. This problem is present in both 2.2.8 and 3.3-stable. I'm pretty much convinced that it is a cisco thing because the cisco can't sync full duplex to an Allied Telesyn MS400 Switch. The 3c908B can sync to the Allied Telesyn at 100Mb FD fine. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 16:55:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id E669314EBF for ; Mon, 20 Dec 1999 16:55:53 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id LAA22574 for ; Tue, 21 Dec 1999 11:55:52 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id LAA29658; Tue, 21 Dec 1999 11:55:51 +1100 (EST) Message-Id: <199912210055.LAA29658@lightning.itga.com.au> From: Gregory Bond Cc: stable@FreeBSD.ORG Subject: Re: xl0 won't autoneg full duplex In-reply-to: Your message of Tue, 21 Dec 1999 10:23:27 +1100. Date: Tue, 21 Dec 1999 11:55:51 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: > This card is happy to run in Full Duplex mode if I force it with ifconfig. If > left to autonegotiate with the switch, the xl0 comes up 100Mbps/half-duplex, > but the switch comes up full duplex. Hence I get lotsa collisions (~20%). Thanks for the responses. Andrew W. Flury pointed out that the switch doesn't do autoneg right if it is hardwired to 100mbps, which looks like it was the problem. I'll keep an eye on it and see what happens. Greg. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 17:15: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id A90741545C; Mon, 20 Dec 1999 17:14:54 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991221011246.IWGJ7552.mail.rdc3.on.home.com@tristan.net>; Mon, 20 Dec 1999 17:12:46 -0800 Content-Length: 900 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <385D8697.D237F7B7@wcnet.net> Date: Mon, 20 Dec 1999 20:12:05 -0500 (EST) From: Colin To: John Estess , freebsd-qa@FreeBSD.ORG Subject: RE: freebsd-stable wannabe tester Cc: freebsd-stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The other thing you might try is subscribing to freebsd-qa. Assuming our friend the moderator doesn't mind ;) This is where we've been tracking the tests on 3.4-RC most recently. On 20-Dec-1999 John Estess wrote: > I'm been shamed into becoming a -stable tester (read > comp.unix.bsd.freebsd.misc if you care how) and wonder what kind of help > you need. Just download and compile latest kernel? Anything else? > > -- > _/ _/_/_/ || John Estess > _/ _/ _/_/ || jestess@wcnet.net > _/_/_/ _/_/_/ || C- FAQ: http://www.eskimo.com/~scs/C-faq/top.html > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message ---------------------------------- E-Mail: Colin Date: 20-Dec-1999 Time: 20:09:51 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 17:25:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id D88E0153D6 for ; Mon, 20 Dec 1999 17:25:22 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 120E3D-0001oJ-00; Mon, 20 Dec 1999 17:25:19 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Michael Lucas Cc: FreeBSD Stable Subject: Re: Sys Admin article on Linux emulation Message-Id: Date: Mon, 20 Dec 1999 17:25:19 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > options "P1003_1B" #POSIX infrastructure > options "_KPOSIX_PRIORITY_SCHEDULING" #Built-in POSIX priority scheduling > options "_KPOSIX_VERSION=199309L" #POSIX version kernel is built for > options SYSVSHM #System V shared memory > options SYSVMSG #System V semaphores > options SYSVSEM #System V messaging > options USER_LDT #allow user-level control of i386 ldt is the last one really needed for stuff such as staroffice? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 17:39:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id 7997A14CFA for ; Mon, 20 Dec 1999 17:39:15 -0800 (PST) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from alphard (alphard [128.130.111.37]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id CAA29233; Tue, 21 Dec 1999 02:39:05 +0100 (MET) Date: Tue, 21 Dec 1999 02:39:05 +0100 (MET) From: Gerald Pfeifer To: Randy Bush Cc: Michael Lucas , FreeBSD Stable Subject: Re: Sys Admin article on Linux emulation 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, 20 Dec 1999, Randy Bush wrote: >> options USER_LDT #allow user-level control of i386 ldt > is the last one really needed for stuff such as staroffice? It's need for Wine, for example. (BTW, why isn't that supported out-of-the-box?) Gerald -- Gerald "Jerry" 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 Mon Dec 20 17:58:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id CC75A153C8 for ; Mon, 20 Dec 1999 17:58:42 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-208-170-119-162.dialup.HiWAAY.net [208.170.119.162]) by mail.HiWAAY.net (8.9.3/8.9.0) with ESMTP id TAA03656 for ; Mon, 20 Dec 1999 19:58:40 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id TAA37058 for ; Mon, 20 Dec 1999 19:58:39 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199912210158.TAA37058@nospam.hiwaay.net> X-Mailer: exmh version 2.1.1 10/15/1999 To: FreeBSD Stable From: David Kelly Subject: Process Scheduling (was: Re: Sys Admin article on Linux emulation) In-reply-to: Message from Randy Bush of "Mon, 20 Dec 1999 17:25:19 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Dec 1999 19:58:39 -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > options "P1003_1B" #POSIX infrastructure > > options "_KPOSIX_PRIORITY_SCHEDULING" #Built-in POSIX priority scheduling > > options "_KPOSIX_VERSION=199309L" #POSIX version kernel is built for Speaking of scheduling, how does _KPOSIX_PRIORITY_SCHEDULING affect the kernel's scheduling algorithm? For instance I've observed dnetc (the http://www.distributed.net/ client (/usr/ports/misc/rc5des and direct) runs nice +20, yet often keeps 10% to 20% of the CPU when other CPU intensive processes only get 80% to 90%. Would have hoped/expected a process at maximum niceness would not run at all if a normal-nice process wanted to run. Does _KPOSIX_PRIORITY_SCHEDULING alter the scheduler, or simply provide more controls? Believe with the 3.0 series FreeBSD now has more real-time scheduling options but these are restricted to root? man rtprio says: Only root is allowed to set realtime or idle priority for a process. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 18: 0:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from megaweapon.zigg.com (megaweapon.zigg.com [206.114.60.8]) by hub.freebsd.org (Postfix) with ESMTP id 6C12114C49 for ; Mon, 20 Dec 1999 18:00:45 -0800 (PST) (envelope-from matt@zigg.com) Received: from localhost (matt@localhost) by megaweapon.zigg.com (8.9.3/8.9.3) with ESMTP id UAA05108; Mon, 20 Dec 1999 20:58:38 -0500 (EST) (envelope-from matt@zigg.com) Date: Mon, 20 Dec 1999 20:58:35 -0500 (EST) From: Matt Behrens To: Gerald Pfeifer Cc: Randy Bush , Michael Lucas , FreeBSD Stable Subject: Re: Sys Admin article on Linux emulation 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 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 21 Dec 1999, Gerald Pfeifer wrote: > On Mon, 20 Dec 1999, Randy Bush wrote: > >> options USER_LDT #allow user-level control of i386 ldt > > is the last one really needed for stuff such as staroffice? > It's need for Wine, for example. > > (BTW, why isn't that supported out-of-the-box?) I don't claim to know a lot about system architecture, but it sounds to me like on your average box it could be a security risk of sorts, or at the very least a potential admin headache. I subscribe to the school of giving user processes as little as possible to get their jobs done, especially when multiple users are present. Matt Behrens Owner/Administrator, zigg.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE4Xt7N+xq4JbgNGlMRAo8BAKChrpjTxJ/Uc38GCJP7uDgWoXC7xACfR5Q/ LSpJBmb4sm0MYNLVZOqjP3I= =2XvQ -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 19:19: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pericles.IPAustralia.gov.au (pericles.IPAustralia.gov.au [202.14.186.30]) by hub.freebsd.org (Postfix) with ESMTP id B423C14F62; Mon, 20 Dec 1999 19:19:02 -0800 (PST) (envelope-from carl@xena.aipo.gov.au) Received: (from smap@localhost) by pericles.IPAustralia.gov.au (8.9.3/8.9.3) id OAA65250; Tue, 21 Dec 1999 14:19:00 +1100 (EST) (envelope-from carl@xena.aipo.gov.au) Received: from newton.aipo.gov.au(10.0.100.18) by pericles.IPAustralia.gov.au via smap (V2.0) id xma065244; Tue, 21 Dec 99 14:18:50 +1100 Received: from localhost (carl@localhost) by newton.aipo.gov.au (8.9.3/8.9.2) with ESMTP id OAA20868; Tue, 21 Dec 1999 14:18:50 +1100 (EST) (envelope-from carl@xena.aipo.gov.au) X-Authentication-Warning: newton.aipo.gov.au: carl owned process doing -bs Date: Tue, 21 Dec 1999 14:18:50 +1100 (EST) From: Carl Makin X-Sender: carl@newton.aipo.gov.au To: questions@freebsd.org, stable@freebsd.org Subject: FibreChannel, FC-Al and NetApp. 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 using FC, FC-AL or NetApp filers on a FreeBSD 3.x-STABLE system? I'm very interested in some real world comparisons of the various technologies. Carl. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 19:26:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.gmx.net (mail1.gmx.net [194.221.183.61]) by hub.freebsd.org (Postfix) with SMTP id 3CEF914C88 for ; Mon, 20 Dec 1999 19:26:32 -0800 (PST) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 6929 invoked by uid 0); 21 Dec 1999 03:26:30 -0000 Received: from pc19f60cb.dip.t-dialin.net (HELO speedy.gsinet) (193.159.96.203) by mail1.gmx.net with SMTP; 21 Dec 1999 03:26:30 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id VAA15156 for freebsd-stable@freebsd.org; Mon, 20 Dec 1999 21:39:29 +0100 Date: Mon, 20 Dec 1999 21:39:29 +0100 From: Gerhard Sittig To: FreeBSD Stable Subject: Re: PCI internal modem Message-ID: <19991220213929.X11805@speedy.gsinet> Mail-Followup-To: FreeBSD Stable References: <199912201649.KAA85652@klentaq.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912201649.KAA85652@klentaq.com>; from stabilizer@klentaq.com on Mon, Dec 20, 1999 at 10:49:44AM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 10:49 -0600, Wayne M Barnes wrote: > > How do I get my PCI modem card to work with FreeBSD 3.4? > > [ ... ] > > CSN 1 Vendor ID: CSC4236 [0x3642630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] I could be wrong, but why does this sound like a sound card to me? Don't look Crystal's chips (respective PnP cards) look like this? I don't have one around, but could someone check this? Anyway -- IF it is a PCI card, why should it ever show up in the ISA PnP section? If the port is a real serial port, it should behave and look just like any other serial port (i.e. io=0x2F8 for the third one, etc). If it is a so called WinModem, chances are bad that there will be driver if the manufacturer or dealer won't provide one. virtually yours - Gerhard Sittig -- mail -s "get pgp key" Gerhard.Sittig@gmx.net < /dev/null If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 19:44:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id D885414EB2 for ; Mon, 20 Dec 1999 19:44:38 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id UAA13944; Mon, 20 Dec 1999 20:44:37 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id UAA21042; Mon, 20 Dec 1999 20:44:37 -0700 (MST) Message-Id: <199912210344.UAA21042@harmony.village.org> To: Gerhard Sittig Subject: Re: PCI internal modem Cc: FreeBSD Stable In-reply-to: Your message of "Mon, 20 Dec 1999 21:39:29 +0100." <19991220213929.X11805@speedy.gsinet> References: <19991220213929.X11805@speedy.gsinet> <199912201649.KAA85652@klentaq.com> Date: Mon, 20 Dec 1999 20:44:37 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <19991220213929.X11805@speedy.gsinet> Gerhard Sittig writes: : ISA PnP section? If the port is a real serial port, it should He found it by 'demsg | grep serial'. It took me a while to read that in his original message. I've started the process of bringing the pci support code into the tree. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 19:58:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id D157D14A25 for ; Mon, 20 Dec 1999 19:58:43 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991221035843.ZRLM9446.mail.rdc1.ct.home.com@home.com> for ; Mon, 20 Dec 1999 19:58:43 -0800 Message-ID: <385EFAEF.5F286795@home.com> Date: Mon, 20 Dec 1999 22:58:39 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: FreeBSD Stable Subject: SOFTUPDATES Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is anyone running the SOFTUPDATES option with Stable? I just enabled it and was wondering if there are any issues I should be aware of performance wise. Any problems? I enabled it for the /usr filesystem. Any reason why / is not specifically recommended? Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 20: 1:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailgw1.netvision.net.il (mailgw1.netvision.net.il [194.90.1.14]) by hub.freebsd.org (Postfix) with ESMTP id 0886214D15 for ; Mon, 20 Dec 1999 20:01:54 -0800 (PST) (envelope-from ak@freenet.co.uk) Received: from freenet.co.uk (RAS1-p53.rlz.netvision.net.il [62.0.168.55]) by mailgw1.netvision.net.il (8.9.3/8.9.3) with ESMTP id GAA06252; Tue, 21 Dec 1999 06:01:34 +0200 (IST) Message-ID: <385EFD1F.F96CEB73@freenet.co.uk> Date: Tue, 21 Dec 1999 04:07:59 +0000 From: Alex X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Warner Losh Cc: Wayne M Barnes , FreeBSD Stable Subject: Re: PCI internal modem References: <199912201649.KAA85652@klentaq.com> <199912201722.KAA17015@harmony.village.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Warner Losh wrote: > > In message <199912201649.KAA85652@klentaq.com> Wayne M Barnes writes: > : How do I get my PCI modem card to work with FreeBSD 3.4? > > *IF* it isn't a win modem, soft modem, etc, then you can apply the > following patch, rebuild your kernel and create /dev/cua4, et al in > /dev. > > If it is a win modem, you lose. Sell it to some sucker and buy a real > pci modem. > > Patch: http://www.freebsd.org/~imp/Psio Just wondering - why isn't this in the tree? You seem to have had this patch for quite some time now (or at least announced it several months ago). Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 20:27: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from aurora.sol.net (aurora.sol.net [206.55.65.76]) by hub.freebsd.org (Postfix) with ESMTP id 8516B14E95; Mon, 20 Dec 1999 20:27:05 -0800 (PST) (envelope-from jgreco@aurora.sol.net) Received: (from jgreco@localhost) by aurora.sol.net (8.9.2/8.9.2/SNNS-1.02) id WAA34841; Mon, 20 Dec 1999 22:27:04 -0600 (CST) From: Joe Greco Message-Id: <199912210427.WAA34841@aurora.sol.net> Subject: 3.4R sysinstall blows up To: install@freebsd.org, stable@freebsd.org Date: Mon, 20 Dec 1999 22:27:03 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG So I go to install 3.4R on a box. sysinstall blows spectacularly as I go to select the distributions. Joe's abbreviated method for 3.4R install. Box in question is a Pentium 200 with 3 ST31055N drives on an ASUS NCR controller, 32MB RAM, dual SMC Ethernet controller, VGA video (serial session log enclosed though, same error). Custom install: Partition disk 1. Disk is previously unlabeled, having been formatted. Select "All" to use entire disk. Select Standard MBR. Quit out, leaving additional drives unselected. Label disk 1. 160M / 180M swap 200M /usr 120M /usr/local 140M /var remainder /export/home/u0 Exit. Select distributions. Select custom (8?). Pouf. "A signal 11 was caught - I'm saving what I can and shutting If you can reproduce the problem, please turn Debug on in the Options menu for the extra information it provides in debugging problems like this." (tried that and didn't seem to get anything BTW) I'd suspect hw except that the box was previously running fine, and it keeps hitting this in the exact same spot. Tried different floppies, etc. too. Is this just me, or is it an actual bug? ... Joe ------------------------------------------------------------------------------- Joe Greco - Systems Administrator jgreco@ns.sol.net Solaria Public Access UNIX - Milwaukee, WI 414/342-4847 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 20:27:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id C520A153DB for ; Mon, 20 Dec 1999 20:27:56 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Mon, 20 Dec 1999 20:27:55 -0800 From: "David Schwartz" To: , "FreeBSD Stable" Subject: RE: SOFTUPDATES Date: Mon, 20 Dec 1999 20:27:55 -0800 Message-ID: <000001bf4b6b$c07acb40$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 Importance: Normal In-Reply-To: <385EFAEF.5F286795@home.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Is anyone running the SOFTUPDATES option with Stable? I just enabled it > and was wondering if there are any issues I should be aware of > performance wise. Any problems? I enabled it for the /usr > filesystem. Any reason why / is not specifically recommended? I've been quite happy with softupdates on my STABLE machines. I see the biggest performance improvements in file extractions from tarballs. Enabling softupdates on / is not recommended primarily because that filesystem is not frequently written to. Another reason not to enable softupdates on / is that you may not have enough free space to do a 'make world' (softupdates delays the returning of empty space to the filesystem). One final reason is possible increased risk. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 20:28:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id A001D151A3 for ; Mon, 20 Dec 1999 20:28:52 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA14071; Mon, 20 Dec 1999 21:28:50 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA21308; Mon, 20 Dec 1999 21:28:50 -0700 (MST) Message-Id: <199912210428.VAA21308@harmony.village.org> To: Alex Subject: Re: PCI internal modem Cc: Wayne M Barnes , FreeBSD Stable In-reply-to: Your message of "Tue, 21 Dec 1999 04:07:59 GMT." <385EFD1F.F96CEB73@freenet.co.uk> References: <385EFD1F.F96CEB73@freenet.co.uk> <199912201649.KAA85652@klentaq.com> <199912201722.KAA17015@harmony.village.org> Date: Mon, 20 Dec 1999 21:28:50 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <385EFD1F.F96CEB73@freenet.co.uk> Alex writes: : Just wondering - why isn't this in the tree? -current is radically different than -stable. Changes generally go in via -current, and I've not had time to port the changes to -current. I gave bruce the changes to -stable review today, and will commit them once I've cleaned them with the bdelint(1). : You seem to have had this patch for quite some time now (or at least : announced it several months ago). Yes. I did. Warer To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 20:46:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from point.osg.gov.bc.ca (point.osg.gov.bc.ca [142.32.102.44]) by hub.freebsd.org (Postfix) with ESMTP id AAD351536E for ; Mon, 20 Dec 1999 20:46:06 -0800 (PST) (envelope-from cy@cschuber.net.gov.bc.ca) Received: (from daemon@localhost) by point.osg.gov.bc.ca (8.8.7/8.8.8) id UAA24594; Mon, 20 Dec 1999 20:46:02 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29), claiming to be "cwsys.cwsent.com" via SMTP by point.osg.gov.bc.ca, id smtpda24592; Mon Dec 20 20:45:50 1999 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id UAA55672; Mon, 20 Dec 1999 20:45:49 -0800 (PST) Message-Id: <199912210445.UAA55672@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpdF55276; Mon Dec 20 20:45:23 1999 X-Mailer: exmh version 2.1.1 10/15/1999 Reply-To: Cy Schubert - ITSD Open Systems Group From: Cy Schubert - ITSD Open Systems Group X-OS: FreeBSD 3.4-RELEASE X-Sender: cy To: "David Schwartz" Cc: tsikora@powerusersbbs.com, "FreeBSD Stable" Subject: Re: SOFTUPDATES In-reply-to: Your message of "Mon, 20 Dec 1999 20:27:55 PST." <000001bf4b6b$c07acb40$021d85d1@youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 20 Dec 1999 20:45:22 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <000001bf4b6b$c07acb40$021d85d1@youwant.to>, "David Schwartz" writes : > > > Is anyone running the SOFTUPDATES option with Stable? I just enabled it > > and was wondering if there are any issues I should be aware of > > performance wise. Any problems? I enabled it for the /usr > > filesystem. Any reason why / is not specifically recommended? > > I've been quite happy with softupdates on my STABLE machines. I see the > biggest performance improvements in file extractions from tarballs. > > Enabling softupdates on / is not recommended primarily because that > filesystem is not frequently written to. Another reason not to enable > softupdates on / is that you may not have enough free space to do a 'make > world' (softupdates delays the returning of empty space to the filesystem). > One final reason is possible increased risk. I've enabled softupdates on / (/ being a 750 MB filesystem, about 60% full, containing /, /usr, and /var) on a couple machines at work. I also use softupdates on one of my machines at home, however on that system I do not use softupdates on / and /usr (on different disks) because they're hardly written to. I've had no problems with data integrity or system availability due to softupdates (knock on wood). Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 Sun/DEC Team, UNIX Group Internet: Cy.Schubert@uumail.gov.bc.ca ITSD Province of BC "e**(i*pi)+1=0" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 21:11:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tranq1.tranquility.net (tranq1.tranquility.net [206.156.230.1]) by hub.freebsd.org (Postfix) with ESMTP id 9ECEE153CC for ; Mon, 20 Dec 1999 21:11:08 -0800 (PST) (envelope-from stephen@math.missouri.edu) Received: from math.missouri.edu (stephen.tranquility.net [206.156.230.78]) by tranq1.tranquility.net (8.9.2/8.9.2) with ESMTP id XAA18552 for ; Mon, 20 Dec 1999 23:11:06 -0600 (CST) Message-ID: <385F0BEA.ABBD694F@math.missouri.edu> Date: Mon, 20 Dec 1999 23:11:06 -0600 From: Stephen Montgomery-Smith X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Subject: Errata for 3.4R Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I was looking at the FreeBSD web page, and I noticed that at the top of the page for the Errata for FreeBSD 3.4R ( http://www.freebsd.org/releases/3.4R/errata.html ) that it says: FreeBSD 3.3 Errata Notes ^ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 21:53:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 9E3A0150D4 for ; Mon, 20 Dec 1999 21:53:51 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 120IF0-0006wb-00; Mon, 20 Dec 1999 21:53:46 -0800 Date: Mon, 20 Dec 1999 21:53:40 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: David Schwartz Cc: tsikora@powerusersbbs.com, FreeBSD Stable Subject: RE: SOFTUPDATES In-Reply-To: <000001bf4b6b$c07acb40$021d85d1@youwant.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, 20 Dec 1999, David Schwartz wrote: ... > Enabling softupdates on / is not recommended primarily because that > filesystem is not frequently written to. Another reason not to enable > softupdates on / is that you may not have enough free space to do a 'make > world' (softupdates delays the returning of empty space to the filesystem). > One final reason is possible increased risk. I don't know anyone who recommends against softupdates on root. I understand it just isn't exactly straightforward to enable (see archives) I don't understand your comment about "make world", as I don't see how that would be a problem, unless you only have a tiny amount of free space in "/". > DS Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 21:55:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.dbitech.bc.ca (i.caniserv.com [139.142.95.1]) by hub.freebsd.org (Postfix) with SMTP id CA66D15157 for ; Mon, 20 Dec 1999 21:55:15 -0800 (PST) (envelope-from darcy@ok-connect.com) Received: (qmail 6321 invoked from network); 21 Dec 1999 05:55:14 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (darcyb@139.142.95.253) by 139.142.95.10 with SMTP; 21 Dec 1999 05:55:14 -0000 Message-Id: <3.0.32.19991220215620.009ec160@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Mon, 20 Dec 1999 21:56:20 -0800 To: freebsd-stable@freebsd.org From: Darcy Buskermolen Subject: 3.4 Release CD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When trying to downaload the 3.4R cd, form the IOS-Images dir, I get a permission denyed. is this because the file is still being uploaded, or is it becasue the file mis chmod'd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 21:59:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 5CED014E96 for ; Mon, 20 Dec 1999 21:59:42 -0800 (PST) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id WAA57065; Mon, 20 Dec 1999 22:59:40 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id WAA38101; Mon, 20 Dec 1999 22:59:40 -0700 (MST) (envelope-from jjreynold@home.com) From: John and Jennifer Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14431.5964.275453.126779@whale.home-net> Date: Mon, 20 Dec 1999 22:59:40 -0700 (MST) To: Darcy Buskermolen Cc: freebsd-stable@freebsd.org Subject: Re: 3.4 Release CD In-Reply-To: <3.0.32.19991220215620.009ec160@mail.ok-connect.com> References: <3.0.32.19991220215620.009ec160@mail.ok-connect.com> X-Mailer: VM 6.73 under Emacs 20.4.1 Cc: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Monday, December 20, Darcy Buskermolen wrote: ] > When trying to downaload the 3.4R cd, form the IOS-Images dir, I get a > permission denyed. is this because the file is still being uploaded, or is > it becasue the file mis chmod'd > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message I noticed the exact same thing and already mailed something off to -questions about it (and jkh). ???????? -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.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 Dec 20 22: 5:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id 59F7115280 for ; Mon, 20 Dec 1999 22:05:44 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Mon, 20 Dec 1999 22:05:42 -0800 From: "David Schwartz" To: "Tom" Cc: , "FreeBSD Stable" Subject: RE: SOFTUPDATES Date: Mon, 20 Dec 1999 22:05:42 -0800 Message-ID: <000001bf4b79$69c8b330$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, 20 Dec 1999, David Schwartz wrote: > > ... > > Enabling softupdates on / is not recommended primarily because that > > filesystem is not frequently written to. Another reason not to enable > > softupdates on / is that you may not have enough free space to > do a 'make > > world' (softupdates delays the returning of empty space to the > filesystem). > > One final reason is possible increased risk. > > I don't know anyone who recommends against softupdates on root. I > understand it just isn't exactly straightforward to enable (see archives) > > I don't understand your comment about "make world", as I don't see how > that would be a problem, unless you only have a tiny amount of free space > in "/". Most people keep the amount of free space on / minimal. I did a default FreeBSD install on a machine, and it did this: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/da0s1a 31743 19641 9563 67% / /dev/da0s1f 3929331 982235 2632750 27% /usr /dev/da0s1e 29751 2220 25151 8% /var DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 22:11:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp3.jp.psi.net (smtp3.jp.psi.net [154.33.63.113]) by hub.freebsd.org (Postfix) with ESMTP id 9611E1529E for ; Mon, 20 Dec 1999 22:11:28 -0800 (PST) (envelope-from ishi-jdc@magical3.egg.or.jp) Received: from [154.33.63.58] (helo=mail8.jp.psi.net) by smtp3.jp.psi.net with esmtp (Exim 3.12 #1) id 120IW8-0004FN-00 for freebsd-stable@freebsd.org; Tue, 21 Dec 1999 15:11:28 +0900 Received: from dmax008-pool068.tokyo2.tnis.egg.or.jp ([210.129.250.69] helo=magical3.egg.or.jp) by mail8.jp.psi.net with esmtp (Exim 3.12 #1) id 120IW6-0000Zl-00 for freebsd-stable@FreeBSD.org; Tue, 21 Dec 1999 15:11:26 +0900 Message-ID: <385F1A20.48982F8C@magical3.egg.or.jp> Date: Tue, 21 Dec 1999 15:11:44 +0900 From: =?iso-2022-jp?B?GyRCQFBLXBsoQiAbJEI4d0c9GyhC?= Organization: IQP Department, JDC X-Mailer: Mozilla 4.7 [ja] (WinNT; I) X-Accept-Language: ja MIME-Version: 1.0 To: freebsd-stable@FreeBSD.org Subject: Request for adding mailing list Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable subscribe cvs-all -- --------------------------------------------- Mitsuyoshi Ishimoto, Japan Direx Corporation mail ishi-jdc@magical3.egg.or.jp --------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 22:14:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 1642B153C7 for ; Mon, 20 Dec 1999 22:14:20 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 120IYr-0007Np-00; Mon, 20 Dec 1999 22:14:17 -0800 Date: Mon, 20 Dec 1999 22:14:11 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: David Schwartz Cc: tsikora@powerusersbbs.com, FreeBSD Stable Subject: RE: SOFTUPDATES In-Reply-To: <000001bf4b79$69c8b330$021d85d1@youwant.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, 20 Dec 1999, David Schwartz wrote: > Most people keep the amount of free space on / minimal. I did a default > FreeBSD install on a machine, and it did this: > > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/da0s1a 31743 19641 9563 67% / > /dev/da0s1f 3929331 982235 2632750 27% /usr > /dev/da0s1e 29751 2220 25151 8% /var And that is very bad. I don't see /tmp on a separate filesystem either. That makes it worse. When you run out of space on "/", bad things happen. I can't believe that anyone would recommend a "minimal" amount of space for root. You need enough space for root so that it never runs out. Also, don't forget about users. You'll need about 7.5MB of space per 15K users in master.passwd, plus another 7.5MB per 15K just to rebuild the *.db files properly. > DS Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 22:18:24 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shell.webmaster.com (mail.webmaster.com [209.133.28.73]) by hub.freebsd.org (Postfix) with ESMTP id A1AD115424 for ; Mon, 20 Dec 1999 22:18:13 -0800 (PST) (envelope-from davids@webmaster.com) Received: from whenever ([209.133.29.2]) by shell.webmaster.com (Post.Office MTA v3.5.3 release 223 ID# 0-12345L500S10000V35) with SMTP id com; Mon, 20 Dec 1999 22:18:12 -0800 From: "David Schwartz" To: "Tom" Cc: , "FreeBSD Stable" Subject: RE: SOFTUPDATES Date: Mon, 20 Dec 1999 22:18:12 -0800 Message-ID: <000001bf4b7b$28922430$021d85d1@youwant.to> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2377.0 In-Reply-To: Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > And that is very bad. I don't see /tmp on a separate filesystem either. > That makes it worse. When you run out of space on "/", bad things happen. > I can't believe that anyone would recommend a "minimal" amount of space > for root. You need enough space for root so that it never runs out. Well, this is another argument entirely. I agree with you, but nevertheless, a large number of FreeBSD machines are configured this way. Here's another box that I let FreeBSD's installer accept its defaults on: /dev/wd0s1a 31775 12726 16507 44% / /dev/wd0s1f 412967 220902 159028 58% /usr /dev/wd0s1e 29727 4675 22674 17% /var And here's another: Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/wd0s1a 31775 14563 14670 50% / /dev/wd0s1f 1802143 1073924 584048 65% /usr /dev/wd0s1e 29727 2866 24483 10% /var So that's why you may hear people saying you shouldn't enable softupdates on /. If you're clueful enough to understand why you can ignore that advice for your particular machine, then fine. DS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 22:31:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 842021537C for ; Mon, 20 Dec 1999 22:31:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA03285 for ; Mon, 20 Dec 1999 22:31:17 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: stable@freebsd.org Subject: Don't use the "custom" install option for 3.4 Date: Mon, 20 Dec 1999 22:31:17 -0800 Message-ID: <3281.945757877@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's broken, sorry (I usually only test with "Novice" since so many more people use it). I'll add something to the errata, until then please use Novice or Express. I'm also sure that this is a completely stupid bug and I should have it fixed shortly. It's also my hope that someone else will be taking over sysinstall for 3.5 since I'm no longer an effective maintainer for it - there's just too much other stuff on my plate these days and I now appear to be adding more bugs than I'm fixing. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 23:35:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id B8C4414E6B for ; Mon, 20 Dec 1999 23:35:51 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id IAA26624 for freebsd-stable@FreeBSD.ORG; Tue, 21 Dec 1999 08:35:50 +0100 (CET) (envelope-from olli) Date: Tue, 21 Dec 1999 08:35:50 +0100 (CET) From: Oliver Fromme Message-Id: <199912210735.IAA26624@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote in list.freebsd-stable: > On Mon, Dec 20, 1999 at 07:36:31PM +0100, Oliver Fromme wrote: > [...] > > About 50%, that is, about 4.5 hours (instead of 9) on average > > per work unit, on an Athlon-500. And I did only optimize the > > FFT and didn't touch the rest. With a bit more effort, further > > improvements would be certainly possible. > > Wow! Quite a difference. Not having an Athlon but > > CPU: AMD-K6(tm) 3D processor (399.81-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > AMD Features=0x80000800 > > would that also make such a difference on the K6-2? Athlon has > different 3Dnow I think ?? The difference would be somewhat smaller, but there would certainly be a difference, too. The Athlon supports the same 3DNow instruction as the K6 family, but it also supports some additional instructions which are very useful. If you're interested in the details, I recommend the following documents: "AMD Athlon Processor x86 Code Optimization Guide" (22007) "3DNow Technology Manual" (21928) "MMX Enhanced Processor Multimedia Technology" (20726) "AMD Extensions to the 3DNow and MMX Instruction Sets" (22466) The number in parentheses is the AMD document order number. All of these documents can be order from AMD on CD-ROM. They can also be downloaded from AMD's web site at the following URL in PDF format: http://www.amd.com/support/techdocdir.html 3DNow instructions work on floating point values, while MMX instructions work on integer values. However, 3DNow code uses the same registers as MMX instructions, so it is common to intermix them (for example, use MMX instructions to move values into registers, then use 3DNow instructions for computation, then use an MMX instruction to negate the result). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Mon Dec 20 23:44:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from azazel.zer0.org (azazel.zer0.org [209.133.53.200]) by hub.freebsd.org (Postfix) with ESMTP id 9EE9F14C49 for ; Mon, 20 Dec 1999 23:44:25 -0800 (PST) (envelope-from gsutter@azazel.zer0.org) Received: (from gsutter@localhost) by azazel.zer0.org (8.9.3/8.9.2) id XAA06921; Mon, 20 Dec 1999 23:42:50 -0800 (PST) (envelope-from gsutter) Date: Mon, 20 Dec 1999 23:42:50 -0800 From: Gregory Sutter To: "Jordan K. Hubbard" Cc: stable@FreeBSD.ORG Subject: Re: Don't use the "custom" install option for 3.4 Message-ID: <19991220234250.O56510@azazel.zer0.org> References: <3281.945757877@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <3281.945757877@zippy.cdrom.com> Organization: Zer0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 10:31:17PM -0800, Jordan K. Hubbard wrote: > It's broken, sorry (I usually only test with "Novice" since so many > more people use it). I'll add something to the errata, until then > please use Novice or Express. I'm also sure that this is a completely Will the 3.4 CDs be pressed with this bug? Greg -- Gregory S. Sutter The best way to accelerate Windows mailto:gsutter@pobox.com is at 9.8 m/s^2. http://www.pobox.com/~gsutter/ PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 0:26:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from xkis.kis.ru (xkis.kis.ru [195.98.32.200]) by hub.freebsd.org (Postfix) with ESMTP id 65A4A14D9D for ; Tue, 21 Dec 1999 00:26:40 -0800 (PST) (envelope-from dv@dv.ru) Received: from localhost (dv@localhost) by xkis.kis.ru (8.9.3/8.9.3) with SMTP id LAA05125; Tue, 21 Dec 1999 11:26:27 +0300 (MSK) Date: Tue, 21 Dec 1999 11:26:26 +0300 (MSK) From: Dmitry Valdov X-Sender: dv@xkis.kis.ru To: "Rodney W. Grimes" Cc: freebsd-stable@freebsd.org Subject: Re: alias ip addresses not pingable In-Reply-To: <199912202308.PAA44335@gndrsh.dnsmgr.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 Hi! btw, I've seen the same problem. I think it doesn't depend on netmask. I'll try to explain: ifconfig doesn't add route for new alias to loopback if You ping new IP address before adding it as alias. For example: 1. We are going to add IP 1.2.3.4 as alias to ed0 2. ping 1.2.3.4 (before adding) - from the same host (!) 3. ifconfig ed0 1.2.3.4 255.255.255.255 alias Result: ping from other host - OK ping from localhost - not OK 4. route add 1.2.3.4 127.0.0.1 ping from localhost - OK. If You skip step 2 in this example, You'll not need to route add 1.2.3.4 to loopback - it adds automaticly. So, in his example when he tests it after boot it "makes" step 2. as in my example. Why? Sorry for my english. I think, You understood. Example: comin# ping 195.98.32.140 PING 195.98.32.140 (195.98.32.140): 56 data bytes ^C --- 195.98.32.140 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss comin# ifconfig fxp0 inet 195.98.32.140 netmask 255.255.255.255 alias comin# ping 195.98.32.140 PING 195.98.32.140 (195.98.32.140): 56 data bytes ping: sendto: Host is down ping: sendto: Host is down ping: sendto: Host is down ^C --- 195.98.32.140 ping statistics --- 5 packets transmitted, 0 packets received, 100% packet loss and: comin# ifconfig fxp0 inet 195.98.32.141 netmask 255.255.255.255 alias comin# ping 195.98.32.141 PING 195.98.32.141 (195.98.32.141): 56 data bytes 64 bytes from 195.98.32.141: icmp_seq=0 ttl=255 time=0.084 ms 64 bytes from 195.98.32.141: icmp_seq=1 ttl=255 time=0.051 ms ^C --- 195.98.32.141 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.051/0.068/0.084/0.016 ms Dmitry. On Mon, 20 Dec 1999, Rodney W. Grimes wrote: > Date: Mon, 20 Dec 1999 15:08:31 -0800 (PST) > From: "Rodney W. Grimes" > To: Randy Bush > Cc: eddy@isi.edu, FreeBSD Stable > Subject: Re: alias ip addresses not pingable > > > >> aliases should have a netmask of 255.255.255.255, as seen in ifconfig(8) > > > why? i regularly use aliases with masks smaller than /32, on a 3.1 > > > system e.g: > > > > well, it turned out that > > > > if i > > boot with the alias netmask of 255.255.255.0 > > it does not work > > delete the alias > > ifconfig the alias with a /32 > > it still does not work > > > > but if i boot with a /32 alias, it works! > > Take a look at netstat -rn in the 2 different situations you describe > above. Your probably getting an error during the boot with alias /24 > that has to do with the fact it can't add the route to the address as > the route already exists. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 0:39:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id BA7EE1540E for ; Tue, 21 Dec 1999 00:39:31 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id BAA16455; Tue, 21 Dec 1999 01:39:30 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912210839.BAA16455@freeway.dcfinc.com> Subject: Re: AMD 3DNow instructions on FreeBSD In-Reply-To: <199912210735.IAA26624@dorifer.heim3.tu-clausthal.de> from Oliver Fromme at "Dec 21, 99 08:35:50 am" To: freebsd-stable@FreeBSD.ORG Date: Tue, 21 Dec 1999 01:39:30 -0700 (MST) Cc: 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, Oliver Fromme wrote: > The Athlon supports the same 3DNow instruction as the K6 > family, but it also supports some additional instructions > which are very useful. If you're interested in the details, > I recommend the following documents: > > "AMD Athlon Processor x86 Code Optimization Guide" (22007) > "3DNow Technology Manual" (21928) > "MMX Enhanced Processor Multimedia Technology" (20726) > "AMD Extensions to the 3DNow and MMX Instruction Sets" (22466) > > The number in parentheses is the AMD document order number. > All of these documents can be order from AMD on CD-ROM. They > can also be downloaded from AMD's web site at the following > URL in PDF format: > > http://www.amd.com/support/techdocdir.html > > 3DNow instructions work on floating point values, while MMX > instructions work on integer values. However, 3DNow code uses > the same registers as MMX instructions, so it is common to > intermix them (for example, use MMX instructions to move values > into registers, then use 3DNow instructions for computation, > then use an MMX instruction to negate the result). Tell me more about the SETIathome project. Did you have source to work with? Did you reverse-engineer something? I know the SETIathome folks are very skeptical about changes to the client software, for fear of a bug poluting the results pool. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 1: 0:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailhost.tue.nl (mailhost.tue.nl [131.155.2.5]) by hub.freebsd.org (Postfix) with ESMTP id 237FE1540E for ; Tue, 21 Dec 1999 01:00:17 -0800 (PST) (envelope-from K.R.A.M.Schreel@wtb.tue.nl) Received: from wop5.wop.wtb.tue.nl [131.155.56.55] by mailhost.tue.nl (8.9.3) id KAA12923 (ESMTP); Tue, 21 Dec 1999 10:00:13 +0100 (MET) Received: from wtb.tue.nl (wop24.wop.wtb.tue.nl [131.155.56.116]) by wop5.wop.wtb.tue.nl (8.8.8/8.6.9) with ESMTP id JAA14689; Tue, 21 Dec 1999 09:00:12 GMT Message-ID: <385F419B.71AAEBFF@wtb.tue.nl> Date: Tue, 21 Dec 1999 10:00:11 +0100 From: Koen Schreel Organization: Eindhoven University of Technology X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: Darcy Buskermolen Cc: freebsd-stable@FreeBSD.ORG Subject: Re: kde & top References: <3.0.32.19991220162448.009c6d30@mail.ok-connect.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Darcy Buskermolen wrote: > > I've just noticed something interesting. > If I start KDE on my workstation, I loose the processor states ie: > > CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle > You don't happen to have an Asus P2B-D(S) motherboard and are running SMP? If so, upgrade the BIOS to version 1010 or 1011. Koen. -- Dr. K.R.A.M. Schreel | Eindhoven University of Technology | Faculty of Mechanical Engineering Combustion Research | Section Energy Technology | P. O. Box 513 K.R.A.M.Schreel@wtb.tue.nl | 5600 MB Eindhoven, The Netherlands To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 1:53:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.scc.nl (node1374.a2000.nl [62.108.19.116]) by hub.freebsd.org (Postfix) with ESMTP id 225FD153C7 for ; Tue, 21 Dec 1999 01:53:23 -0800 (PST) (envelope-from freebsd-stable@scc.nl) Received: (from daemon@localhost) by mail.scc.nl (8.9.3/8.9.3) id KAA26908 for stable@FreeBSD.org; Tue, 21 Dec 1999 10:44:12 +0100 (CET) (envelope-from freebsd-stable@scc.nl) Received: from GATEWAY by dwarf.hq.scc.nl with netnews for stable@FreeBSD.org (stable@FreeBSD.org) To: stable@FreeBSD.org Date: Tue, 21 Dec 1999 10:44:09 +0100 From: Marcel Moolenaar Message-ID: <385F4BE9.8177D2AC@scc.nl> Organization: SCC vof Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit References: , Subject: Re: Sys Admin article on Linux emulation Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gerald Pfeifer wrote: > > On Mon, 20 Dec 1999, Randy Bush wrote: > >> options USER_LDT #allow user-level control of i386 ldt > > is the last one really needed for stuff such as staroffice? > > It's need for Wine, for example. > > (BTW, why isn't that supported out-of-the-box?) One reason is that a GENERIC kernel is "optimized" to support the widest range of devices and can't grow any bigger. This means that anything not important for installation gets removed in favor for device drivers. More reasons exist, which are probably more emotionally sensitive so I won't go into that :-) -- Marcel Moolenaar mailto:marcel@scc.nl SCC Internetworking & Databases http://www.scc.nl/ The FreeBSD project mailto:marcel@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 3:16:56 1999 Delivered-To: freebsd-stable@freebsd.org Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (Postfix) with ESMTP id 222E0152A7 for ; Tue, 21 Dec 1999 03:16:21 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com (gj-14-180.bta.net.cn [202.106.14.180]) by public.bta.net.cn (8.9.3/8.9.3) with ESMTP id SAA23382 for ; Tue, 21 Dec 1999 18:07:59 +0800 (CST) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.8.7) id SAA50337; Tue, 21 Dec 1999 18:02:12 +0800 (CST) (envelope-from robinson) Date: Tue, 21 Dec 1999 18:02:12 +0800 (CST) From: Michael Robinson Message-Id: <199912211002.SAA50337@netrinsics.com> To: freebsd-stable@freebsd.org Subject: Extremely bizarre filename behavior (3.3-RELEASE) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have an image repository indexed by md5 checksum. The repository has about eleven thousand images, and about two dozen directory entries like this: ---------------- # ls -li cb/d3 total 60 468593 -rwxr-xr-x 1 nobody staff 30063 Dec 17 18:54 cbd3b669fd20b2164b4391b053ed02e8.JPG # ls cb/d3/cbd3b669fd20b2164b4391b053ed02e8.JPG ls: cb/d3/cbd3b669fd20b2164b4391b053ed02e8.JPG: No such file or directory ---------------- In other words, there is a directory entry, but the file can't be accessed directly. Then things get wierd: ---------------- # cd cb/d3 # touch * # ls -l total 60 -rwxr-xr-x 1 nobody staff 30063 Dec 21 17:49 cbd3b669fd20b2164b4391b053ed02e8.JPG ---------------- So, the directory entry is attached to a real live inode, whose modification time can be updated with "touch *". But then it gets really, really wierd: ---------------- # touch cbd3b669fd20b2164b4391b053ed02e8.JPG # ls cbd3b669fd20b2164b4391b053ed02e8.JPG cbd3b669fd20b2164b4391b053ed02e8.JPG # ls cbd3b669fd20b2164b4391b053ed02e8.JPG cbd3b669fd20b2164b4391b053ed02e8.JPG # ls -li total 60 468650 -rw-r--r-- 1 root staff 0 Dec 21 17:50 cbd3b669fd20b2164b4391b053ed02e8.JPG 468593 -rwxr-xr-x 1 nobody staff 30063 Dec 21 17:49 cbd3b669fd20b2164b4391b053ed02e8.JPG ---------------- This filesystem passes fsck without a peep. Is it possible that the vast number of long, random filenames is causing lossage in the filename hashing? The system is 3.3-RELEASE. I'm going to upgrade to 3.4-RELEASE tonight to see if the problems persist. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 4: 7:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id F25801542C for ; Tue, 21 Dec 1999 04:07:26 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id NAA07803 for freebsd-stable@FreeBSD.ORG; Tue, 21 Dec 1999 13:07:25 +0100 (CET) (envelope-from olli) Date: Tue, 21 Dec 1999 13:07:25 +0100 (CET) From: Oliver Fromme Message-Id: <199912211207.NAA07803@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: Extremely bizarre filename behavior (3.3-RELEASE) Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Michael Robinson wrote in list.freebsd-stable: > I have an image repository indexed by md5 checksum. The repository has > about eleven thousand images, and about two dozen directory entries like > this: > [...] > # touch cbd3b669fd20b2164b4391b053ed02e8.JPG > # ls cbd3b669fd20b2164b4391b053ed02e8.JPG > cbd3b669fd20b2164b4391b053ed02e8.JPG > # ls > cbd3b669fd20b2164b4391b053ed02e8.JPG cbd3b669fd20b2164b4391b053ed02e8.JPG > # ls -li > total 60 > 468650 -rw-r--r-- 1 root staff 0 Dec 21 17:50 cbd3b669fd20b2164b4391b053ed02e8.JPG > 468593 -rwxr-xr-x 1 nobody staff 30063 Dec 21 17:49 cbd3b669fd20b2164b4391b053ed02e8.JPG > > This filesystem passes fsck without a peep. Is it possible that the vast > number of long, random filenames is causing lossage in the filename > hashing? I don't think so. The FS should not care about the structure of filenames. A lot of applications (web caches, news spools) use similarly "hashed" filenames. If there was a problem with them, it would certainly have been discovered much earlier. Are you _sure_ that that filename in question does not contain any spaces, tabs, control characters etc.? It seems to have a space appended at the end, but that might be an artifact of pasting it to the newsreader. But you should definitely check this. It would certainly explain what you're experiencing. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 4:24:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id E756514A2B for ; Tue, 21 Dec 1999 04:24:19 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id KAA29419; Tue, 21 Dec 1999 10:21:14 GMT (envelope-from nik) Date: Tue, 21 Dec 1999 10:21:11 +0000 From: Nik Clayton To: Stephen Montgomery-Smith Cc: freebsd-stable@freebsd.org Subject: Re: Errata for 3.4R Message-ID: <19991221102111.B21841@catkin.nothing-going-on.org> References: <385F0BEA.ABBD694F@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <385F0BEA.ABBD694F@math.missouri.edu>; from Stephen Montgomery-Smith on Mon, Dec 20, 1999 at 11:11:06PM -0600 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 11:11:06PM -0600, Stephen Montgomery-Smith wrote: > I was looking at the FreeBSD web page, and I noticed that at the top of the > page for the Errata for FreeBSD 3.4R > ( http://www.freebsd.org/releases/3.4R/errata.html ) > that it says: > > FreeBSD 3.3 Errata Notes Oh bugger, that was one of mine. That's what I get for doing the update at 2am in the morning. I'll fix it ASAP. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 4:24:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from nothing-going-on.demon.co.uk (nothing-going-on.demon.co.uk [193.237.89.66]) by hub.freebsd.org (Postfix) with ESMTP id E29331545C for ; Tue, 21 Dec 1999 04:24:27 -0800 (PST) (envelope-from nik@nothing-going-on.demon.co.uk) Received: (from nik@localhost) by nothing-going-on.demon.co.uk (8.9.3/8.9.3) id KAA22159; Tue, 21 Dec 1999 10:18:07 GMT (envelope-from nik) Date: Tue, 21 Dec 1999 10:18:06 +0000 From: Nik Clayton To: Gerhard Sittig Cc: FreeBSD Stable Subject: Re: PCI internal modem Message-ID: <19991221101806.A21841@catkin.nothing-going-on.org> References: <199912201649.KAA85652@klentaq.com> <19991220213929.X11805@speedy.gsinet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <19991220213929.X11805@speedy.gsinet>; from Gerhard Sittig on Mon, Dec 20, 1999 at 09:39:29PM +0100 Organization: FreeBSD Project Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 09:39:29PM +0100, Gerhard Sittig wrote: > On Mon, Dec 20, 1999 at 10:49 -0600, Wayne M Barnes wrote: > > > > How do I get my PCI modem card to work with FreeBSD 3.4? > > > > [ ... ] > > > > CSN 1 Vendor ID: CSC4236 [0x3642630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] > > I could be wrong, but why does this sound like a sound card to > me? Don't look Crystal's chips (respective PnP cards) look like > this? I don't have one around, but could someone check this? I haven't been following the discussion prior to this, but this message caught my eye. I have a Crystal soundcard, and you're write, that is the probe message. Mine looks like this; [...] Probing for PnP devices: CSN 1 Vendor ID: CSC4236 [0x3642630e] Serial 0xffffffff Comp ID: @@@0000 [0x0000 0000] mss_attach 1 at 0x530 irq 5 dma 1:3 flags 0x13 pcm1 (CS423x/Yamaha/AD1816 sn 0xffffffff) at 0x530-0x537 irq 5 drq 1 fl ags 0x13 on isa Probing for devices on the ISA bus: [...] If that helps. N -- If you want to imagine the future, imagine a tennis shoe stamping on a penguin's face forever. --- with apologies to George Orwell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 5:18:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from public.bta.net.cn (public.bta.net.cn [202.96.0.97]) by hub.freebsd.org (Postfix) with ESMTP id 102FE14F70 for ; Tue, 21 Dec 1999 05:18:19 -0800 (PST) (envelope-from robinson@netrinsics.com) Received: from netrinsics.com (gj-14-180.bta.net.cn [202.106.14.180]) by public.bta.net.cn (8.9.3/8.9.3) with ESMTP id VAA07716 for ; Tue, 21 Dec 1999 21:18:00 +0800 (CST) Received: (from robinson@localhost) by netrinsics.com (8.9.3/8.8.7) id VAA50647 for freebsd-stable@FreeBSD.ORG; Tue, 21 Dec 1999 21:16:14 +0800 (CST) (envelope-from robinson) Date: Tue, 21 Dec 1999 21:16:14 +0800 (CST) From: Michael Robinson Message-Id: <199912211316.VAA50647@netrinsics.com> To: freebsd-stable@freebsd.org Subject: Re: Extremely bizarre filename behavior (3.3-RELEASE) In-Reply-To: <199912211002.SAA50337@netrinsics.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wrote: >This filesystem passes fsck without a peep. Is it possible that the vast >number of long, random filenames is causing lossage in the filename >hashing? The system is 3.3-RELEASE. I'm going to upgrade to 3.4-RELEASE >tonight to see if the problems persist. Ok, I'm an idiot. Terminating spaces were leaking in from Windows users through Samba. It never occurred to me that sending filenames through a pipe from "find" to "xargs" (how I discovered the problem) will strip whitespace from filenames. Sorry. Older and wiser, now. -Michael Robinson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 6: 4:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by hub.freebsd.org (Postfix) with ESMTP id C99AF15506 for ; Tue, 21 Dec 1999 06:04:24 -0800 (PST) (envelope-from adamo@dblab.ece.ntua.gr) Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id QAA64869; Tue, 21 Dec 1999 16:04:14 +0200 (EET) Received: (from george@localhost) by dblab.ece.ntua.gr (8.10.0.Beta10/8.10.0.Beta10) id dBLE4b244407; Tue, 21 Dec 1999 16:04:37 +0200 (EET) Date: Tue, 21 Dec 1999 16:04:37 +0200 From: Yiorgos Adamopoulos To: David Schwartz Cc: tsikora@powerusersbbs.com, FreeBSD Stable Subject: Re: SOFTUPDATES Message-ID: <19991221160437.A40524@dblab.ece.ntua.gr> Reply-To: adamo@dblab.ece.ntua.gr References: <385EFAEF.5F286795@home.com> <000001bf4b6b$c07acb40$021d85d1@youwant.to> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <000001bf4b6b$c07acb40$021d85d1@youwant.to>; from davids@webmaster.com on Mon, Dec 20, 1999 at 08:27:55PM -0800 X-URL: http://home.eu.org/~adamo Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 08:27:55PM -0800, David Schwartz wrote: > One final reason is possible increased risk. Or forgetting to build a kernel with it sometime afterwards ;-) -- There is no such thing as silly questions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 6:16:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.gmx.net (mail1.gmx.net [194.221.183.61]) by hub.freebsd.org (Postfix) with SMTP id DA45A14EAB for ; Tue, 21 Dec 1999 06:16:23 -0800 (PST) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 9907 invoked by uid 0); 21 Dec 1999 14:16:19 -0000 Received: from pc19f5d08.dip.t-dialin.net (HELO speedy.gsinet) (193.159.93.8) by mail1.gmx.net with SMTP; 21 Dec 1999 14:16:19 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id MAA16372 for freebsd-stable@freebsd.org; Tue, 21 Dec 1999 12:41:18 +0100 Date: Tue, 21 Dec 1999 12:41:18 +0100 From: Gerhard Sittig To: freebsd-stable@freebsd.org Subject: Re: freebsd-stable wannabe tester Message-ID: <19991221124118.A15372@speedy.gsinet> Mail-Followup-To: freebsd-stable@freebsd.org References: <385D9D5C.7CA03233@wcnet.net> <19991220154158.O11805@speedy.gsinet> <385EC71E.725FC43@wcnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <385EC71E.725FC43@wcnet.net>; from jestess@wcnet.net on Mon, Dec 20, 1999 at 06:17:34PM -0600 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG completely OT, feel free to delete this junk and end this dead end of a thread ... On Mon, Dec 20, 1999 at 18:17 -0600, John Estess wrote: > Gerhard Sittig wrote: > > > > On Sun, Dec 19, 1999 at 21:07 -0600, John Estess wrote: > > > > > > Why does "Reply" send back to the address of the person and > > > not the mailing list? > > > > Because you have a poor mail frontend, no matter what others > > tell you :> [ ... ] Sorry to see this here on the list. This one was my reply by PM and not everybody seems to know the difference between public and private messages :< I'm aware of that it's been OT and not at all of general interest (although I'm convinced of what I wrote). Just in case others ARE interested: mutt (besides being very free in configurability, supporting MIME, having pgp built in, colorizing headers / sigs / quotations / etc, matching patterns to take actions, handling multiple inboxes, customizes settings according to the folder you are in or the person you write to if you want it to, etc) has some special features for handling large message volumes: list-reply (next to reply and group-reply) and threading. This makes mailing lists more comfortable to keep track of and reduces traffic (and avoids the felt need to correct any addresses by hand but still provides all the functionality any other mailer does, too). Grouping old and new or important and unimportant stuff by colors does some good, too. And if you're used to do your work using a keyboard instead of going miles with your mouse everything runs smoothly and is really quickly done. For more info have a look at www.mutt.org, please. I didn't want to start a religious war here (that's why I didn't want to talk about mailers or editors in public -- PM is a completely different matter). Sorry, once more. It's really sad to see personal messages being torn to this forum ... If you feel like discussing this with me, please do a favour to the list's readers and reply in private. I can promise there won't be a summary everyone's happy with, that's why I will never try to write one :) > > Look out for those X-Mailer Lines and compare them to what > > you think how experienced the authors are wrt computers and > > what they expect in terms of functionality or flexibility or > > suitability ... > > Elitism by X-mailer headings. I never thought of that one. I > never thought I'd have to resort to Pine again to get any > respect :-) Not to let a wrong impression bubble up: I don't conclude from used software to behaviour. But when behaviour is somewhat non conformant (sorry, I lack a better word for what I want to express and "defective", "silly" or "brain dead" are too strong words for this) or important features are missing or certain errors occur, one might be tempted to guess "Ahh, it's THIS mailer causing THAT trouble.". And too many times the assumptions prove themselves correct ... We all know the repetition of "failed" messages of Netscape users when they actually succeeded resulting in multiple identical messages causing many threads to show up since the replying readers don't "agree" on which message to "follow". We know that MS doesn't respect the convention to use "Re: " or "(fwd)" and thus confusing almost everyone who's not coming from the same region as the author. We see a thread being split or misformed every time Outlook or Lotus rips "References:" or "In-Reply-To:" off which makes it hard to follow a flowing discussion. We know the posters who don't know what exactly they refer to and since in doubt cite everything in full (including sigs and list footers). We see and hate the blown up multipart/alternative messages which don't provide any higher amount of information for allocating four times the volume of plain text. We see some people "collect" address entries over a thread's life time using group-reply which makes the list of recipients even longer than the actual message being sent and which sends copies over and over to people getting the message already since they're on the list. And we see the regular question "Why won't 'reply' reply to the list?" which comes from broken mailers missing useful reply functions or hiding them from the user. And this misfeatures' list could be continued without end ... Not everything of the above is a software failure. Some things just come from pure laziness or ignorance -- that's where wrong defaults do their job since many people cannot even imagine that a default setup is already defective. It could be so easy to have a great cooperation and painless handling of even large volume lists if it wasn't for some really bad annoyances ... I personally don't want to accept any defective software. This is even more a priority to me once I know of alternatives. And I want to configure the aspects whenever I'm not satisfied with the defaults (or default behaviour). That's why I've been working on UNIX for ages escaping the other systems (or even fleeing them). That's what I said above: Look at people's expectations and they almost certainly won't employ certain software which disqualifies in some ways. Unless they're forced to do so for any reason I can't tell or even think of. That's why I believe there's a drift to certain software once you experience the things you don't like about your current software and look out for something more comfortable or more appropriate for this job. Some programs might be nice to click on and to look at. But they cannot cope with real volume or more specific requirements growing over time. Please forgive me if I should have used the wrong words. Since English is not my native language chances are good that I wrote complete nonsense actually meaning something different. But I'm sure replies will tell me so ... This message is not meant to be a justification for the cited words I wrote. I just felt I had to clear up that I don't judge posters from the software they use. BUT I'm against nonthinking action. And I see a common sense about "applicable" software amongst experienced users. virtually yours - Gerhard Sittig -- mail -s "get pgp key" Gerhard.Sittig@gmx.net < /dev/null If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 6:49:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cx587235-a.chnd1.az.home.com (cx587235-a.chnd1.az.home.com [24.11.88.170]) by hub.freebsd.org (Postfix) with ESMTP id 2FE4015423 for ; Tue, 21 Dec 1999 06:49:57 -0800 (PST) (envelope-from jjreynold@home.com) Received: from whale.home-net (whale [192.168.1.2]) by cx587235-a.chnd1.az.home.com (8.9.3/8.9.3) with ESMTP id HAA58244; Tue, 21 Dec 1999 07:49:56 -0700 (MST) (envelope-from jjreynold@home.com) Received: (from jjreynold@localhost) by whale.home-net (8.9.3/8.9.3) id HAA39720; Tue, 21 Dec 1999 07:49:56 -0700 (MST) (envelope-from jjreynold@home.com) From: John and Jennifer Reynolds MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14431.37779.785746.826760@whale.home-net> Date: Tue, 21 Dec 1999 07:49:55 -0700 (MST) To: Joe Greco Subject: Re: 3.4R sysinstall blows up In-Reply-To: <199912210427.WAA34841@aurora.sol.net> References: <199912210427.WAA34841@aurora.sol.net> X-Mailer: VM 6.73 under Emacs 20.4.1 Cc: stable@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Monday, December 20, Joe Greco wrote: ] > So I go to install 3.4R on a box. sysinstall blows spectacularly as I go > to select the distributions. > > Joe's abbreviated method for 3.4R install. Box in question is a Pentium > 200 with 3 ST31055N drives on an ASUS NCR controller, 32MB RAM, dual SMC > Ethernet controller, VGA video (serial session log enclosed though, same > error). > > Custom install: > > Partition disk 1. Disk is previously unlabeled, having been formatted. > Select "All" to use entire disk. Select Standard MBR. Quit out, leaving > additional drives unselected. Jordan announced to -stable last night that the custom install option in sysinstall is hosed somehow. Don't know much more than that. -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= John Reynolds Chandler Capabilities Engineering, CDS, Intel Corporation jreynold@sedona.ch.intel.com My opinions are mine, not Intel's. Running jjreynold@home.com FreeBSD 3.4-STABLE. FreeBSD: The Power to Serve. http://members.home.com/jjreynold/ Come join us!!! @ http://www.FreeBSD.org/ =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 6:54:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id A5ED614E94 for ; Tue, 21 Dec 1999 06:54:34 -0800 (PST) (envelope-from talon@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.9.3/jtpda-5.3.2) with ESMTP id PAA49299 for ; Tue, 21 Dec 1999 15:54:29 +0100 (CET) Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id PAA12700 for ; Tue, 21 Dec 1999 15:54:29 +0100 (MET) Received: from (talon@localhost) by niobe.lpthe.jussieu.fr (8.9.3/jtpda-5.3.1) id PAA83986 for freebsd-stable@FreeBSD.ORG; Tue, 21 Dec 1999 15:54:29 +0100 (CET) Date: Tue, 21 Dec 1999 15:54:29 +0100 From: Michel TALON To: FreeBSD Stable Subject: Re: SOFTUPDATES Message-ID: <19991221155429.B83918@lpthe.jussieu.fr> Mail-Followup-To: FreeBSD Stable References: <385EFAEF.5F286795@home.com> <000001bf4b6b$c07acb40$021d85d1@youwant.to> <19991221160437.A40524@dblab.ece.ntua.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991221160437.A40524@dblab.ece.ntua.gr>; from adamo@dblab.ece.ntua.gr on Tue, Dec 21, 1999 at 04:04:37PM +0200 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To enable softupdates on / is very simple: boot -s at the loader prompt and do tunefs -n enable / It is my understanding that if you forget to enable softupdates in kernel conf the flag is simply not recognized and causes no trouble. Finally if you are on a rather small disk, for example on a laptop, the config which does not loose space and allows occasional big files in /tmp etc. is to put everything in / flatly. I have done that and never encountered any problem. -- Michel TALON To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 7:45:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pebkac.owp.csus.edu (pebkac.owp.csus.edu [130.86.232.245]) by hub.freebsd.org (Postfix) with ESMTP id 60C9315432 for ; Tue, 21 Dec 1999 07:45:51 -0800 (PST) (envelope-from joseph.scott@owp.csus.edu) Received: from owp.csus.edu (mail.owp.csus.edu [130.86.232.247]) by pebkac.owp.csus.edu (8.9.3/8.9.3) with ESMTP id HAA63851; Tue, 21 Dec 1999 07:45:51 -0800 (PST) (envelope-from joseph.scott@owp.csus.edu) Message-ID: <385FA0AC.70BB6E9@owp.csus.edu> Date: Tue, 21 Dec 1999 15:45:48 +0000 From: Joseph Scott X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: stable@FreeBSD.ORG Subject: vm_page_cache & sendmail dying Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Came in to find that sendmail had died on the following box ( uname -a ) : FreeBSD pebkac.owp.csus.edu 3.3-STABLE FreeBSD 3.3-STABLE #0: Fri Nov 19 10:39:46 PST 1999 root@pebkac.owp.csus.edu:/usr/src/sys/compile/PEBKAC i386 After a quick look in root's mail I discover several items from the log file : > pid 58426 (sendmail), uid 0: exited on signal 11 > pid 58542 (sendmail), uid 0: exited on signal 11 > pid 58612 (sendmail), uid 0: exited on signal 11 > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > pid 59958 (sendmail), uid 0: exited on signal 11 > pid 60331 (sendmail), uid 0: exited on signal 11 > pid 60344 (sendmail), uid 0: exited on signal 11 > pid 190 (sendmail), uid 0: exited on signal 6 > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > vm_page_cache: attempting to cache busy page > pid 60354 (sendmail), uid 0: exited on signal 6 Needless to say it looks like something is happening with vm_page_cache on this box that is not making sendmail happy. Any thoughts as to what might be the problem? This is a brand new box from about 1 month ago, PII450. I'm cvsup'ing -STABLE right now in a hope that it's been resolved already. Thanks. -- Joseph Scott joseph.scott@owp.csus.edu Office Of Water Programs - CSU Sacramento To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 8:14:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mark.kingsu.ab.ca (mark.kingsu.ab.ca [199.185.113.37]) by hub.freebsd.org (Postfix) with ESMTP id 8A57F14F70 for ; Tue, 21 Dec 1999 08:14:15 -0800 (PST) (envelope-from bwood@KingsU.ab.ca) Received: from KingsU.ab.ca (kingsnet.kingsu.ab.ca [199.185.113.33]) by mark.kingsu.ab.ca (8.9.3/8.9.2) with ESMTP id JAA67999 for ; Tue, 21 Dec 1999 09:14:11 -0700 (MST) (envelope-from bwood@KingsU.ab.ca) Message-Id: <199912211614.JAA67999@mark.kingsu.ab.ca> Received: from KINGSNET/SpoolDir by KingsU.ab.ca (Mercury 1.44); 21 Dec 99 09:14:19 -0700 Received: from SpoolDir by KINGSNET (Mercury 1.44); 21 Dec 99 09:14:15 -0700 From: "Broderick Wood" Organization: The King's University College To: freebsd-stable@FreeBSD.ORG Date: Tue, 21 Dec 1999 09:14:14 -0700 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: 3.4 Release CD In-reply-to: <14431.5964.275453.126779@whale.home-net> References: <3.0.32.19991220215620.009ec160@mail.ok-connect.com> X-mailer: Pegasus Mail for Win32 (v3.12a) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > [ On Monday, December 20, Darcy Buskermolen wrote: ] > > When trying to downaload the 3.4R cd, form the IOS-Images dir, I get > > a permission denyed. is this because the file is still being > > uploaded, or is it becasue the file mis chmod'd > > > I noticed the exact same thing and already mailed something off to > -questions about it (and jkh). > Noticd this as well. When you FTP though, it gives you a different e- mail to address FTP problems to. I sent a message off to that address as well. We just need to be patient now I guess. --------------------------- -BMW- To soar like an eagle, fly like a dove. (bwood@kingsu.ab.ca) Broderick Wood, Director of Information Technology Services The King's University College 9125 - 50 Street Edmonton, Alberta T6B 2H3 (780) 465-8315 (780) 465-3534 (FAX) ><> <>< To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 8:14:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hematita.dcc.ufmg.br (hematita.dcc.ufmg.br [150.164.10.11]) by hub.freebsd.org (Postfix) with ESMTP id A53D3154A8 for ; Tue, 21 Dec 1999 08:14:27 -0800 (PST) (envelope-from xlinux@dcc.ufmg.br) Received: from turmalina.dcc.ufmg.br (turmalina [150.164.10.1]) by hematita.dcc.ufmg.br (8.8.8/8.8.8) with SMTP id OAA02986 for ; Tue, 21 Dec 1999 14:14:21 -0200 (EDT) Date: Tue, 21 Dec 1999 14:14:21 -0200 (EDT) From: Bernardo Souza Alves da Silva To: freebsd-stable@freebsd.org Subject: ISO Images 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, I try to download the ISO-IMAGE of FreeBSD 3.4-RELEASE but I can't 'cause the file attributes don't let me do it. Please! Change the files attributes or answer me "Why can't I download the 3.4-RELEASE FreeBSD ISO-IMAGE?" Thanx a lot! Bernardo - xlinux@campus.cce.ufmg.br To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 8:21:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hyperion.aepnet.com (chronos.aepnet.com [208.129.247.8]) by hub.freebsd.org (Postfix) with ESMTP id CA52914F23 for ; Tue, 21 Dec 1999 08:21:41 -0800 (PST) (envelope-from chris@aepnet.com) Received: from localhost (chris@localhost) by hyperion.aepnet.com (8.9.3/8.9.3) with ESMTP id JAA19750; Tue, 21 Dec 1999 09:21:28 -0700 (MST) (envelope-from chris@aepnet.com) X-Authentication-Warning: hyperion.aepnet.com: chris owned process doing -bs Date: Tue, 21 Dec 1999 09:21:28 -0700 (MST) From: chris To: Michel TALON Cc: FreeBSD Stable Subject: Re: SOFTUPDATES In-Reply-To: <19991221155429.B83918@lpthe.jussieu.fr> 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 actually, you can't enable it on a mounted disk, you must boot off of the kern and mfsroot floppies (and if you're without a net connection to another machine, you'll need the fixit floppy (does it have tunefs on it?)) -- chris On Tue, 21 Dec 1999, Michel TALON wrote: > To enable softupdates on / is very simple: boot -s at the loader prompt > and do > > tunefs -n enable / > > It is my understanding that if you forget to enable softupdates in > kernel conf the flag is simply not recognized and causes no trouble. > > Finally if you are on a rather small disk, for example on a laptop, > the config which does not loose space and allows occasional big files > in /tmp etc. is to put everything in / flatly. I have done that and > never encountered any problem. > > -- > > Michel TALON > > > > 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 Tue Dec 21 8:25:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from techpower.net (techpower.net [205.133.231.1]) by hub.freebsd.org (Postfix) with ESMTP id 3C1CE15022 for ; Tue, 21 Dec 1999 08:25:54 -0800 (PST) (envelope-from hometeam@techpower.net) Received: from localhost (hometeam@localhost) by techpower.net (8.9.3/8.9.3) with ESMTP id LAA00542; Tue, 21 Dec 1999 11:29:11 GMT (envelope-from hometeam@techpower.net) Date: Tue, 21 Dec 1999 11:29:11 +0000 (GMT) From: hometeam To: Broderick Wood Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.4 Release CD In-Reply-To: <199912211614.JAA67999@mark.kingsu.ab.ca> 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 noticed this also this morning and got an answer. As mentioned in questions there is a problem with the 3.4R till this is fixed the file will remain permissioned this way. There is another site if you must have the install it is barbones though, which I perfer. The site: ftp7.de.freebsd.org On Tue, 21 Dec 1999, Broderick Wood wrote: > > > > > > [ On Monday, December 20, Darcy Buskermolen wrote: ] > > > When trying to downaload the 3.4R cd, form the IOS-Images dir, I get > > > a permission denyed. is this because the file is still being > > > uploaded, or is it becasue the file mis chmod'd > > > > > I noticed the exact same thing and already mailed something off to > > -questions about it (and jkh). > > > Noticd this as well. When you FTP though, it gives you a different e- > mail to address FTP problems to. I sent a message off to that address > as well. We just need to be patient now I guess. > > > > --------------------------- > -BMW- > > To soar like an eagle, > fly like a dove. > > (bwood@kingsu.ab.ca) > Broderick Wood, > Director of Information Technology Services > The King's University College > 9125 - 50 Street > Edmonton, Alberta > T6B 2H3 > (780) 465-8315 > (780) 465-3534 (FAX) > > ><> <>< > > > 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 Tue Dec 21 8:40:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 894FF15040 for ; Tue, 21 Dec 1999 08:40:26 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id RAA02499 for freebsd-stable@FreeBSD.ORG; Tue, 21 Dec 1999 17:40:25 +0100 (CET) (envelope-from olli) Date: Tue, 21 Dec 1999 17:40:25 +0100 (CET) From: Oliver Fromme Message-Id: <199912211640.RAA02499@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: SOFTUPDATES Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG chris wrote in list.freebsd-stable: > On Tue, 21 Dec 1999, Michel TALON wrote: > > To enable softupdates on / is very simple: boot -s at the loader prompt > > and do > > > > tunefs -n enable / > > > > It is my understanding that if you forget to enable softupdates in > > kernel conf the flag is simply not recognized and causes no trouble. That's correct. > actually, you can't enable it on a mounted disk, you must boot off of the > kern and mfsroot floppies That's not correct. It is enough if the filesystem is mounted read-only. For the root filesystem, the easiest way to accomplish that is to boot to single-user mode, as Michel Talon wrote. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 9: 0:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 964CB153EF for ; Tue, 21 Dec 1999 09:00:39 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id JAA33478; Tue, 21 Dec 1999 09:00:37 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Dec 1999 09:00:37 -0800 (PST) From: Doug White To: tsikora@powerusersbbs.com Cc: FreeBSD Stable Subject: Re: SOFTUPDATES In-Reply-To: <385EFAEF.5F286795@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 Mon, 20 Dec 1999, Ted Sikora wrote: > Is anyone running the SOFTUPDATES option with Stable? I just enabled it > and was wondering if there are any issues I should be aware of > performance wise. Any problems? I enabled it for the /usr > filesystem. Any reason why / is not specifically recommended? One other data point. Softupdates can cause some interesting deadlocks when a disk fills up. Since /tmp is very susceptable to filling, you don't want softupdates set on the /tmp volume either (which is generally /). Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 9: 5:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 13E6E15382 for ; Tue, 21 Dec 1999 09:05:43 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.9.3/8.9.3) with ESMTP id JAA35453; Tue, 21 Dec 1999 09:05:39 -0800 (PST) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 21 Dec 1999 09:05:39 -0800 (PST) From: Doug White To: Michael Robinson Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Extremely bizarre filename behavior (3.3-RELEASE) In-Reply-To: <199912211316.VAA50647@netrinsics.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 Tue, 21 Dec 1999, Michael Robinson wrote: > I wrote: > >This filesystem passes fsck without a peep. Is it possible that the vast > >number of long, random filenames is causing lossage in the filename > >hashing? The system is 3.3-RELEASE. I'm going to upgrade to 3.4-RELEASE > >tonight to see if the problems persist. > > Ok, I'm an idiot. Terminating spaces were leaking in from Windows users > through Samba. It never occurred to me that sending filenames through > a pipe from "find" to "xargs" (how I discovered the problem) will strip > whitespace from filenames. find -print0 | xargs -0 is your friend. Doug White | FreeBSD: The Power to Serve dwhite@resnet.uoregon.edu | www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 9:13:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from shiva.jussieu.fr (shiva.jussieu.fr [134.157.0.129]) by hub.freebsd.org (Postfix) with ESMTP id DE5381534E for ; Tue, 21 Dec 1999 09:13:32 -0800 (PST) (envelope-from talon@lpthe.jussieu.fr) Received: from parthe.lpthe.jussieu.fr (parthe.lpthe.jussieu.fr [134.157.10.1]) by shiva.jussieu.fr (8.9.3/jtpda-5.3.2) with ESMTP id SAA77888 for ; Tue, 21 Dec 1999 18:13:31 +0100 (CET) Received: from niobe.lpthe.jussieu.fr (niobe.lpthe.jussieu.fr [134.157.10.41]) by parthe.lpthe.jussieu.fr (8.9.1a/jtpda-5.3.1) with ESMTP id SAA14843 for ; Tue, 21 Dec 1999 18:13:31 +0100 (MET) Received: from (talon@localhost) by niobe.lpthe.jussieu.fr (8.9.3/jtpda-5.3.1) id SAA84300 for freebsd-stable@FreeBSD.ORG; Tue, 21 Dec 1999 18:13:31 +0100 (CET) Date: Tue, 21 Dec 1999 18:13:31 +0100 From: Michel TALON To: FreeBSD Stable Subject: Re: SOFTUPDATES Message-ID: <19991221181331.B84264@lpthe.jussieu.fr> Mail-Followup-To: FreeBSD Stable References: <385EFAEF.5F286795@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dwhite@resnet.uoregon.edu on Tue, Dec 21, 1999 at 09:00:37AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Softupdates can cause some interesting deadlocks when a disk fills up. > Since /tmp is very susceptable to filling, you don't want softupdates set > on the /tmp volume either (which is generally /). > Here on my desktop i have /tmp mounted with softupdates. /dev/da0s1e on /tmp (local, soft-updates, writes: sync 97 async 14767) I frequently fill up /tmp, for example printing big acroread files, and i have never seen any deadlock since more than 1 year. On my laptop, to avoid any such problem i have installed everything flat under /, so i have 1 Gig free. In this setup softupdates is a big win. -- Michel TALON To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 9:16:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by hub.freebsd.org (Postfix) with ESMTP id 295FD14D0B for ; Tue, 21 Dec 1999 09:16:30 -0800 (PST) (envelope-from adamo@dblab.ece.ntua.gr) Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id TAA74707 for ; Tue, 21 Dec 1999 19:16:23 +0200 (EET) Received: (from george@localhost) by dblab.ece.ntua.gr (8.10.0.Beta10/8.10.0.Beta10) id dBLHGtB50245 for freebsd-stable@freebsd.org; Tue, 21 Dec 1999 19:16:55 +0200 (EET) Date: Tue, 21 Dec 1999 19:16:55 +0200 From: Yiorgos Adamopoulos To: freebsd-stable@freebsd.org Subject: laptop + keyboard problem Message-ID: <19991221191655.A38470@dblab.ece.ntua.gr> Reply-To: adamo@dblab.ece.ntua.gr Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-URL: http://home.eu.org/~adamo Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, I have a problem installing FreeBSD on my Fujitsu 585Tx laptop. I used both the 3.3-RELEASE and 3.3-STABLE-19991216.iso CDROMs and I am getting "keyboard not found" when booting. The strange thing is that Immunix (RH5.2 with StackGuard) and Slackware v7 install.iso image install just fine on the same machine. And I cannot immagine why RH5.2 (which is old enough) finds the keyboard and my favourite OS does not. -- There is no such thing as silly questions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 9:38:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f22.law4.hotmail.com [216.33.149.22]) by hub.freebsd.org (Postfix) with SMTP id 562DB14C45 for ; Tue, 21 Dec 1999 09:38:48 -0800 (PST) (envelope-from binkieboi@hotmail.com) Received: (qmail 89287 invoked by uid 0); 21 Dec 1999 17:38:48 -0000 Message-ID: <19991221173848.89286.qmail@hotmail.com> Received: from 12.10.140.2 by www.hotmail.com with HTTP; Tue, 21 Dec 1999 09:38:48 PST X-Originating-IP: [12.10.140.2] From: "Adidas Boy" To: freebsd-stable@freebsd.org Subject: 3.3-STABLE Question Date: Tue, 21 Dec 1999 10:38:48 MST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am thinking about upgrading my FreeBSD 3.3-RELEASE machine which i'm going to turn into a firewall to the 3.3-STABLE. I have decided that I want to use the program IP Filter with the firewall for the packet filtering and I heard from somewhere that 3.3-STABLE comes already with IP Filter precompiled with the OS? I just need to know if this is true or not? Brian ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.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 21 9:39:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id E940814A17 for ; Tue, 21 Dec 1999 09:39:56 -0800 (PST) (envelope-from cshumway@cdrom.com) Received: from localhost (cshumway@localhost) by pike.cdrom.com (8.9.1a/8.9.1) with ESMTP id JAA06867; Tue, 21 Dec 1999 09:39:54 -0800 (PST) Date: Tue, 21 Dec 1999 09:39:54 -0800 (PST) From: Christopher Shumway To: Yiorgos Adamopoulos Cc: freebsd-stable@FreeBSD.ORG Subject: Re: laptop + keyboard problem In-Reply-To: <19991221191655.A38470@dblab.ece.ntua.gr> 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 Tue, 21 Dec 1999, Yiorgos Adamopoulos wrote: > Hello all, > > I have a problem installing FreeBSD on my Fujitsu 585Tx laptop. I used both > the 3.3-RELEASE and 3.3-STABLE-19991216.iso CDROMs and I am getting "keyboard > not found" when booting. Your keyboard contoller is probably not truely AT compatable. I have made a FreeBSD 3.3-R kern.flp image that disables the keyboard proble, which will let you install the system. You can download it at ftp://ftp.cdrom.com/pub/4cust/kern.flp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 9:40:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 51685154B7 for ; Tue, 21 Dec 1999 09:40:27 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id D252CE89D; Tue, 21 Dec 1999 12:40:24 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id MAA08877; Tue, 21 Dec 1999 12:40:24 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14431.48008.578831.713503@onceler.kcilink.com> Date: Tue, 21 Dec 1999 12:40:24 -0500 (EST) To: Darcy Buskermolen Cc: freebsd-stable@FreeBSD.ORG Subject: Re: kde & top In-Reply-To: <3.0.32.19991220162448.009c6d30@mail.ok-connect.com> References: <3.0.32.19991220162448.009c6d30@mail.ok-connect.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "DB" == Darcy Buskermolen writes: DB> I've just noticed something interesting. DB> If I start KDE on my workstation, I loose the processor states ie: DB> CPU states: 0.0% user, 0.0% nice, 0.0% system, 0.0% interrupt, 0.0% idle Doesn't happen to me, running 3.4-RELEASE from cvsup as of yesterday. I'm using KDE 1.1.2 from the package. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 9:45:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 681C31548D for ; Tue, 21 Dec 1999 09:45:38 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id E0E18E8A6; Tue, 21 Dec 1999 12:45:37 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id MAA08915; Tue, 21 Dec 1999 12:45:37 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14431.48321.808884.135102@onceler.kcilink.com> Date: Tue, 21 Dec 1999 12:45:37 -0500 (EST) To: tsikora@powerusersbbs.com Cc: FreeBSD Stable Subject: Re: SOFTUPDATES In-Reply-To: <385EFAEF.5F286795@home.com> References: <385EFAEF.5F286795@home.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "TS" == Ted Sikora writes: TS> Is anyone running the SOFTUPDATES option with Stable? I just enabled it TS> and was wondering if there are any issues I should be aware of TS> performance wise. Any problems? I enabled it for the /usr TS> filesystem. Any reason why / is not specifically recommended? I've been running it for about 2 weeks now with no ill effects. The only thing that caught me was that the delay between deleting a file and the blocks being released was much larger than I had grown accustomed to on BSD/OS which also has soft updates. I don't know if it is implementation or the fact that this machine in question has IDE instead of SCSI. I have it enabled on *all* my partitions. Quite useful in / since that's where /tmp is, unless you have an MFS /tmp... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 9:52: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by hub.freebsd.org (Postfix) with ESMTP id EF9FD14C45 for ; Tue, 21 Dec 1999 09:52:01 -0800 (PST) (envelope-from adamo@dblab.ece.ntua.gr) Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id TAA76361; Tue, 21 Dec 1999 19:52:00 +0200 (EET) Received: (from george@localhost) by dblab.ece.ntua.gr (8.10.0.Beta10/8.10.0.Beta10) id dBLHqXs16148; Tue, 21 Dec 1999 19:52:33 +0200 (EET) Date: Tue, 21 Dec 1999 19:52:33 +0200 From: Yiorgos Adamopoulos To: Christopher Shumway Cc: Yiorgos Adamopoulos , freebsd-stable@FreeBSD.ORG Subject: Re: laptop + keyboard problem Message-ID: <19991221195233.A7670@dblab.ece.ntua.gr> Reply-To: adamo@dblab.ece.ntua.gr References: <19991221191655.A38470@dblab.ece.ntua.gr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from cshumway@cdrom.com on Tue, Dec 21, 1999 at 09:39:54AM -0800 X-URL: http://home.eu.org/~adamo Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 21, 1999 at 09:39:54AM -0800, Christopher Shumway wrote: > Your keyboard contoller is probably not truely AT compatable. I have made > a FreeBSD 3.3-R kern.flp image that disables the keyboard proble, which > will let you install the system. You can download it at > ftp://ftp.cdrom.com/pub/4cust/kern.flp Thanks! One more Q: I assume that if I plug an external keyboard, it will install. After that, will the installed system boot OK? I am asking because I cannot have both the CD ROM and the floppy plugged on the laptop... -- There is no such thing as silly questions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 9:54:37 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zgia.zp.ua (Eagle.ZGIA.zp.ua [194.183.182.2]) by hub.freebsd.org (Postfix) with ESMTP id 2605C152E8 for ; Tue, 21 Dec 1999 09:54:24 -0800 (PST) (envelope-from laa@zgia.zp.ua) Received: from localhost (laa@localhost) by zgia.zp.ua (8.9.3/8.9.3) with ESMTP id TAA23899; Tue, 21 Dec 1999 19:53:48 +0200 (EET) Date: Tue, 21 Dec 1999 19:53:48 +0200 (EET) From: Alexandr Listopad To: Adidas Boy Cc: freebsd-stable@FreeBSD.ORG Subject: Re: 3.3-STABLE Question In-Reply-To: <19991221173848.89286.qmail@hotmail.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 binkie> binkie>I am thinking about upgrading my FreeBSD 3.3-RELEASE machine which i'm going binkie>to turn into a firewall to the 3.3-STABLE. I have decided that I want to use binkie>the program IP Filter with the firewall for the packet filtering and I heard binkie>from somewhere that 3.3-STABLE comes already with IP Filter precompiled with binkie>the OS? I just need to know if this is true or not? binkie> binkie>Brian heh! yes... ipfw and ipf But you need to enable IP-Firewall support in your NEW kernel: options IPFIREWALL #firewall or like this: options IPFILTER #kernel ipfilter support see /usr/src/sys/i386/conf/LINT Good Luck! Regards, Listopad Alexandr (laa@zgia.zp.ua), LAA7-RIPE ZGIA, Zaporozhye, Ukraine. http://www.zgia.zp.ua. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 9:59:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pike.cdrom.com (pike.cdrom.com [204.216.28.222]) by hub.freebsd.org (Postfix) with ESMTP id 2CD2314BF3 for ; Tue, 21 Dec 1999 09:59:40 -0800 (PST) (envelope-from cshumway@cdrom.com) Received: from localhost (cshumway@localhost) by pike.cdrom.com (8.9.1a/8.9.1) with ESMTP id JAA07179; Tue, 21 Dec 1999 09:59:43 -0800 (PST) Date: Tue, 21 Dec 1999 09:59:42 -0800 (PST) From: Christopher Shumway To: Yiorgos Adamopoulos Cc: freebsd-stable@FreeBSD.ORG Subject: Re: laptop + keyboard problem In-Reply-To: <19991221195233.A7670@dblab.ece.ntua.gr> 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 Tue, 21 Dec 1999, Yiorgos Adamopoulos wrote: > On Tue, Dec 21, 1999 at 09:39:54AM -0800, Christopher Shumway wrote: > > Your keyboard contoller is probably not truely AT compatable. I have made > > a FreeBSD 3.3-R kern.flp image that disables the keyboard probe, which > > will let you install the system. You can download it at > > ftp://ftp.cdrom.com/pub/4cust/kern.flp > > Thanks! > > One more Q: > > I assume that if I plug an external keyboard, it will install. After that, > will the installed system boot OK? I am asking because I cannot have both the > CD ROM and the floppy plugged on the laptop... You will probably get the same results with an external keyboard since the keyboard controller is at fault. But I might be totally wrong, so its worth a try :) Once you have the system installed it won't probe for the keyboard anymore. Perhaps you can do a minimul from-msdos partition install just to get the system working, then install the rest with the cdrom attached? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10: 2:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hawaii.rr.com (hnlmail2.hawaii.rr.com [24.25.227.35]) by hub.freebsd.org (Postfix) with ESMTP id 4DBD4155B9 for ; Tue, 21 Dec 1999 10:02:40 -0800 (PST) (envelope-from art@hawaii.rr.com) Received: from taz ([24.31.76.79]) by hawaii.rr.com with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 21 Dec 1999 08:01:50 -1000 Message-Id: <3.0.6.32.19991221080219.008eb550@pop-server.hawaii.rr.com> X-Sender: art@pop-server.hawaii.rr.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 21 Dec 1999 08:02:19 -1000 To: chris , stable@freebsd.org From: "Art Neilson, WH7N" Subject: Re: SOFTUPDATES Cc: stable@freebsd.org In-Reply-To: References: <19991221155429.B83918@lpthe.jussieu.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, I did the same way Michel did, about 3-4 months ago. Worked fine for me I didn't have to boot off any special diskette or anything, just boot into single and tunefs the root filesystem. root@pilikia# mount /dev/wd0s1a on / (local, soft-updates, writes: sync 9 async 16218) /dev/wd0s1f on /usr (local, soft-updates, writes: sync 43 async 38046) /dev/wd0s1e on /var (local, soft-updates, writes: sync 282 async 18376) procfs on /proc (local) mfs:33 on /tmp (asynchronous, local, writes: sync 6 async 977) soft-updates is enabled on all the filesystems on my firewall box. At 09:21 AM 12/21/99 -0700, you wrote: >actually, you can't enable it on a mounted disk, you must boot off of the >kern and mfsroot floppies (and if you're without a net connection to >another machine, you'll need the fixit floppy (does it have tunefs on >it?)) > > -- chris > >On Tue, 21 Dec 1999, Michel TALON wrote: > >> To enable softupdates on / is very simple: boot -s at the loader prompt >> and do >> >> tunefs -n enable / >> >> It is my understanding that if you forget to enable softupdates in >> kernel conf the flag is simply not recognized and causes no trouble. >> >> Finally if you are on a rather small disk, for example on a laptop, >> the config which does not loose space and allows occasional big files >> in /tmp etc. is to put everything in / flatly. I have done that and >> never encountered any problem. >> >> -- >> >> Michel TALON >> >> >> >> 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 > -- __ / ) _/_ It is a capital mistake to theorise before one has data. /--/ __ / Insensibly one begins to twist facts to suit theories, / (_/ (_<__ Instead of theories to suit facts. -- Sherlock Holmes, "A Scandal in Bohemia" Arthur W. Neilson III, WH7N Bank of Hawaii Tech Support art@hawaii.rr.com, art@boh.com, ah6pz@arrl.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:11: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from klentaq.com (klentaq1.emergingtech.org [199.217.151.234]) by hub.freebsd.org (Postfix) with ESMTP id DEC1814E32 for ; Tue, 21 Dec 1999 10:11:04 -0800 (PST) (envelope-from stabilizer@klentaq.com) Received: (from stabilizer@localhost) by klentaq.com (8.9.3/8.9.2) id MAA87972; Tue, 21 Dec 1999 12:13:03 -0600 (CST) (envelope-from stabilizer) From: Wayne M Barnes Message-Id: <199912211813.MAA87972@klentaq.com> Subject: ISA internal modem (was PCI) In-Reply-To: <199912201722.KAA17015@harmony.village.org> from Warner Losh at "Dec 20, 1999 10:22:55 am" To: imp@village.org (Warner Losh) Date: Tue, 21 Dec 1999 12:13:03 -0600 (CST) Cc: freebsd-stable@freebsd.org (FreeBSD Stable) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Dear Stable, Okay, I got another modem. Couldn't find PCI as fast as ISA, so I got an ISA. Now my system can find sio2 and configure /dev/cuaa2. I tried to just take a baby step to try things out. I figured to run ppp manually to see if things are connecting at all. 'ppp' seems to start up ppp ON correctly ["Working in interactive mode"]. 'term' seems to have read my ppp.conf file, since it knows to connect to /dev/cuaa2. Now I try a simple 'AT' command to see if the modem can hear my typing. The echo of the modem seems to lag 1 character behind. That is, I only see the A after I type the T, and I only get the T after I hit Enter. Modem responds OK. More trouble: ATDT 5120027 This dials up my provider modem, but *Unless* I hit Enter, few characters come through. Error message: ... /kernel: sio2: 1 more silo overflow (total 1) Each time I hit enter, a few more characters come through, until login: I stop here to write for help, because this doesn't look ready for real communication. This is a FreeBSD 3.4-RC system. Wayne M Barnes stabilizer@klentaq.com > In message <199912201649.KAA85652@klentaq.com> Wayne M Barnes writes: > : How do I get my PCI modem card to work with FreeBSD 3.4? > > *IF* it isn't a win modem, soft modem, etc, then you can apply the > following patch, rebuild your kernel and create /dev/cua4, et al in > /dev. > > If it is a win modem, you lose. Sell it to some sucker and buy a real > pci modem. > > Patch: http://www.freebsd.org/~imp/Psio > > Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:28:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hawaii.rr.com (hnlmail2.hawaii.rr.com [24.25.227.35]) by hub.freebsd.org (Postfix) with ESMTP id A458914F19 for ; Tue, 21 Dec 1999 10:28:36 -0800 (PST) (envelope-from art@hawaii.rr.com) Received: from taz ([24.31.76.79]) by hawaii.rr.com with Microsoft SMTPSVC(5.5.1877.197.19); Tue, 21 Dec 1999 08:28:06 -1000 Message-Id: <3.0.6.32.19991221082835.008fc100@pop-server.hawaii.rr.com> X-Sender: art@pop-server.hawaii.rr.com X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Tue, 21 Dec 1999 08:28:35 -1000 To: Vivek Khera From: "Art Neilson, WH7N" Subject: Re: SOFTUPDATES Cc: stable@freebsd.org In-Reply-To: <14431.48321.808884.135102@onceler.kcilink.com> References: <385EFAEF.5F286795@home.com> <385EFAEF.5F286795@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:45 PM 12/21/99 -0500, you wrote: >>>>>> "TS" == Ted Sikora writes: > >I have it enabled on *all* my partitions. Quite useful in / since >that's where /tmp is, unless you have an MFS /tmp... Is there a reason to not have both softupdates on / and a mfs /tmp ? -- __ / ) _/_ It is a capital mistake to theorise before one has data. /--/ __ / Insensibly one begins to twist facts to suit theories, / (_/ (_<__ Instead of theories to suit facts. -- Sherlock Holmes, "A Scandal in Bohemia" Arthur W. Neilson III, WH7N Bank of Hawaii Tech Support art@hawaii.rr.com, art@boh.com, ah6pz@arrl.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:36:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from lcremeans.erols.com (lcremeans.erols.com [216.164.87.29]) by hub.freebsd.org (Postfix) with ESMTP id E77F314C45 for ; Tue, 21 Dec 1999 10:36:19 -0800 (PST) (envelope-from lee@lcremeans.erols.com) Received: (from lee@localhost) by lcremeans.erols.com (8.9.3/8.9.3) id NAA41195; Tue, 21 Dec 1999 13:36:07 -0500 (EST) (envelope-from lee) Date: Tue, 21 Dec 1999 13:36:07 -0500 From: Lee Cremeans To: Wayne M Barnes Cc: FreeBSD Stable Subject: Re: ISA internal modem (was PCI) Message-ID: <19991221133607.A41157@lcremeans.erols.com> References: <199912201722.KAA17015@harmony.village.org> <199912211813.MAA87972@klentaq.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912211813.MAA87972@klentaq.com>; from stabilizer@klentaq.com on Tue, Dec 21, 1999 at 12:13:03PM -0600 X-OS: FreeBSD 3.0-STABLE Organization: My room? Are you crazy? :) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 21, 1999 at 12:13:03PM -0600, Wayne M Barnes wrote: > Dear Stable, > > Okay, I got another modem. Couldn't find PCI as fast as ISA, > so I got an ISA. > > Now my system can find sio2 and configure /dev/cuaa2. > > I tried to just take a baby step to try things out. I figured > to run ppp manually to see if things are connecting at all. > 'ppp' seems to start up ppp ON correctly ["Working in interactive mode"]. > 'term' seems to have read my ppp.conf file, since it knows to connect > to /dev/cuaa2. > Now I try a simple 'AT' command to see if the modem can hear my typing. > > The echo of the modem seems to lag 1 character behind. That is, I only > see the A after I type the T, and I only get the T after I hit Enter. > Modem responds OK. > > More trouble: > ATDT 5120027 This dials up my provider modem, but > > *Unless* I hit Enter, few characters come through. > Error message: > ... /kernel: sio2: 1 more silo overflow (total 1) > > Each time I hit enter, a few more characters come through, until login: This sounds like it may be an IRQ conflict, at first glance. Is anything else trying to use that IRQ? If it has jumpers, use them and mark off the IRQ as used in the BIOS (this way, PnP won't try to map things on top of it). Also, does this modem have a Lucent DSP1673 on it, per chance? I have an ISA modem (an ActionTec) with one of those, and it will drop chraracters and give me tons of silo-overflow messages unless I throttle the line speed to 38400 (I get the feeling its 16550 emulation is broken; it's odd though because the modem behaves fine with Win95's COM drivers). -lee -- +--------------------------------------------------------------------+ | Lee Cremeans -- Manassas, VA, USA (WakkyMouse on WTnet) | | lcremeans@erols.com | http://wakky.dyndns.org/~lee | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:37:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from freeway.dcfinc.com (cx74889-a.phnx3.az.home.com [24.1.193.157]) by hub.freebsd.org (Postfix) with ESMTP id 0EE9914C45 for ; Tue, 21 Dec 1999 10:37:27 -0800 (PST) (envelope-from chad@freeway.dcfinc.com) Received: (from chad@localhost) by freeway.dcfinc.com (8.8.8/8.8.8) id LAA17976; Tue, 21 Dec 1999 11:37:17 -0700 (MST) (envelope-from chad) From: "Chad R. Larson" Message-Id: <199912211837.LAA17976@freeway.dcfinc.com> Subject: Re: ISA internal modem (was PCI) In-Reply-To: <199912211813.MAA87972@klentaq.com> from Wayne M Barnes at "Dec 21, 99 12:13:03 pm" To: stabilizer@klentaq.com (Wayne M Barnes) Date: Tue, 21 Dec 1999 11:37:17 -0700 (MST) Cc: imp@village.org, 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, Wayne M Barnes wrote: > Now I try a simple 'AT' command to see if the modem can hear my typing. > > The echo of the modem seems to lag 1 character behind. That is, I only > see the A after I type the T, and I only get the T after I hit Enter. > Modem responds OK. Last time I saw that, it was an interrupt misconfigure. The receive interrupt was pointed in the wrong place, so the received (echoed) character was not processed until the transmit interrupt (from the next character) was asserted. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? chad@dcfinc.com chad@larsons.org larson1@home.net DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:38:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tsolab.org (dnn.rockefeller.edu [129.85.40.126]) by hub.freebsd.org (Postfix) with ESMTP id B6F21154C2 for ; Tue, 21 Dec 1999 10:38:35 -0800 (PST) (envelope-from dan@tsolab.org) Received: from tsolab.org (ts027d36.hil-ny.concentric.net [206.173.24.96]) by tsolab.org (8.8.7/8.8.7) with SMTP id NAA24319; Tue, 21 Dec 1999 13:35:29 -0500 (EST) (envelope-from dan@tsolab.org) Message-ID: <385FCA45.5E780E37@tsolab.org> Date: Tue, 21 Dec 1999 13:43:17 -0500 From: Dan X-Mailer: Mozilla 4.51 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Wayne M Barnes Cc: FreeBSD Stable Subject: Re: ISA internal modem (was PCI) References: <199912211813.MAA87972@klentaq.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Probably an interrupt problem. You probably have the IRQ of the modem set to the same as COM1 or COM2. COM3 (/dev/cuaa2) is best set at IRQ 5. > Okay, I got another modem. Couldn't find PCI as fast as ISA, > so I got an ISA. > > Now my system can find sio2 and configure /dev/cuaa2. > > I tried to just take a baby step to try things out. I figured > to run ppp manually to see if things are connecting at all. > 'ppp' seems to start up ppp ON correctly ["Working in interactive mode"]. > 'term' seems to have read my ppp.conf file, since it knows to connect > to /dev/cuaa2. > Now I try a simple 'AT' command to see if the modem can hear my typing. > > The echo of the modem seems to lag 1 character behind. That is, I only > see the A after I type the T, and I only get the T after I hit Enter. > Modem responds OK. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:40:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 6EB2015519 for ; Tue, 21 Dec 1999 10:40:19 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id LAA16634; Tue, 21 Dec 1999 11:40:13 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id LAA25891; Tue, 21 Dec 1999 11:40:13 -0700 (MST) Message-Id: <199912211840.LAA25891@harmony.village.org> To: chad@DCFinc.com Subject: Re: ISA internal modem (was PCI) Cc: stabilizer@klentaq.com (Wayne M Barnes), freebsd-stable@FreeBSD.ORG In-reply-to: Your message of "Tue, 21 Dec 1999 11:37:17 MST." <199912211837.LAA17976@freeway.dcfinc.com> References: <199912211837.LAA17976@freeway.dcfinc.com> Date: Tue, 21 Dec 1999 11:40:13 -0700 From: Warner Losh Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199912211837.LAA17976@freeway.dcfinc.com> "Chad R. Larson" writes: : Last time I saw that, it was an interrupt misconfigure. The receive : interrupt was pointed in the wrong place, so the received (echoed) character : was not processed until the transmit interrupt (from the next : character) was asserted. And if this interrupt is from the network card, and this person is networked into the machine, hitting more characters would explain it. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:43:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id BD46715040 for ; Tue, 21 Dec 1999 10:43:40 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 08D68E8A5 for ; Tue, 21 Dec 1999 13:43:40 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id NAA30737; Tue, 21 Dec 1999 13:43:39 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14431.51803.933833.985122@onceler.kcilink.com> Date: Tue, 21 Dec 1999 13:43:39 -0500 (EST) To: freebsd-stable@freebsd.org Subject: three files in /usr/sbin not updated by make world X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday I cvsup'd and did a make world of the latest 3.4-STABLE. Three programs in /usr/sbin were not updated. This machine was initially installed a couple of weeks ago using the 3.3-RELEASE CD, and had make world done on it on December 9 as well. -r-xr-xr-x 1 root wheel 8703 Dec 9 13:23 named-bootconf* -r-xr-xr-x 2 root wheel 3148 Sep 16 18:48 ulaw2alaw* -r-xr-xr-x 2 root wheel 3148 Sep 16 18:48 alaw2ulaw* Everything else is properly dated as December 20. Where do these files come from? They're not in /usr/src/usr.sbin. Are these just old files that can go away? -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Vivek Khera, Ph.D. Khera Communications, Inc. Internet: khera@kciLink.com Rockville, MD +1-301-545-6996 PGP & MIME spoken here http://www.kciLink.com/home/khera/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:47:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ulysses.noc.ntua.gr (ulysses.noc.ntua.gr [147.102.222.230]) by hub.freebsd.org (Postfix) with ESMTP id 18AE715504 for ; Tue, 21 Dec 1999 10:47:13 -0800 (PST) (envelope-from adamo@dblab.ece.ntua.gr) Received: from dblab.ece.ntua.gr (ithaca.dbnet.ece.ntua.gr [147.102.12.1]) by ulysses.noc.ntua.gr (8.9.3/8.9.3) with ESMTP id UAA78848; Tue, 21 Dec 1999 20:47:10 +0200 (EET) Received: (from george@localhost) by dblab.ece.ntua.gr (8.10.0.Beta10/8.10.0.Beta10) id dBLIlho15804; Tue, 21 Dec 1999 20:47:43 +0200 (EET) Date: Tue, 21 Dec 1999 20:47:43 +0200 From: Yiorgos Adamopoulos To: Vivek Khera Cc: freebsd-stable@FreeBSD.ORG Subject: Re: three files in /usr/sbin not updated by make world Message-ID: <19991221204743.A12919@dblab.ece.ntua.gr> Reply-To: adamo@dblab.ece.ntua.gr References: <14431.51803.933833.985122@onceler.kcilink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14431.51803.933833.985122@onceler.kcilink.com>; from khera@kciLink.com on Tue, Dec 21, 1999 at 01:43:39PM -0500 X-URL: http://home.eu.org/~adamo Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 21, 1999 at 01:43:39PM -0500, Vivek Khera wrote: > -r-xr-xr-x 1 root wheel 8703 Dec 9 13:23 named-bootconf* At least this comes from building BIND. Maybe you've built it separately, or the guys responsible for the BIND installation on the base system chose not to install this. -- There is no such thing as silly questions To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:48:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id BFE4514DBB for ; Tue, 21 Dec 1999 10:48:15 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 339E4E8A4 for ; Tue, 21 Dec 1999 13:48:15 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id NAA30743; Tue, 21 Dec 1999 13:48:15 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14431.52079.94710.758347@onceler.kcilink.com> Date: Tue, 21 Dec 1999 13:48:15 -0500 (EST) To: freebsd-stable@freebsd.org Subject: handbook procedure for upgrading via cvsup confusion X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday, I went through the process of upgrading via cvsup to 3.4-STABLE on my 3.3-STABLE box. I had a couple of things confuse me. I picked up the hint to run 'mergemaster' from this list. The handbook doesn't mention this handy utility at all. It walks you through the long laborious process by hand. Wouldn't it be good to mention the existence of this wonderful tool right at the top of that section in the handbook? Secondly, the part about updating /stand... doing as the handbook suggests "make all install" in release/sysintall only updates the sysinstall program; it doesn't update all the hard links to it. Also, the file size is greatly reduced, leading me to believe that it is not a proper upgrade of that directory. What is the proper way to upgrade the /stand directory and the subdirectories within it (the help and TXT files)? Other than that, it went extremely smoothly, and there were no problems whatsoever in getting it up and running. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:54:44 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (castles550.castles.com [208.214.165.114]) by hub.freebsd.org (Postfix) with ESMTP id 8E2BD15500 for ; Tue, 21 Dec 1999 10:54:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA01031; Tue, 21 Dec 1999 10:58:38 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912211858.KAA01031@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gregory Sutter Cc: stable@FreeBSD.ORG Subject: Re: Don't use the "custom" install option for 3.4 In-reply-to: Your message of "Mon, 20 Dec 1999 23:42:50 PST." <19991220234250.O56510@azazel.zer0.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Dec 1999 10:58:38 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Mon, Dec 20, 1999 at 10:31:17PM -0800, Jordan K. Hubbard wrote: > > It's broken, sorry (I usually only test with "Novice" since so many > > more people use it). I'll add something to the errata, until then > > please use Novice or Express. I'm also sure that this is a completely > > Will the 3.4 CDs be pressed with this bug? Yes; we only just hit the this-year window last night with a few minutes to spare. I _did_ manage to work around the "can't boot on some ATAPI CDROMs" bug for CD #1, if that's any consolation. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 10:58:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B643515458 for ; Tue, 21 Dec 1999 10:58:08 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA05169; Tue, 21 Dec 1999 10:58:09 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Gregory Sutter Cc: stable@FreeBSD.ORG Subject: Re: Don't use the "custom" install option for 3.4 In-reply-to: Your message of "Mon, 20 Dec 1999 23:42:50 PST." <19991220234250.O56510@azazel.zer0.org> Date: Tue, 21 Dec 1999 10:58:09 -0800 Message-ID: <5165.945802689@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, there was a big rush with christmas this year or I would not have released at all. Ah well, it's not like it leaves one with no way to install FreeBSD at all. - Jordan > On Mon, Dec 20, 1999 at 10:31:17PM -0800, Jordan K. Hubbard wrote: > > It's broken, sorry (I usually only test with "Novice" since so many > > more people use it). I'll add something to the errata, until then > > please use Novice or Express. I'm also sure that this is a completely > > Will the 3.4 CDs be pressed with this bug? > > Greg > -- > Gregory S. Sutter The best way to accelerate Windows > mailto:gsutter@pobox.com is at 9.8 m/s^2. > http://www.pobox.com/~gsutter/ > PGP DSS public key 0x40AE3052 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 11: 7:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 583A414F19 for ; Tue, 21 Dec 1999 11:07:07 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA32004; Tue, 21 Dec 1999 19:13:49 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA02825; Tue, 21 Dec 1999 19:34:43 +0100 (CET) (envelope-from wilko) Date: Tue, 21 Dec 1999 19:34:43 +0100 From: Wilko Bulte To: Doug White Cc: tsikora@powerusersbbs.com, FreeBSD Stable Subject: Re: SOFTUPDATES Message-ID: <19991221193443.B2749@yedi.iaf.nl> References: <385EFAEF.5F286795@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from dwhite@resnet.uoregon.edu on Tue, Dec 21, 1999 at 09:00:37AM -0800 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 21, 1999 at 09:00:37AM -0800, Doug White wrote: > On Mon, 20 Dec 1999, Ted Sikora wrote: > > > Is anyone running the SOFTUPDATES option with Stable? I just enabled it > > and was wondering if there are any issues I should be aware of > > performance wise. Any problems? I enabled it for the /usr > > filesystem. Any reason why / is not specifically recommended? > > One other data point. > > Softupdates can cause some interesting deadlocks when a disk fills up. > Since /tmp is very susceptable to filling, you don't want softupdates set > on the /tmp volume either (which is generally /). Make that: 'which is generally, but really should not be, / ' -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 11:12:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp2.vnet.net (smtp2.vnet.net [166.82.1.32]) by hub.freebsd.org (Postfix) with ESMTP id EDB4D15498 for ; Tue, 21 Dec 1999 11:12:04 -0800 (PST) (envelope-from rivers@dignus.com) Received: from dignus.com (ponds.vnet.net [166.82.177.48]) by smtp2.vnet.net (8.9.1a/8.9.1) with ESMTP id OAA13900; Tue, 21 Dec 1999 14:10:44 -0500 (EST) Received: from lakes.dignus.com (lakes.dignus.com [10.0.0.3]) by dignus.com (8.9.2/8.8.5) with ESMTP id OAA30351; Tue, 21 Dec 1999 14:10:43 -0500 (EST) Received: (from rivers@localhost) by lakes.dignus.com (8.9.3/8.6.9) id OAA03708; Tue, 21 Dec 1999 14:10:43 -0500 (EST) Date: Tue, 21 Dec 1999 14:10:43 -0500 (EST) From: Thomas David Rivers Message-Id: <199912211910.OAA03708@lakes.dignus.com> To: gsutter@pobox.com, jkh@zippy.cdrom.com Subject: Re: Don't use the "custom" install option for 3.4 Cc: stable@FreeBSD.ORG In-Reply-To: <5165.945802689@zippy.cdrom.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jordan wrote: > > Yes, there was a big rush with christmas this year or I would > not have released at all. Ah well, it's not like it leaves one > with no way to install FreeBSD at all. Is it safe to assume some new floppies will be built, and made available, with this bug corrected? Then, a safe way to install 3.4 is to download the floppies, and _then_ use the CD-ROM distribution (which is how I tend to go anyway...) - Dave R. - To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 11:14:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 5B9EC154E4 for ; Tue, 21 Dec 1999 11:14:26 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA05324; Tue, 21 Dec 1999 11:14:18 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Thomas David Rivers Cc: gsutter@pobox.com, stable@FreeBSD.ORG Subject: Re: Don't use the "custom" install option for 3.4 In-reply-to: Your message of "Tue, 21 Dec 1999 14:10:43 EST." <199912211910.OAA03708@lakes.dignus.com> Date: Tue, 21 Dec 1999 11:14:18 -0800 Message-ID: <5320.945803658@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I wouldn't assume anything, but I'll certainly TRY to fix this and roll some updated floppies. :) - Jordan > Jordan wrote: > > > > Yes, there was a big rush with christmas this year or I would > > not have released at all. Ah well, it's not like it leaves one > > with no way to install FreeBSD at all. > > Is it safe to assume some new floppies will be built, and made available, > with this bug corrected? Then, a safe way to install 3.4 is to download > the floppies, and _then_ use the CD-ROM distribution (which is how I tend to > go anyway...) > > - Dave R. - > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 11:23:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from home.com (c97217-a.plstn1.sfba.home.com [24.1.83.85]) by hub.freebsd.org (Postfix) with ESMTP id 5F0D814DDE for ; Tue, 21 Dec 1999 11:23:40 -0800 (PST) (envelope-from jerry@home.com) Received: (from jerry@localhost) by home.com (8.9.3/8.9.3) id LAA22359; Tue, 21 Dec 1999 11:23:37 -0800 (PST) (envelope-from jerry) Date: Tue, 21 Dec 1999 11:23:36 -0800 From: Jerry Gardner To: tsikora@powerusersbbs.com Cc: freebsd-stable@FreeBSD.ORG Subject: Re: SOFTUPDATES Message-ID: <19991221112336.A22081@home.com> References: <385EFAEF.5F286795@home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <385EFAEF.5F286795@home.com>; from tsikora@home.com on Mon, Dec 20, 1999 at 10:58:39PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 10:58:39PM -0500, Ted Sikora wrote: > Is anyone running the SOFTUPDATES option with Stable? I just enabled it > and was wondering if there are any issues I should be aware of > performance wise. Any problems? I enabled it for the /usr > filesystem. Any reason why / is not specifically recommended? Ted, I have been using softupdates with -STABLE now for quite some time with absolutely no problems. There have been problems reported with the softupdates code if the filesystem is full, or close to full. Kirk McKusick is working on the problem, but if you don't run with full filesystems, you will be OK. -- Jerry Gardner | "Bill Clinton has all the steely resolve w6uv@home.com | of a kamakaze pilot on his 37th mission." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 11:40:55 1999 Delivered-To: freebsd-stable@freebsd.org Received: from evil.2y.net (port-4-114.adsl.one.net [216.2.1.114]) by hub.freebsd.org (Postfix) with ESMTP id 9DA9015498 for ; Tue, 21 Dec 1999 11:40:51 -0800 (PST) (envelope-from cokane@evil.2y.net) Received: (from cokane@localhost) by evil.2y.net (8.9.3/8.9.3) id OAA09530 for freebsd-stable@freebsd.org; Tue, 21 Dec 1999 14:43:17 -0500 (EST) (envelope-from cokane) Date: Tue, 21 Dec 1999 14:43:17 -0500 From: Coleman Kane To: freebsd-stable@freebsd.org Subject: Re: AMD 3DNow instructions on FreeBSD Message-ID: <19991221144317.A9514@evil.2y.net> References: <19991219180557.A58177@ipass.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991219180557.A58177@ipass.net>; from aa8vb@ipass.net on Sun, Dec 19, 1999 at 06:05:57PM -0500 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yes, if you compile the PGCC from the ports, or packages (in ports/lang) it has support for 3dnow. --cokane Randall Hopper had the audacity to say: > > Hi. Is there a FreeBSD assembler out there which supports the AMD 3DNow > instruction set? > > Why I ask: I attempted to build GLX/Mesa3.1 with 3DNow support, and it > bombed since our assembler isn't 3DNow-knowledgable (femms, pfmul, > etc. undefined). The assembler in -stable has the same shortcoming AFAICT. > > Facts? Rumors? I'm interested in anything you may know. > > Thanks, > > Randall > > > 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 Tue Dec 21 11:42: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 7D722154C0 for ; Tue, 21 Dec 1999 11:42:04 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991221194203.HICQ9446.mail.rdc1.ct.home.com@home.com> for ; Tue, 21 Dec 1999 11:42:03 -0800 Message-ID: <385FD807.72FC177D@home.com> Date: Tue, 21 Dec 1999 14:41:59 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: SOFTUPDATES References: <385EFAEF.5F286795@home.com> <19991221112336.A22081@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jerry Gardner wrote: > > On Mon, Dec 20, 1999 at 10:58:39PM -0500, Ted Sikora wrote: > > Is anyone running the SOFTUPDATES option with Stable? I just enabled it > > and was wondering if there are any issues I should be aware of > > performance wise. Any problems? I enabled it for the /usr > > filesystem. Any reason why / is not specifically recommended? > > Ted, > > I have been using softupdates with -STABLE now for quite some time > with absolutely no problems. > > There have been problems reported with the softupdates code if the > filesystem is full, or close to full. Kirk McKusick is working on the > problem, but if you don't run with full filesystems, you will be OK. > Thanks guys you helped tremendously. There's no reason not to use it now. We'll get that penquin yet. That's my only complaint really ...the slow filesystem but again data security is more enticing. So from what I read softupdates on /tmp will also speed things up quite a bit and / is not really necassary. Problem is my /tmp is on / so in the future it may be wise to make a /tmp directory. How about linking /tmp to /usr or /var for my current setup? Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.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 21 11:44: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id B126914FC9 for ; Tue, 21 Dec 1999 11:43:56 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id dBLJhi821258; Tue, 21 Dec 1999 14:43:45 -0500 (EST) Date: Tue, 21 Dec 1999 14:43:44 -0500 (EST) From: jack To: "Jordan K. Hubbard" Cc: stable@FreeBSD.ORG Subject: Re: Don't use the "custom" install option for 3.4 In-Reply-To: <5320.945803658@zippy.cdrom.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 Today Jordan K. Hubbard wrote: > I wouldn't assume anything, but I'll certainly TRY to > fix this and roll some updated floppies. :) A release rolled from CVSup of the morning of the 17th works, one from the 20th dies. I haven't had time to narrow it down any farther. -------------------------------------------------------------------------- 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 Tue Dec 21 11:54:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id D492B154C0 for ; Tue, 21 Dec 1999 11:54:34 -0800 (PST) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn2215.bossig.com [208.26.242.215]) by corinth.bossig.com (Rockliffe SMTPRA 3.4.5) with ESMTP id ; Tue, 21 Dec 1999 12:01:09 -0800 Message-ID: <385FDB0D.D5C9328@3-cities.com> Date: Tue, 21 Dec 1999 11:54:53 -0800 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Adidas Boy Cc: freebsd-stable@freebsd.org Subject: Re: 3.3-STABLE Question References: <19991221173848.89286.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Adidas Boy wrote: > > I am thinking about upgrading my FreeBSD 3.3-RELEASE machine which i'm going > to turn into a firewall to the 3.3-STABLE. I have decided that I want to use > the program IP Filter with the firewall for the packet filtering and I heard > from somewhere that 3.3-STABLE comes already with IP Filter precompiled with > the OS? I just need to know if this is true or not? Just remember that if you cvsup to RELENG_3, you are going to get 3.4-Stable. Kent > > Brian > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 11:55:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gemini.inside.pathcom.com (chihuahua.pathcom.com [209.250.128.11]) by hub.freebsd.org (Postfix) with ESMTP id 6F5BF154D7 for ; Tue, 21 Dec 1999 11:55:49 -0800 (PST) (envelope-from drkangel@gemini.inside.pathcom.com) Received: from localhost (drkangel@localhost) by gemini.inside.pathcom.com (8.9.1/8.9.1) with ESMTP id OAA22343 for ; Tue, 21 Dec 1999 14:55:53 -0500 Date: Tue, 21 Dec 1999 14:55:53 -0500 (EST) From: Marco Paulo Rodrigues To: stable@freebsd.org Subject: PPPoE 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 know this seem like a repetative question, but is there going to be any PPPoE kervel level support for FreeBSD any time soon? Or is there already.. if not is there a package someone can recommend to use temporarily with FreeBSD 3.3 Stable. Thanx! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 11:58:36 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 54BB4154C0 for ; Tue, 21 Dec 1999 11:58:33 -0800 (PST) (envelope-from mike@sentex.net) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id OAA31517; Tue, 21 Dec 1999 14:58:26 -0500 (EST) (envelope-from mike@sentex.net) Message-Id: <3.0.5.32.19991221145607.01efb100@staff.sentex.ca> X-Sender: mdtpop@staff.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Tue, 21 Dec 1999 14:56:07 -0500 To: Marco Paulo Rodrigues , stable@FreeBSD.ORG From: Mike Tancsa Subject: Re: PPPoE In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 02:55 PM 12/21/99 -0500, Marco Paulo Rodrigues wrote: > I know this seem like a repetative question, but is there going to >be any PPPoE kervel level support for FreeBSD any time soon? Or is there >already.. if not is there a package someone can recommend to use >temporarily with FreeBSD 3.3 Stable. Thanx! As was mentioned here, PPPoE was added to STABLE a few weeks ago. If you cvsup to the latest STABLE, you will have it. ---Mike ------------------------------------------------------------------------ Mike Tancsa, tel +1 519 651 3400 Network Administrator, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 12:17: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.gmx.net (mail2.gmx.net [194.221.183.62]) by hub.freebsd.org (Postfix) with SMTP id 802D515511 for ; Tue, 21 Dec 1999 12:17:00 -0800 (PST) (envelope-from Gerhard.Sittig@gmx.net) Received: (qmail 28031 invoked by uid 0); 21 Dec 1999 20:16:51 -0000 Received: from p3e9e7a7f.dip.t-dialin.net (HELO speedy.gsinet) (62.158.122.127) by mail2.gmx.net with SMTP; 21 Dec 1999 20:16:51 -0000 Received: (from sittig@localhost) by speedy.gsinet (8.8.8/8.8.8) id PAA16745 for freebsd-stable@freebsd.org; Tue, 21 Dec 1999 15:43:04 +0100 Date: Tue, 21 Dec 1999 15:43:03 +0100 From: Gerhard Sittig To: freebsd-stable@freebsd.org Subject: Re: Extremely bizarre filename behavior (3.3-RELEASE) Message-ID: <19991221154303.B15372@speedy.gsinet> Mail-Followup-To: freebsd-stable@freebsd.org References: <199912211002.SAA50337@netrinsics.com> <199912211316.VAA50647@netrinsics.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912211316.VAA50647@netrinsics.com>; from robinson@netrinsics.com on Tue, Dec 21, 1999 at 09:16:14PM +0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 21, 1999 at 21:16 +0800, Michael Robinson wrote: > > Terminating spaces were leaking in from Windows users through > Samba. It never occurred to me that sending filenames through > a pipe from "find" to "xargs" (how I discovered the problem) > will strip whitespace from filenames. It seems good habit (unless someone can explain me otherwise :) to do something like find $DIRS $OPTS -print0 | xargs --null $CMD which helps against this sort of thing. virtually yours - Gerhard Sittig -- mail -s "get pgp key" Gerhard.Sittig@gmx.net < /dev/null If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 12:30:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 10BAC15526 for ; Tue, 21 Dec 1999 12:30:08 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id UAA65648; Tue, 21 Dec 1999 20:29:57 GMT (envelope-from joe) Date: Tue, 21 Dec 1999 20:29:56 +0000 From: Josef Karthauser To: Marco Paulo Rodrigues Cc: stable@FreeBSD.ORG Subject: Re: PPPoE Message-ID: <19991221202956.E48740@florence.pavilion.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: X-NCC-RegID: uk.pavilion Organisation: Pavilion Internet plc, Lees House, 21-23 Dyke Road, Brighton, England Phone: +44-845-333-5000 Fax: +44-845-333-5001 Mobile: +44-403-596893 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 21, 1999 at 02:55:53PM -0500, Marco Paulo Rodrigues wrote: > I know this seem like a repetative question, but is there going to > be any PPPoE kervel level support for FreeBSD any time soon? Or is there > already.. if not is there a package someone can recommend to use > temporarily with FreeBSD 3.3 Stable. Thanx! 3.4 has shipped with it - Brian worked his butt off to make it so, he deserves a big cream cake. Joe -- Josef Karthauser FreeBSD: How many times have you booted today? Technical Manager Viagra for your server (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@uk.freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 12:39:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 9421114FF2 for ; Tue, 21 Dec 1999 12:39:28 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40333>; Wed, 22 Dec 1999 07:30:27 +1100 Content-return: prohibited Date: Wed, 22 Dec 1999 07:39:11 +1100 From: Peter Jeremy Subject: Re: SOFTUPDATES In-reply-to: <385FD807.72FC177D@home.com>; from tsikora@home.com on Wed, Dec 22, 1999 at 06:41:59AM +1100 To: tsikora@powerusersbbs.com Cc: freebsd-stable@FreeBSD.ORG Message-Id: <99Dec22.073027est.40333@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <385EFAEF.5F286795@home.com> <19991221112336.A22081@home.com> <385FD807.72FC177D@home.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-22 06:41:59 +1100, Ted Sikora wrote: > So from what I read softupdates on /tmp will also speed things >up quite a bit and / is not really necassary. Yes. >How about linking /tmp to /usr or /var for my current setup? Linking /tmp into /var is probably more reasonable than /usr (/ and /usr should both be `write-rarely' filesystems). Note that some Unices have exploits which rely on hard-links to system files, so it is good general practice not to allow world-writable directories in / or /usr. If you do this, it is probably a good idea to create the same directory in the root filesystem - so you have an accessible /tmp with only the root FS mounted (the extra directory will be hidden when /var is mounted). If you have sufficient RAM or swap, MFS is another option for /tmp. (And if /tmp is in a partition by itself, you should get marginally better performance by making it async instead of using softupdates). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 13:44:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from web505.mail.yahoo.com (web505.mail.yahoo.com [128.11.68.72]) by hub.freebsd.org (Postfix) with SMTP id C2A7915521 for ; Tue, 21 Dec 1999 13:44:55 -0800 (PST) (envelope-from god@yahoo.com) Received: (qmail 26510 invoked by uid 60001); 21 Dec 1999 21:44:55 -0000 Message-ID: <19991221214455.26509.qmail@web505.mail.yahoo.com> Received: from [208.224.169.134] by web505.mail.yahoo.com; Tue, 21 Dec 1999 13:44:55 PST Date: Tue, 21 Dec 1999 13:44:55 -0800 (PST) From: Mike s Subject: bugs in the handbook. To: stable@freebsd.org Cc: docs@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 All, Maybe, just maybe, It is time for a team of "motivated" and "skilled" web developers with FreeBSD expertise to crank out a new web site entirely for the new year ( err, for the new year to come :-) ), Including a new handbook. Of course not trash the current handbook. FreeBSD has evolved so fast but it seems the Documentation has been left in the dust. I'm game, But only if people are serious and not going to say i will help and vanish. i sent this to -stable as well as the doc team mailing list since i haven't heard a peep out of the list in awhile. maybe we start a FreeBSD Portal on FreeBSD.com and leave FreeBSD.org running the way it is now. Just a thought.. love you all. God God@yahoo.com i am not subscribed to the list so please send a copy to me, thanks. __________________________________________________ Do You Yahoo!? Thousands of Stores. Millions of Products. All in one place. Yahoo! Shopping: http://shopping.yahoo.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 21 14:24:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from fep01-svc.mail.telepac.pt (fep01-svc.mail.telepac.pt [194.65.5.200]) by hub.freebsd.org (Postfix) with ESMTP id 5648515090 for ; Tue, 21 Dec 1999 14:24:17 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: from manecao.tafkap.priv ([194.65.198.49]) by fep01-svc.mail.telepac.pt (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991221222011.ISRZ27728.fep01-svc@manecao.tafkap.priv> for ; Tue, 21 Dec 1999 22:20:11 +0000 Content-Length: 1118 Message-ID: X-Mailer: XFMail 1.3.1 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 21 Dec 1999 22:23:41 -0000 (GMT) From: Joao Pedras To: freebsd-stable@freebsd.org Subject: today's stable ? Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all! My -stable sup'ed this afternoon is giving me this in installworld : install -c -o root -g wheel -m 644 cvsup/www-supfile /usr/share/examples/cvsup/www-supfile install -c -o root -g wheel -m 644 diskless/209.157.86.12/README /usr/share/examples/diskless/209.157.86.12/README install: /usr/share/examples/diskless/209.157.86.12/README: No such file or directory *** Error code 71 Stop. *** Error code 1 Stop. *** Error code 1 Is it just me ? Thanks Joao ^\ /^ O O ----------------------------------------o00-(_)-00o-------------------------- Sent on 21-Dec-99 at 22:22:35 Powered by FreeBSD -> http://www.freebsd.org <- "The Power to Serve" More info @ http://www.freebsddiary.org/freebsd/ - http://www.daemonnews.org/ ----------------------------------------------------------------------------- PGP key available upon request or may be cut at http://pedras.webvolution.net/pgpkey.html ----------------------------------------------------------------------------- Never call a man a fool. Borrow from him. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 14:26:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from napalm.plano.sterling.com (napalm.plano.sterling.com [208.24.125.34]) by hub.freebsd.org (Postfix) with ESMTP id B9E7F15314 for ; Tue, 21 Dec 1999 14:26:16 -0800 (PST) (envelope-from alan.edmonds@sterling.com) Received: from sterling.com (CD27T.plano.sterling.com [10.1.54.234]) by napalm.plano.sterling.com (8.9.1b+Sun/8.9.1) with ESMTP id QAA12840; Tue, 21 Dec 1999 16:26:08 -0600 (CST) Message-ID: <385FFE80.22AC9399@sterling.com> Date: Tue, 21 Dec 1999 16:26:08 -0600 From: Alan Edmonds X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Joao Pedras Cc: freebsd-stable@FreeBSD.ORG Subject: Re: today's stable ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Me too....... :-( Joao Pedras wrote: > > Hello all! > > My -stable sup'ed this afternoon is giving me this in installworld : > > install -c -o root -g wheel -m 644 cvsup/www-supfile > /usr/share/examples/cvsup/www-supfile > install -c -o root -g wheel -m 644 diskless/209.157.86.12/README > /usr/share/examples/diskless/209.157.86.12/README > install: /usr/share/examples/diskless/209.157.86.12/README: No such file or > directory > *** Error code 71 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Is it just me ? > > Thanks > > Joao > > ^\ /^ > O O > ----------------------------------------o00-(_)-00o-------------------------- > Sent on 21-Dec-99 at 22:22:35 > Powered by FreeBSD -> http://www.freebsd.org <- "The Power to Serve" > More info @ http://www.freebsddiary.org/freebsd/ - http://www.daemonnews.org/ > ----------------------------------------------------------------------------- > PGP key available upon request or may be cut at > http://pedras.webvolution.net/pgpkey.html > ----------------------------------------------------------------------------- > Never call a man a fool. Borrow from him. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Alan Edmonds, KB5ZUY Sterling Software M/S 132 Phone: +1-972-801-6485 5800 Tennyson Pkwy. Email: alan.edmonds@sterling.com Plano, TX, USA 75024 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 14:31:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id EA86F14F20 for ; Tue, 21 Dec 1999 14:31:07 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991221223107.JHQB9446.mail.rdc1.ct.home.com@home.com> for ; Tue, 21 Dec 1999 14:31:07 -0800 Message-ID: <385FFFA7.B500A05A@home.com> Date: Tue, 21 Dec 1999 17:31:03 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: today's stable ? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Joao Pedras wrote: > > Hello all! > > My -stable sup'ed this afternoon is giving me this in installworld : > > install -c -o root -g wheel -m 644 cvsup/www-supfile > /usr/share/examples/cvsup/www-supfile > install -c -o root -g wheel -m 644 diskless/209.157.86.12/README > /usr/share/examples/diskless/209.157.86.12/README > install: /usr/share/examples/diskless/209.157.86.12/README: No such file or > directory > *** Error code 71 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Is it just me ? > > Thanks > > Joao > > ^\ /^ Same here! Just tried make installworld 2x. I'm cvs'ing now hoping it's been fixed. It went fine Sunday night on another machine but there's been some changes since then. -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.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 21 14:41: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 12B0F15573 for ; Tue, 21 Dec 1999 14:40:57 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id JAA25906; Wed, 22 Dec 1999 09:40:50 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id JAA01550; Wed, 22 Dec 1999 09:40:50 +1100 (EST) Message-Id: <199912212240.JAA01550@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: "Art Neilson, WH7N" Cc: chris , stable@FreeBSD.ORG Subject: Re: SOFTUPDATES In-reply-to: Your message of Tue, 21 Dec 1999 08:02:19 -1000. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Dec 1999 09:40:49 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, I did the same way Michel did, about 3-4 months ago. > Worked fine for me I didn't have to boot off any special > diskette or anything, just boot into single and tunefs the > root filesystem. To be fair to chris, the ability to enable softupdates on RO partitions is relatively new. To turn softupdates on for /, you _used_ to have to boot from a floppy/CD; nowadays boot -s is enough. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 14:48:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 578B915544 for ; Tue, 21 Dec 1999 14:48:51 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991221224850.JNCQ9446.mail.rdc1.ct.home.com@home.com> for ; Tue, 21 Dec 1999 14:48:50 -0800 Message-ID: <386003CF.D8C5FAB5@home.com> Date: Tue, 21 Dec 1999 17:48:47 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: today's stable fixed References: <385FFFA7.B500A05A@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora wrote: > > Joao Pedras wrote: > > > > Hello all! > > > > My -stable sup'ed this afternoon is giving me this in installworld : > > > > install -c -o root -g wheel -m 644 cvsup/www-supfile > > /usr/share/examples/cvsup/www-supfile > > install -c -o root -g wheel -m 644 diskless/209.157.86.12/README > > /usr/share/examples/diskless/209.157.86.12/README > > install: /usr/share/examples/diskless/209.157.86.12/README: No such file or > > directory > > *** Error code 71 > > > > Stop. > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Is it just me ? > > > > Thanks > > > > Joao > > > > ^\ /^ > > Same here! Just tried make installworld 2x. I'm cvs'ing now hoping it's > been fixed. It went fine Sunday night on another machine but there's > been some changes since then. I manually cp'ed /usr/src/share/examples/diskless/* to /usr/share/examples and install world finished up fine. A quick fix for now. -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.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 21 15:59:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 9014E1557B; Tue, 21 Dec 1999 15:59:09 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id RAA13666; Tue, 21 Dec 1999 17:57:52 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 21 Dec 1999 17:57:51 -0600 (CST) From: Chris Dillon To: Joe Greco Cc: install@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: 3.4R sysinstall blows up In-Reply-To: <199912210427.WAA34841@aurora.sol.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 Mon, 20 Dec 1999, Joe Greco wrote: > So I go to install 3.4R on a box. sysinstall blows spectacularly as I go > to select the distributions. [...snip...] > Is this just me, or is it an actual bug? I'm guessing its a legitimate bug, since I just encountered this exact same problem when a friend was trying to install 3.4. I told him to install the 3.3-19991207-STABLE snapshot I have on my ftp server and it worked fine. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) Your mouse has moved. Windows must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 17:49:59 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 19E1714E75 for ; Tue, 21 Dec 1999 17:49:53 -0800 (PST) (envelope-from dneild@HOME.COM) Received: from [24.112.99.250] by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991222014745.SKXZ7552.mail.rdc3.on.home.com@[24.112.99.250]>; Tue, 21 Dec 1999 17:47:45 -0800 User-Agent: Microsoft Outlook Express Macintosh Edition - 5.0 (1513) Date: Tue, 21 Dec 1999 20:49:50 -0500 Subject: Re: today's stable ? From: Dylan Neild To: Joao Pedras , Message-ID: In-Reply-To: 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 Hi Guys, If you: cd /usr/share/examples mkdir diskless cd diskless cp -r /usr/src/share/examples/diskless/* . cd /usr/src make installworld It'll work nicely. Dylan > From: Joao Pedras > Date: Tue, 21 Dec 1999 22:23:41 -0000 (GMT) > To: freebsd-stable@FreeBSD.ORG > Subject: today's stable ? > > Hello all! > > My -stable sup'ed this afternoon is giving me this in installworld : > > install -c -o root -g wheel -m 644 cvsup/www-supfile > /usr/share/examples/cvsup/www-supfile > install -c -o root -g wheel -m 644 diskless/209.157.86.12/README > /usr/share/examples/diskless/209.157.86.12/README > install: /usr/share/examples/diskless/209.157.86.12/README: No such file or > directory > *** Error code 71 > > Stop. > *** Error code 1 > > Stop. > *** Error code 1 > > Is it just me ? > > Thanks > > Joao > > > ^\ /^ > O O > ----------------------------------------o00-(_)-00o-------------------------- > Sent on 21-Dec-99 at 22:22:35 > Powered by FreeBSD -> http://www.freebsd.org <- "The Power to Serve" > More info @ http://www.freebsddiary.org/freebsd/ - http://www.daemonnews.org/ > ----------------------------------------------------------------------------- > PGP key available upon request or may be cut at > http://pedras.webvolution.net/pgpkey.html > ----------------------------------------------------------------------------- > Never call a man a fool. Borrow from him. > > > > 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 Tue Dec 21 18: 3: 9 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ares.cs.Virginia.EDU (ares.cs.Virginia.EDU [128.143.136.41]) by hub.freebsd.org (Postfix) with ESMTP id 3B6E11554E for ; Tue, 21 Dec 1999 18:02:53 -0800 (PST) (envelope-from vkb3q@cs.virginia.edu) Received: from cobra.cs.Virginia.EDU (cobra.cs.Virginia.EDU [128.143.137.16]) by ares.cs.Virginia.EDU (8.9.2/8.9.2/UVACS-1999030200) with ESMTP id VAA15984 for ; Tue, 21 Dec 1999 21:02:51 -0500 (EST) Received: from localhost (vkb3q@localhost) by cobra.cs.Virginia.EDU (8.9.2/8.9.2) with ESMTP id VAA20871 for ; Tue, 21 Dec 1999 21:02:51 -0500 (EST) X-Authentication-Warning: cobra.cs.Virginia.EDU: vkb3q owned process doing -bs Date: Tue, 21 Dec 1999 21:02:51 -0500 (EST) From: Vinod Balakrishnan To: freebsd-stable@FreeBSD.ORG Subject: de driver problems with ZNYX 21140A cards 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, I am working on a 6 pc test bed (FreeBSD boxes) having the 4 port 100Mbps 21140A Znyx cards. I am running FreeBSD 3.1-Release. I have also tested it on FreeBSD 3.0-Stable. I am facing a few problems with the device driver de. 1. netstat -I gives lots of output errors. Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll de3 1500 10.0.8/24 10.0.8.5 434417 0 290242 289158 0 If I use the device driver provided at the ZNYX website (znyx.com) zxe then I do not see any Oerrs. 2. ifconfig de3 mediaopt full-duplex , returns an error: ifconfig:SIOCSIFMEDIA: Device not configured 3. The throughput of a TCP flow from one FreeBSD box to another (each having a ZNYX card) varies with the packet size. For instance for a packet size of 150bytes I achieve 90Mbps. For packetsize of 500bytes it is only 60-70Mbps. 4. If I run a tcp flow from one FreeBSD box to another via an intermediate FreeBSD box (all having the ZNYX344 card and de device driver) I get a throughput of 40Mbps only for 500 byte packets. All of these above problems are not visible when I use the zxe device driver. thank you for your time, -Vinod *********************************************************************** B. Vinod Kumar Dept. of Computer Science, University of Virginia, Charlottesville Residence: 101, Carrollton Terrace, #2 Charlottesville, Va-22903 804-293-5101 ********************************************************************** To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 18: 9:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id 685AC14DE7 for ; Tue, 21 Dec 1999 18:09:25 -0800 (PST) (envelope-from williamsl@Home.Com) Received: from RELIABLE ([24.4.115.31]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991222020924.BTVT17996.mail.rdc1.tn.home.com@RELIABLE> for ; Tue, 21 Dec 1999 18:09:24 -0800 Date: Tue, 21 Dec 1999 21:08:34 -0500 From: Ben WIlliams X-Mailer: The Bat! (v1.34a) UNREG / CD5BF9353B3B7091 Reply-To: Ben WIlliams X-Priority: 3 (Normal) Message-ID: <9880.991221@Home.Com> To: freebsd-stable@FreeBSD.ORG Subject: Re[2]: SOFTUPDATES In-reply-To: <199912212240.JAA01550@lightning.itga.com.au> References: <199912212240.JAA01550@lightning.itga.com.au> 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 Tuesday, December 21, 1999 How far back is "used to"? I have a 3.2-RELEASE box that I tried booting into single-user mode both via `shutdown now` and 'boot -s' and couldn't get it to enable soft updates on /. When I did `shutdown now` it would complete the `tunefs -n enable rwd0s1a` but when I remounted / (still in single user mode) it would not keep soft updates enabled. When I tried it earlier today (it's at a remote site now that takes me an hour to get to) I tried from "boot -s" and managed to get rwd1s1e (/usr .. this box only has / and /usr mount points on different physical IDE drives) to stay enabled but it refused to even set the bit on rwd0s1a even though it was mounted RO. Do I need [br]oot & fixit disks? -- Ben [too much uptime for a human body] Williams mailto:williamsl@Home.Com Tuesday, December 21, 1999, 5:40:49 PM, Gregory Bond wrote: >> Well, I did the same way Michel did, about 3-4 months ago. >> Worked fine for me I didn't have to boot off any special >> diskette or anything, just boot into single and tunefs the >> root filesystem. GB> To be fair to chris, the ability to enable softupdates on RO partitions is GB> relatively new. To turn softupdates on for /, you _used_ to have to boot from GB> a floppy/CD; nowadays boot -s is enough. GB> To Unsubscribe: send mail to majordomo@FreeBSD.org GB> 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 Tue Dec 21 19: 2:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 024BF14CAB for ; Tue, 21 Dec 1999 19:02:10 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 120c2R-0004Ww-00; Tue, 21 Dec 1999 19:02:07 -0800 Date: Tue, 21 Dec 1999 19:02:02 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Ben WIlliams Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Re[2]: SOFTUPDATES In-Reply-To: <9880.991221@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 Tue, 21 Dec 1999, Ben WIlliams wrote: > How far back is "used to"? I have a 3.2-RELEASE box that I tried > booting into single-user mode both via `shutdown now` and 'boot -s' > and couldn't get it to enable soft updates on /. When I did > `shutdown now` it would complete the `tunefs -n enable rwd0s1a` but Probably because the r* superblocks are kept in memory, and don't modify the ondisk superblock. I think tunefs needs some more IQ in what devices it modifies. tunefs is fine to use with r* devices if you just want to see what the current settings are. I think tunefs should refuse to use the raw device for updating parameters, and always use the raw device to display parameters (so that -p works when the file system is mounted). Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 19:10:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id EC40714F98 for ; Tue, 21 Dec 1999 19:10:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA06155 for ; Tue, 21 Dec 1999 19:14:55 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912220314.TAA06155@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: stable@freebsd.org Subject: Mylex RAID controller driver update Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Dec 1999 19:14:55 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The third update to the Mylex PCI:SCSI RAID controller driver for FreeBSD-3.x-STABLE is now available at http://www.freebsd.org/~msmith/RAID/mylex/mlx-stable-991221.tar.gz Key new items in this version: - Finally, a fix for the "mlx%d: poll still busy(%d)" bug. - Support for the eXtremeRAID 1100 and AcceleRAID 352 controllers. This update has also been tested with FreeBSD-3.4-RELEASE. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 19:23:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.tn.home.com (ha1.rdc1.tn.home.com [24.2.7.66]) by hub.freebsd.org (Postfix) with ESMTP id 503A114A28 for ; Tue, 21 Dec 1999 19:23:41 -0800 (PST) (envelope-from williamsl@Home.Com) Received: from RELIABLE ([24.4.115.31]) by mail.rdc1.tn.home.com (InterMail v4.01.01.00 201-229-111) with ESMTP id <19991222032339.DHAJ17996.mail.rdc1.tn.home.com@RELIABLE>; Tue, 21 Dec 1999 19:23:39 -0800 Date: Tue, 21 Dec 1999 22:22:48 -0500 From: Ben WIlliams X-Mailer: The Bat! (v1.34a) UNREG / CD5BF9353B3B7091 Reply-To: Ben WIlliams X-Priority: 3 (Normal) Message-ID: <16932.991221@Home.Com> To: freebsd-stable@FreeBSD.ORG Cc: Tom Subject: Re[4]: SOFTUPDATES In-reply-To: References: 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 Tuesday, December 21, 1999 So that's a "Yes you need [br]oot & fixit"? (I actually tried it with wd0s1a too and got the same effect.) I'll just take my disks next time I go up to see the router/webserver/mailserver(pop&smtp)/ pain-in-my-ass box and be done with it. Thanks for the input. Tuesday, December 21, 1999, 10:02:02 PM, you wrote: T> On Tue, 21 Dec 1999, Ben WIlliams wrote: >> How far back is "used to"? I have a 3.2-RELEASE box that I tried >> booting into single-user mode both via `shutdown now` and 'boot -s' >> and couldn't get it to enable soft updates on /. When I did >> `shutdown now` it would complete the `tunefs -n enable rwd0s1a` but T> Probably because the r* superblocks are kept in memory, and don't modify T> the ondisk superblock. T> I think tunefs needs some more IQ in what devices it modifies. tunefs T> is fine to use with r* devices if you just want to see what the current T> settings are. I think tunefs should refuse to use the raw device for T> updating parameters, and always use the raw device to display parameters T> (so that -p works when the file system is mounted). T> Tom -- Ben mailto:williamsl@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 21 19:34:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id C5C9014E99 for ; Tue, 21 Dec 1999 19:34:11 -0800 (PST) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-384.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FN400NLUHWP0H@mail.uni-bielefeld.de> for stable@freebsd.org; Wed, 22 Dec 1999 04:34:03 +0100 (MET) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id EAA00808 for stable@freebsd.org; Wed, 22 Dec 1999 04:34:18 +0100 (CET envelope-from bjoern) Date: Wed, 22 Dec 1999 04:34:18 +0100 From: Bjoern Fischer Subject: ypbind won't start always To: stable@freebsd.org Message-id: <19991222043418.B749@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, on our diskless clients (server and clients 3.4-STABLE), ypbind won't start in approx 3 out of 5 times. No error messages on stdout nor stderr nor syslog. The exit code of ypbind is 0 (zero). It seems to be a heisenbug: When ktraceing ypbind directly in rc.network, starting ypbind manually, or when doing a `sleep 1' before starting ypbind in rc.network, everything is fine. Maybe the portmapper is not ready yet, when ypbind starts. Unfortunately, when starting the portmapper with -d as a background process, the problem disappears, too. I really don't know how to dig into it. Has anyone an idea? Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 19:34:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id DEA83150FF for ; Tue, 21 Dec 1999 19:34:16 -0800 (PST) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-384.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FN400NLUHWP0H@mail.uni-bielefeld.de> for stable@freebsd.org; Wed, 22 Dec 1999 04:34:02 +0100 (MET) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id EAA00795 for stable@freebsd.org; Wed, 22 Dec 1999 04:23:20 +0100 (CET envelope-from bjoern) Date: Wed, 22 Dec 1999 04:23:20 +0100 From: Bjoern Fischer Subject: /boot/loader fails to reset AMD K6-II FPU To: stable@freebsd.org Message-id: <19991222042320.A749@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, this may be a BIOS/Mainboard issue, so I ask here before filling out a PR. When I reboot the system from the /boot/loader command line (with `reboot'), the system is being resetted, the kernel loads and starts, and when the FPU is being initialized the kernel traps. Can anyone reproduce this? At least this CPU seems to be affected: CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x58c Stepping =3D 12 Features=3D0x8021bf AMD Features=3D0x80000800 Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 19:45:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hawkwind.ncsa.uiuc.edu (hawkwind.ncsa.uiuc.edu [141.142.21.154]) by hub.freebsd.org (Postfix) with ESMTP id CCB2814F45 for ; Tue, 21 Dec 1999 19:45:29 -0800 (PST) (envelope-from koziol@hawkwind.ncsa.uiuc.edu) Received: (from koziol@localhost) by hawkwind.ncsa.uiuc.edu (8.9.3/8.9.2) id VAA79737 for stable@freebsd.org; Tue, 21 Dec 1999 21:45:23 -0600 (CST) (envelope-from koziol) Message-Id: <199912220345.VAA79737@hawkwind.ncsa.uiuc.edu> Subject: error installing latest stable To: stable@freebsd.org Date: Tue, 21 Dec 1999 21:45:23 -0600 (CST) From: koziol@ncsa.uiuc.edu Reply-To: koziol@ncsa.uiuc.edu X-Mailer: ELM [version 2.4ME+ PL65 (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 Howdy, I've cvsup'ed the current version of the stable branch [several times today] and have been trying to get my system updated to the new 3.4 release. The build proceeds fine, but the make installworld is failing as such: install -c -o root -g wheel -m 644 diskless/209.157.86.12/README /usr/share/exam ples/diskless/209.157.86.12/README install: /usr/share/examples/diskless/209.157.86.12/README: No such file or dire ctory *** Error code 71 Stop. *** Error code 1 I've poked around a little and it looks like the files and directories exist, but it's definitely not happy... :-( My system is a 3.3-STABLE machine cvsup'ed from around November 18th. Any ideas? Thanks, Quincey To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 19:52:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id 1917314F45; Tue, 21 Dec 1999 19:52:53 -0800 (PST) (envelope-from jedgar@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id 28E449B4F; Tue, 21 Dec 1999 22:52:51 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id 1C8CABA0C; Tue, 21 Dec 1999 22:52:51 -0500 (EST) Date: Tue, 21 Dec 1999 22:52:50 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Mike Smith Cc: stable@freebsd.org Subject: Re: Mylex RAID controller driver update In-Reply-To: <199912220314.TAA06155@mass.cdrom.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 Tue, 21 Dec 1999, Mike Smith wrote: > > The third update to the Mylex PCI:SCSI RAID controller driver for > FreeBSD-3.x-STABLE is now available at > > http://www.freebsd.org/~msmith/RAID/mylex/mlx-stable-991221.tar.gz > According to the README: Copy the files mlx.c, mlxvar.h, mlxreg.h and mlxio.h into /sys/pci... however, mlxio.h is not present in the archive (and doesn't appear to be required for any of the sources)...typo in README or missing file? ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@freebsd.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 20:13:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 73DD015251 for ; Tue, 21 Dec 1999 20:13:24 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id PAA27236; Wed, 22 Dec 1999 15:13:15 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id PAA05204; Wed, 22 Dec 1999 15:13:12 +1100 (EST) Message-Id: <199912220413.PAA05204@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: Ben WIlliams Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Re[2]: SOFTUPDATES In-reply-to: Your message of Tue, 21 Dec 1999 21:08:34 -0500. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Dec 1999 15:13:12 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How far back is "used to"? I have a 3.2-RELEASE box that I tried > booting into single-user mode both via `shutdown now` and 'boot -s' > and couldn't get it to enable soft updates on /. Looking at the CVS logs for sbin/tunefs/tunefs.c shows ---------------------------- revision 1.7 date: 1999/01/20 01:22:39; author: luoqi; state: Exp; lines: +47 -4 branches: 1.7.2; Allow tuning of read-only mounted file system. --------- which is (IIUC) before 3.1-R. But there is some other magic to do with whether the root partition is RO or RW when booting that is (i think) later. Note that 'shutdown' is not the same as 'boot -s': In the latter case, the root partition is mounted read-only and has never been mounted writable (since the last boot). In the former case, the root partition was mounted writable in multiuser mode and there is no way to go back to read-only, so the root partition is still writable (and hence not tunefs-able) in single-user mode. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 20:51:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from server.baldwin.cx (ric-39.freedomnet.com [198.240.105.39]) by hub.freebsd.org (Postfix) with ESMTP id ED8EA15037 for ; Tue, 21 Dec 1999 20:51:42 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id XAA14929; Tue, 21 Dec 1999 23:51:34 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <199912220451.XAA14929@server.baldwin.cx> X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199912220413.PAA05204@lightning.itga.com.au> Date: Tue, 21 Dec 1999 23:51:32 -0500 (EST) From: John Baldwin To: Gregory Bond Subject: Re: Re[2]: SOFTUPDATES Cc: freebsd-stable@FreeBSD.org, Ben WIlliams Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 22-Dec-99 Gregory Bond wrote: >> How far back is "used to"? I have a 3.2-RELEASE box that I tried >> booting into single-user mode both via `shutdown now` and 'boot -s' >> and couldn't get it to enable soft updates on /. > > Looking at the CVS logs for sbin/tunefs/tunefs.c shows > ---------------------------- > revision 1.7 > date: 1999/01/20 01:22:39; author: luoqi; state: Exp; lines: +47 -4 > branches: 1.7.2; > Allow tuning of read-only mounted file system. > > --------- > > which is (IIUC) before 3.1-R. But there is some other magic to do with > whether > the root partition is RO or RW when booting that is (i think) later. > > Note that 'shutdown' is not the same as 'boot -s': In the latter case, the > root partition is mounted read-only and has never been mounted writable > (since > the last boot). In the former case, the root partition was mounted writable > in > multiuser mode and there is no way to go back to read-only, so the root > partition is still writable (and hence not tunefs-able) in single-user mode. Err, 'mount -u -o ro /' makes root read-only again :) -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.cslab.vt.edu/~jobaldwi/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 21: 0:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from inbox.org (inbox.org [216.22.145.8]) by hub.freebsd.org (Postfix) with ESMTP id E1B3C14E7B for ; Tue, 21 Dec 1999 21:00:23 -0800 (PST) (envelope-from bsd@a.servers.aozilla.com) Received: from localhost (bsd@localhost) by inbox.org (8.9.3/8.9.3) with SMTP id AAA26596 for ; Wed, 22 Dec 1999 00:00:31 -0500 (EST) Date: Wed, 22 Dec 1999 00:00:31 -0500 (EST) From: "Mr. K." X-Sender: bsd@inbox.org To: freebsd-stable@freebsd.org Subject: errata notes 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 http://www.freebsd.org/releases/3.4R/errata.html reads FreeBSD 3.3 Errata Notes --- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 21: 9:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id B49D01517B for ; Tue, 21 Dec 1999 21:09:52 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 120e20-0007aP-00; Tue, 21 Dec 1999 21:09:48 -0800 Date: Tue, 21 Dec 1999 21:09:43 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Ben WIlliams Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Re[4]: SOFTUPDATES In-Reply-To: <16932.991221@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 Tue, 21 Dec 1999, Ben WIlliams wrote: > Tuesday, December 21, 1999 > So that's a "Yes you need [br]oot & fixit"? (I actually tried it > with wd0s1a too and got the same effect.) I'll just take my disks next > time I go up to see the router/webserver/mailserver(pop&smtp)/ > pain-in-my-ass box and be done with it. > > Thanks for the input. > No, you just need to use the correct device. I just did a server today, I booted single user and turned softupdates on for ALL filesystems, including root. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 21:22:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ns.itga.com.au (ns.itga.com.au [192.83.119.129]) by hub.freebsd.org (Postfix) with ESMTP id 36E2C15042; Tue, 21 Dec 1999 21:22:19 -0800 (PST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by ns.itga.com.au (8.9.3/8.9.3) with ESMTP id QAA27487; Wed, 22 Dec 1999 16:22:11 +1100 (EST) (envelope-from gnb@itga.com.au) Received: from lightning.itga.com.au (lightning.itga.com.au [192.168.71.20]) by lightning.itga.com.au (8.9.3/8.9.3) with ESMTP id QAA09357; Wed, 22 Dec 1999 16:22:08 +1100 (EST) Message-Id: <199912220522.QAA09357@lightning.itga.com.au> X-Mailer: exmh version 2.0.1 12/23/97 From: Gregory Bond To: John Baldwin Cc: freebsd-stable@FreeBSD.ORG, Ben WIlliams Subject: Re: Re[2]: SOFTUPDATES In-reply-to: Your message of Tue, 21 Dec 1999 23:51:32 -0500. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Dec 1999 16:22:08 +1100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Err, 'mount -u -o ro /' makes root read-only again :) Really? This actually works?!!? sys/kern/vfs-syscalls.c has /* * We only allow the filesystem to be reloaded if it * is currently mounted read-only. */ if ((SCARG(uap, flags) & MNT_RELOAD) && ((mp->mnt_flag & MNT_RDONLY) == 0)) { vput(vp); return (EOPNOTSUPP); /* Needs translation */ } Greg, no expert in kernel stuff... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 21:53:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from borg-cube.com (226-193.adsl2.avtel.net [207.71.226.193]) by hub.freebsd.org (Postfix) with ESMTP id 0F4A214F51; Tue, 21 Dec 1999 21:53:43 -0800 (PST) (envelope-from dburr@pobox.com) Received: from locutus.collective.borg-cube.com (dburr@locutus.collective.borg-cube.com [192.168.0.1]) by borg-cube.com (8.9.3/8.9.3) with ESMTP id VAA26564; Tue, 21 Dec 1999 21:53:37 -0800 (PST) (envelope-from dburr@pobox.com) Date: Tue, 21 Dec 1999 21:53:37 -0800 (PST) From: Donald Burr To: FreeBSD Questions Cc: freebsd-stable@freebsd.org Subject: NTFS in 3.4-R, will it work with Windows 2000? 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 Will the NTFS support in 3.4-RELEASE work with Windows 2000 filesystems? Win2K uses NTFS, I think, so it probably will work, but i thought i had better ask before I do something potentially destructive to my data. :) Thanks in advance, Donald -- Donald Burr Resistance is Futile! | FreeBSD: The WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | Serve! http:// Phone: (805) 957-9666 FAX: (800) 492-5954 | www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 22:34:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 8109B15459; Tue, 21 Dec 1999 22:34:05 -0800 (PST) (envelope-from obrien@NUXI.com) Received: (from obrien@localhost) by relay.nuxi.com (8.9.3/8.9.3) id WAA79270; Tue, 21 Dec 1999 22:34:04 -0800 (PST) (envelope-from obrien) Date: Tue, 21 Dec 1999 22:34:04 -0800 From: "David O'Brien" To: Donald Burr Cc: FreeBSD Questions , freebsd-stable@FreeBSD.ORG Subject: Re: NTFS in 3.4-R, will it work with Windows 2000? Message-ID: <19991221223403.A79250@relay.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre1i In-Reply-To: X-Operating-System: FreeBSD 3.3-STABLE Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Dec 21, 1999 at 09:53:37PM -0800, Donald Burr wrote: > Will the NTFS support in 3.4-RELEASE work with Windows 2000 filesystems? Good question. > Win2K uses NTFS, I think, Yes it does. But Micro$oft has modified NTFS for Win2k. Not even NT4.0 pre SP5 can read Win2k NTFS partitions. -- -- David (obrien@NUXI.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 21 22:35:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from awfulhak.org (dynamic-99.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.227]) by hub.freebsd.org (Postfix) with ESMTP id EA5E715004 for ; Tue, 21 Dec 1999 22:35:18 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from hak.lan.Awfulhak.org (root@hak.lan.Awfulhak.org [172.16.0.12]) by awfulhak.org (8.9.3/8.9.3) with ESMTP id GAA18657; Wed, 22 Dec 1999 06:35:16 GMT (envelope-from brian@lan.awfulhak.org) Received: from hak.lan.Awfulhak.org (brian@localhost.lan.Awfulhak.org [127.0.0.1]) by hak.lan.Awfulhak.org (8.9.3/8.9.3) with ESMTP id IAA00872; Tue, 21 Dec 1999 08:19:08 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <199912210819.IAA00872@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Stephen Montgomery-Smith Cc: freebsd-stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org Subject: Re: Errata for 3.4R In-Reply-To: Message from Stephen Montgomery-Smith of "Mon, 20 Dec 1999 23:11:06 CST." <385F0BEA.ABBD694F@math.missouri.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 21 Dec 1999 08:19:08 +0000 From: Brian Somers Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I was looking at the FreeBSD web page, and I noticed that at the top of the > page for the Errata for FreeBSD 3.4R > ( http://www.freebsd.org/releases/3.4R/errata.html ) > that it says: > > FreeBSD 3.3 Errata Notes Hmm, this error should be put in ERRATA.TXT :-) -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 22:40:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alexander.pentalpha.com.hk (alexander.pentalpha.com.hk [210.176.109.1]) by hub.freebsd.org (Postfix) with ESMTP id A9BEB1540A for ; Tue, 21 Dec 1999 22:40:07 -0800 (PST) (envelope-from danny@pentalpha.com.hk) Received: (from uucp@localhost) by alexander.pentalpha.com.hk (8.9.3/8.9.3) id OAA96899 for ; Wed, 22 Dec 1999 14:40:04 +0800 (CST) (envelope-from danny@pentalpha.com.hk) Received: from 001.mis.pentalpha.com.hk(10.0.0.168), claiming to be "001.mis.penatlpha.com.hk" via SMTP by alexander.pentalpha.com.hk, id smtpdD96897; Wed Dec 22 14:40:01 1999 Message-ID: <004901bf4c47$876b2c00$a800000a@001.mis.penatlpha.com.hk> From: "Danny Wong" To: Subject: help on make world Date: Wed, 22 Dec 1999 14:41:08 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When I try to make world of 3.4-stable 22Dec99, I found the following error. Can you help me? install -c -o root -g wheel -m 644 cvsup/stable-supfile /usr/share/examples/cvsu p/stable-supfile install -c -o root -g wheel -m 644 cvsup/standard-supfile /usr/share/examples/cv sup/standard-supfile install -c -o root -g wheel -m 644 cvsup/doc-supfile /usr/share/examples/cvsup/d oc-supfile install -c -o root -g wheel -m 644 cvsup/www-supfile /usr/share/examples/cvsup/w ww-supfile install -c -o root -g wheel -m 644 diskless/209.157.86.12/README /usr/share/exam ples/diskless/209.157.86.12/README *** Error code 71 Stop. *** Error code 1 Stop. *** Error code 1 Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 23:10:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from maillist.kabelfoon.nl (maillist.kabelfoon.nl [194.178.9.136]) by hub.freebsd.org (Postfix) with ESMTP id 8389A152A9 for ; Tue, 21 Dec 1999 23:10:14 -0800 (PST) (envelope-from sdehaan@caiw.nl) Received: from 192.168.8.115 (unknown [192.168.8.115]) by maillist.kabelfoon.nl (Postfix) with ESMTP id 40A403AA0; Wed, 22 Dec 1999 08:10:13 +0100 (CET) Message-Id: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Company: Kabelfoon B.V. Date: Wed, 22 Dec 1999 08:03:50 +0100 To: Vinod Balakrishnan , freebsd-stable@FreeBSD.ORG From: Koos de Haan Subject: Re: de driver problems with ZNYX 21140A cards Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, We also use the same ZNYX cards in some boxes and experiencing the same problems. (I didn't get any TCP througput above approx 40 Mbit/s ever.) NetBSD which is using the same driver also is suffering from the same problem. Under Linux the cards work fine, but thats another driver. I think it is some bug in the de driver which causes these problems. I will get the driver form ZNYX a try on my 3.4-STABLE system to see wat will happen. Regards, Koos de Haan Op 03:02 +0100 22-12-1999, Vinod Balakrishnan schreef: > hi, > > I am working on a 6 pc test bed (FreeBSD boxes) having the > 4 port 100Mbps 21140A Znyx cards. > > I am running FreeBSD 3.1-Release. I have also tested it on FreeBSD > 3.0-Stable. > > I am facing a few problems with the device driver de. > > 1. netstat -I gives lots of output errors. > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs > Coll > de3 1500 10.0.8/24 10.0.8.5 434417 0 290242 289158 > 0 > > If I use the device driver provided at the ZNYX website (znyx.com) zxe > then I do not see any Oerrs. > > 2. ifconfig de3 mediaopt full-duplex , returns an error: > ifconfig:SIOCSIFMEDIA: Device not configured > > 3. The throughput of a TCP flow from one FreeBSD box to another (each > having a ZNYX card) varies with the packet size. > For instance for a packet size of 150bytes I achieve 90Mbps. > For packetsize of 500bytes it is only 60-70Mbps. > > 4. If I run a tcp flow from one FreeBSD box to another via an intermediate > FreeBSD box (all having the ZNYX344 card and de device driver) I get a > throughput of 40Mbps only for 500 byte packets. > > > All of these above problems are not visible when I use the zxe > device driver. > > thank you for your time, > > -Vinod > > > *********************************************************************** > B. Vinod Kumar > Dept. of Computer Science, > University of Virginia, Charlottesville > Residence: > 101, Carrollton Terrace, #2 > Charlottesville, Va-22903 > 804-293-5101 > > ********************************************************************** > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message - -- Kabelfoon BV Industriestraat 30, Postbus 45, 2670 AA NAALDWIJK e-mail info@kabelfoon.nl voor informatie, kabelfoon@kabelfoon.nl voor abonnementszaken, help@kabelfoon.nl voor de helpdesk Homepage : http://www.kabelfoon.nl/ Zie http://www.kabelfoon.nl/pgp/ voor Kabelfoon public keys To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 23:50:25 1999 Delivered-To: freebsd-stable@freebsd.org Received: from sonet.crimea.ua (OTC-sl3-FLY.CRIS.NET [212.110.136.71]) by hub.freebsd.org (Postfix) with ESMTP id 4532515496 for ; Tue, 21 Dec 1999 23:50:13 -0800 (PST) (envelope-from phantom@scorpion.crimea.ua) Received: (from uucp@localhost) by sonet.crimea.ua (8.9.3/8.9.3) with UUCP id JAA11278; Wed, 22 Dec 1999 09:54:42 +0300 (MSK) Received: (from phantom@localhost) by scorpion.crimea.ua (8.8.8/8.8.5+ssl+keepalive) id JAA07108; Wed, 22 Dec 1999 09:39:19 +0300 (MSK) Date: Wed, 22 Dec 1999 09:39:19 +0300 From: Alexey Zelkin To: Dylan Neild Cc: Joao Pedras , freebsd-stable@freebsd.org Subject: Re: today's stable ? Message-ID: <19991222093919.B6558@scorpion.crimea.ua> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: X-Operating-System: FreeBSD 2.2.7-RELEASE i386 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi, Sorry guys! It's was my mistake. It's fixed now in etc/mtree/BSD.usr.dist rev 1.146.2.11. Please cvsup and notice me any problems. PS: It was bad idea to not to sleep few nights sequently ... Thanks, On Tue, Dec 21, 1999 at 08:49:50PM -0500, Dylan Neild wrote: > Hi Guys, > > If you: > > cd /usr/share/examples > mkdir diskless > cd diskless > cp -r /usr/src/share/examples/diskless/* . > cd /usr/src > make installworld > > It'll work nicely. > > > Dylan > > > > From: Joao Pedras > > Date: Tue, 21 Dec 1999 22:23:41 -0000 (GMT) > > To: freebsd-stable@FreeBSD.ORG > > Subject: today's stable ? > > > > Hello all! > > > > My -stable sup'ed this afternoon is giving me this in installworld : > > > > install -c -o root -g wheel -m 644 cvsup/www-supfile > > /usr/share/examples/cvsup/www-supfile > > install -c -o root -g wheel -m 644 diskless/209.157.86.12/README > > /usr/share/examples/diskless/209.157.86.12/README > > install: /usr/share/examples/diskless/209.157.86.12/README: No such file or > > directory > > *** Error code 71 > > > > Stop. > > *** Error code 1 > > > > Stop. > > *** Error code 1 > > > > Is it just me ? > > > > Thanks > > > > Joao > > > > > > ^\ /^ > > O O > > ----------------------------------------o00-(_)-00o-------------------------- > > Sent on 21-Dec-99 at 22:22:35 > > Powered by FreeBSD -> http://www.freebsd.org <- "The Power to Serve" > > More info @ http://www.freebsddiary.org/freebsd/ - http://www.daemonnews.org/ -- /* Alexey Zelkin && phantom@cris.net */ /* Tavric National University && phantom@crimea.edu */ /* http://www.ccssu.crimea.ua/~phantom && phantom@FreeBSD.org */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Tue Dec 21 23:53:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mini.ntl.ru (mini.ntl.ru [195.34.20.3]) by hub.freebsd.org (Postfix) with ESMTP id 80A531513B for ; Tue, 21 Dec 1999 23:53:46 -0800 (PST) (envelope-from root@ntl.ru) Received: from netline (netline.ntl.ru [195.34.20.2]) by mini.ntl.ru with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id Y9AXB1NV; Wed, 22 Dec 1999 10:53:33 +0300 Message-ID: <011201bf4c51$b7616aa0$021422c3@ntl.ru> Reply-To: "Sergey A Nasedkin" From: "Sergey A Nasedkin" To: Subject: Date: Wed, 22 Dec 1999 10:54:03 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG subscribe freebsd-stable ó õ×ÁÖÅÎÉÅÍ, óÅÒÇÅÊ îÁÓÅÄËÉÎ. root@ntl.ru úáï "îÜÔìÁÊÎ" ÔÅÌ. 7847616 ÆÁËÓ 7847644 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 1: 0:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id E19681540A for ; Wed, 22 Dec 1999 01:00:14 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id KAA14293 for freebsd-stable@FreeBSD.ORG; Wed, 22 Dec 1999 10:00:05 +0100 (CET) (envelope-from olli) Date: Wed, 22 Dec 1999 10:00:05 +0100 (CET) From: Oliver Fromme Message-Id: <199912220900.KAA14293@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: SOFTUPDATES Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Gregory Bond wrote in list.freebsd-stable: > > Well, I did the same way Michel did, about 3-4 months ago. > > Worked fine for me I didn't have to boot off any special > > diskette or anything, just boot into single and tunefs the > > root filesystem. > > To be fair to chris, the ability to enable softupdates on RO partitions is > relatively new. To turn softupdates on for /, you _used_ to have to boot from > a floppy/CD; nowadays boot -s is enough. Uhm no, you never had to do that. In the very early days of soft-updates, you had to boot single-user, then use tunefs on the root partition (which is mounted read-only at that point), then press the reset-button. Of course, you _could_ also boot from floppy or CD (you still can do that today if you want), but it was not necessary. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 1:42:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 3345B15474 for ; Wed, 22 Dec 1999 01:42:33 -0800 (PST) (envelope-from brad@shub-internet.org) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id KAA07367; Wed, 22 Dec 1999 10:42:24 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <385FD807.72FC177D@home.com> References: <385EFAEF.5F286795@home.com> <19991221112336.A22081@home.com> <385FD807.72FC177D@home.com> Date: Wed, 22 Dec 1999 10:08:42 +0100 To: tsikora@powerusersbbs.com, "freebsd-stable@FreeBSD.ORG" From: Brad Knowles Subject: Re: SOFTUPDATES Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 2:41 PM -0500 1999/12/21, Ted Sikora wrote: > Problem is my > /tmp is on / so in the future it may be wise to make a /tmp directory. > How about linking /tmp to /usr or /var for my current setup? I wouldn't suggest that. You can't guarantee that /usr will be mounted at boot when you might need to write to /tmp, unless you put /usr on / as well. Much better would be to make /tmp a separate filesystem, either softupdates or mfs. At least that way, you could write to the /tmp mount point before /tmp is mounted, and although you'd have to be careful to clean out the mount point periodically (otherwise / could mysteriously run short on space), you'd at least be able to ensure that /tmp would be writable early in the boot process. -- Brad Knowles Your mouse has moved. Windows NT must be restarted for the change to take effect. Reboot now? [ OK ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 1:59:52 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pooh.elsevier.nl (p2.as1.naas1.eircom.net [159.134.254.2]) by hub.freebsd.org (Postfix) with ESMTP id 5D97314EF2 for ; Wed, 22 Dec 1999 01:59:48 -0800 (PST) (envelope-from steve@pooh.elsevier.nl) Received: (from steve@localhost) by pooh.elsevier.nl (8.9.3/8.9.3) id JAA21601; Wed, 22 Dec 1999 09:59:57 GMT (envelope-from steve) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991221160437.A40524@dblab.ece.ntua.gr> Date: Wed, 22 Dec 1999 09:59:36 -0000 (GMT) From: "Steve O'Hara-Smith" To: Yiorgos Adamopoulos Subject: Re: SOFTUPDATES Cc: FreeBSD Stable , tsikora@powerusersbbs.com, David Schwartz Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 21-Dec-99 Yiorgos Adamopoulos wrote: > On Mon, Dec 20, 1999 at 08:27:55PM -0800, David Schwartz wrote: >> One final reason is possible increased risk. > > Or forgetting to build a kernel with it sometime afterwards ;-) Shouldn't do any harm, the data on disc is the same with and without SOFTUPDATES. Of course the benefits will vanish :) ------------------------------------------------------- Tell a computer to WIN and ... ... You lose ------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 4:55:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 135B515069 for ; Wed, 22 Dec 1999 04:55:20 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 120lIV-000HTt-00 for freebsd-stable@freebsd.org; Wed, 22 Dec 1999 04:55:19 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: FreeBSD Stable Subject: ntpd coring again Message-Id: Date: Wed, 22 Dec 1999 04:55:19 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i upgraded from 3.4-RC to 3.4-stable-9912210018 and ntpd started coring reliably again. kernel has posix options. can not rebuild /usr/ports/net/ntp, as has been discussed previously. note that i have two hosts and it only cores on one. both cvsupped at (about) the same time. both asus p2b motherboards. the stable one is smp, the unstable is mono. there are other differences, e.g. cpu speed, the unstable one is headless, ... randy # gdb /usr/local/bin/ntpd /ntpd.core GNU gdb 4.18 Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"... (no debugging symbols found)... Core was generated by `ntpd'. Program terminated with signal 8, Floating point exception. Reading symbols from /usr/lib/libm.so.2...(no debugging symbols found)...done. Reading symbols from /usr/lib/libkvm.so.2...(no debugging symbols found)... done. Reading symbols from /usr/lib/libc.so.3...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)... done. #0 0x80509d3 in free () (gdb) where #0 0x80509d3 in free () #1 0x8081848 in sys_errlist () #2 0x805327e in free () #3 0x80547af in free () #4 0x8053180 in free () #5 0x8052893 in free () #6 0x805bf96 in free () #7 0x805bc22 in free () #8 0x8049a31 in free () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 6:47:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from locsg.garant.ru (locsg.garant.ru [195.209.33.196]) by hub.freebsd.org (Postfix) with ESMTP id 5F80114D70; Wed, 22 Dec 1999 06:47:40 -0800 (PST) (envelope-from taurus@cave.garant.ru) Received: from cave.garant.ru (cave.garant.ru [10.14.3.31]) by locsg.garant.ru (8.9.3/8.9.3) with ESMTP id RAA19376; Wed, 22 Dec 1999 17:46:44 +0300 (MSK) Received: from localhost (taurus@localhost) by cave.garant.ru (8.9.3/8.9.3) with ESMTP id RAA12213; Wed, 22 Dec 1999 17:47:25 +0300 (MSK) Date: Wed, 22 Dec 1999 17:47:23 +0300 (MSK) From: "Andrew A. Bely" To: freebsd-stable@freebsd.org Cc: freebsd-hackers@freebsd.org Subject: ATAPI problems in 3.2-RELEASE 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 There is a problem with an ATAPI devices - CD-ROM, TAPE All of it successfully detects but when i try to get access to them the term with current process hanging up... and neither Ctrl-C nor 'kill -9 xxx' can't ends it ( only reboot helps ). Devices are not accessable. Can anybody advise something? Thanks. Here is dmesg output: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-RELEASE #7: Mon Oct 11 19:59:34 GMT 1999 andrew@home:/usr/src/sys/compile/VAULT Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (350.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x651 Stepping=1 Features=0x183f9ff> real memory = 134217728 (131072K bytes) avail memory = 127741952 (124748K bytes) Preloaded elf kernel "kernel" at 0xc02b4000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 chip3: rev 0x02 on pci0.7.3 wb0: rev 0x00 int a irq 5 on pci0.14.0 wb0: Ethernet address: 00:80:48:db:55:70 wb0: autoneg complete, link status good (half-duplex, 100Mbps) ncr0: rev 0x01 int a irq 10 on pci0.19.0 Probing for devices on PCI bus 1: vga0: rev 0x5c on pci1.0.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 on isa wdc0: unit 0 (atapi): , removable, intr, dma, iordis acd0: drive speed 6875KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wdc1 at 0x170-0x177 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordis wst0: Drive empty, readonly, reverse, qfa, ecc, 512b wst0: Max speed=600Kb/s, Transfer limit=52 blocks, Buffer size=728 blocks ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface ccd0-3: Concatenated disk drivers Waiting 15 seconds for SCSI devices to settle changing root device to da0s1a da1 at ncr0 bus 0 target 6 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da0 at ncr0 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) Andrew A. Bely Software developer in Garant-Service, Moscow, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 7:30:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from locsg.garant.ru (locsg.garant.ru [195.209.33.196]) by hub.freebsd.org (Postfix) with ESMTP id 3668614F78; Wed, 22 Dec 1999 07:30:27 -0800 (PST) (envelope-from taurus@cave.garant.ru) Received: from cave.garant.ru (cave.garant.ru [10.14.3.31]) by locsg.garant.ru (8.9.3/8.9.3) with ESMTP id SAA21514; Wed, 22 Dec 1999 18:29:31 +0300 (MSK) Received: from localhost (taurus@localhost) by cave.garant.ru (8.9.3/8.9.3) with ESMTP id SAA12403; Wed, 22 Dec 1999 18:30:11 +0300 (MSK) Date: Wed, 22 Dec 1999 18:30:10 +0300 (MSK) From: "Andrew A. Bely" To: Chris.Smith@raytheon.co.uk Cc: freebsd-hackers@freebsd.org, freebsd-stable@freebsd.org Subject: Re: ATAPI problems in 3.2-RELEASE In-Reply-To: <0025684F.005226F1.00@rslhub.raytheon.co.uk> 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, 22 Dec 1999 Chris.Smith@raytheon.co.uk wrote: > 1. Does your CD spin up and down for no reason and then the process > accessing it crash? No, it does not. > 2. Is the board a genuine intel one? No again. Maybe it made by MicroStar, but I'm not sure. Andrew A. Bely Software developer in Garant-Service, Moscow, Russia. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 8:20:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail1.bna.bellsouth.net (mail1.bna.bellsouth.net [205.152.150.13]) by hub.freebsd.org (Postfix) with ESMTP id 1736F151AF for ; Wed, 22 Dec 1999 08:20:10 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-216-78-4-192.jan.bellsouth.net [216.78.4.192]) by mail1.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id LAA24652; Wed, 22 Dec 1999 11:20:01 -0500 (EST) Message-ID: <3860FA29.D6778406@siteplus.com> Date: Wed, 22 Dec 1999 11:19:53 -0500 From: Jim Weeks X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i586) X-Accept-Language: en MIME-Version: 1.0 To: Gerhard Sittig Cc: FreeBSD Stable Subject: Re: PCI internal modem References: <199912201649.KAA85652@klentaq.com> <19991220213929.X11805@speedy.gsinet> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I may be wrong, but I believe even though this is a pci card you still have to enter the id information in /usr/src/sys/isa.sioc and rebuild you kernel. Then you would configure the irq and address at boot time with boot -c The example of how this works is at http://www.freebsd.org/FAQ/hardware.html#AEN942 and says this. ------------------------------------------------------------------------ Q: I have an internal Plug & Play modem and FreeBSD can't find it. A: You will need to add the modem's PnP ID to the PnP ID list in the serial driver. To enable Plug & Play support, compile a new kernel with controller pnp0 in the configuration file, then reboot the system. The kernel will print the PnP IDs of all the devices it finds. Copy the PnP ID from the modem to the table in /sys/i386/isa/sio.c, at about line 2777. Look for the string "SUP1310" in the structure "siopnp_ids[]" to find the table. Build the kernel again, install, reboot, and your modem should be found. You may have to manually configure the PnP devices using the `pnp' command in the boot-time configuration with a command like pnp 1 0 enable os irq0 3 drq0 0 port0 0x2f8 to make the modem show. ------------------------------------------------------------------------ Good luck, Jim Weeks Gerhard Sittig wrote: > On Mon, Dec 20, 1999 at 10:49 -0600, Wayne M Barnes wrote: > > > > How do I get my PCI modem card to work with FreeBSD 3.4? > > > > [ ... ] > > > > CSN 1 Vendor ID: CSC4236 [0x3642630e] Serial 0xffffffff Comp ID: @@@0000 [0x00000000] > > I could be wrong, but why does this sound like a sound card to > me? Don't look Crystal's chips (respective PnP cards) look like > this? I don't have one around, but could someone check this? > > Anyway -- IF it is a PCI card, why should it ever show up in the > ISA PnP section? If the port is a real serial port, it should > behave and look just like any other serial port (i.e. io=0x2F8 > for the third one, etc). If it is a so called WinModem, chances > are bad that there will be driver if the manufacturer or dealer > won't provide one. > > virtually yours - Gerhard Sittig > -- > mail -s "get pgp key" Gerhard.Sittig@gmx.net < /dev/null > > If you don't understand or are scared by any of the above > ask your parents or an adult to help you. > > 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 22 10:10:53 1999 Delivered-To: freebsd-stable@freebsd.org Received: from neptune.innovativeinternet.net (neptune.innovativeinternet.net [208.244.165.5]) by hub.freebsd.org (Postfix) with SMTP id 1B32A14DCB for ; Wed, 22 Dec 1999 10:10:51 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: (qmail 12910 invoked from network); 22 Dec 1999 18:10:48 -0000 Received: from unknown (HELO pcpsj.pfcs.com) (?GO9FRbjUSZX+o8qoOSD5HLjWhQ+NhpXl?@208.238.64.78) by 208.244.165.5 with SMTP; 22 Dec 1999 18:10:48 -0000 Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id ; Wed, 22 Dec 1999 13:10:40 -0500 (EST) Received: from root@pcnbs.pfcs.com [192.52.69.42] (HELO pcnbs.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Wed, 22 Dec 1999 10:07:51 -0800 (PST) Received: from harlan@localhost [127.0.0.1] (HELO pcnbs.pfcs.com) by pcnbs.pfcs.com (8.9.3/8.8.8) via ESMTP id ; Wed, 22 Dec 1999 13:07:50 -0500 (EST) To: Randy Bush From: stenn@whimsy.udel.edu Cc: FreeBSD Stable Subject: Re: ntpd coring again In-Reply-To: Randy Bush's (randy@psg.com) message dated Wed, 22 Dec 1999 04:55:19. X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (patch 8) (Bryce Canyon) (i386-unknown-freebsd3.3) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Wed, 22 Dec 1999 13:07:50 -0500 Message-ID: <16610.945886070@pcnbs.pfcs.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can you please download the latest (4.0.98h, as I recall) NTP code from either: or run: % configure % make # ntpd/ntpd (assuming ntpd is not currently running) and then do the gdb backtrace from there? Unless others care, you can just get back to me at . I'm running this code on -STABLE on 2 machines and no problems here. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 10:26:42 1999 Delivered-To: freebsd-stable@freebsd.org Received: from typhoon.mail.pipex.net (typhoon.mail.pipex.net [158.43.128.27]) by hub.freebsd.org (Postfix) with SMTP id 6ED7614A31 for ; Wed, 22 Dec 1999 10:26:39 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 9174 invoked from network); 22 Dec 1999 18:26:37 -0000 Received: from userah69.uk.uudial.com (HELO marder-1.) (62.188.132.254) by smtp.dial.pipex.com with SMTP; 22 Dec 1999 18:26:37 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.8.8) id SAA00378 for freebsd-stable@freebsd.org; Wed, 22 Dec 1999 18:25:55 GMT (envelope-from mark) Date: Wed, 22 Dec 1999 18:25:55 +0000 From: Mark Ovens To: freebsd-stable@freebsd.org Subject: Re: SOFTUPDATES Message-ID: <19991222182555.A322@marder-1> References: <199912211640.RAA02499@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912211640.RAA02499@dorifer.heim3.tu-clausthal.de> Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've been following this thread and decided to enable softupdates on my system. Read /sys/ufs/ffs/README.softupdates Did ``boot -s'' and ran tunefs but got an error: Enter full pathname of shell or RETURN for /bin/sh: # pwd / # tunefs -n enable /usr tunefs: soft updates set tunefs: /dev/rda1s1e: reload: Invalid argument What caused this? There's no reference in the manpage. The only odd thing about my system is that I'm running a 3.4-RC kernel with a 3.3-STABLE, as of the end of September, userland (yeah, yeah, I know I shouldn't do this, but I needed something adding to the kernel but haven't had time to make the world, and it's running fine). Softupdates appears to be working fine: marder-1:/usr/mark{52}% mount /dev/da0s3a on / (local, writes: sync 102 async 174) /dev/da1s1e on /usr (local, soft-updates, writes: sync 73 async 492) procfs on /proc (local) /dev/da0s1 on /drvc (local) /dev/da0s5 on /ntfs (local, read-only) marder-1:/usr/mark{53}% My /etc/fstab: # Device Mountpoint FStype Options Dump Pass# /dev/da0s3b none swap sw 0 0 /dev/da0s3a / ufs rw 1 1 /dev/da1s1e /usr ufs rw 2 2 # /dev/da0s3e /var ufs rw 2 2 /dev/cd0c /cdrom cd9660 ro,noauto 0 0 proc /proc procfs rw 0 0 /dev/da0s1 /drvc msdos rw 0 0 /dev/fd0 /pcfs msdos rw,noauto 0 0 /dev/da0s5 /ntfs ntfs ro 0 0 -- "there's a long-standing bug relating to the x86 architecture that allows you to install Windows too ;" -Matthew D. Fuller ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.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 22 12:10:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from polaris.pylos.net (adsl-63-195-144-244.dsl.scrm01.pacbell.net [63.195.144.244]) by hub.freebsd.org (Postfix) with ESMTP id A957414EFB for ; Wed, 22 Dec 1999 12:10:07 -0800 (PST) (envelope-from mike_p@qed.dhs.org) Received: from localhost (mike_p@localhost) by polaris.pylos.net (8.9.3/8.9.3) with ESMTP id MAA07774 for ; Wed, 22 Dec 1999 12:10:09 -0800 Date: Wed, 22 Dec 1999 12:10:09 -0800 (PST) From: Mike Pontillo X-Sender: mike_p@polaris.pylos.net To: freebsd-stable@freebsd.org Subject: PCMCIA 10/100 Network Card? 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 Anyone have any suggestions for a good, reliable, inexpensive FreeBSD/Linux-compatible PCMCIA 10/100 network card? I've been putting this off for as long as I could stand 10bT... =) Thanks a lot! --- Mike Pontillo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 12:24:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 6A9FD155AF for ; Wed, 22 Dec 1999 12:24:18 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA06572; Wed, 22 Dec 1999 20:29:25 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01098; Wed, 22 Dec 1999 20:47:03 +0100 (CET) (envelope-from wilko) Date: Wed, 22 Dec 1999 20:47:03 +0100 From: Wilko Bulte To: Bjoern Fischer Cc: stable@FreeBSD.ORG Subject: Re: /boot/loader fails to reset AMD K6-II FPU Message-ID: <19991222204703.B833@yedi.iaf.nl> References: <19991222042320.A749@frolic.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991222042320.A749@frolic.no-support.loc>; from bfischer@Techfak.Uni-Bielefeld.DE on Wed, Dec 22, 1999 at 04:23:20AM +0100 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 22, 1999 at 04:23:20AM +0100, Bjoern Fischer wrote: > Hello, > > this may be a BIOS/Mainboard issue, so I ask here > before filling out a PR. > > When I reboot the system from the /boot/loader > command line (with `reboot'), the system is > being resetted, the kernel loads and starts, > and when the FPU is being initialized the kernel > traps. > > Can anyone reproduce this? > > At least this CPU seems to be affected: > > CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > Features=0x8021bf > AMD Features=0x80000800 > Works fine on my Asus T2P4 with the same CPU: WKB ~>dmesg | grep -i amd CPU: AMD-K6(tm) 3D processor (399.81-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 AMD Features=0x80000800 But what date is your -stable? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.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 22 13:39:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id C55F4155C4 for ; Wed, 22 Dec 1999 13:39:44 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id VAA09645 for freebsd-stable@FreeBSD.ORG; Wed, 22 Dec 1999 21:35:43 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA02499 for freebsd-stable@FreeBSD.ORG; Wed, 22 Dec 1999 22:07:29 +0100 (CET) (envelope-from wilko) Date: Wed, 22 Dec 1999 22:07:28 +0100 From: Wilko Bulte To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Message-ID: <19991222220728.A2187@yedi.iaf.nl> References: <199912201836.TAA27912@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912201836.TAA27912@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Mon, Dec 20, 1999 at 07:36:31PM +0100 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Dec 20, 1999 at 07:36:31PM +0100, Oliver Fromme wrote: > Wilko Bulte wrote in list.freebsd-stable: > > On Mon, Dec 20, 1999 at 06:26:48AM +0100, Oliver Fromme wrote: > > [...] > > > Well, when I added 3DNow support to the Seti@home client, I > > > assembled the 3DNow instructions "manually", i.e. I created > > > small gas macros for that purpose. It's ugly, but it works. > > > > Being the curious kind: what speed difference did you observe? > > About 50%, that is, about 4.5 hours (instead of 9) on average > per work unit, on an Athlon-500. And I did only optimize the > FFT and didn't touch the rest. With a bit more effort, further > improvements would be certainly possible. > Is this version on the setiathome server at Berkeley? Related question: there does not seem to be a seti@home client for FreeBSD/alpha. Is there anybody working on this? -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.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 22 13:55:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relax.dreamfire.net (relax.dreamfire.net [207.113.154.29]) by hub.freebsd.org (Postfix) with ESMTP id 9840B14F78 for ; Wed, 22 Dec 1999 13:55:28 -0800 (PST) (envelope-from sean@dreamfire.net) Received: from dreamfire.net (indigo.dreamfire.net [192.168.10.8]) by relax.dreamfire.net (Postfix) with ESMTP id 2935C11A for ; Wed, 22 Dec 1999 13:55:27 -0800 (PST) Message-ID: <3861490B.E641A006@dreamfire.net> Date: Wed, 22 Dec 1999 13:56:27 -0800 From: Sean-Paul Rees Organization: The Dreamfire Solutions Group X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: stable@freebsd.org Subject: Re: AMD 3DNow instructions on FreeBSD References: <199912201836.TAA27912@dorifer.heim3.tu-clausthal.de> <19991222220728.A2187@yedi.iaf.nl> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote: > Is this version on the setiathome server at Berkeley? Is there a MMX enabled setiathome for us with non-3DNow! enhanced processors? > Related question: there does not seem to be a seti@home client for > FreeBSD/alpha. Is there anybody working on this? I bet that there is a NetBSD/alpha port. Sean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 14: 1:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id E877114EE3 for ; Wed, 22 Dec 1999 14:01:44 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id XAA04488; Wed, 22 Dec 1999 23:01:03 +0100 (CET) Message-ID: <19991222230102.A4404@foobar.franken.de> Date: Wed, 22 Dec 1999 23:01:02 +0100 From: Harold Gutch To: Wilko Bulte , freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD References: <199912201836.TAA27912@dorifer.heim3.tu-clausthal.de> <19991222220728.A2187@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <19991222220728.A2187@yedi.iaf.nl>; from Wilko Bulte on Wed, Dec 22, 1999 at 10:07:28PM +0100 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 22, 1999 at 10:07:28PM +0100, Wilko Bulte wrote: > Related question: there does not seem to be a seti@home client for > FreeBSD/alpha. Is there anybody working on this? Don't the OpenBSD/alpha and/or NetBSD/alpha-clients run under FreeBSD as well? bye, Harold -- 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 Wed Dec 22 14:26:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 3961714CB4 for ; Wed, 22 Dec 1999 14:26:33 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id XAA00562 for freebsd-stable@FreeBSD.ORG; Wed, 22 Dec 1999 23:26:32 +0100 (CET) (envelope-from olli) Date: Wed, 22 Dec 1999 23:26:32 +0100 (CET) From: Oliver Fromme Message-Id: <199912222226.XAA00562@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote in list.freebsd-stable: > On Mon, Dec 20, 1999 at 07:36:31PM +0100, Oliver Fromme wrote: > > About 50%, that is, about 4.5 hours (instead of 9) on average > > per work unit, on an Athlon-500. And I did only optimize the > > FFT and didn't touch the rest. With a bit more effort, further > > improvements would be certainly possible. > > Is this version on the setiathome server at Berkeley? No. I submitted my code to the Seti@home folks for review, they said "great, thanks!" and I've never heard anything from them again. :-( > Related question: there does not seem to be a seti@home client for > FreeBSD/alpha. Is there anybody working on this? Not that I'm aware of. I could compile a client, but the problem is that (1) my Alpha's power supply is currently broken, and (2) there is currently OpenBSD installed on it... :-} Does FeeBSD/Alpha run reliably on an AXPpci33 with Quantum Fireball (SCSI)? Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 14:27:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.uni-bielefeld.de (mail.uni-bielefeld.de [129.70.4.90]) by hub.freebsd.org (Postfix) with ESMTP id 2F15E14FCB for ; Wed, 22 Dec 1999 14:27:47 -0800 (PST) (envelope-from bfischer@Techfak.uni-bielefeld.de) Received: from frolic.no-support.loc (ppp36-98.hrz.uni-bielefeld.de) by mail.uni-bielefeld.de (Sun Internet Mail Server sims.3.5.1999.05.24.18.28.p7) with ESMTP id <0FN500K7UYE7L8@mail.uni-bielefeld.de> for stable@freebsd.org; Wed, 22 Dec 1999 23:27:45 +0100 (MET) Received: (from bjoern@localhost) by frolic.no-support.loc (8.9.3/8.9.3) id XAA02260; Wed, 22 Dec 1999 23:27:41 +0100 (CET envelope-from bjoern) Date: Wed, 22 Dec 1999 23:27:41 +0100 From: Bjoern Fischer Subject: Re: /boot/loader fails to reset AMD K6-II FPU In-reply-to: <19991222204703.B833@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Wed, Dec 22, 1999 at 08:47:03PM +0100 To: Wilko Bulte Cc: stable@freebsd.org Message-id: <19991222232741.A1344@frolic.no-support.loc> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable References: <19991222042320.A749@frolic.no-support.loc> <19991222204703.B833@yedi.iaf.nl> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 22, 1999 at 08:47:03PM +0100, Wilko Bulte wrote: [...] > > When I reboot the system from the /boot/loader > > command line (with `reboot'), the system is > > being resetted, the kernel loads and starts, > > and when the FPU is being initialized the kernel > > traps. [...] > Works fine on my Asus T2P4 with the same CPU: >=20 > WKB ~>dmesg | grep -i amd > CPU: AMD-K6(tm) 3D processor (399.81-MHz 586-class CPU) > Origin =3D "AuthenticAMD" Id =3D 0x58c Stepping =3D 12 > AMD Features=3D0x80000800 >=20 > But what date is your -stable? My stable is as fresh as Dec 20th (per CTM). The problem occurs with an ASUS P5A-B and with another noname Aladdin chipset board. Bj=F6rn --=20 -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+=20 ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 14:53:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id B877614CEF for ; Wed, 22 Dec 1999 14:53:16 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id XAA16064 for freebsd-stable@FreeBSD.ORG; Wed, 22 Dec 1999 23:53:13 +0100 (CET) (envelope-from olli) Date: Wed, 22 Dec 1999 23:53:13 +0100 (CET) From: Oliver Fromme Message-Id: <199912222253.XAA16064@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean-Paul Rees wrote in list.freebsd-stable: > Is there a MMX enabled setiathome for us with non-3DNow! enhanced > processors? No, MMX is completely useless for this kind of stuff, because MMX does not support floating point operations. Sorry. However, I modified the FFT algorithm to optimize memory throughput, at the cost of memory footprint (it needs about 2 Mbyte more RAM). The speed increase is not as impressive as with the 3DNow version, but it's still significant. Here are some numbers: Dual Celeron-466, Gigabyte 6BXD mainboard: original code: 18.0 - 18.5 hours per CPU generic optimized code: 10.5 - 11.0 hours per CPU speed increase: ~ 40% Single Celeron-333, Asus P2B mainboard: original code: 14.0 - 14.5 hours generic optimized code: 10.5 - 11.0 hours speed increase: ~ 25% Single Pentium-II-450, Asus P2B-LS mainboard: original code: 9.0 - 9.5 hours generic optimized code: 7.5 - 8.0 hours speed increase: ~ 16% As you can see, the Dual Celeron benefits the most, because it has a very weak RAM bandwidth, but fast (though small) L2 cache. AMD K7-500, MSI MS6167 mainboard: original code: 10.0 - 10.5 hours Athlon optimized code: 4.0 - 4.5 hours speed increase: ~ 60% These numbers speak for themselves. 3DNow rules. :) I'm still waiting for a response from the Seti@home folks. They have all the code, but they seem to ignore it. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 15:34:12 1999 Delivered-To: freebsd-stable@freebsd.org Received: from relax.dreamfire.net (relax.dreamfire.net [207.113.154.29]) by hub.freebsd.org (Postfix) with ESMTP id 67C3114DA6 for ; Wed, 22 Dec 1999 15:34:04 -0800 (PST) (envelope-from sean@dreamfire.net) Received: from dreamfire.net (indigo.dreamfire.net [192.168.10.8]) by relax.dreamfire.net (Postfix) with ESMTP id 78FEC65 for ; Wed, 22 Dec 1999 15:34:02 -0800 (PST) Message-ID: <38616027.2BB9C789@dreamfire.net> Date: Wed, 22 Dec 1999 15:35:03 -0800 From: Sean-Paul Rees Organization: The Dreamfire Solutions Group X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.6 sun4m) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD References: <199912222253.XAA16064@dorifer.heim3.tu-clausthal.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Oliver Fromme wrote: > > Sean-Paul Rees wrote in list.freebsd-stable: > > Is there a MMX enabled setiathome for us with non-3DNow! enhanced > > processors? > > No, MMX is completely useless for this kind of stuff, because > MMX does not support floating point operations. Sorry. > > However, I modified the FFT algorithm to optimize memory > throughput, at the cost of memory footprint (it needs about > 2 Mbyte more RAM). The speed increase is not as impressive > as with the 3DNow version, but it's still significant. > Here are some numbers: Thats a pretty big increase. I wish those seti folks would get a clue and build new clients for it. I'm assuming your patches generate the same results? Sean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 15:39:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 687D814FEE for ; Wed, 22 Dec 1999 15:39:30 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA15837 for freebsd-stable@FreeBSD.ORG; Wed, 22 Dec 1999 23:42:41 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA44786 for freebsd-stable@FreeBSD.ORG; Thu, 23 Dec 1999 00:16:31 +0100 (CET) (envelope-from wilko) Date: Thu, 23 Dec 1999 00:16:31 +0100 From: Wilko Bulte To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Message-ID: <19991223001631.B37471@yedi.iaf.nl> References: <199912222226.XAA00562@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912222226.XAA00562@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Wed, Dec 22, 1999 at 11:26:32PM +0100 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 22, 1999 at 11:26:32PM +0100, Oliver Fromme wrote: > Wilko Bulte wrote in list.freebsd-stable: > > On Mon, Dec 20, 1999 at 07:36:31PM +0100, Oliver Fromme wrote: > > > About 50%, that is, about 4.5 hours (instead of 9) on average > > > per work unit, on an Athlon-500. And I did only optimize the > > > FFT and didn't touch the rest. With a bit more effort, further > > > improvements would be certainly possible. > > > > Is this version on the setiathome server at Berkeley? > > No. I submitted my code to the Seti@home folks for review, > they said "great, thanks!" and I've never heard anything from > them again. :-( Blegh. NIH ? (not invented here) Or are they just to busy with their Corporate Primary Sponsors ? > > Related question: there does not seem to be a seti@home client for > > FreeBSD/alpha. Is there anybody working on this? > > Not that I'm aware of. I could compile a client, but the > problem is that (1) my Alpha's power supply is currently > broken, and (2) there is currently OpenBSD installed on > it... :-} > > Does FeeBSD/Alpha run reliably on an AXPpci33 with Quantum > Fireball (SCSI)? Yes, no problem. My NoName is currently living with Marcel Moolenaar for X-build testing etc. Running -current FreeBSD. Works great, albeit slowly (21066 CPUs are just not fast). If your NoName is the one with the broken PSU: any normal AT-style PSU will work. Since you like tuning 'iprobe' for the Alpha will be a nice tool. Wilko -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.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 22 15:39:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id EEAC5150B3 for ; Wed, 22 Dec 1999 15:39:34 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA15833; Wed, 22 Dec 1999 23:42:39 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA44804; Thu, 23 Dec 1999 00:19:43 +0100 (CET) (envelope-from wilko) Date: Thu, 23 Dec 1999 00:19:42 +0100 From: Wilko Bulte To: Bjoern Fischer Cc: stable@FreeBSD.ORG Subject: Re: /boot/loader fails to reset AMD K6-II FPU Message-ID: <19991223001940.C37471@yedi.iaf.nl> References: <19991222042320.A749@frolic.no-support.loc> <19991222204703.B833@yedi.iaf.nl> <19991222232741.A1344@frolic.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991222232741.A1344@frolic.no-support.loc>; from bfischer@Techfak.Uni-Bielefeld.DE on Wed, Dec 22, 1999 at 11:27:41PM +0100 X-OS: FreeBSD yedi.iaf.nl 3.3-STABLE FreeBSD 3.3-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 22, 1999 at 11:27:41PM +0100, Bjoern Fischer wrote: > On Wed, Dec 22, 1999 at 08:47:03PM +0100, Wilko Bulte wrote: > [...] > > > When I reboot the system from the /boot/loader > > > command line (with `reboot'), the system is > > > being resetted, the kernel loads and starts, > > > and when the FPU is being initialized the kernel > > > traps. > [...] > > Works fine on my Asus T2P4 with the same CPU: > > > > WKB ~>dmesg | grep -i amd > > CPU: AMD-K6(tm) 3D processor (399.81-MHz 586-class CPU) > > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > > AMD Features=0x80000800 > > > > But what date is your -stable? > > My stable is as fresh as Dec 20th (per CTM). I'll buildworld for the latest -stable (3.4-stable I guess ;-) and see what happens. Will take a while to do. > The problem occurs with an ASUS P5A-B and with another > noname Aladdin chipset board. The T2P4 is an Intel HX chipset. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.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 22 15:55:38 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 61554156A3 for ; Wed, 22 Dec 1999 15:55:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA01205; Wed, 22 Dec 1999 15:59:15 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912222359.PAA01205@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Bjoern Fischer Cc: stable@freebsd.org Subject: Re: /boot/loader fails to reset AMD K6-II FPU In-reply-to: Your message of "Wed, 22 Dec 1999 04:23:20 +0100." <19991222042320.A749@frolic.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Wed, 22 Dec 1999 15:59:14 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I believe I've already replied to this; it does indeed appear to be a = BIOS bug. The 'reboot' loader command simply re-invokes the bootstrap = interrupt, it doesn't attempt a complete system restart. It seems that = some BIOSsen don't deal with this very well. > this may be a BIOS/Mainboard issue, so I ask here > before filling out a PR. > = > When I reboot the system from the /boot/loader > command line (with `reboot'), the system is > being resetted, the kernel loads and starts, > and when the FPU is being initialized the kernel > traps. > = > Can anyone reproduce this? > = > At least this CPU seems to be affected: > = > CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) > Origin =FFAuthenticAMD" Id =F0x58c Stepping =F12 > Features=FF8021bf > AMD Features=FF80000800 > = > Bj=F6rn > = > -- = > -----BEGIN GEEK CODE BLOCK----- > GCS d--(+) s++: a- C+++(-) UB++++OSI++++$ P+++(-) L---(++) !E W- N+ o>+= > K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+= = > ------END GEEK CODE BLOCK------ > = > = > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > = -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 15:56:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id BCFCF15667; Wed, 22 Dec 1999 15:56:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA01261; Wed, 22 Dec 1999 16:00:33 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912230000.QAA01261@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Chris D. Faulhaber" Cc: Mike Smith , stable@freebsd.org Subject: Re: Mylex RAID controller driver update In-reply-to: Your message of "Tue, 21 Dec 1999 22:52:50 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Dec 1999 16:00:33 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 21 Dec 1999, Mike Smith wrote: > > > > > The third update to the Mylex PCI:SCSI RAID controller driver for > > FreeBSD-3.x-STABLE is now available at > > > > http://www.freebsd.org/~msmith/RAID/mylex/mlx-stable-991221.tar.gz > > > > According to the README: > > Copy the files mlx.c, mlxvar.h, mlxreg.h and mlxio.h into /sys/pci... > > however, mlxio.h is not present in the archive (and doesn't appear to be > required for any of the sources)...typo in README or missing file? Typo in README, thanks for spotting it. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 15:59:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 52290155A7 for ; Wed, 22 Dec 1999 15:59:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA01316; Wed, 22 Dec 1999 16:03:20 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912230003.QAA01316@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Cc: Ben WIlliams , freebsd-stable@FreeBSD.ORG Subject: Re: Re[4]: SOFTUPDATES In-reply-to: Your message of "Tue, 21 Dec 1999 21:09:43 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 22 Dec 1999 16:03:20 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 21 Dec 1999, Ben WIlliams wrote: > > > Tuesday, December 21, 1999 > > So that's a "Yes you need [br]oot & fixit"? (I actually tried it > > with wd0s1a too and got the same effect.) I'll just take my disks next > > time I go up to see the router/webserver/mailserver(pop&smtp)/ > > pain-in-my-ass box and be done with it. > > > > Thanks for the input. > > > > No, you just need to use the correct device. I just did a server today, > I booted single user and turned softupdates on for ALL filesystems, > including root. Just in case nobody has noticed, you can pass a mountpoint as an argument to tunefs and it will (mostly) correctly guess the device (by reading /etc/fstab). ie. one says tunefs -n enable /usr rather than guessing at which device to use. Much more robust. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 16:24:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 001D314DB8 for ; Wed, 22 Dec 1999 16:24:19 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA01709 for ; Wed, 22 Dec 1999 16:28:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912230028.QAA01709@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-stable@FreeBSD.ORG Subject: FreeBSD/Alpha (was Re: AMD 3DNow instructions on FreeBSD ) In-reply-to: Your message of "Wed, 22 Dec 1999 23:26:32 +0100." <199912222226.XAA00562@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Wed, 22 Dec 1999 16:28:35 -0800 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Does FeeBSD/Alpha run reliably on an AXPpci33 with Quantum > Fireball (SCSI)? Yes; we do test installs onto one (although I think it has a 2GB Empire = in it at the moment, the furball was too small). -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 17: 7:15 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ulstu.ru (ns.ulstu.ru [62.76.34.36]) by hub.freebsd.org (Postfix) with ESMTP id D6071155A7 for ; Wed, 22 Dec 1999 17:06:59 -0800 (PST) (envelope-from vlad@high.net.ru) Received: from siemens.ulstu.ru (siemens.ulstu.ru [62.76.34.44]) by mail.ulstu.ru (8.8.5-MVC-230198/8.8.7) with ESMTP id EAA62662 for ; Thu, 23 Dec 1999 04:06:53 +0300 (MSK) (envelope-from vlad@high.net.ru) Received: from hq.spc.high (ip241.link-ul.ru [195.151.42.241]) by siemens.ulstu.ru (Postfix) with ESMTP id AAAED17422 for ; Thu, 23 Dec 1999 04:06:49 +0300 (MSK) Received: by hq.spc.high (Postfix, from userid 1000) id 1AC15440; Thu, 23 Dec 1999 04:09:49 +0300 (MSK) Date: Thu, 23 Dec 1999 04:09:49 +0300 From: Vlad Skvortsov To: freebsd-stable@freebsd.org Subject: /bin/test broken ? Message-ID: <19991223040949.D4940@high.net.ru> Mail-Followup-To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Seems like /bin/test is broken after cvsup on Dec 16: $ /bin/test 1 -ne 0 ] [: ]: unexpected operator -- Vlad Skvortsov, vss@ulstu.ru, vlad@high.net.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 17:44:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 6B8A7156CB for ; Wed, 22 Dec 1999 17:44:23 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40332>; Thu, 23 Dec 1999 12:35:16 +1100 Content-return: prohibited Date: Thu, 23 Dec 1999 12:44:07 +1100 From: Peter Jeremy Subject: Re: /bin/test broken ? In-reply-to: <19991223040949.D4940@high.net.ru>; from vlad@high.net.ru on Thu, Dec 23, 1999 at 12:09:49PM +1100 To: Vlad Skvortsov Cc: freebsd-stable@FreeBSD.ORG Message-Id: <99Dec23.123516est.40332@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <19991223040949.D4940@high.net.ru> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-23 12:09:49 +1100, Vlad Skvortsov wrote: > Seems like /bin/test is broken after cvsup on Dec 16: > > $ /bin/test 1 -ne 0 ] > [: ]: unexpected operator What behaviour were you expecting? That command should have been expressed as either: $ /bin/test 1 -ne 0 or $ [ 1 -ne 0 ] Mixing `test' and `]' is not allowed, so producing an error message is the correct response. That said, the error message should have been: test: ]: unexpected operator and it is not clear why you are getting `[' reported as the program name. As far as I can tell, nothing related to test or errx(3) has been updated recently. (I'm not actually running -stable, so I can't confirm the behaviour). Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 18:34:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 57DAE14EC3 for ; Wed, 22 Dec 1999 18:34:29 -0800 (PST) (envelope-from randy@psg.com) Received: from randy by rip.psg.com with local (Exim 3.12 #1) id 120y58-000JuB-00; Wed, 22 Dec 1999 18:34:22 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: stenn@whimsy.udel.edu Cc: FreeBSD Stable Subject: Re: ntpd coring again References: <16610.945886070@pcnbs.pfcs.com> Message-Id: Date: Wed, 22 Dec 1999 18:34:22 -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Can you please download the latest (4.0.98h, as I recall) NTP code from > either: > > or > > run: > % configure > % make > # ntpd/ntpd (assuming ntpd is not currently running) did all that, or the equivalent (ran it through normal port sans patch). > and then do the gdb backtrace from there? can't do that because it no longer seems to core! randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 18:42: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.greatbasin.net (mail.greatbasin.net [207.228.35.39]) by hub.freebsd.org (Postfix) with ESMTP id 5F38B1574B for ; Wed, 22 Dec 1999 18:42:00 -0800 (PST) (envelope-from dan@jgl.reno.nv.us) Received: from jgl.reno.nv.us (rno-max8-62.gbis.net [207.228.62.62]) by mail.greatbasin.net (8.9.3/8.9.3) with ESMTP id SAA03654; Wed, 22 Dec 1999 18:41:45 -0800 (PST) Received: from danco (danco.home [10.0.0.2]) by jgl.reno.nv.us (8.9.3/8.9.3) with SMTP id SAA12930; Wed, 22 Dec 1999 18:41:41 -0800 (PST) (envelope-from dan@jgl.reno.nv.us) Message-ID: <012301bf4cef$3fde6f20$0200000a@danco.home> From: "Dan O'Connor" To: "Mark Ovens" , Subject: Re: SOFTUPDATES Date: Wed, 22 Dec 1999 18:28:03 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Did ``boot -s'' and ran tunefs but got an error: > >Enter full pathname of shell or RETURN for /bin/sh: ># pwd >/ ># tunefs -n enable /usr >tunefs: soft updates set >tunefs: /dev/rda1s1e: reload: Invalid argument > >What caused this? There's no reference in the manpage. I've seen it on some IDE drives, and not on some other IDE drives...in each case softupdates was indeed enabled. I've heard from others on the list that the error message is harmless, although no one said exactly what was going on. --Dan ** The thing I like most about Windows 98 is... ** You can download FreeBSD with it! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 19: 6:48 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.7]) by hub.freebsd.org (Postfix) with ESMTP id 41DA31557E for ; Wed, 22 Dec 1999 19:06:46 -0800 (PST) (envelope-from tom@uniserve.com) Received: from shell.uniserve.ca ([204.244.186.218]) by mail2.uniserve.com with smtp (Exim 3.03 #4) id 120yZ9-0008CM-00; Wed, 22 Dec 1999 19:05:24 -0800 Date: Wed, 22 Dec 1999 19:05:18 -0800 (PST) From: Tom X-Sender: tom@shell.uniserve.ca To: Dan O'Connor Cc: Mark Ovens , freebsd-stable@FreeBSD.ORG Subject: Re: SOFTUPDATES In-Reply-To: <012301bf4cef$3fde6f20$0200000a@danco.home> 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, 22 Dec 1999, Dan O'Connor wrote: > >Did ``boot -s'' and ran tunefs but got an error: > > > >Enter full pathname of shell or RETURN for /bin/sh: > ># pwd > >/ > ># tunefs -n enable /usr > >tunefs: soft updates set > >tunefs: /dev/rda1s1e: reload: Invalid argument > > > >What caused this? There's no reference in the manpage. > > I've seen it on some IDE drives, and not on some other IDE drives...in each > case softupdates was indeed enabled. It happens if the filesystem is not currently mounted read-only. It is try to reload the incore (r*) device, but it was never loaded to begin with. When you boot single user, only "/" is mounted, so all other filesystems will give you that warning. So it is completely harmless. > --Dan 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 22 20: 5:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from workhorse.iMach.com (workhorse.iMach.com [206.127.77.89]) by hub.freebsd.org (Postfix) with ESMTP id 6B8CD14DD3 for ; Wed, 22 Dec 1999 20:05:48 -0800 (PST) (envelope-from forrestc@workhorse.iMach.com) Received: from localhost (forrestc@localhost) by workhorse.iMach.com (8.8.8/8.8.8) with SMTP id VAA15962 for ; Wed, 22 Dec 1999 21:03:29 -0700 (MST) Date: Wed, 22 Dec 1999 21:03:28 -0700 (MST) From: "Forrest W. Christian" To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD In-Reply-To: <199912222253.XAA16064@dorifer.heim3.tu-clausthal.de> 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, 22 Dec 1999, Oliver Fromme wrote: > I'm still waiting for a response from the Seti@home folks. > They have all the code, but they seem to ignore it. They're probably busy trying to keep their non-FreeBSD boxen up and alive (Sorry couldn't resist). - Forrest W. Christian (forrestc@imach.com) KD7EHZ ---------------------------------------------------------------------- iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com Solutions for your high-tech problems. (406)-442-6648 ---------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 21:26:28 1999 Delivered-To: freebsd-stable@freebsd.org Received: from corinth.bossig.com (corinth.bossig.com [208.26.239.66]) by hub.freebsd.org (Postfix) with ESMTP id 5CB7B155C7 for ; Wed, 22 Dec 1999 21:26:24 -0800 (PST) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn2124.bossig.com [208.26.242.124]) by corinth.bossig.com (Rockliffe SMTPRA 3.4.5) with ESMTP id ; Wed, 22 Dec 1999 21:33:16 -0800 Message-ID: <3861B297.3D7375F9@3-cities.com> Date: Wed, 22 Dec 1999 21:26:47 -0800 From: Kent Stewart Organization: Columbia Basin Virtual Community Project X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Forrest W. Christian" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Forrest W. Christian" wrote: > > On Wed, 22 Dec 1999, Oliver Fromme wrote: > > > I'm still waiting for a response from the Seti@home folks. > > They have all the code, but they seem to ignore it. > > They're probably busy trying to keep their non-FreeBSD boxen up and alive > (Sorry couldn't resist). They are probably trying to run the same code on all of the systems. That includes other machines such as HP's, SGI's, Sun's, and etc. I wouldn't accept coding for 3DNow unless it ran on all of the systems. Kent > > - Forrest W. Christian (forrestc@imach.com) KD7EHZ > ---------------------------------------------------------------------- > iMach, Ltd., P.O. Box 5749, Helena, MT 59604 http://www.imach.com > Solutions for your high-tech problems. (406)-442-6648 > ---------------------------------------------------------------------- > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html FreeBSD News http://daily.daemonnews.org/ SETI(Search for Extraterrestrial Intelligence) @ HOME http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 21:46:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.nyct.net (bsd4.nyct.net [204.141.86.6]) by hub.freebsd.org (Postfix) with ESMTP id C025C1561F for ; Wed, 22 Dec 1999 21:46:17 -0800 (PST) (envelope-from efutch@nyct.net) Received: from bsd1.nyct.net (efutch@bsd1.nyct.net [204.141.86.3]) by mail.nyct.net (8.8.8/8.8.7) with ESMTP id AAA18504; Thu, 23 Dec 1999 00:45:41 -0500 (EST) (envelope-from efutch@nyct.net) Date: Thu, 23 Dec 1999 00:45:40 -0500 (EST) From: "Eric D. Futch" To: Peter Jeremy Cc: Vlad Skvortsov , freebsd-stable@FreeBSD.ORG Subject: Re: /bin/test broken ? In-Reply-To: <99Dec23.123516est.40332@border.alcanet.com.au> 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 -stable as of Wed Dec 22 01:48:17 EST 1999 dosen't seem to have this problem. % /bin/test 1 -ne 0 ] test: ]: unexpected operator -- Eric Futch New York Connect.Net, Ltd. efutch@nyct.net Technical Support Staff http://www.nyct.net (212) 293-2620 "Bringing New York The Internet Access It Deserves" On Thu, 23 Dec 1999, Peter Jeremy wrote: On 1999-Dec-23 12:09:49 +1100, Vlad Skvortsov wrote: > Seems like /bin/test is broken after cvsup on Dec 16: > > $ /bin/test 1 -ne 0 ] > [: ]: unexpected operator What behaviour were you expecting? That command should have been expressed as either: $ /bin/test 1 -ne 0 or $ [ 1 -ne 0 ] Mixing `test' and `]' is not allowed, so producing an error message is the correct response. That said, the error message should have been: test: ]: unexpected operator and it is not clear why you are getting `[' reported as the program name. As far as I can tell, nothing related to test or errx(3) has been updated recently. (I'm not actually running -stable, so I can't confirm the behaviour). Peter 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 22 22:12: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.greatbasin.net (mail.greatbasin.net [207.228.35.39]) by hub.freebsd.org (Postfix) with ESMTP id D09E614F3F for ; Wed, 22 Dec 1999 22:12:03 -0800 (PST) (envelope-from dan@jgl.reno.nv.us) Received: from jgl.reno.nv.us (rno-max8-62.gbis.net [207.228.62.62]) by mail.greatbasin.net (8.9.3/8.9.3) with ESMTP id WAA11730; Wed, 22 Dec 1999 22:12:02 -0800 (PST) Received: from danco (danco.home [10.0.0.2]) by jgl.reno.nv.us (8.9.3/8.9.3) with SMTP id WAA13393; Wed, 22 Dec 1999 22:11:59 -0800 (PST) (envelope-from dan@jgl.reno.nv.us) Message-ID: <04f501bf4d0c$a0590c80$0200000a@danco.home> From: "Dan O'Connor" To: "Tom" Cc: "Mark Ovens" , Subject: Re: SOFTUPDATES Date: Wed, 22 Dec 1999 22:11:56 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3155.0 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3155.0 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It happens if the filesystem is not currently mounted read-only. It is >try to reload the incore (r*) device, but it was never loaded to begin >with. When you boot single user, only "/" is mounted, so all other >filesystems will give you that warning. > > So it is completely harmless. Ahhhh...That makes complete sense! Thanks for clearing up that little mystery, Tom! --Dan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Wed Dec 22 22:39: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id B2F5A14E26 for ; Wed, 22 Dec 1999 22:39:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA11558; Wed, 22 Dec 1999 22:39:01 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Vivek Khera Cc: freebsd-stable@FreeBSD.ORG Subject: Re: handbook procedure for upgrading via cvsup confusion In-reply-to: Your message of "Tue, 21 Dec 1999 13:48:15 EST." <14431.52079.94710.758347@onceler.kcilink.com> Date: Wed, 22 Dec 1999 22:38:59 -0800 Message-ID: <11554.945931139@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Secondly, the part about updating /stand... doing as the handbook > suggests "make all install" in release/sysintall only updates the > sysinstall program; it doesn't update all the hard links to it. Also, > the file size is greatly reduced, leading me to believe that it is not > a proper upgrade of that directory. What is the proper way to upgrade > the /stand directory and the subdirectories within it (the help and > TXT files)? You are correct, it is not an "equivalent" upgrade but it is the only available upgrade. :) It'll basically just give you the configuration tool, not the stand-alone installer which is a crunched image. If it weren't so kludge, I'd have sysinstall's install procedure remove all the links. :) - 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 23 0:54:13 1999 Delivered-To: freebsd-stable@freebsd.org Received: from postoffice.aims.com.au (advanc2.lnk.telstra.net [139.130.119.73]) by hub.freebsd.org (Postfix) with ESMTP id 3280514F86 for ; Thu, 23 Dec 1999 00:53:30 -0800 (PST) (envelope-from Chris@aims.com.au) Received: from postoffice.aims.com.au (nts-ts1.aims.private [192.168.0.2]) by postoffice.aims.com.au (8.9.3/8.9.3) with ESMTP id TAA86477 for ; Thu, 23 Dec 1999 19:53:04 +1100 (EST) (envelope-from Chris@aims.com.au) Received: from nts-ts1 by aims.com.au with SMTP (MDaemon.v2.8.7.0.R) for ; Thu, 23 Dec 1999 19:53:05 +1100 From: "Chris Knight" To: Subject: RE: NTFS in 3.4-R, will it work with Windows 2000? Date: Thu, 23 Dec 1999 19:53:03 +1100 Message-ID: <002401bf4d23$2058ae20$0200a8c0@nts-ts1.aims.private> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Importance: Normal X-MDaemon-Deliver-To: freebsd-stable@FreeBSD.ORG X-Return-Path: Chris@aims.com.au Reply-To: chris@aims.com.au Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy, I've just installed 3.4R in a dual-boot role with Windows 2000 Pro RC3. I was able to successfully mount and read files from my NTFS partition. Regards, Chris Knight Systems Administrator AIMS Independent Computer Professionals Tel: +61 3 6334 6664 Fax: +61 3 6331 7032 Mob: +61 419 528 795 Web: http://www.aims.com.au > -----Original Message----- > From: owner-freebsd-stable@FreeBSD.ORG > [mailto:owner-freebsd-stable@FreeBSD.ORG]On Behalf Of Donald Burr > Sent: Wednesday, 22 December 1999 16:54 > To: FreeBSD Questions > Cc: freebsd-stable@FreeBSD.ORG > Subject: NTFS in 3.4-R, will it work with Windows 2000? > > > Will the NTFS support in 3.4-RELEASE work with Windows 2000 > filesystems? > Win2K uses NTFS, I think, so it probably will work, but i > thought i had > better ask before I do something potentially destructive to > my data. :) > Thanks in advance, Donald > -- > Donald Burr Resistance is Futile! | FreeBSD: The > WWW: http://www.borg-cube.com/ ICQ: UIN#16997506 | Power to > Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | > Serve! http:// > Phone: (805) 957-9666 FAX: (800) 492-5954 | > www.freebsd.org/ > > > > 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 23 3:51:18 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id E9FA714F22 for ; Thu, 23 Dec 1999 03:51:15 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id MAA07789 for freebsd-stable@FreeBSD.ORG; Thu, 23 Dec 1999 12:51:14 +0100 (CET) (envelope-from olli) Date: Thu, 23 Dec 1999 12:51:14 +0100 (CET) From: Oliver Fromme Message-Id: <199912231151.MAA07789@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sean-Paul Rees wrote in list.freebsd-stable: > Thats a pretty big increase. I wish those seti folks would get a clue > and build new clients for it. I'm assuming your patches generate the > same results? The computation results differ in the least significant bit, which is normal and expected -- different computations lead to different round-off errors. In fact, I believe that my implementation is more accurate than the original, because it involves fewer computational steps, reducing round-off errors. Of course, my code finds exactly the same spikes and gaussians as the original program. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 3:57:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 4464E14A04 for ; Thu, 23 Dec 1999 03:57:31 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id MAA11441 for freebsd-stable@FreeBSD.ORG; Thu, 23 Dec 1999 12:57:29 +0100 (CET) (envelope-from olli) Date: Thu, 23 Dec 1999 12:57:29 +0100 (CET) From: Oliver Fromme Message-Id: <199912231157.MAA11441@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wilko Bulte wrote in list.freebsd-stable: > On Wed, Dec 22, 1999 at 11:26:32PM +0100, Oliver Fromme wrote: > > Does FeeBSD/Alpha run reliably on an AXPpci33 with Quantum > > Fireball (SCSI)? > > Yes, no problem. My NoName is currently living with Marcel Moolenaar > for X-build testing etc. Running -current FreeBSD. Works great, albeit > slowly (21066 CPUs are just not fast). OK, thanks. I know that it's not fast. :-) > If your NoName is the one with the broken PSU: any normal AT-style PSU > will work. I don't have a "NoName" box. I bought the AXPpci33 mainboard + 21066-166 and put it into a standard AT midi tower. Spent $50 for the thing... Yes, I know, it's not worth that much, but I just wanted to play around with AXP stuff. A few days ago, it suddenly performed a spontaneous shutdown and played dead. The fuse in the power supply is OK, but even the light in the power switch (which is on the primary side of the transformer) is off. Strange. Well, I'll probably try to get a cheap used power supply for this box. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 4: 0:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id 245FF14F22 for ; Thu, 23 Dec 1999 04:00:09 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id NAA12842 for freebsd-stable@FreeBSD.ORG; Thu, 23 Dec 1999 13:00:08 +0100 (CET) (envelope-from olli) Date: Thu, 23 Dec 1999 13:00:08 +0100 (CET) From: Oliver Fromme Message-Id: <199912231200.NAA12842@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kent Stewart wrote in list.freebsd-stable: > > On Wed, 22 Dec 1999, Oliver Fromme wrote: > > > I'm still waiting for a response from the Seti@home folks. > > > They have all the code, but they seem to ignore it. > > They are probably trying to run the same code on all of the systems. > That includes other machines such as HP's, SGI's, Sun's, and etc. I > wouldn't accept coding for 3DNow unless it ran on all of the systems. Even if a significant part of their supporters could compute results a lot faster? Well, if that's true, they could at least say so. I think the NIH theory sounds more realistic. Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 5: 4:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (Postfix) with ESMTP id 1479514EA9 for ; Thu, 23 Dec 1999 05:04:11 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with ESMTP id OAA19318 for ; Thu, 23 Dec 1999 14:03:55 +0100 (MET) Date: Thu, 23 Dec 1999 14:03:51 +0100 (MET) From: Marcin Cieslak To: freebsd-stable@FreeBSD.ORG Subject: Re: /bin/test broken ? 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, 23 Dec 1999, Eric D. Futch wrote: > -stable as of Wed Dec 22 01:48:17 EST 1999 dosen't seem to have this > problem. > > % /bin/test 1 -ne 0 ] > test: ]: unexpected operator Recent -stable: $ /bin/test 1 -ne 0 ] test: syntax error $ [ 1 -ne 0 ] $ but on Solaris 2.5 in both sh and ksh: $ /bin/test 1 -ne 0 ] $ [ 1 -ne 0 ] $ What's _the_ standard? -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 5:58:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from vexpert.dbai.tuwien.ac.at (vexpert.dbai.tuwien.ac.at [128.130.111.12]) by hub.freebsd.org (Postfix) with ESMTP id C477E14DC1 for ; Thu, 23 Dec 1999 05:58:37 -0800 (PST) (envelope-from pfeifer@dbai.tuwien.ac.at) Received: from alphard (alphard [128.130.111.37]) by vexpert.dbai.tuwien.ac.at (8.9.1/8.9.1) with ESMTP id OAA15976; Thu, 23 Dec 1999 14:57:58 +0100 (MET) Date: Thu, 23 Dec 1999 14:57:56 +0100 (MET) From: Gerald Pfeifer To: Marcin Cieslak Cc: freebsd-stable@freebsd.org Subject: Re: /bin/test broken ? 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, 23 Dec 1999, Marcin Cieslak wrote: > Recent -stable: > > $ /bin/test 1 -ne 0 ] > test: syntax error > $ [ 1 -ne 0 ] > $ > > but on Solaris 2.5 in both sh and ksh: > > $ /bin/test 1 -ne 0 ] > $ [ 1 -ne 0 ] > $ SuSE Linux 6.3: sh-2.03$ /usr/bin/test 1 -ne 0 ] /usr/bin/test: too many arguments > What's _the_ standard? You would have to consult POSIX or whatever, I guess, but clearly the first variant is not portable (in practice) so one should refrain from using it anyway. http://www.UNIX-systems.org/ has a lot on standards, by the way. Gerald -- Gerald "Jerry" 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 Thu Dec 23 5:59:47 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id A349214F86 for ; Thu, 23 Dec 1999 05:59:45 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991223135945.CLJR9446.mail.rdc1.ct.home.com@home.com> for ; Thu, 23 Dec 1999 05:59:45 -0800 Message-ID: <38622ACA.F0F680A9@home.com> Date: Thu, 23 Dec 1999 08:59:38 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: CDROM mount problems! Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG From day one (several years now) I have always had trouble with cdroms in FreeBSD. Everytime I try to mount one(at least 95% of the time) they fail to mount. For instance I have the new Corel Linux(eyuk!) in the drive now a # mount /dev/acd0a /cdrom yields a mount: /dev/acd0a on /cdrom: incorrect super block error. No matter what machine I use it's the same. I have the cdrom set up the same as the GENERIC conf script. Have I missed something. It's time to fix this once and for all. Could it be my drives? There both old 2x and 5x drives. This ones a Creative CD620E the other one a Sony CDU-55. I've been through the handbook and faq and have pretty much given up on it. I just mount a cdrom via the network on a different machine when I need it. Regards, -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.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 23 6: 7:49 1999 Delivered-To: freebsd-stable@freebsd.org Received: from cs.Technion.AC.IL (csa.cs.technion.ac.il [132.68.32.1]) by hub.freebsd.org (Postfix) with ESMTP id DE7611571E; Thu, 23 Dec 1999 06:07:32 -0800 (PST) (envelope-from nadav@cs.technion.ac.il) Received: from csd.cs.technion.ac.il (csd.cs.technion.ac.il [132.68.32.8]) by cs.Technion.AC.IL (8.9.0/8.9.0) with ESMTP id QAA28746; Thu, 23 Dec 1999 16:10:03 +0200 (IST) Received: from localhost (nadav@localhost) by csd.cs.technion.ac.il (8.9.3/8.9.0) with SMTP id QAA07852; Thu, 23 Dec 1999 16:10:01 +0200 (IST) X-Authentication-Warning: csd.cs.technion.ac.il: nadav owned process doing -bs Date: Thu, 23 Dec 1999 16:10:01 +0200 (IST) From: Nadav Eiron X-Sender: nadav@csd To: tsikora@powerusersbbs.com Cc: questions@freebsd.org Subject: Re: CDROM mount problems! In-Reply-To: <38622ACA.F0F680A9@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, 23 Dec 1999, Ted Sikora wrote: > >From day one (several years now) I have always had trouble with cdroms > in FreeBSD. Everytime I try to mount one(at least 95% of the time) they > fail to mount. For instance I have the new Corel Linux(eyuk!) in the > drive now a # mount /dev/acd0a /cdrom yields a mount: /dev/acd0a on > /cdrom: incorrect super block error. This is better suited to -questions (redirected). > No matter what machine I use it's the same. I have the cdrom set up the > same as the GENERIC conf script. Have I missed something. Yes! The type of the filesystem on the CDROM! CDROMs are usually formatted in ISO-9660. You asked to mount a ufs filesystem. The error you got simply indicates that mount didn't find a ufs system on the media. No wander. Try adding -t cd9660 to the mount command: mount -t cd9660 /dev/acd0c /cdrom > It's time to fix this once and for all. Could it be my drives? Indeed. To fix this once and for all, add an appropriate line to /etc/fstab. Then mount will know the type of the filesystem it should expect automagicaly. man 5 fstab. > There both old 2x and 5x drives. This ones a Creative CD620E the other > one a Sony CDU-55. I've been through the handbook and faq and have Well, this is a FAQ! A search for your error message on www.freebsd.org turned out this page: http://www.freebsd.org/FAQ/troubleshoot.html > pretty much given up on it. I just mount a cdrom via the network on a > different machine when I need it. > > Regards, > -- > Ted Sikora > Jtl Development Group > tsikora@powerusersbbs.com > > Nadav To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 6:20:10 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 40C21155AD for ; Thu, 23 Dec 1999 06:19:57 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991223141956.CPZY9446.mail.rdc1.ct.home.com@home.com>; Thu, 23 Dec 1999 06:19:56 -0800 Message-ID: <38622F86.4FEB5F4D@home.com> Date: Thu, 23 Dec 1999 09:19:50 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Nadav Eiron Cc: "freebsd-stable@FreeBSD.ORG" Subject: Re: CDROM mount problems! References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nadav Eiron wrote: > > On Thu, 23 Dec 1999, Ted Sikora wrote: > > > >From day one (several years now) I have always had trouble with cdroms > > in FreeBSD. Everytime I try to mount one(at least 95% of the time) they > > fail to mount. For instance I have the new Corel Linux(eyuk!) in the > > drive now a # mount /dev/acd0a /cdrom yields a mount: /dev/acd0a on > > /cdrom: incorrect super block error. > > This is better suited to -questions (redirected). I'll try there, thanks. > > > No matter what machine I use it's the same. I have the cdrom set up the > > same as the GENERIC conf script. Have I missed something. > > Yes! The type of the filesystem on the CDROM! CDROMs are usually formatted > in ISO-9660. You asked to mount a ufs filesystem. The error you got simply > indicates that mount didn't find a ufs system on the media. No wander. Try > adding -t cd9660 to the mount command: > > mount -t cd9660 /dev/acd0c /cdrom Same error! > > > It's time to fix this once and for all. Could it be my drives? > > Indeed. To fix this once and for all, add an appropriate line to > /etc/fstab. Then mount will know the type of the filesystem it should > expect automagicaly. man 5 fstab. I have: /dev/acd0c /cdrom cd9660 ro,noauto 0 0 > > There both old 2x and 5x drives. This ones a Creative CD620E the other > > one a Sony CDU-55. I've been through the handbook and faq and have > > Well, this is a FAQ! A search for your error message on www.freebsd.org > turned out this page: http://www.freebsd.org/FAQ/troubleshoot.html I'll look there. > > > pretty much given up on it. I just mount a cdrom via the network on a > > different machine when I need it. > > -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.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 23 6:45:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (Postfix) with ESMTP id D0AE514D89 for ; Thu, 23 Dec 1999 06:45:19 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id PAA23056 for freebsd-stable@FreeBSD.ORG; Thu, 23 Dec 1999 15:45:18 +0100 (CET) (envelope-from olli) Date: Thu, 23 Dec 1999 15:45:18 +0100 (CET) From: Oliver Fromme Message-Id: <199912231445.PAA23056@dorifer.heim3.tu-clausthal.de> To: freebsd-stable@FreeBSD.ORG Subject: Problem with ThunderLAN NIC driver Organization: Administration TU Clausthal Reply-To: freebsd-stable@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have a problem with a ThunderLAN network interface card under FreeBSD: It seems like only 10 Mbps is supported, although the card can do 100 Mbps as well. The machine is currently running 3.4-stable, but I also tried a 4.0-current snapshot some time ago. pciconf -l says: tl0@pci0:10:0: class=0x020000 card=0x00000000 chip=0x0012108d rev=0x01 hdr=0x00 This is dmesg from a verbose boot: tl0: irq 10 at device 10.0 on pci0 tl0: Ethernet address: 00:00:24:24:ff:dc tl0: looking for phy at addr 0 tl0: status: 0 [... this repeats for addr 0 through 1e ...] tl0: looking for phy at addr 1e tl0: status: 0 tl0: looking for phy at addr 1f tl0: status: 1809 tl0: phy at mii address 31 tl0: 10Mbps full duplex autonegotiating tl0: autoneg not complete, link status good (half-duplex, 10Mbps) bpf: tl0 attached "Link status good" is certainly a lie. It cannot be good, because the card is connected to a 100 Mbps hub which cannot do 10 Mbps at all. ifconfig says: tl0: flags=8802 mtu 1500 ether 00:00:24:24:ff:dc media: autoselect (10baseT/UTP ) supported media: 10baseT/UTP autoselect 10base5/AUI 10baseT/UTP 10baseT/UTP Needless to say, I can't get it to work at 100 Mbps. It does work fine at 10 Mbps when I connect it to a different hub. Reading the tl driver docs and source, it seems like the ThunderLan chip has an internal PHY that supports 10 Mbps, and uses an external PHY for 100 Mbps. And indeed, there's another chip on the card beside the ThunderLan chip, which I guess is the 100 Mbps PHY. FreeBSD's tl driver doesn't seem to recognize it for some reason. Any ideas how to proceed? Maybe I'm doing something wrong? Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 7: 8: 7 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 602C314F93 for ; Thu, 23 Dec 1999 07:08:05 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991223150804.DCGG9446.mail.rdc1.ct.home.com@home.com>; Thu, 23 Dec 1999 07:08:04 -0800 Message-ID: <38623ACE.6042C690@home.com> Date: Thu, 23 Dec 1999 10:07:58 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: Glen Foster , "freebsd-stable@FreeBSD.ORG" Subject: Re: CDROM mount problems! References: <199912231414.JAA53041@rr.gfoster.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Glen Foster wrote: > > If your CD has a non-UFS file system on it, you have to tell mount > that this is the case, you also should specify that the media is > read-only, e.g.: > > # mount -t cd9660 -o rdonly /dev/acd0a /cdrom It worked! Strange ..without the -o rdonly flag it would not. Maybe I should just invest in some newer drives. I'm starting to suspect the drives may be too old. 3 out of 5 just worked in a 5 disk set. Leads me to believe the drive probably needs cleaning or replacing. > > for ISO 9660 CD-ROMs. > > If you put a line in /etc/fstab like: > > /dev/acd0a /cdrom cd9660 ro,noauto 0 0 > > a simple: > > # mount /cdrom > > will mount your disk. > > Most data CD's have ISO file systems but I have occasionally seen UFS, > Mac, and FAT file systems. > > See the man pages for mount and mount_cd9660. > > >Date: Thu, 23 Dec 1999 08:59:38 -0500 > >From: Ted Sikora > > > >>From day one (several years now) I have always had trouble with cdroms > >in FreeBSD. Everytime I try to mount one(at least 95% of the time) they > >fail to mount. For instance I have the new Corel Linux(eyuk!) in the > >drive now a # mount /dev/acd0a /cdrom yields a mount: /dev/acd0a on > >/cdrom: incorrect super block error. > >No matter what machine I use it's the same. I have the cdrom set up the > >same as the GENERIC conf script. Have I missed something. > >It's time to fix this once and for all. Could it be my drives? > >There both old 2x and 5x drives. This ones a Creative CD620E the other > >one a Sony CDU-55. I've been through the handbook and faq and have > >pretty much given up on it. I just mount a cdrom via the network on a > >different machine when I need it. -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.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 23 7:53:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 50EA01507A for ; Thu, 23 Dec 1999 07:53:33 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991223155332.DMVQ9446.mail.rdc1.ct.home.com@home.com> for ; Thu, 23 Dec 1999 07:53:32 -0800 Message-ID: <38624577.4E3EDC8A@home.com> Date: Thu, 23 Dec 1999 10:53:27 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.3.34 i686) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: "freebsd-stable@FreeBSD.ORG" Subject: Re: CDROM mount problems! References: <199912231414.JAA53041@rr.gfoster.com> <38623ACE.6042C690@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ted Sikora wrote: > > Glen Foster wrote: > > > > If your CD has a non-UFS file system on it, you have to tell mount > > that this is the case, you also should specify that the media is > > read-only, e.g.: > > > > # mount -t cd9660 -o rdonly /dev/acd0a /cdrom > It worked! Strange ..without the -o rdonly flag it would not. Maybe I > should just invest in some newer drives. I'm starting to suspect the > drives may be too old. 3 out of 5 just worked in a 5 disk set. Leads me > to believe the drive probably needs cleaning or replacing. > > > Under Linux however the cdroms work perfectly always have. The same machine booted to Slackware the same disks all mount perfectly. This is what leads me to believe there has been a problem in FreeBSD's code. > > for ISO 9660 CD-ROMs. > > > > If you put a line in /etc/fstab like: > > > > /dev/acd0a /cdrom cd9660 ro,noauto 0 0 > > > > a simple: > > > > # mount /cdrom > > > > will mount your disk. > > > > Most data CD's have ISO file systems but I have occasionally seen UFS, > > Mac, and FAT file systems. > > > > See the man pages for mount and mount_cd9660. > > > > >Date: Thu, 23 Dec 1999 08:59:38 -0500 > > >From: Ted Sikora > > > -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.com http://powerusersbbs.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 23 8: 1:43 1999 Delivered-To: freebsd-stable@freebsd.org Received: from jason02.u.washington.edu (jason02.u.washington.edu [140.142.76.8]) by hub.freebsd.org (Postfix) with ESMTP id E8EB0158B9 for ; Thu, 23 Dec 1999 08:01:28 -0800 (PST) (envelope-from kraemer@u.washington.edu) Received: from mead2.u.washington.edu (kraemer@mead2.u.washington.edu [140.142.12.164]) by jason02.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA29442 for ; Thu, 23 Dec 1999 08:01:27 -0800 Received: from localhost (kraemer@localhost) by mead2.u.washington.edu (8.9.3+UW99.09/8.9.3+UW99.09) with ESMTP id IAA52062 for ; Thu, 23 Dec 1999 08:01:26 -0800 Date: Thu, 23 Dec 1999 08:01:26 -0800 (PST) From: Brian Kraemer To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD In-Reply-To: <199912222226.XAA00562@dorifer.heim3.tu-clausthal.de> 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, 22 Dec 1999, Oliver Fromme wrote: > No. I submitted my code to the Seti@home folks for review, > they said "great, thanks!" and I've never heard anything from > them again. :-( Actually, I think I read somewhere once that the SETI@home people are worried that if they made optimizations to their clients, their servers and staff would not be able to keep up with all the data pouring in at a faster rate. They never really expected the kind of turnout they received in the first place. -Brian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 9:35:46 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dozer.skynet.be (dozer.skynet.be [195.238.2.36]) by hub.freebsd.org (Postfix) with ESMTP id 190CF15032 for ; Thu, 23 Dec 1999 09:35:44 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by dozer.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id SAA17616; Thu, 23 Dec 1999 18:35:33 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <38623ACE.6042C690@home.com> References: <199912231414.JAA53041@rr.gfoster.com> <38623ACE.6042C690@home.com> Date: Thu, 23 Dec 1999 18:34:01 +0100 To: tsikora@powerusersbbs.com, Glen Foster , "freebsd-stable@FreeBSD.ORG" From: Brad Knowles Subject: Re: CDROM mount problems! Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:07 AM -0500 1999/12/23, Ted Sikora wrote: >> # mount -t cd9660 -o rdonly /dev/acd0a /cdrom > It worked! Strange ..without the -o rdonly flag it would not. That's exactly what's supposed to happen. Normally, when a system mounts a filesystem, it wants to mount it read/write so that it can update the "atime" stamp for any files that may be accessed. Obviously, you can't do this on a CD-ROM, so you need to explicitly tell the system to mount it read-only. You probably would have gotten more helpful (and less curt) answers if you had first gone to -questions with this. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 10:44:54 1999 Delivered-To: freebsd-stable@freebsd.org Received: from web504.mail.yahoo.com (web504.mail.yahoo.com [128.11.68.71]) by hub.freebsd.org (Postfix) with SMTP id 99F8114EE5 for ; Thu, 23 Dec 1999 10:44:52 -0800 (PST) (envelope-from god@yahoo.com) Received: (qmail 4863 invoked by uid 60001); 23 Dec 1999 18:41:15 -0000 Message-ID: <19991223184115.4862.qmail@web504.mail.yahoo.com> Received: from [208.224.169.134] by web504.mail.yahoo.com; Thu, 23 Dec 1999 10:41:15 PST Date: Thu, 23 Dec 1999 10:41:15 -0800 (PST) From: Mike s Subject: Re: bugs in the handbook. (FreeBSD Portal) To: God Cc: 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 Well, as i can see not many people care about the documentation, or at least providing FreeBSD users with there own web site with all the bells and whistles similar to linux.com. What would it take for some folks to get together and crank out an awesome freebsd site? I'm not putting down freebsd.org nor saying that it isn't resourceful because it is tremendously. Doesn't anyone have an opinion on this matter? God@yahoo.com ---God wrote: > Hi All, > > Maybe, just maybe, It is time for a team of > "motivated" > and "skilled" web developers with FreeBSD expertise > to > crank out a new web site entirely for the new year ( > err, for the new year to come :-) ), Including a new > handbook. Of course not trash the current handbook. > FreeBSD has evolved so fast but it seems the > Documentation has been left in the dust. > > I'm game, But only if people are serious and not > going > to say i will help and vanish. > > i sent this to -stable as well as the doc team > mailing > list since i haven't heard a peep out of the list in > awhile. > > maybe we start a FreeBSD Portal on FreeBSD.com and > leave FreeBSD.org running the way it is now. > > Just a thought.. > love you all. > > God > God@yahoo.com > > i am not subscribed to the list so please send a > copy > to me, thanks. > __________________________________________________ > Do You Yahoo!? > Thousands of Stores. Millions of Products. All in > one place. > Yahoo! Shopping: http://shopping.yahoo.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the > message > > > _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 10:48:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id 99B6F15410 for ; Thu, 23 Dec 1999 10:48:30 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id KAA24118; Thu, 23 Dec 1999 10:48:16 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Thu, 23 Dec 1999 10:48:16 -0800 Date: Thu, 23 Dec 1999 10:48:16 -0800 (PST) From: Kip Macy To: Mike s Cc: stable@freebsd.org Subject: Re: bugs in the handbook. (FreeBSD Portal) In-Reply-To: <19991223184115.4862.qmail@web504.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: god@yahoo.com,stable@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This sounds a little bit like flame-bait. Yes freebsd.org has some shortcomings, but no I have not made any contributions myself, so I am very lucky to have all the resources available that I do. Don't expect more of others than you do of yourself. Can I interpret this as an offer to help? -Kip On Thu, 23 Dec 1999, Mike s wrote: > Well, as i can see not many people care about the > documentation, or at least providing FreeBSD users > with there own web site with all the bells and > whistles similar to linux.com. > > What would it take for some folks to get together and > crank out an awesome freebsd site? > > I'm not putting down freebsd.org nor saying that it > isn't resourceful because it is tremendously. > > Doesn't anyone have an opinion on this matter? > > > God@yahoo.com > > ---God wrote: > > Hi All, > > > > Maybe, just maybe, It is time for a team of > > "motivated" > > and "skilled" web developers with FreeBSD expertise > > to > > crank out a new web site entirely for the new year ( > > err, for the new year to come :-) ), Including a new > > handbook. Of course not trash the current handbook. > > FreeBSD has evolved so fast but it seems the > > Documentation has been left in the dust. > > > > I'm game, But only if people are serious and not > > going > > to say i will help and vanish. > > > > i sent this to -stable as well as the doc team > > mailing > > list since i haven't heard a peep out of the list in > > awhile. > > > > maybe we start a FreeBSD Portal on FreeBSD.com and > > leave FreeBSD.org running the way it is now. > > > > Just a thought.. > > love you all. > > > > God > > God@yahoo.com > > > > i am not subscribed to the list so please send a > > copy > > to me, thanks. > > __________________________________________________ > > Do You Yahoo!? > > Thousands of Stores. Millions of Products. All in > > one place. > > Yahoo! Shopping: http://shopping.yahoo.com > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the > > message > > > > > > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-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 23 10:51:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from web503.mail.yahoo.com (web503.mail.yahoo.com [128.11.68.70]) by hub.freebsd.org (Postfix) with SMTP id 1A3FF14D38 for ; Thu, 23 Dec 1999 10:51:28 -0800 (PST) (envelope-from god@yahoo.com) Received: (qmail 17704 invoked by uid 60001); 23 Dec 1999 18:51:25 -0000 Message-ID: <19991223185125.17703.qmail@web503.mail.yahoo.com> Received: from [208.224.169.134] by web503.mail.yahoo.com; Thu, 23 Dec 1999 10:51:25 PST Date: Thu, 23 Dec 1999 10:51:25 -0800 (PST) From: Mike s Subject: Re: bugs in the handbook. To: Nik Clayton Cc: 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 well nothing wrong with the site at all, it is full of resources. But what i would like to do is create a freebsd portal. A full on interactive website similar to linux.com I think it is time, i mean there is a lot of scattered docs from various FreeBSD users all over the web, but i think it would benefit the FreeBSD community tremendously if we create a FreeBSD portal. take a look at linux.com and ponder some idea's yourself and then we can talk again. i do have alot of idea's that i would like to see in a "new" site but i'm in no rush, well maybe i am , i know wih the right team of developers i would be very excited to see this project come to life. --- Nik Clayton wrote: > On Tue, Dec 21, 1999 at 01:46:14PM -0800, Mike s > wrote: > > Maybe, just maybe, It is time for a team of > > "motivated" > > and "skilled" web developers with FreeBSD > expertise to > > crank out a new web site entirely for the new year > ( > > err, for the new year to come :-) ), Including a > new > > handbook. Of course not trash the current > handbook. > > FreeBSD has evolved so fast but it seems the > > Documentation has been left in the dust. > > What, specifically, do you think is wrong with the > current site? I've got > my own list, but I've been quite close to the site > for about a year, so > I don't see it as more normal (or, perhaps, less > 'abnormal' :-) ) users > do. Specific suggestions would be welcome. > > N > -- > If you want to imagine the future, imagine a > tennis shoe stamping > on a penguin's face forever. > --- with apologies to George Orwell > _________________________________________________________ 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 Thu Dec 23 11: 0:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id 61C46156CE for ; Thu, 23 Dec 1999 11:00:33 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id 103D1E8A8; Thu, 23 Dec 1999 14:00:32 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id OAA36340; Thu, 23 Dec 1999 14:00:32 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14434.29007.987036.666080@onceler.kcilink.com> Date: Thu, 23 Dec 1999 14:00:31 -0500 (EST) To: Mike s Cc: stable@freebsd.org Subject: Re: bugs in the handbook. (FreeBSD Portal) In-Reply-To: <19991223184115.4862.qmail@web504.mail.yahoo.com> References: <19991223184115.4862.qmail@web504.mail.yahoo.com> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Ms" == Mike s writes: Ms> Doesn't anyone have an opinion on this matter? My personal opinion is that without (accurate) documentation no computer program or system is very useful. I just switched my desktop from BSD/OS to FreeBSD, and I'm finding all kinds of things on FreeBSD being either inaccurately or incompletely documented. I don't recall any specific instance where the documentation was absolutely incorrect, which is a good thing. There also seems to be some decay in the software. For example, I wanted to try and build a PicoBSD floppy from a -stable snapshot. It doesn't work. I'll eventually figure out why, but it is annoying. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 11: 2:20 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id F093E14DCB for ; Thu, 23 Dec 1999 11:02:15 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 121DVy-000Eyr-00; Thu, 23 Dec 1999 21:03:06 +0200 From: Sheldon Hearn To: Gerald Pfeifer Cc: Marcin Cieslak , freebsd-stable@FreeBSD.ORG Subject: Re: /bin/test broken ? In-reply-to: Your message of "Thu, 23 Dec 1999 14:57:56 +0100." Date: Thu, 23 Dec 1999 21:03:06 +0200 Message-ID: <57588.945975786@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999 14:57:56 +0100, Gerald Pfeifer wrote: > > What's _the_ standard? > > You would have to consult POSIX or whatever, I guess, but clearly the > first variant is not portable (in practice) so one should refrain from > using it anyway. Not only is it not portable, but it's also not POSIX.2. :-) The POSIX.2 Synopsis for test gives: test {expression} [ {expression} ] While other vendors may have chosen to allow a mongrel of these two, folks wishing to keep their scripts portable should refrain from using such a hybrid. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 11: 5:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 17A5215641; Thu, 23 Dec 1999 11:05:54 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 121DaH-000F1C-00; Thu, 23 Dec 1999 21:07:33 +0200 From: Sheldon Hearn To: Mike s Cc: Nik Clayton , stable@FreeBSD.ORG Subject: Re: bugs in the handbook. In-reply-to: Your message of "Thu, 23 Dec 1999 10:51:25 PST." <19991223185125.17703.qmail@web503.mail.yahoo.com> Date: Thu, 23 Dec 1999 21:07:33 +0200 Message-ID: <57733.945976053@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999 10:51:25 PST, Mike s wrote: > But what i would like to do is create a freebsd > portal. Feel free. What are you waiting for? Presumably, you've looked at sites like http://www.freebsddiary.org/freebsd/ and decided they lack something that you can do yourself? Great! Let me know when you need a link to your site from the http://www.freebsd.org/ and I'll be happy to add one. Personally, I think that fragmentation of efforts leads to lots of lesser efforts. But if you feel you have something to offer that doesn't really fit into the htt://www.freebsd.org/ framework and would rather start up something yourself, I'm sure we'd be eager to see what you come up with. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 11: 8:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (Postfix) with ESMTP id 5035714F68 for ; Thu, 23 Dec 1999 11:08:16 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with ESMTP id UAA24540 for ; Thu, 23 Dec 1999 20:08:21 +0100 (MET) Date: Thu, 23 Dec 1999 20:08:17 +0100 (MET) From: Marcin Cieslak To: freebsd-stable@freebsd.org Subject: Re: bugs in the handbook. (FreeBSD Portal) 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 > This sounds a little bit like flame-bait. Yes freebsd.org has some > shortcomings, but no I have not made any contributions myself, so I am > very lucky to have all the resources available that I do. Don't expect > more of others than you do of yourself. Can I interpret this as an offer > to help? Well, yes. I am currently thinking of the my Polish website concept. What I am going to do is better advocacy of some certain subjects which make the FreeBSD actually _better_. I think I will have some ideas on better ports advocacy, also on an easy upgrade option like cvsup. From my experience beginning FreeBSD sysadmins coming from linux or NT background are usually amazed with these features - if "marketed" properly. I am not so sure of my English-writing skills, but I think I can bring some ideas. (Time to subscribe to -doc, you say?:) -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 11:11: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 75C48156AD for ; Thu, 23 Dec 1999 11:10:58 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 121Des-000F2u-00; Thu, 23 Dec 1999 21:12:18 +0200 From: Sheldon Hearn To: Vivek Khera Cc: Mike s , stable@FreeBSD.ORG Subject: Re: bugs in the handbook. (FreeBSD Portal) In-reply-to: Your message of "Thu, 23 Dec 1999 14:00:31 EST." <14434.29007.987036.666080@onceler.kcilink.com> Date: Thu, 23 Dec 1999 21:12:18 +0200 Message-ID: <57839.945976338@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 23 Dec 1999 14:00:31 EST, Vivek Khera wrote: > I just switched my desktop from BSD/OS to FreeBSD, and I'm finding all > kinds of things on FreeBSD being either inaccurately or incompletely > documented. Well thank you for your bug reports. :-) If you don't report the problems, how're they going to get fixed in a project which is essentially driven by user-contributions? Ciao, Sheldon. PS: I see one problem report from you (not a documentation-related problem, though), but that one was misfiled, so it might take people a little longer to get to. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 11:20:40 1999 Delivered-To: freebsd-stable@freebsd.org Received: from math.udel.edu (math.udel.edu [128.175.16.7]) by hub.freebsd.org (Postfix) with ESMTP id E65B314C87 for ; Thu, 23 Dec 1999 11:20:36 -0800 (PST) (envelope-from schwenk@math.udel.edu) Received: from math.udel.edu (sisyphus.math.udel.edu [128.175.16.167]) by math.udel.edu (8.9.3+Sun/8.9.1) with ESMTP id OAA19379; Thu, 23 Dec 1999 14:20:31 -0500 (EST) Message-ID: <386275FF.74333075@math.udel.edu> Date: Thu, 23 Dec 1999 14:20:31 -0500 From: Peter Schwenk Organization: University of Delaware X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: en, fr, de, ko MIME-Version: 1.0 To: Mike s Cc: stable@freebsd.org Subject: Re: bugs in the handbook. (FreeBSD Portal) References: <19991223184115.4862.qmail@web504.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I think the general consensus is that the existing www.freebsd.org should be the FreeBSD portal that you describe. If the documentation sux on freebsd.org, then we should fix it there, not add to the possible confusion by adding a totally separate web site. At least that's what I got from the "resistance" to your idea in this list. Mike s wrote: > Well, as i can see not many people care about the > documentation, or at least providing FreeBSD users > with there own web site with all the bells and > whistles similar to linux.com. > > What would it take for some folks to get together and > crank out an awesome freebsd site? > > I'm not putting down freebsd.org nor saying that it > isn't resourceful because it is tremendously. > > Doesn't anyone have an opinion on this matter? > > God@yahoo.com > -- PETER SCHWENK | UNIX System Administrator Department of Mathematical Sciences | University of Delaware schwenk@math.udel.edu | (302)831-0437 <-NEW!!! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 11:29:23 1999 Delivered-To: freebsd-stable@freebsd.org Received: from luna.lyris.net (luna.shelby.com [207.90.155.6]) by hub.freebsd.org (Postfix) with ESMTP id A648515721 for ; Thu, 23 Dec 1999 11:29:20 -0800 (PST) (envelope-from kip@lyris.com) Received: from luna.shelby.com by luna.lyris.net (8.9.1b+Sun/SMI-SVR4) id LAA24498; Thu, 23 Dec 1999 11:29:00 -0800 (PST) Received: from (luna.shelby.com [207.90.155.6]) by luna.shelby.com with SMTP (MailShield v1.50); Thu, 23 Dec 1999 11:29:00 -0800 Date: Thu, 23 Dec 1999 11:29:00 -0800 (PST) From: Kip Macy To: Peter Schwenk Cc: Mike s , stable@freebsd.org Subject: Re: bugs in the handbook. (FreeBSD Portal) In-Reply-To: <386275FF.74333075@math.udel.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-SMTP-HELO: luna X-SMTP-MAIL-FROM: kip@lyris.com X-SMTP-RCPT-TO: schwenk@math.udel.edu,god@yahoo.com,stable@freebsd.org X-SMTP-PEER-INFO: luna.shelby.com [207.90.155.6] Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG He has a good point. One of the big challengs of FreeBSD vis a vis Linux, is a smaller user base. There are already 4 BSDs out there, it would be potentially harmful to further fragment the user base. -Kip On Thu, 23 Dec 1999, Peter Schwenk wrote: > I think the general consensus is that the existing www.freebsd.org > should be the FreeBSD portal that you describe. If the documentation > sux on freebsd.org, then we should fix it there, not add to the possible > confusion by adding a totally separate web site. At least that's what I > got from the "resistance" to your idea in this list. > > Mike s wrote: > > > Well, as i can see not many people care about the > > documentation, or at least providing FreeBSD users > > with there own web site with all the bells and > > whistles similar to linux.com. > > > > What would it take for some folks to get together and > > crank out an awesome freebsd site? > > > > I'm not putting down freebsd.org nor saying that it > > isn't resourceful because it is tremendously. > > > > Doesn't anyone have an opinion on this matter? > > > > God@yahoo.com > > > > -- > PETER SCHWENK | UNIX System Administrator > Department of Mathematical Sciences | University of Delaware > schwenk@math.udel.edu | (302)831-0437 <-NEW!!! > > > > > > 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 23 11:40:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 33D2E156AD for ; Thu, 23 Dec 1999 11:40:13 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA06282 for freebsd-stable@FreeBSD.ORG; Thu, 23 Dec 1999 19:45:11 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01345 for freebsd-stable@FreeBSD.ORG; Thu, 23 Dec 1999 20:28:53 +0100 (CET) (envelope-from wilko) Date: Thu, 23 Dec 1999 20:28:53 +0100 From: Wilko Bulte To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Message-ID: <19991223202853.D1056@yedi.iaf.nl> References: <199912231157.MAA11441@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912231157.MAA11441@dorifer.heim3.tu-clausthal.de>; from olli@dorifer.heim3.tu-clausthal.de on Thu, Dec 23, 1999 at 12:57:29PM +0100 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 23, 1999 at 12:57:29PM +0100, Oliver Fromme wrote: > Wilko Bulte wrote in list.freebsd-stable: > > On Wed, Dec 22, 1999 at 11:26:32PM +0100, Oliver Fromme wrote: > > > Does FeeBSD/Alpha run reliably on an AXPpci33 with Quantum > > > Fireball (SCSI)? > > > > Yes, no problem. My NoName is currently living with Marcel Moolenaar > > for X-build testing etc. Running -current FreeBSD. Works great, albeit > > slowly (21066 CPUs are just not fast). > > OK, thanks. I know that it's not fast. :-) > > > If your NoName is the one with the broken PSU: any normal AT-style PSU > > will work. > > I don't have a "NoName" box. I bought the AXPpci33 mainboard > + 21066-166 and put it into a standard AT midi tower. Spent > $50 for the thing... Yes, I know, it's not worth that much, > but I just wanted to play around with AXP stuff. The AXPpci33 == NoName. The board was sold to OEMs for inclusion in whatever they liked. I think you confuse the NoName with the Multia (which is also 21066). On the last 'HCC dagen' (in Utrecht, the Netherlands) they were selling the last 166Mc boards for US$ 12 a piece ;-) No cache, but new in the carton box. > A few days ago, it suddenly performed a spontaneous shutdown > and played dead. The fuse in the power supply is OK, but even > the light in the power switch (which is on the primary side of > the transformer) is off. Strange. Duh. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 11:40:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 2F8BD1563C for ; Thu, 23 Dec 1999 11:40:19 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA06284; Thu, 23 Dec 1999 19:45:11 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01396; Thu, 23 Dec 1999 20:30:45 +0100 (CET) (envelope-from wilko) Date: Thu, 23 Dec 1999 20:30:45 +0100 From: Wilko Bulte To: Brian Kraemer Cc: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Message-ID: <19991223203044.E1056@yedi.iaf.nl> References: <199912222226.XAA00562@dorifer.heim3.tu-clausthal.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from kraemer@u.washington.edu on Thu, Dec 23, 1999 at 08:01:26AM -0800 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 23, 1999 at 08:01:26AM -0800, Brian Kraemer wrote: > On Wed, 22 Dec 1999, Oliver Fromme wrote: > > > No. I submitted my code to the Seti@home folks for review, > > they said "great, thanks!" and I've never heard anything from > > them again. :-( > > Actually, I think I read somewhere once that the SETI@home people are > worried that if they made optimizations to their clients, their servers > and staff would not be able to keep up with all the data pouring in at a > faster rate. They never really expected the kind of turnout they received > in the first place. Sjeez. If that is true they should consider how much energy is wasted because machines are not used to their capacity. Or alternatively the same work could be done with less CPUs. Really, sounds like silly reason to me. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 11:40:33 1999 Delivered-To: freebsd-stable@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id E500C1570E for ; Thu, 23 Dec 1999 11:40:24 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA06281; Thu, 23 Dec 1999 19:45:09 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA01331; Thu, 23 Dec 1999 20:25:56 +0100 (CET) (envelope-from wilko) Date: Thu, 23 Dec 1999 20:25:56 +0100 From: Wilko Bulte To: Bjoern Fischer Cc: stable@FreeBSD.ORG Subject: Re: /boot/loader fails to reset AMD K6-II FPU Message-ID: <19991223202556.C1056@yedi.iaf.nl> References: <19991222042320.A749@frolic.no-support.loc> <19991222204703.B833@yedi.iaf.nl> <19991222232741.A1344@frolic.no-support.loc> <19991223001940.C37471@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991223001940.C37471@yedi.iaf.nl>; from wilko@yedi.iaf.nl on Thu, Dec 23, 1999 at 12:19:42AM +0100 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 23, 1999 at 12:19:42AM +0100, Wilko Bulte wrote: > On Wed, Dec 22, 1999 at 11:27:41PM +0100, Bjoern Fischer wrote: > > On Wed, Dec 22, 1999 at 08:47:03PM +0100, Wilko Bulte wrote: > > [...] > > > > When I reboot the system from the /boot/loader > > > > command line (with `reboot'), the system is > > > > being resetted, the kernel loads and starts, > > > > and when the FPU is being initialized the kernel > > > > traps. > > [...] > > > Works fine on my Asus T2P4 with the same CPU: > > > > > > WKB ~>dmesg | grep -i amd > > > CPU: AMD-K6(tm) 3D processor (399.81-MHz 586-class CPU) > > > Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 > > > AMD Features=0x80000800 > > > > > > But what date is your -stable? > > > > My stable is as fresh as Dec 20th (per CTM). > > I'll buildworld for the latest -stable (3.4-stable I guess ;-) > and see what happens. Will take a while to do. I'm now at 3.4-stable and things work like before: as a charm. Looks like the BIOS problem suggested before might be the culprit. -- Wilko Bulte Arnhem, The Netherlands - The FreeBSD Project WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 12:25: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from monsoon.mail.pipex.net (monsoon.mail.pipex.net [158.43.128.69]) by hub.freebsd.org (Postfix) with SMTP id 0B6B4156F2 for ; Thu, 23 Dec 1999 12:25:03 -0800 (PST) (envelope-from mark@dogma.freebsd-uk.eu.org) Received: (qmail 20035 invoked from network); 23 Dec 1999 20:25:01 -0000 Received: from userco81.uk.uudial.com (HELO marder-1.) (62.188.156.11) by smtp.dial.pipex.com with SMTP; 23 Dec 1999 20:25:01 -0000 Received: (from mark@localhost) by marder-1. (8.9.3/8.8.8) id UAA01768; Thu, 23 Dec 1999 20:24:59 GMT (envelope-from mark) Date: Thu, 23 Dec 1999 20:24:59 +0000 From: Mark Ovens To: Tom Cc: "Dan O'Connor" , freebsd-stable@freebsd.org Subject: Re: SOFTUPDATES Message-ID: <19991223202459.E327@marder-1> References: <012301bf4cef$3fde6f20$0200000a@danco.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Organization: Total lack of Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Dec 22, 1999 at 07:05:18PM -0800, Tom wrote: > On Wed, 22 Dec 1999, Dan O'Connor wrote: > > > >Did ``boot -s'' and ran tunefs but got an error: > > > > > >Enter full pathname of shell or RETURN for /bin/sh: > > ># pwd > > >/ > > ># tunefs -n enable /usr > > >tunefs: soft updates set > > >tunefs: /dev/rda1s1e: reload: Invalid argument > > > > > >What caused this? There's no reference in the manpage. > > > > I've seen it on some IDE drives, and not on some other IDE drives...in each > > case softupdates was indeed enabled. > > It happens if the filesystem is not currently mounted read-only. It is > try to reload the incore (r*) device, but it was never loaded to begin > with. When you boot single user, only "/" is mounted, so all other > filesystems will give you that warning. > > So it is completely harmless. > Thanks Tom. I've submitted a PR (docs/15657) to document this warning in the manpage. Hope you don't mind, that I've used your answer pretty much verbatim? > > --Dan > > Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message -- "there's a long-standing bug relating to the x86 architecture that allows you to install Windows too" -Matthew D. Fuller ________________________________________________________________ FreeBSD - The Power To Serve http://www.freebsd.org My Webpage http://ukug.uk.freebsd.org/~mark/ mailto:mark@ukug.uk.freebsd.org http://www.radan.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 23 12:30:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 05B0B14D34 for ; Thu, 23 Dec 1999 12:30:15 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id MAA65714; Thu, 23 Dec 1999 12:30:03 -0800 (PST) Date: Thu, 23 Dec 1999 12:30:03 -0800 (PST) From: David Wolfskill Message-Id: <199912232030.MAA65714@pau-amma.whistle.com> To: peter.jeremy@alcatel.com.au, vlad@high.net.ru Subject: Re: /bin/test broken ? Cc: freebsd-stable@FreeBSD.ORG In-Reply-To: <99Dec23.123516est.40332@border.alcanet.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Thu, 23 Dec 1999 12:44:07 +1100 >From: Peter Jeremy >That said, the error message should have been: > test: ]: unexpected operator >and it is not clear why you are getting `[' reported as the program >name. As far as I can tell, nothing related to test or errx(3) has >been updated recently. (I'm not actually running -stable, so I can't >confirm the behaviour). Well, /bin/test and /bin/[ are links to the same inode: pau-amma[71]% !ls ls -ilL `which \[ test` 107 -r-xr-xr-x 2 root wheel 46572 Feb 15 1999 /bin/[ 107 -r-xr-xr-x 2 root wheel 46572 Feb 15 1999 /bin/test (Not that this is especially new; I just checked on the home Sun 3/60 (SunOS 4.1.1_U1); it reports: dhw[13] ls -ilL `which \[ test` 6045 -rwxr-xr-x 2 root 4760 Oct 13 1990 /bin/[* 6045 -rwxr-xr-x 2 root 4760 Oct 13 1990 /bin/test* Just in case anyone else was wondering....) Cheers, david -- David Wolfskill dhw@whistle.com UNIX System Administrator voice: (650) 577-7158 pager: (888) 347-0197 FAX: (650) 372-5915 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 13: 1: 5 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hotmail.com (f174.law4.hotmail.com [216.33.149.174]) by hub.freebsd.org (Postfix) with SMTP id 1D0721570D for ; Thu, 23 Dec 1999 13:01:04 -0800 (PST) (envelope-from wind_prowler@hotmail.com) Received: (qmail 38706 invoked by uid 0); 23 Dec 1999 21:01:00 -0000 Message-ID: <19991223210100.38705.qmail@hotmail.com> Received: from 203.106.63.99 by www.hotmail.com with HTTP; Thu, 23 Dec 1999 13:01:00 PST X-Originating-IP: [203.106.63.99] From: "Nawfal M. Rouyan" To: freebsd-stable@freebsd.org Subject: localhost doesn't work? Date: Fri, 24 Dec 1999 05:01:00 MYT Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm using freebsd 3.4 stable as of dec 22 1999. It seems that when I ping localhost, there is no response. When I try to ftp localhost, also no response. amnesiac# ifconfig -a ed1: flags=8843 mtu 1500 inet 10.100.98.141 netmask 0xffffff00 broadcast 10.100.98.255 ether 00:00:e8:e8:4c:2a lp0: flags=8810 mtu 1500 tun0: flags=8010 mtu 1500 lo0: flags=8008 mtu 16384 amnesiac# uname -a FreeBSD amnesiac.cyber.mmu.edu.my 3.4-STABLE FreeBSD 3.4-STABLE #0: Wed Dec 22 06:02:32 MYT 1999 opal@amnesiac.cyber.mmu.edu.my:/usr/src/sys/compile/OPAL i386 ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.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 23 13: 7:50 1999 Delivered-To: freebsd-stable@freebsd.org Received: from napalm.plano.sterling.com (napalm.plano.sterling.com [208.24.125.34]) by hub.freebsd.org (Postfix) with ESMTP id 5AF0D14C8C for ; Thu, 23 Dec 1999 13:07:48 -0800 (PST) (envelope-from alan.edmonds@sterling.com) Received: from sterling.com (CD27T.plano.sterling.com [10.1.54.234]) by napalm.plano.sterling.com (8.9.1b+Sun/8.9.1) with ESMTP id PAA05484; Thu, 23 Dec 1999 15:07:41 -0600 (CST) Message-ID: <38628F1D.5EE9769F@sterling.com> Date: Thu, 23 Dec 1999 15:07:41 -0600 From: Alan Edmonds X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Nawfal M. Rouyan" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: localhost doesn't work? References: <19991223210100.38705.qmail@hotmail.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There's been reports of a setup problem with lo0. Check your /etc/rc.conf file. See if lo0 is missing from the network_interfaces list. I just did an install and it was missing. It just had "de0 auto". Just add lo0 and reboot. It worked for me. -- Alan Edmonds, KB5ZUY Sterling Software M/S 132 Phone: +1-972-801-6485 5800 Tennyson Pkwy. Email: alan.edmonds@sterling.com Plano, TX, USA 75024 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 13: 9:39 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id A178F14C27 for ; Thu, 23 Dec 1999 13:09:35 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 121FW0-000Fp4-00; Thu, 23 Dec 1999 23:11:16 +0200 From: Sheldon Hearn To: "Nawfal M. Rouyan" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: localhost doesn't work? In-reply-to: Your message of "Fri, 24 Dec 1999 05:01:00 +0700." <19991223210100.38705.qmail@hotmail.com> Date: Thu, 23 Dec 1999 23:11:16 +0200 Message-ID: <60825.945983476@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Dec 1999 05:01:00 +0700, "Nawfal M. Rouyan" wrote: > I'm using freebsd 3.4 stable as of dec 22 1999. It seems that when I ping > localhost, there is no response. When I try to ftp localhost, also no > response. Let's see the results of this command: grep lo0 /etc/rc.conf Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 13:10:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from pi.yip.org (yip.org [199.45.111.121]) by hub.freebsd.org (Postfix) with ESMTP id CE579156B3 for ; Thu, 23 Dec 1999 13:10:41 -0800 (PST) (envelope-from melange@yip.org) Received: from localhost (melange@localhost) by pi.yip.org (8.9.3/8.9.3) with ESMTP id QAA78899; Thu, 23 Dec 1999 16:10:36 -0500 (EST) (envelope-from melange@yip.org) Date: Thu, 23 Dec 1999 16:10:36 -0500 (EST) From: Bob K X-Sender: melange@localhost To: Alan Edmonds Cc: "Nawfal M. Rouyan" , freebsd-stable@FreeBSD.ORG Subject: Re: localhost doesn't work? In-Reply-To: <38628F1D.5EE9769F@sterling.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, 23 Dec 1999, Alan Edmonds wrote: > There's been reports of a setup problem with lo0. > Check your /etc/rc.conf file. See if lo0 is missing from the > network_interfaces list. I just did an install > and it was missing. It just had "de0 auto". Just > add lo0 and reboot. It worked for me. As opposed to rebooting, one could probably do the following: ifconfig lo0 up To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 13:14:41 1999 Delivered-To: freebsd-stable@freebsd.org Received: from matrix.cxi.cx (CXI.CX [208.138.115.103]) by hub.freebsd.org (Postfix) with ESMTP id 989E714DD7 for ; Thu, 23 Dec 1999 13:14:39 -0800 (PST) (envelope-from nwsedlak@matrix.cxi.cx) Received: (from nwsedlak@localhost) by matrix.cxi.cx (8.9.3/8.9.3) id PAA78930 for freebsd-stable@FreeBSD.ORG; Thu, 23 Dec 1999 15:48:58 -0500 (EST) (envelope-from nwsedlak) Date: Thu, 23 Dec 1999 15:48:58 -0500 From: Neil Sedlak To: freebsd-stable@FreeBSD.ORG Subject: Re: AMD 3DNow instructions on FreeBSD Message-ID: <19991223154858.A78790@matrix.cxi.cx> References: <199912222226.XAA00562@dorifer.heim3.tu-clausthal.de> <19991223203044.E1056@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <19991223203044.E1056@yedi.iaf.nl> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Dec 23, 1999 at 08:30:45PM +0100, Wilko Bulte wrote: > On Thu, Dec 23, 1999 at 08:01:26AM -0800, Brian Kraemer wrote: > > On Wed, 22 Dec 1999, Oliver Fromme wrote: > > > No. I submitted my code to the Seti@home folks for review, > > > they said "great, thanks!" and I've never heard anything from > > > them again. :-( > > Actually, I think I read somewhere once that the SETI@home people are > > worried that if they made optimizations to their clients, their servers > > and staff would not be able to keep up with all the data pouring in at a > Sjeez. If that is true they should consider how much energy is wasted > because machines are not used to their capacity. Or alternatively the > same work could be done with less CPUs. *sigh* Not this pointless argument again. This IS the FreeBSD stable mailing list, right? I don't see what SETI@Home has to do with FreeBSD stable technical questions. Especially since people are so quick to jump on people who should have posted to "questions". > Really, sounds like silly reason to me. Then you don't understand the scope of the problem. This has been argued over and over and over and over again in other forums, do we need it here? -- Neil Sedlak nwsedlak@cxi.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 13:24:35 1999 Delivered-To: freebsd-stable@freebsd.org Received: from neptune.innovativeinternet.net (neptune.innovativeinternet.net [208.244.165.5]) by hub.freebsd.org (Postfix) with SMTP id 8688814C27 for ; Thu, 23 Dec 1999 13:24:33 -0800 (PST) (envelope-from Harlan.Stenn@pfcs.com) Received: (qmail 14736 invoked from network); 23 Dec 1999 21:24:31 -0000 Received: from unknown (HELO pcpsj.pfcs.com) (?U5Gn05Byf2g5u0CFm17uszt4jTXK2wyh?@208.238.64.78) by 208.244.165.5 with SMTP; 23 Dec 1999 21:24:31 -0000 Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id ; Thu, 23 Dec 1999 16:23:57 -0500 (EST) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 23 Dec 1999 13:21:10 -0800 (PST) Received: from localhost.pfcs.com [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id ; Thu, 23 Dec 1999 16:21:10 -0500 (EST) To: Alan Edmonds Cc: "Nawfal M. Rouyan" , freebsd-stable@FreeBSD.ORG Subject: Re: localhost doesn't work? In-Reply-To: Alan Edmonds's (alan.edmonds@sterling.com) message dated Thu, 23 Dec 1999 15:07:41. <38628F1D.5EE9769F@sterling.com> X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d User-Agent: EMH/1.10.0 SEMI/1.13.3 (Komaiko) FLIM/1.12.7 (=?ISO-8859-1?Q?Y?= =?ISO-8859-1?Q?=1B=2ED=8E=FEzaki?=) XEmacs/21.1 (20 Minutes to Nikko) (i386-unknown-freebsd2.2.8) MIME-Version: 1.0 (generated by SEMI 1.13.3 - "Komaiko") Content-Type: text/plain; charset=US-ASCII Date: Thu, 23 Dec 1999 16:21:09 -0500 Message-ID: <16373.945984069@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG rc.network says that if ${network_interfaces} is "auto" it will grab the list of available interfaces from `ifconfig -l`. I don't think using "de0 auto" will do what you expect. Run "ifconfig -l" and see what it says. YTSL. H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 14:55:17 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by hub.freebsd.org (Postfix) with ESMTP id E0D2514F49; Thu, 23 Dec 1999 14:55:13 -0800 (PST) (envelope-from scottm@CS.UCLA.EDU) Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.192.128]) by mailman.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id OAA29549; Thu, 23 Dec 1999 14:55:59 -0800 (PST) Received: (from scottm@localhost) by mordred.cs.ucla.edu (8.9.3/UCLACS-5.0) id OAA00872; Thu, 23 Dec 1999 14:55:13 -0800 (PST) Date: Thu, 23 Dec 1999 14:55:13 -0800 (PST) From: Scott Michel Message-Id: <199912232255.OAA00872@mordred.cs.ucla.edu> To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: TCP Oddities followup Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As I'd recently posted on -current, I've been noticing TCP oddities in 3.3 and 3.4. I've got a pn card (NetGear FA310tx) and a few new things to report: - Invariably, a TCP connection will freeze with something in the send queue. Connections don't freeze even if there's something in the receive queue. - tcpdump-ing the pn0 interface shows that the host thinks that it's sending data. tcpdump-ing elsewhere in the network shows that pn0 isn't actually transmitting anything into the wire. - This really is a TCP or interface bug because NFS connections don't freeze using UDP. - Other TCP connections continue to operate (like a cvsup in the background) I haven't stared at the if_pn.c code all that closely but I'm willing to entertain debugging suggestions. -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 16: 5:57 1999 Delivered-To: freebsd-stable@freebsd.org Received: from alcanet.com.au (border.alcanet.com.au [203.62.196.10]) by hub.freebsd.org (Postfix) with ESMTP id 9058C14D22 for ; Thu, 23 Dec 1999 16:05:53 -0800 (PST) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: by border.alcanet.com.au id <40325>; Fri, 24 Dec 1999 10:56:38 +1100 Content-return: prohibited Date: Fri, 24 Dec 1999 11:05:35 +1100 From: Peter Jeremy Subject: Re: /bin/test broken ? In-reply-to: <199912232030.MAA65714@pau-amma.whistle.com>; from dhw@whistle.com on Fri, Dec 24, 1999 at 07:30:03AM +1100 To: David Wolfskill Cc: freebsd-stable@FreeBSD.ORG Message-Id: <99Dec24.105638est.40325@border.alcanet.com.au> MIME-version: 1.0 X-Mailer: Mutt 1.0i Content-type: text/plain; charset=us-ascii References: <99Dec23.123516est.40332@border.alcanet.com.au> <199912232030.MAA65714@pau-amma.whistle.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 1999-Dec-24 07:30:03 +1100, David Wolfskill wrote: >>That said, the error message should have been: >> test: ]: unexpected operator >>and it is not clear why you are getting `[' reported as the program >>name. > >Well, /bin/test and /bin/[ are links to the same inode: Agreed, but the error message is printed by errx(3). errx(3) prints __progname (which is effectively equivalent to argv[0]) as the program name - ie the name by which the program was invoked. test(1) includes a check near the beginning to see it it was invoked as `[' and if it was it checks to see that the last argument is `]' and deletes it if it was. In both cases, the remaining arguments are then passed to the expression evaluator. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 16:35:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 66C8D14BD2 for ; Thu, 23 Dec 1999 16:35:26 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 121Ij4-000GWQ-00; Fri, 24 Dec 1999 02:36:58 +0200 From: Sheldon Hearn To: David Wolfskill Cc: Peter Jeremy , freebsd-stable@FreeBSD.ORG Subject: Re: /bin/test broken ? In-reply-to: Your message of "Fri, 24 Dec 1999 11:05:35 +1100." <99Dec24.105638est.40325@border.alcanet.com.au> Date: Fri, 24 Dec 1999 02:36:58 +0200 Message-ID: <63513.945995818@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Dec 1999 11:05:35 +1100, Peter Jeremy wrote: > test(1) includes a check near the beginning to see it it was invoked as > `[' and if it was it checks to see that the last argument is `]' and > deletes it if it was. In both cases, the remaining arguments are then > passed to the expression evaluator. The patch below teaches test to ignore a trailing ] when called as [. I am against such a change in FreeBSD, since the change is neither required by POSIX nor safe (consider the case where the last operand on the command line is "]"). Still, if you must have FreeBSD copy the stupidity of another platform, this'll do the trick. Ciao, Sheldon. Index: test.c =================================================================== RCS file: /home/ncvs/src/bin/test/test.c,v retrieving revision 1.28 diff -u -d -r1.28 test.c --- test.c 1999/08/27 23:15:48 1.28 +++ test.c 1999/12/24 00:33:43 @@ -168,7 +168,8 @@ if (strcmp(argv[--argc], "]")) errx(2, "missing ]"); argv[argc] = NULL; - } + } else if (strcmp(argv[argc - 1], "]") == 0) + argv[--argc] = NULL; /* XXX work around the absence of an eaccess(2) syscall */ (void)setgid(getegid()); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 16:44:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc1.ct.home.com (ha1.rdc1.ct.home.com [24.2.0.66]) by hub.freebsd.org (Postfix) with ESMTP id 9B1AF14D34 for ; Thu, 23 Dec 1999 16:44:17 -0800 (PST) (envelope-from tsikora@home.com) Received: from home.com ([24.2.168.186]) by mail.rdc1.ct.home.com (InterMail v4.01.01.07 201-229-111-110) with ESMTP id <19991224004413.IMHQ9446.mail.rdc1.ct.home.com@home.com> for ; Thu, 23 Dec 1999 16:44:13 -0800 Message-ID: <38627B7C.A5CC60CD@home.com> Date: Thu, 23 Dec 1999 14:43:56 -0500 From: Ted Sikora Reply-To: tsikora@powerusersbbs.com Organization: Jtl Development X-Mailer: Mozilla 4.61 [en] (X11; U; OpenBSD 2.6 i386) X-Accept-Language: en-US,en-GB MIME-Version: 1.0 To: FreeBSD Stable Subject: Re: CDROM mount problems! References: <199912231414.JAA53041@rr.gfoster.com> <38623ACE.6042C690@home.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brad Knowles wrote: > > At 10:07 AM -0500 1999/12/23, Ted Sikora wrote: > > >> # mount -t cd9660 -o rdonly /dev/acd0a /cdrom > > It worked! Strange ..without the -o rdonly flag it would not. > > That's exactly what's supposed to happen. Normally, when a > system mounts a filesystem, it wants to mount it read/write so that > it can update the "atime" stamp for any files that may be accessed. > Obviously, you can't do this on a CD-ROM, so you need to explicitly > tell the system to mount it read-only. > > You probably would have gotten more helpful (and less curt) > answers if you had first gone to -questions with this. > Thanks, I appreciate the help. As you can tell I am new to the FreeBSD mailists. I'll learn... I hope! -- Ted Sikora Jtl Development Group tsikora@powerusersbbs.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 23 18:29:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.rdc3.on.home.com (ha1.rdc3.on.home.com [24.2.9.68]) by hub.freebsd.org (Postfix) with ESMTP id 7687514BFA for ; Thu, 23 Dec 1999 18:29:43 -0800 (PST) (envelope-from cwass99@home.com) Received: from tristan.net ([24.114.108.234]) by mail.rdc3.on.home.com (InterMail v4.01.01.02 201-229-111-106) with ESMTP id <19991224022731.OABU7552.mail.rdc3.on.home.com@tristan.net>; Thu, 23 Dec 1999 18:27:31 -0800 Content-Length: 2545 Message-ID: X-Mailer: XFMail 1.4.2 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <19991223184115.4862.qmail@web504.mail.yahoo.com> Date: Thu, 23 Dec 1999 21:26:45 -0500 (EST) From: Colin To: Mike s Subject: Re: bugs in the handbook. (FreeBSD Portal) Cc: stable@FreeBSD.ORG Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I don't think we don't care about the documentation, that strikes me as something of an oversimplification. There are 2 distinct problems here: 1) The peole who know enough about the system to document it properly generally don't have the time (or inclination...gotta love those programmers ;)) to spend on documentation. They're too busy fixing the problems that turn up regularly or adding enhancements (which is where most of the problems start ;)). 2) The peole who are most willing to spend time on the documentation don't have the specific knowledge to do it. They are the one's who would like to be reading the docs. Yes, I know it's inappropriate to generalize that much, but I think you get the idea. There is, of course, quite a lot of good documentation out there already, most of it accessible on-line. There is a definite need for ongoing improvement and upgrading, but I don't think that surprises anyone. There's an interesting article at http://www.firstmonday.org/issues/issue4_12/bezroukov/index.html that talks about the problems of documentation in the Open Software world. Actually, it is just a really good second look at the "Cathedral and Bazaar" with a section on documentation. The upshot is that we cannot accept the code as sufficient documentation for something this complex and there is a definite need for a complete higher level view. To meet that need there are several really good resources including "The Design and Implementation of the 4.4BSD Operating System", and "The Complete FreeBSD". There are,as well, several really good on-line reources, not least of which is the FreeBSD HowTo. I know there are more (not including the general Unix books) but titles escape me right now. Add the books to the FreeBSD specific web sites we already have, and i'm not sure the problem is lacking docs, rather slightly out of date docs due to an ambitious schedule of updates and releases. To start adding additional "Home of the Docs" sites would, IMHO, actually add to the confusion and difficulties. We would be much better served by people submitting pr's (where appropriate ;)) or suggestions that could be integrated into the existing docs. I'm not convinced (having wandered aimlessly down that road) the Linux style of documentation (1000's of sites, no real organization ;)) is the best bet here. On 23-Dec-1999 Mike s wrote: > Well, as i can see not many people care about the > documentation, or at least providing FreeBSD users > .......etc....................... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 18:35:34 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by hub.freebsd.org (Postfix) with ESMTP id 0725714C56; Thu, 23 Dec 1999 18:35:32 -0800 (PST) (envelope-from scottm@CS.UCLA.EDU) Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.192.128]) by mailman.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id SAA22597; Thu, 23 Dec 1999 18:36:18 -0800 (PST) Received: from cs.ucla.edu (localhost.cs.ucla.edu [127.0.0.1]) by mordred.cs.ucla.edu (8.9.3/UCLACS-5.0) with ESMTP id SAA01818; Thu, 23 Dec 1999 18:35:31 -0800 (PST) Message-ID: <3862DBF3.B0EC432B@cs.ucla.edu> Date: Thu, 23 Dec 1999 18:35:31 -0800 From: "B. Scott Michel" Organization: UCLA Computer Chaos X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RC i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: TCP Oddities followup References: <199912232255.OAA00872@mordred.cs.ucla.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Scott Michel wrote: > - tcpdump-ing the pn0 interface shows that the host thinks that it's > sending data. tcpdump-ing elsewhere in the network shows that pn0 > isn't actually transmitting anything into the wire. The host appears to be doing retransmissions but nothing goes out on the wire. > - This really is a TCP or interface bug because NFS connections don't > freeze using UDP. It's not just NFS. I can duplicate this behavior with scp and cvsup (things that do bulk data transfer.) -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 18:37:11 1999 Delivered-To: freebsd-stable@freebsd.org Received: from napalm.plano.sterling.com (napalm.plano.sterling.com [208.24.125.34]) by hub.freebsd.org (Postfix) with ESMTP id BB8D7157AC for ; Thu, 23 Dec 1999 18:37:00 -0800 (PST) (envelope-from alan.edmonds@sterling.com) Received: from sterling.com (ras-0018.plano.sterling.com [10.1.48.127]) by napalm.plano.sterling.com (8.9.1b+Sun/8.9.1) with ESMTP id UAA06111; Thu, 23 Dec 1999 20:33:29 -0600 (CST) Message-ID: <3862DB6A.9CCDD1C1@sterling.com> Date: Thu, 23 Dec 1999 20:33:14 -0600 From: Alan Edmonds X-Mailer: Mozilla 4.7 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Harlan Stenn Cc: "Nawfal M. Rouyan" , freebsd-stable@FreeBSD.ORG Subject: Re: localhost doesn't work? References: <16373.945984069@brown.pfcs.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I actually replaced the 'auto' with 'lo0' and that solved my problem. Perhaps this is the problem people are having with the install not enabling lo0. I'm not sure why the install set it to 'de0 auto'. BTW, ifconfig -l yields de0 lp0 tun0 sl0 ppp0 lo0 Thanks for the clarification. Alan Harlan Stenn wrote: > > rc.network says that if ${network_interfaces} is "auto" it will grab the > list of available interfaces from `ifconfig -l`. > > I don't think using "de0 auto" will do what you expect. > > Run "ifconfig -l" and see what it says. > > YTSL. > > H -- Alan Edmonds, KB5ZUY Sterling Software M/S 132 Phone: +1-972-801-6485 5800 Tennyson Pkwy. Email: alan.edmonds@sterling.com Plano, TX, USA 75024 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 18:38:14 1999 Delivered-To: freebsd-stable@freebsd.org Received: from guardian-ext.merrion.nua.net (guardian-ext.merrion.nua.net [195.7.46.2]) by hub.freebsd.org (Postfix) with ESMTP id 19F1814BDB for ; Thu, 23 Dec 1999 18:38:07 -0800 (PST) (envelope-from tony@nua.ie) Received: (from uucp@localhost) by guardian-ext.merrion.nua.net (8.8.8/8.8.6) id CAA15238; Fri, 24 Dec 1999 02:38:02 GMT Received: from ppp-remote.merrion.nua.net(195.7.46.118) via SMTP by guardian-int.merrion.nua.net, id smtpdX15236; Fri Dec 24 02:37:52 1999 From: Tony Byrne To: "Nawfal M. Rouyan" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: localhost doesn't work? Date: Fri, 24 Dec 1999 02:40:45 +0000 Organization: Nua Ltd. Reply-To: tony@nua.ie Message-ID: References: <19991223210100.38705.qmail@hotmail.com> In-Reply-To: <19991223210100.38705.qmail@hotmail.com> X-Mailer: Forte Agent 1.7/32.534 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Dec 1999 05:01:00 MYT, you wrote: >Hi, > I'm using freebsd 3.4 stable as of dec 22 1999. It seems that when I = ping=20 >localhost, there is no response. When I try to ftp localhost, also no=20 >response. > >amnesiac# ifconfig -a >ed1: flags=3D8843 mtu 1500 > inet 10.100.98.141 netmask 0xffffff00 broadcast 10.100.98.255 > ether 00:00:e8:e8:4c:2a >lp0: flags=3D8810 mtu 1500 >tun0: flags=3D8010 mtu 1500 >lo0: flags=3D8008 mtu 16384 This has been the case for me since 3.3-STABLE. If you look in /etc/defaults/rc.conf or /etc/rc.conf you'll see that the loopback (lo0) device isn't explicitly mentioned in the line that specifies which interfaces are to be configured at boot time. Instead there is an entry for 'auto'. I guess this is supposed to spot the loopback device and configure it. I just removed this and replaced it with 'lo0' and added the missing ifconfig line. It's probably not the correct thing to do, but it "worked for me(TM)". Regards, Tony. -- =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D Tony Byrne , Swords, Co. Dublin, Ireland. MP3 Musician http://www.mp3.com/tony_byrne Get your copy of the Winamp MP3 player: http://www.winamp.com =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Thu Dec 23 21:24:30 1999 Delivered-To: freebsd-stable@freebsd.org Received: from kot.ne.mediaone.net (kot.ne.mediaone.net [24.218.15.190]) by hub.freebsd.org (Postfix) with ESMTP id 14DF51577C; Thu, 23 Dec 1999 21:24:27 -0800 (PST) (envelope-from mi@kot.ne.mediaone.net) Received: from rtfm.newton (rtfm.newton [10.10.0.1]) by kot.ne.mediaone.net (8.9.3/8.9.1) with ESMTP id AAA31837; Fri, 24 Dec 1999 00:24:26 -0500 (EST) From: Mikhail Teterin X-Relay-IP: 10.10.0.1 Received: (from mi@localhost) by rtfm.newton (8.9.3/8.9.3) id AAA18524; Fri, 24 Dec 1999 00:24:25 -0500 (EST) (envelope-from mi@kot.ne.mediaone.net) Message-Id: <199912240524.AAA18524@rtfm.newton> Subject: fstat(2) not filling st_blksize? To: questions@freebsd.org, stable@freebsd.org Date: Fri, 24 Dec 1999 00:24:25 -0500 (EST) X-Face: %UW#n0|w>ydeGt/b@1-.UFP=K^~-:0f#O:D7w hJ5G_<5143Bb3kOIs9XpX+"V+~$adGP:J|SLieM31VIhqXeLBli" Message-Id: <199912240720.XAA10161@apollo.backplane.com> To: "B. Scott Michel" Cc: freebsd-current@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: TCP Oddities followup References: <199912232255.OAA00872@mordred.cs.ucla.edu> <3862DBF3.B0EC432B@cs.ucla.edu> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Scott Michel wrote: :> - tcpdump-ing the pn0 interface shows that the host thinks that it's :> sending data. tcpdump-ing elsewhere in the network shows that pn0 :> isn't actually transmitting anything into the wire. : :The host appears to be doing retransmissions but nothing goes out :on the wire. : :> - This really is a TCP or interface bug because NFS connections don't :> freeze using UDP. : :It's not just NFS. I can duplicate this behavior with scp and :cvsup (things that do bulk data transfer.) : : :-scooter Try doing a ping on the host with the pn0 interface to another machine. See if the packets it thinks it is sending get transmitted after a bunch of ping packets have accumulated. somethign like 'ping -i 0.03 remotehost' so it writes a lot of packets out. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 24 0:11:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id 41F331514F; Fri, 24 Dec 1999 00:11:18 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id AAA23160; Fri, 24 Dec 1999 00:11:18 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "freebsd-stable@FreeBSD. ORG" , , Subject: broken port... Date: Fri, 24 Dec 1999 00:11:34 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG cute one though Updater failed: Cannot install "/usr/ports/japanese/tk80/patches/#cvs.cvsup-1394.186" to "/usr/pobts/japanese/tk80/patches/patch-ab": No such file or directory /usr/pobts :) FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 24 0:19:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by hub.freebsd.org (Postfix) with ESMTP id 636D314E49; Fri, 24 Dec 1999 00:19:18 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.11 #1) id 121PyE-000JGk-00; Fri, 24 Dec 1999 10:21:06 +0200 From: Sheldon Hearn To: Mikhail Teterin Cc: questions@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: fstat(2) not filling st_blksize? In-reply-to: Your message of "Fri, 24 Dec 1999 00:24:25 EST." <199912240524.AAA18524@rtfm.newton> Date: Fri, 24 Dec 1999 10:21:06 +0200 Message-ID: <74073.946023666@axl.noc.iafrica.com> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 24 Dec 1999 00:24:25 EST, Mikhail Teterin wrote: > Whatever the filesystem I try (ufs, nfs, cd9660, mfs) I get the > st_blksize as zero after fstat(2)-ing the file on it. What version of FreeBSD are you using. On a 4-day-old 4.0-CURRENT, fstat(2) seems to fill st_bklsize correctly. The following sample code prints 8192 for every file I tested on my system. Ciao, Sheldon. #include #include #include #include #include int main(int argc, char *argv[]) { struct stat t; int fd; if (argc != 2) { (void)fprintf(stderr, "a single path argument is required\n"); return 1; } if ((fd = open(argv[0], O_RDONLY)) == -1) err(1, NULL); if (fstat(fd, &t) == -1) err(1, NULL); printf("%d\n", t.st_blksize); return 0; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 24 1:11:29 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tank.skynet.be (tank.skynet.be [195.238.2.35]) by hub.freebsd.org (Postfix) with ESMTP id 4F5FE14A00 for ; Fri, 24 Dec 1999 01:11:26 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by tank.skynet.be (8.9.3/odie-relay-v1.0) with ESMTP id KAA16933; Fri, 24 Dec 1999 10:11:18 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@foxbert.skynet.be Message-Id: In-Reply-To: <19991223203044.E1056@yedi.iaf.nl> References: <199912222226.XAA00562@dorifer.heim3.tu-clausthal.de> <19991223203044.E1056@yedi.iaf.nl> Date: Fri, 24 Dec 1999 09:24:59 +0100 To: Wilko Bulte , Brian Kraemer From: Brad Knowles Subject: Re: AMD 3DNow instructions on FreeBSD Cc: freebsd-stable@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:30 PM +0100 1999/12/23, Wilko Bulte wrote: > Sjeez. If that is true they should consider how much energy is wasted > because machines are not used to their capacity. Or alternatively the > same work could be done with less CPUs. > > Really, sounds like silly reason to me. Actually, no it's quite sane -- it's called quality control. They can't be certain that they don't have someone screwing around with the statistics if they're not running exactly the same code everywhere. This has been proved repeatedly on similar projects, not just SETI@home. -- These are my opinions -- not to be taken as official Skynet policy ____________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, News & FTP Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.11.11/12.49 B-1140 Brussels |o| |o| http://www.skynet.be Belgium |o| \/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/ Unix is like a wigwam -- no Gates, no Windows, and an Apache inside. Unix is very user-friendly. It's just picky who its friends are. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 24 10: 5:21 1999 Delivered-To: freebsd-stable@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 6565A15145; Fri, 24 Dec 1999 10:05:05 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.3/8.9.3) id MAA38631; Fri, 24 Dec 1999 12:04:57 -0600 (CST) (envelope-from dan) Date: Fri, 24 Dec 1999 12:04:57 -0600 From: Dan Nelson To: FreeBSD Cc: "freebsd-stable@FreeBSD. ORG" , freebsd-current@FreeBSD.ORG, freebsd-ports@FreeBSD.ORG Subject: Re: broken port... Message-ID: <19991224120457.A38490@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from "FreeBSD" on Fri Dec 24 00:11:34 GMT 1999 X-OS: FreeBSD 4.0-CURRENT Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Dec 24), FreeBSD said: > cute one though > > Updater failed: Cannot install > "/usr/ports/japanese/tk80/patches/#cvs.cvsup-1394.186" to > "/usr/pobts/japanese/tk80/patches/patch-ab": No such file or directory > > /usr/pobts :) You didn't provide much information, but it looks like you were running cvsup, right? If you run it again, does it have trouble on the same file? 'b' and 'r' are one bit apart from each other (01100010 and 01110010). Sounds like your machine flipped a bit. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Fri Dec 24 17:22:16 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mls.gtonet.net (mls.gtonet.net [216.112.90.195]) by hub.freebsd.org (Postfix) with ESMTP id AA79E14D03; Fri, 24 Dec 1999 17:22:11 -0800 (PST) (envelope-from freebsd@gtonet.net) Received: from pld (holeyman@pld.gtonet.net [216.112.90.200]) by mls.gtonet.net (8.9.3/8.9.3) with SMTP id RAA25783; Fri, 24 Dec 1999 17:22:03 -0800 (PST) (envelope-from freebsd@gtonet.net) From: "FreeBSD" To: "Dan Nelson" , "FreeBSD" Cc: "freebsd-stable@FreeBSD. ORG" , , Subject: RE: broken port... Date: Fri, 24 Dec 1999 17:22:27 -0800 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-reply-to: <19991224120457.A38490@dan.emsphone.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Importance: Normal Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Dan Nelson > Sent: Friday, December 24, 1999 10:05 AM > To: FreeBSD > Cc: freebsd-stable@FreeBSD. ORG; freebsd-current@FreeBSD.ORG; > freebsd-ports@FreeBSD.ORG > Subject: Re: broken port... > > > In the last episode (Dec 24), FreeBSD said: > > cute one though > > > > Updater failed: Cannot install > > "/usr/ports/japanese/tk80/patches/#cvs.cvsup-1394.186" to > > "/usr/pobts/japanese/tk80/patches/patch-ab": No such file or directory > > > > /usr/pobts :) > > You didn't provide much information, but it looks like you were running > cvsup, right? If you run it again, does it have trouble on the same > file? 'b' and 'r' are one bit apart from each other (01100010 and > 01110010). Sounds like your machine flipped a bit. > > -- > Dan Nelson > dnelson@emsphone.com > Yeah, I know, it wasnt a big deal. I just thought it was funny. I re-cvsupped and it was fine. It is old hardware (p133,128,6.4gEIDE,pn0) and it very well may have flipped a bit, good call. FreeBSD freebsd@gtonet.net "LinSUX is only free if your time is worthless" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 25 1:21:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: from web505.mail.yahoo.com (web505.mail.yahoo.com [128.11.68.72]) by hub.freebsd.org (Postfix) with SMTP id 22F13151AD for ; Sat, 25 Dec 1999 01:21:22 -0800 (PST) (envelope-from god@yahoo.com) Received: (qmail 14044 invoked by uid 60001); 25 Dec 1999 09:21:21 -0000 Message-ID: <19991225092121.14043.qmail@web505.mail.yahoo.com> Received: from [63.22.81.84] by web505.mail.yahoo.com; Sat, 25 Dec 1999 01:21:21 PST Date: Sat, 25 Dec 1999 01:21:21 -0800 (PST) From: Mike s Subject: Re: bugs in the handbook. (FreeBSD Portal) To: Colin Cc: 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 well yes i agree that the linux Documentation project is along the lines of what i am talking about, but again take linux.com for example. IF we had volunteers who had knowledge of the latest web development resources/languages such as sPHP we can start a site that is based mostly on volunteers as is linux.com Awhile back, there was a discussion on this questions and this mailing list about not nearly enough newbie documentation. So i guess we are a lacking in a few areas. but, its planting the seed that counts. again, not to compete at all with freebsd.org a separate entity entirely. besides, a lot of people who would commit to -docs don't have the knowledge or patience to learn the SGML structure if the site itself. I'd like to see a site going up utilizing php/mysql for fast and convenient site development. I guess i will start by saying that I am willing to donate a considerable ammount of time to working on this project. If anyone else is interested in helping out send me an email with subject "FreeBSD Portal Volunteer" and once we reach a sufficient ammount of volunteers. ( say 5 or 6 ) well, we can get things under way. Of course i am not looking for any financial gain only contribute to the success of my OS of choice. forward this email to any web developers or knowledgable FreeBSD Users and lets plant a seed. happy holidays mike god@yahoo.com --- Colin wrote: > I don't think we don't care about the > documentation, that strikes me as > something of an oversimplification. There are 2 > distinct problems here: > 1) The peole who know enough about the system to > document it properly > generally don't have the time (or > inclination...gotta love those programmers ;)) > to spend on documentation. They're too busy fixing > the problems that turn up > regularly or adding enhancements (which is where > most of the problems start ;)). > 2) The peole who are most willing to spend time on > the documentation don't have > the specific knowledge to do it. They are the one's > who would like to be > reading the docs. > Yes, I know it's inappropriate to generalize > that much, but I think you > get the idea. There is, of course, quite a lot of > good documentation out there > already, most of it accessible on-line. There is a > definite need for ongoing > improvement and upgrading, but I don't think that > surprises anyone. > There's an interesting article at > http://www.firstmonday.org/issues/issue4_12/bezroukov/index.html > that talks > about the problems of documentation in the Open > Software world. Actually, it > is just a really good second look at the "Cathedral > and Bazaar" with a section > on documentation. The upshot is that we cannot > accept the code as sufficient > documentation for something this complex and there > is a definite need for a > complete higher level view. > To meet that need there are several really good > resources including "The > Design and Implementation of the 4.4BSD Operating > System", and "The Complete > FreeBSD". There are,as well, several really good > on-line reources, not least > of which is the FreeBSD HowTo. I know there are > more (not including the general > Unix books) but titles escape me right now. > Add the books to the FreeBSD specific web sites > we already have, and i'm > not sure the problem is lacking docs, rather > slightly out of date docs due to an > ambitious schedule of updates and releases. > To start adding additional "Home of the Docs" > sites would, IMHO, actually > add to the confusion and difficulties. We would be > much better served by > people submitting pr's (where appropriate ;)) or > suggestions that could be > integrated into the existing docs. I'm not convinced > (having wandered aimlessly > down that road) the Linux style of documentation > (1000's of sites, no real > organization ;)) is the best bet here. > > On 23-Dec-1999 Mike s wrote: > > Well, as i can see not many people care about the > > documentation, or at least providing FreeBSD users > > .......etc....................... > _________________________________________________________ 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 Sat Dec 25 3: 7:45 1999 Delivered-To: freebsd-stable@freebsd.org Received: from hungry.spb.cityline.ru (hungry.spb.cityline.ru [212.46.192.3]) by hub.freebsd.org (Postfix) with ESMTP id 438E514CA8 for ; Sat, 25 Dec 1999 03:07:40 -0800 (PST) (envelope-from lev@imc.macro.ru) Received: from lev.sereb.net (ip-971.dialup.cl.spb.ru [212.46.198.3]) by hungry.spb.cityline.ru (8.8.8/8.8/CL) with ESMTP id OAA27163 for ; Sat, 25 Dec 1999 14:03:51 +0300 (MSK) Date: Sat, 25 Dec 1999 00:50:01 +0300 From: Lev Serebryakov X-Mailer: The Bat! (v1.36) S/N F29DEE5D / Educational X-Priority: 3 (Normal) Message-ID: <1034.991225@imc.macro.ru> To: All Subject: strange named behavior in 3.4-STABLE 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 Hi, All! I've upgraded from 3.3-STABLE to 3.4-STABLE and notice strange thing: I have ``named'' run on my machine, which have only dial-up Internet connection. I have ``ppp -nat -auto provider'' run too. My named have configured to be primary NS in my network (domain is not registered and IP addresses are from 192.168.xx.xx range). Also, named have ``forward-only'' option and two addresses of my ISP DNS. Whet it was 3.3-STABLE (really -- 3.3-RELEASE with stable kernel) everything works perfectly. PPP doesn't call my ISP until I (or somebody in local network) need connection. But with new system (3.4-RELEASE) ``named'' initiate dial-up just after start! Why new named want to connect when there is no any outgoing packets? How could I disable such behavior? Lev Serebryakov, 2:5030/661.0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 25 4:49: 3 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 595F214CB6; Sat, 25 Dec 1999 04:49:00 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 46F6E1CD43B; Sat, 25 Dec 1999 04:49:00 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 25 Dec 1999 04:49:00 -0800 (PST) From: Kris Kennaway To: Vivek Khera Cc: freebsd-stable@freebsd.org Subject: Re: three files in /usr/sbin not updated by make world In-Reply-To: <14431.51803.933833.985122@onceler.kcilink.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 Tue, 21 Dec 1999, Vivek Khera wrote: > Three programs in /usr/sbin were not updated. This machine was > initially installed a couple of weeks ago using the 3.3-RELEASE CD, > and had make world done on it on December 9 as well. > -r-xr-xr-x 2 root wheel 3148 Sep 16 18:48 ulaw2alaw* > -r-xr-xr-x 2 root wheel 3148 Sep 16 18:48 alaw2ulaw* Hmm, these probably either came from some software you compiled and installed yourself (not a port) -- the most likely explanation -- or from a port which does the wrong thing and installs under /usr/sbin. You can check whether it's the latter by doing cd /var/db/pkg grep alaw2ulaw */+CONTENTS to see which package you have installed which contains them. If they came from a package then it's probably a bug which you should submit a problem report for (see the handbook) Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 25 7:12:31 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail2.bna.bellsouth.net (mail2.bna.bellsouth.net [205.152.150.14]) by hub.freebsd.org (Postfix) with ESMTP id 3C41214E7E for ; Sat, 25 Dec 1999 07:12:29 -0800 (PST) (envelope-from jim@siteplus.com) Received: from siteplus.com (host-209-215-8-9.cha.bellsouth.net [209.215.8.9]) by mail2.bna.bellsouth.net (3.3.5alt/0.75.2) with ESMTP id KAA02549; Sat, 25 Dec 1999 10:12:00 -0500 (EST) Message-ID: <3864DED4.9633BA0E@siteplus.com> Date: Sat, 25 Dec 1999 10:12:21 -0500 From: Jim Weeks X-Mailer: Mozilla 4.51 [en] (X11; I; Linux 2.2.5-15 i586) X-Accept-Language: en MIME-Version: 1.0 To: Lev Serebryakov Cc: All Subject: Re: strange named behavior in 3.4-STABLE References: <1034.991225@imc.macro.ru> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Your problem is most likely sendmail. It will always issue a request when booting and if you have the standard "sendmail -bd -q30m" set in /etc/rc.conf it will cause dial up every 30 minutes. You could change the command to "sendmail -bd" to stop the 30 minute dialing, but it will still dial during boot. Good luck, Jim Weeks Lev Serebryakov wrote: > Whet it was 3.3-STABLE (really -- 3.3-RELEASE with stable kernel) > everything works perfectly. PPP doesn't call my ISP until I (or > somebody in local network) need connection. > But with new system (3.4-RELEASE) ``named'' initiate dial-up just > after start! Why new named want to connect when there is no any > outgoing packets? How could I disable such behavior? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 25 8:55:32 1999 Delivered-To: freebsd-stable@freebsd.org Received: from germanium.xtalwind.net (germanium.xtalwind.net [205.160.242.5]) by hub.freebsd.org (Postfix) with ESMTP id 7AD0D15029; Sat, 25 Dec 1999 08:55:17 -0800 (PST) (envelope-from jack@germanium.xtalwind.net) Received: from localhost (jack@localhost) by germanium.xtalwind.net (8.10.0.Beta10/8.10.0.Beta10) with ESMTP id dBPGt7G83494; Sat, 25 Dec 1999 11:55:07 -0500 (EST) Date: Sat, 25 Dec 1999 11:55:07 -0500 (EST) From: jack To: Kris Kennaway Cc: Vivek Khera , freebsd-stable@FreeBSD.ORG Subject: Re: three files in /usr/sbin not updated by make world 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 Today Kris Kennaway wrote: > On Tue, 21 Dec 1999, Vivek Khera wrote: > > > Three programs in /usr/sbin were not updated. This machine was > > initially installed a couple of weeks ago using the 3.3-RELEASE CD, > > and had make world done on it on December 9 as well. > > > -r-xr-xr-x 2 root wheel 3148 Sep 16 18:48 ulaw2alaw* > > -r-xr-xr-x 2 root wheel 3148 Sep 16 18:48 alaw2ulaw* > > Hmm, these probably either came from some software you compiled and > installed yourself (not a port) -- the most likely explanation -- or from > a port which does the wrong thing and installs under /usr/sbin. They're leftovers from the isdn4bsd upgrade from version 0.71 to 0.81 back in May. You'll find the source, and man pages, in the src/usr.sbin/i4b/alawulaw directory in the Attic. -------------------------------------------------------------------------- Jack O'Neill Systems Administrator / Systems Analyst jack@germanium.xtalwind.net Crystal Wind Communications, Inc. Finger jack@germanium.xtalwind.net for my PGP key. PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67 FD 09 E9 3C 5F CC EB CD enriched, vcard, HTML messages > /dev/null -------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 25 9: 9:27 1999 Delivered-To: freebsd-stable@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 01A0914CC5; Sat, 25 Dec 1999 09:09:25 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E4F731CD821; Sat, 25 Dec 1999 09:09:25 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sat, 25 Dec 1999 09:09:25 -0800 (PST) From: Kris Kennaway To: jack Cc: Vivek Khera , freebsd-stable@FreeBSD.ORG Subject: Re: three files in /usr/sbin not updated by make world 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 Sat, 25 Dec 1999, jack wrote: > > Hmm, these probably either came from some software you compiled and > > installed yourself (not a port) -- the most likely explanation -- or from > > a port which does the wrong thing and installs under /usr/sbin. > > They're leftovers from the isdn4bsd upgrade from version 0.71 to > 0.81 back in May. You'll find the source, and man pages, in the > src/usr.sbin/i4b/alawulaw directory in the Attic. Ah yes, good work :-) I got confused and thought these were audio tools. Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 25 9:25:22 1999 Delivered-To: freebsd-stable@freebsd.org Received: from foobar.franken.de (foobar.franken.de [194.94.249.81]) by hub.freebsd.org (Postfix) with ESMTP id A331A14D88; Sat, 25 Dec 1999 09:25:17 -0800 (PST) (envelope-from logix@foobar.franken.de) Received: (from logix@localhost) by foobar.franken.de (8.8.8/8.8.5) id SAA14290; Sat, 25 Dec 1999 18:24:48 +0100 (CET) Message-ID: <19991225182447.A13338@foobar.franken.de> Date: Sat, 25 Dec 1999 18:24:47 +0100 From: Harold Gutch To: Kris Kennaway , jack Cc: Vivek Khera , freebsd-stable@FreeBSD.ORG Subject: Re: three files in /usr/sbin not updated by make world References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Kris Kennaway on Sat, Dec 25, 1999 at 09:09:25AM -0800 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Dec 25, 1999 at 09:09:25AM -0800, Kris Kennaway wrote: > On Sat, 25 Dec 1999, jack wrote: > > > > Hmm, these probably either came from some software you compiled and > > > installed yourself (not a port) -- the most likely explanation -- or from > > > a port which does the wrong thing and installs under /usr/sbin. > > > > They're leftovers from the isdn4bsd upgrade from version 0.71 to > > 0.81 back in May. You'll find the source, and man pages, in the > > src/usr.sbin/i4b/alawulaw directory in the Attic. > > Ah yes, good work :-) I got confused and thought these were audio tools. They in fact *are* audio tools used by the scripts/programs in i4b providing answering machine functions. bye, Harold -- 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 Sat Dec 25 10:25:26 1999 Delivered-To: freebsd-stable@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 71F1114BF6; Sat, 25 Dec 1999 10:25:23 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA62936; Sat, 25 Dec 1999 10:25:21 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <199912251825.KAA62936@gndrsh.dnsmgr.net> Subject: Re: three files in /usr/sbin not updated by make world In-Reply-To: from Kris Kennaway at "Dec 25, 1999 04:49:00 am" To: kris@hub.freebsd.org (Kris Kennaway) Date: Sat, 25 Dec 1999 10:25:20 -0800 (PST) Cc: khera@kciLink.com (Vivek Khera), freebsd-stable@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 21 Dec 1999, Vivek Khera wrote: > > > Three programs in /usr/sbin were not updated. This machine was > > initially installed a couple of weeks ago using the 3.3-RELEASE CD, > > and had make world done on it on December 9 as well. > > > -r-xr-xr-x 2 root wheel 3148 Sep 16 18:48 ulaw2alaw* > > -r-xr-xr-x 2 root wheel 3148 Sep 16 18:48 alaw2ulaw* > > Hmm, these probably either came from some software you compiled and > installed yourself (not a port) -- the most likely explanation -- or from > a port which does the wrong thing and installs under /usr/sbin. Nahhh... this was/is part of the i4b ISDN software: gndrsh:rgrimes {655}% find . -name ulaw\* ./usr.sbin/i4b/alawulaw/ulaw2alaw.1 Since that software just went through major revision in -stable this is probably old cruft that can be blown away... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 25 14:36:19 1999 Delivered-To: freebsd-stable@freebsd.org Received: from mail.ulstu.ru (ns.ulstu.ru [62.76.34.36]) by hub.freebsd.org (Postfix) with ESMTP id E72F114BE1 for ; Sat, 25 Dec 1999 14:36:06 -0800 (PST) (envelope-from vss@mail.ulstu.ru) Received: (from vss@localhost) by mail.ulstu.ru (8.8.5-MVC-230198/8.8.7) id BAA43776 for freebsd-stable@FreeBSD.ORG; Sun, 26 Dec 1999 01:35:52 +0300 (MSK) (envelope-from vss) Date: Sun, 26 Dec 1999 01:35:52 +0300 From: Vlad Skvortsov To: freebsd-stable@FreeBSD.ORG Subject: Re: /bin/test broken ? Message-ID: <19991226013551.A43483@ulstu.ru> Mail-Followup-To: freebsd-stable@FreeBSD.ORG References: <99Dec23.123516est.40332@border.alcanet.com.au> <199912232030.MAA65714@pau-amma.whistle.com> <99Dec24.105638est.40325@border.alcanet.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <99Dec24.105638est.40325@border.alcanet.com.au> Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Dec 24, 1999 at 11:05:35AM +1100, Peter Jeremy wrote: > >>That said, the error message should have been: > >> test: ]: unexpected operator > >>and it is not clear why you are getting `[' reported as the program > >>name. > > > >Well, /bin/test and /bin/[ are links to the same inode: > > Agreed, but the error message is printed by errx(3). errx(3) prints > __progname (which is effectively equivalent to argv[0]) as the program > name - ie the name by which the program was invoked. > > test(1) includes a check near the beginning to see it it was invoked as > `[' and if it was it checks to see that the last argument is `]' and > deletes it if it was. In both cases, the remaining arguments are then > passed to the expression evaluator. Why I did an original post is because it appeared that my cron job doesn't work any more: Date: Sun, 26 Dec 1999 01:30:01 +0300 (MSK) From: root@spc.high (Cron Daemon) To: vlad@spc.high Subject: Cron /bin/[ -f /var/run/INET ] && /usr/local/bin/fetchmail From root@spc.high Sun Dec 26 01:30:03 1999 [: ]: unexpected operator It _did_ work before. I put your attention that you'd try using /bin/[, not just [ (as someone on this list did). The latter is executed by shell, obviously. Judjed by my logs the last change to /bin/test was on Dec, 16 or somewhere about. -- Vlad Skvortsov, vss@ulstu.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 25 16:50:58 1999 Delivered-To: freebsd-stable@freebsd.org Received: from tricord.system.pl (tricord.system.pl [195.205.185.10]) by hub.freebsd.org (Postfix) with ESMTP id 692E7151DE for ; Sat, 25 Dec 1999 16:50:52 -0800 (PST) (envelope-from saper@system.pl) Received: from localhost (saper@localhost [127.0.0.1]) by tricord.system.pl (SYSTEM Internet) with ESMTP id BAA26222 for ; Sun, 26 Dec 1999 01:50:58 +0100 (MET) Date: Sun, 26 Dec 1999 01:50:28 +0100 (MET) From: Marcin Cieslak To: Lev Serebryakov Subject: Re: strange named behavior in 3.4-STABLE In-Reply-To: <1034.991225@imc.macro.ru> 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 guess the problem is that some utility attempts do use DNS quite early, like sendmail(1). Most probably, you messed up your /etc/hosts file, if not - you may use "DontProbeInterfaces" sendmail option. -- << Marcin Cieslak // saper@system.pl >> ----------------------------------------------------------------- SYSTEM Internet Provider http://www.system.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message From owner-freebsd-stable Sat Dec 25 22:21: 6 1999 Delivered-To: freebsd-stable@freebsd.org Received: from smtp6.mindspring.com (smtp6.mindspring.com [207.69.200.110]) by hub.freebsd.org (Postfix) with ESMTP id 7FBF8151FD for ; Sat, 25 Dec 1999 22:20:57 -0800 (PST) (envelope-from mvh@ix.netcom.com) Received: from netcom1.netcom.com (lai-ca3d-49.ix.netcom.com [209.110.243.49]) by smtp6.mindspring.com (8.9.3/8.8.5) with ESMTP id BAA22043; Sun, 26 Dec 1999 01:20:47 -0500 (EST) Received: by netcom1.netcom.com (Postfix, from userid 1000) id C5ACEA5F26; Sat, 25 Dec 1999 22:20:23 -0800 (PST) From: Mike Harding To: lev@imc.macro.ru Cc: freebsd-stable@FreeBSD.ORG In-reply-to: <1034.991225@imc.macro.ru> (message from Lev Serebryakov on Sat, 25 Dec 1999 00:50:01 +0300) Subject: Re: strange named behavior in 3.4-STABLE References: <1034.991225@imc.macro.ru> Message-Id: <19991226062023.C5ACEA5F26@netcom1.netcom.com> Date: Sat, 25 Dec 1999 22:20:23 -0800 (PST) Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It's an issue with the new version of Bind - 8.2.2 seems to ping the network on startup, whereas the previous version did not. I haven't found a way around this behaviour but that doesn't mean there isn't one. I noticed this behaviour when I was an early 8.2 adapter via the ports. - Mike H. Date: Sat, 25 Dec 1999 00:50:01 +0300 From: Lev Serebryakov X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.ORG Precedence: bulk X-RULES: lists Hi, All! I've upgraded from 3.3-STABLE to 3.4-STABLE and notice strange thing: I have ``named'' run on my machine, which have only dial-up Internet connection. I have ``ppp -nat -auto provider'' run too. My named have configured to be primary NS in my network (domain is not registered and IP addresses are from 192.168.xx.xx range). Also, named have ``forward-only'' option and two addresses of my ISP DNS. Whet it was 3.3-STABLE (really -- 3.3-RELEASE with stable kernel) everything works perfectly. PPP doesn't call my ISP until I (or somebody in local network) need connection. But with new system (3.4-RELEASE) ``named'' initiate dial-up just after start! Why new named want to connect when there is no any outgoing packets? How could I disable such behavior? Lev Serebryakov, 2:5030/661.0 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