From owner-freebsd-current Sun Jan 30 0:54:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx2.x-treme.gr (mx2.x-treme.gr [212.120.192.15]) by hub.freebsd.org (Postfix) with ESMTP id C163B152C7 for ; Sun, 30 Jan 2000 00:54:48 -0800 (PST) (envelope-from keramida@diogenis.ceid.upatras.gr) Received: from hades.hell.gr (pat12.x-treme.gr [212.120.197.204]) by mx2.x-treme.gr (8.9.3/8.9.3/IPNG-ADV-ANTISPAM-0.1) with SMTP id KAA13458 for ; Sun, 30 Jan 2000 10:54:33 +0200 Received: (qmail 10766 invoked by uid 1001); 30 Jan 2000 07:40:43 -0000 Date: Sun, 30 Jan 2000 09:40:43 +0200 From: Giorgos Keramidas To: Jun Kuriyama Cc: current@FreeBSD.org Subject: Re: "rm -rf" behavior on readonly nfs Message-ID: <20000130094043.B10414@hades.hell.gr> Reply-To: keramida@ceid.upatras.gr References: <86aeloo22e.wl@localhost.sky.rim.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <86aeloo22e.wl@localhost.sky.rim.or.jp>; from kuriyama@sky.rim.or.jp on Sun, Jan 30, 2000 at 09:06:33AM +0900 X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E X-Phone-Number: +30-94-6203692, +30-93-2886457 X-Address: Theodorou Kirinaiou 61, 26334 Patra, Greece Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 30, 2000 at 09:06:33AM +0900, Jun Kuriyama wrote: > > I found difference between "rm -rf" for non-exist file on readonly nfs > and usual non-writable directory. > > In this example, /usr/src is readonly nfs mounted and /usr/bin is > normal filesystem but not writable. And file "a" is not exist. > > ----- > % rm /usr/bin/a > rm: /usr/bin/a: No such file or directory > % rm -f /usr/bin/a > % rm -rf /usr/bin/a > % rm /usr/src/a > rm: /usr/src/a: No such file or directory > % rm -f /usr/src/a > % rm -rf /usr/src/a > rm: /usr/src/a: Read-only file system > % > ----- > > For "-f" option, last behavior is expected one, or not? This happens on either NFS-mounted or real directories. It think that since the manual of rm(1) says: -f Attempt to remove the files without prompting for confirma- tion, regardless of the file's permissions. If the file does not exist, do not display a diagnostic message or modify the exit status to reflect an error. it ought to print nothing in such a case. Let me know if the small patch shown below helps in correcting this. I can't check this cause I got bitten by getflags() in(s)anity last night when I cvsup'ed. The diff -u output is: %%% patch begins here %%% --- /usr/src/bin/rm/rm.c Sat Jan 29 01:14:23 2000 +++ rm.c Sun Jan 30 09:32:18 2000 @@ -196,7 +196,9 @@ } continue; case FTS_ERR: - errx(1, "%s: %s", p->fts_path, strerror(p->fts_errno)); + if (!fflag) + errx(1, "%s: %s", p->fts_path, + strerror(p->fts_errno)); case FTS_NS: /* * FTS_NS: assume that if can't stat the file, it %%% patch ends here %%% -- Giorgos Keramidas, < keramida @ ceid . upatras . gr > "Don't let your schooling interfere with your education." [Mark Twain] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 0:55: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from mx2.x-treme.gr (mx2.x-treme.gr [212.120.192.15]) by hub.freebsd.org (Postfix) with ESMTP id 8D155152C2 for ; Sun, 30 Jan 2000 00:54:48 -0800 (PST) (envelope-from keramida@diogenis.ceid.upatras.gr) Received: from hades.hell.gr (pat12.x-treme.gr [212.120.197.204]) by mx2.x-treme.gr (8.9.3/8.9.3/IPNG-ADV-ANTISPAM-0.1) with SMTP id KAA13450 for ; Sun, 30 Jan 2000 10:54:33 +0200 Received: (qmail 10766 invoked by uid 1001); 30 Jan 2000 07:40:43 -0000 Date: Sun, 30 Jan 2000 09:40:43 +0200 From: Giorgos Keramidas To: Jun Kuriyama Cc: current@FreeBSD.org Subject: Re: "rm -rf" behavior on readonly nfs Message-ID: <20000130094043.B10414@hades.hell.gr> Reply-To: keramida@ceid.upatras.gr References: <86aeloo22e.wl@localhost.sky.rim.or.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <86aeloo22e.wl@localhost.sky.rim.or.jp>; from kuriyama@sky.rim.or.jp on Sun, Jan 30, 2000 at 09:06:33AM +0900 X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E X-Phone-Number: +30-94-6203692, +30-93-2886457 X-Address: Theodorou Kirinaiou 61, 26334 Patra, Greece Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 30, 2000 at 09:06:33AM +0900, Jun Kuriyama wrote: > > I found difference between "rm -rf" for non-exist file on readonly nfs > and usual non-writable directory. > > In this example, /usr/src is readonly nfs mounted and /usr/bin is > normal filesystem but not writable. And file "a" is not exist. > > ----- > % rm /usr/bin/a > rm: /usr/bin/a: No such file or directory > % rm -f /usr/bin/a > % rm -rf /usr/bin/a > % rm /usr/src/a > rm: /usr/src/a: No such file or directory > % rm -f /usr/src/a > % rm -rf /usr/src/a > rm: /usr/src/a: Read-only file system > % > ----- > > For "-f" option, last behavior is expected one, or not? This happens on either NFS-mounted or real directories. It think that since the manual of rm(1) says: -f Attempt to remove the files without prompting for confirma- tion, regardless of the file's permissions. If the file does not exist, do not display a diagnostic message or modify the exit status to reflect an error. it ought to print nothing in such a case. Let me know if the small patch shown below helps in correcting this. I can't check this cause I got bitten by getflags() in(s)anity last night when I cvsup'ed. The diff -u output is: %%% patch begins here %%% --- /usr/src/bin/rm/rm.c Sat Jan 29 01:14:23 2000 +++ rm.c Sun Jan 30 09:32:18 2000 @@ -196,7 +196,9 @@ } continue; case FTS_ERR: - errx(1, "%s: %s", p->fts_path, strerror(p->fts_errno)); + if (!fflag) + errx(1, "%s: %s", p->fts_path, + strerror(p->fts_errno)); case FTS_NS: /* * FTS_NS: assume that if can't stat the file, it %%% patch ends here %%% -- Giorgos Keramidas, < keramida @ ceid . upatras . gr > "Don't let your schooling interfere with your education." [Mark Twain] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 0:56:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from eagle.prod.itd.earthlink.net (eagle.prod.itd.earthlink.net [207.217.120.24]) by hub.freebsd.org (Postfix) with ESMTP id 99F6A152C7; Sun, 30 Jan 2000 00:56:40 -0800 (PST) (envelope-from eogren@earthlink.net) Received: from rod.darktech.org (ip192.cambridge2.ma.pub-ip.psi.net [38.32.112.192]) by eagle.prod.itd.earthlink.net (8.9.3/8.9.3) with ESMTP id AAA19172; Sun, 30 Jan 2000 00:56:37 -0800 (PST) Received: by rod.darktech.org (Postfix, from userid 1001) id B3B641A8; Sun, 30 Jan 2000 03:57:19 -0500 (EST) Date: Sun, 30 Jan 2000 03:57:19 -0500 From: Eric Ogren To: "Daniel C. Sobral" Cc: Jean-Marc Zucconi , current@FreeBSD.ORG Subject: Re: Loader.rc: unknown command Message-ID: <20000130035719.B4090@earthlink.net> References: <200001300528.GAA00406@qix.jmz.org> <3893D11E.B8F95AA6@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <3893D11E.B8F95AA6@newsguy.com>; from dcs@newsguy.com on Sun, Jan 30, 2000 at 02:50:22PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 30, 2000 at 02:50:22PM +0900, Daniel C. Sobral wrote: > Jean-Marc Zucconi wrote: > > > > With a new installed world I get this message at boot: > > > > > \ Loader.rc > > Loader.rc: unknown command > > > > Fortunately this does not prevent the machine to boot :-) > > Any clue? > > The \ command is not working correctly, resulting in the "Loader.rc" > comment being executed instead of ignored. > > Why? I don't have a clue. Is *ANYONE* being able to reproduce this > problem? If so, please contact me ASAP, since we have almost no time to > fix this before 4.0-RELEASE. > > Jean, I need more information about your setup. What was it running > before? How did you install this new world? Did you ever touch any file > in /boot? Can you give me a date of your world source? > I can reproduce this. My world source was cvsuped on Fri 1/28 @ ~1:30EST. Before, it was running code from two weeks ago (1/14). I get the exact same error message as Jean-Marc. All I did was a make buildworld, make installworld, and the only file I've ever touched in /boot is loader.conf.local. Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 1: 0:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id BFDDC14C96 for ; Sun, 30 Jan 2000 01:00:37 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 535 invoked from network); 30 Jan 2000 09:00:26 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 30 Jan 2000 09:00:26 -0000 Date: Sun, 30 Jan 2000 20:00:22 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: John Baldwin Cc: current@FreeBSD.org, committers@FreeBSD.org, Jeroen Ruigrok van der Werven Subject: RE: More world breakage In-Reply-To: <200001300606.BAA46567@server.baldwin.cx> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, John Baldwin wrote: > On 29-Jan-00 Bruce Evans wrote: > One > question though, what architecture *should* the install-tools be? Whichever system they run on. This can be the host machine even for cross-compiling, if the target root is remote mounted. The main problem with this in -current is that some install rules put ${DESTDIR} in the installed files. perl is the main offender. > Normally, one would run installworld on the target machine and not > necessarily the host machine. For example, if I was cross-building an > axp world on my x86 machine, then I would want to run 'make buildworld' > on the x86, but would want to run 'make installworld' on the axp. Thus, It should be sufficient to copy at most a new install(1) from the host's obj dirs (except for a bare target machine, you need something like sysinstall to put a bit more than ssh there to begin with). Unfortunately, some bad install rules build things under ${DESTDIR} at install time and need much more than install(1) to do it. Guess what is the main offender. > the build tools in that case need to be x86 binaries, but the install > tools need to be axp binaries. Of course, in that case you can't use > the build machine's header files or libraries to build the install tools. > Thus, you could use the headers/binaries in the source tree, except that > you might then end up linking against a newer libc that needs a newer > kernel to run. ... This problem is not limited to the install tools. After installing a new /bin/sh, you had better have a kernel that can run it. Problems can be reduced by linking new (target) tools static (if the target supports static linkage). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 1: 2:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 61863152CF for ; Sun, 30 Jan 2000 01:02:17 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id BAA34363; Sun, 30 Jan 2000 01:02:17 -0800 (PST) (envelope-from dillon) Date: Sun, 30 Jan 2000 01:02:17 -0800 (PST) From: Matthew Dillon Message-Id: <200001300902.BAA34363@apollo.backplane.com> To: Giorgos Keramidas Cc: Jun Kuriyama , current@FreeBSD.ORG Subject: Re: "rm -rf" behavior on readonly nfs References: <86aeloo22e.wl@localhost.sky.rim.or.jp> <20000130094043.B10414@hades.hell.gr> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :This happens on either NFS-mounted or real directories. It think that since :the manual of rm(1) says: : : -f Attempt to remove the files without prompting for confirma- : tion, regardless of the file's permissions. If the file does : not exist, do not display a diagnostic message or modify the : exit status to reflect an error. : :it ought to print nothing in such a case. Let me know if the small patch :shown below helps in correcting this. I can't check this cause I got bitten :by getflags() in(s)anity last night when I cvsup'ed. No, it should definitely print an error. If the file didn't exist it should stay silent but if the file exists and cannot be removed, that should generate an error. The -f option does not mean "silently fail", it simply means that no error message should be printed if the error is innocuous. i.e. you try to remove a file that is already removed. -Matt Matthew Dillon :The diff -u output is: : :%%% patch begins here %%% :--- /usr/src/bin/rm/rm.c Sat Jan 29 01:14:23 2000 :+++ rm.c Sun Jan 30 09:32:18 2000 :@@ -196,7 +196,9 @@ : } : continue; : case FTS_ERR: :- errx(1, "%s: %s", p->fts_path, strerror(p->fts_errno)); :+ if (!fflag) :+ errx(1, "%s: %s", p->fts_path, :+ strerror(p->fts_errno)); : case FTS_NS: : /* : * FTS_NS: assume that if can't stat the file, it :%%% patch ends here %%% : :-- :Giorgos Keramidas, < keramida @ ceid . upatras . gr > :"Don't let your schooling interfere with your education." [Mark Twain] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 1:33:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 278B6152C2 for ; Sun, 30 Jan 2000 01:33:50 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 1819 invoked from network); 30 Jan 2000 09:32:55 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 30 Jan 2000 09:32:55 -0000 Date: Sun, 30 Jan 2000 20:32:51 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Jun Kuriyama Cc: current@FreeBSD.ORG Subject: Re: "rm -rf" behavior on readonly nfs In-Reply-To: <86aeloo22e.wl@localhost.sky.rim.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, Jun Kuriyama wrote: > I found difference between "rm -rf" for non-exist file on readonly nfs > and usual non-writable directory. > > In this example, /usr/src is readonly nfs mounted and /usr/bin is > normal filesystem but not writable. And file "a" is not exist. > > ----- > % rm /usr/bin/a > rm: /usr/bin/a: No such file or directory > % rm -f /usr/bin/a > % rm -rf /usr/bin/a > % rm /usr/src/a > rm: /usr/src/a: No such file or directory > % rm -f /usr/src/a > % rm -rf /usr/src/a > rm: /usr/src/a: Read-only file system > % > ----- > > For "-f" option, last behavior is expected one, or not? The kernel returns EROFS for unlink() without even looking up the last component of the filename. This is a cosmetic bug IMO. The errors listed in POSIX.1 are not required to be checked for in the given order. However, checking in that order usually gives the most logical results. For unlink() and similar syscalls, EROFS is at the end of the list. Once unlink() returns EROFS, POSIX.2 requires the error to be reported for rm -f (POSIX.2 requires rm -f to be silent about ENOENT but not about all other errors). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 1:50:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 76C1015018; Sun, 30 Jan 2000 01:50:19 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.10.0.Beta6/8.10.0.Beta6) with ESMTP id e0U9jcw67854; Sun, 30 Jan 2000 11:45:38 +0200 (SAST) Message-Id: <200001300945.e0U9jcw67854@gratis.grondar.za> To: Bruce Evans Cc: John Baldwin , current@FreeBSD.org, committers@FreeBSD.org, Jeroen Ruigrok van der Werven Subject: Re: More world breakage References: In-Reply-To: ; from Bruce Evans "Sun, 30 Jan 2000 20:00:22 +1100." Date: Sun, 30 Jan 2000 11:45:38 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Whichever system they run on. This can be the host machine even for > cross-compiling, if the target root is remote mounted. The main problem > with this in -current is that some install rules put ${DESTDIR} in the > installed files. perl is the main offender. Which install rules? I'd like to fix this. (I know libraries are a big mess). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 2:10:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 0583F14C8F; Sun, 30 Jan 2000 02:10:27 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA46338; Sun, 30 Jan 2000 11:07:58 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001301007.LAA46338@freebsd.dk> Subject: Re: Still problems with latest ATA In-Reply-To: from Kris Kennaway at "Jan 29, 2000 11:04:24 pm" To: kris@hub.freebsd.org (Kris Kennaway) Date: Sun, 30 Jan 2000 11:07:58 +0100 (CET) Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kris Kennaway wrote: > My CDROM still refuses to work with cdcontrol, although the 30-seconds of > kernel spinning is now fixed. > > Trying to play a track gives: > > acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04 I'll bet this drive doesn't support PLAY_BIG but only PLAY_MSF. The problem here is that PLAY_MSF's parameters are either in binary or in BCD, but you dont know which one to use, as this is screwed in more drives than those missing PLAY_BIG. > One of my WDC's still falls back to PIO mode at boot time (see previous > messages, nothing has changed). Its not able to do DMA then, besides cluttering up the console with the retries, it does work afterwards right ? > If anything has changed in the verbose boot I can provide a copy of it, > otherwise all my relevant details are in the archives from previous > messages.. Send me one, there are a few changed items, I'll see what can be done... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 2:26:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mindcrime.bit0.com (mindcrime.bit0.com [207.246.72.162]) by hub.freebsd.org (Postfix) with ESMTP id 16CEA15151 for ; Sun, 30 Jan 2000 02:26:51 -0800 (PST) (envelope-from mandrews@bit0.com) Received: from localhost (mandrews@localhost) by mindcrime.bit0.com (8.9.3/8.9.3) with ESMTP id EAA50473; Sun, 30 Jan 2000 04:50:35 -0500 (EST) (envelope-from mandrews@bit0.com) Date: Sun, 30 Jan 2000 04:50:35 -0500 (EST) From: Mike Andrews To: Alex Zepeda Cc: kibbet , current@FreeBSD.ORG Subject: Re: PAIN In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Jan 2000, Alex Zepeda wrote: > On Sun, 30 Jan 2000, kibbet wrote: > > > /me looks at the bunch of 386 mobo's... lets not go there.. :) > > /me looks at the stack of 386sx chips he has and wonders why no-one did 8 > way SMP with these! uky.edu once had a Sequent Symmetry with twenty-six 386DX's in it -- 20 mhz if I remember right. Interesting box, to say the least... Mike Andrews (MA12) * mandrews@dcr.net * http://www.bit0.com/ VP, sysadmin, & network guy, Digital Crescent Inc, Frankfort KY Internet services for Frankfort, Lawrenceburg, Owenton, Shelbyville "Don't sweat the petty things, and don't pet the sweaty things." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 2:32:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id C4F3E150B7 for ; Sun, 30 Jan 2000 02:32:14 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id A606D1CD7; Sun, 30 Jan 2000 17:51:57 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Matthew Dillon Cc: David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. In-Reply-To: Message from Matthew Dillon of "Sat, 29 Jan 2000 20:21:33 PST." <200001300421.UAA28556@apollo.backplane.com> Date: Sun, 30 Jan 2000 17:51:57 +0800 From: Peter Wemm Message-Id: <20000130095157.A606D1CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Matthew Dillon wrote: > When the new parallel port stuff was put several months ago, my > machine stopped working. I had to set flags to 0x40 to make it > work again. Flags of 0x40 force the driver to use the most > basic probes possible. It was put in because a number of people's > machines stopped working. > > It looks like Peter removed the flags 0x40 in rev 1.228 of GENERIC > on Jan 14. > > At the time I had an argument with the author who insisted that > the correct way to force 'basic' probing of the printer was to > set the flags field in GENERIC rather then make the default a basic > probe. > > * Peter, the comment in your log message makes no mention of the reason > * for removing the flags. If you did this by accident could you please > * set the flags back to 0x40? The reason I did that was because flags 0x40 only does something if you activate the PPC_PROBE_CHIPSET option. By default you get flags 0x40 type behavior and the intrusive probes are simply not even compiled into the driver. If you activate the option, then you can also specify flags 0x40 to disable the code you compiled in. In other words, GENERIC does not require the flag any more as it doesn't have the option active. #ifdef PPC_PROBE_CHIPSET /* we have to differenciate available chipset modes, * chipset running modes and IEEE-1284 operating modes * * after detection, the port must support running in compatible mode */ if (ppc->ppc_flags & 0x40) { if (bootverbose) printf("ppc: chipset forced to generic\n"); #endif > Now, a huge number of changes have been made since the original problem > was reported, so I could be puffing smoke here. I didn't see anything > in the CVS logs, though, so I am assuming that the removal of the > flags field was a mistake. > > David, try putting flags 0x40 back in and see if that fixes your > problem. > > -Matt > Matthew Dillon > > > :Why is it that a properly functioning printer is such a moving target > :in FreeBSD? > : > :I don't mean to be argumentative, but under 3.x, the magic cookie to > :make printers work (it appeared to be a flow control problem) was to > :change > : > :device ppc0 at isa? port? flags 0x40 net irq 7 > : > :to > : > :device ppc0 at isa? port? flags 0x40 tty irq 7 > : > :Now... I've upgraded to -CURRENT, and it has a much more serious > :problem. The line now reads > : > :device ppc0 at isa? port? irq 7 > : > :... so I havn't tried putting net or tty in it, but I have a printer > :with a particular problem --- it will often fail to pick up a sheet of > :paper. I suspect that this sets the paper out sense line of the > :parallel port (?). > : > :When this happens, the entire machine freezes until someone feeds the > :printer --- the momment it starts printing again, the computer > :unfreezes. > : > :Printer-port related things probe as: > : > :ppc0: at port 0x378-0x37f irq 7 on isa0 > :ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode > :ppbus0: IEEE1284 device found /NIBBLE/PS2/ECP > :Probing for PnP devices on ppbus0: > :ppbus0: PCL,MLC,PML > :lpt0: on ppbus0 > :lpt0: Interrupt-driven port > :plip0: on ppbus0 > :ppi0: on ppbus0 > : > :(I have tried putting the BIOS in different parallel port modes.) > : > :Dave. > : > :-- > :============================================================================ > :|David Gilbert, Velocet Communications. | Two things can only be | > :|Mail: dgilbert@velocet.net | equal if and only if they | > :|http://www.velocet.net/~dgilbert | are precisely opposite. | > :=========================================================GLO================ > > Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 2:39:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 0D21F14EB1 for ; Sun, 30 Jan 2000 02:39:19 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 4332 invoked from network); 30 Jan 2000 10:34:09 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 30 Jan 2000 10:34:09 -0000 Date: Sun, 30 Jan 2000 21:34:05 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Mark Murray Cc: John Baldwin , current@FreeBSD.ORG, committers@FreeBSD.ORG, Jeroen Ruigrok van der Werven Subject: Re: More world breakage In-Reply-To: <200001300945.e0U9jcw67854@gratis.grondar.za> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, Mark Murray wrote: > > Whichever system they run on. This can be the host machine even for > > cross-compiling, if the target root is remote mounted. The main problem > > with this in -current is that some install rules put ${DESTDIR} in the > > installed files. perl is the main offender. > > Which install rules? I'd like to fix this. (I know libraries are a > big mess). Ones in perl's internal makefiles. I hardly know what they are, but their are 1384 lines of messages in my buildworld output despite my use of `make -s' to turn off verbose output. Headers are converted and packing lists are built... Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 2:42:47 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 34FF014EB1; Sun, 30 Jan 2000 02:42:45 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 284C31CD5C0; Sun, 30 Jan 2000 02:42:45 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 30 Jan 2000 02:42:45 -0800 (PST) From: Kris Kennaway To: Soren Schmidt Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG Subject: Re: Still problems with latest ATA In-Reply-To: <200001301007.LAA46338@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, Soren Schmidt wrote: > > Trying to play a track gives: > > > > acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04 > > I'll bet this drive doesn't support PLAY_BIG but only PLAY_MSF. > The problem here is that PLAY_MSF's parameters are either in > binary or in BCD, but you dont know which one to use, as this > is screwed in more drives than those missing PLAY_BIG. This drive worked fine under wcd. It would be kind of disconcerting to be told that my CD is no longer supported and I have to buy a new one. > > One of my WDC's still falls back to PIO mode at boot time (see previous > > messages, nothing has changed). > > Its not able to do DMA then, besides cluttering up the console with > the retries, it does work afterwards right ? It works fine afterwards, but according to http://www.westerndigital.com/products/drives/specs/oldspecs/AC26400.html it is certainly DMA-capable. It *does* say, interestingly, that older versions cannot do Ultra ATA 66 (I purchased this as an Ultra ATA 66 drive, but..). I'll see what the diagnostic utility has to say about it. > Send me one, there are a few changed items, I'll see what can be done... Will do tomorrow.. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 3: 2:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 2B30914C8F; Sun, 30 Jan 2000 03:02:15 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA46483; Sun, 30 Jan 2000 11:56:30 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200001301056.LAA46483@freebsd.dk> Subject: Re: Still problems with latest ATA In-Reply-To: from Kris Kennaway at "Jan 30, 2000 02:42:45 am" To: kris@hub.freebsd.org (Kris Kennaway) Date: Sun, 30 Jan 2000 11:56:30 +0100 (CET) Cc: current@FreeBSD.ORG, sos@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Kris Kennaway wrote: > On Sun, 30 Jan 2000, Soren Schmidt wrote: > > > > Trying to play a track gives: > > > > > > acd0: PLAY_BIG - ILLEGAL REQUEST asc=21 ascq=00 error=04 > > > > I'll bet this drive doesn't support PLAY_BIG but only PLAY_MSF. > > The problem here is that PLAY_MSF's parameters are either in > > binary or in BCD, but you dont know which one to use, as this > > is screwed in more drives than those missing PLAY_BIG. > > This drive worked fine under wcd. It would be kind of disconcerting to be > told that my CD is no longer supported and I have to buy a new one. Hmm, I'll have to check up on the exact model then... > > > One of my WDC's still falls back to PIO mode at boot time (see previous > > > messages, nothing has changed). > > > > Its not able to do DMA then, besides cluttering up the console with > > the retries, it does work afterwards right ? > > It works fine afterwards, but according to > > http://www.westerndigital.com/products/drives/specs/oldspecs/AC26400.html > > it is certainly DMA-capable. It *does* say, interestingly, that older > versions cannot do Ultra ATA 66 (I purchased this as an Ultra ATA 66 > drive, but..). I'll see what the diagnostic utility has to say about > it. I'm sorry to tell you, by my experience with WDC drives are, well, not good, there has been lots of flukes. The latest ones that is relabeled IBM drives works just fine though. Ssdly the same can be said about Maxtor. For a laugh grep for all the blacklisted drives in the Linux drivers :) -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 4:25:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id AE06214D18; Sun, 30 Jan 2000 04:25:11 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id VAA04832; Sun, 30 Jan 2000 21:22:14 +0900 (JST) To: kris@hub.freebsd.org Cc: current@freebsd.org Subject: Re: identcpu.c change causes panic From: KATO Takenori In-Reply-To: Your message of "Sat, 29 Jan 2000 23:00:09 -0800 (PST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Sun_Jan_30_21:21:41_2000_809)--" Content-Transfer-Encoding: 7bit Message-Id: <20000130212144I.kato@gneiss.eps.nagoya-u.ac.jp> Date: Sun, 30 Jan 2000 21:21:44 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 111 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Sun_Jan_30_21:21:41_2000_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Kris Kennaway wrote: > This commit causes my P5 to panic at boot: > > kato 2000/01/28 23:49:03 PST > > Modified files: > sys/i386/i386 identcpu.c > Log: > Simplify messages of Pentium II, Pentium II Xeon, Celeron, Pentium III > and Pentium III Xeon CPUs. If a CPU is one of Pentium II, Pentium II > Xeon and Celeron, the message is always "Pentium II/Pentium II > Xeon/Celeron". If a CPU is one of Pentium III and Pentium III Xeon, > the message is always "Pentium III/Pentium III Xeon". > > Revision Changes Path > 1.80 +5 -12 src/sys/i386/i386/identcpu.c It sounds strange. I didn't modify any P5 stuff. I attached the patch from 1.79 to 1.80 diff in this mail. - Could you try to this patch with the -R option? - Please report the panic message you got. -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ ----Next_Part(Sun_Jan_30_21:21:41_2000_809)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=identcpu.c.diff Index: identcpu.c =================================================================== RCS file: /home/ncvs/src/sys/i386/i386/identcpu.c,v retrieving revision 1.79 retrieving revision 1.80 diff -c -c -r1.79 -r1.80 *** identcpu.c 2000/01/15 06:29:03 1.79 --- identcpu.c 2000/01/29 07:49:02 1.80 *************** *** 36,42 **** * SUCH DAMAGE. * * from: Id: machdep.c,v 1.193 1996/06/18 01:22:04 bde Exp ! * $FreeBSD: src/sys/i386/i386/identcpu.c,v 1.79 2000/01/15 06:29:03 tanimura Exp $ */ #include "opt_cpu.h" --- 36,42 ---- * SUCH DAMAGE. * * from: Id: machdep.c,v 1.193 1996/06/18 01:22:04 bde Exp ! * $FreeBSD: src/sys/i386/i386/identcpu.c,v 1.80 2000/01/29 07:49:02 kato Exp $ */ #include "opt_cpu.h" *************** *** 199,221 **** strcat(cpu_model, "Pentium Pro"); break; case 0x30: - strcat(cpu_model, "Pentium II"); - cpu = CPU_PII; - break; case 0x50: - strcat(cpu_model, "Pentium II/Xeon/Celeron"); - cpu = CPU_PII; - break; case 0x60: ! strcat(cpu_model, "Pentium II/Celeron"); cpu = CPU_PII; break; case 0x70: - strcat(cpu_model, "Pentium III/Xeon"); - cpu = CPU_PIII; - break; case 0x80: ! strcat(cpu_model, "Pentium III"); cpu = CPU_PIII; break; default: --- 199,214 ---- strcat(cpu_model, "Pentium Pro"); break; case 0x30: case 0x50: case 0x60: ! strcat(cpu_model, ! "Pentium II/Pentium II Xeon/Celeron"); cpu = CPU_PII; break; case 0x70: case 0x80: ! strcat(cpu_model, ! "Pentium III/Pentium III Xeon"); cpu = CPU_PIII; break; default: ----Next_Part(Sun_Jan_30_21:21:41_2000_809)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 5: 9:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from queeg.ludd.luth.se (queeg.ludd.luth.se [130.240.16.109]) by hub.freebsd.org (Postfix) with ESMTP id 194FC14E9E for ; Sun, 30 Jan 2000 05:09:12 -0800 (PST) (envelope-from pantzer@ludd.luth.se) Received: from speedy.ludd.luth.se (pantzer@speedy.ludd.luth.se [130.240.16.164]) by queeg.ludd.luth.se (8.9.3/8.9.3) with ESMTP id OAA12826; Sun, 30 Jan 2000 14:06:47 +0100 (CET) Message-Id: <200001301306.OAA12826@queeg.ludd.luth.se> X-Mailer: exmh version 2.0.2 2/24/98 To: Yoshinobu Inoue Cc: current@FreeBSD.ORG Subject: Re: INET6 and fxp In-Reply-To: Message from Yoshinobu Inoue of "Sun, 30 Jan 2000 15:45:33 +0900." <20000130154533T.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 30 Jan 2000 14:06:46 +0100 From: Mattias Pantzare Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > If I put INET6 in my kernelconfig my network stops working. Even IPv4. I have > > a Intel EtherExpress Pro 10/100B Ethernet (fxp) card. I found a fix for > > FreeBSD on an OpenBSD mailinglist :-) > > > > http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html > > > > Something better than that is probably needed in the long run. > > Let me confirm it. > Does this also fix your problem on your freebsd-current? Yes. I have only tried ping6, but that works, and IPv4 works. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 6:23:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 4A10214C1D for ; Sun, 30 Jan 2000 06:23:25 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id LAA00326; Sun, 30 Jan 2000 11:29:29 GMT (envelope-from n_hibma@webweaving.org) Date: Sun, 30 Jan 2000 11:29:29 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Warner Losh , Peter Wemm Cc: FreeBSD CURRENT Mailing List Subject: old style pcic attach messages - conversion to newbus Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG To go from pcic-pci0: irq 9 at device 19.0 on pci0 pcic-pci0: driver is using old-style compatability shims pcic-pci1: irq 9 at device 19.1 on pci0 pcic-pci1: driver is using old-style compatability shims to pcic-pci0: irq 9 at device 19.0 on pci0 pcic-pci1: irq 9 at device 19.1 on pci0 in less than 1 minute, you'll need the attached patch. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 6:27:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id 4866015115 for ; Sun, 30 Jan 2000 06:27:08 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id PAA13686; Sun, 30 Jan 2000 15:27:20 +0100 (CET) (envelope-from assar) To: current@FreeBSD.ORG Subject: problems rebooting (hanging on ata0) From: Assar Westerlund Date: 30 Jan 2000 15:27:20 +0100 Message-ID: <5ln1pnzlbr.fsf@assaris.sics.se> Lines: 11 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="=-=-=" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --=-=-= I've had the following problem with several recent versions of current. (dmesg of maching included below) Typing `reboot' kills everything but doesn't reboot machine. And then when I break into DDB and type panic twice it tries to dump but then it fails and goes into an infinite loop of `ad0: timeout waiting for DRQ'. Any ideas? /assar --=-=-= Content-Disposition: attachment Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #8: Fri Jan 28 23:47:23 CET 2000 root@hunahpu.sics.se:/usr/src/sys/compile/HUNAHPU Timecounter "i8254" frequency 1193182 Hz CPU: Pentium Pro (199.31-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping = 7 Features=0xfbff real memory = 134217728 (131072K bytes) config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di ex0 config> di ed0 config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> q avail memory = 126758912 (123788K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xc0348000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc034809c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 vga-pci0: mem 0x80000000-0x81ffffff irq 0 at device 12.0 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A sio2: not probed (disabled) sio3: not probed (disabled) ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 ed0: not probed (disabled) ex0: not probed (disabled) ep0: <3Com 3C509-Combo EtherLink III> at port 0x300-0x30f irq 9 on isa0 ep0: Ethernet address 00:a0:24:77:5d:eb ep0: supplying EUI64: 00:a0:24:ff:fe:77:5d:eb APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! ad0: 775MB [1575/16/63] at ata0-master using WDMA2 Mounting root from ufs:/dev/ad0s1a WARNING: / was not properly dismounted ep0: starting DAD for fe80:0002::02a0:24ff:fe77:5deb ep0: DAD complete for fe80:0002::02a0:24ff:fe77:5deb - no duplicates found --=-=-=-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 7:25:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id A6D2914DD2 for ; Sun, 30 Jan 2000 07:25:43 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id KAA06349 for freebsd-current@freebsd.org; Sun, 30 Jan 2000 10:59:59 -0500 (EST) (envelope-from dervish) Date: Sun, 30 Jan 2000 10:59:59 -0500 From: bush doctor To: freebsd-current@freebsd.org Subject: make installworld broken??? Message-ID: <20000130105959.A6288@ikhala.tcimet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm seeing the following failure on my -current box with sources cvsupped last night about 11:30 est. ===> bin/ps install -C -c -s -o root -g wheel -m 555 ps /bin install -C -c -o root -g wheel -m 444 ps.1.gz /usr/share/man/man1 ===> bin/pwd install -C -c -s -o root -g wheel -m 555 pwd /bin install -C -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1 ===> bin/rcp install -C -c -s -o root -g wheel -m 4555 -fschg rcp /bin /usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" *** Error code 1 Stop in /usr/src/bin/rcp. *** Error code 1 Stop in /usr/src/bin. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. #;^) -- So ya want ta hear da roots? bush doctor Of course I run FreeBSD!! http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 7:28:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id ABF5D1507B for ; Sun, 30 Jan 2000 07:28:38 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas4-46-245.dial.proxad.net [212.27.46.245]) by postfix2.free.fr (Postfix) with ESMTP id E4D4F740D1; Sun, 30 Jan 2000 16:28:33 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id QAA00814; Sun, 30 Jan 2000 16:29:11 +0100 (CET) (envelope-from nsouch) Message-ID: <20000130162910.39466@coreff.free.fr> Date: Sun, 30 Jan 2000 16:29:10 +0100 From: Nicolas Souchu To: chris@calldei.com Cc: David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. References: <14483.45082.151986.340011@trooper.velocet.net> <20000129214940.J10669@holly.calldei.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <20000129214940.J10669@holly.calldei.com>; from Chris Costello on Sat, Jan 29, 2000 at 09:49:40PM -0600 X-Operating-System: FreeBSD coreff 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 29, 2000 at 09:49:40PM -0600, Chris Costello wrote: > >On Saturday, January 29, 2000, David Gilbert wrote: >> When this happens, the entire machine freezes until someone feeds the >> printer --- the momment it starts printing again, the computer >> unfreezes. > > Could it be a printer-specific (or printer-compatibility) >problem? My HP DeskJet 880C does not have that problem at all: > >ppc0 at port 0x378-0x37f irq 7 flags 0x40 on isa0 >ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode >ppb0: IEEE1284 device found /NIBBLE/ECP >Probing for PnP devices on ppbus0: >ppbus0: MLC,PCL,PML >plip0: on ppbus 0 >lpt0: on ppbus 0 >lpt0: Interrupt-driven port >ppi0: on ppbus 0 Note that you're using an older ppbus/lpt drivers. -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 7:30: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id DB23114FF2 for ; Sun, 30 Jan 2000 07:29:58 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas4-46-245.dial.proxad.net [212.27.46.245]) by postfix1.free.fr (Postfix) with ESMTP id BA86B2811E; Sun, 30 Jan 2000 16:29:56 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id QAA00833; Sun, 30 Jan 2000 16:31:49 +0100 (CET) (envelope-from nsouch) Message-ID: <20000130163149.27244@coreff.free.fr> Date: Sun, 30 Jan 2000 16:31:49 +0100 From: Nicolas Souchu To: David Gilbert Cc: chris@calldei.com, freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. References: <14483.45082.151986.340011@trooper.velocet.net> <20000129214940.J10669@holly.calldei.com> <14483.46867.83713.676590@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <14483.46867.83713.676590@trooper.velocet.net>; from David Gilbert on Sat, Jan 29, 2000 at 10:59:15PM -0500 X-Operating-System: FreeBSD coreff 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 29, 2000 at 10:59:15PM -0500, David Gilbert wrote: > >>>>>> "Chris" == Chris Costello writes: > >Chris> On Saturday, January 29, 2000, David Gilbert wrote: >>> When this happens, the entire machine freezes until someone feeds >>> the printer --- the momment it starts printing again, the computer >>> unfreezes. > >Chris> Could it be a printer-specific (or printer-compatibility) >Chris> problem? My HP DeskJet 880C does not have that problem at all: > >To my mind, the printer shouldn't be able to hang the comptuer ... no >matter what it does. My biggest problem is that it hangs the system. Even if rapid interrupts are sent to the computer? A priority issue among various interrupt sources maybe. -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 7:32:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from kibby.knf.beldin.net (kibby.knf.beldin.net [203.38.198.130]) by hub.freebsd.org (Postfix) with ESMTP id 1BFA4151A4 for ; Sun, 30 Jan 2000 07:32:49 -0800 (PST) (envelope-from kibbet@kibby.knf.beldin.net) Received: (from kibbet@localhost) by kibby.knf.beldin.net (8.9.3/8.9.3) id CAA15823; Mon, 31 Jan 2000 02:02:32 +1030 (CST) (envelope-from kibbet) 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, 31 Jan 2000 02:02:31 +1030 (CST) From: kibbet To: Mike Andrews Subject: Re: PAIN Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Jan-00 Mike Andrews wrote: > On Sat, 29 Jan 2000, Alex Zepeda wrote: > >> On Sun, 30 Jan 2000, kibbet wrote: >> >> > /me looks at the bunch of 386 mobo's... lets not go there.. :) >> >> /me looks at the stack of 386sx chips he has and wonders why no-one did 8 >> way SMP with these! > > uky.edu once had a Sequent Symmetry with twenty-six 386DX's in it -- 20 > mhz if I remember right. Interesting box, to say the least... > Certainly sounds interesting. Back a couple of years a friend (electronics guru) and I wanted to do some PP'ing for a little astronomy project. It never eventuated but we were thinking of a tying the 6 odd 486's together directly via a pci to pci circuit. We wanted SPEED though so we tossed around the idea of direct pc/pc communication via SIMM sockets. Idea being, chunk of ram for local processing, starting on a SIMM boundary a circuit (running at cpu bus speed) to communicate with the other pc's. All highly unlikely, but logic didn't enter into it back then :) Cheers... Kent Ibbetson kibbet@knfpub.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 7:32:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix1.free.fr (postfix1.free.fr [212.27.32.21]) by hub.freebsd.org (Postfix) with ESMTP id 9DEE1151B0 for ; Sun, 30 Jan 2000 07:32:53 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas4-46-245.dial.proxad.net [212.27.46.245]) by postfix1.free.fr (Postfix) with ESMTP id 2D0B2280CC; Sun, 30 Jan 2000 16:32:52 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id QAA00841; Sun, 30 Jan 2000 16:34:44 +0100 (CET) (envelope-from nsouch) Message-ID: <20000130163443.06012@coreff.free.fr> Date: Sun, 30 Jan 2000 16:34:43 +0100 From: Nicolas Souchu To: Matthew Dillon Cc: David Gilbert , Peter Wemm , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. References: <14483.45082.151986.340011@trooper.velocet.net> <200001300421.UAA28556@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <200001300421.UAA28556@apollo.backplane.com>; from Matthew Dillon on Sat, Jan 29, 2000 at 08:21:33PM -0800 X-Operating-System: FreeBSD coreff 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Jan 29, 2000 at 08:21:33PM -0800, Matthew Dillon wrote: > > When the new parallel port stuff was put several months ago, my > machine stopped working. I had to set flags to 0x40 to make it > work again. Flags of 0x40 force the driver to use the most > basic probes possible. It was put in because a number of people's > machines stopped working. > > It looks like Peter removed the flags 0x40 in rev 1.228 of GENERIC > on Jan 14. Specific chipset detection is now disabled by default since most of the chipsets detected on new MB are not recognised by ppc. A MACHINE option shall be set to activate chipset detection. See http://www.freebsd.org/~nsouch/ppbus.html for more info. [...] > > David, try putting flags 0x40 back in and see if that fixes your > problem. 0x40 has the same effect only if chipset specific detection is activated at compile time by the correct option. Otherwise the action is null. -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 7:39:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1F08A150C4 for ; Sun, 30 Jan 2000 07:39:25 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id QAA18193; Sun, 30 Jan 2000 16:39:10 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: bush doctor Cc: freebsd-current@FreeBSD.ORG Subject: Re: make installworld broken??? In-reply-to: Your message of "Sun, 30 Jan 2000 10:59:59 EST." <20000130105959.A6288@ikhala.tcimet.net> Date: Sun, 30 Jan 2000 16:39:10 +0100 Message-ID: <18191.949246750@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG You need to manually recompile and install your "install" command. It's source-dir is called "xinstall" btw. Poul-Henning In message <20000130105959.A6288@ikhala.tcimet.net>, bush doctor writes: >I'm seeing the following failure on my -current box with sources cvsupped last >night about 11:30 est. > >===> bin/ps >install -C -c -s -o root -g wheel -m 555 ps /bin >install -C -c -o root -g wheel -m 444 ps.1.gz /usr/share/man/man1 >===> bin/pwd >install -C -c -s -o root -g wheel -m 555 pwd /bin >install -C -c -o root -g wheel -m 444 pwd.1.gz /usr/share/man/man1 >===> bin/rcp >install -C -c -s -o root -g wheel -m 4555 -fschg rcp /bin >/usr/libexec/ld-elf.so.1: install: Undefined symbol "string_to_flags" >*** Error code 1 > >Stop in /usr/src/bin/rcp. >*** Error code 1 > >Stop in /usr/src/bin. >*** Error code 1 > >Stop in /usr/src. >*** Error code 1 > >Stop in /usr/src. >*** Error code 1 > >Stop in /usr/src. >*** Error code 1 > >Stop in /usr/src. > >#;^) >-- >So ya want ta hear da roots? >bush doctor > Of course I run FreeBSD!! > http://www.freebsd.org/ > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 8: 4:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from ikhala.tcimet.net (ikhala.tcimet.net [198.109.166.215]) by hub.freebsd.org (Postfix) with ESMTP id DB43D150B7 for ; Sun, 30 Jan 2000 08:04:12 -0800 (PST) (envelope-from dervish@ikhala.tcimet.net) Received: (from dervish@localhost) by ikhala.tcimet.net (8.9.3/8.9.3) id LAA06479 for freebsd-current@FreeBSD.ORG; Sun, 30 Jan 2000 11:38:30 -0500 (EST) (envelope-from dervish) Date: Sun, 30 Jan 2000 11:38:30 -0500 From: bush doctor To: freebsd-current@FreeBSD.ORG Subject: Re: make installworld broken??? Message-ID: <20000130113830.B6288@ikhala.tcimet.net> References: <20000130105959.A6288@ikhala.tcimet.net> <18191.949246750@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <18191.949246750@critter.freebsd.dk>; from phk@critter.freebsd.dk on Sun, Jan 30, 2000 at 04:39:10PM +0100 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Out of da blue Poul-Henning Kamp aka (phk@critter.freebsd.dk) said: > > > You need to manually recompile and install your "install" command. Thanxs. I had looked at this, but wasn't sure. > > It's source-dir is called "xinstall" btw. Why is the source called "xinstall"? > > Poul-Henning > > In message <20000130105959.A6288@ikhala.tcimet.net>, bush doctor writes: > >I'm seeing the following failure on my -current box with sources cvsupped last > >night about 11:30 est. [snippage ...] > > -- > Poul-Henning Kamp FreeBSD coreteam member > phk@FreeBSD.ORG "Real hackers run -current on their laptop." > FreeBSD -- It will take a long time before progress goes too far! > #;^) -- So ya want ta hear da roots? bush doctor Of course I run FreeBSD!! http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 8:47:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 92AF015D73 for ; Sun, 30 Jan 2000 08:47:19 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id QAA09579; Sun, 30 Jan 2000 16:42:09 GMT (envelope-from n_hibma@webweaving.org) Date: Sun, 30 Jan 2000 16:42:06 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Assar Westerlund Cc: current@FreeBSD.ORG Subject: Re: problems rebooting (hanging on ata0) In-Reply-To: <5ln1pnzlbr.fsf@assaris.sics.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I've had the following problem with several recent versions of > current. (dmesg of maching included below) > > Typing `reboot' kills everything but doesn't reboot machine. And then > when I break into DDB and type panic twice it tries to dump but then > it fails and goes into an infinite loop of `ad0: timeout waiting for > DRQ'. Any ideas? Same message here, but after a panic of the USB subsystem. I blamed the current spl. Until I did a 'call splx(0)' right before giving the command panic. It still did not give me a dump. Nick -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 8:53:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3A03615342 for ; Sun, 30 Jan 2000 08:53:12 -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 JAA21586; Sun, 30 Jan 2000 09:53:06 -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 JAA14358; Sun, 30 Jan 2000 09:53:16 -0700 (MST) Message-Id: <200001301653.JAA14358@harmony.village.org> To: Nick Hibma Subject: Re: old style pcic attach messages - conversion to newbus Cc: Peter Wemm , FreeBSD CURRENT Mailing List In-reply-to: Your message of "Sun, 30 Jan 2000 11:29:29 GMT." References: Date: Sun, 30 Jan 2000 09:53:16 -0700 From: Warner Losh Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message Nick Hibma writes: : pcic-pci0: irq 9 at device 19.0 on pci0 : pcic-pci0: driver is using old-style compatability shims : pcic-pci1: irq 9 at device 19.1 on pci0 : pcic-pci1: driver is using old-style compatability shims : : to : : pcic-pci0: irq 9 at device 19.0 on pci0 : pcic-pci1: irq 9 at device 19.1 on pci0 : : in less than 1 minute, you'll need the attached patch. ???? Need the attached patch... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 9:20:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 0E4711512D for ; Sun, 30 Jan 2000 09:20:33 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id JAA58528 for ; Sun, 30 Jan 2000 09:20:32 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id JAA02649 for current@freebsd.org; Sun, 30 Jan 2000 09:20:32 -0800 (PST) (envelope-from obrien) Date: Sun, 30 Jan 2000 09:20:32 -0800 From: "David O'Brien" To: current@freebsd.org Subject: Error in Makefile one needs to correct before a `make world' Message-ID: <20000130092032.A2435@dragon.nuxi.com> Reply-To: obrien@NUXI.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG If you installed world after my libreadline header moving, you probably have readline headers in /usr/include you'll want to rm. Index: Makefile =================================================================== RCS file: /home/ncvs/src/gnu/lib/libreadline/readline/Makefile,v retrieving revision 1.4 retrieving revision 1.5 diff -u -r1.4 -r1.5 --- Makefile 2000/01/29 12:01:52 1.4 +++ Makefile 2000/01/30 17:11:46 1.5 @@ -17,6 +17,8 @@ DPADD+= $(LIBTERMCAP) LDADD+= -ltermcap + +INCDIR= /usr/include/readline .for hdr in ${INSTALLED_HEADERS} INCS+= ${SRCDIR}/${hdr} To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 10:29:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail1.DInet.de (mail1.dinet.de [212.8.0.3]) by hub.freebsd.org (Postfix) with SMTP id BA11A14DAC for ; Sun, 30 Jan 2000 10:29:30 -0800 (PST) (envelope-from jan@pitr.dinet.de) Received: (qmail 13377 invoked from network); 30 Jan 2000 19:26:20 -0000 Received: from pitr.dinet.de (@212.8.3.251) by mail1.dinet.de with SMTP; 30 Jan 2000 19:26:20 -0000 Received: by pitr.dinet.de (Postfix, from userid 1000) id 16D46D2E; Sun, 30 Jan 2000 19:27:16 +0100 (CET) Date: Sun, 30 Jan 2000 19:27:16 +0100 From: Jan Andres To: "Daniel C. Sobral" Cc: Jean-Marc Zucconi , current@FreeBSD.ORG Subject: Re: Loader.rc: unknown command Message-ID: <20000130192716.B542@pitr.dinet.de> References: <200001300528.GAA00406@qix.jmz.org> <3893D11E.B8F95AA6@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.1i In-Reply-To: <3893D11E.B8F95AA6@newsguy.com>; from dcs@newsguy.com on Sun, Jan 30, 2000 at 02:50:22PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30. Jan. 2000 at 14:50:22 +0900, Daniel C. Sobral wrote: > Jean-Marc Zucconi wrote: > > > > With a new installed world I get this message at boot: > > > > > \ Loader.rc > > Loader.rc: unknown command > > > > Fortunately this does not prevent the machine to boot :-) > > Any clue? > > The \ command is not working correctly, resulting in the "Loader.rc" > comment being executed instead of ignored. > > Why? I don't have a clue. Is *ANYONE* being able to reproduce this > problem? If so, please contact me ASAP, since we have almost no time to > fix this before 4.0-RELEASE. I can reproduce this. I use CTM and the delta that broke the loader is number 4202 of src-cur, which was generated on Jan 28 11:02. I think it's the time when cdldr was committed. There problem seems not to depend on which forth scripts I put into /boot. I tried some old ones from my first install (3.2-RELEASE) that had worked up to that point, and the new ones from the -current source tree. -- Jan Andres jan@dinet.de Ham radio: DH2JAN "Bell Labs Unix -- reach out and grep someone." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 10:56:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from assaris.sics.se (assaris.sics.se [193.10.66.234]) by hub.freebsd.org (Postfix) with ESMTP id A10DE14D0D for ; Sun, 30 Jan 2000 10:56:12 -0800 (PST) (envelope-from assar@assaris.sics.se) Received: (from assar@localhost) by assaris.sics.se (8.9.3/8.9.3) id TAA15214; Sun, 30 Jan 2000 19:56:17 +0100 (CET) (envelope-from assar) To: Nick Hibma Cc: current@FreeBSD.ORG Subject: Re: problems rebooting (hanging on ata0) References: From: Assar Westerlund Date: 30 Jan 2000 19:56:17 +0100 In-Reply-To: Nick Hibma's message of "Sun, 30 Jan 2000 16:42:06 +0000 (GMT)" Message-ID: <5ld7qjwfqm.fsf@assaris.sics.se> Lines: 14 User-Agent: Gnus/5.070098 (Pterodactyl Gnus v0.98) Emacs/20.4 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma writes: > Same message here, but after a panic of the USB subsystem. I blamed the > current spl. Until I did a 'call splx(0)' right before giving the > command panic. It still did not give me a dump. There seems to be two problems here: 1) It hangs instead of rebooting 2) It doesn't manage to write a dump. It doesn't happen every reboot and I haven't been able to figure out what's triggering it. /assar To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 11:13:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from wall.polstra.com (rtrwan160.accessone.com [206.213.115.74]) by hub.freebsd.org (Postfix) with ESMTP id 34D6F15296 for ; Sun, 30 Jan 2000 11:13:09 -0800 (PST) (envelope-from jdp@polstra.com) Received: from vashon.polstra.com (vashon.polstra.com [206.213.73.13]) by wall.polstra.com (8.9.3/8.9.3) with ESMTP id LAA20122; Sun, 30 Jan 2000 11:13:04 -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 LAA35839; Sun, 30 Jan 2000 11:13:03 -0800 (PST) (envelope-from jdp@polstra.com) Date: Sun, 30 Jan 2000 11:13:03 -0800 (PST) Message-Id: <200001301913.LAA35839@vashon.polstra.com> To: dervish@ikhala.tcimet.net Subject: Re: make installworld broken??? In-Reply-To: <20000130113830.B6288@ikhala.tcimet.net> References: <20000130105959.A6288@ikhala.tcimet.net> <18191.949246750@critter.freebsd.dk> <20000130113830.B6288@ikhala.tcimet.net> Organization: Polstra & Co., Seattle, WA Cc: current@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > It's source-dir is called "xinstall" btw. > Why is the source called "xinstall"? To avoid colliding with the standard make target "install". If we had utilities named "all", "depend", and "clean" we'd have to do the same thing for them. John PS - Please remove me from the cc on the inevitable 50-message thread about clever ways to avoid this simple fix, all requiring 100-line perl scripts no doubt. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 11:46:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp10.atl.mindspring.net (smtp10.atl.mindspring.net [207.69.200.246]) by hub.freebsd.org (Postfix) with ESMTP id 2406E15250 for ; Sun, 30 Jan 2000 11:46:12 -0800 (PST) (envelope-from brdean@mindspring.com) Received: from vger.foo.com (user-2ivf0ca.dialup.mindspring.com [165.247.129.138]) by smtp10.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id OAA21879; Sun, 30 Jan 2000 14:45:54 -0500 (EST) Received: (from bsd@localhost) by vger.foo.com (8.9.3/8.9.3) id OAA53806; Sun, 30 Jan 2000 14:42:40 -0500 (EST) (envelope-from bsd) From: Brian Dean Message-Id: <200001301942.OAA53806@vger.foo.com> Subject: Re: Printer fiascos. In-Reply-To: <3893D34D.7F9C90F6@newsguy.com> from "Daniel C. Sobral" at "Jan 30, 2000 02:59:41 pm" To: "Daniel C. Sobral" Date: Sun, 30 Jan 2000 14:42:39 -0500 (EST) Cc: Chuck Robey , David Gilbert , "Sean O'Connell" , freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For what its worth, I am able to reproduce this problem on my system. Simply submit something to lpr, wait for the printer light to blink, and pull the paper tray. The system hangs hard as described and does not return to normal until the paper tray is put back in. I haven't been able to make it do anything while the printer has the system hung, so I haven't been able to track it down, yet. However, I haven't had much time to spend on this problem, but thought I'd chime in a "me too" when I saw someone had the (apparently) same problem. I have an HP LaserJet 4 connected to the parallel port. I am running -current, and a buildworld as of about a week ago. -Brian -- Brian Dean brdean@mindspring.com Here's my dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sun Jan 23 09:10:33 EST 2000 bsd@vger.foo.com:/usr/src/sys/compile/VGER Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 300682757 Hz CPU: Pentium II/Xeon/Celeron (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183f9ff real memory = 201326592 (196608K bytes) avail memory = 192131072 (187628K bytes) Preloaded elf kernel "kernel" at 0xc02f3000. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 11 chip1: port 0x5000-0x500f at device 7.3 on pci0 vga-pci0: mem 0xe5000000-0xe5ffffff,0xe4000000-0xe4ffffff irq 10 at device 9.0 on pci0 xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xc400-0xc43f irq 5 at device 10.0 on pci0 xl0: Ethernet address: 00:60:08:17:67:f9 miibus0: on xl0 nsphy0: on miibus0 nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto ahc0: port 0xc800-0xc8ff mem 0xe9000000-0xe9000fff irq 9 at device 11.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs pci0: unknown card (vendor=0x1102, dev=0x0002) at 12.0 irq 11 pci0: unknown card (vendor=0x1102, dev=0x7002) at 12.1 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata-isa0: already registered as ata0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, unlimited logging Waiting 15 seconds for SCSI devices to settle acd0: CDROM drive at ata0 as master acd0: 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked Mounting root from ufs:/dev/da0a da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da2: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) 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: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) da4 at ahc0 bus 0 target 6 lun 0 da4: Removable Direct Access SCSI-2 device da4: 10.000MB/s transfers (10.000MHz, offset 15) da4: Attempt to query device size failed: NOT READY, Medium not present da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) da3: 8683MB (17783204 512 byte sectors: 255H 63S/T 1106C) pid 52635 (communicator-4.6), uid 1000: exited on signal 10 (core dumped) Dan Sobral wrote: > Chuck Robey wrote: > > > > Sheesh. This is a FreeBSD-questions type thing, not current. > > I disagree. It is obvious that something is getting locked inside the > kernel in his setup. This *SHOULDN'T* happen, it's that simple. If his > machine locked whenever the printer went out of paper, and *stayed* > locked, I'd be willing to believe the problem was caused by hardware. > That's not what was reported. What was reported is rather (better) > explained by some kernel code waiting indefinitely for an event, while > preventing anything else from executing. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 12:29:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by hub.freebsd.org (Postfix) with ESMTP id 030E614CB0; Sun, 30 Jan 2000 12:29:13 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id MAA59276; Sun, 30 Jan 2000 12:29:12 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id MAA03403; Sun, 30 Jan 2000 12:29:13 -0800 (PST) (envelope-from obrien) Date: Sun, 30 Jan 2000 12:29:13 -0800 From: "David O'Brien" To: Jean-Marc Zucconi Cc: current@FreeBSD.org Subject: Re: new C++ compiler changes Message-ID: <20000130122913.A3379@dragon.nuxi.com> Reply-To: current@FreeBSD.org References: <200001290007.TAA05379@whizzo.transsys.com> <200001300500.GAA10115@qix.jmz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200001300500.GAA10115@qix.jmz.org>; from jmz@FreeBSD.org on Sun, Jan 30, 2000 at 06:00:03AM +0100 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > rename it libstdc++.so.1. Then you just have to modify your executable > so that it looks for libstdc++.so.1 instead of libstdc++.so.3 Why not just reinstall the problematic executables? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 12:42:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 1A69314E68; Sun, 30 Jan 2000 12:42:16 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id UAA81296; Sun, 30 Jan 2000 20:39:36 GMT (envelope-from joe) Date: Sun, 30 Jan 2000 20:39:36 +0000 From: Josef Karthauser To: John Baldwin Cc: Marcel Moolenaar , Jeroen Ruigrok van der Werven , committers@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: More world breakage Message-ID: <20000130203936.A74352@florence.pavilion.net> References: <002301bf69df$bd24eb00$0301a8c0@adm.scc.nl> <200001290130.UAA42086@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001290130.UAA42086@server.baldwin.cx> 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Jan 28, 2000 at 08:30:55PM -0500, John Baldwin wrote: > > > I don't think we should change yet another thing before a release. The > > problem shouldn't have been created this close to a release in the first > > place. We have to stop somewhere, and I think we should stop "fixing" right > > here, right now unless there's a *really* good reason not to (IMO of > > course). > > You're right. I guess the proper solution is to just back these changes out > until after 4.0 when you can finish fixing up install side of 'world'. I just > got ahead of myself a little. I've been thinking about this - being the one who made the original commit! This problem is the product of _two_ recent changes in -current only. In -stable, and in -current before the end of December the following tools: ls, rm, chflags, find, xinstall and mtree used a common set of routines to manipulate file flags. These were borrowed from bin/ls/stat_flags.c and statically compiled into each tool. At the beginnig of January, because of the proliferation of utilities using these functions, I moved them to libutil in -current. There were however various objections to this change, on the basis that libutil isn't a utility library as its name suggest, but has a much more narrow definition relating to login related code. It was proposed by Bruce to move these to libc and to change their name to be in keeping with similar routines for manipulating file modes (setmode/getmode). This was what I did last week, renaming flags_to_string to getflags, and string_to_flags to setflags. I missed the clash of name space in a couple of unrelated tools, like mount_nfs, I agree that I should have been more careful here - sorry. There is now a problem for some people with the build chain due to xinstall being dependant upon a function that has changed its name for its file flags support. There is also a secondary question of whether getflags/setflags are good names for these functions (based as there were on getmode/setmode). Thinking out loud: If we back out the name change (string_to_flags->setflags) we'll bump into the buildchain problem again for people who've now got a new xinstall dependant upon setflags. Moving the functions back into libutil, from libc, is the wrong thing to do, IMHO, because the problem here isn't one of which library placement, it's one of function names. Libutil is the wrong place for these functions, which is why I wanted them in libc for the 4.0 release. It may be argued that we should back out _both_ commits and resurrect bin/ls/stat_flags.c. Would this gain us anything? I'm quite happy to DTRT(tm); I'm unsure that backing this change out _is_ the right thing however. Can we discuss it some more first please? Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 12:50: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 29A9714E68; Sun, 30 Jan 2000 12:50:02 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 082751CD820; Sun, 30 Jan 2000 12:50:02 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Sun, 30 Jan 2000 12:50:01 -0800 (PST) From: Kris Kennaway To: KATO Takenori Cc: current@freebsd.org Subject: Re: identcpu.c change causes panic In-Reply-To: <20000130212144I.kato@gneiss.eps.nagoya-u.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, KATO Takenori wrote: > It sounds strange. I didn't modify any P5 stuff. > > I attached the patch from 1.79 to 1.80 diff in this mail. > > - Could you try to this patch with the -R option? Yes, when I back out this revision (& nothing else) I can boot fine :-) > - Please report the panic message you got. I'll have to write this down by hand - it didn't look very interesting, though. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 13:12:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from awfulhak.org (dynamic-123.max4-du-ws.dialnetwork.pavilion.co.uk [212.74.9.251]) by hub.freebsd.org (Postfix) with ESMTP id A5AC6152C9; Sun, 30 Jan 2000 13:12:28 -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 VAA78967; Sun, 30 Jan 2000 21:12:18 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 VAA06647; Sun, 30 Jan 2000 21:12:11 GMT (envelope-from brian@hak.lan.Awfulhak.org) Message-Id: <200001302112.VAA06647@hak.lan.Awfulhak.org> X-Mailer: exmh version 2.1.0 09/18/1999 To: Josef Karthauser Cc: John Baldwin , Marcel Moolenaar , Jeroen Ruigrok van der Werven , committers@FreeBSD.org, current@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: More world breakage In-Reply-To: Message from Josef Karthauser of "Sun, 30 Jan 2000 20:39:36 GMT." <20000130203936.A74352@florence.pavilion.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 30 Jan 2000 21:12:11 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Fri, Jan 28, 2000 at 08:30:55PM -0500, John Baldwin wrote: > > > > > I don't think we should change yet another thing before a release. The > > > problem shouldn't have been created this close to a release in the first > > > place. We have to stop somewhere, and I think we should stop "fixing" right > > > here, right now unless there's a *really* good reason not to (IMO of > > > course). > > > > You're right. I guess the proper solution is to just back these changes out > > until after 4.0 when you can finish fixing up install side of 'world'. I just > > got ahead of myself a little. > > I've been thinking about this - being the one who made the original > commit! > > This problem is the product of _two_ recent changes in -current > only. In -stable, and in -current before the end of December the > following tools: ls, rm, chflags, find, xinstall and mtree used > a common set of routines to manipulate file flags. These were > borrowed from bin/ls/stat_flags.c and statically compiled into each > tool. At the beginnig of January, because of the proliferation of > utilities using these functions, I moved them to libutil in -current. > There were however various objections to this change, on the basis > that libutil isn't a utility library as its name suggest, but has > a much more narrow definition relating to login related code. It > was proposed by Bruce to move these to libc and to change their > name to be in keeping with similar routines for manipulating file > modes (setmode/getmode). This was what I did last week, renaming > flags_to_string to getflags, and string_to_flags to setflags. I > missed the clash of name space in a couple of unrelated tools, like > mount_nfs, I agree that I should have been more careful here - > sorry. > > There is now a problem for some people with the build chain due to > xinstall being dependant upon a function that has changed its name > for its file flags support. There is also a secondary question of > whether getflags/setflags are good names for these functions (based > as there were on getmode/setmode). > > Thinking out loud: > > If we back out the name change (string_to_flags->setflags) we'll > bump into the buildchain problem again for people who've now got > a new xinstall dependant upon setflags. > > Moving the functions back into libutil, from libc, is the wrong > thing to do, IMHO, because the problem here isn't one of which > library placement, it's one of function names. Libutil is the > wrong place for these functions, which is why I wanted them in libc > for the 4.0 release. > > It may be argued that we should back out _both_ commits and resurrect > bin/ls/stat_flags.c. Would this gain us anything? > > I'm quite happy to DTRT(tm); I'm unsure that backing this change out > _is_ the right thing however. Can we discuss it some more first please? I think that getflags()/setflags() should stay where they are, but I can't comment on the namespace pollution issue. If/When the functions are renamed, they'll probably break make world again (because the new libc and old install will be there for a while), but to be honest, this *is* current. I think the issue to focus on is the function names. > Joe > -- > Josef Karthauser FreeBSD: Take the red pill and we'll show you just how > Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) > Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] > > -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 13:30: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 2AEAE14D33; Sun, 30 Jan 2000 13:29:57 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id QAA23122; Sun, 30 Jan 2000 16:29:45 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Sun, 30 Jan 2000 16:29:41 -0500 (EST) From: Chuck Robey To: Brian Somers Cc: Josef Karthauser , John Baldwin , Marcel Moolenaar , Jeroen Ruigrok van der Werven , committers@FreeBSD.org, current@FreeBSD.org, brian@hak.lan.Awfulhak.org Subject: Re: More world breakage In-Reply-To: <200001302112.VAA06647@hak.lan.Awfulhak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, Brian Somers wrote: > > I'm quite happy to DTRT(tm); I'm unsure that backing this change out > > _is_ the right thing however. Can we discuss it some more first please? > > I think that getflags()/setflags() should stay where they are, but I > can't comment on the namespace pollution issue. If/When the > functions are renamed, they'll probably break make world again > (because the new libc and old install will be there for a while), but > to be honest, this *is* current. > > I think the issue to focus on is the function names. I agree that folks should read current, and be able to do fixes. Do the fix, though, in a way that *doesn't* require yet another fix later on, and post the extraordinary steps clearly here, in a "HEADS-UP" mail that folks will definitely see, and maybe stick something in UPDATING too? At least, give everyone a fair chance, don't embed the fix as the end of a 1,000 words of context email, at the end of a long thread. That wouldn't be fair. Not for extraordinary breakage. ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 13:52:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 3E1E114ECE; Sun, 30 Jan 2000 13:52:10 -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 QAA61702; Sun, 30 Jan 2000 16:51:44 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200001302151.QAA61702@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: <20000130203936.A74352@florence.pavilion.net> Date: Sun, 30 Jan 2000 16:51:44 -0500 (EST) From: John Baldwin To: Josef Karthauser Subject: Re: More world breakage Cc: current@FreeBSD.org, committers@FreeBSD.org, Jeroen Ruigrok van der Werven , Marcel Moolenaar Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Jan-00 Josef Karthauser wrote: > On Fri, Jan 28, 2000 at 08:30:55PM -0500, John Baldwin wrote: >> >> > I don't think we should change yet another thing before a release. The >> > problem shouldn't have been created this close to a release in the first >> > place. We have to stop somewhere, and I think we should stop "fixing" right >> > here, right now unless there's a *really* good reason not to (IMO of >> > course). >> >> You're right. I guess the proper solution is to just back these changes out >> until after 4.0 when you can finish fixing up install side of 'world'. I just >> got ahead of myself a little. > > I've been thinking about this - being the one who made the original > commit! :) > There is now a problem for some people with the build chain due to > xinstall being dependant upon a function that has changed its name > for its file flags support. There is also a secondary question of > whether getflags/setflags are good names for these functions (based > as there were on getmode/setmode). I have no opinion on the function names used except that strflags() would be bad, IMO. > Thinking out loud: > > If we back out the name change (string_to_flags->setflags) we'll > bump into the buildchain problem again for people who've now got > a new xinstall dependant upon setflags. My main concern is people going from 3.x to 4.0. Since the xinstall binary on 3.x doesn't call a string_to_flags() function from libc but has it statically compiled in, the upgrade path should work fine for them. I'll test that tonight. If that path works fine, then the problem only exists for the people using fairly recent -current who have an xinstall binary that tries to use string_to_flags() from libc. Given, then, that they are all -current users, their being able to work around this is not too much to ask. I didn't originally realize that 3.x xinstall binaries didn't try to call the string_to_flags() function from libc. With that in mind, the upgrade path is only going to be broken for a few people who should be reading -current and thus know how to work around the problem, so I repeal my request for the changes to be backed out. My apologies. > Moving the functions back into libutil, from libc, is the wrong > thing to do, IMHO, because the problem here isn't one of which > library placement, it's one of function names. Libutil is the > wrong place for these functions, which is why I wanted them in libc > for the 4.0 release. Agreed. > It may be argued that we should back out _both_ commits and resurrect > bin/ls/stat_flags.c. Would this gain us anything? No. > I'm quite happy to DTRT(tm); I'm unsure that backing this change out > _is_ the right thing however. Can we discuss it some more first please? > > Joe -- 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-current" in the body of the message From owner-freebsd-current Sun Jan 30 13:57:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from florence.pavilion.net (florence.pavilion.net [212.74.0.25]) by hub.freebsd.org (Postfix) with ESMTP id 0DE5114C15; Sun, 30 Jan 2000 13:56:56 -0800 (PST) (envelope-from joe@florence.pavilion.net) Received: (from joe@localhost) by florence.pavilion.net (8.9.3/8.8.8) id VAA89970; Sun, 30 Jan 2000 21:56:50 GMT (envelope-from joe) Date: Sun, 30 Jan 2000 21:56:50 +0000 From: Josef Karthauser To: John Baldwin Cc: current@FreeBSD.org, committers@FreeBSD.org, Jeroen Ruigrok van der Werven , Marcel Moolenaar Subject: Re: More world breakage Message-ID: <20000130215650.A83543@florence.pavilion.net> References: <20000130203936.A74352@florence.pavilion.net> <200001302151.QAA61702@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <200001302151.QAA61702@server.baldwin.cx> 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 30, 2000 at 04:51:44PM -0500, John Baldwin wrote: [cut] > With that in mind, the upgrade path is only going > to be broken for a few people who should be reading -current and thus > know how to work around the problem, so I repeal my request for the > changes to be backed out. My apologies. Great :) So, has anyone any strong ideas on both the "correct" function names to use and what the correct API should be for the functions. Joe -- Josef Karthauser FreeBSD: Take the red pill and we'll show you just how Technical Manager deep the rabbit hole goes. (http://www.uk.freebsd.org) Pavilion Internet plc. [joe@pavilion.net, joe@freebsd.org, joe@tao.org.uk] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 13:58:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from FreeBSD.org (ppp13-besancon.isdnet.net [195.154.11.220]) by hub.freebsd.org (Postfix) with ESMTP id 0775415EB5 for ; Sun, 30 Jan 2000 13:58:05 -0800 (PST) (envelope-from jmz@FreeBSD.org) Received: (from jmz@localhost) by qix.jmz.org (8.9.3/8.9.3) id WAA04582; Sun, 30 Jan 2000 22:59:30 +0100 (MET) (envelope-from jmz@FreeBSD.org) Date: Sun, 30 Jan 2000 22:59:30 +0100 (MET) Message-Id: <200001302159.WAA04582@qix.jmz.org> From: Jean-Marc Zucconi To: current@FreeBSD.org In-reply-to: <20000130122913.A3379@dragon.nuxi.com> (obrien@FreeBSD.org) Subject: Re: new C++ compiler changes X-Mailer: Emacs References: <200001290007.TAA05379@whizzo.transsys.com> <200001300500.GAA10115@qix.jmz.org> <20000130122913.A3379@dragon.nuxi.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> David O'Brien writes: >> rename it libstdc++.so.1. Then you just have to modify your executable >> so that it looks for libstdc++.so.1 instead of libstdc++.so.3 > Why not just reinstall the problematic executables? Because I don't always have the time to recompile. My (temporary) solution is invaluable when I am in a hurry. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 14:14:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from postfix2.free.fr (postfix2.free.fr [212.27.32.74]) by hub.freebsd.org (Postfix) with ESMTP id 95E001517A for ; Sun, 30 Jan 2000 14:14:31 -0800 (PST) (envelope-from nsouch@free.fr) Received: from free.fr (paris11-nas3-44-7.dial.proxad.net [212.27.44.7]) by postfix2.free.fr (Postfix) with ESMTP id BE8CB7413F for ; Sun, 30 Jan 2000 23:14:29 +0100 (MET) Received: (from nsouch@localhost) by free.fr (8.9.3/8.9.3) id AAA03726; Mon, 31 Jan 2000 00:17:11 +0100 (CET) (envelope-from nsouch) Message-ID: <20000131001711.27472@breizh.free.fr> Date: Mon, 31 Jan 2000 00:17:11 +0100 From: Nicolas Souchu To: freebsd-current@freebsd.org Subject: bootp and diskless failure Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e X-Operating-System: FreeBSD breizh 4.0-CURRENT FreeBSD 4.0-CURRENT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Is there something changed on BOOTP/diskless configuration? This problem reappears some times and was fixed in August if I remember. A hack was proposed before August, something like 'make root dev' call in bootp_subr.c Thanks, Nicholas >>>> bootpc_init: using network interface 'ed0' Bootpc testing starting bootpc hw address is 0:40:5:e2:a0:e9 My ip address is 10.2.0.1 Server ip address is 10.2.0.2 Gateway ip address is 0.0.0.0 boot file is kernel.coreff Ignoring field type 54 Subnet mask is 255.255.0.0 rootfs is 10.2.0.2:/diskless/rootfs/current Ignoring field type 28 no B_DEVMAGIC (bootdev=0xffffffff) Manual root filesystem specification: : Mount using filesystem eg. ufs:/dev/da0s1a ? List valid disk boot devices Abort manual input >>> panic: Root mount failed, startup aborted. Debugger("panic") Stopped at Debugger+0x35: movb $0,0xc02d7f00 db> panic -- nsouch@free.fr / nsouch@freebsd.org FreeBSD - Turning PCs into workstations - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 14:23:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp7.atl.mindspring.net (smtp7.atl.mindspring.net [207.69.128.51]) by hub.freebsd.org (Postfix) with ESMTP id 3766F14D5A for ; Sun, 30 Jan 2000 14:23:45 -0800 (PST) (envelope-from mremski@ix.netcom.com) Received: from bsg-ma1d-13.ix.netcom.com (bsg-ma1d-13.ix.netcom.com [209.110.251.13]) by smtp7.atl.mindspring.net (8.9.3/8.8.5) with ESMTP id RAA07406; Sun, 30 Jan 2000 17:23:25 -0500 (EST) Date: Sun, 30 Jan 2000 17:25:41 -0500 (EST) From: Michael Remski To: Brian Dean Cc: "Daniel C. Sobral" , Chuck Robey , David Gilbert , "Sean O'Connell" , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. In-Reply-To: <200001301942.OAA53806@vger.foo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is on 3.4 Stable, Another "me too", BUT, with a "data point". NEC SuperScript 870, ASUS MB. Had the same problem when the BIOS was set to ECP+EPP on the parallel port. Sinces it only a printer, I set the BIOS to Normal and deliberately tried to introduce the problem (pull paper tray, etc). Didn't have the problem. Two things had happened, the BIOS change and I removed the "flags 0x40" from the config file. Relevant piece of dmesg: ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppb0: IEEE1284 device found /NIBBLE Probing for PnP devices on ppbus0: ppbus0: PRINTER PrintGear,PCL,PJL lpt0: on ppbus 0 lpt0: Interrupt-driven port dmesg prior to the change: ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/7 bytes threshold lpt0: on ppbus 0 lpt0: Interrupt-driven port Notice it used to say SMC-like chipset? Just a data point. m On Sun, 30 Jan 2000, Brian Dean wrote: > > For what its worth, I am able to reproduce this problem on my system. > Simply submit something to lpr, wait for the printer light to blink, > and pull the paper tray. The system hangs hard as described and does > not return to normal until the paper tray is put back in. I haven't > been able to make it do anything while the printer has the system > hung, so I haven't been able to track it down, yet. However, I > haven't had much time to spend on this problem, but thought I'd chime > in a "me too" when I saw someone had the (apparently) same problem. > > I have an HP LaserJet 4 connected to the parallel port. > > I am running -current, and a buildworld as of about a week ago. > > -Brian > -- > Brian Dean brdean@mindspring.com > > > Here's my dmesg: > > Copyright (c) 1992-2000 The FreeBSD Project. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 4.0-CURRENT #0: Sun Jan 23 09:10:33 EST 2000 > bsd@vger.foo.com:/usr/src/sys/compile/VGER > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 300682757 Hz > CPU: Pentium II/Xeon/Celeron (300.68-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x652 Stepping = 2 > Features=0x183f9ff > real memory = 201326592 (196608K bytes) > avail memory = 192131072 (187628K bytes) > Preloaded elf kernel "kernel" at 0xc02f3000. > Pentium Pro MTRR support enabled > md0: Malloc disk > npx0: on motherboard > npx0: INT 16 interface > pcib0: on motherboard > pci0: on pcib0 > pcib1: at device 1.0 on pci0 > pci1: on pcib1 > isab0: at device 7.0 on pci0 > isa0: on isab0 > ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 > ata-pci0: Busmastering DMA supported > ata0 at 0x01f0 irq 14 on ata-pci0 > pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 11 > chip1: port 0x5000-0x500f at device 7.3 on pci0 > vga-pci0: mem 0xe5000000-0xe5ffffff,0xe4000000-0xe4ffffff irq 10 at device 9.0 on pci0 > xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xc400-0xc43f irq 5 at device 10.0 on pci0 > xl0: Ethernet address: 00:60:08:17:67:f9 > miibus0: on xl0 > nsphy0: on miibus0 > nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > ahc0: port 0xc800-0xc8ff mem 0xe9000000-0xe9000fff irq 9 at device 11.0 on pci0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > pci0: unknown card (vendor=0x1102, dev=0x0002) at 12.0 irq 11 > pci0: unknown card (vendor=0x1102, dev=0x7002) at 12.1 > fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > ata-isa0: already registered as ata0 > atkbdc0: at port 0x60-0x6f on isa0 > atkbd0: irq 1 on atkbdc0 > psm0: irq 12 on atkbdc0 > psm0: model Generic PS/2 mouse, device ID 0 > vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 > sc0: on isa0 > sc0: VGA <16 virtual consoles, flags=0x200> > sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 > sio0: type 16550A > sio1 at port 0x2f8-0x2ff irq 3 on isa0 > sio1: type 16550A > ppc0: at port 0x378-0x37f irq 7 on isa0 > ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode > lpt0: on ppbus0 > lpt0: Interrupt-driven port > ppi0: on ppbus0 > IP packet filtering initialized, divert enabled, rule-based forwarding disabled, unlimited logging > Waiting 15 seconds for SCSI devices to settle > acd0: CDROM drive at ata0 as master > acd0: 128KB buffer, PIO4 > acd0: Reads: CD-R, CD-RW, CD-DA stream, packet > acd0: Audio: play, 255 volume levels > acd0: Mechanism: ejectable tray > acd0: Medium: no/blank disc inside, unlocked > Mounting root from ufs:/dev/da0a > da2 at ahc0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI-2 device > da2: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da2: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da1: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > 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: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > da4 at ahc0 bus 0 target 6 lun 0 > da4: Removable Direct Access SCSI-2 device > da4: 10.000MB/s transfers (10.000MHz, offset 15) > da4: Attempt to query device size failed: NOT READY, Medium not present > da3 at ahc0 bus 0 target 3 lun 0 > da3: Fixed Direct Access SCSI-2 device > da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit) > da3: 8683MB (17783204 512 byte sectors: 255H 63S/T 1106C) > pid 52635 (communicator-4.6), uid 1000: exited on signal 10 (core dumped) > > > Dan Sobral wrote: > > Chuck Robey wrote: > > > > > > Sheesh. This is a FreeBSD-questions type thing, not current. > > > > I disagree. It is obvious that something is getting locked inside the > > kernel in his setup. This *SHOULDN'T* happen, it's that simple. If his > > machine locked whenever the printer went out of paper, and *stayed* > > locked, I'd be willing to believe the problem was caused by hardware. > > That's not what was reported. What was reported is rather (better) > > explained by some kernel code waiting indefinitely for an event, while > > preventing anything else from executing. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 16: 7:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from niwa.cri.nz (clam.niwa.cri.nz [131.203.55.1]) by hub.freebsd.org (Postfix) with ESMTP id 1A97E1535D for ; Sun, 30 Jan 2000 16:07:07 -0800 (PST) (envelope-from w.knowles@niwa.cri.nz) Received: from niwa.cri.nz (tornado.niwa.cri.nz [131.203.58.14]) by niwa.cri.nz (8.9.3/8.9.3) with ESMTP id NAA51656; Mon, 31 Jan 2000 13:06:10 +1300 (NZDT) Message-ID: <3894D2CC.69CDDDD4@niwa.cri.nz> Date: Mon, 31 Jan 2000 13:09:48 +1300 From: Wayne Knowles Organization: NIWA (NZ) Ltd X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: itojun@iijlab.net Cc: current@FreeBSD.ORG, Yoshinobu Inoue , Alex Zepeda , Mattias Pantzare Subject: Re: INET6 and fxp References: <20615.949212875@coconut.itojun.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG itojun@iijlab.net wrote: > >FWIW this doesn't happen with my card: > > > >fxp0: port 0x1000-0x103f mem 0xf4000000-0xf40 > >fffff,0xf4100000-0xf4100fff irq 10 at device 15.0 on pci0 > >fxp0: Ethernet address 00:90:27:d1:83:6a > >fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a > >fxp0: starting DAD for fe80:0001::0290:27ff:fed1:836a > >fxp0: DAD complete for fe80:0001::0290:27ff:fed1:836a - no duplicates found > > > > > >'course I don't actually use the card for internet access, just a local > >lan and the occasional IPv6 testing. > > (from what I've heard) the symptom highly depends on chip revision > so you are lucky. > > itojun The problem only occurs on faster machines. For me it didn't work in a PII 400MHz machine but moving the offending card to a P133 machine made it work again. The addition of the DELAY() fixes the problem. The problem stems from the fact that the driver init routine is called twice in quick succession - once for IPv4 and again for IPv6. The other way of fixing it is to disable the call to ifp->if_ioctl in netinet6/in6_ifattach.c Wayne -- _____ Wayne Knowles, Systems Manager / o \/ National Institute of Water & Atmospheric Research Ltd \/ v /\ P.O. Box 14-901 Kilbirnie, Wellington, NEW ZEALAND `---' Email: w.knowles@niwa.cri.nz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 17: 3:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from eclogite.eps.nagoya-u.ac.jp (eclogite.eps.nagoya-u.ac.jp [133.6.124.145]) by hub.freebsd.org (Postfix) with ESMTP id 8B88914E4F; Sun, 30 Jan 2000 17:02:51 -0800 (PST) (envelope-from kato@ganko.eps.nagoya-u.ac.jp) Received: from localhost (gneiss.eps.nagoya-u.ac.jp [133.6.124.148]) by eclogite.eps.nagoya-u.ac.jp (8.9.3/3.7W) with ESMTP id KAA06803; Mon, 31 Jan 2000 10:02:42 +0900 (JST) To: kris@hub.freebsd.org Cc: current@freebsd.org Subject: Re: identcpu.c change causes panic From: KATO Takenori In-Reply-To: Your message of "Sun, 30 Jan 2000 12:50:01 -0800 (PST)" References: X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) X-PGP-Fingerprint: 03 72 85 36 62 46 23 03 52 B1 10 22 44 10 0D 9E Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000131100212N.kato@gneiss.eps.nagoya-u.ac.jp> Date: Mon, 31 Jan 2000 10:02:12 +0900 X-Dispatcher: imput version 980905(IM100) Lines: 30 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > Yes, when I back out this revision (& nothing else) I can boot fine :-) Hmm, I cannot know why you got panic.... On your CPU (P54C: 586-class CPU), the part which I changed is not executed. I have tested the change on: - Intel MMX Pentium 166MHz - Intel Pentium Pro 200MHz - Intel Pentium II 400MHz (Dual) - AMD Athlon 700MHz - AMD K6-2 400MHz - Cyrix 5x86 100MHz and they work without problem. > I'll have to write this down by hand - it didn't look very interesting, > though. I'm interested in it. What I want to know is whether a bug is in my change or in other part. -----------------------------------------------+--------------------------+ KATO Takenori | FreeBSD | Dept. Earth Planet. Sci, Nagoya Univ. | The power to serve! | Nagoya, 464-8602, Japan | http://www.FreeBSD.org/ | |http://www.jp.FreeBSD.org/| ++++ FreeBSD(98) 3.3R-Rev. 01 available! +==========================+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 17:17: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from goofy.zort.on.ca (cr575310-a.shprd1.on.wave.home.com [24.112.185.167]) by hub.freebsd.org (Postfix) with ESMTP id 3C31A14A00 for ; Sun, 30 Jan 2000 17:16:51 -0800 (PST) (envelope-from rod@zort.on.ca) Received: from rbtBSD.intranet (rbtBSD.zort.on.ca [10.0.0.50]) by goofy.zort.on.ca (Postfix) with SMTP id BD0D540 for ; Sun, 30 Jan 2000 20:16:45 -0500 (EST) From: Rod Taylor Reply-To: rod@zort.on.ca Organization: Zort To: freebsd-current@freebsd.org Subject: Occurred during installworld (Makeworld went off perfectly). Date: Sun, 30 Jan 2000 20:15:08 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <00013020164502.13035@rbtBSD.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please note, I'm attempting to upgrade from -stable to -current. install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option `--defsection=Programming & development tools.' Try `install-info --help' for a complete list of options. *** Error code 1 -- Rod Taylor Partner of Zort (zort.on.ca) -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 17:43:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mrynet.com (mrynet.com [24.234.53.177]) by hub.freebsd.org (Postfix) with ESMTP id AEAEA15325 for ; Sun, 30 Jan 2000 17:43:22 -0800 (PST) (envelope-from freebsd@mrynet.com) Received: (from freebsd@localhost) by mrynet.com (8.9.3/8.9.3) id RAA00650 for freebsd-current@freebsd.org; Sun, 30 Jan 2000 17:43:11 -0800 (PST) (envelope-from freebsd) Posted-Date: Sun, 30 Jan 2000 17:43:11 -0800 (PST) Message-Id: <200001310143.RAA00650@mrynet.com> From: freebsd@mrynet.com (FreeBSD mailing list) Date: Sun, 30 Jan 2000 17:43:11 +0000 X-Mailer: Mail User's Shell (7.2.6 beta(3) 11/17/96) To: freebsd-current@freebsd.org Subject: Re: Printer fiascos Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > For what its worth, I am able to reproduce this problem on my system. > Simply submit something to lpr, wait for the printer light to blink, > and pull the paper tray. The system hangs hard as described and does > not return to normal until the paper tray is put back in. I haven't > been able to make it do anything while the printer has the system > hung, so I haven't been able to track it down, yet. However, I > haven't had much time to spend on this problem, but thought I'd chime > in a "me too" when I saw someone had the (apparently) same problem. > > I have an HP LaserJet 4 connected to the parallel port. > > I am running -current, and a buildworld as of about a week ago. > > -Brian > -- > Brian Dean brdean@mindspring.com I will confirm this problem with the lpt driver. Even worse, on my LaserJet IIIsi printer... Not only did it hang the system, but I went as far as turning the printer off, then back on. THE SYSTEM REBOOTED. There was no panic or other context to share. I suspect it MAY have been related to the about of time it takes the LJ III to cycle on a power-up. Regardless, this is wholly unacceptable for a RELEASE. FWIW, my dmesg follows to show the port-type, etc. ppp0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 pps0: on ppbus0 Cheers, -skots -- Scott G. Akmentins-Taylor InterNet: staylor@mrynet.com MRY Systems staylor@mrynet.lv (Skots Gregorijs Akmentins-Teilors -- just call me "Skots") ----- Labak miris neka sarkans ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 18:25:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from goofy.zort.on.ca (cr575310-a.shprd1.on.wave.home.com [24.112.185.167]) by hub.freebsd.org (Postfix) with ESMTP id 1A7CB14F8A for ; Sun, 30 Jan 2000 18:25:35 -0800 (PST) (envelope-from rod@zort.on.ca) Received: from rbtBSD.intranet (rbtBSD.zort.on.ca [10.0.0.50]) by goofy.zort.on.ca (Postfix) with SMTP id B200440 for ; Sun, 30 Jan 2000 21:25:35 -0500 (EST) From: Rod Taylor Reply-To: rod@zort.on.ca Organization: Zort To: freebsd-current@freebsd.org Subject: Re: Occurred during installworld (Makeworld went off perfectly). Date: Sun, 30 Jan 2000 21:24:09 -0500 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: <00013020164502.13035@rbtBSD.intranet> In-Reply-To: <00013020164502.13035@rbtBSD.intranet> MIME-Version: 1.0 Message-Id: <00013021253403.13035@rbtBSD.intranet> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, you wrote: I've re-cvsupped and noticed UPDATING was changed this time. Upon remaking xinistall, I also discovered I had an incorrect version of libc. (it wanted libc.so.4, I had libc.so.3). Symlinked 3 to 4, we'll see what happens... > Please note, I'm attempting to upgrade from -stable to -current. > > install-info --quiet --defsection="Programming & development tools." > --defentry="* libcom_err: (com_err). A Common Error Description Library > for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option > `--defsection=Programming & development tools.' Try `install-info > --help' for a complete list of options. *** Error code 1 -- Rod Taylor Partner of Zort (zort.on.ca) -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 18:30:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id 7B8E314BCF for ; Sun, 30 Jan 2000 18:30:53 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (local-27.local.net [192.168.1.27]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id SAA13263 for ; Sun, 30 Jan 2000 18:30:52 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <3894F3DC.CB9A4448@MexComUSA.net> Date: Sun, 30 Jan 2000 18:30:52 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "current@FreeBSD.ORG" Subject: libstdc++.so.3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I make a new world today after reinstalling xinstall and thought that along with recompiling my applications that are having problems that I assume started with the c++ compiler change, but I have recompiled several applications and still have the errors. If someone would tell me what I am doing wrong. This is from the latest version of mysql that I just compiled. Error: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined symbol "_vt$9exception" TIA, ed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 18:36:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id 1FEDA14E15 for ; Sun, 30 Jan 2000 18:36:34 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: from shell-1.enteract.com (dscheidt@shell-1.enteract.com [207.229.143.40]) by mail.enteract.com (8.9.3/8.9.3) with SMTP id UAA92985; Sun, 30 Jan 2000 20:36:18 -0600 (CST) (envelope-from dscheidt@enteract.com) Date: Sun, 30 Jan 2000 20:36:18 -0600 (CST) From: David Scheidt To: Warner Losh Cc: Greg Lehey , current@FreeBSD.ORG Subject: Re: PAIN In-Reply-To: <200001300348.UAA11507@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 29 Jan 2000, Warner Losh wrote: > In message <20000130141245.C55643@freebie.lemis.com> Greg Lehey writes: > : I did a make world on my PDP-11 yesterday. It took less than a day. > : But that's 2.11BSD. > > Turns out that 12MB + 30MB of swap isn't enough to build world. I ran > out of swap and the machine rebooted (at least that's what I think > happened, since it silently rebooted). Are you using -pipe? That drastically increases memory requirements. David To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 18:49: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id AD27C14E40 for ; Sun, 30 Jan 2000 18:48:59 -0800 (PST) (envelope-from cdf.lists@fxp.org) Received: by pawn.primelocation.net (Postfix, from userid 1016) id ABD0C9B17; Sun, 30 Jan 2000 21:48:55 -0500 (EST) Received: from localhost (localhost [127.0.0.1]) by pawn.primelocation.net (Postfix) with ESMTP id A3292BA1D; Sun, 30 Jan 2000 21:48:55 -0500 (EST) Date: Sun, 30 Jan 2000 21:48:55 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: cdf.lists@pawn.primelocation.net To: Edwin Culp Cc: "current@FreeBSD.ORG" Subject: Re: libstdc++.so.3 In-Reply-To: <3894F3DC.CB9A4448@MexComUSA.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, Edwin Culp wrote: > I make a new world today after reinstalling xinstall and thought that > along with recompiling my applications that are having problems that I > assume started with the c++ compiler change, but I have recompiled > several applications and still have the errors. > > If someone would tell me what I am doing wrong. This is from the latest > version of mysql that I just compiled. > > Error: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined > symbol > "_vt$9exception" > Please read the first 20000124 entry of src/UPDATING. ----- 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-current" in the body of the message From owner-freebsd-current Sun Jan 30 18:59:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id F0DC314D09 for ; Sun, 30 Jan 2000 18:59:48 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (local-27.local.net [192.168.1.27]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id SAA13452; Sun, 30 Jan 2000 18:59:46 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <3894FAA2.3CD256A4@MexComUSA.net> Date: Sun, 30 Jan 2000 18:59:46 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Chris D. Faulhaber" Cc: "current@FreeBSD.ORG" Subject: Re: libstdc++.so.3 References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Looks like I have to cvsup again, it's not in my UPDATING from 11:40 PST today. That was the first place I checked. Sorry and thanks, ed "Chris D. Faulhaber" wrote: > On Sun, 30 Jan 2000, Edwin Culp wrote: > > > I make a new world today after reinstalling xinstall and thought that > > along with recompiling my applications that are having problems that I > > assume started with the c++ compiler change, but I have recompiled > > several applications and still have the errors. > > > > If someone would tell me what I am doing wrong. This is from the latest > > version of mysql that I just compiled. > > > > Error: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined > > symbol > > "_vt$9exception" > > > > Please read the first 20000124 entry of src/UPDATING. > > ----- > 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-current" in the body of the message From owner-freebsd-current Sun Jan 30 19: 7:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from m2.cs.berkeley.edu (m2.CS.Berkeley.EDU [128.32.45.178]) by hub.freebsd.org (Postfix) with ESMTP id 945DC14DAC for ; Sun, 30 Jan 2000 19:07:38 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: from bubble.didi.com (sji-ca7-14.ix.netcom.com [209.109.235.14]) by m2.cs.berkeley.edu (8.9.3/8.9.3) with ESMTP id TAA85395; Sun, 30 Jan 2000 19:07:36 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Received: (from asami@localhost) by bubble.didi.com (8.9.3/8.8.8) id TAA05532; Sun, 30 Jan 2000 19:05:59 -0800 (PST) (envelope-from asami@cs.berkeley.edu) Date: Sun, 30 Jan 2000 19:05:59 -0800 (PST) Message-Id: <200001310305.TAA05532@bubble.didi.com> X-Authentication-Warning: bubble.didi.com: asami set sender to asami@cs.berkeley.edu using -f To: dillon@apollo.backplane.com Cc: current@FreeBSD.ORG In-reply-to: <200001221733.JAA72550@apollo.backplane.com> (message from Matthew Dillon on Sat, 22 Jan 2000 09:33:27 -0800 (PST)) Subject: Re: crashes From: asami@FreeBSD.ORG (Satoshi - Ports Wraith - Asami) References: <200001120008.QAA89430@silvia.hip.berkeley.edu> <200001120234.SAA66268@apollo.backplane.com> <200001221137.DAA93326@silvia.hip.berkeley.edu> <200001221733.JAA72550@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * From: Matthew Dillon * Ah, that's good. I still have one person reporting a panic with 1.56 * (which I have a core for). w/1.56 my own buildworld tests succeed * and except for this one person everyone else is reporting their * softupdates problems solved. Actually maybe I spoke too soon. Two of the machines just hung this morning. Same symptom (responds to ping, telnet connects but gets only blank lines in responses to return) as before. This is a slightly newer kernel (had to put IPv6 in it) but ffs_softdep.c is still at 1.56. Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 19:11:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from dsl.MexComUSA.net (adsl-63-194-214-46.dsl.snfc21.pacbell.net [63.194.214.46]) by hub.freebsd.org (Postfix) with ESMTP id C6C8414CA8 for ; Sun, 30 Jan 2000 19:11:29 -0800 (PST) (envelope-from eculp@MexComUSA.net) Received: from MexComUSA.net (local-27.local.net [192.168.1.27]) by dsl.MexComUSA.net (8.9.3/8.9.3) with ESMTP id TAA13551; Sun, 30 Jan 2000 19:11:27 -0800 (PST) (envelope-from eculp@MexComUSA.net) Message-ID: <3894FD5F.8E8D0BB3@MexComUSA.net> Date: Sun, 30 Jan 2000 19:11:27 -0800 From: Edwin Culp Organization: Mexico Communicates, S.C. X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Chris D. Faulhaber" , "current@FreeBSD.ORG" Subject: Re: libstdc++.so.3 References: <3894FAA2.3CD256A4@MexComUSA.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just got the new UPDATING and I seem to have done everything. Until I built xinstall, I wasn't able to make world, made a new kernel and rebooted and built a new version of mysql and am still getting the error. I'm going to build a new world, just in case my cvsup timing was bad. Thanks a lot for your help, ed Edwin Culp wrote: > Looks like I have to cvsup again, it's not in my UPDATING from 11:40 PST > today. That was the first place I checked. > > Sorry and thanks, > > ed > > "Chris D. Faulhaber" wrote: > > > On Sun, 30 Jan 2000, Edwin Culp wrote: > > > > > I make a new world today after reinstalling xinstall and thought that > > > along with recompiling my applications that are having problems that I > > > assume started with the c++ compiler change, but I have recompiled > > > several applications and still have the errors. > > > > > > If someone would tell me what I am doing wrong. This is from the latest > > > version of mysql that I just compiled. > > > > > > Error: /usr/libexec/ld-elf.so.1: /usr/lib/libstdc++.so.3: Undefined > > > symbol > > > "_vt$9exception" > > > > > > > Please read the first 20000124 entry of src/UPDATING. > > > > ----- > > 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-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 19:38:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 7331414A0B for ; Sun, 30 Jan 2000 19:38:49 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id A3C3F137FB6; Sun, 30 Jan 2000 22:38:47 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id WAA37910; Sun, 30 Jan 2000 22:38:58 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14485.977.915643.838575@trooper.velocet.net> Date: Sun, 30 Jan 2000 22:38:57 -0500 (EST) To: Michael Remski Cc: Brian Dean , "Daniel C. Sobral" , Chuck Robey , David Gilbert , "Sean O'Connell" , freebsd-current@FreeBSD.ORG Subject: Re: Printer fiascos. In-Reply-To: References: <200001301942.OAA53806@vger.foo.com> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Michael" == Michael Remski writes: Michael> ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: SMC-like chipset Michael> (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with Michael> 16/16/7 bytes threshold lpt0: on ppbus 0 Michael> lpt0: Interrupt-driven port I don't get the FIFO portion of the probe. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 20:54: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from orange.kame.net (orange.kame.net [203.178.141.194]) by hub.freebsd.org (Postfix) with ESMTP id 688EE14DAE for ; Sun, 30 Jan 2000 20:53:58 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from localhost (kame217.kame.net [203.178.141.217]) by orange.kame.net (8.9.1+3.1W/3.7W) with ESMTP id NAA29441; Mon, 31 Jan 2000 13:53:57 +0900 (JST) To: pantzer@ludd.luth.se Cc: current@FreeBSD.ORG Subject: Re: INET6 and fxp In-Reply-To: <200001301306.OAA12826@queeg.ludd.luth.se> References: <200001301306.OAA12826@queeg.ludd.luth.se> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000131135436K.shin@nd.net.fujitsu.co.jp> Date: Mon, 31 Jan 2000 13:54:36 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 14 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > http://www.sigmasoft.com/~openbsd/archive/openbsd-tech/199912/msg00321.html > > > > > > Something better than that is probably needed in the long run. > > > > Let me confirm it. > > Does this also fix your problem on your freebsd-current? > > Yes. I have only tried ping6, but that works, and IPv4 works. Thanks, then it might be better to add same kind of fix to if.c's "#ifdef INET6" part, as a workaround only for 4.0. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 21:19:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id AC88F14CFC; Sun, 30 Jan 2000 21:19:15 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id VAA84869; Sun, 30 Jan 2000 21:18:54 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200001310518.VAA84869@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Cc: Jean-Marc Zucconi Subject: Re: new C++ compiler changes In-reply-to: Your message of "Sun, 30 Jan 2000 12:29:13 PST." <20000130122913.A3379@dragon.nuxi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 30 Jan 2000 21:18:54 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > rename it libstdc++.so.1. Then you just have to modify your executable > > so that it looks for libstdc++.so.1 instead of libstdc++.so.3 > > Why not just reinstall the problematic executables? > Yeap, we do that quite often in Linux 8) Cheers -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 21:30:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [171.64.234.70]) by hub.freebsd.org (Postfix) with ESMTP id 2FCEA14CE7 for ; Sun, 30 Jan 2000 21:30:36 -0800 (PST) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id VAA46265 for current@freebsd.org; Sun, 30 Jan 2000 21:30:35 -0800 (PST) Date: Sun, 30 Jan 2000 21:30:35 -0800 (PST) From: Bob Vaughan Message-Id: <200001310530.VAA46265@tantivy.stanford.edu> To: current@freebsd.org Subject: suspend problems Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm running world built on the 26th, and a kernel built immediately afterwards.. machine is a chembook 3300. if i suspend, upon resuming i get a brief flash of X, and then a black screen. i have to kill X to get a display back. also, while my 3c574 comes back up, it loses the configuration info that was entered by hand after the card came up. (actually, this might have happened when i killed X.. the realaudio stream that i was playing when i suspended came back when i resumed..) Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #9: Thu Jan 27 02:08:53 PST 2000 techie@roadwarrior.stanford.edu:/c1/current/src/sys/compile/ROADWARRIOR Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (233.86-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 100663296 (98304K bytes) avail memory = 93683712 (91488K bytes) Preloaded elf kernel "kernel" at 0xc03b4000. Preloaded elf module "splash_bmp.ko" at 0xc03b409c. Preloaded elf module "vesa.ko" at 0xc03b4140. Preloaded splash_image_data "/boot/splash.bmp" at 0xc03b41dc. Preloaded elf module "cd9660.ko" at 0xc03b422c. Preloaded elf module "linux.ko" at 0xc03b42cc. Intel Pentium detected, installing workaround for F00F bug VESA: v1.2, 2048k memory, flags:0x0, mode table:0xc00c7a88 (c0007a88) VESA: Copyright 1994 TRIDENT MICROSYSTEMS INC. md0: Malloc disk apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 ata-pci0: port 0x1100-0x110f at device 1.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 uhci0: irq 0 at device 1.2 on pci0 uhci0: could not map ports device_probe_and_attach: uhci0 attach returned 6 chip1: port 0x1400-0x140f at device 1.3 on pci0 vga-pci0: mem 0xfe000000-0xfe3fffff,0xfe7f0000-0xfe7fffff,0xfdc00000-0xfdffffff at device 2.0 on pci0 pcic-pci0: irq 10 at device 3.0 on pci0 pcic-pci1: irq 10 at device 3.1 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic: management irq 10 pcic0: at irq 10 on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 sio2: not probed (disabled) sio3: not probed (disabled) ppc0: at port 0x378-0x37f irq 7 flags 0x40 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port unknown0: at port 0x800-0x807 on isa0 sbc0: at port 0x220-0x22f,0x388-0x38b,0x330-0x331 irq 5 drq 1,0 on isa0 pcm0: on sbc0 unknown1: at port 0x201 on isa0 pccard: card inserted, slot 1 ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 3909MB [7944/16/63] at ata0-master using UDMA33 acd0: CDROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a ep0: <3Com 3C574B, Megahertz 3CCFE574BT or Fast Etherlink 3C574-TX> at port 0x240-0x25f irq 9 slot 1 on pccard1 ep0: Ethernet address 00:50:04:8f:2a:8b ep0: unload stray irq 9 pccard: card disabled, slot 1 pccard: card inserted, slot 1 resumed from suspended mode (slept 00:01:30) ata0: resetting devices .. done ata1: resetting devices .. done ep0: <3Com 3C574B, Megahertz 3CCFE574BT or Fast Etherlink 3C574-TX> at port 0x240-0x25f irq 9 slot 1 on pccard1 ep0: Ethernet address 00:50:04:8f:2a:8b # # ROADWARRIOR -- Laptop machine with ide/usb/pcmcia/tools # # $Id: ROADWARRIOR,v 1.143.3.1.3 1999/12/08 23:00:00 techie Exp $ machine "i386" cpu I586_CPU # aka Pentium(tm) ident ROADWARRIOR maxusers 30 makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options NFS #Network Filesystem #options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores ## options from LINT options MD5 options PERFMON options NETATALK options ICMP_BANDLIM options PCIC_RESUME_RESET options MROUTING # Multicast routing options POWERFAIL_NMI options INCLUDE_CONFIG_FILE options DDB options PPP_BSDCOMP #PPP BSD-compress support options PPP_DEFLATE #PPP zlib/deflate/gzip support options PPP_FILTER #enable bpf filtering (needs bpf) #options PNPBIOS device isa0 #device pnp0 device pci0 device ata0 device atadisk0 device atapicd0 #device atapifd0 options ATA_ENABLE_ATAPI_DMA device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 device fd1 at fdc0 drive 1 # atkbdc0 controlls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts pseudo-device splash pseudo-device md device sc0 at isa? # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? #options XSERVER # support for X server #options FAT_CURSOR # start with block cursor device npx0 at nexus? port IO_NPX irq 13 device apm0 at nexus? flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support device pcic0 at isa? device pcic1 at isa? device card0 device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 device sio2 at isa? disable port IO_COM3 irq 5 device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 irq 7 device ppbus0 # Parallel port bus (required) device lpt0 # Printer #device plip0 # TCP/IP over parallel #device ppi0 # Parallel port interface device device ep0 device ed0 device ed1 at isa? port 0x320 irq 11 conflicts iomem 0xd8000 # audio device pcm0 device sbc0 pseudo-device loop pseudo-device ether pseudo-device tun 4 pseudo-device pty 64 pseudo-device gzip # Exec gzipped a.out's pseudo-device bpf 4 # Berkeley packet filter pseudo-device snp # USB support device uhci0 # UHCI PCI->USB interface device usb0 # USB Bus (required) device ugen0 # Generic device uhid0 # "Human Interface Devices" device ukbd0 # Keyboard device ulpt0 # Printer #device umass0 # Disks/Mass storage - Requires scbus and da0 device ums0 # Mouse -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 19792, Stanford, Ca 94309 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 21:37:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from darkstar.qx.net (darkstar.qx.net [208.235.88.101]) by hub.freebsd.org (Postfix) with ESMTP id A52EC1533C for ; Sun, 30 Jan 2000 21:37:22 -0800 (PST) (envelope-from gchil0@pop.uky.edu) Received: from mail.qx.net (mail.qx.net [208.235.88.10]) by darkstar.qx.net (8.8.7/8.8.7) with ESMTP id AAA18065 for ; Mon, 31 Jan 2000 00:37:20 -0500 Received: from k7 ([208.200.111.144]) by mail.qx.net (Netscape Messaging Server 3.6) with ESMTP id AAA5140; Mon, 31 Jan 2000 00:40:10 -0500 Message-Id: <4.2.0.58.20000131003612.00951ad0@pop.uky.edu> X-Sender: gchil0@pop.uky.edu X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Mon, 31 Jan 2000 00:38:52 -0500 To: KATO Takenori , kris@hub.freebsd.org From: Greg Childers Subject: Re: identcpu.c change causes panic - not identcpu.c? Cc: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A panic also occurred on my Pentium (P54C) 66MHz, but backing identcpu.c to 1.79 didn't stop the panic. Here is the panic info, copied by hand. (I hope there are no typos!) Lots of 'ad1: timeout waiting for DRQ' followed by Fatal trap 12: page fault while in kernel mode fault virtual address = 0xc04e5000 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01c56b0 stack pointer = 0x10:0xc49efd7c frame pointer = 0x10:0xc49efda0 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 = 133 (ldconfig) interrupt mask = net tty bio cam trap number = 12 panic: page fault Uptime: 12s Unfortunately, I don't have time right now to explore this further, but if more info is needed, just tell me what to do and I can help tomorrow evening (EST). Greg > > Yes, when I back out this revision (& nothing else) I can boot fine :-) > > Hmm, I cannot know why you got panic.... On your CPU (P54C: 586-class > CPU), the part which I changed is not executed. > > I have tested the change on: > > - Intel MMX Pentium 166MHz > - Intel Pentium Pro 200MHz > - Intel Pentium II 400MHz (Dual) > - AMD Athlon 700MHz > - AMD K6-2 400MHz > - Cyrix 5x86 100MHz > > and they work without problem. > > > I'll have to write this down by hand - it didn't look very interesting, > > though. > > I'm interested in it. What I want to know is whether a bug is in my > change or in other part. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 21:39:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from noop.colo.erols.net (noop.colo.erols.net [207.96.1.150]) by hub.freebsd.org (Postfix) with ESMTP id 4D6E715199 for ; Sun, 30 Jan 2000 21:39:38 -0800 (PST) (envelope-from gjp@in-addr.com) Received: from localhost ([127.0.0.1] helo=in-addr.com) by noop.colo.erols.net with esmtp (Exim 3.12 #1) id 12F9Yk-000LWA-00; Mon, 31 Jan 2000 00:39:34 -0500 To: Alex Zepeda Cc: current@FreeBSD.ORG From: Gary Palmer Subject: Re: PAIN In-Reply-To: Message from Alex Zepeda of "Sat, 29 Jan 2000 22:04:42 PST." Date: Mon, 31 Jan 2000 00:39:34 -0500 Message-ID: <82717.949297174@in-addr.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alex Zepeda wrote in message ID : > On Sun, 30 Jan 2000, kibbet wrote: > > > /me looks at the bunch of 386 mobo's... lets not go there.. :) > > /me looks at the stack of 386sx chips he has and wonders why no-one did 8 > way SMP with these! You never heard of the Sequent boxes, did you? :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 21:39:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from viper.columbus.rr.com (viper.columbus.rr.com [204.210.252.254]) by hub.freebsd.org (Postfix) with ESMTP id 8654415A6A for ; Sun, 30 Jan 2000 21:39:47 -0800 (PST) (envelope-from dzerkel@columbus.rr.com) Received: from columbus.rr.com (dhcp26140113.columbus.rr.com [24.26.140.113]) by viper.columbus.rr.com (8.9.3/8.9.3) with ESMTP id AAA02929 for ; Mon, 31 Jan 2000 00:39:45 -0500 (EST) Message-ID: <38952020.D447FB6E@columbus.rr.com> Date: Mon, 31 Jan 2000 00:39:45 -0500 From: "Danny J. Zerkel" Organization: Zerkular Software X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: Russian, ru, en MIME-Version: 1.0 To: FreeBSD Current Subject: Re: pmap_remove_pages panic during installworld References: <38903769.38338FE4@columbus.rr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, with all problems with buildworld and building kernels, and my limited time. I have only just gotten back to a point where I can retest the crash I was having. This time, no crash. Apparently, my milage is varying... -- Danny J. Zerkel dzerkel@columbus.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 21:50:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from bekool.com (ns2.netquick.net [216.48.34.2]) by hub.freebsd.org (Postfix) with ESMTP id EA36F14D5A for ; Sun, 30 Jan 2000 21:50:52 -0800 (PST) (envelope-from trouble@netquick.net) Received: from angelsguardian.netquick.net ([199.72.47.239] helo=netquick.net) by bekool.com with esmtp (Exim 3.03 #1) id 12FAKV-0004ad-00; Mon, 31 Jan 2000 01:28:55 -0500 Message-ID: <3895250C.53B0020A@netquick.net> Date: Mon, 31 Jan 2000 01:00:44 -0500 From: TrouBle Reply-To: trouble@netquick.net X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Gary Palmer Cc: Alex Zepeda , current@FreeBSD.ORG Subject: Re: PAIN References: <82717.949297174@in-addr.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Geee lets see i have a 386 sx with a really tiny MFM in it still, its just sitting here, doing nothing, wonder if i can get current on it, the thought is killing me... : )) its got 8 megs of ram in it too ??? ~GRIN~ Gary Palmer wrote: > Alex Zepeda wrote in message ID > : > > On Sun, 30 Jan 2000, kibbet wrote: > > > > > /me looks at the bunch of 386 mobo's... lets not go there.. :) > > > > /me looks at the stack of 386sx chips he has and wonders why no-one did 8 > > way SMP with these! > > You never heard of the Sequent boxes, did you? :) > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 22:11:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mta3.snfc21.pbi.net (mta3.snfc21.pbi.net [206.13.28.141]) by hub.freebsd.org (Postfix) with ESMTP id F100814C22 for ; Sun, 30 Jan 2000 22:11:52 -0800 (PST) (envelope-from jazepeda@pacbell.net) Received: from zippy.dyn.ml.org ([207.214.149.184]) by mta3.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.1999.09.16.21.57.p8) with ESMTP id <0FP600D6NRUW2U@mta3.snfc21.pbi.net> for current@FreeBSD.ORG; Sun, 30 Jan 2000 22:11:21 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by zippy.dyn.ml.org (Postfix) with ESMTP id 5D1D19151F; Sun, 30 Jan 2000 22:11:20 -0800 (PST) Date: Sun, 30 Jan 2000 22:11:20 -0800 (PST) From: Alex Zepeda Subject: Re: PAIN In-reply-to: <82717.949297174@in-addr.com> To: Gary Palmer Cc: current@FreeBSD.ORG Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Gary Palmer wrote: > > /me looks at the stack of 386sx chips he has and wonders why no-one did 8 > > way SMP with these! > > You never heard of the Sequent boxes, did you? :) In fact I haven't. But I also don't have DXs either. :) - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 22:29:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from tigger.nu.org (spark1.zip.com.au [61.8.19.145]) by hub.freebsd.org (Postfix) with ESMTP id E1C0F1504A for ; Sun, 30 Jan 2000 22:29:11 -0800 (PST) (envelope-from vance@nu.org) Received: by tigger.nu.org (Postfix, from userid 1000) id 77956389; Mon, 31 Jan 2000 17:27:59 +1100 (EST) Date: Mon, 31 Jan 2000 17:27:58 +1100 From: Christopher Vance To: TrouBle Cc: Gary Palmer , Alex Zepeda , current@FreeBSD.ORG Subject: Re: PAIN Message-ID: <20000131172758.B21646@nu.org> References: <82717.949297174@in-addr.com> <3895250C.53B0020A@netquick.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <3895250C.53B0020A@netquick.net>; from trouble@netquick.net on Mon, Jan 31, 2000 at 01:00:44AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 31, 2000 at 01:00:44AM -0500, TrouBle wrote: : Geee lets see i have a 386 sx with a really tiny MFM in it still, its just : sitting here, doing nothing, wonder if i can get current on it, the thought is : killing me... : )) its got 8 megs of ram in it too ??? ~GRIN~ I'm running a PicoBSD firewall on a 386DX with 8MB. (Well, maybe it's just a screening router...). Mind you, it's pBSD off 3.4-STABLE, not off -CURRENT. But I'm planning to see whether I can do it with -CURRENT so I can get IPv6 in there too. (I'm not using any HD at the moment, but I may have to steal a bit of space of MSW3.11.) -- Christopher Vance To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 23:30:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from quack.kfu.com (quack.kfu.com [170.1.70.2]) by hub.freebsd.org (Postfix) with ESMTP id 0B62E14D61; Sun, 30 Jan 2000 23:30:19 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from icarus.kfu.com (icarus.kfu.com [170.1.70.17]) by quack.kfu.com (8.9.2/8.9.3) with ESMTP id XAA99993; Sun, 30 Jan 2000 23:30:15 -0800 (PST) (envelope-from nsayer@quack.kfu.com) Received: from quack.kfu.com by icarus.kfu.com with ESMTP (8.9.3//ident-1.0) id XAA10901; Sun, 30 Jan 2000 23:30:10 -0800 (PST) Message-ID: <38953A01.D801778@quack.kfu.com> Date: Mon, 31 Jan 2000 07:30:09 +0000 From: Nick Sayer Reply-To: nsayer@freebsd.org X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.0.36 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-emulation@freebsd.org, freebsd-current@freebsd.org Subject: VMware & SCSI CDROM - fix Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This fixes the error messages seen when attempting to use a SCSI cdrom drive with vmware. It is unclear to me whether this would do more harm than good, since I don't really know what the CDIOCREADSUBCHANNEL ioctl does. But it does look righteous to me, since without it, the 'track' variable in the bsdsc will be not be initialized prior to the fo_ioctl(). I can commit this if it would be easiest, though I think someone who knows this area better than me should comment first. :-) --- sys/i386/linux/linux_ioctl.c.orig Sun Jan 30 23:09:11 2000 +++ sys/i386/linux/linux_ioctl.c Sun Jan 30 22:56:07 2000 @@ -890,6 +890,7 @@ sizeof(struct cd_sub_channel_info)); bsdsc.address_format = CD_LBA_FORMAT; bsdsc.data_format = CD_CURRENT_POSITION; + bsdsc.track = 0; bsdsc.data_len = sizeof(struct cd_sub_channel_info); bsdsc.data = bsdinfo; error = fo_ioctl(fp, CDIOCREADSUBCHANNEL, (caddr_t)&bsdsc, p); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sun Jan 30 23:51:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by hub.freebsd.org (Postfix) with ESMTP id A878F14C90 for ; Sun, 30 Jan 2000 23:51:51 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id XAA32676; Sun, 30 Jan 2000 23:52:01 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id XAA24010; Sun, 30 Jan 2000 23:54:27 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Sun, 30 Jan 2000 23:54:26 -0800 (PST) From: Brian Beattie To: Gary Palmer Cc: Alex Zepeda , current@FreeBSD.ORG Subject: Re: PAIN In-Reply-To: <82717.949297174@in-addr.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Gary Palmer wrote: > Alex Zepeda wrote in message ID > : > > On Sun, 30 Jan 2000, kibbet wrote: > > > > > /me looks at the bunch of 386 mobo's... lets not go there.. :) > > > > /me looks at the stack of 386sx chips he has and wonders why no-one did 8 > > way SMP with these! > > You never heard of the Sequent boxes, did you? :) Sequent never did 386SX, they did 386DX > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 1:30:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 46B1714C0A for ; Mon, 31 Jan 2000 01:30:34 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id AAA01879; Mon, 31 Jan 2000 00:22:36 GMT (envelope-from n_hibma@webweaving.org) Date: Mon, 31 Jan 2000 00:22:36 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Jun Kuriyama Cc: FreeBSD CURRENT Mailing List Subject: Re: NEC ohci In-Reply-To: <14470.36398.333535.99329N@localhost.sky.rim.or.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems that support for OHCI type controllers for USB is completely broken at the moment. Why things all of a sudden fall over (before I committed the changes to ohci.c even) is beyond me, but there must be a reason. Please subscribe to usb-bsd@egroups.com. That's were most of the discussion is going on. Nick On Thu, 20 Jan 2000, Jun Kuriyama wrote: > From: Nick Hibma > > Try running usbd -e and see if that makes your mouse show up. usbd -e > > does the explore once. > > I've tested on another machine with same NEC OHCI (Toshiba Libretto SS > 1000). > > ----- dmesg > ohci0: mem 0xffaff000-0xffafffff irq 11 at device 11.0 on pci0 > usb0: OHCI version 1.0 > usb0: on ohci0 > usb0: USB revision 1.0 > uhub0: NEC OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub0: 2 ports with 2 removable, self powered > ----- > > When I plugged USB ethernet device (aue0), there is no message. And > I've got message if I use "usbd -e". > > ----- > usb0: unrecoverable error, controller halted > usbd_new_device: addr=2, getting first desc failed > uhub_explore: usb_new_device failed, error=TIMEOUT > uhub0: device problem, disabling port 1 > ----- > > PCI IRQ 11 of this machine is shared with other devices. > > > Jun Kuriyama // kuriyama@sky.rim.or.jp > // kuriyama@FreeBSD.org > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 1:53:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id D196214C8F; Mon, 31 Jan 2000 01:53:26 -0800 (PST) (envelope-from marcel@scc.nl) Received: from [212.238.132.94] (helo=spike.adm.scc.nl) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 12FDWO-000347-00; Mon, 31 Jan 2000 09:53:24 +0000 Received: from cas (cas.adm.scc.nl [192.168.1.3]) by spike.adm.scc.nl (8.9.3/8.9.3) with SMTP id KAA93768; Mon, 31 Jan 2000 10:52:59 +0100 (CET) (envelope-from marcel@scc.nl) Message-ID: <004e01bf6bd1$01eb54c0$0301a8c0@adm.scc.nl> From: "Marcel Moolenaar" To: "Josef Karthauser" , "John Baldwin" Cc: "Jeroen Ruigrok van der Werven" , , References: <002301bf69df$bd24eb00$0301a8c0@adm.scc.nl> <200001290130.UAA42086@server.baldwin.cx> <20000130203936.A74352@florence.pavilion.net> Subject: Re: More world breakage Date: Mon, 31 Jan 2000 10:52:56 +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.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > only. In -stable, and in -current before the end of December the > following tools: ls, rm, chflags, find, xinstall and mtree used > a common set of routines to manipulate file flags. [snip] > tool. At the beginnig of January, because of the proliferation of > utilities using these functions, I moved them to libutil in -current. [snip] > modes (setmode/getmode). This was what I did last week, renaming > flags_to_string to getflags, and string_to_flags to setflags. I [also moved to libc -- snip] > It may be argued that we should back out _both_ commits and resurrect > bin/ls/stat_flags.c. Would this gain us anything? Yes and no. The commits had a reason. Backing them out completely would only result in a second series of equivalent commits. It seems that install(1) is the only problem child. We can revert install(1) to have it's own set of functions and leave the rest as is. After installworld has been completed, install(1) can be changed back to use the libc versions. Comments? marcel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 2:29:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 596B914C34 for ; Mon, 31 Jan 2000 02:29:22 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 109FC2DC0A; Mon, 31 Jan 2000 11:28:55 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 401B47811; Mon, 31 Jan 2000 11:28:57 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 3478E10E10; Mon, 31 Jan 2000 11:28:57 +0100 (CET) Date: Mon, 31 Jan 2000 11:28:57 +0100 (CET) From: Andrzej Bialecki To: John Polstra Cc: dervish@ikhala.tcimet.net, current@freebsd.org Subject: Re: make installworld broken??? In-Reply-To: <200001301913.LAA35839@vashon.polstra.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 30 Jan 2000, John Polstra wrote: > > > It's source-dir is called "xinstall" btw. > > Why is the source called "xinstall"? > > To avoid colliding with the standard make target "install". If we > had utilities named "all", "depend", and "clean" we'd have to do the > same thing for them. Mhmmm... Isn't this something that .PHONY target is supposed to handle? Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 3: 3:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id CF5AD14EA7 for ; Mon, 31 Jan 2000 03:03:26 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id LAA04089; Mon, 31 Jan 2000 11:00:01 GMT (envelope-from n_hibma@webweaving.org) Date: Mon, 31 Jan 2000 11:00:01 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: FreeBSD CURRENT Mailing List , USB BSD list Subject: patches for USB Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As many things are still being tested, especially wrt OHCI controllers (support for them is fairly non-functional at the moment), I'll be updating a set of patches available from http://www.etla.net/~n_hibma/usb/USB-patch-CURRENT The patch is not for the faint of heart. It contains a snapshot of what I am doing at the moment, and, allthough I do my best to make things work, I'm pretty sure it will bomb your system. The list of things that are patched in there: CHANGELOG 20000131 - Test bug-fix for handling of the done queue - handling of error queues where the transfer consists of more than one TD (OHCI_TD_HANDLED) - Better handling of the done queue when the TD that was in tailp is added to the done queue. In that case we simply skip it and proceed with the rest of the queue instead of dropping the whole queue. - Updated umass driver ** Be warned: While using it /bin/login all of a sudden coredumped ** and other things in the kernel went wrong mysteriously (vm ** errors, etc.). - Fix for the handling of suspend (patch has been posted on usb-bsd) - Fix for deallocation of resources when attach fails (both OHCI and UHCI). Please note that discussions on USB are held in usb-bsd and anyone interested is encouraged to subscribe to that mailing list at www.egroups.com. It is also available through the web interface http://www.egroups.com/. Cheers. Nick P.S.: The patch is not mentioned on the web page because the site is out of date. I'll be updating the site tomorrow or the day after. -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 3: 6:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns.cvzoom.net (ns.cvzoom.net [208.226.154.2]) by hub.freebsd.org (Postfix) with SMTP id 6C06014E53 for ; Mon, 31 Jan 2000 03:06:39 -0800 (PST) (envelope-from dmmiller@cvzoom.net) Received: (qmail 17573 invoked from network); 31 Jan 2000 11:06:38 -0000 Received: from lcm97.cvzoom.net (208.230.69.97) by ns.cvzoom.net with SMTP; 31 Jan 2000 11:06:38 -0000 Date: Mon, 31 Jan 2000 06:06:09 -0500 (EST) From: Donn Miller To: current@freebsd.org Subject: "conflicts" keyword gone? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I noticed that the "conflicts" keyword was eliminated from the kernel config file syntax. Do we just eliminate this keyword, or is there another keyword that we should use in its place? Sorry if I missed this... - Donn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 4:21: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from webweaving.org (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id 0C32F14DA2 for ; Mon, 31 Jan 2000 04:20:54 -0800 (PST) (envelope-from n_hibma@webweaving.org) Received: from localhost (localhost [127.0.0.1]) by webweaving.org (8.9.3/8.9.3) with ESMTP id MAA04320; Mon, 31 Jan 2000 12:02:50 GMT (envelope-from n_hibma@webweaving.org) Date: Mon, 31 Jan 2000 12:02:50 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: USB BSD list Cc: FreeBSD CURRENT Mailing List Subject: for testing - suspend fix for UHCI controllers Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When committing the patch to get suspend to work I managed to forget to commit the parts for pci/[ou]hci_pci.c. The patch is given below. It should make your devices suspend. It is included in the big patchset as well. This is against CURRENT (== 4.0-RC) Thanks in advance. Nick Index: sys/pci/uhci_pci.c =================================================================== RCS file: /home/ncvs/src/sys/pci/uhci_pci.c,v retrieving revision 1.21 diff -w -u -r1.21 uhci_pci.c --- uhci_pci.c 2000/01/26 10:52:27 1.21 +++ uhci_pci.c 2000/01/30 15:15:57 @@ -93,8 +93,13 @@ static int uhci_pci_suspend(device_t self) { + uhci_softc_t *sc = device_get_softc(self); + int err; - bus_generic_suspend(self); + err = bus_generic_suspend(self); + if (err) + return err; + uhci_power(PWR_SUSPEND, sc); return 0; } @@ -102,11 +107,9 @@ static int uhci_pci_resume(device_t self) { -#if 0 uhci_softc_t *sc = device_get_softc(self); - uhci_reset(sc); -#endif + uhci_power(PWR_RESUME, sc); bus_generic_resume(self); return 0; -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 4:29:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.utexas.edu (wb1-a.mail.utexas.edu [128.83.126.134]) by hub.freebsd.org (Postfix) with SMTP id D986B14F5C for ; Mon, 31 Jan 2000 04:29:56 -0800 (PST) (envelope-from rkw@dataplex.net) Received: (qmail 28870 invoked by uid 0); 31 Jan 2000 12:29:55 -0000 Received: from dial-50-7.ots.utexas.edu (HELO localhost.localdomain) (128.83.113.55) by umbs-smtp-1 with SMTP; 31 Jan 2000 12:29:55 -0000 From: Richard Wackerbarth To: Andrzej Bialecki Subject: Re: make installworld broken??? Date: Mon, 31 Jan 2000 06:24:22 -0600 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain References: In-Reply-To: Cc: current@FreeBSD.ORG MIME-Version: 1.0 Message-Id: <00013106294500.00823@localhost.localdomain> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, you wrote: > On Sun, 30 Jan 2000, John Polstra wrote: > > > > > It's source-dir is called "xinstall" btw. > > > Why is the source called "xinstall"? > > > > To avoid colliding with the standard make target "install". If we > > had utilities named "all", "depend", and "clean" we'd have to do the > > same thing for them. > > Mhmmm... Isn't this something that .PHONY target is supposed to handle? How does that help? The problem is namespace pollution. Consider cd /usr/src/usr.bin make install Does this mean cd /usr/src/usr.bin/install make all or .for d in ${SUBDIRS} (cd /usr/src/usr.bin/${d}; make install) .endfor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 4:49:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 6C0AE14E5A for ; Mon, 31 Jan 2000 04:48:13 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id OAA02759; Mon, 31 Jan 2000 14:46:50 +0200 (EET) (envelope-from ru) Date: Mon, 31 Jan 2000 14:46:50 +0200 From: Ruslan Ermilov To: Donn Miller Cc: current@FreeBSD.ORG Subject: Re: "conflicts" keyword gone? Message-ID: <20000131144650.B1038@relay.ucb.crimea.ua> Mail-Followup-To: Donn Miller , current@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: ; from Donn Miller on Mon, Jan 31, 2000 at 06:06:09AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 31, 2000 at 06:06:09AM -0500, Donn Miller wrote: > I noticed that the "conflicts" keyword was eliminated from the kernel > config file syntax. Do we just eliminate this keyword, or is there > another keyword that we should use in its place? Sorry if I missed > this... > > - Donn > : peter 2000/01/29 10:07:08 PST : : Modified files: : sys/i386/conf GENERIC LINT : sys/alpha/conf GENERIC : sys/pc98/conf GENERIC98 : Log: : Remove 'conflicts' token - it has been effectively doing absolutely : nothing for quite some time. The only thing that cared was userconfig, : but it was for one invisible device so we never saw it's effects. : : Revision Changes Path : 1.239 +2 -2 src/sys/i386/conf/GENERIC : 1.742 +2 -2 src/sys/i386/conf/LINT : 1.68 +2 -2 src/sys/alpha/conf/GENERIC : 1.126 +2 -2 src/sys/pc98/conf/GENERIC98 -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 5:54:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 9CB101502D for ; Mon, 31 Jan 2000 05:54:17 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id PAA19374; Mon, 31 Jan 2000 15:54:00 +0200 (EET) (envelope-from ru) Date: Mon, 31 Jan 2000 15:54:00 +0200 From: Ruslan Ermilov To: current@FreeBSD.org Subject: HEADS UP: GNU grep 2.4d Message-ID: <20000131155400.A16502@relay.ucb.crimea.ua> Mail-Followup-To: current@FreeBSD.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Under a big pressure from the FreeBSD community, GNU grep maintainers released grep-2.4d, which has a new option -I, a short equivalent to --binary-files='without-match'. Grep 2.4d is now in the source tree (Approved by: jkh). This, I hope, will finally close this can of worms ;=) Enjoy, -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 6: 8:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 2F7E415083 for ; Mon, 31 Jan 2000 06:07:18 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id CEF341CD7; Mon, 31 Jan 2000 22:07:15 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrzej Bialecki Cc: current@freebsd.org Subject: Re: make installworld broken??? In-Reply-To: Message from Andrzej Bialecki of "Mon, 31 Jan 2000 11:28:57 +0100." Date: Mon, 31 Jan 2000 22:07:15 +0800 From: Peter Wemm Message-Id: <20000131140715.CEF341CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Andrzej Bialecki wrote: > On Sun, 30 Jan 2000, John Polstra wrote: > > > > > It's source-dir is called "xinstall" btw. > > > Why is the source called "xinstall"? > > > > To avoid colliding with the standard make target "install". If we > > had utilities named "all", "depend", and "clean" we'd have to do the > > same thing for them. > > Mhmmm... Isn't this something that .PHONY target is supposed to handle? No. Consider: PROG= install all: ${PROG} ${PROG}: ${OBJS} cc -o ${PROG} ${OBJS} install: ${INSTALL} .... ${PROG} ${BINDIR} .... and with ${PROG} expanded out: all: install install: ${OBJS} cc -o install ${OBJS} install: ${INSTALL} .... install ${BINDIR} .... Spot the problem.. Does the target "install" mean "build the binary" or "install the binary"? src/usr.bin/xinstall could probably have been named src/usr.bin/install, but PROG has to be xinstall regardless. I guess they kept the two as xinstall for consistancy and in case there were other gotcha's like this. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 6:51:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id 750D414C15 for ; Mon, 31 Jan 2000 06:51:16 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id GAA93543; Mon, 31 Jan 2000 06:50:23 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001311450.GAA93543@gndrsh.dnsmgr.net> Subject: Re: make installworld broken??? In-Reply-To: <20000131140715.CEF341CD7@overcee.netplex.com.au> from Peter Wemm at "Jan 31, 2000 10:07:15 pm" To: peter@netplex.com.au (Peter Wemm) Date: Mon, 31 Jan 2000 06:50:23 -0800 (PST) Cc: abial@webgiro.com (Andrzej Bialecki), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Good analysis deleted... > src/usr.bin/xinstall could probably have been named src/usr.bin/install, > but PROG has to be xinstall regardless. I guess they kept the two as > xinstall for consistancy and in case there were other gotcha's like this. But you forgot what happens if you have a ``file'' named install: cd /tmp mkdir install make install Now you know the real reason the directory is called ``xinstall''. -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 8:23:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 0A5CD14CC0 for ; Mon, 31 Jan 2000 08:23:24 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 4CA241CD7; Tue, 1 Feb 2000 00:23:18 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: "Rodney W. Grimes" Cc: abial@webgiro.com (Andrzej Bialecki), current@FreeBSD.ORG Subject: Re: make installworld broken??? In-Reply-To: Message from "Rodney W. Grimes" of "Mon, 31 Jan 2000 06:50:23 PST." <200001311450.GAA93543@gndrsh.dnsmgr.net> Date: Tue, 01 Feb 2000 00:23:18 +0800 From: Peter Wemm Message-Id: <20000131162318.4CA241CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Rodney W. Grimes" wrote: > Good analysis deleted... > > > src/usr.bin/xinstall could probably have been named src/usr.bin/install, > > but PROG has to be xinstall regardless. I guess they kept the two as > > xinstall for consistancy and in case there were other gotcha's like this. > > But you forgot what happens if you have a ``file'' named install: > > cd /tmp > mkdir install > make install > > Now you know the real reason the directory is called ``xinstall''. Ahh yes, of course. 'cd src/usr.bin; make install' would fail. :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 8:24:35 2000 Delivered-To: freebsd-current@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 C8A3914CB6 for ; Mon, 31 Jan 2000 08:24:30 -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 IAA14740 for ; Mon, 31 Jan 2000 08:24:30 -0800 Received: from passer.osg.gov.bc.ca(142.32.110.29) via SMTP by point.osg.gov.bc.ca, id smtpda14734; Mon Jan 31 08:24:13 2000 Received: (from uucp@localhost) by passer.osg.gov.bc.ca (8.9.3/8.9.1) id IAA18692 for ; Mon, 31 Jan 2000 08:24:13 -0800 (PST) Received: from cwsys9.cwsent.com(10.2.2.1), claiming to be "cwsys.cwsent.com" via SMTP by passer9.cwsent.com, id smtpdl18678; Mon Jan 31 08:23:56 2000 Received: (from uucp@localhost) by cwsys.cwsent.com (8.9.3/8.9.1) id IAA01532 for ; Mon, 31 Jan 2000 08:23:56 -0800 (PST) Message-Id: <200001311623.IAA01532@cwsys.cwsent.com> Received: from localhost.cwsent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwsent.com, id smtpddL1523; Mon Jan 31 08:23:31 2000 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: freebsd-current@freebsd.org Subject: IP-Filter w/FreeBSD-current Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Jan 2000 08:23:31 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG With the impending release of FreeBSD-4.0, is anyone on this list using IP-Filter on FreeBSD-current? I'm planning to install -current w/IP-Filter on a testbed and would like to know of there are any gotchas or if it even runs on FreeBSD-current. 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 "COBOL IS A WASTE OF CARDS." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 9:55:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from Brigada-A.Ethereal.RU (Brigada-A.ethereal.ru [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 1CEED14CA7 for ; Mon, 31 Jan 2000 09:55:48 -0800 (PST) (envelope-from nms@Brigada-A.Ethereal.RU) Received: by Brigada-A.Ethereal.RU (Postfix, from userid 1002) id DBCA81F1; Mon, 31 Jan 2000 20:55:33 +0300 (MSK) Received: from Brigada-A.Ethereal.RU (localhost [127.0.0.1]) by Brigada-A.Ethereal.RU (Postfix) with ESMTP id BDECB1D8 for ; Mon, 31 Jan 2000 20:55:33 +0300 (MSK) To: freebsd-current@freebsd.org Subject: kldloaded driver not called at load time From: Nikolai Saoukh Date: Mon, 31 Jan 2000 20:55:28 +0300 Message-Id: <20000131175533.DBCA81F1@Brigada-A.Ethereal.RU> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am trying to make kldloadable driver. But none of functions are called when I kldload it. Is this a bug or I am missing something essential? Sources, dmesg, config and makefile (for module) are at http://ethereal.ru/~nms/TR/tk.tar (~40Kb) P.S. I am chasing for IBM Token Ring Adapter (unknown0:). Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 10: 2:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from argon.blackdawn.com (deepspace9.dcds.edu [207.231.151.2]) by hub.freebsd.org (Postfix) with ESMTP id 976CB14FB9; Mon, 31 Jan 2000 10:02:31 -0800 (PST) (envelope-from will@blackdawn.com) Received: by argon.blackdawn.com (Postfix, from userid 1000) id 5B74919CF; Mon, 31 Jan 2000 13:02:29 -0500 (EST) Date: Mon, 31 Jan 2000 13:02:29 -0500 From: Will Andrews To: ru@FreeBSD.org Cc: FreeBSD Current Subject: Re: HEADS UP: GNU grep 2.4d Message-ID: <20000131130229.E431@argon.blackdawn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 31, 2000 at 03:54:00PM +0200, Ruslan Ermilov wrote: > Under a big pressure from the FreeBSD community, GNU grep > maintainers released grep-2.4d, which has a new option -I, > a short equivalent to --binary-files='without-match'. Is this also equivalent to the old grep's -a option? I mean OLD grep, from like 6 months ago? grep -a normally ignored binary files completely, back then. -- 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-current" in the body of the message From owner-freebsd-current Mon Jan 31 10:29:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 584A514D5A for ; Mon, 31 Jan 2000 10:29:02 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id UAA85511; Mon, 31 Jan 2000 20:28:30 +0200 (EET) (envelope-from ru) Date: Mon, 31 Jan 2000 20:28:30 +0200 From: Ruslan Ermilov To: Will Andrews Cc: FreeBSD Current Subject: Re: HEADS UP: GNU grep 2.4d Message-ID: <20000131202830.A82563@relay.ucb.crimea.ua> Mail-Followup-To: Will Andrews , FreeBSD Current References: <20000131130229.E431@argon.blackdawn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <20000131130229.E431@argon.blackdawn.com>; from Will Andrews on Mon, Jan 31, 2000 at 01:02:29PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Jan 31, 2000 at 01:02:29PM -0500, Will Andrews wrote: > On Mon, Jan 31, 2000 at 03:54:00PM +0200, Ruslan Ermilov wrote: > > Under a big pressure from the FreeBSD community, GNU grep > > maintainers released grep-2.4d, which has a new option -I, > > a short equivalent to --binary-files='without-match'. > > Is this also equivalent to the old grep's -a option? I mean OLD grep, from > like 6 months ago? > Yes, that's why all this fuss have taken place ;=) > grep -a normally ignored binary files completely, back then. > It was a local FreeBSD feature; now it is part of the official GNU grep. -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 10:36:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from gndrsh.dnsmgr.net (GndRsh.dnsmgr.net [198.145.92.4]) by hub.freebsd.org (Postfix) with ESMTP id BDD6D14F92 for ; Mon, 31 Jan 2000 10:36:48 -0800 (PST) (envelope-from freebsd@gndrsh.dnsmgr.net) Received: (from freebsd@localhost) by gndrsh.dnsmgr.net (8.9.3/8.9.3) id KAA93874; Mon, 31 Jan 2000 10:36:34 -0800 (PST) (envelope-from freebsd) From: "Rodney W. Grimes" Message-Id: <200001311836.KAA93874@gndrsh.dnsmgr.net> Subject: Re: make installworld broken??? In-Reply-To: <20000131162318.4CA241CD7@overcee.netplex.com.au> from Peter Wemm at "Feb 1, 2000 00:23:18 am" To: peter@netplex.com.au (Peter Wemm) Date: Mon, 31 Jan 2000 10:36:33 -0800 (PST) Cc: abial@webgiro.com (Andrzej Bialecki), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Rodney W. Grimes" wrote: > > Good analysis deleted... > > > > > src/usr.bin/xinstall could probably have been named src/usr.bin/install, > > > but PROG has to be xinstall regardless. I guess they kept the two as > > > xinstall for consistancy and in case there were other gotcha's like this. > > > > But you forgot what happens if you have a ``file'' named install: > > > > cd /tmp > > mkdir install > > make install > > > > Now you know the real reason the directory is called ``xinstall''. > > Ahh yes, of course. 'cd src/usr.bin; make install' would fail. :-) Actually it use to silently do the wrong thing... nothing at all that is :-) It doesn't anymore since the .mk system has a special internal target that deals with the fact that src/usr.bin is simply a directory that has to be iterated over: Orbit.hpc1.com:root{101}# cd /usr/src/usr.bin Orbit.hpc1.com:root{102}# mkdir install Orbit.hpc1.com:root{103}# make install ===> apply install -c -s -o root -g wheel -m 555 apply /usr/bin install -c -o root -g wheel -m 444 apply.1.gz /usr/share/man/man1 ===> at install -c -s -o root -g wheel -m 4555 at /usr/bin ... -- Rod Grimes - KD7CAX @ CN85sl - (RWG25) rgrimes@gndrsh.dnsmgr.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 11:42:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 2DDD414EDE for ; Mon, 31 Jan 2000 11:42:40 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id OAA10834; Mon, 31 Jan 2000 14:42:34 -0500 (EST) Date: Mon, 31 Jan 2000 14:42:34 -0500 (EST) From: "Matthew N. Dodd" To: Nikolai Saoukh Cc: freebsd-current@FreeBSD.ORG Subject: Re: kldloaded driver not called at load time In-Reply-To: <20000131175533.DBCA81F1@Brigada-A.Ethereal.RU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Nikolai Saoukh wrote: > I am trying to make kldloadable driver. But none of functions are > called when I kldload it. Is this a bug or I am missing something > essential? You're missing something essential. The return values for the DEVICE_PROBE method should be 0 or negative for priority, or positive to indicate an error. if_tok.c:tok_probe() returns ENXIO which is in the return value you use for if_tok_isa.c:tok_isa_probe(). You should take a good look at /sys/dev/{ex,ep} for an example of how to accommodate PnP probes. -- | 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-current" in the body of the message From owner-freebsd-current Mon Jan 31 11:57:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from news.IAEhv.nl (news.IAE.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id 356C614C3E for ; Mon, 31 Jan 2000 11:57:21 -0800 (PST) (envelope-from Arjan.deVet@adv.iae.nl) Received: (from uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id UAA25188 for current@freebsd.org; Mon, 31 Jan 2000 20:57:18 +0100 (MET) Received: by adv.iae.nl (Postfix, from userid 100) id 1588B22C7; Mon, 31 Jan 2000 20:57:00 +0100 (CET) To: current@freebsd.org Subject: Re: IP-Filter w/FreeBSD-current In-Reply-To: <200001311623.IAA01532@cwsys.cwsent.com> Organization: Cc: Message-Id: <20000131195700.1588B22C7@adv.iae.nl> Date: Mon, 31 Jan 2000 20:57:00 +0100 (CET) From: Arjan.deVet@adv.iae.nl (Arjan de Vet) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <200001311623.IAA01532@cwsys.cwsent.com> you write: >With the impending release of FreeBSD-4.0, is anyone on this list using >IP-Filter on FreeBSD-current? I'm planning to install -current Yep, I'm using it as a stateful packet filtering firewall for my cable modem connection. >w/IP-Filter on a testbed and would like to know of there are any >gotchas or if it even runs on FreeBSD-current. No serious problems so far. The only thing I discovered a few days ago is that when I dialin to the company network I have to unload and reload the filter rules to get ppp over the tun0 device working. Before starting /usr/sbin/ppp I do a ifconfig xl0 down to disable the cable modem interface completely. Anybody any idea where I can start to debug this weird problem? Arjan -- Arjan de Vet, Eindhoven, The Netherlands URL: http://www.iae.nl/users/devet/ for PGP key: finger devet@iae.nl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 11:58:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from xena.cs.waikato.ac.nz (xena.cs.waikato.ac.nz [130.217.241.20]) by hub.freebsd.org (Postfix) with ESMTP id 355A814C07 for ; Mon, 31 Jan 2000 11:58:47 -0800 (PST) (envelope-from joerg@lucy.cs.waikato.ac.nz) Received: from lucy.cs.waikato.ac.nz (joerg@lucy.cs.waikato.ac.nz [130.217.241.12]) by xena.cs.waikato.ac.nz (8.9.3/8.9.3) with ESMTP id IAA22086; Tue, 1 Feb 2000 08:58:39 +1300 (NZDT) Received: (from joerg@localhost) by lucy.cs.waikato.ac.nz (8.9.3/8.9.0) id IAA15945; Tue, 1 Feb 2000 08:58:35 +1300 (NZDT) Date: Tue, 1 Feb 2000 08:58:35 +1300 From: Joerg Micheel To: Greg Lehey Cc: TrouBle , Warner Losh , Andy Farkas , current@freebsd.org, joerg@cs.waikato.ac.nz Subject: Re: PAIN Message-ID: <20000201085835.K5288@cs.waikato.ac.nz> References: <200001300049.RAA10279@harmony.village.org> <38938E12.92EF9ABE@netquick.net> <20000130141245.C55643@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20000130141245.C55643@freebie.lemis.com>; from Greg Lehey on Sun, Jan 30, 2000 at 02:12:45PM +1030 Organization: SCMS, The University of Waikato, Hamilton, New Zealand Project: WAND - Waikato Applied Network Dynamics, DAG Operating-System: ... drained by Solaris 7 SPARC Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, Jan 30, 2000 at 02:12:45PM +1030, Greg Lehey wrote: > On Saturday, 29 January 2000 at 20:04:18 -0500, TrouBle wrote: > > Just imagine, too bad its not an 8086 or a 286 prolly take a month or so..... > > > > > > Warner Losh wrote: > > > >> In message Andy Farkas writes: > >> : This was a 'buildworld' of 3.4-stable, on 486DX2-66 with 32MB RAM, and > >> : both src and obj on the same local disk (softupdates enabled): > >> > >> I'm doing this over NFS and only have 12MB of RAM. > >> > >> : Script done on Thu Jan 20 16:22:31 2000 > >> : Script started on Thu Jan 20 01:01:00 2000 > >> > >> 15:21:31. Hmmm, no wonder things have been taking a while... > >> > >> The crypto file that's building now has been going for about 15 > >> minutes now... > >> > >> I think that I'll get my whole week at this rate. > > I did a make world on my PDP-11 yesterday. It took less than a day. > But that's 2.11BSD. That is hard- or software hardware ? Joerg -- Joerg B. Micheel Email: Waikato Applied Network Dynamics Phone: +64 7 8384794 The University of Waikato, CompScience Fax: +64 7 8384155 Private Bag 3105 Pager: +64 868 38222 Hamilton, New Zealand Plan: TINE and the DAG's To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 12:20:51 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 758) id 0456115140; Mon, 31 Jan 2000 12:20:49 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id EBB461CD6E2; Mon, 31 Jan 2000 12:20:49 -0800 (PST) (envelope-from kris@hub.freebsd.org) Date: Mon, 31 Jan 2000 12:20:49 -0800 (PST) From: Kris Kennaway To: Greg Childers Cc: KATO Takenori , current@freebsd.org Subject: Re: identcpu.c change causes panic - not identcpu.c? In-Reply-To: <4.2.0.58.20000131003612.00951ad0@pop.uky.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Greg Childers wrote: > A panic also occurred on my Pentium (P54C) 66MHz, but backing identcpu.c > to 1.79 didn't stop the panic. Here is the panic info, copied by hand. (I > hope there are no typos!) Well, I rebuilt a kernel with 1.80 of identcpu.c and it booted fine this time, so it looks like you can ignore my previous report. My best guess is that something in my kernel was out of sync with itself (I built multiple times to try and get the ipfw6 error to go away, perhaps it didn't recompile an object file when it should have). Sorry for the false alarm, Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 12:22:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id CD26914C07 for ; Mon, 31 Jan 2000 12:22:36 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.com (pC19F5478.dip0.t-ipconnect.de [193.159.84.120]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id VAA31297 for ; Mon, 31 Jan 2000 21:22:05 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 5675AAB92 for ; Mon, 31 Jan 2000 21:22:36 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id VAA02997 for freebsd-current@FreeBSD.ORG; Mon, 31 Jan 2000 21:23:06 +0100 (CET) (envelope-from alex) Date: Mon, 31 Jan 2000 21:23:05 +0100 From: Alexander Langer To: freebsd-current@FreeBSD.ORG Subject: Re: ata: Mount root failure: 6 Message-ID: <20000131212305.A2761@cichlids.cichlids.com> Mail-Followup-To: freebsd-current@FreeBSD.ORG References: <19991217181226.A83674@cichlids.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991217181226.A83674@cichlids.com>; from alex@cichlids.com on Fri, Dec 17, 1999 at 06:12:26PM +0100 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG For the archive of this ml: Some of the commits over the time since I got this error solved the problem silently. I'm now using ata this machine w/o any problem. On another machine that had problems with DMA with the old wd drivers UDMA33 now works ok, too. Nice. Thanks! Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 12:24:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from blackhelicopters.org (geburah.blackhelicopters.org [209.69.178.18]) by hub.freebsd.org (Postfix) with ESMTP id 7E36614D8A; Mon, 31 Jan 2000 12:24:13 -0800 (PST) (envelope-from mwlucas@blackhelicopters.org) Received: (from mwlucas@localhost) by blackhelicopters.org (8.9.3/8.9.3) id PAA24942; Mon, 31 Jan 2000 15:23:38 -0500 (EST) (envelope-from mwlucas) From: Michael Lucas Message-Id: <200001312023.PAA24942@blackhelicopters.org> Subject: NO_NAMED (patch attached) To: current@freebsd.org, stable@freebsd.org Date: Mon, 31 Jan 2000 15:23:38 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Well, the corporate firewall doesn't allow send-pr, so I'm trying this the noisy way. Sorry. :( We have a no_named flag in /usr/src/usr.sbin/Makefile, right by no_sendmail. A recent discussion on -security shows that at least a couple people have a use for this. Therefore, submitted for your approval, as per the Handbook: *** make.conf~ Mon Jan 24 13:55:29 2000 --- make.conf Mon Jan 31 15:25:49 2000 *************** *** 28,33 **** --- 28,36 ---- # To avoid building sendmail #NO_SENDMAIL= true # + # To avoid building named and related tools + #NO_BIND= true + # # To have 'obj' symlinks created in your source directory # (they aren't needed/necessary) #OBJLINK= yes This is against -stable, about a week old. Sorry, don't have -current on my laptop... I'm not a real hacker. ==ml (Wow, my first patch. Trivial, yet I find myself heady with success. ;) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 12:24:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from Brigada-A.Ethereal.RU (Brigada-A.ethereal.ru [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 2EECA150F3 for ; Mon, 31 Jan 2000 12:24:23 -0800 (PST) (envelope-from nms@Brigada-A.Ethereal.RU) Received: by Brigada-A.Ethereal.RU (Postfix, from userid 1002) id 66CFC1F1; Mon, 31 Jan 2000 23:23:35 +0300 (MSK) Received: from Brigada-A.Ethereal.RU (localhost [127.0.0.1]) by Brigada-A.Ethereal.RU (Postfix) with ESMTP id 4E5E21D8; Mon, 31 Jan 2000 23:23:35 +0300 (MSK) From: Nikolai Saoukh To: "Matthew N. Dodd" Cc: freebsd-current@FreeBSD.ORG Subject: Re: kldloaded driver not called at load time In-Reply-To: Your message of "Mon, 31 Jan 2000 14:42:34 EST." Date: Mon, 31 Jan 2000 23:23:29 +0300 Message-Id: <20000131202335.66CFC1F1@Brigada-A.Ethereal.RU> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I am trying to make kldloadable driver. But none of functions are > > called when I kldload it. Is this a bug or I am missing something > > essential? > > You're missing something essential. > > The return values for the DEVICE_PROBE method should be 0 or negative for > priority, or positive to indicate an error. THE PROBLEM is that tok_isa_probe is not called at all, when driver kldloaded. Return value is irrelevant for this case. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 12:37: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 6C914150F0 for ; Mon, 31 Jan 2000 12:36:57 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA11509; Mon, 31 Jan 2000 15:36:50 -0500 (EST) Date: Mon, 31 Jan 2000 15:36:49 -0500 (EST) From: "Matthew N. Dodd" To: Nikolai Saoukh Cc: freebsd-current@FreeBSD.ORG Subject: Re: kldloaded driver not called at load time In-Reply-To: <20000131202335.66CFC1F1@Brigada-A.Ethereal.RU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Nikolai Saoukh wrote: > THE PROBLEM is that tok_isa_probe is not called at all, > when driver kldloaded. Return value is irrelevant for this case. Yea, I see what could be the problem. I'll get back to you. -- | 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-current" in the body of the message From owner-freebsd-current Mon Jan 31 12:44: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 33E7914CF6 for ; Mon, 31 Jan 2000 12:43:56 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id PAA11603; Mon, 31 Jan 2000 15:43:45 -0500 (EST) Date: Mon, 31 Jan 2000 15:43:45 -0500 (EST) From: "Matthew N. Dodd" To: Nikolai Saoukh Cc: freebsd-current@FreeBSD.ORG Subject: Re: kldloaded driver not called at load time In-Reply-To: <20000131202335.66CFC1F1@Brigada-A.Ethereal.RU> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-285129607-949351425=:479" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-285129607-949351425=:479 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 31 Jan 2000, Nikolai Saoukh wrote: > THE PROBLEM is that tok_isa_probe is not called at all, > when driver kldloaded. Return value is irrelevant for this case. Try the attached patch. (cd /sys/isa && patch < isa_common.c.patch) -- | 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 | --0-285129607-949351425=:479 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="isa_common.c.patch" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="isa_common.c.patch" SW5kZXg6IGlzYV9jb21tb24uYw0KPT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQ0K UkNTIGZpbGU6IC9jdnMvc3JjL3N5cy9pc2EvaXNhX2NvbW1vbi5jLHYNCnJl dHJpZXZpbmcgcmV2aXNpb24gMS4xNQ0KZGlmZiAtdSAtcjEuMTUgaXNhX2Nv bW1vbi5jDQotLS0gaXNhX2NvbW1vbi5jCTIwMDAvMDEvMTggMDI6MTU6MDUJ MS4xNQ0KKysrIGlzYV9jb21tb24uYwkyMDAwLzAxLzMxIDIwOjQyOjAzDQpA QCAtNzgzLDggKzc4Myw3IEBADQogc3RhdGljIHZvaWQNCiBpc2FfZHJpdmVy X2FkZGVkKGRldmljZV90IGRldiwgZHJpdmVyX3QgKmRyaXZlcikNCiB7DQot CWRldmljZV90ICpjaGlsZHJlbjsNCi0JaW50IG5jaGlsZHJlbiwgaTsNCisJ ZGV2aWNlX3QgY2hpbGQ7DQogDQogCS8qDQogCSAqIERvbid0IGRvIGFueXRo aW5nIGlmIGRyaXZlcnMgYXJlIGR5bmFtaWNhbGx5DQpAQCAtNzk2LDExICs3 OTUsMTAgQEANCiAJCXJldHVybjsNCiANCiAJREVWSUNFX0lERU5USUZZKGRy aXZlciwgZGV2KTsNCi0JaWYgKGRldmljZV9nZXRfY2hpbGRyZW4oZGV2LCAm Y2hpbGRyZW4sICZuY2hpbGRyZW4pKQ0KLQkJcmV0dXJuOw0KIA0KLQlmb3Ig KGkgPSAwOyBpIDwgbmNoaWxkcmVuOyBpKyspIHsNCi0JCWRldmljZV90IGNo aWxkID0gY2hpbGRyZW5baV07DQorCWZvciAoY2hpbGQgPSBUQUlMUV9GSVJT VCgmZGV2LT5jaGlsZHJlbik7DQorCSAgICAgY2hpbGQ7DQorCSAgICAgY2hp bGQgPSBUQUlMUV9ORVhUKGNoaWxkLCBsaW5rKSkgew0KIAkJc3RydWN0IGlz YV9kZXZpY2UgKmlkZXYgPSBERVZUT0lTQShjaGlsZCk7DQogCQlzdHJ1Y3Qg cmVzb3VyY2VfbGlzdCAqcmwgPSAmaWRldi0+aWRfcmVzb3VyY2VzOw0KIAkJ c3RydWN0IHJlc291cmNlX2xpc3RfZW50cnkgKnJsZTsNCkBAIC04MzEsOCAr ODI5LDYgQEANCiAJCQl9DQogCQl9DQogCX0NCi0NCi0JZnJlZShjaGlsZHJl biwgTV9URU1QKTsNCiB9DQogDQogc3RhdGljIGludA0K --0-285129607-949351425=:479-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 13:26:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (21-106.012.popsite.net [216.126.164.106]) by hub.freebsd.org (Postfix) with ESMTP id 59AE014A11 for ; Mon, 31 Jan 2000 13:26:55 -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 NAA01860; Mon, 31 Jan 2000 13:36:05 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200001312136.NAA01860@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nikolai Saoukh Cc: "Matthew N. Dodd" , freebsd-current@FreeBSD.ORG Subject: Re: kldloaded driver not called at load time In-reply-to: Your message of "Mon, 31 Jan 2000 23:23:29 +0300." <20000131202335.66CFC1F1@Brigada-A.Ethereal.RU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 31 Jan 2000 13:36:05 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > I am trying to make kldloadable driver. But none of functions are > > > called when I kldload it. Is this a bug or I am missing something > > > essential? > > > > You're missing something essential. > > > > The return values for the DEVICE_PROBE method should be 0 or negative for > > priority, or positive to indicate an error. > > THE PROBLEM is that tok_isa_probe is not called at all, > when driver kldloaded. Return value is irrelevant for this case. This is because the unknown driver is never revoked once it owns your device. It's a(nother) bug in the ISA bus code. 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-current" in the body of the message From owner-freebsd-current Mon Jan 31 14:22:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 9F69D14DAF; Mon, 31 Jan 2000 14:22:50 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id RAA12838; Mon, 31 Jan 2000 17:22:49 -0500 (EST) Date: Mon, 31 Jan 2000 17:22:49 -0500 (EST) From: "Matthew N. Dodd" To: Mike Smith Cc: Nikolai Saoukh , freebsd-current@FreeBSD.ORG Subject: Re: kldloaded driver not called at load time In-Reply-To: <200001312136.NAA01860@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Mike Smith wrote: > This is because the unknown driver is never revoked once it owns your > device. It's a(nother) bug in the ISA bus code. 8( Looking at the code in sys/kern/subr_bus.c I'm not sure how any drivers are revoked by a higher priority match. This is probably desirable given the nature of most drivers and one of the reasons for letting BUS_PROBE_NOMATCH announce your 'unknown' hardware. If a driver is attached and providing interfaces to the system (network, scsi, what have you.) then loading a higher priority driver shouldn't cause that device to detach as it would potentially cause the system to become confused. I never liked the unknown driver. I vote we kill it and let isa_probe_nomatch() deal with things. (I'll have to write isa_probe_nomatch() but I don't see that as a problem.) Nikolai, your easy fix is to comment out the relevent module declaration for the 'unknown' driver in isa_common.c. -- | 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-current" in the body of the message From owner-freebsd-current Mon Jan 31 15: 6:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from finch-post-10.mail.demon.net (finch-post-10.mail.demon.net [194.217.242.38]) by hub.freebsd.org (Postfix) with ESMTP id 72F3314E57; Mon, 31 Jan 2000 15:06:43 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by finch-post-10.mail.demon.net with esmtp (Exim 2.12 #1) id 12FPu1-000H0o-0A; Mon, 31 Jan 2000 23:06:37 +0000 Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA10836; Mon, 31 Jan 2000 23:10:16 GMT (envelope-from dfr@nlsystems.com) Date: Mon, 31 Jan 2000 23:10:16 +0000 (GMT) From: Doug Rabson To: "Matthew N. Dodd" Cc: Mike Smith , Nikolai Saoukh , freebsd-current@freebsd.org Subject: Re: kldloaded driver not called at load time In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Matthew N. Dodd wrote: > On Mon, 31 Jan 2000, Mike Smith wrote: > > This is because the unknown driver is never revoked once it owns your > > device. It's a(nother) bug in the ISA bus code. 8( > > Looking at the code in sys/kern/subr_bus.c I'm not sure how any drivers > are revoked by a higher priority match. > > This is probably desirable given the nature of most drivers and one of the > reasons for letting BUS_PROBE_NOMATCH announce your 'unknown' hardware. > > If a driver is attached and providing interfaces to the system (network, > scsi, what have you.) then loading a higher priority driver shouldn't > cause that device to detach as it would potentially cause the system to > become confused. > > I never liked the unknown driver. I vote we kill it and let > isa_probe_nomatch() deal with things. (I'll have to write > isa_probe_nomatch() but I don't see that as a problem.) > > Nikolai, your easy fix is to comment out the relevent module declaration > for the 'unknown' driver in isa_common.c. This is probably the right workaround for now. The unknown driver does serve a purpose. It indirectly allows resources associated with the device to be allocated so that other PnP devices are not allocated on top. On reviewing the code, this seems to happen (in isa_probe_children) whether or not the preceding call to device_probe_and_attach() succeeded so removing the unknown driver would mean that resources are allocated for the un-attached device which is likely to cause trouble. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 15: 6:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from Brigada-A.Ethereal.RU (Brigada-A.ethereal.ru [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id 3F5D914EAB; Mon, 31 Jan 2000 15:06:54 -0800 (PST) (envelope-from nms@Brigada-A.Ethereal.RU) Received: by Brigada-A.Ethereal.RU (Postfix, from userid 1002) id 97D2E1EB; Tue, 1 Feb 2000 02:06:41 +0300 (MSK) Received: from Brigada-A.Ethereal.RU (localhost [127.0.0.1]) by Brigada-A.Ethereal.RU (Postfix) with ESMTP id 56B811D7; Tue, 1 Feb 2000 02:06:41 +0300 (MSK) From: Nikolai Saoukh To: "Matthew N. Dodd" Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: kldloaded driver not called at load time In-Reply-To: Your message of "Mon, 31 Jan 2000 17:22:49 EST." Date: Tue, 01 Feb 2000 02:06:35 +0300 Message-Id: <20000131230641.97D2E1EB@Brigada-A.Ethereal.RU> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Nikolai, your easy fix is to comment out the relevent module declaration > for the 'unknown' driver in isa_common.c. Yes, this fix does the job, BUT Comments for 'unknown' driver says '... for unknown pnp cards ...'. Will my driver be called on computer _without_ any pnp card? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 15: 8:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-31.mail.demon.net (anchor-post-31.mail.demon.net [194.217.242.89]) by hub.freebsd.org (Postfix) with ESMTP id 7B23714F21 for ; Mon, 31 Jan 2000 15:08:02 -0800 (PST) (envelope-from dfr@nlsystems.com) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-31.mail.demon.net with esmtp (Exim 2.12 #1) id 12FPvI-0006tK-0V; Mon, 31 Jan 2000 23:07:57 +0000 Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id XAA10840; Mon, 31 Jan 2000 23:11:31 GMT (envelope-from dfr@nlsystems.com) Date: Mon, 31 Jan 2000 23:11:31 +0000 (GMT) From: Doug Rabson To: "Matthew N. Dodd" Cc: Nikolai Saoukh , freebsd-current@freebsd.org Subject: Re: kldloaded driver not called at load time In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Matthew N. Dodd wrote: > On Mon, 31 Jan 2000, Nikolai Saoukh wrote: > > THE PROBLEM is that tok_isa_probe is not called at all, > > when driver kldloaded. Return value is irrelevant for this case. > > Try the attached patch. > > (cd /sys/isa && patch < isa_common.c.patch) This patch doesn't (shouldn't) compile since it uses private information from bus_private.h. I hope you are not including bus_private.h anywhere in your code - its strictly off limits to driver code, even bus drivers. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 15:15:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 302B214EAF; Mon, 31 Jan 2000 15:15:31 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id SAA13594; Mon, 31 Jan 2000 18:15:27 -0500 (EST) Date: Mon, 31 Jan 2000 18:15:27 -0500 (EST) From: "Matthew N. Dodd" To: Nikolai Saoukh Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: kldloaded driver not called at load time In-Reply-To: <20000131230641.97D2E1EB@Brigada-A.Ethereal.RU> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 1 Feb 2000, Nikolai Saoukh wrote: > Comments for 'unknown' driver says '... for unknown pnp cards ...'. > Will my driver be called on computer _without_ any pnp card? Does your driver have an identify method for non-PnP cards? -- | 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-current" in the body of the message From owner-freebsd-current Mon Jan 31 15:16:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 23D231500E for ; Mon, 31 Jan 2000 15:16:23 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id SAA13602; Mon, 31 Jan 2000 18:16:11 -0500 (EST) Date: Mon, 31 Jan 2000 18:16:10 -0500 (EST) From: "Matthew N. Dodd" To: Doug Rabson Cc: Nikolai Saoukh , freebsd-current@freebsd.org Subject: Re: kldloaded driver not called at load time In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 31 Jan 2000, Doug Rabson wrote: > This patch doesn't (shouldn't) compile since it uses private > information from bus_private.h. I hope you are not including > bus_private.h anywhere in your code - its strictly off limits to > driver code, even bus drivers. Yea, I figured that out. My patch didn't change the function of the code anyway. Not sure what I was thinking. -- | 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-current" in the body of the message From owner-freebsd-current Mon Jan 31 15:23:19 2000 Delivered-To: freebsd-current@freebsd.org Received: from Brigada-A.Ethereal.RU (Brigada-A.ethereal.ru [195.230.65.30]) by hub.freebsd.org (Postfix) with ESMTP id B40B814C36; Mon, 31 Jan 2000 15:23:16 -0800 (PST) (envelope-from nms@Brigada-A.Ethereal.RU) Received: by Brigada-A.Ethereal.RU (Postfix, from userid 1002) id 59F111D8; Tue, 1 Feb 2000 02:23:07 +0300 (MSK) Received: from Brigada-A.Ethereal.RU (localhost [127.0.0.1]) by Brigada-A.Ethereal.RU (Postfix) with ESMTP id 3C1111D7; Tue, 1 Feb 2000 02:23:07 +0300 (MSK) From: Nikolai Saoukh To: "Matthew N. Dodd" Cc: Mike Smith , freebsd-current@FreeBSD.ORG Subject: Re: kldloaded driver not called at load time In-Reply-To: Your message of "Mon, 31 Jan 2000 18:15:27 EST." Date: Tue, 01 Feb 2000 02:23:02 +0300 Message-Id: <20000131232307.59F111D8@Brigada-A.Ethereal.RU> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > On Tue, 1 Feb 2000, Nikolai Saoukh wrote: > > Comments for 'unknown' driver says '... for unknown pnp cards ...'. > > Will my driver be called on computer _without_ any pnp card? > > Does your driver have an identify method for non-PnP cards? This particular card can be "downgraded" to previous model (Auto 16/4) in strict legacy mode (no pnp at all). Or with some pnp. Well, my question was not about my case, rather general one. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Mon Jan 31 15:50:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id 4F4A015251 for ; Mon, 31 Jan 2000 15:48:22 -0800 (PST) (envelope-from ab@cage.tse-online.de) Received: (qmail 27432 invoked by uid 1000); 31 Jan 2000 23:48:48 -0000 Date: Tue, 1 Feb 2000 00:48:48 +0100 From: Andreas Braukmann To: current@freebsd.org Subject: sym0 v1.4 vs. SMP Message-ID: <20000201004848.B27262@cage.tse-online.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="azLHFNyN32YCQGCU" X-Mailer: Mutt 1.0i Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Hi there, ... I have an SMP-box (dual PPro, Natoma, mptable output attached) running -current (with src/sys/dev/sym/sym_hipd.c,v 1.4 2000/01/08 19:58:17) from around 2000/01/22. The machine was running a 'ca. mid 1999' -current/SMP happily for the last few months. I did the upgrade (fresh install) to give the mylex drivers a shot. And because of the non-booting mlx-driver I left my symbios logic dual channel (symbios logic '876 chip) hostadaptor in the machine and included the sym-device in the kernel configuration. (I run the sym-driver on all our other symbios logic hostadaptors) Today I switched from GENERIC (UP) to a more specific configuration and to SMP (again). I attached the kernel configuration file for the uni-processor case, to get the 'hang' one just has to throw over the SMP-switch. The machine hangs right after this message (boot -v). SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff An aequivalent uni-processor kernel (with sym0, just without SMP) runs flawlessly. I attached the dmesg-outputs of a successfully booted SMP-kernel (ncr0 instead sym0) and and successfully booted UP-kernel (with sym0). If anybody needs further information, ... just ask. Any hints? Thanks, Andreas -- Me no internet, only janitor, me just wax floors. --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="mptable.out" =============================================================================== MPTable, version 2.0.15 ------------------------------------------------------------------------------- MP Floating Pointer Structure: location: BIOS physical address: 0x000f0e70 signature: '_MP_' length: 16 bytes version: 1.1 checksum: 0x02 mode: Virtual Wire ------------------------------------------------------------------------------- MP Config Table Header: physical address: 0x000f0e84 signature: 'PCMP' base table length: 308 version: 1.1 checksum: 0x2f OEM ID: 'OEM00000' Product ID: 'PROD00000000' OEM table pointer: 0x00000000 OEM table size: 0 entry count: 30 local APIC address: 0xfee00000 extended table length: 0 extended table checksum: 0 ------------------------------------------------------------------------------- MP Config Base Table Entries: -- Processors: APIC ID Version State Family Model Step Flags 0 0x11 BSP, usable 6 1 9 0xfbff 1 0x11 AP, usable 6 1 9 0xfbff -- Bus: Bus ID Type 0 PCI 1 ISA -- I/O APICs: APIC ID Version State Address 2 0x11 usable 0xfec00000 -- I/O Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 1 0 2 0 INT conforms conforms 1 1 2 1 INT conforms conforms 1 0 2 2 INT conforms conforms 1 3 2 3 INT conforms conforms 1 4 2 4 INT conforms conforms 1 5 2 5 INT conforms conforms 1 6 2 6 INT conforms conforms 1 7 2 7 INT conforms conforms 1 8 2 8 INT conforms conforms 1 9 2 9 INT conforms conforms 1 10 2 10 INT conforms conforms 1 11 2 11 INT conforms conforms 1 12 2 12 INT conforms conforms 1 13 2 13 INT conforms conforms 1 14 2 14 INT conforms conforms 1 15 2 15 INT active-lo level 0 8:A 2 16 INT active-lo level 0 9:A 2 17 INT active-lo level 0 10:A 2 18 INT active-lo level 0 11:A 2 19 INT active-lo level 0 7:A 2 19 INT active-lo level 0 12:A 2 16 SMI conforms conforms 1 0 2 23 -- Local Ints: Type Polarity Trigger Bus ID IRQ APIC ID PIN# ExtINT conforms conforms 0 0:A 255 0 NMI conforms conforms 0 0:A 255 1 ------------------------------------------------------------------------------- # SMP kernel config file options: # Required: options SMP # Symmetric MultiProcessor Kernel options APIC_IO # Symmetric (APIC) I/O # Optional (built-in defaults will work in most cases): #options NCPU=2 # number of CPUs #options NBUS=2 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs =============================================================================== --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename=TSEGENERIC # stripped down GENERIC machine i386 #cpu I386_CPU #cpu I486_CPU #cpu I586_CPU cpu I686_CPU ident TSEGENERIC maxusers 64 #makeoptions DEBUG=-g #Build kernel with gdb(1) debug symbols # Size of the kernel message buffer. Should be N * pagesize. options MSGBUF_SIZE=81920 # options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MD_ROOT #MD is a potential root device options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options CD9660 #ISO 9660 Filesystem options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=15000 #Be pessimistic about Joe SCSI device options UCONSOLE #Allow users to grab the console options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options KTRACE #ktrace(1) syscall trace support options SYSVSHM #SYSV-style shared memory options SYSVMSG #SYSV-style message queues options SYSVSEM #SYSV-style semaphores options P1003_1B #Posix P1003_1B real-time extentions options _KPOSIX_PRIORITY_SCHEDULING options _KPOSIX_VERSION=199309L # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs device isa0 #device eisa0 device pci0 # Floppy drives device fdc0 at isa? port IO_FD1 irq 6 drq 2 device fd0 at fdc0 drive 0 # ATA and ATAPI devices #device ata0 at isa? port IO_WD1 irq 14 #device ata1 at isa? port IO_WD2 irq 15 #device ata2 #device atadisk0 # ATA disk drives #device atapicd0 # ATAPI CDROM drives #device atapifd0 # ATAPI floppy drives #device atapist0 # ATAPI tape drives #options ATA_STATIC_ID #Static device numbering #options ATA_ENABLE_ATAPI_DMA #Enable DMA on ATAPI devices # SCSI Controllers # A single entry for any of these controllers (ahb, ahc, amd, ncr, etc...) is # sufficient for any number of installed devices. #device ahc0 # AHA2940 and onboard AIC7xxx devices #device ncr0 # NCR/Symbios Logic device sym0 # NCR/Symbios Logic (newer chipsets) # SCSI peripherals # Only one of each of these is needed, they are dynamically allocated. device scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD device pass0 # Passthrough device (direct SCSI access) # RAID controllers #device amr0 # AMI MegaRAID device mlx0 # Mylex DAC960 family # atkbdc0 controls both the keyboard and the PS/2 mouse device atkbdc0 at isa? port IO_KBD device atkbd0 at atkbdc? irq 1 device psm0 at atkbdc? irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? # Floating point support - do not disable. device npx0 at nexus? port IO_NPX irq 13 # Power management support (see LINT for more options) #device apm0 at nexus? disable flags 0x20 # Advanced Power Management # Serial (COM) ports device sio0 at isa? port IO_COM1 flags 0x10 irq 4 device sio1 at isa? port IO_COM2 irq 3 #device sio2 at isa? disable port IO_COM3 irq 5 #device sio3 at isa? disable port IO_COM4 irq 9 # Parallel port device ppc0 at isa? port? irq 7 device ppbus0 # Parallel port bus (required) device lpt0 at ppbus? # Printer device plip0 at ppbus? # TCP/IP over parallel device ppi0 at ppbus? # Parallel port interface device #device vpo0 at ppbus? # Requires scbus and da0 # PCI Ethernet NICs. #device de0 # DEC/Intel DC21x4x (``Tulip'') device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) #device tx0 # SMC 9432TX (83c170 ``EPIC'') #device vx0 # 3Com 3c590, 3c595 (``Vortex'') #device wx0 # Intel Gigabit Ethernet Card (``Wiseman'') # PCI Ethernet NICs that use the common MII bus controller code. #device miibus0 # MII bus support #device dc0 # DEC/Intel 21143 and various workalikes #device rl0 # RealTek 8129/8139 #device sf0 # Adaptec AIC-6915 (``Starfire'') #device sis0 # Silicon Integrated Systems SiS 900/SiS 7016 #device ste0 # Sundance ST201 (D-Link DFE-550TX) #device tl0 # Texas Instruments ThunderLAN #device vr0 # VIA Rhine, Rhine II #device wb0 # Winbond W89C840F #device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # Pseudo devices - the number indicates how many units to allocated. pseudo-device loop # Network loopback pseudo-device ether # Ethernet support pseudo-device tun 16 # Packet tunnel. pseudo-device pty 256 # Pseudo-ttys (telnet etc) pseudo-device md # Memory "disks" # The `bpf' pseudo-device enables the Berkeley Packet Filter. # Be aware of the administrative consequences of enabling this! pseudo-device bpf #Berkeley packet filter --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.smp" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Feb 1 00:57:03 CET 2000 toor@paert.tse-online.de:/iron/bsd/src/sys/compile/TSEGENERIC-SMP Calibrating clock(s) ... TSC clock: 200554379 Hz, i8254 clock: 1193776 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method CPU: Pentium Pro (200.46-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002fa000 - 0x07febfff, 131014656 bytes (31986 pages) config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di le0 No such device: le0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> di ex0 No such device: ex0 Invalid command or syntax. Type `?' for help. config> di ed0 No such device: ed0 Invalid command or syntax. Type `?' for help. config> di cs0 No such device: cs0 Invalid command or syntax. Type `?' for help. config> di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config> di aic0 No such device: aic0 Invalid command or syntax. Type `?' for help. config> di aha0 No such device: aha0 Invalid command or syntax. Type `?' for help. config> di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config> q avail memory = 127057920 (124080K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 SMP: CPU0 apic_initialize(): lint0: 0x00000700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 bios32: Found BIOS32 Service Directory header at 0xc00faf30 bios32: Entry = 0xfb330 (c00fb330) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb360 pnpbios: Found PnP BIOS data at 0xc00fc050 pnpbios: Entry = f0000:c078 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel" at 0xc02de000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc02de0a8. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present SMP: CPU0 bsp_apic_configure(): lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000010 SVR: 0x000001ff pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) pcib0: on motherboard found-> vendor=0x8086, dev=0x1237, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000f000, size 4 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x8086, dev=0x1229, revid=0x04 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 1, range 32, base e1908000, size 12 map[14]: type 1, range 32, base 00009100, size 5 map[18]: type 1, range 32, base e1800000, size 20 found-> vendor=0x8086, dev=0x0960, revid=0x05 class=06-04-00, hdrtype=0x01, mfdev=1 subordinatebus=1 secondarybus=1 Freeing (NOT implemented) redirected PCI irq 10. found-> vendor=0x1069, dev=0x0010, revid=0x05 class=01-04-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=17 map[10]: type 1, range 32, base e1904000, size 13 Freeing (NOT implemented) redirected PCI irq 9. found-> vendor=0x1000, dev=0x000f, revid=0x14 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=18 map[10]: type 1, range 32, base 00009200, size 8 map[14]: type 1, range 32, base e1909000, size 8 map[18]: type 1, range 32, base e190a000, size 12 found-> vendor=0x1000, dev=0x000f, revid=0x14 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=5 map[10]: type 1, range 32, base 00009300, size 8 map[14]: type 1, range 32, base e1906000, size 8 map[18]: type 1, range 32, base e1907000, size 12 Freeing (NOT implemented) redirected PCI irq 11. found-> vendor=0x102b, dev=0x051b, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=16 map[10]: type 1, range 32, base e0000000, size 24 map[14]: type 1, range 32, base e1900000, size 14 map[18]: type 1, range 32, base e1000000, size 23 pci0: on pcib0 isab0: at device 7.0 on pci0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: enabled Interrupt Routing: A: IRQ11, B: IRQ10, C: IRQ9, D: IRQ5 MB0: , MB1: isa0: on isab0 pci0: Intel PIIX3 ATA controller (vendor=0x8086, dev=0x7010) at 7.1 fxp0: port 0x9100-0x911f mem 0xe1800000-0xe18fffff,0xe1908000-0xe1908fff irq 16 at device 8.0 on pci0 fxp0: Ethernet address 00:a0:c9:9f:3b:e5 bpf: fxp0 attached pcib1: at device 9.0 on pci0 pci1: on pcib1 mlx0: mem 0xe1904000-0xe1905fff irq 17 at device 9.1 on pci0 mlx0: DAC960PTL1, 1 channel, firmware 4.07-0-29, 8MB RAM mlx0: Hardware ID 0x03020116 mlx0: Firmware ID 0x301d0704 mlx0: Configured/Actual channels 1/1 mlx0: Max Targets 16 mlx0: Max Tags 252 mlx0: Max System Drives 32 mlx0: Max Arms 8 mlx0: Max Spans 4 mlx0: DRAM/cache/flash/NVRAM size 8388608/6815744/524288/32768 mlx0: DRAM type 17 mlx0: Clock Speed 40ns mlx0: Hardware Speed 360ns mlx0: Max Commands 124 mlx0: Max SG Entries 33 mlx0: Max DP 504 mlx0: Max IOD 1024 mlx0: Max Comb 256 mlx0: Latency 12s mlx0: SCSI Timeout 6s mlx0: Min Free Lines 72 mlx0: Rate Constant 50 mlx0: MAXBLK 128 mlx0: Blocking Factor 1 sectors mlx0: Cache Line Size 16 blocks mlx0: SCSI Capability 40MHz, 16 bit mlx0: Firmware Build Number 0 mlx0: Fault Management Type 0 mlx0: Features 0 mlxd0: on mlx0 mlxd0: 10242MB (20975616 sectors) RAID 5 (online) Creating DISK mlxd0 mlxd1: on mlx0 mlxd1: 12288MB (25165824 sectors) RAID 5 (online) Creating DISK mlxd1 mlxd2: on mlx0 mlxd2: 4952MB (10141696 sectors) RAID 0 (online) Creating DISK mlxd2 ncr0: port 0x9200-0x92ff mem 0xe190a000-0xe190afff,0xe1909000-0xe19090ff irq 18 at device 10.0 on pci0 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM ncr1: port 0x9300-0x93ff mem 0xe1907000-0xe1907fff,0xe1906000-0xe19060ff irq 5 at device 10.1 on pci0 ncr1: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr1: single-ended, open drain IRQ driver, using on-chip SRAM vga-pci0: mem 0xe1000000-0xe17fffff,0xe1900000-0xe1903fff,0xe0000000-0xe0ffffff irq 16 at device 12.0 on pci0 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa 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 0a 03 c8 psm: status 0a 03 c8 psm: status 0a 03 c8 psm: status 10 00 64 psm: data c8 c2 50 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0-50, 3 buttons psm0: config:00000000, flags:00000000, packet size:3 psm0: syncmask:08, syncbits:08 vga0: at port 0x3b0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 60 4f 50 83 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 bpf: lp0 attached ppi0: on ppbus0 isa_probe_children: probing PnP devices SMP: enabled INTs: 1, 3, 4, 5, 6, 7, 12, 16, 17, 18, apic_imen: 0x00f8ef05 BIOS Geometries: 0:020efe3f 0..526=527 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 bpf: lo0 attached Waiting 15 seconds for SCSI devices to settle ncr0: restart (scsi reset). ncr1: restart (scsi reset). SMP: AP CPU #1 Launched! SMP: CPU1 apic_initialize(): lint0: 0x00010700 lint1: 0x00010400 TPR: 0x00000010 SVR: 0x000001ff (probe6:ncr0:0:6:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe6:ncr0:0:6:0): ILLEGAL REQUEST asc:24,0 (probe6:ncr0:0:6:0): Invalid field in CDB Creating DISK da0 Creating DISK cd0 pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number F3V95882 pass0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) pass1 at ncr0 bus 0 target 6 lun 0 pass1: Removable CD-ROM SCSI-2 device pass1: 10.000MB/s transfers (10.000MHz, offset 15) Mounting root from ufs:/dev/da0s1a (cd0:ncr0:0:6:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:ncr0:0:6:0): NOT READY asc:3a,0 (cd0:ncr0:0:6:0): Medium not present cd0 at ncr0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number F3V95882 da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da0s1: type 0xa5, start 63, end = 8466254, size 8466192 : OK start_init: trying /sbin/init mlxd2s1: type 0xa5, start 32, end = 10141695, size 10141664 : OK mlxd1s1: type 0xa5, start 32, end = 25165823, size 25165792 : OK mlxd0s1: type 0xa5, start 32, end = 20975615, size 20975584 : OK mlxd1s1: type 0xa5, start 32, end = 25165823, size 25165792 : OK mlxd0s1: type 0xa5, start 32, end = 20975615, size 20975584 : OK mlxd0s1: type 0xa5, start 32, end = 20975615, size 20975584 : OK mlxd0s1: type 0xa5, start 32, end = 20975615, size 20975584 : OK mlxd0s1: type 0xa5, start 32, end = 20975615, size 20975584 : OK mlxd1s1: type 0xa5, start 32, end = 25165823, size 25165792 : OK mlxd0s1: type 0xa5, start 32, end = 20975615, size 20975584 : OK --azLHFNyN32YCQGCU Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.up" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Tue Feb 1 00:55:46 CET 2000 toor@paert.tse-online.de:/iron/bsd/src/sys/compile/TSEGENERIC Calibrating clock(s) ... TSC clock: 200554308 Hz, i8254 clock: 1193776 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 200455432 Hz CPU: Pentium Pro (200.46-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping = 9 Features=0xfbff real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x002ed000 - 0x07febfff, 131067904 bytes (31999 pages) avail memory = 127111168 (124132K bytes) bios32: Found BIOS32 Service Directory header at 0xc00faf30 bios32: Entry = 0xfb330 (c00fb330) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xb360 pnpbios: Found PnP BIOS data at 0xc00fc050 pnpbios: Entry = f0000:c078 Rev = 1.0 Other BIOS signatures found: ACPI: 00000000 Preloaded elf kernel "kernel.up" at 0xc02d4000. Pentium Pro MTRR support enabled md0: Malloc disk Creating DISK md0 Math emulator present pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) npx0: on motherboard npx0: INT 16 interface pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=12378086) pcib0: on motherboard found-> vendor=0x8086, dev=0x1237, revid=0x02 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7000, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000f000, size 4 found-> vendor=0x8086, dev=0x1229, revid=0x04 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base e1908000, size 12 map[14]: type 1, range 32, base 00009100, size 5 map[18]: type 1, range 32, base e1800000, size 20 found-> vendor=0x8086, dev=0x0960, revid=0x05 class=06-04-00, hdrtype=0x01, mfdev=1 subordinatebus=1 secondarybus=1 found-> vendor=0x1069, dev=0x0010, revid=0x05 class=01-04-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[10]: type 1, range 32, base e1904000, size 13 found-> vendor=0x1000, dev=0x000f, revid=0x14 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[10]: type 1, range 32, base 00009200, size 8 map[14]: type 1, range 32, base e1909000, size 8 map[18]: type 1, range 32, base e190a000, size 12 found-> vendor=0x1000, dev=0x000f, revid=0x14 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=b, irq=5 map[10]: type 1, range 32, base 00009300, size 8 map[14]: type 1, range 32, base e1906000, size 8 map[18]: type 1, range 32, base e1907000, size 12 found-> vendor=0x102b, dev=0x051b, revid=0x00 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base e0000000, size 24 map[14]: type 1, range 32, base e1900000, size 14 map[18]: type 1, range 32, base e1000000, size 23 pci0: on pcib0 Correcting Natoma config for non-SMP Correcting Natoma config for non-SMP isab0: at device 7.0 on pci0 I/O Recovery Timing: 8-bit 1 clocks, 16-bit 1 clocks Extended BIOS: disabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: enabled Interrupt Routing: A: IRQ11, B: IRQ10, C: IRQ9, D: IRQ5 MB0: , MB1: isa0: on isab0 pci0: Intel PIIX3 ATA controller (vendor=0x8086, dev=0x7010) at 7.1 fxp0: port 0x9100-0x911f mem 0xe1800000-0xe18fffff,0xe1908000-0xe1908fff irq 11 at device 8.0 on pci0 fxp0: Ethernet address 00:a0:c9:9f:3b:e5 bpf: fxp0 attached pcib1: at device 9.0 on pci0 pci1: on pcib1 mlx0: mem 0xe1904000-0xe1905fff irq 10 at device 9.1 on pci0 mlx0: DAC960PTL1, 1 channel, firmware 4.07-0-29, 8MB RAM mlx0: Hardware ID 0x03020116 mlx0: Firmware ID 0x301d0704 mlx0: Configured/Actual channels 1/1 mlx0: Max Targets 16 mlx0: Max Tags 252 mlx0: Max System Drives 32 mlx0: Max Arms 8 mlx0: Max Spans 4 mlx0: DRAM/cache/flash/NVRAM size 8388608/6815744/524288/32768 mlx0: DRAM type 17 mlx0: Clock Speed 40ns mlx0: Hardware Speed 360ns mlx0: Max Commands 124 mlx0: Max SG Entries 33 mlx0: Max DP 504 mlx0: Max IOD 1024 mlx0: Max Comb 256 mlx0: Latency 12s mlx0: SCSI Timeout 6s mlx0: Min Free Lines 72 mlx0: Rate Constant 50 mlx0: MAXBLK 128 mlx0: Blocking Factor 1 sectors mlx0: Cache Line Size 16 blocks mlx0: SCSI Capability 40MHz, 16 bit mlx0: Firmware Build Number 0 mlx0: Fault Management Type 0 mlx0: Features 0 mlxd0: on mlx0 mlxd0: 10242MB (20975616 sectors) RAID 5 (online) Creating DISK mlxd0 mlxd1: on mlx0 mlxd1: 12288MB (25165824 sectors) RAID 5 (online) Creating DISK mlxd1 mlxd2: on mlx0 mlxd2: 4952MB (10141696 sectors) RAID 0 (online) Creating DISK mlxd2 sym0: <875> port 0x9200-0x92ff mem 0xe190a000-0xe190afff,0xe1909000-0xe19090ff irq 9 at device 10.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/4e/80/01/00/24 sym0: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/46/80/01/08/24 sym0: SCAN AT BOOT disabled for targets 1 2 3 4 5 8 9 10 11 12 13 14 15. sym0: Delay (GEN=11): 243 msec, 36577 KHz sym0: Delay (GEN=11): 263 msec, 33795 KHz sym0: Delay (GEN=11): 263 msec, 33795 KHz sym0: enabling clock multiplier sym0: Downloading SCSI SCRIPTS. sym1: <875> port 0x9300-0x93ff mem 0xe1907000-0xe1907fff,0xe1906000-0xe19060ff irq 5 at device 10.1 on pci0 sym1: chip clock is 40401KHz sym1: Symbios NVRAM, ID 7, Fast-20, SE, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: initial SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 00/00/00/00/00/00 sym1: final SCNTL3/DMODE/DCNTL/CTEST3/4/5 = (hex) 05/46/80/01/08/24 sym1: enabling clock multiplier sym1: Downloading SCSI SCRIPTS. vga-pci0: mem 0xe1000000-0xe17fffff,0xe1900000-0xe1903fff,0xe0000000-0xe0ffffff irq 11 at device 12.0 on pci0 Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 From owner-freebsd-current Mon Jan 31 16:47:44 2000 From owner-freebsd-current Wed Feb 16 7: 7:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 7E24137B57F for ; Wed, 16 Feb 2000 07:07:30 -0800 (PST) (envelope-from takehiro@coral.ocn.ne.jp) Received: from coral.ocn.ne.jp (coral.ocn.ne.jp [202.234.232.80]) by builder.freebsd.org (Postfix) with ESMTP id 94472132D9 for ; Wed, 16 Feb 2000 07:06:53 -0800 (PST) Received: from nomad.ocn.ad.jp (p24-dn09yokohamami.kanagawa.ocn.ne.jp [210.132.20.89]) by coral.ocn.ne.jp (8.9.1a/OCN) with SMTP id XAA09502; Wed, 16 Feb 2000 23:11:45 +0900 (JST) Date: Wed, 16 Feb 2000 23:11:45 +0900 (JST) Message-Id: <200002161411.XAA09502@coral.ocn.ne.jp> To: sobomax@altavista.net Cc: freebsd-current@FreeBSD.ORG, takehiro@coral.ocn.ne.jp Subject: Re: FreeBSD-current question re: binutils In-Reply-To: Your message of "Wed, 16 Feb 2000 09:33:52 +0200". <38AA52DF.A0A11FCC@altavista.net> From: takehiro@coral.ocn.ne.jp (Takehiro Suzuki) X-Mailer: mnews [version 1.22] 1999-12/19(Sun) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <38AA52DF.A0A11FCC@altavista.net> sobomax@altavista.net writes: >> As I pointed earlier I manually updating my cvs shapshot and packing it into >> binutils.tar.bz2, which obviously unpacks into work/binutils directory. Here some It seems so good.Is it in ports-current? Takehiro Suzuki takehiro@coral.ocn.ne.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 7:22:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 8E8AC37B580 for ; Wed, 16 Feb 2000 07:22:03 -0800 (PST) (envelope-from ilmar@ints.ru) Received: from ws-ilmar.ints.ru (ws-ilmar.ints.ru [194.67.173.16]) by builder.freebsd.org (Postfix) with ESMTP id D7DA2132DE for ; Wed, 16 Feb 2000 07:16:58 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by ws-ilmar.ints.ru (8.9.3/8.9.3) with ESMTP id RAA67719 for ; Wed, 16 Feb 2000 17:46:04 +0300 (MSK) Date: Wed, 16 Feb 2000 17:46:03 +0300 (MSK) From: "Ilmar S. Habibulin" To: freebsd-current@FreeBSD.ORG Subject: Re: gcc, eh_rtime_match In-Reply-To: <20000215224914.A9417@dragon.nuxi.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 15 Feb 2000, David O'Brien wrote: I know taht i have correct versions of freebsd, gcc and libstdc++. > > > What version of KDE libs do you have installed? > > current. ;-) 2.0 from 14 or 15 of february. > Hum... I'll have to pass to KDE clueful people on this point. It would be nice to found out the problem. kde list doesn't helped me much or maybe i don't understood them. > You might post to ports@freebsd.org and see if a KDE clueful person can > help you. i think that nobody is occupied with beta(or even alpha) vertion of kde. I hoped to hear something useful about eh_rtime_match() function and it's use. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 8:24:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 5F5C737B505; Wed, 16 Feb 2000 08:24:09 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by builder.freebsd.org (Postfix) with ESMTP id F40F7132DD; Wed, 16 Feb 2000 08:23:26 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id 094D91CD7; Thu, 17 Feb 2000 00:24:00 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: obrien@FreeBSD.ORG Cc: Sheldon Hearn , freebsd-current@FreeBSD.ORG Subject: Re: FTP_INTERNAL_LS In-Reply-To: Message from "David O'Brien" of "Wed, 16 Feb 2000 01:16:42 PST." <20000216011642.A10123@dragon.nuxi.com> Date: Thu, 17 Feb 2000 00:24:00 +0800 From: Peter Wemm Message-Id: <20000216162400.094D91CD7@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "David O'Brien" wrote: > On Wed, Feb 16, 2000 at 09:04:44AM +0200, Sheldon Hearn wrote: > > > What about making FTP_INTERNAL_LS the default for 4.0? > > > > I'm very much in favour of this, > > Agreed. Do you want to bug JKH, or should I? ;) You're 6 months late, this is already done: revision 1.26 date: 1999/08/26 00:45:34; author: peter; state: Exp; lines: +1 -3 unifdef -DINTERNAL_LS - it's too useful to be off by default. If anyone really dislikes this, we could add a switch to disable it at runtime and check in popen.c. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 8:26:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id C292837B505; Wed, 16 Feb 2000 08:26:47 -0800 (PST) (envelope-from sheldonh@axl.noc.iafrica.com) Received: from axl.noc.iafrica.com (axl.noc.iafrica.com [196.31.1.175]) by builder.freebsd.org (Postfix) with ESMTP id 27217132DD; Wed, 16 Feb 2000 08:26:09 -0800 (PST) Received: from sheldonh (helo=axl.noc.iafrica.com) by axl.noc.iafrica.com with local-esmtp (Exim 3.13 #1) id 12L7HR-0003Uc-00; Wed, 16 Feb 2000 18:26:21 +0200 From: Sheldon Hearn To: Peter Wemm Cc: obrien@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: FTP_INTERNAL_LS In-reply-to: Your message of "Thu, 17 Feb 2000 00:24:00 +0800." <20000216162400.094D91CD7@overcee.netplex.com.au> Date: Wed, 16 Feb 2000 18:26:21 +0200 Message-ID: <13429.950718381@axl.noc.iafrica.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000 00:24:00 +0800, Peter Wemm wrote: > You're 6 months late, this is already done: Hahaha! Suits me. I'm sure _someone_ will be unhappy that he can't offer an ftp service sans directory listings, but it certainly won't be me. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 9:18:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 6BE5337B50B for ; Wed, 16 Feb 2000 09:18:39 -0800 (PST) (envelope-from Joe.Jacobson@Halliburton.com) Received: from mail1.halnet.com (mail1.halliburton.com [32.97.163.253]) by builder.freebsd.org (Postfix) with ESMTP id 627A3132D9 for ; Wed, 16 Feb 2000 09:18:02 -0800 (PST) Received: from houconn001.halnet.com [34.226.128.1] by mail1.halnet.com with ESMTP (SMTPD32-5.05) id ABF219AD00E0; Wed, 16 Feb 2000 11:18:42 -0600 Received: by houconn001.halnet.com with Internet Mail Service (5.5.2448.0) id <1ZZJ4ZQY>; Wed, 16 Feb 2000 11:13:38 -0600 Message-ID: From: Joe Jacobson To: 'Thomas Dean' , current@FreeBSD.ORG Subject: RE: Problems with Recent PPP Changes Date: Wed, 16 Feb 2000 11:13:30 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ran into this quoting change problem too. It affects authname, authkey, and phone strings as well. Phone numbers with '*' sequences failed for me, as well my authname and authkey settings (which contained non-alphanumerics). Encasing these strings in "" worked for me. Since your ISP is asking for PAP, I would do the following: set login set authname "yourLoginName" set authkey "yourPassword" If the empty 'set login' fails to work for you, try set login "ABORT NO\\sCARRIER TIMEOUT 5 ogin:--ogin: \\U word: \\P" Maybe somebody can make this new qouting behavior more clear in an example in the sample ppp.conf installed in /etc? Just so other new users of 4.0 won't get bitten by the same thing. > -----Original Message----- > From: Thomas Dean [SMTP:tomdean@ix.netcom.com] > Sent: Wednesday, February 16, 2000 10:00 AM > To: current@FreeBSD.ORG > Subject: Re: Problems with Recent PPP Changes > > Thanks for the reply. > > > Date: Wed, 16 Feb 2000 01:16:25 -0700 > > From: Warner Losh > > > > In message <200002160421.UAA00933@ix.netcom.com> Thomas Dean writes: > > : What change to ppp did I miss? > > > > There were some quoting and comment recognition changes at one > > point... > > > > That is the problem. My ISP requires a '#' as a leading delimiter for > the login name. ppp determines the '#' is the start of a line-end > comment. From the log: > > Phase: bundle: Authenticate > Phase: deflink: his = PAP, mine = none > Phase: Pap Output: ******** > Warning: Sending empty PAP authname! > Phase: Pap Input: FAILURE (Invalid Login) > Phase: deflink: Disconnected! > Phase: deflink: lcp -> logout > > How do I handle the required leading '#' on the login name? Escaping > it doesn't work. > > tomdean > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 9:24:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id C4AEA37B54B; Wed, 16 Feb 2000 09:24:29 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by builder.freebsd.org (Postfix) with ESMTP id C0046132E0; Wed, 16 Feb 2000 09:23:53 -0800 (PST) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA25181; Wed, 16 Feb 2000 09:24:13 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Peter Wemm Cc: obrien@FreeBSD.ORG, Sheldon Hearn , freebsd-current@FreeBSD.ORG Subject: Re: FTP_INTERNAL_LS In-reply-to: Your message of "Thu, 17 Feb 2000 00:24:00 +0800." <20000216162400.094D91CD7@overcee.netplex.com.au> Date: Wed, 16 Feb 2000 09:24:13 -0800 Message-ID: <25178.950721853@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Haha, so much for that issue then. :) > "David O'Brien" wrote: > > On Wed, Feb 16, 2000 at 09:04:44AM +0200, Sheldon Hearn wrote: > > > > What about making FTP_INTERNAL_LS the default for 4.0? > > > > > > I'm very much in favour of this, > > > > Agreed. Do you want to bug JKH, or should I? ;) > > You're 6 months late, this is already done: > revision 1.26 > date: 1999/08/26 00:45:34; author: peter; state: Exp; lines: +1 -3 > unifdef -DINTERNAL_LS - it's too useful to be off by default. If anyone > really dislikes this, we could add a switch to disable it at runtime and > check in popen.c. > > Cheers, > -Peter > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 9:46:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 20B2737B50B for ; Wed, 16 Feb 2000 09:46:24 -0800 (PST) (envelope-from scrappy@hub.org) Received: from thelab.hub.org (nat197.96.mpoweredpc.net [142.177.197.96]) by builder.freebsd.org (Postfix) with ESMTP id A4B5C132D6 for ; Wed, 16 Feb 2000 09:45:41 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id NAA17226 for ; Wed, 16 Feb 2000 13:46:04 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 16 Feb 2000 13:46:04 -0400 (AST) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: Mounting Netware drive onto 4.0-CURRENT ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Can someone poitn me to a document that talks about setting this up? I remember seeing something pass by about 'ifconfig'ng a device for ipx and whatnot, but that was awhile ago ... Thanks ... 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-current" in the body of the message From owner-freebsd-current Wed Feb 16 9:57: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id D301037B50B for ; Wed, 16 Feb 2000 09:57:04 -0800 (PST) (envelope-from gerald@manhattanprojects.com) Received: from smtp.manhattanprojects.com (smtp.manhattanprojects.com [207.181.119.22]) by builder.freebsd.org (Postfix) with ESMTP id 6A69D132DD for ; Wed, 16 Feb 2000 09:56:27 -0800 (PST) Received: from manhattanprojects.com (xs.lab.glc.com [10.0.0.14]) by smtp.manhattanprojects.com (8.9.1/8.8.7) with ESMTP id MAA15687 for ; Wed, 16 Feb 2000 12:48:34 -0500 (EST) (envelope-from gerald@manhattanprojects.com) Message-ID: <38AAE4E4.98AD4C5D@manhattanprojects.com> Date: Wed, 16 Feb 2000 12:56:52 -0500 From: Gerald Abshez X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-current@FreeBSD.ORG Subject: Thinkpad won't boot ISO image Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've tried to boot the ISO image (RC2) on an IBM Thinkpad, type 2621. I get the keyboard probe, and then the >> boot prompt comes up. It doesn't appear to be able to see the loader, and can't boot a kernel. In a Desktop system the disc works all the way to the sysinstall menu. I'm not sure if this is a known issue with the thinkpads or with the ISO boot image, but I thought it might be worth letting people know. I managed to install -CURRENT before on this machine off of floppies and over FTP, so I don't believe it's an issue with the kernel or the hardware in general. Does anyone have any ideas? Gerald. -- This is your FreeBSD -- Where do YOU want to go tommorow? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 10: 6:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id D8AF237B50E for ; Wed, 16 Feb 2000 10:06:34 -0800 (PST) (envelope-from obrien@NUXI.com) Received: from relay.nuxi.com (nuxi.cs.ucdavis.edu [169.237.7.38]) by builder.freebsd.org (Postfix) with ESMTP id 7A933132D9 for ; Wed, 16 Feb 2000 10:05:58 -0800 (PST) Received: from dragon.nuxi.com (root@d60-025.leach.ucdavis.edu [169.237.60.25]) by relay.nuxi.com (8.9.3/8.9.3) with ESMTP id KAA36573; Wed, 16 Feb 2000 10:06:33 -0800 (PST) (envelope-from obrien@dragon.nuxi.com) Received: (from obrien@localhost) by dragon.nuxi.com (8.9.3/8.9.1) id KAA38848; Wed, 16 Feb 2000 10:06:30 -0800 (PST) (envelope-from obrien) Date: Wed, 16 Feb 2000 10:06:30 -0800 From: "David O'Brien" To: Peter Wemm Cc: Sheldon Hearn , freebsd-current@FreeBSD.ORG Subject: Re: FTP_INTERNAL_LS Message-ID: <20000216100630.A38813@dragon.nuxi.com> Reply-To: obrien@FreeBSD.ORG References: <20000216162400.094D91CD7@overcee.netplex.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000216162400.094D91CD7@overcee.netplex.com.au>; from peter@netplex.com.au on Thu, Feb 17, 2000 at 12:24:00AM +0800 X-Operating-System: FreeBSD 4.0-CURRENT Organization: The NUXI BSD group X-PGP-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Keyid: 34F9F9D5 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 17, 2000 at 12:24:00AM +0800, Peter Wemm wrote: > You're 6 months late, this is already done: > revision 1.26 > date: 1999/08/26 00:45:34; author: peter; state: Exp; lines: +1 -3 > unifdef -DINTERNAL_LS - it's too useful to be off by default. If anyone > really dislikes this, we could add a switch to disable it at runtime and > check in popen.c. You missed parts of ftpd.8 that needed changeing with this change. The manpage still clearly states that ~ftp/bin/ls needs to exist: ~ftp/bin Make this directory owned by ``root'' and unwritable by anyone (mode 555). The program ls(1) must be present to support the list command. This program should be mode 111. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 10:10:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 03DF337B50B for ; Wed, 16 Feb 2000 10:10:24 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by builder.freebsd.org (Postfix) with ESMTP id 3C578132E0 for ; Wed, 16 Feb 2000 10:09:05 -0800 (PST) Date: Wed, 16 Feb 2000 12:07:23 -0600 From: Dan Nelson To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: Mounting Netware drive onto 4.0-CURRENT ... Message-ID: <20000216120722.A30617@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from "The Hermit Hacker" on Wed Feb 16 13:46:04 GMT 2000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Feb 16), The Hermit Hacker said: > Can someone point me to a document that talks about setting this up? > I remember seeing something pass by about 'ifconfig'ng a device for > ipx and whatnot, but that was awhile ago ... in rc.conf: ifconfig_fxp0_ipx="ipx 0x87654321" ifconfig_lo0_ipx="ipx 0x12345678.1" ipxrouted_enable="YES" 87654321 is whatever your existing ETHERNET_II ipx network number is. 12345678 is your machines local network number; probably not needed except for machines running mars_new. That should be all you need. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 10:54:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id E777E37B53D for ; Wed, 16 Feb 2000 10:54:16 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by builder.freebsd.org (Postfix) with ESMTP id A5B09132E4 for ; Wed, 16 Feb 2000 10:53:39 -0800 (PST) Received: from cs.rpi.edu (loot.cs.rpi.edu [128.213.16.22]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id NAA52160; Wed, 16 Feb 2000 13:53:48 -0500 (EST) Message-Id: <200002161853.NAA52160@cs.rpi.edu> To: Gerald Abshez Cc: freebsd-current@FreeBSD.ORG, crossd@cs.rpi.edu Subject: Re: Thinkpad won't boot ISO image In-Reply-To: Message from Gerald Abshez of "Wed, 16 Feb 2000 12:56:52 EST." <38AAE4E4.98AD4C5D@manhattanprojects.com> Date: Wed, 16 Feb 2000 13:43:23 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a problem with the thinkpad BIOS that I have not had the time to be able to track down. It would *appear* to be that the BIOS does not do int 13 handling on boot cdroms, and the boot/loader makes much use of that for loading the kernel and drivers. I am, however, out of my league on this. Some feedback from the boot/loader team would be greatly appreciated in this. *hint* *hint* -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 12: 3:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 6101E37B578 for ; Wed, 16 Feb 2000 12:03:28 -0800 (PST) (envelope-from scrappy@hub.org) Received: from thelab.hub.org (nat197.96.mpoweredpc.net [142.177.197.96]) by builder.freebsd.org (Postfix) with ESMTP id 9C192132DD for ; Wed, 16 Feb 2000 12:02:46 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id QAA18075; Wed, 16 Feb 2000 16:01:14 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 16 Feb 2000 16:01:14 -0400 (AST) From: The Hermit Hacker To: Dan Nelson Cc: freebsd-current@FreeBSD.ORG Subject: Re: Mounting Netware drive onto 4.0-CURRENT ... In-Reply-To: <20000216120722.A30617@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Okay, now I'm getting somewhere, but where I don't know :( set the ifconfig, run IPXrouted, and netstat -nr tells me a bunch of stuff about IPX ... great, that appeasr to be up, but I get errors with ncplogin, so obviously I'm missing something (and wihtout the search of archives, this is the most embarressing and painful way of doing this *sigh*) ... athena# netstat -nr Routing tables Internet: Destination Gateway Flags Netif Expire default 131.162.136.1 UGSc xl0 127.0.0.1 127.0.0.1 UH lo0 131.162.136/21 link#1 UC xl0 => 131.162.136.1 8:0:2:17:32:c5 UHLW xl0 1200 131.162.136.69 0:a0:24:b2:26:e2 UHLW xl0 1197 131.162.138.223 0:0:c0:eb:c4:bf UHLW xl0 1042 192.168.254 link#3 UC vmnet1 => 192.168.254.2 0:50:56:d3:51:e4 UHLW vmnet1 942 IPX: Destination Gateway Flags Netif Expire 1.* 83a28800.c08a9aeb UG xl0 8126d01.* 83a28800.800021732c5 UG xl0 b53ccf9.* 83a28800.800021732c5 UG xl0 82428072.* 83a28800.800021732c5 UG xl0 83a2003c.* 83a28800.800021732c5 UG xl0 83a200ca.* 83a28800.508b7148d9 UG xl0 83a200cc.* 83a28800.2200c110aa45 UG xl0 83a20332.* 83a28800.2200c110aa9d UG xl0 83a20333.* 83a28800.800021732c5 UG xl0 83a20832.* 83a28800.2200c1108a0a UG xl0 83a28000.* 83a28800.800021732c5 UG xl0 83a28800.* 83a28800.104b696333 U xl0 83a29000.* 83a28800.800021732c5 UG xl0 83a29800.* 83a28800.800021732c5 UG xl0 83a2a000.* 83a28800.800021732c5 UG xl0 83a2a800.* 83a28800.800021732c5 UG xl0 83a2c800.* 83a28800.800021732c5 UG xl0 83a2c841.* 83a28800.800021732c5 UG xl0 83a2f000.* 83a28800.800021732c5 UG xl0 athena# ncplogin -S admin.acadiau.ca -U marc Warning: no cfg files found. ncplogin: can't find server ADMIN.ACADIAU.CA: syserr = No route to host athena# ncplogin -A admin.acadiau.ca ncplogin: no default connection found: syserr = Bad file descriptor athena# xl0: flags=8843 mtu 1500 inet 131.162.138.193 netmask 0xfffff800 broadcast 131.162.143.255 ipx 83a28800.104b696333 ether 00:10:4b:69:63:33 media: autoselect (10baseT/UTP) status: active I got the "ETHERNET_II ipx network number" from our Novell Network Admin ... IPX is enabled in the kernel ... else I imagine that IPXrouted wouldn't have worked ... How does one 'set a route to host' in IPX? :( Thanks... On Wed, 16 Feb 2000, Dan Nelson wrote: > In the last episode (Feb 16), The Hermit Hacker said: > > Can someone point me to a document that talks about setting this up? > > I remember seeing something pass by about 'ifconfig'ng a device for > > ipx and whatnot, but that was awhile ago ... > > in rc.conf: > > ifconfig_fxp0_ipx="ipx 0x87654321" > ifconfig_lo0_ipx="ipx 0x12345678.1" > ipxrouted_enable="YES" > > 87654321 is whatever your existing ETHERNET_II ipx network number is. > > 12345678 is your machines local network number; probably not needed > except for machines running mars_new. > > That should be all you need. > > -- > Dan Nelson > dnelson@emsphone.com > 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-current" in the body of the message From owner-freebsd-current Wed Feb 16 12: 7:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id F155737B551 for ; Wed, 16 Feb 2000 12:07:26 -0800 (PST) (envelope-from jas@flyingfox.com) Received: from biggusdiskus.flyingfox.com (parker-T1-2-gw.sf3d.best.net [209.157.165.30]) by builder.freebsd.org (Postfix) with ESMTP id 98350132D9 for ; Wed, 16 Feb 2000 12:06:47 -0800 (PST) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.8/8.8.5) id LAA13282 for freebsd-current@freebsd.org; Wed, 16 Feb 2000 11:54:57 -0800 (PST) Date: Wed, 16 Feb 2000 11:54:57 -0800 (PST) From: Jim Shankland Message-Id: <200002161954.LAA13282@biggusdiskus.flyingfox.com> To: freebsd-current@freebsd.org Subject: sysinstall of 20000214 snap hangs Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I just tried installing the 2/14 4.0 snap onto a Cyrix MediaGX-based box, and the sysinstall hung at the "probing devices" phase. Because the 3.4 sysinstall works just fine on this box, and because the last thing I see on the debug screen (ttyv1) is DEBUG: Found a disk device named ad0 I'm inclined to cast a suspicious eye toward Soren's new IDE driver :-). I realize the information I've provided so far is unlikely to be sufficient to diagnose, much less remedy, the problem; but I'm not not sure what to do next. I'm happy to work with anyone who'd like to take a closer look at this. Jim Shankland Decision Data/NLynx Systems, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 12:16:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id CD65E37B54F; Wed, 16 Feb 2000 12:16:32 -0800 (PST) (envelope-from mike@sentex.ca) Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by builder.freebsd.org (Postfix) with ESMTP id 86DD9132D6; Wed, 16 Feb 2000 12:15:49 -0800 (PST) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id PAA69877; Wed, 16 Feb 2000 15:16:20 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000216151400.00ff5e40@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Wed, 16 Feb 2000 15:14:00 -0500 To: current@freebsd.org From: Mike Tancsa Subject: Perc 2/SC problems (aka MegaRAID 466) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I have been trying to get a PERC 2 (aka MegaRAID 466) working with Current. The box worked fine with the 428, but seems to barf with only the controller swapped. newmail# dd if=/dev/zero of=/dev/ramrd0 bs=1k count=1 1+0 records in 1+0 records out 1024 bytes transferred in 0.000446 secs (2295546 bytes/sec) newmail# !fd fdisk amrd0 ******* Working on device /dev/ramrd0 ******* parameters extracted from in-core disklabel are: cylinders=2217 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=2217 heads=255 sectors/track=63 (16065 blks/cyl) fdisk: invalid fdisk partition table found Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 1, size 35616104 (17390 Meg), flag 80 (active) beg: cyl 0/ sector 2/ head 0; end: cyl 168/ sector 63/ head 254 newmail# disklabel -Brw amrd0 auto newmail# disklabel -e amrd0 disklabel: ioctl DIOCGDINFO: Invalid argument FreeBSD newmail.sentex.ca 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Feb 16 07:41:02 GMT 2000 mdtancsa@newmail.sentex.ca:/usr/src/sys/compile/newmail i386 newmail# dmesg | grep amr amr0: mem 0xe9000000-0xe93fffff irq 11 at device 12.1 on pci0 amr0: firmware 3.00 bios 1.36 32MB memory amrd0: on amr0 amrd0: 17396MB (35627008 sectors) RAID 5 (optimal) newmail# This is using the BIOS from Dell. Should I be trying the latest and greatest directly from AMI ? There is a warning from them however saying not to use the AMI version with OEM cards. Should I try it anyways ? ---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-current" in the body of the message From owner-freebsd-current Wed Feb 16 13:18:22 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 03AA837B54D for ; Wed, 16 Feb 2000 13:18:20 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id D4ACC132DD for ; Wed, 16 Feb 2000 13:17:36 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA54097; Wed, 16 Feb 2000 13:18:13 -0800 (PST) (envelope-from dillon) Date: Wed, 16 Feb 2000 13:18:13 -0800 (PST) From: Matthew Dillon Message-Id: <200002162118.NAA54097@apollo.backplane.com> To: current@FreeBSD.org Subject: Heads up, vm.max_proc_mmap sysctl added Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This deals with a mmap+fork bomb that can cause the kernel to eat all of KVM in vm_map_entry structures. The default limit should be set generously enough for people using the current FreeBSD threads incarnation (and isn't an issue w/ linux threads due to rfork resulting in scaling of the limit for the shared address space). Heads up in case a heavy threads programmer sees something I missed. -Matt Matthew Dillon :dillon 2000/02/16 13:11:37 PST : : Modified files: : sys/kern kern_malloc.c : sys/sys kernel.h : sys/vm vm_kern.h vm_map.c vm_mmap.c : lib/libc/sys mmap.2 : Log: : Fix null-pointer dereference crash when the system is intentionally : run out of KVM through a mmap()/fork() bomb that allocates hundreds : of thousands of vm_map_entry structures. : : Add panic to make null-pointer dereference crash a little more verbose. : : Add a new sysctl, vm.max_proc_mmap, which specifies the maximum number : of mmap()'d spaces (discrete vm_map_entry's in the process). The value : defaults to around 9000 for a 128MB machine. The test is scaled for the : number of processes sharing a vmspace (aka linux threads). Setting : the value to 0 disables the feature. : : PR: kern/16573 : Approved by: jkh : : Revision Changes Path : 1.64 +3 -2 src/sys/kern/kern_malloc.c : 1.62 +2 -1 src/sys/sys/kernel.h : 1.22 +2 -1 src/sys/vm/vm_kern.h : 1.186 +8 -2 src/sys/vm/vm_map.c : 1.107 +43 -5 src/sys/vm/vm_mmap.c : 1.20 +3 -2 src/lib/libc/sys/mmap.2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 13:39:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 007A337B54D for ; Wed, 16 Feb 2000 13:39:38 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by builder.freebsd.org (Postfix) with ESMTP id 21153132E7 for ; Wed, 16 Feb 2000 13:38:54 -0800 (PST) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id OAA56722; Wed, 16 Feb 2000 14:25:39 -0700 (MST) Date: Wed, 16 Feb 2000 14:25:39 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <200002162125.OAA56722@narnia.plutotech.com> To: David Gilbert Cc: current@FreeBSD.org Subject: Re: AIC card not recognised? X-Newsgroups: pluto.freebsd.current In-Reply-To: <14505.39674.245011.506206@trooper.velocet.net> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <14505.39674.245011.506206@trooper.velocet.net> you wrote: > I get the following: > > pci0: unknown card (vendor=0x9004, dev=0x5078) at 8.0 irq 11 Nothing has changed in this area for some time and the id for this card is in the table of supported devices. Do you get any additional information from a boot -v? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 13:40:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id EBE0737B54D for ; Wed, 16 Feb 2000 13:40:47 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by builder.freebsd.org (Postfix) with ESMTP id E75B1132E2 for ; Wed, 16 Feb 2000 13:40:09 -0800 (PST) Date: Wed, 16 Feb 2000 15:40:43 -0600 From: Dan Nelson To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: Mounting Netware drive onto 4.0-CURRENT ... Message-ID: <20000216154043.A42792@dan.emsphone.com> References: <20000216120722.A30617@dan.emsphone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from "The Hermit Hacker" on Wed Feb 16 16:01:14 GMT 2000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Feb 16), The Hermit Hacker said: > athena# ncplogin -S admin.acadiau.ca -U marc > Warning: no cfg files found. > ncplogin: can't find server ADMIN.ACADIAU.CA: syserr = No route to host > athena# ncplogin -A admin.acadiau.ca > ncplogin: no default connection found: syserr = Bad file descriptor > How does one 'set a route to host' in IPX? :( Hm. the "no route to host" means that it couldn't find "admin.acadiau.ca" as a netware server name. I believe that the NCP code is all bindery only right now, so giving an NDS object wouldn't work. See if "ncplist s" shows any servers, and try to log into one of those. -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 13:48:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id ECC6E37B851 for ; Wed, 16 Feb 2000 13:48:02 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Received: from fb01.eng00.mindspring.net (fb01.eng00.mindspring.net [207.69.229.19]) by builder.freebsd.org (Postfix) with ESMTP id 4EC03132E0 for ; Wed, 16 Feb 2000 13:47:22 -0800 (PST) Received: from ix.netcom.com (sil-wa16-40.ix.netcom.com [207.93.148.168]) by fb01.eng00.mindspring.net (8.9.3/8.8.5) with ESMTP id QAA30645; Wed, 16 Feb 2000 16:46:04 -0500 (EST) Received: (from tomdean@localhost) by ix.netcom.com (8.9.3/8.8.8) id NAA02484; Wed, 16 Feb 2000 13:46:30 -0800 (PST) (envelope-from tomdean@ix.netcom.com) Date: Wed, 16 Feb 2000 13:46:30 -0800 (PST) Message-Id: <200002162146.NAA02484@ix.netcom.com> X-Authentication-Warning: celebris.tddhome: tomdean set sender to tomdean@ix.netcom.com using -f From: Thomas Dean To: Joe.Jacobson@Halliburton.com Cc: current@FreeBSD.ORG In-reply-to: (message from Joe Jacobson on Wed, 16 Feb 2000 11:13:30 -0600) Subject: Re: Problems with Recent PPP Changes References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A very careful reading of the man page shows: Note that two parsers will examine these escape sequences, so in order to have the `chat parser' see the escape character, it is necessary to escape it from the `command parser'. This means that in practice you should use two escapes, for example: So, I changed my set login to set login "TIMEOUT 5 ogin:-\\r-ogin: \\#xxxxxxx word: xxxxxx" ^^ and, it worked. I previously tried one escape for the '#'. But, two parsers see the login string. So, two escapes are needed. Thanks for the reply. tomdean To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 14: 6: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 4BE5437B55E for ; Wed, 16 Feb 2000 14:06:06 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by builder.freebsd.org (Postfix) with ESMTP id 45E9A132E1 for ; Wed, 16 Feb 2000 14:05:22 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA00599; Wed, 16 Feb 2000 14:17:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002162217.OAA00599@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "David E. Cross" Cc: Gerald Abshez , freebsd-current@FreeBSD.ORG Subject: Re: Thinkpad won't boot ISO image In-reply-to: Your message of "Wed, 16 Feb 2000 13:43:23 EST." <200002161853.NAA52160@cs.rpi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Feb 2000 14:17:21 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > This is a problem with the thinkpad BIOS that I have not had the time to be > able to track down. It would *appear* to be that the BIOS does not do > int 13 handling on boot cdroms, and the boot/loader makes much use of that > for loading the kernel and drivers. The problem with the Thinkpad BIOS is where it puts the emulated floppy image's disk number - it's not in the 'normal' place, and I don't exactly know how to deal with it cleanly. If someone were to lend me a thinkpad or look at this it would be easy to fix. -- \\ 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-current" in the body of the message From owner-freebsd-current Wed Feb 16 14:14: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 72A4F37B505 for ; Wed, 16 Feb 2000 14:14:05 -0800 (PST) (envelope-from jasone@canonware.com) Received: from canonware.com (canonware.com [207.20.242.18]) by builder.freebsd.org (Postfix) with SMTP id 248EA132D6 for ; Wed, 16 Feb 2000 14:13:27 -0800 (PST) Received: (qmail 21752 invoked by uid 1001); 16 Feb 2000 22:13:39 -0000 Date: Wed, 16 Feb 2000 14:13:39 -0800 From: Jason Evans To: Matthew Dillon Cc: current@FreeBSD.org Subject: Re: Heads up, vm.max_proc_mmap sysctl added Message-ID: <20000216141339.C18774@sturm.canonware.com> References: <200002162118.NAA54097@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002162118.NAA54097@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Feb 16, 2000 at 01:18:13PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 16, 2000 at 01:18:13PM -0800, Matthew Dillon wrote: > This deals with a mmap+fork bomb that can cause the kernel to > eat all of KVM in vm_map_entry structures. The default limit > should be set generously enough for people using the current > FreeBSD threads incarnation (and isn't an issue w/ linux > threads due to rfork resulting in scaling of the limit for the > shared address space). > > Heads up in case a heavy threads programmer sees something I missed. Note that thread stack allocation in libc_r also uses mmap() (one region per thread), so this applies there as well. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 14:16:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 9E2D337B505 for ; Wed, 16 Feb 2000 14:16:47 -0800 (PST) (envelope-from jasone@canonware.com) Received: from canonware.com (canonware.com [207.20.242.18]) by builder.freebsd.org (Postfix) with SMTP id 7BDC3132D6 for ; Wed, 16 Feb 2000 14:16:09 -0800 (PST) Received: (qmail 21775 invoked by uid 1001); 16 Feb 2000 22:16:22 -0000 Date: Wed, 16 Feb 2000 14:16:22 -0800 From: Jason Evans To: Jason Evans Cc: Matthew Dillon , current@FreeBSD.org Subject: Re: Heads up, vm.max_proc_mmap sysctl added Message-ID: <20000216141622.E18774@sturm.canonware.com> References: <200002162118.NAA54097@apollo.backplane.com> <20000216141339.C18774@sturm.canonware.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000216141339.C18774@sturm.canonware.com>; from jasone@canonware.com on Wed, Feb 16, 2000 at 02:13:39PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 16, 2000 at 02:13:39PM -0800, Jason Evans wrote: > On Wed, Feb 16, 2000 at 01:18:13PM -0800, Matthew Dillon wrote: > > This deals with a mmap+fork bomb that can cause the kernel to > > eat all of KVM in vm_map_entry structures. The default limit > > should be set generously enough for people using the current > > FreeBSD threads incarnation (and isn't an issue w/ linux > > threads due to rfork resulting in scaling of the limit for the > > shared address space). > > > > Heads up in case a heavy threads programmer sees something I missed. > > Note that thread stack allocation in libc_r also uses mmap() (one region > per thread), so this applies there as well. Never mind. Matt stated this correctly, and I misread it. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 14:28:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 1AB0137B538; Wed, 16 Feb 2000 14:28:34 -0800 (PST) (envelope-from bartol@salk.edu) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by builder.freebsd.org (Postfix) with ESMTP id B51A1132EF; Wed, 16 Feb 2000 14:27:53 -0800 (PST) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id OAA09636; Wed, 16 Feb 2000 14:28:27 -0800 (PST) Date: Wed, 16 Feb 2000 14:28:28 -0800 (PST) From: Tom Bartol To: Mike Smith Cc: "David E. Cross" , Gerald Abshez , freebsd-current@FreeBSD.ORG Subject: Re: Thinkpad won't boot ISO image In-Reply-To: <200002162217.OAA00599@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Feb 2000, Mike Smith wrote: > > This is a problem with the thinkpad BIOS that I have not had the time to be > > able to track down. It would *appear* to be that the BIOS does not do > > int 13 handling on boot cdroms, and the boot/loader makes much use of that > > for loading the kernel and drivers. > > The problem with the Thinkpad BIOS is where it puts the emulated floppy > image's disk number - it's not in the 'normal' place, and I don't exactly > know how to deal with it cleanly. If someone were to lend me a thinkpad > or look at this it would be easy to fix. > I'd like to help look at this. I have a ThinkPad 770 and it too exhibits this behavior. Unfortunately it's my only laptop so I can't loan it out but I certainly would like to help out if I can. I've got an up-to-date -current running. What code should I look at in sys/boot and how do I figure out where the Thinkpad BIOS puts the emulated floppy image's disk number? Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 14:32:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 72C5B37B5A4; Wed, 16 Feb 2000 14:32:49 -0800 (PST) (envelope-from gerald@manhattanprojects.com) Received: from smtp.manhattanprojects.com (smtp.manhattanprojects.com [207.181.119.22]) by builder.freebsd.org (Postfix) with ESMTP id 8A8DC132E5; Wed, 16 Feb 2000 14:31:59 -0800 (PST) Received: from manhattanprojects.com (xs.lab.glc.com [10.0.0.14]) by smtp.manhattanprojects.com (8.9.1/8.8.7) with ESMTP id RAA16498; Wed, 16 Feb 2000 17:24:11 -0500 (EST) (envelope-from gerald@manhattanprojects.com) Message-ID: <38AB257D.9A2A93F7@manhattanprojects.com> Date: Wed, 16 Feb 2000 17:32:30 -0500 From: Gerald Abshez X-Mailer: Mozilla 4.05 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: Mike Smith Cc: "David E. Cross" , freebsd-current@FreeBSD.ORG Subject: Re: Thinkpad won't boot ISO image References: <200002162217.OAA00599@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mike Smith wrote: > The problem with the Thinkpad BIOS is where it puts the emulated floppy > image's disk number - it's not in the 'normal' place, and I don't exactly > know how to deal with it cleanly. If someone were to lend me a thinkpad > or look at this it would be easy to fix. How would I be able to help out with this? I have an older version of -CURRENT on one partition, if you have something that needs to be run under FreeBSD. I also have Win98 available, if that helps. Let me know... Gerald. -- This is your FreeBSD -- Where do YOU want to go tommorow? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 14:42:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 4E3C837B5A9 for ; Wed, 16 Feb 2000 14:42:26 -0800 (PST) (envelope-from keramida@diogenis.ceid.upatras.gr) Received: from mx2.x-treme.gr (mx2.x-treme.gr [212.120.192.15]) by builder.freebsd.org (Postfix) with ESMTP id 8C9A8132E7 for ; Wed, 16 Feb 2000 14:41:42 -0800 (PST) Received: from hades.hell.gr (pat28.x-treme.gr [212.120.197.220]) by mx2.x-treme.gr (8.9.3/8.9.3/IPNG-ADV-ANTISPAM-0.1) with SMTP id AAA28426 for ; Thu, 17 Feb 2000 00:42:10 +0200 Received: (qmail 2106 invoked by uid 1001); 16 Feb 2000 08:56:32 -0000 Date: Wed, 16 Feb 2000 10:56:32 +0200 From: Giorgos Keramidas To: Doug Barton Cc: Kazutaka YOKOTA , current@freebsd.org Subject: Re: 4.0 release candidate issues Message-ID: <20000216105632.A2039@hades.hell.gr> Reply-To: keramida@ceid.upatras.gr References: <200002150314.MAA20288@zodiac.mech.utsunomiya-u.ac.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from Doug@gorean.org on Tue, Feb 15, 2000 at 04:10:59PM -0800 X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E X-Phone-Number: +30-94-6203692, +30-93-2886457 X-Address: Theodorou Kirinaiou 61, 26334 Patra, Greece Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, Feb 15, 2000 at 04:10:59PM -0800, Doug Barton wrote: > On Tue, 15 Feb 2000, Kazutaka YOKOTA wrote: > > > `options XSERVER' is for vt0 only. sc0 doesn't need it to run the X > > server. > > Could you add appropriate comments to this effect in GENERIC and > LINT? I have always been confused by this, and IMO the placement in the > file is not sufficient to make it clear. For instance: > > -#options XSERVER # support for X server > +#options XSERVER # support for X server on a vt > console Nice thing. I think this will stop a lot of questions on their source. Some new users believed that running XF86Config was unnecessary after they added this to their kernel. Without the wrapping, thank you. -- Giorgos Keramidas, < keramida @ ceid . upatras . gr > For my public PGP key: finger keramida@diogenis.ceid.upatras.gr PGP fingerprint, phone and address in the headers of this message. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 15: 1:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id D596837B595 for ; Wed, 16 Feb 2000 15:01:45 -0800 (PST) (envelope-from scrappy@hub.org) Received: from thelab.hub.org (nat197.96.mpoweredpc.net [142.177.197.96]) by builder.freebsd.org (Postfix) with ESMTP id 1BD17132DE for ; Wed, 16 Feb 2000 15:01:04 -0800 (PST) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.1) with ESMTP id TAA19936; Wed, 16 Feb 2000 19:01:22 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 16 Feb 2000 19:01:21 -0400 (AST) From: The Hermit Hacker To: Dan Nelson Cc: freebsd-current@FreeBSD.ORG Subject: Re: Mounting Netware drive onto 4.0-CURRENT ... In-Reply-To: <20000216154043.A42792@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Feb 2000, Dan Nelson wrote: > In the last episode (Feb 16), The Hermit Hacker said: > > athena# ncplogin -S admin.acadiau.ca -U marc > > Warning: no cfg files found. > > ncplogin: can't find server ADMIN.ACADIAU.CA: syserr = No route to host > > athena# ncplogin -A admin.acadiau.ca > > ncplogin: no default connection found: syserr = Bad file descriptor > > > How does one 'set a route to host' in IPX? :( > > Hm. the "no route to host" means that it couldn't find > "admin.acadiau.ca" as a netware server name. I believe that the NCP > code is all bindery only right now, so giving an NDS object wouldn't > work. See if "ncplist s" shows any servers, and try to log into one of > those. *Much* better ... its just listed as 'admin' ... gives me a login failure when I try with ncplogin, but its been so login since I've last tried that I'm not surprised. Will talk to the Novell guys about that tomorrow ... thanks ... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 15:34: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 8406F37B568 for ; Wed, 16 Feb 2000 15:33:59 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id F30DE132DE for ; Wed, 16 Feb 2000 15:33:20 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA54729; Wed, 16 Feb 2000 15:33:58 -0800 (PST) (envelope-from dillon) Date: Wed, 16 Feb 2000 15:33:58 -0800 (PST) From: Matthew Dillon Message-Id: <200002162333.PAA54729@apollo.backplane.com> To: Jason Evans , current@FreeBSD.ORG Subject: Re: Heads up, vm.max_proc_mmap sysctl added References: <200002162118.NAA54097@apollo.backplane.com> <20000216141339.C18774@sturm.canonware.com> <20000216141622.E18774@sturm.canonware.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> > This deals with a mmap+fork bomb that can cause the kernel to :> > eat all of KVM in vm_map_entry structures. The default limit :> > should be set generously enough for people using the current :> > FreeBSD threads incarnation (and isn't an issue w/ linux :> > threads due to rfork resulting in scaling of the limit for the :> > shared address space). :> > :> > Heads up in case a heavy threads programmer sees something I missed. :> :> Note that thread stack allocation in libc_r also uses mmap() (one region :> per thread), so this applies there as well. : :Never mind. Matt stated this correctly, and I misread it. : :Jason Heh heh. Yes, this is my one worry - the guard page between thread stacks as well as the fact that MAP_STACK is used causes a vm_map_entry to be allocated for each thread stack, which is seriously annoying but there is nothing we can do about it at the moment. It is possible to fix the problem. We can add a new mmap() flag which we call MAP_GUARDED which would basically be an anonymous mmap() which implements a special case in vm_fault. This pager is designed to always return a failure for the first and last page. The size of the mmap() determines where the guard pages are and would be stored as part of the vm_map_entry (only for the MAP_GUARDED case). Adjacent vm_map_entry structures with the same guard size would be coalesced. Thus any threaded program will still only require a single vm_map_entry field yet still be completely flexible in regards to the guard pages. Is anyone interested in me doing this for the 4.0 release? It would help both our current threads model and the linux threads model a lot. I can do it in a day and it should be trivial to test, the modifications are actually quite minor. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 15:37:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 6FD4337B564 for ; Wed, 16 Feb 2000 15:37:26 -0800 (PST) (envelope-from Doug@gorean.org) Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by builder.freebsd.org (Postfix) with ESMTP id EDB44132E7 for ; Wed, 16 Feb 2000 15:36:47 -0800 (PST) Received: from slave (slave [10.0.0.1]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id PAA23252; Wed, 16 Feb 2000 15:34:51 -0800 (PST) (envelope-from Doug@gorean.org) Date: Wed, 16 Feb 2000 15:34:48 -0800 (PST) From: Doug Barton X-Sender: doug@dt051n0b.san.rr.com To: Giorgos Keramidas Cc: Kazutaka YOKOTA , current@freebsd.org Subject: Re: 4.0 release candidate issues In-Reply-To: <20000216105632.A2039@hades.hell.gr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Feb 2000, Giorgos Keramidas wrote: > On Tue, Feb 15, 2000 at 04:10:59PM -0800, Doug Barton wrote: > > On Tue, 15 Feb 2000, Kazutaka YOKOTA wrote: > > > > > `options XSERVER' is for vt0 only. sc0 doesn't need it to run the X > > > server. > > > > Could you add appropriate comments to this effect in GENERIC and > > LINT? I have always been confused by this, and IMO the placement in the > > file is not sufficient to make it clear. For instance: > > > > -#options XSERVER # support for X server > > +#options XSERVER # support for X server on a vt > > console > > Nice thing. I think this will stop a lot of questions on their source. > Some new users believed that running XF86Config was unnecessary after > they added this to their kernel. Ahhh.. a new area of confusion I hadn't even considered. :) > Without the wrapping, thank you. But of course. Kazu already committed the comment and I trusted him all along to DTRT with the line wrap. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 15:46:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 8BA9937B513; Wed, 16 Feb 2000 15:46:22 -0800 (PST) (envelope-from jhb@FreeBSD.org) Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by builder.freebsd.org (Postfix) with ESMTP id 6647B132F1; Wed, 16 Feb 2000 15:45:43 -0800 (PST) Received: from john.baldwin.cx (john [10.0.0.2]) by server.baldwin.cx (8.9.3/8.9.3) with ESMTP id SAA22380; Wed, 16 Feb 2000 18:46:11 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200002162346.SAA22380@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: <200002162217.OAA00599@mass.cdrom.com> Date: Wed, 16 Feb 2000 18:46:11 -0500 (EST) From: John Baldwin To: Mike Smith Subject: Re: Thinkpad won't boot ISO image Cc: freebsd-current@FreeBSD.org, Gerald Abshez , "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 16-Feb-00 Mike Smith wrote: >> This is a problem with the thinkpad BIOS that I have not had the time to be >> able to track down. It would *appear* to be that the BIOS does not do >> int 13 handling on boot cdroms, and the boot/loader makes much use of that >> for loading the kernel and drivers. > > The problem with the Thinkpad BIOS is where it puts the emulated floppy > image's disk number - it's not in the 'normal' place, and I don't exactly > know how to deal with it cleanly. If someone were to lend me a thinkpad > or look at this it would be easy to fix. Err, which place? The emulated device is always BIOS drive 0x00, aka the first floppy drive when you are emulating a floppy. -- 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-current" in the body of the message From owner-freebsd-current Wed Feb 16 15:48: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 7557237B513 for ; Wed, 16 Feb 2000 15:48:07 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 8F0A3132D6 for ; Wed, 16 Feb 2000 15:47:28 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id QAA15092; Wed, 16 Feb 2000 16:16:12 -0800 (PST) Date: Wed, 16 Feb 2000 16:16:12 -0800 From: Alfred Perlstein To: Matthew Dillon Cc: Jason Evans , current@FreeBSD.ORG Subject: Re: Heads up, vm.max_proc_mmap sysctl added Message-ID: <20000216161612.G3509@fw.wintelcom.net> References: <200002162118.NAA54097@apollo.backplane.com> <20000216141339.C18774@sturm.canonware.com> <20000216141622.E18774@sturm.canonware.com> <200002162333.PAA54729@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002162333.PAA54729@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Feb 16, 2000 at 03:33:58PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Matthew Dillon [000216 16:05] wrote: > > It is possible to fix the problem. We can add a new mmap() flag which > we call MAP_GUARDED which would basically be an anonymous mmap() which > implements a special case in vm_fault. This pager is designed to always > return a failure for the first and last page. The size of the mmap() > determines where the guard pages are and would be stored as part of > the vm_map_entry (only for the MAP_GUARDED case). > > Adjacent vm_map_entry structures with the same guard size would be > coalesced. > > Thus any threaded program will still only require a single vm_map_entry > field yet still be completely flexible in regards to the guard pages. > > Is anyone interested in me doing this for the 4.0 release? It would > help both our current threads model and the linux threads model a lot. > I can do it in a day and it should be trivial to test, the modifications > are actually quite minor. I'd love to see it happen for 4.0. Toss some diffs up and we'll see if Jordan gives it an ok. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 15:52:28 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id A32C337B583; Wed, 16 Feb 2000 15:52:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by builder.freebsd.org (Postfix) with ESMTP id 7FFBE132EF; Wed, 16 Feb 2000 15:51:47 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id QAA01571; Wed, 16 Feb 2000 16:03:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002170003.QAA01571@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Bartol Cc: Mike Smith , "David E. Cross" , Gerald Abshez , freebsd-current@FreeBSD.ORG Subject: Re: Thinkpad won't boot ISO image In-reply-to: Your message of "Wed, 16 Feb 2000 14:28:28 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Feb 2000 16:03:51 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > The problem with the Thinkpad BIOS is where it puts the emulated floppy > > image's disk number - it's not in the 'normal' place, and I don't exactly > > know how to deal with it cleanly. If someone were to lend me a thinkpad > > or look at this it would be easy to fix. > > I'd like to help look at this. I have a ThinkPad 770 and it too exhibits > this behavior. Unfortunately it's my only laptop so I can't loan it out > but I certainly would like to help out if I can. I've got an > up-to-date -current running. What code should I look at in sys/boot and > how do I figure out where the Thinkpad BIOS puts the emulated floppy > image's disk number? You'll need a CD burner and the time & patience to produce a small number of coasters for this. In sys/boot/i386/loader/main.c:main() you will need to print the value of initial_bootdev, sometime after the console is initialised. From what I've seen, I get the impression that it will be something like 0x87. This is the root of the problem; floppy disks are typically numbered 0,1 and hard disks are numbered 0x80,0x81, etc. Normally all the unit numbers are contiguous. If this is the case, you will need to modify sys/boot/i386/libi386/biosdisk.c:bd_init() to check whether it's scanned the BIOS unit number from initial_bootdev, and if not (and it's legal) scan it as well. Once we've 'probed' the BIOS unit, everything else should work correctly. If you decide to take this on, please let me know how you go. 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-current" in the body of the message From owner-freebsd-current Wed Feb 16 15:52:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 5288C37B583 for ; Wed, 16 Feb 2000 15:52:49 -0800 (PST) (envelope-from jasone@canonware.com) Received: from canonware.com (canonware.com [207.20.242.18]) by builder.freebsd.org (Postfix) with SMTP id 32ADB132DD for ; Wed, 16 Feb 2000 15:52:10 -0800 (PST) Received: (qmail 22072 invoked by uid 1001); 16 Feb 2000 23:52:22 -0000 Date: Wed, 16 Feb 2000 15:52:22 -0800 From: Jason Evans To: Matthew Dillon Cc: Jason Evans , current@FreeBSD.ORG Subject: Re: Heads up, vm.max_proc_mmap sysctl added Message-ID: <20000216155222.G18774@sturm.canonware.com> References: <200002162118.NAA54097@apollo.backplane.com> <20000216141339.C18774@sturm.canonware.com> <20000216141622.E18774@sturm.canonware.com> <200002162333.PAA54729@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002162333.PAA54729@apollo.backplane.com>; from dillon@apollo.backplane.com on Wed, Feb 16, 2000 at 03:33:58PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, Feb 16, 2000 at 03:33:58PM -0800, Matthew Dillon wrote: > Is anyone interested in me doing this for the 4.0 release? It would > help both our current threads model and the linux threads model a lot. > I can do it in a day and it should be trivial to test, the modifications > are actually quite minor. I would really like to see this change happen, and will happily make the necessary libc_r and linuxthreads changes to use the functionality, but we're well into the code freeze right now, which IMO makes this more appropriate for 4.1. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 16:18:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 3E34A37B598; Wed, 16 Feb 2000 16:18:46 -0800 (PST) (envelope-from bartol@salk.edu) Received: from helmholtz.salk.edu (helmholtz.salk.edu [198.202.70.34]) by builder.freebsd.org (Postfix) with ESMTP id AFDC9132E0; Wed, 16 Feb 2000 16:18:04 -0800 (PST) Received: from eccles.salk.edu (eccles [198.202.70.120]) by helmholtz.salk.edu (8.7.5/8.7.3) with ESMTP id QAA11924; Wed, 16 Feb 2000 16:18:41 -0800 (PST) Date: Wed, 16 Feb 2000 16:18:42 -0800 (PST) From: Tom Bartol To: Mike Smith Cc: "David E. Cross" , Gerald Abshez , freebsd-current@FreeBSD.ORG Subject: Re: Thinkpad won't boot ISO image In-Reply-To: <200002170003.QAA01571@mass.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Feb 2000, Mike Smith wrote: > > > The problem with the Thinkpad BIOS is where it puts the emulated floppy > > > image's disk number - it's not in the 'normal' place, and I don't exactly > > > know how to deal with it cleanly. If someone were to lend me a thinkpad > > > or look at this it would be easy to fix. > > > > I'd like to help look at this. I have a ThinkPad 770 and it too exhibits > > this behavior. Unfortunately it's my only laptop so I can't loan it out > > but I certainly would like to help out if I can. I've got an > > up-to-date -current running. What code should I look at in sys/boot and > > how do I figure out where the Thinkpad BIOS puts the emulated floppy > > image's disk number? > > You'll need a CD burner and the time & patience to produce a small number > of coasters for this. O.K. I've got a burner and boat loads of cheap media so no problem there. One question though -- Once I've modified the sources as you've outlined below, how do I make the bootable floppy image that gets written to the CDR? > > In sys/boot/i386/loader/main.c:main() you will need to print the value of > initial_bootdev, sometime after the console is initialised. From what > I've seen, I get the impression that it will be something like 0x87. > This is the root of the problem; floppy disks are typically numbered 0,1 > and hard disks are numbered 0x80,0x81, etc. Normally all the unit > numbers are contiguous. Understood (I think) :-) On my Thinkpad I believe I've seen things like 0x8b or some such. This will be the first CD to burn... > > If this is the case, you will need to modify > sys/boot/i386/libi386/biosdisk.c:bd_init() to check whether it's scanned > the BIOS unit number from initial_bootdev, and if not (and it's legal) > scan it as well. Once we've 'probed' the BIOS unit, everything else > should work correctly. O.K. this makes a lot of sense and sounds easy. > > If you decide to take this on, please let me know how you go. Will do! > > Thanks! > And thank you too!!! Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 16:37:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 75F8437B513 for ; Wed, 16 Feb 2000 16:37:53 -0800 (PST) (envelope-from phoenix@notwise.bsdonline.org) Received: from notwise.bsdonline.org (port130.erdial.netdoor.com [208.137.151.130]) by builder.freebsd.org (Postfix) with ESMTP id 5462E132EC for ; Wed, 16 Feb 2000 16:36:50 -0800 (PST) Received: from localhost (phoenix@localhost) by notwise.bsdonline.org (8.9.3/8.8.7) with ESMTP id SAA03293 for ; Wed, 16 Feb 2000 18:37:36 -0600 Date: Wed, 16 Feb 2000 18:37:34 -0600 (CST) From: Phoenix To: freebsd-current@freebsd.org Subject: dev/umass major and minor numbers Message-ID: X-Secure: warning Penguin Powered. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The current MAKEDEV script seems to be lacking the umass device. I have searched all the docs that I know of and have been unable to find a listing of the major and minor number assaignments, could someone please point me in the right direction ? Bob Rentschler To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 16:52:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 5F12C37B505; Wed, 16 Feb 2000 16:52:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by builder.freebsd.org (Postfix) with ESMTP id A79D4132E7; Wed, 16 Feb 2000 16:51:45 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02112; Wed, 16 Feb 2000 17:04:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002170104.RAA02112@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: Mike Smith , freebsd-current@FreeBSD.org, Gerald Abshez , "David E. Cross" Subject: Re: Thinkpad won't boot ISO image In-reply-to: Your message of "Wed, 16 Feb 2000 18:46:11 EST." <200002162346.SAA22380@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Feb 2000 17:04:25 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 16-Feb-00 Mike Smith wrote: > >> This is a problem with the thinkpad BIOS that I have not had the time to be > >> able to track down. It would *appear* to be that the BIOS does not do > >> int 13 handling on boot cdroms, and the boot/loader makes much use of that > >> for loading the kernel and drivers. > > > > The problem with the Thinkpad BIOS is where it puts the emulated floppy > > image's disk number - it's not in the 'normal' place, and I don't exactly > > know how to deal with it cleanly. If someone were to lend me a thinkpad > > or look at this it would be easy to fix. > > Err, which place? The emulated device is always BIOS drive 0x00, aka the > first floppy drive when you are emulating a floppy. It's not, which is the "Thinkpad CDROM boot problem". The one report I recall put it on 0x87, but I don't have any concrete evidence to suggest that it's always there either. -- \\ 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-current" in the body of the message From owner-freebsd-current Wed Feb 16 16:56:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id ABA4237B505 for ; Wed, 16 Feb 2000 16:56:51 -0800 (PST) (envelope-from jeff@mountin.net) Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by builder.freebsd.org (Postfix) with ESMTP id D6B15132E0 for ; Wed, 16 Feb 2000 16:56:06 -0800 (PST) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id SAA19650 for ; Wed, 16 Feb 2000 18:56:44 -0600 (CST) (envelope-from jeff@mountin.net) Received: from dial-65.max1.wa.cyberlynk.net(207.227.118.65) by peak.mountin.net via smap (V1.3) id sma019628; Wed Feb 16 18:56:42 2000 Message-Id: <3.0.3.32.20000216185632.009d0c00@207.227.119.2> X-Sender: jeffm@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 16 Feb 2000 18:56:32 -0600 To: current@FreeBSD.org From: "Jeffrey J. Mountin" Subject: installworld problem(s) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG CVSup -current as of Wed Feb 16 04:11:01 CST... Figured I'd try a build/install from source before wiping it all for the latest RC: ===> gnu/usr.bin/binutils/doc install-info --quiet --defsection="Programming & development tools." --defentry="* As: (as). The GNU assembler." as.info /usr/share/info/dir install-info --quiet --defsection="Programming & development tools." --defentry="* Ld: (ld). The GNU linker." ld.info /usr/share/info/dir install-info --quiet --defsection="Programming & development tools." --defentry="* GDB annotation: (annotate). Annotations for the GNU Debugger (GDB)." annotate.info /usr/share/info/dir install-info --quiet --defsection="Programming & development tools." --defentry= gdb.info /usr/sh are/info/dir install-info --quiet --defsection="Programming & development tools." --defentry= gdbint.info /usr /share/info/dir install-info --quiet --defsection="Programming & development tools." --defentry= stabs.info /usr/ share/info/dir install-info: /usr/share/info/dir: empty file *** Error code 1 install-info: /usr/share/info/dir: empty file *** Error code 1 2 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error What empty file? The target is there and the source is: ls -l /usr/obj/usr/src/gnu/usr.bin/binutils/doc total 1419 -rw-r--r-- 1 root wheel 23038 Feb 16 07:12 annotate.info -rw-r--r-- 1 root wheel 6762 Feb 16 07:12 annotate.info.gz -rw-r--r-- 1 root wheel 153475 Feb 16 07:12 as.info -rw-r--r-- 1 root wheel 45228 Feb 16 07:12 as.info.gz lrwxr-xr-x 1 root wheel 78 Feb 16 07:12 gdb-cfg.texi -> /usr/src/gnu/usr.bin/binutils/doc/../../../../contrib/gdb/gdb/doc/all-cfg.texi -rw-r--r-- 1 root wheel 452513 Feb 16 07:12 gdb.info -rw-r--r-- 1 root wheel 132031 Feb 16 07:12 gdb.info.gz -rw-r--r-- 1 root wheel 105081 Feb 16 07:12 gdbint.info -rw-r--r-- 1 root wheel 36400 Feb 16 07:12 gdbint.info.gz -rw-r--r-- 1 root wheel 14182 Feb 16 07:12 inc-hist.texi -rw-r--r-- 1 root wheel 14174 Feb 16 07:12 inc-hist.texi.orig -rw-r--r-- 1 root wheel 150162 Feb 16 07:12 ld.info -rw-r--r-- 1 root wheel 43884 Feb 16 07:12 ld.info.gz -rw-r--r-- 1 root wheel 152635 Feb 16 07:12 stabs.info -rw-r--r-- 1 root wheel 45007 Feb 16 07:12 stabs.info.gz Um, yeah. No recent commits AFAIK that should effect this. So much for my build/install streak, but then this is my first -current in a long while. ;) Here's the same point with '-k': ===> gnu/usr.bin/binutils/doc install-info --quiet --defsection="Programming & development tools." --defentry="* As: (as). The GNU assembler." as.info /usr/share/info/dir install-info: /usr/share/info/dir: empty file install-info --quiet --defsection="Programming & development tools." --defentry="* Ld: (ld). The GNU linker." ld.info /usr/share/info/dir install-info: /usr/share/info/dir: empty file install-info --quiet --defsection="Programming & development tools." --defentry="* GDB annotation: (annotate). Annotations for the GNU Debugger (GDB)." annotate.info /usr/share/info/dir install-info --quiet --defsection="Programming & development tools." --defentry= gdb.info /usr/sh are/info/dir install-info --quiet --defsection="Programming & development tools." --defentry= gdbint.info /usr /share/info/dir *** Error code 1 *** Error code 1 install-info --quiet --defsection="Programming & development tools." --defentry= stabs.info /usr/ share/info/dir `install' not remade because of errors. ===> gnu/usr.bin/binutils/gdb And runs error free to completion. Also interesting was during my endeavor I dropped 'INSTALL=install -C' from make.conf and it died way earlier in the install: ===> lib/libncurses install -c -o root -g wheel -m 444 term.7.gz /usr/share/man/man7 /usr/share/man/man3/addch.3.gz -> /usr/share/man/man3/curs_addch.3.gz /usr/share/man/man3/echochar.3.gz -> /usr/share/man/man3/curs_addch.3.gz /usr/share/man/man3/mvaddch.3.gz -> /usr/share/man/man3/curs_addch.3.gz /usr/share/man/man3/mvwaddch.3.gz -> /usr/share/man/man3/curs_addch.3.gz /usr/share/man/man3/waddch.3.gz -> /usr/share/man/man3/curs_addch.3.gz /usr/share/man/man3/wechochar.3.gz -> /usr/share/man/man3/curs_addch.3.gz /usr/share/man/man3/addchnstr.3.gz -> /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/addchstr.3.gz -> /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/mvaddchnstr.3.gz -> /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/mvaddchstr.3.gz -> /usr/share/man/man3/curs_addchstr.3.gz /usr/share/man/man3/mvwaddchnstr.3.gz -> /usr/share/man/man3/curs_addchstr.3.gz install -c -o root -g wheel -m 444 curs_addch.3.gz curs_addchstr.3.gz curs_addstr.3.gz curs_attr.3.g z curs_beep.3.gz curs_bkgd.3.gz curs_border.3.gz curs_clear.3.gz curs_color.3.gz curs_delch.3.gz cur s_deleteln.3.gz curs_getch.3.gz curs_getstr.3.gz curs_getyx.3.gz curs_inch.3.gz curs_inchstr.3.gz cu rs_initscr.3.gz curs_inopts.3.gz curs_insch.3.gz curs_insstr.3.gz curs_instr.3.gz curs_kernel.3.gz c urs_mouse.3.gz curs_move.3.gz curs_outopts.3.gz curs_overlay.3.gz curs_pad.3.gz curs_print.3.gz curs _printw.3.gz curs_refresh.3.gz curs_scanw.3.gz curs_scr_dump.3.gz curs_scroll.3.gz curs_slk.3.gz cur s_termattrs.3.gz curs_termcap.3.gz curs_terminfo.3.gz curs_touch.3.gz curs_util.3.gz curs_window.3.g z define_key.3.gz dft_fgbg.3.gz keybound.3.gz keyok.3.gz ncurses.3.gz resizeterm.3.gz wresize.3.gz /usr/share/man/man3 install -c -o root -g wheel -m 444 term.5.gz terminfo.5.gz /usr/share/man/man5 install -c -o root -g wheel -m 444 curses.h term.h termcap.h unctrl.h /usr/include ln: /usr/share/man/man3/curs_addchstr.3.gz: No such file or directory *** Error code 1 rm -f /usr/include/ncurses.h ln -s curses.h /usr/include/ncurses.h 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Can't recall the last time I didn't use 'install -C', so this may be a problem. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 16:59:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id E53CA37B505 for ; Wed, 16 Feb 2000 16:59:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by builder.freebsd.org (Postfix) with ESMTP id 9EFC3132DE for ; Wed, 16 Feb 2000 16:58:44 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02211; Wed, 16 Feb 2000 17:10:46 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002170110.RAA02211@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tom Bartol Cc: freebsd-current@FreeBSD.ORG Subject: Re: Thinkpad won't boot ISO image In-reply-to: Your message of "Wed, 16 Feb 2000 16:18:42 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Feb 2000 17:10:46 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > O.K. I've got a burner and boat loads of cheap media so no problem there. > One question though -- Once I've modified the sources as you've outlined > below, how do I make the bootable floppy image that gets written to the > CDR? Since we only care about getting to the point where the loader can read the disk image, it's actually pretty easy. Take the kern.flp file off the install CD, then say: vnconfig /dev/vn0 kern.flp mount /dev/vn0a /mnt umount /mnt vnconfig -u /dev/vn0 After that, you can create an almost empty CD, which should take very little time to burn... -- \\ 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-current" in the body of the message From owner-freebsd-current Wed Feb 16 17: 3:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 07D6737B505 for ; Wed, 16 Feb 2000 17:03:30 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by builder.freebsd.org (Postfix) with ESMTP id 73874132E0 for ; Wed, 16 Feb 2000 17:02:51 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02277; Wed, 16 Feb 2000 17:15:00 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002170115.RAA02277@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: current@freebsd.org Subject: Re: Perc 2/SC problems (aka MegaRAID 466) In-reply-to: Your message of "Wed, 16 Feb 2000 15:14:00 EST." <3.0.5.32.20000216151400.00ff5e40@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Feb 2000 17:15:00 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > I have been trying to get a PERC 2 (aka MegaRAID 466) working with > Current. The box worked fine with the 428, but seems to barf with only the > controller swapped. I don't think the two controllers share on-disk configuration formats; you'll probably need to re-initialise the array (I could be wrong about that). > newmail# dd if=/dev/zero of=/dev/ramrd0 bs=1k count=1 > 1+0 records in > 1+0 records out > 1024 bytes transferred in 0.000446 secs (2295546 bytes/sec) > newmail# !fd > fdisk amrd0 > ******* Working on device /dev/ramrd0 ******* > parameters extracted from in-core disklabel are: > cylinders=2217 heads=255 sectors/track=63 (16065 blks/cyl) > > Figures below won't work with BIOS for partitions not in cyl 1 > parameters to be used for BIOS calculations are: > cylinders=2217 heads=255 sectors/track=63 (16065 blks/cyl) > > fdisk: invalid fdisk partition table found > Media sector size is 512 > Warning: BIOS sector numbering starts with sector 1 > Information from DOS bootblock is: > The data for partition 1 is: > > The data for partition 2 is: > > The data for partition 3 is: > > The data for partition 4 is: > sysid 165,(FreeBSD/NetBSD/386BSD) > start 1, size 35616104 (17390 Meg), flag 80 (active) > beg: cyl 0/ sector 2/ head 0; > end: cyl 168/ sector 63/ head 254 > newmail# disklabel -Brw amrd0 auto You probably don't want to do that with a valid slice table installed; the slice code does silly things. Try nuking it first: # dd if=/dev/zero of=/dev/amrd0 count=16 > This is using the BIOS from Dell. Should I be trying the latest and > greatest directly from AMI ? There is a warning from them however saying > not to use the AMI version with OEM cards. Should I try it anyways ? This isn't a BIOS issue, as far as I can tell. -- \\ 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-current" in the body of the message From owner-freebsd-current Wed Feb 16 17:20:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 4F7CA37B505 for ; Wed, 16 Feb 2000 17:20:50 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: from fep02-svc.mail.telepac.pt (fep02-svc.mail.telepac.pt [194.65.5.201]) by builder.freebsd.org (Postfix) with ESMTP id 9C5C0132D6 for ; Wed, 16 Feb 2000 17:20:08 -0800 (PST) Received: from manecao.tafkap.priv ([212.55.187.55]) by fep02-svc.mail.telepac.pt (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000217012328.CIKS4775.fep02-svc.mail.telepac.pt@manecao.tafkap.priv> for ; Thu, 17 Feb 2000 01:23:28 +0000 Content-Length: 671 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: Thu, 17 Feb 2000 01:20:45 -0000 (GMT) Reply-To: Joao Pedras From: Joao Pedras To: freebsd-current@freebsd.org Subject: freezing Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all While making -j 4 buildworld and moving a netscape window, everything frozen. Happens often if do other things while cpu and disk are very active. Happens quite often. Anyone else has noticed this ? Joao ^\ /^ O O ----------------------------------------o00-(_)-00o-------------------------- Shaw's Principle: Build a system that even a fool can use, and only a fool will want to use it. ----------------------------------------------------------------------------- PGP key available upon request or may be cut at http://pedras.webvolution.net/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 17:24:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 18B0A37B5F0 for ; Wed, 16 Feb 2000 17:24:41 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 3D162132E3 for ; Wed, 16 Feb 2000 17:24:02 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id RAA17552; Wed, 16 Feb 2000 17:52:42 -0800 (PST) Date: Wed, 16 Feb 2000 17:52:42 -0800 From: Alfred Perlstein To: Joao Pedras Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing Message-ID: <20000216175242.J3509@fw.wintelcom.net> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jpedras@webvolution.net on Thu, Feb 17, 2000 at 01:20:45AM -0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Joao Pedras [000216 17:50] wrote: > Hello all > > While making -j 4 buildworld and moving a netscape window, everything frozen. > Happens often if do other things while cpu and disk are very active. > > Happens quite often. > > Anyone else has noticed this ? Do you mean dead frozen, as in needs a reboot? or frozen for a second or so? The first one I haven't seen recently, the second I have noticed. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 17:38:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 209AC37B595 for ; Wed, 16 Feb 2000 17:38:44 -0800 (PST) (envelope-from jpedras@webvolution.net) Received: from fep03-svc.mail.telepac.pt (fep03-svc.mail.telepac.pt [194.65.5.202]) by builder.freebsd.org (Postfix) with ESMTP id C634E132E6 for ; Wed, 16 Feb 2000 17:37:55 -0800 (PST) Received: from manecao.tafkap.priv ([212.55.187.55]) by fep03-svc.mail.telepac.pt (InterMail vM.4.01.02.27 201-229-119-110) with ESMTP id <20000217014104.BWTK27212.fep03-svc.mail.telepac.pt@manecao.tafkap.priv>; Thu, 17 Feb 2000 01:41:04 +0000 Content-Length: 732 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: <20000216175242.J3509@fw.wintelcom.net> Date: Thu, 17 Feb 2000 01:38:21 -0000 (GMT) Reply-To: Joao Pedras From: Joao Pedras To: Alfred Perlstein Subject: Re: freezing Cc: freebsd-current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG eheh I mean dead frozen, like if I was watching at a screeshot of a X session ]:) Alfred Perlstein wrote: > > Do you mean dead frozen, as in needs a reboot? or frozen for a second or > so? > > The first one I haven't seen recently, the second I have noticed. > > -Alfred ^\ /^ O O ----------------------------------------o00-(_)-00o-------------------------- Common sense is the collection of prejudices acquired by age eighteen. -- Albert Einstein ----------------------------------------------------------------------------- PGP key available upon request or may be cut at http://pedras.webvolution.net/pgpkey.html To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 17:41: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 073DD37B595 for ; Wed, 16 Feb 2000 17:41:07 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by builder.freebsd.org (Postfix) with ESMTP id 4D410132D9 for ; Wed, 16 Feb 2000 17:40:25 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id RAA02710; Wed, 16 Feb 2000 17:52:27 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002170152.RAA02710@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Jim Shankland Cc: freebsd-current@freebsd.org Subject: Re: sysinstall of 20000214 snap hangs In-reply-to: Your message of "Wed, 16 Feb 2000 11:54:57 PST." <200002161954.LAA13282@biggusdiskus.flyingfox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Feb 2000 17:52:27 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I just tried installing the 2/14 4.0 snap onto a Cyrix MediaGX-based > box, and the sysinstall hung at the "probing devices" phase. > > Because the 3.4 sysinstall works just fine on this box, and because > the last thing I see on the debug screen (ttyv1) is > > DEBUG: Found a disk device named ad0 > > I'm inclined to cast a suspicious eye toward Soren's new IDE driver :-). 8) At that point, it's actually more or less finished with the IDE drive, actually, so it's probably not that. > I realize the information I've provided so far is unlikely to be > sufficient to diagnose, much less remedy, the problem; but I'm not > not sure what to do next. I'm happy to work with anyone who'd > like to take a closer look at this. Debugging these is often actually really painful, because it's hard to tell where exactly you're hung up. You might try hitting a key on the main sysinstall screen (don't laugh), as well as checking for peripherals that are wedged in an active state (eg. CDROM if it's not already listed as found). Then you might also try disabling any devices in the kernel config that aren't actually present in your system (eg. second IDE channel, random ethernet interfaces especially). -- \\ 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-current" in the body of the message From owner-freebsd-current Wed Feb 16 17:41:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id E1DEE37B595 for ; Wed, 16 Feb 2000 17:41:43 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id 0D6BA132E0 for ; Wed, 16 Feb 2000 17:40:58 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id SAA18035; Wed, 16 Feb 2000 18:09:40 -0800 (PST) Date: Wed, 16 Feb 2000 18:09:40 -0800 From: Alfred Perlstein To: Joao Pedras Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing Message-ID: <20000216180940.K3509@fw.wintelcom.net> References: <20000216175242.J3509@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from jpedras@webvolution.net on Thu, Feb 17, 2000 at 01:38:21AM -0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Joao Pedras [000216 18:07] wrote: > eheh > > I mean dead frozen, like if I was watching at a screeshot of a X session ]:) > > Alfred Perlstein wrote: > > > > Do you mean dead frozen, as in needs a reboot? or frozen for a second or > > so? > > > > The first one I haven't seen recently, the second I have noticed. > > > > -Alfred oy! well i guess you need to grab a serial console and see if you can get a crashdump/traceback. let us know if you find out, also check your machine's cooling devices to make sure they are functioning normally. good luck, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 18:42:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 6018F37B53C; Wed, 16 Feb 2000 18:42:18 -0800 (PST) (envelope-from mike@sentex.net) Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by builder.freebsd.org (Postfix) with ESMTP id E66F5132F6; Wed, 16 Feb 2000 18:41:37 -0800 (PST) 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 VAA26223; Wed, 16 Feb 2000 21:42:15 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (p0b.clorine2.sentex.ca [64.7.139.16]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id VAA13495; Wed, 16 Feb 2000 21:42:14 -0500 (EST) Message-Id: <4.2.2.20000216213742.0335de98@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 16 Feb 2000 21:41:09 -0500 To: Mike Smith From: Mike Tancsa Subject: Re: Perc 2/SC problems (aka MegaRAID 466) Cc: current@freebsd.org In-Reply-To: <200002170115.RAA02277@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 05:15 PM 2/16/2000 -0800, Mike Smith wrote: > > Hi, > > I have been trying to get a PERC 2 (aka MegaRAID 466) working with > > Current. The box worked fine with the 428, but seems to barf with only the > > controller swapped. > >I don't think the two controllers share on-disk configuration formats; >you'll probably need to re-initialise the array (I could be wrong about >that). Yes, I did that. I blew away the old config, created a new set, and initialized the array. You probably don't want to do that with a valid slice table installed; >the slice code does silly things. Try nuking it first: > ># dd if=/dev/zero of=/dev/amrd0 count=16 newmail# dd if=/dev/zero of=/dev/amrd0 count=16 16+0 records in 16+0 records out 8192 bytes transferred in 0.006427 secs (1274613 bytes/sec) newmail# disklabel -Brw amrd0 auto newmail# disklabel -e amrd0 disklabel: ioctl DIOCGDINFO: Invalid argument Same deal :-( ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 18:46:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 0289737B5E4 for ; Wed, 16 Feb 2000 18:46:43 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by builder.freebsd.org (Postfix) with ESMTP id B480D132D6 for ; Wed, 16 Feb 2000 18:46:00 -0800 (PST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id NAA21739; Thu, 17 Feb 2000 13:16:20 +1030 (CST) Date: Thu, 17 Feb 2000 13:16:19 +1030 From: Greg Lehey To: Alfred Perlstein Cc: Joao Pedras , freebsd-current@FreeBSD.ORG Subject: Very slow disk transfers (was: freezing) Message-ID: <20000217131618.G20710@freebie.lemis.com> References: <20000216175242.J3509@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000216175242.J3509@fw.wintelcom.net> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wednesday, 16 February 2000 at 17:52:42 -0800, Alfred Perlstein wrote: > * Joao Pedras [000216 17:50] wrote: >> Hello all >> >> While making -j 4 buildworld and moving a netscape window, everything frozen. >> Happens often if do other things while cpu and disk are very active. >> >> Happens quite often. >> >> Anyone else has noticed this ? > > Do you mean dead frozen, as in needs a reboot? or frozen for a second or > so? > > The first one I haven't seen recently, the second I have noticed. I'm seeing the second situation. I've been following it up and find that I have a number of requests which take an inordinate amount of time in the driver strategy routine: Feb 17 12:50:00 freebie /kernel: Request took 10.373469 seconds, dev 3.31, block 5468256, length 16384 The time here is between entering adstrategy (in this case) and biodone. It happens on SCSI drives too, so it doesn't appear to be a problem with a specific driver. If anybody has a suggestion what I should look for next, I'd be grateful. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 18:53: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id CD09937B5E4 for ; Wed, 16 Feb 2000 18:52:58 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by builder.freebsd.org (Postfix) with ESMTP id 7600A132F3 for ; Wed, 16 Feb 2000 18:52:19 -0800 (PST) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA03502; Wed, 16 Feb 2000 19:04:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002170304.TAA03502@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: current@freebsd.org Subject: Re: Perc 2/SC problems (aka MegaRAID 466) In-reply-to: Your message of "Wed, 16 Feb 2000 21:41:09 EST." <4.2.2.20000216213742.0335de98@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 16 Feb 2000 19:04:28 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 05:15 PM 2/16/2000 -0800, Mike Smith wrote: > > > Hi, > > > I have been trying to get a PERC 2 (aka MegaRAID 466) working with > > > Current. The box worked fine with the 428, but seems to barf with only the > > > controller swapped. > > > >I don't think the two controllers share on-disk configuration formats; > >you'll probably need to re-initialise the array (I could be wrong about > >that). > > Yes, I did that. I blew away the old config, created a new set, and > initialized the array. > > > You probably don't want to do that with a valid slice table installed; > >the slice code does silly things. Try nuking it first: > > > ># dd if=/dev/zero of=/dev/amrd0 count=16 > > newmail# dd if=/dev/zero of=/dev/amrd0 count=16 > 16+0 records in > 16+0 records out > 8192 bytes transferred in 0.006427 secs (1274613 bytes/sec) > newmail# disklabel -Brw amrd0 auto > newmail# disklabel -e amrd0 > disklabel: ioctl DIOCGDINFO: Invalid argument Hmm. I should have paid more attention to the fdisk output the first time; you already had the whole-disk label in place. What's the output from 'disklabel mlxd0'? -- \\ 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-current" in the body of the message From owner-freebsd-current Wed Feb 16 18:55:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 13D5337B5E4 for ; Wed, 16 Feb 2000 18:55:36 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by builder.freebsd.org (Postfix) with ESMTP id BE257132D6 for ; Wed, 16 Feb 2000 18:54:56 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id TAA20763; Wed, 16 Feb 2000 19:23:36 -0800 (PST) Date: Wed, 16 Feb 2000 19:23:36 -0800 From: Alfred Perlstein To: Greg Lehey Cc: Joao Pedras , freebsd-current@FreeBSD.ORG Subject: Re: Very slow disk transfers (was: freezing) Message-ID: <20000216192336.L3509@fw.wintelcom.net> References: <20000216175242.J3509@fw.wintelcom.net> <20000217131618.G20710@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000217131618.G20710@freebie.lemis.com>; from grog@lemis.com on Thu, Feb 17, 2000 at 01:16:19PM +1030 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Greg Lehey [000216 19:14] wrote: > On Wednesday, 16 February 2000 at 17:52:42 -0800, Alfred Perlstein wrote: > > * Joao Pedras [000216 17:50] wrote: > >> Hello all > >> > >> While making -j 4 buildworld and moving a netscape window, everything frozen. > >> Happens often if do other things while cpu and disk are very active. > >> > >> Happens quite often. > >> > >> Anyone else has noticed this ? > > > > Do you mean dead frozen, as in needs a reboot? or frozen for a second or > > so? > > > > The first one I haven't seen recently, the second I have noticed. > > I'm seeing the second situation. I've been following it up and find > that I have a number of requests which take an inordinate amount of > time in the driver strategy routine: > > Feb 17 12:50:00 freebie /kernel: Request took 10.373469 seconds, dev 3.31, block 5468256, length 16384 > > The time here is between entering adstrategy (in this case) and > biodone. It happens on SCSI drives too, so it doesn't appear to be a > problem with a specific driver. If anybody has a suggestion what I > should look for next, I'd be grateful. Could you put up a patchset against -current up someplace that includes these diagnostics? I'd like to see if that's what's nailing me. thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 18:57:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id C0E1A37B5E4; Wed, 16 Feb 2000 18:57:16 -0800 (PST) (envelope-from mike@sentex.net) Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by builder.freebsd.org (Postfix) with ESMTP id A818B132F7; Wed, 16 Feb 2000 18:56:36 -0800 (PST) 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 VAA27966; Wed, 16 Feb 2000 21:57:15 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id VAA17585; Wed, 16 Feb 2000 21:57:13 -0500 (EST) Message-Id: <4.2.2.20000216215442.00abd4a0@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Wed, 16 Feb 2000 21:56:14 -0500 To: Mike Smith From: Mike Tancsa Subject: Re: Perc 2/SC problems (aka MegaRAID 466) Cc: current@freebsd.org In-Reply-To: <200002170304.TAA03502@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:04 PM 2/16/2000 -0800, Mike Smith wrote: > > newmail# dd if=/dev/zero of=/dev/amrd0 count=16 > > 16+0 records in > > 16+0 records out > > 8192 bytes transferred in 0.006427 secs (1274613 bytes/sec) > > newmail# disklabel -Brw amrd0 auto > > newmail# disklabel -e amrd0 > > disklabel: ioctl DIOCGDINFO: Invalid argument > >Hmm. I should have paid more attention to the fdisk output the first >time; you already had the whole-disk label in place. > >What's the output from 'disklabel mlxd0'? newmail# disklabel amrd0 disklabel: ioctl DIOCGDINFO: Invalid argument newmail# ls -l /dev/amr* crw-r----- 1 root operator 133, 0x00010002 Feb 16 21:38 /dev/amrd0 crw-r----- 1 root operator 133, 0 Feb 16 21:36 /dev/amrd0a crw-r----- 1 root operator 133, 1 Feb 16 21:36 /dev/amrd0b crw-r----- 1 root operator 133, 2 Feb 16 21:36 /dev/amrd0c crw-r----- 1 root operator 133, 3 Feb 16 21:36 /dev/amrd0d crw-r----- 1 root operator 133, 4 Feb 16 21:36 /dev/amrd0e crw-r----- 1 root operator 133, 5 Feb 16 21:36 /dev/amrd0f crw-r----- 1 root operator 133, 6 Feb 16 21:36 /dev/amrd0g crw-r----- 1 root operator 133, 7 Feb 16 21:36 /dev/amrd0h crw-r----- 1 root operator 133, 0x00020002 Feb 16 21:36 /dev/amrd0s1 crw-r----- 1 root operator 133, 0x00030002 Feb 16 21:36 /dev/amrd0s2 crw-r----- 1 root operator 133, 0x00040002 Feb 16 21:36 /dev/amrd0s3 crw-r----- 1 root operator 133, 0x00050002 Feb 16 21:36 /dev/amrd0s4 ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 19: 6:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id D74AD37B50B for ; Wed, 16 Feb 2000 19:06:35 -0800 (PST) (envelope-from bp@butya.kz) Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by builder.freebsd.org (Postfix) with ESMTP id 9059A132ED for ; Wed, 16 Feb 2000 19:05:53 -0800 (PST) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12LHGf-0009v3-00; Thu, 17 Feb 2000 09:06:13 +0600 Date: Thu, 17 Feb 2000 09:06:13 +0600 (ALMT) From: Boris Popov To: The Hermit Hacker Cc: Dan Nelson , freebsd-current@FreeBSD.ORG Subject: Re: Mounting Netware drive onto 4.0-CURRENT ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 16 Feb 2000, The Hermit Hacker wrote: > Okay, now I'm getting somewhere, but where I don't know :( set the > ifconfig, run IPXrouted, and netstat -nr tells me a bunch of stuff about > IPX ... great, that appeasr to be up, but I get errors with ncplogin, so > obviously I'm missing something (and wihtout the search of archives, this > is the most embarressing and painful way of doing this *sigh*) ... [skip] > athena# ncplogin -S admin.acadiau.ca -U marc > Warning: no cfg files found. "admin.acadiau.ca" looks like a DNS record. If this server is a netware 5.x one, then you can use "-S admin -A admin.acadiau.ca" options and netware client will use UDP protocol. Otherwise, I'm suspect that command line should look like this: ncplogin -S admin -U marc Please note, that user "marc" should be in the bindery context. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 19:28: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 7734737B5A5; Wed, 16 Feb 2000 19:28:04 -0800 (PST) (envelope-from crossd@cs.rpi.edu) Received: from cs.rpi.edu (mumble.cs.rpi.edu [128.213.8.16]) by builder.freebsd.org (Postfix) with ESMTP id 52E6E132E3; Wed, 16 Feb 2000 19:27:24 -0800 (PST) Received: from cs.rpi.edu (crossd@odie.cs.rpi.edu [128.213.12.3]) by cs.rpi.edu (8.9.3/8.9.3) with ESMTP id WAA68483; Wed, 16 Feb 2000 22:27:54 -0500 (EST) Message-Id: <200002170327.WAA68483@cs.rpi.edu> To: Mike Smith Cc: John Baldwin , freebsd-current@FreeBSD.org, Gerald Abshez , "David E. Cross" , crossd@cs.rpi.edu Subject: Re: Thinkpad won't boot ISO image In-Reply-To: Message from Mike Smith of "Wed, 16 Feb 2000 17:04:25 PST." <200002170104.RAA02112@mass.cdrom.com> Date: Wed, 16 Feb 2000 22:27:53 -0500 From: "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mine is on 0x8b. Following some sugestions I hacked my boot/loader to look specifically at 0x8b.... it didn't work. I even went so far as to force 0x8b even though the autodetect did not work... it still didn't work. I then looked at the 1st stage boot loader as that *was* able to load boot/loader. I noticed a huge difference between the 2, with a comment in the 1st stage boot loader about a workarround for int 13h handling since not all bios's did it correctly. I then looked at boot/loader and noticed it *only* did int 13h handling. -- David Cross | email: crossd@cs.rpi.edu Acting Lab Director | NYSLP: FREEBSD Systems Administrator/Research Programmer | Web: http://www.cs.rpi.edu/~crossd Rensselaer Polytechnic Institute, | Ph: 518.276.2860 Department of Computer Science | Fax: 518.276.4033 I speak only for myself. | WinNT:Linux::Linux:FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 19:30:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id A27C937B59F for ; Wed, 16 Feb 2000 19:30:04 -0800 (PST) (envelope-from chuckr@picnic.mat.net) Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by builder.freebsd.org (Postfix) with ESMTP id 7BD90132F4 for ; Wed, 16 Feb 2000 19:29:22 -0800 (PST) Received: from localhost (chuckr@localhost [127.0.0.1]) by picnic.mat.net (8.9.3/8.9.3) with ESMTP id WAA77159; Wed, 16 Feb 2000 22:26:51 -0500 (EST) (envelope-from chuckr@picnic.mat.net) Date: Wed, 16 Feb 2000 22:26:51 -0500 (EST) From: Chuck Robey To: Joao Pedras Cc: Alfred Perlstein , freebsd-current@FreeBSD.ORG Subject: Re: freezing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Joao Pedras wrote: > eheh > > I mean dead frozen, like if I was watching at a screeshot of a X session ]:) I used to get this on a game, which was trying somehow to load a font that wasn't correct. I found it wasn't really frozen, though, because you *could* telnet in (very slow). Are you *really* sure it's frozen? Do you have a network connection you can test telnet or ping with, or maybe a serial terminal you could hook to it? > > Alfred Perlstein wrote: > > > > Do you mean dead frozen, as in needs a reboot? or frozen for a second or > > so? > > > > The first one I haven't seen recently, the second I have noticed. > > > > -Alfred > > > ^\ /^ > O O > ----------------------------------------o00-(_)-00o-------------------------- > > Common sense is the collection of prejudices acquired by age eighteen. > -- Albert Einstein > > ----------------------------------------------------------------------------- > PGP key available upon request or may be cut at > http://pedras.webvolution.net/pgpkey.html > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > ---------------------------------------------------------------------------- Chuck Robey | Interests include C & Java programming, FreeBSD, chuckr@picnic.mat.net | electronics, communications, and signal processing. New Year's Resolution: I will not sphroxify gullible people into looking up fictitious words in the dictionary. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 20:39:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 1EA7C37B559 for ; Wed, 16 Feb 2000 20:39:26 -0800 (PST) (envelope-from maekawa@rr.iij4u.or.jp) Received: from mfo01.iij.ad.jp (mfo01.iij.ad.jp [202.232.2.118]) by builder.freebsd.org (Postfix) with ESMTP id 8022E132DD for ; Wed, 16 Feb 2000 20:38:44 -0800 (PST) Received: from rr.iij4u.or.jp (rr.iij4u.or.jp [210.130.0.42]) by mfo01.iij.ad.jp (8.8.8/MFO1.3) with ESMTP id NAA01352; Thu, 17 Feb 2000 13:38:47 +0900 (JST) Received: from localhost (h091.p048.iij4u.or.jp [210.130.48.91]) by rr.iij4u.or.jp (8.8.8+2.2IIJ/4U1.1) with ESMTP id NAA14162; Thu, 17 Feb 2000 13:38:46 +0900 (JST) To: phoenix@notwise.bsdonline.org Cc: freebsd-current@freebsd.org Subject: Re: dev/umass major and minor numbers From: MAEKAWA Masahide In-Reply-To: References: X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000217133844I.maekawa@rr.iij4u.or.jp> Date: Thu, 17 Feb 2000 13:38:44 +0900 X-Dispatcher: imput version 990905(IM130) Lines: 13 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Phoenix wrote: >The current MAKEDEV script seems to be lacking the umass device. >I have searched all the docs that I know of and have been unable >to find a listing of the major and minor number assaignments, >could someone please point me in the right direction ? Not necessary. umass uses CAM system. umass driver works as a SCSI controller. --- MAEKAWA Masahide --- URL: http://kerberos.math.sci.kobe-u.ac.jp/~maekawa/ --- Kobe University (Faculty of Science, Department of Mathematics) --- Powered by BSD/OS, FreeBSD, NetBSD, OpenBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 20:44:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 3334537B559 for ; Wed, 16 Feb 2000 20:44:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 156E8132D6 for ; Wed, 16 Feb 2000 20:43:44 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA56389; Wed, 16 Feb 2000 20:44:22 -0800 (PST) (envelope-from dillon) Date: Wed, 16 Feb 2000 20:44:22 -0800 (PST) From: Matthew Dillon Message-Id: <200002170444.UAA56389@apollo.backplane.com> To: Jason Evans Cc: current@FreeBSD.ORG Subject: MAP_GUARDED patch (Re: Heads up, vm.max_proc_mmap sysctl added) References: <200002162118.NAA54097@apollo.backplane.com> <20000216141339.C18774@sturm.canonware.com> <20000216141622.E18774@sturm.canonware.com> <200002162333.PAA54729@apollo.backplane.com> <20000216155222.G18774@sturm.canonware.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :On Wed, Feb 16, 2000 at 03:33:58PM -0800, Matthew Dillon wrote: :> Is anyone interested in me doing this for the 4.0 release? It would :> help both our current threads model and the linux threads model a lot. :> I can do it in a day and it should be trivial to test, the modifications :> are actually quite minor. : :I would really like to see this change happen, and will happily make the :necessary libc_r and linuxthreads changes to use the functionality, but :we're well into the code freeze right now, which IMO makes this more :appropriate for 4.1. : :Jason I agree that this is just a tad too complex to go into 4.0 ... the MAP_GUARDED implementation is trivial, I did it in a few lines of code, but we don't want to accidently break threads at this late date and we are in a freeze, so... we'll commit this stuff after the release. I've worked up a patch to add MAP_GUARDED, which I give a reference to below. However, there are some issues: * MAP_GUARDED cannot be combined with MAP_STACK. You have to manage the 'stack' resource yourself by calling getrlimit() and checking it, then using a normal anonymous mmap. * While you can use fixed addresses with MAP_GUARDED maps, if you use downward trending address the VM system can't coalesce the VM objects, so the vm_map_entry optimization will not occur. Here is how MAP_GUARDED works: mmap(NULL, len, prot, MAP_GUARDED|MAP_ANON, -1, 0); mmap(addr, len, prot, MAP_GUARDED|MAP_ANON|MAP_FIXED, -1, 0); The returned map will be 'len' bytes long. The first and last page of this map will be guarded and accessing it will result in a bus fault (you get a seg fault if you access totally unmapped space, you get a bus fault if you access a guard page). So the offsets 0-4095 and len-4096 to len-1 will be guarded. I believe that this can be used in the current threads library but you have to pay attention to a couple of things: * First, you have to use mmap(NULL... ), allocating out of the normal mmap space rather then allocating out of the user stack space. * Second, remember that both the first AND the last page of the returned map is guarded. * Third, since we are not allocating out of the user stack space, you must call getrlimit() and manage the stack resource limit yourself. You might as well do this anyway, because MAP_STACK currently allows you to mmap() out-of-range stacks but then faults when you try to access them. Broken!!! * Lastly, as with MAP_STACK, don't even try calling madvise() on a submap of any of these maps, nor use mmap() to submap any of these maps. Both MAP_STACK and MAP_GUARDED break badly if you do that (MAP_STACK might even potentially crash the machine, but I haven't checked it deeply yet). I believe that I can fix the downward-trending optimization problem but it's more work then I have time for right now. Please check out the patch and tell me what you think. http://www.backplane.com/FreeBSD4/ http://www.backplane.com/FreeBSD4/guard-1.diff http://www.backplane.com/FreeBSD4/guard.c I also looked at the linux threads library. They do guard pages in a way that is just as broken as the way we do them, but I'm not sure if there is a kernel resource issue for them. It looks like it would be easy to patch the port to be optimal under FreeBSD. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 20:54:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 8714437B5EE for ; Wed, 16 Feb 2000 20:54:34 -0800 (PST) (envelope-from phoenix@notwise.bsdonline.org) Received: from notwise.bsdonline.org (port126.erdial.netdoor.com [208.137.151.126]) by builder.freebsd.org (Postfix) with ESMTP id 967DB132F0 for ; Wed, 16 Feb 2000 20:53:50 -0800 (PST) Received: from localhost (phoenix@localhost) by notwise.bsdonline.org (8.9.3/8.8.7) with ESMTP id WAA05126; Wed, 16 Feb 2000 22:54:33 -0600 Date: Wed, 16 Feb 2000 22:54:28 -0600 (CST) From: Phoenix To: MAEKAWA Masahide Cc: freebsd-current@FreeBSD.ORG Subject: Re: dev/umass major and minor numbers In-Reply-To: <20000217133844I.maekawa@rr.iij4u.or.jp> Message-ID: X-Secure: warning Penguin Powered. MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok sorry for the next stupid question but does that mean I need the CAM system compiled in or not? Im just switching over to freebsd and am not very familier with all the subsystems yet. this is an otherwise non-scsi box. thanks Bob Rentschler On Feb 17, The Matrix made MAEKAWA Masahide say, >Phoenix wrote: >>The current MAKEDEV script seems to be lacking the umass device. >>I have searched all the docs that I know of and have been unable >>to find a listing of the major and minor number assaignments, >>could someone please point me in the right direction ? > >Not necessary. umass uses CAM system. >umass driver works as a SCSI controller. > >--- MAEKAWA Masahide >--- URL: http://kerberos.math.sci.kobe-u.ac.jp/~maekawa/ >--- Kobe University (Faculty of Science, Department of Mathematics) >--- Powered by BSD/OS, FreeBSD, NetBSD, OpenBSD > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 21:30:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 9AAE737B628 for ; Wed, 16 Feb 2000 21:30:50 -0800 (PST) (envelope-from am@amsoft.ru) Received: from c008.sfo.cp.net (c008-h017.c008.sfo.cp.net [209.228.14.206]) by builder.freebsd.org (Postfix) with SMTP id 7B166132E1 for ; Wed, 16 Feb 2000 21:30:09 -0800 (PST) Received: (cpmta 19211 invoked from network); 16 Feb 2000 21:30:45 -0800 Received: from ip235.princeton.nj.pub-ip.psi.net (HELO amsoft.ru) (38.26.56.235) by smtp.surfree.com with SMTP; 16 Feb 2000 21:30:45 -0800 X-Sent: 17 Feb 2000 05:30:45 GMT Received: (from am@localhost) by amsoft.ru (8.9.3/8.9.3) id AAA07811 for freebsd-current@freebsd.org; Thu, 17 Feb 2000 00:33:40 -0500 (EST) (envelope-from am) From: Andrew Maltsev Message-Id: <200002170533.AAA07811@amsoft.ru> Subject: 4.0 hangs (fwd) To: freebsd-current@freebsd.org Date: Thu, 17 Feb 2000 00:31:02 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, guys! Any comments? I had to downgrade back to 3.4 yesterday.. which works absolutely without problems. If you're going to say ``it's hardware problem'' -- this was my first thought too. I tried to change memory and it did not help. Ideas? Yours, Andrew. ----- Forwarded message (env-from am) ----- >From am Sat Feb 12 16:03:39 2000 Subject: 4.0 hangs To: freebsd-current@freebsd.org Date: Sat, 12 Feb 2000 16:03:39 -0500 (EST) X-Mailer: ELM [version 2.4ME+ PL54 (25)] I upgraded to 4.0 from 3.4-stable some days ago. Upgrade (make world) itself was not smooth, /bin/sh was replaced with new version during install phase. And old 3.4 kernel can't handle some system calls of it, so everything traps with sig12. I had to first build new kernel, for which new `config' is required ans so on. But may be it is supposed to upgrade kernel first and this mess is my fault. Anyway, now I have 4.0 system and 4.0 kernel. Every 15 minutes or so it silently hangs or reboots. I upgraded kernel to today's cvs.. nothing changed. I removed linux support, P1003_1B option. Now it can work for about 1..2 hour in a row. 3.4 version worked for weeks without any problems on the same hardware. I cannot see any relations of halts with what I do. It appears, that it happens at the moments of active swapping.. But once it halted while I read the mail and the system was idle. I would like to dig in this problem. Any way to see where it hangs (working under X)? I would really appreciate any help.. My dmesg: Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Sat Feb 12 10:52:21 EST 2000 root@croco.amsoft.ru:/usr/var/SRC/FreeBSD/r4/src/sys/compile/Croco-bare Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (467.73-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x665 Stepping = 5 Features=0x183f9ff real memory = 67108864 (65536K bytes) avail memory = 62255104 (60796K bytes) Preloaded elf kernel "kernel" at 0xc02b5000. Preloaded splash_image_data "/boot/splash.bmp" at 0xc02b509c. Preloaded elf module "splash_bmp.ko" at 0xc02b50ec. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: port 0xd000-0xd0ff mem 0xe5000000-0xe5000fff,0xe6000000-0xe6ffffff irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 chip1: port 0x5000-0x500f at device 7.3 on pci0 pcm0: port 0xe400-0xe43f irq 10 at device 17.0 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ad0: 8693MB [17662/16/63] at ata0-master using UDMA33 acd0: DVD-ROM at ata0-slave using UDMA33 Mounting root from ufs:/dev/wd0s2a WARNING: / was not properly dismounted ----- End of forwarded message (env-from am) ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 22: 2:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id B5D5037B564 for ; Wed, 16 Feb 2000 22:02:42 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by builder.freebsd.org (Postfix) with ESMTP id 91AE8132E7 for ; Wed, 16 Feb 2000 22:02:01 -0800 (PST) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA56806; Wed, 16 Feb 2000 22:02:40 -0800 (PST) (envelope-from dillon) Date: Wed, 16 Feb 2000 22:02:40 -0800 (PST) From: Matthew Dillon Message-Id: <200002170602.WAA56806@apollo.backplane.com> To: Jason Evans , current@FreeBSD.ORG Subject: Re: MAP_GUARDED patch (Re: Heads up, vm.max_proc_mmap sysctl added) References: <200002162118.NAA54097@apollo.backplane.com> <20000216141339.C18774@sturm.canonware.com> <20000216141622.E18774@sturm.canonware.com> <200002162333.PAA54729@apollo.backplane.com> <20000216155222.G18774@sturm.canonware.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : I believe that I can fix the downward-trending optimization problem : but it's more work then I have time for right now. Please check out : the patch and tell me what you think. I take it back. It turns out that fixing the downward-trending h optimization is trivial. Well, trivial for me anyway. I have to rewrite vm_map_insert() and vm_object_coalesce() but they needed cleaning up anyway. It turns out that for anonymous objects we can use the vm_map_entry->offset field to create a trivial object coalescing case. By setting the vm_map_entry->offset field to be the same as the virtual start address, adjacent entries in memory wind up being adjacent in the object as well. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Wed Feb 16 23:50:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 8172337B53B for ; Wed, 16 Feb 2000 23:50:29 -0800 (PST) (envelope-from uucp@gruft.de) Received: from gruft.de (gate.obh.snafu.de [195.21.6.17]) by builder.freebsd.org (Postfix) with ESMTP id 85C74132E7 for ; Wed, 16 Feb 2000 23:49:42 -0800 (PST) Received: from localhost (1662 bytes) by gruft.de via rmail with P:stdio/R:inet_hosts/T:smtp (sender: ) (ident using unix) id for ; Thu, 17 Feb 2000 08:49:09 +0100 (CET) (Smail-3.2.0.106 1999-Mar-31 #1 built 1999-May-21) Received: from sauerbruch.evk-koeln.de(localhost.evk-koeln.de[127.0.0.1]) (1263 bytes) by sauerbruch.evk-koeln.de via sendmail with P:esmtp/R:smart_host/T:uux (sender: ) id for ; Thu, 17 Feb 2000 08:42:28 +0100 (CET) (Smail-3.2.0.107 1999-Sep-8 #1 built 2000-Jan-25) Message-Id: Date: Thu, 17 Feb 2000 08:42:27 +0100 (CET) From: Oliver Brandmueller Subject: Re: freezing To: Joao Pedras Cc: freebsd-current@FreeBSD.ORG In-Reply-To: MIME-Version: 1.0 Content-Type: TEXT/plain; CHARSET=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, On 17 Feb, Joao Pedras wrote: > While making -j 4 buildworld and moving a netscape window, everything frozen. > Happens often if do other things while cpu and disk are very active. > > Happens quite often. > > Anyone else has noticed this ? I had that problem three times: Once, when I tried using a K6-3 on my Gigabyte GA5-AX Motherboard. They just weren't working together, when I changed back to a K6-2 (both tried at 350 MHz) the problems disappeared. The K6-3 works fine now in another machine (MSI Mainboard or something like that). Another time something like that happened, when my cooler failed. On one of my old Suns I had a similar problem, when one of the SIMMs was damaged. So, get on and check 'ya hardware. Bye, Oliver To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 0: 1:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 4A4B637B53B for ; Thu, 17 Feb 2000 00:01:41 -0800 (PST) (envelope-from maekawa@rr.iij4u.or.jp) Received: from mfo00.iij.ad.jp (mfo00.iij.ad.jp [202.232.2.117]) by builder.freebsd.org (Postfix) with ESMTP id A2098132E2 for ; Thu, 17 Feb 2000 00:00:58 -0800 (PST) Received: from rr.iij4u.or.jp (rr.iij4u.or.jp [210.130.0.42]) by mfo00.iij.ad.jp (8.8.8/MFO1.3) with ESMTP id RAA04825; Thu, 17 Feb 2000 17:01:36 +0900 (JST) Received: from localhost (h074.p048.iij4u.or.jp [210.130.48.74]) by rr.iij4u.or.jp (8.8.8+2.2IIJ/4U1.1) with ESMTP id RAA20553; Thu, 17 Feb 2000 17:01:34 +0900 (JST) To: phoenix@notwise.bsdonline.org Cc: freebsd-current@FreeBSD.ORG Subject: Re: dev/umass major and minor numbers From: MAEKAWA Masahide In-Reply-To: References: <20000217133844I.maekawa@rr.iij4u.or.jp> X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000217170132V.maekawa@rr.iij4u.or.jp> Date: Thu, 17 Feb 2000 17:01:32 +0900 X-Dispatcher: imput version 990905(IM130) Lines: 14 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Phoenix wrote: >Ok sorry for the next stupid question but does that mean >I need the CAM system compiled in or not? Im just switching over >to freebsd and am not very familier with all the subsystems yet. >this is an otherwise non-scsi box. If you want to use USB Mass storage devices, you must compile CAM system, of course. You just write umass, scbus and da in your kernel configuration file. --- MAEKAWA Masahide --- URL: http://kerberos.math.sci.kobe-u.ac.jp/~maekawa/ --- Kobe University (Faculty of Science, Department of Mathematics) --- Powered by BSD/OS, FreeBSD, NetBSD, OpenBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 0:20:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from builder.freebsd.org (builder.FreeBSD.ORG [204.216.27.24]) by hub.freebsd.org (Postfix) with ESMTP id 1611137B622 for ; Thu, 17 Feb 2000 00:20:19 -0800 (PST) (envelope-from maxim@amur.cbr.ru) Received: from proxy.cbr.amur.ru (proxy.cbr.amur.ru [195.151.156.197]) by builder.freebsd.org (Postfix) with ESMTP id ABF3D132E8 for ; Thu, 17 Feb 2000 00:19:30 -0800 (PST) Received: (from uucp@localhost) by proxy.cbr.amur.ru (8.9.3/8.9.3) with UUCP id RAA16320 for freebsd-current@freebsd.org; Thu, 17 Feb 2000 17:17:16 +0900 (YS) Received: from stone.amur.cbr.ru (stone.amur.cbr.ru [10.82.64.20]) by grizzly.amur.cbr.ru (8.9.3/8.9.3) with ESMTP id RAA25332 for ; Thu, 17 Feb 2000 17:16:02 +0900 (YS) Received: from localhost (localhost [127.0.0.1]) by stone.amur.cbr.ru (Postfix) with ESMTP id 86E7620DC for ; Thu, 17 Feb 2000 17:16:01 +0900 (YAKT) Date: Thu, 17 Feb 2000 17:16:00 +0900 (YAKT) From: Maxim Konovalov To: freebsd-current@freebsd.org Subject: ctm and current q Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, I've got a 4.0-20000210-CURRENT snapshot and decided to try CTM. I've - read handbook chapter about using CTM - subscribed to ctm-cur, ctm-port, ctm-announce - downloaded all src-cur.42* deltas from ftp://ftp.freebsd.org/pub/FreeBSD/development/CTM/src-cur/ - rm -rf /usr/src/* - applied deltas and got a new src tree - read /usr/src/UPDATING - built and installed world - mergemastered /etc - cd /dev && sh MAKEDEV all - built and installed kernel - rebooted When I try: # pstat pstat: undefined symbol: _numvnodes # top top: nlist failed # ps works quite right. It seems like kernel and world are not sync. Where did i make a mistake(s)? Thank you for your help, Maxim Konovalov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 0:46: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from rah.star-gate.com (216-200-29-190.snj0.flashcom.net [216.200.29.194]) by hub.freebsd.org (Postfix) with ESMTP id 5F86637B674 for ; Thu, 17 Feb 2000 00:45:42 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.9.3/8.9.3) with ESMTP id OAA33777 for ; Sun, 13 Feb 2000 14:55:57 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <200002132255.OAA33777@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: current@FreeBSD.ORG Subject: make world Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 13 Feb 2000 14:55:57 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsuped last nite and got the following make world error: touch _stamp.extraobjs (cd /usr/src/share/doc/papers/contents; groff -mtty-c har -Tascii -ms -o1- /usr/src/share/doc/papers/conten ts/contents.ms) | gzip -cn > contents.ascii.gz ===> share/examples ===> share/isdn uudecode < /usr/src/share/isdn/0.al.uu uudecode < /usr/src/share/isdn/1.al.uu uudecode < /usr/src/share/isdn/2.al.uu uudecode < /usr/src/share/isdn/3.al.uu uudecode < /usr/src/share/isdn/4.al.uu uudecode < /usr/src/share/isdn/5.al.uu uudecode < /usr/src/share/isdn/6.al.uu uudecode < /usr/src/share/isdn/7.al.uu uudecode < /usr/src/share/isdn/8.al.uu uudecode < /usr/src/share/isdn/9.al.uu uudecode < /usr/src/share/isdn/beep.al.uu uudecode < /usr/src/share/isdn/msg.al.uu uudecode: input file: stdin encoded file: msg.al character out of range: [33-96] *** Error code 1 Stop in /usr/src/share/isdn. *** Error code 1 Stop in /usr/src/share. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. *** Error code 1 Stop in /usr/src. -- Amancio Hasty hasty@rah.star-gate.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 0:47:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 82D1C37B671 for ; Thu, 17 Feb 2000 00:47:50 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id BAA00651; Thu, 17 Feb 2000 01:16:00 -0800 (PST) Date: Thu, 17 Feb 2000 01:16:00 -0800 From: Alfred Perlstein To: Andrew Maltsev Cc: freebsd-current@FreeBSD.ORG Subject: Re: 4.0 hangs (fwd) Message-ID: <20000217011600.N3509@fw.wintelcom.net> References: <200002170533.AAA07811@amsoft.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002170533.AAA07811@amsoft.ru>; from am@amsoft.ru on Thu, Feb 17, 2000 at 12:31:02AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Andrew Maltsev [000216 22:00] wrote: > Hi, guys! > > Any comments? I had to downgrade back to 3.4 yesterday.. which works > absolutely without problems. If you're going to say ``it's hardware > problem'' -- this was my first thought too. I tried to change memory and > it did not help. Ideas? If you have a serial console available (all you need is a second computer with a terminal program and a null modem adapter) then you can boot the system with a serial console and see what the panic message is. You could also enable crashdumps and provide a traceback, see: http://www.freebsd.org/handbook/kerneldebug.html -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 1: 5:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail5.fujitsu.co.jp (fgwmail5.fujitsu.co.jp [192.51.44.35]) by hub.freebsd.org (Postfix) with ESMTP id EBDC637B68C for ; Thu, 17 Feb 2000 01:05:39 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail5.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id SAA05220; Thu, 17 Feb 2000 18:05:35 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from chisato.nd.net.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id SAA16069; Thu, 17 Feb 2000 18:05:34 +0900 (JST) Received: from localhost (dhcp25.pkt.ts.fujitsu.co.jp [10.36.204.25]) by chisato.nd.net.fujitsu.co.jp (8.8.5+2.7Wbeta5/3.3W8chisato-970826) with ESMTP id SAA25066; Thu, 17 Feb 2000 18:05:33 +0900 (JST) To: ache@nagual.pp.ru Cc: saxonww@ufl.edu, current@FreeBSD.ORG Subject: Re: Broken FTP In-Reply-To: <20000216101731.A27147@nagual.pp.ru> References: <20000216155124R.shin@nd.net.fujitsu.co.jp> <20000216101731.A27147@nagual.pp.ru> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000217180622H.shin@nd.net.fujitsu.co.jp> Date: Thu, 17 Feb 2000 18:06:22 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 12 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > But maybe it is better to print out the first error, as the fact? > > I have nothing against EPSV itself, I am against additional verbosity and > performance degradation since it is tried before _each_ command. OK I'll change not to try it once it fails. But trying to do that I noticed that suppressing the first error message is not easy, because it is sent by server. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 1:34:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0A3DB37B699; Thu, 17 Feb 2000 01:34:51 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id BAA47953; Thu, 17 Feb 2000 01:34:20 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Thu, 17 Feb 2000 01:34:20 -0800 (PST) From: Kris Kennaway To: Amancio Hasty Cc: current@FreeBSD.ORG Subject: Re: make world In-Reply-To: <200002132255.OAA33777@rah.star-gate.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 13 Feb 2000, Amancio Hasty wrote: > uudecode < /usr/src/share/isdn/msg.al.uu > uudecode: > input file: stdin > encoded file: msg.al > character out of range: [33-96] > *** Error code 1 Looks like corruption. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 1:44:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.surf1.de (mail.Surf1.de [194.25.165.21]) by hub.freebsd.org (Postfix) with ESMTP id EB43C37B699 for ; Thu, 17 Feb 2000 01:44:09 -0800 (PST) (envelope-from alex@cichlids.com) Received: from cichlids.com (pC19F546B.dip0.t-ipconnect.de [193.159.84.107]) by mail.surf1.de (8.9.3/8.9.3) with ESMTP id KAA24964 for ; Thu, 17 Feb 2000 10:44:36 +0100 Received: from cichlids.cichlids.com (cichlids.cichlids.com [192.168.0.10]) by cichlids.com (Postfix) with ESMTP id 89648AC26 for ; Thu, 17 Feb 2000 10:45:17 +0100 (CET) Received: (from alex@localhost) by cichlids.cichlids.com (8.9.3/8.9.3) id KAA04618 for current@freebsd.org; Thu, 17 Feb 2000 10:46:31 +0100 (CET) (envelope-from alex) Date: Thu, 17 Feb 2000 10:46:31 +0100 From: Alexander Langer To: current@freebsd.org Subject: how to write kernel modules with newbus? Message-ID: <20000217104631.B4554@cichlids.cichlids.com> Mail-Followup-To: current@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i 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-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I wanted to write a device driver as kernelmodule, using newbus. Since there is almost no documentation, I've read some source. It seems, that I have to do something like: static device_method_t zivads_methods[] = { /* interface */ DEVMETHOD(device_identify, zivads_identify), DEVMETHOD(device_probe, zivads_probe), DEVMETHOD(device_attach, zivads_attach), { 0, 0 } }; and to use zivads_* functions then. But this fails because I don't know the right include files - DEVMETHOD is expanded to unknown funtions What I'm searching for is some info on how to do this. Can anyone point me to a SIMPLE device driver module, that does this? Or any documentation? Or summarize how exactly stuff is done, e.g. which include files are needed for the above? It's very hard to find this things out when starting from scratch :) When I will have got this working, I would even write a small manual/introduction, that can be used as an example/manual for other people, e.g. third party vendors, that want to write drivers for newbus. TIA Alex -- I need a new ~/.sig. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 1:53:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.hcisp.net (StarGate.hcisp.net [208.60.89.1]) by hub.freebsd.org (Postfix) with SMTP id 64D3237B678 for ; Thu, 17 Feb 2000 01:53:24 -0800 (PST) (envelope-from tim@mysql.com) Received: (qmail 7728 invoked from network); 17 Feb 2000 09:58:37 -0000 Received: from modem2.hcsip.net (HELO threads.polyesthetic.msg) (208.60.89.68) by stargate.hcisp.net with SMTP; 17 Feb 2000 09:58:37 -0000 Received: (qmail 4830 invoked by uid 1001); 17 Feb 2000 09:52:27 -0000 From: "Thimble Smith" Date: Thu, 17 Feb 2000 04:52:27 -0500 To: current@freebsd.org Subject: pthread.h and unistd.h Message-ID: <20000217045227.S2611@threads.polyesthetic.msg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I recently updated from -stable to -current. I notice now that pthread.h relies on #defines that are in unistd.h; so in order to use pthread_attr_setscope you have to include unistd.h before pthread.h. Is this standard behaviour? I'm working with MySQL, and unistd.h is included after pthread.h; should I have that code changed, or should FreeBSD somehow compensate for this? Thanks, Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 2: 6:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from bluebottle.calcaphon.com (calcaphon.demon.co.uk [193.237.19.5]) by hub.freebsd.org (Postfix) with ESMTP id BF26837B672 for ; Thu, 17 Feb 2000 02:06:38 -0800 (PST) (envelope-from n_hibma@calcaphon.com) Received: from henny.webweaving.org (dhcp36.calcaphon.com [10.0.1.36]) by bluebottle.calcaphon.com (8.9.3/8.9.1) with ESMTP id KAA01159; Thu, 17 Feb 2000 10:06:33 GMT (envelope-from n_hibma@calcaphon.com) Received: from localhost (localhost [127.0.0.1]) by henny.webweaving.org (8.9.3/8.9.3) with ESMTP id KAA01201; Thu, 17 Feb 2000 10:03:46 GMT (envelope-from n_hibma@calcaphon.com) Date: Thu, 17 Feb 2000 10:03:46 +0000 (GMT) From: Nick Hibma X-Sender: n_hibma@localhost Reply-To: Nick Hibma To: Phoenix Cc: MAEKAWA Masahide , freebsd-current@FreeBSD.org Subject: Re: dev/umass major and minor numbers In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Ok sorry for the next stupid question but does that mean > I need the CAM system compiled in or not? Im just switching over > to freebsd and am not very familier with all the subsystems yet. > this is an otherwise non-scsi box. Yes you will need da and scbus compiled into the kernel. And either you use the usbd.conf file to automatically execute 'camcontrol rescan 0' or you do it by hand when the the drive has been connected. Nick > > thanks > Bob Rentschler > > > On Feb 17, The Matrix made MAEKAWA Masahide say, > > >Phoenix wrote: > >>The current MAKEDEV script seems to be lacking the umass device. > >>I have searched all the docs that I know of and have been unable > >>to find a listing of the major and minor number assaignments, > >>could someone please point me in the right direction ? > > > >Not necessary. umass uses CAM system. > >umass driver works as a SCSI controller. > > > >--- MAEKAWA Masahide > >--- URL: http://kerberos.math.sci.kobe-u.ac.jp/~maekawa/ > >--- Kobe University (Faculty of Science, Department of Mathematics) > >--- Powered by BSD/OS, FreeBSD, NetBSD, OpenBSD > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org > >with "unsubscribe freebsd-current" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- n_hibma@webweaving.org n_hibma@freebsd.org USB project http://www.etla.net/~n_hibma/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 2: 9:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from logger.gamma.ru (logger.gamma.ru [194.186.254.23]) by hub.freebsd.org (Postfix) with ESMTP id 04D9937B68B for ; Thu, 17 Feb 2000 02:09:56 -0800 (PST) (envelope-from ivt@logger.gamma.ru) Received: (from ivt@localhost) by logger.gamma.ru (8.9.3/8.9.3) id NAA75066 for freebsd-current@freebsd.org; Thu, 17 Feb 2000 13:09:52 +0300 (MSK) From: Igor Timkin Message-Id: <200002171009.NAA75066@logger.gamma.ru> Subject: dump of vinum disks To: freebsd-current@freebsd.org Date: Thu, 17 Feb 2000 13:09:52 +0300 (MSK) X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yesterday current: ivt@newsfeed:/news/etc:2:770>uname -a FreeBSD newsfeed.gamma.ru 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Wed Feb 16 03:00:26 MSK 2000 ivt@newsfeed.gamma.ru:/usr/src/sys/compile/NEWSFEED i386 ivt@newsfeed:/news/etc:2:771>dump 0f /dev/null /news DUMP: Date of this level 0 dump: Thu Feb 17 12:24:34 2000 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/vinum/rraid0 (/news) to /dev/null DUMP: Cannot open /dev/vinum/rraid0 vt@newsfeed:/news/etc:2:772>dump 0f /dev/null /dev/vinum/raid0 DUMP: Date of this level 0 dump: Thu Feb 17 12:25:10 2000 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/vinum/rraid0 (/news) to /dev/null DUMP: Cannot open /dev/vinum/rraid0 vt@newsfeed:/news/etc:2:773>ls -ltr /dev/vinum total 4 drwxr-xr-x 2 root wheel 512 Feb 16 06:13 drive drwxr-xr-x 2 root wheel 512 Feb 16 06:13 plex drwxr-xr-x 2 root wheel 512 Feb 16 06:13 sd drwxr-xr-x 3 root wheel 512 Feb 16 06:13 vol crw------- 1 root wheel 91, 0x40000001 Feb 16 06:13 Control crw------- 1 root wheel 91, 0x40000002 Feb 16 06:13 control crw------- 1 root wheel 91, 0x40000000 Feb 16 06:13 controld crw-r----- 1 root operator 91, 0 Feb 16 06:14 raid0 (vinum create vinum's disks with ``wheel'' group, so i made chgrp operator raid0). Just moment solution is (cd /dev/vinum; ln raid0 rraid0). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 2:12:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.hcisp.net (StarGate.hcisp.net [208.60.89.1]) by hub.freebsd.org (Postfix) with SMTP id 79EFF37B586 for ; Thu, 17 Feb 2000 02:12:34 -0800 (PST) (envelope-from tim@mysql.com) Received: (qmail 7756 invoked from network); 17 Feb 2000 10:17:56 -0000 Received: from modem2.hcsip.net (HELO threads.polyesthetic.msg) (208.60.89.68) by stargate.hcisp.net with SMTP; 17 Feb 2000 10:17:56 -0000 Received: (qmail 4959 invoked by uid 1001); 17 Feb 2000 10:11:51 -0000 From: "Thimble Smith" Date: Thu, 17 Feb 2000 05:11:51 -0500 To: current@freebsd.org Subject: ViBRA16X and /dev/dsp Message-ID: <20000217051151.T2611@threads.polyesthetic.msg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi. I'm still trying to figure out why /dev/dsp isn't working with my ViBRA16X card. I wrote a little program to test the device. The trouble is, I don't know what I'm doing and have not found much in the way of documentation. I'm hoping someone can give me a hint, so I can figure out what's going wrong. If I'm way off topic and just annoying everyone, please let me know and I'll just shut up until either I learn more or someone else deals with it. :) Being optimistic, here's my program: #include #include #include #include #include #include #include #define BUFSZ 1024 int main() { int audio_fd; unsigned char audio_buf[BUFSZ]; int format = AFMT_U8; int speed = 8000; ssize_t written; if ((audio_fd = open("/dev/dsp", O_WRONLY, 0)) == -1) { perror("/dev/dsp"); exit(EXIT_FAILURE); } if (ioctl(audio_fd, SNDCTL_DSP_SETFMT, &format) == -1) { perror("SETFMT"); exit(EXIT_FAILURE); } if (format != AFMT_U8) { fprintf(stderr, "AFMT_U8 is unsupported (try 0x%02x)\n", format); exit(EXIT_FAILURE); } if (ioctl(audio_fd, SNDCTL_DSP_SPEED, &speed) == -1) { perror("SPEED"); exit(EXIT_FAILURE); } if (speed != 8000) fprintf(stderr, "warning: speed == %d\n", speed); /* let's give this a shot! */ /* OK, so this doesn't seem to be doing what I want - I'm trying to just play some tone - anything - to test if the thing is working or not. I was hoping this simple thing might be close enough to a sound file that it would play something. But obviously I'm being naive. What should I put into the buffer to get it to play? Do I need to write the buffer many times to the device in order to hear anything? */ memset(audio_buf, 0xaa, BUFSZ); fprintf(stderr, "getting ready to write to the device\n"); written = write(audio_fd, audio_buf, BUFSZ); if (written != BUFSZ) fprintf(stderr, "only wrote %d of %d bytes\n", written, BUFSZ); fprintf(stderr, "getting ready to close the device\n"); close(audio_fd); fprintf(stderr, "Done.\n"); return EXIT_SUCCESS; } When I run the program, I hear a pop; just as if I'd done $ echo "foo" > /dev/dsp; but I hear nothing that sounds like a tone. There are no warnings printed, though. Thanks for any help, Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 4: 2:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 9067937B6B0; Thu, 17 Feb 2000 04:02:51 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id HAA24651; Thu, 17 Feb 2000 07:02:40 -0500 (EST) Date: Thu, 17 Feb 2000 07:02:39 -0500 (EST) From: Daniel Eischen To: Thimble Smith Cc: current@FreeBSD.ORG, jasone@FreeBSD.ORG Subject: Re: pthread.h and unistd.h In-Reply-To: <20000217045227.S2611@threads.polyesthetic.msg> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Thimble Smith wrote: > Hi. I recently updated from -stable to -current. I notice now that > pthread.h relies on #defines that are in unistd.h; so in order to use > pthread_attr_setscope you have to include unistd.h before pthread.h. > > Is this standard behaviour? I'm working with MySQL, and unistd.h is > included after pthread.h; should I have that code changed, or should > FreeBSD somehow compensate for this? I've read the POSIX spec, and it looks like pthread.h should include unistd.h so that the #defines you refer to are properly defined. Solaris 2.5.1 pthread.h doesn't include directly, but does include which includes . I think our pthread.h should include , but don't know if it should be directly included or not. Jason, what do you think? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 4: 5:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4060637B678 for ; Thu, 17 Feb 2000 04:05:56 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id EAA58472; Thu, 17 Feb 2000 04:05:55 -0800 (PST) (envelope-from dillon) Date: Thu, 17 Feb 2000 04:05:55 -0800 (PST) From: Matthew Dillon Message-Id: <200002171205.EAA58472@apollo.backplane.com> To: Jason Evans , current@FreeBSD.ORG Subject: tentitive complete patch for MAP_GUARDED available Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is *NOT* a commit candidate yet (and definitely not until after release). It's only tentitive... I had to rip up some core pieces to get the kernel to properly optimize vm_map_entry structures for the downward-generated-stacks. http://www.backplane.com/FreeBSD4/ http://www.backplane.com/FreeBSD4/guard-2.diff http://www.backplane.com/FreeBSD4/guard2.c With this patch it should be possible to trivially modify the threads code. You pretty much keep what you have except use MAP_GUARDED|MAP_STACK, and deal with skipping over the guard pages. Resource limits are still an issue. It turns out that the MAP_STACK code does not deal with the stack resource limit well at all -- sometimes it catches it, sometimes it doesn't. At the moment MAP_GUARDED doesn't even try but that does not prevent you from using the stack memory areas to do your mmaps. You can use MAP_GUARDED|MAP_STACK now. This is effectively MAP_GUARDED but will cause the mmap() to fail if you specify a fixed address that already contains mappings (which is what you want, I think). i.e. that is what MAP_STACK semantics normally do - return a failure on a conflict. There are probably bugs, much more testing is necessary. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 7:12:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id F08A937B758; Thu, 17 Feb 2000 07:12:05 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id CAA27623; Fri, 18 Feb 2000 02:15:11 +1100 Date: Fri, 18 Feb 2000 02:11:40 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Daniel Eischen Cc: Thimble Smith , current@FreeBSD.ORG, jasone@FreeBSD.ORG Subject: Re: pthread.h and unistd.h In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Daniel Eischen wrote: > On Thu, 17 Feb 2000, Thimble Smith wrote: > > > Hi. I recently updated from -stable to -current. I notice now that > > pthread.h relies on #defines that are in unistd.h; so in order to use > > pthread_attr_setscope you have to include unistd.h before pthread.h. > > > > Is this standard behaviour? I'm working with MySQL, and unistd.h is > > included after pthread.h; should I have that code changed, or should > > FreeBSD somehow compensate for this? > > I've read the POSIX spec, and it looks like pthread.h should include > unistd.h so that the #defines you refer to are properly defined. It can't include or even , at least in POSX.1-1996, because even the latter defines names that are not reserved for . E.g., defines SEEK_SET, but the only non-implementation reserved for are ones beginning with pthread_ or PTHREAD_, or ending with _t. However, including wouldn't add much to the existing namespace violation from including , , , and . > Solaris 2.5.1 pthread.h doesn't include directly, but does > include which includes . This seems to be a bug Solaris 2.5.1. Our avoids including by including to get more fundamental feature test macros for the visibility of the POSIX.1b extensions. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 7:13:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 20F2B37B760 for ; Thu, 17 Feb 2000 07:13:30 -0800 (PST) (envelope-from bde@zeta.org.au) Received: (qmail 29727 invoked from network); 17 Feb 2000 15:13:26 -0000 Received: from bde.zeta.org.au (203.2.228.102) by gidora.zeta.org.au with SMTP; 17 Feb 2000 15:13:26 -0000 Date: Fri, 18 Feb 2000 02:13:24 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Maxim Konovalov Cc: freebsd-current@FreeBSD.ORG Subject: Re: ctm and current q In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Maxim Konovalov wrote: > > Hello, > > I've got a 4.0-20000210-CURRENT snapshot and decided to try CTM. > I've > - read handbook chapter about using CTM > - subscribed to ctm-cur, ctm-port, ctm-announce > - downloaded all src-cur.42* deltas from > ftp://ftp.freebsd.org/pub/FreeBSD/development/CTM/src-cur/ > - rm -rf /usr/src/* > - applied deltas and got a new src tree > - read /usr/src/UPDATING > - built and installed world > - mergemastered /etc > - cd /dev && sh MAKEDEV all > - built and installed kernel > - rebooted > > When I try: > > # pstat > pstat: undefined symbol: _numvnodes > # top > top: nlist failed > # > > ps works quite right. It seems like kernel and world are not sync. Where > did i make a mistake(s)? The boot blocks must be updated if you are starting from an old (2.2?) version of FreeBSD. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 7:36:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from noname.cbr.amur.ru (noname.cbr.amur.ru [195.151.156.206]) by hub.freebsd.org (Postfix) with ESMTP id 17ED437B782 for ; Thu, 17 Feb 2000 07:36:26 -0800 (PST) (envelope-from maxim@amur.cbr.ru) Received: from localhost (localhost [127.0.0.1]) by noname.cbr.amur.ru (8.9.3/8.9.3) with ESMTP id AAA01117; Fri, 18 Feb 2000 00:35:54 +0900 (YAKT) (envelope-from maxim@amur.cbr.ru) Date: Fri, 18 Feb 2000 00:35:54 +0900 (YAKT) From: Maxim Konovalov X-Sender: maxim@noname.cbr.amur.ru To: Bruce Evans Cc: freebsd-current@FreeBSD.ORG Subject: Re: ctm and current q In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Bruce Evans wrote: > > On Thu, 17 Feb 2000, Maxim Konovalov wrote: > > > > Hello, > > > > I've got a 4.0-20000210-CURRENT snapshot and decided to try CTM. > > I've [...] > > ps works quite right. It seems like kernel and world are not sync. Where > > did i make a mistake(s)? > > The boot blocks must be updated if you are starting from an old (2.2?) > version of FreeBSD. I've just got a installed 4.0-20000210-CURRENT snapshot and decided to try CTM :-) > Bruce > Maxim Konovalov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 7:38:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id EF22337B734; Thu, 17 Feb 2000 07:38:12 -0800 (PST) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-c1s1-37.mfi.net [209.26.94.38]) by pawn.primelocation.net (Postfix) with ESMTP id 0B60E9B19; Thu, 17 Feb 2000 10:38:11 -0500 (EST) Date: Thu, 17 Feb 2000 10:38:55 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Dan Moschuk Cc: freebsd-current@freebsd.org Subject: Re: cvs commit: src/usr.sbin/pkg_install/delete main.c src/usr.sbin/pkg_install/info main.c In-Reply-To: <200001180145.RAA50302@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 17 Jan 2000, Dan Moschuk wrote: > dan 2000/01/17 17:45:54 PST > > Modified files: > usr.sbin/pkg_install/delete main.c > usr.sbin/pkg_install/info main.c > Log: > Fix a bug in previous commit where pkg_{delete,info} foo-1.0/ would segfault. > > Noticed first by: kris > Is it just me, or does: 'pkg_delete foo-1.0/' now just spin in the while() loop around line 92 of src/usr.sbin/pkg_install/delete/main.c ? ----- 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 7:39:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 6919237B751; Thu, 17 Feb 2000 07:39:35 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id KAA94708; Thu, 17 Feb 2000 10:39:34 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000217103709.01c2f7b0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 17 Feb 2000 10:37:09 -0500 To: Mike Smith From: Mike Tancsa Subject: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) Cc: current@FreeBSD.ORG In-Reply-To: <200002170304.TAA03502@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 07:04 PM 2/16/00 -0800, Mike Smith wrote: >> At 05:15 PM 2/16/2000 -0800, Mike Smith wrote: >> > > Hi, >> > > I have been trying to get a PERC 2 (aka MegaRAID 466) working with >> > > Current. The box worked fine with the 428, but seems to barf with only the >> > > controller swapped. >> > >> >I don't think the two controllers share on-disk configuration formats; >> >you'll probably need to re-initialise the array (I could be wrong about >> >that). >> >> Yes, I did that. I blew away the old config, created a new set, and >> initialized the array. >> >> >> You probably don't want to do that with a valid slice table installed; >> >the slice code does silly things. Try nuking it first: >> > >> ># dd if=/dev/zero of=/dev/amrd0 count=16 >> >> newmail# dd if=/dev/zero of=/dev/amrd0 count=16 >> 16+0 records in >> 16+0 records out >> 8192 bytes transferred in 0.006427 secs (1274613 bytes/sec) >> newmail# disklabel -Brw amrd0 auto >> newmail# disklabel -e amrd0 >> disklabel: ioctl DIOCGDINFO: Invalid argument > >Hmm. I should have paid more attention to the fdisk output the first >time; you already had the whole-disk label in place. > >What's the output from 'disklabel mlxd0'? > OK, I took a chance and flashed the card's BIOS to the latest from the AMI site.... I had been suspecting BIOS, as the readme.txt mentioned problems with newer motherboards. Lo and Behold, it seems to have done the trick amr0: mem 0xe9000000-0xe93fffff irq 11 at device 12.1 on pci0 amr0: firmware GH6D bios 1.43 32MB memory amrd0: on amr0 amrd0: 17522MB (35885056 sectors) RAID 5 (optimal) As I mentioned, the card came as a Dell unit. I tried the latest BIOS from Dell, but that was a year old. The BIOS from megaraid.com 1.43, which is in there now *seems* to work so far.... At least I can now get a disklable on the drive and newfs the drive newmail# disklabel amrd0 # /dev/ramrd0c: type: SCSI disk: amnesiac label: flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 2233 sectors/unit: 35885056 rpm: 7200 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] c: 35885056 0 4.2BSD 1024 8192 16 # (Cyl. 0 - 2233*) ------------------------------------------------------------------------ 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 7:44:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat197.96.mpoweredpc.net [142.177.197.96]) by hub.freebsd.org (Postfix) with ESMTP id 44F2A37B792 for ; Thu, 17 Feb 2000 07:44:37 -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 LAA27160; Thu, 17 Feb 2000 11:44:10 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 17 Feb 2000 11:44:10 -0400 (AST) From: The Hermit Hacker To: Boris Popov Cc: Dan Nelson , freebsd-current@FreeBSD.ORG Subject: Re: Mounting Netware drive onto 4.0-CURRENT ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Boris Popov wrote: > On Wed, 16 Feb 2000, The Hermit Hacker wrote: > > > Okay, now I'm getting somewhere, but where I don't know :( set the > > ifconfig, run IPXrouted, and netstat -nr tells me a bunch of stuff about > > IPX ... great, that appeasr to be up, but I get errors with ncplogin, so > > obviously I'm missing something (and wihtout the search of archives, this > > is the most embarressing and painful way of doing this *sigh*) ... > [skip] > > > athena# ncplogin -S admin.acadiau.ca -U marc > > Warning: no cfg files found. > > "admin.acadiau.ca" looks like a DNS record. If this server is a > netware 5.x one, then you can use "-S admin -A admin.acadiau.ca" options > and netware client will use UDP protocol. Otherwise, I'm suspect that > command line should look like this: > > ncplogin -S admin -U marc > > Please note, that user "marc" should be in the bindery context. Okay, tried that, still no go: athena:/home/kerri> ncplogin -S admin -U .kerri.admin.acadia Warning: no cfg files found. Netware password: ncplogin: Could not login to server ADMIN: nwerr = 89f0 athena:/home/kerri> Anyone know what 'nwerr = 89f0' is/means? This is an account we know is active and working, as we just switched her off of Netware recently ... 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 8:22:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id C3ABA37B78B; Thu, 17 Feb 2000 08:22:03 -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.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id QAA18213; Thu, 17 Feb 2000 16:23:05 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.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id JAA23539; Thu, 17 Feb 2000 09:21:59 -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 LAA09790; Thu, 17 Feb 2000 11:21:58 -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: <14508.8230.213769.821490@hip186.ch.intel.com> Date: Thu, 17 Feb 2000 09:21:58 -0700 (MST) To: freebsd-qa@freebsd.org, freebsd-current@freebsd.org Subject: feedback on CD install of 4.0-RC2 X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK folks, here's some feedback on 4.0-RC2 from somebody who hasn't done a CD install in a while ... I got my new HDD in last night, put her in the machine and let it rip. Here's the things I found that either puzzled me or might stand a bit of enhancement before RC2->RELEASE. o As I've seen other people mention, there was a considerable delay while waiting for the kernel to get done probing IDE disks. This new disk I got was a Quantum Fireball and the ATA code detected it and used UDMA33 without a hitch. However after the probe message: ata0 at 0x01f0 irq 14 on ata-pci0 the kernel "sat there" for 30-50 seconds. I know I've read this is "needed per the spec" but it would be much less mysterious if a message could be printed before that wait had to happen (much like the scsi subsystem when the bus is reset). I didn't see anything in the FAQ about this, but I'm sure it will become one soon ... o label, partition, and dist. extraction went without a hitch! o I then chose the option of doing "final configuration" (or whatever sysinstall says) where it allows you to pick packages, set root's password, etc. After I picked the packages I wanted to be installed, I hit the "Install" button and things proceeded to install with no hitches--however, it seemed that randomly (because I couldn't pick out any pattern to it) the screen would flash back to the "FreeBSD Configuration Menu" as it cycled through new packages to install. The gray dialog that shows which package is being installed would show this info, then disappear, the "FreeBSD Configuration Menu" would reappear for about 1/5 of a second, then the gray box would show up again with a new package name as it was installed. Now, I haven't done a raw CD install for about a year, but I can't say that I remember that behavior. What I remember is the gray box staying up continuously while all the packages were installed. The constant "flashing" between "gray box on blue" to "FreeBSD Configuration Menu" and back was a little wierd. Everything was physically installed correctly, but it's one of those "polishing" things that would make the install look "better" (IMHO of course ...). o I then tried to configure X. I think sysinstall needs to present a dialog before running the GUI X configure program saying that there is a good chance that the mouse won't work in the GUI program. It should then explain that if you did choose to configure moused (and moused was started by sysinstall at that point--I assume) that you should choose /dev/sysmouse and hit "a" to "apply" the changes so the mouse is found. Equivalently, if you have a ps/2 mouse and are not running moused, choose /dev/psm0 and then hit "a" to apply the changes. I'll be the first to admit that in all the previous times I've configured X on a new machine, I didn't RTFM the on-screen text from the X GUI and didn't hit the 'apply' button (until the run last night). My mistake, but I think it might be a common enough one for sysinstall to specifically say something about it. If you disagree with that point, at least consider having sysinstall direct the user to which device file to point to if his/her mouse isn't recognized. If you were a brand new user to FreeBSD, would you know that /dev/psm0 is to be used for ps/2 mice when not running moused? If you were a brand new user to FreeBSD, would you know that if you did configure and run moused that /dev/sysmouse is the device you should point to? I think not. o The configuration of GNOME+E. worked. However, I had to manually put "gnome-session" in my .xinitrc file. It seems to me that a more "friendly" install would be one where if you chose KDE or GNOME+ that it asks you which accounts you want to setup and does the appropriate things. That way, the first time the new user reboots, logs in, and types "startx" he/she goes into the windowing environment that he/she chose in sysinstall. If I were a completely new user to FreeBSD, I wouldn't have known to put gnome-session in my .xinitrc in order to get it to work. I would have fired up X and saw the ugly-as-sin twm setup that comes with X and thought to myself "boy, GNOME sure is ugly and worthless...". It's a small thing, sure, but a gigantic thing to new-comers. o Finally, again, it seems to me that the skeleton .cshrc, .profile, etc. files that are used for accounts creating during install should have the following variables set: setenv LC_ALL en_US.ISO_8859-1 setenv LC_CTYPE en_US.ISO_8859-1 setenv LANG en_US.ISO_8859-1 (to whatever values are appropriate--this could even be asked if not guessed correctly from the time zone info). Lots of the GNOME/GTK stuff that I installed and ran complained that "LOCALE could not be set" (or whatever--I'm not at the machine and am paraphrasing--those who know what the above variables are for know the error I'm talking about when you don't have them set). When I went to compile a custom kernel, some perl scripts used at the beginning of "make depend" complained about the same lack of these variables. Everything else seemed ok and very speedy. I tweaked rc.conf values to add my default route, NFS, blah blah blah and it all worked A-OK like my 3.4 machine (connecting and routine through my 3.4-S gateway). No problems there! All in all, I think most of the things I experienced last night were "cosmetic" in nature--however, if they could be polished away, it would make for a *completely* bullet-proof and awesome install experience--especially for a new user coming to FreeBSD for the first time. "I'm John, and this has been my Report." -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 8:30:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 78F4E37B735; Thu, 17 Feb 2000 08:30:25 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id LAA00649; Thu, 17 Feb 2000 11:29:58 -0500 (EST) Date: Thu, 17 Feb 2000 11:29:57 -0500 (EST) From: Daniel Eischen To: Bruce Evans Cc: Thimble Smith , current@FreeBSD.ORG, jasone@FreeBSD.ORG Subject: Re: pthread.h and unistd.h In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Bruce Evans wrote: > On Thu, 17 Feb 2000, Daniel Eischen wrote: > > > On Thu, 17 Feb 2000, Thimble Smith wrote: > > > > > Hi. I recently updated from -stable to -current. I notice now that > > > pthread.h relies on #defines that are in unistd.h; so in order to use > > > pthread_attr_setscope you have to include unistd.h before pthread.h. > > > > > > Is this standard behaviour? I'm working with MySQL, and unistd.h is > > > included after pthread.h; should I have that code changed, or should > > > FreeBSD somehow compensate for this? > > > > I've read the POSIX spec, and it looks like pthread.h should include > > unistd.h so that the #defines you refer to are properly defined. > > It can't include or even , at least in > POSX.1-1996, because even the latter defines names that are not reserved > for . E.g., defines SEEK_SET, but the only > non-implementation reserved for are ones beginning with > pthread_ or PTHREAD_, or ending with _t. > > However, including wouldn't add much to the existing > namespace violation from including , , > , and . > > > Solaris 2.5.1 pthread.h doesn't include directly, but does > > include which includes . > > This seems to be a bug Solaris 2.5.1. Our avoids > including by including to get more > fundamental feature test macros for the visibility of the POSIX.1b > extensions. It seems to be fixed under Solaris 2.7. How about we remove the #if defined()s for: _POSIX_THREAD_PROCESS_SHARED _POSIX_THREAD_PRIO_PROTECT _POSIX_THREAD_PRIO_INHERIT _POSIX_THREAD_PRIORITY_SCHEDULING from our ? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 8:40:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id E419937B7B9 for ; Thu, 17 Feb 2000 08:40:27 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12LTyM-000BOp-00; Thu, 17 Feb 2000 22:40:10 +0600 Date: Thu, 17 Feb 2000 22:40:10 +0600 (ALMT) From: Boris Popov To: The Hermit Hacker Cc: Dan Nelson , freebsd-current@FreeBSD.ORG Subject: Re: Mounting Netware drive onto 4.0-CURRENT ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, The Hermit Hacker wrote: > Okay, tried that, still no go: > > athena:/home/kerri> ncplogin -S admin -U .kerri.admin.acadia > Warning: no cfg files found. > Netware password: > ncplogin: Could not login to server ADMIN: nwerr = 89f0 > athena:/home/kerri> NDS and NDS names are not supported by current implementation. Thats why I'm told about bindery context before. If user "kerri" is in the bindery context then "-U kerri" will work. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 8:45:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 25B0137B733; Thu, 17 Feb 2000 08:45:45 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id LAA06277; Thu, 17 Feb 2000 11:45:44 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000217114319.01bd76a0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 17 Feb 2000 11:43:19 -0500 To: current@freebsd.org From: Mike Tancsa Subject: MegaRAID 428 vs 466 and a way to wedge the controller Cc: msmith@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG OK, I seem to have my 466 (aka Perc 2/SC) working somewhat as expected once I flashed to BIOS to the latest rev from AMI. However, I can now more reliably wedge the controller where as with the 428 this would only happen on occasion. I have a 466 with a RAID5 set on 3 quantum LVD drives. If I do 4 copies of bonnie -s 600 -d /mnt & the controller seems to wedge on a fairly regular basis, where as this only happened to me once with the 428. As for performance, I do see good performance on random reads, but not so great performance on raw io. e.g. -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU amrd0 500 5451 22.7 5275 6.5 4756 6.8 12879 80.6 28521 20.9 840.0 6.1 ad0 500 17559 72.3 18083 22.8 5060 9.6 15293 96.2 14258 15.3 426.4 4.0 ad0: 13072MB [26559/16/63] at ata0-master using UDMA33 This is with a 64K stripe. I imagine a 128K stripe will drop the random seeks, but improve the throughput ? Eventually, this will be a pop3 server so I am not quite sure yet how best to optimze for that. ---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-current" in the body of the message From owner-freebsd-current Thu Feb 17 9: 8: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 2A3EB37B7AF; Thu, 17 Feb 2000 09:07:19 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (v-ger [158.227.6.179]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id SAA29417; Thu, 17 Feb 2000 18:01:34 +0100 (MET) Message-ID: <38AC296B.37D39240@we.lc.ehu.es> Date: Thu, 17 Feb 2000 18:01:31 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: John Reynolds~ Cc: freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 References: <14508.8230.213769.821490@hip186.ch.intel.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John Reynolds~ wrote: > > o Finally, again, it seems to me that the skeleton .cshrc, .profile, > etc. files that are used for accounts creating during install should have the > following variables set: > > setenv LC_ALL en_US.ISO_8859-1 > setenv LC_CTYPE en_US.ISO_8859-1 > setenv LANG en_US.ISO_8859-1 > I agree: this would be very useful specially for non-US users. But instead of modifying .cshrc, .profile, etc. for each account, I think that adding the capabilities lang=xx_YY.ISO_8859-ZZ:\ charset=ISO_8859-ZZ: to the "default" entry in /etc/login.conf (or maybe to the "me" entry in .login_conf for each account) would be a better approach. But I would left this improvement for 4.1-RELEASE :) -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 9:30: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id DCAC637B7BB; Thu, 17 Feb 2000 09:30:02 -0800 (PST) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.8.7/8.8.7) with ESMTP id EAA00643; Fri, 18 Feb 2000 04:33:13 +1100 Date: Fri, 18 Feb 2000 04:29:41 +1100 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Daniel Eischen Cc: Thimble Smith , current@FreeBSD.ORG, jasone@FreeBSD.ORG Subject: Re: pthread.h and unistd.h In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Daniel Eischen wrote: > How about we remove the #if defined()s for: > > _POSIX_THREAD_PROCESS_SHARED > _POSIX_THREAD_PRIO_PROTECT > _POSIX_THREAD_PRIO_INHERIT > _POSIX_THREAD_PRIORITY_SCHEDULING > > from our ? Except for the first, which is left undefined in because it is not implemented. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 9:33:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw1.be.to (mailgw1.be.to [210.235.212.5]) by hub.freebsd.org (Postfix) with ESMTP id 4782A37B7A2 for ; Thu, 17 Feb 2000 09:33:12 -0800 (PST) (envelope-from okazaki@be.to) Received: from mail1.be.to (point1.be.to [210.235.212.29]) by mailgw1.be.to (8.9.3+3.2W/BETO.2.1-2000021722000035) with ESMTP id CAA21832 for ; Fri, 18 Feb 2000 02:33:10 +0900 Received: from acidrain (ppp34-Mobara1.mtci.ne.jp [210.172.1.236]) by mail1.be.to (8.8.8+3.0Wbeta13/BETO.2.0-1999110714000000) with SMTP id CAA00315 for ; Fri, 18 Feb 2000 02:33:08 +0900 Received: (qmail 2299 invoked from network); 17 Feb 2000 17:32:32 -0000 Received: from localhost (HELO acidrain.localnet) (127.0.0.1) by localhost with SMTP; 17 Feb 2000 17:32:32 -0000 Date: Fri, 18 Feb 2000 02:32:30 +0900 Message-ID: <86d7pv20r5.wl@dolphin.be.to> From: OKAZAKI Tetsurou To: freebsd-current@FreeBSD.ORG Cc: okazaki@be.to Subject: FYI: routed 2.19 is released... User-Agent: Wanderlust/2.2.17 (One Of Us) EMY/1.13.2 (Better late than never) CLIME/1.13.6 (=?ISO-2022-JP?B?GyRCQ2YlTj4xGyhC?=) APEL/10.0 Emacs/20.5 (i386--freebsd) MULE/4.0 (HANANOEN) Organization: Unknown MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-2022-JP Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Vernon J. Schryver updated his routed to 2.19 at http://www.rhyolite.com/src/. According to the release notes on this page, | $B""(B version 2.19 fixes an unlikely minor memory leak and a man page | typo Just FYI. -- Tetsurou To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 9:54: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id EC84337B75C; Thu, 17 Feb 2000 09:53:57 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA07330; Thu, 17 Feb 2000 09:52:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: John Reynolds~ Cc: freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 In-reply-to: Your message of "Thu, 17 Feb 2000 09:21:58 MST." <14508.8230.213769.821490@hip186.ch.intel.com> Date: Thu, 17 Feb 2000 09:52:35 -0800 Message-ID: <7327.950809955@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > "Install" button and things proceeded to install with no hitches--however, i t > seemed that randomly (because I couldn't pick out any pattern to it) the > screen would flash back to the "FreeBSD Configuration Menu" as it cycled > through new packages to install. The gray dialog that shows which package is Fixed this last night. > o I then tried to configure X. I think sysinstall needs to present a dialog > before running the GUI X configure program saying that there is a good chanc e > that the mouse won't work in the GUI program. It should then explain that if Hmmm. Odd, I've always noted the opposite. If you do the novice install (which everyone should if they're trying to test the "typical case"), the mouse working properly is the typical case. > o The configuration of GNOME+E. worked. However, I had to manually put > "gnome-session" in my .xinitrc file. It seems to me that a more "friendly" How did you install and configure GNOME+E? I just tried a fresh install and selected it off the desktop menu and it worked just fine, exactly as you say you'd like it to work. > o Finally, again, it seems to me that the skeleton .cshrc, .profile, > etc. files that are used for accounts creating during install should have th e > following variables set: > > setenv LC_ALL en_US.ISO_8859-1 > setenv LC_CTYPE en_US.ISO_8859-1 > setenv LANG en_US.ISO_8859-1 This is a question for the I18N folks; I don't even try to puzzle out the various quirks of locale settings these days. :) > "I'm John, and this has been my Report." Thanks! - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 9:55:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id 7C28037B6C6; Thu, 17 Feb 2000 09:55:40 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id KAA07230; Thu, 17 Feb 2000 10:55:39 -0700 (MST) 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.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id KAA14101; Thu, 17 Feb 2000 10:55:39 -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 MAA13651; Thu, 17 Feb 2000 12:55:39 -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: <14508.13850.725857.718236@hip186.ch.intel.com> Date: Thu, 17 Feb 2000 10:55:38 -0700 (MST) To: freebsd-qa@freebsd.org, freebsd-current@freebsd.org Subject: question regarding root_disk_unit ... X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello all, Aside from the feedback on the install of 4.0-RC2 I gave earlier this morning, I have a few related questions to things I saw after putting my machine "back the way it was." Before I installed the new EIDE HDD, my machine had two scsi disks on an aic controller. The root partition is da0s2a. I had previously unconnected the scsi disks when installing 4.0-RC2 on the new HDD because I wanted absolutely no chance of hosing anything on this -STABLE box (I'm not quite ready yet to "take the plunge" :). So, after I install 4.0-RC2 and write down everything for my report earlier, I tried to reboot back into 3.4-S. When I rebooted, chose "F5" to get to the scsi disk's boot options, chose "F2" (since I dual-boot with Ebola '98) and it proceeded to boot 3.4-S. However, things got confused and I received a panic, error 22, cannot mount root (2). I remembered seeing messages like this flying in current-digest and 10 minutes of reading the "help" stuff within the boot loader led me to figure out to say "set root_disk_unit=0" at the boot prompt and put that variable in my /boot/loader.conf for future use. No problem. My question is, is root_disk_unit set for somebody in /boot/loader.conf during an install if there is a chance of things being confused (i.e. IDE and scsi disks in a machine such as mine)? I think I remember somebody saying that they were putting that code into either sysinstall or something so that machines with this disk configuration (or wierder ones) would happily boot after exiting sysinstall. My install was flawless simply because I yanked the scsi disks out of the machine before proceeding. Comments? Also, a non-related-to-freebsd question (but I know somebody will have the answer), the root_disk_unit=0 thing fixed me up for booting FreeBSD off my scsi disk, but when I tried to boot Ebola '98 with the F1 option (also located on da0, da0s1) it just "sat there" ... I assume this is confusion on its part because there is a new disk in the system and Ebola '98 is too stupid to do the Right Thing(tm)? Anybody experienced this behavior with a dual-boot system after adding an IDE disk to what was an an all-scsi disk system? Thanks, -Jr ps: Again, kudos to all contributors to 4.0! It looks very, very good. We just need to do some "polishing" around the corners and it'll be as shiny as a new dime! -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 9:57:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 386ED37B806 for ; Thu, 17 Feb 2000 09:57:42 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 25262 invoked by uid 1001); 17 Feb 2000 17:57:06 -0000 Date: Thu, 17 Feb 2000 09:57:06 -0800 From: Jason Evans To: Daniel Eischen Cc: Bruce Evans , Thimble Smith , current@FreeBSD.ORG Subject: Re: pthread.h and unistd.h Message-ID: <20000217095706.M18774@sturm.canonware.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from eischen@vigrid.com on Thu, Feb 17, 2000 at 11:29:57AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 17, 2000 at 11:29:57AM -0500, Daniel Eischen wrote: > > How about we remove the #if defined()s for: > > _POSIX_THREAD_PROCESS_SHARED > _POSIX_THREAD_PRIO_PROTECT > _POSIX_THREAD_PRIO_INHERIT > _POSIX_THREAD_PRIORITY_SCHEDULING > > from our ? Yes, it looks like use of the last three should be removed from pthread.h. I'll submit a patch to Jordan. Thanks, Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 9:59:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from thelab.hub.org (nat197.96.mpoweredpc.net [142.177.197.96]) by hub.freebsd.org (Postfix) with ESMTP id 4DA3037B704 for ; Thu, 17 Feb 2000 09:59:14 -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 NAA28369 for ; Thu, 17 Feb 2000 13:59:07 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Thu, 17 Feb 2000 13:59:07 -0400 (AST) From: The Hermit Hacker To: freebsd-current@freebsd.org Subject: [mount_nwfs] Got it!! But ... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Great, finally figured out what I was missing for the mount_nwfs command ... *but* ... How do I get it to automount on reboot? From what I can tell, you have to be root to do it ... but, you have to enter a passwd when you do it this way, so its not something you can add to /etc/fstab when a machine reboots ... I've looked at the man page and the .nwfsrc file, but there is a 'flaw' there, and that is what does one do in a multi-user environment, where I want to mount n users netware drives to the system on reboot? they have to give me their netware passwords? So farr as I can tell, this is great for a single-user environemnt, but not multi-user, but it could just be a doc I'm missing ... thanks... 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 10:29:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (Postfix) with ESMTP id 99B8437B760 for ; Thu, 17 Feb 2000 10:29:24 -0800 (PST) (envelope-from dan@dan.emsphone.com) Date: Thu, 17 Feb 2000 12:29:19 -0600 From: Dan Nelson To: The Hermit Hacker Cc: freebsd-current@FreeBSD.ORG Subject: Re: [mount_nwfs] Got it!! But ... Message-ID: <20000217122919.B11137@dan.emsphone.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: ; from "The Hermit Hacker" on Thu Feb 17 13:59:07 GMT 2000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In the last episode (Feb 17), The Hermit Hacker said: > > How do I get it to automount on reboot? From what I can tell, you > have to be root to do it ... but, you have to enter a passwd when you > do it this way, so its not something you can add to /etc/fstab when a > machine reboots > ... > > I've looked at the man page and the .nwfsrc file, but there is a > 'flaw' there, and that is what does one do in a multi-user > environment, where I want to mount n users netware drives to the > system on reboot? they have to give me their netware passwords? This is where Terry joins in, and talks about per-user credentials. The problem is that the unix mount style (mount as root, and limit access on the client as users access files) doesn't mesh well with the Netware/SMB model (one independant mount per user). -- Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 10:35:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 5581A37B7E9 for ; Thu, 17 Feb 2000 10:35:19 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id KAA74986 for ; Thu, 17 Feb 2000 10:35:18 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) To: current@freebsd.org Subject: FWIW: More questionable softupdates+vinum benchmarks X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Thu, 17 Feb 2000 10:35:17 -0800 Message-ID: <74982.950812517@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I have a friend's quad PPro box temporarily sitting in my garage that I've been using to play with 4.0-CURRENT and vinum. Since the last series of bug-fixes a few weeks ago, everything works as advertised. Just for my own curiosity, I've been running some simple (probably questionable) tests involving find|cpio of the source tree and then buildworld -j16 on various vinum volumes. So I thought I'd forward the results to current, for what it's worth. The biggest (non)surprise is how big a difference softupdates makes. Nice! -- Parag Patel "Idiocy: Never underestimate the power of stupid people in large groups" -- Despair.COM # 4xPPro (256k on-chip cache) 200MHz SMP, 512Mb RAM, 5 x 2Gb (older) SCSI disks # volumes / /var /usr are on a newer IDE drive (BIOS doesn't grok SCSI) # softupdates are on for all volumes here, except for / # /tmp is on a 32Mb MFS filesystem and is mounted async # /etc/make.conf defaults to running gcc -O -pipe # vinum.conf drive d0 device /dev/da0s1e drive d1 device /dev/da1s1e drive d2 device /dev/da2s1e drive d3 device /dev/da3s1e drive d4 device /dev/da4s1e volume raid5 setupstate plex org raid5 256k sd length 768m drive d0 sd length 768m drive d1 sd length 768m drive d2 sd length 768m drive d3 sd length 768m drive d4 volume raid10 setupstate plex org striped 256k sd length 0 drive d0 sd length 0 drive d1 plex org striped 256k sd length 0 drive d2 sd length 0 drive d3 volume noraid setupstate plex org concat sd length 0 drive d4 find /usr/src | cpio -pdum /target (~600k blocks): /raid5 (5 drives, 256k, softupdates): 949.21s real 6.28s user 142.21s system /raid5 (5 drives, 256k): 2500.62s real 6.16s user 165.65s system /raid10 (4 drives, 256k stripe, softupdates): 786.46s real 5.86s user 141.50s system /raid10 (4 drives, 256k stripe): 1553.88s real 6.37s user 150.64s system /noraid (1 drive, softupdates): 901.70s real 6.32s user 135.73s system /noraid (1 drive): 1614.45s real 6.09s user 142.46s system build kernel -j16: IDE disk (softupdates) 152.97s real 430.57s user 99.85s system /raid5 volume (5 drives, 256k, softupdates) 162.40s real 434.40s user 99.75s system /raid5 (5 drives, 256k): 159.79s real 432.53s user 99.35s system /raid10 (4 drives, 256k stripe, softupdates): 141.81s real 428.63s user 101.05s system /raid10 (4 drives, 256k stripe): 143.49s real 433.42s user 99.80s system /noraid (1 drive, softupdates): 145.35s real 431.35s user 96.50s system /noraid (1 drive): 148.13s real 433.23s user 95.01s system buildworld -j16: src & obj on IDE disk (softupdates) 5676.29 real 7701.09 user 6133.60 sys src & obj on /raid5 volume (5 drives, 256k, softupdates) 6066.43 real 7929.20 user 7659.18 sys src & obj on /raid5 volume (5 drives, 256k) 7098.73 real 7979.00 user 7843.46 sys src & obj on /raid10 volume (4 drives, 256k stripe, softupdates) 5932.15 real 7918.44 user 7645.84 sys src & obj on /raid10 volume (4 drives, 256k stripe) 6479.33 real 7964.00 user 7565.06 sys src & obj on /noraid volume (1 drive, softupdates) 6053.86 real 7969.94 user 7601.81 sys src & obj on /noraid volume (1 drive) 6607.68 real 7965.14 user 7377.00 sys To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 10:43:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [62.104.201.3]) by hub.freebsd.org (Postfix) with ESMTP id 4F2E937B804 for ; Thu, 17 Feb 2000 10:43:41 -0800 (PST) (envelope-from netchild@leidinger.net) Received: from [62.104.201.6] (helo=mx0.freenet.de) by mout1.freenet.de with esmtp (Exim 3.13 #1) id 12LVto-0006v2-00; Thu, 17 Feb 2000 19:43:36 +0100 Received: from [213.6.223.183] (helo=Magelan.Leidinger.net) by mx0.freenet.de with esmtp (Exim 3.13 #1) id 12LVtm-0007eW-00; Thu, 17 Feb 2000 19:43:35 +0100 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id TAA20541; Thu, 17 Feb 2000 19:32:25 +0100 (CET) (envelope-from netchild@Leidinger.net) Message-Id: <200002171832.TAA20541@Magelan.Leidinger.net> Date: Thu, 17 Feb 2000 19:32:24 +0100 (CET) From: Alexander Leidinger Subject: Re: feedback on CD install of 4.0-RC2 To: jkh@zippy.cdrom.com Cc: freebsd-current@FreeBSD.ORG In-Reply-To: <7327.950809955@zippy.cdrom.com> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17 Feb, Jordan K. Hubbard wrote: [Cc stripped] >> o Finally, again, it seems to me that the skeleton .cshrc, .profile, >> etc. files that are used for accounts creating during install should have the >> following variables set: >> >> setenv LC_ALL en_US.ISO_8859-1 >> setenv LC_CTYPE en_US.ISO_8859-1 >> setenv LANG en_US.ISO_8859-1 > > This is a question for the I18N folks; I don't even try to puzzle out > the various quirks of locale settings these days. :) IMHO sysinstall or motd should print a little note about the possibility to set those variables, so Jordan hasn't to mess with them (e.g. for de_DE one wants to add LC_NUMERIC=C because every lazy script/program which asks for floats and processes them would break [123.4 -> 123,4]). ^ ^ Bye, Alexander. -- Been there, done that, can't remember why... http://www.Leidinger.net Alexander+Home @ Leidinger.net Key fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 10:46:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id ABD5E37B6C6; Thu, 17 Feb 2000 10:46:37 -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 NAA59070; Thu, 17 Feb 2000 13:45:17 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200002171845.NAA59070@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: <14508.8230.213769.821490@hip186.ch.intel.com> Date: Thu, 17 Feb 2000 13:45:17 -0500 (EST) From: John Baldwin To: John Reynolds~ Subject: RE: feedback on CD install of 4.0-RC2 Cc: freebsd-current@FreeBSD.org, freebsd-qa@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Feb-00 John Reynolds~ wrote: > > OK folks, here's some feedback on 4.0-RC2 from somebody who hasn't done a CD > install in a while ... I got my new HDD in last night, put her in the machine > and let it rip. Here's the things I found that either puzzled me or might > stand a bit of enhancement before RC2->RELEASE. > > o As I've seen other people mention, there was a considerable delay while > waiting for the kernel to get done probing IDE disks. This new disk I got was > a Quantum Fireball and the ATA code detected it and used UDMA33 without a > hitch. However after the probe message: > > ata0 at 0x01f0 irq 14 on ata-pci0 > > the kernel "sat there" for 30-50 seconds. I know I've read this is "needed > per the spec" but it would be much less mysterious if a message could be > printed before that wait had to happen (much like the scsi subsystem when the > bus is reset). I didn't see anything in the FAQ about this, but I'm sure it > will become one soon ... Soren's been bugged about this, bug him some more. :) > o I then tried to configure X. I think sysinstall needs to present a dialog [ snip ] Hmm, it used to say something to that effect a while back. > o The configuration of GNOME+E. worked. However, I had to manually put > "gnome-session" in my .xinitrc file. It seems to me that a more "friendly" > install would be one where if you chose KDE or GNOME+ that it asks > you which accounts you want to setup and does the appropriate things. That > way, the first time the new user reboots, logs in, and types "startx" he/she > goes into the windowing environment that he/she chose in sysinstall. If I > were a completely new user to FreeBSD, I wouldn't have known to put > gnome-session in my .xinitrc in order to get it to work. I would have fired > up X and saw the ugly-as-sin twm setup that comes with X and thought to > myself "boy, GNOME sure is ugly and worthless...". It's a small thing, sure, > but a gigantic thing to new-comers. It modifies root's setup and the setup in /usr/share/skel. Note that since sysinstall must run as root, it can't possibly know what username you are using. If you do the Desktop configuration before adding new users, then it will DTRT. If you are prompted to add new users in the Novice install before you do the X Desktop setup, then the order of those two things may need to be switched around. > o Finally, again, it seems to me that the skeleton .cshrc, .profile, > etc. files that are used for accounts creating during install should have the > following variables set: > > setenv LC_ALL en_US.ISO_8859-1 > setenv LC_CTYPE en_US.ISO_8859-1 > setenv LANG en_US.ISO_8859-1 Then submit patches to the /usr/share/skel files in a PR. I'm not sure where they are in the src tree, maybe src/share/skel. > (to whatever values are appropriate--this could even be asked if not guessed > correctly from the time zone info). Lots of the GNOME/GTK stuff that I > installed and ran complained that "LOCALE could not be set" (or whatever--I'm > not at the machine and am paraphrasing--those who know what the above > variables are for know the error I'm talking about when you don't have them > set). When I went to compile a custom kernel, some perl scripts used at the > beginning of "make depend" complained about the same lack of these variables. LC_ALL=LC_CTYPE=LANG=C might be a good default. > Everything else seemed ok and very speedy. I tweaked rc.conf values to add my > default route, NFS, blah blah blah and it all worked A-OK like my 3.4 machine > (connecting and routine through my 3.4-S gateway). No problems there! > > All in all, I think most of the things I experienced last night were > "cosmetic" in nature--however, if they could be polished away, it would make > for a *completely* bullet-proof and awesome install experience--especially for > a new user coming to FreeBSD for the first time. > > "I'm John, and this has been my Report." Thanks. > -Jr -- 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 11:28:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 9583E37B6A5; Thu, 17 Feb 2000 11:28:27 -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 OAA64276; Thu, 17 Feb 2000 14:28:16 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200002171928.OAA64276@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: <200002170104.RAA02112@mass.cdrom.com> Date: Thu, 17 Feb 2000 14:28:15 -0500 (EST) From: John Baldwin To: Mike Smith Subject: Re: Thinkpad won't boot ISO image Cc: "David E. Cross" Cc: "David E. Cross" , Gerald Abshez , freebsd-current@FreeBSD.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Feb-00 Mike Smith wrote: >> >> On 16-Feb-00 Mike Smith wrote: >> >> This is a problem with the thinkpad BIOS that I have not had the time to be >> >> able to track down. It would *appear* to be that the BIOS does not do >> >> int 13 handling on boot cdroms, and the boot/loader makes much use of that >> >> for loading the kernel and drivers. >> > >> > The problem with the Thinkpad BIOS is where it puts the emulated floppy >> > image's disk number - it's not in the 'normal' place, and I don't exactly >> > know how to deal with it cleanly. If someone were to lend me a thinkpad >> > or look at this it would be easy to fix. >> >> Err, which place? The emulated device is always BIOS drive 0x00, aka the >> first floppy drive when you are emulating a floppy. > > It's not, which is the "Thinkpad CDROM boot problem". The one report I > recall put it on 0x87, but I don't have any concrete evidence to suggest > that it's always there either. Gah. Then they need to learn how to read standards. It is passed in via %dl at least? -- 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 11:48:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 8629F37B698 for ; Thu, 17 Feb 2000 11:48: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 LAA00438; Thu, 17 Feb 2000 11:59:49 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002171959.LAA00438@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: current@freebsd.org Subject: Re: MegaRAID 428 vs 466 and a way to wedge the controller In-reply-to: Your message of "Thu, 17 Feb 2000 11:43:19 EST." <3.0.5.32.20000217114319.01bd76a0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Feb 2000 11:59:49 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, > I seem to have my 466 (aka Perc 2/SC) working somewhat as expected once I > flashed to BIOS to the latest rev from AMI. However, I can now more > reliably wedge the controller where as with the 428 this would only happen > on occasion. When you say "wedge", are you referring to the "controller wedged" message? If so, can you increase the 10000 on line 1129 of sys/dev/amr/amr.c to 100000 and try again? I'm fairly sure that this is just my sloppy programming giving you a bad time; I need a better timeout for this. -- \\ 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 11:53: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 30DA137B6E8; Thu, 17 Feb 2000 11:53:07 -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 MAA00520; Thu, 17 Feb 2000 12:05:12 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002172005.MAA00520@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Baldwin Cc: "David E. Cross" , Gerald Abshez , freebsd-current@FreeBSD.org Subject: Re: Thinkpad won't boot ISO image In-reply-to: Your message of "Thu, 17 Feb 2000 14:28:15 EST." <200002171928.OAA64276@server.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Feb 2000 12:05:12 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > On 17-Feb-00 Mike Smith wrote: > >> > >> On 16-Feb-00 Mike Smith wrote: > >> >> This is a problem with the thinkpad BIOS that I have not had the time to be > >> >> able to track down. It would *appear* to be that the BIOS does not do > >> >> int 13 handling on boot cdroms, and the boot/loader makes much use of that > >> >> for loading the kernel and drivers. > >> > > >> > The problem with the Thinkpad BIOS is where it puts the emulated floppy > >> > image's disk number - it's not in the 'normal' place, and I don't exactly > >> > know how to deal with it cleanly. If someone were to lend me a thinkpad > >> > or look at this it would be easy to fix. > >> > >> Err, which place? The emulated device is always BIOS drive 0x00, aka the > >> first floppy drive when you are emulating a floppy. > > > > It's not, which is the "Thinkpad CDROM boot problem". The one report I > > recall put it on 0x87, but I don't have any concrete evidence to suggest > > that it's always there either. > > Gah. Then they need to learn how to read standards. It is passed in via %dl > at least? After David's response, I'm wondering whether the problem isn't that they _arent_ passing the value in via %dl, and we're just getting trash. Not sure how it is that boot1/2 are working though. -- \\ 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 12: 4:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id E68B537B7DC; Thu, 17 Feb 2000 12:04:48 -0800 (PST) (envelope-from mike@sentex.ca) Received: from simoeon (simeon.sentex.ca [209.112.4.47]) by vinyl.sentex.ca (8.9.3/8.9.3) with SMTP id PAA39252; Thu, 17 Feb 2000 15:04:47 -0500 (EST) (envelope-from mike@sentex.ca) Message-Id: <3.0.5.32.20000217150221.0161fcb0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.5 (32) Date: Thu, 17 Feb 2000 15:02:21 -0500 To: Mike Smith From: Mike Tancsa Subject: Re: MegaRAID 428 vs 466 and a way to wedge the controller Cc: current@freebsd.org In-Reply-To: <200002171959.LAA00438@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 11:59 AM 2/17/00 -0800, Mike Smith wrote: >> OK, >> I seem to have my 466 (aka Perc 2/SC) working somewhat as expected once I >> flashed to BIOS to the latest rev from AMI. However, I can now more >> reliably wedge the controller where as with the 428 this would only happen >> on occasion. > >When you say "wedge", are you referring to the "controller wedged" >message? If so, can you increase the 10000 on line 1129 of sys/dev/amr/amr.c >to 100000 and try again? I'm fairly sure that this is just my sloppy >programming giving you a bad time; I need a better timeout for this. Actually, in this case, I dont get that message. Just the same 'effect'. iostat shows no activity, although the bonnies are still running, just doing nothing. If there is there some extra information I can provide you with, let me know what you want me to do. STATE and WCHAN show D and getblk iostat -c 100 shows newmail# iostat -c 100 tty amrd0 ad0 fd0 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 10 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 1 0 0 0 99 0 76 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 0 76 0.00 0 0.00 7.00 2 0.01 0.00 0 0.00 1 0 0 0 99 0 76 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 0 76 0.00 0 0.00 0.00 0 0.00 0.00 0 0.00 0 0 0 0100 even though they are still running. #!/bin/sh /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & /usr/local/bin/bonnie -s 100 -d /mnt & is all I did. How long do I have to wait normally for the wedged message to show up ? The last time I saw it was with the 428, but I seem to recall the message showing up fairly quickly e.g. Feb 11 02:02:57 newmail /kernel: amr0: controller wedged (not taking commands) Feb 11 02:02:57 newmail /kernel: amr0: I/O error - dead Feb 11 02:02:57 newmail /kernel: amr0: cmd 2 ident 3 drive 0 Feb 11 02:02:57 newmail /kernel: amr0: blkcount 16 lba 16580735 Feb 11 02:02:57 newmail /kernel: amr0: virtaddr 0xc9a02000 length 8192 Feb 11 02:02:57 newmail /kernel: amr0: physaddr 00001100 nsg 2 Feb 11 02:02:57 newmail /kernel: amr0: 26da000/4096 Feb 11 02:02:57 newmail /kernel: amr0: 55db000/4096 ------------------------------------------------------------------------ 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 12: 6:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from server.baldwin.cx (jobaldwi.campus.vt.edu [198.82.67.146]) by hub.freebsd.org (Postfix) with ESMTP id 3862537B72B; Thu, 17 Feb 2000 12:06:15 -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 PAA68820; Thu, 17 Feb 2000 15:05:47 -0500 (EST) (envelope-from jhb@FreeBSD.org) Message-Id: <200002172005.PAA68820@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: <200002172005.MAA00520@mass.cdrom.com> Date: Thu, 17 Feb 2000 15:05:47 -0500 (EST) From: John Baldwin To: Mike Smith Subject: Re: Thinkpad won't boot ISO image Cc: freebsd-current@FreeBSD.org, Gerald Abshez , "David E. Cross" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 17-Feb-00 Mike Smith wrote: >> >> On 17-Feb-00 Mike Smith wrote: >> >> >> >> On 16-Feb-00 Mike Smith wrote: >> >> >> This is a problem with the thinkpad BIOS that I have not had the time to be >> >> >> able to track down. It would *appear* to be that the BIOS does not do >> >> >> int 13 handling on boot cdroms, and the boot/loader makes much use of that >> >> >> for loading the kernel and drivers. >> >> > >> >> > The problem with the Thinkpad BIOS is where it puts the emulated floppy >> >> > image's disk number - it's not in the 'normal' place, and I don't exactly >> >> > know how to deal with it cleanly. If someone were to lend me a thinkpad >> >> > or look at this it would be easy to fix. >> >> >> >> Err, which place? The emulated device is always BIOS drive 0x00, aka the >> >> first floppy drive when you are emulating a floppy. >> > >> > It's not, which is the "Thinkpad CDROM boot problem". The one report I >> > recall put it on 0x87, but I don't have any concrete evidence to suggest >> > that it's always there either. >> >> Gah. Then they need to learn how to read standards. It is passed in via %dl >> at least? > > After David's response, I'm wondering whether the problem isn't that they > _arent_ passing the value in via %dl, and we're just getting trash. Not > sure how it is that boot1/2 are working though. I don't think boot1/2 would work at all if %dl was wrong. One thing to note, is that when I finally get cdboot working to the point of loading the loader, I am going to have a similar problem since the device number typically used when booting from a CD is 0x9f, which is not contiguous from 0x80. -- 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 12: 9: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id C2A7A37B6D7 for ; Thu, 17 Feb 2000 12:09:05 -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 MAA00738; Thu, 17 Feb 2000 12:20:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002172020.MAA00738@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: current@freebsd.org Subject: Re: MegaRAID 428 vs 466 and a way to wedge the controller In-reply-to: Your message of "Thu, 17 Feb 2000 15:02:21 EST." <3.0.5.32.20000217150221.0161fcb0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Feb 2000 12:20:39 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 11:59 AM 2/17/00 -0800, Mike Smith wrote: > >> OK, > >> I seem to have my 466 (aka Perc 2/SC) working somewhat as expected once I > >> flashed to BIOS to the latest rev from AMI. However, I can now more > >> reliably wedge the controller where as with the 428 this would only happen > >> on occasion. > > > >When you say "wedge", are you referring to the "controller wedged" > >message? If so, can you increase the 10000 on line 1129 of sys/dev/amr/amr.c > >to 100000 and try again? I'm fairly sure that this is just my sloppy > >programming giving you a bad time; I need a better timeout for this. > > Actually, in this case, I dont get that message. Just the same 'effect'. > iostat shows no activity, although the bonnies are still running, just > doing nothing. If there is there some extra information I can provide you > with, let me know what you want me to do. > > > STATE and WCHAN show D and getblk Ok. This is the race I was alluding to. I'm back onto it today after testing the Mylex stuff some more. It's going to take some moderate changes to the AMI driver, but I think I have them down now. -- \\ 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 12:15:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id C00EA37B7EA for ; Thu, 17 Feb 2000 12:15:40 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id B8BF51235A; Thu, 17 Feb 2000 21:15:33 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <74982.950812517@pinhead.parag.codegen.com> References: <74982.950812517@pinhead.parag.codegen.com> Date: Thu, 17 Feb 2000 21:14:20 +0100 To: Parag Patel , current@FreeBSD.ORG From: Brad Knowles Subject: Re: FWIW: More questionable softupdates+vinum benchmarks Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:35 AM -0800 2000/2/17, Parag Patel wrote: > Hello. I have a friend's quad PPro box temporarily sitting in my garage > that I've been using to play with 4.0-CURRENT and vinum. Since the last > series of bug-fixes a few weeks ago, everything works as advertised. While we're on this subject, I recently did some benchmarking with just a single disk on a machine running 3.4-STABLE, both with and without softupdates. I haven't yet gotten a chance to test it with vinum and softupdates, but what I got did a pretty good job of impressing me. I won't quote the mail messages here (you can go read freebsd-stable for that, look for message-ids and ), but suffice it to say that for my testing, I saw 3-5x performance increase for the benchmark I was running ("postmark", from Network Appliance). The primary reason I was doing this was to get some sort of idea what kind of performance you might be able to expect if you took an application like a mail server or a USENET news server (with traditional spool), and you re-wrote the application so as to avoid expensive synchronous meta-data operations (which are the things that softupdates tries to optimize out of existance). I'm starting to actually believe that you might really be able to see a real-world 5-10x performance increase, if you did that. In fact, I believe that this is pretty much what admins of boxes running INN are seeing when they use CNFS. Jeez, Louise. -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 12:20:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id DDAC037B790 for ; Thu, 17 Feb 2000 12:20:55 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id MAA17332; Thu, 17 Feb 2000 12:49:05 -0800 (PST) Date: Thu, 17 Feb 2000 12:49:04 -0800 From: Alfred Perlstein To: Brad Knowles Cc: Parag Patel , current@FreeBSD.ORG Subject: Re: FWIW: More questionable softupdates+vinum benchmarks Message-ID: <20000217124904.S3509@fw.wintelcom.net> References: <74982.950812517@pinhead.parag.codegen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from blk@skynet.be on Thu, Feb 17, 2000 at 09:14:20PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Brad Knowles [000217 12:45] wrote: > At 10:35 AM -0800 2000/2/17, Parag Patel wrote: > > > Hello. I have a friend's quad PPro box temporarily sitting in my garage > > that I've been using to play with 4.0-CURRENT and vinum. Since the last > > series of bug-fixes a few weeks ago, everything works as advertised. > > While we're on this subject, I recently did some benchmarking > with just a single disk on a machine running 3.4-STABLE, both with > and without softupdates. I haven't yet gotten a chance to test it > with vinum and softupdates, but what I got did a pretty good job of > impressing me. > > I won't quote the mail messages here (you can go read > freebsd-stable for that, look for message-ids > and > ), but suffice it to say that > for my testing, I saw 3-5x performance increase for the benchmark I > was running ("postmark", from Network Appliance). > > > The primary reason I was doing this was to get some sort of idea > what kind of performance you might be able to expect if you took an > application like a mail server or a USENET news server (with > traditional spool), and you re-wrote the application so as to avoid > expensive synchronous meta-data operations (which are the things that > softupdates tries to optimize out of existance). > > I'm starting to actually believe that you might really be able to > see a real-world 5-10x performance increase, if you did that. In > fact, I believe that this is pretty much what admins of boxes running > INN are seeing when they use CNFS. Jeez, Louise. Depending on how temporary your temporary files are, it'd be interesting to see if the 4.0 optimizations benifit your benchmark and also remain stable. Would it be possible for you to grab a 4.0RC and let us know? thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 12:32:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from trinity.skynet.be (trinity.skynet.be [195.238.2.38]) by hub.freebsd.org (Postfix) with ESMTP id BB38337B7D4 for ; Thu, 17 Feb 2000 12:32:18 -0800 (PST) (envelope-from blk@skynet.be) Received: from [195.238.1.121] (brad.techos.skynet.be [195.238.1.121]) by trinity.skynet.be (Postfix) with ESMTP id 2674412218; Thu, 17 Feb 2000 21:32:11 +0100 (MET) Mime-Version: 1.0 X-Sender: blk@pop.skynet.be Message-Id: In-Reply-To: <20000217124904.S3509@fw.wintelcom.net> References: <74982.950812517@pinhead.parag.codegen.com> <20000217124904.S3509@fw.wintelcom.net> Date: Thu, 17 Feb 2000 21:30:38 +0100 To: Alfred Perlstein From: Brad Knowles Subject: Re: FWIW: More questionable softupdates+vinum benchmarks Cc: Parag Patel , current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:49 PM -0800 2000/2/17, Alfred Perlstein wrote: > Depending on how temporary your temporary files are, it'd be > interesting to see if the 4.0 optimizations benifit your benchmark > and also remain stable. Yup, that would be an interesting question. > Would it be possible for you to grab a 4.0RC and let us know? Unfortunately, I don't think I can run 4.0RC on this machine right now. The guys from the vendor that we're leasing the drive array from are coming over on Thursday to set it up, and I need this machine to be rock solid and have lots of benchmarking done to it, so that I can throw the same benchmarks at the drive array once it's set up, and then be able to compare the two. Once they're gone, I can consider throwing 4.0RC on a spare disk I happen to have lying around and plug that into this machine, and see if that makes any difference. I'll almost certainly run -STABLE in production, but I should be able to run some tests with -CURRENT. I'm glad I decided to hang onto that disk.... Out of curiosity, does anyone know if Greg Lehey's "rawio" is dependant on -CURRENT, or if there is some magic incantation required to get it to run under -STABLE? I've run previous benchmarks with it, and I'd like my current ones to be directly comparable to the previous data, by having the same benchmark program, essentially the same hardware, slightly updated OS (3.4-STABLE versus 3.2-RELEASE), etc.... -- These are my opinions and should not be taken as official Skynet policy _________________________________________________________________________ |o| Brad Knowles, Belgacom Skynet NV/SA |o| |o| Systems Architect, Mail/News/FTP/Proxy Admin Rue Col. Bourg, 124 |o| |o| Phone/Fax: +32-2-706.13.11/726.93.11 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 12:41:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 55C7B37B814 for ; Thu, 17 Feb 2000 12:41:24 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id MAA75716; Thu, 17 Feb 2000 12:41:11 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) To: Brad Knowles Cc: current@FreeBSD.ORG Subject: Re: FWIW: More questionable softupdates+vinum benchmarks In-Reply-To: Message from Brad Knowles of "Thu, 17 Feb 2000 21:14:20 +0100." X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Thu, 17 Feb 2000 12:41:11 -0800 Message-ID: <75712.950820071@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000 21:14:20 +0100, Brad Knowles wrote: > > While we're on this subject, I recently did some benchmarking >with just a single disk on a machine running 3.4-STABLE, both with >and without softupdates. I haven't yet gotten a chance to test it >with vinum and softupdates, but what I got did a pretty good job of >impressing me. I'm impressed by both vinum and softupdates. If I didn't need to run cables from my computer-room through the kitchen and to the garage, I'd be tempted to hang on to my friend's machine (he intends to sell it). Oh well. At some point I may create my own poor-man's desktop RAID cluster with several PCI-IDE controllers and a cheap IDE master per interface (no slaves). Not quite as good as SCSI but a heck of a lot cheaper. -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 12:49:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from spirit.jaded.net (spirit.jaded.net [216.94.113.12]) by hub.freebsd.org (Postfix) with ESMTP id 2BC7A37B546 for ; Thu, 17 Feb 2000 12:49:36 -0800 (PST) (envelope-from dan@spirit.jaded.net) Received: (from dan@localhost) by spirit.jaded.net (8.9.3/8.9.3) id PAA01160; Thu, 17 Feb 2000 15:49:26 -0500 (EST) Date: Thu, 17 Feb 2000 15:49:26 -0500 From: Dan Moschuk To: "Chris D. Faulhaber" Cc: freebsd-current@FreeBSD.org Subject: Re: cvs commit: src/usr.sbin/pkg_install/delete main.c src/usr.sbin/pkg_install/info main.c Message-ID: <20000217154926.C1010@spirit.jaded.net> References: <200001180145.RAA50302@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from jedgar@fxp.org on Thu, Feb 17, 2000 at 10:38:55AM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG | > Log: | > Fix a bug in previous commit where pkg_{delete,info} foo-1.0/ would segfault. | > | > Noticed first by: kris | | Is it just me, or does: 'pkg_delete foo-1.0/' now just spin in the | while() loop around line 92 of src/usr.sbin/pkg_install/delete/main.c ? spirit# pkg_delete jive-1.1/ spirit# Just you. :) -- Dan Moschuk (TFreak!dan@freebsd.org) "Waste not fresh tears on old griefs." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 12:50: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id 1364D37B7F3; Thu, 17 Feb 2000 12:49:59 -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.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id UAA01066; Thu, 17 Feb 2000 20:51:04 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.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id NAA26626; Thu, 17 Feb 2000 13:49:56 -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 PAA21642; Thu, 17 Feb 2000 15:49:55 -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: <14508.24306.459593.102063@hip186.ch.intel.com> Date: Thu, 17 Feb 2000 13:49:54 -0700 (MST) To: freebsd-current@freebsd.org, freebsd-qa@freebsd.org Subject: RE: feedback on CD install of 4.0-RC2 In-Reply-To: <200002171845.NAA59070@server.baldwin.cx> References: <14508.8230.213769.821490@hip186.ch.intel.com> <200002171845.NAA59070@server.baldwin.cx> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG [ On Thursday, February 17, John Baldwin wrote: ] > > > [printing ATA message about "waiting"] > > > Soren's been bugged about this, bug him some more. :) > BUG BUG BUG :) > Hmm, it used to say something to that effect a while back. can't comment. I haven't done a CD install in a looong time. > It modifies root's setup and the setup in /usr/share/skel. Note that since > sysinstall must run as root, it can't possibly know what username you are using. > If you do the Desktop configuration before adding new users, then it will DTRT. > If you are prompted to add new users in the Novice install before you do the X > Desktop setup, then the order of those two things may need to be switched around. OK. That's what happened! I added a new user ("me") before I did the desktop configuration. So, you're saying that it adds a "dot.xinitrc" file in /usr/shar/skel which would be copied to all created accounts? Perhaps something could be added to sysinstall so that the "dot.*" files aren't copied to user accounts until a) after a desktop configuration, or b) sysinstall exits. Or, perhaps safer, if you do a desktop configuration recopy all the dot.* files to all user accounts that were created during that sysinstall session. Seems that would fix the problem ... > Then submit patches to the /usr/share/skel files in a PR. I'm not sure where they > are in the src tree, maybe src/share/skel. Indeed. However, as we were talking about this morning in -qa, is a better spot for these variables /etc/csh.cshrc and /etc/profile? > Thanks. no problem! -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 13:45:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from pau-amma.whistle.com (pau-amma.whistle.com [207.76.205.64]) by hub.freebsd.org (Postfix) with ESMTP id 776B237B838 for ; Thu, 17 Feb 2000 13:45:11 -0800 (PST) (envelope-from dhw@whistle.com) Received: (from dhw@localhost) by pau-amma.whistle.com (8.9.2/8.9.2) id NAA21767 for freebsd-current@FreeBSD.ORG; Thu, 17 Feb 2000 13:45:11 -0800 (PST) Date: Thu, 17 Feb 2000 13:45:11 -0800 (PST) From: David Wolfskill Message-Id: <200002172145.NAA21767@pau-amma.whistle.com> Subject: Re: 4.0-RC -- /etc/rc, NFS, & nis_client_enable="NO" Cc: freebsd-current@FreeBSD.ORG In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >Date: Tue, 15 Feb 2000 12:40:21 +1100 (EST) >From: Andy Farkas >Seems like a good idea to me not to have a message displayed if >explicitly configured not to do something! :-} >If you have `nfs_enable_client="NO"' and if you have nfs mounts in your >fstab, then this could be a method of delaying those mounts until after >boot/init time? After discussions with Dougs Barton & Ambrisko :-), it is my current understanding that the intent of the "knob" labeled "nfs_enable_client" is controlling whether or not the nfsiod daemons (which provide a performance enhancement for NFS client code, but do not actually control whether or not it actually functions) are fired up (in rc.network). Thus, it would seem that a name for the knob that currently has the name "nfs_enable_client", but that more accurately reflects the intended function would be in order. In addition, Boug Barton has suggested changes -- other than what I posted -- that would prevent the (rather misleading) startup message in the event that there were, in fact, no NFS mounts to do. 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 13:53:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1006A37B802 for ; Thu, 17 Feb 2000 13:52:54 -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 WAA24852 for freebsd-current@freebsd.org; Thu, 17 Feb 2000 22:48:33 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA01486 for freebsd-current@freebsd.org; Thu, 17 Feb 2000 22:30:12 +0100 (CET) (envelope-from wilko) Date: Thu, 17 Feb 2000 22:30:12 +0100 From: Wilko Bulte To: "FreeBSD_current, mailing list" Subject: ps lost it? Message-ID: <20000217223011.A1427@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is on a K6/233 with yesterday's -current on it. p100#ps ax PID TT STAT TIME COMMAND 0 ?? DLs 0:00.00 () 1 ?? S; Thu, 17 Feb 2000 14:19:19 -0800 (PST) (envelope-from jontow@massive.geek.edu) Received: from massive.geek.edu (scatology [10.0.0.4]) by massive.geek.edu (Postfix) with SMTP id 9835119D6; Thu, 17 Feb 2000 22:19:45 +0000 (GMT) Date: Thu, 17 Feb 2000 22:19:45 GMT From: Jonathan Towne To: Wilko Bulte Cc: freebsd-current@freebsd.org Subject: Re: ps lost it? Reply-To: jontow@massive.geek.edu X-Mailer: Spruce 0.5.14 for X11 w/smtpio 0.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Message-Id: <20000217221945.9835119D6@massive.geek.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Wilko Bulte wrote: > Date: Thu, 17 Feb 2000 22:30:12 +0100 > To: "FreeBSD_current, mailing list" > From: Wilko Bulte > Subject: ps lost it? > > This is on a K6/233 with yesterday's -current on it. .. > 0 ?? DLs 0:00.00 () > 1 ?? S Have I missed something (been away from -current for a couple of weeks) > No, not really, but my machine exhibited the same behavior when i had a new world installed without building a corresponding kernel.. in short: kernel isn't in sync with world, fix it :) -- - Jonathan Towne jontow@massive.geek.edu - System/Network Administrator To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 14:22: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 323A737B844 for ; Thu, 17 Feb 2000 14:21:58 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id IAA28842; Fri, 18 Feb 2000 08:50:06 +1030 (CST) Date: Fri, 18 Feb 2000 08:50:06 +1030 From: Greg Lehey To: Parag Patel Cc: current@FreeBSD.ORG Subject: Re: FWIW: More questionable softupdates+vinum benchmarks Message-ID: <20000218085006.D24604@freebie.lemis.com> References: <74982.950812517@pinhead.parag.codegen.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <74982.950812517@pinhead.parag.codegen.com> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thursday, 17 February 2000 at 10:35:17 -0800, Parag Patel wrote: > > Hello. I have a friend's quad PPro box temporarily sitting in my garage > that I've been using to play with 4.0-CURRENT and vinum. Since the last > series of bug-fixes a few weeks ago, everything works as advertised. > > Just for my own curiosity, I've been running some simple (probably > questionable) tests involving find|cpio of the source tree and then > buildworld -j16 on various vinum volumes. > > So I thought I'd forward the results to current, for what it's worth. > > The biggest (non)surprise is how big a difference softupdates makes. > Nice! > > buildworld -j16: > src & obj on IDE disk (softupdates) > 5676.29 real 7701.09 user 6133.60 sys > src & obj on /noraid volume (1 drive, softupdates) > 6053.86 real 7969.94 user 7601.81 sys I'm not overly happy with these results. I suspect that a throttling mechanism I put in a few months back, which limited the number of simultaneous transactions per drive, might have something to do with it. Could you change the values of VINUM_MAXACTIVE and DRIVE_MAXACTIVE (in /sys/dev/vinum/vinumvar.h) to 30000 each (effectively disabling the throttling), recompile the kld and try again please? Previously, I had limited the number of transactions to 10, but I've just completed a make world here, and the drives had up to 400 outstanding transactions each, so there's quite a possibility the limitation is causing performance problems. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 16: 7:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id F2E9B37B814 for ; Thu, 17 Feb 2000 16:07:55 -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 QAA02987; Thu, 17 Feb 2000 16:19:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002180019.QAA02987@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: current@freebsd.org Subject: Re: MegaRAID 428 vs 466 and a way to wedge the controller In-reply-to: Your message of "Thu, 17 Feb 2000 15:02:21 EST." <3.0.5.32.20000217150221.0161fcb0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Feb 2000 16:19:26 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Actually, in this case, I dont get that message. Just the same 'effect'. > iostat shows no activity, although the bonnies are still running, just > doing nothing. If there is there some extra information I can provide you > with, let me know what you want me to do. ... > #!/bin/sh > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > /usr/local/bin/bonnie -s 100 -d /mnt & > > is all I did. How long do I have to wait normally for the wedged message > to show up ? The last time I saw it was with the 428, but I seem to recall > the message showing up fairly quickly Hmm. I flashed my PERC 2 up to the latest AMI firmware, and with about a dozen bonnie processes running it took about 30 seconds for the controller to lock up completely (I had to power-cycle it to get it to come back). I wouldn't say you have a firmware issue there yet, but it's not looking very good. -- \\ 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 16:31:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id E989137B8B5; Thu, 17 Feb 2000 16:31:02 -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 TAA78475; Thu, 17 Feb 2000 19:30:59 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id TAA02875; Thu, 17 Feb 2000 19:30:58 -0500 (EST) Message-Id: <4.2.2.20000217192443.045cedf0@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 17 Feb 2000 19:30:01 -0500 To: Mike Smith From: Mike Tancsa Subject: Re: MegaRAID 428 vs 466 and a way to wedge the controller Cc: current@FreeBSD.ORG In-Reply-To: <200002180019.QAA02987@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:19 PM 2/17/2000 -0800, Mike Smith wrote: >Hmm. I flashed my PERC 2 up to the latest AMI firmware, and with about a >dozen bonnie processes running it took about 30 seconds for the controller >to lock up completely (I had to power-cycle it to get it to come back). Is this a purely amr box ? I had been testing it out only on 1 partition mounted as /mnt. Although all access to the AMI is hosed, access to my IDE is without issue. >I wouldn't say you have a firmware issue there yet, but it's not looking >very good. What rev of the firmware were you using before hand ? the 3.00 from Dell ? Like I said, without this rev, I could not do anything with the card. From the release notes, it would seem the card has some issues with modern BIOSes ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 16:39:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 3BC5B37B89C for ; Thu, 17 Feb 2000 16:39:07 -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 QAA03318; Thu, 17 Feb 2000 16:50:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002180050.QAA03318@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: current@FreeBSD.ORG Subject: Re: MegaRAID 428 vs 466 and a way to wedge the controller In-reply-to: Your message of "Thu, 17 Feb 2000 19:30:01 EST." <4.2.2.20000217192443.045cedf0@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 17 Feb 2000 16:50:40 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > At 04:19 PM 2/17/2000 -0800, Mike Smith wrote: > >Hmm. I flashed my PERC 2 up to the latest AMI firmware, and with about a > >dozen bonnie processes running it took about 30 seconds for the controller > >to lock up completely (I had to power-cycle it to get it to come back). > > Is this a purely amr box ? I had been testing it out only on 1 partition > mounted as /mnt. Although all access to the AMI is hosed, access to my IDE > is without issue. No, same setup. I have a terminator with a bunch of pretty LEDs on it on the back of the disk box, and the SCSI bus was most surely wedged solid. I've backed off to 4 tags per drive from their "advanced" tag detection (these are 9GB cheetahs) and it's not dying on me now, so I'm fairly certain it's either firmware or firmware:drive interaction. 8( > >I wouldn't say you have a firmware issue there yet, but it's not looking > >very good. > > What rev of the firmware were you using before hand ? the 3.00 from Dell > ? Like I said, without this rev, I could not do anything with the > card. From the release notes, it would seem the card has some issues with > modern BIOSes The latest Dell firmware was working OK; I'm now using the AMI GH6D firmware and as above with tags backed off it was OK for a bit - the box just spontaneously rebooted though, so I'm not so sure it's happy. 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 17: 3:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id D714337B8CC; Thu, 17 Feb 2000 17:03:04 -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 UAA82497; Thu, 17 Feb 2000 20:03:02 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id UAA19810; Thu, 17 Feb 2000 20:03:01 -0500 (EST) Message-Id: <4.2.2.20000217195946.04682de8@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Thu, 17 Feb 2000 20:02:05 -0500 To: Mike Smith From: Mike Tancsa Subject: Re: MegaRAID 428 vs 466 and a way to wedge the controller Cc: current@FreeBSD.ORG In-Reply-To: <200002180050.QAA03318@mass.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 04:50 PM 2/17/2000 -0800, Mike Smith wrote: > > At 04:19 PM 2/17/2000 -0800, Mike Smith wrote: > > >Hmm. I flashed my PERC 2 up to the latest AMI firmware, and with about a > > >dozen bonnie processes running it took about 30 seconds for the controller > > >to lock up completely (I had to power-cycle it to get it to come back). > > > > Is this a purely amr box ? I had been testing it out only on 1 partition > > mounted as /mnt. Although all access to the AMI is hosed, access to my > IDE > > is without issue. > >No, same setup. I have a terminator with a bunch of pretty LEDs on it on >the back of the disk box, and the SCSI bus was most surely wedged solid. >I've backed off to 4 tags per drive from their "advanced" tag detection >(these are 9GB cheetahs) and it's not dying on me now, so I'm fairly >certain it's either firmware or firmware:drive interaction. 8( Hmmm... I forgot to check what the tag settings was on the controller. But I am using 9GIG quantum Atlas IIIs. But on mine, I dont get a complete lock up. Just cant talk to the RAID drives. The latest Dell firmware was working OK; I'm now using the AMI GH6D >firmware and as above with tags backed off it was OK for a bit - the box >just spontaneously rebooted though, so I'm not so sure it's happy. 8( Yikes. It hasnt done that to me. ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 17:47:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id C084237B8F2; Thu, 17 Feb 2000 17:47:24 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id SAA26371; Thu, 17 Feb 2000 18:15:43 -0800 (PST) Date: Thu, 17 Feb 2000 18:15:43 -0800 From: Alfred Perlstein To: current@FreeBSD.org Cc: Mark Murray , committers@FreeBSD.org Subject: Re: Crypto progress! (And a Biiiig TODO list) Message-ID: <20000217181543.G21720@fw.wintelcom.net> References: <200002172130.XAA23664@gratis.grondar.za> <200002180127.UAA83711@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002180127.UAA83711@khavrinen.lcs.mit.edu>; from wollman@khavrinen.lcs.mit.edu on Thu, Feb 17, 2000 at 08:27:23PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Garrett Wollman [000217 17:55] wrote: > < said: > > > o I want to completely dekerberise userland, and only have kerberos > > via PAMs. A ton of work, and I have just started with this. > > Huh? PAM is Pluggable Authentication Modules, not Pluggable Protocol > Modules.... It's unlikely that `rlogin' (for example) could be made > to work this way. (Of course, Kerberized `rlogin' is currently broken > already, and has been for months, so perhaps I'm the only person left > who cares.) > > > o A daemon that userland can query for password checking; this is to > > get around the current requirement that things that need master.passwd > > access need to be suid root. It works, but needs tidying up, review > > and a PAM to query it. Not far to go! > > I'm very uncomfortable with requiring Yet Another Daemon to manage > (and screw up) password checking. Generally speaking, if I wouldn't > trust a program with root privileges, I wouldn't trust it with my > password, either (for obvious reasons). Yes, but the benifits of a correct implementation are quite awesome, a centralized logging place to dole out authentication and potentially administratively shutdown/lockout accounts if a brute force attempt (or other abuse) is detected. -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 18: 3:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id A2B5F37B8EB; Thu, 17 Feb 2000 18:03:35 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id VAA43659; Thu, 17 Feb 2000 21:03:32 -0500 (EST) Date: Thu, 17 Feb 2000 21:03:32 -0500 (EST) From: "Matthew N. Dodd" To: Alfred Perlstein Cc: current@FreeBSD.org, Mark Murray , committers@FreeBSD.org Subject: Re: Crypto progress! (And a Biiiig TODO list) In-Reply-To: <20000217181543.G21720@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Alfred Perlstein wrote: > Yes, but the benifits of a correct implementation are quite awesome, > a centralized logging place to dole out authentication and potentially > administratively shutdown/lockout accounts if a brute force attempt (or > other abuse) is detected. You've just described Kerberos. -- | 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-current" in the body of the message From owner-freebsd-current Thu Feb 17 18:48:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id AB14637B55D for ; Thu, 17 Feb 2000 18:48:33 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12LdSx-000CBf-00; Fri, 18 Feb 2000 08:48:23 +0600 Date: Fri, 18 Feb 2000 08:48:23 +0600 (ALMT) From: Boris Popov To: The Hermit Hacker Cc: freebsd-current@freebsd.org Subject: Re: [mount_nwfs] Got it!! But ... In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, The Hermit Hacker wrote: > Great, finally figured out what I was missing for the mount_nwfs command congrats... > How do I get it to automount on reboot? From what I can tell, you have to > be root to do it ... but, you have to enter a passwd when you do it this > way, so its not something you can add to /etc/fstab when a machine reboots fstab(5) entries can be used to specify options for connection and should be marked as 'noauto' (see man mount_nwfs(8)). Please take a look at /usr/share/examples/nwclient/nwfs.sh.sample file. Line 14 of it sets and exports HOME variable. Nothing prevents you to set this variable to "/home/fred" and call mount_nwfs with "-O fred" argument. Of course, fred has to specify NetWare password in his .nwfsrc file. > So farr as I can tell, this is great for a single-user environemnt, but > not multi-user, but it could just be a doc I'm missing ... I've got reports where ncplib supports more than 10K users. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 18:57:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from pinhead.parag.codegen.com (207-44-235-154.CodeGen.COM [207.44.235.154]) by hub.freebsd.org (Postfix) with ESMTP id 8523A37B838 for ; Thu, 17 Feb 2000 18:57:18 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (parag@localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.9.3/8.9.3) with ESMTP id SAA88034; Thu, 17 Feb 2000 18:34:55 -0800 (PST) (envelope-from parag@pinhead.parag.codegen.com) To: Greg Lehey Cc: current@FreeBSD.ORG Subject: Re: FWIW: More questionable softupdates+vinum benchmarks In-Reply-To: Message from Greg Lehey of "Fri, 18 Feb 2000 08:50:06 +1030." <20000218085006.D24604@freebie.lemis.com> X-Image-URL: http://www.codegen.com/images/CG-logo-only.gif X-URL: http://www.codegen.com X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm Date: Thu, 17 Feb 2000 18:34:54 -0800 Message-ID: <88030.950841294@pinhead.parag.codegen.com> From: Parag Patel Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000 08:50:06 +1030, Greg Lehey wrote: > >Could you change the values of VINUM_MAXACTIVE and >DRIVE_MAXACTIVE (in /sys/dev/vinum/vinumvar.h) to 30000 each >(effectively disabling the throttling), recompile the kld and try >again please? It didn't make any significant difference: find /usr/src | cpio -pdum /target (~600k blocks): /noraid (1 drive, softupdates): 901.70s real 6.32s user 135.73s system 944.64s real 6.40s user 135.49s system (*MAXACTIVE to 30000) buildworld -j16: src & obj on /noraid volume (1 drive, softupdates) 6053.86 real 7969.94 user 7601.81 sys 6040.56 real 7933.80 user 7643.17 sys (*MAXACTIVE to 30000) (The /*raid* volumes are all on the 5 older SCSI disks, but the rest of the system is on a newer IDE disk, which is why the IDE times are better.) -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 19: 2:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id 1B78E37B838 for ; Thu, 17 Feb 2000 19:02:51 -0800 (PST) (envelope-from tstromberg@rtci.com) Received: from rtci.com (karma [208.11.244.6]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with ESMTP id WAA14173 for ; Thu, 17 Feb 2000 22:04:03 -0500 (EST) Message-ID: <38ACB658.70007@rtci.com> Date: Thu, 17 Feb 2000 22:02:48 -0500 From: Thomas Stromberg User-Agent: Mozilla 5.0 [en-US] (FreeBSD; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: procfs crash in -CURRENT (multi-read) Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Just letting you guys know, the nasty multiple-read bug in procfs still exists. I'm preparing a new smashwidgets report for 4.0 (should be ready for tommorow, will post here), and in the process happened to shoot myself in the foot by having two breakwidgets scripts go simultaneously. breakwidgets reads /proc quite a bit (actually, with a minimized copy of /usr/bin/killall), and things go bad when "worlds collide".

So if any of you decide to play with multiple /proc readers, use locks :0 Please note that this crash is very very hard for me to duplicate.. this is after about 32 hours of running the script that does the proc read.

(full vmcore, conf, and kernel.debug available on request)..

FreeBSD karma.afterthought.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Feb 14 23:00:42 GMT 2000     chenresig@karma.afterthought.org:/usr/src/sys/compile/KARMA  i386

dumping to dev #ad/0x20001, offset 1109472
dump ata0: resetting devices .. done
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=256) at ../../kern/kern_shutdown.c:304
304                     dumppcb.pcb_cr3 = rcr3();
(kgdb) bt
#0  boot (howto=256) at ../../kern/kern_shutdown.c:304
#1  0xc014e194 in poweroff_wait (junk=0xc02b9480, howto=-871862272) at ../../kern/kern_shutdown.c:554
#2  0xc022d064 in vm_fault (map=0xc031ee28, vaddr=3423105024, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_fault.c:240
#3  0xc02810d2 in trap_pfault (frame=0xcc136cc4, usermode=0, eva=3423108180) at ../../i386/i386/trap.c:788
#4  0xc0280d37 in trap (frame={tf_fs = -871170032, tf_es = -871170032, tf_ds = 16, tf_edi = -871142055, tf_esi = -871142025,
     tf_ebp = -871141804, tf_isp = -871142160, tf_ebx = -872323392, tf_edx = 0, tf_ecx = -872323392, tf_eax = -871859336, tf_trapno = 12,
     tf_err = 0, tf_eip = -1072160861, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = 0}) at ../../i386/i386/trap.c:423
#5  0xc0181fa3 in procfs_dostatus (curp=0xcc145e00, p=0xcc0166c0, pfs=0xc14abf60, uio=0xcc136eec) at ../../miscfs/procfs/procfs_status.c:115
#6  0xc0182590 in procfs_rw (ap=0xcc136ea0) at ../../miscfs/procfs/procfs_subr.c:277
#7  0xc017dc0a in vn_read (fp=0xc14431c0, uio=0xcc136eec, cred=0xc1450700, flags=0, p=0xcc145e00) at vnode_if.h:334
#8  0xc015ac50 in dofileread (p=0xcc145e00, fp=0xc14431c0, fd=6, buf=0x8235000, nbyte=4096, offset=-1, flags=0) at ../../sys/file.h:140
#9  0xc015ab57 in read (p=0xcc145e00, uap=0xcc136f80) at ../../kern/sys_generic.c:111
#10 0xc028167e in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077946820, tf_esi = 672915688, tf_ebp = -1077946996,
     tf_isp = -871141420, tf_ebx = 672858084, tf_edx = 672809512, tf_ecx = 136531968, tf_eax = 3, tf_trapno = 0, tf_err = 2,
     tf_eip = 672818732, tf_cs = 31, tf_eflags = 659, tf_esp = -1077947040, tf_ss = 47}) at ../../i386/i386/trap.c:1055
#11 0xc0276646 in Xint0x80_syscall ()

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 19: 8:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.butya.kz (butya-gw.butya.kz [212.154.129.94]) by hub.freebsd.org (Postfix) with ESMTP id AB58137B64D for ; Thu, 17 Feb 2000 19:08:49 -0800 (PST) (envelope-from bp@butya.kz) Received: from bp (helo=localhost) by relay.butya.kz with local-esmtp (Exim 3.13 #1) id 12LdmQ-000CDu-00; Fri, 18 Feb 2000 09:08:30 +0600 Date: Fri, 18 Feb 2000 09:08:30 +0600 (ALMT) From: Boris Popov To: Dan Nelson Cc: The Hermit Hacker , freebsd-current@FreeBSD.ORG Subject: Re: [mount_nwfs] Got it!! But ... In-Reply-To: <20000217122919.B11137@dan.emsphone.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 17 Feb 2000, Dan Nelson wrote: > > I've looked at the man page and the .nwfsrc file, but there is a > > 'flaw' there, and that is what does one do in a multi-user > > environment, where I want to mount n users netware drives to the > > system on reboot? they have to give me their netware passwords? > > This is where Terry joins in, and talks about per-user credentials. > The problem is that the unix mount style (mount as root, and limit > access on the client as users access files) doesn't mesh well with the > Netware/SMB model (one independant mount per user). Yeah, this problem exists. Someone with good design and programming skills really should sit down and write session manager. While this isn't done I've made some workarounds in the ncplib to achieve same goals: Connection to netware server have the same the same attributes as file, eg. access mode, owner id, group id. This allows to make private conections which is not visible to other users. Since there is no way to ask user about password at boot time, there is a 'password' variable which works as persistent password "cache". There is also another way to do that, I'm calling it as "lazy mounts". If mount point is marked as "lazy" then it mounted on boot as normal mount but no netware login is performed and user sees typical SYS:LOGIN files. After that, user can issue an "mount_nwfs /home/fred/nwmount" command and enter password at promt. May be this method will be implemented in the next version of ncplib. -- Boris Popov http://www.butya.kz/~bp/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 21:30:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 900B337B998; Thu, 17 Feb 2000 21:30:51 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA37823; Thu, 17 Feb 2000 21:30:49 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38ACD908.E756C802@gorean.org> Date: Thu, 17 Feb 2000 21:30:48 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: "Jordan K. Hubbard" Cc: freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 References: <7327.950809955@zippy.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" wrote: > Hmmm. Odd, I've always noted the opposite. If you do the novice install > (which everyone should if they're trying to test the "typical case"), I've always found the term "novice" to be a little off-putting. Perhaps "Standard Install" would be a better choice? Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 21:46:24 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id CB1D937B971; Thu, 17 Feb 2000 21:46:16 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id HAA25779; Fri, 18 Feb 2000 07:46:11 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200002180546.HAA25779@gratis.grondar.za> To: current@freebsd.org Cc: committers@freebsd.org Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <200002180127.UAA83711@khavrinen.lcs.mit.edu> In-Reply-To: <200002180127.UAA83711@khavrinen.lcs.mit.edu> ; from Garrett Wollman "Thu, 17 Feb 2000 20:27:23 EST." Date: Fri, 18 Feb 2000 07:46:11 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I'm very uncomfortable with requiring Yet Another Daemon to manage > (and screw up) password checking. Generally speaking, if I wouldn't > trust a program with root privileges, I wouldn't trust it with my > password, either (for obvious reasons). If "all those" suid programs could be "de-suid'ed", and replaced with a simple "does this username/password pair check out?" daemon/module, would that make you happier? M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 21:47:41 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id E76FB37B957; Thu, 17 Feb 2000 21:47:32 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id HAA25799; Fri, 18 Feb 2000 07:47:19 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200002180547.HAA25799@gratis.grondar.za> To: Alfred Perlstein Cc: current@FreeBSD.org, committers@FreeBSD.org Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <20000217181543.G21720@fw.wintelcom.net> In-Reply-To: <20000217181543.G21720@fw.wintelcom.net> ; from Alfred Perlstein "Thu, 17 Feb 2000 18:15:43 PST." Date: Fri, 18 Feb 2000 07:47:18 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > I'm very uncomfortable with requiring Yet Another Daemon to manage > > (and screw up) password checking. Generally speaking, if I wouldn't > > trust a program with root privileges, I wouldn't trust it with my > > password, either (for obvious reasons). > > Yes, but the benifits of a correct implementation are quite awesome, > a centralized logging place to dole out authentication and potentially > administratively shutdown/lockout accounts if a brute force attempt (or > other abuse) is detected. My thoughts pretty much close to exactly! M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 22:30: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by hub.freebsd.org (Postfix) with ESMTP id 492DF37B82D; Thu, 17 Feb 2000 22:29:54 -0800 (PST) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id B0DDE1CD9; Fri, 18 Feb 2000 14:29:47 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Mark Murray Cc: current@freebsd.org, committers@freebsd.org Subject: Re: Crypto progress! (And a Biiiig TODO list) In-Reply-To: Message from Mark Murray of "Fri, 18 Feb 2000 07:46:11 +0200." <200002180546.HAA25779@gratis.grondar.za> Date: Fri, 18 Feb 2000 14:29:47 +0800 From: Peter Wemm Message-Id: <20000218062947.B0DDE1CD9@overcee.netplex.com.au> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Mark Murray wrote: > > I'm very uncomfortable with requiring Yet Another Daemon to manage > > (and screw up) password checking. Generally speaking, if I wouldn't > > trust a program with root privileges, I wouldn't trust it with my > > password, either (for obvious reasons). > > If "all those" suid programs could be "de-suid'ed", and replaced with > a simple "does this username/password pair check out?" daemon/module, > would that make you happier? As long as there is some sort of rate limiting system so that it doesn't provide a trivial online brute force password cracking service... Getting this right would be an interesting challenge. :-) Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 22:33:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 8A0C237B53C; Thu, 17 Feb 2000 22:33:37 -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 RAA06961; Fri, 18 Feb 2000 17:02:50 +1030 (CST) (envelope-from doconnor@gsoft.com.au) 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: <20000218062947.B0DDE1CD9@overcee.netplex.com.au> Date: Fri, 18 Feb 2000 17:02:50 +1030 (CST) From: "Daniel O'Connor" To: Peter Wemm Subject: Re: Crypto progress! (And a Biiiig TODO list) Cc: committers@freebsd.org, current@freebsd.org, Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 18-Feb-00 Peter Wemm wrote: > As long as there is some sort of rate limiting system so that it doesn't > provide a trivial online brute force password cracking service... Getting > this right would be an interesting challenge. :-) --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 23:43:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 72A5E37B893; Thu, 17 Feb 2000 23:43:38 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id JAA26529; Fri, 18 Feb 2000 09:43:03 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200002180743.JAA26529@gratis.grondar.za> To: Peter Wemm Cc: current@freebsd.org, committers@freebsd.org Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <20000218062947.B0DDE1CD9@overcee.netplex.com.au> In-Reply-To: <20000218062947.B0DDE1CD9@overcee.netplex.com.au> ; from Peter Wemm "Fri, 18 Feb 2000 14:29:47 +0800." Date: Fri, 18 Feb 2000 09:43:03 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Mark Murray wrote: > > > I'm very uncomfortable with requiring Yet Another Daemon to manage > > > (and screw up) password checking. Generally speaking, if I wouldn't > > > trust a program with root privileges, I wouldn't trust it with my > > > password, either (for obvious reasons). > > > > If "all those" suid programs could be "de-suid'ed", and replaced with > > a simple "does this username/password pair check out?" daemon/module, > > would that make you happier? > > As long as there is some sort of rate limiting system so that it doesn't > provide a trivial online brute force password cracking service... Getting > this right would be an interesting challenge. :-) Easy to do of the daemon is not on by default, or if it is pretty fascist by default, with lots of options to define the fascism. Examples: o A username may only be checked $number times per $timeperiod; after that, _all_ answers are silently converted to "no". o Daemon may only be invoked $number times per $timeperiod; refuses to fork after that. o Daemon will delay $timeperiod before returning answer. ... etc. There are possibilities for DoS attacks, but the daemon talks only to a Unix Domain Socket, so finding the perp is easy. Logging can be as fascist or minimalist as you like. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Thu Feb 17 23:51:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from ns1.sunesi.net (ns1.sunesi.net [196.15.192.194]) by hub.freebsd.org (Postfix) with ESMTP id C49E637B803; Thu, 17 Feb 2000 23:51:24 -0800 (PST) (envelope-from nbm@sunesi.net) Received: from nbm by ns1.sunesi.net with local (Exim 3.03 #1) id 12LiBX-000KtC-00; Fri, 18 Feb 2000 09:50:43 +0200 Date: Fri, 18 Feb 2000 09:50:43 +0200 From: Neil Blakey-Milner To: "Matthew N. Dodd" Cc: Alfred Perlstein , current@FreeBSD.org, Mark Murray , committers@FreeBSD.org Subject: Re: Crypto progress! (And a Biiiig TODO list) Message-ID: <20000218095042.A80194@mithrandr.moria.org> References: <20000217181543.G21720@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Organization: Sunesi Clinical Systems X-Operating-System: FreeBSD 3.3-RELEASE i386 X-URL: http://rucus.ru.ac.za/~nbm/ Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu 2000-02-17 (21:03), Matthew N. Dodd wrote: > On Thu, 17 Feb 2000, Alfred Perlstein wrote: > > Yes, but the benifits of a correct implementation are quite awesome, > > a centralized logging place to dole out authentication and potentially > > administratively shutdown/lockout accounts if a brute force attempt (or > > other abuse) is detected. > > You've just described Kerberos. No, he just described something, amongst many many other things that might not be useful for mere mortals, that Kerberos can do. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 2:58:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from shale.csir.co.za (shale.csir.co.za [146.64.46.5]) by hub.freebsd.org (Postfix) with ESMTP id AD27237B86F; Fri, 18 Feb 2000 02:58:33 -0800 (PST) (envelope-from reg@shale.csir.co.za) Received: from granite.hip.berkeley.edu (granite.hip.berkeley.edu [136.152.155.25]) by shale.csir.co.za (8.9.3/8.9.3) with ESMTP id MAA92570; Fri, 18 Feb 2000 12:57:11 +0200 (SAT) (envelope-from reg@shale.csir.co.za) Received: (from reg@localhost) by granite.hip.berkeley.edu (8.9.3/8.9.3) id CAA32649; Fri, 18 Feb 2000 02:56:29 -0800 (PST) (envelope-from reg) Date: Fri, 18 Feb 2000 02:56:28 -0800 From: Jeremy Lea To: unfurl@freebsd.org, jkh@freebsd.org, current@freebsd.org Subject: Fix for -CURRENT breakage in libc_r Message-ID: <20000218025627.A21724@shale.csir.co.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Please people. If you think you don't need a make world during a code freeze, then please at least read the patched files... Index: Makefile.inc =================================================================== RCS file: /usr/home/ncvs/src/lib/libc_r/man/Makefile.inc,v retrieving revision 1.10 diff -u -r1.10 Makefile.inc --- Makefile.inc 2000/02/18 05:31:26 1.10 +++ Makefile.inc 2000/02/18 10:49:38 @@ -37,9 +37,6 @@ pthread_rwlockattr_init.3 \ pthread_rwlockattr_setpshared.3 \ pthread_self.3 \ - -MLINKS+=pthread_rwlock_wrlock.3 pthread_rwlock_trywrlock.3 -MLINKS+=pthread_rwlock_rdlock.3 pthread_rwlock_tryrdlock.3 \ pthread_setspecific.3 \ pthread_testcancel.3 \ sem_destroy.3 \ @@ -49,8 +46,10 @@ sem_post.3 \ sem_wait.3 -MLINKS+= pthread_cancel.3 pthread_setcancelstate.3 \ - pthread_cancel.3 pthread_getcancelstate.3 \ +MLINKS+= pthread_cancel.3 pthread_getcancelstate.3 \ + pthread_cancel.3 pthread_setcancelstate.3 \ + pthread_rwlock_rdlock.3 pthread_rwlock_tryrdlock.3 \ + pthread_rwlock_wrlock.3 pthread_rwlock_trywrlock.3 \ sem_open.3 sem_close.3 \ sem_open.3 sem_unlink.3 \ sem_wait.3 sem_trywait.3 -Jeremy -- FreeBSD - Because the best things in life are free... http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 3:10:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from rock.gnt.kiev.ua (rock.gnt.kiev.ua [62.244.5.121]) by hub.freebsd.org (Postfix) with ESMTP id 4CB8A37B795 for ; Fri, 18 Feb 2000 03:10:29 -0800 (PST) (envelope-from cob@rock.gnt.kiev.ua) Received: (from cob@localhost) by rock.gnt.kiev.ua (8.9.3/8.9.3) id NAA18321; Fri, 18 Feb 2000 13:10:16 +0200 (EET) To: freebsd-current@FreeBSD.ORG Subject: IP tunnel Reply-To: cob@gnt.kiev.ua X-Class: Fast X-Mailer: GNU Emacs 20.4.4 (i386-unknown-freebsd2.2.1, X toolkit) Organization: Genet, Ltd. From: Cob Date: 18 Feb 2000 13:10:16 +0200 Message-ID: <87og9eg413.fsf@rock.gnt.kiev.ua> Lines: 8 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! What about ${subj} in current? Or maybe someone know how to make ip tunnel on current using patches, tools, etc.? Thanx. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 4:30:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id AE45C37B7DB; Fri, 18 Feb 2000 04:30:33 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id OAA26421; Fri, 18 Feb 2000 14:28:46 +0200 (EET) (envelope-from ru) Date: Fri, 18 Feb 2000 14:28:46 +0200 From: Ruslan Ermilov To: Garrett Wollman , Bruce Evans , Peter Wemm Cc: committers@FreeBSD.org, current@FreeBSD.org, dcs@FreeBSD.org Subject: Re: pstat(8) depends on loader(8)??? Message-ID: <20000218142846.A14682@relay.ucb.crimea.ua> Mail-Followup-To: Garrett Wollman , Bruce Evans , Peter Wemm , committers@FreeBSD.org, current@FreeBSD.org, dcs@FreeBSD.org References: <20000207141429.64F221CDD@overcee.netplex.com.au> <20000207002551.A69709@relay.ucb.crimea.ua> <20000207002551.A69709@relay.ucb.crimea.ua> <200002070238.VAA24590@khavrinen.lcs.mit.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i In-Reply-To: <200002070238.VAA24590@khavrinen.lcs.mit.edu>; from Garrett Wollman on Sun, Feb 06, 2000 at 09:38:41PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi! Why then it works on 3.4-STABLE (booting without loader(8) and having kvm(3) programs like pstat(8) and top(1) working). What makes a difference here? On Sun, Feb 06, 2000 at 09:38:41PM -0500, Garrett Wollman wrote: > < said: > > > If I boot with loader(8), everything is ok. > > Ideas? > > loader loads the kernel symbol table; boot2 does not. > > -GAWollman On Mon, Feb 07, 2000 at 03:22:36PM +1100, Bruce Evans wrote: > On Mon, 7 Feb 2000, Ruslan Ermilov wrote: > > > If I boot the system without loader(8), e.g. with /boot.config=kernel, > > or by interrupting boot blocks and typing /kernel, swapinfo(8) fails: > > > > swapinfo: undefined symbol: _numvnodes > > This is because the elf format puts static symbols in an out-of-the-way > section, and the boot2 stage of the bootstrap loads sections naively. > Static symbols end up in a place where the kernel linker can't find > them. `numvnodes' is a static symbol... Global symbols are found > correctly. > > This bug has affected ddb for more than a year. I don't believe in > or use loader(8), and have "fixed" the problem in ddb by not using > the kernel linker for ddb symbol lookup. This also fixes the > nonexistence of ddb symbols on booting with -d. > > Bruce On Mon, Feb 07, 2000 at 10:14:29PM +0800, Peter Wemm wrote: > Garrett Wollman wrote: > > < said: > > > > > If I boot with loader(8), everything is ok. > > > Ideas? > > > > loader loads the kernel symbol table; boot2 does not. > > > > -GAWollman > > More to the point, a non-stripped kernel has *two* symbol tables. One that > has the global symbols and is used for dynamic linking, and the other that > has the debugging info in it including static symbols. loader(8) goes to a > great deal of trouble to get the second table - it's very hard to get it > when reading from a zlib decompression stream that can't be seek'ed. The ELF > format defines a convenient 'load segment' table which defines (usually) > two chunks of the file to be loaded into memory and at what addresses. The > verbose symbol table is not part of this, but the global table is and we get > it for free. > > Anyway, the correct fix is to make numvnodes global or to change it to a > sysctl. Nothing that is referred to by the common libkvm applications > should be static - this warning has been given before. running a strip on / > kernel has the same effect as using boot2 - only global symbols are > accessible. > > Cheers, > -Peter -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 4:59:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id A55EC37B926 for ; Fri, 18 Feb 2000 04:59:44 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id VAA02453; Fri, 18 Feb 2000 21:58:57 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id VAA18361; Fri, 18 Feb 2000 21:58:56 +0900 (JST) Received: from localhost ([192.168.245.179]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id VAA25483; Fri, 18 Feb 2000 21:58:53 +0900 (JST) To: bmah@CA.Sandia.GOV Cc: bmah@california.sandia.gov, bauer@cc.univie.ac.at, current@FreeBSD.ORG Subject: Re: IPv6 In-Reply-To: <20000216034713O.shin@nd.net.fujitsu.co.jp> References: <20000215041550J.shin@nd.net.fujitsu.co.jp> <200002142150.NAA15862@nimitz.ca.sandia.gov> <20000216034713O.shin@nd.net.fujitsu.co.jp> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Multipart/Mixed; boundary="--Next_Part(Fri_Feb_18_21:59:33_2000_885)--" Content-Transfer-Encoding: 7bit Message-Id: <20000218215940K.shin@nd.net.fujitsu.co.jp> Date: Fri, 18 Feb 2000 21:59:40 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 325 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG ----Next_Part(Fri_Feb_18_21:59:33_2000_885)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit > I fixed it and other problems, and added another changes. (In > particular, I mistakenly left my testing part in router > case. Sorry.) > I'll attach the new diffs. I still made more several fixes to IPv6 configuration scripts. -changed the file rc.net6 to rc.network6 -changed the func net6_pass1 to network6_pass1 -changed several var name more unlikely to confilict -changed if several sentenses in rc.network6 to case sentence like in rc.network -wrapped many var names by {} -and other fixes I believe now it successfully configure each of router and host case, very well. Please try it anyone interested. Thanks, Yoshinobu Inoue ----Next_Part(Fri_Feb_18_21:59:33_2000_885)-- Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="rc.diff" Index: defaults/rc.conf =================================================================== RCS file: /home/ncvs/src/etc/defaults/rc.conf,v retrieving revision 1.48 diff -u -r1.48 rc.conf --- defaults/rc.conf 2000/02/06 19:25:00 1.48 +++ defaults/rc.conf 2000/02/18 12:53:06 @@ -184,6 +184,32 @@ ### Miscellaneous network options: ### icmp_bmcastecho="NO" # respond to broadcast ping packets +### IPv6 options: ### +ipv6_enable="NO" # Set to YES to set up for IPv6. +ipv6_network_interfaces="auto" # List of network interfaces (or "auto"). +ipv6_gateway_enable="NO" # Set to YES if this host will be a gateway. +ipv6_router_enable="NO" # Set to YES to enable an IPv6 routing daemon. +ipv6_router="/usr/sbin/route6d" # Name of IPv6 routing daemon. +ipv6_router_flags="" # Flags to IPv6 routing daemon. +#ipv6_router_flags="-l" # Example for route6d with only IPv6 site local + # addrs. +#ipv6_network_interfaces="ed0 ep0" # Examples for router. + # Choose correct prefix value. +#ipv6_prefix_ed0="fec0:0000:0000:0001 fec0:0000:0000:0002" # Examples for rtr. +#ipv6_prefix_ep0="fec0:0000:0000:0003 fec0:0000:0000:0004" # Examples for rtr. +prefixcmd_enable="YES" # Use prefix command to assigne router prefix. +rtadvd_enable="NO" # Set to YES to enable an IPv6 router + # advertisement daemon. +mroute6d_enable="NO" # Do IPv6 multicast routing. +mroute6d_program="/usr/sbin/pim6dd" # Name of IPv6 multicast routing + # daemon. +mroute6d_flags="" # Flags to IPv6 multicast routing daemon. +gif_interfaces="NO" # List of GIF tunnels (or "NO"). +#gif_interfaces="gif0 gif1" # Examples typically for a router. + # Choose correct tunnel addrs. +#gifconfig_gif0="10.1.1.1 10.1.2.1" # Examples typically for a router. +#gifconfig_gif1="10.1.1.2 10.1.2.2" # Examples typically for a router. +ipv6_default_interface="lo0" # Default output interface for scoped addrs. ############################################################## ### System console options ################################# Index: rc =================================================================== RCS file: /home/ncvs/src/etc/rc,v retrieving revision 1.210 diff -u -r1.210 rc --- rc 2000/02/03 06:06:36 1.210 +++ rc 2000/02/18 12:53:07 @@ -191,6 +191,15 @@ network_pass1 fi +case ${ipv6_enable} in +[Yy][Ee][Ss]) + if [ -r /etc/rc.network6 ]; then + . /etc/rc.network6 # We only need to do this once also. + network6_pass1 + fi + ;; +esac + # Mount NFS filesystems. echo -n "Mounting NFS file systems" mount -a -t nfs Index: rc.network6 =================================================================== RCS file: rc.network6 diff -N rc.network6 --- /dev/null Fri Feb 18 03:29:51 2000 +++ rc.network6 Fri Feb 18 04:53:07 2000 @@ -0,0 +1,219 @@ +#! /bin/sh +# $FreeBSD$ + +# Note that almost all of the user-configurable behavior is no longer in +# this file, but rather in /etc/defaults/rc.conf. Please check that file +# first before contemplating any changes here. If you do need to change +# this file for some reason, we would like to know about it. + +# IPv6 startup + +network6_pass1() { + echo -n 'Doing IPv6 network setup:' + + case ${ipv6_gateway_enable} in + [Yy][Ee][Ss]) + # + # list of interfaces, and prefix for interfaces + # + case ${ipv6_network_interfaces} in + [Aa][Uu][Tt][Oo]) + ipv6_network_interfaces="`ifconfig -l`" + ;; + esac + ;; + *) + # + # manual configurations - in case ip6_gateway_enable=NO + # you can configure only single interface, + # as specification assumes that + # autoconfigured host has single interface only. + # + case ${ipv6_network_interfaces} in + [Aa][Uu][Tt][Oo]) + ipv6_network_interfaces="`ifconfig -l \ + | sed -e 's/ .*//'`" + ;; + esac + ;; + esac + + # just to make sure + ifconfig lo0 up + + # disallow unicast packets without outgoing scope identifiers. + # if you instead want to route such packets to a "default" interface, + # comment out the 1st two lines, and enable the lines after them. + case ${ipv6_default_interface} in + '') + route add -inet6 fe80:: -prefixlen 10 ::1 -reject + ;; + *) + laddr=`ifconfig ${ipv6_default_interface} inet6 \ + | grep 'inet6 fe80:' | head -1 | awk '{print $2}'` + route add -inet6 fe80:: ${laddr} -prefixlen 10 -interface \ + -cloning + route add -inet6 ff02:: ${laddr} -prefixlen 16 -interface \ + -cloning + ;; + esac + + # disallow "internal" addresses to appear on the wire + route add -inet6 ::ffff:0.0.0.0 -prefixlen 96 ::1 -reject + route add -inet6 ::0.0.0.0 -prefixlen 96 ::1 -reject + + case ${ipv6_gateway_enable} in + [Yy][Ee][Ss]) + # act as a router + sysctl -w net.inet6.ip6.forwarding=1 + sysctl -w net.inet6.ip6.accept_rtadv=0 + + # wait for DAD + for i in $ipv6_network_interfaces; do + ifconfig $i up + done + sleep `sysctl net.inet6.ip6.dad_count | awk '{print $NF}'` + sleep 1 + + # setting up interfaces + for i in $ipv6_network_interfaces; do + eval prefix=\$ipv6_prefix_$i + case ${prefix} in + '') + continue; + ;; + esac + for j in ${prefix}; do + case ${prefixcmd_enable} in + [Yy][Ee][Ss]) + prefix $i $j:: + ;; + *) + laddr=`ifconfig $i inet6 \ + | grep 'inet6 fe80:' \ + | head -1 | awk '{print $2}'` + hostid=`echo ${laddr} | sed \ + -e 's/fe80:[0-9a-fA-F]+::/fe80::/' \ + -e 's/fe80:://' -e 's/@.*//'` + address=$j\:${hostid} + + eval hostid_$i=${hostid} + eval address_$i=${address} + + ifconfig $i inet6 ${address} \ + prefixlen 64 alias + ;; + esac + + # subnet-router anycast address (rfc2373) + ifconfig $i inet6 $j:: prefixlen 64 \ + alias anycast + done + + ifconfig $i inet6 + done + + # again, wait for DAD's completion (for global addrs) + sleep `sysctl net.inet6.ip6.dad_count | awk '{print $NF}'` + sleep 1 + + # gifconfig + network6_gif_setup + + # ipv6_router + case ${ipv6_router_enable} in + [Yy][Ee][Ss]) + if [ -x ${ipv6_router} ]; then + echo -n " ${ipv6_router}" + ${ipv6_router} ${ipv6_router_flags} + fi + ;; + esac + + # rtadvd + # This should enabled with a great care. + # You may want to fine-tune /etc/rtadvd.conf. + # + # And if you wish your rtadvd to receive and process + # router renumbering messages, specify your Router Renumbering + # security policy by -P option. + # + # See `man 3 ipsec_set_policy` for IPsec policy specification + # details. + # (CAUTION: This enables your routers prefix renumbering + # from another machine, so if you enable this, do it with + # enough care.) + # + case ${rtadvd_enable} in + [Yy][Ee][Ss]) + # default + rtadvd ${ipv6_network_interfaces} + # + # Enable Router Renumbering, unicaset case + # (use correct src/dst addr) + # rtadvd -P "in ipsec ah/transport/fec0:0:0:1::1-fec0:0:0:10::1/require" \ + ${ipv6_network_interfaces} + # Enable Router Renumbering, multicast case + # (use correct src addr) + # rtadvd -P "in ipsec ah/transport/ff05::2-fec0:0:0:10::1/require" \ + ${ipv6_network_interfaces} + ;; + esac + + # mroute6d + case ${mroute6d_enable} in + [Yy][Ee][Ss]) + if [ -x ${mroute6d_program} ]; then + echo -n " ${mroute6d_program}" + ${mroute6d_program} ${mroute6d_flags} + fi + ;; + esac + ;; + *) + # act as endhost - automatically configured + sysctl -w net.inet6.ip6.forwarding=0 + sysctl -w net.inet6.ip6.accept_rtadv=1 + + ifconfig ${ipv6_network_interfaces} up + rtsol ${ipv6_network_interfaces} + + # install the "default interface" to kernel, which will be used + # as the default route when there's no router. + # ndp -I ${ipv6_default_interface} + + # wait for DAD's completion (for global addrs) + sleep `sysctl net.inet6.ip6.dad_count | awk '{print $NF}'` + sleep 1 + + # gifconfig + network6_gif_setup + ;; + esac + + echo '.' + + # Let future generations know we made it. + # + network6_pass1_done=YES +} + +network6_gif_setup() { + case ${gif_interfaces} in + [Nn][Oo] | '') + ;; + *) + for i in ${gif_interfaces}; do + eval peers=\$gifconfig_$i + case ${peers} in + '') + continue + ;; + *) + gifconfig $i ${peers} + ;; + esac + done + ;; + esac +} ----Next_Part(Fri_Feb_18_21:59:33_2000_885)---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 6:12:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from logger.gamma.ru (logger.gamma.ru [194.186.254.23]) by hub.freebsd.org (Postfix) with ESMTP id 9B57E37B599 for ; Fri, 18 Feb 2000 06:12:17 -0800 (PST) (envelope-from ivt@logger.gamma.ru) Received: (from ivt@localhost) by logger.gamma.ru (8.9.3/8.9.3) id RAA92165; Fri, 18 Feb 2000 17:11:49 +0300 (MSK) From: Igor Timkin Message-Id: <200002181411.RAA92165@logger.gamma.ru> Subject: Re: IP tunnel In-Reply-To: <87og9eg413.fsf@rock.gnt.kiev.ua> from Cob at "Feb 18, 2000 01:10:16 pm" To: cob@gnt.kiev.ua Date: Fri, 18 Feb 2000 17:11:49 +0300 (MSK) Cc: freebsd-current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL61 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG nos-tun. > > Hello! > > What about ${subj} in current? > Or maybe someone know how to make > ip tunnel on current using patches, tools, etc.? > > Thanx. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 6:29:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id B59EA37B94A; Fri, 18 Feb 2000 06:29:46 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p12-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.77]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id XAA05961; Fri, 18 Feb 2000 23:29:39 +0900 (JST) Message-ID: <38AD571D.C5B53079@newsguy.com> Date: Fri, 18 Feb 2000 23:28:45 +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: Doug Barton Cc: "Jordan K. Hubbard" , freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 References: <7327.950809955@zippy.cdrom.com> <38ACD908.E756C802@gorean.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Doug Barton wrote: > > "Jordan K. Hubbard" wrote: > > > Hmmm. Odd, I've always noted the opposite. If you do the novice install > > (which everyone should if they're trying to test the "typical case"), > > I've always found the term "novice" to be a little off-putting. Perhaps > "Standard Install" would be a better choice? Novice is ok, it's the other two that are problematic. Well, particularly "custom". "Custom" does not scare away anyone, and is actually actractive to Windows users. It should be called "death trap" or something like that... -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 6:55:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from barracuda.aquarium.rtci.com (barracuda.aquarium.rtci.com [208.11.247.5]) by hub.freebsd.org (Postfix) with ESMTP id 6CC2D37B6FA for ; Fri, 18 Feb 2000 06:55:43 -0800 (PST) (envelope-from tstromberg@rtci.com) Received: from barracuda (barracuda [208.11.247.5]) by barracuda.aquarium.rtci.com (8.9.3+Sun/8.9.3) with ESMTP id JAA28820 for ; Fri, 18 Feb 2000 09:56:54 -0500 (EST) Date: Fri, 18 Feb 2000 09:56:50 -0500 (EST) From: Thomas Stromberg X-Sender: tstromberg@barracuda.aquarium.rtci.com To: freebsd-current@freebsd.org Subject: repost of procfs crashes in -CURRENT (no html).. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Sorry about the html posting, it seems that Mozilla M13 decided to rape my message. I hate html postings just as much as you do (thank god for procmail filters), and will send this one using pine so Mozilla doesn't try to rethink my e-mail for me. Kernel: ======= FreeBSD karma.afterthought.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Feb 14 23:00:42 GMT 2000 chenresig@karma.afterthought.org:/usr/src/sys/compile/KARMA i386 Background: ============ 3 users. One with X running , and two users running breakwidgets , which make use of a minimized version of the "killall" perl script which reads procfs. This crash appears to be the old one where when two processes read procfs simultaneously, ugly things can happen. mdillon described this in more depth to me once but I've since lost the e-mail. . He suggested having my programs "lock" procfs reads so only one could do it's killall function at a time. Unfortunatly, the binary testing script is very time sensitive and this would slow things down The kernel is a GENERIC one with ipv6, softupdates, and pcm added to it. Crash #1: ========= (kgdb) bt #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 #1 0xc014e194 in poweroff_wait (junk=0xc02b9480, howto=-871862272) at ../../kern/kern_shutdown.c:554 #2 0xc022d064 in vm_fault (map=0xc031ee28, vaddr=3423105024, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_fault.c:240 #3 0xc02810d2 in trap_pfault (frame=0xcc136cc4, usermode=0, eva=3423108180) at ../../i386/i386/trap.c:788 #4 0xc0280d37 in trap (frame={tf_fs = -871170032, tf_es = -871170032, tf_ds = 16, tf_edi = -871142055, tf_esi = -871142025, tf_ebp = -871141804, tf_isp = -871142160, tf_ebx = -872323392, tf_edx = 0, tf_ecx = -872323392, tf_eax = -871859336, tf_trapno = 12, tf_err = 0, tf_eip = -1072160861, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = 0}) at ../../i386/i386/trap.c:423 #5 0xc0181fa3 in procfs_dostatus (curp=0xcc145e00, p=0xcc0166c0, pfs=0xc14abf60, uio=0xcc136eec) at ../../miscfs/procfs/procfs_status.c:115 #6 0xc0182590 in procfs_rw (ap=0xcc136ea0) at ../../miscfs/procfs/procfs_subr.c:277 #7 0xc017dc0a in vn_read (fp=0xc14431c0, uio=0xcc136eec, cred=0xc1450700, flags=0, p=0xcc145e00) at vnode_if.h:334 #8 0xc015ac50 in dofileread (p=0xcc145e00, fp=0xc14431c0, fd=6, buf=0x8235000, nbyte=4096, offset=-1, flags=0) at ../../sys/file.h:140 #9 0xc015ab57 in read (p=0xcc145e00, uap=0xcc136f80) at ../../kern/sys_generic.c:111 #10 0xc028167e in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077946820, tf_esi = 672915688, tf_ebp = -1077946996, tf_isp = -871141420, tf_ebx = 672858084, tf_edx = 672809512, tf_ecx = 136531968, tf_eax = 3, tf_trapno = 0, tf_err = 2, tf_eip = 672818732, tf_cs = 31, tf_eflags = 659, tf_esp = -1077947040, tf_ss = 47}) at ../../i386/i386/trap.c:1055 Crash #2: ========= #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 #1 0xc014e194 in poweroff_wait (junk=0xc02b9480, howto=-873472000) at ../../kern/kern_shutdown.c:554 #2 0xc022d064 in vm_fault (map=0xc031ee28, vaddr=3421495296, fault_type=1 '\001', fault_flags=0) at ../../vm/vm_fault.c:240 #3 0xc02810d2 in trap_pfault (frame=0xcbe0ccc4, usermode=0, eva=3421498452) at ../../i386/i386/trap.c:788 #4 0xc0280d37 in trap (frame={tf_fs = -874512368, tf_es = -874512368, tf_ds = 16, tf_edi = -874459817, tf_esi = -874459788, tf_ebp = -874459564, tf_isp = -874459920, tf_ebx = -873997056, tf_edx = 0, tf_ecx = -873997056, tf_eax = -873469064, tf_trapno = 12, tf_err = 0, tf_eip = -1072160861, tf_cs = 8, tf_eflags = 66118, tf_esp = 0, tf_ss = 0}) at ../../i386/i386/trap.c:423 #5 0xc0181fa3 in procfs_dostatus (curp=0xcbd7df20, p=0xcbe7dd00, pfs=0xc154ac20, uio=0xcbe0ceec) at ../../miscfs/procfs/procfs_status.c:115 #6 0xc0182590 in procfs_rw (ap=0xcbe0cea0) at ../../miscfs/procfs/procfs_subr.c:277 #7 0xc017dc0a in vn_read (fp=0xc1469200, uio=0xcbe0ceec, cred=0xc153d180, flags=0, p=0xcbd7df20) at vnode_if.h:334 #8 0xc015ac50 in dofileread (p=0xcbd7df20, fp=0xc1469200, fd=5, buf=0x8253000, nbyte=4096, offset=-1, flags=0) at ../../sys/file.h:140 #9 0xc015ab57 in read (p=0xcbd7df20, uap=0xcbe0cf80) at ../../kern/sys_generic.c:111 #10 0xc028167e in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, tf_edi = -1077945828, tf_esi = 136638564, tf_ebp = -1077946004, tf_isp = -874459180, tf_ebx = 672858084, tf_edx = 672809512, tf_ecx = 136654848, tf_eax = 3, tf_trapno = 0, tf_err = 2, tf_eip = 672818732, tf_cs = 31, tf_eflags = 663, tf_esp = -1077946048, tf_ss = 47}) at ../../i386/i386/trap.c:1055 #11 0xc0276646 in Xint0x80_syscall () To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 6:59:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id D6F4E37B988 for ; Fri, 18 Feb 2000 06:59:51 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.freebsd.dk [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id PAA03738; Fri, 18 Feb 2000 15:59:43 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Thomas Stromberg Cc: freebsd-current@FreeBSD.ORG Subject: Re: repost of procfs crashes in -CURRENT (no html).. In-reply-to: Your message of "Fri, 18 Feb 2000 09:56:50 EST." Date: Fri, 18 Feb 2000 15:59:43 +0100 Message-ID: <3736.950885983@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The real solution is to make killall(1)s funtionality part of kill(1) and avoid reading /proc so that we don't even have to mount /proc. Poul-Henning In message , Thomas Stromberg writes: >3 users. One with X running , and two users running breakwidgets >, which make use of a minimized version of the >"killall" perl script which reads procfs. > >This crash appears to be the old one where when two processes read procfs >simultaneously, ugly things can happen. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 7:12:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from spoon.beta.com (h00a0242f177e.ne.mediaone.net [24.218.8.93]) by hub.freebsd.org (Postfix) with ESMTP id 0F56D37B6FA; Fri, 18 Feb 2000 07:12:32 -0800 (PST) (envelope-from mcgovern@spoon.beta.com) Received: from spoon.beta.com (mcgovern@localhost.beta.com [127.0.0.1]) by spoon.beta.com (8.9.3/8.9.3) with ESMTP id KAA01992; Fri, 18 Feb 2000 10:12:20 -0500 (EST) (envelope-from mcgovern@spoon.beta.com) Message-Id: <200002181512.KAA01992@spoon.beta.com> To: "Daniel C. Sobral" Cc: Doug Barton , "Jordan K. Hubbard" , freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG, mcgovern@spoon.beta.com Subject: Re: feedback on CD install of 4.0-RC2 In-reply-to: Your message of "Fri, 18 Feb 2000 23:28:45 +0900." <38AD571D.C5B53079@newsguy.com> Date: Fri, 18 Feb 2000 10:12:20 -0500 From: "Brian J. McGovern" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Doug Barton wrote: > > > > "Jordan K. Hubbard" wrote: > > > > > Hmmm. Odd, I've always noted the opposite. If you do the novice instal l > > > (which everyone should if they're trying to test the "typical case"), > > > > I've always found the term "novice" to be a little off-putting. Pe rhaps > > "Standard Install" would be a better choice? > > Novice is ok, it's the other two that are problematic. Well, > particularly "custom". "Custom" does not scare away anyone, and is > actually actractive to Windows users. It should be called "death trap" > or something like that... I don't know if I agree. "Custom" is exactly what it says... You can build out the system with specifically the components you want. Now, perhaps I'm out of the ordinary here, but I _always_ use custom. Of course, of the 100+ machines that run it around here, each can have a very different purpose, so it makes sense to slice it that way. Also, as far as teaching new users how to install it, I _always_ show them the custom route. While this may sound harsh, its used to familarize them with all of sub-components, and what-does-what. Given that these systems can also run up to 3-4 operating systems, and the installations are not clear-cut, it makes more sense. As they become familar with it, they branch off, and use the installation method that most suits their needs. Now, I'll admit, that custom may be a bit daunting to people who are new to Operating Systems. But, even in the Windows enviornment, "Custom Installations" are usually documented as a route for those who are clue as to what they're doing, and "Standard" or "Quick" installs are for the others. In the end, I don't think you should put a negative vibe on the things that do exactly what they say they do. If you check my rulebook, rule number one is "People are stupid". If they're novices, and they stray off the "novice" path laid out for them, they're gonna get what they get. Part of any learning process is learning your limits. :) Anyhow, enough rant. I've just seen enough badmouthing of "custom" over the years that I want to speak up. It does what it claims to do. Leave it alone. -Brian > -- > Daniel C. Sobral (8-DCS) > dcs@newsguy.com > dcs@freebsd.org > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 7:22:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from reliant.nielsenmedia.com (reliant.nielsenmedia.com [205.129.32.15]) by hub.freebsd.org (Postfix) with ESMTP id D138337B817 for ; Fri, 18 Feb 2000 07:22:14 -0800 (PST) (envelope-from David_W_Gray@tvratings.com) Received: from nmrusdunsxg0.nielsenmedia.com (nmrusdunsxg0.nielsenmedia.com [10.9.11.120]) by reliant.nielsenmedia.com (8.9.3/8.9.3) with ESMTP id KAA19286 for ; Fri, 18 Feb 2000 10:22:13 -0500 (EST) Received: by nmrusdunsxg0.nielsenmedia.com with Internet Mail Service (5.5.2448.0) id ; Fri, 18 Feb 2000 10:22:12 -0500 Message-ID: <01D4D419B1A4D111A30400805FE65B13033661FC@nmrusdunsx1.nielsenmedia.com> From: "Gray, David W." To: "'FreeBSD Current list'" Subject: Rc2 install Date: Fri, 18 Feb 2000 10:22:10 -0500 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've come to the conclusion that the -current stuff really doesn't install on an 8 Meg machine anymore. I have an old 486/66 machine I'm using to play with the current-RC's, and it consistantly dies loading the 'bin' stuff. This isn't really a complaint -- after the load & boot cycle, there is only 2.4M free according to the boot messages, so I can see why this would fill up. (I wound up loading the drive on another box that usually drives my printer, 386/25 and 24M, talk about S.L.O.W). And it can't quite compile a kernel in one go, either. Perhaps the release notes, or hardware file need to note you really do need more than 8M ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 7:23:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 71EC337B99E for ; Fri, 18 Feb 2000 07:23:21 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id KAA41134 for ; Fri, 18 Feb 2000 10:24:10 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Fri, 18 Feb 2000 10:24:10 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-current@freebsd.org Subject: break in libcrypto? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Was wondering if anyone else was seeing this one. I'm following the jail(8) build directions on the 02-14 snapshot. I've had the build directions work previously, so I'm a little puzzled. During the make all phase, I get the errors below. I cvsup'd this morning, but still get the same results. Here's the output from make all: cc -fpic -DPIC -O -pipe -DTERMIOS -DANSI_SOURCE -DNO_IDEA -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto -I/usr/obj/usr/src/secure/lib/libcrypto -DL_ENDIAN -DDEVRANDOM=\"/dev/urandom\" -DNO_RSA -DNO_SSL2 -c /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cversion.c -o cversion.So /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cversion.c:64: buildinf.h: No such file or directory /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cversion.c:64: buildinf.h: No such file or directory /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cversion.c:64: buildinf.h: No such file or directory *** Error code 1 *** Error code 1 *** Error code 1 3 errors *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error *** Error code 2 1 error Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 7:27:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id A220937B956 for ; Fri, 18 Feb 2000 07:27:42 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id KAA41179 for ; Fri, 18 Feb 2000 10:28:36 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Fri, 18 Feb 2000 10:28:36 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: freebsd-current@freebsd.org Subject: Re: break in libcrypto? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG A further data point: I was building with a -j, so maybe there's a dependency mixup with the beforedepend target? If I manually cd to the directory and do a make beforedepend, things continue naturally from there. On Fri, 18 Feb 2000, Robert Watson wrote: > > Was wondering if anyone else was seeing this one. I'm following the > jail(8) build directions on the 02-14 snapshot. I've had the build > directions work previously, so I'm a little puzzled. During the make all > phase, I get the errors below. I cvsup'd this morning, but still get the > same results. Here's the output from make all: > > cc -fpic -DPIC -O -pipe -DTERMIOS -DANSI_SOURCE -DNO_IDEA > -I/usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto > -I/usr/obj/usr/src/secure/lib/libcrypto -DL_ENDIAN > -DDEVRANDOM=\"/dev/urandom\" -DNO_RSA -DNO_SSL2 -c > /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cversion.c -o > cversion.So > /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cversion.c:64: > buildinf.h: No such file or directory > /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cversion.c:64: > buildinf.h: No such file or directory > /usr/src/secure/lib/libcrypto/../../../crypto/openssl/crypto/cversion.c:64: > buildinf.h: No such file or directory > *** Error code 1 > *** Error code 1 > *** Error code 1 > 3 errors > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > *** Error code 2 > 1 error > > > > Robert N M Watson > > robert@fledge.watson.org http://www.watson.org/~robert/ > PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 > TIS Labs at Network Associates, Safeport Network Services > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 7:52:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id CF6BD37B599; Fri, 18 Feb 2000 07:52:41 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA86342; Fri, 18 Feb 2000 10:52:37 -0500 (EST) (envelope-from wollman) Date: Fri, 18 Feb 2000 10:52:37 -0500 (EST) From: Garrett Wollman Message-Id: <200002181552.KAA86342@khavrinen.lcs.mit.edu> To: "Daniel C. Sobral" Cc: Doug Barton , "Jordan K. Hubbard" , freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 In-Reply-To: <38AD571D.C5B53079@newsguy.com> References: <7327.950809955@zippy.cdrom.com> <38ACD908.E756C802@gorean.org> <38AD571D.C5B53079@newsguy.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Novice is ok, it's the other two that are problematic. Well, > particularly "custom". "Custom" does not scare away anyone, and is > actually actractive to Windows users. It should be called "death trap" > or something like that... Huh? -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 7:56:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 3C48937B599 for ; Fri, 18 Feb 2000 07:56:16 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id KAA86357; Fri, 18 Feb 2000 10:56:07 -0500 (EST) (envelope-from wollman) Date: Fri, 18 Feb 2000 10:56:07 -0500 (EST) From: Garrett Wollman Message-Id: <200002181556.KAA86357@khavrinen.lcs.mit.edu> To: Mark Murray Cc: current@FreeBSD.org Subject: Re: Crypto progress! (And a Biiiig TODO list) In-Reply-To: <200002180743.JAA26529@gratis.grondar.za> References: <20000218062947.B0DDE1CD9@overcee.netplex.com.au> <200002180743.JAA26529@gratis.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > o A username may only be checked $number times per $timeperiod; > after that, _all_ answers are silently converted to "no". Easier: a username may only be checked by a process running as $uid or by root. > ... etc. There are possibilities for DoS attacks, but the daemon > talks only to a Unix Domain Socket, so finding the perp is easy. And what happens when the daemon is dead, has crashed, or was never started? -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 8:27:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from lor.watermarkgroup.com (lor.watermarkgroup.com [207.202.73.33]) by hub.freebsd.org (Postfix) with ESMTP id BFCE737B989 for ; Fri, 18 Feb 2000 08:27:30 -0800 (PST) (envelope-from luoqi@watermarkgroup.com) Received: (from luoqi@localhost) by lor.watermarkgroup.com (8.8.8/8.8.8) id LAA15059; Fri, 18 Feb 2000 11:27:27 -0500 (EST) (envelope-from luoqi) Date: Fri, 18 Feb 2000 11:27:27 -0500 (EST) From: Luoqi Chen Message-Id: <200002181627.LAA15059@lor.watermarkgroup.com> To: freebsd-current@FreeBSD.ORG, tstromberg@rtci.com Subject: Re: repost of procfs crashes in -CURRENT (no html).. Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kernel: > ======= > FreeBSD karma.afterthought.org 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Mon Feb > 14 23:00:42 GMT 2000 > chenresig@karma.afterthought.org:/usr/src/sys/compile/KARMA i386 > > Background: > ============ > 3 users. One with X running , and two users running breakwidgets > , which make use of a minimized version of the > "killall" perl script which reads procfs. > > This crash appears to be the old one where when two processes read procfs > simultaneously, ugly things can happen. mdillon described this in more > depth to me once but I've since lost the e-mail. reports in late November & early december>. He suggested having my > programs "lock" procfs reads so only one could do it's killall function at > a time. Unfortunatly, the binary testing script is very time sensitive and > this would slow things down paralleled on 4 machines> > I don't believe that's the cause. > The kernel is a GENERIC one with ipv6, softupdates, and pcm added to it. > > Crash #1: > ========= > (kgdb) bt > #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 > #1 0xc014e194 in poweroff_wait (junk=0xc02b9480, howto=-871862272) at > ../../kern/kern_shutdown.c:554 > #2 0xc022d064 in vm_fault (map=0xc031ee28, vaddr=3423105024, fault_type=1 > '\001', fault_flags=0) at ../../vm/vm_fault.c:240 > #3 0xc02810d2 in trap_pfault (frame=0xcc136cc4, usermode=0, > eva=3423108180) at ../../i386/i386/trap.c:788 > #4 0xc0280d37 in trap (frame={tf_fs = -871170032, tf_es = -871170032, > tf_ds = 16, tf_edi = -871142055, tf_esi = -871142025, > tf_ebp = -871141804, tf_isp = -871142160, tf_ebx = -872323392, > tf_edx = 0, tf_ecx = -872323392, tf_eax = -871859336, > tf_trapno = 12, tf_err = 0, tf_eip = -1072160861, tf_cs = 8, > tf_eflags = 66118, tf_esp = 0, tf_ss = 0}) > at ../../i386/i386/trap.c:423 > #5 0xc0181fa3 in procfs_dostatus (curp=0xcc145e00, p=0xcc0166c0, > pfs=0xc14abf60, uio=0xcc136eec) > at ../../miscfs/procfs/procfs_status.c:115 The fault is taken when trying to access the target process' p_stats which resides in the u area. What's interesting here is the code checks P_INMEM flag prior to accessing p_stats, so there shouldn't be a fault. My guess is this is an embryonic process, the p_stats field is inherited from the corpse of another process which points to no where. Would you print out p->p_stat (not p_stats) and check if it is 1 (SIDL)? That would confirm my theory. If this indeed is the case, the fix should be delaying setting P_INMEM flags in fork() until after the u area is allocated. It maybe also a good idea to skip embryonic processes in procfs altogether. > #6 0xc0182590 in procfs_rw (ap=0xcc136ea0) at > ../../miscfs/procfs/procfs_subr.c:277 > #7 0xc017dc0a in vn_read (fp=0xc14431c0, uio=0xcc136eec, cred=0xc1450700, > flags=0, p=0xcc145e00) at vnode_if.h:334 > #8 0xc015ac50 in dofileread (p=0xcc145e00, fp=0xc14431c0, fd=6, > buf=0x8235000, nbyte=4096, offset=-1, flags=0) > at ../../sys/file.h:140 > #9 0xc015ab57 in read (p=0xcc145e00, uap=0xcc136f80) at > ../../kern/sys_generic.c:111 > #10 0xc028167e in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = -1077946820, tf_esi = 672915688, > tf_ebp = -1077946996, tf_isp = -871141420, tf_ebx = 672858084, > tf_edx = 672809512, tf_ecx = 136531968, tf_eax = 3, > tf_trapno = 0, tf_err = 2, tf_eip = 672818732, tf_cs = 31, tf_eflags > = 659, tf_esp = -1077947040, tf_ss = 47}) > at ../../i386/i386/trap.c:1055 > > > > Crash #2: > ========= > #0 boot (howto=256) at ../../kern/kern_shutdown.c:304 > #1 0xc014e194 in poweroff_wait (junk=0xc02b9480, howto=-873472000) at > ../../kern/kern_shutdown.c:554 > #2 0xc022d064 in vm_fault (map=0xc031ee28, vaddr=3421495296, fault_type=1 > '\001', fault_flags=0) at ../../vm/vm_fault.c:240 > #3 0xc02810d2 in trap_pfault (frame=0xcbe0ccc4, usermode=0, > eva=3421498452) at ../../i386/i386/trap.c:788 > #4 0xc0280d37 in trap (frame={tf_fs = -874512368, tf_es = -874512368, > tf_ds = 16, tf_edi = -874459817, tf_esi = -874459788, > tf_ebp = -874459564, tf_isp = -874459920, tf_ebx = -873997056, > tf_edx = 0, tf_ecx = -873997056, tf_eax = -873469064, > tf_trapno = 12, tf_err = 0, tf_eip = -1072160861, tf_cs = 8, > tf_eflags = 66118, tf_esp = 0, tf_ss = 0}) > at ../../i386/i386/trap.c:423 > #5 0xc0181fa3 in procfs_dostatus (curp=0xcbd7df20, p=0xcbe7dd00, > pfs=0xc154ac20, uio=0xcbe0ceec) > at ../../miscfs/procfs/procfs_status.c:115 > #6 0xc0182590 in procfs_rw (ap=0xcbe0cea0) at > ../../miscfs/procfs/procfs_subr.c:277 > #7 0xc017dc0a in vn_read (fp=0xc1469200, uio=0xcbe0ceec, cred=0xc153d180, > flags=0, p=0xcbd7df20) at vnode_if.h:334 > #8 0xc015ac50 in dofileread (p=0xcbd7df20, fp=0xc1469200, fd=5, > buf=0x8253000, nbyte=4096, offset=-1, flags=0) > at ../../sys/file.h:140 > #9 0xc015ab57 in read (p=0xcbd7df20, uap=0xcbe0cf80) at > ../../kern/sys_generic.c:111 > #10 0xc028167e in syscall (frame={tf_fs = 47, tf_es = 47, tf_ds = 47, > tf_edi = -1077945828, tf_esi = 136638564, > tf_ebp = -1077946004, tf_isp = -874459180, tf_ebx = 672858084, > tf_edx = 672809512, tf_ecx = 136654848, tf_eax = 3, > tf_trapno = 0, tf_err = 2, tf_eip = 672818732, tf_cs = 31, tf_eflags > = 663, tf_esp = -1077946048, tf_ss = 47}) > at ../../i386/i386/trap.c:1055 > #11 0xc0276646 in Xint0x80_syscall () > -lq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 8:29:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 4E8BF37B926; Fri, 18 Feb 2000 08:29:19 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta11/8.10.0.Beta6) with ESMTP id e1IGS9P48266; Fri, 18 Feb 2000 09:28:09 -0700 (MST) Message-Id: <200002181628.e1IGS9P48266@orthanc.ab.ca> To: Mark Murray Cc: Peter Wemm , current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: Crypto progress! (And a Biiiig TODO list) In-reply-to: Your message of "Fri, 18 Feb 2000 09:43:03 +0200." <200002180743.JAA26529@gratis.grondar.za> Date: Fri, 18 Feb 2000 09:28:09 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Mark" == Mark Murray writes: Mark> o A username may only be checked $number times per Mark> $timeperiod; after that, _all_ answers are silently Mark> converted to "no". Umm, massive DOS hole. Mark> o Daemon may only be invoked $number times per $timeperiod; Mark> refuses to fork after that. Another massive DOS hole. Mark> o Daemon will delay $timeperiod before returning answer. This is the correct way to deal with (perceived) attacks. Mark> ... etc. There are possibilities for DoS attacks, but the Mark> daemon talks only to a Unix Domain Socket, so finding the Mark> perp is easy. Not if the daemon has shut itself off due to load (#1 or #2 above) and you aren't currently logged in to the box. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 8:31: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 4470437B9D0 for ; Fri, 18 Feb 2000 08:30:57 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta11/8.10.0.Beta6) with ESMTP id e1IGUhP48289; Fri, 18 Feb 2000 09:30:43 -0700 (MST) Message-Id: <200002181630.e1IGUhP48289@orthanc.ab.ca> To: Garrett Wollman Cc: Mark Murray , current@FreeBSD.ORG Subject: Re: Crypto progress! (And a Biiiig TODO list) In-reply-to: Your message of "Fri, 18 Feb 2000 10:56:07 EST." <200002181556.KAA86357@khavrinen.lcs.mit.edu> Date: Fri, 18 Feb 2000 09:30:43 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Garrett" == Garrett Wollman writes: Garrett> And what happens when the daemon is dead, has crashed, or Garrett> was never started? You incorporate my patches to inetd that teach it to listen on named sockets, and then run the daemon from there in wait mode. If inetd dies you're pretty much hosed, anyway. --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 8:33:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 6BC1C37B997 for ; Fri, 18 Feb 2000 08:33:27 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id LAA86511; Fri, 18 Feb 2000 11:33:19 -0500 (EST) (envelope-from wollman) Date: Fri, 18 Feb 2000 11:33:19 -0500 (EST) From: Garrett Wollman Message-Id: <200002181633.LAA86511@khavrinen.lcs.mit.edu> To: Lyndon Nerenberg Cc: Garrett Wollman , Mark Murray , current@FreeBSD.ORG Subject: Re: Crypto progress! (And a Biiiig TODO list) In-Reply-To: <200002181630.e1IGUhP48289@orthanc.ab.ca> References: <200002181556.KAA86357@khavrinen.lcs.mit.edu> <200002181630.e1IGUhP48289@orthanc.ab.ca> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > You incorporate my patches to inetd that teach it to listen on > named sockets, and then run the daemon from there in wait mode. > If inetd dies you're pretty much hosed, anyway. Think ``single-user mode''. -GAWollman To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 8:33:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from happy.checkpoint.com (happy.checkpoint.com [199.203.156.224]) by hub.freebsd.org (Postfix) with ESMTP id 705AD37B9BF for ; Fri, 18 Feb 2000 08:33:31 -0800 (PST) (envelope-from mellon@happy.checkpoint.com) Received: (from mellon@localhost) by happy.checkpoint.com (8.9.3/8.9.3) id SAA02961; Fri, 18 Feb 2000 18:34:21 GMT (envelope-from mellon) Date: Fri, 18 Feb 2000 18:34:21 +0000 From: Anatoly Vorobey To: "Daniel C. Sobral" Cc: freebsd-current@freebsd.org Subject: Re: feedback on CD install of 4.0-RC2 Message-ID: <20000218183421.A2896@happy.checkpoint.com> References: <7327.950809955@zippy.cdrom.com> <38ACD908.E756C802@gorean.org> <38AD571D.C5B53079@newsguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <38AD571D.C5B53079@newsguy.com>; from dcs@newsguy.com on Fri, Feb 18, 2000 at 11:28:45PM +0900 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 11:28:45PM +0900, Daniel C. Sobral wrote: > > Novice is ok, it's the other two that are problematic. Well, > particularly "custom". "Custom" does not scare away anyone, and is > actually actractive to Windows users. It should be called "death trap" > or something like that... I'm actually scared by "novice" because it would be inflicting on me defaults I would almost probably not want. I never run anything but "custom", and I suspect many people do the same. -- Anatoly Vorobey, mellon@pobox.com http://pobox.com/~mellon/ "Angels can fly because they take themselves lightly" - G.K.Chesterton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 8:44:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 6862637B9DA for ; Fri, 18 Feb 2000 08:44:24 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta11/8.10.0.Beta6) with ESMTP id e1IGiMP48348; Fri, 18 Feb 2000 09:44:22 -0700 (MST) Message-Id: <200002181644.e1IGiMP48348@orthanc.ab.ca> To: Garrett Wollman Cc: current@FreeBSD.ORG Subject: Re: Crypto progress! (And a Biiiig TODO list) In-reply-to: Your message of "Fri, 18 Feb 2000 11:33:19 EST." <200002181633.LAA86511@khavrinen.lcs.mit.edu> Date: Fri, 18 Feb 2000 09:44:21 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Garrett" == Garrett Wollman writes: >> You incorporate my patches to inetd that teach it to listen on >> named sockets, and then run the daemon from there in wait mode. >> If inetd dies you're pretty much hosed, anyway. Garrett> Think ``single-user mode''. In single user mode you're root by definition. If init wants roots password before going single user it can certainly go directly to the password file. (It's really no different than if you're serving up passwords via NIS.) --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 8:55:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id C679637B9E1; Fri, 18 Feb 2000 08:55:33 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id IAA22416; Fri, 18 Feb 2000 08:54:49 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id IAA01047; Fri, 18 Feb 2000 08:54:49 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id IAA22477; Fri, 18 Feb 2000 08:54:41 -0800 (PST) Message-ID: <38AD7AE3.B4BEB308@softweyr.com> Date: Fri, 18 Feb 2000 10:01:23 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Lyndon Nerenberg Cc: Mark Murray , Peter Wemm , current@freebsd.org, committers@freebsd.org Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <200002181628.e1IGS9P48266@orthanc.ab.ca> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lyndon Nerenberg wrote: > > >>>>> "Mark" == Mark Murray writes: > > Mark> o A username may only be checked $number times per > Mark> $timeperiod; after that, _all_ answers are silently > Mark> converted to "no". > > Umm, massive DOS hole. Per username. If you publish your userlist, you're an idiot. The daemon should also immediately go into "breakin evasion mode" for all invalid usernames, answering the requests very slowly. > Mark> o Daemon may only be invoked $number times per $timeperiod; > Mark> refuses to fork after that. > > Another massive DOS hole. Right, this one doesn't fly. > Mark> o Daemon will delay $timeperiod before returning answer. > > This is the correct way to deal with (perceived) attacks. Please, not for a single valid request, or even two. Let's give the user the opportunity to login, and perhaps to goober their password once, before screwing them. > Mark> ... etc. There are possibilities for DoS attacks, but the > Mark> daemon talks only to a Unix Domain Socket, so finding the > Mark> perp is easy. > > Not if the daemon has shut itself off due to load (#1 or #2 above) and you > aren't currently logged in to the box. Sure there is, it's called logging. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 8:59:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 9AD1D37B9D7; Fri, 18 Feb 2000 08:59:05 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id LAA41621; Fri, 18 Feb 2000 11:59:02 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Fri, 18 Feb 2000 11:59:02 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Lyndon Nerenberg Cc: Mark Murray , Peter Wemm , current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: Crypto progress! (And a Biiiig TODO list) In-Reply-To: <200002181628.e1IGS9P48266@orthanc.ab.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Another technique that could be used, and gets discussed occasionally on -security, is passing authentication information via ancillary data transfer on UNIX domain sockets. You could limit the effectiveness of DOS attacks by rate limiting per-uid, for example. It should be noted that both the old and new schemes are subject to denial of service--the old due to locking, and the new due to socket/IPC limits, among other things. I would argue, however, that the new mechanism reduces risk as it would allow us to remove the setuid bit from a number of binaries, instead relying on a single auditable code base in the password file manager. If we plan to move to more daemons using IPC to communicate in this style, we might want to think about consistency guidelines for doing this. For example, mandating an LPC structure of some sort, or managing parallelism on a single pipe, etc. Also, documenting techniques that tend to reduce the risk of denial of service for daemons offering IPC services. Robert On Fri, 18 Feb 2000, Lyndon Nerenberg wrote: > >>>>> "Mark" == Mark Murray writes: > > Mark> o A username may only be checked $number times per > Mark> $timeperiod; after that, _all_ answers are silently > Mark> converted to "no". > > Umm, massive DOS hole. > > Mark> o Daemon may only be invoked $number times per $timeperiod; > Mark> refuses to fork after that. > > Another massive DOS hole. > > Mark> o Daemon will delay $timeperiod before returning answer. > > This is the correct way to deal with (perceived) attacks. > > Mark> ... etc. There are possibilities for DoS attacks, but the > Mark> daemon talks only to a Unix Domain Socket, so finding the > Mark> perp is easy. > > Not if the daemon has shut itself off due to load (#1 or #2 above) and you > aren't currently logged in to the box. > > --lyndon > > Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 9:18:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from p2.acadia.net (p2.acadia.net [205.217.210.2]) by hub.freebsd.org (Postfix) with ESMTP id 9923A37B965 for ; Fri, 18 Feb 2000 09:18:25 -0800 (PST) (envelope-from tbuswell@acadia.net) Received: from smpbox.bogus.net (ip142167011029.acadia.net [142.167.11.29]) by p2.acadia.net (8.9.3/8.9.3) with ESMTP id MAA12690 for ; Fri, 18 Feb 2000 12:19:03 -0500 (EST) Received: (from tbuswell@localhost) by smpbox.bogus.net (8.9.3/8.9.3) id MAA07611; Fri, 18 Feb 2000 12:16:10 -0500 (EST) (envelope-from tbuswell) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 18 Feb 2000 12:16:09 -0500 (EST) To: current@freebsd.org Subject: pccardd and mapping memory descriptors X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14509.31140.445498.751403@localhost.bogus.net> From: tbuswell@acadia.net Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I'm writing a driver that talks to a card that has some SRAM. In the driver I'm trying to get a handle to the memory by doing the following: rid = 0; sc->mem = bus_alloc_resource(dev, SYS_RES_MEMORY, &rid, 0ul, ~0ul, 0, RF_ACTIVE); which fails. Treking through the kernel and userland, I've decided that what's missing is that pccardd never configures the memory region using ioctl(PIOCSMEM). It never does that because the code block in assign_io() that determines that the card does have a memory descriptor, doesn't set the MEM_ASSIGNED bit in sp->flags. I believe setting MEM_ASSIGNED is the proper fix and attached is the one line patch. -Ted PS: anybody know why cardaddr is set to 16k? Index: cardd.c =================================================================== RCS file: /home/ncvs/src/usr.sbin/pccard/pccardd/cardd.c,v retrieving revision 1.46 diff -c -r1.46 cardd.c *** cardd.c 2000/01/26 17:53:59 1.46 --- cardd.c 2000/02/18 01:30:25 *************** *** 487,492 **** --- 487,493 ---- sp->config->driver->mem = sp->mem.addr; } sp->mem.cardaddr = 0x4000; + sp->flags |= MEM_ASSIGNED; if (debug_level > 0) { logmsg("Using mem addr 0x%x, size %d, card addr 0x%x\n", sp->mem.addr, sp->mem.size, sp->mem.cardaddr); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 10:10:57 2000 Delivered-To: freebsd-current@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 B2E7E37B9E6 for ; Fri, 18 Feb 2000 10:10:52 -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 TAA01654 for ; Fri, 18 Feb 2000 19:11:00 +0100 (CET) (envelope-from ohartman@ipamzlx.physik.uni-mainz.de) Date: Fri, 18 Feb 2000 19:11:00 +0100 (CET) From: "O. Hartmann" To: freebsd-current@freebsd.org Subject: HELP! Can not build kernel ... :-( Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello. I followed up the stuff posted here and this evening I want to change one of our smaller server towards FBSD 4.0. Got the CD, have a complete new source tree cvsuped this day and now I make a cd /sys/i386/conf ... Within this directory, I only have the GENERIC, LINT NEWCARD files and my own system's configuration file for building kernel. When typing config MACHINE-NAME the command exits with error config: can't open ../conf/devices.i386 Well, theses files have gone? I thought this could be an cvsupdate error, so I installed the stuff for /sys again from CD. The same! What's new? What's the problem? I got the ISO Image of 4.0-RC2-20000214 and cvsupdated today. Can anybody help? Gruss O. Hartmann ------------------------------------------------------------------- ohartman@ipamzlx.physik.uni-mainz.de Klimadatenserver des IPA, Universitaet Mainz Netzwerk- und Systembetreuung To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 10:19:56 2000 Delivered-To: freebsd-current@freebsd.org Received: from nagual.pp.ru (pobrecita.freebsd.ru [194.87.13.42]) by hub.freebsd.org (Postfix) with ESMTP id A6B4D37B9F3; Fri, 18 Feb 2000 10:19:52 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id VAA61239; Fri, 18 Feb 2000 21:19:51 +0300 (MSK) (envelope-from ache) Date: Fri, 18 Feb 2000 21:19:50 +0300 From: "Andrey A. Chernov" To: current@freebsd.org, shin@freebsd.org Subject: strange code in ftp.c Message-ID: <20000218211950.A61219@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Around ftp.c line 383 I see now: } else if (code == 229) { /* result for EPSV */ pflag = 1; pflag = 100; break; } else Please left only one 'pflag' assignment. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 10:23:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from orion.ac.hmc.edu (Orion.AC.HMC.Edu [134.173.32.20]) by hub.freebsd.org (Postfix) with ESMTP id 2E70E37BA06 for ; Fri, 18 Feb 2000 10:23:45 -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 KAA17695; Fri, 18 Feb 2000 10:20:15 -0800 (PST) Date: Fri, 18 Feb 2000 10:20:15 -0800 From: Brooks Davis To: "O. Hartmann" Cc: freebsd-current@FreeBSD.ORG Subject: Re: HELP! Can not build kernel ... :-( Message-ID: <20000218102015.A15893@orion.ac.hmc.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre4i In-Reply-To: ; from ohartman@ipamzlx.physik.uni-mainz.de on Fri, Feb 18, 2000 at 07:11:00PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 07:11:00PM +0100, O. Hartmann wrote: > Hello. > I followed up the stuff posted here and this evening I want to change one of > our smaller server towards FBSD 4.0. Got the CD, have a complete new > source tree cvsuped this day and now I make a cd /sys/i386/conf ... > Within this directory, I only have the GENERIC, LINT NEWCARD files and > my own system's configuration file for building kernel. When typing > config MACHINE-NAME the command exits with error > > config: can't open ../conf/devices.i386 > > Well, theses files have gone? I thought this could be an cvsupdate error, so > I installed the stuff for /sys again from CD. The same! What's new? What's the > problem? I got the ISO Image of 4.0-RC2-20000214 and cvsupdated today. Can anybody help? They have been removed. You need up update your config and genassym before you can build a 4.0 kernel. Also, I hope your kernel config file is based on a new config and isn't just a copy of a 3.x config since that likely won't work. -- Brooks -- Any statement of the form "X is the one, true Y" is FALSE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 10:26: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by hub.freebsd.org (Postfix) with ESMTP id 3009537B9A4 for ; Fri, 18 Feb 2000 10:26:02 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from nonpc.cs.rice.edu (nonpc.cs.rice.edu [128.42.1.219]) by cs.rice.edu (8.9.0/8.9.0) with ESMTP id MAA13046; Fri, 18 Feb 2000 12:25:54 -0600 (CST) Received: (from alc@localhost) by nonpc.cs.rice.edu (8.9.3/8.7.3) id MAA03001; Fri, 18 Feb 2000 12:25:54 -0600 (CST) Date: Fri, 18 Feb 2000 12:25:54 -0600 From: Alan Cox To: Matthew Dillon Cc: current@freebsd.org Subject: Re: tentitive complete patch for MAP_GUARDED available Message-ID: <20000218122554.A2978@nonpc.cs.rice.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > ... > Resource limits are still an issue. It turns out that the > MAP_STACK code does not deal with the stack resource limit > well at all -- sometimes it catches it, sometimes it doesn't. In what sense? My recollection is that resource limits are enforced on the "regular" process stack but not (except perhaps by accident of placement) on other stacks, such as those created by pthreads. At a higher level, it's not been obvious to me how the resource limit on stack size should be interpreted in a multithreaded program. In other words, I don't see one interpretation as obviously best, much less correct. At least three possibilies are: 1. It represents the maximum size of the "legacy" process stack and nothing else, which is what the code currently implements. (pthreads stacks are bounded by other means.) 2. It represents the maximum size of each and every stack, whether it's the "legacy" process stack or for example a pthreads stack. 3. It represents the sum of the size of all of the stacks. There are problems/drawbacks to each and every possibility. So, in conclusion, I think the first order of business is to determine what semantics (1) there may be good precedent for and (2) that threads programmers are comfortable with. Alan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 10:31:35 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id 127BB37B9EE; Fri, 18 Feb 2000 10:31:33 -0800 (PST) Date: Fri, 18 Feb 2000 10:31:33 -0800 From: "Andrey A. Chernov" To: Yoshinobu Inoue Cc: saxonww@ufl.edu, current@FreeBSD.ORG Subject: Re: Broken FTP Message-ID: <20000218103132.A74763@freebsd.org> References: <20000216155124R.shin@nd.net.fujitsu.co.jp> <20000216101731.A27147@nagual.pp.ru> <20000217180622H.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000217180622H.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Thu, Feb 17, 2000 at 06:06:22PM +0900 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, Feb 17, 2000 at 06:06:22PM +0900, Yoshinobu Inoue wrote: > > > But maybe it is better to print out the first error, as the fact? > > > > I have nothing against EPSV itself, I am against additional verbosity and > > performance degradation since it is tried before _each_ command. > > OK I'll change not to try it once it fails. It seems your last patch _not_ fix the problem. Now I got: ftp> dir 500 'EPSV': command not understood. on first 'dir' command issued. This is with wu-ftpd. Remember that different ftpd's could have slightly different format for response so you should not relay on it much. Could you please try EPSV automatically on _login_ and eat predictable response instead of trying on first user command? In that way you can reflect EPSV-able status in ftp's 'status' command to give user info is remote ftpd EPSV-compatible or not, as I already describe in previous messages. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 10:36:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id DA3C337B9B2; Fri, 18 Feb 2000 10:36:51 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA79209; Fri, 18 Feb 2000 10:36:30 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Brian J. McGovern" Cc: "Daniel C. Sobral" , Doug Barton , freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 In-reply-to: Your message of "Fri, 18 Feb 2000 10:12:20 EST." <200002181512.KAA01992@spoon.beta.com> Date: Fri, 18 Feb 2000 10:36:30 -0800 Message-ID: <79206.950898990@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > it makes sense to slice it that way. Also, as far as teaching new users how > to install it, I _always_ show them the custom route. While this may sound > harsh, its used to familarize them with all of sub-components, and I really kinda wish you'd point them to Novice^H^H^H^H^HStandard instead since it does more than be a bit more verbose, it also makes sure that all the appropriate steps are covered and prevents even relatively skilled people from hanging themselves. Let's take the case someone recently reported: He went and added a user or two using the user configuration tool, THEN went and configured X and the default desktop. Since the default desktop configuration writes the new skeleton files, adding the user(s) first means they all get the stock twm environment since the Desktop config tool is hardly going to go back retroactively and frob every user it can find on the system - that would be evil and bad even if I wanted to add the code to do this. Using the Standard installation, you're presented with all the appropriate checklist items in the *right order* so you don't shoot parts of your anatomy off like this. I will also say here and now that even I use the Standard installation since I don't like having to remember all the canonical steps in setting up a "stock" system and if anybody should remember them, it should be me - I've probably installed FreeBSD at least 50,000 times. :-) Do your friends a favor, point them at the now-not-so-embarassingly-named Standard installation as a matter of course. Custom installation is for those who both understand what they're doing and what they're *not* doing as a consequence of using it. As our desktop friend proved, not even those who think they know the full set of "nots" can escape being proven wrong by Custom. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 10:38:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 084C337B9E6 for ; Fri, 18 Feb 2000 10:38:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA79237; Fri, 18 Feb 2000 10:38:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Gray, David W." Cc: "'FreeBSD Current list'" Subject: Re: Rc2 install In-reply-to: Your message of "Fri, 18 Feb 2000 10:22:10 EST." <01D4D419B1A4D111A30400805FE65B13033661FC@nmrusdunsx1.nielsenmedia.com> Date: Fri, 18 Feb 2000 10:38:38 -0800 Message-ID: <79234.950899118@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Perhaps the release notes, or hardware file need to note you really do need > more than 8M ? The CD boxes all say 16MB and the release notes/hardware guide don't say anything at all about this. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 11: 5:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 1BC9737B9F3 for ; Fri, 18 Feb 2000 11:05:35 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA80267; Fri, 18 Feb 2000 11:05:31 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 11:05:31 -0800 (PST) From: Matthew Dillon Message-Id: <200002181905.LAA80267@apollo.backplane.com> To: Alan Cox Cc: current@FreeBSD.ORG Subject: Re: tentitive complete patch for MAP_GUARDED available References: <20000218122554.A2978@nonpc.cs.rice.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :> ... :> Resource limits are still an issue. It turns out that the :> MAP_STACK code does not deal with the stack resource limit :> well at all -- sometimes it catches it, sometimes it doesn't. : :In what sense? My recollection is that resource limits are :enforced on the "regular" process stack but not (except :perhaps by accident of placement) on other stacks, such as :those created by pthreads. It's because the threads library is allocating the thread stacks *ON* the user stack. Stacks created with MAP_STACK, including the user stack, are not entirely reserved at creation time. So if you have an 8m stack resource limit your user stack is actually only as large (growing from the top down) as the lowest address you have yet allocated from it. The kernel can't tell the difference between the default user stack and new MAP_STACK stacks the threads library allocates when they fall within the resource limit. On the otherhand if you mmap a stack well outside the resource limit, the kernel doesn't care either. It's only when you try to 'grow' a stack (any MAP_STACK stack) that is sitting within the resource such that it would grow beyond the resource limit that an error is generated. :At a higher level, it's not been obvious to me how the resource limit :on stack size should be interpreted in a multithreaded program. In :other words, I don't see one interpretation as obviously best, much :less correct. At least three possibilies are: : :1. It represents the maximum size of the "legacy" process stack :and nothing else, which is what the code currently implements. :(pthreads stacks are bounded by other means.) : :2. It represents the maximum size of each and every stack, whether :it's the "legacy" process stack or for example a pthreads stack. : :3. It represents the sum of the size of all of the stacks. : :There are problems/drawbacks to each and every possibility. : :So, in conclusion, I think the first order of business is :to determine what semantics (1) there may be good precedent :for and (2) that threads programmers are comfortable with. : :Alan I think the issue is plain and simply that our implementation is broken. I think the resource limit should only apply to the main user stack and not to any old MAP_STACK one happens to mmap(). Thread stacks should not in any way fall under the system stack resource. It just doesn't apply. I also think that a single guard page at the base of the stack may be insufficient for some applications. I'm considering adding yet another field to vm_map_entry 'vm_pindex_t guard_pages' which allows the number of guard pages to be specified (we can use mmap()'s offset argument to pass the parameter). I also think we should get rid of the avail_ssize field in vm_map_entry and instead simply have a flag for the main user stack's vm_map_entry that allows it to grow downward to be sized up to the resource limit in size. Should the resource limit apply to any MAP_STACK mapping (separately and independantly)? Yes, I think so. It shouldn't matter at all for threads but I can see using MAP_STACK mmaping's to dynamically load programs and run them (rather then fork/exec), in certain cases. What do you think? The above changes would be easy to add, I've already done the hard work of optimizing the VM system. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 11:16:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from freesbee.wheel.dk (freesbee.wheel.dk [193.162.159.97]) by hub.freebsd.org (Postfix) with ESMTP id F394037B9D9 for ; Fri, 18 Feb 2000 11:16:12 -0800 (PST) (envelope-from jesper@skriver.dk) Received: by freesbee.wheel.dk (Postfix, from userid 1001) id E58DF3E39; Fri, 18 Feb 2000 20:16:08 +0100 (CET) Date: Fri, 18 Feb 2000 20:16:08 +0100 From: Jesper Skriver To: current@FreeBSD.org Subject: No getty on ttyd0 after install on serial port ?? Message-ID: <20000218201608.A83037@skriver.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I just installed a box (20000208 -CURRENT snapshot) using a serial console, worked fine (a bit slow in redrawing), but after booting the installed system there was no getty on the serial port ... /Jesper -- Jesper Skriver, jesper(at)skriver(dot)dk - CCIE #5456 Work: Network manager @ AS3292 (Tele Danmark DataNetworks) Private: Geek @ AS2109 (A much smaller network ;-) One Unix to rule them all, One Resolver to find them, One IP to bring them all and in the zone to bind them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 11:21:32 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 6889937B795; Fri, 18 Feb 2000 11:21:30 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id LAA16034; Fri, 18 Feb 2000 11:21:30 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 18 Feb 2000 11:21:30 -0800 (PST) From: Kris Kennaway To: Robert Watson Cc: freebsd-current@freebsd.org Subject: Re: break in libcrypto? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Robert Watson wrote: > A further data point: I was building with a -j, so maybe there's a > dependency mixup with the beforedepend target? If I manually cd to the > directory and do a make beforedepend, things continue naturally from > there. What value of -j? I've built fine with -j4 and -j8, but this says that the depend target hadn't run before the all target did. Did you 'make depend' before building? Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 11:47: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id E855F37BB2B; Fri, 18 Feb 2000 11:47:00 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id EAA06374; Sat, 19 Feb 2000 04:46:55 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id EAA01369; Sat, 19 Feb 2000 04:46:54 +0900 (JST) Received: from localhost ([192.168.245.158]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id EAA05669; Sat, 19 Feb 2000 04:46:52 +0900 (JST) To: ache@FreeBSD.ORG Cc: saxonww@ufl.edu, current@FreeBSD.ORG Subject: Re: Broken FTP In-Reply-To: <20000218103132.A74763@freebsd.org> References: <20000216101731.A27147@nagual.pp.ru> <20000217180622H.shin@nd.net.fujitsu.co.jp> <20000218103132.A74763@freebsd.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000219044734W.shin@nd.net.fujitsu.co.jp> Date: Sat, 19 Feb 2000 04:47:34 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 31 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > OK I'll change not to try it once it fails. > > It seems your last patch _not_ fix the problem. Now I got: > > ftp> dir > 500 'EPSV': command not understood. > > on first 'dir' command issued. This is with wu-ftpd. Remember that different > ftpd's could have slightly different format for response so you should > not relay on it much. > > Could you please try EPSV automatically on _login_ and eat predictable response > instead of trying on first user command? In that way you can reflect EPSV-able > status in ftp's 'status' command to give user info is remote ftpd > EPSV-compatible or not, as I already describe in previous messages. But the change to do it seems to be not so simple as can be done in this code freeze phase. (At least with my level of understanding of ftp code.) Somewhat no printing version of getreply() seems to be necessary. Could you please create the patch which seems to be safely committed? That will be very much help. Thanks, Yoshinobu Inoue > Andrey A. Chernov > > http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 11:58:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from calvin.saturn-tech.com (calvin.saturn-tech.com [207.229.19.6]) by hub.freebsd.org (Postfix) with ESMTP id 1F1AD37BA1E for ; Fri, 18 Feb 2000 11:58:42 -0800 (PST) (envelope-from drussell@saturn-tech.com) Received: from localhost (drussell@localhost) by calvin.saturn-tech.com (8.8.8/8.8.8) with SMTP id MAA10068; Fri, 18 Feb 2000 12:57:52 -0700 (MST) (envelope-from drussell@saturn-tech.com) Date: Fri, 18 Feb 2000 12:57:52 -0700 (MST) From: Doug Russell To: Jake Burkholder Cc: Bill Fumerola , current@FreeBSD.ORG Subject: Re: 4.0-RC Broken driver?: matcd In-Reply-To: <20000215031337.63117BA67@io.yi.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 14 Feb 2000, Jake Burkholder wrote: > > On Mon, Feb 14, 2000 at 02:39:09PM -0700, Doug Russell wrote: > > > > > Does anyone have a Panasonic 526/563 CD-ROM drive working under 4.0-C? I > > > have not had one working for may weeks, however, I wasn't sure if it was a > > > hardware problem here, or something. 3.4 still finds them, so I beleive > > > it is something with the move to newbus or driver compatibility shims. > > > I think this driver is a casualty of newbus; mine stopped being probed > last year when the conversion was made. I'm certain that is the problem, but there are supposed to be shims in place to make it work. They just don't seem to be working at all. I'm trying to fix it, I just can't find where it's broken! :) Later...... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 11:59:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 7DAF337B53C for ; Fri, 18 Feb 2000 11:59:22 -0800 (PST) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id LAA08787; Fri, 18 Feb 2000 11:58:49 -0800 (PST) Message-Id: <200002181958.LAA08787@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: Yoshinobu Inoue Cc: bmah@california.sandia.gov, bauer@cc.univie.ac.at, current@FreeBSD.ORG Subject: Re: IPv6 In-Reply-To: <20000218215940K.shin@nd.net.fujitsu.co.jp> References: <20000215041550J.shin@nd.net.fujitsu.co.jp> <200002142150.NAA15862@nimitz.ca.sandia.gov> <20000216034713O.shin@nd.net.fujitsu.co.jp> <20000218215940K.shin@nd.net.fujitsu.co.jp> Comments: In-reply-to Yoshinobu Inoue message dated "Fri, 18 Feb 2000 21:59:40 +0900." From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1376764464P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 18 Feb 2000 11:58:49 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_1376764464P Content-Type: text/plain; charset=us-ascii The only changes I have for you are small typos... /etc/rc.conf: "assigne router prefix" should be: "assign router prefix" /etc/rc.network6: "if you instead want to route such packets to a "default" interface": Looks to me like this comment is not applicable anymore. "Enable Router Renumbering, unicaset case" should be: "Enable Router Renumbering, unicast case" Unfortunately I can't give you any good comments about functionality...I want to do a buildworld/installworld on my test box to pick up all of the changes regarding scoped addresses...I'm doing a cvs update now to bring the sources over. Once I'm back up and running, I'll let you know how it works for me. Thanks! Bruce. --==_Exmh_1376764464P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: jAGsLM8aGmAi8qMpYtsp75GIRH5MdjAh iQA/AwUBOK2keNjKMXFboFLDEQJXAgCfQ9RtsQq+Bk8p2XqsqN59K4z3I5sAoNeU Jcn/XKkK0imKqtvUBsxp3UkI =mNqm -----END PGP SIGNATURE----- --==_Exmh_1376764464P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 12:29:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 3739937B9D6 for ; Fri, 18 Feb 2000 12:29:15 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA28733; Fri, 18 Feb 2000 22:28:56 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200002182028.WAA28733@gratis.grondar.za> To: Garrett Wollman Cc: current@FreeBSD.org Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <200002181556.KAA86357@khavrinen.lcs.mit.edu> In-Reply-To: <200002181556.KAA86357@khavrinen.lcs.mit.edu> ; from Garrett Wollman "Fri, 18 Feb 2000 10:56:07 EST." Date: Fri, 18 Feb 2000 22:28:56 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > o A username may only be checked $number times per $timeperiod; > > after that, _all_ answers are silently converted to "no". > > Easier: a username may only be checked by a process running as $uid > or by root. ... added to the list of possibles. > > ... etc. There are possibilities for DoS attacks, but the daemon > > talks only to a Unix Domain Socket, so finding the perp is easy. > > And what happens when the daemon is dead, has crashed, or was never > started? Answer is "no". Possible DoS attack to be addressed. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 12:29:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail2.aracnet.com (mail2.aracnet.com [216.99.193.35]) by hub.freebsd.org (Postfix) with ESMTP id A7CD637B53C for ; Fri, 18 Feb 2000 12:29:43 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail2.aracnet.com (8.9.3/8.9.3) with ESMTP id MAA11451; Fri, 18 Feb 2000 12:30:12 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id MAA23197; Fri, 18 Feb 2000 12:30:02 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Fri, 18 Feb 2000 12:30:02 -0800 (PST) From: Brian Beattie To: Anatoly Vorobey Cc: "Daniel C. Sobral" , freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 In-Reply-To: <20000218183421.A2896@happy.checkpoint.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Anatoly Vorobey wrote: > On Fri, Feb 18, 2000 at 11:28:45PM +0900, Daniel C. Sobral wrote: > > > > Novice is ok, it's the other two that are problematic. Well, > > particularly "custom". "Custom" does not scare away anyone, and is > > actually actractive to Windows users. It should be called "death trap" > > or something like that... > > I'm actually scared by "novice" because it would be inflicting on me > defaults I would almost probably not want. I never run anything but > "custom", and I suspect many people do the same. > I never use anything but, unless I'm doing something really wierd. It does not as far as I can tell impose any defaults. Off the top of my head the difference it that the Novice install runs you through the steps of the install in the most logical order and nothing more. I would say if people are getting the impression that Anatoly has that it probably be renamed because IMHO it really is more convienient without sacrificeing any functionality. I'm not sure what I would call it since "Standard" might give a similar impression to "Novice". Maybe, stanard, express, selective, could be the three installation types. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 12:31:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id CC93137BA96; Fri, 18 Feb 2000 12:31:48 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA28751; Fri, 18 Feb 2000 22:30:51 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200002182030.WAA28751@gratis.grondar.za> To: Lyndon Nerenberg Cc: Peter Wemm , current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <200002181628.e1IGS9P48266@orthanc.ab.ca> In-Reply-To: <200002181628.e1IGS9P48266@orthanc.ab.ca> ; from Lyndon Nerenberg "Fri, 18 Feb 2000 09:28:09 MST." Date: Fri, 18 Feb 2000 22:30:51 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG All of the below are representative examples of the lattitude that a sysamin may be granted when setting up her system. There is a DoS of each of them. Pick your own policy. M > >>>>> "Mark" == Mark Murray writes: > > Mark> o A username may only be checked $number times per > Mark> $timeperiod; after that, _all_ answers are silently > Mark> converted to "no". > > Umm, massive DOS hole. > > Mark> o Daemon may only be invoked $number times per $timeperiod; > Mark> refuses to fork after that. > > Another massive DOS hole. > > Mark> o Daemon will delay $timeperiod before returning answer. > > This is the correct way to deal with (perceived) attacks. > > Mark> ... etc. There are possibilities for DoS attacks, but the > Mark> daemon talks only to a Unix Domain Socket, so finding the > Mark> perp is easy. > > Not if the daemon has shut itself off due to load (#1 or #2 above) and you > aren't currently logged in to the box. > > --lyndon -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 12:32:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 8900337BA64 for ; Fri, 18 Feb 2000 12:32:29 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA28778; Fri, 18 Feb 2000 22:32:01 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200002182032.WAA28778@gratis.grondar.za> To: Garrett Wollman Cc: Lyndon Nerenberg , current@FreeBSD.ORG Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <200002181633.LAA86511@khavrinen.lcs.mit.edu> In-Reply-To: <200002181633.LAA86511@khavrinen.lcs.mit.edu> ; from Garrett Wollman "Fri, 18 Feb 2000 11:33:19 EST." Date: Fri, 18 Feb 2000 22:32:00 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > You incorporate my patches to inetd that teach it to listen on > > named sockets, and then run the daemon from there in wait mode. > > If inetd dies you're pretty much hosed, anyway. > > Think ``single-user mode''. Single user mode has nothing to do with the problem I am attempting to address. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 12:38:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id 41C4037BA51; Fri, 18 Feb 2000 12:36:48 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA28827; Fri, 18 Feb 2000 22:35:38 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200002182035.WAA28827@gratis.grondar.za> To: Robert Watson Cc: Lyndon Nerenberg , Peter Wemm , current@FreeBSD.ORG, committers@FreeBSD.ORG Subject: Re: Crypto progress! (And a Biiiig TODO list) References: In-Reply-To: ; from Robert Watson "Fri, 18 Feb 2000 11:59:02 EST." Date: Fri, 18 Feb 2000 22:35:38 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Another technique that could be used, and gets discussed occasionally on > -security, is passing authentication information via ancillary data > transfer on UNIX domain sockets. You could limit the effectiveness of DOS > attacks by rate limiting per-uid, for example. Why is this being discussed as if it is new? This is what my tool _does_, for crying out loud!! > It should be noted that both the old and new schemes are subject to > denial of service--the old due to locking, and the new due to socket/IPC > limits, among other things. I would argue, however, that the new > mechanism reduces risk as it would allow us to remove the setuid bit from > a number of binaries, instead relying on a single auditable code base in > the password file manager. Right!! Forward motion. > If we plan to move to more daemons using IPC to communicate in this style, > we might want to think about consistency guidelines for doing this. For > example, mandating an LPC structure of some sort, or managing parallelism > on a single pipe, etc. Also, documenting techniques that tend to reduce > the risk of denial of service for daemons offering IPC services. Sure. Code/Documetation welcome. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 12:54:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id A6BFD37B99E for ; Fri, 18 Feb 2000 12:54:18 -0800 (PST) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id PAA87342; Fri, 18 Feb 2000 15:53:49 -0500 (EST) (envelope-from wollman) Date: Fri, 18 Feb 2000 15:53:49 -0500 (EST) From: Garrett Wollman Message-Id: <200002182053.PAA87342@khavrinen.lcs.mit.edu> To: Mark Murray Cc: current@FreeBSD.org Subject: Re: Crypto progress! (And a Biiiig TODO list) In-Reply-To: <200002182035.WAA28827@gratis.grondar.za> References: <200002182035.WAA28827@gratis.grondar.za> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Why is this being discussed as if it is new? > This is what my tool _does_, for crying out loud!! Which so far nobody else has ever seen. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 12:58:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id C718D37BA3F for ; Fri, 18 Feb 2000 12:58:19 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id WAA29041; Fri, 18 Feb 2000 22:57:57 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <200002182057.WAA29041@gratis.grondar.za> To: Garrett Wollman Cc: current@FreeBSD.org Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <200002182053.PAA87342@khavrinen.lcs.mit.edu> In-Reply-To: <200002182053.PAA87342@khavrinen.lcs.mit.edu> ; from Garrett Wollman "Fri, 18 Feb 2000 15:53:49 EST." Date: Fri, 18 Feb 2000 22:57:57 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > < said: > > > Why is this being discussed as if it is new? > > > This is what my tool _does_, for crying out loud!! > > Which so far nobody else has ever seen. Nor asked to see. Poul-Henning Kamp's "bike shed" argument applies here _big_time_. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 13:12:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id E77A237BA1E for ; Fri, 18 Feb 2000 13:12:53 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id NAA26387; Fri, 18 Feb 2000 13:41:01 -0800 (PST) Date: Fri, 18 Feb 2000 13:41:01 -0800 From: Alfred Perlstein To: Mark Murray Cc: Garrett Wollman , current@FreeBSD.ORG Subject: Re: Crypto progress! (And a Biiiig TODO list) Message-ID: <20000218134101.U21720@fw.wintelcom.net> References: <200002182053.PAA87342@khavrinen.lcs.mit.edu> <200002182057.WAA29041@gratis.grondar.za> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002182057.WAA29041@gratis.grondar.za>; from mark@grondar.za on Fri, Feb 18, 2000 at 10:57:57PM +0200 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Mark Murray [000218 13:27] wrote: > > < said: > > > > > Why is this being discussed as if it is new? > > > > > This is what my tool _does_, for crying out loud!! > > > > Which so far nobody else has ever seen. > > Nor asked to see. > > Poul-Henning Kamp's "bike shed" argument applies here _big_time_. (not to Mark, but to people slamming him) Jeez people, don't assume someone is reinventing the wheel until you actually see the wheel, it could be something else entirely. Constructive critism is fine, but take a second to settle down. :) It's not like Mark is going to slam this into the tree without putting it up for some serious review. (right Mark? :) ) -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 13:13:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 5946F37B9D9; Fri, 18 Feb 2000 13:13:31 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id QAA43175; Fri, 18 Feb 2000 16:14:23 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Fri, 18 Feb 2000 16:14:23 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Kris Kennaway Cc: freebsd-current@FreeBSD.org Subject: Re: break in libcrypto? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Kris Kennaway wrote: > On Fri, 18 Feb 2000, Robert Watson wrote: > > > A further data point: I was building with a -j, so maybe there's a > > dependency mixup with the beforedepend target? If I manually cd to the > > directory and do a make beforedepend, things continue naturally from > > there. > > What value of -j? I've built fine with -j4 and -j8, but this says that the > depend target hadn't run before the all target did. Did you 'make depend' > before building? Nope -- my make was in the top level /usr/src tree, in the form of ``make -j 3 all''. It was only after the build failed that I cd'd to the directory, looked around, and did a make beforedepend to generate the missing include file. I don't know that much about the current build infrastructure--was just following Poul's building instructions from jail(8). Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 13:16:22 2000 Delivered-To: freebsd-current@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 181A237BA1E for ; Fri, 18 Feb 2000 13:16:19 -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 QAA93313; Fri, 18 Feb 2000 16:16:06 -0500 (EST) (envelope-from bsdx@looksharp.net) Date: Fri, 18 Feb 2000 16:16:06 -0500 (EST) From: Adam To: Joao Pedras Cc: freebsd-current@FreeBSD.ORG Subject: Re: freezing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I do not mean to throw blame on freebsd at all (unless tons of people also see this) but I had a freeze earlier today. I had several windows open, netscape, and was compiling qt2 with not much disk activity at all when it just froze hard as a rock in all ways I can think of. If it happens again I'll look into ddc and serial console or perhaps recreating on normal console. I dont suspect hardware fault but I wouldn't dismiss it. On Thu, 17 Feb 2000, Joao Pedras wrote: >Hello all > >While making -j 4 buildworld and moving a netscape window, everything frozen. >Happens often if do other things while cpu and disk are very active. > >Happens quite often. > >Anyone else has noticed this ? > >Joao > > ^\ /^ > O O >----------------------------------------o00-(_)-00o-------------------------- > >Shaw's Principle: > Build a system that even a fool can use, and only a fool will >want to use it. > >----------------------------------------------------------------------------- >PGP key available upon request or may be cut at >http://pedras.webvolution.net/pgpkey.html > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 13:18:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id ACFBD37BAAD; Fri, 18 Feb 2000 13:18:48 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA24908; Fri, 18 Feb 2000 13:18:48 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 18 Feb 2000 13:18:48 -0800 (PST) From: Kris Kennaway To: Robert Watson Cc: freebsd-current@FreeBSD.org Subject: Re: break in libcrypto? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Robert Watson wrote: > > What value of -j? I've built fine with -j4 and -j8, but this says that the > > depend target hadn't run before the all target did. Did you 'make depend' > > before building? > > Nope -- my make was in the top level /usr/src tree, in the form of ``make > -j 3 all''. It was only after the build failed that I cd'd to the > directory, looked around, and did a make beforedepend to generate the > missing include file. I don't know that much about the current build > infrastructure--was just following Poul's building instructions from > jail(8). You need to make depend first..perhaps the makefile could be improved (I'm no guru) but I've seen lots of other parts of the tree sporadically break if you don't do this. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 13:24:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 73E5237BAA7 for ; Fri, 18 Feb 2000 13:24:25 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id NAA81098; Fri, 18 Feb 2000 13:24:23 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 13:24:23 -0800 (PST) From: Matthew Dillon Message-Id: <200002182124.NAA81098@apollo.backplane.com> To: Alan Cox Cc: current@FreeBSD.ORG Subject: Re: tentitive complete patch for MAP_GUARDED available References: <20000218122554.A2978@nonpc.cs.rice.edu> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, I just finished making the modifications, essentially rewriting vm_map_growstack() and vm_map_stack(). http://www.backplane.com/FreeBSD4/ http://www.backplane.com/FreeBSD4/guard-3.diff http://www.backplane.com/FreeBSD4/guard3.c Here are the proposed semantics: * When you mmap() with MAP_STACK, the stack you map is limited to the number of bytes specified in the mmap() AND ALSO limited by the process stack resource limit (on a per-mmap basis). That is, *EACH* MAP_STACK mmaping may utilize up to the process stack resource and no more, even if you mmap a larger area. This may be a little controversial but it's basically how the kernel allocates the default user stack -- it allocates the maximum kernel limit and assumes the stack will be limited by the stack resource. I think it could be useful for debugging, too. (Also, with MAP_STACK, a fixed address and an anonymous mmap is implied, and the mmap() will fail if the specified region already contains mappings). * When you mmap() with MAP_GUARDED, the offset field in the mmap() call specifies the number of guard pages at the beginning and end of the map. If you specify 0, you don't get any guard pages (which is kinda useless). Normally getpagesize() bytes is specified. An anonymous mmap is implied. * When you mmap() with MAP_GUARDED|MAP_STACK, you get a guarded stack. The system will not create a growable stack, though, it pre-reserves the space (but, of course, does not allocate physical pages for things you haven't touched). The new semantics use the offset field in the mmap to indicate the number of guard pages at the beginning and end of the map, in bytes, so the semantics of MAP_GUARDED mmap's has been changed somewhat. You nominally have to call it with an offset of getpagesize() to get the 'single guard page at beginning and end' behavior. So, to make the threads library use this you mmap MAP_STACK|MAP_GUARDED with an offset of getpagesize() (or more). -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 13:27:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 4052337BA51 for ; Fri, 18 Feb 2000 13:27:48 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m3.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id GAA17177; Sat, 19 Feb 2000 06:27:26 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m3.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id GAA11260; Sat, 19 Feb 2000 06:27:25 +0900 (JST) Received: from localhost ([192.168.245.85]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id GAA06860; Sat, 19 Feb 2000 06:27:24 +0900 (JST) To: cob@gnt.kiev.ua Cc: freebsd-current@FreeBSD.ORG Subject: Re: IP tunnel In-Reply-To: <87og9eg413.fsf@rock.gnt.kiev.ua> References: <87og9eg413.fsf@rock.gnt.kiev.ua> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000219062805W.shin@nd.net.fujitsu.co.jp> Date: Sat, 19 Feb 2000 06:28:05 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 43 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hello! > > What about ${subj} in current? > Or maybe someone know how to make > ip tunnel on current using patches, tools, etc.? > > Thanx. Maybe there are several ways, and one thing I know is gif interface recently added. It can be used by adding following entry in your kernel config. (Any number can be specified.) pseudo-device gif 4 It can do, IPv6 over IPv4 IPv4 over IPv6 IPv4 over IPv4 IPv6 over IPv6 tunnelings. To configure outer addresses, use gifconfig, like, gifconfig gif0 10.1.1.1 10.1.1.2 You need to do opposite on the 10.1.1.2 machine. And to configure inner addresses, just use ifconfig for gif interfaces. Also please take care not to create infinite loop tunnel, when you do, IPv4 over IPv4 IPv6 over IPv6 Please check man for gifconfig for details. Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 13:48:26 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by hub.freebsd.org (Postfix) with ESMTP id 14B6A37B9D9 for ; Fri, 18 Feb 2000 13:48:24 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id NAA28628; Fri, 18 Feb 2000 13:48:40 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id NAA26026; Fri, 18 Feb 2000 13:48:46 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Fri, 18 Feb 2000 13:48:46 -0800 (PST) From: Brian Beattie To: Adam Cc: Joao Pedras , freebsd-current@FreeBSD.ORG Subject: Re: freezing In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Adam wrote: > I do not mean to throw blame on freebsd at all (unless tons of people also > see this) but I had a freeze earlier today. I had several windows open, > netscape, and was compiling qt2 with not much disk activity at all when it > just froze hard as a rock in all ways I can think of. If it happens again > I'll look into ddc and serial console or perhaps recreating on normal > console. I dont suspect hardware fault but I wouldn't dismiss it. > > On Thu, 17 Feb 2000, Joao Pedras wrote: > > >Hello all > > > >While making -j 4 buildworld and moving a netscape window, everything frozen. > >Happens often if do other things while cpu and disk are very active. > > > >Happens quite often. > > > >Anyone else has noticed this ? > > I have had a number of freezes, during a rm -rf and a find at the same time, during a cvs checkout, during a fsck on reboot. The fsck caused a message about an "SCB Timeout" I think. I have returned to slightly older 4.0-Current kernel and was going to build a new kernel. I can try to get more information this evening, if anybody is interested. For me the trigger seems to be heavy disk activity. configuration summary: K6-2 333, 80MB, aha2940(I think, adaptec PCI ultra), 4 2GB segate SCSI drives. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14: 3:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgw00.execpc.com (mailgw00.execpc.com [169.207.1.78]) by hub.freebsd.org (Postfix) with ESMTP id EF44137BA96; Fri, 18 Feb 2000 14:03:21 -0800 (PST) (envelope-from hamilton@pobox.com) Received: from woodstock.monkey.net (minbar-2-58.mdm.mke.execpc.com [169.207.135.186]) by mailgw00.execpc.com (8.9.1) id QAA22651; Fri, 18 Feb 2000 16:02:02 -0600 Received: from pobox.com (localhost [127.0.0.1]) by woodstock.monkey.net (Postfix) with ESMTP id 0BD819B; Fri, 18 Feb 2000 16:01:38 -0600 (CST) X-Mailer: exmh version 2.1.1 10/16/1999 To: Wes Peters Cc: Lyndon Nerenberg , Mark Murray , Peter Wemm , current@freebsd.org, committers@freebsd.org Subject: Re: Crypto progress! (And a Biiiig TODO list) In-reply-to: Your message of "Fri, 18 Feb 2000 10:01:23 MST." <38AD7AE3.B4BEB308@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Feb 2000 16:01:38 -0600 From: Jon Hamilton Message-Id: <20000218220138.0BD819B@woodstock.monkey.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <38AD7AE3.B4BEB308@softweyr.com>, Wes Peters wrote: } Lyndon Nerenberg wrote: } > } > >>>>> "Mark" == Mark Murray writes: } > } > Mark> o A username may only be checked $number times per } > Mark> $timeperiod; after that, _all_ answers are silently } > Mark> converted to "no". } > } > Umm, massive DOS hole. } } Per username. If you publish your userlist, you're an idiot. The } daemon should also immediately go into "breakin evasion mode" for } all invalid usernames, answering the requests very slowly. You don't have to publish a userlist in order for some of that kind of information to leak out. Besides, by answering very slowly for invalid usernames you just gave the bad guys a way to deduce your user list anyway. -- Jon Hamilton hamilton@pobox.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14: 9: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 4F24D37BA9E for ; Fri, 18 Feb 2000 14:09:04 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA81369; Fri, 18 Feb 2000 14:09:02 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 14:09:02 -0800 (PST) From: Matthew Dillon Message-Id: <200002182209.OAA81369@apollo.backplane.com> To: Daniel Eischen Cc: alc@cs.rice.edu, current@FreeBSD.ORG Subject: Re: tentitive complete patch for MAP_GUARDED available References: <200002182141.QAA18866@pcnet1.pcnet.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :Currently, the threads library only creates one guard page :at the top (or bottom depending on how you look at it) of :each threads stack (for stacks of default size). Thread :stacks are allocated in sequential zones, so they are always :placed on top of the previous threads stack, and thus already :have a guard page below the stack. : :Correct me if I'm wrong, but using MAP_STACK|MAP_GUARDED :would allocate one additional guard page for each threads :stack. : :DanE. Correct. At the moment MAP_GUARDED is a 'generic' guarding flag and makes no assumptions about the areas being adjoining. It doesn't cost us anything. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14: 9:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from waldorf.cs.uni-dortmund.de (waldorf.cs.uni-dortmund.de [129.217.4.42]) by hub.freebsd.org (Postfix) with ESMTP id BA4E037BAA6; Fri, 18 Feb 2000 14:09:18 -0800 (PST) (envelope-from Kai.Grossjohann@CS.Uni-Dortmund.DE) Received: from marcy.cs.uni-dortmund.de (marcy.cs.uni-dortmund.de [129.217.20.159]) by waldorf.cs.uni-dortmund.de with ESMTP id XAA07367; Fri, 18 Feb 2000 23:09:17 +0100 (MET) Received: from lucy.cs.uni-dortmund.de (lucy [129.217.20.160]) by marcy.cs.uni-dortmund.de id XAA26981; Fri, 18 Feb 2000 23:09:17 +0100 (MET) Received: (from grossjoh@localhost) by lucy.cs.uni-dortmund.de (8.9.3/8.9.3/Debian 8.9.3-6) id XAA05229; Fri, 18 Feb 2000 23:09:16 +0100 X-Authentication-Warning: lucy.cs.uni-dortmund.de: grossjoh set sender to Kai.Grossjohann@CS.Uni-Dortmund.DE using -f To: freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 References: <79206.950898990@zippy.cdrom.com> From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai=?iso-8859-1?q?_Gro=DFjohann?=) In-Reply-To: "Jordan K. Hubbard"'s message of "Fri, 18 Feb 2000 10:36:30 -0800" User-Agent: Gnus/5.0804 (Gnus v5.8.4) Emacs/20.5 Date: 18 Feb 2000 23:09:16 +0100 Message-ID: Lines: 15 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jordan K. Hubbard" writes: > I really kinda wish you'd point them to Novice^H^H^H^H^HStandard > instead since it does more than be a bit more verbose, it also makes > sure that all the appropriate steps are covered and prevents even > relatively skilled people from hanging themselves. Does this mean that this option should be called `guided'? I know a little bit about Unix but haven't installed FreeBSD more than five times or so. And I always thought that the novice install meant that I didn't get as many choices... kai -- ~/.signature: No such file or directory To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14:12: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 4332937BA5E; Fri, 18 Feb 2000 14:12:05 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id RAA43586; Fri, 18 Feb 2000 17:12:59 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Fri, 18 Feb 2000 17:12:58 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Kris Kennaway Cc: freebsd-current@FreeBSD.org Subject: Re: break in libcrypto? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Kris Kennaway wrote: > On Fri, 18 Feb 2000, Robert Watson wrote: > > > > What value of -j? I've built fine with -j4 and -j8, but this says that the > > > depend target hadn't run before the all target did. Did you 'make depend' > > > before building? > > > > Nope -- my make was in the top level /usr/src tree, in the form of ``make > > -j 3 all''. It was only after the build failed that I cd'd to the > > directory, looked around, and did a make beforedepend to generate the > > missing include file. I don't know that much about the current build > > infrastructure--was just following Poul's building instructions from > > jail(8). > > You need to make depend first..perhaps the makefile could be improved (I'm > no guru) but I've seen lots of other parts of the tree sporadically break > if you don't do this. Ok, is this a make depend in the top /usr/src, or in directories thjat specifically require it. Or more practically speaking--I want the directions in jail(8) to work every time. :-) How can this be fixed? They currently read: Setting up a Jail Directory Tree This shows how to setup a jail directory tree: D=/here/is/the/jail cd /usr/src make hierarchy DESTDIR=$D make obj make all make install DESTDIR=$D cd etc make distribution DESTDIR=$D NO_MAKEDEV=yes cd $D/dev sh MAKEDEV jail cd $D ln -sf dev/null kernel Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14:19:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id E867E37BAD3 for ; Fri, 18 Feb 2000 14:19:51 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id QAA18866; Fri, 18 Feb 2000 16:41:15 -0500 (EST) Date: Fri, 18 Feb 2000 16:41:15 -0500 (EST) From: Daniel Eischen Message-Id: <200002182141.QAA18866@pcnet1.pcnet.com> To: alc@cs.rice.edu, dillon@apollo.backplane.com Subject: Re: tentitive complete patch for MAP_GUARDED available Cc: current@FreeBSD.ORG Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > * When you mmap() with MAP_GUARDED|MAP_STACK, you get > a guarded stack. The system will not create a > growable stack, though, it pre-reserves the space > (but, of course, does not allocate physical pages > for things you haven't touched). > > The new semantics use the offset field in the mmap to > indicate the number of guard pages at the beginning and > end of the map, in bytes, so the semantics of MAP_GUARDED > mmap's has been changed somewhat. You nominally have > to call it with an offset of getpagesize() to get the > 'single guard page at beginning and end' behavior. > > So, to make the threads library use this you mmap > MAP_STACK|MAP_GUARDED with an offset of getpagesize() > (or more). Currently, the threads library only creates one guard page at the top (or bottom depending on how you look at it) of each threads stack (for stacks of default size). Thread stacks are allocated in sequential zones, so they are always placed on top of the previous threads stack, and thus already have a guard page below the stack. Correct me if I'm wrong, but using MAP_STACK|MAP_GUARDED would allocate one additional guard page for each threads stack. DanE. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14:23:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A3CE337BAEA for ; Fri, 18 Feb 2000 14:23:36 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id OAA81419; Fri, 18 Feb 2000 14:23:35 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 14:23:35 -0800 (PST) From: Matthew Dillon Message-Id: <200002182223.OAA81419@apollo.backplane.com> To: Matthew Dillon Cc: Alan Cox , current@FreeBSD.ORG Subject: Re: tentitive complete patch for MAP_GUARDED available References: <20000218122554.A2978@nonpc.cs.rice.edu> <200002182124.NAA81098@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : Ok, I just finished making the modifications, essentially : rewriting vm_map_growstack() and vm_map_stack(). : : http://www.backplane.com/FreeBSD4/ : http://www.backplane.com/FreeBSD4/guard-3.diff : http://www.backplane.com/FreeBSD4/guard3.c Oops, withdrawn... I muffed it up. I'll get it up later today. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14:24:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 2821F37BAB5 for ; Fri, 18 Feb 2000 14:24:22 -0800 (PST) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id RAA24508; Fri, 18 Feb 2000 17:24:08 -0500 (EST) Date: Fri, 18 Feb 2000 17:24:08 -0500 (EST) From: Daniel Eischen To: Matthew Dillon Cc: alc@cs.rice.edu, current@FreeBSD.ORG Subject: Re: tentitive complete patch for MAP_GUARDED available In-Reply-To: <200002182209.OAA81369@apollo.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Matthew Dillon wrote: > :Currently, the threads library only creates one guard page > :at the top (or bottom depending on how you look at it) of > :each threads stack (for stacks of default size). Thread > :stacks are allocated in sequential zones, so they are always > :placed on top of the previous threads stack, and thus already > :have a guard page below the stack. > : > :Correct me if I'm wrong, but using MAP_STACK|MAP_GUARDED > :would allocate one additional guard page for each threads > :stack. > : > :DanE. > > Correct. At the moment MAP_GUARDED is a 'generic' guarding flag > and makes no assumptions about the areas being adjoining. It doesn't > cost us anything. Any problem if we overlay a previously MAP_GUARDED page with another (to save an extra guard page)? Dan Eischen eischen@vigrid.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14:26:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 41A2337BAD7 for ; Fri, 18 Feb 2000 14:26:42 -0800 (PST) (envelope-from dgilbert@trooper.velocet.net) Received: from trooper.velocet.net (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 79B27137FB4 for ; Fri, 18 Feb 2000 17:26:35 -0500 (EST) Received: (from dgilbert@localhost) by trooper.velocet.net (8.9.3/8.9.3) id RAA53513; Fri, 18 Feb 2000 17:26:47 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14509.50981.963519.987797@trooper.velocet.net> Date: Fri, 18 Feb 2000 17:26:45 -0500 (EST) To: freebsd-current@freebsd.org Subject: ipv6 default in current ports? X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've come up against a number of ports lately assume IPv6 support if you're running: .if ${OSVERSION} >= 400014 CONFIGURE_ARGS+= --enable-ipv6 .endif ... I don't see INET6 in my GENERIC kernel. This affects at least net/mtr and lang/ruby. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14:38:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 6E98237BAB5 for ; Fri, 18 Feb 2000 14:38:51 -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 OAA01326; Fri, 18 Feb 2000 14:48:59 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002182248.OAA01326@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Tancsa Cc: current@FreeBSD.ORG Subject: Re: BIOS and PERC 2/SC (was Re: Perc 2/SC problems (aka MegaRAID 466) ) In-reply-to: Your message of "Thu, 17 Feb 2000 10:37:09 EST." <3.0.5.32.20000217103709.01c2f7b0@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Feb 2000 14:48:59 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > OK, I took a chance and flashed the card's BIOS to the latest from the AMI > site.... I had been suspecting BIOS, as the readme.txt mentioned problems > with newer motherboards. Lo and Behold, it seems to have done the trick > > amr0: mem 0xe9000000-0xe93fffff irq 11 at device 12.1 on pci0 > amr0: firmware GH6D bios 1.43 32MB memory > amrd0: on amr0 > amrd0: 17522MB (35885056 sectors) RAID 5 (optimal) > > As I mentioned, the card came as a Dell unit. I tried the latest BIOS from > Dell, but that was a year old. The BIOS from megaraid.com 1.43, which is > in there now *seems* to work so far.... At least I can now get a disklable > on the drive and newfs the drive Hmm. I did some testing, and I can lock both the G6HC and G6HD firmware up within a few minutes. The Dell 3.00 firmware remains stable under the same load (20 simultaneous 'bonnie -s 100's). I'm fairly sure it's a firmware lockup - the SCSI bus is hung and usually the PCI bus 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-current" in the body of the message From owner-freebsd-current Fri Feb 18 14:46:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from dominik.saargate.de (dominik.saargate.de [212.88.133.252]) by hub.freebsd.org (Postfix) with ESMTP id 6976337BA85 for ; Fri, 18 Feb 2000 14:46:34 -0800 (PST) (envelope-from domi@saargate.de) Received: from localhost (localhost [127.0.0.1]) by dominik.saargate.de (8.9.3/8.9.3) with ESMTP id XAA87247 for ; Fri, 18 Feb 2000 23:46:21 +0100 (CET) (envelope-from domi@saargate.de) Date: Fri, 18 Feb 2000 23:46:21 +0100 (CET) From: Dominik Brettnacher To: current@freebsd.org Subject: su(1) and PAM Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Is it planned to make su(1) support authentication via PAM? -- Dominik - http://www.saargate.de/~domi/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14:57:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from norn.ca.eu.org (cr965240-b.abtsfd1.bc.wave.home.com [24.113.19.137]) by hub.freebsd.org (Postfix) with ESMTP id 9173C37BAD7 for ; Fri, 18 Feb 2000 14:57:10 -0800 (PST) (envelope-from cpiazza@norn.ca.eu.org) Received: by norn.ca.eu.org (Postfix, from userid 1000) id 2285A1686; Fri, 18 Feb 2000 14:57:10 -0800 (PST) Date: Fri, 18 Feb 2000 14:57:10 -0800 From: Chris Piazza To: David Gilbert Cc: freebsd-current@FreeBSD.ORG Subject: Re: ipv6 default in current ports? Message-ID: <20000218145710.A831@norn.ca.eu.org> References: <14509.50981.963519.987797@trooper.velocet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14509.50981.963519.987797@trooper.velocet.net>; from dgilbert@velocet.ca on Fri, Feb 18, 2000 at 05:26:45PM -0500 X-Operating-System: FreeBSD 4.0-CURRENT i386 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 05:26:45PM -0500, David Gilbert wrote: > I've come up against a number of ports lately assume IPv6 support if > you're running: > > .if ${OSVERSION} >= 400014 > CONFIGURE_ARGS+= --enable-ipv6 > .endif > > ... I don't see INET6 in my GENERIC kernel. This affects at least > net/mtr and lang/ruby. > It doesn't need kernel support to build with ipv6 support. Trying to use the ipv6 support without it in the kernel is the only problem. -Chris -- cpiazza@jaxon.net cpiazza@FreeBSD.org Abbotsford, BC, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 14:59:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from sabre.velocet.net (sabre.velocet.net [198.96.118.66]) by hub.freebsd.org (Postfix) with ESMTP id 9B3B437BAE8 for ; Fri, 18 Feb 2000 14:59:44 -0800 (PST) (envelope-from dgilbert@velocet.ca) Received: from velocet.ca (trooper.velocet.net [216.126.82.226]) by sabre.velocet.net (Postfix) with ESMTP id 740EA137F6C; Fri, 18 Feb 2000 17:59:02 -0500 (EST) Received: (from dgilbert@localhost) by velocet.ca (8.9.3/8.9.3) id RAA56028; Fri, 18 Feb 2000 17:59:18 -0500 (EST) (envelope-from dgilbert) From: David Gilbert MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14509.52933.883241.459866@trooper.velocet.net> Date: Fri, 18 Feb 2000 17:59:17 -0500 (EST) To: Chris Piazza Cc: David Gilbert , freebsd-current@FreeBSD.ORG Subject: Re: ipv6 default in current ports? In-Reply-To: <20000218145710.A831@norn.ca.eu.org> References: <14509.50981.963519.987797@trooper.velocet.net> <20000218145710.A831@norn.ca.eu.org> X-Mailer: VM 6.75 under 20.4 "Emerald" XEmacs Lucid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "Chris" == Chris Piazza writes: Chris> On Fri, Feb 18, 2000 at 05:26:45PM -0500, David Gilbert wrote: >> I've come up against a number of ports lately assume IPv6 support >> if you're running: >> >> .if ${OSVERSION} >= 400014 CONFIGURE_ARGS+= --enable-ipv6 .endif >> >> ... I don't see INET6 in my GENERIC kernel. This affects at least >> net/mtr and lang/ruby. >> Chris> It doesn't need kernel support to build with ipv6 support. Chris> Trying to use the ipv6 support without it in the kernel is the Chris> only problem. Well... ruby refuses to build with IPv6 if it's not enabled and mtr dies with a "cannot open socket". In escence, both ports (and possibly others) don't work in 4.0 without INET6 in your kernel. Dave. -- ============================================================================ |David Gilbert, Velocet Communications. | Two things can only be | |Mail: dgilbert@velocet.net | equal if and only if they | |http://www.velocet.net/~dgilbert | are precisely opposite. | =========================================================GLO================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 15: 5:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 8F3CD37BAED for ; Fri, 18 Feb 2000 15:05:16 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA81713; Fri, 18 Feb 2000 15:04:45 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 15:04:45 -0800 (PST) From: Matthew Dillon Message-Id: <200002182304.PAA81713@apollo.backplane.com> To: Matthew Dillon Cc: alc@cs.rice.edu, current@FreeBSD.ORG Subject: Re: tentitive complete patch for MAP_GUARDED available References: <200002182141.QAA18866@pcnet1.pcnet.com> <200002182209.OAA81369@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :: ::Correct me if I'm wrong, but using MAP_STACK|MAP_GUARDED ::would allocate one additional guard page for each threads ::stack. :: ::DanE. : : Correct. At the moment MAP_GUARDED is a 'generic' guarding flag : and makes no assumptions about the areas being adjoining. It doesn't : cost us anything. Hmm. The more I think about it, the more I dislike what I just said. I think I am going to change it to just guard the first N pages and not guard both the first and the last N pages. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 15:24:19 2000 Delivered-To: freebsd-current@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 542) id A151D37BAD4; Fri, 18 Feb 2000 15:24:17 -0800 (PST) Date: Fri, 18 Feb 2000 15:24:17 -0800 From: "Andrey A. Chernov" To: Yoshinobu Inoue Cc: saxonww@ufl.edu, current@FreeBSD.ORG Subject: Re: Broken FTP Message-ID: <20000218152417.A52305@freebsd.org> References: <20000216101731.A27147@nagual.pp.ru> <20000217180622H.shin@nd.net.fujitsu.co.jp> <20000218103132.A74763@freebsd.org> <20000219044734W.shin@nd.net.fujitsu.co.jp> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20000219044734W.shin@nd.net.fujitsu.co.jp>; from shin@nd.net.fujitsu.co.jp on Sat, Feb 19, 2000 at 04:47:34AM +0900 Organization: Biomechanoid Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 19, 2000 at 04:47:34AM +0900, Yoshinobu Inoue wrote: > But the change to do it seems to be not so simple as can be > done in this code freeze phase. (At least with my level of > understanding of ftp code.) > Somewhat no printing version of getreply() seems to be > necessary. > > Could you please create the patch which seems to be safely > committed? That will be very much help. Well, I can try but I need to know most shortest and most trivial EPSV check sequence from you since can't check it locally and don't know about EPSV. Look at util.c setpeer() function lines if (command("PASSERVE %s", argv[1]) != COMPLETE) { ... and below if (command("SYST") == COMPLETE && overbose) { ... the check must be in this style... -- Andrey A. Chernov http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 15:59:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 63B9A37BAFE for ; Fri, 18 Feb 2000 15:59:15 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id PAA81991; Fri, 18 Feb 2000 15:59:15 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 15:59:15 -0800 (PST) From: Matthew Dillon Message-Id: <200002182359.PAA81991@apollo.backplane.com> To: alc@cs.rice.edu, current@FreeBSD.ORG Subject: Re: tentitive complete patch for MAP_GUARDED available References: <200002182141.QAA18866@pcnet1.pcnet.com> <200002182209.OAA81369@apollo.backplane.com> <200002182304.PAA81713@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ok, this time for sure... version 3 of the MAP_GUARDED patch is out. http://www.backplane.com/FreeBSD4/ http://www.backplane.com/FreeBSD4/guard-3.diff http://www.backplane.com/FreeBSD4/guard3.c MAP_GUARDED mmap(addr/NULL, len, prot, MAP_GUARDED, fd, offset) The offset field specifies the number of bytes at the base of the returned map which are guarded and should be a multiple of the system page size. Pages at the end of the map are not guarded (any more). MAP_STACK Works as per normal except that the per-process stack resource limit applies to each mmap() separately. MAP_GUARDED|MAP_STACK Useful combination to place guard page(s) at the beginning of a thread stack. Also in this patch set I optimized vm_map_entry creation during normal stack growth operations. Normally the system tries to chunk vm_map_entry allocation for stacks by SGROWSIZ, which is typically 128K. But now the vm_map_entry_insert() optimization is able to optimize standard stack growth, which means that the actual vm_map_entry creation is governed by the more generous vm.map_entry_blk_opt value (512K by default). I like this implementation a lot better. By removing the guard pages at the end of the map MAP_GUARDED|MAP_STACK operation is much, much more intuitive. You don't have to do a blessed thing to the threading code except change MAP_STACK to MAP_STACK|MAP_GUARDED, and bump up the size of the mmap() allocation to include what used to be the skipped 'dead' page. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 16: 8:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id CC43137BB25 for ; Fri, 18 Feb 2000 16:08:08 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id QAA82090; Fri, 18 Feb 2000 16:08:05 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 16:08:05 -0800 (PST) From: Matthew Dillon Message-Id: <200002190008.QAA82090@apollo.backplane.com> To: Daniel Eischen Cc: alc@cs.rice.edu, current@FreeBSD.ORG Subject: Re: tentitive complete patch for MAP_GUARDED available References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :Any problem if we overlay a previously MAP_GUARDED page with another :(to save an extra guard page)? : :Dan Eischen :eischen@vigrid.com Overlaying *anything* on top of a MAP_GUARDED mmap will break its functionality. This is true of a MAP_STACK mmap as well. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 16:11:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 4FA8937BB29 for ; Fri, 18 Feb 2000 16:10:47 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.12 #1) id 12LxTw-000Olv-00; Sat, 19 Feb 2000 00:10:44 +0000 Date: Sat, 19 Feb 2000 01:10:43 +0100 (CET) From: Marc Schneiders To: "Gray, David W." Cc: 'FreeBSD Current list' Subject: Re: Rc2 install In-Reply-To: <01D4D419B1A4D111A30400805FE65B13033661FC@nmrusdunsx1.nielsenmedia.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Gray, David W. wrote: > I've come to the conclusion that the -current stuff really doesn't install > on an 8 Meg machine anymore. I have an old 486/66 machine I'm using > to play with the current-RC's, and it consistantly dies loading the 'bin' > stuff. > I installed CURRENT of approx. January 1 with no problems on a 486/66 with only 8MB. Has something changed very recently that makes it impossible now? I installed through NFS. In fact the disk I installed this on is now in a laptop with only a little over 4MB (4352K), running a webserver :-) (http://keltisch.verboden.nl, in Dutch, but there is a link at the bottom "This server") You cannot install on 4 MB, nor run GENERIC kernel on 4 MB. After taking unnessary (and not strictly necessary like nfs, which is 250K) stuff out of the kernel it did run here (and is running for 28 days). O, yes, I had to make it not do the daily checks. These frooze the 4 MB box. > This isn't really a complaint -- after the load & boot cycle, there is only > 2.4M free according to the boot messages, so I can see why this would > fill up. (I wound up loading the drive on another box that usually drives my > printer, 386/25 and 24M, talk about S.L.O.W). And it can't quite compile a > kernel in one go, either. > I am not absolutely sure I succeeded compiling a kernel on 8 MB. I know I did try. But because I needed a lot of tries to cut down kernel size (and the BIOS of the laptop did not like new ata), I switched to a faster machine for kernel compiling. > Perhaps the release notes, or hardware file need to note you really do need > more than 8M ? > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- Marc Schneiders marc@venster.nl http://zelf.net marc@oldserver.demon.nl propro 12:56am up 11 days, 3:07, load average: 2.02 2.03 2.00 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 16:12:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from nimitz.ca.sandia.gov (nimitz.ca.sandia.gov [146.246.243.56]) by hub.freebsd.org (Postfix) with ESMTP id 9684537BAF2 for ; Fri, 18 Feb 2000 16:12:44 -0800 (PST) (envelope-from bmah@nimitz.ca.sandia.gov) Received: (from bmah@localhost) by nimitz.ca.sandia.gov (8.9.3/8.9.3) id QAA11354; Fri, 18 Feb 2000 16:12:19 -0800 (PST) Message-Id: <200002190012.QAA11354@nimitz.ca.sandia.gov> X-Mailer: exmh version 2.1.1-cvs 10/15/1999 To: Yoshinobu Inoue Cc: bmah@california.sandia.gov, bauer@cc.univie.ac.at, current@FreeBSD.ORG Subject: Re: IPv6 In-Reply-To: <20000218215940K.shin@nd.net.fujitsu.co.jp> References: <20000215041550J.shin@nd.net.fujitsu.co.jp> <200002142150.NAA15862@nimitz.ca.sandia.gov> <20000216034713O.shin@nd.net.fujitsu.co.jp> <20000218215940K.shin@nd.net.fujitsu.co.jp> Comments: In-reply-to Yoshinobu Inoue message dated "Fri, 18 Feb 2000 21:59:40 +0900." From: bmah@CA.Sandia.GOV (Bruce A. Mah) Reply-To: bmah@CA.Sandia.GOV X-Face: g~c`.{#4q0"(V*b#g[i~rXgm*w;:nMfz%_RZLma)UgGN&=j`5vXoU^@n5v4:OO)c["!w)nD/!!~e4Sj7LiT'6*wZ83454H""lb{CC%T37O!!'S$S&D}sem7I[A 2V%N&+ X-Url: http://www.ca.sandia.gov/~bmah/ Mime-Version: 1.0 Content-Type: multipart/signed; boundary="==_Exmh_1638373650P"; micalg=pgp-sha1; protocol="application/pgp-signature" Content-Transfer-Encoding: 7bit Date: Fri, 18 Feb 2000 16:12:19 -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --==_Exmh_1638373650P Content-Type: text/plain; charset=us-ascii If memory serves me right, Yoshinobu Inoue wrote: > I still made more several fixes to IPv6 configuration scripts. > > -changed the file rc.net6 to rc.network6 > -changed the func net6_pass1 to network6_pass1 > -changed several var name more unlikely to confilict > -changed if several sentenses in rc.network6 to case sentence > like in rc.network > -wrapped many var names by {} > -and other fixes I ran across a few problems after I remade world. The new scoped address syntax breaks /etc/rc.network6. In particular, some lines that look like: > + # disallow unicast packets without outgoing scope identifiers. > + # if you instead want to route such packets to a "default" interface, > + # comment out the 1st two lines, and enable the lines after them. > + case ${ipv6_default_interface} in > + '') > + route add -inet6 fe80:: -prefixlen 10 ::1 -reject > + ;; > + *) > + laddr=`ifconfig ${ipv6_default_interface} inet6 \ > + | grep 'inet6 fe80:' | head -1 | awk '{print $2}'` > + route add -inet6 fe80:: ${laddr} -prefixlen 10 -interface \ > + -cloning > + route add -inet6 ff02:: ${laddr} -prefixlen 16 -interface \ > + -cloning > + ;; > + esac The definition of $laddr is not compatible with the scoped addressing syntax. Instead, it needs something like: laddr=`ifconfig ${ipv6_default_interface} inet6 \ | grep "inet6 ${ipv6_default_interface}%fe80:" \ | head -1 | awk '{print $2}' | sed -e 's/.*%//'` There's another, similar snippit of code in the router-specific part of the script. Another problem occurred when I modified /etc/rc.network6 as above: route: writing to routing socket: Network is unreachable add net fe80::: gateway fe80::1: Network is unreachable route: writing to routing socket: Network is unreachable add net ff02::: gateway fe80::1: Network is unreachable add net ::ffff:0.0.0.0 gateway ::1 add net ::0.0.0.0 gateway ::1 net.inet.ip6.forwarding: 0 -> 0 net.inet.ip6.accept_rtadv: 0 -> 1 These actions all happened between the start and the end of DAD for my (one) Ethernet interface (I have a single-homed host). Finally, could you say whether or not lo0 should really be the default value for ipv6_default_interface in /etc/defaults/rc.conf? I have this vague feeling it's wrong but I don't know enough to say why: > +ipv6_default_interface="lo0" # Default output interface for scoped addrs. Thanks! Bruce. --==_Exmh_1638373650P Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: jIRKDXZehribnjnLkm/rMUCU4egd4mc4 iQA/AwUBOK3f49jKMXFboFLDEQJP3QCeI3CSu3eXfUN1GHPg0qncXMZnX5UAn2Ed 6MSW+r4FuQe4gliKgCmKMqXW =MKPN -----END PGP SIGNATURE----- --==_Exmh_1638373650P-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 16:56:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id E71C337BB51; Fri, 18 Feb 2000 16:56:38 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id TAA44482; Fri, 18 Feb 2000 19:57:31 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Fri, 18 Feb 2000 19:57:31 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Kris Kennaway Cc: freebsd-current@FreeBSD.org Subject: Supported ways to do RSA/OpenSSL on 4.0? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris, I was pointed to you for questions regarding whether or not certain ports would be working udner 4.0-RELEASE -- specifically, OpenSSH and related applications which depend on SSL/RSA. Do we plan to provide a consistent and documented way for users of FreeBSD to go from the RSA-disabled base library set to the RSA-enabled set, and in a way that provides adequate instruction? I get rather uninformative errors when trying to compile OpenSSH, SSLproxy, and Apache13-modssl, none of which is discovered by the ports mechanism, rather the application makefiles. While I understand that you are not the maintainer for these ports,... :-) It might be nice, for example, to have a stage in sysinstall for crypto-configuration--it would also be accessible post-install, and would provide easy access to install via package the underlying RSA libraries, with appropriate documentation of licensing issues and confirmation of location, etc. Presumably one could back-end this onto a set of ports or packages, so there would be more scalable command line/scriptable interface. This may already be in the works, but if so it wwasn't obvious from the 02-14 snapshot. Whatever the solution, what's currently there seems to be inadequate :-). Retaining an easy-to-use install path for common crypto-applications, such as SSH, Apache-modssl, SSLproxy, and others, is important as application accessibility (the ports collection) is a big selling point for FreeBSD. In the short term--what is the recommended way to install RSA support without rebuilding world? On real-world systems, rebuilding the world as soon as you have installed is not an option that can be taken seriously--you go from a 1 hour install time (or significantly less) to a build, etc cycle that can take a significant amount of time per-box. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 17: 7:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from coral.ocn.ne.jp (coral.ocn.ne.jp [202.234.232.80]) by hub.freebsd.org (Postfix) with ESMTP id 9E98B37BB48; Fri, 18 Feb 2000 17:07:44 -0800 (PST) (envelope-from takehiro@coral.ocn.ne.jp) Received: from nomad.ocn.ad.jp (p40-dn01myojin.tokyo.ocn.ne.jp [211.0.173.169]) by coral.ocn.ne.jp (8.9.1a/OCN) with SMTP id KAA16665; Sat, 19 Feb 2000 10:07:41 +0900 (JST) Date: Sat, 19 Feb 2000 10:07:41 +0900 (JST) Message-Id: <200002190107.KAA16665@coral.ocn.ne.jp> To: obrien@FreeBSD.org Cc: freebsd-current@FreeBSD.org, takehiro@coral.ocn.ne.jp Subject: Re: FreeBSD-current question re: binutils In-Reply-To: Your message of "Tue, 15 Feb 2000 08:35:12 -0800". <20000215083512.G77406@dragon.nuxi.com> From: takehiro@coral.ocn.ne.jp (Takehiro Suzuki) X-Mailer: mnews [version 1.22] 1999-12/19(Sun) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello,I'm Takehiro Suzuki,a FreeBSD user. :-) In article <20000215083512.G77406@dragon.nuxi.com> obrien@FreeBSD.org writes: >> > It is available from http://www.bsdclub.org/~takehiro/binutils.tar.gz . >> >> I am taking a look at it now. Since you did not rename any of the bits >> (such as `as', `ld', etc..) what is the impact of installing this port? I correct it as following. /usr/local/bin/as -> /usr/local/bin/as295 /usr/local/bin/ld -> /usr/local/bin/ld295 /usr/local/bin/objcopy -> /usr/local/bin/objcopy295 .... If source code is available from CVS automatically,Maxim's port is better. And such way to get source code is done in ports/openssh. Thanks, Takehiro Suzuki takehiro@coral.ocn.ne.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 19: 3:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from canonware.com (canonware.com [207.20.242.18]) by hub.freebsd.org (Postfix) with SMTP id 5F57737BB49 for ; Fri, 18 Feb 2000 19:03:42 -0800 (PST) (envelope-from jasone@canonware.com) Received: (qmail 31068 invoked by uid 1001); 19 Feb 2000 03:02:56 -0000 Date: Fri, 18 Feb 2000 19:02:56 -0800 From: Jason Evans To: Matthew Dillon Cc: current@FreeBSD.ORG Subject: Re: tentitive complete patch for MAP_GUARDED available Message-ID: <20000218190256.E28177@sturm.canonware.com> References: <20000218122554.A2978@nonpc.cs.rice.edu> <200002181905.LAA80267@apollo.backplane.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200002181905.LAA80267@apollo.backplane.com>; from dillon@apollo.backplane.com on Fri, Feb 18, 2000 at 11:05:31AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 11:05:31AM -0800, Matthew Dillon wrote: > I also think that a single guard page at the base of the > stack may be insufficient for some applications. I'm > considering adding yet another field to vm_map_entry > 'vm_pindex_t guard_pages' which allows the number of > guard pages to be specified (we can use mmap()'s offset > argument to pass the parameter). In general, a given number of guard pages is insufficient for some (perhaps non-existent) applications. The basic idea is to catch typical stack overflow. Trying to always catch stack overflow is not practical. Since this is a heuristic error detection technique, I'm not sure how much work/complexity it's worth to paramaterize the number of guard pages for each mapping. Jason To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 19:22: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from tomts2-srv.bellnexxia.net (tomts2.bellnexxia.net [209.226.175.140]) by hub.freebsd.org (Postfix) with ESMTP id 68DD037BB71 for ; Fri, 18 Feb 2000 19:22:03 -0800 (PST) (envelope-from kfarmer@sympatico.ca) Received: from sympatico.ca ([206.172.165.98]) by tomts2-srv.bellnexxia.net (InterMail vM.4.01.02.17 201-229-119) with ESMTP id <20000219032150.ZQYC17030.tomts2-srv.bellnexxia.net@sympatico.ca> for ; Fri, 18 Feb 2000 22:21:50 -0500 Message-ID: <38AE0CDE.2339FD8A@sympatico.ca> Date: Fri, 18 Feb 2000 22:24:14 -0500 From: Kelvin Farmer X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: 4.0(current) on a 486SLC2 ? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, I was wondering if its possible to run FreeBSD-4.0 on a 486 SLC2 66mhz. (win95 runs on this computer ok) I downloaded the floppies from Feb.14th, and disabled the hardware I don't have but the boot panics at: ... npx0: on motherboard npx0:Using IRQ 13 interface Fatal trap 12: page fault while in kernel mode ... (if useful I can copy down the rest of this panic) It doesn't have a pci bus, so my guess is that it dies probing the isa bus ??? Thanks, Kelvin kfarmer@sympatico.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 19:26:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from miles.lambdawerks.org (miles.lambdawerks.org [207.115.75.96]) by hub.freebsd.org (Postfix) with ESMTP id 198AF37BB71 for ; Fri, 18 Feb 2000 19:26:02 -0800 (PST) (envelope-from reggie@lambdawerks.org) Received: from trane (trane.lambdawerks.org [207.115.81.170]) by miles.lambdawerks.org (8.9.3/8.9.3) with SMTP id TAA03277 for ; Fri, 18 Feb 2000 19:25:23 -0800 (PST) (envelope-from reggie@lambdawerks.org) From: "Reginald S. Perry" To: Subject: Installing linux_base 6.1 Date: Fri, 18 Feb 2000 19:25:23 -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.2919.6600 Importance: Normal Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I am currently having a problem installing linux_base, both the port and the package on -current. I used to lurk to discover these problems by browsing the mailing list, but they are down. :-( I just cvsupped and rebuilt the world today and it still fails. Here are the messages: miles# pkg_add -v linux_base-6.1.tgz Requested space: 72761200 bytes, free space: 710092800 bytes in /var/tmp/instmp.UL3236 Package `linux_base-6.1' depends on `gdbm-1.8.0'. - already installed. Package `linux_base-6.1' depends on `rpm-2.5.6'. - already installed. extract: Package name is linux_base-6.1 extract: CWD to /compat/linux pkg_add: unable to cwd to '/compat' miles# make install ===> Extracting for linux_base-6.1 >> Checksum OK for rpm/setup-2.0.5-1.noarch.rpm. >> Checksum OK for rpm/filesystem-1.3.5-1.noarch.rpm. >> Checksum OK for rpm/basesystem-6.0-4.noarch.rpm. >> Checksum OK for rpm/ldconfig-1.9.5-15.i386.rpm. >> Checksum OK for rpm/glibc-2.1.2-11.i386.rpm. >> Checksum OK for rpm/termcap-9.12.6-15.i386.rpm. >> Checksum OK for rpm/libtermcap-2.0.8-18.i386.rpm. >> Checksum OK for rpm/bash-1.14.7-16.i386.rpm. >> Checksum OK for rpm/ncurses-4.2-25.i386.rpm. >> Checksum OK for rpm/zlib-1.1.3-5.i386.rpm. >> Checksum OK for rpm/info-3.12h-2.i386.rpm. >> Checksum OK for rpm/fileutils-4.0-8.i386.rpm. >> Checksum OK for rpm/grep-2.3-2.i386.rpm. >> Checksum OK for rpm/binutils-2.9.1.0.23-6.i386.rpm. >> Checksum OK for rpm/gd-1.3-5.i386.rpm. >> Checksum OK for rpm/gdbm-1.8.0-2.i386.rpm. >> Checksum OK for rpm/glib-1.2.5-1.i386.rpm. >> Checksum OK for rpm/ld.so-1.9.5-11.i386.rpm. >> Checksum OK for rpm/libc-5.3.12-31.i386.rpm. >> Checksum OK for rpm/libstdc++-2.9.0-24.i386.rpm. >> Checksum OK for rpm/sh-utils-2.0-1.i386.rpm. >> Checksum OK for rpm/readline-2.2.1-5.i386.rpm. >> Checksum OK for rpm/redhat-release-6.1-1.noarch.rpm. >> Checksum OK for rpm/rpm-3.0.3-2.i386.rpm. >> Checksum OK for rpm/setserial-2.15-2.i386.rpm. >> Checksum OK for rpm/slang-1.2.2-4.i386.rpm. >> Checksum OK for rpm/stat-1.5-11.i386.rpm. >> Checksum OK for rpm/tcsh-6.08.00-6.i386.rpm. >> Checksum OK for rpm/XFree86-libs-3.3.5-3.i386.rpm. >> Checksum OK for rpm/xpm-3.4k-1.i386.rpm. >> Checksum OK for rpm/glib-1.2.6-2.i386.rpm. ===> linux_base-6.1 depends on executable: rpm - found ===> Patching for linux_base-6.1 ===> Configuring for linux_base-6.1 ===> Installing for linux_base-6.1 setup-2.0.5-1.noarch.rpm filesystem-1.3.5-1.noarch.rpm basesystem-6.0-4.noarch.rpm ldconfig-1.9.5-15.i386.rpm glibc-2.1.2-11.i386.rpm termcap-9.12.6-15.i386.rpm libtermcap-2.0.8-18.i386.rpm execution of script failed -Reggie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 19:30:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id A6F8B37BB29 for ; Fri, 18 Feb 2000 19:30:19 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id TAA90856; Fri, 18 Feb 2000 19:30:17 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 19:30:17 -0800 (PST) From: Matthew Dillon Message-Id: <200002190330.TAA90856@apollo.backplane.com> To: Jason Evans Cc: current@FreeBSD.ORG Subject: Re: tentitive complete patch for MAP_GUARDED available References: <20000218122554.A2978@nonpc.cs.rice.edu> <200002181905.LAA80267@apollo.backplane.com> <20000218190256.E28177@sturm.canonware.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :In general, a given number of guard pages is insufficient for some (perhaps :non-existent) applications. The basic idea is to catch typical stack :overflow. Trying to always catch stack overflow is not practical. Since :this is a heuristic error detection technique, I'm not sure how much :work/complexity it's worth to paramaterize the number of guard pages for :each mapping. : :Jason I think it's important. Pthreads has calls to allow the user to set the stack size. At the moment our uthreads library malloc()'s the stack in this case. Eventually we want to be able to rewrite the code to use mmap() for all the stack types and then keep track of how big they were in the freelist for reuse. I think the following patch to our threads library, when combined with the guard-3.diff, optimizes our threads library for default thread stacks. I did a very simple test and it appears to work. One vm_map_entry is created every 8 64K pthread stacks with vm.map_entry_blk_opt set to 524288. The native port of the linux threads library can probably be patched fairly easily. The real linux threads library (/usr/compat/linux/lib/libpthread) mmap()s guard pages separately, which is impossible to optimize. We would need a special freebsd version of the library to get the VM map optimizations. It may be possible to eventually get rid of vm.map_entry_blk_opt entirely but that requires more work then I have time for right now (we basically have to support negative vm_object offsets in order to be able to grow an anonymous memory object downward to do it right). -Matt Matthew Dillon Index: uthread/uthread_create.c =================================================================== RCS file: /home/ncvs/src/lib/libc_r/uthread/uthread_create.c,v retrieving revision 1.24 diff -u -r1.24 uthread_create.c --- uthread/uthread_create.c 2000/01/19 07:04:46 1.24 +++ uthread/uthread_create.c 2000/02/19 03:04:01 @@ -137,12 +137,23 @@ PANIC("Cannot unlock gc mutex"); /* Stack: */ +#if defined(__FreeBSD__) + if (mmap((char *)stack - PTHREAD_STACK_GUARD, + PTHREAD_STACK_DEFAULT + PTHREAD_STACK_GUARD, + PROT_READ | PROT_WRITE, + MAP_STACK | MAP_GUARDED, + -1, PTHREAD_STACK_GUARD) == MAP_FAILED) { + ret = EAGAIN; + free(new_thread); + } +#else if (mmap(stack, PTHREAD_STACK_DEFAULT, PROT_READ | PROT_WRITE, MAP_STACK, -1, 0) == MAP_FAILED) { ret = EAGAIN; free(new_thread); } +#endif } } /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 20: 7:35 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 8D38D37BB6C for ; Fri, 18 Feb 2000 20:07:33 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA56017; Fri, 18 Feb 2000 20:07:16 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Reginald S. Perry" Cc: freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 In-reply-to: Your message of "Fri, 18 Feb 2000 19:25:23 PST." Date: Fri, 18 Feb 2000 20:07:16 -0800 Message-ID: <56014.950933236@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I am currently having a problem installing linux_base, both the port and the > package on -current. I used to lurk to discover these problems by browsing > the mailing list, but they are down. :-( > > I just cvsupped and rebuilt the world today and it still fails. Here are the > messages: Yes, I've seen this also. For some reason, either the linux_base package or pkg_add is broken here, and I'm tending to suspect the latter at this point since there shouldn't be any attempt to cd to /compat, nowhere in the packing list does it say to do that. Methinks a buffer is overflowing somewhere. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 20:10:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 9372737BB6D; Fri, 18 Feb 2000 20:10:52 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA59300; Fri, 18 Feb 2000 20:10:52 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 18 Feb 2000 20:10:51 -0800 (PST) From: Kris Kennaway To: Robert Watson Cc: freebsd-current@FreeBSD.org Subject: Re: break in libcrypto? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Robert Watson wrote: > Ok, is this a make depend in the top /usr/src, or in directories thjat > specifically require it. Or more practically speaking--I want the > directions in jail(8) to work every time. :-) How can this be fixed? Specifically, 'make depend' in secure/lib/lib{crypto,ssl,rsaglue} and secure/usr.bin/openssl, a covering set of which is 'make depend' in /usr/src :-) Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 20:23:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 7B4D237BB22; Fri, 18 Feb 2000 20:23:35 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA61050; Fri, 18 Feb 2000 20:23:19 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Fri, 18 Feb 2000 20:23:18 -0800 (PST) From: Kris Kennaway To: Robert Watson Cc: freebsd-current@FreeBSD.org Subject: Re: Supported ways to do RSA/OpenSSL on 4.0? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Robert Watson wrote: > I was pointed to you for questions regarding whether or not certain ports > would be working udner 4.0-RELEASE -- specifically, OpenSSH and related > applications which depend on SSL/RSA. All of the ports which explicitly depend on openssl should be working on all supported versions of FreeBSD, modulo screwups :) Jim Bloom has been putting a lot of work into getting these working - I have a couple of patches to commit, but they mostly seem to work fine as far as I've heard. However, Jordan mailed me this morning about a build problem with openssh on a fresh installation which looks very strange - it's like the test for a RSA-enabled openssl is falsely passing, which causes the build to die. This may be the problem you're seeing - as yet I don't have any real clues about why. Could you send me a build log from one of the failing ports as well as the output of 'nm /usr/lib/libcrypto.a | grep RSA_free'? Is this a fresh installation, i.e. with no older cruft possibly lying around? > Do we plan to provide a consistent and documented way for users of > FreeBSD to go from the RSA-disabled base library set to the > RSA-enabled set, and in a way that provides adequate instruction? I > get rather uninformative errors when trying to compile See chapter 6.5 in the handbook. > OpenSSH, SSLproxy, and Apache13-modssl, none of which is discovered by the > ports mechanism, rather the application makefiles. While I understand > that you are not the maintainer for these ports,... :-) > > It might be nice, for example, to have a stage in sysinstall for > crypto-configuration--it would also be accessible post-install, and would > provide easy access to install via package the underlying RSA libraries, > with appropriate documentation of licensing issues and confirmation of > location, etc. Presumably one could back-end this onto a set of ports or > packages, so there would be more scalable command line/scriptable > interface. The packages already exist and are described in the handbook, except they haven't yet made it onto the ftp site. You can pick them up from http://www.freebsd.org/~kris/openssl in the meantime. Sysinstall support is something I'd definitely like to see, but not something I have time (or knowledge) to do right now. I'll be adding some instructions to the release notes this weekend, and it should be giving a helpful error message if you try and install a port which requires RSA and you have a non-RSA library: .if ${USE_OPENSSL} == RSA _HASRSA= "`/usr/bin/nm /usr/lib/libcrypto.a | /usr/bin/grep RSA_free`" .if empty(_HASRSA) .BEGIN: @${ECHO} "This port requires RSA crypto, which is not present in your" @${ECHO} "version of OpenSSL. Please see Chapter 6.5 in the handbook" @${ECHO} "for a description of the problem and alternative solutions." @${FALSE} .endif .endif Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 20:31:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 84A8337BB8E for ; Fri, 18 Feb 2000 20:31:10 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id UAA91173; Fri, 18 Feb 2000 20:31:06 -0800 (PST) (envelope-from dillon) Date: Fri, 18 Feb 2000 20:31:06 -0800 (PST) From: Matthew Dillon Message-Id: <200002190431.UAA91173@apollo.backplane.com> To: "Jordan K. Hubbard" Cc: "Reginald S. Perry" , freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 References: <56014.950933236@zippy.cdrom.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :> I am currently having a problem installing linux_base, both the port and the :> package on -current. I used to lurk to discover these problems by browsing :> the mailing list, but they are down. :-( :> :> I just cvsupped and rebuilt the world today and it still fails. Here are the :> messages: : :Yes, I've seen this also. For some reason, either the linux_base :package or pkg_add is broken here, and I'm tending to suspect the :latter at this point since there shouldn't be any attempt to cd to :/compat, nowhere in the packing list does it say to do that. Methinks :a buffer is overflowing somewhere. : :- Jordan I had similar problems trying to install the latest linux_base onto a system which previously had the old (/compat/linux) version. I wound up having to rm -rf /compat/linux and /usr/compat/linux and then doing the make install, which worked. It created /usr/compat/linux and didn't seem to care that no /compat/linux existed. However, other linux programs (e.g. the linux netscape) still look in /compat so I had to create a softlink from /compat/linux to /usr/compat/linux in order for netscape to run. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 21:56:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by hub.freebsd.org (Postfix) with ESMTP id CB6C137BB0F for ; Fri, 18 Feb 2000 21:56:05 -0800 (PST) (envelope-from rjoseph@nwlink.com) Received: from ip227.r4.d.bel.nwlink.com (ip227.r4.d.bel.nwlink.com [207.202.172.227]) by smtp.nwlink.com (8.9.3/8.9.3) with ESMTP id VAA15278 for ; Fri, 18 Feb 2000 21:55:41 -0800 (PST) Date: Fri, 18 Feb 2000 21:50:49 -0800 (PST) From: R Joseph Wright X-Sender: rjoseph@mammalia.sea To: current@FreeBSD.org Subject: devices under 4.0 In-Reply-To: <20000218192552.B32540@freebie.lemis.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I recently upgraded from 3.2 to 4.0. I use an ide hard disk, and would like to know how to change over the devices. I created the new devices by copying over /usr/src/etc/MAKEDEV to a new /dev directory and running it, but it didn't create any ata* devices such as is shown in the kernel config file. It did make devices ada1, ada2, ada3, and ada4, which would correspond to the four slices on my disk, but if there are no freebsd partitions shown, such as ada4a, etc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 22: 8:37 2000 Delivered-To: freebsd-current@freebsd.org Received: from ind.alcatel.com (postal.xylan.com [208.8.0.248]) by hub.freebsd.org (Postfix) with ESMTP id E70EB37BB88 for ; Fri, 18 Feb 2000 22:08:35 -0800 (PST) (envelope-from wes@softweyr.com) Received: from mailhub.xylan.com (mailhub [198.206.181.70]) by ind.alcatel.com (8.9.3+Sun/8.9.1 (ind.alcatel.com 3.0 [OUT])) with SMTP id WAA01499; Fri, 18 Feb 2000 22:08:01 -0800 (PST) X-Origination-Site: Received: from omni.xylan.com by mailhub.xylan.com (SMI-8.6/SMI-SVR4 (mailhub 2.1 [HUB])) id WAA17754; Fri, 18 Feb 2000 22:08:01 -0800 Received: from softweyr.com (homer.softweyr.com [204.68.178.39]) by omni.xylan.com (8.9.3+Sun/8.9.1 (Xylan engr [SPOOL])) with ESMTP id WAA28758; Fri, 18 Feb 2000 22:07:59 -0800 (PST) Message-ID: <38AE34D8.F7F88DBA@softweyr.com> Date: Fri, 18 Feb 2000 23:14:48 -0700 From: Wes Peters Organization: Softweyr LLC X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Jon Hamilton Cc: Lyndon Nerenberg , current@freebsd.org Subject: Re: Crypto progress! (And a Biiiig TODO list) References: <20000218220138.0BD819B@woodstock.monkey.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Jon Hamilton wrote: > > In message <38AD7AE3.B4BEB308@softweyr.com>, Wes Peters wrote: > } Lyndon Nerenberg wrote: > } > > } > >>>>> "Mark" == Mark Murray writes: > } > > } > Mark> o A username may only be checked $number times per > } > Mark> $timeperiod; after that, _all_ answers are silently > } > Mark> converted to "no". > } > > } > Umm, massive DOS hole. > } > } Per username. If you publish your userlist, you're an idiot. The > } daemon should also immediately go into "breakin evasion mode" for > } all invalid usernames, answering the requests very slowly. > > You don't have to publish a userlist in order for some of that kind > of information to leak out. Besides, by answering very slowly for > invalid usernames you just gave the bad guys a way to deduce your > user list anyway. And how exactly are they supposed to tell the difference between answering slowly due to breakin evasion vs. answering slowly because the system is a 386sx/16? You would want to answer all "mistakes" slowly, but valid logins quickly. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC wes@softweyr.com http://softweyr.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Fri Feb 18 23:43:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id 1B1BA37BB29 for ; Fri, 18 Feb 2000 23:43:38 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from gravy.kishka.net (dyn-7.blackbox-2.netaxs.com [207.106.60.7]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id CAA22268 for ; Sat, 19 Feb 2000 02:39:36 -0500 (EST) Received: from localhost (gravy.kishka.net [127.0.0.1]) by gravy.kishka.net (8.9.3/8.9.3) with ESMTP id CAA00198 for ; Sat, 19 Feb 2000 02:39:35 -0500 (EST) (envelope-from bleez@netaxs.com) Date: Sat, 19 Feb 2000 02:39:35 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: current@freebsd.org Subject: Big ATA problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG The latest ata commits left my system completely unbootable. No disks were probed. I have on the motherboard's Alladin controller: HP 4x4x24 CD burner as master primary channel 40x CD as slave primary channel HP Colorado 8 Gig ATAPI tape as master secondary channel On a Promise Ultra66: WDC AC29100D WDC AC32500H each on thier own channel. Here are the boot messages (I had to write them down) ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY ata0-slave: timeout waiting for intr ata0-slave: identify failed these were repeated once and when attempting to mount / no devsw(msgdev=0 bootdev=0xa200000) no such device 'ad' Prior the the commit, the motherboard ide controllers were numbered ata0,1 and the Promise was ata2,3. After the commit it is switched around. Now the controllers probe as Promise ata0,1 and the motherboard as ata2,3. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 0:28:45 2000 Delivered-To: freebsd-current@freebsd.org Received: from miles.lambdawerks.org (miles.lambdawerks.org [207.115.75.96]) by hub.freebsd.org (Postfix) with ESMTP id 9E38237BB88 for ; Sat, 19 Feb 2000 00:28:41 -0800 (PST) (envelope-from reggie@lambdawerks.org) Received: from trane (trane.lambdawerks.org [207.115.81.170]) by miles.lambdawerks.org (8.9.3/8.9.3) with SMTP id AAA06595; Sat, 19 Feb 2000 00:22:34 -0800 (PST) (envelope-from reggie@lambdawerks.org) From: "Reginald S. Perry" To: "Matthew Dillon" , "Jordan K. Hubbard" Cc: Subject: RE: Installing linux_base 6.1 Date: Sat, 19 Feb 2000 00:22: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.2919.6600 Importance: Normal In-Reply-To: <200002190431.UAA91173@apollo.backplane.com> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Thanks all! rm -rf on /usr/compat/linux did the trick. Now I can try to install Oracle. :-) Thanks again. -Reggie -----Original Message----- From: Matthew Dillon [mailto:dillon@apollo.backplane.com] Sent: Friday, February 18, 2000 8:31 PM To: Jordan K. Hubbard Cc: Reginald S. Perry; freebsd-current@FreeBSD.ORG Subject: Re: Installing linux_base 6.1 :> I am currently having a problem installing linux_base, both the port and the :> package on -current. I used to lurk to discover these problems by browsing :> the mailing list, but they are down. :-( :> :> I just cvsupped and rebuilt the world today and it still fails. Here are the :> messages: : :Yes, I've seen this also. For some reason, either the linux_base :package or pkg_add is broken here, and I'm tending to suspect the :latter at this point since there shouldn't be any attempt to cd to :/compat, nowhere in the packing list does it say to do that. Methinks :a buffer is overflowing somewhere. : :- Jordan I had similar problems trying to install the latest linux_base onto a system which previously had the old (/compat/linux) version. I wound up having to rm -rf /compat/linux and /usr/compat/linux and then doing the make install, which worked. It created /usr/compat/linux and didn't seem to care that no /compat/linux existed. However, other linux programs (e.g. the linux netscape) still look in /compat so I had to create a softlink from /compat/linux to /usr/compat/linux in order for netscape to run. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 1:19:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 2D7B237BB6B; Sat, 19 Feb 2000 01:19:30 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m5.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id SAA16766; Sat, 19 Feb 2000 18:18:35 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m5.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id SAA04115; Sat, 19 Feb 2000 18:18:34 +0900 (JST) Received: from localhost ([192.168.245.162]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id SAA25697; Sat, 19 Feb 2000 18:18:32 +0900 (JST) To: ache@FreeBSD.ORG Cc: saxonww@ufl.edu, current@FreeBSD.ORG Subject: Re: Broken FTP In-Reply-To: <20000218152417.A52305@freebsd.org> References: <20000218103132.A74763@freebsd.org> <20000219044734W.shin@nd.net.fujitsu.co.jp> <20000218152417.A52305@freebsd.org> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000219181917Q.shin@nd.net.fujitsu.co.jp> Date: Sat, 19 Feb 2000 18:19:17 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 30 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Could you please create the patch which seems to be safely > > committed? That will be very much help. > > Well, I can try but I need to know most shortest and most trivial EPSV > check sequence from you since can't check it locally and don't know about EPSV. EPSV is just enhanced version of PASV, and I think it needs to check same kind of errors. Maybe same check as getreply() in ftp/ftp.c will be necessary. About the spec, please check RFC2428. But the problem is that the error message is printed in getreply() which is called from command(), because the error message is sent from server. So following type of check won't work because when returned from command(), the error message is already printed out... > Look at util.c setpeer() function lines > > if (command("PASSERVE %s", argv[1]) != COMPLETE) { ... > > and below > > if (command("SYST") == COMPLETE && overbose) { ... > > the check must be in this style... > -- > Andrey A. Chernov > > http://nagual.pp.ru/~ache/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 1:21: 6 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail7.fujitsu.co.jp (fgwmail7.fujitsu.co.jp [192.51.44.37]) by hub.freebsd.org (Postfix) with ESMTP id 29CAB37BBB9 for ; Sat, 19 Feb 2000 01:21:02 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m2.gw.fujitsu.co.jp by fgwmail7.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id SAA16840; Sat, 19 Feb 2000 18:19:18 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m2.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id SAA22289; Sat, 19 Feb 2000 18:19:17 +0900 (JST) Received: from localhost ([192.168.245.162]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id SAA25708; Sat, 19 Feb 2000 18:19:15 +0900 (JST) To: bmah@CA.Sandia.GOV Cc: bmah@california.sandia.gov, bauer@cc.univie.ac.at, current@FreeBSD.ORG Subject: Re: IPv6 In-Reply-To: <200002190012.QAA11354@nimitz.ca.sandia.gov> References: <20000216034713O.shin@nd.net.fujitsu.co.jp> <20000218215940K.shin@nd.net.fujitsu.co.jp> <200002190012.QAA11354@nimitz.ca.sandia.gov> X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000219182000U.shin@nd.net.fujitsu.co.jp> Date: Sat, 19 Feb 2000 18:20:00 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 43 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I ran across a few problems after I remade world. The new scoped > address syntax breaks /etc/rc.network6. In particular, some lines that > look like: Sorry not to announce it yet, but scoped addr format will still change, like below. addr%scope I'll send another mail to describe it in next to this mail. When this change happens, those problems will be resolved. > Finally, could you say whether or not lo0 should really be the default > value for ipv6_default_interface in /etc/defaults/rc.conf? I have this > vague feeling it's wrong but I don't know enough to say why: > > > +ipv6_default_interface="lo0" # Default output interface for scoped addrs. Maybe your concern is that packets to the default interface should be sent out to outside of host, at least? On the other hand, I thought there should be some default interface by default, but I afraid that an approach of just choosing some interface as default interface might be end up to choose non working interface. But now I feel choosing lo0 approach is also somewhat strange. So I'll try following approach. -"ipv6_default_interface" is empty by default -When all of "ipv6_network_interfaces", "gif_interfaces", and "ipv6_default_interface" are empty, then there will be no default interface -When "ipv6_default_interface" are empty but "ipv6_network_interfaces" and/or "gif_interfaces" is not empty, then choose one default interface from there. Thanks, Yoshinobu Inoue > Thanks! > > Bruce. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 1:21:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from fgwmail6.fujitsu.co.jp (fgwmail6.fujitsu.co.jp [192.51.44.36]) by hub.freebsd.org (Postfix) with ESMTP id CDBC337BB89 for ; Sat, 19 Feb 2000 01:21:20 -0800 (PST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from m1.gw.fujitsu.co.jp by fgwmail6.fujitsu.co.jp (8.9.3/3.7W-MX0002-Fujitsu Gateway) id SAA15110 for ; Sat, 19 Feb 2000 18:20:43 +0900 (JST) (envelope-from shin@nd.net.fujitsu.co.jp) Received: from incapgw.fujitsu.co.jp by m1.gw.fujitsu.co.jp (8.9.3/3.7W-0002-Fujitsu Domain Master) id SAA13660; Sat, 19 Feb 2000 18:20:42 +0900 (JST) Received: from localhost ([192.168.245.162]) by incapgw.fujitsu.co.jp (8.9.3/3.7W-0002) id SAA25753; Sat, 19 Feb 2000 18:20:41 +0900 (JST) To: freebsd-current@freebsd.org Subject: IPv6 scoped addr format change X-Mailer: Mew version 1.94 on Emacs 20.4 / Mule 4.0 (HANANOEN) X-Prom-Mew: Prom-Mew 1.93.4 (procmail reader for Mew) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <20000219182126A.shin@nd.net.fujitsu.co.jp> Date: Sat, 19 Feb 2000 18:21:26 +0900 From: Yoshinobu Inoue X-Dispatcher: imput version 990905(IM130) Lines: 50 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, Unfortunately, I have a notice that IPv6 scoped addr format will change again. It is once changed as the recent discussion between people who are preparing IPv6 scoped addr draft for next IETF meeting in March, like below. From addr@scope To scope%addr And I committed the change. But, in more recent discussion, it further changed like below. From scope%addr To addr%scope Because some MIB expert commented that optional data before addr is not suitable for MIB definition. About that change I didn't committed yet, because I'm afraid of another change. But this time the proposal seems to be stable. But anyway, there is no guarantee that it can get concensus at March IETF meeting, and same format could be adopted in the RFC to be published after the meeting, maybe around April or later. But some scope addr format is need to be supported in 4.0. So now I think of following things. -Adopt the format below now, and never change it again before 4.0 release. addr%scope -If future RFC will adopt another format, then support it also. E.g, Print out in new format. Support each format as input. Sorry for flapping, but it is the best approach I can think of now. Thanks, Yoshinobu Inoue To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 1:53:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id A646337BBA5 for ; Sat, 19 Feb 2000 01:53:17 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id CAA15883 for current@freebsd.org; Sat, 19 Feb 2000 02:21:49 -0800 (PST) Date: Sat, 19 Feb 2000 02:21:49 -0800 From: Alfred Perlstein To: current@freebsd.org Subject: "Fixing" init. Message-ID: <20000219022149.N21720@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I remeber being a newbie and getting burned by the need to explicitly turn a line 'off' in my /etc/ttys file instead of simply deleting it. This fixes it using a trivial mark then collect sweep. Can a couple people take a look? I'd like to get it into 4.0 because it seems to follow POLA better. "hey i deleted and HUP'd but init keeps spawing them!" thanks, -Alfred Index: init.c =================================================================== RCS file: /home/ncvs/src/sbin/init/init.c,v retrieving revision 1.37 diff -u -u -r1.37 init.c --- init.c 1999/11/22 04:23:09 1.37 +++ init.c 2000/02/19 13:53:52 @@ -156,6 +156,7 @@ char *se_window_argv_space; /* pre-parsed argument array space */ char **se_window_argv; /* pre-parsed argument array */ char *se_type; /* default terminal type */ + int se_collect; /* flag for garbage collection */ struct init_session *se_prev; struct init_session *se_next; } session_t; @@ -1330,7 +1331,7 @@ } /* - * This is an n-squared algorithm. We hope it isn't run often... + * This is an (n*2)+(n^2) algorithm. We hope it isn't run often... */ state_func_t clean_ttys() @@ -1344,6 +1345,14 @@ if (! sessions) return (state_func_t) multi_user; + /* + * mark all sessions for death, + * as we find or create new ones they'll be marked as keepers, + * nuke all the ones not found in /etc/ttys + */ + for (sp = sessions; sp != NULL; sp = sp->se_next) + sp->se_collect = 1; + devlen = sizeof(_PATH_DEV) - 1; while ((typ = getttyent()) != NULL) { ++session_index; @@ -1353,6 +1362,8 @@ break; if (sp) { + /* we want this one to live */ + sp->se_collect = 0; if (sp->se_index != session_index) { warning("port %s changed utmp index from %d to %d", sp->se_device, sp->se_index, @@ -1402,6 +1413,18 @@ } endttyent(); + + /* + * sweep through and kill all deleted sessions + * (ones who's /etc/ttys line was deleted) + */ + for (sp = sessions; sp != NULL; sp = sp->se_next) { + /* if the gc flag hasn't been cleared, nuke it. */ + if (sp->se_collect == 1) { + sp->se_flags |= SE_SHUTDOWN; + kill(sp->se_process, SIGHUP); + } + } return (state_func_t) multi_user; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 2:18:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 7BC4137BB6B for ; Sat, 19 Feb 2000 02:18:47 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id LAA93577; Sat, 19 Feb 2000 11:18:37 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002191018.LAA93577@freebsd.dk> Subject: Re: Big ATA problems In-Reply-To: from Bryan Liesner at "Feb 19, 2000 02:39:35 am" To: bleez@netaxs.com (Bryan Liesner) Date: Sat, 19 Feb 2000 11:18:37 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bryan Liesner wrote: > > The latest ata commits left my system completely unbootable. No disks > were probed. He, you always seem to be lucky when I change something :) > I have on the motherboard's Alladin controller: > HP 4x4x24 CD burner as master primary channel > 40x CD as slave primary channel > HP Colorado 8 Gig ATAPI tape as master secondary channel > > On a Promise Ultra66: > WDC AC29100D > WDC AC32500H > each on thier own channel. > > Here are the boot messages (I had to write them down) > ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY > ata0-slave: timeout waiting for intr > ata0-slave: identify failed That doesnt't make sense from the new stuffs angle... > these were repeated once > > and when attempting to mount / > no devsw(msgdev=0 bootdev=0xa200000) > no such device 'ad' > > Prior the the commit, the motherboard ide controllers were numbered > ata0,1 and the Promise was ata2,3. > > After the commit it is switched around. Now the controllers probe as > Promise ata0,1 and the motherboard as ata2,3. Hmm, yes you have one of those motherboards that screw the order of the controllers, it is an ASUS aliddin right ?? You could try to not use the ATA_STATIC_ID option, that way your disks should be numbered 0 and 1 and at least make it boot... I'll try to get this resolved in the meantime, I guess Rabson didn't think about this one, and neither did I for that matter... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 2:25:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 37E5637BBB6 for ; Sat, 19 Feb 2000 02:25:18 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id EAA08509; Sat, 19 Feb 2000 04:25:15 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-82.max1.wa.cyberlynk.net(207.227.118.82) by peak.mountin.net via smap (V1.3) id sma008503; Sat Feb 19 04:24:48 2000 Message-Id: <3.0.3.32.20000219042408.0093a100@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 19 Feb 2000 04:24:08 -0600 To: R Joseph Wright , current@FreeBSD.ORG From: "Jeffrey J. Mountin" Subject: Re: devices under 4.0 In-Reply-To: References: <20000218192552.B32540@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 09:50 PM 2/18/00 -0800, R Joseph Wright wrote: >I recently upgraded from 3.2 to 4.0. I use an ide hard disk, and would >like to know how to change over the devices. I created the new devices >by copying over /usr/src/etc/MAKEDEV to a new /dev directory and running >it, but it didn't create any ata* devices such as is shown in the kernel >config file. It made them, but they are not ad, not ata. >It did make devices ada1, ada2, ada3, and ada4, which would correspond to >the four slices on my disk, but if there are no freebsd partitions shown, >such as ada4a, etc. Not 4 slices, but 4 drives. A quick example. ad[0-3] are drives ad[0-3]s[1-4] are the slices ad[0-3]s[1-4][a-h] are the partitions cd /dev/ sh MAKEDEV ads0e works and you can then mount /dev/ads0e where you like. Using the "dangerously dedicated" method changes this, but let's not go there. Blame sysinstall or the pilot for drive slices without partitions, but if you specify to mount them, then they will be created upon upgrade or install. Otherwise your are on your own to make them. Also note 'sh MAKEDEV all' will update ad[0-3]s[1-4], but the trailing partitions [a-h] are not. To be quite honest I'd rather it didn't make all the possible partitions. Bit crowded in /dev as is. Adding another few hundred more to cover this "problem" has been discussed before. Course I tend to forget this myself, but am quite used to this behaviour. Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 2:33:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from peak.mountin.net (peak.mountin.net [207.227.119.2]) by hub.freebsd.org (Postfix) with ESMTP id 6C7E937BBA7 for ; Sat, 19 Feb 2000 02:33:24 -0800 (PST) (envelope-from jeff-ml@mountin.net) Received: (from daemon@localhost) by peak.mountin.net (8.9.1/8.9.1) id EAA08544; Sat, 19 Feb 2000 04:33:17 -0600 (CST) (envelope-from jeff-ml@mountin.net) Received: from dial-82.max1.wa.cyberlynk.net(207.227.118.82) by peak.mountin.net via smap (V1.3) id sma008542; Sat Feb 19 04:33:08 2000 Message-Id: <3.0.3.32.20000219043230.009e2430@207.227.119.2> X-Sender: jeff-ml@207.227.119.2 X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Sat, 19 Feb 2000 04:32:30 -0600 To: "Jordan K. Hubbard" From: "Jeffrey J. Mountin" Subject: Re: feedback on CD install of 4.0-RC2 Cc: current@FreeBSD.ORG In-Reply-To: <79206.950898990@zippy.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:36 AM 2/18/00 -0800, Jordan K. Hubbard wrote: >I will also say here and now that even I use the Standard installation >since I don't like having to remember all the canonical steps in setting >up a "stock" system and if anybody should remember them, it should be >me - I've probably installed FreeBSD at least 50,000 times. :-) Ah, but doesn't the now-standard-install make a partition for /var and /tmp? Would have to go back to 2.1.5 or thereabout since the last time I tried a then-novice-install. I'd rather have a /, swap, and /usr. Then, at need, add drives at mount points. No need to get into they why, what, and where, but suffice to say is the main reason for using custom. The ports and X are added after the initial install is done and not through sysinstall. Well OK, sometimes I do X with it. 8-) Jeff Mountin - jeff@mountin.net Systems/Network Administrator FreeBSD - the power to serve To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 2:57:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from relay.ucb.crimea.ua (UCB-Async4-CRISCO.CRIS.NET [212.110.129.130]) by hub.freebsd.org (Postfix) with ESMTP id 43BEB37BBC8 for ; Sat, 19 Feb 2000 02:57:18 -0800 (PST) (envelope-from ru@ucb.crimea.ua) Received: (from ru@localhost) by relay.ucb.crimea.ua (8.9.3/8.9.3/UCB) id MAA05026; Sat, 19 Feb 2000 12:57:02 +0200 (EET) (envelope-from ru) Date: Sat, 19 Feb 2000 12:57:02 +0200 From: Ruslan Ermilov To: Kelvin Farmer Cc: freebsd-current@FreeBSD.ORG Subject: Real hackers run -current on their laptop (was: Re: 4.0(current) on a 486SLC2 ?) Message-ID: <20000219125702.B2923@relay.ucb.crimea.ua> Mail-Followup-To: Kelvin Farmer , freebsd-current@FreeBSD.ORG References: <38AE0CDE.2339FD8A@sympatico.ca> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary=bg08WKrSYDhXBjb5 X-Mailer: Mutt 0.95.3i In-Reply-To: <38AE0CDE.2339FD8A@sympatico.ca>; from Kelvin Farmer on Fri, Feb 18, 2000 at 10:24:14PM -0500 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii On Fri, Feb 18, 2000 at 10:24:14PM -0500, Kelvin Farmer wrote: > Hi, > I was wondering if its possible to run FreeBSD-4.0 on a 486 SLC2 66mhz. > I'm sure it is possible, see attached. > (win95 runs on this computer ok) > I downloaded the floppies from Feb.14th, and disabled the hardware I > don't have > but the boot panics at: > > ... > npx0: on motherboard > npx0:Using IRQ 13 interface > > Fatal trap 12: page fault while in kernel mode > ... > (if useful I can copy down the rest of this panic) > > It doesn't have a pci bus, so my guess is that it dies probing the isa > bus ??? > > Thanks, > Kelvin > kfarmer@sympatico.ca > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message -- Ruslan Ermilov Sysadmin and DBA of the ru@ucb.crimea.ua United Commercial Bank, ru@FreeBSD.org FreeBSD committer, +380.652.247.647 Simferopol, Ukraine http://www.FreeBSD.org The Power To Serve http://www.oracle.com Enabling The Information Age --bg08WKrSYDhXBjb5 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="dmesg.boot" Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Thu Feb 17 20:48:58 EET 2000 ru@relay.ucb.crimea.ua:/usr/obj/4.0/home/ru/src-4.0/sys/TIPTOP Timecounter "i8254" frequency 1193182 Hz CPU: Cyrix 486SLC/DLC (486-class CPU) Origin = "CyrixInstead" DIR=0x00ff Stepping=0 Revision=0 real memory = 4587520 (4480K bytes) avail memory = 2543616 (2484K bytes) Preloaded elf kernel "kernel" at 0xc0235000. npx0: on motherboard npx0: 387 emulator isa0: on motherboard fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fd0: <1440-KB 3.5" drive> on fdc0 drive 0 ata0 at port 0x1f0 irq 14 on isa0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16450 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16450 ad0: 200MB [988/8/52] at ata0-master using BIOSPIO Mounting root from ufs:/dev/ad0a --bg08WKrSYDhXBjb5-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 3: 8:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id 3670137BBD4 for ; Sat, 19 Feb 2000 03:08:45 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from gravy.kishka.net (dyn-7.blackbox-2.netaxs.com [207.106.60.7]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id GAA05330; Sat, 19 Feb 2000 06:08:41 -0500 (EST) Received: from localhost (gravy.kishka.net [127.0.0.1]) by gravy.kishka.net (8.9.3/8.9.3) with ESMTP id GAA02957; Sat, 19 Feb 2000 06:08:38 -0500 (EST) (envelope-from bleez@netaxs.com) Date: Sat, 19 Feb 2000 06:08:38 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: Soren Schmidt Cc: Bryan Liesner , current@FreeBSD.ORG Subject: Re: Big ATA problems In-Reply-To: <200002191018.LAA93577@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Soren Schmidt wrote: >It seems Bryan Liesner wrote: >> >> The latest ata commits left my system completely unbootable. No disks >> were probed. > >He, you always seem to be lucky when I change something :) I always hold my breath when I cvsup and see changes to ata* :) >Hmm, yes you have one of those motherboards that screw the order >of the controllers, it is an ASUS aliddin right ?? It's a PCChips motherboard... > >You could try to not use the ATA_STATIC_ID option, that way your >disks should be numbered 0 and 1 and at least make it boot... Never used that option before. -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 6: 0:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 4E22B37BC15 for ; Sat, 19 Feb 2000 06:00:03 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id OAA50270; Sat, 19 Feb 2000 14:59:54 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002191359.OAA50270@freebsd.dk> Subject: Re: Big ATA problems In-Reply-To: from Bryan Liesner at "Feb 19, 2000 06:08:38 am" To: bleez@netaxs.com (Bryan Liesner) Date: Sat, 19 Feb 2000 14:59:54 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bryan Liesner wrote: > On Sat, 19 Feb 2000, Soren Schmidt wrote: > > >It seems Bryan Liesner wrote: > >> > >> The latest ata commits left my system completely unbootable. No disks > >> were probed. > > > >He, you always seem to be lucky when I change something :) > > I always hold my breath when I cvsup and see changes to ata* :) > > > >Hmm, yes you have one of those motherboards that screw the order > >of the controllers, it is an ASUS aliddin right ?? For those that has this problem, this patch should do the trick: Index: ata-all.c =================================================================== RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v retrieving revision 1.48 diff -u -r1.48 ata-all.c --- ata-all.c 2000/02/18 20:57:27 1.48 +++ ata-all.c 2000/02/19 13:58:58 @@ -336,7 +336,7 @@ if (pci_get_progif(dev) & PCIP_STORAGE_IDE_MASTERDEV) lun = unit; else - lun = -1; + lun = 2; if (!(child = device_add_child(dev, "ata", lun))) return ENOMEM; -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 6:42:18 2000 Delivered-To: freebsd-current@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id 24A4D37BCA3; Sat, 19 Feb 2000 06:41:59 -0800 (PST) (envelope-from robert@cyrus.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id JAA00742; Sat, 19 Feb 2000 09:42:53 -0500 (EST) (envelope-from robert@cyrus.watson.org) Date: Sat, 19 Feb 2000 09:42:53 -0500 (EST) From: Robert Watson X-Sender: robert@fledge.watson.org Reply-To: Robert Watson To: Kris Kennaway Cc: freebsd-current@FreeBSD.org Subject: Re: Supported ways to do RSA/OpenSSL on 4.0? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, 18 Feb 2000, Kris Kennaway wrote: > All of the ports which explicitly depend on openssl should be working on > all supported versions of FreeBSD, modulo screwups :) Jim Bloom has been > putting a lot of work into getting these working - I have a couple of > patches to commit, but they mostly seem to work fine as far as I've > heard. > > However, Jordan mailed me this morning about a build problem with openssh > on a fresh installation which looks very strange - it's like the test for > a RSA-enabled openssl is falsely passing, which causes the build to die. > This may be the problem you're seeing - as yet I don't have any real clues > about why. Could you send me a build log from one of the failing ports as > well as the output of 'nm /usr/lib/libcrypto.a | grep RSA_free'? Is this a > fresh installation, i.e. with no older cruft possibly lying around? Here's the build dying: cumin# pwd /usr/ports/security/openssh cumin# make ===> Patching for OpenSSH-1.2.2 ===> Applying FreeBSD patches for OpenSSH-1.2.2 ===> Configuring for OpenSSH-1.2.2 ===> Building for OpenSSH-1.2.2 ===> lib Warning: Object directory not changed from original /usr/ports/security/openssh/ work/ssh/lib cc -O -pipe -I/usr/ports/security/openssh/work/ssh/lib/.. -I/usr/include -DINET6 -I/usr/ports/security/openssh/work/ssh/lib/.. -I/usr/local/usr/include -c /usr/ ports/security/openssh/work/ssh/lib/../authfd.c -o authfd.o In file included from /usr/ports/security/openssh/work/ssh/lib/../ssh.h:21, from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:19: /usr/ports/security/openssh/work/ssh/lib/../rsa.h:22: openssl/rsa.h: No such fil e or directory /usr/ports/security/openssh/work/ssh/lib/../authfd.c:27: openssl/rsa.h: No such file or directory In file included from /usr/ports/security/openssh/work/ssh/lib/../ssh.h:21, from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:19: /usr/ports/security/openssh/work/ssh/lib/../rsa.h:25: syntax error before `*' /usr/ports/security/openssh/work/ssh/lib/../rsa.h:35: syntax error before `RSA' /usr/ports/security/openssh/work/ssh/lib/../rsa.h:36: syntax error before `RSA' In file included from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:19: /usr/ports/security/openssh/work/ssh/lib/../ssh.h:299: syntax error before `RSA' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:416: syntax error before `RSA' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:425: syntax error before `RSA' /usr/ports/security/openssh/work/ssh/lib/../ssh.h:437: syntax error before `RSA' In file included from /usr/ports/security/openssh/work/ssh/lib/../authfd.c:21: /usr/ports/security/openssh/work/ssh/lib/../authfd.h:99: syntax error before `RS A' /usr/ports/security/openssh/work/ssh/lib/../authfd.h:107: syntax error before `R SA' /usr/ports/security/openssh/work/ssh/lib/../authfd.c:343: syntax error before `R SA' /usr/ports/security/openssh/work/ssh/lib/../authfd.c: In function `ssh_add_ident ity': /usr/ports/security/openssh/work/ssh/lib/../authfd.c:352: `key' undeclared (firs t use in this function) /usr/ports/security/openssh/work/ssh/lib/../authfd.c:352: (Each undeclared ident ifier is reported only once /usr/ports/security/openssh/work/ssh/lib/../authfd.c:352: for each function it a ppears in.) /usr/ports/security/openssh/work/ssh/lib/../authfd.c:360: `comment' undeclared ( first use in this function) /usr/ports/security/openssh/work/ssh/lib/../authfd.c:367: `auth' undeclared (fir st use in this function) /usr/ports/security/openssh/work/ssh/lib/../authfd.c: At top level: /usr/ports/security/openssh/work/ssh/lib/../authfd.c:430: syntax error before `R SA' /usr/ports/security/openssh/work/ssh/lib/../authfd.c: In function `ssh_remove_id entity': /usr/ports/security/openssh/work/ssh/lib/../authfd.c:439: `key' undeclared (firs t use in this function) /usr/ports/security/openssh/work/ssh/lib/../authfd.c:448: `auth' undeclared (fir st use in this function) *** Error code 1 Stop in /usr/ports/security/openssh/work/ssh/lib. *** Error code 1 Stop in /usr/ports/security/openssh/work/ssh. *** Error code 1 Stop in /usr/ports/security/openssh. *** Error code 1 Stop in /usr/ports/security/openssh. *** Error code 1 Stop in /usr/ports/security/openssh. cumin# Here's the output of nm on the default installed /usr/lib/libcrypto.a: cumin# nm /usr/lib/libcrypto.a | grep RSA_free cumin# This was installed from the 02-14-2000 snapshot a day or two ago, and I have not upgraded world since then. > > Do we plan to provide a consistent and documented way for users of > > FreeBSD to go from the RSA-disabled base library set to the > > RSA-enabled set, and in a way that provides adequate instruction? I > > get rather uninformative errors when trying to compile > > See chapter 6.5 in the handbook. The handbook appears not to have been installed as part of the ``Novice'' install that I selected. This suggests that the documentation is not sufficiently accessible. However, I did find the following: The OpenSSL package with RSAREF support for USA users which you can get from ftp.FreeBSD.org. Note: Be sure to read the license before installing! This is NOT licensed for general-purpose use! The OpenSSL package for International (non-USA) users. This is not legal for general use in the USA, but international users should use this version because the RSA implementation is faster and more flexible. It is available from ftp.internat.FreeBSD.org. I was unable to build the OpenSSL port, and installing the RSAref port didn't fix these build problems. Also, these directions are pretty non-specific--could you throw in URLs? Also, as I mentioned for auto-install, either building this into sysinstall as a specific install stage would be a good idea. Is the intent that we install the OpenSSL package into /usr/local/lib, or will this stuff be dumped in /usr/lib? Having two different instances of OpenSSL with different degrees of breakage will be pretty confusing for developers and porters of SSL applications, suggesting that the logical target is /usr/lib. It also might be good to have a /usr/include/openssl/README that says ``Looking for rsa.h? You need to read section 6.5 of the handbook''. Also, I note that we don't include an OpenSSL man page: cumin# man openssl No manual entry for openssl cumin# man ssl No manual entry for ssl cumin# man crypto No manual entry for crypto These logical sounding potential manpages would probably be a good place to mirror the handbook information. Are there OpenSSL man pages installed somewhere in the base system? > > OpenSSH, SSLproxy, and Apache13-modssl, none of which is discovered by the > > ports mechanism, rather the application makefiles. While I understand > > that you are not the maintainer for these ports,... :-) > > > > It might be nice, for example, to have a stage in sysinstall for > > crypto-configuration--it would also be accessible post-install, and would > > provide easy access to install via package the underlying RSA libraries, > > with appropriate documentation of licensing issues and confirmation of > > location, etc. Presumably one could back-end this onto a set of ports or > > packages, so there would be more scalable command line/scriptable > > interface. > > The packages already exist and are described in the handbook, except they > haven't yet made it onto the ftp site. You can pick them up from > http://www.freebsd.org/~kris/openssl in the meantime. Sysinstall support > is something I'd definitely like to see, but not something I have time (or > knowledge) to do right now. Is this an export-friendly location for non-USA folks? Any chance Jordan or someone wants to hack up an install stage? I think this is important--especially having it automated, as the automated one-step install of crypto-based applications is important. If we're willing to pause the install to ask about X desktops, this sounds like a good candidate also. It also sounds like a good time to generate an initial value for USA_RESIDENT in make.conf. > I'll be adding some instructions to the release notes this weekend, and it > should be giving a helpful error message if you try and install a port > which requires RSA and you have a non-RSA library: > > .if ${USE_OPENSSL} == RSA > _HASRSA= "`/usr/bin/nm /usr/lib/libcrypto.a | /usr/bin/grep RSA_free`" > .if empty(_HASRSA) > .BEGIN: > @${ECHO} "This port requires RSA crypto, which is not present in > your" > @${ECHO} "version of OpenSSL. Please see Chapter 6.5 in the > handbook" > @${ECHO} "for a description of the problem and alternative > solutions." > @${FALSE} > .endif > .endif Sounds like a step in the right direction, but currently a no-start due to lack of handbook in the install. Although it's more work, I'd rather see an OpenSSL manpage that includes this information, a sure-fire way to check to see what's installed, a sysinstall-phase, etc. Thanks! Looks like all this will be great once it's working! Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 7:13:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from www.geocrawler.com (sourceforge.net [198.186.203.33]) by hub.freebsd.org (Postfix) with ESMTP id 9476E37BC85 for ; Sat, 19 Feb 2000 07:13:48 -0800 (PST) (envelope-from nobody@www.geocrawler.com) Received: (from nobody@localhost) by www.geocrawler.com (8.9.3/8.9.3) id HAA01528; Sat, 19 Feb 2000 07:13:50 -0800 Date: Sat, 19 Feb 2000 07:13:50 -0800 Message-Id: <200002191513.HAA01528@www.geocrawler.com> To: freebsd-current@freebsd.org Subject: openssl in -current From: "Victor Salaman" Reply-To: "Victor Salaman" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This message was sent from Geocrawler.com by "Victor Salaman" Be sure to reply to that address. I personally think that it's braindead to add openssl to the system and stripout parts of it (RSA & IDEA). Don't get me wrong, I love to have openssl inside the system, it's just that a lot of things don't work as expected (OpenSSH, Apache- modssl,etc). I think there are sneaky ways to get around the export restrictions, patents, etc. I think FreeBSD should let the user decide wether they want to take the resposability of installing the restricted code or not, and not let the developers decide that. As a quick fix, I have setup openssl094 separate from the system build, and have incorporated a script to copy the "original" libraries in /usr/lib as the original authors of OpenSSL intented and now my openssh port, apache-modssl, (everything) works as expected. Imagine that you are setting up 100 FreeBSD machines, it's not an option to do make world from sources and build a "new" non-crippled crypto system. You just want to install it and go! This is not a flame. Just my 2 cents. Geocrawler.com - The Knowledge Archive To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 7:17:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from devils.maquina.com (devils.maquina.com [62.229.71.43]) by hub.freebsd.org (Postfix) with ESMTP id 96FFC37BC9C for ; Sat, 19 Feb 2000 07:17:18 -0800 (PST) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.maquina.com (8.9.3/8.9.3) with ESMTP id PAA52032; Sat, 19 Feb 2000 15:16:53 GMT (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.maquina.com: gabriel owned process doing -bs Date: Sat, 19 Feb 2000 15:16:53 +0000 (WET) From: Jose Gabriel Marcelino To: Soren Schmidt Cc: current@FreeBSD.ORG Subject: Re: Big ATA problems In-Reply-To: <200002191359.OAA50270@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG hi Soren, The latest ata commits left me unbootable too, the patch you provided below didn't help this too. I have a very different configuration from Bryan's (much simpler too): - DFI K6XV3+ mb with VIA MVP3 chipset ata-pci0: port 0xe000-0xe00f at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... ad0: 14664MB [31781/15/63] at ata0-master using UDMA33 ad1: 4103MB [8894/15/63] at ata0-slave using UDMA33 acd0: DVD-ROM at ata1-master using UDMA33 afd0: 96MB [96/64/32] at ata1-slave using PIO0 With the latest kernel I get this relevant messages: atapci0: port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed nodevsw (majdev=0 bootdev=0xa0200000) Mouting root from ufs:/dev/wd0s1a no such device 'wd' Thinking that the wd device was gone I tried using /dev/ad0s1a, but it was the same: no such device 'ad' Thanks, Gabriel > > >> The latest ata commits left my system completely unbootable. No disks > > >> were probed. > > > > Index: ata-all.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/ata/ata-all.c,v > retrieving revision 1.48 > diff -u -r1.48 ata-all.c > --- ata-all.c 2000/02/18 20:57:27 1.48 > +++ ata-all.c 2000/02/19 13:58:58 > @@ -336,7 +336,7 @@ > if (pci_get_progif(dev) & PCIP_STORAGE_IDE_MASTERDEV) > lun = unit; > else > - lun = -1; > + lun = 2; > > if (!(child = device_add_child(dev, "ata", lun))) > return ENOMEM; > > -Søren > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 7:27:50 2000 Delivered-To: freebsd-current@freebsd.org Received: from devils.maquina.com (devils.maquina.com [62.229.71.43]) by hub.freebsd.org (Postfix) with ESMTP id AFED737BC6B for ; Sat, 19 Feb 2000 07:27:45 -0800 (PST) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.maquina.com (8.9.3/8.9.3) with ESMTP id PAA52063 for ; Sat, 19 Feb 2000 15:27:40 GMT (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.maquina.com: gabriel owned process doing -bs Date: Sat, 19 Feb 2000 15:27:40 +0000 (WET) From: Jose Gabriel Marcelino To: current@freebsd.org Subject: Many PCI buses and probes on recent kernels Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Apart from the more recently broken ATA stuff I started getting the following (cosmetic only really, but it leaves me wondering..) in kernels compiled around the 12th this month. This machine really just has one pci bus (this is a simple K6 VIA MVP3 motherboard). Also the unknow (to FreeBSD) PCI card is probed too many times (I just have one). This unkown card btw is Realmagic's Hollywood+ DVD card (only supported in Windows unfortunately since it's a great great card). Everything works great apart from that using this kernel so I think this is cosmetic only... Thanks Gabriel Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #33: Sat Feb 12 22:20:35 WET 2000 root@toor.maquina.com:/usr/src/sys/compile/TOOR Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 400911377 Hz CPU: AMD-K6(tm) 3D processor (400.91-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 real memory = 134217728 (131072K bytes) avail memory = 126025728 (123072K bytes) Preloaded elf kernel "kernel" at 0xc03f7000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc03f709c. Preloaded elf module "splash_bmp.ko" at 0xc03f70ec. Preloaded splash_image_data "/boot/splash.bmp" at 0xc03f7190. VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc0337562 (1000022) VESA: NVidia devclass_alloc_unit: pcib0 already exists, using next available unit number npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib2: at device 1.0 on pci0 pci1: on pcib2 STvga-pci0: mem 0xe6000000-0xe7ffffff,0xe4000000-0xe4ffffff irq 11 at device 0.0 on pci1 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xe000-0xe00f at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 uhci0: port 0xe400-0xe41f irq 5 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhub1: Texas Instruments UT-USB41 hub, class 9/0, rev 1.00/1.00, addr 2 uhub1: 4 ports with 4 removable, self powered ums0: Logitech N48, rev 1.00/4.01, addr 3, iclass 3/1 ums0: 3 buttons and Z dir. ulpt0: Lexmark International, Inc. Lexmark Optra E310, rev 1.00/1.00, addr 4, iclass 7/1 pcm0: port 0xe800-0xe83f irq 9 at device 18.0 on pci0 pci0: unknown card (vendor=0x1105, dev=0x8300) at 20.0 irq 5 devclass_alloc_unit: pci1 already exists, using next available unit number pcib1: on motherboard pci2: on pcib1 pci2: unknown card (vendor=0x1105, dev=0x8300) at 0.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 1.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 2.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 3.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 4.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 5.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 6.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 7.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 8.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 9.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 10.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 11.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 12.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 13.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 14.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 15.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 16.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 17.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 18.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 19.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 20.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 21.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 22.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 23.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 24.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 25.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 26.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 27.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 28.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 29.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 30.0 irq 5 pci2: unknown card (vendor=0x1105, dev=0x8300) at 31.0 irq 5 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 psm: keyboard controller failed. vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/15 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 isic0 at port 0xd80,0x960-0x99f,0x160-0x19f,0x560-0x59f irq 10 flags 0x3 on isa0 isic0: Teles S0/16.3 i4btrc: 4 ISDN trace device(s) attached i4brbch: 4 raw B channel access device(s) attached i4btel: 2 ISDN telephony interface device(s) attached i4bipr: 4 IP over raw HDLC ISDN device(s) attached (VJ header compression) i4bctl: ISDN system control port attached i4bisppp: 4 ISDN SyncPPP device(s) attached i4b: ISDN call control device attached IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 10 packets/entry by default IPsec: Initialized Security Association Processing. ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 14664MB [31781/15/63] at ata0-master using UDMA33 ad1: 4103MB [8894/15/63] at ata0-slave using UDMA33 acd0: DVD-ROM at ata1-master using UDMA33 Mounting root from ufs:/dev/wd0s1a i4b: unit 0, assigned TEI = 124 = 0x7c To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 7:34:13 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id D31BB37BC94 for ; Sat, 19 Feb 2000 07:34:10 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id QAA72945; Sat, 19 Feb 2000 16:33:55 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002191533.QAA72945@freebsd.dk> Subject: Re: Big ATA problems In-Reply-To: from Jose Gabriel Marcelino at "Feb 19, 2000 03:16:53 pm" To: gabriel@maquina.com (Jose Gabriel Marcelino) Date: Sat, 19 Feb 2000 16:33:54 +0100 (CET) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Jose Gabriel Marcelino wrote: Well, rebuild the loader, that helped Bryan, apparently it has nothing to do with the ata driver.... > The latest ata commits left me unbootable too, the patch you provided > below didn't help this too. I have a very different configuration from > Bryan's (much simpler too): > > - DFI K6XV3+ mb with VIA MVP3 chipset > ata-pci0: port 0xe000-0xe00f at device 7.1 > on pci0 > ata0 at 0x01f0 irq 14 on ata-pci0 > ata1 at 0x0170 irq 15 on ata-pci0 > ... > ad0: 14664MB [31781/15/63] at ata0-master using UDMA33 > ad1: 4103MB [8894/15/63] at ata0-slave using UDMA33 > acd0: DVD-ROM at ata1-master using UDMA33 > afd0: 96MB [96/64/32] at ata1-slave using PIO0 -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 7:39:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id D2A4C37BC39 for ; Sat, 19 Feb 2000 07:39:50 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from gravy.kishka.net (dyn-16.blackbox-2.netaxs.com [207.106.60.16]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id KAA26094; Sat, 19 Feb 2000 10:39:46 -0500 (EST) Received: from localhost (gravy.kishka.net [127.0.0.1]) by gravy.kishka.net (8.9.3/8.9.3) with ESMTP id KAA00455; Sat, 19 Feb 2000 10:39:42 -0500 (EST) (envelope-from bleez@netaxs.com) Date: Sat, 19 Feb 2000 10:39:42 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: Jose Gabriel Marcelino Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: Big ATA problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote: > >hi Soren, > >The latest ata commits left me unbootable too, the patch you provided >below didn't help this too. I have a very different configuration from >Bryan's (much simpler too): > Jose, the problem seems to be resolved by rebuilding the boot loader. Or bypass the loader altogether. cd /usr/src/sys/boot make obj make all install and you'll be able to boot the kernel with the latest ata stuff. Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 8:58: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from piranha.amis.net (piranha.amis.net [212.18.32.3]) by hub.freebsd.org (Postfix) with ESMTP id 0C87137BC40 for ; Sat, 19 Feb 2000 08:57:47 -0800 (PST) (envelope-from blaz@amis.net) Received: from gold.amis.net (gold.amis.net [212.18.32.254]) by piranha.amis.net (Postfix) with ESMTP id 04EBD5D9D for ; Sat, 19 Feb 2000 17:57:44 +0100 (CET) Date: Sat, 19 Feb 2000 17:57:43 +0100 (CET) From: Blaz Zupan To: freebsd-current@freebsd.org Subject: CGA instead of VGA Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On -current my VGA card is being used as a CGA card. It is correctly recognized as a VGA: vga-pci0: mem 0xf8000000-0xfbffffff irq 11 at device 15.0 on pci0 vga0: at port 0x3d0-0x3db iomem 0xb8000-0xbffff on isa0 but then used as a CGA: sc0: CGA <16 virtual consoles, flags=0x200> The problem is, that I can't set fonts: # vidcontrol real memory = 67108864 (65536K bytes) avail memory = 62050304 (60596K bytes) Preloaded elf kernel "kernel" at 0xc02e7000. Intel Pentium detected, installing workaround for F00F bug npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: port 0xfcb0-0xfcbf at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 9 chip1: port 0x7000-0x700f at device 7.3 on pci0 ed0: port 0xfcc0-0xfcdf irq 9 at device 13.0 on pci0 ed0: address 00:80:48:ca:93:de, type NE2000 (16 bit) ahc0: port 0xf800-0xf8ff mem 0xfedff000-0xfedfffff irq 9 at device 14.0 on pci0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs vga-pci0: mem 0xf8000000-0xfbffffff irq 11 at device 15.0 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3d0-0x3db iomem 0xb8000-0xbffff on isa0 sc0: on isa0 sc0: CGA <16 virtual consoles, flags=0x200> pcic: polling mode pcic: polling mode pcic0: at port 0x3e0 iomem 0xd0000 on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38f,0x330-0x331,0x370-0x371 irq 5 drq 0,1 on isa0 joy0: at port 0x201 on isa0 ad0: 13783MB [28005/16/63] at ata0-master using UDMA33 pccard: card inserted, slot 0 Mounting root from ufs:/dev/ad0s1a da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15) da1: 1547MB (3170160 512 byte sectors: 255H 63S/T 197C) cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present 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: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) wi0: at port 0x240-0x27f irq 10 slot 0 on pccard0 wi0: Ethernet address: 00:60:1d:f1:15:bb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 10:44:46 2000 Delivered-To: freebsd-current@freebsd.org Received: from mailgate.rz.uni-karlsruhe.de (mailgate.rz.uni-karlsruhe.de [129.13.64.97]) by hub.freebsd.org (Postfix) with ESMTP id EE8CB37BCE0 for ; Sat, 19 Feb 2000 10:44:13 -0800 (PST) (envelope-from un1i@rz.uni-karlsruhe.de) Received: from rz114s0-priv-server (exim@rz114s0-197.rz.uni-karlsruhe.de [129.13.197.20]) by mailgate.rz.uni-karlsruhe.de with esmtp (Exim 3.02 #2) id 12MEoE-0000m6-00; Sat, 19 Feb 2000 19:40:51 +0100 Received: from un1i by rz114s0-priv-server with local (Exim 2.12 #1) id 12MEoE-00028h-00; Sat, 19 Feb 2000 19:40:50 +0100 Date: Sat, 19 Feb 2000 19:40:49 +0100 From: Philipp Mergenthaler To: Bryan Liesner Cc: Soren Schmidt , current@FreeBSD.ORG Subject: Re: Big ATA problems Message-ID: <20000219194049.A7428@rz.uni-karlsruhe.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 19, 2000 at 10:39:42AM -0500, Bryan Liesner wrote: > Jose, the problem seems to be resolved by rebuilding the boot > loader. Or bypass the loader altogether. > > cd /usr/src/sys/boot > make obj > make all install > > and you'll be able to boot the kernel with the latest ata stuff. Do you use KLMs? When I load the kernel alone, it detects the ATA devices normally. When I let the loader load a module in addition to the kernel (I tried it with each of vinum, netgraph, linux, splash_bmp and joy), it fails with these messages: ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed (The primary slave is a CDROM.) This was with linux.ko; with joy.ko, the line "WARNING:..." wasn't printed. (BTW, with kernel+umap.ko, the ATA detection succeeded.) Every access to an ATA device then fails like this: # fdisk ad0 fdisk: cannot open disk /dev/rad0: Device not configured # ls -l *ad0 crw-r----- 1 root operator 116, 0x00010002 Feb 19 17:03 ad0 crw-r----- 1 root operator 116, 0x00010002 Feb 19 17:03 rad0 This is with an updated /boot/loader and the "lun=2" patch applied. Bye, Philipp P.S.: Here's a diff between a successful and an unsuccessful verbose boot: ~%diff -1000 -u /var/tmp/dmesgv_ok /var/tmp/dmesgv_fail --- /var/tmp/dmesgv_ok Sat Feb 19 18:55:55 2000 +++ /var/tmp/dmesgv_fail Sat Feb 19 19:51:41 2000 @@ -1,247 +1,205 @@ Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #145: Sat Feb 19 18:13:37 CET 2000 p@i609.hadiko.de:/usr/src/sys/compile/I609 -Calibrating clock(s) ... TSC clock: 233862696 Hz, i8254 clock: 1193178 Hz +Calibrating clock(s) ... TSC clock: 233862171 Hz, i8254 clock: 1193176 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method -Timecounter "TSC" frequency 233864747 Hz -CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) +Timecounter "TSC" frequency 233865033 Hz +CPU: AMD-K6tm w/ multimedia extensions (233.87-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping = 2 Features=0x8001bf AMD Features=0x400<> Data TLB: 128 entries, 2-way associative Instruction TLB: 64 entries, 1-way associative L1 data cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative L1 instruction cache: 32 kbytes, 32 bytes/line, 2 lines/tag, 2-way associative Write Allocate Enable Limit: 96M bytes Write Allocate 15-16M bytes: Enable Hardware Write Allocate Control: Disable real memory = 100663296 (98304K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) -0x0033f000 - 0x05ff5fff, 97218560 bytes (23735 pages) -avail memory = 94158848 (91952K bytes) +0x00353000 - 0x05ff5fff, 97136640 bytes (23715 pages) +avail memory = 94076928 (91872K bytes) bios32: Found BIOS32 Service Directory header at 0xc00f9a20 bios32: Entry = 0xf04e0 (c00f04e0) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0x510 pnpbios: Found PnP BIOS data at 0xc00fcf10 pnpbios: Entry = f0000:cf40 Rev = 1.0 pnpbios: OEM ID cd041 Other BIOS signatures found: ACPI: 00000000 -Preloaded elf kernel "kernel" at 0xc0326000. +Preloaded elf kernel "kernel" at 0xc033a000. +Preloaded elf module "linux.ko" at 0xc033a09c. module_register_init: MOD_LOAD (vesa, c0240a78, 0) error 6 md0: Malloc disk Creating DISK md0 pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71008086) npx0: on motherboard npx0: INT 16 interface -i586_bzero() bandwidth = 43677658 bytes/sec -bzero() bandwidth = 46259888 bytes/sec +i586_bzero() bandwidth = 43664308 bytes/sec +bzero() bandwidth = 46249190 bytes/sec pci_open(1): mode 1 addr port (0x0cf8) is 0x00000000 pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71008086) pcib0: on motherboard found-> vendor=0x8086, dev=0x7100, revid=0x01 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7110, revid=0x01 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[20]: type 1, range 32, base 0000e000, size 4 found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=255 map[20]: type 1, range 32, base 0000d800, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x01 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[90]: type 1, range 32, base 0000e800, size 4 found-> vendor=0x5333, dev=0x88c1, revid=0x00 class=00-01-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 found-> vendor=0x1000, dev=0x0004, revid=0x04 class=01-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[10]: type 1, range 32, base 0000d400, size 8 map[14]: type 1, range 32, base e6800000, size 8 pci0: on pcib0 isab0: at device 1.0 on pci0 isa0: on isab0 atapci0: port 0xe000-0xe00f at device 1.1 on pci0 ata0: iobase=0x01f0 altiobase=0x03f6 bmaddr=0xe000 ata0: mask=03 status0=50 status1=00 ata0: mask=03 status0=50 status1=00 ata0: devices = 0x9 ata0: at 0x1f0 irq 14 on atapci0 ata1: iobase=0x0170 altiobase=0x0376 bmaddr=0xe008 ata1: mask=03 status0=50 status1=00 ata1: mask=03 status0=50 status1=00 ata1: devices = 0x1 ata1: at 0x170 irq 15 on atapci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 1.2 intpm0: port 0xe800-0xe80f irq 9 at device 1.3 on pci0 intpm0: I/O mapped e800 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped e400 pci0: S3 864 graphics accelerator (vendor=0x5333, dev=0x88c1) at 11.0 ncr0: port 0xd400-0xd4ff mem 0xe6800000-0xe68000ff irq 11 at device 12.0 on pci0 ncr0: minsync=25, maxsync=206, maxoffs=8, 16 dwords burst, normal dma fifo ncr0: single-ended, open drain IRQ driver ncr0: driver is using old-style compatability shims Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 fd1: <1200-KB 5.25" drive> on fdc0 drive 1 WARNING: "fd" is usurping "fd"'s cdevsw[] WARNING: "fd" is usurping "fd"'s bmaj atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0067 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d0000 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <12 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: irq maps: 0x41 0x49 0x41 0x41 sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: parallel port found at 0x378 ppc0: ECP SPP ECP+EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/9 bytes threshold ppbus0: IEEE1284 device found /NIBBLE/NIBBLE_ID/Extensibility Link Probing for PnP devices on ppbus0: ppbus0: PRINTER ESCPL2,BDC lpt0: on ppbus0 lpt0: Interrupt-driven port ed0 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 ed0: address 00:80:ad:b0:8e:e4, type NE2000 (16 bit) bpf: ed0 attached sbc0: at port 0x220-0x22f irq 5 drq 1 on isa0 pcm0: on sbc0 -pcm: setmap 20000, ff00; 0xc69f0000 -> 20000 -pcm: setmap 30000, ff00; 0xc6a00000 -> 30000 +pcm: setmap 20000, ff00; 0xc69e7000 -> 20000 +pcm: setmap 30000, ff00; 0xc69f7000 -> 30000 pca0 at port 0x40 on isa0 joy0 at port 0x201 on isa0 isa_probe_children: probing PnP devices BIOS Geometries: 0:03fe1f3f 0..1022=1023 cylinders, 0..31=32 heads, 1..63=63 sectors 1:03fe1f3f 0..1022=1023 cylinders, 0..31=32 heads, 1..63=63 sectors 2:020efe3f 0..526=527 cylinders, 0..254=255 heads, 1..63=63 sectors 0 accounted for Device configuration finished. -IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 40 packets/entry by default bpf: lo0 attached -ata0-master: success setting up WDMA2 mode on PIIX4 chip -ad0: ATA-0 disk at ata0 as master -ad0: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S -ad0: 16 secs/int, 1 depth queue, WDMA2 -ad0: piomode=4 dmamode=2 udmamode=-1 cblid=0 -Creating DISK ad0 -Creating DISK wd0 -ata1-master: success setting up UDMA2 mode on PIIX4 chip -ad1: ATA-4 disk at ata1 as master -ad1: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S -ad1: 16 secs/int, 32 depth queue, UDMA33 -ad1: piomode=4 dmamode=2 udmamode=2 cblid=0 -Creating DISK ad1 -Creating DISK wd1 -ata0-slave: piomode=3 dmamode=-1 udmamode=-1 dmaflag=0 -ata0-slave: success setting up PIO3 mode on generic chip -acd0: CDROM drive at ata0 as slave -acd0: read 689KB/s (689KB/s), 128KB buffer, PIO3 -acd0: Reads: -acd0: Audio: play, 255 volume levels -acd0: Mechanism: ejectable tray -acd0: Medium: no/blank disc inside, unlocked +IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging limited to 40 packets/entry by default +Linux-ELF exec handler installed +ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY +ata0-slave: ata_command: timeout waiting for intr +ata0-slave: identify failed Waiting 2 seconds for SCSI devices to settle ncr0: restart (scsi reset). Creating DISK da0 pass0 at ncr0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number F3TT5812 pass0: 10.000MB/s transfers (10.000MHz, offset 8) Mounting root from ufs:/dev/da0s1a da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number F3TT5812 da0: 10.000MB/s transfers (10.000MHz, offset 8) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da0s1: type 0xa5, start 63, end = 4176899, size 4176837 : OK da0s2: type 0xa5, start 4176900, end = 5397839, size 1220940 : OK da0s3: type 0xa5, start 5397840, end = 6201089, size 803250 : OK start_init: trying /sbin/init -ad1s1: type 0xa5, start 63, end = 8388575, size 8388513 : OK -ad1s2: type 0xa9, start 8391600, end = 9621359, size 1229760 : OK -ad1s3: type 0xa5, start 9621360, end = 10644479, size 1023120 : OK -ad0s1: type 0xa5, start 4032, end = 2874815, size 2870784 : OK -ad0s2: type 0x6, start 3298176, end = 4127759, size 829584 : OK -ad0s3: type 0x7, start 2874879, end = 3298175, size 423297 : OK -ad0s2: rejecting partition in BSD label: it isn't entirely within the slice -ad0s2: start 8391600, end 9621359, size 1229760 -ad0s2d: start 0, end 19807199, size 19807200 -ad0s1: type 0xa5, start 4032, end = 2874815, size 2870784 : OK -ad0s2: type 0x6, start 3298176, end = 4127759, size 829584 : OK -ad0s3: type 0x7, start 2874879, end = 3298175, size 423297 : OK -ad0s1: type 0xa5, start 4032, end = 2874815, size 2870784 : OK -ad0s2: type 0x6, start 3298176, end = 4127759, size 829584 : OK -ad0s3: type 0x7, start 2874879, end = 3298175, size 423297 : OK -ad0s1: type 0xa5, start 4032, end = 2874815, size 2870784 : OK -ad0s2: type 0x6, start 3298176, end = 4127759, size 829584 : OK -ad0s3: type 0x7, start 2874879, end = 3298175, size 423297 : OK -ad1s1: type 0xa5, start 63, end = 8388575, size 8388513 : OK -ad1s2: type 0xa9, start 8391600, end = 9621359, size 1229760 : OK -ad1s3: type 0xa5, start 9621360, end = 10644479, size 1023120 : OK -ad1s2: rejecting partition in BSD label: it isn't entirely within the slice -ad1s2: start 8391600, end 9621359, size 1229760 -ad1s2d: start 0, end 19807199, size 19807200 -ipfw: 3800 Deny UDP 172.20.43.72:513 172.20.63.255:513 in via ed0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 11: 3:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from post.mail.nl.demon.net (post-10.mail.nl.demon.net [194.159.73.20]) by hub.freebsd.org (Postfix) with ESMTP id DE1BE37B799 for ; Sat, 19 Feb 2000 11:03:50 -0800 (PST) (envelope-from marc@oldserver.demon.nl) Received: from [212.238.105.241] (helo=propro) by post.mail.nl.demon.net with esmtp (Exim 2.02 #1) id 12MF6F-0006tS-00 for current@freebsd.org; Sat, 19 Feb 2000 18:59:27 +0000 Date: Sat, 19 Feb 2000 19:59:24 +0100 (CET) From: Marc Schneiders To: current@freebsd.org Subject: release suggestion Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG After installing and rebooting a machine takes a long time to get past sendmail. Adding the hostname to /etc/hosts solves this, as we all know. Is it not possible to let sysinstall do this? Or am I missing something somewhere? -- Marc Schneiders marc@venster.nl http://zelf.net marc@oldserver.demon.nl propro 7:50pm up 11 days, 22:01, load average: 2.03 2.01 2.00 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 11:19:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id EA78737BD32; Sat, 19 Feb 2000 11:19:12 -0800 (PST) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.9.3/8.9.3) id LAA00618; Sat, 19 Feb 2000 11:45:47 -0800 (PST) Date: Sat, 19 Feb 2000 11:45:47 -0800 From: Alfred Perlstein To: current@FreeBSD.ORG Cc: jkh@FreeBSD.ORG Subject: Re: "Fixing" init. Message-ID: <20000219114547.T21720@fw.wintelcom.net> References: <20000219022149.N21720@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20000219022149.N21720@fw.wintelcom.net>; from bright@wintelcom.net on Sat, Feb 19, 2000 at 02:21:49AM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Alfred Perlstein [000219 02:22] wrote: > I remeber being a newbie and getting burned by the need to explicitly > turn a line 'off' in my /etc/ttys file instead of simply deleting it. > > This fixes it using a trivial mark then collect sweep. > > Can a couple people take a look? I'd like to get it into 4.0 because > it seems to follow POLA better. > > "hey i deleted and HUP'd but init keeps spawing them!" ok, NetBSD has had this fixed for _several years_, and they use bitmasks in the se_flags field, here's an updated patch that's essentially the same as the old one but using NetBSD's se_flags implementation. 4.0 please? :) thanks, -Alfred Index: init.c =================================================================== RCS file: /home/ncvs/src/sbin/init/init.c,v retrieving revision 1.37 diff -u -r1.37 init.c --- init.c 1999/11/22 04:23:09 1.37 +++ init.c 2000/02/19 23:26:32 @@ -147,6 +147,7 @@ time_t se_started; /* used to avoid thrashing */ int se_flags; /* status of session */ #define SE_SHUTDOWN 0x1 /* session won't be restarted */ +#define SE_PRESENT 0x2 /* session is in /etc/ttys */ int se_nspace; /* spacing count */ char *se_device; /* filename of port */ char *se_getty; /* what to run on that port */ @@ -964,6 +965,7 @@ /* * Allocate a new session descriptor. + * Mark it SE_PRESENT. */ session_t * new_session(sprev, session_index, typ) @@ -982,6 +984,7 @@ sp = (session_t *) calloc(1, sizeof (session_t)); sp->se_index = session_index; + sp->se_flags |= SE_PRESENT; sp->se_device = malloc(sizeof(_PATH_DEV) + strlen(typ->ty_name)); (void) sprintf(sp->se_device, "%s%s", _PATH_DEV, typ->ty_name); @@ -1330,7 +1333,7 @@ } /* - * This is an n-squared algorithm. We hope it isn't run often... + * This is an (n*2)+(n^2) algorithm. We hope it isn't run often... */ state_func_t clean_ttys() @@ -1344,6 +1347,14 @@ if (! sessions) return (state_func_t) multi_user; + /* + * mark all sessions for death, (!SE_PRESENT) + * as we find or create new ones they'll be marked as keepers, + * we'll later nuke all the ones not found in /etc/ttys + */ + for (sp = sessions; sp != NULL; sp = sp->se_next) + sp->se_flags &= ~SE_PRESENT; + devlen = sizeof(_PATH_DEV) - 1; while ((typ = getttyent()) != NULL) { ++session_index; @@ -1353,6 +1364,8 @@ break; if (sp) { + /* we want this one to live */ + sp->se_flags |= SE_PRESENT; if (sp->se_index != session_index) { warning("port %s changed utmp index from %d to %d", sp->se_device, sp->se_index, @@ -1402,6 +1415,17 @@ } endttyent(); + + /* + * sweep through and kill all deleted sessions + * ones who's /etc/ttys line was deleted (SE_PRESENT unset) + */ + for (sp = sessions; sp != NULL; sp = sp->se_next) { + if ((sp->se_flags & SE_PRESENT) == 0) { + sp->se_flags |= SE_SHUTDOWN; + kill(sp->se_process, SIGHUP); + } + } return (state_func_t) multi_user; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 11:25:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id 9B59237BC18 for ; Sat, 19 Feb 2000 11:25:01 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from gravy.kishka.net (dyn-7.blackbox-2.netaxs.com [207.106.60.7]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id OAA20378; Sat, 19 Feb 2000 14:20:36 -0500 (EST) Received: from localhost (gravy.kishka.net [127.0.0.1]) by gravy.kishka.net (8.9.3/8.9.3) with ESMTP id OAA00201; Sat, 19 Feb 2000 14:20:34 -0500 (EST) (envelope-from bleez@netaxs.com) Date: Sat, 19 Feb 2000 14:20:34 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: Philipp Mergenthaler Cc: Bryan Liesner , Soren Schmidt , current@FreeBSD.ORG Subject: Re: Big ATA problems In-Reply-To: <20000219194049.A7428@rz.uni-karlsruhe.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Philipp Mergenthaler wrote: >On Sat, Feb 19, 2000 at 10:39:42AM -0500, Bryan Liesner wrote: >> Jose, the problem seems to be resolved by rebuilding the boot >> loader. Or bypass the loader altogether. >> >> cd /usr/src/sys/boot >> make obj >> make all install >> >> and you'll be able to boot the kernel with the latest ata stuff. > >Do you use KLMs? Yes, I do! I was loading a screen saver with the boot loader. And now I see I am wrong about rebuilding the loader! When I had success loading the kernel directly, I moved loading the screensaver into rc.conf instead. Then I thought that something may be wrong with the loader, rebuilt it, and booted successfully. I broke the rule - never change more than one thing at a time :) I put the screen saver back in loader.conf and the boot failed again, so it is a loader/kernel issue, but I didn't have to rebuild loader. -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 11:38:31 2000 Delivered-To: freebsd-current@freebsd.org Received: from isbalham.ist.co.uk (isbalham.ist.co.uk [192.31.26.1]) by hub.freebsd.org (Postfix) with ESMTP id B199837BBA0 for ; Sat, 19 Feb 2000 11:38:20 -0800 (PST) (envelope-from rb@gid.co.uk) Received: (from uucp@localhost) by isbalham.ist.co.uk (8.9.2/8.8.7) with UUCP id TAA01969 for current@freebsd.org; Sat, 19 Feb 2000 19:35:55 GMT (envelope-from rb@gid.co.uk) Received: from [194.32.164.2] (eccles [194.32.164.2]) by seagoon.gid.co.uk (8.9.3/8.9.3) with ESMTP id TAA15108 for ; Sat, 19 Feb 2000 19:28:21 GMT (envelope-from rb@gid.co.uk) X-Sender: rb@194.32.164.1 Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Date: Sat, 19 Feb 2000 19:28:23 +0000 To: current@freebsd.org From: Bob Bishop Subject: cdrecord problem with current current Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, cdrecord, freshly built on last night's -current: atlas# cdrecord -v dev=3D1,6,0 -inq Cdrecord release 1.8a21 Copyright (C) 1995-1999 J=96rg Schilling TOC Type: 1 =3D CD-ROM scsidev: '1,6,0' scsibus: 1 target: 6 lun: 0 atapi: 0 cdrecord: Warning: controller returns zero sized CD capabilities page. cdrecord: Warning: controller returns wrong size for CD capabilities page. cdrecord: Warning: controller returns wrong page 0 for CD capabilities page (2A) =2E Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : SYNC Vendor_info : 'YAMAHA ' Identifikation : 'CRW4416S ' Revision : '1.0f' Device seems to be: Generic CD-ROM. atlas# =2E..so cdrecord can't tell what the device is. Am I in trouble because the CDR isn't on the first SCSI controller, or has something got broken? Dmesg follows: =46reeBSD 4.0-CURRENT #28: Sat Feb 19 15:56:28 GMT 2000 rb@atlas:/source/cleansrc/sys/compile/ATLAS Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6tm w/ multimedia extensions (233.86-MHz 586-class CPU) Origin =3D "AuthenticAMD" Id =3D 0x562 Stepping =3D 2 Features=3D0x8001bf AMD Features=3D0x400<> real memory =3D 33554432 (32768K bytes) avail memory =3D 28872704 (28196K bytes) Preloaded elf kernel "kernel" at 0xc03b1000. md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=3D0x8086, dev=3D0x7112= ) at 7.2 irq 10 chip1: port 0x5f00-0x5f0f at dev= ice 7.3 on pci0 ed0: port 0x6500-0x651f irq 9 at device 10.0 on p ci0 ed0: address 00:20:18:80:b4:6d, type NE2000 (16 bit) adw0: port 0x6600-0x66ff mem 0xe0000000-0 xe00000ff irq 10 at device 12.0 on pci0 adw0: SCSI ID 7, High & Low SE Term Enabled, LVD Term Enabled, Queue Depth 2= 53 devclass_alloc_unit: ata0 already exists, using next available unit number devclass_alloc_unit: ata1 already exists, using next available unit number devclass_alloc_unit: ed0 already exists, using next available unit number fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 aha0 at port 0x330-0x333 irq 11 drq 5 on isa0 aha0: AHA-1542CF FW Rev. C.0 (ID=3D45) SCSI Host Adapter, SCSI ID 7, 16 CCBs atkbdc0: at port 0x60-0x6f on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=3D0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0a cd0 at aha0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: cd present [1 x 2048 byte records] da0 at adw0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at adw0 bus 0 target 1 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) -- Bob Bishop (0118) 977 4017 international code +44 118 rb@gid.co.uk fax (0118) 989 4254 between 0800 and 1800 UK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 12:14:23 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 76EA737BC1A; Sat, 19 Feb 2000 12:14:18 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p10-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.11]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA15583; Sun, 20 Feb 2000 05:12:45 +0900 (JST) Message-ID: <38AEF905.A3512928@newsguy.com> Date: Sun, 20 Feb 2000 05:11:49 +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: "Brian J. McGovern" Cc: Doug Barton , "Jordan K. Hubbard" , freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 References: <200002181512.KAA01992@spoon.beta.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Brian J. McGovern" wrote: > > I don't know if I agree. "Custom" is exactly what it says... You can build > out the system with specifically the components you want. Now, perhaps I'm out That proves "Custom" is not exactly what it says. You can do the same thing with Novice. ALL installation modes give you the same granularity of components. The difference is: Novice -- automatically steps through all phases of installation, with explanations at each step Expert -- automatically steps through all phases of installation Custom -- requires the user to select by hand the installation phases All the Custom installation really gives you is: * The ability to avoid phases you won't be needing * The ability to shoot yourself in the foot The last one can be useful in some rather rare cases. > Now, I'll admit, that custom may be a bit daunting to people who are new to > Operating Systems. But, even in the Windows enviornment, > "Custom Installations" are usually documented as a route for those who are > clue as to what they're doing, and "Standard" or "Quick" installs are for > the others. Exactly. That's not how FreeBSD installation options are set up. Which is the whole point. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 12:15:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 84D1737BBF4 for ; Sat, 19 Feb 2000 12:15:29 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (dcs@p10-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.11]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA15800; Sun, 20 Feb 2000 05:15:23 +0900 (JST) Message-ID: <38AEF9A3.925861DE@newsguy.com> Date: Sun, 20 Feb 2000 05:14:27 +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: Anatoly Vorobey Cc: freebsd-current@freebsd.org Subject: Re: feedback on CD install of 4.0-RC2 References: <7327.950809955@zippy.cdrom.com> <38ACD908.E756C802@gorean.org> <38AD571D.C5B53079@newsguy.com> <20000218183421.A2896@happy.checkpoint.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anatoly Vorobey wrote: > > On Fri, Feb 18, 2000 at 11:28:45PM +0900, Daniel C. Sobral wrote: > > > > Novice is ok, it's the other two that are problematic. Well, > > particularly "custom". "Custom" does not scare away anyone, and is > > actually actractive to Windows users. It should be called "death trap" > > or something like that... > > I'm actually scared by "novice" because it would be inflicting on me > defaults I would almost probably not want. I never run anything but > "custom", and I suspect many people do the same. That's why "custom" is the problem. It gives people the impression that "Novice" has defaults that "Custom" doesn't. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 12:47: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id 219EB37BCA8 for ; Sat, 19 Feb 2000 12:46:55 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id UAA88262; Sat, 19 Feb 2000 20:58:25 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002191958.UAA88262@freebsd.dk> Subject: Re: Big ATA problems In-Reply-To: from Bryan Liesner at "Feb 19, 2000 02:20:34 pm" To: bleez@netaxs.com (Bryan Liesner) Date: Sat, 19 Feb 2000 20:58:25 +0100 (CET) Cc: un1i@rz.uni-karlsruhe.de (Philipp Mergenthaler), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bryan Liesner wrote: > >Do you use KLMs? > > Yes, I do! I was loading a screen saver with the boot loader. And > now I see I am wrong about rebuilding the loader! When I had success > loading the kernel directly, I moved loading the screensaver into > rc.conf instead. Then I thought that something may be wrong with the > loader, rebuilt it, and booted successfully. > > I broke the rule - never change more than one thing at a time :) > > I put the screen saver back in loader.conf and the boot failed again, > so it is a loader/kernel issue, but I didn't have to rebuild loader. Have you rebuild your modules lately ?? -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 13: 2:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id 9C3AA37BC50 for ; Sat, 19 Feb 2000 13:02:47 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from gravy.kishka.net (dyn-13.blackbox-2.netaxs.com [207.106.60.13]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id QAA01557; Sat, 19 Feb 2000 16:02:43 -0500 (EST) Received: from localhost (gravy.kishka.net [127.0.0.1]) by gravy.kishka.net (8.9.3/8.9.3) with ESMTP id QAA00188; Sat, 19 Feb 2000 16:02:41 -0500 (EST) (envelope-from bleez@netaxs.com) Date: Sat, 19 Feb 2000 16:02:41 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: Soren Schmidt Cc: Bryan Liesner , Philipp Mergenthaler , current@FreeBSD.ORG Subject: Re: Big ATA problems In-Reply-To: <200002191958.UAA88262@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Soren Schmidt wrote: >Have you rebuild your modules lately ?? > >-S=F8ren > Yes. My world is current as of a few hours ago. I did a make world=20 right after finding out about the loader problem to rule that possibility out. The disk probes still fail when loading today's=20 modules with the loader. -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 13:25:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id D27F337BCE0 for ; Sat, 19 Feb 2000 13:25:55 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id NAA51808; Sat, 19 Feb 2000 13:25:52 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38AF0A60.6667A2CD@gorean.org> Date: Sat, 19 Feb 2000 13:25:52 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Alfred Perlstein Cc: current@freebsd.org Subject: Re: "Fixing" init. References: <20000219022149.N21720@fw.wintelcom.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Alfred Perlstein wrote: > > I remeber being a newbie and getting burned by the need to explicitly > turn a line 'off' in my /etc/ttys file instead of simply deleting it. Here here. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 13:26:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A299A37BCDE; Sat, 19 Feb 2000 13:26:10 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA76855; Sat, 19 Feb 2000 13:26:05 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 13:26:05 -0800 (PST) From: Kris Kennaway To: Robert Watson Cc: current@freebsd.org Subject: Re: Supported ways to do RSA/OpenSSL on 4.0? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Robert Watson wrote: > /usr/ports/security/openssh/work/ssh/lib/../rsa.h:22: openssl/rsa.h: No > such fil > e or directory Yes, this is the same problem Jordan is seeing. I really don't know why, because it SHOULD be failing gracefully when it sees you don't have an openssl-capable libcrypto :-( I'll keep looking at it. > > See chapter 6.5 in the handbook. > > The handbook appears not to have been installed as part of the ``Novice'' > install that I selected. This suggests that the documentation is not > sufficiently accessible. Hmm, you'd have to check with Jordan about that..I haven't done an installation for a long time. > However, I did find the following: > > The OpenSSL package with RSAREF support for USA users which you can get > from ftp.FreeBSD.org. > > Note: Be sure to read the license before installing! This is NOT > licensed for general-purpose use! > > The OpenSSL package for International (non-USA) users. This is not legal > for general use in the USA, but international users should use this > version because the RSA implementation is faster and more flexible. It > is available from ftp.internat.FreeBSD.org. > > I was unable to build the OpenSSL port, and installing the RSAref port > didn't fix these build problems. Also, these directions are pretty No, because you have to install the OpenSSL-RSAREF port as well. The libraries are different when built against librsaref. Grab that port and it will pull in a rsaref dependency. > non-specific--could you throw in URLs? Also, as I mentioned for Yes, once they're actually on the FTP site ;-) Hopefully this weekend. > auto-install, either building this into sysinstall as a specific install > stage would be a good idea. Is the intent that we install the OpenSSL > package into /usr/local/lib, or will this stuff be dumped in /usr/lib? It overwrites the system copy in /usr/lib. Having a stale copy in /usr/local/lib shouldn't hurt things (Jim and I have been trying to make sure the openssl ports will not pick anything up from there if you have it in /usr/lib) but other (e.g. new) ports we haven't touched might not like it off the bat. There's a whole maze of twisty little passages involved in getting all of the n different possible combinations of openssl, openssl crypto options and FreeBSD working properly. > Having two different instances of OpenSSL with different degrees of > breakage will be pretty confusing for developers and porters of SSL > applications, suggesting that the logical target is /usr/lib. It also > might be good to have a /usr/include/openssl/README that says ``Looking > for rsa.h? You need to read section 6.5 of the handbook''. This might be a good idea. > Also, I note that we don't include an OpenSSL man page: > > cumin# man openssl > No manual entry for openssl > cumin# man ssl > No manual entry for ssl > cumin# man crypto > No manual entry for crypto > > These logical sounding potential manpages would probably be a good place > to mirror the handbook information. Are there OpenSSL man pages installed > somewhere in the base system? No, openssl 0.9.4 had no manpages. Openssl 0.9.5 rectifies this. If one of the docs guys wants to manify the handbook contents it's fine by me. > Is this an export-friendly location for non-USA folks? Any chance Jordan Nope, but John Hay has reportedly built international packages which Mark is reportedly going to be putting on internat.freebsd.org. > or someone wants to hack up an install stage? I think this is > important--especially having it automated, as the automated one-step > install of crypto-based applications is important. If we're willing to > pause the install to ask about X desktops, this sounds like a good > candidate also. It also sounds like a good time to generate an initial > value for USA_RESIDENT in make.conf. I agree. Jordan? :) > Sounds like a step in the right direction, but currently a no-start due to > lack of handbook in the install. Although it's more work, I'd rather see > an OpenSSL manpage that includes this information, a sure-fire way to > check to see what's installed, a sysinstall-phase, etc. I'll update the warning to give an actual pointer (file location and URL). > Thanks! Looks like all this will be great once it's working! Thanks. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 13:39: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8FDAC37BCC9; Sat, 19 Feb 2000 13:39:02 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA77454; Sat, 19 Feb 2000 13:39:02 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 13:39:01 -0800 (PST) From: Kris Kennaway To: Victor Salaman Cc: freebsd-current@freebsd.org Subject: Re: openssl in -current In-Reply-To: <200002191513.HAA01528@www.geocrawler.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Victor Salaman wrote: > I personally think that it's braindead to add openssl to the system > and stripout parts of it (RSA & IDEA). Don't get me wrong, I love to > have So do I. Unfortunately our hands are tied - the version of FreeBSD distributed in the US must not contain these because they are patented technologies and not available for unrestricted use. Unfortunately this is also the same version distributed worldwide on FreeBSD CDs, install images, etc (although internat.freebsd.org also produces crypto snapshots which would have the international version of openssl). See chapter 6.5 in the handbook for an explanation of the problem and the solutions - if you're inside the US and comply with the rsaref license you can use the OpenSSL-rsaref package, otherwise you're legally forbidden from using RSA. There's no known workaround for IDEA, but thankfully not many ports make use of it anyway. > Imagine that you are setting up 100 FreeBSD machines, it's not an > option to do make world from sources and build a "new" non-crippled > crypto system. You just want to install it and go! Hopefully at some point in the future sysinstall will have an option at install-time for pulling in the "correct" version of openssl for your situation. At present you can still just pkg_add the relevant package post-install without having to do a make world. See http://www.freebsd.org/~kris/openssl Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 13:50:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebsd.dk (freebsd.dk [212.242.42.178]) by hub.freebsd.org (Postfix) with ESMTP id C5FE537BCAA for ; Sat, 19 Feb 2000 13:50:30 -0800 (PST) (envelope-from sos@freebsd.dk) Received: (from sos@localhost) by freebsd.dk (8.9.3/8.9.1) id WAA88565; Sat, 19 Feb 2000 22:50:15 +0100 (CET) (envelope-from sos) From: Soren Schmidt Message-Id: <200002192150.WAA88565@freebsd.dk> Subject: Re: Big ATA problems In-Reply-To: from Bryan Liesner at "Feb 19, 2000 04:02:41 pm" To: bleez@netaxs.com (Bryan Liesner) Date: Sat, 19 Feb 2000 22:50:15 +0100 (CET) Cc: un1i@rz.uni-karlsruhe.de (Philipp Mergenthaler), current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG It seems Bryan Liesner wrote: > On Sat, 19 Feb 2000, Soren Schmidt wrote: > > >Have you rebuild your modules lately ?? > > > >-Søren > > > Yes. My world is current as of a few hours ago. I did a make world > right after finding out about the loader problem to rule that > possibility out. The disk probes still fail when loading today's > modules with the loader. Wierd, I'll try to investigate that here... -Søren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 13:51:14 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 2DA0237BE02; Sat, 19 Feb 2000 13:51:11 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA41161; Sat, 19 Feb 2000 13:51:05 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 13:39:01 PST." Date: Sat, 19 Feb 2000 13:51:05 -0800 Message-ID: <41158.950997065@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > So do I. Unfortunately our hands are tied - the version of FreeBSD > distributed in the US must not contain these because they are patented > technologies and not available for unrestricted use. Unfortunately this is > also the same version distributed worldwide on FreeBSD CDs, install At this stage, I'm ready to have two different CD products for international and domestic use. I can also ensure that the appropriate ISO images are made available from the US and internat.freebsd.org, along with the distribution bits. What we have now is sort of bordering on nightmarish. Sysinstall also isn't likely to do anything to change this until openssl becomes a "distribution" like the DES bits are. Depending on external packages is actually something I'm trying to wean sysinstall away from because the dependency is a PITA and the creation of the packages collection is not automated in the same way that distribution building is. To put it somewhat more succinctly, I won't be creating any more dependencies on external packages from sysinstall (where "external" is defined as anything not created by "make world"), so any solution which relies on sysinstall sucking in a package should not be entertained. The existing dependencies on things like linux_base and lynx are already enough of a pain as it is and I'd like to eliminate them at some point also. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 13:54: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id A017C37BCE0; Sat, 19 Feb 2000 13:53:58 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id NAA78342; Sat, 19 Feb 2000 13:53:58 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 13:53:51 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: Victor Salaman , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-Reply-To: <41158.950997065@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jordan K. Hubbard wrote: > At this stage, I'm ready to have two different CD products for > international and domestic use. I can also ensure that the > appropriate ISO images are made available from the US and > internat.freebsd.org, along with the distribution bits. What we have > now is sort of bordering on nightmarish. That's excellent news! > Sysinstall also isn't likely to do anything to change this until > openssl becomes a "distribution" like the DES bits are. Depending on > external packages is actually something I'm trying to wean sysinstall > away from because the dependency is a PITA and the creation of the > packages collection is not automated in the same way that distribution > building is. Okay, so what do I need to do to make this happen? Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 13:57:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 86EE737BCF8; Sat, 19 Feb 2000 13:57:36 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p10-dn01kiryunisiki.gunma.ocn.ne.jp [211.0.245.11]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id GAA22480; Sun, 20 Feb 2000 06:57:31 +0900 (JST) Message-ID: <38AF1186.8D04CE12@newsguy.com> Date: Sun, 20 Feb 2000 06:56:22 +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: Kai =?iso-8859-1?Q?Gro=DFjohann?= Cc: freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 References: <79206.950898990@zippy.cdrom.com> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kai Gro=DFjohann wrote: > = > "Jordan K. Hubbard" writes: > = > > I really kinda wish you'd point them to Novice^H^H^H^H^HStandard > > instead since it does more than be a bit more verbose, it also makes > > sure that all the appropriate steps are covered and prevents even > > relatively skilled people from hanging themselves. > = > Does this mean that this option should be called `guided'? I know a > little bit about Unix but haven't installed FreeBSD more than five > times or so. And I always thought that the novice install meant that > I didn't get as many choices... "Guided". I like it. That's *PRECISELY* what this installation option is. There is NO difference in the number of choices available in any of the three types. Guided/Express/Expert. That's my vote. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 14: 2:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from ducky.nz.freebsd.org (chilled.unixathome.org [203.79.82.27]) by hub.freebsd.org (Postfix) with ESMTP id 4A7D037BCBF; Sat, 19 Feb 2000 14:02:39 -0800 (PST) (envelope-from dan@freebsddiary.org) Received: from wocker (wocker.int.nz.freebsd.org [192.168.0.99]) by ducky.nz.freebsd.org (8.9.3/8.9.3) with ESMTP id LAA51122; Sun, 20 Feb 2000 11:02:10 +1300 (NZDT) Message-Id: <200002192202.LAA51122@ducky.nz.freebsd.org> From: "Dan Langille" Organization: The FreeBSD Diary To: "Daniel C. Sobral" Date: Sun, 20 Feb 2000 11:02:10 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: feedback on CD install of 4.0-RC2 Reply-To: dan@freebsddiary.org Cc: freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG In-reply-to: <38AF1186.8D04CE12@newsguy.com> X-mailer: Pegasus Mail for Win32 (v3.12b) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 Feb 00, at 6:56, Daniel C. Sobral wrote: > "Guided". I like it. That's *PRECISELY* what this installation option > is. There is NO difference in the number of choices available in any of > the three types. I have many times encountered a user who avoided the NOVICE install and tried one of the other methods. They clearly lacked the skill necessary to perform anything *other* than a NOVICE install. I suspect they avoided the NOVICE install because they didn't consider themselves a novice ("But I've been using Linux for years!"). I think calling it GUIDED will certainly reduce the number of calls for help. -- Dan Langille - DVL Software Limited [I'm looking for more work] The FreeBSD Diary - http://www.freebsddiary.org/ NZ FreeBSD User Group - http://www.nzfug.nz.freebsd.org/ The Racing System - http://www.racingsystem.com/ unix @ home - http://www.unixathome.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 14: 6: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail4.aracnet.com (mail4.aracnet.com [216.99.193.36]) by hub.freebsd.org (Postfix) with ESMTP id 257D137BCBF; Sat, 19 Feb 2000 14:05:57 -0800 (PST) (envelope-from beattie@aracnet.com) Received: from shell1.aracnet.com (IDENT:root@shell1.aracnet.com [216.99.193.21]) by mail4.aracnet.com (8.9.3/8.9.3) with ESMTP id OAA16019; Sat, 19 Feb 2000 14:06:14 -0800 Received: from localhost by shell1.aracnet.com (8.9.3) id OAA09945; Sat, 19 Feb 2000 14:06:26 -0800 X-Authentication-Warning: shell1.aracnet.com: beattie owned process doing -bs Date: Sat, 19 Feb 2000 14:06:26 -0800 (PST) From: Brian Beattie To: "Daniel C. Sobral" Cc: Kai =?iso-8859-1?Q?Gro=DFjohann?= , freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 In-Reply-To: <38AF1186.8D04CE12@newsguy.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, Daniel C. Sobral wrote: > Kai Gro=DFjohann wrote: > >=20 > > "Jordan K. Hubbard" writes: > >=20 > > > I really kinda wish you'd point them to Novice^H^H^H^H^HStandard > > > instead since it does more than be a bit more verbose, it also makes > > > sure that all the appropriate steps are covered and prevents even > > > relatively skilled people from hanging themselves. > >=20 > > Does this mean that this option should be called `guided'? I know a > > little bit about Unix but haven't installed FreeBSD more than five > > times or so. And I always thought that the novice install meant that > > I didn't get as many choices... >=20 > "Guided". I like it. That's *PRECISELY* what this installation option > is. There is NO difference in the number of choices available in any of > the three types. >=20 > Guided/Express/Expert. That's my vote. This still implies that Expert nee Custom is superior to Guided nee Novice, in ways that it is not. As far as I can tell the only thing Expert provides is the ability to skip steps and to do steps in the wrong order so that the install will fail. Standard/Express/Exceptional. Would be my vote, if I had a vote which I'm sure I don't. Brian Beattie | The only problem with beattie@aracnet.com | winning the rat race ... www.aracnet.com/~beattie | in the end you're still a rat To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 14:25:33 2000 Delivered-To: freebsd-current@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 3C6B237BC1A; Sat, 19 Feb 2000 14:25:30 -0800 (PST) (envelope-from jlemon@flugsvamp.com) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.9.3/8.9.3) id QAA92457; Sat, 19 Feb 2000 16:26:00 -0600 (CST) (envelope-from jlemon) Date: Sat, 19 Feb 2000 16:26:00 -0600 (CST) From: Jonathan Lemon Message-Id: <200002192226.QAA92457@prism.flugsvamp.com> To: dcs@newsguy.com, freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 X-Newsgroups: local.mail.freebsd-current In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article you write: >Kai Großjohann wrote: >> >> "Jordan K. Hubbard" writes: >> >> > I really kinda wish you'd point them to Novice^H^H^H^H^HStandard >> > instead since it does more than be a bit more verbose, it also makes >> > sure that all the appropriate steps are covered and prevents even >> > relatively skilled people from hanging themselves. >> >> Does this mean that this option should be called `guided'? I know a >> little bit about Unix but haven't installed FreeBSD more than five >> times or so. And I always thought that the novice install meant that >> I didn't get as many choices... > >"Guided". I like it. That's *PRECISELY* what this installation option >is. There is NO difference in the number of choices available in any of >the three types. > >Guided/Express/Expert. That's my vote. Cool, seconded. I actually use "novice" most of the time, simply because I like the hints that help me not to screw up, and I've been using this option (or equivalent) since 1.1.5 at least. Guided sounds like a better description to me. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 14:37:17 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id CC08337BD26; Sat, 19 Feb 2000 14:37:14 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA41347; Sat, 19 Feb 2000 14:37:08 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 13:53:51 PST." Date: Sat, 19 Feb 2000 14:37:08 -0800 Message-ID: <41344.950999828@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > openssl becomes a "distribution" like the DES bits are. Depending on > > external packages is actually something I'm trying to wean sysinstall > > away from because the dependency is a PITA and the creation of the > > packages collection is not automated in the same way that distribution > > building is. > > Okay, so what do I need to do to make this happen? 1. Make openssl build as part of the standard "world" and depend on the setting of USA_RESIDENT, which will be initially set by sysinstall. 2. Let me look at where things are installed in each case (if there's any difference at all) and figure out how to hack release/Makefile to package up the extra bits. 3. I add another "crypto" flag for this chunk of stuff in the now-not-very-well-named des/ distribution directory and add sysinstall menu entries for it appropriately. Of course, this all begs the question as to whether or not the current DES/openssl division is even meaningful now. The DES code we have in the tree is rapidly falling under the radar of what the US government considers interesting and this whole openssl thing is over a patent, which is in a rather different category. We're sort of trying to skate in-between the lines here and I think we're only confusing ourselves as a result. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 14:53: 8 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E343737BD44; Sat, 19 Feb 2000 14:53:01 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id OAA82720; Sat, 19 Feb 2000 14:53:01 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 14:53:00 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <41344.950999828@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jordan K. Hubbard wrote: > > Okay, so what do I need to do to make this happen? > > 1. Make openssl build as part of the standard "world" and depend > on the setting of USA_RESIDENT, which will be initially set by > sysinstall. It already does this if you get your crypto from internat. US mirror sites only carry the neutered (no-RSA) version, but internat carries RSA and builds it conditional on USA_RESIDENT. > 2. Let me look at where things are installed in each case (if there's > any difference at all) and figure out how to hack release/Makefile > to package up the extra bits. The only differences are: 1) if you build with rsaref (which it's only sensible to do if USA_RESIDENT == YES) you get a librsaglue.* and include/rsaref.h in addition to the "standard" files. 2) if you don't build with any sort of RSA (i.e. USA_RESIDENT == YES and you don't have the rsaref package installed) then you don't get include/rsa.h but get everything else "standard". See the packages at http://www.freebsd.org/~kris/openssl/ for a better definition of "standard". Mark should be putting the international ones on internat sometime (*nudge*). > 3. I add another "crypto" flag for this chunk of stuff in the > now-not-very-well-named des/ distribution directory and add > sysinstall menu entries for it appropriately. > > Of course, this all begs the question as to whether or not the current > DES/openssl division is even meaningful now. The DES code we have in > the tree is rapidly falling under the radar of what the US government > considers interesting and this whole openssl thing is over a patent, > which is in a rather different category. We're sort of trying to > skate in-between the lines here and I think we're only confusing > ourselves as a result. Did you ever hear back from the lawyers about whether (and how) we can freely distribute openssl (and other stuff) from the US? Apart from that it does just reduce to the case of keeping the patent lawyers happy by keeping the patented code away from US people. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 15:16:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 6788137BC50; Sat, 19 Feb 2000 15:16:41 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id PAA41484; Sat, 19 Feb 2000 15:16:35 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 14:53:00 PST." Date: Sat, 19 Feb 2000 15:16:35 -0800 Message-ID: <41481.951002195@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > It already does this if you get your crypto from internat. US mirror sites > only carry the neutered (no-RSA) version, but internat carries RSA and > builds it conditional on USA_RESIDENT. And why don't the USA sites have the RSAREF version? I'm still not sure I understand the compartmentalization here. > 2) if you don't build with any sort of RSA (i.e. USA_RESIDENT == YES and > you don't have the rsaref package installed) then you don't get > include/rsa.h but get everything else "standard". It's this rsaref thing that's hanging me up. Why is it either on or off vs on from location A or on from location B? > See the packages at http://www.freebsd.org/~kris/openssl/ for a better > definition of "standard". Mark should be putting the international ones on > internat sometime (*nudge*). I still don't think that the packages are going to help us much here. > Did you ever hear back from the lawyers about whether (and how) we can > freely distribute openssl (and other stuff) from the US? Apart from that > it does just reduce to the case of keeping the patent lawyers happy by > keeping the patented code away from US people. The lawyers haven't been willing to say anything about this right now, citing too large of a caseload to even begin untangling the Clinton administration's current position. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 15:43:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from po4.wam.umd.edu (po4.wam.umd.edu [128.8.10.166]) by hub.freebsd.org (Postfix) with ESMTP id 42B2537BD08 for ; Sat, 19 Feb 2000 15:43:35 -0800 (PST) (envelope-from culverk@wam.umd.edu) Received: from rac3.wam.umd.edu (root@rac3.wam.umd.edu [128.8.10.143]) by po4.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA07960 for ; Sat, 19 Feb 2000 18:43:38 -0500 (EST) Received: from rac3.wam.umd.edu (sendmail@localhost [127.0.0.1]) by rac3.wam.umd.edu (8.9.3/8.9.3) with SMTP id SAA15058 for ; Sat, 19 Feb 2000 18:43:28 -0500 (EST) Received: from localhost (culverk@localhost) by rac3.wam.umd.edu (8.9.3/8.9.3) with ESMTP id SAA15048 for ; Sat, 19 Feb 2000 18:43:28 -0500 (EST) X-Authentication-Warning: rac3.wam.umd.edu: culverk owned process doing -bs Date: Sat, 19 Feb 2000 18:43:28 -0500 (EST) From: Kenneth Wayne Culver To: freebsd-current@freebsd.org Subject: ATA errors Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I cvsupped this morning and I just had a chance to build a new kernel, and now I get a "cannot mount root" and it drops into some kind of commandline where I can enter a root for it to mount. This is the error it gives me now: ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY ata0-slave: ata_command: timeout waiting for intr ata0-slave: identify failed it goes on to say that ad1 doesn't exist... This didn't happen with a kernel as of yesterday (which is what I'm using now). This is how it probes right now: ata-pci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 ad1: 13029MB [26473/16/63] at ata0-slave using UDMA33 ad2: 6187MB [13410/15/63] at ata1-master using UDMA33 acd0: DVD-ROM at ata1-slave using UDMA33 Any help would be appreciated.. ================================================================= | Kenneth Culver | FreeBSD: The best OS around. | | Unix Systems Administrator | ICQ #: 24767726 | | and student at The | AIM: muythaibxr | | The University of Maryland, | Website: (Under Construction) | | College Park. | http://www.wam.umd.edu/~culverk/| ================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 15:49: 7 2000 Delivered-To: freebsd-current@freebsd.org Received: from devils.maquina.com (devils.maquina.com [62.229.71.43]) by hub.freebsd.org (Postfix) with ESMTP id F0A0637BD4D; Sat, 19 Feb 2000 15:49:00 -0800 (PST) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by devils.maquina.com (8.9.3/8.9.3) with ESMTP id XAA53056; Sat, 19 Feb 2000 23:48:52 GMT (envelope-from gabriel@maquina.com) X-Authentication-Warning: devils.maquina.com: gabriel owned process doing -bs Date: Sat, 19 Feb 2000 23:48:52 +0000 (WET) From: Jose Gabriel Marcelino To: Soren Schmidt Cc: current@FreeBSD.ORG, freebsd-isdn@FreeBSD.ORG, hm@hcs.de Subject: Re: Big ATA problems In-Reply-To: <200002192150.WAA88565@freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, After remaking the loader (unnecessary since it's still broken), I've removed my KLDs from loader.conf (I was loading a splash screen) and it now boots as Bryan noticed. However it seems another problem showed up, and I'm not sure where the problem is. I have a Teles ISDN card on this machine which was working very well before this change using it's factory default IO configuration which places it at 0xd80. It's driver however due to some hardware "features" unknown to me says the following: ata-pci0: port 0xe000-0xe00f at device 7.1 on pci0 ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 ... isic0 at port 0xd80,0x960-0x99f,0x160-0x19f,0x560-0x59f irq 10 flags 0x3 on isa0 isic0: Teles S0/16.3 This obviously conflicts with the secondary IDE controller which lies at 0x170, however this has not been a problem till this day and no driver complained about this. Now, with the newer kernel I get this: atapci0: port 0xe000-0xe00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 ... isic0: Error allocating io at 0x160 for Teles S0/16.3! While I was able to use the Teles again by changing it's default IO port I think there will be some people who will find it cumbersome to have to change the IO on a card that was working fine before. I feel this is a newbus issue with the ATA driver and/or maybe the i4b driver doesn't really need that many IO ports so I'm sending this email to both parties. Thanks again. Regards, Gabriel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 15:53:30 2000 Delivered-To: freebsd-current@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id 1460B37BD08; Sat, 19 Feb 2000 15:53:22 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (lxpx48.lx.ehu.es [158.227.99.48]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id AAA07223; Sun, 20 Feb 2000 00:52:43 +0100 (MET) Message-ID: <38AF2CCB.ABC4BC55@we.lc.ehu.es> Date: Sun, 20 Feb 2000 00:52:43 +0100 From: "Jose M. Alcaide" Organization: Universidad del =?iso-8859-1?Q?Pa=EDs?= Vasco - Dpto. de Electricidad y =?iso-8859-1?Q?Electr=F3nica?= X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-RELEASE i386) X-Accept-Language: es-ES, es, en-US, en MIME-Version: 1.0 To: Brian Beattie Cc: "Daniel C. Sobral" , Kai =?iso-8859-1?Q?Gro=DFjohann?= , freebsd-qa@FreeBSD.ORG, freebsd-current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Beattie wrote: > > On Sun, 20 Feb 2000, Daniel C. Sobral wrote: > > > > "Guided". I like it. That's *PRECISELY* what this installation option > > is. There is NO difference in the number of choices available in any of > > the three types. > > > > Guided/Express/Expert. That's my vote. > > This still implies that Expert nee Custom is superior to Guided nee > Novice, in ways that it is not. As far as I can tell the only thing > Expert provides is the ability to skip steps and to do steps in the wrong > order so that the install will fail. > > Standard/Express/Exceptional. Would be my vote, if I had a vote which I'm > sure I don't. > Guided/Express/Dangerous ? -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@FreeBSD.org Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-946013071 ----------------------------------------------------------------------- "Beware of Programmers who carry screwdrivers" -- Leonard Brandwein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 16:20: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2CE9037BC50 for ; Sat, 19 Feb 2000 16:20:05 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA81215; Sat, 19 Feb 2000 17:19:50 -0700 (MST) (envelope-from ken) Date: Sat, 19 Feb 2000 17:19:50 -0700 From: "Kenneth D. Merry" To: Bob Bishop Cc: current@FreeBSD.ORG Subject: Re: cdrecord problem with current current Message-ID: <20000219171950.A81155@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 1.0i In-Reply-To: ; from rb@gid.co.uk on Sat, Feb 19, 2000 at 07:28:23PM +0000 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, Feb 19, 2000 at 19:28:23 +0000, Bob Bishop wrote: > Hi, > > cdrecord, freshly built on last night's -current: Freshly built? That's cdrecord 1.8a21, which is several versions old. I think you should be using cdrecord 1.8 release from the ports tree. > atlas# cdrecord -v dev=1,6,0 -inq > Cdrecord release 1.8a21 Copyright (C) 1995-1999 J–rg Schilling > TOC Type: 1 = CD-ROM > scsidev: '1,6,0' > scsibus: 1 target: 6 lun: 0 > atapi: 0 > cdrecord: Warning: controller returns zero sized CD capabilities page. > cdrecord: Warning: controller returns wrong size for CD capabilities page. > cdrecord: Warning: controller returns wrong page 0 for CD capabilities page > (2A) > . > Device type : Removable CD-ROM > Version : 2 > Response Format: 2 > Capabilities : SYNC > Vendor_info : 'YAMAHA ' > Identifikation : 'CRW4416S ' > Revision : '1.0f' > Device seems to be: Generic CD-ROM. > atlas# > > ...so cdrecord can't tell what the device is. Am I in trouble because the > CDR isn't on the first SCSI controller, or has something got broken? Dmesg > follows: It's fine for your drive to be on a different controller. The real question is, has cdrecord worked fine before, or is this the first time you've used it with your drive? Does camcontrol work? Try this: camcontrol devlist camcontrol tur cd0 -v camcontrol inquiry cd0 -v [ note that the inquiry command will return partially bogus results, I'm waiting for Justin to review patches to fix that ] Also see what happens if you try the '-prcap' option to cdrecord. And use the latest version of cdrecord, so we can eliminate any probelms with cdrecord. [ ... ] > aha0 at port 0x330-0x333 irq 11 drq 5 on isa0 > aha0: AHA-1542CF FW Rev. C.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs [ ... ] > Mounting root from ufs:/dev/da0a > cd0 at aha0 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 3.300MB/s transfers > cd0: cd present [1 x 2048 byte records] Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 17:35:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 928C237BD45; Sat, 19 Feb 2000 17:35:48 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id RAA95727; Sat, 19 Feb 2000 17:35:48 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 17:35:48 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <41481.951002195@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jordan K. Hubbard wrote: > > It already does this if you get your crypto from internat. US mirror sites > > only carry the neutered (no-RSA) version, but internat carries RSA and > > builds it conditional on USA_RESIDENT. > > And why don't the USA sites have the RSAREF version? I'm still not > sure I understand the compartmentalization here. I meant they don't carry RSA cryptographic code. They carry the interface stubs which enable it to link against rsaref if present, and to use rsaref to provide the RSA crypto. Building with rsaref can't be the default case, because it's restrictively licensed and not legal for some people to use. > > 2) if you don't build with any sort of RSA (i.e. USA_RESIDENT == YES and > > you don't have the rsaref package installed) then you don't get > > include/rsa.h but get everything else "standard". > > It's this rsaref thing that's hanging me up. Why is it either on > or off vs on from location A or on from location B? If you do nothing, just build with the default sources or install the default binaries, you don't get any RSA. Similarly if you install the openssl-norsa package (e.g. if you want to revert from openssl-rsaref). If you install rsaref via port/package, and then rebuild, you'll get an rsaref-enabled openssl. If you install the openssl-rsaref package on a fresh system, it will pull in a dependency on rsaref and you get the same thing. This is what people who don't want to rebuild from sources, but who need RSA functionality (and pass the rsaref license) should do after installation (or during installation, if sysinstall would support it). The system should be prompting them to do this if they forget and try and install an openssl port which needs RSA (this is seemingly not working). It's really quite simple :-) > > Did you ever hear back from the lawyers about whether (and how) we can > > freely distribute openssl (and other stuff) from the US? Apart from that > > it does just reduce to the case of keeping the patent lawyers happy by > > keeping the patented code away from US people. > > The lawyers haven't been willing to say anything about this right now, > citing too large of a caseload to even begin untangling the Clinton > administration's current position. Okay, thanks. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 17:37: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.netaxs.com (mail.netaxs.com [207.8.186.26]) by hub.freebsd.org (Postfix) with ESMTP id E1FF637BD58 for ; Sat, 19 Feb 2000 17:36:54 -0800 (PST) (envelope-from bleez@netaxs.com) Received: from gravy.kishka.net (dyn-13.blackbox-2.netaxs.com [207.106.60.13]) by mail.netaxs.com (8.8.7/8.8.5) with ESMTP id UAA00414; Sat, 19 Feb 2000 20:36:51 -0500 (EST) Received: from localhost (gravy.kishka.net [127.0.0.1]) by gravy.kishka.net (8.9.3/8.9.3) with ESMTP id UAA19948; Sat, 19 Feb 2000 20:36:49 -0500 (EST) (envelope-from bleez@netaxs.com) Date: Sat, 19 Feb 2000 20:36:49 -0500 (EST) From: Bryan Liesner X-Sender: root@gravy.kishka.net Reply-To: Bryan Liesner To: Kenneth Wayne Culver Cc: freebsd-current@FreeBSD.ORG Subject: Re: ATA errors In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Kenneth Wayne Culver wrote: >I cvsupped this morning and I just had a chance to build a new kernel, and >now I get a "cannot mount root" and it drops into some kind of commandline >where I can enter a root for it to mount. This is the error it gives me >now: > >ata0-slave: WARNING: WAIT_INTR active=ATA_WAIT_READY >ata0-slave: ata_command: timeout waiting for intr >ata0-slave: identify failed I went through this this morning. If you are loading modules from the boot loader, load them later, like from rc.conf. I'm not sure what broke there, but it's a good workaround. -Bryan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 18:13:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id BFD9E37BDB5; Sat, 19 Feb 2000 18:13:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id SAA41902; Sat, 19 Feb 2000 18:13:38 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 17:35:48 PST." Date: Sat, 19 Feb 2000 18:13:38 -0800 Message-ID: <41899.951012818@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Building with rsaref can't be the default case, because it's restrictively > licensed and not legal for some people to use. It's trying to figure out who "some" people are and how to address the needs of people who don't fit that category that I'm still having a hard time with here. If I have multiple CDROM products available, what's to stop me from creating a "complete" solution for each of the different groups? - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 18:16:48 2000 Delivered-To: freebsd-current@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id F319C37BC8A for ; Sat, 19 Feb 2000 18:16:42 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p51-dn02kiryunisiki.gunma.ocn.ne.jp [211.0.245.116]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id LAA18233; Sun, 20 Feb 2000 11:16:35 +0900 (JST) Message-ID: <38AF3A00.BCD1CBB1@newsguy.com> Date: Sun, 20 Feb 2000 09:49:04 +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: "Jeffrey J. Mountin" Cc: "Jordan K. Hubbard" , current@FreeBSD.ORG Subject: Re: feedback on CD install of 4.0-RC2 References: <3.0.3.32.20000219043230.009e2430@207.227.119.2> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG "Jeffrey J. Mountin" wrote: > > At 10:36 AM 2/18/00 -0800, Jordan K. Hubbard wrote: > >I will also say here and now that even I use the Standard installation > >since I don't like having to remember all the canonical steps in setting > >up a "stock" system and if anybody should remember them, it should be > >me - I've probably installed FreeBSD at least 50,000 times. :-) > > Ah, but doesn't the now-standard-install make a partition for /var and /tmp? No. The partitioner creates /, /usr, /var and swap if you say so. That's the exact same partitioner used in any installation mode. > I'd rather have a /, swap, and /usr. Then, at need, add drives at mount > points. No need to get into they why, what, and where, but suffice to say > is the main reason for using custom. The ports and X are added after the It's another indication that you misunderstand "novice" and "custom", proving that they are misnamed. -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "If you consider our help impolite, you should see the manager." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 18:31:12 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id C257F37BDE6; Sat, 19 Feb 2000 18:31:09 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id SAA98762; Sat, 19 Feb 2000 18:31:09 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 18:31:09 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <41899.951012818@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jordan K. Hubbard wrote: > > Building with rsaref can't be the default case, because it's restrictively > > licensed and not legal for some people to use. > > It's trying to figure out who "some" people are and how to address the > needs of people who don't fit that category that I'm still having a > hard time with here. If I have multiple CDROM products available, > what's to stop me from creating a "complete" solution for each of the > different groups? I don't think we're allowed to distribute rsaref on CDROM, period. From the license file: 1. RSAREF is free for personal or corporate use under the following conditions: o RSAREF, RSAREF applications, and services based on RSAREF applications may not be sold. o You must give RSA the source code of any free RSAREF application you plan to distribute or deploy within your company. RSA will make these applications available to the public, free of charge. 2. RSAREF applications and services based on RSAREF applications may be sold under the following conditions: o You must sign and return the RSAREF Commercial License Agreement to RSA (call RSA for a copy of this agreement). Remember, RSAREF is an unsupported toolkit. If you are building an application to sell, you should consider using fully supported libraries like RSA's BSAFE or TIPEM SDK's. 6. You can't send or transmit (or cause to be transmitted) RSAREF outside the United States or Canada, or give it to anyone who is not a U.S. or Canadian citizen or doesn't have a "green card." I haven't contacted RSA about Option 2, but from all reports they refuse to provide the license agreement to be signed anyway - it's a clause they wish they hadn't put in there. I've never heard of RSA fulfilling their part of option 1, either. Since we can't ship rsaref on CD, and openssl must be recompiled to build against rsaref (i.e. one size doesn't fit all) I don't see many options apart from adding the openssl-rsaref package (which we could distribute on CD) and downloading rsaref from the net, if the user says they pass the license agreement. Kris > - Jordan ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 19: 2: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from hydrant.intranova.net (hydrant.intranova.net [209.201.95.10]) by hub.freebsd.org (Postfix) with SMTP id 3E21737BDF9 for ; Sat, 19 Feb 2000 19:01:58 -0800 (PST) (envelope-from oogali@intranova.net) Received: (qmail 1231 invoked from network); 20 Feb 2000 03:02:02 -0000 Received: from localhost (user48802@127.0.0.1) by hydrant.intranova.net with SMTP; 20 Feb 2000 03:02:02 -0000 Date: Sat, 19 Feb 2000 22:02:01 -0500 (EST) From: Omachonu Ogali To: freebsd-current@freebsd.org Subject: make world Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Anyone else got this error? -- snip -- ===> lib/libcom_err/doc install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir install-info: unrecognized option `--defsection=Programming & development tools.' Try `install-info --help' for a complete list of options. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. *** Error code 1 Stop. # -- snip -- -- +-------------------------------------------------------------------------+ | Omachonu Ogali oogali@intranova.net | | Intranova Networking Group http://tribune.intranova.net | | PGP Key ID: 0xBFE60839 | | PGP Fingerprint: C8 51 14 FD 2A 87 53 D1 E3 AA 12 12 01 93 BD 34 | +-------------------------------------------------------------------------+ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 19:20:47 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.254.39]) by hub.freebsd.org (Postfix) with ESMTP id D2DE637BD56; Sat, 19 Feb 2000 19:20:34 -0800 (PST) (envelope-from bloom@reyim.ne.mediaone.net) Received: (from bloom@localhost) by reyim.ne.mediaone.net (8.9.3/8.9.3) id WAA38491; Sat, 19 Feb 2000 22:20:23 -0500 (EST) (envelope-from bloom) Date: Sat, 19 Feb 2000 22:20:23 -0500 (EST) From: Jim Bloom Message-Id: <200002200320.WAA38491@reyim.ne.mediaone.net> To: asami@freebsd.org, jkh@freebsd.org, kris@freebsd.org Subject: Fix for problems building openssl ports Cc: freebsd-current@freebsd.org Reply-To: bloom@acm.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I found the problem Jordan and Robert Watson were having building ports that require rsaref and openssl. The test for whether libcrypto was compiled with RSA was using shell syntax for executing the command and not make's syntax. The extra 'true' on the command is to silence make's warning about a non-zero exit status of the command. With the fix below, the error about RSA being required is now displayed at the correct time. This still does not solve the more fundamental problem of what gets distributed on the CD in terms openssl and RSA. Jim Bloom bloom@asm.org --- ports/Mk/bsd.port.mk.orig Sat Feb 19 21:51:49 2000 +++ ports/Mk/bsd.port.mk Sat Feb 19 22:00:39 2000 @@ -582,7 +582,7 @@ @${FALSE} .else .if ${USE_OPENSSL} == RSA -_HASRSA= "`/usr/bin/nm /usr/lib/libcrypto.a | /usr/bin/grep RSA_free`" +_HASRSA!= /usr/bin/nm /usr/lib/libcrypto.a | /usr/bin/grep RSA_free ; true .if empty(_HASRSA) .BEGIN: @${ECHO} "This port requires RSA crypto, which is not present in your" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 19:27:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 5309C37BD9F; Sat, 19 Feb 2000 19:27:19 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id TAA01700; Sat, 19 Feb 2000 19:27:19 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 19:27:18 -0800 (PST) From: Kris Kennaway To: bloom@acm.org Cc: asami@freebsd.org, jkh@freebsd.org, freebsd-current@freebsd.org Subject: Re: Fix for problems building openssl ports In-Reply-To: <200002200320.WAA38491@reyim.ne.mediaone.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jim Bloom wrote: > I found the problem Jordan and Robert Watson were having building ports that > require rsaref and openssl. The test for whether libcrypto was compiled with > RSA was using shell syntax for executing the command and not make's syntax. > The extra 'true' on the command is to silence make's warning about a non-zero > exit status of the command. D'oh! I was sure I tested this :-( I want to make a few other changes to bsd.port.mk (documentation of where to find the handbook, etc) & will submit the resulting patch to Satoshi. Thanks, Jim! Kris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 19:28:29 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id 7573037BDEE; Sat, 19 Feb 2000 19:28:26 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id TAA10967; Sat, 19 Feb 2000 19:28:25 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38AF5F59.A0BEC49@gorean.org> Date: Sat, 19 Feb 2000 19:28:25 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Sat, 19 Feb 2000, Victor Salaman wrote: > > > I personally think that it's braindead to add openssl to the system > > and stripout parts of it (RSA & IDEA). Don't get me wrong, I love to > > have Pardon me for coming late to the party, but what was the rationale behind putting openssl into the source anyway? Given the rsa/no rsa problems, not to mention the US vs. the world problems, what were the benefits that outweighed the complications? Note, I'm not trying to be critical here, I'm just interested in the thought process behind the decision. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 19:29:20 2000 Delivered-To: freebsd-current@freebsd.org Received: from reyim.ne.mediaone.net (reyim.ne.mediaone.net [24.218.254.39]) by hub.freebsd.org (Postfix) with ESMTP id 13D4837BD9A for ; Sat, 19 Feb 2000 19:29:15 -0800 (PST) (envelope-from bloom@acm.org) Received: from acm.org (localhost [127.0.0.1]) by reyim.ne.mediaone.net (8.9.3/8.9.3) with ESMTP id WAA38500; Sat, 19 Feb 2000 22:28:33 -0500 (EST) (envelope-from bloom@acm.org) Message-ID: <38AF5F61.F48B9FAF@acm.org> Date: Sat, 19 Feb 2000 22:28:33 -0500 From: Jim Bloom Reply-To: bloom@acm.org X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: Omachonu Ogali Cc: freebsd-current@FreeBSD.ORG Subject: Re: make world References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG See the file src/UPDATING. This is one of a couple problems that one sees when trying to install current on an older system. If this error isn't mentioned explicitly, check the sections relating to flags and xinstall (install). Jim Bloom bloom@acm.org Omachonu Ogali wrote: > > Anyone else got this error? > > -- snip -- > ===> lib/libcom_err/doc > install-info --quiet --defsection="Programming & development tools." --defentry="* libcom_err: (com_err). A Common Error Description Library for UNIX." com_err.info /usr/share/info/dir > install-info: unrecognized option `--defsection=Programming & development tools.' > Try `install-info --help' for a complete list of options. > *** Error code 1 > > Stop. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 19:46:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 0391237BD9A; Sat, 19 Feb 2000 19:46:51 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id TAA02519; Sat, 19 Feb 2000 19:46:50 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 19:46:50 -0800 (PST) From: Kris Kennaway To: Doug Barton Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <38AF5F59.A0BEC49@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Doug Barton wrote: > Pardon me for coming late to the party, but what was the > rationale behind putting openssl into the source anyway? Given the > rsa/no rsa problems, not to mention the US vs. the world problems, > what were the benefits that outweighed the complications? Note, I'm > not trying to be critical here, I'm just interested in the thought > process behind the decision. Having _a_ general-purpose cryptography toolkit in the base system allows us to add in all sorts of cool things to FreeBSD (https support for fetch, openssh, random cryptographic enhancements elsewhere). OpenSSL just happens to be the only decent freely-available (BSDL) toolkit. The patent nonsense with RSA will be going away in september, and the US vs. the world problems have also been receding and probably won't last much longer either. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 20: 7: 2 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 89A7137BDF9; Sat, 19 Feb 2000 20:06:59 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA42147; Sat, 19 Feb 2000 20:06:52 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 18:31:09 PST." Date: Sat, 19 Feb 2000 20:06:52 -0800 Message-ID: <42144.951019612@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hmmm. I'm beginning to wonder if openssl shouldn't just be backed-out at this point. The situation with RSA makes this far more problematic than I think anyone first thought, and I've seen a lot of breakage so far for what appears to be comparatively little gain over what we had before with the ports collection version. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 20: 9: 3 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id ADDBF37BDE6; Sat, 19 Feb 2000 20:09:00 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA42161; Sat, 19 Feb 2000 20:08:44 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Doug Barton Cc: Kris Kennaway , Victor Salaman , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 19:28:25 PST." <38AF5F59.A0BEC49@gorean.org> Date: Sat, 19 Feb 2000 20:08:44 -0800 Message-ID: <42158.951019724@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Kris Kennaway wrote: > > > > On Sat, 19 Feb 2000, Victor Salaman wrote: > > > > > I personally think that it's braindead to add openssl to the system > > > and stripout parts of it (RSA & IDEA). Don't get me wrong, I love to > > > have > > Pardon me for coming late to the party, but what was the rationale behind > putting openssl into the source anyway? Given the rsa/no rsa problems, not > to mention the US vs. the world problems, what were the benefits that > outweighed the complications? Note, I'm not trying to be critical here, I'm > just interested in the thought process behind the decision. I think the idea was to eventually bundle openssh into the system, but this now look comparatively difficult enough that I'm definitely having second thoughts about the whole thing. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 20:10: 4 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7195837BE3B; Sat, 19 Feb 2000 20:09:58 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA42181; Sat, 19 Feb 2000 20:09:50 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Doug Barton , Victor Salaman , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 19:46:50 PST." Date: Sat, 19 Feb 2000 20:09:50 -0800 Message-ID: <42178.951019790@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Having _a_ general-purpose cryptography toolkit in the base system allows > us to add in all sorts of cool things to FreeBSD (https support for fetch, > openssh, random cryptographic enhancements elsewhere). OpenSSL just > happens to be the only decent freely-available (BSDL) toolkit. And I still think that this is a reasonable objective, the current gymnastics for making it happen making me wonder whether or not that would not be an objective better moved to sometime in September. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 20:16: 5 2000 Delivered-To: freebsd-current@freebsd.org Received: from gothic.iinet.net.au (gothic.iinet.net.au [203.59.24.252]) by hub.freebsd.org (Postfix) with ESMTP id 8DC1C37BDA1 for ; Sat, 19 Feb 2000 20:15:59 -0800 (PST) (envelope-from julian@elischer.org) Received: from jules.elischer.org (reggae-02-97.nv.iinet.net.au [203.59.91.97]) by gothic.iinet.net.au (8.8.5/8.8.5) with SMTP id MAA16155 for ; Sun, 20 Feb 2000 12:15:51 +0800 Message-ID: <38AF6A0C.167EB0E7@elischer.org> Date: Sat, 19 Feb 2000 20:14:04 -0800 From: Julian Elischer X-Mailer: Mozilla 3.04Gold (X11; I; FreeBSD 4.0-CURRENT i386) MIME-Version: 1.0 To: current@freebsd.org Subject: I'm baaaaack Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm back and resubscribed to a subset of lists (hackers, announce and current) My connectivity is still shitty, but I'm working on it and have managed to Cvsup my cvs tree up-to-date. Julian -- +------------------------------------+ | __--_|\ Julian Elischer | | / \ julian@elischer.org +--from Perth to the world. | ( OZ ) World tour 2000 +- X_.---._/ presently in: Perth v To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 20:23:27 2000 Delivered-To: freebsd-current@freebsd.org Received: from ptldpop2.ptld.uswest.net (ptldpop2.ptld.uswest.net [198.36.160.2]) by hub.freebsd.org (Postfix) with SMTP id 51EAB37BE21 for ; Sat, 19 Feb 2000 20:23:22 -0800 (PST) (envelope-from wwoods@cybcon.com) Received: (qmail 15753 invoked by alias); 20 Feb 2000 04:23:18 -0000 Delivered-To: fixup-freebsd-current@FreeBSD.ORG@fixme Received: (qmail 15728 invoked by uid 0); 20 Feb 2000 04:23:17 -0000 Received: from fdslppp250.ptld.uswest.net (HELO laptop.cybcon.com) (216.161.92.250) by ptldpop2.ptld.uswest.net with SMTP; 20 Feb 2000 04:23:17 -0000 Content-Length: 1184 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: <42158.951019724@zippy.cdrom.com> Date: Sat, 19 Feb 2000 20:20:15 -0800 (PST) Reply-To: bwoods2@uswest.net From: William Woods To: "Jordan K. Hubbard" Subject: Re: openssl in -current Cc: freebsd-current@FreeBSD.ORG, Victor Salaman , Kris Kennaway , Doug Barton Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG How does OpenBSD do it? Cant we do what they do? On 20-Feb-00 Jordan K. Hubbard wrote: >> Kris Kennaway wrote: >> > >> > On Sat, 19 Feb 2000, Victor Salaman wrote: >> > >> > > I personally think that it's braindead to add openssl to the system >> > > and stripout parts of it (RSA & IDEA). Don't get me wrong, I love to >> > > have >> >> Pardon me for coming late to the party, but what was the rationale behind >> putting openssl into the source anyway? Given the rsa/no rsa problems, not >> to mention the US vs. the world problems, what were the benefits that >> outweighed the complications? Note, I'm not trying to be critical here, I'm >> just interested in the thought process behind the decision. > > I think the idea was to eventually bundle openssh into the system, but > this now look comparatively difficult enough that I'm definitely > having second thoughts about the whole thing. > > - Jordan > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message ---------------------------------- E-Mail: William Woods Date: 19-Feb-00 Time: 20:19:39l ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 20:27:52 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 1401D37BE46; Sat, 19 Feb 2000 20:27:49 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA04053; Sat, 19 Feb 2000 20:27:48 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 20:27:48 -0800 (PST) From: Kris Kennaway To: bwoods2@uswest.net Cc: "Jordan K. Hubbard" , freebsd-current@FreeBSD.ORG, Victor Salaman , Doug Barton Subject: Re: openssl in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, William Woods wrote: > How does OpenBSD do it? Cant we do what they do? They do a worse job than us is the short answer. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 20:32:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from kibby.knf.beldin.net (kibby.knf.beldin.net [203.38.198.130]) by hub.freebsd.org (Postfix) with ESMTP id 7AFD237BE28 for ; Sat, 19 Feb 2000 20:32:16 -0800 (PST) (envelope-from kibbet@kibby.knf.beldin.net) Received: (from kibbet@localhost) by kibby.knf.beldin.net (8.9.3/8.9.3) id PAA10197 for freebsd-current@freebsd.org; Sun, 20 Feb 2000 15:01:57 +1030 (CST) (envelope-from kibbet) 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: <38AF5F61.F48B9FAF@acm.org> Date: Sun, 20 Feb 2000 15:01:57 +1030 (CST) From: kibbet To: freebsd-current@freebsd.org Subject: Re: make world Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hey all, I got this error, and the 20000205 entry in UPDATING didn't seem to cover enough for me, I was comming from a clean bin install of 3.2. UPDATING - 20000205 entry; make buildworld make installworld This will fail cd usr.bin/xinstall make clean all install NOSHARED=YES cd ../.. XXX make installworld (2) cd gnu/usr.bin/texinfo (3) make clean all install NOSHARED=YES (4) cd ../../.. (5) make installworld XXX This line failed for me, so I did (2) to (5) :) I guess maybe I should go back in and recompile texinfo without the NOSHARED arg. Its been up just over a day now, no probs, and its just about to compile XFree v4. Cheers, Kent Ibbetson kib@knfpub.com On 20-Feb-00 Jim Bloom wrote: > See the file src/UPDATING. This is one of a couple problems that one > sees when trying to install current on an older system. If this error > isn't mentioned explicitly, check the sections relating to flags and > xinstall (install). > > Jim Bloom > bloom@acm.org > > Omachonu Ogali wrote: >> >> Anyone else got this error? >> >> -- snip -- >> ===> lib/libcom_err/doc >> install-info --quiet --defsection="Programming & development tools." >> --defentry="* libcom_err: (com_err). A Common Error Description >> Library for UNIX." com_err.info /usr/share/info/dir >> install-info: unrecognized option `--defsection=Programming & development >> tools.' >> Try `install-info --help' for a complete list of options. >> *** Error code 1 >> >> Stop. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 20:34:58 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id DC3D537BDEE; Sat, 19 Feb 2000 20:34:55 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id UAA42336; Sat, 19 Feb 2000 20:34:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: bwoods2@uswest.net Cc: freebsd-current@FreeBSD.ORG, Victor Salaman , Kris Kennaway , Doug Barton Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 20:20:15 PST." Date: Sat, 19 Feb 2000 20:34:42 -0800 Message-ID: <42333.951021282@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > How does OpenBSD do it? Cant we do what they do? 1. They're in Canada 2. What they do appears to be kind of icky, e.g. it requires more "hand work" than I think the average FreeBSD user would be willing to accept (or the average developer would be willing to see in the tree in such a form). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 20:40:42 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 67C9F37BE09; Sat, 19 Feb 2000 20:40:39 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id UAA04641; Sat, 19 Feb 2000 20:40:39 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 20:40:39 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <42144.951019612@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jordan K. Hubbard wrote: > Hmmm. I'm beginning to wonder if openssl shouldn't just be backed-out > at this point. The situation with RSA makes this far more problematic > than I think anyone first thought, and I've seen a lot of breakage so > far for what appears to be comparatively little gain over what we had > before with the ports collection version. Well, you're the release engineer of course..but I don't think the problems are insurmountable. Sysinstall could be made to install the correct package after asking the user the right questions (if they choose to install crypto): 1) Are you a resident of the USA? YES/NO NO -> installs the international package (actually, if they're net-installing and get their crypto from an international site they'll get the correct openssl version anyway) YES -> 2) 2) Do you wish to install RSA cryptography support? NOTE: RSA support is required for many third-party applications, but due to patent restrictions it is not available for unrestricted use. Selecting 'YES' will display the text of the license agreement imposed by RSA Security, Inc. and ask if you wish to proceed. NO -> installs the "no-rsa" package YES -> 3) 3) Displays the rsaref license, and asks for confirmation whether the user conforms to it. NO -> installs the "no-rsa" package YES -> installs the rsaref package and the openssl-rsaref package. The situation at present, compared to installing from ports, just unmasks the fact that a lot of people are using rsaref when they're not supposed to be ("make USA_RESIDENT=yes install" will automatically install rsaref without requiring you to read and agree to the license conditions). If you think the above can't be implemented in time for 4.0 and the alternatives (i.e. user deciding for himself which package to install and doing it manually) are not feasible then I will (reluctantly) back it out for the 4.0 release. Kris > > - Jordan > ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 21: 0: 1 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id A1AF037BE8F; Sat, 19 Feb 2000 20:59:54 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id UAA34072; Sat, 19 Feb 2000 20:59:53 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38AF74C8.29BC6EC8@gorean.org> Date: Sat, 19 Feb 2000 20:59:52 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Sat, 19 Feb 2000, Doug Barton wrote: > > > Pardon me for coming late to the party, but what was the > > rationale behind putting openssl into the source anyway? Given the > > rsa/no rsa problems, not to mention the US vs. the world problems, > > what were the benefits that outweighed the complications? Note, I'm > > not trying to be critical here, I'm just interested in the thought > > process behind the decision. > > Having _a_ general-purpose cryptography toolkit in the base system allows > us to add in all sorts of cool things to FreeBSD (https support for fetch, > openssh, random cryptographic enhancements elsewhere). OpenSSL just > happens to be the only decent freely-available (BSDL) toolkit. Ok, that's pretty much what I expected, but thanks for the confirmation. > The patent nonsense with RSA will be going away in september, and the US > vs. the world problems have also been receding and probably won't last > much longer either. So how effective is openssl (plus the things that do/will depend on it) without rsa(ref)? Can we complete the integration process assuming that rsa* won't be on the system, but add hooks so that if the user has independently installed the rsaref port openssl in the base will pick that up? That will solve half the problem I think. As for the other problem, what is currently different between the US and international code repositories? I think I'm getting a handle on what's happening, it sounds like the problems are not that difficult to solve, the just require some planning. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 21: 5:21 2000 Delivered-To: freebsd-current@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id 380F737BE51 for ; Sat, 19 Feb 2000 21:05:17 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA51863; Sun, 20 Feb 2000 15:35:08 +1030 (CST) Date: Sun, 20 Feb 2000 15:35:07 +1030 From: Greg Lehey To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: I'm baaaaack Message-ID: <20000220153507.H50294@freebie.lemis.com> References: <38AF6A0C.167EB0E7@elischer.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <38AF6A0C.167EB0E7@elischer.org> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Saturday, 19 February 2000 at 20:14:04 -0800, Julian Elischer wrote: > I'm back and resubscribed to a subset of lists > (hackers, announce and current) > My connectivity is still shitty, but I'm working on it > and have managed to Cvsup my cvs tree up-to-date. > > +------------------------------------+ > | __--_|\ Julian Elischer | > | / \ julian@elischer.org +--from Perth to the world. > | ( OZ ) World tour 2000 > +- X_.---._/ presently in: Perth Welcome back. What's the truth, your .sig or your time zone? Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 21:14: 9 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id F034037BDF5; Sat, 19 Feb 2000 21:14:06 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id VAA06106; Sat, 19 Feb 2000 21:14:06 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 21:14:06 -0800 (PST) From: Kris Kennaway To: Doug Barton Cc: Victor Salaman , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <38AF74C8.29BC6EC8@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Doug Barton wrote: > > The patent nonsense with RSA will be going away in september, and the US > > vs. the world problems have also been receding and probably won't last > > much longer either. > > So how effective is openssl (plus the things that do/will depend on it) > without rsa(ref)? Can we complete the integration process assuming that It does everything except RSA and SSLv2 (which requires RSA). Openssl works perfectly, the problem is that a lot of ports require RSA. > rsa* won't be on the system, but add hooks so that if the user has > independently installed the rsaref port openssl in the base will pick that > up? That will solve half the problem I think. openssl must be rebuilt after you install rsaref to pick up the changed code. Alternatively, you can install a binary package to do the same job. > As for the other problem, what is currently different between the US > and international code repositories? I think I'm getting a handle on > what's happening, it sounds See chapter 6.5 in the handbook. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 21:23:53 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id BBFA537BDF3; Sat, 19 Feb 2000 21:23:49 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id VAA40550; Sat, 19 Feb 2000 21:23:49 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38AF7A64.53E8DA00@gorean.org> Date: Sat, 19 Feb 2000 21:23:48 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 Cc: John Baldwin , freebsd-current@FreeBSD.ORG Subject: Ready to get back in the game References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've finally got up to date on my mail, so I think I'm ready to dive into following -current. I'm wondering if the below is still a good description of how to update from a pre-signal changes -current to recent versions? UPDATING still mentions the xinstall business, but I seem to have gathered from recent posts that this is no longer necessary? Thanks, Doug "Eugene M. Kim" wrote: > > On Thu, 10 Feb 2000, John Baldwin wrote: > > | You need a -current kernel for installworld to work. In fact, > | if you aren't running a -current kernel installworld will blow > | up on your machine. Try this instead: > | > | - cvsup -current > | - make buildworld > | - make buildkernel > | - make installkernel > > - backup /dev to /dev.orig > - mkdir /dev > - copy /usr/src/etc/MAKEDEV* into /dev > - remake all devices in /dev (don't forget to make the disk slice > entries separately) > > | - reboot into single user mode > | - make -DNOINFO installworld > | - make installworld > | - merge over /etc changes, etc. > | - reboot -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 21:35: 0 2000 Delivered-To: freebsd-current@freebsd.org Received: from tomts2-srv.bellnexxia.net (tomts2.bellnexxia.net [209.226.175.140]) by hub.freebsd.org (Postfix) with ESMTP id 5187137BE5A for ; Sat, 19 Feb 2000 21:34:57 -0800 (PST) (envelope-from kfarmer@sympatico.ca) Received: from sympatico.ca ([206.172.165.86]) by tomts2-srv.bellnexxia.net (InterMail vM.4.01.02.17 201-229-119) with ESMTP id <20000220053455.KBUY17030.tomts2-srv.bellnexxia.net@sympatico.ca> for ; Sun, 20 Feb 2000 00:34:55 -0500 Message-ID: <38AF7D92.984F5DEE@sympatico.ca> Date: Sun, 20 Feb 2000 00:37:22 -0500 From: Kelvin Farmer X-Mailer: Mozilla 4.7 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-current@freebsd.org Subject: Re: 4.0(current) on a 486SLC2 ? References: <38AE0CDE.2339FD8A@sympatico.ca> <20000219125702.B2923@relay.ucb.crimea.ua> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Fri, Feb 18, 2000 at 10:24:14PM -0500, Kelvin wrote: > Hi, > I was wondering if its possible to run FreeBSD-4.0 on a 486 SLC2 66mhz. I tried compiling a custom kernel without the pci device, and get the same panic: .. CPU: Blue Lightning CPU (486 class CPU) Origin="IBM" ... npx0: on motherboard npx0:Using IRQ 13 interface Fatal trap 12: page fault in kernel mode. (etc) (This seems to be a fairly differnet cpu from the SLC reported to work by someone else as: ... CPU: Cyrix 486SLC/DLC (486-class CPU) Origin = "CyrixInstead" DIR=0x00ff Stepping=0 Revision=0 ... npx0: on motherboard npx0: 387 emulator ...) Anybody have any ideas on what to try next? I suppose an earlier version of FreeBSD might help...? Thanks, Kelvin. kfarmer@sympatico.ca To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 21:43:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from diwanh.stu.rpi.edu (diwanh.stu.rpi.edu [128.113.151.72]) by hub.freebsd.org (Postfix) with ESMTP id 76A7837BE51 for ; Sat, 19 Feb 2000 21:43:54 -0800 (PST) (envelope-from hdiwan@diwanh.stu.rpi.edu) Received: (from hdiwan@localhost) by diwanh.stu.rpi.edu (8.9.3/8.9.3) id AAA56054 for freebsd-current@FreeBSD.ORG; Sun, 20 Feb 2000 00:43:44 -0500 (EST) (envelope-from hdiwan) Date: Sun, 20 Feb 2000 00:43:43 -0500 From: Hasan Diwan To: freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current Message-ID: <20000220004343.A53017@diwanh.stu.rpi.edu> References: <42158.951019724@zippy.cdrom.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="Qxx1br4bt0+wmkIi" X-Mailer: Mutt 1.0i In-Reply-To: ; from wwoods@cybcon.com on Sat, Feb 19, 2000 at 08:20:15PM -0800 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG --Qxx1br4bt0+wmkIi Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable * William Woods (wwoods@cybcon.com) [000220 00:28]: > How does OpenBSD do it? Cant we do what they do? OpenBSD is based in Canada, which doesn't restrict the export of encryption. So, unless FreeBSD development moves to Canada, we can't do what they do. -- Hasan Diwan [hdiwan@pobox.com] :) Rensselaer Polytechnic Institute=20 Computer Science Department --Qxx1br4bt0+wmkIi Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBOK9/DvitTU38wbMJAQHK7AQAp0Jh5DYrOvEsOm7NpvfpoDJ49gv2WnVo hmlLO2uv85HDx/STDy6eHQjxjOoCloJ9XGC255y8vsFj1aJTd9IqUEkoGq1Hy6Bu GV0rYSb35G5/0GdFc1FNrn2/uvNmPU803JZ8L5b+4T+amYJndAhvdbpD1QCNMKkv TxbEviHtl18= =rJLJ -----END PGP SIGNATURE----- --Qxx1br4bt0+wmkIi-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 21:52:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from teknos.teknos.com (teknos-gw.nappr.org [216.0.190.254]) by hub.freebsd.org (Postfix) with ESMTP id DD6EA37BDF5; Sat, 19 Feb 2000 21:52:53 -0800 (PST) (envelope-from salaman@teknos.com) Received: by teknos.teknos.com with Internet Mail Service (5.5.2650.21) id <19NW71H3>; Sun, 20 Feb 2000 01:47:48 -0400 Message-ID: <1D45ABC754FB1E4888E508992CE97E4F059CE6@teknos.teknos.com> From: "Victor A. Salaman" To: "'Jordan K. Hubbard'" , Doug Barton Cc: Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: RE: openssl in -current Date: Sun, 20 Feb 2000 01:47:44 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a crazy idea, and don't flame me for it... Don't remove OpenSSL from the three... put the whole thing there, the whole openssl distro in the tree. The problem with the patent is not that you CAN'T get the software, the problem is that you can't build with it and use it. But nobody said that you can't have it in the system. It's up to the USA_RESIDENT variable that RSAREF would be built (over the net). The only thing we would need to do is modify sysinstall if you are a USA resident with a disclaimer screen. That way we put the responsability onto the user, not the FreeBSD group. The logic behind this that OpenSSL has a non-restrictive license, so it can be distributed, you just can't build RSA and IDEA in the USA. If it worked otherwise, everyone downloading OpenSSL is violating the law, and OpenSSL would be illegal. When you download OpenSSL, it has the RSA & IDEA code in it, and it has the option to use RSAREF (see!! the user has the option to go with or against the law), but OpenSSL is distributed freely. I think that we are being too cautious for nothing. Let's just put the whole OpenSSL distribution into the system. If something happens, hey, OpenSSL is also breaking the law. What's the worst that can happen, a slap on the wrist? If it's available on the Net at www.openssl.org, and their license says it can be distributed, then it can. It's up to the user to decide if they want to build with RSAREF or not. I think that this would be the best choice, as we need decent crypto in the system, and it would require very minimal effort on our part. And then again, what the heck, we could always make the CD's in Japan and import them, hehe. Jordan, I think is the way to go... And the 2 CD thing is not a good idea. Just my 2 cents. -----Original Message----- From: Jordan K. Hubbard [mailto:jkh@zippy.cdrom.com] Sent: Sunday, February 20, 2000 12:09 AM To: Doug Barton Cc: Kris Kennaway; Victor Salaman; freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current > Kris Kennaway wrote: > > > > On Sat, 19 Feb 2000, Victor Salaman wrote: > > > > > I personally think that it's braindead to add openssl to the system > > > and stripout parts of it (RSA & IDEA). Don't get me wrong, I love to > > > have > > Pardon me for coming late to the party, but what was the rationale behind > putting openssl into the source anyway? Given the rsa/no rsa problems, not > to mention the US vs. the world problems, what were the benefits that > outweighed the complications? Note, I'm not trying to be critical here, I'm > just interested in the thought process behind the decision. I think the idea was to eventually bundle openssh into the system, but this now look comparatively difficult enough that I'm definitely having second thoughts about the whole thing. - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 21:54:51 2000 Delivered-To: freebsd-current@freebsd.org Received: from nt-exchange.ifas.ufl.edu (nt-exchange.ifas.ufl.edu [128.227.242.250]) by hub.freebsd.org (Postfix) with ESMTP id D3D1F37BE3C for ; Sat, 19 Feb 2000 21:54:42 -0800 (PST) (envelope-from bobj@atlantic.net) Received: from bsd.cisi.com (ocalflifanb-as-1-r1-ip-370.atlantic.net [209.208.29.116]) by nt-exchange.ifas.ufl.edu with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2650.21) id 14SGTLWC; Sun, 20 Feb 2000 00:52:18 -0500 Received: from nancy.cisi.com (nancy.cisi.com [192.168.0.131]) by bsd.cisi.com (8.9.3/8.9.3) with SMTP id AAA25154 for ; Sun, 20 Feb 2000 00:53:01 -0500 (EST) (envelope-from bobj@atlantic.net) Message-Id: <3.0.6.32.20000220005228.009a2b10@rio.atlantic.net> X-Sender: bobj@rio.atlantic.net X-Mailer: QUALCOMM Windows Eudora Light Version 3.0.6 (32) Date: Sun, 20 Feb 2000 00:52:28 -0500 To: freebsd-current@freebsd.org From: Bob Johnson Subject: 4.0RC2 FTP install sig 11 and other problems Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Greetings! The following is intended to be a report of my experience more than a request for help, although I will be happy to investigate this further if it will help debug anything. I created a pair of install floppies from the 20000214-CURRENT snapshot and tried to do an install on my old 486DX2-50 Everex Stepnote. It has previously run either 3.2R or 3.3R (I forget) with no problems except that my Ethernet card wasn't recognized. First problem: during kernel config, under miscellaneous I found ata0 and ata1 both listed as "Unknown device". They were pretty clearly IDE drivers, and ata0 did in fact work just fine. I suggest changing these from "Unknown" to "IDE Controller" or something like that. ========== The next problem I encountered was that while trying to configure the PCCARD stuff, it popped up with this dialog: Please select IRQs that can be used by PC-cards Please specify an IRQs that CANNOT be used by PC-card. For example, if you have a sound card that can't be probed by this installation floppy and it uses IRQ 10, you have to choose "Option 1" or "Option 2" at this menu. Default IRQ 10,11 Option 1 IRQ 5, 11 (ex. soundcard on IRQ 10) Option 2 IRQ 11 (ex. something on IRQ 5 and 10) OK Cancel Now, this confuses me. I couldn't tell whether I was supposed to be specifying what IRQs were not available for the PC Card controller to use, or which IRQs it should try to use. 3.4R-PAO is clearly asking for IRQs that CANNOT be used, so I suggest changing the title of this dialog to "Please select IRQs that cannot be used by PC cards". Also 3.4R-PAO offers more choices, which seems like a good idea. I couldn't ever find a configuration that would recognize either my Ethernet card (Eiger Labs EPX-10BT) or modem (Practical Peripherals PC336T2EZ). I just started a 3.4R-PAO install a few minutes ago and it had no trouble recognizing the modem (I didn't expect it to recognize the Ethernet card), so from my point of view, PCCARD support is worse in 4.0RC than in 3.4-PAO. ======== Now, for the Signal 11: Since neither my PCMCIA Modem nor Ethernet card were detected, I decided to try ppp via an external modem. As I was entering the phone number of the ISP, I realized I had entered the wrong login ID/password. I decided to cancel and try again. When I selected cancel, it caught a signal 11 and rebooted. I didn't manage to record any other information about the sig 11, even though I was able to repeat it (I didn't think to see if alt-F2 would show anything useful until just now). ======== Once I got the information entered, the ISP didn't answer. I decided to try a different ISP, so I attempted to manually configure the new info with "set phone 846xxxx" etc. Gave the dial command and it used the old phone number, instead of the new one I had just entered. ======== Finally, once I got it to dial correctly, I was greeted with the error "Warning: CHAP 0x80 not available without DES" and then it aborted the install. I repeated from a fresh boot (and entered the ISP info correctly the first time), and got the same error. It also turned up tonight when I started a 3.4R-PAO install. ========= I finally gave up on trying to install the 4.0 snapshot. Tonight I started a 3.4R-PAO (Jan 30 build) install and it all went smoothly except (1) it didn't, as usual, recognize the Eigernet card, and (2) I got the "CHAP 0x80 not available" error. The modem was recognized, unlike the 4.0RC install. I managed to get logged in to an ISP manually so it is now happily doing the install (it has a few hours to go). Tomorrow I will see if I can get it to recognize the Ethernet card (in the past I could get it to be recognized, but then got a driver not initialized error). ========== Unless 3.4R-PAO magically works with the Ethernet card, I will probably wipe the thing some time this week to see if I can do a Corel Linux install on it (if I can find a PCMCIA or parallel port CD-ROM that will work), so I don't mind doing more experimenting with 4.0RC if that will help anyone. By the way, the Linux fmvj18x_cs driver works with the Ethernet card. I've been unable to get the FBSD Fujitsu driver to work with it, nor does ed0. I tried looking at the source, but I have a lot to learn before I have a clue why the Linux driver works with this particular card and the FBSD driver doesn't. The first OS that works with the Ethernet card and also doesn't have too many other quirks gets to live on it for a while. Debian Linux had too many other quirks. FBSD 3.2 (3.3?) had no quirks except the bad Ethercard driver, so I'm rooting for it. Maybe I'll blow a few bucks on a card that will work with it, but it would be more satisfying to fix the driver. Anyone know where I can get a dirt cheap 10base2 + 10baseT PCCARD that works with FreeBSD? -- Bob +-------------------------------------------------------- | Bob Johnson | bobj@atlantic.net +-------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 22: 5:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id EAB5037BE21; Sat, 19 Feb 2000 22:05:10 -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 BAA234142; Sun, 20 Feb 2000 01:04:47 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <42178.951019790@zippy.cdrom.com> References: <42178.951019790@zippy.cdrom.com> Date: Sun, 20 Feb 2000 01:05:07 -0500 To: "Jordan K. Hubbard" , Kris Kennaway From: Garance A Drosihn Subject: Re: openssl in -current Cc: Doug Barton , Victor Salaman , freebsd-current@FreeBSD.ORG Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 8:09 PM -0800 2/19/00, Jordan K. Hubbard wrote: > > Having _a_ general-purpose cryptography toolkit in the base system allows > > us to add in all sorts of cool things to FreeBSD (https support for fetch, > > openssh, random cryptographic enhancements elsewhere). OpenSSL just > > happens to be the only decent freely-available (BSDL) toolkit. > >And I still think that this is a reasonable objective, the current >gymnastics for making it happen making me wonder whether or not that >would not be an objective better moved to sometime in September. This will be a lot easier once the patent expires. We would probably be better off sticking with the ports-version until then, so we don't have to delay 4.0-release until all the issues are sorted out. If 4.0 is delayed, I want it delayed for things which are actually busted, and not to move features from the ports collection to the base system. I think everyone agrees that having a cryptography toolkit in the base system would be great, but we don't have to have it for *this* release, and there are no "cool things" for *this* release which depend on some cryptography toolkit being part of the base system. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 22:15:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id 7C38B37BE8E; Sat, 19 Feb 2000 22:15:41 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA40919; Sat, 19 Feb 2000 22:15:21 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: "Victor A. Salaman" Cc: Doug Barton , Kris Kennaway , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-reply-to: Your message of "Sun, 20 Feb 2000 01:47:44 -0400." <1D45ABC754FB1E4888E508992CE97E4F059CE6@teknos.teknos.com> Date: Sat, 19 Feb 2000 22:15:21 -0800 Message-ID: <40915.951027321@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Don't remove OpenSSL from the three... put the whole thing there, the whole > openssl distro in the tree. The problem with the patent is not that you > CAN'T get the software, the problem is that you can't build with it and use > it. But nobody said that you can't have it in the system. It's up to the > USA_RESIDENT variable that RSAREF would be built (over the net). The only > thing we would need to do is modify sysinstall if you are a USA resident > with a disclaimer screen. That way we put the responsability onto the user, > not the FreeBSD group. The questions which aren't being answered here are "what use is OpenSSL without RSA" and "are we really providing anything of value if we stop short of providing a complete out-of-box solution?" - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 22:17:39 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id E3F1E37BE7E; Sat, 19 Feb 2000 22:17:36 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA08888; Sat, 19 Feb 2000 22:17:36 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 22:17:36 -0800 (PST) From: Kris Kennaway To: "Victor A. Salaman" Cc: "'Jordan K. Hubbard'" , Doug Barton , freebsd-current@FreeBSD.ORG Subject: RE: openssl in -current In-Reply-To: <1D45ABC754FB1E4888E508992CE97E4F059CE6@teknos.teknos.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, Victor A. Salaman wrote: > Don't remove OpenSSL from the three... put the whole thing there, the whole > openssl distro in the tree. The problem with the patent is not that you > CAN'T get the software, the problem is that you can't build with it and use > it. But nobody said that you can't have it in the system. It's up to the > USA_RESIDENT variable that RSAREF would be built (over the net). The only > thing we would need to do is modify sysinstall if you are a USA resident > with a disclaimer screen. That way we put the responsability onto the user, > not the FreeBSD group. This doesn't help. The RSA source not being there isn't the problem, the problem is that there are two different binary versions depending on how you build it (with rsaref or not). Source code builds aren't a problem, they already work fine, it's people who install binary snapshots (e.g. from the CD). Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 22:26:55 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id AD14C37BD99; Sat, 19 Feb 2000 22:26:53 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA09197; Sat, 19 Feb 2000 22:26:53 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 22:26:53 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: "Victor A. Salaman" , Doug Barton , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-Reply-To: <40915.951027321@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jordan K. Hubbard wrote: > The questions which aren't being answered here are "what use is OpenSSL > without RSA" To ports, not much - with the exception of one or two, they all require RSA. Intrinsically, a lot. I have big plans for using openssl in the base system, and if we don't get it in at the start of 4.x then it may have to wait until 5.0 to avoid all the potential integration issues, the kind of which we've already seen. It would be easier the next time around, but I still can't guarantee it won't break -stable :-) > and "are we really providing anything of value if we stop short of > providing a complete out-of-box solution?" It's more of a precursor at this stage. The only difference a user who installs the default non-rsa version will see is that instead of installing automatically when they do a 'make install' of e.g. openssh is that it will prompt them: This port requires RSA crypto, which is not present in your version of OpenSSL. Please see Chapter 6.5 in the handbook for a description of the problem and alternative solutions. They'll read this, discover they need to install a package first and do so, and then everything works fine. Thats how things are now (well, with Jim's patch from earlier tonight). If you can make the necessary changes to sysinstall to ask the questions I posted earlier, it can all be taken care of during sysinstall and will work perfectly thereafter. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 22:31:36 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 8442237BEAE; Sat, 19 Feb 2000 22:31:34 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA09909; Sat, 19 Feb 2000 22:31:34 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 22:31:33 -0800 (PST) From: Kris Kennaway To: Garance A Drosihn Cc: "Jordan K. Hubbard" , Doug Barton , Victor Salaman , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 20 Feb 2000, Garance A Drosihn wrote: > This will be a lot easier once the patent expires. We would probably Yes. > be better off sticking with the ports-version until then, so we don't > have to delay 4.0-release until all the issues are sorted out. If > 4.0 is delayed, I want it delayed for things which are actually busted, > and not to move features from the ports collection to the base system. No-one's talking about delaying 4.0. > I think everyone agrees that having a cryptography toolkit in the > base system would be great, but we don't have to have it for *this* > release, and there are no "cool things" for *this* release which > depend on some cryptography toolkit being part of the base system. Except it's not just this release, it's "for the life of the 4.x branch" given the rules of what should get put into -stable. I really don't want to have to wait another year or more for 5.0-RELEASE before we can start making use of crypto in the recommended version of FreeBSD. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 22:52:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from dt051n0b.san.rr.com (dt051n0b.san.rr.com [204.210.32.11]) by hub.freebsd.org (Postfix) with ESMTP id E158237BF34; Sat, 19 Feb 2000 22:52:52 -0800 (PST) (envelope-from Doug@gorean.org) Received: from gorean.org (master [10.0.0.2]) by dt051n0b.san.rr.com (8.9.3/8.9.3) with ESMTP id WAA59366; Sat, 19 Feb 2000 22:52:48 -0800 (PST) (envelope-from Doug@gorean.org) Message-ID: <38AF8F40.CB06E7C7@gorean.org> Date: Sat, 19 Feb 2000 22:52:48 -0800 From: Doug Barton Organization: Triborough Bridge & Tunnel Authority X-Mailer: Mozilla 4.7 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: Kris Kennaway Cc: "Victor A. Salaman" , "'Jordan K. Hubbard'" , freebsd-current@FreeBSD.org Subject: Re: openssl in -current References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Kris Kennaway wrote: > > On Sun, 20 Feb 2000, Victor A. Salaman wrote: > > > Don't remove OpenSSL from the three... put the whole thing there, the whole > > openssl distro in the tree. The problem with the patent is not that you > > CAN'T get the software, the problem is that you can't build with it and use > > it. But nobody said that you can't have it in the system. It's up to the > > USA_RESIDENT variable that RSAREF would be built (over the net). The only > > thing we would need to do is modify sysinstall if you are a USA resident > > with a disclaimer screen. That way we put the responsability onto the user, > > not the FreeBSD group. > > This doesn't help. The RSA source not being there isn't the problem, the > problem is that there are two different binary versions depending on how > you build it (with rsaref or not). So we do what we do with DES. By default you have openssl without RSA, and the RSA version is available as an after market distribution. All that's required is the work necessary to make the two openssl distributions. As for the ports, most of the ports that have the ability to use RSA also have the ability to turn it off (TMK), usually through a configure --variable. The ones that don't can have warnings spit out. Until the patent runs out, leaving RSA as a port seems to be the only reasonable alternative. Once again, I don't think that the problems here are insurmountable, they will just require some engineering. Doug -- "Welcome to the desert of the real." - Laurence Fishburne as Morpheus, "The Matrix" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 22:56:40 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EB46337BFDD; Sat, 19 Feb 2000 22:55:26 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id WAA11256; Sat, 19 Feb 2000 22:55:26 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 22:55:26 -0800 (PST) From: Kris Kennaway To: Doug Barton Cc: "Victor A. Salaman" , "'Jordan K. Hubbard'" , freebsd-current@FreeBSD.org Subject: Re: openssl in -current In-Reply-To: <38AF8F40.CB06E7C7@gorean.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Doug Barton wrote: > > This doesn't help. The RSA source not being there isn't the problem, the > > problem is that there are two different binary versions depending on how > > you build it (with rsaref or not). > > So we do what we do with DES. By default you have openssl without RSA, and > the RSA version is available as an after market distribution. All that's > required is the work necessary to make the two openssl distributions. Already done. > As for the ports, most of the ports that have the ability to use > RSA also have the ability to turn it off (TMK), usually through a > configure --variable. The ones that don't can have warnings spit out. > Until the patent runs out, leaving RSA as a port seems to be the only > reasonable alternative. This actually isn't true. Things like openssh, sslwrap, sslproxy, stunnel, etc, all require it by design. But as I've already pointed out, when a user tries to install the port and they dont have RSA, they'll get a warning telling them how to get the package which provides it. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 23: 3:34 2000 Delivered-To: freebsd-current@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 7BE4F37BEE6 for ; Sat, 19 Feb 2000 22:56:19 -0800 (PST) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id WAA99193; Sat, 19 Feb 2000 22:56:18 -0800 (PST) (envelope-from dillon) Date: Sat, 19 Feb 2000 22:56:18 -0800 (PST) From: Matthew Dillon Message-Id: <200002200656.WAA99193@apollo.backplane.com> To: Julian Elischer Cc: current@FreeBSD.ORG Subject: Re: I'm baaaaack References: <38AF6A0C.167EB0E7@elischer.org> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :I'm back and resubscribed to a subset of lists :(hackers, announce and current) :My connectivity is still shitty, but I'm working on it :and have managed to Cvsup my cvs tree up-to-date. : : :Julian : :-- :+------------------------------------+ :| __--_|\ Julian Elischer | :| / \ julian@elischer.org +--from Perth to the world. Wait, wait! Not yet! (Slams door), Quick, everyone start glueing all the source code back together again! -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 23:12:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.100.7]) by hub.freebsd.org (Postfix) with ESMTP id 4871537C032; Sat, 19 Feb 2000 23:11:46 -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 CAA297472; Sun, 20 Feb 2000 02:11:43 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: References: Date: Sun, 20 Feb 2000 02:12:06 -0500 To: Kris Kennaway From: Garance A Drosihn Subject: Re: openssl in -current Cc: "Jordan K. Hubbard" , Doug Barton , Victor Salaman , freebsd-current@FreeBSD.org Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 10:31 PM -0800 2/19/00, Kris Kennaway wrote: > > if 4.0 is delayed, I want it delayed for things which are actually busted, > > and not to move features from the ports collection to the base system. > >No-one's talking about delaying 4.0. Not directly, but all the work trying to figure this out is work that could be going elsewhere in the 4.0 release. And if we did happen to get to the point where everything else WAS worked out, but this was not, then what would you want to happen? > > I think everyone agrees that having a cryptography toolkit in the > > base system would be great, but we don't have to have it for *this* > > release, and there are no "cool things" for *this* release which > > depend on some cryptography toolkit being part of the base system. > >Except it's not just this release, it's "for the life of the 4.x branch" >given the rules of what should get put into -stable. I really don't want >to have to wait another year or more for 5.0-RELEASE before we can start >making use of crypto in the recommended version of FreeBSD. Hmm. Well, I agree that I would not want to wait quite that long. If it absolutely must be in the base system for 4.0 for us to have it there in 4.x, then I guess I'd put the RSA-less (basically useless) version in the base system now, and then "update" that come september. Either that, or make the exception for this and say it will be in 4.1 even though it didn't make it for 4.0. I realize none of these are particularly attractive strategies, of course... I am agreeable to any strategy which helps get us to the goal of a cryptography kit in the base system, as long as it doesn't cause too much of a delay, and it won't cause any legal problems for people distributing freebsd. --- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or drosih@rpi.edu Rensselaer Polytechnic Institute To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 23:17:43 2000 Delivered-To: freebsd-current@freebsd.org Received: from teknos.teknos.com (teknos-gw.nappr.org [216.0.190.254]) by hub.freebsd.org (Postfix) with ESMTP id 3959537BEA9; Sat, 19 Feb 2000 23:17:35 -0800 (PST) (envelope-from salaman@teknos.com) Received: by teknos.teknos.com with Internet Mail Service (5.5.2650.21) id <19NW71HZ>; Sun, 20 Feb 2000 03:12:30 -0400 Message-ID: <1D45ABC754FB1E4888E508992CE97E4F059CE8@teknos.teknos.com> From: "Victor A. Salaman" To: 'Kris Kennaway' , Garance A Drosihn Cc: "Jordan K. Hubbard" , Doug Barton , freebsd-current@FreeBSD.ORG Subject: RE: openssl in -current Date: Sun, 20 Feb 2000 03:12:26 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting from OpenBSD: "We took a free license release of ssh and OpenBSD-ifyed it. We get around the USA-based RSA patent by providing an easy way to automatically download and install a RSA-enabled package containing shared library versions of libcrypto and libssl. These packages are based on OpenSSL. People living outside the USA can freely use the RSA patented code, while people inside the USA can freely use it for non-commercial purposes. It appears as if companies inside the USA can use the RSA libraries too, as long as RSA is not used in a profit generating role. But this way almost everyone will get ssh built-in." I have just read several documents from www.eff.org, www.rsa.com, and www.openssl.org and have failed to find anything in there, that forbids us from not using openssl's RSA version. RSA has a patent for the algorithm, and they have provided a reference implementation to help the adoption of the algorithm. In their license (RSAREF) it says you can't export the code outside USA, but the US ITAR laws don't say anything about importing. So in theory, if the CD was made outside the USA, then it could be imported without a single problem. The whole RSA scheme is bogus, because anyone in the world can get an implementation of RSA, so its widely accesible, so why all this RSAREF/non-RSAREF mumbo-jumbo? Perhaps we should send e-mail to RSA to clarify this, and in light of this, ask for permission to distribute RSA with the base OS. Gee, we can get RSA anyway, so what's the point on making harder? Does anyone have ANY document saying that if you are in the US you are obligued to use RSAREF? -----Original Message----- From: Kris Kennaway [mailto:kris@FreeBSD.org] Sent: Sunday, February 20, 2000 2:32 AM To: Garance A Drosihn Cc: Jordan K. Hubbard; Doug Barton; Victor Salaman; freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current On Sun, 20 Feb 2000, Garance A Drosihn wrote: > This will be a lot easier once the patent expires. We would probably Yes. > be better off sticking with the ports-version until then, so we don't > have to delay 4.0-release until all the issues are sorted out. If > 4.0 is delayed, I want it delayed for things which are actually busted, > and not to move features from the ports collection to the base system. No-one's talking about delaying 4.0. > I think everyone agrees that having a cryptography toolkit in the > base system would be great, but we don't have to have it for *this* > release, and there are no "cool things" for *this* release which > depend on some cryptography toolkit being part of the base system. Except it's not just this release, it's "for the life of the 4.x branch" given the rules of what should get put into -stable. I really don't want to have to wait another year or more for 5.0-RELEASE before we can start making use of crypto in the recommended version of FreeBSD. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 23:31:54 2000 Delivered-To: freebsd-current@freebsd.org Received: from zippy.cdrom.com (zippy.cdrom.com [204.216.27.228]) by hub.freebsd.org (Postfix) with ESMTP id AC71937BE57; Sat, 19 Feb 2000 23:31:51 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) Received: from zippy.cdrom.com (jkh@localhost [127.0.0.1]) by zippy.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA58754; Sat, 19 Feb 2000 23:31:42 -0800 (PST) (envelope-from jkh@zippy.cdrom.com) To: Kris Kennaway Cc: Victor Salaman , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-reply-to: Your message of "Sat, 19 Feb 2000 20:40:39 PST." Date: Sat, 19 Feb 2000 23:31:42 -0800 Message-ID: <58727.951031902@zippy.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Well, you're the release engineer of course..but I don't think the > problems are insurmountable. Sysinstall could be made to install the > correct package after asking the user the right questions (if they choose > to install crypto): Again, I simply do not wish to depend on any more packages from sysinstall. I'm not trying to be difficult here, it's simply a fact that they: 1) Make my QA process a lot more difficult and error-prone. I don't get to build them myself, I can't fix really them myself if they break, I just plain don't have any control over the circumstances under which such packages are built (in a clean chroot tree, a freshly installed box, whatever's necessary to ensure they're "clean") and that really bothers me. With the distribution tarballs, it's very clear to me just how every piece is built and I have a thread to follow if (when) something breaks. 2) Cause me version-sync problems for sysinstall when things off in ports-land change and it requires someone who knows that sysinstall depends on these things to go look at syncing things up again. Since that's currently mostly just me, I represent a single point of failure when I forget. :) 3) Cost me (us) valuable testing time when I've got a release snapshot ready to go but no up-to-date package(s) which are in sync with it (say a header or library it depends on has changed). If it takes 4 of us to produce "a release" then we've lost a lot of the advantage we gained by automating it in the first place and make it that much more difficult to coordinate the release of one. This essentially underscores a point I've also made many times: There is a very fuzzy division between /usr/src and /usr/ports and that fact costs us every time this sort of thing comes up. If you start depending on ports from src, you both make the lines even fuzzier and you make the entire release building process no more robust than the weakest part of the build chain. In the case of the docports, for example, that part of the chain has often been very weak indeed and frequently requires setting NODOC=YES by default or I don't get any snapshots done at all for long periods of time. If I have to do the same thing for crypto, I've just doubled my exposure and the amount of tarball download time a make release already requires. If you see a better way out of this, I'm all for hearing about it. All I've done with sysinstall so far is set USA_RESIDENT=YES in /etc/make.conf now if you select Yes at the DES distribution menu (which is already covered with all kinds of legal disclaimers). - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 23:37:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 0D6E637BD80; Sat, 19 Feb 2000 23:37:06 -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 CAA30257; Sun, 20 Feb 2000 02:37:02 -0500 Date: Sun, 20 Feb 2000 02:37:01 -0500 (EST) From: Mike Nowlin To: "Victor A. Salaman" Cc: "'Kris Kennaway'" , Garance A Drosihn , "Jordan K. Hubbard" , Doug Barton , freebsd-current@FreeBSD.ORG Subject: RE: openssl in -current In-Reply-To: <1D45ABC754FB1E4888E508992CE97E4F059CE8@teknos.teknos.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > The whole RSA scheme is bogus, because anyone in the world can get an > implementation of RSA, so its widely accesible, so why all this > RSAREF/non-RSAREF mumbo-jumbo? Because US patent law is pretty dumb.... :) --mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message From owner-freebsd-current Sat Feb 19 23:41:25 2000 Delivered-To: freebsd-current@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 497B637BE9F; Sat, 19 Feb 2000 23:41:23 -0800 (PST) (envelope-from kris@FreeBSD.org) Received: from localhost (kris@localhost) by freefall.freebsd.org (8.9.3/8.9.2) with ESMTP id XAA13227; Sat, 19 Feb 2000 23:41:23 -0800 (PST) (envelope-from kris@FreeBSD.org) X-Authentication-Warning: freefall.freebsd.org: kris owned process doing -bs Date: Sat, 19 Feb 2000 23:41:22 -0800 (PST) From: Kris Kennaway To: "Jordan K. Hubbard" Cc: Victor Salaman , freebsd-current@FreeBSD.ORG Subject: Re: openssl in -current In-Reply-To: <58727.951031902@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 19 Feb 2000, Jordan K. Hubbard wrote: > If you see a better way out of this, I'm all for hearing about it. > All I've done with sysinstall so far is set USA_RESIDENT=YES in > /etc/make.conf now if you select Yes at the DES distribution menu > (which is already covered with all kinds of legal disclaimers). Given that we can't import rsaref into FreeBSD and we can't depend on it as a port, that about rules out any options for installing from sysinstall. The remaining possibility is what we have now, namely manual installation of the package post-installation, which is documented in the handbook and referred to when they try and install a port which requires it. Kris ---- "How many roads must a man walk down, before you call him a man?" "Eight!" "That was a rhetorical question!" "Oh..then, seven!" -- Homer Simpson To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message